Search results

Good find — that explains it. If you still get a response with the fiber unplugged, the link was never actually active. Check that your SFP+ modules or DAC cables are compatible with the HP 546SFP+ (Mellanox ConnectX-3 Pro), and run ethtool ens3d1 to confirm the link status. Once the link comes...

Hi, please share more information as following if possible: Host network config: post the relevant parts of /etc/network/interfaces (or whatever file you use) showing eno1, the bridge (vmbr), and how they’re connected. VM NIC info: inside the VM, what NIC model is shown (e.g. virtio, e1000...

Hi @logan893 , yes you are right. the older card doesnt have the necessary drivers for what you are looking for.

Thanks for sharing your config — you’re almost there. A few quick points: Keep only one bridge (vmbr0) — you already made it VLAN-aware, so no need to create vmbr0.110 unless the Proxmox host itself needs an IP inside that VLAN. For your VMs: Use bridge vmbr0 Set the VLAN tag (e.g. 20 or 30)...

Are you running the latest PVE9? If so, you might need to upgrade to ConnectX-3 or newer to read the info

Hi, have you started your configuration in Proxmox VE nodes? If so, can you share the config in there?

Are the eno1, 2, 3 and 4 all on the same physical NIC or motherboard?

Hi, are you running on default NIC settings and no firewall on VM?

Just a quick question - Is the bridge in Proxmox VE set to VLAN aware?

Running in VM will work, but on the Host itself will see conflicts and complications.

The log shows the disk mirror starts over NBD via SSH, progresses for minutes, then the channel fails (“open failed … Broken pipe”). That’s classic of a transport drop under sustained load. Some of the things you can check - Are MTUs identical end-to-end on the migration path (source NIC...

Hi, it seems like its a symptom of a mis-configured or stale network state. I’d start to check with the host’s interface setup and check whether ARP entries are aging out too aggressively on the switch side.

Hi, it seems like your host’s vmbr0 only shows link-local (fe80::…) — no global IPv6. That suggests the host bridge isn’t getting or relaying a global IPv6, so containers won’t have an upstream path. Can you check vmbr0 has a proper global IPv6 + default route, and that IPv6 forwarding /...

Hi, at your host firewall, can you add a rule to explicitly allow DHCP broadcasts (UDP ports 67 & 68) and see it if works?

@tqt3e you might want to check if there is an update on Bios firmware available. I suspect that there is a need to update it.

@silke You’re correct: Proxmox (and corosync) recommend a dedicated NIC for the cluster to avoid heartbeat issues during congestion. A workable compromise: Node1 & Node2: connect a dedicated NIC each to your spare switch ports, use this as the cluster network (vmbr2). Node3: can share the VM...

@logan893 are you running VM using VirtIO-SCSI or IDE?

@akulbe I would remove all the VMs from the node, then do a clean reinstall. Then add back to the cluster to be safe.

@akulbe is this PVE part of a cluster or standalone?

Looks like the helper script is not really helping. What do you want to achieve exactly? If it can be achieve with PVE's UI, should use that instead.