Release Notes for Cisco Active Network Abstraction, 3.6

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 device 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 interoperability, 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 FCAPS 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

The following new features were added in Cisco ANA 3.6:

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

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

•SDR support for CRS1—For more information see SDR Support for CRS1.

•Correlation enhancements to CRS-1—Correlation has been enhanced by defining CRS-1 syslogs and expediting service alarms. For more information see the Cisco ANA Fault Management User Guide.

•Carrier Ethernet Support—For more information see Carrier Ethernet Support and for more information about availability see the Enhanced Functionality for VNEs section.

•Switch Virtual Interface (SVI) Support—The functionality available in ANA 3.6 supports the modeling of Cisco SVI. For information about the scenarios supported see Switch Virtual Interface (SVI). For more information about availability see the Enhanced Functionality for VNEs section.

•New Technologies Support—For more information see New Technologies Support. In addition, GRE Modeling is now supported as follows:

–Discovery of GRE tunnels between managed switches

–Topological view of the GRE tunnels on the map

–Logical Inventory information

–GRE tunnel down alarm

For additional information see the Cisco Active Network Abstraction Fault Management User Guide.

•Support for SSHv2—The SSH protocol provides secure sessions using standard cryptographic mechanisms. The SSHv2 communication protocol can now be used by the VNE to investigate the reachability of the device.

•Correlation Engine Enhancements—The following correlation engine enhancements were made:

–Removal of internal correlation dependencies—The event correlation mechanism has been adjusted to allow the correlation of an event before the event's own correlation logic is complete. This change increases the reliability of event correlation, and eliminates the need for complex system fine-tuning.

–Correlation flows based on cached model (overcome network/model re-convergence)—In order for the Cisco ANA topology-based correlation to provide accurate results, the correlation flows must run across modeled data-paths that existed prior to the failure. In Cisco ANA 3.6 the caching mechanism, which maintains snapshots of the model that recently existed in the network (prior to any change), was adjusted to provide more complete support for model caching.

–Correlation in multi route environments—The root cause event is established based on a filtering algorithm for events that are detected across the multipath flow.

For additional information see the Cisco Active Network Abstraction Fault Management User Guide.

•Hardened System Configuration—The following parameters were removed from the system:

–is-correlation-allowed-when-not-correlated

–correlate-to-cloud

–send-uncorrelated

–expiration-time

–drop-event

–flow-delay

–flow-activation-message

–alarm-min-age

–timeout removed from root cause configuration parameters

–enabled removed from flapping event definitions parameters

–due-to-cause

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

•Improved BGP Support:

–BGP Process Down: The BGP process down alarm is issued when the BGP process is shut down on a device. If a BGP process is shutdown on a device, the BGP neighbor down events will correlate to it as well as all the device unreachable alarms from the CE devices that lost connectivity to the VRF due to the BGP process down on the route reflector. The syslogs that the device issues expedite the status check of the BGP process and BGP neighbors.

•Open Tickets 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.

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

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

•Disable Automatic Client Updates—The automatic client update can be disabled. For more information see the Cisco ANA Installation Guide, Version 3.6.

•Drala Work Flow Engine—The Drala workflow engine was upgraded to version 3.6.3.

•Support SNMPv3—The following methods of encryption were added to the SNMP tab of the New VNE dialog box:

–AES-128

–AES-192

–AES-256

In addition, SNMP V3 trap information is displayed in Cisco ANA EventVision.

•Enhanced garbage collector functionality in the gateway in order to increase gateway throughput.

•The "Sheer One language" used in the Command Builder tool enabling the user to create commands has been renamed "ANA Macro Language".

•New service alarms introduced:

–MPLS interface removed—Indicates when the MPLS IP interface has been removed and there is no MPLS TE tunnel on the same interface. For further information see the Cisco Active Network Abstraction Fault Management User Guide, Version 3.6.

–BGP process down—Indicates when the BGP process has been removed or shut down on a device.

–GRE tunnel down—Indicates when the state of an IP interface for a GRE tunnel edge is identified as down.

–Sub card out—Indicates a sub card out.

–Link down on unreachable—Indicates when one of the devices is unreachable.

–Link down flapping—Indicates when a link is down and is in a flapping state.

–Component Unreachable—Indicates that the component is no longer reachable.

–Port down card out—Indicates that the port is down as the entire card is out.

–Port down flapping—Indicates that the port is down and is in a flapping state.

–MPLS Black hole found—Indicates when a BGP (destination) entry in the label switching table becomes untagged. This event is created per outgoing interface and nextHop.

–Interface status down—Indicates when an IP interface changes operating status to down.

–Interface status down connection—Indicates when an IP interface changes operating status to down on a point to point link.

–Interface status down non connection—Indicates when an IP interface changes operating status to down on a multipoint link.

–Interface status down GRE tunnel—Indicates when an IP interface changes operating status to down on a GRE tunnel link.

For more information see the Cisco Active Network Abstraction Fault Management User Guide.

New VNEs Introduced

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

Table 1 Cisco ANA 3.6 VNEs
Vendor	Device Classification	Device Family	Device Type/Product Number	Software Version	Support Type
Alcatel	Switch	7450	7450 ESS1	3.0.R1	Device
Alcatel	Switch	7450	7450 ESS7	3.0.R7	Device
Cisco	Router	12000 Series	12000/16	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	12000/4	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	12000-SIP-601	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	12000-SPA	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	12016/80	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	12404/80	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	12416/320	12.0(33)S, 12.0(32)SY	Device
Cisco	Router	12000 Series	16OC3X/POS-I-LC-B		Card
Cisco	Router	12000 Series	SPA-OC192POS-VSR		Card
Cisco	Router	12000 Series	SPA-OC192POS-XFP		Card
Cisco	Router	12000 Series	PA-MC-8TE1+		Card
Cisco	Router	12000 Series	PRP-2		Card
Cisco	Router	12000 Series	PRP-2/R		Card
Cisco	Router	12000 Series	PWR-7200		Card
Cisco	Router	12000 Series	PWR-7200/2		Card
Cisco	Router	12000 Series	PWR-7200/2-DC+		Card
Cisco	Router	12000 Series	PWR-7200-DC+		Card
Cisco	Router	12000 Series	SFP-GE-S		Card
Cisco	Router	12000 Series	SFP-OC12-SR		Card
Cisco	Router	12000 Series	SFP-OC3-SR		Card
Cisco	Router	12000 Series	SFP-OC48-SR		Card
Cisco	Router	12000 Series	SPA		Card
Cisco	Router	12000 Series	WS-G5484		Card
Cisco	Router	12000 Series	XFP-10GER-OC192IR		Card
Cisco	Router	12000 Series	XFP-10GLR-OC192SR		Card
Cisco	Router	12000 Series, XR-12000 Series	MEM-12KRP-FD256M		Card
Cisco	Router	12000 Series, XR-12000 Series	MEM-ISE-512A-2PK		Card
Cisco	Router	12000 Series, XR-12000 Series	MEM-PRP2-2G		Card
Cisco	Router	4500 Series	4500	11.2(14)P, 11.2(17), 12.1(22a)	Device
Cisco	Switch	4500 Series	WS-C4503	12.2S, 12.1(12c)EW2, 12.1(13)EW1, 12.1(13)EW2, 12.1(19)EW, 12.1(19)EW1, 12.2(18)EW	Card
Cisco	Switch	6500 MetroE	6524GT-8S	12.2(18)ZU_	Card
Cisco	Switch	6500 MetroE	6524GS-8S	12.2(18)ZU_	Device
Cisco	Router	6500 Series	6503	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(17d)SXB9	Device
Cisco	Router	6500 Series	6509	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(17d)SXB9	Device
Cisco	Router	6500 Series	6513	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(17d)SXB9	Device
Cisco	Switch	6500 Series	6506	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(17d)SXB9	Device
Cisco	Router	6500 Series	WS-F6700-DFC3BXL	12.2(17d)SXB9	Card
Cisco	Router	6500 Series	WS-SUP720-3BXL	12.2(17d)SXB9	Card
Cisco	Router	7200 Series	MEM-NPE-G1-1GB		Card
Cisco	Router	7200 Series	MEM-NPE-G1-FLD256		Card
Cisco	Router	7600 Series	2X1GE-V2-SPA		Card
Cisco	Router	7600 Series	4X1FE-TX-V2-SPA		Card
Cisco	Router	7600 Series	4XCT3/DS0-SPA		Card
Cisco	Router	7600 Series	4XOC3-ATM-SPA		Card
Cisco	Router	7600 Series	4XOC3-POS-SPA		Card
Cisco	Router	7600 Series	4XOC48POS/RPR-SPA		Card
Cisco	Router	7600 Series	5X1GE-SPA		Card
Cisco	Router	7600 Series	5X1GE-V2-SPA		Card
Cisco	Router	7600 Series	WS-X6748-GE-TX		Card
Cisco	Router	7600 Series	WS-X6704-10GE		Card
Cisco	Router	7600 Series	7604	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(30)SRA	Card
Cisco	Router	7600 Series	7613	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(30)SRA	Device
Cisco	Router	7600 Series	7606	12.2(18)SXF (Rockies 3), 12.2(18)SXE (Rockies 2), 12.2(18)SXD (Rockies 1), 12.2(30)SRA	Device
Cisco	Router	7600 Series, 6509-NEB-A	WS-SUP720	12.2(18)SXE, 12.2(18)SXF, 12.2(33)SRA, 12.2(33)SRB	Card
Cisco	Router	7600 Series, 6509-NEB-A	WS-SUP720-3BXL	12.2(18)SXE, 12.2(18)SXF, 12.2(33)SRA, 12.2(33)SRB	Card
Cisco	Router	7600 Series, 6509-NEB-A	WS-SUP720-3B	12.2(18)SXE, 12.2(18)SXF, 12.2(33)SRA, 12.2(33)SRB	Card
Cisco	Router	CRS	SPA-10XGE-V2	For the prerequisite see CRS VNE	Card
Cisco	Router	CRS	SPA-1X10GE-V2	For the prerequisite see CRS VNE	Card
Cisco	Router	CRS	SPA-4XOC48POS/RPR	For the prerequisite see CRS VNE	Card
Cisco	Router	CRS	SPA-8X10GE	For the prerequisite see CRS VNE	Card
Cisco	Router	CRS	SPA-8x1GE	For the prerequisite see CRS VNE	Card
Cisco	Router	CRS	SPA-8XOC12-POS	For the prerequisite see CRS VNE	Card
Cisco	Router	CRS	CRS-MSC-40G	For the prerequisite see CRS VNE	Card
Alcatel	DSLAM	ISAM	7330R		Device

The following SPA cards are supported for the Cisco 12000 and 7600 Series Routers:

Table 2 Cisco 12000 and 7600 Series Routers SPA Cards
SPA-4XCT3/DS0	SPA-1X10GE-L-V2	SPA-4XOC3-POS
SPA-10X1GE	SPA-4X1FE-TX-V2	SPA-1XOC12-POS
SPA-1XTENGE-XFP	SPA-8XOC3-POS	SPA-2GE-7304
SPA-5X1GE	SPA-OC48POS-SFP	SPA-OC192POS-XFP
SPA-OC192POS-SMSR	SPA-IPSEC-2G	SPA-OC192POS-LR
SPA-OC192POS-SMIR	SPA-2XOC3-ATM	SPA-2XT3/E3
SPA-8XOC3-OC12-POS	SPA-4XOC3-ATM	SPA-4XT3/E3
SPA-2X1GE	SPA-1XOC12-ATM	SPA-8XCHT1/E1
SPA-1XCHSTM1/OC3	SPA-1XOC48-ATM	SPA-2XCT3/DS0
SPA-2XOC48POS/RPR	SPA-2XOC3-POS

Enhanced Functionality for VNEs

Table 3 Enhanced Functionality for Cisco ANA 3.6 VNEs
Vendor	Device Classification	Device Family	Software Version
Cisco	Router	7600 Series	SVI, QinQ, STP, LAG (partial)
Cisco	Router	6500 Series	SVI, QinQ, STP, LAG (partial)
Cisco	Router	3750 Series	SVI, QinQ, STP, LAG (partial)
Cisco	Router	6524 Series	SVI, QinQ, STP, LAG (partial)

Carrier Ethernet Support

This section includes the following:

• Spanning Tree Protocol "STP"

• QinQ (IEEE802.1ad)

• Switch Virtual Interface (SVI)

• IMOs

Spanning Tree Protocol "STP"

STP is a Layer 2 link management protocol that provides path redundancy while preventing undesirable loops in the network. For a Layer 2 Ethernet network to function properly, only one active path can exist between any two devices.

STP defines a tree with a root bridge and a loop-free path from the root to all network devices in the Layer 2 network. STP forces redundant data paths into a standby (blocked) state. If a network segment in the spanning tree fails and a redundant path exists, the STP algorithm recalculates the spanning tree topology and activates the standby path.

STP modeling in Cisco ANA 3.6 supports devices that use the following STP variants:

•STP as defined in the 802.1D standard

•RSTP as defined in the 802.1w standard

•PvSTP and PvSTP+ which are Cisco proprietary protocols, or any per VLAN spanning tree protocol

•MST as defined in the 802.1s standard

IMOs

For IMO information see IMOs.

Faults and Alarm Correlation

There are no alarms based on STP technology in Cisco ANA 3.6, however correlation takes into account STP technology when performing flow analysis.

Topology

There is no topology based on STP technology in Cisco ANA 3.6.

QinQ (IEEE802.1ad)

QinQ (IEEE802.1) tagging (namely, dot1q tunneling) is a technology that allows the nesting of an additional VLAN tag on a packet, in addition to an existing one. Either VLAN tag is an 802.1Q header by standard.

QinQ allows service providers to use a single VLAN to support customers who have multiple VLANs. The core service-provider network carries traffic with double-tagged, stacked VLAN (802.1Q-in-Q) headers of multiple customers while maintaining the VLAN and Layer 2 protocol configurations of each customer and without impacting the traffic of other customers.

IMOs

For IMO information see IMOs.

Opening Cisco ANA PathTracer Over Networks

You can open and view PathTracer information between service endpoints (for example, the IP interface) over a network. In order to view a specific path you must specify an initial point like an IP interface and a destination IP address. When the user selects an endpoint the system extracts the relevant IP address from this point and uses it as the destination. For QinQ the path is run from any:

•Router or switch which is part of the carrier ethernet domain with Dot1q and QinQ configuration

•IP destination which can be reached from that point of the network

PathTracer Starting Points

The user can also enter the required destination IP address after opening the Cisco ANA PathTracer from the right-click shortcut menu. The table below describes the starting points available in the shortcut menu in order to open the PathTracer:

Table 4 PathTracer Starting Points
Element	Location	Start PathTracer Options
IP Interface	Inventory window	•to IP Destination •Start Here

For information on opening the Cisco ANA PathTracer from the Inventory window as a starting point, see the Cisco Active Network Abstraction NetworkVision User Guide.

PathTracer Endpoints

If you selected the "Start Here" option the following endpoints can be selected as a path destination to open the PathTracer:

Table 5 PathTracer Endpoints
Element	Location	Start PathTracer Options
IP Interface	Inventory window	End Here

The Cisco ANA PathTracer Multi-Path window is displayed. From this window you can open the Cisco ANA PathTracer Single-Path window with the appropriate QinQ information displayed in the Layer 2 tab.

Using Cisco ANA PathTracer to View Path Information

This section describes the Cisco ANA PathTracer for Dot1q and QinQ. For detailed information about the Cisco ANA PathTracer, see the Cisco Active Network Abstraction NetworkVision User Guide.

Cisco ANA uses the VLAN tags of the Ethernet header and the port configuration to trace the path from one interface to another over the network. The Cisco ANA's PathTracer tool enables you to:

•View a Layer 2 path across a LAN domain with all the VLAN tags' information

•For each network element view the relevant parameters for each interface on all layers along the path.

Layer 2 Dot1q and QinQ information is displayed in the Cisco ANA PathTracer windows when a path is traced over Ethernet ports with Dot1q and a QinQ configuration.

Layer 2

The following Layer 2 properties that may be displayed in the Layer 2 tab relate specifically to QinQ and VLAN port configuration:

•VLAN Mode—The work mode for the interface, namely, Unknown, Access, Trunk, Dot1QTunnel.

Note Trunk mode refers to multiple tagging too.

•Native VLAN ID—The VLAN ID that is used to tag untagged traffic received on a trunked interface. The default native VLAN ID is `1' if VLAN tagging is enabled. The native VLAN ID is `0' or `no VLAN ID' if VLAN tagging is disabled.

•CE VLAN ID—The customer edge device's VLAN ID.

•SP VLAN ID—The service provider's VLAN ID.

Layer 3

There are no Layer 3 properties that relate specifically to QinQ.

Faults and Alarm Correlation

There are no alarms based on QinQ technology in Cisco ANA 3.6. however correlation takes into account STP technology when performing flow analysis.

Topology

There is no topology based on QinQ technology in Cisco ANA 3.6.

Note See CSCsi65238 which describes the potential problems in topology discovery in QinQ scenarios.

Switch Virtual Interface (SVI)

SVI is a Cisco term representing the configuration used to attach a VLAN to Ethernet Pseudo Wire, IP interface or MPLS access points. A SVI represents a VLAN (broadcast domain) of switch ports as one interface to a routing or bridging function in the system. SVI provides IP host connectivity to a Layer 3 protocol. Routing can be configured across SVIs. There is a one to one mapping between a VLAN and SVI which means that a single SVI can only be mapped to a single VLAN and a SVI cannot be activated until it is associated with a physical port.

SVIs are created the first time that VLAN interface commands are configured for a VLAN interface. The VLAN corresponds to the VLAN tag associated with data frames on an ISL or 802.1Q encapsulated trunk or the VLAN ID configured for an access port.

The following SVI configuration scenarios are supported in Cisco ANA 3.6:

•Simple SVI (interface VLAN) with IP address

interface Vlan100

 ip address 10.126.1.5 255.255.255.252

end

•SVI (interface VLAN) with IP address and MPLS (tag switching)

interface Vlan100

 ip address 10.126.1.5 255.255.255.252

 mpls label protocol ldp

 tag-switching ip

end

•SVI (interface VLAN) with AToM configuration (xconnect)

interface Vlan400

 no ip address

 xconnect 80.80.80.61 503 encapsulation mpls

end

IMOs

For IMO information see IMOs.

Faults and Alarm Correlation

There are no alarms based on SVI technology in Cisco ANA 3.6.

Topology

There is no topology based on SVI technology in Cisco ANA 3.6.

IMOs

This section describes the inventory and Information Model Objects (IMOs) for Carrier Ethernet. It includes the following tables:

• Link Aggregation Group (ILinkAggregationGroup802dot3ad)

• Ethernet Interface (IEthernet)

• Ethernet Physical (IPhysicalLayer)

• Virtual LAN Interface (IVlanInterface)

• Virtual LAN Entry (IVlanEntry)

• Virtual LAN Multiplexer (IVlanEncapMux)

• Virtual LAN Encapsulation (IIEEE802)

• Data Link Aggregation Container(IDataLinkAggregationContainer)

• Spanning Tree Protocol Service (IStpService)

• Multiple Spanning Tree Protocol Service (IMstService)

• Multiple Spanning Tree Protocol Properties (IMstProperties)

• Spanning Tree Protocol Bridge Information (IStpBridgeInfo)

• Multi Spanning Tree Protocol Bridge Information (IMstBridgeInfo)

• Per Virtual LAN Spanning Tree Protocol Bridge Information (IPvstpBridgeInfo)

• Rapid Spanning Tree Protocol Bridge Information (IRstpBridgeInfo)

• Spanning Tree Protocol Port Information (IStpPortInfo)

• Multi Spanning Tree Protocol Port Information (IMstPortInfo)

• Ethernet Channel (IEthernetChannel)

This section uses the following conventions:

Table 6 Document Conventions
Convention	Description
Blue text	Indicates references to enumeration values
Underlined blue text	Indicates references to defined objects/tables

Note For each object the interface used in the IMO is written in parenthesis.

Link Aggregation Group

The Link Aggregation Group object was added with the following attributes:

Note Currently only partial modeling of the Link Aggregation Group is supported, namely, Group Number, Bandwidth, Aggregation Protocol, IANA Type, Containing Termination Points and Contained Connection Termination Points.

Table 7 Link Aggregation Group (ILinkAggregationGroup802dot3ad)
Attribute Name	Attribute Description
MAC Address	Media Access Control (MAC) address
Actor and Partner System Priorities	Actor and partner system priorities
Actor and Partner System Identifications	Actor and partner system identifications (in the form of MAC addresses)
Actor Administrative Key	Actor administrative key
Actor and Partner Operational Keys	Actor and partner operational keys
Collector Maximum Delay	Maximum delay (microseconds) for either delivering or discarding a received frames by the frame collector
Aggregation Ports Table	Array of Link Aggregation Group Port Entries
Group Number	Group identification of the aggregated ethernet interfaces
Bandwidth	Accumulated bandwidth of all aggregated ethernet interfaces in Mbps
Aggregation Protocol	Aggregation protocol (None, LACP, PAGP)
IANA Type	IANA type of the sub/layer
Containing Termination Points	Underlying termination points (connection or physical)
Contained Connection Termination Points	Bound connection termination points and forwarding component (Bridging Entity)

Ethernet Interface

The Ethernet Interface object was added with the following attributes:

Table 8 Ethernet Interface (IEthernet)
Attribute Name	Attribute Description
MAC Address	Media Access Control (MAC) address
Duplex Mode	Duplex mode (Unknown, Full, Half)
Output Flow Control	Output flow control (Enable, Disable)
Input Flow Control	Input flow control (Enable, Disable)
IANA Type	IANA type of the sub/layer
Containing Termination Points	Underlying termination points (connection or physical)
Contained Connection Termination Points	Bound connection termination points and forwarding component (Bridging Entity)

Ethernet Physical

The Ethernet Physical object was added with the following attributes:

Table 9 Ethernet Physical (IPhysicalLayer)
Attribute Name	Attribute Description
Same as physical layer (IPhysicalLayer)

Virtual LAN Interface

The Virtual LAN Interface object was added with the following attributes:

Table 10 Virtual LAN Interface (IVlanInterface)
Attribute Name	Attribute Description
Mode	Virtual LAN mode (Access, Trunk, 802.1Q Tunnel)
Native Identification	Virtual LAN identification, used for untagged received and transmitted frames
Customer Edge Identification	Virtual LAN identification within the customer private network
Service Provider Identification	Virtual LAN identification used by the service provider to identify the customer private network
Virtual LAN Table	Array of Virtual LAN Entries
IANA Type	IANA type of the sub/layer
Containing Termination Points	Underlying termination points (connection or physical)
Contained Connection Termination Points	Bound connection termination points and forwarding component (Bridging Entity)

Virtual LAN Entry

The Virtual LAN Entry object was added with the following attributes:

Table 11 Virtual LAN Entry (IVlanEntry)
Attribute Name	Attribute Description
Identification	Virtual LAN identification of received and transmitted frames
Encapsulation Type	Virtual LAN encapsulation (Unknown, ISL, IEEE 802.10, IEEE 802.1Q)
Upper Layer	Upper Layer Object Identification (OID)

Virtual LAN Multiplexer

The Virtual LAN Multiplexer object was added with the following attributes:

Table 12 Virtual LAN Multiplexer (IVlanEncapMux)
Attribute Name	Attribute Description
IANA Type	IANA type of the sub/layer
Containing Termination Points	Underlying termination points (Ethernet Interface)
Contained Connection Termination Points	Bound connection termination points (Virtual LAN Encapsulations) and forwarding component (Bridging Entity)

Virtual LAN Encapsulation

The Virtual LAN Encapsulation object was added with the following attributes:

Table 13 Virtual LAN Encapsulation (IIEEE802)
Attribute Name	Attribute Description
VLAN Identification	Virtual LAN identification
Binding Information	Binding information (User Name, ...)
Binding Status	Binding status (Not Bound, Bound)
IANA Type	IANA type of the sub/layer
Containing Termination Points	Underlying termination points (connection or physical)
Contained Connection Termination Points	Bound connection termination points and forwarding component (Bridging Entity)

Data Link Aggregation Container

The Data Link Aggregation Container object was added with the following attributes:

Table 14 Data Link Aggregation Container(IDataLinkAggregationContainer)
Attribute Name	Attribute Description
Traffic Descriptors	Array of a single type data link aggregations (Link Aggregation Group/Ethernet Channel)
Type	Aggregation type (Null, Ethernet Link Aggregator)

Spanning Tree Protocol Service

The Spanning Tree Protocol Service object was added with the following attributes:

Table 15 Spanning Tree Protocol Service (IStpService)
Attribute Name	Attribute Description
Protocol Type	Spanning tree protocol type (Unknown, STP, RSTP, PVSTP, MST)
Current and Bridge	The current value used and the value that all bridges should use when this bridge is acting as the root for maximum age of learned spanning tree protocol port information (in hundredths of seconds)
Current and Bridge Hello Time	The current value used and the value that all bridges should use when this bridge is acting as the root for hello time messages' keep alive interval of a spanning tree protocol root (in hundredths of seconds)
Current and Bridge Forward Delay	The current value used and the value that all bridges should use when this bridge is acting as the root for port delay in each of the listening and learning states, preceding the forwarding one (in hundredths of seconds)
Bridge Information Table	Array of Spanning Tree Protocol Bridge Informations
Same as system service (ISystemService)

Multiple Spanning Tree Protocol Service

The Multiple Spanning Tree Protocol Service object was added with the following attributes:

Table 16 Multiple Spanning Tree Protocol Service (IMstService)
Attribute Name	Attribute Description
Protocol Properties	Multiple Spanning Tree Protocol Properties
Same as spanning tree protocol service (IStpService)

Multiple Spanning Tree Protocol Properties

The Multiple Spanning Tree Protocol Properties object was added with the following attributes:

Table 17 Multiple Spanning Tree Protocol Properties (IMstProperties)
Attribute Name	Attribute Description
Force Version	Force version (Unknown, STP, RSTP, PVSTP, MST)
Configuration Format, Region Name and Revision Level	Configuration format, region name and revision level used by this device and is negotiated with other device
External Root Cost	External root cost of this multi spanning tree protocol
Maximum Instances	Maximum multi spanning tree protocol instances

Spanning Tree Protocol Bridge Information

The Spanning Tree Protocol Bridge Information object was added with the following attributes:

Table 18 Spanning Tree Protocol Bridge Information (IStpBridgeInfo)
Attribute Name	Attribute Description
Object Identification	Bridge Object Identification (Object ID)
Identification	Bridge identification (MAC address)
Priority	Bridge priority in the spanning tree protocol
Designated Parent and Root Bridges	MAC addresses of the designated parent and root bridges in the spanning tree
Root Cost	Root cost value for this bridge
Is Root	Is this bridge currently the root of the spanning tree protocol (True, False)
Root Port Identification	Object Identification (OID) of the bridge's port used to reach the designated root
Port Information Table	Array of Spanning Tree Protocol Port Information

Multi Spanning Tree Protocol Bridge Information

Table 19 Multi Spanning Tree Protocol Bridge Information (IMstBridgeInfo)
Attribute Name	Attribute Description
Instance Identification	Multi spanning tree protocol instance identification
Same as spanning tree protocol bridge information (IStpBridgeInfo)

Per Virtual LAN Spanning Tree Protocol Bridge Information

Table 20 Per Virtual LAN Spanning Tree Protocol Bridge Information (IPvstpBridgeInfo)
Attribute Name	Attribute Description
Protocol Type	Spanning tree protocol type (Unknown, STP, RSTP, PVSTP, MST)
Current and Bridge Maximum Age	The current value used and the value that all bridges should use when this bridge is acting as the root for maximum age of learned spanning tree protocol port information (in hundredths of seconds)
Current and Bridge Hello Time	The current value used and the value that all bridges should used when this bridge is acting as the root for hello time messages' keep alive interval of a spanning tree protocol root (in hundredths of seconds)
Current and Bridge Forward Delay	The current value used and the value that all bridges should used when this bridge is acting as the root for port delay in each of the listening and learning states, preceding the forwarding one (in hundredths of seconds)
Same as spanning tree protocol bridge information (IStpBridgeInfo)

Rapid Spanning Tree Protocol Bridge Information

Table 21 Rapid Spanning Tree Protocol Bridge Information (IRstpBridgeInfo)
Attribute Name	Attribute Description
Force Version	Force version (Unknown, STP, RSTP, PVSTP, MST)
Same as spanning tree protocol bridge information (IStpBridgeInfo)

Spanning Tree Protocol Port Information

The Spanning Tree Protocol Port Information object was added with the following attributes:

Table 22 Spanning Tree Protocol Port Information (IStpPortInfo)
Attribute Name	Attribute Description
Object Identification	Port Object Identification (Object ID)
Priority	Port priority in the spanning tree protocol
State	Port state (Unknown, Disable, Blocking, Listening, Learning, Forwarding, Broken, Down, LoopBack)
Path Cost	Port path cost, which represents the media speed for this port
Is Edge	Is this an edge (connected to a nonbridging device) port (True, False)
Is Point To Point	Is this port connected to a point to point link (True, False)
Role	Port role (Unknown, Disable, Backup, Alternative, Designated, Root, Boundary)

Multi Spanning Tree Protocol Port Information

Table 23 Multi Spanning Tree Protocol Port Information (IMstPortInfo)
Attribute Name	Attribute Description
Hello Time	Hello time messages' keep alive interval of a spanning tree protocol root (in hundredths of seconds)
Same as spanning tree protocol port information (IStpPortInfo)

Vendor Specific

The Ethernet Channel object was added with the following attributes:

Table 24 Ethernet Channel (IEthernetChannel)
Attribute Name	Attribute Description
Group Number	Group identification of the aggregated ethernet interfaces
Bandwidth	Accumulated bandwidth of all aggregated ethernet interfaces in Mbps
Aggregation Protocol	Aggregation protocol (None, LACP, PAGP)
IANA Type	IANA type of the sub/layer
Containing Termination Points	Underlying termination points (connection or physical)
Contained Connection Termination Points	Bound connection termination points and forwarding component (Bridging Entity)

New Technologies Support

This section outlines the changes to the technology IMOs, as detailed in the following tables:

• Inverse Multiplexing for ATM (IMA) Group (IIMAGroup)

• Generic Routing Encapsulation (GRE) Tunnel Interface (ITunnelGRE)

• IP Interface (IIPInterface)

For Carrier Ethernet technology IMO changes see Carrier Ethernet Support.

Inverse Multiplexing for ATM (IMA) Group

The following Inverse Multiplexing for ATM (IMA) Group object, multiplex multiple Digital Signaling 1 Physicals, which it is bound to by its Containing Termination Points attribute, into a single Data Link layer ATM Interface, which it is accessed by.

Table 25 Inverse Multiplexing for ATM (IMA) Group (IIMAGroup)
Attribute Name	Attribute Description
Description	IMA Port Description
Speed	Group Aggregated Speed
Administrative Status	Administrative Status (Unknown, Up, Down, Testing)
Operational Status	Operational Status (Unknown, Up, Down, Testing, Dormant, Not Presented)
Operational Status Last Change	Date of Last Operational Status Change
IANA Type	IANA Type of the Sub/Layer
Containing Termination Points	Underlying Termination Points (Digital Signaling 1 Physicals)

Generic Routing Encapsulation (GRE) Tunnel Interface

The following Network layer Generic Routing Encapsulation (GRE) Tunnel Interface object, which represents a GRE Tunnel Interface configuration in a network element, is primarily being accessed by an IP Interface bound by its Contained Connection Termination Points attribute.

Table 26 Generic Routing Encapsulation (GRE) Tunnel Interface (ITunnelGRE)
Attribute Name	Attribute Description
Name	Tunnel Name
Tunnel Destination and Source	Tunnel Destination and Source IP Addresses
IP Address	Primary IP Address
IP Interface State	IP Interface State (Unknown, Up, Down)
IANA Type	IANA Type of the Sub/Layer
Containing Termination Points	Underlying Termination Points (Connection or Physical)
Contained Connection Termination Points	Bound Connection Termination Points and Forwarding Component (Routing Entity)

IP Interface

The following property was removed from the IP interface:

Table 27 IP Interface (IIPInterface)
Attribute Name	Attribute Description
IP Ports	Array of IP Port Aliases (GUI Usage)

SDR Support for CRS1

Secure Domain Router (SDR) is supported as a separate independent VNE, with its own IP and login sequence. When adding a SDR to Cisco ANA it is treated like any other network element, namely, it is added as a new VNE using Cisco ANA Manage. The SDR IP address is attached to the active DRP of the SDR (or the virtual IP, if it exists).

As a prerequisite for the CRS-1 VNE, install the Cisco IOS XR Manageability Package on top of the IOS-XR version (XR 3.4 and 3.4.1). In addition, the device configuration must contain the command, xml agent tty and when creating the SNMP community the SystemOwner should be specified.

The IP address, snmp read community and telnet login sequence must be defined.

Cisco ANA uses the management network (if available) to manage the devices. The CRS platform assigns specific management interfaces on the RP modules (DRP in the case of SDR). In order to retrieve the IP address of these management interfaces, login to the device and run the command show ipv4 interface brief | include Mgmt as shown in the example:

RP/0/RP1/CPU0:P1_CRS8#show ipv4 interface brief | include Mgmt

MgmtEth0/RP1/CPU0/0            1.60.34.104     Up                    Up

MgmtEth0/4/CPU0/0              unassigned      Shutdown              Down

MgmtEth0/4/CPU1/0              unassigned      Shutdown              Down

In a multiple (D)RP environments there is an option to configure a virtual management interface and assign an IP address to it, so that the device is reachable via the same IP address no matter which (D)RP is active. In such an environment, each (D)RP has its own IP address but it is not used in order to access the device.

In order to get the virtual IP address, login to the device and run the command show running-config ipv4 virtual address as shown in the example:

DRP/0/3/CPU0:CRS-PE1#show running-config ipv4 virtual address

ipv4 virtual address 10.52.123.11 255.255.255.0

If the SDR is managed in-band the management IP address should be supplied by the customer.

The owner SDR (namely, the main router) presents all the modules that are installed on the chassis, excluding the ports that belong to other SDRs.

The VNE of the SDR only displays the modules that are associated with the SDR in the Inventory window of Cisco ANA NetworkVision, it does not display the fabric, fan and power supply (namely, the shared modules).

Changes from the Last Release

This section includes the following:

•IMO Changes from Cisco ANA 3.5.2 to 3.6—For more information see IMO Changes from Cisco ANA 3.5.2 to 3.6.

•API Changes from Cisco ANA 3.5.2 to 3.6—For more information see API Changes from Cisco ANA 3.5.2 to 3.6.

•A different set of patches for Solaris 10 is required for this release—For more information see Solaris 10.

•Changes to the scheme—Addition of ipcore scheme. This is used for routers that serve as Provider (P) or Provider Edge (PE) devices only.

For more information see Cisco Active Network Abstraction Administrator Guide.

•Security enhancements from Cisco ANA 3.5.2 to 3.6—The following security enhancements were made:

–Secured the Cisco ANA graphs—The Cisco ANA graphs (diagnostic FW) are now visible on a secure channel only (https) and require user names or passwords to obtain access. A user name or password is provided during the installation of Cisco ANA. For more information see the Cisco Active Network Abstraction Install Guide.

–Masked Telnet sequences in Cisco ANA Manage—Every password field in the GUI of Cisco ANA Manage is masked with an asterisk. For more information see the Cisco Active Network Abstraction Administrator Guide.

–Secured PTP Transport—The communication between Cisco ANA clients and the gateway (PTP) is now secured (SSL). This is the default behavior of the system.

–Encryption added to registry files—Entries in the registry are now encrypted. When viewing registry xml files only the encrypted form of the entry is visible.

•Changes to the event.xml files during the migration procedure—In earlier versions of Cisco ANA, all events were defined in the events.xml (including site.xml for specific customer needs), which contained references to the alarm-types.xml. The events.xml file is no longer used in Cisco ANA 3.6. The alarm-types.xml now contains new events. Each event must now be defined in three main xml files, namely, eventmanager.xml, event-correlation-app.xml, and send-alarm-msg-util.xml. In addition, events that support persistency also need to be defined in the event-persistency-app.xml, and flapping events need to be defined in the flapping-app.xml. For more information see the Cisco Active Network Abstraction Server Installation Guide.

Note Important: If you are installing Cisco ANA on a machine on which a previous version of the application is installed, you must delete all the files from /tmp which belong to user sheer, before installation. For more information see the Cisco Active Network Abstraction Installation Guide.

IMO Changes from Cisco ANA 3.5.2 to 3.6

The table below lists the IMO changes that occurred between Cisco ANA 3.5.2 and Cisco ANA 3.6. The following columns are displayed in the table:

•IMO Name—Name of the IMO

•Method/Type—Namely one of the following:

–IMO—The entire IMO is new in this version

–Inheritance—The IMO inherits a different IMO from that which it did in the previous release

–Field Name—There is a field modification within the IMO

•Status—The type of change that was made to the element.

•New Signature—The new value of the updated element (completed only if IMO/Method name have changed)

•Old Signature—The old value of the updated element (completed only if IMO/Method name have changed)

Table 28 IMO Changes from Cisco ANA 3.5.2 to 3.6
IMO Name	Method/Type	Status	New Signature	Old Signature
IClientMultiPathInformation	getSimulatedTimestamp	Added
IClientMultiPathInformation	setSimulatedTimestamp	Added
IContext	getDataLinkAggregationContainers	Added
IContext	setDataLinkAggregationContainers	Added
IDataLinkAggregation	IMO	Added
IDataLinkAggregationContainer	IMO	Added
IDataLinkAggregationContainerOid	IMO	Added
IDataLinkAggregationOid	IMO	Added
IElementManagement	Enum S_128	Added
IElementManagement	Enum S_192	Added
IElementManagement	Enum S_256	Added
IElementManagement	Enum S_CIPHER	Added
IElementManagement	Enum S_CLIENT_AUTH	Added
IElementManagement	Enum S_HOST_KEY_ALGO	Added
IElementManagement	Enum S_KEY_EXCHANGE	Added
IElementManagement	Enum S_MAC	Added
IElementManagement	Enum S_SERVER_AUTH	Added
IElementManagement	Enum S_SERVER_AUTH_DATA_TYPE	Added
IElementManagement	Enum S_SNMP_V3ENCRYPTION_TYPE	Changed	S_SNMP_V3ENCRYPTION_TYPE = {"des", "aes128", "aes192", "aes256"}	S_SNMP_V3ENCRYPTION_TYPE = {"des"}
IElementManagemen	Enum S_TELNET_PROTOCOL	Changed	S_TELNET_PROTOCOL = {"Telnet","SSHv1","SSHv2"}	S_TELNET_PROTOCOL = {"Telnet","SSH1"}
IElementManagement	getCipher	Added
IElementManagement	getClientAuthEnum	Added
IElementManagement	getClientPrivateKey	Added
IElementManagement	getClientPublicKey	Added
IElementManagement	getFingerPrint	Added
IElementManagement	getHostKeyAlgo	Added
IElementManagement	getKeyExchange	Added
IElementManagement	getMAC	Added
IElementManagement	getServerAuthDataTypeEnum	Added
IElementManagement	getServerAuthEnum	Added
IElementManagement	getServerPublicKey	Added
IElementManagement	setCipher	Added
IElementManagement	setClientAuthEnum	Added
IElementManagement	setClientPrivateKey	Added
IElementManagement	setClientPublicKey	Added
IElementManagement	setFingerPrint	Added
IElementManagement	setHostKeyAlgo	Added
IElementManagement	setKeyExchange	Added
IElementManagement	setMAC	Added
IElementManagement	setServerAuthDataTypeEnum	Added
IElementManagement	setServerAuthEnum	Added
IElementManagement	setServerPublicKey	Added
IEthernetChannel	Inheritance	Different	IDataLinkAggregation	IDataLinkLayer
IIMAGroup	getPortType	Added
IIMAGroup	getSpeed	Added
IIMAGroup	getStatusChangedTime	Added
IIMAGroup	setPortType	Added
IIMAGroup	setSpeed	Added
IIMAGroup	setStatusChangedTime	Added
IIPInterface	getIpPort	Removed
IIPInterface	setIpPort	Removed
ILogicalRoot	getDataLinkAggregationContainers	Added
ILogicalRoot	setDataLinkAggregationContainers	Added
IMstInstanceInfo	IMO	Added
IMstPortInfo	IMO	Added
IMstProperties	IMO	Added
IMstPropertiesOid	IMO	Added
IMstService	IMO	Added
IPvstpInstanceInfo	IMO	Added
IRstpInstanceInfo	IMO	Added
IServiceEventOid	IMO	Added
IStpInstanceInfo	IMO	Added
IStpInstanceInfoOid	IMO	Added
IStpPortInfo	IMO	Added
IStpPortInfoOid	IMO	Added
IStpService	IMO	Added
IStpServiceOid	IMO	Added
ISystemEvent	Enum S_CAPACITY	Added
ISystemEvent	Enum S_TYPE	Changed	S_TYPE = {"Alarm Threshold", "Bad Oid", "Reachability", "BOS Misconfiguration","Affected Droped","Session Ping Timeout","Bad Severity Data","Bad Alarm", "High Availability","Partitioning Error" , "No stacktrace abailable exception in session","Error in the backup process","Tickets overflow","Tickets back to normal"}	S_TYPE = {"Alarm Threshold", "Bad Oid", "Reachability", "BOS Misconfiguration","Affected Droped","Session Ping Timeout","Bad Severity Data","Bad Alarm", "High Availability","Partitioning Error" , "No stacktrace abailable exception in session","Error in the backup process"}
ISystemServiceOid	setSystemServiceType	Signature Change	(int systemServiceType)	(String systemServiceType)
ITunnelContainerOid	Enum S_TUNNEL_TYPE	Changed	S_TUNNEL_TYPE ={"Unknown",//Unknown tunnel type "Pseudo Wire Tunnels (Martini)",//PWE3 (Martini) tunnels "Traffic Engineering Tunnels",//MPLS-TE tunnels "L2TP", // L2tp tunnels "GRE Tunnels" //GRE tunnels}	S_TUNNEL_TYPE ={"Unknown",//Unknown tunnel type "Pseudo Wire Tunnels (Martini)",//PWE3 (Martini) tunnels "Traffic Engineering Tunnels",//MPLS-TE tunnels "L2TP" // L2tp tunnels}
ITunnelGre	Inheritance	Different	ITunnelEdge	INetworkLayer
ITunnelGreOid	Inheritance	Different	ITunnelEdgeOid	INetworkLayerOid
IVlanEntry	IMO	Added
IVlanEntryOid	IMO	Added
IVlanInterface	IMO	Added
IVlanInterfaceOid	IMO	Added

API Changes from Cisco ANA 3.5.2 to 3.6

There were no changes to the gateway API commands between Cisco ANA 3.5.2 and Cisco ANA 3.6.

Installation Notes

Refer to the Cisco Active Network Abstraction Installation Guide, 3.6.

Solaris 10

The recommended operating system to run Cisco ANA 3.6 on SUN servers is Solaris 10. Cisco ANA 3.6 is compatible with the latest patch release as published by Sun on April 13, 2007. This patch release contains the following patches:

Table 29 Sun Patch Release (13/04/07)
119254-06	SunOS 5.10: Install and Patch Utilities Patch
120719-02	SunOS 5.10 : SunFreeware gzip patch
121296-01	SunOS 5.10: fgrep Patch
118815-05	SunOS 5.10: awk nawk patch
118872-04	SunOS 5.10: ksh patch
120900-04	SunOS 5.10: libzonecfg Patch
121133-02	SunOS 5.10: zones library and zones utility patch
119254-36	SunOS 5.10: Install and Patch Utilities Patch
119757-04	SunOS 5.10: Samba patch
119042-10	SunOS 5.10: svccfg & svcprop patch
121901-01	SunOS 5.10: i.manifest r.manifest class action script patch
120543-09	SunOS 5.10: Apache 2 Patch
119317-01	SunOS 5.10: SVr4 Packaging Commands (usr) Patch
118918-24	SunOS 5.10: Solaris Crypto Framework patch 119578-30
118833-36	SunOS 5.10: kernel patch
120085-01	SunOS 5.10: in.ftpd patch
119593-01	SunOS 5.10: net-svc patch
120292-01	SunOS 5.10 : mysql patch
119574-02	SunOS 5.10: su patch
120329-02	SunOS 5.10: rexec patch
121229-01	SunOS 5.10: libssl patch
120849-04	SunOS 5.10: Sun PCI-E Gigabit Ethernet Adapter Patch
124188-02	SunOS 5.10: Trusted Solaris Attributes Patch
121012-02	SunOS 5.10: traceroute patch
121308-08	SunOS 5.10: Solaris Management Console Patch
118959-03	SunOS 5.10: patch usr/bin/lastcomm and usr/bin/acctcom
124997-01	SunOS 5.10: /usr/bin/tip patch
119903-02	OpenWindows 3.7.3: Xview Patch
121004-03	SunOS 5.10: sh patch
119764-05	SunOS 5.10 : ipmitool patch
120061-02	SunOS 5.10: glm patch
118560-02	SunOS 5.10: usr/bin/telnet patch
122911-02	SunOS 5.10: Apache 1.3 Patch
121002-03	SunOS 5.10: pax patch
123256-02	SunOS 5.10: eri patch
124457-01	X11 6.6.2: xdm patch
121265-03	SunOS 5.10: libc_psr_hwcap1.so.1 patch
123186-02	SunOS 5.10: NIS yp utilities patch
124244-01	SunOS 5.10: /usr/bin/rm patch
118731-01	SunOS 5.10: /usr/sbin/zonecfg patch
122032-04	SunOS 5.10: Update timezones patch
119059-21	X11 6.6.2: Xsun patch
120824-08	SunOS 5.10: usr/platform/SUNW,Sun-Fire-T200/lib/libprtdiag_psr.so.1 Patch
120068-03	SunOS 5.10: in.telnetd patch
119685-10	SunOS 5.10: svc.startd patch
119812-02	X11 6.6.2: Freetype patch
123590-03	SunOS 5.10: PostgresSQL patch
118371-09	SunOS 5.10: elfsign patch
123839-07	SunOS 5.10: Fault Manager Patch
120222-16	SunOS 5.10: Emulex-Sun LightPulse Fibre Channel Adapter driver
118562-12	SunOS 5.10: Solaris Data Encryption Kit Patch
118712-14	SunOS 5.10: Sun XVR-100 Graphics Accelerator Patch
120469-07	SunOS 5.10: kerberos patch
122172-06	SunOS 5.10: swap swapadd isaexec patch
122174-03	SunOS 5.10: dumpadm patch
119081-25	SunOS 5.10: CD-ROM Install Boot Image Patch
120272-06	SunOS 5.10: SMA patch
122640-05	SunOS 5.10: zfs genesis patch
119130-33	SunOS 5.10: Sun Fibre Channel Device Drivers
120050-05	SunOS 5.10: usermod patch
124999-01	SunOS 5.10: mc-us3 driver patch
124918-02	SunOS 5.10: devfsadm, devlinks, drvconfig patch
125011-01	SunOS 5.10: sendmail patch
120473-05	SunOS 5.10: libc nss ldap PAM zfs patch
124922-03	SunOS 5.10: ld.so.1 patch
124258-02	SunOS 5.10: ufs and nfs driver patch
125042-02	SunOS 5.10: picl patch
125100-05	SunOS 5.10: Kernel Update patch
121453-02	SunOS 5.10: Sun Update Connection Client Foundation
119986-03	SunOS 5.10: clri patch
124630-03	SunOS 5.10: System Administration Applications, Network and Core Libraries Patch
121118-11	SunOS 5.10: Sun Update Connection System Client 1.0.9
122660-08	SunOS 5.10: zones patch

Note For any later patches distributed by Sun, contact Cisco Professional Services.

Limitations and Restrictions

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, contact Cisco Professional Services.

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, refer to the Cisco ANA Fault Management Guide, 3.6. 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 Professional Services.

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.

HSRP

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

IOX-Based Platforms

The following service alarms are not supported for the Cisco Carrier Routing System (CRS-1) and Cisco XR 12000 Series routers:

•Memory Over-Utilization

•Rx/Tx Over Utilized

•Concurrent Backup and Primary Port

•Backup Warning

•HSRP group status changed

•MPLS interface removed/MPLS interface added

•Layer 2 Tunnel Down

•MPLS TE Tunnel Down/Flapping

•Dropped Packets

•Discard Packets

•BGP process down/BGP process up

Important Notes

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 30 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 31 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, the SystemOwner should be specified.

Online Help

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

•Microsoft Internet Explorer version 6

•Firefox version 2.0

•Avant Browser version 11 build 25

Open Caveats - Release Cisco ANA 3.6

Table 32 Open Caveats - Release Cisco ANA 3.6
Identifier	Title	Impact	Workaround
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.
CSCsc90738	Catalyst 4507 - long time to model due to large VLAN quantity	It takes a couple of hours to investigate the device.	None. Wait for the VNE to finish
CSCsd27001	ASAM 100 new alarms persistencies don't work	When an ASAM VNE has open alarms and the VNE is restarted, the alarms do not clear.	Remove the alarms manually after VNE restart.
CSCsd27342	Unable to delete multiple templates/ workflows in Workflow Engine	Deleting multiple workflow instances or templates in the ANA Manage, deletes only the workflow/template.	Delete the workflow instances one by one.
CSCsd66486	Enterprise generic trap description has junk characters	EventVision - Junk characters in the description of V1 trap alarm - `Enterprise junk trap' type.	None
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
CSCsd72544	VPN Overlay Time Out	Running VPN Overlay on VPN with many VRFs results in a timeout message.	Increase the timeout on the gateway for that command, to more than 2 minutes. Note Contact Cisco Professional Services for further assistance related to this issue.
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.
CSCse44166	FR-5-DLCICHANGE syslog not parsed correctly with T1 channelized interface	When the VNE receives a FR-5-DLCICHANGE syslog, the event may appear as a generic syslog in EventVision.	Add a dedicated parsing rule using Registry Editor.
CSCse63323	LDP neighbor loss not correlated to link down due to card out	LDP neighbor loss does not correlate to link down, due to card out.	None
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
CSCsf02136	Allocated AVM memory calculation is wrong	AVM memory usage calculation is not correctly calculated in ANA Manage.	Admin needs to account for memory required for OS as well as AVM (50 MB). Admin also needs to account for any other application's memory requirements that may be running on the ANA Unit.
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.
CSCsg45646	Cisco AS5300 12.0(3)T1 isn't moduled properly with redunno scheme	Not all modules may display in AS5300 VNEs.	None
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.
CSCsg87547	No Affected Parties for BGP Neighbor loss when router ID is different	BGP Neighbor Loss alarm does not produce affected parties, if the BGP router ID is different to the IP address used by other BGP peers as the neighboring IP.	Configure the neighboring IP address with the BGP router ID.
CSCsh28508	The "any" option feature in the search dialogue does not work.	In Cisco ANA Manage in the `Find' dialog, the `any' type doesn't work when the ANA Servers branch is selected	None. Need to search each unit separately
CSCsh28511	Issue with screen refresh, alarm vision and search	When the alarm table is updated the text in the `Find' field is deleted and loses the focus	None
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
CSCsh57305	Client waits for server response, if server BQL response fails.	Client is stuck waiting forever for the server to respond.	Restart the client.
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
CSCsh59223	AS5300 and AS5800 - access list is not displayed.	Access lists are not modeled on access server devices.	None
CSCsh70734	ERX1440: ARP table is not modelled	No ARP table. Affects flow that uses ARP table.	None
CSCsh72690	RedbackSE800: Redback card manager 6 port state syslog is not ticketed.	The following two syslogs for the Redback (Card manager port state Syslog) are not shown in the Ticket pane, but the syslog is generated and shown in the EventVision syslog tab->table. •CARDMGR-6-PORT_STATE-SHUTDOWN,DOWN (port down) =>Major •CARDMGR-6-PORT_STATE-NO SHUTDOWN, UP (port up) =>Cleared In addition, the severity of both these syslogs is shown as "Informational", which is not the correct severity.	None
CSCsh72692	RedbackSE800: Link down/up trap severity does not show the correct severity	On RedbackSE800 when there is a trap for Link down/up, the severity is incorrect. The following link down/link up traps do not show the correct severity: •Link Up Snmp V1 Generic Trap (3) => Cleared •Link Down - Snmp V1 Generic Trap (2) => Major The severity of both these traps is shown as "Informational". They should display the appropriate severity.	None
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.
CSCsh76148	Hi-Focus SAM480: TANI E1 module is not supported	Hi-Focus SAM480: TANI E1 module is not supported.	None
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.
CSCsh84022	Link does not disappear from NetworkVision after CDP verification	Link doesn't disappear from the Cisco ANA NetworkVision maps after CDP verification	None
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
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
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".
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.
CSCsh93058	Shelf status shown as "UNKNOWN"	The shelf status appears as 'unknown' on the VNE. 1. It is impossible 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
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.
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
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
CSCsi23224	MultiDsl port support - 2360	Missing Profile Name and line spectrum profiles on ABLT-E ports on ASAM XD devices.	None
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
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.
CSCsi33700	MPLS IP coupled with MPLS TE tunnel doesn't contain all the data	When an MPLS interface configuration which is configured with IP and traffic-engineering capabilities is changed, there is no proper alarm on the MPLS interface. Other service alarms, such as a Black-Hole alarm, which occur due to the change, cannot correlate to the alarm.	None
CSCsi45107	MS Plus: Missing routing table entries	Some of the entries are not displayed on the routing table. Flow will not work properly.	None
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.
CSCsi53032	Soft Properties TCA does not work, till restart the VNE	After defining TCA alarms, there are not seen in the Event Vision	Restart VNE or AVM
CSCsi53289	No cleanup event for "Link down on unreachable" in the reload	`Link down on unreachable' alarm isn't cleared	None
CSCsi53458	BGP neighbor Loss service alarm does not contain real affected parties	When viewing the BGP neighbor Loss service alarm, the "Affected" tab doesn't display real affected parties.	None
CSCsi55025	Unsupported format for "show mpls forwarding-table detail" table.	MPLS entries are missing. The command "show mpls forwarding-table detail" returns these entries in the following format: 40 Aggregate vrf:LOTTE2001 0 MAC/Encaps=0/0, MRU=0, Tag Stack{} VPN route: LOTTE2001 No output feature configured Flows that use these specific labels will not pass.	None
CSCsi58373	Catalyst 3750ME: Two GigabitEthernet ports are wrongly shown as trunks.	On Catalyst 3750ME devices, GigabitEthernet ports configured as switchport may be displayed as trunks in the vlanInterface mode field.	None
CSCsi62213	Cisco 6506: Fan Tray module is unsupported.	Unsupported module. An unsupported module alarm will appear on the VNE, but since this is a fan module that doesn't contain any ports, there is no other impact (on flow, etc.).	None
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
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.
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
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
CSCsi73433	Cat3750 and Cat3750ME: ARP table Interface shows wrong information	On Cat3750 and Cat3750ME devices, the ARP table Interface column shows incorrect information, which may affect the flow.	None
CSCsi76887	Cisco-2801:Module discovered as generic	One of the cards in the 2800 device family appears as generic. This happens with cards of type PVDMI DP SIMM with one DSP on 2800 devices.	None
CSCsi78280	Card down on GSR - not getting link down alarm	Shutting down a GSR module that has a link on it - receive card down alarm in the vision, without any link down alarm.	None
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 Cisco Professional Services for further assistance related to this issue.
CSCsi78647	Link down on SDR - bad correlation	In a scenario where there is a link down between 2 CRS devices, the Interface Status Down and BGP Neighbor Loss service alarms do not correlate to the link down ticket, viewed in NetworkVision.	None
CSCsi80363	Session: Command Builder, editing script with 'combo' arg	When creating an activation script with one of its arguments of type "combo", subsequent editing changes the "combo" type to "string".	When editing the script, make sure to re-edit the argument type back to "combo".
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.
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.
CSCsi83608	2348-VC add notification is not sent when executing WF	After configurating VC on ISAM port, the VC add notification is not received. The problem occurred when running the Activation GUI. When executing the same workflow by BQL, the problem did not reproduce. The workflow purpose is to delete and create a service for the same ADSL client.	None
CSCsi83886	Port Up/down alarm persistency doesn't work	Port Up/Down alarm is not persisted in VNE alarm persistency. This means that in a scenario when a device port state is changed during the time it's VNE (Virtual Network Element) is unloaded the system may reach an inconsistent state from an alarm perspective, namely, it shows alarms which do not exist anymore. When a Port Down alarm is issued by the VNE which manages the specific device, it should keep information that such alarm issued in the VNE alarm persistency. If the VNE is unloaded and the port state changed during this time, the VNE should clear the Port Down alarm when it is reloaded. This is done using the alarm persistency.	Use the "Clear And Remove" functionality from the Client GUI to manually remove the alarm that exists in the system.
CSCsi83980	Wrong default gateway on Redback SMS 1800	The RedBack VNE shows a wrong default gateway in the routing table. This may affect the flow on the device.	None
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.
CSCsi84181	TIER_4_call 2335 - Port under processor NPE300 + call 2340 - Slot 0 dupl	When two cards are placed in the same slot, one in the front and one in the back, NetworkVision displays the same card twice.	None
CSCsi89516	GRE Tunnel - GRE tunnel doesn't correlate every time to link down	GRE Tunnel Down alarms do not correlate to the Link Down which caused them to be in the Down state.	None
CSCsi94499	Change route port to switch port is not updated in model	When changing the configuration of ports in the catalyst device between route-port and switch-port a VNE which is working with the new VlanInterface model is not updated.	Reload the VNE and it will be updated correctly
CSCsi95942	POS-OC12 on GSR moduled as PPP when configured HCLD	The port is HDLC encapsulated, but on the VNE the port appears as ppp.	None
CSCsi95944	Device Reachable/ Unreachable Persistency doesn't work	Device Reachable/Unreachable alarm is not persisted in VNE alarm persistency. This means that in a scenario when the device reachability state changes during the time it's VNE (Virtual Network Element) is unloaded, the system may reach an inconsistent state from an alarm perspective, meaning that it shows alarms which do not exist anymore. When Device Unreachable alarm is issued by the VNE which manages the specific device, it should keep the information that such alarm was issued in the VNE alarm persistency. In case the VNE is unloaded and the device reachability state changed during this time, the VNE should clear the Device Unreachable alarm when it is reloaded. This is done using the alarm persistency.	Use the "Clear And Remove" functionality from the Client GUI to manually remove the alarm that exists in the system.
CSCsi9600	Missing notifications on the property IAtm.CrossConnectTable	IMO notification is identified by the component OID. The OID is a hierarchical structure which is built based on the relationship between internal components inside the VNE (for example modules and ports). In the case where the model is temporarily not completely structured, the notification cannot be created and therefore will not be sent.	None.
CSCsj04678	Card In/Out persistency doesn't work	Card Out/In alarm is not persisted in the VNE alarm persistency. This means that in a scenario when a Card is removed from a device when the VNE (Virtual Network Element) is loaded and inserted back into the device during the time it's VNE is unloaded, the system may reach an inconsistent state from an alarm perspective, meaning that it shows alarms which do not exist anymore. When the Card Out alarm is issued by the VNE which manages the specific device, it should keep information that such alarm was issued. In case the VNE is unloaded and the Card was inserted back into the device during this time, the VNE should clear the Card Out alarm when it is reloaded. This is done using the alarm persistency.	Use the "Clear And Remove" functionality from the Client GUI to manually remove the alarm that exists in the system.
CSCsj05197	Installation failure on Solaris 8	Installation fails on permissions check with error "* ERROR: Failed to open a directory [directory]. ABORTING. * for example: * ERROR: Failed to open a directory /export/home/sheer4/utils/apache/php/lib/php/doc/Archive_Tar/docs. ABORTING. *	Run installation with -override_permissions flag: #perl install.pl -encaped -override_permissions Note Contact Cisco Professional Services for further assistance related to this issue.
CSCsj05685	High volume of flapping events	Low performance as a result of high volume of flapping events. Flapping events, such that are caused by a back-and-forth movement/failure in a device, results in a multiple failures and successors for the same root cause (ticket). In cases where there is a steady noise from such an event, the ticket stored in the DB become too fat to contain the hierarchy of successors and failures correlated to it.	In order to overcome this, please apply a rule for splitting the ticket length every 200 events using the Drools mechanism. Note Contact Cisco Professional Services for further assistance related to this issue.
CSCsj07730	VLAN information is not modeled for trunk ports on catalyst	In the Catalyst device the trunk VLAN information is not modeled. You can't see the trunk port in the interface table for any of the bridges. Also any path that passes through the trunk port will fail. The problem is related to catalyst devices that use the default Catalyst product scheme, the 3400 Catalyst scheme and 4900 Catalyst scheme.	For details of the workaround see the Cisco Active Network Abstraction Installation Guide.
CSCsw09406	Link connect/disconnect between CE and PE which are directly connected	When two devices are configured one as a CE and the other as a PE in an MPLS network, and are connected directly (no switches between them), the link in the VNEs will connect and disconnect periodically. This is reflected by the link blinking on and off in the GUI.	Create a static link between the PE and CE.
CSCsw13047	Service Path, wrong device side is displayed when selecting a link	Service Path - Wrong device side is displayed when selecting A/Z side command on a link	Selecting the link displays the two relevant columns in the table
CSCsw13418	Can't sort by Managed Element in the Device List	In NetworkVision, the user cannot sort the 'Device List' table by the Managed Element column.	Use the `Find' text field

Resolved Caveats - Cisco ANA, Release 3.5.2

Table 33 Resolved Caveats - Cisco ANA, Release 3.5.2
Identifier	Summary	Explanation
CSCsd85803	The traps RTT operation timeout, RTT operation threshold violation, bgpBackwardTransition, bgpEstablished will arrive as generic traps in Cisco ANA EventVision.	Fixed.
CSCsg44987	BQL queries for the Cisco device does not show CPU usage history and FlashDeviceSize.	Fixed.
CSCsg50208	The cross connect table is not shown after the card is removed.	Fixed.
CSCsh51454	When creating a soft property there is a possibility to override the system property by giving the soft property the same name as the system property.The registration will not be overridden, just the property name, which will cause the property to change values whenever one of the registrations (system or soft) pools.	Fixed.
CSCsh69252	When moving a large number of VNEs (150 were tested) from one AVM to another in a different unit, all of the VNEs lost their connection to their hierarchy nodes (the icons of the VNEs appear in Cisco ANA NetworkVision as blue boxes). Once this happens, these devices cannot be managed by the system.	Fixed.
CSCsh96756	Missing entries in IP interface multi-point table prevent flows from running and stopping properly in the VNE model.	Fixed.
CSCsi03708	The scripts Parser.pm and Cisco.pm located under the ./Main/scripts/monitoring/RPC/XML may not work properly.	Fixed
CSCsh74067	When the date is changed in a unit, all of the AVMs in the unit become unreachable (including the unit itself).	Closed
CSCsh85650	Dense Wavelength Division Multiplexing (DWDM) optical technology is not supported, therefore no information relating to these interfaces is shown.	Junked

Open Caveats - Cisco ANA, Release 3.5.2

Table 34 Open Caveats - Cisco ANA, Release 3.5.2
Identifier	Title	Impact	Workaround
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.
CSCse08188	Stinger: VC admin status is missing.	When viewing the VC properties of the Lucent stinger, the admin status is not shown.	None.
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.
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.
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.
CSCsh42902	Verification topology doesn't work on Lucent trunk	Even though the link is removed from the devices (they are no longer connected in the network) the link is still displayed Cisco ANA NetworkVision.	Stop one of the VNEs and restart it.
CSCsh46315	ECI: Values under MCR is not displayed.	The MCR column in the ATM traffic profile is empty.	None.
CSCsh47093	ECI: Card serial number not modelled	Card serial number not modelled (iso.3.6.1.4.1.1286.1.3.3.1.1.7) Device serial number is also not modelled	None.
CSCsh53017	AVM properties are missing when an AVM down.	If an AVM is down it does not show the devices in the right pane allocated to the AVM. It stays in "Please wait ..." mode and does not timeout. After the AVM goes into the "Please wait ..." state, you cannot see the content in the right pane for any other AVM or unit. It freezes. If you do not touch the down AVM, the other AVMs in any Unit are available for navigation.	Restart the client.
CSCsh54780	Alcatel Mini RAM-480:DS1 port Clocking shown as unknown.	In the physical inventory of the Alcatel miniram device, when choosing a port, the port clocking property is undefined.	None.
CSCsh57305	Client waits for server response if a server BQL response fails.	The Client does not time out when waiting for BQL response.	Restart the client.
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.
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.
CSCsh82831	BA40: "Customer ID" is missing on ADSL ports.	In the physical inventory of the BA 40 device, when choosing a port, the customer ID is not shown.	None.

Resolved Caveats - Cisco ANA, Release 3.5.1

Table 35 Resolved Caveats - Cisco ANA, Release 3.5.1
Identifier	Summary	Explanation
CSCsd34847	Missing link between the ASAM <-> CBX	Fixed.
CSCsg26227	Deadlock in Workflow Editor	Fixed.
CSCse82338	For some network elements there is no physical inventory. This may occur with network elements that do not respond well to SNMP or Telnet requests.	Fixed.

Open Caveats - Cisco ANA, Release 3.5.1

Table 36 Open Caveats - Cisco ANA, Release 3.5.1
Identifier	Title	Impact	Workaround
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.
CSCsd27001	Asam 1000 new alarms Persistency don'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.
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.
CSCsd84445	Overlay does not work with aggregations - aggregations color issue	Overlay result, which contains devices that are nested in aggregations, doesn't show accurate result.	Run Overlay on a flat map
CSCsd84449	Overlay and link properties- missing selection sensitive menu	Build a map with aggregation of a device. run overlay that is relevant to that device. show aggregation as thumbnail, and right click over the links from that device, that are relevant to the overlay. And there is no context sensitive menu (no popup)	None.
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
CSCsf02136	Allocated memory calculation is wrong	Over allocation of the memory can be made to the unit causing the unit to work slower than intended.	When calculating the memory add 50MB for each AVM that is created (including AVM0, AVM66 and AVM99). The operating system memory is not accounted for (included) either.
CSCsg48454	VC Removed is not scale	Not supported in this version.	None.
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.

Resolved Caveats - Cisco ANA, Release 3.5.

Table 37 Resolved Caveats - Cisco ANA, Release 3.5
Identifier	Summary	Explanation
CSCsw12670	When running the BQL command for creating static link between cloud VNE and a VNE, the command reports failure even if it succeeded.	Fixed.
CSCsd63693	IMA is not supported.	Fixed.

Open Caveats - Release Cisco ANA 3.5

Table 38 Open Caveats - Release Cisco ANA 3.5
Identifier	Title	Impact	Workaround
CSCsw09406	Link connect/disconnect between CE and PE which are directly connected.	When two devices are configured one as CE and one as a PE in a MPLS network and are connected directly (no switches between them), the link in the VNES will connect and disconnect periodically. The reflection of this problem is the link blinking on and off in the GUI.	Create a static link between the PE and CE.

Documentation Updates

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

Cisco Active Network Abstraction Installation Guide

It is important to note the following:

If you are installing Cisco ANA on a machine on which a previous version of the application is installed, you must delete all the files from /tmp which belongs to the user sheer, before installation.

To locate the list of files, run the following commands:

cd /tmp

ls -l | grep sheer

Then, to delete each file in the list, run this command:

rm <file_name>

Cisco Active Network Abstraction Administrator Guide

Cisco ANA Schemes

Cisco ANA 3.6 supports two schemes:

•Product—The default scheme which includes all device types supported in this release.

•ipcore—This scheme is used only for routers serving as Provider (P) or Provider Edge (PE) devices.

Two schemes now provide users with more flexibility to specify which registrations the VNEs modeling their routers will use. A registration is how the VNE queries a live device for information. In previous releases, all router VNEs used to poll IP/VPN related commands for PEs. With Cisco ANA 3.6, you can designate a VNE as a core router by setting it to work with the ipcore scheme, or an edge router by setting it to work with the product scheme.

Note The ipcore scheme applies only to routers. All VNEs are supported with the product scheme.

Product Scheme

The Product scheme should be used for routers that are not configured to serve as PE and P. The product scheme includes all device families.

Since the routing entry to the management may be discovered via BGP, one registration has been added in Cisco ANA 3.6 that will support discovering just that one entry (mc-ip-bgp under the RoutingEntity DC).

The following commands available in previous releases are not used by the Cisco ANA 3.6 product scheme:

•gre tunnel

•lse

•martini

•mpbgp

•mpls interfaces

•mpls te tunnels headend creator

•tunnel container

•vrf interfaces

•label switching table

•ldp local ip

•mpls te tunnels in lse

•mpls distribution protocol

•mpls te interface attribute

•mpls te interface properties

•mpls traffic engineering tunnel information

•bgp neighbours

•bgp-process-state

•local bgp as

•local bgp identifier

•VRF RoutingTable

•VrfRoutingTarget

ipcore Scheme

The ipcore scheme is used when the user wants the VNE to poll for additional data that is typical for PE or P routers, for example VRF, BGP. The ipcore scheme is applicable for the following device types:

•All Cisco router devices of families greater then or equal to 3600.

•All Juniper routers.

In addition to usual registrations in the product scheme, this scheme also includes the following registrations according to DCs and device queries using registrations:

•GenericForwardingInvestigator

–gre tunnel

–lse

–martini

–mpbgp

–mpls interfaces

–mpls te tunnels headend creator

–tunnel container

•GenericVrfInvestigator

–vrf interfaces

•LSE

–label switching table

–ldp local ip

–mpls te tunnels in lse

•Mpls

–mpls distribution protocol

–mpls te interface attribute

–mpls te interface properties

•MplsTETunnel

–mpls traffic engineering tunnel information

•PTPLayer2MplsTunnel

–Details

•MPBgp

–bgp neighbours

–bgp-process-state

–local bgp as

–local bgp identifier

•Vrf

–RoutingTable

–VrfRoutingTarget

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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

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

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.

Table Of Contents