Powering Off a cluster

Last Updated : Mar 20, 2026 |
Prolog information
Use this procedure to gracefully shut down your lab. Complete this procedure during a maintenance window.
Note:
Skip this procedure if you are upgrading from 4.3.1.0
Caution:
If you shut down your lab 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 Cluster Control Manager with customer account and then switch to root user.
  2. Run ccm smoke-test before starting any upgrade, migration, or reboot.
    ADDITIONAL INFORMATION:
    Resolve any negative condition before starting any procedure.
  3. 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.
  4. Determine which nodes contain the image registry pod using kubectl get pods -n image-registry -o wide.
    ADDITIONAL INFORMATION:
    Note the cluster node IP/FQDN which has the image registry.
  5. 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.
  6. Log in to vCenter as an administrator or with the account used to deploy the cluster.
  7. Click the VMs and Templates tab.
  8. Locate and click on each node virtual machine in the folder you designated during your cluster deployment.
  9. Use the following steps to shut down each node:
    ADDITIONAL INFORMATION:
    1. Right-click on diskless node and click Power Shut Down Guest OS to shut down the node. Wait for the node to shut down.
    2. Right-click on disk bearing node 1 and click Power Shut Down Guest OS to shut down the node. Wait for the node to shut down.
    3. Right-click on disk bearing node 2 and click Power Shut Down Guest OS to shut down the node. Wait for the node to shut down.