Manualsbrain.com
  1. Manuals
  2. Brands
  3. Cisco
  4. Cisco Prime Infrastructure 2.0
  5. Installation Guide

Cisco Cisco Prime Infrastructure 2.0 Installation Guide

Download
Page of 32
20
pnp-server/admin# configure
Enter configuration commands, one per line. End with CNTL/Z.
pnp-server/admin(config)# repository <repository_name>
pnp-server/admin(config-Repository)# url ftp://<SERVER_HOST_NAME>/<FOLDER_LOCATION>
pnp-server/admin(config-Repository)# user <USER_ID> password <OPTION> <PASSWORD>
pnp-server/admin(config-Repository)# exit
pnp-server/admin(config)# exit
pnp-server/admin#
pnp-server/admin# patch install pnp-gateway-patch-2.0.0.28.tar.gz
pnp-patching-<VERSION>.tar.gz <repository_name>
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Patch installation...
Patch successfully installed
pnp-server/admin#
pnp-server/admin# pnp setup
Migrating to a New System
System migration is the preferred option for most upgrades of production installations. In most cases, you will need to supply 
new server hardware to complete the migration. 
Note that, to use this path, you must be migrating from one of the release levels listed in 
, and have installed the required backup and restore patches listed in 
.
Step 1
Before you begin, remove any existing High Availability configuration from your primary and secondary Prime 
Infrastructure servers. You can do this using either of the following options:
•
Launch Prime Infrastructure, choose Administration > High Availability > HA Configuration, and click Remove.
•
Go to admin console and run the ncs ha remove command.
Step 2
If you have not already done so: Set up a remote backup repository for the old host. For details, see 
 in the Cisco Prime Infrastructure 2.0 Administrator Guide.
Step 3
Take an application backup of the old host on the remote repository. For details, see 
 in the Cisco Prime Infrastructure 2.0 Administrator Guide
Step 4
Install the new host as explained in 
Step 5
Configure the new host to use the same remote backup repository as the old host.
Step 6
Restore the application backup on the remote repository to the new host, as explained in 
 in the Cisco Prime Infrastructure 2.0 Administrator Guide.
Step 7
When the upgrade is complete: 
•
Instruct users to clear the browser cache on all client machines that accessed an older version of Prime 
Infrastructure before they try to connect to the upgraded Prime Infrastructure server.
•
If you run into problems creating a backup after you have upgraded to version 2.0, see 
•
If you were using external AAA (RADIUS or TACACS) before the upgrade, see