|
Search |
If you've receive an email stating that your Failover IP is not configured correctly, then you should follow this guide. You can configure your Virtual Machine in bridge mode. Some changes must be made on the VM to make a working network configuration. In blue are the file names to edit (with vi, nano, pico ...) and the content. In these configurations, the fields should be replaced, they will be in red. A dedicated server with VMware ESXi or Citrix Xen Server or Hyper-V Have assigned a mac to a virtual failover IP Know about SSH To configure Virtual Machines, you need to know the gateway of your host machine (nsxxx.ovh.net; ksxxx.ovh.net ...). To do this, you must replace the last group of numbers assigned to your server with .254. You can find the IP of your server in the OVH Manager. ex : IP of your server : 123.456.789.012 IP gateway is your server's IP ending in .254 Gateway is: 123.456.789.254 WARNING: Under no circumstances use the primary IP of your server as the gateway! You must under no circumstances use: route add default gw dev eth0 or you could cut your IP from the virtual server.
/etc/network/interfaces auto lo eth0 iface lo inet loopback iface eth0 inet static address IP.Fail.over netmask 255.255.255.255 broadcast IP.Fail.over post-up route add Your.Server.IP.254 dev eth0 post-up route add default gw Your.Server.IP.254 post-down route del Your.Server.IP.254 dev eth0 post-down route del default gw Your.Server.IP.254 /etc/resolv.conf nameserver 213.186.33.99 WARNING: Under no circumstances use the primary IP of your server as the gateway! You must under no circumstances use: route add default gw dev eth0 or you could cut your IP from the virtual server. /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes USERCTL=no IPV6INIT=no PEERDNS=yes TYPE=Ethernet NETMASK=255.255.255.255 IPADDR=IP.Fail.over GATEWAY=Your.Server.IP.254 ARP=yes HWADDR=VI:RTU:AL:MA:C: /etc/sysconfig/network-scripts/route-eth0 Your.Server.IP.254 dev eth0 default via Your.Server.IP.254 dev eth0 /etc/resolv.conf nameserver 213.186.33.99 WARNING: Under no circumstances use the primary IP of your server as the gateway! You must under no circumstances use: route add default gw dev eth0 or you could cut your IP from the virtual server. Here is the network configuration : IP: Fail.over.IP Netmask : 255.255.255.255 You will then add the following routes : route add Your.Server.IP.254 dev eth0 route add default gw Your.Server.IP.254 You will then need to configure the dns of your machine so that it can make resolution domain. The IP information is 213.186.33.99 WARNING: Under no circumstances use the primary IP of your server as the gateway! You must under no circumstances use: route add default gw dev eth0 or you could cut your IP from the virtual server. /etc/rc.conf ifconfig_em0="inetIP.Fail.over netmask 255.255.255.255 broadcast IP.Fail.over" static_routes="net1 net2" route_net1="-net Your.Server.IP.254/32 IP.Fail.over" route_net2="default Your.Server.IP.254" /etc/resolv.conf nameserver 213.186.33.99 WARNING: Under no circumstances use the primary IP of your server as the gateway! You must under no circumstances use: route add default gw dev eth0 or you could cut your IP from the virtual server. At first, you must connect to the panel "Network Connections" (Start> Control Panel> Network Connections> Local Area Connections) Then, select Properties : ![]() Then, select Internet Protocol (TCP/IP) : ![]() Finally, fill in your failover IP in the "IP Address" field, the subnet mask 255.255.0.0, the gateway to your physical machine as default gateway and the IP 213.186.33.99 as the preferred DNS server. ![]() For the second step, via the Start menu, click Run, then type regedit. Once in the application, you should find your failover IP (Edit Search). Once the IP found, double-click the parameter SubnetMask? "and change 255.255.0.0 to 255.255.255.255, then you validate. Close the registry editor Finally, to validate the changes, you must restart the network interface (Start> Control Panel> Network Connections> Connection LAN> right click, then Disable) Wait a few seconds and re-enable the network connection |