--------------------------
修改vip为同网段(子网掩码不变)其它IP,公网网卡信息保持不变。
-----------------修改前:
192.168.57.216 bys1-vip.bys.com bys1-vip
192.168.57.218 bys2-vip.bys.com bys2-vip
-----------------修改后:
192.168.57.116 bys1-vip.bys.com bys1-vip
192.168.57.118 bys2-vip.bys.com bys2-vip
参考MOS文档:如何修改集群的公网信息(包括 VIP) (文档 ID 1674442.1)
--------目录
1.查看当前的VIP配置信息及集群及OS层面网卡信息
2.停止VIP资源并检查集群及OS层面网卡信息
3.修改/etc/hosts中记录(两个节点均修改)--IP由216改为116
4.修改OCR中VIP资源的信息--root用户
5.检查VIP资源信息并启动VIP资源及监听、数据库资源--如果数据库实例也关闭了
6.VIP配置信息及集群及OS层面网卡信息--VIP/监听均正常
7.修改ASM及数据库实例的local_listener参数
如果改完VIP后,重新启动了数据库实例,则不需要改数据库实例的local_listener参数。
在数据库实例(ASM实例由集群重启时同样)启动时,会自动使用OCR中的VIP信息来设置实例的local_listener参数。
以上的修改可以使用滚动的方式完成,例如:每次修改一个节点。
---------------------------
###########################
---------------------------
具体步骤:--仅显示节点1,节点2同样步骤。
1.查看当前的VIP配置信息及集群及OS层面网卡信息
[grid@bys1 ~]$ srvctl config nodeapps -a
Network exists: 1/192.168.57.0/255.255.255.0/eth0, type static
VIP exists: /bys1-vip/192.168.57.216/192.168.57.0/255.255.255.0/eth0, hosting node bys1
VIP exists: /bys2-vip/192.168.57.218/192.168.57.0/255.255.255.0/eth0, hosting node bys2
[grid@bys1 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.LISTENER.lsnr
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.asm
ONLINE ONLINE bys1 Started
ONLINE ONLINE bys2 Started
ora.gsd
OFFLINE OFFLINE bys1
OFFLINE OFFLINE bys2
ora.net1.network
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.ons
ONLINE ONLINE bys1
ONLINE ONLINE bys2
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1 ONLINE ONLINE bys1
ora.bys1.vip
1 ONLINE ONLINE bys1
ora.bys2.vip
1 ONLINE ONLINE bys2
ora.cvu
1 ONLINE ONLINE bys2
ora.oc4j
1 ONLINE ONLINE bys2
ora.scan1.vip
1 ONLINE ONLINE bys1
[grid@bys1 ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:29:4B:B4
inet addr:192.168.57.215 Bcast:192.168.57.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe29:4bb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:972 errors:0 dropped:0 overruns:0 frame:0
TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:143661 (140.2 KiB) TX bytes:54192 (52.9 KiB)
eth0:1 Link encap:Ethernet HWaddr 08:00:27:29:4B:B4
inet addr:192.168.57.216 Bcast:192.168.57.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
###############
2.停止VIP资源并检查集群及OS层面网卡信息
从 10.2.0.3 开始,ASM 和数据库实例对 VIP 资源的依赖关系已经被删除,所以修改 VIP 不需要停止 ASM 和数据库实例,只有当修改 VIP 时产生的客户端连接会受影响。如果修改只涉及到特定的节点,那么只有连接到对应节点的客户端链接在修改时会受影响。
---
[grid@bys1 ~]$ srvctl stop vip -n bys1 -f
[grid@bys1 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.LISTENER.lsnr
OFFLINE OFFLINE bys1 ------节点1的监听已经关闭--监听依赖于VIP资源
ONLINE ONLINE bys2
ora.asm
ONLINE ONLINE bys1 Started
ONLINE ONLINE bys2 Started
ora.gsd
OFFLINE OFFLINE bys1
OFFLINE OFFLINE bys2
ora.net1.network
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.ons
ONLINE ONLINE bys1
ONLINE ONLINE bys2
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1 ONLINE ONLINE bys1
ora.bys1.vip
1 OFFLINE OFFLINE ------节点1VIP资源已关闭
ora.bys2.vip
1 ONLINE ONLINE bys2
ora.cvu
1 ONLINE ONLINE bys2
ora.oc4j
1 ONLINE ONLINE bys2
ora.scan1.vip
1 ONLINE ONLINE bys1
[grid@bys1 ~]$ ifconfig --OS层面查看VIP的已经不存在
eth0 Link encap:Ethernet HWaddr 08:00:27:29:4B:B4
inet addr:192.168.57.215 Bcast:192.168.57.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe29:4bb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1081 errors:0 dropped:0 overruns:0 frame:0
TX packets:444 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:152176 (148.6 KiB) TX bytes:70753 (69.0 KiB)
eth0:2 Link encap:Ethernet HWaddr 08:00:27:29:4B:B4
inet addr:192.168.57.219 Bcast:192.168.57.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
###############
3.修改/etc/hosts中记录(两个节点均修改)--IP由216改为116
改之前
192.168.57.216 bys1-vip.bys.com bys1-vip
改之后
192.168.57.116 bys1-vip.bys.com bys1-vip
###############
4.修改OCR中VIP资源的信息--root用户
[root@bys1 ~]# srvctl modify nodeapps -n bys1 -A bys1-vip/255.255.255.0/eth0
###############
5.检查VIP资源信息并启动VIP资源及监听、数据库资源--如果数据库实例也关闭了
[grid@bys1 ~]$ srvctl config nodeapps -a
Network exists: 1/192.168.57.0/255.255.255.0/eth0, type static
VIP exists: /bys1-vip/192.168.57.116/192.168.57.0/255.255.255.0/eth0, hosting node bys1
VIP exists: /bys2-vip/192.168.57.218/192.168.57.0/255.255.255.0/eth0, hosting node bys2
[grid@bys1 ~]$ srvctl start vip -n bys1
[grid@bys1 ~]$ srvctl start listener -n bys1
###############
6.VIP配置信息及集群及OS层面网卡信息--VIP/监听均正常
[grid@bys1 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
NAME TARGET STATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.LISTENER.lsnr
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.asm
ONLINE ONLINE bys1 Started
ONLINE ONLINE bys2 Started
ora.gsd
OFFLINE OFFLINE bys1
OFFLINE OFFLINE bys2
ora.net1.network
ONLINE ONLINE bys1
ONLINE ONLINE bys2
ora.ons
ONLINE ONLINE bys1
ONLINE ONLINE bys2
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1 ONLINE ONLINE bys1
ora.bys1.vip
1 ONLINE ONLINE bys1
ora.bys2.vip
1 ONLINE ONLINE bys2
ora.cvu
1 ONLINE ONLINE bys2
ora.oc4j
1 ONLINE ONLINE bys2
ora.scan1.vip
1 ONLINE ONLINE bys1
[grid@bys1 ~]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:29:4B:B4
inet addr:192.168.57.215 Bcast:192.168.57.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe29:4bb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1424 errors:0 dropped:0 overruns:0 frame:0
TX packets:679 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:183151 (178.8 KiB) TX bytes:99652 (97.3 KiB)
eth0:1 Link encap:Ethernet HWaddr 08:00:27:29:4B:B4
inet addr:192.168.57.116 Bcast:192.168.57.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
###############
7.修改ASM及数据库实例的local_listener参数
如果改完VIP后,重新启动了数据库实例,则不需要改数据库实例的local_listener参数。
在数据库实例启动时,会自动使用OCR中的VIP信息来设置实例的local_listener参数。ALERT日志中输出如下:
Sun Nov 27 21:49:24 2016
ALTER SYSTEM SET local_listener=' (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.57.116)(PORT=1521))' SCOPE=MEMORY SID='bysrac1';
ALTER DATABASE MOUNT /* db agent *//* {1:30982:359} */
在集群重启,ASM实例也重启时,会自动使用OCR中的VIP信息来设置实例的local_listener参数。ALERT日志中有如下输出:
Sun Nov 27 21:57:04 2016
ALTER SYSTEM SET local_listener=' (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.57.116)(PORT=1521))))' SCOPE=MEMORY SID='+ASM1';
建议检查local_listener参数,如ASM未重启,需要手动设置:
alter system set local_listener='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.57.116)(PORT=1521)))';
-------------检查监听状态
[grid@bys1 ~]$ lsnrctl status