The negotiation status between the local client and the server changes. (ServerId=[ServerId], NegoState=[NegoState], ErrorReason=[ErrorReason])
Negotiation status between the local client and remote servers 1 and 2.
In VS mode, this trap is supported only by the admin VS.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Event |
Trap Severity |
Warning |
Mnemonic Code |
PTPACRNEGOSTATE |
Trap OID |
1.3.6.1.4.1.2011.5.25.187.5.28 |
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 |
|---|---|
ServerId |
Server ID. The value can be: server1(1) server2(2) |
NegoState |
Negotiation status. The value can be: init(0), indicating the initial state. success(1), indicating that the negotiation succeeds. error(2), indicating that the negotiation fails. none(3) indicates that the IP address of the server is unavailable. |
ErrorReason |
Negotiation failure cause. The value can be: none(0). delete_link(1) announce_timeout(2). announce_nego_timeout(3) announce_nego_deny(4) sync_nego_failed(5) sync_nego_deny(6) delayresp_nego_timeout(7) delayresp_nego_deny(8) ifcannotsupport_ptp(9) servicemodenotsupport_ptp(10) route_unreach(11) bmc_failed(12) master_synchronization_fault(13) |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.187.1.109 |
hwPtpAdaptiveRemoteServerId |
- |
1.3.6.1.4.1.2011.5.25.187.1.110 |
hwPtpAdaptiveRemoteServerNegoState |
- |
1.3.6.1.4.1.2011.5.25.187.1.111 |
hwPtpAdaptiveNegoErrorReason |
- |
1. Run the display ptp-adaptive all command to check the negotiation status between the client and the remote server.
If the negotiation status with a remote server is success, the negotiation with the remote server is successful, and no action is required.
If the negotiation status between the and all remote servers is error, run the ping command to check whether the links between the and remote servers are normal.
If so, go to Step 2.
If not, go to Step 3.
2. Run the display current-configuration command to check whether the clock configuration of the client is changed.
If yes, go to Step 3.
If no, go to Step 4.
3. Reconfigure the remote server. For details, see System Management > 1588v2 Configuration > Configuring 1588v2 ACR Clock Synchronization in the Configuration Guide.
Check whether the fault is rectified.
If the alarm is cleared, go to Step 5.
If the alarm persists, go to Step 4.
4. Collect trap, log, and configuration information, and contact technical support.
5. Ends.