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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Bad configuration regarding your server (SoYouStart)
Don't know why this message comes to me while I configure my VM as the Manual of OVH sad exactly here
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 IP.YOUR.DEDI dev eth0
post-up route add default gw IP.YOUR.DEDI
post-down route del IP.YOUR.DEDI dev eth0
post-down route del default gw IP.YOUR.DEDI
I have two servers one of them didn't got any messages when creating a new vm , the second give me the message again and again and every time I create a new VM with Proxmox. Indeed I use the above configuration but the message still come every time!
is there anyone else have the same problem here ?
Comments
If my memory is okay.
Also you create your vMac's ?
Don't have this problem, then again I'm not using proxmox. Could it be your failover IP configuration? Support's quite helpful, did you check with them?
@davidgestiondbi
http://help.ovh.co.uk/Proxmox
yeah but this with ip alias o bridging, in this page it's the configuration of proxmox also I already created the MAC address
@century1stop
I contact them but as you know soyoustart is one of the slowest support due to the huge number od servers they manage !!
yea true, takes 2 - 3 days at times but they'll be able to guide you. Sure the IP block's configured correctly? Gateway has to be server ip.254 for every block. Oh, you're using vmac. nvrm.
This is OK configuration. So, if your IP is for example 86.193.47.156, your IP for your post-up/down lines is 86.193.47.254
I always use this tutorial on all OVH brand around their datacenters, and never receive a warning of misconfiguration.
https://translate.google.com/translate?sl=fr&tl=en&js=y&prev=_t&hl=fr&ie=UTF-8&u=http://guides.ovh.com/BridgeClient&edit-text=&act=url
ok I reconfigure the route for IP.254
but this is not like the configuration here !!
http://help.ovh.co.uk/Proxmox
I'm really confused
I'm using proxmox with SYS and I don't need to add that post-up/down crap
Just in the VM I add the proper gateway ending in 254 for the failovers just like the nodes IP is configured.
Instructions for IP block configuration - applies if you configure an IP block for your server but you'll probably need to use the documentation you mentioned when NAT is used
1 - Configuration within a dedicated server
In this case, all IPs of your block 167.xxx.xxx.xxx/29 are usable.
Please use of one of the following guides for the configuration:
If used in virtual machines: http://docs.ovh.ca/en/guides-network-bridging.html.
If used on the same interface network of your server: http://docs.ovh.ca/en/guides-network-ipaliasing.html.
In general, all IPs must have the following netmask:
255.255.255.255, and the gateway is composed of the main IP of the server ending in .254
2 - Configuration within a virtual rack (vRack) or on a Dedicated Cloud offer
If you use this block in a virtual rack or a Dedicated Cloud, the following addresses must be freed up:
Network IP : 167.xxx.xxx.xxx
IP for router n°1 : 167.xxx.xxx.xxx
IP for router n°1 : 167.xxx.xxx.xxx
Gateway IP : 167.xxx.xxx.xxx (not usable)
Broadcast IP: : 167.xxx.xxx.xxx
Then use the sub-netmask 255.255.255.248.
For your information, your block has the following characteristics:
167.xxx.xxx.xxx/29
Network IP :167.xxx.xxx.xxx
Broadcast IP :167.xxx.xxx.xxx
Gateway IP :167.xxx.xxx.xxx
Netmask :255.255.255.248
thank you for this great explain , I usually use /32 but this is great information
@alsemany yes it is server.ip.254 this guide is old i found that on some wired french document i found on .com...
@century1stop i give you a thanks never know ovh.ca got so good documentation their EU based one is awful
Welcome, guess you'd be able to get things going this time round?