Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Frequent disconnects since upgrading to the Hub 5

Cstark
Tuning in

on ‎24-11-2022 18:11

Hi there,

Since upgrading from the Hub 4 to Hub 5 I have been getting recent disconnects which is incredibly frustrating! 

Hub 5 is in modem mode.

I suspect it's the equipment at fault but would be good if someone could take a look and confirm 🙂

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
11460000003.541QAM 2562
21380000003.841QAM 2561
31540000003.341QAM 2563
41620000003.441QAM 2564
51700000003.641QAM 2565
61780000003.440QAM 2566
71860000003.440QAM 2567
81940000003.341QAM 2568
92020000003.341QAM 2569
102100000003.841QAM 25610
112180000004.242QAM 25611
122260000003.941QAM 25612
132340000003.641QAM 25613
142420000003.441QAM 25614
152500000003.441QAM 25615
162580000003.441QAM 25616
172660000003.141QAM 25617
182740000002.541QAM 25618
192820000002.341QAM 25619
202900000002.141QAM 25620
212980000002.141QAM 25621
223060000002.141QAM 25622
233140000002.741QAM 25623
243220000002.941QAM 25624
253300000002.541QAM 25625
26338000000240QAM 25626
273460000002.541QAM 25627
283540000003.241QAM 25628
293620000003.241QAM 25629
303700000002.441QAM 25630
313780000002.241QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked41104977
2Locked41121
3Locked4161518493
4Locked41116478172
5Locked41122198760
6Locked4092349027
7Locked40130208432
8Locked41164411776
9Locked419811993
10Locked415092547
11Locked42115150
12Locked412708333
13Locked411956204
14Locked4199507029
15Locked41600213957
16Locked4188857952
17Locked4168517740
18Locked4179144077
19Locked4170485092
20Locked4160165
21Locked4181727104
22Locked4136053810
23Locked413331678
24Locked413941960
25Locked415861660
26Locked401433872
27Locked41547391
28Locked41247236
29Locked41489403
30Locked41459314
31Locked41428238

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
06030000034.35120QAM 649
15370000034.85120QAM 6410
24620000034.35120QAM 6411
33940000034.35120QAM 6412

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000

 

Network Log

Time Priority Description
24-11-2022 18:04:48noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 18:02:47noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 18:02:33warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 17:58:55noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 17:57:50noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 17:57:29warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 17:01:57noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 17:00:38noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 17:00:11warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 16:26:40noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 16:25:34noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 16:25:15warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 15:53:35noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 15:52:05noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 15:52:03warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 12:36:31noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 12:35:44noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 12:35:21warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 10:36:34noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 10:35:39noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 10:35:17warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 10:13:34noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 10:12:07noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 10:11:53warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 05:30:04noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 05:29:05noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 05:28:49warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 00:22:55noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 00:21:59noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 00:21:33warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-11-2022 20:46:28noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;C
23-11-2022 20:46:28noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

0 Kudos
31 REPLIES 31

Cstark
Tuning in

on ‎25-11-2022 11:08

Forgot to mention I have tried the usual rebooting, and reconnecting the cables.

More disconnects happened last night/today:

Network Log

Time Priority Description
25-11-2022 09:42:04noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 09:41:12noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 09:40:51warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 08:09:36noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 08:08:23noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 08:07:53warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 22:44:52noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 22:43:17noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 22:43:15warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 21:06:53noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 21:05:29noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 21:05:19warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 20:05:56noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 20 28 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 20:04:51noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2022 20:04:43warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

Tudor
Very Insightful Person
Very Insightful Person
In response to Cstark

on ‎25-11-2022 12:17

Too many errors, but the figures are accumulative since the hub was last power cycled. So please turn off your hub for a short period, this will reset the counters, then post a new full set of stats after about two hours. This will indicate the current line status. 

Also Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page status, but this is not recommended as it only covers issues that affect a very large number of customers.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

Cstark
Tuning in
In response to Tudor

on ‎25-11-2022 16:29

Hub restarted and had a few more disconnects, however, don't seem to have any errors this time in the downstream...

The timeouts seem to coincide with the following messageMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; seen in the Network Log.

Called Area faults and no known issue.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
11460000003.641QAM 2562
21380000003.841QAM 2561
31540000003.441QAM 2563
41620000003.441QAM 2564
51700000003.741QAM 2565
61780000003.541QAM 2566
71860000003.541QAM 2567
81940000003.441QAM 2568
92020000003.441QAM 2569
102100000003.841QAM 25610
112180000004.242QAM 25611
12226000000442QAM 25612
132340000003.742QAM 25613
142420000003.542QAM 25614
152500000003.542QAM 25615
162580000003.441QAM 25616
172660000003.241QAM 25617
182740000002.641QAM 25618
192820000002.341QAM 25619
202900000002.241QAM 25620
212980000002.141QAM 25621
223060000002.141QAM 25622
233140000002.741QAM 25623
24322000000341QAM 25624
253300000002.541QAM 25625
263380000002.141QAM 25626
273460000002.541QAM 25627
283540000003.241QAM 25628
293620000003.241QAM 25629
303700000002.441QAM 25630
313780000002.241QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4100
2Locked4100
3Locked4100
4Locked4100
5Locked4100
6Locked4100
7Locked4100
8Locked4100
9Locked4100
10Locked4100
11Locked4200
12Locked4200
13Locked4200
14Locked4200
15Locked4200
16Locked4100
17Locked4100
18Locked4100
19Locked4100
20Locked4100
21Locked4100
22Locked4100
23Locked4100
24Locked4100
25Locked4100
26Locked4100
27Locked4100
28Locked4100
29Locked4100
30Locked4100
31Locked4100

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
06030000034.35120QAM 649
15370000034.85120QAM 6410
24620000034.85120QAM 6411
33940000034.35120QAM 6412

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
06030000034.35120QAM 649
15370000034.85120QAM 6410
24620000034.85120QAM 6411
33940000034.35120QAM 6412

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA000

0

 

 

Network Log

Time Priority Description
25-11-2022 15:24:33noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 15:23:12noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 15:22:53warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 15:08:17noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 15:07:18noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 15:06:59warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 13:08:03noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 13:06:58noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 13:06:31warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:28:52criticalDHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:28:37criticalDHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:28:36criticalDHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:55noticeREGISTRATION COMPLETE - Waiting for Operational status
25-11-2022 12:21:50warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:45noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:41noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:39warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:37noticeHonoring MDD; IP provisioning mode = IPv4
25-11-2022 12:21:28criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:28criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:27criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:23criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:23criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-11-2022 12:21:11criticalCable Modem Reboot due to power button reset
25-11-2022 12:21:11criticalCable Modem Reboot due to power button reset
25-11-2022 12:21:11criticalCable Modem Reboot due to power button reset
25-11-2022 12:21:06criticalCable Modem Reboot due to master console reset
25-11-2022 12:21:06criticalCable Modem Reboot due to master console reset
23-11-2022 20:45:48criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-11-2022 02:43:06criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-11-2022 20:18:11criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-11-2022 20:18:09criticalREG-RSP - invalid format or not recognized;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

legacy1
Alessandro Volta
In response to Cstark

‎25-11-2022 16:35 - edited ‎25-11-2022 16:36

setup a BQM
https://www.thinkbroadband.com/broadband/monitoring/quality
what own router do you have? maybe test with a PC to the hub in modem mode

---------------------------------------------------------------

BQM, Test for outgoing ports and SSL/L2TP VPN test

Cstark
Tuning in
In response to legacy1

on ‎25-11-2022 16:37

Using Nest Wifi Pro which blocks ICMP so BQM is not possible. Hub is already in modem mode... or do you mean some other test?
0 Kudos

legacy1
Alessandro Volta
In response to Cstark

on ‎25-11-2022 17:25

You can connect by wire a PC to the hub in modem mode to do BQM allowed by the firewall
---------------------------------------------------------------

BQM, Test for outgoing ports and SSL/L2TP VPN test

Ashleigh_C
Forum Team
Forum Team
In response to Cstark

on ‎28-11-2022 09:36

Hi there @Cstark

 

Thank you so much for your post and welcome to the community forums, it's great to have you here. 

 

I am so sorry to hear that you are facing these issues with your Hub! Have you been able to try the BQM set up as advised by @legacy1? 

 

If not are you able to switch your Hub to router mode so that we can run diagnostics? 

 

Thank you again.

0 Kudos

Cstark
Tuning in
In response to Ashleigh_C

on ‎28-11-2022 11:07

Thanks for the warm welcome, Ash_C! 

I couldn't get connectivity when connected directly to the Hub in Modem mode for BQM as suggested by @legacy1 Possibly I missed a step.

So I ended up putting the Hub in router mode, so far I have had a couple of drops which correspond to what I see in the network logs:

2e3cb82482af3de6c2dd45a1b49a21aeb3b47946

 

Time Priority Description

28-11-2022 03:37:51noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-11-2022 03:36:46noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-11-2022 03:36:33warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 20:29:05noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 20:27:57noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 20:27:33warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:38:55criticalDHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:38:40criticalDHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:38:39criticalDHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:46noticeREGISTRATION COMPLETE - Waiting for Operational status
27-11-2022 16:31:40warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:35noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:33warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:31criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:31criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:31noticeHonoring MDD; IP provisioning mode = IPv4
27-11-2022 16:31:31criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:30criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:21criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-11-2022 16:31:14criticalCable Modem Reboot due to power button reset
27-11-2022 16:31:14criticalCable Modem Reboot due to power button reset
27-11-2022 16:31:14criticalCable Modem Reboot due to power button reset
27-11-2022 16:31:14criticalCable Modem Reboot due to power button reset
27-11-2022 16:31:09criticalCable Modem Reboot due to master console reset
27-11-2022 16:31:09criticalCable Modem Reboot due to master console reset
27-11-2022 16:31:09criticalCable Modem Reboot due to master console reset
23-11-2022 20:45:48criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-11-2022 02:43:06criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-11-2022 20:18:11criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-11-2022 20:18:09criticalREG-RSP - invalid format or not recognized;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1
0 Kudos

Cstark
Tuning in
In response to Cstark

on ‎28-11-2022 17:13

Now have 24 hours' worth of data.

I had a drop at 14:48:

4934bef4f322fbfbd821a97987426343965db255-28-11-2022

Any thoughts? what can I do to stop these disconnects? never had this issue with the Hub 4! maybe it's just coincidental... 

 

28-11-2022 14:49:41noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-11-2022 14:48:25noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-11-2022 14:48:01warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Top