Table Of Contents
Cisco Prime Network 3.10 Release Notes
Revised: February 28, 2013
This release notes document provides an overview of the new features and enhancements in this release, highlights important issues you need to know before using this release, and describes how to access information on Prime Network 3.10 bugs.
Note You can access the most current Prime Network documentation, including these release notes, online at http://www.cisco.com/en/US/products/ps11879/tsd_products_support_series_home.html.
These release notes contain the following sections:
New and Changed Information
The following table describes information that has been added or changed since this document was first published.
Date Released Revision Location
February 28, 2013
CCM Device Support—Added that a complete list of devices that support CCM in this version of Prime Network is provided in the Addendum: Additional VNE Driver Support for Cisco Prime Network 3.10.
Cisco Prime Network 3.10 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 IP NGN suite for customers needing end-to-end network management lifecycle capabilities.
Until now, Prime Network's operations support functionality has been focused on the network traffic transport and distribution areas of service provider networks. In this release, Prime Network expands its device operation and administration and network assurance support to:
•Wire line subscriber network infrastructures: BNG
•Mobility: LTE support
•Datacenter infrastructures: UCS, Nexus, datacenter connectivity and virtualization
•Network Virtualization (nV): ASR 9000 cluster and satellite
This section provides important information of which you should be aware before using Prime Network 3.10.
Automatic Restart After Gateway Reboot
Prime Network 3.10 will automatically restart 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 3.10 Administrator Guide for more information.
Auto-Discovery of Unsupported Modules
In Prime Network 3.10, a new mechanism to automatically discover unsupported module types was introduced. The discovery 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:configuresnmp mib ENTITY-MIBsnmp mib IF-MIBsnmp mib ENTITY-STATE-MIBsnmp mib CISCO-ENTITY-FRU-CONTROL-MIB
To verify if the above MIBs are enabled, use:show snmp server
New Features and Enhancements in Prime Network 3.10
The following topics describe the new features and enhancements introduced in Prime Network 3.10:
New Technology Support in Prime Network 3.10
Prime Network 3.10 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 3.10 Supported Cisco VNEs.
•Y.1731 IPSLA probes
•In topology views showing Ethernet Virtual Connection(s), Prime Network 3.10 allows the addition of a CPE network element to the map and manual attachment of the device to an edge Ethernet Flow Point (EFP).
•MPLS-TP bulk lockout—Allows locking or unlocking multiple MPLS-TP tunnels on different VNEs at the same time. This is required when performing maintenance in the network. It enables you to divert the MPLS-TP packets through an alternative LSP.
Prime Network 3.10 provides the first phase of support for multicast, focusing on representation of multicast configuration attributes and monitoring of events.
•IP Multicast - representation of baseline IPv4 and IPv6 configurations
•MPLS Multicast - representation of multicast Label Distribution Protocol (mLDP) and multicast VPN (mVPN) configuration attributes for IPv4 and IPv6 on PE routers
Satellite and Cluster Technologies
•ASR 9000 cluster support:
–Chassis inventory shown in physical inventory
–Table showing all physical ports connecting the Active and Backup Chassis in the cluster
–Support for cluster-related traps and syslogs
–Inter-chassis link state shown in inventory
•Topology visualization for multi-chassis devices—ASR 9000 host device plus satellites are represented in the map as an aggregation that can be expanded. When the aggregation is expanded, the host and satellite devices are represented separately with inter-chassis links.
Broadband Network Gateway (BNG)
•BNG policies and global configuration attributes discovered and shown in logical inventory
•IP pool management and monitoring
•Retail model of BNG with PPPoE PTA and IPoE subscriber support
•Required AAA, Radius Server components & attributes
•DHCP (IPv4) profiles for IP subscriber
•BBA groups for PPPoE subscriber
•Dynamic templates for IP & PPP subscriber
•Class of Service (Class-Map)
•QoS and Subscriber control policies
Prime Network 3.10 completes the second phase of support for LTE gateway functionality by representing:
•GGSN service configurations on ASR 5000 and ASR 5500 devices.
•StarOS APN service configurations
•StarOS P-GW and S-GW service configurations
•GPRS Tunnel Protocol Prime (GTPP) accounting configurations on ASR 5000 and ASR 5500 devices.
•Operator policies, APN remaps, and APN profiles
•StarOS configurations for Evolved GPRS Tunneling Protocol Control (EGPTC) messaging
•AAA configurations including AAA groups and diameter endpoints
•IP address pool configurations and association to service contexts on ASR 5000 and ASR 5500 devices
•System Architecture Evolution (SAE) Gateway configurations on StarOS that combine S-GW and P-GW functionality
•Local time zone of ASR 5000 and ASR 5500 devices
•PCRF faults generated by CPM 3.0 installed over UCS
•Covers aggregation layer support (VDCs on Nexus), compute support from UCS physical inventory to the virtualization layer (hosts and VMs)
–Inventory collection and visualization of the physical/virtual environment, limited to auto-discovery of hypervisors and VMs and compute resources, i.e., CPU and memory.
–Mapping of the hierarchical relationships between virtualized components - servers and virtual machines.
–Representation of the relationship between UCS blades, hypervisors and VMs
•Representation of FabricPath configuration attributes on Nexus 5000 and 7000 devices
•Representation of configuration attributes for the Virtual Port Channel feature on Nexus 7000 and Nexus 5000 series devices
Enhanced modeling of redundancy and representation of redundancy parameters in the physical inventory.
Additional Device Configuration Scripts
Prime Network 3.10 provides new predefined configuration scripts to configure the following services on ASR 5000 and ASR 5500 devices:
•GGSN, APN, GGTP, GTPU, EGTP, and DHCP
•P-GW and S-GW
•Home Agent, Subscriber, HA SPI List, AAA Group, Route Map, Route Access List, and Proxy DNS Intercept List
•Active Charging, RuleDef, RuleBase, AccessRuleDef and GroupOfRuleDef
•Port Interface, BGP, VRF, and BFD
Prime Network Administration
The following new features and enhancements are described in the Cisco Prime Network 3.10 Administrator Guide.
Session and User Management
•New Session Manager GUI which tracks all active GUI and NBI user sessions. Session Manager can be used to disconnect sessions and request users to re-login, or completely terminate sessions.
•New configurable global account inactivity period which, when exceeded, disables a user's account. The account can be re-enabled from the Administration GUI client.
•New configurable global password rules:
–Configurable popup message that reminds users that their password is about to expire.
–Configurable setting to control how many consecutive characters from a previous password cannot be used.
•New per-user authorization mode for job scheduling in global security settings. When this mode is enabled, individual users can be granted permissions to schedule jobs across the product. Users who do not have job scheduling permissions will not be allowed to schedule jobs.
Note See also Command Scripts and Activations, for information on other configurable options you can use to manage how users run command scripts and activations.
Script to Change Gateway IP Address
New script for updating the Prime Network registry with a new gateway IP address.
The embdctl command provides a new option that changes the SMTP server for e-mail notifications from an embedded database
New Adaptive Polling tab in the VNE properties dialog box for fine-tuning adaptive polling (how Prime Network responds when a device has a CPU spike). After setting the upper and lower CPU thresholds, the following can be configured:
•The number of polls required to move a VNE from normal polling to slow polling, and from slow polling to maintenance mode (where all polling except for CPU usage is suspended)
•The number of polls required to move a VNE back to regular polling
•The delay (in milliseconds) between SNMP and Telnet commands that are sent from the VNE to the device.
Reduced Polling (Event-Based Polling) for VNEs
Reduced polling is now the default polling method for all VNEs and is also supported by the Network Discovery mechanism. This default setting can be changed, if necessary. If a VNE does not support reduced polling, it uses regular polling.
If desired, you can "force" reduced polling for a VNE. In this case, if the VNE does not support reduced polling, Prime Network will generate a Device Unsupported event. This is controlled from the Polling tab in the VNE properties dialog box.
Event Notification Service
The Event Notification Service has been enhanced as follows:
•Notifications can include network element properties (such as an interface description) and business tags in order to provide more information about the alarm source
•Notifications can include the alarm location as a user-friendly string (instead of an Object Identifier)
•Multiple notification services can use the same destination IP and port (UDP only). For example, you can forward these two services to the same destination:
–One notification service that forwards specific service events for a group of VNEs
–Another notification service that forwards syslogs and traps for a different group of VNEs
Command Scripts and Activations
•Configurable option to require users to enter their device access credentials when executing an activation or command script (as opposed to using the Telnet or SSH credentials defined for the VNE). The device user name is listed in Provisioning and Audit events, allowing you to track user actions. For cases in which this option is not supported (scheduled commands or activations or for SNMP commands), the VNE's Telnet or SSH credentials will be used.
•Configurable option to display a message upon execution of commands or activations, warning the user that the action might interrupt services. The system provides a default message which can be edited in the Commands and Activations global settings. In addition, when creating a command script using Command Builder, the message can be edited or the global setting can be overridden.
•Support for changing a VNE IP address without having to create a new VNE.
•Support for networks where two VNEs have the same IP address.
•Ability to configure global defaults for VNEs:
–SNMP V1/V2 community read/write credentials and SNMP V3 authentication and encryption settings (new VNEs use SNMP V2 by default)
–Telnet and SSH V1/V2 credentials
–New EMS scheme which only polls devices for system information and physical inventory
–Ability to create customized schemes so you can specify which technologies and topologies you want Prime Network to model and monitor
•Support for TL1 parameters in the VNE creation editor (for using Configuration and Change Management on Cisco Carrier Packet Transport devices)
•Enhanced ivne script with a new option to display only the most recent VNE Device Package that is installed on the gateway (rather than simply listing all installed packages)
Change and Configuration Management
The following new Change and Configuration Management features and enhancements are described in the Cisco Prime Network 3.10 User Guide.
•Configuration Audit—the ability to audit configurations on a device against a specified baseline configuration policy file. The configuration policy is compared with the actual running configuration on the device, discrepancies are identified and published in a report.
•Scheduling of configuration and image management jobs is limited to users who have permissions to perform the operation.
•For configuration and image transfers, the TFTP directory available in the Prime Network gateway and/or unit can be modified using commands.
•For Cisco Carrier Packet Transport (CPT) devices, the Prime Network unit user credentials must be added to the registry. This is required because Prime Network initiates the FTP operation using a TL1 interface, and the TL1 commands require the username and password as input parameters. After you add this information to the registry, the credentials are automatically read when needed.
•Flash Player version 10 or higher must be available to view the Configuration Restore page.
•Configuration Restore—For Cisco CPT devices, the Running option restores the selected configuration to startup config and then to running config on the device.
•While importing images from an external repository or from a file system, CCM displays all images or packages (bin, pie, smu, and so on) from the directory specified in the Image Management Settings page, and also from its sub directory, in order to support tar files.
•Ability to perform an in-service software upgrade (ISSU) for Cisco ASR 903 devices and Cisco Carrier Routing System (CRS) to update the router software with minimal service interruption.
•Ability to modify boot priorities for Cisco ASR 5000 series devices and then perform activation.
•Satellite support for Cisco ASR 9000 devices, as follows:
–Synchronization of all satellites together without activation.
–Activation of the satellite pie image on Cisco ASR 9000 device with and without synchronization of satellites. You must run a CLI/XML command to check for compatibility and then push the image to the remote satellite.
For a complete list of devices that support CCM in this version of Prime Network, see the Addendum: Additional VNE Driver Support for Cisco Prime Network 3.10.
The following new fault management features and enhancements are described in the Cisco Prime Network 3.10 User Guide.
•Stronger alignment with ITU-T Recommendation X.733 by displaying fault nature (ADAC or ADMC) and category (communications, QoS, processing, and so on).
•Provision of probable cause and recommended action for ASR 5000 traps to aid in troubleshooting fault conditions.
•Integration of traps from Cisco Prime Performance Manager (PPM) version 1.3—The Prime Network Event Collector receives threshold crossing alarm (TCA) events from PPM components and generates tickets that can be viewed in Prime Network Events.
•Event and ticket properties show the date and time when the ticket was created, based on the time zone of the device (For ASR 5000 and ASR 5500 devices)
•New (predefined) Events Troubleshooting Info report that provides probable cause and troubleshooting information for traps
•Several Event Notification Service enhancements. See Prime Network Administration.
•When creating a command script, a new Text Area input type is now available. This enables cutting and pasting multi-line strings, including end of line characters <CR><LF>. This is referenced in the script as a single attribute.
•User-authentication based execution of activations or command scripts (if this option is enabled in Prime Network Administration).
•Warning of potential service interruption upon execution of commands or activations (if this option is enabled in Prime Network Administration). The message can be edited or the global setting can be overridden when creating a command script.
•Ability to clone a job and then edit the job properties. For example, after scheduling a command to run on certain devices, you can clone the job and then add/change devices.
The following new reports are provided in Prime Network 3.10 and described in the Cisco Prime Network 3.10 User Guide.
•Database Monitoring—Shows the state of the database at regular time intervals (e.g., hourly), over a specified period of time. Examples of information shown in this report are number of active tickets, alarms, events, biggest ticket ID, actionable event rate per second, and so on.
•Events Troubleshooting Info—Shows probable cause, action to be taken, and the clearing condition for events.
VNE Customization Builder (VCB)
Several enhancements have been made to the VCB GUI for enabling support for unsupported traps. These enhancements are described in the Cisco Prime Network 3.10 Customization Guide.
•The VCB now allows bulk upload of MIBs.
•When defining subtype mapping, possible values for subtypes are displayed. Users no longer need to enter subtype values in a text field.
•Support can now be added for multiple traps in a single flow; the MIB does not need to be loaded again for each trap.
•Usability enhancements to the wizard for adding support for traps.
Prime Network Integration Layer
Prime Network Integration Layer allows Prime Network to seamlessly integrate with an OSS by leveraging standardized interfaces. This integration layer functionality can be conceived as an additional layer running on top of Prime Network exposing 3GPP and MTOSI web services. Furthermore, a migration from this standalone deployment to Prime Suite mode is possible, if a Suite environment is available. See the Cisco Prime Central Quick Start Guide for more information.
In this specific release, inventory management functionality has been provided, both over 3GPP and MTOSI. While the 3GPP inventory management functionality is for ASR5500 and ASR5000 device types capturing both logical and physical inventory data in 3GPP prescribed XML format, the MTOSI interfaces available in this release retrieve physical inventory data for devices supported by Prime Network. 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 3.10 Installation Guide.
User Documentation Enhancements
The following user documentation changes have been made in Prime Network 3.10:
•The Cisco Prime Network 3.10 Gateway High Availability Guide is a new document that consolidates all of the information related to installing and managing gateway high availability using Red Hat Cluster Suite (RHCS) and Oracle Active Data Guard (ADG). All Red Hat HA-related information that was previously documented in the installation guide, has been moved to this guide. For information on gateway high availability using Veritas, please contact your Cisco representative.
•The Cisco Prime Network 3.10 User Guide now includes information on Change and Configuration Management (CCM), rather than having that information in a separate guide. In addition, descriptions of the command scripts that are packaged with Cisco Prime Network have been moved to the appropriate chapters of this guide and are no longer documented in the reference guide.
•The Cisco Prime Network 3.10 Administrator Guide has been reorganized so that information related to the task you want to perform is easier to find. It also contains a new setup chapter that guides you through the initial tasks you should perform after installing Prime Network.
•The Cisco Prime Network 3.10 Customization Guide has been reorganized so that information related to the task you want to perform is easier to find.
•The Cisco Prime Network 3.10 Installation Guide has been reorganized to make it easier to follow the installation prerequisites and flow. The installation guide now describes Small, Medium, Large, and VM profiles with typical hardware combinations and event rates for Gateway and Unit. It also includes a chapter describing the next steps required after installation of Prime Network.
•The original Cisco Prime Network Reference Guide has been split into individual documents listing supported events, alarms, traps, syslogs, and technologies/topologies, as follows:
–Cisco Prime Network 3.10 Supported Cisco VNEs
–Cisco Prime Network 3.10 Supported Service Alarms
–Cisco Prime Network 3.10 Supported Security and System Events
–Cisco Prime Network 3.10 Supported Syslogs
–Cisco Prime Network 3.10 Supported Traps
–Cisco Prime Network 3.10 Supported Technologies and Topologies
New Device Support Information
Note Prime Network 3.9 with Device Package (DP) 1210 or later: After upgrading to Prime Network 3.10, you must install the latest DP from Cisco.com in order to have the same level of device support that you had in your earlier installation. This is because Prime Network 3.10 includes all of the support that is provided up to Prime Network 3.8.x-3.9.x-DP1209.
Prime Network 3.10 incorporates all the device support additions that were provided in Prime Network 3.8.x-3.9.x-DP1209 (the DP that was released in September 2012). To get the latest VNE support, please download and install the latest Prime Network DP from the Prime Network download site on Cisco.com.
For detailed information about new device support in Prime Network 3.10, please see Cisco Prime Network 3.10 Supported Cisco VNEs.
For a complete list of devices that support CCM in this version of Prime Network, see the Addendum: Additional VNE Driver Support for Cisco Prime Network 3.10.
Prime Network 3.10 Bugs
This section contains the following information:
Open Bugs in Prime Network 3.10
The following sections identify bugs that are open in Prime Network 3.10, according to the following criteria:
•All catastrophic and severe bugs (if any).
•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 3.8.1 development cycle.
The open bugs have been grouped in the following categories:
Device and Software Version Specific Bugs
Network Discovery Bugs
Change and Configuration Management (CCM) Bugs
Fault Management Bugs
Table 8 Workflow-Related Bugs
Workflow execution failed, with "IllegalArgumentException: Invalid command syntax. no such command" error
Prime Network Vision/Events GUI Bugs
Table 11 identifies bugs that were listed as open bugs in the Prime Network 3.9 release notes and have since been resolved.
Table 12 identifies bugs that were listed as open bugs in the Prime Network 3.9 Release Notes and have since been closed.
Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.10
The bugs listed in Table 13 were identified too late in the Prime Network 3.10 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.
Using the Bug Toolkit
This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release.
Step 1 Go to http://tools.cisco.com/Support/BugToolKit.
Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Toolkit page opens.
Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 3 To search for a specific bug, click the Search Bugs tab, enter the bug ID in the Search for Bug ID field, and click Go.
Step 4 To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:
•Select Product Category—Network Management and Automation.
•Select Product—Cisco Abstract Network Abstraction.
Note Cisco Prime Network is the new product name for the former Cisco Abstract Network Abstraction. At this time, the Bug Toolkit does not accept Cisco Prime Network as the product name.
•Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.
•Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information:
–Severity—Choose the severity level.
–Status—Choose Terminated, Open, or Fixed.
Choose Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate suboption (Closed, Junked, or Unreproducible) that appears below the Terminated check box. Select multiple options as required.
Choose Open to view all open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate suboptions that appear below the Open check box. For example, if you want to view only new bugs in Prime Optical 9.5, choose only New.
Choose Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate suboption (Resolved or Verified) that appears below the Fixed check box.
–Advanced—Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds.
–Modified Date—Choose this option to filter bugs based on the date when the bugs were last modified.
–Results Displayed Per Page—Specify the number of bugs to display per page.
Step 5 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.
Note In the search results, the headlines and release-note enclosures might contain both Cisco Prime Network and Cisco Active Network Abstraction product names.
Step 6 To export the results to a spreadsheet:
a. In the Search Bugs tab, click Export All to Spreadsheet.
b. Specify the filename and location at which to save the spreadsheet.
c. Click Save. All bugs retrieved by the search are exported.
If you cannot export the spreadsheet, log into the Technical Support website at http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).
For a list of the guides available for Cisco Prime Network 3.10, see the Cisco Prime Network 3.10 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 Cisco.com account with partner level access, or you must be a Prime Network licensee. You can access the Prime Network Technology Center at: http://developer.cisco.com/web/prime-network/home.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.