Changing the IP Address of VMware Identity Manager 3.3.7 Appliance

Two procedures are described in this topic, change the IP address for a single node and change the IP address in a cluster.

Prerequisites

Verify that you have taken a snapshot of VMware Identity Manager nodes.
List of the new cluster nodes IP addresses.
Confirm that the new IP and associated subnet networking are compatible with the containing vCenter distributed switch and networking.

Change IP Address in a VMware Identity Manager Single Node Standard Instance

Change the IP address for a single node VMware Identity Manager 3.3.7 appliance.

Procedure

Perform an Inventory sync to verify that the VMware Identity Manager configuration is in sync with vRealize Suite Lifecycle Manager.
Power OFF the virtual machine.
Update the DNS name mapping for new IP.
Update the VMware Identity Manager IP, Gateway, Netmask, and DNS in the vCenter vApp OVF properties.
Power ON the virtual machine.
Connect to the VMware Identity Manager database using the following steps.
1. Copy the db password: cat /usr/local/horizon/conf/db.pwd
2. Navigate to the path: opt/vmware/vpostgres/current/bin/psql -U horizon saas
3. Paste the password you copied from db.pwd and hit enter.

Update the ServiceInstance table of the database with the new IP address of the node.

update "ServiceInstance" set "IPAddress" = '<newIPAddress' where "IPAddress" = '<oldIPAddress>’;

Result: UPDATE 1

Restart the horizon service. Enter
```
/etc/init.d/horizon-workspace restart
```
Check the VMware Identity Manager diagnostics for errors.
Run Inventory Sync in the vRealize Suite LCM Repository to update the new IP address in the vRealize Suite Lifecycle Manager inventory.
If failure occurs at the snapshot update task, skip the task in the request and proceed.
Trigger Inventory Sync again to make sure there are no failures.

Change IP Address in a VMware Identity Manager Cluster Instance with Lifecycle Manager PGpool

Change the IP address cluster nodes in VMware Identity Manager 3.3.7.

Procedure

Perform an Inventory sync to verify that the VMware Identity Manager configuration is in sync with vRealize Suite Lifecycle Manager.If the cluster status is critical (red), run the Remediate action before proceeding. If the cluster status is health (green), proceed to step 3.
Shut down all of the VMware Identity Manager services. If necessary, see the Clustered VMware Identity Manager section in the VMware Graceful Shutdown and Power On a VMware Identity Manager PostgreSQL cluster KB article.
In the /usr/local/etc/pgpool.conf file for each node in the cluster, change the hard-coded cluster node IP addresses to the new set of IP addresses.
On each node, update the value of VIDM_NETMASK in the /usr/local/etc/failover.sh file to the new netmask.
On each node edit /etc/hosts and update the Cluster primary IP.
Update the DNS mapping for new IP's to existing Host names.
Update the load balancer with the new IP's
Power OFF the virtual machines in vCenter.
Update the VMware Identity Manager IP, Gateway, Netmask, and DNS in the vCenter OVF properties for each of the nodes.
Power ON the virtual machines in vCenter, beginning with the primary node, followed by the secondary nodes.
Change the delegate IP address of the cluster.
1. Create an SSH connection to each node in the cluster as the root user.
2. Enter the command /etc/init.d/pgService stop to stop pgService on each of the nodes, begin with the secondary nodes and then stop the primary node.
3. Enter the command ifconfig eth0:0 down to shut down the driver for the delegate IP address in the primary node.
4. Add the new delegate IP address to the /etc/hosts file in each of the nodes. This address must be a free static IP address.
5. Enter /etc/init.d/pgService start to start pgService on each of the nodes, beginning with the primary node, followed by the secondary nodes.
6. To reassign the delegate IP address run the following command on the primary node, ifconfig eth0:0 inet delegateIP netmask <Netmask>. For <Netmask>, enter the netmask currently configured for the node.
Connect to the VMware Identity Manager database using the following steps.
1. Copy the db password: cat /usr/local/horizon/conf/db.pwd
2. Navigate to the path: opt/vmware/vpostgres/current/bin/psql -U horizon saas
3. Paste the password you copied from db.pwd and hit enter.
Update the ServiceInstance table of the VMware Identity Manager database with the new IP address of the nodes. For each node, enter
```
update "ServiceInstance" set "IPAddress" = '<newIPAddress' where "IPAddress" = '<oldIPAddress>’;
```
Restart horizon services.
1. Restart horizon service on each of the nodes in the cluster, beginning with the primary node followed by the secondary nodes. Enter /etc/init.d/horizon-workspace restart.
2. Restart the OpenSearch service on each of the nodes in the cluster, beginning with the primary node followed by the secondary nodes. Enter /etc/init.d/opensearch restart.
3. Validate that the secondary nodes can communicate to the delegateIP address at port 5432. Enter curl -v delegateIP:5432.