bic007's profile

Frequent Visitor

 • 

6 Messages

Tue, Nov 24, 2020 11:00 AM

Arris SB8200 signals

We started having intermittent internet outages for the past 6 hours. We have a 100/5MB  connection from Xfinity which has never given us any problems in the past. 

I wanted to post the numbers from our Arris SB8200 cable modem to see if anyone who understands these numbers sees a problem with them.   Could it be the Arris cable modem going bad, or could there be a problem with our tap or with the closest amp in the Xfinity cable system?   

Downstream Bonded Channels
Channel IDLock StatusModulationFrequencyPowerSNR/MERCorrectedUncorrectables
20LockedQAM256507000000 Hz-10.9 dBmV26.9 dB490825066131162
4LockedQAM256399000000 Hz-11.5 dBmV27.8 dB70121001905
5LockedQAM256405000000 Hz-11.5 dBmV27.6 dB94441515424
6LockedQAM256411000000 Hz-11.7 dBmV27.5 dB1569090334215
7LockedQAM256417000000 Hz-11.8 dBmV27.3 dB23571825163167
8LockedQAM256423000000 Hz-11.8 dBmV27.2 dB27076977288187
9LockedQAM256429000000 Hz-11.7 dBmV27.2 dB26070129245668
10LockedQAM256435000000 Hz-11.6 dBmV27.2 dB26312244255121
11LockedQAM256441000000 Hz-11.8 dBmV27.0 dB401896171805617
12LockedQAM256453000000 Hz-11.7 dBmV26.9 dB459412004405535
13LockedQAM256459000000 Hz-11.9 dBmV26.7 dB4788235811120522
14LockedQAM256465000000 Hz-11.9 dBmV26.7 dB4545279617333942
15LockedQAM256471000000 Hz-11.9 dBmV26.6 dB3906647926934748
16LockedQAM256477000000 Hz-11.8 dBmV26.6 dB3870583327415325
17LockedQAM256483000000 Hz-11.7 dBmV26.5 dB3899025227037161
18LockedQAM256489000000 Hz-11.5 dBmV26.7 dB4229312022475059
19LockedQAM256495000000 Hz-11.2 dBmV26.7 dB4624879215804498
21LockedQAM256513000000 Hz-10.9 dBmV26.9 dB473056125962808
22LockedQAM256519000000 Hz-10.6 dBmV27.0 dB385218181427157
23LockedQAM256525000000 Hz-10.6 dBmV27.1 dB34335380812047
24LockedQAM256531000000 Hz-10.3 dBmV27.3 dB23325969154060
25LockedQAM256537000000 Hz-10.0 dBmV27.5 dB1362966419957
26LockedQAM256543000000 Hz-9.8 dBmV27.7 dB87928814100
27LockedQAM256549000000 Hz-9.4 dBmV28.1 dB4028664254
28LockedQAM256555000000 Hz-9.1 dBmV28.2 dB3201838112
29LockedQAM256561000000 Hz-8.7 dBmV28.5 dB142535414
30LockedQAM256567000000 Hz-8.6 dBmV28.6 dB10721134
31LockedQAM256573000000 Hz-8.4 dBmV28.8 dB7570600
32LockedQAM256579000000 Hz-8.3 dBmV28.8 dB5768191
33LockedQAM256585000000 Hz-8.2 dBmV28.9 dB4474800
34LockedQAM256591000000 Hz-8.0 dBmV29.2 dB2346330
48LockedOther722000000 Hz-7.5 dBmV27.0 dB14657379426462694


 

 
Upstream Bonded Channels
ChannelChannel IDLock StatusUS Channel TypeFrequencyWidthPower
170LockedSC-QAM Upstream30100000 Hz6400000 Hz39.0 dBmV
269LockedSC-QAM Upstream36500000 Hz6400000 Hz39.0 dBmV
371LockedSC-QAM Upstream23700000 Hz6400000 Hz39.0 dBmV
472LockedSC-QAM Upstream17300000 Hz6400000 Hz39.0 dBmV

Responses

Accepted Solution

EG

Expert

 • 

87.2K Messages

7 m ago

The downstream power is too low / out of spec, as is the SNR. That can cause random disconnects, spontaneous / s re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

Frequent Visitor

 • 

6 Messages

7 m ago

Thank you @EG . 

 

We only have internet at our townhouse.  No TV or phone, so no other equipment and no splitters within the townhouse.   As far as I know, there are not any splitters between the tap and what comes into the basement from the Comcast cable box on the outside of the town house.  When we were first connected, we did not have a dedicated drop from the pedestal to the cable box on the outside of the house, so they put us on a splitter to share with the unit next to us until the drop was installed.   When the drop was installed, they said they took our connection off the splitter.  This all happened last April, but due to having to keep our distance, I did not go out and look in the cable box to verify that the splitter had been removed.   We never had an issue during the few weeks were shared a drop and until today, never an issue while on our own drop.   The townhouse is two years old.  All Internal Coax is  RG6.  The cable modem is currently in the family room, so there are two  F connector splices between the cable modem the outside box; one in the utility room and one in the wall plate in the family room.   

We do have a tech coming tomorrow morning. 

EG

Expert

 • 

87.2K Messages

7 m ago

Bear in mind that if the premises facing techs can not find or fix a problem at your premises, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home.
Good luck with it !

Frequent Visitor

 • 

6 Messages

7 m ago


@EG wrote:

The downstream power is too low / out of spec, as is the SNR. That can cause random disconnects, spontaneous / s re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


@EG   

BTW... what are the ideal Power and SNR levels that we should hope to see?   We are definitely seeing random disconnects, and the speeds I've measured when we do have a connection range from  2 - 15 Mbps  down and 4 - 5 Mbps up.    My VoIP phone reboots itself every time the internet is lost for 10-30 seconds or so, and I have been watching it reboot every two or three minutes.   Makes comms with our HQ offices impossible. 

I also meant to post the latest event log from the Arris SB8200.  I certainly don't understand the events. 

Date Time Event ID Event Level Description

11/24/2020 12:52840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:51740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:51840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:51740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 15 16; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:51740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:51840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 16 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 16 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49820005003"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 15 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 13 14 16 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:49840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48820005003"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 14 15 17 18 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 16 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:48840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 16 17 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:47840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:46740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:46740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 14 15 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:46840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 16 17 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 17 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 13 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:45820005003"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:44840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:44740101006"CM-STATUS message sent. Event Type Code: 4; Chan ID: 7 11 12 13 14 15 18 19 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:44740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 16 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:44840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:44740101006"CM-STATUS message sent. Event Type Code: 1; Chan ID: 14 15 16 17 18 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;CM-VER=3.1;"
11/24/2020 12:44840203005"MDD message timeout;CM-MAC=b0:da:f9:2b:49:d9;CMTS-MAC=00:01:5c:83:68:57;CM-QOS=1.1;C



EG

Expert

 • 

87.2K Messages

7 m ago

From the pinned Troubleshooting Tips topic at the top of this board;

 

 

Specification      Min             Max

Downstream Power Level  
Cable Modems-10dBmV+10dBmV
Gateways and EMTAs-7dBmV+7dBmV
Downstream Signal to Noise Ratio35dB-
Upstream Power Level+35dBmV+50dBmV
Upstream Signal to Noise Ratio31dB-
Upstream Receive Power-2dBmV+2dBmV

 

EG

Expert

 • 

87.2K Messages

7 m ago

Nope. The downstream power levels and the SNR's are still out of spec. More work is needed.

Frequent Visitor

 • 

6 Messages

7 m ago

The Xfinity techician visited this morning.  He first checked signals at the network box and said the signals/power levers from the tap looked good. 

He was able to see the power and SNR levels for the modem and could see those levers were not good.  He warned that it could be that the modem was going bad, but said he would check the terminations.   He noted that the coax terminations were not done very well.   These terminatinos were not done by Xfinity.  They never had a chance to come in the home last spring since on the very day of our install, the technicians in our area had been ordered to no longer enter homes due to COVID-19 risks.  Therefore, the terminations were done by third party network installer who was willing to enter homes.  Since everything worked fine once those original terminations were done, we trusted the terminations had been done right.   

Here is a photo showing a normal termination on the left, the builder's electrical contractor's termination at a wall plate 2nd from left, and the third party network installer's two terminations on the right.   

bic007_0-1606321788839.png

In case this photo doesn't show in this forum thread, here is an imgur link:
One good - three bad  - Imgur

The tech that visited this morning said that over time with temp changes or any vibrations, like a furnace in next to the wall were all the cables terminate, could cause a barely working connection to stop working as well as it once had.  The tech also checked the wall jack termination, which had been done by the builder's electrical contractor. That termination was also not correctly "seated".  

After the Xfinity tech re-terminated all the connections and hooked up the cable modem the internet returned to normal speeds and stopped dropping connections. I think these power levels and SNR values might be more normal now: 

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
4 Locked QAM256 399000000 Hz -16.1 dBmV 34.5 dB 2186 0
5 Locked QAM256 405000000 Hz -16.1 dBmV 34.3 dB 2474 0
6 Locked QAM256 411000000 Hz -16.1 dBmV 34.2 dB 2859 0
7 Locked QAM256 417000000 Hz -16.3 dBmV 34.0 dB 3672 0
8 Locked QAM256 423000000 Hz -16.3 dBmV 33.9 dB 3227 0
9 Locked QAM256 429000000 Hz -16.1 dBmV 34.0 dB 2903 0
10 Locked QAM256 435000000 Hz -16.1 dBmV 33.9 dB 2621 0
11 Locked QAM256 441000000 Hz -16.3 dBmV 33.7 dB 3685 0
12 Locked QAM256 453000000 Hz -16.2 dBmV 33.6 dB 3137 0
13 Locked QAM256 459000000 Hz -16.2 dBmV 33.5 dB 3251 0
14 Locked QAM256 465000000 Hz -16.1 dBmV 33.5 dB 3073 0
15 Locked QAM256 471000000 Hz -16.1 dBmV 33.4 dB 3367 0
16 Locked QAM256 477000000 Hz -15.9 dBmV 33.4 dB 2724 0
17 Locked QAM256 483000000 Hz -15.9 dBmV 33.2 dB 3063 0
18 Locked QAM256 489000000 Hz -15.7 dBmV 33.3 dB 2371 0
19 Locked QAM256 495000000 Hz -15.5 dBmV 33.4 dB 2737 0
20 Locked QAM256 507000000 Hz -15.0 dBmV 33.4 dB 1839 0
21 Locked QAM256 513000000 Hz -15.0 dBmV 33.3 dB 2199 0
22 Locked QAM256 519000000 Hz -14.7 dBmV 33.5 dB 1702 0
23 Locked QAM256 525000000 Hz -14.6 dBmV 33.5 dB 1921 0
24 Locked QAM256 531000000 Hz -14.4 dBmV 33.5 dB 1696 0
25 Locked QAM256 537000000 Hz -14.1 dBmV 33.6 dB 1683 0
26 Locked QAM256 543000000 Hz -14.0 dBmV 33.6 dB 1653 0
27 Locked QAM256 549000000 Hz -13.7 dBmV 33.7 dB 1396 0
28 Locked QAM256 555000000 Hz -13.5 dBmV 33.7 dB 1373 0
29 Locked QAM256 561000000 Hz -13.1 dBmV 33.9 dB 1244 0
30 Locked QAM256 567000000 Hz -13.0 dBmV 33.9 dB 1340 0
31 Locked QAM256 573000000 Hz -12.8 dBmV 33.8 dB 1379 0
32 Locked QAM256 579000000 Hz -12.5 dBmV 33.9 dB 1218 0
33 Locked QAM256 585000000 Hz -12.4 dBmV 33.9 dB 1407 0
34 Locked QAM256 591000000 Hz -12.2 dBmV 33.9 dB 1225 0
48 Locked Other 722000000 Hz -11.3 dBmV 30.8 dB 241287930 18185485


 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 70 Locked SC-QAM Upstream 30100000 Hz 6400000 Hz 44.0 dBmV
2 69 Locked SC-QAM Upstream 36500000 Hz 6400000 Hz 44.0 dBmV
3 71 Locked SC-QAM Upstream 23700000 Hz 6400000 Hz 44.0 dBmV
4 72 Locked SC-QAM Upstream 17300000 Hz 6400000 Hz 44.0 dBmV





Frequent Visitor

 • 

6 Messages

7 m ago

@EG 
How do I convince Xfinity that more work is needed?

Also, since Xfinity left, I was able to reach 192.168.100.1  just once.   I can no longer navigate to my SB8200 and just get a message that says  192.168.100.1 refused to connect. 

EG

Expert

 • 

87.2K Messages

7 m ago

Any tech worth their salt can obviously see that the numbers are off. Show them this thread.

New to the Community?

Start Here