VS and management network interface must be disconnected

1.  Migrate all VM's inside this node to another node.
2.  If the node is controller, move to another controller.
3.  Isolate the node to prevent VM's move to this node.
4.  Replace the node with new one.

1. The configuration of the new host (hardware configuration, number and capacity of disks) must not be lower than that of the original failed host.

2. The management IP address of the replacement host must not be the same as that of the original host.

3. The wiring of the host must be the same as that of the old host.

4. The version of the new host must be the same as the version of the host in the original cluster.

The following should be taken into account while replacing a node:

1. Data Backup To ensure that you don't lose anything, be careful to backup any crucial data from the previous node.

2. Compatibility Verify that the new node is in harmony with the network and system that already exist.

3. Configuration Get ready to set up the new node using the same configuration as the previous one.

4. Testing After installation, test the new node to make sure it functions properly inside the network.

5. Documentation Make sure all records are up to date with the modifications made during the replacement.

6. Downtime Assume that there may be a downtime during the replacement procedure. In the event that this occurs, inform users.

7. Monitoring  As soon as the new node is operational, keep an eye on its functionality to identify any problems early.

When performing a node replacement in the HCI (Hyper-Converged Infrastructure) 5.8.6 version, there are several key aspects you should consider to ensure a smooth and successful process:

Data Backup:

Ensure that all critical data is backed up before starting the replacement process to avoid any data loss.
Compatibility Check:

Verify that the replacement node is compatible with the existing HCI cluster in terms of hardware, firmware, and software versions.
Cluster Health:

Check the health of the cluster before starting the node replacement. The cluster should be in a stable state with no critical issues.
Network Configuration:

Ensure the network settings on the replacement node match the cluster's requirements, including IP addresses, VLAN settings, and network roles.
Node Configuration:

Make sure the new node is properly configured according to the existing cluster settings, including storage, compute, and networking configurations.
Data Rebalancing:

Be aware of the need for data rebalancing after the node is replaced. This process can consume network and CPU resources, so plan accordingly to minimize impact.
Replication and Redundancy:

Check the status of data replication and redundancy within the cluster. Ensure that redundancy is maintained throughout the replacement process.
Testing:

After replacing the node, perform thorough testing to ensure the new node is fully integrated and functioning as expected within the cluster.
Documentation and Logging:

Document the entire replacement process and keep logs of any issues encountered for future reference and troubleshooting.
Cluster Rebuild and Synchronization:

Monitor the cluster rebuild and synchronization process to ensure that data is properly distributed across the nodes.
These steps are crucial for minimizing risks and ensuring that the node replacement process is carried out smoothly.

• Backup Data: Make sure to back up any important data on the old node.
• Check Settings: Ensure the new node has the same settings and software as the old one.
• Update Network: Set up the new node with the correct network details.
• Test: Run tests on the new node to make sure it works properly.
• Monitor Performance: Keep an eye on how the new node performs.
• Update Records: Update any relevant documentation with details about the new node.
• Verify Compatibility: Check that the new node works with your existing setup.
  
  

1. Ensure compatibility, backup data & update firmware.
2. Migrate workloads & check data replication.
3. Gracefully shut down & remove the old node from the cluster.
4. Add the new node to the cluster than verify synchronization & restore workloads.
5. Run diagnostics, monitor performance & check logs.
6. Update records.

Hi,moving a node from one Sangfor HCI cluster to another involves several steps and careful planning to minimize downtime. Here are some general steps you can follow:

Data Backup: Initiate the process by ensuring that a recent backup of all vital data on the node to be moved is available.
VM Migration: Transfer all Virtual Machines (VMs) from the node to be moved to other nodes within the same cluster. This can be accomplished by exporting the VM and subsequently importing it to another HCI.
Cluster Controller Change: If the node to be moved is currently a cluster controller, you’ll need to assign another node as the cluster controller. This can be done by selecting the desired node and then choosing More > Set to Cluster Controller.
Node Removal: Once the VMs have been migrated and the cluster controller has been reassigned (if required), the node can be removed from the cluster. Please note that the Sangfor HCI interface does not directly provide the option to remove HCI nodes from the cluster. It is advisable to seek assistance from Sangfor support for this step.
Node Addition to New Cluster: After successful removal of the node from the old cluster, it can be added to the new cluster. Follow the standard procedure for adding a node to a Sangfor HCI cluster.
Resource Rebalancing: Once the node has been added to the new cluster, rebalance the resources as required to ensure optimal performance.

node replacement must have similar or higher number of  HDD and sizes. Total volume of HDD
cannot used as references.