Table Of Contents
Cisco Active Network Abstraction 3.7.1
Release Notes
New and Changed Information
Contents
Introduction
Technology Support
Cisco ANA Client Applications
Network Element Inventory Discovery
Network and Service Monitoring
Event and Fault Management
Configuration and Activation
Security
Cisco ANA Reports
Northbound Integration
Cisco ANA Configuration and Image Management
Cisco ANA Network Service Activation 1.1
New Features and Enhancements in Cisco ANA 3.7.1
Cisco ANA Software License
Installation and Migration
Carrier Ethernet
Fault Management
Foundation-Level Enhancements
Reports
VNE Life Cycle Management (LCM)
External Launch Enhancements
IP RAN and MToP
IPv4 and IPv6
Command Scripts
GUI-Related Enhancements
Features Removed or Changed in Cisco ANA 3.7.1
Features Removed
Features Changed
Documentation Enhancements
Other Changes
New Network Element, Module, and Software Support
New Network Element Support
New Module Support
New Software Version Support
Network Elements and Features Validated for Cisco ANA Configuration and Image Management
New Alarm, Trap, and Syslog Support
Service Alarm Severity Change
New Service Alarm Subtypes
New Service Alarms
New Trap Support
Cisco ASR 9000 V1 Trap Support Added
Cisco ASR 9000 V2 Trap Support Added
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 ACE V1 Traps
Cisco ACE V2/V3 Traps
Cisco Nexus V1 Traps
Cisco Nexus V2/V3 Traps
New Syslog Support
Cisco ASR 9000 Syslog Support Added
Cisco IOS Syslog Support Added
Cisco IOS XR Syslog Support Added
Cisco ACE Syslog Support Added
Cisco Nexus Syslog Support Added
Important Notes
Installation Notes
Before Installing Cisco ANA 3.7.1
Changes in the Cisco ANA Installation
Changes in the Upgrade Process
Before Upgrading to Cisco ANA 3.7.1
Using the install.pl Command
Memory Consumption
Backward Compatibility
Cisco ANA 3.7 Upgrade Limitations
Solaris Services and Components
Using Cisco CRS-1 VNEs
Installing the Cisco IOS XR Manageability Package
Creating the SNMP Community
SDR Support
For Cisco XR 12000 Series Devices
For Cisco CRS-1 Devices
Device and Software-Specific Limitations
Supported Schemes
JDK DST Timezone Update Tool for Cisco ANA
Configuring Database Storage (Redo Logs)
Online Help
Limitations and Restrictions
Cisco ANA Configuration and Image Management
Cisco ANA NetworkVision
Cisco ANA Fault Management
Cisco ANA Workflow Editor Sessions
ATM Topology Discovery
BGP Neighbors
EVC Discovery
HSRP
OSPF
VLAN Tagged Interface Limitation
Open Caveats in Cisco ANA 3.x
Significant Caveats Before Using Cisco ANA 3.7.1
Outstanding Cisco ANA 3.7.1 Caveats that Were Resolved for Earlier Releases of Cisco ANA
Open Caveats in Cisco ANA 3.x
Resolved Caveats - Cisco ANA 3.7.1
Related Documentation
User Guides
Administrator Guides
Developer Guides
Other Documentation
Obtaining Documentation and Submitting a Service Request
Cisco Active Network Abstraction 3.7.1
Release Notes
Revised: September 15, 2011, OL-21801-01
These release notes support the release of Cisco Active Network Abstraction (Cisco ANA) 3.7.1.
Note 
See Cisco.com for the most up-to-date version of the Cisco Active Network Abstraction 3.7.1 Release Notes.
New and Changed Information
The following table describes information that has been added or changed since the initial release of the Cisco Active Network Abstraction 3.7.1 Release Notes.
Table 1 New and Changed Information in the Release Notes
Date Released
|
Revision
|
Location
|
September 15, 2011
|
Added the following open caveat:
CSCtq94559—Unit machines become unreachable following initial setup/installation
|
Open Caveats in Cisco ANA 3.x
|
June 6, 2011
|
Added the following items:
•Text describing support introduced in Cisco ANA 3.7.1 for wrapped syslogs and multisource events.
•CSCto84146—Cisco ANA 3.7.1 mvm.pl script continues even with failures
|
•New Alarm, Trap, and Syslog Support
•Open Caveats in Cisco ANA 3.x
|
|
February 17, 2011
|
Added the following information under EVC Discovery:
In Cisco ANA 3.7.1, if you initiate full EVC discovery by issuing the runFullDiscovery command on AVM 11, not all EVCs are found even though the command appears to complete successfully. To work around this situation, issue the runFullDiscovery command again. For more information, see CSCti03000.
|
Limitations and Restrictions
|
January 28, 2011
|
Added the following open caveat:
CSCth79506—Max speed shown as -1 for all Gig and 10Gig Cisco GSR devices running Cisco IOS XR 4.0 software
|
Open Caveats in Cisco ANA 3.x
|
November 4, 2010
|
•Added the following open caveat:
CSCti95693—System cannot handle large number of tickets with thousands of events attached
•Added the following resolved caveat:
CSCtg19555—Event notification svc resets cenUserMessages after update TFS
|
•Open Caveats in Cisco ANA 3.x
•Resolved Caveats - Cisco ANA 3.7.1
|
November 2, 2010
|
Added the following caveat:
CSCtj73268—Configurator User - Restrictions
|
Open Caveats in Cisco ANA 3.x
|
October 11, 2010
|
Added the following caveat:
CSCtj40515—CDP table port hyperlink and port status do not update correctly
|
Open Caveats in Cisco ANA 3.x
|
October 6, 2010
|
Made the following changes:
•Revised the section regarding Cisco ANA Workflow editor.
|
Cisco ANA Workflow Editor Sessions
|
•Added the following caveats to the list of open caveats:
–CSCti05315—IP RAN scale: Integrity test of "Regular Workflows" deletion fails
–CSCtj32671—Port 162 appears to be occupied when IP address contains "162"
|
Open Caveats in Cisco ANA 3.x
|
September 22, 2010
|
Replaced the 9120088 patch for Oracle 11g Release 11.2.0.1.0 with:
•p9259407_112010_SOLARIS64.zip
(for Solaris)
•p9259407_112010_Linux-x86-64.zip
(for Linux)
|
Table 28
|
August 30, 2010
|
Initial version.
|
—
|
Contents
This document includes the following topics:
•Introduction
•New Features and Enhancements in Cisco ANA 3.7.1
•New Network Element, Module, and Software Support
•New Alarm, Trap, and Syslog Support
•Important Notes
•Limitations and Restrictions
•Open Caveats in Cisco ANA 3.x
•Resolved Caveats - Cisco ANA 3.7.1
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
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:
•Interoperable interfaces, including physical and logical ports.
•Protocol stacks.
•Forwarding entities, including switching and routing tables.
•Adjacencies, including physical and service links.
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—The main GUI application used to visualize the network through network and service maps, and to view device physical and logical inventories and connectivity.
Cisco ANA NetworkVision is also used to launch other clients and tools, such as Command Builder and Cisco ANA Network Service Activation.
•Cisco ANA EventVision—Used to browse historical events archived by Cisco ANA.
•Cisco ANA Manage—The Cisco ANA administration and configuration application used to manage the entire product.
•Cisco ANA Configuration and Image Management—Used to manage the software and device configuration changes that are made to devices in your network. (This GUI client is available only if you install the Cisco ANA Configuration and Image Management feature.)
For more information, see Cisco Active Network Abstraction 3.7.1 Configuration and Image Management User and Administrator Guide.
All Cisco ANA client applications support automatic client updates. Whenever a client application is launched and connects to the Cisco ANA server, Cisco ANA automatically checks the client software version, and, if necessary, automatically performs updates.
Network Element Inventory Discovery
Every node managed by Cisco ANA is assigned to an autonomous VNE. The VNE continuously investigates the NE status and configuration in order to reflect it accurately and generate an accurate virtual model of the network.
Cisco ANA provides full control over the information collection process. Different polling intervals are assigned to the various information types, such as status, configuration, and performance counters, which can also be differentiated by device types, groups, and instances. Furthermore, the polling intervals are modifiable in runtime, which allows VNEs to implement adaptive polling, that is, to increase or reduce the polling rates according to the device load or CPU consumption.
Network and Service Monitoring
Effective network management requires accurate, up-to-date network information. Cisco ANA uses Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP) for the initial network discovery and to maintain the real-time, virtual network image.
After discovery, presentation of the network in Cisco ANA includes:
•Network maps
•Service overlays
•Service path traces
•Addition of business tags
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 customize one of the existing report types as required for your environment by setting report input values for later use. The Report Manager is available from Cisco ANA NetworkVision, Cisco ANA EventVision, and Cisco ANA Manage. 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.
Cisco ANA Configuration and Image Management
The new Configuration and Image Management GUI enables you to detect and track changes that are made to a device configurations, and provide rapid, reliable software upgrades to devices.
For device configuration changes, copies of configuration files are stored in a configuration archive, from which you can compare configurations, restore configuration files to devices, and for Cisco IOS devices, synchronize running and startup configuration files.
Cisco IOS and Cisco IOS XR software images are stored in the Cisco ANA image repository. You are alerted when running and startup configurations are no longer synchronized. You can add new images by importing them from Cisco.com or a local filesystem. Before an image is distributed, NEIM performs an upgrade analysis to ensure that the network element is compatible with the image. For Cisco IOS XR devices, you can deactivate packages, test changes before committing them, commit changes, and rolling packages back to previous rollback points.
Device configuration and software image files are stored in the Cisco ANA database in the new anauser_xmp schema.
For more information, see Cisco Active Network Abstraction 3.7.1 Configuration and Image Management User and Administrator Guide.
Cisco ANA Network Service Activation 1.1
Cisco ANA Network Service Activation 1.1 (Cisco ANA NSA) is a Cisco ANA service activation extension for users wanting to deploy Carrier Ethernet, IP Radio Access Network (RAN), and Mobile Transport over Pseudowire (MToP) services using a service activation wizard launched from Cisco ANA NetworkVision. Cisco ANA NSA provides:
•A predefined collection of service activation wizards, workflows, and scripts that allow you to begin activating services on Cisco network elements after Cisco ANA NSA is installed.
•The ability for service designers, network planners, and service integrators to customize the wizards and workflows to address service activation needs not provided in the delivered Cisco ANA NSA package.
Delivered Cisco ANA NSA 1.1 activation wizards include:
•Create E-LAN VPLS Hub
•Create E-LAN VPLS Neighbor
•Create E-LAN EFP
•Create E-LAN H-VPLS Spoke
•Create E-LAN H-VPLS Neighbor
•Create Point-to-Point E-Line
•Create E-Line Local Connection
•Create Access
•Create Layer 3 VPN
•Create Residential HSI
Delivered Cisco ANA NSA 1.1 policy wizards include:
•Create Layer 2 ACL
•Create QoS Policy
•Add MAC Secure Addresses
Delivered MToP wizards include:
•Create ATM Pseudowire
•Create TDM Pseudowire
•Create TDM Clock Pseudowire
•Create Clock Synchronization
Cisco ANA NSA 1.1 customization enhancements include:
•Activation Wizard Builder—AWB allows users to customize, validate, and synchronize Cisco ANA NSA wizard metadata using a user-friendly GUI instead of a text or XML editor.
•Workflow Editor enhancements—Two NSA-specific enhancements are added to the Cisco ANA Workflow Editor:
–New NSA Workflow—creates a workflow with required NSA attributes defined.
–NSA Tokenizer—Inserts a tokenizer function into workflows that automatically generates a BeanShell script to tokenize workflow parameter values and set the activation script parameters with those values.
New Features and Enhancements in Cisco ANA 3.7.1
The following topics describe the new features, enhancements, and changes in Cisco ANA 3.7.1:
•Cisco ANA Software License
•Installation and Migration
•Carrier Ethernet
•Fault Management
•Foundation-Level Enhancements
•Reports
•VNE Life Cycle Management (LCM)
•External Launch Enhancements
•IP RAN and MToP
•IPv4 and IPv6
•Command Scripts
•GUI-Related Enhancements
•Features Removed or Changed in Cisco ANA 3.7.1
•Documentation Enhancements
•Other Changes
For information about support added in Cisco ANA 3.7.1 for devices, software, or fault management, see:
•New Network Element, Module, and Software Support
•New Alarm, Trap, and Syslog Support
For information about element and feature support in Cisco ANA Configuration and Image Management, see Network Elements and Features Validated for Cisco ANA Configuration and Image Management.
Cisco ANA Software License
All purchased Cisco ANA licenses (the Cisco ANA base kit, UI Clients, RTMs, and so on) must be registered and activated, by installing a license file on the Cisco ANA server.
Two types of licenses are available:
•Cisco ANA Software Base Kit for a production network.
•Cisco ANA Lab Bundle for lab or staging networks.
Note The Cisco ANA 3.7.1 license file must be installed within 120 days of installation or upgrade. If there are no valid license files on the gateway server, Cisco ANA acts as an evaluation version. This means that it has full functionality for 120 days after installation, and then it expires. When the Cisco ANA gateway server is next restarted, Cisco ANA will not start.
Licensing for Upgrades to Cisco ANA 3.7.1
•Upgrade from Cisco ANA 3.7: If you are upgrading from a registered version of Cisco ANA 3.7, no new license files are required. To check whether you have a valid license file installed on the Cisco ANA gateway server, see the Cisco Active Network Abstraction 3.7.1 Administrator Guide.
•Upgrade from Cisco ANA 3.6.x: A new license file is required because there is no automatic transfer of licenses from Cisco ANA 3.6.x. Contact your Cisco account representative or send an e-mail to ask-ana-licensing@cisco.com to get a new license file, and install it on the Cisco ANA 3.7.1 gateway server within 120 days of the upgrade.
Licensing for High Availability Setups
If you are setting up high availability, contact your Cisco account representative or send an e-mail to ask-ana-licensing@cisco.com for licensing information and assistance.
Installation and Migration
Cisco ANA 3.7.1 provides the following new features related to installation and migration:
•Support for Windows 7 on the Cisco ANA client.
•Cisco ANA 3.7.1 provides the installation files on three DVDs:
–Cisco ANA 3.7.1 Disk 1: New Install—Contains the files for a new installation of Cisco ANA 3.7.1. Disk 1 includes the Cisco ANA client, server, Configuration and Image Management, Network Service Activation (NSA), and documentation.
–Cisco ANA 3.7.1 Disk 2: Upgrade Install—Contains the files for an upgrade installation of Cisco ANA 3.7.1.
–Cisco ANA 3.7.1 Addendum: Use as prompted—Contains addendum files for a new installation. In most cases, the addendum files are not required; use them only if prompted.
For more information, see the Cisco Active Network Abstraction 3.7.1 Installation Guide.
•Support for dual network interface cards (NICs). Dual NICs let you isolate the northbound interface from the back-end interface.
•Ability to install the optional Cisco ANA 3.7.1 Configuration and Image Management component when you install the Cisco ANA gateway, or install it separately.
•Inclusion of installation-specific error messages in the Cisco Active Network Abstraction 3.7.1 Installation Guide.
•Ability to install the following add-on modules on the Cisco ANA gateway:
–Cisco ANA Network Service Activation (NSA) 1.1
–Cisco ANA NSA 1.1 Activation Wizard Builder (AWB)
•Support for a new ana-user_admin user who can run maintenance tasks, such as gathering statistics, on the other Cisco ANA database schemas. This support is available for new installations only.
•Ability to create database schemes manually.
Table 2 describes the new ports that are used by Cisco ANA 3.7.1.
Table 2 New Ports Used by Cisco ANA 3.7.1
Port
|
Protocol
|
Description
|
Cisco ANA Gateway—Northbound
|
2077
|
TCP
|
Spring DM OSGi console, used for Cisco ANA Configuration and Image Management
|
8080
|
HTTP
|
HTTP connector, used for Cisco ANA Configuration and Image Management
|
8443
|
TCP
|
DM server HTTPS connector port, used for Cisco ANA Configuration and Image Management
|
8509
|
TCP
|
DM server AJP connector port, used for Cisco ANA Configuration and Image Management
|
9005
|
TCP
|
Tomcat server port, used for Cisco ANA Configuration and Image Management
|
9009
|
TCP
|
Tomcat AJP connector port, used for Cisco ANA Configuration and Image Management
|
9080
|
TCP
|
Tomcat HTTP connector port, used for Cisco ANA Configuration and Image Management
|
9443
|
TCP
|
Tomcat HTTPS connector port, used for Cisco ANA Configuration and Image Management
|
9875
|
TCP
|
JMX console port, used for Cisco ANA Configuration and Image Management
|
Cisco ANA Gateway—Southbound and Intraunit Communication
|
69
|
UDP
|
TFTP communication between the devices and the units
|
1101
|
TCP
|
Cisco ANA user exclusive hardened SSH connection for system administration operations
|
9490
|
TCP
|
Secured SSL transport
|
Table 3 describes the new Cisco ANA 3.7.1 TCP and UDP ports with the direction of communication.
Table 3 New Cisco ANA 3.7.1 TCP and UDP Ports
TCP or UDP Port Number
|
Source
|
Destination
|
Used by...
|
7 (TCP/UDP)
|
Gateway or unit
|
Unit or gateway
|
Cisco ANA environment and core OS services; ping
|
69 (UDP)
|
Gateway
|
TFTP service
|
AVM 83 TFTP service, used for Cisco ANA Configuration and Image Management
|
8080 (HTTP)
|
Gateway
|
Client
|
HTTP port for Cisco ANA Configuration and Image Management web clients
|
8443
|
Gateway
|
Client
|
Secure HTTP port for Cisco ANA Configuration and Image Management web clients
|
9490 (TCP)
|
Gateway
|
Unit
|
Cisco ANA SSL transport
|
9490 (TCP)
|
Unit
|
Gateway
|
Cisco ANA SSL transport
|
Carrier Ethernet
Cisco ANA 3.7.1 includes enhancements at the element, network, and service levels.
Element-Level Enhancements
•Support for EVC port storm control and monitoring for Cisco ME3400 and Cisco 3750ME devices running Cisco IOS versions 12.2(52)SE to 12.2(54)SE.
•IP SLA Responder TWAMP discovery and modeling support.
•Ethernet Operations, Administration, and Management (OAM) enhancements:
–Additional CFM support for configurations and faults.
–Ethernet LMI modeling and fault support.
–Link OAM modeling and fault support.
•Provider Backbone Bridge (PBB) discovery, modeling, and fault support.
•Support for Intermediate System-to-Intermediate System (IS-IS) process, metric, interface, and neighbor properties in logical inventory.
Network-Level Enhancements
•VPLS/H-VPLS flow domain discovery, visualization, and overlays.
•VPLS/H-VPLS summary and detailed reports.
•EoMPLS flow domain discovery, visualization, and overlays, including support for multi-segment pseudowires.
Multi-segment pseudowire support includes:
–Pinging a pseudowire.
–Tracing a network pseudowire using Cisco ANA PathTracer.
–Viewing Virtual Circuit Connectivity Verification (VCCV) and Control Channel (CC) information for a pseudowire endpoint.
•VLAN flow domain discovery for bridge domains and cross-connects.
•VLAN service link enhancements for additional EFP types, such as port-based and VLAN tag range EFPs.
•LAG link discovery.
•LAG service alarm enhancements.
Service Level Enhancements
•Ethernet service discovery, including edge EFP discovery, visualization, and overlays.
•Ethernet service summary and detail reports.
Fault Management
Cisco ANA 3.7.1 introduces fault management improvements that provide the following:
•New GUI in Cisco ANA Manage for configuring an Event Notification Service.
•A new flag in the registry allows you to enable and disable processing of events from the unmanaged NEs. When the flag is enabled, events from all NEs (managed and unmanaged) are persisted in AVM 100 and forwarded to the Event Archive and, if configured, to the Event Notification Service for further filtering.
See the Cisco Active Network Abstraction 3.7.1 Administrator Guide for more information.
•You can register for notification for a particular event by using the new BQL command RegisterEventNotifications. This command can be used for the following event categories:
–Actionable events
–EMS internal event (System, Security, Audit, and Provisioning)
The Event type and SeverityEnum can be used as a filter while registering for the notification.
See the Cisco Active Network Abstraction Integration Developer Guide for more information.
•Support for event notifications generated by all devices (including devices not represented by a VNE). This support includes receiving, persisting, filtering, displaying, and forwarding events. The option for this support is configurable.
•Support for running the Cisco ANA Event Collector (AEC, which runs on AVM 100) on both gateways and units. This includes new documentation with recommendations and sample scenarios.
•AEC with proxy forwarding support. If the AEC is running on a unit and the unit server does not have a direct connection to the database, you can configure another unit to be its proxy and persist event information to the Fault Database. For more information, see the Cisco Active Network Abstraction 3.7.1 Administrator Guide.
Foundation-Level Enhancements
Cisco ANA 3.7.1 introduces the following foundation-level enhancement:
•External User Authentication—The Cisco ANA Manage GUI for configuring an external authentication server now includes a Test Connection button that validates the connectivity between the Cisco ANA gateway server and the LDAP server in real time.
•Gateway server—New script for changing the IP address of the gateway server.
•AVMs—New procedure that allows you to move AVMs from a down unit.
•Database purging—New procedure that specifies when to purge the Fault Database based on the size of the data.
•High CPU Issues—New procedure for configuring Telnet throttling by defining a vty terminal length for Telnet commands (recommended for use with Cisco IOS devices).
For more information, see the Cisco Active Network Abstraction 3.7.1 Administrator Guide.
Reports
Cisco ANA 3.7.1 Report Manager includes the following new reports:
•AToM detailed and summary reports
•Ethernet service detailed and summary reports
•VPLS detailed and summary reports
•Syslog Trend (by severity)
For information about reports and Report Manager, see the Cisco Active Network Abstraction 3.7.1 User Guide.
You can also retrieve reports using BQL. For more information, see the Cisco Active Network Abstraction Integration Developer Guide.
VNE Life Cycle Management (LCM)
Cisco ANA 3.7.1 introduces the following VNE LCM enhancements:
•Device reachability improvements:
–A new Communication Details window (in NetworkVision) provides information on the status of the protocols used by a VNE, and also reports whether the device is generating traps and syslogs.
–New registry customization settings allow users to fine tune when Cisco ANA should consider a protocol unreachable. In addition, users can choose from different VNE management communication policies to report reachability in a more or less strict manner. This allows Cisco ANA to report reachability in a more accurate way, according to a customer configuration.
–New GUI decorators are used to report VNE communication and investigation states.
•Improved VNE discovery time identification mechanism— VNEs can instead use a convergence mechanism (rather than the discovery process timeout) to determine whether discovery has ended. Using the convergence mechanism, the VNE evaluates whether commands are still updating the model to help determine if more model changes are expected. The mechanism ensures that:
–The most complicated commands have more than sufficient time to run.
–VNEs do not remain in the Discovering state when a relatively inconsequential command has not completed.
For more information, see the Cisco Active Network Abstraction 3.7.1 Administrator Guide.
External Launch Enhancements
Cisco ANA 3.7.1 enables you to add external launch points to links, tickets, and events so that you can launch them from the Cisco ANA NetworkVision navigation pane, map view, links view, or ticket pane, and from Cisco ANA EventVision for any type of event.
For more information, see the Cisco Active Network Abstraction 3.7.1 Customization User Guide.
IP RAN and MToP
Cisco ANA 3.7.1 includes the following enhanced support and features for IP Radio Access Networks (RANs) and Mobile Transport over Packet (MToP):
•At the element level:
–Modeling of pseudowire cross-connects and VFI.
–Pseudowire Virtual Circuit Connectivity Verification (VCCV) Command Builder script support.
•At the network level:
–Cisco ANA PathTracer support for multi-segment pseudowires.
–Multi-segment pseudowire discovery.
•At the service level, end-to-end visualization and overlay support for AToM topologies (TDMoMPLS, ATMoMPLS, and EoMPLS).
IPv4 and IPv6
Cisco ANA 3.7.1 includes the following enhancements for IP technology:
•At the element level:
–OSPF and OSPFv3 support for IPv4 and IPv6, including modeling of OSPF processes, interfaces, and neighbors.
–Carrier Grade Name Address Translation (NAT) support for Cisco CRS-1 devices, including modeling of Carrier Grade NAT service instances, service apps interfaces, address pools, and summary statistics.
•At the network level:
–OSPF neighbor down service alarm and correlation support
–TCAs for Carrier Grade NAT statistics
Command Scripts
The following new command scripts are automatically installed with Cisco ANA 3.7.1:
•Ethernet Local Management Interface (LMI) commands
•Ethernet Operations, Administration, and Maintenance (OAM) commands
•Carrier Grade NAT commands
•Pseudowire virtual circuit connectivity verification (VCCV) commands
The following existing commands include new support:
•CFM commands include new parameter support.
•REP commands support additional network elements.
For more information, see the Commands section of the Cisco Active Network Abstraction 3.7.1 Reference Guide.
GUI-Related Enhancements
Cisco ANA 3.7.1 provides the following GUI-related enhancements:
•Enhanced filtering support in tables.
•Ability to perform ticket operations on multiple tickets at the same time.
•New icons and badges for new elements, VNE communication and investigation states, and links.
•Improved layout of information for tickets and alarms in Cisco ANA NetworkVision and Cisco ANA EventVision.
•The Ticket table in Cisco ANA NetworkVision includes a new column that displays the severity of the root cause alarm for each ticket.
•Support for display of multiple links for REP segments.
Features Removed or Changed in Cisco ANA 3.7.1
Features Removed
The following features are not available in Cisco ANA 3.7.1:
•OSPF Networks object in Cisco ANA NetworkVision
Because the OSPF Networks object is no longer available, existing tickets and alarms that were associated with the OSPF Networks object remain open and are not cleared after upgrading to Cisco ANA 3.7.1. Newly received traps and syslogs generate new tickets and are associated with the OSPF Interface, OSPF Neighbor, or OSPF Process. If insufficient event data prevents Cisco ANA from associating traps or syslogs with one of these objects, the traps or syslogs are associated with the Managed Element object or the OSPF Networks object, in which case the OSPF Networks icon is displayed in logical inventory (CSCtg86206). For details about OSPF-specific traps and syslogs, see the Cisco Active Network Abstraction 3.7.1 Reference Guide Part 3, "Alarms and Events."
For events that occurred before the upgrade to Cisco ANA 3.7.1, the source identifier uses the old format. After upgrading, when the event is cleared, the clearing event's source identifier uses the new format, which prevents Cisco ANA from linking the events.
If you are upgrading from Cisco ANA 3.6.x, see the section "Managing 3.6.x Events" in the Cisco Active Network Abstraction 3.7.1 Installation Guide to understand the event migration. Postmigration event management in Cisco ANA 3.7.1 is the same as in Cisco ANA 3.7.
•In Cisco ANA NetworkVision, the following options are no longer available for working with route targets:
–Provisioning route targets
–Enabling IPv6 Virtual Routing and Forwarding (VRF)
–Adding route targets
–Removing route targets
Features Changed
The following features have changed in Cisco ANA 3.7.1:
•Cisco ANA EventVision:
–Access to Cisco ANA EventVision is limited to only those users with the Administrator user role.
–New and changed options for the amount of data that is displayed.
–The Client Type field is no longer included in the Security tab.
–The General tab is now named Details.
–The Correlation tab displays the severity, short description, and other information for the alarm instead of the ticket.
–The History tab contains two panels:
- The upper panel displays the table.
- The lower panel displays the long description of the selected event.
For more information, see the Cisco Active Network Abstraction 3.7.1 User Guide.
•Cisco ANA Manage—In Global Settings > Event Management, the unit of measurement that controls when database partitions should be split was changed from days to hours. By default, database partitions are now split every 6 hours.
For more information, see the Cisco Active Network Abstraction 3.7.1 Administrator Guide.
•Cisco ANA NetworkVision:
–In the Ticket pane, the right-click option Find Source has been replaced by Find Affected Elements.
–In the Links view, the right-click option Find Source has been replaced by Select Link in Map.
–New categories for adding elements to maps, such as cross-connects, Ethernet services, pseudowires, and unassociated bridges.
–New overlay types, such as Ethernet service, pseudowire, and VPLS.
•Report Manager:
–The All Dates option is no longer available for generating reports.
–The Daily Event Count report has been renamed Detailed Event Count (by device).
–The Software Version Summary (by device) report has been renamed Software Summary (by device).
–The Software Version Summary (by version) report has been renamed Software Summary (by version).
For more information, see the Cisco Active Network Abstraction 3.7.1 User Guide.
Documentation Enhancements
In addition to the new features and support described in previous sections, individual Cisco ANA 3.7.1 documents have been updated and enhanced as detailed in the following sections.
Cisco Active Network Abstraction 3.7.1 Administrator Guide
The Cisco Active Network Abstraction 3.7.1 Administrator Guide includes:
•New chapters:
–Cisco ANA 3.7.1 Licensing—Details about Cisco ANA licensing, including obtaining, installing, verifying, and managing licenses.
–Cisco ANA Polling Mechanisms—Details about polling methods and how to customize them.
–Cisco ANA Logs—Cisco ANA logs and their locations, and how to customize logging.
•Gateways—New procedure that describes how to change the gateway server IP address.
•AVMs—New procedure that describes to move an AVM from a down unit.
•VNEs:
–Device reachability— Updated with device reachability improvements. Also provides better descriptions of VNE investigation states and the new GUI decorators.
–VNE discovery time identification mechanism— Improved description of the discovery process, how Cisco ANA determines when discovery is completed, and how you customize the discovery process.
•Event Notification Service—How to configure an Event Notification Service (ENS) to forward received from devices and system events generated by Cisco ANA to OSSs, using the new GUI for this feature.
•User Security: Roles and Scopes—Better descriptions of default permissions and device scopes and how they work together.
•ANA Event Collector (AEC) AVM 100)—Extensively rewritten to explain what happens when Cisco ANA receives an event; supported configurations for the AEC on gateways and units; examples and recommendations. Also describes how to configuring a proxy when a unit (running an AEC) is not connected to a database.
•Purging Data—How to purge data from the Event Archive and the Fault Database, with clarifications of which procedures affect which schemas. Also includes a new procedure for implementing size-based purging of the Fault Database.
•Utility Scripts—How to change passwords for the new anauser_xmp and anauser_admin schemas.
•High Availability/Unit Switchover—How high availability scenarios affect the AEC, and new recommendations for configuring high availability on units.
•Managing Device Reachability—How to use and interpret the Communication Details window and how to customize device reachability reporting, including how to use VNE management communication policies. Also provides steps for troubleshooting reachability problems.
•CPU Utilization—New procedure that describes how to configure telnet throttling by defining a vty terminal length for Telnet commands (recommended for use with Cisco IOS devices).
New chapters for installing and uninstalling Network Service Activation.
The Cisco Active Network Abstraction 3.7.1 User Guide includes the following enhancements:
•Each chapter includes a table that identifies the default user roles required to perform the procedures described in that chapter.
•New chapters for:
–Carrier Grade NAT
–Viewing Ethernet OAM Tool Properties
The Cisco Active Network Abstraction 3.7.1 Customization User Guide includes:
•A new section on the VNE Customization Builder (VCB) that describes:
–VCB
–How to add support for modules and devices using VCB
–Concepts and commands for customizing events
–Adding support for events
–Using VCB templates
•A new chapter that describes the External Launch application and provides examples for creating external launch points.
Cisco Active Network Abstraction 3.7.1 Reference Guide
The Cisco Active Network Abstraction 3.7.1 Reference Guide includes the following enhancements:
•A consolidated Alarms and Events section that includes service alarms, events, syslogs, and traps.
•Where possible, the service alarms in the Technology Support and Information Model Objects section are linked to their entries in the Alarms and Events section.
The Cisco Active Network Abstraction Integration Developer Guide includes the following new chapters:
•Generating Reports Using BQL
•Managing Soft Properties Using BQL
Other Changes
Cisco ANA 3.7.1 has resolved a number of open bugs. For details, see Resolved Caveats - Cisco ANA 3.7.1.
New Network Element, Module, and Software Support
The following topics describe the new support provided in Cisco ANA 3.7.1 for network elements, modules, and software:
•New Network Element Support
•New Module Support
•New Software Version Support
New Network Element Support
Table 4 identifies the new network element types supported in Cisco ANA 3.7.1.
Table 4 Network Element Support Added in Cisco ANA 3.7.1
Device
|
Network Element
|
Cisco 4700 Router
|
cisco4700
|
Cisco Access Server 5800
|
ciscoAS5800
|
Cisco ACE 4710 Switch
|
ciscoACE4710
|
Cisco Catalyst 2960-24TC Switch
|
c2960-24TC-L
|
Cisco Catalyst 4948E Switch
|
WS-C4948E
|
Cisco ISR 3925/K9 Router
|
ciscoISR3925
|
Cisco ISR 3945 Router
|
ciscoISR3945
|
Cisco ME-3600X-24FSM
|
ciscoME3600x24FSM
|
Cisco ME-3600X-24TSM
|
ciscoME3600x24TSM
|
Cisco ME-3800X-24FSM
|
ciscoME3800X24FSM
|
Cisco Nexus 7010 Switch
|
cevChassisN7Kc7010
|
Cisco Nexus 7018 Switch
|
cevChassisN7Kc7018
|
Cisco UBR 10012
|
ciscoUBR10012
|
Cisco UBR7246VXR
|
ciscoUBR7246VXR
|
CISCO2901/K9
|
cisco2901
|
CISCO2911/K9
|
cisco2911
|
CISCO2921/K9
|
cisco2921
|
CISCO2951/K9
|
cisco2951
|
New Module Support
Table 5 identifies the new module support available in Cisco ANA 3.7.1.
Table 5 Module Support Added in Cisco ANA 3.7.1
Device
|
Module Support Added in Cisco ANA 3.7.1
|
Cisco AS 5800 Series
|
AS5800-1FE-DSI
|
cevMAs5800MicaDmm
|
cevMAs5800-Dsc
|
cevMAs5800MicaHmm
|
cevMAs5800Dsp
|
cevMAs5800T1
|
cevMAs5800Dspm6c549
|
cevMAs5800T3
|
cevMAs5800E1
|
cevMAs5800Vcc
|
cevMAs5800FeDsi
|
Cisco ISR 2900 Series
|
GE-DCARD-ESW
|
PWR-2911-AC
|
HWIC-1GE-SFP
|
PWR-2921-51-AC
|
NM-16ESW-1GIG
|
SM-NM-ADPTR
|
NME-16ES-1G
|
Cisco ISR 3900 Series
|
C3900-SPE100/K9
|
GE-DCARD-ESW
|
C3900-SPE150/K9
|
HWIC-1GE-SFP
|
C3900-SPE200/K9
|
NM-16ESW-1GIG
|
C3900-SPE250/K9
|
PWR-3900-AC
|
Cisco 7600 Series
|
76-ES+T-20G
|
76-ES+T-4TGQ
|
76-ES+T-20GQ
|
X2-10GB-CX4
|
76-ES+T-2TG
|
X2-10GB-ER
|
76-ES+T-2TGQ
|
X2-10GB-LR
|
76-ES+T-40G
|
X2-10GB-LX4
|
76-ES+T-40GQ
|
X2-10GB-SR
|
76-ES+T-4TG
|
Cisco 10000 Series
|
ESR-1OC-12-ATM
|
10000-SIP-600
|
ESR-8E3/DS3
|
Cisco 12000 Series
|
SPA-1X10GE-L-ITUC
|
Cisco CRS-1 Series
|
4-10GBE-WL-XFP
|
CRS-ADVSVC-PLIM
|
8-10GBE-WL-XFP
|
XENPAK-10GB-LR+
|
Cisco ASR 1000 Series
|
SPA-1XCHOC12/DS0
|
Cisco ASR 9000 Series
|
A9K-8T-L
|
XFP-10GER-OC192IR
|
Cisco ME 3400 Series
|
GLC-BX-D
|
GLC-BX-U
|
Cisco ME 3600X
|
CWDM-SFP-1470
|
GLC-FE-100LX
|
CWDM-SFP-1490
|
GLC-LH-SM
|
CWDM-SFP-1510
|
GLC-SX-MM
|
CWDM-SFP-1530
|
GLC-T
|
CWDM-SFP-1550
|
GLC-ZX-SM
|
CWDM-SFP-1570
|
ME-FANTRAY
|
CWDM-SFP-1590
|
PWR-390W-AC
|
CWDM-SFP-1610
|
PWR-390W-DC
|
GLC-BX-D
|
SFP-10G-LR
|
GLC-BX-U
|
SFP-10G-LRM
|
GLC-FE-100BX-D
|
SFP-10G-SR
|
GLC-FE-100BX-U
|
SFP-GE-L
|
GLC-FE-100EX
|
SFP-GE-S
|
GLC-FE-100FX
|
Cisco ME 3800X
|
CWDM-SFP-1470
|
GLC-FE-100LX
|
CWDM-SFP-1490
|
GLC-LH-SM
|
CWDM-SFP-1510
|
GLC-SX-MM
|
CWDM-SFP-1530
|
GLC-T
|
CWDM-SFP-1550
|
GLC-ZX-SM
|
CWDM-SFP-1570
|
ME-FANTRAY
|
CWDM-SFP-1590
|
PWR-390W-AC
|
CWDM-SFP-1610
|
PWR-390W-DC
|
GLC-BX-D
|
SFP-10G-LR
|
GLC-BX-U
|
SFP-10G-LRM
|
GLC-FE-100BX-D
|
SFP-10G-SR
|
GLC-FE-100BX-U
|
SFP-GE-L
|
GLC-FE-100EX
|
SFP-GE-S
|
GLC-FE-100FX
|
Cisco MWR 2941 Devices
|
CWDM-SFP-1470
|
DWDM-SFP-4453
|
CWDM-SFP-1490
|
DWDM-SFP-4532
|
CWDM-SFP-1510
|
DWDM-SFP-4612
|
CWDM-SFP-1530
|
DWDM-SFP-4692
|
CWDM-SFP-1550
|
DWDM-SFP-4772
|
CWDM-SFP-1570
|
DWDM-SFP-4851
|
CWDM-SFP-1590
|
DWDM-SFP-4931
|
CWDM-SFP-1610
|
DWDM-SFP-5012
|
DWDM-SFP-3033
|
DWDM-SFP-5092
|
DWDM-SFP-3112
|
DWDM-SFP-5172
|
DWDM-SFP-3190
|
DWDM-SFP-5252
|
DWDM-SFP-3268
|
DWDM-SFP-5332
|
DWDM-SFP-3346
|
DWDM-SFP-5413
|
DWDM-SFP-3425
|
DWDM-SFP-5494
|
DWDM-SFP-3504
|
DWDM-SFP-5575
|
DWDM-SFP-3582
|
DWDM-SFP-5655
|
DWDM-SFP-3661
|
DWDM-SFP-5736
|
DWDM-SFP-3739
|
DWDM-SFP-5817
|
DWDM-SFP-3819
|
DWDM-SFP-5898
|
DWDM-SFP-3898
|
DWDM-SFP-5979
|
DWDM-SFP-3977
|
DWDM-SFP-6061
|
DWDM-SFP-4056
|
DWDM-SFP-6141
|
Cisco MWR 2941 Devices (cont.)
|
DWDM-SFP-4134
|
GLC-LX-SM-RGD
|
DWDM-SFP-4214
|
GLC-SX-SM-RGD
|
DWDM-SFP-4294
|
GLC-ZX-SM-RGD
|
DWDM-SFP-4373
|
SFP-GE-T
|
Cisco UBR7200 Series
|
UBR7200-NPE-G1
|
WS-G5484
|
UBR-MC28U
|
WS-G5486
|
UBR-MC28X
|
WS-G5487
|
Cisco UBR10000
|
10000-SIP-600
|
UBR10-MC5X20H-D
|
ESR-PRE4
|
UBR10-PWR-AC
|
SFP-GE-T
|
UBR10-PWR-DC
|
SPA-1X10GE-L-V2
|
XFP-10GER-OC192IR
|
SPA-24XDS-SFP
|
XFP-10GLR-OC192SR
|
UBR10-2XDS-SIP
|
XFP-10GZR-OC192LR
|
UBR10-5X20S-D
|
Cisco Catalyst 4900 Series
|
WS-X4908-10G-RJ45
|
Cisco Catalyst 6500 Series (IOS)
|
76-ES+T-20G
|
76-ES+T-40G
|
76-ES+T-2TG
|
76-ES+T-4TG
|
Cisco Nexus 7000 Series
|
GLC-SX-MM
|
N7K-M148GS-11
|
N7K-AC-7.5KW-US
|
N7K-M148GT-11
|
N7K-C7010-FAB-1
|
N7K-SUP1
|
N7K-C7018-FAB-1
|
SFP-10G-LR
|
N7K-C7018-FAN
|
SFP-10G-SR
|
N7K-M132XP-12
|
SFP-GE-S
|
New Software Version Support
Table 6 identifies the new software versions supported in Cisco ANA 3.7.1.
Table 6 Software Support Added in Cisco ANA 3.7.1
Product
|
Software
|
Version
|
Cisco 4924 ME
|
IOS
|
12.2(53)SG2
|
Cisco 7200 Series
|
Cisco IOS
|
12.2(28)SB8
|
12.2(33)SRC1
|
12.2(33)SRC2
|
12.2(33)SRC4
|
12.2(33)SRC5
|
Cisco 7200 Series (cont.)
|
Cisco IOS (cont.)
|
12.2(33)SRC6
|
12.2(33)SRD
|
12.2(33)SRD2
|
12.2(33)SRD3
|
12.2(33)SRD4
|
12.4(24)T
|
Cisco 7600 Series
|
Cisco IOS
|
12.2(33)SRC6
|
15.0(1)S
|
Cisco 10000 Series
|
Cisco IOS
|
12.2(33)SB8
|
12.2(33)XNE
|
Cisco 12000 Series
|
Cisco IOS
|
12.0(33)S6
|
12.0(32)S5
|
12.0(32)SY6b
|
Cisco ACE 4700
|
ACE Appliance SW
|
3.2
|
Cisco AS 5800 Series
|
Cisco IOS
|
12.1(11b)
|
Cisco ASR 1000 Series
|
Cisco IOS XE
|
2.6.0
|
3.1.0 S
|
Cisco ASR 9000 Series
|
Cisco IOS XR
|
3.9.1
|
Cisco Catalyst 2900 Series
|
IOS
|
12.2(25)SEE2
|
12.2(25)SEE3
|
Cisco Catalyst 3750 Metro Series
|
IOS
|
12.2(54)SE
|
Cisco Catalyst 4500 Series
|
IOS
|
12.2(54)SG
|
12.2(53)SG1
|
12.2(53)SG2
|
Cisco Catalyst 4900 Series
|
IOS
|
12.2(54)SG
|
12.2(53)SG1
|
Cisco CRS-1 Devices
|
Cisco IOS XR
|
3.8.4
|
Cisco ISR 2900 Series
|
Cisco IOS
|
15.1(1)T
|
Cisco ISR 3900 Series
|
Cisco IOS
|
15.1(T)
|
Cisco ME 3400 Series
|
IOS
|
12.2(54)SE
|
Cisco ME 3600X
|
IOS
|
12.2(52)EY
|
Cisco ME 3800X
|
UIS
|
12.2(52)EY
|
Cisco Nexus 7000 Series
|
NX-OS
|
4.2(2)
|
4.2(3)
|
Cisco UBR 7200 Series
|
Cisco IOS
|
12.3(21a)BC6
|
Cisco UBR 10000 Series
|
Cisco IOS
|
12.2(33)SCB2
|
12.2(33)SCB3
|
12.2(33)SCB6
|
Cisco XR 12000 Series
|
Cisco IOS XR
|
3.8.4
|
3.9.1
|
Network Elements and Features Validated for Cisco ANA Configuration and Image Management
The following tables list the devices, software, and features that have been validated with Cisco ANA Configuration and Image Management. While all Cisco IOS and Cisco IOS XR devices have the software required to support these functions, only the devices listed below have been validated. Keep this in mind if you use any devices not listed in Table 7.
Table 7 identifies the network elements and software that were validated for Cisco ANA Configuration and Image Management in Cisco ANA 3.7.1.
Table 7 NEs and Software Validated for Configuration and Image Management
Device
|
Network Element
|
Software
|
Software Version
|
Cisco MWR 2900 Series Mobile Wireless Routers
|
ciscoMWR2941
|
Cisco IOS
|
12.2(33)MRA
|
Cisco 3800 Series Routers
|
cisco3845
|
Cisco IOS
|
12.4(24)T1
|
Cisco 7200 Series Routers
|
cisco7206VXR
|
Cisco IOS
|
12.4(24)T
|
Cisco 7600 Series Routers
|
cisco7609S
cisco7613
|
Cisco IOS
|
12.2(18)SXF16
12.2(33)SRD4
|
Cisco ASR 1000 Series Aggregation Services Routers
|
ciscoASR1004
|
Cisco IOS
|
2.6.2
3.1.0S
|
Cisco ASR 9000 Series Aggregation Services Routers
|
ciscoASR9010 chassis
|
Cisco IOS
|
3.9.1
3.9.0
|
Cisco XR 12000 Series Routers
|
cisco12816
|
Cisco IOS XR
|
3.7.0
|
Cisco CRS-1 Carrier Routing System
|
Cisco CRS-1 4-slot Single Shelf System
|
Cisco IOS XR
|
3.6.0
|
Cisco ME 3400 Series Ethernet Access Switches
|
cisco340024TSA
ciscoMe3400g12CsA
|
Cisco IOS
|
12.2(25)SEG 3
12.2(53)SE
|
Cisco Catalyst 3750 Metro Series Switches
|
catalyst375024ME
|
Cisco IOS
|
12.2(52)SE
|
Cisco Catalyst 4500 Series Switches
|
catalyst4507R-E
catalyst4506E
|
Cisco IOS
|
12.2(53)SG
12.2(54)SG194
|
Cisco Catalyst 6500 Series Switches (IOS)
|
ciscoWSC6513
|
Cisco IOS
|
IOS 12.2(33)SXI3
|
Table 8 identifies the Cisco ANA Configuration and Image Management features that were validated on the devices listed in Table 7.
Table 8 Validated Configuration and Image Management Features
Function
|
Routers
|
Switches
|
MWR
2900
|
3800
|
7200
|
7600
|
ASR
1000
|
ASR
9000
|
XR
12000
|
CRS-1
|
ME
3400
|
3750 Metro
|
4500
|
6500 (IOS)
|
CM: Backup, Restore
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
CM: Synch Configs
|
X
|
X
|
X
|
X
|
X
|
—
|
—
|
—
|
X
|
X
|
X
|
X
|
NEIM: Distribute, Activate
|
X
|
X
|
X
|
X
|
X
|
—
|
—
|
—
|
X
|
X
|
X
|
X
|
NEIM Package Mgmt, Rollback, Commit
|
—
|
—
|
—
|
—
|
—
|
X
|
X
|
X
|
—
|
—
|
—
|
—
|
New Alarm, Trap, and Syslog Support
Cisco ANA 3.7.1 provides the following new features:
•Wrapped syslog support—Syslogs-on-traps are enabled for devices on which syslogs are disabled.
With wrapped syslog support, Cisco ANA can parse the clogMessageGenerated trap (OID 1.3.6.1.4.1.9.9.41.2.0.1), wherein the device sends the syslog within the trap as varbinds.
•Multisource event support—Cisco devices can send syslogs and traps from IP address sources other than the device management IP address. With multisource event support, Cisco ANA can handle these events that arrive from the alternate IP addresses.
For example, assume that a Cisco device has a management IP address of 10.10.10.10 and that Cisco ANA manages this device by using the management IP address. When the device sends syslogs and traps using another IP address, such as 10.1.1.1, Cisco ANA captures them, parses them, and displays them in the Cisco ANA GUI.
The following topics describe the new service alarms, trap support, and syslog support provided in Cisco ANA 3.7.1:
•Service Alarm Severity Change
•New Service Alarm Subtypes
•New Service Alarms
•New Trap Support
•New Syslog Support
Service Alarm Severity Change
In Cisco ANA 3.7.1, the severity for the Link Down Due to Admin Down service alarm has changed from Major to Minor.
New Service Alarm Subtypes
Cisco ANA 3.7.1 differentiates between certain alarms that are generated by an administrator action and those that are generated by a change in the operational state by providing new alarm subtypes with differing severities, depending on the cause.
Table 9 identifies the new alarm subtypes and severities for those alarms that are administratively down and those that are operationally down.
Table 9 New Alarm Subtypes in Cisco ANA 3.7.1
Alarm
|
New Alarm Subtype
|
Severity
|
BGP Link Down
|
BGP Link Down Due to Admin Down
|
Minor
|
BGP Link Down Due to Oper Down
|
Major
|
BGP Link Down VRF
|
BGP Link Down VRF Due to Admin
|
Minor
|
BGP Link Down VRF Due to Oper
|
Major
|
BGP Neighbor Loss
|
BGP Neighbor Loss Due to Admin
|
Minor
|
BGP Neighbor Loss Due to Oper
|
Major
|
BGP Neighbor Loss VRF
|
BGP Neighbor Loss VRF Due to Admin
|
Minor
|
BGP Neighbor Loss VRF Due to Oper
|
Major
|
Port Down
|
Port Down Due to Admin
|
Minor
|
Port Down Due to Oper
|
Major
|
In conjunction with the new alarm subtypes and severities, similar changes have been made to the severities of the associated syslogs and traps identified in Table 10.
Table 10 Changed Syslog and Trap Severities in Cisco ANA 3.7.1
Event
|
Event Subtype
|
Event Name
|
Severity
|
link down syslog
|
link down syslog
|
LINK-5-CHANGED
|
Minor
|
link down syslog
|
link down syslog
|
LINK-3-UPDOWN
|
Minor
|
line down syslog
|
line down syslog
|
LINEPROTO-5-UPDOWN
|
Minor
|
snmp link down trap
|
snmp link down
|
MIB2 V1 and V2 link down
|
Minor
|
New Service Alarms
Table 11 describes the service alarms that were added in Cisco ANA 3.7.1.
Table 11 Service Alarms Added in Cisco ANA 3.7.1
Alarm
|
Description
|
Clearing Alarm
|
BFD Connectivity Down
|
Alarm is triggered when BFD connection is lost
|
BFD Connectivity Up
|
BFD Neighbor Loss
|
Alarm is triggered when the connection to the BFD neighbor is lost.
|
BFD Neighbor Found
|
Carrier Grade NAT Translations Create Rate Higher Threshold Exceeded
|
Alarm is triggered when the number of translations created exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Translations Create Rate Threshold Normal
|
Carrier Grade NAT Translations Create Rate Lower Threshold Exceeded
|
Alarm is triggered when the number of translations created is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Translations Create Rate Threshold Normal
|
Carrier Grade NAT Translations Delete Rate Higher Threshold Exceeded
|
Alarm is triggered when the number of translations deleted exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Translations Delete Rate Threshold Normal
|
Carrier Grade NAT Translations Delete Rate Lower Threshold Exceeded
|
Alarm is triggered when the number of translations deleted is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Translations Delete Rate Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Forward Rate Higher Threshold Exceeded
|
Alarm is triggered when the number of packets forwarded exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Inside-to-Outside Forward Rate Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Forward Rate Lower Threshold Exceeded
|
Alarm is triggered when the number of packets forwarded is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Inside-to-Outside Forward Rate Threshold Normal
|
Carrier Grade NAT Outside-to-Inside Forward Rate Higher Threshold Exceeded
|
Alarm is triggered when the number of packets forwarded exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Outside-to-Inside Forward Rate Threshold Normal
|
Carrier Grade NAT Outside-to-Inside Forward Rate Lower Threshold Exceeded
|
Alarm is triggered when the number of packets forwarded is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Outside-to-Inside Forward Rate Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Drops Port Limit Higher Threshold Exceeded
|
Alarm is triggered when the number of packets dropped exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Inside-to-Outside Drops Port Limit Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Drops Port Limit Lower Threshold Exceeded
|
Alarm is triggered when the number of packets dropped is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Inside-to-Outside Drops Port Limit Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Drops System Limit Reached Higher Threshold Exceeded
|
Alarm is triggered when the number of packets dropped exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Inside-to-Outside Drops System Limit Reached Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Drops System Limit Reached Lower Threshold Exceeded
|
Alarm is triggered when the number of packets dropped is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Inside-to-Outside Drops System Limit Reached Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Drops Resource Depletion Higher Threshold Exceeded
|
Alarm is triggered when the number of packets dropped exceeds the higher threshold value. The default higher threshold value is 80.
|
Carrier Grade NAT Inside-to-Outside Drops Resource Depletion Threshold Normal
|
Carrier Grade NAT Inside-to-Outside Drops Resource Depletion Lower Threshold Exceeded
|
Alarm is triggered when the number of packets dropped is lower than the lower threshold value. The default lower threshold value is 40.
|
Carrier Grade NAT Inside-to-Outside Drops Resource Depletion Threshold Normal
|
Lag Admin Down
|
Alarm is triggered when the status changes due to administrative status change.
|
Lag Up
|
Lag Oper Down
|
Alarm is triggered when the status changes due to oper status change.
|
Lag Up
|
Lag Link Admin Down
|
Alarm is triggered when the LAG link is administratively down.
|
Lag Link Up
|
Lag Link Oper Down
|
Alarm is triggered when the LAG link is operatively down.
|
Lag Link Up
|
Local Switching Entry Down
|
Alarm is triggered when the status changes to down.
|
Local Switching Entry Up
|
High Priority Member Down
|
Alarm is triggered when the percentage of active links is greater than or equal to zero and less than or equal to the high priority threshold defined in the registry.
|
All Members Operationally Up
|
Medium Priority Member Down
|
Alarm is triggered when the percentage of active links is less than or equal to the medium priority threshold and greater than the high priority threshold defined in the registry.
|
All Members Operationally Up
|
Low Priority Member Down
|
Alarm is triggered when the percentage of active links is less than or equal to the low priority threshold and greater than the medium priority threshold defined in the registry.
|
All Members Operationally Up
|
OSPF Neighbor Down
|
Issued by the neighboring VNEs after the OSPF device status has changed to down.
|
OSPF Neighbor Up
|
SONET Path Link Down Due to Admin Down
|
Alarm is triggered when the administrative status changes.
|
SONET Path Link Up
|
SONET Path Link Down Due to Oper Down
|
Alarm is triggered when the oper status changes.
|
SONET Path Link Up
|
SONET Path Link Down Due to Card
|
Alarm is triggered when the path link is down due to card.
|
SONET Path Link Up
|
SONET Path Link Down on Unreachable
|
Alarm is triggered when the path link is down due to unreachable status.
|
SONET Path Link Up
|
SONET Path Port Down Due to Admin Down
|
Alarm is triggered when the administrative status changes.
|
SONET Path Port Up
|
SONET Path Port Down Due to Oper Down
|
Alarm is triggered when the oper status changes.
|
SONET Path Port Up
|
SONET Path Port Down Due to Card
|
Alarm is triggered when the path port is down due to card.
|
SONET Path Port Up
|
New Trap Support
The following sections identify the trap support added in Cisco ANA 3.7.1:
•Cisco ASR 9000 V1 Trap Support Added
•Cisco ASR 9000 V2 Trap Support Added
•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 ACE V1 Traps
•Cisco ACE V2/V3 Traps
•Cisco Nexus V1 Traps
•Cisco Nexus V2/V3 Traps
Cisco ASR 9000 V1 Trap Support Added
Table 12 identifies the Cisco ASR SNMPv1 trap support added in Cisco ANA 3.7.1.
Table 12 Cisco ASR V1 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Trap OID
|
Short Description
|
dot1agCfmFaultAlarm
|
1.0.8802.1.1.3, 1.3.111.2.802.1.1.8
|
dotlag CFM Fault Alarm
|
Cisco ASR 9000 V2 Trap Support Added
Table 13 identifies the Cisco ASR SNMPv2 trap support added in Cisco ANA 3.7.1.
Table 13 Cisco ASR V2 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Trap OID
|
Short Description
|
warmStart
|
1.3.6.1.6.3. 1.1.5.2
|
Warm start trap
|
dot1agCfmFaultAlarm
|
1.0.8802.1.1.3, 1.3.111.2.802.1.1.8
|
dotlag CFM Fault Alarm
|
Cisco IOS V1 Trap Support Added
Table 14 identifies the Cisco IOS SNMPv1 trap support added in Cisco ANA 3.7.1.
Table 14 Cisco IOS V1 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Enterprise OID
|
Short Description
|
vrrpTrapAuthFailure
|
1.3.6.1.2.1.68
|
Vrrp trap auth failure trap
|
vrrpTrapNewMaster
|
1.3.6.1.2.1.68
|
Vrrp trap new master trap
|
cdot3OamNonThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM Non-threshold crossing link fault trap
|
cdot3OamNonThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM Non-threshold crossing dying gasp trap
|
cdot3OamNonThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM Non-threshold crossing critical Link trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM threshold errored Symbol trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM threshold errored Frame Period trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM threshold errored Frame trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136
|
OAM threshold errored Frame Seconds trap
|
cbfDefineFileCompletion
|
1.3.6.1.4.1.9.9.81.2
|
CBF File operation state indicator
|
cbgpBackwardTransition
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP backward transition trap
|
cbgpFsmStateChange
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP down trap
|
cbgpFsmStateChange
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP established trap
|
cbgpPrefixThresholdExceeded
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP prefix threshold exceeded
|
cbgpPrefixThresholdClear
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP prefix threshold clear
|
ciscoConfigManEvent
|
1.3.6.1.4.1.9.9.43.2
|
Cisco Configuration management event notification
|
cefcFanTrayStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc fan-tray oper status down
|
cefcFanTrayStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc fan-tray oper status up
|
cefcFRUInserted
|
1.3.6.1.4.1.9.9.117.2
|
cefc FRU inserted
|
cefcFRURemoved
|
1.3.6.1.4.1.9.9.117.2
|
cefc FRU removed
|
cefcModuleStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc module oper status down
|
cefcModuleStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc module oper status up
|
cefcPowerStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc power status down
|
cefcPowerStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc power status up
|
entSensorThresholdNotification
|
1.3.6.1.4.1.9.9.91.2.0.1
|
sensor value crossed threshold in entSensorThresholdTable
|
ciscoFlashCopyCompletionTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco flash copy failed
|
ciscoFlashCopyCompletionTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco flash copy completion
|
ciscoFlashCopyCompletionTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco flash copy in progress
|
ciscoFlashDeviceChangeTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash device changed
|
ciscoFlashDeviceInsertedNotif
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash device inserted
|
ciscoFlashDeviceRemovedNotif
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash device removed
|
ciscoFlashDeviceInsertedNotifRev1
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash device inserted
|
ciscoFlashDeviceRemovedNotifRev1
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash device removed
|
ciscoFlashMiscOpCompletionTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash miscellaneous operation failed
|
ciscoFlashMiscOpCompletionTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash miscellaneous operation completed
|
ciscoFlashMiscOpCompletionTrap
|
1.3.6.1.4.1.9.9.10.1.3
|
Cisco Flash miscellaneous operation in progress
|
chassisAlarmOff
|
1.3.6.1.4.1.9.5
|
chassis alarm off
|
chassisAlarmOn
|
1.3.6.1.4.1.9.5
|
chassis alarm on
|
cPimNbrLoss
|
1.3.6.1.4.1.9.10.119
|
Cisco PIM neighbor lost
|
ciscoPingCompletion
|
1.3.6.1.4.1.9.9.16.2
|
Cisco ping completion
|
ciscoSonetSectionStatusChange
|
1.3.6.1.4.1.9.9.126
|
Cisco Sonet section status changed to error
|
ciscoSonetSectionStatusChange
|
1.3.6.1.4.1.9.9.126
|
Cisco Sonet section status changed to clear
|
ciscoSonetLineStatusChange
|
1.3.6.1.4.1.9.9.126
|
Cisco Sonet line status changed to error
|
ciscoSonetLineStatusChange
|
1.3.6.1.4.1.9.9.126
|
Cisco Sonet line status changed to clear
|
ciscoSonetPathStatusChange
|
1.3.6.1.4.1.9.9.126
|
Cisco Sonet path status changed to error
|
ciscoSonetPathStatusChange
|
1.3.6.1.4.1.9.9.126
|
Cisco Sonet path status changed to clear
|
mplsLdpFailedInitSessionThresholdExceeded
|
1.3.6.1.4.1.9.10.65.2
|
MPLS LDP init session threshold exceeded Trap
|
mplsLdpSessionDown
|
1.3.6.1.4.1.9.10.65.2
|
MPLS LDP session down Trap
|
mplsLdpSessionUp
|
1.3.6.1.4.1.9.10.65.2
|
MPLS LDP session up Trap
|
mplsTunnelUp
|
1.3.6.1.3.95.3
|
MPLS-TE tunnel up trap
|
mplsTunnelDown
|
1.3.6.1.3.95.3
|
MPLS-TE tunnel down trap
|
mplsTunnelRerouted
|
1.3.6.1.3.95.3
|
MPLS-TE tunnel rerouted trap
|
ciscoIpMRouteMissingHeartBeats
|
1.3.6.1.4.1.9.10.2.3.1
|
Failed receive multicast router heartbeat
|
ciscoRFProgressionNotif
|
1.3.6.1.4.1.9.9.176.2.
|
Cisco VSS Shelf 1 is Disabled
|
ciscoRFProgressionNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco VSS Shelf 1 is Standby Cold
|
ciscoRFProgressionNotif
|
1.3.6.1.4.1.9.9.176.2.
|
Cisco VSS Shelf 1 is Standby Hot
|
ciscoRFProgressionNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco VSS Shelf 2 is Disabled
|
ciscoRFProgressionNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco VSS Shelf 2 is Standby Cold
|
ciscoRFProgressionNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco VSS Shelf 2 is Standby Hot
|
cvsVSLConnectionChangeNotif
|
1.3.6.1.4.1.9.9.388
|
VSL Connection Changed: Down
|
cvsVSLConnectionChangeNotif
|
1.3.6.1.4.1.9.9.388
|
VSL Connection Change: Up
|
topologyChange
|
1.3.6.1.2.1.17
|
dot1qBridge trap
|
cEtherCfmCcMepUp
|
1.3.6.1.4.1.9.9.461.0
|
Mep up trap
|
cEtherCfmCcMepDown
|
1.3.6.1.4.1.9.9.461.0
|
Mep down trap
|
coldStart
|
1.3.6.1.2.1.11
|
Cold start trap
|
cHsrpStateChange
|
1.3.6.1.4.1.9.9.106.2
|
Cisco hsrp state standby
|
cHsrpStateChange
|
1.3.6.1.4.1.9.9.106.2
|
Cisco hsrp state non active
|
cHsrpStateChange
|
1.3.6.1.4.1.9.9.106.2
|
Cisco hsrp state active
|
ciscoEnvMonFanNotification
|
1.3.6.1.4.1.9.9.13.3
|
Cisco Environment Monitoring Fan Notification - Critical
|
ciscoEnvMonFanNotification
|
1.3.6.1.4.1.9.9.13.3
|
Cisco Environment Monitoring Fan Notification - Normal
|
ciscoEnvMonFanNotification
|
1.3.6.1.4.1.9.9.13.3
|
Cisco Environment Monitoring Fan Notification - Not Functioning
|
ciscoEnvMonFanNotification
|
1.3.6.1.4.1.9.9.13.3
|
Cisco Environment Monitoring Fan Notification - Not Present
|
ciscoEnvMonFanNotification
|
1.3.6.1.4.1.9.9.13.3
|
Cisco Environment Monitoring Fan Notification - Shutdown
|
ciscoEnvMonFanNotification
|
1.3.6.1.4.1.9.9.13.3
|
Cisco Environment Monitoring Fan Notification - Warning
|
ciscoEnvMonRedundantSupplyNotification
|
1.3.6.1.4.1.9.9.13.3
|
Redundant Supply State - Critical
|
ciscoEnvMonRedundantSupplyNotification
|
1.3.6.1.4.1.9.9.13.3
|
Redundant Supply State - Normal
|
ciscoEnvMonRedundantSupplyNotification
|
1.3.6.1.4.1.9.9.13.3
|
Redundant Supply State - Not Functioning
|
ciscoEnvMonRedundantSupplyNotification
|
1.3.6.1.4.1.9.9.13.3
|
Redundant Supply State - Not Present
|
ciscoEnvMonRedundantSupplyNotification
|
1.3.6.1.4.1.9.9.13.3
|
Redundant Supply State - Shutdown
|
ciscoEnvMonRedundantSupplyNotification
|
1.3.6.1.4.1.9.9.13.3
|
Redundant Supply State - Warning
|
newRoot
|
1.3.6.1.2.1.17
|
new root trap
|
stpxInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx port inconsistency discovered
|
stpxInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx port inconsistency resolved
|
stpxLoopInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx loop inconsistency discovered
|
stpxLoopInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx loop inconsistency resolved
|
stpxRootInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx root inconsistency discovered
|
stpxRootInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx root inconsistency resolved
|
vtpConfigRevNumberError
|
1.3.6.1.4.1.9.9.46.2
|
vtp configuration revision number error trap
|
vtpConfigDigestError
|
1.3.6.1.4.1.9.9.46.2
|
vtp configuration digest error trap
|
ciscoEnvMonShutdownNotification
|
1.3.6.1.4.1.9.9.13.3
|
cisco EnvMon Shutdown Notification Trap
|
caemTemperatureNotification
|
1.3.6.1.4.1.9.9.61.2
|
caem Temperature Notification Trap
|
caemVoltageNotification
|
1.3.6.1.4.1.9.9.61.2
|
caem Voltage Notification Trap
|
cmnMacChangedNotification
|
1.3.6.1.4.1.9.9.215.2
|
cmn Mac Changed Notification Trap
|
cmnMacMoveNotification
|
1.3.6.1.4.1.9.9.215.2
|
cmn Mac Move Notification Trap
|
vtpVersionOneDeviceDetected
|
1.3.6.1.4.1.9.9.46.2
|
vtp VersionOne Device Detected trap
|
vtpLocalModeChanged
|
1.3.6.1.4.1.9.9.46.2
|
vtp Local Mode Changed trap
|
vtpVersionInUseChanged
|
1.3.6.1.4.1.9.9.46.2
|
vtp VersionInUse Changed trap
|
vlanTrunkPortDynamicStatusChange
|
1.3.6.1.4.1.9.9.46.2
|
Vlan trunk port dynamic status changed to trunking
|
vlanTrunkPortDynamicStatusChange
|
1.3.6.1.4.1.9.9.46.2
|
Vlan trunk port dynamic status changed to not trunking
|
cpsSecureMacAddrViolation
|
1.3.6.1.4.1.9.9.315.0
|
cps Secure MacAddr Violation Trap
|
cpsIfVlanSecureMacAddrViolation
|
1.3.6.1.4.1.9.9.315.0
|
cps IfVlan Secure MacAddr Violation Trap
|
clcVlanMacLimitNotif
|
1.3.6.1.4.1.9.9.313
|
cisco L2 Control VlanMacLimit Notif Trap
|
clcVlanMacLimitHighNotif
|
1.3.6.1.4.1.9.9.313
|
cisco L2 Control VlanMacLimit High Notif Trap
|
clcIfMacLimitLowNotif
|
1.3.6.1.4.1.9.9.313
|
cisco L2 Control IfMacLimit Low Notif Trap
|
clcIfMacLimitHighNotif
|
1.3.6.1.4.1.9.9.313
|
cisco L2 Control IfMacLimit High Notif Trap
|
clcIfVlanMacLimitLowNotif
|
1.3.6.1.4.1.9.9.313
|
cisco L2 Control IfVlanMacLimit Low Notif Trap
|
clcIfVlanMacLimitHighNotif
|
1.3.6.1.4.1.9.9.313
|
cisco L2 Control IfVlanMacLimit High Notif Trap
|
csbSourceAlertEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC source alert off trap
|
csbSourceAlertEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC source alert on trap
|
csbSourceAlertEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC source alert informational trap
|
csbDynamicBlackListEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC dynamic blacklist trap
|
csbAdjacencyStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC adjacency state up trap
|
csbAdjacencyStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC adjacency state down trap
|
csbAdjacencyStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC adjacency state informational trap
|
csbServiceStateEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC service state up trap
|
csbServiceStateEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC service state down trap
|
csbServiceStateEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC service state informational trap
|
csbSystemCongestionAlarmEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC system congestion cleared trap
|
csbSystemCongestionAlarmEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC system congestion raised trap
|
csbSystemCongestionAlarmEvent
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC system congestion informational trap
|
csbSLAViolationRev1
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC SLA violation off trap
|
csbSLAViolationRev1
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC SLA violation on trap
|
csbSLAViolationRev1
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC SLA violation informational trap
|
csbRadiusConnectionStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC radius connection state up trap
|
csbRadiusConnectionStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC radius connection state down trap
|
csbRadiusConnectionStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC radius connection state informational trap
|
csbH248ControllerStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC H248 controller state up trap
|
csbH248ControllerStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC H248 controller state down trap
|
csbH248ControllerStatus
|
1.3.6.1.4.1.9.9.658
|
Cisco SBC H248 controller state informational trap
|
Cisco IOS V2/V3 Trap Support Added
Table 15 identifies the Cisco IOS SNMPv2/v3 trap support added in Cisco ANA 3.7.1.
Table 15 Cisco IOS V2/V3 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Trap OID
|
Short Description
|
cHsrpStateChange
|
1.3.6.1.4.1.9.9.1 06.2.0.1
|
Cisco hsrp state non active
|
vrrpTrapAuthFailure
|
1.3.6.1.2.1.68.0.2
|
Vrrp trap auth failure trap
|
vrrpTrapNewMaster
|
1.3.6.1.2.1.68.0.1
|
Vrrp trap new master trap
|
cdot3OamNonThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.2
|
OAM Non-threshold crossing link fault trap
|
cdot3OamNonThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.2
|
OAM Non-threshold crossing dying gasp trap
|
cdot3OamNonThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.2
|
OAM Non-threshold crossing critical Link trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.1
|
OAM threshold errored Symbol trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.1
|
OAM threshold errored Frame Period trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.1
|
OAM threshold errored Frame trap
|
cdot3OamThresholdEvent
|
1.3.6.1.4.1.9.10.136.0.1
|
OAM threshold errored Frame Seconds trap
|
ciscoEnvMonSuppStatusChangeNotif
|
1.3.6.1.4.1.9.9.13.3.0.9
|
Power Supply - Critical
|
ciscoEnvMonSuppStatusChangeNotif
|
1.3.6.1.4.1.9.9.13.3.0.9
|
Power Supply - Normal
|
ciscoEnvMonSuppStatusChangeNotif
|
1.3.6.1.4.1.9.9.13.3.0.9
|
Power Supply - Not Functioning
|
ciscoEnvMonSuppStatusChangeNotif
|
1.3.6.1.4.1.9.9.13.3.0.9
|
Power Supply - Not Present
|
ciscoEnvMonSuppStatusChangeNotif
|
1.3.6.1.4.1.9.9.13.3.0.9
|
Poser Supply - Shutdown
|
ciscoEnvMonSuppStatusChangeNotif
|
1.3.6.1.4.1.9.9.13.3.0.9
|
Power Supply - Warning
|
Cisco IOS XR V1 Trap Support Added
Table 16 identifies the Cisco IOS XR SNMPv1 trap support added in Cisco ANA 3.7.1.
Table 16 Cisco IOS XR V1 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Enterprise OID
|
Short Description
|
vrrpTrapAuthFailure
|
1.3.6.1.2.1.68
|
Vrrp trap auth failure trap
|
vrrpTrapNewMaster
|
1.3.6.1.2.1.68
|
Vrrp trap new master trap
|
ciscoBfdSessDown
|
1.3.6.1.4.1.9.10.137
|
Cisco bfd session down trap
|
ciscoBfdSessUp
|
1.3.6.1.4.1.9.10.137
|
Cisco bfd session up trap
|
cbgpBackwardTransition
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP backward transition trap
|
cbgpFsmStateChange
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP down trap
|
cbgpFsmStateChange
|
1.3.6.1.4.1.9.9.187
|
Cisco BGP established trap
|
ccCopyCompletion
|
1.3.6.1.4.1.9.9.96.2.1
|
Config-copy request completion
|
cfhBundleDownedLinkNotification
|
1.3.6.1.4.1.9.9.257
|
cfh bundle link status down
|
cfhBundleDownedLinkNotification
|
1.3.6.1.4.1.9.9.257
|
cfh bundle link status up
|
cfhBundleStateNotification
|
1.3.6.1.4.1.9.9.257
|
cfh Fabric bundle operational state changed to Down
|
cfhBundleStateNotification
|
1.3.6.1.4.1.9.9.257
|
cfh Fabric bundle operational state changed to Up
|
cfhPlaneStateNotification
|
1.3.6.1.4.1.9.9.257
|
cfh Fabric plane status down
|
cfhPlaneStateNotification
|
1.3.6.1.4.1.9.9.257
|
cfh Fabric plane status up
|
cpwVcUp
|
1.3.6.1.4.1.9.10.106.2
|
Pseudo wire tunnel up
|
cpwVcDown
|
1.3.6.1.4.1.9.10.106.2
|
Pseudo wire tunnel down
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - Unsupported
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - None
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - Not Known
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - User Initiated
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - User Forced
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - Active Unit Failed
|
ciscoRFSwactNotif
|
1.3.6.1.4.1.9.9.176.2
|
Cisco RF Swap Status - Active Unit Removed
|
Cisco IOS XR V2/V3 Trap Support Added
Table 17 identifies the Cisco IOS XR SNMPv2/v3 trap support added in Cisco ANA 3.7.1.
Table 17 Cisco IOS XR V2/V3 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Trap OID
|
Short Description
|
vrrpTrapAuthFailure
|
1.3.6.1.2.1.68.0.2
|
VRRP trap auth failure trap
|
vrrpTrapNewMaster
|
1.3.6.1.2.1.68.0.1
|
VRRP trap new master trap
|
ciscoBfdSessDown
|
1.3.6.1.4.1.9.10.137.0.2
|
Cisco BFD session down trap
|
ciscoBfdSessUp
|
1.3.6.1.4.1.9.10.137.0.1
|
Cisco BFD session up trap
|
Cisco MIB2 V1 Trap Support Added
Table 18 identifies the Cisco MIB2 V1 trap support added in Cisco ANA 3.7.1.
Table 18 Cisco MIB2 V1 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Enterprise OID
|
Short Description
|
coldStart
|
1.3.6.1.6.3.1.1.5
|
Cold start trap
|
bgpBackwardTransition
|
1.3.6.1.2.1.15.7
|
BGP down trap
|
bgpEstablished
|
1.3.6.1.2.1.15.7
|
BGP established trap
|
authenticationFailure
|
1.3.6.1.6.3.1.1.5
|
SNMP authentication failure
|
ospfIfStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF interface state changed to Down
|
ospfIfStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF interface state changed to Up
|
ospfVirtIfStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual interface state changed to Down
|
ospfNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF neighbor state down
|
ospfNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF neighbor state up
|
ospfVirtNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual neighbor state down
|
ospfVirtNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual neighbor state up
|
ospfIfConfigError
|
1.3.6.1.2.1.14.16.2
|
OSPF interface configuration error
|
ospfVirtIfConfigError
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual interface configuration error
|
ospfIfAuthFailure
|
1.3.6.1.2.1.14.16.2
|
OSPF interface authentication failure
|
ospfVirtIfAuthFailure
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual interface authentication failure
|
ospfIfRxBadPacket
|
1.3.6.1.2.1.14.16.2
|
OSPF bad packet received
|
ospfVirtIfRxBadPacket
|
1.3.6.1.2.1.14.16.2
|
OSPF bad packet received on virtual interface
|
ospfTxRetransmit
|
1.3.6.1.2.1.14.16.2
|
OSPF packet retransmitted
|
ospfVirtIfTxRetransmit
|
1.3.6.1.2.1.14.16.2
|
OSPF packet retransmitted on virtual interface
|
ospfOriginateLsa
|
1.3.6.1.2.1.14.16.2
|
OSPF new LSA originated
|
ospfMaxAgeLsa
|
1.3.6.1.2.1.14.16.2
|
OSPF LSA aged to MaxAge
|
mteEventSetFailure
|
1.3.6.1.2.1.88.2
|
mte event set failure
|
mteTriggerFalling
|
1.3.6.1.2.1.88.2
|
Cisco mte trigger falling
|
mteTriggerFired
|
1.3.6.1.2.1.88.2
|
mte trigger fired
|
mteTriggerRising
|
1.3.6.1.2.1.88.2
|
Cisco mte trigger rising
|
entConfigChange
|
1.3.6.1.2.1.47.2
|
Entity table configuration changed
|
ipv6IfStateChange
|
1.3.6.1.2.1.55.2
|
ipv6 interface state changed
|
mplsL3VpnNumVrfRouteMaxThreshCleared
|
1.3.6.1.2.1.10.166.11
|
mpls l3 vpn numvrf routemax thresh cleared Trap
|
mplsL3VpnVrfDown
|
1.3.6.1.2.1.10.166.11
|
mpls l3 vpn vrf Down Trap
|
mplsL3VpnVrfNumVrfRouteMaxThreshExceeded
|
1.3.6.1.2.1.10.166.11
|
mpls l3 vpn vrf numvrf routemax thresh exceeded Trap
|
mplsL3VpnVrfRouteMidThreshExceeded
|
1.3.6.1.2.1.10.166.11
|
mpls l3 vpn vrf routemid thresh exceeded Trap
|
mplsL3VpnVrfUp
|
1.3.6.1.2.1.10.166.11
|
mpls l3 vpn vrf Up Trap
|
mplsLdpInitSessionThresholdExceeded
|
1.3.6.1.2.1.10.166.4
|
MPLS LDP init session threshold exceeded Trap
|
mplsLdpSessionDown
|
1.3.6.1.2.1.10.166.4
|
MPLS LDP session down Trap
|
mplsLdpSessionUp
|
1.3.6.1.2.1.10.166.4
|
MPLS LDP session up Trap
|
mplsTunnelRerouted
|
1.3.6.1.2.1.10.166.3
|
MPLS-TE tunnel rerouted trap
|
mplsTunnelReoptimized
|
1.3.6.1.2.1.10.166.3
|
MPLS-TE tunnel reoptimized trap
|
mplsTunnelDown
|
1.3.6.1.2.1.10.166.3
|
MPLS-TE tunnel down
|
mplsTunnelUp
|
1.3.6.1.2.1.10.166.3
|
MPLS-TE tunnel up
|
Cisco ACE V1 Traps
Table 19 identifies the Cisco Application Control Engine (ACE) SNMPv1 trap support added in Cisco ANA 3.7.1.
Table 19 CIsco ACE V1 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Enterprise OID
|
Short Description
|
cesRealServerStateUp
|
1.3.6.1.4.1.9.9.470
|
ces real server state up trap
|
cesRealServerStateDown
|
1.3.6.1.4.1.9.9.470
|
ces real server state down trap
|
cesRealServerStateChange
|
1.3.6.1.4.1.9.9.470
|
ces real server state change trap
|
cesRserverStateUp
|
1.3.6.1.4.1.9.9.470
|
ces R server state up trap
|
cesRserverStateDown
|
1.3.6.1.4.1.9.9.470
|
ces R server state down trap
|
cesRserverStateChange
|
1.3.6.1.4.1.9.9.470
|
ces R server state change trap
|
ciscoSlbVServerVIPStateChange
|
1.3.6.1.4.1.9.9.161.2
|
cisco sib V server VIP state change trap
|
ciscoSlbVServerStateChange
|
1.3.6.1.4.1.9.9.161.2
|
cisco sib V server state change trap
|
clmLicenseExpiryNotify
|
1.3.6.1.4.1.9.9.369.3
|
clm license expiry notify trap
|
clmLicenseFileMissingNotify
|
1.3.6.1.4.1.9.9.369.3
|
clm license file missing notify trap
|
clmLicenseExpiryWarningNotify
|
1.3.6.1.4.1.9.9.369.3
|
clm license expiry warning notify trap
|
Cisco ACE V2/V3 Traps
Table 20 identifies the Cisco Application Control Engine (ACE) SNMPv2/v3 trap support added in Cisco ANA 3.7.1.
Table 20 Cisco ACE V2/V3 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Trap OID
|
Short Description
|
linkDown
|
1.3.6.1.6.3.1.1.5.3
|
SNMP Link down
|
linkUp
|
1.3.6.1.6.3.1.1.5.4
|
SNMP Link up
|
cesRealServerStateUp
|
1.3.6.1.4.1.9.9.470.0.1
|
ces real server state up trap
|
cesRealServerStateDown
|
1.3.6.1.4.1.9.9.470.0.2
|
ces real server state down trap
|
cesRealServerStateChange
|
1.3.6.1.4.1.9.9.470.0.3
|
ces real server state change trap
|
cesRserverStateUp
|
1.3.6.1.4.1.9.9.470.0.4
|
ces R server state up trap
|
cesRserverStateDown
|
1.3.6.1.4.1.9.9.470.0.5
|
ces R server state down trap
|
cesRserverStateChange
|
1.3.6.1.4.1.9.9.470.0.6
|
ces R server state change trap
|
ciscoSlbVServerVIPStateChange
|
1.3.6.1.4.1.9.9.161.2.0.6
|
cisco sib V server VIP state change trap
|
ciscoSlbVServerStateChange
|
1.3.6.1.4.1.9.9.161.2.0.5
|
cisco sib V server state change trap
|
clmLicenseExpiryNotify
|
1.3.6.1.4.1.9.9.369.3.0.1
|
clm license expiry notify trap
|
clmLicenseFileMissingNotify
|
1.3.6.1.4.1.9.9.369.3.0.3
|
clm license file missing notify trap
|
clmLicenseExpiryWarningNotify
|
1.3.6.1.4.1.9.9.369.3.0.4
|
clm license expiry warning notify trap
|
Cisco Nexus V1 Traps
Table 21 identifies the Cisco Nexus SNMPv1 trap support added in Cisco ANA 3.7.1.
Table 21 Cisco Nexus V1 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Enterprise OID
|
Short Description
|
bgpEstablished
|
1.3.6.1.2.1.15.7
|
BGP established trap
|
bgpBackwardTransition
|
1.3.6.1.2.1.15.7
|
BGP down trap
|
newRoot
|
1.3.6.1.2.1.17
|
new root trap
|
topologyChange
|
1.3.6.1.2.1.17
|
Spanning Tree Topology Changed
|
cefcModuleStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc module oper status down
|
cefcModuleStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc module oper status up
|
cefcPowerStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc power status down
|
cefcPowerStatusChange
|
1.3.6.1.4.1.9.9.117.2
|
cefc power status up
|
cefcFRUInserted
|
1.3.6.1.4.1.9.9.117.2
|
cefc FRU inserted
|
cefcFRURemoved
|
1.3.6.1.4.1.9.9.117.2
|
cefc FRU removed
|
entSensorThresholdNotification
|
1.3.6.1.4.1.9.9.91.2.0
|
sensor value crossed threshold in entSensorThresholdTable
|
cpsIfVlanSecureMacAddrViolation
|
1.3.6.1.4.1.9.9.315
|
cps IfVlan Secure MacAddr Violation Trap
|
cpsSecureMacAddrViolation
|
1.3.6.1.4.1.9.9.315
|
cps Secure MacAddr Violation Trap
|
stpxInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
Stpx Pvid Inconsistency Trap
|
stpxInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
Stpx Type Inconsistency Trap
|
stpxLoopInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx loop inconsistency discovered
|
stpxLoopInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx loop inconsistency resolved
|
stpxRootInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx root inconsistency discovered
|
stpxRootInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2
|
stpx root inconsistency resolved
|
linkDown
|
1.3.6.1.6.3.1.1.5
|
SNMP Link down
|
linkUp
|
1.3.6.1.6.3.1.1.5
|
SNMP Link up
|
risingAlarm
|
1.3.6.1.2.1.16
|
RMON Rising Alarm
|
fallingAlarm
|
1.3.6.1.2.1.16
|
RMON Falling Alarm
|
coldStart
|
1.3.6.1.6.3.1.1.5
|
Cold start trap
|
ospfVirtIfStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual interface state changed to Down
|
ospfNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF neighbor state down
|
ospfNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF neighbor state up
|
ospfVirtNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual neighbor state down
|
ospfVirtNbrStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual neighbor state up
|
ospfIfConfigError
|
1.3.6.1.2.1.14.16.2
|
OSPF interface configuration error
|
ospfVirtIfConfigError
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual interface configuration error
|
ospfIfAuthFailure
|
1.3.6.1.2.1.14.16.2
|
OSPF interface authentication failure
|
ospfVirtIfAuthFailure
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual interface authentication failure
|
ospfIfRxBadPacket
|
1.3.6.1.2.1.14.16.2
|
OSPF bad packet received
|
ospfVirtIfRxBadPacket
|
1.3.6.1.2.1.14.16.2
|
OSPF bad packet received on virtual interface
|
ospfTxRetransmit
|
1.3.6.1.2.1.14.16.2
|
OSPF packet retransmitted
|
ospfVirtIfTxRetransmit
|
1.3.6.1.2.1.14.16.2
|
OSPF packet retransmitted on virtual interface
|
ospfOriginateLsa
|
1.3.6.1.2.1.14.16.2
|
OSPF new LSA originated
|
ospfMaxAgeLsa
|
1.3.6.1.2.1.14.16.2
|
OSPF LSA aged to MaxAge
|
ospfLsdbOverflow
|
1.3.6.1.2.1.14.16.2
|
OSPF lsdb overflow trap
|
ospfLsdbApproachingOverflow
|
1.3.6.1.2.1.14.16.2
|
OSPF lsdb approaching overflow trap
|
ospfIfStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF interface state changed to Down
|
ospfIfStateChange
|
1.3.6.1.2.1.14.16.2
|
OSPF interface state changed to Up
|
ospfNssaTranslatorStatusChange
|
1.3.6.1.2.1.14.16.2
|
OSPF NSSA translator status change trap
|
ospfRestartStatusChange
|
1.3.6.1.2.1.14.16.2
|
OSPF restart status change trap
|
ospfNbrRestartHelperStatusChange
|
1.3.6.1.2.1.14.16.2
|
OSPF neighbor restart helper status change trap
|
ospfVirtNbrRestartHelperStatusChange
|
1.3.6.1.2.1.14.16.2
|
OSPF virtual neighbor restart helper status change trap
|
Cisco Nexus V2/V3 Traps
Table 22 identifies the Cisco Nexus SNMPv2/v3 trap support added in Cisco ANA 3.7.1.
Table 22 Cisco Nexus V2/V3 Trap Support Added in Cisco ANA 3.7.1
Trap Name
|
Trap OID
|
Short Description
|
bgpEstablished
|
1.3.6.1.2.1.15.7.1
|
BGP established trap
|
bgpBackwardTransition
|
1.3.6.1.2.1.15.7.2
|
BGP down trap
|
newRoot
|
1.3.6.1.2.1.17.1
|
new root trap
|
topologyChange
|
1.3.6.1.2.1.17.2
|
Spanning Tree Topology Changed
|
cefcModuleStatusChange
|
1.3.6.1.4.1.9.9.117.2.1
|
cefc module oper status down
|
cefcModuleStatusChange
|
1.3.6.1.4.1.9.9.117.2.1
|
cefc module oper status up
|
cefcPowerStatusChange
|
1.3.6.1.4.1.9.9.117.2.2
|
cefc power status down
|
cefcPowerStatusChange
|
1.3.6.1.4.1.9.9.117.2.2
|
cefc power status up
|
cefcFRUInserted
|
1.3.6.1.4.1.9.9.117.2.3
|
cefc FRU inserted
|
cefcFRURemoved
|
1.3.6.1.4.1.9.9.117.2.4
|
cefc FRU removed
|
entSensorThresholdNotification
|
1.3.6.1.4.1.9.9.91.2.0.1
|
sensor value crossed threshold in entSensorThresholdTable
|
cpsIfVlanSecureMacAddrViolation
|
1.3.6.1.4.1.9.9.315.3
|
cps IfVlan Secure MacAddr Violation Trap
|
cpsSecureMacAddrViolation
|
1.3.6.1.4.1.9.9.315.1
|
cps Secure MacAddr Violation Trap
|
stpxInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2.1
|
Stpx Pvid Inconsistency Trap
|
stpxInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2.1
|
Stpx Type Inconsistency Trap
|
stpxLoopInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2.3
|
stpx loop inconsistency discovered
|
stpxLoopInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2.3
|
stpx loop inconsistency resolved
|
stpxRootInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2.2
|
stpx root inconsistency discovered
|
stpxRootInconsistencyUpdate
|
1.3.6.1.4.1.9.9.82.2.2
|
stpx root inconsistency resolved
|
linkDown
|
1.3.6.1.6.3.1.1.5.3
|
SNMP Link down
|
linkUp
|
1.3.6.1.6.3.1.1.5.4
|
SNMP Link up
|
risingAlarm
|
1.3.6.1.2.1.16.0.1
|
RMON Rising Alarm
|
fallingAlarm
|
1.3.6.1.2.1.16.0.2
|
RMON Falling Alarm
|
coldStart
|
1.3.6.1.6.3.1.1.5.1
|
Cold start trap
|
ospfVirtIfStateChange
|
1.3.6.1.2.1.14.16.2.1
|
OSPF virtual interface state changed to Down
|
ospfNbrStateChange
|
1.3.6.1.2.1.14.16.2.2
|
OSPF neighbor state down
|
ospfNbrStateChange
|
1.3.6.1.2.1.14.16.2.2
|
OSPF neighbor state up
|
ospfVirtNbrStateChange
|
1.3.6.1.2.1.14.16.2.3
|
OSPF virtual neighbor state down
|
ospfVirtNbrStateChange
|
1.3.6.1.2.1.14.16.2.3
|
OSPF virtual neighbor state up
|
ospfIfConfigError
|
1.3.6.1.2.1.14.16.2.4
|
OSPF interface configuration error
|
ospfVirtIfConfigError
|
1.3.6.1.2.1.14.16.2.5
|
OSPF virtual interface configuration error
|
ospfIfAuthFailure
|
1.3.6.1.2.1.14.16.2.6
|
OSPF interface authentication failure
|
ospfVirtIfAuthFailure
|
1.3.6.1.2.1.14.16.2.7
|
OSPF virtual interface authentication failure
|
ospfIfRxBadPacket
|
1.3.6.1.2.1.14.16.2.8
|
OSPF bad packet received
|
ospfVirtIfRxBadPacket
|
1.3.6.1.2.1.14.16.2.9
|
OSPF bad packet received on virtual interface
|
ospfTxRetransmit
|
1.3.6.1.2.1.14.16.2.10
|
OSPF packet retransmitted
|
ospfVirtIfTxRetransmit
|
1.3.6.1.2.1.14.16.2.11
|
OSPF packet retransmitted on virtual interface
|
ospfOriginateLsa
|
1.3.6.1.2.1.14.16.2.12
|
OSPF new LSA originated
|
ospfMaxAgeLsa
|
1.3.6.1.2.1.14.16.2.13
|
OSPF LSA aged to MaxAge
|
ospfLsdbOverflow
|
1.3.6.1.2.1.14.16.2.14
|
OSPF lsdb overflow trap
|
ospfLsdbApproachingOverflow
|
1.3.6.1.2.1.14.16.2.15
|
OSPF lsdb approaching overflow trap
|
ospfIfStateChange
|
1.3.6.1.2.1.14.16.2.16
|
OSPF interface state changed to Down
|
ospfIfStateChange
|
1.3.6.1.2.1.14.16.2.16
|
OSPF interface state changed to Up
|
ospfNssaTranslatorStatusChange
|
1.3.6.1.2.1.14.16.2.17
|
OSPF NSSA translator status change trap
|
ospfRestartStatusChange
|
1.3.6.1.2.1.14.16.2.18
|
OSPF restart status change trap
|
ospfNbrRestartHelperStatusChange
|
1.3.6.1.2.1.14.16.2.19
|
OSPF neighbor restart helper status change trap
|
ospfVirtNbrRestartHelperStatusChange
|
1.3.6.1.2.1.14.16.2.20
|
OSPF virtual neighbor restart helper status change trap
|
New Syslog Support
The following topics identify the syslog support added in Cisco ANA 3.7.1:
•Cisco ASR 9000 Syslog Support Added
•Cisco IOS Syslog Support Added
•Cisco IOS XR Syslog Support Added
•Cisco ACE Syslog Support Added
•Cisco Nexus Syslog Support Added
Cisco ASR 9000 Syslog Support Added
Table 23 identifies the Cisco ASR syslog support added in Cisco ANA 3.7.1.
Table 23 Cisco ASR 9000 Syslog Support Added in Cisco ANA 3.7.1
Syslog Name
|
Short Description
|
Severity
|
L2-ELO-6-INTF_REMOTE_LOOPBACK
|
Ethernet OAM Remote loopback session stopped Syslog
|
Minor
|
L2-ELO-6-INTF_REMOTE_LOOPBACK
|
Ethernet OAM Remote loopback session started Syslog
|
Minor
|
L2-ELO-6-INTF_REMOTE_LOOPBACK
|
Ethernet OAM Local loopback session stopped Syslog
|
Minor
|
L2-ELO-6-INTF_REMOTE_LOOPBACK
|
Ethernet OAM Local loopback session started Syslog
|
Minor
|
L2-ELO-6-INTF_SESSION_DOWN
|
Ethernet OAM Session down Syslog
|
Informational
|
L2-ELO-6-INTF_SESSION_DOWN
|
Ethernet OAM Session up Syslog
|
Informational
|
L2-CFM-6-CC_ERROR
|
CFM cc error syslog
|
Informational
|
L2-CFM-6-CC_ERROR
|
CFM cc error cleared syslog
|
Clearing
|
Cisco IOS Syslog Support Added
Table 24 identifies the Cisco IOS syslog support added in Cisco ANA 3.7.1.
Table 24 Cisco IOS Syslog Support Added in Cisco ANA 3.7.1
Syslog Name
|
Short Description
|
Severity
|
ETHERNET_OAM-3-LOOPBACK_ERROR
|
Ethernet OAM Loopback Error syslog
|
Informational
|
ETHERNET_OAM-5-LINK_MONITOR
|
Ethernet OAM Link Monitor syslog
|
Informational
|
ETHERNET_OAM-5-LINK_MONITOR_HT_CROSS
|
Ethernet OAM Link Monitor high threshold syslog
|
Informational
|
ETHERNET_OAM-6-(ENTER|EXIT)_SESSION
|
Ethernet OAM exited the session
|
Informational
|
ETHERNET_OAM-6-(ENTER|EXIT)_SESSION
|
Ethernet OAM entered the session
|
Informational
|
ETHERNET_OAM-6-LINK_TIMEOUT
|
Ethernet OAM Link timeout Syslog
|
Informational
|
VRRP-6-STATECHANGE
|
VRRP backup to master syslog
|
Informational
|
VRRP-6-STATECHANGE
|
VRRP master to backup syslog
|
Informational
|
ETHER_LMI-6-MISMATCHED_VLAN_(CONFIGURED|NOT_CONFIGURED)
|
ELMI Vlan configured syslog
|
Clearing
|
ETHER_LMI-6-MISMATCHED_VLAN_(CONFIGURED|NOT_CONFIGURED)
|
ELMI Vlan not configured syslog
|
Minor
|
PM-4-ERR_(DISABLE|RECOVER)_VP
|
ELMI Vlan disabled syslog
|
Minor
|
PM-4-ERR_(DISABLE|RECOVER)_VP
|
ELMI Vlan enabled syslog
|
Clearing
|
ETHERNET_OAM-6-RFI-Dyinggasp
|
EOAM RFI dying gasp syslog - admin shutdown on peer
|
Minor
|
ETHERNET_OAM-6-RFI-Dyinggasp
|
EOAM RFI dying gasp syslog - no ethernet oam
|
Minor
|
ETHERNET_OAM-6-RFI-Dyinggasp
|
EOAM RFI dying gasp syslog - admin reload on peer
|
Minor
|
ETHERNET_OAM-6-RFI-Dyinggasp
|
EOAM RFI dying gasp syslog - no org specific TLV
|
Minor
|
ETHERNET_OAM-6-RFI_CLEAR-Dyinggasp
|
Eoam RFI dying gasp clear syslog
|
Clearing
|
ETHERNET_OAM-6-RFI-linkfault
|
EOAM RFI link fault syslog
|
Minor
|
ETHERNET_OAM-6-RFI_CLEAR-linkfault
|
EOAM RFI link fault clear syslog
|
Clearing
|
PM-4-ERR_(DISABLE|RECOVER)
|
PM Error disable syslog
|
Major
|
PM-4-ERR_(DISABLE|RECOVER)
|
PM Error recover syslog
|
Clearing
|
PM-SP-4-ERR_(DISABLE|RECOVER)
|
PM SP Error disable syslog
|
Major
|
ETHERNET_OAM-6-LOOPBACK
|
Eoam entered master loopback mode syslog
|
Minor
|
ETHERNET_OAM-6-LOOPBACK
|
Eoam exited master loopback mode syslog
|
Minor
|
ETHERNET_OAM-6-LOOPBACK
|
Eoam entered slave loopback mode syslog
|
Minor
|
ETHERNET_OAM-6-LOOPBACK
|
Eoam exited slave loopback mode syslog
|
Minor
|
TRANSCEIVER-DFC3-6-INSERTED
|
Transceiver inserted syslog
|
Clearing
|
TRANSCEIVER-DFC3-6-REMOVED
|
Transceiver removed syslog
|
Major
|
OIR-SP-6-INSCARD
|
card in syslog
|
Clearing
|
OIR-SP-6-REMCARD
|
card out syslog
|
Major
|
Cisco IOS XR Syslog Support Added
Table 25 identifies the Cisco IOS XR syslog support added in Cisco ANA 3.7.1.
Table 25 Cisco IOS XR Syslog Support Added in Cisco ANA 3.7.1
Syslog Name
|
Short Description
|
Severity
|
ROUTING-ISIS-4-ADJCHANGE
|
routing ISIS neighbor down syslog
|
Major
|
ROUTING-ISIS-4-ADJCHANGE
|
routing ISIS neighbor up syslog
|
Clearing
|
IP-VRRP-6-INFO_STATECHANGE
|
Backup to Master change syslog
|
Informational
|
IP-VRRP-6-INFO_STATECHANGE
|
Master to Backup change syslog
|
Informational
|
IP-STANDBY-6-INFO_STATECHANGE
|
IP standby state change syslog
|
Minor
|
IP-STANDBY-6-INFO_STATECHANGE
|
IP standby state restored syslog
|
Clearing
|
L2-DWDM-5-SRLG_OVERFLOW
|
DWDM5 SRLG OVERFLOW syslog
|
Warning
|
Cisco ACE Syslog Support Added
Table 26 identifies the Cisco ACE syslog support added in Cisco ANA 3.7.1.
Table 26 Cisco ACE Syslog Support Added in Cisco ANA 3.7.1
Syslog Name
|
Short Description
|
Severity
|
LINK-5-CHANGED
|
Link down syslog
|
Minor
|
LINK-5-CHANGED
|
Link up syslog
|
Clearing
|
LINK-3-UPDOWN
|
Link down syslog
|
Minor
|
LINK-3-UPDOWN
|
Link up syslog
|
Clearing
|
ACE-1-106021
|
Deny protocol reverse path check
|
Major
|
ACE-1-106028
|
Access rule memory exhausted
|
Major
|
ACE-1-444006
|
License manager exiting
|
Major
|
ACE-1-456029
|
The ACE attempted to start or set up the application acceleration core daemon process
|
Major
|
ACE-1-456078
|
Critical shared memory setup failure
|
Major
|
ACE-1-456080
|
Critical Semaphore related errors
|
Major
|
ACE-1-456085
|
A generic alert-level message
|
Informational
|
ACE-1-456086
|
The ACE initialization has failed
|
Major
|
ACE-1-727001
|
Peer IP address is not reachable
|
Major
|
ACE-1-727002
|
Peer device is not reachable on an FT Interface
|
Major
|
ACE-1-727003
|
Mismatch in context names detected for FT group
|
Major
|
ACE-1-727004
|
Both devices were detected to be Active for the same FT group
|
Major
|
ACE-1-727005
|
Configuration could not be synced to the peer device
|
Major
|
ACE-1-727006
|
Peer is incompatible
|
Major
|
ACE-1-727007
|
Module Initialization failure
|
Major
|
ACE-1-727008
|
Failed to send heartbeats to peer
|
Major
|
ACE-1-728001
|
Initialization failure - general
|
Major
|
ACE-1-728002
|
Initialization failure - sticky
|
Major
|
ACE-1-728003
|
Initialization failure - sticky hash
|
Major
|
ACE-2-100001
|
The CLI end of line (EOL) function
|
Major
|
ACE-2-199006
|
Reload started
|
Major
|
ACE-2-212007
|
SNMPD initialization failed
|
Major
|
ACE-2-313006
|
ICMP Manager Initialization Failed
|
Major
|
ACE-2-443001
|
System experienced fatal failure
|
Major
|
ACE-2-444001
|
License checkout failure
|
Major
|
ACE-2-444004
|
Evaluation license expired
|
Major
|
ACE-2-456014
|
Invalid stream
|
Major
|
ACE-2-456090
|
Critical error parsing ACC module configuration
|
Major
|
ACE-2-727009
|
Communication failure
|
Major
|
ACE-2-727010
|
Data replication failed and not synced to the peer device
|
Major
|
ACE-2-727011
|
Configuration synchronization does not occurred
|
Major
|
ACE-2-727012
|
The state transitions made by an HA state device for a context.
|
Informational
|
ACE-2-727013
|
The peer is now reachable
|
Informational
|
ACE-2-727014
|
The redundancy heartbeats from a peer have become unidirectional
|
Major
|
ACE-2-727015
|
Detected mismatch in heartbeat interval from the peer
|
Informational
|
ACE-2-727016
|
The replication is being carried out to a peer
|
Informational
|
ACE-2-727017
|
ACE FT Track UP syslog
|
Clearing
|
ACE-2-727018
|
ACE FT Track DOWN syslog
|
Major
|
ACE-LB_General-2-728033
|
Drop connection as Application Acceleration Maximum
|
Informational
|
ACE-LB_General-2-728035
|
Disabled Web Application Acceleration
|
Informational
|
ACE-LB_General-2-728036
|
Enabled Web Application Acceleration
|
Informational
|
Cisco Nexus Syslog Support Added
Table 27 identifies the Cisco Nexus syslog support added in Cisco ANA 3.7.1.
Table 27 Cisco Nexus Syslog Support Added in Cisco ANA 3.7.1
Syslog Name
|
Short Description
|
Severity
|
HSRP_ENGINE-6-STATECHANGE
|
HSRP group change syslog
|
Informational
|
HSRP_ENGINE-6-STATECHANGE
|
HSRP group restored syslog
|
Clearing
|
BGP-5-ADJCHANGE
|
BGP neighbor down syslog
|
Major
|
BGP-5-ADJCHANGE
|
BGP neighbor up syslog
|
Clearing
|
OSPF-5-ADJCHANGE
|
OSPF neighbor down syslog
|
Major
|
OSPF-5-ADJCHANGE
|
OSPF neighbor up syslog
|
Clearing
|
Important Notes
This section includes the following topics:
•Installation Notes
•Solaris Services and Components
•Using Cisco CRS-1 VNEs
•Device and Software-Specific Limitations
•Supported Schemes
•JDK DST Timezone Update Tool for Cisco ANA
•Configuring Database Storage (Redo Logs)
•Online Help
Installation Notes
This section includes the following topics:
•Before Installing Cisco ANA 3.7.1
•Changes in the Cisco ANA Installation
•Changes in the Upgrade Process
•Before Upgrading to Cisco ANA 3.7.1
•Using the install.pl Command
•Memory Consumption
•Backward Compatibility
•Cisco ANA 3.7 Upgrade Limitations
For installation procedures, see the Cisco Active Network Abstraction 3.7.1 Installation Guide.
Cisco ANA 3.7.1 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.1 installation script.
Before Installing Cisco ANA 3.7.1
Note the following before installing Cisco ANA 3.7.1:
•One of the Oracle versions shown in Table 28 must be installed with the Oracle JVM and partitioning options:
Table 28 Supported Oracle Versions and Required Patches
Oracle Version
|
Required Solaris Patches
|
Required Linux Patches
|
Oracle 10g Enterprise Edition Release 10.2.0.3.0 or later
|
p6025805_10203_SOLARIS64.zip
|
p6025805_10203_Linux-x86-64.zip
|
Oracle 11g Enterprise Edition Release 11.1.0.7.0
|
p8982191_11107_Solaris-64.zip
|
p8332021_111070_Linux-x86-64.zip
|
p8332021_11107_Solaris-64.zip
|
Oracle 11g Enterprise Edition Release 11.2.0.1.0 or later
|
p9259407_112010_SOLARIS64.zip
|
p9259407_112010_Linux-x86-64.zip
|
p8332021_112010_SOLARIS64.zip
|
p8332021_112010_Linux-x86-64.zip
|
•Clients communicate with the gateway; therefore, IP connectivity is required between the clients and the gateway. The Cisco ANA EventVision client also requires IP connectivity to the database. Cisco ANA EventVision is the only client application that communicates directly with the database.
•For Windows 7 installations only, we recommend that you do not install the Cisco ANA GUI clients in the Program Files folder. Only Windows Administrators can run the GUI clients if they are installed in that folder.
•In Cisco ANA, the clocks on the gateway and units must be synchronized. If Oracle is running on a separate workstation, that remote database workstation's clock must be synchronized with the gateway and unit clocks.
The time set on the clocks of all units in the setup is the same. The maximum difference allowed between the different clocks is 4 minutes.
Note Changing the gateway clock while the system is running will significantly impact Cisco ANA performance.
Changes in the Cisco ANA Installation
The Cisco ANA 3.7.1 installation procedure has changed as follows:
•The default installation location for Cisco ANA 3.7.1 is C:\Cisco Systems\ANA\.
Changes in the Upgrade Process
The Cisco ANA 3.7.1 upgrade process has changed as follows:
•The upgrade process does not create the ana_admin user and scheme.
•The upgrade process overrides the customized "Message of the Day" and restores the default message. After upgrading to Cisco ANA 3.7.1, use Cisco ANA Manage to re-enter your customized "Message of the Day" content.
•The upgrade process overrides the event management settings, such as the number of days before removing events from the database, and restores the default values. After upgrading to Cisco ANA 3.7.1, use Cisco ANA Manage to reset the event management settings to the required values.
For more information, see the Upgrading Cisco ANA chapter in the Cisco Active Network Abstraction 3.7.1 Installation Guide.
Before Upgrading to Cisco ANA 3.7.1
Note For complete information on the changes and requirements for upgrading to Cisco ANA 3.7.1, review the information in the Upgrading Cisco ANA chapter in the Cisco Active Network Abstraction 3.7.1 Installation Guide. That chapter identifies the requirements and effects of the upgrade in detail.
•If you are upgrading from Cisco ANA 3.7, install the Cisco ANA 3.7.0.1 service patch before installing the Cisco ANA 3.7.1 upgrade software.
•If required, back up and store the following information so you can restore it after the upgrade:
–Existing "Message of the Day" content
–Event management settings
If you do not back up and store this information, you can enter the information after the upgrade by using Cisco ANA Manage.
•For an upgrade installation, if you have disabled any plugins prior to upgrading Cisco ANA by modifying site.xml, remove the modification from site.xml before upgrading to Cisco ANA 3.7.1.
•Before migrating to Cisco ANA 3.7.1, close all database sessions (such as TOAD, SQL, and so on).
•Cisco ANA 3.7.1 introduces IMO changes as described in the Cisco Active Network Abstraction 3.7.1 Installation Guide. Review these changes before upgrading to Cisco ANA 3.7.1 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.
•While the Cisco ANA application is up and running, enter the following commands to verify that the databasePath and databaseUser entries are set in the avm66.xml file:
cat $SHEERHOME/Main/registry/ConfigurationFiles/127.0.0.1/avm66.xml | grep databaseUser
cat $SHEERHOME/Main/registry/ConfigurationFiles/127.0.0.1/avm66.xml | grep databasePath
If the first query returns empty output, enter the following commands to set the databaseUser in avm66.xml:
./runRegTool.sh -gs localhost set 127.0.0.1 avm66/services/workflow/engine/databaseUser ""
./runRegTool.sh -gs localhost get 127.0.0.1
workflowavm/services/workflow/engine/databaseUser
./runRegTool.sh -gs localhost set 127.0.0.1 avm66/services/workflow/engine/databaseUser
result-from-previous-command
If the second query returns empty output, enter the following commands to set the databasePath in avm66.xml:
./runRegTool.sh -gs localhost set 127.0.0.1 avm66/services/workflow/engine/databasePath ""
./runRegTool.sh -gs localhost get 127.0.0.1
workflowavm/services/workflow/engine/databasePath
./runRegTool.sh -gs localhost set 127.0.0.1 avm66/services/workflow/engine/databasePath
result-from-previous-command
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 name
The 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.1 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
Refer to the following links for changes in Cisco ANA 3.7.1 that might affect existing integrations:
•For changes in API and information model changes, see the Cisco Developer Network at http://developer.cisco.com/web/ana/home.
•For changes to event types, see the Managing Events section in the Cisco Active Network Abstraction 3.7.1 Installation Guide.
Cisco ANA 3.7 Upgrade Limitations
When upgrading to Cisco ANA 3.7 from Cisco ANA 3.6.x, the following limitations and restrictions apply:
•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.
To work around this issue, close and reopen the Ticket tab in Cisco ANA EventVision. For more information, see CSCtd17665.
•When migrating data to Cisco ANA 3.7 from an earlier version of Cisco ANA, if you specify a database for the event processing scheme that is different than the Cisco ANA database, the migration fails.
To work around this issue:
a. Migrate the data using the same database for Cisco ANA and the event processing scheme.
b. After migrating the data, move the event processing scheme to the desired database.
c. Update the persitency.xml file.
For more information, see CSCtf98838.
Solaris Services and Components
Cisco ANA uses the Solaris services and components. You must not remove them. For more information, see the Cisco Active Network Abstraction 3.7.1 Installation Guide.
Using Cisco CRS-1 VNEs
This section contains the following topics:
•Installing the Cisco IOS XR Manageability Package
•Creating the SNMP Community
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:
Creating 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 SystemOwner
snmp-server community ate9riv RW
SDR Support
Secure Domain Router (SDR) is supported as a separate, independent VNE, with its own IP address and login sequence. When adding an SDR to Cisco ANA, it is treated like any other network element; that is, it is added as a new VNE using Cisco ANA Manage. The SDR IP address is attached to the active RP of the SDR (or to its virtual IP, if it exists).
The following sections describe how to set up Cisco XR 12000 series devices and Cisco CRS-1 devices for use with SDR.
For more information about SDR support and either of these devices, see the Cisco Active Network Abstraction 3.7.1 Reference Guide.
For Cisco XR 12000 Series Devices
As a prerequisite for a Cisco XR 12000 Series VNE:
Step 1 Install the Cisco IOS XR Manageability Package on top of the Cisco IOS-XR version.
Step 2 Add the command xml agent tty to the device configuration.
Step 3 Define the IP address, SNMP read community and Telnet login sequence. When adding the Telnet login sequence, add the user as an admin user (username@admin).
For Cisco CRS-1 Devices
As a prerequisite for the CRS-1 VNE:
Step 1 Install the Cisco IOS XR Manageability Package on top of the Cisco IOS XR version (Cisco IOS XR 3.4 and 3.4.1).
Step 2 Add the command xml agent tty to the device configuration.
Step 3 When creating the SNMP community string, specify the SystemOwner (for SDRs, specify the SDROwner; LROwner on Cisco IOS XR 3.5.x and lower).
Step 4 Define the IP address, SNMP read community, and Telnet login sequence. When adding the Telnet login sequence, add the user as an admin user (username@admin, e.g. cisco@admin).
Device and Software-Specific Limitations
Table 29 describes caveats related to specific devices or versions of software.
Table 29 Device- and Software-Specific Limitations
Device Family
|
Element
|
Affected Software Version
|
Description
|
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:
•3.9.0
•3.8.2
|
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:
•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.
|
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:
•MAC table entries in Cisco ANA NetworkVision logical inventory under Bridge domains.
•Correlation and impact flows in end-to-end scenarios with Viking devices
•MAC-based service path traces in end-to-end scenarios with Viking devices
•Dynamic discovery of MAC-based topologies involving Viking devices
The affected devices are:
•Cisco 12000 IOS XR series devices
•Cisco CRS-1 devices
•Cisco Viking devices
For more information, see CSCtd57684.
|
Supported Schemes
Cisco ANA supports two schemes:
•Product—The default scheme used for all device types supported in this release, except for Cisco CRS-1 and Cisco 3750ME devices.
•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.7.1 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 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
Step 2 Extract the tzupdater.jar file from the downloaded zip file and copy it to /tmp on each gateway and unit.
Step 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. Run the following command:
java -jar tzupdater.jar -u -v
Step 4 Restart the Cisco ANA system.
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.1 Installation Guide.
Online Help
The online help has been updated for Cisco ANA 3.7.1 and has been tested using the following browsers:
•Netscape 9.0
•Microsoft Internet Explorer 8.0
•Firefox 3.5.7
•Mozilla 1.7.13
Limitations and Restrictions
This section includes the following limitations and restrictions:
•Cisco ANA Configuration and Image Management
•Cisco ANA NetworkVision
•Cisco ANA Fault Management
•Cisco ANA Workflow Editor Sessions
•ATM Topology Discovery
•BGP Neighbors
•EVC Discovery
•HSRP
•OSPF
•VLAN Tagged Interface Limitation
For deployment information and recommendations, such as supported configurations and system sizing, contact your Cisco account representative.
Cisco ANA Configuration and Image Management
The following items pertain to Cisco ANA Configuration and Image Management:
•Cisco ANA Configuration and Image Management runs a maximum of four concurrent jobs with four tasks each. As a result, backing up the configurations of 6000 devices in Cisco ANA can take up to 24 hours to complete. For more information, see CSCth85718.
•If you attempt to log into Cisco ANA Configuration and Image Management by using a web browser immediately after the Cisco ANA gateway is up, you will receive an HTTP Error 404.
To avoid this error, we recommend that you wait approximately 15 minutes after the Cisco ANA gateway is up before trying to log into Cisco ANA Configuration and Image Management via a browser. For more information, see CSCth85747.
Cisco ANA NetworkVision
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.1 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.
Cisco ANA Workflow Editor Sessions
You can open only a single Cisco ANA workflow session at a time.
ATM Topology Discovery
ATM topology discovery is performed in two phases:
1. 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.
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.
EVC Discovery
In Cisco ANA 3.7.1, if you initiate full EVC discovery by issuing the runFullDiscovery command on AVM 11, not all EVCs are found even though the command appears to complete successfully. To work around this situation, issue the runFullDiscovery command again. For more information, see CSCti03000.
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:
•In the ingress direction, the VLAN tags in the packet are matched with the tags defined on the subinterface. If a match exists, the tags are extracted from the packet, and the packet is sent for upper-layer handling. The functionality implemented in the device is the same as that implemented by Cisco ANA VNEs.
•In the egress direction, because there is a range of VLAN tags on the subinterface, the device does not know which tag from the range to apply to the packet. Some Cisco IOS devices, such as the Cisco ASR 1000 series and the Cisco 7200 series, apply the first tag in the range. However, this behavior is not consistent for all Cisco IOS or Cisco IOS XR devices.
As a result of the inconsistent behavior in the egress direction, Cisco ANA VNEs do not implement VLAN tagged interface functionality for this direction. If a flow in the egress direction reaches a subinterface with a range of VLAN tags defined, the flow stops.
Open Caveats in Cisco ANA 3.x
The following sections identify and describe caveats that are open against Cisco ANA:
•Significant Caveats Before Using Cisco ANA 3.7.1 identifies significant caveats that require your attention before you start using Cisco ANA 3.7.1.
•Outstanding Cisco ANA 3.7.1 Caveats that Were Resolved for Earlier Releases of Cisco ANA identifies caveats that were identified after June 10, 2010 and fixed on releases of Cisco ANA prior to version 3.7.1.
•Open Caveats in Cisco ANA 3.x identifies other open caveats in Cisco ANA 3.x.
Significant Caveats Before Using Cisco ANA 3.7.1
We recommend that you read the caveats in Table 30 before using Cisco ANA 3.7.1 so that you understand the possible impact on your environment.
Table 30 Significant Open Caveats in Cisco ANA 3.7.1
Identifier
|
Title
|
Impact
|
Workaround
|
Release
|
CSCti16118
|
VLAN snapshot is missing information of VLAN mappings
|
In some situations, you might notice that VLAN links connecting different network VLANs are missing, and that the Add Associated VLANs function does not retrieve all VLANs. In turn, some Ethernet services that rely on these VLAN links are split.
This situation can occur on a device that was modeled by Cisco ANA without any VLAN mapping configuration on a given port. When new VLAN mapping definitions are configured on that port at a later time, the new definitions do not affect the VLAN links as described in the above paragraph.
This situation can also occur upon system startup when using underpowered hardware for Cisco ANA. In this case, VNEs are modeled slowly due to the heavy CPU load on the Cisco ANA machine.
|
Stop and start the VNE.
If restarting the VNE is not desirable, Cisco Technical Support can provide a workaround that does not require restarting the VNE.
|
3.7.1
|
CSCti15505
|
VNE stuck in shutting down after Cisco IOS XR is updated with no commit and reload
|
The VNE appears in investigation mode while shutting down and remains there.
In Cisco ANA NetworkVision, you can only choose to start the VNE, and in Cisco ANA Manage, you can only choose to stop the VNE.
This situation has been seen on Cisco ASR 9000 series devices running Cisco IOS XR 3.9.1.
This situation occurs if you do not commit after reloading VNEs and then issue another reload command.
|
Use Cisco ANA Manage to stop and then restart the VNE.
|
3.7.1
|
CSCti08530
|
Unit does not come up when installed in a different path than the gateway
|
When a unit and gateway are installed in different locations (for example, the gateway is at /export/home/ana/ana, and the unit is at /export/home/ana), the unit fails to retrieve the golden source from the gateway.
Instead of connecting to /export/home/ana/ana/Main, the unit tries to connect to /export/home/ana/Main, which does not exist on the gateway.
|
Install the gateway and units in the same directory.
|
3.7.1
|
CSCti03236
|
CE service elements lose connection with VNE that is unreachable for 10 minutes
|
CE service elements lose connection with VNEs that are unreachable for 10 minutes. When this occurs, reconciliation icons appear on Ethernet Flow Points and Switching Entity elements in Cisco ANA NetworkVision maps. As a result, their containing elements (network VLANs, VPLS, and EVCs) might not display updated information.
|
Stop and start the VNE.
If restarting the VNE is highly undesirable, Cisco Technical Support can provide a workaround that does not require restarting the VNE.
|
3.7.1
|
CSCti02030
|
Layer 1 counters are missing in path traces for devices not running Cisco IOS XR software
|
Layer 1 counters are displayed in the Layer 1 tab in the Cisco ANA PathTracer single-path window only for devices running Cisco IOS XR software. The counters are not displayed for other devices.
|
Use Site customization to change the following entries:
•"mib2repository/port all octet counters snmp" registrations "readoninit=true"
•"mib2repository/port all octet counters snmp" registrations "monitored=false"
Issue the following runRegTool commands under the Main directory to make the required changes:
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
"site/mib2repository/port
all octet counters
snmp/readoninit" true
./runRegTool.sh -gs
127.0.0.1 get 0.0.0.0
"site/mib2repository/port
all octet counters
snmp/monitored" "false"
|
3.7.1
|
CSCth89176
|
Cisco 6504 with Cisco CatOS: CPU reaches 95% after modeling by Cisco ANA
|
If a Cisco 6504 device running Cisco CatOS has a relatively high number of bridges, the device CPU can reach 95% after modeling by Cisco ANA.
As long as the CPU usage is high, the VNE maintains a low polling rate. As CPU usage returns to normal (<40%), VNE will return to a normal polling rate.
|
None
|
3.7.1
|
CSCth89167
|
Scope-based BQL alarm registration mechanisms do not work
|
Running the GetAllTickets command with registration initially returns a result based on the user-attached scopes. However, the command does not filter out notifications of new tickets issued by devices that are out of the user's scope.
|
None
|
3.7.1
|
CSCth84697
|
Event Cache: Flagging event can get incorrect "connectTo" data
|
If two identical network incidents with different root causes occur within 20 minutes, the second incident might be associated with the first incident even if the first incident was fixed.
|
None
|
3.7.1
|
CSCth78358
|
Link Down sometimes not correlated to Card Down ticket
|
The Link Down service alarm is not correlated to a Card Down ticket when the following command is issued:
no power enable module
module-number
In response, the device sends the card status of 15:poweredDown, which is not handled by Cisco ANA. As a result, the card status is set as Unknown or OK, and the Link Down Due to Card Out service alarm is generated as separate ticket.
This caveat applies to all modular devices.
|
None
|
3.7.1
|
CSCth77560
|
Path Tracer counters are not updated
|
When viewing a path trace in the Cisco ANA PathTracer single-path window, the counters displayed in the Layer 1 tab are not updated.
|
None
|
3.7
|
CSCth66425
|
Few EVC left in the database after VNE is removed
|
When trying to add an EVC to a map, empty EVCs might appear in the list of available EVCs if all VNEs that were associated to the EVC were removed.
|
Contact Cisco Technical Support.
|
3.7.1
|
CSCth57475
|
SFP/XFP out on linked port correlation issues
|
Occasionally, after inserting an SFP/XFP into a port, a Link Up ticket is not generated and the Link Down ticket generated on the SFP/XFP removal is not cleared.
When an SFP or XFP is removed from a port that was up and the link was discovered in Cisco ANA, the following occurs:
1. The port state is changed to down.
2. Cisco ANA creates a ticket for the SFP / XFP removal (on Cisco 7600 devices): Transceiver Removed syslog.
3. Cisco ANA generates a Link Down ticket.
4. After a while the link is removed.
After the link is removed, if the SFP / XFP is reinserted, the port status, which is changing to Up, does not generate the Link Up event and the Link Down ticket is not cleared.
|
Acknowledge and clear the ticket from the Cisco ANA GUI.
The link is rediscovered after a short while.
|
3.7
|
CSCth57304
|
Port Up does not clear ticket after Port Down Due to Admin scenario
|
If all events have the same source and name, only the last event is cleared.
This situation occurs specifically in point-to-multipoint configurations, like LDP neighbors or BGP down, where each event replaces the previous event in the VNE EventCache.
When the clearing event arrives, it clears only the last event. All other clearing events are successors of the first clearing event.
|
Use the Clear command from the Cisco ANA GUI or BQL.
|
3.7
|
CSCth55619
|
Pseudowire tunnel down expedite
|
For the same root cause alarm, if multiple Layer 2 Tunnel Down alarms are generated for the same root cause alarm, the Tunnel Down alarms might not correlate to the root cause alarm.
This situation can occur if multiple pseudowires are configured on the same main interface via an EFP or subinterface.
|
None
|
3.7.1
|
CSCth55080
|
Two EVCs are connected with VLAN service link and do not merge
|
In some cases, two Ethernet services are displayed in a map with a link between them instead of being unified in a single Ethernet service.
This situation can occur after initial discovery or in other scenarios.
|
Contact Cisco Technical Support.
|
3.7.1
|
CSCth42970
|
show bfd session command fails to get the flow's result
|
If a Cisco IOS XR device runs Cisco IOS XR version 3.6.3 or lower, the BFD Sessions table is not displayed in Cisco ANA NetworkVision (Logical Inventory > Bidirectional Forwarding Detection).
|
None
|
3.7.1
|
CSCth13578
|
Gateway fails to start a unit due to Net::Ping problems
|
Cisco ANA gateway and units fail to communicate even though there are no errors. The unit might be displayed as Unreachable in Cisco ANA Manage.
This situation usually occurs on setups with firewalls.
|
Edit $ANAHOME/local/lib/perl/ana/SHEER/remote.pm as follows:
1. Comment out the following two lines:
my $cam = Net::Ping->new();
print "\nERROR: $ip is not
reachable, ABORTING.\n\n"
and exit 1 unless
$cam->ping($ip);
2. Modify the following line:
system("ssh_client -F
$SHEERHOME/local/ana_secure
d/ssh_config -l $ENV{USER}
$ip \'$command\'");
to add the timeout parameter, as follows:
system("ssh_client -o
ConnectTimeout=30 -F
$SHEERHOME/local/ana_secure
d/ssh_config -l $ENV{USER}
$ip \'$command\'");
|
3.7
|
CSCtg60434
|
Link disappears from map after connector is unplugged from port
|
If you add two VNEs with a link between them to a map in Cisco ANA NetworkVision, disconnect and reconnect the cable between the devices two times, and then leave the cable disconnected, the following occur:
•Cisco ANA produces a ticket with critical severity with the alarm Link Down due to Oper Status Down.
•The link between the devices changes to red.
•After approximately ten minutes, the link disappears from the map.
|
None
|
3.7.1
|
CSCtg47817
|
Physical link disappears from the map
|
If a physical link disappears from a Cisco ANA NetworkVision map due to a link down, trying to open the link from within the ticket results in an error being displayed.
This situation occurs as follows:
1. Shutting down an interface results in the physical links turning to down between two VNEs.
2. Cisco ANA produces tickets regarding the link down. If you try to open the link from one of these tickets, an error message is displayed.
3. One of the VNEs in Step 1 that lost connection returns after a few minutes.
4. After the link status returns to up, it is displayed again in Cisco ANA NetworkVision.
|
Remove topology persistency and restart both VNEs.
|
3.7.1
|
Outstanding Cisco ANA 3.7.1 Caveats that Were Resolved for Earlier Releases of Cisco ANA
When a customer identifies a defect in Cisco ANA, the availability of the software that fixes that defect depends on when the defect was identified during the development process.
At the beginning of a development cycle, defects that are identified by customers against released versions of the product are scheduled for resolution in the current release. In addition, all fixes that were delivered as point patches or service patches to customers are included in the current release.
During the middle of the development cycle, customer-found defects are handled in one of the following ways, depending on the amount of risk associated with fixing the defect:
•Low-risk fixes are included in the current release.
•High-risk fixes are included in a service patch for the current release and are incorporated into the next release.
At the end the development cycle, customer-found defects identified against released versions of the product are either included in a point patch or service patch, or are scheduled for inclusion in the next release, depending on their severity.
The caveats identified in Table 31 were identified late in the Cisco ANA 3.7.1 development cycle and have been fixed for releases of Cisco ANA earlier than 3.7.1. The fixes for these caveats have been provided to customers as needed and are scheduled for inclusion in the next release.
Table 31 Outstanding Caveats in Cisco ANA 3.7.1 that Were Resolved in Earlier Releases of Cisco ANA
Identifier
|
Title
|
Impact
|
Workaround
|
Release
|
CSCth95599
|
Devices connected to cloud were corrupted in registry
|
Devices connected to a cloud via static links cannot be added in Cisco ANA NetworkVision if their entries are corrupted in the registry.
|
None.
|
3.6.7
|
CSCth89632
|
Only one EFP is displayed if two EFPs share same key
|
If two EFPs share the same key, they might not be created or displayed in the Cisco ANA NetworkVision.
For example, if the following interfaces have a key of GigabitEthernet1/0/112, only one EFP is created:
•GigabitEthernet1/0/1 Efp Id: 12
•GigabitEthernet1/0/11 Efp Id: 2
|
Create an EFP index with a different number, so that each EFP has its own key.
|
3.7
|
CSCth86518
|
Cisco ANA shows different behavior for XENPAK ports
|
Cisco ANA shows different behavior for XENPAK ports.
|
None.
|
3.7
|
CSCth70506
|
BQL interface error constructing the XML
|
If a BQL query is sent to a BQL interface, the BQL interface occasionally fails to respond and the following error is displayed in AVM11:
ERROR [07 05 2010 14:15:00.817
WEST] -
IMObject2XMLConverter.fillEleme
ntArrayTree -
IMObjectsArrayEditor.getAsXmlEl
ement() - error constructing
the xml Element
Some BQL queries work fine. An example of a command that fails is:
<command name="DeviceList">
</command>
|
Restart the Cisco ANA gateway.
|
3.7
|
CSCth67919
|
Generic syslogs and traps not forwarded
|
Occasionally the generic trap and syslog are not forwarded to Netcool by ENS.
|
Remove the following line from avm11.xml and mvm.xml after the ENS forwarder is configured:
<key
name="cenUserMessage1">
<entry
name="original">LatestState
</entry> </key>
Note This workaround impacts the Netcool Integration solution such that the @Summary is not displayed correctly.
|
3.7
|
CSCth66892
|
MP-BGP: Cross VRF entries are not deleted on Cisco ASR 1000 devices
|
If you delete a VRF from a device, the cross-VRF entry is not removed from the Cross VRFs tab under MP-BGP in logical inventory.
|
Delete the VNE persistency file and restart the VNE.
|
3.7
|
CSCth63017
|
Wrong module location for syslog from Cisco ASR 9000 device running Cisco IOS XR 3.9.1
|
For Cisco ASR 9000 devices running Cisco IOS XR 3.9.1, the Card Oper Status alarm correlates to the wrong module.
The Syslog tab in Cisco ANA EventVision displays the Card Oper Status Changed alarm with the wrong module location. As a result, the syslog is not expedited, and the Card Down service alarm is not created.
|
None
|
3.7
|
CSCth57852
|
ES-20 Card In does not clear previous Card Out - cefc trap
|
Card Out tickets with cefc traps correlated to them can remain open if the device does not send a clearing trap.
|
Set the autoClear property for cefc traps to true.
|
3.7
|
CSCth49493
|
Cisco ANA sends email alerts that can bring down servers
|
In a situation in which the OPEN_CURSORS parameter was set to 300, the following occurred:
•Cisco ANA sent 30,000 email messages (due to a configured Drool rule) in 30 minutes and shut down the email server.
•Events were not associated to tickets.
|
1. Increase the OPEN_CURSORS parameter to 2000 by entering the following command:
sqlplus> alter system set
OPEN_CURSORS=2000
scope=BOTH;
2. If changing the parameter does not resolve the issue, restart avm11.
|
3.7
|
CSCth47894
|
Card Out creates multiple tickets and no correlation
|
Card Out on a Cisco 7600 device results in several tickets generated without proper correlation. This situation occurs on Cisco 7600 devices running SRD04 and with WS-X6704-10GE or similar cards.
Device MIBs are updated only after the device sends the Link Down traps and syslogs. When Cisco ANA expedites the relevant registrations, it sees the card is still present and therefore does not correlate the Port Down alarm with the Card Out alarm.
|
Enter the following runRegTool commands:
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/cisco-trap-repository/
parsing-rules/cefc-module-o
per-status-changed-v2/rule-
13/registration-delay 5000
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/cisco-trap-repository/
parsing-rules/cefc-power-st
atus-changed-v2/rule-11/reg
istration-delay 5000
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/cisco-syslog-repositor
y/parsing-rules/LINEPROTO-5
-UPDOWN/rule-8/registration
-delay 5000
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/cisco-syslog-repositor
y/parsing-rules/LINEPROTO-5
-UPDOWN/rule-11/registratio
n-delay 5000
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/cisco-syslog-repositor
y/parsing-rules/LINK-3-UPDO
WN/rule-8/registration-dela
y 5000
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/mib2-trap-repository/p
arsing-rules/link-down-v1/r
ule-8/registration-delay
5000
./runRegTool.sh -gs
127.0.0.1 set 0.0.0.0
site/mib2-trap-repository/p
arsing-rules/link-down-v2/r
ule-10/registration-delay
5000
|
3.7
|
CSCth45324
|
Exception in MP-BGP parser
|
CiscoRouterMPBGPTableParser generates an exception in the log if no cross VRF is configured.
|
None
|
3.6.6
|
CSCth36349
|
BGP events flood Cisco ANA event tables
|
BGP events flood the Cisco ANA event database.
|
Stop and restart the Cisco ANA gateway.
|
3.6.7
|
CSCth19641
|
Add correlation delay for Port Down, Card Out, and Link Down
|
It can take two minutes for events to appear as tickets.
|
None
|
3.7
|
CSCth09040
|
Event Correlation application should enable customized correlation delays
|
Cisco ANA does not provide an option to customize specific correlation delays for event types.
|
None
|
3.7
|
CSCtg96014
|
AVM 11 stuck
|
The Cisco ANA GUI stops responding to requests and the AVM11.log continues to receive new messages.
|
Restart Cisco ANA.
|
3.6.6
|
CSCtg73635
|
Cisco ASR 9000 devices: LSE entries are missing for Viking routers
|
Cisco ASR 9000s devices with LSE entries with the following configuration are not modeled in Cisco ANA:
•No outgoing interface for the LSE entry.
•No next hop for the LSE entry.
|
None
|
3.7.1
|
CSCtg72958
|
Cisco ANA pseudowire tunnels monitoring
|
Pseudowire tunnels (Martini) are not discovered or displayed in Cisco ANA NetworkVision logical inventory even though pseudowire is enabled on nearly all routers.
|
None
|
3.6.6
|
CSCtg68636
|
SPA submodules do not correlate to SIP card out or card down
|
The Card Down/Out alarms for SPA submodules do not correlate to SIP Card Down/Out root cause alarms when a SIP card is removed, shut down, or reloaded.
In general, the Card Down/Out event is a root cause for corresponding subcard Down/Out events.
|
None
|
3.7
|
CSCtg35855
|
Cefc FRU Removed tickets flood Cisco ANA NetworkVision
|
Cisco ANA NetworkVision is flooded with a continuous flow of cefc FRU Removed alarms.
|
None
|
3.7
|
CSCtf64976
|
Cisco ANA chooses BFD Neighbor Loss service alarm as root cause
|
Cisco ANA occasionally incorrectly chooses BFD Neighbor Loss alarm as the root cause instead of the appropriate root cause alarm.
|
None
|
3.6.6
|
Open Caveats in Cisco ANA 3.x
Table 32 lists additional caveats, in descending order, that are open against Cisco ANA 3.x.
Table 32 Open Caveats in Cisco ANA 3.x
Identifier
|
Title
|
Impact
|
Workaround
|
Release
|
CSCtq94559
|
Unit machines become unreachable following initial setup/installation
|
Unit machines enter an Unreachable state following the initial installation.
This situation occurs when the following error is present in 99.out on the unit machine:
Unrecognized VM option
`-ReduceInitialCardMarks'
|
1. In ~/Main/jvm_params.xml, change the following line:
<machine
name="Default">-verbose:gc
-XX:-ReduceInitialCardMarks
</machine>
to:
<machine
name="Default">-verbose:gc<
/machine>
Note This line occurs twice; change it in both places.
2. Enter the following command:
If there are multiple units, changing the file on the gateway makes the change on all units.
|
3.7.1
|
|
CSCto84146
|
Cisco ANA 3.7.1 mvm.pl script continues even with failures
|
The mvm.pl script continues even though it reports failures.
This situation can occur when you restart Cisco ANA on a unit. Even though Cisco ANA fails to retrieve files from the gateway for the unit, Cisco ANA starts on the unit and the file retrieval failures are noted in the log.
This situation might be caused by either of the following:
•Cisco ANA cannot retrieve classes.jar from the gateway to the unit /tmp directory.
•/tmp on the unit is not accessible to the ANA user.
|
1. Check the /tmp access to confirm that it is readable. If it is not, change access to readable and restart Cisco ANA on the unit.
2. Check SSH access from the gateway to the unit and from the unit to the gateway. If necessary, correct any issues and restart Cisco ANA on the unit.
If Steps 1 and 2 do not resolve the issue, continue with the following steps:
3. Enter the following command on the gateway:
4. Copy all the JAR files in the Step 1 output to the corresponding directories on the unit.
5. If a third_party.jar file is among the copied files, enter the following command:
cd ~; jar xf
Main/third_party.jar
6. Restart Cisco ANA on the unit.
|
3.7.1
|
|
CSCtj73268
|
Configurator User - Restrictions
|
A user with the Configurator role cannot connect to Cisco ANA Manage unless all of the following are true:
•The user has the scope of "All Managed Elements."
•The security level of the user is "Configurator."
•The following script is executed:
$ANAHOME/Main/scripts/EnableMan
ageForConfigurator.csh
If any of the above items are not true, the user attempting to log into Cisco ANA Manage receives a Permission Denied message for all connection attempts.
|
None
|
3.7.1
|
CSCtj40515
|
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:
•Reloading the router.
•Replacing a card with a different card of almost the same type (such as with a different number of ports).
•Replacing the card with a different card type.
•Removing the card and placing it in a different slot in the same router.
|
1. Stop the VNE.
2. Delete the inventory and topology persistency files for the VNE.
3. Restart the VNE.
|
3.7
|
CSCtj32671
|
Port 162 appears to be occupied when IP address contains "162"
|
When installing Cisco ANA using the install.pl script, the installation fails due to occupied port 162, even though the netstat command confirms that the port is not occupied.
|
Run the install.pl script with the -override_ports option.
|
3.7.1
|
|
CSCti95693
|
System cannot handle large number of tickets with thousands of events attached
|
Cisco ANA does not perform well if the following conditions exist:
•A large number of tickets exists with the event count of some tickets reaching 135K.
•The tickets are up to four months old and not being closed (flagging).
As a result of these conditions:
•The nonarchived partition size is extremely large.
•Other features (such as Ticket Agent and Integrity Test) do not run normally, with delays in their execution.
|
Contact Cisco Technical Support for the availability of a patch.
|
3.7
|
CSCti50840
|
Installing Cisco ANA Configuration and Image Management on existing installation fails
|
The Cisco ANA Configuration and Image Management application does not initialize properly if the installation is corrupted by attempting to install it more than once.
The commands to start the application show error messages in the startup log files indicating that the startup of the application was not successful, and the application is not usable.
The specific message is:
ERROR: DDL execution of the
script
/export/home/ana37/XMP_Platform
/scripts/xmp_ quartz_ddl.sql
failed, Please check the log
file:
/export/home/ana37/XMP_Platfom/
startup.log, exiting
The installation can become corrupted if you accept the option to install Cisco ANA Configuration and Image Management more than once in repeated executions of the ana-conf script. It is also possible to run the setup_xmp_nccm.cmd script more than once, to run it after the application has been installed by ana-conf.
|
Avoid the problem by installing Cisco ANA Configuration and Image Management only once. If you are unsure whether the application has been installed, do either of the following:
•Enter the anactl status command. If the result shows that the XMP Runtime DM is in [UP] state, the application has been installed.
•Check for the presence of the following directories beneath the ANA home directory (usually /export/home/ana37):
–XMP_Platform
–NCCMComponents
If these directories are present and contain files, Cisco ANA Configuration and Image Management has been installed.
If the application has become corrupted, you must manually uninstall it before installing it again. Use the following procedure to uninstall Cisco ANA Configuration and Image Management:
1. Change to the Cisco ANA home directory.
2. Issue the following commands:
./NCCMComponents/scripts/nc
cmShutdown.csh
chmod -R 777 XMP_Platform
chmod -R 777 NCCMComponents
|
3.7.1
|
|
CSCti25818
|
BGP State Change trap is not processed if source peer is from the VPN IPv6 table
|
Cisco ANA does not handle BGP State Change traps for VPN IPv6 peers if the neighbor IP address is not in the BGP peer table.
This situation occurs if the BGP neighbor belongs to the IPv6, VPNv6, or VPNv4 address family.
|
None
|
3.6.6
|
CSCti15503
|
EVC discovery is stopped after a timeout
|
Cisco ANA might issue an alarm that the EVC service has stopped.
This situation can occur after initial discovery or in other scenarios.
|
Contact Cisco Technical Support.
|
3.7.1
|
CSCti15427
|
Event register filtering by source for syslogs does not work
|
Register event notification might not show syslogs filtered by the OIDs that you are familiar with.
For example, the following does not support notifications for filtered syslogs, traps, or service events by OID because it is not the internal representation that Cisco ANA uses:
<?xml version="1.0"
encoding="UTF-8"?>
<command
name="RegisterEventNotification
s">
<param name="imobjectArr">
<Source
type="Oid">{[ManagedElement(Key
=169.254.207.60_3)]}
</newalarm.INetworkEvent>
<entry
name="depth">20</entry>
<entry
name="register">true</entry>
The Cisco ANA internal representation is not available in Cisco ANA EventVision, but must be used to successfully filter by OID. For example, the suffix for a syslog OID is "[Syslog]".
|
None
|
3.7.1
|
CSCti13516
|
Not all Layer 3 VPNs are listed for Add VPN option or displayed in maps
|
More VRFs are displayed in Cisco ANA logical inventory than in the Add VPN dialog box and Cisco ANA NetworkVision maps.
|
None
|
3.6.6
|
CSCti12285
|
Port Down alarm is not correlated to root Card Out ticket
|
A Port Down alarm does not correlate to a Card Out ticket if the Port Down alarm is received before the Card Out alarm. Instead, the Port Down alarm creates its own ticket.
|
None
|
3.7.0
|
CSCti10465
|
Creating a unit with a secondary IP address of the gateway causes the gateway to crash
|
If you use Cisco ANA Manage to create a new unit with the IP address of the second NIC of the gateway, the Cisco ANA gateway crashes.
|
1. Delete the new unit.
2. Restart Cisco ANA.
|
3.7.1
|
CSCti10300
|
AVM remains unreachable and cannot be deleted if unit real status is down
|
If you create a new AVM on a Cisco ANA unit by using Cisco ANA Manage, the AVM stays in unreachable mode if the following conditions exist:
•The real unit status is down.
•Cisco ANA Manage shows the unit status as up.
|
Enter the following command on the unit:
anactl restart
|
3.7.1
|
CSCti10256
|
HA/DR R3.2: Static link disappears in Cisco ANA NetworkVision after a DR switch
|
In a Cisco ANA integration with a high availability (HA)/DR R3.2 solution, if you add a static link and then perform a site-to-site failover from local to remote, the static link might not be displayed in Cisco ANA NetworkVision, but can be viewed in Cisco ANA Manage.
Restarting Cisco ANA with offline and online Cisco ANA resources in Veritas can refresh the link in Cisco ANA NetworkVision.
|
None
|
3.7.1
|
CSCti07551
|
IP RAN: Transport drops in AVM 11 after extended use
|
After an extended period of time, Cisco ANA EventVision might drop messages and display the following error: "An outgoing MESSAGE frame to switch... was dropped."
This situation occurs whether you install Cisco ANA 3.7.1 as a new installation, or upgrade to Cisco ANA 3.7.1 from an earlier release.
|
Complete the following steps to update the registry settings:
1. After the system is up and running, log into Cisco ANA as the ana-user and enter the following commands:
runRegTool.sh -gs 127.0.0.1
add 127.0.0.1
mmvm/services/transport/que
ues/output
runRegTool.sh -gs 127.0.0.1
set 127.0.0.1
mmvm/services/transport/que
ues/output/maxSize 15000
2. Enter the following command to restart Cisco ANA:
|
3.7.1
|
CSCti07532
|
Incorrect Card Out tickets after a new list of cards
|
Card Out service alarms and tickets might be generated even though the the cards were not removed from the chassis.
After a short time, the same cards are rediscovered in Cisco ANA physical inventory.
|
None
|
3.7
|
CSCti07179
|
OSPF syslog not parsed correctly
|
During an OSPF state transition, the syslogs are incorrectly parsed by Cisco ANA.
|
None
|
3.6.7
|
CSCti06770
|
In scale setup, pseudowire discovery slow when gateway alone is restarted
|
If the Cisco ANA gateway alone is restarted and the number of pseudowire endpoints is very large (more than 40,000), pseudowire discovery can take a long time.
This situation does not occur when the gateway and units are both restarted.
|
None
|
3.7.1
|
CSCti05580
|
BFD with registered protocols of OSPF and BGP link topology not discovered
|
If BFD is configured for multiple protocols between two devices, only one BFD link is displayed in the topology even though there are two BFD links between the devices.
This situation occurs when BFD is configured for multiple protocols, such as BGP and OSPF, between two devices.
|
None
|
3.7.1
|
CSCti05315
|
IP RAN scale - Integrity test of "Regular Workflows" deletion fails
|
Workflows are not purged from the system after one week or any other time frame defined by the user or the Cisco ANA NSA application.
Because the Workflow integrity test that purges old workflows is stuck, database issues can also occur, such as events being dropped from the system.
This situation occurs when all of the following conditions are met:
•Cisco ANA and Cisco ANA NSA are both installed.
•Workflows are executed at a high rate.
•The workflows are executed for a minimum of one week.
|
Do either of the following:
•Manually remove old workflows from the system, either by using Cisco ANA Manage or by running a DeleteWorkflow BQL command.
•Disable the Workflow integrity test that purges old workflows by entering the following command:
./runRegTool.sh -gs
127.0.0.1 set 127.0.0.1
mmvm/agents/integrity/w
orkflowEngine/enabled f
|
3.7.1
|
CSCti05030
|
Missing BFD Link Down service alarm
|
Occasionally, when BFD connectivity is terminated by shutting down the BFD link interface, the BFD Connectivity Down service alarm is not generated. Only the BFD Neighbor Down service alarm is generated.
|
None
|
3.7.1
|
CSCti04946
|
Missing VTP snapshot domain properties in Cisco ANA NetworkVision inventory
|
Not all VTP snapshot properties in Cisco ANA NetworkVision inventory are discovered or, alternatively, all VTP properties are discovered but, if you click the VTP, VNEs are missing from the list of the VTP domain properties.
|
If appropriate, stop and start the VNE.
If it is not appropriate to stop and start the VNE, contact Cisco Technical Support for assistance.
|
3.7.1
|
CSCti04340
|
LSP Broken alarms are not generated
|
LSP Broken service alarms are not generated with an Mpls Black Hole service alarm condition.
If an Mpls Black Hole alarm is generated and the MPLS forwarding table contains `no label' entries, LSP Broken alarms are not generated.
|
Examine the LSP forwarding table for details of missing labels and affected links.
|
3.7.1
|
CSCti03160
|
Port shows wrong information regarding access/trunk
|
If a port configuration is changed from routed to trunk with access to a specific VLAN, the port mode property does not show the correct mode. Although it is supposed to be displayed as trunk, it is occasionally displayed as access.
|
Restart the VNE.
|
3.7.1
|
CSCti03063
|
Port down on device results in Device Lost Reachability ticket delay
|
Device Lost tickets and their correlating events might be delayed if you reload a device and then manually shut down an interface in a link.
|
Wait approximately nine minutes for the ticket and correlated events to be generated.
|
3.7.1
|
CSCti02735
|
After port channel deletion, Ethernet Link Aggregation is also deleted
|
If a port channel is removed from a device configuration, the Ethernet Link Aggregation tab is no longer displayed in Cisco ANA NetworkVision logical inventory.
|
Stop and restart the VNE.
|
3.7.1
|
CSCti02652
|
Duplicate events when the source is a link
|
If you have two VNEs with physical and LAG topographical links between them, and then shut down and restore the link, two events are produced instead of one.
This situation rarely occurs.
|
None
|
3.7.1
|
CSCti02031
|
After no interface polling and readding LAG, Link Down Due to Oper Down alarm
|
If a configured port channel is removed and then returned, the LAG Link Down Due to Oper Down alarm is generated even though the LAG link is up.
|
1. Clear and remove the alarm.
2. Wait for the LAG link to be discovered.
|
3.7.1
|
CSCth99759
|
No alarms are seen when tickets are filtered from the 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
|
CSCth99728
|
Cisco ANA Installation Guide does not specify certain prerequisites for Oracle configuration
|
The ana-conf command fails if the password chosen for the database user begins with an exclamation point (!).
|
Select a password that begins with a letter, a number, or one of the following special characters:
•Underscore (_)
•Dollar sign ($)
•Number sign (#)
|
3.7
|
CSCth97469
|
ATM-UNI: Local Switched ATM interfaces show blank Segment for Cisco CRS-1 and Cisco GSR devices running Cisco IOS XR software
|
Cisco ANA does not populate segment information for Cisco CRS-1 and Cisco GSR devices running Cisco IOS XR software with local switching configured on ATM subinterfaces.
Instead of displaying a hyperlink to the appropriate ATM subinterface in physical inventory, the Segment column in the Local Switching table is empty in Cisco ANA NetworkVision logical inventory (Logical Inventory > Local Switching > Local Switching Entity > Local Switching Table).
|
None
|
3.7.1
|
CSCth96692
|
Cisco ANA 3.7.1 Upgrade: After upgrade, deleting old Cisco ANA user results in exception
|
If you delete a user in Cisco ANA Manage who was migrated to Cisco ANA 3.7.1 from an earlier version and who was not allowed to run workflows, the user is deleted but an exception is generated.
|
None. Because the user was deleted as requested, you can close the exception window.
|
3.7.1
|
CSCth95087
|
Links filter does not remove service links from Cisco ANA NetworkVision
|
Tickets that are due to service links that do not appear in the map are displayed in the ticket list.
If you use a filter to filter out service links in a Cisco ANA NetworkVision map, the service links are removed from the map and links view. However, the service links are not removed from the model. As a result, tickets on those links are displayed in the ticket list.
|
Do either of the following:
•In the ticket table, filter out the tickets related to the service links.
•Return the service links to the map by canceling the filter on the service links.
|
3.7.1
|
CSCth94844
|
Duplicate VRF XID exception
|
A VRF XID exception that might indicate a problem in modeling is displayed in avm11.
|
None
|
3.7
|
CSCth94635
|
Cisco ASR 9000: No interface displayed for MEP configured on Bundle-Ether interfaces
|
If CFM MEP is configured on Bundle-Ether interfaces on Cisco ASR 9000 devices, the Interface field in the Maintenance End Points table is empty in Cisco ANA NetworkVision logical inventory (Logical Inventory > CFM > MD > MA > Maintenance End Points).
|
None
|
3.7.1
|
CSCth92728
|
Missing E1 port information for Cisco MWR 2900 devices prevents static link creation to cloud
|
Missing information for E1 ports on Cisco MWR 2900 devices prevents the creation of static links from the E1 port to a cloud.
|
None
|
3.7.1
|
CSCth92170
|
Changing port channel number on physical LAG port provides incomplete tickets
|
If you change the logical group number of all physical interfaces that a LAG is associated to, a LAG Unreachable alarm is incorrectly issued.
|
1. Clear and remove the alarm.
2. Wait a polling cycle for the LAG link to be discovered.
|
3.7.1
|
CSCth90473
|
BGP alarm is not correlated to main Port Down event
|
Occasionally, the BGP alarm is not correlated to the main Port Down event when the Port Down alarm was cleared and then regenerated at a later time.
Instead, the BGP alarm is correlated to the original, cleared Port Down ticket and not the active Port Down ticket.
|
None
|
3.7
|
CSCth90178
|
Ethernet Link Aggregation tab disappears and LAG Link Down ticket issued
|
If the ports of an Ethernet link aggregation are removed from a device configuration, the Ethernet Link Aggregation tab disappears from logical inventory and a LAG Link Down on Unreachable ticket is generated.
|
1. Stop and restart the VNE.
2. Clear the ticket manually.
|
3.7.1
|
CSCth90168
|
Cisco ANA generates All Members Operationally Up alarm after removal of LAG members
|
Cisco ANA occasionally incorrectly generates an All Members Up alarm after all members of a LAG have been removed.
|
None
|
3.7.1
|
CSCth90097
|
Fake BGP Link Down service alarm
|
A BGP Link Down ticket was issued even though the link was not dropped. This alarm was issued after a BGP session had been established for 12 weeks.
This situation was seen on a Cisco 12404 device running Cisco IOS XR 3.6.2.
|
None
|
3.6.6
|
CSCth89794
|
All IP Interfaces Down service alarm is not generated in link down scenario
|
When a main interface is shut down and two or more IP addresses are assigned to the interface and subinterface, the All IP Interfaces Down service alarm is not generated, even though the individual service alarms for each interface is generated.
|
None
|
3.7.1
|
CSCth89171
|
Get Card Down ticket when loading a device the first time
|
The Card Down ticket and alarm are generated when you start a VNE the first time or restart a VNE.
A Card Out ticket should be generated only when a card that was up goes down.
|
None
|
3.7.1
|
CSCth87920
|
Cisco IOS 12.2(52)EY: Unsupported software version error log for Cisco ME3600X and Cisco ME3800X devices
|
An unsupported software version error log is displayed for Cisco ME3600X and Cisco ME3800X devices running Cisco IOS 12.2(52)EY.
Note The error message appears in the log, but there is no instrumentation loss. All physical, logical, and event-related aspects work as expected.
|
Use the VCB tool to add this software version to the scheme.
For example:
vcb uvne add -sysoid sysoid
-softwareversion
software-version
-clonesoftwareversion
clone-softwareversion
-clonedevicefamily
devicefamily [-devicetype
device-type] -user
username -password password
|
3.7.1
|
CSCth86653
|
OSPF Link Up/Down is not correlated to Port Down ticket
|
If an interface configured with OSPF is down, the associated OSPF traps and syslogs are not correlated under the Port Down ticket.
Instead, the OSPF traps and syslogs are correlated under tickets that have already been cleared.
|
None
|
3.7
|
CSCth83849
|
Problem with BFD link hyperlink and link color on alarm
|
BFD links are not colored despite having a major event on the link. Clicking the BFD link hyperlink results in an error message being displayed.
This issue occurs whenever a BFD link exists between two devices.
|
None
|
3.7.1
|
CSCth83769
|
Failed delete VNE operation does not remove VNE from list
|
Attempting to delete a VNE by using the following steps fails:
1. Add an AVM and VNE to a Cisco ANA unit.
2. Stop all java processes on the unit.
3. After the unit becomes unreachable, try to delete the VNE.
4. Start the unit.
5. After the unit is up, try to move or delete the VNE.
A message is displayed stating that the VNE is in the process of deletion.
|
None
|
3.7.1
|
CSCth82582
|
Detailed Traps report failure
|
The Detailed Traps report fails if you run the report with a filter that results in displaying the details for more than 200,000 traps in the report.
|
Run the report with a finer filter; for example, with fewer devices or for a shorter time period.
|
3.7.1
|
CSCth82050
|
Type column in the ARP table does not match the device
|
For Cisco CRS 4-slot devices running Cisco IOS XR 3.7.1, the Type column in the ARP Entity table in Cisco ANA NetworkVision displays the state of the address (either static or dynamic) instead of the type, such as ARPA.
|
None
|
3.7
|
CSCth80506
|
Tunnel links disappear after moving AVM
|
If you move an AVM to a unit or gateway that has only one endpoint, a pseudowire link might not be discovered.
|
Do either of the following:
•Before moving the AVM, shut down all VNEs and then move the AVM.
•After moving the AVM, restart the AVM for the other endpoint of the link.
|
3.7.1
|
CSCth79786
|
Port down flapping not generated
|
Port Down events are not generated when a port cycles up and down multiple times.
|
None
|
3.7.1
|
CSCth79783
|
Some AffectedSNC records might fail to persist in the database
|
Some AffectedSNC records that are related to a network event might fail to persist in the database if the source's length of the network element of an AffectedSNC is larger than 1000.
|
Change the following columns in NEWAFFECTEDSNC table to VARCHAR2(2000) instead of VARCHAR2(1000) so they are the same as the source column in the NETWORKEVENT table:
•ASIDEOID
•ZSIDEOID
|
3.7.1
|
CSCth79757
|
VNE "Connecting" communication state is misleading
|
If you create a new AVM in Down state and load a new VNE in Up state, the VNE communication state displayed in Cisco ANA NetworkVision is Connecting.
Instead, the VNE communication state should be Down.
|
Start the AVM.
|
3.7.1
|
CSCth79506
|
Max speed shown as -1 for all Gig and 10Gig Cisco GSR devices running Cisco IOS XR 4.0 software
|
The maximum speed for all Gigabit and 10-Gigabit ports is displayed as -1 for all Cisco GSR devices running Cisco IOS XR 4.0 software.
|
None
|
3.7.1 SP1
|
CSCth78121
|
Stopping and starting a VNE or moving an AVM causes a Flickering Topology system event
|
If you do either of the following, a Flickering Topology system event is displayed in Cisco ANA EventVision even though the link is not flickering:
•Stop and start the VNE on one side of the link two or more times.
•Move the AVM two or more times.
The event states that the reason for disconnecting the event is null.
You can ignore this event.
|
None
|
3.7.1
|
CSCth76819
|
Removed devices are treated as managed devices
|
VNEs that have been removed from Cisco ANA are represented as if they still existed:
•VNE in Up state—If you add a VNE to Cisco ANA in an Up state, remove the VNE, and then send a network event from the VNE IP address, the network event is processed as if the VNE still existed.
•VNE in Down state—If you add a VNE to Cisco ANA in Down state and then send a network event from the VNE IP address, the network event is processed as if the VNE were an unmanaged device.
|
•For VNEs in Up state, restart AVM 100.
•For VNEs in Down state, start the VNE and then stop it.
|
3.7.1
|
CSCth75067
|
Cisco ANA EventVision hangs when trying to display SNMP v3 traps
|
If you select the V3 Trap tab in Cisco ANA EventVision, the Cisco ANA EventVision client hangs.
|
None
|
3.7
|
CSCth74585
|
Ambiguous information in physical inventory 0/RP0 and 0/RP1
|
For Cisco IOS XR devices, some Control Ethernet ports under the route processor are modeled in physical inventory in Cisco ANA NetworkVision.
|
None
|
3.6.6
|
CSCth72844
|
TFS: TCA-generated tickets do not show description on traps sent
|
When a TCA ticket is created using thresholds, the ticket is sent northbound via a trap forwarding service, but the notification does not include the ticket description. Instead, it contains the alarm-type number specified in site.xml during Soft Property creation.
For example, when a TCA ticket is created using Soft Properties and thresholds, the trap sent should include the ticket description in cenAlarmStatusDefinition, such as cenAlarmStatusDefinition = 179, layer 2 tunnel down.
Instead, the TCA-generated ticket contains cenAlarmStatusDefinition = 9015,....
|
None
|
3.7
|
CSCth72801
|
Dual-port modeling does not work as expected
|
When a pluggable port is inserted into a device with a module that supports dual ports, Cisco ANA shows both the ports instead of the inserted port.
For example, a Cisco 7600 device can contain a WS-SUP720-3BXL module that supports dual ports. The two ports are Gigabit Ethernet ports that will work as an SFP or RJ-45 port depending on whether or not an SFP is inserted.
When an SFP is inserted into one of these Gigabit Ethernet ports, Cisco ANA should display the SFP port and not the Gigabit Ethernet port. However, Cisco ANA displays both ports.
In addition, instead of modeling the SFP with its properties (PID, Serial Number, Pluggable Type, and Media Type), Cisco ANA displays both ports as normal ports.
|
None
|
3.7.1
|
CSCth72346
|
Same Layer 2 Tunnel Down service alarm is raised twice simultaneously
|
A Layer 2 Tunnel Down alarm might not be cleared if the Layer 2 Tunnel Down alarm is generated twice:
•Once on a pseudowire link.
•Once on a pseudowire endpoint.
This situation occurs if the pseudowire is down before Cisco ANA discovers it and both endpoint devices are managed by Cisco ANA.
|
Clear the ticket manually.
|
3.7.1
|
CSCth70371
|
Redundancy state is displayed incorrectly for all network elements
|
If redundancy is configured on a device, and the device is managed in Cisco ANA, physical inventory displays the wrong redundant state for the card or module on which redundancy is configured.
|
None
|
3.7
|
CSCth69539
|
AVM does not start if port is in use
|
An AVM does not start if the port is already in use.
|
None
|
3.7.1
|
CSCth67545
|
Need to set registration-delay for Card In traps and syslogs
|
Card status update is delayed after a card is inserted.
Cisco ANA has a registration delay value of 30 seconds for all Cisco IOS devices for:
•OIR-6-INSCARD syslogs
•TRANSCEIVER-DFC-6-INSERTED syslogs
•CEFC FRU inserted traps
As a result, the clearing ticket (Card In) service alarm is generated 30 seconds after the card is inserted.
|
Contact Cisco Advanced Services for assistance in modifying the length of the delay.
|
3.7
|
CSCth66348
|
EFP Down alarm is sent when EFP was down originally
|
EFP Down alarms might be sent for EFPs that are originally in an operational down state under the following circumstances:
1. Create a VNE for a device with EFPs configured on some of the ports.
2. Confirm the EFPs are operationally down and administratively up.
3. Remove the module from the device. A Card Out alarm is generated with its correlated events.
4. Reinsert the module. The Card Out alarm is cleared, and EFP Down alarms are generated on the EFPs.
|
None
|
3.7.1
|
CSCth62214
|
Devices with the Most Events (by type) report runs forever in scale setup
|
If you run the Devices with the Most Events (by type) report on a long date range and a setup with a high event rate, the report stays in Running state.
|
Run the report using a shorter date range, such as the last day.
|
3.7.1
|
CSCth61922
|
OSPF Neighbor Down alarm does not correlate to Link Down
|
OSPF Neighbor Down alarms do not correlate to Link Down events.
|
None
|
3.7.1
|
CSCth59731
|
Activation scripts do not appear after importing and restarting AVM
|
Activation scripts and Soft Properties are not displayed after they were imported and the VNE and AVM were restarted.
|
Restart Cisco ANA.
|
3.7.1
|
CSCth58175
|
Cisco ASR 9000 devices: OSPF processes do not show serial interfaces in GUI
|
Logical inventory in Cisco ANA NetworkVision does not display the information for serial interfaces on Cisco ASR 9000 series devices that have serial interfaces as subinterfaces of OSPF processes.
|
None
|
3.7.1
|
CSCth57528
|
SNMP elements hash code is always 0 (zero)
|
SNMP elements hash code is always 0, resulting in relatively slow modeling of VNEs for Cisco 7600, Cisco CRS, and Cisco ASR 9000 series devices.
|
None
|
3.7
|
CSCth57511
|
Module Unsupported alarm generated for AC power module in Cisco 3900 devices
|
The Module Unsupported alarm is displayed in Cisco ANA NetworkVision for Cisco 3900 series devices even though Cisco ANA supports the PWR-3900-AC module.
|
Use the VNE Customization Builder (VCB) to support this module.
|
3.7.1
|
CSCth55132
|
Moving a VNE to an unreachable AVM causes the VNE to become unreachable
|
If you create a new AVM, start the AVM, and, while the AVM is unreachable, move a VNE from a different AVM to the unreachable AVM, the VNE is not reachable after the AVM comes up.
|
None
|
3.7.1
|
CSCth49807
|
Wrong behavior on REP change with NO_NEIGHBOR configuration
|
When the Resilient Ethernet Protocol (REP) configuration is changed on a device (specifically for ports with Operational Link Status of NO_NEIGHBOR), the REP table in Cisco ANA NetworkVision logical inventory is not updated.
|
None
|
3.7.1
|
CSCth49796
|
Cisco ASR 9000 VNE is operational but MAC address tables not displayed in logical inventory
|
Some MAC address tables appear in Cisco ANA NetworkVision logical inventory after the VNE enters an operational state.
This situation occurs on very large configurations on Cisco ASR 9000 devices.
|
Wait until all tables are displayed in the GUI.
|
3.7.1
|
CSCth49073
|
DWDM syslog of L2-G709-4-ALARM does not consider the alarm type
|
The DWDM L2-G709-4-ALARM and L2-G709-4-ALARM- CLEARED syslogs do not consider the type of the G709 alarm.
As a result, when any clearing syslog similar to L2-G709-4-ALARM-CLEARED is received and parsed by Cisco ANA, all L2-G709-4* syslogs are cleared.
For example, if syslog G709 alarm LOS is invoked, and then syslog G709 alarm BEI clear, the G709 alarm BEI clear syslog clears the G709 alarm LOS syslog.
|
None
|
3.7.1
|
CSCth48719
|
Multiple AVMs with the same AVM ID when more than 1000 AVM IDs
|
Cisco ANA allows you to create AVMs with identifiers greater than 1000, but when these AVMs are created and managed, multiple AVMs are seen with the same identifier after a period of time.
|
Do not create AVMs with identifiers greater than 1000.
|
3.7.1
|
CSCth47929
|
No system event when restarting Cisco ANA with no license in limit of 120 days
|
System events related to not having a license after the limit of 120 days are not persisted if you restart Cisco ANA.
Any events that are generated from the gateway during Cisco ANA startup are not persisted if AVM 25 is not yet running.
|
None
|
3.7.1
|
CSCth45530
|
Detailed Event Count (by device) report does not work in scale setup
|
If you run the Detailed Event Count (by device) report for thousands of devices, the report stays in Running state.
|
Run the report for fewer devices, such as hundreds instead of thousands.
|
3.7.1
|
CSCth45321
|
Creating a unit with unit protection disabled does not save to registry
|
If you create a unit with unit protection disabled, restart the Cisco ANA gateway, and then view the unit properties, unit protection is shown as enabled.
|
None
|
3.7.1
|
CSCth45167
|
Command Builder command is not published to all VNEs
|
If you create a command for VNEs using Command Builder or Soft Properties and publish the command to all VNEs by cutting and pasting to the highest hierarchy level or location, the script is not published to all VNEs.
|
Restart the VNE or AVM.
|
3.7.1
|
CSCth44936
|
Mass of uncleared tickets causes correlation failure
|
If there is an extremely high number of uncleared tickets, events are not correlated to their root cause and open tickets.
When the number of open tickets reaches the threshold of ActiveTicketTest, Cisco ANA starts to archive cleared tickets. If there are not enough cleared tickets to archive, it archives uncleared tickets.
When Cisco ANA archives uncleared tickets, and when new tickets are opened and the root alarm is cleared but the correlated events have not yet been received, the following actions occur:
•The new tickets are archived because their aggregated severity is cleared.
•The correlated events do not correlate to the root alarm (because it is already archived) and they result instead in new tickets.
|
Check the number of open tickets on a regular basis. If there are a large number of tickets, archive some of the older tickets.
|
3.7.1
|
CSCth43161
|
Command Builder commands not shown in VNE right-click menu
|
Commands that are created in Command Builder are not visible in the right-click menu for VNEs.
This situation occurs if the Microsoft Windows time of the Cisco ANA client precedes the gateway time and another application is open.
|
1. Close and reopen the Cisco ANA client for the command to appear in the right-click menu.
2. If the command still does not appear, delete the client cache in the client installation directory \ANA\cache\gateway-ip where gateway-ip is the IP address of the Cisco ANA gateway.
|
3.7.1
|
CSCth42118
|
Empty Maintenance column if creating VNE with vne_creation_scirpt.pl
|
If you create a VNE on a Cisco ANA unit using vne_creation_script.pl from Main/scripts, the Maintenance column is empty.
If you then change the VNE to maintenance mode, the value entered in the Maintenance column for that VNE is true.
When a VNE starts, the maintenance state should be false by default.
|
None
|
3.7.1
|
CSCth40078
|
Upgrade to Cisco ANA 3.7.1, roll back, and upgrade again fails by @LongLink
|
The Cisco ANA 3.7.1 upgrade script creates a compressed archive of the ANAHOME directory. During the tar operation, a @LongLink file might be created as tar cannot handle very long filenames.
If you try to roll back an upgrade that contains @LongLink and upgrade again, the following error message is displayed:
tar: ./@LongLink: Cannot open:
Permission denied
This situation occurs when reexecuting an upgrade to Cisco ANA 3.7.1 on a Solaris gateway.
|
Before upgrading Cisco ANA to version 3.7.1, determine if @LongLink appears under $ANAHOME. If it does, remove it.
|
3.7.1
|
CSCth38369
|
Unrequired extra EVCs are discovered as a result of shared real and fake EFPs
|
In situations in which Cisco ANA manages only EoMPLS and not access to the EoMPLS, VLAN discovery generates a VLAN domain for a single EFP that is the Attachment Circuit into the EoMPLS. These VLANs are not associated with the EoMPLS and are part of a separate EVC.
|
None
|
3.7.1
|
CSCth36256
|
Generate two separate tickets regarding link down and up
|
Cisco ANA generates two separate link down events when a port is disconnected and connected a few times.
This situation occurs because, when a port is connected and disconnected, the port can be in any of a number of link event negotiation states. As a result, events might be sent from different sides of the link.
|
None
|
3.7.2
|
CSCth36192
|
Wrong severity on device after port down scenario
|
After performing a port down scenario, returning the port to up status, and clearing and removing the associated ticket, the device displays the wrong severity.
This situation does not recur consistently.
|
None
|
3.7
|
CSCth33536
|
Events are persisted to ana37_ep only in groups of 10 (configurable)
|
Events in the network are persisted in groups of 10. For example, if 14 events are received, only 10 are persisted. In the 20th event, another 10 are persisted.
The persistency bulk size is configurable, and 10 is the default value.
|
None
|
3.7.1
|
CSCth31243
|
EFPs deleted and readded to the same map have reconciliation icons
|
The reconciliation icon is displayed in Cisco ANA NetworkVision maps on EFPs that are deleted and rediscovered.
This situation occurs if you:
1. Create a map and add an EVC to it.
2. Delete the VNEs that are related to the EVC.
3. Wait for the EVC to be deleted.
4. Readd the VNEs, and wait for the EVC to be discovered.
5. Readd the EVC to the map.
The EFPs representing switch ports have reconciliation icons.
|
Close and reopen the map.
|
3.7.1
|
CSCth31082
|
Cannot open huge reports in different formats
|
Extremely large reports cannot be viewed in some formats. For example, if you run a Detailed Syslog report or an Ethernet Service Summary report that contains more than 100,000 items, the report does not display.
|
Do any of the following:
•View the report in CSV format.
•For medium reports, save the report in XLS or XML format and then view it.
•Run the report with a finer filter.
|
3.7.1
|
CSCth30582
|
Reports: BIRT temporary files cause a full disk
|
BIRT temporary files are not deleted, thereby filling the disk.
|
Delete the DataEngine_xxx directories under /var/tmp/.
|
3.7.1
|
CSCth25775
|
SONET bundles are not modeled for Cisco 7200 devices
|
Cisco ANA NetworkVision does not model SONET bundles for Cisco 7200 devices.
|
None
|
3.7.1
|
CSCth22927
|
Table Soft Property: Missing notification upon update
|
When a single value in a Table Soft Property is modified, currently open inventory windows do not update their views.
|
Reopen the Soft Property tab or inventory window to view the new value.
|
3.7.1
|
CSCth22846
|
Proxy for AVM 25 does not work in high availability (HA) scenarios
|
Proxy configuration for AVM 25 does not work in the following HA scenario:
•AVM 25 on Unit A is configured to use proxy AVM 25 on Unit B.
•Unit B is part of a HA protection group, where Unit C is its standby.
•Unit B fails, and Unit C takes over.
In this situation, AVM 25 on Unit A is still configured to use Unit B, which is now down.
|
In a setup in which the Cisco ANA gateway supports HA, use the gateway machine AVM 25 as proxy for units with no database connectivity.
|
3.7
|
CSCth21387
|
Static link exists in system but is not shown in the map
|
A static link exists in the system, and is seen in Cisco ANA Manage, but the link is not seen in Cisco ANA NetworkVision in the map view.
This situation occurs when the static link is created while the dynamic link is connected.
|
Do either of the following:
•Restart one of the VNEs that holds the static link.
•Recreate the static link while there is no dynamic link.
|
3.7.1
|
CSCth20657
|
Unable to override a dynamic LAG link with a static link
|
If a LAG link is dynamically discovered and you want to override it with a different static link, you cannot do it through Cisco ANA NetworkVision.
|
Use BQL to create the static link.
You can use the following example, replacing the A Side OID and Z Side OID with the required OIDs:
<?xml version="1.0"
encoding="UTF-8"?>
<value>{[StaticTopologyM
anagement]}</value>
<param
name="imobjectArr">
<NewIMO
type="management.IStaticTop
ologyManagement">
<ID
type="Oid">{[StaticTopology
Management]}</ID>
<Links
type="IMObjects_Array">
<management.IStatic
TopologyLinkManagement>
<ID
type="Oid">{[StaticTopology
Link(ASideOid={[ManagedElem
ent(Key=10.56.101.96)][Logi
calRoot][Context(ContextNam
e=Default
context)][DataLinkAggregati
onContainer(Type=1)][DataLi
nkAggregation(Index=22)]})(
ZSideOid={[ManagedElement(K
ey=c2-core1)][LogicalRoot][
Context(ContextName=Default
context)][DataLinkAggregati
onContainer(Type=1)][DataLi
nkAggregation(Index=10)]})]
}</ID>
<BiDirectional
type="Boolean">true</BiDire
ctional>
</management.IStati
cTopologyLinkManagement>
<PropertyName
type="String">Links</Proper
tyName>
|
3.7.1
|
CSCth19045
|
Routers with crypto commands are always shown as "out of synch"
|
In Cisco ANA Configuration and Image Management 1.0, a router that includes a crypto certificate within its configuration always appears as "out of synch." This occurs even after executing a job to explicitly perform the synchronization, or by going directly to the device to copy the running configuration to the startup configuration.
This situation is seen on routers with the following element present in the running configuration:
crypto pki certificate chain
A router with this command is referred to as "running a crypto image."
|
Ignore any such routers when they appear on the list of devices that are out of synch as shown on the dashboard or in the Configurations > Synchronize screen.
Adding the crypto pki certificate command to the exclude list does not solve the problem because this is a multiple-line command that is not processed correctly by the exclude command logic. The exclude commands handling logic currently handle single-line commands only.
|
3.7.1
|
CSCth17529
|
Business Element Not Found error when trying to add an EVC to a map
|
When trying to add a EVC or VPLS to a map, a Business Element Not Found error might be displayed, and the element is not added to the map.
This situation is more likely to occur when deleting a large number of VNEs.
|
Wait two to ten minutes for the system to finish updating, and then add the element.
|
3.7.1
|
CSCth11086
|
LAG not updated on changes
|
If you move ports to LAG (of type Ethernet Channel) and no ports are available, the ports move, but the state stays Manual instead of changing to LACP.
If you remove all ports from LAG, the ports are moved and the state changes to Down, but the protocol type stays LACP and does not change to Manual.
|
Restart the VNE.
|
3.7.1
|
CSCth08934
|
Unreachable unit cannot be removed from Cisco ANA Manage
|
If a Cisco ANA unit remains in an unreachable state and the unit contains AVMs, it cannot be deleted from Cisco ANA Manage.
|
Do the following:
1. Connect to the Cisco ANA gateway as ana-user (where ana-user is the UNIX user account for the Cisco ANA application, created when Cisco ANA is installed).
2. Go to the ~/Main directory and enter the following commands:
./runRegTool.sh -gs 127.0.0.1 set 127.0.0.1
avm11/services/plugin/BosManagePlugin/ignoreElementsState/enable true
anactl restart
3. Move all AVMs to another unit.
4. Delete the unit.
5. Enter the following commands:
./runRegTool.sh -gs 127.0.0.1 set 127.0.0.1
avm11/services/plugin/BosManagePlugin/ignoreElementsState/enable false
anactl restart
|
3.7.1
|
CSCth08839
|
Power shelf and Rectifier are not modeled for Cisco CRS -1 8-slot device with Cisco IOS XR 3.90/3.9.1
|
For Cisco CRS-1 8-slot devices running Cisco IOS XR 3.9.0 or 3.9.1, the power shelf in the device and the AC power rectifiers are not modeled in Cisco ANA NetworkVision physical inventory.
|
None
|
3.6.3
|
CSCth07286
|
Cisco ANA 3.7.1 Upgrade: Cisco ANA clients logging into the gateway might become `stuck'
|
If you upgrade or downgrade the same Cisco ANA gateway a few times, or open multiple Cisco ANA clients from the same gateway, the Cisco ANA clients might not open successfully.
This situation is more likely to occur if you upgrade and downgrade the same gateway multiple times or if you open multiple Cisco ANA applications on the same gateway at the same time.
|
Delete the client cache in the client installation directory \ANA\cache\gateway-ip where gateway-ip is the IP address of the Cisco ANA gateway.
|
3.7.1
|
CSCth07046
|
Creating static link before dynamic link on the same port results in two links
|
Incorrect service discovery occurs when duplicate links are associated with the same port.
If the corresponding devices are already open in a map, Cisco ANA NetworkVision displays two links (one static and one dynamic) connected to the same port.
This situation occurs if a static link that overrides a dynamic link is added exactly when the dynamic topology starts to discover links.
|
None
|
3.7.1
|
CSCth06430
|
Cisco GSR device port connector is modeled as Missing Pluggable Port
|
On Cisco GSR devices running Cisco IOS XR software, the ports under modules SPA-5X1GE-V2 and SPA-1X10GE-L-V2 are modeled as Missing Pluggable Ports. As a result, links on the interfaces are not discovered.
|
None
|
3.7.1
|
CSCth03168
|
Cisco CRS-1 8-slot devices with Cisco IOS XR 3.7.1: Fan tray issue on OIR
|
For Cisco CRS 8-slot devices running Cisco IOS XR 3.7.1, fan status is shown as Unknown instead of Out or Down when the fan is switched off.
As a result, fan card tickets are not issued if the fan card status changes.
|
None
|
3.7
|
CSCth03112
|
Cisco CRS 8-slot devices with Cisco IOS XR 3.7.1: Power supply issue on OIR
|
For Cisco CRS 8-slot devices running Cisco IOS XR 3.7.1, power supply module status is shown as Unknown instead of Out or Down when the power supply is switched off.
As a result, power supply tickets are not generated when the power supply status changes.
|
None
|
3.7
|
CSCth01054
|
Cisco ANA models Cisco 3750g fiber optic ports as RJ45 ports
|
Cisco ANA models fiber optic ports as RJ45 ports for Cisco Catalyst 3750G devices running Cisco IOS 12.2(25)SEE2.
|
None
|
3.7.1
|
CSCtg98699
|
Terminating EFPs retain reconciliation icons when they should be removed
|
Some EFPs might appear with a reconciliation icon, indicating that the EFPs were removed. Instead, EFPs that have been removed should not be displayed.
|
Stop and start the VNE to refresh the screen without the EFPs.
|
3.7.1
|
CSCtg98169
|
Install and Activate do not work for Cisco ASR 9000 devices via Cisco ANA Configuration and Image Management
|
For Cisco ASR 9000 series devices, the Install and Activate queries via Cisco ANA Configuration and Image Management successfully activate the same version of the software image, but do not work if the image is upgraded or downgraded.
|
None
|
3.7.1
|
CSCtg97318
|
Link between Cisco ME3400 with REP Edge No Neighbor to Cisco ASR 9000 not discovered
|
If a ring of Cisco ME-3400E access nodes is closed by a pair of Cisco ASR 9000 aggregation nodes, the links between the Cisco ME-3400E devices and the Cisco ASR 9000 devices are not discovered.
Because Cisco ASR 9000 devices do not support REP on EVCs, the edge ports on the Cisco ME-3400 devices are configured as REP Edge No Neighbor ports. These uplinks to the Cisco ASR 9000 devices are not discovered by Cisco ANA or displayed in Cisco ANA NetworkVision maps.
|
None
|
3.7.1
|
CSCtg96418
|
Cisco ANA PathTracer fails with IP address destination
|
Running a path trace to a destination IP address fails to find the required path.
If ARP cache information is missing in the device (due to aging), and thus not modeled by the VNE, the path trace might not have enough information to perform a trace to a destination IP address.
To overcome this lack of information, Cisco ANA PathTracer initiates a flood on the VNE model to find the correct path. In some cases, the flood identifies multiple ways to reach the destination IP address. Cisco ANA PathTracer chooses a path that might or might not be the optimal path from among the options and, as a result, might display a nonoptimal or even incorrect path.
|
Launch the path trace again as sometimes it is a timing issue.
|
3.7.1
|
CSCtg96406
|
Cleared ticket not appearing as blue although correlated with Info alarm
|
Tickets that contain alarm severities of both Cleared and Information have a severity of Cleared instead of Information.
|
None
|
3.7.1
|
CSCtg75431
|
Separate ticket is created for SPA when containing SIP is removed or shut down
|
For Cisco GSR devices running Cisco IOS XR 3.8.2, removing or shutting down the SIP-600 card that contains an SPA results in a ticket for the SPA alarm instead of correlating it to the Card Down/Out ticket.
|
None
|
3.7.1
|
CSCtg70888
|
Instrumentor persistency misses duplicate commands
|
In some cases, a VNE might perform polling during startup even if instrumentor persistency is enabled and the data is stored in the persistency.
When two or more commands poll the same SNMP OID (including the same columns) or the same Telnet CLI, the persistency data is available to the first command that requests it.
|
None
|
3.7.1
|
CSCtg68710
|
MPLS black hole consistently does not correlate to Link Down events
|
In link down scenarios, MPLS Black Hole events are not correlated to Link Down events.
|
None
|
3.7.1
|
CSCtg62772
|
Alarm ticket regarding OSPF flapping does not correlate to Link Flapping
|
The alarm for OSPF flapping does not correlate to the Link Flapping ticket.
This situation occurs under the following conditions:
1. Two VNEs are added to a Cisco ANA NetworkVision map with a link between them and OSPF configured on at least one of them.
2. The cable is unplugged and plugged in a few times (approximately five times) to create a Link Down Flapping ticket.
The OSPF flapping alarm is not correlated to the Link Down Flapping ticket.
|
None
|
3.7.1
|
CSCtg62738
|
Alarm regarding Primary HSRP Not Active does not correlate to Link Down
|
If HSRP is configured between two devices and the link between the devices goes down, the Primary HSRP Not Active alarm should correlate to the Link Down alarm, but it does not.
|
None
|
3.7.1
|
CSCtg60410
|
GUI ignores icons in Scalar Notification on OID property
|
Bridge properties in Cisco ANA NetworkVision maps are not updated when a VLAN is deleted and added with a different name.
When a VLAN that has been added to a map is removed from a device, the reconciliation icon is displayed on the switching entity and all EFPs under it.
If the same VLAN is added using a different name:
•The reconciliation icons are removed.
•The Bridge Properties window (right-click the VLAN, then choose Properties) shows the old bridge properties instead of the new one.
|
Close and reopen the map.
|
3.7.1
|
CSCtg57985
|
All Managed Elements can be removed from user Administrator but cannot be added
|
A user with the Administrator security level can remove All Managed Elements from another user with Administrator security level, but cannot add All Managed Elements back.
|
None
|
3.7.1
|
CSCtg57041
|
Using Filter in Cisco ANA EventVision for large table of Syslog
|
Filtering the contents of the Syslogs tab in Cisco ANA EventVision can result in the query running for a long time and the client appearing to be stuck.
This situation can occur when all of following conditions apply:
•The database is heavily loaded.
•The contents of the Syslogs tab are filtered by the Description field.
•The search string does not match any syslog.
|
None
|
3.7.1
|
CSCtg54230
|
ATM IMA cards do not populate Loopback, Framing, or Scrambling values
|
ATM IMA cards do not populate E1 properties like Framing, Loopback, or Scrambling values.
This situation occurs for channelized cards inserted into Cisco 7200 devices.
|
None
|
3.7.1
|
CSCtg52657
|
Access pseudowire attached from both sides to VFI gathers the VFI
|
A VPLS Instance might contain a VPLS Forward that should not be included.
When an Access pseudowire is attached from both sides to a VSI, both VPLS Forwards are part of the same VPLS Instance.
|
None
|
3.7.1
|
CSCtg52183
|
TicketListAspect notifications are missing on correlated alarms
|
TicketListAspect is part of the IMO model that contains a list of tickets that the requested element is part of. After the first Get request, this model is updated through notifications from the server.
The notification on new or removed tickets is missing when the element is not the root cause of the ticket.
|
Do either of the following:
•Initiate new Get command.
•For Cisco ANA NetworkVision maps, close and reopen the map.
|
3.7.1
|
CSCtg49881
|
Generates Port Down alarm instead of Link Down alarm in HA scenario
|
Cisco ANA generates alarms for a link that is down for only one of the interfaces. Also, the link between two involved VNEs stays green on a Cisco ANA NetworkVision map even though one side of the link is down per the link properties.
This situation can occur in a high availability environment under the following conditions:
1. A few VNEs from the same AVM are added to a map.
2. AVM protection is enabled on the AVM.
3. The AVM process is stopped.
4. An interface is shut down.
5. Cisco ANA brings the AVM and all VNEs back up.
|
Clear the tickets.
|
3.7.1
|
CSCtg40816
|
SBC DBE information changes after upgrade
|
After upgrading to Cisco ANA 3.7.1, logical inventory displays additional tabs and Cisco ANA internal values for SBC DBE.
|
None
|
3.7.1
|
CSCtg16978
|
VNE duplicate alarms regarding module, memory, CPU, and card down
|
Duplicate tickets and alarms are produced for Module Unsupported, Memory Utilization, CPU Utilization, and Card Down in the following situations:
•Deleting and readding a VNE.
•Restarting a gateway, unit, or VNE.
•Moving a VNE to a different AVM.
|
None
|
3.7.1
|
CSCtf90169
|
NullPointerException in AVM 11 - some VRFs are not discovered
|
Due to a race condition between discovery and VNE flapping, some VRFs and sites are not discovered.
|
Restart AVM 11.
|
3.6.6
|
CSCtf74090
|
Event archive contains redundant raw events in high availability (HA) scenario with multiple AVM 100s
|
In certain HA scenarios, after a switchover occurs, the Event Archive contains redundant raw events. This occurs on systems that meet ALL of the following:
1. High availability is enabled and the system has multiple running AVM 100s.
2. The system has a running Event Notification Service.
3. The system is configured to persist (save) events from unmanaged devices.
4. A unit switchover occurs.
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:
•Device1 is forwarding raw events to Unit1 (active) and Unit3 (standby).
•Device2 is forwarding raw events to Unit2 (active) and Unit3 (standby).
•Unit1 goes down and Unit3 becomes active.
•AVM 100 starts on Unit3, and Unit3 starts persisting all events to the event archive.
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 resolves itself as soon as the down unit (Unit 1 in the example) comes back up.
|
3.7
|
CSCtf47898
|
Cisco CRS 16-slot running Cisco IOS XR 3.8.2: Power supply issue on OIR
|
If you switch off the power supply tray on a shelf for a Cisco CRS 16-slot device running Cisco IOS XR 3.8.2, the power supplies in the shelf are displayed with the status OK in Cisco ANA.
|
None
|
3.6.6
|
CSCtf47373
|
Cisco ASR 9000: Spanning Tree not being modeled
|
Multiple Spanning Tree (MST) instances configured on Bundle-Ether interfaces on Cisco ASR 9000 devices are not modeled in Cisco ANA NetworkVision.
MST instances that are configured on physical ports are modeled correctly.
|
None
|
3.7.1
|
CSCtf36187
|
Counter 64 OID values not shown properly
|
Any Soft Property used to collect an OID that is a 64-bit counter is not displayed properly in Cisco ANA NetworkVision. The value shown is in the format [J@34d1d1.
|
None
|
3.7
|
CSCtf22181
|
Topology is not discovered when CDP is configured on subinterface only
|
If CDP is configured on a subinterface only, or on the interface and subinterface, the topology is not discovered correctly.
|
Do either of the following:
•Create a static link instead of the link that was supposed to be discovered dynamically.
•Make sure that CDP is configured only on ports and not on subinterfaces.
|
3.7
|
CSCtf00180
|
Cisco uBR10012 port is not modeled under SPA-24XDS-SFP card
|
Cisco ANA does not model ports under SPA-24XDS-SFP cards for Cisco uBR10012 devices running Cisco IOS 12.2(33)SCB2. As a result, these ports are not displayed in Cisco ANA NetworkVision maps or in inventory.
|
None
|
3.7.1
|
CSCte63920
|
Creating a cross-connect in an ATM cloud takes a long time
|
Creating a cross-connect configuration of two devices that connect to a cloud takes a long time and can appear is if the creation has failed. This situation can occur when connecting two ATM ports to a cloud VNE.
You can ignore the command status as it is actually successful.
|
None
|
3.7.1
|
CSCte33382
|
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
|
CSCte20128
|
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. Make sure all the devices are reachable (via Telnet). If some devices are unreachable, stop Cisco ANA and manually remove the respective VNEs by carefully editing the avmXXX.xml file.
2. Restart Cisco ANA and the VNEs by using the Cisco ANA GUI. Restarting the VNEs enables the VNEs to update the registry accurately. At this point, AVM 11 still fails.
3. Restart the Cisco ANA gateway. AVM 11 starts successfully because it can now read the correct registry values of the VNEs.
|
3.7
|
CSCte11960
|
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
|
CSCte10891
|
Migration: Small-scale migration takes longer than large-scale migration
|
Migrating Cisco ANA from version 3.6.7 to version 3.7 takes a few hours for a small-scale environment.
|
None
|
3.7
|
CSCte10299
|
Incorrect exception is returned for nonexistent ticket via BQL
|
Ticket operations like Acknowledge, Clear, and Remove on nonexistent or archived tickets return the wrong error message. The error displayed is "Execution failed. Tickets are in use. Please try again."
This situation occurs when a BQL command is executed on an archived or nonexistent ticket OID.
The behavior of executing BQL commands on tickets in Cisco ANA 3.7 changed from Cisco ANA 3.6.7.
|
None
|
3.7
|
CSCte09020
|
Multiple ticket selection during arrival of new tickets changes focus
|
If you select multiple tickets in Cisco ANA NetworkVision while new tickets are added, the selection is not saved. This situation occurs when a number of new tickets are added to the ticket pane while you are selecting multiple tickets.
|
Do one of the following:
•Traverse the sort (using an ascending time sort) and select multiple lines.
•Filter for all tickets older than a specific time, such as the last 5 minutes, and use the multiple selection on a stale list.
|
3.7
|
CSCtd97496
|
Duplicate AVMs are created after moving AVMs between units
|
In Cisco ANA Manage, if you perform parallel requests of AVMs, the following occur:
•Duplicate AVMs are displayed in Cisco ANA Manage
•Entries are included in the 11.out log file that start with:
"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. Go to the 11.out log.
2. For each error described in the Impact section, discover the problematic AVM number. (It is included in the error message.)
3. In ~/Main/registry/ConfigurationFiles, enter the following command if you discover that there are more than one avm<problematic-avm- id>.xml files:
grep
avm<problematic-avm-id>
*/*.xml
4. Check whether the key also exists in avm99.xml in that unit.
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. Restart the gateway.
|
3.7
|
CSCtd97183
|
Cisco ANA 3.6.x-3.7 migration: Links are removed after tickets are cleared
|
After migrating 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
|
CSCtd93871
|
Keepalive and hold time are incorrect for VRF in BGP table
|
The BGP Neighbors table (Logical Inventory > MPBGPs > MPBGP) displays the incorrect values in the Hold Time and Keepalive columns for VRFs.
|
None
|
3.6.7
|
CSCtd65670
|
Cloud Problem service alarm is not generated
|
If an Ethernet cloud is configured and an event occurs in the network that causes a problem in the cloud (such as Link Down), the Cloud Problem service alarm is not generated.
|
None
|
3.7
|
CSCtd50358
|
IPoDWDM: Trace detail script fails in Cisco CRS device with Cisco IOS XR 3.9.0 image
|
If you attempt to run the Trace detail script on the SONET ports of a Cisco CRS device with Cisco IOS XR 3.9.0, the script fails. The Trace detail script is available by right-clicking the device and then selecting Commands > SONET > Show > Trace Details.
This situation occurs for Cisco CRS devices with Cisco IOS XR 3.9.0 and SONET controllers.
|
None
|
3.7
|
CSCtd43007
|
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 running Cisco IOS version 12.2(52)SE or higher that supports the IEEE version of CFM.
|
None
|
3.7
|
CSCtd33304
|
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
|
CSCtd31477
|
MAC path trace returns exception if MAC address not found
|
If you launch a MAC address-based path trace and the MAC address is not found, an error message is displayed.
|
None
|
3.7
|
CSCtd31461
|
Cannot attach a business tag to BGP neighbors
|
If you select Logical Inventory > MPBGPs > MPBGP > BGP Neighbors and attempt to attach a business tag to a BGP neighbor, the following error is displayed: "Could not created element."
|
None
|
3.7
|
CSCtd28734
|
SSH with Cisco ASR 9000 series devices causes VTY syslogs
|
Cisco ASR 9000 series devices generate the following security syslog message each time Cisco ANA starts an SSH session with them:
%SECURITY-SSHD-6-INFO_GENERAL:
Warning: The requested
term-type is not supported
The SSH session is initiated correctly and you can ignore the message.
|
None
|
3.7
|
CSCtd28331
|
Missing ports for PA-MC-2E1-120 card on Cisco 7200 devices
|
Physical inventory in Cisco ANA NetworkVision does not model ports for PA-8E1/120 modules in Cisco 7200 devices if the module has the entPhysicalVendorType of cevPa8ce1.
In addition, any links configured on these ports are not modeled.
|
None
|
3.7
|
CSCtd15593
|
Cisco ANA 3.7 Migration: Static links between a cloud and router are lost
|
After migrating to Cisco ANA 3.7, Cisco ANA NetworkVision might not display static links that were created before the migration.
|
Delete the static link and then recreate it.
|
3.7
|
CSCtd13824
|
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 displayed in the physical inventory navigation pane.
|
3.7
|
CSCtd12855
|
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
|
CSCtc61567
|
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
|
CSCtc37407
|
Cisco ANA does not model CWDM SFP correctly
|
If a CWDM SFP is inserted into a Cisco 4900 or Cisco 4500 device, Cisco ANA NetworkVision displays the Hardware Type of CWDM GBIC instead of CWDM SFP.
|
None
|
3.7
|
CSCtb85201
|
Cisco ANA GUI application javaw.exe process shuts down occasionally
|
When working intensively on Cisco ANA NetworkVision or Cisco ANA EventVision, you might experience a Java crash causing the GUI application to close. This issue does not affect the Cisco ANA server and is related only to the Java GUI applications running on a Windows machine with some models of Nvidia graphics cards.
This situation can occur while working with multiple open windows of the Cisco ANA application. The crash happens sporadically with no specific scenario.
|
Do either of the following:
•Restart the Cisco ANA application.
•Consider updating your graphics card driver (the latest drivers for a particular card are usually available on the website of your computer, video card, or video chip manufacturer, such as http://www.nvidia.com)
|
3.7
|
CSCtb54145
|
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
|
CSCtb40790
|
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 ethernet
xconnect 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 ethernet
xconnect 172.255.3.175
999999 encapsulation mpls
The 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
|
CSCta70258
|
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:
•Use snmp get and snmpwalk commands.
•Use other tools to retrieve the attribute.
•Use CLI commands directly on the affected router.
|
3.6.7
|
CSCta49041
|
Notification not generated after changing user role
|
If you add a user with the Administrator role, log into Cisco ANA Manage, and change the user role from Administrator to Operator, Viewer, or Configurator, no error message is generated when the user with the Administrator role attempts to add an AVM or VNE.
|
After changing the user role from Administrator to another role, log out and log in again for the change to take effect.
|
3.6.7
|
CSCta47166
|
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
|
CSCta46622
|
LAG topology between MSTP and PVSTP devices is not discovered
|
Link Aggregation (LAG) links are not discovered in Cisco ANA NetworkVision between devices when one of the devices is configured for Per-VLAN Spanning Tree Protocol (PVSTP) and the other device is configured for Multiple Spanning Tree Protocol (MSTP).
The physical link is discovered if CDP or LLDP is configured on the devices.
The LAG link is discovered if the LAG runs LACP protocol.
|
None
|
3.6.7
|
CSCta33768
|
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
|
CSCta08126
|
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.1 Reference Guide for details on the supported technologies.
|
3.6.5
|
CSCta02983
|
Error in Registry Editor
|
A general error is displayed in Registry Editor.
|
None
|
3.6.5
|
CSCsz81967
|
BQL adapter does not raise an error when a BQL command contains invalid data
|
If you enter the IMO property name incorrectly while creating a BQL command, the BQL command disregards this property without displaying an error.
For example, if the command contains an "Index" property and you enter "index" as the property name, the value is disregarded.
|
None
|
3.6.5
|
CSCsz81399
|
Cloud: Cisco 3750 switch MAC address does not appear in Bridge table
|
For some Cisco 3750 devices connected to a cloud, Cisco ANA NetworkVision logical inventory shows the connected interface in the Interfaces table but the MAC addresses do not appear in the Bridge table.
|
None
|
3.6.7
|
CSCsz61942
|
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
|
CSCsz33626
|
Cisco 4503 device: Dynamic VLAN type is shown as static VLAN
|
For Cisco Catalyst 4503 devices, the dynamic VLAN setup is displayed as static VLAN in Cisco ANA NetworkVision.
|
None
|
3.6.6
|
Resolved Caveats - Cisco ANA 3.7.1
Table 33 identifies the caveats resolved in Cisco ANA 3.7.1.
Table 33 Resolved Caveats in Cisco ANA 3.7.1
Identifier
|
Summary
|
CSCth36614
|
Unit AVMs are unreachable when the Unit protection group is disabled
|
CSCth02801
|
Soft Properties GUI does not support negative numbers for TCA threshold
|
CSCtg88728
|
User role and scope bug
|
CSCtg73766
|
Cisco ANA client does not work with Oracle secured connection
|
CSCtg71147
|
Cisco ASR 9000: Need to support dot1qgCfmFaultAlarm 1.3.111.2.802.1.1.8.0.1
|
CSCtg49631
|
TFS does not send the correct EPM-MIB (cenAlarmIndex in wrong place)
|
CSCtg19555
|
Event notification svc resets cenUserMessages after update TFS
|
CSCtg12044
|
Part of CDP links are not discovered
|
CSCtf68795
|
Handling reserved characters in Cisco ANA cross-launch URL
|
CSCtf32482
|
Removing 200 tickets frequently results in operation timeout
|
CSCte73853
|
Bells are not always removed after being acknowledged
|
CSCte72094
|
No reflection in severity aspect for event with severity of Information
|
CSCte71607
|
Severity aspect: Concurrency issue with force-clearing events
|
CSCte60447
|
Network VLANs that are deleted are not rediscovered
|
CSCte52642
|
Static port creation on ATM cloud not working on Cisco ANA 3.7
|
CSCte33895
|
Dropped packets on port alarm does not show the right port number
|
CSCte33850
|
Cisco MWR devices: BFD entries missing from logical inventory
|
CSCte20937
|
Filter on tickets in Cisco ANA NetworkVision does not filter notified ticket
|
CSCte19593
|
Missing XFP port connectors for Cisco CRS-1 device are not populated
|
CSCte09049
|
The system does not support 2000 CE VNEs on one unit
|
CSCte08952
|
BFD service shown as running in Cisco GSR devices running Cisco IOS XR all the time
|
CSCte07394
|
Adding new EFP to a loaded Cisco ASR 9000 series device takes a long time to be discovered
|
CSCte03061
|
Q-in-Q is not modeled in Cisco GSR XR 3.8.2
|
CSCtd97095
|
Online Help PDF of Cisco ANA Administrator Guide or Cisco ANA User Guide cannot be displayed in Mozilla
|
CSCtd91747
|
Cisco ANA 3.6.7 Registry backup issue
|
CSCtd88045
|
Ticket Severity Update filtering does not forward events
|
CSCtd81511
|
Port is not displayed in the inventory with AToM subinterfaces
|
CSCtd81288
|
Events not generated after flapping
|
CSCtd73933
|
Events cannot be collected when there is a clean install of Cisco ANA 3.6.7
|
CSCtd72122
|
Exception when editing or creating a VNE
|
CSCtd66437
|
10-Gigabit Transceiver Port Container names are incorrect
|
CSCtd60719
|
Cisco 7600 device running Cisco IOS SRE and Cisco ASR 1000 device running RLS5: MPBGP is not modeled
|
CSCtd60561
|
BFD throwing java.lang.NullPointerException
|
CSCtd57854
|
Restore BOS Shell user
|
CSCtd57828
|
Cisco GSR device: Configuring an EtherChannel removes the node from logical inventory and does not update the DC
|
CSCtd52182
|
Cisco ME 3400 device flows do not support blocking between ENI ports
|
CSCtd46256
|
SBC call policy sets and blacklists are not modeled for Cisco ASR 1000 devices
|
CSCtd38258
|
Cisco CRS SDR VNEs do not map correct card slots to devices
|
CSCtd36077
|
Cisco ANA 3.7 Migration: Old tab alarm filters cannot open
|
CSCtd33714
|
ExceptionInInitializerError when opening two Cisco ANA Workflow Editor sessions simultaneously
|
CSCtd31553
|
SBC script commands are not supported in RLS5 image
|
CSCtd31314
|
Cisco GSR XR device discovery and modeling take more than an hour
|
CSCtd31285
|
Cannot edit or define a business tag for a physical subinterface
|
CSCtd28686
|
Cisco ANA EventVision accessible to Viewer role
|
CSCtd25159
|
ANA 3.7 Migration: Cisco ANA 3.6 cannot be uninstalled after Cisco ANA 3.7 migration
|
CSCtd16567
|
Few MST entries missing from the logical inventory of Viking device
|
CSCtd15592
|
NetworkVlanDiscoveryPlugin: Exception upon AVM 11 loading
|
CSCtc70478
|
For Cisco Viking devices, TE FRR status is not updated in the next interval
|
CSCtc43118
|
VNE physical inventory does not model Cisco 7206 VXR devices
|
CSCtc37432
|
Cisco ANA does not set transceiver-related properties for Cisco Catalyst 4500 and 4900 devices
|
CSCtc27946
|
Event source of any TE Tunnel trap is linked to IP Interfaces tab
|
CSCtc09819
|
Cisco ANA does not set PIDs correctly for transceivers on SUP in Cisco 7600 devices
|
CSCtb82922
|
REP topology is not discovered
|
CSCtb67791
|
Alarm Ticket: Couldn't be found message displayed if you attempt to remove tickets
|
CSCtb51738
|
POS port is not modeled under PA-POS-10C3 module for Cisco 7200 devices
|
CSCtb49799
|
For Cisco 1800 devices, some properties are missing for modules
|
CSCtb36765
|
For Cisco 2800 devices, junk values are returned in tree view
|
CSCtb33211
|
Fan tray for Cisco CRS device shows unknown status
|
CSCtb16314
|
Cisco ANA is not able to discover interfaces in inventory when GBIC is missing
|
CSCtb11703
|
On Cisco 3800 devices, HWIC-1GE-SFP ports are not modeled correctly
|
CSCtb11464
|
Dual ports are not modeled properly
|
CSCta56359
|
Part IDs are incorrect for pluggable Cisco 1000BaseSX modules
|
CSCta54345
|
After adding LAG topology to an existing device, the map is not updated
|
CSCta54115
|
Junk characters are included in physical model name
|
CSCta17212
|
The cmpctl script does not always return an error message for illegal input
|
CSCta00886
|
No connection from the GRE DC to the underline IP Interface
|
CSCsz76766
|
Attributes such as clocking, framing, loopback, and scrambling are not populated
|
CSCsz61137
|
Clear all ticket does not put the VNE into the green state
|
CSCsz50727
|
VLAN and bridge information is missing from Cisco ANA PathTracer over an Ethernet cloud
|
CSCsz11805
|
Physical port is not getting modeled for Cat4503-E
|
CSCsy33815
|
Improper modeling of Power and Fan modules of 6500VSS
|
CSCsx78454
|
Low GUI performance while working with a maximum sized map
|
Related Documentation
User Guides
Cisco Active Network Abstraction 3.7.1 Documentation Guide
Cisco Active Network Abstraction 3.7.1 User Guide
Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide
Cisco Active Network Abstraction 3.7.1 Reference Guide
Cisco Active Network Abstraction Configuration and Image Management 1.0 User and Administrator Guide
Cisco Active Network Abstraction Network Service Activation 1.1 User Guide
Administrator Guides
Cisco Active Network Abstraction 3.7.1 Installation Guide
Cisco Active Network Abstraction 3.7.1 Administrator Guide
Cisco Active Network Abstraction Configuration and Image Management 1.0 User and Administrator Guide
Developer Guides
Cisco Active Network Abstraction 3.7.1 Customization User Guide
Cisco Active Network Abstraction 3.7.1 Integration Developer Guide
Cisco Active Network Abstraction Network Service Activation 1.1 Customization Guide
Other Documentation
Open Source Used in Cisco Active Network Abstraction 3.7.1
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 1999-2011 Cisco Systems, Inc. All rights reserved.
