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.
The following topics tell you how to install and start Cisco Prime Performance Manager, and also how to verify the installation.
Install Prime Performance Manager in the following order. Many steps are partially or fully automated.
1. Downloading and Extracting the Prime Performance Manager Software
Prime Performance Manager uses separate gateway and unit installation scripts. If you install the gateway and unit on the same server, the gateway script runs first, then the unit script.
If you are installing Prime Performance Manager in a gateway HA environment, go to Installing Prime Performance Manager on High Availability Gateways and following the installation flow in that section.
Before you install Prime Performance Manager, verify that:
You can get the Prime Performance Manager 1.7 software in one of two ways. You can either download the evaluation version from Cisco.com or the licensed software version from the DVD. If you downloaded the complete Prime Performance Manager nonevaluation software image it will be named:
ppm170-cd-linux-2015- mmdd -k9-full-fcs.zip
If you are installing Prime Performance Manager 1.7 from the software DVD, go to the Starting the Installation. To download and extract the Prime Performance Manager 1.7 zip file:
Step 1 Log into the server as root.
If you are already logged in, but not as the root user, use the su command to change your login to root:
root-password
Step 2 Create (or use an existing) directory where you can unzip the Prime Performance Manager 1.7 zip file. You can extract the file into any disk partition with enough space to contain the downloaded zip file and the extracted image. You will need 900 MB for the full extracted image and the zip file.
Note Do not use the /tmp directory for the temporary unzip location. Using the /tmp directory can cause unexpected results.
Step 3 To download the Prime Performance Manager upgrade software:
a. Log into the Cisco Prime Performance Manager website:
http://www.cisco.com/go/performance
b. At the bottom of the page, click Try Cisco Prime Performance Manager.
c. In the Downloads area Find box, enter Cisco Prime Performance Manager 1.7.
d. In the Download Software page, click Download Now next to the appropriate Release 1.7 upgrade software module:
– ppm170-cd-linux-upgrade-k9-fcs.zip—1.x upgrade installation for Linux servers.
e. On the Download Cart confirmation page, click Proceed With Download and download the file to the directory specified in Step 2.
Step 4 To download the Prime Performance Manager 1.7 evaluation software:
a. Log into the Cisco Prime Performance Manager website:
http://www.cisco.com/go/performance
b. Scroll to the bottom of the Cisco Prime Performance Manager page and click Try Cisco Performance Manager.
c. In Welcome to Cisco Promotional Store page, click Cisco Prime Performance Manager (PPM) 1.7. Linux.
d. Proceed through the checkout cart. At the end, you will download one of the following evaluation zip files to In the Download Software page, click Download Now next to the appropriate Release 1.7 upgrade software module:
– ppm170-cd-linux-2015- mmdd -k9-eval-fcs.zip—Evaluation installation for Linux servers.
Step 5 Unzip the Prime Performance Manager 1.7 file:
Where ppm170zipfile is the file you downloaded in Step 3 or Step 4.
Step 6 Continue with the Starting the Installation.
Complete the following steps to install:
Note To install Prime Performance Manager in a high availability configuration, go to Installing Prime Performance Manager on High Availability Gateways.
During the installation, the Prime Performance Manager installer prompts you for a response and displays the default value for each prompt in square brackets [ ]. To accept the default value, press Enter.
To install a Prime Performance Manager gateway and/or unit:
Step 1 Enter one of the following:
Software on DVD: insert the DVD, then enter:
Step 2 Enter one of the following:
The installer checks for the gateway and unit installation, then displays the installation menu:
Step 3 Enter the installation option.
Note For Options 5, 6, and 7, see Installing Prime Performance Manager on High Availability Gateways. For option 8, see “Integrating Prime Performance Manager with Prime Central” in the Cisco Prime Performance Manager 1.7 User Guide.
Gateway and Unit or Gateway Only Installation
Note If you selected option 4 (unit only), go to Unit Installation.
If you selected Option 2 (gateway and unit) or 3 (gateway only), the installer displays information similar to the following:
The installer checks your system to ensure that all requirements are met. Information similar to the following appears:
If any requirement is missing, a warning message appears. For a list of all system requirements, see Evolved Programmable Networks Requirements.
Next, the installer checks the TCP/IP addresses. Information similar to the following appears:
If multiple IP addresses are configured on the Linux server, you are prompted to bind the server to a specific IP address during the installation. This prompt appears during the TCP/IP Address Check.
For example, The Gateway must bind to a specific IP address. Available IP addresses. xx.yy.zz.ww, aa.bb.cc.dd. Enter IP address to bind server to: nnn.nnn.nnn.nnn.
Next, the installer checks the TCP/IP port usage. Information similar to the following appears:
The installer displays the gateway summary information and prompt:
Prime Performance Manager checks the disk space to determine whether adequate space in the.../opt default installation directory to install gateway. Information similar to the following is displayed:
If space is available, installation continues. If not, the installer prompts you to specify a different directory, then continues the installation. If your system meets all requirements, the installer displays the following information and prompt:
Express Install uses all the default settings. It minimizes system prompts and installs Prime Performance Manager in the.../opt directory.
Step 5 Select an installation option:
The installer prompts you to enter the directory name and TCP port number for the web server, JSP server, and naming server. The installer displays prompts, similar to the following:
– Where should the product be installed ? [/opt]
– Which tcp port should JSP Server use [4470] ?
– Which tcp port should Naming Server use [45742] ?
If you chose the Express installation, the installer displays the following messages and prompt:
Step 6 Press Enter to accept the default, or enter a different SNMP read community string.
The following messages and prompt appear:
Step 7 Enter y to add user with the required access role, or n to add user access later. (For information on enabling user access, see the Cisco Prime Performance Manager 1.7 User Guide.) If you enter y, the following is displayed:
If you enter n, the following is displayed:
See Client Requirements for the supported browsers to launch Prime Performance Manager.
The installer completes gateway installation and displays the following message:
Step 8 If you do not want to view the log, press Enter. To view the log, enter y, press Enter, then press the spacebar to scroll through the log.
If you chose to install only the gateway in Step 3 (Option 3) continue with .
If you chose to install both gateway and unit (Option 2), the unit installation begins automatically. If you selected unit only (Option 4), the installer displays information similar to the following:
The installer checks the system to ensure that all requirements are met. Information similar to the following appears:
If any requirement is missing, a warning message appears. For a list of all system requirements, see Evolved Programmable Networks Requirements.
The installer checks the TCP/IP addresses. Information similar to the following appears:
If multiple IP addresses are configured on the Linux server, you are prompted to bind the server to a specific IP address. For example:
The Unit must bind to a specific IP address. Available IP addresses. xx.yy.zz.ww, aa.bb.cc.dd. Enter IP address to bind server to: xx.yy.zz.ww.
The installer checks the TCP/IP port usage. Information similar to the following appears:
The installer displays the following unit summary information:
The installer checks the disk to ensure adequate space in the.../opt default installation directory is available to install the unit. It displays information similar to the following:
If space is adequate, installation continues. If the space is not adequate, the installer prompts you to specify a different directory, then continues the installation.
The Express Install option uses default settings, minimizing system prompts, and places the Cisco Prime Performance Manager in the /opt directory.
If space is available, installation continues. If not, the installer prompts you to specify a different directory, then continues the installation. If your system meets all requirements, the installer displays the following information and prompt:
Express Install uses all the default settings. It minimizes system prompts, and installs Prime Performance Manager in the.../opt directory.
Step 10 Select an installation option:
The installer prompts you to enter the directory name and TCP port number for the web server, JSP server, and naming server:
– Where should the product be installed ? [/opt]
– Which tcp port should JSP Server use [5470] ?
– Which tcp port should Naming Server use [55742] ?
If you chose the Express installation, the following messages and prompt appear:
Note If you installed the unit on a different server than the gateway, you are prompted to enter the IP address or hostname of the gateway server and the RMI port.
After the unit is installed, the following message appears:
Step 11 If you do not want to view the log, press Enter. To view the log, enter y, press Enter, then press the spacebar to scroll through the log.
Step 12 At the Set Superuser prompt, indicate whether you want to assign a non-root OS user as the Prime Performance Manager superuser. If no, press Enter and continue with the next step. To set a non-root user as the superuser, enter Y, press Enter, and enter the user. You can:
Note If you plan to integrate Prime Performance Manager with Cisco Prime Central, do not set up the superuser at this time. You must be the root user to run the Prime Central integration. For information about integrating Prime Performance Manager with Prime Central, see the “Integrating Prime Performance Manager with Prime Central” procedure in the Cisco Prime Performance Manager 1.7 User Guide.
========================================================================
===============================Set superuser============================
========================================================================
Prime Performance Manager by default will be run as the root user
Do you want to run Prime Performance Manager as a non-root user (y/n)? [N]
After you respond to the Set Superuser prompt, Prime Performance Manager runs commands and displays the output, after which, the Startup Options appear:
Note The displayed startup options depend on the installation option you chose. For example, if you installed just the gateway, only the Start Prime Performance Manager Gateway, Integrate with Prime Central, and Exit Setup options are displayed. If you installed just the unit, only the Start Prime Performance Manager Unit and Exit Setup options are displayed.
Step 13 Choose a startup option:
Note If you exit the setup without starting Prime Performance Manager, you can start Prime Performance Manager later. See Starting Prime Performance Manager Using the CLI.
If you chose to start the gateway and unit, the installer starts the gateway and displays messages similar to the following:
After the installation is completed, the following message appears:
If you install gateways and units across a firewall, you must change the ports shown in Table 2-1 . You can change the ports in properties/ System.properties.
|
|
|
|
---|---|---|---|
The Apache web server is no longer used. The Tomcat JSP server works as the web server also. However, if you changes these ports, set WEB_PORT to the same value as JSP_PORT.
– If you specify 0, Prime Performance Manager uses any available port, 1024 and above.
– If you specify the CLIENT_PORT on a gateway with a single value other than 0, such as 33459, Prime Performance Manager uses that port for the unit to connect to the gateway. You only need to specify one port on a unit because the unit can connect to only one gateway.
– If you specify the CLIENT_PORT on a gateway with a range of values other than 0, such as 33459-33479, the port can use any of the ports in the range, including the beginning and ending ports, and you can run more than one unit at a time.
If a firewall exists between clients and the gateway, the JSP_PORT is the only port you need to open for client-to-gateway communication. This includes both non-SSL and SSL-based deployments. JSP_PORT is set to 4440 by default. You can change it at installation or by using the ppm jspport command.
Note The ppm webport and ppm jspport commands both change the JSP_PORT and WEB_PORT and set them to the same values.
If units and devices must communicate across a firewall, open SNMP Port 161. If using reports that require SSH or Telnet communication, such as Y.1731, EVC, or other CLI-based reports, open the SSH or Telnet ports between the units and devices as specified in the Telnet/SSH tab under Administration. The default Telnet port is 23, and the default SSH port is 22. You do not need to open the SNMP trap Port 162 between devices and the units because Prime Performance Manager does not process SNMP traps from devices.
You can install Prime Performance Manager in local and geographical HA environments. Installation procedures are provided in the following topics:
To install Prime Performance Manager in a gateway local HA environment, Prime Performance Manager binaries are installed in the SAN storage where they are shared by the primary and secondary gateways. Installation is performed at each gateway, but the install packages in the secondary gateway are not used. The installer only installs the files needed by the gateway, such as cron jobs and RPM information, as well as software needed to run, upgrade, or uninstall Prime Performance Manager in the secondary gateway. Figure 2-1 provides an overview of the gateway local HA installation architecture.
Figure 2-1 Local HA Installation Architecture
When planning for a Prime Performance Manager gateway local HA installation, keep the following points in mind:
The general process for mount device access is:
– Run ppmGatewayHA.sh freeze to freeze the service.
– Complete the work, for example, stop or restart Prime Performance Manager.
– When finished, leave the mount devices directories and run ppmGatewayHA.sh unfreeze to unfreeze the service.
For more information, see the “Freezing and Unfreezing RHCS” in the Cisco Prime Performance Manager 1.7 User Guide.
Before you begin the Prime Performance Manager local HA gateway installation:
In some scenarios, for example, if Prime Performance Manager 1.7 DVD image with Prime Performance Manager 1.7.0 SP1are available and you want to deploy Prime Performance Manager 1.7.0 SP1703 Local HA on RHEL 6.8 or RHEL 6.9, perform the following steps to overcome the limitation on earlier Prime Performance Manager installation packages version:
a. Unzip Prime Performance Manager 170 SP1 packages both on the primary gateway and the secondary gateway.
b. Modify the validateSytem.sh script under the unzipped folder to add your OS number.
The current Linux OS is RHEL 6.10, search for checkOSCPU4GWHA() in validateSystem.sh script and add as specified below:
“5.5”|”5.7”|"5.8"|"5.9"|"5.10"|"6.10"
c. Install Prime Performance Manager 170SP1 Local HA mode on SAN storage on the primary gateway and install Prime Performance Manager 170SP1 on the local storage on the secondary gateway.
Note Do not start Prime Performance Manager during this installation step.
d. Perform SP upgrade only from Prime Performance Manager 1.7.0 SP1 to Prime Performance Manager 1.7.0 SP1703 on the both the Prime Performance Manager gateway servers.
e. Unmount the SAN shared storage from the primary gateway manually.
f. Run the ppmGatewaySetup.sh script to create RHCS service configuration and start the Prime Performance Manager on the Local HA mode.
Begin the Prime Performance Manager HA gateway installation:
Step 1 Log into the primary gateway as the root user.
Step 2 Mount the SAN storage to the primary gateway, for example, to an /ha directory. This directory will be used for the installation. Make sure the SAN storage device is configured correctly.
Note Do not use the default /opt directory for installation to avoid overwriting it.
Note For the local HA cluster to operate, configure a label on your partitions or use multipath. If you do not use multipath, that is, your machine has two connections to the storage, configure the label. To configure the label on your partitions use e2label.
Step 3 Complete the Downloading and Extracting the Prime Performance Manager Software.
Step 4 Complete the Starting the Installation, with the following exceptions:
– Option 5 Install Prime Performance Manager Gateway with Red Hat Cluster Suite HA Mode and install Prime Performance Manager in the /ha directory if you are installing only the local HA, or,
– Option 7 Install Prime Performance Manager Gateway with Geographical HA and Red Hat Cluster Suite HA if you are installing both local and geographical HA.
Note Prime Performance Manager allows you to save files outside the installation directories in a standalone directory, for example, you might want to save the report data in a separate directory. If you want to save files in a directory outside the installation directory, you must create the directories in the SAN, then mount them, and run command to specify the respective directories, for example, ppm repdir and ppm reportDir. See the Cisco Prime Performance Manager 1.7 User Guide Command Reference for information on using these commands.
Note The primary and secondary gateway installation is identical. Only the install directories differ. The primary gateway is installed in the SAN storage while secondary gateway is installed on the local disk.
Step 5 Log into the second HA gateway and complete Step 4.
Step 6 After the installation is complete at the secondary gateway and you are asked to choose a startup option enter option 4 (Exit Setup).
Step 7 If you want to enable SSL in HA gateway, log into the primary gateway as the root user, then enter:
Note If SSL is enabled on the primary gateway, enable it on the secondary one as well.
a. To verify that the RHCS cman, rgmanager, ricci and NetworkManager are stopped on the two HA gateways, run the following status check commands at each gateway:
b. If needed, run these commands on the two HA gateways to stop the service if necessary:
c. Verify that all the required storage devices are mounted at the primary HA gateway node.
Note ● Only mount storage devices to one HA gateway; never mount a storage device to both gateways.
d. Log into the primary gateway as the root user and switch to the HA bin directory. The default location is:
e. Run ppmGatewayHASetup.sh and enter the RHCS configuration parameters:
– When you are asked to enter the storage mount device parameters, the first mounted device should be the location where the Prime Performance Manager is installed.
– You can enter multiple mount device point parameters for different Prime Performance Manager files outside of the installation. For example, in scale deployments, you might need to place Prime Performance Manager backup or report files in different directories. You can assign their mount devices points during RHCS configuration.
– When you are asked to enter the hostname parameters, enter the primary gateway hostname for Node 1 and the secondary gateway hostname for Node 2. Do not enter the gateway IP as the hostname.
– You must configure two fencing methods: IPMI or manual. To use other fencing methods, such VM Fencing, choose the manual fence type to complete the configuration, then use the RHCS Conga to manage the failover domains and change cluster node fencing method.
RHCS configuration takes 5-6 minutes. The configuration phases include ssh validation, ssh configuration, RHCS validation, and RHCS configuration. For each phase, you will see start and finish information.
To see the detailed configuration process information, display the HA lib log, then use tail-f to watch the ppmGatewayHASetupLog.log information. This log is located in the same directory where you ran ppmGatewayHASetup.sh. After the RHCS configuration is completed:
– RHCS is up on the primary gateway.
– The floating IP is reachable.
– The SAN storage volume LUNs are mounted.
– The Prime Performance Manager Gateway is running.
f. Log into the primary gateway, run the following command to get the ppm processes information:
g. Launch a web browser and enter the following in the URL:
For example, http://10.74.125.114:4440
h. Log into the secondary gateway as the root user (Prime Performance Manager is running on the primary gateway).
i. Change to the Prime Performance Manager local install directory, for example, /ha.
j. Rename the installation directory:
Renaming the directory helps you identify which mount point is currently being used.
Note If you upgrade or uninstall Prime Performance Manager, be sure to change the directory name back to its original name.
Step 9 As the root user on primary gateway, verify the cluster and services are running:
Step 10 Verify that the cman and rgmanager services are running on both cluster nodes. This is shown by the following lines:
Step 11 To manage the cluster from the CLI, you have two options:
ppmGatewayHA.sh options include:
– switchover—Switches the service to another cluster node.
– freeze—Freezes the RHCS service.
– unfreeze—Unfreezes the RHCS service.
– status—ShowS the RHCS service status.
Table 2-2 shows the RHCS clusvcadm command options.
|
|
---|---|
Migrate <group> to <member> (e.g. for live migration of VMs). |
|
The cluster log can be found under /var/log/messages.
Step 12 Install Prime Performance Manager on the units by completing the Starting the Installation, choosing unit only with the following exceptions:
The following text shows a sample gateway installation using the RHCS HA option:
The following output provides an example of the gateway HA RHCS configuration:
Before you begin a geographical HA configuration, verify the following:
Note If you install a unit in a geographical HA environment, and install and reinstall the unit several times and then connect it to the gateway or you refresh the gateway build but do not stop the unit first, duplicate gateway/units will appear on the Gateway/Units page.
To install Prime Performance Manager in a geographical HA configuration:
Step 1 Complete the Downloading and Extracting the Prime Performance Manager Software.
Step 2 Start the Starting the Installation. At Step 3, choose Option 6 Install Prime Performance Manager Gateway with Geographical HA.
Step 3 Complete Steps 4 through 6 of the Starting the Installation.
At the enable User Access prompt, enter the following:
Step 4 Enter the gateway service role:
Note The service role is predefined. However, the first working gateway one will become the primary gateway.
Step 5 Enter the IP address or hostname of the peer gateway.
Note The gateway IP address format must match the peer one. Mixing address formats is not permitted.
Step 6 Enter the RMI port of the peer gateway.
Note The primary and secondary gateway must use the same RMI port.
Step 7 Enter the HA health check interval. This is the time interval when the secondary gateway checks the primary gateway status.
Step 8 Enter the maximum continuous tolerated fail number. This is the number of times the secondary gateway is unable to communicate with the primary gateway before it initiates a failover. The default is 6. If you are installing local and geographical HA, enter 60.
Step 9 Enable CSV file synchronization.
Note Enabling CSV file synchronization will generally double the demands on network resources.
Step 10 Enter the primary database age out. This is the amount of time that the secondary gateway is not connected to the primary gateway database, after which the primary gateway is marked Out of Sync.
Step 11 Enter database differences cache records limitation. If the primary database caching is up to the configured number and the secondary gateway is not connected, the primary gateway is marked Out of Sync.
After the unit is installed, the following message is displayed:
Step 12 If you do not want to view the log, press Enter. To view the log, enter y, press Enter, then press the spacebar to scroll through the log.
At the end of the installation, you are presented with the following options.
Step 13 If user access is not enabled on the primary gateway, choose 1 to start or 3 to exit. If user access is enabled on the primary gateway, continue with the next step.
Step 14 If user access is enabled on the primary gateway, complete the following steps:
a. Choose 3 to exit, then enable SSL. For information, see the Cisco Prime Performance Manager 1.7 User Guide.
b. Restart the gateway to connect to the primary gateway and synchronize the user information.
c. Enable user access and choose the existing user database.
Note Before starting the secondary gateway, verify the primary gateway is up. To check the status of primary gateway, you can run the ppm primeha status command. For information, see “Displaying Geographical HA Status” in the Cisco Prime Performance Manager 1.7 User Guide.
To install Prime Performance Manager in a local and geographical HA configuration:
Step 1 Complete the Installing Prime Performance Manager in a Local HA Configuration. When completing the Starting the Installation, at Step 3, choose Option 7 Install Prime Performance Manager Gateway with Geographical HA and Red Hat Cluster Suite.
Step 2 Complete the Installing Prime Performance Manager in a Geographical HA Configuration. At Step 8, enter 60 for the maximum continuous tolerated fail numbers.
Note In local and geographical HA mode, the secondary geographical gateway must keep at least five minutes timeout (recommended) so that it provides sufficient time for the local HA switchover or failover when local HA failure occurs. The local HA sites do not need to change its default timeout value.
Note In local and geographical HA mode, use the RHCS Relocate service instead of Restart service for local HA.
If DNS is not configured, install dnsmasq on the primary and secondary HA gateways to ensure gateway connectivity following switchovers. (dnsmasq is included with Red Hat Enterprise for Linux.)
Step 1 At the command prompt, enter:
Step 2 Edit /etc/dnsmasq.conf:
Note If you install dnsmasq after Prime Performance Manager is running, you must stop the secondary Prime Performance Manager HA gateway, restart the primary HA gateway, then start the secondary HA gateway. For information about starting and topping Prime Performance Manager, see the Cisco Prime Performance Manager 1.7 User Guide.
After you install the Geographical HA gateways and units, start the gateways in the following orders:
For secondary gateway, if you are trying to connect to an Out of Sync primary gateway, the following exceptions will be raised. Follow the instructions to start it.
2013/08/01 21:44:20: The db is out of sync. Please run following steps:
For information on performing these steps, see the “Managing Geographical HA” topic in the Cisco Prime Performance Manager 1.7 User Guide.
If you try to connect a unit to the secondary gateway, the following exceptions will be raised. Follow the provided steps to start it.
After you install the Prime Performance Manager gateway and/or unit, you can start the gateway and/or unit immediately after the installation or at a later time.
To start the Prime Performance Manager gateway and/or unit from the command line, log in as the root user and use the following commands:
Note The following procedures assume that you installed the Prime Performance Manager in the default directory, /opt. If you installed the Prime Performance Manager in a different directory, use the name of that directory in place of /opt.
Table 2-3 lists the commands used to start Prime Performance Manager. For detailed instructions on using the commands to start and manage to start Prime Performance Manager, see “Managing Gateways and Units Using the Command Line Interface” in the Cisco Prime Performance Manager 1.7 User Guide.
|
|
---|---|
|
|
|
|
|
To verify the Prime Performance Manager installation, you can perform tasks in the following topics:
Note These procedures are only needed if problems occur during installation. If Prime Performance Manager installs and starts normally, no verification tasks need to be performed.
During installation, messages are recorded in a log file to provide diagnostic information about problems that might arise. The location of the installation log file is provided at the end of the installation.
To check for installation error messages:
Step 1 Log into the Prime Performance Manager server as the root user
Step 2 Use the following commands to view the installation logs:
Where install_directory is the directory in which the Prime Performance Manager is installed. The default installation directory for the Prime Performance Manager is /opt/CSCOppm-gw or /opt/CSCOppm-unit
Step 3 Press the spacebar to scroll through the log.
You can also display the Prime Performance Manager gateway installation logs using the ppm installlog command.
To verify that the Prime Performance Manager gateway and unit software package is installed on a Linux server:
Step 2 To view more information about a package, enter one of the following commands:
Step 3 Verify that you receive output similar to the following:
If a package is not found, one of the following messages is displayed:
If the Prime Performance Manager software packages were not installed, install the Prime Performance Manager again.
After you install Prime Performance Manager, you can check the gateway status by entering the following command:
Information about the gateway is displayed. In the output, you should see the following status:
If a unit is installed on the same server as the gateway, the unit information is provided. In the output, you should see the following status:
To check the status of a remote unit, log into the remote server and enter:
For additional information, see “Managing Gateways and Units using the Command Line Interface” in the Cisco Prime Performance Manager 1.7 User Guide.
The following topics describe how to upgrade Prime Performance Manager to Release 1.7 and how to upgrade from non-HA to HA version:
Complete the following steps to upgrade an existing Prime Performance Manager gateway or unit to Prime Performance Manager 1.7.
Step 1 If the Prime Performance Manager gateway is colocated with the unit, prepare another server and relocate unit to the new server. Gateways in an HA environment must reside on their own server.
Step 3 At the Upgrade Program screen, choose an upgrade option:
Note For HA upgrade procedures, see Upgrading Prime Performance Manager to an HA Environment
The upgrade script will upgrade the gateway and unit, gateway only, or unit only, depending on your selection.
Note After the upgrade script finishes, allow Prime Performance Manager to run for at least one hour before shutting it back down for any reason, including another upgrade.
Complete the following steps to upgrade an existing Prime Performance Manager gateway to a local HA gateway.
Step 1 Verify that your primary and secondary gateways meet the RHCS HA requirements described in RHCS Requirements.
Step 2 Verify that Prime Performance Manager 1.7 is installed and functioning normally:
Step 3 If the Prime Performance Manager gateway is colocated with the Prime Performance Manager unit, prepare another server and relocate unit to the new server. Gateways in an HA environment must reside on their own server.
Step 4 If the Prime Performance Manager gateway install directory is not in SAN storage, relocate the directory to the SAN storage following the steps in Change the Prime Performance Manager Installation Directory.
Step 5 Release the primary gateway IP address and use it as the RHCS floating IP address.
Step 6 Change the current gateway IP address to a new one. (Do not start Prime Performance Manager at this point.)
Step 7 Install the HA lib for the primary gateway:
For additional information, enter:
The ppmGatewayHALibUpgrade.sh script is located in the directory where you extracted the Prime Performance Manager installation zip.
Step 8 Complete the Installing Prime Performance Manager on High Availability Gateways to install the Prime Performance Manager gateway with HA in another node local directory. The local directory name should be same as the SAN storage directory. Enter the floating IP address as the gateway IP address which was released as the gateway IP address in Step 5.
Step 9 Configure RHCS following instructions in Step 8 of the Install the Local HA Gateway.
Note If you encounter an error during the HA lib installation, use the ppmGatewayHALibUpgrade.sh clean command to clean the HA lib and HA installation information.
The following sections tell you how to upgrade an existing Prime Performance Manager gateway to an HA environment:
Note Prime Performance Manager 1.7 does not support upgrades from Prime Performance Manager 1.2.1 directly to Prime Performance Manager 1.7 in gateway HA mode. You must upgrade from Prime Performance Manager 1.2.1 to Prime Performance Manager 1.7 in non-HA mode using the normal upgrade procedure, then follow the procedures in this section to upgrade from non-HA to HA mode. This also applies to upgrades from Prime Performance Manager 1.7 non-HA mode to Prime Performance Manager 1.7 HA mode.
Complete the following steps to upgrade a Prime Performance Manager gateway in a local HA configuration to a later Prime Performance Manager release gateway in a local HA configuration.
Step 1 Verify that your current primary and secondary gateways are running in Prime Performance Manager gateway HA mode.
Step 2 Freeze the health monitor between primary and secondary gateways following steps in the “Freezing and Unfreezing RHCS” procedure in the Cisco Prime Performance Manager 1.7 User Guide.
Step 3 Upgrade the primary gateway that is mounted to a SAN storage, then start the gateway.
Step 4 Unfreeze the health monitor.
Step 5 Switch over to the secondary gateway and let it act as the active gateway.
Step 6 Freeze the health check monitor.
Step 7 Stop the Prime Performance Manager installed on the SAN Storage.
Step 8 Unmount the SAN storage on the secondary gateway.
Step 9 Start the Prime Performance Manager installed on the disk.
Step 10 Upgrade the secondary gateway that has the Prime Performance Manager installed on a local disk. Do not start the gateway.
Step 11 Mount the SAN storage on the secondary gateway, and
Step 12 Start Prime Performance Manager installed on SAN storage.
Step 13 Unfreeze the health check monitor.
Step 14 Switch back to the original active gateway.
Step 15 Upgrade the units and then restart them.
Step 16 Verify that the Prime Performance Manager gateway and units are upgraded and functioning normally.
To upgrade Prime Performance Manager 1.6.0 SP4 to 1.7.0 SP1703 while upgrading OS from RHEL 5.8 to 6.8, perform the following steps:
Step 1 Freeze the RHCS service.
Step 2 Upgrade the primary gateway with the SAN shared storage from Prime Performance Manager 1.6.0 SP4 to 1.7.0 SP1703.
Step 3 Add the RHCS Virtual IP Address (VIP) on the secondary gateway manually and upgrade the Secondary gateway with the local storage from Prime Performance Manager 1.6.0 SP4 to 1.7.0 SP1703.
Step 4 Remove the virtual IP address manually after the upgrade.
Step 5 Upgrade the Prime Performance Manager units to SP1703.
Step 6 Unfreeze the RHCS and check if the RHCS works correctly with Prime Performance Manager.
Step 7 Create backup of the primary gateway using the following command:
Step 8 Upload the backup tar to a different backup server which does not impact the OS re-installation.
Step 9 Reinstall both the Local HA Linux server OS to RHEL 6.8 with RHCS packages.
Maintain the same IP address, hostname, and VIP as specified earlier.
Step 10 Perform a fresh installation of Prime Performance Manager Local HA on RHEL 6.8 and start Prime Performance Manager on the primary gateway.
Step 11 Copy the Prime Performance Manager gateway backup tar to the primary gateway using Secure Copy Protocol (SCP).
Step 13 Restore the Prime Performance Manager on the primary gateway from the backup tar using the following command:
Step 14 Check if the gateway unit connections, device reports, Prime Performance Manager configuration, and CSV reports are restored correctly.
Step 16 Perform a Local HA switchover or switchback, failover or failback, freeze or unfreeze actions to make sure that the RHCS service works correctly.
Complete the following steps to upgrade an existing Prime Performance Manager standalone gateway to a primary and secondary peer gateways in geographical HA mode.
Step 1 Verify the current standalone gateway server meets all requirements in Geographical HA Requirements. If not, do not continue. Address the requirement deficiencies, then begin the installation.
Step 2 Complete the Upgrading to Prime Performance Manager 1.7, choosing Option 4 Upgrade Prime Performance Manager Gateway.
Step 3 Start the primary gateway.
Step 4 Complete the Upgrading to Prime Performance Manager 1.7 to upgrade all units to 1.7, choosing Option 5 Upgrade Prime Performance Manager Unit.
Step 6 On the primary gateway, run /opt/CSCOppm-gw/bin/ppmGeoHA.sh to change the gateway from non-HA to geographical HA mode and provision the geographical HA parameters.
Step 7 Prepare a new server to install the secondary gateway and configure the new server as its peer gateway name. Sample configuration:
Step 8 After you configure the geographical HA parameters, restart the gateway. It will operate as the primary gateway.
Step 9 Install the secondary gateway on the new server. For more information on geographical HA configuration parameters, see Steps 4 through 11 in the Installing Prime Performance Manager in a Geographical HA Configuration. Do NOT start the new gateway after setup.
Step 10 Create a database backup file in the upgraded gateway:
Step 11 Remote copy the database backup file to the new installed gateway.
Step 12 On the new gateway, restore the backup file so the two gateways have the same database and files base:
Step 13 Run commands ppm primeha status on both Primary gateway and secondary gateway to verify the communication and connection established.
Step 14 (Optional) If SSL is enabled, see “Configuring SSL Between Gateways and Units” in the Cisco Prime Performance Manager 1.7 User Guide.
Step 15 Verify that the Prime Performance Manager primary and secondary gateways and units are functioning normally.
Complete the following steps to upgrade a Prime Performance Manager gateway in a geographical HA configuration to a later Prime Performance Manager Release gateway in a geographical HA configuration.
Step 1 Verify that your current primary and secondary gateways are running in Prime Performance Manager Gateway Geographical HA mode.
Note In the following steps, the primary gateway is PPM1, and the secondary gateway is PPM2.
Step 2 Upgrade PPM2, then restart it. See Upgrading to Prime Performance Manager 1.7.
Step 3 Upgrade the redundant unit, then restart it.
Step 4 Stop PPM1 using the command, ppm stop. The secondary gateway (PPM2) becomes the primary one.
Note When the Actions menu does not appear after stopping the PPM1, ensure to clear the browser cache of PPM2 or reload the browser page from PPM2.
Step 5 Perform a Failover on the primary unit. See “Performing Manual Redundant Unit Failovers” in the Managing Gateways and Units chapter of the Cisco Prime Performance Manager 1.7 User Guide. This sets the redundant unit as the active one.
Step 6 Upgrade the primary unit, then restart it.
Step 7 Perform a Fallback on the primary unit. See “Switching Redundant Units Back to Standby” in the Managing Gateways and Units chapter of the Cisco Prime Performance Manager 1.7 User Guide.
Step 8 Set PPM 1 as the secondary gateway:
Step 9 Start PPM1, upgrade it, then restart it.
Step 10 Restart PPM2 using the ppm restart command. This switches PPM1 back to the primary gateway.
Note When the Actions menu does not appear after stopping the PPM2, ensure to clear the browser cache of PPM1 or reload the browser page from PPM1.
Step 11 Verify that the upgrade did not cause the primary and secondary gateway databases to get out of synchronization. If the primary and secondary gateway databases are out of synchronization, as indicated by the primary gateway Out of Sync parameter (see “Displaying Geographical HA Status” in the Managing Gateways and Units chapter of the Cisco Prime Performance Manager 1.7 User Guide), synchronize them (see “Synchronizing the Geographical HA Gateways” in the Managing Gateways and Units chapter of the Cisco Prime Performance Manager 1.7 User Guide).
Step 12 Verify that the Prime Performance Manager primary and secondary gateways and units are upgraded and functioning normally.
You cannot upgrade a Prime Performance Manager 1.2.1 gateway directly to Prime Performance Manager 1.7 gateway with an integrated local and geographical HA configuration. To upgrade a gateway to geographical HA integrated with local HA:
Step 1 Complete the Upgrading to Prime Performance Manager 1.7 to upgrade the existing Prime Performance Manager to 1.7.
Step 2 Complete the Upgrade a Gateway to Local HA to upgrade the existing Prime Performance Manager gateway to local HA gateway.
Step 3 Complete the Enable Geographical HA in an Upgraded Local HA Gateway to enable geographical HA in the upgraded local HA gateway.
Complete the following steps to upgrade a Prime Performance Manager gateway in a geographical HA integrated with local HA configuration to a later Prime Performance Manager Release gateway in a geographical HA integrated with local HA configuration.
Step 1 Verify that your current primary and secondary gateways are running in Prime Performance Manager Gateway geographical HA integrated with local HA mode.
Step 2 Stop the geographical HA secondary gateway and all of the units.
Step 3 Freeze the health monitor between local HA primary and secondary gateways following steps in Red Hat Cluster Suite documentation.
Step 4 Upgrade the local HA primary gateway that is mounted to a SAN storage.
Step 6 Unfreeze the health monitor.
Step 7 Switch over to the local HA secondary gateway and let it act as the local HA active gateway.
Step 8 Freeze the health check monitor.
Step 9 Unmount SAN storage, and upgrade the local HA secondary gateway that has the Prime Performance Manager binary installation on a local disk.
Note Do not start the gateway on the local disk.
Before you begin to enable geographical HA:
To enable geographical HA in an upgraded local HA gateway:
Step 1 Freeze the local HA gateway:
Step 2 Stop the local HA gateway.
Step 3 From the install_directory/bin directory, enable the geographical HA on the local HA gateway:
Step 4 Configure the to-be installed geographical gateway IP address (see Step 7 ) as the peer gateway name. After setup, restart Local HA gateway.
Step 5 Unfreeze local HA gateway:
Step 6 Install one new Prime Performance Manager gateway with Option 6) Install Prime Performance Manager Gateway with Geographical HA.
Step 7 Configure the local HA gateway floating IP address as the peer gateway, and configure 60 as the maximum continuous tolerated fail numbers.
Step 8 Before you start the secondary gateway, copy the database files from the primary to the secondary gateway:
a. Back up the primary gateway:
b. Copy the database files to the secondary gateway.
c. Start the secondary gateway:
Step 9 (Optional) If SSL is enabled, see “Configuring SSL Between Gateways and Units” in the the Cisco Prime Performance Manager 1.7 User Guide.
If you installed the Prime Performance Manager gateway in local directory, you must change the directory because gateway HA requires the gateway installation directory be installed in the SAN storage.
Step 1 Verify that Prime Performance Manager is running.
Step 2 Enable the HA backup flag:
Step 3 Verify that HA backup is enabled:
Step 4 Run the Prime Performance Manager backup:
Note If you want to change the backup directory, run the ppm backupdir target_dir command to specify the target directory. For example: ppm backupdir /root/test/backupdirectory.
Step 5 Make a copy of the backed up gateway files to another directory for future reference. For example:
Step 6 Uninstall the Prime Performance Manager gateway.
Step 7 Change to a new directory mounted on the SAN storage.
Step 8 Install the new gateway; do not start it at this time.
Step 9 Specify the backup directory so that Prime Performance Manager can find the backup tar in Step 5, for example:
Step 11 Disable the HA backup flag:
Step 12 Verify that the flag is disabled:
Note The ppm localhabackupflag is only used for changing a normal gateway installation directory for upgrading to HA. After the directory change is completed, the flag should be disabled.