AZURE ISE 3.3 unable to ssh to ise after changing to static ip

[mitchellT]

i'm installing Cisco ISE 3.3 in Azure. after node is installed and I change the IP to static, I can not ssh to the node with public key or via the Azure Serial console and it seems ISE service won't start either. i've tried multiple times with new install and got the same result. anyone running into this same issue with Azure ISE 3.3? 

[balaji.bandi]

what was the before IP address - is the static IP address same range ?

3 days back tested in My lab using exsi working for me with below guide :

https://www.cisco.com/c/en/us/td/docs/security/ise/3-3/install_guide/b_ise_installationGuide33/b_ise_InstallationGuide33_chapter_4.html

[mitchellT]

yes, all i did was change from dynamic (10.200.101.5) to static (10.200.101.25) and then start the azure vm. after that it stopped working. i can ping it 10.200.101.25 but can not access serial console

Failed to log in 0 time(s)
Failed to connect to server
Exit
Connection to 10.200.101.25 closed.

[Aref Alsouqi]

Where did you apply that change?

[mitchellT]

In Azure vm's network setting, I change from dynamic to static

[adamscottmaster2013]

@balaji.bandi:  ESXi environment is NOT the same as Azure or AWS environment.  They are not the same.

[mitchellT]

i open TAC case and it seems i'm hitting this bug

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwi33361