7363 AP Want to set up as a standalone off the controller (without the controller seeing the AP )

  • 1
  • Question
  • Updated 5 years ago
  • Answered

we are a small education department with a ZD 1100 and Licensed for only 12 APs, we have aquired another 7363 AP, this cannot go onto the Controller as its not licensed, (the limit is already reached)  we want to set it up as a standalone non-managed with the same SSID as the establishment so a few devices can connect to it in a small out house room, it will be AC powered not POE, I have gone into the AP and set up manually, BUT after a few days the controller see's the non managed stanadlone AP (as number 13) and disconnects it, or disconnects and random other.

I have also made sure of disabling on the controller to "automatically allow new AP's to connect"

but still this hasnt worked, the controller still eventually see's the AP thinks it as no 13 and disconnects.


Many Thanks
Photo of Angelo De Luca

Angelo De Luca

  • 6 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 1
Photo of Karl Lavender

Karl Lavender

  • 21 Posts
  • 5 Reply Likes
Is your controller set to block malicious SSID ?  If it sees a standalone broadcasting the same SSID as one it handles, it would consider this malicious.  I don't think the option is on by default, but it would be work checking.  As an alternative, put it on a different subnet / vlan if you can so the controller has no real contact with it.  It should allow routing, you'd just miss features like FT etc.
Photo of Angelo De Luca

Angelo De Luca

  • 6 Posts
  • 0 Reply Likes
Hi Karl

I was not aware of such a setting, not too sure where that setting is, I will dig around to find.
Yes I was thinking of putting on a different subnet, but thought I could do all fromn the same SSID so it would be seamless transition if a device was to connect to it.

thanks for useful info, and pointers.
Photo of Sid Sok

Sid Sok

  • 102 Posts
  • 49 Reply Likes
Is the new AP on the same subnet as the controller?

The AP will try to connect to the ZD in the following order:

1. "set director ip ..."
2. DHCP Option 43
3. DNS lookup for "zonedirector"
4. L3 broadcast

Try putting the standalone AP on a different subnet, reset to factory default then configure the trunked switch port with the appropriate vlan and that should keep the AP from trying to connect to the ZD.
Photo of Michael Brado

Michael Brado, Official Rep

  • 3298 Posts
  • 523 Reply Likes
Another option to keep specific APs as Standalone and Not ZD-managed, is to SSH into the AP
and assign a non-existent IP address for ZoneDirector search.

set director ip      (you can specify up to 2 ZD IP addresses, so use 2 bogus IPs)

Your DHCP server will likely gve them the same address after reboot, but you can
delete these AP from Configure/APs on the ZD and they won't try to reconnect again.
Photo of Angelo De Luca

Angelo De Luca

  • 6 Posts
  • 0 Reply Likes

Thanks for all the info and support on this, this is how I got a standalone AP working, without being seen by the ZD Controller. (the process was what Michael Brado suggested ) this was the procedure:

 Tell the AP to connect to a "fake" controller –


1. Before connecting the Access Point in network, connect Access Point to laptop and SSH into it using application like Putty.

2. Provide the IP address of the Access Point( to ssh into it. Log in with AP credentials

Username: super
password: sp-admin

3. After successful login, execute the below commands:

rkscli: set director ip

** Please reboot for this change to take effect


rkscli: reboot

After successful reboot of Access Point, now connect it back to the network.

Now Access Point will try to discover the ZD with IP address is not present) and hence would work in Standalone mode.
Photo of Michael Brado

Michael Brado, Official Rep

  • 3223 Posts
  • 490 Reply Likes
Then, all you need is to find your AP MAC address on the DHCP server to determine what IP it was given on the network.

Note:  If you plan to have Standalone mode APs in the network, manually assign them an IP address outside of the
DHCP scope used by the server, with a 'reserved address', like your ZoneDirector, so you can always 'find' them, or
on another VLAN, like Sid suggested.