Menu
Reply
  • 2
  • 0
  • 0
ke1tha1ng3
Joining in
75 Views
Message 1 of 5
Flag for a moderator

Network log errors - slow connection

Hi.

In the last few days I have noticed a slowing down of my network connection.

The router network log is full of this error ...

Date Time Error Number Error Description

02/01/201715:07:50 GMT84020200Lost MDD Timeout
02/01/201715:08:16 GMT84020200Lost MDD Timeout
02/01/201715:07:50 GMT84020200Lost MDD Timeout
02/01/201715:08:16 GMT84020200Lost MDD Timeout

 

Here are my other logs which I know you will find useful...

Downstream   DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)323000000267000000275000000283000000291000000299000000307000000315000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID12567891011
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)-1.47-1.19-1.11-1.09-1.12-1.30-1.40-1.35
RxMER (dB)37.0936.3937.0936.3937.0937.3637.0937.36
Pre RS Errors5781285446685305302308304
Post RS Errors294276290304296295286298

 

Upstream   US-1 US-2 US-3 US-4

Channel Type2.0N/AN/A2.0
Channel ID50N/AN/A49
Frequency (Hz)39400000N/AN/A46200000
Ranging StatusSuccessOtherOtherSuccess
Modulation64QAMN/AN/A64QAM
Symbol Rate (Sym/sec)5120000N/AN/A5120000
Mini-Slot Size4N/AN/A4
Power Level (dBmV)38.00N/AN/A38.50
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts1000
T4 Timeouts0000

 

Network Log

First TimeLast TimePriorityError NumberDescription
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout
02/01/2017 15:10:14 GMT02/01/2017 15:10:14 GMTWarning (5)84020200Lost MDD Timeout

 

Any ideas what is happening here Guys?

Oh and Happy New Year to you all!

0 Kudos
Reply
  • 9.02K
  • 760
  • 1.88K
Superuser
Superuser
68 Views
Message 2 of 5
Flag for a moderator

Re: Network log errors - slow connection

Your stats are fine.

The network logs are full and the last entry is repeating itself, a known bug in the SH firmware.

I would clear the logs and reboot the hub. If the lost MDDs keep happening then it  would suggest a downstream impairment.

Are you connecting with a wired or wireless device?. If wireless try a wired device.

Are you experiencing slower wired speeds all the time or only during evening peak periods?

0 Kudos
Reply
  • 2
  • 0
  • 0
ke1tha1ng3
Joining in
65 Views
Message 3 of 5
Flag for a moderator

Re: Network log errors - slow connection

Hi and thanks for the quick response!

I have tried a warm and cold reboot of the router and the logs fill with the same error after.

I have both wireless and wired connections and they all suffer from the same slowing down issue.

The wired speeds are showing the same slow down all the time.

It does not appear to change during peak and off peak times.

0 Kudos
Reply
  • 9.02K
  • 760
  • 1.88K
Superuser
Superuser
53 Views
Message 4 of 5
Flag for a moderator

Re: Network log errors - slow connection

If the lost MDDs are still frequent sfter you cleared the logs then it does look like a downstream problem.

You will need to contact VM to take a closer look, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.

0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
41 Views
Message 5 of 5
Flag for a moderator

Re: Network log errors - slow connection

Hi ke1tha1ng3, 

 

Thank you for posting! I am sorry to hear about your network log errors and slow connection, I apologise for any inconvenience caused.

I have run some checks from here and I noticed a number of time outs inside the Hubs logs, I would like to arrange for an engineer to attend and investigate things for you. I will send you a PM (purple envelope at the top) detailing what's required to proceed with making the booking.

Please respond to me there and I'll get this sorted for you.

Take care, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply