Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ostEvcType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"standardEvc",
"(",
"1",
")",
",",
"simpleETree",
"(",
"2",
")",
",",
"branchETree",
"(",
"3",
")",
",",
"trunkETree",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object defines type of EVC. standardEvc(1) The EVC type is a standard EVC, following normal forwarding rules for all the ports associated with the EVC (ostEvcPortList) simpleETree(2) The EVC is a type of simple Rooted Multipoint (E-Tree) that uses the EVC defined ports (ostEvcPortList) and root ports (ostEvcEtreePortList). The S-TAG VID is used for both Root and Leaf Ports Root Ports send to and receive from Leaf and Root Ports Leaf Ports send to and receive from Root ports, but do not send to or receive from Leaf ports branchETree(3) The EVC is a type of complex Rooted Multiport (E-Tree) that supports an S-TAG that is designated as a Branch S-TAG and uses the EVC defined ports (ostEvcPortList) and root ports (ostEvcEtreePortList). Root Ports receive on the Branch S-TAG Leaf Ports send on the Branch S-TAG trunkETree(4) The EVC is a type of complex Rooted Multiport (E-Tree) that supports an S-TAG that is designated as a Trunk S-TAG and uses the EVC defined ports (ostEvcPortList) and root ports (ostEvcEtreePortList). Root Ports send/receive on the Trunk S-TAG Leaf Ports receive on the Trunk S-TAG For correct operation the complex E-Tree that uses the Branch and Trunk construct should have both a branchETree EVC and a trunkETree EVC defined for the same ports. At a UNI interface only ports designated as Leaf Ports have a definition, i.e. ostIfEvcCeVlanIdList, for the branchETree EVC and Root Ports only have a definition for the trunkETree EVC. This object is supported by the GM4, GM4-PoE, and XM5. \"",
"DEFVAL",
"{",
"standardEvc",
"}",
"::=",
"{",
"ostEvcEntry",
"20",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"standardEvc",
1
],
[
"simpleETree",
2
],
[
"branchETree",
3
],
[
"trunkETree",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object defines type of EVC. standardEvc(1) The EVC type is a standard EVC, following normal forwarding rules for all the ports associated with the EVC (ostEvcPortList) simpleETree(2) The EVC is a type of simple Rooted Multipoint (E-Tree) that uses the EVC defined ports (ostEvcPortList) and root ports (ostEvcEtreePortList). The S-TAG VID is used for both Root and Leaf Ports Root Ports send to and receive from Leaf and Root Ports Leaf Ports send to and receive from Root ports, but do not send to or receive from Leaf ports branchETree(3) The EVC is a type of complex Rooted Multiport (E-Tree) that supports an S-TAG that is designated as a Branch S-TAG and uses the EVC defined ports (ostEvcPortList) and root ports (ostEvcEtreePortList). Root Ports receive on the Branch S-TAG Leaf Ports send on the Branch S-TAG trunkETree(4) The EVC is a type of complex Rooted Multiport (E-Tree) that supports an S-TAG that is designated as a Trunk S-TAG and uses the EVC defined ports (ostEvcPortList) and root ports (ostEvcEtreePortList). Root Ports send/receive on the Trunk S-TAG Leaf Ports receive on the Trunk S-TAG For correct operation the complex E-Tree that uses the Branch and Trunk construct should have both a branchETree EVC and a trunkETree EVC defined for the same ports. At a UNI interface only ports designated as Leaf Ports have a definition, i.e. ostIfEvcCeVlanIdList, for the branchETree EVC and Root Ports only have a definition for the trunkETree EVC. This object is supported by the GM4, GM4-PoE, and XM5."
],
null,
null,
null,
[
"DEFVAL",
"standardEvc"
]
]
}