Troubleshooting Physical Interface Anomaly; Data Transmission Anomaly; Collecting Information - H3C MSR Series Troubleshooting Manual

Troubleshooting physical interface anomaly

Symptom
The physical interface is abnormal, for example, the LOS, LFA, AIS, or RAI alarms exist on the
controller interface and the controller interface stays down or flaps.
Solution
To resolve this issue:
Troubleshoot the hardware.
1.
Troubleshoot the cables.
2.
Troubleshoot the configuration.
3.
Troubleshoot the clocks.
4.
Troubleshoot grounding.
5.
Troubleshoot through looping.
6.

Data transmission anomaly

Symptom
The physical interface is up, and has no alarms. However, the data cannot be sent or received
properly. For example, error packets exist on the local and peer interfaces, and the link layer protocol
comes up and go down.
Solution
To resolve this issue:
Troubleshoot the hardware.
1.
Troubleshoot the cables.
2.
Troubleshoot the configuration.
3.
Troubleshoot the clocks.
4.
Troubleshoot grounding.
5.
Troubleshoot through looping.
6.

Collecting information

If the issue persists, execute the following commands to collect information and contact H3C
Support.
•
display diagnostic-information
•
display device verbose
•
display controller or display fe1/ft1
•
display interface serial (If the number of inbound or outbound error packets increases, execute
this command multiple times)
•
Enter the hidden view, and use hidden commands to obtain the physical chip status. Available
commands are as follows:
Enter the hidden view in Comware 7：
<H3C>system-view
System View: return to User View with Ctrl+Z.
[H3C]probe
[H3C-probe]
19