Set a new virtual provision IP address

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

Before you begin

Before setting a new virtual provision IP address, ensure that the following requirements are met:
  • You must have a high availability environment that is already enabled.
  • You must also have a new IP address available in the same subnet.
Also, be aware of the following points, and make your changes accordingly:
  • Changing the virtual provision IP address impacts the operation of the cluster. This change must be scheduled to avoid any impact to users or the environment.

  • Compute nodes use the virtual provision IP address to access cluster services on the active management node. To set a new virtual provision IP address, the compute nodes must be reprovisioned or reconfigured with the new defined virtual IP address.

About this task

This procedure uses example IP address value. IP address value 192.168.1.5 is the old IP address and 192.168.1.10 is the new IP address.

Procedure

  1. Change the site table attributes.
    # chdef -t site master=192.168.1.10 
    # chdef -t site nameservers=192.168.1.10
  2. Change the network interface configuration table attributes.
    # lsdef -t node -o newvirtualmn -i nicips
    Object name: newvirtualmn
        nicips.eth0:0=172.20.7.10
        nicips.eth1:0=192.168.1.5
    
    # chdef -t node -o newvirtualmn nicips='eth0:0!172.20.7.10,eth1:0!192.168.1.10’
     ip=192.168.1.10
    where newvirtualmn is the name of the virtual management node.
  3. In the networks table, change the old IP address 192.168.1.5 to the new IP address 192.168.1.10 and save the changes.
    #tabdump networks|grep 192.168.1.5
    #tabedit networks
  4. Reconfigure the PCMHA service agent to use the new virtual IP address.
    # pcm-ha-support gendata
    # pcm-ha-support start –-service PCMHA
  5. Update database files and reload the database server.
    #  vi /var/lib/pgsql/data/pg_hba.conf 
    #  IPv4 local connections: 
    host all all 192.168.1.5/32 md5 
    becomes 
    host all all 192.168.1.10/32 md5
    
    # service postgresql reload
  6. Reconfigure other services on the management nodes to use the new virtual IP address.
    # pcmconfig -f
  7. Reconfigure compute nodes to use the new virtual provision IP address.
    # updatenode __Managed -P

What to do next

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