Community Forum
Top

Random Network Disconnects with only a single upstream connection on Netgear CM500

Mitoh
Frequent Visitor
‎06-15-2020 11:04 PM

Random Network Disconnects with only a single upstream connection on Netgear CM500

For the past week or so I have been having issues with the stability of my network connection.

 

My upload speed is slower than it was previously and I have had several game connections drop in the middle of playing due to the spotty network connection. When this first started happening, I noticed that only a single upstream channel was connected as well.

 

I have already attempted to troubleshoot a bit myself with 3 different reboot attempts including 1 factory reset. The modem is connected to the drop via a single high quality -5 db splitter. The donwstream connection was running at borderline high levels between a low of 9.5 dBmV and 11 dBmV. I installed an attenuator to the line at the modem to drop this to the current levels shown.

 

Procedure Status Comment
Acquire Downstream Channel 627000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 32 627000000 Hz 2.2 dBmV 38.7 dB 5 0
2 Locked QAM256 33 633000000 Hz 2.1 dBmV 38.6 dB 0 0
3 Locked QAM256 34 639000000 Hz 1.9 dBmV 38.4 dB 5 0
4 Locked QAM256 35 645000000 Hz 2.2 dBmV 38.6 dB 3 0
5 Locked QAM256 36 651000000 Hz 2.1 dBmV 38.4 dB 2 0
6 Locked QAM256 37 657000000 Hz 2.2 dBmV 38.4 dB 4 0
7 Locked QAM256 38 663000000 Hz 2.8 dBmV 38.6 dB 1 0
8 Locked QAM256 39 669000000 Hz 2.5 dBmV 38.5 dB 1 0
9 Locked QAM256 40 675000000 Hz 2.3 dBmV 37.9 dB 3 0
10 Locked QAM256 41 681000000 Hz 2.2 dBmV 38.3 dB 2 0
11 Locked QAM256 42 687000000 Hz 2.2 dBmV 38.2 dB 5 0
12 Locked QAM256 43 693000000 Hz 2.3 dBmV 38.4 dB 1 0
13 Locked QAM256 44 699000000 Hz 2.7 dBmV 38.5 dB 2 0
14 Locked QAM256 45 705000000 Hz 2.7 dBmV 38.4 dB 2 0
15 Locked QAM256 46 711000000 Hz 2.8 dBmV 38.4 dB 1 0
16 Locked QAM256 47 717000000 Hz 2.8 dBmV 38.3 dB 0 0
 
Upstream Bonded Channels (Partial Service)
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 21 5120 Ksym/sec 36500000 Hz 48.5 dBmV
2 Not Locked Unknown 22 0 Ksym/sec 30100000 Hz 0.0 dBmV
3 Not Locked Unknown 23 0 Ksym/sec 23700000 Hz 0.0 dBmV
4 Not Locked Unknown 24 0 Ksym/sec 17300000 Hz 0.0 dBmV

 

Time Priority Description
2020-6-15, 19:47:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:50 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:28 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:07 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:47:06 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:44 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:23 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:22 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:22 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-15, 19:46:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
0 Likes
Reply
Mitoh
Frequent Visitor
‎06-22-2020 10:09 PM

Re: Random Network Disconnects with only a single upstream connection on Netgear CM500

It has been a week and I continue to have issues with my service. T3 timeouts are still frequently occuring and I am only locked on a single uplink channel.

 

Time Priority Description
2020-6-22, 19:08:12 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:12 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:10 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:10 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:10 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:08:10 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:50 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:50 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:48 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:48 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:48 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:48 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:48 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:48 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:28 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:28 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:26 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:26 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:26 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:26 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:26 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:26 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:07 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:05 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:05 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:03 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:03 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:03 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:07:03 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:06:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:06:43 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:06:43 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:06:41 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;
2020-6-22, 19:06:41 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:d2:94:64:8c:c8;CMTS-MAC=00:01:5c:63:c4:63;CM-QOS=1.1;CM-VER=3.0;

 

Procedure Status Comment
Acquire Downstream Channel 627000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 32 627000000 Hz 2.1 dBmV 38.5 dB 2824 9386
2 Locked QAM256 33 633000000 Hz 2.4 dBmV 38.6 dB 5361 24912
3 Locked QAM256 34 639000000 Hz 1.9 dBmV 38.2 dB 2882 8908
4 Locked QAM256 35 645000000 Hz 2.2 dBmV 38.5 dB 3658 10452
5 Locked QAM256 36 651000000 Hz 2.1 dBmV 38.2 dB 3654 9987
6 Locked QAM256 37 657000000 Hz 2.6 dBmV 38.4 dB 3411 10464
7 Locked QAM256 38 663000000 Hz 3 dBmV 38.4 dB 2885 9000
8 Locked QAM256 39 669000000 Hz 2.6 dBmV 38.3 dB 2890 8997
9 Locked QAM256 40 675000000 Hz 2.6 dBmV 37.9 dB 3682 10907
10 Locked QAM256 41 681000000 Hz 2.6 dBmV 38.1 dB 3591 10132
11 Locked QAM256 42 687000000 Hz 2.3 dBmV 38 dB 3022 9107
12 Locked QAM256 43 693000000 Hz 2.5 dBmV 38.2 dB 3737 10226
13 Locked QAM256 44 699000000 Hz 3.2 dBmV 38.4 dB 3445 10684
14 Locked QAM256 45 705000000 Hz 3.1 dBmV 38.3 dB 3697 10894
15 Locked QAM256 46 711000000 Hz 2.9 dBmV 38.2 dB 3148 8926
16 Locked QAM256 47 717000000 Hz 3.1 dBmV 38.2 dB 3631 10441
 
Upstream Bonded Channels (Partial Service)
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 21 5120 Ksym/sec 36500000 Hz 43 dBmV
2 Not Locked Unknown 22 0 Ksym/sec 30100000 Hz 0.0 dBmV
3 Not Locked Unknown 23 0 Ksym/sec 23700000 Hz 0.0 dBmV
4 Not Locked Unknown 24 0 Ksym/sec 17300000 Hz 0.0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
0 Likes
Reply
EG
Expert
‎06-23-2020 12:44 AM

Re: Random Network Disconnects with only a single upstream connection on Netgear CM500

The upstream power is on the high side in your first post and obviously it is intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous 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.



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? Mark the post as Best Answer!
0 Likes
Reply
Mitoh
Frequent Visitor
‎06-25-2020 01:19 AM

Re: Random Network Disconnects with only a single upstream connection on Netgear CM500

The initial attenuator I had acquired was an unbiased attenuator that caused an increase in the upstream signal as well as the desired decrease in downstream signal. I have now installed a forward path attenuator that is only attenuating the downstream signal as desired which lead to the lower levels in the update I posted.

As I stated in my first post, the connection is through a single high quality splitter.

0 Likes
Reply
EG
Expert
‎06-25-2020 12:41 PM

Re: Random Network Disconnects with only a single upstream connection on Netgear CM500

I would get a tech out to investigate. A high pass noise filter may have been placed on your line at the tap. That may be why your modem is only able to lock on to one upstream channel. Good luck !



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? Mark the post as Best Answer!
0 Likes
Reply
Visit Our Help Communities