B ME User Guide 82
B ME User Guide 82
2
First Published: 2015-11-30
Last Modified: 2021-02-16
Thats normal procedure. If you set a static address and if the ap cant join a
Americas Headquarters wlc it falls back to DHCP.
Cisco Systems, Inc.
It seems like your issue is a join problem. Can you share what method of
170 West Tasman Drive joining are you using?
San Jose, CA 95134-1706
USA DHCP Option 43
http://www.cisco.com
Tel: 408 526-4000 DNS
800 553-NETS (6387) Forward UDP
Fax: 408 527-0883
Broadcast
You can manually prime your AP. Go to CLI in the AP and type the
following:
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (1721R)
© 2015–2021 Cisco Systems, Inc. All rights reserved.
CONTENTS
Managing SNMP 59
Setting Up System Message Logging 59
Resetting the Mobility Express Controller 61
Rebooting the Mobility Express Controller 61
Saving Controller Configuration 61
Note The documentation set for this product strives to use bias-free language. For purposes of this documentation
set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial
identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be
present in the documentation due to language that is hardcoded in the user interfaces of the product software,
language used based on RFP documentation, or language that is used by a referenced third-party product.
Note • APs listed under primary APs can also function as subordinate APs.
• The software on the APs listed under primary APs can be converted from Cisco Mobility Express to
CAPWAP Lightweight AP software and vice versa. For ordering information, visit the Cisco Aironet
Access Points Ordering Guide
AP models that are supported only as subordinates require a CAPWAP-based lightweight AP software image.
The Cisco Mobility Express software for your AP model can be downloaded from: https://software.cisco.com/
download/navigator.html.
From the Download Software window, browse to your AP model and then select Mobility Express Software
to view a list of currently available software, with the latest the top. The software releases are labeled as
follows to help you determine which release to download:
• Early Deployment (ED)—These software releases provide new features, new hardware platform support,
and bug fixes.
• Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software
maintenance.
• Deferred (DF)—These software releases have been deferred. We recommend that you migrate to an
upgraded release.
Cisco Mobility Express software for Cisco Wireless Release 8.2 is as follows:
• Your laptop should have a compatible browser. For a list of browsers compatible with the Cisco Mobility
Express wireless controller web interface and the initial configuration wizard, see Supported Browsers,
on page 69.
• If your network is using universal regulatory domain access points, then you will need prime the access
point to the right regulatory domain, before the APs start serving clients. See the Cisco Aironet Universal
AP Priming and Cisco AirProvision User Guide, at this URL: http://www.cisco.com/c/en/us/td/docs/
wireless/access_point/ux-ap/guide/uxap-mobapp-g.html.
After these prerequisites are met, proceed to Configuring the Switch Port, on page 6.
Note A CLI-based Initial Configuration Wizard is also available, but recommended only for advanced users. See
Using the CLI Initial Configuration Wizard, on page 63.
After the switch port configuration is done, proceed to Starting the Initial Configuration Wizard, on page 6.
Step 2 Connect the Wi-Fi-enabled laptop to the CiscoAirProvision SSID advertised by the AP, using Wi-Fi. The password is
password.
The laptop gets an IP address from the subnet 192.168.1.0/24.
Step 3 Using a supported browser, go to http://192.168.1.1, which is redirected to the initial configuration wizard.
The initial configuration wizard’s admin account window is displayed in your browser.
What to do next
If the initial configuration wizard's admin account window is displayed, then proceed to Using the Initial
Configuration Wizard , on page 7, else proceed to Checking if an AP has CAPWAP Lightweight AP Software
or Cisco Mobility Express Software, on page 19.
The banner on this window shows the name of the AP model on which the Cisco Mobility Express wireless
controller is being configured, for example, Cisco Aironet 1830 Series Mobility Express.
Create an admin account on the controller by specifying the following parameters and then clickStart:
• Enter an administrative username. You can enter up to 24 ASCII characters.
• Enter a password. You can enter up to 24 ASCII characters.
When specifying a password, ensure the following:
• The password must contain characters from at least three of the following classes, lowercase letters,
uppercase letters, digits, and special characters.
• No character in the password can be repeated more than three times consecutively.
• The new password must not be the same as the associated username or the username reversed.
• The password must not be cisco, ocsic, or any variant obtained by changing the capitalization of
the letters in the word Cisco. In addition, you cannot substitute 1, I, or ! for i, 0 for o, or $ for s.
The IPv4 address or the FQDN name, which you specify here, will be applied to the server with NTP
Index 1, thereby overwriting its default FQDN, 0.ciscome.pool.ntp.org . For editing NTP server details,
go to Management > Time.
• Management IP Address—Enter the IP address for managing the controller.
• Subnet Mask—Enter the subnet mask for the controller.
• Default Gateway—Enter the default gateway for the controller.
• Pass Phrase—If you have chosen WPA2 Personal security, specify the PSK here.
• VLAN—Choose Employee VLAN to have the same VLAN as that defined for the Employee Network
or create a New VLAN (with a VLAN ID ranging from 1 to 4094).
• VLAN ID—Specify the VLAN ID for the new VLAN.
• DHCP Server Address—This is optional.
Note If you do not enable RF Parameter Optimization during the initial configuration wizard, then client density
is set to Typical (the default value), and RF traffic type is set to Data (the default value).
Once you apply these configuration settings, the access point reboots and the controller restarts. You can now
proceed to Logging in to Cisco Mobility Express , on page 22.
What to do next
AP Image Type: MOBILITY EXPRESS IMAGE This means that the AP has the Cisco Mobility
Express software, but is running as a CAPWAP
AP Configuration: NOT MOBILITY EXPRESS CAPABLE
lightweight AP.
This AP is currently not configured to run as Mobility
Express controller, does not take part in the primary
AP election process either, and hence does not
broadcast the the CiscoAirProvision SSID. This AP
can, however, function as a subordinate AP in a
Mobility Express network.
To enable the Mobility Express controller
functionality of this AP, run the command ap-type
mobility-express tftp on the AP console. The AP
will reboot, come back online, and take part in the
primary AP election process. If and when it is elected
as primary, it will broadcast the CiscoAirProvision
SSID.
The AP Image Type and AP Configuration fields This means that the AP has a CAPWAP lightweight
are not present in the output AP software and not Cisco Mobility Express software.
Proceed to Converting from CAPWAP Lightweight
AP to Cisco Mobility Express Software, on page 20.
Tip If you face issues with converting the AP software to a Cisco Mobility Express software, upgrade the AP
CAPWAP software to the latest AP software version ap3g3-k9w8-tar.153-3.JD.tar. Now, you can convert the
CAPWAP software to the Cisco Mobility Express software AIR-AP2800-K9-ME-8-3-102-0.tar.
This issue occurs in Mobility Express-capable APs shipped with default images or a version of the images
prior to Cisco Wireless Release 8.3. This is due to insufficient space in the AP’s memory or because the AP
has been started in U-boot mode where the image is not found in flash.
Note The following procedure shows a conversion from the 8.1.122.0 Lightweight AP release on an 1850 series
AP, and hence uses the corresponding software file. Ensure that you use the appropriate software file depending
on the release you are converting from and the AP model.
Step 1 Download the AIR-AP1850-K9-8.1.122.0.tar software file from Cisco.com to the TFTP server.
On the Download Software page, for a given release, this .TAR file is labeled, 'Software to be used for conversion from
Lightweight Access Points only'.
Step 3 Log in to the AP using the username Cisco and password Cisco. Both are case-sensitive.
This is the default factory-shipped username and password on all Cisco Aironet APs.
Step 4 To convert the AP from CAPWAP lightweight AP software to Cisco Mobility Express software, use the ap-type
mobility-express tftp://<tftp server ip-address>/<filename of TAR file with path from root on the TFTP server>
command.
The software file is downloaded to the AP, and is written to the AP's flash memory. The AP reboots with a Mobility
Express-capable configuration and starts broadcasting the CiscoAirProvison SSID.
What to do next
Proceed to Starting the Initial Configuration Wizard, on page 6.
For an alternative to the above conversion process, using the .ZIP file, see Alternative Method for CAPWAP
to Mobility Express Conversion, on page 72.
To convert an AP from Mobility Express type to CAPWAP type, see Converting an AP from Mobility Express
to CAPWAP Type, on page 73.
Step 1 Download the latest Cisco Mobility Express bundle from Cisco.com to the TFTP server. This pack is either in .zip format
(for Windows) or .tar format (Linux or Mac OSX) and contains the software images for all the supported APs.
Step 2 Unzip the software pack to a folder on the TFTP server.
Step 3 Provide the path to the folder in the Management > Software Update > File Path field.
Step 4 Perform a software update. .
What to do next
Managing Associated Access Points, on page 47
What to do next
After you log in, the default landing page is the Network Summary window. For more information, see
About the Cisco Mobility Express Monitoring Service, on page 27.
1 The side pane of the web interface. This is main navigational pane using which you can navigate
to the various sub-sections in the web interface.
2 The title of the web interface. It indicates the AP model of the primary AP (on which the integrated
controller functionality is currently operating)
4 Click to save the current controller configuration to the NVRAM. For more information, see
Saving Controller Configuration, on page 61.
5 Click to view the current system information or to log off the controller web interface.
6 The Mobility Express Network Monitoring section. For more information, see About the Cisco
Mobility Express Monitoring Service, on page 27.
7 The Wireless Settings section, where you can administer associated APs, manage WLANs, WLAN
user accounts, and guest user accounts.
For more information, see Specifying Wireless Settings, on page 41.
8 The Management section, where you can set management access parameters, manage admin
accounts, network time, and perform software updates.
For more information, see Managing the Network, on page 51.
9 The Advanced section, where you can set SNMP settings, sys log settings, and perform a reset to
factory default.
For more information, see Using Advanced Settings and Operations, on page 59.
Note • All the parameters on the Network Summary window are read-only parameters.
• This page is automatically refreshed every 30 seconds.
Viewing WLANs
The WLAN Configuration window lists all the WLANs that are currently configured on the primary AP’s
controller, along with the following details for each WLAN:
• Active—Whether the WLAN is enabled or disabled.
• Name—Name of the WLAN
• Security Policy
• Radio Policy
Tip The total number of active WLANs is displayed at the top of the page. If the list of WLANs spans multiple
pages, you can browse these pages by clicking the page number links or the forward and backward icons.
Step 2 In the Wireless Networks summary window, click the status icon or count display icon to view high-level details of the
corresponding WLAN, such as the Active status, Name, Security Policy, and Radio Policy.
You can also add new WLANs from this page. For details, see Adding a WLAN, on page 42.
Step 2 In the Active Clients summary section, click the count display icon to view high-level details of the client device.
The information shown includes:
• General details.
• Connectivity status graphic.
• Top applications on the client that are using the network connection.
• Mobility State graphic.
• Network, QoS, Security and Policy details.
• Client ping and packet capture tests.
Click the downward facing arrow on the top right of the column headers to customize the details displayed in the table
either to hide or show desired columns or to filter the table view based on desired parameters.
• Name of the AP through which the client is connected to the controller, along with the type of connection
(for example, Flexconnect), the AP's IP address, and the AP's model number.
• Nature of connection between the AP and the client. For example, wireless 802.11n 5 GHz connection.
• Name of the client, type of client (for example, Microsoft Workstation), VLAN ID of the client, and the
client's IP address.
Note This feature does not work on subordinate APs having Cisco AP-OS, namely the Cisco Aironet 1810W, 1830,
1850, 2800, and 3800 Series access points.
The Client Packet Capture feature allows network administrators to capture packets flowing to, through, and
from an AP, while the AP continues to operate normally. The packets are captured and exported to an FTP
server, where you can do an offline analysis by using a tool such as Wireshark. This feature facilitates
troubleshooting by helping to gather information about the packet format, application analysis, and security.
Points to Note
• Packet capture can be enabled for only one client at a time.
• The packets are captured and dumped in the order of arrival or transmission of packets, except for beacons
and probe responses. The packet capture contains information such as channel, RSSI, data rate, SNR,
and timestamp. Each packet is appended with additional information from the AP.
• A file is created on the FTP server for each AP based on AP name, controller name and timestamp.
• If the FTP transfer time is slower than the packet rate, some of the packets may not appear in the capture
file.
• If the buffer on the AP does not contain any packets, a dummy packet is dumped to keep the connection
alive.
• If the FTP transfer fails or FTP connection is lost during packet capture, the AP stops capturing packets,
notifies with an error message and SNMP trap, and a new FTP connection is established.
• Not all packets in the air are captured, but only those that reach the radio driver.
• Before you start ensure that you have an FTP server, that is reachable by the AP. The captured packets
are dumped to this FTP server.
4. Under Capture Filters, specify the types of packets that need to be captured. You have the following
types:
• Control Packets
• Data Packets
• Dot1x
• IAPP
• Management Packets
• ARP
• Multicast frames
• Broadcast frames
• All IP
• TCP with matching port number
• UDP with matching port number
5. Under FTP Details, specify the following details of the FTP server to which the captured packets are
dumped:
• IP Address
• Path of the folder on the FTP server where the packets are to be dumped
• Username and Password for access to the FTP server
6. Click Start.
The Client Status icon is Green when a packet capture is in progress. It is Red otherwise.
Step 2 In the Rogues summary window, click the count display icon to view high-level details of the rogue devices (unmanaged
neighboring APs or clients).
Step 2 In the Interferers summary window, click the count display icon to view high-level details of the interfering device.
• Client Connections
• You cannot map a WLAN to VLAN0, and you cannot map VLANs 1002 to 1006.
• Dual-stack clients with static IPv4 addresses are not supported.
• When creating WLANs with the same SSID, create a unique profile name for each WLAN.
Adding a WLAN
Step 4 Under the WLAN Security tab, set the following parameters:
• Security—Choose one of the following security authentication options from this drop-down list:
• Guest—The controller can provide guest user access on WLANs which are specifically designated for use by
guest users. To set this WLAN exclusively for guest user access, choose the Security as Guest.
You can set the authentication for guest users by choosing one of the following options in the Guest
Authentication drop-down list:
• Require Username and Password—This is the default option. Choose this option to authenticate guests
using the username and password which you can specify for guest users of this WLAN, under Wireless
Settings > WLAN Users. For more information, see Viewing and Managing WLAN Users, on page 46.
• Display Terms & Conditions—Choose this option to allow guests access to the WLAN upon acceptance
of displayed terms and conditions. This option allows guest users to access the WLAN without entering
a username and password.
• Require Email Address—Choose this option, if you want guest users to be prompted for their e-mail
address when attempting to access the WLAN. Upon entering a valid email address, access it provided.
This option allows guest users to access the WLAN without entering a username and password.
• Open—This option stands for Open authentication, which allows any device to authenticate and then attempt
to communicate with an AP. Using open authentication, any wireless device can authenticate with the AP.
• WPA2 Personal—This option stands for Wi-Fi Protected Access 2 with pre-shared key (PSK). WPA2 Personal
is a method used for securing your network with the use of a PSK authentication. The PSK is configured
separately both on the controller AP, under the WLAN security policy, and on the client. WPA2 Personal does
not rely on an authentication server on your network. This option is used when you do not have an enterprise
authentication server. If you choose this option, then specify the PSK in the Shared Key field.
• WPA2 Enterprise—This option stands for Wi-Fi Protected Access 2, with a local authentication server or a
RADIUS server. This is the default option.
To have a local authentication method, choose AP in the Authentication Server drop-down list. This option
is a Local EAP authentication method that allows users and wireless clients to be authenticated locally. The
controller in the primary AP serves as the authentication server and the local user database, which removes
dependence on an external authentication server.
To have a RADIUS server-based authentication method, choose External Radius in the Authentication Server
drop-down list. RADIUS is a client/server protocol that enables communication with a central server to
authenticate users and authorize their access to the WLAN. You can specify up to two RADIUS authentication
servers. For each server you need to specify the following details:
• RADIUS IP—IPv4 address of the RADIUS server
• RADIUS Port—Enter the communication port of the RADIUS server. The default value is 1812.
• Shared Secret—Enter the secret key used by the RADIUS server, in ASCII format.
Step 5 Under the VLAN & Firewall tab, in the Use VLAN Tagging drop-down list, choose Yes to enable VLAN tagging of
packets. Then, choose a VLAN ID from the drop-down list, to use for the tagging. By default, VLAN tagging is disabled.
Note VLAN trunking is also disabled by default in Cisco Mobility Express. To enable VLAN trunking, execute
config ap vlan-trunking enable ap-name on the command line interface of the Cisco Mobility Express
controller.
By enabling VLAN Tagging, the chosen VLAN ID is inserted into a packet header in order to identify which VLAN
(Virtual Local Area Network) the packet belongs to. This enables the controller to use the VLAN ID to determine which
VLAN to send a broadcast packet to, thereby providing traffic separation between VLANs.
Step 6 If you have chosen to enable VLAN Tagging, then you have an option to enable a firewall for the WLAN based on Access
Control Lists (ACLs). An ACL is a set of rules used to limit access to a particular WLAN to control data traffic to and
from wireless clients or to the controller CPU to control all traffic destined for the CPU.
Note that ACL rules are applied to the VLAN. Multiple WLANs can use the same VLAN, hence inheriting ACL rules,
if any.
Configure a rule for this ACL as follows:
a. From the Action drop-down list, choose Deny to cause this ACL to block packets or Permit to cause this ACL to
allow packets. The default is Permit. The controller can permit or deny only IP packets in an ACL. Other types of
packets (such as ARP packets) cannot be specified.
b. From the Protocol drop-down list, choose the protocol ID of the IP packets to be used for this ACL. These are the
protocol options:
• Any—Any protocol (this is the default value)
• TCP—Transmission Control Protocol
• UDP—User Datagram Protocol
• ICMP—Internet Control Message Protocol
ESP—IP Encapsulating Security Payload
• AH—Authentication Header
• GRE—Generic Routing Encapsulation
• IP in IP—Internet Protocol (IP) in IP (permits or denies IP-in-IP packets)
• Eth Over IP—Ethernet-over-Internet Protocol
• OSPF—Open Shortest Path First
• Other—Any other Internet Assigned Numbers Authority (IANA) protocol. If you choose Other, enter the number
of the desired protocol in the Protocol text box. You can find the list of available protocols in the IANA website.
c. In the Dest. IP/Mask field, enter the IP address and netmask of the specific destination.
d. If you have chosen TCP or UDP, you will need specify a Destination Port. This destination port can be used by
applications that send and receive data to and from the networking stack. Some ports are designated for certain
applications such as Telnet, SSH, HTTP, and so on.
e. From the DSCP drop-down list, choose one of these options to specify the differentiated services code point (DSCP)
value of this ACL. DSCP is an IP header text box that can be used to define the quality of service across the Internet.
You can choose:
• Any—Any DSCP (this is the default value)
• Specific—A specific DSCP from 0 to 63, which you enter in the DSCP edit box
Step 7 Quality of service (QoS) refers to the capability of a network to provide better service to selected network traffic over
various technologies. The primary goal of QoS is to provide priority, including dedicated bandwidth, controlled jitter and
latency (required by some real-time and interactive traffic), and improved loss characteristics.
The Cisco Mobility Express controller supports the following four QoS levels. Under the QoS tab, from the QoS drop-down
list, choose one of the following QoS levels:
• Platinum (Voice)—Ensures a high quality of service for voice over wireless.
• Gold (Video)—Supports high-quality video applications.
• Silver (Best Effort)—Supports normal bandwidth for clients.
• Bronze (Background)—Provides the lowest bandwidth for guest services.
Step 8 Application Visibility classifies applications using the Network-Based Application Recognition (NBAR2) engine, and
provides application-level visibility in wireless networks. Application Visibility enables the controller to detect and
recognize more than 1000 applications and perform real-time analysis, and monitor network congestion and network link
usage. This feature contributes to the Applications By Usage statistic in the Monitoring > Network Summary.
To enable Application Visibility, choose Enabled (the default option) from the Application Visibility drop-down list.
Otherwise, choose Disabled.
What to do next
You can proceed to creating or editing user accounts for this WLAN. See Viewing and Managing WLAN
Users, on page 46.
You can view and manage WLAN users only for the WPA2 Enterprise with Local Server setup. To use your
Cisco Mobility Express wireless network, a wireless client should connect to a WLAN in the network. To
connect to a WLAN, the wireless client will have to use the user credentials set for that WLAN. If this WLAN
uses WPA2-Personal as a Security Policy, then the user must provide the appropriate WPA2-PSK set for that
WLAN on the Controller AP. If the Security Policy is set to WPA2-Enterprise, the user must provide a valid
user identity and the corresponding password set in the RADIUS user database.
Step 2 Click the Edit icon adjacent to the AP you want to manage.
The Edit window with the General tab is displayed.
Step 3 Under the General tab, you can edit the following AP parameters:
• IP Configuration—Choose Obtain from DHCP to let the IP address of the AP be assigned by a DHCP server on
the network, or choose to have a Static IP address. If you choose to have a static IP address, then you can edit the
IP Address, Subnet Mask, and Gateway fields.
• AP Name—Edit the name of the AP. This is a free text field.
The following non-editable AP parameters are also displayed under the General tab:
• Operating Mode—For a primary AP, this field shows AP & Controller. For other associated APs, this field shows
AP Only.
• AP MAC address
• AP Model number
• IP Address of the access point (non-editable only if Obtain from DHCP has been selected).
• Subnet mask (non-editable only if Obtain from DHCP has been selected).
• Gateway (non-editable only if Obtain from DHCP has been selected).
Step 4 (Only for the primary AP) Under the Controller tab, you can manually edit the following controller parameters for the
integrated Mobility Express wireless LAN controller:
• System Name—Edit the name that you have assigned to this controller. You can enter up to 31 ASCII characters.
The system name is first specified during the initial configuration wizard.
• IP Address—This IP address decides the login URL to the controller's web interface. The URL is in the format
https://<ip address>. If you change this IP address, the login URL also changes.
• Subnet Mask
• Country Code—You can set the country code for the controller and all associated APs using this drop-down list.
Once you apply your changes, the country codes on all subordinate APs are automatically changed, the APs reboot
and come back online with the new country code, and rejoin the controller. However the change will not be applied
on the controller and the primary AP until the primary AP is manually rebooted.
Step 5 Under the 802.11 b/g/n tab, you can set the following parameters:
• Admin Mode—Enabled or Disabled. This enables or disables the corresponding radio on the AP (2.4 GHz for
802.11 b/g/n)
• Channel—Automatic, 1 to 11.
Selecting Automatic enables Dynamic Channel Assignment. This means that channels are dynamically assigned
to each AP, under the control of the primary AP. This prevents neighboring APs from broadcasting over the same
channel and prevents interference and other communication problems. For the 2.4 GHz radio, 11 channels are offered
in the U.S. and up to 14 in other parts of the world. However, only 1-6-11 can be considered non-overlapping if they
are used by neighboring APs.
Assigning a specific value statically assigns a channel to that AP.
• Channel Width—20 MHz
The channel width for 2.4 GHz can only be 20 MHz.
Channel bonding groups the channels by 2 or 4 for a single radio stream. This increases the speed and the throughput.
Because the number of channels is insufficient in 2.4 GHz, channel bonding cannot be used to enable multiple
non-overlapping channels.
• Transmit Power—Automatic, 1 to 8.
This is a logarithmic scale of the transmit power, that is the transmission energy used by the AP, with 1 being the
highest, 2 being half of it, 3 being 1/4th, and so on.
Selecting Automatic adjusts the radio transmitter output power based on the varying signal level at the receiver.
This allows the transmitter to operate at less than maximum power for most of the time; when fading conditions
occur, transmit power will be increased as required until the maximum is reached.
Step 6 Under the 802.11 a/n/ac tab, you can set the following parameters:
• Admin Mode—Enabled or Disabled. This enables or disables the corresponding radio on the AP (5 GHz for
802.11a/n/ac).
• Channel—Automatic, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 149, 153, 157, 161,
165.
For the 5 GHz radio, up to 23 non-overlapping channels are offered.
Assigning a specific value statically assigns a channel to that AP.
• Channel Width—20, 40, 80 MHz
The channel width for 5 GHz can be set to 20, 40, or 80 MHz, if channel bonding is used.
• Transmit Power—1 to 8.
This is a logarithmic scale of the transmit power, that is the transmission energy used by the AP, with 1 being the
highest, 2 being half of it, 3 being 1/4th, and so on.
Selecting Automatic adjusts the radio transmitter output power based on the varying signal level at the receiver.
This allows the transmitter to operate at less than maximum power for most of the time; when fading conditions
occur, transmit power will be increased as required until the maximum is reached.
Step 2 You can enable or disable the following types of management access to the controller, by choosing the appropriate option
from the drop-down list:
• HTTP Access—To enable HTTP access mode, which allows you to access the controller GUI using
http://<ip-address> through a web browser, choose Enabled from the HTTP Access drop-down list. Otherwise,
choose Disabled.
The default value is Disabled.
Note HTTP access mode is not a secure connection.
• HTTPs Access—To enable HTTPS access mode, which allows you to access the controller GUI using
http://ip-address through a web browser, choose Enabled from the HTTPS Access drop-down list. Otherwise,
choose Disabled.
• Read Only
• Read/Write
• Lobby Ambassador
• Password—The password is case sensitive and should be created based on the following guidelines:
• It should have at least eight characters using a combination of numbers, special characters, as well as upper
and lower case letters.
• It should neither contain the word Cisco or a management username nor be a variant of these words obtained
by:
• Reversing the letters of these words
• Changing the capitalization of the letters
• Substituting the following:
• 1, |, or ! for i
• 0 for o
• $ for s
• No character can be repeated more than three times consecutively in the password.
Step 2 Click the Edit icon adjacent to the account you want to edit.
Step 3 Modify the admin account parameters, as required. For descriptions of these parameters, see Adding an Admin Account,
on page 52.
Step 4 Click Apply.
Step 2 Click the Delete icon adjacent to the account you want to delete.
Step 3 Click Ok in the confirmation dialog box.
You can specify the IPv4 address or the FQDN name of an NTP server during the initial configuration wizard.
This will be applied to the server having NTP Index 1, thereby overwriting its default FQDN,
0.ciscome.pool.ntp.org .
For adding and editing NTP server details, go to Management > Time. This opens the Time Settings page.
Step 2 In the NTP Polling Interval field, specify the polling interval, in seconds.
Step 3 To edit an existing NTP server, click its adjacent Edit icon. To add a new NTP server, click Add NTP Server.
Step 4 You can add or edit the following values for an NTP server:
a) In the NTP Index box, specify an NTP Index value to set the priority of the NTP server. NTP Index values can be
set from 1 to 3, in the order of decreasing priority. The controller will try and sync with the NTP server with the
highest priority first, until the specified polling interval time runs out. If the sync is successful, the controller does
not continue trying to sync with any remaining NTP servers. If the sync is unsuccessful, then the controller will try
to sync with the next NTP server.
b) In the NTP Server box, specify the IP address or the fully qualified domain name (FQDN) for the NTP server. When
you specify an FQDN, a DNS lookup is done. If the lookup fails, an error will be logged in the Syslog server. The
controller will continue to resolve this FQDN and errors will be logged until you change the NTP configuration or
specify a valid FQDN.
Step 5 Click Apply.
Step 4 Select the Set Time Automatically from Current Location check box to set the time based on the time zone specified.
Step 5 In the Set Time Manually field:
• Click the calendar icon and choose the month, day, and year.
• Click the clock icon and specify the time, in hour and minutes.
This displays the Software Update window, with the current software version number displayed at the
top.
You can update the Cisco Mobility Express controller software using the controller's web interface. This will
prevent the current configurations on the Cisco Mobility Express controller from being deleted.
A software update ensures that both the internal controller software and the AP software on all the associated
APs are updated. APs that have older Cisco Mobility Express AP software, on joining the primary AP after
the software upgrade are automatically upgraded to the latest Cisco Mobility Express AP software. This is
because, during the software update process, the latest Cisco Mobility Express software for all Cisco Mobility
Express-supported APs that are associated with the controller is also downloaded. An AP joining the controller
compares its Cisco Mobility Express software version with that on the primary AP and if a mismatch is
detected, the new AP requests for a software upgrade. The primary AP facilitates the transfer of the new
software from the TFTP server or the HTTP path, to the new AP.
Downloading a newer version of the Cisco Mobility Express software image from the TFTP server to the
Cisco Mobility Express network that has to be upgraded can take around 5 minutes per AP. The software
download happens in the background, without impacting the network. The upgrades are automatically sequenced
to ensure that the network performance is not impacted by software update.
Note Ensure that the TFTP server always has the same Cisco Mobility Express software bundle as that on the Cisco
Mobility Express controller, or the latest software bundle.
If your network consists of only 1850, 1830, or both models of access points (which support ap1g4
images), then you can perform the update via TFTP or HTTP. If you have other supported AP models
in your network, then you can use only TFTP for the update.
• If you are using a TFTP server for the software update, then the TFTP server should be configured and
accessible. See Guidelines for Preparing a TFTP Server, on page 56.
• A computer that can access Cisco.com and the TFTP server should be available.
Step 3 In the Transfer Mode drop-down list, choose TFTP or HTTP as required.
Step 4 If you have chosen TFTP as the transfer mode then:
a) In the IP Address (IPv4) field, enter the IP address of the TFTP server.
b) In the File Path field, enter the TFTP server directory path of the software file, along with the name of the file.
Step 5 If you have chosen HTTP as the transfer mode, then click the Browse button adjacent the File Path field, and then
browse to and choose the software file.
The file name of the software file appears in the File Path field
Step 6 Click Apply to save the parameters that you have specified.
These parameters will remain saved unless you specifically change them in future. You do not have to enter these
parameters afresh for the next software update.
Step 7 You can perform the update right away or schedule it for a later time.
• To proceed with the update right away, click Update Now, and then click Ok in the confirmation dialog.
The top section of the page indicates the status of the download. Do not manually power down or reset the controller
or any AP during this process; otherwise, you might corrupt the software image.
The Preimage Download Status section of the page shows the status of the pre-image download to the APs in the
network.
After the pre-image download is complete, click Reboot to reboot the controller.
• To perform the update at a later time, up to a maximum of 5 days from the current date, specify the later date and
time in the Set Reboot Time field, and then click Schedule Later. After the preimage download is complete, the
controller automatically reboots.
For more information on the Preimage Download feature, see Predownloading an Image to an Access Point, on page 71.
Step 8 Log in to the controller and verify the controller software version in the Software Update window.
Managing SNMP
Simple Network Management Protocol Version 2 (SNMPv2) is a protocol for network management. It is used
for collecting information from, and configuring and managing all the devices in the network.
To enable SNMPv2 Access, choose Enabled from the SNMPv2 Access drop-down list. Otherwise, choose
Disabled. The default is Disabled.
To configure an SNMP community with read-only privileges, in the Read-Only Community field, enter a
name for the community. The default is Public.
To configure an SNMP community with read-write privileges, in the Read-Write Community field, enter a
name for the community. The default is Private.
To enable the SNMP Trap Receiver tool that receives, logs, and displays SNMP traps sent from network
devices, choose Enabled from the SNMP Trap drop-down list. The default is Disabled.
To connect to an SNMP server, specify the IP address of the server in the SNMP Server IP field.
Step 2 From the Syslog Logging drop-down list, choose Enabled. The default is Disabled.
The System Message Logging feature is enabled.
Step 3 In the Syslog Server IP field, enter the IPv4 address of the server to which the syslog messages are to be sent.
Step 4 Set the severity level for filtering syslog messages to the syslog server. From the Logging Level drop-down list, set the
severity level by choosing one of the following (given in the order of severity):
• Emergencies (Highest severity)
• Alerts
• Critical
• Errors (Default)
• Warnings
• Notifications
• Informational
• Debugging (Lowest severity)
After a syslog level is set, only messages with a severity equal to or more than the set level are sent to the syslog server.
Step 5 To set the facility for outgoing syslog messages to the syslog servers, choose one of the following options from the Syslog
Facility drop-down list:
• Kernel = Facility level 0
• User Process = Facility level 1
• Mail = Facility level 2
• System Daemons = Facility level 3
• Authorization System = Facility level 4
• Syslog = Facility level 5 (default value)
• Line Printer = Facility level 6
• USENET = Facility level 7
• Unix-to-Unix Copy = Facility level 8
• Cron = Facility level 9
• FTP Daemon = Facility level 11
• System Use 12 = Facility level 12
• System Use 13 = Facility level 13
• System Use 14 = Facility level 14
• System Use 15 = Facility level 15
• Local Use 0 = Facility level 16
• Local Use 1 = Facility level 17
• Local Use 2 = Facility level 18
• Local Use 3 = Facility level 19
• Local Use 4 = Facility level 20
• Local Use 5 = Facility level 21
• Local Use 6 = Facility level 22
• Local Use 7 = Facility level 23
After the Mobility Express Controller reboots, proceed to Starting the Initial Configuration Wizard, on page
6.
Step 1 When prompted to terminate the autoinstall process (the CLI Initial Configuration Wizard), wait for 30 seconds. The
CLI Initial Configuration Wizard begins after 30 seconds.
To terminate and exit the process, enter yes.
The wizard downloads a configuration file from a TFTP server and then loads the configuration onto the controller
automatically.
Step 2 Enter the Administrative Username and Administrative password to be assigned to this controller. You can enter
up to 24 ASCII characters for each.
The following is the password policy:
• The password must contain characters from at least three of the following classes:
• Lowercase letters
• Uppercase letters
• Digits
• Special characters
• No character in the password must be repeated more than three times consecutively.
• The new password must not be the same as the associated username and not be the username reversed.
• The password must not be cisco, ocsic, or any variant obtained by changing the capitalization of letters of the word
Cisco. In addition, you cannot substitute 1, I, or ! for i, 0 for o, or $ for s.
Step 3 Enter the System Name, which is the name that you want to assign to the controller. You can enter up to 31 ASCII
characters.
Step 4 Enter the code for the country in which the Mobility Express network is located.
Note Enter help to view the list of available country codes.
Step 5 If you want the controller to receive its time setting from an external Network Time Protocol (NTP) server when it
powers up, enter YES to configure an NTP server. Otherwise, enter no.
If you entered YES, then enter the NTP server's IP address.
If you entered no, then enter the following to manually set the time and date:
• Enter the date in MM/DD/YY format.
• Enter the time in HH:MM:SS format.
Step 6 Enter the timezone location index to set the timezone. Enter help for a list of timezones listed by their indexes.
Step 7 Enter the IP address of the management interface.
Note The management interface is the default interface for in-band management of the controller and connectivity
to enterprise services.
Step 8 Enter the IP address and subnet mask of the management interface.
Step 9 Enter the IP address of the default gateway router.
Step 10 To enable the Employee Network, enter YES. Otherwise enter no.
If you have entered YES, then enter the following:
a. Employee Network Name (SSID)
b. Employee VLAN Identifier (0 = untagged)
c. Employee Network Security. You can enter PSK or enterprise.
d. If you have entered Employee Network Security as enterprise, specify the following:
• RADIUS Server's Address.
• RADIUS Server's Port.
• RADIUS Server's Secret (password).
e. If you have entered Employee Network Security as PSK, specify the following:
• Enter PSK Pass phrase (8 to 38 characters).
• Re-Enter PSK Pass phrase (8 to 38 characters).
Step 11 To enable the Guest Network, enter YES. Otherwise enter no.
If you have entered YES, then enter the following:
a. Guest Network Name (SSID).
b. Guest VLAN Identifier (0 = untagged).
c. Guest Network Security. You can enter WEB_CONSENT or psk.
d. If you have entered Guest Network Security as PSK, specify the following:
• Enter Guest Pass phrase (8 to 38 characters).
• Re-Enter Guest Pass phrase (8 to 38 characters).
Step 13 When prompted to verify that the configuration is correct, enter yes or NO.
The controller saves your configuration when you enter yes, reboots, and prompts you to log on.
CLI Procedures
Changing the SNMPv3 User Default Values
The controller uses a default value of “default” for the username, authentication password, and privacy
password for SNMPv3 users. Using these standard values presents a security risk. Therefore, Cisco strongly
advises that you change these values.
Step 1 See the current list of SNMPv3 users for this controller by entering this command:
show snmpv3user
Step 2 If “default” appears in the SNMPv3 User Name column, enter this command to delete this user:
config snmp v3user delete username
The username parameter is the SNMPv3 username (in this case, “default”).
Step 1 To enable or disable 802.11r fast transition parameters, use the config wlan security ft {enable | disable} wlan-id
command.
Step 2 To enable or disable 802.11r fast transition parameters over a distributed system, use the config wlan security ft
over-the-ds {enable | disable} wlan-id command.
By default, the fast transition over a distributed system is disabled.
Step 3 To enable or disable the authentication key management for fast transition using preshared keys (PSK), use the config
wlan security wpa akm ft-psk {enable | disable} wlan-id command.
By default, the authentication key management using PSK is disabled.
Step 4 To enable or disable the authentication key management for fast transition using 802.1X, use the config wlan security
wpa akm ft-802.1X {enable | disable} wlan-id command.
By default, the authentication key management using 802.1X is disabled.
Step 5 To enable or disable 802.11r fast transition reassociation timeout, use the config wlan security ft reassociation-timeout
timeout-in-seconds wlan-id command.
The valid range is 1 to 100 seconds. The default value of reassociation timeout is 20 seconds.
Step 6 To enable or disable the authentication key management for fast transition over a distributed system, use the config
wlan security wpa akm ft over-the-ds {enable | disable} wlan-id command.
By default, the authentication key management for fast transition over a distributed system is enabled.
Step 7 To view the fast transition configuration on a client, use the show client detailed client-mac command.
Step 8 To view the fast transition configuration on a WLAN, use the show wlan wlan-id command.
Step 9 To enable or disable debugging of fast transition events, use the debug ft events {enable | disable} command.
Step 10 To enable or disable debugging of key generation for fast transition, use the debug ft keys {enable | disable}
command.
Note You cannot set the CDP hold time by configuring it from the controller console on the primary AP. The
controller's hold time configuration is ignored since both the controller and internal AP on the Cisco Mobility
Express primary AP share the same interface on the switch.
Step 1 To enable or disable Cisco Umbrella, use the config opendns {enable | disable}
Example:
(Cisco Controller) > config opendns enable
Creates, deletes, or refreshes a Cisco Umbrella profile that can be applied over a WLAN.
Supported Browsers
Operating System Supported Browsers and Versions
Note Clients that connect to the primary AP will lose connectivity during a failover.
Note For a primary AP, the Operating Mode field shows AP & Controller. For other associated APs, this field
shows AP Only. The Make Me Controller button is available only for subordinate APs that are capable of
participating in the primary election process.
When you force the failover of the primary to an AP of your choice, using the GUI or CLI methods, the current
primary AP reboots while the new AP takesover as the controller, with the IP address and configuration as
the previous primary. The previous primary, after rebooting, comes back online and joins the new primary
AP as a subordinate AP.
Note Like any failover, this forced failover causes some downtime in the Cisco Mobility Express network. During
this downtime, clients associated to APs that have the standalone feature enabled will not face any disruption
in service. Clients of APs that do not have the standalone functionality enabled will be affected.
AlternativeMethodforCAPWAPtoMobilityExpressConversion
Note • The recommended method is Converting from CAPWAP Lightweight AP to Cisco Mobility Express
Software, on page 20. The following is an alternative only in case the recommended method does not
work.
• The following procedure shows a conversion from the 8.1.122.0 Lightweight AP release on an 1850
series AP, and hence uses the corresponding software file. Ensure that you use the appropriate software
file depending on the release you are converting from and the AP model.
Tip If you face issues with converting the AP software to a Cisco Mobility Express software, upgrade the AP
CAPWAP software to the latest AP software version ap3g3-k9w8-tar.153-3.JD.tar. Now, you can convert the
CAPWAP software to the Cisco Mobility Express software AIR-AP2800-K9-ME-8-3-102-0.tar.
This issue occurs in Mobility Express-capable APs shipped with default images or a version of the images
prior to Cisco Wireless Release 8.3. This is due to insufficient space in the AP’s memory or because the AP
has been started in U-boot mode where the image is not found in flash.
Step 1 Download the AIR-AP1850-K9-ME-8-1-122-0.zip software file from Cisco.com to the TFTP server.
On the Download Software page, for a given release, this .ZIP file is labeled, ''Access point image bundle, to be used for
software update and/or supported access points images''.
Step 2 Unzip the contents of the ZIP file to a directory on the TFTP server.
Step 3 Connect to the console port of the AP.
Step 4 Log in to the AP using the username Cisco and password Cisco. Both are case-sensitive.
This is the default factory-shipped username and password on all Cisco Aironet APs.
Step 5 Use the command ap-type mobility-express tftp://<tftp server ip-address>/<filename of ap1g4 TAR file with path from
root on the TFTP server> command.
The AP reboots, comes back online, and tries to join a controller for about 5 minutes. After this, the AP continues to boot
into Mobility Express mode and starts broadcasting the CiscoAirProvison SSID.
What to do next
Proceed to Starting the Initial Configuration Wizard, on page 6.
To convert multiple access points running Mobility Express image to CAPWAP simultaneously from the
Mobility Express controller CLI, execute the following command:
(Cisco Controller) > config ap unifiedmode <switch_name> <switch_ip_address>
The arguments <switch_name> and <switch_ip_address> are the name and IP address, respectively, of the
WLC to which the APs need to be migrated to.
The above command converts all APs to AP Configuration: NOT MOBILITY EXPRESS CAPABLE. The APs
are then reloaded, and they come back up in local mode.
Note If you do not enable RF Parameter Optimization during the initial configuration wizard, then client density
is set to Typical (the default value), and RF traffic type is set to Data (the default value).
TPC Threshold, Specific RF profile TPC Min: Default at TPC Threshold: TPC Threshold:
TPC Min, and TPC per band -10 dB
• -65 dB for 5 • -60 dB for 5
max
TPC Max: Default GHz GHz
(These parameters at 30 dB
are equivalent to TX • -70 dB for 2.4 • -65 dB for 2.4
Power) GHz GHz
CCA Threshold Global per band Default (0) Default (0) Default (0)
802.11 a only
(hidden)
RF Profiles
Coverage RSSI Global per band Default (Data: -80 Default (Data: -80 Higher (Data: -90
Threshold Voice: -80) Voice: -80) Voice:-90)
Data and voice RSSI
RF Profiles
Coverage Client Global per band Default (3) Default (3) Lower (2)
Count (Coverage
Lower (1 to 3)
Exception)
RF Profiles
(Coverage Hole
Detection)
Data Rates Global per band 12 Mbp mandatory 12 Mbp mandatory CCK rates enabled
(network)
9 Mbp supported 9 Mbp supported 1,2, 5.5, 6, 9, 11, 12
RF Profiles Mbp enabled
1,2, 5.5, 6, 11 Mbp 1,2, 5.5, 6, 11 Mbp
disabled disabled
Related Documents
• Cisco Mobility Express Release Notes
FAQs
Which access points can host the Cisco Mobility Express wireless LAN controller function and which access
points can be managed by it?
See #unique_81.
What controller-based modes does the Cisco Mobility Express wireless LAN controller function support?
Access points managed by the Cisco Mobility Express solution will operate with Centralized Control Plane
and Distributed Data Plane, similar to the AireOS FlexConnect mode.
Can I expand the scale of access points and convert to a wireless controller deployment?
Yes, you can simply point the APs to the WLAN controller IP address as the primary controller. This is
independent of modes. The WLAN controller will push the right AP image and respective configuration. For
detailed information, see Converting an AP from Mobility Express to CAPWAP Type, on page 73.
If my deployment needs to downsize to 25 access points or less, can they convert from existing controller-based
deployment to Cisco Mobility Express?
Yes. You can convert your wireless controller-based deployment to Cisco Mobility Express, as long as your
deployment has APs capable of hosting the Cisco Mobility Express controller functionality (listed as primary
APs in #unique_81).
If the number of APs connected to the primary AP is less than or equal to 25, the maximum clients for the
internal AP is limited to 20. What is the workaround for more efficiency and reducing traffic congestion?
The workaround is to move Cisco Mobility Express to some other AP that has lower loads. Complete the
following steps to move Cisco Mobility Express to other APs:
1. Enter the show ap summary command. The list of APs are listed.
2. Identify the APs with the least number of clients.
3. Enter the config ap next-preferred-master <new_ap_name> forced-failover command. This command
will move the Cisco Mobility Express controller to the new AP and the current AP will serve the clients.
Where can I get more information on the Cisco Mobility Express solution?
Go to http://www.cisco.com/go/mobilityexpress.