Skip to content

Commit 06d62fd

Browse files
Merge pull request #234884 from LouisBerner/v-lberner-ADO_72982
Updated 'Cluster deployment' section
2 parents 0419963 + 1aaec3d commit 06d62fd

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 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: 02/22/2022
10+
ms.date: 04/18/2023
1111
ms.author: alkohli
1212
---
1313

@@ -150,7 +150,7 @@ Before you configure clustering on your device, you must cable the devices as pe
150150
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).
151151
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).
152152
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.
154154
1. Use the authentication token from the prepared node and join this node to the first node to form a cluster.
155155
1. Set up a cloud witness using an Azure Storage account or a local witness on an SMB fileshare.
156156
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
169169
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).
170170
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).
171171
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.
173173
1. Use the authentication token from the prepared node and join this node to the first node to form a cluster.
174174
1. Set up a cloud witness using an Azure Storage account or a local witness on an SMB fileshare.
175175
1. Assign a virtual IP to provide an endpoint for Azure Consistent Services or when using NFS.

0 commit comments

Comments
 (0)