IP Failover in OVH not working

Issues related to configuring your network
Post Reply
Reverse
Posts: 1
Joined: 2020/01/01 19:53:39

IP Failover in OVH not working

Post by Reverse » 2020/01/01 21:19:10

Hello :)
I have problem with my server. I buyed dedicated server in OVH and IP Failover 149.202.123.176/29.

On basic this tutorial https://docs.ovh.com/gb/en/dedicated/ne ... paliasing/ i added my ip failover to network configuration.
This i my ifcfg-eth0:0 file:
DEVICE=eth0:0
BOOTPROTO=static
IPADDR=149.202.123.176
NETMASK=255.255.255.255
ONBOOT=yes
GATEWAY=149.202.123.254
BROADCAST=149.202.123.176
In e-mail from ovh i got this message:
In general, all IP addresses must have a network mask of 255.255.255.255 and a gateway composed of a master IP address with a server ending in .254
that's why I set netmask to 255.255.255.255 and the gateway to the server IP with the ending changed to 254

From this block i assign IP 149.202.123.176 to my domain tr-bahis.com but domain not working. When i ping domain i got response:
[pawel@54 network-scripts]# ping tr-bahis.com
PING tr-bahis.com (149.202.123.177) 56(84) bytes of data.
64 bytes from ip177.ip-149-202-123.eu (149.202.123.177): icmp_seq=1 ttl=64 time=0.045 ms
64 bytes from ip177.ip-149-202-123.eu (149.202.123.177): icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from ip177.ip-149-202-123.eu (149.202.123.177): icmp_seq=3 ttl=64 time=0.030 ms
64 bytes from ip177.ip-149-202-123.eu (149.202.123.177): icmp_seq=4 ttl=64 time=0.057 ms
64 bytes from ip177.ip-149-202-123.eu (149.202.123.177): icmp_seq=5 ttl=64 time=0.058 ms
64 bytes from ip177.ip-149-202-123.eu (149.202.123.177): icmp_seq=6 ttl=64 time=0.060 ms
ifconfig output, my interface is visible
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 54.38.93.62 netmask 255.255.255.0 broadcast 54.38.93.255
inet6 fe80::a6bf:1ff:fe1f:92c8 prefixlen 64 scopeid 0x20<link>
ether a4:bf:01:1f:92:c8 txqueuelen 1000 (Ethernet)
RX packets 37578 bytes 3145531 (2.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14161 bytes 2375886 (2.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xa2b00000-a2bfffff

eth0:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 149.202.123.176 netmask 255.255.255.255 broadcast 149.202.123.176
ether a4:bf:01:1f:92:c8 txqueuelen 1000 (Ethernet)
device memory 0xa2b00000-a2bfffff
ip -br address
[pawel@54 network-scripts]# ip -br address
lo UNKNOWN 127.0.0.1/8 ::1/128
dummy0 DOWN
ifb0 DOWN
ifb1 DOWN
eth0 UP 54.38.93.62/24 149.202.123.176/32 149.202.123.177/32 fe80::a6bf:1ff:fe1f:92c8/64
eth1 DOWN
teql0 DOWN
tunl0@NONE DOWN
gre0@NONE DOWN
gretap0@NONE DOWN
erspan0@NONE DOWN
sit0@NONE DOWN
ip6tnl0@NONE DOWN
ip a output
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a4:bf:01:1f:92:c8 brd ff:ff:ff:ff:ff:ff
inet 54.38.93.62/24 brd 54.38.93.255 scope global eth0
valid_lft forever preferred_lft forever
inet 149.202.123.176/32 brd 149.202.123.176 scope global eth0:0
valid_lft forever preferred_lft forever
inet 149.202.123.177/32 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::a6bf:1ff:fe1f:92c8/64 scope link
valid_lft forever preferred_lft forever
I've been sitting on it for a week and I can't handle it :( I even did reinstall systems from debian on CentOS but I still can't solve this problem. I have direct admin installed on the server. Does anyone have any idea what might not work? The domain provider's IP changed 2 weeks ago, so that's not a problem.

Regards Pawel

Post Reply

Return to “CentOS 7 - Networking Support”