LLDP
LLDP_1.0.8802.1.1.2.0.0.1 lldpRemTablesChange
Description
LLDP/4/NBRCHGTRAP: OID [oid] Neighbor information is changed. (LldpStatsRemTablesInserts=[integer], LldpStatsRemTablesDeletes=[integer], LldpStatsRemTablesDrops=[integer], LldpStatsRemTablesAgeouts=[integer])
This alarm is generated when a neighbor is added, deleted, discarded, or aged.
Parameters
| Name | Meaning |
|---|---|
[oid] |
Indicates the MIB object ID of the alarm. |
LldpStatsRemTablesInserts |
Indicates the number of new neighbors. |
LldpStatsRemTablesDeletes |
Indicates the number of neighbors that are deleted. |
LldpStatsRemTablesDrops |
Indicates the number of neighbors that are discarded because of insufficient space. |
LldpStatsRemTablesAgeouts |
Indicates the number of neighbors that are aged. |
Impact on the System
This alarm is a notification of changes in the network topology for the NMS, and no action is required.
Possible Causes
Cause 1
A neighbor is found.
Cause 2
A neighbor is deleted.
Cause 3
A neighbor is aged.
Cause 4
A neighbor is discarded because of insufficient space.
Procedure
- Check the values of LldpStatsRemTablesInserts, LldpStatsRemTablesDeletes, LldpStatsRemTablesDrops, and LldpStatsRemTablesAgeouts in the alarm message.
- If the value of LldpStatsRemTablesInserts is not 0, go to Step 2.
- If the value of LldpStatsRemTablesDeletes is not 0, go to Step 3.
- If the value of LldpStatsRemTablesDrops is not 0, go to Step 4.
- If the value of LldpStatsRemTablesAgeouts is not 0, go to Step 5.
- Neighbors are discovered, indicating that new devices are connected to the device or LLDP is enabled on some neighbors. This message is a normal notification and you do not need to handle it. Go to Step 6.
- Some neighbors are deleted, indicating that LLDP is disabled on these neighbors or the neighbors are disconnected from the device. Check whether the administrator has disabled LLDP on these devices or disconnected these devices from the device.
- If the administrator has disabled LLDP on these devices or disconnected these devices from the device, go to Step 6.
- If not, rectify the link fault and go to Step 6.
- The number of neighbors reaches the maximum (512 on the entire device and 256 on each port). It is recommended that you disable LLDP on some minor ports to save information about the new neighbors. Go to Step 6.
- Some neighbors are deleted after their aging time expires, indicating that the links between the neighbors and the device are faulty. Rectify the link fault and go to Step 6.
- End.
LLDP_1.3.6.1.4.1.2011.5.25.134.2.1 hwLldpEnabled
Description
LLDP/4/ENABLETRAP: OID [oid] Global LLDP is enabled.
This notification is sent to the NMS when LLDP is enabled globally.
This alarm is allowed by the alarm delay.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.134.2.1 | Warning | equipmentAlarm(5) |
LLDP_1.3.6.1.4.1.2011.5.25.134.2.2 hwLldpDisabled
Description
LLDP/4/DISABLETRAP: OID [oid] Global LLDP is disabled.
This notification is sent to the NMS when the LLDP is disabled globally.
This alarm is allowed by the alarm delay.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.134.2.2 | Warning | equipmentAlarm(5) |
LLDP_1.3.6.1.4.1.2011.5.25.134.2.5 hwLldpLocManIPAddrChange
Description
LLDP/4/ADDCHGTRAP: OID [oid] Local management address is changed. (LocManAddr=[STRING])
The LLDP management address of a device was changed.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.134.2.5 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| LocManAddr | Indicates the local LLDP management address. |
Impact on the System
This alarm is a notification of the change of the network topology for the NMS, and does not affect services.
Possible Causes
- The LLDP management address of a device was changed by running the lldp management-address command manually.
- The lldp management-address command was not configured on the device, but IP addresses of some interfaces changed. As a result, the LLDP management address changed.
Procedure
- Check whether the local LLDP management address is the
same as the planned one.
- If so, this alarm is informational only, and no action is required.
If not, go to step 2.
- Run the lldp management-address command in the system view, and configure the local LLDP management address to the planned IP address.
LLDP_1.3.6.1.4.1.2011.5.25.134.2.7 hwLldpRateExcessive
Description
LLDP/4/RATEEXCESSIVE: OID [oid] The rate of received PDUs exceeded the threshold. (IfName=[STRING])
The LLDP packets received by an interface exceeded five in one second.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.134.2.7 | Warning | equipmentAlarm(6) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| IfName | Indicates the interface name. |
Impact on the System
If the interface is attacked by LLDP packets, it may not receive LLDP packets sent by a neighbor device. As a result, the judgment of the network topology for the NMS will be affected.
Possible Causes
- The interface had more than five LLDP neighbors, and all neighbors sent LLDP packets to it simultaneously.
- The interface was attacked by LLDP packets.
Procedure
- Run the display lldp neighbor interface interface-type interface-number command in any view to check the number
of LLDP neighbors on the interface found in the alarm. The n in "STRING has n neighbor(s)" displayed in the first
line is the number.
- If n ranges from 0 to 5, the interface is attacked by LLDP packets. Go to step 2.
- If n is greater than 5, the alarm cause cannot be determined. Go to step 2.
- Run the capture-packet interface interface-type interface-number destination terminal command in the system view to
capture packets received by the STRING interface. Check whether
two or more captured LLDP packets have the same source MAC address.
- If so, run the mac-address blackhole mac-address command in the system view to set this MAC address as a blackhole MAC address, and go to step 4.
- If not, go to step 3.
- Check whether the current LLDP neighbor relationships on
this interface are needed.
- If so, this alarm is informational only, and no action is required.
- If not, go to step 4.
- Disconnect unnecessary LLDP neighbor relationships. If the neighbor relationships can be disconnected, run the undo lldp enable command on the neighbor's interface that establishes a neighbor relationship with the local device to disable the LLDP function, or run the undo l2protocol-tunnel lldp enable command to disable transparent transmission for LLDP packets on the intermediate device's interface that connects to the LLDP neighbor device.
- If the alarm persists, collect alarm information and configuration information, and then contact technical support personnel.