%3CLINGO-SUB%20id%3D%22lingo-sub-2014107%22%20slang%3D%22en-US%22%3ESteps%20to%20Associate%20Old%20IP%20address%20to%20New%20Service%20Fabric%20cluster.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2014107%22%20slang%3D%22en-US%22%3E%3CP%3EAssume%20you%20have%20a%20Existing%20Cluster%3C%2FP%3E%0A%3CP%3EResource%20Group%3A%20oldsf-rg%3C%2FP%3E%0A%3CP%3ECluster%20name%3A%20oldsfcluster%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStep%201%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EGo%20to%20Resource%20Group(oldsf-rg)-%20%26gt%3B%20Public%20IP%20address%20resource%20-%26gt%3BConfiguration%3C%2FP%3E%0A%3CP%3EEnsure%20you%20have%20static%20assignment%2C%20if%20not%20yet%20(If%20its%20Dynamic%2C%20when%20you%20associate%20old%20Public%20IP%20address%20to%20new%20Sf%20cluster%2C%20the%20IP%20address%20will%20get%20changed)%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_16-1608805345586.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242685i47BE4D9603331AC8%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_16-1608805345586.png%22%20alt%3D%22reshmav_16-1608805345586.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStep%202%3A%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EPlease%20delete%20all%20the%20resources%20from%20the%20resource%20group%20(oldsf-rg)%20except%20your%20Public-Ip%20address%20resource.%3C%2FP%3E%0A%3CP%3ENote%3A%20Do%20not%20delete%20the%20resource%20group%20directly%2C%20rather%20I%20would%20suggest%20you%20to%20delete%20the%20each%20resources%20separately%20in%20below%20order%20one%20by%20one(%20Since%20some%20resource%20will%20have%20dependency)%3C%2FP%3E%0A%3CP%3EOrder%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EVirtual%20machine%20scale%20set%3C%2FLI%3E%0A%3CLI%3EService%20Fabric%20cluster%3C%2FLI%3E%0A%3CLI%3EStorage%20account%20(both)%3C%2FLI%3E%0A%3CLI%3EVirtual%20network%3C%2FLI%3E%0A%3CLI%3ENetwork%20security%20group%3C%2FLI%3E%0A%3CLI%3ELoad%20Balancer%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ENow%20you%20will%20be%20having%20only%20Public%20IP%20address%20resource%20under%20your%20resource%20group%20(oldsf-rg)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStep%203%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EPlease%20create%20the%20new%20SF%20cluster%20with%20your%20desired%20configurations%3C%2FP%3E%0A%3CP%3EAssume%20New%20SF%20name%20%3A%20newsfcluster%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF0000%22%3EPlease%20Note%3A%20Both%20Old%20and%20New%20Cluster%20has%20to%20be%20in%20Same%20region.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EOnce%20successful.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStep%204%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EGo%20to%20New%20Resource%20group%20-%26gt%3B%20Load%20balancer%20resource-%26gt%3B%20Frontend%20IP%20configuration(%20left%20pane)%3C%2FP%3E%0A%3CP%3EYou%20will%20be%20able%20to%20see%20a%20dropdown%20as%20shown%20below%2C%20where%20your%20old%20Public%20IP%20address%20will%20be%20listed.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_17-1608805382729.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242686iC6C930843BFCF7C2%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_17-1608805382729.png%22%20alt%3D%22reshmav_17-1608805382729.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAssociate%20the%20New%20LB%20to%20Old%20IP%20address%20and%20click%20on%20%E2%80%9CSave%E2%80%9D%3C%2FP%3E%0A%3CP%3EDeployment%20Starts%2C%20please%20wait%20till%20the%20Deployment%20succeeded.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStep%205%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EOnce%20successful%2C%20Please%20verify%20below%3A%3C%2FP%3E%0A%3CP%3EOld%20Public%20IP%20address%20is%20associated%20with%20New%20LB%20resource%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_10-1608804950717.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242678iA304E33C4BD7C28E%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_10-1608804950717.png%22%20alt%3D%22reshmav_10-1608804950717.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EOld%20Public%20IP%20address%20with%20New%20VMSS%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_11-1608804950733.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242681i303142E02CA6AE99%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_11-1608804950733.png%22%20alt%3D%22reshmav_11-1608804950733.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ENow%20you%20should%20be%20able%20to%20RDP%20into%20new%20node%20using%20old%20Public%20IP%20address%20(IPaddress%3A3389%20)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETry%20Accessing%20the%20SFX%20with%20Public%20IP%20address%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2FXX.XXX.XXX.XXX%3A19080%2FExplorer%2Findex.html%23%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2FXX.XXX.XXX.XXX%3A19080%2FExplorer%2Findex.html%23%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EHowever%20when%20you%20click%20on%20SFX%2FManagement%20Endpoint%20the%20one%20in%20Portal%2C%20you%20may%20get%20below%20Error%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_18-1608805417578.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242687iE6F72441C6A8AB5B%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_18-1608805417578.png%22%20alt%3D%22reshmav_18-1608805417578.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EReason%3A%20Management%20Endpoint%20Domain%20is%20still%20pointing%20to%20Old%20DNS%20name%20which%20is%20no%20more%20resolving%20to%20Old%20public%20IP.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStep%206%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ETo%20map%20Management%20Endpoint%20Domain%20to%20New%20DNS%20name.%3C%2FP%3E%0A%3CP%3EGo%20to%20new%20Public%20IP%20address%20resource%20-%26gt%3B%20Configuration%3C%2FP%3E%0A%3CP%3ECopy%20the%20DNS%20value%20and%20Change%20the%20DNS%20name%20to%20some%20random%20value%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_19-1608805459185.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242688iDAF476771DAFAE80%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_19-1608805459185.png%22%20alt%3D%22reshmav_19-1608805459185.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAnd%20paste%20on%20Old%20Public%20IP%20address%20-%26gt%3B%20Configuration%20-%26gt%3B%20DNS%20name%20label%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_20-1608805486544.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242689i83BE70CC64D0CDFD%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_20-1608805486544.png%22%20alt%3D%22reshmav_20-1608805486544.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3BNow%20Azure-Portal-%26gt%3B%20SF%20cluster%20should%20point%20to%20new%20DNS%20name%20and%20SFX%20link%20should%20be%20accessible%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22reshmav_15-1608804950796.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F242683iFE97E5C6D5C2F0C4%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22reshmav_15-1608804950796.png%22%20alt%3D%22reshmav_15-1608804950796.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2014107%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Service%20Fabric%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Assume you have a Existing Cluster

Resource Group: oldsf-rg

Cluster name: oldsfcluster

 

Step 1:

Go to Resource Group(oldsf-rg)- > Public IP address resource ->Configuration

Ensure you have static assignment, if not yet (If its Dynamic, when you associate old Public IP address to new Sf cluster, the IP address will get changed)

reshmav_16-1608805345586.png

 

Step 2:

Please delete all the resources from the resource group (oldsf-rg) except your Public-Ip address resource.

Note: Do not delete the resource group directly, rather I would suggest you to delete the each resources separately in below order one by one( Since some resource will have dependency)

Order:

  • Virtual machine scale set
  • Service Fabric cluster
  • Storage account (both)
  • Virtual network
  • Network security group
  • Load Balancer

Now you will be having only Public IP address resource under your resource group (oldsf-rg)

 

Step 3:

Please create the new SF cluster with your desired configurations

Assume New SF name : newsfcluster

Please Note: Both Old and New Cluster has to be in Same region.

Once successful.

 

Step 4:

Go to New Resource group -> Load balancer resource-> Frontend IP configuration( left pane)

You will be able to see a dropdown as shown below, where your old Public IP address will be listed.

reshmav_17-1608805382729.png

Associate the New LB to Old IP address and click on “Save”

Deployment Starts, please wait till the Deployment succeeded.

 

Step 5:

Once successful, Please verify below:

Old Public IP address is associated with New LB resource

reshmav_10-1608804950717.png

Old Public IP address with New VMSS

reshmav_11-1608804950733.png

Now you should be able to RDP into new node using old Public IP address (IPaddress:3389 )

 

Try Accessing the SFX with Public IP address:

https://XX.XXX.XXX.XXX:19080/Explorer/index.html#/

However when you click on SFX/Management Endpoint the one in Portal, you may get below Error:

reshmav_18-1608805417578.png

Reason: Management Endpoint Domain is still pointing to Old DNS name which is no more resolving to Old public IP.

 

 

Step 6:

To map Management Endpoint Domain to New DNS name.

Go to new Public IP address resource -> Configuration

Copy the DNS value and Change the DNS name to some random value

reshmav_19-1608805459185.png

And paste on Old Public IP address -> Configuration -> DNS name label

reshmav_20-1608805486544.png

 Now Azure-Portal-> SF cluster should point to new DNS name and SFX link should be accessible:

reshmav_15-1608804950796.png