Menu
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
343 Views
Message 1 of 7
Flag for a moderator

Speed drop

For the past 2 weeks i have had problems with the speed of my router
I have had a steady 90 Mbps   but i pay for 500  so there is a problem somewhere
these are my network logs
Network LogTime Priority Description
28/09/2019 16:19:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/10/2019 09:00:5ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/10/2019 17:25:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/10/2019 20:01:2ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2019 08:30:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2019 10:23:16ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2019 04:58:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2019 08:48:40ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2019 16:17:11ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2019 16:17:11noticeDHCP Renew - lease parameters tftp file-Vcb573b2ee9a9587e.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2019 21:35:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 11:35:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 11:35:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 11:35:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 11:35:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2019 07:35:16ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2019 14:49:19ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2019 14:49:19noticeDHCP Renew - lease parameters tftp file-Vcb573b2ee9a9587e.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/10/2019 01:33:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
 
 
 
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
342 Views
Message 2 of 7
Flag for a moderator

Re: Speed drop


Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 483000000 6 40 256 qam 30
2 187000000 6.5 40 256 qam 7
3 195000000 6.6 40 256 qam 8
4 203000000 6.5 40 256 qam 9
5 211000000 6.1 40 256 qam 10
6 219000000 6.1 40 256 qam 11
7 227000000 5.8 40 256 qam 12
8 235000000 5.9 40 256 qam 13
9 243000000 5.9 40 256 qam 14
10 251000000 6.3 40 256 qam 15
11 259000000 6 40 256 qam 16
12 267000000 6 40 256 qam 17
13 275000000 6.4 40 256 qam 18
14 283000000 6.8 40 256 qam 19
15 291000000 6.9 40 256 qam 20
16 299000000 7.1 40 256 qam 21
17 307000000 7.4 40 256 qam 22
18 315000000 7.5 40 256 qam 23
19 323000000 7.5 40 256 qam 24
20 443000000 6 40 256 qam 25
21 451000000 6 40 256 qam 26
22 459000000 6 40 256 qam 27
23 467000000 6.3 40 256 qam 28
24 475000000 6.3 40 256 qam 29


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.9 236 0
2 Locked 40.3 8 0
3 Locked 40.3 7 0
4 Locked 40.3 5 0
5 Locked 40.9 6 0
6 Locked 40.3 7 0
7 Locked 40.3 9 0
8 Locked 40.9 9 0
9 Locked 40.3 8 0
10 Locked 40.3 8 0
11 Locked 40.9 14 0
12 Locked 40.9 6 0
13 Locked 40.3 9 0
14 Locked 40.9 8 0
15 Locked 40.9 10 0
16 Locked 40.9 14 0
17 Locked 40.3 19 0
18 Locked 40.9 12 0
19 Locked 40.3 21 0
20 Locked 40.3 139 0
21 Locked 40.3 203 0
22 Locked 40.3 229 0
23 Locked 40.3 157 0
24 Locked 40.3 162 0
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
341 Views
Message 3 of 7
Flag for a moderator

Re: Speed drop



Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400024 4.425 5120 64 qam 2
2 25799986 4.425 5120 64 qam 4
3 32599996 4.425 5120 64 qam 3
4 46200009 4.425 5120 64 qam 1


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
0 Kudos
Reply
Highlighted
  • 11.8K
  • 1.08K
  • 2.56K
Alessandro Volta
328 Views
Message 4 of 7
Flag for a moderator

Re: Speed drop

Stats look fine

Are you experiencing the problems whilst connected wired or wirelessly?
If wireless test wired directly to the Hub.

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
324 Views
Message 5 of 7
Flag for a moderator

Re: Speed drop

Iam on wired connection

but surly all them errors from the log mean something  ??

i have even coneccted by straight my computer and the speeds the same 

 

0 Kudos
Reply
Highlighted
  • 11.8K
  • 1.08K
  • 2.56K
Alessandro Volta
318 Views
Message 6 of 7
Flag for a moderator

Re: Speed drop

Yes they do,

The DHCP errors are just the way VM handles DHCP leases, by ignoring the Hub's DHCP lease requests whilst in the RENEW state and only responding to DHCP requests when the Hub goes into the REBIND state when the Hub has to provide some validation info to obtain a DHCP lease and hence an IP address. This is a security feature and does not affect performance in any way.

The No Ranging Response received is when the Hub has not received a response from a Ranging request which the Hub sends every 30secs.
This is usually due to (but not exclusive) to a bit of noise on the upstream which prevents the Ranging Request from reaching the Hub. As the ranging Requests are sent every 30secs. it is not unusual for the odd one or two to get lost in transit. As you are getting an odd T3 every 5 days or so this will be nowhere near the frequency to indicate a significant problem.It is you get a lot of T3s in short succession then you will have a problem.

The Sync Timing Synchronisation error is when the Hub doesn't receive a SYNC message which the CMTS broadcasts at least every 200ms to synchronise the Hub's and CMTS clocks. Without the clocks being in SYNC the Hub cannot lock onto the QAM clock so the Hub goes into partial service mode. If the Hub picks up the next SYNC message 200ms later then everything goes back to normal.So, as with the T3 errors the odd missing SYNC will not affect performance and shouldn't be noticeable unless you are using a real time app such as VOIP when you might notice a minor blip.

In conclusion, whilst there are errors in the logs they are not frequent enough to be service affecting.

EDIT

What device did you do the direct connection with?
Has it got a Gigabit NIC?

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
293 Views
Message 7 of 7
Flag for a moderator

Re: Speed drop

Thanks for your help

I have it sorted now feel a idiot  tho cable been usinging was damaged 😐
New cable back to speed  😁

0 Kudos
Reply