Contents

PIM-STD-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

pimNeighborLoss· 1

PIM-STD-MIB

About this MIB

Use this MIB to manage PIM routers.

MIB file name

rfc5060-pim-std.mib

Notifications

pimNeighborLoss

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.157.0.1	PIM neighbor loss.	Informational	Warning	N/A	ON

 

Notification triggers

This notification is generated when the timer of a neighbor expires and no neighbor of the same IP version and with a lower IP address exists.

This notification might be generated for the following reasons:

·     The hold timer of the PIM neighbor expires.

·     The interface where the PIM neighbor resides goes down.

·     The PIM neighbor is deleted.

·     The device receives a neighbor message with the hold time as 0.

·     The BFD session of the neighbor goes down.

System impact

A connection will fail to be established, and data forwarding will be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable pim neighbor-loss command.

CLI: Use the snmp-agent trap enable pim6 neighbor-loss command.

OFF

CLI: Use the undo snmp-agent trap enable pim neighbor-loss command.

CLI: Use the undo snmp-agent trap enable pim6 neighbor-loss command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.2.1.157.1.2.1.6 (pimNeighborUpTime)	Time since the neighbor has come up.	pimNeighborIfIndex pimNeighborAddressType pimNeighborAddress	TimeTicks	Standard MIB values.

 

Recommended action

To resolve this issue:

1.     Use the display this command to identify whether the pim neighbor-policy or ipv6 pim neighbor-policy command is executed on the interface.

¡     If yes, go to step 2.

¡     If no, go to step 3.

2.     Use the display acl or display acl ipv6 command to identify whether the neighbor is permitted by the ACL.

¡     If yes, go to step 3.

¡     If no, reconfigure the ACL to permit the neighbor.

3.     Use the display interface command on the local device and the neighbor device to identify the physical state of the interface.

¡     If the physical state is Administratively DOWN, execute the undo shutdown command.

¡     If the physical state is Down, check the physical connection (including whether the network cable and transceiver module are loose or disconnected), and reconnect the physical connection.

¡     If the physical state is Up, go to step 4.

4.     Use the display ip interface or display ipv6 interface command on the local device and the neighbor device to identify the protocol state of the interface.

¡     If the protocol state is Up, go to step 5.

¡     If the protocol state is Down, use the ip address or ipv6 address command to assign an IP address to the interface.

5.     Use the display this command on the local device and the neighbor device to identify whether the interface is enabled with PIM SM or IPv6 PIM SM.

¡     If yes, go to step 6.

¡     If no, execute the pim sm or ipv6 pim sm command on the interface.

6.     Use the display current-configuration command on the local device and the neighbor device to identify whether the VPN instance is enabled multicast routing or IPv6 multicast routing.

¡     If yes, go to step 7.

¡     If no, execute the multicast routing or ipv6 multicast routing command on the interface.

7.     Use the display memory command on the local device and the neighbor device to identify the memory usage.

¡     If the memory is insufficient, address the memory issue.

¡     If the memory is sufficient, go to step 8.

8.     Use the ping or ping ipv6 command on the local device to test the connectivity with the neighbor device.

¡     If the ping succeeds, go to step 10.

¡     If the ping fails, go to step 9.

9.     Use the display ip routing-table or display ipv6 routing-table command on the local device and the neighbor device to identify the unicast routes to each other are normal.

¡     If the unicast routes are normal, go to step 10.

¡     If the unicast routes are abnormal, address the route issues.

10.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.