OID reference

mplsManTunnelTable

1.3.6.1.4.1.738.10.6.3.2.1.2

Description

The mplsManTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cro…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.738.10.6.3.2.1 (mplsTeObjects)
Node code
2
Node name
mplsManTunnelTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.738.10.6.3.2.1.2
URN notation
urn:oid:1.3.6.1.4.1.738.10.6.3.2.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 738 10 6 3 2 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) privateVendorOID(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) prvtVendorDefMIB(738) prvt-products(10) ipSwitch(6) mpls(3) prvtMplsTeMIB(2) mplsTeObjects(1) mplsManTunnelTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/738/10/6/3/2/1/2
  • /ISO/Identified-Organization/6/1/4/1/738/10/6/3/2/1/2
  • /ISO/3/6/1/4/1/738/10/6/3/2/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/738/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/enterprise/privateVendorOID/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/enterprise/prvtVendorDefMIB/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/enterprises/738/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/enterprises/privateVendorOID/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/enterprises/prvtVendorDefMIB/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/738/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/privateVendorOID/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/prvtVendorDefMIB/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/738/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/privateVendorOID/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/prvtVendorDefMIB/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/org/dod/internet/private/enterprise/738/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/org/dod/internet/private/enterprise/privateVendorOID/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/org/dod/internet/private/enterprise/prvtVendorDefMIB/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • /iso/org/dod/internet/private/enterprises/738/prvt-products/ipSwitch/mpls/prvtMplsTeMIB/mplsTeObjects/mplsManTunnelTable
  • Additional combinations skipped.

SNMP properties

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

mplsManTunnelTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF MplsManTunnelEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION 
        "The mplsManTunnelTable allows new MPLS tunnels to be
         created between an LSR and a remote endpoint, and
         existing tunnels to be reconfigured or removed.
         Note that only point-to-point tunnel segments are
         supported, although multi-point-to-point and point-
         to-multi-point connections are supported by an LSR
         acting as a cross-connect. Each MPLS tunnel can
         thus have one out-segment originating at this LSR
         and/or one in-segment terminating at this LSR.
         
         To configure tunnels where the ingress and egress routers
         are identified by IPv6 addresses, the following approach is
         used.
         
         - The mplsManTunnelIngressLSRId and mplsManTunnelEgressLSRId
         fields are set to 32-bit identifiers for the ingress and
         egress routers.
         
         - mplsManTunnelHopTableIndex must be set to a non-zero value.
         
         - The first hop in the hop table for the tunnel path must be
         set to a global scope IPv6 address of the local router.
         
         - The last entry in the hop table must be set to a global
         scope IPv6 address of the egress router."
    ::= { mplsTeObjects 2 }

Meaning

Descriptions

1 unique

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

The mplsManTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. To configure tunnels where the ingress and egress routers are identified by IPv6 addresses, the following approach is used. - The mplsManTunnelIngressLSRId and mplsManTunnelEgressLSRId fields are set to 32-bit identifiers for the ingress and egress routers. - mplsManTunnelHopTableIndex must be set to a non-zero value. - The first hop in the hop table for the tunnel path must be set to a global scope IPv6 address of the local router. - The last entry in the hop table must be set to a global scope IPv6 address of the egress router.

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

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

Status in source: current.

Names: mplsManTunnelTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mplsManTunnelTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "MplsManTunnelEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The mplsManTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. To configure tunnels where the ingress and egress routers are identified by IPv6 addresses, the following approach is used. - The mplsManTunnelIngressLSRId and mplsManTunnelEgressLSRId fields are set to 32-bit identifiers for the ingress and egress routers. - mplsManTunnelHopTableIndex must be set to a non-zero value. - The first hop in the hop table for the tunnel path must be set to a global scope IPv6 address of the local router. - The last entry in the hop table must be set to a global scope IPv6 address of the egress router.\"",
    "::=",
    "{",
    "mplsTeObjects",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "MplsManTunnelEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The mplsManTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. To configure tunnels where the ingress and egress routers are identified by IPv6 addresses, the following approach is used. - The mplsManTunnelIngressLSRId and mplsManTunnelEgressLSRId fields are set to 32-bit identifiers for the ingress and egress routers. - mplsManTunnelHopTableIndex must be set to a non-zero value. - The first hop in the hop table for the tunnel path must be set to a global scope IPv6 address of the local router. - The last entry in the hop table must be set to a global scope IPv6 address of the egress router."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.738)

Killim Nahum

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.738.10.6.3.2.1.2.1 mplsManTunnelEntry3737

Siblings (21)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.738.10.6.3.2.1.1 mplsTeObjectReserved100
1.3.6.1.4.1.738.10.6.3.2.1.3 mplsTeObjectReserved300
1.3.6.1.4.1.738.10.6.3.2.1.4 mplsAutoTunnelTable137
1.3.6.1.4.1.738.10.6.3.2.1.5 mplsTeObjectReserved500
1.3.6.1.4.1.738.10.6.3.2.1.6 mplsDynTunnelTable137
1.3.6.1.4.1.738.10.6.3.2.1.7 mplsTeObjectReserved700
1.3.6.1.4.1.738.10.6.3.2.1.8 mplsTunnelManHopTable111
1.3.6.1.4.1.738.10.6.3.2.1.9 mplsTeObjectReserved900
1.3.6.1.4.1.738.10.6.3.2.1.10 mplsTunnelAutoHopTable19
1.3.6.1.4.1.738.10.6.3.2.1.11 mplsTeObjectReserved1100
1.3.6.1.4.1.738.10.6.3.2.1.12 mplsTunnelManResTable18
1.3.6.1.4.1.738.10.6.3.2.1.13 mplsTeObjectReserved1300
1.3.6.1.4.1.738.10.6.3.2.1.14 mplsTunnelAutoResTable17
1.3.6.1.4.1.738.10.6.3.2.1.15 mplsTeObjectReserved1500
1.3.6.1.4.1.738.10.6.3.2.1.16 mplsTunnelDynResTable18
1.3.6.1.4.1.738.10.6.3.2.1.17 mplsTeObjectReserved1700
1.3.6.1.4.1.738.10.6.3.2.1.18 mplsTunnelARHopTable15
1.3.6.1.4.1.738.10.6.3.2.1.19 mplsTeObjectReserved1900
1.3.6.1.4.1.738.10.6.3.2.1.20 mplsTunnelCHopTable17
1.3.6.1.4.1.738.10.6.3.2.1.21 mplsTeObjectReserved2100
1.3.6.1.4.1.738.10.6.3.2.1.22 prvtMplsTunnelTrapEnableTable12