Skip to content

Commit ab9ebbd

Browse files
committed
resolve the conflict
1 parent c871e9a commit ab9ebbd

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

azure-local/manage/sdn-express.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,9 @@ ms.reviewer: anirbanpaul
1212

1313
> Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022, Windows Server 2019, Windows Server 2016
1414
15-
<<<<<<< HEAD:azure-local/manage/sdn-express.md
1615
[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
1716

1817
In this topic, you deploy an end-to-end Software Defined Network (SDN) infrastructure using SDN Express PowerShell scripts. The infrastructure includes a highly available (HA) Network Controller (NC), and optionally, a highly available Software Load Balancer (SLB), and a highly available Gateway (GW). The scripts support a phased deployment, where you can deploy just the Network Controller component to achieve a core set of functionality with minimal network requirements.
19-
=======
20-
This article describes how to deploy an end-to-end Software Defined Network (SDN) infrastructure using SDN Express PowerShell scripts. The infrastructure includes a highly available (HA) Network Controller (NC), and optionally, a highly available Software Load Balancer (SLB), and a highly available Gateway (GW). The scripts support a phased deployment, in which you can deploy just the Network Controller component to achieve a core set of functionality with minimal network requirements.
21-
>>>>>>> main:azure-stack/hci/manage/sdn-express.md
2218

2319
You can also deploy an SDN infrastructure using Windows Admin Center or using System Center Virtual Machine Manager (VMM). For more information, see [Create a cluster - Step 5: SDN](../deploy/create-cluster.md#step-5-sdn-optional) and [Manage SDN resources in the VMM fabric](/system-center/vmm/network-sdn).
2420

0 commit comments

Comments
 (0)