Cisco Prime Performance Manager Quick Start Guide, 1.7

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.

• Installation Requirements
• Installing Prime Performance Manager
• Next Steps
• Uninstalling Prime Performance Manager

Book Title

Cisco Prime Performance Manager Quick Start Guide, 1.7

Installation Requirements

• PDF - Complete Book (1.66 MB)PDF - This Chapter (889.0 KB) View with Adobe Reader on a variety of devices

Results

Chapter: Installation Requirements

• New and Revised Information
• Supported Operating Systems
  • Ubuntu Requirements
  • VM Environments
  • Additional Requirements Notes
  • Server Requirements for Single Deployments
    • Proof of Concept Single Deployment Installation Requirements
    • Medium Network Single Deployment Server Requirements
    • Large Network Single Deployment Server Requirements
    • Very Large Network Single Deployment Server Requirements
    • Large Network Distributed Deployment Server Requirements
    • Very Large Network Distributed Deployment Server Requirements
    • Extremely Large Network Distributed Deployment Server Requirements
    • Extremely Large Network Distributed Deployment Server Requirements with 5-Minute Reports Enabled
    • Maximum Supported Scale Distributed Deployment Server Requirements
    • Mobility StarOS Medium Scale EPC on Single VM
    • Mobility StarOS Scale EPC Distributed Active Only Configuration
    • 30 0,000 3G Access Points Small Cell Scale on a Distributed Server s with Managed ULS Redundancy
    • 120,000 3G Access Points Small Cell Scale on a Single Ser ver
    • RAN Management System Requirements
    • Server Requirements for Managing KVM and Cisco Unified Computing Service Manager Deployments
    • 100 Ceph Nodes with 1-Minute Reports Enabled on a Single Server
    • Local High Availability Requirements
      • RHCS Components and Functionality
      • RHCS Requirements
      • Latency Recommendations

      Cisco Prime Performance 1.7 Installation Requirements

      The following topics provide the hardware and software requirements for installing Cisco Prime Performance Manager 1.7:

      • New and Revised Information, page 1-2
      • Supported Operating Systems, page 1-3
      • Client Requirements, page 1-6
      • Cisco Prime Interoperability, page 1-7
      • Evolved Programmable Networks Requirements, page 1-7
      • Requirements for Mobility StarOS Networks, page 1-47
      • Code Division Multiple Access Distributed Mobility Scale Requirements, page 1-53
      • Requirements for Small Cell Networks, page 1-55
      • Requirements for collectd, page 1-61
      • Single Server ESXi Hypervisor Requirements, page 1-62
      • Single Server Requirements for Data Collection Manager, page 1-64
      • Requirements for Managing KVM Deployments
      • Requirements for Ceph Deployments
      • Requirements for TCP/HTTP Probes
      • Requirements for NetFlow
      • Linux Update Requirements, page 1-75
      • Gateway Requirements Large Number of Units Distributed Scale, page 1-77
      • Gateway High Availability Installation Requirements, page 1-85
      • Network Device Configuration, page 1-91
      • Prime Performance Manager Ports, page 1-91
      • Permissible IPv4 and IPv6 Addresses, page 1-92
      • Bandwidth and Latency Requirements

      New and Revised Information

      Table 1-1 lists new and revised information since the first Prime Performance Manager 1.7 release.

      Table 1-1 New and Revised Information

      Date Change Location

      Added dnsmasq installation procedure.

      Support for the following:

      • RHEL 7.2 and Ubuntu 14.04
      • VMWare ESX 6.0
      • Cisco Prime Interoperability
      • RHCS Requirements
      • Updated steps to install the local HA gateway on the earlier version of Prime Performance Manager.
      • Added steps to upgrade an existing Prime Performance Manager local HA gateway while performing an OS upgrade from RHEL 5.X to RHEL 6.X.
      • Supported Operating Systems
      • VM Environments
      • Cisco Prime Interoperability
      • RHCS Components and Functionality
      • Install the Local HA Gateway
      • Upgrade an Existing Local HA Gateway

      Support for the following:

      • RHCS Requirements
      • Prime Central 1.5.3 and Prime Network 4.3.1, 4.3.2
      • RHCS Requirements
      • Cisco Prime Interoperability

      Support for the following

      Support for the following:

      • RHEL 6.9 requirement
      • RHCS requirements
      • Updated steps for Local HA Operation Notes and to install the local HA gateway on the earlier version of Prime Performance Manager
      • Supported Operating Systems
      • RHCS Requirements
      • Install the Local HA Gateway

      Support for the following

      Support for the following:

      • RHEL 6.10
      • RHCS requirements
      • Updated steps to install the local HA gateway on the earlier version of Prime Performance Manager
      • Cisco Prime Interoperability
      • Client requirements
      • Supported Operating Systems
      • RHCS Requirements
      • Install the Local HA Gateway
      • Cisco Prime Interoperability
      • Client Requirements

      Support for the following:

      • Cisco Prime Interoperability
      • Updated steps to install the local HA gateway
      • Cisco Prime Interoperability
      • Install the Local HA Gateway

      Support for the following:

      Support for the following:

      Update to the additional RPM packages

      Supported Operating Systems

      You can install Prime Performance Manager gateway and unit servers on the following 64-bit Linux versions:

      • Red Hat Enterprise Linux 5.0 Advanced Platform Update 5, Update 6, Update 7, Update 8, Update 9, Update 10, Update 11, or CentOS equivalent.
      • Red Hat Enterprise Linux 6.0, Update 2, Update 3, Update 4, Update 5, Update 6, Update 8, Update 9, Update 10, or CentOS equivalent.
      • Red Hat Enterprise Linux 7.0, 7.1, 7.2, 7.3, 7.4, 7.7, or CentOS equivalent.
      • Linux Ubuntu Server 12.04 and 14.04 Release.
      • XenApp 6.0

      Note RHEL 6.9 is supported from Release 1.7 Service Pack 1805 and above.
      RHEL 7.4 is supported from Release 1.7 Service Pack 1807 and above.
      RHEL 6.10 is supported from Release 1.7 Service Pack 1901 and above.
      RHEL 7.7 is supported from Release 1.7 Service Pack 2003 and above.

      Note Only 64-bit Linux images are supported; 32-bit Linux images are not supported.

      Note Solaris is not supported.

      In addition, the following additional RPM packages (or later versions) must be installed if they are not already installed:

      • crontabs-1.10-8
      • vixie-cron-4.1-76
      • bzip2-libs-1.0.3-4
      • ksh-20080202-2
      • glibc-2.5-34
      • bc-1.06-21
      • bind-utils-9.3.4-10
      • time-1.7-27
      • words-3.0-9
      • freetype-2.2.1-21
      • fontconfig-2.4.1-7
      • expat-1.95.8-8.2.1
      • gawk-3.1.5
      • net-tools-1.60

      If you are running SELinux (Security-Enhanced Linux) and you enabled Prime Performance Manager user access with SSL enabled, run the following command to load the SSL shared library from Prime Performance Manager:

      chcon -t textrel_shlib_t '/opt/CSCOppm-gw/apache/libexec/libssl.so'

      If you are running Red Hat Enterprise Linux Version 6 Update 2 or later:

      • Install the following additional RPM packages (or later versions) if not already installed:
      • Install the following the compatibility libraries:

      Package collections -> Compatibility Libraries

      If you will use Prime Performance Manager to manage hypervisors, after installing Prime Performance Manager, run the ppm hypervisor checklibrary command to determine if all required shared libraries are installed:

      ppm hypervisor checklibrary

      Missing libraries are listed as “not found”.

      Common RPM packages that must be installed—but might not be by default—include:

      • cyrus-sasl-lib
      • cyrus-sasl-md5
      • e2fsprogs-libs
      • keyutils-libs
      • krb5-libs
      • libgcrypt
      • libgpg-error
      • libidn
      • libselinux
      • libsepol
      • openldap
      • compat-openldap
      • zlib
      • openssl
      • openssl-0.9.8e (for RedHat Linux Version 5)
      • openssl098e (for RedHat Linux Version 6)
      • openssl098e (for RedHat Linux Version 7)

      If you are integrating with LDAP using PAM, the following RPMs are required:

      • RedHat Linux Version 5
      • RedHat Linux Version 6
      • RedHat Linux Version 7

      Libraries for PAM_LDAP are provided with the Linux distribution with no support from Cisco. Any issues with PAM_LDAP in a specific deployment are beyond the scope of Cisco support.

      To verify the RPMs that are installed on your system, enter:

      Check for the packages listed above or more recent versions. To get RPMs for Red Hat Enterprise Linux, contact your Red Hat representative or download them from the Red Hat website at: http://www.redhat.com.

      Note Downloading Red Hat Enterprise Linux RPMs might require a support agreement.

      Ubuntu Requirements

      Prime Performance Manager supports Ubuntu 12.04 and later with the following guidelines:

      • Install the RPMs before you install Prime Performance Manager.
      • The apt-get install libssl0.9.8 package must be installed.
      • All required Red Hat packages must be installed. To verify whether the packages are installed on your server, enter:
      • Configure Ubuntu to not use dash as the default shell. For example:

      VM Environments

      You can install and run Prime Performance Manager in a VM environment as long as the VM meets the equivalent requirements provided in the following sections. VM releases supported as both runtime environments and as targets for monitoring by Prime Performance Manager include:

      • VMWare ESX 4.1, ESXi 5.0, 5.1, 5.5, 6.0
      • Linux KVM 2.x
      • OpenStack Havana, Icehouse, and Juno releases

      HyperV and Xen are only supported as targets for monitoring by Prime Performance Manager. They have not been tested as runtime environments.

      Note Run Prime Performance Manager on a VM only for POC or medium size networks, For large networks and higher, run Prime Performance Manager on bare metal servers with direct disk access. (For network sizes, see Table 1-2.)

      Client Requirements

      Prime Performance Manager clients do not require a separate installation. Clients can access using a web browsers. The following browsers are supported:

      • Microsoft Internet Explorer 9.0 or greater
      • Firefox 24 or later up to Firefox 55
      • Firefox 24 Extended Support Release (ESR) or later up to Firefox 52 ESR

      Later versions of Internet Explorer and Firefox, Safari and Chrome are not formally tested but are widely used without problems.

      Other client requirements:

      • The minimum screen resolution is 1280 x 960.
      • The hostname configured on the Prime Performance Manager gateway must be resolvable to an IP address on the client machine using DNS or a local hosts file.

      Cisco Prime Interoperability

      Prime Performance Manager 1.7 can inter-operate with the following Cisco Prime products:

      • Cisco Prime Central 1.3, 1.4, 1.4.1, 1.5, 1.5.1, 1.5.2, 1.5.3, 2.0, and 2.1
      • Cisco Prime Network 3.10, 3.11, 4.0, 4.1, 4.2, 4.2.1, 4.2.2, 4.2.3, 4.3.0, 4.3.1, 4.3.2, 5.0, 5.1, 5.2, and 5.3
      • Cisco Prime Service Catalog 10.1
      • Cisco Prime Network Service Controller 3.2 and 3.3

      If you integrate Prime Performance Manager 1.7 with Prime Carrier Management, integration is only allowed with the following Prime Central and Prime Network releases:

      • Prime Central 2.1 with Prime Network 5.3 and Prime Performance 1.7 SP2003 and above
      • Prime Central 2.1 with Prime Network 5.2 and Prime Performance 1.7 SP1909 and above
      • Prime Central 2.1 with Prime Network 5.1 and Prime Performance 1.7 SP1807 and above
      • Prime Central 2.0 with Prime Network 5.0 and Prime Performance 1.7 SP1805 and above
      • Prime Central 1.5.3 with Prime Network 4.2.1, 4.2.2, 4.2.3, 4.3.0, 4.3.1, 4.3.2 and Prime Performance 1.7 SP1705 and above
      • Prime Central 1.5.1 and 1.5.2 with Prime Network 4.2, 4.2.1, 4.2.2, 4.2.3, 4.3 and Prime Performance 1.7 SP4 and above
      • Prime Central 1.5 with Prime Network 4.2, 4.2.1, 4.2.2, 4.2.3 and Prime Performance 1.7
      • Prime Central 1.4.1 with Prime Network 4.2.1 and Prime Performance 1.7
      • Prime Central 1.4 with Prime Network 4.2 and Prime Performance 1.7
      • Prime Central 1.3 and Prime Network 4.1

      Evolved Programmable Networks Requirements

      For Evolved Programmable Networks (EPNs), Prime Performance Manager gateway and unit(s) can be installed on the same server (single deployment) or on separate servers (distributed deployments). Single deployments are permitted when high availability will not be configured for proof of concept (POC), medium, large, and very large networks. Distributed deployments are required if you plan to configure high availability or your network is in the extremely large or maximum supported categories. Server and operating system requirements depend on your network size. Network sizes are based on maximums numbers for the following:

      • Devices
      • Layer 3 pseudowires (PWE3s)
      • Interfaces—The number of device interface table entries. This number is usually higher than the number of physical ports because it includes pseudowires, virtual circuits, VLANs, and other virtual interfaces.
      • Interfaces generating statistics—The number of interfaces generating statistics. This category excludes DS1, DS3, SONET, SDH, and ATM layers that do not return valid statistics for these layers.

      Table 1-2 shows the maximums used for the Prime Performance Manager server requirements for single and distributed deployments.

      Table 1-2 Network Sizes for Planning Prime Performance Manager Server Requirements

      Element Single Deployment Distributed Deployment