dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
14
alternety
join:2009-01-05
Anacortes, WA

1 edit

alternety to Johkal

Member

to Johkal

Re: SB6120 continuously blinking activity light

I will go figure out if I can do that. I do not remember what the logon/password was since I assumed that when Comcast provisioned it I would be locked out.

However, the check I had Comcast do indicated good levels and they reported there was nothing wrong in their look at the modem.

Speedtest is showing normal results. Everything seems to be working just fine - except for the unknown exchanges.

Johkal
Cool Cat
MVM
join:2002-11-13
Pennsyltucky

Johkal

MVM

»192.168.100.1/
alternety
join:2009-01-05
Anacortes, WA

alternety

Member

Downstream 1 dBmV on both channels.

Upstream 48 dBmV

Total Unerrored Codewords 3549669358 3549668952
Total Correctable Codewords 16 0
Total Uncorrectable Codewords 1533 2131

Jan 01 1970 00:00:31 3-Critical D05.0 TFTP failed - Request sent - No Response;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:29 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:03:08 3-Critical D02.0 DHCP FAILED - Request sent, No response;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:08 3-Critical D02.0 DHCP FAILED - Request sent, No response;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Dec 03 2009 03:36:00 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Dec 03 2009 03:35:36 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:46 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;
Dec 03 2009 03:24:33 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:20:0b;CMTS-MAC=00:1d:70:b0:0e:b4;CM-QOS=1.1;CM-VER=3.0;

Firmware Name: SB6120-1.0.2.1-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 1.0
Firmware Build Time: Jul 20 2009 20:04:47

Johkal
Cool Cat
MVM
join:2002-11-13
Pennsyltucky

1 recommendation

Johkal

MVM

Keep an eye on your log entries for this:

"Critical D05.0 TFTP failed - Request sent - No Response"

If you see this reoccurring, post over in the "Comcast Direct Forum" so someone can address this.

»Comcast Direct
taffeys
join:2009-11-30
Oceanside, CA

taffeys to alternety

Member

to alternety
The modem is constantly receiving requests, when I look at my firewall log those requests occur all the time but my firewall blocks them.
alternety
join:2009-01-05
Anacortes, WA

alternety

Member

It is a significant change in the way the modem is working.

3 - 4 months: not doing this

Starting Wednesday night: doing this

What has changed? What does it mean? Is it indicative of a problem? How do I make it go back to what it was doing? Is the modem bad?

Two 05 level errors at uncorrelatable times would not seem to be the cause of this behavior. At least one of those is probably related to testing or power cycling.
alternety

alternety

Member

I have been searching about some more to see if I can get some idea why this is happening. A thought occurred to me. Could there have been a firmware update from Comcast that changed this behavior. Is there a config parameter that would alter the behavior of the modem in this way?