Brkagg-2012 0101

Cisco Motion: Design and Deployment of Context-Aware Mobility Services
BRKAGG-2012
Presentation_ID
2009 Cisco Systems, Inc. All rights reserved.
Cisco Public
Abstract
The Cisco Context Aware Mobility solution (which includes location-based services) is an important advanced service that can be provided with the Cisco g unified WLAN network. This session focuses on design and deployment fundamentals, as well as operational best practices to optimize the performance and accuracy when tracking wireless devices (tags and wireless clients) using the Cisco Context-Aware Mobility solution.
BRKAGG-2012
Cisco Public
Agenda
Overview - Principles of Context-Aware Mobility Solution Technology Background System Architecture Network for Context Aware: Planning and Setup Validation And Improvements Of Context Aware Network Final Checklist
BRKAGG-2012
Cisco Public
Technology Background
BRKAGG-2012
Cisco Public
Terminology
Mobility Services Engine (MSE): appliance designed as an open platform that supports multiple mobility services as software applications Network Mobility Services Protocol (NMSP): Cisco-defined protocol t l used df for secure communication i ti b between t WLC MSE Clients: all endpoint devices that connect/associated through wireless network Rogue AP: any access point that is determined not to be part of the wireless LAN mobility group that detected it Rogue clients: all devices that are associated to rogue access points. Active RFID tags: Wi-Fi device that can be detected and located on Wi-Fi Wi Fi network t k
5
BRKAGG-2012
Cisco Public
Receive Signal Strength Indication (RSSI) Overview

Cisco RSSI-based location tracking solution based on network-side RSSI measurements Requires min. of three APs; optimal accuracy requires more than 3 APs AP s Best suited for indoor office-like environments (carpeted, low ceiling, i.e. < 20 feet) Main factors affecting accuracy:
AP density AP placement RF environment
BRKAGG-2012
Cisco Public
Time Difference of Arrival (TDoA) Overview

Based upon relative differences in time measurement Requires clock synchronization at receivers, but not the mobile device Requires min. of three time-synchronized TDoA receivers Ti Time for f message to t be b received i d at t different diff t receivers i is proportional to length of transmission path between the mobile device and each receiver
BRKAGG-2012
Cisco Public
Time Difference of Arrival (TDoA) Overview (continued)

Each TDOA installation must have at least one synchronization source
Depending on the size of the site, may require more than one synchronization y source TDoA receiver can act a synchronization source as well as a TDOA receiver for locating transmitting devices
Physical placement of TDoA receivers must be non-colinear O Operates t well ll i in multipath lti th and d hi high-ceiling h ili environments
Possible to achieve high g accuracy y( (35m) ) even in difficult, , industrial environments
BRKAGG-2012 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
Device Tracking - WCS
client: tag:
Rogue AP: Rogue clients:

9
System Architecture
BRKAGG-2012
Cisco Public
10
MSE Software Overview

Hardened Linux-based appliance Hardening split into two types configurable and non configurable
configurable some items must be configured by the user via setup script (e.g. root/GRUB passwords, hostname, gateway) Non-configurable g unneeded services and users disabled or shut down (e.g. inetd, ftp, uucp)
Will host multiple software services

In software release 5.1, hosting only CAS In software release 5.2, wIPS and MIR services hosted on MSE
BRKAGG-2012
Cisco Public
11
Mobility Service Engine Internal Architecture

Context Aware Context Aware Engine for Clients Engine for Tags HTTP/ SOAP SIP Listener AAA Service Engine Manager Licensing Control Monitoring Backup Restore
DB
Message Bus/Router Reliable Asynchronous Secure Messaging
NMSP Module
Network Repository wIPS Client Mgmt Engine
Common
CLI
Common Services
BRKAGG-2012
Cisco Public
12
Role of MSE - Context Aware

Execution of positioning algorithms Maintenance of calibration information gg g and dispatch p of location notifications Triggering Processing of statistics and historical location
BRKAGG-2012
Cisco Public
13
Context Aware Software Architecture

Business Application
SOAP/XML API
Context-Aware Software
MSE
Context C t tA Aware Engine for Clients

RSSI
Context C t tA Aware Engine for Tags

RSSI / TDOA
Si
Si
Mobile User Voice over 802.11 Smart Phone
802.11 Clients
802.11 CCX Tags
Indoor Environment
BRKAGG-2012 2009 Cisco Systems, Inc. All rights reserved.
Indoor & Outdoor Environments

Cisco Public
14
Cisco Context Aware Mobility Solution

Tracking Tags and Clients
Applicat tion and Management
Tracking tags (indoor and outdoor/outdoor-like) outdoor/outdoor like) Context-aware engine for tags (partner engine) Utilizes:
LWAPP infrastructure for indoor environments Wi-Fi TDOA receivers for outdoor and outdoor-like outdoor like environments Partner HW/SW managed by System Manager (partner) and Cisco WCS
Wi-Fi TDOA Receiver Cisco 3350 Mobility Services Engine Context Aware Engine for Tags Context Aware Engine for Clients
Si
Cisco Wireless Control System (WCS)
Context Aware Software
Netw work
Tracking clients (indoor) Context aware engine for clients (Cisco engine) Utilizes LWAPP infrastructure Managed by Cisco WCS
AeroScout
Chokepoint 125 kHz
Tag g and Dev vices

15
Required Components Client and Tag Tracking

Client Tracking Tag Tracking
WCS
Cisco WCS PLUS with Cisco WCS PLUS with location location Client client tracking license with appropriate client count Client tag tracking license with appropriate client count (TDoA or RSSI) TDoA location receivers (if and when required) q ) LR license for each TDoA receiver
MSE License
Additional Components
None
BRKAGG-2012
Cisco Public
16
Cisco Wireless Deployment with CAS

WCS Client Browser HTTPS Cisco WCS Location Client
Location API via SOAP/XML over HTTPS Cisco Mobility Services Engine (MSE)
Cisco Wireless LAN Controller
NMSP
Access Point
AeroScout System Manager and Analyzer
NMSP Network Mobility Services Protocol (port 16113)

17
BRKAGG-2012
Cisco Public
Historical and Statistics Trending

MSE records and maintains historical location and statistics information for clients and tags Can be viewed via WCS or using 3rd-party location clients By default, default 30 days of historical data is stored in the MSE
MSE will not delete historical data before the 30 day window has been reached
Th The greater t the th number b of f element l t transitions t iti per minute, i t th the greater the amount of disk space that will be consumed Cisco recommends changing the history parameter for devices that are moving frequently to a value less than 30 days
BRKAGG-2012
Cisco Public
18
Historical Data Storage

Transitions Per Minute 100 200 300 400 500 600 700 800 900 1000
Number Of Rows In History Table After 1 Day 144,000 288 000 288,000 432,000 576,000 720,000 864,000 1 008 000 1,008,000 1,152,000 , , 1,296,000 1,440,000
Cisco Public
Days to Hit 10 Million Rows 69.44 34 72 34.72 23.15 17.36 13.89 11.57 9 92 9.92 8.68 7.75 7.14
19
Cisco Extensions (CCX) for Wi Wi-Fi Fi Tags

partnered with a variety of asset tag vendors to create an extensible specification for 802 802.11 11 Wi Wi-Fi Fi based active asset tags defines a common transmission format that tag vendors can use to interoperate with the Context Aware Cisco UWN includes a baseline feature set that includes telemetry, tag transmit power level, battery information, and advanced fields for emergency groups and chokepoints allows customers to take advantage of these capabilities and "mix and match" compliant asset tags from different vendors in the same network currently, tag vendors have implemented CCXv1
BRKAGG-2012
Cisco Public
20
Network for Context Aware: Planning and Setup
BRKAGG-2012
Cisco Public
21
Use Case Scenarios

INDOOR + Clients (RSSI) INDOOR + Clients + Tags (RSSI)
HIGH CEILING + Clients + Tags

(RSSI & TDOA)
OUTDOOR + Tags
(TDOA)
BASELINE ASSUMPTIONS:
Pervasive Cisco Unified Wireless Network (RSSI) Controller Based Architecture (RSSI) Wi-Fi TDOA Receivers (TDOA) WCS Software
22
WLC Client and Tag Tracking Capacity

WLC Model WLCM 2106/12/25 Catalyst 3750G with Integrated WLC 4402 4404 WiSM
Client Capabilities 500 500 2 500 2,500 2,500 5,000 10.000
Tag Capabilities 256 256 2 500 2,500 2,500 2,500 5,000

23
WCSPorts WCS Ports Used

Name Database FTP TFTP HTTP HTTPS HTTP Connector HTTP Connector Redirect NTP RMI Trap Web Container
Port Number 1315 21 69 80 443 8456 8457 123 1299 169 8009
24
MSEPorts MSE Ports Used

Name NMSP FTP SSH HTTP HTTPS Port Number 16113 21 22 80 443
BRKAGG-2012
Cisco Public
25
RSSIAP RSSI AP Placement Guidelines

Optimal accuracy is normally received with more than 3 APs In quadrilateral area, min. of four APs should be installed at the four corners of the area Factors affecting accuracy: AP placement placement, wall materials materials, large moving objects, RF interference May need to sub-divide floor space into sub-areas and design/deploy sub-areas independently to account for large barriers that obstructs RF signals Recommend using antenna diversity - helps ensure optimal range and throughput in high multipath environments For wireless data only deployments: 10% AP cell overlap For wireless data + voice deployments: 20% AP cell overlap
BRKAGG-2012
Cisco Public
26
RSSIGeneral RSSI General Deployment Guidelines

AP should be placed every 50-70 linear feet (~17-20 meters)
Translates to one access point every 2,500 to 5,000 square feet (~230-450 square meters)
APs should preferably be positioned along and within the perimeter of an enclosed area APs should be distributed evenly, i.e., APs should be relatively equadistant from each other Ph Physical i l placement l t of f APs AP should h ld b be non-colineareven li when h placed l d at t equal distances from each other Geometric shapes formed by the distribution of APs affect accuracy
Equilateral triangles placement will yield better accuracy than APs that form an obtuse triangle Square deployment placement yields better results than APs that form rectangles
BRKAGG-2012
Cisco Public
27
AP Placement Examples
Poor AP placement and coverage g for location
Good G d AP placement l t and d coverage for location
BRKAGG-2012
Cisco Public
28
AP Placement Examples
Wi-Fi device
Poor AP placement and coverage for location linear AP placement
Wi-Fi device
Proper AP placement and coverage for location staggered AP placement with perimeter coverage
BRKAGG-2012
Cisco Public
29
MSE System Configuration

Use the following command which starts wizard to guide the user in setting the system parameters
/opt/mse/setup/setup.sh
/opt/mse/setup/setup.sh must be used for

Host name / Domain name changes Changing system IP address/subnet Dual homing Routes configuration Console/ssh access settings Root password changes WCS user password changes
30
MSE Start/Status/Stop
For managing Context Aware Engine for Clients Start command: /etc/init.d/msed start Status command: /etc/init.d/msed status Stop command: /etc/init.d/msed stop Restart command: /etc/init.d/msed /etc/init d/msed restart
BRKAGG-2012
Cisco Public
31
getserverinfo getserverinfo Command

root@MSE ~]# getserverinfo MSE Platform is up, getting the status ------------Server Config ------------Product name: Cisco Mobility Service Engine Version: 6.0.62.0 Hw Version: V01 Hw Product Identifier: AIR AIR-MSE-3350-K9 MSE 3350 K9 Hw Serial Number: MXQ828A4L9 Use HTTP: false Legacy HTTPS: true L Legacy P Port: t 8001 Log Modules: 262143 Log Level: INFO Days to keep events: 2 Session timeout in mins: 30 DB backup in days: 2
32
------------Services ------------Service Name: Context Aware Service Service Version: 6.0.42.0 Admin Status: Enabled Operation Status: Up
Service Name: Wireless Intrusion Protection Service Service Version: 1.0.1103.0 Admin Status: Enabled Operation Status: Up
BRKAGG-2012
Cisco Public
getserverinfo getserverinfo Command

------------Context Aware Service ------------Total Active Elements(Clients, Rogues, Interferers): 129 Active Clients: 34 Active Tags: 29 Active Rogues: 66 Active Interferers: 0 Active Wired Clients: 0 Active Elements(Clients, Rogues, Interferers) Limit: 100 Active Tag Limit: 100 Active Wired Clients Limit: 0 Active Sessions: 1 Clients Not Tracked due to the limiting: 481 Tags Not Tracked due to the limiting: 0 Rogues Not Tracked due to the limiting: 1306 Interferers Not Tracked due to the limiting: 0 Wired ed C Clients e ts Not ot Tracked ac ed due to the limiting: 0 Total Elements(Clients, Rogues, Interferers) Not Tracked due to the limiting: 1787 ------------Context Aware Sub Services ------------Sub Service Name: aeroscout Version: 3.2.0 - 4.0.14.13 Description: AeroScout Location Engine for RSSI and TDOA asset tracking Registered: true Active: true Watchdog Process ID: 25579 Engine Process ID: 25761
# of active NMSP sessions
# of devices not tracked due to licensing
# of active NMSP sessions
AeroScout engine version info
33
Finding Detailed Info On Partner Engine

[root@MSE ~]# rpm -qi aeroscout-engine Name Version Release : aeroscout-engine aeroscout engine : 4.0.13 : 11 Relocations: (not relocatable) Vendor: AeroScout Build Date: Mon 06 Oct 2008 07:43:32 AM PDT Build Host: talim
Install Date: Tue 25 Nov 2008 05:46:17 PM PST G Group Size : Applications/System A li ti /S t : 249409173
S Source RPM RPM: aeroscout-engine-4.0.13-11.src.rpm t i 4 0 13 11 License: Commercial
Signature : (none) Summary Description : AeroScout computation engine [root@MSE ~]# : Build
BRKAGG-2012
Cisco Public
34
Add MSE to WCS
Change in WCS Menu from Location/Location Servers to Mobility/Mobility Service Engine

35
Separate Menu Items for

BRKAGG-2012
Location Server (Cisco 2710)

Cisco Public
and Mobility Service Engine

36
BRKAGG-2012
Cisco Public
37
Adding WIFI TDOA Receivers To MSE/WCS

TDOA Receivers must be connected to the network Receivers are added to WCS specifying their MAC address and static IP address Receivers are positioned on maps in WCS WCS maps are synchronized with MSE running C t t Aware Context A (partner ( t engine) i ) Receivers are configured with IP address and TDOA parameters using Aeroscout System Manager
BRKAGG-2012
Cisco Public
38
Place Location Sensors Using WCS Map Editor
BRKAGG-2012
Cisco Public
39
TDOA Outdoor Deployment
BRKAGG-2012
Cisco Public
40
Location Optimized Monitor Mode

Prior to 5.0 release (WLC and WCS)
Regular AP (local mode) + monitor mode AP (rogue, IPS)
With 5.0 release (WLC and WCS)

Same as above + LOMM APs
Good for periphery of buildings to improve location accuracy without ih adding ddi extra traffic ffi that h may i impact voice or client services Ensure that channels on LOMM APs AP s are configured to be the same as the local mode APs
Controller CLI for changing monitor mode channels
BRKAGG-2012
Cisco Public
41
Design Criteria - Voice and Location

For wireless voice deployments: cell-to-cell overlap = 20%
more stringent than data deployments (10% cell-to-cell overlap) voice i +d data t d deployments l t may require i cell ll overlap l of fV VoWLAN WLAN deployment
Balance AP p placement to optimize p for voice coverage g and location accuracy For location, 3 APs placed in 3 out of 4 quadrants within 4070 ft. f of f all locations within the convex hull of f APs to meet 90%/10m accuracy without detailed calibration
BRKAGG-2012
Cisco Public
42
Design Criteria - Voice and Location (Cont)

Location Optimized Monitor Mode (LOMM) APs: place APs evenly spaced on perimeter perimeter, quadrant quadrant-based based deployment within perimeter
Shuffle APs to even out perimeter and inside APs spacing
Local + LOMM ( (Location Optimized p Monitor Mode): ) q quadrantbased deployment inside coverage area for voice/location coverage plus APs evenly placed around the perimeter Leverage new location deployment tools introduced in location appliance 4.0 software release :
Location optimized monitor mode Site survey and interpolated heat maps Location accuracy tool
BRKAGG-2012
Cisco Public
43
Deploying LOMM AP APs s

LOMM L Local l LOMM
Local mode AP placement and density may be sufficient for data/voice applications Use LOMM APs to fill in coverage gaps
Wi-Fi device
Local LOMM Local
BRKAGG-2012
Cisco Public
44
Site Survey and Calibration

More data points are generated internally when using 5.0 release System obtaining more information from the network Point calibration: client at fixed location Linear calibration: data collected between two different ff points (straight line) Requires CCX v2 compatible client
Calibration with non-CCX clients will not be supported from software version 5.0 onwards Old method of calibration not supported starting with software version 5.0
Faster calibration process vs. previous calibration mechanism
BRKAGG-2012
Cisco Public
45
Calibration Point Mode
Represents completed calibration area
BRKAGG-2012
Cisco Public
46
Calibration date collected for entire floor space
BRKAGG-2012
Cisco Public
47
Represents completed calibration area
BRKAGG-2012
Cisco Public
48
Point Mode Calibration Results
BRKAGG-2012
Cisco Public
49
Calibration Linear Mode
Path of calibration data collection

50
Rails and Regions

Provides mechanism for defining inclusion/exclusion areas for location services Allows for certain regions in map to be defined as within or outside the scope of valid location area Three types of regions can be specified
Location inclusion region: tracked device cannot be outside of this polygon (examples: outside of building outer walls) Location exclusion region: tracked device cannot be inside of this polygon (examples: open atrium) Rails: tracked device must be within defined area with narrow band band. Typically used within exclusion region (examples: conveyor belt).
Regions defined in WCS and pushed (via synchronization process to MSE/2710
BRKAGG-2012
Cisco Public
51
Rails and Regions Configuration
Step 1:
Create Rails and Regions g Using g Map Editor
Step 2:
Synchronize (Pass Rails and Regions g Points to Location Appliance)
BRKAGG-2012
Cisco Public
52
Example p of: Inclusion Region Exclusion Region Rail (prompt for specifying Exclusion Region around line)
For Adding F Addi Location L ti F Adding For Addi Location L ti Inclusion Region Exclusion Region
F Adding For Addi Rails R il
BRKAGG-2012
Cisco Public
53
Viewing Regions and Rails on Floor Map
BRKAGG-2012
Cisco Public
54
Location Accuracy Tool

Two forms of accuracy testing
Scheduled accuracy On-demand accuracy
User can choose either method after selecting the floor to run the accuracy test.
All th these t tests t on the th same floor fl
BRKAGG-2012
Cisco Public
55
Scheduled Accuracy
Run on active environment (live network) Preposition clients and tags and schedule the test Uses actual location of an element vs. measured location User can modify f the test by:
Adding/deleting elements Changing positions Changing the schedules
Test can be run as a scheduled task and generate alarms if falls b l below certain t i range of f accuracy
Should be retested periodically as RF environment may change, impacting location accuracy
BRKAGG-2012
Cisco Public
56
Scheduled Accuracy Test
BRKAGG-2012
Cisco Public
57
On-Demand On Demand Accuracy

To be run when a user does not have any active client/tag deployments yet and is interested in measuring accuracy Can be run when a floor does not have prepositioned tags/clients Conducted similar to pre-5 pre 5.0 0 accuracy test with single client User places client at a particular location and indicates that location on the map by dragging the test point and dropping it User clicks on start and waits for few minutes for RSSI collection and clicks on stop button and can continue to move to the next point When user has collected all the points, they can choose to run the test by clicking on analyze results button. This will produce the accuracy result in a report.
BRKAGG-2012
Cisco Public
58
Wired Location
Users configure location data using Switch CLIs MSE provides the functionality to gather and maintain CIVIC location information for Switches and Switch ports WCS configures MSE with the list of Switches Switch and MSE communicate/sync with each other for location information using NMSP requests/responses. Switches notify wired client association/dis-association events to MSE MSE also tracks location history y of the wired clients MSE provides the APIs to search/track a client across wired and wireless categories Switches S it h supported t d - Catalyst C t l t 3750, 3750 3750E 3750E, 3560 3560, 3560E 3560E, 2960
59
BRKAGG-2012
Cisco Public
Major Interfaces
BRKAGG-2012
Cisco Public
60
Switch Side Configuration Steps

1. Understand the Slot/Module/Port configuration (1/0/20) 2. Use correct IOS version 12.2 (50) pertaining to the respective switch model 3. Enable NMSP 4 Enable 4. E bl IP D Device i t tracking ki 5. Configure SNMP Community with read-write access 6. Configure Civic/ELIN Location Identifiers 7. Assign identifiers to switch interfaces
BRKAGG-2012
Cisco Public
61
WCS Side Configuration Steps

1. Go to Configure >Ethernet Switches 2. Add Ethernet Switches
Add IP Address Enable Location Capable Enter the SNMP Community (read-write)
3. Go to Services > Synchronize y Services > Switches

Click on Assign to assign to preferred MSE Select the Switch and Synchronize
4. Go to Services > Mobility Services, and click on MSE

Go to System > Status > NMSP Connection status Check for active NMSP status for each switch
BRKAGG-2012
Cisco Public
62
Wired Elements Display on WCS

Under Context Aware Services, click on Wired Switches under Wired List of all the switches will be displayed Click on Switch IP Address to view details One can also view Switch ports and Civic information Wired clients seen by all the switches can be viewed by clicking Wired Clients under Wired
BRKAGG-2012
Cisco Public
63
Location Data
Formats
CIVIC Address (RFC 4776 / RFC 5139) GEO CISCO
Tracking
Current association and location History of associations and dis-associations
Searching S hi
Extensions to search across wired and wireless categories based on MAC Address, IP Address, 802.1x user name
64
Validation And Improvements Of Context Aware Network
BRKAGG-2012
Cisco Public
65
Use Location Readiness Tool

Use prior to calibration to gauge AP placement and coverage holes A point on map is l location-ready ti d if if:
min. of 4 APs are deployed min. of 3 APs are within 70 ft At least 1 AP placed in each of at least 3 surrounding quadrants.
BRKAGG-2012
Cisco Public
66
Location Location Ready Ready Point
<= 70 <= 70
<= 70
BRKAGG-2012
Cisco Public
67
Advanced Location Parameters

Relative discard RSSI time: time between the most recent RSSI sample and the oldest usable RSSI sample. Default = 3 minutes Absolute discard RSSI time: oldest RSSI value that will be used in location calculation. Default = 60 minutes RSSI cutoff: MSE will retain the 4 highest signal strength values plus any signal strength reports that meet or exceed the RSSI cutoff value value. Default = -75 dBm
BRKAGG-2012
Cisco Public
68
NMSP Overview
NMSP Network Mobility Service Protocol introduced in software v4.1 as LOCP and renamed to NMSP in 4.2 replaced SNMP as protocol between WLC and location appliance WLC C sends NMSP S message to MSE S either of f these conditions:
new client joins more than 5 dB change in the RSSI value
WLC uses NMSP messages to update MSE when device leaves the system WLC v5.0 1 NMSP connection per controller WLC v5.1 10 NMSP connections per controller
BRKAGG-2012
Cisco Public
69
Time Synchronization/Configuration
possible symptom of clock discrepancy between WLC and MSE: cant establish NMSP connection after adding MSE to the system suggested course of action:
Use NTP server ser er for s synchronizing nchroni ing clocks (recommended) Manual configuration (controller time should be ahead of time on MSE)
BRKAGG-2012
Cisco Public
70
Establishing NMSP Connection

MSE
root@mse ~]# cmdshell cmd> show server-auth-info invoke command: com.aes.server.cli.CmdGetServerAuthInfo ---------------Server Auth Info ---------------MAC Address: 00:1e:0b:61:35:60 Key Hash: 5384ed3cedc68eb9c05d36d98b62b06700c707d9 Certificate Type: SSC
==============================
MAC address and key hash for authenticating NMSP session between MSE and WLC
WLC
(Cisco controller) >config auth auth-list list add lbs lbs-ssc ssc <MSE Ethernet MAC> <MSE key hash>
Note: WCS template for adding MSE should create association between MSE and WLC automatically. Manual process should not be required.
71
Verifying NMSP Connection Status (WLC)

(Cisco Controller) >show nmsp status
LocServer IP -------------172.20.224.17
TxEchoResp ----------18006
RxEchoReq
TxData
RxData -------163023 ------10
--------18006
BRKAGG-2012
Cisco Public
72
Verifying NMSP Connection Status (MSE)

(Cisco Controller) >show auth-list
<snip>
Mac Addr ----------------------00:1e:0b:61:35:60
Cert Type ---------LBS-SSC
Key Hash -----------------------------------------5384ed3cedc68eb9c05d36d98b62b06700c707d9
MSE MAC address
MSE key y hash
BRKAGG-2012
Cisco Public
73
NMSP Monitoring UI
BRKAGG-2012
Cisco Public
74
If Tag Is Not Seen By WLC

Tags must be configured to beacon in 3 channels 1,6,11 and with 3 or more repetitions. repetitions
Example: 1,6,11, 1,6,11, 1,6,11
Check global RFID config on the controller

show rfid config
If the RFID tag detection is not enabled, enable it using the following command
config rfid status enable
Verify/set timeout parameters

config rfid timeout 1200 config rfid auto-timeout disable
Check RSSI expiry timeout

show location summary
If tag is still not seen by controller, use following debug commands

debug mac addr <tag mac addr> debug rfid receive enable
75
BRKAGG-2012
Cisco Public
If Tag Is Seen By WLC

Check to see if controller sees the tag
show rfid summary show rfid detail <MAC address>
If tag is seen by the controller but not seen in WCS, see if NMSP notifications are being sent to MSE
debug rfid nmsp enable
Verify y if the NMSP layer y on the controller is sending g notification

debug nmsp message tx enable
RSSI cutoff: MSE will retain the 4 highest signal strength values plus any signal strength reports that meet or exceed the RSSI cutoff value. Default = -75 dBm
BRKAGG-2012
Cisco Public
76
show show rfid summary summary Command

lists all of the RFID tags reported by APs including the following information:
RFID MAC address closest AP RSSI value time since the tag was last heard (Cisco Controller) >show rfid summary Total Number of RFID <snip> ----------------- -------- ------------------ ------ --------------------RFID ID VENDOR Closest AP RSSI Time Since Last Heard : 128
----------------- -------- ------------------ ------ --------------------00:04:f1:00:04:ea Wherenet sjc14-42b-ap4 00:04:f1:00:04:eb Wherenet sjc14-42b-ap4 sjc14 42b ap4 00:0c:cc:5b:fc:54 Aerosct 00:0c:cc:5b:fe:29 Aerosct sjc14-31b-ap9 sjc14-31b-ap2 -69 -75 75 -87 -92 52 seconds ago 27 seconds ago 63 seconds ago 22 seconds ago
BRKAGG-2012
Cisco Public
77
show show rfid detail detail Command

(Cisco Controller) >show rfid detail 00:0c:cc:5b:fe:29
RFID address..................................... 00:0c:cc:5b:fe:29 Vendor........................................... Aerosct Last Heard....................................... 4 seconds ago P k t Received................................. Packets R i d 561211 Bytes Received................................... 16836330 Detected Polling Interval........................ 14 seconds Bluesoft Type.................................... TYPE_NORMAL Battery Status................................... MEDIUM Nearby AP Statistics: sjc14-41b-ap8(slot 0, chan 6) 3 seconds.... -88 dBm
(Cisco Controller) >
BRKAGG-2012
Cisco Public
78
Client Location Debugging

see which AP the client is associated to and the RSSIs seen by the APs
show client summary show client detail <MAC address>
Verify that the RSSI timeouts for client are set to the default values
show advanced location summary
If RSSI values are different from the default values, set them to default using the following config commands
config advanced location expiry client <seconds> config advanced location rssi-half-life client <seconds>
Enable the load-balancing debugs which will show which APs heard the client and with what RSSI
debug mac addr <client mac> debug dot11 load-balancing load balancing enable
Debug notification related issues using the following commands

debug mac addr <client mac> debug dot11 locp enable debug nmsp message tx enable
BRKAGG-2012
Cisco Public
79
show show client summary summary Command

(Cisco Controller) >show client summary
Number of Clients................................ 276
<snip>
MAC Address Wired
AP Name
Status
WLAN/Guest-Lan Auth Protocol Port
----------------- ----------------- ------------- -------------- ---- -------- --------
00:02:8a:ea:55:15 sjc14-12b-ap5 No
Associated
Yes
802.11b
BRKAGG-2012
Cisco Public
80
show show client detail detail Command

Cisco Controller) >show client detail 00:02:8a:ea:55:15 <snip> Nearby AP Statistics: TxExcessiveRetries: 0 TxRetries: 0 RtsSuccessCnt: 0 RtsFailCnt 0 RtsFailCnt: TxFiltered: 0 TxRateProfile: [0,0,0,0,0,0,0,0,0,0,0,0] sjc14-11b-ap2(slot 0) ..................... antenna0: 308 seconds ago -86 dBm................ antenna1: 308 seconds ago -80 dBm sjc14-11b-ap1(slot 0) ..................... antenna0: 307 seconds ago -82 dBm................ antenna1: 307 seconds ago -91 dBm sjc14-12b-ap6(slot 0) ..................... antenna0: 307 seconds ago -66 dBm................ antenna1: 307 seconds ago -66 dBm sjc14-12b-ap3(slot 0) ..................... antenna0: 307 seconds ago -76 dBm................ antenna1: 307 seconds ago -64 dBm sjc14-12b-ap5(slot 0) ..................... antenna0: 7217 seconds ago -53 dBm............... antenna1: 7217 seconds ago -48 dBm sjc14-11b-ap5(slot j p ( 0) ) ..................... antenna0: 7217 seconds ago -79 dBm............... antenna1: 7217 seconds ago -75 dBm
BRKAGG-2012
Cisco Public
81
Final Checklist
BRKAGG-2012
Cisco Public
82
Deployment Checklist
Follow proper AP placement guidelines (location and density) Configure NTP server on both WLC and MSE or manually synchronize both the devices (and preferably WCS) with the correct time and time zone.
Note: controllers use GMT(UTC) time with correct time zone to derive local time. Consequently, time needs to be entered in UTC and the correct time zone specified specified.
Specify which controllers should talk to which MSE using the WCS MSE Synchronization page Check that certificates are exchanged correctly Check ec t the e NMSP S co connection ect o status o on t the e co controller to e C Ensure that tracking is enabled for the right devices Ensure that the maps and AP positions are synchronized between the WCS and MSE Ensure that location calculations are taking place either on the tracking page or the MSE console using getserverinfo command For Clients Verify tracking is enabled on MSE Verify V if clients li t are d detected t t db by controller t ll Max calculation time taken into account For Tags Verify tracking is enabled on MSE Verify tags are detected by controller Max calculation time taken into account
83
3310 MSE vs. 3350 MSE

Hardware and Software Specifications
3310 Mobility Services Engine 3350 Mobility Services Engine
(1) Dual-Core Intel Processor 1.8 GHz 4-GB PC2-5300 ( (4 x 1 GB) )
(2) Quad-Core Intel Xeon Processors 2.33 GHz 8-GB PC2-5300 ( (4 x 2 GB) )
(2) Fixed 247-GB Serial ATA-150 / SATA- (2) Hot-swapable 137-GB SAS-300 MBps 300 MBps drives Available with Cisco MSE Software Available with Cisco MSE Software R l Release 5 5.2.xxx 2 or l later. t R l Release 5 5.1.xxx 1 or l later. t Requires WLC software version 4.2.130 or later and WCS version 5.2 or later. Requires WLC software version 4.2.130 or later and WCS version 5.1 or later.
Mobility Services may have different WLC / WCS software requirements

84
3310 MSE vs. 3350 MSE

Service Support
3310 Mobility Services Engine 3350 Mobility Services Engine
Supports Adaptive wIPS for up to 2,000 Monitor Mode APs
Supports Adaptive wIPS for up to 3,000 Monitor Mode APs
Supports Context Aware for up to 2,000 tracked devices Supports Mobile Intelligent Roaming for up to 500 simultaneous registered devices
Supports Context Aware for up to 18,000 tracked devices
Does not currently support MIR
BRKAGG-2012
Cisco Public
85
MSE-3310 Service Support Matrix

wIPS and Context Aware
Clients / T Tags g
2000
Y Y Y
0 1000 2000
1000
wIPS Monitor Mode APs

86
MSE-3350 Service Support Matrix

wIPS and Context Aware
18000
Clien nts / Ta ags g
Y Y Y Y
0 1000 2000 3000
12000
6000
wIPS Monitor Mode APs

87
Co-Existence Co Existence Notes

Coexistence limits are not enforced Warning messages will be displayed when limits exceeded Performance will be impacted Over the limit combinations will be non-TAC supported
BRKAGG-2012
Cisco Public
88
Cisco WCS Supported Versions

WCS Software Version 4.2 5.0 51 5.1 Minimum Release Required Unsupported version Unsupported version MSE 3350: 5.1.xxx or later MSE 3310: not supported 5.2.xxx or later
5.2
BRKAGG-2012
Cisco Public
89
Cisco Wireless LAN Controller (WLC) Supported Versions

WLC Software Version 4.2 5.0 51 5.1 Minimum Release Required 4.2.xxx (xxx>=130) or later 5.0.xxx (xxx>148) or later 51 5.1.xxx or l later t
5.2
5.2.xxx or later
BRKAGG-2012
Cisco Public
90
Cisco 2710 vs. Cisco MSE

Feature Supported pp customer environments Cisco 2710 Cisco MSE Indoor low-ceiling g( (RSSI) ) Indoor low-ceiling g( (RSSI) ) Indoor high-ceiling (TDOA) Outdoor (TDOA) RSSI only RSSI TDoA Future technologies Cisco Partner MSE 3310: 2,000 MSE 3350: 18,000 Multiple p ( (Context Aware Mobility Solution, wIPS, MIR)
91
Supported location technologies Supported location engines Max. number of tracked Wi-Fi devices Number of services supported
Cisco only
2,500
g ( (location only) y) Single
Cisco Public
Recommended Reading
Cisco Wi Fi L Wi-Fi Location-Based ti B dS Services i 4 4.1 1D Design i G Guide id http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/lbswifig_external.pdf Cisco 3350 Mobility Services Getting Started Guide Cisco Context Aware Software Configuration Guide Cisco MSE Deployment Guide
AeroScout Indoor Deployment Guide for Wi-Fi Access Points AeroScout Exciter Deployment Guidelines AeroScout Engine for Cisco Mobility Services Engine TDOA Deployment Guide htt // http://support.aeroscout.com t t
BRKAGG-2012
Cisco Public
92
Please Visit the Cisco Booth in the World of Solutions

See the technology in action
Mobility
MOB1 Collaboration in Motion MOB2 Cisco Unified Wireless Network MOB3 Mobile High-Speed g p Performance with 802.11n
BRKAGG-2012
Cisco Public
93
Complete Your Online Session Evaluation

Give us your feedback and you could win fabulous prizes prizes. Winners announced daily. Receive 20 Passport points for each session evaluation you complete. Complete your session evaluation online now ( (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center.
Dont forget f to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the h year. A Activate i your account at the h Cisco booth in the World of Solutions or visit www.ciscolive.com.
94
BRKAGG-2012
Cisco Public
BRKAGG-2012
Cisco Public
95

Brkagg-2012 0101

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Brkagg-2012 0101

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco Motion: Design and Deployment of Context-Aware Mobility Services

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

Receive Signal Strength Indication (RSSI) Overview

2009 Cisco Systems, Inc. All rights reserved.

Time Difference of Arrival (TDoA) Overview

2009 Cisco Systems, Inc. All rights reserved.

Time Difference of Arrival (TDoA) Overview (continued)

Device Tracking - WCS

Rogue AP: Rogue clients:

2009 Cisco Systems, Inc. All rights reserved.

MSE Software Overview

Will host multiple software services

2009 Cisco Systems, Inc. All rights reserved.

Mobility Service Engine Internal Architecture

Message Bus/Router Reliable Asynchronous Secure Messaging

Network Repository wIPS Client Mgmt Engine

2009 Cisco Systems, Inc. All rights reserved.

Role of MSE - Context Aware

2009 Cisco Systems, Inc. All rights reserved.

Context Aware Software Architecture

Context C t tA Aware Engine for Clients

Context C t tA Aware Engine for Tags

Mobile User Voice over 802.11 Smart Phone

802.11 CCX Tags

Indoor & Outdoor Environments

Cisco Context Aware Mobility Solution

Cisco Wireless Control System (WCS)

Context Aware Software

Chokepoint 125 kHz

Tag g and Dev vices

Required Components Client and Tag Tracking

2009 Cisco Systems, Inc. All rights reserved.

Cisco Wireless Deployment with CAS

Cisco Wireless LAN Controller

AeroScout System Manager and Analyzer

NMSP Network Mobility Services Protocol (port 16113)

2009 Cisco Systems, Inc. All rights reserved.

Historical and Statistics Trending

2009 Cisco Systems, Inc. All rights reserved.

Historical Data Storage

Cisco Extensions (CCX) for Wi Wi-Fi Fi Tags

2009 Cisco Systems, Inc. All rights reserved.

Network for Context Aware: Planning and Setup

2009 Cisco Systems, Inc. All rights reserved.

Use Case Scenarios

HIGH CEILING + Clients + Tags

WLC Client and Tag Tracking Capacity

Client Capabilities 500 500 2 500 2,500 2,500 5,000 10.000

Tag Capabilities 256 256 2 500 2,500 2,500 2,500 5,000

WCSPorts WCS Ports Used

MSEPorts MSE Ports Used

2009 Cisco Systems, Inc. All rights reserved.

RSSIAP RSSI AP Placement Guidelines

2009 Cisco Systems, Inc. All rights reserved.

RSSIGeneral RSSI General Deployment Guidelines

2009 Cisco Systems, Inc. All rights reserved.

Poor AP placement and coverage g for location

Good G d AP placement l t and d coverage for location

2009 Cisco Systems, Inc. All rights reserved.