PTP_1.3.6.1.4.1.2011.5.25.187.5.48 hwPtpPassiveMeasureOverflow

Trap Buffer Description

The time offset of the passive port is abnormal. (hwPtpPortName=[hwPtpPortName], hwPtpPortIfIndex=[hwPtpPortIfIndex], hwPtpPortRingFiberLengthChangeValue=[hwPtpPortRingFiberLengthChangeValue], hwPtpPortRingFiberLengthChangeValueFlag=[hwPtpPortRingFiberLengthChangeValueFlag], hwPtpPassiveAlarmThreshold=[hwPtpPassiveAlarmThreshold])

Passive monitoring threshold-crossing alarm. The passive port that is configured as the Ethernet reference port does not support the passive monitoring threshold-crossing alarm.

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwPtpPassiveMeasureOverflow

Trap OID

1.3.6.1.4.1.2011.5.25.187.5.48

MIB

HUAWEI-PTP-MIB

Alarm ID

0x00F1037f

Alarm Name

hwPtpPassiveMeasureOverflow

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

PTP_1.3.6.1.4.1.2011.5.25.187.5.49 hwPtpPassiveMeasureOverflowResume

Trap Buffer Parameters

Parameter Description

hwPtpPortName

Name of the current port.

hwPtpPortIfIndex

Index of the current port.

hwPtpPortRingFiberLengthChangeValue

New time offset caused by the fiber length change of the current port. (unit: ns)

hwPtpPortRingFiberLengthChangeValueFlag

Plus or minus sign of the new time offset caused by the fiber change of the current port.

The value can be:

Minus sign (0).

Positive sign (1).

hwPtpPassiveAlarmThreshold

Passive monitoring threshold configured on the current device.

VB Parameters

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.3.6.1.4.1.2011.5.25.187.1.92

hwPtpPassiveAlarmThreshold

-

Impact on the System

The precision of clock synchronization is affected.

Possible Causes

The offset values of Passive ports are checked every 300s. The time offset value of the current Passive port is larger than the time offset threshold configured on the Passive port.

Procedure

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 9.

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 asymmetry 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. 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 9.

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 not, go to step 6.

If yes, go to step 8.

6. Run the disp alarm active | inc PTP_OFFSETSUM_OVER command to check whether time offset accumulation and threshold-crossing alarms are generated on the device.

If yes, there is a high probability that the problem is caused by different frequency and time sources. Go to step 7.

If no, go to step 8.

7. Re-plan the deployment to ensure that the frequency and time are synchronized. Then, check whether the alarm is cleared.

If the alarm is cleared, go to step 9

If the alarm persists, go to step 8

8. Collect trap, log, and configuration information, and contact technical support personnel.

9. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >