pimGroupMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF PimGroupMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing mappings from multicast
group prefixes to the PIM mode and RP address to use for
groups within that group prefix.
Rows in this table are created for a variety of reasons,
indicated by the value of the pimGroupMappingOrigin object.
- Rows with a pimGroupMappingOrigin value of \fixed\ are
created automatically by the router at startup, to
correspond to the well-defined prefixes of link-local and
unroutable group addresses. These rows are never
destroyed.
- Rows with a pimGroupMappingOrigin value of \embedded\ are
created by the router to correspond to group prefixes
that are to be treated as being in Embedded-RP format.
- Rows with a pimGroupMappingOrigin value of \configRp\ are
created and destroyed as a result of rows in the
pimStaticRPTable being created and destroyed.
- Rows with a pimGroupMappingOrigin value of \configSsm\
are created and destroyed as a result of configuration of
SSM address ranges to the local router.
- Rows with a pimGroupMappingOrigin value of \bsr\ are
created as a result of running the PIM Bootstrap Router
(BSR) mechanism. If the local router is not the elected
BSR, these rows are created to correspond to group
prefixes in the PIM Bootstrap messages received from the
elected BSR. If the local router is the elected BSR,
these rows are created to correspond to group prefixes in
the PIM Bootstrap messages that the local router sends.
In either case, these rows are destroyed when the group
prefixes are timed out by the BSR mechanism.
- Rows with a pimGroupMappingOrigin value of \other\ are
created and destroyed according to some other mechanism
not specified here.
Given the collection of rows in this table at any point in
time, the PIM mode and RP address to use for a particular
group is determined using the following algorithm.
1. From the set of all rows, the subset whose group prefix
contains the group in question are selected.
2. If there are no such rows, then the group mapping is
undefined.
3. If there are multiple selected rows, and a subset is
defined by pimStaticRPTable (pimGroupMappingOrigin value
of \configRp\) with pimStaticRPOverrideDynamic set to
TRUE, then this subset is selected.
4. From the selected subset of rows, the subset that have
the greatest value of pimGroupMappingGrpPrefixLength are
selected.
5. If there are still multiple selected rows, the subset
that has the highest precedence (the lowest numerical
value for pimGroupMappingPrecedence) is selected.
6. If there are still multiple selected rows, the row
selected is implementation dependent; the implementation
might or might not apply the PIM hash function to select
the row.
7. The group mode to use is given by the value of
pimGroupMappingPimMode from the single selected row; the
RP to use is given by the value of
pimGroupMappingRPAddress, unless pimGroupMappingOrigin is
\embedded\, in which case, the RP is extracted from the
group address in question."
REFERENCE "RFC 4601 section 3.7, RFC 3956, and RFC 4610"
View at oid-info.com
The (conceptual) table listing mappings from multicast
group prefixes to the PIM mode and RP address to use for
groups within that group prefix.
Rows in this table are created for a variety of reasons,
indicated by the value of the pimGroupMappingOrigin object.
- Rows with a pimGroupMappingOrigin value of 'fixed' are
created automatically by the router at startup, to
correspond to the well-defined prefixes of link-local and
unroutable group addresses. These rows are never
destroyed.
- Rows with a pimGroupMappingOrigin value of 'embedded' are
created by the router to correspond to group prefixes
that are to be treated as being in Embedded-RP format.
- Rows with a pimGroupMappingOrigin value of 'configRp' are
created and destroyed as a result of rows in the
pimStaticRPTable being created and destroyed.
- Rows with a pimGroupMappingOrigin value of 'configSsm'
are created and destroyed as a result of configuration of
SSM address ranges to the local router.
- Rows with a pimGroupMappingOrigin value of 'bsr' are
created as a result of running the PIM Bootstrap Router
(BSR) mechanism. If the local router is not the elected
BSR, these rows are created to correspond to group
prefixes in the PIM Bootstrap messages received from the
elected BSR. If the local router is the elected BSR,
these rows are created to correspond to group prefixes in
the PIM Bootstrap messages that the local router sends.
In either case, these rows are destroyed when the group
prefixes are timed out by the BSR mechanism.
- Rows with a pimGroupMappingOrigin value of 'other' are
created and destroyed according to some other mechanism
not specified here.
Given the collection of rows in this table at any point in
time, the PIM mode and RP address to use for a particular
group is determined using the following algorithm.
1. From the set of all rows, the subset whose group prefix
contains the group in question are selected.
2. If there are no such rows, then the group mapping is
undefined.
3. If there are multiple selected rows, and a subset is
defined by pimStaticRPTable (pimGroupMappingOrigin value
of 'configRp') with pimStaticRPOverrideDynamic set to
TRUE, then this subset is selected.
4. From the selected subset of rows, the subset that have
the greatest value of pimGroupMappingGrpPrefixLength are
selected.
5. If there are still multiple selected rows, the subset
that has the highest precedence (the lowest numerical
value for pimGroupMappingPrecedence) is selected.
6. If there are still multiple selected rows, the row
selected is implementation dependent; the implementation
might or might not apply the PIM hash function to select
the row.
7. The group mode to use is given by the value of
pimGroupMappingPimMode from the single selected row; the
RP to use is given by the value of
pimGroupMappingRPAddress, unless pimGroupMappingOrigin is
'embedded', in which case, the RP is extracted from the
group address in question.
Parsed from file rfc5060-Protocol-Independent-Multicast-PIM.mib.txt
Company: None
Module: PIM-STD-MIB
The (conceptual) table listing mappings from multicast
group prefixes to the PIM mode and RP address to use for
groups within that group prefix.
Rows in this table are created for a variety of reasons,
indicated by the value of the pimGroupMappingOrigin object.
- Rows with a pimGroupMappingOrigin value of 'fixed' are
created automatically by the router at startup, to
correspond to the well-defined prefixes of link-local and
unroutable group addresses. These rows are never
destroyed.
- Rows with a pimGroupMappingOrigin value of 'embedded' are
created by the router to correspond to group prefixes
that are to be treated as being in Embedded-RP format.
- Rows with a pimGroupMappingOrigin value of 'configRp' are
created and destroyed as a result of rows in the
pimStaticRPTable being created and destroyed.
- Rows with a pimGroupMappingOrigin value of 'configSsm'
are created and destroyed as a result of configuration of
SSM address ranges to the local router.
- Rows with a pimGroupMappingOrigin value of 'bsr' are
created as a result of running the PIM Bootstrap Router
(BSR) mechanism. If the local router is not the elected
BSR, these rows are created to correspond to group
prefixes in the PIM Bootstrap messages received from the
elected BSR. If the local router is the elected BSR,
these rows are created to correspond to group prefixes in
the PIM Bootstrap messages that the local router sends.
In either case, these rows are destroyed when the group
prefixes are timed out by the BSR mechanism.
- Rows with a pimGroupMappingOrigin value of 'other' are
created and destroyed according to some other mechanism
not specified here.
Given the collection of rows in this table at any point in
time, the PIM mode and RP address to use for a particular
group is determined using the following algorithm.
1. From the set of all rows, the subset whose group prefix
contains the group in question are selected.
2. If there are no such rows, then the group mapping is
undefined.
3. If there are multiple selected rows, and a subset is
defined by pimStaticRPTable (pimGroupMappingOrigin value
of 'configRp') with pimStaticRPOverrideDynamic set to
TRUE, then this subset is selected.
4. From the selected subset of rows, the subset that have
the greatest value of pimGroupMappingGrpPrefixLength are
selected.
5. If there are still multiple selected rows, the subset
that has the highest precedence (the lowest numerical
value for pimGroupMappingPrecedence) is selected.
6. If there are still multiple selected rows, the row
selected is implementation dependent; the implementation
might or might not apply the PIM hash function to select
the row.
7. The group mode to use is given by the value of
pimGroupMappingPimMode from the single selected row; the
RP to use is given by the value of
pimGroupMappingRPAddress, unless pimGroupMappingOrigin is
'embedded', in which case, the RP is extracted from the
group address in question.
Parsed from file PIM-STD-MIB.mib
Module: PIM-STD-MIB
Automatically extracted from RFC5060
pimGroupMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF PimGroupMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing mappings from multicast group prefixes to the PIM mode and RP address to use for groups within that group prefix. Rows in this table are created for a variety of reasons, indicated by the value of the pimGroupMappingOrigin object. - Rows with a pimGroupMappingOrigin value of 'fixed' are created automatically by the router at startup, to correspond to the well-defined prefixes of link-local and unroutable group addresses. These rows are never destroyed. - Rows with a pimGroupMappingOrigin value of 'embedded' are created by the router to correspond to group prefixes that are to be treated as being in Embedded-RP format. - Rows with a pimGroupMappingOrigin value of 'configRp' are created and destroyed as a result of rows in the pimStaticRPTable being created and destroyed. - Rows with a pimGroupMappingOrigin value of 'configSsm' are created and destroyed as a result of configuration of SSM address ranges to the local router. - Rows with a pimGroupMappingOrigin value of 'bsr' are created as a result of running the PIM Bootstrap Router (BSR) mechanism. If the local router is not the elected BSR, these rows are created to correspond to group prefixes in the PIM Bootstrap messages received from the elected BSR. If the local router is the elected BSR, these rows are created to correspond to group prefixes in the PIM Bootstrap messages that the local router sends. In either case, these rows are destroyed when the group prefixes are timed out by the BSR mechanism. - Rows with a pimGroupMappingOrigin value of 'other' are created and destroyed according to some other mechanism not specified here. Given the collection of rows in this table at any point in time, the PIM mode and RP address to use for a particular group is determined using the following algorithm. 1. From the set of all rows, the subset whose group prefix contains the group in question are selected. 2. If there are no such rows, then the group mapping is undefined. 3. If there are multiple selected rows, and a subset is defined by pimStaticRPTable (pimGroupMappingOrigin value of 'configRp') with pimStaticRPOverrideDynamic set to TRUE, then this subset is selected. 4. From the selected subset of rows, the subset that have the greatest value of pimGroupMappingGrpPrefixLength are selected. 5. If there are still multiple selected rows, the subset that has the highest precedence (the lowest numerical value for pimGroupMappingPrecedence) is selected. 6. If there are still multiple selected rows, the row selected is implementation dependent; the implementation might or might not apply the PIM hash function to select the row. 7. The group mode to use is given by the value of pimGroupMappingPimMode from the single selected row; the RP to use is given by the value of pimGroupMappingRPAddress, unless pimGroupMappingOrigin is 'embedded', in which case, the RP is extracted from the group address in question." REFERENCE "RFC 4601 section 3.7, RFC 3956, and RFC 4610" ::= { pim 13 }
pimGroupMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF PimGroupMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing mappings from multicast group prefixes to the PIM mode and RP address to use for groups within that group prefix. Rows in this table are created for a variety of reasons, indicated by the value of the pimGroupMappingOrigin object. - Rows with a pimGroupMappingOrigin value of 'fixed' are created automatically by the router at startup, to correspond to the well-defined prefixes of link-local and unroutable group addresses. These rows are never destroyed. - Rows with a pimGroupMappingOrigin value of 'embedded' are created by the router to correspond to group prefixes that are to be treated as being in Embedded-RP format. - Rows with a pimGroupMappingOrigin value of 'configRp' are created and destroyed as a result of rows in the pimStaticRPTable being created and destroyed. - Rows with a pimGroupMappingOrigin value of 'configSsm' are created and destroyed as a result of configuration of SSM address ranges to the local router. - Rows with a pimGroupMappingOrigin value of 'bsr' are created as a result of running the PIM Bootstrap Router (BSR) mechanism. If the local router is not the elected BSR, these rows are created to correspond to group prefixes in the PIM Bootstrap messages received from the elected BSR. If the local router is the elected BSR, these rows are created to correspond to group prefixes in the PIM Bootstrap messages that the local router sends. In either case, these rows are destroyed when the group prefixes are timed out by the BSR mechanism. - Rows with a pimGroupMappingOrigin value of 'other' are created and destroyed according to some other mechanism not specified here. Given the collection of rows in this table at any point in time, the PIM mode and RP address to use for a particular group is determined using the following algorithm. 1. From the set of all rows, the subset whose group prefix contains the group in question are selected. 2. If there are no such rows, then the group mapping is undefined. 3. If there are multiple selected rows, and a subset is defined by pimStaticRPTable (pimGroupMappingOrigin value of 'configRp') with pimStaticRPOverrideDynamic set to TRUE, then this subset is selected. 4. From the selected subset of rows, the subset that have the greatest value of pimGroupMappingGrpPrefixLength are selected. 5. If there are still multiple selected rows, the subset that has the highest precedence (the lowest numerical value for pimGroupMappingPrecedence) is selected. 6. If there are still multiple selected rows, the row selected is implementation dependent; the implementation might or might not apply the PIM hash function to select the row. 7. The group mode to use is given by the value of pimGroupMappingPimMode from the single selected row; the RP to use is given by the value of pimGroupMappingRPAddress, unless pimGroupMappingOrigin is 'embedded', in which case, the RP is extracted from the group address in question." REFERENCE "RFC 4601 section 3.7, RFC 3956, and RFC 4610" ::= { pim 13 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.157.1.13.1 | pimGroupMappingEntry | 8 | 8 | An entry (conceptual row) in the pimGroupMappingTable. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.157.1.1 | pimInterfaceTable | 1 | 29 | The (conceptual) table listing the router's PIM interfaces. PIM is enabled on all interfaces listed in this table. |
| 1.3.6.1.2.1.157.1.2 | pimNeighborTable | 1 | 16 | The (conceptual) table listing the router's PIM neighbors. |
| 1.3.6.1.2.1.157.1.3 | pimNbrSecAddressTable | 1 | 5 | The (conceptual) table listing the secondary addresses advertised by each PIM neighbor (on a subset of the rows of the pimNeighbo… |
| 1.3.6.1.2.1.157.1.4 | pimStarGTable | 1 | 21 | The (conceptual) table listing the non-interface specific (*,G) state that PIM has. |
| 1.3.6.1.2.1.157.1.5 | pimStarGITable | 1 | 13 | The (conceptual) table listing the interface-specific (*,G) state that PIM has. |
| 1.3.6.1.2.1.157.1.6 | pimSGTable | 1 | 28 | The (conceptual) table listing the non-interface specific (S,G) state that PIM has. |
| 1.3.6.1.2.1.157.1.7 | pimSGITable | 1 | 13 | The (conceptual) table listing the interface-specific (S,G) state that PIM has. |
| 1.3.6.1.2.1.157.1.8 | pimSGRptTable | 1 | 5 | The (conceptual) table listing the non-interface specific (S,G,rpt) state that PIM has. |
| 1.3.6.1.2.1.157.1.9 | pimSGRptITable | 1 | 7 | The (conceptual) table listing the interface-specific (S,G,rpt) state that PIM has. |
| 1.3.6.1.2.1.157.1.10 | pimBidirDFElectionTable | 1 | 11 | The (conceptual) table listing the per-RP Designated Forwarder (DF) Election state for each interface for all the RPs in BIDIR mo… |
| 1.3.6.1.2.1.157.1.11 | pimStaticRPTable | 1 | 10 | This table is used to manage static configuration of RPs. If the group prefixes configured for two or more rows in this table ove… |
| 1.3.6.1.2.1.157.1.12 | pimAnycastRPSetTable | 1 | 7 | This table is used to manage Anycast-RP via PIM Register messages, as opposed to via other protocols such as MSDP (Multicast Sour… |
| 1.3.6.1.2.1.157.1.14 | pimKeepalivePeriod | 1 | 1 | The duration of the Keepalive Timer. This is the period during which the PIM router will maintain (S,G) state in the absence of … |
| 1.3.6.1.2.1.157.1.15 | pimRegisterSuppressionTime | 1 | 1 | The duration of the Register Suppression Timer. This is the period during which a PIM Designated Router (DR) stops sending Regis… |
| 1.3.6.1.2.1.157.1.16 | pimStarGEntries | 1 | 1 | The number of entries in the pimStarGTable. |
| 1.3.6.1.2.1.157.1.17 | pimStarGIEntries | 1 | 1 | The number of entries in the pimStarGITable. |
| 1.3.6.1.2.1.157.1.18 | pimSGEntries | 1 | 1 | The number of entries in the pimSGTable. |
| 1.3.6.1.2.1.157.1.19 | pimSGIEntries | 1 | 1 | The number of entries in the pimSGITable. |
| 1.3.6.1.2.1.157.1.20 | pimSGRptEntries | 1 | 1 | The number of entries in the pimSGRptTable. |
| 1.3.6.1.2.1.157.1.21 | pimSGRptIEntries | 1 | 1 | The number of entries in the pimSGRptITable. |
| 1.3.6.1.2.1.157.1.22 | pimOutAsserts | 1 | 1 | The number of Asserts sent by this router. Discontinuities in the value of this counter can occur at re-initialization of the man… |
| 1.3.6.1.2.1.157.1.23 | pimInAsserts | 1 | 1 | The number of Asserts received by this router. Asserts are multicast to all routers on a network. This counter is incremented b… |
| 1.3.6.1.2.1.157.1.24 | pimLastAssertInterface | 1 | 1 | The interface on which this router most recently sent or received an assert, or zero if this router has not sent or received an a… |
| 1.3.6.1.2.1.157.1.25 | pimLastAssertGroupAddressType | 1 | 1 | The address type of the multicast group address in the most recently sent or received assert. If this router has not sent or rec… |
| 1.3.6.1.2.1.157.1.26 | pimLastAssertGroupAddress | 1 | 1 | The multicast group address in the most recently sent or received assert. The InetAddressType is given by the pimLastAssertGroup… |
| 1.3.6.1.2.1.157.1.27 | pimLastAssertSourceAddressType | 1 | 1 | The address type of the source address in the most recently sent or received assert. If the most recent assert was (*,G), or if … |
| 1.3.6.1.2.1.157.1.28 | pimLastAssertSourceAddress | 1 | 1 | The source address in the most recently sent or received assert. The InetAddressType is given by the pimLastAssertSourceAddressT… |
| 1.3.6.1.2.1.157.1.29 | pimNeighborLossNotificationPeriod | 1 | 1 | The minimum time that must elapse between pimNeighborLoss notifications originated by this router. The maximum value 65535 repre… |
| 1.3.6.1.2.1.157.1.30 | pimNeighborLossCount | 1 | 1 | The number of neighbor loss events that have occurred. This counter is incremented when the neighbor timer expires, and the route… |
| 1.3.6.1.2.1.157.1.31 | pimInvalidRegisterNotificationPeriod | 1 | 1 | The minimum time that must elapse between pimInvalidRegister notifications originated by this router. The default value of 65535 … |
| 1.3.6.1.2.1.157.1.32 | pimInvalidRegisterMsgsRcvd | 1 | 1 | The number of invalid PIM Register messages that have been received by this device. A PIM Register message is invalid if either o … |
| 1.3.6.1.2.1.157.1.33 | pimInvalidRegisterAddressType | 1 | 1 | The address type stored in pimInvalidRegisterOrigin, pimInvalidRegisterGroup, and pimInvalidRegisterRp. If no invalid Register me… |
| 1.3.6.1.2.1.157.1.34 | pimInvalidRegisterOrigin | 1 | 1 | The source address of the last invalid Register message received by this device. |
| 1.3.6.1.2.1.157.1.35 | pimInvalidRegisterGroup | 1 | 1 | The IP multicast group address to which the last invalid Register message received by this device was addressed. |
| 1.3.6.1.2.1.157.1.36 | pimInvalidRegisterRp | 1 | 1 | The RP address to which the last invalid Register message received by this device was delivered. |
| 1.3.6.1.2.1.157.1.37 | pimInvalidJoinPruneNotificationPeriod | 1 | 1 | The minimum time that must elapse between pimInvalidJoinPrune notifications originated by this router. The default value of 65535… |
| 1.3.6.1.2.1.157.1.38 | pimInvalidJoinPruneMsgsRcvd | 1 | 1 | The number of invalid PIM Join/Prune messages that have been received by this device. A PIM Join/Prune message is invalid if eith… |
| 1.3.6.1.2.1.157.1.39 | pimInvalidJoinPruneAddressType | 1 | 1 | The address type stored in pimInvalidJoinPruneOrigin, pimInvalidJoinPruneGroup, and pimInvalidJoinPruneRp. If no invalid Join/Pru… |
| 1.3.6.1.2.1.157.1.40 | pimInvalidJoinPruneOrigin | 1 | 1 | The source address of the last invalid Join/Prune message received by this device. |
| 1.3.6.1.2.1.157.1.41 | pimInvalidJoinPruneGroup | 1 | 1 | The IP multicast group address carried in the last invalid Join/Prune message received by this device. |
| 1.3.6.1.2.1.157.1.42 | pimInvalidJoinPruneRp | 1 | 1 | The RP address carried in the last invalid Join/Prune message received by this device. |
| 1.3.6.1.2.1.157.1.43 | pimRPMappingNotificationPeriod | 1 | 1 | The minimum time that must elapse between pimRPMappingChange notifications originated by this router. The default value of 65535 … |
| 1.3.6.1.2.1.157.1.44 | pimRPMappingChangeCount | 1 | 1 | The number of changes to active RP mappings on this device. Information about active RP mappings is available in pimGroupMappingT… |
| 1.3.6.1.2.1.157.1.45 | pimInterfaceElectionNotificationPeriod | 1 | 1 | The minimum time that must elapse between pimInterfaceElection notifications originated by this router. The default value of 655… |
| 1.3.6.1.2.1.157.1.46 | pimInterfaceElectionWinCount | 1 | 1 | The number of times this device has been elected DR or DF on any interface. Elections occur frequently on newly-active interfaces… |
| 1.3.6.1.2.1.157.1.47 | pimRefreshInterval | 1 | 1 | The interval between successive State Refresh messages sent by an Originator. This timer period is called the RefreshInterval in… |
| 1.3.6.1.2.1.157.1.48 | pimDeviceConfigStorageType | 1 | 1 | The storage type used for the global PIM configuration of this device, comprised of the objects listed below. If this storage ty… |