Howdy Pepfolks,
I’m working on a MBX High Availability design, but things aren’t quite working as expected.
Clients connected to the MBX that’s in slave mode (with establish connections enabled) do not get a connection unless it takes over the master role.
Is there some hidden checkbox I’m missing to make this work?
Thanks!
Hi…
Maybe another colegue will have another sugestions…
But… When I build the HA solution for Peplink devices…
I had a managed L2 switch " split by vlan access " ( LAN ports ) and other WAN ports " again, split by vlan access " between both peplink devices.
like this, but using a dummy switch… just a sample for lan side… and you need the same for wan side.
1 Like
Do you have the MBXs directly connected to each other for the heartbeat?
If so it will not work as expected, you need to have a switch between the MBXs so that the LAN port stays live and its can still attempt heartbeat requests or it sees it as both down.
1 Like
Yep, the red cable is intended to be the HA/VRRP heartbeat.
However this got me thinking, the MBX is essentially a router with an 8 port managed switch, so conceptually it should be possible.
After some further experimentation, setting all 8 LAN ports to access with a VLAN, with WAN3 set as the trunk/untagged appears to work!
Nice, glad you got it working.
1 Like