Chapter 14. Network Setup
162
14.2. VLAN Allocation Example
VLANs are required for public and guest traffic. The following is an example of a VLAN allocation
scheme:
VLAN IDs Traffic type Scope
less than 500 Management traffic. Reserved
for administrative purposes.
CloudPlatform software can
access this, hypervisors,
system VMs.
500-599 VLAN carrying public traffic. CloudPlatform accounts.
600-799 VLANs carrying guest traffic. CloudPlatform accounts.
Account-specific VLAN is
chosen from this pool.
800-899 VLANs carrying guest traffic. CloudPlatform accounts.
Account-specific VLAN chosen
by CloudPlatform admin to
assign to that account.
900-999 VLAN carrying guest traffic CloudPlatform accounts. Can
be scoped by project, domain,
or all accounts.
greater than 1000 Reserved for future use
14.3. Example Hardware Configuration
This section contains an example configuration of specific switch models for zone-level layer-3
switching. It assumes VLAN management protocols, such as VTP or GVRP, have been disabled. The
example scripts must be changed appropriately if you choose to use VTP or GVRP.
14.3.1. Dell 62xx
The following steps show how a Dell 62xx is configured for zone-level layer-3 switching. These steps
assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is
connected to Ethernet port 1/g1.
The Dell 62xx Series switch supports up to 1024 VLANs.
1. Configure all the VLANs in the database.
vlan database
vlan 200-999
exit
2. Configure Ethernet port 1/g1.
interface ethernet 1/g1
switchport mode general
switchport general pvid 201
switchport general allowed vlan add 201 untagged
switchport general allowed vlan add 300-999 tagged
exit
The statements configure Ethernet port 1/g1 as follows:
• VLAN 201 is the native untagged VLAN for port 1/g1.