One Wireless Profile for Multiple Sites

Question

Hello,
I was wondering if someone can help me get my head around what I am trying to do and whether or not it is even possible.  The goal is to give our users the ability to go to any of our locations (which are connected via circuits) with a Cisco 7925 phone and have it function.  So in essence we want to have a single Network Profile so the user doesn't need to do anything to the phone for it to function if the move between locations.  We are using a 5508 Controller w/ 3502 APs.
So at our main location I have an SSID created, which is bound to an interface I created on the controller in our Voice VLAN.  This works great, the phones pickup an IP in the block and everything functions as it should.  My confusion is how do I create the same SSID / security parameters for each of our other locations, so if they leave our main site with the phone and goto the other location it sees the SSID, associates and then picks up an IP address in the Voice VLAN at the other location?  What confuses me is the AP / controller seem to handle all the DHCP requests, so even if I have a ip helper-address on say the routers interface it isn't actually being forwarded from the router, it is coming from whatever interface is bound to the WLAN on the controller.  I'm sure I didn't explain this well, I'm not looking for a step by step guide maybe just some pointers as to examples or what I need to study up on to accomplish this.  Thank you very much for all your time.

Answer 1

If this other location is not deemed remote (with a slower WAN link), then you may want to look into utilizing AP groups vs H-REAP.
AP groups would allow you to specify which SSIDs and associated VLANs are enabled per AP group. Then just add the necessary APs (e.g. APs in BLDG-2) to that group (e.g. BLDG-2).
But also depends on where you want the client subnet terminated.
With AP groups or H-REAP central switching the client subnet would terminate at the central location where the WLC is located.
With H-REAP local switching, the client subnet would terminate locally where the AP resides.
Central switching just means all data will be sent back to the WLC, where local switching means that the data will be routed out locally.
To me, AP groups are easier to configure as the config is done at the AP group and then just a matter of putting the AP in that group.
With H-REAP, you have to configure the AP, H-REAP group including adding the AP to the group as well as SSID config if wanting local switching.
See the following for more info.
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob41dg/emob41dg-wrapper.html
Sent from Cisco Technical Support iPhone App