cancel
Showing results for 
Search instead for 
Did you mean: 

Deciphering line reports

Dave_H
Newbie
Posts: 6
Registered: 10-08-2007

Deciphering line reports

Hi,

I have been having problems with connection to Metronet for over a week and recently requested my line to be checked (I have been connected for over a year with few problems).

My router continually connects, runs for a few seconds (sometimes minutes) then disconnects. Occasionally I have managed an hour or so uptime and yesterday, for the first time in 8 days I managed to remain connected from
08:30 to 16:23 and then the problem returned.

Can anyone decipher the following for me in 'plain english' ? Thanks

First the result of a line test analysis (Bearing in mind that my equipment starts up at 08:00 and shuts down at 23:00 and this test was apparently run at 03:23 i.e. when my equipment was powered off)

=========
2006-05-08
03:23:15
{agent name removed}
CSC Agent Assigned : Copper Line Test Analysis
Time out/premature termination.
TEST FAILURE - LTS Failure - communications failure

Regards,
{agent name removed}
========

I read this as ' tried to reach your equipment and failed' , which is no surprise as my equipment is powered down.
Am I right ?


Second the result of an xDSL Status Check Analysis once again run in the early hours of the morning
=========
2006-05-08
03:39:05
{agent name removed}
CSC Agent Assigned : xDSL Status Check Analysis
Not in synch - suggest cct reset and line test.
Circuit Information
Circuit NOT In Sync

Upstream xDSL Link Info
Loop Loss n/a dB
Cell Count 0

Downstream xDSL Link Info
Loop Loss n/a dB
Cell Count 0
Copper Line Test Analysis
Test OK.
Diagnosis T005 : Line Test OK
MFL OK
Duration 30

Determine Algorithm Branch Analysis
No synch on a long line
One Shot Check Diagnosis
Final Test Outcome Inconclusive
Major Findings
Conclusion Inconclusive
=========

Which I read as ; can't find any equipment working on the line. Sent nothing up the line, got nothing back, can't work out any losses, but the line exists and appears ok (some sort of continuity check).

Am I barking up the wrong tree ?

============
I now have received the following message :
2006-05-08
03:46:20
{agent name removed}
CSC Agent Actioned : Dear {Me}
We have checked your line and no fault can be found with your service therefore I am passing the fault back to you for further checking and testing at your end.
.................(plus a lot of repeat stuff about checking my connections and liability if I want BT to check the line)
==============

I am not sure how much more I can do from my end. I have bought a new modem and professional filter (from adsl nation) and it has made no difference.
I only use the BT master socket and have no other equipment on the line barring my phone (but its removal makes no difference. Neither does direct connection from adsl modem to the master socket improve matters).

Would a request to Metronet for a test when my equipment is powered up be useful, or do I push for BT to test my line (and be prepared for a charge should there be no fault ) ?

I should point out that connectng to the BT test domain produces similar symptoms to Metronet, which I had thought at the beginning was conclusive of line problems rather than equipment failure but all this happened pretty close to the DNS changeover debacle.
6 REPLIES
N/A

Deciphering line reports

Hi.
What is the snr from your modem stats and if you keep an eye on it does it drop before you loose connection. Have you done all the other stuff like unplugging all phones skyboxes etc?
Is connection stats from your modem showing any errors?
Cheers
Jon
Dave_H
Newbie
Posts: 6
Registered: 10-08-2007

Deciphering line reports

snr shows up on my stats as anything from 54 to 99 for a connected line (but it won't stay connected for long) and 45 to 88 for an unconnected line. Doesn't seem to be much in it - not that I know what this is supposed to represent . The values in front of these numbers are usually something like;

Receive
13.4/9.52: 99
10.21/9.52: 95
12.5/9.52: 54
16.29/9.52: 45

I can't work out the relation of one to the other. These values were taken over a 10 minute spell just now (at 23:15).

AAL link stats and AAL5 Channel stats show discarded bytes and frames and CRC errors


Having said all that my modem is now up and has been connected for 6 minutes without breaking down (first time in 9 days it has stayed up for so long at this hour of the day).
N/A

Deciphering line reports

Hi.
Can you cut and paste the stats page please.
Cheers
Jon
Dave_H
Newbie
Posts: 6
Registered: 10-08-2007

Deciphering line reports

Here is the stats from earlier this evening, and thanks for any help you can offer here.

Interestingly I left my system up last night (normally it shuts down at 23:00 and restarts at 08:00) and my logs show I had a connection from around 00:30 to 10:30 in the morning, at which point normal 'non-service' was resumed.

The stats;
------------------------
Conexant AccessRunner PCI ADSL Modem Adapter Status
---------------------------------------------------

ADSL Line Not Connected
Line Rates: Not available

ADSL Modulation: T1.413 Issue 2

ATM Virtual Channel IDs: VPI: 0 VCI: 38

Physical Layer Stats: Receive Transmit
Noise Margin 10.92/ 8.14: 62 127.99/127.99: 0
Attenuation 63.98 31.50
Power -38

ATM Link Stats: Receive Transmit
Bytes 81166585 8285861
Cells 1531445 156337
Management Cells 0 0
CLP=0 Cells 1531445 0
CLP=1 Cells 0 156337
HEC Errors 0
Alignment Errors 0
Unroutable Cells 324327

AAL Link Stats: Receive Transmit
Good Bytes 21634704 4776336
Good Frames 68431 61636
Discarded Bytes 49612704
Discarded Frames 170041
CRC Errors 168613
Invalid Length Errors 1428
Timeout Errors 0

ATM Channel Stats: Receive Transmit VPI: 0 VCI: 38
Bytes 53 159
Cells 1 3
Mgmt Cells 0 0
CLP=0 Cells 1 0
CLP=1 Cells 0 3
HEC Errors 0
Alignment Errors 0
Unroutable Cells 0

AAL5 Channel Stats: Receive Transmit VPI: 0 VCI: 38
Good Bytes 48 0
Good Frames 1 3
Discarded Bytes 0
Discarded Frames 0
CRC Errors 0
Invalid Length Errors 0
Timeout Errors 0

Driver version - 6.1.2.007-CLN (20041001)
Dave_H
Newbie
Posts: 6
Registered: 10-08-2007

Deciphering line reports

.... and these are some 'connected' stats (which don't remain connected for long)

Conexant AccessRunner PCI ADSL Modem Adapter Status
---------------------------------------------------

ADSL Line Connected
Line Rates: Receive 576 kbps Transmit 288 kbps

ADSL Modulation: T1.413 Issue 2

ATM Virtual Channel IDs: VPI: 0 VCI: 38

Physical Layer Stats: Receive Transmit
Noise Margin 12.71/ 9.98: 66 127.99/127.99: 0
Attenuation 63.98 31.50
Power -38

ATM Link Stats: Receive Transmit
Bytes 24592 11448
Cells 464 216
Management Cells 0 0
CLP=0 Cells 464 0
CLP=1 Cells 0 216
HEC Errors 0
Alignment Errors 0
Unroutable Cells 8895

AAL Link Stats: Receive Transmit
Good Bytes 15648 1680
Good Frames 266 187
Discarded Bytes 6624
Discarded Frames 45
CRC Errors 45
Invalid Length Errors 0
Timeout Errors 0

ATM Channel Stats: Receive Transmit VPI: 0 VCI: 38
Bytes 0 53
Cells 0 1
Mgmt Cells 0 0
CLP=0 Cells 0 0
CLP=1 Cells 0 1
HEC Errors 0
Alignment Errors 0
Unroutable Cells 0

AAL5 Channel Stats: Receive Transmit VPI: 0 VCI: 38
Good Bytes 0 0
Good Frames 0 1
Discarded Bytes 0
Discarded Frames 0
CRC Errors 0
Invalid Length Errors 0
Timeout Errors 0

Driver version - 6.1.2.007-CLN (20041001)
N/A

Deciphering line reports

Hi.
Sorry for the delay in getting back.
Thanks for the stats, they look a but weird to me somehow
I've just been reading your first post again which I don't think I did properly first time around.
If you can rule out the wiring on your side of the BT mastersocket then you need to raise a ticket containing a cut and paste of your line stats and telling CS everything you have checked. It might be of interest to watch the figures whilst you are connected and see if things slowly fade out out just drop out.
If the connection was OK through the night it could suggest some day time interference so if you have installed any new electrical equipment check that
Sorry to be of little help. I only just realised the test results you gave earlier were done by Metronet. They didn't seem to offer much help in what you should do next.
Cheers
Jon