Addressing on client bond

RouterOS Beginner Basics
1

I’m following this guide to create a bond:

https://help.mikrotik.com/docs/display/ROS/Multi-chassis+Link+Aggregation+Group

Bond appears to be up, LACP is working from what I can tell. What I don’t know is how to apply an IP address to the client-bond interface, if that makes sense? Links are up, but no matter where I apply the address (and again, I’m showing my ignorance here) I can’t get a response from the “client” in the picture.

/interface bridge
add name=bridge1 vlan-filtering=yes
/interface bonding
add mlag-id=1001 mode=802.3ad name=client-bond slaves=sfp-sfpplus24
/interface bridge mlag
set bridge=bridge1 peer-port=qsfpplus1-1
/interface bridge port
add bridge=bridge1 interface=qsfpplus1-1 pvid=99
add bridge=bridge1 interface=client-bond
/interface bridge vlan
add bridge=bridge1 tagged=qsfpplus1-1 vlan-ids=1

802.3ad is active; MLAG is showing connected and primary/secondary… just lost on the “where does the ip address go?”

2

IP address goes to bridge1 interface. The rest of interfaces (sfp-sfpplus24, client-bond, qsfpplus1-1) are ports or slaves this way or another.

There could be a mild confusion about where to apply IP address as you also have VLANs in the mix:

  • VLAN ID 1 is tagged over qsppplus1-1.
    Default configuration (which you did not override) is to have all ports set with PVID=1, and that includes bridge1 port … which means that bridge1 can be used directly as interface to that VLAN.
  • VLAN ID 99 is untagged over qsfpplus1-1 but otherwise unconfigured on other bridge ports. So VLAN 99 is essentially unusable in your device.
    If you want router to participate in VLAN 99 as L3 device, then you have to configure bridge1 port to be tagged member of VLAN 99 (/interface bridge vlan add bridge=bridge1 tagged=bridge1 vlan-ids=99) and create VLAN interface (/interface vlan add interface=bridge1 name=vlan99 vlan-id=99). Then use that VLAN interface (vlan99) to set IP address.

But then, since all of L2 config is a slight mess (inconsistent use of VLANs, 802.3ad bond with single slave link, MLAG with members of different L2 “technologies”) it’s impossible to tell what is the goal and if your attempt so far is even in the right direction. So you may want to explain (in plain English) what you’re trying to achieve and we may be able to point you in the right direction.