Troubleshooting PE data ports
Traffic loss can occur on data ports attached to Campus Fabric PE units for several reasons. You can send an ECID port ping to help isolate the cause of traffic loss.
Once you issue the
spx ping command, the CB sets up an ECID trap for the ECID associated with the PE data port
under test and places the port in loopback mode. When the PE confirms the loopback,
the CB sends a single ECID ping, identifiable by its sequence number, to the port
under test. In a successful test, the PE port receives the ECID ping directed to it
and loops it back to the CB. The CB then removes the loopback. In an unsuccessful
test, the PE port does not respond to the ping within a maximum of four seconds, and
the PE removes the loopback after a four-second timer expires.
If an ECID port ping succeeds but data traffic issues persist, the cause 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.
Consider the following before performing an ECID port ping:
- ECID pings place the port under test in loopback and, as a result, can disrupt control and data traffic on the port.
- ECID pings do not work for ports that are physically down.
- ECID pings are not supported for SPX ports.
- ECID pings can be initiated only from the CB.
- Each ECID ping is sent to a specific PE, and only one ping can be sent at a time.
Perform the following steps to send an ECID ping to a PE data port.
- In Privileged EXEC mode, enter the
spx ping command followed by the port number to be tested. When prompted, enter
y to continue.
ICX7750-48F Router# 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 ICX7750-48F Router# Received response (seq# 6) for ecid1 ping to 17/1/1 port from PE 17
The 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.ICX7750-48F Router# 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 ICX7750-48F Router# No ecid ping response for spx port 17/1/2, seq 8 from PE 17 !
The example shows a failed test on PE port 17/1/2. The port cannot be reached, possibly due to an SPX infrastructure issue. - (Optional) When an ECID port ping fails, enter the
show spx csp events distributedcommand for the PE under test to verify that the loopback command from the CB was received.ICX7750-48F Router# show spx csp events distributed 17 ********************* Response from PE 17: ********************* PE 0: port 17/1/1 loopback disable pass (13 minute(s) 58 second(s) ) [stack: 002dffdc 0030dd90 002f36b4 002eaee8 002ebc2c 002ea064 00324a3c 002c53dc 009f9740 00ee16c0 00ee24b4 00c0acc8] … <snip> … PE 0: port 17/1/1 loopback enable pass (13 minute(s) 58 second(s) ) [stack: 002dfdd0 0030dd90 002f36b4 002eaee8 002ebc2c 002ea064 00324a3c 002c53dc 009f9740 00ee16c0 00ee24b4 00c0acc8]
The example shows that PE port 17/1/1 received a loopback enable command from the CB and that the PE later disabled the loopback. - (Optional) Based on the outcome of the ECID port ping, follow any prescribed steps for troubleshooting packet loss.