Being a cisco guy, I am having some trouble with LACP sharing on XOS when I need to move a device (a switch or a server) to another group of ports. Since config master in XOS must be a sharing group member, I keep bumping into having to 'disable sharing', then 'enable' a new one and apply all the settings (vlans etc) all over again. Even worse when the ports overlap.
I made a feature request to create a new entity for LACP config master in XOS, but its being ignored so far. So I decided to do some magic.
All our Summits are in stacks. I have noticed one can have a config master on a non-present slot in stack. We can have up to 8 members in a stack topology, but we do not intended to go higher than 3. So, all I need to do is to create a slot 8 device with as many ports as I want to have LAGs. Then I create all my 'sharings' with a config master on that non-present slot. Now I can move member ports wherever I want - no config changes for config master.
So far this was tested in our lab and it looks good. However, before going into production with this crazy idea, I would like to be criticized by experienced Extreme professionals. What caveats are waiting for me in this configuration? Any better ideas to avoid the 'config master port' trouble&