VPLEX: El testigo de clúster muestra un estado de administrador incoherente

Implemente y configure el servidor de Cluster Witness.

Cluster Witness muestra un estado de administrador "incoherente" en su contexto de CLI de VPLEX después de implementar correctamente la VM del servidor y configurarla en la CLI según el procedimiento oficial de SolVe Desktop correspondiente (según la versión de código de GeoSynchrony instalada):
 

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

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

El estado de administrador incoherente significa que todos los componentes son accesibles a través de la red de administración, pero algunos componentes informan su estado administrativo como deshabilitado , mientras que otros informan que está habilitado.

Este es un estado extremadamente raro.
 

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 <<<<

En este caso, dado que el componente deshabilitado que causaba que el estado del administrador fuera "incoherente" era el propio servidor del testigo de clúster, habilitarlo con el comando "cluster-witness enable" resolvió el problema y el estado del administrador cambió a "habilitado":
 

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

En algunos casos poco frecuentes, es posible que el estado de administrador se muestre como "incoherente", a pesar de que el estado de la VPN muestre un estado correcto y no pueda habilitar el testigo del clúster debido a que no se muestra el contexto /cluster-witness/ en uno de sus clústeres.

CLI DE VPLEX DEL CLÚSTER 1:

VPlexcli:/> ll /cluster-witness/components/

/cluster-witness/components:
Name       ID  Admin State  Operational State  Mgmt Connectivity
---------  --  -----------  -----------------  -----------------
cluster-1  1   disabled     -                  ok
cluster-2  2   disabled     -                  ok
server     -   enabled      unknown            ok

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

VPlexcli:/> cluster-witness enable
cluster-witness enable:  Evaluation of <<cluster-witness enable>> failed.
cause:                   Could not enable Cluster Witness.
cause:                   Cluster Witness cannot be enabled due to failure of a pre-check.
cause:                   Cluster Witness is not configured on cluster-2

CLI DE VPLEX DEL CLÚSTER 2:

VPlexcli:/> ll /cluster-witness/

ls:  No context found for '/cluster-witness/'

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

VPlexcli:/> cluster-witness enable
<unknown command>:  Evaluation of <<cluster-witness enable>> failed.
cause:              Property 'cluster-witness' is not supported.

Para resolver el problema de un clúster que no tiene un contexto de testigo de clúster, ejecutará el comando cluster-witness configure que debe crear el contexto si aún no existe uno. Después, debería poder habilitar el testigo de clúster en el clúster de manera normal.

Compruebe si existe el contexto Cluster-Witness

VPlexcli:/> ll
Name                 Description
-------------------  ----------------------------------------------------------
clusters             Contains all the clusters that are currently connected, or
                     have been connected during the current session.
data-migrations      Contains extent migrations and device-migrations.
distributed-storage  Contains distributed devices and WAN outage rule sets.
engines              Contains all the engines that are currently connected.
management-server    Contains the management server for the local cluster
monitoring           Contains system performance monitors.
notifications        Contains the call-home event-filter and its sinks.
recoverpoint         Contains RecoverPoint components within this system.
system-defaults      System-wide default values and settings.

Si no ve el contexto Cluster-Witness en la lista, ejecute el comando,VPlexcli

:/>cluster-witness configure

A continuación, repita el paso 1 para ver si Cluster-Witness aparece ahora en la lista

VPlexcli:/> ll
Name                 Description
-------------------  ----------------------------------------------------------
cluster-witness      Contains the Cluster Witness connected to all clusters <<<<
                     within this system.
clusters             Contains all the clusters that are currently connected, or
                     have been connected during the current session.
data-migrations      Contains extent migrations and device-migrations.
distributed-storage  Contains distributed devices and WAN outage rule sets.
engines              Contains all the engines that are currently connected.
management-server    Contains the management server for the local cluster
monitoring           Contains system performance monitors.
notifications        Contains the call-home event-filter and its sinks.
recoverpoint         Contains RecoverPoint components within this system.
system-defaults      System-wide default values and settings.

A continuación, compruebe si cluster-witness se muestra como habilitado mediante la ejecución del comando:

VPlexcli:/>ll /cluster-witness/

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

Contexts:
Name        Description
----------  --------------------------
components  Cluster Witness Components

Si el estado del administrador se muestra como "deshabilitado", habilítelo mediante el siguiente

comando VPlexcli:/>cluster-witness enable

Una vez que el estado del administrador se muestre como "habilitado", compruebe los componentes del testigo de clúster para asegurarse de que todos se muestren como "habilitados", como se muestra a continuación.

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     -   enabled      clusters-in-contact  ok

Si el estado del administrador sigue siendo "incoherente" después de comprobar el estado del testigo del clúster o después de ejecutar el comando de habilitación, póngase en contacto con el servicio de soporte al cliente de VPLEX.