It is that simple 🙂
With Fabric Attach enabled it's even simpler, because the "sharing" is build automatically by the SwitchEngine node, when he detects (from a switch cluster working as FA server) same FA system ID over multiple links.
look at ports 49 & 50 here:
When you write 8600 - which one do you mean ? ERS 8600 or VSP 8600. Both support Fabri Connect and Fabric Attach server, so if they are running in SPBm mode, that migration would be quite easy - you would just have to enable FA on the MLTs to these new switches (do not use FA message authentication, as this is per default disabled on SwitchEngine ports per default).
here is - from the example above - what happens, when the switch builds the sharing dynamically: (look at flag d - Dynamically created shared port)
CmpA-E1.6 #% show sharing
Load Sharing Monitor
Config Current Agg Min Ld Share Ld Share Agg Link Link Up
Master Master Control Active Algorithm Flags Group Mbr State Transitions
================================================================================
49 49 Static 1 L3 Ad 49 Y A 1
L3 d 50 Y A 1
================================================================================
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback
Minimum Active: (<) Group is down. # active links less than configured minimum
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based
(L3_L4) Layer 3 address and Layer 4 port based
(custom) User-selected address-based configuration
Custom Algorithm Configuration: ipv4 L3-and-L4, xor
Custom Hash Seed: Switch MAC address (0x9699A1D2)
Flags:
A - All: Distribute to all members,
d - Dynamically created shared port,
L - Local Slot: Distribute to members local to ingress slot,
P - Port Lists: Distribute to per-slot configurable subset of members,
R - Resilient Hashing enabled.
