You can check the health of components in your Migrate for Compute Engine installation by using health checks pages in the Velostrata Manager. The health checks feature is useful after you've configured your system and are ready to migrate VMs.
Migrate for Compute Engine periodically performs health checks on the following components by polling for status, then displaying the results.
- Cloud Extension
- Exporter
- Velostrata On-Premises Backend virtual appliance
Migrate for Compute Engine provides two places to check health:
- In the Velostrata Backend, where you can confirm that the Velostrata Backend has a healthy connection with the Velostrata Manager. Without this connection, other health checks are not possible.
- In the Velostrata Manager, where you can check the health of other components.
Migrate for Compute Engine provides health checks at any time for systems configured to migrate from vSphere. For other migration sources, health checks are available only during migration.
Checking health of the Velostrata Manager connection with the Velostrata Backend
Unless the connection between Velostrata Manager and the Velostrata Backend is healthy, the system will be unable to report on health for other components. To check on that Velostrata Manager connection, Migrate for Compute Engine provides user interface that you can reach directly via its URL.
- Log in to vCenter.
In the Navigator pane, locate the Velostrata Backend VM created from the .ova file you installed.
For more on deploying the Velostrata Backend, see Deploying the Velostrata Backend.
On the Summary tab, note or copy the Host IP address.
In a web browser, use the IP address to visit the health check page for the Velostrata Backend with a URL of the following form:
https://IP-address
In the on-prem appliance login page, enter the
admin
username and password you specified when deploying the Velostrata Backend, then click Login.On the Google Cloud Velostrata On-prem Appliance page, you can view the status of the connection with the Velostrata Manager.
Checking system health after successfully configuring Velostrata Manager
When the connection between Velostrata Manager and the Velostrata Backend is healthy, you can view health check information for other Migrate for Compute Engine components.
- Log in to the Velostrata Manager.
- On the Home page, click Target Cloud.
- On the Target Cloud page, view the list of Cloud Extensions, along with their state and health checks.
- To view an extension's health check information, click the Health checks icon at the right end of the extension's row in the list.
On the Health Checks page, view the list of components for which health has been checked.
Unhealthy connections will be displayed first by default. In the row for an unhealthy connection, the Result column will display Failed rather than Passed. The Reason column will display a message describing the failure, such as that the connection timed out or was denied.
Health check error codes
The following tables list the health check error codes for Cloud Extension nodes, Migrate for Compute Engine Exporter, and the Velostrata Backend.
The vCenter error console also displays errors returned by the Compute Engine and Cloud Storage APIs. For more information on these errors, refer to documentation for Compute Engine and Cloud Storage.
Cloud Extension edge nodes
Code | Description |
---|---|
110 | CloudEdge Process |
120 | CloudEdge Functionality |
140 | Storage Grid Process |
145 | Object Store Availability |
150 | Cloud Control Access |
170 | iSCSI Layer |
800 | Instance Running |
820 | Critical Disk Space Utilization |
830 | Instance Availability |
840 | Check Instance Not Terminated |
850 | Internal Error |
860 | SQS |
900 | Frontend connectivity from Backend\Importer |
Migrate for Compute Engine Exporter
Code | Description |
---|---|
140 | Storage Grid Process |
145 | Object Store Availability |
410 | Exporter Process |
420 | Exporter Functionality |
830 | Instance Availability |
840 | Check Instance Not Terminated |
850 | Internal Error |
Velostrata Backend
Code | Description |
---|---|
210 | Backend Service |
220 | Backend Functionality |
830 | Instance Availability |
850 | Internal Error |
910 | VC Connection Status from Backend |
920 | VC Credentials |
930 | VC Privileges |