Skip to main content

    Support

    Offers

billk55's profile
billk55
1st Topic
1st Like

Visitor

 • 

6 Messages

Wednesday, January 17th, 2024 11:32 PM

Closed

Intermittent internet loss - high number of correctables on one channel

I'm getting lousy internet connectivity intermittently, typically in the morning. When I'm connected, speeds are very high and I'm very happy. But this loss of internet (for a few minutes, over and over again) is not good. While I am a computer guy, I'm not a hardware guy, but I started looking at the modem stats. I'm on a Netgear CM1150V.

First thing that concerned me was that channel 32 is ringing up tons of errors (currently 1173532 Correctable and 49694 Uncorrectable, with a 14 minute uptime).  No errors on any other channel. 

The logs are spitting out "UCD invalid or channel unusable" messages, mixed in with "Started Unicast Maintenance Ranging - No Response received "

Does anyone have any bright ideas about what's going on?

Many thanks

Question

 • 

Updated 

1 year ago

299

4

0

BruceW

Gold Problem Solver

 • 

26.4K Messages

1 year ago

... Netgear CM1150V ... 1173532 Correctable and 49694 Uncorrectable, with a 14 minute uptime ...

Ouch!

Problems like this are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power. 

If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you still need help, please post your Internet plan speed and the following information from your modem (from http://192.168.100.1):

  • downstream: power levels, SNR (or MER), and error counts for all channels
  • upstream: power levels for all channels
  • complete event log, if available (Be sure to remove or blot out any MAC addresses. Forum security processing considers them "personal information" and may prevent the event log from posting if these are present.)

Copy and pasted text is preferred over images. Be aware that, if you post any images, your message will be made Private for a time, as all images must be approved by the Forum Moderators before the messages containing them become generally visible.

If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit (approx $100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

(edited)

1

0

EG

Expert

 • 

110.4K Messages

1 year ago

@billk55 

Please redact the CM MAC and the CMTS MAC addresses from some of your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

3

0

billk55

Visitor

 • 

6 Messages

@EG​ Thought I'd gotten all of them - two stray MACs made it through.

Thanks for your reply. Struggling a bit with the formatting, but here goes. The basic setup hasn't been touched for years. The modem is about 2 feet from the  service entrance, there is one splitter for video (all Comcast installed). 


Again, any help is greatly appreciated!



Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 435000000 Hz 8.9 dBmV 45.4 dB 28 0
2 Locked QAM256 1 417000000 Hz 9.2 dBmV 45.8 dB 35 87
3 Locked QAM256 2 423000000 Hz 8.9 dBmV 45.6 dB 46 53
4 Locked QAM256 3 429000000 Hz 8.7 dBmV 45.4 dB 1 0
5 Locked QAM256 5 441000000 Hz 9.2 dBmV 45.5 dB 25 0
6 Locked QAM256 6 447000000 Hz 9.5 dBmV 45.8 dB 0 0
7 Locked QAM256 7 453000000 Hz 9.6 dBmV 45.1 dB 0 0
8 Locked QAM256 8 459000000 Hz 9.7 dBmV 45.8 dB 0 0
9 Locked QAM256 9 465000000 Hz 9.7 dBmV 43 dB 0 0
10 Locked QAM256 10 471000000 Hz 9.4 dBmV 45.7 dB 8 27
11 Locked QAM256 11 477000000 Hz 9.4 dBmV 45.7 dB 0 0
12 Locked QAM256 12 483000000 Hz 9.4 dBmV 33.7 dB 1 0
13 Locked QAM256 13 489000000 Hz 9.3 dBmV 34.4 dB 21 0
14 Locked QAM256 14 495000000 Hz 9.6 dBmV 45.5 dB 0 0
15 Locked QAM256 15 501000000 Hz 10.2 dBmV 46 dB 0 0
16 Locked QAM256 16 507000000 Hz 10.4 dBmV 46.1 dB 0 0
17 Locked QAM256 17 513000000 Hz 10.2 dBmV 46 dB 0 0
18 Locked QAM256 18 519000000 Hz 10.2 dBmV 44.8 dB 0 0
19 Locked QAM256 19 525000000 Hz 9.8 dBmV 35.3 dB 0 0
20 Locked QAM256 20 531000000 Hz 9.7 dBmV 38 dB 0 0
21 Locked QAM256 21 537000000 Hz 9.3 dBmV 37.9 dB 0 0
22 Locked QAM256 22 543000000 Hz 9.4 dBmV 40.5 dB 0 0
23 Locked QAM256 23 549000000 Hz 9.3 dBmV 45.6 dB 0 0
24 Locked QAM256 24 555000000 Hz 9.8 dBmV 44.5 dB 0 0
25 Locked QAM256 25 561000000 Hz 10.3 dBmV 45.8 dB 0 0
26 Locked QAM256 26 567000000 Hz 10.3 dBmV 37.5 dB 0 0
27 Locked QAM256 27 573000000 Hz 10 dBmV 36.1 dB 0 0
28 Locked QAM256 28 579000000 Hz 10 dBmV 42.4 dB 0 0
29 Locked QAM256 29 585000000 Hz 9.5 dBmV 41.1 dB 0 0
30 Locked QAM256 30 591000000 Hz 8.8 dBmV 41.7 dB 0 0
31 Locked QAM256 31 597000000 Hz 8.5 dBmV 43.4 dB 0 0
32 Locked QAM256 32 603000000 Hz 8.7 dBmV 29.4 dB 23396731 3573440
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 49.5 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 47.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 49.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 53.3 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
And the event log, scrubbed:
Time Priority Description
Thu Jan 18 15:03:32 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:14:49 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:14:44 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:14:19 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:14:13 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out 
Thu Jan 18 10:13:49 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:49 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;C 
Thu Jan 18 10:13:41 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:32 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:23 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:13:22 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:01 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:55 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:32 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:12:27 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:25 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:12:25 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:18 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:12:13 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:02 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:11:43 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:34 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:11:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:19 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:11:08 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:11:02 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:01 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:01 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:10:52 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Thu Jan 18 10:10:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:09:10 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"]; 
Thu Jan 18 10:08:56 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:51 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:25 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:08:24 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:19 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:19 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:07:34 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:06:10 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; 

(edited)

1 year ago

0

billk55

Visitor

 • 

6 Messages

Thanks for your reply. Struggling a bit with the formatting, but here goes. The basic setup hasn't been touched for years. The modem is about 2 feet from the  service entrance, there is one splitter for video (all Comcast installed). 

Trying again - I missed one last MAC on my last post. 

Again, any help is greatly appreciated!



Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 435000000 Hz 8.9 dBmV 45.4 dB 28 0
2 Locked QAM256 1 417000000 Hz 9.2 dBmV 45.8 dB 35 87
3 Locked QAM256 2 423000000 Hz 8.9 dBmV 45.6 dB 46 53
4 Locked QAM256 3 429000000 Hz 8.7 dBmV 45.4 dB 1 0
5 Locked QAM256 5 441000000 Hz 9.2 dBmV 45.5 dB 25 0
6 Locked QAM256 6 447000000 Hz 9.5 dBmV 45.8 dB 0 0
7 Locked QAM256 7 453000000 Hz 9.6 dBmV 45.1 dB 0 0
8 Locked QAM256 8 459000000 Hz 9.7 dBmV 45.8 dB 0 0
9 Locked QAM256 9 465000000 Hz 9.7 dBmV 43 dB 0 0
10 Locked QAM256 10 471000000 Hz 9.4 dBmV 45.7 dB 8 27
11 Locked QAM256 11 477000000 Hz 9.4 dBmV 45.7 dB 0 0
12 Locked QAM256 12 483000000 Hz 9.4 dBmV 33.7 dB 1 0
13 Locked QAM256 13 489000000 Hz 9.3 dBmV 34.4 dB 21 0
14 Locked QAM256 14 495000000 Hz 9.6 dBmV 45.5 dB 0 0
15 Locked QAM256 15 501000000 Hz 10.2 dBmV 46 dB 0 0
16 Locked QAM256 16 507000000 Hz 10.4 dBmV 46.1 dB 0 0
17 Locked QAM256 17 513000000 Hz 10.2 dBmV 46 dB 0 0
18 Locked QAM256 18 519000000 Hz 10.2 dBmV 44.8 dB 0 0
19 Locked QAM256 19 525000000 Hz 9.8 dBmV 35.3 dB 0 0
20 Locked QAM256 20 531000000 Hz 9.7 dBmV 38 dB 0 0
21 Locked QAM256 21 537000000 Hz 9.3 dBmV 37.9 dB 0 0
22 Locked QAM256 22 543000000 Hz 9.4 dBmV 40.5 dB 0 0
23 Locked QAM256 23 549000000 Hz 9.3 dBmV 45.6 dB 0 0
24 Locked QAM256 24 555000000 Hz 9.8 dBmV 44.5 dB 0 0
25 Locked QAM256 25 561000000 Hz 10.3 dBmV 45.8 dB 0 0
26 Locked QAM256 26 567000000 Hz 10.3 dBmV 37.5 dB 0 0
27 Locked QAM256 27 573000000 Hz 10 dBmV 36.1 dB 0 0
28 Locked QAM256 28 579000000 Hz 10 dBmV 42.4 dB 0 0
29 Locked QAM256 29 585000000 Hz 9.5 dBmV 41.1 dB 0 0
30 Locked QAM256 30 591000000 Hz 8.8 dBmV 41.7 dB 0 0
31 Locked QAM256 31 597000000 Hz 8.5 dBmV 43.4 dB 0 0
32 Locked QAM256 32 603000000 Hz 8.7 dBmV 29.4 dB 23396731 3573440
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 49.5 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 47.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 49.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 53.3 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
And the event log, scrubbed:
Time Priority Description
Thu Jan 18 15:03:32 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:14:49 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:14:44 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:14:19 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:14:13 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out 
Thu Jan 18 10:13:49 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:49 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A; OFDM/OFDMA Profile ID: N/A.;C 
Thu Jan 18 10:13:41 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:32 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:23 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:13:22 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:13:01 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:55 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:32 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:12:27 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:25 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:12:25 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:18 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:12:13 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:12:02 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:11:43 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:34 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:11:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:19 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:11:08 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:11:02 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:01 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:11:01 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:10:52 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Thu Jan 18 10:10:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:09:10 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:08:56 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 32 193; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:51 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:25 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:08:24 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A;   OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:19 2024 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 
Thu Jan 18 10:08:19 2024 Warning (5) MDD message timeout; 
Thu Jan 18 10:07:34 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
Thu Jan 18 10:06:10 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A;  OFDM/OFDMA Profile ID: N/A.; 

1 year ago

0

EG

Expert

 • 

110.4K Messages

@billk55​ 

There is still a MAC address left in line 32 of the first output.

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer!tick

1 year ago

0

BruceW

Gold Problem Solver

 • 

26.4K Messages

1 year ago

Downstream, power levels are a bit too high, and several SNR values are borderline to out of spec (too low). Upstream power levels are borderline to out of spec (too high). Suggest you have a Comcast premise tech out to investigate and correct.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

1

0

billk55

Visitor

 • 

6 Messages

@BruceW​ Thanks, I was just hoping it would be more obvious what the underlying issue is. However - on to Comcast!

1 year ago

0

XfinityThomasA

Official Employee

 • 

2.4K Messages

1 year ago

Our Digital Care Team can help, @billk55! And, thank you @BruceW, and @EG for your contributions. @billk55 - can you please send a direct chat message with your full name and complete service address to “Xfinity Support”? To do so, click on the chat icon located at the top right of this forum's page.
 
Here are the detailed steps to direct message us:
• Click "Sign In" if necessary
• Click the "Direct Message” icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message

3

0

billk55

Visitor

 • 

6 Messages

@XfinityThomasA​  Thanks - just saw this message, I was out. I actually had a call around 6:30am today from Comcast, who said that a technician was able to address the problem remotely. That, strangely enough, was the time of day when most outages occurred. I had scheduled an on-site visit on Monday, but at Comcast's suggestion, I canceled it.

Thanks to both @BruceW and @EG for their help. As a retired tech guy, it has been very interesting to learn a bit more about this side of the house.


1 year ago

XfinityEva

Official Employee

 • 

1.7K Messages

@billk55 Thanks for the update. We will want to keep an eye on this since it has been intermittent and the suggestions above that this could benefit from having a tech check the location. Please let us know if you continue to see these concerns and we can get that appointment scheduled again for you. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

1 year ago

0

XfinityBenjaminM

Official Employee

 • 

2K Messages

@billk55 Hello! We just wanted to check in and see if the intermittent connection issues you were experiencing have remained resolved. If you are still having any trouble, please let us know.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

1 year ago

0

forum icon

New to the Community?

Start Here