This is the first maintenance release for Cisco Prime Infrastructure 3.5.1
You can install Cisco Prime Infrastructure 3.5.1 Maintenance Release on Cisco Prime Infrastructure 3.5. Prime Infrastructure 3.5.1 Maintenance Release file PI_3_5_1-1.0.22.ubf is approximately 183 MB. The downloading time depends on the available network connection in the enterprise environment. Ensure that you have adequate bandwidth and are not running into high latency issues.
Cisco End User License Agreement
This software is governed by the Cisco End User License Agreement available at the following URL:
Cisco Prime Infrastructure 3.5 collects anonymous usage data to help improve the product. By using this product, you are providing your consent to collect your usage data.
For more information, or to opt out at any time, go to Administration > Settings > System Settings > General > Help Us Improve.
Supported Physical Appliance Environments
Prime Infrastructure 3.5.1 is supported on the Cisco Prime Infrastructure Physical Appliance (Gen 2 and Gen 3). For more information, see the Physical Appliance Options section in the Cisco Prime Infrastructure 3.5 Quick Start Guide.
Prime Infrastructure 3.5.1 is supported on the Cisco Prime Infrastructure Virtual Appliance (VMware). For more information, see the Understand System Requirements section in the Cisco Prime Infrastructure 3.5 Quick Start Guide.
Before You Begin Installing the Maintenance Release
CautionOnce 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.
If the backup is a Prime Infrastructure 3.5 backup, restore the backup on Prime Infrastructure 3.5 server before applying the Maintenance Release 3.5.1.
Similarly, if you are running Prime Infrastructure 3.5 in a Virtual Machine (VM) and your organization permits taking VM snapshots, stop Prime Infrastructure and 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. For more details, see Restore an Application Backup in the Cisco Prime Infrastructure 3.5 Administrator Guide.
To restore the backup of the Prime Infrastructure 3.5 installation, follow these steps:
1. Install Prime Infrastructure 3.5 from an OVA or ISO distribution.
2. Clear the Cache and log in to Prime Infrastructure GUI again and proceed with the Prime Infrastructure 3.5.1 upload.
Step 4 Log in with your cisco.com credentials and click Yes or No in the Remember Credentials pop-up dialogue box.
Step 5 Click Show Details in the Critical Fixes pane to view the updates.
Step 6 Click Download corresponding to the Prime Infrastructure 3.5.1 Maintenance Release file name PI_3_5_1-1.0.22.ubf.
Step 7 Click Install to install the maintenance release.
Step 8 Click Yes in the popup dialogue box to install Cisco Prime Infrastructure 3.5.1. It may take approximately 30 minutes for the installation process to complete.
Note Do not manually restart the server while the installation is in progress.
Step 9 You can verify the maintenance release installation from Prime Infrastructure Login under Critical Fixes by clicking View Installed Updates 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.
Installing the Maintenance Release from Local Storage
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 PI_3_5_1-1.0.22.ubf is listed under FileName column.
Step 6 In the Critical Fixes pane, click Install.
Step 7 Click Yes in the pop-up dialogue box to install Cisco Prime Infrastructure 3.5.1. It may take approximately 1 hour for the installation process to complete.
Note Do not manually restart the server while the installation is in progress.
Step 8 You can verify the maintenance release installation from Prime Infrastructure Login under Critical Fixes by clicking View Installed Updates 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.
Installing the Maintenance Release in High Availability Mode
Note Prime Infrastructure 3.5.1 can be applied only in primary and secondary standalone servers. The server will restart automatically once the installation is complete. The restart typically takes 25 to 35 minutes. You cannot apply Prime Infrastructure 3.5.1 when HA is enabled.
If you are installing Cisco Prime Infrastructure Maintenance Release 3.5.1 on High Availability (HA) paired servers, you will get the following error message:
Continue the patching once HA removed completely. For more details, see the How to Patch New HA Servers section in the Cisco Prime Infrastructure 3.5 Administrator Guide.
Troubleshooting Maintenance Release Installs in High Availability Implementations
If you are unable to apply this maintenance release in a High Availability (HA) implementation, check whether your network bandwidth, throughput and latency meets the network requirements recommended in Network Throughput Restrictions on HA section in the Cisco Prime Infrastructure 3.5 Administrator Guide. 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 restart 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 the back-logs section in the Cisco Prime Infrastructure 3.5 Command Reference Guide.
Renewing AAA Settings After Installing a New Prime Infrastructure Version
If you are using external RADIUS or TACACS+ user authentication, before migrating your existing data to a new version of Prime Infrastructure, you must transfer the expanded Prime Infrastructure user task list to your AAA server. After you upgrade Prime Infrastructure, you must re-add any permissions on the TACACS+ or RADIUS server and update the roles in your TACACS server with the tasks from the Prime Infrastructure server. For more details, Configure External Authentication section in the Cisco Prime Infrastructure 3.5 Administrator Guide.
Migrating from Previous Releases of Cisco Prime Infrastructure
You can restore the backup from the following Prime Infrastructure versions to Prime Infrastructure 3.5.1:
Cisco Prime Infrastructure 188.8.131.52
Cisco Prime Infrastructure 3.0.1
Cisco Prime Infrastructure 3.0.2
Cisco Prime Infrastructure 3.0.3
Cisco Prime Infrastructure 184.108.40.206.132
Cisco Prime Infrastructure 3.1.1
Cisco Prime Infrastructure 3.1.2
Cisco Prime Infrastructure 3.1.3
Cisco Prime Infrastructure 3.1.4
Cisco Prime Infrastructure 3.1.5
Cisco Prime Infrastructure 3.1.6
Cisco Prime Infrastructure 3.1.7
Cisco Prime Infrastructure 3.2
Cisco Prime Infrastructure 3.2.1
Cisco Prime Infrastructure 3.2.2
Cisco Prime Infrastructure 3.4
Cisco Prime Infrastructure 3.4.1
Cisco Prime Infrastructure 3.4.2
Cisco Prime Infrastructure 3.5
If you are running multiple previous releases of Prime Infrastructure (for example, you are running version 220.127.116.11 and 3.0.1, 3.0.2, 3.0.3, 18.104.22.168.132), you must select one version from which to restore data.
See Before You Migrate Your Data in the Cisco Prime Infrastructure 3.5 Quick Start Guide before you restore your data from Prime Infrastructure 3.0.x or 3.1 to your newly installed Prime Infrastructure 3.5 server:
You can apply the Cisco Prime Infrastructure 3.5.1 over Cisco Prime Infrastructure 3.5 upgraded server. For detailed information about upgrading from previous releases of Prime Infrastructure, including the list of versions from which you can upgrade, see the How to Upgrade From Previous Releases of Prime Infrastructure section of the Cisco Prime Infrastructure 3.5 Quick Start Guide.
Your feedback will help us improve the quality of our product. You must configure the email server and then enable data collection to configure the feedback tool. To send your feedback, follow these steps:
Step 1 If you have configured your mail server, go to Step 4.
Step 2 Choose Administration > Settings > System Settings > Mail and Notification > Mail Server Configuration.
Step 3 In the Mail Server Configuration page, enter the mail server details, then click Save to save the configuration settings.
Step 4 Choose Administration > Settings > System Settings > General > Help Us Improve.
Step 5 In the Help Us Improve Cisco Products page, select Yes, collect data periodically, then click Save.
Step 6 Click the Settings icon, then select Feedback > I wish this page would....
Step 7 Enter your feedback, then click Submit Feedback.
In addition to installing Prime Infrastructure 3.5.1 on Prime Infrastructure instances, make sure that you also install Prime Infrastructure 3.5.1 on Prime Operations Center.
Prime Operations Center 3.5.1 manages Prime Infrastructure 3.5.1. You must ensure that Prime Operations Center version is the same as the version of the Prime infrastructure instances that it manages. For more details, see Set Up Operations Center in Cisco Prime Infrastructure 3.5 Administrator Guide.
You can install Prime Infrastructure 3.5.1 on operations center from the Cisco Site, or local storage. You can also install the update in high availability mode if the high availability is available on Prime Operations Center. For more details on how to install the update, see Installation Guidelines.
After installing the update, enable HA for Operations Center. For more details, see Enable HA for Operations Center in Cisco Prime Infrastructure 3.5 Administrator Guide.
If the email address contains numeric value (e.g. email@example.com), the email notification sent to the email destination will contain only the alarm instance ID.
CLI templates and Guest users cannot be deployed from Wireless Configuration Groups.
Cisco Prime Infrastructure does not support monitoring for Cisco Application Control Engine (ACE) module, because ACE has been moved to end-of-life and does not respond to related monitoring MIBs.
If the Boot Option in the BIOS settings is enabled with UEFI shell, deployment gets completed. Once deployment gets completed, it fails to enter the configuration mode, instead enters the shell mode in the CIMC console. UEFI shell option must be disabled in the BIOS settings to access configuration mode.
If VIP is enabled, after failover or fallback, SSO server should be added again in Prime Infrastructure for the auto login to work.
It is recommended to use different web browsers to avoid from menus getting affected while loading in ISE, during the cross launching of ISE reports from Cisco Prime Infrastructure and logging in to ISE Admin.
Table 1 lists the Open Caveats in Cisco Prime Infrastructure Release 3.5.1.
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.
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.
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. (1721R)
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.