[pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

[Dietmar Maurer]

> On December 13, 2018 at 9:12 AM Alexandre DERUMIER <aderumier at odiso.com> wrote:
> 
> 
> >>I just noticed that can have v(x)lan IDs multiple times,
> >>once for each transport zone? So we need a better 
> >>naming scheme, for example:
> 
> >>vxlan2 in zone1 => z1vxlan2
> >>vxlan2 in zone2 => z2vxlan2
> 
> it's not possible to have 2 vxlan vtep with same vxlan-id.
> 
> auto vxlan2
> iface vxlan2 inet manual
>     vxlan-id 2
> 
> auto vxlan3
> iface vxlan3 inet manual
>     vxlan-id 2
> 
> # ifup vxlan2
> # ifup vxlan3
> warning: vxlan3: vxlan add/set failed: cmd '/bin/ip link add dev vxlan3 type vxlan id 2 dstport 4789' failed: returned 2 (Error: A VXLAN device with the specified VNI already exists.

Is there a technical reason for that, or is that just a bug?