Recent content by bitposs

Good stuff Hedius, I didn't even think of this! For now, we were in need of another piece of hardware anyways, so built it and are just using it for VM's on one of the networks, hence can use it safely as the exit gateway. The problem with static changes, we're a company of 30 ppl, so...

Cool thanks for your swift reply. Yeah, it looks like they did patch it https://github.com/FRRouting/frr/issues/14419 - assuming should be good now. I've gotta schedule up a maintenance window and I'll give it a test (full production here, so have to make changes gently). I'll report back...

Hey guys, I saved this thread for when I upgraded to Prox8. First cluster, no problem, upgrade went fairly seamless. Second cluster, bit more complicated, as it has 2 diff EVPN zones with separate exit nodes but share a an EVPN controller: Zones (EVPN): * VM100 * VM200 VNETS: * VM100 has 1...

Hey all, On all six nodes in the cluster, which denotes the time I ran the upgrade: -- Journal begins at Mon 2022-12-19 06:05:25 CST, ends at Tue 2023-05-02 17:07:39 CDT. -- Apr 30 15:55:10 node444 systemd[1]: Reloading PVE Status Daemon. Apr 30 15:55:10 node444 pvestatd[625311]: send HUP to...

Upgraded one of our production clusters this weekend as we were adding a new host. Went to live migrate a VM from one to another and got: 2023-05-01 08:52:32 ERROR: migration aborted (duration 00:00:00): target node is too old (manager <= 7.2-13) and doesn't support new cloudinit section...

Thanks for letting me know! I think I'll start install ProxMox 7 on my new clusters going forward and also look at upgrading some of my existing. Along that note, I played around with using VRRP with FRR but ran into some troubles with my maclan devices, which I created on top of my linux...

OK perfect! For what its worth, here are my package versions (haven't yet upgraded to 7.X as I was having issues with my Intel 10Gig NICs and still have to sort that): proxmox-ve: 6.4-1 (running kernel: 5.4.162-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4...

Sure: root@myhostname-24:~# cat /etc/frr/frr.conf log syslog informational ip forwarding ipv6 forwarding frr defaults datacenter service integrated-vtysh-config hostname myhostname-24 ! ! vrf vrf_evpn400 vni 10001 exit-vrf ! router bgp 65001 bgp router-id 192.168.1.24 no bgp default...

Thanks for your reply Thomas! I was thinking the same thing, as I did some research, and noticed PVE/Network/SDN/Controllers/Plugin.pm was like that previously. I went ahead and modified it - and was able to create a BGP controller successfully: Changed PVE/Network/SDN/Controllers/Plugin.pm...

Love the SDN plugin, we're using it with great success! Fantastic work! Was previously using this method, but the plugin makes things even easier. I did run across one concern, we cannot add a BGP controller with nodes that have a dash (-) in their hostname (i.e. myhostname-24): I know...

Anddddd I knew I was overlooking something simple o_O Apparently I commented out that interface to do some testing a while ago and forgot to remove ugh. Thanks for your reply, all good here!

Package versions (on all nodes): proxmox-ve: 6.4-1 (running kernel: 5.4.128-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-5 pve-kernel-helper: 6.4-5 pve-kernel-5.4.128-1-pve: 5.4.128-2 pve-kernel-5.4.124-1-pve: 5.4.124-2 pve-kernel-5.4.106-1-pve...

root@failed-node:/etc/pve# journalctl -b -u corosync -- Logs begin at Sat 2021-10-16 13:46:09 CDT, end at Sat 2021-10-16 15:29:44 CDT. -- Oct 16 13:46:13 failed-node systemd[1]: Starting Corosync Cluster Engine... Oct 16 13:46:13 failed-node corosync[7582]: [MAIN ] Corosync Cluster Engine...

Hello all, Before I begin I want to thank you all for your great posts/replies here. We've been using Proxmox for over 1 year and have never made a post as we've always found the answers here by searching (and that could be the case here, but I'm currently on vacation and wife gonna kill me if...