Page 1 of 1

Cannot ping eth2 after cloning

Posted: 9. Oct 2013, 15:21
by gbite
Hello Gurus,

My Setup
-----------
Guest created in VBox on Windows 7
Guest allocated 3 network adapters - NAT(dhcp),HO(192.168.56.11) and internal (10.10.10.11)
OEL6 installed in it (lots of processes to make Oracle rac work undertaken)

I have successfully cloned my guest called rac1 to rac2 as part of my trial implementation of Oracle RAC 12 on VBox and updated the hostname and the ifcfg files with the new MAC addresses etc.

Now ping the machines on the 192.168.56.xx works for the eth1 addresses but I can not ping successfully on the eth2 subnet i.e 10.10.10.11.

The only difference I noticed when I do ifconfig -a on the 2 guest is that the clone i.e rac2 is missing the line:
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0.

Could this be the problem? How do I fix this?


rac1
------[oracle@rac1 Desktop]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:55:27:1C
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe55:271c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1180 (1.1 KiB) TX bytes:5033 (4.9 KiB)

eth1 Link encap:Ethernet HWaddr 08:00:27:2A:0C:B5
inet addr:192.168.56.11 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe2a:cb5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:193 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23168 (22.6 KiB) TX bytes:6196 (6.0 KiB)

eth2 Link encap:Ethernet HWaddr 08:00:27:CE:3F:A2
inet addr:10.10.10.11 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::a00:27ff:fece:3fa2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 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:3078 (3.0 KiB) TX bytes:4677 (4.5 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:16436 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0



rac2
------
[oracle@rac2 Desktop]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:BD:5C:66
inet6 addr: fe80::a00:27ff:febd:5c66/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:360 (360.0 b) TX bytes:3726 (3.6 KiB)

eth1 Link encap:Ethernet HWaddr 08:00:27:F1:AD:FA
inet addr:192.168.56.12 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fef1:adfa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:124 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12611 (12.3 KiB) TX bytes:5356 (5.2 KiB)

eth2 Link encap:Ethernet HWaddr 08:00:27:20:5F:02
inet addr:10.10.10.12 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::a00:27ff:fe20:5f02/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:3836 (3.7 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:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 b) TX bytes:480 (480.0 b)

Re: Cannot ping eth2 after cloning

Posted: 9. Oct 2013, 15:24
by mpack
Look for "NAT limitations" in the user manual. Also I assume you're aware that 10.x addresses are by definition not routeable, and that NAT VMs will not receive unsolicited messages unless you set up port forwarding rules.

Re: Cannot ping eth2 after cloning

Posted: 12. Oct 2013, 10:55
by noteirak
The netmask for eth2 is wrong - you're using 255.0.0.0. but then you already have another interface in 10.x.x.x, so you're going to have conflict. Set netmask of 255.255.255.0 on your eth2.