IpAlias XenServer OVH

Posted on July 23, 2013 at 11:08 am

When you buy new IP FailOvers (RIPE IPs divided in FailOvers) from OVH, you may need to add these IP addresses in the XenServer network as virtual interfaces (eth0:1, eth0:2, eth0:3, etc), to be able to ping them, as described in this tutorial:

http://help.ovh.co.uk/IpAlias

Login with SSH to your XenServer and then type:

cd /etc/sysconfig/network-scripts
cp ifcfg-xenbr1 ifcfg-xenbr1:1
vi ifcfg-xenbr1:1

Remove all the text contained in the file ifcfg-xenbr1:1 and add:

DEVICE="xenbr1:1"
ONBOOT="yes"
BOOTPROTO="static"
IPADDR="IP.FAIL.OVER.ADDR"
NETMASK="255.255.255.255"
BROADCAST="IP.FAIL.OVER.ADDR"

Enable xenbr1:1:

ifup ifcfg-xenbr1:1

You should be able to ping the IP FailOver from the XenServer now:

ping IP.FAIL.OVER.ADDR
PING IP.FAIL.OVER.ADDR (IP.FAIL.OVER.ADDR) 56(84) bytes of data.
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=1 ttl=64 time=0.021 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=2 ttl=64 time=0.020 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=3 ttl=64 time=0.018 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=4 ttl=64 time=0.073 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=5 ttl=64 time=0.051 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=6 ttl=64 time=0.080 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=7 ttl=64 time=0.031 ms
64 bytes from IP.FAIL.OVER.ADDR: icmp_seq=8 ttl=64 time=0.028 ms

Updated on November 19, 2016 at 12:07 pm

Receive updates via email

Other Posts

Updated Posts