Aerohive HiveAP 320 Quick Start Manual

Aerohive QuickStart
for the HiveAP 320
This QuickStart guide explains how to set up a HiveAP 320 as either a managed HiveAP or as a
management AP, and how to mount it on a ceiling or wall.
Connect a standard Ethernet
cable with RJ-45 connectors
from ETH0 on the HiveAP 320
to a switch.
1
DHCP
Server
Switch
Eth0
Ethernet Some other network devices (They
Cable might all be incorporated in the same
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
a
connect to HiveManager
using the default domain
HiveManager
name "hivemanager.
or
<local_domain>:
HiveManager Virtual
12222", where
Appliance
<local_domain> is the
domain name that a
DHCP server supplied
to the HiveAP and
12222 is the UDP port
number. If a DNS server
has been configured
to resolve that domain
name to an IP address, the
HiveAP and HiveManager
HiveManager Online
then form a secure CAPWAP
connection on port 12222.
If the HiveAP cannot make a
CAPWAP connection to HiveManager
on port 12222, it tries to reach it by
using TCP port 80: hivemanager.<local_
secure CAPWAP connection. If the HiveAP cannot
domain>:80.
c
make a CAPWAP connection to HiveManager Online
on UDP port 12222, it tries to reach it on TCP port 80. If
that proves unsuccessful, the HiveAP returns to its initial
search through a DNS lookup and repeats the cycle.
P/N 330024-04 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 previously created VHM, to a physical HiveManager appliance,
or to a HiveManager Virtual Appliance, the staging server automatically redirects the CAPWAP
connection to that HiveManager instance. The staging server does this by sending the HiveAP
the HiveManager domain name or IP address as its new CAPWAP server. If the HiveAP is currently
using HTTP and it will be redirected to a HiveManager Online VHM, the staging server also
sends it the configuration needed to continue using HTTP. Similarly, if the HiveAP is accessing
the network through an HTTP proxy server, the staging server also saves those settings on the
HiveAP so it can reach the HiveManager Online VHM using HTTP through the HTTP proxy server.
If the staging server must redirect the HiveAP to a standalone HiveManager appliance or
HiveManager Virtual Appliance, then you must configure the connection settings on the staging
Internet
server that you want it to push to the HiveAP to make that connection. The HiveAP first uses
whatever settings are configured on it to reach the staging server, which might be on the other
side of an HTTP proxy server or firewall that only permits outbound HTTP traffic. Then the
staging server might supply it with different settings so that the HiveAP can reach a standalone
Firewall
HiveManager instance, which might be on the same side of the HTTP proxy server or firewall as
the HiveAP and therefore require different connection parameters.
If the HiveAP serial number or MAC address is in the staging server but the VHM has not yet been
created or the connection settings of the standalone HiveManager has not yet been configured
on the staging server, then the HiveAP remains in the staging server. The HiveManager admin
must manually reassign it to the appropriate HiveManager later.
If the staging server does not have the HiveAP serial number or MAC address, then the ACL
on the staging server ignores the CAPWAP connection attempts, and the HiveAP repeats the
connection cycle shown above.
If the switch does not
provide PoE, use the
AC/DC power adaptor
Using the Virtual Access Console
(available as an
accessory) to connect
As explained in the previous section, after connecting a HiveAP to the network and powering
the HiveAP to a 100-
it on, it acts as a DHCP client and tries to get its network settings automatically from a DHCP
240 AC power source.
server in VLAN 1. However, if there is no DHCP server in that VLAN, if the native VLAN for the
network segment is not 1, or if you just want to assign it a static IP address, then you need to
access the CLI and define the network settings yourself.
One approach is to use a console cable, which is available from Aerohive as an accessory.
Another is to use the virtual access console. This is a way of accessing the CLI on a HiveAP
wirelessly through a special SSID that the HiveAP, by default, automatically activates for
administrative access when it has no configuration and cannot reach its default gateway.
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 it, and when
prompted to enter a
network key, type aerohive
and then click Connect.
(b) If the DNS server cannot
b
resolve the domain
name to an IP address,
5
Check the IP address of the
the HiveAP broadcasts
default gateway that the
CAPWAP Discovery
DHCP server on the HiveAP
messages on its local
subnet. If HiveManager assigned your client. Then
is on the local network make an SSH or
and responds, they
Telnet connection
form a secure CAPWAP
to the HiveAP at that IP
connection.
address. When prompted to
enter your credentials, enter
(c) If the first two
the default Aerohive login name
searches for a local
(admin) and password (aerohive).
HiveManager produce no
results, the HiveAP tries
to contact HiveManager
Online at staging.aerohive.
C:\>ipconfig
com:12222. If the staging server
has a serial number or MAC address Windows IP Configuration
for that HiveAP in its ACL (access
Ethernet adapter Wireless
control list), it responds and they form a
Network Connection:
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
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 five status LEDs on the top of the HiveAP 320 indicate various states of activity
through their color (dark, green, amber, and red) and illumination patterns (steady
glow or pulsing). The meanings of the various color + illumination patterns for each
LED are explained below.
Power
• Dark: No power
• Steady green: Powered on and the firmware is running normally
• Pulsing green: Firmware is booting up
• Steady amber: Firmware is being updated
• Pulsing amber: Alarm indicating a firmware issue has occurred
• Steady red: Alarm indicating a hardware issue has occurred
ETH0 and ETH1
• Dark: Ethernet link is down or disabled
• Steady green: 1000 Mbps Ethernet link is up but inactive
• Pulsing green: 1000 Mbps Ethernet link is up and active
• Steady amber: 10/100 Mbps Ethernet link is up but inactive
• Pulsing amber: 10/100 Mbps Ethernet link is up and active
WLAN 0 and WLAN 1
• Dark: Wireless interface is disabled
• Steady green: Wireless interface is in access mode but inactive
• Pulsing green: Wireless interface is in access mode and active
• Steady amber: Wireless interface is in backhaul mode but inactive
• Pulsing amber: Wireless interface is in backhaul mode and is connected with other
hive members
• Alternating green and amber: Wireless interface is in backhaul mode and is
searching for other hive members