Cisco Prime Infrastructure 2.2.3 Release Notes

Available Languages

Download Options

PDF (253.7 KB)
View with Adobe Reader on a variety of devices
ePub (82.2 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (91.2 KB)
View on Kindle device or Kindle app on multiple devices

Updated:September 30, 2015

Cisco Prime Infrastructure 2.2.3 Release Notes

Introduction

System Requirements

Installation Guidelines

Before You Begin Installing the Maintenance Release

Installation Scenarios Not Supported in Prime Infrastructure 2.2.3

Installing the Maintenance Release from Cisco Site

Installing the Maintenance Release from Local Storage

Installing the Maintenance Release in High Availability Mode

Troubleshooting Maintenance Release Installs in High Availability Implementations

Upgrading from Previous Releases of Cisco Prime Infrastructure

Submitting Feedback

Prime Infrastructure Licenses

Supported Devices

New Features and Enhancements

Important Notes

FAQs: Operations Center and Prime Infrastructure

Open Caveats

Resolved Caveats

Cisco Prime Infrastructure 2.2.3 Release Notes

This document contains the following sections:

Introduction

This is the third maintenance release for Cisco Prime Infrastructure 2.2.

You can install Cisco Prime Infrastructure 2.2.3 Maintenance Release on a server running the Cisco Prime Infrastructure, version 2.2, 2.2.1 and 2.2.2. This maintenance release supports coexistence of Wireless Technology Package 1.0.1 and Data Center Technology package 1.0.1.

System Requirements

For more information on server and web client requirements, see the section Understanding System Requirements of the Cisco Prime Infrastructure 2.2 Quick Start Guide.

Installation Guidelines

The following sections explain how to install the maintenance release.

Before You Begin Installing the Maintenance Release

Caution

Once you install this maintenance release, you cannot un-install or remove it.

Since the maintenance release 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 maintenance release installation to fail.

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

To revert to the original Prime Infrastructure 2.2, 2.2.1 or 2.2.2 installation, follow these steps:

1. Reinstall Prime Infrastructure 2.2 from an OVA or ISO distribution.

2. Install any prior point patches.

3. If the original version is Prime Infrastructure 2.2.1/2.2.2, install the maintenance release 2.2.1/2.2.2 over Prime Infrastructure 2.2.

4. Restore the data from the backup that you made before applying the maintenance release 2.2.3.

Similarly, if you are running Prime Infrastructure 2.2.x in a Virtual Machine (VM) and your organization permits taking VM snapshots, use the VMware client to take a VM snapshot before applying this maintenance release. Store the snapshot in an external storage repository, and restore from the snapshot if the maintenance release installation is unsuccessful.

If you are installing this maintenance release as part of a High Availability (HA) implementation, you will want to ensure that the network links between the two servers provide maximum bandwidth (at lease 100 Mbits/sec) and low latency (less than 20 milliseconds) throughout the maintenance release installation. For more information, see Troubleshooting Maintenance Release Installs in High Availability Implementations.

Installation Scenarios Not Supported in Prime Infrastructure 2.2.3

The following installation scenarios are not supported in Prime Infrastructure 2.2.3:

Installation of Wireless Technology Package 1.0.0 over Prime Infrastructure 2.2.3
Installation of Data Center Technology Package 1.0.0 over Prime Infrastructure 2.2.3

Installing the Maintenance Release from Cisco Site

Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance Release.

Step 1 Log in to the Prime Infrastructure 2.2, 2.2.1 or 2.2.2 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 the Critical Fixes pane to view the updates.

Step 5 Click Download corresponding to the Prime Infrastructure 2.2.3 Maintenance Release file name pi223-26.ubf.

Step 6 Click Install to install the maintenance release.

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 maintenance release installation from Prime Infrastructure Login page under Critical Fixes 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 maintenance release in the Updates tab, with “Installed” in the Status column.

Note We recommend you to take backup immediately after successful installation of Prime Infrastructure 2.2.3.

Installing the Maintenance Release from Local Storage

Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance Release.

Step 1 Download the Prime Infrastructure 2.2.3 Maintenance Release pi223-26.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 2.2 > Prime Infrastructure Patches-2.2.3 and save the file in your local storage.

Step 2 Log in to Prime Infrastructure 2.2, 2.2.1 or 2.2.2 server.

Step 3 Choose Administration > Software Update.

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

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

Step 6 In the Critical Fixes pane, click Install. You will see a dialog box informing that manual restart of Prime Infrastructure is required. 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 maintenance release installation from Prime Infrastructure Login page under Critical Fixes in the Installed Updates popup 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 maintenance release in the Updates tab, with “Installed” in the Status column.

Note We recommend you to take backup immediately after successful installation of Prime Infrastructure 2.2.3.

Installing the Maintenance Release in High Availability Mode

Download the Prime Infrastructure 2.2.3 Maintenance Release pi223-26.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 2.2 > Prime Infrastructure Patches-2.2.3 and save the file in your local storage.

To install the downloaded Prime Infrastructure 2.2.3 Maintenance Release pi223-26.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 Maintenance Release.
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 (HA) 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 Maintenance Release Installs in High Availability Implementations

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

If you are unable to verify that this maintenance release has been successfully installed on a Prime Infrastructure server, or one or both of the servers fails to re-start properly after installing the maintenance release, you may need to re-image the server as explained in Before You Begin Installing the Maintenance Release before continuing.

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.

Upgrading from Previous Releases of Cisco Prime Infrastructure

For detailed information about upgrading from previous releases of Prime Infrastructure, including the list of versions from which you can upgrade, see the If You Are Upgrading From Previous Releases of Prime Infrastructure section of the Cisco Prime Infrastructure 2.2 Quick Start Guide.

Submitting Feedback

Your feedback will help us improve the quality of our product. To send your feedback, follow these steps:

Step 1 Choose Administration > System Settings > Mail Server Configuration.

Step 2 In the Mail Server Configuration page, enter the mail server details.

Step 3 Click Save to save the configuration settings.

Step 4 Choose Help > Help Us Improve Cisco Products.

Step 5 In the Help Us Improve Cisco Products page, select the Yes, collect data periodically (monthly) option.

Step 6 Click OK.

Prime Infrastructure Licenses

For detailed information on procuring a license for Prime Infrastructure, see the Cisco Prime Infrastructure 2.2 Ordering and Licensing Guide.

Supported Devices

To see the list of devices supported in this release of Prime Infrastructure:

Step 1 Log in to Prime Infrastructure.

Step 2 Switch to the Converged Theme (if applicable).

Step 3 Click the question mark icon (Help) at the top right.

Step 4 Click Supported Devices List.

You can also view the Cisco Prime Infrastructure 2.2 Supported Devices list at the following URL:

http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-device-support-tables
-list.html

For detailed information on the software compatibility for the Cisco wireless devices, see the following URL:

http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html

For detailed information on Wireless LAN Controller software features that are not configurable in Prime Infrastructure Release 2.2 using the pre-packaged templates, see Non-Configurable Features for Wireless LAN Controller Software Releases in Cisco Prime Infrastructure 2.2 Release Notes.

New Features and Enhancements

There are no new features in this release.

Important Notes

Prime Infrastructure 2.1.x instances can authenticate via Prime Infrastructure 2.2.3 single sign-on (SSO) server only if you apply the ISE patch pi212_PIGEN_CSCur43834_01.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 2.1 > Prime Infrastructure Patches-2.1.2 before configuring Prime Infrastructure 2.2.3 SSO server IP in Prime Infrastructure 2.1.x instances. It is a prerequisite to manage Prime Infrastructure 2.1.2 instances in Prime Operation Center 2.2.3.
In addition to installing Prime Infrastructure 2.2.3 on Prime Infrastructure instances, make sure that you also install Prime Infrastructure 2.2.3 on Prime Operations Center.
Prime Operation Center supports both Prime Infrastructure 2.1.x with cluster enable Patch and 2.2.x as managed instance.
Install Plug and Play gateway before installing Prime Infrastructure 2.2.3.
Prime Infrastructure 2.2.3 has a fix for POODLE vulnerability which disables SSLv3 and enables TLS on Prime Infrastructure server. The CNS agent on the devices currently support only SSLv3 and is poodle vulnerable ( CSCus48378). Installing the Prime Infrastructure 2.2.3 maintenance release would break the Secure PnP (SSL and HTTPS enabled) functionality in Prime Infrastructure for devices.
If you upgrade Prime Infrastructure from version 1.4.x or version 2.1.x to Prime Infrastructure version 2.2.3, the Refresh From Network property settings under Floor Maps is set to disabled by default. You can enable the Refresh From Network property settings associated with the Floor Maps.

Caution

A Refresh on the Floor Map, will take long time to complete if you enable the Refresh From Network property settings under Floor Maps.

FAQs: Operations Center and Prime Infrastructure

For the frequently asked questions about Operations Center and its interactions with the instances of Prime Infrastructure that it manages, see Cisco Prime Infrastructure 2.2 Release Notes.

Open Caveats

Table 1 lists the Open Caveats in Cisco Prime Infrastructure Release 2.2.3.

Click the identifier to view the impact and workaround for the caveat. This information is displayed in the Bug Search Tool. You can track the status of the open caveats using the Bug Search Tool.

Table 1 Open Caveats
Identifier	Description
CSCuh16286	Global search for IPv6 clients based on IP addresses is not working.
CSCul06347	When comparing the Prime Infrastructure server and cluster, a few fields have mismatched data.
CSCul35804	Prime Infrastructure 2.0 has the CBC Mode vulnerability.
CSCuo68188	The syslogs tab does not display any data in the cluster server though the Prime Infrastructure instance has data in it.
CSCuo70141	Failback fails due to low bandwidth.
CSCuo71039	IPsec credentials are updated when bulk importing the devices.
CSCuo89119	The switchport link down event is categorized incorrectly as WLC link down event.
CSCup25645	Cross-launching to the source IP address from the Events page displays the alarm tab with no data available.
CSCup94066	When selecting many devices, the filter criteria is minimized and does not show anything inside the filter.
CSCuq04072	Unable to map WLAN mobility anchor for IPv6 wireless controller.
CSCuq51763	Device selection refresh issue in IWAN workflow.
CSCur21924	The columns in Prime Infrastructure wIPS alarms have to be edited to show only relevant information.
CSCur23731	When you click a WLC device to view inventory details, the Operations Center is unable to load data.
CScur45282	Auto SPT is running on adhoc rogues and showing false alarm.
CSCur45975	Backups with lengthy filenames are not restored.
CSCur56614	Error thrown while configuring dhcp option 82 fields in interface page.
CSCur58621	The Import from device option fails and images are displayed as not available.
CSCur67549	IWAN: The HUB Master Controller template is not part of routing instance configuration.
CSCur75625	For client attribute, Cross launch to ISE, if the filter is set as end-point ID, the query returns no data.
CSCur83964	The failover operation is not successful during HA software update.
CSCur85223	The Initial Device Setup is empty for restored Server and any of the supported devices from “Unassigned” group is not listed.
CSCur85653	Location Groups are placed under All Devices.
CSCur85763	The report shows the status as Not Applicable, when only the Admin status of 802.11ac is configured via LWAP template.
CSCur87358	The Device Port Summary shows no information for 5508 Series WLAN Controller.
CSCur91049	ActiveMQ flooding slows down the process of creating a group.
CSCur94452	Unwanted dialog box appears while trying to open existing client reports.
CSCus15638	Misleading message shown under “Compliance Service” after clicking Save.
CSCus54753	Issue in setting up Multicast Address for both Cisco 5500 and 8500 devices with dual stack.
CSCus72290	Swim image distribution to many devices in parallel may cause the job to be in pending state forever.
CSCus75042	Issue in cofing archive page - Device details are not displayed.
CSCus77041	Plug and Play day-0 functionality is not happening for HTTPS Provisioning.
CSCus78734	Prime Infrastructure 2.2.1 IPv6 Mobility anchor set issue.
CSCus88449	Rogue reports show “No data available” message for IPv6 controller filter.
CSCut95862	In Prime Infrastructure 2.2.1 /2.2.2, the technology packages are not listed under “Add-ons”, instead listed under “critical fixes” in the Software Update page.
CSCut99230	Wrong mobility anchor/Export anchor WLC IP is displayed in Prime Infrastructure 2.2.2.
CSCut99761	Enable mobility mode button should be disabled for 5520/8540 in Prime Infrastructure 2.2.2.
CSCuu12444	When Prime Infrastructure 2.2.2 UBF is installed over Prime Infrastructure 2.2.1 system, the Software Update page does not list the update without process restart.
CSCuw31929	Installation of Prime Infrastructure 2.2.3 and restarting ncs process are prerequisites to install revised technology packages.
CSCuw31557	Custom Application deployment window does not display ISR/ASR devices.

Resolved Caveats

Click the identifier to view the impact and workaround for the caveat. This information is displayed in the Bug Search Tool. You can track the status of the resolved caveats using the Bug Search Tool.

Table 2 Resolved Caveats
Identifier	Description
CSCuf65530	Some of the WLCs are not properly inserted into mne table during upgrade
CSCur70325	“Top N Devices with Most Alarms” dashlet does not display data for Devices.
CSCur72133	Date stamp is not shown in the tool tip on some chart types in Client AP association history chart.
CSCus23761	Error message appears, when navigating out of a page while there is an ongoing process.
CSCus81393	Unified AP database update fails if SSH/Telnet credentials are not configured on the AP.
CSCus85944	Prime Infrastructure 2.2 fails to restore Prime Infrastructure 1.4 backup file.
CSCut09703	Background tasks are stuck in waiting state, since ISE is not responding.
CSCut12655	Remove SSO requirement for a reverse lookup on IP address
CSCut37025	Credentials are not applied on a device, when it is discovered using SSH credential profile.
CSCut42639	Prime Infrastructure adds default VLANs, when changing allowed VLANs.
CSCut58313	Netflow data site classification needs to stamp the location group id.
CSCut80827	The Clients Statistics dashlet in Clients & Users page is misleading, on selecting the 1 week option.
CSCut81188	Advanced Search option for selecting Floor area in Client category takes long time to load.
CSCut96535	Restoring Prime Infrastructure to version 2.2 fails.
CSCuu00995	Network Aware filter is not working.
CSCuu01614	Manual Switch Port Tracing: Hop 0 tracing skips switches other than 3750.
CSCuu14943	WLAN template is misplaced in different folder during discovery of template Discovery from Controller.
CSCuu21721	Some devices are getting synchronized periodically for every 15-20 minutes.
CSCuu22124	Prime Infrastructure does not retrieve license count for 4400 wireless LAN controller.
CSCuu28072	Configuration Archive page is not launching properly.
CSCuu28739	Configuration > Features & Technologies page does not show tree view listing of templates.
CSCuu39350	Unable to delete ISR router from Cisco prime Infrastructure 2.2.
CSCuu40399	Client data is not updated when device Ip address in last session is null.
CSCuu45098	wIPS Alarm Summary report fails to run.
CSCuu46260	Clients and Users page inconsistently shows empty graph for client data rate.
CSCuu48182	Interface capacity report is empty for Catalyst 6K Virtual Switching System (VSS) in Prime Infrastructure 2.2.
CSCuu51082	Signed certificates of both primary and secondary servers are same.
CSCuu53049	Report selection criteria is lost on a saved report in Prime Infrastructure 2.2.1.
CSCuu62065	Service restart happens in primary on primary failover state.
CSCuu66784	Client Traffic report is empty, when viewing more than one site at a time.
CSCuu69955	Polling time is optimized for device and interface monitoring jobs.
CSCuu79533	Oracle environment needs to be set correctly on secondary/standby server.
CSCuu82403	Evaluation of ncs for OpenSSL June 2015.
CSCuu84291	Prune scripts fails to execute and points to wcs instead of wcss1.
CSCuu85618	Interface Capacity report is not displayed in Reports > Reports Launch pad > Device.
CSCuu85852	ISR G2 891F is not recognized as AVC capable during AVC deployment.
CSCuu87516	Even if the backup is not fully copied in repository, it is marked as successful.
CSCuu87994	Noise by Channel graph always shows 110 in Monitor > Network Device > Unified AP > Interfaces page.
CSCuu90803	Issue occurs while opening a saved report template in upgraded server.
CSCuu91191	Support for 30 days long client data retention.
CSCuu94828	Unpredictable behavior while handling virtual domains with a space character in operations center 2.2.2.
CSCuu97721	Oracle database of Prime Infrastructure throws an ORA-4021 error in some HA scenarios.
CSCuu98616	Mandatory prompt message is not displayed after adding and saving a new device custom prompt in Administrator > System Settings > Inventory.
CSCuu98662	The Inventory and Alarm pages do not display any information after test MIB validation.
CSCuv00656	An error occurs when adding an object in Shared Policy object for IPv4/IPv6 Network Object.
CSCuv00834	SSO server addition by DNS name is missing in Prime Infrastructure 2.2.3 setup.
CSCuv00896	An error occurs while trying to deploy the AVC template on a device and archiving jobs.
CSCuv02930	Prime Infrastructure services fail to restart when installing 2.2.3 software update on Prime Infrastructure 2.2 server.
CSCuv06873	Issue in primary and secondary domain maps folder synchronizing, after HA registration.
CSCuv07041	For non-root users, Dashboard > Access point > Site page displays the performance of APs.
CSCuv08754	Prime Infrastructure 2.2.3 secondary server fails to restart after installing the patch 223_4.
CSCuv09482	Different warning messages appear while adding the same device with different parameters.
CSCuv18331	Configuration tab does not load any data for the Nexus switches.
CSCuv19912	“Create Element” button does not appear in Network Topology page.
CSCuv20928	WLCs and devices need to be in alphabetical order in Config Deploy page.
CSCuv21888	Device Availability Summary dashlet displays incorrect device status information.
CSCuv21897	Op Center - Device IP hyperlink is missing in Device Reachability Status dashlet.
CSCuv21905	Device Memory/CPU Utilization Trend dashlet displays incorrect polled time.
CSCuv22518	Device selector in Configuration template takes more time to load.
CSCuv26599	Oracle memory gets Reset to 6GB upon HA Failback.
CSCuv26601	Spell error seen in Application Troubleshooting page.
CSCuv30887	Unable to access Prime Infrastructure login page.
CSCuv31769	Rogue AP History data needs longer or flexible retention period and size.
CSCuv33527	Client session data retention gets reset upon HA failover.
CSCuv35102	Error occurs when loading Device Groups in Alarms and Events page.
CSCuv43044	Prime Infrastructure 2.2: IPFIX and NETFLOW applications are not getting populated from taxonomy file no.14.
CSCuv49206	The fix for CSCuu97721 in Active Dataguard Standby database, is lost upon HA failback.
CSCuv49477	Application fails to start, after the failure of HA failback.
CSCuv56960	Small Business switches in Prime Infrastructure topology Maps do not show links.
CSCuv59542	HA with SSO configured fails to launch secondary server.
CSCuv59689	Opcenter - Site filter does not display User Created Location subgroups.
CSCuv61381	The real value of Default ICMP Heartbeat interval is incorrect.
CSCuv79823	Backup generation failed in secondary server.
CSCuv90723	Database index on CLIENTSESSIONINFO is missing.
CSCuv91354	Active Secondary goes to standalone secondary state after a restart.
CSCuv97607	Top N Clients dashlet is not displaying usage data, when configuring Netflow template in a device without matching output interface.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

This document is to be used in conjunction with the documents listed in the “Related Documentation” section.

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.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

Related Cisco Community Discussions

This Document Applies to These Products

Prime Infrastructure 2.2

Cisco Prime Infrastructure 2.2.3 Release Notes

Available Languages

Download Options

Table of Contents

Cisco Prime Infrastructure 2.2.3 Release Notes

Introduction

System Requirements

Installation Guidelines

Before You Begin Installing the Maintenance Release

Installation Scenarios Not Supported in Prime Infrastructure 2.2.3

Installing the Maintenance Release from Cisco Site

Installing the Maintenance Release from Local Storage

Installing the Maintenance Release in High Availability Mode

Troubleshooting Maintenance Release Installs in High Availability Implementations

Upgrading from Previous Releases of Cisco Prime Infrastructure

Submitting Feedback

Prime Infrastructure Licenses

Supported Devices

New Features and Enhancements

Important Notes

FAQs: Operations Center and Prime Infrastructure

Open Caveats

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

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

Was this Document Helpful?

Contact Cisco

Related Cisco Community Discussions

This Document Applies to These Products

Cisco Prime Infrastructure 2.2.3 Release Notes

Available Languages

Download Options

Table of Contents

Cisco Prime Infrastructure 2.2.3 Release Notes

Introduction

System Requirements

Installation Guidelines

Before You Begin Installing the Maintenance Release

Installation Scenarios Not Supported in Prime Infrastructure 2.2.3

Installing the Maintenance Release from Cisco Site

Installing the Maintenance Release from Local Storage

Installing the Maintenance Release in High Availability Mode

Troubleshooting Maintenance Release Installs in High Availability Implementations

Upgrading from Previous Releases of Cisco Prime Infrastructure

Submitting Feedback

Prime Infrastructure Licenses

Supported Devices

New Features and Enhancements

Important Notes

FAQs: Operations Center and Prime Infrastructure

Open Caveats

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

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

Was this Document Helpful?

Contact Cisco

Related Cisco Community Discussions

This Document Applies to These Products

Share