![]() |
Re: Post RS Errors
Quote:
|
Re: Post RS Errors
Quote:
|
Re: Post RS Errors
Grrr, why does this always happen just before a technician is about to come. Looks as though there was a brief outage around 7:30pm (was out at the time) according to the TBB graph.
https://www.cableforum.co.uk/images/local/2015/08/3.png Upstream power levels have now significantly reduced from the 54dBmv they were. US-1 US-2 US-3 US-4 Channel Type 2.0 N/A N/A 2.0 Channel ID 50 N/A N/A 51 Frequency (Hz) 39400000 N/A N/A 32600000 Ranging Status Success N/A N/A Success Modulation 16QAM N/A N/A 16QAM Symbol Rate (Sym/sec) 5120000 N/A N/A 5120000 Mini-Slot Size 4 N/A N/A 4 Power Level (dBmV) 40.71 N/A N/A 40.25 T1 Timeouts 0 0 0 0 T2 Timeouts 0 0 0 0 T3 Timeouts 1 0 0 0 T4 Timeouts 0 0 0 0 DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8 Frequency (Hz) 299000000 267000000 275000000 283000000 291000000 307000000 315000000 323000000 Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked Locked Locked Channel ID 13 9 10 11 12 14 15 16 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) 0.35 -0.20 -0.00 0.19 0.18 0.61 0.66 0.67 RxMER (dB) 36.39 36.39 36.17 36.39 36.84 36.84 36.84 36.39 Pre RS Errors 792 1287 694 472 617 364 477 504 Post RS Errors 359 695 211 79 265 68 193 193 Network Log First Time Last Time Priority Error Number Description 21/07/2015 18:32:12 GMT 21/07/2015 18:32:12 GMT Error (4) 68000407 TOD established 21/07/2015 18:31:58 GMT 21/07/2015 18:31:58 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:50 GMT 21/07/2015 18:31:50 GMT Notice (6) 84000510 Downstream Locked Successfully 21/07/2015 18:31:45 GMT 21/07/2015 18:31:45 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:43 GMT 21/07/2015 18:31:43 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:43 GMT 21/07/2015 18:31:43 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:41 GMT 21/07/2015 18:31:41 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted 21/07/2015 18:31:41 GMT 21/07/2015 18:31:41 GMT Critical (3) 82000300 Ranging Request Retries exhausted 21/07/2015 18:31:41 GMT 21/07/2015 18:31:41 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted 21/07/2015 18:31:41 GMT 21/07/2015 18:31:41 GMT Critical (3) 82000300 Ranging Request Retries exhausted 21/07/2015 18:31:39 GMT 21/07/2015 18:31:39 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:39 GMT 21/07/2015 18:31:39 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:37 GMT 21/07/2015 18:31:37 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:37 GMT 21/07/2015 18:31:37 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:35 GMT 21/07/2015 18:31:35 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:34 GMT 21/07/2015 18:31:34 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:33 GMT 21/07/2015 18:31:33 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:32 GMT 21/07/2015 18:31:32 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:31 GMT 21/07/2015 18:31:31 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 21/07/2015 18:31:30 GMT 21/07/2015 18:31:30 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out Now whether getting the CEO office on to the case has kicked networks butts into fixing it or whether its coincidental, I don't know. Have to see what the technician can find out tomorrow. Edit: Looking at the My Virgin Media page, the technician appointment looks as though its been cancelled, as its no longer showing. I'm going to have to ring the CEO office tomorrow to find out whats going on. |
Re: Post RS Errors
From the BQM, there seems to be a low level of constant noise. These are the red bits at the top which denote lost packets on the BQM round trip. If that noise was on the upstream, it could account for the T3 events and eventually the reboot.
The snapshot log you provided shows nothing alarming. If the BQM has stopped showing red at the top then whatever it was might have been cured. I hope so. |
Re: Post RS Errors
yup, I bet the tech comes out tomorrow and it is a courtesy visit. He'll know they have fixed it and is coming out to kiss some ass and make sure everything is ok.
Edit: just red your modified post. Tech visits are cancelled when the fault is logged as being fixed so as far as VM are concerned it is fixed (which is certainly looks like from your power levels) |
Re: Post RS Errors
Hmmm, rebooted the SH yesterday and I've had no Post RS errors until now. Stats are all good and it doesn't appear to be noticeably affecting the connection, so do I just ignore it or carry on chasing up the complaint?
DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8 Frequency (Hz) 299000000 267000000 275000000 283000000 291000000 307000000 315000000 323000000 Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked Locked Locked Channel ID 13 9 10 11 12 14 15 16 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) 0.40 -0.28 -0.17 0.19 0.24 0.62 0.64 0.70 RxMER (dB) 36.39 36.39 36.17 36.17 36.84 36.84 36.84 36.61 Pre RS Errors 10286 8331 11756 7344 7207 6960 6939 7343 Post RS Errors 4180 940 4409 3347 4250 4286 4297 4788 US-1 US-2 US-3 US-4 Channel Type 2.0 N/A N/A 2.0 Channel ID 50 N/A N/A 51 Frequency (Hz) 39400000 N/A N/A 32600000 Ranging Status Success Other Other Success Modulation 16QAM N/A N/A 16QAM Symbol Rate (Sym/sec) 5120000 N/A N/A 5120000 Mini-Slot Size 4 N/A N/A 4 Power Level (dBmV) 40.50 N/A N/A 40.00 T1 Timeouts 0 0 0 0 T2 Timeouts 0 0 0 0 T3 Timeouts 0 0 0 0 T4 Timeouts 0 0 0 0 |
Re: Post RS Errors
If the post-RS errors are rising in normal use, then you have a fault, imo.
|
Re: Post RS Errors
Quote:
|
Re: Post RS Errors
But are they rising in normal operation?
|
Re: Post RS Errors
if it ain't broken don't fix it
|
Re: Post RS Errors
Quote:
|
Re: Post RS Errors
It means, imo, that there is occasional noise somewhere on the downstream if those errors are increasing without a reboot having occurred.
|
Re: Post RS Errors
However, that can be normal and not necessarily impactful.
|
Re: Post RS Errors
I disagree, though I know what you mean. There should be NO lost data packets at the CPE.
|
Re: Post RS Errors
You are correct, there should be but in the real world, it does sometimes happen. How often it happens is what really matters.
Or rather, whether your service is being affected in a noticeable way is what matters. |
| All times are GMT +1. The time now is 16:20. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum