VMware Cloud Foundation 5.1

5.2 5.1 5.0 4.5
Français Italiano 日本語

VLANs and Subnets for

Configure your VLANs and subnets according to the guidelines and requirements for
.
When designing the VLAN and subnet configuration for your
deployment, consider the following guidelines:
VLAN and Subnet Guidelines for
All Deployment Topologies
Multiple Availability Zones
NSX Federation Between Multiple
Instances
  • Ensure your subnets are scaled appropriately to allow for expansion as expanding at a later time can be disruptive.
  • Use the IP address of the floating interface for Virtual Router Redundancy Protocol (VRPP) or Hot Standby Routing Protocol (HSRP) as the gateway.
  • Use the RFC 1918 IPv4 address space for these subnets and allocate one octet by
    instance and another octet by function.
  • For network segments which are stretched between availability zones, the VLAN ID must meet the following requirements:
    • Be the same in both availability zones with the same Layer 3 network segments.
    • Have a Layer 3 gateway at the first hop that is highly available such that it tolerates the failure of an entire availability zone.
  • For network segments of the same type which are not stretched between availability zones, the VLAN ID can be the same or different between the zones.
  • An RTEP network segment should have a VLAN ID and Layer 3 range that are specific to the
    instance.
  • In a
    instance with multiple availability zones, the RTEP network segment must be stretched between the zones and assigned the same VLAN ID and IP range.
  • All Edge RTEP networks must reach each other.
When deploying VLANs and subnets for
, they must conform to the following requirements according to the
topology:
Choosing a VLAN Model for Host and Management VM Traffic
The first decision is based on the need to access separately hosts and management VMs. If not, the next decision is based on the traffic isolation. If neither is required, use the same VLAN. If either is required, use separate VLANs.
VLANs and Subnets for
Function
 Instances with a Single Availability Zone
 Instances with Multiple Availability Zones
VM management
  • Required
  • Highly available gateway within the instance
  • Required
  • Must be stretched within the instance
  • Highly available gateway across availability zones within the instance
Host management - first availability zone
  • Required
  • Highly available gateway within the instance
  • Required
  • Highly available gateway across availability zones within the instance
vSphere vMotion - first availability zone
  • Required
  • Highly available gateway within the instance
  • Required
  • Highly available gateway in first availability zone within the instance
vSAN - first availability zone
  • Required
  • Highly available gateway within the instance
  • Required
  • Highly available gateway in first availability zone within the instance
Host overlay - first availability zone
  • Required
  • Highly available gateway within the instance
  • Required
  • Highly available gateway in first availability zone within the instance
Uplink01
  • Required
  • Gateway optional
  • Required
  • Gateway optional
  • Must be stretched within the instance
Uplink02
  • Required
  • Gateway optional
  • Required
  • Gateway optional
  • Must be stretched within the instance
Edge overlay
  • Required
  • Highly available gateway within the instance
  • Required
  • Must be stretched within the instance
  • Highly available gateway across availability zones within the instance
Host management - second availability zone
  • Not required
  • Required
  • Highly available gateway in second availability zone within the instance
vSphere vMotion - second availability zone
  • Not required
  • Required
  • Highly available gateway in second availability zone within the instance
vSAN - second availability zone
  • Not required
  • Required
  • Highly available gateway in second availability zone within the instance
Host overlay - second availability zone
  • Not required
  • Required
  • Highly available gateway in second availability zone within the instance
Edge RTEP
  • Required for NSX Federation only
  • Highly available gateway within the instance
  • Required for NSX Federation only
  • Must be stretched within the instance
  • Highly available gateway across availability zones within the instance
Management and Witness - witness appliance at a third location
  • Not required
  • Required
  • Highly available gateway at the witness location

Content feedback and comments