The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides information on prerequisites, system requirements, and enabling the Cisco CMX analytics service.
This chapter contains the following sections:
Follow these guidelines when editing the mse.properties file.
– Network, building, or floors—By default, the analytics takes all the data that is available in the MSE. These three settings allow you to download only a subset. For example, if you have three building B1, B2, and B3 in network N and want to run analytics only on building B1 and building B2, then you need to specify as buildings=N>B1,N>B2.
– max-history—By default, when the analytics becomes active for the first time, it searches for the previous three days data in the MSE history file and tries to fetch data if there is any. If there is more data available in the history file and you want to retrieve, then you must set this to a different value.
If you set the max-history to nnnD, then it retrieves nnn days and if you set to nnnW, then it retrieves nnn weeks.
– Control the size of the database—New parameters max-points and reset-points are added in the mse.properties file to help control the size of the database. Once the database reaches the threshold value of 8 million points, it removes the oldest data to reset the size to 7.9 million points.
Note In order for the CMX analytics to access data from the MSE, you must set the history parameters on the MSE. For more information, see the “Configuring MSE Tracking and History Parameters” section.
Note Depending on your browser and the hardware, images over 2MB may not appear in the 3D environment. In the mse.properties file, set the value of max-dimension. For example, setting max-dimension to 2048 can reduce the resolution of the picture to at most 2048 pixels on the longest side.
– All settings (including the above mentioned information) are documented in the properties file.
Prime Infrastructure comes preinstalled on a physical appliance with various performance characteristics. Prime Infrastructure software runs on either a dedicated Prime Infrastructure appliance or on a VMware server. The software image does not support the installation of any other packages or applications on this dedicated platform. The inherent scalability of Prime Infrastructure allows you to add appliances to a deployment and increase performance and resiliency.
Prime Infrastructure is delivered in two modes, the physical appliance and the virtual appliance. This section contains the following topics:
The physical appliance is a dual Intel 2.40 GHz Xeon E5620 quad core processor, with 16 GB RAM, and four hard drives running in a RAID level 5 configuration. The physical appliance runs the latest 64-bit Red Hat Linux Operating System.
The physical appliance supports up to 15000 Cisco Aironet lightweight access points, 5000 standalone access points, 5000 switches and 1200 Cisco wireless LAN controllers.
Note For expected results with the Prime Infrastructure, you need a high performance physical appliance with built-in redundancy for hard disks, power supplies and internal cooling fans.
Prime Infrastructure is also offered as a virtual appliance to help support lower level deployments. It can be run on a workstation or a server; access points can be distributed unevenly across controllers.
Prime Infrastructure virtual appliance software is distributed as an Open Virtualization Archive (OVA) file. There are three recommended levels of Prime Infrastructure distribution with different resources and numbers of devices supported.
This section contains the following topics:
Note You can deploy the OVA file directly from the vSphere Client; you do not need to extract the archive before performing the deployment.
You can install the Prime Infrastructure virtual appliance using any of the methods available for deploying an OVF supported by the VMware environment. Before you begin, make sure that Prime Infrastructure virtual appliance distribution archive is in a location that is accessible to the computer on which you are running the vSphere Client.
Note For more information about setting up your VMware environment, see the VMware vSphere 4.0 documentation.
Note The free disk space listed is a minimum requirement but might be different for your system depending on the number of backups that are performed.
Note The free disk space listed is a minimum requirement, but several variables (such as backups) impact the disk space.
The following operating systems are supported:
Note Individual operating systems running Prime Infrastructure in VMware must follow the specifications for the size of Prime Infrastructure that you intend to use.
Prime Infrastructure user interface requires Mozilla Firefox 11.0 or 12.0 or Internet Explorer 8 or 9 with the Chrome plug-in releases or Google Chrome 19.0.
Note We strongly advise that you do not enable third-party browser extensions. In Internet Explorer, you can disable third-party browser extensions by choosing Tools > Internet Options and unselecting the Enable third-party browser extensions check box on the Advanced tab.
The client running the browser must have a minimum of 1 GB of RAM and a 2-GHz processor. The client device should not be running any CPU or memory-intensive applications.
Note We recommend a minimum screen resolution of 1280 x 800 pixels.
Before installing Prime Infrastructure, ensure that you have completed the following:
Note See the latest release notes for information on the service packs and patches required for correct operation of Prime Infrastructure.
– HTTP: configurable during install (80 by default)
– HTTPS: configurable during install (443 by default)
– 1522 (for HA configuration between the primary and secondary Prime Infrastructure)
Note Make sure your firewall rules are not restrictive. You can check the current rules on Linux with the built-in iptables -L command.
You must have root privileges to install Prime Infrastructure on a physical appliance.
To reinstall Prime Infrastructure on a physical appliance, follow these steps:
Step 1 Insert the provided Prime Infrastructure software Image DVD. The system boots up and the following console appears:
Step 2 Select option 1 to reinstall Prime Infrastructure software image. The system reboots and the Configure Appliance screen appears.
Step 3 Enter the initial setup parameters and the system reboots again. Remove the DVD and follow the steps to start the Prime Infrastructure server.
This section describes how to deploy the Prime Infrastructure virtual appliance from the VMware vSphere Client using the Deploy OVF Wizard or from the command line. (VMware vSphere Client is a Windows application for managing and configuring the vCenter Server.) This section contains the following topics:
Prime Infrastructure Virtual Image is packaged as an OVA file. An OVA is a collection of items in a single archive. In the VMware vSphere Client, you can use the Deploy OVF Wizard to create a virtual machine, running the Prime Infrastructure virtual appliance application, as described in this section.
Note While the following procedure provides a general guideline on how to deploy the Prime Infrastructure virtual appliance, the exact steps might vary depending on the characteristics of your VMware environment and setup.
To deploy the Prime Infrastructure virtual appliance, for VMware client, follow these steps:
Step 1 From the VMware vSphere Client main menu, choose File > Deploy OVF Template. The Deploy OVF Template Source window appears (see Figure 2-1).
Figure 2-1 Deploy OVF Template Window
Step 2 Choose Deploy from file and choose the OVA file that contains the Prime Infrastructure virtual appliance distribution.
Step 3 Click Next. The OVF Template Details window appears. VMware ESX/ESXi reads the OVA attributes. The details include the product you are installing, the size of the OVA file (download size), and the amount of disk space that needs to be available for the Virtual Machine(VM).
Step 4 Verify the OVF Template details and click Next. The Name and Location window appears (see Figure 2-2).
Figure 2-2 Name and Location Window
Step 5 Either keep the default name for the VM to be deployed in the Name text box or provide a new one and click Next. This name value is used to identify the new virtual machine in the VMware infrastructure; you should use any name that distinguishes this particular VM in your environment. The Host / Cluster window appears (see Figure 2-3).
Figure 2-3 Host/Cluster Window
Step 6 Choose the destination host or HA cluster on which you want to deploy the Prime Infrastructure VM, and click Next. The Resource Pool window appears.
Step 7 If you have more than one resource pool in your target host environment, choose the resource pool to use for the deployment, and click Next. The Ready to Complete window appears.
Step 8 Review the settings shown for your deployment and, if needed, click Back to modify any of the settings shown.
Step 9 Click Finish to complete the deployment. A message notifies you when the installation completes and you can see the Prime Infrastructure virtual appliance in your inventory.
Step 10 Click Close to dismiss the Deployment Completed Successfully dialog box.
This section describes how to deploy Prime Infrastructure virtual appliance from the command line. As an alternative to using the vSphere Client to deploy Prime Infrastructure OVA distribution, you can use the VMware OVF Tool, which is a command-line client.
To deploy an OVA with the VMware OVF Tool, use the ovftool command, which takes the name of the OVA file to be deployed and the target location as arguments, as in the following example:
In this case, the OVA file to be deployed is Prime Infrastructure-VA-X.X.X-large.ova and the target ESX host is my.vmware-host.example.com. For complete documentation on the VMware OVF Tool, see the VMware vSphere 4.0 documentation.
This section describes how to configure the initial settings of Prime Infrastructure virtual appliance.
Note These steps need to be performed only once when you install the Prime Infrastructure virtual appliance the first time.
To configure the basic network and login settings for Prime Infrastructure virtual appliance system, complete these steps. After the steps are completed, Prime Infrastructure virtual appliance is accessible over the network.
Note Once you insert the Prime Infrastructure Image DVD in the physical appliance for reinstallation, you get the same console prompt. Use these steps to reinstall Prime Infrastructure on the physical appliance.
Step 1 At the login prompt, enter the setup command.
Prime Infrastructure configuration script starts. The script takes you through the initial configuration steps for Prime Infrastructure virtual appliance. In the first sequence of steps, configure the network settings.
Step 2 When prompted, type these parameters:
a. The hostname for the virtual appliance.
b. The IP address for the virtual appliance.
c. The IP default subnet mask for the IP address entered.
d. The IP address of the default gateway where you would create the virtual machine.
e. The default DNS domain for the target environment.
f. The IP address or hostname of the primary IP nameserver in the network.
g. At the Add/Edit another nameserver prompt, enter y (yes) to add additional nameservers. Otherwise, press Enter to continue.
h. The NTP server location (or accept the default by pressing Enter). At the Add/Edit secondary NTP server prompt, enter y (yes) to add another NTP server. Otherwise, enter n (no) to continue.
Step 3 Enter the username to access Prime Infrastructure system running on the virtual machine. The default username is admin, but you can change it here.
Step 4 Enter your password. The password must be at least eight characters and must include both lowercase and uppercase letters, with at least one number. This does not include the username. Once you enter the password, the script verifies the network settings you configured. For example, it attempts to reach the default gateway you configured.
After verifying the network settings, the script starts Prime Infrastructure installation processes. This process can take several minutes, during which there is no screen feedback. When finished, the following banner appears on the screen:
Once this banner appears, the configuration starts with database scripts and reboots the server.
Note If you are installing a physical appliance, remove the ISO DVD from the DVD tray.
Step 5 Log in as admin and enter the admin password.
Step 6 Exit the console using the exit command.
This section provides instructions for starting Prime Infrastructure on either a physical or virtual appliance.
To start Prime Infrastructure when it is installed on a physical or virtual appliance, follow these steps:
Step 1 Log into the system as administrator.
Step 2 Using the command-line interface, enter the following command:
To log into Prime Infrastructure user interface through a web browser, follow these steps:
Step 1 Launch Internet Explorer 8 or 9 or Mozilla Firefox 11.0 or 12.0 on a different computer than the one on which you installed and started Prime Infrastructure.
Note When you use Firefox to log in and access Prime Infrastructure for the first time, the Firefox web browser displays a warning stating that the site is untrustable. When Firefox displays this warning, follow the prompts to add a security exception and download the self-signed certificate from Prime Infrastructure server. After you complete this procedure, Firefox accepts Prime Infrastructure server as a trusted site both now and during all future login attempts.
Step 2 In the address line of browser, enter https://ncs-ip-address, where ncs-ip-address is the IP address of the server on which you installed and started Prime Infrastructure. Prime Infrastructure user interface displays the Login page.
Step 3 Enter your username. The default username is root.
Step 4 Enter the root password you created during setup.
Note If any licensing problems occur, a message appears in an alert box. If you have an evaluation license, the number of days until the license expires is shown. You are also alerted to any expired licenses. You have the option to go directly to the licensing page to address these problems.
Step 5 Click Login to log into Prime Infrastructure. Prime Infrastructure user interface is now active and available for use. Prime Infrastructure home page appears. Prime Infrastructure home page enables you to choose the information that you want to see. You can organize the information in user-defined tabs called dashboards. The default view comes with default dashboards and preselected dashlets for each, and you can arrange them as you like. You can predefine what appears on the home page by choosing the monitoring dashlets that are critical for your network. For example, you might want different monitoring dashlets for a mesh network so that you can create a customized mesh dashboard.
Note If the database or Apache web server does not start, check the launchout.txt file in Linux. You see a generic “failed to start database” or “failed to start the Apache web server” message.
Note When an upgrade occurs, the user-defined tabs arranged by the previous user in the previous version are maintained. Therefore, the latest dashlets might not show. Look at the Edit dashboard link to find what new dashlets are added.
The home page provides a summary of the Cisco Unified Network Solution, including coverage areas, the most recently detected rogue access points, access point operational data, reported coverage holes, and client distribution over time.
By default, you should see six dashboards in Prime Infrastructure home page: the General, Client, Security, Mesh, CleanAir, and ContextAware dashboards.
Note When you use Prime Infrastructure for the first time, the network summary pages show that the Controllers, Coverage Areas, Most Recent Rogue APs, Top 5 APs, and Most Recent Coverage Holes databases are empty. It also shows that no client devices are connected to the system. After you configure Prime Infrastructure database with one or more controllers, Prime Infrastructure home page provides updated information.
To exit Prime Infrastructure user interface, close the browser page or click Log Out in the upper-right corner of the page. Exiting an Prime Infrastructure user interface session does not shut down Prime Infrastructure on the server.
When a system administrator stops Prime Infrastructure server during your Prime Infrastructure session, your session ends, and the web browser displays the message: “The page cannot be displayed.” Your session does not reassociate to Prime Infrastructure when the server restarts. You must restart Prime Infrastructure session.
This section contains the following topics:
The License Center allows you to manage Prime Infrastructure, wireless LAN controllers, and MSE licenses. The License Center is available from Prime Infrastructure Administration menu. To view the License Center page, choose Administration > Licenses.
Note Although Prime Infrastructure and MSE licenses can be fully managed from the License Center, WLC licenses can only be viewed. You must use WLC or CLM to manage WLC licenses.
Tip To learn more about Prime Infrastructure License Center, go to Cisco.com to watch a multimedia presentation. Here you can also find the learning modules for a variety of Prime Infrastructure topics. Over future releases, we will add more overview and technical presentations to enhance your learning.
Prime Infrastructure Licenses portion of the License Center page displays the following:
Note AP count includes both associated and unassociated access points. When you are near the AP limit, you can delete any unassociated access points to increase available license capacity. For a demo license, you can click the “If you do not have a Product Authorization Key (PAK), please click here for available licenses” link and choose Wireless Control System Trial License.
Note Autonomous access points are not counted towards the total device count for your license.
Note To obtain a new license for Prime Infrastructure, go to the Product License Registration link
(https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet)
and provide your Product Authorization Key (PAK) and hostname.
Note If you choose Summary > Prime Infrastructure from the left sidebar menu, only Prime Infrastructure license information is displayed.
See the Cisco Wireless Control System Licensing and Ordering Guide at this URL:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd804b4646.html#wp9000156.
It covers selecting the correct SKU, ordering the SKU, installing the software, registering the PAK certificate, and installing the license file on the server.
The Controller Licensing portion of the License Center page provides the following information for both WPLUS and Base licenses:
Note Only 5500 series controllers are included in the count. Prime Infrastructure provides only an inventory view and issues warnings if a license is expiring.
Note Clicking the number in this column is the same as choosing Summary > Controller from the left sidebar menu, except that it is sorted by the feature you select. This page provides a summary of active controllers.
Note For any controllers with a type other than Permanent, the least number of days left to expiration is shown.
– Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by the licensing portal of Cisco and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.
– Evaluation—Licenses are non-node-locked and are valid only for a limited period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license that has the fewest number of days until expiration is shown.
– Extension—Licenses are node-locked and metered. They are issued by licensing portal of Cisco and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.
– Grace Period—Licenses are node-locked and metered. These licenses are issued by the licensing portal of Cisco as part of the permission ticket to rehost a license. They are installed on the device as part of the rehost operation, and you must accept a EULA as part of the rehost operation.
If you need to revoke a license from one controller and install it on another, it is called rehosting. You might want to rehost a license to change the purpose of a controller.
Note The licensing status is updated periodically. To initiate an immediate update, choose Administration > Background Tasks and run the Controller License Status task.
If your network contains various Cisco licensed devices, you might want to consider using the Cisco License Manager (CLM) to manage all of the licenses using a single application. CLM is a secure client/server application that manages Cisco software licenses network wide. You can download the CLM software and access user documentation at this URL: http://www.cisco.com/go/clm. You can either register a PAK certificate with CLM or with the licensing portal found at the following URL: https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet.
If you want to see more details about controller licensing, from the left sidebar menu, choose the Summary > Controller. The License Center page appears. All currently active licenses on the controller are summarized.
All licensed controllers and their information in the bulleted list below are displayed. If you want to change how the controller results are displayed, click Edit View. In the Edit View page, highlight License Status, and click Hide to remove the column from the display.
Above the Controller Summary list is a series of filters that allow you to filter the list by Controller Name, Feature, Type, or Greater Than Percent Used. For example, if you enter 50, the list shows any WLCs that have more than 50% of its licenses used.
Note You can also use the Advanced Search link to sort the list of controllers.
Note For any controllers with a type other than Permanent, the least number of days left to expiration is shown.
– Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by licensing portal of Cisco and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.
– Evaluation—Licenses are non-node-locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license which has the fewest number of days until expiration is shown.
– Extension—Licenses are node-locked and metered. They are issued by licensing portal of Cisco and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.
Note If a license shows as expired, the controller does not stop functioning. Only upon a reboot, the controller with the expired license become inactive.
– Inactive—The license level is being used, but this license is not being used.
– Not In Use—The license level is not being used and this license is not currently recognized.
– Expired In Use—The license is being used, but is expired and will not be used upon next reboot.
– Expired Not In Use—The license has expired and can no longer be used.
There are three types of licenses:
The MSE Licenses portion of the License Center page provides information for each service. See ( Table 2-1 ).
Note ● When a license is deleted, the mobility services engine automatically restarts to load the new license limits.
If you want to see more details about MSE licensing, choose Administration > License Center to access the License Center page and choose Summary > MSE from left sidebar menu. The License Center page appears.
All licensed MSEs are listed in the following columns:
– Permanent—Licenses are node-locked and have no usage period associated with them. They are issued by licensing portal of Cisco and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.
– Evaluation—Licenses are non-node-locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node-locked, their usage is recorded on the device. The number of days remaining on the evaluation license which has the fewest number of days until expiration is shown.
If you choose Files > Prime Infrastructure Files from the left sidebar menu, you can manage Prime Infrastructure licenses. This page displays the following information:
To add a new Prime Infrastructure license file, follow these steps:
Step 1 In the License Center > Files > Prime Infrastructure Files page, click Add.
Step 2 In the Add a License File dialog box, enter or browse to the applicable license file.
Step 3 Once displayed in the License File text box, click Upload.
To delete a Prime Infrastructure license file, follow these steps:
Step 1 In the License Center > Files > Prime Infrastructure Files page, select the check box of Prime Infrastructure license file that you want to delete.
Step 3 Click OK to confirm the deletion.
If you choose Files > Controller Files from the left sidebar menu, you can monitor the controller licenses.
Note Prime Infrastructure does not directly manage controller licenses, rather it simply monitors the licenses. To manage the licenses you can use command-line interface, Web UI, or Cisco License Manager (CLM).
This page displays the following parameters:
For every physical license installed, two license files display in the controller: a feature level license and an ap-count license. For example if you install a “WPlus 500” license on the controller, “wplus” and “wplus-ap-count” features display. There are always two of these features active at any one time that combine to enable the feature level (WPlus or Base) and the AP count.
Note You can have both a WPlus and Base license, but only one can be active at any given time.
– Permanent—Licenses are node locked and have no usage period associated with them. They are issued by Cisco licensing portal and must be installed using management interfaces on the device. Upon installation of these licenses, you have the necessary permissions across different versions.
– Evaluation—Licenses are non-node locked and are valid only for a limited time period. They are used only when no permanent, extension, or grace period licenses exist. Before using an evaluation license, you must accept an End User License Agreement (EULA). Even though they are non-node locked, their usage is recorded on the device. The number of days left displays for the evaluation license with the fewest number of remaining active license days.
– Extension—Licenses are node locked and metered. They are issued by Cisco licensing portal and must be installed using management interfaces on the device. Before using an extension license, you must accept a EULA during installation.
– Grace Period—Licenses are node locked and metered. These licenses are issued by Cisco licensing portal as part of the permission ticket to rehost a license. They are installed on the device as part of the rehost operation, and you must accept a EULA as part of the rehost operation.
Note Types other than Permanent display the number of days left until the license expires. Licenses not currently in use do not have their counts reduced until they become “In Use”.
– In Use—The license level and the license are in use.
– Inactive—The license level is being used, but this license is not being used.
– Not In Use—The license level is not being used and this license is not currently recognized.
– Expired In Use—The license is being used, but is expired and will not be used upon next reboot.
– Expired Not In Use—The license has expired and can no longer be used.
– Count Consumed—The ap-count license is In Use.
Note If you need to filter the list of license files, you can enter a controller name, feature, or type and click Go.
If you choose Files > MSE Files from the left sidebar menu, you can manage the mobility services engine licenses.
To delete a mobility services engine license file, follow these steps:
Step 1 In the License Center > Files > MSE Files page, select the check box of the mobility services engine license file that you want to delete.
Step 3 Click OK to confirm the deletion.
You can add MSE using the Add Mobility Services Engine dialog box in the Mobility Service page. In this dialog box, you can add licensing files, tracking parameters, and assign maps to MSE. If you launch the wizard with an existing MSE for configuration, then the Add MSE option appears as Edit MSE Details. This section contains the following topics:
Note The Prime Infrastructure Release 1.0 recognizes and supports MSE 3355 appropriately.
To add a mobility services engine to the Prime Infrastructure, log into the Prime Infrastructure and follow these steps:
Step 1 Verify that you can ping the mobility services engine.
Step 2 Choose Services > Mobility Services to display the Mobility Services page.
Step 3 From the Select a command drop-down list, choose Add Mobility Services Engine. Click Go.
Step 4 In the Device Name text box, enter a name for the mobility services engine.
Step 5 In the IP Address text box, enter the IP address of the mobility services engine.
Step 6 (Optional) In the Contact Name text box, enter the name of the mobility services engine administrator.
Step 7 In the User Name and Password text boxes, enter the username and password for the mobility services engine.
This refers to the Prime Infrastructure communication username and password created during the setup process.
If you have not specified the username and password during the setup process, use the defaults.
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, we recommend that you rerun the automatic installation script and change the username and password.
Step 8 Select the HTTP check box to allow communication between the mobility services engine and third-party applications. By default, the Prime Infrastructure uses HTTPs to communicate with MSE.
Step 9 Select the Delete synchronized service assignments check box if you want to permanently remove all service assignments from the mobility services engine.
This option is applicable for network designs, wired switches, controllers and event definitions. The existing location history data is retained, however, you must use manual service assignments to perform any future location calculations.
Step 10 Click Next. The Prime Infrastructure automatically synchronizes the selected elements with the MSE.
After the synchronization, the MSE License Summary page appears. You can use the MSE License Summary page to install a license, add a license, remove a license, install an activation license, and install service license.The Select Mobility Service page appears.
Note After adding a new mobility services engine, you can synchronize network designs (campus, building, and outdoor maps), controllers, switches (Catalyst Series 3000 only), and event groups on the local mobility services engine using the Prime Infrastructure. You can perform this synchronization immediately after adding a new mobility services engine or at a later time. To synchronize the local and the Prime Infrastructure databases, see the Information About Synchronizing the Prime Infrastructure and Mobility Services Engines.
Enabling Services on the Mobility Services Engine
Step 11 After adding the license file, the Select Mobility Service page appears.
Step 12 To enable a service on the mobility services engine, select the check box next to the service. The different type of services are as follows:
Note It is recommended not to have wIPS and CMX Analytics service running on the same MSE.
Step 13 Click Next to configure the tracking and history parameters.
Configuring MSE Tracking and History Parameters
Step 14 After you enable services on the mobility services engine, the Select Tracking & History Parameters page appears.
Note If you skip configuring the tracking parameters, the default values are selected.
Step 15 You can select the clients that you want to keep track of by selecting the corresponding Tracking check box(es). The various tracking parameters are as follows:
Note You must select Wireless Clients for CMX analytics.
Step 16 You can enable the history tracking of devices by selecting the corresponding devices check box(es). The different history parameters are as follows:
Step 17 Click Next to Assign Maps to the MSE.
Note The Assigning Maps page is available only if you select CAS as one of the services to be enabled on the MSE.
Step 18 Once you configure MSE tracking and history parameters, the Assigning Maps page appears.
The Assign Maps page shows the following information:
Step 19 You can see the required map type by selecting All, Campus, Building, Floor Area, or Outdoor Area from the Filter option available on the page.
Step 20 To synchronize a map, select the Name check box and click Synchronize.
Upon synchronization of the network designs, the appropriate controllers that have APs assigned on a particular network design are synchronized with the MSE automatically. Click Done to save the MSE settings.
This section describes how to synchronize the Prime Infrastructure and mobility services engines manually and automatically.
Note The Services > Synchronize Services page is available only in the virtual domain in Release 7.3.101.0.
After adding a mobility services engine to the Prime Infrastructure, you can synchronize network designs (campus, building, floor, and outdoor maps), controllers (name and IP address), specific Catalyst 3000 series and 4000 series switches, and event groups with the mobility services engine.
– The mobility services engine can be synchronized with Catalyst stackable switches (3750, 3750-E, 3560, 2960, IE-3000 switches), switch blades (3110, 3120, 3130, 3040, 3030, 3020), and switch ports.
– The mobility services engine can also be synchronized with the following Catalyst 4000 series switches: WS-C4948, WS-C4948-10GE, ME-4924-10GE, WS-4928-10GE, WS-C4900M, WS-X4515, WS-X4516, WS-X4013+, WS-X4013+TS, WS-X4516-10GE, WS-X4013+10GE, WS-X45-SUP6-E, and WS-X45-SUP6-LE.
http://www.cisco.com/en/US/products/ps9742/tsd_products_support_series_home.html
When you synchronize elements with MSE, there might be event groups on the MSE that have been created by third-party applications. You can either delete the unused elements or mark them as third-party elements.
This section contains the following topic:
Deleting Elements or Marking Them as Third-Party Elements
To delete elements or mark them as third-party elements, follow these steps:
Step 1 Choose Services > Synchronize Services.
The Network Designs page appears.
Step 2 In the Network Designs page, choose Third Party Elements from the left sidebar menu.
The Third Party Elements page appears.
Step 3 Select one or more elements.
Step 4 Click one of the following buttons:
This section describes how to synchronize a controller, assign an MSE to any wireless controller and also to unassign a network design, controller, wired switch, or event group from a mobility services engine. This section contains the following topics:
To synchronize network designs, a controller, a Catalyst switch, or event group with the mobility services engine, follow these steps:
Step 1 Choose Services > Synchronize Services.
The left sidebar menu contains the following options: Network Designs, Controllers, Event Groups, Wired Switches, Third Party Elements, and Service Advertisements.
Step 2 From the left sidebar menu, choose the appropriate menu options.
Step 3 To assign a network design to a mobility services engine, in the Synchronize Services page, choose Network Designs from the left sidebar menu.
The Network Designs page appears.
Step 4 Select all the maps to be synchronized with the mobility services engine by selecting the corresponding Name check box.
Note Through Release 6.0, you can assign only up to a campus level to a mobility services engine. Starting with Release 7.0 this option is granular to a floor level. For example, you can choose to assign floor1 to MSE 1, floor2 to MSE 2, and floor3 to MSE 3.
Step 5 Click Change MSE Assignment.
Step 6 Select the mobility services engine to which the maps are to be synchronized.
Step 7 Click either of the following in the MSE Assignment dialog box:
“To be assigned - Please synchronize.”
You can also click Reset to undo the mobility services engine assignments.
Note A network design may include a floor in a campus or a large campus with several buildings, each monitored by a different mobility services engine. Because of this, you may need to assign a single network design to multiple mobility services engines.
Note Network design assignments also automatically picks up the corresponding controller for synchronization.
Step 8 Click Synchronize to update the mobility services engine(s) database(s).
When items are synchronized, a green two-arrow icon appears in the Sync. Status column for each synchronized entry.
You can use the same procedure to assign wired switches or event groups to a mobility services engine. To assign a controller to a mobility services engine, see “Synchronizing Controllers with a Mobility Services Engine” section for more information.
To assign a mobility services engine with any wireless controller on a per-service basis (CAS or wIPS), follow these steps:
Step 1 Choose Services > Synchronize Services.
Step 2 In the Network Designs page, choose Controller from the left sidebar menu.
Step 3 Select the controllers to be assigned to the mobility services engine by selecting the corresponding Name check box.
Step 4 Click Change MSE Assignment.
Step 5 Choose the mobility services engine to which the controllers must be synchronized.
Step 6 Click either of the following in the Choose MSEs dialog box:
“To be assigned - Please synchronize.”
You can also click Reset to undo the mobility services engine assignments.
Step 7 Click Synchronize to complete the synchronization process.
Step 8 Verify that the mobility services engine is communicating with each of the controllers for only the chosen service. This can be done by clicking the NMSP status link in the status page.
Note After Synchronizing a controller, verify that the timezone is set on the associated 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 is synchronized.
You can use the same procedure to assign Catalyst switches or event groups to a mobility services engine.
Note A switch can only be synchronized with one mobility services engine. However, a mobility services engine can have many switches attached to it.
To unassign a network design, controller, wired switch, or event group from a mobility services engine, follow these steps:
Step 1 Choose Services > Synchronize Services.
Step 2 From the left sidebar menu, choose the appropriate menu options.
Step 3 Select one or more elements by selecting the Name check box, and click Change MSE Assignment. The Choose MSEs dialog box appears.
Step 4 Unselect the mobility services engine if you do not want the elements to be associated with that mobility services engine by selecting either the CAS or wIPS check box.
Step 5 Click Save to save the assignment changes.
The Sync Status column appears blank.
Manual synchronization of the Prime Infrastructure 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.
To prevent out-of-sync conditions, use the Prime Infrastructure to carry out synchronization. This policy ensures that synchronization between the Prime Infrastructure and mobility services engine databases is triggered periodically and any related alarms are cleared.
Any change to one or more of any synchronized component is automatically synchronized with the mobility services engine. For example, if a floor with access points is synchronized with a particular mobility services engine and then one access point is moved to a new location on the same floor or another floor that is also synchronized with the mobility services engine, then the changed location of the access point is automatically communicated.
To further ensure that the Prime Infrastructure and MSE are in sync, smart synchronization happens in the background.
This section contains the following topics:
To configure smart synchronization, follow these steps:
Step 1 Choose Administration >Background Tasks.
Step 2 Select the Mobility Service Synchronization check box.
The Mobility Services Synchronization page appears.
Step 3 To set the mobility services engine to send out-of-sync alerts, select the Out of Sync Alerts Enabled check box.
Step 4 To enable smart synchronization, select the Smart Synchronization Enabled check box.
Note Smart synchronization does not apply to elements (network designs, controllers, or event groups) that have not yet been assigned to a mobility services engine. However, out-of-sync alarms are still generated for these unassigned elements. For smart synchronization to apply to these elements, you must manually assign them to a mobility services engine.
Note When a mobility services engine is added to an Prime Infrastructure, the data in the Prime Infrastructure is always treated as the primary copy that is synchronized with the mobility services engine. All synchronized network designs, controllers, event groups and wired switches that are present in the mobility services engine and not in the Prime Infrastructure are removed automatically from mobility services engine.
Step 5 Enter the time interval, in minutes, that the smart synchronization is to be performed.
By default, the smart-sync is enabled.
For Smart controller assignment and selection scenarios, see the “Smart Controller Assignment and Selection Scenarios” section.
If a floor having at least one access point from a controller is chosen to be synchronized with the mobility services engine in the Network Designs menu of the Synchronize Services page, then the controller to which that access point is connected is automatically selected to be assigned to the mobility services engine for CAS service.
When at least one access point from a controller is placed on a floor that is synchronized with the mobility services engine, the controller to which the access point is connected is automatically assigned to the same mobility services engine for the CAS service.
An access point is added to a floor and assigned to a mobility services engine. If that access point is moved from controller A to controller B, then controller B is automatically synchronized to the mobility services engine.
If all access points placed on a floor that is synchronized to the MSE are deleted, then that controller is automatically removed from the mobility services engine assignment or unsynchronized.
Out-of-sync alarms are of the minor severity (yellow), and are raised in response to the following conditions:
Out-of-sync alarms are cleared when the following occurs:
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 alarm for the following event: “elements not assigned to any server” is deleted.
You can use the Synchronize Services feature in the Prime Infrastructure to view the status of network design, controller, switch, and event group synchronization with a mobility services engine.
This section contains the following topics:
To view the synchronization status, follow these steps:
Step 1 Choose Services > Synchronize Services.
Step 2 From the left sidebar menu, choose Network Designs, Controllers, Event Groups, Wired Switches, Third Party Elements, or Service Advertisements.
For each of the elements, the Sync. Status column shows the synchronization status. A green two-arrow icon indicates that its corresponding element is synchronized with the specified server such as a mobility services engine. A gray two-arrow icon with a red circle indicates that its corresponding item is not synchronized with a provided server.
The Message column shows the reason for failure if the elements are out of sync.
You can also view the synchronization status at Monitor > Site Maps > System Campus > Building > Floor.
where Building is the building within the campus and Floor is a specific floor in that campus building.
The MSE Assignment option on the left sidebar menu shows which mobility services engine the floor is currently assigned to. You can also change the mobility services engine assignment in this page.
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 choose Services > Synchronization History. The Synchronization History page appears. Click the column headings to sort the entries.
Table 2-2 describes the table column headings that appear in the Synchronization History page.
|
|
---|---|
The date and time at which the synchronization has happened. |
|
The status of the synchronization. It can be either Success or Failed. |
|
To delete an MSE license file, follow these steps:
Step 1 Choose Services > Mobility Service Engine.
The Mobility Services page appears.
Step 2 Click Device Name to delete a license file for a particular service.
Step 3 From the Select a command drop-down list, choose Edit Configuration.
The Edit Mobility Services Engine dialog box appears.
Step 4 Click Next in the Edit Mobility Services Engine dialog box.
The MSE License Summary page appears.
Step 5 Choose the MSE license file that you want to delete in the MSE License Summary page.
Step 7 Click OK to confirm the deletion or Cancel to close this page without deleting the license.
Step 8 Click Next to enable services on the mobility services engine.
To delete one or more mobility services engines from the Prime Infrastructure database, follow these steps:
Note The Services > Mobility Services Engine page is available only in the virtual domain in Release 7.3.
Step 1 Choose Services > Mobility Services.
The Mobility Services page appears.
Step 2 Select the mobility services engine to be deleted by selecting the corresponding Device Name check box(es).
Step 3 From the Select a command drop-down list, choose Delete Service(s). Click Go.
Step 4 Click OK to confirm that you want to delete the selected mobility services engine from the Prime Infrastructure database.
Step 5 Click Cancel to stop deletion.
To view clients and users in the Prime Infrastructure UI, follow these steps:
Step 1 Choose Monitor > Clients and Users to view both wired and wireless clients information. The Clients and Users page appears.
The Clients and Users table displays a few columns by default. If you want display the additional columns that are available, click , and then click Columns. The available columns appear. Select the columns that you want to show in the Clients and Users table. When you click anywhere in a row, the row is selected and the client details are shown.
The following columns are available in the Clients and Users table:
The IP address that appears in the IP Address column is determined by a predefined priority order. The first IP address available in the following order appears in the IP address field:
– IPv6 unique global address. If there are multiple addresses of this type, most recent IPv6 address the client received are shown, because a user can have two global IPv6 addresses but one might be from an older router advertisement that is being aged out.
– IPv6 unique local address. If there are multiple IPv6 unique local addresses, the most recent one is used.
– IPv6 link-local address. The IPv6 clients always have at least one link-local address.
The following are the different IPv6 address types:
– Link-local Unicast—The link-local addresses are designed to be used for addressing on a single link for purposes such as auto-address configuration, neighbor discovery, or when no routers are present.
– Site-local Unicast—The site-local addresses are designed to be used for addressing inside of a site without the need for a global prefix.
– Global Unicast—The global unicast address uniquely identifies the client in the global network and is equivalent to a public IPv4 address. A client can have multiple global unicast addresses.
Note When there is more than one IP address of the same type, only the most recent IP address of that type appears, and the rest appear in the QuickView page when you hover your mouse cursor over the QuickView (+) icon.
– Unknown—Indicates that the state of the client cannot be determined.
– Activated—Indicates that the client is ready to establish a tunnel.
– Tunneled—Indicates that a bidirectional tunnel is established.
– Indicates a lightweight client
– Indicates an autonomous client
– Idle—Normal operation; no rejections of client association requests.
– Auth Pending—Completing a AAA transaction.
– Authenticated—802.11 authentication complete.
– Associated—802.11 association complete. This is also used by wired clients to represent that a client is currently connected to the network.
– Power Save—Client is in power save mode.
– Disassociated—802.11 disassociation complete. This is also used by wired clients to represent that a client is currently not on the network.
– To Be Deleted—The client that is deleted after disassociation.
– Excluded—Automatically disabled by the system due to perceived security threat.
Step 2 Select a client or user. The following information appears:
Note Client Statistics shows statistical information after the client details are shown.
This section describes how to add floor plans to either a campus building or a standalone building in the Prime Infrastructure database.
This section contains the following topics:
After you add a building to a campus map, you can add individual floor plan and basement maps to the building.
Note Use the zoom controls at the top of the campus image to enlarge or decrease the size of the map view and to hide or show the map grid (which shows the map size in feet or meters).
To add a floor area to a campus building, follow these steps:
Step 1 Save your floor plan maps in.PNG,.JPG,,JPEG, or.GIF format.
Note For CMX analytics, it is recommended that the size of image file is maximum of 500k. Loading large images into the 3D version of CMX analytics causes certain browsers to show black images. The mse.properties file can also be configured to automatically compress the image.
Note If there are problems converting the auto-cad file, an error message is displayed. The Prime Infrastructure uses a native image conversion library to convert auto-cad files into raster formats like.png. If the native library cannot be loaded, the Prime Infrastructure shows an “unable to convert the auto-cad file” message. If you receive this error, make sure all the required dependencies are met for the native library. To find any dependency problems, use ldd on Linux platforms. The following DLLs must be present under the /webnms/rfdlls Prime Infrastructure installation directory: LIBGFL254.DLL, MFC71.DLL, MSVCR71.DLL, and MSVCP71.DLL. If dependency problems occurs, you have to install the required libraries and restart Prime Infrastructure.
Note The floor map image is enhanced for zooming and panning. The floor image is not visible completely until this operation is complete. You can zoom in and out to view the complete map image. For example, if you have a high resolution image (near 181 megapixels) whose size is approximately 60 megabytes, it may take two minutes to appear on the map.
Step 2 Choose Monitor > Site Maps.
Step 3 From the Maps Tree View or the Monitor > Site Maps list, choose the applicable campus building to open the Building View page.
Step 4 Hover your mouse cursor over the name within an existing building rectangle to highlight it.
Note You can also access the building from the Campus View page. In the Campus View page, click the building name to open the Building View page.
Step 5 From the Select a command drop-down list, choose New Floor Area.
Step 6 Click Go. The New Floor Area page appears.
Step 7 In the New Floor Area page, follow these steps to add floors to a building in which to organize related floor plan maps:
a. Enter the floor area and contact names.
b. Choose the floor or basement number from the Floor drop-down list.
c. Choose the floor or basement type (RF Model).
d. Enter the floor-to-floor height in feet.
Note To change the unit of measurement (feet or meters), choose Monitor > Site Maps, and choose Properties from the Select a command drop-down list.
e. Select the Image or CAD File check box.
f. Browse to and choose the desired floor or basement image or CAD filename, and click Open.
Note If you are importing a CAD file, use the Convert CAD File drop-down list to determine the image file for conversion.
Tip It is not recommended to use a.JPEG (.JPG) format for an auto-cad conversion. Unless a JPEG is specifically required, use.PNG or.GIF format for higher quality images.
g. Click Next. At this point, if a CAD file was specified, a default image preview is generated and loaded.
Note The Prime Infrastructure uses a native image conversion library to convert auto-cad files into raster formats like.PNG. When there are issues loading the native library, Prime Infrastructure shows the following error: “Unable to convert the auto-cad file. Reason: Error while loading the auto-cad image conversion library.” For more information see Prime Infrastructure online help or Prime Infrastructure documentation.
The names of the CAD file layers are listed with check boxes to the right side of the image indicating which are enabled.
Note When you choose the floor or basement image filename, the Prime Infrastructure shows the image in the building-sized grid.
Note The maps can be of any size because the Prime Infrastructure automatically resizes the maps to fit the workspace.
Note The map must be saved in.PNG,.JPG,.JPEG, or.GIF format.
h. If you have CAD file layers, you can select or deselect as many as you want and click Preview to view an updated image. Click Next when you are ready to proceed with the selected layers.
Enter the remaining parameters for the floor area.
i. Either leave the Maintain Aspect Ratio check box selected to preserve the original image aspect ratio or unselect the check box to change the image aspect ratio.
j. Enter an approximate floor or basement horizontal and vertical span (width and depth on the map) in feet.
Note The horizontal and vertical spans should be smaller than or the same size as the building horizontal and vertical spans in the Prime Infrastructure database.
k. If applicable, enter the horizontal position (distance from the corner of the outdoor area rectangle to the left edge of the campus map) and vertical position (distance from the corner of the outdoor area rectangle to the top edge of the campus map) in feet or meters.
Tip Use Ctrl-click to resize the image within the building-sized grid.
l. If desired, select the Launch Map Editor after floor creation check box to rescale the floor and draw walls.
m. Click OK to save this floor plan to the database. The floor is added to the Maps Tree View and the Design > Site Maps list.
Note Use different floor names in each building. If you are adding more than one building to the campus map, do not use a floor name that exists in another building. This overlap causes incorrect mapping information between a floor and a building.
Step 8 Click any of the floor or basement images to view the floor plan or basement map.
Note You can zoom in or out to view the map at different sizes and you can add access points.
After you have added a standalone building to the Prime Infrastructure database, you can add individual floor plan maps to the building.
To add floor plans to a standalone building, follow these steps:
Step 1 Save your floor plan maps in.PNG,.JPG, or.GIF format.
Note The maps can be of any size because the Prime Infrastructure automatically resizes the maps to fit the workspace.
Step 2 Browse to and import the floor plan maps from anywhere in your file system. You can import CAD files in DXF or DWG formats or any of the formats you created in Step 1.
Note If there are problems converting the auto-cad file, an error message is displayed. the Prime Infrastructure uses a native image conversion library to convert auto-cad files into raster formats like.PNG. If the native library cannot be loaded, the Prime Infrastructure shows an “unable to convert the auto-cad file” message. If you receive this error, make sure all the required dependencies are met for the native library. To find any dependency problems, use ldd on Linux platforms. The following DLLs must be present under the /webnms/rfdlls the Prime Infrastructure installation directory: LIBGFL254.DLL, MFC71.DLL, MSVCR71.DLL, and MSVCP71.DLL. If dependency problems occurs, you must install the required libraries and restart the Prime Infrastructure.
Step 3 Choose Monitor > Site Maps.
Step 4 From the Maps Tree View or the Design > Site Maps left sidebar menu, choose the desired building to display the Building View page.
Step 5 From the Select a command drop-down list, choose New Floor Area.
Step 7 In the New Floor Area page, add the following information:
Note If you are importing a CAD file, use the Convert CAD File drop-down list to determine the image file for conversion.
Tip A.JPEG (.JPG) format is not recommended for an auto-cad conversion. Unless a.JPEG is specifically required, use a.PNG or.GIF format for higher quality images.
Step 8 Click Next. At this point, if a CAD file was specified, a default image preview is generated and loaded.
Note The Prime Infrastructure uses a native image conversion library to convert auto-cad files into raster formats like.PNG. When there are issues loading the native library, the Prime Infrastructure shows the following error: “Unable to convert the auto-cad file. Reason: Error while loading the auto-cad image conversion library. For more information, see the Prime Infrastructure online help or the Prime Infrastructure documentation”.
The names of the CAD file layers are listed with check boxes to the right side of the image indicating which are enabled.
Note When you choose the floor or basement image filename, the Prime Infrastructure shows the image in the building-sized grid.
Note The maps can be any size because the Prime Infrastructure automatically resizes the maps to fit the workspace.
Note The map must be saved in.PNG,.JPG,.JPEG, or.GIF format.
If you have CAD file layers, you can select or deselect as many as you want and click Preview to view an updated image. Click Next when you are ready to proceed with the selected layers.
Step 9 Enter the remaining parameters for the floor area.
Note The horizontal and vertical spans should be smaller than or the same size as the building horizontal and vertical spans in the Prime Infrastructure Prime Infrastructure database.
Tip Use Ctrl-click to resize the image within the building-sized grid.
Step 10 Click OK to save this floor plan to the database. The floor is added to the Maps Tree View and the Design > Site Maps list.
Step 11 Click any of the floor or basement images to view the floor plan or basement map.
You can zoom in or out to view the map at different sizes and you can add access points.
To draw a coverage area using the Prime Infrastructure UI, follow these steps:
Note You must add floor plan before drawing a coverage area.
Step 1 Add the floor plan if it is not already represented in the Prime Infrastructure.
Step 2 Choose Monitor > Site Maps.
Step 3 Click the Map Name that corresponds to the outdoor area, campus, building, or floor you want to edit.
Step 4 From the Select a command drop-down list, choose Map Editor, and click Go.
Step 5 It the Map Editor page, click the Draw Coverage Area icon on the toolbar.
Step 6 Enter the name of the area that you are defining. Click OK.
Step 7 Move the drawing tool to the area you want to outline.
The outlined area must be a closed object to appear highlighted on the map.
Step 8 Click the disk icon on the toolbar to save the newly drawn area.
The MSE provides physical location of wired clients, wired endpoints, switches, controllers, and access points present in a wireless network deployment. Currently, MSE provides location information in geo-location format to the external entities through northbound and southbound entities.
To improve the accuracy of the geo-location information provided by MSE, this feature aims to transform the geometric location co-ordinates of a device to geo-location coordinates (latitude and longitude) and provides it to the external entities through northbound and southbound interfaces.
Note At least three GPS markers are required for geo-location calculation. The maximum number of GPS markers that you can add is 20.
Note For CMX Analytics, the 2D OpenStreetMaps requires all points to be geo-located as latitude/longitude in order for the results to be displayed in the correct geographical location.
This section contains the following topics:
To add a GPS marker to a floor map, follow these steps:
Step 1 Choose Monitor > Site Maps to display the Maps page.
Step 2 Choose Campus Name > Building Name > Floor Name.
Step 3 Choose the Add/Edit GPS Markers Information menu option on the top left menu to open the Add/Edit GPS page.
A GPS Marker icon appears on the top left corner of the map (X=0 Y=0).
Step 4 You can drag the GPS Marker icon and place it in the desired location on the map or enter the X and Y position values in the GPS Marker Details table on the left sidebar menu to move the marker to the desired position.
Note If the markers added are too close, then the accuracy of geo-location information is less.
Step 5 Enter the Latitude and Longitude degrees for the selected GPS Marker icon in the left sidebar menu.
The GPS Marker information is saved to the database.
Step 7 Click Apply to other Floors of Building to copy GPS markers on one floor of a building to all the remaining floors of that building.
Note The GPS marker information is required by the CMX analytics to show results for the building in the 2D Open Street Maps view. A warning message is displayed if these GPS markers are not set. The latitude or longitude of the GPS markers can often be obtained through some of the mapping software such as Google maps or Open Street Maps.
To edit a GPS marker present on the floor, follow these steps:
Step 1 Choose Monitor > Site Maps to display the Maps page.
Step 2 Choose the Campus Name > Building Name > Floor Name.
Step 3 Choose the Add/Edit GPS Markers Information menu option on the top left menu to open the Add/Edit GPS page.
Step 4 Select an existing GPS marker present on the floor.
Step 5 From the left sidebar menu, you can change the Latitude, Longitude, X Position, and Y Position which is associated with the GPS marker.
The modified GPS marker information is now saved to the database.
To delete a GPS marker present on a floor, follow these steps:
Step 1 Choose Monitor > Site Maps to display the Maps page.
Step 2 Choose Campus Name > Building Name > Floor Name.
Step 3 Choose the Add/Edit GPS Markers Information menu option to open the Add/Edit GPS page.
Step 4 Select an existing GPS Marker which is present on the floor from the left sidebar menu.
Note You can delete multiple GPS markers present on a floor by selecting the Multiple GPS Markers check box.
Step 5 Click Delete GPS Marker.
Step 6 The selected GPS marker is deleted from the database.
This section contains the following topics:
To define an inclusion area, follow these steps:
Step 1 Choose Monitor > Site Maps.
Step 2 Click the name of the appropriate floor area.
Step 3 From the Select a command drop-down list, choose Map Editor.
Step 5 At the map, click the aqua box on the toolbar.
Note A message box appears reminding you that only one inclusion area can be defined at a time. Defining a new inclusion region automatically removes the previously defined inclusion region. By default, an inclusion region is defined for each floor when it is added to Prime Infrastructure. The inclusion region is indicated by a solid aqua line and generally outlines the region.
Step 6 Click OK in the message box that appears. A drawing icon appears to outline the inclusion area.
Step 7 To begin defining the inclusion area, move the drawing icon to a starting point on the map and click once.
Step 8 Move the cursor along the boundary of the area you want to include and click to end a border line. Click again to define the next boundary line.
Step 9 Repeat Step 8 until the area is outlined and then double-click the drawing icon. A solid aqua line defines the inclusion area.
Step 10 Choose Save from the Command menu or click the disk icon on the toolbar to save the inclusion region.
Note If you made an error in defining the inclusion area, click the area. The selected area is outlined by a dashed aqua line. Next, click the X icon on the toolbar. The area is removed from the floor map.
Step 11 Select the Location Regions check box if it is not already selected. If you want it to apply to all floor maps, click Save settings. Close the Layers configuration page.
Step 12 To resynchronize Prime Infrastructure and MSE databases, choose Services > Synchronize Services.
Note If the two DBs are already synchronized then a resynchronization happens automatically every time there is a change. There is no need for an explicit resynch.
Step 13 In the Synchronize page, choose Network Designs from the Synchronize drop-down list and then click Synchronize.
You can confirm that the synchronization is successful by viewing two green arrows in the Sync. Status column.
Note Newly defined inclusion and exclusion regions appear on heatmaps only after the mobility services engine recalculates location.
To further refine location calculations on a floor, you can define areas that are excluded (exclusion areas) in the calculations. For example, you might want to exclude areas such as an atrium or stairwell within a building. As a rule, exclusion areas are generally defined within the borders of an inclusion area.
To define an exclusion area, follow these steps:
Step 1 Choose Monitor > Site Maps.
Step 2 Click the name of the appropriate floor area.
Step 3 From the Select a command drop-down list, choose Map Editor.
Step 5 At the map, click the purple box on the toolbar.
Step 6 Click OK in the message box that appears. A drawing icon appears to outline the exclusion area.
Step 7 To begin defining the exclusion area, move the drawing icon to the starting point on the map, and click once.
Step 8 Move the drawing icon along the boundary of the area you want to exclude. Click once to start a boundary line, and click again to end the boundary line.
Step 9 Repeat Step 8until the area is outlined and then double-click the drawing icon. The defined exclusion area is shaded in purple when the area is completely defined. The excluded area is shaded in purple.
Step 10 To define additional exclusion regions, repeat Step 5 to Step 9.
Step 11 When all exclusion areas are defined, choose Save from the Command menu or click the disk icon on the toolbar to save the exclusion region.
Note To delete an exclusion area, click the area to be deleted. The selected area is outlined by a dashed purple line. Next, click the X icon on the toolbar. The area is removed from the floor map.
Step 12 Select the Location Regions check box if it is not already selected, click Save setting s, and close the Layers configuration page when complete.
Step 13 To resynchronize Prime Infrastructure and location databases, choose Services > Synchronize Services.
Step 14 In the Synchronize page, choose Network Designs from the Synchronize drop-down list and then click Synchronize.
You can confirm that the synchronization is successful by viewing two green arrows in the Sync. Status column.
To enable CMX analytics service on the mobility services engine within the Prime Infrastructure UI, follow these steps:
Step 1 Choose Services > Mobility Services Engine.
The Mobility Services Engines page appears.
Step 2 In the Mobility Services page, click the Device Name to configure its properties.
Step 3 To enable CMX analytics service on the mobility services engine, select the check box next to the CMX analytics Service.
Step 4 Click Save to save the settings.
See the Managing User Accounts chapter in the Cisco Prime Infrastructure Classic View Configuration Guide for Wireless Devices, Release 2.0 at the following URL:
http://www.cisco.com/en/US/products/ps12239/products_installation_and_configuration_guides_list.html
To log into CMX analytics user interface through a web browser, follow these steps:
Step 1 In the address line of browser, enter https://mse-ip-address/ui/, where mse-ip-address is the IP address of the CMX analytics server. CMX analytics user interface displays the User Login page.
Step 4 Click Login to log into CMX analytics.
The CMX analytics home page appears.
The CMX analytics provides ability to view the analytic results in both 2D (Open Street Maps) and 3D (WebGL) environments. This provides improved understanding of results on multiple floor paths, or when dwell times are calculated throughout a multi-storey building. The 3D environment presents the same information as the 2D environment.
WebGL is an advanced feature that provides graphic capabilities. All browsers do not support WebGL on a particular hardware. Verify your browser compatibility at the following URL: http://get.webgl.org/. If your browser supports WebGL, then you must see a spinning cube.
If your browser does not support WebGL, you must do the following:
– In the browser address line, enter about:config
– In the Search text box, enter webgl to filter the settings.
– Double click webgl.forceenabled.
– Make sure that webgl.disables is disabled.
– Download the latest building of Safari browser.
– You must enable the Develop menu and enable the WebGL.
– To enable Develop menu, choose Safari > Preferences.
– Select the Show Develop menu in menu bar check box.
– Choose Enable WebGL from the Develop menu.
Note If your system does not support 3D, then the analytic results are displayed only in 2D Open Street Maps view provided that GPS markers are enabled.
After installing the analytics, you must validate the results and ensure that the correct data is coming.
To validate the analytics for correct data, follow these steps:
Step 1 Look at the date to see how much data is in the Analytics database. When the analytics starts for the first time, it downloads the previous three days data by default if it is available. This takes several hours if there is a lot of data stored in the MSE. Therefore, you must see the current data appearing after an hour or so.
Step 2 The point data that is coming in must reflect in the expected building. This displays the areas of high and low density using the Heatmap option. These points should be in locations where you expect visitors and should reflect areas of high and low traffic.
Step 3 Run a Typical Location analysis for today across building from the Analytics tab. Check that the distribution of device icons show areas where most or lease people visited for the entire day. You can further refine this check by limiting the zones or time window.
You can validate areas where people spend more time than others, such as reception, restaurants, etc.
Figure 2-4 Distribution of Devices across the Floor
Step 4 Use the Rules pane to further focus on certain time periods or zones where you want to know the number and type of visitors.