Skip to content

Commit 7d125f5

Browse files
Update service-fabric-cluster-windows-server-add-remove-nodes.md
1 parent 41a8310 commit 7d125f5

File tree

1 file changed

+14
-4
lines changed

1 file changed

+14
-4
lines changed

articles/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,23 @@ After you have [created your standalone Service Fabric cluster on Windows Server
2222

2323
## Add nodes to your cluster
2424

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+
2830
3. Remote desktop (RDP) into the VM/machine that you want to add to the cluster
2931
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
3032
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.
34+
Unsecure (prototyping):
35+
```
36+
37+
.\AddNode.ps1 -NodeName VM5 -NodeType NodeType0 -NodeIPAddressorFQDN 182.17.34.52 -ExistingClientConnectionEndpoint 182.17.34.50:19000 -UpgradeDomain UD1 -FaultDomain fd:/dc1/r0 -AcceptEULA
38+
39+
```
40+
41+
Secure (Certificate-based):
3242
```
3343

3444
$CertThumbprint= "***********************"

0 commit comments

Comments
 (0)