VPLEX: NDU-Vorabprüfungsfehler auf den VPLEX-Clustern nach dem Codeupgrade
Zusammenfassung: Der Zweck dieses Artikels besteht darin, die Vorabprüfungsfehler des unterbrechungsfreien Upgrades (NDU) zu beseitigen, die nach dem Codeupgrade auf den VPLEX-Clustern angezeigt werden. ...
Dieser Artikel gilt für
Dieser Artikel gilt nicht für
Dieser Artikel ist nicht an ein bestimmtes Produkt gebunden.
In diesem Artikel werden nicht alle Produktversionen aufgeführt.
Symptome
Nach dem Upgrade des GeoSynchrony-Codes auf 6.1 wird Folgendes ausgeführt:
Beispiel:
ndu pre-check Befehl auf VPlexcli von einem der VPLEX-Cluster gibt Fehler zurück. Es werden keine Fehler gefunden, wenn die NDU-Vorabprüfung vom anderen Cluster ausgeführt wird.
Beispiel:
Von Cluster-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
Ursache
Nach dem Upgrade auf GeoSynchrony 6.1 fehlen möglicherweise Details in der Konfigurationsdatei auf dem Verwaltungsserver, weshalb das entsprechende Cluster Fehler in der Ausgabe der NDU-Vorabprüfung zurückgibt.
Lösung
Schritt 1: Melden Sie sich bei
Beispiel:
Von Cluster-2:
Schritt 3: Die beiden obigen Schritte bestätigen, dass das Problem nur auf Cluster-1 auftritt. Schließen Sie beide PuTTY-Sitzungen.
Schritt 4: Starten Sie eine neue PuTTY-Sitzung auf dem Managementserver von Cluster-1 mit dem Servicekonto und starten Sie die Managementserverdienste vom neuesten
Schritt 7: Stellen Sie eine Verbindung zum Cluster-1-Managementserver her und melden Sie sich an bei
Beispiel:
Von Cluster-1:
VPlexcli vom Cluster-1-Managementserver und Ausgabe ndu pre-check . Die folgenden Fehler werden während der NDU-Vorabprüfung angezeigt.
Beispiel:
Von Cluster-1:
Schritt 2: Melden Sie sich bei 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 Vom Cluster-2-Managementserver und Ausgabe ndu pre-check. Beachten Sie, dass keine Fehler angezeigt werden, wenn die NDU-Vorabprüfung von Cluster-2 ausgegeben wird.
Beispiel:
Von Cluster-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
Schritt 4: Starten Sie eine neue PuTTY-Sitzung auf dem Managementserver von Cluster-1 mit dem Servicekonto und starten Sie die Managementserverdienste vom neuesten
mgmtServerBackup.tar zu verwenden.
service@<cluster-1> sudo /opt/emc/VPlex/bin/VPlex-MS-backup --restart-services --restore /tmp/mgmtServerBackup-<SERIAL-NUMBER>.tar
Ignorieren Sie alle Fehler, die angezeigt werden.
Wenn die
Schritt 5: Starten Sie den Managementserver mit dem folgenden Befehl neu.
mgmtServerBackup-<SERIAL_NUMBER>.tar Datei nicht im Ordner /tmp des Managementservers von VPLEX vorhanden ist, kann sie vom Director abgerufen werden, indem Sie Artikel 119212 befolgen. Stellen Sie sicher, dass die mgmtServerBackup.tar Die Datei wird im Ordner /tmp des Managementservers abgelegt.
service@<cluster-1> sudo /sbin/rebootSchritt 6: Der Managementserver wird neu gestartet, es kann jedoch 5 bis 10 Minuten dauern, bis der Vorgang fortgesetzt wird.
Schritt 7: Stellen Sie eine Verbindung zum Cluster-1-Managementserver her und melden Sie sich an bei
VPlexcli. Problem ndu pre-check , um zu bestätigen, dass die Fehler nicht mehr vorhanden sind.
Beispiel:
Von Cluster-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
Betroffene Produkte
VPLEX Series, VPLEX VS2, VPLEX VS6Artikeleigenschaften
Artikelnummer: 000168180
Artikeltyp: Solution
Zuletzt geändert: 05 Mai 2026
Version: 4
Antworten auf Ihre Fragen erhalten Sie von anderen Dell NutzerInnen
Support Services
Prüfen Sie, ob Ihr Gerät durch Support Services abgedeckt ist.