Just plugged in 5 3602i APs and instead of joining the controller for this building they joing a controller for a different building. Not sure what to look for on the controllers or what to post...but why would this happen? How can I get them off the wrong controller and onto the right controller?
A couple other things is to make sure you don't have master controller enabled on the WLC with the other building. Change the primary WLC on the AP(As rasika explained) to the WLC which you want to join and either wait a couple minutes or just reboot the AP.
Also change this on WLC. Go to the primary controller > Wireless > Access Points > Global Configuration
Just to add.... Since you already have WLC's and AP's that are up, most likely you also have option 43 or DNS configured which is pointing to that WLC that these new AP's are joining. Like Raskia mentioned, if you change the high availability, the AP should join that WLC you pointed to. The hostname is case sensitive!!!! If the AP fails to join the WLC, then maybe the WLC time is off or something is blocking udp 5246 and udp 5247.
The best thing you can do is put the AP on the same vlan as the WLC management, the AP needs to get a dhcp address or you need to configure a static address, but if the AP is on the same vlan, it should find the WLC and join using layer 2 broadcast. Once the AP joins, you can move that AP to another vlan since the AP already knows of the WLC.
Help out other by using the rating system and marking answered questions as "Answered"
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...