Ausführen des Hyperflex Health and Pre-Upgrade Check-Tools

Einleitung

In diesem Dokument wird der Prozess zum Ausführen des Hypercheck-Tools für Integrität und vor dem Upgrade beschrieben.

Voraussetzungen

Anforderungen

Cisco empfiehlt, dass Sie über Kenntnisse in diesem Thema verfügen:

• Hyperflex

Verwendete Komponenten

Die Informationen in diesem Dokument basieren auf dem Hypercheck-Integritäts- und Vorabupgradetool.

Die Informationen in diesem Dokument beziehen sich auf Geräte in einer speziell eingerichteten Testumgebung. Alle Geräte, die in diesem Dokument benutzt wurden, begannen mit einer gelöschten (Nichterfüllungs) Konfiguration. Wenn Ihr Netzwerk in Betrieb ist, stellen Sie sicher, dass Sie die möglichen Auswirkungen aller Befehle kennen.

Hintergrundinformationen

Dieses Tool ist ein Dienstprogramm, das proaktive Selbstprüfungen auf Hyperflex-Systemen durchführt, um deren Stabilität und Ausfallsicherheit zu gewährleisten. Es ermöglicht die Automatisierung einer Liste von Integritäts- und Vorab-Upgrades der Hyperflex-Systeme, um Zeit bei Upgrades und Wartungsarbeiten zu sparen.

Hinweis: Laden Sie vor der Verwendung immer die neueste Version des Tools herunter. Da das Tool häufig verbessert wird, kann die Verwendung einer früheren Version dazu führen, dass wichtige Prüfungen fehlen.

Unterstützte HX-Systeme

• Hyperflex-Versionen - 1.8, 2.0, 2.1, 2.5, 2.6, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5
• HyperFlex Standard-Cluster
• Hyperflex-Stretch-Cluster
• Hyperflex Edge-Cluster (2 Knoten, 3 Knoten und 4 Knoten)
• Nur auf Hyperflex-Cluster auf VMWare ESXi unterstützt

Hinweis: Informationen zum Ausführen von Hypercheck auf dem Hyperflex HyperV-Cluster finden Sie unter Hypercheck: Hyperflex Health & Pre-Upgrade Check Tool - HyperV.

Verwendungszweck

Die effektiven Zeiten für die Verwendung des Hyperflex Health and Pre-Upgrade Check Tools sind:

• Vor Hyperflex-Upgrades
• Hyperflex Health Check vor und nach Wartungsfenstern
• Zur Identifizierung ausgefallener Laufwerke/Festplatten
• Zusammenarbeit mit dem Cisco TAC
• Proaktive Statusprüfung jederzeit

Nutzung

HX-Version 4.5 und höher

Schritt 1: Initiieren Sie eine SSH-Verbindung zum Storage Controller VM (SCVM) mithilfe der Cluster Management-IP (CMIP), der HX-Connect-IP.

Schritt 2: Führen Sie den Befehl hypercheck aus.

admin:~$ hypercheck

Schritt 3: Geben Sie auf Aufforderung das SCVM-Admin-Kennwort ein, und geben Sie das Root-Kennwort des ESXi ein.

admin:~$ hypercheck

                  HX Health Check 4.5.0

Please enter below info of HX-Cluster:
Enter the HX-Cluster Root Password:
Enter the HX-Cluster Admin Password:
Enter the ESX Root Password:

HX Version 4.0 und frühere Version

Schritt 1: Laden Sie die DateiHyperflex-Hypercheck.zip vom Cisco github devnet-Konto herunter. Holen Sie sich das neueste Exemplar mit den neuesten Verbesserungen und Updates.

Hinweis: Nur registrierte Cisco Benutzer können auf interne Tools, Dateien und Informationen von Cisco zugreifen.

Hinweis: Verwenden Sie nur das Skript, das Sie vom Cisco github-Konto heruntergeladen haben.

Schritt 2: Laden Sie es mit dem CMIP in das SCVM hoch.

Verwenden Sie Ihre bevorzugte Methode - scp/sftp/ftp/tftp - Um die Hyperflex-Hypercheck.zip in das /tmp Verzeichnis kopieren.

Für MAC:

SCP über die CLI durchführen (vergewissern Sie sich, dass sich dasHyperflex-Hypercheck.zip im selben Ordner befindet, von dem aus Sie SCP ausführen).

# scp Hyperflex-Hypercheck.zip root@<scvm-eth0:mgmtip>:/tmp/.

Verwenden Sie diese Option, um die Cluster Management-IP in Ihrer HX-Umgebung zu identifizieren - Hyperflex-Leitfaden.

Für Windows:

Sie können die Dateien wie folgt übertragen verwendenWINSCP:

Schritt 3: Extrahieren Sie den Inhalt von Hyperflex-Hypercheck.zip.

Geben Sie cd /tmp ein, um zum /tmp Verzeichnis zu wechseln.



root@SpringpathController7PVQWP6WV1:~# cd /tmp/


Geben Sie unzip Hyperflex-Hypercheck.zip ein, um die Dateien zu extrahieren.



root@SpringpathController7PVQWP6WV1:/tmp# unzip Hyperflex-Hypercheck.zip 
Archive:  Hyperflex-Hypercheck.zip
b61c59f7962b72902692ce70548ba3d760efdf06
   creating: Hyperflex-Hypercheck/
  inflating: Hyperflex-Hypercheck/HXTool.py 
  inflating: Hyperflex-Hypercheck/LICENSE.txt 
  inflating: Hyperflex-Hypercheck/ReadMe.txt 
  inflating: Hyperflex-Hypercheck/TestInfo.txt 
  inflating: Hyperflex-Hypercheck/prettytable.py 
  inflating: Hyperflex-Hypercheck/progressbar.py 
root@SpringpathController7PVQWP6WV1:/tmp# 


Schritt 4: Führen Sie das HXTool Python-Skript aus.

Geben Sie cd Hyperflex-Hypercheck ein, um zum Hyperflex-Hypercheck Verzeichnis zu navigieren.



root@SpringpathControllerABCDE01234:/tmp# cd Hyperflex-Hypercheck


Geben Sie python HXTool.py  ein, um das Skript auszuführen.



root@SpringpathControllerABCDE01234:/tmp/Hyperflex-Hypercheck# python HXTool.py


Schritt 5: Geben Sie auf Aufforderung das SCVM-Root-Kennwort ein.



Enter this information of HX-Cluster:
Enter the HX-Cluster Root Password:
Enter the ESX Root Password:

Hinweis: Um die Skriptausführung zu stoppen, drücken Sie die Taste (STRG+Z) und die Ausführung wird sofort beendet.

Schritt 6: Hyperflex-Hypercheck-Tool startet seine Prüfungen. Die Ausführung dauert etwa 3-10 Minuten, je nach Anzahl der konvergenten Knoten im Cluster.

Schritt 7. Rufen Sie einen Bericht der Skriptausgaben ab. Sie können es wie gezeigt erhalten:

Die Hypercheck Report tar Datei wird unter /var/log/springpath  und /tmp/Hyperflex-Hypercheck gespeichert. Sie können das TAR-Paket also von unter /var/log/springpath oder /tmp/Hyperflex-Hypercheck herunterladen. Alternativ können Sie einfach ein storfs-support-Paket generieren und hochladen, das auch den Hypercheck-Bericht tar enthält.

Beispiel für eine Bericht-TAR-Datei - HX_Report_2020_08_30_10_43_50.tar wird in den Pfad kopiert: /var/log/springpath.

Geben Sie ls -l | grep HX_Report ein, um die vom Hyperflex-Hypercheck-Tool erstellten Dateien zu überprüfen.



Under /var/log/springpath,

root@SpringpathControllerABCDE01234:/var/log/springpath# ls -l | grep HX_Report
-rw-r--r-- 1 root root 380K Sep 23 15:41 HX_Report_2020_08_30_10_43_50.tar
root@SpringpathControllerABCDE01234:/var/log/springpath#

Under /tmp/Hyperflex-Hypercheck,

root@SpringpathControllerABCDE01234:/tmp/Hyperflex-Hypercheck# ls
HX_Report_2020_08_30_10_43_50.tar prettytable.py HX_Report_2020_08_30_10_43_50 TestInfo.txt progressbar.py
HXTool.py prettytable.pyc ReadMe.txt progressbar.pyc LICENSE.txt
root@SpringpathControllerABCDE01234:/tmp/Hyperflex-Hypercheck# 


Dateien und Protokolle im Hypercheck-Protokollpaket:



root@SpringpathControllerABCDE01234:/tmp/Hyperflex-Hypercheck# ls HX_Report_2020_08_30_10_43_50/
HX_Tool_2020-08-30_10-43-50.log 
HX_Tool_Main_Report_2020-08-30_10-54-34.txt 
HX_Tool_Summary.json


Schritt 8: Exportieren und mit demHX_YYYY_MM_DD_HH_MM_SS.tar TAC teilen

scp/sftp/ftp/tftp Verwenden Sie Ihre bevorzugte Methode, um die Hypercheck-Protokolle mit der Verwendung von aus dem SCVM zu exportieren, oder Sie können einfach das storfs-support-Paket herunterladen, das das TAR-Paket HX_Report enthält.

Ermitteln der Ausgaben/Überprüfungen

Von Hypercheck durchgeführte Prüfungen

Diese Prüfungen werden vom Hyperflex-Hypercheck-Tool durchgeführt:



Hyperflex Checks: (Below checks are performed on all the storage controller VMs)
  Cluster services check - Verifies the status of storfs, stMgr and stNodeMgr services
    Enospc state check - Checks if the cluster space usage is above the warning threshold or no   
    Zookeeper check - Checks whether the Zookeeper is running or no
    Exhibitor check - Verfies the status of the Exhibitor service which manages the ZK
 System Disks Usage - Checks if /sda1, var/stv and /var/zookeeper is less than 80% 
    HDD health check - Reports if you have any blacklisted disk in your cluster      
    DNS check - Checks whether DNS is configured and reachable                
    vCenter reachability check - Checks whether the vCenter is reachable on the required ports
    Timestamp check - Checks if all the controller VMs have the exact same time           
    NTP sync check - Checks whether NTP is reachable from the storage controller VMs and synced
   Check package & versions - Checks for packages and versions on Storage Controller VMs
 Check Iptables count - Checks for Iptables count on and ensure it is same on all Storage Controller VMs.              
    Extra pnodes check - Looks for any extra/duplicate pnode entries in the cluster
    Out of memory check - Checks through the log files if the cluster had any oom event
    Supported vSphere versions - Shows all the vSphere Versions supported with your current HXDP version
 Permissions for /tmp - Checks if the /tmp permissions are set correctly
 Check Cluster Policy - Checks the Configured Cluster Policy
 Check springpath_keystore.jceks file - Check if All the SCVM have same keystore file
 SED Capable - Checks if the cluster is SED Capable
 SED Enabled - Checks if Encryption is enabled in the Cluster
 USB-0 Check - If Encryption is enabled, Checks that USB0 interface is present on all the SCVMs
 SED 5100/5200 Drive Check - If we have Micron SED 5100 drives and version is below 3.5.2b, we wont be able to replace or add new 5200 drives
 Disk Lock Check - If Encryption is enabled, Checks for any Locked drives
 Network Checks - Checks the connectivity in Storage network
 Check ZK-Cleanup-Script - Checks to identify ZKTxnCleanUp Script
 Replication Checks - If replication is enabled, we check the local and remote network connectivity (HX 4.5 Only)
 Stretched Cluster Checks - Checks the latency between the sites and the witness VM (HX 4.5 Only)

ESXi Checks: (Below checks are performed on each ESXI node)
    HX User Account check - Verifies if the HXUser is created on all the esxi hosts and has admin rights
    vMotion enabled check - Checks if the vMotion network is confirgued
 Check for ESXI Failback timer - Check for ESXi Failback timer on ESXi host
    Check connectivity between vmk1 and eth1 - Checks the connectivity between the Mgmt and Storage network
    No extra controller vm folders check - Checks for duplicate Controller SCVM Folders
 VMware Tools location check  - Checks for Non default VMware Tools location
 vfat Disk Usage check - Checks for vfat Disk Usage
 Check /tmp usage - Checking for /tmp usage
 Compute Node Checks - All the ESXI checks are also performed on Compute nodes (HX 4.5 Only)


Beispiel für die Hypercheck-Ausgabe aus einem Cluster mit 4 Knoten und gestreckten Knoten



Enter this information of HX-Cluster: Enter the HX-Cluster Root Password: Enter the ESX Root Password: Cluster Name: HX-10-Stretched Site-100 Site-97 Cluster Type: STRETCH_CLUSTER SSH connection established to HX Node: 192.168.53.135 SSH connection established to HX Node: 192.168.53.136 SSH connection established to HX Node: 192.168.53.137 SSH connection established to HX Node: 192.168.53.138 HX Cluster Nodes: +-------+--------------+--------------------------------+ | Nodes | IP Address | HostName | +-------+--------------+--------------------------------+ | 1 | 14.39.53.134 | SpringpathControllerOHCWUK9X3N | +-------+--------------+--------------------------------+ | 2 | 14.39.53.135 | SpringpathController37MHMEIBCY | +-------+--------------+--------------------------------+ | 3 | 14.39.53.136 | SpringpathControllerDWRWWIBFLF | +-------+--------------+--------------------------------+ | 4 | 14.39.53.137 | SpringpathControllerWB4UNXDKX3 | +-------+--------------+--------------------------------+ SSH connection established to ESX Host: 14.39.53.133 SSH connection established to ESX Host: 14.39.53.130 SSH connection established to ESX Host: 14.39.53.132 SSH connection established to ESX Host: 14.39.53.131 HX Controller: 192.168.53.135 Cluster services check [########################] COMPLETED ZooKeeper & Exhibitor check [########################] COMPLETED HDD health check [########################] COMPLETED Pre-Upgrade Check [########################] COMPLETED Network check [########################] COMPLETED HX Controller: 192.168.53.136 Cluster services check [########################] COMPLETED ZooKeeper & Exhibitor check [########################] COMPLETED HDD health check [########################] COMPLETED Pre-Upgrade Check [########################] COMPLETED Network check [########################] COMPLETED HX Controller: 192.168.53.137 Cluster services check [########################] COMPLETED ZooKeeper & Exhibitor check [########################] COMPLETED HDD health check [########################] COMPLETED Pre-Upgrade Check [########################] COMPLETED Network check [########################] COMPLETED HX Controller: 192.168.53.138 Cluster services check [########################] COMPLETED ZooKeeper & Exhibitor check [########################] COMPLETED HDD health check [########################] COMPLETED Pre-Upgrade Check [########################] COMPLETED Network check [########################] COMPLETED HX Controller: 192.168.53.135 Test Summary: +--------------------------------------+-----------+----------------------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+-----------+----------------------------------------------------------------+ | Cluster services check | PASS | Checks storfs, stMgr, sstNodeMgr service running on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Enospc state check | PASS | Checks if the cluster storage utilization is above threshold. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Zookeeper check | PASS | Checks if Zookeeper service is running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Exhibitor check | PASS | Checks if Exhibitor in running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | System Disks Usage | PASS | Checks if /sda1, var/stv and /var/zookeeper is less than 80%. | +--------------------------------------+-----------+----------------------------------------------------------------+ | HDD Health check | PASS | Checks if any drive is in blacklisted state. | +--------------------------------------+-----------+----------------------------------------------------------------+ | DNS check | PASS | Checks if configured DNS is reachable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | vCenter reachability check | PASS | Checks if vCenter is network reachable using PING. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Timestamp check | PASS | Checks if the timestamp is same across all Nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | NTP sync check | PASS | Checks if the NTP is synced with NTP server. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check package & versions | PASS | Checks for count and version of HX packages on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Iptables count | PASS | Checks if the IP Table count matches on all nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Extra pnodes check | PASS | Checks for any stale Node entry. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Memory usage check | PASS | Checks for available memory more than 2GB. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Incidence of OOM in the log file | PASS | Checks for any previous incidence of Out Of Memory Condition. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Supported vSphere versions | 6.0.0-U3 | Prints the supported ESXi versions. | | | 6.5.0-U1 | | | | 6.5.0-U2 | | | | 6.5.0-U3 | | | | 6.7.0-UGA | | | | 6.7.0-U1 | | | | 6.7.0-U2 | | | | 6.7.0-U3 | | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check permissions for /tmp | PASS | Checks if the /tmp permissions are set correctly. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Cluster Policy | Lenient | Checks the Configured Cluster Policy | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check springpath_keystore.jceks file | PASS | All the SCVM have same keystore file. | +--------------------------------------+-----------+----------------------------------------------------------------+ | SED Capable | NO | Checks if the cluster is SED Capable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Witness Reachability | PASS | Checks Witness VM IP address is reachabile. | +--------------------------------------+-----------+----------------------------------------------------------------+
| Check ZK-Cleanup-Script | PASS | Checks to identify ZKTxnCleanUp Script. | 
+--------------------------------------+-----------+----------------------------------------------------------------+ HX Controller: 192.168.53.136 Test Summary: +--------------------------------------+-----------+----------------------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+-----------+----------------------------------------------------------------+ | Cluster services check | PASS | Checks storfs, stMgr, sstNodeMgr service running on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Enospc state check | PASS | Checks if the cluster storage utilization is above threshold. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Zookeeper check | PASS | Checks if Zookeeper service is running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Exhibitor check | PASS | Checks if Exhibitor in running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | System Disks Usage | PASS | Checks if /sda1, var/stv and /var/zookeeper is less than 80%. | +--------------------------------------+-----------+----------------------------------------------------------------+ | HDD Health check | PASS | Checks if any drive is in blacklisted state. | +--------------------------------------+-----------+----------------------------------------------------------------+ | DNS check | PASS | Checks if configured DNS is reachable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | vCenter reachability check | PASS | Checks if vCenter is network reachable using PING. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Timestamp check | PASS | Checks if the timestamp is same across all Nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | NTP sync check | PASS | Checks if the NTP is synced with NTP server. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check package & versions | PASS | Checks for count and version of HX packages on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Iptables count | PASS | Checks if the IP Table count matches on all nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Extra pnodes check | PASS | Checks for any stale Node entry. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Memory usage check | PASS | Checks for available memory more than 2GB. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Incidence of OOM in the log file | PASS | Checks for any previous incidence of Out Of Memory Condition. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Supported vSphere versions | 6.0.0-U3 | Prints the supported ESXi versions. | | | 6.5.0-U1 | | | | 6.5.0-U2 | | | | 6.5.0-U3 | | | | 6.7.0-UGA | | | | 6.7.0-U1 | | | | 6.7.0-U2 | | | | 6.7.0-U3 | | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check permissions for /tmp | PASS | Checks if the /tmp permissions are set correctly. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Cluster Policy | Lenient | Checks the Configured Cluster Policy | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check springpath_keystore.jceks file | PASS | All the SCVM have same keystore file. | +--------------------------------------+-----------+----------------------------------------------------------------+ | SED Capable | NO | Checks if the cluster is SED Capable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Witness Reachability | PASS | Checks Witness VM IP address is reachabile. | +--------------------------------------+-----------+----------------------------------------------------------------+
| Check ZK-Cleanup-Script | PASS | Checks to identify ZKTxnCleanUp Script. | 
+--------------------------------------+-----------+----------------------------------------------------------------+ HX Controller: 192.168.53.137 Test Summary: +--------------------------------------+-----------+----------------------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+-----------+----------------------------------------------------------------+ | Cluster services check | PASS | Checks storfs, stMgr, sstNodeMgr service running on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Enospc state check | PASS | Checks if the cluster storage utilization is above threshold. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Zookeeper check | PASS | Checks if Zookeeper service is running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Exhibitor check | PASS | Checks if Exhibitor in running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | System Disks Usage | PASS | Checks if /sda1, var/stv and /var/zookeeper is less than 80%. | +--------------------------------------+-----------+----------------------------------------------------------------+ | HDD Health check | PASS | Checks if any drive is in blacklisted state. | +--------------------------------------+-----------+----------------------------------------------------------------+ | DNS check | PASS | Checks if configured DNS is reachable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | vCenter reachability check | PASS | Checks if vCenter is network reachable using PING. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Timestamp check | PASS | Checks if the timestamp is same across all Nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | NTP sync check | PASS | Checks if the NTP is synced with NTP server. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check package & versions | PASS | Checks for count and version of HX packages on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Iptables count | PASS | Checks if the IP Table count matches on all nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Extra pnodes check | PASS | Checks for any stale Node entry. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Memory usage check | PASS | Checks for available memory more than 2GB. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Incidence of OOM in the log file | PASS | Checks for any previous incidence of Out Of Memory Condition. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Supported vSphere versions | 6.0.0-U3 | Prints the supported ESXi versions. | | | 6.5.0-U1 | | | | 6.5.0-U2 | | | | 6.5.0-U3 | | | | 6.7.0-UGA | | | | 6.7.0-U1 | | | | 6.7.0-U2 | | | | 6.7.0-U3 | | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check permissions for /tmp | PASS | Checks if the /tmp permissions are set correctly. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Cluster Policy | Lenient | Checks the Configured Cluster Policy | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check springpath_keystore.jceks file | PASS | All the SCVM have same keystore file. | +--------------------------------------+-----------+----------------------------------------------------------------+ | SED Capable | NO | Checks if the cluster is SED Capable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Witness Reachability | PASS | Checks Witness VM IP address is reachabile. | +--------------------------------------+-----------+----------------------------------------------------------------+
| Check ZK-Cleanup-Script | PASS | Checks to identify ZKTxnCleanUp Script. | 
+--------------------------------------+-----------+----------------------------------------------------------------+ HX Controller: 192.168.53.138 Test Summary: +--------------------------------------+-----------+----------------------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+-----------+----------------------------------------------------------------+ | Cluster services check | PASS | Checks storfs, stMgr, sstNodeMgr service running on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Enospc state check | PASS | Checks if the cluster storage utilization is above threshold. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Zookeeper check | PASS | Checks if Zookeeper service is running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Exhibitor check | PASS | Checks if Exhibitor in running. | +--------------------------------------+-----------+----------------------------------------------------------------+ | System Disks Usage | PASS | Checks if /sda1, var/stv and /var/zookeeper is less than 80%. | +--------------------------------------+-----------+----------------------------------------------------------------+ | HDD Health check | PASS | Checks if any drive is in blacklisted state. | +--------------------------------------+-----------+----------------------------------------------------------------+ | DNS check | PASS | Checks if configured DNS is reachable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | vCenter reachability check | PASS | Checks if vCenter is network reachable using PING. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Timestamp check | PASS | Checks if the timestamp is same across all Nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | NTP sync check | PASS | Checks if the NTP is synced with NTP server. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check package & versions | PASS | Checks for count and version of HX packages on each node. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Iptables count | PASS | Checks if the IP Table count matches on all nodes. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Extra pnodes check | PASS | Checks for any stale Node entry. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Memory usage check | PASS | Checks for available memory more than 2GB. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Incidence of OOM in the log file | PASS | Checks for any previous incidence of Out Of Memory Condition. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Supported vSphere versions | 6.0.0-U3 | Prints the supported ESXi versions. | | | 6.5.0-U1 | | | | 6.5.0-U2 | | | | 6.5.0-U3 | | | | 6.7.0-UGA | | | | 6.7.0-U1 | | | | 6.7.0-U2 | | | | 6.7.0-U3 | | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check permissions for /tmp | PASS | Checks if the /tmp permissions are set correctly. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Cluster Policy | Lenient | Checks the Configured Cluster Policy | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check springpath_keystore.jceks file | PASS | All the SCVM have same keystore file. | +--------------------------------------+-----------+----------------------------------------------------------------+ | SED Capable | NO | Checks if the cluster is SED Capable. | +--------------------------------------+-----------+----------------------------------------------------------------+ | Check Witness Reachability | FAIL | Checks Witness VM IP address is reachabile. | +--------------------------------------+-----------+----------------------------------------------------------------+
| Check ZK-Cleanup-Script | PASS | Checks to identify ZKTxnCleanUp Script. | 
+--------------------------------------+-----------+----------------------------------------------------------------+ | Check Disk for SMART Failure. | PASS | Checks disks for SMART Failure. |
+--------------------------------------+-----------+----------------------------------------------------------------+ ################################################################################ Network check: ################################################################################ ESX vmk0: 14.39.53.130, 14.39.53.131, 14.39.53.132, 14.39.53.133 ESX vmk1: 192.168.53.130, 192.168.53.131, 192.168.53.132, 192.168.53.133 SCVM eth0: 14.39.53.134, 14.39.53.135, 14.39.53.136, 14.39.53.137 SCVM eth1: 192.168.53.135, 192.168.53.136, 192.168.53.137, 192.168.53.138 ESX Host: 14.39.53.130 +--------------------------------------+--------+-------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+--------+-------------------------------------------------+ | HX User Account check | PASS | Checks if HXUSER is present. | +--------------------------------------+--------+-------------------------------------------------+ | vMotion enabled check | PASS | Checks if vMotion is enabled on the host. | +--------------------------------------+--------+-------------------------------------------------+ | Check for ESXI Failback timer | PASS | Checks for ESXi FAILBACK timer set to 30000ms. | +--------------------------------------+--------+-------------------------------------------------+ | Check vmk1 ping to eth1 | PASS | Checks Network between ESXi vmk1 and SCVM eth1. | +--------------------------------------+--------+-------------------------------------------------+ | No extra controller vm folders check | PASS | Checks for duplicate Controller SCVM Folders. | +--------------------------------------+--------+-------------------------------------------------+ | VMware Tools location check | PASS | Checks for Non default VMware Tools location. | +--------------------------------------+--------+-------------------------------------------------+ | vfat Disk Usage check | PASS | Checks for vfat Disk Usage. | +--------------------------------------+--------+-------------------------------------------------+ | Check /tmp usage | PASS | Checking for /tmp usage. | +--------------------------------------+--------+-------------------------------------------------+ ESX Host: 14.39.53.131 +--------------------------------------+--------+-------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+--------+-------------------------------------------------+ | HX User Account check | PASS | Checks if HXUSER is present. | +--------------------------------------+--------+-------------------------------------------------+ | vMotion enabled check | PASS | Checks if vMotion is enabled on the host. | +--------------------------------------+--------+-------------------------------------------------+ | Check for ESXI Failback timer | PASS | Checks for ESXi FAILBACK timer set to 30000ms. | +--------------------------------------+--------+-------------------------------------------------+ | Check vmk1 ping to eth1 | PASS | Checks Network between ESXi vmk1 and SCVM eth1. | +--------------------------------------+--------+-------------------------------------------------+ | No extra controller vm folders check | PASS | Checks for duplicate Controller SCVM Folders. | +--------------------------------------+--------+-------------------------------------------------+ | VMware Tools location check | PASS | Checks for Non default VMware Tools location. | +--------------------------------------+--------+-------------------------------------------------+ | vfat Disk Usage check | PASS | Checks for vfat Disk Usage. | +--------------------------------------+--------+-------------------------------------------------+ | Check /tmp usage | PASS | Checking for /tmp usage. | +--------------------------------------+--------+-------------------------------------------------+ ESX Host: 14.39.53.132 +--------------------------------------+--------+-------------------------------------------------+ | Name | Result | Comments | +--------------------------------------+--------+-------------------------------------------------+ | HX User Account check | PASS | Checks if HXUSER is present. | +--------------------------------------+--------+-------------------------------------------------+ | vMotion enabled check | PASS | Checks if vMotion is enabled on the host. | +--------------------------------------+--------+-------------------------------------------------+ | Check for ESXI Failback timer | PASS | Checks for ESXi FAILBACK timer set to 30000ms. | +--------------------------------------+--------+-------------------------------------------------+ | Check vmk1 ping to eth1 | PASS | Checks Network between ESXi vmk1 and SCVM eth1. | +--------------------------------------+--------+-------------------------------------------------+ | No extra controller vm folders check | PASS | Checks for duplicate Controller SCVM Folders. | +--------------------------------------+--------+-------------------------------------------------+ | VMware Tools location check | PASS | Checks for Non default VMware Tools location. | +--------------------------------------+--------+-------------------------------------------------+ | vfat Disk Usage check | PASS | Checks for vfat Disk Usage. | +--------------------------------------+--------+-------------------------------------------------+ | Check /tmp usage | PASS | Checking for /tmp usage. | +--------------------------------------+--------+-------------------------------------------------+ Main Report File: HX_Tool_Main_Report_2020-08-26_09-54-59.txt Report tar file: HX_Report_2020_08_26_09_43_18.tar Report file copied to path: /var/log/springpath Release Notes: https://www.cisco.com/c/en/us/support/hyperconverged-systems/hyperflex-hx-data-platform-software/products-release-notes-list.html Upgrade Guides: https://www.cisco.com/c/en/us/support/hyperconverged-systems/hyperflex-hx-data-platform-software/products-installation-guides-list.html Note: 1) If upgrading to HX 4.0(2a), please review the following link and perform workaround – https://tinyurl.com/wc7j5qp 2) Please check the status of Compute nodes manually, script only verifies the config on the converged nodes. 3) Hypercheck doesnot perform FAILOVER TEST, so please ensure that the upstream is configured for network connectivity for JUMBO or NORMAL MTU size as needed.
4) If you have performed any activity on your vcenter(like upgrade, certificate replacement,etc.), it is recommended to reregister your cluster to the vcenter before performing upgrades. Refer to the Hyperflex CLI guide for relevant commands. 


Analyse der Werkzeugausgabe

Nächste Schritte

• Das Tool automatisiert die Ausführung manueller Befehle auf Hyperflex-Systemen.
• Wenn das Tool OK ausführt und alle Tests BESTÄTIGT, ist das HX-System für alle Prüfungen geeignet, die das Skript durchgeführt hat.
• In Situationen, in denen das Tool bei einigen Prüfungen FEHLT oder nicht erfolgreich ausgeführt wird, können Sie die CLI-Befehle (die aufgeführt sind) verwenden, um die gleichen Prüfungen auf Hyperflex System durchzuführen, wie sie vom Skript manuell durchgeführt werden.
• Das Tool überprüft nicht auf alte/neue/offene/gelöste Vorbehalte. Daher wird dringend empfohlen, die Hyperflex-Versionshinweise und Upgrade-Leitfäden vor jeder Upgrade- oder Wartungsaktivität zu lesen.

Hinweis: Öffnen Sie kein TAC-Ticket, da das Skript nicht ausgeführt werden konnte. Führen Sie die Befehle manuell aus, identifizieren Sie das Problem, und öffnen Sie einen Serviceticket für das erkannte Problem.

CLI-Befehle

Auf Hyperflex SCVM:



SSH to All Hyperflex SCVMs-

# service_status.sh

# sysmtool --ns cluster --cmd enospcinfo

# echo srvr | nc 0 2181

# pidof exhibitor

# stcli disk list --ip <Corresponding ESXi Mgmt IP Address> |grep -B 2 -A 8 blacklisted

# stcli services dns show (and ping the IPs listed)

# ping <vCenter IP Address>

# date ; compare the time on all SCVMs. They should ideally be identical

# stcli services ntp show

# stcli cleaner info

# ntpq -p -4 

# dpkg -l | grep -i springpath | grep -v storfs-support*

# sysmtool --ns disk --cmd list | grep -i blacklisted

# iptables -L -n | wc -l 

# stcli cluster info

# df -h ; check that /var/stv should be less than 80%

# zgrep -i “out of memory” /var/log/springpath/debug-storfs.*

# ping -I eth0 <eth0> of all SCVMs

# ping -I eth1 <eth1> of all SCVMs

# "ls -ld /tmp" check for 775 and 777

# stcli cluster info | grep -i 'clusterAccessPolicy:' | head -1

# md5sum /etc/springpath/secure/springpath_keystore.jceks

# cat /etc/springpath/sed_capability.conf

# cat /etc/springpath/sed.conf

# cat /var/log/springpath/diskslotmap-v2.txt

# stcli cluster info | grep dataZkIp (ping dataZkIp for latency)


Auf ESXi-Systemen:



SSH to all ESXi hosts

# esxcli system account list

# esxcli network firewall ruleset list | grep -i vMotion

# esxcli software vib list| egrep -i 'scvm|stHyper|stfs'

# chkconfig --list | grep -E 'ntpd|hostd|vpxa|stHypervisorSvc|scvmclient|hxctlvm' 

# esxcfg-vmknic -l ; confirm that vMotion VMK2 is created

# vmkping -I vmk1 <eth1> of all SCVMs

# cd /vmfs/volumes/Springpath-XXXXXXXXXX ; Ensure that it has only one Folder that has the Storage Controller VM

# df -h | grep vfat ; Ensure dir has free space

Zugehörige Informationen

• Technischer Support und Downloads von Cisco