pimGroupMappingTable
DC-PIM-MIB ·
.1.2.826.42.1.1578918.5.71.1.1.1.13
Object
table
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 'embedded' are
created by the router for each Embedded-RP group-to-RP
mapping which corresponds to a group for which the PIM
router maintains protocol state.
- Rows with a pimGroupMappingOrigin value of 'config' are
created and destroyed as a result of configuration of
pimStaticRP[Multi]Table being created and destroyed.
Additionally, DC-PIM creates default rows in the
pimStaticRPTable table at startup to correspond to the
SSM ranges defined by IANA. The administrator is
permitted to modify and destroy the SSM range
configuration.
- 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.
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. This
algorithm has minor aspects which are specific to DC-PIM.
1) If the group corresponds to the well-defined prefixes of
link-local and unroutable group addresses, it cannot be used
as a PIM group. There are no rows in the
pimGroupMappingTable corresponding to these prefixes.
2) If the group corresponds to the format defined in the
Embedded-RP mechanism [RFC3956] where the RP address is
embedded in the multicast group address, the RP address is
extracted from the group address and pimGroupMappingPimMode
is 'asm'.
3) From the set of all rows in the pimGroupMappingTable, the
subset whose group prefix contains the group in question is
selected.
4) If there are no such rows, the group cannot be used for
PIM.
5) If there are multiple selected rows, and a subset is
defined by pimStaticRP[Multi]Table (pimGroupMappingOrigin
value of 'config') with pimStaticRPOverrideSubranges /
pimStaticRPMultiOverrideSubrngs set to TRUE, then this
subset is selected.
6) From the selected subset of rows, the subset that has the
greatest value of pimGroupMappingGrpPrefixLength is
selected.
7) If there are still multiple selected rows, the subset
that has the highest precedence (the lowest numerical value
for pimGroupMappingPrecedence) is selected.
8) If there are still multiple selected mappings, and a
subset is associated with the BIDIR-PIM protocol rather than
the PIM-SM protocol, this subset is selected.
9) If there are still multiple selected mappings, the subset
with the numerically lowest priority vector is selected.
For a BSR mapping, the priority vector is simply the RP
priority; for a configured mapping, it is whether the RP is
unreachable, then the RP priority.
10) If there are still multiple selected mappings, the
algorithm specified by pimTmEntRPMultipathAlgorithm is used
to select one or more mappings - unless that mechanism is
disabled (via pimTmEntBsrRPMultipathMode for BSR mappings,
or via pimTmEntBidirDataMonitorEnable for BIDIR mappings).
11) If there are still multiple selected rows, the highest
RP address is selected.
12) 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.
This table is not used by MGMD snooping or proxy (except in
the deprecated mode enabled by pimTmEntMgmdProxy).
Context
- MIB
- DC-PIM-MIB
- OID
.1.2.826.42.1.1578918.5.71.1.1.1.13- Type
- table
- Status
- current
- Parent
- pimTables
- Siblings
- 22
- Children
- 1
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| pimInterfaceTable This table is used to create and manage the {interface, IP
version} pairs for which PIM is enabled.
When the entity is running MGMD Snooping or Proxy (but not
in the de… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.1 |
| pimStaticRPTable This table is used to create and manage static configuration
of RPs and group ranges.
If the group prefixes configured for two or more rows in
this table overlap, the r… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.11 |
| pimAnycastRPSetTable This table is used to create and manage Anycast-RP via PIM
Register messages (draft-ietf-pim-anycast-rp), as opposed to
via other protocols such as MSDP.
Entries must b… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.12 |
| pimNbrStatsTable This table lists the statistics for PIM neighbors.
Note that if a neighbor's Liveness Timer expires (including
on receipt of a PIM Hello message with a zero Holdtime),
… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.14 |
| pimIfStatsTable This table lists the statistics for {interface, IP version}
pairs for which PIM is enabled.
Note that any messages filtered out by
pimInterfaceNeighborFilter do not con… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.15 |
| pimNmEntTable This table is used to create and manage DC-PIM Neighbor
Manager entities.
There is no reason to create rows in this table if
pimTmEntMode is always set to 'mgmd-snoopin… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.16 |
| pimNmEntStatsTable This table lists the statistics for DC-PIM Neighbor Manager
entities.
Note that any messages filtered out by
pimInterfaceNeighborFilter do not contribute to any
statist… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.17 |
| pimTmEntTable This table is used to create and manage DC-PIM TIB Manager
entities. | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.18 |
| pimTmMjTable This table is used to create and manage the master joins
that DC-PIM TIB Manager forms to other entities. Each join
is represented by a row in this table. The status of each
joi… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.19 |
| pimNeighborTable The (conceptual) table listing the router's PIM neighbors.
This table is not used for MGMD Snooping or Proxy. | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.2 |
| pimTmSjTable This table shows which entities the DC-PIM TIB Manager is
joined to as slave. Each join is represented by a row in
this table. | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.20 |
| pimBidirDFElectionTable The (conceptual) table listing the per-RP Designated
Forwarder (DF) Election state for each interface for all the
RPs in BIDIR-PIM mode.
This table is empty if 'bidir' … | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.21 |
| pimStaticRPMultiTable This table performs the same role as pimStaticRPTable, but
it allows multiple static RPs to be configured for the same
ASM or BIDIR group range.
This allows for RP load… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.22 |
| pimGroupAddrMappingTable The (conceptual) table listing the PIM mode and RP address
(if any) in use for each multicast group address.
See the pimGroupMappingTable for the algorithm that DC-PIM
… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.23 |
| pimTmEntStatsTable This table lists the statistics for DC-PIM TIB Manager
entities.
The statistics in this table can be cleared using the
pimTmEntClearCounters field. | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.24 |
| pimNbrSecAddressTable The (conceptual) table listing the secondary addresses
advertised by each PIM neighbor (on a subset of the rows of
the pimNeighborTable defined above).
This table is no… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.3 |
| pimStarGTable The (conceptual) table listing the non-interface specific
(*,G) state that the entity maintains.
This MIB table is not used for MGMD Snooping or PIM-DM, nor
for MGMD Pr… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.4 |
| pimStarGITable The (conceptual) table listing the interface-specific (*,G)
state that the entity maintains.
For MGMD Proxy or Snooping, or PIM-DM, (*,G,I) state exists
only because of… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.5 |
| pimSGTable The (conceptual) table listing the non-interface specific
(S,G) state that the entity maintains.
This MIB table is not used for MGMD Snooping or MGMD Proxy
(except in t… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.6 |
| pimSGITable The (conceptual) table listing the interface-specific (S,G)
state that the entity maintains.
For MGMD Proxy or Snooping, (S,G,I) state exists only
because of local grou… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.7 |
| pimSGRptTable The (conceptual) table listing the non-interface specific
(S,G,rpt) state that the entity maintains.
This MIB table is not used for MGMD Snooping or PIM-DM or
BIDIR-PIM… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.8 |
| pimSGRptITable The (conceptual) table listing the interface-specific
(S,G,rpt) state that the entity maintains.
For MGMD Proxy or Snooping, or PIM-DM or BIDIR-PIM,
(S,G,I,rpt) state e… | table | - | .1.2.826.42.1.1578918.5.71.1.1.1.9 |
Child Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| pimGroupMappingEntry An entry (conceptual row) in the pimGroupMappingTable. | row | - | .1.2.826.42.1.1578918.5.71.1.1.1.13.1 |