[INS-41112] Specified network interface doesnt maintain connectivity across cluster nodes
issue and solution 01:-
restart both node and excute below command..
[oracle@node02 grid]$ ./runcluvfy.sh comp nodecon -n node01,node02 -verbose
Verifying node connectivity
Checking node connectivity...
Checking hosts config file...
Node Name Status
------------------------------------ ------------------------
node02 passed
node01 passed
Verification of the hosts config file successful
Interface information for node "node02"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
eth0 192.168.132.180 192.168.132.0 0.0.0.0 192.168.132.2 00:50:56:25:A2:E2 1500
eth1 192.168.223.180 192.168.223.0 0.0.0.0 192.168.132.2 00:50:56:28:FE:F1 1500
Interface information for node "node01"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
eth1 192.168.223.182 192.168.223.0 0.0.0.0 192.168.132.2 00:50:56:35:72:E6 1500
eth0 192.168.132.182 192.168.132.0 0.0.0.0 192.168.132.2 00:50:56:31:79:FD 1500
Check: Node connectivity of subnet "192.168.132.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02[192.168.132.180] node01[192.168.132.182] yes
Result: Node connectivity passed for subnet "192.168.132.0" with node(s) node02,node01
Check: TCP connectivity of subnet "192.168.132.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02:192.168.132.180 node01:192.168.132.182 passed
Result: TCP connectivity check passed for subnet "192.168.132.0"
Check: Node connectivity of subnet "192.168.223.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02[192.168.223.180] node01[192.168.223.182] yes
Result: Node connectivity passed for subnet "192.168.223.0" with node(s) node02,node01
Check: TCP connectivity of subnet "192.168.223.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02:192.168.223.180 node01:192.168.223.182 passed
Result: TCP connectivity check passed for subnet "192.168.223.0"
Interfaces found on subnet "192.168.132.0" that are likely candidates for VIP are:
node02 eth0:192.168.132.180
node01 eth0:192.168.132.182
Interfaces found on subnet "192.168.223.0" that are likely candidates for a private interconnect are:
node02 eth1:192.168.223.180
node01 eth1:192.168.223.182
Checking subnet mask consistency...
Subnet mask consistency check passed for subnet "192.168.132.0".
Subnet mask consistency check passed for subnet "192.168.223.0".
Subnet mask consistency check passed.
Result: Node connectivity check passed
Verification of node connectivity was successful.
issue and solution node2:-
check owner of 'CVU_11.2.0.3.0_oracle' location /tmp
[root@node01 tmp]# ls -ltr
total 56
drwx------ 2 root root 16384 Jul 16 21:08 lost+found
drwxr-xr-x 3 502 oinstall 4096 Jul 24 21:26 OraInstall2016-07-24_09-24-01PM
drwxr-xr-x 3 502 oinstall 4096 Jul 24 21:33 CVU_11.2.0.3.0_oracle
-rwxr-xr-x 1 root root 8551 Jul 24 21:47 cvuqdisk-1.0.9-1.rpm
drwxr-xr-x 3 oracle oinstall 4096 Jul 24 22:23 OraInstall2016-07-24_10-21-53PM
drwxr-xr-x 3 oracle oinstall 4096 Jul 24 22:42 OraInstall2016-07-24_10-40-33PM
srwxr-xr-x 1 root root 0 Jul 24 22:51 mapping-root
drwx------ 2 root root 4096 Jul 24 22:59 gconfd-root
drwxr-xr-x 3 oracle oinstall 4096 Jul 24 23:03 OraInstall2016-07-24_11-02-03PM
[root@node01 tmp]# chown -R oracle:oinstall OraInstall2016-07-24_09-24-01PM
[root@node01 tmp]# chown -R oracle:oinstall CVU_11.2.0.3.0_oracle
[oracle@node02 grid]$ ./runcluvfy.sh comp nodecon -n node01,node02 -verbose
Verifying node connectivity
Checking node connectivity...
Checking hosts config file...
Node Name Status
------------------------------------ ------------------------
node02 passed
node01 passed
Verification of the hosts config file successful
Interface information for node "node02"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
eth0 192.168.132.180 192.168.132.0 0.0.0.0 192.168.132.2 00:50:56:25:A2:E2 1500
eth1 192.168.223.180 192.168.223.0 0.0.0.0 192.168.132.2 00:50:56:28:FE:F1 1500
Interface information for node "node01"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
eth1 192.168.223.182 192.168.223.0 0.0.0.0 192.168.132.2 00:50:56:35:72:E6 1500
eth0 192.168.132.182 192.168.132.0 0.0.0.0 192.168.132.2 00:50:56:31:79:FD 1500
Check: Node connectivity of subnet "192.168.132.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02[192.168.132.180] node01[192.168.132.182] yes
Result: Node connectivity passed for subnet "192.168.132.0" with node(s) node02,node01
Check: TCP connectivity of subnet "192.168.132.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02:192.168.132.180 node01:192.168.132.182 passed
Result: TCP connectivity check passed for subnet "192.168.132.0"
Check: Node connectivity of subnet "192.168.223.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02[192.168.223.180] node01[192.168.223.182] yes
Result: Node connectivity passed for subnet "192.168.223.0" with node(s) node02,node01
Check: TCP connectivity of subnet "192.168.223.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
node02:192.168.223.180 node01:192.168.223.182 passed
Result: TCP connectivity check passed for subnet "192.168.223.0"
Interfaces found on subnet "192.168.132.0" that are likely candidates for VIP are:
node02 eth0:192.168.132.180
node01 eth0:192.168.132.182
Interfaces found on subnet "192.168.223.0" that are likely candidates for a private interconnect are:
node02 eth1:192.168.223.180
node01 eth1:192.168.223.182
Checking subnet mask consistency...
Subnet mask consistency check passed for subnet "192.168.132.0".
Subnet mask consistency check passed for subnet "192.168.223.0".
Subnet mask consistency check passed.
Result: Node connectivity check passed
Verification of node connectivity was successful.
