Powering on a cluster

Last Updated : Dec 17, 2025 |
Prolog information
Use this procedure to gracefully power on your solution cluster. You can also use this procedure to power on after an unexpected power down. Complete this procedure during a maintenance window.
  1. Log in to vCenter as an administrator or with the account used to deploy the cluster.
  2. Click the VMs and Templates tab.
  3. Power on Cluster Control Manager.
    1. Locate and click Cluster Control Manager in the folder you designated for the cluster.
    2. Right-click Cluster Control Manager and then click PowerPower On.
    3. Wait until the VM has initialized and you can log in to Cluster Control Manager before proceeding to the next step.
  4. Locate and click on each node virtual machine in the folder you designated during your cluster deployment.
  5. Power on the image-registry controller-work node first and then the controller-worker and worker nodes.
    ADDITIONAL INFORMATION:
    Caution:
    You must power on the controller-worker nodes before powering on the worker nodes.
    You must power on the nodes containing a second disk before powering on nodes without a second disk.
    1. Right-click on the controller node containing the second disk that was running the image-registry pod and then click PowerPower On
    2. Wait until login screen is present on VM console before proceeding with next VM.
    3. Right-click on the other controller node containing a second disk and then click PowerPower On
    4. Wait until login screen is present on VM console before proceeding with next VM.
    5. Right-click on each controller-worker node without a second disk and then click PowerPower On
    6. Right-click each worker node and then click PowerPower On.
  6. Wait approximately 8 minutes for all nodes to power on before proceeding to the next step.
  7. If you ran the pre-infra-upgrade command and gracefully shut down the cluster nodes, then run the post-infra-upgrade command to start the authorization service database.
    ADDITIONAL INFORMATION:
    Skip this step if the cluster was unexpectedly powered down.
  8. Wait approximately 7 minutes for pods to come up and for storage to sync.
  9. For Avaya Analytics™, if you stopped all Avaya Oceana® traffic then run the following command to start data flow to the cluster.
    ADDITIONAL INFORMATION:
    Skip this step if the cluster was unexpectedly powered down.
    ADDITIONAL INFORMATION:
    Note:
    This step requires an account with root privileges.
    • For non-HA Avaya Analytics™:
      kubectl scale --replicas=1 deployment orca-ref-input-adaptor
    • For HA Avaya Analytics™:
      kubectl scale --replicas=2 deployment orca-ref-input-adaptor
    ADDITIONAL INFORMATION:
    Wait for the command to complete before continuing. Ensure that the command is successful.
  10. Run ccm smoke-test to verify the operational state of the cluster.
    ADDITIONAL INFORMATION:
    If ccm smoke-test fails, run it again in 10 minutes. If the test continuously fails for over an hour, contact your technical support representative.