Aerohive AP20AG Deployment Guide

Aerohive
Deployment Guide

Copyright Notice

Copyright © 2007 Aerohive Networks, Inc. All rights reserved.
Aerohive Networks, the Aerohive Networks logo, HiveOS, HiveAP, and HiveManager are trademarks of Aerohive

Networks, Inc. All other trademarks and registered trademarks are the property of their respective companies.
Information in this document is subject to change without notice. No part of this document may be reproduced or

transmitted in any form or by any means, electronic or mechanical, for any purpose, without receiving written
permission from:

Aerohive Networks, Inc.
2045 Martin Avenue, Suite 206
Santa Clara, CA 95050

P/N 330002-01, Rev. A

HiveAP Compliance Information

Federal Communication Commission Interference
Statement

This equipment has been tested and found to comply with the limits for
a Class B digital device, pursuant to Part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates,
uses and can radiate radio frequency energy and, if not installed and
used in accordance with the instructions, may cause harmful
interference to radio communications. However, there is no guarantee
that interference will not occur in a particular installation. If this
equipment does cause harmful interference to radio or television
reception, which can be determined by turning the equipment off and
on, the user is encouraged to try to correct the interference by one of
the following measures:

• Reorient or relocate the receiving antenna

• Increase the separation between the equipment and receiver

• Connect the equipment into an outlet on a circuit different from

that to which the receiver is connected

• Consult the dealer or an experienced radio/TV technician for help

FCC Caution: Any changes or modifications not expressly approved by
the party responsible for compliance could void the user's authority to
operate this equipment. This device complies with Part 15 of the FCC
Rules. Operation is subject to the following two conditions: (1) This
device may not cause harmful interference, and (2) this device must
accept any interference received, including interference that may
cause undesired operation.

Important: FCC Radiation Exposure Statement

This equipment complies with FCC radiation exposure limits set forth
for an uncontrolled environment. This equipment should be installed
and operated with a minimum distance of 20 centimeters (8 inches)
between the radiator and your body. This transmitter must not be co­located or operating in conjunction with any other antenna or
transmitter.

Wireless 5 GHz Band Statements

High power radars are allocated as primary users (meaning they have
priority) of the 5250-5350 MHz and 5650-5850 MHz bands. These radars
could cause interference and/or damage to the HiveAP when used in
Canada.

The term "IC" before the radio certification number only signifies that
Industry Canada technical specifications were met.

Industry Canada - Class B

This digital apparatus does not exceed the Class B limits for radio noise
emissions from digital apparatus as set out in the interference-causing
equipment standard entitled "Digital Apparatus," ICES-003 of Industry
Canada.

Cet appareil numérique respecte les limites de bruits radioélectriques
applicables aux appareils numériques de Classe B prescrites dans la
norme sur le matérial brouilleur: "Appareils Numériques," NMB-003
édictée par l'Industrie.

EC Conformance Declaration

Marking by the above symbol indicates compliance with the Essential
Requirements of the R&TTE Directive of the European Union (1999/5/
EC). This equipment meets the following conformance standards:

• EN 60950-1 (IEC 60950-1) - Product Safety

• EN 301 893 - Technical requirements for 5 GHz radio equipment

• EN 300 328 - Technical requirements for 2.4 GHz radio equipment

• EN 301 489-1 / EN 301 489-17 - EMC requirements for radio

equipment

Countries of Operation and Conditions of Use in the
European Community

This device is intended to be operated in all countries of the European
Community. Requirements for indoor vs. outdoor operation, license
requirements and allowed channels of operation apply in some
countries as described below.

Note: The user must use the configuration utility provided with this
product to ensure the channels of operation are in conformance with
the spectrum usage rules for European Community countries as
described below.

• This device requires that the user or installer properly enter the
current country of operation in the command line interface as
described in the user guide, before operating this device.

• This device will automatically limit the allowable channels
determined by the current country of operation. Incorrectly
entering the country of operation may result in illegal operation
and may cause harmful interference to other systems. The user is
obligated to ensure the device is operating according to the
channel limitations, indoor/outdoor restrictions and license
requirements for each European Community country as described
in this document.

• This device employs a radar detection feature required for
European Community operation in the 5 GHz band. This feature is
automatically enabled when the country of operation is correctly
configured for any European Community country. The presence of
nearby radar operation may result in temporary interruption of
operation of this device. The radar detection feature will
automatically restart operation on a channel free of radar.

• The 5 GHz Turbo Mode feature is not allowed for operation in any
European Community country. The current setting for this feature
is found in the 5 GHz 802.11a Radio Settings Window as described
in the user guide.

• The 5 GHz radio's Auto Channel Select setting described in the
user guide must always remain enabled to ensure that automatic 5
GHz channel selection complies with European requirements. The
current setting for this feature is found in the 5 GHz 802.11a Radio
Settings Window as described in the user guide.

• This device is restricted to indoor use when operated in the
European Community using the 5.15 - 5.35 GHz band: Channels 36,
40, 44, 48, 52, 56, 60, 64. See table below for allowed 5 GHz
channels by country.

• This device may be operated indoors or outdoors in all countries of
the European Community using the 2.4 GHz band: Channels 1 - 13,
except where noted below.

Deployment Guide 3

HiveAP Compliance Information

– In Italy the end-user must apply for a license from the national

spectrum authority to operate this device outdoors.

– In Belgium outdoor operation is only permitted using the 2.46 -

2.4835 GHz band: Channel 13.

– In France outdoor operation is only permitted using the 2.4 -

2.454 GHz band: Channels 1 - 7.

Operation Using 5 GHz Channels in the European
Community

The user/installer must use the provided configuration utility to check
the current channel of operation and make necessary configuration
changes to ensure operation occurs in conformance with European
National spectrum usage laws as described below and elsewhere in this
document.

Allowed 5 GHz Channels in Each European Community Country
Allowed

Frequency Bands

5.15 – 5.25 GHz*36, 40, 44, 48Austria, Belgium

5.15 – 5.35 GHz*36, 40, 44, 48, 52, 56,

5.15 – 5.35 GHz*
and 5.470 – 5.725
GHz

5 GHz Operation
Not Allowed

* Outdoor operation is not allowed using 5.15 – 5.35 GHz bands
(Channels 36 – 64).

Allowed Channel
Numbers

60, 64
36, 40, 44, 48, 52, 56,

60, 64, 100, 104, 108,
112, 116, 120, 124, 128,
132, 136, 140

NoneGreece

Countries

France, Switzerland,
Liechtenstein

Denmark, Finland,
Germany, Iceland,
Ireland, Italy,
Luxembourg,
Netherlands, Norway,
Portugal, Spain,
Sweden, U.K.

Declaration of Conformity in Languages of the
European Community

EnglishHereby, Edgecore, declares that this Radio LAN

FinnishValmistaja Edgecore vakuuttaa täten että Radio LAN

DutchHierbij verklaart Edgecore dat het toestel Radio

FrenchPar la présente Edgecore déclare que l'appareil

SwedishHärmed intygar Edgecore att denna Radio LAN

DanishUndertegnede Edgecore erklærer herved, at

device is in compliance with the essential
requirements and other relevant provisions of
Directive 1999/5/EC.

device tyyppinen laite on direktiivin 1999/5/EY
oleellisten vaatimusten ja sitä koskevien direktiivin
muiden ehtojen mukainen.

LAN device in overeenstemming is met de
essentiële eisen en de andere relevante bepalingen
van richtlijn 1999/5/EG.

Bij deze Edgecore dat deze Radio LAN device
voldoet aan de essentiële eisen en aan de overige
relevante bepalingen van Richtlijn 1999/5/EC.

Radio LAN device est conforme aux exigences
essentielles et aux autres dispositions pertinentes
de la directive 1999/5/CE.

device står I överensstämmelse med de väsentliga
egenskapskrav och övriga relevanta bestämmelser
som framgår av direktiv 1999/5/EG.

følgende udstyr Radio LAN device overholder de
væsentlige krav og øvrige relevante krav i direktiv
1999/5/EF.

GermanHiermit erklärt Edgecore, dass sich dieser/diese/

Greek

ItalianCon la presente Edgecore dichiara che questo Radio

SpanishPor medio de la presente Manufacturer declara que

PortugueseManufacturer declara que este Radio LAN device

dieses Radio LAN device in Übereinstimmung mit
den grundlegenden Anforderungen und den anderen
relevanten Vorschriften der Richtlinie 1999/5/EG
befindet". (BMWi)

Hiermit erklärt Edgecore die Übereinstimmung des
Gerätes Radio LAN device mit den grundlegenden
Anforderungen und den anderen relevanten
Festlegungen der Richtlinie 1999/5/EG. (Wien)

LAN device è conforme ai requisiti essenziali ed alle
altre disposizioni pertinenti stabilite dalla direttiva
1999/5/CE.

el Radio LAN device cumple con los requisitos
esenciales y cualesquiera otras disposiciones
aplicables o exigibles de la Directiva 1999/5/CE.

está conforme com os requisitos essenciais e outras
disposições da Directiva 1999/5/CE.

Safety Compliance

Power Cord Safety

Please read the following safety information carefully before installing
the HiveAP.

Warning: Installation and removal of the unit must be carried out by
qualified personnel only.

• The unit must be connected to an earthed (grounded) outlet to
comply with international safety standards.

• Do not connect the unit to an A.C. outlet (power supply) without
an earth (ground) connection.

• The appliance coupler (the connector to the unit and not the wall
plug) must have a configuration for mating with an EN 60320/IEC
320 appliance inlet.

• The socket outlet must be near to the unit and easily accessible.
You can only remove power from the unit by disconnecting the
power cord from the outlet.

• This unit operates under SELV (Safety Extra Low Voltage)
conditions according to IEC 60950. The conditions are only
maintained if the equipment to which it is connected also
operates under SELV conditions.

• The PoE (Power over Ethernet), which is to be interconnected with
other equipment that must be contained within the same building
including the interconnected equipment's associated LAN
connections.

France and Peru only:

This unit cannot be powered from IT* supplies. If your supplies are of IT
type, this unit must be powered by 230 V (2P+T) via an isolation
transformer ratio 1:1, with the secondary connection point labelled
Neutral, connected directly to earth (ground).

* Impédance à la terre

Important! Before making connections, make sure you have the correct
cord set. Check it (read the label on the cable) against the following:

4 Aerohive

HIVEAP COMPLIANCE INFORMATION

Power Cord Set

U.S.A.
and Canada

DenmarkThe supply plug must comply with Section 107-2-D1,

SwitzerlandThe supply plug must comply with SEV/ASE 1011.
U.K.The supply plug must comply with BS1363 (3-pin 13 A)

EuropeThe supply plug must comply with CEE7/7

Veuillez lire à fond l'information de la sécurité suivante avant d'installer
le HiveAP.

Avertissement: L'installation et la dépose de ce groupe doivent être
confiés à un personnel qualifié.

• Ne branchez pas votre appareil sur une prise secteur (alimentation
électrique) lorsqu'il n'y a pas de connexion de mise à la terre (mise
à la masse).

• Vous devez raccorder ce groupe à une sortie mise à la terre (mise
à la masse) afin de respecter les normes internationales de
sécurité.

• Le coupleur d'appareil (le connecteur du groupe et non pas la prise

murale) doit respecter une configuration qui permet un
branchement sur une entrée d'appareil EN 60320/IEC 320.

• La prise secteur doit se trouver à proximité de l'appareil et son
accès doit être facile. Vous ne pouvez mettre l'appareil hors
circuit qu'en débranchant son cordon électrique au niveau de
cette prise.

• L'appareil fonctionne à une tension extrêmement basse de
sécurité qui est conforme à la norme IEC 60950. Ces conditions ne
sont maintenues que si l'équipement auquel il est raccordé
fonctionne dans les mêmes conditions.

France et Pérou uniquement:

Ce groupe ne peut pas être alimenté par un dispositif à impédance à la
terre. Si vos alimentations sont du type impédance à la terre, ce groupe
doit être alimenté par une tension de 230 V (2 P+T) par le biais d'un
transformateur d'isolement à rapport 1:1, avec un point secondaire de
connexion portant l'appellation Neutre et avec raccordement direct à la
terre (masse).

Cordon électrique - Il doit être agréé dans le pays d'utilisation

Etats-Unis
et Canada

The cord set must be UL-approved and CSA certified.
Minimum specifications for the flexible cord:

- No. 18 AWG not longer than 2 meters, or 16 AWG

- Type SV or SJ

- 3-conductor
The cord set must have a rated current capacity of at

least 10 A.
The attachment plug must be an earth-grounding

type with NEMA 5-15P (15 A, 125 V) or NEMA 6-15 (15
A, 250 V) configuration.

Standard DK2-1a or DK2-5a.

and be fitted with a 5 A fuse that complies with
BS1362.

The mains cord must be <HAR> or <BASEC> marked and
be of type HO3VVF3GO.75 (minimum).

("SCHUKO").
The mains cord must be <HAR> or <BASEC> marked and

be of type HO3VVF3GO.75 (minimum).
IEC-320 receptacle.

Le cordon doit avoir reçu l'homologation des UL et un
certificat de la CSA.

Les spécifications minimales pour un cable flexible

- AWG No. 18, ou AWG No. 16 pour un cable de
longueur inférieure à 2 mètres.

- Type SV ou SJ

- 3 conducteurs

Le cordon doit être en mesure d'acheminer un
courant nominal d'au moins 10 A.

La prise femelle de branchement doit être du type à
mise à la terre (mise à la masse) et respecter la
configuration NEMA 5-15P (15 A, 125 V) ou NEMA 6­15P (15 A, 250 V).

DanemarkLa prise mâle d'alimentation doit respecter la section

SuisseLa prise mâle d'alimentation doit respecter la norme

EuropeLa prise secteur doit être conforme aux normes CEE

Bitte unbedingt vor dem Einbauen des HiveAP die folgenden
Sicherheitsanweisungen durchlesen.

Warnung: Die Installation und der Ausbau des Geräts darf nur durch
Fachpersonal erfolgen.

• Das Gerät sollte nicht an eine ungeerdete Wechselstromsteckdose
angeschlossen werden.

• Das Gerät muß an eine geerdete Steckdose angeschlossen werden,
welche die internationalen Sicherheitsnormen erfüllt.

• Der Gerätestecker (der Anschluß an das Gerät, nicht der
Wandsteckdosenstecker) muß einen gemäß EN 60320/IEC 320
konfigurierten Geräteeingang haben.

• Die Netzsteckdose muß in der Nähe des Geräts und leicht
zugänglich sein. Die Stromversorgung des Geräts kann nur durch
Herausziehen des Gerätenetzkabels aus der Netzsteckdose
unterbrochen werden.

• Der Betrieb dieses Geräts erfolgt unter den SELV-Bedingungen
(Sicherheitskleinstspannung) gemäß IEC 60950. Diese Bedingungen
sind nur gegeben, wenn auch die an das Gerät angeschlossenen
Geräte unter SELV-Bedingungen betrieben werden.

Stromkabel. Dies muss von dem Land, in dem es benutzt wird
geprüft werden:

U.S.A.
und

Kanada

DanemarkDieser Stromstecker muß die ebene 107-2-D1, der

SchweizDieser Stromstecker muß die SEV/ASE

EuropeEurope Das Netzkabel muß vom Typ HO3VVF3GO.75

107-2 D1 de la norme DK2 1a ou DK2 5a.

SEV/ASE 1011.

7/7 ("SCHUKO").
LE cordon secteur doit porter la mention <HAR> ou

<BASEC> et doit être de type HO3VVF3GO.75
(minimum).

Der Cord muß das UL gepruft und war das CSA
beglaubigt.

Das Minimum spezifikation fur der Cord sind:

- Nu. 18 AWG - nicht mehr als 2 meter, oder 16 AWG.

- Der typ SV oder SJ

- 3-Leiter
Der Cord muß haben eine strombelastbarkeit aus

wenigstens 10 A.
Dieser Stromstecker muß hat einer erdschluss mit der

typ NEMA 5-15P (15A, 125V) oder NEMA 6-15P (15A,
250V) konfiguration.

standard DK2-1a oder DK2-5a Bestimmungen
einhalten.

1011Bestimmungen einhalten.

(Mindestanforderung) sein und die Aufschrift <HAR>
oder <BASEC> tragen.

Der Netzstecker muß die Norm CEE 7/7 erfüllen
("SCHUKO").

Deployment Guide 5

HiveAP Compliance Information

6 Aerohive

Contents

Chapter 1 The HiveAP Platform................................................................9

Product overview...........................................................................................10

Ethernet and Console Ports......................................................................................12

Status LEDs.........................................................................................................13

Antennas............................................................................................................14

Mounting the HiveAP.......................................................................................15

Device, Power, and Environmental Specifications.....................................................16

Chapter 2 The HiveManager Platform.......................................................17

Product overview...........................................................................................18

Ethernet and Console Ports......................................................................................19

Status LEDs.........................................................................................................20

Rack Mounting the HiveManager..........................................................................21

Device, Power, and Environmental Specifications.....................................................22

Chapter 3 Using HiveManager.................................................................23

Installing and Connecting to the HiveManager GUI....................................................25

Introduction the the HiveManager GUI..................................................................28

Detaching Windows................................................................................................29

Cloning Configurations............................................................................................29

Sorting Displayed Data............................................................................................30

Multiselecting......................................................................................................30

HiveManager Configuration Workflow...................................................................31

Updating HiveAP Firmware................................................................................32

Updating Software on the HiveManager.................................................................33

Chapter 4 HiveManager Examples............................................................35

Example 1: Mapping Locations and Installing HiveAPs................................................37

Setting Up Topology Maps........................................................................................37

Preparing the HiveAPs............................................................................................40

Example 2: Defining Network Objects...................................................................42

Example 3: Defining User Profiles and QoS Settings...................................................45

Example 4: Setting SSID Profiles..........................................................................49

Example 5: Setting Management Service Parameters.................................................52

Deployment Guide 7

Contents

Example 6: Setting AAA RADIUS Settings................................................................55

Example 7: Creating Two Device Groups................................................................57

Example 8: Creating Three Hive Profiles................................................................60

Example 9: Assigning HiveAPs to a Device Group, Radio Profile,

Hive Profile, and Topology Map...........................................................................61

Chapter 5 HiveOS................................................................................65

Common Default Settings and Commands...............................................................66

Configuration Overview....................................................................................67

Device-Level Configurations.....................................................................................67

Policy-Level Configurations......................................................................................68

Chapter 6 Deployment Examples (CLI)......................................................69

Example 1: Deploying a Single HiveAP...................................................................70

Example 2: Deploying a Hive..............................................................................73

Example 3: Using IEEE 802.1X Authentication..........................................................78

Example 4: Applying QoS..................................................................................81

CLI Commands for Examples..............................................................................87

Commands for Example 1........................................................................................87

Commands for Example 2........................................................................................87

Commands for Example 3........................................................................................88

Commands for Example 4........................................................................................89

8 Aerohive

Chapter 1The HiveAP Platform

The Aerohive HiveAP 20 ag is a new generation wireless access point. HiveAPs offer unique abilities to self-organize
and coordinate with each other, creating a distributed-control WLAN solution that offers greater mobility, security,
quality of service, and radio control.

This guide combines product information with installation instructions. This chapter covers the following topics:

• "Product overview" on page10

• "Ethernet and Console Ports" on page12

• "Status LEDs" on page13

• "Antennas" on page14

• "Mounting the HiveAP" on page15

• "Device, Power, and Environmental Specifications" on page16

Deployment Guide 9

Chapter 1 The HiveAP Platform

PRODUCTOVERVIEW

The HiveAP is a multi-channel wireless AP (access point). It is compatible with IEEE 802.11b/g (2.4 GHz) and IEEE

802.11a (5 GHz) standards and supports a variety of Wi-Fi (wireless fidelity) security protocols, including WPA (Wi-Fi
Protected Access) and WPA2.

You can see the hardware components on the HiveAP in Figure1. Each component is described in Table1.

Figure 1 HiveAP Hardware Components

Fixed Dual-Band Antennas

Status LEDs

RP-SMA

Connector for

802.11a

Radio Antenna

Connector

Power

Mounting

Screw

10/100 Mbps

Power-over-

Ethernet Port

For Detachable Single-Band Antennas

Reset

Button

Console

Port

Device

Lock Slot

RP-SMA

Connector for

802.11b/g

Radio Antenna

Table 1 HiveAP Component Descriptions

Component Description

Fixed Dual-Band AntennasThe two fixed omnidirectional dipole antennas can operate at either of

the two radio frequencies: 2.4 GHz (for IEEE 802.11b/g) and 5 GHz (for
IEEE 802.11a). For details, see "Antennas" on page14.

Status LEDsThe status LEDs convey operational states for system power, and the LAN,

Access, and Mesh interfaces. For details, see "Status LEDs" on page13.

802.11a RP-SMA Connector(For future use) You can connect a detachable single-band antenna to the
male 802.11a RP-SMA (reverse polarity-subminiature version A)
connector. Note that doing so disables the adjacent fixed antenna.

10 Aerohive

PRODUCTOVERVIEW

Component Description

Power ConnectorThe 48-volt DC power connector (0.38 amps) is one of two methods

through which you can power a HiveAP. To connect it to a 100 – 240-volt
AC power source, use the AC/DC power adaptor that ships with the
product as an option. Because that the HiveAP does not have an on/off
switch, connecting it to a power source automatically powers on the
device.

Mounting ScrewTo mount the HiveAP on a surface, attach the mounting plate that ships

with the product, and then attach the device to the plate by tightening
the mounting screw. For details, see "Mounting the HiveAP" on page15.

10/100 Mbps PoE PortThe 10/100-Mbps Ethernet port supports IEEE 802.3af PoE (Power over

Ethernet) and receives RJ-45 connectors. The HiveAP can receive its
power through an Ethernet connection to power sourcing equipment
(PSE) that is 802.3af-compatible. (If you connect the HiveAP to a power
source through the power connector and PoE port simultaneously, the
device draws power through the power connector and automatically
disables PoE.)

The HiveAP can also connect to the wired network or to a wired device
(such as a security camera) through this port. It is compatible with 10/
100Base-T/TX and automatically negotiates half- and full-duplex
connections with the connecting device. It is autosensing and adjusts to
straight-through and cross-over Ethernet cables automatically. It also
automatically adjusts for 802.3af Alternative A and B methods of PoE.

Reset ButtonThe reset button allows you to reboot the device or reset the HiveAP to

its factory default settings. Insert a paper clip, or something similar, into
the Reset pinhole and press the reset button. To reboot the device, hold
the button down between 1 and 5 seconds. To return the configuration to
the factory default settings, hold it down for at least 5 seconds. After
releasing the button, the Power LED goes dark, and then glows steady
amber while the software loads and the system performs a self-test.
After the software finishes loading, the Power LED glows steady green

Console PortA male DB-9 serial port to which you can make a console connection using

an RS-232 (or "null modem") cable. The management station from which
you make a serial connection to the HiveAP must have a VT100 emulation
program, such as Tera Term Pro© (a free terminal emulator) or Hilgraeve
Hyperterminal® (provided with Windows® operating systems). The
following are the serial connection settings: bits per second:9600, data
bits: 8, parity: none, stop bits: 1, flow control: none.

Device Lock SlotYou can physically secure the HiveAP by attaching a lock and cable (such

as a Kensington® notebook lock) to the device lock slot. After looping the
cable around a secure object, insert the T-bar component of the lock into
the slot on the HiveAP and turn the key to engage the lock mechanism.

802.11b/g RP-SMA Connector(For future use) You can connect a detachable single-band antenna to the
male 802.11b/g RP-SMA connector. Note that doing so disables the
adjacent fixed antenna.

Deployment Guide 11

Chapter 1 The HiveAP Platform

Ethernet and Console Ports

There are two ports on the HiveAP: a 10/100Base-T/TX Ethernet port and a male DB-9 console port. Both ports use
standard pin assignments.

The pin assignments in the PoE (Power over Ethernet) Ethernet port follow the TIA/EIA-568-B standard (see

Figure2). The PoE port accepts standard types of Ethernet cable—cat3, cat5, cat5e, or cat6—and receives power

over this cable from power sourcing equipment (PSE) that is 802.3af-compatible. Such equipment can be embedded
in a switch or router, or it can come from purpose-built devices that inject power into the Ethernet line en route to
the HiveAP. Because the PoE port has autosensing capabilities, the wiring termination in the Ethernet cable can be
either straight-through or cross-over.

Figure 2 PoE Wire Usage and Pin Assignments

Pin Numbers

1 8

(View of the PoE port

on the HiveAP)

The PoE port is auto-sensing and can automatically adjust to transmit and receive data over straight-through or cross-over Ethernet
connections. Likewise, it can automatically adjust to 802.3af Alternative A and B power delivery methods. Furthermore, when the
Alternative A method is used, the PoE port automatically allows for polarity reversals depending on its role as either MDI or MDI-X.

T568A-Terminated Ethernet Cable

with an RJ-45 Connector

T568B -terminated Ethernet Cable

with an RJ-45 Connector

Pin Data Signal MDI MDI-X MDI or MDI-X

1Transmit +DC+DC–– – –
2Transmit -DC+DC–– – –
3Receive +DC– DC+ – – –
4(unused) – – –– – –DC+
5(unused) – – –– – –DC+
6Receive -DC– DC+ – – –
7(unused) – – –– – –DC–
8(unused) – – –– – –DC–

MDI = Medium dependent interface for straight-through connections
MDI-X = Medium dependent interface for cross-over (X) connections

Pin T568A Wire Color

1White/Green
2Green
3White/Orange
4Blue
5White/Blue
6Orange
7White/Brown
8Brown

Pin T568B Wire Color

1White/Orange
2Orange
3White/Green
4Blue
5White/Blue
6Green
7White/Brown
8Brown

802.3af Alternative A
(Data and Power on
the Same Wires)

T568A and T568B are two standard
wiring termination schemes. Note that
the only difference between them is
that the white/green + solid green pair
of wires and the white/orange + solid
orange pair are reversed.

For straight-through Ethernet cables—
using either the T568A or T568B
standard—the eight wires terminate at
the same pins on each end.

For cross-over Ethernet cables, the
wires terminate at one end according
to the T568A standard and at the
other according to T568B.

802.3af Alternative B
(Data and Power on
Separate Wires)

12 Aerohive

PRODUCTOVERVIEW

The pin assignments in the male DB-9 console port follow the EIA (Electronic Industries Alliance) RS-232 standard. To
make a serial connection between your management system and the console port on the HiveAP, you can use a null
modem serial cable, use another serial cable that complies with the RS-232 standard, or refer to the pin-to-signal
mapping shown in Figure3 to make your own serial cable. Connect one end of the cable to the console port on the
HiveAP and the other end to the serial (or COM) port on your management system. The management system must
have a VT100 terminal emulation program, such as Tera Term Pro© (a free terminal emulator) or Hilgraeve
Hyperterminal® (provided with Windows® operating systems).

Figure 3 Console Port Pin Assignments

RS-232 Standard Pin Assignments

Male DB-9 Console Port

1 2 3 4 5

6 7 8 9

(View of the console

port on the HiveAP)

Pin Signal Direction

1DCD (Data Carrier Detect)(unused)

2RXD (Received Data)Input
3TXD (Transmitted Data)Output

4DTR (Data Terminal Ready)(unused)

5GroundGround

6DSR (Data Set Ready)(unused)
7RTS (Request to Send)(unused)
8CTS (Clear to Send)(unused)
9RI (Ring Indicator)(unused)

The above pin assignments show a DTE configuration for a
DB-9 connector complying with the RS-232 standard. Because
this is a console port, only pins 2, 3, and 5 need be used.

Status LEDs

The four status LEDs on the top of the HiveAP indicate various states of activity through their color (dark, green,
amber) and illumination patterns (steady glow or blinking). The meanings of the various color + illumination
patterns for each LED is explained below.

Power

• Dark: No power

• Steady green: Powered on and the firmware is running normally

• Steady amber: Firmware is booting up or is being updated

• Blinking amber: Alarm indicating firmware failure

LAN

• Dark: Ethernet link is down or disabled

• Steady green: Ethernet link is up but inactive

• Blinking green: Ethernet link is up and active

Access

• Dark: Wireless link is disabled

• Steady green: Wireless link is up but inactive

• Blinking green: Wireless link is up and active

Mesh

• Dark: Wireless link is disabled

• Steady green: Wireless link is up but inactive

• Blinking green (fast): Wireless link is up and the HiveAP is searching for other hive members

• Blinking green (slowly): Wireless link is up and active

Deployment Guide 13

Chapter 1 The HiveAP Platform

Antennas

The HiveAP includes two fixed dual-band antennas. These antennas are omnidirectional, providing fairly equal
coverage in all directions in a toroidal (donut-shaped) pattern around each antenna. When the antennas are
positioned vertically, coverage expands primarily on the horizontal plane, extending horizontally much more than
vertically. See Figure4, which shows the toroidal pattern emanating from a single vertically positioned antenna. To
change coverage to be more vertical than horizontal, position the antennas horizontally. You can also resize the
area of coverage by increasing or decreasing the signal strength.

Figure 4 Omnidirectional Radiation Pattern

The omnidirectional antennas
radiate equally in all directions,
forming a toroidal pattern.

Note: To show the shape of radiation more clearly,
this illustration depicts the coverage provided by
only one active antenna and is not drawn to scale.

HiveAP

The pair of fixed dual-band antennas can operate at different frequencies concurrently—one antenna at 2.4 GHz
(IEEE 802.11b/g) and the other at 5 GHz (IEEE 802.11a)—and they can also both operate currently at the same
frequency—for example, at 2.4 GHz. Conceptually, the relationship of antennas and radios is shown in Figure5.

Figure 5 Antennas and Radios

\

RP-SMA Connectors

802.11a/b/g
Dual-Band

Fixed

Antenna

Antenna
Switch 1

Antenna
Switch 2

802.11a/b/g
Dual-Band

Fixed

Antenna

Radio 1

RF 802.11b/g

Cut-away view of the HiveAP to show the relationship
of the antennas and the two internal radios.

Radio 2

RF 802.11a

14 Aerohive

MOUNTINGTHE HIVEAP

After connecting an external antenna, you must enter the following command to move subinterfaces from the fixed
antennas to the external antenna:

interface subinterface radio antenna external

where subinterface stems from an interface (wifi0 or wifi1) linked to the radio to which the external antenna
connects: radio 1 (frequency = 2.4 GHz for IEEE 802.11b/g) or radio 2 (frequency = 5 GHz for IEEE 802.11a).

Note that you link interfaces to radios, and subinterfaces to antennas. For example, to link the wifi0 interface to
radio 2, enter this command:

interface wifi0 radio profile name phymode 11a

where radio profile name is a set of previously defined radio parameters. Then, link one of the wifi0.x
subinterfaces to the external antenna connected to radio 2 by using the interface subinterface radio
antenna external command. If you do not enter this command, the subinterface uses the remaining fixed
antenna that remains connected to radio 2 (the external antenna only disables the adjacent fixed antenna).

Note: For information about these and other commands, see the Aerohive CLI Reference Guide.

MOUNTINGTHE HIVEAP

You can use the mounting plate to attach the HiveAP to any surface that supports its weight (1.5 lb., 0.68 kg) and to
which you can screw or nail the plate. First, mount the plate to the surface, and then attach the device to the
plate, as shown in Figure6.

Figure 6 Mounting the HiveAP on a Wall

1

With the two wings at the sides of the plate extending
away from the surface, attach the mounting plate to a
secure object such as a wall, ceiling, post, or beam.

3

Use the mounting screw
to secure the HiveAP
to the plate.

2

Insert the pins on the underside
of the HiveAP into the two slots.

Note: There are a variety of holes through which you can
screw or nail the plate in place. Choose the two or three that
best suit the object to which you are attaching it.

Deployment Guide 15

Chapter 1 The HiveAP Platform

DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS

Understanding the range of specifications for the HiveAP is necessary for optimal deployment and operation of the
device. The following specifications describe the physical features and hardware components, the power adapter
and PoE (Power over Ethernet) electrical requirements, and the temperature and humidity range in which the
device can operate.

Device Specifications

• Chassis dimensions: 8 1/4" W x 1" H x 4 15/16" D (21 cm W x 2.5 cm H x 12.5 cm D)

• Weight: 1.5 lb. (0.68 kg)

• Antennas: Two fixed dual-band 802.11a/b/g antennas, and two RP-SMA connectors for detachable single-band

802.11a or 802.11b/g antennas

• Serial port: DB-9 (bits per second:9600, data bits: 8, parity: none, stop bits: 1, flow control: none)

• Ethernet port: autosensing 10/100Base-T/TX Mbps, with IEEE 802.3af-compliant PoE (Power over Ethernet)

Power Specifications

• AC/DC power adapter:

• Input:100 – 240 VAC

• Output: 48V/0.38A

• PoE nominal input voltages: 48 V, 0.35A

• RJ-45 power input pins: Wires 4, 5, 7, 8 or 1, 2, 3, 6

Environmental Specifications

• Operating temperature: 32 to 122 degrees F (0 to 50 degrees C)

• Storage temperature: -4 to 158 degrees F (-20 to 70 degrees C)

• Relative Humidity: Maximum 95%

16 Aerohive

Chapter 2The HiveManager Platform

The HiveManager is a management appliance that provides centralized configuration, monitoring, and reporting for
multiple HiveAPs. The following are a few of the many benefits that a HiveManager offers:

• True "zero configuration" installations of HiveAPs

• Template-based configurations that simplify the deployment of large numbers of HiveAPs

• Scheduled firmware upgrades on HiveAPs by location

• Exportation of detailed information on HiveAPs for reporting

This chapter covers the following topics related to the HiveManager platform:

• "Product overview" on page18

• "Ethernet and Console Ports" on page19

• "Status LEDs" on page20

• "Rack Mounting the HiveManager" on page21

• "Device, Power, and Environmental Specifications" on page22

Deployment Guide 17

Chapter 2 The HiveManager Platform

PRODUCTOVERVIEW

The Aerohive HiveManager is a central management system for configuring and monitoring HiveAPs. You can see its
hardware components in Figure1 and read a description of each component in Table1.

Figure 1 HiveManager Hardware Components

Front Panel

Mounting

Bracket

Rear Panel

System

Fans

Console

Port

Serial

Number

USB

Port

Status

LEDs

MGT and LAN
Ethernet Ports

On/Off
Switch

AC Power

Inlet

Mounting

Bracket

Power

Fan

Table 1 HiveManager Component Descriptions

Component Description

Mounting BracketsThe two mounting brackets allow you to mount the HiveManager in a

standard 19" (48.26 cm) equipment rack. You can also move the brackets
to the rear of the chassis if you need to reverse mount it.

Console PortA male DB-9 serial port to which you can make a console connection using

an RS-232 (or "null modem") cable. The pin assignments are the same as
those on the HiveAP (see "Ethernet and Console Ports" on page12).

The management station from which you make a serial connection to the
HiveManager must have a VT100 emulation program, such as Tera Term
Pro© (a free terminal emulator) or Hilgraeve Hyperterminal® (provided
with Windows® operating systems). The following are the serial
connection settings: bits per second:9600, data bits: 8, parity: none, stop
bits: 1, flow control: none. The default login name is root and the
password is aerohive. After making a connection, you can access the
Linux operating system.

18 Aerohive

PRODUCTOVERVIEW

Component Description

USB PortThe USB port is reserved for internal use.
Status LEDsThe status LEDs convey operational states for the system power and hard

disk drive. For details, see "Status LEDs" on page20.

MGT and LAN Ethernet PortsThe MGT and LAN Ethernet ports are compatible with 10/100/1000-Mbps

connections, automatically negotiate half- and full-duplex mode with the
connecting devices, and support RJ-45 connectors. They are autosensing
and automatically adjust to straight-through and cross-over Ethernet
cables. The two ports allow you to separate traffic between the
HiveManager and its administrators from traffic between the
HiveManager and the HiveAPs it manages.

System FansThe two system fans maintain an optimum operating temperature. Be

sure that air flow through the system fan vents is not obstructed.
Serial NumberThe serial number
AC Power InletThe three-prong AC power inlet is a C14 chassis plug through which you

can connect a HiveManager to a 100 – 240-volt AC power source using the

10-amp/125-volt IEC power cord that ships with the product.
On/Off SwitchThe on ( | ) and off ( ) switch controls the power to the HiveManager.
Power FanThe fan that maintains the temperature of the power supply.

Ethernet and Console Ports

The two 10/100/1000-Mbps Ethernet ports on the HiveManager labeled MGT and LAN use standard RJ-45 connector
pin assignments that follow the TIA/EIA-568-B standard (see Figure2). They accept standard types of Ethernet
cable—cat3, cat5, cat5e, or cat6. Because the ports have autosensing capabilities, the wiring termination in the
Ethernet cables can be either straight-through or cross-over.

Figure 2 Ethernet Port LEDs and Pin Assignments

(View of an Ethernet port

on the HiveManager)

Link Rate LED

Dark: 10 Mbps
Green: 100 Mbps
Amber: 1000 Mbps

Link Activity LED

Dark: Link is down
Steady amber: Link is up

but inactive

Blinking amber: Link is up

and active

8 1

Pin Numbers

The Ethernet ports are auto-sensing and can automatically adjust to transmit and receive data over straight-through or cross-over
Ethernet connections. For a diagram showing T568A and T568B wiring, see "Ethernet and Console Ports" on page12.

10/100Base-T

Pin

Data Signal

1Transmit +BI_DA+
2Transmit -BI_DA­3Receive +BI_DB+
4(unused)BI_DC+
5(unused)BI_DC­6Receive -BI_DB­7(unused)BI_DD+
8(unused)BI_DD-

Legend: BI_D = bidirectional
A+/A-, B+/B-, C+/C-, D+/D- = wire pairings

1000Base-T
Data Signal

Note: The default IP address/netmask for the MGT interface is 192.168.2.10/24, and the IP address of the

default gateway is 192.168.2.254. By default, the LAN interface is not configured.

Deployment Guide 19

Chapter 2 The HiveManager Platform

The pin assignments in the male DB-9 console port follow the EIA (Electronic Industries Alliance) RS-232 standard. To
make a serial connection between your management system and the console port on the HiveManager, you can use a
null modem serial cable, use another serial cable that complies with the RS-232 standard, or refer to the
pin-to-signal mapping shown in Figure3 to make your own serial cable. Connect one end of the cable to the console
port on the HiveManager and the other end to the serial (or COM) port on your management system. The
management system must have a VT100 terminal emulation program, such as Tera Term Pro© (a free terminal
emulator) or Hilgraeve Hyperterminal® (provided with Windows® operating systems).

Figure 3 Console Port Pin Assignments

RS-232 Standard Pin Assignments

Male DB-9 Console Port

1 2 3 4 5

6 7 8 9

(View of the console port

on the HiveManager)

Pin Signal Direction

1DCD (Data Carrier Detect)(unused)

2RXD (Received Data)Input
3TXD (Transmitted Data)Output

4DTR (Data Terminal Ready)(unused)

5GroundGround

6DSR (Data Set Ready)(unused)
7RTS (Request to Send)(unused)
8CTS (Clear to Send)(unused)
9RI (Ring Indicator)(unused)

The above pin assignments show a DTE configuration for a
DB-9 connector complying with the RS-232 standard. Because
this is a console port, only pins 2, 3, and 5 need be used.

The serial connection settings are as follows:

• Bits per second: 9600

• Data bits: 8

• Parity: none

• Stop bits: 1

• Flow control: none

Status LEDs

The two status LEDs on the front of the HiveManager indicate various states of activity through their color (dark,
green, amber) and illumination patterns (steady glow or blinking). The meanings of the various color + illumination
patterns for each LED are shown in Figure4.

Figure 4 Status LEDs

System Power

Dark: No power
Steady illumination: Powered on

Hard Disk Drive

Dark: Idle
Blinking: Active

20 Aerohive

RACK MOUNTINGTHE HIVEMANAGER

RACK MOUNTINGTHE HIVEMANAGER

You can mount the HiveManager in a standard 19" (48 cm) equipment rack with two rack screws—typically 3/4",
1/2", or 3/8" long with 10-32 threads. The HiveManager ships with mounting brackets already attached to its left
and right sides near the front panel (see Figure1 on page18). In this position, you can front mount the HiveManager
as shown in Figure5. Depending on the layout of your equipment rack, you might need to mount the HiveManager in
reverse. To do that, move the brackets to the left and right sides near the rear before mounting it.

Figure 5 Mounting the HiveManager in an Equipment Rack

Rack Rails

Mounting

Bracket

1.Position the HiveManager so that the holes in the mounting brackets align with two mounting holes in the
equipment rack rails.

2.Insert a screw through a washer, the hole in one of the mounting brackets, and a hole in the rail.

3.Tighten the screw until it is secure.

4.Repeat steps 2 and 3 to secure the other side of the HiveManager to the rack.

Deployment Guide 21

WasherRack

Screw

Chapter 2 The HiveManager Platform

DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS

Understanding the range of specifications for the HiveAP is necessary for optimal deployment and operation of the
device. The following specifications describe the physical features and hardware components, the power adapter
and PoE (Power over Ethernet) electrical requirements, and the temperature and humidity range in which the
device can operate.

Device Specifications

• Form factor: 1U rack-mountable device

• Chassis dimensions: 16 13/16" W x 1 3/4" H x 15 13/16" D (42.7 cm W x 4.4 cm H x 40.2 cm D)

• Weight: 13.75 lb. (6.24 kg)

• Serial port: male DB-9 RS-232 port (bits per second:9600, data bits: 8, parity: none, stop bits: 1, flow control:

none)

• USB port: standard Type A USB 2.0 port

• Ethernet ports: MGT and LAN — autosensing 10/100/1000Base-T/TX Mbps

Power Specifications

• ATX (Advanced Technology Extended) autoswitching power supply with PFC (power factor corrector):

• Input: 100 – 240 VAC

• Output: 250 watts

• Power supply cord: Standard three conductor SVT 18AWG cord with an NEMA5-15P three-prong male plug and

three-pin socket

Environmental Specifications

• Operating temperature: 32 to 140 degrees F (0 to 60 degrees C)

• Storage temperature: -4 to 176 degrees F (-20 to 80 degrees C)

• Relative Humidity: 10% – 90% (noncondensing)

22 Aerohive

Chapter 3Using HiveManager

You can conceptualize the Aerohive cooperative control architecture as consisting of three broad planes of
communication. On the data plane, wireless clients gain network access by forming associations with HiveAPs. On
the control plane, HiveAPs communicate with each other to coordinate functions such as best-path forwarding, fast
roaming, and automatic RF (radio frequency) management. On the management plane, the HiveManager provides
centralized configuration, monitoring, and reporting of multiple HiveAPs. These three planes are shown in Figure1.

Figure 1 Three Communication Planes in the Aerohive Cooperative Control Architecture

̱ ¬¸» ©·®»¼
²»¬©±®µ òòò

Ü¿¬¿ д¿²»

©·®»´»-- ½´·»²¬ ¬®¿ºº·½ ø«-»® ¼¿¬¿÷

·- ¬¸» ´±¹·½¿´ ¼·ª·-·±² ±º

¬®¿ª»®-·²¹ ¿ ©·®»´»--ó¬±ó©·®»¼ ÔßÒò Ì®¿ºº·½

·² ¬¸» ¼¿¬¿ °´¿²» º±´´±©- ±°¬·³¿´ °¿¬¸­¬¸¿¬ ª¿®·±«- ³»½¸¿²·-³- ·² ¬¸» ½±²¬®±´
°´¿²» ¼»¬»®³·²»ò

̸» ¼¿¬¿ °´¿²»

ݱ²¬®±´ д¿²»

̸» ½±²¬®±´ °´¿²» ·-

̸» ³¿²¿¹»³»²¬

°´¿²» ·- ¬¸» ´±¹·½¿´ ¼·ª·-·±² ±º

Ó¿²¿¹»³»²¬ д¿²»

Ó¿²¿¹»³»²¬

ͧ-¬»³

¬¸» ´±¹·½¿´ ¼·ª·-·±² ±º ¬®¿ºº·½ ¬¸¿¬
¸·ª» ³»³¾»®- «-» ¬± ½±´´¿¾±®¿¬» ±² ¸±©
¾»-¬ ¬± º±®©¿®¼ «-»® ¼¿¬¿ô ½±±®¼·²¿¬»
®¿¼·± º®»¯«»²½·»-ô ¿²¼ °®±ª·¼» ´¿§»®óî
®±¿³·²¹ ½¿°¿¾·´·¬·»- ©·¬¸ »¿½¸ ±¬¸»® ¿²¼
´¿§»®óí ®±¿³·²¹ ½¿°¿¾·´·¬·»- ©·¬¸ ¬¸»
³»³¾»®- ±º ²»·¹¸¾±®·²¹ ¸·ª»-ò

¿¼³·²·-¬®¿¬·ª» ¬®¿ºº·½ ®»´¿¬·²¹ ¬± ¬¸»

½±²º·¹«®¿¬·±² ¿²¼ ³±²·¬±®·²¹ ±º Ø·ª»ßÐ-ò Ú®±³ ¿

³¿²¿¹»³»²¬ -§-¬»³ô ¿² ¿¼³·² ½¿² «-» ¬¸» Ø·ª»Ó¿²¿¹»® ¬±

½±²º·¹«®»ô ³¿·²¬¿·²ô ¿²¼ ³±²·¬±® ³«´¬·°´» Ø·ª»ßÐ-ô »--»²¬·¿´´§ ½±±®¼·ó

²¿¬·²¹ ¬¸» ½±²¬®±´ ¿²¼ ¼¿¬¿ °´¿²»- º®±³ ¿ -·²¹´»ô ½»²¬®¿´ ´±½¿¬·±²ò

As you can see in Figure1, the HiveManager operates solely on the management plane. Any loss of connectivity
between the HiveManager and the HiveAPs it manages only affects HiveAP manageability; such a loss has no impact
on communications occurring on the control and data planes.

Deployment Guide 23

Chapter 3 Using HiveManager

This chapter introduces the HiveManager GUI and explains how to do the following basic tasks:

• Using the console port to change the network settings for the MGT and LAN interfaces

• Powering on the HiveManager and connecting it to a network

• Installing the GUI client on your management system and logging in

It then introduces the HiveManager GUI, including a summary of the configuration workflow. Finally, the chapter
concludes with the procedures for updating HiveAP firmware and HiveManager software. The sections are as
follows:

• "Installing and Connecting to the HiveManager GUI" on page25

• "Introduction the the HiveManager GUI" on page28

• "Detaching Windows" on page29

• "Cloning Configurations" on page29

• "Sorting Displayed Data" on page30

• "Multiselecting" on page30

• "HiveManager Configuration Workflow" on page31

• "Updating HiveAP Firmware" on page32

• "Updating Software on the HiveManager" on page33

24 Aerohive

INSTALLINGAND CONNECTINGTOTHE HIVEMANAGER GUI

INSTALLINGAND CONNECTINGTOTHE HIVEMANAGER GUI

To begin using the HiveManager GUI, you must first configure one or both of its interfaces to be accessible on the
network, put the HiveManager and your management system (that is, your computer) on the network, and then
make an HTTP connection from your system to the MGT port of the HiveManager and download the GUI application
for use with JWS (Java Web Start).

Note: The MGT and LAN interfaces must be in different subnets. The MGT interface is for managing the

HiveManager and the LAN interface is for managing HiveAPs. If you use only one interface for both types of
management traffic, you must use the MGT interface.

Besides the HiveManager and your management system, you need two Ethernet cables and a serial cable (or "null
modem"). The Ethernet cables can be standard cat3, cat5, cat5e, or cat6 cables with T568A or T568B terminations
and RJ-45 connectors. The serial cable must comply with the RS-232 standard and terminate on the HiveManager
end with a female DB-9 connector. (For more details, see "Ethernet and Console Ports" on page19.)

The GUI requirements for the management system are as follows:

• Standard browser that associates JNLP (Java Network Launching Protocol) file types with the Java application
(The Java installation typically makes this association automatically, although not in all UNIX environments.)

• JRE (Java Runtime Environment) version 1.5 or later

• JWS application, which is automatically installed with JRE 1.4.2 or later

• VT100 terminal emulation program, such as Tera Term Pro© (a free terminal emulator) or Hilgraeve

Hyperterminal® (provided with Windows® operating systems)

1

Changing Network Settings for the HiveManager

To be able to connect the HiveManager to the network, you must first set the IP address/netmask of its MGT
interface so that it is in the subnet to which you plan to cable it. To do this, you can use the startup wizard that is
available through the console port.

1.Connect the power cable to a 100 – 240-volt power source, and use the switch on the back panel to turn on the
HiveManager.

2.Connect one end of an RS-232 serial cable to the serial port (or Com port) on your management system.

3.Connect the other end of the cable to the male DB-9 console port on the HiveManager.

4.On your management system, run a VT100 emulation program using the following settings:

• Bits per second (baud rate): 9600

• Data bits: 8

• Parity: none

• Stop bits: 1

• Flow control: none

5.Log in by entering the default user name (root) and password (aerohive).

6.The network startup wizard automatically starts. If not, enter the following command: startupWizard.sh

7.Follow the instructions in the wizard to configure the IP address and netmask for the MGT and LAN interfaces,
as well as the default gateway and host name of the HiveManager and its primary DNS server.

Note: The default IP address/netmask for the MGT interface is 192.168.2.10/24, and the IP address of the

default gateway is 192.168.2.254.

1.JRE 1.5 is basically the same as JRE 5.0. However, JRE 1.5 version names are more granular (1.5.0_01, 1.5.0_02, 1.5.0_03, and

so on). Use JRE 1.5.0_06 or later or the latest version of JRE 5.0.

Deployment Guide 25

Chapter 3 Using HiveManager

When deciding to use one interface (MGT) or both (MGT and LAN), keep in mind that there are two main types
of traffic to and from the HiveManager:

• HiveManager management traffic for admin access and FTP uploads

• HiveAP management traffic for CAPWAP, SNMP monitoring and notifications, and TFTP configuration and

software downloads

When you enable both interfaces, HiveManager management traffic uses the MGT interface while HiveAP
management traffic uses the LAN interface, as shown in Figure2.

Figure 2 Using Both MGT and LAN Interfaces

пртптктпо

᫬»®

Ø·ª»- ·² ¼·ºº»®»²¬ -«¾²»¬-

пртптнтрсом

пртптмтрсом

пртптлтрсом

Û¿½¸ ¸·ª» ½±²¬¿·²­³«´¬·°´» Ø·ª»ßÐ-ò

ÔßÒ

пртптптисом

ÓÙÌ

пртптотисом

Ø·ª»Ó¿²¿¹»®

ß¼³·²

пртптйтнм

Static Routes: The HiveManager sends traffic destined for 10.1.6.0/24 to 10.1.2.1.

The HiveManager sends traffic destined for 10.1.7.0/24 to 10.1.2.1.

Default Gateway:10.1.1.1 (The HiveManager sends traffic here when there are no specific routes to the destination.)

Í©·¬½¸

пртптотп

пртптптп

᫬»®

ÚÌÐ Í»®ª»®

Note: To set static routes after you log in to the GUI, click HiveManager Administration > Network

Configuration, complete the fields in the Route Configuration section, and then click Add.

When only the MGT interface is enabled, both types of management traffic use the same interface. A possible
drawback to this approach is that the two types of management traffic cannot be separated into two different
networks. For example, if you have an existing management network, you cannot use it for the HiveManager
management traffic. Both the HiveManager and HiveAP management traffic would need to flow on the
operational network because the MGT interface would need to be on that network so that the HiveManager
could communicate with the HiveAPs (see Figure3). However, if the separation of both types of traffic is not an
issue, then using just the MGT interface is a simple approach to consider.

Figure 3 Using Just the MGT Interface

пртптктпо

᫬»®

Ø·ª»- ·² ¼·ºº»®»²¬ -«¾²»¬-

пртптнтрсом

пртптмтрсом

пртптлтрсом

Û¿½¸ ¸·ª» ½±²¬¿·²­³«´¬·°´» Ø·ª»ßÐ-ò

Í©·¬½¸

ÓÙÌ

пртптптисом

Ø·ª»Ó¿²¿¹»®

ß¼³·²

пртптйтнм

Default Gateway:10.1.1.1 (The HiveManager sends all traffic to the default gateway.)

пртптптп

ÚÌÐ Í»®ª»®

8.After you complete the startup wizard, enter these commands to reboot the software:

stopHiveManager.sh root public
reboot

You can now disconnect the serial cable.

26 Aerohive

INSTALLINGAND CONNECTINGTOTHE HIVEMANAGER GUI

Installing the GUI Client and Connecting to the MGT Interface

1.Connect Ethernet cables from the MGT interface and LAN interface—if you are using it—to the network.

2.Connect an Ethernet cable from your management system to the network so that you can make an Ethernet
connection to the IP address you set for the MGT interface.

3.Open a web browser and enter the IP address of the MGT interface in the address field followed by the
destination port number 9090. For example, if you changed the IP address to 10.1.1.20, enter this in the address
field: http://10.1.1.20:9090

Note: If you ever forget the IP address of the MGT interface and cannot make an HTTP connection to the

HiveManager, make a serial connection to its console port and enter this command: ifconfig. The
output displays data about the MGT interface (internally called "eth0"), including its IP address. For
serial connection settings, see "Changing Network Settings for the HiveManager" on page25.

The management system downloads the GUI client software from the HiveManager and installs it in a Java
sandbox. The initial download and installation might take a minute or so to complete, and the web browser
window might appear blank for several seconds at the start. This is normal. After a few seconds, a download
status bar appears onscreen that allows you to monitor the progress of the download and installation.

When the download and installation completes, a login prompt appears.

4.Type the default user name and password (root and aerohive) in the login fields and then click Connect.

The HiveManager GUI application automatically opens and prompts you to enter a license key.

5.Copy the license key string provided by Aerohive when the HiveManager was purchased, paste it in the License
Key field, and then click OK.

You are now logged in to the HiveManager GUI.

Deployment Guide 27