Cisco Prime Network Installation Guide, 4.2

Supported Prime Network Upgrade and Rolling back versions

Refer the following table for supported Prime Network Upgrade and rolling back versions.

Table 11-3 Supported Prime Network Upgrade and Rolling back versions

Upgrading from RHEL 6.4 with PN 4.1 to RHEL 6.5 with PN 4.2 and Oracle 12

To upgrade from RHEL 6.4 with PN 4.1 to RHEL 6.5 with PN 4.2 and Oracle 12, follow the procedure provided below:

Step 1 Upgrade to PN 4.2 using Prime_Network_upgrade directory from Disk 5 to the temporary upgrade directory you created. See Upgrading to Prime Network 4.2 from 4.0 and 4.1 (Intermediate Steps).

Step 2 Upgrade embedded Oracle 12 using the embedded_upgrade_12.1.zip file from Disk 5. See Upgrading the Embedded Database to Oracle 12.1.0.

Step 3 Upgrade the RHEL 6.4 to 6.5 using In-line upgrade with latest Open ssl package. Contact your System Admin for RHEL in-line upgrade.

Step 4 After upgrading the RHEL, login with PN user and verify the web server status and the compliance engine status.

Step 5 Login as PN user and restart AVM11 using $ANA_HOME# anactl restart -avm 11.

Note If you have Unit server attached with Gateway, first upgrade the Gateway as mentioned in the above steps, and Upgrade the RHEL version 6.5 in the Unit server with the latest Open ssl package by using the In-line upgrade.

Upgrading from RHEL 5.5 - 5.8 to RHEL 6.5 with PN 4.2 and Oracle 12

Upgrading from RHEL 5.5-5.8 to 6.5 consists of upgrading to PN 4.2 on a local RHEL 5.5-5.8 system, backing up the database, and saving it to a different location. After which, you need to re-image the system with RHEL 6.5, reinstall the PN 4.2, and restore the previous database from the location where you saved it.

Note If you have RHEL 5.8 and do not wish to re-image to RHEL 6.5, you can continue to upgrade PN 4.2 with RHEL 5.8

To upgrade RHEL from 5.5, 5.6, 5.7, and 5.8 with lower version of prime network to RHEL 6.5 with PN 4.2 and Oracle 12, follow the steps provided below:

Step 1 Note down the PN Username and Password, and Oracle username and Database profile that you had selected while installing PN lower version.

Step 2 Upgrade to PN4.2 from PN lower version using Prime_Network_upgrade directory from Disk 5. See Upgrading to Prime Network 4.2 from 4.0 and 4.1 (Intermediate Steps).

Step 3 Upgrade embedded Oracle 12 using the embedded_upgrade_12.1.zip file from Disk 5. See Upgrading the Embedded Database to Oracle 12.1.0.

Step 4 Login as Prime user and Backup the Embedded oracle database $ ANAHOME/Main/scripts/embedded_db# emdbctl --backup. Please refer PN 4.2 Admin guide for knowing how to back up the Gateway data and the Embedded Database.

Note If you have operations reports in Gateway, Uninstall it before performing PN Database backup.

Step 5 Copy the latest backup folder in $ ANA_HOME/backup# to your local server (for example, other than the server you are currently using).

Step 6 Re-image the Gateway server to RHEL 6.5. If you have a Unit server attached in the Gateway, re-image the Unit server to RHEL6.5.

Step 7 Install the PN4.2 Gateway, Oracle 12 and the Unit server. If you have unit Gateway setup in PN lower version, use the PN Username and Password, and Oracle username and Database profile that you had chosen while installing PN Gateway lower version.

Note If you have installed the embedded Oracle in remote server for PN lower version, install embedded database 12 on the same server for PN 4.2.

Step 8 Once installation is complete, login as a Prime user, back up the Prime network Gateway data and embedded database $ ANAHOME/Main/scripts/embedded_db # emdbctl --backup . Please refer PN 4.2 Admin guide to know more on how to back up the Gateway data and the embedded database.

Step 9 Navigate to $ANA_HOME/backup location, and remove the back up file folder in the location.

Step 10 Paste the backup file folder which you already have in your local machine to the location $ANA_HOME/backup.

Step 11 Provide the group owner permissions to the backup file directory and its contents as follows:

chown - R pnuser: pngroup directory_name. Example: chown -R pn40:ana 201503101439

Step 12 Login as Prime user and restore the embedded database with Prime network gateway data by using the command $ ANAHOME/Main/scripts/embedded_db # emdbctl --restore . Please refer PN 4.2 Admin guide to know more on how to restore the gateway data and the embedded database.

Step 13 Once the restoring process is completed, check the status of PN.

Step 14 Ensure that the status of both compliance engine and web server is up.

Step 15 Start the Unit server as a Prime user using the command $ ANA_HOME# anactl start, if it is attached with the Gateway.

Step 16 Restart the PN as Prime user using the command $ ANA_HOME# anactl restart.

Upgrading PN-IL in Standalone Mode

Before You Begin

Perform these tasks as pnuser:

• Disable the health monitor to disable the PN-IL services permanently otherwise the services will start automatically after a delay of 3 minutes.

• Back up the $PRIMEHOME directory.
• Stop the PN-IL using the following command:

To upgrade a standalone PN-IL:

Step 1 As the root user, launch a terminal on the Prime Network gateway server where you want to install PN-IL.

Step 2 Insert Disk 5: Installation and Upgrade in the DVD drive.

Step 3 Mount the inserted DVD using mount and move to the mount location.

Step 4 Log in as pnuser :

Step 5 Create a temporary PN-IL upgrade directory.

Step 6 Copy the PN-IL upgrade tar file from the mount location to the pnilupgrade directory.

Step 7 Navigate to the directory in which the tar file was copied and extract the PN-IL upgrade tar.

Step 8 Navigate to the extracted files directory.

Step 9 Run the upgrade script

Step 10 Enter yes at the prompt to continue the upgrade process. The upgrade process is completed and the log files can be located at $PRIMEHOME/upgrade/1.0.0.0-1.3.0.0/upgrade.log.

Step 11 Perform the following post-upgrade tasks:

a. As pnuser, reload the user profile:

b. Configure the PN-IL in standalone mode:

c. Start the PN-IL:

d. Enable the health monitor:

Upgrading PN-IL in Suite Mode

If you have been working with Prime Network 4.2, you will have PN-IL 1.3 installed on your system. The procedure for upgrading to PN-IL 1.3 in suite mode is the same as upgrading in standalone mode. See Upgrading PN-IL in Standalone Mode.

If you have been working with a release prior to Prime Network 4.0, follow the instructions below to upgrade to PN-IL 1.3.

Step 1 Upgrade PN-IL in standalone mode as described in Upgrading the Prime Network Integration Layer (PN-IL).

Step 2 Perform these tasks on the Prime Central Server to create a backup of the PN-IL configuration data.

a. Log in to the Prime Central server as root.

b. Create Prime Central upgrade directory

c. Copy the PN-IL upgrade tar file (example: PNIntegrationLayerUpgrade_1.0.0.0-1.3.0.tar.gz) from the upgrade directory on the Prime Network server to the upgrade directory on the Prime Central server.

d. Extract the files.

e. Run the PN-IL upgrade utility script to create a backup tar file in $PRIMEHOME/backup.

Step 3 Perform these tasks on the Prime Network server to restore the PN-IL configuration.

a. As pnuser, copy the backup tar from the Prime Central upgrade directory to Prime Network server.

b. Extract the files:

c. Run the PN-IL utility script to restore the PN-IL configuration:

Step 4 Perform these tasks on Prime Central as described in C isco Prime Central Quick Start Guide, 1.4

• Upgrade Prime Central
• Integrate Prime Network and PN-IL with Prime Central

Step 5 Start the upgraded PN-IL:

$PRIMEHOME/bin/itgctl start

Enable Units to Restart Automatically After they are Rebooted

After upgrade, you need to perform the following steps on each unit in your setup otherwise the units will not restart automatically after they are rebooted.

Step 1 Log into the unit as pnuser.

Step 2 Copy rootdeploy.cmd from the gateway, as follows:

Step 3 Switch to the root user:

As the root user, execute the rootdeploy command:

Restoring Customized Crontabs

If you saved user-defined cron jobs in NETWORKHOME /local/cron/crontab.user.list, they are restored. User-defined cron jobs that are not placed in this directory must be manually recreated.

Restarting Crontab Jobs for NAT Units

Cron jobs on NAT units must be manually restarted.

Step 1 Log into the unit as pnuser.

Step 2 Copy the upgrade_restart_crons.pl script from the gateway, as follows:

Step 3 Run the upgrade_restart_crons.pl script. It will display output similar to the following:

Step 4 Verify that the crontab list is not empty:

Step 5 The upgrade is now complete. Run the status command and check the version number to make sure that the upgrade has been successful.

Fixing the Database Entry for Vision Clients with NAT

If you are using network address translation (NAT) with the Prime Network Vision client, update the database host in the Prime Network registry to contain the hostname instead of the IP address.

If you already use a hostname instead of an IP address, you do not have to repeat this procedure.

Step 1 Make sure Prime Network is running.

Step 2 Verify that the client workstations have the correct Domain Name System (DNS) mapping.

Step 3 From NETWORKHOME/Main, run the following commands:

Step 4 Enter the following command to restart Prime Network:

Updating the Port Watchdog (AVM Protection) Scripts

After upgrading to Prime Network 4.2, copy the port watchdog scripts to /var/adm/cisco/prime-network/scripts. Enter the following commands as the root user:

Restore Links Between Devices and Cloud VNEs

If your deployment had cloud VNEs that were connected to devices with static links, the connection between the cloud VNE and the device may be lost after the upgrade. Delete and recreate the link using the Administration GUI.

Support for Third-Party VNEs

Prime Network supports third-party devices through Cisco Advanced Services engagement. As of release 4.2, Prime Network will not natively support third-party devices, and a Cisco Advanced Services contract will be required for their enablement and support.

Command Builder Scripts

If you had customized Command Builder scripts (which you should have uninstalled), you may need to update your scripts if your deployment:

• Executes command scripts using the Prime Network northbound APIs (for example, BQL)
• Includes references to IMOs or to the Prime Network internal model

Verify whether the command names, parameters, or IMO references have changed, in which case you must update your scripts. The reinstall your customized scripts.

Gathering DB Statistics in First 24 Hours

The pnuser _admin user performs maintenance tasks—such as gathering statistics—on the other Prime Network database schemas. After this user is created, a cron job runs every 24 hours to gather statistics on the Fault Database tables.

However, if you expect a high scale in the first 24 hours, you might need to manually force statistics gathering twice during the first day, 1 and 5 hours after noise start. To force statistics gathering, enter the following UNIX command as pnuser :

If you deploy Prime Network to handle a high event rate, disabling Oracle’s automatic maintenance jobs is recommended. Automatic maintenance significantly affects Oracle performance and increases event processing time. See Disabling Automatic Maintenance Jobs.

Integration Changes

For details on BQL and other integrations after the upgrade, refer to the Cisco Developer Network at https://developer.cisco.com/site/prime-network/.

Example-Upgrading the Embedded Database to Oracle 12.1.0

Step 1 In the database server, perform the following steps:

a. Unzip the embedded_upgrade_12.1.zip to /tmp/upg12c by entering the following command:

b. Copy the following two zip files to /tmp/upg12c.

– linuxamd64_12c_database_1of2.zip

– linuxamd64_12c_database_2of2.zip

c. Create the staging directory by entering the following commands:

d. Upgrade to Oracle 12.1.0 by entering the following command:

Step 2 Enter the required information as shown in the following table.

Step 3 Navigate to /export/home/oracle/product/12.1.0/db_1/network/admin/listener.ora, and update oracle_home=/export/home/oracle/product/12.1.0/db_1

Step 4 Login to Oracle, and restart the embedded Oracle by following command:

#lsnrctl stop

#lsnrctl start

Example-Upgrading the Embedded Database to Oracle 12.1.0 in a HA Setup with Geographical Redundancy and Oracle ADG

Step 1 Stop the Prime Network.

Step 2 Verify if the replication between databases work.

Step 3 In the STANDBY database server, perform the following steps:

a. Navigate to the location where the embedded Oracle software is available.

b. Unzip the embedded_upgrade_12.1.zip to a location /tmp/upg12c by entering the following command:

c. Copy the two zip files to /tmp/upg12c:

– linuxamd64_12c_database_1of2.zip

– linuxamd64_12c_database_2of2.zip

d. Create the staging directory by entering the following commands:

e. Upgrade to Oracle 12.1.0 by entering the following command:

Step 4 In the PRIMARY database server, perform the following steps:

a. Navigate to the location where the embedded Oracle software is available.

b. Unzip the embedded_upgrade_12.1.zip to /tmp/upg12c by entering the following command:

c. Copy the two zip files to /tmp/upg12c:

– linuxamd64_12c_database_1of2.zip

– linuxamd64_12c_database_2of2.zip

d. Create the staging directory by entering the following commands:

e. Upgrade to Oracle 12.1.0 by entering the following command:

Step 5 In the STANDBY database server, perform the following steps:

a. Enter the following command:

b. Upgrade the Oracle version by entering the following command: