Table Of Contents

Mobility Services

CAS

MIR

wIPS

Adding a Mobility Services Engine to Cisco WCS

Deleting a Mobility Services Engine from the Cisco WCS

Keeping the Mobility Services Engines Synchronized

Synchronizing Cisco WCS and a Mobility Services Engine

Configuring Automatic Database Synchronization and Out of Sync Alerts

Out-of-Sync Alarms

Viewing Synchronization Information

Viewing Mobility Services Engine Synchronization Status

Viewing Synchronization History

Context Aware Planning and Configuring

Mobile Intelligent Roaming Planning and Configuring

wIPS Planning and Configuring

Mobility Services

---

WCS supports only one service (CAS, MIR, or wIPS) at a time. This chapter briefly describes these three services and gives steps for mobility procedures that are common across all services. References are made and links are provided for the Cisco 3300 Series Mobility Services Engine documentation, which describes CAS, MIR, and wIPS configuration and management in detail.

CAS

Context Aware Software (CAS) allows a mobility services engine to simultaneously track thousands of mobile assets and clients by retrieving contextual information such as location, temperature, and availability from Cisco access points.

---

Note You must purchase licenses from Cisco to retrieve contextual information on tags and clients from access points. Licenses for tags and clients are offered independently. For details on tag and client licenses, refer to the Cisco 3350 Mobility Services Engine Release Note at:

http://www.cisco.com/en/US/products/ps9742/tsd_products_support_series_home.html.

---

MIR

MIR allows a mobility services engine to support hand-off voice calls between Cisco Wi-Fi networks and cellular networks. Voice calls must be placed on phones that support dual-mode radios.

wIPS

The Cisco Adaptive Wireless IPS (wIPS) is an advanced approach to wireless threat detection and performance management. Cisco Adaptive wIPS combines network traffic analysis, network device and topology information, signature-based techniques and anomaly detection to deliver highly accurate and complete wireless threat prevention.

---

Note wIPS functionality is not supported for non-root partition users.

---

Adding a Mobility Services Engine to Cisco WCS

To add a Cisco 3300 Series Mobility Services Engine to Cisco WCS, log into WCS and follow these steps:

---

Step 1 Verify that you can ping the mobility service engine that you want to add from Cisco WCS.

Step 2 Click Mobility > Mobility Services to display the Mobility Services window.

Step 3 From the Select a command drop-down menu, select Add Mobility Services Engine and click GO.

Step 4 In the Device Name field, enter a name for the mobility services engine.

Step 5 In the IP Address field, enter the mobility services engine's IP address.

Step 6 (Optional) In the Contact Name field, enter the name of the mobility services engine administrator.

Step 7 In the User Name and Password fields, enter the username and password for the mobility services engine.

The default username and password are both admin.

---

Note If you changed the username and password during the automatic installation script, enter those values here. If you did not change the default passwords, Cisco strongly recommends that you rerun the automatic installation script and change the username and password.

---

Step 8 Click Next. The Select Mobility Service window appears .

Step 9 To enable one service on the mobility services engine, click the circle next to that service.

---

Note A mobility services engine can only be configured to support a single service at a time.

---

Step 10 Click Save.

---

Note After adding a new mobility services engine, you can synchronize network designs (campus, building, and outdoor maps) and event groups on the local mobility services engine with Cisco WCS. You can also choose to synchronize the mobility services engine with a specific controller. You can do this synchronization immediately after adding a new mobility services engine or at a later time. To synchronize the local and Cisco WCS databases, continue to the "Synchronizing Cisco WCS and a Mobility Services Engine" section.

---

---

Deleting a Mobility Services Engine from the Cisco WCS

To delete a mobility services engine from the Cisco WCS database, follow these steps:

---

Step 1 Click Mobility > Mobility Services to display the Mobility Services window.

Step 2 Select the mobility services engine(s) to be deleted by checking the corresponding check box(es).

Step 3 From the Select a command drop-down menu, select Delete Service(s) and click GO.

Step 4 Click OK to confirm that you want to delete the selected mobility services engine from the WCS database.

Step 5 Click Cancel to stop deletion.

---

Keeping the Mobility Services Engines Synchronized

This section describes how to synchronize Cisco WCS and mobility service engines manually and automatically.

After adding a mobility services engine to Cisco WCS, you can synchronize network designs (campus, building, and outdoor maps), event groups, or controller information (name and IP address) with the mobility services engine.

---

Note Be sure to verify software compatibility between the controller, Cisco WCS, and the mobility services engine before synchronizing. Refer to the latest mobility services engine release note at the following link: http://www.cisco.com/en/US/products/ps9742/tsd_products_support_series_home.html.

---

---

Note Communication between the mobility services engine and Cisco WCS and the controller is in universal time code (UTC). Configuring NTP on each system provides devices with the UTC time. The mobility services engine and its associated controllers must be mapped to the same NTP server and the same Cisco WCS server. An NTP server is required to automatically synchronize time between the controller, Cisco WCS, and the mobility services engine.

---

Synchronizing Cisco WCS and a Mobility Services Engine

To synchronize Cisco WCS network designs, a controller, or event groups with the mobility services engine, follow these steps:

---

Note Even though all clients are loaded in the map, the display has a limit of 250 clients per floor to prevent overcrowding. You can do an advanced search of the map to see the items of interest.

---

---

Step 1 Click Mobility > Synchronize Services to display the Mobility Services > Synchronize WCS and MSE(s) window. A three-tabbed window appears.

---

Note The Devices column lists the IP address of the mobility services engine and the active service on that device. Services are noted in parentheses next to the IP address. Services supported are Mobile Intelligent Roaming (M), Context Aware Service (C), and wireless Intrusion Protection Service (W).

---

Step 2 Select the appropriate tab (network designs, controllers, or event groups).

a. To assign a network design to a mobility services engine, click its corresponding Assign link.

---

Note A network design might comprise a large campus with several buildings, each monitored by a different mobility services engine. Therefore, you might need to assign a single network design to multiple mobility service engines.

---

In the Network Designs panel that appears, check the check box of each network design that you want to apply to the mobility services engine. Click OK when the selection is complete.

A red asterisk (*) appears next to the Assign link. To undo assignments, click Reset. To go back to the Synchronize WCS and MSE(s) window without making any changes, click Cancel.

b. To associate a mobility services engine with a controller, click the Assign link for that mobility services engine.

In the Controllers panel that appears, check the check box next to each controller to which you want the mobility services engine associated. Click OK.

---

Note The controller must support the service that is configured on the mobility service engine (as noted in the supported services column). If not, when you click OK, a warning message appears noting that the service is not supported on that controller.

---

---

Note Controller names must be unique for synchronizing with a mobility services engine. If you have two controllers with the same name, only one controller synchronizes.

---

A red asterisk (*) appears next to the Assign link. To undo assignments, click Reset. To go back to the Synchronize WCS and MSE(s) window without making any changes, click Cancel.

c. To assign an event group to a mobility services engine, click its corresponding Assign link.

In the Event Groups panel that appears, check the check box for each event group that you want to assign to the mobility services engine. Click OK.

A red asterisk (*) appears next to the Assign link. To undo assignments, click Reset. To go back to the Synchronize WCS and Server(s) window without making any changes, click Cancel.

Step 3 Click Synchronize to update the mobility services engine database.

When items are synchronized, a green two-arrow icon appears in the Sync. Status column for each synchronized entry.

---

Note To unassign a network design, controller, or event group from a mobility services engine, click the Assign link next to the system. In the panel that appears, uncheck the check box for the corresponding network design, controller, or event group. Click OK. Then, click Synchronize. The name of the removed network design, controller, or event group is replaced with None Assigned.

---

---

Configuring Automatic Database Synchronization and Out of Sync Alerts

Manual synchronization of Cisco WCS and mobility services engine databases is immediate. However, future deployment changes (such as changes to maps and access point positions) can yield incorrect location calculations and asset tracking until resynchronization reoccurs.

To prevent out-of-sync conditions, use Cisco WCS to enable automatic synchronization. This policy ensures that synchronization between Cisco WCS and mobility services engine databases is triggered periodically and any related alarms are cleared.

To configure automatic synchronization, follow these steps:

---

Step 1 Choose Administration > Background Tasks.

The Background Tasks summary window appears (see Figure 12-1).

Figure 12-1 Administration > Background Tasks

Step 2 Check the Mobility Service Synchronization check box. Select Enable Task from the Select a command drop-down menu if not already enabled. Click GO.

Step 3 Click the Mobility Service Synchronization link and the Task > Mobility Service Synchronization window appears.

Step 4 To set the mobility services engine to send out-of-sync alerts, check the Out of Synch Alerts Enabled check box. By default, out-of-sync alarms are enabled.

---

Note Uncheck the Out of Sync Alerts Enabled check box to disable forwarding of out-of-synch alarms.

---

---

Note For a summary of out of sync alerts that are sent, refer to the "Out-of-Sync Alarms" section.

---

Step 5 To enable automatic synchronization, check the Auto Synchronization Enabled check box.

---

Note Automatic synchronization does not apply to network designs, controllers, or event groups that have not yet been assigned to a mobility services engine. However, out-of-sync alarms will still be generated for these unassigned elements. For automatic synchronization to apply to network designs, controllers, or event groups, you need to manually assign them to a mobility services engine.

---

Step 6 Enter the time interval in days and the time of day (xx:yy) that the automatics synchronization is to be performed.

By default, auto-sync is disabled.

Step 7 Click Submit.

You are returned to the Administration > Background Tasks screen and the Mobility Service Synchronization task displays an enabled state.

---

Out-of-Sync Alarms

Out-of-sync alarms are of Minor severity (yellow) and are raised in response to the following conditions:

•Elements have been modified in Cisco WCS (the auto-sync policy will forward these elements)

•Elements have been modified in mobility services engine (the auto-sync policy will retrieve these elements)

•Elements other than controllers exist in the mobility services engine database but not in Cisco WCS (the auto-sync policy will retrieve these elements)

•Elements have not been assigned to any mobility services engine (the auto-sync policy does not apply)

Out-of-sync alarms are cleared when the following occurs:

•Mobility services engine is deleted

---

Note When you delete a mobility services engine, the out-of-sync alarms for that system are also deleted. In addition, if you delete the last available mobility services engine, the alarms for the following event: elements not assigned to any server will also be deleted.

---

•Elements are synchronized manually or automatically

•User manually clears the alarm (although the alarms may reappear in the future when the scheduled task is next executed)

Viewing Synchronization Information

This section describes how to view synchronization status and history.

Viewing Mobility Services Engine Synchronization Status

You can use the Synchronize Servers command in WCS to view the status of network design, controller, and event group synchronization with a mobility services engine.

To view synchronization status, follow these steps:

---

Step 1 Choose Mobility > Synchronize Services.

Step 2 From the Synchronize drop-down menu, select either the Network Designs, Controllers, or Event Groups tab.

In the panel that appears, check the Sync. Status column for the synchronization status. A green two-arrow icon indicates that the mobility services engine is synchronized with the specified network design, controller, or event group. A gray two-arrow icon with a red circle indicates that its corresponding item is not synchronized with a given server.

---

Viewing Synchronization History

You can view the synchronization history for the last 30 days for a mobility services engine. This is especially useful when automatic synchronization is enabled as alarms are automatically cleared. Synchronization history provides a summary of those cleared alarms.

To view synchronization history, follow these steps:

---

Step 1 Choose Mobility > Synchronization History. The Synchronization History window appears.

Step 2 Click the column headers to sort the entries.

In the Synchronization History window, the Sync Direction column indicates whether information is forwarded into the mobility services engine or retrieved by the mobility services engine. The Generated By column indicates whether the synchronization was manual or automatic.

---

Context Aware Planning and Configuring

Context Aware Software (CAS) resides on the mobility services engine. For more information on the CAS service, refer to the Cisco Context Aware Software Configuration Guide.

---

Note Non-Cisco CX tags are not tracked or mapped by Cisco WCS.

---

---

Note Context Aware Software was previously referred to as Cisco location-based services.

---

Chapter 4 of the Cisco Conxtext Aware Software Configuration Guide contains the following information on configuring and viewing system properties on the mobility services engine:

•Configuring general properties

•Modifying NMSP parameters

•Viewing active sessions on a system

•Adding and deleting trap destinations

•Viewing and configuring advanced parameters

Chapter 5 of the Cisco Context Aware Software Configuration Guide contains information on configuring and managing users and groups on the mobility services engine.

Chapter 6 of the Cisco Context Aware Software Configuration Guide contains the following information on event notifications:

•Adding and deleting event groups

•Adding, deleting, and testing event definitions

•Viewing event notification summary

•Notifications cleared

•Notification message formats

Chapter 7 of the Cisco Context Aware Software Configuration Guide contains the following information on the tools and configurations that can be used to enhance the location accuracy of elements (clients, tags, rogue clients, and rogue access points):

•Planning for data, voice, and location deployment

•Creating and applying calibration models

•Inspecting location readiness and quality

•Verifying location accuracy

•Using chokepoints to enhance tag location reporting

•Using WiFi TDOA receiver to enhance tag location reporting

•Using tracking optimized monitor mode to enhance tag location reporting

•Defining inclusion and exclusion regions on a floor

•Defining a rail line on a floor

•Modifying context aware software parameters

Chapter 8 of the Cisco Context Aware Software Configuration Guide contains the following information on how to monitor the mobility services engine by configuring and viewing alarms, events, and logs and how to generate reports on system utilization and element counts:

•Working with alarms

•Working with events

•Working with logs

•Generating reports

•Monitoring clients

•Monitoring tagged assets

•Monitoring chokepoints

•Monitoring WiFi TDOA receivers

Chapter 9 of the Cisco Context Aware Software Configuration Guide contains the following information on backing up and restoring mobility services engine data and updating the mobility services engine software:

•Recovering a lost password

•Recovering a lost root password

•Backing up and restoring mobility services engine data

•Downloading software to mobility services engines

•Configuring the NTP server

•Defragmenting the mobility services engine database

•Rebooting the mobility services engine hardware

•Shutting down the mobility services engine hardware

•Clearing mobility services engine configurations

Mobile Intelligent Roaming Planning and Configuring

The Mobile Intelligent Roaming (MIR) service is supported on the mobility services engine. For more information on the MIR service, refer to the Cisco Mobile Intelligent Roaming Configuration Guide.

Chapter 4 of the Cisco 3300 Series Mobility Services Engine Configuration Guide contains the following information on configuring and viewing system properties on the mobility services engine:

•Configuring general properties

•Modifying NMSP parameters

•Viewing active aessions on a aystem

•Adding and deleting trap destinations

•Viewing and configuring advanced parameters

Chapter 5 of the Cisco 3300 Series Mobility Services Engine Configuration Guide contains information on configuring and managing users and groups on the mobility services engine.

Chapter 6 of the Cisco 3300 Series Mobility Services Engine Configuration Guide contains the following information on event notifications:

•Adding and deleting event groups

•Adding, deleting, and testing event definitions

•Viewing event notification summary

•Notifications cleared

•Notification message formats

Chapter 7 of the Cisco 3300 Series Mobility Services Engine Configuration Guide contains the following information on handing off voice calls between Cisco Wi-Fi networks and cellular networks:

•Prerequisites for Wi-Fi connectivity for dual mode phones

•Adding portal groups

•Configuring handover settings

Chapter 8 of the Cisco 3300 Series Mobility Services Engine Configuration Guide contains the following information on how to monitor the mobility services engine by configuring and viewing alarms, events, and logs and how to generate reports:

•Monitoring DMMS list

•Working with alarms

•Working with events

•Working with logs

•Generating reports

Chapter 9 of the Cisco 3300 Series Mobility Services Engine Configuration Guide contains the following information on how to back up and restore mobility services engine data and then update the mobility services engine software:

•Recovering a lost password

•Recovering a lost root password

•Backing up and restoring mobility services engine data

•Downloading software to mobility services engines

•Configuring the NTP server

•Defragmenting the mobility services engine database

•Rebooting the mobility services engine software

•Shutting down the mobility services engine hardware

•Clearing mobility services engine configurations

wIPS Planning and Configuring

With a fully integrated solution, Cisco can continually monitor wireless traffic on both the wired and wireless networks and can use that network intelligence to analyze attacks from many different sources of information to more accurately pinpoint and proactively prevent attacks versus waiting until damage or exposure has occurred. Refer to Cisco Adaptive Wireless IPS documentation for the following information:

•WCS and wIPS integration overview

•Mobility services engines

•wIPS profiles

•Configuring SSID group list

•Viewing wIPS alarms

•Viewing wIPS events

•Configuring access points and access point templates

•wIPS policy alarm encyclopedia

•WCS security vulnerability assessment

•Rogue management

•Radio resource management