Table of Contents
- Basic internetworking terminology and concepts
- Network topology and protocols
- Microsoft Windows 7 and Windows XP
- Linux administration
- Oracle database administration
- Telecommunication Management Network (TMN) architecture model
See the Cisco Prime Carrier Management April 2014 Documentation Overview for a list of related guides.
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.
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:
- 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:
- 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.
- 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.
- 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:
Table 5 lists the supported hardware, as well as compute and storage required for each suite component.
Prime Network Unit Servers 1 , 2
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.
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).
Table 7 lists the resources needed to support 200 devices within a Carrier Ethernet or Data Center deployment. The deployment sizing assumes that the devices are distributed as follows: 70% access devices, 10% aggregation devices, 15% distribution devices, and 5% core devices.
Table 10 lists the supported thick client hardware for Prime Network and Prime Optical.
Table 11 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.
For older Firefox browsers, please see: http://download.cdn.mozilla.net/pub/firefox/releases .
Table 12 lists the database requirements for the suite components. The sizing is the same for both external and embedded Oracle databases.
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.
- 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.
Table 14 lists the high-level tasks to upgrade Prime Central and the suite components.
See “Upgrading Prime Central” in the Cisco Prime Central 1.3 Quick Start Guide .
See “Upgrading to Prime Central Fault Management 1.3” in the Cisco Prime Central 1.3 Quick Start Guide .
- 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.
- Cisco Prime Network 4.1 Installation Guide to upgrade to Prime Network 4.1 from an earlier release.
- Cisco Prime Optical 10.0 Installation Guide to upgrade to Prime Optical 10.0 from an earlier release.
- Cisco Prime Performance Manager 1.5 Quick Start Guide to upgrade from Prime Performance Manager 1.4 to 1.5.
- Cisco Prime Provisioning 6.6 Installation Guide to upgrade to Prime Provisioning 6.6 from an earlier release.
See “Starting and Stopping the Prime Central Components” in the Cisco Prime Central 1.3 Quick Start Guide .
See “Integrating Prime Provisioning with Prime Central” in the Cisco Prime Central 1.3 Quick Start Guide .
See “Verifying the Upgrade” in the Cisco Prime Central 1.3 Quick Start Guide .
See “Manually Registering Fault Management to Retrieve Alarm Data” in the Cisco Prime Central 1.3 Quick Start Guide .