Add Virtual SAN traffic to the list of available services and click Ok. Ensure Virtual SAN is selected under enabled services and click Next.Ĭonfigure the network settings for the VMkernel port and click Next.įor lab environments with limited physical interfaces you select the Management Network and click the Edit Settings icon. When you have finished the network adapter configuration click Next.Ĭonfigure a name for the VMkernel port and a VLAN ID if required. For production environments make sure multiple physical network adapters are assigned for redundancy. Select a New standard switch and click Next.Īssign physical adapters to the switch using the green plus symbol. Ensure the connection type is VMkernel Network Adapter and click Next. Click VMKernel Adapters and the Add Networking icon. In the vSphere client (HTML5) or vSphere web client browse to each of the hosts in the designated cluster for which you intend to use vSAN, open the Configure tab and select Networking. vSAN Portsīefore configuring vSAN each host in the cluster must be configured with a VMkernel port for use with vSAN traffic.
For full details see the licensing guide for the relevant vSAN version: vSAN 6.5 | vSAN 6.6 | vSAN 6.7. RAID 5/6 erasure coding, deduplication and compression require advanced licensing. Features such as data-at-rest encryption and stretched clusters need enterprise licensing. The current licensing model comes in three tiers standard, advanced, and enterprise, as well as standard and advanced ROBO (Remote Office/Branch Office) versions. VMware vSAN can be added to any version of vSphere and is licensed per CPU, per VM, or per concurrent user. Before implementing vSAN review Designing and Sizing a Virtual SAN Cluster.For compatibility with additional VMware products see the Product Interoperability Matrix.
This post intends to give an overview of vSAN 6.5/6.7 and how to enable it. VMware vSAN achieves high availability by adding a software layer leveraging existing server hardware to provide the same resiliency and features as expensive SAN, NAS, or DAS arrays. Further to this vSAN is uniquely embedded within the hypervisor kernel, directly in the I/O path allowing it to make rapid data placement decisions without the installation of additional VIBs or virtual appliances. VMware vSAN utilises server attached flash devices and local hard disk drives to create a shared datastore across hosts in a vSphere cluster.
For more information see the VMware Upgrade Matrix. Upgrade to vSphere 7 can be achieved directly from vSphere 6.5.0 and above, whereas vSphere 6.0 requires an intermediate upgrade to 6.5 or 6.7 first.
See also How to Install vSphere 7.0 and How to Install vSAN 7.0. VMware vSAN 6.5, 6.6, and 6.7 are all scheduled to reach end of general support 15 October 2022, referenced in the VMware Lifecycle Matrix.