OID reference

pimGroupMappingTable

1.2.826.42.1.1578918.5.71.1.1.1.13

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 'embedded' a…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.71.1.1.1 (pimTables)
Node code
13
Node name
pimGroupMappingTable
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.71.1.1.1.13
URN notation
urn:oid:1.2.826.42.1.1578918.5.71.1.1.1.13
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 42 1 1578918 5 71 1 1 1 13}

  • {iso(1) member-body(2) gb(826) 42 1 1578918 5 71 dcPimMIB(1) pimMIBObjects(1) pimTables(1) pimGroupMappingTable(13)}
  • {iso(1) memberBody(2) gb(826) 42 1 1578918 5 71 dcPimMIB(1) pimMIBObjects(1) pimTables(1) pimGroupMappingTable(13)}
OID-IRI notation
  • /1/2/826/42/1/1578918/5/71/1/1/1/13
  • /ISO/Member-Body/GB/42/1/1578918/5/71/1/1/1/13
  • /ISO/Member-Body/826/42/1/1578918/5/71/1/1/1/13
  • /ISO/2/826/42/1/1578918/5/71/1/1/1/13
Named path variants
  • /iso/member-body/gb/42/1/1578918/5/71/dcPimMIB/pimMIBObjects/pimTables/pimGroupMappingTable
  • /iso/memberBody/gb/42/1/1578918/5/71/dcPimMIB/pimMIBObjects/pimTables/pimGroupMappingTable

SNMP properties

Value type
SEQUENCE OF PimGroupMappingEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

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 '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)."
    REFERENCE "RFC 4601 section 3.7, RFC 3956, RFC 4610, and
               RFC 5059 section 3.3"
    ::= { pimTables 13 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

pimGroupMappingTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: pimGroupMappingTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "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 '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).\"",
    "REFERENCE",
    "\"RFC 4601 section 3.7, RFC 3956, RFC 4610, and RFC 5059 section 3.3\"",
    "::=",
    "{",
    "pimTables",
    "13",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "PimGroupMappingEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "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 '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)."
    ],
    [
      "REFERENCE",
      "RFC 4601 section 3.7, RFC 3956, RFC 4610, and RFC 5059 section 3.3"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.2.826)

The UK Name Registration Authority

Current Registration Authority (inferred from ancestor 1.2.826)

Mark Barratt or Vanessa Tatler

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.71.1.1.1.13.1 pimGroupMappingEntry88

Siblings (22)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.71.1.1.1.1 pimInterfaceTable152
1.2.826.42.1.1578918.5.71.1.1.1.2 pimNeighborTable119
1.2.826.42.1.1578918.5.71.1.1.1.3 pimNbrSecAddressTable15
1.2.826.42.1.1578918.5.71.1.1.1.4 pimStarGTable121
1.2.826.42.1.1578918.5.71.1.1.1.5 pimStarGITable114
1.2.826.42.1.1578918.5.71.1.1.1.6 pimSGTable128
1.2.826.42.1.1578918.5.71.1.1.1.7 pimSGITable114
1.2.826.42.1.1578918.5.71.1.1.1.8 pimSGRptTable15
1.2.826.42.1.1578918.5.71.1.1.1.9 pimSGRptITable17
1.2.826.42.1.1578918.5.71.1.1.1.11 pimStaticRPTable19
1.2.826.42.1.1578918.5.71.1.1.1.12 pimAnycastRPSetTable17
1.2.826.42.1.1578918.5.71.1.1.1.14 pimNbrStatsTable118
1.2.826.42.1.1578918.5.71.1.1.1.15 pimIfStatsTable121
1.2.826.42.1.1578918.5.71.1.1.1.16 pimNmEntTable120
1.2.826.42.1.1578918.5.71.1.1.1.17 pimNmEntStatsTable144
1.2.826.42.1.1578918.5.71.1.1.1.18 pimTmEntTable170
1.2.826.42.1.1578918.5.71.1.1.1.19 pimTmMjTable18
1.2.826.42.1.1578918.5.71.1.1.1.20 pimTmSjTable16
1.2.826.42.1.1578918.5.71.1.1.1.21 pimBidirDFElectionTable111
1.2.826.42.1.1578918.5.71.1.1.1.22 pimStaticRPMultiTable112
1.2.826.42.1.1578918.5.71.1.1.1.23 pimGroupAddrMappingTable16
1.2.826.42.1.1578918.5.71.1.1.1.24 pimTmEntStatsTable17