如何debugvip故障问题及处理因为网关缺失导致VIP资源无法启动

如何debug vip故障问题及处理因为网关缺失导致VIP资源无法启动 如何debug vip故障问题： -----查看节点应用资源的统计信息: /u01/crs/bin/srvctl config nodeapps -n dbtest2 -a -g -s -l VIP exists.: /dbtest2-vip/10.11.11.198/255.255.255.0/eri0 GSD ex



如何debug vip故障问题及处理因为网关缺失导致VIP资源无法启动

如何debug vip故障问题：

-----查看节点应用资源的统计信息:
/u01/crs/bin/srvctl config nodeapps -n dbtest2 -a -g -s -l
VIP exists.: /dbtest2-vip/10.11.11.198/255.255.255.0/eri0
GSD exists.
ONS daemon exists.
Listener does not exist.

------debug vip
Further debug it by uncommenting the environment variable _USR_ORA_DEBUG=1 in the script $ORA_CRS_HOME/bin/racgvip

OR simply as root user, issue the command :
crsctl debug log res "ora.dbtest2.vip:5"

You may turn off debugging with command :
crsctl debug log res "ora.dbtest2.vip:0"

Start the VIP using srvctl start nodeapps again. This will create a log for VIP starting problem for 10.2 and above version
in directory $ORA_CRS_HOME/log//racg/*vip.log

----------oracle rac 10g 中 网关 gateway 的作用：
By default, the server's default gateway is used as a ping target during the Oracle RAC 10g VIP status check action.
Upon a ping failure, Oracle will decide that the current interface where the VIP is running has failed, and will initiate an interface / internode VIP failover.

In above case, we used just one node for CRS installation, so the VIP coudn't failover to other nodes and thus reported additional error like :
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.dbtest2.vip'.

--------SOLUTION
10.1.0.4 and above introduced a parameter FAIL_WHEN_DEFAULTGW_NOT_FOUND in the file
$ORA_CRS_HOME/bin/racvip to address this problem.

The following steps will fix the VIP starting problem for above mentioned scenario.

1- stop nodeapps

2- As root,
vi the script $ORA_CRS_HOME/bin/racgvip and change the value of
variable FAIL_WHEN_DEFAULTGW_NOT_FOUND=0 .

3- start nodeapps and you should see the resources ONLINE

You may proceed with netca and dbca to create a RAC database after this.

添加默认网关

#route add default gw 192.168.8.1