OVH Community, your new community space.

Virtual Server - Secondary IP not working!


heise
20-10-2014, 20:39
He was using IP bridging with 2 network cards, which theoretically should work, once the metric is set right. For IP alias you would use only one network card, hence we only need one MAC.

BaoZaiz
20-10-2014, 19:37
hi,

I am not sure if RIPE IP works the same as OVH Failover IP, means it is bond to MAC address. If this is the case then I believe IP Aliasing is not working because you can't have 2 MAC address in single ethernet interface.

Sorry if I'm wrong.

Thank you.

marc5000
13-10-2014, 20:11
Hi guys,

Thanks for all the replies. I have chosen to go down the route of an IP alias - you're right, having two network cards is going to be a pain and is probably not worth the effort.

marks, I tested each IP by disabling the the other retrospectively and I was able to ping the box when the other wasn't on. Clearly there is a special routing configuration I need to follow for this to work and I'm probably taking the long way round!

I'll get back to you regarding the ip alias! Thanks =)

Marc

heise
13-10-2014, 16:29
I'm no expert in this, but are you setting the router metrics http://en.wikipedia.org/wiki/Metrics_%28networking%29 ? After all, how shall the server know which network card to use to connect to the internet??

marks
13-10-2014, 11:57
that's not a very common configuration, but I can't see why it shouldn't work, specially if the network configuration on the server side for the network cards is correct.

One test you can do is to try the IPs/vMAC pairs individually on single network card VMs first. Try if in normal circumstances (1 VM and 1 network card) both IPs should work. IF one of them doesn't work, troubleshoot it individually.

After that, put them together under the same VM.

Do let us know how it went

heise
13-10-2014, 03:04
Two network cards in one VM? Why not one network card and IP Alias?

marc5000
13-10-2014, 00:40
Hi, I hope someone can assist me or lead me to a post where this has been asked?.This is bugging me now!

I recently bought a RIPE block of IP addresses, and have setup a virtual machine...

The first IP address on eth0 (92.xxx.xxx.136) of my virtual machine (correlating to Network 0 on XenServer) is working fine.
My second IP address on eth1 (92.xxx.xxx.137) of my virtual machine (correlating to Network 1 on XenServer) is not working at all?

Both virtual network cards are going out the correct gateway and my configurations are the same, with the obvious changes::

eth0:

DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
NETMASK=255.255.255.255
IPADDR=92.xxx.xxx.136
GATEWAY=46.xxx.xxx.254
ARP=yes
HWADDR=02:xx:xx:xx:xx:e5

eth1:

DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=yes
TYPE=Ethernet
NETMASK=255.255.255.255
IPADDR=92.xxx.xxx.137
GATEWAY=46.xxx.xxx.254
ARP=yes
HWADDR=02:xx:xx:xx:xx:ec

route0:

46.xxx.xxx.254 dev eth0
default via 46.xxx.xxx.254 dev eth0

route1:

46.xxx.xxx.254 dev eth1
default via 46.xxx.xxx.254 dev eth1

Can anyone see any reason why this shouldn't be working? I'm running XenServer 6.2, and I've created a second network card on the virtual server (which is Centos 6.5)

Thanks!