Route Tracing; Stack Loopback Testing; Time Domain Reflectometer - Avaya 5000 Series Troubleshooting Manual

Route Tracing

Identify network connection issues that are not directly related to the ERS 5600 Series
device.
The traceroute <ip> command records the route (the specific gateway computers at each
hop) through the Internet between your computer and a specified destination computer. The
command also calculates and displays the amount of time each hop took. The command is
useful for understanding where problems occur in the Internet and to get a detailed sense of
the Internet itself.

Stack Loopback Testing

The stack loopback tests help you determine if the cause of your stacking problem is a bad
stack cable or a damaged stack port.
Two types of stack loopback tests exist. The internal loopback test and external loopback test.
The purpose of the internal loopback test is to verify that the stack ports are functional in each
switch. The purpose of the external loopback test is to verify that the stack cables are
functional.
For accurate results, the internal loopback test must be run before the external loopback test.
The stack loopback tests can only be performed on a standalone unit with no traffic running
on the unit.
To run the test, first use the stack-loopback test internal command. To perform the
external loopback test, connect the stack uplink port with the stack downlink port. Use the
stack-loopback test external command.
For more information about stack loopback testing, see Configuring System Monitoring on
Avaya Ethernet Routing Switch 5000 Series, NN47200-505.

Time Domain Reflectometer

The Avaya Ethernet Routing Switch 5600 Series device is equipped with a Time Domain
Reflectometer (TDR). The TDR provides a diagnostic capability to test connected cables for
defects, such as short pin and pin open. You can obtain TDR test results from Avaya command
line interface (ACLI) or Enterprise Device Manager (EDM).
The cable diagnostic tests only apply to Ethernet copper ports; fiber ports cannot be tested.
Troubleshooting
Route Tracing
December 2013 19