Sie sind auf Seite 1von 6

How to Modify Public Network Information including VIP in Oracle Clusterware (Do

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.

Changing public hostname

Public hostname is recorded in OCR, it is entered during installation phase. It


can not be modified after the installation. The only way to modify public hostna
me is by deleting the node, then add the node back with a new hostname, or reins
tall the clusterware.

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.

Case III. Changing public network interface, subnet or netmask


If the change involves different subnet(netmask) or interface, delete the existi
ng interface information from OCR and add it back with the correct information i
s required. In the example here, the subnet is changed from 10.2.156.0 to 10.2
.166.0 via two separate commands - first a 'delif' followed by a 'setif':
% $CRS_HOME/bin/oifcfg/oifcfg delif -global <if_name>[/<subnet>]
% $CRS_HOME/bin/oifcfg/oifcfg setif -global <if_name>/<subnet>:public
For example:
% $CRS_HOME/bin/oifcfg delif -global eth0/10.2.156.0
% $CRS_HOME/bin/oifcfg setif -global eth0/10.2.166.0:public
Then make the change at OS layer. There is no requirement to restart Oracle clus
terware unless OS change requires a node reboot. This can be done in rolling fas
hion.
Once public network is changed, its associated VIP and SCAN VIP are also require
d to change, refer to CASE IV and CASE V.

Case IV. Changing VIPs associated with public network change


Planning for VIP changes
In general, a complete outage is only required for pre-10.2.0.3 release. From 10
.2.0.3 onwards, the ASM/database instance dependency on the VIP resource is remo
ved, so the VIP could be modified without having to take down the ASM/database i
nstance, only client connections to the database will be affected when VIP is do
wn. If the modification is a node specific, then only connection to that node wi
ll be affected during the time of change.
Please follow Case III to ensure public network changes are made first. If there
is a node reboot or Clusterware restart after the OS network change, vip will n
ot start, please skip to step "Modifying VIP and its Associated Attributes".
Gathering Current VIP Configuration
1. Gather the existing setup
for 10g and 11gR1, as Oracle Clusterware owner:
$ srvctl config nodeapps -n <node> -a

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>

(optional for 10.2.0.3+)


(optional for 10.2.0.3+)

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

PRCR-1065 : Failed to stop resource ora.racnode1.vip


CRS-2529: Unable to act on 'ora.racnode1.vip' because that would require stoppin
g or relocating 'ora.LISTENER.lsnr', but the force option was not specified
...
4. Verify VIP is now OFFLINE and the interface is no longer bound to the public
network interface
$ crs_stat -t (or $ crsctl stat res -t for 11gR2)
$ ifconfig -a
(netstat -in for HP and ipconfig /all for windows)
Modifying VIP and Its Associated Attributes
5. Determine the new VIP IP/subnet/netmask or VIP hostname, make the network cha
nge on OS first, ensure the new VIP is registered in DNS or modified in /etc/hos
ts (for Unix/Linux) and \WINDOWS\System32\drivers\etc\hosts file (for Windows).
If the network interface is changed, ensure the new interface is available on th
e server before proceeding with the modification.
For
New
new
new
new

example:
VIP is: 110.11.70.11 racnode1-nvip
subnet is 110.11.70.0
netmask is 255.255.255.0
interface is eth2

6. Modify the VIP resource, as root user:


# srvctl modify nodeapps -n <node> -A <new_vip_address or new_vip_hostname>/<net
mask>/<[if1[if2...]]>
eg:
# srvctl modify nodeapps -n racnode1 -A racnode1-nvip/255.255.255.0/eth2
Note: Starting with 11.2, the VIPs depend on the network resource (ora.net1.netw
ork), the OCR only records the VIP hostname or the IP address associated with th
e VIP resource. The network attributes (subnet/netmask/interface) are recorded w
ith the network resource. When the nodeapps resource is modified, the network re
soure(ora.net1.network) attributes are also modified implicitly.
From 11.2.0.2 onwards, if only subnet/netmask/interface change is required, netw
ork resource can be modified directly via srvctl modify network command.
as root user:
# srvctl modify network -k <network_number>] [-S <subnet>/<netmask>[/if1[|if2...
]]
eg:
# srvctl modify network -k 1 -S 110.11.70.0/255.255.255.0/eth2
There is no need to modify VIP or SCAN if other attributes are not changed.
* A special case for 11gR2 modifying the VIP hostname only without changing the
IP address.
For example: only VIP hostname changes from racnode1-vip to racnode1-nvip, IP an
d other attributes remain the same.
If IP address is not changed, above modify command will not change the USR_ORA_V

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

(optional for 10.2.0.3+)


(optional for 10.2.0.3+)

nodeapps -n racnode1
asm -n racnode1
instance -d RACDB -i RACDB1
Infrastructure owner:

$ srvctl start vip -n <node_name>


$ srvctl start instance -d <db_name> -n <node_name>

(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

ter to reflect the VIP change if necessary.

Case V. Change SCAN VIP associated with public network change


With Grid Infrastructure 11gR2, SCAN and SCAN VIP are introduced for client conn
ections. To modify the SCAN VIP, please refer to
Note 952903.1 How to update the IP address of the SCAN VIP resources (ora.scan<n
>.vip)
Note 972500.1 How to Modify SCAN Setting or SCAN Listener Port after Installatio
n