OID reference

mgmdRouterCacheTable

1.2.826.42.1.1578918.5.86.1.1.4

Description

The (conceptual) table listing the interfaces that are members of a particular group. This table includes entries for group memberships learned over IGMP/MLD as well as memberships statically configured through mgmdRouterCacheCfgTable and mgmdRouterSrcListCfgTable. This includes both (G,I) and (G,I,S) memberships. The…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.86.1.1 (mgmdRouterMibObjects)
Node code
4
Node name
mgmdRouterCacheTable
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.86.1.1.4
URN notation
urn:oid:1.2.826.42.1.1578918.5.86.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 42 1 1578918 5 86 1 1 4}

  • {iso(1) member-body(2) gb(826) 42 1 1578918 5 86 dcmgmdRouterMib(1) mgmdRouterMibObjects(1) mgmdRouterCacheTable(4)}
  • {iso(1) memberBody(2) gb(826) 42 1 1578918 5 86 dcmgmdRouterMib(1) mgmdRouterMibObjects(1) mgmdRouterCacheTable(4)}
OID-IRI notation
  • /1/2/826/42/1/1578918/5/86/1/1/4
  • /ISO/Member-Body/GB/42/1/1578918/5/86/1/1/4
  • /ISO/Member-Body/826/42/1/1578918/5/86/1/1/4
  • /ISO/2/826/42/1/1578918/5/86/1/1/4
Named path variants
  • /iso/member-body/gb/42/1/1578918/5/86/dcmgmdRouterMib/mgmdRouterMibObjects/mgmdRouterCacheTable
  • /iso/memberBody/gb/42/1/1578918/5/86/dcmgmdRouterMib/mgmdRouterMibObjects/mgmdRouterCacheTable

SNMP properties

Value type
SEQUENCE OF MgmdRouterCacheEntry
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.

mgmdRouterCacheTable OBJECT-TYPE
-- FAMILY-SHORT-NAME qgr_gi
    SYNTAX     SEQUENCE OF MgmdRouterCacheEntry
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
-- DC modifications {
-- Correct the error in the description of this table
            "The (conceptual) table listing the interfaces that are
             members of a particular group.

             This table includes entries for group memberships learned
             over IGMP/MLD as well as memberships statically configured
             through mgmdRouterCacheCfgTable and
             mgmdRouterSrcListCfgTable.  This includes both (G,I) and
             (G,I,S) memberships.

             There are two MIB tables that are suitable for reading (G,I)
             state - mgmdRouterCacheTable and mgmdRouterPerEntCacheTable.
             These tables contain the same objects, but their indexing is
             different.

             For IGMP snooping, the administrator must read the
             mgmdRouterPerEntCacheTable.  The mgmdRouterCacheTable is not
             supported (because a single row in that table would
             correspond to multiple objects, one per bridge domain).

             When not performing IGMP snooping, the administrator can use
             either table.  In systems in which there are a large number
             of Router entities, there might be a performance benefit to
             using the mgmdRouterPerEntCacheTable for queries for which
             only a subset of Router entities are of interest.

             For example, if an entity index corresponds to a particular
             line card, and the administrator is interested in (G,I)
             state for only one line card, then walking this table for a
             particular entity index returns the (G,I) state for the
             interfaces on that line card only (whereas
             mgmdRouterCacheTable returns (G,I) state for all interfaces
             on the device).

             (The possible performance benefit arises because to get the
             rows in mgmdRouterPerEntCacheTable, MIB Manager queries a
             single Router entity per row, whereas to get the rows in
             mgmdRouterCacheTable, MIB Manager queries every Router
             entity per row)."
-- } End DC modifications
    ::= { mgmdRouterMibObjects 4 }

Meaning

Descriptions

1 unique

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

The (conceptual) table listing the interfaces that are members of a particular group. This table includes entries for group memberships learned over IGMP/MLD as well as memberships statically configured through mgmdRouterCacheCfgTable and mgmdRouterSrcListCfgTable. This includes both (G,I) and (G,I,S) memberships. There are two MIB tables that are suitable for reading (G,I) state - mgmdRouterCacheTable and mgmdRouterPerEntCacheTable. These tables contain the same objects, but their indexing is different. For IGMP snooping, the administrator must read the mgmdRouterPerEntCacheTable. The mgmdRouterCacheTable is not supported (because a single row in that table would correspond to multiple objects, one per bridge domain). When not performing IGMP snooping, the administrator can use either table. In systems in which there are a large number of Router entities, there might be a performance benefit to using the mgmdRouterPerEntCacheTable for queries for which only a subset of Router entities are of interest. For example, if an entity index corresponds to a particular line card, and the administrator is interested in (G,I) state for only one line card, then walking this table for a particular entity index returns the (G,I) state for the interfaces on that line card only (whereas mgmdRouterCacheTable returns (G,I) state for all interfaces on the device). (The possible performance benefit arises because to get the rows in mgmdRouterPerEntCacheTable, MIB Manager queries a single Router entity per row, whereas to get the rows in mgmdRouterCacheTable, MIB Manager queries every Router entity per row).

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

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

Status in source: current.

Names: mgmdRouterCacheTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mgmdRouterCacheTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "MgmdRouterCacheEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The (conceptual) table listing the interfaces that are members of a particular group. This table includes entries for group memberships learned over IGMP/MLD as well as memberships statically configured through mgmdRouterCacheCfgTable and mgmdRouterSrcListCfgTable. This includes both (G,I) and (G,I,S) memberships. There are two MIB tables that are suitable for reading (G,I) state - mgmdRouterCacheTable and mgmdRouterPerEntCacheTable. These tables contain the same objects, but their indexing is different. For IGMP snooping, the administrator must read the mgmdRouterPerEntCacheTable. The mgmdRouterCacheTable is not supported (because a single row in that table would correspond to multiple objects, one per bridge domain). When not performing IGMP snooping, the administrator can use either table. In systems in which there are a large number of Router entities, there might be a performance benefit to using the mgmdRouterPerEntCacheTable for queries for which only a subset of Router entities are of interest. For example, if an entity index corresponds to a particular line card, and the administrator is interested in (G,I) state for only one line card, then walking this table for a particular entity index returns the (G,I) state for the interfaces on that line card only (whereas mgmdRouterCacheTable returns (G,I) state for all interfaces on the device). (The possible performance benefit arises because to get the rows in mgmdRouterPerEntCacheTable, MIB Manager queries a single Router entity per row, whereas to get the rows in mgmdRouterCacheTable, MIB Manager queries every Router entity per row).\"",
    "::=",
    "{",
    "mgmdRouterMibObjects",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "MgmdRouterCacheEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The (conceptual) table listing the interfaces that are members of a particular group. This table includes entries for group memberships learned over IGMP/MLD as well as memberships statically configured through mgmdRouterCacheCfgTable and mgmdRouterSrcListCfgTable. This includes both (G,I) and (G,I,S) memberships. There are two MIB tables that are suitable for reading (G,I) state - mgmdRouterCacheTable and mgmdRouterPerEntCacheTable. These tables contain the same objects, but their indexing is different. For IGMP snooping, the administrator must read the mgmdRouterPerEntCacheTable. The mgmdRouterCacheTable is not supported (because a single row in that table would correspond to multiple objects, one per bridge domain). When not performing IGMP snooping, the administrator can use either table. In systems in which there are a large number of Router entities, there might be a performance benefit to using the mgmdRouterPerEntCacheTable for queries for which only a subset of Router entities are of interest. For example, if an entity index corresponds to a particular line card, and the administrator is interested in (G,I) state for only one line card, then walking this table for a particular entity index returns the (G,I) state for the interfaces on that line card only (whereas mgmdRouterCacheTable returns (G,I) state for all interfaces on the device). (The possible performance benefit arises because to get the rows in mgmdRouterPerEntCacheTable, MIB Manager queries a single Router entity per row, whereas to get the rows in mgmdRouterCacheTable, MIB Manager queries every Router entity per row)."
    ],
    null,
    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.86.1.1.4.1 mgmdRouterCacheEntry1111

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.86.1.1.1 mgmdRouterEntTable143
1.2.826.42.1.1578918.5.86.1.1.3 mgmdRouterInterfaceTable173
1.2.826.42.1.1578918.5.86.1.1.5 mgmdRouterInverseCacheTable110
1.2.826.42.1.1578918.5.86.1.1.6 mgmdRouterSrcListTable16
1.2.826.42.1.1578918.5.86.1.1.7 mgmdRouterPerEntCacheTable112
1.2.826.42.1.1578918.5.86.1.1.8 mgmdRouterPerEntSrcListTable16
1.2.826.42.1.1578918.5.86.1.1.9 mgmdRouterCacheCfgTable18
1.2.826.42.1.1578918.5.86.1.1.10 mgmdRouterSrcListCfgTable19
1.2.826.42.1.1578918.5.86.1.1.11 mgmdRouterSrcCfgTable18