Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 12-PIM-BSR-MIB | 125.80 KB |
Contents
PIM-BSR-MIB
About this MIB
Use this MIB to manage PIM BSR settings.
MIB file name
rfc5240-pim-bsr.mib
Root object
iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).pimBsrMIB(172)
Tabular objects
pimBsrCandidateRPTable
About this table
This table contains the IP multicast group for which the local router is to advertise itself as a Candidate-RP.
Support for operations
Create：Not supported
Edit/Modify：Not supported
Delete：Not supported
Read：Supported
Columns
The table indexes are pimBsrCandidateRPAddressType, pimBsrCandidateRPAddress, pimBsrCandidateRPGroupAddress, and pimBsrCandidateRPGroupPrefixLength.
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
pimBsrCandidateRPAddressType (1.3.6.1.2.1.172.1.1.1.1) |
not-accessible |
InetAddressType |
ipv4(1), ipv6(2), |
Address type of a C-RP. |
Supports only values ipv4(1) and ipv6(2). |
|
pimBsrCandidateRPAddress (1.3.6.1.2.1.172.1.1.1.2) |
not-accessible |
InetAddress |
OCTET STRING (4|16) |
IP address of the C-RP. |
As per the MIB. |
|
pimBsrCandidateRPGroupAddress (1.3.6.1.2.1.172.1.1.1.3) |
not-accessible |
InetAddress |
OCTET STRING (4|16) |
IP address of the multicast group for which the C-RP is advertised. |
Supports only multicast group addresses. |
|
pimBsrCandidateRPGroupPrefixLength (1.3.6.1.2.1.172.1.1.1.4) |
not-accessible |
InetAddressPrefixLength |
Unsigned32(4..128) |
Mask of the multicast group for which the C-RP is advertised. |
Supports only multicast group addresses. |
|
pimBsrCandidateRPBidir (1.3.6.1.2.1.172.1.1.1.5) |
read-create |
TruthValue |
true(1), false(2) |
PIM mode of the multicast group range for the RP, BIDIR-PIM or PIM-SM. |
Read-only. |
|
pimBsrCandidateRPAdvTimer (1.3.6.1.2.1.172.1.1.1.6) |
read-only |
TimeTicks |
Standard MIB values. |
Time remaining before the local router sends a Candidate-RP-Advertisement to the elected BSR for this zone. |
To disable this timer, set the value of this object to 0. |
|
pimBsrCandidateRPPriority (1.3.6.1.2.1.172.1.1.1.7) |
read-create |
Unsigned32 |
Unsigned32(0..255) |
Priority for the C-RP. |
Read-only. |
|
pimBsrCandidateRPAdvInterval (1.3.6.1.2.1.172.1.1.1.8) |
read-create |
Unsigned32 |
Unsigned32(1..26214) |
Time interval between two consecutive advertisements, in seconds. |
Read-only. |
|
pimBsrCandidateRPHoldtime (1.3.6.1.2.1.172.1.1.1.9) |
read-create |
Unsigned32 |
Unsigned32(0..65535) |
Holdtime for the C-RP. |
Read-only. Value table: 1:1..65535. |
|
pimBsrCandidateRPStatus (1.3.6.1.2.1.172.1.1.1.10) |
read-create |
RowStatus |
active(1) createAndGo(4) destroy(6) |
Row status. |
Read-only. Supports only the following values: active(1), createAndGo(4), and destroy(6). |
|
pimBsrCandidateRPStorageType (1.3.6.1.2.1.172.1.1.1.11) |
read-create |
StorageType |
other(1) |
Row storage type. |
Read-only. Supports only value other(1). |
pimBsrElectedBSRRPSetTable
About this table
This table contains BSR-specific information about PIM group mappings. It supports only the public network.
Support for operations
Create：Not supported
Edit/Modify：Not supported
Delete：Not supported
Read：Supported
Columns
The table indexes are pimBsrElectedBSRGrpMappingAddrType, pimBsrElectedBSRGrpMappingGrpAddr,
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
pimBsrElectedBSRGrpMappingAddrType (1.3.6.1.2.1.172.1.2.1.2) |
not-accessible |
InetAddressType |
ipv4(1), ipv6(2) |
Address type of a multicast group. |
Supports only values ipv4(1) and ipv6(2). |
|
pimBsrElectedBSRGrpMappingGrpAddr (1.3.6.1.2.1.172.1.2.1.3) |
not-accessible |
InetAddress |
OCTET STRING (4|16) |
IP address of the multicast group. |
As per the MIB. |
|
pimBsrElectedBSRGrpMappingGrpPrefixLen (1.3.6.1.2.1.172.1.2.1.4) |
not-accessible |
InetAddressPrefixLength |
Unsigned32(4..128) |
Mask of the multicast group address. |
As per the MIB. |
|
pimBsrElectedBSRGrpMappingRPAddr (1.3.6.1.2.1.172.1.2.1.5) |
not-accessible |
InetAddress |
OCTET STRING (4|16) |
IP address of the RP to be used for the multicast group. |
As per the MIB. |
|
pimBsrElectedBSRRPSetPriority (1.3.6.1.2.1.172.1.2.1.6) |
read-only |
Unsigned32 |
Unsigned32(0..255) |
Priority of the RP. |
As per the MIB. |
|
pimBsrElectedBSRRPSetHoldtime (1.3.6.1.2.1.172.1.2.1.7) |
read-only |
Unsigned32 |
Unsigned32(0..65535) |
Holdtime of the RP. |
As per the MIB. |
|
pimBsrElectedBSRRPSetExpiryTime (1.3.6.1.2.1.172.1.2.1.8) |
read-only |
TimeTicks |
Standard MIB values. |
Minimum time remaining before this entry will be aged out. |
Value zero indicates that the entry will age out immediately. |
|
pimBsrElectedBSRRPSetGrpBidir (1.3.6.1.2.1.172.1.2.1.9) |
read-only |
TruthValue |
true(1), false(2) |
PIM mode used for the multicast group, BIDIR-PIM or PIM-SM. |
As per the MIB. |
pimBsrCandidateBSRTable
About this table
This table contains C-BSR settings.
Support for operations
Create：Supported
Edit/Modify：Supported
Delete：Supported
Read：Supported
Columns
The table index is pimBsrCandidateBSRZoneIndex.
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
pimBsrCandidateBSRZoneIndex (1.3.6.1.2.1.172.1.3.1.1) |
not-accessible |
InetZoneIndex |
Unsigned32(1..4294967295) |
Index of the zone to which a C-BSR is attached. |
Supports only 0xFFFFFFFF 0X7FFFFFFF. |
|
pimBsrCandidateBSRAddressType (1.3.6.1.2.1.172.1.3.1.2) |
read-create |
InetAddressType |
ipv4(1), ipv6(2) |
Address type of the C-BSR. |
Supports only values ipv4(1) and ipv6(2). |
|
pimBsrCandidateBSRAddress (1.3.6.1.2.1.172.1.3.1.3) |
read-create |
InetAddress |
OCTET STRING (4|16) |
IP address of the C-BSR. |
As per the MIB. |
|
pimBsrCandidateBSRPriority (1.3.6.1.2.1.172.1.3.1.4) |
read-create |
Unsigned32 |
Unsigned32(0..255) |
Priority of the C-BSR. |
Default: 1:64 (int). Value range: 1:0..255. |
|
pimBsrCandidateBSRHashMaskLength (1.3.6.1.2.1.172.1.3.1.5) |
read-create |
Unsigned32 |
Unsigned32(0..32) |
Mask length for the IP address of the C-BSR. |
Value range: 1:0..32. |
|
pimBsrCandidateBSRElectedBSR (1.3.6.1.2.1.172.1.3.1.6) |
read-only |
TruthValue |
true(1), false(2) |
Whether this router is a BSR. |
As per the MIB. |
|
pimBsrCandidateBSRBootstrapTimer (1.3.6.1.2.1.172.1.3.1.7) |
read-only |
TimeTicks |
Standard MIB values. |
Time remaining for this router to send the next BSR message. |
As per the MIB. |
|
pimBsrCandidateBSRStatus (1.3.6.1.2.1.172.1.3.1.8) |
read-create |
RowStatus |
active(1) createAndGo(4) destroy(6) |
Row status. |
Supports only the following values: active(1), createAndGo(4), and destroy(6). |
|
pimBsrCandidateBSRStorageType (1.3.6.1.2.1.172.1.3.1.9) |
read-create |
StorageType |
other(1) |
Row storage type. |
Read-only. Supports only value other(1). |
pimBsrElectedBSRTable
About this table
This table contains BSR settings. It supports only the public network and does not support administratively-scoped zones.
Support for operations
Create：Not supported
Edit/Modify：Not supported
Delete：Not supported
Read：Supported.
Supports only index 0xffffffff.
Supports only IPv4.
Columns
The table index is pimBsrElectedBSRZoneIndex.
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
pimBsrElectedBSRZoneIndex (1.3.6.1.2.1.172.1.4.1.1) |
not-accessible |
InetZoneIndex |
Unsigned32(1..4294967295) |
Index of the zone to which a C-BSR is attached. |
Supports only 0xFFFFFFFF 0X7FFFFFFF. |
|
pimBsrElectedBSRAddressType (1.3.6.1.2.1.172.1.4.1.2) |
read-only |
InetAddressType |
ipv4(1), ipv6(2) |
Address type of a BSR. |
Supports only values ipv4(1) and ipv6(2). |
|
pimBsrElectedBSRAddress (1.3.6.1.2.1.172.1.4.1.3) |
read-only |
InetAddress |
OCTET STRING (4|16) |
IP address of the BSR. |
As per the MIB. |
|
pimBsrElectedBSRPriority (1.3.6.1.2.1.172.1.4.1.4) |
read-only |
Unsigned32 |
Unsigned32(0..255) |
Priority of the BSR. |
As per the MIB. |
|
pimBsrElectedBSRHashMaskLength (1.3.6.1.2.1.172.1.4.1.5) |
read-only |
Unsigned32 |
Unsigned32(0..128) |
Mask length for the BSR's IP address. |
Value range: 1:0..128. |
|
pimBsrElectedBSRExpiryTime (1.3.6.1.2.1.172.1.4.1.6) |
read-only |
TimeTicks |
Standard MIB values. |
Time remaining before the BSR ages out. |
As per the 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.
