Skip to content

Commit bea3a1a

Browse files
author
Manika Dhiman
committed
Update for Pro 2 network options.
2 parents fad2373 + 905023a commit bea3a1a

File tree

2 files changed

+48
-52
lines changed

2 files changed

+48
-52
lines changed

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

Lines changed: 46 additions & 50 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: 10/18/2023
10+
ms.date: 03/20/2024
1111
ms.author: alkohli
1212
---
1313

@@ -56,15 +56,15 @@ The infrastructure cluster on your device provides persistent storage and is sho
5656
The Kubernetes cluster allows for application orchestration whereas the infrastructure cluster provides persistent storage.
5757

5858

59-
## Supported networking topologies
59+
## Supported network topologies
6060

61-
Based on the use-case and workloads, you can select how the two Azure Stack Edge device nodes will be connected. The networking topologies available will differ depending on whether you use an Azure Stack Edge Pro GPU device or an Azure Stack Edge Pro 2 device.
61+
Based on the use case and workloads, you can select how the two Azure Stack Edge device nodes will be connected. Network topologies will differ depending on whether you use an Azure Stack Edge Pro GPU device or an Azure Stack Edge Pro 2 device.
6262

63-
The supported network topologies for each of the device types are described here.
63+
At a high level, supported network topologies for each of the device types are described here.
6464

6565
### [Azure Stack Edge Pro GPU](#tab/1)
6666

67-
On your Azure Stack Edge Pro GPU device node:
67+
On your Azure Stack Edge Pro GPU device node:
6868

6969
- Port 2 is used for management traffic.
7070
- Port 3 and Port 4 are used for storage and cluster traffic. This traffic includes that needed for storage mirroring and Azure Stack Edge cluster heartbeat traffic that is required for the cluster to be online.
@@ -73,70 +73,68 @@ The following network topologies are available:
7373

7474
![Available network topologies](media/azure-stack-edge-gpu-clustering-overview/azure-stack-edge-network-topologies.png)
7575

76-
1. **Switchless** - Use this option when you don't have high speed switches available in the environment for storage and cluster traffic.
76+
- **Option 1 - Switchless** - Use this option when you don't have high speed switches available in the environment for storage and cluster traffic.
7777

7878
In this option, Port 3 and Port 4 are connected back-to-back without a switch. These ports are dedicated to storage and Azure Stack Edge cluster traffic and aren't available for workload traffic. <!--For example, these ports can't be enabled for compute--> Optionally you can also provide IP addresses for these ports.
7979

80-
81-
1. **Using switches and NIC teaming** - Use this option when you have high speed switches available for use with your device nodes for storage and cluster traffic.
80+
- **Option 2 - Use switches and NIC teaming** - Use this option when you have high speed switches available for use with your device nodes for storage and cluster traffic.
8281

8382
Each of ports 3 and 4 of the two nodes of your device are connected via an external switch. The Port 3 and Port 4 are teamed on each node and a virtual switch and two virtual NICs are created that allow for port-level redundancy for storage and cluster traffic. These ports can be used for workload traffic as well.
8483

85-
86-
1. **Using switches and without NIC teaming** - Use this option when you need an extra dedicated port for workload traffic and port-level redundancy isn’t required for storage and cluster traffic.
84+
- **Option 3 - Use switches without NIC teaming** - Use this option when you need an extra dedicated port for workload traffic and port-level redundancy isn’t required for storage and cluster traffic.
8785

8886
Port 3 on each node is connected via an external switch. If Port 3 fails, the cluster may go offline. Separate virtual switches are created on Port 3 and Port 4.
8987

9088
For more information, see how to [Choose a network topology for your device node](azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md#configure-network).
9189

9290
### [Azure Stack Edge Pro 2](#tab/2)
9391

94-
On your Azure Stack Edge Pro 2 device node:
95-
96-
- Port 1 is used for initial configuration. Port 1 is then reconfigured and assigned an IP address that may or may not be in the same subnet as the Port 2. Port 1 and Port 2 are used for clustering, storage and management traffic.
97-
- Port 3 and Port 4 may be used for are used for Private Multi-Access Edge Computing workload deployment or for storage traffic.
98-
99-
The following network topologies are available:
100-
101-
- **Switchless** - Use this option when you don't have high speed switches available in the environment for storage and cluster traffic. There are further sub-options:
92+
On your Azure Stack Edge Pro 2 device node:
10293

103-
- **With 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.
104-
105-
- **With Port 1 and Port 2 in same subnets** - In this case, Port 1 and Port 2 have a teamed virtual switch and both the ports are in the same subnet.
106-
107-
In each case, Port 3 and Port 4 are connected back-to-back directly without a switch. These ports are dedicated to storage and Azure Stack Edge cluster traffic and aren't available for workload traffic.
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.
95+
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.
10897

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.
10999

110-
- **Using external switches** - Use this option when you have high speed switches (10 GbE switches) available for use with your device nodes for storage and cluster traffic. There are further sub-options:
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.
111101

112-
- **With 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.
113-
114-
- **With Port 1 and Port 2 in same subnets** - In this case, Port 1 and Port 2 have a teamed virtual switch and both the ports are in the same subnet.
102+
> [!NOTE]
103+
> If you run PMEC workloads, use Option 1 or Option 2.
115104
116-
In each case, Port 3 and Port 4 are reserved for Private Multi-Access Edge Computing workload deployments.
105+
Usage considerations on your Azure Stack Edge Pro 2 device nodes:
117106

118-
The pros and cons for each of the above supported topologies can be summarized as follows:
107+
- **Switchless for Port 3 and Port 4** - Use this option when you don't have high speed switches available in the environment, or you want to dedicate Port 3 and Port 4 for storage and cluster traffic.
108+
- **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.
109+
- **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.
110+
- **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.
119113

120-
| Local web UI option | Advantages | Disadvantages |
121-
|----------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------|
122-
| Switchless, Port 1 and Port 2 in separate subnet, separate virtual switches | Redundant paths for management and storage traffic. | Clients need to reconnect if Port 1 or Port 2 fails. |
123-
| | No single point of failure within the device. | |
124-
| | Lots of bandwidth for storage and cluster traffic across the nodes. | |
125-
| | Can be deployed with Port 1 and Port 2 in different subnets. | |
126-
| | | |
127-
| Switchless, Port 1 and Port 2 in the same subnet, teamed virtual switch | Redundant paths for management and storage traffic. | Teamed virtual switch is a single point of failure in the software. |
128-
| | Lots of bandwidth for storage and cluster traffic across the nodes. | |
129-
| | Higher fault tolerance. | |
130-
| | | |
131-
| Using external switch, Port 1 and Port 2 in separate subnet, separate virtual switches | Two independent virtual switches and network paths provide redundancy. | Clients need to reconnect if Port 1 or Port 2 fails. |
132-
| | No single point of failure with the device. | |
133-
| | Port 1 and Port 2 can be connected to different subnets. | |
134-
| | | |
135-
| Using external switch, Port 1 and Port 2 in same subnet, teamed virtual switch | Load balancing. | Teamed switch is a single point of failure in software. |
136-
| | Higher fault toelerance. | Can't be deployed in an environment with different subnets. |
137-
| | Two independent, redundant paths between the nodes. | |
138-
| | Clients do not need to reconnect. | |
114+
Additional considerations:
139115

116+
- Port 1 is used for initial configuration. Port 1 is then reconfigured and assigned an IP address that may or may not be in the same subnet as Port 2.
117+
- If you select the **Using external switches** option, Port 1 and Port 2 are used for storage in both teaming and non-teaming modes.
118+
- When using the **Switchless** option, Port 3 and Port 4 are connected back-to-back directly, without a switch. These ports are dedicated to storage and Azure Stack Edge cluster traffic. Port 3 and Port 4 aren't available for workload traffic.
119+
120+
Pros and cons for supported topologies are summarized as follows:
121+
122+
| Local web UI option | Advantages | Disadvantages |
123+
|---------------------|------------|---------------|
124+
| Port 3 and Port 4 are Switchless, Port 1 and Port 2 in separate subnet, separate virtual switches. | Redundant paths for management and storage traffic. | Clients must reconnect if Port 1 or Port 2 fails. |
125+
| | No single point of failure within the device. | VM workload can't leverage Port 3 or Port 4 to connect to network endpoints other than a peer Azure Stack Edge node. This is why PMEC workloads can't use this option. |
126+
| | Lots of bandwidth for storage and cluster traffic across nodes. | |
127+
| | Can be deployed with Port 1 and Port 2 in different subnets. | |
128+
| Port 3 and Port 4 are Switchless, Port 1 and Port 2 are in the same subnet, teamed virtual switch. | Redundant paths for management and storage traffic. | VM workload can't leverage Port 3 or Port 4 to connect to network endpoints other than a peer Azure Stack Edge node. This is why PMEC workloads can't use this option. |
129+
| | Lots of bandwidth for storage and cluster traffic across nodes. | |
130+
| | Higher fault tolerance. | |
131+
| Port 3 and Port 4 use an external switch with >=10Gbps link bandwidth, Port 1 and Port 2 in separate subnets, separate virtual switches | Two independent virtual switches and network paths provide redundancy. | Clients must reconnect if Port 1 or Port 2 fails. |
132+
| | No single point of failure with the device. | |
133+
| | Port 1 and Port 2 can be connected to different subnets. | |
134+
| Port 3 and Port 4 use an external switch with >=10Gbps link bandwidth, Port 1 and Port 2 in the same subnet, teamed virtual switch. | Load balancing. | |
135+
| | Higher fault tolerance. | Can't be deployed in an environment with different subnets. |
136+
| | Two independent, redundant paths between nodes. | |
137+
| | Clients do not need to reconnect. | |
140138

141139
---
142140

@@ -218,5 +216,3 @@ If you deploy an Azure Stack Edge two-node cluster, each node is billed separate
218216
- Learn about [Cluster witness for your Azure Stack Edge](azure-stack-edge-gpu-cluster-witness-overview.md).
219217
- See [Kubernetes for your Azure Stack Edge](azure-stack-edge-gpu-kubernetes-overview.md)
220218
- Understand [Cluster failover scenarios](azure-stack-edge-gpu-cluster-failover-scenarios.md)
221-
222-

0 commit comments

Comments
 (0)