Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
SmartFabric Services with Multisite vSAN Stretched Cluster Deployment Guide
Notes, cautions, and warnings Introduction Hardware Used in this Guide Topology Deployment Planning
Minimum requirements
Unsupported features
Networks and IP addresses
BGP ASNs and router IDs
DNS server records
SFS default fabric settings
SFS switch configuration Configure DCI switches Configure Fabric Interconnects Configure Networks Add ESXi hosts to topology Configure a jump host Deploy the DNS server and the vCenter Server ESXi services and witness host configuration Deploy the vSAN Stretched Cluster Migrate the vCenter Server and the DNS server Add User VMs Deploy OMNI Validated Components Technical Resources CLI Command Output

Networks and IP addresses

Home > Networking Solutions > Converged and Hyperconverged Solutions > vSAN Networking Solutions > Guides > SmartFabric Services with Multisite vSAN Stretched Cluster Deployment Guide > Networks and IP addresses

Networks and IP addresses

  • Networks and IP addresses used for the vSAN stretched cluster should be planned before starting deployment. The SmartFabric VLAN IDs and network addresses used in this guide are shown in the following table.

    Table 1. SmartFabric VLAN IDs and network addresses used in this deployment
    VLAN ID Description SFS network name Network Gateway
    11 Management mgmt-11 192.168.11.0/24 192.168.11.254
    12 vMotion vmotion-12 192.168.12.0/24 None
    13 vSAN vsan-13 192.168.13.0/24 192.168.13.254
    20 VM Data (optional) vmdata-20 192.168.20.0/24 192.168.20.254

    With SFS, each VLAN in the table above is automatically placed in a VXLAN virtual network with a Virtual Network Identifier (VNI) that matches the VLAN ID. VLAN 11 is in virtual network 11, VLAN 12 is in virtual network 12, and so on.

    The Management VLAN is used for ESXi host management, vCenter Server, DNS, and NTP traffic. The vMotion VLAN is for VM migration, and the vSAN VLAN is for distributed storage traffic. The VM Data VLAN is optional and is used in this guide to demonstrate how additional VLANs are deployed and configured.

    Note: The Management network is part of the production topology and is in-band. This is not to be confused with the OOB management network.

    A gateway is required for Management and vSAN traffic for communication with the witness host. The vMotion VLAN does not require a gateway. vMotion is only done in this deployment between Site 1 and Site 2, and all vMotion traffic is Layer 2. For additional VLANs such as VM data, a gateway is only required if the VMs need to communicate outside of their existing network.

    The VLAN IDs and network IP addresses in the table above are examples only. In SmartFabric mode, VLANs 1 through 3999, excluding VLAN 3939, are available for use.

    Note: SFS reserves VLANs 3939 and 4000 through 4094. By default, server ports connected to the SmartFabric are untagged in VLAN 4091. For more information about the reserved VLANs, see the SFS default fabric settings section below and the Dell SmartFabric Services User Guide, Release 10.5.3.

    In a vSAN stretched cluster, the witness host has one VLAN for Management traffic, and one VLAN for vSAN traffic. The witness host does not participate in vMotion.

    The VLAN IDs and network addresses used for the witness host are shown in the following table. These VLANs are configured on the DCI-Site-3 switch that the witness host is connected to. The networks differ from the SmartFabric networks because all traffic is routed to the witness host in this deployment.

    Table 2. Witness host VLAN IDs and network addresses used in this deployment
    VLAN ID Description Network Gateway
    31 Management – witness host 192.168.31.0/24 192.168.31.254
    33 vSAN – witness host 192.168.33.0/24 192.168.33.254