© Copyright IBM Corp. 2011
Chapter 8. VLANs
103
Port-Based vs. Protocol-Based VLANs
Each VLAN supports both port-based and protocol-based association, as follows:
•
The default VLAN configuration is port-based. All data ports are members of
VLAN 1, with no PVLAN association.
•
When you add ports to a PVLAN, the ports become members of both the
port-based VLAN and the PVLAN. For example, if you add port 1 to PVLAN 1 on
VLAN 2, the port also becomes a member of VLAN 2.
•
When you delete a PVLAN, it’s member ports remain members of the port-based
VLAN. For example, if you delete PVLAN 1 from VLAN 2, port 1 remains a
member of VLAN 2.
•
When you delete a port from a VLAN, the port is deleted from all corresponding
PVLANs.
PVLAN Priority Levels
You can assign each PVLAN a priority value of 0-7, used for Quality of Service
(QoS). PVLAN priority takes precedence over a port’s configured priority level. If no
priority level is configured for the PVLAN (priority = 0), each port’s priority is used (if
configured).
All member ports of a PVLAN have the same PVLAN priority level.
PVLAN Tagging
When PVLAN tagging is enabled, the switch tags frames that match the PVLAN
protocol. For more information about tagging, see
Untagged ports must have PVLAN tagging disabled. Tagged ports can have PVLAN
tagging either enabled or disabled.
PVLAN tagging has higher precedence than port-based tagging. If a port is tag
enabled, and the port is a member of a PVLAN, the PVLAN tags egress frames that
match the PVLAN protocol.
Use the tag list command (
protocol-vlan
<x>
tag-pvlan
) to define the
complete list of tag-enabled ports in the PVLAN. Note that all ports not included in
the PVLAN tag list will have PVLAN tagging disabled.
PVLAN Configuration Guidelines
Consider the following guidelines when you configure protocol-based VLANs:
•
Each port can support up to 16 VLAN protocols.
•
The G8000 can support up to 16 protocols simultaneously.
•
Each PVLAN must have at least one port assigned before it can be activated.
•
The same port within a port-based VLAN can belong to multiple PVLANs.
•
An untagged port can be a member of multiple PVLANs.
•
A port cannot be a member of different VLANs with the same protocol
association.
Summary of Contents for RackSwitch G8000
Page 1: ...RackSwitch G8000 Application Guide...
Page 2: ......
Page 3: ...RackSwitch G8000 Application Guide...
Page 16: ...16 RackSwitch G8000 Application Guide...
Page 22: ...20 RackSwitch G8000 Application Guide...
Page 23: ...Copyright IBM Corp 2011 21 Part 1 Getting Started...
Page 24: ...22 RackSwitch G8000 Application Guide...
Page 54: ...52 RackSwitch G8000 Application Guide...
Page 55: ...Copyright IBM Corp 2011 53 Part 2 Securing the Switch...
Page 56: ...54 RackSwitch G8000 Application Guide...
Page 92: ...90 RackSwitch G8000 Application Guide...
Page 94: ...92 RackSwitch G8000 Application Guide...
Page 144: ...142 RackSwitch G8000 Application Guide...
Page 145: ...Copyright IBM Corp 2011 143 Part 4 Advanced Switch ing Features...
Page 146: ...144 RackSwitch G8000 Application Guide...
Page 148: ...146 RackSwitch G8000 Application Guide...
Page 182: ...180 RackSwitch G8000 Application Guide...
Page 184: ...182 RackSwitch G8000 Application Guide...
Page 212: ...210 RackSwitch G8000 Application Guide...
Page 258: ...256 RackSwitch G8000 Application Guide...
Page 286: ...284 RackSwitch G8000 Application Guide...
Page 294: ...292 RackSwitch G8000 Application Guide...
Page 298: ...296 RackSwitch G8000 Application Guide...
Page 310: ...308 RackSwitch G8000 Application Guide...
Page 311: ...Copyright IBM Corp 2011 309 Part 7 Network Management...
Page 312: ...310 RackSwitch G8000 Application Guide...
Page 320: ...318 RackSwitch G8000 Application Guide...
Page 332: ...330 RackSwitch G8000 Application Guide...
Page 334: ...332 RackSwitch G8000 Application Guide...
Page 345: ...Copyright IBM Corp 2011 343 Part 9 Appendices...
Page 346: ...344 RackSwitch G8000 Application Guide...
Page 357: ...Copyright IBM Corp 2011 Appendix C Notices 355 Taiwan Class A compliance statement...