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
# Customer intent: As an IT admin, I need to understand how to connect and activate Azure Stack Edge Pro so I can use it to transfer data to Azure.
@@ -63,8 +63,7 @@ In this tutorial, you learn about:
63
63
Before you configure and set up your Azure Stack Edge Pro device with GPU, make sure that:
64
64
65
65
* You've installed the physical device as detailed in [Install Azure Stack Edge Pro](azure-stack-edge-gpu-deploy-install.md).
66
-
* You've connected to the local web UI of the device as detailed in [Connect to Azure Stack Edge Pro](azure-stack-edge-gpu-deploy-connect.md)
67
-
66
+
* You've connected to the local web UI of the device as detailed in [Connect to Azure Stack Edge Pro with GPU](azure-stack-edge-gpu-deploy-connect.md).
68
67
69
68
::: zone pivot="single-node"
70
69
@@ -73,8 +72,7 @@ Before you configure and set up your Azure Stack Edge Pro device with GPU, make
73
72
1. Go to the **Get started** page.
74
73
1. In the **Set up a single node device** tile, select **Start**.
75
74
76
-

77
-
75
+
:::image type="content" source="./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/setup-type-single-node-1.png" alt-text="Screenshot of local web UI 'Get started' page for one node." lightbox="./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/setup-type-single-node-1.png":::
78
76
79
77
## Configure network
80
78
@@ -84,13 +82,13 @@ Follow these steps to configure the network for your device.
84
82
85
83
1. In the local web UI of your device, go to the **Get started** page.
86
84
87
-
2. On the **Network** tile, select **Configure**.
85
+
2. On the **Network** tile, select **Needs setup**.
88
86
89
-

87
+
:::image type="content" source="./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/network-1.png" alt-text="Screenshot of local web UI 'Network' tile for one node." lightbox="./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/network-1.png":::
90
88
91
-
On your physical device, there are six network interfaces. PORT 1 and PORT 2 are 1-Gbps network interfaces. PORT 3, PORT 4, PORT 5, and PORT 6 are all 25-Gbps network interfaces that can also serve as 10-Gbps network interfaces. PORT 1 is automatically configured as a management-only port, and PORT 2 to PORT 6 are all data ports. For a new device, the **Network** page is as shown below.
89
+
On your physical device, there are six network interfaces. Port 1 and Port 2 are 1-Gbps network interfaces. Port 3, Port 4, Port 5, and Port 6 are all 25-Gbps network interfaces that can also serve as 10-Gbps network interfaces. Port 1 is automatically configured as a management-only port, and Port 2 to Port 6 are all data ports. For a new device, the **Network** page is as shown below.
92
90
93
-

91
+
:::image type="content" source="./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/network-2a.png" alt-text="Screenshot of local web UI 'Network' page for one node." lightbox="./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/network-2a.png":::
94
92
95
93
3. To change the network settings, select a port and in the right pane that appears, modify the IP address, subnet, gateway, primary DNS, and secondary DNS.
96
94
@@ -133,7 +131,10 @@ Follow these steps to configure the network for your device.
133
131
134
132
Follow these steps to add or delete virtual switches.
135
133
136
-
1. In the local UI, go to **Advanced networking** page.
134
+
> [!NOTE]
135
+
> There is no restriction on the number of virtual switches that you can create on your device. However, you can enable compute only on one virtual switch at a time.
136
+
137
+
1. In the local UI of your device, go to the **Advanced networking** page.
137
138
1. In the **Virtual switch** section, add or delete virtual switches. Select **Add virtual switch** to create a new switch.
138
139
139
140

@@ -193,7 +194,6 @@ You can add or delete virtual networks associated with your virtual switches. To
193
194
194
195
1. Select **Next: Kubernetes >** to next configure your compute IPs for Kubernetes.
195
196
196
-
197
197
## Configure compute IPs
198
198
199
199
After the virtual switches are created, you can enable the switches for Kubernetes compute traffic.
@@ -236,7 +236,6 @@ After the virtual switches are created, you can enable the switches for Kubernet
236
236
237
237
::: zone-end
238
238
239
-
240
239
::: zone pivot="two-node"
241
240
242
241
## Configure setup type
@@ -251,11 +250,12 @@ After the virtual switches are created, you can enable the switches for Kubernet
251
250
252
251

253
252
254
-
255
253
## Configure network, topology
256
254
257
255
You'll configure network as well as network topology on both the nodes. These steps can be done in parallel. The cabling on both nodes should be identical and should conform with the network topology you choose.
258
256
257
+
For more information about selecting a network topology, see [Supported networking topologies](azure-stack-edge-gpu-clustering-overview.md?tabs=1#supported-networking-topologies).
258
+
259
259
### Configure network on first node
260
260
261
261
To configure the network for a 2-node device, follow these steps on the first node of the device:
@@ -264,11 +264,13 @@ To configure the network for a 2-node device, follow these steps on the first no
264
264
265
265

266
266
267
-
1. In the **Network** page, configure the IP addresses for your network interfaces. On your physical device, there are six network interfaces. PORT 1 and PORT 2 are 1-Gbps network interfaces. PORT 3, PORT 4, PORT 5, and PORT 6 are all 25-Gbps network interfaces that can also serve as 10-Gbps network interfaces. PORT 1 is automatically configured as a management-only port, and PORT 2 to PORT 6 are all data ports. For a new device, the **Network settings** page is as shown below.
267
+
1. In the **Network** page, configure the IP addresses for your network interfaces. On your physical device, there are six network interfaces. Port 1 and Port 2 are 1-Gbps network interfaces. Port 3, Port 4, Port 5, and Port 6 are all 25-Gbps network interfaces that can also serve as 10-Gbps network interfaces. Port 1 is automatically configured as a management-only port, and Port 2 to Port 6 are all data ports.
268
+
269
+
For a new device, the **Network settings** page is as shown below.
268
270
269
271

270
272
271
-
To change the network settings, select a port and in the right pane that appears, modify the IP address, subnet, gateway, primary DNS, and secondary DNS. You can configure your network interface as IPv4.
273
+
1. To change the network settings, select a port and in the right pane that appears, modify the IP address, subnet, gateway, primary DNS, and secondary DNS. You can configure your network interface as IPv4.
272
274
273
275

274
276
@@ -320,6 +322,7 @@ You'll now prepare the second node for clustering. You'll first need to configur
320
322
321
323

322
324
325
+
1. Configure the network on the second node in a similar way that you configured the first node.
323
326
324
327
### Configure network topology on second node
325
328
@@ -329,7 +332,6 @@ You'll now prepare the second node for clustering. You'll first need to configur
329
332
330
333
1. Select **Back to get started**.
331
334
332
-
333
335
## Get authentication token
334
336
335
337
You'll now get the authentication token that will be needed when adding this node to form a cluster. Follow these steps in the local UI of the second node:
@@ -343,12 +345,10 @@ You'll now get the authentication token that will be needed when adding this nod
343
345
344
346

345
347
346
-
347
348
## Configure cluster
348
349
349
350
To configure the cluster, you'll need to establish a cluster witness and then add a prepared node. You'll also need to configure virtual IP settings so that you can connect to a cluster as opposed to a specific node.
350
351
351
-
352
352
### Configure cluster witness
353
353
354
354
You'll now create a cluster witness. A cluster witness helps establish quorum for a two-node device if a node goes down. To learn about quorum, see [Understanding quorum](/windows-server/failover-clustering/manage-cluster-quorum#understanding-quorum).
@@ -395,8 +395,6 @@ Follow these steps to configure the cluster witness.
395
395
396
396

397
397
398
-
399
-
400
398
### Add prepared node to cluster
401
399
402
400
You'll now add the prepared node to the first node and form the cluster. Before you add the prepared node, make sure the networking on the incoming node is configured in the same way as that of this node where you initiated cluster creation.
@@ -405,7 +403,6 @@ You'll now add the prepared node to the first node and form the cluster. Before
405
403
406
404

407
405
408
-
409
406
1. In the **Add node** blade, input the following information for the incoming node:
410
407
411
408
1. Provide the serial number for the incoming node.
@@ -419,7 +416,6 @@ You'll now add the prepared node to the first node and form the cluster. Before
419
416
420
417
1. The node is now ready to join the cluster. Select **Apply**. The cluster creation takes several minutes. Once the cluster is created, the page updates to show both the nodes are added.
421
418
422
-
423
419
## Configure virtual IPs
424
420
425
421
For Azure consistent services and NFS, you'll also need to define a virtual IP that allows you to connect to a clustered device as opposed to a specific node. A virtual IP is an available IP in the cluster network and any client connecting to the cluster network on the two-node device should be able to access this IP. Azure consistent services and NFS must be on the same network.
@@ -646,4 +642,4 @@ In this tutorial, you learned about:
646
642
To learn how to set up your Azure Stack Edge Pro GPU device, see:
0 commit comments