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-clustering-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: alkohli
7
7
ms.service: databox
8
8
ms.subservice: edge
9
9
ms.topic: conceptual
10
-
ms.date: 02/22/2022
10
+
ms.date: 04/18/2023
11
11
ms.author: alkohli
12
12
---
13
13
@@ -150,7 +150,7 @@ Before you configure clustering on your device, you must cable the devices as pe
150
150
1. Order two independent Azure Stack Edge devices. For more information, see [Order an Azure Stack Edge device](azure-stack-edge-gpu-deploy-prep.md#create-a-new-resource).
151
151
1. Cable each node independently as you would for a single node device. Based on the workloads that you intend to deploy, cross connect the network interfaces on these devices via cables, and with or without switches. For detailed instructions, see [Cable your two-node cluster device](azure-stack-edge-gpu-deploy-install.md#cable-the-device).
152
152
1. Start cluster creation on the first node. Choose the network topology that conforms to the cabling across the two nodes. The chosen topology would dictate the storage and clustering traffic between the nodes. See detailed steps in [Configure network and web proxy on your device](azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md).
153
-
1. Prepare the second node. Configure the network on the second node the same way you configured it on the first node. Get the authentication token on this node.
153
+
1. Prepare the second node. Configure the network on the second node the same way you configured it on the first node. Ensure that port settings match between same port name on each appliance. Get the authentication token on this node.
154
154
1. Use the authentication token from the prepared node and join this node to the first node to form a cluster.
155
155
1. Set up a cloud witness using an Azure Storage account or a local witness on an SMB fileshare.
156
156
1. Assign a virtual IP to provide an endpoint for Azure Consistent Services or when using NFS.
@@ -169,7 +169,7 @@ Before you configure clustering on your device, you must cable the devices as pe
169
169
1. Order two independent Azure Stack Edge devices. For more information, see [Order an Azure Stack Edge device](azure-stack-edge-pro-2-deploy-prep.md#create-a-new-resource).
170
170
1. Cable each node independently as you would for a single node device. Based on the workloads that you intend to deploy, cross connect the network interfaces on these devices via cables, and with or without switches. For detailed instructions, see [Cable your two-node cluster device](azure-stack-edge-pro-2-deploy-install.md#cable-the-device).
171
171
1. Start cluster creation on the first node. Choose the network topology that conforms to the cabling across the two nodes. The chosen topology would dictate the storage and clustering traffic between the nodes. See detailed steps in [Configure network and web proxy on your device](azure-stack-edge-pro-2-deploy-configure-network-compute-web-proxy.md).
172
-
1. Prepare the second node. Configure the network on the second node the same way you configured it on the first node. Get the authentication token on this node.
172
+
1. Prepare the second node. Configure the network on the second node the same way you configured it on the first node. Ensure that port settings match between same port name on each appliance. Get the authentication token on this node.
173
173
1. Use the authentication token from the prepared node and join this node to the first node to form a cluster.
174
174
1. Set up a cloud witness using an Azure Storage account or a local witness on an SMB fileshare.
175
175
1. Assign a virtual IP to provide an endpoint for Azure Consistent Services or when using NFS.
0 commit comments