Cisco Cisco Prime Infrastructure 2.2
4
Readme for Data Center Technology Package 1.0.1 for Cisco Prime Infrastructure 2.2.3
Data Center Technology Package Installation
Step 8
You can verify the package installation from Prime Infrastructure Login page under Prime Add-Ons 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 package in the
Updates tab, with “Installed” in the Status column.
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 package in the
Updates tab, with “Installed” in the Status column.
Installing the Technology Package in High Availability Mode
Download the Data Center Technology Package Datacenter_Technology_Pack-1.0.53.ubf from
and save the package file in your local storage
.
To install the downloaded Data Center Technology Package Datacenter_Technology_Pack-1.0.53.ubf
in High Availability mode follow the below steps:
in High Availability mode follow the below steps:
•
Make sure you have completed the recommended preparation steps given in
•
If your current Prime Infrastructure implementation has High Availability (HA) servers that are not
at the same patch level, see
at the same patch level, see
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
servers are not at the same patch level, see
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 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
to restart properly after the package installation, you may need to re-image the server as explained in
.
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
in Command Reference Guide for Cisco
Prime Infrastructure 2.2.