Shutdown and Startup sequence for a vRealize Operations cluster
search cancel

Shutdown and Startup sequence for a vRealize Operations cluster

book

Article ID: 341964

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article provide steps to safely reboot one or more vRealize Operations cluster nodes if the cluster cannot be taken offline from the Admin UI.

Environment

VMware vRealize Operations Manager 6.6.x
VMware vRealize Operations Manager 6.x
VMware vRealize Operations Manager 6.0.x
VMware vRealize Operations Manager 6.5.x
VMware vRealize Operations Manager 6.2.x
VMware vRealize Operations Manager 6.3.x
VMware vRealize Operations 8.0.x
VMware vRealize Operations Manager 6.7.x
VMware vRealize Operations Manager 6.4.x
VMware vRealize Operations Manager 7.5.x
VMware vRealize Operations Manager 7.0.x
VMware vRealize Operations 8.x
VMware vRealize Operations Manager 6.1.x

Resolution

If you are unable to take the entire cluster offline or online by clicking Take Offline or Bring Online under Cluster Status in the Admin UI, follow the orders below applicable to your cluster type.

 

Non HA/CA enabled Clusters

Taking Nodes Offline

In vCenter, preform a Shut Down Guest OS action on the VM.
vRealize Operations nodes should be taken offline in the following order:
  1. Remote collector node(s)
  2. Data node(s)
  3. Primary node
 

Bringing Nodes Online

In vCenter, preform a Power On action on the VM.
vRealize Operations nodes should be brought online in the following order:

  1. Primary node
  2. Data node(s)
  3. Remote collector node(s)
 

HA enabled Clusters

Taking Nodes Offline

In vCenter, preform a Shut Down Guest OS action on the VM.
vRealize Operations nodes should be taken offline in the following order:
  1. Remote collector node(s)
  2. Data node(s)
  3. Primary replica node
  4. Primary node
 

Bringing Nodes Online

In vCenter, preform a Power On action on the VM.
vRealize Operations nodes should be brought online in the following order:

  1. Primary node
  2. Primary replica node
  3. Data node(s)
  4. Remote collector node(s)
 

CA enabled Clusters

Taking Nodes Offline

In vCenter, preform a Shut Down Guest OS action on the VM.
vRealize Operations nodes should be taken offline in the following order:
  1. Witness node
  2. Remote collector node(s)
  3. FD2 Replica Data node(s)
  4. FD2 Primary replica node
  5. FD1 Data node(s)
  6. FD1 Primary node
 

Bringing Nodes Online

In vCenter, preform a Power On action on the VM.
vRealize Operations  nodes should be brought online in the following order:

  1. FD1 Primary node
  2. FD1 Data node(s)
  3. FD2 Primary replica node
  4. FD2 Replica Data node(s)
  5. Remote collector node(s)
  6. Witness node


Additional Information

For more information on how to take a node offline or bring a node online, see Rebooting nodes in vRealize Operations.

Impact/Risks:
Taking vRealize Operations nodes offline one by one can have negative effects on the cluster if not done in the correct order.
Whenever possible, VMware recommends to take the entire cluster offline or online by clicking Take Offline or Bring Online under Cluster Status in the Admin UI.

These steps are only to be used when the cluster cannot be taken offline or brought online from the Admin UI.