All grid node types: Replacing a Linux node

If a failure requires that you deploy new physical or virtual hosts or reinstall Linux on an existing host, you must deploy and configure replacement hosts before you can recover individual grid nodes. This procedure is one step of the grid node recovery process for all types of grid node.

About this task

This guide uses "Linux" to refer to a Red Hat® Enterprise Linux®, Ubuntu®, CentOS®, or Debian® deployment. Use the NetApp Interoperability Matrix Tool to get a list of supported versions.

This procedure is only performed as one step in the process of recovering virtual Storage Nodes, primary or non-primary Admin Nodes, API Gateway Nodes, or Archive Nodes. The steps are identical regardless of the type of grid node you are recovering.

If more than one grid node is hosted on a physical or virtual Linux host, you can recover the grid nodes in any order. However, recovering a primary Admin Node first, if present, prevents the recovery of other grid nodes from stalling as they try to contact the primary Admin Node to register for recovery.

Steps

  1. Deploying new Linux hosts
  2. Restoring grid nodes to the host

After you finish

Grid node recovery might be complete after you restore existing nodes to the host if no corrective actions were necessary during recovery. "What next?" explains how to determine if grid node recovery is complete, and lists the next actions to take for each node type if additional steps are needed.