You are on page 1of 28

Level One Troubleshooting - Ethernet Over Copper

Step 1 - Locating EOC customers information

Log into TPFx

Step 2 - Click on Account

Step 3 - Search by Account number

Step 4 - Select customers address and Click on GO

Step 5 - Click on Loop one to gather all EoC info and view numbers in account
Step 6 - Gathering Loop Circuit ID & TA5000 assignment
1/1/3 - Is the loops assignment in the TA5000
05.ARSU.966443..GTEW - Is the loops circuit Id
Step 7 - Gathering TA5000 & CFA information
Click on the Circuit Details - EoC Tab
SWC - Is the TA5000 CLLI name that is used to telnet to the equipment
CFA - Is the CFA assignment for Loop One - used when a ticket is opened with the LEC
Loop Distance (EWL) - Is the loop distance from the CO to the customers' prem

Step 8 - Gathering NTU & CSU IP information

Click on the Internet IP Tab
WAN IP - Is the IP used to log into the CSU providing the smartvoice product
EoX Internet Management IP - Is the IP used to log into the NTU - via the Irvine DCN
Click on the VPN tab to see the VPN info, if applicable
Now you can go to the DCN Page to access the NTU & TA5000
Once you get to the DCN, use SECURE CRT to log into the NTU & TA5000
Logging into an NTU
the command show interface shdsl cr
will see all of the links and if they are provisioned.What is important are the:

1. State
2. Status
3. Channel Rate (Bandwidth for that 1 Link)

These are errors that we can fully understand. To see a history of the last 7 days for any interface,
type in: show menu performance-statistics shdsl 1/0/1 24
show menu performance-statistics ethernet 1/0/1 24
To see
a performance history you can also do it this way: show interface efm-l 1 performance-statistics 15
or 24
Note: clearing a counter will not clear the performance history. We should not clear the performance
history so that someone else working on this NTU can see a historical chart.To clear counters: clear
counters EFM LinksEach loop (layer 1) has a corresponding Link (layer 2)The command is show
interface efm-l X
1. Err Fragments, Discards, FCS errors and Coding errors are noteworthy
2. Coding errors will normally reflect layer one errored seconds on the facility.
3. When you see errored fragments or discarded fragments, these could cause voice issues on SV or
cause a router to request the far end to resend packets which would decrease the up and down
4. When an EFM-link hits the threshold for removal, it will appear in the alarm log. If the link clears, it
will go back in the group once that the threshold is not at the inhibit limit.

5) You can view an alarm log by entering the command: show alarm log
To clear the alarms enter: force alarm acknowledge then enter the command: force alarm clear
EFM GroupsThe command to show an EFM-G is: show interface efm-g 1 (there is only one EFM
You need to look at:

1. Status
2. Provisioned Links
3. Active Links (should be the same as provisioned)
4. Inhibited Links (you would look at the EFM-L to see if it was inhibited. To add the inhibited link back
in to the group, you would clear the counters: clear counters
5. Data Rate/Bandwidth Available ( the sum of all active links)
6. Errors would be displayed under bad or lost fragments, lost start or lost end

Bad Splice You can see if the loop has a bad spice by running the command: show interface shdsl
1/0/1 splice-detect 24
If there
is a bad splice, you will see the distance in the summary. Also it needs to see 5 counts before it will
show the detected bad splice. Note: if you are seeing errors that are unexplainable by viewing
statistics from the NTU, always look at the service via the TA5000. We have found bad connections
in the CO that have been detected by TSCAN or querying bad splice detect from the TA5000. As
you can see, the bad splice is around 246', the distance from the TA5K to the meet me point in the

Central Office TA5000 Testing a

Loop from the NTU with TSCAN You may test a loop from the NTU with TSCAN. It will tell you if the
loop is open or has a short and the distance to the open. Type in APP to get to the diagnostics of the
NTU test interface shdsl 1/0/5 tscan

Here you can see there is an open, from the NTU, at 1760'At this time you could set up a dispatch
with the LEC or schedule a meet with FOPS and the LEC if you have already dispatched the LEC. A
dispatch will be determined from your experience in trouble shooting a loop. If you feel the distance
indicates an open at the MPOE, dispatch FOPS, if it is a greater distance, between 800' to 1800', the
trouble would probably be at the B Box and then you would dispatch the LEC. The same applies
from the TA5000, but if the open was within 300', the open would probably be there in the LSO, and
then the LEC would get the ticket. You could not determine what the issue would be if the open is
greater than 300', it still would go to the LEC. TSCAN is good up to 6000'. That is why you might
need to test from each location, (NTU & TA5000) to help determine where the issue is located.
+Testing the customer in the TA5000+ Verifying and testing an EoC customer in the TA5000 is
basically the same as the NTU with a few exceptions. The ports are diversified in the TA so they will
not be in a numerical order. Also the EFM group number will be in TPFX.You can also determine the
EFM Group by logging into the TA5K, do a: _+show int efm-g | in 278557003+_ and it will respond
with the EFM group associated with the customers service: _+EFM Group 1/1/3 {278557003} is
the command: show int efm-g 1/1/3
will see the card you are on, slot 1, the provisioned ports and the active ports, any inhibited links, the
total bandwidth of the service and any bad or fragment errors. To test the loops from the TA5000,
you would go to the APP prompt, enter: test in shdsl 1/4/1 tscan
To see
the results: show test in shdsl 1/4/1 tscan and you would see the results. Notice that it see's a short
at 6270', you would need to log into the NTU, run the TSCAN Test to confirm. Also you would look in
FX to see the length of the loop to help determine the location of the short. You can also look at the
efm-l to see its status: show in efm-l 1/4/1
can see the loop is enabled and down, no sync, errored fragments, and coding errors. The reason
the link is down is that the loop is down.If you see that the link is enabled and inhibited, the EFM-G
inhibited the link and took it out of the EFM-G because it met the XCV Threshold, which is
adjustable. How to verify loop assignments between the NTU and the TA5000 1) Post up the efm-
group in the TA5000 in a real-time view. (show interface efm-group x/x/x realtime)
2) Drop
the circuit in question on the NTU.Config tInterface shdsl 1/0/XShut
1. Verify which link on the TA5000 dropped.
Remember to do a no shut on the loop you disabled in the NTU once done