We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Bad configuration regarding your server


eximushosting
02-02-2015, 22:47
This will kill the dedicated server but the VMs will stay online...

Code:
ip link set dev br0 arp off

eximushosting
02-02-2015, 21:42
OK.. I had more emails from OVH/SYS..

So I am trying a different method at the moment, basically the same as above but with arp=no in the file for :0

Code:
cat /etc/sysconfig/network-scripts/ifcfg-eth0:0
DEVICE=eth0:0
ONPARENT=yes
IPADDR=151.80.123.242
NETMASK=255.255.255.255
GATEWAY=94.23.42.254
ARP=no
HWADDR=02:00:00:4A:6E:FE
BROADCAST=151.80.123.242

cat /etc/sysconfig/network-scripts/route-eth0:0
94.23.42.254 dev eth0
default via 94.23.42.254 dev eth0
and then running the below on the server
Code:
ip link set dev eth0 arp off
and the same on (almost) on the dedicated server
Code:
ip link set dev br0 arp off


Lets see if this satisfies OVH

eximushosting
01-02-2015, 06:36
Hello.

Last night I removed the extra IPs restarted the networking and added them to /etc/ips. So far I have not had any emails from OVH so fingers x'ed.

eximushosting
31-01-2015, 11:02
Hello,

I can not find anything online saying that using a bridge (br0) with KVM wont work with multiple IPs on a single Virtual Server.

Can someone point me in the right direction or an alternative method to achieve multiple IPs on a Virtual Machine with a SYS dedicated server.

Thanks.

eximushosting
29-01-2015, 18:04
So.. How can I add more than IP address per VM?

If the server has cPanel will adding them via cPanel work?

heise
29-01-2015, 14:20
If you use bridge (br0), you cannot use eth0:0 (IP alias). Google OVH+IP+alias

eximushosting
29-01-2015, 12:21
OK, I have had emails about all the IP addresses now.. so not sure what to do.. Perhaps its the bridge setup on the dedicated server?

Code:
DEVICE="eth0"
NM_CONTROLLED="no"
ONBOOT=yes
TYPE="Ethernet"
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
BRIDGE=br0

-------------------------------------
DEVICE="br0"
NM_CONTROLLED="no"
ONBOOT=yes
TYPE=Bridge
BOOTPROTO=none
IPADDR=94.23.42.220
NETMASK=255.255.255.0
GATEWAY=94.23.42.254
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
NAME="System br0"

eximushosting
29-01-2015, 11:16
Hello,

I had an email from SYS stating

We have detected that your server ns3511040.ip-94-23-42.eu unnecessarily sending
a large number of requests over the network via its IP failover 5.135.254.123
This is due to a misconfiguration.
I had this for all the fail over IPs I ordered (8 in total), today I have had another email for 2 of them stating they are still sending a large number of requests. The configuration all of them of them are the same so I am not sure why 2 are still 'sending;

Here is the config on eth0 (this is a virtual machine)
{CODE]
DEVICE=eth0
HWADDR=02:00:00:4A:6E:FE
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=151.80.123.243
GATEWAY=94.23.42.254
NETMASK=255.255.255.255
ARP=yes
PEERDNS=yes
[/CODE]

and the IP Alias files
Code:
DEVICE=eth0:0
IPADDR=151.80.123.242
NETMASK=255.255.255.255
BROADCAST=151.80.123.242
---------------------------------------------------
DEVICE=eth0:1
IPADDR=151.80.123.241
NETMASK=255.255.255.255
BROADCAST=151.80.123.241
---------------------------------------------------
DEVICE=eth0:2
IPADDR=5.135.254.120
NETMASK=255.255.255.255
BROADCAST=5.135.254.120
---------------------------------------------------
DEVICE=eth0:3
IPADDR=5.135.254.121
NETMASK=255.255.255.255
BROADCAST=5.135.254.121
---------------------------------------------------
DEVICE=eth0:4
IPADDR=5.135.254.122
NETMASK=255.255.255.255
BROADCAST=5.135.254.122
---------------------------------------------------
DEVICE=eth0:5
IPADDR=5.135.254.123
NETMASK=255.255.255.255
BROADCAST=5.135.254.123
The route-eth0 files is per the instructions OVH provide
Code:
94.23.42.254 dev eth0
default via 94.23.42.254 dev eth0