Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"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",
"}"
],
"syntax_tree": [
[
"row",
"MplsLdpEntityConfAtmLabelRangeEntry"
],
null,
[
"MaxAccessPart",
"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."
],
null,
null,
[
"INDEX",
[
[
0,
"mplsLdpEntityLdpId"
],
[
0,
"mplsLdpEntityIndex"
],
[
0,
"mplsLdpEntityConfAtmLabelRangeMinimumVpi"
],
[
0,
"mplsLdpEntityConfAtmLabelRangeMinimumVci"
]
]
],
null
]
}