There is 1 3750 model on which you can split your LAG. That is, on the controller you still create only one LAG (you can't create more than 1 as Fella explains, it's an on or off type of feature), 2 links go to the first 3750, 2 others to the second, and a link between switches ensures consistency.

Not a good or recommended design though. If you lose your switch, you probably lose along with it a good part of your network anyway. LAG relies on the idea that redundancy is built by having space on a backup controller.

Having a AP Manager per port, therefore physical links to different switches, is another possibility, but it has also some other limitations (load balancing system)... I try to use LAG and controller backup whenever it is possible...

Jerome is correct about the 3750 using cross stack etherchannel. Or if your core chassis is running VSS you can do that also.

Cisco mentions this: Do not configure a LAG connection that spans across multiple switches. When you use LAG, it must be with all ports that belong to the same EtherChannel that goes to the same physical switch

But who knows if this was released before the cross stack or VSS.

Thx guys for the input.

So the recommended design is NOT to have a WLC across two switches (LAG or not). Correct?

And use the backup controller as the redunacny for the wireless infrastructure, ie N+N and N=1 etc etc

Is this correct?

Many thx once again,

Ken

I would have to say yes.... that is the recommended best practice. If you can afford to have antoher controller, then split up the ap's on both wlc's. You can also place all ap's on one wlc and let the other controller be your backup. Either way, you can have the backup wlc on a different switch in case the other switch fails.

many thx mate