Related Documentation

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.

System Requirements for the Prime Carrier Management April 2014
Suite Components

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.

Deployment Sizing

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:

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 who 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 30 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.

Suite Integration – Multiple Instance Application Support

Prime Central supports multiple instances of Prime Network and Prime Optical, for a total of five instances, in any combination. For example:

3.Oversubscription of vCPU for any given suite application will have a negative impact in terms of performance.

4.The Prime Carrier Management Suite is also deployable onto a single small server.

5.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 10.0 Installation Guide.

6.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.

7.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 gateway and unit is required to process records before they are uploaded to the database (both on the gateway and each unit).

Prime Performance Manager embeds a distributed database that is part of the installation and is not accessible by any other external process.

Prime Provisioning—External Oracle

Oracle 11g R2

Linux

Small

24 GB

12 GB

133 GB

101 GB

Medium

24 GB

24 GB

250 GB

208 GB

Large

48 GB

48 GB

458 GB

394 GB

Certified Platforms

Table 13 lists the platforms that were used for certification during Prime Carrier Management April 2014 suite testing. You can use other comparable platforms, provided that you meet the minimum requirements for CPU, RAM, and so on.

Table 13 Platforms Used for Certification

Network Size

Platforms Tested

Prime Central

Small

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

HP ProLiant DL580 Server

Medium

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

HP ProLiant DL580 Server

Large

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

HP ProLiant DL580 Server

Prime Network

Small

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Medium

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Large

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Prime Optical

Small

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Medium

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Large

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Prime Performance Manager

Small

Cisco UCS C22M3/C220M3/C200M2/B200M3

Medium

Cisco UCS C240M3/C22M3/C200M2/B200M2

Large

Cisco UCS C240M3/C220M3/B200M3

Prime Provisioning

Small

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Medium

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Large

Cisco UCS B-Series Blade Server

Cisco UCS C-Series Rack Server

Upgrading to the Prime Carrier Management April 2014 Suite

This section explains how to upgrade to the Prime Carrier Management April 2014 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.

(Prime Optical only) Make a copy of the
Prime-Optical-installation-directory
/prime_integrator/
dmid.xml file.

—

4

Upgrade the application to the required component version:

Cisco Prime Network 4.1

Cisco Prime Optical 10.0

Cisco Prime Performance Manager 1.5

Cisco Prime Provisioning 6.6

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.3.