Recent content by stefan.runkel

  1. [ovs] mtu on several devices are "wrong" after a reboot

    After some severe networking issues with corosync, we had to revert the mtu changes. We are switching back to 1500 mtu. The problem is simple. PMTUD (Path MTU Discovery) only works with TCP. corosync works with UDP - thus MTU will definitely be an issue if there are differences in the network...
  2. [request] please add zpool_influxdb to the zfs packages

    Hi, according to the github repo; https://github.com/openzfs/zfs/tree/zfs-2.1.2/cmd/zpool_influxdb zpool_influxdb should be available with v2.1.2 - which we have currently installed (zfsutils-linux). Please include this program, so we can do better monitoring for the zfs drives. Thank you Alex
  3. [ovs] mtu on several devices are "wrong" after a reboot

    @spirit what mtu will the vlans have, if I remove them from the interfaces-config? I think they should have the mtu from vmbr9 -> 9000.
  4. [ovs] mtu on several devices are "wrong" after a reboot

    Ah - sorry for my rudeness. Thank you for the hint - I should be more thankful :D I'll correct that and I'll look for other misconfigurations I might have in the network. Greetings Alex
  5. [ovs] mtu on several devices are "wrong" after a reboot

    I've copied most of the config at the beginning and expanded it later. We need a good overview of all vlans and their purpose, so it's easier to put the VMs NIC to the according vlan. Some vlans are used for the Proxmox hosts (vlan010 and vlan099), that's why there is an IP assigned The...
  6. [ovs] mtu on several devices are "wrong" after a reboot

    There you go - I had to censor IPs, remove some comments and routes as well as some names. The namechanges (the vlans) were done properly via regex, so you could reuse this config in theory.
  7. [ovs] mtu on several devices are "wrong" after a reboot

    Hey there, after testing the behavior a bit, there are probably two bugs I noticed. One "bug" is resolved with an ifreload or with ifup -a. 1. A ovs_bonds Interface have the mtu of 1500 - despite setting it to 9000 (ovs_mtu 9000). netstat -i (only bond0 and vmbr9) Kernel Interface table Iface...
  8. Proxmox-Cluster: Anbindung an HPE MSA 2052

    Hallo zusammen, vielen Dank für den Input. Ich habe es befürchtet, dass wir mit so einem teuren Storage keine anderen Möglichkeiten haben - das ist natürlich verdammt traurig und definitiv ein Fehlkauf vom Kunden :-/ Der Verzicht auf Snapshots ist natürlich gravierend. Habe ich es richtig...
  9. Proxmox-Cluster: Anbindung an HPE MSA 2052

    Hallo zusammen, wir haben aktuell einen Proxmox-Cluster mit drei Nodes in Betrieb. Nun möchten wir unsere neue HPE MSA 2052 an diesen Cluster per FibreChannel anbinden. Jede Node ist mit einem FC-Kabel an einen der MSA-Controller angeschlossen. Sehe ich es richtig, dass wir nun als erstes...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!