Line Diagnostics: Difference between revisions

From AAISP Support Site
(There are no BE lines anymore (AFAIK))
Line 70: Line 70:
If you get a Copper line test error, try the test again with all equipment unplugged, and the NTE5 faceplate removed as the fault could be caused by local wiring or equipment.
If you get a Copper line test error, try the test again with all equipment unplugged, and the NTE5 faceplate removed as the fault could be caused by local wiring or equipment.


<strike>
==BE Line Data and Settings==
==BE Line Data and Settings==
*Available on BE Lines
*Available on BE Lines
From here you can set the line profile as well as view sync status. This is non-intrusive and should not cause the line to drop.
From here you can set the line profile as well as view sync status. This is non-intrusive and should not cause the line to drop.
</strike>


==Kill Buttons==
==Kill Buttons==

Revision as of 14:37, 25 September 2014

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 View login log rect 198 2 311 26 Capture traffic happening on the line rect 316 0 404 26 Force router to relogin rect 410 1 553 28 BT Knowledge-Based Diagnostics rect 559 1 697 30 FTTC and FTTP Line tests </imagemap>

Clueless-run-pstn-test.png Clueless-belinesettings.png Speedtest-button.png

Clueless-line-diag-on-a-bt-line.png


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

Log

  • Available on all lines

Displays the radius stats for the line, normally at (roughly) hourly intervals. Information is mostly usage but will also have details of any disconnects/connects including disconnect reason and connect sync speed.

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. This is non-intrusive and should not cause the line to drop.

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

Sometimes the line test will (cryptically) suggest that a fault needs to be reported to the phone line provider, eg, it will say Report to OR (OpenReach), for example:

BT Test CopperLineTest:Fail Line test failed report fault to OR.fail Line test failed report fault to OR. T023:FAULT - Battery Contact

In this case, report the fault to your phone line provider, if this is BT Retail, then you can report online: https://www.bt.com/faults

The copper line could come back with other outcomes, such as:

  • DIS The test cannot get a capacitance reading of your line. You probably have no dial tone. It's broken somewhere, somehow!
  • LOOP The 2 wires that make up the line are in contact with each other and are causing a loop.
  • Battery Contact The line is in contact with another line, perhaps due to water, or bad insulation
  • Earth Contact The line is going to earth. The line may be damaged and wire touching earth somewhere
  • Rectified Loop a one way loop - check internal wiring before going further.
  • High Resistance DIS Both lines have high resistance - some connection problem along the line.

If you get a Copper line test error, try the test again with all equipment unplugged, and the NTE5 faceplate removed as the fault could be caused by local wiring or equipment.

BE Line Data and Settings

  • Available on BE Lines

From here you can set the line profile as well as view sync status. This is non-intrusive and should not cause the line to drop.

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

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 Copper Test

  • Available on BT ADSL Lines

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

Example output:

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.

Run PSTN Test

  • Available where AAISP provide the PSTN line. This may cause the line to drop sync and reconnect.

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 (as the fault is located at the exchange). However, running the test a little while later gave:

WLR3Test WLR3_CIDT_Test rds089a006:240514264: 
Pass Line Test OK. Dial tone OK ServiceLevel:2, MainFaultLocation:OK, FaultReportAdvised:N, AppointmentRequired:N, LineStability:Stable, 
NetworkStability:Stable, StabilityStatement:Stable - no adverse line test history. CP may request an Engineer visit to investigate, test and demonstrate with the EU. 
Routine test & fault data available at Customer Diagnostic Tool on INFORMe under MIS>Artisan>CDT. 
If no fault is found clear RWT and apply Time Related Charges.

This is suggesting that there is no fault...

If a fault is Fault Report is Advised it is a good idea to run the test again with equipment unplugged from the line. If the results suggest a fault at the Customer Equipment then try removing the NTE faceplate which will remove any internal wiring and see if it still says there is a fault.

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.

Speedtest

Speedtest-button.png

  • Available on TalkTalk Wholesale lines

See GetSpeedTestResults

Automatic Tests

See Automatic Line Testing for information on the up/down and regular line testing features.

Other Control Page pages:

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