Why Oracle VIP can not be switched to original node ?

Oracle RAC is an share everything database architecture.

The article is how to check out why virtual ip can not be switched to original version. You also see clearly if you have known a little about
Oracle.

Here is begin:

RAC cluster status is:

/oracle/product/10.2.0/crs/bin #./crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.bis.db application OFFLINE OFFLINE
ora....S3.lsnr application ONLINE OFFLINE
ora....is3.gsd application ONLINE ONLINE bis3
ora....is3.ons application ONLINE ONLINE bis3
ora....is3.vip application ONLINE ONLINE bis4
ora....S4.lsnr application ONLINE ONLINE bis4
ora....is4.gsd application ONLINE ONLINE bis4
ora....is4.ons application ONLINE ONLINE bis4
ora....is4.vip application ONLINE ONLINE bis4
It should be all ONLINE status. What happen ? I shut it down and started up again about Oracle RAC cluster CSR
/oracle/product/10.2.0/crs/bin/./crsctl start CSR
However, that was still same.
After checking crs log, I found this.
2017-01-08 16:52:10.193: [ CRSRES][11066]32Attempting to start `ora.bis3.vip` on member `bis4`
2017-01-08 16:52:12.905: [ CRSRES][11066]32Start of `ora.bis3.vip` on member `bis4` succeeded.
2017-01-08 16:52:12.960: [ CRSRES][11066]32StopResource: setting CLI values
2017-01-08 16:52:12.973: [ CRSRES][11066]32Attempting to stop `ora.bis3.vip` on member `bis4`
2017-01-08 16:52:13.421: [ CRSRES][11066]32Stop of `ora.bis3.vip` on member `bis4` succeeded.
2017-01-08 16:52:13.433: [ CRSRES][11066]32startRunnable: setting CLI values
2017-01-08 16:52:13.433: [ CRSRES][11066]32Attempting to start `ora.bis3.vip` on member `bis3`
2017-01-08 16:52:16.018: [ CRSAPP][11066]32StartResource error for ora.bis3.vip error code = 1
2017-01-08 16:52:16.475: [ CRSRES][11066]32Start of `ora.bis3.vip` on member `bis3` failed.
2017-01-08 16:52:16.526: [ CRSRES][11066]32Attempting to start `ora.bis3.vip` on member `bis4`
2017-01-08 16:52:19.305: [ CRSRES][11066]32Start of `ora.bis3.vip` on member `bis4` succeeded.
2017-01-08 16:52:19.359: [ CRSRES][11074]32startRunnable: setting CLI values
2017-01-08 16:52:19.381: [ CRSRES][11843]32startRunnable: setting CLI values
2017-01-08 16:52:19.392: [ CRSRES][11074]32Attempting to start `ora.bis3.gsd` on member `bis3`
2017-01-08 16:52:19.399: [ CRSRES][11843]32Attempting to start `ora.bis3.ons` on member `bis3`
2017-01-08 16:52:21.282: [ CRSRES][11843]32Start of `ora.bis3.ons` on member `bis3` succeeded.
2017-01-08 16:52:21.767: [ CRSRES][11074]32Start of `ora.bis3.gsd` on member `bis3` succeeded.
2017-01-08 16:53:31.417: [ CRSRES][11079]32 startup = 0
2017-01-08 16:53:31.481: [ CRSRES][11848]32StopResource: setting CLI values
2017-01-08 16:53:31.497: [ CRSRES][11848]32Attempting to stop `ora.bis3.vip` on member `bis4`
2017-01-08 16:53:31.967: [ CRSRES][11848]32Stop of `ora.bis3.vip` on member `bis4` succeeded.
2017-01-08 16:53:31.980: [ CRSRES][11848]32startRunnable: setting CLI values
2017-01-08 16:53:31.980: [ CRSRES][11848]32Attempting to start `ora.bis3.vip` on member `bis3`
2017-01-08 16:53:34.569: [ CRSAPP][11848]32StartResource error for ora.bis3.vip error code = 1
2017-01-08 16:53:35.031: [ CRSRES][11848]32Start of `ora.bis3.vip` on member `bis3` failed.
2017-01-08 16:53:35.194: [ CRSRES][11848]32Attempting to start `ora.bis3.vip` on member `bis4`
2017-01-08 16:53:37.909: [ CRSRES][11848]32Start of `ora.bis3.vip` on member `bis4` succeeded.
2017-01-08 16:53:37.969: [ CRSRES][11848]32StopResource: setting CLI values
2017-01-08 16:53:37.984: [ CRSRES][11848]32Attempting to stop `ora.bis3.vip` on member `bis4`
2017-01-08 16:53:38.442: [ CRSRES][11848]32Stop of `ora.bis3.vip` on member `bis4` succeeded.
2017-01-08 16:53:38.455: [ CRSRES][11848]32startRunnable: setting CLI values
2017-01-08 16:53:38.456: [ CRSRES][11848]32Attempting to start `ora.bis3.vip` on member `bis3`
2017-01-08 16:53:41.042: [ CRSAPP][11848]32StartResource error for ora.bis3.vip error code = 1
2017-01-08 16:53:41.491: [ CRSRES][11848]32Start of `ora.bis3.vip` on member `bis3` failed.
2017-01-08 16:53:41.543: [ CRSRES][11848]32Attempting to start `ora.bis3.vip` on member `bis4`
2017-01-08 16:53:44.306: [ CRSRES][11848]32Start of `ora.bis3.vip` on member `bis4` succeeded.

all services are OK. Why ?

node which status is OK network setting

ifconfig -a
en10: flags=1e084863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 10.10.1.99 netmask 0xffffff00 broadcast 10.10.1.255
en8: flags=1e084863,8c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 150.150.187.27 netmask 0xffffff00 broadcast 150.150.187.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
en9: flags=1e084863,8c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 192.168.141.10 netmask 0xffffff00 broadcast 192.168.141.255
inet 192.168.141.9 netmask 0xffffff00 broadcast 192.168.141.255
inet 192.168.141.8 netmask 0xffffff00 broadcast 192.168.141.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1

node which status is failed network setting
ifconfig -a
en10: flags=5e084863,18c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 10.10.1.98 netmask 0xffffff00 broadcast 10.10.1.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
en6: flags=1e084863,8c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 150.150.187.34 netmask 0xffffff00 broadcast 150.150.187.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
en8: flags=1e084863,8c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 192.168.141.26 netmask 0xffffff00 broadcast 192.168.141.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
Yes, that red marked is why. The network card name is different. It`s name should be same is RAC system on each node.
So, solution is to change the networke card name from en8 to en9 if we get permittion.

RAC: Frequently Asked Questions (RAC FAQ) ( Doc ID 220970.1 )

Can the Network Interface Card (NIC) device names be different on the nodes in a cluster, for both public and private?

All public NICs must have the same name on all nodes in the cluster

Similarly, all private NICs must also have the same names on all nodes
Thanks is all.