Table Of Contents
Cisco Prime Carrier Management August 2013 Sizing Guide
Revised: August 13, 2013, OL-29516-01
This guide lists the baseline system requirements for all components in the Cisco Prime Carrier Management August 2013 suite.
The primary audience for this guide is network operations personnel and system administrators. This guide assumes that you are familiar with the following products and topics:
•Basic internetworking terminology and concepts
•Network topology and protocols
•Microsoft Windows 7 and Windows XP
•Solaris and Linux administration
•Oracle database administration
•Telecommunication Management Network (TMN) architecture model
See the Cisco Prime Carrier Management August 2013 Documentation Overview for a list of related guides.
Note We sometimes update the documentation after original publication. Therefore, you should review the documentation on Cisco.com for any updates.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS version 2.0.
2 System Requirements for the Prime Carrier Management August 2013
This section lists suite-level sizing guidelines for small, medium, and large networks. For extremely large or high-end networks, refer to the application documentation or contact your account representative.
Table 1 lists the typical deployment size for each suite component in small, medium, and large networks. The deployment sizing assumes that the devices are distributed as follows:
Prime Central and Prime Network: Carrier Ethernet (CE), Multiprotocol Label Switching (MPLS), or IP Radio Access Network (RAN)
•CE: 2% provider devices, 8% network provider edge, 80% user provider edge, 10% customer edge.
•MPLS: 5% core routers, 95% customer premises equipment.
•IP RAN: 15% aggregation, 30% cell sites, 55% Layer 2 switches.
•Data Center: (11% compute + 56% aggregation + 11% storage, 22% Virtual) for every 576 devices where:
–Compute = 64 systems * (8 chassis + 2 fixed interface cards [FICs]).
–Aggregation = 64 systems * (two Nexus 7K + Cisco Catalyst 6500 with two chassis in VSS mode + two Cisco ASR 1000s).
–Storage = 64 storage systems.
–Virtual = 64 systems * two Nexus 1000v.
•Small network—Up to 200 devices with 100 links, 5000 circuits, and 20,000 interfaces generating statistics.
•Medium network—Up to 500 devices with 250 links, 15,000 circuits, and 50,000 interfaces generating statistics.
•Large network—Up to 2000 devices with 1000 links, 50,000 circuits, and 200,000 interfaces generating statistics.
Prime Performance Manager
•Small network—Up to 200 devices with up to 500 PWE3 links, 5000 interfaces, and 2500 interfaces generating statistics.
•Medium network—Up to 2000 devices with up to 10,000 PWE3 links, 100,000 interfaces, and 50,000 interfaces generating statistics.
•Large network—Up to 5000 devices with up to 270,380 PWE3 links, 815,260 interfaces, and 489,500 interfaces generating statistics.
1 For Prime Central, events are the northbound interface events received from the applications.
2 Prime Performance Manager and Prime Provisioning do not process events.
Maximum Number of User Accounts Supported
Prime Central supports up to 150 simultaneous users, all of whom can see their own customized view of the Prime Central portal.
Note the following:
•In Prime Central, 30 users can perform all portal operations concurrently. The remaining 120 users can monitor data, but it is not recommended that they perform memory-intensive operations such as application cross-launch or user management.
•A single Prime Central user can have up to ten cross-launched application windows open simultaneously. If a user tries to open an eleventh window, the user cannot proceed without first closing one of the open windows.
•If users stagger the cross-launches over a period of 3 to 5 minutes, Prime Central supports up to 50 cross-launches of Prime Network and Prime Performance Manager.
•The number of application cross-launches Prime Central supports depends on:
–CPU and memory available on a user's machine.
–CPU, memory, and connections available on the machines on which the applications run.
Operating System Matrix
Table 2 lists the supported operating system (OS) for each suite component. Support is provided across the suite for Red Hat Enterprise Linux 5.8 (RHEL 5.8)
Table 3 Virtualization Matrix
Platform Prime Central Prime Network Prime Performance Manger Prime Optical Prime Provisioning
VMware ESXi 5.0
VMware ESX 4.1
Currently, virtualization is unsupported in the suite High Availability deployments.
Table 4 JRE Matrix
Platform Prime Central Prime Network Prime Performance Manger Prime Optical Prime Provisioning
In suite mode, Prime Optical must be configured to run the following JRE versions:
•Prime Optical server—JRE 7.0
•Prime Optical client and integration layer—JRE 6.0
Table 5 lists the supported hardware, as well as compute and storage required for each suite component.
1 Oversubscription of vCPU for any given suite application will have a negative impact in terms of performance.
2 The Prime Carrier Management Suite is not certified to operate in a single server at this time. A single server deployment for the entire suite should only be used in a proof of concept setup.
3 For Prime Optical, total disk space assumes performance monitoring (PM) data collection is enabled, with 30 days of data saved. The total disk space includes the /ctm_backup partition reserved for database backups. If the database is installed on a separate server, the disk requirements are different; see "Disk Space and Partition Requirements for the Prime Optical Server when Installing the Prime Optical Server and Oracle on Separate Workstations" in the Cisco Prime Optical 9.8 Installation Guide.
4 For Prime Performance Manager, the backup disk space values are for the default report selection. If you customize the report selection and enable additional reports, the backup disk space increases.
5 For Prime Provisioning, there are no formal disk requirements for backup space allocation. The disk space required is based on the backup policy that your workstation administrators implement. Factors that affect sizing include frequency of complete versus partial backups, and the length of time to retain backups. For maximum performance, allocate swap space to a separate disk.
Prime Network Reporting Requirements
Table 6 includes the memory needed for the Reporting engine: Pentaho. The storage sizes represent 180 days of retained data. The local disk size required on the GW and unit is required for processing of the records before they are uploaded to the DB (both on GW and on each Unit).
Thick Client Matrix
Table 7 lists the supported thick client hardware for Prime Network and Prime Optical.
Thin Client Matrix
Table 8 lists the thin client browser support for the Suite: Prime Central, Prime Optical (online help and the NE Audit tool only), Prime Network Change and Configuration Management, Prime Performance Manager, and Prime Provisioning. Each component may support more versions, please refer to the suite application documentation for details on broader browser support.
Table 8 Thin Client Matrix
Browser Windows XP Windows 7
Firefox 17 ESR
Internet Explorer 8.0
Internet Explorer 9.0
For older Firefox browsers, please see: http://download.cdn.mozilla.net/pub/firefox/releases.
Table 9 lists the database requirements for the suite components. The sizing is the same for both external and embedded Oracle databases.
Table 10 lists the platforms that were used for certification during Prime Carrier Management August 2013 suite testing. You can use other comparable platforms, provided that you meet the minimum requirements for CPU, RAM, and so on.
3 Upgrading to the Prime Carrier Management August 2013 Suite
This section explains how to upgrade to the Prime Carrier Management August 2013 suite.
Before You Begin
•If you are using an external Prime Central database, back it up manually.
•If you are using an embedded (local or remote) Prime Central database, it is recommended (but not required) that you back it up manually before upgrading.
•Back up your application database.
Caution During the upgrade, do not unregister any of the applications from Prime Central.
Suite Upgrade Matrix
Table 11 lists the high-level tasks to upgrade Prime Central and the suite components.
Table 11 Suite Upgrade Matrix
Step Number High-Level Task For More Information, See... 1
Upgrade to Prime Central 1.2.
Note Cisco might have released a Prime Central 1.2 patch after this document was last published online. Contact your Cisco account representative for the latest patch.
Upgrade to Prime Central Fault Management 1.2.
(Prime Optical only) Make a copy of the Prime-Optical-installation-directory/prime_integrator/
Upgrade the application to the required component version:
•Cisco Prime Network 4.0
•Cisco Prime Optical 9.8
•Cisco Prime Performance Manager 1.4
•Cisco Prime Provisioning 6.5
Note Cisco might have released patches to the required component versions after this document was last published online. Contact your Cisco account representative for the latest component patch that is compatible with Prime Central 1.2.
•Cisco Prime Network 4.0 Installation Guide to upgrade to Prime Network 4.0 from an earlier release.
•Cisco Prime Optical 9.8 Installation Guide to upgrade to Prime Optical 9.8 from an earlier release.
During the Prime Optical upgrade, be sure to install Prime Optical in standalone mode, not suite mode.
•Cisco Prime Performance Manager 1.4 Quick Start Guide to upgrade from Prime Performance Manager 1.3 to 1.4.
•Cisco Prime Provisioning 6.5 Installation Guide to upgrade to Prime Provisioning 6.5 from an earlier release.
If you install Prime Provisioning in standalone mode rather than suite mode during the upgrade, be sure to complete Step 7.
(Prime Optical only) Restore the copied dmid.xml file in the Prime-Optical-installation-directory/
(Prime Optical or Prime Provisioning only) Restart the integration layer.
(Prime Provisioning installed in standalone mode only) Run the DMIntegrator.sh script on Prime Provisioning.
Verify that the suite upgrade succeeded.
If you plan to upgrade Prime Network, rerun the PrimeNetworkRegistration.sh script so that Prime Central Fault Management can retrieve fault data from Prime Network.