Category: Prime Infrastructure

Prime Infrastructure – the saga………

OK, this wasn’t quite as simple as i would have first thought but I got there in the end.

The version of Prime I was initially running was 2.0.0.0.39 and had to be upgraded before I could do a backup that would be compatible with 2.2.

I upgraded 2.0.0.0.39 >> version 2.1 by downloading PI-Upgrade-2.1.0.0.87.gz from Cisco.com (from the below location)

pi2

Once downloaded I dropped the file onto my FTP Server.  This can be viewed from the PI Server by running the show repository ftpserver

First stop NCS by running ncs stop then run the following command:

application upgrade PI-Upgrade-2.1.0.0.87.gz ftpserver

This takes a while and at the end you will recieve a message ‘Application upgrade successful’, then you can restart NCS – ncs start

Once complete you can then backup your PI Server (using the Backup/Restore procedure) including configuration but most importantly all your historical data.

Then you can restore the PI-Backup to your new 2.2 instance of Prime 🙂 using the following command:

restore PIBackup-xxxxxx-xxxx.tar.gpg repository ftpserver application NCS

……..2hr:44m’s later she’s alive.

Prime Infrastructure – Backup/Restore

Project ‘Upgrade Cisco Prime’, requires i backup the Database using the below commands.

Cisco Prime Infrastructure 2.2 Admin Guide

Step 1  Open a CLI session with the Prime Infrastructure server (see Connecting Via CLI).

Step 2  Enter configuration mode:

PIServer/admin# configure terminal

Step 3  Configure a symbolic link to the remote FTP server:

PIServer/admin(config)# repository repositoryName

PIServer/admin(config-Repository)# url ftp:// RemoteServerIP (needs to be an IP address)

PIServer/admin(config-Repository)# user userName password plain userPassword

PIServer/admin(config-Repository)# exit

PIServer/admin(config)# exit

Where:

  • repositoryName is the name of the repository (for example: MyRepo or PrimeInfrastructure).
  • RemoteServerIP is the IP address of the FTP server hosting the shared backup folder.
  • userName is the name of a user with write privileges to the repository on the FTP server.
  • userPassword is the corresponding password for that user.

Step 4  Verify creation of the symbolic link:

PIServer/admin# show repository repositoryName

Step 5  When taking backups at the command line, specify the new remote FTP repository as the repository name in the backup command. For example:

PIServer/admin# backup MyBackupFileName repository MyRepo application NCS

If you want to perform backups automatically, select the repository name you created as the repository name in the Prime Infrastructure web interface.

Maintaining Prime Infrastructure Server Health