Change Vapp IP

[sudip karmacharya]

Dear Team,

Currently, we are shifting our network so we required to change the ip of the vapp but in vapp there is no permission to change ip directly. 
In Vapp also there is too much module that is using those IPs. 
Is this required to redeploy the Vapp?

Please suggest how can achieve this?



Thank you,

------------------------------
Network and security Engineer technical associative
Cas Trading House
Putalisadak, KTM
------------------------------

[Yuan Heng Lin]

Hi Sudip,

You will require to redeploy the Vapp. Once the Vapp was deployed, you won't be able to change IPs.

Best regards,
Frank

------------------------------
------------------------------
And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.
Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at [e-mail]. https://www.hcltech.com/enterprise-studio
------------------------------

[sudip karmacharya]

Dear Frank,

We will redeploy the Vapp but the issue is what to do for the configuration file.
like
1. User data 
2. Roles detail
3. email configuration
4. policy detail
5. in Portal created task, form, other related data
6. custom attribute

how to restore this thing to the new Vapp and please suggest.
And in the user store, provisioning store, and External DB which Data will store in it?


Thank you,


------------------------------
Network and security Engineer technical associative
Cas Trading House
Putalisadak, KTM
------------------------------

[Widjaja Sangtoki]

Hi Sudip,

Provided the new network is connected to the old network fast enough, alternative way to move vApp to the new network is to add new vApp on the new network into the cluster of the existing vApp on the old network. Replicate all the components/services into the new vApp and re-deploy. Once successful, you can access the new vApp dashboard and go to Setup screen, shutdown the old vApp, remove the old vApp from the Setup screen of new vApp and redeploy. Once the redeploy is successful, the new vApp will run at its own and you can decommission the old vApp.

I am not sure with your vApp version, but theoretically this approach should work. I would suggest you can test this approach firstly before doing the steps on your Production environment.

------------------------------
Regards,
Widjaja
====================
Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.

Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at [e-mail]. https://www.hcltech.com/enterprise-studio
------------------------------

[Rinat Matityahu]

As pointed out by my peers, indeed there is no way to change the IP of a vApp once deployed.
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/identity-suite/14-3/ca-identity-suite-reference-architecture/foundation-physical-architecture/base-system-configuration-requirements/requirements-for-virtual-machine-platform-networking-configuration.html

You will have to use the .ova for a complete new extract of a vApp, as redeployment from the dashboard will not be sufficient - just want to make it clear as the term redeploy has a specific meaning in Identity Suite realm.

As long as you are pointing the new vApp to the original DB - Identity Manager / Identity Portal data will remain in place.

As for the Directory data (User Store, Provisioning Store, Schema) - these will need to be manually restored using the normal CA Directory procedures for backup and restore.

Another option is to add the new vApp servers to the cluster (as suggested by Widjaja) and allow the data to be replicated that way, before disassociating the old, redundant servers.

Regards
Rinat