Failover IP in Windows 2003/08
I swapped the IP's around on my Proxmox VM no probs and it worked no issues (other than having to reconnect via remote desktop - vnc interface didn't flinch) when I was still with 1&1 before I could get out of the contract & move here
Guys , did anyone actually try swapping the IP's around like this - did the srever still respond with 2008 R2? just wanted to check before trying it!
Originally Posted by
IainK
@Tz-OVH: I tried this out on a Windows server and Windows does seem to report the first IP address as 94.23.159.153 instead of 91.121.176.170.
However may I ask why you are trying to do this? If you are doing it to have google.com and other sites redirect you to a UK or other country page (not French) then you're out of luck as it's still going through the same gateway and for some reason the IP address 91.121.176.170 is still reported as the address visiting webpages. I haven't found a way to change this, yet!
Well damn, that was one of the minor reasons, but the main was having a UK IP as my primary rather than an IP that is seen by geoip as France based.
@Tz-OVH: I tried this out on a Windows server and Windows does seem to report the first IP address as 94.23.159.153 instead of 91.121.176.170.
However may I ask why you are trying to do this? If you are doing it to have google.com and other sites redirect you to a UK or other country page (not French) then you're out of luck as it's still going through the same gateway and for some reason the IP address 91.121.176.170 is still reported as the address visiting webpages. I haven't found a way to change this, yet!
Aha, thanks IanK...I was going to follow the guide from the OVH help page Razakel posted, but I'll try what you suggested, seems easier.
@Tz-OVH:
Say your Primary IP address is 91.121.176.170 and your failover IP is 94.23.159.153. You would set up your ethernet adaptor to use the following settings:
IP Address: 94.23.159.153
Netmask: 255.255.255.0
Default Gateway: 91.121.176.254
Additional Addresses
IP Address: 91.121.176.170
Netmask: 255.255.255.0
Hope that helps.
Originally Posted by
Tz-OVH
OVH say its ok to do it. But they say my Primary/Fixed IP should still respond to a ping...so their switches don't think the machine is offline. How do I do this.
Windows 2003 Server section on
http://help.ovh.com/IpAlias using your primary IP.
OVH say its ok to do it. But they say my Primary/Fixed IP should still respond to a ping...so their switches don't think the machine is offline. How do I do this.
Originally Posted by
Tz-OVH
I'm running Windows, so I don't think those would apply to me?
No. Just make sure everything's set correctly before OKing it, else you won't be able to connect. :P
Originally Posted by
IainK
It works fine
Code:
[root@x1 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1C:C0:65:0F:BC
inet addr:94.23.159.153 Bcast:94.23.159.255 Mask:255.255.255.0
inet6 addr: fe80::21c:c0ff:fe65:fbc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2172 errors:0 dropped:0 overruns:0 frame:0
TX packets:924 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:212889 (207.8 KiB) TX bytes:126309 (123.3 KiB)
Interrupt:225 Base address:0x2000
eth0:0 Link encap:Ethernet HWaddr 00:1C:C0:65:0F:BC
inet addr:91.121.176.170 Bcast:91.121.176.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:225 Base address:0x2000
Just make sure that your default gateway setting is always set correctly. Also I would recommend rebooting or using 'service network restart' rather than ifdown eth0 && ifdown eth0:0 && ifup eth0 && ifup eth0:0.
I'm running Windows, so I don't think those would apply to me?
It works fine
Code:
[root@x1 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1C:C0:65:0F:BC
inet addr:94.23.159.153 Bcast:94.23.159.255 Mask:255.255.255.0
inet6 addr: fe80::21c:c0ff:fe65:fbc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2172 errors:0 dropped:0 overruns:0 frame:0
TX packets:924 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:212889 (207.8 KiB) TX bytes:126309 (123.3 KiB)
Interrupt:225 Base address:0x2000
eth0:0 Link encap:Ethernet HWaddr 00:1C:C0:65:0F:BC
inet addr:91.121.176.170 Bcast:91.121.176.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:225 Base address:0x2000
Just make sure that your default gateway setting is always set correctly. Also I would recommend rebooting or using 'service network restart' rather than ifdown eth0 && ifdown eth0:0 && ifup eth0 && ifup eth0:0.
I've learned its better to check, especially on OVH
Why would it? Looking at my Linux box, the virtual adapters have the same MAC address:
eth0 Link encap:Ethernet HWaddr 00:11:11:6C:43:4F
inet addr:x.x.x.55 Bcast:x.x.x.255 Mask:255.255.255.0
inet6 addr: x::x:x:x:434f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:85652258 errors:0 dropped:0 overruns:0 frame:0
TX packets:90583022 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2929065875 (2.7 GiB) TX bytes:261024222 (248.9 MiB)
eth0:1 Link encap:Ethernet HWaddr 00:11:11:6C:43:4F
inet addr:y.y.y.128 Bcast:y.y.y.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
I'm sure it'd work fine if I swapped the IPs on eth0 and eth0:1. Presumably this'll work in Windows too.
I've been meaning to try this, was wondering if someone here has already.
Since OVH don't lock the network adapter settings, we can change the IP to the Failover IP assigned to the particular server?
My concern in doing this is that the machine gets thrown off the network due to some OVH router rules and leaving it inaccessible.