|
Frame Relay Troubleshooting
*Also see: Debugging Tools
If the s port does not display an "ESTABLISHED" status,
perform the following commands:
Command> set console
Setting CONSOLE to admin session
Command> set debug 0x51
Setting debug value to 0x51
- If you see Local Management Interface (LMI) packets being transmitted but no packets
being received as show in the the following example, enter the following commands:
Command> reset s1
Resetting port S1
Command> Enabling port S1 (DMA) # Port being started
(S1) LMI: Sending Full Status Enquiry - Sequence 2
(S1) LMI: Sending Full Status Enquiry - Sequence 3
(S1) LMI: Sending Full Status Enquiry - Sequence 4
Put the CSU/DSU into a local loopback. This will cause each packet sent to the CSU/DSU
to be reflected back to the Wide Area Network (WAN) port. This is for testing purposes
only, the line will not function while the CSU/DSU is in a local loopback. If
"LCP: Apparent Loop", is seen it indicates the following occurrences:
- The WAN port on the Lucent PortMaster (TM) is transmitting and receiving data.
- The cable and connectors between the PortMaster and the CSU/DSU are functioning.
- The Data Terminal Equipment (DTE) port on the CSU/DSU is functioning.
- THE PortMaster IS FUNCTIONING PROPERLY
If apparent loops are not seen:
- Verify that the RS232-V.35 dip switch next to the WAN port is set correctly, (usually
V.35)
- Verify that all cables are securely connected.
- Verify that the V.35 cable that came with the unit are being used
- Swapping cables, CSU/DSUs, etc. is another method used to eliminate equipment
hardware problems.
If you get apparent loops and the status is not "ESTABLISHED" but shows
"CONNECTING":
- Verify the CSU/DSU settings such as clocking, etc. In most cases the CSU/DSU should be
set for external clocking. The Telco provides the clock source.Verify your CSU/DSU
settings with the manufacturer.
- Have the telephone carrier provider test the line. Asking for a hard copy of the test
results will often get you better test.
If the port status is "ESTABLISHED" but you are
unable ping the other side, perform the following steps:
- Verify settings. Verify that the IP address for the WAN ports on both sides are in the
same subnet.
- Verify that the correct signal type is being used. There are only two signal
types, LMI and Annex-d. If you are unsure of the signal type try each individually.
Reset the port after each setting.
Command> set w1 lmi 10
or
command> set w1 annex-d 10
- Like polling there are only two types of encoding NRZ and NRZI. NRZ is the default
setting. If you are unsure of the encoding type try each individually.
Command> set w1 encode nrz
or
Command> set w1 encode nrzi
- Traceroute from your workstation at the PortMaster to the router in trouble. Then
traceroute from the router in trouble (assuming you can get to it) back to your
workstation. The problem will lie in the gap between the two traceroutes.
- Verify that the "set gateway" is set to the upstream router.
|