This witness vRops VM acts as a tie-breaker or a quorum disk to maintain the metadata between members participating in the fault domain. This concept of a quorum is very similar to the IBM SVC Storage SAN Controller quorum- topology. The witness node is only required if we wish to enable Continuous Availability in vRops which we will cover in the next chapter.
Prerequisites
- You should have a working master and a data mode before you deploy w
- Read vRealize Operations Sizing Guidelines
- Ensure that you have read the vROps Sizing Guide prior to expanding your vRops cluster. Input all your existing vCenter environment into this one and also ensure the projected growth is as well accounted for.
We will download the same OVA version we have on the master and data nodes and deploy the OVA as usual. During the deployment, we will just need to pick the size of the deployment and ignore the below configuration chart.
Deploying a witness node to the vRops cluster
Open https://fqdn of the second node in the browser and select expand an existing installation.
Click Next to continue
First, we will add the second node as a data node, and once successful will get the option to enable HA and configure replica.
Provide the following info
- Node name – vrops-2.ash.local
- Node type – witness
- Under the cluster information, provide the master vRops node IP and Click validate
Here we will provide the admin password for our first node or master node
Click Finish
The cluster expansion process with take some time
Click Finish adding the new witness node
Click OK and proceed
All our nodes and running and our cluster is healthy.
