GHV Usage
GHV is executed from the command line or terminal using the command healthView.py. It takes the MSA FQDN/IP, vCenter Server hostname and credentials as input. If the vCenter Server password is not provided, the script prompts the user to enter it.
Command
Two optional primary inputs can be used:
-o OUTPUTDIR |
The directory where all the files generated by the tool are saved. The default directory is healthView-dir. |
-c CONFIGFILE |
The database file where the data from a prior invocation is saved. This is used for comparison to the current invocation instead of the default file. |
Additional optional inputs can also be applied:
--use-certificate-login |
Use certificate based login instead of vCenter username/password. This option can be used if the tool is being executed in the MSA. |
-r RPOTHRESHOLD |
Maximum permissible RPO in minutes for a protected domain beyond which GHV flags it as an error condition. |
-i IOERRORTHRESHOLD |
Maximum permissible increase in IO errors between two consecutive executions of GHV. |
-s SUPPORTDIR |
Directory where MSA support logs are downloaded and saved. |
--non-recoverable |
Only list VMs that are not in a complete, recoverable state. |
--trigger-alarm |
Triggers a GHV specific vCenter alarm. |
Example: Help Command
[admin@fs123-COSbld healthView]$ python3 healthView.py -h
usage: healthView.py [-h] -m MSAIP -vi VCHOSTNAME [-vu VCUSER] [-vp VCPWD]
[-u] [-c CONFIGFILE] [-r RPOTHRESHOLD]
[-i IOERRORTHRESHOLD] [-o OUTPUTDIR] [-s SUPPORTDIR] [-n]
[-t]
Global health view of JetStream DR components
optional arguments:
-h, --help show this help message and exit
-m MSAIP, --msa-ip MSAIP
MSA IP
-vi VCHOSTNAME, --vc-hostname VCHOSTNAME
vcenter hostname
-vu VCUSER, --vc-user VCUSER
vCenter username
-vp VCPWD, --vc-pwd VCPWD
vCenter password. If the input is not provided, then
the script will prompt for the vCenter password
-u, --use-certificate-login
Use certificate based login instead of
username/password
-c CONFIGFILE, --config-file CONFIGFILE
Saved jetdr configuration file
-r RPOTHRESHOLD, --rpo-threshold RPOTHRESHOLD
Maximum permissible RPO in minutes
-i IOERRORTHRESHOLD, --io-error-threshold IOERRORTHRESHOLD
Maximum permissible IO errors between 2 consecutive
runs
-o OUTPUTDIR, --output-dir OUTPUTDIR
Directory where output files are saved
-s SUPPORTDIR, --support-bundle SUPPORTDIR
Directory where the support logs are saved
-n, --non-recoverable
List only VMs that are not in complete recoverable
state
-t, --trigger-alarm Triggers a health viewer specific vCenter alarm
[admin@fs123-COSbld healthView]$
Comparing Status
It is possible to compare the saved results of a previous run to the current configuration status by doing the following:
- When a desired configuration status is achieved in the output of GHV, save a copy of the DB file which is present in healthView-dir/jetdrConfig.json.
- Use the saved DB file as the input for the -c CONFIGFILE option. This will generate a comparison of the current status to the last saved status in the DB file when GHV is run.