Home > Integrated Products > VxBlock 1000 and 3-Tier Platform Reference Architectures > White Papers > VMware Cloud Foundation Stretched Cluster on Dell VxBlock 1000 Multi-Site > Workload domain network topology
In an environment with multiple availability zones, Layer 2 networks must be stretched between the availability zones by the physical infrastructure.
Layer 3 gateways are in the VxBlock 1000 Cisco Nexus 9000 Switches and are highly available between availability zones.
Note: Static IP pools are not available for w-host-overlay. In a Multi AZ deployment, DHCP must be used.
The following table shows how the VLANs must be physically stretched between availability zones:
Function | Availability zone | VLAN ID | IP range |
w-mgmt | AZ1 and AZ2 | 1631 (Stretched) | 172.16.31.0/24 |
w-edge-uplink01 | AZ1 and AZ2 | 2731 (Stretched) | 172.27.31.0/24 |
w-edge-uplink02 | AZ1 and AZ2 | 2732 (Stretched) | 172.27.32.0/24 |
w-edge-overlay | AZ1 and AZ2 | 2733 (Stretched) | 172.27.33.0/24 |
The following table shows the VLANs that are created in each availability zone. The VLANs use the same VLAN numbers but are in different subnets of each availability zone.
Function | Availability zone | VLAN ID | IP range |
w-vmotion | AZ1 | 1632 | 172.16.32.0/24 |
w-host-overlay | AZ1 | 1634 | 172.16.34.0/24 (DHCP) |
w-vmotion | AZ2 | 1632 | 172.16.42.0/24 |
w-host-overlay | AZ2 | 1634 | 172.16.44.0/24 (DHCP) |
Stretched VLAN SVIs have different priorities on the ToR Cisco Nexus 9000 Switches to route traffic to the AZ1 ToR switch. The NSX Tier 0 peers with ToR Cisco Nexus 9000 Switches in AZs 1 and 2 by using the w-edge-uplink01 and w-edge-uplink02 stretched VLANs. NSX BGP local preference and route maps are applied to AZ 2 to ensure inbound and outbound traffic occurs through AZ1, unless it is down. Each AZ ToR Cisco Nexus 9000 Switch pair requires a unique BGP autonomous system ID. Each AZ ToR Cisco Nexus 9000 Switch pair must be in a different VPC domain. Expansion of a cluster requires that all the hosts have a shared datastore before creating the initial cluster or VI workload domain.
Note: When BGP is not used from the VxBlock 1000 to the customer core, configure the routing protocol at the customer core to use AZ 1 over AZ 2.
In the following figure, the NSX edge VMs are peered with the ToR Cisco Nexus 9000 Switches in each availability zone. HSRP on the ToR switches and route maps in the Tier 0 gateway cause the inbound and outbound traffic to use the switches in AZ 1.
The following table lists the workload domain VLANs for AZ-1 and AZ-2:
AZ1 and AZ2 workload domain VLANs | VLAN IDs |
1631 stretch | |
w-vmotion | 1632 |
w-host-overlay | 1634 |
w-edge-overlay | 2733 stretch |
w-edge-uplink01 | 2731 stretch |
w-edge-uplink01 | 2732 stretch |
The following list details the route maps for AZ-2, which apply to the AZ-2 neighbors: