Aerohive access point, Deployment Manual

Page: 134 / 221

Deployment Guide 133
E
XAMPLE
4: C
ONNECTING
H
IVE
AP
S TO
H
IVE
M
ANAGER
How HiveAPs Connect to HiveManager
If CAPWAP (Control and Provisioning of Wireless Access Points) clients are in the same layer 2 broadcast domain as
the CAPWAP server—as they are in the previous example—the clients broadcast CAPWAP Discovery Request messages
to discover and establish a secure connection with the server automatically. There is no need for any extra
configuration on your part.
However, if the CAPWAP clients and server are in different subnets, the clients cannot discover the server by
broadcasting CAPWAP Discovery Request messages. In this case, you can use one of the following methods to
configure HiveAPs with the HiveManager IP address or domain name, or configure them so that they can learn it
through DHCP or DNS. When HiveAPs have the HiveManager IP address or domain name, they can then send unicast
CAPWAP Discovery Request messages to it.
• Log in to the CLI on the HiveAP and enter the IP address or domain name of the CAPWAP server:
capwap client server name <string>
• Configure the DHCP server to supply the HiveManager domain name as DHCP option 225 or its IP address as
option 226 in its DHCPOFFER. (If you use a domain name, the authoritative DNS server for that domain must
also be configured with an A record that maps the domain name to the HiveManager IP address.) A HiveAP
requests options 225 and 226 by default when it broadcasts DHCPDISCOVER and DHCPREQUEST messages.
• If HiveManager continues to use its default domain name ("hivemanager") plus the name of the local domain
to which it and the HiveAPs belong, configure an authoritative DNS server with an A record that resolves
"hivemanager.<local_domain>" to an IP address. If a HiveAP does not have an IP address or domain name
configured for the CAPWAP server and does not receive an address or domain name returned in a DHCP
option, then it tries to resolve the domain name to an IP address.
If you are using HiveManager Online instead of a physical HiveManager appliance or HiveManager Virtual Appliance
and the HiveAPs go online for the first time without any specific CAPWAP server configuration entered manually or
received as a DHCP option, they progress through the following cycle of CAPWAP connection attempts. First, they
try to connect with a CAPWAP server at hivemanager.<local_domain>. If that is unsuccessful, they next try to elicit
a response from the broadcast of CAPWAP Discovery messages on their local subnet. If neither of these efforts
produce a response, they try to connect to HiveManager Online, first using the CAPWAP UDP port 12222 and then
using CAPWAP over the HTTP TCP port of 80. This cycle is shown in
Figure 6 on page 134 .
Note: If you need to change the DHCP option number (perhaps because another custom option with that
number is already in use on the DHCP server), enter this command with a different option number:
interface mgt0 dhcp client option custom hivemanager <number> { ip | string }