Hello there,
at my wits end on this one, since I cannot really find a reasonable explanation for this:
a cluster of 3 proxmox nodes, each with 10 network interfaces, bonded in pairs with 802.3ad comprising 5 networks that have 7 VLANs in total
Not using all that SDN stuff, mainly because I have no real grasp of them yet.
Due to client's security policy, the first 4 bonds can only serve 1 VLAN each, so
bond0 is VLAN 171
bond1 is VLAN 170
bond2 is VLAN 172
bond3 is VLAN 173
The fifth bond (bond4) hosts 3 VLANs and works quite as expected, so let's ignore it.
Intra-VLAN routing is supposed to happen on the ``far'' end of the Proxmox network, ie on the switches that the nodes are connected to.
The problem is that a service on VLAN 171 needs a DB that sits on VLAN 173.
This works all fine and dandy when a VM that uses 171 accesses a VM on 173 and those two VMs are on different Proxmox hosts in the cluster.
If they happen to be running on the same host, I see the packets leaving the client on VLAN 171 and see some kind of packets arriving on VLAN 173 but they are most definitely not the packets I sent.
So there must be some mixup on the way Proxmox handles the intra-VLAN routing but I have no idea how to go about debugging and hopefully resolving this. I'm not much of a Layer2 guy, so any pointers appreciated.
I am attaching /etc/network/interfaces of one of the nodes, apart from the IP address, the other two have identical config.
at my wits end on this one, since I cannot really find a reasonable explanation for this:
a cluster of 3 proxmox nodes, each with 10 network interfaces, bonded in pairs with 802.3ad comprising 5 networks that have 7 VLANs in total
Not using all that SDN stuff, mainly because I have no real grasp of them yet.
Due to client's security policy, the first 4 bonds can only serve 1 VLAN each, so
bond0 is VLAN 171
bond1 is VLAN 170
bond2 is VLAN 172
bond3 is VLAN 173
The fifth bond (bond4) hosts 3 VLANs and works quite as expected, so let's ignore it.
Intra-VLAN routing is supposed to happen on the ``far'' end of the Proxmox network, ie on the switches that the nodes are connected to.
The problem is that a service on VLAN 171 needs a DB that sits on VLAN 173.
This works all fine and dandy when a VM that uses 171 accesses a VM on 173 and those two VMs are on different Proxmox hosts in the cluster.
If they happen to be running on the same host, I see the packets leaving the client on VLAN 171 and see some kind of packets arriving on VLAN 173 but they are most definitely not the packets I sent.
So there must be some mixup on the way Proxmox handles the intra-VLAN routing but I have no idea how to go about debugging and hopefully resolving this. I'm not much of a Layer2 guy, so any pointers appreciated.
I am attaching /etc/network/interfaces of one of the nodes, apart from the IP address, the other two have identical config.
