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/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,13 +22,23 @@ After you have [created your standalone Service Fabric cluster on Windows Server
22
22
23
23
## Add nodes to your cluster
24
24
25
-
1. Prepare the VM/machine you want to add to your cluster by following the steps outlined in [Plan and prepare your Service Fabric cluster deployment](service-fabric-cluster-creation-for-windows-server.md)
26
-
(For an exiting cluster, you do not need to follow the steps to create the cluster, ensure that the Service fabric Standalone package and Service fabric Runtime cab file is present on the new node)
27
-
2. Identify which fault domain and upgrade domain you are going to add this VM/machine to
25
+
1. Prepare the VM/machine you want to add to your cluster by following the steps outlined in [Plan and prepare your Service Fabric cluster deployment](service-fabric-cluster-standalone-deployment-preparation.md)
26
+
27
+
2. Identify which fault domain and upgrade domain you are going to add this VM/machine to.
28
+
When using certificates to secure the cluster they are expected to be installed in the local certificate stores in preparation for the node to join the cluster. The analog is applicable when using other forms of security.
29
+
28
30
3. Remote desktop (RDP) into the VM/machine that you want to add to the cluster
29
31
4. Copy or [download the standalone package for Service Fabric for Windows Server](https://go.microsoft.com/fwlink/?LinkId=730690) to the VM/machine and unzip the package
30
32
5. Run Powershell with elevated privileges, and navigate to the location of the unzipped package
31
-
6. Run the *AddNode.ps1* script with the parameters describing the new node to add. The example below adds a new node called VM5, with type NodeType0 and IP address 182.17.34.52, into UD1 and fd:/dc1/r0. The *ExistingClusterConnectionEndPoint* is a connection endpoint for a node already in the existing cluster, which can be the IP address of *any* node in the cluster. The cluster certificate used below should be installed under Personal (My) store of the current user.
33
+
6. Run the *AddNode.ps1* script with the parameters describing the new node to add. The example below adds a new node called VM5, with type NodeType0 and IP address 182.17.34.52, into UD1 and fd:/dc1/r0. The *ExistingClusterConnectionEndPoint* is a connection endpoint for a node already in the existing cluster, which can be the IP address of *any* node in the cluster.
0 commit comments