The sdn configuration shouldn't overrwrite the ip address. the config is generated in /etc/network/interfaces.d/sdn , and merged (not overwritten) with interfaces defined in /etc/network/interfaces .
But, as with sdn , the vmbr0.101 is plugged to a vnet, you can't defined ip on vmbr0.101...
technically, this is the same. I don't see why vmbr0.101 syntax don't work for you.
The sdn use vmbr0.101 syntax internally, that's why it's conflicting with your vlan101.
a vnet is a bridge.
as a vnet in a simple zone is internal only (not attached to a physical interface), you can reuse the same subnet present on another bridge.
But don't use same gateway/bridge ip than your other nat bridge, or it'll break the routing.
You are luke to not have problem with this intel chipset before.
They are a lof of reports since multiple years about tso/gso driver bug, doing nic hang
see:
https://forum.proxmox.com/threads/e1000-driver-hang.58284/page-8
Can you try:
ethtool -K <interface> tso off gso off
?
Thanks for the report . seem to be related. The ip range creation manual creation is expected currently.(I should add a note in doc). But the ip search in the range was working previously, maybe is it a regression in 4.X. I need to check that.
short response: you need 3 datacenters for the monitors, and you can loose 1dc. (as you always need quorum for monitor)
the osd can be located on 2 datacenters (replicat4 for example, 2 copies on each dc)
what is your ceph version ?
ceph 17 (quincy) have a qos , to priorize client access vs repair
ceph config set global osd_mclock_profile high_client_ops
ceph config set global osd_mclock_profile balanced (default)
ceph config set global osd_mclock_profile high_recovery_ops
Each trunk port has the following defined VLANs:
100,110, 150, 160, 200, 250
do you mean your physical switch port ? Because you need to allow vlan30 too.
just trolling ;) But Hetzner is the only hosting provider with such l2 crap network without filtering in known in the world.
(personnaly, I'll use a routed setup if I was hosting at hetzner)
you can't use vxlan 2 for both vnet && in evpn zone at the same time.
(I thinked we had a verification for this in the gui. Do you have done all the setup through the gui without editing manually the cfg files ?)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.