VIP FAILOVER DEMONSTRATION
2015-07-27 21:56
375 查看
Recently, a student of mine wanted me to demonstrate failover of VIP.
Here is the demonstration:
Current scenario:
2 node 11.2.0.1 RAC cluster with SCAN and GNS
nodes : host01, host02
Overview:
– check that VIP’s of both the nodes are running on respective nodes
— Stop clusterware on host01
— check that VIP of host01 has failed over to host02
— Trace route of request to connect to VIP of host01 and verify that connection is not made as listener on host02 accepts requests to its own VIP only
— Trace route of request to connect to VIP of host02 and verify that connection is made as listener on host02 accepts requests to host02’s VIP
— start clusterware on host01
— check that host01 vip is running on host01 again
— Trace route of request to connect to VIP of host01 and verify that connection is made as listener on host01 accepts requests to its own VIP
Implementation :
- check that VIP’s of both the nodes are running on respective nodes
- Stop clusterware on host01
- check that VIP of host01 (192.9.201.247) has failed over to host02
– Trace route of request to connect to VIP of host01 i.e. 192.9.201.147
– It can be seen there is no listener as listener on host02 accepts requests to host02’s VIP (192.9.201.235) only
– Trace route of request to connect to VIP of host02 i.e. 192.9.201.235
– It can be seen that connection is made as listener on host02 accepts requests to host02’s VIP
– start clusterware on host01
– check that host01 vip (192.9.201.147) is running on host01 again
– Trace route of request to connect to VIP of host01 i.e. 192.9.201.247
– It can be seen that connection is made as listener on host01 accepts requests to its own VIP
I hope this post was useful.
Your comments and suggestions are always welcome.
—————————————————————————————-
Related LInks:
Home
11g R2 RAC INDEX
Need For VIP In RAC
Here is the demonstration:
Current scenario:
2 node 11.2.0.1 RAC cluster with SCAN and GNS
nodes : host01, host02
Overview:
– check that VIP’s of both the nodes are running on respective nodes
— Stop clusterware on host01
— check that VIP of host01 has failed over to host02
— Trace route of request to connect to VIP of host01 and verify that connection is not made as listener on host02 accepts requests to its own VIP only
— Trace route of request to connect to VIP of host02 and verify that connection is made as listener on host02 accepts requests to host02’s VIP
— start clusterware on host01
— check that host01 vip is running on host01 again
— Trace route of request to connect to VIP of host01 and verify that connection is made as listener on host01 accepts requests to its own VIP
Implementation :
- check that VIP’s of both the nodes are running on respective nodes
[root@host02 ~]# srvctl status nodeapps -n host01 VIP 192.9.201.247 is enabled VIP 192.9.201.247 is running on node: host01 Network is enabled Network is running on node: host01 [root@host02 ~]# srvctl status nodeapps -n host02 VIP 192.9.201.235 is enabled VIP 192.9.201.235 is running on node: host02 Network is enabled Network is running on node: host02
- Stop clusterware on host01
[root@host01 ~]# crsctl stop crs
- check that VIP of host01 (192.9.201.247) has failed over to host02
[root@host02 ~]# srvctl status nodeapps -n host01 VIP 192.9.201.247 is enabled VIP 192.9.201.247 is running on node: host02 Network is enabled Network is not running on node: host01
– Trace route of request to connect to VIP of host01 i.e. 192.9.201.147
– It can be seen there is no listener as listener on host02 accepts requests to host02’s VIP (192.9.201.235) only
[root@host02 ~]# trcroute 192.9.201.247 Route of TrcRoute: ------------------ Node: Client Time and address of entry into node: ------------------------------------------------------------- 08-JAN-2014 14:14:39 ADDRESS= PROTOCOL=TCP HOST=192.9.201.247 PORT=1521 TNS-12224: TNS:no listener TNS-12541: TNS:no listener TNS-12560: TNS:protocol adapter error TNS-03601: Failed in route information collection
– Trace route of request to connect to VIP of host02 i.e. 192.9.201.235
– It can be seen that connection is made as listener on host02 accepts requests to host02’s VIP
[root@host02 ~]# trcroute 192.9.201.235 Route of TrcRoute: ------------------ Node: Client Time and address of entry into node: ------------------------------------------------------------- 08-JAN-2014 14:14:51 ADDRESS= PROTOCOL=TCP HOST=192.9.201.235 PORT=1521 Node: Server Time and address of entry into node: ------------------------------------------------------------- 08-JAN-2014 14:14:52 ADDRESS= PROTOCOL=TCP HOST=192.9.201.235 PORT=1521
– start clusterware on host01
[root@host01 ~]# crsctl start crs
– check that host01 vip (192.9.201.147) is running on host01 again
[root@host02 ~]# srvctl status nodeapps -n host01 VIP 192.9.201.247 is enabled VIP 192.9.201.247 is running on node: host01 Network is enabled Network is running on node: host01
– Trace route of request to connect to VIP of host01 i.e. 192.9.201.247
– It can be seen that connection is made as listener on host01 accepts requests to its own VIP
[root@host02 ~]# trcroute 192.9.201.247 Route of TrcRoute: ------------------ Node: Client Time and address of entry into node: ------------------------------------------------------------- 08-JAN-2014 14:23:00 ADDRESS= PROTOCOL=TCP HOST=192.9.201.247 PORT=1521 Node: Server Time and address of entry into node: ------------------------------------------------------------- 08-JAN-2014 14:23:00 ADDRESS= PROTOCOL=TCP HOST=192.9.201.247 PORT=1521
I hope this post was useful.
Your comments and suggestions are always welcome.
—————————————————————————————-
Related LInks:
Home
11g R2 RAC INDEX
Need For VIP In RAC
相关文章推荐
- 火车头采集器3.2SP5 VIP破解版附注册机下载
- [Oracle] Data Guard 之 浅析Switchover与Failover
- keepalived原理使用和配置
- Juniper ScreenOS下的MIP, VIP, DIP, NAT-src, NAT-dst区别
- ASA failover实例
- Setup Microsoft Windows 2008 R2 Failover Cluster in VMware Workstation
- Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
- 多个地市连接MQ,如果较长时间没有消息发送,ActiveMQ的消费端会自动断开连接(topic端)
- postgresql通过repmgr搭建standby
- Python 通过thrift接口连接Hbase读取存储数据
- “小”身份也有“大”权利!
- 有关SCAN与VIP的试验(一)
- ORACLE RAC Failover
- 迅雷高速通道破解教程
- 配置 RAC 负载均衡与故障转移
- 未配置默认网关导致RAC数据库VIP启动失败,节点重启
- Hadoop-2.4.1学习之使用Quorum Journal Manager的HDFS的高可用性(三)
- Hadoop-2.4.1学习之QJM HA的自动故障转移
- [Oracle] Data Guard 系列(6) - 角色转换
- [Oracle] RAC 之 - HA