|
|
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.
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 PDF format in the /cdrom/cdrom0/docs directory on the Cisco EMF product CD.
This section describes the system requirements for the Cisco EMF 3.0.3 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.
| Resource | Cisco EMF (large installation) | Cisco EMF (small installation) | Cisco EMF Client |
|---|---|---|---|
Hardware | Sun Enterprise 450 | Sun Ultra 60 workstation | Sun Ultra 5 workstation |
Operating System | Solaris 2.6 | Solaris 2.6 | Solaris 2.6 |
Memory | 1GB RAM | 1GB RAM | 256MB RAM |
Disk space | Six 9GB 10,000 RPM disks | Two 9GB internal disks 9GB 10,000 RPM external disk | 9GB disk |
Processor | Four x 250MHz | Two x 360MHz | 333MHz |
Swap space | 2GB | 2GB | 2GB |
Monitor | 17" color monitor | 17" color monitor | 17" color monitor |
Graphics Card | 24 bit | 24 bit | 24 bit |
Operating Environment | Common Desktop Environment (CDE) | Common Desktop Environment (CDE) | Common Desktop Environment (CDE) |
Cisco EMF 3.0.3 is a full, minor release. As well as the bug fixes outlined in "Bugs Fixed in this Release", 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. Increased performance and scalability and user security improvements.
4. Object state modeling.
5. The Object Store Database version is now 5.1 (it was previously version 5.0.1).
6. Support for common components for Element Managers.
7. CORBA Gateway integration capability.
8. 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.
9. A cemf show option has been added to the cemfinstall command which allows you to show a list of the installed Cisco EMF packages.
10. The cemfload command functionality has been merged with the cemfinstall command so that Element Manager packages can be installed using the cemfinstall command.
This section contains information about the bugs fixed in the Cisco EMF 3.0.3 release.
1. ATLuk09722---multiple object selector instances result in an error.
2. ATLuk09936---after a reset, object groups are not displayed in the Object Group view. Starting Cisco EMF twice circumvents this problem.
3. ATLuk10599---if you try to restore a database while CEMF processes are running, a message is displayed stating that the database has been restored (this seems to appear as soon as the process starts). However, the restore will not work if the processes are running. It should detect the processes and advise you that they should be stopped before a restore is attempted.
4. ATLuk10892---if the Auto Discovery scheduler is configured to start two different discoveries on different networks at the same time, only one actually takes place. Also, the discovered objects are placed in the wrong containment path. As a workaround, stagger the Auto Discovery start times.
5. ATLuk10934---varbinds are never resolved under certain circumstances.
6. ATLuk11002---the Event Browser crashes when an alarm message includes variable substitution.
7. ATLuk11017---trap forwarding sends out the wrong source address.
8. ATLuk11095---the default location of backup files has been changed from <CEMF_ROOT>/backup to /opt/backup to protect backup data when CEMF is deinstalled.
9. ATLuk11101---the cemfinstall -show command should show patch revisions as well as packages.
10. ATLuk11154---in the Event Browser, an unacknowledged event is initially unavailable after acknowledging multiple events.
11. ATLuk11216---misleading message for deployment of same IP address.
12. ATLuk11285---during installation, the prompt to use a raw partition for ObjectStore is ambiguous.
13. ATLuk11398---in the Event Browser, event history doesn't display cleared alarms.
14. ATLuk11399---if you try to unacknowledge an event acknowledged by another user, a message is not displayed informing you that CEMF is unable to unacknowledge the event.
15. ATLuk11412---event description has greyed out values for no apparent reason.
16. ATLuk11416---often after a redraw, the Description field in the Event Browser displays incorrect data, such as European characters.
17. ATLuk11438---the Alarm Deleter feature does not work; an ObjectStore error is seen in the log file.
18. ATLuk11461---new access spec to allow users to only view the Map Viewer (no edit access) is needed.
19. ATLuk11615---default trapForwardingFile is in wrong directory.
20. ATLuk11741---dynamic refresh doesn't work in object configuration screen.
21. ATLuk11742---for read-only technology view, View menu items should be greyed out.
22. ATLuk11758---LANG variables set to anything other than C stops CEMF startup.
23. ATLuk11781---merge 3.5 schema changes into the 3.0 release.
24. ATLuk11885---the cemf restore command always looks for backup in /opt/AV2.
25. ATLuk11957---need to be able to backup databases totaling more than 2Gb.
26. ATLuk11982---generic objects can be added without specifying a name.
27. ATLuk12027---two duplicate events are listed the first time the Event Browser is opened.
28. ATLuk12109---events which have been acknowledged by an admin user can be unacknowledged by a non-admin user.
29. ATLuk12206---the Event Browser cores when a query was set to find all critical alarms.
30. ATLuk12294---event severity not updated in Viewer.
31. ATLuk12309---when changing the object type being viewed in an Object Configuration window, the display often shows "ERROR" for all values. Refreshing the window with the refresh button will cause the correct values to be seen.
32. ATLuk12330---Auto-discovery fails when rediscovering an existing device.
33. ATLuk12390---clear correlation rules should be parsed in at CEMF startup.
34. ATLuk12550---major alarms are not being displayed properly and sometimes are grey.
35. ATLuk12551---when you create an object with the Map Viewer open, the event status color is gray instead of green, if no events are raised against the object. Once events have been raised, the color is displayed correctly, and will revert to green (normal) when events clear.
36. ATLuk12526---template wizard problem.
37. ATLuk12799---Acrobat and documents remain in list of installed packages even after they have been deinstalled.
38. ATLuk12813---the Event Browser core dumps if an object is deleted while it is launched.
This section contains information about the known Cisco EMF 3.0.3 limitations.
1. 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.
2. The enhanced cemfinstall utility generates files which it uses to determine which Cisco EMF packages are installed. This information was not present in prior releases. Therefore, 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.
3. 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.
4. The Cisco EMF class model has changed slightly. Object classes snmpv1manageable and snmpv2cmanageable have been removed. You should inherit this information from either snmpAgent or snmpProxy.
5. Some help files may not be accessible.
6. 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.
7. 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.
8. 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.
9. 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.
This section contains information about known Cisco EMF 3.0.3 issues.
1. 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.
2. 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).
3. 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.
4. ATLuk08310---when creating an Object Group, the Select All Children option only includes children objects that are expanded.
5. 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.
6. 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.
7. ATLuk09593---newly cleared events are not displayed in the Event History window until the Refresh button is selected.
8. ATLuk09615---when you stop Cisco EMF (using the cemf stop command) and Cisco EMF applications are open, the applications are not killed. It is recommended you always close Cisco EMF applications before issuing a cemf stop command.
9. ATLuk09652---the Map Viewer application cannot be launched from an event in the Event Browser window.
10. 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.
11. ATLuk09707---folders in the Object Group Manager cannot be renamed.
12. ATLuk09868---when an Element Manager is deinstalled while the Map Viewer is running, the application core dumps.
13. ATLuk09927---when the Performance Manager is refreshed, it does not update newly selected attributes.
14. ATLuk10099---each object group can only include objects from a single scope (section of the network), however, the interface allows you to select more than one scope. Only the most recently used scope is used to create the object group.
15. 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.
16. 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.
17. 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. As a workaround, disable, for example, Element Manager services access to the high level object, for the user.
18. ATLuk11010---if all criteria which are loaded into the system contain summary intervals and rules, a historyAdmin export will only export summarized data, not raw data.
19. 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.
20. ATLuk11761---sysmgrClient commands must be invoked in avshell?????
21. ATLuk12720---the Performance Manager dumps core when you try to save data when no data exists.
22. ATLuk12442---a sporadic problem exists where Performance Manager fails to display performance data. The workaround is to ensure the history criteria files are loaded into the system. This is done by invoking the following command:
23. <CEMF_ROOT>/bin/historyAdmin add <CEMF_ROOT>/config/historyCriteria
24. ATLuk12887---very occasionally, on some hardware platforms, the Event Browser fails to show events. A workaround is to refresh the Browser display; this results in the displaying of all events.
25. ATLuk13088---multiple object re-parenting intermittently causes the Map Viewer application to core dump. The workaround is to restart the Map Viewer application.
This section contains information about the known Cisco EMF 3.0.3 documentation issues.
At the time of the CEMF 3.0.3 release, the 2.0 CEMF Event Manager product was not available. Therefore, any references to the CEMF Event Manager product throughout the Cisco EMF 3.0.3 documentation, should be ignored.
The following Atlantech products can be installed and operated with this release:
This section lists the components of the Cisco EMF 3.0.3 product:
1. Cisco Element Management Framework 3.0.3 product CD (part number EMF-SOL-3.0).
2. Release Notes for Cisco Element Management Framework, Release 3.0.3 (part number 78-10145-01 (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 (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:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.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
Posted: Wed Feb 2 09:59:27 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.