Cisco Prime Carrier Management provides end-to-end management, from access to the core, helping enable carrier-class delivery of next-generation voice, mobile, cloud, and managed services. With the modular architecture, you have the flexibility to deploy the entire integrated suite or do it incrementally as you grow your business, depending on your needs.
The Cisco Prime Carrier Management solution consists of the following applications, which are accessible through the Cisco Prime Central portal:
Cisco Prime Network—Provides management of packet networks, including access, aggregation, edge, Multiprotocol Label Switching (MPLS) core, and Evolved Packet Core (EPC).
Cisco Prime Optical—Provides efficient and productive optical infrastructure management for fault, configuration, performance, and security.
Cisco Prime Performance Manager—Provides performance statistics and reports for service provider and large enterprise networks, including access, edge, distribution, core, mobile backhaul, Carrier Ethernet, MPLS core, and EPC networks.
Cisco Prime Provisioning—Provides automated resource management and rapid, profile-based provisioning capabilities for Carrier Ethernet, Radio Access Network (RAN) backhaul, MPLS, and Packet Transport technologies.
Prime Central is compatible with the application versions listed in Table 1.
Table 2 lists the new features and enhancements in Prime Central 1.3.
Table 2 New and Enhanced Features in Prime Central 1.3
Gigabit-capable Passive Optical Network (GPON) and Metro Ethernet Forum (MEF) device support
Physical inventory support for GPON and MEF-compliant devices.
Redhat Enterprise Linux (RHEL) 6.4 support
Support for RHEL 6.4.
Email and SMS alarm notification support
Support for the notification of users via email and SMS messages whenever a critical or major alarm is generated.
Support of cross-application alarm management tasks
Ability to perform key alarm management tasks in Prime Central, Prime Network, Prime Optical, and Prime Performance Manager (when configured in Suite mode) and keep the information for those tasks in sync among the applications.
Fault Source Management portlet
Allows you to identify and determine the current status of the sources from which Prime Central gathers your network’ s alarm and trap information.
Cross-launch to the Cisco ME 4600 Series Agora-NG network provisioning platform
Ability to cross-launch the Cisco ME 4600 Series Agora-NG network provisioning platform in order to manage GPON and active Ethernet networks.
Geographical disaster recovery and operational redundancy
Ability to configure geographical disaster recovery in order to mitigate the downtime brought about when Prime Central or another Cisco Prime application goes down.
Prime Central 1.3 Bugs
For more information on a specific bug or to search for all bugs in a particular Prime Central release, see Using the Bug Search Tool.
When running in an Internet Explorer browser, Prime Central prompts for your username and password after you generate a report in the Alarm Report portlet.
To reproduce the problem:
1. With Prime Central and Fault Management 1.3 already installed, create a new user in Prime Central that has access to both Prime Network and Fault Management.
2. Log in to Prime Central as the new user.
3. Select Assure > Prime Central Fault Management > Alarm Report.
4. Generate a report, such as the Ack_Events_Details report.
5. Click Home to return to the Prime Central home page.
You are prompted to enter your username and password.
Click Cancel to close the Windows Security dialog box. You do not need to enter your username and password here.
After stopping and restarting an external Oracle database, you are able to log in to the Prime Central portal but portal content does not load.
To reproduce the problem:
1. Install Prime Central and the integration layer along with an external Oracle database.
2. Reboot the external Oracle database server.
3. Stop and then restart the Oracle service.
4. Start the listener and database without starting the Prime Central portal or integration layer.
5. Open the portal login page and enter a valid username and password.
The Prime Central portal hangs while vCenter and Unified Computing System (UCS) devices are being synchronized.
This problem was observed in a setup where Prime Network is integrated with Prime Central, managing 100 UCS devices and two vCenter devices with 500 VMs configured. After initiating synchronization from Prime Central’s Common Inventory portlet, the portal hangs and is not accessible for 2 hours.
Fault Management was observed to go down occasionally in a setup where Prime Central, the Prime Central integration layer, Fault Management, and an embedded Oracle database are installed on the same server managing 470 UCS devices.
Contextual cross-launch of the Cisco ME 4600 Series Agora-NG EMS from the Common Inventory portlet may occasionally not work due to Agora-NG’s inability to fully discover certain ME 4600 Series devices, such as the ME 4620. (Refer to CSCun59574 for a description of the root cause of this problem.)
ME 4600 OS 3.1.1 is limited to three concurrent connections. Typically, each management component uses at least one connection, and when more than three management components connect to same ME 4600 Series device, this issue can occur.
Using the Bug Search Tool
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
All product documents are accessible except for images, graphics, and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact firstname.lastname@example.org.
Obtaining Documentation and Submitting a Service Request
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.