The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can upgrade to the 12.1 virtual appliance from any of the following version: 11.0, 11.1, 11.1.1, and 12.0.
To upgrade to Cisco Prime Service Catalog Virtual Appliance 12.1, you must perform a migration process rather than an in-place upgrade. This is because many third-party components have changed in version 12.1, such as the Operating System, RabbitMQ and so on. Therefore, you must deploy a new 12.1 virtual appliance prior to migrating the existing virtual appliance. For instructions to deploy Cisco Prime Service Catalog Virtual Appliance 12.1, see Installing Prime Service Catalog Virtual Appliance.
At a high level, the upgrade procedures are as follows:
Step 1 |
Disable the UCS Director automatic polling flag. This setting should be disabled on the previous Prime Service Catalog virtual appliance set up. |
Go to Administration > Settings and disable the UCSD Scheduler option. |
Step 2 |
Back up the database on the previous virtual appliance. |
See Backing up the Database on Previous Cisco Prime Service Catalog Virtual Appliance |
Step 3 |
Install a new 12.1 Virtual Appliance. |
|
Step 4 |
Retrieve Remote Backup of Prime Service Catalog Database |
|
Step 5 |
Upgrade the database from previous virtual appliance to 12.1 virtual appliance. You can either manually copy the database from the backup in Step 2 or you can let the system copy it from the remote location using the shell menu option. |
|
Step 6 |
Perform the post upgrade steps to complete the upgrade/migration process. |
Note | If you plan to use your own database and choose not to install the database node. You can download the factory default dump CPCSUSER__factory_default.dmp from the cisco.com website and import the dump into your Oracle 12c database instance. For more information on Importing, see Exporting Cisco Prime Service Catalog Schema and Importing to the External Oracle Database. |
Install the 12.1 virtual appliance. For more information, see Installing Prime Service Catalog Virtual Appliance
Step 1 | Back up the database. For detailed procedure, see section Backing up the Database on Previous Cisco Prime Service Catalog Virtual Appliance. |
Step 2 | Login as the root user on the Prime Service Catalog 12.0 Virtual Appliance. |
Step 3 | Go to the
Oracle Backup Directory by executing the following command:
cd /opt/cisco/.backups/oracle/cpscuser |
Step 4 | Execute the
following command to copy the backup files from previous Virtual Appliance to
the external Oracle database:
scp CPSCUSER_backup_<timestamp>.dmp root@{IP_of_external oracle database}:/<external oracle directory> |
Step 5 | Enter the password of the external oracle database. |
Step 6 | Execute the
following command on the external oracle to create the directory in the
external oracle database by logging in as system user:
SQL> create or replace directory CPSC_BACKUPS as ‘opt/cisco/.backups/oracle/cpscuser’ |
Step 7 | Execute the
following command on the external oracle to verify the location of the dump
file in the specified directory:
SQL> select directory_name,directory_path from dba_directories |
Step 8 | Execute the
following command on the external oracle to import the backup files:
impdp <systemuser>_schemas=cpscuser directory=CPSC_BACKUPS dumpfile=CPSCUSER_backup_<timestamp>.dmp |
You can either manually copy the database from the backup or you can let the system copy it from the remote location using the shell menu option. Follow the automated method if you want system to copy the database files from a remote machine. Choose the manual method if you want to manually copy the database from some location to your local folder.
This option is used to retrieve backup of Prime Service Catalog database hosted on a remote server, using SSH connection.
If you have already performed the steps to retrieve the backup of the prior virtual appliance, skip this procedure. Otherwise, use the following procedure to manually copy the database files from a local folder to the desired location.
Command or Action | Purpose | |
---|---|---|
Step 1 | Login as the root user on the 12.1 Virtual Appliance. | |
Step 2 | Go to the Oracle Backup Directory by executing the following command: |
cd /opt/cisco/.backups/oracle/cpscuser |
Step 3 | Execute the following command to copy the backup files from previous Virtual Appliance to the new 12.1 Virtual Appliance: |
scp root@{IP_of_11.1_VA}:/opt/cisco/.backups/oracle/cpscuser/CPSC_11.1_backup.dmp. |
Step 4 | Change the backup file ownership and permissions: |
chown oracle.oracle CPSCUSER_11.0_backup.dmp
chmod a+r CPSCUSER_11.0_backup.dmp |
Upgrade to the latest Virtual Appliance database. For more information, see Upgrading the Cisco Prime Service Catalog Virtual Appliance.
In case the
backup files are located in another location follow the procedure in section
Retrieving Backup of Prime Service Catalog Database
to copy the back up file to a local folder.
Step 1 | Login to the Virtual Appliance as the shelladmin user and the password that you had provided while Installing Prime Service Catalog Virtual Appliance 12.1. Once logged in, you will see the Shell Menu. | ||
Step 2 | Select
. You will be prompted for the following
values:
| ||
Step 3 | Update the
python packages on the database and application nodes.
If you need access to the repository that contain the Cisco VA patch files on cisco.com, follow the steps in the section Requesting Access to Repository. | ||
Step 4 | Select Do you want to proceed:Enter y to proceed with the database upgrade. from the Prime Service Catalog node. You will be prompted for the following values: | ||
Step 5 | Ensure database upgrade was successful. |
Perform the post upgrade steps to complete the upgrade/migration process. For more information, see Performing the Post-upgrade Tasks.
Step 1 |
Log in to the Service Catalog application as a Site
Administrator user.
|
Step 2 | Update UCSD users, groups, infrastructure templates, containers. |
Step 3 | (Optional)
This step is applicable only if the Docker app was used in 11.0. After the
upgrade, select an application template with Docker software, click on the
software and do the following:
|