After upgrading all of your ESXi hosts to v7.0, it is time to either upgrade or deploy a new witness appliance and introduce it to the cluster. Upgrading witness appliance is done the same way as every other ESXi host, but since that procedure can initiate a known bug where witness appliance loses embedded witness appliance license and switches to evaluation license, you might end up deploying a new appliance anyway.
First you need to download the latest vSAN Witness Appliance OVF template from VMware website. Since the development of the new witness appliance is apparently not entirely finished, please do not configure anything else than required root password. Configuring any other options will leave you with an appliance without vSAN traffic switch that cannot communicate on the vSAN witness network and you will not be able to repair it. Manually adding second switch and configuring vmk1 will not resolve the issue.
Here is the sum-up of the correct steps to deploy new witness appliance.
- Download VMware vSAN Witness Appliance OVF
- Log in into your VCSA
- Right click on the vSAN cluster and select Deploy OVF Template
- Select Local File, click Browse and select OVF file downloaded in step 1 and click Next
- Type in vSAN Witness Host VM name and select the folder where to store you VM
- Select a compute ressource for your VM. Note that cross-cluster deployments are not supported. Running stretched cluster requires quorum site.
- Accept EULA
- Select deployment size according to your environment. Selecting larger deployment size than necessary does not give any performance improvement.
- Select storage and storage policy
- Select networks (VLANs) for both management and witness traffic.
- Under customise template configure ONLY root password! Leave all other fields empty!
- Deploy template
- Log in to your witness host via DCUI
- Configure management network and test it. Make sure that you can ping gateway, DNS server(s) and that you can resolve hostname.
- Add witness appliance as a standalone ESXi host to your VCSA. Note that witness host cannot be placed in the any clusters, but it must be within your datacenter in the VCSA hierarchy.
- Configure Witness ESXi switch (secondarySwitch) MTU to 9000
- Configure Witness ESXi witness traffic vmk port (vmk1) either with the static or DHCP IP address.
- Enable SSH (Configure – Services – SSH – Start)
- Log in into your vSAN Witness Appliance via SSH
- Add static route for witness network
# esxcli network ip route ipv4 add --gateway x.x.x.x --network x.x.x.x/xx
- Confirm that you can ping vSAN witness traffic interface from your ESXi hosts.
Note that running vSAN Witness Appliance in stretched L2 subnet is not supported. Quorum site must be accessed via L3 network.