BRKAGG-2012_0101

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

BRKAGG-2012

© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 1

AbstractAbstract

The Cisco Context Aware Mobility solution (which includes location-based services) is an important advanced service that can be provided with the Cisco unified WLAN network. This session focuses on design gand deployment fundamentals, as well as operational best practices to optimize the performance and accuracy when tracking wireless devices (tags and wirelesswhen tracking wireless devices (tags and wireless clients) using the Cisco Context-Aware Mobility solution.

© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKAGG-2012 2

AgendaAgenda

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


Technology Background


TerminologyTerminology

Mobility Services Engine (MSE): appliance designed as an open platform that supports multiple mobility services as softwareplatform that supports multiple mobility services as software applications

Network Mobility Services Protocol (NMSP): Cisco-defined t l d f i ti b t WLC MSEprotocol used for secure communication between 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 accessRogue clients: all devices that are associated to rogue access points.

Active RFID tags: Wi-Fi device that can be detected and located Wi Fi t k


on Wi-Fi network

Receive Signal Strength Indication (RSSI) Overview(RSSI) Overview

Cisco RSSI-based location tracking solution based on “network-side” RSSI measurements

Requires min. of three AP’s; optimal accuracy requires more than 3 AP’smore than 3 AP s

Best suited for indoor office-like environments (carpeted, low ceiling, i.e. < 20 feet)(carpeted, low ceiling, i.e. 20 feet)

Main factors affecting accuracy:AP densityAP density

AP placement

RF environment


Time Difference of Arrival (TDoA) OverviewOverview

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 f t b i d t diff t iTime for message to be received at different receivers is proportional to length of transmission path between the mobile device and each receiver


Time Difference of Arrival (TDoA) Overview (continued)(continued)

Each TDOA installation must have at least one synchronization source

Depending on the size of the site, may require more than one synchronization sourcey

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 t ll i lti th d hi h iliOperates well in multipath and high-ceiling environments

Possible to achieve high accuracy (3–5m) even in difficult,


g y ( ) ,industrial environments

Device Tracking - WCSDevice Tracking WCS


client: tag:

Rogue AP: Rogue clients:

System Architecture


MSE Software OverviewMSE 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 – unneeded services and users disabled or gshut down (e.g. inetd, ftp, uucp)

Will host multiple software servicesIn software release 5.1, hosting only CAS

In software release 5.2, wIPS and MIR services hosted on MSE


Mobility Service Engine – Internal Architecture

Context AwareEngine for Clients

Context AwareEngine for Tags

Architecture

HTTP/SOAP

SIP Listener

Service Engine Manager

AAA

Reliable Asynchronous Secure MessagingMessage Bus/Router

•Licensing Control •Monitoring•Backup•RestoreDB

Network Repository

NMSPModule

Client MgmtEngine

wIPS

CLICommon


Common Services

Role of MSE - Context AwareRole of MSE Context Aware

Execution of positioning algorithms

Maintenance of calibration information

Triggering and dispatch of location notificationsgg g p

Processing of statistics and historical location


Context Aware Software ArchitectureContext Aware Software ArchitectureBusiness Application

C t t A C t t A

SOAP/XML API MSEContext-Aware

Software

SiSi

SiSi

Context Aware Engine for Clients

Context Aware Engine for Tags

RSSI RSSI / TDOARSSI RSSI / TDOA

Smart Phone

Voice over 802.11

Mobile User

802.11 Clients 802.11 CCX Tags


Indoor EnvironmentIndoor & Outdoor Environments

Cisco Context Aware Mobility SolutionTracking Tags and ClientsTracking Tags and Clients

Tracking tags (indoor and outdoor/outdoor-like)

Applicat

Manage

Cisco Wireless Control System (WCS)

Cisco 3350 Mobility Services Engineoutdoor/outdoor like)

Context-aware engine for tags (partner engine)

Utilizes:

tion and m

ent

SiSi

Context AwareEnginefor Clients

Context Aware Software

Context Aware Enginefor Tags

LWAPP infrastructure for indoor environments

Wi-Fi TDOA receivers for outdoor and outdoor-like environments

Netw

SiSi

Wi-Fi TDOA

Context Aware Software

and outdoor like environments

Partner HW/SW managed by System Manager (partner) and Cisco WCS

Tracking clients (indoor)

workReceiver

Context aware engine for clients (Cisco engine)

Utilizes LWAPP infrastructure

TagD

ev

Chokepoint 125 kHz


Managed by Cisco WCS

g and vices

AeroScout

Required Components – Client and Tag TrackingTracking

Client Tracking Tag Tracking

WCS Cisco WCS PLUS with location

Cisco WCS PLUS with location

MSE License

Client client tracking license with appropriate client count

Client tag tracking license with appropriate client count (TDoA or RSSI)count count (TDoA or RSSI)

Additional None

TDoA location receivers (if and when required)

Components None q )LR license for each TDoA receiver


Cisco Wireless Deployment with CAS

Cisco WCS

LocationClient

Cisco Wireless Deployment with CASWCS Client Browser

Location API via

HTTPS

Cisco Wireless LANCiscoMobility

SOAP/XML over HTTPS

NMSPCisco Wireless LAN

ControllerMobility Services Engine (MSE)

AccessAccess Point AeroScout

System Manager and Analyzer


NMSP – Network Mobility Services Protocol (port 16113)

Analyzer

Historical and Statistics TrendingHistorical and Statistics Trending

MSE records and maintains historical location and statistics information for clients and tagsinformation for clients and tags

Can be viewed via WCS or using 3rd-party location clients

By default 30 days of historical data is stored in the MSEBy default, 30 days of historical data is stored in the MSEMSE will not delete historical data before the 30 day window has been reached

Th t th b f l t t iti i t thThe greater the number of element transitions per minute, 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


Historical Data StorageTransitions Per

MinuteNumber Of Rows In History Table After 1

Days to Hit 10 Million Rows

Historical Data Storage

Minute History Table After 1 Day

Million Rows

100 144,000 69.44200 288 000 34 72200 288,000 34.72300 432,000 23.15400 576,000 17.36500 720,000 13.89600 864,000 11.57700 1 008 000 9 92700 1,008,000 9.92800 1,152,000 8.68900 1,296,000 7.75


, ,1000 1,440,000 7.14

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

partnered with a variety of asset tag vendors to create an extensible specification for 802 11 Wi Fi based active asset tagsextensible specification for 802.11 Wi-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


Network for Context Aware: Planning and SetupPlanning and Setup


Use Case ScenariosUse Case ScenariosINDOOR + 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

WLC – Client and Tag Tracking Capacity

WLC Model Client Capabilities Tag Capabilities

WLC Client and Tag Tracking Capacity

WLCM 500 256

2106/12/25 500 256

Catalyst 3750G with 2 500 2 500Integrated WLC 2,500 2,500

4402 2,500 2,500

4404 5,000 2,500


WiSM 10.000 5,000

WCS—Ports UsedWCS Ports UsedName Port NumberDatabase 1315Database 1315FTP 21TFTP 69HTTP 80HTTPS 443HTTP Connector 8456HTTP Connector 8456

HTTP Connector Redirect 8457

NTP 123RMI 1299Trap 169


Trap 169Web Container 8009

MSE—Ports UsedMSE Ports Used

Name Port Number

NMSP 16113

FTP 21

SSH 22

HTTP 80HTTP 80

HTTPS 443


RSSI—AP Placement GuidelinesRSSI AP Placement Guidelines

Optimal accuracy is normally received with more than 3 AP’s

In quadrilateral area, min. of four AP’s should be installed at the four corners of the area

Factors affecting accuracy: AP placement wall materials largeFactors affecting accuracy: AP placement, wall 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 largedesign/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 environmentsand throughput in high multipath environments

For wireless data only deployments: 10% AP cell overlap

For wireless data + voice deployments: 20% AP cell overlap


For wireless data voice deployments: 20% AP cell overlap

RSSI—General Deployment GuidelinesRSSI 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 areaenclosed area

APs should be distributed evenly, i.e., APs should be relatively equa-distant from each other

Ph i l l t f AP h ld b li h l d tPhysical placement of APs should be non-colinear—even when placed at equal distances from each other

Geometric shapes formed by the distribution of APs affect accuracyEquilateral triangles placement will yield better accuracy than APs that form an obtuse triangle

Square deployment placement yields better results than APs that form rectangles


AP Placement ExamplesAP Placement Examples

Poor AP placement and coverage for location g

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


AP Placement ExamplesAP Placement Examples

Poor AP placement and coverage for location – linear APlocation linear AP placement Wi-Fi

device

Proper AP placement and coverage forand coverage for location – staggered AP placement with perimeter coverage

Wi-Fi device


perimeter coverage

MSE System ConfigurationMSE System Configuration

Use the following command which starts wizard to guide the user in setting the system parametersin 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 configurationRoutes configuration

Console/ssh access settings

Root password changes


WCS user password changes

MSE Start/Status/StopMSE 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 restartRestart command: /etc/init.d/msed restart


“getserverinfo” Commandgetserverinfo Commandroot@MSE ~]# getserverinfo

MSE Platform is up, getting the status

-------------

Services

-------------

Server Config

-------------

Product name: Cisco Mobility Service

-------------

Service Name: Context Aware Service

Service Version: 6.0.42.0

Admin Status: EnabledProduct name: Cisco Mobility Service Engine

Version: 6.0.62.0

Hw Version: V01

Hw Product Identifier: AIR-MSE-3350-K9

Admin Status: Enabled

Operation Status: Up

Service Name: Wireless Intrusion Protection ServiceHw Product Identifier: AIR MSE 3350 K9

Hw Serial Number: MXQ828A4L9

Use HTTP: false

Legacy HTTPS: true

L P t 8001

Protection Service

Service Version: 1.0.1103.0

Admin Status: Enabled

Operation Status: Up

Legacy Port: 8001

Log Modules: 262143

Log Level: INFO

Days to keep events: 2


Session timeout in mins: 30

DB backup in days: 2

“getserverinfo” Commandgetserverinfo Command-------------Context Aware Service-------------

Clients Not Tracked due to the limiting: 481Tags Not Tracked due to the limiting: 0

Total Active Elements(Clients, Rogues, Interferers): 129

Active Clients: 34

Rogues Not Tracked due to the limiting: 1306Interferers Not Tracked due to the limiting: 0Wired Clients Not Tracked due to

Active Tags: 29Active Rogues: 66Active Interferers: 0Active Wired Clients: 0

ed C e ts ot ac ed due tothe limiting: 0Total Elements(Clients, Rogues, Interferers) Not Tracked due to the limiting: 1787------------- # of devices not

Active Elements(Clients, Rogues, Interferers) Limit: 100

Active Tag Limit: 100Active Wired Clients Limit: 0

Context Aware Sub Services-------------Sub Service Name: aeroscoutVersion: 3.2.0 - 4.0.14.13

# of active NMSP sessions

tracked due to licensing

Active Sessions: 1 Description: AeroScout® Location Engine for RSSI and TDOA asset trackingRegistered: trueActive: true# of active

AeroScout engine version


Active: trueWatchdog Process ID: 25579Engine Process ID: 25761

NMSP sessionsengine version info

Finding Detailed Info On Partner EngineFinding Detailed Info On Partner Engine[root@MSE ~]# rpm -qi aeroscout-engine

Name : aeroscout-engine Relocations: (not relocatable)Name : aeroscout engine Relocations: (not relocatable)

Version : 4.0.13 Vendor: AeroScout

Release : 11 Build Date: Mon 06 Oct 2008 07:43:32 AM PDT

Install Date: Tue 25 Nov 2008 05:46:17 PM PST Build Host: talim

G A li ti /S t S RPM t i 4 0 13 11Group : Applications/System Source RPM: aeroscout-engine-4.0.13-11.src.rpm

Size : 249409173 License: Commercial

Signature : (none)

Summary : Build

Description :

AeroScout computation engine

[root@MSE ~]#


Add MSE to WCSAdd MSE to WCS


Change in WCS Menu from “Location/Location Servers” to “Mobility”/“Mobility Service Engine”


“Location Server” (Cisco 2710)

and “Mobility Service Engine” Separate Menu Items for

Adding WIFI TDOA Receivers To MSE/WCSMSE/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 A ( t i )Context Aware (partner engine)

Receivers are configured with IP address and TDOA parameters using Aeroscout System Managerparameters using Aeroscout System Manager


Place Location Sensors Using WCS Map EditorWCS Map Editor


TDOA – Outdoor DeploymentTDOA Outdoor Deployment


Location Optimized Monitor ModeLocation 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 AP’s

Good for periphery of buildings to improve location i h ddi ffi h iaccuracy without adding extra traffic that may impact

voice or client services

Ensure that channels on LOMM AP’s are configured toEnsure that channels on LOMM AP s are configured to be the same as the local mode AP’s

Controller CLI for changing monitor mode channels


Design Criteria - Voice and LocationDesign Criteria Voice and Location

For wireless voice deployments: cell-to-cell overlap = 20%

more stringent than data deployments (10% cell-to-cell overlap)

i + d t d l t i ll l f V WLANvoice + data deployments – may require cell overlap of VoWLAN deployment

Balance AP placement to optimize for voice coverage p p gand location accuracy

For location, 3 AP’s placed in 3 out of 4 quadrants f f fwithin 40–70 ft. of all locations within the convex hull of

AP’s to meet 90%/10m accuracy without detailed calibration


Design Criteria - Voice and Location (Cont)(Cont)

Location Optimized Monitor Mode (LOMM) AP’s: place AP’s evenly spaced on perimeter quadrant based deployment within perimeterspaced on perimeter, quadrant-based deployment within perimeter

Shuffle AP’s to even out perimeter and inside AP’s spacing

Local + LOMM (Location Optimized Monitor Mode): quadrant-( p ) qbased deployment inside coverage area for voice/location coverage plus AP’s evenly placed around the perimeter

Leverage new location deployment tools introduced in location appliance 4.0 software release :

Location optimized monitor modeLocation optimized monitor mode

Site survey and interpolated heat maps

Location accuracy tool


Deploying LOMM AP’sDeploying LOMM AP s

Local mode AP placement and densityL lLOMM LOMM placement and density may be sufficient for data/voice applications

LocalLOMM LOMM

Use LOMM AP’s to fill in coverage gaps

Wi-Fi device

LocalLocal LOMM


Site Survey and CalibrationSite 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

ffLinear calibration: data collected between two different points (straight line)

Requires CCX v2 compatible clientCalibration with non-CCX clients will not be supported from software version 5.0 onwards

Old method of calibration not supported starting with software versionOld method of calibration not supported starting with software version 5.0

Faster calibration process vs. previous calibration mechanism


Calibration – Point ModeCalibration Point Mode

RepresentsRepresents completed calibration area



Calibration dateCalibration date collected for entire floor space



Represents completed calibration area


Point Mode – Calibration ResultsPoint Mode Calibration Results


Calibration – Linear ModeCalibration Linear Mode


Path of calibration data collection

Rails and RegionsRails and Regions

Provides mechanism for defining inclusion/exclusion areas for location serviceslocation 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 specifiedLocation inclusion region: tracked device cannot be outside of this polygon (examples: outside of building outer walls)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 bandRails: tracked device must be within defined area with narrow band. Typically used within exclusion region (examples: conveyor belt).

Regions defined in WCS and “pushed” (via synchronization process to MSE/2710


process to MSE/2710

Rails and Regions – ConfigurationRails and Regions Configuration

Step 1: Create Rails and Regions Using

Step 2: Synchronize (Pass Rails and Regions Points to g g

Map Editorg

Location Appliance)


Example of:p

Inclusion Region

Exclusion Region

Rail(prompt for specifying Exclusion Region around line)

F Addi L ti F Addi L ti F Addi R il


For Adding Location Inclusion Region

For Adding Location Exclusion Region

For Adding Rails

Viewing Regions and Rails on Floor MapViewing Regions and Rails on Floor Map


Location Accuracy ToolLocation Accuracy Tool

Two forms of accuracy testingScheduled accuracy

On-demand accuracy

User can choose either method after selecting the floor to run the accuracy test.

All th t t th flAll these tests on the same floor


Scheduled AccuracyScheduled Accuracy

Run on active environment (live network)

Preposition clients and tags and schedule the test

Uses “actual” location of an element vs. “measured” location

fUser can modify the test by:Adding/deleting elements

Changing positionsChanging positions

Changing the schedules

Test can be run as a scheduled task and generate alarms if falls b l t i fbelow certain range of accuracy

Should be retested periodically as RF environment may change, impacting location accuracy


Scheduled Accuracy TestScheduled Accuracy Test


On-Demand AccuracyOn Demand Accuracy

To be run when a user does not have any active client/tag deployments yet and is interested in measuring accuracydeployments yet and is interested in measuring accuracy

Can be run when a floor does not have prepositioned tags/clients

Conducted similar to pre-5 0 accuracy test with single clientConducted similar to pre 5.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.


Wired LocationWired 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 SwitchesWCS 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 of the wired clients y

MSE provides the APIs to search/track a client across wired and wireless categories

S it h t d C t l t 3750 3750E 3560 3560E 2960


Switches supported - Catalyst 3750, 3750E, 3560, 3560E, 2960

Major InterfacesMajor Interfaces


Switch Side Configuration StepsSwitch 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 modelrespective switch model

3. Enable NMSP

4 E bl IP D i t ki4. Enable IP Device tracking

5. Configure SNMP Community with read-write access

6. Configure Civic/ELIN Location Identifiers

7. Assign identifiers to switch interfaces


WCS Side Configuration StepsWCS Side Configuration Steps

1. Go to Configure >Ethernet Switches

2. Add Ethernet Switches Add IP Address

Enable Location CapableEnable Location Capable

Enter the SNMP Community (read-write)

3. Go to Services > Synchronize Services > SwitchesyClick on Assign to assign to preferred MSE

Select the Switch and Synchronize

4. Go to Services > Mobility Services, and click on MSEGo to System > Status > NMSP Connection status

Check for active NMSP status for each switch


Check for active NMSP status for each switch

Wired Elements Display on WCSWired 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”


Location DataLocation Data

FormatsCIVIC Address (RFC 4776 / RFC 5139)

GEO

CISCO

TrackingCurrent association and location

History of associations and dis-associations

S hiSearchingExtensions to search across wired and wireless categories based on –


MAC Address, IP Address, 802.1x user name

Validation And Improvements Of Context Aware NetworkContext Aware Network


Use Location Readiness ToolUse Location Readiness Tool

Use prior to calibration to gauge AP placementto gauge AP placement and coverage holes

A point on map is l ti d iflocation-ready if:

– min. of 4 AP’s are deployed

– min. of 3 AP’s are within 70 ft

– At least 1 AP placed in each of at least 3 surrounding quadrants.


“Location Ready” PointLocation Ready Point

<= 70’<= 70’

<= 70’


Advanced Location ParametersAdvanced 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 thatAbsolute 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 Default = -75meet or exceed the RSSI cutoff value. Default = -75 dBm


NMSP OverviewNMSP 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

C S S fWLC sends NMSP message to MSE either of these conditions:new client joins

more than 5 dB change in the RSSI valuemore 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


Time Synchronization/ConfigurationTime Synchronization/Configuration

possible symptom of clock discrepancy between WLC and MSE: can’t establish NMSP connection after adding MSE to the system

suggested course of action:Use NTP ser er for s nchroni ing clocks (recommended)Use NTP server for synchronizing clocks (recommended)

Manual configuration (controller time should be ahead of time on MSE)


Establishing NMSP ConnectionEstablishing NMSP Connection

MSEroot@mse ~]# cmdshellroot@mse ~]# cmdshell

cmd> show server-auth-info

invoke command: com.aes.server.cli.CmdGetServerAuthInfo

----------------

Server Auth InfoServer Auth Info

----------------

MAC Address: 00:1e:0b:61:35:60

Key Hash: 5384ed3cedc68eb9c05d36d98b62b06700c707d9

Certificate Type: SSC

MAC address and key hash for authenticating NMSPCertificate Type: SSC

==============================

WLC(Cisco controller) >config auth list add lbs ssc <MSE Ethernet MAC> <MSE key hash>

authenticating NMSP session between MSE and WLC

(Cisco controller) >config auth-list add lbs-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.

Verifying NMSP Connection Status (WLC)(WLC)

(Cisco Controller) >show nmsp status

LocServer IP TxEchoResp RxEchoReq TxData RxData

-------------- ----------- --------- -------- -------

172.20.224.17 18006 18006 163023 10172.20.224.17 18006 18006 163023 10


Verifying NMSP Connection Status (MSE)(MSE)(Cisco Controller) >show auth-list

<snip>

Mac Addr Cert Type Key Hash

----------------------- ---------- ------------------------------------------

00:1e:0b:61:35:60 LBS-SSC 5384ed3cedc68eb9c05d36d98b62b06700c707d9

MSE MAC address MSE key hashy


NMSP Monitoring UINMSP Monitoring UI


If Tag Is Not Seen By WLCIf Tag Is Not Seen By WLC

Tags must be configured to beacon in 3 channels 1,6,11 and with 3 or more repetitionsrepetitions.

Example: 1,6,11, 1,6,11, 1,6,11

Check global RFID config on the controller show rfid configshow rfid config

If the RFID tag detection is not enabled, enable it using the following commandconfig rfid status enable

Verify/set timeout parametersVerify/set timeout parametersconfig rfid timeout 1200

config rfid auto-timeout disable

Check RSSI expiry timeoutCheck RSSI expiry timeoutshow location summary

If tag is still not seen by controller, use following debug commandsdebug mac addr <tag mac addr>


debug mac addr <tag mac addr>

debug rfid receive enable

If Tag Is Seen By WLCIf Tag Is Seen By WLC

Check to see if controller sees the tagshow 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 if the NMSP layer on the controller is sending notificationy y gdebug 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. Defaultsignal strength reports that meet or exceed the RSSI cutoff value. Default = -75 dBm


“show rfid summary” Commandshow rfid summary Command

lists all of the RFID tags reported by AP’s including the following information:RFID MAC addressRFID MAC address

closest AP

RSSI value

time since the tag was last heard

(Cisco Controller) >show rfid summary

Total Number of RFID : 128

<snip>

----------------- -------- ------------------ ------ ---------------------

RFID ID VENDOR Closest AP RSSI Time Since Last Heard

----------------- -------- ------------------ ------ ---------------------

00:04:f1:00:04:ea Wherenet sjc14-42b-ap4 -69 52 seconds ago

00:04:f1:00:04:eb Wherenet sjc14-42b-ap4 -75 27 seconds ago00:04:f1:00:04:eb Wherenet sjc14 42b ap4 75 27 seconds ago

00:0c:cc:5b:fc:54 Aerosct sjc14-31b-ap9 -87 63 seconds ago

00:0c:cc:5b:fe:29 Aerosct sjc14-31b-ap2 -92 22 seconds ago


“show rfid detail” Commandshow rfid 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 R i d 561211Packets Received................................. 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) >


Client Location DebuggingClient Location Debugging

see which AP the client is associated to and the RSSIs seen by the APs show client summaryshow client summary

show client detail <MAC address>

Verify that the RSSI timeouts for client are set to the default valuesshow 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 enabledebug dot11 load balancing enable

Debug notification related issues using the following commandsdebug mac addr <client mac>

debug dot11 locp enable


debug nmsp message tx enable

“show client summary” Commandshow client summary Command(Cisco Controller) >show client summary

Number of Clients................................ 276

<snip>

MAC Address AP Name Status WLAN/Guest-Lan Auth Protocol Port Wired

----------------- ----------------- ------------- -------------- ---- -------- ---------

00:02:8a:ea:55:15 sjc14-12b-ap5 Associated 7 Yes 802.11b 2 No


“show client detail” Commandshow client detail CommandCisco Controller) >show client detail 00:02:8a:ea:55:15

<snip>

Nearby AP Statistics:

TxExcessiveRetries: 0

TxRetries: 0

RtsSuccessCnt: 0

RtsFailCnt 0RtsFailCnt: 0

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) .....................


sjc14-12b-ap6(slot 0) .....................


sjc14-12b-ap3(slot 0) .....................


sjc14-12b-ap5(slot 0) .....................

antenna0: 7217 seconds ago -53 dBm............... antenna1: 7217 seconds ago -48 dBm

sjc14-11b-ap5(slot 0) .....................


j p ( )

antenna0: 7217 seconds ago -79 dBm............... antenna1: 7217 seconds ago -75 dBm

Final Checklist


Deployment ChecklistFollow 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 specifiedand the correct time zone specified.

Specify which controllers should talk to which MSE using the WCS MSE Synchronization page

Check that certificates are exchanged correctly

Check the NMSP connection status on the controllerC ec t e S co ect o status o t e co t o e

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

V if li t d t t d b t llVerify clients are detected by controller

Max calculation time taken into account

For Tags




Verify tags are detected by controller

Max calculation time taken into account

3310 MSE vs. 3350 MSEHardware and Software SpecificationsHardware and Software Specifications

3310 Mobility Services Engine 3350 Mobility Services Engine

(1) Dual-Core Intel Processor 1.8 GHz (2) Quad-Core Intel Xeon Processors 2.33 GHz

4-GB PC2-5300 (4 x 1 GB) 8-GB PC2-5300 (4 x 2 GB)( ) ( )

(2) Fixed 247-GB Serial ATA-150 / SATA-300 MBps

(2) Hot-swapable 137-GB SAS-300 MBps drives

Available with Cisco MSE Software R l 5 2 l t

Available with Cisco MSE Software R l 5 1 l tRelease 5.2.xxx or later. Release 5.1.xxx or later.

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

3310 MSE vs. 3350 MSEService SupportService 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 Context Aware for up to 18,000 tracked devices

Supports Mobile Intelligent Roaming for up to 500 simultaneous registered

devicesDoes not currently support MIR


MSE-3310 Service Support MatrixwIPS and Context AwarewIPS and Context Aware

Y2000 YgTa

gs

1000 Y

ents

/ T

0 YCli

0 1000 2000


wIPS Monitor Mode APswIPS Monitor Mode APs

MSE-3350 Service Support MatrixwIPS and Context AwarewIPS and Context Aware

Y18000 Y12000 Ygag

s

12000 Y6000 Ynt

s / T

a

6000 Y0 Y

Clie

n

0 Y0 1000 2000 3000


wIPS Monitor Mode APswIPS Monitor Mode APs

Co-Existence NotesCo Existence Notes

Coexistence limits are not enforced

Warning messages will be displayed when limits exceeded

Performance will be impactedPerformance will be impacted

“Over the limit” combinations will be non-TAC supported


Cisco WCS – Supported VersionsCisco WCS Supported Versions

WCS Software Version Minimum Release Required

4.2 Unsupported version

5.0 Unsupported version

5 1 MSE 3350: 5.1.xxx or later5.1 MSE 3350: 5.1.xxx or laterMSE 3310: not supported

5.2 5.2.xxx or later


Cisco Wireless LAN Controller (WLC) –Supported VersionsSupported Versions

WLC Software Version Minimum Release Required

4.2 4.2.xxx (xxx>=130) or later

5.0 5.0.xxx (xxx>148) or later

5 1 5 1 l t5.1 5.1.xxx or later

5.2 5.2.xxx or later


Cisco 2710 vs. Cisco MSECisco 2710 vs. Cisco MSEFeature Cisco 2710 Cisco MSE

Supported customer Indoor low-ceiling (RSSI) Indoor low-ceiling (RSSI)ppenvironments

g ( ) g ( )Indoor high-ceiling (TDOA)Outdoor (TDOA)

Supported location technologies

RSSI only RSSITDoAFuture technologiesFuture technologies

Supported location engines

Cisco only CiscoPartner

Max. number of tracked Wi-Fi devices

2,500 MSE 3310: 2,000MSE 3350: 18,000

Number of services Single (location only) Multiple (Context Aware


supportedg ( y) p (

Mobility Solution, wIPS, MIR)

Recommended ReadingRecommended Reading

Cisco

Wi Fi L ti B d S i 4 1 D i G idWi-Fi Location-Based Services 4.1 Design Guide

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 GuidelinesAeroScout Exciter Deployment Guidelines

AeroScout Engine for Cisco Mobility Services Engine

TDOA Deployment Guide

htt // t t


http://support.aeroscout.com

Please Visit the Cisco Booth in theWorld of Solutions

Mobility

World of SolutionsSee the technology in action

MOB1 – Collaboration in Motion

MOB2 – Cisco Unified Wireless Network

MOB3 – Mobile High-Speed Performance g pwith 802.11n


Complete Your Online Session EvaluationSession Evaluation

Give us your feedback and you could win fabulous prizescould win fabulous prizes. Winners announced daily.

Receive 20 Passport points for each session evaluation youeach 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. fthe Convention Center. Don’t forget to activate your

Cisco Live Virtual account for access to all session material, communities, andon-demand and live activities throughout h A i h


the year. Activate your account at the Cisco booth in the World of Solutions or visit www.ciscolive.com.

BRKAGG-2012_0101

Documents

Transcript of BRKAGG-2012_0101