Hi, I have Comcast HSI 50Mbps in Hillsboro OR with a SB6121 modem. I've had the service for a few months now with no problems. Then recently I've been getting consistent connectivity failures. Very bad packet drops or no connection to the internet at all. Also this happens during all times of the day, not just times of highest congestion. Its extremely disruptive to my work since I VPN in sometimes.
Usually I chalk it up to congestion or something, but this time I looked at the logs and it seems the date/time gets reset and my modem freaks out. During the down time, the whole lights (for up and down link etc) are all solid and green/whatever color stands for good. After a reboot of the modem usually my connection comes back up (but not always).
Could anyone please take a look and give me some pointers?
Help:
-------------------------------------------
Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.10-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 5.0
Serial Number: removed
Firmware Build Time: Oct 29 2012 18:07:13
Signal:
-------------------------------------------
Downstream Bonding Channel Value
Channel ID 9 10 11 12
Frequency 561000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
4 dBmV 5 dBmV 5 dBmV 4 dBmV
Upstream Bonding Channel Value
Channel ID 1 2 3 4
Frequency 32400000 Hz 22800000 Hz 15700000 Hz 37400000 Hz
Ranging Service ID 4530 4530 4530 4530
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec
Power Level 46 dBmV 46 dBmV 46 dBmV 46 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
[3] 64QAM
Ranging Status Success Success Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 9 10 11 12
Total Unerrored Codewords 17883117 16378785 16378961 16379134
Total Correctable Codewords 12 6 8 13
Total Uncorrectable Codewords 686 596 564 536
LOGS:
-------------------------------------------
Feb 27 2014 14:12:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2014 14:03:44 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=removed;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2014 14:02:52 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2014 14:01:22 5-Warning T202.0 Lost MDD Timeout;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2014 14:00:58 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:38:09 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:38:07 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=removed;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:37:18 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:35:19 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:34:42 5-Warning T202.0 Lost MDD Timeout;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:34:19 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 15:33:47 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 14:39:46 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 14:38:44 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
Feb 26 2014 14:28:45 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=removed;CMTS-MAC=00:1d:70:af:c4:39;CM-QOS=1.1;CM-VER=3.0;
↧