Menu
Reply
Highlighted
  • 13
  • 0
  • 0
Tuning in
178 Views
Message 1 of 4
Flag for a moderator

post rs errors & Lost MDD Timeout and T3 timeouts

Hi,

since last week I've been experiencing problem with my connection. had a look at the stats and noticed lots of post rs errors and also a Lost MDD Timeout. Posting below. Is this something to be worried about? Can one of the support guys please check it from their end?

 

28/04/2020 19:39:47Warning!Lost MDD Timeout;CM-CM-QOS=1.1;CM-VER=3.0;
28/04/2020 19:34:56criticalNo Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0;
28/04/2020 19:16:8Warning!Lost MDD Timeout;CM-QOS=1.1;CM-VER=3.0;
28/04/2020 13:48:9criticalNo Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels

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

14110000005.840256 qam1
24190000005.540256 qam2
34270000005.840256 qam3
44350000005.840256 qam4
54430000005.540256 qam5
64510000005.540256 qam6
74590000005.940256 qam7
84670000005.840256 qam8
94750000005.340256 qam9
104830000005.340256 qam10
114910000005.440256 qam11
12499000000540256 qam12
135070000004.540256 qam13
145150000004.540256 qam14
15523000000540256 qam15
165310000004.840256 qam16
175390000004.340256 qam17
185470000004.140256 qam18
195550000004.640256 qam19
205630000004.440256 qam20
21571000000440256 qam21
225790000004.440256 qam22
235870000004.540256 qam23
245950000003.940256 qam24



Downstream bonded channels

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

1Locked40.3795484
2Locked40.37969790
3Locked40.394871014
4Locked40.91134248773
5Locked40.3932552
6Locked40.91092816
7Locked40.91177912
8Locked40.3122033
9Locked40.9159760
10Locked40.91534026
11Locked40.91698534
12Locked40.31937519
13Locked40.3203780
14Locked40.9253980
15Locked40.32590412
16Locked40.92767017
17Locked40.9262350
18Locked40.3366140
19Locked40.9394511
20Locked40.3395251
21Locked40.94689911
22Locked40.94988130
23Locked40.95340719
24Locked40.36407112

 

thanks a dozen!

0 Kudos
Reply
Highlighted
  • 15.53K
  • 1.62K
  • 2.65K
Very Insightful Person
Very Insightful Person
173 Views
Message 2 of 4
Flag for a moderator

Re: post rs errors & Lost MDD Timeout and T3 timeouts

Post the upstream data too.

PostRS errors are not good and might indicate noise. To double check, do a quick check that all of your coax connections are in nice and "finger" tight at the Hub and wall box and at any splitters/attenuators/etc with no “unterminated loose ends, and that the internal wiring is ok with no kinking or chaffing. Also check that all looks good with the outside cabling and wall box.

Then.... reboot the Hub and check that the RS error counts have all reset to 0. Then check in there every hour or so and see if they are starting to reappear again.

Report back.

--------------------
John
--------------------

My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
Highlighted
  • 13
  • 0
  • 0
Tuning in
119 Views
Message 3 of 4
Flag for a moderator

Re: post rs errors & Lost MDD Timeout and T3 timeouts

Thanks for your advice jbrennand.

As per your advice I have checked the cabling and reset the hub. 21h since reboot and no post RS errors so far:

Downstream bonded channels

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

14110000005.840256 qam1
24190000005.540256 qam2
34270000005.640256 qam3
44350000005.640256 qam4
54430000005.440256 qam5
64510000005.540256 qam6
74590000005.840256 qam7
84670000005.640256 qam8
94750000005.140256 qam9
104830000005.140256 qam10
114910000005.340256 qam11
12499000000540256 qam12
135070000004.440256 qam13
145150000004.440256 qam14
155230000004.940256 qam15
165310000004.840256 qam16
175390000004.340256 qam17
185470000004.140256 qam18
195550000004.540256 qam19
205630000004.440256 qam20
21571000000440256 qam21
225790000004.340256 qam22
235870000004.540256 qam23
245950000003.940256 qam24



Downstream bonded channels

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

1Locked40.3670
2Locked40.9640
3Locked40.9870
4Locked40.3760
5Locked40.9980
6Locked40.91040
7Locked40.9820
8Locked40.31130
9Locked40.91500
10Locked40.31490
11Locked40.91420
12Locked40.91800
13Locked40.32310
14Locked40.92750
15Locked40.32650
16Locked40.33380
17Locked40.33380
18Locked40.34030
19Locked40.34750
20Locked40.95190
21Locked40.35380
22Locked40.96190
23Locked40.97000
24Locked40.37980

 

Uplink stats:

pstream bonded channels

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

1537000344.35512064 qam10
2393999934.15512064 qam12
3461999884.35512064 qam11
4603000174.35512064 qam9



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Another T3 timeout this morning though. Is this something to check further?

30/04/2020 06:59:57criticalNo Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 1.3K
  • 184
  • 618
Very Insightful Person
Very Insightful Person
113 Views
Message 4 of 4
Flag for a moderator

Re: post rs errors & Lost MDD Timeout and T3 timeouts

That's looking a lot healthier. The occasional T3 error is fine, as is the occasional MDD Timeout or Sync loss, it's only when you get a number of them in succession over a prolonged period of time that you need to be concerned. One every few days is fine.

0 Kudos
Reply