ElasticXL Bond/Aggregate Behavior

[Kit_E]

Hi everyone,

I’m hoping someone with experience in ElasticXL clustering can shed some light on how bonding/aggregation works in this setup.

Let’s say we have a two-member cluster, and each member has a bond configured on a single port (e.g., eth1) using 802.3ad (LACP). Both eth1 interfaces are then connected to a single switch, with the corresponding two switch ports also configured for LACP.

However, this setup is causing an error on the switch—one of the LACP ports gets disabled. I initially assumed that since the SMO for the cluster was configured to bond on eth1, it would sync across the cluster nodes, effectively creating a shared bond using both eth1 interfaces.

This is our first time working with cluster technology, so apologies if this is a basic question. Any clarification or insights on the correct bonding approach in this scenario would be greatly appreciated.

Thanks in advance!

[emmap]

The bond configuration is sync'd to each cluster member, but the bonds on each cluster member are individual bonds. So in your case, you have two separate LACP bonds with one interface in each, and your switch configuration needs to change to reflect this.