Troubleshooting guide

3. Troubleshooting Functional Failures During Operation
34
For details about the log, see the manual Message and Log Reference.
2. Isolating the cause of the problem by checking the port status
Use the
show interfaces command to check the port status, and isolate the cause of the
problem according to the following table.
Table 3-8: Checking the port status and action to take
No. Port status Cause Action
1
active up The target port is operating
normally.
No
2
active down A line failure has occurred on the
target port.
Based on the log entry for the target port displayed by the
show logging command, see the manual Message and
Log Reference and take the action described in Action.
3
inactive The port is in inactive status due
to one of the following reasons:
•
inactivate command
• The standby link functionality
of link aggregation
• The BPDU guard
functionality of a Spanning
Tree Protocol
• Port resetting of GSRP
• Failure detection in the IEEE
802.3ah/UDLD functionality
• The port is deactivated by the
L2 loop detection
functionality.
• The port is deactivated by the
storm control functionality.
• If the port is deactivated by the standby link
functionality of the link aggregation, this is normal
operating status. Do not activate the port by using the
activate command. Use the show channel-group
command with the
detail parameter to check the
standby link functionality.
• If the port is deactivated by the BPDU guard
functionality of a Spanning Tree Protocol, check the
settings of the partner switch, modify the configuration
so that the Switch does not receive BPDUs, and use the
activate command to activate the target port. Use
the
show spanning-tree command with the detail
parameter to check the BPDU guard functionality.
• If the port is deactivated by the port resetting of GSRP,
the port will automatically return to the active status.
This inactive status of the port is normal. Do not
activate the port by using the
activate command.
• If the port is deactivated due to the unidirectional link
failure detection or L2 loop detection in the IEEE
802.3ah/UDLD functionality, see
3.19 Communication failures in the IEEE 802.3ah/
UDLD functionality. After restoration from the failure,
use the
activate command to activate the target port.
• If the port is deactivated by the L2 loop detection
functionality, modify the configuration in which the
loop occurs, and then use the
activate command to
activate the target port. Also, if
loop-detection
auto-restore-time is specified by a configuration
command, the port will automatically return to the
active status.
• If the port is deactivated by the storm control
functionality, after the LAN is restored from the storm,
use the
activate command to activate the target port.
• If any of the reasons described above do not apply and
you want to activate the port, make sure the cable is
connected to the target port, and then use the
activate command to activate the target port.
4
test A line test is being performed at
the port by the test interfaces
command.
To resume the communication, use the no test
interfaces command to stop the line test, and then use
the
activate command to activate the target port.
5
fault A failure has occurred on the
hardware of the target port.
Based on the log entry for the target port displayed by the
show logging command, see the manual Message and
Log Reference and take the action described in Action.
6
initialize The target port is being initialized. Wait until the initialization is complete.