Validate Environment
Validate Environment ("validateEnv.py") is a tool used to analyze the computing environment primarily before the JetStream DR software installation. The tool evaluates various components necessary for seamless installation and operation of JetStream DR software and it also evaluates network connectivity between the components. Validate Environment performs the following checks:
Network
a. Check local NICs and deduce IPs.
b. Check if the local IPs are DHCP or static.
c. Check and retrieve the Network segment details (mapped to NICs).
d. Check and retrieve the IP routes for all local NICs.
MSA
a. Check if input MSA FQDN record is found in any one of the input DNS servers or default DNS server.
b. Check if input MSA IP matches the IP resolved from DNS.
c. Check if MSA IP is reachable.
d. Do a reverse lookup of the IP and retrieve the FQDN.
** ONLY POST INSTALL PHASE**
e. Check the certificate state.
f. Check if ports 443 and 8443 are open from each and every local NIC.
MMS
a. Check if MMS subscription link is resolved from DNS.
b. Check if MMS subscription link is reachable.
c. Check if port 443 is open from each and every local NIC.
vCenter
a. Check if vCenter FQDN is resolvable.
b. Check if the vCenter IP resolved from DNS matches the input vCenter IP.
c. Check if vCenter FQDN or IP is reachable.
d. Do a reverse lookup of the IP and retrieve the FQDN.
e. Check the certificate state of vCenter.
f. Check if ports 80, 443 and 8443 are open from each and every local NIC.
g. Check if login to vCenter is successful.
h. Check and get the vCenter build version.
Object store
a. Check if object store FQDN is resolvable.
b. Check if object store is reachable.
c. Check if the object store port is open (443 for Azure) from each and every local NIC.
d. Check the upload/download object bandwidth to/from object store.
ESXi host
a. Check and retrieve all hosts from input cluster. If no cluster is input, then all ESXi hosts are retrieved.
b. Check if every host is reachable.
c. Check if port 5989 is open.
d. Check if CIM service and IOF daemon service is running and active.
e. Check and retrieve the ESXi build version.
DRVA
a. If DRVA names are input, check if the DRVA name is resolvable from DNS.
b. Check if the IP resolved from DNS is reachable.
** ONLY POST INSTALL PHASE**
c. If no DRVA names are input, fetch a list of DRVAs from MSA.
d. Check and retrieve DRVA IPs.
e. Check if DRVA IPs are reachable (from the place where pre-check tool is run).
f. Check if DRVA IPS are reachable from MSA.
g. Check if ports 32877 and 32878 are open from each and every local NIC.
NOTE: If the computing environment involves multiple network interfaces, either of the following can be done to check the networks:
• Re-initialize the deployed automation toolkit VM on the new network segment and re-run the tool. Repeat this for all network segments.
• Use the management interface of the deployed automation toolkit VM to create multiple networks. The multiple network configuration should emulate configuration on a DRVA (with routes and default gateway). For example: https://<Deployed Automation toolkit ova IP>:9090