The setup is in a Lab enviornment with an East and West campus to simulate two buildings, and everything was working fine until we wanted to use AP Group Vlans. Once we configured the AP Group Vlans, updated the AP Templates and pushed them out - it broke.
All of a sudden, all three wlans (broadcasting SSID's) could not be seen, but all AP radio's were up. We rebooted the AP's but nothing changed. We RESET one AP and once it found it's controller (via DHCP Option 43), all WLANs came back online for the EAST campus...the WEST Campus still cannot be seen. We have rebuilt every aspect of the setup from scratch and this still happens.
Here's my question - If a WLAN is tied to the Mgt Interface at the WLAN level but is then tied to another interface in the AP Group VLAN, does the AP Group VLAN setting trump the WLAN level setting (Controller ->WLANS->WLAN ID->Interface) OR do the WLAN/Interface assignments have to match between the Controller WLAN level and AP Group VLAN settings?
My thought is that the AP Group VLAN - WLAN to Interface config overrides the initial Controller WLAN to Interface config.
Here's the setup:
Cat6506 - 12.2.18 SXF5
2 x WiSM - 12.2.18 SXF5
Interfaces - East_EAP, East_WEP
WLANs/SSID - LLeap/lableap, LPeap/labpeap, LWep/labwep
Cat6506 - 12.2.18 SXF5
1 x WiSM - 12.2.18 SXF5
Interfaces - West_EAP
WLANs/SSID - LLeap/lableap, LPeap/labpeap
Each campus is on a seperate subnet to simulate two different buildings.
All WiSM's/Controllers have the same Virtual Interface and are in the same Mobility Group - we want to roam between buildings.
I am tying the Leap and Peap WLAN's to the same Interface (Eap_East or Eap_West) in each respective campus and WEP on its own Interface.
(This is done in the AP Group VLAN config - Under Controller->WLAN->WLAN ID all WLANs default to Mgt Interface)
I have AP Group VLANs setup for each Campus:
Lab_East_Group --> LLeap/LPeap tied to East_Eap Interface. LWep tied to East_Wep Interface
Lab_West_Group --> LLeap/LPeap tied to West_Eap_Interface (no wep in the West Campus).
AP Templates are setup for each Campus specifying Primary, Secondary and Tertiary Controllers, Group Vlan Name and WLAN Override enabled:
AP Template Lab_East --> Group VLAN - Lab_East_Group, WLAN Override enables Leap/Peap/Wep Wlans
AP Template Lab West --> Group VLAN - Lab_West_Group, WLAN Override enables Leap/Peap Wlans
You are correct and what you need to do is have only those three controllers in one Mobility groups. Unless you need all wlc on a single mobility group. The most stable code I think is 4.1.185. If you decide to go to 4.2 then go with 4.2.112. I have that code running in a couple of my clients.
I would also upgrade the boot image.