Menu
Reply
Highlighted
  • 16
  • 0
  • 2
Tuning in
347 Views
Message 1 of 23
Flag for a moderator

Intermittent and irregular 5-10 minute dropouts

Hi, looking for any advice and possibly to to reach an engineer, by-passing the helpdesk.

I have been having intermittent and irregular losses of connection which have been getting more frequent over the last few months. The connection drops, the Shub recognises a problem and does a reset. A few months ago this could happen several times a day but there could be days with no outages. I am running BQM. I was running an old Shub1 in modem mode and, thinking that the finger would point here, took a free upgrade to a Shub3. This made no difference and things have got worse. Yesterday there were 14 outages (some overnight) and 4 so far today, 8 in the last 24 hours. And the Shub3 takes longer to restart!

Here is the live BQM. Unfortunately VM changed my WAN IP last week while I was away, even though the Shub was left on. I created a new BQM on Monday and disabled the old so I can still browse and share days from history if this is of interest.

I have been collecting Shub logs for a while. A set from earlier today are below. They are just cut'n'pasted so I apologise for the lack of good formatting (hints welcome). Typically, at dropouts, they show a flurry of T3 timeouts plus a few T4s. The batch of Sync errors around 10:40 are not typical but might be significant to someone. There wasn't a dropout then. I'm not yet familiar with Shub3 power levels and hope someone will comment. An 8dB Forward Path Equaliser was installed by a VM engineer some years ago and I left it in place when swapping to the Shub3. The Shub hasn't been power cycled for a while but I was surprised by the number of RS errors. I've not seen that many before.

Ideas please...

Network Log
Time Priority Description
21/10/2020 13:55:7 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:54:15 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:53:33 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:49:19 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:49:9 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:49:9 critical Ranging Request Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:48:25 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 13:48:7 Warning! RCS Partial Service;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 11:22:0 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:26 Warning! Lost MDD Timeout;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:20 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:20 Warning! RCS Partial Service;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:20 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:20 Warning! RCS Partial Service;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:6 Warning! Lost MDD Timeout;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:0 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:0 Warning! RCS Partial Service;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:0 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 10:40:0 Warning! RCS Partial Service;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:43:5 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:42:20 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:38:23 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:38:23 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:38:23 critical Ranging Request Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:38:14 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:37:58 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:37:58 critical Ranging Request Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:37:32 critical No Ranging Response received - T3 time-out;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 09:37:31 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=Shub3-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 410250000 1.5 37 256 qam 1
2 418250000 0.9 38 256 qam 2
3 426250000 0.7 38 256 qam 3
4 434250000 0.9 38 256 qam 4
5 442250000 1 38 256 qam 5
6 450250000 1 38 256 qam 6
7 458250000 1 38 256 qam 7
8 466250000 1.2 38 256 qam 8
9 474250000 1 38 256 qam 9
10 482250000 1.2 38 256 qam 10
11 490250000 1 38 256 qam 11
12 498250000 1 38 256 qam 12
13 506250000 1 38 256 qam 13
14 514250000 1 38 256 qam 14
15 522250000 1 38 256 qam 15
16 530250000 1.4 38 256 qam 16
17 538250000 1.5 38 256 qam 17
18 546250000 1.7 38 256 qam 18
19 554250000 1.9 38 256 qam 19
20 562250000 2 38 256 qam 20
21 570250000 2.5 38 256 qam 21
22 578250000 2.7 38 256 qam 22
23 586250000 3 38 256 qam 23
24 594250000 3.2 38 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.6 1155 5879
2 Locked 38.6 1131 4433
3 Locked 38.6 1225 534
4 Locked 38.6 1141 477
5 Locked 38.6 1116 6224
6 Locked 38.6 1083 5217
7 Locked 38.9 1168 426
8 Locked 38.9 1606 5357
9 Locked 38.9 1252 5467
10 Locked 38.6 992 5142
11 Locked 38.6 1052 5644
12 Locked 38.6 962 5699
13 Locked 38.6 1163 5582
14 Locked 38.9 1103 5887
15 Locked 38.6 1086 5494
16 Locked 38.6 1198 5410
17 Locked 38.9 988 5723
18 Locked 38.6 965 1862
19 Locked 38.6 708 9569
20 Locked 38.9 957 6542
21 Locked 38.9 819 6749
22 Locked 38.9 911 6995
23 Locked 38.9 778 6687
24 Locked 38.6 855 6906

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 35.8 5120 64 qam 6
2 46200000 35.8 5120 64 qam 5
3 25800000 34.0 5120 64 qam 8
4 32600000 34.8 5120 64 qam 7


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 1 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 21 0
4 ATDMA 0 0 0 0

General Configuration
Network access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode Docsis30
Config file cmreg-vmdg505-bbt057-b.cm


Primary Downstream Service Flow
SFID 318246
Max Traffic Rate 117000047
Max Traffic Burst 42600
Min Traffic Rate 0


Primary Upstream Service Flow
SFID 318245
Max Traffic Rate 10500047
Max Traffic Burst 16320
Min Traffic Rate 0
Max Concatenated Burst 16320
Scheduling Type BestEffort

Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz) 410250000 Locked
Ranged Upstream Channel (Hz) 39400000 Locked
Provisioning State Online

0 Kudos
Reply
Highlighted
  • 17.2K
  • 1.81K
  • 2.98K
Very Insightful Person
Very Insightful Person
334 Views
Message 2 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Yep BQM and logs not looking great and RS errors a concern. Down power levels ok Up ones on the low side but in spec.

Start from a blank sheet. Switch Hub for 5' and unplug from mains for 5'. Restart and check RS error counts have gone to 0 and monitor them.

Do a quick check that all of your coax cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure.

You could also try a 60 second pinhole reset and see if that helps.

--------------------
John
--------------------

My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
Highlighted
  • 16
  • 0
  • 2
Tuning in
321 Views
Message 3 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Thanks for your comments John. I'm out this evening so I'll run through the 'blank sheet' reset and connection check tomorrow morning and post some more logs later. I'm curious; what does unplugging from the mains do that the switch at the back of the Shub 3 doesn't do?

JohnC

0 Kudos
Reply
Highlighted
  • 17.2K
  • 1.81K
  • 2.98K
Very Insightful Person
Very Insightful Person
299 Views
Message 4 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

It's anecdotal sayings that people have heard VM techs say that whist the Hub is still plugged in - but switched off - there is a trickle charge still going in and that can prevent some activities. Dunno if its true but some have claimed they did a normal restart and the RS errors didnt seem to reset.

You could test that and report back 🙂

--------------------
John
--------------------

My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
Highlighted
  • 16
  • 0
  • 2
Tuning in
266 Views
Message 5 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Hi, I did a single rear switch powercycle around 11am today and I'm now seeing Pre RS errors from 4 to 26 and Post RS error all 0. The relationship between the powercycle and the RS error zero'ing remains a bit of a mystery. Here are some snippets:

Yesterday

1 Locked 37.6 1155 5879
2 Locked 38.6 1131 4433
3 Locked 38.6 1225 534
4 Locked 38.6 1141 477

Today just before power cycle - they were lower

1 Locked 37.6 186 399
2 Locked 37.6 191 321
3 Locked 38.6 189 310
4 Locked 38.6 166 268

Today immediately following power cycle - they were higher!

1 Locked 37.6 650 524
2 Locked 38.6 707 435
3 Locked 38.9 696 441
4 Locked 38.6 638 407

Today 30 minutes after power cycle

1 Locked 37.6 10 176
2 Locked 38.6 1 0
3 Locked 38.6 9 0
4 Locked 38.6 0 0

and another 20 minutes later

1 Locked 38.6 7 0
2 Locked 38.6 0 0
3 Locked 38.6 0 0
4 Locked 38.9 0 0

The hub reset itself multiple times over the hour following the power cycle, as you can see from the BQM. Is there some renegotiation with the network after a power cycle that needs this?

However, don't let me distract you from the main mission. Maybe another time!

I checked the connectors. We don't have TV so it's simple. No chance of unterminated loose ends. Nothing was loose. I was able to give each just a slight tweak. We were connected about 15 years ago to "Superfast 1Mb" and nothing's been changed or rerouted indoors. We're about 200 meters from the nearest green box and that cabling dates from the same time, when our area was first cabled.

Here is a set of logs from 4:15pm

Network Log
Time Priority Description
22/10/2020 15:02:1 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 15:01:11 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 15:00:24 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:56:29 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:56:28 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:56:28 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:56:18 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:56:5 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:56:5 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:55:36 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:55:36 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:55:36 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 14:54:52 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:58:18 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:57:27 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:48:54 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:48:3 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:47:18 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:43:29 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
22/10/2020 12:43:29 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 410250000 4 38 256 qam 1
2 418250000 3.5 38 256 qam 2
3 426250000 3.7 38 256 qam 3
4 434250000 3.7 38 256 qam 4
5 442250000 4 38 256 qam 5
6 450250000 4 38 256 qam 6
7 458250000 4 38 256 qam 7
8 466250000 4 38 256 qam 8
9 474250000 3.7 38 256 qam 9
10 482250000 4 38 256 qam 10
11 490250000 3.7 38 256 qam 11
12 498250000 3.7 38 256 qam 12
13 506250000 3.7 38 256 qam 13
14 514250000 3.5 38 256 qam 14
15 522250000 3.7 38 256 qam 15
16 530250000 3.9 38 256 qam 16
17 538250000 4 38 256 qam 17
18 546250000 4.1 38 256 qam 18
19 554250000 4.3 38 256 qam 19
20 562250000 4.5 38 256 qam 20
21 570250000 4.6 38 256 qam 21
22 578250000 5 38 256 qam 22
23 586250000 5 38 256 qam 23
24 594250000 5.3 38 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 11 0
2 Locked 38.6 4 0
3 Locked 38.6 11 0
4 Locked 38.9 7 0
5 Locked 38.6 7 0
6 Locked 38.6 12 0
7 Locked 38.6 8 0
8 Locked 38.6 10 0
9 Locked 38.9 11 0
10 Locked 38.6 9 0
11 Locked 38.6 10 0
12 Locked 38.6 9 0
13 Locked 38.6 11 0
14 Locked 38.6 5 0
15 Locked 38.6 12 0
16 Locked 38.9 15 0
17 Locked 38.9 11 0
18 Locked 38.6 16 0
19 Locked 38.6 16 0
20 Locked 38.9 26 0
21 Locked 38.9 21 0
22 Locked 38.9 18 0
23 Locked 38.6 25 0
24 Locked 38.9 19 0


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 32 5120 64 qam 6
2 46200000 32.3 5120 64 qam 5
3 25800000 31.3 5120 64 qam 8
4 32600000 31.5 5120 64 qam 7


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

Short outages with T3 and T4 timeouts. Much as I've been seeing for several months. What next? Is it really worth a factory reset? This hub was fresh out of the box 6 weeks ago.

Cheers

JohnC

0 Kudos
Reply
Highlighted
  • 17.2K
  • 1.81K
  • 2.98K
Very Insightful Person
Very Insightful Person
252 Views
Message 6 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Needs VM to take a look I have flagged it for their attention. Check back here.

--------------------
John
--------------------

My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
Highlighted
  • 16
  • 0
  • 2
Tuning in
236 Views
Message 7 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Thank you John.😀

JohnC

0 Kudos
Reply
Highlighted
  • 711
  • 38
  • 58
Forum Team
Forum Team
210 Views
Message 8 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Hi there @JamaisDodger 

 

Thanks for your post. Apologies for the delay in response and to hear that you've been having these issues with your broadband connection. 

 

I've been able to locate your account and I can't see any issues with the hub, connection or signals at the moment. Are you still having issues today? 

 

Let me know and I'll do my best to help 🙂 

 

Thanks, 

 

 

Hollie - Forum Team


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
Highlighted
  • 16
  • 0
  • 2
Tuning in
202 Views
Message 9 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Hi Hollie,

Thanks for picking up my post. I haven't dared to post an update, for fear of hex'ing things, but there was a dramatic improvement overnight between Weds 28th and Thurs 29th. On Weds, for instance, BQM showed 15 short outages which was typical. Since early Thursday until now (three whole days) there has just been one, late Friday 30th morning. I was wondering if the VM wizards had done some long distance magic, very early on Thursday?

The logs below from yesterday tell the story. I don't think I'm able to share the BQM history with you but I'd be happy to send some screen grabs if you want to see the difference. Let me know if you need any other details.

Checking this morning, I see that Pre RS Errors are still increasing rapidly but Post RS Errors haven't changed since yesterday. I haven't yet worked out how/when these numbers reset.

I think it's too early to consider this problem resolved. It's been going on for a long time and there have been previous periods of 'remission'. Of course, if you can confirm that there was some wizardry early Thursday, that would change things. Otherwise, I'd like to keep the thread open for at least another week and I'll report any further incidents.

Thanks

JohnC

Hub 3.0 device information
The information below shows current status of this Hub 3.0.

Standard specification compliant : DOCSIS 3.0
Hardware version : 11
Software version : 9.1.1912.302 <<< no change since 22/10
Cable MAC address : CM-MACaddress
Cable modem serial number : ABAP01903932
System up time : 9 days 11h:4m:59s
Network access : Allowed

Network Log
Time Priority Description
31/10/2020 22:42:7 notice LAN login Success;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:23:20 Warning! RCS Partial Service;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:21:12 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:48 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:31 Warning! RCS Partial Service;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:24 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:24 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:15:40 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:14:11 Warning! RCS Partial Service;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:23:50 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:22:59 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:22:1 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:57 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:56 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:56 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:29 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:28 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:28 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:16:45 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 22:32:50 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 474250000 1.4 38 256 qam 9
2 482250000 1.5 38 256 qam 10
3 490250000 1.5 38 256 qam 11
4 498250000 1.5 38 256 qam 12
5 506250000 1.5 38 256 qam 13
6 514250000 1.7 38 256 qam 14
7 522250000 1.7 38 256 qam 15
8 530250000 2 38 256 qam 16
9 538250000 2.4 38 256 qam 17
10 546250000 2.7 38 256 qam 18
11 554250000 2.9 38 256 qam 19
12 562250000 3 38 256 qam 20
13 570250000 3.5 40 256 qam 21
14 578250000 3.9 38 256 qam 22
15 586250000 4 40 256 qam 23
16 594250000 4.4 38 256 qam 24
17 658250000 3.4 38 256 qam 25
18 666250000 2.9 38 256 qam 26
19 674250000 3 38 256 qam 27
20 682250000 3.5 38 256 qam 28
21 690250000 3.7 38 256 qam 29
22 698250000 4 38 256 qam 30
23 706250000 4 40 256 qam 31
24 714250000 4 38 256 qam 32


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 6678 205
2 Locked 38.9 7717 325
3 Locked 38.6 8501 251
4 Locked 38.9 9144 341
5 Locked 38.6 10404 359
6 Locked 38.9 12708 377
7 Locked 38.9 14992 311
8 Locked 38.9 15911 359
9 Locked 38.9 16731 416
10 Locked 38.9 18944 341
11 Locked 38.9 22340 301
12 Locked 38.9 25018 376
13 Locked 40.3 26191 276
14 Locked 38.9 26831 302
15 Locked 40.3 26625 395
16 Locked 38.9 30306 351
17 Locked 38.9 59415 159
18 Locked 38.9 63837 194
19 Locked 38.9 65469 158
20 Locked 38.9 70756 108
21 Locked 38.9 67823 139
22 Locked 38.9 67696 197
23 Locked 40.3 69672 140
24 Locked 38.9 75188 173

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39399879 38 5120 64 qam 6
2 46200029 38 5120 64 qam 5
3 25800000 36 5120 64 qam 8
4 32600010 36.8 5120 64 qam 7


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

 

0 Kudos
Reply
Highlighted
  • 16
  • 0
  • 2
Tuning in
195 Views
Message 10 of 23
Flag for a moderator

Re: Intermittent and irregular 5-10 minute dropouts

Hah!  I knew posting an update was risky!! About 10 minutes after the last post there was an outage and hub reset. I captured the logs during this time (possibly why only 3 upstream channels showing?). There were actually several outages in quick order; the dotted line in the Network Log is where I pasted in extra lines. BQM shows the outages. What next @Hollie_B ? 🤔

Thanks

JohnC

Network Log
Time Priority Description
01/11/2020 13:25:39 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:25:37 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:25:37 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:25:15 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:25:15 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:24:31 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
---------------------------------------------------------------------------
01/11/2020 13:11:58 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:11:8 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:10:13 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
---------------------------------------------------------------------------
01/11/2020 13:06:0 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:05:38 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:05:38 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
01/11/2020 13:04:54 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
31/10/2020 22:42:7 notice LAN login Success;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:23:20 Warning! RCS Partial Service;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:21:12 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:48 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:31 Warning! RCS Partial Service;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:24 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:16:24 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:15:40 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
30/10/2020 11:14:11 Warning! RCS Partial Service;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:23:50 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:22:59 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:22:1 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:57 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:56 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:56 critical Ranging Request Retries exhausted;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 23:17:29 critical No Ranging Response received - T3 time-out;CM-MAC=CM-MACaddress;CMTS-MAC=CMTS-MACaddress;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 474250000 1.5 38 256 qam 9
2 482250000 1.5 40 256 qam 10
3 490250000 1.7 38 256 qam 11
4 498250000 1.7 40 256 qam 12
5 506250000 1.9 38 256 qam 13
6 514250000 2 38 256 qam 14
7 522250000 2.2 38 256 qam 15
8 530250000 2.7 38 256 qam 16
9 538250000 3 38 256 qam 17
10 546250000 3.2 38 256 qam 18
11 554250000 3.7 38 256 qam 19
12 562250000 3.9 38 256 qam 20
13 570250000 4.3 38 256 qam 21
14 578250000 4.5 38 256 qam 22
15 586250000 4.9 38 256 qam 23
16 594250000 5 40 256 qam 24
17 658250000 3.5 38 256 qam 25
18 666250000 3 38 256 qam 26
19 674250000 3.2 38 256 qam 27
20 682250000 3.7 38 256 qam 28
21 690250000 3.9 38 256 qam 29
22 698250000 4 38 256 qam 30
23 706250000 4.1 40 256 qam 31
24 714250000 4.3 38 256 qam 32


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 8984 205
2 Locked 40.3 10275 325
3 Locked 38.9 11493 251
4 Locked 40.3 12306 341
5 Locked 38.6 13964 359
6 Locked 38.6 17075 377
7 Locked 38.9 20241 311
8 Locked 38.9 21422 359
9 Locked 38.6 22599 416
10 Locked 38.9 25518 341
11 Locked 38.9 30180 301
12 Locked 38.9 33839 376
13 Locked 38.9 35526 276
14 Locked 38.6 36110 302
15 Locked 38.9 36024 395
16 Locked 40.3 40795 351
17 Locked 38.6 80454 159
18 Locked 38.9 86407 194
19 Locked 38.9 88592 158
20 Locked 38.6 95774 108
21 Locked 38.6 91839 139
22 Locked 38.9 91846 197
23 Locked 40.3 94518 140
24 Locked 38.9 101912 173

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400151 39.8 5120 64 qam 6
2 46199915 42.8 5120 64 qam 5
3 32600102 38.5 5120 64 qam 7


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 16 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 35 0

0 Kudos
Reply