Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dPrivateVlanIfVlanMapEntry",
"OBJECT-TYPE",
"SYNTAX",
"DPrivateVlanIfVlanMapEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"An entry configures an association between a secondary VLAN and a primary VLAN on a port/port-channel whose port mode is host, promiscuous, trunk secondary or trunk promiscuous. If the port is private vlan host port, at most one dPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID can be created for a port/port-channel. In other words, a host port only can belong to at most one secondary VLAN. If the port is private vlan promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. But it cannot be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple dPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (dPrivateVlanIfVlanMapSecVlanId) in one private VLAN (dPrivateVlanIfVlanMapPriVlan) can be created for a port/port-channel. But multiple dPrivateVlanIfVlanMapEntry with different private VLAN IDs (dPrivateVlanIfVlanMapPriVlan) cannot be created for a port/port-channel. If the port is private vlan trunk promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. It also can be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple dPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (dPrivateVlanIfVlanMapSecVlanId) can be created for a port/port-channel, and multiple dPrivateVlanIfVlanMapEntry with different private VLAN IDs (dPrivateVlanIfVlanMapPriVlan) also can be created for a port/port-channel. If the port is private vlan trunk secondary port, it only can be mapped to at most one secondary VLAN in a private VLAN. But it can be mapped to multiple private VLANs. In other words, a dPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID in a private VLAN can be created for a port/port-channel. And the dPrivateVlanIfVlanMapEntry with multiple private VLANs (dPrivateVlanIfVlanMapPriVlan)can also be created for a port/port-channel. \"",
"INDEX",
"{",
"dPrivateVlanMappingPortIndex",
",",
"dPrivateVlanIfVlanMapSecVlanId",
"}",
"::=",
"{",
"dPrivateVlanIfVlanMapTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"DPrivateVlanIfVlanMapEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"An entry configures an association between a secondary VLAN and a primary VLAN on a port/port-channel whose port mode is host, promiscuous, trunk secondary or trunk promiscuous. If the port is private vlan host port, at most one dPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID can be created for a port/port-channel. In other words, a host port only can belong to at most one secondary VLAN. If the port is private vlan promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. But it cannot be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple dPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (dPrivateVlanIfVlanMapSecVlanId) in one private VLAN (dPrivateVlanIfVlanMapPriVlan) can be created for a port/port-channel. But multiple dPrivateVlanIfVlanMapEntry with different private VLAN IDs (dPrivateVlanIfVlanMapPriVlan) cannot be created for a port/port-channel. If the port is private vlan trunk promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. It also can be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple dPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (dPrivateVlanIfVlanMapSecVlanId) can be created for a port/port-channel, and multiple dPrivateVlanIfVlanMapEntry with different private VLAN IDs (dPrivateVlanIfVlanMapPriVlan) also can be created for a port/port-channel. If the port is private vlan trunk secondary port, it only can be mapped to at most one secondary VLAN in a private VLAN. But it can be mapped to multiple private VLANs. In other words, a dPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID in a private VLAN can be created for a port/port-channel. And the dPrivateVlanIfVlanMapEntry with multiple private VLANs (dPrivateVlanIfVlanMapPriVlan)can also be created for a port/port-channel."
],
null,
null,
[
"INDEX",
[
[
0,
"dPrivateVlanMappingPortIndex"
],
[
0,
"dPrivateVlanIfVlanMapSecVlanId"
]
]
],
null
]
}