You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/manage/add-server.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to manage capacity on your Azure Local, version 23H2 syst
4
4
ms.topic: article
5
5
author: alkohli
6
6
ms.author: alkohli
7
-
ms.date: 03/25/2025
7
+
ms.date: 04/21/2025
8
8
---
9
9
10
10
# Add a node on Azure Local
@@ -98,6 +98,9 @@ On the new node that you plan to add, follow these steps.
98
98
99
99
1. Install the operating system and required drivers on the new node that you plan to add. Follow the steps in [Install the Azure Stack HCI Operating System, version 23H2](../deploy/deployment-install-os.md).
100
100
101
+
>[!NOTE]
102
+
> For versions 2503 and later, you'll need to use the OS image of the same solution as that running on the existing cluster. To get the OS image, contact Microsoft Support or OEM Support.
103
+
101
104
2. Register the node with Arc. Follow the steps in [Register with Arc and set up permissions](../deploy/deployment-arc-register-server-permissions.md).
Copy file name to clipboardExpand all lines: azure-local/manage/repair-server.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,9 +123,10 @@ Follow these steps on the node you're trying to repair.
123
123
:::image type="content" source="./media/repair-server/delete-machine-node-resource-1.png" alt-text="Screenshot of deletion of faulty Azure Arc machine node." lightbox="./media/repair-server/delete-machine-node-resource-1.png":::
124
124
125
125
1. Install the operating system and required drivers on the node you wish to repair. Follow the steps in [Install the Azure Stack HCI Operating System, version 23H2](../deploy/deployment-install-os.md).
126
-
126
+
127
127
> [!NOTE]
128
-
> If you deployed your Azure Local instance using custom storage IPs, you must manually assign IPs to the storage network adapters after the node is repaired.
128
+
> - For versions 2503 and later, you'll need to use the OS image of the same solution as that running on the existing cluster. To get the OS image, contact Microsoft Support or OEM Support.
129
+
> - If you deployed your Azure Local instance using custom storage IPs, you must manually assign IPs to the storage network adapters after the node is repaired.
129
130
130
131
1. Register the node with Arc. Follow the steps in [Register with Arc and set up permissions](../deploy/deployment-arc-register-server-permissions.md).
The Azure Local includes multiple release trains: 2402, 2405, 2408, 2411, and 2503. Each release train includes a feature build and subsequent cumulative updates.
25
+
The Azure Local includes multiple release trains: 2408, 2411, 2503, and 2504. Each release train includes a feature build and subsequent cumulative updates.
28
26
29
27
-**Feature build**: The feature update build is the initial version of the software in a release train. Feature releases go beyond quality and security fixes, incorporating product enhancements, including updates for Azure Local services and agents.
30
28
31
29
-**Cumulative build**: A cumulative update build includes the incremental updates from the most recent feature build.
32
30
33
-
-**Baseline release**: A version that is available to be installed directly as part of a fresh deployment. Starting with 2408.0, every release (both feature and cumulative builds) is a baseline release.
34
-
35
31
The following diagram illustrates the release trains, their associated feature builds, and update paths.
36
32
37
33
:::image type="content" source="./media/release-information-23h2/release-trains-supported-update-paths.png" alt-text="Diagram illustrating Azure Local release trains with supported update paths."lightbox="./media/release-information-23h2/release-trains-supported-update-paths.png":::
38
34
39
35
#### Move to the next release train
40
36
41
-
Follow these guidelines to move to the next release train:
37
+
Follow these guidelines to skip releases with the same release train as you move to the next release train:
42
38
43
39
- Update the existing deployment to a build that allows you to move to the next release train. The following table provides examples of how to move between release trains:
| From 2411 to 2503 | 2411 --> 2411.2 --> 2411.3 --> 2503 |
45
+
46
+
<!-- Update the 2503 train to 2504 or create a new deployment.-->
50
47
51
48
#### Move within the same release train
52
49
53
-
Follow these guidelines to move within the same release train:
50
+
Follow these guidelines to update to each release within your current release train:
54
51
55
-
- Within your release train, you can update to the latest update build anytime. For example, if you're running the 2405 feature build, you can update to any of the 2405 cumulative update builds, such as 2405.1, 2405.2, or 2405.3.
52
+
- Within your release train, you can update to the latest update build anytime. For example, if you're running the 2411 feature build, you can update to any of the 2411 cumulative update builds, such as 2411.1, 2411.2, or 2411.3.
56
53
57
-
- To keep your Azure Local instance in a supported state, you have up to six months to install updates. For example, if you're running the 2405 feature build, update to a later build within six months.
54
+
| Timeframe for 2411 release train | Update path |
- To keep your Azure Local instance in a supported state, you have up to six months to install updates. For example, if you're running the 2408 feature build, update to a later build within six months.
58
61
59
62
## Azure Local release information summary
60
63
61
64
### Supported versions of Azure Local
62
65
63
-
The following table summarizes the release information for Azure Local across all supported versions. All dates are listed in ISO 8601 format: *YYYY-MM-DD*
66
+
The following tables summarize the release information for Azure Local across all supported versions. All dates are listed in ISO 8601 format: *YYYY-MM-DD*.
67
+
68
+
<!--Starting in 2504, we offer two releases. One release provides the path to upgrade from 2503 to 2504. The other release supports a new deployment of 2504.-->
0 commit comments