M

Sunday, July 30th, 2023 4:33 AM

Closed

At my wit's end over intermittent connectivity issues and keep getting told there isn't a problem

This has been going on close to two months now. Periodically and at random times, out service cuts out. We had an Xfinity gateway and the modem would reboot. Got in touch with customer service. They scheduled a service call. Service got restored. Service call cancelled. This happened again the next day, again service call cancelled. The third day, I refused to let them cancel on me. Tech came out, ran some tests, removed an unnecessary splitter from the basement so the modem was connected more directly to the outside source, and replaced our gateway. Issues persisted. I ordered an Arris SB8200 and a Nighthawk, thinking maybe if I upgraded the equipment, I could see what was going on better and could improve our reliability. Issues persisted. Tech 2 comes to the house and actually shows me that there are problems. He can see the "noise" on his system. He back-tracks and was going to replace the line which runs from the pole underground (under the driveway) and into the crawlspace. He ended up replacing the ends. I thought the problems were resolved because he showed me his diagnostic tool again and showed the noise was gone. Later that evening, the internet went out again. It just so happened, I hadn't responded to the text survey yet, so I did and stated the problem wasn't fixed. A supervisor called me the next day and told me he was going to watch our service and get back to me. The issues persisted, so I contacted support again and got a third tech to come out. This guy comes out, tells me everything is fine, shows me his diagnostic tools (which look way different than the previous tech btw) and how all our signal levels are green and our WAN score was 98.5 which is "Outstanding". He then reaches up to the modem and says "oh this connection is way too loose". The previous tech apparently didn't tighten it back down. I should have checked that, but oh well...maybe the problem is finally fixed....NOPE. More issues the last two days. I ignored yesterday because there were outages in the area due to a storm. Today, no problems in the area. So I log into the modem and find the following....

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 495000000 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
17 Locked QAM256 495000000 Hz 9.3 dBmV 41.7 dB 0 0
14 Locked QAM256 477000000 Hz 9.4 dBmV 41.9 dB 1 0
15 Locked QAM256 483000000 Hz 9.5 dBmV 41.8 dB 1 0
16 Locked QAM256 489000000 Hz 9.4 dBmV 41.7 dB 2 0
18 Locked QAM256 507000000 Hz 9.0 dBmV 41.6 dB 0 0
19 Locked QAM256 513000000 Hz 8.9 dBmV 41.5 dB 1 0
20 Locked QAM256 519000000 Hz 8.6 dBmV 41.4 dB 0 0
21 Locked QAM256 525000000 Hz 8.6 dBmV 41.4 dB 1 0
22 Locked QAM256 531000000 Hz 8.7 dBmV 41.5 dB 6 0
23 Locked QAM256 537000000 Hz 8.7 dBmV 41.5 dB 1 0
24 Locked QAM256 543000000 Hz 8.4 dBmV 41.1 dB 0 0
25 Locked QAM256 549000000 Hz 8.4 dBmV 39.6 dB 0 0
26 Locked QAM256 555000000 Hz 8.2 dBmV 39.2 dB 2 0
27 Locked QAM256 561000000 Hz 7.7 dBmV 41.0 dB 0 0
28 Locked QAM256 567000000 Hz 7.4 dBmV 41.1 dB 1 0
29 Locked QAM256 573000000 Hz 6.7 dBmV 40.8 dB 0 0
30 Locked QAM256 579000000 Hz 6.1 dBmV 40.8 dB 2 0
31 Locked QAM256 585000000 Hz 5.9 dBmV 40.6 dB 2 0
32 Locked Other 690000000 Hz 2.8 dBmV 37.0 dB 3269032511 385466
33 Not Locked QAM256 0 Hz 0.0 dBmV 40.7 dB 3 0
34 Locked QAM256 591000000 Hz 6.1 dBmV 40.6 dB 2 0
35 Locked QAM256 597000000 Hz 5.7 dBmV 40.5 dB 1 0
36 Locked QAM256 603000000 Hz 5.6 dBmV 40.2 dB 0 0
37 Locked QAM256 609000000 Hz 5.1 dBmV 39.8 dB 3 0
38 Locked QAM256 615000000 Hz 3.8 dBmV 39.3 dB 25 0
39 Locked QAM256 621000000 Hz 2.8 dBmV 39.1 dB 33 118
40 Locked QAM256 627000000 Hz 2.3 dBmV 39.4 dB 51 215
41 Locked QAM256 633000000 Hz 2.9 dBmV 39.9 dB 48 144
42 Locked QAM256 639000000 Hz 3.9 dBmV 40.2 dB 1 0
43 Locked QAM256 645000000 Hz 4.5 dBmV 40.0 dB 1 0
44 Locked QAM256 651000000 Hz 4.1 dBmV 39.8 dB 0 0
45 Locked QAM256 657000000 Hz 3.5 dBmV 39.9 dB 4 0

Upstream Bonded Channels

Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 2 Locked SC-QAM Upstream 16300000 Hz 6400000 Hz 34.0 dBmV
2 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 34.0 dBmV
3 4 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 35.0 dBmV
4 9 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 35.0 dBmV
5 10 Locked SC-QAM Upstream 40400000 Hz 3200000 Hz 36.0 dBmV

and then I look at the logs....All MAC's replaced with aa:aa:aa:aa:aa:aa

Date Time Event ID Event Level Description
7/29/2023 21:53 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 21:52 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 21:37 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 21:37 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 21:09 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:30 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:29 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:29 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:18 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:18 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:15 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 20:14 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:28 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:28 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:12 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:12 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:11 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:11 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:10 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:07 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:07 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 19:00 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 18:59 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:19 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:19 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:18 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:17 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:17 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:16 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:16 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:12 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:11 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:11 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:01 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 17:00 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 16:29 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
1/1/1970 0:00 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
1/1/1970 0:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
1/1/1970 0:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
7/29/2023 16:28 2436694044 3 "Resetting the cable modem due to docsDevResetNow"
7/28/2023 14:40 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
7/28/2023 14:39 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
7/28/2023 14:36 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/28/2023 14:36 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/28/2023 14:36 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/28/2023 14:36 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=aa:aa:aa:aa:aa;CMTS-MAC=aa:aa:aa:aa:aa;CM-QOS=1.1;CM-VER=3.1;"
7/28/2023 14:36


Just to make sure I'm covering all the bases here....

Configuration shows:

Downstream Frequency (Hz)
Upstream Channel ID
Downstream Frequency Plan

And information shows:

Information
Standard Specification Compliant Docsis 3.1
Hardware Version 6
Software Version AB01.02.053.05_051921_193.0A.NSH
Cable Modem MAC Address aa:aa:aa:aa:aa:aa
Serial Number 23..my..private..number

Status
Up Time 0 days 06h:56m:13s.00

That up time is since the last time it glitched out.

Biggest things I'm noticing in this limited information (I think log is clearing or something because I expected more than that and no clue why some things show 1970) is the number of "uncorrectables" and channel 32 and 33 for the downstream look weird. According to Arris, the Upstream is supposed to be 45 to 51 dBmV for 3+ channels and mine are all <36, but the screenshot in Arris doesn't match the text, so maybe it's wrong.

Sorry for the crazy long post, but if you stayed this long, hopefully you have some insight and can assist!

Official Employee

 • 

2K Messages

2 years ago

Welcome to our community forum, @mrnelson03! I work from home so I know how stressful internet issues can be. We'll definitely stick with you here until we get to the bottom of this and you can enjoy your reliable connection. I checked your modem logs and everything looks great for the last 2 days. Since you're still noticing issues after multiple appointments with our technicians, I'd like to investigate the account in more detail.

Please send a direct message by clicking the chat icon in the upper right corner of the page, click on the pen and paper icon, then enter “Xfinity Support” in the “To” section. Please include your name and address and I'll be happy to help :).

Problem Solver

 • 

1.5K Messages

2 years ago

1/1/1970 -- that's a time not established and a default time stamp when it's got nothing else.

Signal power is all over the map and is NOT OK.  They need to come back and take a look at it again.

(edited)

6 Messages

2 years ago

I started the chat as @XfinityEmilyB instructed and am awaiting a response. I don't know what logs show everything good for the last 2 days though. We lost internet twice last night in one movie. 

Can someone explain Channel ID 32 and 33 to me? I just looked at it and channel 32 is up to 3.38 million uncorrectables.

Problem Solver

 • 

1.5K Messages

2 years ago

ID 32 listed as "Other".  OFDM channel.  A phase lock loop channel of sorts to track signal.  Correctable errors are part of the protocol and cost you nothing.  Expect a lot of correctable errors on that as it fixes "jitter" or signal drift.  Uncorrectable errors on that are not good.

ID 33 just isn't locked at all.  So that one is error'd out at that particular time and is going down the error path of trying to reconnect.

6 Messages

2 years ago

ok, so both are definite problems. I have connected directly to the modem and had to reset the modem in order to get a valid IP and now ID 33 isn't even showing and all the uncorrectables are cleared. The log seems to have retained some messages but cleared a lot of them. I'm guessing it only retains the most important messages. The downstream channels are all mostly between 5.5 and 10.1 dBmV with SNRs being around 40-43dB. The upstreams all have a Power of 34-36 dBmV.

6 Messages

2 years ago

So direct connection to the modem and a reboot. Everything looked good remotely, so they are sending another tech out. I am really curious about this channel 32 "Other" which in 20 minutes since the reboot has over 12,000 uncorrectables. That's not normal, right?

6 Messages

2 years ago

One last interesting tidbit. When I reconnected my router and went to look at the modem again, the channels above 32 came back, to include that weird channel 33 that wasn't locked in my original post. Directly connected to the modem I get channels 1-32. Connected to the modem through the router, I get channels 17-45. 

Problem Solver

 • 

1.5K Messages

2 years ago

The channel numbers are going to change with every reboot and sometimes just on their own anyway, but yeah, the uncorrectables are not good.  Also that big delta on signal power is pretty wonky and indicates a reflection in transmission line theory, and you are running out of spec anyway.  In your case, it's even stranger just because you usually see a pretty clear, predictable frequency dependency either increasing or decreasing as the frequency increases or decreases, but there's some strange poles in that shape.  Bad filters?  Malfunctioning amp somewhere?  Dunno.

None of this is helping you.  There's some guidance on what you should be seeing for signals here:  https://forums.xfinity.com/conversations/your-home-network/internet-troubleshooting-tips/602dae4ac5375f08cde52ea0 

I don't know what your gear would hold for logs on a warm boot.  None of the signal information on most gateways, and probably not much for logging on a warm boot.  Likely nothing on a hard power cycle.  

6 Messages

@flatlander3​ What did you mean by the big delta on signal power? The downstreams look like they are in range according to the link you provided. 2 of the upstream channels are out of range and the others are on the fringe, so I could see those pulsing out of range from time to time. Tech coming back out Friday. Hopefully this next one doesn't try to gaslight me again with the "Your WAN score is 98.5" nonsense.

Problem Solver

 • 

1.5K Messages

@mrnelson03​   From 2.3 dBmV to 9.5dBmv in your original post?

That's a reflection.  Some call it "tilt".  You want that to be within a dBmV or so.  Weird things happen with silicon when you slam the front end transceivers with mismatched inputs. 

You are also looking at a particular instance in time, and that may change over time quite a bit.  Judging by your error logs, dropping a channel, and uncorrectables, it does.  Also not too sure about that -10dBmV to +10dBmV for a modem these days.  It's all the same cost reduced consumer DOCSIS 3.1 parts, so that might not be so accurate now.  I'd derate that to -7dBmV to +7dBmV, but you really want more wiggle room than riding the edges.     

forum icon

New to the Community?

Start Here