Oracle 11.2.0.4 x64 RAC modify public/private/vip/scan address

I. Description 1. Database Information

Operating system version: OEL6.5 x64
Database Version: Oracle 11.2.0.4 x64 RAC

This document describes how to change the publiic/private/VIP/scan IP address on oracle 11.2.0.4 x64 for OEL6.5. The detailed modification process is as follows. For example, the modification in the production environment requires repeated tests and subsequent operations.

2. IP address information

Original IP Address
192.168.10.201 node1
192.168.10.202 node2
192.168.10.203 node1-vip
192.168.10.204 node2-vip
10.10.10.10 node1-priv
10.10.10.20 node2-priv
192.168.10.200 scan-cluster
Adjusted IP Address
192.168.76.211 node1
192.168.76.212 node2
The 192.168.76.213 node1-vip
The 192.168.76.214 node2-vip
Megaamount 000020 node1-priv
California California 21 node2-priv
192.168.76.210 scan-cluster

Ii. Stop crs and other service resources 1. Disable Automatic listening at two nodes

# Cd/u01/app/11.2.0/grid_1/bin
#./Srvctl disable listener

2. Stop listening for two nodes

#./Srvctl stop listener

3. Disable Automatic database start and stop at two nodes.

#./Srvctl disable database-d orcl

4. Stop the two-node database

#./Srvctl stop database-d orcl-o immediate

5. Disable Automatic VIP activation at two nodes

#./Srvctl disable vip-I "node1-vip"
#./Srvctl disable vip-I "node2-vip"

6. Stop two-node VIP

#./Srvctl stop vip-n node1
#./Srvctl stop vip-n node2

7. Disable node SCAN_LISTENER startup and stop SCAN listening

#./Srvctl disable scan_listener
#./Srvctl stop scan_listener

8. Disable SCAN startup for all nodes

#./Srvctl disable scan

9. Stop SCAN on all nodes

#./Srvctl stop scan

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243546432-0.png "height =" 721 "/>

 

10. Stop operations on CRS (1) node1 Node

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243544592-1.png "height =" 677 "/>

(2) operations on node node2

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243541115-2.png "height =" 572 "/>

 

3. Modify the Public Nic IP address and start crs 1. Modify the two nodes/etc/hosts file

192.168.76.211 node1
192.168.76.212 node2
The 192.168.76.213 node1-vip
The 192.168.76.214 node2-vip
Megaamount 000020 node1-priv
California California 21 node2-priv
192.168.76.210 scan-cluster

2. Modify the NIC address of the server service

Node1 Node
# Cat/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE = bond0
BOOTPROTO = none
IPADDR = 192.168.76.211
NETMASK = 255.255.255.0
GATEWAY = 192.168.76.2
ONBOOT = yes
TYPE = Ethernet
USERCTL = no
PEERDNS = no
# Service network restart

Node2 Node

# Cat/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE = bond0
BOOTPROTO = none
IPADDR = 192.168.76.212
NETMASK = 255.255.255.0
GATEWAY = 192.168.76.2
ONBOOT = yes
TYPE = Ethernet
USERCTL = no
PEERDNS = no

# Service network restart

3. node1 node starts crs

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/224354H47-3.png "height =" 82 "/>

 

4. Start crs on node node2

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/224354M96-4.png "height =" 81 "/>

After a while, you can view it through crs_stat-t.

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/224354K32-5.png "height =" 461 "/>

4. Modify the Public IP address 1. Set the public IP address of the Cluster

# Obtain the cluster IP Address Configuration. If the modified IP address is only in the same CIDR block, you do not need to modify it below.

#./Oifcfg getif
Bond0 192.168.10.0 global public
Bond1 10.10.10.0 global cluster_interconnect

#./Oifcfg delif-global bond0
#./Oifcfg setif-global bond0/192.168.76.0: public

#./Oifcfg getif
Bond1 10.10.10.0 global cluster_interconnect
Bond0 192.168.76.0 global public

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243544U9-6.png "height =" 179 "/>

 

2. modify Network Resources

# Note: For RAC of version 11.2.0.2 or later, you need to modify network resources.
# View the current network configuration

# Cd/u01/app/11.2.0/grid_1/bin

#./Srvctl config network
Network existence: 1/192. 168.10.0/255.255.255.0/bond0, Type static

You can see that the network resource is still the original IP address information, which needs to be modified.

#./Srvctl modify network-k 1-S 192.168.76.0/255.255.255.0/eth0-v

# Note:-k specifies the network number, the number following the exists. -S specifies the New subnet address/New subnet mask/new interface.

#./Srvctl config network
Network existence: 1/192. 168.76.0/255.255.255.0/bond0, Type static

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243545031-7.png "height =" 123 "/>

 

5. Modify the Private IP Address

Note: If a Private IP address is a Private IP address and is isolated by VLAN, no modification is required unless there are special requirements.
If you do not need to modify the content, skip this section.

1. Add a new Private IP Address

#./Oifcfg getif
Bond1 10.10.10.0 global cluster_interconnect
Bond0 192.168.76.0 global public

Delete the content directly. You cannot delete the content. You must add a new one before deleting the old content.

#./Oifcfg delif-global bond1
PRIF-31: Failed to delete the specified network interface because it is the last private interface

#./Oifcfg setif-global bond1/strongswan 20.0: cluster_interconnect

#./Oifcfg getif
Bond1 10.10.10.0 global cluster_interconnect
Bond0 192.168.76.0 global public
Bond1 255.255.20.0 global cluster_interconnect

2. Delete the original IP address information

#./Oifcfg delif-global bond1/10.10.10.0: cluster_interconnect

#./Oifcfg getif
Bond0 192.168.76.0 global public
Bond1 255.255.20.0 global cluster_interconnect

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243543144-8.png "height =" 228 "/>

 

3. Modify the Private IP Address

Note: PrivateIP must be modified before modifying the IP address of the NIC.

Node1 Node
# Cat/etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE = bond1
BOOTPROTO = none
IPADDR = 255.255.255.255.20
NETMASK = 255.255.255.0
ONBOOT = yes
TYPE = Ethernet
USERCTL = no
PEERDNS = no
# Service network restart

Node2 Node
# Cat/etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE = bond1
BOOTPROTO = none
IPADDR = 00000000000021
NETMASK = 255.255.255.0
ONBOOT = yes
TYPE = Ethernet
USERCTL = no
PEERDNS = no

# Service network restart

6. Modify the cluster VIP address

 

1. First view the cluster's VIP

# Cd/u01/app/11.2.0/grid_1/bin
#./Srvctl config vip-n node1
VIP exist:/node1-vip/192.168.76.213/192.168.10.0/255.255.255.0/bond0, managed node node1

2. Cluster VIP configuration

#./Srvctl modify nodeapps-n node1-A 192.168.76.213/255.255.255.0/bond0
#./Srvctl modify nodeapps-n node2-A 192.168.76.214/255.255.255.0/bond0

3. View VIP addresses

#./Srvctl config vip-n node1
VIP exists:/node1-vip/192.168.76.213/192.168.76.0/255.255.255.0/bond0, managed node node1
#./Srvctl config vip-n node2
VIP exists:/node2-vip/192.168.76.214/192.168.76.0/255.255.255.0/bond0, managed node node2

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243541463-9.png "height =" 123 "/>

VII. Cluster SCANIP settings 1. view the scan ip address of the Cluster

#./Srvctl config scan
SCAN name: scan-cluster, network: 1/192. 168.76.0/255.255.255.0/bond0
Scan vip name: scan1, IP:/scan-cluster/192.168.10.200

2. Modify the scan ip Address

#./Srvctl modify scan-n 192.168.76.210

3. view the modified results

#./Srvctl config scan
SCAN name: 192.168.76.210, networking: 1/192. 168.76.0/255.255.255.0/bond0
Scan vip name: scan1, IP:/192.168.76.210/192.168.76.210

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/22435415R-10.png "height =" 129 "/>

 

8. Start the RAC cluster

Operation on node 1

# Cd/u01/app/11.2.0/grid_1/bin
#./Srvctl enable listener
#./Srvctl enable vip-I "node1-vip"
#./Srvctl enable vip-I "node2-vip"
#./Srvctl enable scan_listener
#./Srvctl enable scan
#./Srvctl enable database-d orcl
#./Srvctl start listener
#./Srvctl start scan_listener
#./Srvctl start scan
#./Srvctl start database-d orcl

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/22435433J-11.png "height =" 259 "/>

650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px; "title =" image "border =" 0 "alt =" image "src =" http://www.bkjia.com/uploads/allimg/140207/2243546163-12.png "height =" 464 "/>

This article is from the "koumm linux technology blog" blog, please be sure to keep this source http://koumm.blog.51cto.com/703525/1353237