Xfinity plant
Xfinity globe
Community Forum

Is my SB8200 functioning optimally? Signal info & Event Log

Regular Visitor

Is my SB8200 functioning optimally? Signal info & Event Log

The reason I a posting this, is that I have recently starting monitoring our home alarm via internet connection, and want to be sure my connection is as good as possible to keep my monitoring online.  I was informed that my alarm lost connection over the past weekend.

 

I have had issues with disconnects in the past, but not recently.  We did have an outage somewhat recently where I believe a repair was being done upstream and things seem to have been better since.  Hopefully all is good now, but I would appreciate any input concerning my current signal levels and event log.

 

Here is my event log-

 

Time Priority Description
5-1-2018, 14:21:38 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:36 Notice(6) "Honoring MDD; IP provisioning mode = IPv6"
1-1-1970, 0:1:30 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:24 Warning(5) "ToD request sent- No Response received;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:22 Critical(3) "TFTP Request Retries exceeded, CM unable to register "
1-1-1970, 0:1:22 Critical(3) "TFTP failed - Request sent - No Response;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:7 Warning(5) "ToD request sent- No Response received;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:41 Notice(6) "Honoring MDD; IP provisioning mode = IPv6"
1-1-1970, 0:0:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:37 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
4-25-2018, 2:36:16 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:32 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:31 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:31 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:31 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:30 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:30 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:29 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:3:29 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:2:15 Critical(3) "TFTP Request Retries exceeded, CM unable to register "
1-1-1970, 0:2:15 Critical(3) "TFTP failed - Request sent - No Response;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:31 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:1:24 Critical(3) "TFTP Request Retries exceeded, CM unable to register "
1-1-1970, 0:1:24 Critical(3) "TFTP failed - Request sent - No Response;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:38 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:43 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
4-6-2018, 3:50:44 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:7:23 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"
1-1-1970, 0:6:56 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
4-6-2018, 3:42:13 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:45:1d;CMTS-MAC=00:01:5c:aa:9c:66;CM-QOS=1.1;CM-VER=3.1;"

 

And here are signal levels-

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 687000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed
Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
30 Locked QAM256 687000000 Hz 1.2 dBmV 40.4 dB 0 0
1 Locked QAM256 513000000 Hz -1.6 dBmV 39.3 dB 0 0
2 Locked QAM256 519000000 Hz -1.3 dBmV 39.5 dB 0 0
3 Locked QAM256 525000000 Hz -1.1 dBmV 39.3 dB 0 0
4 Locked QAM256 531000000 Hz -0.9 dBmV 39.4 dB 0 0
5 Locked QAM256 537000000 Hz -0.6 dBmV 39.5 dB 0 0
6 Locked QAM256 543000000 Hz -0.5 dBmV 39.7 dB 0 0
7 Locked QAM256 549000000 Hz -0.2 dBmV 39.8 dB 0 0
8 Locked QAM256 555000000 Hz -0.1 dBmV 39.8 dB 0 0
9 Locked QAM256 561000000 Hz -0.1 dBmV 39.5 dB 0 0
10 Locked QAM256 567000000 Hz -0.1 dBmV 39.7 dB 0 0
11 Locked QAM256 573000000 Hz -0.2 dBmV 39.5 dB 0 0
12 Locked QAM256 579000000 Hz -0.3 dBmV 39.4 dB 0 0
13 Locked QAM256 585000000 Hz -0.3 dBmV 39.4 dB 0 0
14 Locked QAM256 591000000 Hz -0.4 dBmV 39.2 dB 0 0
15 Locked QAM256 597000000 Hz -0.3 dBmV 39.3 dB 0 0
16 Locked QAM256 603000000 Hz -0.1 dBmV 39.4 dB 0 0
17 Locked QAM256 609000000 Hz -0.2 dBmV 39.6 dB 0 0
18 Locked QAM256 615000000 Hz -0.1 dBmV 39.7 dB 0 0
19 Locked QAM256 621000000 Hz 0.2 dBmV 39.9 dB 0 0
20 Locked QAM256 627000000 Hz 0.3 dBmV 39.8 dB 0 0
21 Locked QAM256 633000000 Hz 0.7 dBmV 40.0 dB 0 0
22 Locked QAM256 639000000 Hz 0.6 dBmV 40.1 dB 0 0
23 Locked QAM256 645000000 Hz 0.7 dBmV 40.3 dB 0 0
24 Locked QAM256 651000000 Hz 0.9 dBmV 40.3 dB 0 0
25 Locked QAM256 657000000 Hz 0.9 dBmV 40.4 dB 0 0
26 Locked QAM256 663000000 Hz 1.1 dBmV 40.5 dB 0 0
27 Locked QAM256 669000000 Hz 1.1 dBmV 40.6 dB 0 0
28 Locked QAM256 675000000 Hz 1.0 dBmV 40.3 dB 0 0
29 Locked QAM256 681000000 Hz 1.1 dBmV 40.6 dB 0 0
31 Locked QAM256 693000000 Hz 1.2 dBmV 40.6 dB 0 0
32 Locked Other 750000000 Hz 3.0 dBmV 39.8 dB 241811 0
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 2 Locked SC-QAM 29400000 Hz 6400000 Hz 39.5 dBmV
2 1 Locked SC-QAM 35800000 Hz 6400000 Hz 39.0 dBmV
3 3 Locked SC-QAM 23000000 Hz 6400000 Hz 39.5 dBmV
Current System Time: Wed May 2 02:42:52 2018

Expert

Re: Is my SB8200 functioning optimally? Signal info & Event Log

The stats at that moment were o/k. FWIW most of those error log entries are unhelpful and basically useless because they have the default 1970 date/time stamp so they can't really be used for troubleshooting and are invalid. The default time happens when a modem is re-booted/powercycled either deliberately by the end user or spontaneously because of connectivity / signal issues with the system and spits out a number of random errors caused by the re-boot. Makes the entries look more numerous than they really are.