LLDP/4/LLDP_REMTABLECHANGE

Message

LLDP/4/LLDP_REMTABLECHANGE: LLDP neighbor information was changed. (Added=[lldpStatsRemTablesInserts], Deleted=[lldpStatsRemTablesDeletes], Dropped=[lldpStatsRemTablesDrops], Aged=[lldpStatsRemTablesAgeouts])

Description

Neighbor information is changed.

Parameters

Parameter Name	Parameter Meaning
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.
lldpStatsRemTablesAgeouts	Indicates the number of neighbors that are aged.

Possible Causes

Cause 1: A neighbor is found.

Cause 2: A neighbor is deleted.

Cause 3: A neighbor is discarded because of insufficient space.

Cause 4: A neighbor is aged.

Procedure

Cause 1: A neighbor is found.

1. Check whether LLDP is enabled on the neighbor.

If LLDP is enabled, this log message is informational only, and no action is required.
LLDP is not enabled, go to Step 2.

2. Collect log information and configuration information, and then contact technical support personnel.

Cause 2: A neighbor is deleted.

1. Check whether LLDP is disabled on the neighbor.

If LLDP is disabled, run the lldp enable (system view) command on the neighbor.
If LLDP is not disabled, go to Step 2.

2. Check whether the link between the neighbor and local device is faulty.

If the link is faulty, rectify the fault.
If the link is normal, go to Step 3.

3. Collect log information and configuration information, and then contact technical support personnel.

Cause 3: A neighbor is discarded because of insufficient space.

1. Check whether the number of neighbors stored on the local device has reached the maximum limit.

If the number of neighbors has reached the maximum limit, this log message is informational only, and no action is required.
If the number of neighbors has not reached the maximum limit, go to Step 2.

2. Collect log information and configuration information, and then contact technical support personnel.

Cause 4: A neighbor is aged.

1. Check whether neighbor information stored on the local device has timed out.

If neighbor information has timed out, this log message is informational only, and no action is required.
If neighbor information has not timed out, go to Step 2.

2. Check whether the interfaces used to connect the neighbor to the local device are shut down.

If an interface is shut down, run the undo shutdown command on this interface.
If no interface is shut down, go to Step 3.

3. Check the usage of CPU resources to determine whether the link between the neighbor and local device is congested.

If the link is congested, stop unnecessary traffic to alleviate the congestion.
If the link is not congested, go to Step 4.

4. Collect log information and configuration information, and then contact technical support personnel.