VPLEX: Se observaron errores de comprobación previa de NDU en los clústeres de VPLEX después de la actualización de código
Resumen: El propósito de este artículo es borrar los errores de comprobación previa de la actualización no disruptiva (NDU) que aparecen en los clústeres de VPLEX después de la actualización del código. ...
Este artículo se aplica a
Este artículo no se aplica a
Este artículo no está vinculado a ningún producto específico.
No se identifican todas las versiones del producto en este artículo.
Síntomas
Después de la actualización del código de GeoSynchrony a 6.1, ejecute
Ejemplo:
ndu pre-check Comando activado VPlexcli de uno de los clústeres de VPLEX arroja errores. No se encuentran errores cuando la comprobación previa de NDU se ejecuta desde el otro clúster.
Ejemplo:
Desde el clúster 1:
service@<cluster-1>:~> vplexcli Trying ::1... Connected to localhost. Escape character is '^]'. VPlexcli:/> ndu pre-check Warning: During the NDU process, multiple directors will be offline for a portion of the time. This is non-disruptive but is dependent on a host-based multipathing solution being installed, configured, and operating on all connected hosts. Warning: Please run the "health-check --full" command to verify that the VPLEX is healthy. Analyzing system configuration: .DONE ================================================================================ Performing NDU pre-checks ================================================================================ Verify NDU is not in progress.. ERROR Verify that AIX initiators are configured in VPLEX.. OK Verify director communication status.. OK Verify management network redundancy.. OK Verify management network latency.. ERROR Verify time drift between directors and management server ERROR Verify firmware software version can be retrieved ERROR Verify sufficient disk space on the management server ERROR Verify sufficient disk space on directors ERROR Verify director SSD health ERROR Verify bios quiet mode enabled on the directors ERROR Verify sps conditioning status.. ERROR Verify intra-cluster communications connectivity.. OK Verify inter-director management connectivity status.. OK Verify directors have been commissioned.. OK Verify no unreachable or dead storage-volumes.. OK Verify no unhealthy virtual-volumes.. OK Verify distributed device settings.. OK Verify no unhealthy storage views.. OK Verify valid system configuration.. OK Verify valid metadata volume.. ERROR Verify metadata volume redundancy.. OK Verify all local-com ports have correct topologies.. OK Verify cluster status.. ERROR Verify and prepare directors for ndu.. ERROR Verify the response time of front-end switches.. OK Verify the response time of back-end switches.. OK Verify for potential slow I/O in the last 30 seconds.. ERROR Verify meta-volume backup configuration.. ERROR Verify metadata volume slot availability.. OK Verify RecoverPoint cluster registrations.. OK Verify no virtual volume expansion.. OK Verify if array aware operations are in progress.. ERROR Verify all back-end connections comply with LUN count restriction.. OK Verify inter-cluster communications connectivity.. OK Verify the remote management server version.. ERROR Verify cache-mode consistency for distributed virtual-volumes.. OK Verify clusters are joined.. OK Verify cluster witness state.. ERROR Verify sufficient disk space on the cluster witness server.. ERROR Verify there is no recent I/O aborts.. ERROR
Causa
Después de actualizar a GeoSynchrony 6.1, es posible que falten detalles en el archivo de configuración en el servidor de administración, por lo cual el clúster correspondiente devuelve errores en la salida de la comprobación previa de NDU.
Resolución
Paso 1: Inicie sesión en
Ejemplo:
Desde el clúster 2:
Paso 3: Los dos pasos anteriores confirman que el problema se observa solo en el clúster 1. Cierre ambas sesiones de PuTTY.
Paso 4: Inicie una nueva sesión de PuTTY en el servidor de administración del clúster 1 con una cuenta de servicio y reinicie los servicios del servidor de administración desde la versión más reciente
Paso 7: Conéctese al servidor de administración del clúster 1 e inicie sesión en
Ejemplo:
Desde el clúster 1:
VPlexcli desde el servidor de administración del clúster 1 y el problema ndu pre-check comando. Los siguientes errores se observan durante la comprobación previa de NDU.
Ejemplo:
Desde el clúster 1:
Paso 2: Inicie sesión en service@<cluster-1>:~> vplexcli Trying ::1... Connected to localhost. Escape character is '^]'. VPlexcli:/> ndu pre-check Warning: During the NDU process, multiple directors will be offline for a portion of the time. This is non-disruptive but is dependent on a host-based multipathing solution being installed, configured, and operating on all connected hosts. Warning: Please run the "health-check --full" command to verify that the VPLEX is healthy. Analyzing system configuration: .DONE ================================================================================ Performing NDU pre-checks ================================================================================ Verify NDU is not in progress.. ERROR Verify that AIX initiators are configured in VPLEX.. OK Verify director communication status.. OK Verify management network redundancy.. OK Verify management network latency.. ERROR Verify time drift between directors and management server ERROR Verify firmware software version can be retrieved ERROR Verify sufficient disk space on the management server ERROR Verify sufficient disk space on directors ERROR Verify director SSD health ERROR Verify bios quiet mode enabled on the directors ERROR Verify sps conditioning status.. ERROR Verify intra-cluster communications connectivity.. OK Verify inter-director management connectivity status.. OK Verify directors have been commissioned.. OK Verify no unreachable or dead storage-volumes.. OK Verify no unhealthy virtual-volumes.. OK Verify distributed device settings.. OK Verify no unhealthy storage views.. OK Verify valid system configuration.. OK Verify valid metadata volume.. ERROR Verify metadata volume redundancy.. OK Verify all local-com ports have correct topologies.. OK Verify cluster status.. ERROR Verify and prepare directors for ndu.. ERROR Verify the response time of front-end switches.. OK Verify the response time of back-end switches.. OK Verify for potential slow I/O in the last 30 seconds.. ERROR Verify meta-volume backup configuration.. ERROR Verify metadata volume slot availability.. OK Verify RecoverPoint cluster registrations.. OK Verify no virtual volume expansion.. OK Verify if array aware operations are in progress.. ERROR Verify all back-end connections comply with LUN count restriction.. OK Verify inter-cluster communications connectivity.. OK Verify the remote management server version.. ERROR Verify cache-mode consistency for distributed virtual-volumes.. OK Verify clusters are joined.. OK Verify cluster witness state.. ERROR Verify sufficient disk space on the cluster witness server.. ERROR Verify there is no recent I/O aborts.. ERROR
VPlexcli desde el servidor de administración del clúster 2 y el problema ndu pre-check. Observe que no se observan errores cuando la comprobación previa de NDU se emite desde el clúster 2.
Ejemplo:
Desde el clúster 2:
service@<cluster-2>:~> vplexcli Trying ::1... Connected to localhost. Escape character is '^]'. VPlexcli:/> ndu pre-check Warning: During the NDU process, multiple directors will be offline for a portion of the time. This is non-disruptive but is dependent on a host-based multipathing solution being installed, configured, and operating on all connected hosts. Warning: Please run the "health-check --full" command to verify that the VPLEX is healthy Analyzing system configuration: .DONE ================================================================================ Performing NDU pre-checks ================================================================================ Verify NDU is not in progress.. OK Verify that AIX initiators are configured in VPLEX.. OK Verify director communication status.. OK Verify management network redundancy.. OK Verify management network latency.. OK Verify time drift between directors and management server.. OK Verify firmware software version can be retrieved.. OK Verify sufficient disk space on the management server.. OK Verify sufficient disk space on directors.. OK Verify director SSD health.. OK Verify bios quiet mode enabled on the directors.. OK Verify sps conditioning status.. OK Verify intra-cluster communications connectivity.. OK Verify inter-director management connectivity status.. OK Verify directors have been commissioned.. OK Verify no unreachable or dead storage-volumes.. OK Verify no unhealthy virtual-volumes.. OK Verify distributed device settings.. OK Verify no unhealthy storage views.. OK Verify valid system configuration.. OK Verify valid metadata volume.. OK Verify metadata volume redundancy.. OK Verify all local-com ports have correct topologies.. OK Verify cluster status.. OK Verify and prepare directors for ndu.. OK Verify the response time of front-end switches.. OK Verify the response time of back-end switches.. OK Verify for potential slow I/O in the last 30 seconds.. OK Verify meta-volume backup configuration.. OK Verify metadata volume slot availability.. OK Verify RecoverPoint cluster registrations.. OK Verify no virtual volume expansion.. OK Verify if array aware operations are in progress.. OK Verify all back-end connections comply with LUN count restriction.. OK Verify inter-cluster communications connectivity.. OK Verify the remote management server version.. OK Verify cache-mode consistency for distributed virtual-volumes.. OK Verify clusters are joined.. OK Verify cluster witness state.. OK Verify sufficient disk space on the cluster witness server.. OK Verify there is no recent I/O aborts.. OK
Paso 4: Inicie una nueva sesión de PuTTY en el servidor de administración del clúster 1 con una cuenta de servicio y reinicie los servicios del servidor de administración desde la versión más reciente
mgmtServerBackup.tar de NetWorker.
service@<cluster-1> sudo /opt/emc/VPlex/bin/VPlex-MS-backup --restart-services --restore /tmp/mgmtServerBackup-<SERIAL-NUMBER>.tar
Ignore cualquier error que aparezca.
Si la solicitud en
Paso 5: Reinicie el servidor de administración mediante el comando que se muestra a continuación.
mgmtServerBackup-<SERIAL_NUMBER>.tar El archivo no está presente en la carpeta /tmp del servidor de administración de VPLEX; se puede obtener del director siguiendo el artículo 119212. Asegúrese de que el mgmtServerBackup.tar se coloca en la carpeta /tmp del servidor de administración.
service@<cluster-1> sudo /sbin/rebootPaso 6: El servidor de administración se reinicia, pero espere de 5 a 10 minutos antes de continuar.
Paso 7: Conéctese al servidor de administración del clúster 1 e inicie sesión en
VPlexcli. Problema ndu pre-check De nuevo para confirmar que los errores ya no están presentes.
Ejemplo:
Desde el clúster 1:
service@<cluster-1>:~> vplexcli Trying ::1... Connected to localhost. Escape character is '^]'. VPlexcli:/> ndu pre-check Warning: During the NDU process, multiple directors will be offline for a portion of the time. This is non-disruptive but is dependent on a host-based multipathing solution being installed, configured, and operating on all connected hosts. Warning: Please run the "health-check --full" command to verify that the VPLEX is healthy. Analyzing system configuration: .DONE ================================================================================ Performing NDU pre-checks ================================================================================ Verify NDU is not in progress.. OK Verify that AIX initiators are configured in VPLEX.. OK Verify director communication status.. OK Verify management network redundancy.. OK Verify management network latency.. OK Verify time drift between directors and management server.. OK Verify firmware software version can be retrieved.. OK Verify sufficient disk space on the management server.. OK Verify sufficient disk space on directors.. OK Verify director SSD health.. OK Verify bios quiet mode enabled on the directors.. OK Verify sps conditioning status.. OK Verify intra-cluster communications connectivity.. OK Verify inter-director management connectivity status.. OK Verify directors have been commissioned.. OK Verify no unreachable or dead storage-volumes.. OK Verify no unhealthy virtual-volumes.. OK Verify distributed device settings.. OK Verify no unhealthy storage views.. OK Verify valid system configuration.. OK Verify valid metadata volume.. OK Verify metadata volume redundancy.. OK Verify all local-com ports have correct topologies.. OK Verify cluster status.. OK Verify and prepare directors for ndu.. OK Verify the response time of front-end switches.. OK Verify the response time of back-end switches.. OK Verify for potential slow I/O in the last 30 seconds.. OK Verify meta-volume backup configuration.. OK Verify metadata volume slot availability.. OK Verify RecoverPoint cluster registrations.. OK Verify no virtual volume expansion.. OK Verify if array aware operations are in progress.. OK Verify all back-end connections comply with LUN count restriction.. OK Verify inter-cluster communications connectivity.. OK Verify the remote management server version.. OK Verify cache-mode consistency for distributed virtual-volumes.. OK Verify clusters are joined.. OK Verify cluster witness state.. OK Verify sufficient disk space on the cluster witness server.. OK Verify there is no recent I/O aborts.. OK
Productos afectados
VPLEX Series, VPLEX VS2, VPLEX VS6Propiedades del artículo
Número del artículo: 000168180
Tipo de artículo: Solution
Última modificación: 05 may 2026
Versión: 4
Encuentre respuestas a sus preguntas de otros usuarios de Dell
Servicios de soporte
Compruebe si el dispositivo está cubierto por los servicios de soporte.