This section explains how to safely replace hardware components on Supermicro platforms running Qumulo Core.

This section provides guidance for safely replacing hardware components on Supermicro platforms running Qumulo Core. It covers procedures for both hot-swappable components (drives, power supplies) and components that require the node to be taken offline (DIMMs, fans, CPUs, motherboards, NICs).

Component Replacement Overview

Component Hot-Swappable Node Offline Required
Drives (NVMe, HDD) Yes No
Power Supplies Yes No
Fans No Yes
DIMMs (Memory) No Yes
CPUs No Yes
Motherboard No Yes
NICs No Yes

Hot-Swappable Components

Drive Replacement

For the drive replacement procedure, see Drive Replacement.

Platform-Specific Notes

GrandTwin (AS-2115GT-HNTR)

Each node in the GrandTwin chassis has dedicated drive bays. Ensure you identify the correct node before replacing drives.

Hybrid Models (SH-series)

The SH-series models have separate NVMe cache bays and HDD storage bays. Verify you are replacing the correct drive type.

Power Supply Replacement

All Supermicro platforms use redundant power supplies, allowing hot-swap replacement.

  1. Verify redundancy: ensure both PSUs are connected and at least one is functioning.
  2. Identify the failed PSU by checking the PSU LED (amber indicates failure).
  3. Remove the failed PSU:
    • Disconnect the power cord.
    • Press the release latch.
    • Slide the PSU out of the chassis.
  4. Install the replacement PSU:
    • Slide the new PSU into the bay until it clicks.
    • Connect the power cord.
    • Verify the PSU LED shows green.

Components Requiring Node Offline

For DIMM, CPU, motherboard, or NIC replacements, the node must be safely taken offline using the following procedure.

Before You Begin

Step 1: Verify Cluster Protection Status

You can verify cluster protection status using either the Web UI or the CLI.

Using the Qumulo Web UI

  1. Log in to the Qumulo Web UI.
  2. Navigate to Cluster > Cluster Overview.
  3. Under Data Protection, verify that the cluster can tolerate a node failure.

Using the qq CLI

SSH into any node and run:

qq protection_status_get

You will see output similar to:

{
    "remaining_drive_failures": 1,
    "remaining_node_failures": 2
}

Step 2: Recuse the Node

Recusing a node safely removes it from the cluster quorum, allowing data protection mechanisms to account for the missing node.

  1. SSH into the node that requires maintenance.

  2. Run the recuse command:

    /opt/qumulo/recuse_node.py --reason "Component replacement"

  3. After running this command, a red banner appears in the Qumulo Web UI stating:

    Unable to communicate with node X

  4. This confirms the node was successfully recused from the cluster.

Step 3: Power Off the Node

After the node is recused, power it off:

Using IPMI

  1. Log in to the node’s IPMI interface.
  2. Navigate to Remote Control > Power Control.
  3. Click Power Off.

Using the CLI

From another node or management system:

ipmitool -I lanplus -H <IPMI-IP> -U <your_user> -P <password> power off

Using the Physical Power Button

Press and hold the power button on the front panel until the server powers off.

Step 4: Replace the Component

Perform the hardware replacement according to your hardware vendor’s documentation:

DIMM Replacement Notes

When replacing DIMMs:

  1. Follow your vendor’s DIMM population guidelines.
  2. Ensure replacement DIMMs match the specifications of the original.
  3. Use proper ESD precautions.

Step 5: Power On the Node

After completing the component replacement:

  1. Power on the node using the power button, IPMI, or IPMI command.
  2. Wait for the node to complete POST and boot Qumulo Core.
  3. Verify the component is functioning:
    • For DIMMs: Check total memory in IPMI or using qq node_status
    • For NICs: Check network connectivity
    • For fans: Check IPMI sensor readings

Step 6: Reintroduce the Node

After verifying the component replacement was successful, reintroduce the node to the cluster:

  1. SSH into the node that was serviced.

  2. Run the reintroduce command:

    /opt/qumulo/sbin/reintroduce_node.sh

  3. Monitor the Qumulo Web UI to verify:

    • The red banner disappears
    • The node appears healthy in the cluster overview
    • Data reprotection begins (if applicable)

Step 7: Verify Cluster Health

After reintroduction:

  1. Check cluster protection status:

    qq protection_status_get

  2. Verify all nodes are healthy:

    qq cluster_slots

  3. Monitor the Web UI for any alerts or warnings.

Getting Help

If you have any questions or encounter issues during component replacement, contact contact the Qumulo Care Team through Slack, email, or by phone.

When contacting support, provide:

  • Cluster name and node serial number
  • Description of the issue
  • Error messages from the Qumulo Web UI or CLI
  • IPMI event logs (if available)