Configuring VLANs Using Private VLANs
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 4-25
• Untagged traffic is passed into an untagged Secondary (community) port 1 on OmniSwitch-1.
– The traffic will be tagged with the PVID of the port which is Secondary VLAN.
– The ISL port will then carry the tagged traffic into the community port on the other switch
(OmniSwitch-2:1, OmniSwitch-2:2).
– Traffic outgoing through the promiscuous port (OmniSwitch-3: P: 100) will modify the tag to
Primary VLAN.
• Tagged traffic is passed into an untagged Secondary (community) port
– If the tag matches the PVID of the port, it will be allowed.
– The ISL port will then carry the tagged traffic into the community port on the other switch
(OmniSwitch-2:1, OmniSwitch-2:2).
– Traffic outgoing through promiscuous port (OmniSwitch-3: P: 100) will modify the tag to Primary
VLAN.
• Untagged traffic passed into a tagged Secondary (community) port is dropped.
• Tagged traffic passed into a tagged Secondary (community) port is dropped if the VLAN tag of the
traffic does not match the VLAN tag of the port.
Verifying the PVLAN Configuration
To display information about the PVLAN configuration, use the show commands listed below:
Use the show configuration snapshot command with the pvlan option to display the PVLAN
configuration. For example:
-> show configuration snapshot pvlan
! PVLAN:
pvlan 300 admin-state enable
pvlan 300 secondary 20-25 type community
pvlan 300 members port 1/3/10 tagged
pvlan 300 members linkagg 10 tagged
show pvlan Displays a list of PVLANs configured on the switch.
show pvlan mapping Displays Primary PVLAN and Secondary PVLAN mapping.
show pvlan members Displays port associations (VPAs) for all or specific PVLANs.
To Next Page
Loading...
Need help?
General
