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

Alarm Handling

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document provides the explanations, causes, and recommended actions of alarms 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_1.3.6.1.4.1.2011.5.25.149.4.0.1 neighbor-loss

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.1 neighbor-loss

Description

PIM neighbor loss. (NbrIntIndex=[NbrIntIndex], NbrAddrType=[NbrAddrType], NbrAddr=[NbrAddr], NbrUpTime=[NbrUpTime], NbrIntName=[NbrIntName], InstanceID=[InstanceID], InstanceName=[InstanceName], NeighborLossReason=[NeighborLossReason])

After receiving a Hello message from a neighbor, a device recorded information about this neighbor and started a timer for this neighbor. If the device received no Hello packet before the timer expired, the device considered the neighbor lost, and thereby reported a trap message.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

neighbor-loss

Trap OID

1.3.6.1.4.1.2011.5.25.149.4.0.1

Alarm ID

0x08850001

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.6 hwPimNeighborAdd

Parameters

Parameter Description

NbrIntIndex

Index of the interface where the neighbor relationship is established.

NbrAddrType

Address family of a PIM neighbor

NbrAddr

Neighbor address

NbrUpTime

Time since the neighbor relationship is established

NbrIntName

Name of the interface where the neighbor relationship is established

InstanceID

Instance index

InstanceName

Instance name

NeighborLossReason

Reason why the neighbor relationship is unavailable

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.149.4.1.2.1.6

hwPimNeighborUpTime

hwPimNeighborIfIndex;

hwPimNeighborAddressType;

hwPimNeighborAddress;

1.3.6.1.4.1.2011.5.25.149.4.1.2.1.16

hwPimNeighborIfName

hwPimNeighborIfIndex;

hwPimNeighborAddressType;

hwPimNeighborAddress;

1.3.6.1.4.1.2011.5.25.149.4.1.57

hwPimInstanceID

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.60

hwPimInstanceName

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.61

hwPimNeighborNotificationReason

N/A

Impact on the System

The PIM neighbor relationship is interrupted or fails to be established, the route is unreachable, and data forwarding services are interrupted.

Possible Causes

Cause 1: Neighbor timer expired.

Cause 2: Interface is down.

Cause 3: Neighbor is deleted.

Cause 4: Receive hello cancel message.

Cause 5: BFD session is down.

Procedure

  • Cause 1: Neighbor timer 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 log messages and contact technical support personnel.
  • Cause 2: Interface is down.
    1. Run the display interface brief command to check the physical layer status and the protocol layer status of the interface. First, check whether the protocol layer status of the interface is up.

      • If the protocol layer status of the interface is up, go to Step 2.
      • If the protocol layer status is down, run the ip address command to configure an IP address for the interface.

    2. Check whether the physical layer status of the interface is up.

      • If the physical layer status of the interface is up, go to Step 3.
      • If the physical layer status of the interface is down, the interface is Down. Then, locate the fault on the interface.
      • If the physical layer status is of the interface *down, the shutdown command is run on the interface. In this case, run the undo shutdown command on the interface to clear the alarm.

    3. Collect log messages and contact technical support personnel.
  • Cause 3: Neighbor is deleted.
    1. Run the display this command in the view of the corresponding interface to check whether the pim neighbor-policy command is run on the interface.

      • If the pim neighbor-policy command is run on the interface, go to Step 2.
      • If the pim neighbor-policy command is not run on the interface, go to Step 3.

    2. Run the display acl command to check whether the ACL configuration is proper.

      • If the ACL configuration is proper, go to Step 3.
      • If the ACL configuration is improper, reconfigure ACL rules.

    3. Collect log messages and contact technical support personnel.
  • Cause 4: Receive hello cancel message.
    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 log messages and contact technical support personnel.
  • Cause 5: BFD session is 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 log messages and contact technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17569

Downloads: 25

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