Welcome to Comcast Help & Support Forums
Find solutions, share knowledge, and get answers from customers and experts

New to the Community? Start here.

5,683,930

members

44

online now

1,852,240

discussions

Back to Top

Only one bonded upstream channel?

Posted by
New Poster
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!

Message 1 of 4
154 Views

My line outside also has no grounded wire. I also get many disconnects. 

 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 537000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 5 537000000 Hz 0.9 dBmV 40.4 dB 438 589
2 Locked QAM256 25 657000000 Hz 1.3 dBmV 39.8 dB 298 416
3 Locked QAM256 6 543000000 Hz 1.3 dBmV 40.2 dB 430 520
4 Locked QAM256 7 549000000 Hz 1.4 dBmV 40.4 dB 456 801
5 Locked QAM256 8 555000000 Hz 1.4 dBmV 40.4 dB 352 613
6 Locked QAM256 9 561000000 Hz 1.2 dBmV 40.3 dB 412 683
7 Locked QAM256 10 567000000 Hz 1.3 dBmV 40.3 dB 446 517
8 Locked QAM256 11 573000000 Hz 1.5 dBmV 40.3 dB 450 670
9 Locked QAM256 12 579000000 Hz 1.5 dBmV 40.4 dB 380 435
10 Locked QAM256 13 585000000 Hz 1.3 dBmV 40.2 dB 451 560
11 Locked QAM256 14 591000000 Hz 1.0 dBmV 40.2 dB 400 452
12 Locked QAM256 15 597000000 Hz 1.1 dBmV 40.2 dB 445 558
13 Locked QAM256 16 603000000 Hz 1.4 dBmV 40.3 dB 462 430
14 Locked QAM256 17 609000000 Hz 1.4 dBmV 40.2 dB 366 601
15 Locked QAM256 18 615000000 Hz 1.3 dBmV 40.1 dB 333 487
16 Locked QAM256 19 621000000 Hz 1.3 dBmV 40.1 dB 351 505
17 Locked QAM256 20 627000000 Hz 1.5 dBmV 40.8 dB 0 0
18 Locked QAM256 21 633000000 Hz 1.5 dBmV 40.8 dB 0 0
19 Locked QAM256 22 639000000 Hz 1.1 dBmV 40.2 dB 0 0
20 Locked QAM256 23 645000000 Hz 1.0 dBmV 39.9 dB 0 0
21 Locked QAM256 24 651000000 Hz 1.2 dBmV 40.2 dB 0 0
22 Locked QAM256 26 663000000 Hz 1.2 dBmV 40.0 dB 0 0
23 Locked QAM256 27 669000000 Hz 0.8 dBmV 39.9 dB 0 0
24 Locked QAM256 28 675000000 Hz 0.8 dBmV 39.4 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 36100000 Hz 45.0 dBmV
2 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
3 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 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

 

My event log.

 

Time Priority Description
2017-08-12, 21:46:10 Warning (5) Dynamic Range Window violation
2017-08-12, 21:46:07 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 21:19:05 Warning (5) Dynamic Range Window violation
2017-08-12, 19:58:42 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 19:36:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 19:36:31 Warning (5) Dynamic Range Window violation
2017-08-12, 15:55:36 Warning (5) Dynamic Range Window violation
2017-08-12, 15:55:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 14:08:58 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2017-08-12, 14:08:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:08:45 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:08:35 Warning (5) Lost MDD Timeout;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:08:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:08:26 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:07:53 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:07:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:07:29 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:07:19 Warning (5) Lost MDD Timeout;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:07:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:07:09 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:06:59 Warning (5) Lost MDD Timeout;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:06:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 14:06:48 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 14:06:13 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2017-08-12, 14:05:59 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 14:05:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 14:05:26 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2017-08-12, 14:05:12 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 14:05:09 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 14:04:33 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2017-08-12, 14:04:18 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 13:01:53 Warning (5) Unicast DSID PSN startup error
2017-08-12, 12:59:35 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.1;CM-VER=3.0;
2017-08-12, 12:58:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 12:58:51 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 12:58:33 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 12:58:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:56:2b:77:12:43;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 12:57:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-08-12, 12:57:36 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:62:ff:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
3 REPLIES
Posted by
Connection Expert

Message 2 of 4
139 Views

Have you tried powercycling the modem ?




Community Icon
I am not a Comcast employee, I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help. For information on the program click here.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee. I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee.

Was your question answered?
Mark it as a solution!solution Icon

Posted by
New Poster
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!

Message 3 of 4
127 Views

After doing a reset, it goes to 4 bonded US, a few hours later it goes back to only 1 with orange light. 

Highlighted
Posted by
Connection Expert

Message 4 of 4
122 Views

The stats as read at the modem level at that moment in time were o/k but there are three additional signal stats that can cause problems / cause the unbonding of channels due to an upstream impairment which can't be read by the modem. They can only be read from their end by them polling the CMTS (Cable Modem Termination System) at the local headend facility.

They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.

You can call in and ask what these figures are. The Upstream Receive Power Level should fall within the range of -2dB to +2dB with 0dB being in the middle and perfect.

The Upstream SNR should be least 31dB, and the higher it is the better.

The ICFR should be no higher than 2 dB.

You could have an intermittent noise ingress issue in only the upstream channel(s) / return path only somewhere.

They will be able to see whether or not everything is in the green zone and also see a history plot for the modem.





Community Icon
I am not a Comcast employee, I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help. For information on the program click here.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee. I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee.

Was your question answered?
Mark it as a solution!solution Icon