Internet dropouts: interesting promise by VM, should I believe it?

[seunje]

This is what I have been told today, after 2+ months of internet dropout horror show

"<name>, I am going to make few updates and changes on the acocunt to get the stable connection until the outage is fixed for that i need to clear the security checks on the account. Hence Let us quickly clear the security checks and can I take the 1st, 10th and 13th character of the password. "

it looks much more like a lie compared to other promises (which were never carried out), I almost think it may be true!

Anyway, I did set up https://www.thinkbroadband.com/broadband/monitoring/quality/create so will see!

[jbrennand]

Your link is to the login page - so no good.

Post the link to "Share live graph" - its under the trace on the TB site

[seunje]

---

@jbrennand wrote:
Your link is to the login page - so no good.

Post the link to "Share live graph" - its under the trace on the TB site

---

I only mean to indicate that I have created that! It has only up for very short while, so not much there:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fe007fca5bf49d93a6e524efbe33afa8ee...

the yellow peak that is happening now may be due to VM support "fixing" it, here's what I've just been told on chat:

"<name>, Thank you for confirming the details, I am in the process of making few changes. I request you not to use the wifi. Kindly connect the internet to mobile date or hotspot so that we get inactive while doing the procedure. Kindly provide me few minutes while i work on it."

[seunje]

By the way, super useful tool, feel stupid for not setting it up when I first saw it recommended here

[jbrennand]

Its building now.

Lets see the rest of the connection data - can you do this
________________________________________________

In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return.

On the first page up dont login (unless you have the Hub4/5 - when you do need to login) just click on the “router status” icon/text at bottom-middle (Hub3) or top/right (SH’s) of the Login page

Then Navigate to these “pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs page. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again. If character limits are “exceeded” - just do two posts

[seunje]

Here are the tables in order they appear in the tabs.

Thanks for looking into this

Channel
Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
17 266750000 8.000000 38.983261 QAM256 17
6 178750000 9.199997 38.983261 QAM256 6
7 186750000 9.099998 40.366287 QAM256 7
8 194750000 8.800003 40.366287 QAM256 8
9 202750000 8.500000 38.983261 QAM256 9
10 210750000 8.199997 40.366287 QAM256 10
11 218750000 8.099998 38.983261 QAM256 11
12 226750000 7.699997 38.983261 QAM256 12
13 234750000 7.699997 38.983261 QAM256 13
14 242750000 7.800003 38.983261 QAM256 14
15 250750000 7.900002 38.983261 QAM256 15
16 258750000 8.099998 38.983261 QAM256 16
18 274750000 8.000000 38.983261 QAM256 18
19 282750000 7.300003 38.605377 QAM256 19
20 290750000 7.599998 38.605377 QAM256 20
21 298750000 7.800003 38.983261 QAM256 21
22 306750000 8.099998 40.366287 QAM256 22
23 314750000 8.099998 38.983261 QAM256 23
24 322750000 8.199997 38.983261 QAM256 24
25 330750000 7.900002 38.983261 QAM256 25
26 338750000 7.500000 38.983261 QAM256 26
27 346750000 7.400002 38.983261 QAM256 27
28 354750000 7.300003 38.983261 QAM256 28
29 362750000 7.300003 38.983261 QAM256 29
30 370750000 7.099998 38.983261 QAM256 30
31 378750000 7.199997 38.605377 QAM256 31
32 386750000 6.800003 38.983261 QAM256 32
34 394750000 6.699997 38.605377 QAM256 34
35 402750000 6.400002 38.605377 QAM256 35
36 410750000 6.599998 38.983261 QAM256 36
37 418750000 6.500000 38.983261 QAM256 37

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
17 Locked 38.983261 0 0
6 Locked 38.983261 0 0
7 Locked 40.366287 0 0
8 Locked 40.366287 0 0
9 Locked 38.983261 0 0
10 Locked 40.366287 0 0
11 Locked 38.983261 0 0
12 Locked 38.983261 0 0
13 Locked 38.983261 0 0
14 Locked 38.983261 0 0
15 Locked 38.983261 0 0
16 Locked 38.983261 0 0
18 Locked 38.983261 0 0
19 Locked 38.605377 0 0
20 Locked 38.605377 0 0
21 Locked 38.983261 0 0
22 Locked 40.366287 7 0
23 Locked 38.983261 0 0
24 Locked 38.983261 0 0
25 Locked 38.983261 0 0
26 Locked 38.983261 0 0
27 Locked 38.983261 0 0
28 Locked 38.983261 0 0
29 Locked 38.983261 0 0
30 Locked 38.983261 0 0
31 Locked 38.605377 0 0
32 Locked 38.983261 0 0
34 Locked 38.605377 0 0
35 Locked 38.605377 0 0
36 Locked 38.983261 0 0
37 Locked 38.983261 0 0

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33 94 4K 1840 QAM4096 424

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33 Locked 41 5.2 10381646
0 

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 23600000 41.270599 5120 "KSym/sec" 64QAM 11
2 30100000 41.270599 5120 "KSym/sec" 64QAM 10
3 49600000 41.770599 5120 "KSym/sec" 64QAM 7
4 43100000 41.520599 5120 "KSym/sec" 64QAM 8
5 36600000 41.270599 5120 "KSym/sec" 64QAM 9

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 US_TYPE_STDMA 0 0 1 0
2 US_TYPE_STDMA 0 0 0 0
3 US_TYPE_STDMA 0 0 0 0
4 US_TYPE_STDMA 0 0 0 0
5 US_TYPE_STDMA 0 0 0 0

Time Priority Description
Thu Jan 1 00:01:19 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:05 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:05 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:07 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 15:20:11 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:19 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:54 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:54 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:56 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 15:53:01 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:22 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:55 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:55 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:57 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 16:13:17 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:22 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:05 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:05 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:06 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 22:43:07 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:20 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:58 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:58 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:05:59 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 22:50:46 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:20 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:56 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:56 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:58 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 23:11:01 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:21 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:36 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:36 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:07:38 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 23:29:51 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:21 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:25 1970 3 Ranging Request Retries exhausted;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:25 1970 3 16 consecutive T3 timeouts while trying to range on upstream channel 13;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:06:26 1970 3 No Ranging Response received - T3 time-out;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;
Thu Sep 22 23:42:44 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(BLANKED_OUT);CMTS-MAC=(BLANKED_OUT);CM-QOS=1.1;CM-VER=3.1;

[jbrennand]

Looks like a Hub5?

All power stats and RS/T3 errors look fine and within range.

Logs do look strange though - but I am no expert and someone else will need to comment on them

[seunje]

---

@jbrennand wrote:
Looks like a Hub5?

All power stats and RS/T3 errors look fine and within range.

Logs do look strange though - but I am no expert and someone else will need to comment on them

---

Yep logs got timestamps messed up.

These tables are right after VM support has updated something in it - my WiFi SSID was changed as well.

[jbrennand]

BQM shows the connection was down for ~10 minutes just before 4pm. Was that VM doing something?

Since then its looking very nice.

[Tudor]

Looking closely at the log it seems to me that the hub is not sorting the output into date/time. All the 01 Jan 1970 entries would be when the hub starts up before it’s got the time from the CMTS. The Sep 22 entries all look ok.