Table of Contents

Introduction
Related Documentation
System Requirements
Enhancements in this Release
Bugs Fixed in this Release
Known Limitations with this Release
Known Issues with this Release
Known Documentation Issues with this Release
Compatibility
Bill of Materials
Cisco EMF and Cisco EMF Event Manager Demo CDs
Cisco Connection Online
Documentation CD-ROM

Release Notes for Cisco Element Management Framework,
Release 2.1.4

Introduction

Cisco Element Management Framework is the new homogeneous element management layer of the Cisco Service Management (CSM) system. It comprises a highly scalable framework designed to support carrier-class element managers across Cisco's service-provider product lines. This flexible, modular model allows Service Providers to install the mix of Element Managers they need to support their dynamic businesses. It also enables rapid development and deployment of new Element Managers, permitting Service Providers to more rapidly introduce and manage new services.

Cisco EMF provides common interfaces and element management services to applications in the network and service management levels of CSM. Cisco's EcoSystem partners can also build third-party element management systems to provide element management support in mixed network environments.

Related Documentation

The following documents are companions to this document:

• Cisco Element Management Framework User Guide, Release 2.1

• Release Notes for Cisco Element Management Framework Event Manager, Release 1.1.3

• Cisco Element Management Framework Event Manager User Guide, Release 1.1

System Requirements

This section describes the system requirements for the Cisco EMF 2.1.4 product.

Cisco EMF can be deployed in a number of configurations, from a single hardware system solution, up to a multi-site distributed management system. All Cisco EMF-based solutions run on Sun Solaris/SPARC hardware running the Solaris 2.6 operating environment.

A basic Cisco EMF installation requires 300MB of free file system disk space (for example, /opt). The system also requires an appropriate amount of free disk space for database files. Table 1 lists the Cisco EMF system requirements.

Enhancements in this Release

Cisco EMF 2.1.4 is a full, minor release. As well as the bug fixes outlined below, the following major improvements are included in this release:

1. Multiple EM support---a single Cisco EMF system can be used to manage several different network devices, each with a different Element Manager.

2. Menus presentation---the presentation of right mouse button menus are improved to include:

(a) cascading menus to fit more easily on the screen

(b) sorting options for menu items.

3. Installation improvements.

Bugs Fixed in this Release

1. ATLUK05913---after running Cisco EMF for a day or two, stopping core causes a core dump.

2. ATLUK06802---Acrobat Reader is now supplied with software releases to facilitate reading the manuals supplied in PDF format. You can copy it from the product CD if you wish to install it.

3. ATLUK07205---rebranded software is now installable ina single installation.

4. ATLUK07245---when an attribute was created and then deleted, it could not be reused.

5. ATLUK07346---AutoDiscovery finds devices other than the devices specified in the OIDMapping config file; AutoDiscovery does not find all devices within the IP address range; AutoDiscovery finds devices outside the (default) subnet; AutoDiscovery finds impertinent devices under the mgmt-containment and network-containment tree in the Manager GUI.

6. ATLUK07477---Event Browser event severities are now displayed by default.

7. ATLUK07479---when an Event Manager is installed and numofSamplingPeriods is set to an incorrect value, a core is generated from attributehistor.

8. ATLUK07522---the Performance Meter core dumps when launched against a Sun object.

9. ATLUK07609---Hex Handler on screen causes an Element Manager to core dump.

10. ATLUK07655---several license keys can be used simultaneously

11. ATLUK07658---the eventTimeStamp is not displayed correctly within a partial table matrix.

12. ATLUK07665---the "24 Hr Perf Task" causes Cisco EMF to enter a continuous loop.

13. ATLUK07771---the serialization buffer is no longer resized indefinitely.

Known Limitations with this Release

This section contains information about the known Cisco EMF 2.1.4 limitations.

1. The Event Browser is limited to showing no more than 10000 alarms. Any attempt to view more than this amount results in an error being message. Use the Filter Editor to modify the filter to reduce the granularity.

2. The AutoDiscovery application allows you to specify discovery of a Class A network which could result in the discovery of potentially four million objects. When this is attempted, AutoDiscovery shuts down after a period of time.

3. The Class Palette available on the Map application can be used to initiate deployment of an object. However, the AccessVision Management Toolkit generates classes that are incompatible with the Class Palette and therefore, it cannot be used to deploy classes of objects that are generated by the AccessVision Management Toolkit.

4. When installing Cisco EMF on a UNIX system that has more than one network card installed, you must take care in answering the installation questions correctly.

The multiple interfaces will each have been configured with a name and associated IP address. The Cisco EMF installation should be associated with the main network interface (that is, that network on which Cisco EMF clients will be installed). If this is not chosen correctly, the Cisco EMF client/server functionality may not operate correctly.

During the installation process, you will be asked to confirm whether the system hostname and IP address that has been determined automatically, is valid. If you wish to associate the Cisco EMF installation with a different interface card than the one displayed, you should answer "N" to the confirmation question and then supply the appropriate interface hostname information. The IP address will then be automatically determined, if possible, and again you will be asked to confirm that the information is valid.

Therefore, although you are not provided with a list of the configured multiple interfaces to choose from, you still have the opportunity to choose the appropriate interface. You just need to be aware of the system configuration before you begin the Cisco EMF installation process.

Known Issues with this Release

This section contains information about known Cisco EMF 2.1.4 issues.

• ATLuk3851---in the Performance Manager, the X-axis is non-linear when reporting raw performance statistics.

• ATLuk3944---two sessions of the Performance Manager cannot be run on the same GUI server.

• ATLuk03655---when the Event Browser is set to manual update and an alarm arrives, no indication is given that the page requires updating.

• ATLuk04236---clearing multiple alarms in the Event Browser when using the Shift Select key sequence, does not always work. This happens when you select on either the top or bottom alarm and use Shift Select to select another alarm in the Event Browser. Clearing the selected alarms may only clear the first alarm selected.

• ATLuk4305---the Bar chart does not print out correctly.

• ATLuk04861---the printing of the hierarchy in the Map Manager is missing the rootNode and links.

• ATLuk5106---accelerators do not work in some Cisco EMF scenarios.

• ATLuk5755---inconsistency with shortcut keys between the Map Manager and the Performance Manager for Zoom in/out capabilities. Refer to the Cisco Element Management Framework User Guide for specific information.

• ATLuk5810---attempting to provision on a second top-level map results in the objects being added to the first top level map.

Workaround: use the Add Objects service and drag/drop to overcome this problem.

• ATLuk05813---if an object is provisioned and that object creation only partially succeeded, the object is not properly added to the maps. The maps are responsible for setting up status propagation which won't be set up correctly when the objects are not added to the map hierarchy correctly.

Workaround 1: partially created objects only occur when the object is provisioned with attributes that do not belong to that class of object. Make sure this is not the case.

Workaround 2: the objects can be added manually to the correct location by using the Add Objects feature on the maps. Add the objects to the desired place in the hierarchy and status propagation is set up.

• ATLuk5822---the Object Manager GUI sometimes shuts down upon creation and deletion of a large number of objects simultaneously, due to a comms corruption bug. This does not affect the integrity of object data.

Workaround: reopen the Object Manager.

• ATLuk05830---you cannot change the IP address of the Manager machine.

• ATLuk5855---MIBs do not load properly when the MIB module name is split into two parts and separated by MIB comments.

• ATLuk5888---using the Sun admintool to install Cisco EMF 2.1.4 can occasionally lead to installation problems. Refer to the Cisco Element Management Framework User Guide to ensure correct installation.

• ATLuk05902---in the discoverScheduler.ini file, when a nonexistent network is specified, the discoveryScheduler program shuts down.

• ATLuk05941---map nodes are representations of objects in containment trees. When an object is renamed in a containment tree, it is not renamed for the node on the map.

Workaround: after renaming the object in a containment tree, use the map node's Rename feature to change the name there, as well.

• ATLuk06173---when an Object Configuration screen is open over an object and communications is lost to that network device, the Object Manager closes.

• ATLuk06189---when an object with a valid IP address is created through the Provisioning wizard, the object may be rediscovered using AutoDiscovery.

Workaround: AutoDiscovery uses the networkContainment tree to validate whether an object has already been discovered. The Event Manager controller should add the object created through the Provisioning wizard, under the appropriate network object in the network containment tree.

• ATLuk06205---when the window from which avsession was initiated is closed, the Launchpad application also closes. Other windows remain open.

• ATLuk06210---when using only the system description part of the OID mapping field, the AutoDiscovery engine does not discover nodes.

Workaround: use both systemObjectId and sysDescription.

• ATLuk06348---in a generic Cisco EMF installation with no specific EM controller, when AutoDiscovery is launched from a specific object, the discovered devices may not be created under the object from which you launched the discovery. This is desired behavior, however, it is confusing.

• ATLuk07238---when the Object Manager is closed and Help has just been launched, it can cause the objectAdminGUI to core dump, therefore, Help is un-launchable on the next attempt.

• ATLuk07567---performance data is not logged to a directory when that directory does not exist.

• ATLuk07639---Auto-naming (for example, for sites) does not work for appending additional objects (for example, sites) onto previously deployed sites.

• ATLuk07899---documentation is not automatically installed in the relevant directory (for example, /opt/AV/docs).

• ATLuk07902---you must have the Cisco EMF 2.1.4 product CD to be able to uninstall this version of the software.

• ATLuk08120---the Auto Discovery GUI dumps core when you attempt to discover a subnet without first ensuring that appropriate UNIX routes exists between the network of the Cisco EMF Server and the subnet in question.

Known Documentation Issues with this Release

This section contains information about the known Cisco EMF 2.1.4 documentation issues.

The 2.1 Cisco Element Management Framework User Guide is not provided in hard copy format, nor on the Cisco Documentation CD, nor on Cisco Connection Online (CCO). The documentation is only provided in PDF format on the 2.1.4 Cisco EMF product CD. Upon installation of the 2.1.4 Cisco EMF product, the CiscoEMF.pdf file is located in the <AVROOT>/docs directory, where <AVROOT> is the directory into which you installed the 2.1.4 Cisco EMF product.

Compatibility

The following Cisco and Atlantech products are compatible with this release:

• Cisco EMF Event Manager, Release 1.1.3

• Atlantech AccessVision Management Toolkit (AVMT), Release 1.0.9

Bill of Materials

This section lists the components of the Cisco EMF 2.1.4 product:

1. Cisco Element Management Framework 2.1.4 product CD (part number EMF-SOL-2.1).

2. Release Notes for Cisco Element Management Framework, Release 2.1.4 (part number 78-7030-01 (this document)).

3. Cisco Element Management Framework User Guide (online part number OL-0236-01).

Cisco EMF and Cisco EMF Event Manager Demo CDs

When you receive a Cisco EMF Demo CD, you also receive the Cisco EMF Event Manager Demo CD. Upon installing the Demo CDs, you need not install a Cisco EMF Event Manager license key, as you normally would. Instead, follow the licensing instructions found in the "Installation" chapter in the Cisco Element Management Framework User Guide, as the Cisco EMF demo license applies to the Cisco EMF Event Manager demo product as well.