182
VLAN ID: 2
VLAN type: Static
Private VLAN type: Secondary
Route interface: Not configured
Description: VLAN 0002
Name: VLAN 0002
Tagged ports: None
Untagged ports:
Ten-GigabitEthernet1/0/2
Ten-GigabitEthernet1/0/5
VLAN ID: 3
VLAN type: Static
Private VLAN type: Secondary
Route interface: Not configured
Description: VLAN 0003
Name: VLAN 0003
Tagged Ports: None
Untagged Ports:
Ten-GigabitEthernet1/0/3
Ten-GigabitEthernet1/0/5
The output shows that:
• The promiscuous port (Ten-GigabitEthernet 1/0/5) is an untagged member of primary VLAN 5
and secondary VLANs 2 and 3.
• Host port Ten-GigabitEthernet 1/0/2 is an untagged member of primary VLAN 5 and secondary
VLAN 2.
• Host port Ten-GigabitEthernet 1/0/3 is an untagged member of primary VLAN 5 and secondary
VLAN 3.
Trunk promiscuous port configuration example
Network requirements
As shown in Figure 60, configure the private VLAN feature to meet the following requirements:
• VLANs 5 and 10 are primary VLANs on Device B. The uplink port (Ten-GigabitEthernet 1/0/1)
on Device B permits the packets from VLANs 5 and 10 to pass through tagged.
• On Device B, downlink port Ten-GigabitEthernet 1/0/2 permits secondary VLAN 2. Downlink
port Ten-GigabitEthernet 1/0/3 permits secondary VLAN 3. Secondary VLANs 2 and 3 are
associated with primary VLAN 5.
• On Device B, downlink port Ten-GigabitEthernet 1/0/4 permits secondary VLAN 6. Downlink
port Ten-GigabitEthernet 1/0/5 permits secondary VLAN 8. Secondary VLANs 6 and 8 are
associated with primary VLAN 10.
• Device A is aware of only VLANs 5 and 10 on Device B.