Search results

Hi Widely, It won't show up as "used storage" in the other location as this data is not used on that location. You will see however that the total storage of the other location is lower than before. In this case you'll see the total size of "local" in- and decreasing in size this past year due...

I have a few clusters still on pve7 with a pbs on version 3. So far no issues, you just can't use the newer features like namespaces.

I can see your patch in the mailing list, would it help if I created a feature request in git?

I'm sorry to hear that, I've been running this setup with okay results. root@pbs1:~# dd if=/dev/zero of=testfile.bin bs=4G count=1 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 6.73434 s, 319 MB/s This is done using an Intel s3610 1,92,tb sata ssd in a 2.5" enclosure...

Hi Jarvar, It is possible to assign a vlan in Opnsense or create an interface with vlan managed in proxmox. The problem with this however is that you can only have a vlan set-up in one of these two ways at the time. This is a limitation of the inner workings of linux bridges. The solution for...

1. Get the ID of your disk: michael@next-michael:~$ ls /dev/disk/by-id/ dm-name-cryptdata nvme-eui.002538bb21047659-part2 dm-name-cryptswap nvme-eui.002538bb21047659-part3...

As a matter of fact I do, had to do this solution once more a while back. These are the steps: 1. Backup the VG data: vgcfgbackup pve -f lvbackup 2. Edit the ID to match what it's expecting: vim lvbackup 3. restore the backup you made: vgcfgrestore pve -f lvbackup --force You're not done...

I had the same results as you for my testsetup. The way I fixed this is by assigning the disk to the vm instead of usb, this way the IO doesn't run though usb-passtrough. It's not not possible to assign it using the gui but by editing conf file or qm command. In my case it was this line: scsi1...

Yes that works perfectly! Stupid mistake from my side. All servers now use their loopback address.

Thank you for this update! It's almost working as intended but assigns the wrong ip-address. Setting controllers.cfg loopback to lo isis: pve4-test isis-domain 1 isis-ifaces eno8,eno7 isis-net 10.0000.0000.0007.00 loopback: lo node pve4-test And having...

This one works as intended! Was able to have 2 isis sessions and have them failover: pve4-test# show isis interface Area 1: Interface CircId State Type Level eno7 0x0 Up lan L1L2 eno8 0x7 Up lan L1L2 We ran into a small...

The route-map part is back, the other changes broke isis. Interfaces are not added in frr config anymore. Same goes for isis settings. controller.cfg: root@pve1-test:~# cat /etc/pve/sdn/controllers.cfg evpn: evpn asn 65000 peers 10.99.99.1 isis: pve1-test isis-ifaces...

I downloaded the file but it doesn't seem to be the new one, are you sure this is the correct link? root@pve1-test:~# sha1sum libpve-network-perl_0.8.1_all.deb 0c8d46ce6d88400324718d28e260050b928fcc4c libpve-network-perl_0.8.1_all.deb root@pve1-test:~# sha1sum...

I did some more testing with and without the libpve-network-perl patch so I could control the route-map easier. With the old frr and frr-pythontools packages I was not able to get a connection with route-map enabled. After disabling route-map as stated in my first post the connection suddenly...

The name itself in FRR is not used for anything outside the FRR config, only the isis-net 10.0000.0000.0005.00 is important to the other devices. It is nice however to have it configurable to match your other devices to administration. If we were to create another proxmox cluster in a different...

I wan't very clear on this one. The idea for the dynamic name is more administrative. FRR can only have one isis process/domain but the network doesn't. Making the name dynamic will help in case your network has multiple isis domains. I am testing on the latest stable release of proxmox. We...

Both fixed work so far! I tried setting the interface block in frr.conf.local and it appeared in the frr.conf as expected. Your other change is working as wel, I managed to get the setup working without the need to use frr.conf.local which is nice! My controller.cfg looks like this: evpn: evpn...

Thank you so much! We will try to test the beta this week.

Hi Spirit, I opened 2 feature requests, one for the "interface" block and another for the GUI addition. https://bugzilla.proxmox.com/show_bug.cgi?id=4901 https://bugzilla.proxmox.com/show_bug.cgi?id=4902 I saw more FRR users with issues regarding the route-map on Github, that part might be...

I've been trying to integrate the Proxmox SDN into an existing vxlan network using IS-IS. This way we'll be able to use the different vnets across multiple clusters as well as bind that to a vlan to attach legacy devices. Our lab setup is using a route-reflector on a spine switch and 2 leaf...