Multiple Drops per Day

[RARamaker]

My internet drops multiple times per day either for a 30+ seconds or in a need to reset the modem.  I have MB7420 that is subscriber owned.  Here is the signal and logs.

Connection

Startup Sequence

Startup Step Status Comment       Acquire Downstream Channel 525000000 Hz Locked       Upstream Connection OK Operational       Boot State OK Operational       Configuration File OK         Security Enabled BPI+

Connection Status

System Up Time 0 days 02h:27m:43s         Network Access Allowed

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected 1 Locked QAM256 13 525.0 3.0 38.8 754 923 2 Locked QAM256 1 447.0 3.6 38.8 765 855 3 Locked QAM256 2 453.0 3.7 38.8 790 862 4 Locked QAM256 3 459.0 3.8 38.8 767 878 5 Locked QAM256 4 465.0 4.0 39.0 720 930 6 Locked QAM256 5 471.0 4.2 39.2 703 901 7 Locked QAM256 6 477.0 3.8 38.9 728 953 8 Locked QAM256 7 483.0 3.3 38.7 813 1143 9 Locked QAM256 8 489.0 3.5 38.8 714 787 10 Locked QAM256 9 495.0 4.2 39.1 707 923 11 Locked QAM256 10 507.0 2.9 36.4 733 811 12 Locked QAM256 11 513.0 2.8 38.6 763 733 13 Locked QAM256 12 519.0 3.0 38.6 732 787 14 Locked QAM256 14 531.0 3.1 38.8 677 819 15 Locked QAM256 15 537.0 3.3 38.9 652 764 16 Locked QAM256 16 543.0 2.9 38.6 681 762 Total             11699 13831

Upstream Bonded Channels

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV) 1 Locked ATDMA 1 5120 35.8 45.0 2 Not Locked Unknown 0 0 0 0.0 3 Not Locked Unknown 0 0 0 0.0 4 Not Locked Unknown 0 0 0 0.0

Log

Time   Priority   Description  Wed May 20 13:37:45 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Wed May 20 13:38:17 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Wed May 20 13:38:25 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Wed May 20 13:38:57 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Wed May 20 13:39:25 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Wed May 20 13:39:57 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Wed May 20 13:40:04 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Time Not Established  Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.0;CM-VER=3.0;  Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.0;CM-VER=3.0;  Thu May 21 08:00:12 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:00:49 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:01:15 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:01:52 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:02:19 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:02:56 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:03:20 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:03:57 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:04:24 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 08:05:01 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 11:56:03 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 12:24:56 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 14:39:13 2020   Critical (3)  Resetting the cable modem due to docsDevResetNow  Thu May 21 14:52:12 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 14:54:45 2020   Critical (3)  Resetting the cable modem due to docsDevResetNow  Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.0;CM-VER=3.0;  Time Not Established  Notice (6)  Honoring MDD; IP provisioning mode = IPv6  Thu May 21 15:29:54 2020   Critical (3)  REG RSP not received;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 15:29:56 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 15:30:32 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.1;CM-VER=3.0;  Thu May 21 15:30:57 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.0;CM-VER=3.0;  Thu May 21 15:31:01 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:46:f8:58;CMTS-MAC=00:5f:86:92:86:b3;CM-QOS=1.0;CM-VER=3.0;  Thu May 21 15:31:12 2020   Notice (6)  Honoring MDD; IP provisioning mode = IPv6

[CCAndrew]

You’ll want to investigate why you only have 1 upstream channel. Could be equipment, could be house wiring, could be maintenance put a high pass filter on your drop for noise. You should have 3 possibly 4 upstream channels (depending on market).

[RARamaker]

Thanks for the info.  It explains my very slow upload speed.  Could this explain the drops as well?  I've heard that overloading the upload channel will stop downloads.

[CCAndrew]

It could if there’s ingress/noise present

[RARamaker]

I just checked the modem again and now it shows 4 channels.  Is that normal to take a day to get 4 channels?

Upstream Bonded Channels

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV) 1 Locked ATDMA 2 5120 29.4 44.0 2 Locked ATDMA 1 5120 35.8 44.0 3 Locked ATDMA 3 5120 23.0 44.0 4 Locked ATDMA 4 5120 16.6 42.5

[CCAndrew]

The channels were always there , it’s a matter of your modem being able to read them. Just something to watch in the future

[EG]

FWIW, intermittent noise ingress into the line / connection quality impairments can cause the channels to unlock and return.