PDF(209.5 KB) View with Adobe Reader on a variety of devices
Updated:July 31, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Prime Network 4.3.2 provides service providers and other network operators with a comprehensive assurance and device management solution for IP next-generation networks (NGNs), mobility, data center, and cloud. It is offered as a standalone application and as a fully integrated component of the Cisco Prime Carrier Management suite for customers needing end-to-end network management lifecycle capabilities. It provides standards-based interfaces to integrate with OSS applications.
The Cisco Prime Network 4.3.2 primarily supports the following features and enhancements:
Path Tracer support on FEC129 Pseudowire
Support for adding Element IPs to the database manually for Prime Central-Fault Management Resync
Long Description option in systems and security event notification
Platform: RedHat 6.8 support with latest RPMs
Virtual context VRF for back-up and configuration
Oracle Patch update
Suppression of IPv6 false service alarms on Virtual Interfaces
StarOS Alarm Clear Correlation and Alarm correlation granularity
Note Prime Network supports third-party devices through Cisco Advanced Services engagement. As of release 4.2, Prime Network will not natively support third-party devices, and a Cisco Advanced Services contract will be required for their enablement and support.
New Features and Enhancements
The following topics describe the new features and enhancements introduced in Prime Network 4.3.2:
Red Hat 6.8 64-bit Server Edition (English language) is supported in Prime Network 4.3.2. It can run in a virtual environment and is supported on VMware ESXi version 4.0 and 5.5.
Install Prime Network GUI clients from thick and thin clients in a remote PC (Windows 10 OS).
Element IP in Tickets and Integration Changes
Ability to add managed elements to the database manually for Prime Central-Fault Management Resync.
Note For this Element IP in Prime Central-Fault Management Resync feature to be supported in setups, which are upgraded to Prime Network 4.3.2, a BQL needs to be executed. For more information about the steps see the Prime Network 4.3.2 Installation Guide.
Oracle Patch update
You need to install the Oracle Patch in Prime Network with Embedded Oracle 12c to authenticate several security vulnerabilities. Ensure that the following updates are performed in Prime Network:
During Prime Network fresh Installation with Embedded Oracle 12c, the Oracle 12c July 2016 patch is installed automatically.
During Prime Network upgrade from 4.2.0 onwards, a prompt to Install Oracle 12c July 2016 Patch is displayed. Click Yes to install the Oracle 12c July 2016 patch or click No to skip the Patch installation.
This section provides important information of which you should be aware before using Prime Network 4.3.2.
Installation and Upgrade
Before performing any fresh installation of High Availability (HA), ensure that any label used by any cluster service to name a distinct block device on any node in the cluster, must be unique across all block devices on the nodes of the cluster. You need to run the command on all nodes of the cluster, and cross check across all results before configuring local HA cluster because, a label used in a cluster service may not be reused by any block device with a different UUID which is listed by command 'blkid'.
Non-Starting of Compliance Engine
If the compliance engine does not start, follow the below steps:
Before upgrading to 184.108.40.206, take the backup file nccmDatabase.properties that is located in PNHOME/utils/independent/compliance/resources/server/global/nccmDatabase.properties.
After upgrading to 220.127.116.11, replace the backed up file nccmDatabase.properties.
Perform cmctl restart.
The Unconfigured VDC in the logical inventory shows configuration detail with empty data.
Differentiation between Unconfigured VDC and suspended VDC in Prime Network is not available.
PN-IL Health Monitor
By default, the PN-IL health monitor is disabled.
CCM Environment Limitations
1. The XMP process requires 64-bit Java environment.
2. The number of Linux memory pages should be increased to 8718 to support CCM.
To increase the Linux memory page size, perform the following steps:
a. Login to the Linux server as a pnuser.
b. Increase the number of pages in the server by entering the following command: sysctl -w vm.nr_hugepages=8718
c. View the changes by entering the following command: cat /proc/meminfo | grep Huge
Limitations in Compliance Manager
1. In Compliance Audit, few system AAA service policies show incorrect audit violations. For more information, see CSCvm56361.
2. In Compliance Audit, few Fix CLI commands are applied twice. For more information, see CSCvm84162.
Workflow and Activation Replaced With Transaction Manager
Activation and workflow features have been replaced with Transaction Manager. These features are no longer available in Prime Network.
Configuration Audit Features Available Only upon Upgrade
The configuration audit feature in Change and Configuration Management is deprecated and is being replaced with Compliance Audit. When you upgrade to Prime Network Version 4.3.2, the system prompts you about the Configuration feature. Based on your input, the Configuration Audit feature is enabled or disabled.
Cable Technology - uBR10K Devices
For uBR10K devices, cable modeling for Upstream and Downstream channels and complete modeling for the MC20X20V and MC3GX60V line cards will be only supported from versions 12.2(33)SCG5 and higher.
Browser Limitations for Prime Network Web Components
In Firefox 24, users might not be able to connect to the Prime Network 4.3.2 web server to use features such as VCB, Network Discovery, and CCM, using Firefox 24 if the gateway IP address is a raw IPv6 address. This issue seen because of Firefox defect. To avoid this issue, log in to Prime Network 4.3.2 using a hostname instead of an IP address.
Automatic Restart After Gateway Reboot
Prime Network 4.3.2 will restart automatically whenever the gateway server is restarted. This behavior can be disabled (so that Prime Network 4.3.2 has to be manually started after a gateway restart). See the Cisco Prime Network 4.3.2 Administrator Guide for more information.
Auto-Discovery of Unsupported Modules
Auto-discovery of unsupported module types is done on a best effort basis and is based on standard information which is reported by the device as part of the ENTITY-MIB. Operators are advised to validate that the discovery was fully successful. If not, add support for the specific module type using the VCB.
When VNE is configured to use SNMPv2 or SNMPv3 for discovery, SNMPv1 must also be enabled with the device.
Prime Network 4.3.2 Bugs Using Bug Search Tool
Use the Bug Search tool (BST) to get the latest information about Cisco Prime Network bugs. BST allows partners and customers to search for software bugs based on product, release, and keyword, and it aggregates key data such as bug details, product, and version.
Bug Search allows you to:
Quickly scan bug content
Configure e-mail notifications for updates on selected bugs
Start or join community discussions about bugs
Save your search criteria so you can use it later
When you open the Bug Search page, check the interactive tour to familiarize yourself with these and other Bug Search features.
a. Enter Prime Network 4.3.2 in the Search For field and hit Return. (Leave the Product, Software Type, Release, and Show Bugs fields empty.)
b. When the search results are displayed, use the filter and sort tools to find the types of bugs you are looking for. You can search for bugs by severity, by status, how recently they were modified, according to the number of support cases associated with them, and so forth.
If you know the bug ID, simply enter it in the Search For field and hit Return.
Open Bugs in Prime Network 4.3.2
lists the open bug in Cisco Prime Network 4.3.2 release. Click the Bug ID to view the impact and workaround for the bug in the Bug Search Tool. Use this tool to track the status of the open bug.
Choose Series/Model and enter Cisco Prime Network.
Releases drop-down list
Choose Affecting or Fixed in these Releases and enter 4.3.2.
Choose Fixed from the Status drop-down list.
Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.3.2
The bugs listed in Table 3 were identified too late in the Prime Network 4.3.2 development cycle to be fixed for this release. The fixes for these bugs have been provided to customers running older versions of the product as needed and are scheduled for inclusion in the next release.
Table 3 Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.3.2
Link/Line down syslog alarms for BE sub-interface erroneously associated with line LAG DC.
Accessibility Features in Prime Network 4.3.2
The Prime Network 4.3.2 software does not provide accessibility features. 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 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.