Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
Planning Guide—VMware Cloud Foundation 4.0 on VxRail
Cloud Foundation on VxRail Physical Network Preparation
Introduction Capture configuration settings for Cloud Foundation on VxRail VxRail cluster and NSX-T networks leaf switch preparation DHCP services for NSX-T host overlay network preparation Application Virtual Network leaf switch preparation Layer 3 network preparation BGP peering preparation

VxRail cluster and NSX-T networks leaf switch preparation

  • While the networking requirements for VxRail and Cloud Foundation differ, there is overlap in the sense that Cloud Foundation domains depend on the networking resources enabled by VxRail for connectivity. Therefore, the supporting physical network must be properly designed and configured to support VxRail cluster network traffic, as well as the additional requirements for Cloud Foundation.

    Figure 29.          VxRail and NSX-T Overlay Networks

    A leaf switch is at the lowest tier in a multi-tier architecture, and often referred to as a ‘top-of-rack’ switch. The VxRail nodes will only connect with a leaf switches in a single rack, with the upper tier switches enable multi-rack interconnectivity. The following tasks must be performed in the top-of-rack switches in order to prepare for a VxRail cluster deployment and to prepare to support NSX-T:

    1. Select switches with sufficient open ports for Cloud Foundation on VxRail.
    1. Configure at least 1600 MTU to support host overlay network traffic (9000 preferred). A minimum MTU size of 1600 (9000 preferred) must be configured on the ToR switches.
    2. Make sure the port type on the switches (RJ45, SFP+) match the port type on the VxRail nodes.
    3. Configure each of the VLANs required for VxRail on the switches.
    4. Configure VLAN for the NSX-T host overlay network on the switches.
    5. Configure the switch ports to be directly connected to the VxRail nodes as Layer 2 trunk ports.
    6. Configure unicast on the VLAN representing the vSAN network.
    7. Configure multicast on the VLAN representing the VxRail Internal Management network.
    8. Configure MLD snooping and MLD querier on the VLAN representing the VxRail Internal Management Network (recommended).
    9. Configure Spanning Tree on the switch ports to be directly connected to the VxRail nodes as edge ports, or in ‘portfast’ mode.
    10. If the Layer 2 networks do not terminate at the top-of-rack switches, configure the inter-switch links to allow passage for all VLANs.

    Each VxRail node has a separate Ethernet port for out-of-band server management called ‘Integrated Dell Remote Access Controller’ (iDRAC). A separate Ethernet switch is recommended to provide connectivity for server maintenance. The server maintenance traffic can also be redirected through the existing network infrastructure. For complete details about VxRail cluster network requirements, see the Dell EMC VxRail Network Planning Guide.

    The table in Appendix C: Cloud Foundation on VxRail VLANs lists the individual VLANs that need to be configured on the top-of-rack switches. The example switch configuration syntax displayed in Error! Reference source not found. offers guidance on how to configure an Ethernet switch with sample VLANs and a sample switch port configuration.

next

DHCP services for NSX-T host overlay network preparation