there are config example about bonding in user manual
/interface bonding add slaves=ether1,ether2 name=bond1
/ip address add address=172.16.0.1/24 interface=bond1
but this is for layer 3 bonding, how to config layer2 bonding to connect to cisco switch which was configured with Port-Channel Interfaces
you mean 802.3ad?
not sure, maybe static aggregation (user config), maybe dynamic aggregation( lacp protocol), which cisco switch supports both ways.
by the way, Why do mikrotk inherit Linux's bonding load balancing algorithm instead of directly using the switch manufacturer's aggregation load balancing algorithm such as {dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac}
ROS only supports statically configured bonds. 802.3ad is de-iure industry standard and it’s supported on all Mikrotik devices. Only a few can offload that to switch chip, IIRC RB4011 is not one of them.
Because ROS is essentially UI wrapped around linux kernel. And I don’t think it worth complaining about how things would be better the other way around, ROS is the way it is and will stay (at least during v7 life time). We just have to accept this reality. Other vendors (you mentioned) have their own strengths but come with price to be paid.
There are a few custom things, one of them is (some) support for HW offload … but the idea is tho have similar/same feature set available on all devices running ROS and with same UI. Which means that HW offload mostly means that MT devs did configuration translation from ROS UI to specific switch chip API … and since each switch chip family comes with different API it’s a bit of an effort for MT devs to do it for all devices running ROS. Hence missing HW offload on some devices where hardware is capable of performing certain functions.