| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.workload | pms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Replace a scale unit node on an Azure Stack integrated system | Microsoft Docs |
Learn how to replace a physical scale unit node on an Azure Stack integrated system. |
azure-stack |
troettinger |
byronr |
f9434689-ee66-493c-a237-5c81e528e5de |
azure-stack |
na |
na |
na |
article |
10/20/2017 |
twooley |
Applies to: Azure Stack integrated systems
This article describes the general process to replace a physical computer (also referred to as a scale unit node) on an Azure Stack integrated system. Actual scale unit node replacement steps will vary based on your original equipment manufacturer (OEM) hardware vendor. See your vendor’s field replaceable unit (FRU) documentation for detailed steps that are specific to your system.
The following flow diagram shows the general FRU process to replace an entire scale unit node.
*This action may not be required based on the physical condition of the hardware.
If a scale unit node is down, you’ll receive all the following critical alerts:
- Node not connected to network controller
- Node inaccessible for virtual machine placement
- Scale unit node is offline
If you open the "Scale unit node is offline" alert, the alert description contains the scale unit node that's inaccessible. You may also receive additional alerts in the OEM-specific monitoring solution that's running on the hardware lifecycle host.
The following steps are provided as a high-level overview of the scale unit node replacement process. See your OEM hardware vendor’s FRU documentation for detailed steps that are specific to your system. Do not follow these steps without referring to your OEM-provided documentation.
-
Use the Drain action to put the scale unit node into maintenance mode. This action may not be required based on the physical condition of the hardware.
-
If the node is still powered on, use the Power off action. This action may not be required based on the physical condition of the hardware.
[!NOTE] In the unlikely case that the Power off action doesn't work, use the baseboard management controller (BMC) web interface instead.
-
Replace the physical computer. Typically, this is done by your OEM hardware vendor.
-
Use the Repair action to add the new physical computer to the scale unit.
-
Use the privileged endpoint to check the status of virtual disk repair. With new data drives, a full storage repair job can take multiple hours depending on system load and consumed space.
-
After the repair action has finished, validate that all active alerts have been automatically closed.
- For information about replacing a hot-swappable physical disk, see Replace a disk.
- For information about replacing a non hot-swappable hardware component, see Replace a hardware component.