PIM/2/hwPimNeighborLoss_active

Message

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

Description

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.

Parameters

Parameter Name Parameter Meaning

NbrIntIndex

Index of the interface where the neighbor relationship is established.

NbrAddrType

Address type of the neighboring interface:

  • 0: MIB_ADDRESSTYPE_UNKNOWN
  • 1: MIB_ADDRESSTYPE_IPV4
  • 2: MIB_ADDRESSTYPE_IPV6
  • 3: MIB_ADDRESSTYPE_IPV4Z
  • 4: MIB_ADDRESSTYPE_IPV6Z
  • 16: MIB_ADDRESSTYPE_DNS
  • 17: MIB_ADDRESSTYPE_MAX

ATN950B:

Address type of the neighboring interface:

  • 0: MIB_ADDRESSTYPE_UNKNOWN
  • 1: MIB_ADDRESSTYPE_IPV4
  • 3: MIB_ADDRESSTYPE_IPV4Z
  • 16: MIB_ADDRESSTYPE_DNS
  • 17: MIB_ADDRESSTYPE_MAX

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.

Possible Causes

  • Cause 1: Neighbor timer expired.
  • Cause 3: Interface is down.
  • Cause 5: Neighbor is deleted.
  • Cause 7: Receive hello cancel message.
  • Cause 8: BFD session is down.

Procedure

  • Cause 1: Neighbor timer expired.

    1. Run the ping or ping ipv6 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 or display ipv6 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, configure the interface enable with PIM-SM.

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

  • Cause 3: Interface is down.

    1. Run the display this command in the view of the corresponding interface to check whether the pim neighbor-policy or pim ipv6 neighbor-policy command is run on the interface.

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

    2. Run the display acl or display acl ipv6 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 alarm information and configuration information, and then contact technical support personnel.

  • Cause 5: Neighbor is deleted.

    1. Run the ping or ping ipv6 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 or display ipv6 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 or ping ipv6 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 or display ipv6 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 4.
    • If the route works improperly, you can clear the alarm by rectifying the routing fault.

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

  • Cause 7: Receive hello cancel message.

    1. Run the display this command in the interface view of the neighbor to check whether PIM SM or PIM IPv6 SM is enabled on the interface.

    • If PIM SM or PIM IPv6 SM is enabled, go to step 2.
    • If PIM-SM or IPv6 PIM-SM is not enabled on the interface, run the pim sm or pim ipv6 sm command on the interface.

    2. Run the display ip interface brief or display ipv6 interface brief command to check whether the interface status is Up and whether the interface is configured with an IP address.

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

    3. Collect alarm and configuration information, and contact technical support personnel.

  • Cause 8: BFD session is down.

    1. Run the display this command in the interface view of the neighbor to check whether PIM SM or PIM IPv6 SM is enabled on the interface.

    • If PIM SM or PIM IPv6 SM is enabled, go to step 2.
    • If PIM-SM or IPv6 PIM-SM is not enabled on the interface, run the pim sm or pim ipv6 sm command on the interface.

    2. Run the display ip interface brief or display ipv6 interface brief command to check whether the interface status is Up.

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

    3. Check whether the route to the peer device is normal using the display ip routing-table or display ipv6 routing-table command.

    • If the route is normal, go to Step 4.
    • If the route is abnormal, configure a route to the peer device.

    4. Collect alarm and configuration information, and contact technical support personnel.

Parent Topic: PIM
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >