Modifying the VIP or VIP Hostname for 11gR2

Verification of Existing Configuration:

$ srvctl config nodeapps -a >>> Use this command to find the existing info
crsctl stat res -t >>> It should show VIPs are ONLINE
$ ifconfig -a



Stop all the relevant resources:

$ srvctl stop instance -d <db_name> -n <node_name>
$ srvctl stop vip -n <node_name> -f

To prevent the automatic startup of ASM or database instances until the change has been verified, one might want to disable the corresponding resources:
$ srvctl disable nodeapps
crsctl stat res -t >>> It should show VIPs are OFFLINE
ifconfig -a



Modifying VIP and Its Associated Attributes


As root user:
# srvctl modify nodeapps -n <node> -A <new_vip_address or new_vip_hostname>/<netmask>/<[if1[if2...]]>

From 11.2.0.2 onwards, network resource can be modified directly via srvctl modify network command.
as root user:
# srvctl modify network -k <network_number>] [-S <subnet>/<netmask>[/if1[|if2...]]



Start the nodeapps and the other resources

If resources are disabled before, they can be enabled now with
$ srvctl enable nodeapps
$ srvctl enable asm -n <node_name>
$ srvctl enable database -d <db_name>

$ srvctl start nodeapps -n <node_name>
$ srvctl start instance -d <dbanme> -i <inst>
$ srvctl start asm -n <node_name>



Verification After Completion:

$ srvctl config nodeapps -a
crsctl stat res -t
ifconfig -a

Repeat the same steps for the rest nodes in the cluster only if the similar change is required.