Managing Nodes
Nodes are initially added to a storage cluster using the Create Cluster feature of the HX Data Platform Installer. Nodes are added to an existing storage cluster using the Expand Cluster feature of the HX Data Platform Installer. When nodes are added or removed from the storage cluster, the HX Data Platform adjusts the storage cluster status accordingly.
-
Tasks for node maintenance with a failed node.
-
The ESXi or HX software needs to be reinstalled.
-
A node component needs to be replaced.
-
The node needs to be replaced.
-
The node needs to be removed.
-
-
Tasks for node maintenance with a non-failed node.
-
Putting the node into maintenance mode.
-
Changing the ESX password.
-
Note |
Though there are subtle differences, the terms server, host, and node are used interchangeably throughout the HyperFlex documentation. Generally a server is a physical unit that runs software dedicated to a specific purpose. A node is a server within a larger group, typically a software cluster or a rack of servers. Cisco hardware documentation tends to use the term node. A host is a server that is running the virtualization and/or HyperFlex storage software, as it is 'host' to virtual machines. VMware documentation tends to use the term host. |
Procedure
Step 1 |
Monitor the nodes in the cluster. HX storage cluster, node, and node component status is monitored and reported to HX Connect, HX Data Platform Plug-in, vCenter UI, and assorted logs as Operational status (online, offline) and Resiliency (healthy, warning) status values.
|
||||
Step 2 |
Analyze the node failure and determine the action to take. This frequently requires monitoring the node state through HX Connect, HX Data Platform Plug-in, vCenter, or ESXi; checking the server beacons; and collecting and analyzing logs. |
||||
Step 3 |
Complete the identified tasks.
|