Powering on a cluster

Last Updated : Sep 25, 2023 |
Prolog information
Metadata
Keywords:
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.
Important:
Do not manually delete virtual machine cluster nodes from vCenter.
  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. Enter swversion.
  5. Locate and click on each node virtual machine in the folder you designated during your cluster deployment.
  6. Power on the nodes. in the following order:
    1. Right-click on the master node that runs the registry-pod. Click PowerPower On and waitn for the node to allow login.
    2. Right-click on next controller-worker node containing a second disk and click PowerPower On.
    3. Wait 7 minutes.
    4. Right-click on the controller-worker node without a second disk and click PowerPower On.
    5. Right-click each worker node and then click PowerPower On.
  7. Wait approximately 10 minutes for all nodes to power on before continuing.
  8. If the cluster was shutdown using a gracefully power off:
    1. Enter post-infra-upgrade to start the authorization service database.
    2. Wait approximately 20 minutes for pods to come up and for storage to sync.
    3. During this time, monitor the pods for 0/1 status and only proceed for the next step when the status of the pods has not changed for about 10 minutes. Remaining pods show 0/1 or INIT as they are waiting on the orca-ref- input-adaptor pods to come up in next step.
  9. For Avaya Analytics™, if you stopped all Avaya Oceana® traffic, restart data flow to the cluster.
    1. This step requires an account with root privileges.
    • For non-HA Avaya Analytics™, enter:
      kubectl scale --replicas=1 deployment orca-ref-input-adaptor
    • For HA Avaya Analytics™, enter:
      kubectl scale --replicas=2 deployment orca-ref-input-adaptor
    1. Wait for the command to complete before continuing. This can take 90 minutes.
    2. Monitor the status of the pods by entering the following command to list those pods that are not fully running as yet:
      ADDITIONAL INFORMATION:
      k get pods -A | egrep -v "1/1|2/2|3/3|4/4|5/5|6/6|Completed"
    3. Wait for all pods to show Running or Completed. Check using k get pods -A
  10. Verify the operational status of the cluster
    1. Run ccm smoke-test
    2. 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.
  11. Check the health of the pods:
    1. Enter k get pods -A
    2. If any pod is listed as other than Running or Completed, do not proceed any further. Contact Avaya Support.
    3. Enter ccm status --health
    4. Check that all products are listed as Healthy.
    5. Check that historical reporting is working.
    6. Check that the supervisor desktop shows data.