Documente Academic
Documente Profesional
Documente Cultură
c ID 276434.1)
How to Modify Public Network Information including VIP in Oracle Clusterware (Do
c ID 276434.1) To BottomTo Bottom
In this Document
Purpose
Scope
Details
Case I. Changing public hostname
Case II. Changing public IP only without changing interface, subnet or
netmask
Case III. Changing public network interface, subnet or netmask
Case IV. Changing VIPs associated with public network change
Planning for VIP changes
Gathering Current VIP Configuration
Stopping Resources
Modifying VIP and Its Associated Attributes
Restarting Resources
Others
Case V. Change SCAN VIP associated with public network change
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.1.0.1 [Release 10.
1 to 12.1]
Information in this document applies to any platform.
PURPOSE
The purpose of this note is to illustrate how to change a public hostname, publi
c IP, a Virtual IP Address (VIP), VIP hostname or other VIP attributes in an Ora
cle Clusterware/Grid Infrastructure environment.
SCOPE
Oracle Database 10g and 11g use VIPs (Virtual IP) in clustered environments for
clients to connect to the database. These VIPs are static IP addresses associate
d with (virtual) hostnames and resolved through DNS (except when using 11gR2 GNS
).
During the installation of the Oracle Clusterware users are prompted to enter a
Virtual IP and Virtual hostname for each of the node in the cluster. These are s
tored within the OCR (Oracle Cluster Registry) and different components within t
he HA framework depend on these VIPs. If for some reason the need arises to chan
ge either the VIP, the VIP hostname, or the subnet, netmask etc, this procedure
should be followed.
For changes associated with private network/cluster interconnect, please refer t
o Note 283684.1
DETAILS
Case I.
Case II. Changing public IP only without changing interface, subnet or netmask
If the change is only public IP address and the new ones are still in the same s
ubnet, nothing needs to be done on clusterware layer, all changes need to be don
e at OS layer to reflect the change.
1. Shutdown Oracle Clusterware stack
2. Modify the IP address at network layer, DNS and /etc/hosts file to reflect th
e change
3. Restart Oracle Clusterware stack
Above change can be done in rolling fashion, eg: one node at a time.
eg:
$ srvctl config nodeapps -n racnode1 -a
VIP exists.: /racnode1-vip/101.17.80.184/255.255.254.0/eth1
for 11gR2, as Grid Infrastructure owner:
$ srvctl config nodeapps -a
eg:
$ srvctl config nodeapps -a
Network exists: 1/101.17.80.0/255.255.254.0/eth1, type static
VIP exists: /racnode1-vip/101.17.80.184/101.17.80.0/255.255.254.0/eth1, hosting
node racnode1
VIP exists: /racnode2-vip/101.17.80.186/101.17.80.0/255.255.254.0/eth1, hosting
node racnode2
2. Verify VIP status
10.2 and 11.1:
$ crs_stat -t
11.2:
$ crsctl stat res -t
- it should show VIPs are ONLINE
$ ifconfig -a
(netstat -in for HP and ipconfig /all for Windows)
- VIP logical interface is bound to the public network interface
Stopping Resources
3. Stop the nodeapps resources (and all dependent resources ASM/DB only if requi
red):
10g and 11gR1, as Oracle Clusterware owner:
$ srvctl stop instance -d <db_name> -i <inst_name>
$ srvctl stop asm -n <node_name>
$ srvctl stop nodeapps -n <node_name>
eg,
$ srvctl stop instance -d RACDB -i RACDB1
$ srvctl stop asm -n racnode1
$ srvctl stop nodeapps -n racnode1
11gR2, as Grid Infrastructure owner:
$ srvctl stop instance -d <db_name> -n <node_name>
$ srvctl stop vip -n <node_name> -f
(optional)
eg,
$ srvctl stop instance -d RACDB -n racnode1
$ srvctl stop vip -n racnode1 -f
Note 1: The -f option is required for 11gR2 to stop listener resource, otherwise
following error will occur:
PRCR-1014 : Failed to stop resource ora.racnode1.vip
example:
VIP is: 110.11.70.11 racnode1-nvip
subnet is 110.11.70.0
netmask is 255.255.255.0
interface is eth2
IP value in 'crsctl stat res ora.racnode1.vip -p' output. Please use the followi
ng command:
# crsctl modify res ora.racnode1.vip -attr USR_ORA_VIP=racnode1-nvip
Verify the changes for USR_ORA_VIP field:
# crsctl stat res ora.racnode1.vip -p |grep USR_ORA_VIP
Note: For Windows platform, the interface name needs to be in quote (") if there
is a space in between, eg:
As administrator user or software install user:
> srvctl modify nodeapps -n racnode1 -A 110.11.70.11/255.255.255.0/"Local Area C
onnection 1"
7. Verify the change
$ srvctl config nodeapps -n <node> -a (10g and 11gR1)
$ srvctl config nodeapps -a (11gR2)
eg:
$ srvctl config nodeapps -n racnode1 -a
VIP exists.: /racnode1-nvip/110.11.70.11/255.255.255.0/eth2
Restarting Resources
8. Start the nodeapps and the other resources
10g and 11gR1, as Oracle Clusterware owner:
$ srvctl start nodeapps -n <node_name>
$ srvctl start asm -n <node_name>
$ srvctl start instance -d <dbanme> -i <inst>
eg:
$ srvctl start
$ srvctl start
$ srvctl start
11gR2, as Grid
nodeapps -n racnode1
asm -n racnode1
instance -d RACDB -i RACDB1
Infrastructure owner:
(optional)
eg,
$ srvctl start vip -n racnode1
$ srvctl start instance -d RACDB -n racnode1
9. Verify the new VIP is ONLINE and bind to the public network interface
$ crs_stat -t (or $ crsctl stat res -t for 11gR2)
$ ifconfig -a
(netstat -in for HP or ipconfig /all for windows)
10. Repeat the same steps for the rest nodes in the cluster only if the similar
change is required.
Others
11. Modify listener.ora, tnsnames.ora and LOCAL_LISTENER/REMOTE_LISTENER parame