Recent content by spirit

  1. spirit

    evpn? network segmentation?

    I think it could be done with a dedicated interface in each zone/vrf, (not sure if a vlan tagged interface could work to avoid the need to have dedicated interfaces). That's why I'm doing it with my physical router/switch currently, with a lot of zones,it's more simplier
  2. spirit

    Does EVPN Zone support 'pve' IPAM to trigger PowerDNS updates?

    currently ipam/dns are working with dhcp only, and dhcp is working with simple zone. it's working in progress to add feature on other zones.
  3. spirit

    Proxmox SDN Traffic breakout Interface and routing

    if you have talking about the vxlan tunnels themself or the bgp peers, they are simply using the route to reach to remote peers ips. so you can make simple routes on your host if needed. or do you want PBR specifically for the vxlan udp port on a different nic ????
  4. spirit

    Proxmox SDN Traffic breakout Interface and routing

    do you have an example of what you need to do with manual routes to be sure to understand what you need? on the underlay, evpn/vxlan are using peers adress list to establish vxlan tunnel, and the vxlan tunnels are working in default vrf only. in the overlay, in evpn, if you define an...
  5. spirit

    Proxmox VE 9.1.1 dnsmasq issue

    currently the gateway ip from gui is only apply to simple zone && evpn zone as the ip is pushed on the vnet on all hosts. (or you could have ip conflict on layer2 zones like vlan,vxlan,....) you can add an ip with add in /etc/network/interfaces of the node iface vnet100 address...
  6. spirit

    evpn? network segmentation?

    each zone is a different vrf in evpn with their own routing table. (only using exit-node is doing a vrf route leak between the zone && default zone. but If you use multiple zones, I'll command to use physical routers as exit evpn nodes) so yes, you have overlaping ip range, you have firewall...
  7. spirit

    [SOLVED] VM slow IO read from historian DB

    your fio show 0 problem with random io read
  8. spirit

    [SOLVED] VM slow IO read from historian DB

    so, it's a windows vm ? (0.1.271 driver , try to keep this one, because the more recent have known bug). fio seem to push hardware to max (500MB/s seem to be the pci bus limit of the raid controller) try to avoid writeback on vm side, as you already have writeback on your controller. do you...
  9. spirit

    Upgrade from 6.3-9 to 7.x

    my oldest cluster have been updated from pve4->5->6>7>8>9 without any reinstall ;)
  10. spirit

    Ceph PGs go inactive when adding large OSDs on new host

    I think you could look to increase mon_max_pg_per_osd which is 250 by default. as if you have only 2 osd, and a lot more osd (4 ..6 ) on the other side, maybe they can handle enough pg. (could explain why splitting the disk in mutiple osd is helping)
  11. spirit

    Ceph PGs go inactive when adding large OSDs on new host

    ah ok ! Do you use the new fast EC from ceph20 ? what is your K & M values ?
  12. spirit

    40 node prod cluster restarts when joining a new node or removing.

    from last corosync release https://github.com/corosync/corosync/releases "A new option (totem.ip_dscp) is available to configure DSCP for traffic prioritization. Thanks to David Hanisch for this great improvement." could be interesting for stretched cluster across datacenter where links can be...
  13. spirit

    Ceph PGs go inactive when adding large OSDs on new host

    what is your pool size replicat number ????? (looks like replicat x7 ????)
  14. spirit

    MAC prefix for each vnet

    setting mac on vnet could be only usefull if you have an ip on the vnet. (so mainly when vnet is used as gateway for the vms). It's only possible with evpn, as the ip/mac is the same on each vnet (anycast ip). Don't make sense to add feature for other zone type. if really needed, you can...
  15. spirit

    apt or pve for automatic (unatended) upgrades?

    proxmox used apt update / apt dist-upgrade behind pveupdate/pveupgrade, so no problem. Just be carefull to use "apt dist-upgrade" and not "apt upgrade" !