Table Of Contents
Release Notes for
Cisco Active Network Abstraction, 3.6
Service Pack 1
Contents
Introduction
New Features in Cisco ANA 3.6 Service Pack 1
New VNEs Introduced
Enhanced Functionality for VNEs
Service Alarms Added
Shelf Out
Rx Dormant
Tx Dormant
Link Over Utilized
Changes from the Last Release
IMO Changes from Cisco ANA 3.6 to 3.6 Service Pack 1
Installation Notes
Before Installing Cisco ANA 3.6 Service Pack 1
Solaris 10
Possible Solaris Library Errors
Limitations and Restrictions
Cisco ANA NetworkVision
Cisco ANA Fault Management
Cisco ANA High Availability
Cisco ANA Workflow Editor
OSPF
HSRP
ATM Topology Discovery
Fast Polling Group
Adaptive Polling
Important Notes
Solaris Services and Components
CRS VNE
Daylight Savings Time Tool for Cisco ANA
Configuring Database Storage (Redo Logs)
Online Help
Open Caveats - Release Cisco ANA 3.6 Service Pack 1
Resolved Caveats - Cisco ANA, Release 3.6 and Service Pack 1
Open Caveats - Release Cisco ANA 3.6
Resolved Caveats - Cisco ANA, Release 3.5.2
Open Caveats - Cisco ANA, Release 3.5.2
Open Caveats - Cisco ANA, Release 3.5.1
Documentation Updates
Cisco Active Network Abstraction Installation Guide
Service Pack Installation
Cisco Active Network Abstraction Virtual Network Element Reference Guide
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 1
December 23, 2009
These release notes support the release of Cisco Active Network Abstraction, 3.6 Service Pack 1.
Note 
See Cisco.com for the most up-to-date version of the Release Notes for Cisco Active Network Abstraction, 3.6 Service Pack 1.
Contents
This document includes the following topics:
•Introduction
•New Features in Cisco ANA 3.6 Service Pack 1
•Changes from the Last Release
•Installation Notes
•Limitations and Restrictions
•Important Notes
•Open Caveats - Release Cisco ANA 3.6 Service Pack 1
•Resolved Caveats - Cisco ANA, Release 3.6 and Service Pack 1
•Open Caveats - Release Cisco ANA 3.6
•Resolved Caveats - Cisco ANA, Release 3.5.2
•Open Caveats - Cisco ANA, Release 3.5.2
•Open Caveats - Cisco ANA, Release 3.5.1
•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 1(Cisco ANA 3.6 Service Pack 1).
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 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 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 1
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.
•Enhanced functionality for the CRS-1 VNE—The new functionality added to the CRS-1 VNE includes PWE3 modeling, MPLS-TE modeling, multi-chassis support and new MPLS related traps.
•New Technologies Support—LDP modeling is now supported as follows:
–Logical Inventory information—The table of LDP neighbors is attached to the LSE.
–LDP Neighbor Down alarm—Indicates when there is a failure in the TCP connection on which LDP is running, or if the interface is no longer running MPLS. For more information see the Cisco Active Network Abstraction MPLS User Guide.
–The changes to the technology IMOs, include:
- Label Distribution Protocol Service (ILdpService)
- Label Distribution Protocol Peer (ILdpPeer)
- LDP Peer Discovery Source (ILdpPeerDiscoverySource)
For additional information see the Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6 Service Pack 1.
•Remote Database—The system supports the installation and operation of a distributed system database. This means that the database and the Cisco ANA Gateway can run on separate servers. For more information see the Cisco Active Network Abstraction Installation Guide.
•Oracle 10g—The system supports Oracle 10g Enterprise Edition Release 10.2.0.3 64 bit as a database. This option is available for new installations of Cisco ANA 3.6 and not as an upgrade from Cisco ANA 3.6.
•New service alarms introduced:
•Shelf out—Indicates that a shelf (or subtended card) was removed from the network element.
–Rx/Tx dormant—Indicates that traffic over a particular port has dropped below a predefined threshold, providing a method for identifying customer services that have slowed significantly or stopped altogether.
–Link over utilization—Used for correlating port over utilization alarms on the ports at both ends of a link into a single alarm.
See Service Alarms Added.
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 Service Pack 1 VNEs
Vendor
|
Device Classification
|
Device Family
|
Device Type/Product No.
|
Cisco
|
Router
|
1700 series
|
1700
|
Cisco
|
Router
|
1700 series
|
1701
|
Cisco
|
Router
|
1700 series
|
1710
|
Cisco
|
Router
|
1700 series
|
1711
|
Cisco
|
Router
|
1700 series
|
1720
|
Cisco
|
Router
|
1700 series
|
1721
|
Cisco
|
Router
|
1700 series
|
1750
|
Cisco
|
Router
|
1700 series
|
1760
|
Cisco
|
Router
|
2800 series
|
2801
|
Cisco
|
Router
|
2800 series
|
2811
|
Cisco
|
Router
|
2800 series
|
2851
|
Cisco
|
Router
|
2800 series
|
2801 ADSL/K9
|
Cisco
|
MetroE Switch
|
3400ME
|
3400ME_g12CsA
|
Cisco
|
MetroE Switch
|
3400ME
|
3400ME_g12CsD
|
Cisco
|
MetroE Switch
|
3400ME
|
3400ME_g2csA
|
Cisco
|
Router
|
3560 series
|
3560 24PS
|
Cisco
|
Router
|
3560 series
|
3560 48PS
|
Cisco
|
Router
|
3560 series
|
3560G 24PS
|
Cisco
|
Router
|
3560 series
|
3560G 24TS
|
Cisco
|
Router
|
3560 series
|
3560G 48PS
|
Cisco
|
Router
|
3560 series
|
3560G 48TS
|
Cisco
|
Router
|
3560 series
|
3560 24TS
|
Cisco
|
Router
|
4900 series
|
4948
|
Cisco
|
Router
|
4900 series
|
4948-E
|
Cisco
|
Router
|
4900 series
|
4948-S
|
Cisco
|
Router
|
4900 series
|
4948-10GE
|
Cisco
|
Router
|
4900 series
|
4948-10GE-E
|
Cisco
|
Router
|
4900 series
|
4948-10GE-S
|
Cisco
|
MetroE Switch
|
4900ME
|
4924ME_10GE
|
Cisco
|
Router
|
7600 series
|
7603-S
|
Cisco
|
Router
|
7600 series
|
7604-S
|
Cisco
|
Router
|
7600 series
|
7606-S
|
Cisco
|
Router
|
7600 series
|
7609-S
|
Cisco
|
Router
|
800 series
|
837
|
Cisco
|
Router
|
800 series
|
877W
|
Juniper
|
Router
|
M series
|
10i
|
Juniper
|
Router
|
M series
|
320
|
Juniper
|
Router
|
M series
|
40e
|
For details of the type of support provided for each VNE see the Cisco Active Network Abstraction VNE Reference Guide 3.6 Service Pack 1.
Enhanced Functionality for VNEs
Table 2 Enhanced Functionality for Cisco ANA 3.6 Service Pack 1 VNEs
Vendor
|
Device Classification
|
Device Family
|
Functionality
|
Cisco
|
MetroE Switch
|
3400ME
|
QinQ
|
Cisco
|
Switch
|
3550
|
QinQ
|
Cisco
|
MetroE Switch
|
4900ME
|
QinQ
|
Cisco
|
Router
|
CRS-1
|
Martini Tunnel, MPLS-TE, Traps - 14 MPLS traps
|
Cisco
|
Router
|
GSR-IOX
|
Martini Tunnel, MPLS-TE, Traps - 14 MPLS traps, multi-chassis
|
Cisco
|
Router
|
IOS
|
LDP support for all IOS Cisco routers
|
Juniper
|
Router
|
M series
|
Events expediting
|
For details regarding scheme support see the Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6 Service Pack 1.
Service Alarms Added
Table 3 provides a summary of the service alarms that have been added in Cisco ANA 3.6 SP1.
Table 3 Service Alarms Added in Cisco ANA 3.6 SP1
Alarm
|
Description
|
Clearing Alarm
|
Shelf Out
|
A shelf was removed from a network element.
|
Shelf In
|
Rx Dormant
|
The traffic received by the port (measured as a percentage) dropped below the configured threshold.
|
Rx Dormant Normal
|
Tx Dormant
|
The traffic transmitted by the port (measured as a percentage) dropped below the configured threshold.
|
Tx Dormant Normal
|
Link Over Utilized
|
The traffic on the link (measured as a percentage) exceeded the configured threshold.
|
Link Utilization Normal
|
Table 4 lists the values of the basic parameters for each of the service alarms that were added in Cisco ANA 3.6 SP1.
Table 4 Service Alarm Parameters
Name
|
is-correlation-allowed
|
correlate
|
is-ticketable
|
severity
|
weight
|
Shelf Out
|
true
|
false
|
true
|
MAJOR
|
-1 (maximum)
|
Rx Dormant
|
false
|
false
|
true
|
MINOR
|
-2 (minimum)
|
Tx Dormant
|
false
|
false
|
true
|
MINOR
|
-2 (minimum)
|
Link Over Utilized
|
true
|
true
|
true
|
MINOR
|
-2 (minimum)
|
For more information about event and alarm configuration parameters, see the Cisco Active Network Abstraction Fault Management Guide.
Shelf Out
A Shelf out alarm is issued when a shelf is removed from a network element. This alarm applies only to network elements that support removable or subtended shelves, such as the ECI HiFocus and the Alcatel ASAM. The Shelf in alarm is issued after the problem has been fixed.
Rx Dormant
An Rx Dormant alarm is issued when the traffic received over a physical port (measured as a percentage of the port's capacity) drops below a predefined threshold. The alarm description includes the current traffic percentage compared with the defined threshold. This alarm provides service providers with a method for identifying customer services that have slowed down significantly or stopped altogether. An Rx Dormant Normal alarm is issued after the traffic percentage exceeds a predefined upper threshold.
By default, the Rx Dormant alarm is disabled. This alarm is enabled and its thresholds are configured using the Cisco ANA Registry Editor.
Note Changes to the registry should be performed only with the support of Cisco, for details please contact the Cisco Project Manager or Cisco Account Team.
Tx Dormant
A Tx Dormant alarm is issued when the traffic transmitted over a physical port (measured as a percentage of the port's capacity) drops below a predefined threshold. The alarm description includes the current traffic percentage compared with the defined threshold. This alarm provides service providers with a method for identifying customer services that have slowed down significantly or stopped altogether. A Tx Dormant Normal alarm is issued after the traffic percentage exceeds a predefined upper threshold.
By default, the Tx Dormant alarm is disabled. This alarm is enabled and its thresholds are configured using the Cisco ANA Registry Editor.
Note Changes to the registry should be performed only with the support of Cisco, for details please contact the Cisco Project Manager or Cisco Account Team.
Link Over Utilized
A link over utilized alarm is issued when the traffic transmitted over a port that is connected to another port via a network link (measured as a percentage of the port's capacity) exceeds a predefined threshold. The port over utilization alarm is correlated into a link over utilized alarm. If the ports at both ends of a link are overutilized, the two port over utilization alarms are correlated into a single link over utilization alarm. The alarm description includes the direction of the overutilization. A link utilization normal alarm is issued when the utilization level falls below a predefined threshold.
The overutilization thresholds are configured using the Cisco ANA Registry Editor.
Note Changes to the registry should be performed only with the support of Cisco, for details please contact the Cisco Project Manager or Cisco Account Team.
Changes from the Last Release
This section includes the following:
•IMO Changes from Cisco ANA 3.6 to 3.6 Service Pack 1—For more information see IMO Changes from Cisco ANA 3.6 to 3.6 Service Pack 1.
•Backup and Restore—The backup and restore procedures have been updated. For more information see the Cisco Active Network Abstraction Administrator Guide.
•System Recovery—The time that it takes to the Cisco ANA Gateway to detect that a Cisco ANA Unit has failed has been reduced to six minutes.
•Events History Size—Any customer already running Cisco ANA 3.6 should note that the default value in the registry that sets the size of the events history in the database has changed to two weeks. To extend this period the customer must enlarge the available disk space. For more information see the Cisco Active Network Abstraction Installation Guide.
•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. See also Configuring Database Storage (Redo Logs).
IMO Changes from Cisco ANA 3.6 to 3.6 Service Pack 1
The table below lists the major IMO changes that occurred between Cisco ANA 3.6 and Cisco ANA 3.6 Service Pack 1. 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.
•Old Signature—The old value of the updated element (completed only if IMO/Method name have changed)
•New Signature—The new value of the updated element (completed only if IMO/Method name have changed)
The major changes to the IMO for this release relate to the addition of the following objects:
Table 5 IMO Changes from Cisco ANA 3.6 to 3.6 Service Pack 1
IMO Name
|
Method/Type
|
Status
|
Old Signature
|
New Signature
|
IStpPortInfoOid
|
setStpPort
|
Signature Change
|
(IOid oid)
|
(String port)
|
IMstProperties
|
getMstMaxMstInstances
|
Property name change
|
|
getMstMaxInstances
|
IMstProperties
|
setMstMaxMstInstances
|
Property name change
|
|
setMstMaxInstances
|
ILdpPeer
|
IMO
|
Added
|
|
|
ILdpPeerDiscoverySource
|
IMO
|
Added
|
|
|
ILdpService
|
IMO
|
Added
|
|
|
ILse
|
getLdpService
|
Added
|
|
|
ILse
|
setLdpService
|
Added
|
|
|
ILdpPeerDiscoverySourceOid
|
IMO
|
Added
|
|
|
ILdpPeerOid
|
IMO
|
Added
|
|
|
ILdpServiceOid
|
IMO
|
Added
|
|
|
ISlotOid
|
setFront
|
Added
|
|
|
ISlotOid
|
isFront
|
Added
|
|
|
IAdslTrafficDescriptor
|
setXdslLineServiceProfileIndex
|
Added
|
|
|
IAdslTrafficDescriptor
|
getXdslLineServiceProfileIndex
|
Added
|
|
|
IDataLinkAggregation
|
getMacAddress
|
Added
|
|
|
IDataLinkAggregation
|
setMacAddress
|
Added
|
|
|
IDataLinkAggregation
|
getPortIps
|
Added
|
|
|
IDataLinkAggregation
|
setPortIps
|
Added
|
|
|
IEthernet
|
getAggregationGroup
|
Added
|
|
|
IEthernet
|
setAggregationGroup
|
Added
|
|
|
IEciHifocusAdslTrafficDescriptor
|
getTrafficProfileName
|
Added
|
|
|
For detailed information about the changes made to the IMO in this release see the Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6 Service Pack 1.
Installation Notes
For the installation see the Cisco Active Network Abstraction Installation Guide, 3.6 Service Pack 1.
Note The Service Pack Installation procedure in the Cisco Active Network Abstraction Installation Guide, 3.6 Service Pack 1 has been updated to include a new step. For information about the changes see Documentation Updates.
This service pack is installed as a patch on top of an existing installation of Cisco ANA 3.6 and allows automated installation with the minimum of manual operations.
Note If other patches have been installed on top of Cisco ANA 3.6 please contact Professional Services before installing Cisco ANA 3.6 SP1.
With regard to backward compatibility of the Cisco ANA 3.6 service pack 1 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 1 to ensure that the integration is not affected. In addition, review the IMO Changes from Cisco ANA 3.6 to 3.6 Service Pack 1 section.
•All system configuration changes made to the registry are maintained.
•Consult the Enhanced Functionality for Cisco ANA 3.6 Service Pack 1 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. Contact Cisco Professional Services to perform the necessary calculations.
Before Installing Cisco ANA 3.6 Service Pack 1
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 1.
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. For more information see the Cisco Active Network Abstraction Installation Guide 3.6 Service Pack 1.
Solaris 10
The recommended operating system to run Cisco ANA 3.6 Service Pack 1 on SUN servers is Solaris 10. Cisco ANA 3.6 Service Pack 1 is compatible with the latest patch release as published by Sun on April 13, 2007. This patch release contains the following patches:
Table 6 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.
Possible Solaris Library Errors
Because several Solaris library files are packaged with Cisco ANA 3.6.7, you may see error messages if your version of Solaris includes commands that rely on updated versions of these libraries. This has been observed when Cisco ANA is installed on Solaris 10 with a kernel level later than Generic_120011-14. (You can check your operating system's current kernel level with the Solaris uname -v command.)
This is the type of error message you will see in this scenario:
ld.so.1: id: fatal: libelf.so.1: version `SUNW_1.6' not found (required by file
/lib/libproc.so.1)
ld.so.1: id: fatal: libelf.so.1: open failed: No such file or directory Killed
The workaround is to overwrite the Cisco ANA version of the library file (which is listed in the error message) with the newer version that is packaged with your version of Solaris:
cp new-solaris-library ANAHOME/old-solaris-library
In the following example:
•The outdated library is libelf.so.1
•The updated library is located in /usr/lib/libelf.so.1
•The Cisco ANA installation directory is /export/home/sheer4
•The Cisco ANA subdirectory that contains the outdated library file is /local/lib/sparc/5.10
This is the command you would run to overwrite the old library with the new library:
# cp /usr/lib/libelf.so.1 /export/home/sheer4/local/lib/sparc/5.10/
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, see the Cisco ANA Fault Management Guide, 3.6 Service Pack 1. The operator should ensure that tickets are closed on time.
Note Changes to the registry should be performed only 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.
Fast Polling Group
The appearance of the fast polling group in Cisco ANA Manage is a bug. This group should not be used, and will be removed in the next release.
Adaptive Polling
Adaptive polling is supported for Cisco devices only.
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 7 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 8 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.
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. See also Changes from the Last Release.
Online Help
The online help for Cisco ANA 3.6 Service Pack 1 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 Service Pack 1
Table 9 Open Caveats - Release Cisco ANA 3.6 Service Pack 1
Identifier
|
Title
|
Impact
|
Workaround
|
CSCse01350
|
Wrong encapsulation
|
Wrong encapsulation is displayed in NetworkVision. The link is not displayed.
|
None.
|
CSCsi50166
|
Gigaethernet 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 few workarounds for this:
1. Configure in the registry that the specific Cisco devices with CDP enabled will be connected just according to CDP.
2. Connect the correct links as static links which will override the wrong links which was dynamically discovered.
|
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.
|
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.
|
CSCsi83621
|
Wrong Cross Connect notification-2364 2365 2351 2357 23
|
Wrong Cross Connect notification-2364 2365 2351 2357 2366. This takes place when a Cross Connect change occurs between a Virtual Connection and a Cross Connection command handler polling events. Thus, in case of new VC's populating the modified/new Cross Connection. Cross Connection notification fails since there is no identification of contained virtual connections.
|
None.
|
CSCsi95991
|
Installation phase doesn't succeed the remote DB configuration
|
Install of Cisco ANA fails when trying to use a database on a remote server.
|
1. Run install.pl and extract the product.
2. From the Cisco ANA SP extract the jar patch_other.jar.
3. From patch_other.jar extract the file:
nm_cmp-sp-pkg/pkg_env/ana3x/root/
local/scripts/attach_db.pl
into [ANA user directory]/local/scripts (usually /export/home/sheer4/local/scripts).
4. Continue by running sheer-conf.pl.
|
CSCsj14352
|
Migration: inability to decrease maxvarbindspermessage
|
Some of the device's tables appear as empty in Cisco ANA Vision.
|
If increasing the `maxvarbindpermessage' parameter is impossible:
Divide SNMP commands that sample wide tables using a CompoundCommand. For example, if `maxvarbindpermessage' is 10, and we are sampling a table with 14 columns, use 2 sub-commands, each command will sample 7 columns at a time.
|
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.
|
CSCsk36398
|
CRS-1 VNE - Missing modules software version
|
CRS-1VNE Cards have no software version value.
|
None.
|
CSCsk36619
|
CRS-1 Missing Inventory of Mgmt ports on RP, DRP
|
CRS-1 Missing Inventory of Mgmt ports on RP, DRP. Incorrect correlation on management interfaces. For example no device unreachable correlation.
|
None.
|
CSCsk36681
|
CRS-1 VNE, Mismatch in module/interface name and real physical location
|
CRS-1 VNE, mismatch in module/interface name and real physical location.
|
Was already implemented but this results in the first module (the CPU) to be located hard coded on the bogus slot 10.
|
CSCsk36704
|
CRS-1VNE, Missing Status and other ports properties
|
CRS-1VNE, missing Status and other ports properties.
|
None.
|
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.
|
CSCsk77839
|
Martini tunnels are not discovered between 7300 devices
|
This bug is characterized by the fact Martini tunnel links between Cisco IOS and any other device are not discovered.
|
None.
|
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.
|
CSCsk78405
|
Ethernet cloud does not work correctly with duplicate IPs
|
Ethernet Cloud does not support duplicate IPs in the sense that the modeling of the forwarding information and the encapsulation of the ports in cloud is not correct.
This will cause failure in flows and correlation over the cloud.
|
The partial workaround to address this situation is to connect the device to multiple cloud VNEs where there will not be overlapping IPs in the devices connected to one cloud.
This is not possible in the case on top of one port in the PE where there are multiple sub-interfaces connected to different VRFs which has the same IPs.
|
CSCsk78547
|
Cisco7200 - update port state command
|
Link down alarm is not shown.
|
None.
|
CSCsl02151
|
The CRS-1 and GSR (IOS\IOS XR) devices should be removed from the product scheme
|
If the CRS-1 or GSR (IOS\IOS XR) devices are loaded using the products scheme the VNE will display incorrect modeling of the actual device.
|
If loaded using the product scheme, then unload the VNE, remove it and add it again using the ipcore scheme.
|
Resolved Caveats - Cisco ANA, Release 3.6 and Service Pack 1
Table 10 Resolved Caveats - Cisco ANA, Release 3.6 and 3.6 Service Pack 1
Identifier
|
Summary
|
Explanation
|
CSCsw13418
|
In NetworkVision, the user cannot sort the `Device List' table by the Managed Element column.
|
Fixed.
|
CSCsw13047
|
Service Path - Wrong device side is displayed when selecting A/Z side command on a link.
|
Fixed.
|
CSCsw09406
|
Link connect/disconnect between CE and PE which are directly connected.
|
Fixed.
|
CSCsk36724
|
CRS-1 VNE, Asics are represented as type `module'
|
Fixed.
|
CSCsk36444
|
CRS-1 VNE, Missing Fan modules status
|
Fixed.
|
CSCsj97066
|
TIER_4_traps and syslogs from ICMP devices are not handled.
|
Fixed.
|
CSCsj87949
|
Correlation problem due to alarms with identical,
|
Fixed.
|
CSCsj62027
|
Modeling large MPLS forwarding table delays event identification
|
Fixed.
|
CSCsj61920
|
High CPU and memory consumption modeling PEs with large VRF tables.
|
Fixed.
|
CSCsj51097
|
Snmp V3 communication can go out of sync.
|
Fixed.
|
CSCsj05685
|
High volume of flapping events.
|
Fixed.
|
CSCsj05197
|
Installation failure on Solaris 8.
|
Fixed.
|
CSCsj04678
|
Card In/Out persistency doesn't work.
|
Fixed.
|
CSCsj01854
|
Syslogs and Traps are getting parsed but are not seen through Event Vision.
|
Fixed.
|
CSCsi95944
|
Device Reachable/Unreachable Persistency doesn't work.
|
Fixed.
|
CSCsi94499
|
Change routeport to switchport is not updated in model.
|
Fixed.
|
CSCsi89617
|
Delay in execution of expedited commands.
|
Fixed.
|
CSCsi89516
|
GRE Tunnel Down alarms do not correlate to the Link Down which caused them to be in the Down state.
|
Fixed.
|
CSCsi83980
|
The RedBack VNE shows a wrong default gateway in the routing table. This may affect the flow on the device.
|
Fixed.
|
CSCsi83886
|
Port Up/down alarm persistency doesn't work.
|
Fixed.
|
CSCsi80363
|
When creating an activation script with one of its arguments of type "combo", subsequent editing changes the "combo" type to "string".
|
Fixed.
|
CSCsi78647
|
Link down on SDR - bad correlation.
|
Fixed.
|
CSCsi78280
|
Shutting down a GSR module that has a link on it - receive card down alarm in the vision, without any link down alarm.
|
Fixed.
|
CSCsi76887
|
Cisco-2801:Module discovered as Generic.
|
Fixed.
|
CSCsi73433
|
Cat 3750 & Cat 3750ME ARP table Interface show wrong info.
|
Fixed.
|
CSCsi70559
|
Adding complete Get on scalar change notification.
|
Fixed.
|
CSCsi62213
|
Cisco 6506: Fan Tray module is unsupported.
|
Fixed.
|
CSCsi58373
|
On Catalyst 3750ME devices, Gigabit Ethernet ports configured as switchport may be displayed as trunks in the vlanInterface mode field.
|
Fixed.
|
CSCsi55025
|
Unsupported format for "show mpls forwarding-table detail" table.
|
Fixed.
|
CSCsi53458
|
When viewing the BGP neighbor Loss service alarm, the "Affected" tab doesn't display real affected parties.
|
Fixed.
|
CSCsi53289
|
`Link down on unreachable' alarm isn't cleared.
|
Fixed.
|
CSCsi53032
|
After defining TCA alarms, there are not seen in the Event Vision.
|
Fixed.
|
CSCsh84022
|
Link doesn't disappear from the Cisco ANA NetworkVision maps after CDP verification.
|
This is an enhancement, not part of the product.
|
CSCsh76148
|
Hi-Focus SAM480: TANI E1 module is not supported.
|
Fixed.
|
CSCsh57901
|
Some of the data related to soft properties is stored in the wrong location.
|
Fixed.
|
CSCsh57697
|
Deleting a soft property, some of the information that needs to be deleted is not deleted.
|
Fixed.
|
CSCsh54780
|
In the physical inventory of the Alcatel miniram device, when choosing a port, the port clocking property is undefined.
|
Fixed.
|
CSCsh28508
|
In Cisco ANA Manage in the `Find' dialog, the `any' type doesn't work when the ANA Servers branch is selected
|
Fixed.
|
CSCsh21857
|
The Vision shows wrong value for the Max Speed property in 10Gb ports.
|
Fixed.
|
CSCsg97468
|
CPU over utilized on the unit servers.
|
Fixed.
|
CSCsg87547
|
No Affected Parties for BGP Neighbor loss while the Router ID is different from the BGP Neighbor
|
Fixed.
|
CSCsg16609
|
Cloud correlation problem.
|
Fixed.
|
CSCsf02136
|
AVM memory usage calculation is not correctly calculated in ANA Manage.
|
Fixed.
|
CSCse63323
|
LDP neighbor loss does not correlate to link down, due to card out.
|
Fixed.
|
CSCse44166
|
FR-5-DLCICHANGE syslog not parsed correctly wit T1 channelized interface.
|
Fixed.
|
CSCsd84449
|
Overlay and link properties- missing selection sensitive menu.
|
Fixed.
|
CSCsd84445
|
Overlay does not work with aggregations - aggregations color issue.
|
Fixed.
|
CSCsc90738
|
Catalyst 4507 - long time to model due to large Vlan quantity.
|
Fixed.
|
Open Caveats - Release Cisco ANA 3.6
Table 11 Open Caveats - Release Cisco ANA 3.6
Identifier
|
Title
|
Impact
|
Workaround
|
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.
|
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
|
CSCsh59223
|
AS5300 and AS5800 - access list is not displayed.
|
Access lists are not modeled on access server devices.
|
None
|
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
|
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.
|
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
|
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.
|
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
|
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
|
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.
|
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
|
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
|
CSCsg45646
|
Cisco AS5300 12.0(3)T1 isn't moduled properly with redunno scheme
|
Not all modules may display in AS5300 VNEs.
|
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.
|
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
|
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
|
CSCsd66486
|
Enterprise generic trap description has junk characters
|
EventVision - Junk characters in the description of V1 trap alarm - `Enterprise junk trap' type.
|
None.
|
CSCsh70734
|
ERX1440: ARP table is not modeled
|
No ARP table. Affects flow that uses ARP table.
|
None
|
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.
|
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.
|
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.
|
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.
|
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.
|
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.
|
CSCsi96000
|
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.
|
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
|
CSCsi45107
|
MS Plus: Missing routing table entries
|
Some of the entries are not displayed on the routing table. Flow will not work properly.
|
None
|
CSCsi23224
|
MultiDsl port support - 2360
|
Missing Profile Name and line spectrum profiles on ABLT-E ports on ASAM XD devices.
|
None.
|
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
|
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
|
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
|
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
|
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
|
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.
|
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.
|
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
|
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.
|
CSCsi50224
|
Support for cisco router 3845
|
Physical & Logical inventory is not shown for Cisco router 3845 if the device is not supported.
|
None.
|
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
|
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".
|
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.
|
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.
|
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.
|
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
|
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.
|
Resolved Caveats - Cisco ANA, Release 3.5.2
Table 12 Resolved Caveats - Cisco ANA, Release 3.5.2
Identifier
|
Summary
|
Explanation
|
CSCsh42902
|
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.
|
Fixed.
|
CSCsh82831
|
In the physical inventory of the BA 40 device, when choosing a port, the customer ID is not shown.
|
Fixed.
|
Open Caveats - Cisco ANA, Release 3.5.2
Table 13 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.
|
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 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.
|
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.
|
Open Caveats - Cisco ANA, Release 3.5.1
Table 14 Open Caveats - Cisco ANA, Release 3.5.1
Identifier
|
Title
|
Impact
|
Workaround
|
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.
|
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.
|
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
|
CSCsg48454
|
VC Removed is not scale
|
Not supported in this version.
|
None.
|
Documentation Updates
This section of the Release Notes includes updates to the Cisco Active Network Abstraction 3.6 Service Pack 1 documentation set.
•Cisco Active Network Abstraction Installation Guide
•Cisco Active Network Abstraction Virtual Network Element Reference Guide
Cisco Active Network Abstraction Installation Guide
In Chapter 7, Installing Service Pack 1 the following procedure has been updated to include a new step 5:
Service Pack Installation
The following procedure describes how to install a Service Pack on the gateway and units.
To install Service Pack 1 on the gateway and launch the units:
Step 1 Log in to the gateway as user "sheer".
Step 2 Create a temporary directory /tmp/ANAPatch on the gateway.
Step 3 Copy the provided file (ANA_3_6_SP1.jar) file to the temporary directory.
Step 4 Enter the command jar xvf ANA_3_6_SP1.jar.
This command extracts the necessary JAR files and a Perl script.
Step 5 Copy the patch InstallationScript.pl to /tmp/ANAPatch/scripts. Contact the Cisco Project Manager or Cisco Account Team to obtain the InstallationScript.pl file.
This overwrites the existing InstallationScript.pl.
Step 6 Enter the command perl ./update.pl SP1 -all.
This command installs the Service Pack, updates the SSH keys, and restarts the system.
Step 7 Log in to a unit connected to the gateway as user "sheer".
Step 8 Enter the command cd /export/home/sheer4/Main to return to the main directory.
Step 9 Enter mvm.csh to launch the unit.
Step 10 Repeat Steps 7to 9 for each unit.
Cisco Active Network Abstraction Virtual Network Element Reference Guide
The Cisco ANA VNE Reference Guide has been corrected and posted to Cisco.com after the following updates were made:
LAG Support Claimed on Cisco Routers
The Cisco Active Network Abstraction VNE Reference Guide, Version 3.6 SP1 incorrectly states which Cisco routers support Link Aggregation (LAG, also known as Ethernet Channel). In fact, among those Cisco routers currently supported by Cisco ANA, LAG support is available only on the Cisco 7600 Series.
Alcatel-Lucent ISAM (7302)
The entry for the Alcatel-Lucent ASAM (7301) is incorrect, and should refer instead to the ISAM (7302). The device and software version information has been updated.
Cisco XR 12000 Routers
A new topic has been added to the Cisco XR 12000 routers section, which mentions the need for the xml agent tty command in the device config, as well as the need to specify the SystemOwner in the SNMP community string.
Related Documentation
User Guides
Cisco Active Network Abstraction Documentation Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction NetworkVision User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction EventVision User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction MPLS User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction Fault Management User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6 Service Pack 1
Cisco Active Network Abstraction VNE Reference Guide 3.6 Service Pack 1
Administrator Guides
Cisco Active Network Abstraction Installation Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction Administrator Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction Error Messages, 3.6 Service Pack 1
Cisco Active Network Abstraction Shell User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction High Availability User Guide, 3.6 Service Pack 1
Developer Guides
Cisco Active Network Abstraction Customization User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction Command Builder User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction Workflow User Guide, 3.6 Service Pack 1
Cisco Active Network Abstraction BQL User Guide, 3.6 Service Pack 1
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
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.
