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
Dell VxRail Network Planning Guide
Introduction Planning Your Data Center Network for VxRail VxRail Cluster Types VxRail Feature-Driven Decision Points VxRail Hardware and Switch Selection Decision Points Prepare Data Center for VxRail Implementation Planning the VxRail Cluster Implementation
Introduction to implementation planning
Decide on VxRail single point of management
Decide on VxRail network traffic segmentation
Decide on teaming and failover policies for VxRail networks
Plan the VxRail logical network
Plan network settings for VxRail management components
Plan network settings for vCenter Server management network
Identify IP addresses for VxRail management components
Select hostnames for VxRail management components
Identify external applications and settings for VxRail
Prepare customer-managed vCenter server
Prepare customer-managed virtual distributed switch
Reserve IP addresses for VxRail vMotion network
Reserve IP addresses for VxRail vSAN network
Decide on VxRail logging solution
Assign passwords for VxRail management
Planning vSAN Witness Networking Planning VxRail Satellite Nodes Networking Configure the Network for VxRail Preparing to Build the VxRail Cluster VxRail Network Considerations After Implementation Appendixes

Decide on VxRail network traffic segmentation

Decide on VxRail network traffic segmentation

  • You have options regarding segmenting the VxRail network traffic at the virtual distributed switch level. You can configure all the required VxRail networks to a single virtual distributed switch, or you can deploy a second virtual distributed switch to isolate the VxRail management network traffic and the VxRail nonmanagement network traffic.

    DiagramDescription automatically generated

    Figure 55.    VxRail network segmentation with two virtual distributed switches

    If your company or organization has stringent security policies regarding network separation, splitting the VxRail networks between two virtual distributed switches will enable better compliance with those policies, and simplify redirecting the VxRail management network traffic and nonmanagement network traffic down separate physical network paths.

    You can choose from the following options to align with your company or organization networking policies:

    • Place all the required VxRail network traffic and guest network traffic on a single virtual distributed switch.
    • Use two virtual distributed switches to segment the VxRail management network traffic from the VxRail nonmanagement traffic and guest virtual machine network traffic.
    • Deploy a separate virtual distributed switch to support guest virtual machine network traffic.

    DiagramDescription automatically generated 

    Figure 56.    VxRail network segmentation with two virtual distributed switches

    VxRail supports either a single virtual distributed switch or two virtual distributed switches as part of the initial implementation process. If your security posture changes after the VxRail cluster initial implementation has completed, a second virtual distributed switch can still be deployed, and the VxRail network traffic can be redirected to that second virtual distributed switch. Any additional virtual distributed switches beyond two switches, such as those for user requirements outside of VxRail networking can be deployed after initial implementation.