The fiber length of the passive port changed. (hwPtpCurrentIfIndex=[hwPtpCurrentIfIndex], hwPtpPortName=[hwPtpPortName], hwPtpPortRingFiberLengthChangeValue=[hwPtpPortRingFiberLengthChangeValue], hwPtpPortRingFiberLengthChangeValueFlag=[hwPtpPortRingFiberLengthChangeValueFlag])
This object indicates the optical fiber length change event of a passive interface.
In VS mode, this trap is supported only by the admin VS.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Event |
Trap Severity |
Warning |
Mnemonic Code |
hwPtpPassiveFiberLengthChange |
Trap OID |
1.3.6.1.4.1.2011.5.25.187.5.23 |
MIB |
HUAWEI-PTP-MIB |
Alarm ID |
This is an event trap and does not involve alarm ID. |
Alarm Name |
This is an event trap and does not involve alarm name. |
Alarm Type |
This is an event trap and does not involve alarm type. |
Raise or Clear |
This is an event trap and does not involve alarm generation or clearance. |
Match trap |
- |
| Parameter | Description |
|---|---|
hwPtpCurrentIfIndex |
Index of the current port. |
hwPtpPortName |
Name of the current port. |
hwPtpPortRingFiberLengthChangeValue |
New time offset caused by the fiber length change of the current port. |
hwPtpPortRingFiberLengthChangeValueFlag |
Plus or minus sign of the new time offset caused by the fiber change of the current port. The options are as follows: Minus sign (0) Positive sign (1) |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.187.2.1.1.43 |
hwPtpPortName |
hwPtpPortIfIndex |
1.3.6.1.4.1.2011.5.25.187.2.1.1.45 |
hwPtpPortRingFiberLengthChangeValue |
hwPtpPortIfIndex |
1.3.6.1.4.1.2011.5.25.187.2.1.1.46 |
hwPtpPortRingFiberLengthChangeValueFlag |
hwPtpPortIfIndex |
1. Check whether the lengths of the optical fibers on the active and standby links are changed.
If the length of the new optical fiber is different from that of the original optical fiber, it indicates that the transmit and receive optical fibers are asymmetric. In this case, go to Step 2.
If the optical fiber length does not change, go to Step 3.
2. Replace the symmetric fiber or run the ptp asymmetry-correction command in the interface view to set the asymmetry correction value on the interface connected to the asymmetric fiber. Then, check whether the alarm is cleared.
If the alarm is cleared, go to Step 7.
If the alarm persists, go to Step 3.
3. Check whether the asymmetry value is configured for the ports on the active and standby links within 10 minutes before this event occurs. Run the display current-configuration | in asymetry command in the system view to check whether a new asymmetric value is delivered for all devices on the active and standby links.
If yes, the asymmetric value is incorrectly configured. In this case, go to Step 4.
If no, no new asymmetric value is delivered. In this case, go to Step 5.
4. Determine the asymmetry value to be configured and run the ptp asymmetry-correction command in the interface view to re-deliver the asymmetry value. Then, check whether the alarm is cleared.
If the alarm is cleared, go to Step 7.
If the alarm persists, go to Step 5.
5. Check whether the active and standby links are stable. Links are unstable in many cases. Occasional instability can be ignored. If a link is unstable for a long time, locate the cause.
If yes, go to Step 6.
If not, locate the cause of the unstable link.
6. Collect trap, log, and configuration information, and contact technical support.
7. End.