HPE - c05321602 - ArubaOS 6.2 - Quick Start Guide
HPE - c05321602 - ArubaOS 6.2 - Quick Start Guide
ArubaOS 6.2
Quick Start Guide
This document describes the initial setup of an Aruba user-centric network that consists of an Aruba
controller and Aruba Access Points (APs). The installation consists of the following steps:
1. Launch the WebUI or Console Setup Wizard to configure the controller.
2. Connect the controller to the wired network.
3. Configure the controller to allow APs, when installed and powered on, to able to locate and connect to
the controller. If you are configuring mesh, define the mesh cluster profile, mesh radio profile, before
installing APs in a mesh networking environment.
4. Install and connect your APs to the network.
Before you begin, read the ArubaOS End User License Agreement and review the contents of your
controller shipment to ensure that you have received the following:
Aruba controller with appropriate power cord and accessories
The ArubaOS Quick Start Guide included with your controller.
The ArubaOS End User License Agreement
The default certificate installed in the controller does not guarantee security in production networks. Aruba
strongly recommends that you replace the default certificate with a custom certificate issued for your site or
domain by a trusted Certificate Authority. See the ArubaOS User Guide for more information about certificates.
7. The initial window of the Mobility Controller Setup Wizard asks you to select one of the following
deployment modes. Select Standalone, Master, Local or Remote Node, then click Continue. If you
are configuring a Remote Node controller, refer to the ArubaOS User Guide for details on using the
Remote Node Configuration Wizard.
Standalone: This is the only controller on the network.
Master: This controller will manage other controllers on the network.
Local: This controller will be managed by a master controller.
Remote Node: This controller will act as a remote node and get its local and global configuration
and license limits from a master controller called a remote node controller (RNC).
8. If you selected Standalone or Master in the step above, you will be prompted to select the Campus
WLAN or Remote Access Points deployment mode. The Remote Access Points deployment mode
allows you to configure additional settings specific to remote APs.
9. Enter the information described in Table 1, and, if desired, the optional configuration information
described in "Optional Information" on page 3.
Requirement Description
System Name A user-defined name by which the controller will be referenced. You can specify a name of up
to 63 characters.
Country Code The country in which the controller will operate. The country code determines the 802.11
wireless transmission spectrum. You cannot change the country code for controllers
designated for certain countries, such as the U.S. or Israel. Improper country code
assignment can disrupt wireless transmissions. Most countries impose penalties and
sanctions for operators of wireless networks with devices set to improper country codes.
Admin Password Password of up to 32 characters for the admin user to log in to the controller.
Enable Mode Password of up to 15 characters for the admin user to access the Enable mode in the CLI.
Password
Date and Time You can either manually set the date, time, and GMT time zone or specify the IP address of an
NTP server from which the controller will obtain its date and time settings.
Connectivity Enter the controller IP address and default gateway.The gateway is usually the IP address of
Settings the interface on the upstream switch or router to which you will connect the controller. The
default gateway and the VLAN 1 IP address need to be in the same network.
Requirement Description
Authentication If you are configuring a master or local controller that uses pre-shared key authentication,
Settings enter the pre-shared key.
If you are configuring a master controller to use certificate authentication, enter the MAC
addresses of the local controllers.
If you are configuring a local controller to use certificate authentication, enter the MAC
address of the master controller.
Optional Information
The Setup Wizard to also allows you to:
Create virtual local area networks (VLANs) into which wireless users are placed after authentication
Modify default port settings
Enable the Uplink firewall, and configure the following Management and Aruba interface types
Management Interfaces: SSH, HTTPS, SNMP and DHCP.
Aruba Interfaces: RAP, VIA, VIA Mac and Site-to-Site VPN
Install licenses for ArubaOS software modules
Configure internal and guest WLANs
Specify IP address pools to define the inner IP addresses assigned to VPN clients and access points
connecting to a local controller, or to a standalone or master controller with remote APs.
If you plan on adding controller licenses or configuring additional VLANs, WLANs, or port settings on your
controller, make a note of the desired licenses or settings before you launch the Setup wizard.
These optional configuration settings cannot be configured when running initial setup on a serial port connection.
2. Connect your terminal or PC/workstation to the serial port on the controller using an RS-232 serial
cable. All accessory kits shipped with Aruba controllers contain an RJ-45 cable and DB-9 to RJ-45
adapter. You may need to provide a USB adapter to connect the serial cable to your PC.
3. Boot up the Aruba controller. After the controller has booted up, you should see a screen similar to the
following:
4. The Serial Port Configuration Dialog displays the configuration prompts described in Table 3. The
prompts may vary, depending upon the switch role you choose. Enter the required information at each
prompt, then press Enter to continue to the next question.
Enter System Name Enter a name for the controller, or press Enter to use the default system name. You
can specify a name of up to 63 characters.
Enter VLAN 1 interface IP The controller takes its IP address from VLAN 1 and uses this IP address to
address communicate with other controllers and with APs. Enter the VLAN 1 interface IP
address, or press Enter without specifying an IP address to use the default address
172.16.0.254.
Enter VLAN 1 interface Enter the VLAN 1 interface IP subnet mask, or press Enter without specifying an IP
subnet mask address to use the default address 255.255.255.0.
Enter IP Default gateway This is usually the IP address of the interface on the upstream switch or router to
which you will connect the controller. The default gateway and the VLAN 1 IP
address need to be in the same network. To continue without specifying an IP
gateway, press Enter.
(For US controllers only) If your controller has a country code that restricts its usage, enter yes to confirm this
This controller is restricted code.
to Country code US for
United States, please
confirm (yes|no)
Enter Time Zone Enter the time zone for the controller, or press Enter to select the default time zone.
Enter Time in UTC Enter the current time in UTC format, or press Enter to select the default time.
Enter Date (MM/DD/YYYY) Enter the current date, or press Enter to select the default date.
Enter Password for admin Enter a password to allow the admin user to login to the controller WebUI, CLI and
login (up to 32 chars) console interfaces. This password can be up to 32 alphanumeric characters long.
Enter Password for enable Enter a password for the admin user to access Enable mode in the controller WebUI,
mode (up to 15 chars CLI and console interfaces. This password can be up to 15 alphanumeric
characters.
Do you wish to shutdown all Enter yes to shut down all ethernet ports on the controller, or press Enter to allow all
the ports (yes|no)? [no] ports to remain active.
5. At the end of the Initial Setup, you are asked to review and confirm your configuration changes. Enter y
to accept the changes. The controller reboots.
If you want to complete optional configuration options (e.g. disabling spanning tree or installing software licenses)
before connecting the controller to the network, refer to the ArubaOS User Guide for additional information on
controller configuration.
Controller Discovery
An Aruba AP can discover the IP address of the controller in one of several ways. The Aruba Discovery
Protocol (ADP) is enabled by default on all Aruba APs and controllers. If all APs and controllers are
connected to the same Layer-2 network, APs will use ADP to discover their controllers. If the devices are on
different networks, you must configure the AP to use a Layer-3 compatible discovery mechanism such as
DNS, DHCP, or IGMP forwarding after installing the AP on the network. For details, refer to the ArubaOS
User Guide.
With ADP, APs send out periodic multicast and broadcast queries to locate the master controller. If the APs
are in the same broadcast domain as the master controller, the controller automatically responds to the
APs’ queries with its IP address. If the APs are not in the same broadcast domain as the master controller,
you need to enable multicast on the network. If multicast is not an option, then the APs can be configured to
use DNS or DHCP based provisioning to contact the controller.
The information in this section applies only if you are configuring and deploying APs in a mesh networking
environment. If you are not, proceed to "Install the APs" on page 7.
Before you install APs in a mesh networking environment, you must do the following:
Define and configure the mesh cluster profile and mesh radio profile before configuring an AP to
operate as a mesh node. An AP configured for mesh is also known as a mesh node.
Provision one of the following mesh roles on the AP:
Mesh portal: The gateway between the wireless mesh network and the enterprise wired LAN.
Mesh point: APs that can provide traditional Aruba WLAN services (such as client connectivity,
intrusion detection system (IDS) capabilities, user roles association, LAN-to-LAN bridging, and
Quality of Service (QoS) for LAN-to-mesh communication) to clients on one radio and perform mesh
backhaul/network connectivity on the other radio. Mesh points provides LAN-to-LAN bridging
through their Ethernet interfaces. It can now provide backhaul and access BSSIDs on the same radio.
For detailed provisioning guidelines, caveats, and instructions, see the “Secure Enterprise Mesh” chapter in
the ArubaOS User Guide.
Contacting Support
Table 4 Web Sites and Emails
Web Site
Support Emails
EMEA emea_support@arubanetworks.com
Telephone Numbers
Support
Copyright
© 2012 Aruba Networks, Inc. Aruba Networks trademarks include , Aruba Networks®, Aruba
Wireless Networks , the registered Aruba the Mobile Edge Company logo, Aruba Mobility Management System®,
®
Mobile Edge Architecture®, People Move. Networks Must Follow®, RFProtect®, Green Island®. All rights reserved. All
other trademarks are the property of their respective owners.
Open Source Code
Certain Aruba products include Open Source software code developed by third parties, including software code subject
to the GNU General Public License (GPL), GNU Lesser General Public License (LGPL), or other Open Source Licenses.
The Open Source code used can be found at this site:
http://www.arubanetworks.com/open_source
Legal Notice
The use of Aruba Networks, Inc. switching platforms and software, by all individuals or corporations, to terminate other
vendors’ VPN client devices constitutes complete acceptance of liability by that individual or corporation for this action
and indemnifies, in full, Aruba Networks, Inc. from any and all legal actions that might be taken against it with respect
to infringement of copyright on behalf of those vendors.
Warranty
This hardware product is protected by the standard Aruba warranty of one year parts/labor. For more information, refer
to the ARUBACARE SERVICE AND SUPPORT TERMS AND CONDITIONS.
Altering this device (such as painting it) voids the warranty.
.
www.arubanetworks.com
1344 Crossman Avenue
Sunnyvale, California 94089
Phone: 408.227.4500
© 2012 Aruba Networks, Inc. All rights reserved. Fax 408.227.4550