Aerohive HiveAP 100 Series Quick Start

Aerohive QuickStart
for the HiveAP 100 Series
This QuickStart guide explains how to set up a HiveAP 100 series device as a managed HiveAP and
how to mount it on a ceiling or wall.
Connect a standard Ethernet
cable with RJ-45 connectors
from ETH0 on the HiveAP to
a switch.
1
DHCP
Server
Switch
Eth0
Some other network devices (They
Ethernet
might all be incorporated in the same
Cable
device, such as a router or firewall.)
2
If the switch provides
PoE (Power-over-
Ethernet), cabling the
HiveAP to the switch
will cause the HiveAP
to power on in a few
seconds.
Connecting to HiveManager
3
Cable the HiveAP to an Ethernet network—a HiveAP connected directly to the network like
this is called a portal—or place it within radio range of a portal so that it forms a wireless
link through the portal to the wired network. This kind of HiveAP is called a mesh point. By
default, a HiveAP acts as a DHCP client and gets its network settings automatically from a
DHCP server. (You can also configure it with static network settings through the CLI. See the
next section, "Using the Virtual Access Console".)
CAPWAP (Control and Provisioning of Wireless Access Points) is a protocol that access points
use to contact a management device and communicate with it. After getting its network
settings through DHCP, the HiveAP then acts as a CAPWAP client and sends CAPWAP Discovery
messages until HiveManager, acting as the CAPWAP server, responds. A mesh point initially
forms a hive with its portal using a default hive called hive0. Through this link, the mesh
point can reach the network and get its network settings from the DHCP server. Then it can
form a CAPWAP connection with HiveManager. (To add mesh points after changing the hive
name, first connect them to the wired network. Next, push the configuration with the new
hive name and password to them from HiveManager. Finally, deploy them as mesh points.)
When a HiveAP goes online for the first time without any specific CAPWAP server
configuration entered manually or received as a DHCP option, it progresses through the cycle
of CAPWAP connection attempts shown below.
a
The HiveAP tries to
connect to HiveManager
using the default domain
HiveManager
name hivemanager.<local_
or
domain>, where "<local_
HiveManager Virtual
domain>" is the domain
Appliance
name that a DHCP server
supplied to the HiveAP.
If a DNS server has been
configured with an A
record to resolve that
domain name to an IP
address, the HiveAP
and HiveManager then
form a secure CAPWAP
connection.
d HiveManager
If the HiveAP cannot
Online
make a CAPWAP
connection to HiveManager
Online using UDP port 12222,
it tries to reach it by using TCP port 80:
contact HiveManager Online at staging.
staging.aerohive.com:80. If that proves
aerohive.com:12222. If the staging server
unsuccessful, the HiveAP returns to its
has a serial number or MAC address for
initial search through a DNS lookup and
that HiveAP, it responds and they form a
repeats the cycle.
P/N 330026-03 Rev. A
If the HiveAP forms a CAPWAP connection with the staging server and its serial number or MAC
address has been assigned to a VHM (virtual HiveManager) and that VHM has already been
created, the staging server automatically redirects the CAPWAP connection to that VHM. The
staging server does this by sending the HiveAP the VHM domain name as its new CAPWAP server.
If the HiveAP is currently using HTTP, the staging server also sends it the configuration needed
to continue using HTTP. Finally, if the HiveAP is accessing the network through an HTTP proxy
server, the staging server also saves those settings on the HiveAP so that it can reach the VHM
using HTTP through the HTTP proxy server.
If the serial number or MAC address is in the staging server but the VHM has not yet been
created, then the HiveAP remains connected to the staging server. The VHM admin must
manually reassign it to a VHM later after the VHM has been created.
Internet
If the staging server does not have the serial number or MAC address of the HiveAP, then an
ACL (access control list) on the staging server ignores the CAPWAP connection attempt, and the
HiveAP repeats the cycle shown above.
Firewall
Using the Virtual Access Console
The virtual access console is a way of accessing the CLI on a HiveAP wirelessly through a special
If the switch does not SSID that the HiveAP, by default, automatically activates for administrative access when it has
provide PoE, use the no configuration and cannot reach its default gateway. As explained in the previous section,
AC/DC power adaptor after connecting a HiveAP to the network and powering it on, it acts as a DHCP client and tries
(available as an to get its network settings automatically from a DHCP server in VLAN 1. However, if there is no
accessory) to connect DHCP server in that VLAN, if the native VLAN for the network segment is not 1, or if you just
the HiveAP to a 100- want to assign the HiveAP a static IP address, then you can access the CLI through the virtual
240 AC power source. access console SSID and define the network settings yourself.
The default virtual access console SSID name is "<hiveap_hostname>_ac". The default host
name of a HiveAP consists of "AH-" plus the last six digits of its MAC address; for example,
AH-123456. In this case, the name of the default virtual access console SSID would be "AH-
123456_ac". By default, this SSID uses aerohive as the PSK (preshared key) for authenticating
user access. To access the virtual access console, do the following:
4
Using your wireless client,
scan for wireless networks.
If you are within range, an
SSID such as "AH-123456_ac"
appears.
Select the SSID, and when
prompted to enter a
network key, type aerohive,
and then click Connect.
5
Check the IP address of the
default gateway that the
b
DHCP server on the HiveAP
assigned your client. Then
If the DNS server cannot
make an SSH or
resolve the domain
name to an IP address, Telnet connection
the HiveAP broadcasts
to the HiveAP at that IP
CAPWAP Discovery
address. When prompted to
messages on its local
enter your credentials, enter
subnet for a CAPWAP
the default Aerohive login name
server (HiveManager).
(admin) and password (aerohive).
If HiveManager is on
the local network
and responds, they
form a secure CAPWAP
connection.
c C:\>ipconfig
If the first two
Windows IP Configuration
searches for a local
HiveManager produce
Ethernet adapter Wireless
Network Connection:
no results, the HiveAP
broadens its search and tries to
Connection-specific DNS Suffix
IP Address. . . . . . : 1.1.1.2
Subnet Mask . . . . . : 255.255.255.0
Default Gateway . . . : 1.1.1.1
C:\>telnet 1.1.1.1
secure CAPWAP connection.
Beacons
Beacons
Wireless
Client
. :
6
After logging in to the virtual access console, you can view the status of various
functions and make configuration changes. Here are some commonly used commands.
Use these commands: To do the following:
show interface
Check the status of both wired and
wireless interfaces
show interface mgt0
See the network settings (IP address,
netmask, default gateway) and VLAN ID
of the mgt0 interface
no interface mgt0 dhcp client
Disable the DHCP client
interface mgt0 ip <ip_addr>
Set the IP address and netmask of the
<netmask>
mgt0 interface
interface mgt0 native-vlan <id>
Set the native (untagged) VLAN that the
switch infrastructure in the surrounding
wired and wireless network uses
show capwap client
See CAPWAP client settings and status
capwap client server name
Set the IP address or domain name of the
<string>
CAPWAP server (HiveManager)
capwap client vhm-name <string>
Set the VHM (virtual HiveManager) to
which the client belongs
show hive
See the hive name
show hive <string> neighbor
Check for any neighboring hive members
hive <string> ...
Create a hive and set its parameters
show ssid
See a list of all SSID names
ssid <string> ...
Configure an SSID
interface { wifi0 | wifi1 } ssid
Bind an SSID to a wireless interface in
<string>
access mode
To see a list of commands, and their accompanying CLI Help, type a question mark ( ? ).
For example, to see all the show commands, enter show ?
If you want to find a command that uses a particular character or string of characters,
you can do a search using the following command: show cmds | include
<string>, where <string> is the word or string of characters you want to find.
Device- and platform-specific CLI reference guides are available online. (To learn how
to access them, see "Where to go for more information" elsewhere in this document.)
Status LEDs
The status indicator has been incorporated into the Aerohive logo on the top of the
HiveAP 110 and 120. It is illuminated by various colors to indicate different states of
activity. The meanings of the colors are explained below.
• Dark: There is no power or the status indicator is disabled.
• Blue: (solid) The device is booting up or there is no backhaul link; (flashing) the
device is shutting down
• Green: The default route is through the backhaul Ethernet interface, but not all
conditions for normal operations (white) have been met.
• Yellow: The default route is through a backhaul wifi interface, but not all
conditions for normal operations (white) have been met.
• White: The device is powered on and the firmware is operating normally; that is,
a wireless interface in access mode is up, a wired or wireless backhaul link is up,
and the HiveAP has a CAPWAP connection to HiveManager.
• Purple: A new image is being loaded from HiveManager or a management AP.
• Orange: An alarm indicating a firmware or hardware issue has occurred.
For locations where the status indicator might be a distraction or attract unwanted
attention, you can adjust its brightness level from bright (the default) to soft to dim.
You can even turn it off completely. In HiveManager, choose the brightness level that
you want from the LED Brightness drop-down list on the Configuration > Management
Services > Management Options page. Through the CLI, enter
. The four settings are shown below.
brightness { soft | dim | off }
Bright Soft Dim
[ no ] system led
Off