It is a fact that Cisco WLCs per their design supports only LAG type or protocol which has no negotiation (in this aspect LAG considered as non-LACP and non-PaGP etherchannel technique, in some documentation though LAG (link aggregation groups) may be considered as a general term for all types of protocols to build etherchannel ). LAG on Cisco switches can be recognized by null in the “protocol” field, as shown below:
Pic.1 – Po1,Po2 – LAG etherchannels
In Lab environment following hardware was used and connected:
Pic.2 – Lab topology to test LAG support by Aruba switch
Configuration on Cisco WLCs (enabled LAG) and on Aruba core2 L3 switch are shown below:
Pic3 – LAG settings on WLC1
Pic4 – LACP configuration and verification on Aruba core2 L3 switch
Ping and SSH from core1 to WLC via such etherchannel were successful. Per such example, Aruba automatically negotiates LACP or LAG based on what is configured on the other end.