spx ping
Privileged EXEC mode
ECID pings can be initiated only from the CB.
ECID pings are not supported for SPX ports.
ECID pings do not work for ports that are physically down.
ECID pings place the port under test in loopback and, as a result, can disrupt control and data traffic on the port.
Each ECID ping is sent to a specific PE, and only one ping can be sent at a time.
If an ECID port ping succeeds, the cause of traffic loss on the port is likely related to an application issue, such as incorrect IP settings. If the ECID port ping fails, the cause of traffic loss on the port is likely related to an SPX infrastructure issue.
When an ECID port ping fails, you may want to enter the
show spx csp events distributed command for the PE under test to verify that the loopback command from the CB was
received.
The following example shows a successful test on PE port 17/1/1. Traffic loss on the port may be due to a problem with IP settings or other applications issues.
device# spx ping 17/1/1 SPX Ping Port is disruptive to control, data traffic. Are you sure, you want to continue (enter 'y' or 'n'): y device# Received response (seq# 6) for ecid1 ping to 17/1/1 port from PE 17
The following example shows a failed test on PE port 17/1/2. The port cannot be reached, possibly due to an SPX infrastructure issue.
device# spx ping 17/1/2 SPX Ping Port is disruptive to data traffic. Are you sure, you want to continue (enter 'y' or 'n'): y device# No ecid ping response for spx port 17/1/2, seq 8 from PE 17 !
| Release version | Command history |
|---|---|
| 08.0.61 | This command was introduced. |