Table Of Contents
Cisco Active Network Abstraction 3.7.3
Release NotesNetwork Element Inventory Discovery
Network and Service Monitoring
Cisco ANA Configuration and Image Management
Cisco ANA Network Service Activation
New Features and Enhancements in Cisco ANA 3.7.3
Cisco ANA 3.7.3 Configuration and Image Management Enhancements
Cisco ANA Network Service Activation 1.3 Enhancements
Cisco ANA NetworkVision Enhancements
Features Changed or Removed in Cisco ANA 3.7.3
New Module, Software, and Technology Support
Cisco 7600 Series—Supported Modules
Cisco ASR 1000 Series—Supported Modules
Cisco ASR 9000 Series—Supported Modules
Cisco CRS Series—Supported Modules
Cisco Nexus 7000 Series—Supported Modules
New Alarm, Event, Trap, and Syslog Support
Cisco IOS XR Syslog Support Added
Cisco ASR 9000 Syslog Support Added
New Event-Based Polling Support
New Independent VNE Driver Support
Technology Information Model Object (IMO) Changes
Before Installing Cisco ANA 3.7.3
Changes in the Cisco ANA Installation
Changes in the Upgrade Process
Before Upgrading to Cisco ANA 3.7.3
Cisco ANA 3.7 Upgrade Limitations
Solaris Services and Components
Working with Cisco IOS XR VNEs
Installing the Cisco IOS XR Manageability Package
For Cisco XR 12000 Series Devices
Device and Software-Specific Limitations
JDK DST Timezone Update Tool for Cisco ANA
Cisco ANA Configuration and Image Management
Cisco ANA Workflow Editor Sessions
VLAN Tagged Interface Limitation
Significant Caveats Before Using Cisco ANA 3.7.3
Outstanding Cisco ANA 3.7.3 Caveats that Were Resolved for Earlier Releases of Cisco ANA
Resolved Caveats in Cisco ANA 3.7.3
Closed Caveats in Cisco ANA 3.7.3
Obtaining Documentation and Submitting a Service Request
Cisco Active Network Abstraction 3.7.3
Release Notes
First Published: May 23, 2011, OL-24477-01
Revised: April 26, 2012This document supports the release of Cisco Active Network Abstraction (Cisco ANA) 3.7.3.
Contents
This document includes the following topics:
•
New Features and Enhancements in Cisco ANA 3.7.3
•
•
•
•
•
•
•
•
•
Release Note Revisions
Table 1 describes information that has been added or changed since the initial release of the Cisco ANA 3.7.3 Release Notes.
Introduction
Managing diverse converged, multiple-technology, multiple-layer, and multiple-vendor IP networks is challenging. Cisco ANA addresses this challenge with its model-based, virtual network abstraction. This abstraction serves as a live information foundation that presents a consistent and complete end-to-end topological view of network resources and services to higher-level functions. Cisco ANA creates this abstraction, referred to as the Virtual Network Element (VNE) model, by automatically discovering and polling managed network elements (NEs), and by processing network-generated events.
Cisco ANA supports converged core, aggregation, and access networks based on MPLS, Carrier Ethernet, and IP Radio Access Network (RAN)/Mobile Transport over Packet (MToP) technology foundations, and extends to support other emerging services and technologies.
Cisco ANA is multitiered. Initially, it can be deployed as an element manager for Cisco NEs such as the Cisco CRS and Cisco ASR 9000 series devices. It can later be used as a service-aware network manager that is a foundation for a broad, integrated suite of functionalities including provisioning, resource inventory planning, performance management, and service assurance.
The Cisco ANA Integration Software Development Kit (ISDK) provides developers with tools and a standards-based programmatic interface to the Cisco ANA information model to enable the tight integration of Cisco ANA with OSS and other management applications. The ISDK is backed by developer support and advanced technical services.
Technology Support
Discovering and identifying basic network components is the foundation of Cisco ANA. Cisco ANA obtains end-to-end visibility of the network resources, connections, and dependencies, which enables it to manage and analyze network behavior. Basic components used to build the end-to-end network view include:
•
•
•
•
After identifying and modeling these components, Cisco ANA achieves a complete, end-to-end understanding of the network structure across vendors, technologies, and network layers. The Cisco ANA virtual network model is kept up-to-date (in near-real time) through polling and traps.
Cisco ANA Client Applications
Cisco ANA provides several client applications that offer simple, intuitive interfaces to manage the network and services and to perform required system administration activities. The three main Cisco ANA client applications are:
•
Cisco ANA NetworkVision is also used to launch other clients and tools, such as Command Builder and Cisco ANA Network Service Activation.
•
•
•
For more information, see the Cisco Active Network Abstraction 3.7.3 Configuration and Image Management User and Administrator Guide.
All Cisco ANA client applications support automatic client updates. Whenever a client application is launched and connects to the Cisco ANA server, Cisco ANA automatically checks the client software version, and, if necessary, automatically performs updates.
Network Element Inventory Discovery
Every node managed by Cisco ANA is assigned to an autonomous VNE. The VNE continuously investigates the NE status and configuration in order to reflect it accurately and generate an accurate virtual model of the network.
Cisco ANA provides full control over the information collection process. Different polling intervals are assigned to the various information types, such as status, configuration, and performance counters, which can also be differentiated by device types, groups, and instances. Furthermore, the polling intervals are modifiable in runtime, which allows VNEs to implement adaptive polling, that is, to increase or reduce the polling rates according to the device load or CPU consumption.
Network and Service Monitoring
Effective network management requires accurate, up-to-date network information. Cisco ANA uses Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP) for the initial network discovery and to maintain the real-time, virtual network image.
After discovery, presentation of the network in Cisco ANA includes:
•
•
•
•
Event and Fault Management
Cisco ANA offers extensive fault analysis and management capabilities that ensure quick and accurate fault detection, isolation, and correlation. After a fault is identified, Cisco ANA uses the autodiscovered virtual network model to perform fault inspection and correlation to determine the root cause of the fault and, if applicable, to perform service impact analysis.
Configuration and Activation
Cisco ANA provides an activation framework that can be used for NE configurations and end-to-end service activations. Cisco ANA enables both standalone activation and integration with northbound design and assigns systems to enable integrated flow-through provisioning.
The configuration and activation framework of Cisco ANA is based on Command Builder and the Workflow Engine. Command Builder commands and Workflow Engine workflow sequences can be executed from the Cisco ANA GUI, as well as from northbound systems using the Cisco ANA API.
Security
Cisco ANA implements a two-dimensional security model by combining a role-based security mechanism that is applied on scopes of NEs and user-defined maps. Cisco ANA supports built-in roles, each with predefined security and access control for performing different system functions.
Cisco ANA Reports
Cisco ANA provides a Report Manager that enables you to generate, view, and export reports of the information managed by Cisco ANA. You can save the generated reports in multiple formats, including PDF, CSV, HTML, and XML. In addition to a variety of standard reports for events and inventory, you can customize one of the existing report types as required for your environment by setting report input values for later use. The Report Manager is available from Cisco ANA NetworkVision, Cisco ANA EventVision, and Cisco ANA Manage.
Northbound Integration
Cisco ANA supports multiple concurrent northbound integration sessions through any protocol (standard or proprietary) and information model. The gateway server manages and authenticates all client sessions, as well as the required protocol and information model adaptations for the various clients.
Cisco ANA northbound information modeling is based on an information model derived from TMF-513/608. It is called the Information Model Object (IMO), and is designed to accommodate any technology and network type.
Cisco ANA Configuration and Image Management
The Cisco ANA Configuration and Image Management GUI enables you to detect and track changes that are made to device configurations, and provide rapid, reliable software upgrades to devices.
For device configuration changes, copies of configuration files are stored in a configuration archive, from which you can compare configurations, restore configuration files to devices, and for Cisco IOS devices, synchronize running and startup configuration files.
Cisco IOS and Cisco IOS XR software images are stored in the Cisco ANA image repository. You are alerted when running and startup configurations are no longer synchronized. You can add new images by importing them from Cisco.com or a local file system. Before an image is distributed, the Network Element and Image Management (NEIM) component performs an upgrade analysis to ensure that the network element is compatible with the image. For Cisco IOS XR devices, you can deactivate packages, test changes before committing them, commit changes, and restore packages to previous rollback points.
Device configuration and software image files are stored in the Cisco ANA database in the new anauser_xmp schema.
Device and software image files are stored in the Cisco ANA database in the anauser_xmp schema.
For more information, see the Cisco Active Network Abstraction 3.7.3 Configuration and Image Management User and Administrator Guide.
Cisco ANA Network Service Activation
Cisco ANA Network Service Activation (Cisco ANA NSA) is a Cisco ANA service activation extension for users who want to deploy Carrier Ethernet, IP Radio Access Network (RAN), and Mobile Transport over Pseudowire (MToP) services using a service activation wizard launched from Cisco ANA NetworkVision. Cisco ANA NSA provides:
•
•
–
–
–
For more information, see the Cisco Active Network Abstraction Network Service Activation 1.3 User Guide.
New Features and Enhancements in Cisco ANA 3.7.3
The following topics describe the new features, enhancements, and changes in Cisco ANA 3.7.3:
•
•
•
•
•
•
For information about support added in Cisco ANA 3.7.3 for devices, software, or fault management, see:
•
•
•
•
•
Cisco ANA Software License
Note
For more information about Cisco ANA licenses, see the Cisco Active Network Abstraction 3.7.3 Administrator Guide.
Licensing for Upgrades to Cisco ANA 3.7.3
•
•
Licensing for Gateway High Availability
If you are using gateway high availability, contact your Cisco account representative or send an e-mail to ask-ana-licensing@cisco.com for licensing information and assistance. For more information on licensing for gateway high availability, see the Cisco Active Network Abstraction 3.7.3 Administrator Guide.
Installation and Migration
Cisco ANA 3.7.3 provides the following features related to installation and migration:
•
–
–
–
–
For more information, see the Cisco Active Network Abstraction 3.7.3 Installation Guide.
•
If the user chooses to not update the IVNE drivers after the Cisco ANA 3.7.3 upgrade is complete, they can run the IVNE installer from the Cisco ANA Disk 1 DVD at a later time.
Foundation-Level Enhancements
Cisco ANA 3.7.3 introduces the following foundation-level enhancements:
•
•
For more information, see the Cisco Active Network Abstraction 3.7.3 Administrator Guide.
Cisco ANA 3.7.3 Configuration and Image Management Enhancements
Cisco ANA 3.7.3 Configuration and Image Management provides the following new features:
•
•
•
•
•
•
For more information, see the Cisco Active Network Abstraction 3.7.3 Configuration and Image Management User and Administrator Guide.
Cisco ANA Network Service Activation 1.3 Enhancements
Cisco ANA NSA 1.3 includes the following new features:
•
•
For more information, see the following documents:
•
•
Cisco ANA NetworkVision Enhancements
Cisco ANA 3.7.3 NetworkVision includes the following enhancements:
•
–
–
•
Discovery Enhancements
Beginning with Cisco ANA 3.7.3, Link Aggregation Control Protocol (LACP) is also used as a discovery technique for Ethernet physical links in cases where the ports are associated with an LACP LAG.
The existence of a topological link is deduced as follows:
•
•
Fault Management Enhancements
Cisco ANA 3.7.3 includes the following new information for tickets:
•
•
•
This information is displayed in:
•
–
–
–
•
–
–
Report Manager Enhancements
Cisco ANA 3.7.3 includes a new report named IOS-XR Software Package Summary. For each Cisco IOS XR device included in the report, the report includes the following information:
•
•
•
•
•
•
For more information, see the Cisco Active Network Abstraction 3.7.3 User Guide.
GUI-Related Enhancements
Cisco ANA 3.7.3 NetworkVision includes the following new GUI-related features. Most of these features also exist in Cisco ANA PathTracer.
•
–
–
–
–
•
–
–
–
–
•
–
–
•
–
–
•
–
–
–
Note
–
–
For more information, see the Cisco Active Network Abstraction 3.7.3 User Guide.
Features Changed or Removed in Cisco ANA 3.7.3
Features Changed
The following features have changed in Cisco ANA 3.7.3 NetworkVision:
•
•
•
Features Removed
The Tree layout option for maps is no longer available in Cisco ANA. It has been replaced by the Orthogonal layout option.
For more information, see the Cisco Active Network Abstraction 3.7.3 User Guide.
Documentation Enhancements
Although the following documents have not been updated for Cisco ANA 3.7.3, their content applies to this release:
•
•
•
•
In addition to the features described in New Features and Enhancements in Cisco ANA 3.7.3, the guides in the following subsections have been enhanced for Cisco ANA 3.7.3 as described.
See Related Documentation for a list of all documentation available for Cisco ANA 3.7.3.
Cisco Active Network Abstraction 3.7.3 Installation Guide
The Cisco Active Network Abstraction 3.7.3 Installation Guide includes the following enhancements:
•
•
•
Cisco Active Network Abstraction 3.7.3 Administrator Guide
The Cisco Active Network Abstraction 3.7.3 Administrator Guide includes the following enhancements:
•
•
Cisco Active Network Abstraction 3.7.3 User Guide
The Cisco Active Network Abstraction 3.7.3 User Guide includes the following enhancements:
•
•
Other Changes
Cisco ANA 3.7.3 has resolved a number of open bugs. For details, see Resolved Caveats in Cisco ANA 3.7.3.
New Module, Software, and Technology Support
The following topics describe the new support provided in Cisco ANA 3.7.3 for network elements, modules, software, and topologies:
Note
See the following documents for new device support added to Cisco ANA 3.7.3 Configuration and Image Management and Cisco ANA Network Service Activation 1.3:
•
New Module Support
The following sections identify the new module support in Cisco ANA 3.7.3:
•
•
•
•
•
Cisco 7600 Series—Supported Modules
Cisco ASR 1000 Series—Supported Modules
Cisco ASR 9000 Series—Supported Modules
Cisco CRS Series—Supported Modules
Cisco Nexus 7000 Series—Supported Modules
New Software Version Support
Table 7 identifies the new software versions supported in Cisco ANA 3.7.3.
New Technology Support
Table 8 describes the new technology support in Cisco ANA 3.7.3.
New Alarm, Event, Trap, and Syslog Support
The following topics describe the new service alarms, service events, trap support, and syslog support provided in Cisco ANA 3.7.3:
New System Events
Table 9 describes the system events added in Cisco ANA 3.7.3.
New Syslog Support
The following topics identify the syslog support added in Cisco ANA 3.7.3:
•
•
Cisco IOS XR Syslog Support Added
Table 10 identifies the Cisco IOS XR syslog support added in Cisco ANA 3.7.3.
Table 10 Cisco IOS XR Syslog Support Added in Cisco ANA 3.7.3
HA-REDCON-6-GO_ACTIVE
redundancy role change syslog
Informational
Cisco ASR 9000 Syslog Support Added
Table 11 identifies the Cisco ASR 9000 syslog support added in Cisco ANA 3.7.3.
New Event-Based Polling Support
Cisco ANA 3.7.3 supports event-based polling (also known as reduced polling) in the following devices:
•
•
•
•
•
•
•
•
•
New Independent VNE Driver Support
Cisco ANA 3.7.3 supports independent VNE drivers for the following devices:
•
•
•
•
•
•
•
•
Technology Information Model Object (IMO) Changes
No new technology IMOs were added in this release. However, several attributes were added to the IAtm IMO, which represents a data link circuit switching technology
Important Notes
This section includes the following topics:
•
•
•
•
Installation Notes
This section includes the following topics:
•
•
•
•
•
For installation procedures, see the Cisco Active Network Abstraction 3.7.3 Installation Guide.
Before Installing Cisco ANA 3.7.3
Note the following before installing Cisco ANA 3.7.3:
•
•
•
•
The time set on the clocks of all units in the setup is the same. The maximum difference allowed between the different clocks is 4 minutes.
Note
•
Note
To verify that you have the required Linux version, enter:
# cat /etc/redhat-releaseIn the command output, you should see:
Red Hat Enterprise Linux Server release 5.3 Beta (Tikanga)To verify that all required RPMs are installed, enter the following command as the root user:
rpm -q binutils compat-libstdc++-33-3.2.3 elfutils-libelf elfutils-libelf-devel gcc-4.1.2 gcc-c++-4.1.2 glibc glibc-common glibc-devel glibc-headers ksh libaio libaio-devel libgcc-4.1.2 libstdc++ libstdc++-devel make numactl-devel sysstat-7.0.2 --qf '%{name} version:%{version} arch:%{arch}\n'|sortThe installed RPMs are displayed. Compare the output with the list of RPMs above. If any are missing, install them following the procedures in the Red Hat documentation.
Changes in the Cisco ANA Installation
The Cisco ANA 3.7.3 installation procedure has added the ability to install a new integrated gateway high availability solution that provides High Availability/Disaster Recovery (HA/DR) for the gateway server and database using Red Hat Cluster Suite (for local redundancy) and Oracle Active Data Guard (for geographical redundancy).
For more information, see the Cisco Active Network Abstraction 3.7.3 Installation Guide.
Changes in the Upgrade Process
If you upgrade from Cisco ANA 3.7.2 to Cisco ANA 3.7.3, you are given the option to run the IVNE driver installer to update IVNE drivers. The Cisco ANA 3.7.3 upgrade script presents this option after the upgrade to Cisco ANA 3.7.3 is complete.
If you choose to not update the IVNE drivers after the Cisco ANA 3.7.3 upgrade is complete, you can run the IVNE installer from the Cisco ANA Disk 1 DVD at a later time.
For more information, see the Cisco Active Network Abstraction 3.7.3 Installation Guide.
Before Upgrading to Cisco ANA 3.7.3
For complete information on the changes and requirements for upgrading to Cisco ANA 3.7.3, review the information in the "Upgrading Cisco ANA" chapter in the Cisco Active Network Abstraction 3.7.3 Installation Guide. That chapter identifies the requirements and effects of the upgrade in detail.
Migration Issues
The GUI enhancements in Cisco ANA 3.7.3 can have the following effects if you migrate to Cisco ANA from an earlier release:
•
•
For more information on the Cisco ANA 3.7.3 NetworkVision interface, see the Cisco Active Network Abstraction 3.7.3 User Guide.
Memory Consumption
Before you upgrade to Cisco ANA 3.7.3, we recommend that you check your AVM memory allocations to see if there is a change in memory requirements. Contact your Cisco account representative obtain a copy of the Cisco Active Network Abstraction 3.7.3 Capacity Planning Guide and to perform the necessary calculations.
Backward Compatibility
Refer to the following links for changes in Cisco ANA 3.7.3 that might affect existing integrations:
•
•
Cisco ANA 3.7 Upgrade Limitations
When migrating data to Cisco ANA 3.7 from an earlier version of Cisco ANA, if you specify a database for the event processing scheme that is different than the Cisco ANA database, the migration fails.
To work around this issue:
1.
2.
3.
For more information, see CSCtf98838.
Solaris Services and Components
Cisco ANA uses the Solaris services and components. You must not remove them. For more information, see the Cisco Active Network Abstraction 3.7.3 Installation Guide.
Working with Cisco IOS XR VNEs
This section contains the following topics:
•
Installing the Cisco IOS XR Manageability Package
For VNEs for Cisco IOS XR devices, you must install the Cisco IOS XR Manageability Package on top of the Cisco IOS XR version. In addition, verify that the tty agent is enabled for XML requests. To configure it, enter the following command in Configuration mode:
xml agent ttyCreating the SNMP Community
When creating the SNMP community, configure a new SNMP community string that has SystemOwner privileges.
To do this, log into the device and create a new community read string with SystemOwner privileges, and then direct the Cisco ANA VNE to use the new community. For example:
snmp-server community 1icpub RO SystemOwnersnmp-server community ate9riv RWSDR Support
Secure Domain Router (SDR) is supported as a separate, independent VNE, with its own IP address and login sequence. When adding an SDR to Cisco ANA, it is treated like any other network element; that is, it is added as a new VNE using Cisco ANA Manage. The SDR IP address is attached to the active RP of the SDR (or to its virtual IP, if it exists).
The following sections describe how to set up Cisco XR 12000 series devices and Cisco CRS devices for use with SDR.
For more information about SDR support and either of these devices, see the Cisco Active Network Abstraction 3.7.2 Reference Guide.
For Cisco XR 12000 Series Devices
As a prerequisite for a Cisco XR 12000 Series VNE:
Step 1
Step 2
Step 3
For Cisco CRS Series Devices
As a prerequisite for Cisco CRS VNEs:
Step 1
Step 2
Step 3
Step 4
Device and Software-Specific Limitations
Table 14 describes caveats related to specific devices or versions of software.
Table 14 Device- and Software-Specific Limitations
Cisco 3750ME device
N/A
Prior to Cisco IOS 12.2(52)
In Cisco ANA NetworkVision logical inventory in the LLDP Neighbors Table (Logical Inventory > Link Layer Discovery Protocol), the port description appears in the Local Port ID column instead of the port identifier.
As a result, the LLDP links are not connected. For more information, see CSCtc89665.
Cisco 6500 series router
Supervisor Engine 32 module
Prior to Cisco IOS 12.2
Ports on Supervisor Engine 32 modules are not displayed in Cisco ANA NetworkVision. For more information, see CSCsm23483.
Cisco 6503 router
Cisco Multilayer Switch Feature Card 2A (MSFC2A)
Cisco IOS 12.2(33)SRD2
In Cisco ANA NetworkVision, the Status, Hardware Type, and Hardware Version fields for MSFC2A cards are not populated for Cisco 6503 devices running Cisco IOS version 12.2(33)SRD2. For more information, see CSCta00558.
Cisco 7600 series router
Supervisor Engine 32 module
Prior to Cisco IOS 12.2
Ports on Supervisor Engine 32 modules are not displayed in Cisco ANA NetworkVision. For more information, see CSCsm23483.
Supervisor Engine 720 modules and Route Switch Processor (RSP) cards
N/A
Transceiver Inserted or Removed syslogs are not received in Cisco ANA. As a result, Transceiver Inserted or Removed service alarms are not generated. This issue has been observed for SUP and RSP cards, such as WS-SUP720-BASE or RSP720-3CXL-10GE. For more information, see CSCtj64948.
Cisco ASR 9000 series routers
Card
Cisco IOS XR 4.0.1
After removing a card from a Cisco ASR 9000 device, multiple Card In alarms are observed for the power supply and fan in Cisco ANA.
This situation was observed on a Cisco ASR 9000 device running Cisco IOS XR 4.0.1.
For more information, see CSCtn59607.
Cisco CRS devices
Cisco 1OC768- DPSK/C-O module
Cisco IOS XR 3.6.1 and 3.7.1
In Cisco ANA NetworkVision, the Cisco 1OC768-DPSK/C-O module is displayed as Unknown Module in the Hardware Type field. For more information, see CSCsz81415.
Cisco 8x10GBE or 160C48 module
Prior to the following Cisco IOS XR versions:
•
•
Cisco ANA NetworkVision does not model missing pluggable ports under Cisco 8x10GBE or 160C48 modules in physical inventory.
Instead Cisco ANA NetworkVision displays them as actual ports. For more information, see CSCsz41149.
Cisco CRS 16-slot device
Cisco IOS XR 3.8.2
If you switch off the power supply tray on a shelf for a Cisco CRS 16-slot device running Cisco IOS XR 3.8.2, the power supplies in the shelf are displayed with the status OK in Cisco ANA.
For more information, see CSCtf47898.
Cisco CRS-FCC-SC-22GE module
Prior to Cisco IOS XR 3.9.
Cisco ANA NetworkVision does not display all ports under Cisco CRS-FCC-SC-22GE modules in physical inventory. For more information, see CSCsz16471.
DWDM port
Prior to Cisco IOS XR 3.6.3
In Cisco ANA NetworkVision, DWDM ports appear twice in Cisco CRS-1 devices that use software earlier than Cisco IOS XR version 3.6.3.
This issue was resolved in Cisco IOS XR version 3.6.3, but occurs in earlier versions. For more information, see CSCsz70225.
Cisco CRS device
(cont.)
Gigabit Ethernet port
Prior to the following Cisco IOS XR versions:
•
•
•
•
•
Gigabit Ethernet ports are displayed under RP instead of Mgmt ports in Cisco ANA NetworkVision. For more information, see CSCsz13522.
N/A
Prior to Cisco IOS XR 3.7
The module software version does not appear for Cisco CRS-1 devices that use software earlier than Cisco IOS XR version 3.7.
This issue was resolved in Cisco IOS XR version 3.7 but occurs in earlier versions. For more information, see CSCsk36398.
Cisco GSR devices
Fan
Cisco IOS XR 3.6.3
Fans in Cisco GSR devices running Cisco IOS XR 3.6.3 are not modeled in Cisco ANA NetworkVision. For more information, see CSCta32822.
Interface
Cisco IOS
On Cisco GSR 12000 series devices running Cisco IOS software, TenGigabitEthernet interfaces are identified as GigabitEthernet interfaces. This situation occurs because the MIB populates these interfaces as GigabitEthernet, and Cisco ANA uses the information from the MIB. For more information, see CSCte48873.
N/A
Prior to Cisco IOS XR 3.9
BGP Neighbor Loss VRF service alarms generate root cause tickets instead of correlating to Link Down service alarms. For more information, see CSCtb88143.
N/A
Cisco IOS XR 3.7.1
Cisco GSR devices running Cisco IOS XR software can exhibit flapping ATM bandwidth values in Cisco ANA when a change on a virtual channel occurs. For more information, see CSCta25148.
Pluggable port
Cisco IOS XR 4.0 or 4.0.1
If a pluggable port is removed from a Cisco GSR device running Cisco IOS XR 4.0 or 4.0.1, Cisco ANA displays the port status Out instead of Missing Pluggable Port. For more information, see CSCtl10872.
Submodule
Cisco IOS XR 3.6.3
Subcard status values are incorrect in Cisco ANA for Cisco GSR devices running Cisco IOS XR 3.6.3. For more information, see CSCta15668.
Cisco IOS XR devices:
•
•
•
N/A
Cisco IOS XR 4.0.1
On Cisco IOS XR devices with large configurations, some technologies are not modeled in Cisco ANA even though the device is shown in an Operational state.
This situation occurs for Cisco ASR 9000 series devices running Cisco IOS XR 4.0.1 software.
To work around this issue, set the convergence timeout value to 30 minutes by using the following command:
./runRegTool.sh -gs localhost set 0.0.0.0 site/agentdefaults/da/investigation-progress/user-convergence-timeout-in-milliseconds 1800000
For more information, see CSCtj92761.
Cisco ME 3600X and ME 3800X devices
N/A
Cisco IOS 12.2(52)EY
If you use Cisco ANA Configuration and Image Management to upgrade the software image on a Cisco ME 3600X or ME 3800X device, device utilization might rise to 90% or higher. If this occurs, Cisco ANA might place the device into maintenance mode, causing the device to become unreachable and the image upgrade to time out.
For more information, see the Release Notes for the Cisco ME 3800X and ME 3600X Switches, Cisco IOS Release 12.2(52)EY and caveat CSCti68215.
Cisco MWR 2941 devices
Motherboard and power supply
Prior to Cisco IOS 12.4(20)MR
Values for the motherboard hardware revision and the power supply field replacement unit (FRU) are blank or contain incorrect information. For more information, see CSCta65998.
Cisco Nexus 5000 devices
Power supply module shows description as Unknown
Prior to Cisco NX-OS 4.2(1)N1(1)
The description for power supply modules for Cisco Nexus 5000 series devices are displayed as Unknown in Cisco ANA NetworkVision. for more information, see CSCti69549.
Multiple device families
N/A
Prior to Cisco IOS XR 3.8.x
The total number of MAC address table entries in Cisco ANA might not accurately reflect the number of entries available on the device.
As a result, the following items can be affected:
•
•
•
•
The affected devices are:
•
•
•
For more information, see CSCtd57684.
Cisco SIP-600 or Cisco SIP-800
Prior to Cisco IOS XR 3.9.1
If you enter a hw-module shutdown command to shut down a SIP-800 or SIP-600 (Cisco Carrier Routing System SPA Interface Processor), the status of the card is displayed as UNKNOWN in Cisco ANA.
The affected devices are:
•
•
For more information, see CSCtj49181.
Supported Schemes
Cisco ANA supports two schemes:
•
•
For supported device type and schemes table, see the Cisco Active Network Abstraction 3.7.3 Administrator Guide.
JDK DST Timezone Update Tool for Cisco ANA
Cisco ANA comes with Java Development Kit (JDK) 1.6.0_14. It is possible that the daylight saving time (DST) at your location has changed since JDK 1.6.0_14 was released. If this applies to you, you can use the Sun JDK DST Timezone Update Tool to be current with the latest daylight saving time as published by Sun.
To use the Sun JDK DST Timezone Update Tool:
Step 1
http://java.sun.com/javase/downloads/index.jsp
Step 2
Step 3
a.
b.
c.
d.
java -jar tzupdater.jar -u -vStep 4
Online Help
The online help has been updated for Cisco ANA 3.7.3 and has been tested using the following browsers:
•
•
Limitations and Restrictions
This section includes the following limitations and restrictions:
•
•
•
•
For deployment information and recommendations, such as supported configurations and system sizing, contact your Cisco account representative.
Cisco ANA Configuration and Image Management
The following items pertain to Cisco ANA Configuration and Image Management:
•
–
–
To avoid this situation, we recommend that you do not use the global operation check box with filtered lists. For more information, see CSCtq36813.
•
•
To avoid this error, we recommend that you wait approximately 15 minutes after the Cisco ANA gateway is up before trying to log into Cisco ANA Configuration and Image Management via a browser. For more information, see CSCth85747.
Cisco ANA NetworkVision
The following items pertain to Cisco ANA NetworkVision:
•
–
–
•
The following actions might occur if a routing protocol (such as EIGRP) or other management protocol is enabled on a device on one side of the link and disabled on the device on the other side:
–
–
•
This situation occurs if the static link is created while the dynamic link is connected.
To address this situation, do either of the following:
–
–
•
In Cisco ANA, the physical topology is incorrectly discovered if any of the following configurations exist:
–
–
–
If enough traffic passes through these links, the link in Cisco ANA becomes flickering (repeatedly discovered and then disconnected).
After two cycles of discovery and disconnecting, Cisco ANA sends a system event announcing that the link is probably incorrect.
To address this situation, create a static link in place of the flickering link.
•
Cisco ANA Fault Management
Cisco ANA automatically clears and removes (archives) tickets with more than 150 associated events, and generates a system notification event regarding the actions taken. For more information, see the Cisco Active Network Abstraction 3.7.3 Administrator Guide.
A Tickets Capacity Overflow system alarm is generated when the maximum number of open tickets is exceeded. The alarm severity is defined as Critical. For a definition of an open ticket, see the Cisco Active Network Abstraction 3.7.3 User Guide. To avoid exceeding the maximum number of open tickets, we recommend that you close the tickets on time.
Note
Cisco ANA Workflow Editor Sessions
You can open only a single Cisco ANA workflow session at a time.
ATM Topology Discovery
ATM topology discovery is performed in two phases:
1.
2.
ATM topology discovery is supported on topologies where the ports at either end of the connection are both configured with VCs or VPs. Discovery is not supported on ATM topologies where VPs are configured at one end and VCs are configured at the other end.
BGP Neighbors
•
•
HSRP
For correlation to work, the path through which HSRP signaling passes must be modeled (must exist) in the system.
VLAN Tagged Interface Limitation
When a Layer 3 subinterface is configured on an Ethernet port with a range of VLAN tags as the first or second tag, the following occurs at the device level:
•
•
As a result of the inconsistent behavior in the egress direction, Cisco ANA VNEs do not implement VLAN tagged interface functionality for this direction. If a flow in the egress direction reaches a subinterface with a range of VLAN tags defined, the flow stops.
Open Caveats in Cisco ANA 3.x
The following sections identify and describe caveats that are open against Cisco ANA:
•
•
•
Each of the following subsections contains a table with the following information:
If you have a question about one of these caveats or a caveat that is not included in this document, we recommend that you use Cisco Bug Toolkit. Cisco Bug Toolkit enables you to search for a caveat by identifier or product and version, and can provide additional details about the caveat, such as more information or that the caveat has been fixed.
Significant Caveats Before Using Cisco ANA 3.7.3
We recommend that you read the caveats in Table 15 before using Cisco ANA 3.7.3 so that you understand the possible impact on your environment.
Outstanding Cisco ANA 3.7.3 Caveats that Were Resolved for Earlier Releases of Cisco ANA
When a customer identifies a defect in Cisco ANA, the availability of the software that fixes that defect depends on when the defect was identified during the development process.
At the beginning of a development cycle, defects that are identified by customers against released versions of the product are scheduled for resolution in the current release. In addition, all fixes that were delivered as point patches or service patches to customers are included in the current release.
During the middle of the development cycle, customer-found defects are handled in one of the following ways, depending on the amount of risk associated with fixing the defect:
•
•
At the end the development cycle, customer-found defects identified against released versions of the product are either included in a point patch or service patch, or are scheduled for inclusion in the next release, depending on their severity.
The caveats identified in Table 16 were identified late in the Cisco ANA 3.7.3 development cycle and have been fixed for releases of Cisco ANA earlier than 3.7.3. The fixes for these caveats have been provided to customers as needed and are scheduled for inclusion in the next release.
Open Caveats in Cisco ANA 3.x
Table 17 lists additional caveats, in descending order, that are open against Cisco ANA 3.x.
Table 17 Open Caveats in Cisco ANA 3.x
Incorrect command to enable VNE Staggering mechanism.
VNE staggering mechanism does not work and moves VNEs to partially reachable and unsynchronized state.
Run the below runRegTool command to start the gateway services:
# ./runRegTool.sh -gs gateway-IP set unit-IP avm99/services/initlevel5/vneLoginSupervisor com.sheer.system.os.services.vne.login.VneLoginSupervisorServiceImpl
3.7.3
Web server failed to startup after performing switchover or failover
Web server fails to startup when performing switchover or failover in a disaster recovery (DR) setup.
Restart the web server after performing switchover or failover. First kill the current web server process and then start the web control again.
3.7.3
Upgrade to Cisco ANA 3.7.3 SP1 PP3 or later forces the user to recheck the ENS entries for System and Trap event types
Notifications are not being sent for some event types after upgrading to Cisco ANA 3.7.3 SP1 PP3 or later versions.
This situation occurs due to the new event type IDs assigned to the System event types.
Check the System and Trap event types configured on the ENS entries before and after upgrading to Cisco ANA 3.7.3 SP1 PP3 or later version.
3.7.3 SP1 PP3
Unit becomes unreachable after installation
Unit becomes unreachable, when installing unit/redundant unit that does not have the same home directory as the gateway.
Make sure that the home directory of the unit/redundant unit is the same as the home directory of the gateway.
3.7.3
Recommended Solaris patch update
The Oracle 11g R2 database is built and tested on the Solaris 10 Update 10(u10) operating system. Any version earlier than Solaris 10 u10 causes Java to crash.
Oracle Global Software Support cannot support anything earlier than Solaris 10 u10.
Verify that you have the required Solaris version. If you have any earlier version, you must upgrade to u10.
3.7.3
A patch is required for DR HA setups using Oracle Dataguard
In disaster recovery (DR) high availability (HA) environments, the standby database might stop applying redo. As a result, the standby database does not synchronize with the primary database.
This situation occurs in Cisco ANA HA DR environments that use Oracle Dataguard solution for database DR.
If you use the Embedded Oracle edition 11.2.0.1, you might see the following Oracle internal error in the alert log file:
ORA-00600: internal error code, arguments: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], []Incident details in: /export/home/oracle/diag/rdbms/a nadb_sb/anadb/incident/incdir_11 2337/anadb_pr0d_5316_i112337.trcSlave exiting with ORA-600 exception.As a result of the error, the standby database changes mode from "read only with redo apply" to "read only," and the standby database is no longer synchronized with the primary database.
1.
2.
alter database recover managed standby database using current logfile disconnect from session;3.7.3
Workflow migration does not migrate Template Display Name
If you migrate from Cisco ANA 3.7.3 to 3.7.3.0.1, the Cisco ANA NSA Template Display Name field is not populated after the migration.
Instead, the Template Display Name is populated with the template name, allowing you to search by the Template Name field.
This situation occurs when Cisco ANA NSA workflows exist in the database in Cisco ANA 3.7.3.
None
3.7.3
Workflow search with Contains or Equals fails
Filtering workflows with the Device Name option and the Contains or Equals operator does not produce the expected output:
•
•
•
•
3.7.3
Search does not present "Running" workflows
If you search for a workflow by using the search criterion "State Equals Running," no results are returned.
However, you can successfully search for completed workflows by using the State search criteria of Aborted or Done.
Search for running workflows by using an attribute other than State.
3.7.3
Unit machines become unreachable after initial setup/installation
Occasionally, unit machines enter an unreachable state after initial installation, and the following error appears in the 99.out file on the unit machine:
Unrecognized VM option `-ReduceInitialCardMarks'1.
<machine name="Default">-verbose:g c -XX:-ReduceInitialCardMar ks</machine>to:
<machine name="Default">-verbose:g c</machine>Note
2.
anactl restartIf there are multiple units, changing the file on the gateway makes the change on all units.
3.7.1
Unit install should allow user to choose a network interface
When installing and configuring a unit, Cisco ANA uses the first interface. This can cause an issue when a unit has multiple interfaces.
1.
2.
3.
3.7.3
CE scale: Messages are dripped in service link discovery plugin mailbox
There are drops in Service Link Discovery, causing missing updates to VLAN links.
This situation occurs in large scale deployments (15,000 CE VNEs) under heavy event and client noise.
None
3.7.3
Cannot open Cisco ANA Shell from the default Cisco ANA GUI menu
The Windows shortcut for opening Cisco ANA Shell does not work.
Further Problem Description
Beginning with Cisco ANA 3.7.0, there is no access to the Cisco ANA gateway using Telnet other than from the local machine. Because the Windows shortcut uses Windows Telnet, access to Cisco ANA Shell fails.
Use the SSH client.
3.7.3
Migration: Restore database fails to start gateway
An error message is displayed in the gateway log that the AVM cannot be configured with a heap size of 6 Gb.
Gateway failed to start after 60 seconds. Please check the logs!This situation occurs because, after an upgrade from Cisco ANA 3.7.2 to 3.7.3, the gateway AVM returns to 32-bit mode.
To roll back to Cisco ANA 3.7.2, complete the following steps:
1. Restore the database and the old Cisco ANA configuration files.
After Step 1, the system automatically tries to reboot. This results in the error message.
You can ignore the error message because the system cannot be restarted until both Step 1 and Step 2 are complete. Continue with Step 2.
2. Roll back to Cisco ANA 3.7.2.
None
3.7.3
Missing VPN links on MPLS setup with IPv6 configuration
Cisco ANA does not display all VPNv4 links in an MPLS setup when IPv6 is configured (IPv6 BGP neighbors).
Cisco ANA occasionally does not display all VPNv4 links if the configuration contains IPv6 addresses. However, this situation has not been consistently reproduced.
None
3.7.3
Ticket Property: Correlation Tab export does not include Severity or Alarm ID
Cisco ANA does not include Severity or Alarm ID information if you export ticket correlation data to a CSV file.
This situation occurs if you export the data in the Correlation tab in the Ticket Properties window to a CSV file.
None
3.7.0
Column names in Cisco ANA EventVision differ from Filter dialog box fields
The names that are displayed in Cisco ANA EventVision column are different from the fields that are displayed in the Filter dialog box.
This situation is observed when you apply a filter to a Cisco ANA EventVision table. The field names in the Filter dialog box are not the same as those in the table columns.
None
3.7.0
Power Down scenario results in 2 identical Device Unreachable tickets
In a unit high availability (protection group) situation, you might see duplicate events in the database.
This situation can occur if a connectivity issue exists between the gateway and unit for longer than six minutes.
If a protection group is defined, the gateway detaches itself from the older unit which, since it is still running, might continue to send reachability events to the database.
Enter the following command on the older unit:
anactl stop3.7.2
Line Up/Down syslog message not associated with EFP
Syslogs messages for EFP-related interfaces point to the physical interface instead of the EFP.
This situation occurs when an EFP is configured on an interface and the EFP status changes.
When a syslog is sent on an EFP-related interface to indicate the EFP status change, Cisco ANA attaches the syslog to the physical interface on which the EFP is configured instead of the EFP itself.
None
3.7.3
Missing service links for configurations with LAG and VLAN mappings
A VLAN service link between a port and its neighbor is missing under the following conditions:
•
•
None
3.7.3
Missing expediting for EFP status in Subinterface Down scenario
Expediting does not occur when the EFP status in a subinterface changes.
This situation occurs when an EFP changes to up or down.
None
3.7.2 PP1
EFD of VLAN with MUX-UNI EFP not updated when the port moves to new EFD
In Cisco ANA 3.7.3, MUX-UNI port configuration creates an Ethernet Flow Point and Network VLAN element for the VLAN tagged interface elements in the MUX-UNI.
However, when the port is moved to a new EFD, the Network VLAN is not updated with the new EFD.
This situation occurs when a port with MUX-UNI configuration is moved to a new EFD.
None
3.7.3
Duplicate BGP Link Down Due to Oper generated by Cisco ANA
Two Link Down alarms are created across what looks like a single BGP link.
This situation occurs when two BGP neighbors have both IPv4 and IPv6 links configured.
Clear the duplicate alarm.
3.7.3
Unit free memory decreases over time from 10-12 GB to 500 MB
The overall memory consumed by the Solaris OS is twice the JVM heap size. That is, if the heap maximum size is set to 1 GB, the overall memory that the operating system uses is 2 GB.
This caveat is not related to Cisco ANA functionality or a Cisco ANA memory leak. Cisco ANA performs well and without memory leaks. This caveat was opened because the operating system itself (not the java heap) requires more memory than originally expected.
Add more servers as units if the free memory on the machine is too low.
3.7.2 PP3
High Availability: NTP servers are not synchronized
Cisco ANA gateways are not synchronized in a high availability setup.
This situation can occur if there are two gateways, each with their own clock, and each gateway sets its own clock as the NTP host.
Further Problem Description
If the gateways in a high availability setup are synchronized, the following occur:
•
•
If the gateways in a high availability setup are not synchronized, the following can occur:
•
•
Use a single clock source to synchronize gateways in a high availability setup.
3.7.3
ARP table is not modeled for all contexts in Cisco Nexus 7000 devices
The ARP table is not modeled in Cisco ANA NetworkVision under routing entities for Cisco Nexus 7000 series devices. The default context is configured for ARP but the ARP table is not displayed in Cisco ANA NetworkVision for the default context.
Cisco ANA NetworkVision displays the ARP table correctly for other contexts.
If appropriate for your environment, upgrade to Cisco ANA 3.7.2 VNE Device Package 3 (Cisco-ANA3.7.2-DP3.tar).
Cisco ANA VNE Device Packages can be installed on Cisco ANA 3.7.3 and are available from www.cisco.com.
3.7.2 DP2
Missing association for cefc FRU Removed traps on Cisco ASR 9000 devices
Cefc FRU Removed and cefc FRU Inserted traps are not associated on Cisco ASR9000 devices that contain SFP or XFP modules.
This situation occurs with Cisco ASR9000 devices running Cisco IOS XR version 4.0.1.
Further Problem Description
After removing a XFP-10G-MM-SR module from port TenGigE0/0/CPU0/3, the cefc FRU Removed trap was not associated with the XFP-10G-MM-SR module. Instead, it was associated with the ManagedElement.
None
3.7.3
Cannot change to a previous password after unchecking the Last 5 Passwords check box
In Cisco ANA Manage, if you uncheck The last n passwords cannot be repeated check box, you cannot change the password to an old password.
This situation occurs as follows:
1. In Cisco ANA Manage, create a new user.
3. If you are logged into Cisco ANA NetworkVision, log out and log in again as the new user.
2. In Cisco ANA Manage, uncheck The last n passwords cannot be repeated check box for the user created in Step 1.
4. In Cisco ANA Manage, try to change password to the old password.
Although the option for not repeating a previously used password has been disabled, you cannot change the password to a previously used one.
Change the password to a new password that is not already being used.
3.7.3
Cisco IOS XR Report - Support ModularOS OS version
In Cisco ANA Report Manager, the software version in the IOS-XR Package Summary report is listed as N/A for Cisco CRS devices.
This situation applies to Cisco CRS devices running Cisco IOS XR versions 3.7.1[00] and 3.7.2.
None
3.7.3
Real EFP is not created for subinterface on switchport (MUX-UNI)
In MUX-UNI configurations, attachment circuits are missing on pseudowire edges and, as a result, the EVCs are not merged.
This situation occurs when the pseudowire local interface is a subinterface on a switch port (MUX-UNI).
None
3.7.3
Missing physical link when LLDP is configured
A physical link is missing from Cisco ANA NetworkVision maps when LLDP is configured.
This situation occurs when the following conditions exist:
•
•
If there are other means by which the link can be discovered, disable LLDP on these ports.
3.7.3
File transfer of Detailed Traps Report is very slow for PDF files
In Cisco ANA Report Manager, if you generate a Detailed Traps Report and choose to save it as PDF, the report can contain thousands of pages and take a long time to save.
Save the report in Excel format.
3.7.3
When switching over in H/A, VNEs become stuck in Maintenance mode
In disaster recovery configurations only, VNEs become stuck in Maintenance mode when switching over to the standby gateway.
This situation occurs under the following conditions:
•
•
•
This situation does not occur when fully cloned Cisco ANA units (VNEs) exist in each geographic zone.
Restart the entire setup if this situation occurs.
3.7.3
Reconciled cross-connects cannot be deleted from Cisco ANA NetworkVision
Reconciled cross-connects cannot be deleted as expected in Cisco ANA NetworkVision.
This situation occurs in the following scenario:
1. Delete a cross-connect from a device.
In response, Cisco ANA NetworkVision displays the cross-connect with a reconciliation icon.
2. Right-click the cross-connect that displays the reconciliation icon.
The Delete option is grayed out instead of being available for selection.
This situation occurs when the deleteReconciled flag is set to false.
Delete the cross-connect via the BQL interface.
For example:
<?xml version="1.0" encoding="UTF-8"?><command name="Delete"><param name="oids"><value>{[EfpCrossConn ect(Id=914)]}</value></param></command>3.7.3
VSI presentation in inventory is not updated with pseudowires
In Cisco ANA NetworkVision inventory, VSIs do not reflect the pseudowires connected to them.
If you add an interface VLAN with a cross-connect to a VSI configured with pseudowires, the VSI status changes to Up, but the pseudowires configured under the VSI are not modeled.
If you remove an interface VLAN with a cross-connect to a VSI configured with pseudowires, the VSI status changes to Down, but the pseudowires configured under the VSI are not removed.
Restart the VNE.
3.7.3
Add TE-Tunnel Rerouted or Reoptimized syslog and trap flow
Traps and syslogs for the TE-Tunnel Reroute and TE-Tunnel Reoptimized events do not correlate to the root cause link failure event.
This situation occurs when the Traffic Engineering tunnel reroute interface changes from Up to Down.
If appropriate for your environment, upgrade to the Cisco ANA VNE Drivers April 2011 Device Package (available on www.cisco.com).
3.7.2
Missing ticket for Layer 2 tunnel
When Layer 2 tunnel changes occur, such as when the tunnel status changes to Up or Down, Layer 2 Tunnel Up or Layer 2 Tunnel Down tickets are not issued.
None
3.7.3
Some multilink interfaces are missing under BFD in Cisco ANA
Cisco ANA does not display all multilink interfaces that are configured under BFD on Cisco GSR devices running Cisco IOS XR software.
None
3.7.2
Some properties in VRF route tables are not modeled properly
In Cisco ANA NetworkVision, the Outer Label and Bottom Out Label fields in the VRF route table are not modeled for Cisco 7200 devices.
This situation has been seen when the destination interface shows a value in the Next Hop field instead of the BGP Next Hop field.
None
3.7.3
IP interface link is not modeled for Port Channels on Cisco Nexus 7000 series devices
In Cisco ANA NetworkVision, if you configure an IP interface link for a Cisco Nexus 7000 series device, that information is not displayed in the Port-channel table.
Further Problem Description
Some versions of Cisco Nexus software do not support IP address configuration on an interface or VLAN. If Cisco Nexus software supports an IP address configuration on a particular interface or VLAN, the same interface should be displayed as a Port-channel.
None
3.7.3
Service report - Using uppercase in BQL returns incorrect data
Network service reports return no data if you use BQL to generate the report and include parameters with uppercase letters.
Use only lowercase letters for parameter values when generating reports with BQL.
3.7.2
ES20 Card In does not clear cefc Module Oper Status Down trap
In Cisco ANA, if you reinsert an ES20 card into the router, the cefc Module Oper Status Down trap that is correlated to the Card Out ticket is not cleared.
This situation occurs for ES20 cards in Cisco 7600 series devices.
None
3.7.2 DP2
CPU Usage history data is not updated in Cisco ANA NetworkVision
The CPU Usage history graph in Cisco ANA NetworkVision is not updated with the latest data from the device.
None
3.7.2
Duplicate Link Down on Unreachable tickets in card down scenario
When shutting down an SPA-8XOC12-POS shared port adapter on a Cisco CRS-1 device, the following occur:
•
•
None
3.7.3
Cisco GSR XR EVNE: Ethernet link aggregation not changed from Manual to LACP
If you use the Reduced Polling mechanism for Cisco GSR devices running Cisco IOS XR software, mode changes from Manual to LACP are not displayed in Cisco ANA NetworkVision logical inventory in Ethernet Link Aggregation.
Use the normal polling mechanism.
3.7.2 DP2
AVM 11 stops after continuous Find EVC by Name operations
AVM 11 can require a restart after a number of continuous Find EVC by Name operations in a large scale environment.
This situation occurs under the following conditions:
1.
2.
3.
Do either of the following:
•
•
3.7.3
Search Business Elements times out in a scale setup
In Cisco ANA NetworkVision, if you search for unassociated bridges to add to a map in a large scale environment, the search operation times out.
This situation occurs under the following conditions:
1.
2.
The search operation times out without notifying the user.
Enter more granular search criteria.
3.7.3
MAC address not modified in GUI for Ether bundle on Cisco IOS XR 12000
If the MAC address of an existing Bundle Ether interface is modified on a Cisco IOS XR 12000 series device, the updated MAC address is not reflected in the Cisco ANA GUI.
This situation occurs for Cisco IOS XR devices with MAC addresses that are modified on the device.
However, the information is modeled correctly for newly created Bundle Ether interfaces.
None
3.7.2 DP1
Wrong file modeling in Cisco ACE 4701
While activating an image that was distributed previously by using a Cisco ANA Configuration and Image Management script, the job fails and states that the activation was unsuccessful because the VNE script prefixed additional characters to the image name before activation.
This situation occurs when activating an image on a Cisco ACE 4701 device by using Cisco ANA Configuration and Image Management.
None
3.7.2 PP1
Gateway CPU consumption reaches 100% during Config backup of 10,000 VNEs
Cisco ANA gateway CPU consumption can run high during the configuration backup of 10,000 devices.
This situation occurs only when backing up the configurations of 10,000 devices.
Back up device configurations in smaller groups.
3.7.3
Cisco ANA support for 64-bit SNMP counters for interfaces above 20 Mb/s
Cisco ANA models incorrect port counter values for interfaces with speeds greater than 20 Mb/s. This impacts Cisco ANA PathTracer, port utilization graphs, and topology discovery.
This situation exists for both Cisco IOS and Cisco IOS XR in Cisco ANA.
None
3.7.0
Cisco IOS XR devices exhibit delay for configuration changes
Cisco ANA Configuration and Image Management exhibits delays for configuration changes while the ConfigArchive script runs in Cisco ANA.
This situation occurs for Cisco IOS XR devices with configuration changes while the ConfigArchive script runs.
None
3.7.3
Initial Config Syncup fails to back up some devices
The initial Config Syncup fails to back up some devices while the Cisco ANA Configuration and Image Management ConfigArchive script is running in Cisco ANA.
This situation occurs when the ConfigFetch BQL script is running in Cisco ANA.
None
3.7.3
V1 traps are not displayed in Cisco ANA NetworkVision if varbind list is empty
SNMP v1 traps are not displayed in Cisco ANA NetworkVision or Cisco ANA EventVision of the varbind list is empty.
This situation occurs for traps with no varbinds, such as the following:
•
•
•
•
•
None
3.7.0
Dashboard indicates wrong number of config changes
In Cisco ANA Configuration and Image Management, the number of configuration changes displayed is different than the actual number of changes made on the device.
This situation occurs if you enter configuration mode on a device, and then exit without making a configuration change.
Avoid entering configuration mode on managed devices if no changes are to be made.
3.7.3
Port with VLAN mapping port neighbor does not have EFD
In Cisco ANA NetworkVision, EFDs are not created for ports with neighbor ports that have VLAN mapping configurations.
This situation occurs in setups that contain two connected ports, and one of the ports has a VLAN mapping configuration.
Further Problem Description
The missing EFD should have only one port, which is the neighbor without a VLAN mapping configuration.
None
3.7.3
Pure IPv6 interface does not connect to a cloud
A cloud does not connect to a port if you create a static link on a port that is configured with an IPv6 address and that resides on a device that uses IPv6 addresses.
None
3.7.3
VRF GUI throws cast error on product for Cisco GSR with Cisco IOS XR
In Cisco ANA NetworkVision, if you click a VRF in a Cisco GSR device running Cisco IOS XR modeled with the product scheme, it results in a Class Cast exception.
This situation occurs for Cisco GSR devices running Cisco IOS XR software and modeled with the product scheme.
Further Problem Description
The VRF feature is not supported in the product scheme.
None
3.7.2
Restarting AVM 35 does not load the Vlansnapshot plugin
AVM 35 fails to restart if AVM 11 is up and issues the following exception in the AVM 35 log:
AgentBase.boot - Unable to set unicast address com.sheer.system.transport.err.I llegalUnicastAddressException: the address 700000230a383ad5 is in use at com.sheer.system.transport.drive r.Driver.setUnicastAddress(Drive r.java:581)at com.sheer.system.transport.drive r.Mailbox.setUnicastAddress(Mail box.java:783)at com.sheer.system.agentshell.Agen tBase.boot(AgentBase.java:108)at com.sheer.system.os.services.sch eduler.SchedulerImpl.addAgent0(S chedulerImpl.java:260)at com.sheer.system.os.services.sch eduler.SchedulerImpl.addAgent(Sc hedulerImpl.java:206)at com.sheer.system.os.services.bas e.MessageDrivenService.init(Mess ageDrivenService.java:99)at com.sheer.metromission.pluginfw. PluginManagerImpl.init(PluginMan agerImpl.java:92)at com.sheer.system.os.AVM.addServi ce(AVM.java:558)Restart AVM 35.
3.7.3
(cont.)
Restarting AVM 35 does not load the Vlansnapshot plugin (cont.)
(cont.)
(cont.)
Cisco ANA NSA: Attach Bandwidth Profile script fails-Cisco ME3800
In Cisco ANA NSA, if you specify the wrong bandwidth when using the Attach Bandwidth Profile script, the script runs successfully even though it should fail.
Further Problem Description
The script runs successfully even though the following error is displayed:
User Remark: FAILURE-- The policy map name 70000000000 does not existUser Remark: FAILURE-- The script ---add_policy_map_to_service_ins tance--- failedNone
1.3
Cannot change to Cisco ANA authentication if LDAP URL field is empty
If you are in LDAP authentication and the LDAP URLs field is empty, the following occur:
•
•
Enter LDAP URLs in the LDAP URLs field.
3.7.3
SCP backup failure caused by authorization
SCP backup failure caused by authorization.
When an SCP backup is run on a Cisco 7600 device, the SCP backup fails due to authorization.
Change the authorization to the user on the device.
3.7.3
BFD and BGP events are not correlated to Bundle Interface Up/Down tickets
If an Ethernet bundle is configured on an interface, and the Ethernet bundle interface status changes to Up or Down, the resulting BFD and BGP traps and syslogs are not correlated to the following tickets:
•
•
None
3.7.2 PP2
Cisco ANA NSA activation scripts fail with NMS-in-a-box setup
If you use Cisco ANA NSA to activate a service via the VNE in a unit, an error is displayed and the activation fails.
This situation occurs when Cisco ANA NSA is installed in the Cisco ANA gateway and the unit is not restarted.
Restart units as needed after installing Cisco ANA in the gateway.
1.1
Removing many EVCs from a map takes longer than with Cisco ANA 3.7.2
Removing or adding a large number of EVCs to a map takes approximately one minute.
Large EVCs, composed of approximately 3,600 elements, are discovered when there are multiplex EVCs.
None
3.7.3
Old DB files are not removed if DB is down during Embedded DB install
Reinstalling the embedded database fails because it tries to create datafiles and redologs that already exist from the previous installation.
This situation occurs because redologs and datafiles that were created on a separate disk or mount point (that is, not under the Oracle home directory) are not removed while removing the previous embedded database installation.
Manually remove datafiles and redologs of previous installations that are located on separate disks or mount points before starting the embedded database installation.
3.7.3
Moving VNE to maintenance generates Device Partially Reachable ticket
If a VNE is manually moved to the maintenance state, a Device Partially Reachable ticket is generated.
This situation applies to all VNE types.
Clear the ticket manually.
3.7.3
Cisco ANA NSA cannot add activations to Cisco ME3800/ME3600 ports that do not contain SFPs
Ports on Cisco ME3800 and ME3600 devices can be configured with Cisco ANA NSA only when the ports contain small form-factor pluggable (SFP) modules.
None
1.1
High Availability: Problem with multicast address
If you enter a multicast address in a high availability environment, the address is not validated.
If this address is not configured correctly, the cluster will have communication problems that can cause the cluster to malfunction or shut down the cluster service.
1. Enter a valid multicast address.
2. After configuring the multicast address, edit /etc/cluster/cluster.conf with the correct address directly or via the GUI interface.
3. Restart the cluster in either of the following ways:
•
a. For each node, enter service rgmanager stop and service cman stop.
b. For each node, enter service cman start and service rgmanager start
•
3.7.3
Browser does not respond when using Tab key in Configuration Viewer
In Cisco ANA Configuration and Image Management, if you use the Tab key in Configuration Viewer with a large configuration, the window does not respond for few seconds.
This situation occurs only when using the Mozilla Firefox browser while viewing large configurations.
Do either of the following:
•
•
3.7.3
Cannot copy from Configuration Viewer with Microsoft Internet Explorer
In Cisco ANA Configuration and Image Management, in the Configuration Viewer dialog box, configuration lines cannot be copied to the clipboard by using the Ctrl-C keyboard shortcut.
This situation occurs only when using Microsoft Internet Explorer as the browser.
Use a supported version of the Mozilla FireFox browser instead.
3.7.3
GRE Tunnel Down causes the GRE tunnel to disappear
A GRE Tunnel Down event causes the GRE tunnel to disappear from a Cisco ANA NetworkVision map.
This situation occurs if you log into the device and bring one side of the tunnel down with the no tunnel source loopback command.
After few minutes, the GRE tunnel link disappears between the VNEs in the map.
Further Problem Description
If you bring the link up again, the GRE tunnel link reappears, but with a Major severity due to the uncleared ticket.
None
3.7.3
Opening ticket properties with a large number of correlated events times out
If you open a ticket with a large number of events:
•
•
The Get command depends on the database and gateway load, and can take longer when many events are correlated to a ticket.
Increase the timeout value.
For assistance, contact Cisco Technical Support.
3.7.2
Separate entries for subinterfaces with VLAN encapsulation in Cisco ANA NV
VLANs and associated subinterfaces are displayed separately in the Subinterfaces table in Cisco ANA NetworkVision.
For every subinterface created, there is a IP address associated with it and a VLAN encapsulation associated with it. There should be one entry per subinterface with both of these details.
None
3.7.3
Cannot set AVM35 memory higher than 3.5 Gb via Cisco ANA Manage
In Cisco ANA Manage, if you attempt to update AVM 35 memory to a value higher than 3.5 Gb, an error is issued.
This situation occurs whether updating AVM 35 memory using Cisco ANA Manage or BQL.
1. Change the value in the registry by entering the following command on the gateway:
runRegTool.sh -gs 127.0.0.1 set unit-or-GW-IP avm99/services/bsm/avm35/ maxmem memory-sizeFor example, to change the AVM memory on the gateway to 4000 MB, you would enter:
runRegTool.sh -gs 127.0.0.1 set 127.0.0.1 avm99/services/bsm/avm35/ maxmem 40002. Restart the gateway and relevant unit.
3.7.3
ana-conf asks twice for remote Oracle machine information
The ana-conf script asks you to enter the following information twice if you install Cisco ANA 3.7.2 with a remote Oracle system:
•
•
•
•
•
•
•
None
3.7.2
Trap forwarder does not remove managed device from source selection
When defining a new Event Notification Service (ENS), a device added to the Selected Devices list cannot be removed.
This situation occurs when you add a device to the Selected Devices list and then try to remove that device.
Do either of the following:
•
•
3.7.2
IP interface for IPv6 is not modeled if IPv4 is also configured
IP interfaces that have both IPv4 and IPv6 addresses appear only once in the IP Interfaces table under Routing Entity. That single entry contains only the IPv4 address.
This situation occurs for interfaces configured with both IPv4 and IPv6 addresses.
None
3.7.3
emdbctl -restore script does not accept environmental variables as input
When prompted to enter the location of the Cisco ANA backup directory, if you enter a directory that begins with $ANAHOME or tilde (~), the script indicates that the path is invalid and asks for a valid path.
Enter a fully qualified path without environmental variables or tilde.
3.7.3
Bundle location on Frame Relay cloud port is inconsistent
The value of the Bundle Location property on the same E1 port on a Frame Relay cloud might change each time the cloud is loaded.
This situation can occur if you load a Frame Relay cloud and connect it to multiple E1 ports on two different gateways.
Further Problem Description
If you load the same Frame Relay cloud setup on two different gateways, the value of the Bundle Location property on the E1 port on the cloud might be different for the two gateways.
None
3.7.3
Admin and Oper status are displayed as out of bound on cloud E1 ports
The Admin status and Oper status of E1 ports on Frame Relay clouds display the value -1.
This situation occurs if you load a Frame Relay cloud and connect it to E1 ports.
After loading the Frame Relay cloud and connecting it to E1 ports, the Admin and Oper statuses of the E1 ports on the cloud are -1 (out of bounds) whereas the same E1 ports on the VNE have Admin and Oper statuses of Up.
None
3.7.3
emdbctl -restore command fails
If you use an invalid location when backing up files, the following occur:
•
•
As a result, Cisco ANA cannot start.
Confirm that the backup location is valid when entering the emdbctl -restore command.
3.7.3
Ethernet flow point is not generated for subinterface under VLAN interface
Ethernet flow points are not generated for subinterfaces that are configured on a VLAN interface.
This situation occurs if you load a VNE which models a device with subinterfaces on a VLAN interface.
None
3.7.1
If RMAN issues an error, Cisco ANA generates a Backup Failed event
If you manually delete archive files, the backup procedure issues a system event stating that the backup failed even though it completed successfully.
You can safely ignore the system event in this instance because the backup completes successfully, even if warning messages are issued.
None
3.7.2
Local switching entity is not modeled in Cisco ANA NetworkVision
Local switching entities are not modeled in Cisco ANA NetworkVision logical inventory.
This situation occurs with Cisco IOS version 12.2(18) SXF11 because the output for the telnet command does not provide segment status.
None
3.7.2 PP1
Cisco GSR with Cisco IOS XR: Average CPU utilization is high
The average CPU utilization of Cisco GSR devices running Cisco IOS XR software is high.
This situation occurs when the Cisco GSR device is running Cisco IOS XR version 4.0 and configured with high profiles of MPLS.
Further Problem Description
In this situation, the CPU utilization on the Cisco GSR device with Cisco IOS XR reaches maximum of 100% and an average of 82%.
None
3.7.3
Cisco ANA continues polling deleted context causing higher CPU util.
Cisco ANA continues to poll a context even though the context has been removed from a device.
This situation has been seen on Cisco Nexus 7000 devices.
Restart the VNE.
3.7.3
Filter does not work in the All tab in Cisco ANA EventVision
You cannot filter the contents in the All tab in Cisco ANA EventVision.
This situation applies only to the All tab, which displays a collection of all object types.
Filter objects using any of the other tabs in Cisco ANA EventVision.
3.7.2
Ethernet MAC links are not discovered when VNEs are in different units
Physical links are not displayed in maps under the following conditions:
•
•
Load the two VNEs on the same Cisco ANA unit.
3.7.3
Link severity color and ticket in Link Properties window are not cleared
Cleared Link Down tickets are not updated in the Cisco ANA NetworkVision Link Properties window.
In Cisco ANA NetworkVision, if you double-click a link with a Link Down ticket and clear the Link Down ticket, the Cisco ANA NetworkVision map is updated with the relevant changes in the ticket panel and the link is removed from the map as expected. However, the Link Properties window retains the ticket in the ticket panel and the link severity color is not updated.
Close and reopen the Link Properties window.
3.7.3
In a local installation, embedded database installation files are not validated
During a Cisco ANA 3.7.2 installation on a local machine, the conf procedure requests the location of the embedded database files. The files in the embedded database directory are not validated for the operating system. That is, embedded database files for Linux systems can be installed on Solaris systems, and vice versa.
This situation occurs because, in a local installation, the installation procedure uses the IP address instead of localhost. As a result, the code to validate the type of system is not invoked.
Ensure that the Solaris-specific database files are copied for installation on a Solaris system and that Linux-specific database files are copied for installation on a Linux system.
3.7.2
Cisco ANA NetworkVision issues an Insufficient Memory error and closes in large scale setup
Cisco ANA NetworkVision issues an Insufficient Memory error and closes under the following conditions:
•
•
Close and reopen Cisco ANA NetworkVision.
3.7.2
Aggregation in service VLAN is not updated correctly after change
Service configurations are not updated if you manually create an aggregation inside the service.
This situation occurs when the following steps occur:
1.
2.
3.
In response, the switching entity and Ethernet flow point edge are updated in the network VLAN, but not in the aggregation.
Add the VLAN to a new map, and avoid aggregations as the services are read-only views and are updated by the discovery mechanism.
3.7.3
Null Pointer Exception in GUI when running specific MAC path trace
When running a specific MAC-based path trace, an error is displayed with a null pointer exception and the path trace result is not displayed.
This situation occurs only for MAC-based path traces in a specific scenario.
Further Problem Description
This problem occurs only when running this specific path trace; other path traces work as expected.
None
3.7.3
ATM VC Table Encapsulation not created after migrating from Cisco ANA 3.6.5 to Cisco ANA 3.7.2
After migrating from Cisco ANA 3.6.5 to Cisco ANA 3.7.2, the ATM VC table association for SHDSL ports is not created. Specifically, the Show VC Table button is not enabled for the port in physical inventory.
None
3.7.2
FRR Unprotected trap not correlated to Link Down alarm
The FRR Unprotected trap is not correlated to the Link Down alarm for Cisco IOS XR devices.
If a Cisco ASR 9000 series device running Cisco IOS XR software generates n FRR Unprotected trap along with a Link Down alarm, the trap is not correlated to the Link Down alarm and is displayed in as a trap in Cisco ANA EventVision.
None
3.7.2
After restart, a redundant Link Down ticket is created with the wrong source
After Cisco ANA restarts, a redundant Link Down ticket is created with a source that contains only one side of the link instead of both sides.
This situation occurs in the following scenario.
1. Perform Link Down.
A ticket is issued correctly with both sides of the link identified.
2. Restart Cisco ANA.
After Cisco ANA restarts, a new Link Down ticket is issued even though the previous ticket is still active. The new ticket contains only one side of the link instead of both sides.
This situation is not always reproducible.
None
3.7.2
Polling interval changes for CPU usage command for Cisco ASR 1000 and Cisco ACE 4710 devices
The CPU usage command polls Cisco ASR 1000 series and Cisco ACE 4710 devices using the status interval.
Use the Cisco ANA Registry Editor to change the CPU usage interval from the status interval to 30000.
3.7.2
VCB export does not include the event definition
System-defined event definition properties that are updated by using the vcb event modify command are not included in the export command list.
If you update system-defined event definition properties like auto-clear or ticketable by using the vcb event modify command, and then run the vcb sitechanges export command, the changes made in site.xml are not included in the list of commands that is to be exported.
1. Open site.xml(from $ANAHOME/Main/registry directory).
2. Locate the event definitions under the key send-alarm-msg-util/types.
These event definitions are not included in the export list.
3. Manually reconstruct the vcb event modify command by going through the xml file for event.
3.7.2
Partially reachable tickets are not cleared
In some cases, Partially Reachable tickets are not cleared.
This situation occurs only when the reachability issue spans multiple devices.
Manually clear the operation on the tickets that remain open.
3.7.2
OSPF-5-ADJCHG Up Status syslog does not expedite BFD session command for Cisco 76xx
The OSPF-5-ADJCHG Up Status syslog does not expedite the BFD session.
This situation occurs as follows:
•
•
•
None
3.7.1 PP1
Modeling issue during Card Down scenario on Cisco ASR 9000 series device
A pluggable port modeling issue occurs when a card is shut down.
Instead of changing the status to Out when a card is powered down, pluggable ports display the status Disabled and change the text that is displayed.
This situation occurs when the card is powered down by using the following command:
hw-module shutdown location a/b/cNone
3.7.2
Not all bridges displayed on interface when port configured in trunk mode
If a port is configured for Trunk mode, existing bridges are not listed in the corresponding Subinterfaces tab in Cisco ANA NetworkVision physical inventory.
This symptom has been observed on Cisco 7600 series devices running with the Reduced Polling option selected.
Restart the VNE.
3.7.2
Moving AVMs operation fails; not all AVMs are moved between units
If you move AVMs from one unit to another, some AVMs might not move. Those that fail to move display the state Down.
Move the AVMs again.
3.7.2
VNE flapping due to time synchronization issue
If Cisco ANA is installed in a VMware environment, the VNEs can enter a flapping state with their status changing every 15 minutes.
This situation occurs because both VMware ESX and Cisco ANA attempt to synchronize the system clock.
Further Problem Description
All Cisco ANA units (both virtualized and nonvirtualized) are synchronized on a single NTP server located on the Cisco ANA gateway.
If you have a VMware ESX environment, configure VMware ESX so that it does not adjust the time on its virtual instances.
To synchronize your Cisco ANA machines yourself:
1. Manually remove the NTP configuration from each Cisco ANA machine.
2. Configure all Cisco ANA machines for synchronization with your organizational NTP.
Make sure only one time synchronization service is in effect on the Cisco ANA unit.
3.7.2
Memory leak in AVM 11 after unit clock jump
If you move AVMs from one unit to another, some AVMs might not move. The AVMs that fail to move display the state Down.
Move the remaining AVMs again while they are down.
3.7.2
Network license cannot acquire more than 10K licenses per group
In Cisco ANA 3.7.2, the license framework is limited to a maximum of 10,000 devices in the same group, due to a licensing management limitation.
If Cisco ANA is deployed on a setup that contains more than 10,000 devices in the same RTM group, the network license service can acquire only 9,999 licenses for this group. All other devices result in a violation event that is displayed in Cisco ANA EventVision and the Cisco ANA Manage License report.
None
3.7.2
Solaris unit installation fails
Preinstallation validation stops on the swap file check for Sun Solaris OS.
This situation occurs when the prtdiag command attempts to obtain the RAM size.
1. Restart the Solaris picl service by entering the following commands as root user:
svcadm disable piclsvcadm enable picl2. Install Cisco ANA again.
3.7.2
Table Filter: Device list table does not reapply filter on data change
A filtered table displays elements that do not match the filter.
If you filter a table and then modify one of the entries in the table so that the entry no longer meets the filter criteria, the entry continues to be displayed in the table.
Remove the filter and reapply it.
3.7.2
AVM stuck in Shutting Down state for two minutes
If you create eight AVMs with ten VNEs each and move all of the AVMs to a different unit, some of the AVMs will stay in Shutting Down state and do not move to the other unit.
If more than one minute passes after the AVM reaches the Down state and the AVM is still displayed on the source unit, rerun the move operation.
3.7.2
Cisco ASR 9000 series power supply redundancy state and configured value are None
The redundancy status of a Cisco ASR 9000 series power supply is not displayed correctly in Cisco ANA NetworkVision.
This situation occurs whether the device has one or two power supplies.
None
3.7.2
Fix upgrade.pl warning for uninitialized value
While upgrading to Cisco ANA 3.7.2 and using the upgrade.pl script, the following message is displayed:
uninitialized value in pattern match (m//) at ./upgrade.plThis message is a perl warning and can safely be ignored.
None
3.7.2
Available storage value is incorrect for Cisco ASR 1000 series devices
Occasionally, Cisco ANA Configuration and Image Management displays an incorrect value for the available storage for Cisco ASR 1000 series devices.
Restart the corresponding VNE.
3.7.2
Deadlock in AVM 11 after stopping the license server
A deadlock can occur in AVM 11 after stopping the license server.
None
3.7.2
VSI status and VSI Down ticket are not updated after VSI returns to Up status
Occasionally, Cisco ANA does not clear the VSI Admin Down ticket when it should.
This situation can occur if you perform the following steps:
1. Remove the interface VLAN and wait for the VSI Admin Down ticket to be generated.
2. Restore the configuration.
The VSI status returns to Up on the device, but is not cleared in Cisco ANA.
Clear and remove the ticket.
3.7.2
Incorrect behavior for backup directory when running restore
If you enter the restore.pl command with an invalid directory, Cisco ANA fails to start, as it removed the entire registry.
If you enter an invalid location (such as /export/home/ana37/backup) for the backup directory when you enter the restore.pl command, the script executes and removes the registry without providing a backup .jar.
To extract the registry.jar and recreate the missing registry, rerun restore.pl with a valid backup directory. The default location is $ANAHOME/backup/date- time.
3.7.2
Event handling issues occur 25 minutes after system cold restart
The following can occur after starting or restarting a large scale setup with tens of thousands of VNEs:
•
•
Also, events are not persisted if there are many devices, and it takes a long time for the VNEs to load.
ENS notifications are dropped regardless of the number of devices.
The symptoms disappear after the ManagedElementSnapshotPlugin component in the gateway is up and holds all network element information.
In a large scale setup, loading all network element information can require up to 30 minutes.
None
3.7.2
Yes or no questions during the embedded database installation accept incorrect input
The Cisco ANA installation procedure for the embedded database contains inconsistent prompts for Yes or No questions.
None
3.7.2
PE-CE BGP Neighbor Link Down VRF alarm is not always generated
If a PE-CE BGP neighbor peering exists, administratively shutting down the BGP neighbor does not always result in a BGP Link Down VRF alarm being generated.
None
3.7.2
Embedded database: Path for destination cannot contain underscore (_) or dash (-)
The Cisco ANA installation with the embedded database is unsuccessful if you enter a destination path for the database that contains an underscore (_) or dash (-).
Enter destinations that do not contain underscores or dashes.
3.7.2
Layer 2 tunnel ticket is not cleared after bringing the AVM up while the VNE is down
Layer 2 Tunnel Down ticket might not be cleared if the following sequence of steps occurs:
1. Generate a Layer 2 Tunnel Down ticket.
2. Stop the AVM.
3. Correct the problem in the device.
4. Start the AVM.
None
3.7.2
Some 10GigabitEthernet port location information is marked as Unknown
For 10GigabitEthernet ports only in Cisco 7600 devices, the following fields in Cisco ANA NetworkVision physical inventory display the value Unknown:
•
•
•
This situation occurs only for 10GigabitEthernet ports in Cisco 7600 devices.
None
3.7.0
Discovery protocol disappears from Cisco ANA NetworkVision physical inventory after a change
Cisco Discovery Protocol (CDP) properties are removed from the Cisco ANA NetworkVision GUI and DC debugger.
This situation occurs when the configuration of an interface is changed from switchport to no switchport or vice versa.
None
3.7.2
Migration: anactl start halts after upgrade step fails
When upgrading to Cisco ANA 3.7.2, the anactl start command stops after an upgrade step fails.
Restart the upgrade process.
3.7.2
LAG ticket is not cleared after bringing it up while the VNE is down
A LAG Link Down due to Admin Down ticket appears if the following sequence of steps occurs:
1. Shut down a link aggregation group (LAG) and wait until the LAG Link Down due to Admin Down ticket appears.
2. Stop the VNE the LAG is configured on.
The LAG Link Down ticket disappears from the GUI.
3. While the VNE is down, bring the port channel up.
4. Start the VNE.
Clear and remove the LAG Link Down due to Admin Down ticket.
3.7.2
BGP Link Down ticket is not cleared if it is brought up while the VNE is down
The BGP Link Down due to Admin ticket remains active after it is cleared.
This situation occurs if the AVM or VNE is shut down and, during that shutdown, the BGP Link Down condition is cleared on the device. After the VNE is brought back up, the BGP Link Down ticket is displayed as active.
Manually clear the alarm.
3.7.2
Layer 2 tunnel down alarm is not generated if a neighbor or cross-connect is removed
A Layer 2 Tunnel Down alarm is not generated if a neighbor or cross-connect is removed.
This situation occurs intermittently when a Layer 2 tunnel endpoint is deleted using the router CLI.
To trigger a Layer 2 Tunnel Down service alarm, in Cisco ANA NetworkVision, right-click the required network element and choose VNE Tools > Poll Now.
3.7.2
PBB core bridge missing I-Bridge and B-Bridge mapping
Cisco ANA does not model the I-Bridge and B-Bridge mappings for newly added Bridge LANs for Cisco ASR 9000 series devices.
In this scenario, newly added bridge LANs are discovered but mappings are not populated in Cisco ANA.
Restart the VNE.
3.7.2
Cisco ANA fails to complete path trace across the core
Path traces do not complete in some cases.
This situation occurs when there are LSE entries without outgoing interfaces.
For example, if the path trace destination path is to be traced by looking up LSE entries that do not contain outgoing interfaces, the trace fails. This is because the flow mechanism in LSE does not handle entries that do not have outgoing interfaces and that need a double-lookup in the LSE table.
None
3.7.2
Administrator user with new scope cannot view VNE properties
An Administrator user with a new scope cannot view VNE properties.
This situation can occur after the following sequence of steps:
1. In Cisco ANA Manage, create a scope that does not include all managed elements.
2. Add a new user with the scope created in Step 1 and the security level of Administrator.
3. As the new user, log into Cisco ANA NetworkVision.
4. Double-click a VNE icon.
The VNE properties are not displayed.
None
3.7.2
Cannot deactivate TDM pseudowire operation
You cannot deactivate a TDM multisegment pseudowire using Cisco ANA Network Service Activation.
None
3.7.2
Pseudowire tunnel container is removed when all tunnels are removed
Occasionally, pseudowires might not be discovered at the gateway level.
Initially, all pseudowires are discovery for a specific device. However, if you delete all pseudowires and then readd one, the new pseudowire might not be discovered.
Restart the VNE and AVM.
3.7.2
Wrong serial connection through CDP in MLPPP technology
Physical links under MLPPP are discovered incorrectly.
If CDP is defined on a multilink, the ports under one side of the multilink might connect to the wrong ports under the other side of the multilink.
Disable CDP status on the multilink.
3.7.2
The TFS update command does not have a validateRequest method
If you define several equal trap forwarding services (TFS), and then update an existing TFS, no validation occurs on the new values. As a result, you can update an existing TFS that has the same name, destination, or other information as another TFS.
None
3.7.1
Cisco ANA places an interface under the wrong VRF
If VRF is configured with multilink interfaces, Cisco ANA also populates it on a nonmember VRF.
This situation occurs only for VRFs with multilink members.
None
3.7.2
Cisco ANA does not discover VRF interfaces for FrameRelay multilink subinterfaces
Cisco ANA does not model VRF interfaces configured on FrameRelay multilink subinterfaces on devices running Cisco IOS XR software.
None
3.7.2
Unit remains unreachable after deleting it and readding it as a redundant system
A unit remains unreachable after you delete it and then readd it as a redundant system.
This situation occurs if you:
1. Add a unit to Cisco ANA
2. Add AVMs and VNEs to the unit.
3. Delete the unit.
4. Readd the unit as a redundant unit.
The unit is added in a Down state and then becomes and remains in an Unreachable state.
None
3.7.2
Soft Property command in debug takes too long
Running a Soft Property command in the debug window can take 20-30 minutes for completion.
This situation has been observed with Cisco ASR 9000 series devices (that is, "heavy" devices).
Further Problem Description
Soft Property commands have a regular priority (the same priority as many other commands) and thus wait in the queue for execution.
In addition, other commands can take up to 30 minutes to complete, adding to the delay in the Soft Property command execution.
Do not run Soft Property commands in debug during VNE startup.
3.7.2
Cisco ASR 1006 devices are partially discovered and other issues
Cisco ASR 1006 devices running Cisco IOS 15.1(1)S software are partially discovered in Cisco ANA NetworkVision. Specifically, Cisco ANA NetworkVision models a duplicate power supply and provides no module unsupported information.
The duplicate modeling of the power supply is specific to Cisco IOS version 15.1(1).
Further Problem Description
Adding an unsupported fan module to the device could cause the partial discovery.
None
3.7.2
BFD is not detected when configured under eBGP and IS-IS
BFD is not detected when it is configured under eBGP and IS-IS on Cisco IOS XR devices.
None
3.7.2
Cisco ANA does not have an IS-IS Neighbor tab for Cisco 7600 devices
When only one IS-IS instance is available on the device and no other routing protocol (such as BGP) is enabled on the device, Cisco ANA NetworkVision does not show the IS-IS Neighbor table.
Enable another routing protocol on the device.
3.7.2
Link Down alarm is not correlated to Card Down alarm
On Cisco CRS-1 devices running Cisco IOS XR 3.7.1[00] software, Link Down alarms are not correlated to a Card Down alarms.
None
3.7.2
Migration: Legacy scripts from Cisco ANA 3.7.1 disappear after migration
When updating to Cisco ANA 3.7.2 from earlier versions of Cisco ANA, Cisco Developer Network activation scripts are not displayed in the Cisco ANA GUI.
After upgrading to Cisco ANA 3.7.2, download the activation scripts from the Cisco Developer Network site and install them in Cisco ANA.
3.7.2
OSPFv3 Routing Neighbor Down syslog on Cisco IOS XR does not correlate to OSPF interface
The location of the syslog ROUTING-OSPF-v3-5-ADJCHG is missing in the syslog event in Cisco ANA.
This situation occurs if the syslog of ROUTING-OSPF-v3-5-ADJCHG contains a short form of the interface name, such as Gi0/3. The interface name Gi0/3 does not convert to the standard name and does not appear in the syslog event.
The location of the syslog is available in the ticket the syslog is correlated to.
3.7.2
VLAN interface information is displayed multiple times under the same port
In Cisco ANA NetworkVision physical inventory, VLAN information might be duplicated for port properties.
None
3.7.2
VNE restarts due to software version change
If you reload a device with a new version of Cisco IOS software while the VNE is up and running, the Software Version property is not updated with latest Cisco IOS version.
Clear the persistency and restart the VNE.
3.7.2
No definition for the subtype stop flapping non cleared for type MPLS.
Sometimes, the MPLS TE Tunnel flapping alarm with the description stop flapping non cleared cannot be generated.
However, occasionally, if the flapping continues for a while (that is, if TE Tunnel down alarm occurs seven times instead of five times), the flapping alarm is seen with description stop flapping non cleared as expected.
This issue is not always reproducible and is seen only intermittently.
None
3.7.2
BGP Neighbor Down VRF syslog not correlated to BGP Link Down VRF due to Admin ticket
The BGP Neighbor Down VRF syslog is not correlated to the BGP Link Down VRF due to Admin ticket.
If a PE-CE BGP VRF neighbor peer is established and one of the neighbor entries is administratively shut down, the BGP Neighbor Down syslog and BGP Neighbor Down VRF syslog are generated. However, these syslogs are not correlated to the BGP Link Down ticket.
As a result, the BGP Neighbor Down syslogs are displayed in Cisco ANA EventVision, but they are not correlated to the root cause ticket and must be manually associated by the user given the information in the syslog.
None
3.7.2
AVM 100 error: Error writing snmpv3_engineboots to Golden Source
The following error appears in the 100.out log: Error writing snmpv3_engineboots to Golden Source: null.
This error is displayed if all of the following conditions occur:
•
•
•
The value of snmpv3_engineboots represents the number of times that AVM 100 (the SNMP engine) has initialized or reinitialized itself since its initial configuration. This parameter is used to authenticate devices that work with Cisco ANA. The error means that the system failed to write this parameter to the registry, hence the security check might be invalid.
None
3.7.2
Links stay down in map when unplugging and plugging in SFP connectors
In Cisco ANA NetworkVision maps, the link status remains down when an SFP connector is unplugged and reinserted for Cisco Catalyst 3750 devices.
This situation occurs for all SFPs for all Cisco IOS versions for Cisco Catalyst 3750 devices.
None
3.7.2
Running images are not recognized
Running images are not displayed in Cisco ANA Configuration and Image Management after the device is discovered by Cisco ANA.
This situation might be caused by device synchronization and generation of the operating system snapshots.
Readd the device and wait for the synchronization to complete.
3.7.2
Shutting down a BGP link causes a false BGP Process Down service alarm
A BGP neighbor link down condition sometimes results in a BGP Process Down service alarm.
When a PE-PE BGP neighbor peer is established and one of the neighbor entries is administratively shut down, a false BGP Process Down alarm is displayed in Cisco ANA EventVision. You can confirm that the BGP process is actually up by checking Cisco ANA logical inventory. The service alarm clears after several minutes.
This issue is not always reproducible and is rarely seen.
None
3.7.2
Duplicate Link Down ticket due to Card Out event
Duplicate Link Down tickets due to Card Out event are generated when inband management is temporary unavailable due to STP convergence.
After the card is reinserted, one Link Down event is cleared while the other Link Down event is still visible in Cisco ANA.
This situation occurs when the following sequence of steps occurs:
1. A device is managed in Cisco ANA using inband management.
2. The card is removed from the port through which management is performed. As a result, the management connection to the device is temporarily broken.
3. STP convergence discovers an alternate path for Cisco ANA management.
After the new path is discovered, the following two Link Down tickets are generated:
•
•
Clear the event that is displayed in Cisco ANA.
In response, Cisco ANA removes the link and then rediscovers it.
3.7.2
Exception while reading ATM virtual path (VP) counters
ATM virtual path (VP) counters are not modeled Cisco ANA NetworkVision for Cisco IOS XR versions 3.8.2 and 4.0.1.
This situation occurs for Cisco CRS devices running Cisco IOS XR version 3.8.2 or 4.0.1.
None
3.7.2
Cisco SFP-10GBase- CUxM does not return the proper vendor OID
The Cisco SFP-10GBase-CUxM module does not provide the correct vendor OID in Cisco ANA NetworkVision.
None
3.7.2
Ticket regarding link down is cleared although the link remains down
Cisco ANA clears a Link Down alarm even though the physical link is still down.
This situation occurs if the following sequence of steps occurs:
1. Cisco ANA manages two connected devices and discovers the topology between the devices.
2. A cable is removed from and reinserted into a connected port multiple times over a short period of time, ending with the cable unplugged.
In this scenario, Cisco ANA can display all events as cleared while also displaying the port state as down.
Cisco ANA will not generate an updated Link Down event unless additional changes occur in the network.
None
3.7.2
CDP table port hyperlink and port status do not update correctly
In Cisco ANA NetworkVision logical inventory for CDP, the hyperlink for the port identifies the wrong port.
This situation might occur after any of the following scenarios that change the Interface Index of the port:
•
•
•
•
1. Stop the VNE.
2. Delete the inventory and topology persistency files for the VNE.
3. Restart the VNE.
3.7
IPv6 command is not supported in Cisco NX-OS version 4.2
IPv6 and IPv6-related information is not displayed in Cisco ANA for Cisco Nexus 5xxx series devices running Cisco NX-OS 4.2 software.
None
3.7.2
Port 162 appears to be occupied when IP address contains "162"
When installing Cisco ANA using the install.pl script, the installation fails due to occupied port 162, even though the netstat command confirms that the port is not occupied.
Run the install.pl script with the -override_ports option.
3.7.1
LAG link is not rediscovered after clearing and removing the ticket
If you have a Link Aggregation Group (LAG) with ports under it, and you move the ports to another LAG, Cisco ANA issues a LAG Link Down ticket for the original LAG link and displays the link in red in Cisco ANA NetworkVision maps.
If you then clear and remove the LAG Link Down ticket, the ticket no longer appears in Cisco ANA but the new LAG link is not discovered.
Restart the VNE with the LAG.
3.7.2
Cisco RSP 720 removal redundancy state ticket is issued only after reinsertion.
If you remove an active Cisco RSP card in the Hot Standby state from a Cisco 7600 series device, Cisco ANA does not issue a Cisco RF Unit State Changed ticket until the active card is reinserted and it reaches at least the Cold Standby state.
Further Problem Description
The Cisco ANA event is based on the SNMP v2 trap being received from the device when the Cisco RSP card is removed, but the expected SNMP v2 trap OID is never received.
This issue has been observed with the following Cisco IOS images:
•
•
None
3.7.1
Cisco ME3600X and ME3800x series devices: Port-channel modeling changes
For Cisco ME3600X and Cisco ME3800X series devices, if a switch port is configured with the allowed VLAN value of None, the port-channel is modeled in Cisco ANA NetworkVision as a routed port.
As a result, in Cisco ANA NetworkVision, under a port-channel of type switch port, a routed port can also appear for Cisco ME3600X and ME3800X devices.
For Cisco ME3600X and ME3800X devices, do either of the following:
•
•
3.7.2
Physical and Ethernet links disappear after moving and restarting AVM
Some physical links are not discovered in Cisco ANA if a MAC test incorrectly connects a port that is supposed to be connected to a different port.
Make sure the ports that are incorrectly connected have traffic on them. If these ports have traffic, the incorrect link will be disconnected and the correct link connected.
3.7.2
Cisco CRS-1 device: BGP/BFD ticket does not correlate to Link Down ticket
In some cases with Cisco CRS-1 devices, BGP/BFD tickets do not correlate with Link Down tickets.
This situation occurs if the following conditions exist:
•
•
When connectivity between the connected ports is lost, BGP and BFD correlation does not work as expected.
Further Problem Description
If connectivity between connected ports is lost due to a port shutting down and the connectivity loss is notified on the port operational state, the Link Down event should be identified as the root cause. All other events, including OSPF, BGP, and BFD-related service events, should be correlated to the Link Down event.
If the connectivity loss is not identified on the port operational state, (for example, if an optical network exists between connected ports and it is not managed in Cisco ANA), the BFD Connectivity Down event should be the root cause. All other generated events, including OSPF or BGP service events, should be correlated to the BFD Connectivity Down event.
None
3.7.2
Modeling Cisco CatOS takes a long time
Cisco ANA can take more time to model physical inventory for Cisco 6500 series devices running Cisco CatOS version 8.5(7) software.
None
3.7.2
Cannot start new AVM 100 on unit when unit with old AVM 100 is down
If the following sequence of steps occurs, an error message is displayed stating that AVM 100 is already running:
1. Create an AVM 100 on a unit.
2. Put the unit into an Unreachable state.
3. Add a new AVM 100 on a different unit.
4. Start the new AVM 100.
This situation occurs when at least two units are configured on the Cisco ANA gateway.
None
3.7.2
LAG topology is reconnected before LAG status changes to Up
In Cisco ANA, LAG links are displayed as connected even though the LAG status is displayed as Down.
This occasionally occurs if the LAG link is disabled and reenabled on one side.
None
3.7.2
Cisco 7200 device link filter discovery is not layer-specific in Cisco ANA
Cisco ANA does not discover physical layer links between two Cisco 7200 devices because on the device Tx Counters & Rx Counters on the connected ends will be different.
This situation occurs for connected Cisco 7200 devices that are running versions of Cisco IOS software lower than 12.0(33)S.
None
3.7.2
BGP State Change trap is not processed if source peer is from the VPN IPv6 table
Cisco ANA does not handle BGP State Change traps for VPN IPv6 peers if the neighbor IP address is not in the BGP peer table.
This situation occurs if the BGP neighbor belongs to the IPv6, VPNv6, or VPNv4 address family.
None
3.6.6
BFD with registered protocols of OSPF and BGP link topology not discovered
If BFD is configured for multiple protocols between two devices, only one BFD link is displayed in the topology even though there are two BFD links between the devices.
This situation occurs when BFD is configured for multiple protocols, such as BGP and OSPF, between two devices.
None
3.7.1
Port down on device results in Device Lost Reachability ticket delay
Device Lost tickets and their correlating events might be delayed if you reload a device and then manually shut down an interface in a link.
Wait approximately nine minutes for the ticket and correlated events to be generated.
3.7.1
Cisco ANA 3.7.1 Upgrade: After upgrade, deleting old Cisco ANA user results in exception
If you delete a user in Cisco ANA Manage who was migrated to Cisco ANA 3.7.1 from an earlier version and who was not allowed to run workflows, the user is deleted but an exception is generated.
None. Because the user was deleted as requested, you can close the exception window.
3.7.1
Get Card Down ticket when loading a device the first time
The Card Down ticket and alarm are generated when you start a VNE the first time or restart a VNE.
A Card Out ticket should be generated only when a card that was up goes down.
None
3.7.1
Problem with BFD link hyperlink and link color on alarm
BFD links are not colored despite having a major event on the link. Clicking the BFD link hyperlink results in an error message being displayed.
This issue occurs whenever a BFD link exists between two devices.
None
3.7.1
VNE "Connecting" communication state is misleading
If you create a new AVM in Down state and load a new VNE in Up state, the VNE communication state displayed in Cisco ANA NetworkVision is Connecting.
Instead, the VNE communication state should be Down.
Start the AVM.
3.7.1
Dual-port modeling does not work as expected
When a pluggable port is inserted into a device with a module that supports dual ports, Cisco ANA shows both the ports instead of the inserted port.
For example, a Cisco 7600 device can contain a WS-SUP720-3BXL module that supports dual ports. The two ports are Gigabit Ethernet ports that work as an SFP or RJ-45 port depending on whether or not an SFP is inserted.
When an SFP is inserted into one of these Gigabit Ethernet ports, Cisco ANA should display the SFP port and not the Gigabit Ethernet port. However, Cisco ANA displays both ports.
Further Problem Description
In addition, instead of modeling the SFP with its properties (PID, Serial Number, Pluggable Type, and Media Type), Cisco ANA displays both ports as normal ports.
None
3.7.1
Cisco ASR 9000 devices: OSPF processes do not show serial interfaces in GUI
Logical inventory in Cisco ANA NetworkVision does not display the information for serial interfaces on Cisco ASR 9000 series devices that have serial interfaces as subinterfaces of OSPF processes.
None
3.7.1
Generate two separate tickets regarding link down and up
Cisco ANA generates two separate Link Down events when a port is disconnected and connected a few times.
This situation occurs because, when a port is connected and disconnected, the port can be in any of a number of link event negotiation states. As a result, events might be sent from different sides of the link.
None
3.7.2
SONET bundles are not modeled for Cisco 7200 devices
Cisco ANA NetworkVision does not model SONET bundles for Cisco 7200 devices.
None
3.7.1
Proxy for AVM 25 does not work in high availability (HA) scenarios
Proxy for AVM 25 does not work in the following HA scenario:
•
•
•
In this situation, AVM 25 on Unit A is still configured to use Unit B, which is now down.
In a setup in which the Cisco ANA gateway supports HA, use the gateway machine AVM 25 as proxy for units with no database connectivity.
3.7
Business Element Not Found error when trying to add an EVC to a map
When trying to add a EVC or VPLS to a map, a Business Element Not Found error might be displayed, and the element is not added to the map.
This situation is more likely to occur when deleting a large number of VNEs.
Wait two to ten minutes for the system to finish updating, and then add the element.
3.7.1
Cisco ANA models Cisco 3750g fiber optic ports as RJ45 ports
Cisco ANA models fiber optic ports as RJ45 ports for Cisco Catalyst 3750G devices running Cisco IOS 12.2(25)SEE2.
None
3.7.1
Link between Cisco ME3400 with REP Edge No Neighbor to Cisco ASR 9000 not discovered
If a ring of Cisco ME-3400E access nodes is closed by a pair of Cisco ASR 9000 aggregation nodes, the links between the Cisco ME-3400E devices and the Cisco ASR 9000 devices are not discovered.
Because Cisco ASR 9000 devices do not support REP on EVCs, the edge ports on the Cisco ME-3400 devices are configured as REP Edge No Neighbor ports. These uplinks to the Cisco ASR 9000 devices are not discovered by Cisco ANA or displayed in Cisco ANA NetworkVision maps.
None
3.7.1
Cleared ticket not appearing as blue although correlated with Info alarm
Tickets that contain alarm severities of both Cleared and Information have a severity of Cleared instead of Information.
None
3.7.1
Cisco IOS XR devices: VPN ID is incorrect
A random identifier that is used for creating a VSI key is displayed as the VPN identifier in Cisco ANA NetworkVision for Cisco IOS XR devices instead of the actual VPN identifier.
A VPN identifier is not returned from a Cisco IOS XR device if VPN is not configured. Thus, VPN identifier cannot be used for key creation and cannot be displayed in Cisco ANA.
None
3.7.1
GUI ignores icons in Scalar Notification on OID property
This caveat is exhibited in the following ways:
•
•
•
–
–
•
•
•
Close and reopen the map to update the map.
3.7.1
Using Filter in Cisco ANA EventVision for large table of Syslog
Filtering the contents of the Syslogs tab in Cisco ANA EventVision can result in the query running for a long time and the client appearing to be stuck.
This situation can occur when all of following conditions apply:
•
•
•
None
3.7.1
Missing VlanInterface notification when moving switchport to routed
The VLAN Interface notification is missing if you change switchport to routed.
This situation occurs as follows:
1. Add a VNE.
2. Select a GigabitEthernet trunk port, and verify that the related VLAN interface appears under the respective bridge.
3. Change the Switchport to routed by entering the no switchport command.
VLAN Interface notification will be missing.
None
3.7.1
ATM IMA cards do not populate Loopback, Framing, or Scrambling values
ATM IMA cards do not populate E1 properties like Framing, Loopback, or Scrambling values.
This situation occurs for channelized cards inserted into Cisco 7200 devices.
None
3.7.1
VNE duplicate alarms regarding module, memory, CPU, and card down
Duplicate tickets and alarms are produced for Module Unsupported, Memory Utilization, CPU Utilization, and Card Down in the following situations:
•
•
•
None
3.7.1
Corresponding ATM interfaces are not displayed in Cisco ANA for ATM-IMA interfaces for Cisco 7200 series devices
If IMA is configured on ATM in a Cisco 7200 series device, corresponding ATM interfaces are not displayed in Cisco ANA NetworkVision for the ATM-IMA interfaces.
None
3.7.1
Creating a cross-connect in an ATM cloud takes a long time
Creating a cross-connect of two devices that connect to a cloud takes a long time and can appear is if the creation has failed. This situation can occur when connecting two ATM ports to a cloud VNE.
You can ignore the command status as it is actually successful.
None
3.7.1
Migration: Small-scale migration takes longer than large-scale migration
Migrating Cisco ANA from version 3.6.7 to version 3.7 takes a few hours for a small-scale environment.
None
3.7
Incorrect exception is returned for nonexistent ticket via BQL
Ticket operations like Acknowledge, Clear, and Remove on nonexistent or archived tickets return the wrong error message. The error displayed is
"Execution failed. Tickets are in use. Please try again."This situation occurs when a BQL command is executed on an archived or nonexistent ticket OID.
The behavior of executing BQL commands on tickets in Cisco ANA 3.7 changed from Cisco ANA 3.6.7.
None
3.7
IPoDWDM: Trace detail script fails in Cisco CRS device with Cisco IOS XR 3.9.0 image
If you attempt to run the Trace detail script on the SONET ports of a Cisco CRS device with Cisco IOS XR 3.9.0, the script fails. The Trace detail script is available by right-clicking the device and then selecting Commands > SONET > Show > Trace Details.
This situation occurs for Cisco CRS devices with Cisco IOS XR 3.9.0 and SONET controllers.
None
3.7
IPoDWDM: Configuring Laser state script fails for Cisco CRS devices running Cisco IOS XR 3.9.x
Laser state scripts fail for Cisco CRS devices that are running Cisco IOS XR version 3.9.0 or later.
None
3.7.1
Cannot attach a business tag to BGP neighbors
If you select Logical Inventory > MPBGPs > MPBGP > BGP Neighbors and attempt to attach a business tag to a BGP neighbor, the following error is displayed:
"Could not created element."None
3.7
SSH with Cisco ASR 9000 series devices causes VTY syslogs
Cisco ASR 9000 series devices generate the following security syslog message each time Cisco ANA starts an SSH session with them:
%SECURITY-SSHD-6-INFO_GENERAL: Warning: The requested term-type is not supportedThe SSH session is initiated correctly and you can ignore the message.
None
3.7
Cisco ANA 3.7 Migration: Static links between a cloud and router are lost
After migrating to Cisco ANA 3.7, Cisco ANA NetworkVision might not display static links that were created before the migration.
Delete the static link and then recreate it.
3.7
For bundle interfaces and subinterfaces, protocol information is not displayed for ports
In Cisco ANA NetworkVision, CDP and LLDP information is not displayed for bundle interfaces or subinterfaces.
None
3.7
Redundant Martini tunnel status is not updated
If you use a redundant Martini and you switch from the active tunnel to the inactive tunnel, the new port tab is not updated in Cisco ANA NetworkVision.
Stop and then restart the VNE.
3.6.6
Wrong physical links are discovered with Cisco Discovery Protocol (CDP) when service instances are configured with encapsulation untagged
Cisco ANA discovers the wrong links with the following configuration:
•
•
•
service instance 1 ethernetencapsulation untaggedxconnect 172.255.3.169 999999 encapsulation mpls•
•
•
service instance 1 ethernetencapsulation untaggedxconnect 172.255.3.175 999999 encapsulation mplsThe results of this are:
•
•
–
–
None
3.6.7
IP SLA Trap Ticket information does not contain rttMonEchoAdminLSPSelecto
Cisco ANA EventVision does not show Trap Ticket information for the following field in the SNMP trap:
iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoRttMonMIB.ciscoRttMonObjects.rttMonCtrl.rttMonEchoAdminTable.rttMonEchoAdminEntry.rttMonEchoAdminLSPSelector
This situation occurs when IP SLA is configured on the router and router traps are configured to be sent to Cisco ANA.
Retrieve the attribute manually from the router in any of the following ways:
•
•
•
3.6.7
Inconsistency between Path and Path Details possibly because of LAG
If you run Cisco ANA PathTracer between two switches, discrepancies exist between the information that is displayed in the content area and that displayed in Properties table of the Cisco ANA PathTracer window.
These inconsistencies between the path and path details are possibly caused by LAG.
None
3.6.7
LAG topology between MSTP and PVSTP devices is not discovered
Link Aggregation (LAG) links are not discovered in Cisco ANA NetworkVision between devices when one of the devices is configured for Per-VLAN Spanning Tree Protocol (PVSTP) and the other device is configured for Multiple Spanning Tree Protocol (MSTP).
The physical link is discovered if CDP or LLDP is configured on the devices.
The LAG link is discovered if the LAG runs LACP protocol.
None
3.6.7
Local switching is not supported on physical interface scenarios
Local switching is supported only when both interfaces of Cisco CRS-1 devices are configured as subinterfaces.
The following scenarios are not supported on Cisco ANA:
•
•
None
3.6.7
Subinterface not discovered
The subinterface is not populated in Cisco ANA.
This situation occurs because the subinterfaces are populated based on the technologies that are supported in Cisco ANA.
See the Cisco Active Network Abstraction 3.7.2 Reference Guide for details on the supported technologies.
3.6.5
BQL adapter does not raise an error when a BQL command contains invalid data
If you enter the IMO property name incorrectly while creating a BQL command, the BQL command disregards this property without displaying an error.
For example, if the command contains an "Index" property and you enter "index" as the property name, the value is disregarded.
None
3.6.5
Filter ticket does not work in VPN map view
In Cisco ANA NetworkVision, if you right-click a link in the VPN map view and choose Filter Ticket, no results are displayed.
None
3.6.6
Cisco 4503 device: Dynamic VLAN type is shown as static VLAN
For Cisco Catalyst 4503 devices, the dynamic VLAN setup is displayed as static VLAN in Cisco ANA NetworkVision.
None
3.6.6
Resolved Caveats in Cisco ANA 3.7.3
Table 18 identifies the caveats resolved in Cisco ANA 3.7.3.
Closed Caveats in Cisco ANA 3.7.3
Table 19 identifies the caveats that were closed in Cisco ANA 3.7.3. For more information on a specific caveat, click the identifier hyperlink to view the caveat in Cisco Bug Toolkit.
Related Documentation
The following documentation is available for Cisco Active Network Abstraction 3.7.3:
Cisco Active Network Abstraction 3.7.3 Administrator Guide
Cisco Active Network Abstraction 3.7.2 Customization User Guide
Cisco Active Network Abstraction 3.7.3 Documentation Guide
Cisco Active Network Abstraction 3.7.3 Installation Guide
Cisco Active Network Abstraction 3.7.3 Quick Start Guide
Cisco Active Network Abstraction 3.7.3 Release Notes
Cisco Active Network Abstraction 3.7.2 Reference Guide
Cisco Active Network Abstraction 3.7.2 Theory of Operations Guide
Cisco Active Network Abstraction 3.7.3 User Guide
Cisco Active Network Abstraction Network Service Activation 1.3 User Guide
Cisco Active Network Abstraction Network Service Activation 1.3 Customization Guide
Open Source Used in Cisco Active Network Abstraction 3.7.3
Cisco Active Network Abstraction 3.7.2 Integration Developer Guide is available on the Cisco ANA Technology Center website. This guide describes how to use Cisco ANA integration interfaces.
The Cisco ANA Technology Center is an online resource for additional downloadable Cisco ANA support content, including help for integration developers who use Cisco ANA application programming interfaces (APIs). It provides information, guidance, and examples to help you integrate your applications with Cisco ANA. It also provides a platform for you to interact with subject matter experts. To view the information on the Cisco ANA Technology Center website, you must have a Cisco.com account with partner level access, or you must be a Cisco ANA licensee. You can access the Cisco ANA Technology Center at http://developer.cisco.com/web/ana/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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and 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 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.
© 1999-2011 Cisco Systems, Inc. All rights reserved.
