Skip to content

Commit 9cb2cb6

Browse files
authored
Sync release-hotfixes with main
Sync release-hotfixes with main
2 parents 425af68 + 75e75d2 commit 9cb2cb6

File tree

4 files changed

+22
-21
lines changed

4 files changed

+22
-21
lines changed

AKS-Hybrid/deploy-gpu-node-pool.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Install the Azure Stack HCI, version 23H2 operating system locally on each serve
7373
On each host machine, navigate to **Control Panel > Add or Remove programs**, uninstall the NVIDIA host driver, then reboot the machine. After the machine reboots, confirm that the driver was successfully uninstalled. Open an elevated PowerShell terminal and run the following command:
7474

7575
```powershell
76-
Get-PnpDevice | select status, class, friendlyname, instanceid | findstr /i /c:"3d video"
76+
Get-PnpDevice | select status, class, friendlyname, instanceid | where {$_.friendlyname -eq "3D Video Controller"}
7777
```
7878

7979
You should see the GPU devices appear in an error state as shown in this example output:
@@ -99,7 +99,7 @@ Dismount-VMHostAssignableDevice -LocationPath $lp1 -Force
9999
To confirm that the GPUs were correctly dismounted from the host, run the following command. You should put GPUs in an `Unknown` state:
100100

101101
```powershell
102-
Get-PnpDevice | select status, class, friendlyname, instanceid | findstr /i /c:"3d video"
102+
Get-PnpDevice | select status, class, friendlyname, instanceid | where {$_.friendlyname -eq "3D Video Controller"}
103103
```
104104

105105
```output
@@ -131,7 +131,7 @@ pnputil /scan-devices
131131
After you install the mitigation driver, the GPUs are listed in the **OK** state under **Nvidia A2_base - Dismounted**:
132132

133133
```powershell
134-
Get-PnpDevice | select status, class, friendlyname, instanceid | findstr /i /c:"nvidia"
134+
Get-PnpDevice | select status, class, friendlyname, instanceid | where {$_.friendlyname -match "Nvidia"}"
135135
```
136136

137137
```output

azure-stack/hci/concepts/network-atc-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Network ATC overview
33
description: This article introduces Network ATC for Azure Stack HCI and Windows Server.
44
author: parammahajan5
55
ms.topic: overview
6-
ms.date: 10/15/2024
6+
ms.date: 10/25/2024
77
ms.author: jgerend
88
ms.reviewer: JasonGerend
99
zone_pivot_groups: windows-os
@@ -13,7 +13,7 @@ zone_pivot_groups: windows-os
1313

1414
:::zone pivot="azure-stack-hci"
1515

16-
[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2.md)]
16+
[!INCLUDE [hci-applies-to-23h2-22h2](../../includes/hci-applies-to-23h2-22h2.md)]
1717

1818
Deployment and operation of Azure Stack HCI networking can be a complex and error-prone process. Due to the configuration flexibility provided with the host networking stack, there are many moving parts that can be easily misconfigured or overlooked. Staying up to date with the latest best practices is also a challenge as improvements are continuously made to the underlying technologies. Additionally, configuration consistency across HCI cluster nodes is important as it leads to a more reliable experience. Network ATC is the complete product name and not an acronym.
1919

azure-stack/hci/deploy/sdn-express-23h2.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy an SDN infrastructure using SDN Express for Azure Stack HCI, versi
33
description: Learn to deploy an SDN infrastructure using SDN Express for Azure Stack HCI, version 23h2.
44
author: alkohli
55
ms.topic: how-to
6-
ms.date: 05/29/2024
6+
ms.date: 10/28/2024
77
ms.author: alkohli
88
ms.reviewer: anirbanpaul
99
---
@@ -47,24 +47,24 @@ The following requirements must be met for a successful SDN deployment:
4747

4848
[!INCLUDE [download-vhdx](../../includes/hci-download-vhdx.md)]
4949

50-
## Download the GitHub repository
50+
## Install the SDN Express PowerShell module
5151

52-
The SDN Express script files live in GitHub. The first step is to get the necessary files and folders onto your deployment computer.
52+
Run the following command to install the latest version of the SDN Express PowerShell module on the machine where you want to run the SDN installation:
5353

54-
1. Go to the [Microsoft SDN GitHub](https://github.com/microsoft/SDN) repository.
54+
```powershell
55+
Install-Module -Name SDNExpress
56+
```
5557

56-
1. In the repository, expand the **Code** drop-down list, and then choose either **Clone** or **Download ZIP** to download the SDN files to your designated deployment computer.
58+
The files automatically install in the default PowerShell module directory: `C:\Program Files\WindowsPowerShell\Modules\SdnExpress\`.
5759

58-
> [!NOTE]
59-
> The designated deployment computer must be running Windows Server 2016 or later.
60-
61-
1. Extract the ZIP file and copy the `SDNExpress` folder to your deployment computer's `C:\` folder.
60+
> [!NOTE]
61+
> The SDN Express script files are no longer available on GitHub.
6262
6363
## Edit the configuration file
6464

6565
The PowerShell `MultiNodeSampleConfig.psd1` configuration data file contains all the parameters and settings that are needed for the SDN Express script as input for the various parameters and configuration settings. This file has specific information about what needs to be filled out based on whether you're deploying only the network controller component, or the software load balancer and gateway components as well. For detailed information, see [Plan a Software Defined Network infrastructure](../concepts/plan-software-defined-networking-infrastructure.md) article.
6666

67-
Navigate to the `C:\SDNExpress\scripts` folder and open the `MultiNodeSampleConfig.psd1` file in your favorite text editor. Change specific parameter values to fit your infrastructure and deployment:
67+
Navigate to the `C:\Program Files\WindowsPowerShell\Modules\SdnExpress\` folder and open the `MultiNodeSampleConfig.psd1` file in your favorite text editor. Change specific parameter values to fit your infrastructure and deployment:
6868

6969
### General settings and parameters
7070

@@ -185,14 +185,14 @@ The SDN Express script deploys your specified SDN infrastructure. When the scrip
185185
1. Run the following command from a user account with administrative credentials for the cluster host servers:
186186

187187
```powershell
188-
SDNExpress\scripts\SDNExpress.ps1 -ConfigurationDataFile MultiNodeSampleConfig.psd1 -Verbose
188+
.\SDNExpress.ps1 -ConfigurationDataFile MultiNodeSampleConfig.psd1 -Verbose
189189
```
190190
191191
1. After the NC VMs are created, configure dynamic DNS updates for the Network Controller cluster name on the DNS server. For more information, see [Dynamic DNS updates](../concepts/network-controller.md#dynamic-dns-updates).
192192
193193
## Configuration sample files
194194
195-
The following configuration sample files for deploying SDN are available on the [Microsoft SDN GitHub](https://github.com/microsoft/SDN/tree/master/SDNExpress/scripts) repository:
195+
The following configuration sample files for deploying SDN are available in the location where the PowerShell module is installed (`C:\Program Files\WindowsPowerShell\Modules\SdnExpress\`):
196196
197197
- **Traditional VLAN networks.psd1** - Deploy Network Controller for managing network policies like microsegmentation and Quality of Service on traditional VLAN Networks.
198198
@@ -204,5 +204,4 @@ The following configuration sample files for deploying SDN are available on the
204204
205205
## Next steps
206206
207-
- [Manage VMs](../manage/vm.md)
208-
207+
- [Manage VMs](../manage/vm.md)

azure-stack/hci/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -588,6 +588,10 @@ items:
588588
items:
589589
- name: Azure Stack HCI observability
590590
href: concepts/observability.md
591+
- name: Host networking
592+
items:
593+
- name: Network ATC overview
594+
href: concepts/network-atc-overview.md?pivots=azure-stack-hci
591595
- name: SDN
592596
items:
593597
- name: SDN technical reference
@@ -806,8 +810,6 @@ items:
806810
href: concepts/nested-virtualization.md
807811
- name: Host networking
808812
items:
809-
- name: Network ATC overview
810-
href: concepts/network-atc-overview.md?pivots=azure-stack-hci
811813
- name: Network HUD overview
812814
href: concepts/network-hud-overview.md
813815
- name: Software Defined Networking (SDN)

0 commit comments

Comments
 (0)