How to debugvip fault problems and troubleshooting VIP resources cannot be started due to missing gateways

How to debugvip fault problems and troubleshooting VIP resources cannot start due to lack of gateway problems: ----- view node application resources statistics: u01crsbinsrvctlconfignodeapps-ndbtest2-a-g-s-lVIPexists.: dbtest2-vip10.11.11.198255.255.255.0eri0GSDex

How to debug the vip fault and how to solve the problem that the VIP resource cannot be started due to the lack of Gateway: ----- view the node Application resource statistics: /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

Zookeeper how to debug vip fault problems and handle problems caused by lack of gateway VIP resources cannot be started

How to debug vip faults:

----- View node Application resource statistics:
/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

---------- Role of gateway in oracle rac 10g:
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: cocould 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
Variable FAIL_WHEN_DEFAULTGW_NOT_FOUND = 0.

3-start nodeapps and you shoshould see the resources ONLINE

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

Add Default Gateway

# Route add default gw 192.168.8.1