Contents

PIM-STD-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

pimNeighborLoss· 1

pimInvalidRegister 3

pimInvalidJoinPrune· 4

pimRPMappingChange· 6

pimInterfaceElection· 7

 

 

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 (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.

Object

OID (object name)	Description	Index	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 the 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.

pimInvalidRegister

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.157.0.2	An invalid PIM register message was received.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an invalid PIM register message is received. A PIM register message is invalid if the device is not the RP corresponding to the group address in the message or the group address is in the SSM range of the device.

System impact

Multicast sources might fail to be registered with the RP.

Status control

ON

CLI: Use the snmp-agent trap enable pim invalid-register command.

CLI: Use the snmp-agent trap enable pim6 invalid-register command.

OFF

CLI: Use the undo snmp-agent trap enable pim invalid-register command.

CLI: Use the undo snmp-agent trap enable pim6 invalid-register command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.157.1.13.1.7 (pimGroupMappingPimMode)	PIM mode.	pimGroupMappingOrigin pimGroupMappingAddressType pimGroupMappingGrpAddress pimGroupMappingGrpPrefixLength pimGroupMappingRPAddressType pimGroupMappingRPAddress	PimMode	Standard MIB values.
1.3.6.1.2.1.157.1.33 (pimInvalidRegisterAddressType)	Address type of the register message.	N/A	InetAddressType	Standard MIB values.
1.3.6.1.2.1.157.1.34 (pimInvalidRegisterOrigin)	Source address of the register message.	N/A	InetAddress	Standard MIB values.
1.3.6.1.2.1.157.1.35 (pimInvalidRegisterGroup)	Group address of the register message.	N/A	InetAddress	Standard MIB values.
1.3.6.1.2.1.157.1.36 (pimInvalidRegisterRp)	Destination address of the register message.	N/A	InetAddress	Standard MIB values.

 

Recommended action

To resolve the issue if the device is not the RP corresponding to the group address in the packet:

1.Modify the source DR or RP configuration.

You can use the display pim rp-info or display ipv6 pim rp-info command to identify whether the device is the RP corresponding to the group address in the packet.

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

To resolve the issue if the group address in the packet is not in the SSM range of the device:

3.Modify an SSM range to make sure the SSM ranges on the local device and on the peer device are the same.

You can use the display current-configuration command to identify whether the group address in the packet is in the SSM range of the device.

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

pimInvalidJoinPrune

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.157.0.3	An invalid PIM join/prune message was received.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an invalid PIM join/prune message is received. A PIM join/prune message is invalid if the RP address in a PIM join/prune message is different from the RP address on the device or the group address in a (*,G) or (S,G,RPT) join/prune message is in the SSM range of the device.

System impact

Multicast member information might fail to reach the RP, and multicast traffic forwarding might be affected.

Status control

ON

CLI: Use the snmp-agent trap enable pim invalid-join-prune command.

CLI: Use the snmp-agent trap enable pim6 invalid-join-prune command.

OFF

CLI: Use the undo snmp-agent trap enable pim invalid-join-prune command.

CLI: Use the undo snmp-agent trap enable pim6 invalid-join-prune command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.157.1.13.1.7 (pimGroupMappingPimMode)	PIM mode.	pimGroupMappingOrigin pimGroupMappingAddressType pimGroupMappingGrpAddress pimGroupMappingGrpPrefixLength pimGroupMappingRPAddressType pimGroupMappingRPAddress	PimMode	Standard MIB values.
1.3.6.1.2.1.157.1.39 (pimInvalidJoinPruneAddressType)	Address type of the join/prune message.	N/A	InetAddressType	Standard MIB values.
1.3.6.1.2.1.157.1.40 (pimInvalidJoinPruneOrigin)	Source address of the join/prune message.	N/A	InetAddress	Standard MIB values.
1.3.6.1.2.1.157.1.41 (pimInvalidJoinPruneGroup)	Group address of the join/prune message.	N/A	InetAddress	Standard MIB values.
1.3.6.1.2.1.157.1.42 (pimInvalidJoinPruneRp)	Destination address of the join/prune message	N/A	InetAddress	Standard MIB values.
1.3.6.1.2.1.157.1.2.1.6 (pimNeighborUpTime)	Neighbor uptime.	pimNeighborIfIndex pimNeighborAddressType pimNeighborAddress	TimeTicks	Standard MIB values.

 

Recommended action

To resolve the issue if the RP address in a PIM join/prune message is different from the RP address for the multicast group:

1.Modify the RP address to make sure the two RP addresses are the same.

You can use the display pim rp-info or display ipv6 pim rp-info command to view RP address information.

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

To resolve the issue if the RP address in the group address in a (*,G) or (S,G,RPT) join/prune message is in the SSM range of the device:

3.Modify an SSM range to make sure the SSM ranges on the local device and on the peer device are the same.

You can use the display current-configuration command to view SSM range information.

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

pimRPMappingChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.157.0.4	RP change.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated for the following possible reasons:

The configuration of the RP changes.

The RP fails.

An RP is added.

System impact

The source and multicast group members might fail to communicate, affecting multicast services.

Status control

ON

CLI: Use the snmp-agent trap enable pim rp-mapping-change command.

CLI: Use the snmp-agent trap enable pim6 rp-mapping-change command.

OFF

CLI: Use the undo snmp-agent trap enable pim rp-mapping-change command.

CLI: Use the undo snmp-agent trap enable pim6 rp-mapping-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.157.1.13.1.7 (pimGroupMappingPimMode)	PIM mode.	pimGroupMappingOrigin pimGroupMappingAddressType pimGroupMappingGrpAddress pimGroupMappingGrpPrefixLength pimGroupMappingRPAddressType pimGroupMappingRPAddress	PimMode	Standard MIB values.
1.3.6.1.2.1.157.1.13.1.8 (pimGroupMappingPrecedence)	Priority	pimGroupMappingOrigin pimGroupMappingAddressType pimGroupMappingGrpAddress pimGroupMappingGrpPrefixLength pimGroupMappingRPAddressType pimGroupMappingRPAddress	Unsigned32	Standard MIB values.

 

Recommended action

If the RP change is not desired, configure the device as a static RP or increase the priority of the original RP.

If the RP change is desired, no action is required.

pimInterfaceElection

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.157.0.5	DR change.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated for the following possible reasons:

A PIM interface receives a hello packet, and the DR priority or IP address of the interface is higher than that of all other interface on the shared network segment.

A PIM interface does not receive hello packets from other interfaces during the first hello interval after the interface comes up.

System impact

The RP might receive incorrect Register messages if the multicast source-side DR changes. The RP might receive incorrect Join messages if the multicast receiver-side DR changes.

Status control

ON

CLI: Use the snmp-agent trap enable pim interface-election command.

CLI: Use the snmp-agent trap enable pim6 interface-election command.

OFF

CLI: Use the undo snmp-agent trap enable pim interface-election command.

CLI: Use the undo snmp-agent trap enable pim6 interface-election command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.157.1.1.1.3 (pimInterfaceAddressType)	Interface address type.	pimInterfaceIfIndex pimInterfaceIPVersion	InetAddressType	Standard MIB values.
1.3.6.1.2.1.157.1.1.1.4 (pimInterfaceAddress)	Interface address	pimInterfaceIfIndex pimInterfaceIPVersion	InetAddress	Standard MIB values.

 

Recommended action

If the DR change is not desired, configure a lower DR priority or a lower IP address.

If the DR change is desired, no action is required.