Cisco Active Network Abstraction

Table Of Contents

Release Notes for
Cisco Active Network Abstraction, 3.6
Service Pack 2

Contents

Introduction

New Features in Cisco ANA 3.6 Service Pack 2

New VNEs Introduced

Enhanced Functionality for VNEs

Service Alarms Added

Correlation Over Unmanaged MPLS Core

Changes from the Last Release

Important Notes

Installation Notes

Memory Consumption

Generating SSH Keys

Backward Compatibility

Before Installing Cisco ANA 3.6 Service Pack 2

During the Installation of the Cisco ANA 3.6 Service Pack 2

Solaris 10

Solaris Services and Components

CRS VNE

Daylight Savings Time Tool for Cisco ANA

Configuring Database Storage (Redo Logs)

Online Help

Limitations and Restrictions

Cisco ANA NetworkVision

Cisco ANA Fault Management

Cisco ANA High Availability

Cisco ANA Workflow Editor

OSPF

HSRP

ATM Topology Discovery

Adaptive Polling

BGP Neighbors

Open Caveats - Release Cisco ANA 3.x

Resolved Caveats - Cisco ANA, Release 3.6 Service Pack 2

Documentation Updates

Cisco Active Network Abstraction Fault Management User Guide

Flapping

Supported Service Alarms

All ip interfaces down

Cloud problem

Interface status

Link down

Professional Services Note

Related Documentation

User Guides

Administrator Guides

Developer Guides

Obtaining Documentation and Submitting a Service Request

Release Notes for
Cisco Active Network Abstraction, 3.6
Service Pack 2

---

April 7, 2009

These release notes support the release of Cisco Active Network Abstraction, 3.6 Service Pack 2.

---

Note See Cisco.com for the most up-to-date version of the Release Notes for Cisco Active Network Abstraction, 3.6 Service Pack 2.

---

Contents

This document includes the following topics:

•Introduction

•New Features in Cisco ANA 3.6 Service Pack 2

•Changes from the Last Release

•Important Notes

•Limitations and Restrictions

•Open Caveats - Release Cisco ANA 3.x

•Resolved Caveats - Cisco ANA, Release 3.6 Service Pack 2

•Documentation Updates

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

These Release Notes support the release of Cisco Active Network Abstraction, 3.6 Service Pack 2 (Cisco ANA 3.6 Service Pack 2).

Cisco ANA 3.6 is a carrier-class, multi-vendor network and service management platform providing the flexibility for carriers and service providers to efficiently respond to the constant market demand for new, reliable and more sophisticated services.

Cisco ANA 3.6 understands network characteristics and builds a real-time virtual model of the network, serving as a live information base for value-added tools and applications capable of seamless integration within a customer's existing OSS environment.

Cisco ANA 3.6 provides a unified solution for diverse network environments and applications. Implemented with a highly-scalable distributed architecture, Cisco ANA 3.6 offers integrated configurable network resource management, network and service discovery, network and service fault isolation and a highly flexible service activation engine. These integrated applications enable correlated management of global scale networks supporting millions of subscribers and customers.

Cisco ANA 3.6 is a unified, fully-integrated solution offering:

•Multi-vendor device support

•Multi-Technology coverage: IP, Layer 2 and Layer 3 VPN, xDSL, ATM, Frame Relay, Gigabit Ethernet, Ethernet, 802.1Q, Inter-Switch Link (ISL), QinQ VLAN tag (QinQ), Spanning Tree Protocol (STP), Layer 2 Tunneling Protocol (L2TP), and routing protocols (such as Border Gateway Protocol [BGP]).

•Integrated device, network and service management functionality

•Open interfaces for integration with multiple OSS/BSS applications

Cisco ANA 3.6 dynamically discovers and identifies basic network components, while obtaining end-to-end visibility of the network resources, connections and dependencies, enabling Cisco ANA 3.6 to manage and analyze network behavior. Cisco ANA 3.6 builds its end-to-end understanding of the network structure and inter operability, across vendors, technologies and network layers, into a customer-specific virtual network model for each and every installation.

The virtual network model within Cisco ANA 3.6 is an always maintained up-to-date enabling powerful device, network and service management functionality, including:

•Configurable Device Manager: Basic resource management features for multi-vendor devices

•Network and Service Discovery: Physical and logical discovery with multi-layer network and service connectivity

•Network and Service Fault Isolation: End-to-end, topology-based fault isolation, monitoring & root cause analysis

•Service Activation

•And a series of product options including Northbound APIs, Path Tracing and Client UIs

New Features in Cisco ANA 3.6 Service Pack 2

The following new features were added in Cisco ANA 3.6 Service Pack 2:

•New VNEs introduced—For more information see New VNEs Introduced.

•Enhanced functionality for existing VNEs—For more information see Enhanced Functionality for VNEs.

•New service alarms introduced:

•BGP Link Down—Indicates that a BGP neighbor entry has changed its state from Established to another state, or a BGP neighbor entry that had an Established state has been removed from the BGP neighbors table and the entry has an adjacent peer.

See Service Alarms Added.

•BGP enhancement—The system now detects BGP links between BGP peers with different AS numbers.

•Correlation over unmanaged MPLS core—This relates to scenarios in which only PE devices in MPLS networks are managed (the MPLS Core-P routers are not managed). Along with BGP connectivity loss the following issues may arise:

–Failure on the managed unreachable PE or Route Reflector (RR).

–One or more PEs or RRs report BGP connectivity loss to a neighbor, which becomes unreachable.

–No additional issues arise.

See Correlation Over Unmanaged MPLS Core.

•Cloud enhancement—In previous releases the Cloud VNE could simulate an Ethernet network with (optionally) multiple VLANs configured, in which the endpoints were routers with Ethernet interfaces. Cisco ANA 3.6 SP2 now supports LAN switches as endpoints.

•Fast polling—Fast polling is not supported in Cisco ANA 3.6 Service Pack 2.

---

Note When upgrading from a previous version, any VNE which was configured with a fast polling group, will be loaded in a down state for SP2. See the workaround for CSCsl72454.

---

•Source association fallback—In some cases, the event source may not be in the internal VNE model at the time of the event notification. For instance, when a new module is inserted, it takes some time for Cisco ANA to poll all of its interfaces and build up (populate) the model. If the new event notification is handled before the model is fully populated, the association logic may fail to find and retrieve the entity that is the correct source of the trap. A retry mechanism minimizes the occurrence of such a race condition, but if it persists, the association logic will fallback to the managed element entity (Network Element) that is the source of the new event. An additional identifier (the alarm differentiator), representing the intended source, is later used in the correlation logic. See also alarm differentiator in the Cisco Active Network Abstraction Fault Management User Guide.

•T2000 Server—The hardware requirements for the Cisco ANA Gateway have been enhanced with an additional option as follows:

Item	Specifications
Hardware Requirements
Sun server based on Sun UltraSPARC T1 Recommended: Sun Fire T2000	•1* 8 core, at least 1200 MHz UltraSPARC T1 Processor •Solaris 10 compatible •Minimum of 16 GB RAM •Swap file must be at least twice the size of the installed RAM. •2 x 73 GB HDD space Note For information on how disk space is configured on the gateway, see Recommended Disk's Structure in the Cisco Active Network Abstraction Installation Guide. •1 x DVD drive

•The maximum memory that may be used on the Sun T2000, when it is defined as a Cisco ANA Unit, has now been increased from 16 GB to 32 GB.

---

Note Increasing the memory size along with memory consumption due to additional AVMs and VNEs will increase the unit's start up time.

---

New VNEs Introduced

This section details the Virtual Network Element (VNE) device support information for Cisco ANA 3.6 Service Pack 2.

Table 1 Cisco ANA 3.6 Service Pack 2 VNEs 

Vendor	Device Classification	Device Family	Device Type/Product No.
Juniper	Router	T Series	640
Lucent	Ethernet Switch	Riverstone	1000
Lucent	Ethernet Switch	Riverstone	1100
Lucent	Ethernet Switch	Riverstone	3000
Lucent	Ethernet Switch	Riverstone	3100

For details of the type of support provided for each VNE see the Cisco Active Network Abstraction VNE Reference Guide 3.6 Service Pack 2.

The Service Pack also includes support for additional modules and software versions for VNEs that are supported by previous Cisco ANA releases. For details of the updated list, refer to Cisco Active Network Abstraction VNE Reference Guide 3.6 Service Pack 2.

Enhanced Functionality for VNEs

Table 2 Enhanced Functionality for Cisco ANA 3.6 Service Pack 2 VNEs 

Vendor	Device Classification	Device Family	Functionality
Juniper	Router	M Series,T Series	Traps added.
Juniper	Router	M Series,T Series	Adaptive Polling added.
Cisco	Router	CRS-1	Traps added.
Cisco	Router	CRS-1	LAG Support added.
Cisco	Router	GSR-IOX	LAG Support added.

For details regarding scheme support see the Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6 Service Pack 2.

Service Alarms Added

Table 3 provides a summary of the service alarms that have been added in Cisco ANA 3.6 Service Pack 2.

Table 3 Service Alarms Added in Cisco ANA 3.6 SP 2 

Alarm	Description	Clearing Alarm
BGP link down	Issued when both sides of the BGP link are managed and the BGP neighbor entry has changed its state from Established to another state, or a BGP neighbor entry that had an Established state has been removed from the BGP neighbors table and the entry has an adjacent peer.	BGP link up
BGP link down vrf	Issued in the same conditions as the BGP link down alarm except that the neighbor is defined in the context of a VRF (BGP connection between PE router and CE router).	BGP link up

For more information about event and alarm configuration parameters, see the Cisco Active Network Abstraction Fault Management User Guide.

Correlation Over Unmanaged MPLS Core

Correlation over unmanaged MPLS core—This relates to scenarios in which PE devices and RRs in MPLS networks are managed (the MPLS Core-P routers are not managed).

---

Note If the other side of the link becomes unreachable the "BGP link down" correlates to the concrete issue discovered on the reachable side.

---

Along with BGP connectivity loss the following issues may arise:

•Scenario A—Failure on the managed unreachable PE or RRs.

In this scenario a failure on the managed PE and RRs caused BGP connectivity loss. The system is able to detect the failure since the management connection to the PE and RRs is not lost. The system detects:

–BGP connectivity loss to one or more PEs or RRs

–One of the following types of failures on the PE or RR: port down, interface down, BGP process down.

Assuming the failed BGP and RR connections are established through the failed port or interface, the following correlation will be reported:

–Port down, interface down or BGP process down as root cause.

–One or more BGP link down alarms correlated to one of the three root causes mentioned above.

•Scenario B—One or more PEs or RRs report BGP connectivity loss to a neighbor, which becomes unreachable.

In this scenario either a failure in the unmanaged network occurred or the neighboring PEs or RRs were disconnected from the network for some reason. The system is able to detect the "BGP link down" if at least one of the edge points is still managed. The system will report the following correlation:

–Device unreachable as the root cause.

–One or more BGP link down alarms correlated to the device unreachable (only if the device unreachable is on one side of the lost BGP link).

---

Note Where more than one device unreachable is detected, a separate ticket is opened for each.

---

•Scenario C—No additional issues arise.

In this scenario only a BGP neighbor loss is reported from the devices on both sides of the BGP links. The edge points remain managed. The system will report the "BGP link down" as the root cause of the ticket.

---

Note Where multiple BGP links fail, a separate ticket is opened for each.

---

Changes from the Last Release

This section includes the following:

•Product Scheme—The product scheme is now configured to poll all routing entries that were learned through the BGP protocol.

•Service Alarms—The following changes were made in this release:

–Cloud up was removed.

–Cloud down is now defined with an Information severity.

Important Notes

This section includes the following:

•Installation Notes

•Solaris 10

•Solaris Services and Components

•CRS VNE

•Daylight Savings Time Tool for Cisco ANA

•Configuring Database Storage (Redo Logs)

•Online Help

Installation Notes

This section includes the following:

•Memory Consumption

•Generating SSH Keys

•Backward Compatibility

•Before Installing Cisco ANA 3.6 Service Pack 2

•During the Installation of the Cisco ANA 3.6 Service Pack 2

For the installation see the Cisco Active Network Abstraction Installation Guide, 3.6 Service Pack 2.

This service pack is installed as a patch on top of the existing installation of Cisco ANA 3.6 and all Service Packs prior to SP2 and allows automated installation with the minimum of manual operations.

---

Note If other patches have been installed on top of Cisco ANA 3.6, they must be uninstalled before installing the Service Pack. See the Cisco Active Network Abstraction Installation Guide.

---

Memory Consumption

In a situation where there are several routers that maintain a few thousand BGP routing entries or more in their routing table, and the VNEs for these devices are using the product scheme, memory consumption may have increased and AVM memory allocations should be checked. Please contact the Cisco Project Manager or Cisco Account Team to perform the necessary calculations.

Consult the Enhanced Functionality for Cisco ANA 3.6 Service Pack 2 VNEs table to review whether new technology modeling was added to the VNE in use in your deployed environment. In the event that new modeling was added, memory consumption may have increased and AVM memory allocations should be checked. Please contact the Cisco Project Manager or Cisco Account Team to perform the necessary calculations.

Generating SSH Keys

When adding a unit to an already existing setup, the SSH keys must be generated. For more information see the Cisco Active Network Abstraction Installation Guide.

Backward Compatibility

With regard to backward compatibility of the Cisco ANA 3.6 Service Pack 2 with existing installations of Cisco ANA 3.6 note the following:

•Before performing the installation review the Best Practices for Integration BQL Parsing chapter in the Cisco Active Network Abstraction BQL User Guide, 3.6 Service Pack 2 to ensure that the integration is not affected.

•All system configuration changes made to the registry are maintained.

Before Installing Cisco ANA 3.6 Service Pack 2

If other patches or fix packs have been installed on top of Cisco ANA 3.6 they must be uninstalled before installing the Cisco ANA 3.6 Service Pack 2.

To uninstall:

---

Step 1 Remove the patch name from the site.xml by running the following command from the gateway Main directory:

./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 site/mvm/services/bsm/patchjar <new value>

---

Note The <new value> is usually the same value without the spoken patch (most of the time it is the last one).

---

Step 2 Remove the patch name line from all .jnlp files in the directory ~/Main/webstart.

Step 3 If the patch does not include xml or class files, for example, perl script, all of the old files are copied into the backup directory. The location of the backup directory is:

The home directory of the <user sheer>/backup. The files directory tree is maintained.

The file names convention is: <filename>_<patchname>_<date>.bak

When reverting back, copy the file under the same directory tree starting from the Main directory, and then change the file names and make them executable.

Step 4 Restart all the units and the gateway by running mvm.csh. For more information see the Cisco Active Network Abstraction Installation Guide 3.6 Service Pack 2.

---

During the Installation of the Cisco ANA 3.6 Service Pack 2

If the error java.io.FileNotFoundException: Main/scripts/redirectUdp.pl (Permission denied) occurs when you run perl ./update.pl SP2 -all, enter the following commands in the ANAPatch directory (with root user):

jar -xvf patch_other.jar 
cp Main/scripts/redirectUdp.pl /export/home/sheer4/Main/scripts/redirectUdp.pl

Solaris 10

The recommended operating system to run Cisco ANA 3.6 Service Pack 2 on SUN servers is Solaris 10. Cisco ANA 3.6 Service Pack 2 is compatible with the latest patch release as published by Sun on January 18, 2008 (the ID of the Cluster patch is: Generic_120011-14). This patch release contains the following patches:

Table 4 Sun Patch Release (18 January 2008) 

Patch Number	Patch Number
116781-02	117447-01
117463-05	118371-10
118373-01	118564-03
118731-01	118879-02
118890-03	118925-05
118929-05	119012-03
119073-03	119077-10
119265-02	119332-01
119336-01	119573-02
119580-05	119586-02
119593-01	119685-11
119824-02	119826-02
119981-09	119985-02
119998-02	120023-01
120032-04	120048-03
120050-06	120469-07
120473-12	120629-08
120780-04	120809-01
120824-09	120845-05
120990-02	120998-02
121006-02	121010-06
121215-01	121229-02
121235-01	121278-01
121282-02	121284-02
121288-03	121292-01
121294-01	121406-01
121473-01	121474-01
121476-01	121478-01
121786-01	121905-01
122251-01	122328-01
122404-01	122412-01
122513-02	122535-01
122637-01	122646-02
122658-04	122660-10
122662-05	122752-04
123017-01	123249-02
123256-02	123324-03
123330-01	123350-01
123354-03	123356-02
123362-01	123418-02
123420-02	123422-03
123441-05	123444-01
123910-03	123911-01
123916-05	123954-01
124204-04	124208-01
124250-03	124254-04
124258-07	124280-01
124286-01	124327-04
124442-01	124916-03
124918-02	124921-02
124922-03	124987-02
124990-01	124993-01
124995-01	125009-01
125011-01	125014-03
125018-02	125020-01
125024-01	125026-01
125028-02	125028-03
125035-01	125040-01
125042-02	125073-01
125077-03	125079-01
125100-10	125112-01
125114-01	125116-02
125118-01	125120-03
125123-01	125127-01
125129-01	125198-02
125203-01	125329-03
125363-06	125371-01
125383-01	125385-02
125420-01	125422-01
125424-01	125427-01
125430-01	125432-01
125465-02	125478-01
125486-01	125488-02
125492-01	125494-02
125497-01	125792-01
125795-01	126255-01
126303-02	126310-01
126320-01	126429-01
126536-01	126663-01
126838-01

---

Note For any later patches distributed by Sun, please contact the Cisco Project Manager or Cisco Account Team.

---

Solaris Services and Components

The following table lists the Solaris services and components that are being used by the Cisco ANA system and must not be removed:

Table 5 Solaris Services and Components used by Cisco ANA

Name	Description of function	Configuration information	TCP and UDP port numbers	Traffic classification
Xntpd	Time server	/etc/inet/ntp.conf	123 (UDP)	ntp
/bin/tcsh	Unix shell	None	None	None
/usr/bin/tcsh	Unix shell	None	None	None
Perl	Scripting language	None	None	None
/bin/sh	Unix shell	None	None	None
Rsh/rexec	Remote shell	None	512,513,514 (TCP)	None

The following table lists the product services that are installed with the Cisco ANA system:

Table 6 Product Services Installed with Cisco ANA 

Name	Description of function	Configuration information	TCP or UDP port numbers	Dynamic TCP or UDP port ranges	Inter-dependencies with other features, applications and services	Traffic classification
Avm[1-999]	Main app	Main/registry/Avm[NUM].xml		2000-3000, 8000-9000 (TCP)	Java,Perl,Tcsh	Inner protocol
Udp2icmp	Icmp redirector	-	10001 (UDP)	-	Perl	-
redirectUdp	Udp redirector	-	162,1162,514,1514 (UDP)	-	Perl	-
Sheer_secured	Secured connectivity between gateway and unit	local/sheer_secured/sheer_config	1101 (TCP)	-	-	ssh
webserver	Serves the client webstart and the bloodtest.	utils/apache/conf/ sheer.conf	1310, 1311 (TCP)	-	-	http
Machine interface	BQL machine to machine interface	-	9002 (TCP)	-	Java	-
secure machine interface	Secured BQL machine to machine interface	-	9003 (TCP)	-	Java	-
transport switch	Gateway/unit internal message bus	-	9290 (TCP)	-	Java	-
Client Applications Transport	Client/ Gateway message bus This point to point (PTP) connection is secured by SSL.	-	9771 (TCP)	-	Java	-
Syslog redirector	Redirects syslog messages	-	1162 (UDP)	-	-	-
Traps redirector	Redirects trap events	-	1512 (UDP)	-	-	Snmp

CRS VNE

As a prerequisite for the CRS-1 VNE, install the Cisco IOS XR Manageability Package on top of the IOS-XR version. In addition, the device configuration must contain the command, xml agent tty.

When creating the SNMP community, configure a new SNMP community that has SystemOwner privileges. To do this login to the device and create a new community READ with SystemOwner privileges, and then direct the ANA VNE to use the new community. For example:

snmp-server community 1icpub RO SystemOwner

snmp-server community ate9riv RW

Daylight Savings Time Tool for Cisco ANA

As Cisco ANA comes with JDK 1.4.2_13 it is possible that the daylight savings time at your location has changed since JDK 1.4.2_13 was released. If you suspect that this is true for you, you can use Sun's Daylight Savings Time tool in order to be up to date with the latest daylight savings time as published by SUN.

1. Download the JDK US DST Timezone Update Tool - 1.2.2 from the Java.sun.com website. Currently the download URL is:

http://java.sun.com/javase/downloads/index.jsp

2. Extract the tzupdater.jar file from the downloaded zip file and copy them to /tmp on the gateway and unit machines.

3. On all the gateway and units machines perform the following steps:

a. Login to the machine as sheer.

b. Stop all AVM processes

c. Enter the /tmp directory.

d. Execute the command: java -jar tzupdater.jar -u -v

4. Restart the Cisco ANA system.

Configuring Database Storage (Redo Logs)

Anyone already running Cisco ANA 3.6 should change the Oracle installation to write the logs on a different disk. For more information see the Cisco Active Network Abstraction Installation Guide.

Online Help

The online help for Cisco ANA 3.6 Service Pack 2 has been tested using the following browsers:

•Microsoft Internet Explorer version 6

•Firefox version 2.0

•Avant Browser version 11 build 25

---

Note The online help was not updated for this version. The most current product documentation for Cisco ANA 3.6 Service Pack 2 is available on Cisco.com at the following URL:
http://www.cisco.com/en/US/products/ps6776/tsd_products_support_series_home.html

---

Limitations and Restrictions

This section includes the following limitations and restrictions:

•Cisco ANA NetworkVision

•Cisco ANA Fault Management

•Cisco ANA High Availability

•Cisco ANA Workflow Editor

•OSPF

•HSRP

•ATM Topology Discovery

•Adaptive Polling

•BGP Neighbors

Cisco ANA NetworkVision

Cisco ANA NetworkVision with a configuration 512MB of free-non virtual memory per running instance, supports across all of the maps that are open, a maximum of 10000 objects (devices, VPNs, VRFs and sites) 12000 links and 10000 tickets (if the same tickets are displayed in different maps, each instance will be counted separately).

One map in Cisco ANA NetworkVision, supports a maximum of 5000 objects, 6000 links and 5000 tickets.

The maximum number of maps that can be opened for Cisco ANA NetworkVision is five (default), regardless of the number of devices, links and tickets, but this number is configurable assuming that the overall number of links and devices per application do not exceed the maximum limits. For information about customizing the maximum number of maps, please contact the Cisco Project Manager or Cisco Account Team.

Cisco ANA Fault Management

The maximum number of open tickets (other tickets can be correlated to them) for the system is 5000. This number is configurable in the registry, however we do not recommend increasing it. For a definition of an open ticket, see the Cisco ANA Fault Management Guide, 3.6 Service Pack 2. The operator should ensure that tickets are closed on time.

---

Note Changes to the registry should only be carried out with the support of Cisco, for details please contact the Cisco Project Manager or Cisco Account Team.

---

A "tickets capacity overflow" system alarm is generated when this number is exceeded. The alarm severity is defined as critical.

Cisco ANA High Availability

The high availability mechanism will attempt to load an AVM, after it crashes, a maximum of five times. Thereafter, the high availability mechanism will not try to reload this AVM again and a system event will be issued. Instead, you must stop and restart the AVM manually.

Cisco ANA Workflow Editor

The following restriction applies to the names of Workflow templates.

The user should not include the "_" and "%" characters (wildcard characters) in Workflow template names when executing a workflow or referencing a subflow as this can lead to ambiguity. The execution will fail and the following message will be displayed in the AVM66 log:

"WARN [13 21:00:08,248] - dralasoft.workflow - Task aborted. Task: 245886, Workflow: 
245885 java.lang.IllegalArgumentException: Template AA_BB.template is ambiguous, templates 
ids are: 245874 , 245873"

"_" denotes any single character

"%" denotes a zero or many characters

The following examples depict workflow template names that can lead to ambiguity if they are deployed together:

In this example the WFTLM_MUESTRA.template leads to ambiguity with the WFTLM#MUESTRA.template when they are deployed together.

In this example the WFTLM%MUESTRA.template leads to ambiguity with the WFTLM####MUESTRA.template when they are deployed together.

The ambiguity only occurs if the template containing the wild characters is executed.

OSPF

OSPF networks are presented in the Cisco ANA logical inventory. The current implementation was developed to present non-overlapping interfaces, namely, in a case where a device has multiple interfaces with the same IP (for example, in multiple VRFs configurations) that participate in different OSPF networks, only one interface is displayed.

This situation may occur when multiple OSPF processes are running on the device.

OSPF processes (OSPFService) currently do not have IMO representation in Cisco ANA.

HSRP

For correlation to work, the path through which the HSRP signaling passes must be modeled (exist) in the system.

ATM Topology Discovery

ATM topology discovery is performed in two phases:

1. Discovery matches active VCs/VPs on the ATM ports.

2. Discovery matches the traffic signatures of the VC/VPs that were identified during the first phase.

ATM topology discovery is supported on topologies where the ports at either end of the connection are both configured with VCs or VPs. Discovery is not supported on ATM topologies where VPs are configured at one end and VCs are configured at the other end.

Adaptive Polling

Adaptive polling is only supported for Cisco devices and the Juniper VNE.

BGP Neighbors

•When both IP and VPN capabilities are enabled between BGP neighbors only the VPN capability's state will be displayed in the MpBGP neighbors table.

•In order to support the BGP fault mechanism, each device must have a unique BGP router ID.

Open Caveats - Release Cisco ANA 3.x

Table 7 Open Caveats - Release Cisco ANA 3.x 

Identifier	Title	Impact	Workaround	Release #
CSCsj82011	ANA3.6: Catalyst4948: Module Serial Number and Software version missing	In ANA 3.6.2 for Catalyst4948 Module Serial Number and Software version missing for one of the modules.	None	3.6 SP2
CSCsl14813	ANA doesn't login to the Juniper device using SSH	When a device is reachable only with SSH2 and loading a VNE by SSHv2, the device will appear as device unreachable (for the VNE). When connecting to the device by SSHv2 there is no connection problem.	The workaround solution for this scenario requires changes to the site.xml. Note Contact the Cisco Project Manager or Cisco Account Team for further assistance related to this issue.	3.6 SP2
CSCsl20680	Juniper M10i both routing engines appear as routing engine 0	Juniper M series, two routing engines appear as 0. In the case of two routing engines, they both appear as "routing engine 0".	None	3.6 SP2
CSCsl45444	Problem in displaying serial number for modules in physical inventory	Cisco 3560 with version "12.2(25)SEE2": the serial number has a "NULL" value. Cisco 7204VXR with version "12.2(31)SB3x": the serial number parameter does not exist at all.	None	3.6 SP2
CSCsl47680	NODE-STATE-CHANGE syslog is not supported	NODE-STATE-CHANGE syslog is not supported for Cisco IOS XR.	None	3.6 SP2
CSCsl49642	Link down not issued when one side of the link is a 7600 device	Link Down alarm is not issued when shutting down an interface.	None	3.6 SP2
CSCsl70131	ANA generates false alarms if rejections are made at the ACS/Tacacs+	ANA may create false alarms as if the device lost all entities of a certain type, for example, all BGP neighbors, all IP interfaces or all routing entries. This bug affects network setups which use TACACS for Telnet command authorization. The symptom may occur: 1. If the TACACS server becomes too busy and doesn't reply to a device's authorization request on time. 2. If the TACACS server administrator lowers the privilege of the ANA Telnet user, blocking it from inspecting some of the device's configuration.	None	3.6 SP2
CSCsl72454	Fast Polling: Device Unreachable when upgrading from SP1 to SP2	When upgrading to Cisco ANA 3.6 SP2, VNEs that were defined as fast polling groups are loaded in a down state and are missing their Telnet sequence & SNMP community in the GUI.	1. Change the polling group of these VNEs to a valid polling group. 2. Restart the system by running mvm.csh - the Telnet sequence will reappear.	3.6 SP2
CSCsl74628	Cisco 6516 and 6516-A devices are being modelled incorrectly	Cisco 6516 and 6516-A devices are being modelled incorrectly. The interface RJ45 is shown as a port but it's actually a fiber optic port with Gbic.	None	3.6 SP2
CSCsl78328	Double click on map layout button in "NetworkVision" crashes the Vision	When Double clicking on the "map layout" icon in NetworkVision, NetworkVision exits with a stack overflow exception.	None	3.6 SP2
CSCsl94381	6500 traps being identified as generic instead of specific as supported	For 6509 devices two traps arrive as generic traps, namely, the traps: •1.3.6.1.2.1.15.7.2 - bgp-backward-transition-trap_v2 •1.3.6.1.2.1.14.16.2.13 - ospf-max-age-lsa	None	3.6 SP2
CSCsm04903	SPA card events in GSR12000 are not properly correlated	Sometimes, SPA card alarms on GSR devices are not correlated properly, or are not cleared. This issue will occur in specific SW versions (like 12.0(32)SY4) where the Entity MIB is created but the FRU MIB wasn't.	None	3.6 SP2
CSCsm14931	Juniper VNE: FPC and PIC Order	The order of the information presented in Cisco ANA for FPC and PIC is confusing.	None	3.6 SP2
CSCsm14993	Juniper VNE: Descriptions for PEM and PCG Modules are incomplete	Descriptions of Juniper Modules PEM and PGC should be clearer.	None	3.6 SP2
CSCsm15074	Jun VNE: Interface Data descriptions are missing from ANA	VNEs of Juniper Junos devices show no port description. This relates to the description which the user may set on each interface.	None	3.6 SP2
CSCsm16556	ANA 3.6 Command Builder Menu Caption shows "No Description"	The Command Builder menu caption displays "No Description" when there is a proper defined menu description.	Go through the steps of Edit Command (even without editing anything) to save the command again, to get this Menu Caption value back to the Command Builder command table, but later it will return to "No Description".	3.6 SP2
CSCsm16885	Jun VNE: Scrambling, loopback and clocking info not displayed in GUI	Scrambling, loopback and clocking info not displayed in the GUI.	None	3.6 SP2
CSCsm23316	BGP Link Down/Up Alarm description has wrong IP Address	The description in the BGP Link down ticket is confusing. It will appear sometimes as Management IP to Peer IP and sometimes vice versa.	None	3.6 SP2
CSCsm29938	VNE polling status/configuration can't be changed more than once	When trying to change the status or configuration time in a polling instance, the changes are not saved.	When in the Polling Tab, move to "group" instead of "instance", save, and then create a new instance with the new value.	3.6 SP2
CSCsm30001	Can't create static link between cloud and device via the ANA Manage	A static link can't be created between a cloud and a VNE when using the Tree Pane in Cisco ANA Manage. This is due to no physical inventory appearing on the cloud.	A static link between a cloud and a VNE should be created using Cisco ANA NetworkVision via the inventory of the relevant device.The scenario is as follows: 1. Open Cisco ANA NetworkVision. 2. Open the inventory of the relevant device. 3. Right-click on one of the ports. 4. Select "Topology" and afterwards "Mark as A Side". 5. Repeat steps 2-4 for the other device and "Mark as Z Side".	3.6 SP2
CSCsm30720	Cisco sub-Interface with no configuration causes flapping alarm	A flapping alarm appears even though there is no flapping event on the device.	None	3.6 SP2
CSCsm30731	Windows 2000 Client no Help files	Online help does not display properly in Windows 2000.	None, recommend upgrading to Windows XP.	3.6 SP2
CSCsm67035	CRS - BGP neighbor loss syslog does not correlate to BGP Link Down alarm	BGP neighbor loss syslog is not correlated to BGP Link Down alarm and does not appear in the Network Vision, but only in the Event Vision.	If you still want to see the syslogs in NetworkVision, you can change them to be ticketable.	3.6 SP2
CSCsm68937	FlappingEvent on Traps is not working	Flapping is the occurrence of a flood of consecutive event notifications (often severity toggling) related to the same alarm. This can happen when a fault is unstable and causes repeated event notifications, for instance, the use of a cable with a loosely-fitting, rattling connector. This will not work for traps that behave this way.	None	3.6 SP2
CSCsi63614	Cisco 10008: ATM Traffic Profiles not modeled	Under Logical inventory ATM profiles are not displayed. As a result of this the Traffic descriptors are empty in the VC table.	None	3.6 SP1
CSCsi65238	Auto topology may discover wrong Neighbor in QinQ configuration	Topology discovery may connect VLAN ports configured in Dot1Q_Tunnel mode (QinQ configuration) and configured with L2TP (Layer2 Protocol Tunneling) which are not directly connected.	In order to overcome this situation static link may be configured which will override the wrong dynamically discovered link.	3.6 SP1
CSCsj91682	GRE Tunnel down do not correlate to Device Unreachable alarm	Performing the following scenario will result in a correlation issue: Shutting down a device that has GRE tunnel. This generates two alarms: one for Device Unreachable, and the other for GRE tunnel down. Since shutting down the device is the root cause for the GRE tunnel down, the expected result is correlating the GRE tunnel down alarm to the Device Unreachable alarm. This correlation doesn't occur.	None	3.6 SP1
CSCsk36398	CRS-1 VNE - Missing modules software version	CRS-1VNE Cards have no software version value.	None	3.6 SP1
CSCsk36749	CRS-1, SDR owner displays both it's own physical and those of SDR	Cannot differentiate between SDR entities and SDR-Owner entities in the entPhysicalTable MIB.	None	3.6 SP1
CSCsk78234	Backup&Restore crontab operation error	When trying to save the temporary crontab file, getting the following error: crontab: error on previous line; unexpected character found in line. crontab: errors detected in input, no crontab file generated.	Maximize the window of the PICO, so the pasted line won't cut in the middle of it.	3.6 SP1
CSCsc54311	Inconsistent exception on adding VNE to non existing AVMs with large IDs	When creating an AVM, if you enter a very large integer value for the AVM number, the error message received is "parsing issues" and not "AVM number is too large".	Do not enter values larger than 999 for the AVM number.	3.6
CSCsd66486	Enterprise generic trap description has junk characters	EventVision - Junk characters in the description of V1 trap alarm - `Enterprise junk trap' type.	None	3.6
CSCsd70706	MM-ISAM element type shown as ASAM in ANA Manage	MM-ISAM element type shown as unknown.	In NetworkVision, in the inventory window the element type is displayed correctly.	3.6
CSCsd80155	Exception dialog (GUI) when Oracle is shutdown.	A general error is received when opening EventVision.	Make sure the Oracle listener is up and running in the gateway. The gateway itself won't work without Oracle listener.	3.6
CSCse69481	Concurrent Backup and Primary Port alarm is does not appear	An ISDN backup interface became active on a network element but an alarm of type "backup interface is up" was not received. When the primary interface came back up an alarm of type "concurrent backup port and primary port" was not received.	None	3.6
CSCsf28370	SP properties for port table level created automatically for all VNEs	New Soft Property that was added to a specific entity is displayed for all entities of the same type.	Restart the client application.	3.6
CSCsg79619	Unit installation with multiple interfaces	When installing the product as a unit on a machine with multiple network interfaces, the installation checks the IP of the interface which acts as the default route to the gateway.	A new tool had been added "choose_nic.pl", which lets customers choose which IP interface to use, manually.	3.6
CSCsh37883	Uplink GE ports to be connected to relevant bridges	An uplink connection is missing between the GE port to the relevant bridges. May affect flow.	None	3.6
CSCsh57305	Client waits for server response, if server BQL response fails.	Client is stuck waiting forever for the server to respond.	Restart the client.	3.6
CSCsh57909	Part of soft properties data is stored once for multiple instances	Non persistent data for soft property and for TCA alarms is seen in the EventVision.	None. Do not define soft properties and TCA alarms with the same name on different levels.	3.6
CSCsh59223	AS5300 and AS5800 - access list is not displayed.	Access lists are not modeled on access server devices.	None	3.6
CSCsh70734	ERX1440: ARP table is not modeled	No ARP table. Affects flow that uses ARP table.	None	3.6
CSCsh74067	Changing Date/Time causes transport disconnection	Changing the Date/Time on the Unix machine while the product is running causes transport disconnection.	You cannot change the time while the product is up and running. If you need to maintain the date/time, you need to first shut down the entire ANA product.	3.6
CSCsh77858	RunRegTools doesn't allow create port instance with "!slash!"	Try to create a static like info via RegTool.	Use the Registry Editor for this task.	3.6
CSCsh90578	Physical for DSLAM does not differentiate FEM/PEM HLS/HLM	The device shows both PEM and HL-M cards as PEM, which is how they appear on the VNE, making it impossible to differentiate between these card types. Since this is an internal card (with no ports on it), there's no further impact on the ANA system.	None	3.6
CSCsh90610	CRS-1: For some access-lists, the entries are not displayed	CRS-1: For some access-lists, some access-list entries, which contain new parameters are not displayed. Only the entries that are in the old (IOS-like) format will appear. This is for standard and extended access-lists as well.	None	3.6
CSCsh91003	There is more than one scheme in the installation process	During installation, the list of schemes contains schemes that no longer exist.	Ignore schemes other than "product".	3.6
CSCsh91496	Register and unregister for events without notification.	Via the BQL interface, you perform a "register" command for events. The "unregister" for this does not work until you receive the first notification.	Restart the BQL session.	3.6
CSCsh93058	Lucent-Max-TNT- Shelf status shown as "UNKNOWN"	For Lucent MAX-TNT devices the shelf status appears as `unknown' on the VNE. 1. It is not possible to see the status of the shelf on the VNE. 2. A `shelf out' alarm will not appear if the shelf is taken out.	None	3.6
CSCsh93113	Traps do not expedite the physical command	When removing a card in an ASAM device, alarms, such as card-out service alarm, take a long time to display in NetworkVision. This happens because the physical changes trap does not expedite the physical command.	Shorten the configuration interval for the physical command.	3.6
CSCsh94836	System Backup using mc.csh is not working	System Backup using mc.csh is not working.	Command to be used: ./mc.csh localhost 8011 integrity.executeTest backup	3.6
CSCsh99945	AS5300- Card Shown as Generic module	One of the modules appears as generic	Upgrade the IOS to a version with sufficient support in the OLD-CISCO-CHASSIS-MIB	3.6
CSCsi23224	MultiDsl port support - 2360	Missing Profile Name and line spectrum profiles on ABLT-E ports on ASAM XD devices.	None	3.6
CSCsi27384	Cat 3750ME module as simple L2switch	The 3750ME device modules as a regular L2 switch, with no MPLS/VRF and routing protocols. This occurs with all 3750ME VNEs.	None	3.6
CSCsi29367	"Register" for inventory properties command of the VNE returns error	When you try to do only register via BQL on a VNE inventory element, you receive an error.	Do not use "Register" on elements other than events. Instead, use the "Get" command with the "register" flag.	3.6
CSCsi45107	MS Plus: Missing routing table entries	Some of the entries are not displayed on the routing table. Flow will not work properly.	None	3.6
CSCsi50166	Giga Ethernet links are discovered incorrectly	Ethernet topology links were not discovered correctly. The system is configured to run the following topology tests: CDP, MAC, to connect the Ethernet links. The devices were devices from Cisco 7600 and 6500 series.	There are a few workarounds: 1. Configure in the registry that specific Cisco devices with CDP enabled will be connected according to CDP only. 2. Connect the correct links as static links which will override the wrong links which were dynamically discovered.	3.6
CSCsi63472	Cisco 6509-NEB-A: PFC Card shown as unknown	The PFC card in a Cisco 6509 shows as unknown. Cisco 6509-NEB-A VNE is loaded with Product Scheme, version 12.2(18)SXD5.	None	3.6
CSCsi65238	Auto topology discovers wrong Neighbor	Topology discovery may connect VLAN ports configured in Dot1Q_Tunnel mode (QinQ configuration) and configured with L2PT (Layer2 Protocol Tunneling) which are not directly connected.	A static link may be configured which will override the incorrect dynamically discovered link.	3.6
CSCsi65664	ASAM: ARP Entry is missing in ANA 3.6	One ARP entry is missing for ASAM. May affect flow that uses this entry.	None	3.6
CSCsi66890	Cisco 4506: ARP Table displays IfIndex values under Interface column	On Cisco 4506 VNE there is a mismatch in the ARP table. The Interface column contains IfIndex values which may affect the flow.	None	3.6
CSCsi78507	GRE Tunnel - more than 100 traps/syslogs per second are dropped	On devices configured with many GRE tunnels (78 in this specific case) running through a single physical link, the correlation of the GRE Tunnel down alarms to the physical link down does not work in the default registry configuration. This situation occurs when a lot of traps arrive at the Trap Manager at the same time and some of the traps are dropped. This causes the loss of correlation of the GRE tunnels.	Changes to the registry will solve this problem. Note Contact the Cisco Project Manager or Cisco Account Team for further assistance related to this issue.	3.6
CSCsi83539	Missing data in ATM Traffic Descriptor notification	Notification on changed ATM profiles in CBX ATM switches do not contain the ATM profile parameters.	After getting notification on the profiles that were changed, another BQL query must be done to retrieve the new profile parameters.	3.6
CSCsi83569	TIER_4_OID of Notification on profiles in cbx composed of field values	OID of Notification on profiles in CBX are composed of field values. The OID of these notifications contains the values of the fields which causes the following notifications: 1. IRemoveNotification 2. IAddNotification The received BQL result doesn't contain or indicate where the change really is, so it is almost impossible to know what changed, unless the previous device field properties were saved.	There should be a notification on the ATM VC which notes the change of the profile. An additional BQL to get the profile will reveal the new ATM profile parameters.	3.6
CSCsi84030	VNE is up with unknown element type when devices response is slow	The VNE is loaded for the first time with an "unknown" element type.	After a restart of the VNE, the element type changes to the correct one.	3.6
CSCsj04941	Wrong Root cause in case of 2 consecutive unreachable events	Wrong Root cause is being chosen in case of two consecutive unrelated unreachable events on the same device, which have different reasons.	None	3.6
CSCsl19310	OSPF-MIB creates loops in GET-NEXT	IOX VNEs do not show or model some of the OSPF entries in the network.	SMU is available for this bug from the IOX team. SMU has to be installed on top of the XR image for getting all OSPF entries. The following releases have this fix:- 3.5.3, 3.4.3, 3.6.1	3.6
CSCsd12788	Path tool doesn't open when the path should pass through IMA topology	The Cisco ANA PathTracer does not open when the path goes through IMA	None	3.5.1
CSCsd27001	Asam 1000 new alarms Persistency doesn't work	When an alarm occurs in the ASAM VNE and the VNE goes down (for any reason), if the alarm is fixed during the down time, then when the VNE goes up again the alarm is not cleared.	Clear the alarm manually.	3.5.1
CSCsd61127	Able to add a VNE in UP state to an AVM that is down	A VNE is transferred from an Up state to a down state unintentionally.	Pay attention to the move action before moving a VNE.	3.5.1
CSCsd61370	UT-Starcom modeling - missing interface under routing entity.	In the logical inventory of a UT-Starcom device, one or more of the IP interfaces may not be shown.	None	3.5.2
CSCse08188	Stinger: VC admin status is missing.	When viewing the VC properties of the Lucent stinger, the admin status is not shown.	None	3.5.2
CSCse66308	Cannot load VNE against Cisco 10K with 15,000 Ip int.	When loading a Cisco router 10K device with a lot of sessions (~15000) the AVM may crash due to out of memory.	Decrease the polling interval for the encapsulations command and increase the amount of memory available for the AVM	3.5.1
CSCsg46860	For Cisco 7206VXR, ATM Traffic Profiles entries missing in ANA 3.5.1 NW.	ATM profiles are not shown in the logical inventory of Cisco 7206VXR.	None	3.5.2
CSCsg48454	VC Removed is not scale	Not supported in this version.	None	3.5.1
CSCsg48456	Events are dropped when doing high scale alarm manipulation	Events are dropped when doing high scale alarm manipulations.	Avoid performing alarm manipulation actions in high scale. Check Cisco ANA EventVision for reports of the dropped events.	3.5.1
CSCsg84343	Interface description is not displayed in the routing table.	In the logical inventory of Cisco 12012, the interface description is not available in the routing table.	None	3.5.2
CSCsg87329	Stinger - Port type, Last change and MAX speed are not displayed.	Some of the port properties, like type, last changed and max speed are not displayed in Cisco ANA NetworkVision.	None	3.5.2
CSCsh46315	ECI: Values under MCR is not displayed.	The MCR column in the ATM traffic profile is empty.	None	3.5.2
CSCsh47093	ECI: Card serial number not modeled	Card serial number not modeled (iso.3.6.1.4.1.1286.1.3.3.1.1.7) Device serial number is also not modeled	None	3.5.2
CSCsh64220	Cisco 4507- Hardware version is missing in the GUI.	In the physical inventory of the Cisco 4507 device, when choosing a card, the hardware version is missing.	None	3.5.2
CSCsh71005	NTP doesn't work.	NTP is a process that should sync the date and time between the machines in the setup (gateway and units). This bug indicates a problem in this sync mechanism, which can cause sync problems in the system. For example, a problem with the events time stamp can cause event correlation to fail and to DB mess.	After installation, the system time should be set manually in all of the units. The difference between the clocks on all of the units should not be more than 4 minutes. Once this is done NTP will sync the machines precisely.	3.5.2

Resolved Caveats - Cisco ANA, Release 3.6 Service Pack 2

Table 8 Resolved Caveats - Cisco ANA, Release 3.6 Service Pack 2 

Identifier	Summary	Explanation
CSCsc90738	Catalyst 4507 - long time to model due to large VLAN quantity	Fixed
CSCsh72690	RedbackSE800: Redback card manager 6 port state syslog is not ticketed	Fixed
CSCsh72692	RedbackSE800: Link down/up trap severity does not show the correct severity	Fixed
CSCsi50224	Support for Cisco Router 3845	Fixed
CSCsi83608	2348-VC add notification is not sent when executing workflow	Fixed
CSCsi83621	Wrong cross connect notification-2364 2365 2351 2357 23	Fixed
CSCsi95942	POS-OC12 on GSR modeled as PPP when configured HCLD	Fixed
CSCsi95991	Installation phase doesn't succeed the remote database configuration	Fixed
CSCsi96000	Missing notifications on the property IAtm.CrossConnectTable	Fixed
CSCsj14352	Migration: inability to decrease maxvarbindspermessage	Fixed
CSCsj30736	Cisco 6509 - Unsupported Module	Fixed
CSCsj36580	BQL interface is returning - undefined variable	Fixed
CSCsj56055	Port down service alarm due to "admin down" not generated	Fixed
CSCsj62366	IP interface down alarm not cleared if up syslog is missing	Fixed
CSCsj66118	Tickets remain with high severity due to incorrect Auto Clear config	Fixed
CSCsj70386	Tickets cleared after gateway correlation timeout	Fixed
CSCsj71952	Auto Clear delays clearing tickets	Fixed
CSCsj76535	Modeling port speed by ifHighSpeed	Fixed
CSCsj81830	ANA generated 1200 false tickets in one hour	Fixed
CSCsj84193	Non Auto Clear alarm mistakenly auto-cleared by gateway	Fixed
CSCsj89430	IOX: Supporting SNMP and Syslogs with multiple IPs	Fixed
CSCsk36444	CRS-1 VNE, Missing Fan modules status	Fixed
CSCsk36681	CRS-1 VNE, mismatch in module/interface name and real physical location	Fixed
CSCsk36724	CRS-1 VNE, Asics are represented as type "module"	Fixed
CSCsk52374	MPBGP table of Juniper device is not modeled properly	Fixed
CSCsk69084	Failure in loading VNE with SSHv2 for missing password	Fixed
CSCsk77839	Martini tunnels are not discovered between 7300 devices	Fixed
CSCsk78405	Ethernet cloud does not work correctly with duplicate IPs	Fixed
CSCsk78416	Juniper trap does not get parssed	Fixed
CSCsk78547	Cisco7200 - update port state command	Fixed
CSCsk82995	IOX devices CRS-1 GSR-IOX get over utilized CPU & move to maintenance	Fixed
CSCsk84550	Link down due to admin event trying to correlate	Fixed
CSCsk86666	ANA3.6.1:Cisco12K: Gigabit Port speed does not model by ifHighSpeed	Fixed
CSCsk90688	Juniper - over-registrations - Routing Entity	Fixed
CSCsk94580	VNE loaded with "Fast" polling by default	Fixed
CSCsk97716	Integration of Duplicate IPs of Cloud VNE	Fixed
CSCsl00315	CDP topology over vlan interface is not connecting	Fixed
CSCsl02151	The CRS-1 and GSR (IOS\IOS XR) devices should be removed from the product scheme	Fixed
CSCsl08041	Static topology not connecting between E1 ports	Fixed
CSCsl12181	syslog and trap flapping alarms are set to auto clear	Fixed
CSCsl16316	GSR - ENTITY-MIB does not report SPA-8XCHT1/E1 ports	Fixed
CSCsl36424	SPA-24CHT1-CE-ATM module on 7609-S is unsupported	Fixed
CSCsl45416	Black hole alarms in ANA 3.6.1	Fixed
CSCsl50037	"interface status down" is not correlated to "link down" during flapping	Fixed
CSCsl52188	CDP topology: no ip addresses published	Fixed
CSCsl59133	Missing ports due to missing GBICs	Fixed
CSCsl61050	High CPU utilization value for Juniper M-Series devices	Fixed
CSCsl70178	ANA 3.6.1 unsupported line cards on the 7603 and 6506 chassis	Fixed
CSCsl72107	Cisco 7xxx: Missing POS port - overridden by virtual port	Fixed
CSCsl82383	SP1 SIP-601 Removal/Insertion Alarm clearing	Fixed
CSCsl86220	Traps are getting duplicated on a CRS device with multiple management IP	Fixed
CSCsl89883	Add registration to map between TE tunnel ID and its ifindex	Fixed

Documentation Updates

This section of the Release Notes includes updates to the Cisco Active Network Abstraction 3.6 Service Pack 2 documentation set.

•Cisco Active Network Abstraction Fault Management User Guide

•Professional Services Note

Cisco Active Network Abstraction Fault Management User Guide

The updates to this user guide include:

•Flapping

•Supported Service Alarms

Flapping

A sequence of events is identified as flapping if:

•All events share the same event type and are associated to the same source.

•The time interval between consecutive events is less than one minute (default value).

•There are more than five events (default value) with a severity different from "Cleared".

Supported Service Alarms

In Appendix A, Supported Service Alarms the following service alarms are not supported in the Cisco ANA 3.6 Service Pack 2:

•rate above low rate threshold

•rate below high rate threshold

•rate below low rate threshold

•rate exceeds high rate threshold

•agent exceeds memory

•agent memory ok

•mpls te tunnel reoptimized

•mpls te tunnel rerouted

In Appendix A, Supported Service Alarms the registry parameters of the following service alarms have been updated:

•All ip interfaces down—Flapping information parameters were added.

•Cloud problem—Severity changed from "MAJOR" to "INFO".

•Interface status—Flapping information parameters were added.

•Link down—Correlate changed from "true' to "false".

All ip interfaces down

Table 9 Active ip interfaces found 

Type	all ip interfaces down
Subtype	active ip interfaces found
Correlation information	activate-flow=false
	correlate=false
	is-correlation-allowed=false
	weight=0
Northbound metadata	alarm-type=837
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=CLEARED
	gw-correlation-timeout=1200000
	is-ticketable=false
	send-to-gw=true
	short-description=Active ip interfaces found
Flapping information	clear-interval=240000
	flapping-interval=60000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Table 10 All ip interfaces down 

Type	all ip interfaces down
Subtype	all ip interfaces down
Correlation information	activate-flow=false
	correlate=true
	is-correlation-allowed=true
	weight=750
Northbound metadata	alarm-type=837
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=MAJOR
	gw-correlation-timeout=1200000
	is-ticketable=true
	send-to-gw=true
	short-description=All ip interfaces down
Flapping information	clear-interval=240000
	flapping-interval=60000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Cloud problem

Table 11 Cloud problem 

Type	cloud problem
Subtype	cloud problem
Correlation information	activate-flow=false
	correlate=false
	is-correlation-allowed=true
	weight=2000
Northbound metadata	alarm-type=122
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=INFO
	gw-correlation-timeout=1200000
	is-ticketable=true
	send-to-gw=true
	short-description=cloud problem

Interface status

Table 12 Interface status down 

Type	interface status
Subtype	interface status down GRE tunnel
Correlation information	activate-flow=false
	correlate=true
	is-correlation-allowed=true
	weight=825
Northbound metadata	alarm-type=700
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=MAJOR
	gw-correlation-timeout=1200000
	is-ticketable=true
	send-to-gw=true
	short-description=Interface status down
Flapping information	clear-interval=240000
	flapping-interval=60000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Table 13 Interface status down 

Type	interface status
Subtype	interface status down connection
Correlation information	activate-flow=true
	correlate=true
	is-correlation-allowed=true
	weight=500
Northbound metadata	alarm-type=700
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=MAJOR
	gw-correlation-timeout=1200000
	is-ticketable=true
	send-to-gw=true
	short-description=Interface status down
Flapping information	clear-interval=240000
	flapping-interval=60000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Table 14 Interface status down 

Type	interface status
Subtype	interface status down non connection
Correlation information	activate-flow=true
	correlate=true
	is-correlation-allowed=true
	weight=700
Northbound metadata	alarm-type=700
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=MAJOR
	gw-correlation-timeout=1200000
	is-ticketable=true
	send-to-gw=true
	short-description=Interface status down
Flapping information	clear-interval=240000
	flapping-interval=60000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Table 15 Interface status up 

Type	interface status
Subtype	interface status up
Correlation information	activate-flow=false
	correlate=false
	is-correlation-allowed=false
	weight=0
Northbound metadata	alarm-type=700
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=CLEARED
	gw-correlation-timeout=1200000
	is-ticketable=false
	send-to-gw=true
	short-description=Interface status up
Flapping information	clear-interval=240000
	flapping-interval=60000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Link down

Table 16 Link down due to admin down 

Type	link down
Subtype	link down due to admin down
Correlation information	activate-flow=false
	correlate=false
	is-correlation-allowed=true
	weight=850
Northbound metadata	alarm-type=1
	auto-cleared=false
	auto-removed=true
	functionality-type=SERVICE
	severity=CRITICAL
	gw-correlation-timeout=1200000
	is-ticketable=true
	send-to-gw=true
	short-description=Link down due to admin down
Flapping information	clear-interval=360000
	flapping-interval=150000
	flapping-threshold=5
	update-interval=200000
	update-threshold=20

Professional Services Note

The following note appears throughout the documentation for Cisco Active Network Abstraction 3.6 Service Pack 2:

Changes to the registry should be carried out only with the support of Cisco Professional Services.

This note has now been replaced with the following:

Changes to the registry should only be carried out with the support of Cisco. For details, please contact the Cisco Project Manager or Cisco Account Team.

Related Documentation

User Guides

Cisco Active Network Abstraction Documentation Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction NetworkVision User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction EventVision User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction MPLS User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction Fault Management User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6 Service Pack 2

Cisco Active Network Abstraction VNE Reference Guide 3.6 Service Pack 2

Administrator Guides

Cisco Active Network Abstraction Installation Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction Administrator Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction Error Messages, 3.6 Service Pack 2

Cisco Active Network Abstraction Shell User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction High Availability User Guide, 3.6 Service Pack 2

Developer Guides

Cisco Active Network Abstraction Customization User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction Command Builder User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction Workflow User Guide, 3.6 Service Pack 2

Cisco Active Network Abstraction BQL User Guide, 3.6 Service Pack 2

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0805R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 1999-2008 Cisco Systems, Inc. All rights reserved.