Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMIDot1qFutureVlanPortType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"accessPort",
"(",
"1",
")",
",",
"trunkPort",
"(",
"2",
")",
",",
"hybridPort",
"(",
"3",
")",
",",
"hostPort",
"(",
"4",
")",
",",
"promiscuousPort",
"(",
"5",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing Vlans and also for any new vlan created. When configured as hybrid port, the port can send or accept both tagged and untagged frames. hostPort, promiscuousPort are types of port in PVLAN domain. Behaviour of host port varies based on the secondary vlan to which it is configured as member port. If a host port is a member port of an isolated VLAN, traffic from the host port is sent only to the promiscuous port of the Private VLAN and the trunk port. If a host port is a member port of the community VLAN, traffic from the port can be sent only to other ports of the community VLAN , trunk port and promiscuous port of the private VLAN. A host port can be associated with only one secondary vlan and with the associated primary vlan. The PVID of host port will be set the ID of the secondary vlan to which it belongs to. If a host port is member port of primary vlan, but is not member port of any secondary vlan, then its PVID will be set to primary vlan id. Promiscuous ports should be configured as member port of primary vlan and member port of all(some) secondary vlans associated with that primary vlan. The PVID of promiscuous port will be set as the ID of the primary vlan to which it belongs to. Host and promiscuous ports should be configured as untagged members of primary/secondary vlans. When a access/hybrid port is configured as a member port of a primary/secondary vlan, it becomes a hostPort automatically.\"",
"DEFVAL",
"{",
"hybridPort",
"}",
"::=",
"{",
"fsMIDot1qFutureVlanPortEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"accessPort",
1
],
[
"trunkPort",
2
],
[
"hybridPort",
3
],
[
"hostPort",
4
],
[
"promiscuousPort",
5
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing Vlans and also for any new vlan created. When configured as hybrid port, the port can send or accept both tagged and untagged frames. hostPort, promiscuousPort are types of port in PVLAN domain. Behaviour of host port varies based on the secondary vlan to which it is configured as member port. If a host port is a member port of an isolated VLAN, traffic from the host port is sent only to the promiscuous port of the Private VLAN and the trunk port. If a host port is a member port of the community VLAN, traffic from the port can be sent only to other ports of the community VLAN , trunk port and promiscuous port of the private VLAN. A host port can be associated with only one secondary vlan and with the associated primary vlan. The PVID of host port will be set the ID of the secondary vlan to which it belongs to. If a host port is member port of primary vlan, but is not member port of any secondary vlan, then its PVID will be set to primary vlan id. Promiscuous ports should be configured as member port of primary vlan and member port of all(some) secondary vlans associated with that primary vlan. The PVID of promiscuous port will be set as the ID of the primary vlan to which it belongs to. Host and promiscuous ports should be configured as untagged members of primary/secondary vlans. When a access/hybrid port is configured as a member port of a primary/secondary vlan, it becomes a hostPort automatically."
],
null,
null,
null,
[
"DEFVAL",
"hybridPort"
]
]
}