13
Troubleshooting POS interfaces
This section provides troubleshooting information for common POS interface problems.
Interface physically down
Symptom
The physical state of the POS interface is down.
Solution
To resolve the problem:
1.
Verify that the two ends use different clock mode settings (
master
at one end and
slave
at the
other end).
2.
Verify that the POS interface and its optical module have matching transmission rate.
3.
Verify that the two ends use the same framing format.
4.
Use the
display interface pos
interface-number
command to view the alarms generated on
the interface.
If an AIS alarm was generated, verify that the interface has correct overhead bytes settings.
If an LOS or LOF error was generated, verify that the optical module on the two ends and
the optical fiber are working correctly.
5.
If the problem persists, contact H3C Support.
Data link layer down
Symptom
The physical state of the POS interface is up, but the data link layer state is down.
Solution
This symptom might occur due to negotiation failures caused by packet loss.
To resolve the problem:
1.
Execute the
debugging physical packet all interface pos
command on both devices to
identify the faulty device.
2.
On the faulty device, perform the following tasks:
a.
Execute the
reset counters interface pos
interface-number
command to clear statistics
for the POS interface.
b.
In probe view, execute the
display hardware internal module
pos
interface-number
statistics
command to view packet statistics.
c.
Perform the following tasks:
−
Use the
display hardware internal module
pos
interface-number
reg
3
command in
probe view to verify that the physical layer configuration is correct.
