Powering off a cluster

Last Updated : Aug 01, 2024 |
Prolog information
Use this procedure to gracefully shut down your solution cluster. Complete this procedure during a maintenance window.
Caution:
If you shut down your cluster using a different method than what is described in this procedure, file corruption might occur.
Before you begin
  • You must plan a maintenance window to perform this task.
  • Stop call events across the solution.
    To stop all Avaya Oceana® traffic for an Avaya Analytics™ cluster, run the kubectl scale deployment orca-ref-input-adaptor --replicas=0 command using an account with root privileges.
  • Back up Common Services using the ccm backup command.
    If you do not perform a backup, you risk a full reinstallation of the solution.
  • Back up product application data as described in your solution documentation.
  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. Locate and click on each node virtual machine in the folder you designated during your cluster deployment.
  4. Log in to Cluster Control Manager.
  5. Run the pre-infra-upgrade command to gracefully shut down the authorization service database.
    ADDITIONAL INFORMATION:
    Wait for the command to complete before continuing. Ensure that this command is successful.
  6. Run ccm version -k to determine role of each node: either worker or controller-worker.
    ADDITIONAL INFORMATION:
    Note the node roles, for use when shutting down or powering on nodes.
  7. Run kubectl get pods -n image-registry -o wide as a root user.
    ADDITIONAL INFORMATION:
    Note the cluster node hosting the image registry.
  8. Determine which nodes contain a second disk and which nodes are diskless.
    ADDITIONAL INFORMATION:
    Note the disk status of each node, for use when shutting down or powering on nodes.
    To identify a list of nodes that have a second disk, run the checkInfra -Sd | grep LVM_THIN command. The output lists the FQDNs of nodes containing a second disk.
    [cust@flex190-129 ~]$ checkInfra -Sd | grep LVM_THIN
    | pool_sds             | flex190-132.dr.example.com | LVM_THIN | vg_sds/sds_thinpool |   341.00 GiB |    464.76 GiB | True         | Ok    |            |
    | pool_sds             | flex190-133.dr.example.com | LVM_THIN | vg_sds/sds_thinpool |   341.00 GiB |    464.76 GiB | True         | Ok    |            |
    [cust@flex190-129 ~]$
    The other nodes in the cluster are diskless nodes. That is, node FQDNs not printed in the command output are diskless nodes.
  9. Log in to vCenter as an administrator or with the account used to deploy the cluster.
  10. Click the VMs and Templates tab.
  11. Locate and click on each node virtual machine in the folder you designated during your cluster deployment.
  12. Power off worker and controller-worker nodes.
    ADDITIONAL INFORMATION:
    Caution:
    You must shut down the guest OS of the worker nodes before shutting down the controller-worker nodes.
    You must gracefully shut down the guest OS on nodes without a second disk (diskless nodes) before shutting down nodes containing a second disk.
    1. Right-click on each worker node and then click Power Shut Down Guest OS.
    2. Wait until the worker node has completely powered down before continuing to the next node. Check VM status in the vCenter.
    3. Right-click on the controller-worker node without a second disk and then click Power Shut Down Guest OS.
    4. Wait until the worker node has completely powered down before continuing to the next node. Check VM status in the vCenter.
    5. Right-click on each controller-worker node containing a second disk and then click Power Shut Down Guest OS.
      ADDITIONAL INFORMATION:
      Note:
      Power these off relatively together. No wait time is needed between the nodes.
  13. Power off Cluster Control Manager.
    1. Click the VMs and Templates tab.
    2. Locate and click on Cluster Control Manager in the folder you designated for the cluster.
    3. Right-click Cluster Control Manager and then click Power Shut Down Guest OS.