OID reference

pimGroupMappingTable

1.3.6.1.2.1.157.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 'fixed' are …

Full description and source information

Identification

Identifier and names

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

{1 3 6 1 2 1 157 1 1 13}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pim(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pim(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pimMIBObjects(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pimMIBObjects(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pimStdMIB(157) pim(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pimStdMIB(157) pim(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pimStdMIB(157) pimMIBObjects(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pimStdMIB(157) pimMIBObjects(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pimStdMIB(157) pim(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pimStdMIB(157) pim(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pimStdMIB(157) pimMIBObjects(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pimStdMIB(157) pimMIBObjects(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pim(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pim(1) pim(1) pimGroupMappingTable(13)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pimMIBObjects(1) pimInterfaceTable(1) pimGroupMappingTable(13)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pimStdMIB(157) pimMIBObjects(1) pim(1) pimGroupMappingTable(13)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/2/1/157/1/1/13
  • /ISO/Identified-Organization/6/1/2/1/157/1/1/13
  • /ISO/3/6/1/2/1/157/1/1/13
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pimStdMIB/pim/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pimStdMIB/pim/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pimStdMIB/pimMIBObjects/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pimStdMIB/pimMIBObjects/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib/pimStdMIB/pim/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib/pimStdMIB/pim/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib/pimStdMIB/pimMIBObjects/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/mib/pimStdMIB/pimMIBObjects/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pimStdMIB/pim/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pimStdMIB/pim/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pimStdMIB/pimMIBObjects/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pimStdMIB/pimMIBObjects/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/pimStdMIB/pim/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/pimStdMIB/pim/pim/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/pimStdMIB/pimMIBObjects/pimInterfaceTable/pimGroupMappingTable
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/pimStdMIB/pimMIBObjects/pim/pimGroupMappingTable
  • Additional combinations skipped.

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.

Product context

Documented MIB packages

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

pimGroupMappingTable · current

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 · current

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 }

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

Sources for this description

LANCOM official release MIBsNETGEAR official product and EOL MIB downloads

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 1LANCOM official release MIBs, NETGEAR official product and EOL MIB downloads1 record · 6 sources

Description 1

pimGroupMappingTable · currentLANCOM official release MIBs, NETGEAR official product and EOL MIB downloads6 sources

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 '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",
    "}"
  ],
  "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 '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"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.157.1.1.13.1 pimGroupMappingEntry88

Siblings (11)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.157.1.1.1 pimInterfaceEntry, pimInterfaceTable2856 An entry (conceptual row) in the pimInterfaceTable. This
entry is preserved on agent restart.
1.3.6.1.2.1.157.1.1.2 pimNeighborTable116
1.3.6.1.2.1.157.1.1.3 pimNbrSecAddressTable15
1.3.6.1.2.1.157.1.1.4 pimStarGTable121
1.3.6.1.2.1.157.1.1.5 pimStarGITable113
1.3.6.1.2.1.157.1.1.6 pimSGTable128
1.3.6.1.2.1.157.1.1.7 pimSGITable113
1.3.6.1.2.1.157.1.1.8 pimSGRptTable15
1.3.6.1.2.1.157.1.1.9 pimSGRptITable17
1.3.6.1.2.1.157.1.1.10 pimBidirDFElectionTable111
1.3.6.1.2.1.157.1.1.11 pimStaticRPTable110