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

Reminder

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

upgrade

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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

PIM/4/NBR_DOWN

Message

PIM/4/NBR_DOWN:In the VPN instance, a neighbor was deleted from the interface. (VPNName=[VPNName], NbrAddr=[NbrAddr], IfName=[IfName], Reason=[Reason], CpuUsage=[CpuUsage]%, LastHelloTime=[LastHelloTime])

Description

In the VPN instance, a neighbor was deleted from the interface.

Parameters

Parameter Name Parameter Meaning
VPNName Name of the VPN instance
NbrAddr IP address of the neighbor
IfName Interface name
Reason Possible cause of PIM neighbor loss, which can be one of the following:
  • The neighbor relationship expired.

  • A Hello packet with the holdtime 0 was received.

  • The BFD session went Down.

  • PIM silent was configured on the interface.

  • An interface went Up or PIM was re-enabled.

CpuUsage CPU usage
LastHelloTime Time when the last Hello message was received

Possible Causes

Cause 1: The neighbor relationship expired.

Cause 2: A Hello packet with the holdtime 0 was received.

Cause 3: The BFD session went Down.

Cause 4: PIM silent was configured on the interface.

Cause 5: An interface went Up or PIM was re-enabled.

Procedure

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface verbose command to check whether the interface is in the Up state. Ensure that the link works normally.
  • Collect configuration information, trap messages, and log messages, and then contact technical support personnel.
  • Cause 1: The neighbor relationship expired.
    1. Run the ping command to check whether the link between PIM neighbors is Up.

      • If the link is Up, go to Step 3.
      • If the link is Down, go to Step 2.

    2. Run the display ip routing-table command to check whether the unicast route from the local device to the neighbor works properly.

      • If the route works properly, go to Step 3.
      • If the route works improperly, you can clear the alarm by rectifying the routing fault.

    3. Run the display this command in the view of the corresponding PIM neighboring interface to check whether the interface is enabled with PIM-SM.

      • If PIM-SM is enabled on the neighboring interface, the IP address of the neighboring interface changes. If the PIM neighbor relationship is not re-established after a certain period, go to Step 4.
      • If PIM-SM is not enabled on the neighboring interface, run the pim sm command in the interface view to enable PIM-SM to clear the alarm.

    4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 2: A Hello packet with the holdtime 0 was received.
    1. Run the display this command in the view of the interface connecting the neighbor to the local device to check whether the interface is enabled with PIM-SM.

      • If the interface is enabled PIM-SM, go to Step 2.
      • If the interface is not enabled with PIM-SM, run the pim sm command to enable PIM-SM on it.

    2. Run the display interface brief command on the neighboring device to check the status of the interface directly connected to the local device. Check whether the protocol layer status of the interface is Up.

      • If the protocol layer status of the interface is Up, go to Step 3.
      • If the protocol layer status is Down, run the ip address command to configure an IP address for the interface.
      • If the interface status is *Down, run the undo shutdown command.

    3. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 3: The BFD session went Down.
    1. Run the ping command to check whether the link between PIM neighbors is Up.

      • If the link is Up, go to Step 3.
      • If the link is Down, go to Step 2.

    2. Run the display interface brief command on the device to check the status of the interface directly connected to the local device. Check whether the protocol layer status of the interface is Up.

      • If the protocol layer status of the interface is Up, go to Step 3.
      • If the protocol layer status is Down, run the ip address command to configure an IP address for the interface.
      • If the interface status is *Down, run the undo shutdown command.

    3. Run the display ip routing-table command to check whether the unicast route from the local device to the neighbor works properly.

      • If the route works properly, go to Step 3.
      • If the route works improperly, you can clear the alarm by rectifying the routing fault.

    4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 4: PIM silent was configured on the interface.
    1. Run the undo pim silent command in the interface view to disable the PIM silent function.
    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 114492

Downloads: 85

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next