Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[NEXUS2345]

In regards to me not uploading to MDWS as of current, I am currently away on holiday and so the only computer I have set up to upload is currently offline, as well as my HG612 unplugged in case of a lightning strike...

[Weaver]

Snapshot of the three lines on 3 Aug

=== Line 1: ===
BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync
BRAS=2232Kb/s FTR=1817Kb/s MSR=2272Kb/s ServOpt=1 I/L=I
Up Sync=515Kb/s LoopLoss=42.9dB SNR=5.8dB ErrSec=0 HECErr=0 Cells=0
Down Sync=2531Kb/s LoopLoss=66.2dB SNR=1.7dB ErrSec=0 HECErr=N/A Cells=0
===

=== Line 3: ===
BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync
BRAS=2223Kb/s FTR=1817Kb/s MSR=2272Kb/s ServOpt=1 I/L=I
Up Sync=402Kb/s LoopLoss=43.1dB SNR=5.8dB ErrSec=0 HECErr=0 Cells=0
Down Sync=2521Kb/s LoopLoss=66.3dB SNR=2.5dB ErrSec=1 HECErr=N/A Cells=0
===

=== Line 4: ===
BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync
BRAS=2364Kb/s FTR=2278Kb/s MSR=2848Kb/s ServOpt=1 I/L=I
Up Sync=409Kb/s LoopLoss=43.5dB SNR=5.5dB ErrSec=0 HECErr=0 Cells=0
Down Sync=2681Kb/s LoopLoss=66.6dB SNR=1.5dB ErrSec=0 HECErr=N/A Cells=0
===

[aesmith]

I wonder why your snapshots don't include ILQ.  I'm assuming these are from clueless via the "Sync Status" option.   The equivalent from my line includes a line which might read "THIS LINE IS STABLE AND WELL WITHIN ERROR/RETRAIN LIMITS FOR THE CHOSEN SERVICE OPTION (ILQ=GREEN)" if all is going well.

By the way are those real MSR/FTR figures for lines 1 and 3?

[Weaver]

I've never seen the ILQ thing in clueless. How odd.

The MSR / FTR figures are just as clueless reports them, and have been nonsensical for an age. I would rather like to get the FTRs fixed.

The >2800 downstream sync rate for line four would be from last December I suspect.

[aesmith]

If you think the sync rates might improve in cooler weather, then it might be an idea to get the two MSR/FTRs reset at that time.  You should be able to initiate that from the "SNR Reset" button on Clueless, at least I have done so on my 20CN line.   

[Weaver]

I used the SNR reset feature, on a couple of occasions since last December, but it seemed to make no difference to the MSR/FTR issue. It simply set the target SNRM, as it should, but did no more than that.

[aesmith]

I wonder how you do it on 21CN then.   For my line the only option is that reset, which sets it back to 6dB/Fast and restarts the learning process.   When I selected the option it logged the following ...

"Test SNR reset::SNR reset initiated which will enable the line to reach optimum performance, service interruption may be experienced during this period."

Just a random thought, I wonder if on 21CN it only relearns if you reset back to the default 6dB?

[Weaver]

The thing is, a few days ago, I did an SNR reset and set line 3 back to 6 dB downstream target SNRM. And that hasn't fixed the MSR / FTR, so it remains a mystery. One for AA staff I think.

If some bad line fault were to develop, I (or is it "AA and I"?) would not get the "benefit" of a quotable FTR-breach at the correct level.

It's very weird - I don't understand why there's the difference between lines 3 and 4. Line 4 behaved as normal and increased its MSR when I converted to 21CN / ADSL2+ last December. Note how the (rung) value 2272 (from the 20CN days) has just got jammed into the MSR fields for lines 1 and 3, and has, it seems, become detached from the updating process which would normally be expected to overwrite it.

[aesmith]

I guess it would be a question for A&A.   Not that it helps but after I did the SNR reset here the MSR/FTR changed from the preexisting 2272/1817 figures, to 288/288 which remained until the end of the 10 days.