on 24-02-2023 07:03
Our hub is regularly kicking off all connected devices (Ethernet and WiFi) several times a day. Service Status for the area has been green every day the past week so it is just a problem for us. How do I get a resolution?
on 24-02-2023 15:30
on 25-02-2023 07:39
Thanks John. Here it is.
Downstream bonded channels
1 | 139000000 | 7 | 40 | QAM 256 | 1 |
2 | 147000000 | 7 | 40 | QAM 256 | 2 |
3 | 155000000 | 6.9 | 40 | QAM 256 | 3 |
4 | 163000000 | 6.7 | 41 | QAM 256 | 4 |
5 | 171000000 | 6.3 | 41 | QAM 256 | 5 |
6 | 179000000 | 6.6 | 41 | QAM 256 | 6 |
7 | 187000000 | 6.2 | 40 | QAM 256 | 7 |
8 | 195000000 | 6.5 | 40 | QAM 256 | 8 |
9 | 203000000 | 6.4 | 41 | QAM 256 | 9 |
10 | 211000000 | 6.3 | 40 | QAM 256 | 10 |
11 | 219000000 | 5.9 | 40 | QAM 256 | 11 |
12 | 227000000 | 5.8 | 40 | QAM 256 | 12 |
13 | 235000000 | 5.7 | 40 | QAM 256 | 13 |
14 | 243000000 | 5.6 | 41 | QAM 256 | 14 |
15 | 251000000 | 5.6 | 41 | QAM 256 | 15 |
16 | 259000000 | 5.1 | 40 | QAM 256 | 16 |
17 | 267000000 | 4.8 | 40 | QAM 256 | 17 |
18 | 275000000 | 4.6 | 40 | QAM 256 | 18 |
19 | 283000000 | 4.6 | 41 | QAM 256 | 19 |
20 | 291000000 | 4.8 | 41 | QAM 256 | 20 |
21 | 299000000 | 5 | 41 | QAM 256 | 21 |
22 | 307000000 | 5 | 41 | QAM 256 | 22 |
23 | 315000000 | 4.7 | 41 | QAM 256 | 23 |
24 | 323000000 | 5 | 41 | QAM 256 | 24 |
25 | 331000000 | 5.2 | 41 | QAM 256 | 25 |
26 | 339000000 | 5.2 | 41 | QAM 256 | 26 |
27 | 347000000 | 5.5 | 41 | QAM 256 | 27 |
28 | 355000000 | 5.9 | 41 | QAM 256 | 28 |
29 | 363000000 | 6.4 | 42 | QAM 256 | 29 |
30 | 371000000 | 6.5 | 42 | QAM 256 | 30 |
31 | 379000000 | 6.8 | 42 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 40 | 7 | 0 |
2 | Locked | 40 | 10 | 0 |
3 | Locked | 40 | 9 | 0 |
4 | Locked | 41 | 7 | 0 |
5 | Locked | 41 | 11 | 0 |
6 | Locked | 41 | 11 | 0 |
7 | Locked | 40 | 8 | 0 |
8 | Locked | 40 | 7 | 0 |
9 | Locked | 41 | 10 | 0 |
10 | Locked | 40 | 7 | 0 |
11 | Locked | 40 | 9 | 0 |
12 | Locked | 40 | 10 | 0 |
13 | Locked | 40 | 13 | 0 |
14 | Locked | 41 | 17 | 0 |
15 | Locked | 41 | 8 | 0 |
16 | Locked | 40 | 8 | 0 |
17 | Locked | 40 | 11 | 0 |
18 | Locked | 40 | 13 | 0 |
19 | Locked | 41 | 17 | 0 |
20 | Locked | 41 | 15 | 0 |
21 | Locked | 41 | 24 | 0 |
22 | Locked | 41 | 15 | 0 |
23 | Locked | 41 | 30 | 0 |
24 | Locked | 41 | 35 | 0 |
25 | Locked | 41 | 29 | 0 |
26 | Locked | 41 | 31 | 0 |
27 | Locked | 41 | 33 | 0 |
28 | Locked | 41 | 48 | 0 |
29 | Locked | 42 | 43 | 0 |
30 | Locked | 42 | 44 | 0 |
31 | Locked | 42 | 42 | 0 |
Upstream bonded channels
0 | 49600000 | 44 | 5120 | QAM 64 | 1 |
1 | 43100000 | 43.5 | 5120 | QAM 64 | 2 |
2 | 36600000 | 42.5 | 5120 | QAM 64 | 3 |
3 | 30100000 | 42 | 5120 | QAM 64 | 4 |
4 | 23600000 | 41.5 | 5120 | QAM 64 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
on 25-02-2023 07:41
Time | Priority | Description |
25/02/2023 07:24 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 07:22 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 07:22 | warning | MDD message timeout;CM-MAC=replaced :27;CMTS- |
25/02/2023 06:59 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 06:59 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 04:24 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 04:24 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:44 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:42 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:42 | warning | MDD message timeout;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:24 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:24 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:03 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:01 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 03:01 | warning | MDD message timeout;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 02:33 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 02:33 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:30 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:29 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:28 | warning | MDD message timeout;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:25 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:25 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:02 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 01:02 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 00:15 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 00:14 | notice | CM-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=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
25/02/2023 00:13 | warning | MDD message timeout;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 23:52 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 23:52 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 23:52 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 23:52 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 23:51 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 23:51 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 22:42 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
24/02/2023 22:42 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=replaced:27;CMTS-MAC=replaced:91;CM-QOS=1.1;CM-VER=3.1; |
on 25-02-2023 08:34
on 25-02-2023 08:35
[url=https://www.thinkbroadband.com/broadband/monitoring/quality/share/16ba4d9bd07dedda57a6079ab56933b05608f9e0]My Broadband Ping[/url]
on 25-02-2023 08:39
https://www.thinkbroadband.com/broadband/monitoring/quality/share/16ba4d9bd07dedda57a6079ab56933b05608f9e0
on 25-02-2023 16:23
on 26-02-2023 10:27
Thanks for taking a look. Will look up threads on packet drops.
on 26-02-2023 16:24
I have now tried selecting the ‘Block fragmented IP packets’ box in Firewall settings, which was the only one deselected by default. No dropped pings on the graph since doing this nor breaks in Ethernet or WiFi connections in the house. Crossing my fingers this may have been the issue - broken data coming into the Hub from outside causing it to engage the Firewall function perhaps?