PIM-STD-MIB Table View

The (conceptual) table listing the router's PIM interfaces.
PIM is enabled on all interfaces listed in this table.

The (conceptual) table listing the router's PIM neighbors.

The (conceptual) table listing the secondary addresses
advertised by each PIM neighbor (on a subset of the rows of
the pimNeighborTable defined above).

The (conceptual) table listing the non-interface specific
(*,G) state that PIM has.

The (conceptual) table listing the interface-specific (*,G)
state that PIM has.

The (conceptual) table listing the non-interface specific
(S,G) state that PIM has.

The (conceptual) table listing the interface-specific (S,G)
state that PIM has.

The (conceptual) table listing the non-interface specific
(S,G,rpt) state that PIM has.

The (conceptual) table listing the interface-specific
(S,G,rpt) state that PIM has.

The (conceptual) table listing the per-RP Designated
Forwarder (DF) Election state for each interface for all the
RPs in BIDIR mode.

This table is used to manage static configuration of RPs.
          
If the group prefixes configured for two or more rows in
this table overlap, the row with the greatest value of
pimStaticRPGrpPrefixLength is used for the overlapping
range.

This table is used to manage Anycast-RP via PIM Register
messages, as opposed to via other protocols such as MSDP
(Multicast Source Discovery Protocol).
          
Entries must be configured in this table if and only if the
local router is a member of one or more Anycast-RP sets,
that is, one or more Anycast-RP addresses are assigned to
the local router.  Note that if using static RP
configuration, this is in addition to, not instead of, the
pimStaticRPTable entries that must be configured for the
Anycast-RPs.
          
The set of rows with the same values of both
pimAnycastRPSetAddressType and pimAnycastRPSetAnycastAddress
corresponds to the Anycast-RP set for that Anycast-RP
address.
          
When an Anycast-RP set configuration is active, one entry
per pimAnycastRPSetAnycastAddress corresponds to the local
router.  The local router is identified by the
pimAnycastRpSetLocalRouter object.  That entry determines
the source address used by the local router when forwarding
PIM Register messages within the Anycast-RP set.

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.