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: 

Possibly Hub Issue

Go to solution
MartJ
Rising star

on ‎24-01-2023 21:02

I have had to reboot hub a few times due to wifi issues again, I had the hub replaced a beginning of January everything OK until 16 January, looking at my BQM I notice that the dropped packets have taken over the Hub so to speak.

This was as it was yesterday

MartJ_0-1674593146100.png

This as it is now

MartJ_1-1674593325828.png

Rebooted Hub on 17, the redness retuned on 18, rebooted on 19th when I noticed issue again, then rebooted again late on 22, but issue back today.

We are also seeing buffering on our Amazon Firestick when streaming, plus to random wifi disconnections, not as many as previously.

Any thoughts as to why I am seeing this problem? Do I have to reboot everyday?

 

 

Martin
0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
MartJ
Rising star
In response to Akua_A

on ‎15-03-2023 14:28

Has been a week since the principal engineer has been, he again check all the connections, the cabinet and also replace Hub4 with a Hub5, a week has passed and no significant issues have occurred, very few dropouts, speed is much better even on mobile devices. I was able to split the SSIDs into 2.4 and 5 ghz, thus my smart plugs and 1t Series Amazon Echo are working fine.

Hopefully after 4 months of problems there will be no further issues. 

Martin

See where this Helpful Answer was posted

0 Kudos
49 REPLIES 49

Go to solution
MartJ
Rising star

on ‎24-01-2023 21:09

This is current speedtest on my Laptop via wifi connection, we are a 1 gig connection

MartJ_0-1674594574580.png

 

Martin
0 Kudos

Go to solution
MartJ
Rising star
In response to MartJ

on ‎24-01-2023 21:12

Now via wired connection

MartJ_0-1674594731368.png

 

Martin
0 Kudos

Go to solution
MartJ
Rising star
In response to MartJ

on ‎24-01-2023 21:13

Downstream Stats

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

253310000002.00000037.636276QAM25625
11390000008.00000038.983261QAM2561
21470000007.69999738.983261QAM2562
31550000007.40000238.983261QAM2563
41630000006.80000338.983261QAM2564
51710000006.40000238.605377QAM2565
61790000006.00000038.605377QAM2566
71870000006.00000038.605377QAM2567
81950000005.69999738.605377QAM2568
92030000005.40000238.605377QAM2569
102110000005.09999838.983261QAM25610
112190000005.19999738.605377QAM25611
122270000005.19999738.983261QAM25612
132350000005.30000338.605377QAM25613
142430000005.00000038.605377QAM25614
152510000005.00000038.605377QAM25615
162590000004.69999738.605377QAM25616
172670000004.30000338.605377QAM25617
182750000004.00000038.605377QAM25618
192830000004.00000038.983261QAM25619
202910000003.50000038.605377QAM25620
212990000002.79999938.605377QAM25621
223070000001.90000238.605377QAM25622
233150000001.40000238.605377QAM25623
243230000001.40000237.636276QAM25624
263390000002.50000038.605377QAM25626
273470000002.40000238.605377QAM25627
283550000002.40000238.605377QAM25628
293630000002.40000238.605377QAM25629
303710000002.29999938.605377QAM25630
313790000002.40000238.605377QAM25631



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

25Locked37.63627600
1Locked38.98326100
2Locked38.98326100
3Locked38.98326100
4Locked38.98326100
5Locked38.60537700
6Locked38.60537700
7Locked38.60537700
8Locked38.60537700
9Locked38.60537700
10Locked38.98326100
11Locked38.60537700
12Locked38.98326100
13Locked38.60537700
14Locked38.60537700
15Locked38.60537700
16Locked38.60537700
17Locked38.60537700
18Locked38.60537700
19Locked38.98326100
20Locked38.60537700
21Locked38.60537700
22Locked38.60537700
23Locked38.60537700
24Locked37.63627600
26Locked38.60537700
27Locked38.60537700
28Locked38.60537700
29Locked38.60537700
30Locked38.60537700
31Locked38.60537700



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked39-3.3153429841310675
Martin
0 Kudos

Go to solution
carl_pearce
Community elder

on ‎24-01-2023 21:14

Check if your public IP address has changed vs the IP address the BQM is monitoring.

0 Kudos

Go to solution
MartJ
Rising star
In response to MartJ

on ‎24-01-2023 21:15

Upstream Logs

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13010000039.0205995120 KSym/sec64QAM4
22360000038.0205995120 KSym/sec64QAM5
33660000039.5205995120 KSym/sec64QAM3
44310000039.5205995120 KSym/sec64QAM2
54960000040.0205995120 KSym/sec64QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
5US_TYPE_STDMA0010



3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
610.034.52KQAM8


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA20053.900
Martin
0 Kudos

Go to solution
MartJ
Rising star
In response to MartJ

on ‎24-01-2023 21:16

Network Log, note nothing shows after first reboot on 16th

Network Log

Time Priority Description

Sun Jan 8 19:57:59 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 8 21:14:24 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 8 21:25:37 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 8 23:12:23 20236US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 8 23:39:53 20234DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 8 23:39:53 20236DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 9 13:56:39 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 9 15:42:57 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 9 20:59:34 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 10 15:42:55 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 10 19:05:53 20236US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 10 23:20:51 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 11 15:43:17 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 12 11:39:53 20234DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 12 11:39:53 20236DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 12 15:43:00 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 13 01:27:16 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 13 15:43:05 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 14 12:14:46 20236US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 14 15:44:31 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 14 21:40:56 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jan 14 23:21:07 20233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 15 19:53:40 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 15 23:39:52 20234DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 15 23:39:52 20236DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 16 15:42:56 20236CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Martin
0 Kudos

Go to solution
MartJ
Rising star
In response to carl_pearce

on ‎24-01-2023 21:18

Addresses are the same

Martin
0 Kudos

Go to solution
jbrennand
Very Insightful Person
Very Insightful Person
In response to MartJ

on ‎24-01-2023 21:18

Red wall suggests the router is not responding to ICMP "pings" - or the ip adress in the BQM settings is incorrect

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

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos

Go to solution
MartJ
Rising star
In response to jbrennand

on ‎24-01-2023 21:34

The IP Addresses of router and BQM are the same. Issue goes away after reboot, but returns after a day or so. 

The BQM was fine from 9 to 15 January, so what has changed?

 

Martin
0 Kudos
Top