---
title: "Replacing an EBox"
slug: "replacing-an-ebox"
tags: ["5.4"]
updated: 2026-10-28T01:53:34Z
published: 2026-10-28T01:53:34Z
canonical: "docs.vastdata.com/replacing-an-ebox"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Replacing an EBox

This procedure describes how to replace an existing EBox with a new one. The new unit is configured to have the same name and IP address as the one it replaces.

SSDs and SCMs from the replaced unit are removed from it and inserted in the new unit. This means there is no loss of data, and the replacement can be completed in a few minutes.

EBoxes are replace one by one. If several units are being replaced, complete these steps for one unit before starting on the next.

## Prerequisites

- The cluster must have at least two EBoxes, each with an active CNode, in order to replace an EBox (this ensures at least one active CNode in the cluster, as CNodes are part of the EBox).
- Please consult your VAST Data sales engineer for help designating switch ports and ensuring that they are configured with the correct port designations for DNodes as required.

## Step 1: Remove faulty EBox

1. In the **Eboxes** tab, right-click the faulty Ebox and select **Deactivate**.
2. Right-click and select **Power off**, and then remove the unit from the rack, The state for the EBox should indicate **Failed**.

## Step 2: Add the Replacement EBox

1. Rack mount the new EBox and add the new EBox to the cluster. Follow the instructions in this [cluster expansion procedure](/docs-5-4/docs/adding-cboxes-dboxes-or-eboxes-to-a-cluster) to add the EBox to the cluster. Make sure to select **Empty box** in the **General Settings** screen.

## Step 3: Migrate the SSDs to the New EBox

1. On the **Clusters** tab of the **Infrastructure** page, check that the cluster's **Raid State** is *healthy*.
2. Prepare to move SSDs from the old EBox into the new EBox. Plan to insert each SSD into the slot in the new EBox that has the same slot number as in the old EBox.
3. Migrate each SSD, one at a time, as follows:
  1. Remove the SSD from the faulty EBox.
  2. Insert the removed SSD into the target slot in the new EBox.

## Step 4: Migrate the SCMs to the New EBox

Follow these steps if the EBoxes have SCMs.

1. Prepare to move SCMs from the old EBox into the new EBox. Plan to insert each SCM into the slot in the new EBox that has the same slot number as in the old EBox.
2. On the **Clusters** tab of the **Infrastructure** page, check that the cluster's **SCM State** is *healthy*.
3. For each SCM in turn:
  1. In the SCMs tab, right-click the SCM and select **Deactivate**.
  2. When the SCM is deactivated, remove the SCM from the faulty EBox.
  3. Insert it into the target slot in the new EBox. In case of a faulty SCM, insert the replacement SCM into the planned slot.
  4. Verify that the slot is active and the device is healthy.
  5. Right-click the moved SCM and select **Activate**.
  6. Verify that the cluster's **SCM State** is *healthy* before proceeding with the next SCM.

## Step 5: Configure Networking for the New EBox

The networking for the EBox is configured manually by VAST Support engineers. The new EBox unit will have the same IP address and ID as the faulty one it is replacing.

## Step 6: Activate the new EBox

1. In the **Eboxes** tab, select the EBox, right-click and select **Replace**. This activates the new EBox and configures it as part of the cluster.
2. Click **Yes** to confirm your action. The new EBox unit is now configured as part of the cluster, a process that can take a few minutes. When complete, the status of the EBox is *Active*. You can monitor the process in the Activities page (look for activities marked '*replace_ebox*').
3. Ship the replaced unit back to VAST Data.