Solved: H-REAP with local switching at multiple remote sites

JUSTIN LOUCKS · ‎07-28-2009

I am doing some testing with H-REAP for deploying 1-2 APs at remote offices to allow for centrally managed wireless across the board. I have one AP up and running in a lab right now but it generated a question for me. Can I use a common SSID at all sites with H-REAP and local switching? I guess my concern is with the need for a virtual interface definition for each remote site and the possibility of needing to tie the SSID to that interface. I do have a working SSID tied generically to the management interface right now and it works but I don't know if it should be that way. I'm just hoping that I don't have to maintain a unique SSID for each site to properly tie it back to a virtual interface on the controller.

dancampb · ‎07-28-2009

No you don't. When you go to configure the AP you will just define which VLAN number you want the traffic for that WLAN to dump to.

View solution in original post

dancampb · ‎07-28-2009

Sure, you can have a H-REAP WLAN spread over multiple sites. You just need to define which WLAN the AP will be dumping the traffic to locally for that site.

JUSTIN LOUCKS · ‎07-28-2009

Thanks. Do I even need an interface on the controller for each site's layer 3 gateway that the AP uses or am I overcomplicating things? I've read so many different documents and examples on H-REAP now that I think I've confused myself. I guess in summary, can I just point my SSID to the management interface of the controller and make sure the SSID is mapped to the appropraite VLAN on the AP definition in the controller?

dancampb · ‎07-28-2009

No you don't. When you go to configure the AP you will just define which VLAN number you want the traffic for that WLAN to dump to.