This release notes document provides an overview of the new features and enhancements in Cisco Prime Network 4.1 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.1 bugs in Bug Search.
Cisco Prime Network 4.1 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.
Note IP NGN has been renamed as Evolved Programmable Networks (EPN). Please keep this in mind when viewing the suite and application documentation for the next Cisco Prime Carrier Management release.
The primary enhancements provided by Prime Network 4.1 are as follows:
Cisco Prime Network 4.1 provides service providers and other network operators with a comprehensive assurance and device management solution for evolved programmable networks (EPNs), 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 primary enhancements provided by Prime Network 4.1 are as follows:
Enhanced OSS integration through standards-based northbound interfaces (NBIs):
– Alarm management support over 3GPP NBI
– SGSN and MME Inventory support over 3GPP NBI
– GPON support over MTOSI NBI.
Expansion of device operation and administration and network assurance support for for new technologies:
– Support for CPT 9.7 ring topology
– Change and Configuration Management enhancements to support CPT and GPON devices
Evolution of the Prime Network core functionality, including:
– Enhanced Operations Reports to include traps and syslogs as generic events
– Alarm synchronization for ASR5500 and ASR 5550
– Easy GUI installation with InstallAnywhere for Prime Network and for its integration layer (separate installations)
Prime Network supports third-party devices through Cisco Advanced Services engagement. As of release 4.1, Prime Network native support is deprecated. 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.1:
System-defined compliance policy groups are provided with Prime Network 4.1.
Ability to include “show” commands in compliance policy definitions so that the compliance audit is performed against the output of the “show” command.
Ability to choose a command from the Command Manager repository as a fix for a compliance violation.
Additional useful information can be accessed from the Compliance Audit Violation Details page:
– Running configuration on the device
– Audited devices and their compliance status
– Details of compliance fix jobs
Events are now generated for compliance audit operations:
– Audit event is generated when a device is audited or fixed.
– System event is generated when the compliance engine is down.
– Provisioning event is generated when a fix or a command builder script is executed on a device.
Operations Reports is an optional add-on component to Prime Network 4.1 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.
New prepackaged report type—Network Service Reports. These reports can be generated to display information about virtual connections, VPLS, and network pseudowires in your network.
New prepackaged report, Daily Standard Event Count, for displaying information on standard events (minimal parsing, not processed for correlation). In addition, customized reports can be created using the new Standard Reports data source to define the information that will be included in the report.
New threshold-crossing syslogs reports that shows the count of syslogs over and above a defined maximum threshold. Until this threshold is reached, the events are not reported, and are counted as ignored events.
Hardware inventory data source extended to include sub-module port details.
New Technology Support in Prime Network 4.1
Prime Network 4.1 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.1 Supported Cisco VNEs.
Support for Remote Loop Free Alternate (LFA) which enables a quick reroute and recovery in case of network failure. Includes modelling and new service event support.
Ability to locate and view the L2 and L3 Ethernet Virtual Connections related to an Ethernet or LAG port.
Modeling of pseudowire headend (PW-HE) virtual interfaces that allow termination of access or aggregation pseudowires into an L2 or L3 domain.
Support for Carrier Packet Transport (CPT) 9.7, including:
– Modeling and topology view of CPT 50 single homed linear and closed rings and dual homed closed rings.
– CERENT alarms
Linear protection where a protected LSP takes over transmission of data when a working LSP fails. Prime Network 4.1 provides commands that enable you to switch normal traffic from a working LSP to a protected LSP and vice versa.
Support for Gigabit Passive Optical Network (GPON) physical, logical, and service modeling, including profiles, Class of Services (COS), Link Aggregation Groups (LAG), firmware configuration, services and bridges, DHCP relay agent, OLT and ONU physical inventory, and routing entities.
Small cell technology support with modeling of Home eNodeB gateway and Home Node B gateway.
Generic syslog support for ASR 5000 and ASR 5500 devices.
IuPS enhancement in SGSN technology and IuPS service support for ASR 5000 and ASR 5500 devices.
Support for SGSN in Infobright database with IuPS and RNC support for ASR 5000 and ASR5500 devices.
Fault resync support for ASR 5000 and ASR 5500 devices.
Data Center 1.0 Enhancements
Nexus VDC to port mapping—ability to view the VDC context and port allocation details for a Nexus 7000 device
VDC impact in event description.
Mapping of Virtual Ethernet Module (VEM) to server/hypervisor and of VEM to physical server, including topology visualization.
Quality of Service (QoS)
Full modeling of QoS class of service, service policies, policy groups, and policy mapping to network services on ASR 9000, ASR 901/903, CPT, and ME3600X devices.
Inventory and map view of ASA failover configuration.
Additional Device Configuration Scripts
The following additional configuration scripts are packaged with Prime Network 4.1:
Configuration scripts to support various technologies on ME 4600 OLT devices, including:
– Profiles—Ethernet, Upstream, ONT, VOIP
– Class of service—Ethernet, LAG, GPON\
– IP route and interfaces
– Services—DHCP, OLT, ONU
– ONU physical inventory—Ethernet port, analog RF port, VOIP, system interfaces
– SNMP management
Linear protection commands for ASR 903 devices:
– Global linear protection configuration
– Linear protection at MPLS-TP tunnel
– Manual switch at MPLS-TP tunnel
Remote LFA commands, including ISIS and OSPF routing protocol configuration commands. Supported on ASR 9000, ASR 901/903, ME 3600X, ME 3800X, Cisco 7600 devices.
Ability to disable ticket management operations in the Vision and Events clients. When these operations are disabled, users can only manage the ticket lifecycle through BQL or the external OSS.
Ability to change the minimum user role required to use the Administration client. The change can be made using the CLI runRegTool.sh command and requires a gateway restart.
Ability to control whether standard events are displayed in a map's Latest Events tab (in the Vision client). Standard events are syslogs and traps that are not recognized by the Prime Network Event Collector and only basic parsing is performed on them. The setting is in Global Settings>Event Management Settings> Standard Events (Display Standard Events in Latest Events Tab in Vision check box). If this setting is changed, active Vision clients must be restarted for the changes to take effect.
VNE restart is no longer required if its credentials are changed in the VNE properties dialog box. Prime Network will detect these changes and reconnect with the device to validate the new credentials.
Enhanced gateway memory calculations and display available in the gateway properties dialog.
The default allocated memory for user-created AVMs is now 1500MB instead of 256MB. In addition to the 1500 MB allocated memory, Prime Network configures user-created AVMs with an additional 400 MB for backend operating system tasks, for a total assigned memory of 1900 MB.
Users can customize an AVM's allocated memory by adjusting it in the AVM's property dialog box. If the allocated memory is changed, the AVM must be stopped and restarted for the changes to take effect.
Units—The titles for the following fields have changed:
– Total Potential Memory of Running AVMs (formerly "Total Memory Assigned Up AVMs")—If all running AVMs used all of their assigned memory, this is the amount of physical memory that would be required. This includes both user-created and reserved AVMs.
– Total Potential Memory of All AVMs (formerly "Total Memory Assigned All AVMs")—If all AVMs used all of their assigned memory, this is the amount of physical memory that would be required. This includes both user-created and reserved AVMs.
New AVM 45 for gateway high availability for the Operations Reports Infobright database. This AVM synchronizes information between the local and remote Infobright databases.
Ability to view all events received by Prime Network, including standard events (minimal parsing, not processed for correlation) and upgraded events (parsed, processed for correlation). These events are listed in the Vision and Events GUI clients.
In the case of temporary disconnection of an ASR 5000 device, Prime Network retrieves any traps that were missed when the device was disconnected. A ticket is created and all the retrieved traps are associated to this ticket.
Enhanced ticket filtering capabilities, including saving named filters and sharing saved filters with other users.
Ability to disable ticket management operations in the Vision and Events clients. When these operations are disabled, users can only manage the ticket lifecycle through BQL or the external OSS. This can be done using the Administration GUI client.
Automatic translation of the sysOID to a unique device name plus identifier (if a compiled MIB version is available). This value will be displayed in the SysOID Translation column in the VNE drivers page, making it easier to identify the device.
Ability to add multiple traps simultaneously, in bulk, irrespective of the trap type. This is useful if you need to add support for a large number of traps of different types.
Ability to display MIB names instead of numbers in the trap details, for easier identification.
Ability to enhance the event details and make them more useful by outlining the actions that should be performed after receiving the event. The recommended actions will appear in the Troubleshooting section of the event or ticket properties (Details tab).
In previous versions of Prime Network, the event description was a static string and could not be changed. From Prime Network 4.1, you can define more descriptive event descriptions by including runtime parameters with dynamic values, such as interface names, threshold levels, and so on. These parameter values will be included in the event description displayed in Prime Network Vision or Events, making it easier to identify, at a glance, what the event is about without having to drill down to the event details.
Prime Network Integration Layer
Prime Network 4.1 introduces the following new integration layer features and enhancements:
User Guide—Information has been streamlined into setup, device management, fault management, and network management sections. The document includes a new chapter that explains and contains illustrations showing how Prime Network responds to incoming events.
Supported VNEs Addendum—Contains device support information for all CCM functions and command scripts.
This section provides important information of which you should be aware before using Prime Network 4.1.
Installation and Upgrade
Operations Reports does not support IPv6. The gateway, database server (Oracle and Infobright), and the units should be installed with IPv4.
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 upon Upgrade Only
The configuration audit feature in Change and Configuration Management is being replaced with Compliance Audit. In Prime Network 4.1, the legacy configuration audit feature is available only when upgrading to Prime Network 4.1 from the Prime Network 3.10 and 3.11 versions that included this functionality.
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 Network 4.1 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 4.1 using a hostname instead of an IP address.
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 4.1's ability to display installed IOS-XR packages and distribute IOS-XR images to the device. While Prime Network 4.1 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 when in Suite Mode
Command Builder access privileges can be controlled from the Prime Network 4.1 Administration GUI client, even when using Prime Network 4.1 in suite mode.
Automatic Restart After Gateway Reboot
Prime Network 4.1 will restart automatically whenever the gateway server is restarted. This behavior can be disabled (so that Prime Network 4.1 has to be manually started after a gateway restart). See the Cisco Prime Network 4.1 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, ensure that the device must be enabled with SNMPv1 also.
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:
When trying to install a Geographical Redundancy only scenario the following error is received: “SSHProcessError The ssh process was terminated. at setup_replication.pl line 859 *** ERROR: Failed to setup the replication. ABORTING. ***”
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.
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 (./ctl.sh under export/home/<pnuser>/pentaho/server/biserver/tomcat/scripts).
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.
"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.
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.
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.
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.
In Network Discovery, the scheme selected for the device is Product, but when it is created in Prime Network, the scheme is IpCore.
Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.1
The bugs listed in Table 18 were identified too late in the Prime Network 4.1 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 18 Bugs Resolved in Earlier Releases but Still Open in Prime Network 4.1
When two devices are connected via a topological link, and one of the devices becomes unreachable, a link down ticket will show up in the Vision GUI. Once the device becomes reachable again, the ticket should be cleared however it is not cleared.
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.1 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.
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 Cisco.com account with partner level access. You can access the Prime Network Technology Center at: http://developer.cisco.com/web/prime-network/home.
Accessibility Features in Prime Network 4.1
The Prime Network 4.1 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.