oracle11g R2:node Connectivity check failed solution ____oracle

Source: Internet
Author: User

Copyright notice: When reprinted, please indicate the original source and author information of the article by hyperlink form and this statement
http://blog.csdn.net/wenshuangzhu/article/details/46226179


The "Node connectivity check failed" is prompted at the Oracle11gr2 graphical interface for installation checks, as shown in the following illustration:




There are two main reasons for this problem on the Internet:

1./etc/hosts didn't match up.
Firewall not closed in 2.Linux

But my firewall is closed, the Hosts file is also determined to configure well.

Check with the Runcluvfy tool:

grid@node74:/home/software/linux_11gr2/grid>./runcluvfy.sh stage-post hwos-n Node74,node76-verbose

Performing post-checks for hardware and operating system setup


Checking node reachability ...
Check:node reachability from Node "Node74"
Destination Node reachable?
------------------------------------  ------------------------
Node74 Yes
node76 Yes
Result:node reachability check passed from Node "Node74"

Checking User Equivalence ...
Check:user equivalence for User "grid"
Node Name Comment
------------------------------------  ------------------------
Node76 passed
Node74 passed
Result:user equivalence check passed for User "grid"

Checking Node Connectivity ...
Checking hosts config file ...
Node Name Status Comment
------------  ------------------------  ------------------------
Node76 passed
Node74 passed

Verification of the hosts config file successful

Interface Information for node "node76"
Name IP address Subnet Gateway DEF. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
Eth0 172.16.54.76 172.16.52.0 0.0.0.0 172.16.52.254 b4:99:ba:bc:31:4a 1500
Eth0 172.16.54.176 172.16.52.0 0.0.0.0 172.16.52.254 b4:99:ba:bc:31:4a 1500
eth1 10.10.10.2 10.10.10.0 0.0.0.0 172.16.52.254 b4:99:ba:bc:31:4c 1500
Eth2 20.20.20.2 20.20.20.0 0.0.0.0 172.16.52.254 b4:99:ba:bc:31:4e 1500

Interface Information for node "Node74"
Name IP address Subnet Gateway DEF. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
Eth0 172.16.54.74 172.16.52.0 0.0.0.0 172.16.52.254 98:4b:e1:04:c7:b4 1500
Eth0 172.16.54.174 172.16.52.0 0.0.0.0 172.16.52.254 98:4b:e1:04:c7:b4 1500
Eth0 172.16.54.175 172.16.52.0 0.0.0.0 172.16.52.254 98:4b:e1:04:c7:b4 1500
eth1 10.10.10.1 10.10.10.0 0.0.0.0 172.16.52.254 98:4b:e1:04:c7:b6 1500
Eth2 20.20.20.1 20.20.20.0 0.0.0.0 172.16.52.254 98:4b:e1:04:c7:b8 1500

Check:node connectivity of subnet "172.16.52.0"
Source destination Connected?
------------------------------  ------------------------------  ----------------
Node76:eth0 Node76:eth0 Yes
Node76:eth0 Node74:eth0 Yes
Node76:eth0 Node74:eth0 Yes
Node76:eth0 Node74:eth0 Yes
Node76:eth0 Node74:eth0 Yes
Node76:eth0 Node74:eth0 Yes
Node76:eth0 Node74:eth0 Yes
Node74:eth0 Node74:eth0 Yes
Node74:eth0 Node74:eth0 Yes
Node74:eth0 Node74:eth0 Yes
Result:node connectivity passed for subnet ' 172.16.52.0 ' with Node (s) node76,node74

CHECK:TCP connectivity of subnet "172.16.52.0"
Source destination Connected?
------------------------------  ------------------------------  ----------------
node74:172.16.54.74 node76:172.16.54.76 passed
node74:172.16.54.74 node76:172.16.54.176 passed
node74:172.16.54.74 node74:172.16.54.174 passed
node74:172.16.54.74 node74:172.16.54.175 passed
RESULT:TCP connectivity check passed for subnet "172.16.52.0"

Check:node connectivity of subnet "10.10.10.0"
Source destination Connected?
------------------------------  ------------------------------  ----------------
Node76:eth1 node74:eth1 Yes
Result:node connectivity passed for subnet ' 10.10.10.0 ' with Node (s) node76,node74

CHECK:TCP connectivity of subnet "10.10.10.0"
Source destination Connected?
------------------------------  ------------------------------  ----------------
node74:10.10.10.1 node76:10.10.10.2 passed
RESULT:TCP connectivity check passed for subnet "10.10.10.0"

Check:node connectivity of subnet "20.20.20.0"

WARNING:
Make sure IP address "20.20.20.1" are up and are a valid IP address on node "Node74"
Source destination Connected?
------------------------------  ------------------------------  ----------------
Node76:eth2 Node74:eth2 No
Result:node connectivity failed for subnet "20.20.20.0"

CHECK:TCP connectivity of subnet "20.20.20.0"
Source destination Connected?
------------------------------  ------------------------------  ----------------
node74:20.20.20.1 node76:20.20.20.2 failed------Note: Two nodes have a set of network cards configured with the same network segment of IP, but no unicom, resulting node Connectivity check failed.
RESULT:TCP connectivity check failed for subnet "20.20.20.0"

Interfaces found on subnet "172.16.52.0" which are likely for VIP candidates:
node76 eth0:172.16.54.76 eth0:172.16.54.176
Node74 eth0:172.16.54.74 eth0:172.16.54.174 eth0:172.16.54.175

Interfaces found on subnet "10.10.10.0" which are likely candidates for a private interconnect are:
Node76 eth1:10.10.10.2
Node74 eth1:10.10.10.1

Result:node Connectivity Check failed

Checking for multiple users with UID value 0
Result:check for multiple users with UID value 0 passed

Post-check for hardware and operating system setup is unsuccessful on all the nodes.

The original is because two nodes have a pair of network cards configured through the network segment IP address, but in fact, two network cards are not connected, resulting in node connectivity check failed.

CHECK:TCP connectivity of subnet "20.20.20.0"
Source destination Connected?
------------------------------  ------------------------------  ----------------
node74:20.20.20.1 node76:20.20.20.2 failed


This solution is available, or is to connect two network cards, or to change to different network segments, or simply disable the two network cards directly.

After I deactivate the two network adapters, I'll run the installation check again.



Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.