Guest

Cisco Prime Network

Cisco Prime Network Release Notes, 3.11

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

Cisco Prime Network 3.11 Release Notes

Contents

New and Changed Information

Introduction

New Features and Enhancements

New Device Support Information

Installation and Upgrade Notes for Prime Network 3.11

Important Notes

Upcoming Changes in Feature Support

Prime Network 3.11 Bugs

Open Bugs

Installation/Upgrade Bugs

Bugs Related to Hardware or Software Version Issues

Command Script Bugs

Technology-Related Bugs

VCB Bugs

Change and Configuration Management (CCM) Bugs

Fault Management Bugs

Reports Bugs

VNE/AVM Bugs

Network Discovery Bugs

Resolved Bugs

Closed Bugs

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

Using the Bug Search Tool

Related Documentation

Accessibility Features in Prime Network 3.11

Obtaining Documentation and Submitting a Service Request


Cisco Prime Network 3.11 Release Notes

Revised: September 17, 2013

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

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.

Contents

This document contains the following sections:

•New and Changed Information

•Introduction

•New Features and Enhancements

•New Device Support Information

•Installation and Upgrade Notes for Prime Network 3.11

•Important Notes

•Prime Network 3.11 Bugs

•Using the Bug Toolkit, page 15

•Related Documentation

•Accessibility Features in Prime Network 3.11

•Obtaining Documentation and Submitting a Service Request

New and Changed Information

The following table describes information that has been added or changed since the initial release of this document.

Date
Revision
Location

September 17, 2013

Added information about third-party device package availability.

New Device Support Information

Replaced Bug Toolkit with Bug Search (Bug Toolkit will be deprecated in the next few months)

Using the Bug Search Tool

May 2013

Initial release.

—


Introduction

Cisco Prime Network 3.11 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.

Prime Network 3.11 is a minor release that extends support for mobility networks into the CDMA network to include Evolved Packet Data Gateway (ePDG), Packet Data Serving Node (PDSN), Home Agent (HA), and High Rate Packet Data Serving Gateway (HSGW). This release also provides modeling and representation of pseudowire headend configuration on ASR 9000 devices. In addition, it provides a set of configuration scripts for staging of ASR 901 and ASR 903 devices plus IP routing configuration of ASR 9000 devices.

New Features and Enhancements

Prime Network 3.11 includes the following new features and enhancements, all of which are documented in the Cisco Prime Network 3.11 User Guide:

•RAN Backhaul enhancements, including:

–A set of configuration scripts for staging of ASR 901 and ASR 903 devices plus IP routing configuration of ASR 9000 devices.

–Discovery and representation of pseudowire headend configuration on ASR 9000 devices.

•Mobility enhancements, including:

–Discovery, representation, and trap monitoring of CDMA configurations on ASR 5000 gateways (StarOS 14.1), including ePDG, HSGW, Home Agent, and PDSN.

–A set of configuration scripts for application on mobility gateways, such as ASR 5000/5500 devices. This includes scripts for ePDG, HSGW, ToD, and PDSN.

•Additional configuration scripts to enhance support for the following technologies on ASR 901, ASR 903, and ASR 9000 devices:

–BGP

–IS-IS

–Clocking (SyncE and 1588)

–VRRP

–MPLS

–Unified MPLS

–TDM, ATM, IMA and Channelized POS

New Device Support Information

Prime Network 3.11 incorporates all the device support additions that were provided in the January 2013 Device Package (Prime Network 3.10 DP 1301). The contents of DP 1301 are listed in Addendum: Additional VNE Driver Support for Cisco Prime Network 3.11. Additional device support will be available in the next DP, to be released in May 2013. It will be available for download from the Prime Network download site on Cisco.com.

For third-party devices, you can download and install new support using the August 2013 third-party DP (3.10x-3.11x-TPDP1308). The contents of that DP are listed in Cisco Prime Network 3.11 Device Package Third-Party VNE Reference Guide.

Installation and Upgrade Notes for Prime Network 3.11

There have been no major changes in the installation and upgrade procedures since the previous release of Prime Network. Please follow the procedures in the Cisco Prime Network 3.10 Installation Guide for Prime Network 3.11 installation or upgrade.

Please be aware of the following before installing or upgrading:

•If you run network-conf as part of the installation/upgrade, Prime Network 3.11 automatically enables the Network Discovery tool. If you run network-conf independently of the installation/upgrade, follow the procedure in the Next Steps section in the Cisco Prime Network 3.10 Installation Guide to manually enable the Network Discovery tool.

•For open issues that might be encountered during installation or upgrade, see Installation/Upgrade Bugs.

Important Notes

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

Browser Limitations for Prime Network Web Components

•Firefox—Users might not be able to connect to the Prime Network 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/9—The Network Discovery Profile page might not display properly and might take longer than usual to load.

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.30, and Cisco is working on resolving it. If you encounter this issue, try restarting the VNE.

Integration of Traps from Cisco Prime Performance Manager (PPM) Version 1.4

Network Event Collector receives threshold crossing alarm (TCA) events from PPM components and generates tickets that can be viewed in Prime Network Events.

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 3.11 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 3.10 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.

•ENTITY-MIB

•IF-MIB

•ENTITY-STATE-MIB

•CISCO-ENTITY-FRU-CONTROL-MIB

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

configure

snmp mib ENTITY-MIB

snmp mib IF-MIB

snmp mib ENTITY-STATE-MIB

snmp mib CISCO-ENTITY-FRU-CONTROL-MIB

To verify if the above MIBs are enabled, use: 

show snmp server

Upcoming Changes in Feature Support

Support for Solaris to be Removed in the Next Release of Prime Network

Prime Network 3.11 is the last release to provide support for Prime Network installation in a Solaris environment. From the next release of Prime Network, only Linux environments will be supported.

Support for Activation and Workflow Components for Upgrade Customers Only in the Next Release of Prime Network

Prime Network 3.11 is the last release to provide full support for Activation and Workflow functionality. In the next release (Prime Network 4.0), this functionality will be available only for upgrades, not for new installations of Prime Network.

Prime Network 3.11 Bugs

This section contains the following information:

•Open Bugs

•Resolved Bugs

•Closed Bugs

•Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.11

•Using the Bug Search Tool

Open Bugs

The following tables identify bugs that are open in Prime Network 3.11, using 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 3.11 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

•Technology-Related Bugs

•VCB Bugs

•Change and Configuration Management (CCM) Bugs

•Fault Management Bugs

•Reports Bugs

•VNE/AVM Bugs

•Network Discovery Bugs

Installation/Upgrade Bugs

Bug ID
Description

CSCui64970

Prime Network webstart clients fail to start.

CSCug68965

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

CSCud87332

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

CSCug68959

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.

CSCug68949

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

CSCue00169

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

CSCud87138

After upgrade, an ICMP VNE is not modeled.

CSCud87142

After upgrade, a cloud VNE is not modeled.

CSCud87149

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

CSCud88180

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

CSCud87995

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

CSCud01686

New unit added after upgrade is in unreachable state.

CSCuc90531

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.

CSCug22532

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. ***"

CSCud83905

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

CSCud83907

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

CSCug79313

Cannot decouple Prime Network from Prime Central.


Bugs Related to Hardware or Software Version Issues

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

Bug ID
Description

CSCud14557

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

CSCug21624

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

CSCue86942

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

CSCtw65605

VEM module status shown as Unknown for Nexus1000V.

CSCub30191

Inconsistent or incorrect MAC Address modeling for Nexus VNE.

CSCty79971

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

CSCtq36525

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

CSCtu24056

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

CSCuf89644

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

CSCud22188

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

CSCue12403

Unexpected physical inventory changes.


Command Script Bugs

Bug ID
Description

CSCug48793

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

CSCug60590

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

CSCug56551

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

CSCug53511

Beanshell error received for ASR9000 Create/Modify APS script.

CSCue96698

Exception received for Create PDSN Context Security command when special characters are entered.

CSCug42747

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

CSCug43206

Selected policies are not deleted when modifying the PDSN Policy.


Technology-Related Bugs

Bug ID
Description

CSCug68358

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

CSCug66629

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

CSCug21885

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

CSCug54195

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

CSCug54176

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

CSCug33989

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

CSCug64781

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

CSCug62422

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

CSCug42988

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

CSCud52807

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

CSCug18142

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

CSCug26824

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

CSCud97174

Virtualization inventory does not update after changes.

CSCug14910

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

CSCue48689

No LAG links are displayed between Nexus devices.

CSCug47928

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

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.

CSCug20371

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

CSCue00084

CFM Local MEP is not modeled on ME3400 devices.

CSCuc50104

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

CSCuc85097

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

CSCuc85479

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

CSCtz80712

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

CSCtj30236

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

CSCtu27429

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

CSCuc94395

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

CSCud09522

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.

CSCud22188

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

CSCub31023

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

CSCuf60889

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

CSCuf30430

Correlation flow failed going through encapsulation untagged on SI.

CSCug35754

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

CSCue92339

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

CSCug17323

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

CSCuf44013

BFD interval is not shown on ASR 903 device.

CSCue07259

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

CSCug23445

Duplicate data is shown in the Service Policy Properties page.

CSCuc43901

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

CSCuc92336

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


VCB Bugs

Bug ID
Description

CSCug52980

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).

CSCtu33115

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

CSCuc81714

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.

CSCuc13194

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".

CSCud00287

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.


Change and Configuration Management (CCM) Bugs

Bug ID
Description

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.

CSCug18535

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.

CSCud10404

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.

CSCuc80344

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

CSCuc52800

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).

CSCud15961

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.

CSCud98020

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

CSCug13285

Flash is not modeled so CCM does not get the storage info using BQL.

CSCue92486

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

CSCug14761

Users with Operator profile can schedule boot IOS changes.

CSCug26226

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

CSCug26986

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.

CSCue43530

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

CSCue86820

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


Fault Management Bugs

Bug ID
Description

CSCug18701

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.

CSCuf26689

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

CSCug10225

Duplicate alarm ID is displayed in Prime Network Events.

CSCue21779

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.

CSCue94445

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

CSCuf77169

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

CSCuf90721

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.

CSCuf94075

"Link down on unreachable" trap is not cleared.

CSCug45873

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

CSCtx01472

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

CSCuc82018

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.

CSCug27611

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

CSCug38135

No EPM ticket notifications are forwarded to north bound interface.

CSCuf77270

The AVM log is filled with INFO messages.

CSCug17375

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.

CSCuf39121

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

CSCuf25014

New LDP neighbor events are not correlated to existing tickets after a previous LDP neighbor event was cleared.

CSCuf25939

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

CSCuf52803

VNE stops processing syslogs and traps.


Reports Bugs

Bug ID
Description

CSCud74402

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

CSCud03138

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


VNE/AVM Bugs

Bug ID
Description

CSCue81102

List size continually increases and AVM crashes.

CSCue04500

Device CPU spikes.

CSCue08619

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

CSCuc81740

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

CSCtj92252

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

CSCud05482

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

CSCuf77193

AVM crashes with "Out Of Memory" error.

CSCug46195

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

CSCud44619

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

CSCue51047

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

CSCue15812

The physical inventory of the device is not modeled.

CSCue87299

Physical inventory of Nexus 3000 devices is not modeled.

CSCue93598

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

CSCuc83565

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

CSCue96677

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

CSCud92702

Flooding of logs while loading Cisco 7600 device.

CSCuf39058

Nexus primary card redundancy status is always shown as None.

CSCtw65605

VEM module status shown as Unknown for Nexus 1000V.

CSCua33760

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

CSCud18484

Chassis disconnected alarm will be raised in Prime Network when Nexus 2K is disconnected from Nexus 5K. However, it is not cleared when the connection is re-established in the device setup.

CSCue38089

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

CSCug15195

ASR 903 remains in Discovering state.

CSCug42735

ASR 901 VNE is not modeled in Product scheme.

CSCug48442

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


Network Discovery Bugs

Bug ID
Description

CSCuc96102

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.

CSCuf56479

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


Resolved Bugs

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

Bug ID
Description

CSCug43813

Missing PW topology/service links when PW goes over MPLS-TP.

CSCtw29586

FlashDevice Size is not modeled on Cisco ME3600 series device running Cisco IOS versions 15.1.2.EY and 15.1.2.EY1.

CSCuc53525

Cannot log into the Prime Network GUI client after an upgrade from 3.8 to 3.10 in a Local HA setup.

CSCub55176

Card down/UP ticket is not raised for module N7K-F248XP-25 in EVNE for Nexus 7000.

CSCub86764

IPv6 access list entries not modeled in ASR 9K,CRS and GSR XR devices.

CSCuc71849

On 7600 routers running IOS 15.1, multiple NullPointerExceptions are received in OspfInterfacePHLoader class and correspondingly, multiple OSPF property holders are not created.

CSCuc73922

When the ASR 9000 is configured with Clock and SyncE details, SyncE properties are shown as Unknown.

CSCuc90543

Nexus port admin status modeling incorrect for Nx-OS 6.1(1).

CSCty74187

ASR 5500 device, fan tray down service alarm is not cleared.

CSCud14121

Port up/down alarms are not generated for ports when Nexus 3000 is added using Reduced Polling.

CSCuc75229

For UCS device, some of the HBA and NIC Ports are not shown in the inventory.

CSCuc39142

Out interfaces of TE Tunnels missing when one of the tunnel edge devices is reloaded.

CSCuc76082

CFM MEP configured on Ether channel is not modeled and not shown in the logical inventory under the CFM container.

CSCuc77359

Clock PTP Service logical inventory is not populated on ASR 903 device. The clock PTP service logical inventory has a wrong PTP State for ASR901 device if the state on the device is either "Phased_Aligned" or "Freq_Locked".

CSCuc85484

Diameter peer with IPv6 address is not updated in Prime Network.

CSCuc91568

OSPF neighbor down service and ticket not created after the neighbor has been removed on ASR 903 device.

CSCuc92314

IPv6 Routing Table tab does not exists under ME3800 Routing Entity container in PN.

CSCuc97852

DWDM technology related properties show wrong/blank values under Physical Inventory for the ports under supported DWDM modules.

CSCuc54022

After initiation of 7609 device software upgrade, the VNE created 'BFD connectivity down' alarm which stays uncleared indefinitely although BFD session status was restored back to UP.

CSCuc74616

After IOS upgrade and router reload, the 7600 VNE was automatically restarted, dropping current state and disconnecting all the links. After the device and links were rediscovered, the OSPF Neighbor Down alarm correlated to corresponding Link Down root cause alarm was not cleared, keeping the resulting link alarm in Major state. Following Poll Now and VNE restart operation could not clear the alarm although inventory shows that the OSPF neighbor is UP.

CSCub55128

LAG Down ticket is not raised when Port Channel is shut in Nexus 7K.

CSCud05474

Poll now is not working for following technologies on Nexus 7000 device:

MPBGP, STP, Arp Table, Routing Table, Bridges, Ethernet LinkAggregation.

CSCud07691

VRF Routing Table is not modeling for Nexus 7K.

CSCud09747

"Failed to save data" error is thrown when trying to edit user-defined software versions.

CSCud09395

Copy startup-config to running-config will not work for CPT devices.

CSCuc80341

When using theIE8 browser, a script error appears when clicking on the last run results page.

CSCuc63379

Backup/restore running config job is not implemented.

CSCuc06110

Sort order issue in Archived Configurations page in Change and Configuration Management.

CSCud15947

Sync entry is not removed from sync page after performing synchronize job for IPv6 VNE.

CSCuc67095

Event Notification Service does not forward business tag information on physical port.

CSCud16596

Workflow execution failed, with "IllegalArgumentException: Invalid command syntax. no such command" error.

CSCuc71283

Cannot save map as PDF or SVG type.

CSCud05936

Existing value is not shown when renaming a service added to a map.

CSCuc86976

False CARD OUT alarms are received from ASR1006 and ASR 9006 devices.

CSCuc96770

AVM crashes.

CSCuc82722

Multiple VNEs with the same agentIDs in the avmxxx.xml files within the system.

CSCtz41239

Incorrect outgoing interface for endpoint LSPs on IOX devices.

CSCua59577

Device goes out of sync.


Closed Bugs

The following table identifies bugs that were listed as open bugs in the Prime Network 3.10 Release Notes and have since been closed.

Bug ID
Description

CSCud12790

Adaptive polling mechanism incorrectly putting CRS into slow polling and maintenance mode. It never returns to normal even though the usage is below low threshold for consecutive # polls defined in low_tolerance.


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

The bugs listed in the following table were identified too late in the Prime Network 3.11 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.

Bug ID
Description

CSCua35492

'Chassis Connected' clearing service alarm will not appear when satellite chassis is reconnected for Multi-Chassis devices.

CSCud74402

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

CSCud42163

When trying to add an XR package, no package listed in CCM Add Package screen.

CSCud55430

Fault category for ACE syslog is not updated in Vision.

CSCud38658

MPLS TE Tunnel down ticket is not correlated under the BFD down ticket.


Using the Bug Search Tool

Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.

Step 1 Go to http://tools.cisco.com/bugsearch.

Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search 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, enter the bug ID in the Search For field and press Return.

Step 4 To search for bugs in the current release:

, click the Search Bugs tab and specify the following criteria:

a. In the Search For field, enter Prime Network 3.11 and press Return. (Leave the other fields empty.)

b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth. To export the results to a spreadsheet, click the Export All to Spreadsheet link.

Related Documentation

For a list of the guides available for Prime Network 3.11, see the Cisco Prime Network 3.11 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.

Accessibility Features in Prime Network 3.11

The Prime Network 3.11 software does not provide accessibility features.

However, 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 accessibility@cisco.com.

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.

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.

© 2013 Cisco Systems, Inc. All rights reserved.