DC-PIM-MIB Table View

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 deprecated mode enabled by pimTmEntMgmdProxy), this
table is not used, and all rows created will be ignored.

The (conceptual) table listing the router's PIM neighbors.
          
This table is not used for MGMD Snooping or Proxy.

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 not used for MGMD Snooping or Proxy.

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 Proxy (except in the deprecated mode), so is empty
if pimTmEntMgmdProxy is set to 'false' and 'sparse' and
'bidir' are both clear for pimTmEntMode.

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 local group membership requirements that
DC-PIM has learned from the MGMD Router implementation.

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 the deprecated mode enabled by
pimTmEntMgmdProxy).

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 group membership requirements that DC-PIM
has learned from the MGMD Router implementation.

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, nor for MGMD Proxy (except in the deprecated
mode), so is empty if pimTmEntMgmdProxy is set to 'false'
and 'sparse' is clear for pimTmEntMode.

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 exists only because of local group
membership requirements that DC-PIM has learned from the
MGMD Router implementation.

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 row with the greatest value of
pimStaticRPGrpPrefixLength is used for the overlapping
range.
          
DC-PIM creates default rows in this table at startup to
correspond to the SSM ranges defined by IANA.  The
administrator is permitted to modify and destroy these rows,
or create other rows for different group prefixes.
          
If DC-PIM supports dense mode groups, the network
administrator must create group ranges in this table to
indicate the multicast groups which should be treated as
dense mode.
          
Bidir and PIM-SM ASM group ranges can be configured in this
table and/or learned dynamically via BSR.  To configure
multiple RPs for the same group range, see
pimStaticRPMultiTable.
          
This table is not used if pimTmEntMgmdProxy is set to
'true', or pimTmEntMode is set to 'mgmd-snooping' or
'mgmd-proxy'.

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 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
pimStaticRP[Multi]Table 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.  The maximum number of remote routers in an
Anycast-RP set is given by the value of the customizable
constant QPTM_ANYCAST_RP_MAX_REM_RTR.
          
Exactly one entry per Anycast-RP set corresponds to the
local router.  That entry is identified by the
pimAnycastRPSetLocalRouter object, and determines the source
address used by the local router when forwarding PIM
Register messages to the other routers in the Anycast-RP
set.
          
This table is only used by PIM-SM.  Rows are ignored if
any of the following are true:
          
- pimTmEntMgmdProxy is set to 'true'
          
- 'sparse' is clear for pimTmEntMode.

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).

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),
this event resets all of the statistics in this table.
However, if a neighbor's Generation ID value changes, none
of the statistics in this table are affected.
          
This table is not used for MGMD Snooping or Proxy.

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 contribute to any
statistics in this table except for
pimIfStatsNumFilteredOut.
          
The statistics in this table can be cleared using the
pimNmEntClearStatsCounters field.
          
This table is not used for MGMD Snooping or Proxy.

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-snooping' or
'mgmd-proxy'.

This table lists the statistics for DC-PIM Neighbor Manager
entities.
          
Note that any messages filtered out by
pimInterfaceNeighborFilter do not contribute to any
statistics in this table.
          
Note that in the case of critical parsing errors, only the
first error encountered will be counted.  The checks are
made in the following order.
          
- Length.
- Checksum.
- Message type.
- Version.
          
This table is not used for MGMD Snooping or Proxy.

This table is used to create and manage DC-PIM TIB Manager
entities.