You can install Cisco Prime Infrastructure 3.10.5 on Cisco Prime Infrastructure 3.10.2 System Patch or Cisco Prime Infrastructure 3.10.3 or Cisco Prime Infrastructure 3.10.4+3.10.4 System Patch or Cisco Prime Infrastructure 3.10.4 Update 01 or Cisco Prime Infrastructure 3.10.4 Update 02+3.10.4 Update 02 System Patch or Cisco Prime Infrastructure 3.10.4 Update 03 from Software Download page.

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.

Similarly, if you are running Prime Infrastructure 3.10.4 Update 03 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.10 Administrator Guide.

To revert to Prime Infrastructure 3.10.5 installation (with PI 3.10.x, PI 3.9.x, PI 3.8.x, or PI 3.7.x backup), follow these steps:

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

2. Upgrade to Cisco Prime Infrastructure 3.10.2 using tar bundle and install PI 3.10.2 system patch once after upgrade is completed. For more information, see Cisco Prime Infrastructure 3.10.2 Release Notes

3. Install Cisco Prime Infrastructure 3.10.5

4. Install Cisco Prime Infrastructure 3.10.5 System Patch

5. If you have a prior 3.10.x, 3.9.x, PI 3.8.x, PI 3.7.x backup - Restore this backup

If you are installing this release as part of a High Availability (HA) implementation, see Installing the Maintenance Release in High Availability Mode in the Cisco Prime Infrastructure 3.10 Administrator Guide .

Download PI_3_10_5-1.0.29.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 3.10 > Prime Infrastructure Patches - 3.10.5 and save the file in your local system.

To install the downloaded PI_3_10_5-1.0.29.ubf in High Availability mode follow the below prerequisites:

• Make sure that you have completed the recommended preparation steps given in Before You Begin Installing MR.

Note	Prime Infrastructure 3.10.5 can be applied only in primary and secondary standalone servers. The server will restart automatically once the installation is complete. The restart typically takes more than 60 minutes. You cannot apply Prime Infrastructure 3.10.5 when HA is enabled.

• If you are installing Cisco Prime Infrastructure 3.10.5 on High Availability (HA) paired servers, you will get an error message.

For more details, see Remove HA Via the GUI in the Cisco Prime Infrastructure 3.10 Administrator Guide.

• 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.10 Administrator Guide .

• Prime was migrated to Smart Receiver and as per their guidelines Direct and Transport Gateway mode is not supported. You must use Proxy to enable smart license using new url https://smartreceiver.cisco.com/licservice/license.

• Cisco announced the End-of-Life and End-of-Sale for all versions of Prime Infrastructure. Please use the PDMT to migrate data to Cisco DNA Center or use Cisco Networking Bot for self-help migration. For more information reach out to the migration team at primetodnacmigration@external.cisco.com.

• After installing Prime Infrastructure 3.10.5, you will be notified with the below warning message during ncs status, show version, ncs stop, ncs start, and restore console and this can be ignored as there is no functionality impact:

  SLF4J: Class path contains multiple SLF4J bindings.

  SLF4J: Found binding in [jar:file:/opt/CSCOlumos/lib/xmp-third-party/com.cisco.xmp.osgi.slf4j-log4j12-1.5.8.PATCHED.jar!/org/slf4j/impl/StaticLoggerBinder.class]

  SLF4J: Found binding in [jar:file:/opt/CSCOlumos/lib/xmp-third-party/log4j-slf4j-impl-2.20.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]

  SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

• By default, the Automonitoring device health does not monitor Security and VPN Devices. Due to this, Security and VPN Devices such as ASA devices does not appear in the Wired Device Availability report. To include them in the report, you will need to create an additional Device Health policy in the Monitoring Polices and select the ASA device in the policy, and generate the report.

• Cisco Prime Infrastructure supports only one unique registration interface for each GDOI group. If you need multiple registration interface support, please contact the Cisco Technical Assistance Center (TAC).

• The EOL/EOS message always appears on the login page of Prime Infrastructure.

• The EOL/EOS message appears in a pop-up notification window every time the user login to the Prime Infrastructure. However, after restart of the Prime Infrastructure services, the pop-up message will not be notified in the future.

• For all the versions of Prime Infrastructure, Prime XWT Widgets are not compatible with the latest versions of Chrome and Edge browsers. This impacts the prime xwt actions such as add, update, delete, duplicate, and so on.

  • Edge:

    • 114.0.1823.51

    • 114.0.1823.43

  • Chrome:

    • 114.0.5735.133

• It is recommended to use Firefox or lower versions of Chrome and Edge browsers to carry out the Prime XWT widget actions in the Prime Infrastructure.

• When you restore to Cisco Prime Infrastructure 3.10.4 from earlier versions 3.7.x, 3.8.x, 3.9.x, 3.10.x backup, you will be notified with the following warnings in the restore console window:

  
  Warning:
  <verisigntsaca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  <airespace-root> uses a 1536-bit RSA key which is considered a security risk. This key size will be disabled in a future update. 
  <verisignclass1ca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  <verisignclass1g2ca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  <verisignclass2g2ca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  <verisignclass3ca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  <verisignclass3g2ca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  <verisigntsaca> uses a 1024-bit RSA key which is considered a security risk. This key size will be disabled in a future update.
  Warning:
  <airespace-root> uses a 1536-bit RSA key which is considered a security risk. This key size will be disabled in a future update.

  These warning messages are displayed due to the recent upgrade of JRE in Prime Infrastructure 3.10.2. For more information, see JDK-8172404.