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
Copy file name to clipboardExpand all lines: articles/databox-online/azure-stack-edge-gpu-connect-powershell-interface.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ If the compute role is configured on your device, you can also get the compute l
96
96
97
97
After you have formed and configured a cluster and you have created new virtual switches, you can add or delete virtual networks associated with your virtual switches. For detailed steps, see [Configure virtual switches](azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md?pivots=two-node#configure-virtual-switches-1).
98
98
99
-
After virtual switches are created, you can enable the switches for Kubernetes compute traffic to specify a Kubernets workload profile. To do so using the local UI, use the steps in [Configure compute IPS](azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md?pivots=two-node#configure-compute-ips-1). To do so using PowerShell, use the following steps:
99
+
After virtual switches are created, you can enable the switches for Kubernetes compute traffic to specify a Kubernetes workload profile. To do so using the local UI, use the steps in [Configure compute IPS](azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md?pivots=two-node#configure-compute-ips-1). To do so using PowerShell, use the following steps:
100
100
101
101
1. [Connect to the PowerShell interface](#connect-to-the-powershell-interface).
102
102
2. Use the `Get-HcsApplianceInfo` cmdlet to get current `KubernetesPlatform` and `KubernetesWorkloadProfile` settings for your device.
Copy file name to clipboardExpand all lines: articles/databox-online/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ Follow these steps to add or delete virtual switches.
163
163
164
164
When you create a virtual switch, the MTU column is populated with its MTU value.
165
165
166
-
166
+
167
167
168
168
1. The configuration will take a few minutes to apply and once the virtual switch is created, the list of virtual switches updates to reflect the newly created switch. You can see that the specified virtual switch is created and enabled for compute.
169
169
@@ -228,7 +228,7 @@ After the virtual switches are created, you can enable the switches for Kubernet
228
228
229
229
1. Select **Apply**.
230
230
231
-
231
+
232
232
233
233
1. The configuration takes a couple minutes to apply and you may need to refresh the browser.
234
234
@@ -298,7 +298,7 @@ To configure the network for a 2-node device, follow these steps on the first no
298
298
-**Use switches and NIC teaming**. Use this option when you need port level redundancy through teaming. NIC Teaming allows you to group two physical ports on the device node, Port 3 and Port 4 in this case, into two software-based virtual network interfaces. These teamed network interfaces provide fast performance and fault tolerance in the event of a network interface failure. For more information, see [NIC teaming on Windows Server](/windows-server/networking/windows-server-supported-networking-scenarios#bkmk_nicteam).
299
299
-**Use switches without NIC teaming**. Use this option if you need an extra port for workload traffic and port level redundancy is not required.
300
300
301
-
301
+
302
302
303
303
1. Make sure that your node is cabled as per the selected topology.
304
304
1. Select **Apply**.
@@ -494,7 +494,7 @@ After the cluster is formed and configured, you can now create new virtual switc
494
494
495
495
When you create a virtual switch, the MTU column is populated with its MTU value.
496
496
497
-
497
+
498
498
499
499
1. The configuration will take a few minutes to apply and once the virtual switch is created, the list of virtual switches updates to reflect the newly created switch. You can see that the specified virtual switch is created and enabled for compute.
Copy file name to clipboardExpand all lines: articles/databox-online/azure-stack-edge-pro-2-deploy-configure-network-compute-web-proxy.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,15 +150,15 @@ Follow these steps to add or delete virtual switches.
150
150
151
151
If a virtual network interface is created on the virtual switch, the interface will use the specified MTU setting. If this virtual switch is enabled for compute, the Azure Kubernetes Service VMs and container network interfaces (CNIs) will use the specified MTU as well.
152
152
153
-
153
+
154
154
155
155
When you create a virtual switch, the MTU column is populated with its MTU value.
156
156
157
-
157
+
158
158
159
159
1. The configuration will take a few minutes to apply and once the virtual switch is created, the list of virtual switches updates to reflect the newly created switch. You can see that the specified virtual switch is created and enabled for compute.
160
160
161
-
161
+
162
162
163
163
1. You can create more than one switch by following the steps described earlier.
164
164
@@ -219,7 +219,7 @@ After the virtual switches are created, you can enable the switches for Kubernet
219
219
220
220
1. Select **Apply**.
221
221
222
-
222
+
223
223
224
224
1. The configuration takes a couple minutes to apply and you may need to refresh the browser.
225
225
@@ -296,19 +296,19 @@ To configure the network for a 2-node device, follow these steps on the first no
296
296
-**Use switches and NIC teaming**. Use this option when you need port level redundancy through teaming. NIC Teaming allows you to group two physical ports on the device node, Port 3 and Port 4 in this case, into two software-based virtual network interfaces. These teamed network interfaces provide fast performance and fault tolerance in the event of a network interface failure. For more information, see [NIC teaming on Windows Server](/windows-server/networking/windows-server-supported-networking-scenarios#bkmk_nicteam).
297
297
-**Use switches without NIC teaming**. Use this option if you need an extra port for workload traffic and port level redundancy is not required.
298
298
299
-
299
+
300
300
301
301
1. Make sure that your node is cabled as per the selected topology.
302
302
1. Select **Apply**.
303
303
1. You'll see a **Confirm network setting** dialog. This dialog reminds you to make sure that your node is cabled as per the network topology you selected. Once you choose the network cluster topology, you can't change this topology without a device reset. Select **Yes** to confirm the network topology.
304
304
305
-
305
+
306
306
307
307
The network topology setting takes a few minutes to apply and you see a notification when the settings are successfully applied.
308
308
309
309
1. Once the network topology is applied, the **Network** page updates. For example, if you selected network topology that uses switches and NIC teaming, you will see that on a device node, a virtual switch **vSwitch1** is created at Port 2 and another virtual switch, **vSwitch2** is created on Port 3 and Port 4. Port 3 and Port 4 are teamed and then on the teamed network interface, two virtual network interfaces are created, **vPort3** and **vPort4**. The same is true for the second device node. The teamed network interfaces are then connected via switches.
310
310
311
-
311
+
312
312
313
313
You'll now configure the network and the network topology of the second node.
314
314
@@ -326,7 +326,7 @@ You'll now prepare the second node for clustering. You'll first need to configur
326
326
327
327
1. Make sure that the second node is cabled as per the topology you selected for the first node. In the **Advanced networking** page, choose and **Apply** the same topology that you selected for the first node.
328
328
329
-
329
+
330
330
331
331
1. Select **Back to get started**.
332
332
@@ -408,7 +408,7 @@ You'll now add the prepared node to the first node and form the cluster. Before
408
408
409
409
1. Select **Validate & add**. This step takes a few minutes.
410
410
411
-
411
+
412
412
413
413
You see a notification when the node is successfully validated.
414
414
@@ -424,7 +424,7 @@ For Azure Consistent Services, follow these steps to configure virtual IP.
424
424
425
425
1. In the local UI on the **Cluster** page, under the **Virtual IP settings** section, select **Azure Consistent Services**.
426
426
427
-
427
+
428
428
429
429
1. In the **Virtual IP settings** blade, input the following.
430
430
@@ -442,7 +442,7 @@ For clients connecting via NFS protocol to the two-node device, follow these ste
442
442
443
443
1. In the local UI on the **Cluster** page, under the **Virtual IP settings** section, select **Network File System**.
444
444
445
-
445
+
446
446
447
447
1. In the **Virtual IP settings** blade, input the following.
448
448
@@ -466,7 +466,7 @@ After the cluster is formed and configured, you can now create new virtual switc
466
466
1. In the local UI, go to **Advanced networking** page.
467
467
1. In the **Virtual switch** section, add or delete virtual switches. Select **Add virtual switch** to create a new switch.
468
468
469
-
469
+
470
470
471
471
1. In the **Network settings** blade, if using a new switch, provide the following:
472
472
@@ -488,15 +488,15 @@ After the cluster is formed and configured, you can now create new virtual switc
488
488
489
489
If a virtual network interface is created on the virtual switch, the interface will use the specified MTU setting. If this virtual switch is enabled for compute, the Azure Kubernetes Service VMs and container network interfaces (CNIs) will use the specified MTU as well.
490
490
491
-
491
+
492
492
493
493
When you create a virtual switch, the MTU column is populated with its MTU value.
494
494
495
-
495
+
496
496
497
497
1. The configuration will take a few minutes to apply and once the virtual switch is created, the list of virtual switches updates to reflect the newly created switch. You can see that the specified virtual switch is created and enabled for compute.
498
498
499
-
499
+
500
500
501
501
1. You can create more than one switch by following the steps described earlier.
502
502
@@ -558,7 +558,7 @@ After the virtual switches are created, you can enable the switches for Kubernet
558
558
559
559
1. Select **Apply**.
560
560
561
-
561
+
562
562
563
563
1. The configuration takes a couple minutes to apply and you may need to refresh the browser.
0 commit comments