Sommario

Introduzione

Prerequisiti

Requisiti

Componenti usati

Premesse

Sistemi HX supportati

Scenari d'uso

Modalità d'uso

HX versione 4.5 e successive

HX versione 4.0 e precedenti

Uscite/controlli eseguiti

Controlli eseguiti da Hypercheck

Output di esempio di Hypercheck da un cluster esteso a 4 nodi

Analizza output strumento

Fasi successive

Comandi CLI

Informazioni correlate

Introduzione

Questo documento descrive il processo di esecuzione dello strumento Hypercheck Health and Pre-upgrade.

Prerequisiti

Requisiti

Cisco raccomanda la conoscenza di questo argomento:

- Hyperflex

Componenti usati

Le informazioni fornite in questo documento si basano sullo strumento Hypercheck Health and Pre-upgrade.

Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi.

Premesse

Questo strumento è un'utilità che esegue autocontrolli proattivi sui sistemi Hyperflex per garantirne la stabilità e la resilienza. Consente di automatizzare un elenco di controlli dello stato e pre-aggiornamento dei sistemi Hyperflex per risparmiare tempo durante le operazioni di aggiornamento e manutenzione di Hyperflex.

Nota: scarica sempre la versione più recente dello strumento prima dell'uso. Poiché lo strumento viene migliorato frequentemente, l'utilizzo di una versione precedente può comportare la mancanza di controlli importanti.

Sistemi HX supportati

- Versioni 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 Hyperflex Edge (2 nodi, 3 nodi e 4 nodi)

- Supportato solo su cluster Hyperflex su VMWare ESXi

Nota: per informazioni su come eseguire Hypercheck sul cluster HyperV Hyperflex, fare riferimento a Hypercheck: strumento di verifica dello stato e pre-aggiornamento di Hyperflex - HyperV.

Scenari d'uso

I tempi effettivi per l'utilizzo dello strumento Hyperflex Health and Pre-upgrade Check sono i seguenti:

- Prima degli aggiornamenti di Hyperflex

- Controllo dello stato di Hyperflex prima e dopo le finestre di manutenzione

- Per identificare le unità/i dischi guasti

- Quando si lavora con Cisco TAC

- Controllo proattivo in qualsiasi momento

Modalità d'uso

HX versione 4.5 e successive

Passaggio 1. Avviare una connessione SSH alla macchina virtuale del controller di storage (SCVM) utilizzando l'IP di gestione del cluster (CMIP), che è l'IP della connessione HX.

Passaggio 2. Eseguire il comando hypercheck.

admin:~$ hypercheck

Passaggio 3. Quando richiesto, immettere la password SCVM admin e la password root di 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 versione 4.0 e precedenti

Passaggio 1. Scarica Hyperflex-Hypercheck.zip dall'account Cisco github devnet. Ottenere la copia più recente con gli ultimi miglioramenti e aggiornamenti.

Nota: solo gli utenti Cisco registrati possono accedere agli strumenti, ai file e alle informazioni interni di Cisco.

Nota: utilizzare solo lo script scaricato dall'account devnet Cisco github.

Passaggio 2. Caricarlo nello SCVM con CMIP.

Utilizzare il metodo preferito - scp/sftp/ftp/tftp - Per copiare il file nellaHyperflex-Hypercheck.zip /tmp directory.

Per MAC:

Eseguire SCP dalla CLI (verificare che si troviHyperflex-Hypercheck.zip nella stessa cartella da cui si esegue SCP).

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

Usare questo comando per identificare l'IP di gestione cluster nell'ambiente HX in uso - playbook Hyperflex.

Per Windows:

È possibile utilizzare WINSCP per trasferire i file come mostrato di seguito:

Passaggio 3. Estrarre il contenuto di Hyperflex-Hypercheck.zip.

Digitare cd /tmp per passare alla /tmp directory.

root@SpringpathController7PVQWP6WV1:~# cd /tmp/

Digitare unzip Hyperflex-Hypercheck.zip per estrarre i file.

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#

Passaggio 4. Eseguire lo script HXTool Python.

Digitare cd Hyperflex-Hypercheck per passare alla Hyperflex-Hypercheck directory.

root@SpringpathControllerABCDE01234:/tmp# cd Hyperflex-Hypercheck

Digitare python HXTool.py  per eseguire lo script.

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

Passaggio 5. Quando richiesto, immettere la password della radice SCVM.

Enter this information of HX-Cluster:

Enter the HX-Cluster Root Password:

Enter the ESX Root Password:

Nota: per arrestare l'esecuzione dello script, utilizzare il tasto (CTRL+Z) e arrestarsi immediatamente.

Passaggio 6. Lo strumento Hyperflex-Hypercheck avvia i controlli. Il completamento dell'esecuzione, che dipende dal numero di nodi convergenti nel cluster, richiede circa 3-10 minuti.

Passaggio 7. Ottenere un report degli output dello script. È possibile riceverlo come mostrato:

Il fileHypercheck Report tar viene salvato in /var/log/springpath  e /tmp/Hyperflex-Hypercheck. Quindi, potete scaricare il pacchetto tar da sotto /var/log/springpath o /tmp/Hyperflex-Hypercheck. In alternativa, è possibile generare e caricare un bundle di supporto storfs che contiene anche l'hypercheck report tar.

Esempio di file TAR di report - HX_Report_2020_08_30_10_43_50.tar viene copiato nel percorso: /var/log/springpath.

Digitare ls -l | grep HX_Report per esaminare i file creati dallo strumento 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#

File e log nel bundle del log 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

Passaggio 8. Esporta il file HX_YYYY_MM_DD_HH_MM_SS.tar e condividilo con TAC.

Usare il metodo preferito per esportare i log di Hypercheck con l'uso di scp/sftp/ftp/tftp da SCVM o è possibile semplicemente scaricare il bundle storfs-support che contiene il bundle tar HX_Report.

Uscite/controlli eseguiti

Controlli eseguiti da Hypercheck

Questi controlli vengono eseguiti dallo strumento 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)

Output di esempio di Hypercheck da un cluster esteso a 4 nodi

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.

Analizza output strumento

Fasi successive

- Lo strumento automatizza il processo di esecuzione dei comandi manuali su Hyperflex Systems.

- Se lo strumento esegue OK e passa a tutti i test, il sistema HX è adatto per tutti i controlli eseguiti dallo script.

- Nei casi in cui lo strumento non riesce a eseguire alcuni controlli o non viene eseguito correttamente, è possibile utilizzare i comandi CLI (elencati) per eseguire gli stessi controlli su Hyperflex System eseguiti manualmente dallo script.

- Lo strumento non verifica eventuali avvertenze vecchie/nuove/aperte/risolte e pertanto si consiglia vivamente di esaminare le Note di rilascio e le Guide all'aggiornamento di Hyperflex prima di qualsiasi attività di aggiornamento o manutenzione.

Nota: non aprire una richiesta TAC perché l'esecuzione dello script non è riuscita. Eseguire i comandi manualmente, identificare il problema e aprire una SR per il problema identificato.

Comandi CLI

Su SCVM Hyperflex:

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)

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

Informazioni correlate

- Supporto tecnico Cisco e download