No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Log Reference

AR500, AR510, and AR530 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.

Rate and give feedback:
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).



PIM/4/NBR_DOWN:In VPN instance "[vpn-instance-name]", a neighbor was deleted from the interface. The reason is [reason] (NeighborIpAddress=[STRING], Interface=[STRING], FlCode=[STRING][ULONG])


A neighbor was deleted from the neighbor list of the interface.


Parameter Name Parameter Meaning
[vpn-instance-name] Indicates the name of a VPN instance.
Indicates the possible causes of PIM neighbor loss:
  • Hold time expired

  • Receive hello message with holdTime zero

  • BFD session down

  • PIM status of the interface changes

NeighborIpAddress Indicates the IP address of a neighbor.
Interface Indicates the name of an interface.
FlCode Indicates the name of the source code file and the line number of this log message.

Possible Causes

1. The interface did not receive any Hello message within a certain period, which caused the timeout of the PIM neighbor relationship.

2. The interface received a Hello message with the Holdtime field being 0.

3. The BFD session on the interface was Down.

4. PIM status of the interface changes.


  1. Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface verbose command to check whether the interface is in the Up state and check the BFD session status. Ensure that the link can work normally.
  2. Collect log information and configuration information, and then contact technical support personnel.
Updated: 2019-05-29

Document ID: EDOC1000097294

Views: 97204

Downloads: 35

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next