After you configure a Provider VM, VMware Data Services Manager provides status of the Provider node. You can view the status of the Provider node, analyse the status, and take actions if required.
Status of Provider Nodes
The following table lists different status of Provider nodes in an HA cluster:
| Status | Description | Implication | Recommendation |
|---|---|---|---|
| Active Mode | Node is healthy and all services are up and running. | Only an Active node can consume updates. | Apply VMware Data Services Manager updates for provider nodes only when they are in Active mode. |
| Critical | Apart from the application management service (apms) and vpostgresql service, any other VMware Data Services Manager (provider, update manager, and so on) or system service is down. | Node is unable to consume any updates. | Execute the Provider Appliance Health Status API (/appliance/status) to understand the details, and then take action as required. |
| Lost Connectivity | Node is unable to connect to the Provider appliance because apms or vpostgresql service is down. | Node is down, unreachable, or unable consume any updates. | Before you update or edit the cluster, troubleshoot to check if the Provider node is up, if apms is up, and if vpostgresql service is up. Restart the service that is down. |
| Maintenance Mode | Node is consuming VMware Data Services Manager updates. | Wait until VMware Data Services Manager updates are completed. | Do not perform any Add or Delete operations on the Provider Node because it may lead to instability of the cluster. |
| Unknown | VMware Data Services Manager is not able to provide any status of the node because root password of the Provider appliance has expired. | Node cannot consume any updates. | Change the root password immediately for the smooth functioning of the Provider. |
Note: You can use the /appliance/status API to determine the health of a Provider node.
