Ensuring That APs Can Discover the Controller on the Network
Method 2: Perform Auto Discovery on Same Subnet, then Transfer the AP to Intended Subnet
SmartCell Gateway 200 Getting Started Guide for SmartZone 3.4, 800-71126-001 Rev A
88
Method 2: Perform Auto Discovery on Same
Subnet, then Transfer the AP to Intended
Subnet
If you are deploying the AP and the controller on different subnets, let the AP perform
auto discovery on the same subnet as the controller before moving the AP to another
subnet. To do this, connect the AP to the same network as the controller. When
the AP starts up, it will discover and attempt to register with the controller. Approve
the registration request if auto approval is disabled. After the AP registers with the
controller successfully, transfer it to its intended subnet. It will be able to find and
communicate with the controller once you reconnect it to the other subnet.
NOTE:
If you use this method, make sure that you do not change the IP address
of the controller after the AP discovers and registers with it. If you change the
controller’s IP address, the AP will no longer be able to communicate with it and will
be unable to rediscover it.
Method 3: Register the Controller with the
DNS Server
If you register the controller with your DNS server, supported APs that request IP
addresses from your DHCP server will also obtain DNS related information that will
enable them to discover controllers on the network. Using the DNS information they
obtained during the DHCP request, APs will attempt to resolve the controller IP
address using RuckusController.{DNS domain name} and
zonedirector.{DNS domain name}.
To register the controller with the DNS server, do the following.
1
Open the DNS zone file, and then add two records with the following information:
•
Record Key#1: RuckusController
Type: A (IPv4 Domain Name Translation)
Value: (IP address of the controller)
•
Record Key#2: zonedirector
Type: A (IPv4 Domain Name Translation)
Value: (IP address of the controller)
