Migrate for Compute Engine periodically performs health checks on the following components:
- Cloud Extension
- Exporter
- Migrate for Compute Engine On-Premises Backend virtual appliance
To view the health checks:
- Log into the vSphere console.
- Review the Status column for data centers you want to review.
If the status is Impaired, click that cell to see more details about which Cloud Edge node is impaired along with error codes:
The following tables define the health check error codes for Cloud Extension Nodes, Velostrata Exporter, and the Migrate for Compute Engine 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.
Health check error codes for 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 |
Health check error codes for Velostrata 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 |
Health check error codes for Velostrata backend
210 | Backend Service |
220 | Backend Functionality |
830 | Instance Availability |
850 | Internal Error |