Skip to content

Commit 268b5db

Browse files
author
Manika Dhiman
committed
Merge branch 'lberner-ADO-update-pro-2-network-topology' of https://github.com/louisberner/azure-docs into md-lou-databox
2 parents 1e488fe + ec0224c commit 268b5db

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/databox-online/azure-stack-edge-gpu-clustering-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: edge
99
ms.topic: conceptual
10-
ms.date: 03/20/2024
10+
ms.date: 03/21/2024
1111
ms.author: alkohli
1212
---
1313

@@ -91,13 +91,13 @@ For more information, see how to [Choose a network topology for your device node
9191

9292
On your Azure Stack Edge Pro 2 device node:
9393

94-
- **Option 1** - Port 1 and Port 2 are in different subnets. Separate virtual switches will be created. Port 3 and Port 4 connect to an external virtual switch.
94+
- **Option 1** - Port 1 and Port 2 are in different subnets. Separate virtual switches are created. Port 3 and Port 4 connect to an external virtual switch.
9595

96-
- **Option 2** - Port 1 and Port 2 are in the same subnet. A teamed virtual switch will be created. Port 3 and Port 4 connect to an external virtual switch.
96+
- **Option 2** - Port 1 and Port 2 are in the same subnet. A teamed virtual switch is created. Port 3 and Port 4 connect to an external virtual switch.
9797

98-
- **Option 3** - Port 1 and Port 2 are in separate subnets. A teamed virtual switch will be created. Port 3 and Port 4 are connected back-to-back, switchless for Port 3 and Port 4.
98+
- **Option 3** - Port 1 and Port 2 are in separate subnets. Separate virtual switches are created on Port 1 and Port 2. Port 3 and Port 4 are connected back-to-back, switchless for Port 3 and Port 4.
9999

100-
- **Option 4** - Port 1 and Port 2 are in the same subnet. A teamed virtual switch will be created. Port 3 and Port 4 are connected back-to-back, switchless for Port 3 and Port 4.
100+
- **Option 4** - Port 1 and Port 2 are in the same subnet. A teamed virtual switch is created. Port 3 and Port 4 are connected back-to-back, switchless for Port 3 and Port 4.
101101

102102
> [!NOTE]
103103
> If you run PMEC workloads, use Option 1 or Option 2.
@@ -108,8 +108,8 @@ Usage considerations on your Azure Stack Edge Pro 2 device nodes:
108108
- **Port 1 and Port 2 in separate subnets** - This is the default option. In this case, Port 1 and Port 2 have separate virtual switches and are connected to separate subnets.
109109
- **Port 1 and Port 2 in the same subnet** - In this case, Port 1 and Port 2 have a teamed virtual switch and both ports are in the same subnet.
110110
- **Using external switches for Port 3 and Port 4** - Use this option when you have high speed switches (>=10 GbE bandwidth) available for use with your device nodes and you want to allow a VM network adapter to connect to the virtual network created on Port 3 or Port 4, like a PMEC use case.
111-
- **Port 1 and Port 2 in separate subnets** - This is the default option. In this case, Port 1 and Port 2 have separate virtual switches and are connected to separate subnets.
112-
- **Port 1 and Port 2 in the same subnet** - In this case, Port 1 and Port 2 have a teamed virtual switch and both ports are in the same subnet.
111+
- **Port 1 and Port 2 in separate subnets** - This is the default option. In this case, Port 1 and Port 2 have separate virtual switches and are connected to separate subnets.
112+
- **Port 1 and Port 2 in the same subnet** - In this case, Port 1 and Port 2 have a teamed virtual switch and both ports are in the same subnet.
113113

114114
Additional considerations:
115115

0 commit comments

Comments
 (0)