Table Of Contents
Release Notes for Cisco Element Management Framework,
Cisco Element Management Framework is the 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.
This document is divided into the following sections:
The 3.0 Cisco Element Management Framework Installation and Licensing Guide and the 3.0 Cisco Element Management Framework User Guide documents are companion documents. These documents are provided in hard copy format, as well as, online on the Cisco Document CD and through Cisco Connection Online (CCO) at the following URL:
See the "Cisco Connection Online" section for detailed information on how to access CCO.
This section describes the system requirements for the Cisco EMF 3.0.4 product.
Note You must install the CEMF3.0.4-Patch<n>.tar.z patch when you install the Cisco EMF 3.0.4 product. Note, install the patch whose number, <n>, is the highest, as that patch will incorporate the contents of the patches with lower numbers.
For CCO users, you obtain access to this patch and its corresponding release notes (CEMF3.0.4-Patch<n>.rel-note.txt) from the following URL:
or via FTP at ftp://ftp.cisco.com/cisco/netmgmt/cemf
For public users, you obtain access to this patch and its corresponding release notes (CEMF3.0.4-Patch<n>.rel-note.txt) from the following URL:
or via FTP at ftp://ftp.cisco.com/pub/netmgmt/cemf
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 two internal disks with at least 9GBs of free file system disk space (for example, /opt). The system also requires an appropriate amount of free disk space for database files. See for a list of the Cisco EMF recommended system configuration requirements.
Enhancements in this Release
Cisco EMF 3.0.4 is a full, major release. The following major improvements are included in this release:
1 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.
2 Increased performance and scalability and user security improvements.
3 Object state modeling.
4 The Object Store Database version is now 5.1 (it was previously version 5.0.1).
5 CORBA Gateway integration capability.
6 The cemfinstall command can be used to deinstall (-remove option) packages, such as Element Managers, without the need for the original product CD (that contained the package) to be available.
7 A cemf show command option has been added to the cemfinstall command which allows you to show a list of the installed Cisco EMF packages.
8 The cemfload command functionality has been merged with the cemfinstall command so that Element Manager packages can be installed using the cemfinstall command.
9 Installation now checks for swap space available for Cisco EMF. It displays a warning if less than 1 Gigabyte of physical and virtual memory is available.
10 During installation, you no longer need to update the hostname information when using a temporary license key.
11 The Class Palette, used for deploying objects onto Maps, now contains "SNMP Agent" and "SNMP proxied device" for easier deployment.
12 A new version of the SNMP Research Brass stack is now part of Cisco EMF. It provides a major improvement in trap and polling performance.
13 The cemf query command now provides the full software version number for easy reference.
Known Limitations with this Release
This section contains information about the known Cisco EMF 3.0.4 limitations.
1 Installation of any Element Management System (EMS) does not check for the correct compatible version of Cisco EMF.
2 There is no way to cancel a scheduled download of an IOS image. NOC operators also have no view of scheduled actions.
3 Some provisioning operations can significantly impact other user operations on the same system.
4 Backup/Restore—when an Element Manager is installed and run, it creates its own database under /db. Currently, it is required that the dbGroups file under config/data is updated with the new database name. This must be done manually after installation.
5 The enhanced cemfinstall utility generates files which it uses to determine which Cisco EMF packages are installed. Element Managers should be deinstalled using the cemfload utility that was provided as part of their release and Cisco EMF should be deinstalled using the cemfinstall utility of its release.
6 Deinstalling an Element Manager is supposed to bring down all running applications as part of the deinstallation. This sometimes causes the applications to crash. It is better to manually bring down all application sessions before deinstalling an Element Manager.
7 The Event Browser is limited to showing no more than 10000 alarms. Any attempt to view more than this amount results in an error message. Use the Filter Editor to modify the filter to reduce the granularity.
8 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.
9 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, the Class Palette cannot be used to deploy classes of objects that are generated by the AccessVision Management Toolkit.
10 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 3.0.4 issues.
1 CSCdp38669—more than one alarm for a single object. In the Map Viewer window, the total number of alarms displayed can exceed the total number of objects in a system.
More than one alarm for the same object can be displayed in the Event Browser.
New alarms on an object do not replace previous alarms on the object, but are accumulated. For the Event Browser, selecting Refresh updates the screen correctly.
2 CSCdp40994—under certain circumstances, the Performance Manager shows/plots erroneous data. The graphs plotted with this data are misleading and confusing. When the data is exported to a file using Export to file option, the file has the correct data.
3 CSCdp67835—in the Event Browser, object names have been known to be displayed as "NO NAME AVAILABLE" if the events are dynamically updated. Object names are displayed properly if the events are not dynamically updated.
4 CSCdp92877—on a client, when two or more persons start the same operation simultaneously, the system can hang. The Map Viewer stops painting in the right pane. When the Map Viewer hangs, random clicking on it leads to more problems.
5 ATLuk06620—object groups cannot be created to include more than one "Containment scope". However, several Object Groups can be created, one for each "scope" or subset of the network, and then these groups can be collected into a single Object Group.
6 ATLuk07063—Event Browser views customized using the Query Editor are updated dynamically. However, the event list is not dynamically updated for customized views that are specific to individual users (for example, all events acknowledged by JDoe). This can be overcome by either doing a manual refresh (Refresh button), or customizing the view to be independent of an individual user (for example, all acknowledged events).
7 ATLuk07995—it is no longer possible to query SNMP attributes over the network. Only attributes stored on a local database can be queried to prevent queries from overloading the network. However, if such a query is initiated, it will not succeed and a warning is not provided.
8 ATLuk08310—when creating an Object Group, the Select All Children option only includes children objects that are expanded.
9 ATLuk08428—when managed object icons are placed at the top of the right-hand map view, the message balloon that provides information on events, cannot be seen. It is recommended to leave enough space for the message balloon between the top of the managed object icon and the top of the map view.
10 ATLuk08867—objects can be created with a blank name or names that contain slashes. This can lead to confusion. It is recommended that only alphanumeric names be used.
11 ATLuk09593—newly cleared events are not displayed in the Event History window until the Refresh button is selected.
12 ATLuk09652—the Map Viewer application cannot be launched from an event in the Event Browser window.
13 ATLuk09653—when you navigate down through the Map views in the right panel by double clicking on object icons, the "up arrow" icon displays blank map views. As a workaround, you should navigate up using the left panel's hierarchy tree.
14 ATLuk10469—enabling the "Export to File" option from the Performance Manager results in performance data being appended to the existing file, instead of overwriting what is already in the file.
15 ATLuk10674—when viewing a graph in the Performance Manager, the y-axis ranges from 0 at the origin to -1 at the top; polled values can be seen normally in the table view.
16 ATLuk10728—launching services from a high-level access point (for example, from a "site"), enables services on all of the children of the access object to be available, regardless of any data access restrictions placed on the children objects elsewhere.
17 ATLuk11582—it is only possible to deploy regions, using the Deployment wizard, under the root of the Physical tree. If regions are required elsewhere, the "Reparent" function should be used.
18 ATLuk13088—multiple object re-parenting intermittently causes the Map Viewer application to core dump. The workaround is to restart the Map Viewer application.
19 ATLuk13976—use of the Solaris pkgchk utility: note that, due to the fact that the eminstall program (used to install Element Managers) substitutes the correct path for <CEMFROOT>, invoking the pkgchk utility on a Cisco EMF installed package fails.
20 ATLuk14437—if the Manager is stopped, the following error message is displayed:
ERROR: <CEMFROOT>/config/scripts/session command failed.
This message can be ignored.
21 ATLuk14775—the Event Browser is not automatically updated when events are acknowledged or cleared using the menu, rather then the browser buttons. Refreshing the browser window will update the display.
22 ATLuk15354—if you change the IP address of a managed object to be in a different network, the object count in the Network view is not updated.
23 ATLuk15420—the Deployment Wizard allows you to deploy two objects with the same IP address. Devices should not be deployed with the same IP address.
The following Atlantech products can be installed and operated with this release:
•AccessVision Management Toolkit (AV-MT), Release 1.2.1
•AccessVision CORBA Gateway Developer Toolkit, Release 1.0.2
Bill of Materials
This section lists the components of the Cisco EMF 3.0.4 product:
1 Cisco Element Management Framework 3.0.4 product CD (part number EMF-SOL-3.0).
2 Release Notes for Cisco Element Management Framework, Release 3.0.4 (part number 78-10145-02 (this document)).
3 3.0 Cisco Element Management Framework Installation and Licensing Guide (part number 78-10148-01).
4 3.0 Cisco Element Management Framework User Guide (part number 78-10146-01).
Cisco Connection Online
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
•Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact firstname.lastname@example.org. For additional information, contact email@example.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or firstname.lastname@example.org. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or email@example.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
78-10145-02 Rev. A0