Exécuter l'outil Hyperflex Health and Pre-upgrade Check Tool

Introduction

Ce document décrit le processus d'exécution de l'outil Hypercheck Health and Pre-upgrade.

Conditions préalables

Exigences

Cisco recommande que vous ayez une connaissance de ce sujet :

• Hyperflex

Composants utilisés

Les informations contenues dans ce document sont basées sur l'outil Hypercheck Health and Pre-upgrade.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. Si votre réseau est en ligne, assurez-vous de bien comprendre l’incidence possible des commandes.

Informations générales

Cet outil est un utilitaire qui effectue des auto-contrôles proactifs sur les systèmes Hyperflex afin de garantir leur stabilité et leur résilience. Il permet d'automatiser une liste de vérifications d'intégrité et de pré-mise à niveau sur les systèmes Hyperflex afin de gagner du temps lors des opérations de mise à niveau et de maintenance d'Hyperflex.

Remarque : téléchargez toujours la dernière version de l'outil avant de l'utiliser. Comme l'outil est fréquemment amélioré, l'utilisation d'une version antérieure peut entraîner l'absence de vérifications importantes.

Systèmes HX pris en charge

• Versions Hyperflex : 1.8, 2.0, 2.1, 2.5, 2.6, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5
• Cluster Hyperflex Standard
• Cluster Hyperflex Stretched
• Cluster de périphérie Hyperflex (2 noeuds, 3 noeuds et 4 noeuds)
• Prise en charge uniquement sur le cluster Hyperflex sur VMWare ESXi

Remarque : pour plus d'informations sur l'exécution d'Hypercheck sur le cluster Hyperflex HyperV, reportez-vous à Hypercheck : Hyperflex Health & Pre-Upgrade Check Tool - HyperV.

Cas d’utilisation

Les délais d'utilisation de l'outil Hyperflex Health and Pre-upgrade check sont les suivants :

• Avant les mises à niveau Hyperflex
• Vérification de l'intégrité Hyperflex avant et après les fenêtres de maintenance
• Afin d'identifier les lecteurs/disques défaillants
• Lorsque vous travaillez avec le TAC Cisco
• Contrôle d'intégrité proactif à tout moment

Marche à suivre

HX versions 4.5 et ultérieures

Étape 1. Lancez une connexion SSH à la machine virtuelle du contrôleur de stockage (SCVM) à l'aide de l'adresse IP de gestion de cluster (CMIP), qui est votre adresse IP HX-connect.

Étape 2. Exécutez la commande hypercheck .

admin:~$ hypercheck

Étape 3. Entrez le mot de passe d'administration SCVM lorsque vous y êtes invité, puis le mot de passe racine d'ESXi.

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 versions 4.0 et antérieures

Étape 1. Téléchargez Hyperflex-Hypercheck.zip à partir du compte de périphérique github Cisco. Procurez-vous la copie la plus récente, qui contient les dernières améliorations et mises à jour.

Remarque : seuls les utilisateurs Cisco enregistrés peuvent accéder aux outils, fichiers et informations internes de Cisco.

Remarque : utilisez uniquement le script téléchargé à partir du compte devnet github Cisco.

Étape 2. Téléchargez-le sur le SCVM avec le CMIP.

Utilisez votre méthode préférée - scp/sftp/ftp/tftp - Afin de copier le Hyperflex-Hypercheck.zip dans le répertoire/tmp.

Pour MAC :

Exécutez la SCP à partir de l'interface de ligne de commande (vérifiez que le Hyperflex-Hypercheck.zip se trouve dans le même dossier à partir duquel vous exécutez la SCP).

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

Utilisez ceci afin d'identifier l'IP de gestion de cluster dans votre environnement HX - guide Hyperflex.

Pour Windows :

Vous pouvez utiliser WINSCP afin de transférer les fichiers comme indiqué ici :

Étape 3. Extrayez le contenu de Hyperflex-Hypercheck.zip.

Tapez cd /tmp afin de passer au répertoire/tmp.



root@SpringpathController7PVQWP6WV1:~# cd /tmp/


Tapez unzip Hyperflex-Hypercheck.zip afin d'extraire les fichiers.



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# 


Étape 4. Exécutez le script HXTool Python.

Tapez cd Hyperflex-Hypercheck afin de naviguer vers le répertoireHyperflex-Hypercheck.



root@SpringpathControllerABCDE01234:/tmp# cd Hyperflex-Hypercheck


Tapez python HXTool.py  afin d'exécuter le script.



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


Étape 5. Entrez le mot de passe racine SCVM lorsque vous y êtes invité.



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

Remarque : pour arrêter l'exécution du script, utilisez la touche (CTRL+Z) et elle s'arrête immédiatement.

Étape 6. L'outil Hyperflex-Hypercheck commence ses vérifications. Il faut environ 3 à 10 minutes pour que l'exécution se termine, ce qui dépend du nombre de noeuds convergents dans le cluster.

Étape 7. Obtenir un rapport des résultats du script. Vous pouvez le recevoir comme indiqué :

Le fichierHypercheck Report tar est enregistré sous /var/log/springpath  et /tmp/Hyperflex-Hypercheck. Vous pouvez donc télécharger le bundle tar à partir de under /var/log/springpath ou /tmp/Hyperflex-Hypercheck. Sinon, vous pouvez simplement générer et télécharger un bundle de support storfs qui contient également le tar du rapport hypercheck.

Exemple de fichier tar de rapport - HX_Report_2020_08_30_10_43_50.tar est copié vers le chemin : /var/log/springpath.

Tapez ls -l | grep HX_Report afin de revoir les fichiers créés par l'outil Hyperflex-Hypercheck.



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# 


Fichiers et journaux du bundle de journaux Hypercheck :



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


Étape 8. Exportez le HX_YYYY_MM_DD_HH_MM_SS.tar et partagez-le avec le TAC.

Utilisez la méthode de votre choix afin d'exporter les journaux Hypercheck avec l'utilisation de scp/sftp/ftp/tftp depuis SCVM ou vous pouvez simplement télécharger le bundle de support storfs qui contient le bundle tar HX_Report.

Comprendre les résultats/contrôles effectués

Contrôles effectués par Hypercheck

Ces vérifications sont effectuées par l'outil Hyperflex-Hypercheck :



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)


Exemple de sortie Hypercheck d'un cluster étendu à 4 noeuds



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. 


Analyser les résultats des outils

Étapes suivantes

• L'outil automatise le processus d'exécution des commandes manuelles sur Hyperflex Systems.
• Si l'outil fonctionne OK et donne une PASS sur tous les tests, le système HX est bon pour toutes les vérifications que le script a effectuées.
• Dans les cas où l'outil ÉCHOUE sur certaines vérifications ou ne s'exécute pas correctement, vous pouvez utiliser les commandes CLI (qui sont répertoriées) afin d'effectuer les mêmes vérifications sur Hyperflex System que celles effectuées manuellement par le script.
• L'outil ne vérifie pas les anciennes/nouvelles/ouvertes/résolues et il est donc fortement recommandé de consulter les notes de version et les guides de mise à niveau d'Hyperflex avant toute activité de mise à niveau ou de maintenance.

Remarque : n'ouvrez pas de dossier TAC car le script n'a pas pu s'exécuter. Exécutez les commandes manuellement, identifiez le problème et ouvrez une demande de service pour le problème identifié.

Commandes CLI

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


Sur les systèmes ESXi :



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

Informations connexes

• Assistance technique de Cisco et téléchargements