Table Of Contents

Cisco Prime Performance Manager 1.1 Installation Requirements

Server Requirements

Network Sizes for Planning Server Requirements

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

Server Requirements for Distributed Deployment Installations

Very Large Network Distributed Deployment Server Requirements

Extremely Large Network Distributed Deployment Server Requirements

Super Large Network Distributed Deployment Server Requirements

Client Requirements

Network Device Configuration

Prime Performance Manager Ports

Cisco Prime Performance Manager 1.1 Installation Requirements

---

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

•Server Requirements

•Client Requirements

•Network Device Configuration

•Prime Performance Manager Ports

Server Requirements

You can install the Prime Performance Manager gateway and units on Solaris or Red Hat Enterprise Linux.

---

Note Prime Performance Manager supports VMWare environments as long as the virtual machines meet the requirements provided in the following sections. However, Cisco does not recommend VMWare for high-scale environments. High-scale environments should always use physical servers with direct disk access.

---

Table 1-1 shows the supported Solaris versions.

Table 1-1 Supported Solaris Versions

Version	Prime Performance Manager Release
	1.1	1.1.1
Solaris 10	Yes	Yes
Solaris 11	No	Yes

If you install Prime Performance Manager on Solaris, apply the latest patches for your Solaris version.

---

Note If the required patches are not installed, the Prime Performance Manager might not operate as expected.

---

Prime Performance Manager checks for these patches automatically and reports any that are missing. You can download the Oracle Solaris patches from the Oracle support site:

https://support.oracle.com/CSP/ui/flash.html

---

Note The J2SE Patch Cluster is discontinued. Oracle recommends the Solaris Recommended Patch Cluster in its place. See the Oracle website for information.

---

Table 1-2 shows the supported Red Hat Enterprise Linux versions.

Table 1-2 Supported Red Hat Enterprise Linux Versions

Version	Prime Performance Manager Release
	1.1	1.1.1
Red Hat Enterprise Linux 5.0 Update 3 or later, or equivalent CentOS.	Yes	Yes
Red Hat Enterprise Linux 6.0 Update 2 or later, or equivalent CentOS.	No	Yes

If you are installing Prime Performance Manager on Red Hat Enterprise Linux 5, Update 3 or later, the following RPM packages must be installed:

•crontabs-1.10-7 or later.

•vixie-cron-4.1-49 or later.

•bzip2-libs-1.0.3 or later.

•ksh-20080202-2 or later

•glibc-2.5 or later

If you are installing Prime Performance Manager on Red Hat Enterprise Linux Version 6 Update 2 or later, the following RPM packages must be installed:

•ksh-20100621-12 or later.

•glibc-2.12-1.47 or later.

You can use the following command to verify that these RPM packages are installed on your server:

rpm -q -a

To obtain RPMs for Red Hat Enterprise Linux, contact your Red Hat representative or download them from the Red Hat website at http://www.redhat.com. (Downloading Red Hat Enterprise Linux RPMs might require a support agreement.)

If you are running SELinux (Security-Enhanced Linux) and using 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'

Network Sizes for Planning Server Requirements

The Prime Performance Manager gateway and unit(s) can be installed on the same server (single deployment) or on separate servers (distributed deployments). Server and operating system requirements depend on the network size. Network sizes are based on the maximum number of:

•Devices

•Layer 3 pseudowires (PWE3s)

•Interfaces—The number of device interface table entries. This number is usually higher than number of physical ports because it includes pseudowires, virtual circuits, VLANs, and other virtual interfaces.

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

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

Maximum Number	Single Deployment				Distributed Deployment
	POC	Medium	Large	Very Large	Very Large	Extremely Large	Super Large
Devices	100	2,000	5,000	10,000	10,000	15,000	25,000
PWE3 links	500	10,000	270,000	540,000	540,000	860,000	1,351,000
Interfaces	5.000	100,000	815,000	1,630,000	1,630,000	2,470,000	4,076,000
Interfaces generating statistics	2,500	50,000	489,000	815,000	815,000	1,125,000	2,447,000

Server Requirements for Single Deployments

In a single Prime Performance Manager deployment, the gateway and unit are installed on the same server. Server requirements are based on the following criteria:

•Set of reports—CPU, memory, interface, and PWE3s.

•Report aging—You can change the aging for both statistics and CSV report files. The statistics and CSV report defaults are:

–15-minute—3 Days

–Hourly—7 Days

–Daily—31 Days

–Weekly—365 Days

–Monthly—1825 Days

Increasing retention time requires additional disk space. Smaller networks can easily increase the time retention in most cases. Larger networks require capacity planning for disk space usage needs.

For single-server deployments, the following additional disk space is required for every 1000 devices averaging 300 interfaces or PWE3s that can generate statistics for each additional day of retention for 15-minute and hourly reports:

–3.2 GB for the database and reports

–7.0 GB for backups

---

Note Adding retention days to daily, weekly, and monthly reports do not impact disk space as significantly as adding retention days to 15-minute and hourly reports.

---

•Hardware or ZFS RAID is recommended for production systems for partitions, storing the database, reports, and backups.

•For high-scale environments, increasing the gateway and unit server JVM heap size to 8-12 GB is recommended. You can change the JVM heap size with the ppm setsvrjvmsize command.

The following topics provide single deployment server requirements:

•Proof of Concept Single Deployment Installation Requirements

•Medium Network Single Deployment Server Requirements

•Large Network Single Deployment Server Requirements

•Very Large Network Distributed Deployment Server Requirements

Proof of Concept Single Deployment Installation Requirements

Table 1-4 shows the single deployment proof of concept Oracle Solaris server requirements. (See Table 1-3 for network size details.)

Table 1-4 Proof of Concept Network Single Deployment Oracle Solaris Server Requirements 

Item	Specifications
Hardware	•Sparc T3-1 or equivalent for non-NEBs-compliant systems •Sparc T5120 or equivalent for non-NEBs-compliant systems •Sparc Netra T5220 or equivalent for NEBs-compliant systems •Sparc Netra T3-1 or equivalent for NEBs-compliant systems
Software	See Table 1-1.
CPU Type	One of the following: •4-core (T5220) •8-core (T512x) •16-core (T3-1)
CPU Number	One
CPU Speed	One of the following: •1.4 GHz (T5120) •1.2 GHz (T5220) •1.65 GHz (T3-1)
Memory (RAM)	8 GB or greater
Swap Space	8 GB or greater
Storage	One 300 GB SAS 10K RPM drive

Table 1-5 lists the proof of concept network single deployment Linux server requirements. (See Table 1-3 for network size details.)

Table 1-5 Proof of Concept Network Single Deployment Linux Server Requirements 

Item	Specifications
Hardware	•Cisco Unified Computing System (UCS) C200M2 for non-NEBs-compliant systems •Oracle Sun Netra X4250 or equivalent for NEBs-compliant systems
Software	See Table 1-2.
CPU Type	One of the following: •4-core (X4250) •6-core (Cisco UCS C200M2 or Cisco UCS C210M2)
CPU Number	One
CPU Speed	2.13 GHz (minimum); 3.0 GHz (recommended)
Memory (RAM)	8 GB or greater
Swap Space	8 GB or greater
Storage	One 146 GB SAS 15K RPM drive

Medium Network Single Deployment Server Requirements

Table 1-6 lists the medium network single deployment Linux server requirements. (See Table 1-3 for network size details.)

Table 1-6 Medium Network Single Deployment Linux Server Requirements 

Item	Specifications
Hardware	•Cisco Unified Computing System (UCS) C200M2 or Cisco UCS C210M2 for non-NEBs-compliant systems •Sun Netra X4250 or equivalent for NEBs-compliant systems
Software	See Table 1-2.
CPU Type	One of the following: •4-core (X4250) •6-core (Cisco UCS C200M2 or Cisco UCS C210M2)
CPU Number	Two
CPU Speed	2.13 GHz (minimum); 3.0 GHz (recommended)
Memory (RAM)	24 GB or greater
Swap Space	12 GB or greater
Storage	• Cisco UCS C210M2—Expansion, Performance, and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Four 146 GB SAS 15K RPM drives –For backups using RAID10: Four 146 GB SAS 15K RPM drives –Requires usage Of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C200M2—Expansion and Performance Option –For OS One 146 GB SAS 15K RPM drive –For database using RAID0: Two 300 GB SAS 15K RPM drives –For backups: One 300 GB SAS 15K RPM drive –Uses LSI Mezzanine RAID controller •Cisco UCS C200M2—Performance Option –For OS: One146 GB SAS 15K RPM drive –For database using RAID0: Two 146 GB SAS 15K RPM drives –For backups: One 300 GB SAS 15K RPM drive –Uses LSI Mezzanine RAID controller •Cisco UCS C200M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For database: One 146 GB SAS 15K RPM drives –For backups: One 300 GB SAS 15K RPM drive •Oracle Netra X4250—Basic Option –For OS: One 300 GB SAS 10K RPM drive –For database using RAID0: Two 300 GB SAS 10K RPM drives –For backups: One 300 GB SAS 10K RPM drive

Table 1-7 shows the single deployment medium network Oracle Solaris server requirements. (See Table 1-3 for network size details.)

Table 1-7 Medium Network Single Deployment Oracle Solaris Server Requirements 

Item	Specifications
Hardware	•Sparc T3-1 or equivalent for non-NEBs-compliant systems •Sparc T5120 or equivalent for non-NEBs-compliant systems •Sparc Netra T5220 or equivalent for NEBs-compliant systems •Sparc Netra T3-1 or equivalent for NEBs-compliant systems
Software	See Table 1-1.
CPU Type	One of the following: •4-core (T5220) •8-core (T512x) •16-core (T3-1)
CPU Number	One
CPU Speed	One of the following: •1.4 GHz (T5120) •1.2 GHz (T5220) •1.65 GHz (T3-1)
Memory (RAM)	12 GB or greater
Swap Space	12 GB or greater
Storage	•Oracle Sparc—Expansion and Performance Option –For OS: One 300 GB SAS 10K RPM drive –For database using ZFS RAID: Four 300 GB SAS 10K RPM drives –For backups using ZFS pool: Two 300 GB SAS 10K RPM drives •Oracle Sparc—Basic Option –For OS: One 300 GB SAS 10K RPM drive –For database using ZFS pool: Two 300 GB SAS 10K RPM drives –For backups: One 300 GB SAS 10K RPM drives

Large Network Single Deployment Server Requirements

Table 1-8 shows the large network Linux server requirements. (See Table 1-3 for network size details.)

Table 1-8 Large Network Single Deployment Linux Server Requirements 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant Systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz
Memory (RAM)	64 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Expansion, Performance, and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Six 146 GB SAS 15K RPM drives –For backups using RAID10: Four 146 GB SAS 10K RPM drives –Requires usage Of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C210M2—Performance Option –For OS: One 146 GB SAS 15K RPM drive –For CSV reports and database using RAID10: Two146 GB SAS 15K RPM drives –For backups: Two 146 GB SAS 10K RPM drives –Requires Usage Of LSI MegaRAID controllers •Cisco UCS C210M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For CSV reports and database using RAID10: Two 146 GB SAS 10K RPM drives –For backups using RAID10: Two 146 GB SAS 10K RPM drive –Uses LSI Mezzanine RAID controller

Table 1-9 shows the large network Oracle Solaris server requirements.

Table 1-9 Large Network Single Deployment Oracle Solaris Server Requirements 

Item	Specifications
Hardware	•Sparc T3-1 or equivalent for non-NEBs-compliant systems •Sparc Netra T3-1 or equivalent for NEBs-compliant systems
Software	See Table 1-1.
CPU Type	16-core (T3-1)
CPU Number	One
CPU Speed	1.65 GHz (T3-1)
Memory (RAM)	64 GB or greater
Swap Space	32 GB or greater
Storage	•Oracle Sparc—Expansion and Performance Option –For OS: One 300 GB SAS 10K RPM drive –For database using ZFS RAID: Six 300 GB SAS 10K RPM drives –For backups using ZFS Pool: Two 300 GB SAS 10K RPM drives •Oracle Sparc—Basic Option –For OS: One 300 GB SAS 10K RPM drive –For database using ZFS RAID: Four 300 GB SAS 10K RPM drives –For backups using ZFS Pool: Two 300 GB SAS 10K RPM drives

Very Large Network Single Deployment Server Requirements

Table 1-10 shows the very large network Linux server requirements. (See Table 1-3 for network size details.)

Table 1-10 Very Large Network Single Deployment Linux Server Requirements 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz (minimum)
Memory (RAM)	96 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Performance and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Eight 146 GB SAS 15K RPM drives –For backups using RAID10: Six146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual Power Supply •Cisco UCS C210M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For CSV reports and database using RAID10: Four 146 GB SAS 10K RPM drives –For backups using RAID0: Four 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers

Server Requirements for Distributed Deployment Installations

In a Prime Performance Manager distributed deployment, the gateway and units are installed on different servers. Server requirements are based on the following criteria:

•Reports:

–Availability—interfaces, pseudowires, and SNMP Ping.

–Resources—CPU and memory

–Transport statistics—interface and pseudowire.

•Report aging—You can change the aging for both statistics and CSV report files. The statistics and CSV report defaults are:

–15-minute—3 Days

–Hourly—7 Days

–Daily—31 Days

–Weekly—365 Days

–Monthly—1825 Days

For distributed deployments, the following additional disk space is required for every 1000 devices averaging 300 interfaces or PWE3s that can generate statistics, for each additional day of retention for 15-minute and hourly reports:

For gateways:

–1.2 GB for database and reports

–2.4 GB for backups

For units:

–2.4 GB for database and reports

–4.8 GB for backups

---

Note Adding retention days to daily, weekly, and monthly reports does not impact disk space as significantly as adding retention days to 15-minute and hourly reports.

---

•Hardware or ZFS RAID is recommended for production systems for partitions, storing the database, reports, and backups.

•For high-scale environments, increasing the gateway and unit server JVM heap size to 8-12 GB is recommended. You can change the JVM heap size with the ppm setsvrjvmsize command.

The following topics provide the distributed network server requirements:

•Very Large Network Distributed Deployment Server Requirements

•Extremely Large Network Distributed Deployment Server Requirements

Very Large Network Distributed Deployment Server Requirements

Table 1-11 shows the very large network gateway server requirements.

Table 1-11 Very Large Network Gateway and Unit With 5,000 Devices Requirements 

Item	Specifications
Hardware	Cisco UCS C210 or Cisco UCS C200M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	64 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Performance and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For CSV Reports and database using RAID10: Eight146GB SAS 15K RPM drives –For backups using RAID10: Six146GB SAS 15K RPM drives –Requires usage of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C210—Performance Option –For OS: One 146 GB SAS 15K RPM drive –For CSV Reports and database using RAID0: Six 146GB SAS 15K RPM drives –For backups using RAID0: Four 146 GB SAS 15K RPM drive –Uses LSI Mezzanine RAID controller •Cisco UCS C210M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For CSV Reports and database using RAID0: Two146GB SAS 15K RPM drives –For backups: Two 146 GB SAS 15K RPM drive

Table 1-12 shows the very large network server requirements for a unit with 10,000 devices.

Table 1-12 Very Large Network Server Requirements for a Unit with 5,000 Devices 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant Systems
Software	See Table 1-2.
CPU Type	6-core (UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	48 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Expansion, Performance and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Six 146 GB SAS 15K RPM drives –For backups using RAID10: Four 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C210M2—Performance Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Four 146 GB SAS 15K RPM drives –For backups using RAID10: Two 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers •Cisco UCS C210M2—Basic Option –For OS: One 146GB SAS 15K RPM drive –For database using RAID10: Two 146 GB SAS 10K RPM drives –For backups using RAID0: Two 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers

Extremely Large Network Distributed Deployment Server Requirements

Table 1-13 shows the extremely large network gateway server requirements.

Table 1-13 Extremely Large Network Gateway Server Requirements 

Item	Specifications
Hardware	Cisco UCS C210 or Cisco UCS C200M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	64 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Performance and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database: One 146 GB SAS 15K RPM drives –For CSV Reports using RAID10: Six 146 GB SAS 15K RPM drives –For backups using RAID10: Six146 GB SAS 15K RPM drives –Requires usage of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C200M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For database: One 146 GB SAS 15K RPM drives –For CSV Reports: Four 146GB SAS 15K RPM drives –For backups: Two 146 GB SAS 15K RPM drive

Table 1-14 shows the extremely large network server requirements for a unit with 10,000 devices:

Table 1-14 Extremely Large Network Server Requirements for a Unit with 10,000 Devices 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	64 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Expansion, Performance, and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Eight 146 GB SAS 15K RPM drives –For backups using RAID10: Six 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C210M2—Basic Option With Additional Performance –For OS: One 146 GB SAS 15K RPM drive –For database using RAID0: Four 146 GB SAS 10K RPM drives –For backups: Two 146 GB SAS 10K RPM drive –Uses LSI Mezzanine RAID controller

Table 1-15 shows the extremely large network server requirements for a unit with 5,000 devices.

Table 1-15 Extremely Large Network Server Requirements for a Unit with 5,000 Devices 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	48 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Expansion, Performance, and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Six 146 GB SAS 15K RPM drives –For backups using RAID10: Four 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual power supply •Cisco UCS C210M2—Performance Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Four 146 GB SAS 15K RPM drives –For backups using RAID10: Two 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual power supply •Cisco UCS C210M2—Basic Option –For OS: One 146GB SAS 15K RPM drive –For database using RAID10: Two 146 GB SAS 10K RPM drives –For backups using RAID0: Two 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers

Super Large Network Distributed Deployment Server Requirements

Table 1-16 shows the super large network gateway server requirements.

Table 1-16 Super Large Network Gateway Server Requirements 

Item	Specifications
Hardware	Cisco UCS C210 or Cisco UCS C200M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	96 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Performance and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For CSV Reports using RAID10: Eight 146 GB SAS 15K RPM drives –For backups using RAID10: Six 146 GB SAS 15K RPM drives –Requires usage of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C210M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For CSV Reports: Six 146 GB SAS 15K RPM drives –For backups: Two 146 GB SAS 15K RPM drive –Requires usage of LSI MegaRAID controllers

Table 1-17 shows the super large network server requirements for a unit with 10,000 devices:

Table 1-17 Super Large Network Server Requirements for a Unit with 10,000 Devices 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	64 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Expansion, Performance, and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Eight 146 GB SAS 15K RPM drives –For backups using RAID10: Six 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual PowerSupply •Cisco UCS C210M2—Basic Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID0: Four 146 GB SAS 10K RPM drives –For backups: Two 146 GB SAS 10K RPM drive –Uses LSI Mezzanine RAID controller

Table 1-18 shows the super large network server requirements for a unit with 5,000 devices.

Table 1-18 Super Large Network Server Requirements for a Unit with 5,000 Devices 

Item	Specifications
Hardware	Cisco UCS C210M2 for non-NEBs-compliant systems
Software	See Table 1-2.
CPU Type	6-core (Cisco UCS C210M2)
CPU Number	Two
CPU Speed	3.0 GHz minimum
Memory (RAM)	48 GB or greater
Swap Space	32 GB or greater
Storage	•Cisco UCS C210M2—Expansion, Performance, and Reliability Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Six 146 GB SAS 15K RPM drives –For backups using RAID10: Four 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers –Dual power supply •Cisco UCS C210M2—Performance Option –For OS: One 146 GB SAS 15K RPM drive –For database using RAID10: Four 146 GB SAS 15K RPM drives –For backups using RAID10: Two 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers •Cisco UCS C210M2—Basic Option –For OS: One 146GB SAS 15K RPM drive –For database using RAID10: Two 146 GB SAS 10K RPM drives –For backups using RAID0: Two 146 GB SAS 10K RPM drives –Requires usage of LSI MegaRAID controllers

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 8.0 or greater (Windows)

•Firefox 3.6.x or greater (Solaris, Linux, and Windows)

Clients can often access Prime Performance Manager using a non-supported browser, for example, Safari (Macintosh) is widely used, but only Internet Explorer 8.0 and Mozilla Firefox 3.6.x are supported.

Network Device Configuration

Network devices must have two-way IP connectivity with the Prime Performance Manager units. Each device must be accessible from the Prime Performance Manager unit. Configure devices to use SNMP community names. Prime Performance Manager requires that the names be at least read-only (RO). Read-write (RW) names can also be used. To implement these requirements, enter the following IOS commands on all Prime Performance Manager-managed devices:

snmp-server community snmp community string RO 1

For more information about these commands, see http://www.cisco.com/univercd/cc/td/doc/product/software/ios122

Prime Performance Manager Ports

Table 1-19 lists the default ports used by the Prime Performance Manager gateway.

Table 1-19 Ports Used by the Prime Performance Manager Gateway

Function	Port
RMI Registry	45742
Login Server	45752
Client	46173-46273 (The range depends on the number of expected units)
HTTP Web Server	4440
Data Server	45751

The Prime Performance Manager unit must know the ports that are used by the Prime Performance Manager gateway. Table 1-20 lists the default ports used by the Prime Performance Manager unit.

Table 1-20 Ports Used by the Prime Performance Manager Unit

Function	Port
Web Server	5440
RMI Registry Port	55742
Data Server Port	55751
Login Server Port	55752
Client Port	56173

Sometimes the default ports cannot be used because they are used by other system functions. If the Prime Performance Manager gateway uses ports not listed in Table 1-19, specify the ports during the Prime Performance Manager unit installation.

No additional configuration is required if a unit uses a non-default port.

During installation, Prime Performance Manager will identify port conflicts. The find available TCP ports, you can enter the following command:

Solaris: netstat -a -n -f inet -P tcp

Linux: netstat -a -n -t

If you use an alternate port, do not use Ports 1 through 1023. These are reserved for system processes. For more information about Prime Performance Manager ports, see the User Guide for the Cisco Prime Performance Manager 1.1.

---

Note In most cases, the default ports will be fine and you will not need to customize the ports that Prime Performance Manager uses.

---