Aerohive Quickstart and Deployment Guide Supplement
Total Page:16
File Type:pdf, Size:1020Kb
Aerohive QuickStart and Deployment Guide Supplement Aerohive QuickStart and Deployment Guide Supplement | 2 About This Guide Whereas the various Aerohive AP and router QuickStarts and the Aerohive Deployment Guide explain how to deploy devices in typical network environments where they can receive their network settings through DHCP, this guide explains alternate ways to deploy APs, routers, and CVGs (Cloud VPN Gateways) under different circumstances. It also includes some commonly used CLI commands and deployment tips that might prove useful during the setup of your Aerohive products. This guide is intended as a resource for all Aerohive administrators to aid in the deployment of their Aerohive products. If you would like to see an explanation for anything that is not covered in this guide—or anywhere else in Aerohive product documentation—please contact [email protected]. We welcome your suggestions and will strive to provide the documentation you need to use Aerohive products more effectively. To register, get product documentation, and download software updates, visit www.aerohive.com/support. Copyright © 2012 Aerohive Networks, Inc. All rights reserved Aerohive Networks, Inc. 330 Gibraltar Drive Sunnyvale, CA 94089 P/N 330090-01, Rev. A To learn more about Aerohive products visit www.aerohive.com/techdocs Aerohive Networks, Inc. Aerohive QuickStart and Deployment Guide Supplement | 3 Contents AP Deployment in a Network without DHCP ................................................................................................................................. 4 Console Connection ...................................................................................................................................................................... 4 Virtual Access Console .................................................................................................................................................................. 5 Configuring Network and HiveManager Settings ..................................................................................................................... 5 Router Deployment in a Network without DHCP .......................................................................................................................... 7 Useful CLI Commands ....................................................................................................................................................................... 8 Deployment and Configuration Tips ............................................................................................................................................... 9 To learn more about Aerohive products visit www.aerohive.com/techdocs Aerohive Networks, Inc. Aerohive QuickStart and Deployment Guide Supplement | 4 AP Deployment in a Network without DHCP Although DHCP is commonly available in most networks, you might occasionally find it necessary to add APs to a network without it. For example, management networks sometimes use static IP addressing while their accompanying access networks provide addresses to clients dynamically. In such cases, the APs require static network settings while acting as DHCP servers to assign network settings dynamically to clients connected to them. After connecting an AP to a network and powering it on, its default behavior is to act as a DHCP client and try to get its network settings automatically from a DHCP server. However, if there is no DHCP service in that network, then you must access the CLI and define the network settings for the AP yourself. To configure static network settings for an Aerohive AP that is cabled to a network, follow either of the next two procedures to access the CLI. Console Connection One way to access the CLI is to use an RS-232 serial (or "null modem") cable, which is available from Aerohive as an optional accessory (AH-ACC-Serial-DB9) and make a physical connection from your management system to the AP. You might also need a DB9-to-USB adapter depending on the ports available on your management system. You also need a VT100 emulator on your management system. 1. Connect one end of the RS-232 serial cable to the serial port on your management system, or—with the aid of a DB9-to-USB adapter—to a USB port on your management system. 2. Connect the other end of the cable to the RJ-45 console port on the AP. 3. On your management system, run a VT100 terminal emulation program, such as Tera Term Pro© (a free terminal emulator). Use the following settings: Bits per second (baud rate): 9600 Data bits: 8 Parity: none Stop bits: 1 Flow control: none For APs set with "FCC" as the region code, the Initial CLI Configuration Wizard appears. For APs set with "world" as the region code, a prompt appears to set the country code for the location where you intend to deploy the AP. To set the country code, enter the boot-param country-code <number> command, in which <number> is the appropriate country code number. For a list of country codes, see the HiveManager GUI: Click Monitor > All Devices > Update > Update Country Code, and then view the New Country Code drop-down list. 4. Because you do not need to configure all the settings presented in the wizard, press N to cancel it. The login prompt appears. 5. Log in using the default login name admin and password aerohive. To learn more about Aerohive products visit www.aerohive.com/techdocs Aerohive Networks, Inc. Aerohive QuickStart and Deployment Guide Supplement | 5 Virtual Access Console Another way to access the CLI is to use the virtual access console. This is a way of accessing the CLI on an Aerohive AP wirelessly through a special SSID that the AP, by default, automatically activates for administrative access when its mgt0 interface has no configuration. This is a convenient approach to take if the AP is already mounted in a location that is difficult to access, such as on a ceiling or high wall. The default virtual access console SSID name is “<ap-hostname>_ac”. The default host name of an AP consists of "AH-" plus the last six digits of its MAC address; for example, AH-123456. In this case, the name of the default virtual access console SSID would be "AH-123456_ac". By default, this SSID uses aerohive as the PSK (preshared key) for authenticating user access. To access the virtual access console, do the following: 1. Using your wireless client, scan for wireless networks. If you are within range, an SSID such as "AH-123456_ac" appears. 2. Select that SSID, and when prompted to enter a network key, type aerohive, and then click Connect. 3. Check the IP address of the default gateway that the DHCP server for the wireless interface on the AP assigns your client. Then make an SSH or Telnet connection to the AP at that IP address. (Note that the Telnet connection is protected by WPA2 security mechanisms.) When prompted to enter your credentials, enter the default login name admin and password aerohive. Configuring Network and HiveManager Settings After connecting to the CLI, you can now configure static network settings (IP address, netmask, default route, and DNS server) for the AP and the IP address or domain name of the HiveManager to which you want the AP to connect so that you can manage it. 1. If you are accessing the CLI wirelessly over a virtual access console SSID, temporarily change its mode from “auto” to “enable”. When it is in automatic mode, the AP enables the virtual access console only when the mgt0 interface does not have an IP address. As soon as you assign it a static IP address, the AP will automatically close the virtual access console, which will prevent you from entering other commands, such as its default route. To keep the virtual access console SSID up indefinitely so that you can finish configuring the AP, enter the following command: access-console mode enable 2. Enter the following commands to disable the DHCP client running on the mgt0 interface and set a static IP address and netmask for it. You then define a default route and the IP address of its primary DNS server: no interface mgt0 dhcp client interface mgt0 ip <ip_addr>/<mask> ip route default gateway <ip_addr> dns server-ip <ip_addr> 3. Enter the next command to set the IP address or domain name of the HiveManager that you want the AP to contact for further management: capwap client server name { <ip_addr> | <domain_name> } 4. To test the accessibility of the default gateway for the AP, ping its IP address: ping <ip_addr> 5. To test domain name resolution, ping a domain name, for example: ping www.aerohive.com To learn more about Aerohive products visit www.aerohive.com/techdocs Aerohive Networks, Inc. Aerohive QuickStart and Deployment Guide Supplement | 6 6. To check that the AP has a secure CAPWAP connection to HiveManager, enter show capwap client 7. To return the virtual access console to automatic mode, enter the following command: access-console mode auto When you do, the AP terminates the current access console SSID as well as your Telnet or SSH session. If you want to keep the virtual access console SSID available even when the AP has an IP address for its mgt0 interface, then leave the mode as “enable” and change the PSK for the SSID so it no longer uses the default text string (aerohive). You can do this by entering the following command: access-console security protocol-suite wpa2-aes-psk ascii-key <string> The PSK can be from 8 to 63 characters long. To help guard against anyone guessing the PSK, use a fairly long string with a combination of numerals, special