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-stack/hci/upgrade/install-enable-network-atc.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,7 @@ author: ronmiab
5
5
ms.author: robess
6
6
ms.topic: how-to
7
7
ms.reviewer: alkohli
8
-
ms.lastreviewed: 08/13/2024
9
-
ms.date: 08/13/2024
8
+
ms.date: 08/14/2024
10
9
#Customer intent: As a Senior Content Developer, I want to provide customers with content and steps to help them successfully install and enable Network ATC on their existing Azure Stack HCI, version 22H2 cluster.
11
10
---
12
11
@@ -16,6 +15,9 @@ ms.date: 08/13/2024
16
15
17
16
This article provides information on how to install and enable Network ATC on your existing Azure Stack HCI, version 22H2 cluster. Once Network ATC is enabled you can take advantage of several benefits and utilize this configuration across all new deployments.
18
17
18
+
> [!IMPORTANT]
19
+
> Network ATC must be installed and enabled on your existing Azure Stack HCI, version 22H2 cluster before you can upgrade to Azure Stack HCI, version 23H2. If Network ATC is already enabled on your existing cluster, you can skip this step.
20
+
19
21
## About Network ATC
20
22
21
23
Network ATC stores information in the cluster database, which is then replicated to other nodes in the cluster. From the initial node, other nodes in the cluster see the change in the cluster database and create a new intent. Here, we set up the cluster to receive a new intent. Additionally, we control the rollout of the new intent by stopping or disabling the Network ATC service on nodes that have virtual machines (VM) on them.
Copy file name to clipboardExpand all lines: azure-stack/hci/upgrade/install-solution-upgrade.md
+48-8Lines changed: 48 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Install solution upgrade on your Azure Stack HCI cluster
3
3
description: Learn about how to install upgrade on your Azure Stack HCI cluster.
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 08/13/2024
6
+
ms.date: 08/14/2024
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
ms.subservice: azure-stack-hci
@@ -24,47 +24,67 @@ Before you install the solution upgrade, make sure that you:
24
24
25
25
- Validate the cluster using the Environment Checker as per the instructions in [Assess solution upgrade readiness](./validate-solution-upgrade-readiness.md#run-the-validation).
26
26
- Verify that latest `AzureEdgeLifecycleManager` extension on each cluster node is installed as per the instructions in [Check the Azure Arc extension](./validate-solution-upgrade-readiness.md#remediation-9-check-the-azure-arc-lifecycle-extension).
27
+
28
+
:::image type="content" source="media/install-solution-upgrade/verify-lcmextension-installed.png" alt-text="Screenshot of Extensions page showing AzureEdgeLifeCycleManager extension install on Azure Stack HCI node." lightbox="./media/install-solution-upgrade/verify-lcmextension-installed.png":::
29
+
27
30
- Have an Active Directory user credential that's a member of the local Administrator group. Work with your Active Directory administrator to obtain this credential.
28
31
- Have IPv4 network range with six, contiguous IP addresses available for new Azure Arc services. Work with your network administrator to ensure that the IP addresses aren't in use and meet the outbound connectivity requirement.
29
32
- Have Azure subscription permissions for [Azure Stack HCI Administrator and Reader](../manage/assign-vm-rbac-roles.md#about-builtin-rbac-roles).
30
33
34
+
:::image type="content" source="media/install-solution-upgrade/verify-subscription-permissions-roles.png" alt-text="Screenshot of subscription with permissions assigned to required roles for upgrade." lightbox="./media/install-solution-upgrade/verify-subscription-permissions-roles.png":::
35
+
36
+
31
37
## Install the solution upgrade via Azure portal
32
38
39
+
You install the solution upgrade via the Azure portal.
40
+
41
+
1. Go to your Azure Stack HCI cluster resource in the portal.
42
+
1. In the **Overview** page, you can see a banner indicating that a solution upgrade is available. Select the **Upgrade** link in the banner.
43
+
44
+
:::image type="content" source="./media/install-solution-upgrade/upgrade-banner.png" alt-text="Screenshot of Azure Stack HCI Overview page with upgrade available banner." lightbox="./media/install-solution-upgrade/upgrade-banner.png":::
45
+
46
+
33
47
### Basics tab
34
48
35
49
On the **Basics** tab, specify the following information:
36
50
37
-
1.Specify whether you want to create a new key vault to store the credentials, or if you want to select an existing key vault. Only vaults in the same resource group are shown.
51
+
1.Select an existing key vault from vaults in the resource group. Sharing an existing key vault can have security implications. If you don't have a key vault, you can create a new one to store the credentials.
38
52
39
-
> [!NOTE]
40
-
> We recommend that you select a new key vault as sharing an existing key vauilt may have security implications.
53
+
1. Select **Create a new key vault**.
54
+
1. Provide a **Name** for the new key vault. The name should be 3 to 24 characters long and contain only letters, numbers, and hyphens. Two consecutive hyphens are not allowed.
55
+
56
+
:::image type="content" source="./media/install-solution-upgrade/create-new-key-vault.png" alt-text="Screenshot of Create key vault page." lightbox="./media/install-solution-upgrade/create-new-key-vault.png":::
41
57
42
58
1. Specify the deployment account credential. This credential is from your Active Directory for a principal that is a member of the local Administrator group on each cluster node.
43
59
44
60
> [!NOTE]
45
61
> The user can't be Administrator and can't use format `domain\username`.
46
62
47
-
1.Specify the custom location name used for Azure Arc services.
63
+
1.Accept default name or specify the custom location name used for Azure Arc services.
48
64
49
-
1. Specify network IP address information. A total of six IP addresses is required, defined by an IP address range. IP addresses in the range must:
65
+
1. Specify network IP address information. A total of six, contiguous IP addresses is required, defined by an IP address range. IP addresses in the range must:
On the **Validation** tab, the operation automatically creates Azure resources like the cluster and the service principal, and also configures permissions and the audit login.
60
78
61
-
1. Select **Start validation** to begin the operation. To learn more about validation, see [Validate solution upgrade readiness of your Azure Stack HCI cluster](./validate-solution-upgrade-readiness.md).
79
+
1. Select **Start validation** to begin the operation. This operation involves running the Environment Checker to check external connectivity and storage requirements and that the environment is ready for solution upgrade. To learn more about validation, see [Validate solution upgrade readiness of your Azure Stack HCI cluster](./validate-solution-upgrade-readiness.md).
0 commit comments