Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mplsLdpEntityAtmMergeCap",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notSupported",
"(",
"0",
")",
",",
"vpMerge",
"(",
"1",
")",
",",
"vcMerge",
"(",
"2",
")",
",",
"vpAndVcMerge",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Denotes the Merge Capability of this Entity. This is the EXACT value for the ATM Session Parameter, field M (for ATM Merge Capabilities). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate. - The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.' Please refer to the following reference for a complete description of this feature.\"",
"REFERENCE",
"\"RFC3036, LDP Specification, Section 3.5.3 Initialization Message.\"",
"::=",
"{",
"mplsLdpEntityAtmEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notSupported",
0
],
[
"vpMerge",
1
],
[
"vcMerge",
2
],
[
"vpAndVcMerge",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Denotes the Merge Capability of this Entity. This is the EXACT value for the ATM Session Parameter, field M (for ATM Merge Capabilities). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate. - The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.' Please refer to the following reference for a complete description of this feature."
],
[
"REFERENCE",
"RFC3036, LDP Specification, Section 3.5.3 Initialization Message."
],
null,
null,
null
]
}