The Prime Carrier Management suite for service providers supports integrated lifecycle management of next-generation networks and services based on a business-centric framework. This comprehensive suite supports major Cisco architectures, including IP Next-Generation Network (NGN), next-generation mobile internet, and cloud intelligent networks.
Note Cisco IP NGN has been renamed as Cisco Evolved Programmable Network (EPN). Please keep this in mind when viewing the suite and application documentation for the upcoming Cisco Prime Carrier Management release.
As shown in Figure 1, Prime Carrier Management includes the following suite components, which are accessible through the Cisco Prime Central portal.
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 Carrier Management.
Suite Component Version
Cisco Prime Central 1.3
Plays the role of the presentation tier for the entire suite. The portal provides a single point of access (single sign-on) to the suite components, plus central access to the experience lifecycle tasks.
Cisco Prime Network 4.1
Provides management of packet networks, including access, aggregation, edge, and MPLS core.
Cisco Prime Optical 10.0
Provides efficient and productive optical infrastructure management for fault, configuration, performance, and security.
Cisco Prime Performance Manager 1.5
Provides performance statistics and reports for service provider and large enterprise networks, including access, edge, distribution, core, mobile backhaul, Carrier Ethernet, and core MPLS networks.
Cisco Prime Provisioning 6.6
Provides automated resource management and rapid profile-based provisioning capabilities for Carrier Ethernet, Multiprotocol Label Switching (MPLS), and Packet Transport technologies.
Figure 1 Prime Carrier Management Suite Components
New Features and Enhancements
Prime Carrier Management includes the following features and enhancements for next-generation network support:
Support for Metro Ethernet Forum (MEF)-compliant devices
Support for Gigabit-capable Passive Optical Network (GPON) devices
Support for Redhat Enterprise Linux 6.4.
Enhanced physical inventory support for Network Convergence System (NCS) 6000 series devices
Ability to perform key alarm management tasks in Prime Central, Prime Network, Prime Optical, and Prime Performance Manager (when configure in Suite mode) and keep the information for those tasks in sync among the applications.
Enhanced 3GPP NBI support
Prime Carrier Management April 2014 Bugs
For more information on a specific bug or to search all bugs in the Prime Carrier Management suite, see Using the Bug Toolkit.
Alarms generated for GPON devices are not cleared from the Prime Network Events client after they have been resolved. As a result, users will not be able to identify the alarms that are no longer active.
After upgrading to Prime Optical 10.0, the Prime Optical 9.8 integration layer is still listed in Prime Central’s Suite Monitoring portlet.
To reproduce the problem:
1. On a server where Prime Optical 9.8 is installed and integrated with Prime Central 1.2, shut down Prime Optical:
2. Use the Data Migrator Wizard to export information from Prime Optical.
3. Make a copy of the /opt/CiscoTransportManagerServer/prime_integrator/dmid.xml file and save it.
4. Upgrade to Prime Central 1.3.
5. Uninstall Prime Optical 9.8, and then install Prime Optical 10.0.
6. Import data from Prime Optical 10.0 using the Data Migrator Wizard.
7. Restore the /opt/CiscoTransportManagerServer/prime_integrator/dmid.xml you saved in Step 3.
8. Integrate Prime Optical 10.0 with Prime Central 1.3.
9. Start Prime Optical 10.0:
10. Start Prime Central 1.3 and then open the Suite Monitoring portlet (
Administration > System > Suite Monitoring
To resolve the problem, select the Prime Optical 9.8 integration layer radio button and then click
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.
Physical terminal points information is not displayed for ASR 5500 and CPT 600 devices in the Prime Central Common Inventory portlet.
To reproduce the problem:
1. Log in to the Prime Central portal.
2. Cross-launch Prime Network and discover any new devices.
3. In Prime Central, open the Common Inventory portlet and click the Expand icon for either an ASR 5500 or CPT 600 device to view its physical inventory data.
4. Expand the chassis and select a card.
Physical terminal point information for that card is not displayed.
Using the Bug Toolkit
To search for bugs in the Prime Carrier Management suite, you must look up bugs for each application in the suite (Prime Central, Prime Network, Prime Optical, Prime Performance Manager, and Prime Provisioning).
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
Obtaining Documentation and Submitting a Service Request
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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.