Menu
Reply
  • 1
  • 0
  • 0
ryanbate
Joining in
198 Views
Message 1 of 4
Flag for a moderator

Connection failing on heavy uploads

Hi

Looking for advice from any community members that can advise on levels and such like and (if available, eventually) any VM staff who can do the same.

We have M200 broadband having been successively upgraded over the years in speed. Modem is a Superhub 2ac which is used in modem mode with a separate router.

In performing large cloud backups I am noticing that after a few minutes of sustained upload (effectively maxing out the speed allowed) the connection completely fails. When it does this, the only remedy is to restart the Superhub and then all is well assuming that the upload does not resume - if it does, it fails again within around 20-30 minutes.

I have looked through the operation log on the SH and cannot see only see messages that I believe relate to it booting up and establishing connection again.

Screen Shot 2019-10-08 at 14.38.46.png

This graph is taken from my router and shows throughput as recorded by it - green for download and blue for upload. You can see that the spikes in upload correspond with when the traffic drops to zero. 

Data from the SH status pages and logs  are here:

 

Spoiler


Information
Cable Modem EuroDOCSIS 3.0 Compliant
Serial Number XXXXXXXXXXXX
Boot Code Version PSPU-Boot 1.0.20.1391
Software Version V2.01.15
Hardware Version 1.03
CA Key Installed

 

 

Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz) 283000000 Locked
Ranged Upstream Channel (Hz) 46200000 Success
Provisioning State OK Operational


Downstream
DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 283000000 267000000 275000000 291000000 299000000 307000000 315000000 323000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked Locked Locked
Channel ID 19 17 18 20 21 22 23 24
Modulation 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM
Symbol Rate (Msym/sec) 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000
Interleave Depth 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 I=12
J=17
Power Level (dBmV) 7.13 6.58 6.85 7.50 7.78 7.87 8.01 8.01
RxMER (dB) 38.61 38.26 38.26 38.61 38.98 38.26 37.94 39.40
Pre RS Errors 277 292 288 929 329 919 322 950
Post RS Errors 275 290 288 929 329 919 322 950


Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 2.0 2.0 2.0
Channel ID 1 4 3 2
Frequency (Hz) 46200000 25800000 32600000 39400000
Ranging Status Success Success Success Success
Modulation 64QAM 64QAM 64QAM 64QAM
Symbol Rate (Sym/sec) 5120000 5120000 5120000 5120000
Mini-Slot Size 2 2 2 2
Power Level (dBmV) 42.50 42.50 42.50 42.50
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 0 0 0 0
T4 Timeouts 0 0 0 0


Upstream Burst
Req
(1) Init Maint
(3) Per Maint
(4) Adv Short
(9) Adv Long
(10) Adv UGS
(11)
Modulation Type 16QAM QPSK 16QAM 64QAM 64QAM 16QAM
Differential Encoding OFF OFF OFF OFF OFF OFF
Preamble Length 36 384 384 64 64 64
Preamble Value Offset 396 6 6 396 396 396
FEC Error Correction (T) 0 5 5 7 14 5
FEC Codeword Information Bytes (K) 16 34 34 88 220 86
Maximum Burst Size 0 0 0 3 0 55
Guard Time Size 22 48 48 22 22 22
Last Codeword Length Fixed Fixed Fixed Shortened Shortened Shortened
Scrambler On/Off ON ON ON ON ON ON

General Configuration
Network Access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode EuroDOCSIS 3.0
Config File
Primary Downstream Service Flow
SFID 210
Max Traffic Rate 230000061 bps
Max Traffic Burst 42600 bytes
Min Traffic Rate 0 bps
Primary Upstream Service Flow
SFID 209
Max Traffic Rate 22000061 bps
Max Traffic Burst 42600 bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 42600 bytes
Scheduling Type Best Effort

Network Log
First Time Last Time Priority Error Number Description
08/10/2019 13:29:12 GMT 08/10/2019 13:29:12 GMT Error (4) 68000407 TOD established
Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully
08/10/2019 07:58:05 GMT 08/10/2019 07:58:05 GMT Error (4) 68000407 TOD established
08/10/2019 07:57:47 GMT 08/10/2019 07:57:47 GMT Notice (6) 84000510 Downstream Locked Successfully
08/10/2019 07:57:42 GMT 08/10/2019 07:57:42 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
08/10/2019 07:57:22 GMT 08/10/2019 07:57:22 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
08/10/2019 07:57:02 GMT 08/10/2019 07:57:02 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
08/10/2019 07:56:42 GMT 08/10/2019 07:56:42 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
07/10/2019 19:55:35 GMT 07/10/2019 19:55:35 GMT Error (4) 68000407 TOD established
Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully
07/10/2019 18:48:10 GMT 07/10/2019 18:48:10 GMT Error (4) 68000407 TOD established
07/10/2019 18:47:55 GMT 07/10/2019 18:47:55 GMT Notice (6) 84000510 Downstream Locked Successfully
07/10/2019 18:47:49 GMT 07/10/2019 18:47:49 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
07/10/2019 18:47:29 GMT 07/10/2019 18:47:29 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
07/10/2019 18:47:09 GMT 07/10/2019 18:47:09 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
07/10/2019 18:46:49 GMT 07/10/2019 18:46:49 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
07/10/2019 18:45:59 GMT 07/10/2019 18:45:59 GMT Warning (5) 84020200 Lost MDD Timeout
07/10/2019 18:45:59 GMT 07/10/2019 18:45:59 GMT Warning (5) 84020200 Lost MDD Timeout
07/10/2019 18:45:59 GMT 07/10/2019 18:45:59 GMT Warning (5) 84020200 Lost MDD Timeout
07/10/2019 18:45:59 GMT 07/10/2019 18:45:59 GMT Warning (5) 84020200 Lost MDD Timeout

I can see that my router is not breaking a sweat from the traffic (it's a Mikrotik RB3011UIAS RM - massive overkill) and that the connection comes back without resetting that or having to interact with it in any way.

I can see the upload speed limit is currently set to ~22Mbps which was completely unbeknown to me so perhaps this is why this issue is only now starting to become apparent if there are wonky levels. Or potentially that given the SH2ac is an older piece of kit it may not be up to the job for this kind of upload speed?

Any thoughts or insight would be appreciated.

Thanks

 

0 Kudos
Reply
  • 6.05K
  • 466
  • 1.01K
Tudor
Hero
173 Views
Message 2 of 4
Flag for a moderator

Re: Connection failing on heavy uploads

Stats look ok, but T4 timeouts in the log are bad. Possibly a noise ingress problem in your local area. Phone customer services and see if there is a reported problem. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos
Reply
  • 876
  • 43
  • 72
Forum Team
Forum Team
96 Views
Message 3 of 4
Flag for a moderator

Re: Connection failing on heavy uploads

Hi ryanbate,

 

Sorry to hear that your broadband connection is failing on heavy uploads.

 

Just looking the details already provided, I cannot see any errors on our end. 

 

Is the connection failing in general or just when your conducting heavy uploads?

 

Please give us more information so we can help.

 

Regards,

 

Lisa

0 Kudos
Reply
  • 4.47K
  • 302
  • 749
Roger_Gooner
Community elder
85 Views
Message 4 of 4
Flag for a moderator

Re: Connection failing on heavy uploads

In view of the wild swings in speeds I'm inclined to think that this is a network issue, quite possibly within the hub site. If so a VM technician won't be able to fix it.

--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG1008D 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection
0 Kudos
Reply