Hair-pulling behavior with 802.3ad or balance-xor on RB2011-iL

I anticipate I discovered a bug, but the many Mikrotik docs I have read are not very clear. All forum posts which contradict some of the docs, indicate 802.3ad does not function unless via CPU are several months old. Release notes and docs seem to indicate 802.3ad is supported via the switch chip, now. Regardless, I see the identical behaviour when using balance-xor:
LACP_Issue.JPG
All anticipated sent and received traffic seems to be ‘mirrored’ to the second bonded interface (ether2). It seems all of the traffic is mirrored to the interface not chosen by the layer 2+3 xmit_hash_policy (ether3). This is a simple home lab configuration comprised of an RB2011iL (RouterOS 6.38.1 & firmware 3.33), a single iSCSI Linux target (ether2 & ether3) and a single Windows initiator (ether5):
NetworkLayout.txt (508 Bytes)
I’ve been up and down on this behavior and left the details from this post to prevent confusion or unnecessary complexity. I appreciate comment from anyone who does not lead me to bridging…

/interface vlan
add interface=ether10 name=ether10-vlan6 vlan-id=6
/interface bonding
add mode=802.3ad name=bond0 slaves=ether2,ether3 transmit-hash-policy=layer-2-and-3
/interface ethernet switch port
set 2 default-vlan-id=2
set 3 default-vlan-id=2
set 5 default-vlan-id=6
/interface ethernet switch vlan
add independent-learning=no ports=ether2,ether3,ether5 switch=switch1 vlan-id=2

Thank you!

Bueller ?