The Cyber Recovery connector CLI allows you to check network connectivity between the Cyber Recovery connector and the Orchestrator, cloud file system, and auto-support server, and the protected site vCenter Server and ESXi hosts.
Cyber Recovery connector Connectivity Check CLI
- Determine if the connector can communicate successfully with the Orchestrator, the cloud file system, and autosupport server (cloud scope).
- Determine if the connector can communicate successfully with registered vCenter Servers and its ESXi hosts on the protected site (local scope).
- Obtain the IP address or FQDN, and port number of unreachable entities, and error information if an entity is unreachable.
To check connectivity from the Cyber Recovery connector to other entities in your environment, run the following Cyber Recovery connector CLI command on the virtual appliance:
drc network test
| Option | Description |
|---|---|
| --scope [all | cloud | local] |
Sets the scope of the check, which can be one of three options:
|
| --orchestrator | Fully Qualified Domain Name (FQDN) of the Orchestrator. You must supply a password for authentication. This option is required only if the Cyber Recovery connector is not configured. |
| --vcenter [vcenter server IP address/FQDN] | For a local scope check, use this option to check connectivity to a registered vCenter Server using its IP address or FQDN. You must add the --vcenter-user option, which requires password authentication after you run the command. |
| --vcenter-username | When performing a local connectivity to a registered vCenter Server, you must supply the vCenter Server username. The command prompts you for the password of this user. |
| --output-format [JSON | default] |
Choose the output format (optional):
|
Check Connectivity to All Entities
SSH to the Cyber Recovery connector virtual appliance and run this command to check connectivity from the Cyber Recovery connector to all entities (cloud and local) in your environment:
drc network test --scope all
In this example output, all VMware Live Cyber Recovery cloud entities are reachable by the Cyber Recovery connector, while the protected site vCenter Servers are unreachable. A comment section for the unreachable vCenter Servers indicates the cause of failure.
connector-name>># drc network test --scope all FQDN/IP Port Cloud EntityType Status Comment 192.168.139.207 80 False VCENTER UNREACHABLE Cannot complete login due to an incorrect user name or password. 192.168.139.207 443 False VCENTER UNREACHABLE Cannot complete login due to an incorrect user name or password. 35.84.127.181 443 True SCFS REACHABLE -- autosupport.datrium.com 443 True SUPPORT REACHABLE -- vcdr-56-188-244-16.staging.app.vcdr.vmware.com 443 True ORCHESTRATOR REACHABLE -- vcdr-56-188-244-16.staging.app.vcdr.vmware.com 443 True ORCHESTRATOR REACHABLE --
Check Connectivity to Cloud Entities
Run this command to check connectivity from the Cyber Recovery connector to the Orchestrator, the cloud file system, and the Auto-support server:
connector-name>># drc network test --scope cloud
This example output shows that all VMware Live Cyber Recovery entities are reachable by the Cyber Recovery connector:
drc network test --scope cloud FQDN/IP Port Cloud EntityType Status Comment 35.84.127.181 443 True SCFS REACHABLE -- autosupport.datrium.com 443 True SUPPORT REACHABLE -- vcdr-52-184-288-53.staging.app.vcdr.vmware.com 443 True ORCHESTRATOR REACHABLE -- vcdr-52-184-288-53.staging.app.vcdr.vmware.com 443 True ORCHESTRATOR REACHABLE --
Check Connectivity to Local Entities
Run this command to check connectivity from the Cyber Recovery connector to a protected site vCenter Server and its ESXi hosts:
connector-name>># drc network test --scope local
This example output shows that all local entities are reachable by the Cyber Recovery connector:
drc network test --scope local FQDN/IP Port Cloud EntityType Status Comment 192.168.139.207 80 False VCENTER REACHABLE -- 192.168.139.207 443 False VCENTER REACHABLE -- 192.168.139.211 902 False ESXI REACHABLE --
Check Connectivity to the Orchestrator and Cloud Entities
Run the following command if the Cyber Recovery connector is not configured but you want to check connectivity from the Cyber Recovery connector to the Orchestrator, and other cloud entities. You must provide the Orchestrator IP address or FQDN.
drc network test --scope cloud --orchestrator vcdr-192-168-21-0.staging.app.vcdr.vmware.com Enter the site-specific Orchestrator password:
This example output shows that all VMware Live Cyber Recovery entities are reachable:
FQDN/IP Port Cloud EntityType Status Comment 35.84.127.181 443 True SCFS REACHABLE -- autosupport.datrium.com 443 True SUPPORT REACHABLE -- vcdr-54-184-246-36.staging.app.vcdr.vmware.com 443 True ORCHESTRATOR REACHABLE -- vcdr-54-184-246-36.staging.app.vcdr.vmware.com 443 True ORCHESTRATOR REACHABLE --
Check Connectivity to vCenter Server
Run the following command to check connectivity from the Cyber Recovery connector to a registered vCenter Server and its ESXi hosts. You must provide the registered vCenter Server IP address or FQDN and a vCenter Server username. The CLI prompts you for the vCenter Server user password.
drc network test --vcenter 192.168.139.207 --vcenter-username [email protected] --scope local Enter password for vCenter login:
This example output shows that all local vCenter Server entities are reachable:
FQDN/IP Port Cloud EntityType Status Comment 192.168.139.207 80 False VCENTER REACHABLE -- 192.168.139.207 443 False VCENTER REACHABLE -- 192.168.139.211 902 False ESXI REACHABLE --
