Symptoms

Deploy and configure Cluster Witness server.Cluster Witness displays "inconsistent" admin-state on its VPLEX CLI context after successfully deploying the server VM and configuring it in the CLI as per the applicable official SolVe Desktop procedure (depending on the installed GeoSynchrony code version): VPlexcli:/> ll cluster-witness/ /cluster-witness: Attributes: Name Value ------------------ ------------- admin-state inconsistent private-ip-address 128.221.254.3 public-ip-address X.X.X.X Cluster Witness displays as "reachable" on VPN status. It seems to be properly configured and healthy: VPlexcli:/> vpn status Verifying the VPN status between the management servers... IPSEC is UP Remote Management Server at IP Address X.X.X.X is reachable Remote Internal Gateway addresses are reachable Verifying the VPN status between the management server and the cluster witness server... IPSEC is UP Cluster Witness Server at IP Address 128.221.254.3 is reachable

Cause

Inconsistent admin-state means all components are reachable over the management network but some components report their administrative state as disabled while others report it as enabled.This is an extremely rare state. VPlexcli:/> ll cluster-witness/components/ /cluster-witness/components: Name ID Admin State Operational State Mgmt Connectivity --------- -- ----------- ----------------- ----------------- cluster-1 1 enabled in-contact ok cluster-2 2 enabled in-contact ok server - disabled - ok <<<<

Resolution

In this case, since the disabled component causing the admin-state to be "inconsistent" was the Cluster Witness server itself, enabling it with the "cluster-witness enable" command cleared the issue and the admin-state changed to "enabled": VPlexcli:/> cluster-witness enable VPlexcli:/> ll cluster-witness/ /cluster-witness: Attributes: Name Value ------------------ ------------- admin-state enabled private-ip-address 128.221.254.3 public-ip-address X.X.X.X

Support Cases