topic Re: As discovers an access point to the controller on different networks and different branches in ZoneDirector

As discovers an access point to the controller on different networks and different branches

carlos_donoso_7 — Fri, 15 Jan 2016 15:11:55 GMT

Good afternoon, I have my controller and several access points connected in a network within the same network without VLAN.

Now what I need is to connect two access points are in another branch and connecting to the controller.

The problem is that they are in diferetes networks, branches are connected via MPLS.

I suggest doing? you can connect a controller to an access point on a different network that are geographically separated and connected via MPLS? thanks.

Re: As discovers an access point to the controller on different networks and different branches

chuck_aaker — Fri, 15 Jan 2016 15:19:16 GMT

Reference this document https://support.ruckuswireless.com/answers/000001255

Re: As discovers an access point to the controller on different networks and different branches

monnat_systems — Sat, 16 Jan 2016 05:00:57 GMT

Carlos,

Its a pretty common scenario. As long both those two different networks are talking to each other, there is no problem.

You just have to run following CLI command using putty on the AP which will be residing in THAT different network. IP address below in the command is controller's IP address. We are literally asking the AP to contact the controller on THAT ip. this is being done as AP may have to jump L3 boundaries and this activity helps.

set director ip

Example : set director ip 192.168.1.99

Re: As discovers an access point to the controller on different networks and different branches

martin_martin — Sat, 16 Jan 2016 21:57:34 GMT

Hi Carlos,

Exactly as Monnat has said.

for ZoneDirector

set director iP

or with SZ-100/vSZ/SCG AP firmware

set scg ip

Regards
Martin

Re: As discovers an access point to the controller on different networks and different branches

seanmuir — Thu, 21 Jan 2016 00:37:04 GMT

Also make sure that the Firewall has the appropriate ports open: