vRealize Operations includes a central page where you can monitor and manage the nodes in your vRealize Operations cluster and the adapters that are installed on the nodes.
How Cluster Management Works
You can view and change the online or offline state of the overall vRealize Operations cluster or the individual nodes. In addition, you can enable or disable high availability (HA) and view statistics related to the adapters that are installed on the nodes.
Where You Find Cluster Management
Log in to the vRealize Operations administration interface at https://master-node-name-or-ip-address/admin.
Cluster Management Options
The options include cluster-level monitoring and management features.
|Cluster Status|| Displays the online, offline, or unknown state of the vRealize Operations cluster and provides an option to take the cluster online or offline.
If a cluster fails to go offline, click the Force Take Offline button to take the cluster offline.
Note: The Force Take Offline button appears only when the Bring Cluster offline operation fails.
You can select to display the reason for taking the cluster offline. Select the Show reason on maintenance page check box in the Take Cluster Offline dialog box. When you log in to vRealize Operations when the cluster is offline, the reason for taking the cluster offline is displayed.
|High Availability||Indicates whether HA is enabled, disabled, or degraded and provides an option to change that setting.|
|Continuous Availability||Indicates whether CA is enabled, disabled, or degraded and provides an option to change that setting.|
vRealize Operations provides node-level information as well as a toolbar for taking nodes online or offline.
|Generate Passphrase||Generate a passphrase that can be used instead of the administrator credentials to add a node to this cluster.|
|Add New Node||Add a new node to the this cluster. You cannot add a witness node.|
|Take Node Online/Offline||You can select the required node and bring it online or offline. You are required to understand the risk involved and provide a valid reason for the action performed when you bring a node online or offline.|
|Remove Node||Remove node from the cluster without any loss of collected data. Only offline or inaccessible remote collector nodes can be removed. Data nodes must be removed by shrinking.|
|Reload Nodes||Reload data in the screen.|
|Shrink Cluster||This option provides a mechanism to remove a node without having to lose any data. The shrink cluster removes nodes by migrating data from one node to any other node.
All the historical data is either moved to the primary node or any other node, which has sufficient disk space.
If HA is enabled and you have selected the replica node for removal, then you are asked to select another replica node. vRealize Operations provides a list of nodes that be a possible candidate to become a replica node.vRealize Operations stops collecting data from the removed nodes. However, the data that is available in the removed node is migrated to an existing node. Once the migration is complete, then the removed nodes are deleted with the cluster state as offline.
For remote collectors, if any adapters are on the collectors of the removed nodes, then such nodes are migrated as well.
Note: vRealize Operations cannot move pinned adapters. The adapter instances which were pinned on removed nodes do not move to another collector automatically. You must change the collector before starting the shrink cluster process.
|Replace Node||You cannot remove one node in a CA cluster, because the nodes are in pairs. Use the replace node option to replace one of the nodes in the CA cluster. The following rules apply:
|Node Name||Machine name of the node.
The node that you are logged into displays a dot next to the name.
|Node Address||Internet protocol (IP) address of the node. Primary and replica nodes require static IP addresses. Data nodes may use DHCP or static IP.|
|Cluster Role||Type of vRealize Operations node: primary, data, replica, or remote collector.|
|State||Powered on, powered off, unknown, or other condition of the node.|
|Status||Online, offline, unknown, or other condition of the node.|
|Objects||Total environment objects that the node currently monitors.|
|Metrics||Total metrics that the node has collected since being added to the cluster.|
|Build||vRealize Operations software build number installed on the node.|
|Version||vRealize Operations software version installed on the node.|
|Deployment Type||Type of machine on which the node is running: vApp|
|SSH Status||Enable or disable the SSH Status.|
In addition, there are adapter statistics for the selected node.
|Name||Name that the installing user gave to the adapter.|
|Status||Indication of whether the adapter is collecting data or not.|
|Objects||Total environment objects that the adapter currently monitors.|
|Metrics||Total metrics that the adapter has collected since being installed on the node.|
|Last Collection Time||Date and time of the most recent data collection by the adapter.|
|Added On||Date and time when the adapter was installed on the node.|