Thread: 50M Post RS Errors
View Single Post
Old 19-03-2015, 16:09   #53
Kushan
FORMER Virgin Media Staff
 
Join Date: Dec 2010
Location: Warrington
Posts: 4,737
Kushan has a bronzed appealKushan has a bronzed appeal
Kushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appeal
Re: Post RS Errors

Quote:
Originally Posted by Jon22 View Post
Tech has been and gone, unsurprisingly couldn't find anything wrong. He did ring up his team (network engineers?) and they couldn't find anything wrong. What they could see matched what was being reported, said Cardi(?) was at 0%. Re-booted the SH. So looks as though I'll just have to leave it unless things do start causing issues.

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) 2.67 2.68 2.63 2.84 2.86 2.99 3.03 3.28
RxMER (dB) 34.63 34.63 34.63 34.63 34.77 34.77 34.63 34.48
Pre RS Errors 388 423 452 382 326 334 353 1120
Post RS Errors 0 0 0 0 0 0 0 0
All your stats look spot on right now. CARDIE (AFAIK that's how it's spelled, cannot remember what it stands for) is the tool they use to gauge noise on your cable. 0% is a good thing generally, but that can be measured over different periods. 0% over the last hour doesn't mean much, 0% over 24hours is better.

The way the cable tech works, is there's expected to be a certain level of error - it happens, even on a good day. Sometimes you can correct that error (known as FEC - Forward Error Correction), sometimes you can't (FEC Errors) and the data has to be retransmitted - again, this is normal and will happen on occasion on even good lines. The more FEC Errors, the higher the score gets.

Likewise, the lines can automatically drop down to different modulations that are less affected by noise. QAM64 might drop to QAM16, for example, which has a lot less bandwidth but some bandwidth is better than none at all (This is why "slow speeds" doesn't always mean congestion, it could mean there's noise on the line killing the modulation, so everyone has less bandwidth to share). If that happens, the score goes up. If it hits QPSK, it's even worse.

I've seen CARDIE scores of 70%+ and that generally means everything's ****ed. If I recall correctly, anything above 30% over a 24 hour period needs to be raised to networks.

Oddly enough, when the entire line is down, CARDIE seems to report exactly 25%. I have no idea why.
Kushan is offline   Reply With Quote