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.
Chapter 4 The HiveAP 340 Platform 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 in Table 1.
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.
Chapter 4 The HiveAP 340 Platform 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.
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 first disables 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).
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.
HIVEAP 340 PRODUCT OVERVIEW Console Port The pin-to-signal mapping in the RJ-45 console port is shown shown in Figure 3.
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.
HIVEAP 340 PRODUCT OVERVIEW Figure 5 HiveAP 340 Antennas Generally, orient the antennas vertically for improved radio coverage, as shown here: When mounting the HiveAP 340 on a ceiling, orient its antennas downward. 2.4 GHz Antenna for IEEE 802.11b/g/n 5 GHz Antenna for IEEE 802.
Chapter 4 The HiveAP 340 Platform 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.
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.
Chapter 4 The HiveAP 340 Platform 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 Keps nuts that ship as an option with the HiveAP 340.
MOUNTING THE HIVEAP 340 Figure 9 Attaching the HiveAP 340 to the Mounting Plate and Connecting Cables Mounting Plate HiveAP 340 (shown as transparent for clairty) (side view) 4 With the HiveAP 340 upside down, align its port side with the edge of the plate. Tab Slot 5 Push the HiveAP 340 upward, inserting the four tabs on the plate into the four slots on the HiveAP 340. 6 Slide the HiveAP 340 toward the port panel, locking the tabs inside the slots.
Chapter 4 The HiveAP 340 Platform 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.
DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS Understanding the range of specifications for the HiveAP 340 is necessary for optimal deployment and device operation. 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 ranges in which the device can operate.
Chapter 4 The HiveAP 340 Platform 60 Aerohive
Chapter 5 The HiveManager Platform The HiveManager Network Management System provides centralized configuration, monitoring, and reporting for multiple HiveAPs.
Chapter 5 The HiveManager Platform PRODUCT OVERVIEW The Aerohive HiveManager is a central management system for configuring and monitoring HiveAPs. You can see its hardware components in Figure 1 and read a description of each component in Table 1.
PRODUCT OVERVIEW Component Description USB Port The USB port is reserved for internal use. Status LEDs The status LEDs convey operational states for the system power and hard disk drive. For details, see "Status LEDs" on page 64. MGT and LAN Ethernet Ports The 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.
Chapter 5 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 Figure 3 to make your own serial cable.
RACK MOUNTING THE HIVEMANAGER RACK MOUNTING THE 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 Figure 1 on page 62). In this position, you can front mount the HiveManager as shown in Figure 5.
Chapter 5 The HiveManager Platform DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS Understanding the range of specifications for the HiveManager is necessary for optimal deployment and operation of the device. The following specifications describe the physical features and hardware components, the electrical requirements for the power supply and cord, and the temperature and humidity ranges in which the device can operate.
Chapter 6 The High Capacity HiveManager Platform The High Capacity HiveManager is a management system that provides centralized configuration, monitoring, and reporting for multiple HiveAPs.
Chapter 6 The High Capacity HiveManager Platform PRODUCT OVERVIEW The Aerohive High Capacity HiveManager is a central management system for configuring and monitoring HiveAPs. You can see its hardware components in Figure 1 and read a description of each component in Table 1.
PRODUCT OVERVIEW Component Description Console Port A 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 HiveManager and on the HiveAP (see "Ethernet and Console Ports" on page 26).
Chapter 6 The High Capacity HiveManager Platform RACK MOUNTING THE HIGH CAPACITY HIVEMANAGER Use the rack mounting kit to mount the High Capacity HiveManager in a standard 19" (48 cm) equipment rack.
RACK MOUNTING THE HIGH CAPACITY HIVEMANAGER Figure 3 Attaching the Chassis Rail to the HiveManager Place the slide stop against the front mounting bracket. Chassis Rail cross-head machine screws with 10-32 threads 3. Secure the other chassis rail to the other side of the HiveManager. 4. Use three slot-head screws to attach the rear mounting bracket to the outer slide.
Chapter 6 The High Capacity HiveManager Platform 7. From the front of the equipment rack, guide the chassis rails on the sides of the HiveManager into the inner slides. Then push the HiveManager into the rack until the front mounting brackets are flush against the front rack rails. 8. Using four screws—two for each of the front brackets—fasten the HiveManager to the equipment rack as shown in Figure 6.
REPLACING POWER SUPPLIES REPLACING POWER SUPPLIES The high capacity HiveManager has a pair of redundant, hot-swappable power supplies. If one of the power supplies fails, the other will continue to power the device. When a a power supply fails, a continuous beeping alarm sounds and the power LED glows amber. To replace the failed power supply, do the following: 1. Disconnect the failed power supply from the power source. 2. Lower the handle to a horizontal position. 3.
Chapter 6 The High Capacity HiveManager Platform REPLACING HARD DISK DRIVES To provide fault tolerance from disk errors and single disk failure, the high capacity HiveManager uses level 1 RAID (Redundant Array of Independent Drives) HDDs (hard disk drives). Each HDD holds identical data, the data that is written to one disk being mirrored to the other. The lower LEDs on the front of each HDD flash in unison to indicate that they are writing data to memory. The upper LEDs indicate that they have power.
DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS DEVICE, POWER, AND ENVIRONMENTAL SPECIFICATIONS Understanding the range of specifications for the high capacity HiveManager is necessary for the optimal deployment and operation of the device. The following specifications describe the physical features and hardware components, the electrical requirements for the power supply and cord, and the temperature and humidity ranges in which the device can operate.
Chapter 6 The High Capacity HiveManager Platform 76 Aerohive
Chapter 7 Using 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.
Chapter 7 Using HiveManager This chapter explains how to do the following basic tasks: • Use the console port to change the network settings for the MGT and LAN interfaces • Power on HiveManager and connect it to a network • Make an HTTPS connection from your management system to HiveManager and log in to the GUI It then introduces the HiveManager GUI and includes a summary of the configuration workflow.
INSTALLING AND CONNECTING TO THE HIVEMANAGER GUI INSTALLING AND CONNECTING TO THE HIVEMANAGER GUI To begin using the HiveManager GUI, you must first configure the MGT interface to be accessible on the network, cable HiveManager and your management system (that is, your computer) to the network, and then make an HTTP connection from your system to the MGT interface and download the GUI application. Note: HiveManager has two Ethernet interfaces—MGT and LAN.
Chapter 7 Using HiveManager • HiveAP management traffic for CAPWAP, SNMP monitoring and notifications, and SCP configuration, captive web portal file, and HiveOS firmware uploads to managed HiveAPs When you enable both interfaces, HiveManager management traffic uses the MGT interface while HiveAP management traffic uses the LAN interface, as shown in Figure 2. Figure 2 Using Both MGT and LAN Interfaces LAN 10.1.1.8/24 MGT 10.1.2.8/24 Router Switch 10.1.1.1 10.1.3.0/24 10.1.2.1 10.1.4.
INSTALLING AND CONNECTING TO THE HIVEMANAGER GUI Connecting to the GUI through 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 HTTPS connection to the IP address that you set for the MGT interface. 3. Open a web browser and enter the IP address of the MGT interface in the address field. For example, if you changed the IP address to 10.1.1.
Chapter 7 Using HiveManager INTRODUCTION TO THE HIVEMANAGER GUI Using the HiveManager GUI, you can set up the configurations needed to deploy, manage, and monitor large numbers of HiveAPs. The configuration workflow is described in "HiveManager Configuration Workflow" on page 85. The GUI consists of several important sections, which are shown in Figure 4. Figure 4 Important Sections of the HiveManager GUI Menu Bar: The items in the menu bar open the major sections of the GUI.
INTRODUCTION TO THE HIVEMANAGER GUI Cloning Configurations When you need to configure multiple similar objects, you can save time by configuring just the first object, cloning it, and then making slight modifications to the subsequent objects. With this approach, you can avoid re-entering repeated data. Figure 5 Cloning a Hive To clone an object, select it in an open window, and then click the Clone button. Retain the settings you want to keep, and modify those you want to change. 2. Click 1.
Chapter 7 Using HiveManager Sorting Displayed Data You can control how the GUI displays data in the main panel by clicking a column header. This causes the displayed content to reorder itself alphanumerically or chronologically in either ascending or descending order. Clicking the header a second time reverses the order in which the data is displayed.
HIVEMANAGER CONFIGURATION WORKFLOW HIVEMANAGER CONFIGURATION WORKFLOW Assuming that you have already installed your HiveAPs, uploaded maps (see "Setting Up Topology Maps" on page 91), accepted the HiveAPs for management, and decided on the features and settings you want to use, you are now ready to start configuring the HiveAPs through HiveManager1. You can configure numerous objects, some of which might need to reference other objects.
Chapter 7 Using HiveManager UPDATING SOFTWARE ON HIVEMANAGER You can update the software running on HiveManager from either a local directory on your management system or an SCP (Secure Copy) server. If you download an image and save it to a local directory, you can load it from there. If you save the image to an SCP server, you can direct HiveManager to log in and load it from a directory there. 1.
UPDATING HIVEOS FIRMWARE UPDATING HIVEOS FIRMWARE HiveManager makes it easy to update HiveOS firmware running on managed HiveAPs. First, you obtain new HiveAP firmware from Aerohive Support and upload it onto HiveManager. Then you push the firmware to the HiveAPs and activate it by rebooting them. Note: When upgrading both HiveManager software and HiveOS firmware, do so in this order: • Upgrade HiveManager (HiveManager can manage HiveAPs running the current version of HiveOS and also previous versions).
Chapter 7 Using HiveManager • Activate at next reboot: Select to load the software and not activate it. The loaded software gets activated the next time the HiveAP reboots. Note: When choosing which option to use, consider how HiveManager connects to the HiveAPs it is updating. See "Updating HiveAPs in a Mesh Environment". • Select the check box for each HiveAP whose software you want to update.
Chapter 8 HiveManager Configuration Examples The following examples in this chapter show how to install over 70 HiveAPs at three locations in a corporate network, use HiveManager to create configurations for them, and then push the configurations to them over the network.
