Set a new virtual public IP address

In an existing high availability environment, you can change the virtual public IP address.

Before you begin

Note: Changing the virtual public IP address impacts the operation of the cluster. This change must be scheduled to avoid any impact to users or the environment.

To change the virtual public IP address, you must have a high availability environment that is already enabled. You must also have a new IP address available in the same subnet.

Procedure

Change the network interface configuration table attributes.

# lsdef -t node -o newvirtualmn -i nicips
Object name: newvirtualmn
    nicips.eth0:0=172.20.7.5
    nicips.eth1:0=192.168.1.5

# chdef -t node -o newvirtualmn nicips='eth0:0!172.20.7.10,eth1:0!192.168.1.5'

where newvirtualmn is the name of your virtual management node, and 172.20.7.5 is the old public IP address and 172.20.7.10 is the new public IP address.

Regenerate the host and DNS entry for the virtual management node name. Also, you must update your corporate DNS server to change the name resolution in public domain accordingly. Contact your IT administrator for details on how to change the corporate DNS server.
```
# makehosts newvirtualmn
# makedns newvirtualmn 
```
Reconfigure the PCMHA service agent to use the new virtual IP address.
```
# pcm-ha-support gendata
# pcm-ha-support start –-service PCMHA
```
Verify that the new IP address is available.
```
# ifconfig
```
Synchronize the /etc/hosts to other nodes in Platform Cluster Manager Community Edition cluster.
```
#updatenode standby-mn -F
#updatenode __Managed -F
```
where standby-mn is the standby management node.

What to do next

If the old virtual name is used anywhere on the management nodes or compute nodes, those values must be updated according to the new value. For example, any configuration files not managed by Platform Cluster Manager Community Edition.