OID reference

mplsLdpEntityConfAtmLabelRangeEntry

1.3.6.1.4.1.9.10.65.1.2.4.2.1

Description

A row in the LDP Entity Configurable ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message. NOTE: The ranges for a specific LDP Entity are UNIQUE and …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.9.10.65.1.2.4.2 (mplsLdpEntityConfAtmLabelRangeTable, mplsLdpEntityConfAtmLRTable)
Node code
1
Node names
  • mplsLdpEntityConfAtmLabelRangeEntry
  • mplsLdpEntityConfAtmLREntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.9.10.65.1.2.4.2.1
URN notation
urn:oid:1.3.6.1.4.1.9.10.65.1.2.4.2.1
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 9 10 65 1 2 4 2 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLabelRangeTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLabelRangeEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoExperiment(10) mplsLdpMIB(65) mplsLdpObjects(1) mplsLdpEntityObjects(2) mplsLdpEntityAtmObjects(4) mplsLdpEntityConfAtmLRTable(2) mplsLdpEntityConfAtmLREntry(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/10/65/1/2/4/2/1
  • /ISO/Identified-Organization/6/1/4/1/9/10/65/1/2/4/2/1
  • /ISO/3/6/1/4/1/9/10/65/1/2/4/2/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLabelRangeTable/mplsLdpEntityConfAtmLREntry
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLabelRangeEntry
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/mplsLdpMIB/mplsLdpObjects/mplsLdpEntityObjects/mplsLdpEntityAtmObjects/mplsLdpEntityConfAtmLRTable/mplsLdpEntityConfAtmLREntry
  • Additional combinations skipped.

SNMP properties

Value type
MplsLdpEntityConfAtmLREntry, MplsLdpEntityConfAtmLabelRangeEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory, current

Definitions may combine these properties differently.

Compare 3 source variants

Variant 1 — MIBdepot

Value type
MplsLdpEntityConfAtmLREntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory

Variant 2 — Cisco, Circitor

Value type
MplsLdpEntityConfAtmLabelRangeEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Variant 3 — Cisco SMIv1

Value type
MplsLdpEntityConfAtmLabelRangeEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory

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.

mplsLdpEntityConfAtmLREntry OBJECT-TYPE
    SYNTAX MplsLdpEntityConfAtmLREntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "A row in the LDP Entity Configurable ATM Label
        Range Table.  One entry in this table contains
        information on a single range of labels
        represented by the configured Upper and Lower
        Bounds VPI/VCI pairs.  These are the same
        data used in the Initialization Message.
        
        NOTE:  The ranges for a specific LDP Entity
        are UNIQUE and non-overlapping.  For example,
        for a specific LDP Entity index, there could
        be one entry having ConfLowerBound vpi/vci == 0/32, and
        ConfUpperBound vpi/vci == 0/100, and a second entry
        for this same interface with ConfLowerBound
        vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200.
        However, there could not be a third entry with
        ConfLowerBound vpi/vci == 0/200 and
        ConfUpperBound vpi/vci == 0/300 because this label
        range overlaps with the second entry (i.e. both
        entries now have 0/200).
        
        A row will not be created unless a unique and
        non-overlapping range is specified.  Thus, row
        creation implies a one-shot row creation of
        LDP EntityID and ConfLowerBound vpi/vci and
        ConfUpperBound vpi/vci.  At least one label
        range entry for a specific LDP Entity MUST
        include the default VPI/VCI  values denoted
        in the LDP Entity Table."
    INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpEntityConfAtmLRMinVpi, mplsLdpEntityConfAtmLRMinVci }
    ::= { mplsLdpEntityConfAtmLRTable 1 }

Meaning

Descriptions

1 unique

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

A row in the LDP Entity Configurable ATM Label
Range Table. One entry in this table contains
information on a single range of labels
represented by the configured Upper and Lower
Bounds VPI/VCI pairs. These are the same
data used in the Initialization Message.

NOTE: The ranges for a specific LDP Entity
are UNIQUE and non-overlapping. For example,
for a specific LDP Entity index, there could
be one entry having ConfLowerBound vpi/vci == 0/32, and
ConfUpperBound vpi/vci == 0/100, and a second entry
for this same interface with ConfLowerBound
vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200.
However, there could not be a third entry with
ConfLowerBound vpi/vci == 0/200 and
ConfUpperBound vpi/vci == 0/300 because this label
range overlaps with the second entry (i.e. both
entries now have 0/200).

A row will not be created unless a unique and
non-overlapping range is specified. Thus, row
creation implies a one-shot row creation of
LDP EntityID and ConfLowerBound vpi/vci and
ConfUpperBound vpi/vci. At least one label
range entry for a specific LDP Entity MUST
include the default VPI/VCI values denoted
in the LDP Entity Table.
Sources for this description

MIBdepot

See 1 matching source record

Circitor

Parsed from MPLS-LDP-MIB.mib · MPLS-LDP-MIB

Source file: Download MPLS-LDP-MIB.mib

Browse all files from Circitor

Evidence

Source records

1 records

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

Records for description 1MIBdepot1 record · 1 source

Description 1

mplsLdpEntityConfAtmLREntry · mandatoryMIBdepot1 source

Status in source: mandatory.

Names: mplsLdpEntityConfAtmLREntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mplsLdpEntityConfAtmLREntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "MplsLdpEntityConfAtmLREntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"A row in the LDP Entity Configurable ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. For example, for a specific LDP Entity index, there could be one entry having ConfLowerBound vpi/vci == 0/32, and ConfUpperBound vpi/vci == 0/100, and a second entry for this same interface with ConfLowerBound vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. However, there could not be a third entry with ConfLowerBound vpi/vci == 0/200 and ConfUpperBound vpi/vci == 0/300 because this label range overlaps with the second entry (i.e. both entries now have 0/200). A row will not be created unless a unique and non-overlapping range is specified. Thus, row creation implies a one-shot row creation of LDP EntityID and ConfLowerBound vpi/vci and ConfUpperBound vpi/vci. At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table.\"",
    "INDEX",
    "{",
    "mplsLdpEntityLdpId",
    ",",
    "mplsLdpEntityIndex",
    ",",
    "mplsLdpEntityConfAtmLRMinVpi",
    ",",
    "mplsLdpEntityConfAtmLRMinVci",
    "}",
    "::=",
    "{",
    "mplsLdpEntityConfAtmLRTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "MplsLdpEntityConfAtmLREntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "A row in the LDP Entity Configurable ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. For example, for a specific LDP Entity index, there could be one entry having ConfLowerBound vpi/vci == 0/32, and ConfUpperBound vpi/vci == 0/100, and a second entry for this same interface with ConfLowerBound vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. However, there could not be a third entry with ConfLowerBound vpi/vci == 0/200 and ConfUpperBound vpi/vci == 0/300 because this label range overlaps with the second entry (i.e. both entries now have 0/200). A row will not be created unless a unique and non-overlapping range is specified. Thus, row creation implies a one-shot row creation of LDP EntityID and ConfLowerBound vpi/vci and ConfUpperBound vpi/vci. At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "mplsLdpEntityLdpId"
        ],
        [
          0,
          "mplsLdpEntityIndex"
        ],
        [
          0,
          "mplsLdpEntityConfAtmLRMinVpi"
        ],
        [
          0,
          "mplsLdpEntityConfAtmLRMinVci"
        ]
      ]
    ],
    null
  ]
}
  • Preserved mibdepot archive

    Module: MPLS-LDP-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'CISCO-SMI': ['ciscoExperiment'], 'ATM-TC-MIB': ['AtmVpIdentifier'], 'MPLS-TC-MIB': ['MplsAtmVcIdentifier', 'MplsLabel', 'MplsLdpGenAddr', 'MplsLdpIdentifier', 'MplsLdpLabelTypes', 'MplsLsrIdentifier'], 'RFC1155-SMI': ['Counter', 'Gauge'], 'SNMPv2-TC-v1': ['RowStatus', 'TimeInterval', 'TruthValue', 'TimeStamp', 'StorageType'], 'SNMPv2-SMI-v1': ['transmission'], 'IANA-ADDRESS-FAMILY-NUMBERS-MIB': ['AddressFamilyNumbers']}
    · Download MPLS-LDP-MIB-V1SMI.my.txt

Historical records

Additional source information

Information from Cisco SMIv1
mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE
    SYNTAX MplsLdpEntityConfAtmLabelRangeEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "A row in the LDP Entity Configurable ATM Label
        Range Table.  One entry in this table contains
        information on a single range of labels
        represented by the configured Upper and Lower
        Bounds VPI/VCI pairs.  These are the same
        data used in the Initialization Message.
        
        NOTE:  The ranges for a specific LDP Entity
        are UNIQUE and non-overlapping.  For example,
        for a specific LDP Entity index, there could
        be one entry having ConfLowerBound vpi/vci == 0/32, and
        ConfUpperBound vpi/vci == 0/100, and a second entry
        for this same interface with ConfLowerBound
        vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200.
        However, there could not be a third entry with
        ConfLowerBound vpi/vci == 0/200 and
        ConfUpperBound vpi/vci == 0/300 because this label
        range overlaps with the second entry (i.e. both
        entries now have 0/200).
        
        A row will not be created unless a unique and
        non-overlapping range is specified.  Thus, row
        creation implies a one-shot row creation of
        LDP EntityID and ConfLowerBound vpi/vci and
        ConfUpperBound vpi/vci.  At least one label
        range entry for a specific LDP Entity MUST
        include the default VPI/VCI  values denoted
        in the LDP Entity Table."
    INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpEntityConfAtmLabelRangeMinimumVpi, mplsLdpEntityConfAtmLabelRangeMinimumVci }
    ::= { mplsLdpEntityConfAtmLabelRangeTable 1 }
Information from OID Repository
Vendor: Cisco
Module: MPLS-LDP-MIB

[Automatically extracted from oidview.com]
Information from Cisco
mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE
         SYNTAX MplsLdpEntityConfAtmLabelRangeEntry
         MAX-ACCESS not-accessible
         STATUS current
         DESCRIPTION
             "A row in the LDP Entity Configurable ATM Label
             Range Table.  One entry in this table contains
             information on a single range of labels
             represented by the configured Upper and Lower
             Bounds VPI/VCI pairs.  These are the same
             data used in the Initialization Message.

             NOTE:  The ranges for a specific LDP Entity
             are UNIQUE and non-overlapping.  For example,
             for a specific LDP Entity index, there could
             be one entry having ConfLowerBound vpi/vci == 0/32, and
             ConfUpperBound vpi/vci == 0/100, and a second entry
             for this same interface with ConfLowerBound
             vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200.
             However, there could not be a third entry with
             ConfLowerBound vpi/vci == 0/200 and
             ConfUpperBound vpi/vci == 0/300 because this label
             range overlaps with the second entry (i.e. both
             entries now have 0/200).

             A row will not be created unless a unique and
             non-overlapping range is specified.  Thus, row
             creation implies a one-shot row creation of
             LDP EntityID and ConfLowerBound vpi/vci and
             ConfUpperBound vpi/vci.  At least one label
             range entry for a specific LDP Entity MUST
             include the default VPI/VCI  values denoted
             in the LDP Entity Table."
         INDEX       {  mplsLdpEntityLdpId,
                        mplsLdpEntityIndex,
                        mplsLdpEntityConfAtmLabelRangeMinimumVpi,
                        mplsLdpEntityConfAtmLabelRangeMinimumVci
                     }
         ::= { mplsLdpEntityConfAtmLabelRangeTable 1 }
Information from Circitor
mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE
         SYNTAX MplsLdpEntityConfAtmLabelRangeEntry
         MAX-ACCESS not-accessible
         STATUS current
         DESCRIPTION
             "A row in the LDP Entity Configurable ATM Label
             Range Table.  One entry in this table contains
             information on a single range of labels
             represented by the configured Upper and Lower
             Bounds VPI/VCI pairs.  These are the same
             data used in the Initialization Message.

             NOTE:  The ranges for a specific LDP Entity
             are UNIQUE and non-overlapping.  For example,
             for a specific LDP Entity index, there could
             be one entry having ConfLowerBound vpi/vci == 0/32, and
             ConfUpperBound vpi/vci == 0/100, and a second entry
             for this same interface with ConfLowerBound
             vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200.
             However, there could not be a third entry with
             ConfLowerBound vpi/vci == 0/200 and
             ConfUpperBound vpi/vci == 0/300 because this label
             range overlaps with the second entry (i.e. both
             entries now have 0/200).

             A row will not be created unless a unique and
             non-overlapping range is specified.  Thus, row
             creation implies a one-shot row creation of
             LDP EntityID and ConfLowerBound vpi/vci and
             ConfUpperBound vpi/vci.  At least one label
             range entry for a specific LDP Entity MUST
             include the default VPI/VCI  values denoted
             in the LDP Entity Table."
         INDEX       {  mplsLdpEntityLdpId,
                        mplsLdpEntityIndex,
                        mplsLdpEntityConfAtmLabelRangeMinimumVpi,
                        mplsLdpEntityConfAtmLabelRangeMinimumVci
                     }
         ::= { mplsLdpEntityConfAtmLabelRangeTable 1 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.10.65.1.2.4.2.1.1 mplsLdpEntityConfAtmLabelRangeMinimumVpi, mplsLdpEntityConfAtmLRMinVpi00 The minimum VPI number configured for this range.
1.3.6.1.4.1.9.10.65.1.2.4.2.1.2 mplsLdpEntityConfAtmLabelRangeMinimumVci, mplsLdpEntityConfAtmLRMinVci00 The minimum VCI number configured for this range.
1.3.6.1.4.1.9.10.65.1.2.4.2.1.3 mplsLdpEntityConfAtmLabelRangeMaximumVpi, mplsLdpEntityConfAtmLRMaxVpi00 The maximum VPI number configured for this range.
1.3.6.1.4.1.9.10.65.1.2.4.2.1.4 mplsLdpEntityConfAtmLabelRangeMaximumVci, mplsLdpEntityConfAtmLRMaxVci00 The maximum VCI number configured for this range.
1.3.6.1.4.1.9.10.65.1.2.4.2.1.5 mplsLdpEntityConfAtmLabelRangeStorageType, mplsLdpEntityConfAtmLRStorType00 The storage type for this entry.
1.3.6.1.4.1.9.10.65.1.2.4.2.1.6 mplsLdpEntityConfAtmLabelRangeRowStatus, mplsLdpEntityConfAtmLRRowStatus00 An object that allows entries in this
table to be created and deleted using
the RowStatus convention.

There must exist at least on…