Quackers Posted January 17, 2012 Posted January 17, 2012 We have just taken over support of a second site, and are having a private 100 Meg link put in between us and them. They have no WiFi, and we also want to move to a managed wifi system. So my question is, do i need 2 Zone Directors (1 at each site) or can i get away with 1? Does all the WiFi traffic go through the Zone Director or does it purely manage their settings, so the bandwidth usage is not that much? I do not want 1 Zone Director if all the traffic from the remote site AP's has to come over the 100 Meg link and back down again.
Quackers Posted January 17, 2012 Author Posted January 17, 2012 Nobody with Ruckus knows how it works?
Haptic Posted January 17, 2012 Posted January 17, 2012 (edited) Hi Quackers, With the private link it would depend on latency across the network- basically if you have a latency of higher than 100milliseconds between AP's and controller (regardless of physical location) you will have issues. As for data backhaul, it is a setting you can apply (if you also lick windows) but something I never really recommend, so no you won't have data being hauled back across the 100 meg connection to the ZD. I'll give you a call to discuss further. Thanks, Mark Edited January 17, 2012 by Haptic
localzuk Posted January 17, 2012 Posted January 17, 2012 Just to clarify Mark, by default only the management info is sent back to the controller, the data isn't. You can (if you're odd) enable a config to do that, but it is inadvisable. 100Mbit between the 2 sites should be fine, IMO, to have a single controller. I'd suggest borrowing a test setup and trying it out first. Plenty of suppliers will do this for you.
White_Fi Posted January 17, 2012 Posted January 17, 2012 Tunnelling traffic is useful for Layer3 traffic back to the ZD. e.g - a VoIP call roams from AP1(10.19.90.0/24) to AP2(10.19.95.0/24) and drops the call. With L3 tunnelling the IP is preserved and the call is not dropped. It is an architecture most vendors are moving away from. By default Ruckus' architecture is distributed forwarding (an architecture vendors are moving to, they really have no choice these days). Authenticated traffic(only) is dropped from the AP on the edge switch.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now