Aerohive Networks HIVEAP340 Users Manual
Chapter 4 The HiveAP 340 Platform
The Aerohive HiveAP 340 is a high-performance and highly reliable 802.11n wireless access point. The HiveAP 340
provides dual concurrent 802.11b/g/n and 802.11a/n radios for 3x3 MIMO (Multiple In, Multiple Out) and dual
10/100/1000 Ethernet ports for link aggregation or link redundancy. Its power management system uses a concept
called smart PoE (Power over Ethernet) to adjust its power consumption automatically in response the available
power in different environments. Smart PoE supports the IEEE 802.3af standard and the 802.3at pre-standard.
This chapter covers the following topics relating to the HiveAP:
• "HiveAP 340 Pro duct Overview" on page 46
• "Ethernet and Console Ports" on page 48
• "Status LEDs" on page 52
• "Antennas" on page 52
• "Mounting the HiveAP 340" on page 56
• "Ceiling Mount" on page 56
• "Surface Mount" on page 58
• "Device, Power, and Environmental Specifications" on page 59
Deployment Guide 45
Chapter 4 The HiveAP 340 Platform
Power
Connector
10/100 /1000
Mbps PoE Ports
Reset
Button
Console
Port
Device
Lock Slot
Status LEDs
802.11b/g/n RP-SMA Connectors for Detachable Single-Band Antennas
802.11a/n RP-SMA Connectors for Detachable Single-Band Antennas
HIVEAP 340 PRODUCT OVERVIEW
The HiveAP 340 is a multi-channel wireless access point. It is compatible with IEEE 802.11b/g/n (2.4 GHz) and IEEE
802.11a/n (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 Figure 1. Each component is described i n Table 1.
Figure 1 HiveAP 340 Hardware Components
5 GHz (B)5 GHz (C)
2.4 GHz (A) 2.4 GHz (B) 2.4 GHz (C)
ETH0
ETH1
48V DC
(.625A)
CONSOLE
RESET
5 GHz (A)
Table 1 HiveAP 340 Component Descriptions
Component Description
Status LEDs The status LEDs convey operational states for system power, firmware,
Ethernet interfaces, and radios. For details, see "Status LEDs" on page 52.
Device Lock Slot You can physica ll y secure the HiveAP by attaching a lock and cable (such
as a Kensington® notebook lock) to the device lock slot or by using the
lock adapter that is included in the mounting kit and a padlock. For more
information, see "Locking the HiveAP 340" on page 57.
802.11a/b/g/n RP-SMA Connectors You can connect up to six detachable single-band antennas to the male
802.11a/b/g/n RP-SMA (reverse polarity-subminiature version A)
connectors. Connect the longer antennas, which support 2.4 GHz
frequencies (for IEEE 802.11b/g/n), to the connectors on the side panel
with the Ethernet ports. Connect the shorter antennas, which support 5
GHz frequencies (for IEEE 802.11a/n), to the connectors on the side pane l
with the device lock slot. For details, see "Antennas" on page 52.
46 Aerohive
HIVEAP 340 PRODUCT OVERVIEW
Component Description
10/100/1000 Mbps PoE Ports The two 10/100/1000-Mbps Ethernet ports—ETH0 and ETH1—support IEEE
802.3af and 802.3at PoE (Power over Ethernet) and receive RJ-45
connectors. The HiveAP can receive power through one or both Ethernet
connections from power sourcing equipment (PSE) that is compatible with
the 802.3af standard and forthcoming 802.at standard. (If you connect
the HiveAP to a power source through the power connector and PoE ports
simultaneously, the device draws power through the power connector and
automatically disables PoE.)
You can configure ETH0 and ETH1 as two individual Ethernet interfaces,
combine them into an aggregate interface to increase throughput, or
combine them into a redundant interface to increase reliability. You can
connect the HiveAP 340 to a wired network or to a wired device (such as
a security camera) through these ports using bridging. They are
compatible with 10/100/1000Base-T/TX and automatically negotiate
half- and full-duplex conn ections with the connecting device. They are
autosensing and adjust to straight-through and cross-over Ethernet cables
automatically. For details, see "Ethernet and Console Ports" on page 48.
Power Connector The 48-volt DC power connector (0.625 amps) is one of two methods
through which you can power the HiveAP 340. To connect it to a 100 –
240-volt AC power source, use the AC/DC power adaptor tha t is available
as an extra option. Because the HiveAP does not have an on/off switch,
connecting it to a power source automatically powers on the device.
Console Port You can access the CLI by making a serial connection to the RJ-45 console
port. The management station from which you make a serial connection
to the HiveAP must have a VT100 emulation program, such as Tera Term
©
(a free terminal emulator) or Hilgraeve Hyperterminal® (provided
Pro
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. For details, see "Ethernet and Console
Ports" on page 48.
Reset Button The reset button allows you to reboot the device or reset the HiveAP to
its factory default settings. Insert a paper clip , o r som et hing sim ilar, 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 as the system reboots.
Then it pulses green while the firmware loads and the system performs a
self-test. After the software finishes loading, the Power LED glows steady
green.
To disable the reset button from resetting the configuration, enter this
command: no reset-button reset-config-enable Pressing the
button between 1 and 5 seconds will still reboot the Hive AP, but pressing
it for more than 5 seconds will not reset its configuration.
Note: The rear surface of the HiveAP 340 is used for heat dissipation to reduce the internal temperature.
Consequently, it can become hot, so use caution when handling it.
Deployment Guide 47
Chapter 4 The HiveAP 340 Platform
ETH0
Pin T568A Wire Color
1 White/Green
2 Green
3 White/Orange
4Blue
5 White/Blue
6 Orange
7 White/Brown
8Brown
(View of the ETH0 PoE
Port on the HiveAP 340)
8 1
Pin Numbers
Pin T568B Wire Color
1 White/Orange
2 Orange
3 White/Green
4Blue
5 White/Blue
6 Green
7 White/Brown
8Brown
T568A-T erminated Ethernet Cable
with an RJ-45 Connector
802.3af Alternative A
(Data and Power on
the Same Wires)
802.3af Alternative B
(Data and Power on
Separate Wires)
802.3at Wiring Options
Pin Data Signal MDI MDI-X MDI or MDI-X 1 2 3 4
1 Transmit + DC+ DC– – – – DC1+ DC1– DC1+ DC1–
2 Transmit - DC+ DC– – – – DC1+ DC1– DC1+ DC1–
3 Receive + DC– DC+ – – – DC1– DC1+ DC1– DC1+
4 (unused) – – – – – – DC+ DC2+ DC2+ DC2– DC2–
5 (unused) – – – – – – DC+ DC2+ DC2+ DC2– DC2–
6 Receive - DC– DC+ – – – DC1– DC1+ DC1– DC1+
7 (unused) – – – – – – DC– DC2– DC2– DC2+ DC2+
8 (unused) – – – – – – DC– DC2– DC2– DC2+ DC2+
MDI = Medium dependent interface for straight-through connections
MDI-X = Medium dependent interface for cross-over (X) connections
The PoE ports are auto-sensing and can automatically adjust to transmit and receive data over straight-through or cross-over Etherne
connections. Likewise, they can automatically adjust to 802.3af Alternative A and B power delivery methods. Furthermore, when the
Alternative A method is used, the ports automatically allow for polarity reversals depending on their role as either MDI or MDI-X. In
802.3at, the 1/2 and 3/6 wire pairs connect to DC source 1 and 4/5 and 7/8 pairs to DC source 2 in PSE. Although the exact polarity
depends on the PSE design, the HiveAP 340 Ethernet ports can support all possible options.
T568B -terminated Ethernet Cable
with an RJ-45 Connector
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.
Ethernet and Console Ports
There are three ports on the HiveAP 340: two RJ-45 10/100/1000Base-T/TX Ethernet ports and an RJ-45 console port.
The pin assignments in the PoE (Power over Ethernet) Ethernet ports follow the TIA/EIA-568-B standard (see
Figure 2). The ports accept standard types of Ethernet cable—cat3, cat5, cat5e, or cat6—and can receive power
over this cable from power sourcing equipment (PSE) that is 802.3af-compatible. If you use cat5, cat5e, or cat6
cables, the HiveAP 340 can also support 802.3at-compliant PSE. 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 ports have 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
48 Aerohive
HIVEAP 340 PRODUCT OVERVIEW
Smart PoE
The HiveAP 340 applies the Aerohive concept of smart PoE to adjust power consumption as necessitated by varying
levels of available power. If the HiveAP needs more power than is available, it fi rst di sables the ETH1 interface . If it
still needs more power , it switches from 3x3 MIMO (Multiple In, Multiple Out) to 2x3 (see "MIMO" on page 53). In rare
cases when further power conservation is necessary, the HiveAP then reduces the speed on ETH0 from 10/100/1000
Mbps to 10/100 Mbps. Finally, in the event that there is a problem with the PoE switch or Ethernet cable, the HiveAP
disables its wireless interfaces and returns its ETH0 and ETH1 interfaces to 10/100/1000 Mbps speeds. Through the
application of smart PoE, the HiveAP 340 can make power usage adjustments so that it can continue functioning
even when the available power level drops.
Aggregate and Redundant Interfaces
By default ETH0 and ETH1 act as two individual Ethernet interfaces. When both interfaces are connected to the
network and are in backhaul mode, the HiveAP transmits broadcast traffic only through ETH0. The HiveAP transmits
broadcast traffic through ETH1 only when ETH0 does not have network connectivity. When both Ethernet interfaces
are connected to the network and are in access mode, then the HiveAP transmits broadcast traffic through all the
access interfaces: ETH0, ETH1, and all wireless subinterfaces in access mode.
In addition to using ETH0 and ETH1 as individual interfaces, you can combine them into an aggregate interface
(agg0) to increase throughput, or combine them into a redundant interface (red0) to increase reliability. The logical
red0 and agg0 interfaces support all the settings that you can configure for Ethernet interfaces except those
pertaining to physical link characteristics such as link speed. See the sections below for configuration information.
Aggregate Interface
You can increase throughput onto the wired network by combining ETH0 and ETH1 into a single logically aggregated
interface called "agg0". The aggregate interface effectively doubles the bandwidth that each physical has when
used individually. In this configuration, both Ethernet ports actively forward traffic, the HiveAP applying an internal
scheduling mechanism based on the source MAC address of each packet to send traffic through the aggregate
member interfaces. To configure an aggregate interface, enter the following commands:
interface eth0 bind agg0
interface eth1 bind agg0
In addition to configuring the HiveAP, you must also configure the connecting switch to support EtherChannel. For
example, the following commands bind two physical Ethernet ports—0/1 and 0/2—to the logical interface
port-channel group 1 on a Cisco Catalyst 2900 switch running Cisco IOS 12.2:
Switch#conf t
Switch(config)#interface port-channel 1
Switch(config-if)#switchport mode access
Switch(config-if)#spanning-tree portfast
Switch(config-if)#exit
Switch(config)#interface fastEthernet 0/1
Switch(config-if)#switchport mode access
Switch(config-if)#channel-group 1 mode on
Switch(config-if)#spanning-tree portfast
Switch(config-if)#exit
Deployment Guide 49
Chapter 4 The HiveAP 340 Platform
Switch(config)#int fastEthernet 0/2
Switch(config-if)#switchport mode access
Switch(config-if)#channel-group 1 mode on
Switch(config-if)#spanning-tree portfast
Switch(config-if)#exit
Switch(config)#exit
Switch#wr mem
Finally, you must cable the Cisco switch and the HiveAP together: Cisco 0/1 to HiveAP eth0, and Cisco 0/2 to HiveAP
eth1.
Redundant Interface
If a single Ethernet link provides sufficient bandwidth and speed, such as a 1000 Mbps link, but you want to ensure
link redundancy, you can connect the two Ethernet ports to the same switch—or to two different switches—and
configure them to act as a redundant interface called "red0". In this mode, only one Ethernet interface is actively
forwarding traffic at any one time. If eth0 is active and eth1 is passive and eth0 loses its connection, the HiveAP
switches over to eth1. To configure a redundant interface, enter the following commands:
interface eth0 bind red0 primary
interface eth1 bind red0
The interface that you specify as primary is the one that the HiveAP uses when both interfaces have network
connectivity. Because the HiveAP uses eth0 as the primary interface, it is unnecessary to specify "primary" in the
first command above. However, it is included to make the role of eth0 as the primary interface obvious.
Note: No extra configuration is necessary on the connecting switch or switches to support a redundant interface.
Interface Selection for the Default Route
In cases where there are multiple active interfaces in backhaul mode, the HiveAP uses the following logic to choose
which interface to use in its default route:
• If there is an Ethernet interface and a wireless interface in backhaul mode, the HiveAP uses the Ethernet
interface in its default route.
• If there are multiple Ethernet interfaces in backhaul mode, the HiveAP chooses which one to use in its default
route in the following order:
• It uses red0 or agg0 if one of them has at least one member interface bound to it and its link state is UP.
• It uses ETH0 if neither red0 nor agg0 has any member interfaces and the link state for ETH0 is UP.
• It uses ETH1 if neither red0 nor agg0 has any member interfaces, the link state for ETH0 is DOWN, and the
link state for ETH1 is UP.
50 Aerohive
Console Port
Pin Signal Direction
1 RTS (Request to Send) Output, unused
2 DTR (Data Te rminal Ready) Output, unused
3 TXD (Transmitted Data) Output
4 Ground Ground
5 Ground Ground
6 RXD (Received Data) Input
7 DSR (Data Set Ready) Input, unused
8 CTS (Clear to Send) Input, unused
RJ-45 Console Port
(View of the console
port on the HiveAP)
Because this is a console port, only pins 3, 4, 5, and 6 are currently in use.
Console Port Pin Assignments
6 13457 28
Rollover Cable with
RJ-45 Connectors
RJ-45-to-Female DB-9 Adapter
Console Port
COM Port
(on Back Panel)
CONSOLE
Management System
HiveAP 340
Console Port
(HiveAP 340)
RJ-45-to-RJ-45
Rollover Cable
RJ-45-to-Female
DB-9 Adapter
Management
System
Signal RJ-45 Pin RJ-45 Pin RJ-45 Pin DB-9 Pin Signal
RTS (Request to Send) 1 8 1 8 CTS (unused)
DTR (Data Terminal Ready) 2 7 2 6 DSR (unused)
TXD (Transmitted Data) 3 6 3 2 RXD
Ground 4 5 4 5 Ground
Ground 5 4 5 5 Ground
RXD (Received Data) 6 3 6 3 TXD
DSR (Data Set Ready) 7 2 7 4 DTR (unused)
CTS (Clear to Send) 8 1 8 7 RTS (unused)
- - - - 9 RI (Ring Indicator, unused)
The pin-to-signal mapping in the RJ-45 console port is shown shown in Figure 3.
Figure 3 Console Port Pin Assignments
CONSOLE
HIVEAP 340 PRODUCT OVERVIEW
To make a serial connection between your management system and the HiveAP, you can use the console cable that
is available as an extra option. Insert the RJ-45 connector into the HiveAP 340 console port, and attach the DB-9
connector 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
(provided with Windows
Figure 3.
Figure 4 Wiring Details for Making a Serial Cable with an RJ-45-to-Female DB-9 Adapter
©
®
operating systems). If you want to make your own serial cable and adapter, refer to
(a free terminal emulator) or Hilgraeve Hyperterminal®
Deployment Guide 51
Chapter 4 The HiveAP 340 Platform
Status LEDs
The five status LEDs on the top of the HiveAP 340 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: Alarm indicating a firmware issue has occurred
• Pulsing amber: Firmware is being updated
• 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
WIFI0 and WIFI1
• 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 active
• Alternating green and amber: Wireless interface is in backhaul mode and is searching for other hive
members
Antennas
The HiveAP 340 can accept up to six detachable dipole an tennas . The three shorter antenn as are des igned for the 5
GHz band and have a 2-dBi gain. The three longer antennas are designed for the 2.4 GHz band and have a 4.9-dBi
gain. These antennas are omnidirectional, providing fairly equal coverage in all directions in a toroidal
(donut-shaped) pattern around each antenna (see Figure 4 on page 28). For greater coverage o n a h oriz onta l pla ne,
it is best to orient the antennas vertically. So that you can easily do that whether the HiveAP chassis is mounted
horizontally or vertically, the antennas hinge and swivel (see Figure 5 on page 53.)
Although hive members automatically adjust their signal strength according to their environments, you can resize
the area of coverage by increasing or decreasing the signal strength manually by entering the interface {
wifi0 | wifi1 } radio power <number> command, where <number> can be from 1 to 20 and represents
a value in dBm.
52 Aerohive
Figure 5 HiveAP 340 Antennas
The base of the antennas hinge up to 90 degrees so that you
can orient the antennas independently of the orientation of
the HiveAP chassis. The antennas also rotate in a full circle.
When mounting the HiveAP
340 on a ceiling, orient its
antennas downward.
When mounting the HiveAP
on a wall or post, fully extend
its antennas upward and
downward.
When mounting the HiveAP
above a ceiling or on a
horizontal beam, orient its
antennas upward.
Generally, orient the antennas vertically for
improved radio coverage, as shown here:
HIVEAP 340 PRODUCT OVERVIEW
2.4 GHz Antenna for
IEEE 802.11b/g/n
Length when fully
extended: 7 7/8” (20 cm)
5 GHz Antenna for IEEE
802.11a/n
Length when fully
extended: 5 15/16” (15 cm)
MIMO
MIMO (Multiple In, Multiple Out) is a major WLAN advancement introduced in the IEEE 802.11n standard in which
multiple RF links are formed on the same channel between the transmitter and receiver simultaneously. To
accomplish this, the transmitter separates a single data stream into multiple spatial s treams, one for ea ch RF ch ain
(an antenna + various digital signal processing modules linked to the antenna). The transmit antennas at the end of
each RF chain then transmit their spatial streams. The recipient’s receive antennas obtain streams from all the
transmit antennas. In fact, due to multipath, they receive multiple streams from each transmit antenna. The
receive antennas pass the spatial streams to the digital signal processors in their RF chains, which take the best data
from all the spatial streams and reassemble them into a single data stream once again (see Figure 6).
Figure 6 2x2 MIMO (2 Transmit Antennas x 2 Receive Antennas)
802.11n wireless client
with two antennas
HiveAP 340 using
two antennas
RF Chains RF Signals (Multipath)
Digital Signal
Processors
Data
Transmit
Antennas
Deployment Guide 53
RF Chains
Object
Receive
Antennas
Digital Signal
Processors
Reassembled
Data
Chapter 4 The HiveAP 340 Platform
PWR
ETH1
ETH0
WIFI1
WIFI0
Radio 1
RF 802.11b/g/n
2.4 GHz
Radio 2
RF 802.11a/n
5 GHz
2.4 GHz (A)
2.4 GHz (B)
2.4 GHz (C)
5 GHz (A)
5 GHz (B)
5 GHz (C)
RP-SMA
Connectors
RP-SMA
Connectors
Cut-away view of the HiveAP 340 to show the relationship of the antennas and the two internal radios
In previous 802.11 standards, access points and clients each employed a single set of components, or RF chain, for
transmitting or receiving. Although two antennas are often used for diversity, only the one with the best
signal-to-noise ratio is used at any given moment, and that antenna makes use of the single RF chain while the other
antenna remains inactive. A significant improvement that MIMO introduces is to permit each antenna to have its
own RF chain and for all antennas to function simultaneously. For the HiveAP 340, you can connect up to three
antennas per radio and configure the radio to use two or three transmit chains and two or three receive chains.
1
Using two or three transmit and receive chains simultaneously increases the amount of data that can flow across the
WLAN and accelerates the processing of that data at each end of the wireless link.
Another major aspect of MIMO is how it turns multipath signals from a curse to a boon. As a radio signal moves
through space, some objects reflect it, others interfere with it, and still others absorb it. The receiver can end up
receiving multiple copies of the original signal, all kind of muddled together. However, the digital signal processors
in the multiple receive chains are able to combine their pro cessing efforts to sort thro ugh all the received data and
reconstruct the original message. Furthermore, because the transmitter makes use of multiple RF chains, there is
an even richer supply of signals for the receive chains to use in their processing. To set the transmit and receive RF
chains for a radio profile, enter the following commands:
radio profile <name> transmit-chain { 2 | 3 }
radio profile <name> receive-chain { 2 | 3 }
There are two sets of antennas—three antennas per set—that operate concurrently in two different frequency
ranges: 2.4 GHz (IEEE 802.11b/g/n) and 5 GHz (IEEE 802.11a/n). Using two different frequency ranges reduces the
probability of interference that can occur when numerous channels operate within the same range. Conceptually,
the relationship of antennas and radios is shown in Figure 7.
Figure 7 Antennas and Radios
\
The wifi0 interface links to radio 1 (frequency range = 2.4 GHz for IEEE 802.11b/g), and the wifi1 interface links to
radio 2 (frequency range = 5 GHz for IEEE 802.11a). These interface-to-radio relationships are permanent.
When deciding how many antennas to use, consider the types of wireless clients—802.11n only, 802.11g/n,
802.11b/g/n, or 802.11a/n—the area needing coverage, and the RF environment.
1. The convention for presenting the configuration of transmitting and receiving MIMO RF chains is TxR. For
example, a HiveAP 340 radio functioning in access mode might be configured to use two RF chains for
transmitting and three for receiving. In that case, its configuration can be presented as "2x3". In general, the
number of receive antennas is equal to or greater than the number of transmit antennas.
54 Aerohive
HIVEAP 340 PRODUCT OVERVIEW
Using MIMO with Legacy Clients
In addition to supporting up to 300-Mbps throughput per radio for 802.11n clients, MIMO (Multiple In, Multiple Out)
can improve the reliability and speed of legacy 802.11a/b/g client traffic. When an 802.11a/b/g access point does
not receive acknowledgement that a frame it sent was received, it resends that frame, possibly at a somewhat
lower transmission rate. If the access point must continue resending frames, it will continue lowering its
transmission rate. As a result, clients that could get 54-Mbps throughput in an interference-free environment might
have to drop to 48- or 36-Mbps speeds due to multipath interface. However, because MIMO technology makes better
use of multipath, an access point using MIMO can continue transmitting at 54 Mbps, or at least at a better rate than
it would in a pure 802.11a/b/g environment, thus improving the reliability and speed of 802.11a/b/g client traffic.
Although 802.11a/b/g client traffic can benefit somewhat from an 802.11n access point using MIMO, supporting such
legacy clients along with 802.11n clients can have a negative impact on 802.11n client traffic. Legacy clients take
longer to send the same amount of data as 802.11n clients. Consequently, legacy clients consume more airtime than
802.11n clients do, causing greater congestion in the WLAN and reducing 802.11n performance.
By default, the HiveAP 340 supports 802.11a/b/g clients. Yo u can restrict access only to clients using the IEEE
802.11n standard. By only allowing traffic from clients using 802.11n, you can increase the overall bandwidth
capacity of the access point so that there will not be an impact on 802.11n clients during times of network
congestion. To do that, enter the following command:
radio profile <string> 11n-clients-only
You can also deny access just to clients using the IEEE 802.11b standard, which has the slowest data rates of the
three legacy standards, while continuing to support 802.11a and 802.11g clients. To do that, enter the following
command:
no radio profile <string> allow-11b-clients
By blocking access to 802.11b clients, their slower data rates cannot clog the WLAN when the amount of wireless
traffic increases.
Deployment Guide 55
Chapter 4 The HiveAP 340 Platform
1
2
Press the track clips against the
ceiling track and swivel them until
they grip the edges of the track.
If necessary, slide one or both of
the clips along the track to position
them at the proper distance to fit
through the holes in the mounting
plate (2 1/4” or 7 cm).
Insert the mounting plate over the
bolts attached to the track clips,
and use the Keps nuts to fasten
the plate to the clips.
Use a wrench to tighten the nuts
firmly to the bolts and secure the
plate to the track.
3
Through the oblong opening in the
plate, cut or drill a hole in the ceiling
tile (not shown). Then pass one or
both Ethernet cables through the
hole, and if you plan to supply power
from an AC power source rather than
through PoE, pass the power cable
through as well.
Cut hole in ceiling tile and
feed cables through here.
Mounting Plate
Ceiling Track
Track Clip
(worms’s eye view with ceiling
tiles removed for clarity)
2 1/4 “ (7 cm)
MOUNTING THE HIVEAP 340
Using the mounting plate and track clips, you can mount the HiveAP 340 to the tracks of a dropped ceiling grid.
Using just the mounting plate, you can mount the HiveAP to any surface that can support its weight (3.3 lb., 1.5 kg).
Ceiling Mount
To mount the HiveAP 340 to a track in a dropped ceiling, you need the mounting plate, two track clips, and two K eps
nuts that ship as an option with the HiveAP 340. You also need a wrench and—most likely—a ladder.
Nudge the ceiling tiles slightly away from the track to clear some space. Attach the track clips to the ceiling track,
and then fasten the mounting plate to the clips, as shown in Figure 8. When you have the mounting plate in the
correct location, cut or drill a hole in the ceiling through which you can then pass the Ethernet and power cables.
Figure 8 Attaching the Track Clips and Mounting Plate to the Ceiling Track
Attach the HiveAP 340 to the mounting plate and connect the cables, as shown in Figure 9 on page 57.
Note: You can tie the cables to the tie points (small arched strips) on the mounting plate to prevent them from
being pulled out of their connections accidentally.
56 Aerohive
Figure 9 Attaching the HiveAP 340 to the Mounting Plate and Connecting Cables
With the HiveAP 340 upside
down, align its port side with
the edge of the plate.
Push the HiveAP 340 upward,
inserting the four tabs on the
plate into the four slots on the
HiveAP 340.
Slide the HiveAP 340 toward
the port panel, locking the tabs
inside the slots.
Connect the cables to
complete the installation.
4
6
7
5
Tab
inside
slot.
Tab
locked in
place.
Mounting Plate
HiveAP 340 (shown as transparent for clairty)
Tab
Slot
(side view)
Mounting Plate
HiveAP 340
Ceiling
Cables pass through the hole in
the mounting plate and ceiling
5 GHz (A)
5 GHz (B)5 GHz (C)
Rotate the
lock adapter
clockwise.
Insert a lock
through the
opening.
HiveAP 340
Mounting Plate
MOUNTING THE HIVEAP 340
When done, adjust the ceiling tiles back into their former position.
Locking the HiveAP 340
To lock the HiveAP 340 to the mounting plate, use either a Kensington lock or the lock adapter that is included with
the mounting kit and a small padlock (not included).
To use a Kensington lock, loop the cable attached to the lock around a secure object, insert the T-bar component of
the lock into the device lock slot on the HiveAP, and then turn the key to engage the lock mechanism.
To use the lock adapter :
1. Insert the T-shaped extension on the adapter into the device lock slot, and rotate it clockwise so that the
2. Link a padlock through the opening in the adapter and engage the lock t o secure the HiveAP 340 to the
curved section extends through the slot in the mounting plate (see Figure 10).
Figure 10 Locking the HiveAP 340 to the Mounting Plate
mounting plate. The opening is 1/8" (0.3 cm) in diameter at its narrowest.
Deployment Guide 57
Chapter 4 The HiveAP 340 Platform
Mounting Plate
HiveAP 340
Wall
Insert the tabs on the mounting plate
into the slots on the underside of the
HiveAP 340. Then push the HiveAP
340 downward to lock it in place.
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.
1
3
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.
HiveAP 340
2
Cut or drill a hole through one of the
openings in the mounting plate to
pass the cables through to the
HiveAP 340.
Connect the cables to the HiveAP 340.
Depending on the deployment, you might
connect one or two Ethernet cables and a
power cable.
4
(side view)
Surface Mount
You can use the mounting plate to attach the HiveAP 340 to any surface that supports its weight, and to which you
can screw or nail the plate. First, mount the plate to the surface. Then, through one of the two large openings in
the plate, make a hole in the wall so that you can pass the cables through to the HiveAP.
Note: You can tie the cables to the tie points on the mounting plate to prevent them from being pulled out of
their connections accidentally.
Finally, attach the device to the plate, and connect the cables, as shown in Figure 11.
Figure 11 Mounting the HiveAP on a Wall
58 Aerohive
Loading...