cancel
Showing results for 
Search instead for 
Did you mean: 

Intermittent T3 Timeouts

DeadSignal
Tuning in

Hi all,

TL;DR - Shibboleet help please! Am I being a muppet or is this upstream?

For background - I'm a Linux analyst and CCNA qualified but know very little about DOCSIS.

I'm getting occasional T3 (and previous T4) dropouts plus a bunch of Post-RS errors. I understand this is bad! 🤔

VM Superhub 3.0
Hardware version : 11
Software version : 9.1.2109.200
Last reboot: 06/02/2023 ~18:40

My first concern is that the superhub was delivered without a coax cable so currently have no primary isolator (I have the PSU into the VM wall-box setup... I'd love to know how this works!)

I'm currently using about 5m of CT100 cable, kept from last year's VM subscription.

Secondly, I noted a kernel panic in the logs when I first booted it! This has since disappeared.

Here's the log. 23:43 was when my Twitch broadcast dropped for a few seconds:

Time Priority Description

11/02/2023 01:25:37noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2023 23:43:22Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2023 23:43:17criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2023 23:43:16Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2023 23:43:16criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2023 13:11:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/02/2023 15:49:5ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2023 18:43:51noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Up/Down metrics in comments due to character limit.

TIA. Rich.

13 REPLIES 13

DeadSignal
Tuning in

Here's the Metrics:

Downstream:

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1426250000534256 qam9
2362250000434256 qam1
33702500004.434256 qam2
43782500004.534256 qam3
53862500004.534256 qam4
63942500004.934256 qam5
7402250000534256 qam6
8410250000534256 qam7
9418250000534256 qam8
10434250000534256 qam10
114422500005.334256 qam11
124502500005.134256 qam12
134582500004.934256 qam13
14466250000534256 qam14
154742500004.834256 qam15
164822500004.634256 qam16
174902500004.534256 qam17
184982500004.434256 qam18
195062500004.334256 qam19
205142500004.134256 qam20
21522250000434256 qam21
225302500003.934256 qam22
23538250000434256 qam23
245462500003.934256 qam24

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked34.41549396519
2Locked34.41821676062
3Locked34.33462946061
4Locked34.32808155980
5Locked34.42845936431
6Locked34.91796846656
7Locked34.41666456647
8Locked34.42634896408
9Locked34.41589906862
10Locked34.91071506441
11Locked34.9981956398
12Locked34.42019846314
13Locked34.31934196179
14Locked34.41359156478
15Locked34.91507256554
16Locked34.91557106611
17Locked34.42468396512
18Locked34.31416116566
19Locked34.31859196557
20Locked34.42267856648
21Locked34.43412026559
22Locked34.32909006489
23Locked34.41898016580
24Locked34.41160166531

 

Upstream:

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14620000036512064 qam3
23939996536512064 qam4
36029995135.8512064 qam1
45369997136512064 qam2

 

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0010
4ATDMA0000

 

Possibly the cable you're using is not adequate for cable internet, which is hugely vulnerable to radio interference if the wrong cables are used.  VM normally use their own triple shielded  RG6 for that reason.  I'd suggest you're looking at booking a £25 non-fault call out to have the connection looked at, the hub connected with the right cable, and SNR checked.

Thanks for the info.

Do you have the specs for this cable?

Standard RG6 is single aluminium shielded. That's why I've always used CT100. Same impedance, same attenuation but duofoil shielded and harder to kink.

Quick update. 

I've put it on a 0.5m cable cut from a fresh reel and I'll contact support on Monday to get a VM supplied one.

If the PSU into the VM wall box is like this, it is an RFoG / FTTP area.

The PSU via the coax is powering an ONU in the external OMNI box. 

Client62_0-1676127128217.png

Client62_1-1676127291147.png

 

 

Nice one. Thank you @Client62.

That's my exact setup. 

I guessed it was FTTP

I assume the external piece of kit is effectively an ER fibre to RF modem.

Seems kinda mad that it isn't simply converted to copper ethernet.

Thanks for the details. I'm going to have some fun on Google this afternoon 😁

I agree with the comments about coax cable quality being suspect for the following reasons ...

We are an RFoG area with a 10dB attenuator on the Hub3's coax - our Downstream Power levels are about 8 dB below those shown above.

But our Hub3's Downstream SNR figures are higher (read better) , and the number of Pre RS & Post RS errors are minimal.

If the Post RS (Reed-Solomon) i.e. the uncorrectable errors can be sorted a smoother connection should be possible.

PS ... for primary isolation, the 50+ meters of fibre cable will see to that.

I think you may both be bang on about the cable.

4h after swapping to a short cable - Zero Post RS errors and zero warnings.

I'll keep an eye on it for a couple of days and do some reading so that I can understand the power and SNR thresholds.

To be fair, I should have just run a longer ethernet cable in the first place, I was just being lazy 😁

Thank you very much for the docs and technical info.