Contents

PIM-BSR-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

pimBsrElectedBSRLostElection· 1

pimBsrCandidateBSRWinElection· 2

 

 

PIM-BSR-MIB

About this MIB

Use this MIB to manage PIM BSR settings.

MIB file name

rfc5240-pim-bsr.mib

Notifications

pimBsrElectedBSRLostElection

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.172.0.1	The device changed from the BSR to a C-BSR.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the BSR becomes a C-BSR because another device is elected as the new BSR.

System impact

The BSR change might affect the advertisement of RP information, interrupt the exchange of source and group member information, and affect multicast traffic forwarding.

Status control

ON

CLI: Use the snmp-agent trap enable pim elected-bsr-lost-election command.

CLI: Use the snmp-agent trap enable pim6 elected-bsr-lost-election command.

OFF

CLI: Use the undo snmp-agent trap enable pim elected-bsr-lost-election command.

CLI: Use the undo snmp-agent trap enable pim6 elected-bsr-lost-election command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.172.1.4.1.2 (pimBsrElectedBSRAddressType)	Address type of the BSR.	pimBsrElectedBSRZoneIndex	InetAddressType	ipv4(1), ipv6(2)
1.3.6.1.2.1.172.1.4.1.3 (pimBsrElectedBSRAddress)	IP address of the BSR.	pimBsrElectedBSRZoneIndex	InetAddress	OCTET STRING (4|16)
1.3.6.1.2.1.172.1.4.1.4 (pimBsrElectedBSRPriority)	Priority of the BSR.	pimBsrElectedBSRZoneIndex	Unsigned32	Unsigned32(0..255)

 

Recommended action

To resolve the issue:

1.Check whether the configuration of the old BSR is modified.

  - If yes, no action is required.

  - If no, proceed to step 2.

2.Check whether the new BSR has recovered from a failure, whether the link between the old BSR and the new BSR has recovered from a failure, whether the new BSR is newly added, .or whether the configuration of the new BSR has been modified.

  - If yes, no action is required.

  - If no, proceed to step 3.

3.Use the display this command to check whether the old BSR has been configured with a correct BSR address.

  - If no, configure a correct BSR address.

  - If yes, proceed to step 4.

4.Use the display pim bsr-info or display ipv6 pim bsr-info command to check whether the old BSR is a C-BSR.

  - If no, proceed to step 5.

  - If yes, proceed to step 6.

5.Use the display pim bsr-info or display ipv6 pim bsr-info command to check whether a PIM interface exists for the old BSR.

  - If no, configure a PIM interface.

  - If yes, proceed to step 6.

6.Use the display memory command to check whether the memory is sufficient.

  - If no, solve the memory issue.

  - If yes, proceed to step 7.

7.Collect alarm information and configuration data, and then contact H3C Support for help.

pimBsrCandidateBSRWinElection

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.172.0.2	The device changed from a C-BSR to the BSR.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when a C-BSR was elected as the new BSR. A C-BSR can be elected as the new BSR for the following possible reasons:

The configuration of the old BSR is modified.

The link between the new BSR and the old BSR fails.

The old BSR fails.

System impact

The BSR change might affect the advertisement of RP information, interrupt the exchange of source and group member information, and affect multicast traffic forwarding.

Status control

ON

CLI: Use the snmp-agent trap enable pim candidate-bsr-win-election command.

CLI: Use the snmp-agent trap enable pim6 candidate-bsr-win-election command.

OFF

CLI: Use the undo snmp-agent trap enable pim candidate-bsr-win-election command.

CLI: Use the undo snmp-agent trap enable pim6 candidate-bsr-win-election command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.172.1.3.1.6 (pimBsrCandidateBSRElectedBSR)	Whether this router is the E-BSR.	pimBsrCandidateBSRZoneIndex	TruthValue	true(1), false(2)

 

Recommended action

To resolve the issue:

1.Check whether the configuration of the old BSR is modified.

  - If yes, no action is required.

  - If no, proceed to step 2.

2.Check whether the old BSR has failed, whether the link between the old BSR and the new BSR has recovered from a failure, or whether the old BSR has been removed as a C-BSR.

  - If yes, no action is required.

  - If no, proceed to step 3.

3.Use the display pim bsr-info or display ipv6 pim bsr-info command to check whether a PIM interface exists for the old BSR.

  - If no, configure a PIM interface.

  - If yes, proceed to step 4.

4.Use the display memory command to check whether the memory is sufficient.

  - If no, solve the memory issue.

  - If yes, proceed to step 5.

5.Use the ping or ping ipv6 command to check whether the new BSR can reach the old BSR.

  - If no, solve the connectivity issue.

  - If yes, proceed to step 6.

6.Collect alarm information and configuration data, and then contact H3C Support for help.