PIM_1.3.6.1.4.1.2011.5.25.149.4.0.1 hwPimNeighborLoss

Description

PIM/2/NBRLOSS:OID [oid] PIM neighbor loss. (NbrIntIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], NbrUpTime=[timetick], NbrIntName=[string], InstanceID=[integer], InstanceName=[string], NeighborLossReason=[integer])

The PIM neighbor was lost.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.149.4.0.1	Major	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
NbrIntIndex	Indicates the index of a neighbor.
NbrAddrType	Indicates the inetAddressType of neighbor address. The value can be: 1: IPv4 address 2: IPv6 address
NbrAddr	Indicates the address of a neighbor.
NbrUpTime	Indicates the period during which the neighbor relationship is in the Up state.
NbrIntName	Indicates the name of the neighbor interface.
InstanceID	Indicates the ID of the instance to which the neighbor interface belongs.
InstanceName	Indicates the name of the instance to which the neighbor interface belongs.
NeighborLossReason	Indicates a possible cause for PIM neighbor loss. 1: The neighbor relationship expires. 7: Hello messages with the holdtime 0 are received. 8: The BFD session goes Down. 9: A user manually tears down the PIM neighbor relationship.

Impact on the System

The PIM neighbor is disconnected, which has impact on multicast services.

Possible Causes

1. The timer of the PIM neighbor expired.

2. The wireless access controller received a Hello message with the Holdtime value being 0.

Procedure

Run the display pim interface interface-type interface-number command on the neighboring wireless access controller to check whether PIM is enabled on the interface that connects the local wireless access controller.
- If so, go to Step 3.
- If not, go to Step 2.
Run the pim dm or pim sm command on the interface that connects the local wireless access controller to enable PIM. Run the display pim neighbor neighbor-address command on the neighboring wireless access controller to check whether the PIM neighbor of the local wireless access controller is established.
- If so, go to Step 6.
- If not, go to Step 3.
Run the display ip routing-table ip-address command on the neighboring wireless access controller to check whether the route to the local wireless access controller exists.
- If so, go to Step 5.
- If not, go to Step 4.
Confirm that no unicast route is faulty. Run the display pim neighbor neighbor-address command on the neighboring wireless access controller to check whether the PIM neighborship is established between the local wireless access controller and its neighbor.
- If so, go to Step 6.
- If not, go to Step 5.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None