Table Of Contents
Cisco Prime Carrier Management August 2013 Sizing Guide
Preface
Related Documentation
Obtaining Documentation and Submitting a Service Request
System Requirements for the Prime Carrier Management August 2013
Suite Components
Deployment Sizing
Maximum Number of User Accounts Supported
Operating System Matrix
Virtualization Matrix
JRE Matrix
Hardware Matrix
Prime Network Reporting Requirements
Thick Client Matrix
Thin Client Matrix
Database Matrix
Certified Platforms
Upgrading to the Prime Carrier Management August 2013 Suite
Before You Begin
Suite Upgrade Matrix
Cisco Prime Carrier Management August 2013 Sizing Guide
Revised: August 13, 2013, OL-29516-01
1 Preface
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
Related Documentation
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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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
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:
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.
Prime Optical
•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.
Table 1 Deployment Sizing Matrix
Application
|
Maximum Number of Devices
|
Maximum Number of Events per Second 1 ,2
|
Small Network
|
Prime Central
|
200 devices
|
5
|
Prime Network
|
200 devices
|
20
|
Prime Optical
|
200 devices
|
10
|
Prime Performance Manager
|
200 devices
|
—
|
Prime Provisioning
|
200 devices
|
—
|
Medium Network
|
Prime Central
|
2000 devices
|
10
|
Prime Network
|
2000 devices
|
50
|
Prime Optical
|
500 devices
|
30
|
Prime Performance Manager
|
2000 devices
|
—
|
Prime Provisioning
|
2000 devices
|
—
|
Large Network
|
Prime Central
|
5000 devices
|
240
|
Prime Network
|
5000 devices
|
100
|
Prime Optical
|
2000 devices
|
120
|
Prime Performance Manager
|
5000 devices
|
—
|
Prime Provisioning
|
5000 devices
|
—
|
Extremely Large Network
|
Prime Central
|
Contact your Cisco account representative.
|
Prime Network
|
Prime Performance Manager
|
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 2 Operating System Matrix
Operating System
|
OS Version
|
Prime Central
|
Prime Network
|
Prime Optical
|
Prime Performance Manager
|
Prime Provisioning
|
Solaris
|
10
|
—
|
—
|
X
|
—
|
—
|
11
|
—
|
—
|
X
|
—
|
—
|
Linux
|
5.5
|
—
|
X
|
—
|
X
|
X
|
5.6
|
—
|
X
|
—
|
X
|
X
|
5.7
|
—
|
X
|
—
|
X
|
—
|
5.8
|
X
|
X
|
X
|
X
|
X
|
6.2
|
—
|
—
|
X
|
X
|
—
|
6.3
|
—
|
—
|
—
|
X
|
—
|
Virtualization Matrix
Table 3 Virtualization Matrix
Platform
|
Prime Central
|
Prime Network
|
Prime Performance Manger
|
Prime Optical
|
Prime Provisioning
|
VMware ESXi 5.0
|
X
|
X
|
X
|
X
|
X
|
VMware ESX 4.1
|
X
|
—
|
—
|
X
|
—
|
Currently, virtualization is unsupported in the suite High Availability deployments.
JRE Matrix
Table 4 JRE Matrix
Platform
|
Prime Central
|
Prime Network
|
Prime Performance Manger
|
Prime Optical
|
Prime Provisioning
|
6.0
|
X
|
X
|
X
|
X
|
X
|
7.0
|
—
|
—
|
—
|
X
|
—
|
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
Hardware Matrix
Table 5 lists the supported hardware, as well as compute and storage required for each suite component.
Table 5 Hardware Matrix
OS
|
Network Size
|
CPU Type
|
No. of CPUs
|
No. of Virtual CPUs (for VMware Deployments)
|
No. of CPU Cores
|
Core Frequency
|
Disk Space
|
Swap Space
|
RAM
|
Backup Disk Space
|
|
|
Linux
|
Small
|
Intel Xeon E5540
|
2
|
8
|
4
|
2.53 GHz
|
144 GB
|
24 GB
|
24 GB
|
—
|
Medium
|
Intel Xeon E7-2830
|
2
|
24
|
8
|
2.13 GHz
|
350 GB
|
48 GB
|
48 GB
|
—
|
Large
|
Intel Xeon E7-2830
|
2
|
32
|
8
|
2.13 GHz
|
650 GB
|
64 GB
|
64 GB
|
—
|
|
|
Linux
|
Small
|
Intel Xeon
X5550
|
1
|
8 or 12
|
4 or 6
|
2.66 GHz
|
300 GB
|
10 GB
|
16 GB
|
70 GB/day
|
Medium
|
Intel Xeon
X5550
|
2
|
8 or 12
|
4 or 6
|
2.66 GHz
|
750 GB
|
10 GB
|
32 GB
|
160 GB/day
|
Large
|
Intel Xeon
X5670
|
2
|
24
|
12
|
3.0 GHz
|
1500 GB
|
10 GB
|
64 GB
|
320 GB/day
|
Prime Network Unit Servers 1,2
|
Linux
|
Small
|
Intel Xeon
X5550
|
1
|
8 or 12
|
4 or 6
|
2.66 GHz
|
10 GB
|
10 GB
|
16 GB
|
—
|
Medium
|
Intel Xeon X5550
|
2
|
8 or 12
|
4 or 6
|
2.66 GHz
|
10 GB
|
10 GB
|
32 GB
|
—
|
Large
|
Intel Xeon X5670
|
2
|
24
|
12
|
3.0 GHz
|
10 GB
|
10 GB
|
64 GB per 5000 NEs
|
—
|
|
|
Solaris
|
Small
|
Oracle SPARC T3
|
1
|
16
|
4
|
1.415 GHz
|
131 GB
|
12 GB
|
8 GB
|
101 GB
|
Medium
|
Oracle SPARC T3
|
1
|
32
|
4
|
1.415 GHz
|
236 GB
|
24 GB
|
16 GB
|
208 GB
|
Large
|
Oracle SPARC T3
|
1
|
64
|
4
|
1.415 GHz
|
420 GB
|
48 GB
|
32 GB
|
394 GB
|
Linux
|
Small
|
Intel Xeon 5620
|
2
|
1
|
4
|
2.40 GHz
|
131 GB
|
12 GB
|
24 GB
|
101 GB
|
Medium
|
Intel Xeon 5640
|
2
|
2
|
4
|
2.67 GHz
|
236 GB
|
24 GB
|
24 GB
|
208 GB
|
Large
|
Intel Xeon 5640
|
2
|
8
|
4
|
2.67 GHz
|
420 GB
|
48 GB
|
48 GB
|
394 GB
|
Prime Performance Manager 1,2,4
|
Linux
|
Small
|
Intel Xeon 5600 or E5-2400
|
1
|
4 or more
|
4 or more
|
3.0 GHz
|
1*146-GB SAS 15K RPM drive
|
8 GB
|
8 GB
|
1*146-GB SAS 15K RPM drive
|
Medium
|
Intel Xeon 5600 or E5-2400
|
1
|
6 or more
|
6 or more
|
3.0 GHz
|
1*146-GB SAS 15K RPM drive for OS
1*146-GB SAS 15K RPM drive for database
|
12 GB
|
24 GB
|
1*300-GB SAS 10K RPM drive
|
Large
|
Intel Xeon 5600 or E5-2600
|
2
|
6 or more
|
6 or more
|
3.0 GHz
|
1*146-GB SAS 15K RPM drive for OS
4*300-GB SAS 10K RPM drives for CSV reports and database using RAID10
|
32 GB
|
64 GB
|
6*300-GB SAS 10K RPM drives for backups using RAID10 (requires use of LSI MegaRAID controllers)
|
|
|
Linux
|
Small
|
Intel Xeon X5550
|
1
|
2 per core
|
4
|
2.66 GHz
|
73 GB
|
8 GB
|
8 GB
|
—
|
Medium
|
Intel Xeon X5550
|
2
|
2 per core
|
4
|
2.66 GHz
|
73 GB
|
16 GB
|
16 GB
|
—
|
Large
|
Intel Xeon X5670
|
2
|
2 per core
|
6
|
2.93 GHz
|
146 GB
|
32 GB
|
24 GB
|
—
|
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).
Table 6 Prime Network Reporting Requirements
Platform/OS
|
Network Size
|
GW additional RAM (both IM and Pentaho)
|
Unit Additional RAM (for IB upload)
|
Total Data Disk Space on storage (with backup)
|
Additional Processing Disk Space on PN Unit and PN GW
|
Linux
|
Small
|
10 GB
|
2 GB
|
275 GB
|
8 GB
|
Medium
|
16 GB
|
4 GB
|
700 GB
|
20 GB
|
Large
|
20 GB
|
4 GB
|
1400 GB
|
40 GB
|
Thick Client Matrix
Table 7 lists the supported thick client hardware for Prime Network and Prime Optical.
Table 7 Thick Client Matrix
Suite Component
|
Platform/Hardware
|
Total RAM
|
Total CPU
|
Disk Space
|
Prime Network
|
Windows PC
|
2 GB
|
Pentium IV, 2.66-GHz or better processor
|
200 MB
|
Prime Optical
|
Solaris workstation
|
512 MB
|
—
|
750 MB
|
Linux workstation
|
512 MB
|
—
|
750 MB
|
Windows PC
|
512 MB
|
—
|
750 MB
|
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
|
X
|
X
|
Firefox 17 ESR
|
X
|
X
|
Firefox 20
|
X
|
X
|
Internet Explorer 8.0
|
X
|
X
|
Internet Explorer 9.0
|
—
|
X
|
For older Firefox browsers, please see: http://download.cdn.mozilla.net/pub/firefox/releases.
Database Matrix
Table 9 lists the database requirements for the suite components. The sizing is the same for both external and embedded Oracle databases.
Table 9 Database Matrix
Version
|
Platform/OS
|
Network Size
|
RAM
|
Swap Space
|
Total Disk Space
|
Backup Disk Space
|
Prime Central—External and Embedded Oracle
|
Oracle 11gR2
|
Linux
|
Small
|
12 GB
|
12 GB
|
140 GB
|
—
|
Medium
|
16 GB
|
16 GB
|
250 GB
|
—
|
Large
|
32 GB
|
24 GB
|
433 GB
|
—
|
Prime Network—External and Embedded Oracle
|
Oracle 11gR2
|
Linux
|
Small
|
24 GB
|
12 GB
|
1302 GB
|
510 GB
|
Medium
|
24 GB
|
24 GB
|
3054 GB
|
1163 GB
|
Large
|
48 GB
|
48 GB
|
5934 GB
|
2226 GB
|
Prime Optical—External and Embedded Oracle (with PM Data Collection Enabled)
|
Oracle 11g R2
|
Solaris
|
Small
|
8 GB
|
12 GB
|
133 GB
|
101 GB
|
Medium
|
16 GB
|
24 GB
|
250 GB
|
208 GB
|
Large
|
32 GB
|
48 GB
|
458 GB
|
394 GB
|
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
|
Prime Performance Manager
|
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 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.
Table 10 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
|
Medium
|
Cisco UCS B-Series Blade Server
|
Large
|
Cisco UCS B-Series Blade Server
|
Prime Optical
|
Small
|
Cisco UCS C-Series Rack Server
|
Oracle UltraSPARC T2, UltraSPARC T2+, and SPARC64 (UltraSPARC-IIIi)
|
Medium
|
Cisco UCS C-Series Rack Server
|
Oracle UltraSPARC T2, UltraSPARC T2+, and SPARC64 (UltraSPARC-IIIi and US-IV)
|
Large
|
Cisco UCS C-Series Rack Server
|
Oracle UltraSPARC T2, UltraSPARC T2+, and SPARC64 (UltraSPARC-IIIi and US-IV)
|
Prime Performance Manager
|
Small
|
Cisco UCS C200M2 for non-NEBs-compliant systems
|
Medium
|
Cisco UCS C200M2/C240M3 for non-NEBs-compliant systems
|
Large
|
Cisco UCS C240M3 for non-NEBs-compliant systems
|
Prime Provisioning
|
Small
|
Cisco USC C200
|
Medium
|
Cisco UCS C200
|
Large
|
Cisco UCS C210
|
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.
|
Upgrading Prime Central.
|
2
|
Upgrade to Prime Central Fault Management 1.2.
|
Upgrading to Prime Central Fault Management 1.2.
|
3
|
(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.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.
|
5
|
(Prime Optical only) Restore the copied dmid.xml file in the Prime-Optical-installation-directory/
prime_integrator/ directory.
|
—
|
6
|
(Prime Optical or Prime Provisioning only) Restart the integration layer.
|
Starting and Stopping the Prime Central Components.
|
7
|
(Prime Provisioning installed in standalone mode only) Run the DMIntegrator.sh script on Prime Provisioning.
|
Integrating Prime Provisioning with Prime Central.
|
8
|
Verify that the suite upgrade succeeded.
|
Verifying the Upgrade.
|
9
|
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.
|
Manually Registering Fault Management to Retrieve Alarm Data.
|
