All rights reserved. Specifications in this manual are subject to change without notice.
Originated in the USA. 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.
Dell PowerConnect W-Series ArubaOS 6.1 | User Guide0510845-01 | June 2011
Page 3
Contents
About this Guide ..................................................................................................................................................... 45
Installing VIA ...................................................................................................................................816
Using VIA ......................................................................................................................................... 816
Figure 16Access Point Editor..........................................................................................................................93
Figure 41Working of RMP.............................................................................................................................. 257
Figure 42Provisioning an AP as a Remote Mesh Portal...........................................................................258
Figure 43Server Group ...................................................................................................................................264
Figure 44IP-Address parameter in the local database............................................................................. 271
Dell PowerConnect W-Series ArubaOS 6.1 | User Guide | 35
Page 36
Figure 45IP-Address parameter in the RAP Whitelist .............................................................................. 271
Figure 46Domain-Based Server Selection Example .................................................................................275
Figure 47802.1x Authentication with RADIUS Server ............................................................................... 287
Figure 48802.1x Authentication with Termination on Controller .............................................................287
Figure 49Upload a certificate........................................................................................................................ 316
Figure 104usb test extended. ..........................................................................................................................512
Figure 105show dialer group example .......................................................................................................... 513
Figure 106W-600 Series Topology................................................................................................................. 518
Figure 109Add an OSPF Area..........................................................................................................................529
Figure 147Devices vs Channel........................................................................................................................634
Figure 207Networks to Access....................................................................................................................... 795
Figure 208Wireless Network Association ................................................................................................... 796
Table 2Contacting Dell Support .................................................................................................................. 47
Table 3Classifying Trusted and Untrusted Traffic.................................................................................... 64
Table 4Planning Worksheet - Building Dimensions ................................................................................ 78
Table 5Planning Worksheet - AP Desired Rates (2.4 GHz Radio Properties)......................................79
Table 6Planning Worksheet - AM Desired Rates .................................................................................... 79
Table 7Definition of Campus List Buttons ................................................................................................. 80
Table 8Building List Buttons ........................................................................................................................81
Table 9New Building Specifications Parameters ....................................................................................83
Table 19Sample Building ..............................................................................................................................101
Table 20Create a Building ............................................................................................................................ 102
Table 21AP Configuration Function Overview .......................................................................................... 107
Table 22AP System Profile Configuration..................................................................................................128
Table 144Usage per License..........................................................................................................................653
Dell PowerConnect W-Series ArubaOS 6.1 | User Guide | 43
Page 44
Table 145MIPS Controller AP Capacity ....................................................................................................... 654
Table 146IPv6 APs Support Matrix ............................................................................................................... 661
Table 150Default Voice Net Services and Ports ........................................................................................ 676
Table 151Services for ALGs ...........................................................................................................................677
Table 152Other Mandatory Services for the ALGs .................................................................................... 678
Table 153VoIP Call Admission Control Configuration Parameters .......................................................... 688
Table 154WMM Access Category to 802.1p Priority Mapping ................................................................ 690
Table 155WMM Access Category to DSCP Mappings ............................................................................. 691
Table 156WMM Access Categories and 802.1p Tags ...............................................................................692
Table 157EDCA Parameters Station and EDCA Parameters AP Profile Settings .................................693
Table 158Ports used by the Apple Facetime Application ......................................................................... 695
Table 159Examples of Dial Plans .................................................................................................................. 704
Table 160Character-matching operators in regular expressions ........................................................... 742
Table 176Provision using Static IP ............................................................................................................... 820
Table 177Provision using PPPoE Connection ............................................................................................. 821
Table 178List of acronyms.............................................................................................................................. 825
Table 179List of terms ..................................................................................................................................... 830
44 | Dell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 45
About this Guide
This User Guide describes the features supported by ArubaOS and provides instructions and examples for
configuring controllers and Access Points (APs). This chapter covers:
“Audience” on page45
“Fundamentals” on page45
“Related Documents” on page46
“Conventions” on page46
“Contacting Support” on page47
Audience
This guide is intended for system administrators responsible for configuring and maintaining wireless networks
and assumes you are knowledgeable in Layer 2 and Layer 3 networking technologies.
Fundamentals
Throughout this document reference are made to controllers; controllers categories are based on architecture:
MIPS Controllers—W-6000, W-3000 Series, W-600 Series
Configuring your controller and AP is accomplished using either the Web User Interface (WebUI) or the
command line interface (CLI).
WebUI
Each controller supports up to 22 simultaneous WebUI connections. The WebUI is accessible through a
standard Web browser from a remote management console or workstation. The WebUI includes configuration
wizards that step you through easy-to-follow configuration tasks. The wizards are:
LAN Wizard—creating and configuring new WLAN(s) associated with the “default” ap-group
License Wizard—installation and activation of software licenses
In addition to the wizards, the WebUI includes a Dashboard monitoring feature that provides enhanced visibility
into your wireless network’s performance and usage. This allows you to easily locate and diagnose WLAN issues.
For details on the WebUI Dashboard, see Chapter 13, “Dashboard Monitoring” on page339.
CLI
The CLI is a text-based interface accessible from a local console connected to the serial port on the controller or
through a Telnet or Secure Shell (SSH) session.
NOTE: By default, you access the CLI from the serial port or from an SSH session. You must explicitly enable Telnet on your
controller in order to access the CLI via a Telnet session.
Dell PowerConnect W-Series ArubaOS 6.1 | User Guide About this Guide | 45
Page 46
When entering commands remember that:
commands are not case sensitive
the space bar will complete your partial keyword
the backspace key will erase your entry one letter at a time
the question mark ( ? ) will list available commands and options
Related Documents
The following items are part of the complete documentation for the Dell user-centric network:
Dell PowerConnect W-Series Command Line Reference Guide
Dell PowerConnect W-Series MIB Reference Guide
Release Notes
Conventions
The following conventions are used throughout this manual to emphasize important concepts:
Table 1 Typographical Conventions
Type StyleDescription
ItalicsThis style is used to emphasize important terms and to mark the titles of books.
System itemsThis fixed-width font depicts the following:
Sample screen output
System prompts
Filenames, software devices, and specific commands when mentioned in the text
CommandsIn the command examples, this bold font depicts text that you must type exactly as shown.
<Arguments>In the command examples, italicized text within angle brackets represents items that you
[Optional]In the command examples, items enclosed in brackets are optional. Do not type the brackets.
{Item A | Item B}In the command examples, items within curled braces and separated by a vertical bar
The following informational icons are used throughout this guide:
should replace with information appropriate to your specific situation. For example:
# send <text message>
In this example, you would type “send” at the system prompt exactly as shown, followed by
the text of the message you wish to send. Do not type the angle brackets.
represent the available choices. Enter only one choice. Do not type the braces or bars.
NOTE: Indicates helpful suggestions, pertinent information, and important things to remember.
CAUTION: Indicates a risk of damage to your hardware or loss of data.
46 | About this GuideDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 47
WARNING: Indicates a risk of personal injury or death.
Contacting Support
Table 2 Contacting Dell Support
Web Site
Main Websitedell.com
Support Websitesupport.dell.com
Documentation Websitesupport.dell.com/manuals
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideAbout this Guide | 47
Page 48
48 | About this GuideDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 49
Chapter 1
The Basic User-Centric Networks
This chapter describes how to connect an Dell controller and Dell APs to your wired network. After completing
the tasks described in this chapter, see “Access Points” on page107 for information on configuring APs.
This chapter describes the following topics:
“Configuring the User-Centric Network” on page49
“Deployment and Configuration Tasks” on page49
“Configuring the Controller” on page52
“Configuring a VLAN for Network Connection” on page53
“Additional Configuration” on page57
Configuring the User-Centric Network
Configuring your controller and AP is done through either the Web User Interface (WebUI) or the command
line interface (CLI).
WebUI is accessible through a standard Web browser from a remote management console or workstation.
The WebUI includes configuration wizards that step you through easy-to-follow configuration tasks. Each
wizard has embedded online help. The wizards are:
AP Wizard—basic AP configuration s including LAN, Remote, LAN Mesh and Remote Mesh deployment
scenarios
Controller Wizard—basic controller configuration including system settings, Control Plane security,
cluster settings and licenses
WLAN/LAN Wizard—creating and configuring new WLANs and LANs associated with the “default” ap-
group. Includes campus only and remote networking.
License Wizard—installation and activation of software licenses (see Chapter 34 on page651)
NOTE: Clicking Cancel from the Wizards return you to where you launched the wizard. Any configuration changes you entered are
not saved.
The command line interface (CLI) allows you to configure and manage controllers. The CLI is accessible
from a local console connected to the serial port on the controller or through a Telnet or Secure Shell (SSH)
session from a remote management console or workstation.
NOTE: By default, you can only access the CLI from the serial port or from an SSH session. To use the CLI in a Telnet session, you
must explicitly enable Telnet on the controller.
Deployment and Configuration Tasks
This section describes typical deployment scenarios and the tasks you must perform in connecting an Dell
controller and Dell APs to your wired network. For details on performing the tasks mentioned in these scenarios,
see the remaining sections within this chapter.
Dell PowerConnect W-Series ArubaOS 6.1 | User Guide The Basic User-Centric Networks | 49
Page 50
Deployment Scenario #1
Router is Default Gateway for
controller and clients
In this deployment scenario, the APs and controller are on the same subnetwork and will use IP addresses
assigned to the subnetwork. There are no routers between the APs and the controller. APs can be physically
connected directly to the controller. The uplink port on the controller is connected to a layer-2 switch or router.
For this scenario, you must perform the following tasks:
1. Run the initial setup wizard.
Set the IP address of VLAN 1.
Set the default gateway to the IP address of the interface of the upstream router to which you will connect
the controller.
2. Connect the uplink port on the controller to the switch or router interface. By default, all ports on the
controller are access ports and will carry traffic for a single VLAN.
3. Deploy APs. The APs will use the Aruba Discovery Protocol (ADP) to locate the controller.
Configure the SSID(s) with VLAN 1 as the assigned VLAN for all users.
Deployment Scenario #2
Floor 3 subnet
Floor 2 subnet
Floor 1 subnet
Controller is default
gateway for clients
Data Center
In this deployment scenario, the APs and the controller are on different subnetworks and the APs are on multiple
subnetworks. The controller acts as a router for the wireless subnetworks (the controller is the default gateway for
the wireless clients). The uplink port on the controller is connected to a layer-2 switch or router; this port is an
access port in VLAN 1.
50 | The Basic User-Centric NetworksDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 51
For this scenario, you must perform the following tasks:
1. Run the initial setup wizard.
Set the IP address for VLAN 1.
Set the default gateway to the IP address of the interface of the upstream router to which you will connect
the controller.
2. Connect the uplink port on the controller to the switch or router interface.
3. Deploy APs. The APs will use DNS or DHCP to locate the controller.
4. Configure VLANs for the wireless subnetworks on the controller.
5. Configure SSIDs with the VLANs assigned for each wireless subnetwork.
NOTE: Each wireless client VLAN must be configured on the controller with an IP address. On the uplink switch or router, you must
configure static routes for each client VLAN, with the controller’s VLAN 1 IP address as the next hop.
Deployment Scenario #3
Floor 3 subnet
Floor 2 subnet
Floor 1 subnet
Trunk port carries
client traffic
Data Center
Router is default gateway
for controller and clients
In this deployment scenario, the APs and the controller are on different subnetworks and the APs are on multiple
subnetworks. There are routers between the APs and the controller. The controller is connected to a layer-2
switch or router through a trunk port that carries traffic for all wireless client VLANs. An upstream router
functions as the default gateway for the wireless users.
NOTE: This deployment scenario does not use VLAN 1 to connect to the layer-2 switch or router through the trunk port. The initial
setup prompts you for the IP address and default gateway for VLAN 1; use the default values. In later steps, you configure the
appropriate VLAN to connect to the switch or router as well as the default gateway.
For this scenario, you must perform the following tasks:
1. Run the initial setup.
Use the default IP address for VLAN 1. Since VLAN 1 is not used to connect to the layer-2 switch or router
through the trunk port, you must configure the appropriate VLAN in a later step.
Do not specify a default gateway (use the default “none”). In a later step, you configure the default
gateway.
2. Create a VLAN that has the same VLAN ID as the VLAN on the switch or router to which you will connect
the controller. Add the uplink port on the controller to this VLAN and configure the port as a trunk port.
3. Add client VLANs to the trunk port.
4. Configure the default gateway on the controller. This gateway is the IP address of the router to which you will
connect the controller.
5. Configure the loopback interface for the controller.
6. Connect the uplink port on the controller to the switch or router interface.
7. Deploy APs. The APs will use DNS or DHCP to locate the controller.
8. Now configure VLANs on the controller for the wireless client subnetworks and configure SSIDs with the
VLANs assigned for each wireless subnetwork.
Configuring the Controller
The tasks in deploying a basic user-centric network fall into two main areas:
Configuring and connecting the controller to the wired network (described in this section)
Deploying APs (described later in this section)
To connect the controller to the wired network:
1. Run the initial setup to configure administrative information for the controller.
Initial setup can be done using the browser-based Setup Wizard or by accessing the initial setup dialog via a
serial port connection. Both methods are described in the Dell PowerConnect W-Series Quick Start Guide and
are referred to throughout this chapter as “initial setup.”
2. (Deployment #3) Configure a VLAN to connect the controller to your network. You do not need to perform
this step if you are using VLAN 1 to connect the controller to the wired network.
3. (Optional) Configure a loopback address for the controller. You do not need to perform this step if you are
using the VLAN 1 IP address as the controller’s IP address. Disable spanning tree on the controller if
necessary.
4. Configure the system clock.
5. (Optional) Install licenses; see Chapter 34, “Software Licenses” on page651.
6. Connect the ports on the controller to your network.
This section describes the steps in detail.
Running the Initial Setup
When you connect to the controller for the first time using either a serial console or a Web browser, the initial
setup requires you to set the role (master or local) for the controller and passwords for administrator and
configuration access.
NOTE: Do not connect the controller to your network when running the initial setup. The factory-default controller boots up with a
default IP address and both DHCP server and spanning tree functions are not enabled. Once you have completed the initial setup,
you can use either the CLI or WebUI for further configuration before connecting the controller to your network.
52 | The Basic User-Centric NetworksDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 53
The initial setup might require that you specify the country code for the country in which the controller will
operate; this sets the regulatory domain for the radio frequencies that the APs use.
NOTE: You cannot change the country code for controllers designated for certain countries, such as the U.S.
Improper country code assignment can disrupt wireless transmissions. Many countries impose penalties and sanctions for
operators of wireless networks with devices set to improper country codes.
If none of the channels supported by the AP you are provisioning have received regulatory approval by the country whose country
code you selected, the AP will revert to Air Monitor mode.
The initial setup requires that you configure an IP address for the VLAN 1 interface, which you can use to access
and configure the controller remotely via an SSH or WebUI session. Configuring an IP address for the VLAN 1
interface ensures that there is an IP address and default gateway assigned to the controller upon completion of
the initial setup.
Connecting to the Controller after Initial Setup
After you complete the initial setup, the controller reboots using the new configuration. (See the Dell
PowerConnect W-Series Quick Start Guide for information about using the initial setup.) You can then connect to
and configure the controller in several ways using the administrator password you entered during the initial setup:
You can continue to use the connection to the serial port on the controller to enter the command line
interface (CLI). (See Chapter 32, “Management Access” for information on how to access the CLI and enter
configuration commands.)
You can connect an Ethernet cable from a PC to an Ethernet port on the controller. You can then use one of
the following access methods:
Use the VLAN 1 IP address to start an SSH session where you can enter CLI commands.
Enter the VLAN 1 IP address in a browser window to start the WebUI.
WebUi Wizards.
NOTE: This chapter and the user guide in general focus on CLI and standard WebUI configuration examples. However, basic
controller configuration and WLAN/LAN creation can be completed using the alternative wizards from within the WebUI. If you
wish to use a configuration wizard, navigate to Configuration > Wizards, click on the desired wizard, and follow the imbedded help
instructions within the wizard.
Configuring a VLAN for Network Connection
You must follow the instructions in this section only if you need to configure a trunk port between the controller
and another layer-2 switch (shown in “Deployment Scenario #3” on page51).
This section shows how to use both the WebUI and CLI for the following configurations (subsequent steps show
how to use the WebUI only):
Create a VLAN on the controller and assign it an IP address.
Optionally, create a VLAN pool. A VLAN pool consists of two more VLAN IDs which are grouped together to
efficiently manage multi-controller networks from a single location. For example, policies and virtual
application configurations map users to different VLANs which may exist at different controllers. This creates
redundancy where one controller has to back up many other controllers. With the VLAN pool feature you can
control your configuration globally.
CAUTION: VLAN pooling should not be used with static IP addresses.
Assign to the VLAN the ports) that you will use to connect the controller to the network. (For example, the
uplink ports connected to a router are usually Gigabit ports.) In the example configurations shown in this
section, a controller is connected to the network through its Gigabit Ethernet port 1/25.
Configure the port as a trunk port.
Configure a default gateway for the controller.
Creating and Updating a VLAN
You can create and update a single VLAN or bulk VLANS using the WebUI or the CLI. See “Creating and
Updating VLANs” on page59.
NOTE: In the WebUI configuration windows, clicking the Save Configuration button saves configuration changes so they are
retained after the controller is rebooted. Clicking the Apply button saves changes to the running configuration but the changes are
not retained when the controller is rebooted. A good practice is to use the Apply button to save changes to the running
configuration and, after ensuring that the system operates as desired, click Save Configuration.
Viewing Existing VLAN IDs
Use the CLI to view VLAN IDs.
(host) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(host) (config) #show vlan
CAUTION: VLAN pooling should not be used with static IP addresses.
You can create, update, delete a VLAN pool using the WebUI or the CLI. See “Creating, Updating and Deleting
VLAN Pools” on page60.
Adding existing VLAN IDs to a VLAN Pool in the CLI
Use the CLI to add existing VLAN IDS to a pool.
54 | The Basic User-Centric NetworksDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 55
(host) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(host) (config) #vlan-name mygroup pool
(host) (config) #vlan mygroup 2,4,12
(host) (config) #
To confirm the VLAN pool status and mappings assignments, use the show vlan mapping command:
(host) (config) #show vlan mapping
VLAN Name Pool Status VLAN IDs
The following configurations assign a default gateway for the controller.
In the WebUI
1. Navigate to the Configuration > Network > IP > IP Routes window.
2. To add a new static gateway, click the Add button below the static IP address list.
a. In the IP Address field, enter an IP address in dotted-decimal format.
b. In the Cost field, enter a value for the path cost.
c. Click Add.
3. You can define a dynamic gateway using DHCP, PPPOE or a cell uplink interface. In the Dynamic section,
click the DHCP, PPPoE or Cellular checkboxes to select one or more dynamic gateway options. If you select
more than one dynamic gateway type, you must also define a cost for the route to each gateway. The
controller will first attempt to obtain a gateway IP address using the option with the lowest cost. If the
controller is unable to obtain a gateway IP address, it will then attempt to obtain a gateway IP address using
the option with the next-lowest path cost.
4. Click Apply.
In the CLI
ip default-gateway <ipaddr>|{import cell|dhcp|pppoe}|{ipsec <name>} <cost>
Configuring the Loopback for the Controller
You must configure a loopback address if you are not using a VLAN ID address to connect the controller to the
network (see “Deployment Scenario #3” on page51).
NOTE: After you configure or modify a loopback address, you must reboot the controller.
If configured, the loopback address is used as the controller’s IP address. If you do not configure a loopback
address for the controller, the IP address assigned to the first configured VLAN interface IP address. Generally,
VLAN 1 is configured first and is used as the controller’s IP address.
ArubaOS allows the loopback address to be part of the IP address space assigned to a VLAN interface. In the
example topology, the VLAN 5 interface on the controller was previously configured with the IP address
10.3.22.20/24. The loopback IP address in this example is 10.3.22.220.
NOTE: Youconfigure the loopback address as a host address with a 32-bit netmask. The loopback address should be routable
from all external networks.
Spanning tree protocol (STP) is enabled by default on the controller. STP ensures a single active path between
any two network nodes, thus avoiding bridge loops. Disable STP on the controller if you are not employing STP in
your network.
In the WebUI
1. Navigate to the Configuration > Network > Controller > System Settings window.
2. Enter the IP address under Loopback Interface.
3. On this window, you can also turn off spanning tree. Click No for Spanning Tree Enabled.
4. Click Apply at the bottom of the window (you might need to scroll down the window).
5. At the top of the window, click Save Configuration. Note that you must reboot the controller for the new IP
address to take effect.
6. Navigate to the Maintenance > Controller > Reboot Controller window.
7. Click Continue.
In the CLI
interface loopback ip address 10.3.22.220
no spanning-tree
write memory
reload
The controller returns the following messages:
Do you really want to reset the system(y/n):
Enter y to reboot the controller or n to cancel.
56 | The Basic User-Centric NetworksDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 57
System will now restart!
...
Restarting system.
To verify that the controller is accessible on the network, ping the loopback address from a workstation on the
network.
Configuring the System Clock
You can manually set the clock on the controller, or configure the controller to use a Network Time Protocol
(NTP) server to synchronize its system clock with a central time source. For more information about setting the
controller’s clock, see “Setting the System Clock” on page604.
Installing Licenses
ArubaOS consists of a base operating system with optional software modules that you can activate by installing
license keys. If you use the Setup Wizard during the initial setup phase, you will have the opportunity to install
software licenses at that time. See Chapter 34, “Software Licenses” on page651 for detailed information on
Licenses.
Connecting the Controller to the Network
Connect the ports on the controller to the appropriately-configured ports on an L2 switch or router. Make sure
that you have the correct cables and that the port LEDs indicate proper connections. See the Installation Guide
for the controller for port LED and cable descriptions.
NOTE: In many deployment scenarios, an external firewall is situated between various Dell devices. Appendix B, “External
Firewall Configuration” describes the network ports that must be configured on the external firewall to allow proper operation
of the network.
To verify that the controller is accessible on the network:
If you are using VLAN 1 to connect the controller to the network (“Deployment Scenario #2” on page50 and
“Deployment Scenario #3” on page51), ping the VLAN 1 IP address from a workstation on the network.
If you created and configured a new VLAN (“Deployment Scenario #3” on page51), ping the IP address of
the new VLAN from a workstation on the network.
Additional Configuration
Wireless users can connect to the SSID but because you have not yet configured authentication, policies, or user
roles, they will not have access to the network. Other chapters in the ArubaOS User Guide describe how to build
upon this basic deployment to configure user roles, firewall policies, authentication, authentication servers, and
other wireless features.
58 | The Basic User-Centric NetworksDell PowerConnect W-Series ArubaOS 6.1 | User Guide
Page 59
Chapter 2
Network Parameters
This chapter describes some basic network configuration on the controller. This chapter describes the following
topics:
“Configuring VLANs” on page59
“Configuring Ports” on page63
“About VLAN Assignments” on page65
“Configuring Static Routes” on page72
“Configuring the Loopback IP Address” on page72
“Configuring the Controller IP Address” on page73
“Configuring GRE Tunnels” on page74
Configuring VLANs
The controller operates as a layer-2 switch that uses a VLAN as a broadcast domain. As a layer-2 switch, the
controller requires an external router to route traffic between VLANs. The controller can also operate as a layer-3
switch that can route traffic between VLANs defined on the controller.
You can configure one or more physical ports on the controller to be members of a VLAN. Additionally, each
wireless client association constitutes a connection to a virtual port on the controller, with membership in a
specified VLAN. You can place all authenticated wireless users into a single VLAN or into different VLANs,
depending upon your network. VLANs can exist only inside the controller or they can extend outside the
controller through 802.1q VLAN tagging.
You can optionally configure an IP address and netmask for a VLAN on the controller. The IP address is up when
at least one physical port in the VLAN is up. The VLAN IP address can be used as a gateway by external devices;
packets directed to a VLAN IP address that are not destined for the controller are forwarded according to the
controller’s IP routing table.
Creating and Updating VLANs
You can create and update a single VLAN or bulk VLANs.
Using the WebUI
1. Navigate to the Configuration > Network > VLANs page.
2. Click Add a VLAN to create a new VLAN. (To edit an existing VLAN click Edit for the VLAN entry.) See
“Create a Bulk VLANs Using the WebUI” on page60 to create a range of VLANs.
3. In the VLAN ID field, enter a valid VLAN ID. (Valid values are from 1 to 4094, inclusive).
4. To add physical ports to the VLAN, select Port. To associate the VLAN with specific port-channels, select
Port-Channel.
5. (Optional) Click the Wired AAA Profile drop-down list to assign an AAA profile to a VLAN. This wired AAA
profile enables role-based access for wired clients connected to an untrusted VLAN or port on the controller.
Note that this profile will only take effect if the VLAN or port on the controller is untrusted. If you do not
assign an wired AAA profile to the VLAN, the global wired AAA profile applies to traffic from untrusted wired
ports.
6. If you selected Port in step 4, select the ports you want to associate with the VLAN from the Port Selection
window.
-or-
If you selected Port-Channel in step 4, click the Port-Channel ID drop-down list, select the specific channel
number you want to associate with the VLAN, then select the ports from the Port Selection window.
1. To add multiple VLANs at one time, click Add Bulk VLANs.
2. In the VLAN Range pop-up window, enter a range of VLANs you want to create at once. For example, to add
VLAN IDs numbered 200-300 and 302-350, enter 200-300, 302-350.
3. Click OK.
4. To add physical ports to a VLAN, click Edit next to the VLAN you want to configure and click the port in the
Port Selection section.
5. Click Apply.
Using CLI
(host) (config) #vlan
(host) (config) #vlan range 200-300,302-350
Creating, Updating and Deleting VLAN Pools
You can create, update and delete a VLAN pool.
Creating a VLAN pool Using the WebUI
The following configurations create a VLAN Pool named mygroup. VLAN IDs 2, 4 and 12 are then assigned to the
VLAN pool mygroup.
1. Navigate to Configuration > Network > VLAN.
2. Select the VLAN Pool tab to open the VLAN Pool window.
3. Click Add.
4. In the VLAN Name field, enter a name that identifies this VLAN pool. Names must be between 1 and 32
characters; spaces are not allowed. The VLAN name can not be modified; choose the name carefully.
5. In the List of VLAN IDs field, enter the VLAN IDs you want to add to this pool. If you know the ID, enter
each ID separated by a comma. Or, click the drop-down list to view the IDs then click the <-- arrow to add
the ID to the pool..
CAUTION: VLAN pooling should not be used with static IP addresses.
6. You must add two or more VLAN IDs to create a pool.
The VLAN pool along with its assigned IDs appears on the VLAN Pool window. If the pool is valid (it has two
or more IDs assigned to it), its status is enabled. If you create a VLAN pool and add only one or no VLAN IDs,
its status appears as disabled.
8. Click Apply.
9. At the top of the window, click Save Configuration.
Updating a VLAN Pool
1. On the VLAN Pool window, click Modify next to the VLAN name you want to edit.
2. Modify the list of VLAN IDs. Note that you can not modify the VLAN name.
3. Click Update.
4. Click Apply.
5. At the top of the window, click Save Configuration.
Deleting a VLAN Pool
1. On the VLAN Pool window, click Delete next to the VLAN name you want to delete. A prompt appears.
2. Click OK.
3. Click Apply.
4. At the top of the window, click Save Configuration.
Create a VLAN Pool Using CLI
The pool option allows you to create a VLAN pool consisting of two more VLAN IDs.
(host) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(host) (config) #vlan-name mygroup pool
(host) (config) #
Viewing Existing VLAN IDs Using CLI
(host) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(host) (config) #show vlan
The following example illustrates adding existing VLAN IDs to a VLAN pool:
(host) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(host) (config) #vlan-name mygroup pool
(host) (config) #vlan mygroup 2,4,12
(host) (config) #
Bandwidth contracts on a VLAN can limit broadcast and multicast traffic. ArubaOS includes an internal
exception list to allow broadcast and multicast traffic using the VRRP, LACP, OSPF, PVST and STP protocols.
To remove per-VLAN bandwidth contract limits on an additional broadcast or multicast protocol, add the MAC
address for that broadcast/multicast protocol to the VLAN Bandwidth Contracts MAC Exception List.
The command in the example below adds the MAC address for CDP (Cisco Discovery Protocol) and VTP
(Virtual Trunking Protocol to the list of protocols that are not limited by VLAN bandwidth contracts.
(host) (config) #vlan-bwcontract-explist mac 01:00:0C:CC:CC:CC
To show entries in the VLAN bandwidth contracts MAC exception list, use the show vlan-bwcontract-explist
[internal] command:
Broadcast and Multicast (BCMC) traffic from APs, remote APs, or distributions terminating on the same VLAN
floods all VLAN member ports. This causes critical bandwidth wastage especially when the APs are connected to
L3 cloud where the available bandwidth is limited or expensive. Suppressing the VLAN BCMC traffic to prevent
flooding can result in loss of client connectivity.
To effectively prevent flooding of BCMC traffic on all VLAN member ports, use the bcmc-optimization
parameter under the interface vlan command. This parameter ensures controlled flooding of BCMC traffic
without compromising the client connectivity. By default this option is disabled. You must enable this parameter
for the controlled flooding of BCMC traffic.
The bcmc-optimization parameter has the following exemptions:
All DHCP traffic will continue to flood VLAN member ports even if the bcmc-optimization parameter is
enabled.
The controller will do proxy ARP if the target IP entry exists on the controller. If the target IP does not exist
on the controller, ARP requests will be flooded on all VLAN member ports.
You can configure BCMC optimization in CLI and in the WebUI.
Hardware is CPU Interface, Interface address is 00:0B:86:61:5B:98 (bia
00:0B:86:61:5B:98)
Description: 802.1Q VLAN
Internet address is 10.17.22.1 255.255.255.0
Routing interface is enable, Forwarding mode is enable
Directed broadcast is disabled, BCMC Optimization enable
Encapsulation 802, loopback not set
MTU 1500 bytes
Last clearing of "show interface" counters 12 day 1 hr 4 min 12 sec
link status last changed 12 day 1 hr 2 min 21 sec
Proxy Arp is disabled for the Interface
In the WebUI
1. Navigate to Configuration > Network > IP.
2. In the IP Interfaces tab, click the Edit button of the VLAN for configuring BCMC optimization.
3. Select Enable BCMC check box to enable BCMC Optimization for the selected VLAN.
Figure 1 Enable BCMC Optimization
Configuring Ports
Both Fast Ethernet and Gigabit Ethernet ports can be set to access or trunk mode. By default, a port is in access
mode and carries traffic only for the VLAN to which it is assigned. In trunk mode, a port can carry traffic for
multiple VLANs.
For a trunk port, specify whether the port will carry traffic for all VLANs configured on the controller or for
specific VLANs. You can also specify the native VLAN for the port. A trunk port uses 802.1q tags to mark frames
for specific VLANs, However, frames on a native VLAN are not tagged.
Classifying Traffic as Trusted or Untrusted
You can classify wired traffic based not only on the incoming physical port and channel configuration but also on
the VLAN associated with the port and channel.
About Trusted and Untrusted Physical Ports
By default, physical ports on the controller are trusted and are typically connected to internal networks while
untrusted ports connect to third-party APs, public areas, or other networks to which access controls can be
applied. When you define a physical port as untrusted, traffic passing through that port needs to go through a
predefined access control list policy.
About Trusted and Untrusted VLANs
You can also classify traffic as trusted or untrusted based on the VLAN interface and port/channel. This means
that wired traffic on the incoming port is trusted only when the port’s associated VLAN is also trusted, otherwise
the traffic is untrusted. When a port and its associated VLANs are untrusted, any incoming and outgoing traffic
must pass through a predefined ACL. For example, this setup is useful if your company provides wired user guest
access and you want guest user traffic to pass through an ACL to connect to a captive portal.
You can set a range of VLANs as trusted or untrusted in trunk mode. The following table lists the port, VLAN and
the trust/untrusted combination to determine if traffic is trusted or untrusted. both the port and the VLAN have
to be configured as trusted for traffic to be considered as trusted. If the traffic is classified as untrusted then
traffic must pass through the selected session access control list and firewall policies.
Table 3 Classifying Trusted and Untrusted Traffic
PortVLANTraffic Status
TrustedTrustedTrusted
UntrustedUntrustedUntrusted
UntrustedTrustedUntrusted
TrustedUntrustedUntrusted
Configuring Trusted/Untrusted Ports and VLANs
You can configure an Ethernet port as an untrusted access port, assign VLANs and make them untrusted, and
designate a policy through which VLAN traffic on this port must pass.
Using WebUI
1. Navigate to the Configuration > Network > Ports window.
2. In the Port Selection section, click the port you want to configure.
3. In the Make Port Trusted section, clear the Trusted check box to make the port untrusted. The default is
trusted (checked).
4. In the Port Mode section, select Access.
5. From the VLAN ID drop-down list select the VLAN ID whose traffic will be carried by this port.
6. In the Enter VLAN(s) section, clear the Trusted check box to make the VLAN untrusted. The default is
trusted (checked).
7. In the VLAN Firewall Policy drop-down list, select the policy through which VLAN traffic must pass. You can
select a policy for both trusted and untrusted VLANs.
8. From the Firewall Policy section, select the policy from the in drop-down list through which inbound traffic
on this port must pass.
9. Select the policy from the out drop-down list through which outbound traffic on this port must pass.
10. To apply a policy to this session’s traffic on this port and VLAN, select the policy from the session drop-down
list.
Configure Trusted/Untrusted Ports and VLANs in Trunk Mode
The following procedures configure a range of Ethernet ports as untrusted native trunks ports, assign VLANs and
make them untrusted and designate a policy through which VLAN traffic on the ports must pass.
Using the WebUI
1. Navigate to the Configuration > Network > Ports window.
2. In the Port Selection section, click the port you want to configure.
3. For Port Mode select Trunk.
4. To specify the native VLAN, select a VLAN from the Native VLAN drop-down list and click the <-- arrow.
5. Choose one of the following options to control the type of traffic the port carries:
Allow All VLANS Except– The port carries traffic for all VLANs except the ones from this drop-down list.
Allow VLANs – The port carries traffic for all VLANs selected from this drop-down list.
Remove VLANs – The port does not carry traffic for any VLANs selected from this drop-down list.
6. To designate untrusted VLANs on this port, click Trusted except. In the corresponding VLAN field enter a
range of VLANs that you want to make untrusted. (In this format, for example: 200-300, 401-500 and so on).
Only VLANs listed in this range are untrusted. Or, to make only one VLAN untrusted, select a VLAN from the
drop-down menu.
7. To designate trusted VLANs on this port, click Untrusted except. In the corresponding VLAN field enter a
range of VLANs that you want to make trusted. (In this format, for example: 200-300, 401-500 and so on).
Only VLANs listed in this range are trusted. Or, to make only one VLAN trusted, select a VLAN from the
drop-down menu.
8. To remove a VLAN, click the Remove VLANs option and select the VLAN you want to remove from the dropdown list and click the left arrow to add it to the list.
9. To designate the policy through which VLAN traffic must pass, click New under the Session Firewall Policy
field.
10. Enter the VLAN ID or select it from the associated drop-down list. Then select the policy, through which the
VLAN traffic must pass, from the Policy drop-down list and click Add. Both the selected VLAN and the policy
appear in the Session Firewall Policy field.
11. When you are finished listing VLAN and policies, click Cancel.
A client is assigned to a VLAN by one of several methods. There is an order of precedence by which VLANs are
assigned. The assignment of VLANs are (from lowest to highest precedence):
1. The default VLAN is the VLAN configured for the WLAN (see “Virtual AP Profiles” on page139).
2. Before client authentication, the VLAN can be derived from rules based on client attributes (SSID, BSSID,
client MAC, location, and encryption type). A rule that derives a specific VLAN takes precedence over a rule
that derives a user role that may have a VLAN configured for it.
3. After client authentication, the VLAN can be the VLAN configured for a default role for an authentication
method, such as 802.1x or VPN.
4. After client authentication, the VLAN can be derived from attributes returned by the authentication server
(server-derived rule). A rule that derives a specific VLAN takes precedence over a rule that derives a user role
that may have a VLAN configured for it.
5. After client authentication, the VLAN can be derived from Microsoft Tunnel attributes (Tunnel-Type,
Tunnel Medium Type, and Tunnel Private Group ID). All three attributes must be present. This does not
require any server-derived rule.
6. After client authentication, the VLAN can be derived from Vendor Specific Attributes (VSA) for RADIUS
server authentication. This does not require any server-derived rule. If a VSA is present, it overrides any
previous VLAN assignment.
How a VLAN Obtains its IP Address
A VLAN on the controller obtains its IP address in one of the following ways:
Manually configured by the network administrator. This is the default method and is described in “Assigning
a Static Address to a VLAN” on page66. At least one VLAN on the controller must be assigned a static IP
address.
Dynamically assigned from a Dynamic Host Configuration Protocol (DHCP) or Point-to-Point Protocol over
Ethernet (PPPoE) server.
Assigning a Static Address to a VLAN
You can manually assign a static IP address to a VLAN on the controller. At least one VLAN on the controller
must be assigned a static IP address.
Using the WebUI
1. Navigate to the Configuration > Network > IP > IP Interfaces page on the WebUI. Click Edit for the
VLAN you just added.
2. Select the Use the following IP address option. Enter the IP address and network mask of the VLAN interface.
If required, you can also configure the address of the DHCP server for the VLAN by clicking Add.
3. Click Apply.
Using CLI
interface vlan <id>
ip address <address> <netmask>
Configuring a VLAN to Receive a Dynamic Address
In a branch office, you can connect a controller to an uplink switch or server that dynamically assigns IP addresses
to connected devices. For example, the controller can be connected to a DSL or cable modem, or a broadband
remote access server (BRAS). shows a branch office where a controller connects to a cable modem. VLAN 1 has a
static IP address, while VLAN 2 has a dynamic IP address assigned via DHCP or PPPoE from the uplink device.
Figure 2 IP Address Assignment to VLAN via DHCP or PPPoE
You can assign up to four VLAN interfaces to operate in active-standby topology. An active-standby topology
provides redundancy so that when an active interface fails, the user traffic can failover to the standby interface.
To allow the controller to obtain a dynamic IP address for a VLAN, enable the DHCP or PPPoE client on the
controller for the VLAN.
The following restrictions apply when enabling the DHCP or PPPoE client on the controller:
You can enable the DHCP/PPPoE client multiple uplink VLAN interfaces (up to four) on the controller; these
VLANs cannot be VLAN 1.
Only one port in the VLAN can be connected to the modem or uplink switch.
At least one interface in the VLAN must be in the up state before the DHCP/PPPoE client requests an IP
address from the server.
Enabling the DHCP Client
The DHCP server assigns an IP address for a specified amount of time called a lease. The controller automatically
renews the lease before it expires. When you shut down the VLAN, the DHCP lease is released.
Using the WebUI
1. Navigate to the Configuration > Network > IP > IP Interfaces page.
2. Click Edit for a previously-created VLAN.
3. Select Obtain an IP address from DHCP.
4. Enter a priority value for the VLAN ID in the Uplink Priority field. By default, all wired uplink interfaces have
the same priority. If you want to use an active-standby topology then prioritize each uplink interfaces by
entering a different priority value (1– 4) for each uplink interface.
interface vlan 62 ip address dhcp-client client-id myclient
Enabling the PPPoE Client
To authenticate to the BRAS and request a dynamic IP address, the controller must have the following
configured:
PPPoE user name and password to connect to the DSL network
PPPoE service name — either an ISP name or a class of service configured on the PPPoE server
When you shut down the VLAN, the PPPoE session terminates.
Using the WebUI
1. Navigate to the Configuration > Network > IP > IP Interfaces page.
2. Click Edit for a previously-created VLAN.
3. Select Obtain an IP address with PPPoE.
4. Enter the service name, username, and password for the PPPoE session.
5. Enter a priority value for the VLAN ID in the Uplink Priority field. By default, all wired uplink interfaces have
the same priority. If you want to use an active-standby topology then prioritize each uplink interfaces by
entering a different priority value (1– 4) for each uplink interface.
6. Click Apply.
Using CLI
In this example, a PPoE service name, username and password are assigned. The interface VLAN 14 has an uplink
priority of 3.
interface vlan 14
ip address pppoe
interface vlan 14 ip pppoe-service-name <service_name>
interface vlan 14 ip pppoe-username <username>
interface vlan 14 ip pppoe-password *****
uplink wired vlan 14 priority 3
Default Gateway from DHCP/PPPoE
You can specify that the router IP address obtained from the DHCP or PPPoE server be used as the default
gateway for the controller.
Using the WebUI
1. Navigate to the Configuration > Network > IP > IP Routes page.
2. For Default Gateway, select (Obtain an IP address automatically).
3. Select Apply.
Using CLI
ip default-gateway import
Configuring DNS/WINS Server from DHPC/PPPoE
The DHCP or PPPoE server can also provide the IP address of a DNS server or NetBIOS name server, which can
be passed to wireless clients through the controller’s internal DHCP server.
For example, the following configures the DHCP server on the controller to assign addresses to authenticated
employees; the IP address of the DNS server obtained by the controller via DHCP/PPPoE is provided to clients
along with their IP address.
Using the WebUI
1. Navigate to the Configuration > Network > IP > DHCP Server page.
2. Select Enable DCHP Server.
3. Under Pool Configuration, select Add.
4. For Pool Name, enter employee-pool.
5. For Default Router, enter 10.1.1.254.
6. For DNS Servers, select Import from DHCP/PPPoE.
7. For WINS Servers, select Import from DHCP/PPPoE.
8. For Network, enter 10.1.1.0 for IP Address and 255.255.255.0 for Netmask.
9. Click Done.
Using CLI
ip dhcp pool employee-pool
default-router 10.1.1.254
dns-server import
netbios-name-server import
network 10.1.1.0 255.255.255.0
Configuring Source NAT to Dynamic VLAN Address
When a VLAN interface obtains an IP address through DHCP or PPPoE, a NAT pool (dynamic-srcnat) and a
session ACL (dynamic-session-acl) are automatically created which reference the dynamically-assigned IP
addresses. This allows you to configure policies that map private local addresses to the public address(es)
provided to the DHCP or PPPoE client. Whenever the IP address on the VLAN changes, the dynamic NAT pool
address also changes to match the new address.
For example, the following rules for a guest policy deny traffic to internal network addresses. Traffic to other
(external) destinations are source NATed to the IP address of the DHCP/PPPoE client on the controller.
Using the WebUI
1. Navigate to the Configuration > Security > Access Control > Policies page. Click Add to add the policy
guest.
2. To add a rule, click Add.
a. For Source, select any.
b. For Destination, select network and enter 10.1.0.0 for Host IP and 255.255.0.0 for Mask.
ip access-list session guest
any network 10.1.0.0 255.255.0.0 any deny
any any any src-nat pool dynamic-srcnat
Configuring Source NAT for VLAN Interfaces
The example configuration in the previous section illustrates how to configure source NAT using a policy that is
applied to a user role. You can also enable source NAT for a VLAN interface to cause NAT to be performed on the
source address for all traffic that exits the VLAN.
Packets that exit the VLAN are given a source IP address of the “outside” interface, which is determined by the
following:
If you configure “private” IP addresses for the VLAN, the controller is assumed to be the default gateway for
the subnetwork. Packets that exit the VLAN are given the IP address of the controller for their source IP
address.
If the controller is forwarding the packets at Layer-3, packets that exit the VLAN are given the IP address of
the next-hop VLAN for their source IP address.
Example Configuration
In the following example, the controller operates within an enterprise network. VLAN 1 is the outside VLAN.
Traffic from VLAN 6 is source NATed using the IP address of the controller. In this example, the IP address
assigned to VLAN 1 is used as the controller’s IP address; thus traffic from VLAN 6 would be source NATed to
66.1.131.5.
Figure 4 Example: Source NAT using Controller IP Address
Private IP addresses:
192.168.2.1/24
VLAN 6
Inside
Public IP addresses: 66.1.131.5/
24
VLAN 1
Outside
Using the WebUI
1. Navigate to the Configuration > Network > VLANs page. Click Add to configure VLAN 6 (VLAN 1 is
configured through the Initial Setup).
a. Enter 6 for the VLAN ID.
b. Click Apply.
2. Navigate to the Configuration > Network > IP > IP Interfaces page.
3. Click Edit for VLAN 6:
a. Select Use the following IP address.
b. Enter 192.168.2.1 for the IP Address and 255.255.255.0 for the Net Mask.
c. Select the Enable source NAT for this VLAN checkbox.
interface vlan 1
ip address 66.1.131.5 255.255.255.0
interface vlan 6
ip address 192.168.2.1 255.255.255.0
ip nat inside
ip default-gateway 66.1.131.1
Inter-VLAN Routing
On the controller, you can map a VLAN to a layer-3 subnetwork by assigning a static IP address and netmask or by
configuring a DHCP or PPPoE server to provide a dynamic IP address and netmask to the VLAN interface. The
controller, acting as a layer-3 switch, routes traffic between VLANs that are mapped to IP subnetworks; this
forwarding is enabled by default.
In Figure 5, VLAN 200 and VLAN 300 are assigned the IP addresses 2.1.1.1/24 and 3.1.1.1/24, respectively. Client
A in VLAN 200 is able to access server B in VLAN 300 and vice versa, provided that there is no firewall rule
configured on the controller to prevent the flow of traffic between the VLANs.
Figure 5 Default Inter-VLAN Routing
Client AServer B
VLAN 200
VLAN 300
You can optionally disable layer-3 traffic forwarding to or from a specified VLAN. When you disable layer-3
forwarding on a VLAN, the following restrictions apply:
Clients on the restricted VLAN can ping each other, but cannot ping the VLAN interface on the controller.
Forwarding of inter-VLAN traffic is blocked.
IP mobility does not work when a mobile client roams to the restricted VLAN. You must ensure that a mobile
client on a restricted VLAN is not allowed to roam to a non-restricted VLAN. For example, a mobile client on
a guest VLAN should not be able to roam to a corporate VLAN.
To disable layer-3 forwarding for a VLAN configured on the controller:
Using the WebUI to restrict VLAN routing
1. Navigate to the Configuration > Network > IP > IP Interface page.
2. Click Edit for the VLAN for which routing is to be restricted.
3. Configure the VLAN to either obtain an IP address dynamically (via DHCP or PPPoE) or to use a static IP
address and netmask.
4. Deselect (uncheck) the Enable Inter-VLAN Routing checkbox.
interface vlan <id>
ip address {<ipaddr> <netmask>|dhcp-client|pppoe}
no ip routing
Configuring Static Routes
To configure a static route (such as a default route) on the controller, do the following:
Using the WebUI
1. Navigate to the Configuration > Network > IP > IP Routes page.
2. Click Add to add a static route to a destination network or host. Enter the destination IP address and network
mask (255.255.255.255 for a host route) and the next hop IP address.
3. Click Done to add the entry. Note that the route has not yet been added to the routing table.
4. Click Apply to add this route to the routing table. The message Configuration Updated Successfully
confirms that the route has been added.
Using CLI
ip route <address> <netmask> <next_hop>
Configuring the Loopback IP Address
The loopback IP address is a logical IP interface that is used by the controller to communicate with APs. The
loopback address is used as the controller’s IP address for terminating VPN and GRE tunnels, originating requests
to RADIUS servers and accepting administrative communications. You configure the loopback address as a host
address with a 32-bit netmask. The loopback address is not bound to any specific interface and is operational at all
times. To use this interface, ensure that the IP address is reachable through one of the VLAN interfaces. It should
be routable from all external networks.
You must configure a loopback address if you are not using VLAN1 to connect the controller to the network. If
the loopback interface address is not configured then the first configured VLAN interface address is selected.
Generally, VLAN 1 is the factory default setting and thus becomes the controller IP address
Using the WebUI
1. Navigate to the Configuration > Network > Controller > System Settings page and locate the Loopback
Interface section.
2. Modify the IP Address as required.
3. Click Apply.
CAUTION: If you are using the loopback IP address to access the WebUI, changing the loopback IP address will result in loss of
connectivity. Dell recommends that you use one of the VLAN interface IP addresses to access the WebUI.
4. Navigate to the Maintenance > Controller > Reboot Controller page to reboot the controller to apply the
change of loopback IP address.
6. When prompted that the changes were written successfully to flash, click OK.
7. The controller boots up with the changed loopback IP address.
Using CLI
interface loopback ip address <address>
write memory
Using the CLI to reboot the controller
Enter the following command in Enable mode:
reload
Configuring the Controller IP Address
The Controller IP address is used by the controller to communicate with external devices such as APs.
You can set the Controller IP address to the loopback interface address or to an existing VLAN ID address. This
allows you to force the controller IP address to be a specific VLAN interface or loopback address across multiple
machine reboots. Once you configure an interface to be the controller IP address, that interface address cannot be
deleted until you remove it from the controller IP configuration.
If the controller IP address is not configured then the controller IP defaults to the current loopback interface
address. If the loopback interface address is not configured then the first configured VLAN interface address is
selected. Generally, VLAN 1 is the factory default setting and thus becomes the controller IP address.
Using the WebUI
1. Navigate to the Configuration > Network > Controller > System Settings page.
2. Locate the Controller IP Details section.
3. Select the address you want to set the Controller IP to from the VLAN ID drop-down menu. This list only
contains VLAN IDs that have statically assigned IP addresses. If a loopback interface IP address has been
previously configured then it will also appear in this list. Dynamically assigned IP addresses, for example
DHCP/PPPOE do not display.
4. Click Apply.
NOTE: Any change in the controller’s IP address requires a reboot.
5. Navigate to the Maintenance > Controller > Reboot Controller page to reboot the controller to apply the
change of controller IP address.
A controller supports generic routing encapsulation (GRE) tunnels between the controller and APs. An AP opens
a GRE tunnel to the controller for each radio interface. On the AP, the other end of the GRE tunnel is specified
by the IP address configured variable values (in descending order of priority) <master>, <servername>, and
<serverip>. If these variable are left to default values, the AP uses DNS to look up aruba-master to discover the
IP address of the controller.
The controller also supports GRE tunnels between the controller and other GRE-capable devices. This section
describes how to configure a GRE tunnel to such a device and how to direct traffic into the tunnel.
NOTE: The controller uses GRE tunnels for communications between master and local controllers; these GRE tunnels are
automatically created and are not subject to the configuration described in this section.
Creating a Tunnel Interface
To create a GRE tunnel on the controller, you need to specify the following:
Tunnel ID: this can be a number between 1 and 2147483647.
IP address and netmask for the tunnel.
Tunnel source: the local endpoint for the tunnel on the controller. This can be one of the following:
Loopback address of the controller
A specified IP address
A specified VLAN
Tunnel destination: the IP address of the remote endpoint of the tunnel on the other GRE device.
Using the WebUI
1. Navigate to the Configuration > Network > IP > GRE Tunnels page.
2. Click Add.
3. Enter the tunnel ID.
4. Enter the IP address and netmask for the tunnel.
5. Select (check) Enabled to enable the tunnel interface.
6. Select the tunnel source, if it is not the loopback address of the controller. If you select IP Address, enter the
IP address for the tunnel source. If you select VLAN, select the ID of the VLAN.
7. Enter the IP address of the tunnel destination.
interface tunnel <id>
tunnel mode gre <num> <ip>
ip address <ipaddr> <netmask>
no shutdown
tunnel source {<ipaddr>| loopback | vlan <vlan>}
tunnel destination <ipaddr>
Directing Traffic into the Tunnel
You can direct traffic into the tunnel by configuring one of the following:
Static route, which redirects traffic to the IP address of the tunnel
Firewall policy (session-based ACL), which redirects traffic to the specified tunnel ID
Static Routes
You can configure a static route that specifies the IP address of a tunnel as the next-hop for traffic for a specific
destination. See “Configuring Static Routes” on page72 for descriptions of how to configure a static route.
Firewall Policy
You can configure a firewall policy rule to redirect selected traffic into a tunnel.
Traffic redirected by a firewall policy rule is not forwarded to a tunnel that is “down” (see “Tunnel Keepalives” on
page75 for more information on how GRE tunnel status is determined). If you have more than one GRE tunnel
configured, you can create multiple firewall policy rules with each rule redirecting the same traffic to different
tunnels. If the tunnel in the first traffic redirect rule is down, then the tunnel in the subsequent traffic redirect
rule is used instead.
WebUI
1. Navigate to the Configuration > Security > Access Control > Policies page.
2. Click Add to create a new firewall policy, or click Edit to edit a specific policy.
3. Click Add to create a new policy rule.
4. Configure the Source, Destination, and Service for the rule.
5. For Action, select redirect to tunnel. Enter the tunnel ID.
6. Configure any additional options, and click Add.
7. Click Apply.
CLI
ip access-list session <name>
<source> <destination> <service> redirect tunnel <id>
Tunnel Keepalives
The controller can determine the status of a GRE tunnel by sending periodic keepalive frames on the tunnel. If
you enable tunnel keepalives, the tunnel is considered to be “down” if there is repeated failure of the keepalives.
If you configured a firewall policy rule to redirect traffic to the tunnel, traffic is not forwarded to the tunnel until
it is “up”. When the tunnel comes up or goes down, an SNMP trap and logging message is generated. The remote
endpoint of the tunnel does not need to support the keepalive mechanism.
By default, the controller sends keepalive frames at 60-second intervals and retries keepalives up to three times
before the tunnel is considered to be down. You can reconfigure the intervals from the default. For the interval,
specify a value between 1-86400 seconds. For the retries, specify a value between 0-1024.
RF Plan is a wireless deployment modeling tool that helps you design an efficient Wireless Local Area Network
(WLAN) that optimizes coverage and performance, without complicated WLAN network setup. RF Plan
provides the following critical functionality:
Defines WLAN coverage.
Defines WLAN environment security coverage.
Assesses equipment requirements.
Optimizes radio resources.
RF Plan provides a view of each floor, allowing you to specify how you want to provide wireless coverage for each
area. RF Plan also generates coverage maps with AP and AM placement.
Unlike other static site survey tools that require administrators to have intricate knowledge of building materials
and other potential radio frequency (RF) hazards, RF Plan calibrates coverage in real-time through a
sophisticated RF calibration algorithm. This real-time calibration lets you characterize the indoor propagation of
RF signals to determine the best channel and transmission power settings for each AP. You can program the
calibration to occur automatically or you can manually launch the calibration at any time to quickly adapt to
changes in your wireless environment.
This chapter discusses the following topics:
“Supported Planning” on page77
“Before You Begin” on page78
“Launching the RF Plan” on page79
“Using the FQLN Mapper in the AP Provision Page” on page100
“RF Plan Example” on page101
Supported Planning
All the features included in the WebUI RF Plan tool will aide you in the planning 802.11n standard compliant
deployments.
This WebUI RF Plan supports planning of the following types of deployments:
802.11n Deployments—The RF Plan now supports planning of network environments that use the Dell’s AP-
12x series of indoor access points, which are 802.11n compliant. RF Plan supports the planning of these APs in
the following capacity: 802.11a/n, 802.11b/g/n, or 802.11a/b/g/n.
802.11n Hotspot Deployment within an Existing Environment—This type of environment requires that AP/
AM locations be fixed at the building level, see “Fix All Suggested AP/AMs” on page96. If you set and fix the
location of APs prior to planning for the 802.11n APs, the APs will not move when you initialize/optimize the
802.11n AP locations.
802.11n Hotspot Deployment and New Environment—The RF Plan allows you to plan for a new
deployment that uses an 802.11n hotspot and 802.11a and/or 802.11 b/g support outside of the hotspot.
To plan for this type of deployment, start by planning your 802.11n hotspot. When you initialize and optimize
the APs planned for the hotspot, the 802.11n APs are placed within the hotspot area. However, the same AP
type will also be placed outside of the hotspot area with 802.11n support disabled.
Dell PowerConnect W-Series ArubaOS 6.1 | User Guide RF Plan | 77
Page 78
RF Plan will deploy APs outside of the hotspot area based on the 802.11a and/or 802.11b/g rates defined by
the system. For the system to define 802.11a and/or 802.11b/g rates, the system looks at the defined 802.11n
rate and the distance covered by the defined rate; it then selects corresponding 802.11a and/or 802.11b/g rates
based on the distance covered.
Before You Begin
Review the following steps to create a building model and plan the WLAN for your model.
Task Overview
1. Gather information about your building’s dimensions and floor plan.
2. Determine the level of coverage you want for your APs and AMs.
3. Create a new building and add its dimensions.
4. Enter the parameters of your AP coverage.
5. Enter the parameters of your AM coverage.
6. Add floors to your building and import the floor plans.
7. Define special areas.
8. Generate suggested AP and AM tables by executing the AP/AM Plan features.
Planning Requirements
You should collect the following information before using RF Plan. Having this information readily available will
expedite your planning efforts.
Building dimensions
Number of floors
Distance between floors
Number of users and number of users per AP
Radio type(s)
Overlap Factor
Desired data rates for APs
Desired monitoring rates for AMs
Areas of your building(s) that you do not necessarily want coverage
Areas of your building(s) where you do not want or cannot deploy an AP or AM
Areas of your building(s) where you want to deploy an 802.11n Hotspot (Zone)
Any area where you want to deploy a fixed AP or AM
Use the worksheets (Table 4, Table 5, and Table 6) to collect your information:
Table 4 Planning Worksheet - Building Dimensions (Continued)
Building Dimensions
Radio Types:
AP Type:
Overlap Factor:
802.11a Desired Rate:
802.11n (HT) Support:
Use 40 MHz Channel Spacing:
802.11n Desired Rate:
Table 5 Planning Worksheet - AP Desired Rates (2.4 GHz Radio Properties)
AP Desired Rates (2.4 GHz Radio Properties)
802.11b/g Desired Rate:
802.11n (HT) Support:
Use 40 MHz Channel Spacing:
802.11n Desired Rate:
Table 6 Planning Worksheet - AM Desired Rates
AM Desired Rates
802.11b|g:
802.11a:
Don’t Care/Don’t Deploy Areas
802.11n Hotspot (Zone) Areas
NOTE: If 802.11n (HT) support is enabled, the system will automatically define the 802.11a and/or 802.11b/g rate as applicable. For
details, see “Radio Properties (Desired Rates and HT Support Options)” on page 86.
Launching the RF Plan
This section describes how to launch the RF Plan and enter information in RF Plan windows.
To launch RF Plan from the WebUI, click the Plan tab in the WebUI menu bar. When you launch the RF Plan,
the browser window displays the Campus List page.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 79
Page 80
Campus List Page
The Campus List is the first page you see when you start RF Plan. This list contains a default campus and any
campus you have defined using the RF Plan software.
Figure 6 Plan>Campus List Window
You may add, edit, and delete campuses using this page. You may also import and export campus information.
Table 7 details the buttons on the Campus page.
Table 7 Definition of Campus List Buttons
ButtonsDescription
New CampusUse this button to create a new campus.
Browse CampusUse this button to edit existing campuses from the campus list. To edit a campus, select the checkbox
Rename CampusUse this button to rename an existing campus in the list. To rename a campus, select the checkbox next
Delete CampusesUse this button to delete existing campuses in the list. To delete a campus, select the checkbox next to
ExportUse this button to export a database file with all the specifications and background images of one or
ImportUse this button to import database files that define campuses into the RF Plan list. See “Exporting and
AP FQLN MapperThe AP name is a fully-qualified location name (FQLN) in the format APname.floor.building.campus (the
next to the campus name, then click Browse Campus. When you edit a campus, you can access other
RF Plan pages.
to the campus name, then click Rename Campus.
A dialog box appears into which you enter the new name of the campus. Click OK to accept the new
name, or click Cancel to exit this action.
the building ID, then click Delete Campuses.
You can only delete empty campuses. If you attempt to delete a campus that contains one or more
buildings, an error message appears.
more selected campuses in the list. See “Exporting and Importing Files” on page 97.
Importing Files” on page 97.
APname portion of the FQLN must be unique).
The FQLN is not case sensitive and supports a maximum of 249 characters, including spaces. You can
use any combination of characters except a new line, carriage return, and non-printable control
characters.
You can manually set the FQLN for the AP by clicking the AP FQLN Mapper button. Setting the FQLN will
reboot the APs. See “FQLN Mapper” on page 98
You can add, edit, and delete buildings using this page. You may also import and export building information.
The buttons on this page are defined in Table 8.
Table 8 Building List Buttons
ButtonsDescription
New BuildingUse this button to create a new building. When you add or edit a building, you can access other RF Plan
Edit BuildingUse this button to edit existing buildings in the building list. To edit a building, select the checkbox next to
Delete BuildingsUse this button to delete existing buildings in the building list. To delete a building, select the checkbox next
ExportUse this button to export a database file with all the specifications and background images of one or more
ImportUse this button to import database files that define buildings into the RF Plan building list. See “Exporting
LocateUse this button to locate Wi-Fi devices in a building. See “Locate” on page 98.
AP FQLN MapperThe AP name is a fully-qualified location name (FQLN) in the format APname.floor.building.campus (the
pages.
the building ID, then click Edit Building. When you add or edit a building, you can access other RF Plan
pages.
to the building ID, then click Delete Building.
selected buildings in the building list. See “Exporting and Importing Files” on page 97.
and Importing Files” on page 97.
APname portion of the FQLN must be unique).
The FQLN is not case sensitive and supports a maximum of 249 characters, including spaces. You can use
any combination of characters except a new line, carriage return, and non-printable control characters.
You can manually set the FQLN for the AP by clicking the AP FQLN Mapper button. Setting the FQLN will
reboot the APs. See “FQLN Mapper” on page 98.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 81
Page 82
Building Specifications Overview
The Building Specification Overview window displays the default values for a building that you are adding or the
current values for a building that you are modifying.
Figure 8 Plan>New Building>Overview Window
The Overview page includes the following:
Building Dimensions: Your building’s name and dimensions
Access Point Modeling Parameters
Air Monitor Modeling Parameters
Building Dimension button (in the upper right-hand portion of the page). Click on this button to edit the
building dimensions settings.
When you create or edit information for a building, there are several ways you can navigate through RF Plan
windows:
The navigation pane on the left side of the browser window displays RF Plan pages in the order in which they
should be accessed when you are creating a new building. If you are editing a building, simply click on the
page you want to display or modify.
A button for the next page appears in the upper right-hand portion of the page. You can click on this button
to display the next page. For example, the Building Dimension button appears in the Building Specifications
Overview page.
Clicking Apply on editable pages sequences you to the next page. For example, when you click Apply in the
Building Dimensions page, the AP Modeling Parameters page displays.
Building Dimension Page
The Building Dimension page allows you to specify the name and identification for the building and its
dimensions. Table 9 defines the parameters to insert in this window.
Table 9 contains the information for you to enter in the Specification window.
Table 9 New Building Specifications Parameters
ParameterDescription
Campus NameSelect a campus for this building from the drop-down menu.
Building NameThe Building Name is an alphanumeric string up to 64 characters in length.
Width and LengthEnter the rectangular exterior dimensions of the building.
The valid range for this field is any integer from 1 to a value corresponding to 1x10,000.
If your building has an irregular shape, the
width and length should represent the
maximum width and length of the overall
footprint of the building as seen from above.
For example:
When width and length are specified, RF
Plan creates a rectangular area in the
Planning feature pages that represent the
overall area covered by the building. You
need to import an appropriate background
image (see “Floor Editor Dialog Box” on
page 90.) to aid you in defining areas that do
not require coverage or areas in which you
do not wish to deploy APs and AMs (see
“Area Editor Dialog Box” on page 91).
Inter-Floor HeightThis is the distance between floor surfaces in the building. The valid range for this field is any integer
FloorsEnter the number of floors in your building here. The valid range for this field is any integer from 1 to
UnitSpecify the unit of measurement for the dimensions you specified on the page. The choices are feet
from 1 to a value corresponding to 1x10,000. RF Plan uses the inter-floor height to allow APs on one
floor to service users on adjacent floors. If you do not want RF Plan to factor adjacent floors, select a
high inter-floor height value (for example, 300).
NOTE: This is not the distance from floor to ceiling. Some buildings have a large space between the
interior ceilings and the floor above.
255. A building can have a maximum of 255 floors. You can also configure negative floor IDs.
Negative floor IDs let you allocate floors as sub floors, ground floors, basements or other
underground floors, or floors where you do not need to deploy APs.
You specify a negative integer when modifying an existing floor; you do not configure negative floor
settings when adding a building or adding a floor. For more information, see “Level” on page 90.
and meters.
AP Modeling Parameters Page
The AP Modeling Parameters page allows you to specify the information necessary for RF Plan to determine the
appropriate placement of your APs. These settings are on a per-building basis. If you have a mix of APs, choose
the most common one to define the building parameters.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 83
This window allows you to select or control the parameters as defined in Table 10.
Table 10 AP Modeling Parameters
ParameterDescription
Radio TypeUse this drop-down menu to specify the radio type. See “Radio Type” on page 85
AP TypeDell AP device. Use the drop-down menu to select the device type. The supported APs listed in the
Design ModelUse the Coverage, Capacity, and Custom radio buttons to specify a design model to use in the
Overlap FactorUse this field and drop-down to specify an overlap factor. See“Overlap Factor” on page 85.
UsersUse this field to specify the number of users on your WLAN. See “Users/AP” on page 86.
Radio Properties (Desired
Rates and HT Support
Options)
APsUse this field to enter the fixed number of APs to be used in this building’s network (Custom model
drop-down menu are dependent on the selected radio type.
placement of APs. See“Design Model” on page 85
Use this drop-down to define 802.11a, 802.11b/g, and 802.11n settings for the 5 GHz and 2.4 GHz
frequency bands, including high-throughput, data rates, and 40 Mhz channel spacing
See “Radio Properties (Desired Rates and HT Support Options)” on page 86.
Use the drop-down radio type menu to specify radio type of your AP. The available types are defined in Table 11.
Table 11 Radio Type Definitions
ParameterDescription
801.11a/b/gSimultaneous use of 802.11b/g and 802.11a.
802.11b/g2.4 GHz, Direct Spread Spectrum (DSSS) multiplexing with data rates up to 11 Mbps, combined with
802.11a5 GHz Orthogonal Frequency Division Multiplexing (OFDM) with data rates up to 54 Mbps.
802.11a/b/g + nMixed-mode radio type which allows for simultaneous use of 802.11b/g and 802.11n traffic on the 2.4 GHz
802.11b/g + nMixed-mode radio type that allows for simultaneous use of 802.11b/g and 802.11n traffic on the 2.4 GHz
802.11a + nMixed-mode radio type that allows for simultaneous use of 802.11a and 802.11n traffic on the 5 GHz
Orthogonal Frequency Division Multiplexing/Complementary Code Keying (OFDM/CCK) with data rates up to
54 Mbps.
frequency band, and 802.11a and 802.11n traffic on the 5 GHZ frequency band.
frequency band.
frequency band.
Design Model
Three radio buttons, defined in Table 12, allow you to control the kind of model used to determine the number
and type of APs.
Table 12 Design Model Radio Buttons
Radio
Button
CoverageUse this option to let RF Plan automatically determine the number of APs based on desired data
Description
rates and the configuration of your building.
The higher the data rate, the smaller the coverage area, and the more APs that are required.
Coverage is the most common type of installation.
CapacityUse this option to let RF Plan determine the number of APs based on the total number of users,
CustomUse this option to specify a fixed number of APs.
ratio of users to APs, and desired data rates.
Capacity-based coverage is useful for high capacity conference or training rooms, where the APs
could have a high volume of users.
Custom coverage is useful for deployments with a known number of APs or if you have a fixed
project budget.
Overlap Factor
The Overlap Factor is the amount of signal area overlap when the APs are operating. Overlap is important if an
AP fails as it allows the network to self-heal with adjacent APs powering up to assume some of the load from the
failed device. Although there may be no holes in coverage in this scenario, there is likely to be a loss of
throughput. Increasing the overlap allows for higher throughputs when an AP has failed and allows for future
capacity as the number of users increases.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 85
Page 86
You can select a pre-determined value from the drop-down overlap menu or specify a value in the text box to the
left of the drop-down. The following table describes the available options.
Table 13 Overlap Factor Values
Overlap
Factor
100% LowUse this option for buildings that contain open spaces such as warehouses.
150% MediumUse this option for most typical office environments with cubicles and sheetrock walls that have higher
200% HighUse this option for dense deployments such as buildings with poor RF coverage characteristics including
CustomUse this option to enter a custom rate. For most office spaces, 120% works well.
Description
WLAN user density than warehouses.
buildings with thick brick or concrete walls, lots of metal, or excess RF noise (for example, data centers).
When specifying the custom rate, the valid range is 1% to 1000%.
Users/AP
NOTE: The Users text boxes are active only when the Capacity model is selected.
Enter the number of users you expect to have on your WLAN in the Users text box. Enter the number of users
per AP you expect in the Users/AP text box.
The numbers entered in these two text boxes must be non-zero integers between 1-255 inclusive.
Radio Properties (Desired Rates and HT Support Options)
Define 802.11a, 802.11b/g, and 802.11n settings for the 5 GHz and 2.4 GHz frequency bands, including highthroughput, data rates, and 40 Mhz channel spacing.
Table 14 Radio Properties
Radio PropertyDescription
802.11a Desired RateThe desired 802.11a rate defines the estimated transmit rate within the WLAN coverage area.
5 GHz 802.11 (HT) SupportHigh-throughput is available when utilizing the IEEE 802.11n standard and can be enabled on the
5 GHz 802.11n Desired RateThe desired 802.11n rate defines the estimated transmit rate within the WLAN coverage area.
The higher the speed, the smaller the coverage area, and the more APs required. The valid
values are: 54, 48, 36, 24, 18, 12, 9, 6.
This option is only available when 802.11n (HT) support is disabled (unchecked or grayed out).
When an 802.11n radio type, such as 802.11a+nor802.11a/b/g + n, is selected and 802.11n (HT)
support is enabled (checked) on the 5 GHz band, the system will automatically define the 802.11a
rate. The system looks at the defined 802.11n rate and the distance covered by the defined rate;
the system then selects a corresponding 802.11a rate based on the distance covered.
5 GHz frequency band when either the 802.11a+nor802.11a/b/g + n mixed-mode radio type is
selected.
The 802.11n (high-throughput) draft standard supports MIMO (Multiple Input, Multiple Output)
and the option of 40 MHz mode of operation. However, high-throughput can be utilized on a 20
MHz channel or on a 40 MHz channel (bonded channel pair).
The higher the speed, the smaller the coverage area, and the more APs required.
This option is only available when 802.11n (HT) support is enabled (checked).
The valid values when using 20 MHz channel spacing: 6.5, 13.0, 19.5, 26.0, 39.0, 52.0, 58.5, 65.0,
78.0, 104.0, 117.0, 130.0.
The valid values when using 40 MHz channel spacing: 13.5, 27.0, 40.5, 54.0, 81.0, 108.0, 121.15,
802.11b/g Desired RateThe desired 802.11b/g rate defines the estimated transmit rate within the WLAN coverage area.
2.4 GHz 802.11 (HT) SupportHigh-throughput is available when utilizing the IEEE 802.11n standard and can be enabled on the
2.4 GHz 802.11n Desired Rate The desired 802.11n rate defines the estimated transmit rate within the WLAN coverage area.
Use 40 MHz Channel Spacing—40 MHz operation, which supports higher data rates by utilizing
two 20 MHz channels as a bonded pair, requires that high-throughput be enabled (checked). 40
MHz mode is most often utilized on the 5 GHz frequency band due to a greater number of
available channels.
This option is only available when 802.11n (HT) support is enabled (checked).
The higher the speed, the smaller the coverage area, and the more APs required. The valid
values are: 54, 48, 36, 24, 18, 12, 9, 6, 11, 5.5, 2, 1.
This option is only available when 802.11n (HT) support is disabled (unchecked or grayed out).
When an 802.11n radio type, such as 802.11g+nor802.11a/b/g + n, is selected and 802.11n (HT)
support is enabled (checked) on the 2.4 GHz band, the system will automatically define the
802.11b/g rate. The system looks at the defined 802.11n rate and the distance covered by the
defined rate; the system then selects a corresponding 802.11b/g rate based on the distance
covered.
2.4 GHz frequency band when either the
802.11g+nor802.11a/b/g + n mixed-mode radio type is selected.
The 802.11n (high-throughput) draft standard supports MIMO (Multiple Input, Multiple Output)
and the option of 40 MHz mode of operation. However, high-throughput can be utilized on a 20
MHz channel or on a 40 MHz channel (bonded channel pair).
The higher the speed, the smaller the coverage area, and the more APs required.
This option is only available when 802.11n (HT) support is enabled (checked).
The valid values when using 20 MHz channel spacing: 6.5, 13.0, 19.5, 26.0, 39.0, 52.0, 58.5, 65.0,
78.0, 104.0, 117.0, 130.0.
The valid values when using 40 MHz channel spacing: 13.5, 27.0, 40.5, 54.0, 81.0, 108.0, 121.15,
135.0, 162.0, 216.0, 243.0, 270.0.
2.4 GHz Use 40 MHz Channel
Spacing
40 MHz operation, which supports higher data rates by utilizing two 20 MHz channels as a
bonded pair, requires that high-throughput be enabled (checked). Due to a limited number of
channels on the 2.4 GHz frequency band, 40 MHz mode is most often utilized on the 5 GHz
frequency band where a greater number of channels are available.
This option is only available when 802.11n (HT) support is enabled (checked).
AM Modeling Page
The AM Modeling page allows you to specify the information necessary for RF Plan to determine the appropriate
placement of your AMs.
NOTE: The AM coverage rate refers to the rate at which an AM captures packets. RF Plan uses that information to determine the
placement of AMs.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 87
Page 88
Figure 11 AM Modeling Page
Controls on this page allow you to select the following functions, which are described in more detail in this
section:
Table 15 AM Modeling Radio Buttons
Radio ButtonDescription
Design ModelUse these radio buttons to specify a design model to use in the placement of AMs. See “Design
Monitor RatesUse this drop-down menu to specify the desired monitor rate for the AMs. See “Monitor Rates” on
AMsUse this field to manually specify the number of AMs to deploy (Custom Model only).
Models” on page 88.
page 88.
Design Models
Two radio buttons on the page allow you to specify the model used to determine the number and type of APs.
Table 16 Design Model Radio Buttons
Radio ButtonDescription
CoverageUse this option to let RF Plan automatically determine the number of AMs based on desired monitor
CustomUse this option to specify a fixed number of AMs. When the AM Plan portion of RF Plan is executed,
NOTE: The monitor rates you select for the AMs should be less than the data rates you selected for the APs. If you set the rate for
the AMs at a value equal to that specified for the corresponding PHY type AP, RF Plan allocates one AM per AP. If you specify a
monitor rate greater than the data rate, RF Plan allocates more than one AM per AP.
rates and the configuration of the building.
Desired rate is selectable from 1 to 54 Mbps in the Coverage model.
RF Plan distributes the AMs evenly.
Monitor Rates
Use the drop down menus to select the desired monitor rates for the 2.4 Ghz (802.11b/g) and 5 GHz (802.11a)
frequency bands. The available monitor rates that display in drop-down lists will vary: these rates are dependent
on the radio type selected on AP modeling page and they will also be adjusted to accommodate for 20 MHz vs. 40
MHz channel spacing when 802.11n (HT) support is enabled.
NOTE: This option is available only when the coverage design model is selected.
Planning Floors Page
The Planning Floors page enables you to see the footprint of your floors.
You can select or adjust the features as described in Table 17:
Table 17 Floor Planning Features
FeatureDescription
ZoomUse this drop-down menu or type a zoom factor in the text field to increase or decrease
Approximate Coverage Map (select
radio type)
Edit FloorClick on this link to launch the Floor Editor dialog box. See “Floor Editor Dialog Box” on
New in Areas sectionClick on this link to launch the Area Editor dialog box. See “Area Editor Dialog Box” on
New in Suggested Access Points and
Air Monitors section
Status in Deployed Access Points
and Air Monitors section
the size of the displayed floor area.
See “Zoom” on page 89.
Use this drop-down to select a particular radio type for which to show estimated
coverage.
See “Approximate Coverage Map” on page 90.
page 90.
page 91.
Click on this link to launch the Suggested Access Point Editor dialog box. See “Access
Point Editor Dialog Box” on page 92.
The Status column displays the status of each AP for the floor you are viewing within a
live network.
Up: AP is up (live). The corresponding AP icon on the floor map will display a live AP icon.
Down: AP is down. The corresponding AP icon on the floor map will display with a red
“X” over the AP icon symbolizing that the AP is down.
Zoom
The Zoom control sets the viewing size of the floor image. It is adjustable in finite views from 10% to 1000%. You
may select a value from the drop-down zoom menu or specify a value in the text box to the left of the drop-down.
When you specify a value, RF Plan adjusts the values in the drop-down to display a set of values both above and
below the value you typed in the text box.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 89
Page 90
Approximate Coverage Map
Select a radio type from the Coverage drop-down menu to view the approximate coverage area for each of the APs
that RF Plan has deployed in AP Plan or AM Plan. Adjusting the coverage values help you to understand how the
AP coverage works in your building.
NOTE: You will not see coverage areas displayed here until you have executed either an AP Plan or an AM Plan.
Figure 13 Coverage Map Example
Floor Editor Dialog Box
The Floor Editor dialog box allows you to modify the floor level, specify the background image, and name the
floor. The Floor Editor is accessible from the Floors Page by clicking on the Edit Floor link.
Figure 14 Floor Editor Dialog Box
Level
When modifying an existing floor, you can configure it with a negative integer to specify a basement or some
other underground floor that you do not need or want to deploy APs.
To configure a negative floor, specify a negative integer in the Level field. The valid range is -100 to 255; however,
a building can have a maximum of 255 floors.
Naming
You may name the floor anything you choose as long as the name is an alphanumeric string with a maximum
length of 64 characters. The name you specify appears to the right of the Floor Number displayed above the
background image in the Planning view.
Background Images
You can import a background image (floor plan image) into RF Plan for each floor. A background image is
extremely helpful when specifying areas where coverage is not desired or areas where an AP/AM is not to be
physically deployed.
Use the guidelines in this section when importing background images. By becoming familiar with these
guidelines, you can ensure that your graphic file is edited properly for pre- and post-deployment planning.
Edit the image—Use an appropriate graphics editor to edit the file as needed.
Scale the image—If the image is not scaled, proportional triangulation and heat map displays can be incorrect
when the plan is deployed.
Calculate image dimensions—Calculate the image pixels per feet (or meters) against a known dimension. Use
that value to calculate the width and length of the image.
Leave a border around the image—When creating the image, leave a boarder around the image to help
triangulate Wi-Fi devices outside of the building.
Multiple floors—If your building has multiple floors, make sure there is a common anchor point for all floors;
for example an elevator shaft, a staircase, and so on.
Larger dimensions—Use larger dimensions only for scaling to more accurately calculate the full dimensions.
For best results, final floor images 2048 X 2048 and smaller perform best.
Select a background image using the Browse button on the Floor Editor dialog box.
File Type and Size
Background images must be JPEG format and may not exceed 2048 X 2048 pixels in size. Attempting to
import a file with a larger pixel footprint than that specified here results in the image not scaling to fit the
image area in the floor display area.
Because background images for your floors are embedded in the XML file that defines your building, you
should strongly consider minimizing the file size of the JPEGs that you use for your backgrounds. You can
minimize the file size by selecting the maximum compression (lowest quality) in most graphics programs.
NOTE: The ArubaOS WebUI displays floor plans using Adobe Flash Player, which does not support progressive JPEG images. If
you have a progressive JPEG image you want to use as background image, open the image in an image editing program and resave the image with standard/baseline compression.
Image Scaling
Images are scaled (stretched) to fit the display area. The display area aspect ratio is determined by the
building dimensions specified on the Dimension page.
Area Editor Dialog Box
The Area Editor dialog box allows you to specify areas on your building floors where you either do not care about
coverage, or where you do not want to place an AP or AM.
Open the Area Editor dialog box by clicking New in the Areas section.
You specify these areas by placing them on top of the background image using the Area Editor.
Figure 15 Area Editor Dialog Box
Naming
Logical name of area, as an alphanumeric string consisting of 1 to 64 characters. Dell recommends that you
provide a meaningful name to the area to ensure that it is readily identifiable.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 91
Page 92
Location and Dimensions
Specify absolute coordinates for the lower left corner and upper right corner of the box that represents the area
being defined.
Begin the measurement with the lower left corner of the rectangular display area that represents your
building’s footprint.
The coordinates of the upper right-hand corner of the display area are the absolute values of the dimensions
you provided for the building.
Location settings are zero-based. Values range from 0 to (height -1 and width -1). For example, coordinates of the
upper right corner for a building that measures 200 ft. wide x 400 ft. in length, would be 199 and 399.
NOTE: The unit of measurement displayed as either feet or meters is based on your building settings. See “Building Dimension
Page” on page 82 for details about configuring building parameters.
You may also use the drag and drop feature of the Area Editor to drag your area to where you want it and resize it
by dragging one or more of the handles displayed in the corners of the area.
Area Types
Select one of the area types from the drop-down menu: Don’t Care, Don’t Deploy, or 802.11n Zone.
Don’t Care: Coverage is not required in the area specified in this dialog box. This specification typically
applies to areas where coverage cannot be guaranteed.
This setting results in the display of an orange rectangle at the associated area in the floor diagram.
Don’t Deploy: No APs are to be positioned in the area specified in this dialog box.
This setting results in display of a yellow rectangle at the associated area in the floor diagram.
802.11n Zone: 802.11n compliant APs are required to be positioned in the area specified in this dialog box
only.
This setting results in display of a green rectangle at the associated area in the floor diagram.
You cannot right-click within an existing area to add another area inside of it. For instance, if a Don’t Care or
Don’t Deploy Area needs to overlap with an 802.11n Zone, you must create each of the areas outside of one
another and then move them to the correct position of overlap. You can click and drag the areas to the
appropriate positions of overlap, or you can right-click on the area to modify its location.
Access Point Editor Dialog Box
The Access Point Editor allows you to manually create or modify a suggested AP.
To create an AP, open the Access Point Editor dialog box by clicking New in the Suggested Access Points and Air
Monitors section.
To modify an existing AP, place the cursor over the AP and click it to display the Suggested Access Point Editor
dialog box.
RF Plan automatically names APs using the default convention ap number, where number starts at 1 and
increments by one for each new AP. When you manually create an AP, the new AP is assigned the next number
and is added to the bottom of the suggested AP list.
You may name an AP anything you wish. The name must consist of alphanumeric characters and be 64 characters
or less in length.
Fixed
Fixed APs do not move when RF Plan executes the positioning algorithm.
NOTE: You might typically set a fixed AP when you have a specific room, such as a conference room, in which you want saturated
coverage. You might also want to consider using a fixed AP when you have an area that has an unusually high user density.
Choose Yes or No from the drop-down menu. Choosing Yes locks the position of the AP as it is shown in the
coordinate boxes of the Access Editor. Choosing No allows RF Plan to move the AP as necessary to achieve best
performance.
Radio Types
The Radio drop-down menu allows you to specify what frequency band the AP uses. You can choose from one of
the following:
802.11a/b/g (2.4 GHz and 5 GHz frequency bands)
802.11a (5 GHz frequency band)
802.1 b/g (2.4 GHz frequency band)
NOTE: 802.11n (HT) support features are available on the 2.4 or 5 GHz frequency band. The availability of these options on these
frequency bands is dependent on the radio (frequency band) chosen and whether or not these feature were enabled on the AP
modeling page at the building level.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 93
Page 94
X and Y Coordinates
The physical location of the AP is specified by X-Y coordinates that begin at the lower left corner of the display
area. The numbers you specify in the X and Y text boxes are whole units. The Y-coordinate increases as a point
moves up the display and the X-coordinate increases as they move from left to right across the display.
802.11 Types
The 802.11 b/g and 802.11a Type drop-down menus allow you to choose the mode of operation for the AP. You
may choose to set the mode of operation to Access Point or Air Monitor.
802.11 Channels
The 802.11a and 802.11b/g channel drop-down menus allow you to select from the available channels.
NOTE: The available channels vary depending on the regulatory domain (country) in which the device is being operated.
802.11 Power Levels
The power level drop-down menus allow you to specify the transmission power of the AP. Choices are OFF, 0, 1,
2, 3, and 4. A setting of 4 applies the maximum Effective Isotropic Radiated Power (EIRP) allowed in the
regulatory domain (country) in which you are operating the AP.
802.11n Features
802.11n (HT) Support (2.4 or 5 GHz): Specify if 802.11n high-throughput support should be enabled on this
AP.
In order to enable high-throughput on a new AP being added to the plan at the floor level, 802.11n (HT)
support must first be enabled at the building level within the AP modeling parameters. If not, this option will
be grayed out. See “AP Modeling Parameters Page” on page83 for details about AP modeling parameters.
Use 40 MHz Channel (2.4 or 5 GHz): Specify if 802.11n high-throughput support should utilize a 40 MHz
channel (bonded channel pair).
In order to select a valid 40 MHz channel for a new AP being added at the floor level, use of 40 MHz channel
spacing must first be enabled at the building level within the AP modeling parameters. If not, this option will
be grayed out. See “AP Modeling Parameters Page” on page83 for details about AP modeling parameters.
If high-throughput is enabled and use of a 40 MHz channel pair is not enabled, a 20 Mhz channel will be
utilized.
Memo
The Memo text field allows you to enter notes regarding the AP. You can enter a maximum of 256 alphanumeric
characters in the Memo field.
The AP Plan page uses the information entered in the modeling pages to locate APs in the building(s) you
described. All of the options on the Floors page can also be viewed and configured on the AP Plan page. The AP
Plan page also includes some additional options, such as initializing, optimizing, and fixing AP/AM locations.
Figure 17 AP Planning
Initialize
Initialize the Algorithm by clicking the Initialize button. This makes an initial placement of the APs and prepares
RF Plan for the task of determining the optimum location for each of the APs. As soon as you click Initialize you
see the AP symbols appear on the floor plan.
Colored circles around the AP symbols on the floor plan indicate the approximate coverage of the individual AP
and the color of the circle represents the channel on which the AP is operating. The circles appear when you select
an approximate coverage value on one of the Floors pages. You may also click an AP icon and drag it to manually
reposition it.
Optimize
Click Optimize to launch the optimizing algorithm. The AP symbols move on the page as RF Plan finds the
optimum location for each.
The process may take several minutes. You may watch the progress on the status bar of your browser. The
algorithm stops when the movement is less than a threshold value calculated based on the number of APs. The
threshold value may be seen in the status bar at the bottom of the browser window.
Viewing the Results
The results of optimizing algorithm may be viewed two ways: graphically and in a table of suggested APs. You may
obtain information about a specific AP by placing the cursor over its symbol. An information box appears that
contains information regarding location, radio type, high-throughput support, channel(s), and power.
The Suggested Access Points and Air Monitors table lists the coordinates, power, location, power setting, highthroughput support, and channel(s) for each of the APs that are shown in the floor plan.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 95
Page 96
Fix All Suggested AP/AMs
Fix existing AP/AM locations at the building level. If AP/AM locations are fixed, AP/AMs will not move from their
fixed locations during initialization or optimization. Clicking on this button will fix the locations of existing APs
and AMs. You only need to click this button on either the AP or AM Plan page.
AM Plan Page
The AM Plan page uses the information entered in the modeling pages to locate AMs in the building(s) you
described and calculate the optimum placement for the AMs. All of the options on the Floors page can also be
viewed and configured on the AM Plan page. The AM Plan page also includes some additional options, such as
initializing, optimizing, and fixing AP/AM locations.
Initialize
Initialize the Algorithm by clicking Initialize. This makes an initial placement of the AMs and prepares RF Plan
for the task of determining the optimum location for each of the AMs. When you click Initialize, the AM
symbols appear on the floor plan.
Optimize
Click Optimize to launch the optimizing algorithm. The AM symbols move on the page as RF Plan finds the
optimum location for each.
The process may take several minutes. You may watch the progress on the status bar of your browser. The
algorithm stops when the movement is less than a threshold value calculated based on the number of AMs. The
threshold value may be seen in the status bar at the bottom of the browser window.
Viewing the Results
Viewing the results of the AM Plan feature is similar to that for the AP Plan feature.
The results of optimizing algorithm may be viewed two ways: graphically and in a table of suggested AMs. You
may obtain information about a specific AM by placing the cursor over its symbol. An information box appears
that contains information about the exact location, PHY type, high-throughout-support, channel, power, and so
on.
The Suggested Access Points and Air Monitors table lists the coordinates, power, location, power setting, and
channel for each of the AMs that are shown in the floor plan.
Fix All Suggested AP/AMs
Fix existing AP/AM locations at the building level. If AP/AM locations are fixed, AP/AMs will not move from their
fixed locations during initialization or optimization. Clicking on this button will fix the locations of existing APs
and AMs. You only need to click this button on either the AP or AM Plan page.
Both the Campus List page and the Building List page have Export and Import buttons, which allow you to
export and import files that define the parameters of your campus and buildings. You can export a file so that it
may be imported into and used to automatically configure a controller. On a controller, you can import a file that
has been exported from another controller or from the standalone version of RF Plan that runs as a Windows
application.
NOTE: The WebUI version of RF Plan only supports JPEG file formats for background images.
The files that you export and import are XML files and, depending on how many buildings are in your campus,
floors are in your buildings, and how many background images you have for your floors, the XML files may be
quite large. (See “Background Images” on page90.)
NOTE: In order for the WebUI RF Plan tool to import and read a standalone plan that incorporates 802.11n standard APs and was
originally created in the Java-based standalone RF Plan tool, the plan must be exported out from the standalone tool using the
Controller WebUI Format (version 3.0).
Export Campus
To export a file that defines the parameters of one or more campuses, including all of its associated buildings,
select the campus(es) to be exported in the Campus List page and then click Export.
After you click the Export button, you are prompted to include the background images.
When exporting a campus file, Dell recommends that you click OK to export the background images. If you click
Cancel, the exported file does not include the background images. The File Download window appears.
From the File Download window, click Save to save the file. The Save As dialog box appears. From here, navigate
to the location where you want to save the file and enter the name for the exported file. When naming your
exported file, be sure to give the file the.XML file extension, for example, My_Campus.XML.
Exported campus files include detailed information about the campus and the selected building(s).
Import Campus
You can import only XML files exported from another controller or from the standalone version of RF Plan that
runs as a Windows application.
NOTE: Importing any other file, including XML files from other applications, may result in unpredictable results.
To import a file that defines the building parameters of one or more campuses, click the Import button in the
Campus List page. The Import Buildings page appears, as described in “Import Buildings Page” on page98.
Export Buildings Page
To export a file that defines the parameters of one or more buildings, select the building(s) to be exported in the
Building List page and then click Export.
After you click the Export button, you are prompted to include the background images.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 97
Page 98
When exporting a building file, Dell recommends that you click OK to export the background images. If you click
Cancel, the exported file does not include the background images. The File Download window appears.
From the File Download window, click Save to save the file. The Save As dialog box appears. From here, navigate
to the location where want to save the file and enter the name for the exported file. When naming your exported
file, be sure to give the file the.XML file extension, for example, My_Building.XML.
Exported building files include the name of the campus to which the building belongs; however, detailed campus
parameters are not included.
Import Buildings Page
You can import only XML files exported from another controller or from the standalone version of RF Plan that
runs as a Windows application.
NOTE: Importing any other file, including XML files from other applications, may result in unpredictable results.
To import a file that defines the parameters of one or more buildings, click the Import button in the Building List
page.
In the Import Buildings page, click Browse to select the file to be imported, then click the Import button.
Locate
The Locate button on the Building List page allows you to search for APs, AMs, monitored clients, etc. on a
building by building basis. To use this feature, select the building in which you want to search, and click Locate.
The Target Devices table displays information on each of these devices. To add a device, click Add Device. To
delete a device, click Remove Device. To select a device, click Choose Devices.
FQLN Mapper
Both the Campus List page and the Building List page have the AP FQLN Mapper button, which allows you to
create a fully-qualified location name (FQLN) for the specified AP/AM in the format
APname.Floor.Building.Campus.
The FQLN is not case sensitive and supports a maximum of 249 characters, including spaces. You can use any
combination of characters except a new line, carriage return, and non-printable control characters.
You can use the FQLN mapper for multiple purposes, including:
Searching for deployed APs/AMs
Configuring the AP name in the form APname.Floor.Building.Campus
To use this feature, select one or more campuses from the Campus List page, or one or more buildings from the
Building List page, and click AP FQLN Mapper.
The AP FQLN Mapper page appears. From here, you can search for deployed APs by entering one or more
parameters in the Search fields, view the results in the Search Results table, configure the FQLN, and modify the
location of an AP.
To search for deployed APs, enter information in the Search fields and click Search.
You can perform a search based on one or more of the following AP properties:
Table 18 AP Property Search
PropertyDescription
AP NameLogical name of the AP or AM. You can enter a portion of the name to widen the search.
Wired MACMAC address of the AP or AM. You can enter a portion of the MAC address to widen the
IP AddressIP address of the AP or AM. You can enter a portion of the IP address to widen the search.
FQLNFully-qualified location name of the AP, in the form APname.floor.building.campus. You can
Serial NumberSerial number of the AP. You can enter a portion of the serial number to widen the search.
StatusCurrent state of the AP, including Up/Down/Any.
search.
enter a portion of the FQLN to widen the search.
Use the drop-down list to the right of the Number of results per page to specify the number of APs to display in
the search results.
After entering the search criteria, you can either click Reset to clear the entries or click Search to search for APs. If
you click Search, the results are displayed in the Search Result table:
You can view the information in ascending or descending order. By default, the display is in ascending order,
based on the AP name (the white arrow indicates the row that is being used to sort the information). Left-click on
a column head to view the information in ascending or descending order (you may need to click multiple times to
get the desired display).
In addition to displaying AP names, wired MAC addresses, serial numbers, IP addresses, FQLNs, and AP status,
the Search Result table displays the AP type and when it was last updating.
From here you can modify the attributes that create the FQLN for the selected AP, using the following dropdown lists:
Campus—Displays the campus where the AP is deployed. To deploy the AP in a different campus, select a
campus form the drop-down list. The Campus defines the buildings and floors displayed.
NOTE: This drop-down list only displays the existing campuses that you are managing. To add a new campus, see “Campus List
Page” on page 80.
Dell PowerConnect W-Series ArubaOS 6.1 | User GuideRF Plan | 99
Page 100
Building—Displays the building where the AP is deployed. To deploy the AP in a different building, select a
building from the drop-down list.
NOTE: This drop-down list only displays the available buildings in the selected campus. To
add a new building, see “Building List Pane” on page 81.
Floor—Displays the floor where the AP is deployed. To deploy the AP on a different floor, select a floor from
the drop-down list.
NOTE: This drop-down lists only displays the available floors in the selected building. To add a new floor, see “Planning Floors
Page” on page 88.
To submit your changes, click Set FQLN. Setting the FQLN reboots the APs.
Using the FQLN Mapper in the AP Provision Page
The AP Provision page (available from Configuration > Wireless > AP Installation) allows you to set an FQLN
during the AP provisioning process.
Scroll to the FQLN Mapper near the bottom of the AP Provision page to modify the following attributes that
create the FQLN:
Campus
Building
Floor
The AP name appears in the AP List at the bottom of the page and will be used when provisioning the AP. To
rename an AP, enter the new name in the AP Name field.
To retain the old FQLN value when reprovisioning an AP, do not select the Overwrite FQLN checkbox. However,
if you configure new values for the campus, building, and floor settings, the FQLN value is changed, even if the
Overwrite FQLN checkbox is selected. To remove a previously configured value, you can select N/A for a specific
attribute.
If you provision more than one AP, the selected value for the campus, building, and floor is based on the first
selected AP and applies to all APs. Only the AP name will be different as each AP must have a unique name.
Using the WebUI
1. Navigate to the Configuration > Wireless > AP Installation page. The list of discovered APs appears in the
page.
2. Select the AP you want to set an FQLN, and click Provision.
3. Modify the FQLN attributes:
In the Provisioning page, scroll to the FQLN Mapper near the bottom of the page and modify the campus,
building, and floor attributes.
Optionally, if you want rename an AP, scroll to the AP List at the bottom of the page and enter the new
name in the AP Name field. For more information about AP names, see Chapter 4, “Access Points” on
page107.
4. Click Apply and Reboot.
Using CLI
Reprovisioning the AP causes it to automatically reboot. When configuring the FQLN, you may also provision
other AP settings.