To use the Service Witness Protocol, you need to create and configure a witness EVS to monitor a service EVS.
- A valid CIFS license is required. Review your licensed EVS count before making changes.
- The server to which the Witness protocol applies must be in a clustered environment of more than one cluster node.
- The service EVS must be running version 3 of the CIFS protocol. To set the version, use the cifs-max-supported-version 3 command.
- Windows clients must be joined to the domain.
Note: You can use only CLI commands to configure and manage a witness EVS. For more information about the CLI commands, and for more CLI options for the Service Witness Protocol, see the Command Line Reference.
-
Set up a share on the service EVS that you want the witness EVS to monitor.
-
Create a witness EVS for the service EVS that contains the share by using the following command:
evs create [-l <label>] -i [<ipaddr/prefix> | <ipaddr> -m <mask>] -p <port> [-n <dst-nodeid>][-w <witness-for>]
For example, a witness EVS on cluster node 2 for a service EVS on cluster node 1 would be:
evs create -l WITNESSEVS01 -i 192.0.2.1/24 -p ag1 n 2 -w EVS01
The witness EVS is created and bound to the service EVS.
-
Configure an ADS CIFS name for the witness EVS:
-
Put the witness EVS in context.
-
Add an ADS CIFS name by using the following command:
cifs-name add -m ads -a <dc ipaddr> <my-ads-name>
-
Enter your user name and password.
-
Map the continuously available share in Windows 8, 8.1, Server 2012, or Server 2012 R2.
Note: When mapping the share, use a fully qualified domain name (FQDN) instead of the IP address of the service node.
-
To verify that the client is registered to the witness EVS, use the following command:
witness-registration-list-show