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: 

High Latency Issues :(

johnrs1970
Joining in

on ‎23-12-2022 14:25

Hi All.  I see there are a few posts about this topic.  I am having the same issue.  I have just upgraded to the 1GB package and received a new hub5.

These are some of the logs.  Hoping someone can help. 

Many thanks for advice and help.  🙂

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000005.841QAM 25625
21390000007.840QAM 2561
31470000007.540QAM 2562
41550000007.440QAM 2563
51630000007.240QAM 2564
6171000000740QAM 2565
71790000006.940QAM 2566
81870000006.841QAM 2567
91950000006.641QAM 2568
102030000006.441QAM 2569
112110000006.441QAM 25610
122190000006.10QAM 25611
132270000005.937QAM 25612
142350000005.741QAM 25613
152430000005.341QAM 25614
162510000004.941QAM 25615
17259000000541QAM 25616
182670000005.141QAM 25617
192750000005.341QAM 25618
202830000005.741QAM 25619
212910000005.941QAM 25620
222990000005.741QAM 25621
233070000005.941QAM 25622
24315000000642QAM 25623
25323000000642QAM 25624
263390000005.842QAM 25626
273470000005.841QAM 25627
283550000005.641QAM 25628
293630000005.741QAM 25629
303710000005.641QAM 25630
313790000005.441QAM 25631
0 Kudos
7 REPLIES 7

johnrs1970
Joining in

on ‎23-12-2022 14:26

these logs are after a 5 min power off and back on again.

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4145453
2Locked402810297155100
3Locked401456671261498
4Locked4014454309151275
5Locked4030954712275
6Locked409962616653
7Locked4014111349532
8Locked418123915310
9Locked4195275313
10Locked41180315228
11Locked411071965248
12Locked01357700
13Locked372637662515011327
14Locked414524292161
15Locked413866668228
16Locked413583102419
17Locked415092525
18Locked41673551364
19Locked411714523303
20Locked4139606361
21Locked41896720749
22Locked414654786618
23Locked41226856
24Locked4240537
25Locked4227542
26Locked4283756
27Locked4176267947
28Locked4133798941
29Locked4121527
30Locked4131033
31Locked4158529
0 Kudos

Adduxi
Very Insightful Person
Very Insightful Person

on ‎23-12-2022 14:29

You need to post all the logs and the network log as well. 

A BQM will not go amiss either   www.thinkbroadband.com/ping   This will show up any capacity problems in the area.

Are you using wired or wifi connections for gaming, as a direct Cat 6a wired connection would be preferred.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos

johnrs1970
Joining in
In response to Adduxi

on ‎23-12-2022 15:01

Thanks

 

Here are the network logs

etwork Log

Time Priority Description
23-12-2022 14:00:58noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:55:41noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:53:57noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6 12; 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;
23-12-2022 13:52:15noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6; 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;
23-12-2022 13:52:03noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 11 12; 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;
23-12-2022 13:50:45noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 1; 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;
23-12-2022 13:50:35noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 1 11 12; 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;
23-12-2022 13:50:28warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:47:53noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6; 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;
23-12-2022 13:47:37noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 11 12; 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;
23-12-2022 13:47:18warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:43:52noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6 12; 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;
23-12-2022 13:43:44noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 11; 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;
23-12-2022 13:43:34warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:40:04noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 11 12; 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;
23-12-2022 13:39:55noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6; 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;
23-12-2022 13:38:12noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 6 7 11 12; 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;
23-12-2022 13:38:02noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 1; 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;
23-12-2022 13:37:47noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 6; 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;
23-12-2022 13:37:45warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:37:45noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 1 6 11 12; 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;
23-12-2022 13:36:26noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 6 7 11 12; 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;
23-12-2022 13:36:21noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 6; 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;
23-12-2022 13:35:33noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:35:31noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 7 11 12; 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;
23-12-2022 13:35:26noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 1 6 11 12; 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;
23-12-2022 13:35:25noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 1 6; 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;
23-12-2022 13:35:17noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 2 3 4 7 11 12; 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;
23-12-2022 13:35:12warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:35:10noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 1 2 3 4 7 11; 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;
23-12-2022 13:35:06warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-12-2022 13:21:53noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 12; 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

johnrs1970
Joining in
In response to johnrs1970

‎23-12-2022 15:03 - edited ‎23-12-2022 15:07 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/7efb90c434832d2b9b8ecf18364371aa072c1d42
0 Kudos

johnrs1970
Joining in
In response to johnrs1970

on ‎25-12-2022 17:08

thought I would post some more logs

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked41656490
2Locked372829920155497
3Locked361463981364229
4Locked3914461715152532
5Locked4031266913333
6Locked4010104017016
7Locked3718346856449
8Locked408374115648
9Locked40964751067
10Locked40181278389
11Locked401262373883
12Locked34188561852192
13Locked313562963515336711
14Locked404525037286
15Locked403925744776
16Locked4038840741029
17Locked4059751081
18Locked41673760541
19Locked411721993439
20Locked4141371464
21Locked409191051105
22Locked405115445808
23Locked412546197
24Locked41576133
25Locked41439234
26Locked411031266
27Locked41764889202
28Locked41345683112
29Locked41398136
30Locked41516170
31Locked41764122
0 Kudos

johnrs1970
Joining in
In response to johnrs1970

on ‎25-12-2022 17:10

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000005.241QAM 25625
21390000007.137QAM 2561
31470000006.836QAM 2562
41550000006.639QAM 2563
51630000006.340QAM 2564
61710000006.240QAM 2565
7179000000637QAM 2566
81870000006.140QAM 2567
91950000006.240QAM 2568
102030000005.840QAM 2569
112110000005.640QAM 25610
122190000005.234QAM 25611
132270000004.831QAM 25612
142350000004.540QAM 25613
152430000004.240QAM 25614
162510000003.940QAM 25615
172590000004.240QAM 25616
182670000004.541QAM 25617
192750000004.841QAM 25618
202830000004.941QAM 25619
21291000000540QAM 25620
22299000000540QAM 25621
233070000005.241QAM 25622
243150000005.341QAM 25623
253230000005.441QAM 25624
263390000005.141QAM 25626
273470000005.141QAM 25627
28355000000541QAM 25628
293630000004.941QAM 25629
303710000004.641QAM 25630
313790000004.541QAM 25631

 

Network Log

Time Priority Description
25-12-2022 17:06:50noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6 7 11 12; 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-12-2022 17:06:36noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 11 12; 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-12-2022 17:06:20warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 17:06:15noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6 7 11 12; 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-12-2022 17:06:09warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 17:00:49noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 10:10:53noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 10:00:05noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 09:55:14noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 09:37:55noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 08:56:43noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 08:54:57noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:55:42noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:53:26noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6 7 11 12; 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-12-2022 07:53:18noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 11 12; 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-12-2022 07:51:32noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 12; 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-12-2022 07:51:20noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 12; 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-12-2022 07:51:12warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:44:55noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:43:27noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:42:14noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:39:33noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 11 12; 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-12-2022 07:39:14noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 6 7 11 12; 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-12-2022 07:39:05noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:39:03noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 12; 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-12-2022 07:38:57noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 11; 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-12-2022 07:38:53noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 12; 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-12-2022 07:38:26warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-12-2022 07:37:19noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-12-2022 23:38:20noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-12-2022 23:36:02noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-12-2022 20:11:05noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

Paul_DN
Forum Team
Forum Team
In response to johnrs1970

on ‎27-12-2022 13:34

Hi johnrs1970,

Thank you for reaching out to us in our community and welcome back, I was able to locate you on our system with the details we have for you and have found an issue which does require a technician, so I can arrange this, I will send you an invite into a private chat, once received please click on the purple envelope to accept.

Regards

Paul.

 

0 Kudos
Top