Whether a decision is made to enable Layer 2 or Layer 3 connectivity upstream, VLANs for the required VxRail cluster networks must be reserved. The ‘VxRail Required Network VLANs’ table in the Settings’ in Appendix B: VxRail cluster network configuration tables lists the VxRail networks required when performing initial build.
- It is best practice to use a VLAN entered for the VxRail External Management Network that is different than the VLAN representing the virtual network for the Client Management Network. This will allow for additional VxRail clusters to be deployed on the switch fabric and preserve the virtual network assigned to the client management network for its intended purpose of access to discovered nodes and client onboarding. This VLAN captured in VxRail Manager during initial build will be configured as a tagged virtual network on the switch fabric.
- The default VLAN for the VxRail Internal Management Network (3939) is configured into each VxRail node in the factory to standardize the network ID used for node and switch discovery. This VLAN must match the value representing the virtual network for the Client Control Network configured into the SmartFabric-based network. If a new VLAN ID is used for the VxRail Internal Management Network, then the value for the Client Control Network must be changed to match this VLAN. In addition, this VLAN must be changed on each VxRail node to run in the switch fabric to enable discovery. This can only be done through the ESXi console on a powered-on VxRail node.