ALM-3276800770 The peer device cannot go online because Eth-Trunk auto-negotiation fails

Description

ENTITYTRAP/4/PNP_TRUNK_FAILED: OID [oid] The peer device cannot go online because Eth-Trunk auto-negotiation fails. Check the configuration and connection. (PeerDeviceEsn=[STRING])

When Eth-Trunk auto-negotiation is performed in PnP mode, the negotiation failed on the peer device.

Attribute

AlarmID	Alarm OID	Alarm Severity	Alarm Type
3276800770	1.3.6.1.4.1.2011.5.25.667.2.39	Major	Communication alarm

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
hwPeerDeviceEsn	Indicates the ESN of the peer device.

Impact on the System

Eth-Trunk link negotiation fails and the peer device cannot register with iMaster NCE-Campus and go online.

Possible Causes

The device connection is incorrect or the PnP configuration of the device is incorrect.

Procedure

Check whether the PnP configuration of the device is correct.
- If the pnp startup-link-aggregation enable command exists in the configuration file of the upstream device (that is, the local device), check whether the pnp startup-vlan send enable command exists in the configuration file of the upstream device. If not, run the pnp startup-vlan send enable command to enable the device to transmit PnP VLAN information to its downstream devices.
- Check whether the undo pnp startup-vlan receive enable command exists in the configuration file of the downstream device (that is, the peer device). If so, run the pnp startup-vlan receive enable command to enable the device to receive PnP VLAN negotiation packets from its upstream devices.
- Check whether the undo pnp startup-link-aggregation receive enable command exists in the configuration file of the downstream device (that is, the peer device). If so, run the pnp startup-link-aggregation receive enable command to enable Eth-Trunk auto-negotiation.
Check whether the Eth-Trunk negotiation failure is caused by non-default configurations on the physical interface of the downstream device (that is, the peer device). If so, run the undo command to delete the non-default configurations.
Check whether the ports on the upstream and downstream devices are correctly connected. If the connections are incorrect, Eth-Trunk negotiation will fail. In this case, correct the connections according to the plan.
Collect alarm information and configuration information, and then contact technical support personnel.