Table Of Contents
Cisco Active Network Abstraction 3.6.7
Release NotesNew Features in Cisco ANA 3.6.7
Cisco IOS V1 Trap Support Added
Cisco IOS V2 Trap Support Added
Cisco IOS XR V1 Trap Support Added
Cisco IOS XR V2 Trap Support Added
Cisco MIB2 V1 Trap Support Added
Cisco MIB2 V2 Trap Support Added
Cisco IOS Syslog Support Added
Cisco IOS XR Syslog Support Added
Cisco ANA 3.6.0 Postinstallation Script
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
Workflow Editor and Floating User Licenses
Resolved Caveats - Cisco ANA 3.6.7
Obtaining Documentation and Submitting a Service Request
Cisco Active Network Abstraction 3.6.7
Release Notes
Revised: November 18, 2009, OL-19645-02
These release notes support the release of Cisco Active Network Abstraction (Cisco ANA) 3.6.7.
Note
See Cisco.com for the most up-to-date version of the Cisco Active Network Abstraction 3.6.7 Release Notes.
Contents
This document includes the following topics:
•
New Features in Cisco ANA 3.6.7
•
Open Caveats in Cisco ANA 3.x
•
Resolved Caveats - Cisco ANA 3.6.7
•
Obtaining Documentation and Submitting a Service Request
Introduction
Cisco ANA 3.6 is a carrier-class, multiple-vendor network and service management platform providing the flexibility for carriers and service providers to efficiently respond to the constant market demand for new, reliable, and more sophisticated services.
Cisco ANA 3.6 identifies network characteristics and builds a real-time virtual model of the network, serving as a live information base for value-added tools and applications capable of seamless integration within a customer's existing Operations Support System (OSS) environment.
Cisco ANA 3.6 provides a unified solution for diverse network environments and applications. Implemented with a highly scalable and distributed architecture, Cisco ANA 3.6 offers:
•
Integrated and configurable network resource management
•
Network and service discovery
•
Network and service fault isolation
•
A highly flexible service activation engine
These integrated applications enable correlated management of global-scale networks supporting millions of subscribers and customers.
Cisco ANA 3.6 is a unified, fully integrated solution that offers:
•
Multiple-vendor device support
•
Multiple-technology coverage: IP, Layer 2 and Layer 3 VPN, xDSL, ATM, Frame Relay, Gigabit Ethernet, Ethernet, 802.1Q, Inter-Switch Link (ISL), QinQ VLAN tag (QinQ), Spanning Tree Protocol (STP), Layer 2 Tunneling Protocol (L2TP), and routing protocols such as Border Gateway Protocol (BGP)
•
Integrated device, network, and service management functionality
•
Open interfaces for integration with multiple OSS/Business Support System (BSS) applications
Cisco ANA 3.6 dynamically discovers and identifies basic network components, while obtaining end-to-end visibility of the network resources, connections, and dependencies, enabling Cisco ANA 3.6 to manage and analyze network behavior. Cisco ANA 3.6 builds its end-to-end understanding of the network structure and interoperability across vendors, technologies, and network layers into a customer-specific virtual network model for each installation.
The virtual network model within Cisco ANA 3.6 is an always maintained, up-to-date, enabling, and powerful device, network, and service management function, including:
•
Configurable Device Manager: Basic resource management features for multiple-vendor devices
•
Network and Service Discovery: Physical and logical discovery with multiple-layer network and service connectivity
•
Network and Service Fault Isolation: End-to-end, topology-based fault isolation, monitoring, and root cause analysis
•
Service Activation
•
A series of product options including Northbound APIs, Path Tracing, and client UIs
New Features in Cisco ANA 3.6.7
The following new features were added in Cisco ANA 3.6.7:
•
New Java version Sun JDK 1.4.2_19 included in the Cisco ANA server installation
•
Support for the Sun SPARC 64 VI-based processor as a Cisco ANA gateway system.
•
Support for Windows Vista.
•
Modeling, flow, and fault support for Carrier Ethernet for:
–
Cisco ME 3400 UNI-ENI VLANs
–
Ethernet flow points
–
Ethernet over MPLS (EoMPLS) tunnels
–
Link Layer Discovery Protocol
–
MAC-based destination addresses in Cisco ANA PathTracer
–
Virtual Private LAN Service
–
VLANs
–
VLAN overlays in Cisco ANA NetworkVision map view
–
VLAN tagged interfaces (Q-in-Q)
–
VLAN Trunk Protocol
•
Modeling, flow, and fault support for Mobile Transport over Packet (MToP) services for:
–
Inverse Multiplexing over ATM (IMA) groups
–
Time-division multiplexing (TDM)
–
Structure-Agnostic TDM over Packet (SAToP)
–
Circuit Emulation Services over PSN (CESoPSN)
–
ATM virtual connection cross-connects
–
MPLS pseudowire over generic routing encapsulation (GRE)
–
Network clocking service
–
Pseudowire clock recovery
–
Circuit emulation (CEM) interfaces and virtual CEM interfaces
–
CEM groups
•
Support for Session Border Controller (SBC) system-defined commands:
–
To configure Signaling Border Elements (SBEs) for adjacency properties, SIP profiles, QoS properties, CAC policy properties, and Blacklist policy properties.
–
To configure Data Border Elements (DBE) components for media properties.
–
For on-demand, real-time SBC statistics data polling.
–
To display call rates, call statistics, media statistics, and H.248 statistics.
•
Support for the IP over Dense Wavelength-Division Multiplexing (IPoDWDM) system-defined commands to configure Dense Wavelength-Division Multiplexing (DWDM) and SONET controller attributes.
Go to the Cisco ANA Technology Center, which is part of the Cisco Developer Community, to download these commands:
http://developer.cisco.com/web/ana/home
•
Enhancements in the Command Builder GUI: While creating a new command you can:
–
Specify if the parameters are either mandatory or optional along with a description using the Required and Tooltip fields in the Add/Edit User Argument for Command dialog box.
–
Group the input parameters using the Tab Pages dialog box.
•
Support for using an external Lightweight Directory Access Protocol (LDAP) server to perform user authentication. For more information, see the Cisco Active Network Abstraction 3.6.7 Administrator User Guide.
•
Ability to launch external applications from managed network elements and its attributes from the Cisco ANA NetworkVision user interface. For more information, see the Cisco Active Network Abstraction 3.6.7 Customization User Guide.
•
Support for the additional network element types identified in Table 1.
•
Support for the additional modules identified in Table 2.
•
Support for the additional modules for Cisco 7600 Series routers identified in Table 3.
•
Support for the additional software versions identified in Table 4.
•
New or enhanced service alarms, trap support, and syslog support, identified in the following sections:
•
Various bug resolutions. For details, see Resolved Caveats - Cisco ANA 3.6.7.
•
The following are the documentation enhancements:
–
A new deliverable, the Cisco Active Network Abstraction Integration Developer Guide. This guide describes how to use the Cisco Active Network Abstraction (Cisco ANA) integration interface. This interface (API) consists of simple XML-based query language, called the ANA Broadband Query Language (BQL), which provides programmatic access to the entire ANA information model, as well as other ANA key features and functions.
–
The information from the Cisco Active Network Abstraction 3.6.6 MPLS User Guide has been incorporated into the Cisco Active Network Abstraction 3.6.7 User Guide.
–
Information on the VPN Leak alarm has been removed from the documentation. The VPN Leak alarm was previously documented in the Cisco Active Network Abstraction 3.6.6 MPLS User Guide.
–
The information on the Drools rules engine that was previously in the Cisco Active Network Administration 3.6.6 Administrator Guide has been incorporated into the Cisco Active Network Abstraction 3.6.7 Customization User Guide.
New Service Alarms
Table 5 describes the service alarms that were added in Cisco ANA 3.6.7.
Enhanced Service Alarm
In previous releases, Cisco ANA generated the Layer 2 Tunnel Down alarm only when an Layer 2 tunnel changed its operational state to down. Beginning with Cisco ANA 3.6.7, Cisco ANA also generates a Layer 2 Tunnel Down alarm if it detects that the Layer 2 tunnel is down when Cisco ANA begins to manage it.
New Trap Support
The following sections identify the trap support added in Cisco ANA 3.6.7:
•
Cisco IOS V1 Trap Support Added
•
Cisco IOS V2 Trap Support Added
•
Cisco IOS XR V1 Trap Support Added
•
Cisco IOS XR V2 Trap Support Added
•
Cisco MIB2 V1 Trap Support Added
•
Cisco MIB2 V2 Trap Support Added
Cisco IOS V1 Trap Support Added
Cisco IOS V2 Trap Support Added
Cisco IOS XR V1 Trap Support Added
Cisco IOS XR V2 Trap Support Added
Cisco MIB2 V1 Trap Support Added
Cisco MIB2 V2 Trap Support Added
New Syslog Support
The following sections identify the syslog support added in Cisco ANA 3.6.7:
•
Cisco IOS Syslog Support Added
•
Cisco IOS XR Syslog Support Added
Cisco IOS Syslog Support Added
Cisco IOS XR Syslog Support Added
IMO Model API Changes
The following topics identify the changes that were made in the Information Model Object (IMO) model API between Cisco ANA 3.6.6 and Cisco ANA 3.6.7:
No IMOs were removed in Cisco ANA 3.6.7.
IMOs Added
IMOs Changed
Important Notes
This section includes the following topics:
•
Solaris Services and Components
•
Device and Software-Specific Limitations
•
JDK DST Timezone Update Tool for Cisco ANA
•
Configuring Database Storage (Redo Logs)
Installation Notes
This section includes the following topics:
•
Cisco ANA 3.6.0 Postinstallation Script
For installation procedures, see the Cisco Active Network Abstraction 3.6.7 Installation Guide.
Cisco ANA 3.6.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.6.7 installation script.
New Java Version
Cisco ANA 3.6.7 provides Java version 1.4_19 on the product DVD, an upgrade from Java version 1.4_13.
After you install the Cisco ANA gateway and unit software, you must manually update the Java version to 1.4_19 on both the gateway and the unit. For more information, see the Cisco Active Network Abstraction 3.6.7 Installation Guide.
Upgrading to Cisco ANA 3.6.7
Before Upgrading to Cisco ANA 3.6.7
Cisco ANA 3.6.7 introduces IMO changes as described in IMO Model API Changes. Review these changes before upgrading to Cisco ANA 3.6.7 so that you know how any integration using the Cisco ANA North Bound Interface (NBI) is affected. We also recommend that you review the Best Practices for Integration BQL Parsing chapter in the Cisco Active Network Abstraction Customization User Guide to ensure that the integration is not affected by these changes.
Time Required for Upgrade
Upgrading to Cisco ANA 3.6.7 from an earlier version of Cisco ANA could take a long time on Cisco ANA servers that have a large number of alarms in the database. For example, on an enterprise-level server with 1 million alarms in the database, the upgrade might take approximately 90 minutes. The upgrade time is linear to the events volume in the database. Specifically, the upgrade time from Cisco 3.6.6 to Cisco 3.6.7 can be double the time. Consult Cisco Advanced Services to evaluate the upgrade time in your environment. If, in your case, the amount of alarms is greater than 1 million alarms altogether, we strongly recommend that you contact Cisco TAC for a consultation before you begin the upgrade process. This also affects downgrading from Cisco ANA 3.6.7 to earlier versions of Cisco ANA. See CSCta10859 for more details.
Cisco ANA 3.6.7 Post-Upgrade Migration Tasks
Cisco ANA 3.6.7 introduces a change to the structure of link OIDs. If you are upgrading to Cisco ANA 3.6.7 from an earlier version of Cisco ANA, the GUI clients:
•
Will not display working hyperlinks in the Location field for any link events or link tickets that were created before the upgrade.
•
Will not correlate clearing events for any link events or link tickets that were created before the upgrade.
•
Will not display business tags that were associated with links.
If these changes affect you, please contact the Cisco Technical Assistance Center.
Cisco ANA 3.6.0 Postinstallation Script
Cisco ANA provides a postinstallation script that fixes installation problems associated with Oracle 10G software and Cisco ANA schemas.
This script is to be used only if you are installing Cisco ANA 3.6.0 for the first time. For detailed instructions on using this script, see the gateway installation chapter in the Cisco Active Network Abstraction 3.6.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.
Generating SSH Keys
You must generate Secure Shell Protocol (SSH) keys to ensure synchronization between the gateway and units. SSH keys are generated on the gateway and propagated to all the units in the setup. For more information, see the Cisco Active Network Abstraction 3.6.7 Installation Guide.
Backward Compatibility
Note the following with regard to backward compatibility of Cisco ANA 3.6.7 with existing installations of Cisco ANA 3.6:
•
Before installing Cisco ANA 3.6.7, review the Best Practices for Integration BQL Parsing chapter in the Cisco Active Network Abstraction 3.6.7 Customization User Guide to ensure that the integration is not affected.
•
All system configuration changes made to the registry are maintained.
Solaris 10
Note
When installing a Solaris 10 patch cluster, carefully follow the instructions in the readme file that comes with the Sun patch cluster, as the readme includes procedures that are important for the successful installation of the patch.
On Sun servers, the recommended operating system for Cisco ANA 3.6.7 is Solaris 10. Cisco ANA 3.6.7 is compatible with the latest patch release as published by Sun on January 18, 2008 (cluster patch ID Generic_120011-14). For more information, see the Cisco Active Network Abstraction 3.6.7 Installation Guide.
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.6.7 Installation Guide.
Using Cisco CRS-1 VNEs
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 16 describes caveats related to specific devices or versions of software.
Table 16 Device- and Software-Specific Limitations
Device Family Element Affected Software Version DescriptionCisco 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.
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:
•
03.08.00.017i.BASE
•
03.06.03.002i.BASE
•
03.07.02.014i.BASE
•
03.09.00.004i.BASE
•
03.09.00.013i.BASE
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.
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.
Supported Schemes
Cisco ANA supports two schemes:
•
Product—The default scheme used for all device types supported in this release, except for the Cisco CRS-1, Cisco XR 12000 series, Cisco ASR 1000, Cisco ASR 9000, Cisco 3750ME, and the Juniper M-Series.
•
ipcore—The scheme used only for routers serving as Provider (P) or Provider Edge (PE) devices.
For supported device type and schemes table, see Cisco Active Network Abstraction 3.6.7 Administrator Guide.
JDK DST Timezone Update Tool for Cisco ANA
Cisco ANA comes with Java Development Kit (JDK) 1.4.2_13. It is possible that the daylight saving time (DST) at your location has changed since JDK 1.4.2_13 was released. If this is true for 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:
1.
Download the latest version of the JDK US DST Timezone Update Tool from the Java.sun.com website. The current download URL is:
http://java.sun.com/javase/downloads/index.jsp
2.
Extract the tzupdater.jar file from the downloaded zip file and copy it to /tmp on each gateway and unit.
3.
Perform the following steps on each gateway and unit:
a.
Log into the machine as user sheer.
b.
Stop all AVM processes.
c.
Change to the /tmp directory.
d.
Execute the following command:
java -jar tzupdater.jar -u -v4.
Restart the Cisco ANA system.
Configuring Database Storage (Redo Logs)
If you are already running Cisco ANA 3.6, change the Oracle installation to write the logs on a different disk. For more information, see the Cisco Active Network Abstraction 3.6.7 Installation Guide.
Online Help
The online help for Cisco ANA 3.6.7 has been tested using the following browsers:
•
Microsoft Internet Explorer version 8
•
Mozilla version 3.5.3
•
Avant Browser version 11.7
Note
The online help was not updated for Cisco ANA 3.6.7. The most current product documentation for Cisco ANA 3.6.7 is available on Cisco.com at:
http://www.cisco.com/en/US/products/ps6776/tsd_products_support_series_home.html
Limitations and Restrictions
This section includes the following limitations and restrictions:
•
OSPF
•
HSRP
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.
Links in Maintenance Mode
When a link is placed in maintenance mode, the severity property of the physical layer link remains in the same state as it was before the link was placed in maintenance mode. The link property changes for other layers except for physical layer. You can view the link state in the maps displayed in Cisco ANA NetworkVision.
For example: When a fault occurs on a link that is not on maintenance mode. The link turns red. If the operator adds this link to maintenance mode to suppress further alarms. The link continues to remain in red as long as the link is in maintenance mode even though the fault in the physical link is rectified.
Cisco ANA Fault Management
The maximum number of open tickets (other tickets can be correlated to them) for the system is 5000. Although this number is configurable in the registry, we do not recommend increasing it. For a definition of an open ticket, see the Cisco Active Network Abstraction 3.6.7 User Guide. To avoid exceeding the maximum number of open tickets, we recommend that you close the tickets on time.
Note
Changes to the registry should only be carried out with the support of Cisco. For details, contact your Cisco account representative.
A tickets capacity overflow system alarm is generated when the maximum number of open tickets is exceeded. The alarm severity is defined as critical.
Cisco ANA Workflow Editor
The following sections provide information for working with Cisco ANA Workflow Editor:
•
Workflow Editor Template Naming Conventions
•
Workflow Editor and Floating User Licenses
Workflow Editor Template Naming Conventions
Do not include the characters underscore (_) or percent (%) in workflow template names when executing a workflow or referencing a subflow. In template names, these characters act as wildcards and represent the following:
•
_ indicates a single character.
•
% indicates a zero or many characters.
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:
•
The template name WFTLM_MUESTRA.template leads to ambiguity with the WFTLM#MUESTRA.template when they are deployed together.
•
The WFTLM%MUESTRA.template leads to ambiguity with the WFTLM####MUESTRA.template when they are deployed together.
The ambiguity occurs only when templates containing wildcard characters in their names are executed.
Workflow Editor and Floating User Licenses
Users cannot open multiple Cisco ANA workflow sessions from the same PC when they are using the Floating User License.
Carrier Ethernet/MToP
For Cisco ANA 3.6.7, we recommend limiting Carrier Ethernet and MToP support to networks of approximately 350 devices. For Cisco ANA deployment services, contact Cisco Advanced Services.
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.
HSRP
For correlation to work, the path through which HSRP signaling passes must be modeled (must exist) in the system.
ATM Topology Discovery
ATM topology discovery is performed in two phases:
1.
Discovery matches active VCs and VPs on the ATM ports.
2.
Discovery matches the traffic signatures of the VCs and VPs that were identified during the first phase.
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.
Adaptive Polling
Adaptive polling is supported only for Cisco and the Juniper devices.
BGP Neighbors
•
When both IP and VPN capabilities are enabled between BGP neighbors, only the VPN capability state is displayed in the MpBGP neighbors table.
•
To support the BGP fault mechanism, each device must have a unique BGP router ID.
Open Caveats in Cisco ANA 3.x
Table 17 identifies the open caveats in Cisco ANA 3.x.
Table 17 Open Caveats in Cisco ANA 3.x
Identifier Title Impact Workaround ReleaseAfter upgrade, some VNEs are erroneously displayed as unsupported
After upgrading to 3.6.7, Cisco ANA NetworkVision and Cisco ANA EventVision may display some VNEs as unsupported even though they are fully modeled and functioning.
This issue is related only to the upgrade procedure and not the VNE. After the upgrade, the VNE is fully modeled and functional, but is not displayed as such in Cisco ANA NetworkVision or Cisco ANA EventVision.
Perform one of the following:
•
During the migration process, stop the VNE before doing the upgrade. After successfully upgrading, restart the VNE. The AVM should be in the up state.
•
After the upgrade is complete, clear and remove the alarms. The VNE icons will reflect the proper states.
3.6.7
Adding 2K devices to a map fails with an Operation timed out message
If you choose to add 2000 devices to a map, the following error message might be displayed:
Operation timed out while trying to execute command.None
3.6.7
GUI hangs when aggregating or disaggregating 1000 devices in 2000-device map
When using Cisco ANA NetworkVision, you might experience slow GUI performance, or the application might stop, if you aggregate or disaggregate 1000 devices in a map that contains 2000 devices.
None
3.6.7
CRS devices: NetworkVision does not display management IP
The NetworkVision physical inventory does not display the management interface for CRS devices.
None
3.6.7
Soft property publish displays incorrect behavior in the Local column
If you complete the following steps, Cisco ANA Soft Properties Manager displays the incorrect value in the Local column:
1.
Add three VNEs.
2.
Add a soft property to VNE1.
3.
Publish the soft property on VNE1 to all VNEs.
4.
Stop and then restart VNE2 and VNE3.
5.
Right-click VNE2 and choose Management > Soft Properties Management. In the Local column, the value for the published soft property is true.
6.
Add a new soft property to VNE2.
7.
Right-click VNE2 and choose Management > Soft Properties Management. In the Local column, the value for the published soft property is now false.
None
3.6.7
Cisco CRS 8x10GE ports do not show missing Xenpak pluggables
For Cisco CRS devices running Cisco IOS XR software versions lower than 3.9 or 3.8.1, empty containers in Cisco 8x10GE and 160C48 modules are modeled as actual ports instead of missing pluggable ports.
None
3.6.7
Running workflow fails after starting AVM 66
Cisco ANA Manage occasionally indicates that AVM 66 is up even though not all of its services are up.
You might encounter this situation when you deploy a workflow. If the AVM is not up as indicated, the following message is displayed:
The workflow service was not initialized properly.
Wait a few seconds and then deploy the workflow again.
3.6.7
Exporting a soft property using a BQL command results in illegal argument exception
If you export a soft property using a BQL command, an illegal argument exception is displayed.
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
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
Opening a map with many VPNs takes a long time
In Cisco ANA NetworkVision, opening a map with 50 VPNs, 255 links, and 408 sites can take approximately 30 seconds.
None
3.6.7
Wrong slot number for Cisco WS-F6K-PFC3B feature card
In Cisco ANA NetworkVision physical inventory, the slot numbers for Cisco WS-F6K-PFC3B feature cards are incorrect.
None
3.6.7
Cisco ANA PathTracer Layer 2 flow information is missing on Cisco ME 3400 Series devices
In Cisco ANA PathTracer, when a path passes a Cisco ME 3400 device, the device no longer is displayed in the PathTracer window.
None
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 given.
To ensure that cmpctl command options are fully and correctly typed, enter command alone (cmpctl) to view its manual.
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:
•
Both interfaces on Cisco CRS-1 devices are configured as physical interfaces.
•
One interface is configured as a physical interface and the other is configured as a subinterface.
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
Inconsistency between Path and Path Details possibly due to 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 due to LAG.
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 complete the following steps:
1.
Add two devices with a LAG link between them to a map.
2.
Telnet to the devices and remove the LAG from the interfaces. For example:
-interface GigabitEthernet1/3no channel-group 1In Cisco ANA NetworkVision, the LAG topology is deleted from the link.
3.
Telnet again to the device and add the LAG configuration to the interfaces again.
The map does not reflect the addition of LAG.
Clear topology persistency and then stop and restart the VNE.
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
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 rtr traps are configured to be sent to Cisco ANA.
Retrieve the attribute manually from the router in any of the following ways:
•
Use snmp get and snmpwalk commands.
•
Use other tools to retrieve the attribute.
•
Use CLI commands directly on the affected router.
3.6.7
Incorrect association on Cisco CRS devices
On Cisco CRS-1 devices, if DWDM is configured on port 0/0/0/0, the DWDM syslog message is incorrectly associated with a different port.
For example, if DWDM is configured on TenGigE0/0/0/0 on a Cisco CRS device, the syslog message generated from port TenGigE0/0/0/0 is:
%L1-PMENGINE-4-TCA : Port DWDM 0/0/0/0 reports FEC BIT-EC(NE) PM TCA with current value 0, threshold 0 in current 15-min interval windowThe port information 0/0/0/0 is passed to create the key. However, the port layer key is created for MgmtEth0/RP0/CPU0/0 as follows:
# SourceOID : ={[ManagedElement(Key=CRS79)][Ph ysicalRoot][Chassis][Shelf(Shel fNum=0)][Slot(SlotNum=32)][Modu le][Port(PortNumber=MgmtEth0/RP 0/CPU0/0)][PhysicalLayer][Syslo g]}As a result, the syslog message is incorrectly associated with port MgmtEth0/RP0/CPU0/0.
None
3.6.7
Cisco GLC-BX-U module is not modeled in Cisco ANA
Cisco 7600 devices do not return the PID and vendor type values for Cisco GLC-BX-U pluggable ports in SNMP responses. As a result, the pluggable ports are not displayed in Cisco ANA NetworkVision physical inventory.
Instead, under interface properties for the device, the media type for the Cisco GLC-BX-U module is displayed as BX10U. This is the only way to confirm that the Cisco GLC-BX-U is inserted in the device.
None
3.6.7
Deleted VNE appears in Scope properties
In Cisco ANA Manage, if you add a new VNE to a new scope and then delete the VNE, the VNE still appears in the Scope Properties dialog box.
None
3.6.7
When front module is Card Out, the back module is also shown as Card Out in Cisco CRS devices
If you remove a Cisco 20-1GE-FLEX or 42-1GE module from a front slot in a Cisco CRS device, a module from the back also displays a Card Out ticket and the Card Out alarm is issued.
The Card Out tickets are displayed in Cisco ANA EventVision, and the alarm can be viewed in Cisco ANA NetworkVision physical inventory.
This situation occurs on Cisco CRS devices running Cisco IOS XR 3.8.1 software.
None
3.6.7
Local database installation fails if the previous server installation used a remote database
If you install a Cisco ANA gateway server on a Cisco ANA gateway that previously used a remote database, the installation fails.
None
3.6.7
MP-BGP: Notification received twice when BGP process is up
In Cisco ANA NetworkVision, the notification window show two entries for a change in BGP state.
None
3.6.7
STP does not display VLANs when switching from MSTP to PVSTP
If you change the spanning tree configuration from MSTP to PVSTP for a VNE you are viewing in Cisco ANA NetworkVision, the VNE is not refreshed.
Close and then reopen the VNE in Cisco ANA NetworkVision.
3.6.7
Disk capacity thresholds in registry cannot be modified
If you change disk capacity thresholds in the registry, the default values of 80% and 90% are automatically reinstated.
None
3.6.7
Exception in Protocol Handler while setting status for fan and PS
Cisco ANA NetworkVision displays the status Unknown for fans and Power Entry Modules (PEMs) in Cisco GSR devices running Cisco IOS XR software.
None
3.6.7
Error when trying to get a big list of workflows in Cisco ANA Manage
In Cisco ANA Manage, if you attempt to list more than 5000 workflows, the following error is displayed:
ERROR(5142): The Workflow service (AVM66) is not loaded or busy.None
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:
•
CDP is enabled on all interfaces.
•
The link UPE11-TX - port 1/1/2 < > AGG-7604-TX port 3/0/3 exists.
•
AGG-7604-TX port 3/0/3 is configured as follows:
service instance 1 ethernetencapsulation untaggedxconnect 172.255.3.169 999999 encapsulation mpls•
The cross-connect is to AGG-7606-TX.
•
The link AGG-7606-TX port 1/0/2 < > UPE9-TX: port 1/1/2 exists.
•
AGG-7606-TX port 1/0/2 configuration is:
service instance 1 ethernetencapsulation untaggedxconnect 172.255.3.175 999999 encapsulation mplsThe results of this configuration are:
•
Cisco ANA discovers the link UPE9-TX: port 1/1/2 < > UPE11-TX - port 1/1/2 in error.
•
Cisco ANA does not discover the following links:
–
UPE11-TX - port 1/1/2 < > AGG-7604-TX port 3/0/3
–
AGG-7606-TX port 1/0/2 < > UPE9-TX: port 1/1/2
None
3.6.7
SFP-GE-S/ L/ Z not modeled in Cisco ANA for Cisco IOS XR software versions 3.71 and 3.6.3
If a Cisco GSR device is running Cisco IOS XR software lower than version 3.8.1, Cisco SFP-GE-S, SFP-GE- L, and SFP-GE- Z modules are not displayed in Cisco ANA NetworkVision.
None
3.6.7
Bridge without interfaces is not discovered as an empty switching entity (inconsistent)
In Cisco ANA NetworkVision, if you load a VNE associated with a bridge that does not contain interfaces, the switching entity is not displayed in a consistent way.
For example, the switching entity might be displayed in either of the following ways or not displayed at all:
•
Under a network VLAN that is not associated with an Ethernet flow domain.
•
Under a VLAN that is associated with the Ethernet flow domain that other bridges in the same device are associated with.
None
3.6.7
VRF container in VNE inventory disappears when VNE is restarted
In Cisco ANA NetworkVision, the VRF container is not displayed when the VNE is shut down and restarted.
The situation occurs only when the polling cycles of the configuration and the status are lowered to the 30-second minimum.
Use one of the following workarounds:
•
Restart the VNE until the VRF container appears.
•
Raise the polling cycles and restart the VNE.
3.6.7
Gi1/9 port is not modeled on Cisco WS-SUP32-GE-3B 9-port Supervisor Engine 32
One of the fixed ports under the Cisco WS-SUP32-GE-3B 9-port Supervisor Engine 32 module is not modeled in Cisco ANA.
For the Cisco WS-SUP32-GE-3B 9-port Supervisor Engine 32 module, which has both fixed and pluggable ports, entPhysicalParentRelPosition are the same for both one of the fixed ports and a pluggable port container. As a result, the fixed port is not modeled in Cisco ANA.
None
3.6.7
Upgrading from Cisco ANA 3.6.6 to 3.6.7 fails on the initial attempt
If a server is running Cisco ANA 3.6.6 and you attempt to upgrade to Cisco ANA 3.6.7 using the perl ./update.pl -r command, the following message is displayed:
SP2-0310: unable to open file "/export/home/sheer4/Main/scrip ts/patch/ANA3.6.7_db_update_rol lback.sql"Subsequent attempts to upgrade using the same command are successful.
The workaround depends on whether you have already tried to upgrade to Cisco ANA 3.6.7 or not:
•
Before upgrading—Open the ANA3.6.7.jar file and copy the db_rollback.sql script to the ~Main/scripts/patch directory before running update.pl with the -r option.
•
After failing to upgrade—Reenter the following command:
perl ./update.pl -r3.6.7
Cisco VWIC2-1MFT-
G703 module hardware type is incorrectly modeledFor Cisco VWIC2-1MFT-G703 modules in Cisco 2800 routers, Cisco ANA NetworkVision displays the hardware type Wvic-2dsu-E1-G703 instead of cevWvic2dsuE1DiG703.
None
3.6.7
Missing notifications for adding VLAN interfaces
In Cisco ANA NetworkVision, if you remove a VLAN and add it again, the VLAN snapshot is occasionally not updated with the new VLAN interfaces. As a result:
•
Ethernet flow points (EFPs) might not appear in the VLAN map view.
•
The associated VNE displayed in an open Cisco ANA NetworkVision window is not updated with the new interfaces on the bridge.
Restart the VNE.
3.6.7
Module status is displayed as OK for Cisco 10000 Series router at all times
The status of a module in a Cisco 10000 Series router is displayed as OK in Cisco ANA NetworkVision, even if the module is removed from the router.
This situation occurs on Cisco 10000 Series routers running Cisco IOS version 12.2(33)SB1.
None
3.6.7
Card Out alarm is not received and physical inventory is not polled for Cisco GSR XR devices
If a card is removed from a Cisco GSR XR device, the Card Out service alarm is not generated and Cisco ANA NetworkVision does not poll the physical inventory.
None
3.6.7
Cefc-related traps for submodules are associated with main module
In Cisco ANA NetworkVision, when a Card Down or Card Out is performed on submodule 0, the cefc-related traps are associated with the main module instead of the submodule.
This situation occurs for submodule 0 only.
None
3.6.7
Some subcard modeling fails for Cisco GSR-XR devices when status is RESET
Some shared port adapters (SPAs) and line cards in Cisco GSR devices running Cisco IOS XR software are not modeled in Cisco ANA NetworkVision.
This situation occurs in Cisco GSR devices when the SPA status is RESET.
None
3.6.7
Cisco PathTracer fails in the Cisco ANA GUI while crossing (reentering) the same device twice
Cisco ANA PathTracer fails to open when it crosses or enters the same device twice.
None
3.6.7
Duplicated syslogs in Cisco ANA EventVision
Duplicate syslog messages appear in Cisco ANA EventVision.
None
3.6.7
BGP neighbor entries are not modeled for Cisco 7200 devices
In Cisco ANA NetworkVision, BGP neighbors are not modeled if the local router BGP session IP address is an IPv6 address.
None
3.6.7
Cisco ANA PathTracer fails through VPLS
Cisco ANA PathTracer fails when traversing Cisco 7600 series devices with Distributed Forwarding Cards (DFCs) due to nonpersistent dynamic MAC entries.
Enter the following command under the global configuration mode to synchronize dynamic MAC entries to the mac-address table:
mac-address-table synchronize
3.6.7
Cisco ASR 9000 with large configuration is not modeled; the VNE is unreachable
If a Cisco ASR 9000 device is configured with a large configuration, the device is not modeled in Cisco ANA and becomes unreachable.
None
3.6.7
Topology creation fails due to encapsulation mismatch in Cisco CRS devices
Due to the improper encapsulation, link discovery and topology formation fails for Cisco CRS devices that are configured with Point-to-Point Protocol (PPP) encapsulation and that are running Cisco IOS XR 3.5.x, 3.6.x, or 3.7.x.
As a result, Cisco ANA incorrectly identifies encapsulation as High-Level Data Link Control (HDLC) instead of PPP on Packet Over SONET (POS) interfaces.
None
3.6.7
Missing LAG Link Down/Up service alarm
In Cisco ANA NetworkVision, if the status of a LAG link is changed in logical inventory:
•
No LAG Link Down service alarm is generated.
•
The VLAN topology is not affected.
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
Exception is displayed: Ethernet/unicast packets Rx/Tx problem loading registration
When two devices are connected to each other through more than one link, and the links between them are switched, CDP and LLDP are not updated. The following exception is displayed in the device logs:
ERROR [09 09 2009 09:59:59.910 IDT] - RegistrationLoader. loadRegistrationCreationInfo - 169.254.117.250 with key avm600/agents/da/Topo1/dcs/registrations/com.sheer.metrocentral.coretech.ethernet.dc.Ethernet/unicast packets rx tx Problem loading registration unicast packets rx tx got exception java.lang. NumberFormatException: cant format NULL value
at com.sheer.system.os. services.registry2.RegistryServiceUtil.translateToBoolean(RegistryServiceUtil.java:258)
at com.sheer.system.os. services.agentregistry.AgentRegistryServiceImpl.translateEntryToBoolean(AgentRegistryServiceImpl.java
None
3.6.7
Flood starting after the first hop of the flow fails
In Cisco ANA PathTracer, a MAC address-based trace fails to find the destination.
If a MAC destination address appears at the starting point of the path, but does not appear in one of the next hops, Cisco ANA PathTracer fails to find the MAC destination address.
Make sure all bridge tables are updated with the MAC destination address. That is, make sure there is constant traffic through the path.
3.6.7
Frequent port counter polling in legacy code can bring down Cisco ANA and router
If a retrieval specification is registered on port counters to receive notification upon changes, and the retrieval spec is configured with a depth value other than 0 (zero), Cisco ANA GUI clients might hang and VNE AVMs might not be able process requests.
Ensure that the retrieval spec is configured with the depth of 0.
3.6.7
Pseudowire OID change can cause backward compatibility issues
If you upgrade to Cisco ANA 3.6.7 and the existing database contains pseudowire information from a previous Cisco ANA release:
•
The existing pseudowire OIDs of the previous release are not migrated to the new pseudowire OIDs.
•
Existing data might be lost or inconsistent with new data.
None
3.6.7
VLAN discovery is not modeled correctly in Delete Reconcile mode
When Delete Reconcile mode is enabled in the registry, a VLAN discovery business object is deleted instead of receiving a reconciliation aspect.
However, in Cisco ANA 3.6.7, when Delete Reconcile mode is enabled, the initial discovery (the first time VNEs are loaded) omits some VLANs and contains incorrect merges.
None
3.6.7
For devices running Cisco IOS XR 3.5.3, pseudowire tunnel status is not modeled
For devices running Cisco IOS XR 3.5.3, the status of a pseudowire end-to-end emulation (PWE3) tunnel is not displayed during initial modeling.
PWE3 tunnel status is displayed during the first expedition phase of modeling. The expedition phase can occur when the status of a PWE3 tunnel changes.
This situation is seen only on devices running Cisco IOS XR 3.5.3.
None
3.6.7
Cisco CRS-1 physical inventory is not discovered after upgrading from Cisco IOS XR 3.6.1 to Cisco IOS XR 3.7.1
The physical inventory for Cisco CRS-1 devices is not populated in Cisco ANA NetworkVision after the device is upgraded from Cisco IOS XR 3.6.1 to Cisco IOS XR 3.7.1.
None
3.6.7
Multiple ATM VCs are not discovered in Cisco ANA
Cisco ANA does not discover multiple ATM virtual connections (VCs) for encapsulation type AAL5/AAL0.
This symptom also exists in prior releases of Cisco ANA.
This situation occurs if you configure more than 32 contiguous virtual channel identifiers (VCIs) on the same interface with the same virtual path identifier (VPI).
On an interface with the same VPI, configure VCIs in either of the following ways:
•
Using 1 through 31.
•
Using 1, 34, 67, and so on.
That is, the VC value anding with 31(0x11111) should not be the same as any other VCI if the VPI and interface name are the same.
3.6.7
A scale limitation in pseudowire tunnels
Cisco ANA supports high availability environments of the following sizes:
•
For MPLS, up to 800 tunnels on 15,000 devices with 300 cores.
•
For Carrier Ethernet, up to 1,500 tunnels on 350 devices.
If you have fewer devices in your setup, you can increase the number of tunnels.
Contact Cisco Technical Support for more information.
3.6.7
During Cisco ANA 3.6.6 to Cisco ANA 3.6.7 migration, maintenance link data is erased
When upgrading 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
After Cisco ANA 3.6.6 to Cisco ANA3.6.7 migration, old business tags are not displayed
When upgrading Cisco ANA 3.6.6 to Cisco ANA 3.6.7, business tags that were attached to links before the upgrade are not displayed in the Cisco ANA GUI.
None
3.6.7
After Cisco ANA 3.6.6 to Cisco ANA3.6.7 migration, hyperlinks for old tickets do not work
When upgrading Cisco ANA 3.6.6 to Cisco ANA 3.6.7, the Location hyperlink for an old event or ticket do not work in the Cisco ANA GUI. You can still open the ticket and view the ticket or event information, correlation, and so on.
None
3.6.7
After Cisco ANA 3.6.6 to Cisco ANA3.6.7 migration, old Link Up events are not cleared
After upgrading Cisco ANA 3.6.6 to Cisco ANA 3.6.7, the Link Up event covering an old Link Down ticket (after upgrade) is not cleared in the system.
None
3.6.7
Low GUI performance while working with a maximum sized map
When using Cisco ANA NetworkVision, you might experience slow GUI performance when working with a map of the maximum size. The maximum size of a map is defined as containing:
•
8,000 devices
•
10,000 links
•
5,000 tickets
None
3.6.6
Layer 3 ports cause MAC-based topology to create the wrong links
If you have Layer 3 Cisco 6500 or Cisco 7600 devices in the network and they do not have unique MAC addresses for each port, the physical topology is discovered incorrectly and ports are erroneously connected in Cisco ANA.
Disable MAC-based topology discovery in Cisco ANA using the following steps:
1.
Run
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 "site/ciscorouter2/76xx/ipcore/software version/default version/amsi/topology/Ethernet/MacTestEnable" false2.
Restart the gateway.
3.6.6
Cisco MWR 2941: Serial number for motherboard is missing
If you add a VNE for a Cisco MWR 2941 running Cisco IOS 12.4(19)MR02, and then, in Cisco ANA NetworkVision, choose Physical Inventory > Chassis > Slot, the serial number for the motherboard is not displayed.
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
Cisco ANA does not set transceiver-related properties for some cards
Cisco ANA does not set transceiver-related properties for cards affected by Transceiver Hierarchy-related MIB changes after the Cisco IOS 12.2(33)SRD1 release.
None
3.6.6
Ports under Cisco CRS-FCC-SC-22GE modules are not displayed
For Cisco CRS-1 devices running Cisco IOS XR 3.8.0 software, ports under Cisco CRS-FCC-SC-22GE module are not displayed in Cisco ANA NetworkVision physical inventory.
None
3.6.6
DS0 Bundle and Layer 2 encapsulation modeling for controller ports in Cisco GSR XR devices
Cisco ANA NetworkVision does not display channelized port properties for DS0 bundle and Layer 2 encapsulations if the mode is T1/E1.
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
Port is not displayed in link aggregation if it is configured with on mode
In Cisco ASR 900 devices, an Ethernet link aggregation port is not displayed if it is configured with bundle mode as ON. For example, bundle id 73 mode on.
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 issue occurs when you:
1.
Add a VNE in Cisco ANA Manage.
2.
Invoke Cisco ANA NetworkVision and select a device.
3.
Choose Physical Inventory > Chassis > Slot.
4.
Pull out the module. Card Down ticket is generated in the Tickets Pane.
5.
Insert the module. Even after several minutes, the Card Down ticket is not cleared.
None
3.6.6
For DWDM modules, laser status is not modeled and G.709 status is incorrect
Cisco ANA does not model the laser status, and G.709 status is modeled with a set of signals instead of enable/disable.
None
3.6.6
Filter ticket does not work in VPN map view
In Cisco ANA NetworkVision, if you right-click a link in VPN map view and then choose Filter Ticket, no results are displayed.
None
3.6.6
Client memory got to 99% after it stayed open for the weekend
The memory consumption reached 99% when Cisco ANA NetworkVision application ran continuously for a few days.
Relaunch Cisco ANA NetworkVision.
3.6.6
VNEs are stuck in the Initializing state
When you load VNEs using the vne_creation_script.pl script, the VNEs remain in the Initializing state.
Either restart the units or load a few VNEs at a time.
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
Opened a large VPN and got a Time Out message, but the operation continued
After opening a VPN map in Cisco ANA NetworkVision, a Time Out message was displayed, but the map opened a few moments later.
The map contained:
•
501 VPNs
•
2505 links
•
4008 sites
None
3.6.6
The same VPN appears twice in a map
If two users add the same VPN to the same map simultaneously in Cisco ANA NetworkVision, the map appears twice in the map.
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
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, but it displays the status Unknown for each individual fan tray.
None
3.6.6
Redundant Martini tunnel status is not updated
If redundant Martini is being used, if 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
If tunnel interface contains #, it breaks LSE info
If the hash symbol (#) appears in a tunnel description, the LSE information that is displayed in Cisco ANA NetworkVision inventory is incorrect.
For example, if you include a description similar to the following for a tunnel, LSE information is not displayed correctly in Cisco ANA NetworkVision:
interface Tunnel61description Test#1Do not include hash symbols in tunnel descriptions.
3.6.6
CPU levels on Cisco CRS-1 devices increase when managed by Cisco ANA 3.6.6
You might see high CPU levels on Cisco CRS-1 devices when you are using Cisco ANA 3.6.6.
None
3.6.6
Static link cannot be deleted from Cisco ANA NetworkVision GUI
In Cisco ANA NetworkVision, if you create a static link between two ports that have already been assigned to a dynamic link, you cannot delete the static link.
None
3.6.6
Alarm Ticket: Couldn't be found message displayed when attempting 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, stating that the alarm tickets could not be found even though you can open and view them.
None
3.6.6
Failed to create db statement error is displayed in Cisco ANA EventVision
After successfully logging into Cisco ANA GUI applications, you might encounter both of the following items:
•
In Cisco ANA NetworkVision, an hourglass icon.
•
In Cisco ANA EventVision, the following message when you choose the Syslog, Ticket, V1 Trap, or V2-V3 Trap tab:
Failed to create db statementNone
3.6.6
Memory leak when removing a VNE from the gateway
Memory leak occurs on the Cisco ANA gateway server when a VNE is removed.
None
3.6.5
For Cisco 6503 devices, the software version is a mismatch
If you update the software on a Cisco 6503 device, Cisco ANA inventory updates the product description in inventory, but not the software version.
The software version can take 30 minutes to be updated.
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 might stay in maintenance state.
Manually start the VNEs that remain in maintenance state.
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
Port name shown only for pseudowire sides in the down state
When the link is in the down state, the port name is shown only for a pseudowire.
None
3.6.5
Cisco ANA PathTracer displays the wrong path
Cisco ANA PathTracer does not display the correct path for packets. The final destination is not reached. However, the path is displayed correctly for the neighboring devices.
None
3.6.5
BQL adapter does not raise an error when the BQL command contains invalid data
If the IMO property name is incorrectly entered while creating a BQL command, the BQL disregards this property without giving an error.
None
3.6.5
Error in Registry editor
Error in Registry editor.
None
3.6.5
Subinterface not discovered
The subinterface is not populated in Cisco ANA.
This issue occurs because the subinterfaces are populated based on the technologies that are supported in Cisco ANA.
See Cisco Active Network Abstraction 3.6.7 VNE Reference Guide for details on the supported technologies.
3.6.5
Cisco ANA EventVision shows Table statistics are too old
Cisco ANA EventVision occasionally displays the message Table statistics are too old if table statistics are more than 30 days old.
None
3.6.5
Links are not discovered between Cisco PA-2T3+ and Cisco SPA-4XT3/E3 adapters
Cisco ANA NetworkVision does not discover links between Cisco PA-2T3+ and Cisco SPA-4XT3/E3 adapters.
None
3.6.5
Adaptive Polling conditions cause Cisco XR/GSR CPU to reach 100%
When Cisco ANA 3.6.5 polls a Cisco 12000 Series router running Cisco IOS XR 3.6.1, the router CPU reaches 100%.
None
3.6.5
Repetitive commands are sent to the device
While discovering the network, VNEs send repetitive commands to the devices, delaying network discovery.
None
3.6.4
Juniper LDP Session Up/Down trap without correlation
The SNMP trap Juniper LDP Session Up/Down is generated when the value of jnxMplsLdpSesState leaves the operational(5) state.
This situation occurs for:
•
Type: NOTIFICATION-TYPE
•
OID: 1.3.6.1.4.1.2636.4.4.0.4/ 1.3.6.1.4.1.2636.4.4.0.3
•
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).juniperMIB(2636).jnxTraps(4).jnxLdpTraps(4).jnxLdpTrapPrefix(0).jnxLdpSesDown(4)
•
Module: JUNIPER-LDP-MIB
None
3.6.4
Cisco ANA does not present the interface when SONET interface changes
Cisco ANA does not display the interface when a SONET interface changes.
This situation occurs if you disable a SONET port on a Juniper device and then enable it. Cisco ANA EventVision displays the trap with the device name, but not the interface.
None
3.6.4
Cisco ANA PathTracer does not reach an IP interface configured on L3 Link Agg on Cisco CRS-1 devices
If you use Cisco ANA PathTracer on an interface that is configured for Layer 3 link aggregation on a Cisco CRS-1 device, the path does not reach the IP interface of the remote device.
None
3.6.4
Some of the Juniper VNEs appear under Product scheme
Some Juniper VNEs appear under the Product scheme even though they are supported by the ipcore scheme.
This situation occurs when you run the VEG tool. The results show the VNEs for some Juniper devices under the Product scheme instead of the ipcore scheme.
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. Create a new VNE for the affected device and open a map in Cisco ANA NetworkVision with this device.
2. Open MPLS interfaces under the LSE table and enter LDP in the Distribution Protocol field.
3. Change the distribution protocol type to TDP on the device and confirm the change in Cisco ANA NetworkVision.
4. Change the distribution protocol type to LDP on the device.
None
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 due to appearance of unexpected characters. As a result, the recordings cannot be used for device modeling in Cisco ANA.
None
3.6.4
No expedite on local switching Card Out on Cisco CRS device
On Cisco CRS devices, the event Local Switching Entry Down is not correlated to a Card Out alarm.
None
3.6.4
Cisco Catalyst 6509 cannot connect to the cloud VNE
Cisco Catalyst 6509 devices cannot connect to the cloud VNE even though the configuration is similar to Cisco Catalyst 3560 devices.
None
3.6.4
Cannot restrict maps on a user basis
Cannot assign maps to the user using Cisco ANA Manage.
You can assign maps to the user by updating a registry file. Changes to the registry should be performed only with the support of Cisco. For details, contact your Cisco account representative.
3.6.4
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
Tickets are not cleared
Tickets are not cleared even after the issue on the device or network has been resolved. The Correlation tab shows that the root alarm is cleared, but some alarms that are correlated to it are not cleared and are propagated to the overall ticket severity.
None
3.6.4
On Juniper devices, wrong BGP peer modeling for peers with the same parameters
If External BGP (eBGP) is configured in VRFs using the same peer IP address, local IP address, and peer AS number (for example, when using templates to configure eBGP), the BGP Neighbors container displays only one peer for the last modeled VRF.
This situation occurs on Juniper devices running JUNOS software.
None
3.6.4
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
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 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
New VNEs added after disaster recovery failover are in the Unreachable state.
In the High Availability Cisco ANA setup, after disaster recovery, the newly added VNE goes into the Unreachable state.
Restart the AVMs to remodel the VNEs. For details, see Cisco Active Network Abstraction 3.6.7 Administrator User Guide.
3.6.3
ECI Hi-FOCuS devices are not modeled
ECI Hi-FOCuS devices are not modeled in Cisco ANA NetworkVision physical inventory.
None
3.6.2
Juniper routers Cross VRF information is wrong
Cisco ANA displays incorrect cross-VRF information for Juniper routers.
None
3.6.2
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.6.7
The resolved caveats in Cisco ANA 3.6.7 are:
Related Documentation
User Guides
Cisco Active Network Abstraction 3.6.7 Documentation Guide
Cisco Active Network Abstraction 3.6.7 User Guide
Cisco Active Network Abstraction 3.6.7 Technology Support and Information Model Reference Manual
Cisco Active Network Abstraction 3.6.7 VNE Reference Guide
Administrator Guides
Cisco Active Network Abstraction 3.6.7 Installation Guide
Cisco Active Network Abstraction 3.6.7 Administrator User Guide
Developer Guides
Cisco Active Network Abstraction 3.6.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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0910R)
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-2009 Cisco Systems, Inc. All rights reserved.

