Cisco Prime Network 4.1 Release Notes Revised: October 5, 2016 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. Note You can access the most current Prime Network 4.1 documentation, including these release notes, online at http://www.cisco.
Introduction Introduction 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).
New Features and Enhancements • Operations Reports, page 4 • New Technology Support in Prime Network 4.
New Features and Enhancements • System events are now generated for transaction import failure and transaction execution. Compliance Audit The following new Compliance Audit features and enhancements are described in the Cisco Prime Network 4.1 User Guide: • 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.
New Features and Enhancements 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. Carrier Ethernet • 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.
New Features and Enhancements ASA Failover • Inventory and map view of ASA failover configuration. Additional Device Configuration Scripts The following additional configuration scripts are packaged with Prime Network 4.
New Features and Enhancements Administration The following new features and enhancements are described in the Cisco Prime Network 4.1 Administrator Guide. • 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.
New Features and Enhancements • ME 4600 OLT device support: – Support for backup, restore, configuration change log, configuration export, and configuration archive system jobs. – Both OLT and ONU images can be distributed to the OLT file systems. – Images can be activated in both OLT and ONU. • Support for IOS XR package management using TAR file for performing distribute, add, and activate operations together.
New Features and Enhancements 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: • New GUI installation wizard for quicker and easier installation of the PN-IL. For details, see the Cisco Prime Network 4.
Important Notes Important Notes 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.
Prime Network 4.1 Bugs 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. SNMP Configuration When VNE is configured to use SNMPv2 or SNMPv3 for discovery, ensure that the device must be enabled with SNMPv1 also.
Prime Network 4.1 Bugs • Bugs that were fixed in previous releases of Prime Network 4.1 but are still open in the current release because they were identified too late in the Prime Network 4.1 development cycle.
Prime Network 4.1 Bugs Table 1 Installation/Upgrade Bugs (continued) Bug ID Description CSCul97261 status.pl returns the wrong output after upgrade. The ENV variable ANA_VER is missing. CSCuh37129 Upgrade fails if sqlplus passwd contains '&'. CSCud87995 In VCB, user-defined VNE is switched to system default after upgrade. CSCun89143 Unable to launch CCM after upgrading from 4.0.0.1.2 PP to 4.1.
Prime Network 4.1 Bugs Table 3 Bugs Related to Hardware or Software Version Issues (continued) Bug ID Description CSCua70104 'mplsL3VpnDown Trap' is not cleared when SIP is powered up. CSCuh38759 Fan is not modeled in Physical Inventory for CISCO ISR 3945 devices. CSCug17875 LLDP neighbor table is not modeled for Whales device. CSCuj99023 NCS 6008: The Modular OS does not show all of the data in the logical inventory as part of the technology modeling.
Prime Network 4.1 Bugs Table 3 Bugs Related to Hardware or Software Version Issues (continued) Bug ID Description CSCun46551 Nexus 7000 VNE fails to parse VPC PEER_KEEP_ALIVE_RECV syslog messages when domain number is more than one digit. CSCug73614 ASR 901 CPU spikes. Technology-Related Bugs Table 4 Technology-Related Bugs Bug ID Description CSCun13956 Missing entries in Label Switching table and VRF Label table for ASR 9000 IOS XR 4.3.2.
Prime Network 4.1 Bugs Table 4 Technology-Related Bugs (continued) Bug ID Description CSCun08829 ASR 5000 VNE becomes unreachable every polling cycle for a period of around two minutes when there are a few thousand AAA Diameter Route entries. CSCum70578 TP Tunnel is missing in the map pseudowire view. CSCum54365 Prime Network stops discovering TP tunnel services. AVM35 process hangs, TP-tunnel Service Discovery plug-in stops working.
Prime Network 4.1 Bugs Change and Configuration Management (CCM) Bugs Table 6 CCM Bugs Bug ID Description CCSCtq26336 When the Nexus 7000 VNE is stopped, its configuration archives are removed. CSCug63646 After restoring archived config to startup-config on an ASR 903 device, the latest startup-config is not retrieved although the configuration is different. CSCun15580 In Archive page, edit configuration does not work when there is more than one page of configuration to be edited.
Prime Network 4.1 Bugs Table 8 Command Manager Bugs (continued) Bug ID Description CSCul89089 Rule "Check maximum number of SSH authentication retries" in System policy "SSH Parameters" is not working properly. CSCul46999 With Internet Explorer version-8, there are problems in the Rule Input dialog when adding "List of Values" in table, enabling/disabling of fields, and edit functionality.
Prime Network 4.1 Bugs Operations Reports Bugs This table shows open bugs in the new Prime Network Operations Reports component. Table 11 Operations Reports Bugs Bug ID Description CSCun18255 Inventory data report stops responding and remains “in-progress” for a long time. CSCuf48387 Pie chart distribution is not equal to 100% in report. CSCug14300 Bottom scroll bar in interactive reports is not fully visible. CSCug34500 Drop down list does not disappear when performing a subsequent action.
Prime Network 4.1 Bugs Table 12 VNE/AVM Bugs (continued) Bug ID Description CSCui81411 Bridge table is not modeled for Nexus 1000v device. CSCug89915 VNE is unsynchronized and AVM crashes even with 2GB of memory. CSCum81307 VNE consumes a lot of memory. Suite-Related Bugs Table 13 Suite-Related Bugs Bug ID Description CSCuh59694 Although vCenter is not modeled in Prime Central, vCenter details may temporarily appear in the Prime Central GUI.
Prime Network 4.1 Bugs Table 16 Resolved Bugs in Cisco Prime Network 4.1 Bug ID Description CSCuc44069 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. CSCuh45319 Prime Network incorrectly creates topological links between multi-chassis devices. CSCuh40148 ASR 901: MPLS label range in activation script is different from the range supported on the device.
Prime Network 4.1 Bugs Table 16 Resolved Bugs in Cisco Prime Network 4.1 (continued) Bug ID Description CSCuh81373 Crtl + Space adds parameter display name instead of variable name. CSCuh81422 Import command fails with message "implementation already exists" although the command has been deleted. CSCuh82257 Command import does not work when using IE 9.0.
Prime Network 4.1 Bugs Table 16 Resolved Bugs in Cisco Prime Network 4.1 (continued) Bug ID Description CSCug27611 A system event stating "Number of orphan events reached major limit" is generated. CSCuh96294 Element type filtering is not working in Prime Network Events. CSCuh57307 Transaction job does not have a tasks list in the Job results screen. CSCug34467 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 Network 4.1 Bugs Table 16 Resolved Bugs in Cisco Prime Network 4.1 (continued) Bug ID Description CSCuf89644 Module is not discovered properly for a Nexus 7000 device because the OID returned by the device is incorrect. CSCuh35846 Missing values when editing a command for a second time. CSCue71985 Wrong association of syslog alarms for TP-tunnel interfaces on ASR 9000 devices. CSCuh52235 Repetition of Ethernet OAM Session syslog in Event Notification (ENS).
Prime Network 4.1 Bugs Table 17 Closed Bugs in Cisco Prime Network 4.1 (continued) Bug ID Description CSCug99337 Saved PDF report cannot be opened by Acrobat Reader. CSCuh71664 When opening a scheduled HTML report from an email, only tabular data is shown. Charts and graphs are not displayed. CSCuh72361 In Operations Reports, a report does not display unless all permissions are given at the folder level.
Prime Network 4.1 Bugs 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.
Related Documentation 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.
Accessibility Features in Prime Network 4.1 Cisco Prime Network 4.
