Please consider solved. The physical cards were the issue. While they work on Proxmox for something like a PCAP, they do not work for bonds or a second vmbr. The below config worked just fine with Intel cards:
auto lo
iface lo inet loopback
auto enp5s0
iface enp5s0 inet static...
After another day of no success, I did a point-to-point using enp8s0 to the same port on another server. Since this process did not work, but the same thing is already working for the SAN on an Intel XG NIC, I started to suspect the NIC.
I plugged in a USB NIC and found it to immediately work...
@wigor I actually do not want an address on that interface, but simply removing it does not work. It might be a routing issue now, so trying a few things on that front. The downside is that I now have less of a troubleshooting plane on the Proxmox node (I cannot ping from an interface that...
When attempting ping -I vmbr1 172.16.0.1, arp seems to be the problem.
tcpdump -ennqti vmbr1 \( arp or icmp \)
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr1, link-type EN10MB (Ethernet), capture size 262144 bytes
68:1c:a2:13:2c:85 >...
Small update:
I can ping from vmbr0 like ping -I vmbr0 172.16.0.1 but not from vmbr1 like ping -I vmbr1 172.16.0.1.
Started looking into routing issues on the Proxmox node, ip route output is below:
default via 172.16.0.1 dev vmbr0 onlink
172.16.0.0/22 dev vmbr0 proto kernel scope link src...
I am in the process of troubleshooting a single node in my cluster before expanding the configuration.
Each node has 4 NICs:
- enp5s0 is the primary NIC where the webui is attached (working properly)
- enp10s0 is an XG card for a separate SAN (working properly)
- enp8s0 and enp9s0 are a pair...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.