Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

"No route to Host" network issue preventing RAC installation

WilhelmJul 27 2015 — edited Jul 28 2015

Oracle Linux : 6.6

Grid Infra version: 11.2.0.4

Virtual Box : 4.3.28 (on Win 7 Host)

I am trying to Install a 2-node RAC in VMs created in VirtualBox. But the cluvfy check is failing for both my Public and Private networks with "No route to Host" error  as shown below.

ping between both nodes work without any latency. passwordless ssh is configured succesfully.

I have a dedicated DNS server (10.194.135.185). nslookups of SCAN, Public and VIPs are working fine.

Googling didn't help much . Hence posting it here

==== Error from cluvfy start

Check: TCP connectivity of subnet "10.194.135.0"

  Source                          Destination                     Connected?

  ------------------------------  ------------------------------  ----------------

  brcpda178 : 10.194.135.178      brcpda178 : 10.194.135.178      passed

  brcpda179 : 10.194.135.179      brcpda178 : 10.194.135.178      passed

  brcpda178 : 10.194.135.178      brcpda179 : 10.194.135.179      failed

ERROR:

PRVG-11850 : The system call "connect" failed with error "113" while executing exectask on node "brcpda178"

No route to host

  brcpda179 : 10.194.135.179      brcpda179 : 10.194.135.179      passed

Result: TCP connectivity check failed for subnet "10.194.135.0"

Check: Node connectivity of subnet "169.182.16.0"

  Source                          Destination                     Connected?

  ------------------------------  ------------------------------  ----------------

  brcpda178[169.182.16.24]        brcpda179[169.182.16.25]        yes

Result: Node connectivity passed for subnet "169.182.16.0" with node(s) brcpda178,brcpda179

Check: TCP connectivity of subnet "169.182.16.0"

  Source                          Destination                     Connected?

  ------------------------------  ------------------------------  ----------------

  brcpda178 : 169.182.16.24       brcpda178 : 169.182.16.24       passed

  brcpda179 : 169.182.16.25       brcpda178 : 169.182.16.24       passed

  brcpda178 : 169.182.16.24       brcpda179 : 169.182.16.25       failed

ERROR:

PRVG-11850 : The system call "connect" failed with error "113" while executing exectask on node "brcpda178"

No route to host

  brcpda179 : 169.182.16.25       brcpda179 : 169.182.16.25       passed

Result: TCP connectivity check failed for subnet "169.182.16.0"

====== Error end

#### Below is my network configuration.

I have created 2 virtual adaptors at host (Host-only network) .

ipconfig Output from Host (Windows 7)

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::7930:46e8:a531:289%24

   IPv4 Address. . . . . . . . . . . : 10.194.135.1

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network #2:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::b43f:3255:b3d0:70eb%30

   IPv4 Address. . . . . . . . . . . : 169.182.16.1

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . :

10.194.135.0 will be my Public network ----> eth0 in each node

169.182.16.0 will be my Private network ----> eth1 in each node

Following is my /etc/hosts file

[grid@brcpda178 grid]$ cat /etc/hosts

10.194.135.185          dnsnode185

####### Public IP ###############

10.194.135.178      brcpda178.testenv.com    brcpda178

10.194.135.179      brcpda179.testenv.com    brcpda179

#### Private IP ###############

169.182.16.24  brcpda178-priv.testenv.com brcpda178-priv

169.182.16.25  brcpda179-priv.testenv.com brcpda179-priv

##### Virtual IP ##############3

10.194.135.217 brcpda178-oravip.testenv.com brcpda178-oravip

10.194.135.218 brcpda179-oravip.testenv.com brcpda179-oravip

#127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4

#::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

Following are configuration files for network interfaces in each RAC node.

GATEWAY value in /etc/sysconfig/network-scripts/ifcfg-ethn file is set to the IP of virtual NIC adaptor at host (win7) level.

Node2 was cloned out of Node1 . So, the UUID of eth0 and eth1 remains the same for both the nodes . Hope this is not an issue because HWADDR (MAC ID) is different between the nodes.

brcpda178 (Node1)

eth0

=====

# cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0

TYPE=Ethernet

UUID=2ca3918d-d038-483d-946a-271751aeb11f

ONBOOT=yes

NM_CONTROLLED=yes

BOOTPROTO=none

HWADDR=08:00:27:17:91:24

IPADDR=10.194.135.178

PREFIX=24

GATEWAY=10.194.135.1

DEFROUTE=yes

IPV4_FAILURE_FATAL=yes

IPV6INIT=no

NAME="System eth0"

eth1

====

# cat /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1

TYPE=Ethernet

UUID=dc9be031-ee5f-4129-9023-9c45f6a282da

ONBOOT=yes

NM_CONTROLLED=yes

BOOTPROTO=none

HWADDR=08:00:27:01:FC:38

IPADDR=169.182.16.24

PREFIX=24

GATEWAY=169.182.16.1

DEFROUTE=yes

IPV4_FAILURE_FATAL=yes

IPV6INIT=no

NAME="System eth1"

brcpda179 (Node2)

eth0

====

# cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0

TYPE=Ethernet

UUID=2ca3918d-d038-483d-946a-271751aeb11f

ONBOOT=yes

NM_CONTROLLED=yes

BOOTPROTO=none

HWADDR=08:00:27:A9:68:39

IPADDR=10.194.135.179

PREFIX=24

GATEWAY=10.194.135.1

DEFROUTE=yes

IPV4_FAILURE_FATAL=yes

IPV6INIT=no

NAME="System eth0"

eth1

====

# cat /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1

TYPE=Ethernet

UUID=dc9be031-ee5f-4129-9023-9c45f6a282da

ONBOOT=yes

NM_CONTROLLED=yes

BOOTPROTO=none

HWADDR=08:00:27:05:A5:45

IPADDR=169.182.16.25

PREFIX=24

GATEWAY=169.182.16.1

DEFROUTE=yes

IPV4_FAILURE_FATAL=yes

IPV6INIT=no

NAME="System eth1"

This post has been answered by Salman Qureshi on Jul 28 2015
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 25 2015
Added on Jul 27 2015
8 comments
5,743 views