Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Failover IPs - OVH VPS Debian10
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Failover IPs - OVH VPS Debian10

citrixcitrix Member
edited June 2020 in Help

hey all,

wondering if someone could provide me a little direction it's been a while since i've used failvoer ips on a VPS probably Debian8 to be fair.

Now with Debian10 I'm seeing conflicting information across the OVH website not sure what guide to follow to be honest, any pointers?

I tried this guide. - https://docs.ovh.com/gb/en/public-cloud/configure_a_failover_ip/

**auto eth0
iface eth0 inet dhcp

auto eth0:0
iface eth0:0 inet static
address MAIN IP 0
netmask 255.255.255.255

auto eth0:1
iface eth0:1 inet static
address FAILOVER_IP1 1
netmask 255.255.255.255**

but i get the following error

Jun 01 22:05:51 vpsXXX systemd[1]: Starting Raise network interfaces...
Jun 01 22:05:51 vpsXXX ifup[704]: Error: either "local" is duplicate, or "0/255.255.255.255" is a garbage.
Jun 01 22:05:51 vpsXXX ifup[704]: ifup: failed to bring up eth0:0
Jun 01 22:05:51 vpsXXX ifup[704]: Error: either "local" is duplicate, or "1/255.255.255.255" is a garbage.
Jun 01 22:05:51 vpsXXX ifup[704]: ifup: failed to bring up eth0:1
Jun 01 22:05:51 vpsXXX systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 01 22:05:51 vpsXXX systemd[1]: networking.service: Failed with result 'exit-code'.
Jun 01 22:05:51 vpsXXX systemd[1]: Failed to start Raise network interfaces.

Many Thanks

Comments

  • Shot2Shot2 Member

    remove the "0" and the "1" at the end of each "address" line.

    Thanked by 1citrix
  • citrixcitrix Member
    edited June 2020

    @Shot2 said:
    remove the "0" and the "1" at the end of each "address" line.

    Think im getting closer... got this error now.
    **
    service networking restart**

    Jun 02 00:01:40 vpsxxx systemd[1]: Starting Raise network interfaces...
    Jun 02 00:01:40 vpsxxx ifup[6296]: RTNETLINK answers: File exists
    Jun 02 00:01:40 vpsxxx ifup[6296]: ifup: failed to bring up eth0:0
    Jun 02 00:01:40 vpsxxx systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
    Jun 02 00:01:40 vpsxxx systemd[1]: networking.service: Failed with result 'exit-code'.
    Jun 02 00:01:40 vpsxxx systemd[1]: Failed to start Raise network interfaces.

  • dfroedfroe Member, Host Rep
    edited June 2020

    If you already bind your main IP via DHCP to eth0, why are you trying to also statically assign it to eth0:0? That's the reason for the "already exists" error you are seeing.

    If you want to configure eth0 via DHCP, there is no need to configure your main IP also as an additional IP on eth0:0.

    If you want to configure it statically without DHCP, remove the DHCP config.

    It's your choice - but chose one way and do not try to combine them. :)

    And I know reading docs isn't cool nowadays, but if you want to understand what you are doing, it is worth reading man interfaces - which by the way is usually less error-prone than OVH KBs. ;)

    Thanked by 1citrix
  • Shot2Shot2 Member

    Good catch, hadn't noticed the dhcp + main_ip repetition

    Anyway, dhcp for main_ip + static for additional_ip may work.

    Thanked by 1citrix
  • citrixcitrix Member

    Hi @Shot2 and @dfroe just wanted to say thank you.

    I've used the below and confirm it's now working.

    auto eth0
    iface eth0 inet dhcp

    auto eth0:0
    iface eth0:0 inet static
    address FAILOVER_IP
    netmask 255.255.255.255

Sign In or Register to comment.