Cisco Prime Infrastructure 2.1.2 Release Notes
Before You Begin Installing the Patch
Installing the Patch With High Availability
Troubleshooting Patch Installs in HA Implementations
Upgrading Prime Infrastructure
Supported Wireless LAN Controller Hardware Models
Non Configurable Features for Wireless LAN Controller Software Releases
Non Configurable Features for Wireless LAN Controller Release 8.0
Non Configurable Features for Wireless LAN Controller Release 7.6
Non Configurable Features for Wireless LAN Controller Release 7.5
Non Configurable Features for Wireless LAN Controller Release 7.4
Obtaining Documentation and Submitting a Service Request
Last Updated: November 18, 2014
These release notes contain the following sections:
This is a patch release for Cisco Prime Infrastructure 2.1.
You can install this patch release on top of your existing Prime Infrastructure 2.1 installation or Prime Infrastructure 2.1.1 patch.
For more information on server and web client requirements, see the System Requirements section of the Cisco Prime Infrastructure 2.1 Quick Start Guide.
The following sections explain how to install the patch.
Because the patch 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 patch installation to fail.
To ensure you can do this, take a backup of your system before downloading and installing this UBF patch.
To revert to the original Prime Infrastructure 2.1 installation, follow these steps:
1. Reinstall Prime Infrastructure 2.1 from an OVA or ISO distribution.
2. Restore the data from the backup that you made before applying the patch.
Similarly, if you are running Prime Infrastructure 2.1 in a Virtual Machine (VM) and your organization permits taking VM snapshots, use the VMware client to take a VM snapshot before applying this patch. Store the snapshot in an external storage repository, and restore from the snapshot if the patch is unsuccessful.
If you are installing the patch as part of a High Availability (HA) implementation, you will want to ensure that the network links between the two servers provide maximum bandwidth and low latency throughout the patch install. For more information, see Troubleshooting Patch Installs in HA Implementations.
Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Patch.
If your current Prime Infrastructure implementation has High Availability enabled, follow the steps in Installing the Patch With High Availability instead of the steps below.
If you are currently using Prime Infrastructure without enabling High Availability, follow the steps below to install the patch.
Step 1 Point your browser to the software patches listing for Cisco Prime Infrastructure 2.1.
Step 2 Click the Download button for the Release 2.1.2 patch file (pi212_20141118_01.ubf), and save the file locally.
Step 3 Log in to the Prime Infrastructure server using an ID with administrator privileges and choose Administration > Software Update.
Step 4 Click Upload Update File and browse to the location where you saved the patch file. Click OK to upload the file.
Step 5 When the upload is complete:
a. On the Software Upload page, confirm that the Name, Published Date and Description of the patch file are correct.
b. Select the patch file and click Install.
c. You will see a popup message indicating that the installation is complete. You should also see a listing for the patch in the “Updates” table, with a “Yes” in the “Installed” column, and a “Yes” in the “Pending Restart” column.
Step 6 Restart the server by first executing the ncs stop command and then the ncs start command, as explained in Running Commands.
Step 7 Verify that the patch is installed by logging into the server and choosing Administration > Software Update. You should see a listing for the patch in the “Updates” table, with a “Yes” in the “Installed” column, and a “No” in the “Pending Restart” column.
Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Patch.
If you are not using the Prime Infrastructure High Availability (HA) feature, follow the steps in Installing the Patch instead of the steps below.
If your current Prime Infrastructure implementation has High Availability enabled, follow the steps below to install the patch. You must start the patch installation with the primary server in “Primary Active” state and the secondary server in “Secondary Syncing” state.
Patching of the primary and secondary servers takes approximately one hour. During that period, both servers will be down. If you have trouble at any point, see Troubleshooting Patch Installs in HA Implementations.
Step 1 Ensure that your HA implementation is enabled and ready for update:
a. Log in to the primary server using an ID with Administrator privileges.
b. Select Administration > System Settings > High Availability, The primary server state displayed on the HA Status page should be “Primary Active”.
c. Select HA Configuration. The current Configuration Mode should show “HA Enabled”.
d. The Failover Type must be set to “Manual” throughout the patch installation. If Failover Type is currently set to “Automatic”, select “Manual” and then click Save.
e. Access the secondary server’s Health Monitor (HM) web page by pointing your browser to the following URL:
where ServerIP is the IP address or host name of the secondary server.
f. You will be prompted for the authentication key entered when HA was enabled. Enter it and click Login.
g. Verify that the secondary server state displayed on the HM web page is “Secondary Syncing”.
a. Point your browser to the software patches listing for Cisco Prime Infrastructure 2.1.
b. Click the Download button for the Release 2.1.2 patch file (pi212_20141118_01.ubf), and save the file locally.
Step 3 Install the patch on the secondary server:
a. Access the secondary server’s HM web page by pointing your browser to the following URL:
where ServerIP is the IP address or host name of the secondary server.
b. You will be prompted for the authentication key entered when HA was enabled. Enter it and click Login.
c. Choose the HM web page’s Software Update link. You will be prompted for the authentication key a second time. Enter it and click Login again.
d. Click Upload Update File and browse to the location where you saved the patch file.
e. Click OK to upload the patch file.
f. When the upload is complete: On the Software Upload page, verify that the Name, Published Date and Description of the patch file are correct.
g. Select the patch file and click Install. When the installation is complete, you will see a popup message confirming this.
h. After the installation is complete on the secondary server, verify that the Software Updates page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the secondary server. Do not restart the secondary server at this point.
Step 4 Install the patch on the primary server:
a. Log in to the primary server using an ID with administrator privileges and choose Administration > Software Update.
b. Click Upload Update File and browse to the location where you saved the patch file.
c. Click OK to upload the patch file.
d. When the upload is complete: On the Software Upload page, verify that the Name, Published Date and Description of the patch file are correct.
e. Select the patch file and click Install. When the installation is complete, you will see a popup message confirming this.
f. After the installation is complete on the primary server, verify that the Software Update page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the primary server. Do not restart the primary server at this point.
Step 5 Stop the servers in the following sequence, using the commands explained in Running Commands:
a. On the secondary server, run the ncs stop command.
b. On the primary server, run the ncs stop command.
Step 6 Re-start and monitor the servers in the following sequence, using the commands explained in Running Commands:
a. On the secondary server, run:
– The ncs start command to restart the secondary server. Wait for the processes on the secondary to restart.
– The ncs status command to verify that the processes on the secondary have re-started.
– The ncs ha status command to verify that the secondary state is “Secondary Lost Primary”.
b. Once the secondary server is in “Secondary Lost Primary” state: On the primary server, run:
– The ncs start command to restart the primary server. Wait for the processes on the primary to restart.
– The ncs status command to verify that the primary’s Health Monitor and other processes have re-started.
Once all the processes on the primary are up and running, automatic HA registration will be triggered. This normally completes after a few minutes.
Step 7 Once registration completes, verify the patch installation as follows:
a. Run the ncs ha status command on both the primary and secondary servers. You should see the primary server state change from “HA Initializing” to “Primary Active”. You should see the secondary server state change from “Secondary Lost Primary” to “Secondary Syncing”.
b. Log in to the primary server and access its Software Update page as you did earlier. The “Installed” column should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.
c. Access the secondary server’s Health Monitor page as you did earlier. The “Installed” column should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.
You will need to connect to Prime Infrastructure server via the command line interface (CLI) to run commands that:
Before you begin, make sure you know the:
Step 1 Start up your SSH client, start an SSH session via your local machine’s command line, or connect to the dedicated console on the Prime Infrastructure physical or virtual appliance.
a. If you are connecting via a GUI client: Enter the ID of an active Prime Infrastructure administrator ID with CLI access, and the IP address or host name of the Prime Infrastructure server or appliance. Then initiate the connection.
b. If you are using a command-line client or session: Log in with a command like the following:
[localhost]#
ssh -I admin IPHost
– admin is an active Prime Infrastructure administrator ID with CLI access.
– IPHost is the IP address or host name of the Prime Infrastructure server or appliance.
c. If you are connecting via the physical or virtual appliance console, a prompt is shown for the administrator user name. Enter the user name.
Prime Infrastructure will prompt you for the password for the administrator ID you entered.
Step 3 Enter the administrative ID password.
Prime Infrastructure will present a command prompt like the following: PIServer/admin#.
Step 4 As an administrator, run the following commands from the CLI to start, stop, and check the server and HA status:
PIServer/admin#
ncs stop PIServer/admin#
ncs start PIServer/admin#
ncs status PIServer/admin#
ncs ha status Users who apply this patch 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-patch 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.
If you are unable to verify that the patch has been applied to a server, or one or both of the servers fails to re-start properly after the patch, you may need to re-image the server as explained in Before You Begin Installing the Patch 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.
If you are currently using Prime Infrastructure 2.1 or 2.1.1, you can apply the Prime Infrastructure 2.1.2 UBF patch.
If you are currently using Prime Infrastructure 2.0 you must first upgrade to Prime Infrastructure 2.1 before applying the Prime Infrastructure 2.1.2 UBF patch.
If you are running releases of Prime Infrastructure earlier than 2.0, first upgrade to Prime Infrastructure 2.1 and then apply this patch.
For detailed information about upgrading from previous releases of Prime Infrastructure, including the list of versions from which you can upgrade, see the Upgrading Cisco Prime Infrastructure section of the Cisco Prime Infrastructure 2.1 Quick Start Guide.
Your feedback will help us improve the quality of our product. To send your feedback, follow these steps:
Step 1 If you have configured your mail server, go to Step 8.
Step 2 Choose Administration > System Settings > Mail Server Configuration.
Step 3 In the Mail Server Configuration page, enter the mail server details.
Step 4 Click Save to save the configuration settings.
Step 5 Choose Help > Help Us Improve Cisco Products.
Step 6 In the Help Us Improve Cisco Products page, select the Yes, collect data periodically option.
Step 8 Choose Help > Submit Feedback (in the Classic view) or click the question mark icon at the top right and then click Submit Feedback (in the Lifecycle view). You must configure the email server and then enable data collection to configure the feedback tool.
For detailed information on Prime Infrastructure licensing, see the Cisco Prime Infrastructure 2.1 Ordering and Licensing Guide.
To see the list of devices supported in this release of Prime Infrastructure, follow these steps:
Step 1 Log in to Prime Infrastructure.
Step 2 Switch to the Lifecycle view (if applicable).
Step 3 Click the question mark icon (Help) at the top right.
Step 4 Click Devices Level Support.
Table 1 lists the wireless devices and their software versions that are supported by Prime Infrastructure 2.1
For detailed information on the software compatibility for the Cisco wireless devices, see the following URL:
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
Table 2 lists the Prime Infrastructure supported devices for switches, wireless LAN controllers, access point images, Identity Services Engines (ISEs), and mobility services engines (MSEs).
The following sections describe the Wireless LAN Controller software features that are not configurable in Prime Infrastructure Release 2.1.2 using the pre-packaged templates:
The following Wireless LAN Controller 8.0 software features are not configurable in Prime Infrastructure Release 2.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these features.
The following Wireless LAN Controller 7.6 software features are not configurable in Prime Infrastructure Release 2.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these features:
The following Wireless LAN Controller 7.5 software features are not configurable in Prime Infrastructure Release 2.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these features.
The following Wireless LAN Controller 7.4 software features are not configurable in Prime Infrastructure Release 2.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these features.
This release supports Cisco Aironet 1700 Series Access Points.
For more details on new features and enhancements, refer to Release Notes for Prime Infrastructure 2.1.1.
If you are unable to delete all unreachable devices using the Select All option at one time then retry the delete operation by selecting the unreachable devices.
Table 3 lists the Open Caveats in Prime Infrastructure Release 2.1.2.
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.
Note: All of the open caveats for Prime Infrastructure 2.1.1 are applicable to Prime Infrastructure 2.1.2. For the list of open caveats see the following URL:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1-1/release/notes/cpi_rn.html#pgfId-44304
Table 4 lists the resolved caveats in Prime Infrastructure Release 2.1.2. 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.
You can access additional Prime Infrastructure documentation at:
http://www.cisco.com/en/US/products/ps12239/tsd_products_support_series_home.html
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.