CMX V1.0 160616

Converged Mobile Experience
CMX Version 10.2

Lab Guide
Version 1.0
Solutions Readiness Engineers

Americas Partner Organization
Cisco Connected Mobile Experience v10.2 Lab Guide
Contents
Introduction .................................................................................................................................... 3
Infrastructure Design and Components ......................................................................................... 4
Radio Frequency Principles for Location Services .......................................................................... 5
Cisco Prime Infrastructure RF Planning Tool .................................................................................. 6
Lab Activities ................................................................................................................................... 7
Lab Objectives ................................................................................................................................. 7
Disclaimer........................................................................................................................................ 8
Build Information ............................................................................................................................ 9
Prerequisite Knowledge .................................................................................................................. 9
Physical and Logical Topology....................................................................................................... 10
Exercise 1: Access the Lab Environment and Baseline the Network ............................................ 11
Section 1.1 Review the Solutions and Network Design ............................................................ 11
Section 1.2 Access Your Lab Pod............................................................................................... 14
Section 1.3 Review and Test the Existing Network .................................................................. 20
Wireless LAN Controller (WLC) Configuration .............................................................................. 22
Section 1.1 WLC CLI Wizard ...................................................................................................... 22
Section 1.2 WLC GUI Configuration .......................................................................................... 28
Prime Infrastructure ..................................................................................................................... 53
Section 1.1 Prime Infrastructure Configuration ....................................................................... 53
Section 1.2 Device Inventory .................................................................................................... 54
Section 1.3 Adding Maps to Prime ........................................................................................... 60
Section 1.4 Adding APs to Branch Map .................................................................................... 68
Section 1.5 Adding Corporate Maps ......................................................................................... 73
Section 1.6 Adding Corp APs ..................................................................................................... 76
Section 1.7 Monitoring AP Alarms in Prime ............................................................................. 81
Section 1.8 Map Editor ............................................................................................................. 86
CMX ............................................................................................................................................... 94
CMX Location ............................................................................................................................ 94
Section 1.1 Location Configuration ........................................................................................... 94
Section 1.2 Defining Location Services ................................................................................... 108
Section 1.3 Verticals ................................................................................................................ 127
CMX Presence ......................................................................................................................... 139
Section 1.1 Configuration ....................................................................................................... 139
Section 1.2 Portal Setup .......................................................................................................... 148
2
Introduction
The growth wireless networks and the explosion of mobile devices means that nearly everyone
has access to the Internet and can be contacted through a communications or data network.
According to the Wi-Fi Alliance more than 10 Billion devices have been shipped with Wi-Fi
interfaces. Users leverage their mobile devices to find, share and send information about goods
and services. Mobile devices have given users the ability to be always connected to the
internet. With the increase in the mobile device usage organizations need to find new ways to
deliver services to these users and offer new experiences to keep users engaged. The growth of
Wi-Fi networks has also increased the growth of mobile applications, users now have the ability
to compare product prices online while in brick and mortar stores, find information and also
post to social media. This new mobile is called the connected user.
Ciscos Connected Mobile Experiences (CMX) built on Cisco Wireless LAN Architecture (WLAN)
allows enterprises and service providers to deliver customized, location-based services that
provide personalized device experience while allowing organizations to learn about their users
through analytics (online, social, onsite). Location-based services allow mobile users to get
useful information and capabilities based on their location in a venue. Organization get the
benefit of receiving information about mobile users from footfall traffic to dwell times in areas.
With CMX solutions, organizations are able to:
Build customer loyalty, and retention.
Elevate venue operations with intelligent product placement, appropriate staffing, and
improved floor layouts.
The CMX solution has three aspects:
CMX Detectacknowledges a mobile consumers presence in a venue by detecting the
mobile device and its characteristics before they enter.
CMX Connectprovides premium mobile consumer access in a venue with seamless and
secure
Wi-Fi connectivity, allowing mobile consumers to receive personalized and location-based
services.
Organizations can collect these preferences and device and roaming credentials through direct
access to a venues network or through social media sites.
CMX Engageorganizations can gather highly relevant content and services based on user
attributes and real time location to deliver a personalized, context-aware experience to a
mobile consumer while in their venue.
The CMX solution relies on a Wi-Fi infrastructure within a venuethe key enabler for service
deliveryto detect, connect, and engage with mobile users. An organizations WLAN network
must become as robust, secure, scalable, and predictable as possible to ensure a positive
experience for mobile users within a venue. Wi-Fi network is critical to provide services
customized for the individual.
3
Infrastructure Design and Components

The underlying infrastructure behind all CMX applications and services is the Cisco wireless LAN
(IEEE 802.11) network infrastructure, which consists of the following hardware:
Cisco Aironet Access Points (APs)
Cisco Wireless LAN Controllers (WLCs)
Cisco Mobility Services Engine (MSEs)
Cisco Prime Infrastructure
High-level Overview of Hardware and Information Flows for CMX Location Analytics
APs are used for client connectivity.

WLCs are used for AP connectivity and gathering of RF statistics.
The MSE is the math calculator used for location calculation and combined with CMX
application for analytics and services.
Prime Infrastructure is used for map rendering and Access Point placement heat map and visual
display of client location (based on information sent back from MSE).
4
You will be configuring each one of these components in the upcoming lab in the following
scenario:
Radio Frequency Principles for Location Services

An AP consists of a radio and an antenna. The radio is used for transmitting and receiving
energy while the antenna used for the formation of the energy pattern. While this may be
basic knowledge it is the premise for Location Based Services. APs hear the energy that is
sent by clients probing for wireless networks to connect.
Note: Up to CMX 8.0 this client probing was how a device was located, as of CMX 10.0 a new
feature called fast locate was added. Fast locate uses the Wireless Security Module (WSM)
plugged into the expansion slot of the Cisco 36xx and 37xx APs to scan for client data packets to
allow for better location updates. As multiple APs hear a client they use RSSI (Receive Signal
Strength Indicator is an indication of the power being received at an antenna) and report it to
the WLC which in turn sends it to the MSE. These calculations are then used to determine the
relative position of the client. The Location Services also calculate ToA (Time of Arrival) which is
a Client transmission is heard by multiple APs and the variance of arrival time of the packets is
calculated to determine location. When using Presence Analytics RSSI values (that you can
configure) are used to determine location in proximity to a single AP.
5
A pre-deployment site survey is one of the most important tasks that should be conducted
before deploying a Cisco Wireless LAN. Pre-deployment RF site surveys involve physically
inspecting the location where the WLAN needs to be deployed, studying building properties to
plan for multipath, signal attenuation, etc., and verifying that Access Points can be installed in a
location that provides maximum coverage with good signal strength to users. Once a pre-site
survey has been done and all the necessary information has been obtained, tools like the RF
planning tool in Prime Infrastructure or other Wi-Fi planner should be used to do predictive RF
planning. With a completed site survey it will give you a much better understanding of RF
environment which will lead to better location calculations.
Cisco Prime Infrastructure RF Planning Tool

The RF Planning tool can be used to add wall attenuation information to floor maps. Wall
information added via the Map Editor does not affect access point placement or location
designs, however it will be used by the planning tool when displaying predicted RF coverage
maps for planned access points. The planning tool operates purely on a hypothetical basis
without the need to connect or deploy any access points or controllers. Since it is Cisco Prime
Infrastructure feature, a Cisco Prime Infrastructure server must be installed somewhere in
network before the planning tool can be used. If there are any existing access points that have
been deployed and defined to Cisco Prime Infrastructure already, the planning tool allows for
the configuration of those access points to be copied into the planning virtual environment.
This will allow you to safely model with a virtual copy of your production environment.
Before using the planning tool for RF coverage planning, ensure that an appropriate path loss
model has been assigned to the floor upon which you wish to conduct your planning. Cisco
Prime Infrastructure uses the coverage reference path losses and path loss exponents when it
plots the predicted coverage heat maps from each access point in the planning tool.
6
Lab Activities
The main activities in this lab are:
Lab Objectives
After completing this lab, you will meet the following objectives:
7
Disclaimer
This Guide is intended to demonstrate one way to configure the network, to meet the specified
requirements of this example. There are various ways that this can be accomplished, depending
on the situation and the customers goals/requirements. Please ensure that you consult all
current official Cisco documentation before proceeding with a design or installation. This lab is
primarily intended to be a learning tool, and may not necessarily follow best practice
recommendation at all times, in order to convey specific information. This is not intended to be
a deployment guide. It is intended for learning purposes only.
8
Build Information
As of the writing of this document, the current relevant documentation could be found on CCO
at the following links:
WLC 8.1
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/configurationguide/b_cg81.html
Cisco Prime 3.0
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/30/user/guide/pi_ug.html
Cisco CMX
http://www.cisco.com/c/en/us/td/docs/wireless/mse/10-2/cmx_config/b_cg_cmx102.html
The labs were constructed using the following software versions:
WLC
Prime 3.0
CMX
Version
Version
Version
Deployed from CCO ISO

ct5760-ipservicesk9
cat3k_caa-universalk9
Prerequisite Knowledge
A solid understanding of networking, including routing and switching is assumed. Some
background with Cisco Unified Wireless solution is helpful, but not required.
9
Physical and Logical Topology

The following diagram depicts the topology of the lab.
10
Exercise 1: Access the Lab Environment and Baseline the

Network
This exercise will cover baseline testing of the existing network, including accessing the existing
5508 WLC, wireless test PC, Jump PC1, Prime Infrastructure Server, CMX Location, and CMX
Presence.
Section 1.1 Review the Solutions and Network Design

The goal of this section is to become familiar with the existing network, as well as the intended
configuration changes and big picture solutions.
Step 1: Begin by taking a closer look at the layer two, layer three diagram.
Looking at the above diagram, we can see that at the top left is the internet connection which is
front-ended by a Cisco Router running IOS Firewall Feature set. The Cisco Router is acting as the
Gateway for VLANs 20 and 21. Attached to it is a 3850 switch acting as the trunk link to the core of
the network. Attached to 3850 Switch-1 is a 5508 WLC; also connected to Switch-1 is User PC1,
which is where the majority of configuration will be made from, as well as the yet to be configured
Prime Infrastructure, CMX Location and Presence Servers. The Access points connected to Switch-1
is be serviced by the 5508, on VLAN 20 representing the corporate headquarters network.
Corporate network VLAN 20 we will configure the WLC, Prime Infrastructure and CMX Location
Server for more granular analytics.
11
To the right of Switch-1, connected by a trunk, is 3850 Switch-2, which is acting as a Campus Branch
Switch. Branch AP1 and Branch AP2 are connected to the switch on VLAN 21. We will be using the
CMX Presence Server and PC2 to connecting into the Branch network and using the Guest Portal
and Presence based analytics.
In order to get the most from the lab and this companion document, it is helpful to understand
some of the terminology and functions of the surrounding components. If you are unfamiliar with
Connected Mobility Experience, please take a moment to look through the information below.
The key to understanding CMX is to understand the relevance of the components and deployment
methodologies that make up Location Services (Context Aware Services [CAS]).
Wireless LAN Controller (WLC): A WLC is the translational bridge for the system. Wireless
Networks have a different frame format 802.11 than Ethernet. In an 802.11 frame there are three
Mac (Media Access Control) address that has the source (Client) Destination 1(Access Point) and
Destination 2 (Destination Client). There is also an option for a fourth Mac address if the Access
Point is performing a bridging function. The Access Point will receive the 802.11 frame and in the
case of a WLC base Wireless Network will place the 802.11 frame in a CAPWAP (Control and
Provisioning of Wireless Access Points) tunnel that terminates on the WLC. The Tunnel has the
ability to be encrypted so you can think of the tunnel just like an IPSec tunnel or a VPN connection
to a concentrator. The WLC takes information contained in the CAPWAP header [Receive Signal
Strength (RSSI), Signal to Noise Ratio (SNR)] and store that information about that particular client.
These values will later be reported to CMX for the location of client or other devices. The WLC will
then take the 802.11 frame and substitute its Mac Address as the source of the Ethernet Frame
with the Destination Client Mac Address and tag the Ethernet Frame with the appropriate 802.1q or
VLAN tag and place the Ethernet Frame back into the network. There is no layer three routing
functionality in a WLC.
Cisco Prime Infrastructure: Cisco Prime Infrastructure (Prime) is a management platform for Cisco
Network devices. Prime is used for the management of WLCs and Access Points (APs). There are
many management tools and templates that Prime has for managing wireless networks that are
beyond the scope of this lab. We will however be using the Map feature in Prime that will allow
you to load Campus, Building and Floor maps and place APs accordingly. You will be able to select
the type of walls that the floor has and place APs on the map. This will build a heat map which is
the RF propagation on the floor or the building. This heat map and information collected will be
sent to the Mobility Services Engine (MSE)/CMX server, to calculate analytics. It is important when
placing the map in Prime that you size and scale it correctly to give the greatest accuracy to the
CMX server for calculating movement and location.
12
Cisco Connected Mobility Experience (CMX): Cisco CMX is an analytics platform for finding
Location and Presence information about wireless devices. The MSE/CMX can gather many
statistics about a network including: visitors, new and repeat, movement patterns, dwell time and
movement playback. CMX also allows you to set up verticals (pre-defined reports for specific types
of applications), such as retail, hospitality, education and others. There are two types of CMX
services Context Aware Services (CAS) which is also called Location Based Services, which gather
information from three or more APs, and Presence which uses values set on a signal AP to define a
general area of a device. CMX also offers the ability to build portals for wireless clients access that
can include social media login as well as a custom defined portal.
In summary, CMX is more than a software platform. CMX relies on the WLC and Prime to get
information about the wireless network and the propagation of the Radio Frequency (RF) signals.
CMX is used as the tracking engine for the devices that are found throughout the wireless network.
It is extremely important that the configuration of Prime and the placement of the APs on the maps
in Prime be accurate in order for the best chance at accurate location of devices. Proper RF
attenuation values are also vital in the ability to locate devices. CMX also offers the ability to create
customer reports and portals that will allow unique user experiences.
Step 2: Now with this information in mind, take a look at the functional diagram below.
13
Step 3: Looking at the functional diagram, note the location of User PC1 in VLAN 20.
Again, this is where the majority of the configuration will be completed from. The above
functional diagram is of the final design. Currently the 5508, which is yet to be
configured, as well as Prime, CMX Location and Presence which are located in VLAN 20
with the DNS server.
Now that we have all of the above information, it is a good time to talk about what the premise of
the design was. This is a campus deployment with a centralized controller in the corporate building.
VLAN 21 is a branch in the campus where potential visitors are located. Although you would
typically have a guest anchor controller in the DMZ, it was determined at this point the separation
of traffic by VLANs would be sufficient.
Section 1.2 Access Your Lab Pod

The goal of this section is to access the Lab pod that has been assigned to you. Before baseline
testing can begin, you must access the lab pod. At this point, you should have been supplied with
several pieces of information for accessing your lab pod via email or by your lab proctor. You should
have:
The URL to access the student portal
The user ID and password used for logging into the lab portal
Your pod number (Very Important)
Step 4: Using the information provided, please log into the lab now. Begin by opening a
browser and accessing the lab portal https://128.107.69.142/student at this address.
14
Step 5: When you are prompted with a certificate warning from our VPN Gateway,
please accept the self-signed certificate to continue.
15
Step 6: Carefully enter the following credentials and click Login:
Username: stu-xx (Where xx is assigned by your instructor)

Password:
Step 7: Click Continue in the resulting welcome message.
You are now logged into the student portal, and should be presented with a list of bookmarks to
access the images for your pod.
16
Step 8: Verify access to the images by attempting to access the PC1. Carefully click on
the double boxes with arrows on the far left of the bookmark for PC1. This should
open PC1 in a new window. Please note that a current version of JAVA is required on
your PC.
Step 9: Upon clicking the icon to the left of each link, the page shown below may open
to display the security warning. Click to accept it, if it does.
Step 10: Click on the Continue button, to accept the warning and proceed.
17
Step 11: A second security warning will appear. Click the checked box to accept the
risk, and select Run.
18
Proceeding, accept the security warnings a TightVNC connection will open, as can be seen below.
After a moment, the TightVNC connection should connect, and PC1 should appear, as shown below.
Step 12: Now, open the other three listed items the same way, from the student
portal, starting with PC2.
19
Make certain that each of the connections to the lab devices opens successfully, before continuing
any further in the lab. If you have a problem, contact your lab proctor.
Section 1.3 Review and Test the Existing Network

The goal of this section is to become familiar with the existing network, and perform the baseline
testing. It is always good practice to confirm the state of the network, prior to implementing any
changes.
20
Step 13: Now with access to the lab pod, return to the first VNC connection you
opened to PC 1.
Step 14: On PC1, log in, with the password shown below in red.
cisco123 (All Lower Case)
The desktop pictured below will load.
21
Note: In this lab the 2811 router is already configured with interfaces and NAT Pools, and the switching
infrastructure is already configured with VLANs.
Wireless LAN Controller (WLC) Configuration

Section 1.1 WLC CLI Wizard
The goal of this section is to configure the WLC from the CLI Wizard.
Step 15: Open the Putty connection on the desktop
Step 16: Configure the Putty session with the following information:
Hostname:
Port:
Connection Type:
WLC
Will be Auto Populated
Telnet
22
Step 17: You are now in the setup Wizard. Use the setup wizard to configure the WLC
using the following information.
Note: if the System Name Line does not appear use the -sign to move back one level
System Name:
wlcpodX (Where X is your assigned Pod Number)
23
Service Interface IP Address Configuration: DHCP

Enable Link Aggregation (LAG):
yes
Administrative User Name:
admin
Administrative Password:
Cisco123
Management Interface IP Address:
10.1.20.252
Management Interface Netmask:
255.255.255.0
Management Interface Default Router:
10.1.20.254
Management Interface VLAN Identifier:
20
Management Interface DHCP Server:
10.1.20.253
Enable HA:
No
Virtual Gateway IP Address:
1.1.1.1
Mobility/RF Group Name:
PodX (Where X is your assigned Pod Number)
Network Name (SSID):
podXcorp (Where X is your assigned Pod Number)
24
Configure DHCP Bridging Mode:

Allow Static IP Addresses:
Configure RADIUS Server:
Enter Country Code:
Enable 802.11b
Enable 802.11a
Enable 802.11g
Enable Auto-RF
Enter NTP Server:
Enter Polling Interval:
Would you like to Configure IPv6:
Configuration Correct:
No
Yes
No
US
Yes
Yes
Yes
Yes
192.0.2.254
604800
No
Yes
25
After selecting Yes for Configuration correct, the WLC will reboot.
Services restarting
26
Step 18: After the system, restarts login:
Username:
Password:
admin
Cisco123
Step 19: The WLC is now ready for GUI configuration. Close the Putty Session.
27
Section 1.2 WLC GUI Configuration

Step 20: From the desktop, open either Firefox or Chrome to set up the Web GUI for
the WLC
The Lab will be demonstrated in Chrome. If you choose to use Firefox, your screenshots will be different.
Step 21: Connect to https://10.1.20.252 - which is the management address that you
configured in the CLI Setup Wizard.
Note: as of WLC code 7.4 the management interface is the same as the AP-dynamic Management
interface.
28
Step 22: You will receive a Privacy warning. Click on the Advanced field to accept the
security settings
Step 23: Click on Proceed to 10.1.20.252.
29
Step 24: Click the Login button.
Step 25: Login into the WLC using the following credentials:
Username:
Password:
admin
Cisco123
30
Step 26: Before starting configuration, look at the menus to see what options are
available. Click on Access Points. If you dont see APs right away refresh your screen.
Note: the APs are CAPWAP enabled.
Step 27: Click on an AP to look at the details. There should not be any clients attached
to the AP.
31
AP Details
Step 28: Click on Network Summary.
32
Step 29: To configure the Controller, click on the Advanced Link.
Step 30: In the left navigation menu, click on Access Points.
33
Step 31: Below Access Points, select one of the radios. In this example 802.11a/n/ac
was selected.
Step 32: Click the Wireless tab along the top of the display.
34
Step 33: Find the two APs that have 10.1.21.X addresses - these will be the Branch APs.
Click on one of the blue links to configure that AP.
Step 34: Change the AP Name to be Branch1 and then click Apply.
35
Step 35: Note the message about disrupting clients and then click OK.
Step 36: In the left pane, under Access Points, click on All APs.
36
Step 37: Verify that the AP name was changed. Then click on the next AP with a
10.1.21.X address.
Step 38: Change the name of this AP to Branch2 and then click Apply. You will receive
the same message about disrupting clients, click OK.
37
Step 39: Click the All APs link again.
Step 40: Next, name the other APs with the 10.1.20.X addresses to be Corp1, Corp2,
Corp3, and Corp4.
38
Step 41: When all the APs have been named, click on the WLANs tab.
Step 42: Select the WLAN with WLAN ID 1. This WLAN was setup in the initial CLI setup
Wizard.
39
Step 43: Click the Security Tab. You will be removing Security from the WLAN.
Step 44: Select Layer 2 and then select None from the dropdown menu.
40
Step 45: Click Apply and note the next message about disrupting clients. Click OK to
close the message.
Step 46: Next you will set up a WLAN for the Branch Office. Click on WLANs.
41
Step 47: In the drop-down box, select Create New and then click Go.
Step 48: Enter podXbranch as the Profile Name and also the SSID (Where X is your
assigned Pod Number), then click Apply.
While still under the General tab, set the Status of the WLAN to Enabled.
42
Step 49: Click the Security tab, and then select Layer2 and then None and finally, click
Apply.
Step 50: Click on WLANs again and you will return to the WLAN list and see two
separate WLANs.
43
Step 51: Make sure that the Admin Status of both WLANs is set to Enabled. Next, you
will set up AP Groups. You will use the AP Groups to send different SSIDs on different
APs. This will be used to segment (SSID) podXcorp and (SSID) podXbranch . Click on the
AP Groups link under Advanced.
Note: all APs are assigned to the default-group. As you build more AP groups you will be able to segment
services.
Step 52: Click on the Add Group Button.
44
Step 53: Add an AP Group with name Corp and click Add.
Step 54: Repeat the process to add another AP Group with the name Branch.
Step 55: Once both Corp and Branch AP Groups have been created, click on AP Group
Branch to configure that AP Group.
45
Step 56: Select the WLANs tab.
Step 57: Click the Add New button and select podxbranch. Finally, click Add.
46
Step 58: Next, click the APs tab.
Step 59: Click to select the two APs labeled Branch1 and Branch2; and then click Add
APs. Note the Warning Statement, and then click OK to close the warning.
47
Step 60: Return to the AP Groups list, and click on AP Group Corp to configure that AP
Group.
Step 61: Click the WLANs tab; and then click the Add New button. For this AP Group,
select podxcorp and then click Add.
48
Step 62: Click the APs tab and add the four APs labeled CorpX. Click OK to close the
warning dialog.
Step 63: When done, click on Save Configuration from the very top menu options.
49
Step 64: Youll receive another message - about saving the configuration to flash: Click
OK.
Step 65: Once the configuration is successfully saved, click OK.
50
Step 66: In the next section, you will need to configure Cisco Prime Infrastructure with
the correct SNMP Community String for the WLC. Click the Management tab.
Step 67: In the left navigation pane, select SNMP and then select Communities.
51
Step 68: Check the Community names and see there is public and private. You will be
using only the Read-Only community string public - in configuring your devices, since
you do not need to change settings on these devices through SNMP you only need to
be able to access the devices through SNMP.
You have set up two AP Groups Corp and Branch. Branch APs are on a different Network and
will be used in CMX Presence lab. The Presence lab will also have the CMX custom portal set
up.
END OF THE WLC SETUP LAB
52
Prime Infrastructure
Section 1.1 Prime Infrastructure Configuration
Step 69: Open the Chrome Browser on your PC.
Step 70: From the browser, go to https://10.1.20.250
Step 71: Log into the Prime Server using the following credentials:
Username:
Password:
root
PrimePass!
53
Step 72: Click on the Menu Button in the upper left corner.
Section 1.2 Device Inventory

Step 73: Navigate to Inventory and then, Network Devices.
54
Step 74: At this point, you will add the Infrastructure Devices. Click the Add Device
Button.
Step 75: Enter the Controller information that you configured during the CLI Wizard
setup.
IP Address:
10.1.20.252
55
Step 76: Click the SNMP button.
Step 77: Set the Read Community and Confirm Read Community fields to public. Then
click the Verify Credentials button.
56
Step 78: Prime will attempt to connect with the controller to pull information. When
the credentials are verified, you will see a success message in the bottom right corner. If
unsuccessful, check the Device IP address and recheck the SNMP Communities.
Successful credentials.
Step 79: When the credentials have been successfully verified, click the Add button.
57
When the device is successfully added, you will see the message at the bottom right of the
screen.
It will take a few second for Prime to Poll the device and add it to the database, so you will see
the statuses of Un-Managed and Add Initiated.
58
Step 80: Click the refresh Icon at the top of the screen to get an updated page, until
you will see that the device has been added.
Step 81: Repeat the previous seven steps to add the following devices:
IP Address:
10.1.20.254
IP Address:
10.1.20.253
IP Address:
10.1.21.247
Read Community String for all devices: cisco123 or cisco
When all devices are added you will have 4 devices total.
Note that the 3850-Switch-2 is on a different subnet. This switch is acting as the branch switch in a
campus environment. You will be using the Branch location later for Presence based analytics.
59
Section 1.3 Adding Maps to Prime

Step 82: Click the Menu button in the upper left corner and navigate to Maps -> Site
Maps.
Step 83: Click the down arrow in the drop down box labeled Select a Command. From
the drop down box, select New Campus and then click Go.
You will be building a hierarchical model that consists of Campus, Buildings, Floors and Zones for placing
APs. For proper location based services it is extremely important to configure proper dimensions and
scales to the map elements. CMX will import the maps and associated parameters to calculate location
and then derive analytics from the information. If map sizing is not correct the accuracy of the Location
Based Services will suffer.
60
Step 84: Enter the Campus Name as SRE_Campus_PodX (Where X is your assigned Pod
Number). Then, next to Image File Name, click the Choose File button. Navigate to
Desktop >PI_Maps and Choose Cisco_Campus and then click Open. Finally, click the
Next Button.
61
Step 85: Deselect the Maintain Aspect Ratio button. You will enter custom spans on
these maps and change the sizes to accommodate the number of APs that are in the lab.
Change the Horizontal and Vertical Spans to be equal to or greater than the numbers
shown below; and then click the OK button:
Horizontal Span:
Vertical Span:
1850
1240.4
In your own environment, if you know the Latitude and Longitude you can enter them, they can be used if
you want to use GPS markers.
Step 86: You will be taken back to the map screen and can see the new campus that
you have selected. Click on the link for the Campus that you have created.
62
Step 87: In the Select a command drop down box, select New Building and then Go.
This will allow you to create a building size and then set the parameters on the map.
Note that the BLD_14 link is already configured, but you will configure two more buildings that will have
enabled links.
63
Step 88: Name the building SRE_Branch_Bld. Move the blue box from the upper left
corner of the map - to the building to be added. Hold down the <CTRL> key and use the
mouse to resize the blue box around the building. When you have the blue box properly
sized around the building, click the Save button.
If the Horizontal and Vertical Positions and/or Spans are known, you can enter them manually; and then
use the Place button to place the box at that location and size, around the building.
64
Step 89: The building Link will now be active. Click on the link to add floors to your
building. In this lab we will use five floors and two basements.
Step 90: Select the command New Floor Area and then GO. You will import a floor to
be part of the building.
65
Step 91: Name the new floor and then select which floor it is.
Note: you can also adjust the type of floor and height of the floor to help the RF prediction model. When
adding APs later you can select the height of the AP based on the height of the floor to get better RF
prediction for Location Based or Context Aware Services.
Step 92: For the lab, leave the Floor Type as Cubes and Walled Offices for the RF
Prediction and 10 ft. as the Floor height. Feel free to change these settings if you would
like to see the effect on the RF Prediction. Select Choose File and then navigate to
Desktop >PI_Maps > Branch and then select Open and then the Next button.
66
Step 93: Enter the following information for the floor you just uploaded. Due to these
floors not being part of the original Campus building, when editing the Horizontal and
Vertical Spans deselect the Maintain Aspect Ratio box:
Horizontal Span:
Vertical Span:
140.0
260.0
Step 94: When you are satisfied with the dimensions and type of floor, click the OK
button.
67
Section 1.4 Adding APs to Branch Map

Step 95: Once the floor has been added, you can place APs. Go to the Select a
command drop down box; select Add Access Points and then click Go.
Step 96: Next you will see a list - of available APs - that was pulled from the WLC during
the synchronization process. Select the two APs that are labeled Branchx, and then click
the OK button.
68
The APs will be added to the corner of the map. You can choose the drop down box to select
the AP you wish to place or you can click directly on that AP to move it.
When you select an AP a frame will open up on the left hand side that will tell you information about the AP, such
as the name of the AP, the MAC Address, type of AP, etc. You can also use the pull down menu for the protocol
type 802.11a/n/ac. Adjustable parameters include: AP Height, Mounting Azimuth, and Elevation. These setting are
very important in the calculation of the RF Prediction tools.
69
Step 97: Place the APs in approximately the same position as shown below.
Step 98: Once the APs are place in their locations, click on the save icon.
Note: it is very important to be as accurate as possible in the placement of the APs for the Context Aware
Services. Client devices locations are calculated based on how many APs (3 minimum 4 or more better)
and calculating the ToA (Time of Arrival) as the radio signal reaches the multiple APs.
70
Step 99: Note the warning about the APs resetting if the antenna gain might have
changed. Click OK.
If the APs were not placed in the proper locations you can use the Move AP Icon highlighted below.
Step 100: Notice that there is a heat map associated with each AP. The color scale at
the top left of the floor map shows relative signal strength associated with the heat map
on the AP.
Note: the closer the number is to zero (0), the better the signal strength.
You can practice moving the APs if you wish to do so.

Note: The Yellow circle and arrow representing the APs indicates a minor alarm condition. You can click on
the AP to see the status of the alarm. We will be doing this later in the lab.
It is important to note that you should not arbitrarily change the positon of the APs in a production
environment. This could disrupt the Context Aware Services in and give wrong RF information to CMX.
71
New position of the APs and associated heat maps.
Step 101: In order to see accurate coverage models based on your site surveys, you
may need to adjust heat map sensitivity. Go to Access Points and adjust the RSSI
Cutoff. See how that affects the heat map.
You have now completed Adding and Moving APs on a Map. You will now add APs to
another building.
72
Section 1.5 Adding Corporate Maps

Step 102: Go back to Maps > Site Maps and click on the SRE_Campus_PodX link.
Step 103: In the Select a command drop down menu, select New Building and click Go.
73
Step 104: Name the Building as Corp and position the blue box in the corner over the
building, as shown below. When the box is the size of the building, Click the Save
button.
Step 105: The building will now be highlighted in green. Click on the Corp link and go
to the floor menu.
74
Step 106: Go to the Select a command drop down box and select New Floor Area; and
then click the Go button.
Step 107: Next name the Floor Area and Select a floor. If you wish, you can change the
Floor Type and Floor Height. To load the floor map, go to Choose File and then navigate
to Desktop > PI_Maps and load the file named Corp. Click on Open , and then click the
Next button.
75
Step 108: Enter the following information for the floor you just uploaded. Due to these
floors not being part of the original Campus building, when editing the Horizontal and
Vertical Spans deselect the Maintain Aspect Ratio box. When you are done, click the
OK button.
Horizontal Span:
Vertical Span:
203.8
183.3
Section 1.6 Adding Corp APs

Step 109: Click on the add AP icon to get to a list of APs that are available.
76
Step 110: Select the four APs that are named Corp1, Corp2, Corp3, Corp4; and then
click OK. These APs will be placed on the map in the next screens.
Step 111: The four APs are now at the top of the Map, Click on each AP and place it on
the Map in approximately the same positions as shown below.
77
Practice moving the APs to the desired locations.
Step 112: When you have placed the APs click on the Save Icon to save the current
location of the APs.
Step 113: Note the message about APs potentially resetting if you have made changes
to the in Prime.
Reminder: Be careful about making changes to APs in a production environment.
78
Step 114: Practice adjusting the magnification of the map area by adjusting the slider
on the left.
Once the APs have been placed and saved they will generate a heat map based on the RF predictions of
the floor that was entered earlier, for example AP Height, Azimuth, Tilt, as well as the type of construction
of the of the floor.
There is a RF Prediction Tool in Prime Infrastructure that allows the building of walls and the use of
customized attenuation parameters, but it is beyond the scope of this lab.
79
Step 115: Click on the Site Maps link. This will bring you back to the Site Maps page.
From there you will look at the AP placement numbers on the screen.
Step 116: Looking at the highlighted area you can see that the Campus accounts for six
APs, with a breakdown of which buildings and floors have APs and the number of APs
per floor. You will also see the numbers and types of radios that are in use as well as
alarm status on the radios.
80
Section 1.7 Monitoring AP Alarms in Prime

From the heat map screen you can see that some APs are green which means no alarms
and other APs are yellow which means they have a minor alarm.
Step 117: Select the Corp1 AP to see on the following screens the information that can
be obtained about the AP.
81
From the AP info you can see the MAC Address, type of AP, which controller it is
connected to, Location and Height. There are separate tabs for 802.11a/n and 802.11
b/g/n. Additionally, there are four links at the bottom that you can click to check
various operations of the AP.
Step 118: Click on the Minor AP Alarm to check on the alarm.
Step 119: Click the alarm link to go to the monitoring tools. This alarm was caused by
an interference threshold violation, typically another radio device too close to the AP.
82
Step 120: Go to the Change Status drop down to the see four actions you can take. We
will Acknowledge this alarm but you could clear it also.
When the alarm is acknowledged it will not be generated again for seven days if the
original even occurs again.
Step 121: Click on the OK button to proceed.
83
Next we will look at the radios. From the menu you can see the Channel Width,
Transmit Power (Tx), Client Count, Channel Utilization; also with CleanAir you can see
the air quality. Looking at the Links below you can also see Neighbors, Active
Interferers, and Radio details.
Step 122: Take a few minutes and click on the links to see the information that can be
gathered about the network.
Step 123: Do the same for the 802.11 b/g/n radios.
84
The default heat map refresh rate is 5 minutes. If you would like to manually refresh the
heat map, you can click on the icon below. You can also use the pull down menu to
adjust the refresh time.
Step 124: When done with the refresh rates Click on the Site Maps link at the top of
the screen. This will take you to the Site Maps where you will edit Map parameters
next.
85
Section 1.8 Map Editor

Step 125: Click on the SRE_Branch_Bld>Floor_1 link to get to the map.
Step 126: Go to Select a command drop down box and find Map Editor.
With the Map Editor we will be configuring Inclusion Zones.

Inclusion Zones are areas of the Map that will be used in the RF Calculations by MSE/CMX.
You can also configure Exclusion Zones, these are Zones that will not be used in the RF
Calculations.
86
Step 127: Click on Map Editor

Step 128: Click on the Go Button
This will pull up the Map Editor.

Step 129: Click on the Aqua polygon to configure an Inclusion Zone.
Select Inclusion as the type. Note: you can have only one Inclusion Zone per Map instance.
87
An Aqua dot will appear and you will use that to draw the Inclusion Zone.
Step 130: Click on the area that you would like to start the inclusion area.
Step 131: Click again to form another point on the boundary.
Step 132: When you have reached the last point double-click to stop the drawing
process.
An Aqua line will be drawn around the Inclusion area.
88
Step 133: Save the Inclusion area by clicking on the Save Icon.
Step 134: A screen will pop up that says successfully saved the changes. Click OK
89
Step 135: To compute the new heat maps click on the icon with the question mark.
There will be a message stating that heat maps will not be displayed until the RF Prediction is
complete.
Step 136: Click on the OK button.
Once the RF Prediction is complete you will get a message that says RF Prediction is complete.
90
Step 137: Click on the OK button.
Step 138: Go back to the Site Maps to get out of the Map Editor
91
Step 139: Click on the SRE_Branch_Bld>Floor_1 to pull up the map.
92
You will now see the newly computed RF Predicted heat map.
THIS ENDS THE PRIME INFRASTRUCTURE EXERCISE
93
CMX
The CMX lab will configure a Location Server and a Presence Server. The Location Server will
track both associated and not associated clients, using RF Prediction Tools and Zones. CMX
Location uses a minimum of three APs to determine location of a device. There is also a
historical tracking feature of devices so you can see movement of individual clients. On the
Location Server you will also configure a Vertical. A Vertical is a prepackaged report generator
for a specific business.
The second part of the CMX lab will be the configuration of a Presence Server. When using
presence you do not need three or more APs aware of a client, you need only one AP. Presence
will use RSSI values to help determine the location of the client. You can configure the RSSI
values to set whether a device is classified as a passerby or as a customer. CMX 10.2 will not
allow both a Location and Presence Server on the same instance, so you will configure a
separate server. On the Presence Sever you will also configure a Custom Captive Portal for
Wireless Clients.
CMX Location
Section 1.1 Location Configuration
Step 140: From your desktop on your PC open your Chrome Browser and go to
https://10.1.20.251:1984 this is the installation and setup port for CMX.
The username: cmxadmin is automatically populated in the username field.

Step 141: Fill in the Password Field
Password: Cisco123!
94
The setup screen presents two options. Remember you cannot run both Presence and Location
on the same instance of CMX.
95
Step 142: Click on the Location Box to start the Location Installation.
Service configuration process.
96
Service Start Process.
When the Service Start process is finished a link will appear.

Step 143: Click on the link to continue the installation process.
97
If CMX session expires

Login:
Username: admin
Password: admin
On the CMX welcome page click the Next button to continue the configuration.
98
Step 144: This page will setup the password for the admin user. Use the Password:
admin1
Step 145: Next import the WLC information from Prime Infrastructure.
Username: root
Password: PrimePass!
IP Address 10.1.20.250
Keep the Overwrite Maps box checked.
Select import Controllers.
99
Import Controller process.
Importing the Controllers will also import associated Maps.

Step 146: Click the Next Button to continue.
100
Next are the email settings this is mandatory but we do not have an email server in the
lab.
Step 147: Change the To Email Address to: cmx@cisco.com
Step 148: Click on the Save and Test Settings and then Send e-mail Button.
You will get a message that the Test email was sent.
Step 149: Click on the Next Button.
Step 150: Setup is now finished click on the Finish button
101
The dashboard screen will be shown after the setup is complete.

Step 151: Under Controllers if the IP Address is red click on the Edit link under the
Action Tab and verify the WLC SNMP Community String.
Step 152: Enter RW community string you set up in prior exercise on WLC
Step 153: Click Save
On dashboard refresh screen
102
Step 154: Click on the System Tab and then click on the Alerts
Step 155: Notice the different Alerts from Live and Last 24 hours.
103
Step 156: Under the System Tab click under Patterns to view the different patterns.
Step 157: Under System click on the Metrics to view different metrics.
104
Step 158: Select Users on the Manage tab to see the available types of users that can
be configured.
Different Users can have different levels of access.

For example if you choose to add a user called Analytics that is all they will have access to.
Step 159: To create a new user under Manage Tab click Users and then + New User.
Username: tuser
Password: cisco123
Roles: Select Analytics and System
Step 160: Click the Submit Button and verify the new user has been created.
105
Step 161: Verify a new user has been created.

Step 162: Go to the Admin link in the upper right hand corner and logout.
Step 163: Go to https://10.1.20.251 and Login.

Username: tuser
Password: cisco123
106
Step 164: When successfully Logged in you will see the two roles that tuser is
allowed access to.
Step 165: Logout
Step 166: Log back into CMX

https://10.1.20.251
Username:
admin
Password:
admin1
107
Step 167: Go to Manage and Notifications and New Notifications to see the types of
Notifications that are available.
Section 1.2 Defining Location Services

If you need to re-login
Go to https://10.1.20.251
Username: admin
Password: admin1
108
The Pane on the left shows the SRE_Campus_PodX that was imported from before.
We are now going to configure the Location Services.
Step 168: Click on the Manage Tab and then the Locations link.
Step 169: Select Zone uder the Campus to configure new zones.
109
When Zone is selected you will see both Floor2 and Floor1 from the imported Map.
We will configure Zones on Floor1 which is located in the Branch building.
Step 170: You can click on the arrow to take you to the Floor_1 map.
110
Configuring of Zones is important in the ability to gather analytical data. We will configure
Zones for both the Branch Building and the Corporate Building. Note: you dont have to
configure Zones if you are using CMX Presence which you will be doing in a later section. We
will not be using the Branch Building as part of the location analytics, but it is good practice to
build Zones for familiarity.
First we need to configure a perimeter before Zones can be configured. A Perimeter is an all
inclusive Zone that all clients will be contained within. New Zones will be configured inside the
Perimeter.
Lets configure the Perimeter.
Step 171: Select the Icon at the lower Left screen this will bring up the Perimeter
drawing tool.
111
Step 172: From the drawing tool click on a point outside the map location and create
points by a single mouse click.
Step 173: When you have defined the area double click the mouse to release the
drawing tool and then click add.
Next we will edit the Perimeter. When a Perimeter has been created click on the same Icon
that you used to draw the perimeter before and click inside the existing Perimeter.
The Perimeter will turn purple and the points will be shown where you can then click on them
and adjust the Perimeter coverage area.
112
Step 174: Click on the edit perimeter icon
Step 175: Select a Purple Point on the Perimeter and Move to edit the Perimeter
When you have adjusted the Perimeter the way you would like now you can build zones.
Step 176: Click on the Icon above the Perimeter Icon.
You will be presented a screen that asks you to name the Zone.
113
Step 177: Choose a name and then click add.

Note Zones must be contained within the Perimeter.
A drawing tool will appear and you can now draw different zones.
New zones must be contained within the Perimeter.
Step 178: Create at least two zones on the map to show use Location Services.
114
115
After the zones have been created you can go to the drop-down on the Lab Zone under Floor_1
and add tags.
Tags are used to categorize locations and devices.
Step 179: Click on a Zone from the Menu on the left and select a Zone.
Step 180: Create a Tag for that Zone and Name it. (Your choice)
Now will configure a Perimeter for the Corp building.
116
Step 181: Click on Campus and Building, Corp, Floor2 and Create a Perimeter.
117
Step 182: Click on the drawing Icon to Edit the Perimeter and use the Points to size
the Perimeter.
Step 183: Create Zones for the Corp Building and Add them to the Map.
If you want to edit the Zone click on the Edit Zone Icon and then the drawing Icon.
You will see dots around zone.
118
Step 184: Click on a point and adjust the size.
Step 185: Continue to create new zones we will use these zones later when
configuring Verticals.
If you wish to change the name of a Zone you can select the zone and under Zone Item change
the name.
You can also change the Tag.
119
Now that the Zones have been configured we will look at the heat maps that are generated by
using the APs and the integration with the Prime Infrastructure for the placement of the APs
and the mapping and the calculation and movement of devices.
Step 186: Click on Corp Floor2 and bring up the map.

You will see that the APs are displayed as well as devices that have been detected by the APs.
If you need to adjust the size of your map use the + - buttons.
120
Step 187: Click on the fire Icon to bring up a heat map and the Square icon that brings
up Zones.
Step 188: Click on the Config Icon in order to change the Refresh rate in order to
collect movement data.
Note: be careful when adjusting the Refresh rate on a production system.
Observe the devices moving for a couple of minutes and choose a device that is actively
moving.
121
We will be testing the movement playback feature.

Step 189: When you choose a device you will see a list of parameters come up.
Step 190: Copy the Mac address and paste it in the search function.
Step 191: When Client has been selected press the playback icon.
This will allow you to see the movement of the client over time.
Devices are shown in the map.

122
Step 192: Click on a device you will be able to view which APs have detected it.
Now we will test the Analytics portion of CMX.
A report template will show up with fields that you can select. We will build a report in the next
screen.
123
Step 193: Choose Zone from the Building Drop Down menu.
124
Step 194: Choose a date and time of This Week.
Step 195: Changing the Dwell Threshold and change it to one minute.
Note: this is being changed for Lab purposes only changing to one minute in a production
environment will give skewed results for number of clients.
125
Step 196: Click done and you will see a report page.
Notice that you will see Total Visitor Account as well as top Zone from a Visitor and for Dwell
time.
You can also see a graphic representation of Visitors by Zone.
CMX is using the Zone boundarys that were created in order to calculate these analytics.
126
Section 1.3 Verticals

CMX Analytics comes packaged with a report generator that can automatically generate reports with
the most important metrics for specific businesses. By selecting a vertical, you can take advantage of
predefined reports that can help you make informed decisions based on the vertical your network is set
up for. This feature is called verticalization.
Step 197: Go to https://10.1.20.251 and enter

Username: admin
Password: admin1
Step 198: Select Manage and then Verticalization.
There are several different verticals you can choose we will select retail for this lab.
127
Step 199: Once you have selected the vertical click the Run Setup Wizard button.
Step 200: The Setup Wizard will walk you through the steps of setting up a vertical.
Step 201: Press the Get Started button to start the Wizard.
First label the Campus we will keep the default name.
128
Step 202: Press the Continue button to proceed.
Step 203: Next you will be presented with the Building. We will keep it default.
129
Step 204: Next you will be presented with the Floor. We will keep it default.
Step 205: Next you will be presented with the Zone. We will keep it default.
Step 206: When done click the Review Button.
130
Step 207: You will see that the hierarchy levels click the Save button.
Step 208: Next we will create assign Tags select the Continue button.
You will see a list of Tags that you can select.

We will choose a few Tags.
When you have chosen your Tags
131
Step 209: Press the Continue button.
Once you have selected your tags you will be presented with your selections.
Step 210: Click on the Save & Continue button.
Now the custom Tags are being created.
132
Step 211: Press the Continue button.
Once the Location Tags have been created they will be placed with the corresponding zones.
We will be using the same Zones that were created in the previous lab but tag the zones with
the new tags.
133
Step 212: Select the SRE_Campus_PodX, then select the corresponding Tags that
were just created.
Step 213: Then select the Continue button to Tag the Campus.
Next you will go down a level to the building and Tag the building.
134
Step 214: Click on the Continue button.
Step 215: Next click on the Zone and Tag the Zone.
In this example we are editing the Corp Executive Zone and will add the tags for Sporting Goods
to that Zone.
135
Step 216: Repeat the step above to apply other tags to a Zone.
Step 217: Repeat steps to add more Tags.
136
Step 218: Once Tagged Items have been added and verified against Zones press the
Continue button.
You will see a success page that will ask you now to run a report.
Step 219: Click on the Create a Report button.
The report genterator will look very similar to the report you configured previously in the lab.
137
The output now is Vertical specific and includes Top Tag for Dwell time and Top Tag for
Visitors.
There is also a Total Visitors and repeat visitors.
Repeat visitors are Mac address that have been tracked previously.
138
Note that dwell time is now average shopping time and is catagorized by new and repeat
visitors.
CMX Presence
Section 1.1 Configuration
Note you cannot have CMX that is running both Location and Presence on the same instance.
Step 220: Note the IP address change of the CMX Presence Server.
https://10.1.20.151:1984
Username: cmxadmin
Password: Cisco123!
139
Step 221: REPEAT STEPS 142-150 EXCEPT SELECT PRESENCE IN SETUP

If the WLC is not connected go to the Action Tab and then the Edit link.
The Controller SNMP information can be checked.

Step 222: IP Address and for the Controller SNMP Write Community use the
Community string specified in WLC Exercise.
140
Step 223: Go to Presence Analytics and Manage.
Step 224: Click on the Add Site button.
Under the New Site enter the Name and Address. You can check and adjust the the Signal
Strength Threshold.
By adjusting the Passerby and Visitor settings you can tune analytics.
Note: Prescence does not use mulitple APs for location calculation.
So only RSSI is used to calculate position of device.
141
Step 225: When you have adjusted the settings as needed click on the Save button.
Step 226: Now add APs to the site. Under Presence Analytics choose Access Points.
Step 227: Under APs by Controller you will see a list of AP currently associated to the
Controller.
Step 228: Select AP Branch1 and Branch2.
Use Ctrl-a for multiple selections.
142
Step 229: When APs have been selected click the Add to Site button.
143
Step 230: A site list will come up select Branch and then the Add button
Going back to the main screen and Sites you will now see Branch with two APs associated to the
Branch.
Step 231: Go back to the Dashboard and you will see the Analytics collected.
Let the system run collecting information and review this section again for more updated data.
144
Now we will build an Analytics report. This report can be done several different ways we will
use PDF format.
Step 232: Select the PDF Icon.
Enter Notes if desired and an optional email address.
145
Step 233: Click Submit to start report generation.
Report will compile you will see the hour glass moving until the report is ready.
146
Step 234: After the Report is generated you can click on the link to download the
report.
Report is presented in the browser window.
147
Section 1.2 Portal Setup

There are several types of portals that CMX supports including Facebook, and Twitter.
There is also a Custom Portal that you will be building.
Step 235: Go to https://10.1.20.151
Login with
Username: admin
Password: admin1
Step 236: Go to the Connect & Engage Tab.
148
Step 237: From the Connect & Engage to to Connect Experiences.
Step 238: Under Custom Portal click on Create Default.
Step 239: Name the Portal SRE_Portal and then click on the Custom Portal.
149
Step 240: Click on the Next button to proceed.
Step 241: From the portal widget page select Content and then Image Element.
150
Step 242: Select Choose Image.
Step 243: Select an Image to upload from the the Desktop PC

Desktop\Portal_Images\ and file cisco and then click open.
151
Step 244: Click on the Image and select upload.
Step 245: To resize the image select height.
152
Step 246: To get back to the Content click on the Content.
Step 247: Click on the Registration Form to add to the Portal Page.
153
Step 248: Expand the input fields to see required and optional fields for the
Registration form.
Step 249: Go back to Content elements and select the Submit Button.
154
Step 250: You can modify the fields on the Submit button.
If you want to change Languages go to Select Language.
155
Step 251: Save the portal settings by pressing the Save & Assign button.
Step 252: The portal is now saved and assigned to a Global Location.
156
Step 253: Go to the Connect Experiences and then Click on the Branch and then on
the SRE_Portal.
Step 254: Click on the Custom Portal information button to see the URL that you will
need later.
157
Step 255: Copy the https address to be used for the WLC.
Step 256: Click on the Post Auth URL to create a URL for for post authentication.
Step 257: Enter http://www.cisco.com and then click set.
158
Step 258: See that the Post Auth URL is bound to Branch.
Setting up the Controller for a Captive Portal

Step 259: Login into the Controller
Username: admin
Passwod: Cisco123
159
Step 260: Go to Advanced to pull up the WLC menu.
Step 261: Under Security click on Access Control Lists.
160
Step 262: Check New under Access Control Lists to configure new ACL.
Step 263: Name the ALC SRE_Portal and then Apply.
Step 264: Click on the link to SRE_Portal to configure ACL.
161
Step 265: Click on the Add New Rule.
Type in the following:

Sequence:
1
Source IP Address: 10.1.20.151 255.255.255.255
Protocol:
TCP
Source Port:
HTTPS
Action:
Permit
Note: CMX 10.2 sslmode is enabled by default
Step 266: Click Apply.
162
Step 267: Click Add New Rule.
Type the following:

Sequence:
Source:
Destination IP Address:
Protocol:
Source Port:
Destination Port:
Action:
Step 268: Click Apply.
2
Any
10.1.20.151 255.255.255.255
TCP
Any
HTTPS
Permit
163
Step 269: Check the ACL to verify
Step 270: Go to WLANs and click on WLAN 2 link.
Step 271: Click on the Security Tab.
Step 272: Check that Layer 2 Security is set to None.
164
Step 273: Click on the Layer 3 Tab.
Step 274: Use the pull down box and Web Policy.
Click on Passthrough
Preauthenticaton ACL:
Over-ride Global Config:
Web Auth type:
URL:
Click Apply
IPv4 choose SRE_Portal

Enable
External
https://10.1.20.151/visitor/login
165
Step 275: Click Ok to warning about possible loss of client connectivity.
Client Testing:
166
Step 276: Go to PC2 control panel, Network sharing, adapter settings.

Step 277: Right click and search for wireless networks and click connect.
167
Step 278: Select podXbranch network (Where X is your assigned Pod)
168
podXbranch is now connected
Step 279: Open your FireFox browser.
The following URL will appear note that it is the 10.1.20.151 redirect address as well as the
1.1.1.1 Virtual Interface.
169
Step 280: Click on the Add Exception and Confirm Security Exception
You will see the portal page being displayed.
170
Step 281: Enter the name SRE and email address: test@cisco.com
The Virtual Interface Address will be shown again from Firefox.

Step 282: Click on add exception and confirm exception.
171
172
You will see the redirection to www.cisco.com
CONGRATULATIONS YOU HAVE COMPLETED THE CMX 10.2 LAB
173

CMX V1.0 160616

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CMX V1.0 160616

Uploaded by

Copyright:

Available Formats

Converged Mobile Experience

CMX Version 10.2

Solutions Readiness Engineers

Cisco Connected Mobile Experience v10.2 Lab Guide

Infrastructure Design and Components

APs are used for client connectivity.

Radio Frequency Principles for Location Services

Cisco Prime Infrastructure RF Planning Tool

Deployed from CCO ISO

Physical and Logical Topology

Exercise 1: Access the Lab Environment and Baseline the

Section 1.1 Review the Solutions and Network Design

Section 1.2 Access Your Lab Pod

Step 6: Carefully enter the following credentials and click Login:

Username: stu-xx (Where xx is assigned by your instructor)

Step 7: Click Continue in the resulting welcome message.

Section 1.3 Review and Test the Existing Network

The desktop pictured below will load.

Wireless LAN Controller (WLC) Configuration

wlcpodX (Where X is your assigned Pod Number)

Service Interface IP Address Configuration: DHCP

Configure DHCP Bridging Mode:

Step 18: After the system, restarts login:

Section 1.2 WLC GUI Configuration

Step 23: Click on Proceed to 10.1.20.252.

Step 24: Click the Login button.

Step 28: Click on Network Summary.

Step 29: To configure the Controller, click on the Advanced Link.

Step 30: In the left navigation menu, click on Access Points.

Step 39: Click the All APs link again.

Step 52: Click on the Add Group Button.

Step 56: Select the WLANs tab.

Step 58: Next, click the APs tab.

Step 65: Once the configuration is successfully saved, click OK.

END OF THE WLC SETUP LAB

Step 70: From the browser, go to https://10.1.20.250

Section 1.2 Device Inventory

Step 76: Click the SNMP button.

Section 1.3 Adding Maps to Prime

Section 1.4 Adding APs to Branch Map

You can practice moving the APs if you wish to do so.

New position of the APs and associated heat maps.

Section 1.5 Adding Corporate Maps

Section 1.6 Adding Corp APs

Practice moving the APs to the desired locations.

Section 1.7 Monitoring AP Alarms in Prime

Step 123: Do the same for the 802.11 b/g/n radios.

Section 1.8 Map Editor

With the Map Editor we will be configuring Inclusion Zones.

Step 127: Click on Map Editor

This will pull up the Map Editor.

Step 136: Click on the OK button.

Step 137: Click on the OK button.

Step 139: Click on the SRE_Branch_Bld>Floor_1 to pull up the map.

THIS ENDS THE PRIME INFRASTRUCTURE EXERCISE

The username: cmxadmin is automatically populated in the username field.

Service configuration process.

Service Start Process.

When the Service Start process is finished a link will appear.

If CMX session expires

Import Controller process.

Importing the Controllers will also import associated Maps.

Step 150: Setup is now finished click on the Finish button