Proxmox and Advance Server OVH

[kennysamuerto]

Hi,

I'm here to see if you can help me out. I'm using an OVH Advance-4 server, which doesn't have the capability to generate virtual MACs. I found this guide to activate the VMs:

https://support.us.ovhcloud.com/hc/...work-on-Proxmox-VE-with-ADVANCE-Gen-3-Servers

And I've followed it on my Proxmox server. Let me share the details. First, in a VRACK, I've added both the server (with IP 79.137.xxx.48) and the block of 4 IPs that I have.

This is my IP block (4 IPs):

Network IP: 46.105.xxx.44
Gateway IP: 46.105.xxx.46 (not usable)
Broadcast IP: 46.105.xxx.47

So, the first thing I did was edit the file

/etc/iproute2/rt_tables

And I added:

1 vrack

At the bottom. Then, I went to my

/etc/network/interfaces

file and edited it like this:

auto lo
iface lo inet loopback


iface enp10s0f0np0 inet manual


auto vmbr0
iface vmbr0 inet static
        address 79.137.xxx.48/32
        gateway 100.xx.0.1
        bridge-ports enp10s0f0np0
        bridge-stp off
#       bridge-fd 0
        hwaddress 04:7C:XX:XX:02:2C


iface vmbr0 inet6 static
        address 2001:41d0:XXX:3000::/56
        gateway feXX::1


auto vmbr1
iface vmbr1 inet static
    address 46.105.XXX.45/30
    gateway 46.105.XXX.46
    broadcast 46.105.XXX.47
    bridge-ports enp10s0f1np1
    bridge-stp off
    bridge-fd 0
post-up ip route add 46.105.XXX.44/30 dev vmbr1 table vrack
post-up ip route add default via 46.105.XXX.46 dev vmbr1 table vrack
post-up ip rule add from 46.105.XXX.44/30 table rack
post-up rule add to 46.105.XXX.44/30 table rack

I create the virtual machine, like Debian for example, and assign the new network I created (vmbr1) to it, then I start the machine configuring the network like this:

IP: 46.105.xxx.45
Gateway: 46.105.xxx.46
Mask: 255.255.255.252

I start the machine, it pings, and has internet access.

But mysteriously, the node loses internet access and becomes unreachable.

I don't understand what's happening, but the IP of the virtual machine also pings even when the virtual machine is not running. If I start it, it works fine and the VM runs without problems, but whether I start it or not, I lose connectivity to the main machine (the node). What could be going on?

 

[_gabriel]

not experience here, but afaik, set public ip and the route in the vm not on the vmbr1.

auto vmbr1
iface vmbr1 inet manual
        bridge-ports enp10s0f1np1 
        bridge-stp off
        bridge-fd 0

 

[rruano]

Did you manage to solve it? The same thing happened to me

 

[SkynetJS]

Did you manage to solve it? The same thing happened to me

Virtual MACs are not currently supported by their 3rd generation Advance servers. Projected to be available mid-December.

Per their FAQ:

The latest Advance next-generation servers, equipped with AMD EPYC 4000 and 8000 CPUs, do not currently support the VMAC feature. This temporary incompatibility is only specific to this latest generation of servers, launched in July 2024. The VMAC feature is essential for setting up virtual machines in bridge mode on your server. This is especially useful in virtualized environments, where multiple virtual machines share a single physical network interface. By assigning a unique virtual MAC address to each virtual machine, network traffic can be successfully routed to the correct virtual machine.

It is important to note that older-generation servers are compatible with VMAC. We are aware of how essential this feature is for many users, and we are actively working on integrating it into new servers. Advance servers are expected to be VMAC-compatible by the end of 2024. This update will give you greater flexibility and optimized management of your virtual network.

For more information on managing IPs and virtual MACs with OVHcloud, please refer to Network configuration in Proxmox VE. This guide provides instructions for configuring your OVHcloud servers with Proxmox VE to optimize network performance in virtualized environments. This is done using techniques like routing additional IPs via the vRack.

Thank you for your patience and understanding. Stay tuned for future updates on the availability of the VMAC feature on our Advance servers.