Thanks for the reply. With regards LACP, good question. I was under the impression it was in place, but based on the CLI output, I'm not so sure. Output below is from the CLI for one of the APs
(Controller) # show ap debug lacp ap-name AP001
AP LACP GRE Striping IP: 0.0.0.0
AP LACP Status
--------------
Link Status LACP Rate Num Ports Actor Key Partner Key Partner MAC
----------- --------- --------- --------- ----------- -----------
Up slow 2 17 10 00:59:dc:a4:9f:80
Slave Interface Status
----------------------
Slave I/f Name Permanent MAC Addr Link Status Member of LAG Link Fail Count
-------------- ------------------ ----------- ------------- ---------------
eth0 b4:5d:50:c7:d7:ea Up Yes 0
eth1 b4:5d:50:c7:d7:eb Up Yes 0
GRE Traffic Received on Enet Ports
----------------------------------
Radio Num Enet 0 Rx Count Enet 1 Rx Count
--------- --------------- ---------------
0 11396 0
1 2824 0
non-wifi 337205 0
Traffic Sent on Enet Ports
--------------------------
Radio Num Enet 0 Tx Count Enet 1 Tx Count
--------- --------------- ---------------
0 7474 0
1 3 0
non-wifi 7690 518176
It looks to my undertrained eye that LACP is in place, though based on the documentation link, we dont have a GRE striping IP in place, though the LMS IP address is configured. I should add from the original post, that the port-channel does become active, we just need to bring it online in a controlled manner one interface at a time.