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: articles/databox-online/azure-stack-edge-gpu-install-update.md
+27-27Lines changed: 27 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,9 +40,9 @@ For information on what's new in this update, go to [Release notes](azure-stack-
40
40
41
41
**To apply the 2403 update, your device must be running version 2203 or later.**
42
42
43
-
- If you are not running the minimum required version, you'll see this error:
43
+
- If you aren't running the minimum required version, you see this error:
44
44
45
-
*Update package cannot be installed as its dependencies are not met.*
45
+
*Update package can't be installed as its dependencies aren't met.*
46
46
47
47
- You can update to 2303 from 2207 or later, and then install 2403.
48
48
@@ -70,27 +70,27 @@ Use the following steps to update your Azure Stack Edge version and Kubernetes v
70
70
1. Update your Kubernetes version to 2303.
71
71
1. Update both device software and Kubernetes to 2403.
72
72
73
-
If you are running 2210 or 2301, you can update both your device version and Kubernetes version directly to 2303 and then to 2403.
73
+
If you're running 2210 or 2301, you can update both your device version and Kubernetes version directly to 2303 and then to 2403.
74
74
75
-
If you are running 2303, you can update both your device version and Kubernetes version directly to 2403.
75
+
If you're running 2303, you can update both your device version and Kubernetes version directly to 2403.
76
76
77
-
In Azure portal, the process will require two clicks, the first update gets your device version to 2303 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2403.
77
+
In Azure portal, the process requires two clicks, the first update gets your device version to 2303 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2403.
78
78
79
-
From the local UI, you will have to run each update separately: update the device version to 2303, update Kubernetes version to 2210, update Kubernetes version to 2303, and then the third update gets both the device version and Kubernetes version to 2403.
79
+
From the local UI, you'll have to run each update separately: update the device version to 2303, update Kubernetes version to 2210, update Kubernetes version to 2303, and then the third update gets both the device version and Kubernetes version to 2403.
80
80
81
-
Each time you change the Kubernetes profile, you are prompted for the Kubernetes update. Go ahead and apply the update.
81
+
Each time you change the Kubernetes profile, you're prompted for the Kubernetes update. Go ahead and apply the update.
82
82
83
83
### Updates for a single-node vs two-node
84
84
85
-
The procedure to update an Azure Stack Edge is the same whether it is a single-node device or a two-node cluster. This applies both to the Azure portal or the local UI procedure.
85
+
The procedure to update an Azure Stack Edge is the same whether it's a single-node device or a two-node cluster. This applies both to the Azure portal or the local UI procedure.
86
86
87
-
-**Single node** - For a single node device, installing an update or hotfix is disruptive and will restart your device. Your device will experience a downtime for the entire duration of the update.
87
+
-**Single node** - For a single node device, installing an update or hotfix is disruptive and restarts your device. Your device will experience a downtime for the entire duration of the update.
88
88
89
89
-**Two-node** - For a two-node cluster, this is an optimized update. The two-node cluster might experience short, intermittent disruptions while the update is in progress. We recommend that you shouldn't perform any operations on the device node when update is in progress.
90
90
91
-
The Kubernetes worker VMs will go down when a node goes down. The Kubernetes master VM will fail over to the other node. Workloads will continue to run. For more information, see [Kubernetes failover scenarios for Azure Stack Edge](azure-stack-edge-gpu-kubernetes-failover-scenarios.md).
91
+
The Kubernetes worker VMs goes down when a node goes down. The Kubernetes master VM fails over to the other node. Workloads continue to run. For more information, see [Kubernetes failover scenarios for Azure Stack Edge](azure-stack-edge-gpu-kubernetes-failover-scenarios.md).
92
92
93
-
Provisioning actions such as creating shares or virtual machines are not supported during update. The update takes about 60 to 75 minutes per node to complete.
93
+
Provisioning actions such as creating shares or virtual machines aren't supported during update. The update takes about 60 to 75 minutes per node to complete.
94
94
95
95
To install updates on your device, follow these steps:
96
96
@@ -107,7 +107,7 @@ Each of these steps is described in the following sections.
107
107
108
108
2. In **Select update server type**, from the dropdown list, choose from Microsoft Update server (default) or Windows Server Update Services.
109
109
110
-
If updating from the Windows Server Update Services, specify the server URI. The server at that URI will deploy the updates on all the devices connected to this server.
110
+
If updating from the Windows Server Update Services, specify the server URI. The server at that URI deploys the updates on all the devices connected to this server.
@@ -123,10 +123,10 @@ We recommend that you install updates through the Azure portal. The device autom
123
123
> - Make sure that the device is healthy and status shows as **Your device is running fine!** before you proceed to install the updates.
124
124
125
125
126
-
Depending on the software version that you are running, install process might differ slightly.
126
+
Depending on the software version that you're running, install process might differ slightly.
127
127
128
-
- If you are updating from 2106 to 2110 or later, you will have a one-click install. See the **version 2106 and later** tab for instructions.
129
-
- If you are updating to versions prior to 2110, you will have a two-click install. See **version 2105 and earlier** tab for instructions.
128
+
- If you're updating from 2106 to 2110 or later, you'll have a one-click install. See the **version 2106 and later** tab for instructions.
129
+
- If you're updating to versions prior to 2110, you'll have a two-click install. See **version 2105 and earlier** tab for instructions.
130
130
131
131
### [version 2106 and later](#tab/version-2106-and-later)
132
132
@@ -136,7 +136,7 @@ Depending on the software version that you are running, install process might di
136
136
137
137
### [version 2105 and earlier](#tab/version-2105-and-earlier)
138
138
139
-
1. When the updates are available for your device, you see a notification in the **Overview** page of your Azure Stack Edge resource. Select the notification or from the top command bar, **Update device**. This will allow you to apply device software updates.
139
+
1. When the updates are available for your device, you see a notification in the **Overview** page of your Azure Stack Edge resource. Select the notification or from the top command bar, **Update device**. This allows you to apply device software updates.
140
140
141
141

142
142
@@ -163,7 +163,7 @@ Depending on the software version that you are running, install process might di
163
163

164
164
165
165
166
-
4. After the download is complete, the notification banner updates to indicate the completion. If you chose to download and install the updates, the installation will begin automatically.
166
+
4. After the download is complete, the notification banner updates to indicate the completion. If you chose to download and install the updates, the installation begins automatically.
167
167
168
168
If you chose to download updates only, then select the notification to open the **Device updates** blade. Select **Install**.
169
169
@@ -179,11 +179,11 @@ Depending on the software version that you are running, install process might di
179
179
180
180

181
181
182
-
7. After the restart, the device software will finish updating. After the update is complete, you can verify from the local web UI that the device software is updated. The Kubernetes software version has not been updated.
182
+
7. After the restart, the device software will finish updating. After the update is complete, you can verify from the local web UI that the device software is updated. The Kubernetes software version hasn't been updated.
183
183
184
184

185
185
186
-
8. You will see a notification banner indicating that device updates are available. Select this banner to start updating the Kubernetes software on your device.
186
+
8. You'll see a notification banner indicating that device updates are available. Select this banner to start updating the Kubernetes software on your device.
187
187
188
188

189
189
@@ -232,7 +232,7 @@ Do the following steps to download the update from the Microsoft Update Catalog.
1. In the search box of the Microsoft Update Catalog, enter the Knowledge Base (KB) number of the hotfix or terms for the update you want to download. For example, enter **Azure Stack Edge**, and then click**Search**.
235
+
1. In the search box of the Microsoft Update Catalog, enter the Knowledge Base (KB) number of the hotfix or terms for the update you want to download. For example, enter **Azure Stack Edge**, and then select**Search**.
236
236
237
237
The update listing appears as **Azure Stack Edge Update 2403**.
238
238
@@ -247,7 +247,7 @@ Do the following steps to download the update from the Microsoft Update Catalog.
247
247
| Kubernetes for Azure Stack Edge |Other workloads in your environment | Azure Stack Edge Update 2403 Kubernetes Package for Non Private MEC/Non SAP Workloads | \release~ase-2307d.3.2.2380.1632-42623-79365624-release_host_AseKubernetes_Package |
248
248
249
249
250
-
1. Select **Download**. There are two packages to download for the update. The first package will have two files for the device software updates (*SoftwareUpdatePackage.0.exe*, *SoftwareUpdatePackage.1.exe*) and the second package has two files for the Kubernetes updates (*Kubernetes_Package.0.exe* and *Kubernetes_Package.1.exe*), respectively. Download the packages to a folder on the local system. You can also copy the folder to a network share that is reachable from the device.
250
+
1. Select **Download**. There are two packages to download for the update. The first package has two files for the device software updates (*SoftwareUpdatePackage.0.exe*, *SoftwareUpdatePackage.1.exe*) and the second package has two files for the Kubernetes updates (*Kubernetes_Package.0.exe* and *Kubernetes_Package.1.exe*), respectively. Download the packages to a folder on the local system. You can also copy the folder to a network share that is reachable from the device.
251
251
252
252
253
253
### Install the update or the hotfix
@@ -261,7 +261,7 @@ Prior to the update or hotfix installation, make sure that:
261
261
262
262
This procedure takes around 20 minutes to complete. Perform the following steps to install the update or hotfix.
263
263
264
-
1. In the local web UI, go to **Maintenance** > **Software update**. Make a note of the software version that you are running.
264
+
1. In the local web UI, go to **Maintenance** > **Software update**. Make a note of the software version that you're running.
265
265
266
266
267
267
2. Provide the path to the update file. You can also browse to the update installation file if placed on a network share. Select the two software files (with *SoftwareUpdatePackage.0.exe* and *SoftwareUpdatePackage.1.exe* suffix) together.
@@ -272,16 +272,16 @@ This procedure takes around 20 minutes to complete. Perform the following steps
4. When prompted for confirmation, select **Yes** to proceed. Given the device is a single node device, after the update is applied, the device restarts and there is downtime.
275
+
4. When prompted for confirmation, select **Yes** to proceed. Given the device is a single node device, after the update is applied, the device restarts and there's downtime.
5. The update starts. After the device is successfully updated, it restarts. The local UI is not accessible in this duration.
279
+
5. The update starts. After the device is successfully updated, it restarts. The local UI isn't accessible in this duration.
280
280
281
-
6. After the restart is complete, you are taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2312**.
281
+
6. After the restart is complete, you're taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2312**.
282
282
283
283
284
-
7. You will now update the Kubernetes software version. Select the remaining two Kubernetes files together (file with the *Kubernetes_Package.0.exe* and *Kubernetes_Package.1.exe* suffix) and repeat the above steps to apply update.
284
+
7. You'll now update the Kubernetes software version. Select the remaining two Kubernetes files together (file with the *Kubernetes_Package.0.exe* and *Kubernetes_Package.1.exe* suffix) and repeat the above steps to apply update.
285
285
286
286
<!---->
287
287
@@ -291,7 +291,7 @@ This procedure takes around 20 minutes to complete. Perform the following steps
291
291
292
292
9. When prompted for confirmation, select **Yes** to proceed.
293
293
294
-
10. After the Kubernetes update is successfully installed, there is no change to the displayed software in **Maintenance** > **Software update**.
294
+
10. After the Kubernetes update is successfully installed, there's no change to the displayed software in **Maintenance** > **Software update**.
295
295
296
296

0 commit comments