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 provide steps to uninstall the Prime Performance Manager gateway and unit.
If you are uninstalling Prime Performance Manager installed in a gateway HA environment, complete the Uninstalling Prime Performance Manager in a Gateway Local HA Environment before completing the uninstallation steps below.
Note If Prime Performance Manager is integrated with Cisco Prime Central, all Cisco Prime Network instances must be running in order for Prime Performance Manager to uninstall the Prime Network cross launch points.
Note You must log in as the root user to use this command.
When you run the Uninstall option, note that:
To uninstall the Prime Performance Manager software:
Step 1 Log into the Prime Performance Manager server as the root user.
Step 2 Enter one of the following:
Note If you want a completely unprompted uninstall you can can run: ppm uninstall -n
The uninstall option checks for the gateway and/or unit installation, then displays the uninstallation menu:
Step 3 Choose an uninstall option:
Use this option if the Prime Performance Manager gateway and unit reside on the same server and you want to remove all Prime Performance Manager software from the server including the gateway (CSCOppm-gw) and unit (CSCOppm-unit) packages.
Use this option if you want to remove only the Prime Performance Manager gateway package (CSCOppm-gw) from the server.
Note Because the unit depends on gateway, do not use this option if the gateway and unit are installed on the same server. You can uninstall unit first, then uninstall the gateway later.
Use this option if you want to remove only the Prime Performance Manager unit package (CSCOppm-unit) from the server.
Step 4 Choose the option, enter y and press Enter.
Messages indicate that the packages were deleted successfully. For example, the following example shows the message displayed when uninstalling the Prime Performance Manager gateway:
Step 5 If you do not want to view the log, press Enter. If you want to view the log, enter y. The gateway uninstallation log appears, followed by the prompt:
The following message appears:
Step 7 To verify that Prime Performance Manager and its associated services are uninstalled, enter:
The packages are listed based on your uninstallation option. For example, if you uninstalled only the unit on a server containing gateway and unit, the following gateway packages are listed:
CSCOppm-gw-web-1.4.1-01.i386
CSCOppm-gw-openssl-1.4.1-01.i386
CSCOppm-gw-server-1.4.1-01.i386
CSCOppm-gw-jre-1.4.1-01.64bit.i386
Uninstalling Prime Performance Manager in a Gateway Local HA Environment
To uninstall Prime Performance Manager when installed in a gateway HA environment:
Step 1 Use a standalone Red Hat Conga (the standalone Conga is installed on a standalone server; it is not part of the cluster node) to delete the Prime Performance Manager gateway HA cluster service.
Step 2 Run the following commands to stop the RHCS ricci service on each gateway:
Step 3 Go to the primary gateway, mount the SAN storage where you installed Prime Performance Manager, then complete the Prime Performance Manager uninstallation steps above.
Step 4 After Prime Performance Manager is uninstalled on the primary gateway, log into the secondary gateway as the root user.
Step 5 Rename the installation directory to back to CSCOppm-gw. This will help when you uninstall Prime Performance Manager on the secondary gateway.
Step 6 Complete the Prime Performance Manager uninstallation steps above.
Step 7 Reboot the primary and secondary gateway servers.