Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
LLDP/4/LLDP_MDN_REMTABLECHANGE
LLDP/4/LLDP_MDN_REMTABLECHANGE
Message
LLDP/4/LLDP_MDN_REMTABLECHANGE: MDN
Neighbor information was changed.
Description
MDN neighbor information is changed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Cause 1: A MDN neighbor is found.
Cause 2: A MDN neighbor is deleted.
Cause 3: A MDN neighbor is discarded because of insufficient
space.
Cause 4: A MDN neighbor is aged.
Procedure
Cause 1: A MDN neighbor is found.
Check whether a new MDN neighbor is found.
If a new MDN neighbor is found, this log message is informational
only, and no action is required.
If no new MDN neighbor is found, go to Step 2.
Collect information about configurations, trap messages,
and log messages, and contact technical support personnel.
Cause 2: A MDN neighbor is deleted.
Check whether a MDN neighbor has been deleted.
If a MDN neighbor has been deleted, this log message is informational
only, and no action is required.
If no MDN neighbor has been deleted, go to Step 2.
Check whether the link between the local device and
its MDN neighbor is faulty.
If the link is fault, rectify the fault.
If the link is normal, go to Step 3.
Collect information about configurations, trap messages,
and log messages, and contact technical support personnel.
Cause 3: A MDN neighbor is discarded because
of insufficient space.
Check whether the number of MDN neighbors stored on
the local device has reached the maximum limit.
If the number of MDN neighbors has reached the maximum limit,
this log message is informational only, and no action is required.
If the number of MDN neighbors has not reached the maximum limit,
go to Step 2.
Collect information about configurations, trap messages,
and log messages, and contact technical support personnel.
Cause 4: A MDN neighbor is aged.
Check whether the MDN neighbor information stored on
the local device has timed out.
If the MDN neighbor information has timed out, this log message
is informational only, and no action is required.
If the MDN neighbor information has not timed out, go to Step
2.
Check whether the interfaces used to connect the MDN
neighbor and 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.
Check the usage of CPU resources to determine whether
the link between the MDN neighbor and local device is congested.
If the link is congested, stop unnecessary traffic to alleviate
link congestion.
If the link is not congested, go to Step 4.
Collect information about configurations, trap messages,
and log messages, and then contact technical support personnel.
Previous
