20-07-2021 10:59 - edited 20-07-2021 11:08
Hi, I’ve been following a few threads in this issue woth Ping/latency ect.
could someone advise on the below and how best to try improve it.
currently on the OOMP package (600) wired connection
on 22-07-2021 11:37
Hi coljenks1980, thanks for your post.
Sorry to hear you've had some issues with ping/latency. I can't see any information in your post about this as suggested - and I wasn't able to look into this using your forum details on this occasion.
I'll be happy to take a further look into it if you get back to me via PM, just look out for the purple envelope & we'll take it from there.
Tom
on 25-07-2021 08:40
Thanks for getting back to me @coljenks1980.
Taking a look into this there are no known issues and on the surface everything appears to be OK.
When digging a bit deeper though I can some of the downstream power levels are borderline high, and with natural fluctuations these could be pushed out of spec from time to time causing the connection issues.
Can you please post some hub-stats to give us an idea of the impact this is having and help us determine the best course of action? If you're unsure how:
In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) and hit return. If you have a hub 2 or 3 when the page loads don't log in but click ‘Check Router Status’. If you have a Hub 4 when the page loads log in and then click ‘Check Router Status’. Copy full sets of data onto here from the downstream, upstream, & network logs pages and paste them here. Copy full sets of data onto here from the downstream, upstream, & network logs pages and paste them here. Please don’t post screencaps - if you copy/paste the data the forum software should blank any sensitive details out for you.
You can also set up a free “Broadband Quality Monitor” to continually monitor the state of your connection and record any network dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections: https://www.thinkbroadband.com/broadband/monitoring/quality
Tom
on 25-07-2021 12:26
25/07/2021 12:18:52noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;25/07/2021 12:18:40Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;23/07/2021 08:13:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;23/07/2021 07:06:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;19/07/2021 21:22:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;19/07/2021 19:06:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;17/07/2021 02:39:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;16/07/2021 07:06:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;16/07/2021 01:10:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;15/07/2021 18:13:46noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 01:27:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;13/07/2021 21:49:30noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;12/07/2021 22:19:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;12/07/2021 19:06:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;12/07/2021 02:19:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;11/07/2021 18:25:42noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;11/07/2021 18:22:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;11/07/2021 11:20:46noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;10/07/2021 13:46:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;10/07/2021 04:53:39criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Downstream bonded channels
Upstream
1 | 46200000 | 46.3 | 5120 | 64 qam | 1 |
2 | 32600000 | 45.8 | 5120 | 64 qam | 3 |
3 | 39400000 | 46 | 5120 | 64 qam | 2 |
4 | 25800000 | 45.8 | 5120 | 64 qam | 4 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 42 | 0 |
2 | ATDMA | 0 | 0 | 40 | 0 |
3 | ATDMA | 0 | 0 | 26 | 0 |
4 | ATDMA | 0 | 0 | 39 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 483000000 | 4.3 | 40 | 256 qam | 32 |
2 | 203000000 | 5 | 40 | 256 qam | 9 |
3 | 211000000 | 5 | 40 | 256 qam | 10 |
4 | 219000000 | 5.1 | 40 | 256 qam | 11 |
5 | 227000000 | 5 | 40 | 256 qam | 12 |
6 | 235000000 | 5 | 40 | 256 qam | 13 |
7 | 243000000 | 4.6 | 40 | 256 qam | 14 |
8 | 251000000 | 5 | 40 | 256 qam | 15 |
9 | 259000000 | 5 | 40 | 256 qam | 16 |
10 | 267000000 | 5.4 | 40 | 256 qam | 17 |
11 | 275000000 | 5.1 | 40 | 256 qam | 18 |
12 | 283000000 | 5.8 | 40 | 256 qam | 19 |
13 | 291000000 | 6.1 | 40 | 256 qam | 20 |
14 | 299000000 | 6.9 | 40 | 256 qam | 21 |
15 | 307000000 | 7.5 | 40 | 256 qam | 22 |
16 | 315000000 | 7.6 | 40 | 256 qam | 23 |
17 | 323000000 | 7.9 | 40 | 256 qam | 24 |
18 | 427000000 | 6 | 40 | 256 qam | 25 |
19 | 435000000 | 5.8 | 40 | 256 qam | 26 |
20 | 443000000 | 5.3 | 40 | 256 qam | 27 |
21 | 451000000 | 5.1 | 40 | 256 qam | 28 |
22 | 459000000 | 5.1 | 40 | 256 qam | 29 |
23 | 467000000 | 5 | 40 | 256 qam | 30 |
24 | 475000000 | 4.3 | 40 | 256 qam | 31 |
on 25-07-2021 13:06
Thank you, there's certainly more errors/time-outs than we'd like to see there. If all of your connections are snug & secure then we'll need to arrange a tech-visit, I'll get in touch via PM so we can get that sorted.
Tom