Table Of Contents
Cisco Active Network Abstraction 3.7
Release NotesNetwork Element Inventory Discovery
Network and Service Monitoring
New Features and Enhancements in Cisco ANA 3.7
Fault Management Northbound Integration
Cisco ANA Management Enhancements
Features Removed or Changed in Cisco ANA 3.7
New Network Element, Module, and Software Support
New Alarm, Trap, and Syslog Support
Cisco IOS V1 Trap Support Added
Cisco IOS V2/V3 Trap Support Added
Cisco IOS XR V1 Trap Support Added
Cisco IOS XR V2/V3 Trap Support Added
Cisco MIB2 V1 Trap Support Added
Cisco MIB2 V2/V3 Trap Support Added
Cisco IOS Syslog Support Added
Cisco IOS XR Syslog Support Added
Prerequisite for Cisco ANA 3.7
Before Upgrading to Cisco ANA 3.7
Solaris Services and Components
Installing the Cisco IOS XR Manageability Package
Device and Software-Specific Limitations
JDK DST Timezone Update Tool for Cisco ANA
Configuring Database Storage (Redo Logs)
Workflow Editor Template Naming Conventions
VLAN Tagged Interface Limitation
Resolved Caveats - Cisco ANA 3.7
Obtaining Documentation and Submitting a Service Request
Cisco Active Network Abstraction 3.7
Release Notes
Revised: January 28, 2011, OL-20013-16
These release notes support the release of Cisco Active Network Abstraction (Cisco ANA) 3.7.
Note
See Cisco.com for the most up-to-date version of the Cisco Active Network Abstraction 3.7 Release Notes.
New and Changed Information
The following table describes information that has been added or changed since the Cisco Active Network Abstraction 3.7 Release Notes was last published online.
Contents
This document includes the following topics:
•
•
•
•
•
•
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-1 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) Telecommunications Management Forum (TMF)-compliant information model and other Cisco ANA services. 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.
•
•
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 network element 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 define reports as required for your environment. The Report Manager is available from Cisco ANA NetworkVision, Cisco ANA EventVision, and Cisco ANA Manage. The Report Manager enables you to run standard reports, such as the number of syslogs by device, or to define reports suited to your environment.
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.
New Features and Enhancements in Cisco ANA 3.7
The following topics describe the new features, enhancements, and changes in Cisco ANA 3.7:
•
•
For information about support added in Cisco ANA 3.7 for devices, software, or fault management, see:
•
•
Installation and Migration
Cisco ANA 3.7 provides the following new features related to installation and migration:
•
•
•
–
–
–
•
•
Carrier Ethernet
Enhancements for Carrier Ethernet in Cisco ANA 3.7 include:
•
–
–
–
•
–
–
–
•
–
–
–
•
•
–
–
IP RAN and MToP
Cisco ANA 3.7 includes the following enhanced support and features for IP Radio Access Networks (RANs) and Mobile Transport over Packet (MToP):
•
•
•
•
•
•
–
–
–
•
–
–
–
•
–
–
–
–
•
•
IP over DWDM
Cisco ANA 3.7 includes the following additional inventory support for IP over Dense Wavelength Division Multiplexing (DWDM):
•
•
•
Cisco ANA 3.7 also supports IPoDWDM:
•
•
•
IPv6 and 6VPE
The Cisco ANA 3.7 IPv6 implementation completes support for:
•
•
–
–
–
–
•
•
•
•
•
–
–
•
•
•
•
Fault Management
Cisco ANA 3.7 introduces fault management improvements that provide:
•
•
•
•
–
–
–
•
For more information, see the Cisco Active Network Abstraction 3.7 User Guide.
Reports
Cisco ANA 3.7 includes a Report Manager option that enables you to generate, customize, view, and export a variety of reports about events, traps, tickets, syslogs, software versions, and devices. The Report Manager, available from Cisco ANA Manage, Cisco ANA NetworkVision, and Cisco ANA EventVision, provides out-of-the-box reports for events and inventory.
The Report Manager enables you to:
•
•
•
•
For information about reports and Report Manager, see the Cisco Active Network Abstraction 3.7 User Guide.
You can also retrieve reports using BQL. For more information, see the Cisco Active Network Abstraction Integration Developer Guide.
Security
Security enhancements in Cisco ANA 3.7 include:
•
–
–
–
•
Fault Management Northbound Integration
Cisco ANA 3.7 includes the following support for event notification services for northbound integration (NBI):
•
•
•
•
–
–
•
For more information about fault management NBI, see the Cisco Active Network Abstraction Integration Developer Guide.
GUI-Related Enhancements
•
•
Cisco ANA Management Enhancements
Cisco ANA 3.7 includes the following enhancements related to Cisco ANA management:
•
•
–
–
–
–
•
–
–
Features Removed or Changed in Cisco ANA 3.7
Features Removed
The following features are not available in Cisco ANA 3.7:
•
If you are upgrading from an earlier version of Cisco ANA and use the third-party VNE drivers described in the Cisco Active Network Abstraction 3.6.7 VNE Reference Guide, the third-party VNE drivers can be reenabled for migration to Cisco ANA 3.7.
Contact your Cisco Account Manager or Advanced Services point-of-contact for assistance in reenabling third-party VNE drivers.
•
•
Features Changed
The following features have changed in Cisco ANA 3.7:
•
•
•
–
–
Documentation Enhancements
Cisco ANA 3.7 provides an improved and better-organized documentation set that includes:
•
•
•
Individual Cisco ANA 3.7 documents have been updated and enhanced as follows:
•
•
–
–
–
•
•
•
–
- Web services—Implemented using JAX-WS framework. This provides the capabilities to run BQL commands over web services (WSDL) connections. The web service client supports running BQL commands and registering for notifications. It is also compatible with other WS integration tools.
- BQL commands over HTTP interface—Provides the capabilities to run BQL commands through HTTP requests by using a standard web browser. The HTTP GET and POST operations are used to send and retrieve the data from Cisco ANA gateway.
–
You can also filter these notifications based on event type, event category, severity, and source IP address. See the Cisco Active Network Abstraction Integration Developer Guide for details.
•
–
–
- IP over DWDM commands are supported on Cisco 7600 series routers.
- CFM and Ethernet Operations, Administration, and Maintenance (E-OAM) commands are supported on Cisco ASR 9000 Series Aggregation Services routers.
Note
Other Changes
Cisco ANA 3.7 has resolved a number of open bugs. For details, see Resolved Caveats - Cisco ANA 3.7.
New Network Element, Module, and Software Support
The following topics describe the new support provided in Cisco ANA 3.7 for network elements, modules, and software:
New Network Element Support
Table 2 identifies the new network element types supported in Cisco ANA 3.7.
New Module Support
Table 3 identifies the new module support available in Cisco ANA 3.7.
New Software Version Support
Table 4 identifies the new software versions supported in Cisco ANA 3.7.
New Alarm, Trap, and Syslog Support
The following topics describe the new service alarms, trap support, and syslog support provided in Cisco ANA 3.7:
New Service Alarms
Table 5 describes the service alarms that were added in Cisco ANA 3.7.
New Trap Support
The following sections identify the trap support added in Cisco ANA 3.7:
•
•
•
•
•
•
Cisco IOS V1 Trap Support Added
Table 6 identifies the Cisco IOS SNMPv1 trap support added in Cisco ANA 3.7.
Cisco IOS V2/V3 Trap Support Added
Table 7 identifies the Cisco IOS SNMPv2/v3 trap support added in Cisco ANA 3.7.
Cisco IOS XR V1 Trap Support Added
Table 8 identifies the Cisco IOS XR SNMPv1 trap support added in Cisco ANA 3.7.
Cisco IOS XR V2/V3 Trap Support Added
Table 9 identifies the Cisco IOS XR SNMPv2/v3 trap support added in Cisco ANA 3.7.
Cisco MIB2 V1 Trap Support Added
Table 10 identifies the Cisco MIB2 V1 trap support added in Cisco ANA 3.7.
Cisco MIB2 V2/V3 Trap Support Added
Table 11 identifies the Cisco MIB2 V2/V3 trap support added in Cisco ANA 3.7.
New Syslog Support
The following topics identify the syslog support added in Cisco ANA 3.7:
•
•
Cisco IOS Syslog Support Added
Table 12 identifies the Cisco IOS syslog support added in Cisco ANA 3.7.
Cisco IOS XR Syslog Support Added
Table 13 identifies the Cisco IOS XR syslog support added in Cisco ANA 3.7.
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 Installation Guide.
Cisco ANA 3.7 is installed on top of a Cisco ANA 3.6 installation and includes all patches that were released since the Cisco ANA 3.6 release. Any patches or fix packs that were previously installed on top of Cisco ANA 3.6 are automatically uninstalled by the 3.7 installation script.
Prerequisite for Cisco ANA 3.7
If you are using Oracle Database 11g, you must install the following patch, as appropriate for your system, before installing Cisco ANA 3.7:
•
•
Before Upgrading to Cisco ANA 3.7
Before migrating to Cisco ANA 3.7, close all database sessions (such as TOAD, SQL, and so on).
Cisco ANA 3.7 introduces IMO changes as described in the Cisco Active Network Abstraction 3.7 Installation Guide. Review these changes before upgrading to Cisco ANA 3.7 so that you know how any integration that uses the Cisco ANA northbound interface (NBI) is affected.
We also recommend that you review the BQL section in the Cisco Active Network Abstraction Integration Developer Guide to ensure that the integration is not affected by these changes.
Using the install.pl Command
When entering the install.pl command, you must enter perl at the beginning of the command line. For example, when installing a Cisco ANA gateway, enter:
perl ./install.pl -user nameThe perl install.pl command is used when installing a Cisco ANA gateway or unit, and when migrating from Cisco ANA 3.6.7 to Cisco ANA 3.7.
For more information, see the Cisco Active Network Abstraction 3.7 Installation Guide.
Memory Consumption
If your network contains several routers that maintain 1000 or more BGP routing entries in their routing tables, and if the VNEs for these devices use the product scheme, memory consumption might increase with this release.
If new modeling was added for VNEs used in your environment, we recommend that you check your AVM memory allocations. Contact the Cisco ANA Project Manager or Cisco Account Team to perform the necessary calculations.
Backward Compatibility
Note the following with regard to backward compatibility of Cisco ANA 3.7 with existing installations of Cisco ANA 3.6.x:
•
•
•
If you have a very large database (~42 million records) with up to 5,000 open tickets, you can expect a normal upgrade execution time of 6 to 7 hours.
For more information, contact your Cisco account representative.
•
•
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 Installation Guide.
Using Cisco CRS-1 VNEs
This section contains the following topics:
•
Installing the Cisco IOS XR Manageability Package
For Cisco CRS-1 VNEs, you must install the Cisco IOS XR Manageability Package on top of the Cisco IOS XR version. In addition, verify that the device configuration contains the following command:
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 RWDevice 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.
Cisco CRS-1 router
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-FCC-SC-22GE module
Prior to Cisco IOS XR 3.9.0.
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.
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 device
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.0
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.
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 MWR 2941 device
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.
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.
Supported Schemes
Cisco ANA supports two schemes:
•
•
For supported device type and schemes table, see Cisco Active Network Abstraction 3.7 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
Configuring Database Storage (Redo Logs)
If you are already running Cisco ANA 3.6.x, change the Oracle installation to write the logs on a different disk. For more information, see the Cisco Active Network Abstraction 3.7 Installation Guide.
Online Help
The online help has been updated for Cisco ANA 3.7 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 NetworkVision
For information on the maximum number of objects, links, tickets, and maps that Cisco ANA NetworkVision can display, contact your Cisco account representative.
Cisco ANA Fault Management
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 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
The following sections provide information for working with Cisco ANA Workflow Editor:
•
Workflow Editor Template Naming Conventions
Do not include the characters underscore (_) or percent (%) in workflow template names when running a workflow or referencing a subflow. In template names, these characters act as wildcards and represent the following:
•
•
If these characters are included in template names, the execution fails and the following message is displayed in the AVM 66 log:
"WARN [13 21:00:08,248] - dralasoft.workflow - Task aborted. Task: 245886, Workflow: 245885 java.lang.IllegalArgumentException: Template AA_BB.template is ambiguous, templates ids are: 245874 , 245873"The following examples illustrate how workflow template names with these characters can lead to ambiguity if they are deployed together:
•
•
This ambiguity occurs only when templates containing wildcard characters in their names are run.
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.
OSPF
OSPF networks are presented in Cisco ANA logical inventory. The current implementation was developed to present nonoverlapping interfaces so that, when a device has multiple interfaces with the same IP address and these interfaces participate in different OSPF networks, only one interface is displayed.
For example, a device might have multiple interfaces that use the same IP address if it is configured for multiple VRFs.
This situation can occur when multiple OSPF processes are running on the device.
OSPF processes (OSPFService) do not have IMO representation in Cisco ANA.
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
Table 15 identifies the open caveats in Cisco ANA 3.x.
Table 15 Open Caveats in Cisco ANA 3.x
Ticket duplicated after upgrade from Cisco ANA 3.7.0.2 Point Patch 10 to Cisco ANA 3.7.0.2 Point Patch 11
If tickets exist that have not been cleared and you upgrade from Cisco ANA 3.7.0.2 Point Patch 10 to Cisco ANA 3.7.0.2 Point Patch 11, the tickets are duplicated and the original tickets are not correlated to any alarms.
Do either of the following:
•
•
3.7.0.2 PP11
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 ifindex of the port:
•
•
•
•
1.
2.
3.
3.7
System cannot handle large number of tickets with thousands of events attached
Cisco ANA does not perform well if the following conditions exist:
•
•
As a result of these conditions:
•
•
Contact Cisco Technical Support for the availability of a patch.
3.7
No alarms when tickets filtered from device VNE level in Cisco ANA NetworkVision
If you filter tickets in Cisco ANA NetworkVision by right-clicking a VNE has displays an alarm icon, no tickets are displayed in the ticket pane.
However, when you open the device properties window or Cisco ANA EventVision, the tickets are displayed correctly.
None
3.7
Cisco ANA sending email alerts took a corporate server down
If Cisco ANA sends 30,000 email messages in 30 minutes, it can shut down a corporate email server. In addition, events are not associated with tickets.
This situation was encountered when Cisco ANA was configured via a Drools rule to send email and the OPEN_CURSORS parameter value was set to 300.
Do either of the following:
•
•
1.
sqlplus> alter system set OPEN_CURSORS=2000 scope=BOTH2.
3.7
Unit AVMs are unreachable when unit protection group is disabled
If you add a standby unit with protection enabled to a gateway, disable unit protection, and then restart the unit, all AVMs on the unit being restarted are disabled by the high availability (HA) service.
This situation occurs if you add a unit with protection enabled, disable unit protection, and then restart the unit.
1.
2.
3.
3.7
Location filter in Cisco ANA EventVision uses Contains instead of Equals function
When filtering by Location in Cisco ANA EventVision, standard filtering logic applies. For example, if you set the Location filter to CRS, records containing CRS (such as CRS1 and CRS2) are included in the list of results.
None
3.7.0
TFS doesn't send correct EPM-MIB (cenAlarmIndex in wrong place)
Currently the cenAlarmIndex is sent as a separate OID (1.3.6.1.4.1.9.9.311.1.1.2.1.1) plus value. It should instead be a suffix in all OIDs of the generated trap (instead of sending 1.3.6.1.4.1.9.9.311.1.1.2.1.1).
None
3.7
Event Archive may contain redundant raw events in high availability (HA) scenario with multiple AVM 100s
In certain HA scenarios, after a switchover occurs, the Event Archive will contain redundant raw events. This occurs on systems that meet ALL of the following:
1.
2.
3.
4.
Events are duplicated because the same device is classified as managed by one unit and unmanaged by another unit; and because ANA is configured to save events from unmanaged devices. Example:
•
•
•
•
The result is that when Unit3 comes up, it classifies Device2 as unmanaged; but Unit2 continues to classify Device2 as managed (no change). Therefore, when Device2 forwards any events, the events will be duplicated in the Event Archive because the same device is considered both managed and unmanaged, and events from unmanaged devices are being saved.
This is a temporary situation that will resolve itself as soon as the down unit (Unit 1 in the example) comes back up.
3.7
Soft Properties GUI does not support negative numbers for TCA threshold
The Soft Properties GUI does not support negative numbers in the threshold crossing alarm threshold field.
The workaround is to either copy and paste the negative number into the field, or use BQL instead of the Soft Properties GUI.
3.7
User Role and Scope
A user with the role of Operator can access the Soft Properties management menu and add, edit, or remove entries.
This situation occurs when a user with the role Operator logs into Cisco ANA and has access to a network element in a scope.
Contact Cisco Technical Support for the availability of a patch.
3.7
Cisco ANA client does not work with Oracle secured connection
After installing Cisco ANA 3.7 with a secured Oracle connection, Cisco ANA EventVision cannot connect to the database.
This situation occurs if you install Cisco ANA 3.7 while using a secured connection to the Oracle database.
Enter the following commands on the gateway as user ana37 from directory ~/main:
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 persistency/nodes/main/Exte rnalEncryptionTypesClient RC4_256,RC4_128,RC4_56,RC4_ 40,AES256,AES192,AES128,3DE S168,3DES112./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 persistency/nodes/main/Exte rnalEncryptionClient Requested3.7
ASR 9000: Need to support dot1agCfmFaultAlarm 1.3.111.2.802.1.1.8.0.1
The following are not supported in the ASR 9000:
•
•
The first is reported as a generic trap and the second as a generic syslog.
Contact Cisco Technical Support for the availability of a patch.
3.7
Event notification service resets cenUserMessages after update to TFS forwarder
Each event notification service subscription maintains a counter of notifications sent.
If the subscription is updated, the counter is reset and it should not be.
None
3.7
Part of CDP links are not discovered
In Cisco ANA NetworkVision, some physical links for CDP are not discovered.
This situation can occur if both CDP and LLDP are configured on the port, and the Cisco IOS software version is earlier than 12.2(52).
Use either of the following workarounds:
•
•
3.7
Handling reserved characters in Cisco ANA cross-launch URL
If you configure a URL as a cross-launch option and the URL contains a special character like an ampersand (&), all characters following the special character are ignored.
None
3.7
Removing 200 tickets frequently results in operation timeout messages
If you run ticket commands, such as Clear or Remove, on a high number of tickets, the operation might timeout.
Whether or not this situation occurs depends on the number of tickets affected by the command and the current system load.
Run the command on fewer tickets.
3.7
Bells are not always removed after being acknowledged
If you use the Acknowledge operation on a large number of tickets, all tickets are correctly marked as Acknowledged, but not all counters related to the severity aspect are reset. As a result, some VNEs continue to display bell alarm icons with the appropriate color for the ticket severity.
If you continue working with the system, additional VNEs retain their bell icons, and there is no way to remove them.
This situation can occur when you acknowledge an especially large number of tickets, or when the gateway is busy.
None
3.7
No reflection in severity aspect for event with severity of Information
When an event with the severity of Information arrives, there is no indication of the event on the VNE:
•
•
None
3.7
Severity aspect: Concurrency issue with force-clearing events
If multiple clearing operations are performed concurrently on the same ticket, Cisco ANA might indicate the incorrect severity for the ticket.
The severity indicator might be wrong if the Clear command is issued on a ticket concurrently with one of the following operations:
•
•
None
3.7
Network VLANs that are deleted are not rediscovered
Network VLANs that existed and were removed are not rediscovered in Cisco ANA NetworkVision when the bridges are rediscovered.
For example, this situation can occur if you remove bridges and delete the related switching entities.
Contact Cisco Technical Support for assistance.
3.7
Static port creation on ATM cloud not working on Cisco ANA 3.7
If you use the command CloudPortOperation to add a port to an ATM cloud, the static port is not created.
Discover the ports dynamically.
3.7
Cisco MWR devices: BFD entries missing from logical inventory
When a Cisco MWR devices is configured with multiple Bidirectional Forwarding Detection (BFD) entries, some of the BFD entries might not appear in Cisco ANA NetworkVision logical inventory.
This situation occurs when BFD is configured with the same source and destination IP addresses in different VRF and routing tables.
It can also occur when the device output is different from the defined format.
None
3.7
Physical topology is not discovered when STP is configured over a service instance on one of the ports
If two devices are configured with STP, and at least one of them is configured with STP over a service instance, STP is not modeled correctly in Cisco ANA NetworkVision and the topology is not discovered. This situation occurs even if CDP and LLDP are defined.
This situation occurs on Cisco ASR 9000 series and Cisco 7600 devices when STP is configured over a service instance on one of the ports.
None.
3.7
Error (1000): General error while clearing tickets in Cisco ANA NetworkVision
While clearing a large number of tickets, the following error appears:
ERROR (1000): General Error[Ljava.lang.StackTraceElement;@ 4d557b9f-------------------------------ERROR (1000): General error - [Ljava.lang.StackTraceElement;@ 4d557b9fat com.sheer.metromission.plugin.n ewalarm.commands.AbstractUpdate TicketCommand.run(AbstractUpdat eTicketCommand.java:48)at com.sheer.framework.commands.St atelessCommand.localExecute(Sta telessCommand.java:68)at com.sheer.framework.commands.Co mmand.execute(Command.java:63)at com.sheer.metromission.session. CommandEntry.execute(CommandEnt ry.java:55)at com.sheer.metromission.session. Session.processMessage(Session. java:356)...Select a smaller number of tickets and clear them in several batches.
3.7
Filter on tickets in Cisco ANA NetworkVision does not filter notified ticket
If you set a filter in Cisco ANA NetworkVision so that cleared tickets are not displayed and then receive new ticket, the new ticket is displayed even after you clear it.
Clear the filter and then reapply it.
3.7
Cisco ANA 3.6.x to Cisco ANA 3.7 Migration: VNE display error after migration
After migrating from Cisco ANA 3.6.x to Cisco ANA 3.7, Cisco ANA might not display all VNE attributes.
The VNE software version changed in Cisco ANA 3.7. As a result, some of the AVM 11 plugins fail to start and VNE data might not be displayed in the Cisco ANA Manage GUI.
Complete the following steps after successfully migrating to Cisco ANA 3.7:
1.
2.
3.
3.7
Missing XFP port connectors for Cisco CRS-1 device are not populated
XFP port connectors that are missing in Cisco CRS-1 devices running Cisco IOS XR 3.9.0 are not modeled in Cisco ANA NetworkVision physical inventory.
Usually, when an XFP port connector is not inserted in a port slot, Cisco ANA models the port connector name followed by string "Missing Pluggable port." this string does not appear in Cisco ANA NetworkVision for Cisco CRS-1 devices due to this issue.
None
3.7
Cisco ANA 3.7 Migration: LDAP authenticated user cannot log in
Cisco ANA GUI users who were authenticated by remote LDAP servers through SSL in Cisco ANA 3.6.7 are no longer authenticated by remote LDAP servers after migration to Cisco ANA 3.7.
None
3.7
Cisco ANA 3.7 Migration: Small-scale environment migration is longer than large-scale environment
Migrating Cisco ANA from version 3.6.7 to version 3.7 takes a few hours for a small-scale environment.
None
3.7
The system does not support 2000 CE VNEs on one unit
After loading 2000 CE VNEs on a single 64-GB unit, the following can occur:
•
•
•
Distribute the VNEs between units so that there are 1000 on each unit.
3.7
BFD service shown as running in Cisco GSR devices running Cisco IOS XR all the time
For Cisco GSR devices running Cisco IOS XR software, Bidirectional Forwarding Detection (BFD) is displayed as up and running in Cisco ANA NetworkVision logical inventory when BFD is not configured on the device.
This situation occurs only for Cisco GSR devices running Cisco IOS XR software.
None
3.7
Adding new EFP to a loaded Cisco ASR 9000 series device takes a long time to be discovered
An Ethernet flow point (EFP) that is newly added to a Cisco ASR 9000 device takes a while to be discovered in Cisco ANA.
This situation occurs when the Cisco ASR 9000 device is loaded with a large number (30,000) of EFPs.
None
3.7
Duplicate AVMs were created after moving AVMs between units
In Cisco ANA Manage, if you perform parallel requests of AVMs, the following occur:
•
•
"ElementManagementElementHandle r.handleDuplicateKey - CONFIGURATION ERROR - Duplicate DA Key!"This situation can occur if you move an AVM from unit X to unit Y, and then move the same AVM to unit Z.
Complete the following steps:
1.
2.
3.
grep avm<problematic-avm-id> */*.xml4.
If not, remove the file in that unit and leave it only in the unit that contains that key in the avm99.xml.
If the key exists in more than one avm99.xml, remove the whole key from the avm99.xml in the duplicate units and the avm<problematic-avm-id>.xml files. Leave it only in the required unit.
5.
3.7
Cisco ANA 3.6.x-3.7 migration: Links are removed after tickets are cleared
After migration from Cisco ANA 3.6.x to Cisco ANA 3.7, existing links are removed from Cisco ANA NetworkVision if Link Down tickets related to the links are cleared.
For example, assume you are running Cisco ANA 3.6.6 and Link Down tickets exist for some of the links.
If you clear the Link Down tickets after migrating to Cisco ANA 3.7, the links are removed from Cisco ANA NetworkVision.
The links are displayed again when the VNEs are rediscovered.
None
3.7
Online Help PDF of Cisco ANA Administrator Guide or Cisco ANA User Guide cannot be displayed in Mozilla
If you click the PDF link in online help for the Cisco ANA 3.7 User Guide or the Cisco ANA 3.7 Administrator Guide, the PDF file is displayed correctly in Windows Internet Explorer (IE), but not in Mozilla Firefox.
This situation occurs if Mozilla Firefox is your default browser.
Use either of the following workarounds:
•
•
3.7
Ticket Severity Update filtering does not forward events
If you create a notification service with TicketSeverityUpdate as a category, TicketSeverityUpdate filtering does not forward events.
Use the TicketUpdate category and refer only to ticket updates that have the Severity field updated.
3.7
Events not generated after flapping
If you complete the following steps, events are not generated after flapping:
1.
2.
3.
Link down stopped flapping non cleared.4.
Note that the port status changed, but the link status is still down and a 'Port Up' ticket is not generated.
5.
None
3.7
anactl does not stop the unit
The anactl command does not stop Cisco ANA units.
Enter the following commands:
pkill javapkill mvm3.7
Exception when editing or creating a VNE
In Cisco ANA Manage, an exception is generated when you edit or create a VNE.
None
3.7
Cloud problem service alarm is not received
When an Ethernet cloud is configured and an event occurs in the network that causes a problem in the cloud (such as link down), Cloud Problem service alarms are not generated.
None
3.7
Cisco 7600 device running Cisco IOS SRE and Cisco ASR 1000 device running RLS5: MPBGP is not modeled
MPBGP properties are not modeled correctly in Cisco ANA NetworkVision logical inventory for:
•
•
None
3.7
BFD throwing java.lang.NullPointerException
Bidirectional Forwarding Detection (BFD) is not displayed in Cisco ANA NetworkVision when BFD is configured on an existing, managed VNE.
Restart the VNE.
3.7
Cisco SA-VAM2+ module details are wrong
The following properties for Cisco SA-VAM2+ modules are displayed incorrectly in Cisco ANA NetworkVision:
•
•
•
None
3.7
Cisco 7600 device: ACE10-6500-K9 module details are incorrect
On Cisco 7600 devices, the properties for the ACE10-6500-K9 module are displayed incorrectly in Cisco ANA NetworkVision physical inventory.
None
3.7
Cisco 7600 device: Cisco Catalyst 6000 series WS-SVC-FWM-1 module details are incorrect
On Cisco 7600 devices, the properties for the Cisco Catalyst 6000 series WS-SVC-FWM-1 firewall modules are displayed incorrectly in Cisco ANA NetworkVision physical inventory.
None
3.7
Restore BOS Shell user
The BOS UNIX user is not available in Cisco ANA 3.7.
As user root:
1.
2.
bos:x:1310:104:Bos Admin:/export/home/ana3 7:/export/home/ana37/Ma in/bosconfig/bos_shell_ scripts/run.cshWhen entering this line, make sure that:
–
–
3.
pwconvpasswd bosAs a Cisco ANA user:
1.
2.
#!/bin/tcsh -m ~/.cshrc3.
3.7
Cisco GSR device: Configuring an EtherChannel removes the node from logical inventory and does not update the DC
If you change the EtherChannel configuration on a Cisco GSR device, the EtherChannel node is:
•
•
None
3.7
Cisco ME 3400 device flows do not support blocking between ENI ports
Cisco ME3400 devices support:
•
–
–
–
•
–
–
When the Cisco ME 3400 device is in Isolated mode, it is required to block flows between two UNI interfaces or two ENI interfaces.
With Cisco ANA 3.7, Cisco ME 3400 devices block flows only for UNIs.
None
3.7
SONET: 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 a Cisco CRS device with Cisco IOS XR 3.9.0, the script fails.
This situation occurs for devices with SONET controllers.
None
3.7
Cloud: Cisco ANA PathTracer does not open while links are connected via a cloud
Cisco ANA PathTracer fails to open when links to customer edge (CE) devices are connected via a cloud, such as CE< > Cloud < > CE.
None
3.7
SBC call policy sets and blacklists are not modeled for Cisco ASR 1000 devices
When a Cisco ASR 1000 device is configured for a call policy set or blacklist, the properties are not modeled in Cisco ANA.
None
3.7
Configure continuity check fails due to wrong command used for Cisco 3750 device
The Configure CFM Continuity Check activation script fails on Cisco 3750 and Cisco 3400ME devices.
None
3.7
Cisco CRS SDR VNEs do not map correct card slots to devices
The slot numbers of modules for Cisco CSR secure domain routers (SDRs) are incorrect in Cisco ANA NetworkVision physical inventory.
None
3.7
Cisco GSR IOS Devices: SPA-4XOC3-POS-V2 ports are wrong
Cisco ANA does not display all pluggable ports under SPA-4XOC3-POS-V2 modules in Cisco GSR IOS devices.
None
3.7
Cisco ANA 3.7 Migration: Old tab alarm filters cannot open
The Cisco ANA EventVision filter options that were available in Cisco ANA 3.6.x are not available after migrating to Cisco ANA 3.7.
None
3.7
ExceptionInInitializerError when opening two Cisco ANA Workflow Editor sessions simultaneously
If you open the Cisco ANA Workflow Editor on your system and then launch Cisco ANA Workflow Editor again on the same system, the following errors are displayed:
"Unable to initialize studio:java.lang.ExceptionInInitializerError"
"java.lang.NoClassDefFoundError. This application will be closed"
This situation occurs whether you connect to the same gateway or a different gateway when you launch Cisco ANA Workflow Editor the second time.
Close the open instance of Cisco ANA Workflow Editor and then launch it again.
3.7
Removing a ticket less than seven minutes after its creation can cause problems
If you remove a ticket from the Cisco ANA GUI within seven minutes of its creation, events that are caused by the ticket might not find it as the root cause. As a result, they cannot correlate to it.
Instead of correlating to the original ticket, the newer events open tickets with their own descriptions.
This situation occurs because ticket creation can take up to seven minutes after event creation.
None
3.7
SBC script commands are not supported in RLS5 image
Errors are generated if you run the following scripts:
•
•
•
•
•
This situation occurs when using RP1 and RP2 images of RLS5 on Cisco ASR 1000 series devices.
None
3.7
Cisco GSR XR device discovery and modeling take more than an hour
When initially loading a VNE for a Cisco GSR IOS XR device with a large configuration, the discovery and modeling take a while to complete.
None
3.7
Cannot edit or define a business tag for a physical subinterface
In Cisco ANA NetworkVision, you cannot define business tags on subinterfaces under a port.
In logical inventory, select the required IP interface or VRF and add a business tag.
The tag will be displayed appropriately in the IP Interfaces table or VRFs table, but not in the Subinterfaces table in physical inventory.
3.7
SSH with Cisco ASR 9000 series devices causing 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 do not need to do anything about the message.
None
3.7
Cisco ANA EventVision accessible to "Viewer" role
The Cisco ANA EventVision application is available to all user roles.
None
3.7
Missing ports for PA-MC-2E1-120 card on Cisco 7200 device
Cisco ANA NetworkVision does not model ports for PA-MC-2E1 modules that are installed in Cisco 7200 devices.
None
3.7
ANA 3.7 Migration: Cisco ANA 3.6 cannot be uninstalled after Cisco ANA 3.7 migration
You cannot uninstall Cisco ANA 3.6 after migrating to Cisco ANA 3.7.
Enter the following commands to delete the Cisco ANA 3.6 pkg files:
cd /var/sadm/pkg/rm -rf sheer-dna-baserm -rf sheer-dna-user3.7
Cisco ANA PathTracer starting view shows physical links and not aggregation links
If you start a path trace from an aggregation link, Cisco ANA PathTracer displays the physical link but not the aggregation link in the multipath window.
The aggregation link is displayed correctly in the Cisco ANA PathTracer single-path window.
None
3.7
ATM topology is not discovered
When a device is configured with ATM interfaces, the ATM topology is not discovered even though the topology exists.
The ATM attributes and properties are displayed in the logical and physical inventories in Cisco ANA NetworkVision. However, the ATM topology is not displayed in the map view.
None
3.7
Cisco ANA PathTracer end options do not work from a VRF entity in the routing table
If you launch a path trace from a VRF by using the following steps, the options for ending the path trace do not work:
1.
2.
3.
4.
None
3.7
Cisco ANA 3.7 Migration: Devices go to Unreachable status after rollback
If you successfully migrate to Cisco ANA 3.7 and then roll back to the previous version, the following occur:
•
•
Delete and add the VNE again so that the device returns to Normal status.
3.7
Cisco ANA 3.7 Migration: In Cisco ANA EventVision, many tickets cannot be force-cleared in the Ticket tab
After migrating to Cisco ANA 3.7, if you force a migrated ticket to clear in Cisco ANA EventVision in the Ticket tab, the ticket severity is not updated in the GUI.
In Cisco ANA EventVision, close and reopen the Ticket tab.
3.7
Few MST entries missing from the logical inventory of Viking device
When a Viking device contains a large number of STP configurations, the following can occur:
•
•
This situation occurs because the XML iterator splits the data in a non-uniform way.
Turn off XML iteration by entering the following command:
xml agent tty iteration offNote
3.7
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
NetworkVlanDiscoveryPlugin: Exception upon AVM 11 loading
The NetworkVlanDicoveryPlugin displays an error when AVM 11 loads.
This message is not serious and can be ignored.
None
3.7
Slot numbering of power supply and fan is incorrect
In Cisco ANA NetworkVision, the numbers shown in the content pane for the fan and power supply are incorrect. For example, if the navigation pane lists a fan, the content pane contains a random slot number for that fan, such as Slot 202. This also occurs for power supplies.
Use the slot number given in the physical inventory navigation pane.
3.7
Cisco 7204 VXR device is missing ports under slot 4
Cisco ANA NetworkVision does not model ports for PA-8E1/120 modules in Cisco 7204 VXR devices in physical inventory.
None
3.7
Several event tables reside in single partition after migration from Cisco ANA 3.6.x to Cisco ANA 3.7
During data fault migration from Cisco ANA 3.6.x to Cisco ANA 3.7, migrated data of the following tables reside in a single database partition:
•
•
•
•
•
•
•
As a result, you might observe performance degradation while browsing data in Cisco ANA EventVision or generating reports.
This situation applies only to Cisco ANA 3.6.x fault data that is migrated to Cisco ANA 3.7.
By default, after 14 days of normal system operation, this problem no longer exists.
None
3.7
Channelization not modeled for Cisco IOS XR device
If a Cisco GSR XR device running Cisco IOS XR 3.4.1 is configured for channelization, the channelization properties are not modeled in Cisco ANA NetworkVision physical inventory under the relevant ports.
None
3.7
Newly created AVMs are not monitored until the Cisco ANA gateway is restarted
When you add a new AVM, it is not reflected in the graphs until you restart the system.
To activate graphs for a newly added unit, run the following scripts from ..Main/scripts/monitoring:
•
•
•
3.7
SSL Exception: Unsupported SSL v2.0 ClientHello is displayed many times
An SSL exception: Unsupported SSL v2.0 ClientHello appears frequently.
This message does not harm the system and can be ignored.
None
3.7
For Cisco Viking devices, TE FRR status is not updated in the next interval
Occasionally, the Traffic Engineering (TE) Fast Reroute (FRR) status of the MPLS TE tunnel is not updated immediately after the status has been modified on Cisco Viking devices. Instead, the status is updated after two or three polling cycles.
Do either of the following:
•
•
3.7
Dual port not seen in Cisco ANA
When a Small Form-Factor Pluggable (SFP) port is inserted into a Cisco 3800 device, the dual port is not displayed in Cisco ANA NetworkVision physical inventory.
None
3.7
BGP and BFD traps and syslogs are not generated by SRE image on Cisco 7600 devices
When a Cisco 7600 device loaded with the SRE image is managed in Cisco ANA, BGP traps and BFD syslogs are not generated from the device.
None
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
VNE physical inventory does not model Cisco 7206 VXR devices
Cisco ANA NetworkVision does not model physical inventory for Cisco 7200 devices that are running the SP services image of Cisco IOS versions 12.2(33) SRC, 12.2(33) SRC3, and 12.2(33) SRD1.
Software images other than the SP services images (such as IP Services and Advanced Services images) do not exhibit this behavior.
None
3.7
Cisco ANA does not set transceiver-related properties for Cisco Catalyst 4500 and 4900 devices
Cisco ANA displays incorrect PIDs for transceivers for Cisco Catalyst 4500 and 4900 devices.
None
3.7
Event source of any TE Tunnel trap is linked to IP Interfaces tab
In Cisco ANA EventVision, if you click the TE tunnel for any event that has an MPLS TE tunnel as an alarm source, you are linked to the TE tunnel in Cisco ANA NetworkVision logical inventory (Logical Inventory > Routing Entity > IP Interfaces tab) instead of the TE tunnel in the TE Tunnels branch.
Manually navigate to the TE tunnel by choosing Logical Inventory > Traffic Engineering Tunnels > TE-tunnel.
3.7
Cisco ANA does not set PIDs correctly for transceivers on SUP in Cisco 7600 devices
Cisco ANA does not display PIDs correctly for transceivers on supervisor engines (Sups) that are compatible with Cisco 7600 devices.
Examples of incorrect PIDs include:
•
•
None
3.7
REP topology is not discovered
Occasionally, when starting Cisco ANA, physical links are not discovered by REP.
Restart the two VNEs that are supposed to be connected.
3.7
POS port is not modeled under PA-POS-10C3 module for Cisco 7200 devices
Cisco ANA does not model POS ports on Cisco PA-POS-1OC3 modules for Cisco 7206 VXR devices running Cisco IOS 12.2(31)SB11.
None
3.7
For Cisco 1800 devices, some properties are missing for modules
The following information is not displayed for Cisco 1800 series devices in Cisco ANA NetworkVision:
•
•
•
•
This situation occurs for Cisco 1800 devices running Cisco IOS 12.4(24)T.
None
3.7
For Cisco 2800 devices, junk values are returned in tree view
Meaningless values are displayed in Cisco ANA NetworkVision physical inventory for Cisco 2800 series devices running Cisco IOS 12.4(24)T.
None
3.7
On Cisco 3800 devices, HWIC-1GE-SFP ports are not modeled correctly
Cisco ANA does not model ports correctly for Cisco HWIC-1GE-SFP modules in Cisco 3800 devices.
None
3.7
Dual ports are not modeled properly
If a Cisco 7200 series device running Cisco IOS 12.4(20)T contains dual ports, the port that appears first in the entity MIB is the one that is modeled in Cisco ANA. This occurs whether the port listed first is active or inactive.
None
3.7
Dropped packets on port alarm does not show the right port number
The alarm "Dropped packets on port" does not show the correct port number in the Description field.
None
3.6.7
Cisco ANA 3.6.7: No backups done
If you attempt to back up Cisco ANA 3.6.7, Permission Denied errors are displayed for Oracle *.trc files.
None
3.6.7
Q-in-Q is not modeled in Cisco GSR XR 3.8.2
Subinterfaces for Cisco GSR devices running Cisco IOS XR 3.8.2 software are not displayed in the Subinterfaces table in Cisco ANA NetworkVision physical inventory.
None
3.6.7
Cisco ANA 3.6.7 Registry backup issue
Cisco ANA 3.6.7 backup does not work. This situation occurs because the registry.jar file is not created after running the backup command.
None
3.6.7
Search function in Cisco ANA Registry Editor is not working
The Search function in the Cisco ANA Registry Editor tool does not work.
None
3.6.7
Port is not displayed in the inventory with AToM subinterfaces
If Any Transport over MPLS (AToM) circuits are configured on outgoing subinterfaces, the field port is not displayed in Cisco ANA NetworkVision logical inventory (Logical Inventory > Pseudowires).
None
3.6.7
Events cannot be collected when there is a clean install of Cisco ANA 3.6.7
Cisco ANA does not collect any events upon a clean install of Cisco ANA 3.6.7.
A clean install refers to installing Cisco ANA 3.6.7 on Cisco ANA 3.6, instead of on an intermediate release, such as Cisco ANA 3.6.5.
None
3.6.7
10-Gigabit Transceiver Port Container names are incorrect
In Cisco ANA NetworkVision physical inventory, the names for 10-Gigabit Transceiver Port Containers are incorrect.
The name should include the name of the interface and an additional description, such as TenGigabitEthernet13/4 - Missing pluggable port.
None
3.6.7
Important TLS/SSL Security Update
An industry-wide vulnerability exists in the Transport Layer Security (TLS) protocol that could impact any Cisco product that uses any version of TLS and SSL.
This vulnerability exists in the way in which the protocol handles session renegotiation and exposes users to a potential man-in-the-middle attack.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20091109-tls.shtml.
See the advisory at http://www.cisco.com/warp/public/707/cisco-sa-20091109-tls.shtml.
3.6.7
During Cisco ANA 3.6.6 to Cisco ANA 3.6.7 migration, maintenance link data is erased
During an upgrade from Cisco ANA 3.6.6 to Cisco ANA 3.6.7, data related to the maintenance link feature is erased.
None
3.6.7
LLDP logical inventory is not updated
If you have two Link Layer Discovery Protocol (LLDP) links (that is, two ports on a device configured with LLDP) and you switch them, thereby crossing the links, the information is not reflected in logical inventory, and the links in the topology are incorrect.
Enter the following command on the device:
run clear lldp table
3.6.7
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 configuration 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
Junk characters are included in physical model name
The product identifier (PID) is not displayed correctly for Cisco WIC-2T modules in Cisco ANA.
This situation occurs with devices running Cisco IOS software versions 12.4(22)T and 12.4(24)T.
None
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).
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
No connection from the GRE DC to the underline IP Interface
GRE tunnel down alarms do not correlate to any other alarms. This situation occurs because Cisco ANA does not know the destination IP address of GRE tunnels.
None
3.6.7
Subinterface table is not updated on notifications
In Cisco ANA NetworkVision, if the interface properties window is open and changes occur on the subinterface, the subinterface properties are not updated in the window.
Select another item in logical inventory and return to the interface properties window.
3.6.7
Part IDs are incorrect for pluggable Cisco 1000BaseSX modules
In Cisco ANA NetworkVision, the Part ID of SFP type GLC-SX-MM is incorrectly displayed as SFP-GE-S.
None
3.6.7
After adding LAG topology to an existing device, the map is not updated
If you remove and add LAG topology to devices, the map in Cisco ANA NetworkVision is not updated.
For example, LAG topology is not updated if you do the following:
1.
2.
-interface GigabitEthernet1/3no channel-group 1In Cisco ANA NetworkVision, the LAG topology is deleted from the link.
3.
The map does not reflect the addition of LAG.
Clear topology persistency and then stop and restart the VNE.
3.6.7
The cmpctl script does not always return an error message for illegal input
If you enter the cmpctl command with its options partially typed, no error message is displayed.
To ensure that cmpctl command options are fully and correctly typed, enter command alone (cmpctl) to view the cmpctl manual.
3.6.7
Power supply properties are missing in physical inventory
Cisco ANA NetworkVision does not display the following properties for standard and nonintelligent power supply modules in Cisco GSR IOS devices:
•
•
•
None
3.6.7
VLAN and bridge information is missing from Cisco ANA PathTracer over an Ethernet cloud
Cisco ANA PathTracer Layer 2 does not display VLAN or bridge information when crossing an Ethernet cloud.
None
3.6.7
Alarm Ticket: Couldn't be found message displayed if you attempt to remove tickets
In Cisco ANA NetworkVision, when you attempt to clear and remove all tickets, some tickets might remain.
If you attempt to remove these remaining tickets, a Java exception is displayed. This error states that the alarm tickets could not be found even though you can open and view them.
None
3.6.6
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
Attributes such as clocking, framing, loopback, and scrambling are not populated
Cisco ANA does not display loopback, scrambling, clocking, or framing details for Cisco 7200 devices running Cisco IOS version 12.2(33)SRD1.
None
3.6.6
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
Card Down ticket is not cleared
A Card Down ticket is not cleared when the card is inserted in the device. This situation occurs when you:
1.
2.
3.
4.
The Card Down ticket is generated in the Tickets Pane.
5.
Even after several minutes, the Card Down ticket is not cleared.
None
3.6.6
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
Physical port is not getting modeled for Cat4503-E
FastEthernet1 ports are not modeled for Cisco Catalyst 4503-E devices in Cisco ANA NetworkVision physical inventory.
None
3.6.6
Fan tray for Cisco CRS device shows unknown status
For Cisco CRS-1 devices running Cisco IOS XR 3.7.1 software, Cisco ANA NetworkVision physical inventory displays the fan tray main module with the status OK.
However, it displays the status Unknown for each individual fan tray.
None
3.6.6
Cisco ANA is not able to discover interfaces in inventory when GBIC is missing
For Cisco 4506 devices, Cisco ANA NetworkVision does not discover interfaces in inventory when the Gigabit Interface Converter (GBIC) is missing.
None
3.6.6
Low GUI performance while working with a maximum sized map
While using Cisco ANA NetworkVision, you might experience slow GUI performance while working with a map of the maximum size. The maximum size of a map is defined as containing:
•
•
•
None
3.6.6
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 Reference Guide for details on the supported technologies.
3.6.5
BQL adapter does not raise an error when the BQL command contains invalid data
If you enter the IMO property name is incorrectly while creating a BQL command, the BQL command disregards this property without displaying an error.
None
3.6.5
Clear all ticket does not put the VNE into the green state.
The VNE state remains unchanged (in the orange state) even after the ticket is cleared and removed.
None
3.6.5
Few VNEs stay in maintenance after gateway returns to up
When the connection between the gateway and a unit is broken, all VNEs on the unit change to maintenance state. When the connection is restored, some VNEs continue to remain in maintenance state.
Manually start the VNEs that remain in maintenance state.
3.6.5
Error in Registry editor
Error in Registry editor.
None
3.6.5
Cisco ANA raises MPLS black hole events for destination devices with VRFLite
Cisco ANA generates incorrect MPLS black hole events on the PE when the destination device is a VRFlite CE.
Disable MPLS black hole checking.
3.6.4
Failed to model Cisco GSR devices running Cisco IOS XR inventory from recordings
Telnet output of recordings for Cisco GSR devices running Cisco IOS XR software appears to be corrupted because of unexpected characters.
As a result, the recordings cannot be used for device modeling in Cisco ANA.
None
3.6.4
LDP protocol type received in Cisco ANA NetworkVision is not followed by expedite
The wrong Label Distribution Protocol (LDP) status appears in inventory.
This occurs if you complete the following steps:
1.
2.
3.
4.
None
3.6.4
Cisco 6500 VSS Module status shown as OUT in active switch
When Cisco 6500 VSS systems are issued the redundancy force-switchover command, the Module status is shown as OUT in the active switch.
None
3.6.3
Cisco 6500 VSS Interface operational state is down in active switch
When Cisco 6500 VSS systems are issued the redundancy force-switchover command, the Interface operational state goes down in the active switch.
None
3.6.3
Cisco 6500 Virtual Switching System (VSS) Shelf out and Card out alarms are generated when the redundancy force-switchover command is issued
When Cisco 6500 VSS systems are issued the redundancy force-switchover command, the force-switchover occurs and the active switch is moved to Stand-By state and vice versa.
In the Cisco ANA GUI, the Shelf Out and Card Out alarms are generated.
None
3.6.3
Improper modeling of Power and Fan modules of 6500VSS
If you add a VNE for a Cisco 6500 device and then, in Cisco ANA NetworkVision, choose Physical Inventor > Chassis > Shelf > Module, the power and fan modules for Chassis 1 are not displayed. However, they are displayed for Chassis 2.
None
3.5.2
Resolved Caveats - Cisco ANA 3.7
Table 16 identifies the caveats resolved in Cisco ANA 3.7.
Related Documentation
User Guides
Cisco Active Network Abstraction 3.7 Documentation Guide
Cisco Active Network Abstraction 3.7 User Guide
Cisco Active Network Abstraction 3.7 Theory of Operations Guide
Cisco Active Network Abstraction 3.7 Reference Guide
Administrator Guides
Cisco Active Network Abstraction 3.7 Installation Guide
Cisco Active Network Abstraction 3.7 Administrator User Guide
Developer Guides
Cisco Active Network Abstraction 3.7 Customization User Guide
Cisco Active Network Abstraction Integration Developer Guide
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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
