Readme for Wireless Technology Package 1.0.1 for Cisco Prime Infrastructure 2.2.3

Before You Begin Installing the Wireless Technology Package

Caution Once you install this package, you cannot uninstall or remove it.

---

Since the package is not removable, it is important to have a way to revert your system to the original version in case hardware or software problems cause the package installation to fail.

To ensure you can do this, take a backup of your system before downloading and installing this UBF package.

To revert to the original Cisco Prime Infrastructure 2.2.3 Maintenance Release installation, follow these steps:

1. Reinstall Prime Infrastructure 2.2 from an OVA or ISO distribution and install Cisco Prime Infrastructure 2.2.3 Maintenance Release.

2. Restore the data from the backup that you made before applying the package.

Similarly, if you are running Cisco Prime Infrastructure 2.2.3 Maintenance Release in a Virtual Machine (VM) and your organization permits taking VM snapshots, use the VMware client to take a VM snapshot before applying this package. You can store the snapshot in an external storage repository, and restore from the snapshot if the package is unsuccessful.

If you are installing the package as part of a High Availability (HA) implementation, you have to ensure that the network links between the two servers provide maximum bandwidth and low latency throughout the package installation. For more information, see Troubleshooting Package Installation in High Availability Implementations section.

Installing the Wireless Technology Package from Cisco Site

Step 1 Log in to the Prime Infrastructure 2.2.3 server.

Step 2 Choose Administration > Software Update.

Step 3 Click Download.

Step 4 Log in with your cisco.com credentials and click Show Details in Prime Add-Ons pane to view the updates.

Step 5 Click Download corresponding to the wireless technology package 1.0.1 file name ca_technology_package-2.1.0.0.41.ubf.

Step 6 Click Install to install the Technology Package.

Step 7 Restart the Cisco Prime Infrastructure server as explained in Restarting Prime Infrastructure in Cisco Prime Infrastructure 2.2 Administration Guide to complete the installation process.

Step 8 You can verify the package installation from Prime Infrastructure Login page under Prime Add-Ons by hovering your mouse over the version and also by logging into the server and choosing Administration > Software Update. You should see a listing for the package in the Updates tab, with “Installed” in the Status column.

Installing the Wireless Technology Package from Local Storage

Step 1 Download the Wireless Technology Package ca_technology_package-2.1.0.0.41.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 2.2 > Prime Infrastructure Add-ons and save the package file in your local storage.

Step 2 Log in to Prime Infrastructure 2.2.3 server.

Step 3 Choose Administration > Software Update.

Step 4 Click Upload and browse to the location where you have saved the package file. Click OK to upload the file.

Step 5 In the Status of Updates pane, click the Files tab and check whether ca_technology_package-2.1.0.0.41.ubf is listed under FileName column.

Step 6 In the Prime Add-Ons pane, click Install. You will see a popup message indicating the manual restart of Prime Infrastructure. Click Yes for successful installation.

Step 7 Restart the server by first executing the ncs stop command and then the ncs start command, as explained in Restarting Prime Infrastructure in Cisco Prime Infrastructure 2.2 Administration Guide.

Step 8 You can verify the package installation from Prime Infrastructure Login page under Prime Add-Ons by hovering your mouse over the version and also by logging into the server and choosing Administration > Software Update. You should see a listing for the package in the Updates tab, with “Installed” in the Status column.

Installing the Technology Package in High Availability Mode

Download the Wireless Technology Package ca_technology_package-2.1.0.0.41.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 2.2 > Prime Infrastructure Add-ons and save the package file in your local storage.

To install the downloaded Wireless Technology Package ca_technology_package-2.1.0.0.41.ubf in High Availability mode follow the below steps:

• Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Wireless Technology Package.
• If your current Prime Infrastructure implementation has High Availability (HA) servers that are not at the same patch level, see Patching Paired High Availability Servers in Cisco Prime Infrastructure 2.2 Administration Guide.
• If you are setting up a new Prime Infrastructure High Availability implementation and your new servers are not at the same patch level, see Patching New High Availability Servers in Cisco Prime Infrastructure 2.2 Administration Guide.

Troubleshooting Package Installation in High Availability Implementations

Users who apply this package in a High Availability (HA) implementation may experience difficulties if the network links between the two servers offer low bandwidth and high latency. In particular, this kind of low throughput can cause the post-package restart and re-registration to take far longer than normal. In most cases, simply waiting longer will fix the problem with no intervention. In few cases, continued or intermittent throughput problems can cause complete failure. If you believe this has occurred, contact Cisco TAC.

If you are unable to verify that the package has been applied to a server, or one or both of the servers fail to restart properly after the package installation, you may need to re-image the server as explained in Before You Begin Installing the Wireless Technology Package.

In all cases, you can use the backup-logs command on one or both servers to get information on the source of the failure. For more information, see backup-logs in Command Reference Guide for Cisco Prime Infrastructure 2.2.

Converged Access Template based Workflow Deployment

Prerequisites

This section describes the prerequisites for Layer 2, Layer 3, and Server configurations for Converged Access template based workflow deployment.

Prerequisites for Layer 2 Configuration

• Layer 2 network in branch, campus and demilitarized zone (DMZ) must be present before using Converged Access workflows:

– Wireless Management VLAN

• Create VLAN ID in database.
• Assign network wide common or unique VLAN name.
• Associate VLAN to AP ports.

– Wireless Client VLAN

• Create VLAN ID in database.
• Assign network wide common VLAN name.

– Guest Client VLAN

• Create VLAN ID in database of Guest Anchor Wireless LAN Controller (WLC).
• VLAN must be common on all Guest Anchor.
• Enable DHCP Snooping and Trust settings on Wireless Client VLANs.
• Allow wireless management and wireless client VLAN on L2 Trunk ports of switches and upstream L2/L3 devices (Router/Switch).

Prerequisites for Layer 3 Configuration

• Layer 3 gateway configuration in Branch, Campus and DMZ must be present before using Converged Access workflows:

– Layer 3 Interfaces—SVI/Sub-Interface.

– DHCP Configuration—Relay or Local Pool.

– Route Advertisement

• IP default-gateway on Catalyst switches and 5760 Guest Anchor or WLC.

Prerequisites for Server Configuration

• Cisco Prime Infrastructure

– All network-wide catalyst switches and 5760 WLCs must be configured with SNMP.

– Programmed in Cisco Prime Infrastructure Device Management

– Link Cisco Prime Infrastructure with Cisco ISE engine as external server to centrally monitor end-to-end client connectivity and policy enforcement details.

• Cisco ISE/ACS

– All network devices including catalyst switches and Guest Anchor WLC must be configured in Cisco ISE/ACS to enable centralized policy engine function.

– No AAA configuration required on network devices. Automated using Cisco Prime Infrastructure workflows.

• DHCP Server—Internal or external DHCP server must be preconfigured with appropriate pool settings for wireless clients.
• DNS Server—must be preconfigured with appropriate name-lookup process to successfully connect the network.

The converged access template based workflow deployment supports 5760, 3650 and 3850 platforms and can be deployed in small, large and centralized networks.

Step 1 Choose Services > Converged Access.

Step 2 Click Next to choose the configuration.

Step 3 From the Select Deployment Model drop-down list, choose any one of the following options:

• IOS-XE Controller - Small Network
• IOS-XE Controller - Large Network
• IOS-XE Centralized Wireless Network

Step 4 Click Next to choose the devices to be deployed.

Step 5 Choose the devices and click Next to apply the selected network configuration.

The selected device will be listed out in the left pane and in the right pane you can configure the templates by entering the values for the WLANs, Guest WLAN, Security, and Wireless Management. For more details, see Converged Access Template Field Descriptions.

Step 6 Click Apply and then Next to view the confirmation screen.

The confirmation screen allows you to view the device configuration information before deployment.

Converged Access Template Field Descriptions

This section contains the field descriptions for converged access template.

Table 2 WLAN Field Descriptions

Table 3 Guest Controller Field Descriptions

Table 4 Security Field Descriptions

Table 5 Application Services Field Descriptions

Table 6 Wireless Mobility Field Descriptions

Table 7 Wireless Management Field Descriptions

Enhanced Guided Workflow for Wireless Deployment

This technology package provides an enhanced guided workflow for configuring the wireless devices.

Step 1 Choose Configuration > Plug and Play > Initial Device setup.

Step 2 Click Next to assign location to new devices.

Step 3 Choose a location from Add these devices to the location drop-down list and Click Next.

Step 4 Choose Add wireless features to my device(s) from the I would like to drop-down list.

Step 5 (optional) Check the I would like to configure my guest access as part of my wireless configuration check box.

Step 6 Choose Create a new Mobility Group or any configured mobility group from the Mobility Group drop-down list and click Next.

Step 7 Configure the selected devices as Mobility Controller/Mobility Agent or delete the Mobility Controller/Mobility Agent from the Mobility group, and click Next.

Step 8 Enter the wireless parameter values for the new devices and click Next. You cannot change the wireless parameter values of the preconfigured devices.

Step 9 Click Next to add secure wireless configuration details for WLAN connectivity.

Step 10 If you have selected Guest Access in Step 5, provide the Guest WLAN details.

Step 11 Click Next to view the wireless device configuration before deployment.

Monitoring Dashlet for Unreachable MA-MC CAPWAP Tunnels

You can add a new Unreachable MA-MC CAPWAP Tunnels dashlet in Overview > General dashboard and Performance > Site dashboards, for more details see, Adding Dashlets in Cisco Prime Infrastructure User Guide 2.2. The Unreachable MA-MC CAPWAP Tunnels dashlet displays the unreachability status between the mobility agent and mobility controller.

Support for Cisco Meraki Devices

This technology package provides a single pane of glass visibility for both Cisco and Cisco Meraki devices. You can view both Cisco wireless network and Cisco Meraki network at the same time.

The following features are supported in this technology package:

• Discovery of Cisco Meraki devices
• Inventory Collection
• Device Reachability (Up/ Down)
• Client Count

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2012-2015 Cisco Systems, Inc. All rights reserved.