[Solved] A connectivity issue using host-only network adapter

Discussions about using Linux guests in VirtualBox.
Post Reply
2tea22
Posts: 6
Joined: 25. Dec 2013, 15:56

[Solved] A connectivity issue using host-only network adapter

Post by 2tea22 »

Hello everybody,

I was trying to follow the following tutorials to create Oracle two nodes RAC demo using virtual box although I have encountered a number of networking issues that do not allow me completing it. My host is Windows 2008 pro. I created two vms with Oracle Linux 6.5 on them.

Here are the networking details:

1) Host

C:\Users\Administrator>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dstch.com
IPv4 Address. . . . . . . . . . . : 192.168.168.111
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.168.168

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::454a:61c5:3acd:6e55%16
IPv4 Address. . . . . . . . . . . : 192.168.56.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{AAECA17B-4F67-4AA6-92BE-5F79E30F8D86}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.dstch.com:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : dstch.com

2) vm 1

[root@ol6-121-rac1 Desktop]# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:54:2E:96
inet6 addr: fe80::a00:27ff:fe54:2e96/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:258 (258.0 b)

eth1 Link encap:Ethernet HWaddr 08:00:27:92:FB:01
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe92:fb01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:520 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3737 (3.6 KiB) TX bytes:48760 (47.6 KiB)

eth2 Link encap:Ethernet HWaddr 08:00:27:87:C1:9F
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe87:c19f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4800 (4.6 KiB) TX bytes:1128 (1.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB)

2) vm 2

[root@ol6-121-rac1 Desktop]# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:54:2E:96
inet6 addr: fe80::a00:27ff:fe54:2e96/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:258 (258.0 b)

eth1 Link encap:Ethernet HWaddr 08:00:27:92:FB:01
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe92:fb01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:520 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3737 (3.6 KiB) TX bytes:48760 (47.6 KiB)

eth2 Link encap:Ethernet HWaddr 08:00:27:87:C1:9F
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe87:c19f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4800 (4.6 KiB) TX bytes:1128 (1.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1168 (1.1 KiB) TX bytes:1168 (1.1 KiB)

The issue:
From the first vm I can ping the host: 192.168.56.1 but cannot ping the second node 192.168.56.102

From the second vm I cannot ping the host or the firs vm: 192.168.56.101

The firewalls are disabled on all three servers. I did create a host only network and enabled it:

Make sure that the information is as follows.

Adapter address 192.168.56.1
Mask 255.255.255.0

Address 192.168.56.100
mask 255.255.255.0
Lower address 192.168.56.101
Upper address 192.168.56.254

Please help me troubleshooting this problem.

Thank you,
MM
Top
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: A connectivity issue using host-only network adapter

Post by socratis »

2tea22 wrote:2) vm 1
eth1 Link encap:Ethernet HWaddr 08:00:27:92:FB:01
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
2tea22 wrote:2) vm 2
eth1 Link encap:Ethernet HWaddr 08:00:27:92:FB:01
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
Unless you posted the wrong 'ifconfig' information, it seems that both your VMs have the same MAC address (08:00:27:92:FB:01) and get the same IP address (192.168.56.101). It looks like you cloned the VMs and you forgot to re-initialize the MAC addresses.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Top
2tea22
Posts: 6
Joined: 25. Dec 2013, 15:56

Re: A connectivity issue using host-only network adapter

Post by 2tea22 »

You are right socratis! That's it. Thank you very much!
Top
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: A connectivity issue using host-only network adapter

Post by socratis »

I should have added in my previous post the instructions on how to change the MAC addresses. Just pick VM2, go to VM Settings, Network, Advanced and click the icon that looks like a blueish circle with two arrows (any better way to describe that?) to re-generate a random MAC.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Top
2tea22
Posts: 6
Joined: 25. Dec 2013, 15:56

Re: [Solved] A connectivity issue using host-only network adapter

Post by 2tea22 »

after refreshing the mac addresses, I was able to ping the host and the nodes as well, although the network cards appeared as eth7, 8, 9
After updating HWADDR to the new mac addresses in /etc/sysconfig/network-scripts/ifcfg-eth0, 1, 2 the network adapters showed up correctly in ifconfig output but the communication was interrupted again....

[root@ol6-121-rac2 Desktop]# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:CD:36:B9
inet6 addr: fe80::a00:27ff:fecd:36b9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:10224 (9.9 KiB)

eth1 Link encap:Ethernet HWaddr 08:00:27:5C:C7:1B
inet addr:192.168.56.102 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe5c:c71b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:5808 (5.6 KiB)

eth2 Link encap:Ethernet HWaddr 08:00:27:B8:2D:62
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:feb8:2d62/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:131 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7860 (7.6 KiB) TX bytes:1058 (1.0 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5664 (5.5 KiB) TX bytes:5664 (5.5 KiB)
Top
2tea22
Posts: 6
Joined: 25. Dec 2013, 15:56

Re: [Solved] A connectivity issue using host-only network adapter

Post by 2tea22 »

ifconfig -a | grep eth
[root@ol6-121-rac2 Desktop]# ifconfig -a | grep eth
eth0 Link encap:Ethernet HWaddr 08:00:27:CD:36:B9
eth1 Link encap:Ethernet HWaddr 08:00:27:5C:C7:1B
eth2 Link encap:Ethernet HWaddr 08:00:27:B8:2D:62

/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=yes
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
HWADDR=08:00:27:CD:36:B9
BOOTPROTO=dhcp
PEERDNS=yes
PEERROUTES=yes
~
/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=yes
DNS1=192.169.56.1
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth1"
DOMAIN=localdomain
HWADDR=08:00:27:5C:C7:1B
BOOTPROTO=none
IPADDR=192.168.56.102
PREFIX=24
GATEWAY=192.168.56.1
LAST_CONNECT=1464103027
~
/etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
TYPE=Ethernet
UUID=da70f213-b790-4471-805e-d69fafabc30c
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=none
IPADDR=192.168.1.102
PREFIX=24
DEFROUTE=no
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth2"
HWADDR=08:00:27:B8:2D:62
LAST_CONNECT=1464093043

PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
From 192.168.56.102 icmp_seq=1 Destination Host Unreachable
From 192.168.56.102 icmp_seq=2 Destination Host Unreachable
From 192.168.56.102 icmp_seq=3 Destination Host Unreachable
From 192.168.56.102 icmp_seq=4 Destination Host Unreachable
From 192.168.56.102 icmp_seq=5 Destination Host Unreachable
From 192.168.56.102 icmp_seq=6 Destination Host Unreachable
Top
Post Reply

Return to “Linux Guests”