Search results

Please post the iperf (iperf3) commands you are running on the server and clients. Please share your /etc/network/interfaces file. What model of NICs are you using on each host? What model are the switches you are connecting your PVE hosts to?

Mounting the NFS share from your Synology and using a Sync Job requires a couple of extra steps to set up, but once it is set up, it will be automatic and will not require you to SCP the files over manually. It would be slow, but the speed might be acceptable, given your use case.

@daubner Thank you for sharing this information. Your information makes it reasonable to conclude that a prolonged broadcast storm on the host network caused the reboot. This is based on the assumption that the cluster was set up much like you have it right now. I'll explain...

These are two standalone hosts, correct? The SDN is easier configured in the web GUI. Are you adding a physical NIC to the PVE host and trying to make it available to the VMs? For a physical NIC on the host, you would add it to the bridge used by the SDN. You can do that in the...

Because of the way PBS handles the data, you will need to use another Datastore ("repository" is a misnomer) and a Sync Job to move the data. Yes, you can use Removable Datastores.

It sounds like you have an issue with your Corosync links. Please provide the following information: Contents of /etc/network/interfaces The output from corosync-cfgtool -s The output from ha-manager status The contents of /etc/ceph/ceph.conf

Yes, when a node joins a cluster, many parts of its configuration are overwritten -- including the certs. If you add your custom cert after the node has joined the cluster, life will be fine.

When you say "crashed," what exactly happened? Did the node stop responding? Did it spontaneously reboot? Or... ?

Hey @Darkk It would be totally fine to wipe it and reload PVE before using pvenode to remove it from the cluster. This would be no different from having a node hard fail and then replacing it.

@intelliimpulse@intelliimp You are not the first. :) https://forum.proxmox.com/threads/sdn-vnet-trunking-tagging.146199/ https://bugzilla.proxmox.com/show_bug.cgi?id=5443 https://bugzilla.proxmox.com/show_bug.cgi?id=6272 I recommend you comment on the bug (aka feature request) that matches...

@wolfspyre We always used Open vSwitch (OVS) and encouraged our clients to do the same. It was easier to do some things. However, since PVE SDN was released, we have discouraged using OVS and strongly recommend SDN. Configuring OVS is done on a per-host basis where SDN is cluster-wide, which...

You are welcome. :-) Use the Add button with the same plugin.

You do not need OVS for PVE SDN. You are describing SDN Simple Zones. Each Vnet is an isolated network that only connects VMs. You would use either SDN VLAN Zones or SDN EVPN/VXLAN Zones. If you use the VLAN Zone, you must ensure the switches are configured for the VLANS. If you use...

You could replace this code: # dummy nic for node-scoped intra-node-comms for VMs auto foonic iface foonic inet manual ovs_type OVSIntPort ovs_bridge vmbr2 ovs_mtu 9198 pre-up ip link set foonic txqueuelen 13888 auto vmbr2 iface vmbr2 inet manual ovs_type OVSBridge...

If your Synology is local to your DR PBS, you could present it to the PBS with either iSCSI or NFS. Once mounted on the DR PBS, you could put a PBS Datastore on it. Then, you would use a Sync Job to move the backups from the primary PBS Datastore to the Synology-based Datastore. IMPORTANT: The...

Remove the fingerprint in PVE. You do not need the fingerprint if you have Let's Encrypt TLS certificates and connect using a hostname covered by that TLS certificate. There is a fingerprint because the starting TLS certificate is self-signed and, therefore, not trusted. The fingerprint is...

Yes. If you have two physical interfaces (e.g., eno1 and eno2), you can bond them (e.g., bond1) and use LACP. Then, you would assign the bond to a bridge (e.g. vmbr3) that was VLAN-aware. The VMs that needed multiple VLANs would use vmbr3 as their VM's bridge. For VMs that only need a...

Ah. That makes sense. That functionality is not currently available in the SDN. We have implemented that by using a VLAN-aware bridge. However, that same bridge would need to exist on each PVE host in the cluster. The downside of this approach is that guests can tag the traffic however they...

@intelliimpulse@intelliimp you would create a vnet for each of the VLAN tags. Each vnet would then show up a bridge. If one VM needed access to three vnets, you would create three NICs on the VM.

Hi @greptrig There are two commands that should get you what you need: ip Command If you run ip a from the command line, it will match your interface names to their MAC Addresses. lshw Command The lshw the command will need to be installed, but it will give you much more information about...