Line Diagnostics: Difference between revisions

From AAISP Support Site
m (Redirected page to Category:Diagnostic Tools)
 
(30 intermediate revisions by 3 users not shown)
Line 1: Line 1:
#REDIRECT [[Category:Diagnostic Tools]]
The control pages offer customers to run various line tests. These are mostly tests performed by the back haul operator.

These buttons can be found by clicking on your 'line' on the Control Pages (editline.cgi)

The buttons vary depending on what sort of line you have. -Not all tests are available on all types of lines.

<imagemap>Image:Control-pages-Diagnostics.png|
rect 101 1 191 27 [[#Log|View login log]]
rect 198 2 311 26 [[#Traffic_Dump|Capture traffic happening on the line]]
rect 316 0 404 26 [[#Kill_Buttons|Force router to relogin]]
rect 410 1 553 28 [[#KBD|BT Knowledge-Based Diagnostics]]
rect 559 1 697 30 [[#End_to_End_tests|FTTC and FTTP Line tests]]
</imagemap>

[[File:Clueless-run-pstn-test.png|link=#Run_PSTN_Test]]
[[File:Clueless-belinesettings.png|link=#BE_Line_Data_and_Settings]]

[[File:clueless-line-diag-on-a-bt-line.png|border]]


=Line Options=
[[Line Options and Line Settings]] are described on a separate page: [[Line Options and Line Settings]]

==TalkTalk Wholesale Profiles and Tests==
Please see these separate pages for TalkTalk Diagnostics
*[[TalkTalk Wholesale Line Tests]]
*[[TalkTalk Wholesale Line Profiles]]

==Log==
*Available on all lines
This will show the (raw) radius log. This will include the hourly 'stats' as well as login messages.

The page will carry on loading for a few minutes so that you can view the log live as things happen.

==Traffic Dump==
*Available on all lines
This will perform a traffic capture of your line (or lines if you have more than one). You can then view the capture on the page or download a pcap file which can be viewed with other software - eg Wireshark.

==Sync Status==
*Available on BT lines
This will report back the current sync status of the line, including error counts.

Example output:
BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync
BRAS=5779Kb/s FTR=6502Kb/s MSR=8128Kb/s ServOpt=1 I/L=A
Up Sync=854Kb/s LoopLoss=22.6dB SNR=17.5dB ErrSec=0 HECErr=0 Cells=1677609
Down Sync=6551Kb/s LoopLoss=40.8dB SNR=13.5dB ErrSec=0 HECErr=N/A Cells=4001712

==Copper Line Test==
*Available on BT lines
Carries out a copper line test to test aspects of the actual phone line. This will cause the line to drop sync for a minute or so. It may report back that an OR (Open Reach) fault will need to be raised with the provider of the PSTN line. Sometimes just running this test can fix some fault conditions!

Example output:
BT Test xDSL Copper Test:Pass Standalone sub test passed successfully.
Pass Copper Line Test Successful T300:CIDT LINE TEST OK - END USER EQUIPMENT DETECTED


==BE Line Data and Settings==
*Available on BE Lines
From here you can set the line profile as well as view sync status.

==Kill Buttons==
===PPP Kill===
*Available on all lines
Kills your individual PPP session to AAISP which will cause your modem (or whatever is maintaining the PPP session) to log in again. It does NOT cause the modem to resync though.

This option can be useful if there has been a problem between AAISP and BT which has caused your connection to pick up a BT test session (and hence IP) instead of a proper AAISP session/IP.

It can also be useful if you've changed routing options (eg [[IPv6]] routing, routing of legacy IPs between multiple lines) which also require a new session.

===Kill BT / Kill TT ===
*Available on BT ADSL Lines, TTW Lines
This will cause the line to resync.

==KBD==
*Available on BT lines.

Carry out BT Knowledge Based Diagnostics on the line. Depending on the sub tests carried out this procedure may cause a line drop.

Since the diagnostics are knowledge based it is impossible to give details of what tests will actually be carried out on a given line.

It tries to summarise line faults in plain English, so you don't need
a detailed understanding of ADSL to run it. You probably will to
understand some of the detailed info it comes out with though.

KBD test results are logged, so you can ask staff members to look at
historical test results.

==End to End tests==
*Available on BT FTTC/FTTP lines.
This will run FTTC/FTTP specific tests and will suggest if it finds a fault or not.

Example result:
BT Test E2E Access Test/DCN:Inconclusive OR test pass. Unable to find the fault.
Down:40.0 (39.9/39.7/39.9) Up:10.0 (10.0/10.0/10.0)
NA 0.128M-40M Downstream, Interleaving Off - 0.128M-10M Upstream, Interleaving Off
In Sync Pass:GTC_FTTC_SERVICE_0000 GEA service test completed and no fault found .

==Set Profile==
*Available on TTW Lines, see: [[TalkTalk Wholesale Line Profiles]]

== Line Test ==

Warning - this option will (often if not always) cause your line to drop (it should resync once the test is complete).

Carries out a BT xDSL line test on your line. This has three subparts (all of which are carried out in order once you click the link):

== xDSL Status Check ==
*Available on BT ADSL Lines
Checks whether there is currently an ADSL session on the line - if so displays the parameters.

Example output:
<pre>
BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass DSL Status Check Successful Circuit In Sync
BRAS=3500Kb/s FTR=3200Kb/s MSR=4000Kb/s ServOpt= I/L=O Resysch
Up Sync=1035Kb/s LoopLoss=14.5dB SNR=7dB ErrSec=0 HECErr=0 Cells=487812
Down Sync=7494Kb/s LoopLoss=29.6dB SNR=12dB ErrSec=4 HECErr=N/A Cells=397235
</pre>

== xDSL IP Test ==
[what is this supposed to do?] This test will normally FAIL on a working line.

== xDSL Copper Test ==
*Available on BT ADSL Lines

Checks the loop loss on the line. This will often (if not always) cause a line drop.

Example output:

<pre>
BT Test xDSL Copper Test:Pass Standalone sub test passed successfully.Pass Copper Line Test Successful DS10:Line Test OK.Line loss within appropriate limits.
</pre>

==Run PSTN Test==
*Available where AAISP provide the PSTN line
[[File:Clueless-run-pstn-test.png]]

This runs a CIDT Test (Copper Integrated Demand Test) on the PSTN line and will report any problems it finds along with suggestions.

If the result includes 'FaultReportAdvised:Y' then please contact support, as a fault may need to be submitted to Open Reach.

Example output:
WLR3Test WLR3_CIDT_Test rds089a006:240448742: Fail FAULT - Dis in exchange ServiceLevel:2, MainFaultLocation:FU, FaultReportAdvised:Y, AppointmentRequired:N, LineStability:, NetworkStability:, StabilityStatement:
This actually shows a fault, 'Disconnect in exchange'. It is suggesting a fault is to be reported (contact support), but that no appointment is required to me made at the End user premises.

Fault Locations are as follows:

CA Fault located at Customer Apparatus
DT Diagnostic test required to establish fault
EX Fault located in Exchange
LN Fault Located in Local Network
CE "Fault located at Customer Equipment. Provides further breakdown of a CA fault"
FU "Fault Located at Frames Unit. Provides further breakdown of an EX fault.

==Other Control Page pages:==
<ncl style=bullet maxdepth=5 headings=bullet headstart=2 showcats=1 showarts=1>Category:Control Pages</ncl>


[[Category:Internet]]
[[Category:Control Pages]]

Latest revision as of 20:57, 18 April 2015

Redirect to:

Retrieved from ‘http://support.aa.net.uk/index.php?title=Line_Diagnostics&oldid=9026’