Cisco Prime Network

Cisco Prime Network Release Notes, 4.0

  • Viewing Options

  • PDF (832.0 KB)
  • Feedback
Cisco Prime Network 4.0 Release Notes

Table Of Contents

Cisco Prime Network 4.0 Release Notes



New Features and Enhancements

Command Manager

Transaction Manager

Compliance Audit

Operations Reports

New Technology Support in Prime Network 4.0

Additional Device Configuration Scripts

High Availability

Prime Network Administration

Change and Configuration Management

Fault Management

VNE Customization Builder (VCB)

Prime Network Integration Layer

New Device Support Information

Important Notes

Prime Network 4.0 Bugs

Open Bugs

Installation/Upgrade Bugs

Bugs Related to Hardware or Software Version Issues

Command Script Bugs

Command Manager Bugs

Technology-Related Bugs

VCB Bugs

Change and Configuration Management (CCM) Bugs

Job Manager Bugs

Compliance Audit Bugs

Fault Management Bugs

Report Manager Bugs

Transaction Manager Bugs

Operations Reports Bugs

Prime Network Vision GUI Bugs


Suite-Related Bugs

Resolved Bugs

Closed Bugs

Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.0

Bugs Resolved in Earlier Releases but Closed in Prime Network 4.0

Using the Bug Search Tool

Related Documentation

Accessibility Features in Prime Network 4.0

Obtaining Documentation and Submitting a Service Request

Cisco Prime Network 4.0 Release Notes

Revised: October 3, 2013

This release notes document provides an overview of the new features and enhancements in Cisco Prime Network 4.0 and highlights important issues you need to know before using this release. It lists open, resolved, and closed bugs and how to access information on Prime Network 4.0 bugs in Bug Search.

Note You can access the most current Prime Network documentation, including these release notes, online at


This document contains the following sections:


New Features and Enhancements

Important Notes

Prime Network 4.0 Bugs

Related Documentation

Accessibility Features in Prime Network 4.0

Obtaining Documentation and Submitting a Service Request


Cisco Prime Network 4.0 provides service providers and other network operators with a comprehensive assurance and device management solution for IP next-generation networks (NGNs). 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.

The primary enhancements provided by Prime Network 4.0 are as follows:

Tighter integration with the Cisco Prime Carrier Management suite:

Prime Network 4.0 incorporates architectural enhancements that provide tighter integration with Prime Central and the other Prime Carrier Management component applications. These enhancements include registering multiple instances of Prime Network with Prime Central and alarm acknowledgement from Prime Central.

Expansion of device operation and administration and network assurance support for mobility, data center, and cable access network scenarios:

Support for CDMA and UMTS deployments in mobility network scenarios

Support for computing and networking virtualization in data center environments

First phase of support for CMTS downstream functionality and support for RF Gateway for cable access network segments

Evolution of the Prime Network core functionality, including:

Configuration and Change Management—expands the configuration audit and compliance functionality.

Command Builder evolution to Command Manager that provides a command repository that contains all of the device-level commands and command scripts on the Prime Network gateway and allows the execution of commands on multiple devices.

Extension of reporting functionality by introducing a new reporting tool.

New Features and Enhancements

The following topics describe the new features and enhancements introduced in Prime Network 4.0:

Command Manager

Transaction Manager

Compliance Audit

Operations Reports

New Technology Support in Prime Network 4.0

Additional Device Configuration Scripts

High Availability

Prime Network Administration

Change and Configuration Management

Fault Management

VNE Customization Builder (VCB)

Prime Network Integration Layer

New Device Support Information

Command Manager

Command Manager is a new component that allows you to create and manage customized commands and scripts that perform device configuration operations. Command Manager uses the Command Builder back-end, but it provides the following additional features:

View a command repository that contains all commands available on the Prime Network gateway Execute commands on multiple devices

Use input from files to provide parameter substitution

Create command packages

Command Manager commands can only be applied at the network element (IManagedElement) level

Command Manager is launched from the Change and Configuration Management GUI or by entering a URL. For more information, see the Cisco Prime Network 4.0 Customization Guide.

Transaction Manager

Transaction Manager provides a GUI framework you can use to schedule and run transactions (activation workflows) that are created using the XDE Eclipse SDK. For new installations of Prime Network, Transaction Manager replaces the Prime Network workflow and activation features that were provided in previous releases of Prime Network. If you have upgraded to Prime Network 4.0, the Workflow and Activation features are still available, but they will be deprecated in the future. We recommend that you use Transaction Manager.

Transaction Manager is launched from the Change and Configuration Management GUI or by entering a URL. For more information, see the Cisco Prime Network 4.0 Customization Guide. Information about installing the XDE Eclipse SDK is available in the Prime Network Technology Center on the Cisco Developer Network.

Compliance Audit

Compliance Audit is a new component that enables the creation of compliance policies to detect and highlight compliance violations in device configurations. This new component replaces the configuration audit functionality that was provided in previous releases. For more information, see the Cisco Prime Network 4.0 User Guide..

Operations Reports

Operations Reports is an optional add-on component to Prime Network 4.0 that provides extended reporting functionality. It provides a wide range of prepackaged reports that you can run for your various business needs. It also allows you to create your own reports or customize reports according to your own requirements. Operations Reports processes and stores a large amount of data relating to faults, device inventory, technologies (including data center and mobility), and so on. Operations Reports enables you to access this data and evaluate it by generating meaningful reports which can help you understand your deployments better and take better business-critical decisions.

The Operations Reports component is a Web component that is installed on top of Prime Network and accessed via a URL. For information on installing Operations reports, see the Cisco Prime Network 4.0 Installation Guide. For information on using Operations reports, see the Cisco Prime Network 4.0 Operations Reports User Guide.

New Technology Support in Prime Network 4.0

Prime Network 4.0 adds device-level inventory modeling and event generation for the technologies listed below. For information on which technologies are supported on which Cisco devices, see Cisco Prime Network 4.0 Supported Cisco VNEs.


Inventory modeling of Mobility Management Entity (MME) in LTE access networks.

Inventory modeling of Serving GPRS Support Node (SGSN) in GPRS networks.

Data Center

Topology view of UCS compute servers—Using Prime Network Vision, you can view the physical layout and topology among the multi-chassis devices on the map. The multi-chassis devices have more than one physical chassis, but they are represented as a single entity in Prime Network. In a map, this device is shown as an aggregation of all the device chassis. For a UCS device, you can view its chassis along with the other elements relevant to the UCS device, such as Blade Server and IO Modules.

Modeling of VMware vCenter virtualization which provides centralized management of virtualized hosts and virtual machines from a single console. vCenter is modeled as a single VNE.

Significantly improved data center discovery performance—The discovery timeline of 1 VM vMotion for a vCenter VNE with load of 3000 VMs has been reduced from 11 minutes 23 seconds in Prime Network 3.10 to 30 seconds in Prime Network 4.0.

Modeling of Fibre Channel (FC) and Fiber Channel over Ethernet (FCoE) technologies and topology on Nexus 5000, Nexus 7000, UCS, and MDS devices.

Additional Virtual Network Device Support

Cisco Cloud Service Router (CSR) 1000v

Cisco Virtual Security Gateway (VSG)

Additional Compute Server Support

UCS B-Series Servers

UCS C-Series Servers

Non-Cisco servers including non-UCS servers such as HP, Dell or IBM


Modeling of the following cable configurations for the RF Gateway-10 and uBR10012 devices:

DOCSIS Timing Interface client (DTI Client)

Quadrature Amplitude Modulation domain (QAM Domain)

MAC Domain

Narrowband Channels

Wide Band Channels

Fiber Node

Additional Device Configuration Scripts

The following additional configuration scripts are packaged with Prime Network 4.0:

Configuration scripts to support Cable technologies on UBR10K and RFGW10 devices, including:

Configuring Cable Ports and Interfaces

Viewing Upstream and Downstream Configurations for Cable

Viewing QAM Configurations that includes configuring RF and Frequency Profiles

Configuring Downstream External PHY Interface (DEPI) and Layer 2 Tunnel Protocol (L2TP)

Configuration scripts to configure the Systems Architecture Evolution (SAE) - GW on ASR 5000 devices.

High Availability

Prime Network 4.0 introduces the Hot Backup feature for high availability. When restoring the redundancy configuration on a failed site, the active site does not need to be taken down. Both sites are up while the failed site resumes, and you can switch back to the active site without any down time. For more details, see the Cisco Prime Network 4.0 Gateway High Availability Guide.

Prime Network Administration

The following new features and enhancements are described in the Cisco Prime Network 4.0 Administrator Guide.

New Registry Controller for Changing System-Wide Defaults for VNEs, User Accounts, Link Displays, and Oracle Database Encryption

The Registry Controller GUI provides an easy way to change the system-wide defaults for the most frequently changed settings. This includes:

User Accounts—Whether users can view maps created by other users; and the user access role required to log into the Events GUI client (the default is Administrator).

Links Display— Whether a link should be displayed on a map only when both link endpoints are in the user's device scope.

Database —Settings that control the archiving of tickets in the Oracle database based on the total number of tickets; settings that control the archiving of tickets in the Oracle database based on the size of individual tickets; and whether raw events are saved to the Event Archive.

System Security—How to encrypt external Oracle database connections and which algorithms can be used for encryption.


Reduced Polling—Whether all VNEs should use reduced polling or not; and if they do, whether Prime Network should generate an event if a VNE does not support reduced polling.

Adaptive Polling— Settings that control the Telnet delimiter delay and terminal length used by the adaptive polling mechanism when a VNE is using slow polling.

Communication Policies— Settings that determine when a device is unreachable.

Device Protocol Reachability— Settings that determine when individual device protocols (HTTP, ICMP, SNMP, Telnet, and XML) are unreachable.

Smart Polling—Settings that control the interval that prevents over polling when repeated queries are sent to a device.

Staggering Mechanism—Settings that control the rate at which VNEs initiate Telnet/SSH connections (to prevent degraded performance on TACACS servers).

The Registry Controller is launched by choosing Tools > Registry Controller from the Administration GUI client main menu.

VNE Adaptive Polling Groups

You can now create customized adaptive polling groups that control how VNEs respond to high CPU events. This groups mechanism allows you to apply settings to multiple VNEs, rather than having to specify settings per VNEs. Once an adaptive polling group is created, it is made available to all VNEs in the new Adaptive Polling tab in the VNE properties.

User Authorization

Some user authorization controls have been extended to apply to additional Prime Network features. The controls include:

Requiring users to enter device access credentials when they execute device configuration operations.

Support for the global per-user authorization which, if enabled, means users can only execute jobs if they have been granted this privilege in their user account.

These controls already apply to Command Builder, Activations, and Workflows. The controls have been extended to Command Manager, Transaction Manager, Configuration and Change Management (including Compliance Audit).

New AVMs for New Features

AVM 41—Change and Configuration Management Compliance Audit

AVM 44—Prime Network Operations Reports

Change and Configuration Management

The following new CCM features and enhancements are described in the Cisco Prime Network 4.0 User Guide.

Framework available to support non-Cisco devices.

NBI support for configuration backup, restore, and export.

NBI to retrieve CCM job details

Ability to edit archived configuration files, and restore them later. The edited configuration files can also be deployed to devices of the same series.

Ability to download an IOS image from as a .tar file and deploy in the image repository without changes. The .tar files available in the image repository can later be distributed to the devices.

Ability to compare device configurations without excluded lines.

Support for using a non-default SCP port during image distribution and configuration backup operations.

Ability to apply images immediately after distribution without waiting for polling.

Enhanced security measure that can be enabled to restrict access to devices. If enabled, users must provide device credentials before accessing or making any configuration changes to devices.

Ability to perform configuration restore in overwrite mode on ASR 901, ASR 903, and MWR 2941 devices.

Ability to change the port being used by Change and Configuration Management by changing it in the VNE properties (from the Telnet/SSH tab).

Fault Management

The following new fault management features and enhancements are described in the Cisco Prime Network 4.0 Administrator Guide.

A lock for tickets that, if specified, determines when a cleared ticket can no longer be reopened and no new events can be added to it. It is disabled by default and is controlled from the Administration GUI client (under Global Settings > Event Management Settings).

A new Cisco Configuration Management Trap Filter that filters out ciscoConfigManEvent traps using a Noise Filter. These traps are ignored and are not saved to the Event Archive.

VNE alarm persistency information is associated to the VNE's ID instead of its IP address. This means that if the device IP address is changed or the VNE is moved, the persistency information is still associated to the correct VNE.

The new Registry Controller provides an easy way to change the following fault-related settings:

Settings that control the archiving of tickets in the Oracle database based on the total number of tickets.

Settings that control the archiving of tickets in the Oracle database based on the size of individual tickets.

Whether raw events are saved to the Event Archive.

The Registry Controller is launched by choosing Tools > Registry Controller from the Administration GUI client main menu.

The following new fault management features and enhancements are described in the Cisco Prime Network 4.0 User Guide.

Ability to manually deacknowledge an acknowledged ticket.

Ticket and events tables and properties now display the "Element Type" which is the type of device that triggered the event or the root event (in the case of a ticket). Tables can be filtered by the Element Type parameter.

The following ticket actions are now disabled when Prime Network is operating in suite mode: Acknowledge, Deacknowledge, Clear, Remove, and Add Note.

VNE Customization Builder (VCB)

The following new VCB features and enhancements are described in the Cisco Prime Network 4.0 Customization Guide.

The VCB GUI now enables import of VCB customizations. Prior to this release, import could be done using CLI only.

Support for identifying new or existing events as a flapping events (events that rapidly change state and are identified based on the number of times and the frequency with which the change of state occurs).

Ability to create an expedite rule for events that will cause the device to be polled immediately for inventory updates upon receipt of the event, instead of waiting for the next polling cycle.

Ability to simulate new or customized events from the VCB GUI in order to check that the customization has been successful.

Prime Network Integration Layer

Prime Network 4.0 introduces the following new integration layer features and enhancements:

3GPP Features

Real time inventory notifications that will enable OSS applications to receive notifications whenever inventory files are ready in 3GPP format for ASR 5000, ASR5500 devices.

Options for operators to list available 3GPP inventory files in the system.

Enhanced logical inventory support for AAA, ACS, GTPP, and Operator Policy.

Seamless integration of 3GPP operations and notifications in standalone and suite mode and also across multiple Prime Network instances.

Web Service scheduling functionality for generating 3GPP inventory files at regular intervals. For details on how to use the Web service scheduler in Prime Network, see the Cisco Prime Network 4.0 User Guide.

3GPP File Transfer IRP Release 10 compliance.

Alarm Lifecycle Functionality

Ability to perform acknowledge, deacknowledge, clear, retire, and add note operations on alarms using northbound web services.

Retrieval of a list of subtending events for an alarm using northbound web services.

Data Center and Service Inventory

Physical inventory for devices, including UCS, Nexus, MDS, CAT, and so on.

Logical inventory for VM, Host, Host Cluster, Data Center, Data Store, and vCenter.

Data center notifications whenever there is a change in data center related information.

Delta inventory functionality to avoid the need for full inventory synchronization all the time.

Floating termination points.

Service inventory details for L3 VPN.

Credential Management (suite mode only)

Retrieval of various credential details for SNMP, Telnet, SSH, HTTP, and HTTPS.

Distributed Architecture and Multi-Instance Support

Enhanced installation mechanism to support multiple Prime Network Integration Layer instances in suite mode.

Enhanced monitoring mechanism to continuously check the health of the Prime Network Integration Layer.

Ability to set up Prime Network Integration Layer 1.1 in a local high availability environment. For details, see the Cisco Prime Network 4.0 Gateway High Availability Guide.

New Patch and Upgrade Framework

New framework for applying Integration Layer specific patches.

New upgrade framework to perform integration layer upgrade from Prime Network Integration Layer 1.0 (corresponding to the Prime Network 3.10 release) to Prime Network Integration Layer 1.1 (corresponding to the Prime Network 4.0 release). For details on the upgrade procedure, see the Cisco Prime Network 4.0 Installation Guide.

For details on the various operations supported in this release, please refer to the Cisco Prime OSS Integration Guide for MTOSI and 3GPP.

For information about setting up the integration layer in Prime Network, see the Cisco Prime Network 4.0 Installation Guide.

New Device Support Information

Prime Network 4.0 introduces new device support and also incorporates all the device support additions that were provided in the March 2013 Device Package (Prime Network 3.10 DP1303). For more information, see the Cisco Prime Network 4.0 Supported Cisco VNEs. Additional device support will be available in the next DP. This will be available for download on the Prime Network download site on and will be documented in the Cisco Prime Network 4.0 Supported Cisco VNEs—Addendum.

For user convenience, the addendum will be appended to the PDF version of the Supported Cisco VNEs document so that there is a single source of up to date device support information.

Important Notes

This section provides important information of which you should be aware before using Prime Network 4.0.

Installation and Upgrade

Solaris Support Discontinued—From this release onwards, Prime Network installation is only supported in a Linux environment and is no longer supported in a Solaris environment.

Operations Reports does not support IPv6. The gateway, database server (Oracle and Infobright), and the units should be installed with IPv4.

Configuration Audit, Activation, and Workflow Features Available upon Upgrade Only

The configuration audit feature in Change and Configuration Management is being replaced with Compliance Audit, a new component introduced in this release. In Prime Network 4.0, the legacy configuration audit feature is available only when upgrading to Prime Network 4.0 from an earlier version that included this functionality.

Activation and workflow features are being replaced with Transaction Manager, a new component introduced in this release. In Prime Network 4.0, the legacy activation and workflow features are available only when upgrading to Prime Network 4.0 from an earlier version.

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

Firefox—Users might not be able to connect to the Prime Networkk Web server to use features such as VCB, Network Discovery, and CCM using Firefox if the gateway IP address is a raw IPv6 address. This is due to a Firefox defect. To avoid this issue, log into Prime Network using a hostname instead of an IP address.

Internet Explorer 8—The Network Discovery Profile page might take longer than usual to load due to this browser's slower JavaScript engine.

Potential Image Management Issues on ASR 9000 Devices Running IOS XR 4.3.0

Under some circumstances the device driver (VNE) representing an ASR 9000 device running IOS-XR 4.3.0 can enter and remain in a state that affects Prime Network's ability to display installed IOS-XR packages and distribute IOS-XR images to the device. While Prime Network can continue to monitor the device and update the physical and logical inventory, the condition affecting the image management functionality will persist. This issue has been observed on occasion with densely populated ASR 9000 devices running IOS-XR 4.3.0, and Cisco is working on resolving it. If you encounter this issue, try restarting the VNE.

Changing Command Builder and Workflow Privileges when in Suite Mode

Command Builder and Workflow access privileges can be controlled from the Prime Network Administration GUI client, even when using Prime Network in suite mode.

Automatic Restart After Gateway Reboot

Prime Network 4.0 will restart automatically whenever the gateway server is restarted. This behavior can be disabled (so that Prime Network has to be manually started after a gateway restart). See the Cisco Prime Network 4.0 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.

StarOS 14.0 - Disabled MIBs

Starting from StarOS 14.0, the following MIBs are disabled by default in the device.





The physical inventory will not be modeled if these MIBs are disabled. Enable the MIBs using the following:

snmp mib ENTITY-MIB
snmp mib IF-MIB

To verify if the above MIBs are enabled, use:

show snmp server

Prime Network 4.0 Bugs

This section contains the following information:

Open Bugs

Resolved Bugs

Closed Bugs

Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.0

Bugs Resolved in Earlier Releases but Closed in Prime Network 4.0

Using the Bug Search Tool

Open Bugs

The following sections identify bugs that are open in Prime Network 4.0, according to the following criteria:

All catastrophic and severe bugs (if any).

Customer-found bugs.

Moderate, minor, and enhancement bugs that are considered likely to affect the customer's experience with Prime Network.

Bugs that were fixed in previous releases of Prime Network but are still open in the current release because they were identified too late in the Prime Network 4.0 development cycle.

The open bugs have been grouped in the following categories:

Installation/Upgrade Bugs

Bugs Related to Hardware or Software Version Issues

Command Script Bugs

Command Manager Bugs

Technology-Related Bugs

VCB Bugs

Change and Configuration Management (CCM) Bugs

Job Manager Bugs

Compliance Audit Bugs

Fault Management Bugs

Report Manager Bugs

Transaction Manager Bugs

Operations Reports Bugs

Prime Network Vision GUI Bugs


Suite-Related Bugs

Installation/Upgrade Bugs

Table 1 Installation/Upgrade Bugs 

Bug ID


Retained CCM jobs cannot be run after upgrade to 4.0 or 4.0 SP1.


After upgrading from Prime Network 3.x to 4.0, the Compliance engine does not start up.


Prime Network webstart clients fail to start.


After upgrade, a report that was created in the previous version is not found.


Device added with Generic VNE scheme prior to upgrade of Prime Network 3.10 or Prime Network 3.11, is modeled with Product scheme post upgrade.


A report created prior to upgrade to Prime Network 3.10 or Prime Network 3.11 does not work post upgrade.


In VCB, user-defined VNE is switched to system default after upgrade.


When trying to install a Geographical Redundancy only scenario the following error is received:
"SSHProcessError The ssh process was terminated. at line 859
*** ERROR: Failed to setup the replication. ABORTING. ***"


Cannot decouple Prime Network from Prime Central.


Link filter in map in Vision - mismatch in group and contents after upgrade to 4.0.


Upgrade fails and Java VM crashes.

CSCuh44996 script does not provide information as to why the IVNE install fails when downloading the DP in ASCII mode.


Upgrade fails if sqlplus passwd contains '&'.

Bugs Related to Hardware or Software Version Issues

These are hardware or software version specific issues that are causing bugs in Prime Network.

Table 2 Bugs Related to Hardware or Software Version Issues 

Bug ID


VEM module status shown as Unknown for Nexus1000V.


ASR 5000 and ASR5500: When Virtual APN is deleted, it is still shown under main APN where it was referenced earlier.


Wrong PID shown for transceiver/SFP modules for Nexus 7000 device.


Module is not discovered properly for a Nexus 7000 device because the OID returned by the device is incorrect.


CDP does not display channelized remote Serial ports for 7206VXR in Cisco Prime Network.


E1/T1 Controllers of ASR 901 device does not list the T1 Controllers in Physical Inventory.


ASR 901 CPU spikes.


ASR 903 Physical Inventory does not list T1 controllers.


Syslogs do not appear in Cisco Prime Network from a device with an IPv6 management address.


ASR 903 Satellite configured Ports do not display Admin/Oper Status and Ethernet Interface attributes.


Logical interfaces like Null0,Loopback0 are modeling as physical interfaces and are shown in the physical inventory for CGR2010 devices.


Ports under the module GRWIC-2CE1T1-PRI / GRWIC-1CE1T1-PRI are not shown in the physical inventory.


Ports under the module GRWIC-D-6S are not modeled in the physical inventory for CGR2010 devices.


Ports under the module GRWIC-D-ES-2S-8PC are not modeled in the physical inventory for CGR2010 devices.


For CGS-2520-24TC Chassis, Cisco Prime Network displays wrong entity Physical Name.


'mplsL3VpnDown Trap' is not cleared when SIP is powered up.


Fan is not modeled in Physical Inventory for CISCO ISR 3945 devices.


LLDP neighbor table is not modeled for Whales device.


Cisco Prime Network displays extra Gigabit ports for 24 port Whales (ME3600x/ME3800x) device.


Connector type for pluggable ports is displayed as UNKNOWN in Vision for Nexus 7k Device.


When an interface is removed the syslog is not correlated with the ticket ID and syslog generation is not done properly for a Nexus 5550 device.


Module and Port status change is not reflected for UCS.


Inconsistency in data between UCS Manager CLI/GUI and Nexus OS CLI.UCS Bridges on VSN in parser.


Port status is showing up after server/adaptor module is out in UCS.

Command Script Bugs

Table 3 Command Script Bugs 

Bug ID


MPLS Label range incorrect in CPT when trying to add via LSE command.


ASR 901: MPLS label range in activation script is different from the range supported on the device.


ASR 903: MPLS label range in activation script is different from the range supported on the device.


Updating global configuration for mpls tp contains incorrect range.


Changing SONET port status using a script throws an error on ASR 9000/903 devices.


When executing the Create ISIS Router command, the specified EIGRP AS Number is not used for execution.


When executing the Update Interface Configuration script, a Beanshell error is received and the VOID is used.


Execution of MPLS_TP Add Configuration Link command fails.


The CPU of CRS device spikes when added to Cisco Prime Network.


A redundancy switchover in CRS creates a card out alarm in Cisco Prime Network.


When the power supply is pulled out of the CRS device, the relevant ticket takes a long time to appear in Cisco Prime Network.

Command Manager Bugs

Table 4 Command Manager Bugs 

Bug ID


Edit command: devices specified for the source command are not selected in the GUI when editing the command.


Missing values when editing a command for a second time.


Commands created in Vision are not reflected in the command repository after restarting AVM11.


When using Vision to edit a command that was created in Command Manager, a new implementation is created instead of updating the existing implementation.


Crtl + Space adds parameter display name instead of variable name.


Import command fails with message "implementation already exists" although the command has been deleted.


Command import does not work when using IE 9.0.


"None" is not displayed as an option in the new/edit parameter screen when creating a command, therefore it cannot be selected as the default value.

Technology-Related Bugs

Table 5 Technology-Related Bugs 

Bug ID


Wrong association of syslog alarms for TP-tunnel interfaces on ASR 9000 devices.


P2MP MPLS-TE tunnel configuration changes are not updated on mid/tail nodes on VNEs using reduced polling.


When adding an MPLS-TP service to the map, endpoints or middle points may not be discovered properly.


Satellite IC port status participating in ICLs does not have status populated on initial investigation of VNE. Satellite ICL Link is not seen in the map.


When shutting down a multilink interface, the MLPPP link disappears instead of becoming red.


LAG link is not rediscovered after clearing and removing the ticket.


MPLS topology test is based on ip instead of LDP neighbors.


High rate of Oracle DBF file creation during VPLS service discovery.


Upgrading ME-3400E image fails.


Duplicate BFD connectivity down service alarms on LAG interfaces.


Deleting/stopping a large scale VCenter VNE takes a long time.


Fiber channel link is not removed/down when the vfc interface is unbound from the Ethernet port.


On a Cisco CRS S/W 4.3.0 modeled with "Reduced Polling", deleting IPv4 from an interface is not reflected in the inventory until the "POLL NOW" button is clicked on the card level.


When a member of an MLPPP link is brought back up after being shut down, the number of active links in the MLPPP bundle is not restored.


When LDP is configured on VLAN, VRF, or LAG sub-interface, Prime Network fails to correlate the LDP neighbor down to the root cause event.


If Chassis is removed and connected again, Blade Server details are incomplete.


Card down ticket on a Nexus 7018 device is not cleared even after the card is re-inserted.


Prime Network incorrectly creates topological links between multi-chassis devices.


Local router ID for tunnel edge entries in static pseudowire logical inventory is populated as instead of l2vpn router id.


When LACP channel is split between cards and one of the cards is removed, the channel stays in up state and a low priority member down ticket is created. When the card is inserted the card out ticket is cleared as expected, but the low priority member down ticket is not cleared.


Unable to correlate all MPLS TE FRR state changes to root cause.


ASR 9000 VNE logs PatternSyntaxException when VFR name includes '*' characters, which are special characters for RegExp.


ASR 903 VNE fails to parse %LINEPROTO-5-UPDOWN syslog message.


OIR cards with DWDM do not map DWDM interface traps to the interface. The events generated are not correlated correctly and the events are not associated with the interface.


"MPLS TE FRR State Changed to Active/Ready" service alarm is not correlated properly. Sometimes it is created as standalone ticket, and sometimes it is correlated to root cause such as "Port up" or "Port down due to ..." ticket.


Network event does not show up for CPT RP switchover syslog.


Inventory is not updated correctly with all VMs after migration in the case of large scale VCenter. For example, when 200 vMotion is performed on a VCenter with 7000 VMs, some of the VMs are missing in the inventory.


VNE state is device unsynchronized after CTP reboot or power-recycle.


Pseudowires are not discovered.


Server down event is not correlated to Host down event.


Number of vMotion events generated is less than the number of vMotions performed on the vCenter.


After the VM key is changed, e.g., due to rename or migration, all the old VM-related alarms continue to point to the old VM location. Any new alarm, including the renaming and migration alarm, will point to the correct VM location.


SAN port channel and Fiber channel port down events are generated when the VNE models for first time.


Config syslog changes take a long time to update in the GUI for MPBGP in Nexus 7000 and Nexus 5000 devices.


Poll now does not work for LAG technology in Nexus 5000 devices.


Routing entries are not populated under the VRF table for Nexus 5000 devices.


Cross launch from Generic server port to PPM fails. This happens because Prime Network uses ifName from IF-MIB and normalizes the port name for better UI presenattion.


Repetition of Ethernet OAM Session syslog in Event Notification (ENS).

VCB Bugs

Table 6 VCB Bugs 

Bug ID


When adding support for third-party line cards that support multiple port types, port layers are not displayed correctly.


When committing a new syslog or trap through VCB, after pressing the Finish button, the application reports an error "Failed to save data: Timeout waiting for result".


Module groups of only a few third-party vendors are displayed in the 'Modules' tab or module group information is empty for a few third-party vendors when viewing VNE driver details in the 'Drivers' tab.


VCB Events GUI does not show all the supported Logical Containers.

Change and Configuration Management (CCM) Bugs

Table 7 CCM Bugs 

Bug ID


After restoring archived config to startup-config on an ASR 903 device, the latest startup-config is not retrieved although the configuration is different.


In Edited Archive Restore Flow, when selecting the running configuration, selecting the restore to startup config option and scheduling the job, the job fails.


After creating a device group, some device members are not displayed in the group.

Job Manager Bugs

Table 8 Job Manager Bugs 

Bug ID


In some cases, for recurring jobs (Daily, Weekly, Monthly), the Job Manager does not show the correct "Next Run Time" and the job is not executed at the expected time.


Failed to reschedule job.

Compliance Audit Bugs

Table 9 Compliance Audit Bugs 

Bug ID


Newly created compliance policy disappears from the display.

CSCuh55242 and CSCui04697

Compliance Audit Module Screen shows message dialog stating "Compliance Engine is Down".

Fault Management Bugs

Table 10 Fault Management Bugs 

Bug ID


The location column/field in the Tickets/Events for ASR5k/5500 traps points to the Managed Element instead of to their corresponding service modeled in the logical inventory.


Newly added event types are not forwarded through the Event Notification Service if specific event types were selected when defining the service.


A system event stating "Number of orphan events reached major limit" is generated.


Element type filtering is not working in Prime Network Events.


Some tickets might not be cleared after upgrade.


For a specific ticket or event, the element type column in the Prime Network GUI is blank or showing as "Unknown".


Prime Network Events displays errors indicating dropped messages.

Report Manager Bugs

This table shows open bugs in the Report Manager (the legacy reporting tool accessed from Prime Network Vision, Events, and Administration clients).

Table 11 Report Manager Bugs 

Bug ID


Errors received in Fault DB vs. Event Archive report output.

Transaction Manager Bugs

Table 12 Transaction Manager Bugs 

Bug ID


Transaction job does not have a tasks list in the Job results screen.

Operations Reports Bugs

This table shows open bugs in the new Prime Network Operations Reports component.

Table 13 Operations Reports Bugs 

Bug ID


Date format of Device Up time as well as the value of time for a VNE is different in the report from what is shown in the inventory.


Prime Performance Manager (PPM) events are not displayed in Operations Reports.


Pie chart distribution is not equal to 100% in report.


Bottom scroll bar in interactive reports is not fully visible.


Drop down list does not disappear when performing a subsequent action.


Tooltip is not clearly visible in Operations Reports GUI.


Saved PDF report cannot be opened by Acrobat Reader.


In the Active Events interactive report, the text does not wrap and field values overlap into the next field.


For pre-packaged interactive report scheduling email option not provided.


Scheduled interactive report names in Workspace not recognizable.


"Schedule" option is not enabled for pre-packaged reports.


Admin users can delete prepackaged reports and data sources but there is no way to retrieve them.


Scheduled Interactive reports are all shown in the same page.


No option to select an output type (HTML, PDF, etc.) when scheduling an interactive report.


When editing and then saving a prepackaged interactive report, the name of the report is changed.


Reports folders are not visible when Operations Reports is launched for the first time.


When opening a scheduled HTML report from an email, only tabular data is shown. Charts and graphs are not displayed.


Device selector in Operations Reports is not automatically updated when VNEs are added/deleted.


Unassociated FA service is not deleted from the report.


Tickets generated by network events are not shown in the reports.


Report scheduled with recurrence value of "run once" disappears from the Workspace after it has been executed.


Only the Prime Network user (pnuser) should be allowed to start/stop Operations Reports processes but the root user can also do this by running the reports server start/stop server script (./ under export/home/<pnuser>/pentaho/server/biserver/tomcat/scripts).


Data source was deleted and cannot be retrieved.

The following table shows Operations Reports bugs that have been closed because they cannot be resolved at this time.

Table 14 Closed Operations Reports Bugs 

Bug ID


In Operations Reports, a report does not display unless all permissions are given at the folder level.


In Operations Reports, in a hardware inventory report for a device with ports under modules and sub-modules, the ports under the sub-modules do not show up.


In Operations Reports, if a non-Admin user does not have "execute" permissions for the folder and the report, the interactive report cannot be viewed.

Prime Network Vision GUI Bugs

Table 15 Prime Network Vision GUI Bugs 

Bug ID


Drop down menus appear to the left of and far from the drop down button (instead of just below the button).


Prime Network Vision client memory consumption reaches 100% and the client crashes.


An error "Windows cannot find 'telnet'. Make sure you typed the name correctly, and then try again" is displayed when trying to telnet from Prime Network Vision to a device using the Tools->Telnet menu option.


Table 16 VNE/AVM Bugs 

Bug ID


For ISR 1800 device, VNE restarts due to software version change.


High load average may be caused because of southbound IP search.


Physical inventory of Nexus 3000 devices is not modeled.


VEM module status shown as Unknown for Nexus 1000V.


Device configuration validation pass event is not received after adding an unreachable VNE to the server.


RFGateway 10 device does not model when Third Party Device Package is installed in the system.


Units do not start after reboot.


AVM error log fills up with errors similar to this:
ERROR [06 28 2013 16:24:13.555 CDT] - L1MH.onValidateTests - [Ljava.lang.Object;@78be2d
The log rolls over every few minutes.


When trying to open the inventory of a VNE from the Administration GUI, out of memory occurs.


VNEs remain in initializing state during system startup.


When loading 30K VNEs at once for the first time, the system hangs.


VNE is stuck in discovering mode.


Nexus device takes time to become operational and the device CPU is increased in a scale setup.


VNE fails to recognize the %CONTROLLER-5-UPDOWN syslog issued for T1 controller on the serial interface and therefore fails to generate the Port down service alarm.

Suite-Related Bugs

Table 17 Suite-Related Bugs 

Bug ID


Although vCenter is not modeled in Prime Central, vCenter details may temporarily appear in the Prime Central GUI.


The Prime Central GUI may not reflect real time power off/disconnected status for blade servers. This behavior may be temporary until an inventory sync is performed from Prime Central.


The Prime Central GUI may not reflect real time card in/out status. This behavior may be temporary until an inventory sync is performed from Prime Central.


Device port line rate might not reflect properly in the Prime Central GUI.


The Prime Central GUI may temporarily show Logical DC entities (VM, Host, Host Cluster, etc.) after a vCenter is deleted from Prime Network.


When a data store is deleted on a vCenter, the data store and all its association to Hosts will be removed from vCenter inventory.


UCS device synchronization takes longer than expected in a scale setup.

Resolved Bugs

Table 18 identifies bugs that were listed as open bugs in the Prime Network 3.10 release notes and have since been resolved.

Table 18 Resolved Bugs in Cisco Prime Network 4.0 

Bug ID


After upgrade, the polling method is different, e.g., changed from Regular Polling to Use Reduced Polling if Possible.


Prime Network does not discover all the P2MP TE tunnel LSP links.


After upgrade, SNMP v3 VNE is shown as SNMP v2 in Vision.


Unable to create or edit Message of the Day after upgrade.


New unit added after upgrade is in unreachable state.


Backing up Prime Network during upgrade fails with the following error: ./local/scripts/embedded_oracle/gen_database_files_to_remove.sql: Cannot open: Permission denied.


Upgrade failed while running ?SeverityAspectInsertionException," saying that the object does not exist.


Upgrade failed as the table ?NETWORKEVENT_TA_HASH? does not exist.


On UCS device, hosts that are part of one data center are shown under a different data center.


Prime Network does not capture events for existing hosts after a new host (UCS) is added to VCenter.


Link Properties for P2MP LSP tunnel show the tunnel status instead of LSP status.


P2MP TE tunnel links discovered in Prime Network are not removed when the relevant LSP is deleted.


DS0 bundle admin down ticket is not cleared when a channelized interface is brought up again after being down.


Individual tickets are received for the same root cause, instead of showing as a single ticket with correlation.


AlarmStatusChangedEvent wrongly correlated to VM Power off and Power on Event in UCS Virtualization.


MPLS-TE tunnel down event is not correlated to the relevant BFD connectivity down event.


No alarm on a static link when its end is down.


ASR 9000: One of the remote peers' state shows up in the device inventory as blank when the neighbor's BGP state is 'Closing.'


After a satellite chassis is disconnected and then reconnected, the ticket is not cleared and the satellite chassis is shown as OUT in Physical Inventory.


When using the Integration Layer, inventory data related to APN DHCP always appears as empty although it might be actually configured in the device.


Power and Fan Rack, Modules are displayed without PID in the Prime Network Vision.


The CLI command to generate delete commands - vcb sitechanges delete - does not create the script file. This command is used to remove all customizations, usually in an upgrade scenario (Export VCB Customizations -> Delete VCB Customizations -> Upgrade -> Import VCB Customizations).


When adding traps from MIB, clicking the Analyze button in the upload dependencies step returns the same list that shows that the dependencies are not uploaded, and the process is stopped.


CCM sync page shows the "old" out of sync entry of the VNEs on IE8.


Job Schedule setting page does not show all years in the pulldown list of 'Start on date'; it only shows a few years (1912-1918).


CCM does not launch when right-clicking on a device in the map in Prime Network Vision GUI and clicking on Config Management or Image Management menu item.


In Change and Configuration Management, Scheduled Backups use local PC date/time, not server time.


Users with Operator profile can schedule boot IOS changes.


In CCM, no data is available in the Boot config page during activation by device.


In Change and Configuration Management, in IOS-XR by Device flow, when selecting mini package, a notification is received to select corresponding mgbl and upgrade packages to activate, even though those packages are not available in the device.


CCM formats flash on ASR901 without being requested to do so.


CCM import of image from ASR903-1 with DUAL RSP ISSU fails.


During card out/in test some of the OSPF related service and syslog alarms were not cleared.


When performing OIR of a line card on ASR903 device, some of the correlated service alarms (MPLS interface removed, Interface status down) were not cleared. Therefore, the root cause ticket Card In remains not cleared.


In the Prime Network Administration GUI client, it is not possible to edit an existing Event Notification service that was created manually and that had registered for ticket severity updates.


No EPM ticket notifications are forwarded to north bound interface.


The "High Memory" consumption alert is raised although there is no real issue in the AVM.


CPU goes up to 100% for a limited amount of time, then drops back to normal level.


The physical inventory of the device is not modeled.


When trying to create VNEs from devices discovered using Network Discovery, the VNEs are not created and the discovery result shows the devices in "Deleted" state after refresh. In this case, the devices are discovered with SNMP V3 with authentication but no encryption password.


When using Network Discovery with Internet Explorer 8 or older, the discovered devices table does not appear.


No SNMP responses to Sonet MIB query on ASR 9000 devices running XR4.3.


Inconsistent or incorrect MAC Address modeling for Nexus VNE.


Unexpected physical inventory changes.


Show access ruledef script on an ASR 5000 device generates an unknown command "access-reledef."


Create ISIS script cannot be executed if the fast re-route attribute is IPV4 Multicast and IPV6 Unicast/Multicast.


Beanshell error is received for "ASR9K Create PTP Clock Global" script when a value is entered for "Sync Timeout."


Beanshell error received for ASR9000 Create/Modify APS script.


ePDG activation scripts are not supported on ASR 5000 12.2 image.


Selected policies are not deleted when modifying the PDSN Policy.


MPLS TE Tunnel LSP does not display Outgoing Interface and Label.


'Poll Now' does not work for MPLS Traffic Engineering Tunnels container.


The TE tunnel type for P2MP TE tunnels does not show up in the inventory and its discovery takes a long time.


LSP role is not updated after lockout when using reduced polling.


IP Pool hyperlink does not disappear after deletion of destination context.


LAG link is not modeled between Nexus 7000 and Nexus 5000 devices.


No LAG links are displayed between Nexus devices.


MAG service does not display the default IPV6 address in the inventory.


Under Diameter Endpoints, Route health status displays invalid data for deleted or stale diameter peer.


Correlation flow failed going through encapsulation untagged on SI.


Only one PTP interface entry is populated in the PTP Service for MWR2900 devices.


Missing information under Clock in ME3600, ASR903, and 7600 device inventory.


IPv6 multicast VRF and neighbor PIM details are missing for ASR 9000, CRS, and GSR devices.


BFD interval is not shown on ASR 903 device.


On ASR 5000 devices, OC3 ports in the OLC card are modeled with Ethernet port properties instead of OC3 port properties.


Duplicate data is shown in the Service Policy Properties page.


Memory Usage graph is not updated for ASR 5000 and ASR 5500 devices.


When selecting files for image upgrade or config restore from flash or hd-raid, files with "config" or "crashinfo" in the file name are not displayed for selection.


When attempting to distribute an OS image to an ASR 5000 device, CCM displays a negative value for available flash size, although the device actually has enough space for the selected image.


Syslog message %SONET-4-ALARM is received indicating that connectivity to the remote SONET interface has been lost although no Port Down alarm was created.


Netsync input Signal Failure ticket is not correlated with relevant Link Down event for clock service event.


Events/tickets for traps received from ASR5000/5500 devices do not display device time.


When VNE receives a syslog of type '%MPLS_TP_LSP-3-UPDOWN' with explicitly specified LSP ID, it associates the event and alarm with the MPLS-TP endpoint instead of the LSP endpoint. As a result, the event is not correlated to the root cause alarms and appears in Vision as independent ticket. There is also no expedite on LSP status when notification is received, hence no LSP status update is reflected in the inventory and no service alarm is generated.


Many tickets are created for syslogs and traps in various scenarios relating to Nexus 7000 devices.


VNE stops processing syslogs and traps.


List size continually increases and AVM crashes.


Device CPU spikes.


AVM crashes with "Out Of Memory" error.


When an XR platform device is modeled, the corresponding AVM crashes due to a huge number of VRF route entries.


Multiple defects in VNE modeling with Prime Network 3.8.x + DP1207 or older.


Nexus primary card redundancy status is always shown as None.


Oper states of back plane and fabric ports do not update properly after disconnecting the connection from chassis to IOcard.


There are no interfaces in the model for ASR 1001 device.


ASR 903 remains in Discovering state.


ASR 901 VNE is not modeled in Product scheme.


With IOS-XR devices, peaks and falls are observed in the port utilization graph even though the traffic rate through the port is constant.


CFM Local MEP is not modeled on ME3400 devices.


Poll Now does not work on a Nexus device and many SSH connections are opened and closed on the device.


Configuration changes are not reflected on ASR 903 devices when using reduced polling.


ASR 903 VNE redundancy properties are not updated after RSP switchover.


Flooding of logs while loading Cisco 7600 device.


After upgrade, an ICMP VNE is not modeled.


After upgrade, a cloud VNE is not modeled.


Virtualization inventory does not update after changes.


After a new DP is added, some of the VNEs go into Currently Unsynchronized state indefinitely.


Hardware detail report does not show subslot, fan, and power modules information.


The AVM log is filled with INFO messages.


ASR 9000 VNE running IOS XR 4.3.0 remains in unsync state and certain image management functionality does not work properly.


The P2MP TE tunnel mid & tail LSPs are presented as Point-To-Point on IOS-XR devices.

Closed Bugs

Table 19 identifies bugs that have been closed since the previous release.

Table 19 Closed Bugs in Cisco Prime Network 4.0 

Bug ID


Static links created between VNEs prior to Prime Network 3.10 or Prime Network 3.11 upgrade do not work post upgrade.


CPU usage attribute is not populated in the GUI for SCE2000.


In Change and Configuration Management, when clicking Logout, a script error is received. If the Stop button is clicked, the page hangs.


MPLS TP LSP midpoint events are not associated correctly when MPLS TP LSP midpoints are added, deleted, or updated on an ASR903 device.


Duplicate alarm ID is displayed in Prime Network Events.


The Upstream and Downstream channels will not be modeled in the port on the UBR device.


For Upstream of the MC3GX60V and Down stream ports of the MC20X20V the status is UNKNOWN.


RF Switch Card status is always showing as OK.


Virtualization inventory is not modeled when a vCenter VNE with a large number of VMs is restarted.


Prime Network Vision GUI is not updated for VM operations like vMotion, VM addition, Power On/off, etc.


Host disconnected and VM disconnected events are cleared from Prime Network when performing the "Connect" operation under vCenter on a Host that is down.

Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.0

The bugs listed in Table 20 were identified too late in the Prime Network 4.0 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 20 Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.0 

Bug ID


AVM crashes with Out Of Memory error


checkPatchInstallation error message includes perl debug details

Bugs Resolved in Earlier Releases but Closed in Prime Network 4.0

The fix for the bug listed in Table 21 was provided to customers running older versions of the product but the bug has since been closed so the fix is not available in Prime Network 4.0.

Table 21 Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.0 

Bug ID


High CPU in the unit related to ATM counter topology discovery.

Using the Bug Search Tool

Bug Search is a new tool for getting information about Prime Network bugs. In addition to having better performance than the legacy Bug Toolkit, 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.

Step 1 Access the Bug Search tool from the Bug Toolkit page.

a. Go to

b. At the Log In screen, enter your registered username and password; then, click Log In. The Bug Toolkit page opens.

Note If you do not have a username and password, you can register for them at

Step 2 Open the Bug Search page by clicking the Bug Search link from the top of the Bug Toolkit page.

Step 3 To search for bugs in the current release:

a. Enter Prime Network 4.0 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.

Related Documentation

For a list of the guides available for Prime Network 4.0, see the Cisco Prime Network 4.0 Documentation Overview.

Additional information can be found in the Cisco Prime Network Technology Center, which is an online resource for Prime Network support content, including help for integration developers who use Prime Network application programming interfaces (APIs). It also provides a platform for you to interact with subject matter experts. To access the Prime Network Technology Center website, you must have a account with partner level access, or you must be a Prime Network licensee. You can access the Prime Network Technology Center at:

Accessibility Features in Prime Network 4.0

The Prime Network 4.0 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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at:

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.