Table Of Contents
Release Notes for
Cisco Element Management Framework v3.2
This document is divided into the following sections:
Cisco Element Management Framework (Cisco EMF) is the homogeneous element management layer of the Cisco Internet Operation Support System (OSS) building on and adding to the Cisco EMF v3.0 and v3.1 product functionality. It comprises a highly scalable framework designed to support carrier-class Element Managers (EMSs) across Cisco's service-provider product lines with network event management. A range of EMSs are available on Cisco EMF v3.0, with additional EMSs available on Cisco EMF v3.1.
Cisco EMF provides common interfaces and element management services to applications in the network and service management levels of Cisco Internet OSS.
Cisco EMF v3.2 is an update release to Cisco EMF v3.1. As well as the major feature enhancements detailed below, a large number of bug fixes and minor customer enhancements are included in this release. Please consult Cisco DDTS for full details of bugs resolved in the Cisco EMF v3.2 release.
For customers migrating to Cisco EMF v3.2 from Cisco EMF v3.0, it is advisable first to be familiar with the Cisco EMF v3.1 feature set - Cisco EMF v3.1 included significant enhancements in fault management capability as well as northbound integration interfaces. In particular, the Cisco EMF Event Manager application - available as an option on Cisco EMF 2.1.4 but not with Cisco EMF v3.0 - is now a standard part of Cisco EMF v3.1 (and above).
For more detailed information on Cisco EMF v3.2, please see the documentation available from CCO at:
Or as defined in Related Documentation
For information on the differences between Cisco EMF v3.0 and v3.1, please consult:
Enhancements in This Release
Solaris 8 Support
Cisco EMF v3.2 now supports operation on Sun Microsystem's Solaris 8 as well as 2.6 operating system.
Specifically Cisco EMF supports EMSs which have been built on Solaris 2.6, and tested on Solaris 2.6 and 8.
Note If you are deploying your Cisco EMF EMS on Solaris 2.6, you cannot run on one of the newer Sun products which support Solaris 8 only. This includes the SunBlade and SunFire product ranges.
Note Please check your EMS documentation for Sun operating systems support details. While Cisco EMF supports both operating systems, individual Cisco EMF EMSs may only run on one of the two supported Solaris releases.
Improved Scale and Performance
Cisco EMF v3.2 includes a large number of improvements which increase Cisco EMF EMS scale and performance, including:
•Improved Cisco EMF startup time—significantly improved over Cisco EMF v3.0 and v3.1
•Improved SNMP polling capability, enabling EMSs to support more network elements. In particular, this capability is enabled by Cisco EMF support for multiple SNMP stacks. Please consult your EMS documentation for specific recommendation on the numbers of network elements supported.
•Improved responsiveness when Cisco EMF EMSs are used with multiple users. Cisco EMF v3.2 EMS end user scale is defined in terms of 'active' and 'inactive' users. An active user is defined as an end user making actually use of Cisco EMF and EMS GUIs, or as having the Event Browser active and displaying events. An inactive user is defined as one who specifically is not performing GUI interaction at all, who has - for example - the Map Viewer open, but specifically is not running the Performance Manager or Event Browser applications.
•Cisco EMF v3.2 EMSs typically support up to 10-30 active, with a balance of passive users up to a maximum combined total of 50 concurrent active and passive, simultaneous end users. Additional testing with specific EMSs has also shown significant improvements over Cisco EMF v3.0.4 and v3.1 based EMSs, and application responsiveness degradation as end user load increases has been radically reduced. Cisco EMF v3.2 EMSs have shown reasonable response times for thirty active, twenty inactive users, with on-going simultaneous background EMS load including background provisioning (object creation), trap processing and presence polling load. These figures will vary from EMS to EMS, so please consult appropriate EMS User and Administration documentation for complete details before purchasing deployment hardware. Also, please consult the Cisco EMF v3.2 Installation and Administration Guide for typical deployment configurations, with Sun and X clients. In particular, Cisco EMF v3.2 recommends the use of Cisco EMF Presentation Servers for multi-user deployments. With five users per CPU and 100MB per user RAM, a typical presentation server specification will be a two CPU Sun Ultra 60, with 1GB RAM, for ten users.
•Significantly improved Cisco EMF EMS chassis deployment and commissioning times
•Improved EMS PVC provisioning times
Availability Improvements: Cisco EMF Backup
Cisco EMF Backup, as on Cisco EMF v3.0.4-patch 9 and Cisco EMF v3.1, paused object creation operations while the backup occurred. Improvements have been made so that now in Cisco EMF v3.2 only a slight pause in object creation related occurs at the start of the backup (a `quiesce' period), to enable a consistent snapshot of all Cisco EMF and EMS databases to be taken. As part of this quiesce period, all in progress Cisco EMF object creation operations are allowed to complete, and new operations suspended until the quiesce period is over. At this time, normal Cisco EMF operation is resumed and Cisco EMF backup proceeds in tandem with normal Cisco EMF operation. This contrasts markedly with previous releases where normal operation was resumed only when the full backup was complete. This improvement is particularly significant for large databases when backup times are long.
Cisco EMF backup has been improved for Cisco EMF v3.2 EMSs, with many improvements including the following feature additions:
•With Cisco EMF v3.1 and previous releases, performing a backup paused all database updates (including object and alarm creation) for the duration of the backup. In Cisco EMF v3.2, only a small quiesce period is required prior to backup commencing to ensure consistency of the data. Database backup starts and normal system operation resumes, so that Cisco EMF approaches on-line backup.
•Cisco EMF v3.2 backup supports multiple backups per day without overwriting previous backups this day. This improves availability and disaster recovery time.
•Command line usability has been improved, for example a -h option now displays full command line help information
Cisco EMF v3.0.4 and v3.1 EMS Compatibility
Cisco EMF v3.0 EMSs will not run on Cisco EMF v3.2 and are not supported. Cisco EMF v3.1 EMSs will be supported running on Cisco EMF v3.2 when Cisco EMF v3.2-patch1 (or above) is available.
A number of administration and application usability enhancements are included with Cisco EMF v3.2, including:
•Client switching—it is now possible, via the use of multiple simultaneous Cisco EMF sessions, to connect a Cisco EMF client or Cisco EMF presentation Server to multiple Cisco EMF management servers workstations providing that the EMS client software has been installed on the Cisco EMF client/presentation server workstation.
•Cisco EMF Viewer enhancements—the multiple view structure has been simplified, the `genericObjects' view is now hidden to assist end user clarity.
•A new Launch Map feature is now available from, for example object lists in Cisco EMF EMSs and Event Browser events—this enables you to navigate from an EMS GUI or other Cisco EMF application such as the Event Browser to the map which contains the relevant object with a single menu operation.
•The Cisco EMF Auto Discovery GUI has been made more intuitive with a clear workflow defined by the GUI.
•Event propagation in Cisco EMF EMS chassis map views has been improved. At the chassis level, in previous releases, an event on a subordinate object (e.g. port) would propagate to the chassis level but would not appear in Event Browser. This has been changed, so that propagated events on subordinate objects appears in Event Browsers invoked at the chassis level. Launching the Event Browser on higher level objects now shows all alarms on or beneath that object.
•Cisco EMF Thresholder—it is now possible to setup thresholding on EMS attributes from EMS GUIs. Simply move your mouse cursor over the relevant attribute on the EMS GUI - for example CPU Utilization. You will notice that the mouse cursor changes from a pointer to a computer mouse icon. At this point, you can right click to receive a popup menu that will let you add new thresholds, and add new attributes to existing threshold regimes. This saves you from the time consuming process of identifying the attribute within the Cisco EMF class hierarchy, as was the case in Cisco EMF v3.1.
•Cisco EMF now supports more flexible permissions for EMS menu options: depending upon your EMS, you may find that some menu options will not be available- these are not permitted operations for the selected network element and access to them has been denied by your Cisco EMF EMS.
Important Functionality Changes
A number of behavior changes have been made to Cisco EMF v3.2, details as follows:
•Cisco EMF Security Management by Domain (often called Data Partitioning). Since release in Cisco EMF v3.0, there have been a number of bugs in this feature - serious bugs unfortunately that meant that the feature was not secure (as detailed in previous release notes). It has not been possible to resolve these in the Cisco EMF v3.2 release and this feature has been turned off for this release. Specifically the capability to associate a Cisco EMF Access Specification with an Object Group has been disabled. By default, when upgrading to Cisco EMF v3.2, any such associations will be removed. It is intended to re-introduce this feature in a post Cisco EMF v3.2 release.
Note Cisco EMF security features based around the Access Specifications are still fully supported, and give very powerful security management features to a very granular level.
•The Cisco EMF CORBA Gateway now includes the Iona Orbix 2000 ORB and Notification service. Use of the Cisco EMF CORBA Gateway for system integration with operational support systems requires an integration module, built using the Cisco EMF CORBA Gateway Developers Toolkit. For those customers using an EMS in an integrated OSS environment, via the Cisco EMF CORBA Gateway, use of the newer release of the Iona ORB may require some updates to the integration code. Please refer to the release notes for the Cisco EMF CORBA Gateway Developer Toolkit product for further details.
Cisco EMF can be deployed in a number of different configurations, from a single hardware system to a multi-site management system, using Sun Solaris/SPARC hardware with Solaris, Release 2.6 or Solaris 8.
Note If you are deploying your Cisco EMF EMS on Solaris 2.6, you cannot run on one of the newer Sun products which support Solaris 8 only. This includes the SunBlade and SunFire product ranges.
Element Managers installed on Cisco EMF (versions 2.1.4, 3.0.4 and 3.1) have been tested and released for Sun's Solaris 2.6 operating system.
Note Solaris 2.6, as of April 2001, is still fully supported but no longer sold by Sun Microsystems.
A Sun Solaris 2.6 media pack is available for purchase from Cisco.com to enable you to run Cisco Element Management Framework element managers (Cisco EMF EMSs) in the event that you do not have access to Solaris 2.6.
Note If you already have access to Solaris 2.6 CD or machine, it is not necessary to order one as they can be reused.
Sun Microsystems have given Cisco permission to ship this to you, and your Sun license permits you to install this Solaris software on Sun workstations. Note that it can be installed on both Sun desktop and server products - specifically those that support Solaris 2.6.
System Requirements and Solaris Release Choice
Cisco EMF EMSs certified to run on Solaris 8 can be deployed on the following Sun hardware models which run Solaris 8 (and above) only.
•Sun Desktops: SunBlade 100, and SunBlade 1000
•Sun Servers: E280R and the SunFire range 3800, 4800, 4810, 6800
Note If deploying Cisco EMF EMSs on Solaris 2.6, you cannot choose one of the aforementioned Sun systems - please deploy on a Sun system which runs Solaris 2.6.
Known Limitations in the Release
Cisco EMF CORBA Gateway Runtime component
Iona Orbix issue : If Cisco EMF is installed on a Sun workstation which is not running Domain Naming Service (DNS), the Cisco EMF-CORBA Gateway Runtime Server fails to start.
re-install Cisco EMF, and when asked for a domain press Return, this enters an empty string. Do not re-install Orbix
install Cisco EMF only on workstations which run DNS.
How to remove the Orbix demon from Cisco EMF process control
Some clients may wish the CORBA Orbix demon to run constantly even after Cisco EMF has shutdown. To do this the client must execute the following commands:
> cd <CEMF_ROOT>
> mkdir backupProcessFile
> cd config/processes/
> mv S08orbixd_3.0.x /<CEMF_ROOT>/backupProcessFile/.
> cd <CEMF_ROOT>/bin
> sysmgrClient -k orbixd
> <CEMF_ROOT>/Orbix/bin/orbixd -s &
where <CEMF_ROOT> is substituted for the current installation directory.
The Cisco Element Management Framework Installation and Administration Guide Version v3.2, provides information to install, license, and configure the product and includes detailed administration tasks.
Locating Cisco EMF Patches
You must login to Cisco.com to access patches. All Cisco patches can be accessed from : http://www.cisco.com/kobayashi/sw-center/sw-netmgmt.shtml
From this location you can select the appropriate patch page depending on the version of Cisco EMF you need to patch or if you need patches for EMS Development.
Note If you try to navigate to Cisco EMF patches via the software centre on Cisco.com, you must first select the login option, otherwise Cisco EMF patches will not be visible.
For information, note that Cisco EMF 3.2 was tested with the following Solaris patches, Solaris Patches and Solaris 8 Patches, which were current when Cisco EMF 3.2 was released. None of these patches is known to be mandatory, though we would recommend having this or higher revisions of any recommended Solaris patch.
The current Sun recommended patch cluster can be downloaded from http://sunsolve.Sun.COM. Please note that higher revisions of the patches may introduce dependencies on other patches which are not reflected in the following lists. You should follow the patch dependencies as recommended by Sun Microsystems, Inc.
Solaris 2.6 Patches
Solaris 8 Patches
Default Backup Directory
If the default installation settings were used to install v3.0, the default backup directory has changed between versions as follows:
Cisco EMF v3.0 default backup directory Cisco EMF v3.2 default backup directory
Desktop Color Setup
Cisco EMF uses the color setup of your display. If your system is set up to display text in white, this may give problems in some Cisco EMF applications, for example on an event group icon in the Event Groups application. To avoid this, select the default color configuration.
Cisco EMF EMS Interoperability
Please consult your EMS documentation for certified EMS interoperability information, if you wish to run two or more EMSs on the one Cisco EMF installation.
Note Cisco EMF v3.2 incorporates all resolved bugs and fixes incorporated in Cisco EMF v3.0.4 and v3.1 patches, specifically:
—upto and including Cisco EMF v3.0.4 patch 14
—upto and including Cisco EMF v3.1 patch 4
Cisco EMF v3.2 is constantly improving, and caveats will be resolved and workarounds provided after the release date. For the most up-to-date information refer to the Release Note and Customer Note enclosures provided in DDTS on Cisco Connection Online.
This section includes the following information:
Open Caveats (Application Framework)
object group access not updated for client
Symptom / Conditions—It is possible to use the Access Manager to allow certain application features to be restricted for a user. In particular, an Access Specification can be created to restrict features to objects in a particular object group.
If however, the contents of such a group changes while a particular Cisco EMF session is running, the change will not appear popup menus in, for example, the Map Viewer.
This means that, where an object is removed from a group, features will still appear to be available. Where an object is added to a group, the features may appear to be unavailable.
Workaround—This does not affect the actual security of the features when they are launched: at this point, object group membership is checked and access to features will be as intended.
The workaround to correct the popup menus is to close the session and open a new one.
[CSCdr15596] Default values must be re-selected to activate in menus
Symptom—Default values in various EM menus must be re-selected in order to activate them.
Conditions—This problem is seen when using some EM menus.
Workaround—No workaround is currently available.
(CSCat20433) AV allows TNet Radios to be re-parented to subnets
Symptom—Cisco EMF allows an object to be re-parented under another object that shouldn't be a valid parent.
Conditions—This problem is seen when, for example, an object has been deployed under a site and that same object is subsequently allowed to be placed under a Proxy or a subnet.
Workaround—There is currently no workaround for this problem.
Reparent/remove services fail for a containment-independant map
Symptom—Reparent and remove services fail for a containment-independent map.
Conditions—This problem occurs when a service is invoked from the right-hand side of the Map Viewer, and an object is passed to the service as the parent of another object.
Workaround—No workaround is currently available for this problem.
Event Browser: printing fails silently when lp is not installed
Symptom—When using the Event Browser to print the list of events displayed it can be the case that nothing prints, and no message is apparent to explain that the print operation has failed.
The sysmgr.log file (located in <CEMF ROOT>/logs [typically /opt/cemf/logs]) should show the message -"sh: lp: execute permission denied"
which indicates the nature of the problem.
Condition—This condition occurs if you are running the Event Browser on a machine which does not have the lp command installed or if your user account on Unix does not have access to the lp command. The Event Browser attempts to use this command to print with, but gives no message back to the user if it is not found or cannot be accessed.
Workaround—Contact your system administrator to request that the lp command if made available with the correct permissions on your Unix machine.
ATM core dump occurs on creation of profile.
Symptom—When an object is created the dialog on which the object is created exits unexpectedly.
Conditions—This problem occurs when an object is created with a name that is more than a hundred characters long.
Workaround—Do not create an object with a name that is more than a hundred characters long.
Sub-dialogs launch with incorrect list population
Symptom—Child dialog launches with previous object list's objects.
Conditions—This happens when the user changes the selection on a parent dialog's object list prior to launching the child dialog.
Workaround—Do not change the selection on the parent dialog prior to launching the child dialog.
1st time launch of EvBrw from LaunchPad with CDM too long
Symptom—The first time the user launches the Event Browser from the Launch Pad, it may take at least 30 seconds for the query editor to display.
Condition—The length to time it takes the query editor to display depends upon the internal complexity of the element manager you are using, and can vary between element managers.
This only affects the first time launch, subsequent launching of the Event Browser, will result in it being displayed in the region of 5 seconds.
Workaround—There is no workaround.
Multi-line text field attribute cannot be saved.
Symptom—After modifying an attribute represented by a multi-line text field within an element manager dialog you may find that the save button on the dialog remains greyed out and you have no way of saving your changes. Changing the contents of another attribute on the dialog to then activate the save functionality and then saving will not save the changes made on the multi-line text field.
Condition—This problem occurs when an a multi-line text field attribute is on a dialog outwith a notebook page.
Workaround—There is no workaround for EM end users.
Busy pointer (cursor) disappears before action complete.
Symptom—While an Element Manager dialog is performing a large operation such as auto discovering 30 devices with 1500 managed objects under each, the dialog may move from a busy state (i.e. the cursor is a small clock) to a busy off state (i.e. the cursor becomes a small arrow) before the operation has completed.
Condition—This occurs when the Dialog is performing an operation that takes a long period of time and occurs because EM dialogs have a built in timeout period for operations. This timeout busies off the dialog if it has been waiting a configurable time period (default is 20 seconds).
Workaround—There is no workaround for the CEMF end user.
Closing rename dialog before rename complete causes map exit
Symptom—Map Viewer exits unexpectedly when the Rename Object dialog which can be opened by accessing the Tools->View Manipulation->Rename Object ... menu is closed before the rename operation has completed.
Condition—Select the Rename Object menu option from the View Manipulation Menu. Perform an operation that loads the CEMF manager server (e.g. Commissioning a number of objects). Change the name of the object in the Rename Object Dialog then quickly press Apply and then Close. The Map Viewer will exit unexpectedly.
Workaround—When the Apply button has been pressed, wait until the Map Viewer updates with the renamed object before selecting close.
Session exits unexpectedly on a client while installing an EM.
Symptom—The user observes a warning dialog appearing which states communications with the server have been lost. Shortly after the appearance of this dialog the session closes.
Condition—If the user has an open session while an EM is being installed (removed) the session will be forcefully closed.
Workaround—The solution to this problem lies with the Systems Administration team. A procedure needs to be put in place which ensures CEMF sessions are closed prior to the installation or removal of an EM.
Shouldn't be able to deploy snmpManageable objects without ipaddr
Symptom—SNMP Manageable objects which are deployed using the objectFileParser do not appear in the Network view.
Conditions—If IP addressable objects (which includes SNMP Manageable) are deployed using the objectFileParser but their IP address attribute is not setup within the object specifications file then the deployed objects will not appear in the Network view.
Workaround—Delete the incorrectly deployed objects, correct their objectSpecifications file, and re-deploy the objects using the objectFileParser.
Alarm propagation is wrong in mapViewer after reparenting objects
Symptom—In the map viewer application, the alarm propagation circle is grey when it should be green or it is green when it should be grey.
Condition—This problem will occur when objects are reparented either from a propagating view to a non-propagating view or from a non-propagating view to a propagating view.
Workaround—The problem can be resolved by reopening the map viewer application.
User can type in EM dialog text boxes when dialog is busied on
Symptom—The user can enter text into an EM dialog whilst the cursor indicates the dialog is busy (i.e. the cursor appears as a small clock).
Condition—This occurs when the user performs an operation that leads to the dialog becoming busy. For example, when choosing save, a dialog box will be displayed asking you to confirm. At this point, even though the original dialog correctly appears as busy, you are able to modify fields within it.
Workaround—There is no workaround to this problem. The user should refrain from interacting with the dialog while it is displayed as busy.
Map Viewer not updating with newly deployed objects
Symptom—On deploying objects the user observes
a. The right hand side of the MapViewer (ie. the map) does not display the newly deployed objects.
b. The left hand side (the hierarchy view) of the MapViewer does display the newly deployed objects.
Condition—This situation occurs if the machine being used as the CEMF manager server runs so low on disk space that the map database cannot update itself by adding nodes for newly deployed objects.
a. Free up some disk space.
b. For transient maps :- Closing the MapViewer, and launching a new MapViewer will display a map consistent with the system.
c. For persistent maps :- Identify the objects which are not present in the Network view ( by manual comparison of left hand hierarchy view with right hand map), delete these objects and re-deploy them.
Modal dialogs end up behind parent window
Symptom—Sometimes a dialog will appear to have frozen with the busy cursor displayed, as if the dialog is waiting to do something.
Condition—This occurs when a dialog has opened a further dialog and become busy itself until the new dialog is dealt with. It is possible that this new dialog can be hidden behind the original parent dialog giving the impression that the original dialog is frozen, whereas it is actually waiting for you to do something with the (hidden) new dialog.
For Example, launch the EventBrowser from the Launchpad. EventBrowser opens with QueryEditor on top. Click on the title bar of the EventBrowser window. The QueryEditor goes behind the EventBrowser and the EventBrowser remains busied on.
Workaround—There is no workaround. However, if you minimize or move the busy dialog you should find the hidden dialog.
Application screens do not show the server they are connected to.
Symptom—Looking at an application screen you cannot tell which CEMF manager server the application is connected to.
Condition—If the user opens the same application from multiple sessions which in turn are connected to multiple CEMF manager servers, the user cannot tell to which CEMF manager server an application is connected. It is only the launch pad which shows the CEMF manager server the session belongs to and the name of the session user.
Workaround—There is a Window menu on every screen. The user will be able to use this to navigate to the Launch Pad for this session to check the CEMF manager server they are logged into.
Startup errors in partitioningTool & sessionMgrServer log files.
Symptom—The partitioningTool log file contains :-general : ERROR EventChannelManager : multiple creations attempted
The sessionMgrServer log file contains :-Session : ERROR sysmgrEventHandler.cc:82 SysmgrEventHandler::openFeedResultFailed to open event feed for sysmgr channel
Condition—Both of these error messages are logged during startup of CEMF manager server.
Workaround—There is no workaround. These messages can safely be ignored.
Rename object in MapViewer displays error even though successful
Symptom—When renaming an object within the Physical view in the MapViewer you may receive an error messages stating that the rename operation has failed, yet the object will still have been successfully renamed.
Condition—As an example, consider the following deployment:
Should you attempt to rename the SomeName1 object to SomeName2 within the
Physical view you will be returned an error explaining that a non-unique name was specified. However, underneath the Physical:/Bay-1/ the object will have been successfully renamed to SomeName2.
Workaround—There is no workaround for this problem. The object has been successfully renamed and the error message should be ignored.
Sub-dialogs do not multi-select when launched from parent
Symptom—Sub-dialog does not select all objects selected prior to launching.
Conditions—This happens when objects are multi-selected on a parent dialog and another dialog is launched from the same parent dialog.
Workaround—No workaround is currently available for this problem.
Its possible to deploy SNMP agent without defining community strs
Symptom—User can deploy an SNMP manageable object leaving the SNMP community strings as undefined.
Condition—User initiates deployment of a generic object by selecting Deployment -> Deploy Generic Objects ... from an objects service menu. This brings up the list of generic templates. User then selects from SNMP Agent or SNMP-2 Agent SNMP Proxied Device
A subsequent deployment wizard screen prompts user for SNMP community string. User can change this value to undefined (ie. delete the default string leaving field blank). User is not forced to enter a value for the community strings. User is then able to deploy the SNMP object.
Workaround—Following deployment of SNMP agent user can change the community string value using Object Configuration dialog. This can be accessed by right clicking on the object and selecting Tools -> Open Object Configuration. On Object Configuration dialog, select either "Community Strings (SNMPv1)" or "Community Strings (SNMPv2)" from "Object Types" menu. These selections bring up the community tabs which allow the community string to be entered.
Note Object Configuration dialog should be used with caution. It provides the user with the capability of changing how devices behave.
Further problem description
If the user attempts to access SNMP object using Object Configuration, the Object Configuration dialog will display "Error" for all its attributes. This indicates the fetching of the attributes from the device has failed.
Popup menu not available for ObjectGroup on Client machine
Symptom—Sometimes when right-clicking on the objectGroups item within Object Group Manager the resultant menu is empty, and only displays the menu title. "Create Object Group" and "Create Folder" are expected to appear, but they do not.
Condition—This can happen on an installation where there are several Element Managers installed, and relates to timing. It can occur on both CEMF client and manager server installations, but may be more likely on a client.
Workaround—The following steps should be followed to work around this problem -
a. Close your current session
b. Start a new session, and open the MapViewer
c. From any object within the MapViewer choose the Get object group membership option from the Tools menu.
d. You can now start the Object Group Manager from the launchpad (the MapViewer can be closed if no longer required.)
Event Groups Application view object count incorrect post delete
Symptom—When the user deletes an event group the event group hierarchy object count does not update. The object count will remain as it was before the deletion.
Condition—This occurs whenever the user deletes an event group.
Workaround—Closing and then relaunching the Event Groups Application. This causes Event Groups Application to correctly refresh its event group view.
Deploy Wiz. handling of 64bit Integers incorrect
Symptom—When a user attempts to deploy an object an error message similar to following is displayed by the deployment wizard :-Parse ERRORDetails :-Parsing file :- /opt/cemf/config/templates/myEM.myClassError description :- DEFAULT expression is incompatible with the parameter type which as been specified.Near line:- 29Last text parsed :- END_PARAMETER
Condition—If a deployment template prompts for a 64 bit integer using following :-
PROMPT "Please enter my64Integer: "
template will fail parsing. When the user selects the template which contains this prompt the deployment wizard will fail to parse the template with an error message similar to above displayed in its results screen. This parse failure will be seen when a 64 bit integer is defaulted in a parameter prompt specification (as above).
Workaround—Remove the DEFAULT line. Above would be changed to :-
PROMPT "Please enter my64Integer: "
Dynamic Update Toggle in Obj Conf doesnt work
Symptom—When the object Configuration dialog is displayed for an object which is in a polling state it should be possible to choose whether the displayed attributes are automatically updated by using the dynamic update on/off menu item. This menu option does not work correctly and displayed attributes will always be updated automatically.
Condition—This problem occurs when the object configuration dialog is open on an object which is being polled.
Workaround—No workaround currently identified.
EM screen exit if screen closed before object list population end
Symptom—Some EM dialogs that use Object Lists which are populated when the Dialog is launched may exit unexpectedly when that particular dialog is closed.
Condition—This occurs when a user launches a dialog and then immediately closes it by double clicking on the top left of the Window, before the Dialog has been fully populated.
Workaround—There is no workaround.
Open Caveats (Applications)
AUtoDiscovery does not always log expected error messages
Symptom— The expected error messages are not logged by the auto-discovery application.
Condition— This problem happens when using the Discovery Scheduler and the user enters negative or invalid numbers in the discoverySchedules file.
Workaround— There is currently no workaround for this problem.
Wrongly configured Solaris hostname on client hangs session startup
Symptom— If the Solaris hostname of a Cisco EMF client is wrongly configured, then the CEMF session can hang, i.e. the splash screen and login will open but freeze after the username and password have been entered.
Condition— This is due to the clients machine name being mismatched with its name in DNS.
On the client machine, hostame will return 'nameA' but on the Manager, doing an nslookup for 'nameA' fails. In DNS, the client machine is called 'nameB'.
Workaround— This problem can be resolved by changing the files:/etc/hostname.hme0, /etc/hosts and /opt/cemf/config/env/avCore.sh to use 'nameB'.
SNMP comm strings always entrd in V2 fields of SNMP Mgmt screen
Symptom— SNMP Community Strings always appear in the SNMP V2 fields of the SNMP Management, no matter which version of SNMP the user has selected.
Condition— This problem is seen when the user enters an SNMP Community string in the Deployment Wizard.
Workaround— No workaround is currently available for this problem.
After use cdm to delete FCAP,remove&insert back,cdm does not disc
Symptom— The icon representing an object is not displayed.
Condition—This problem occurs after an object has been removed and re-inserted into its container and the object is discovered automatically.
Workaround— Manually deploy the object instead of waiting for the device to automatically deploy when traps are received due to the insertion of an object.
Autodiscover 1000s of devices makes system unusable
Symptom— If the user attempts to discover a network with many thousands of possible devices then the CEMF system will be unusable.
Condition— The Auto Discovery application within CEMF allows the user to set up a range as large as he requires. If the range is sufficiently large, then the performance of CEMF will degrade.
Workaround— The user should only attempt a discovery of a manageable size of network.
If LaunchPad exits unexpectedly, the session will not be closed
Symptom— In the unusual circumstance that the Launch Pad were to close unexpectedly then the other applications will remain open.
Condition— The open applications will continue to function however, since the Launch Pad is the main way to navigate in CEMF, then applications that can only be launched from the Launch Pad and are not already open will not be able to be launched.
Also, the licence that the current session is using will still be in use.
Workaround— The workaround to free up the licence in this unusual occasion would be to run the following command :
CEMFROOT/bin/sysmgrClient -r 20000
This will stop the relevant processes, including any running applications and will therefore free up the licence that is currently in use.
It should then be followed by running the command :
CEMFROOT/bin/sysmgrClient -r 100000
This will return CEMF to the appropriate run level and normal operation can be continued.
EvntBrwsr: deleted objects results in incorrect display of alarms
Symptom— When viewing Events in the Event Browser Application, there is a rare condition, that makes it possible for the Event Browser to display incorrect full object names for some Events, or display Events which do not match a query on "Object Scope".
Condition— This is due to the fact that the Event Browser does not update with respect to descendant objects when their parent objects are deleted. In addition the Event Browser does not update when objects are renamed or reparented. This can cause the following problems:
A. In the case of an object being renamed, the new name will not take effect in any of the open Event Browsers displaying this object or descendants of this object.
B. In the case when the Event Browser Application is opened with an "Object Scope" query, (e.g. launched from an object in the Map Viewer), and that object has descendant objects with Events raised against them. The Event Browser displays all of the Events currently on the object and it's descendants.
In such a scenario the above problem can manifest itself in the following ways:
(i) If any object which matches the Event Browsers "Object Scope" query is deleted then its own Events are deleted but it's descendent object's Events are not. If this occurs then the Event Browser will continue to display the Events on the child objects even though they no longer match the Event Browser's "Object Scope" query.
(ii) If any object which matches the Event Browser's "Object Scope" query is reparented or its parent relationship removed (using the Map Viewer Application) then that object's Events and any of it's descendent object's Events will remain in the Event Browser. This is true, even if the Events no longer satisfy the Event Browser's "Object Scope" query.
(iii) If the "Add Object(s) to" or "Reparent Object(s)" services in the Map Viewer cause any object with Events to match an already open Event Browser's "Object Scope" query, the Event Browser will not update to the new Events which now match its current query.
Workaround— If any of these problems occur, the user can close the current Event Browser and open a new one with the same Query. This will force the query to be re-run and ensure that we get all of the current correct Object Names and Events which match the query.
Connection lost to CEMF when autodiscovering
Symptom— Discovering network devices causes the process to exit unexpectedly.
Condition— This problem occurs when certain subnet masks are used to discover network devices.
Workaround— There is currently no workaround for this problem.
eventBrowser cores when opening it...
Symptom— The Event Browser application exits unexpectedly upon startup.
Condition— This problem occurs when the user attempts to launch more than one Event Browser dialog from the same CEMF session in quick succession. The second Event Browser must be launched before the first one has finished initialising.
1. Avoid starting Event Browser dialogs in quick succession (short delay is sufficient)
2. If the problem occurs then restart the Event Browser.
Should not be able to remove parent relationship of generic object
Symptom—If a CEMF object is created, such as a chassis and it's parent relationship is removed, then the object subsequently cannot be seen in any view, and thus is effectively invisible to the user.
Similarly, if a CEMF object is deleted and it has descendents then, if those descendents are not located in any other view, then they will also be invisible to the user.
Condition— Consider the following containments, assuming the objects are only in the views specified:
If the user selects Region-1 in the Map Viewer, then right-clicking on the "Deployment->Delete Objects ..." menu option , they will be informed they are deleting 1 object and asked to confirm this. In doing this, the user will no longer see the following objects in the Physical view : Site-1, Shelf-1 and Chassis-1 but they will still see them in the ComponentManaged view. However, if the Site-1 is then selected and deleted then the Shelf-1 and Chassis-1 objects will never be able to be viewed.
Workaround— No workaround currently identified.
technolgy views not being removed when physical views removed
Symptom— When the user selects an object and requests to delete it, then CEMF will only delete that object.
Condition— If the user selects to delete an object that has children in that view, then the child objects may still be present in other views, or may not be seen in any other view but will still exist within CEMF.
Workaround— The only workaround is to select all the objects that you want to delete and then request to delete them.
Objectgui core dump on object deployment
Symptom— The Map Viewer exits unexpectedly.
Condition— This may happen when deploying objects.
Workaround— There is currently no workaround.
Race conditions in ObjectGui. DA vs Events. Grey smartie.
Symptom— The mapViewer displays a grey propagated status and no plus sign to indicate that a tree (object) view has children.
Condition— This problem happens when the system is very busy and the children of a tree view are being changed rapidly, whilst the tree view is being expanded at the same time. For example, when the system is very busy and objects are being deployed under a particular tree view whilst that view is being expanded.
Workaround— Close and re-open the viewer.
SOAKtest: EventQueryEditor launch from launchpad takes 15secs+
Symptom— Launch time of Event Browser increases when CEMF servers are busy with a complex operation.
Condition— Install CEMF and set up a large system. Create traps in the system by generating a sustained trap rate. Leave the system to run for at least a day, then perform a complex operation that will cause the system to become very busy. The first time launch of the Query Editor from an Event Browser, can take over 15 seconds.
Workaround— No workaround currently identified.
alarm count at bottom of screen is misleading
Symptom— In the Event Browser Application, in "Automatic Update Mode", on rare occasions the Event Group - Event Count (displayed in the Event Browser's status footer) may become out of sync with the actual Event Group count. For example, this can be observed when Event Group count seems to imply:
(i) that we are viewing more Events than exist in the Group (i.e. say "321 of 311").
(ii) that we are viewing less Events than exist in the Group (i.e. say "301 of 311").
Condition— This can occur when the browser is viewing a large number of Events (say around 50,000), and an operation has been performed which adds or removes a large number of Events (say around 5,000).
Workaround— If this situation occurs then pressing the "Refresh" button on the Event Browser Toolbar will refresh the Browser, ensuring that it's Event Count is correct.
cannot view active, unacknowledged alarms
Symptom—The CEMF Event Browser does not allow users to view events that are both active and unacknowledged.
Condition— The CEMF Event Browser allows users to view active and cleared events and also ones that have been acknowledged and unacknowledged. An event can be
–active and acknowledged
–active and unacknowledged
–cleared and acknowledged
–cleared and unacknowledged
The Event Browser cannot be refined to only show either of these four. If the query is refined to be active and unacknowledged then it will show all active events or all unacknowledged events which means it would show all events that were:
–active and acknowledged
–active and unacknowledged
–cleared and unacknowledged
Workaround— No workaround currently identified.
The Event Browser will clearly show which events are active and unacknowledged but the user cannot refine the query to only show such events.
Chassis map doesn't function correctly after Module name-change
Symptom— In the Map Viewer Application, changing the name of a Module on some types of Chassis may lead to that Chassis' Modules being moved in the Map View and possibly obscured behind other modules.
Condition— This only occurs for Chassis in which their depiction in the Map Viewer is as a large picture icon containing its modules within this icon. And is only noticeable when the new name used contains around 20 characters or more.
Workaround— This will not be a problem for these types of Chassis if the user limits the size of any module names, that are renamed.
Assigned NP don't run when TRs breech on COM based attributes?
Symptom— If the user has an Element Manager screen open and right clicks with the mouse on an attribute value, and uses the popup to set up or edit a thresholding regime, then it may not actually check the threshold condition that has been set up.
Condition— There are certain circumstances, with particular CEMF EMSs, that the assigned notification profile will not fire when thresholds are breached. This case is EMS specific - please consult your EMS release note for details.
Workaround— No workaround currently identified.
Open Caveats (Infrastructure)
First time CEMF start takes too long with CDM installed.
Symptom—After installing Cisco EMF and Element Manager (EM) packages, doing a "cemf start" will take a considerable amount of time if no databases already exist for this system.
This problem is also present if a "cemf stop" followed by a "cemf reset" and "cemf start" is performed.
Condition—This will only happen on first time startup, or if a "cemf reset" is performed.
Workaround—The first time that Cisco EMF system is started and after all EM packages have been installed, ensure that a backup is performed - i.e. type the command:
"cemf backup -l <InitDBBackupDirectory>"
This will save a copy of all the initialized databases to the "InitDBBackupDirectory" specified. Ensure that any subsequent backups are not saved to this location.
Should a "cemf reset" be required, simply perform a restore as follows:
"cemf restore -l <InitDBBackupDirectory>"
after the "cemf reset".
Now, perform a "cemf start" and CEMF will start up substantially quicker.
This procedure can also be followed when re-installing the same version of CEMF and the EM packages.
Cant backup after breaking out of objectFileParser
Symptom—Object deployment fails to work after using the objectFileParser utility to create objects from a text file.
Condition—The user has used the utility 'objectFileParser' to create objects from a text file, and has exited the parser during the creation by killing the process or typing CTRL-C.
Workaround—Stop and restart the Cisco EMF server.
restore gives incorrect warnings about EMs not being installed
Symptom—A cemf restore will report that the current system does not have the same EM packages installed as were installed on the backup system. The restore operation completes successfully.
Condition—Element Manager (EM) packages may support two modes of installation:-
- installation with CEMF already running
- installation before CEMF is started
The problem only occurs when an EM package is able to be installed on theCEMF system while the server is not running (check your EM installation documentation to see if this is the case).
If your EM supports this mode of installation, then a backup which is made from this system will report an error if it is restored onto another CEMF system where the EM package was installed with CEMF running.
During the restore operation, a warning will be seen from the command cemf restore , as in the following example:-
> /opt/cemf/bin/cemf restore -t 08-14-2001 -l /myRestoreDir/mybackup
Validating system ...
The installed EMs do not match the installed EMs from the backup system.
<EM name+version> is not installed on the current system.
EMs installed on current system
<list of EM packages>
EMs installed on backup system
<list of EM packages>
Verifying the backup file checksums...
Workaround—Ignore the warning and chose to continue with the restore. Alternatively, make sure that the system being restored to has been installed using the same procedure as the original system from which the backup was made.
sysmgrClient bypasses normal locking processes
Symptom—After use of the 'sysmgrClient' utility, the Cisco EMF system information appears to be inconsistent. In particular, received traps have not been converted to alarms, objects which should
have been added do not exist, or objects which were being removed still exist in the system.
Condition—The user has used the 'sysmgrClient' utility to start and stop Cisco EMF server processes during deployment (object creation/ deletion) operations, or during trap reception.
Workaround—Do not use the process start/stop or run-level functionality of the 'sysmgrClient', except under the instruction of Cisco TAC or engineering personnel.
There is no workaround to recover the missed information if the processes were not running at the time the information was received, or if an in-progress operation was interrupted.
non-default logs directory is left when CEMF is deinstalled
Symptom—The directory for Cisco EMF log files is not removed during deinstallation.
Condition—The user has specified a non-default location for the logs directory while installing CEMF.
Workaround—The directory may be removed manually after deinstallation.
Objects without mandatory attributes should be rejected
Symptom—Objects can be successfully created without setting the value of mandatory attributes.
Condition—This can happen when creating objects using the objectFileParser, or when calling the Cisco EMF APIs directly.
Workaround—Strictly, there is no workaround, although additional care can be taken to ensure that any necessary attribute values are properly set.
Generic Trap mapping is slow for certain types of mapping
Symptom—There is a delay between traps being received from a device and an alarm being raised against that object in Cisco EMF.
Condition—This may happen when the mapping between the traps and Cisco EMF objects is complex. Traps have an IP address which corresponds to the SNMP agent against which the trap has been raised. Information in the trap can then be used to determine if the trap should be mapped to a child object in Cisco EMF.
In general, traps which map to the agent object will be mapped fastest, then traps against children with simple index-based mappings (i.e. every child has an single index value which uniquely represents it), and finally traps which have a rule involving looking up containment information.
Workaround—No workaround currently identified.
License file wont parse if command is run within cemf shell
Symptom—When attempting to parse in the Cisco EMF license file from a UNIX command-line session in which the 'cemf shell' command has been executed, an error is produced and the license file is not parsed.
Condition—This occurs when trying to parse in a license file from within a cemf shell
using the 'cemf license' command.
Workaround—A workaround to the problem is to parse in the license file outwith a cemf shell.
e.g. Open a new terminal
Run the command 'cemf license -file <full path to license file>'
Large number of concurrent CEMF logins fail - server timeouts.
Symptom—Attempts to login to a Cisco EMF server will fail.
Condition—30 or more users attempt to login to the same Cisco EMF server at the same instant. Note that this is not the same as having 30 existing user sessions already logged in.
Workaround—Repeat the login until it succeeds - the issue is caused by the simultaneous login attempts.
Backup lock-out dialogs do not provide user with clear explanation
Symptom—While a backup is occurring, GUI operations may take a long time or fail without informing the user that a backup is in progress. This will be seen on both client and server-side GUIs.
Condition—A backup is in progress on the Cisco EMF server.
Workaround—Try to schedule backup operations at times when few GUI operations are being carried out.
User notification required when deployment not allowed by backup.
Symptom—While a backup is occurring operations may take a long time or fail without informing the user that a backup is in progress.
Condition—A backup is in progress.
Workaround—No workaround currently available.
corba event channel will not work after first time start
Symptom—No events are received on Corba event channels.
Condition—First-time start-up of Cisco EMF server.
Workaround—After first-time start-up of the Cisco EMF server has completed, stop and restart the CEMF server.
Network view not getting updated while many objects are added
Symptom—Using the map viewer, some objects which were just deployed do not appear in the view after the deployment has completed.
Condition—A user has a map viewer dialog open during a deployment operation which is adding a large number of objects to the system (in this case, 2000 objects at once).
The views on the left of the map viewer dialog do not appear to show all the new deployed objects, although the deployment appears to complete successfully.
Workaround—If the problem is seen, close and re-open any map viewer dialogs after the deployment operation. Alternatively, try to deploy fewer objects at one time if possible.
Headline : PSR reach exception in localDBServer (400 chassis databuild)
Symptom—The sysmgr.log log file contains an error message from the localDBServer process. The error message is from ObjectStore, and states that the process has 'exceeded its PSR reach'.
Condition—The CEMF system is managing a large number of chassis (in this case, 400), and the user tries to carry out an operation involving many objects, such as commissioning 50 chassis at once.
Workaround—No workaround available.
Removing patch doesn't roll back shared libs
Symptom—After backing out a previously-installed patch, CEMF binary and shared library files may remain as the patched versions.
Condition—Installing a CEMF patch package, then later backing it out. Under certain circumstances, the files which were updated by the patch installation process do not revert back to their original versions if the patch is subsequently backed out.
Workaround—There is currently no workaround.
eventChannelHost size grows after network outage with multi-users
Symptom—The process 'eventChannelHost' uses more and more memory over time.
Condition—A CEMF system which is managing a large number of chassis (in this case over 200) and has many user sessions running, and network connectivity has been lost to a substantial part of the devices on the network.
Workaround—No workaround available.
Backwards compatibility issue found with ATM QoS Profiles.
Symptom—This occurs when code built against CEMF version 3.1 is rerun against CEMF version 3.2 (Odin). The ProfileMonitor class contains virtual methods which will not be called unless the code is rebuilt.
Condition—Attempting to apply a profile can fail, because the underlying system cannot retrieve the profile.
Condition—The workaround is to recompile any code which uses the ProfileMonitor API.
Backwards compatibility issue found with ATM Upload.
Symptom—When an element manager which was compiled for Cisco EMF 3.1 is run on Cisco EMF 3.2 system, query-related functionality may not appear to give the correct results.
Condition—A query is being performed which checks for the presence of a particular attribute or attributes against one or more objects.
Workaround—If the element manager is recompiled for Cisco EMF 3.2, this problem will not occur.
Open Caveats (Between Release and 1st October 2001)
No security on controller operations
Symptom—A user can perform operations on their machine that should only be available to users with root permission, even if that user doesn't have root permission.
carry out root operations via controller actions, even although they do not have root privileges.
Conditions—This occurs when the user creates actions that perform root operations.
Workaround—There is currently no workaround.
Install script say succesfull when errors occur
Symptom—The "cemf load" command does not return an error code if processes fail to start during installation.
Conditions—Occurs when an EM is installed, but one of the processes cannot be started.
Workaround—The "<CEMF_ROOT>/bin/cemf status" command can be used to ascertain the status of all process that are supposed to be running. The output from this command can be used to determine which process failed to start.
Object Deletion Needs Initial User Feedback
Symptom—After the user initiates delete operation on a large number of objects the Deployment Wizard appears to hang.
Conditions—The user selects a set of objects to be deleted and invokes the delete option from the MapViewer menu "Deployment" -> "Delete Objects". This starts the delete operation. The actual set of objects deleted can automatically expand to a greater number than the user selected (In some cases reaching 50, 000 objects. Number is technology specific). This delete operation can then take a considerable amount of time during which the user receives no feedback.
Workaround—User should attempt to delete objects in as small a number as possible.
GUI Not Updated Following Object Deletion
Symptom—After initiating the deletion of objects via the Deployment Wizard the Deployment Wizard GUI remains busied out.
Conditions—This problem arises when a large number of objects are deleted. User selects set of objects to delete and initiates the deletion via the Deployment Wizard. Objects are automatically added to the set of objects to be deleted. If the total set of objects to be deleted is sufficiently large the deletion operation will result in the Deployment Wizard remaining busied out. Some of the objects (and perhaps all) may have been successfully deleted.
Workaround—User to delete small sets of objects.
sysmgr fails to handle process failures on cemf start up
Symptom—No errors are reported to the screen when a process failed to start after EM installation.
Conditions—Occurs when an EM is installed, but one of the processes cannot be started.
Workaround—The "<CEMF_ROOT>/bin/cemf status" command can be used to ascertain the status of all process that are supposed to be running. The output from this command can be used to determine which process failed to start.
eventChannelHost grows enourmously
Symptom—The Cisco EMF 'eventChannelHost' process grows to a large size.
Conditions—Many attributes are being polled, and their values databased for later use
by the Performance Manager.
Workaround—There are two possible workarounds:
1. Reduce the polling frequency of attributes being polled
2. Do not database the values of as many attributes. This can be achieved
by changing the history regimes for the EMS.
Generic Objects Are Not Deleted
Symptom—Child objects are not deleted upon deletion of their parent.
Conditions—Happens when a generic (ie non EM specific) object with children is deleted.
Workaround—The effects of having these orphan objects remaining in the system will not be noticeable to the end user. However, if necessary, the child objects can be explicitly deleted via the GUI prior to deletion of the parent object. So, when deleting generic objects, the user should firstly manually delete any generic object children of the object that is to be deleted.
kill coordinator - sysMgr restarts it - looses all participants
Symptom—if coordinator process dies/gets killed the sysMgr process will restart it, but there will be no more deployments possible, as the coordinator looses all its participants and has no mechanism to get them back.
Workaround—cemf stop followed by cemf start clears the error condition.
Resolved Between Cisco EMF v3.1 and This Release
•CSCat06835—copy paste config saves automatically
•CSCat14758—New EventBrowser window launched for the same object
•CSCat15305—Coredump occurs on closing the ObjectGroupEditor window
•CSCat15443—Wrong screens appear when an old Acc. Spec is copied to a new Acc. Spec
•CSCat15492—Refresh problem during un-acknowledging the events
•CSCat15617—DecommissionTask::enterGroup wrongly consumes incoming ObjAttrList.
•CSCat16486—[CSCdp86505] manually clearing alarm creates two entries in event histo
•CSCat16584—Misleading message in case of Get Object Group Membership
•CSCat16596—Object Group Manager Should not accept illegal characters at GUI level
•CSCat16656—Core launching session while processes stopped
•CSCat16991—ObjectUtils assumes attr not writeable if adeAccess not set
•CSCat17139—Debugging Deployment Problems
•CSCat17203—Updating Table Matrix attribs Scrambles
•CSCat17258—attribute value cache persists between runs of nbinterface
•CSCat17510—[CSCdr07902] Out-of-range value in wizard dialog offer no messages
•CSCat17515—Changing password with different levels of permission does not work
•CSCat17594—[CSCdp94104] discoverySchedule interval ignored if cemf is restarted.
•CSCat17621—Event Browser: need ability to view alarms on children
•CSCat17628—Open Map for Object ... can we put this back!
•CSCat17750—Rename Object Dialog does not show all instances after reparenting
•CSCat17754—Map View does not show the reparented objects after reboot.
•CSCat17826—User unable to change own password
•CSCat18240—removal of feature list after upgrade
•CSCat18343—add description to maual clearing alarms
•CSCat18366—Closing login window via CDE close causes segmentation fault error
•CSCat18427—per mgr: Refresh button obscured
•CSCat18505—Query editor not updating when a map object is deleted.
•CSCat18639—AHC exiting due to ObjectStore exception—Address space is full
•CSCat18763—Need to bulk up the execution of notifications that require substitutio
•CSCat18847—first opening the veiwer the alarms dont appear on the objects
•CSCat18934—Alarms raised at container level without object being present under it
•CSCat18936—COREDUMP attributeHistor while purging DBs—DEP
•CSCat18942—Support of multiple IP addresses on CEMF server
•CSCat18948—Problem With setResult and vectors.
•CSCat18992—SimpleAttributeProcessor FMR problem
•CSCat19030—System appears to run up even tho 2 processes crashed
•CSCat19075—Free index at the end of a set request will cause the SNMP DR to core d
•CSCat19077—[CSCdr61113] Install Patch 4 ontop of 3 wouldnt remove later on.
•CSCat19213—EventBrowser does not startup from launch pad under wierd circumstance
•CSCat19229—propagation of alarms on regions only occur after the second alarm
•CSCat19533—OGM wont display path when object only in EM view
•CSCat19538—enum type in varbind shows integer value instead of text
•CSCat19546—Can install manager & client on same machine using ./cemfinstall -c
•CSCat19568—ObjectUtilsTestRig getObjectDetailsAsync core dumps.
•CSCat19642—Line card labels are overlapping
•CSCat19645—Useful for dbms to read in common files first then app specific
•CSCat19695—Attribute History Server too slow when purging large data sets
•CSCat19696—Object Group Manager hogs the processor when a query on all objects-DEP
•CSCat19743—EM Dialogs allow closure while attributes are unsaved
•CSCat19800—os_marker release function doesnt work in nested transaction
•CSCat19815—Containment Server stores an invalid object
•CSCat19844—Trap Mapping broken because of AttrString/AttrOctet comparison
•CSCat19845—[CSCdr74005] cemfinstall does not return error code when install fails
•CSCat19854—Cant retrieve the clearing time for a cleared event
•CSCat19888—Patch script only need to make up CEMF as of patch 06
•CSCat19961—High CPU usage by attributeHistoryCollector during sub-rack discovery
•CSCat20041—highest severity info field in event browser not always up-to-date
•CSCat20114—[CSCdr76957] localDBServer crashed
•CSCat20116—[CSCdr63200] snmpv2c traps are not being forwarded
•CSCat20166—many ERRORs seen once CEMF had been started
•CSCat20226—Comms gateway infinite loops when accept() fails
•CSCat20269—[CSCdr78908] sysmgr exited when I tried to restart controller
•CSCat20284—No error message if rename object fails
•CSCat20299—CGM: SCAL: Can get situation where prop is broken in the viewer
•CSCat20346—EM views not being updated on AV on EM upgrade
•CSCat20382—[CSCdr90139] Deletion does not fail if same OG exists in context twice
•CSCat20389—[CSCdr92254] ObjectGroup.moveObjects should move all or no objects
•CSCat20391—Access Manager allows the user to delete the other users.
•CSCat20423—No way for a user to point his client to a new server with update scrip
•CSCat20424—Name validation in og and cont. servers should semantically identical
•CSCat20434—Access Manager crashes when User Group value is large
•CSCat20484—System uses too many TCP connections between processes
•CSCat20496—[CSCdr84769] Core dump after deleting chassis and closing Deploy Wizar
•CSCat20510—scoped alarm query for cleared alarms returns all alarms within scope
•CSCat20572—SNMP DR ini file has incorrect variable name commented
•CSCat20618—LicenseMgr class crashes when demo license missing.
•CSCat20624—virtual attribute server should have large DA timeout
•CSCat20695—ObjectGroupApp cores if you try to delete an EM perfGroup
•CSCat20699—Possible core dump if you delete an alarm group while you edit it
•CSCat20773—No progress dialog in Event B when you launch it from object.
•CSCat20779—Restore form tape not working
•CSCat20784—Table retreival broken with free index of MAC address
•CSCat20786—wrong iostream seek call used
•CSCat20799—ObjectListViewer displays objs multiple times under certain conditions.
•CSCat20806—datalook get (..) rows x on mo (..) broken
•CSCat20863—[CSCdr82807] Scheduled dialogs dont accept US time format
•CSCat20871—Event Browser does not inform when auto update off and need to refresh
•CSCat20879—[CSCdr22246] Image not removed from chassis view after module is delete
•CSCat20884—[CSCdr97843] CDM allows us to create site name with no characters(empty
•CSCat20892—[CSCdr57330] Core dump while exiting from Access Manager window
•CSCat20893—[CSCdp86813] Wrong event description for clearing event in Event Histor
•CSCat20896—[CSCdr23653] ENUM overrides not used in deployment wizard.
•CSCat20928—[CSCdr55707] server specific scripts should not be allowed on client
•CSCat20930—[CSCdr59277] dialog hangs if clearing event button is pressed for norma
•CSCat20934—[CSCdr50806] attributeHistoryServer exiting/restaring everyday due to
•CSCat21041—[CSCdr69348] Event Browser does not close even if CEMF window is closed
•CSCat21043—[CSCdr82780] Error: ObjectFileParer: create/delete failure after -upgra
•CSCat21046—The ./cemf help full command is not being translated correctly.
•CSCat21081—GUI sets attributes which havent changed since last set
•CSCat21116—2 scheduled discoveries within same address range—neither takes place
•CSCat21130—Bogus files in /var/sadm/pkg causes showrev to fail
•CSCat21132—Object Gui logs misleading messages after object deletion
•CSCat21133—subs not made in config files when CEMF is restored on another machine
•CSCat21134—Performance Manager sometimes misses values at start of range
•CSCat21143—Edited query not saved for query populated Object Group
•CSCat21149—Event Browser problem after restore
•CSCat21177—Can handle variable length string indices
•CSCat21187—Perf Manager data not displayed until polling is actioned on new object
•CSCat21193—Event browser throughput problems with >3 users
•CSCat21229—reParent event not raised if re-parented to root
•CSCat21235—Event Browser User filter on cleared alarms not working.
•CSCat21248—clearCorrelationServer showing high CPU usage when all alarms cleared
•CSCat21261—encoding of strings to OIDs flawed
•CSCat21262—Logger logs when shouldnt: logfiles fill with junk, making debug harde
•CSCat21274—Customer core files are often unusable
•CSCat21291—A performant alarm API or helper class would be useful
•CSCat21341—Edited event group name can contain invalid characters
•CSCat21346—Cannot create event groups on the event browser
•CSCat21348—cemf restore does not restore & does not return to the command prompt
•CSCat21357—Dynamic Object Mapping containment cache maps traps to incor. obj
•CSCat21366—attributeHistoryServer terminating due to Cache Manager disappearing
•CSCat21398—AGQueryController sometimes doesnt retrieve the required attributes
•CSCds27785—The CommsMessageBuffer destructor fails to close connection.
•CSCds29039—unixManager core dumping
•CSCds29938—Admin neither change own password nor users password
•CSCds29967—Large tables on EM screens slow to update
•CSCds30827—Removing final n.p. from trig.cond. resets rather than stops it
•CSCds30842—Event Browser hogging CPU—have to kill the process to get out
•CSCds30923—Input field name Access Specification is lopped off.
•CSCds30967—Trapmapper constructor code duplicated.
•CSCds30969—ClearCorrelation broken under Patch 8
•CSCds31860—HierarchyTreePolicy::onSelected is called extra times (3.1-D9)
•CSCds31953—objectgroup.partspec renameFolderService has RWA permission
•CSCds31975—key information should be cached by the SNMP DR
•CSCds32031—Event Details screen (notifApp) displays Warning ! (3.1-D6)
•CSCds32136—Event Browser displays 0 of X Events in status footer.
•CSCds32947—DepInitiatorHelper hangs deployment context
•CSCds33013—Purify errors in notificationServer
•CSCds33994—Class Pallette doesnt work properly
•CSCds33999—Access Manager Admin user locked out when permissions are RW only
•CSCds34882—clear correlation clears the last incoming alarm
•CSCds34885—Viewer Smartie goes GREY after rename/reparent functions.
•CSCds34977—Event History not working when Event Browser is opened from an EG
•CSCds35147—Not able to successfully keep 6100 commissioned (CSCds09922)
•CSCds35786—OGServer fails to callback on async operations
•CSCds35835—Event Browser does not display events added to top or bottom.
•CSCds35838—Event Browser displays No Description Available by default.
•CSCds35846—Expanding Physical view creates different OGM queries?
•CSCds35889—Core Dumps in Object Groups when an object is pasted in another
•CSCds36796—ensure that NEI functionality in 3.1 matches that in 3.0.4
•CSCds36821—No message to user that acking alarm does not work during backup
•CSCds36865—abstractionServer crashing after prolonged use
•CSCds37813—Event Browser does not refresh when events are cleared.
•CSCds37913—188.8.131.52.0.5 Incorrect alarm count in Event Browser
•CSCds37936—OG partspec file has incorrect features for ObjectGroups-View
•CSCds37984—Backup/restore can fail
•CSCds38013—Require an AsyncDRepPerfTestRig.
•CSCds38292—Map Viewer does not support Chassis View with alarm propagation
•CSCds38442—Dialogs do not refresh after add/delete entry in table.
•CSCds38488—Pop up window is hidden behind launchpad during login.
•CSCds38496—&menuMore list item at the bottom of lrg svc prof lists incorrect
•CSCds38977—Spurious error message when starting session on non-root client.
•CSCds39015—ENTITY traps do not get processed correctly
•CSCds39017—Outstanding backup issues
•CSCds39763—no information is logged on screen or in log files during backup
•CSCds39769—Display Full Objectname menu option clears the severity info
•CSCds39839—Changes will be applied to the appFramework for multiple managers
•CSCds39906—One SCM server install—comm/decomm noop and autodisc noop.
•CSCds39920—Sub-rack discovery fails when backup is running/started.
•CSCds40451—OGManager requires excess ObjectStore cache
•CSCds40700—StrListEntry::compare core dump
•CSCds40725—restore from tape fails if local backup dir not present
•CSCds40743—unknown normal alarms found with weird clearing details
•CSCds40792—Auto update in event browser not performing correctly
•CSCds40809—Clear Correlation uses User instead of network in clearing method
•CSCds40891—SNMP DR: Logging of SNMP errors incorrect and not comprehensive
•CSCds41493—MapViewer sometimes hangs when deleting objects
•CSCds41701—Agent Poller does not update Agent data as new packages are loade
•CSCds41772—second system folder created when P09-2 is installed
•CSCds41834—Event Browser orders events incorrectly upon opening.
•CSCds41840—MibManager and mibParser parse time and memory footprint
•CSCds41854—very slow serial controller startup
•CSCds41867—OCDManager causes system deadlock during startup
•CSCds42095—Need support for more frequent backups
•CSCds42725—Auto Discovery re-discovers some devices
•CSCds42732—Spurious error message Unexpected Controller state—Idle
•CSCds42781—objectTypeFileParser cant parser objectTypes in random order
•CSCds43114—OGmanager doesnt store number of segments persistently
•CSCds43924—CSRoot uses inefficient segment lookup
•CSCds45665—Backup does not report an error when disk space is full.
•CSCds46727—discoverySchedules file missed from CSCds42725 fix.
•CSCds46775—AGManager leaks creation contexts
•CSCds46816—OS exception when creating named transient AG
•CSCds46859—autoD failing to discover objects in some circumstances
•CSCds46900—Event Browser takes long time to acknowledge/unacknowledge events
•CSCds46983—ObjectIdInfo:adeObjectIdName is completely broken
•CSCds47542—Need easy way to remove objectDefs and containment specs
•CSCds47850—In Autodiscovery objects with no IP add. show subnet masks
•CSCds48015—Auto Discovery hopping broken
•CSCds48511—severityServer process is not needed
•CSCds49886—attributeHistoryServer impacts performance creating summary info
•CSCds50436—State manager requires merge from CEMF 3.1
•CSCds50543—objectFileParser requires merge from CEMF 3.1
•CSCds50555—The metadata subsystem needs a merge from CEMF 3.1 to 3.0.4
•CSCds50565—Participation needs merge from 3.5 back to 3.0.4.
•CSCds50920—Toshiba P.C. Reflection X session No Perf Mgr
•CSCds50965—Unselectable items in the hierarchy are not readable
•CSCds51063—cemf backup fails if CEMF manager is not running.
•CSCds51527—asyncSnmpDrep core dumps
•CSCds53187—SNMP set has incorrectly inserted string len. before index
•CSCds53872—restore causes manager to go into an uninitialized backup state
•CSCds53992—Controller is not passing failed set error codes to Manager
•CSCds54140—genericObjects containment tree should not be propagating
•CSCds54526—abstractionServer brings system to its knees for hours
•CSCds55011—When right clicked on the map, objectGUI becomes too busy and sys
•CSCds55167—handling of ContainmentServer return codes broken in QueryServer.
•CSCds55988—wndws left open after abrupt srvr/mgr take down. coredumps later
•CSCds56081—Alarms sometimes fail to clear in event browser
•CSCds56091—Need to be able to tell object list to stop looking after match
•CSCds56195—Problems restoring from backups created on different machine
•CSCds56213—Agent Poller code review of CSCds41701—amendments required
•CSCds57080—Performance manager printing options confusing.
•CSCds57144—PartitioningManager may set feature availability incorrectly
•CSCds57806—Default message in DefaultAction is incorrect
•CSCds57811—Message changing functionality in DefaultAction has been removed
•CSCds57907—configServer tries to use nonexistent ContainmentRepository
•CSCds58993—objectTypeFileParser -c option does not report errors.
•CSCds59603—Client install causes server mib parsing
•CSCds60034—#includeDir ini file feature not robust
•CSCds60474—MibDependencyMgr doesnt handle different Mib files from EMs
•CSCds60807—Processes fail to allocate new port if bind fails
•CSCds60971—Insufficient information on Save failures in EMs
•CSCds61245—false error message in controller log when processing traps
•CSCds62889—OG Server reverses valid contexts on deletion
•CSCds62904—asyncSNMPDatarepository process core dumps on chassis commission
•CSCds63219—A network with invalid IP address is allowed to create
•CSCds63969—agServer process size grows to consume memory & swap
•CSCds64009—Wrongly constructed MDVAF in virtualAttributeServer
•CSCds64962—menus inconsistent for multi selections in the event browser
•CSCds65068—User environment can cause RAWFS problems
•CSCds65968—SNMP DR default outstanding requests limit too small
•CSCds66965—Need to be able to specify tab order on EM dialog
•CSCds66988—Error messages after EM upgrade
•CSCds67010—Auto discovery puts device in two networks
•CSCds67951—Progress dialog window in EB stays open after query is run
•CSCds67972—Deployment changes to meet 3.1.1 deploy requirements (ENG-84633)
•CSCds68664—AbstractionServer slows down deployment
•CSCds69206—need to disable labels on a per-object-per-map basis
•CSCds70261—ipAddrChanger doesnt check if objectstore is running
•CSCds71155—Can only create one profile in CEMF profile dialog
•CSCds72244—backup script does not cope with error conditions
•CSCds72258—removal of feature list after upgrade
•CSCds72336—Query Editor for Event Groups not listing created users
•CSCds72461—Backup routine doesnt check if ObjectStore is running
•CSCds72475—Performance Data missing in XP4 EM
•CSCds72636—Performance degredation for LocalDB sets
•CSCds73409—EventBrowser cores after relaunch.
•CSCds73687—Can mouse paste bad Max Log values when kybd cannot. Crashed w/s
•CSCds74392—MibObjectDef causing core dump on call to indexValue.
•CSCds74427—object state events not processed for object on its own map
•CSCds74839—Save button on Action Report window does append to file
•CSCds75373—cemf shell command causes tcsh to core on a client
•CSCds75390—object scope filter of event browser broken
•CSCds75394—Server installation option leads to dead-end
•CSCds75399—Syntax error in emcommonErr.dbm file
•CSCds75869—eventSnoop is not outputing SnmpTrapEvents
•CSCds76354—Class action for perlscript doesnt replace AVROOT
•CSCds76358—deleting fields using CL does not work properly in query editor
•CSCds76366—Selecting 2 users to delete causes duplication on display
•CSCds76400—Logging in Controller Trap Mapping is misleading
•CSCds77229—no help message for cemf updateServer command
•CSCds77258—Action result dialog has no save button:paste error in code
•CSCds77293—The Notifications pop-up dialog can be closed permanently
•CSCds77297—Event Browser displays a wrong message on a service failure
•CSCds77494—Finishing deployment during backup causes system hang-up!
•CSCds77805—No error handling in Notification Profile Play Sound
•CSCds77821—Turn off LD_BIND_NOW for non-core processes
•CSCds77826—Allow path to logs directory to be set at install
•CSCds77850—Incorrect connection-lost Statement on Client
•CSCds78623—Event Browser needs to be refreshed before object name is visible
•CSCds78627—Copyright and splashscreen say incorrect dates and CEMF version
•CSCds78633—Event Browser has 2 scroll bars if Toolbar is hidden
•CSCds78642—Beep Continuously need to be alone in Scoreboard else doesnt work
•CSCds78982—cemf shell does not work properly if default shell is not /bin/sh
•CSCds79600—CGM:SCAL: Can get situation where prop is broken in viewer
•CSCds80840—Backup hangs until alarm process killed
•CSCds81705—Aborting a Backup leaves system unusable.
•CSCds81748—Backup hangs at ObjectServer Locked when entering new OG
•CSCds82754—IANAifType-MIB needs updating to lastest version
•CSCds82975—Must click in all IP & Mask fields to get IP Range to appear
•CSCds83059—Incorrect Trap Alarm Mapping
•CSCds83911—Scorecard deploy during Backup inconsistent
•CSCds83926—Login dialog can truncate hostname
•CSCds83966—Fetching object metadata sometimes fails
•CSCds83988—AsyncSnmpDataRep core when initialising Set Request Counter Map.
•CSCds84965—Restore gains priority when performing Backup as well
•CSCds84985—Errors in DeploymentWizard service code.
•CSCds84988—The set request count for an agent is incremented on table get.
•CSCds85071—Busy items in the hierarchy can be mistaken as unselectable
•CSCds85923—Jumbo patch de-install continues despite mini patches
•CSCds86018—Installing mini-patch should not stop system cant install
•CSCds86054—cemf backup not accepting arguments being passed
•CSCds87170—Incorrect behaviour from the Service Cache when populates menu
•CSCds87806—Federating Data Repository Proxy constructor memory handling
•CSCds87816—Uninstall NEM (CMGM) with 13 chassis, CEMF hangs
•CSCds87899—SNMP Research configuration files installed in wrong location.
•CSCds88480—Event Browser title not displaying name of object
•CSCds88514—Right click on rhs in maps much slower than in lhs
•CSCds88651—auto discovery of 6400s does not discover ips ending in 0 or 255
•CSCds89663—Automatic deinstallation of core patches.
•CSCds89701—Automatic deinstallation of dependent mini patches.
•CSCds89796—Column attributes get polled as scalar: parser should remove them
•CSCds90630—Bulk Downloader core in setIndexReturn
•CSCds90724—The Event Browser crashed when the Query Editor was closed.
•CSCds90733—Backup fails on CEMF-3.1.1-22—complains directory already exist
•CSCds90735—Access Manager crashes after editing an Access Specification
•CSCds90752—Paste service not avaliable in Object Group App
•CSCds90779—Types file missing so cannot annotate deployment contexts
•CSCds90785—Unhelpful messages when deployment fails
•CSCds90812—Copyright statements in scripts
•CSCds90843—Need to investigate multi-file backup
•CSCds91746—notificationChannelSnoop doesnt build
•CSCds91796—Summary displayed in Event Group App when no group selected
•CSCds91840—Merge error on avinstall script.
•CSCds91858—NEI needs to be more robust to configuration errors
•CSCds91891—Bulk Downloader cant trigger download in callback
•CSCds91936—Object COnfiguration doesnt display object name when launched
•CSCds91987—setRequestDispatchedMapper::raiseEvents is leaking memory.
•CSCds92276—SNMP DR needs to reply to abort call
•CSCdt01048—Core dump in notification server when started without CEMF runnin
•CSCdt01085—Test option on partitioningTool removes previously added info
•CSCdt01119—alarmDirTestRig needs to be updated
•CSCdt01175—trParser reports success when trServer part of cmd fails
•CSCdt01207—Cannot set a TimeTick, Gauge, Gauge32, Counter, Counter32
•CSCdt01311—MLKs in object group app
•CSCdt01312—Sort widget in Clear/Ack column of EvntBrwser obscured
•CSCdt01320—EventBrowser: Status footer is not updated for Sort by Clear/Ack
•CSCdt02144—Side-effect when stopping auto-discovery half-way
•CSCdt02154—LHS hierarchy doesnt update when invoke Open Map on an object
•CSCdt02211—Access Manager memory leaks found with purify
•CSCdt02226—Object Groups not created when partspec files are parsed
•CSCdt02250—ThresholdApp Core dumps on selection of label-less attribute
•CSCdt02275—Lost connection to AV core dialog incorrect
•CSCdt02331—Free Memory Read and Write when closing an app
•CSCdt02360—Object only in RO view can no longer be added elsewhere
•CSCdt02390—Updates to Map description do not get saved
•CSCdt03156—Popup Service menu is empty!
•CSCdt03187—need updates to bootstrap scripts to handle OTFP errors
•CSCdt03205—The Discovery Scheduler does not validate all the parameters
•CSCdt03225—sysmgrClient -k : ambiguity in how processes are specified
•CSCdt03236—FMR in ContainmentHierarchy::getResult(AwaitNodeInfoResult)
•CSCdt03240—Query time not updated at information, query run time box
•CSCdt03271—Attachements are not set in the main discovery dialog
•CSCdt03284—Error message for invalid SNMP timeout is not translated
•CSCdt03327—MetaDataServer returning extra DistributionEvent
•CSCdt03353—The QueryServer leaks new memory
•CSCdt04319—Certain table get fails using AsyncSnmpDataRepository
•CSCdt04340—Warning must be given when restoring using different version
•CSCdt04415—Suspect host command in cemf session -s remote_server
•CSCdt04420—makefile.defs.common requires update for ProLint
•CSCdt04429—sysmgr damages environment variables containing spaces
•CSCdt04458—Editing a regime to monitor a new attribute doesnt work.
•CSCdt04477—Erroneous error message when performing a bulk export.
•CSCdt04480—queryServer core dumped:Null pointer
•CSCdt05108—Getting index value for table in bulk downloader
•CSCdt05116—failure to translate names during cemf restore on new system
•CSCdt05127—Timercallback not deregistered in bulk downloader
•CSCdt05163—ipAddrChanger fails when restoring dbs from Unix fs to rawfs
•CSCdt05169—MLK in AlarmGroupIcon::setGadgetFont
•CSCdt05174—Autodiscovery fails to discover some of the network devices
•CSCdt05177—UMR in AlarmGroupIconInteractor::handleEvent
•CSCdt05180—UMR in StringListInteractor::handleEvent
•CSCdt06061—datalook does not handle containment paths which has spaces
•CSCdt06698—CGM:SCA:Lostcomms Alarms not cleared for objs comes back to Perfp
•CSCdt07463—Alarms not raised by controller due to race condition
•CSCdt09115—EvntBrwser: Consistency problems when Auto Update Disabled
•CSCdt09127—User is not informed if they select a start date after end date.
•CSCdt09165—Redraw problems with the Performance Manager dialog
•CSCdt09203—EvntBrwsr: Selection of multiple events, deployment->delete errs
•CSCdt09980—MIB can cause a core-dump if decoding an index which is unbounded
•CSCdt10008—Cancelling object deployment caused objectGui to core.
•CSCdt10021—EvntBrwsr: Full Object Name Display Options shows hidden views
•CSCdt10045—Cannot recover summarised history values via Perf Mgr of histAdmi
•CSCdt10050—FMW invoking services in ServiceExtraCheckingHelper & 600b MLK rc
•CSCdt10101—Performance Manager core dumps if there are no summary rules
•CSCdt10104—-u option for restore not available
•CSCdt11001—FMRs on closing View Scope Editor in query dialog in EvBrowser
•CSCdt11040—genericController locks in initialization phase
•CSCdt11128—killing notificationServer takes session out.
•CSCdt12216—Perf Manager does not handle correctly events for added criteria
•CSCdt12260—Unexpected tooltip, &tooltip_label1, in perf manager dialog
•CSCdt12282—Perf Manager doesnt close when monitored managed obj is deleted
•CSCdt12298—getDiagnostics script does not include trParser output
•CSCdt12300—Mib Parser Fails To Parse MIB
•CSCdt12312—Object deletion can return failure, yet still succeed
•CSCdt12368—Query Editor: defaultFilterMask = 64 activates extra criterion
•CSCdt13263—Memory errors during perf manager purify testing
•CSCdt13292—Unable to print from Event Browser Window.
•CSCdt13305—Deleting 2000 objects causes mapServer to exit with Obj Store err
•CSCdt13309—AbstractionServer core dump at SBC using SCM & CNOM
•CSCdt14607—.systemInfo file mechanism problems
•CSCdt14617—Auto discovery re-discovers discovered devices
•CSCdt14832—Possible risk of restore failue if done incorrectly
•CSCdt15793—Backup and restore CLI help inadequate
•CSCdt15798—Sleep in Sysmgr should be removed.
•CSCdt15846—Thresholder GUI adds thresholds to TRs in peculiar order
•CSCdt15848—Upgrade tool for attribute history auto-purge required
•CSCdt15852—snmpAgents deployed without ipaddress not added to setRequest map
•CSCdt15898—_LINE_ and _FILE_ in wrong order causing core dump
•CSCdt16870—unnecessary creation of setCounter cache in AsyncSnmpDREP
•CSCdt16871—Bulk Download Parser Infinite Loop
•CSCdt16889—rename a node with no label, refresh map, label appears on node
•CSCdt16911—AccessManager User Group list doesnt remove deleted UGs
•CSCdt17032—Bulk file transfer: need to tidy up device data in destructor
•CSCdt17044—Bulk file transfer: need better error handling and return codes
•CSCdt17070—Event Browser: memory leaks, purify .pv files
•CSCdt18206—Map shows invalid status icon for objects
•CSCdt18231—EventBrwser: crash in purify for alarm message filter
•CSCdt18249—Potentially unusual effects of new AHS purge policy.
•CSCdt18272—Wrong version in cemf query output.
•CSCdt18364—avLog is not working properly
•CSCdt19368—CEMF restore -h option not informative enough
•CSCdt19471—statusPropagationServer memory leak
•CSCdt19478—Notification Service crash not handled cleanly by CEMF
•CSCdt19504—EMs show NO status propagation when commissioned.
•CSCdt20553—Errors in the EventBrowser Services/Service Tasks
•CSCdt20602—Use of const char* in the CoreQueryBroker
•CSCdt20652—OGManger OG info on rhs of main dialog doesnt update edits
•CSCdt20673—CLI error when stopping client
•CSCdt20725—Error in the Query Editors enumerated criteria tabs
•CSCdt20753—Auto Discovery hop count broken again.
•CSCdt21793—BRASS log no longer avaliable, therefore cant debug SNMP
•CSCdt21846—queryServer limit is set too low
•CSCdt21933—ObjectConfig fails to fetch IP Agent attribute values
•CSCdt22086—Put all tools in vobs (DDTS Plan script only)
•CSCdt22532—BRASS cores when setting Counter64 values
•CSCdt23024—Window option displays wrong title for Event Browser
•CSCdt23043—Objects missing from tree view in map viewer
•CSCdt23077—warnings displayed during compilation of Performance Mgr
•CSCdt23098—Probs with Points option in Performance Manager
•CSCdt23158—user is informed when invalid name is used for SB, but not EG
•CSCdt23162—creating new user groups while editing user, selects new ones
•CSCdt23233—Zoom out in Performance Manager does not work correctly
•CSCdt23283—clear correlation is inconsistent at clearing last normal alarms
•CSCdt24431—Cannot install new patch on top of existing one.
•CSCdt24497—Access Object creation malfunctions if copy from existing Object
•CSCdt24540—Event Browser test spec work phase 1: placeholder DDTS report
•CSCdt24583—CEMF start misleading[C
•CSCdt24589—Incorrectly named Option in Access Man Help
•CSCdt24604—AttrVectorValueHelper should check for NULL pointer parameter
•CSCdt24642—Server:Side effect when stopping auto-discovery half-way
•CSCdt24647—Purify Results (mem leaks) for ThresholderApp
•CSCdt24710—sysmgr <-> daemon coms stops a machine reboot
•CSCdt25540—Following deletion of TRs trServer hogs CPU
•CSCdt25625—Number of SNMP stacks not easily configurable.
•CSCdt26747—mkpgk.CEMF does not check user priveleges until end of script
•CSCdt26750—OG/AG locking is unreliable, resulting in backup freezing
•CSCdt26786—Memory leaks found in core vob classes whilst testing EBrowser
•CSCdt26788—Lochness doesnt build direct from the vob.
•CSCdt26802—Memory leaks in Event Browser
•CSCdt27003—AttributeMapper should handle invalid MASKED attributes.
•CSCdt28123—EventBrowser title incorrect
•CSCdt28151—Inefficient EM controller calls when setting controllerState
•CSCdt28226—SQA-./cemf reset -h does not provide help instead carries out res
•CSCdt28228—All CEMF code base should be compiled with multithread support
•CSCdt28572—getDiagnostics should check disk space before tarring DBs
•CSCdt30384—SelfDeletingDialogServiceUser::serviceInvokeCB simply returns
•CSCdt30421—Memory leaks may occur when calling ServParamColl::loose_entries
•CSCdt31431—FTP Bulk Downloader does not offer DA replacement.
•CSCdt31433—TrapManager logging everything when logging level set to debug
•CSCdt31435—Queued alarm operations are leaked
•CSCdt31558—PortAllocationEntry class doesnt initialize m_port
•CSCdt31559—CEMF 3.2s Iona and CORBA vobs needs Patch 1 of CEMF 3.1
•CSCdt31758—CEMF should use ObjectStore 5.1 SP 4
•CSCdt31866—Setting vectorAnyValue() takes to long in corbaDataAbstractor
•CSCdt32742—start up process hangs forever while package installation
•CSCdt32896—object File Parser hanging while EM is being updated
•CSCdt32919—EditFilter::invokeServiceResult discarding status information
•CSCdt33062—Environment handling should be more robust.
•CSCdt33969—Unable to restart CEMF after cemf reset
•CSCdt34023—AsyncDRepPerfTestRig config file incorrect.
•CSCdt34036—Bulk File Transfer : Error in checking time of day
•CSCdt34051—Evnt Brwsr: Launching map viewer expand incorrect view
•CSCdt34098—SetRequestsDispatchedMapper compiles with warnings.
•CSCdt35222—Failed to get name of Object if not in Physical view
•CSCdt36180—comBuff resizing failure should log an error
•CSCdt36443—AttrIpAddress comparison operator semantics broken
•CSCdt36555—containmentServer leaks new memory
•CSCdt37596—metadataServer leaks new memory
•CSCdt37620—SnmpResearch stack performance issue.
•CSCdt37693—INTEGER syntax should default to signed integer in avvTranslator
•CSCdt37720—RetrievalStatusEnum in AttrVectorValueHelper should be public
•CSCdt37969—Backup should test for sufficient disk space
•CSCdt38746—Backup record removed when backup fails
•CSCdt38752—Old backups deleted regardless of archiving outcome
•CSCdt38844—CEMF fails to create backup directory if it does not exist
•CSCdt38963—High priority QueryManager changes after code review
•CSCdt38992—AsyncDRepPerfTestRig polls same object.
•CSCdt39003—Restore process does not catch sufficient errors
•CSCdt39139—avmt shell overlays the current shell env LM_LICENSE_FILE
•CSCdt39966—Possible race condition in Alarm Status Propagation calculation
•CSCdt39974—Cancel query in eventBrowser does not disable sort option
•CSCdt39992—Automic controller upgrade for PAS index fix
•CSCdt40000—Data Abstractor leaks new memory
•CSCdt40075—ObjectFileParser does send before updates.
•CSCdt40178—Clearing an already cleared alarm doesnt log any errors
•CSCdt41180—service constrained to OG available on obj not in OG
•CSCdt41184—QueryServer core dumps when using two scopes from different views
•CSCdt41191—Event browser is getting confused when the query server crashes
•CSCdt41200—updateName/updateIP doesnt change shell environment
•CSCdt41392—ABEV::m_cardinality causes problems in the manual update mode
•CSCdt42577—need annotations to explain failure after CSCds63219 merged
•CSCdt42582—Need to update bulk file transfer docs for partial tables
•CSCdt42603—Memory Leak in Event Channel Manager
•CSCdt42788—AHC core and high io/kernel with one thresholding regime
•CSCdt43776—Code review of CSCds79600
•CSCdt43882—Need extra SNMP Stack logging for testing
•CSCdt44967—Use of static_cast and const_cast in alarmBrowserEntry.cc
•CSCdt46055—Re-parent option operates differently depending on view setup
•CSCdt47181—Timeout issues causing service menu to be empty
•CSCdt47201—Profile testing from ObjectConfig no longer works
•CSCdt47207—Federating Data Rep : Get failing and no values on fail list
•CSCdt47209—Untidy message when restoring on RAWFS system
•CSCdt47234—Watchdog script logging problem on deinstall.
•CSCdt47249—SBC: Invalid object displayed in map pane of viewer app
•CSCdt47532—Event Browser menubar is not attached to the rhs of the screen
•CSCdt47539—User not informed if another user changes their selected object
•CSCdt48765—Processes which dont start should be logged at ERROR level.
•CSCdt48903—Makefile.defs.common refers to missing Purify
•CSCdt49170—Core dump inside MibManager::findByOid()
•CSCdt49204—Bulk File Transfer broken for varbinds per packet of 1
•CSCdt49236—AHS loses first value when using scheduled purging
•CSCdt49404—ContainmentTestRig::retrieveAllTreesIdsTest can miss events
•CSCdt49725—Require discovery API for use in StackEm in Loch Parr
•CSCdt50339—Table indices of syntax Gauge are always zero
•CSCdt50532—Og Info Display Updating query run time for OG Folders
•CSCdt50579—Alarms propagated in non-propagating tree
•CSCdt51698—Comms Handle errors displayed in log files
•CSCdt52635—CGM2.1:TrapAlarmMapper core dumps—During deletion of chassis.
•CSCdt54190—CGM2.1:Junk displayed in deployment when select multiple,CSC &SFC
•CSCdt54197—service invocation locks if app fails to start
•CSCdt54366—Core dumps while searching for a specific object in ObjGroup List
•CSCdt55643—Unable to build binaries for purify
•CSCdt55678—OGOperationTypeEnum ogSetOp and ogSetAttrsOp not perfoming set
•CSCdt56966—ContainmentUtils::getPathObjectId() could sometimes return rootId
•CSCdt57059—Matching results from poll() call to user is v inefficient
•CSCdt57415—Containment performance is slow for wide views
•CSCdt58072—Unnecessary ERRORs logged by asyncSnmpDataRepository
•CSCdt58099—ContainmentPath::set causes memory leak
•CSCdt59454—Counter64 index values are stored in code as int
•CSCdt60782—default logs dir is still created when non-default is specified
•CSCdt60786—Attribute mdsClassAllDerived is incorrectly documented in header
•CSCdt60885—ObjectUtils dumps lists ignoring logging level
•CSCdt60954—Prebuilt DataRepository attributes appear incorrect
•CSCdt62054—Event Browser should use a configurable Refresh Rate
•CSCdt62146—Event Browser stores object names in a list—performance issue
•CSCdt62159—Sysmgr should not sleep after execing backgrounded processes
•CSCdt62187—Memory errors in the core vob
•CSCdt62429—Sysmgr should not sleep for 1 second before stopping processes.
•CSCdt63276—ObjectUtils::fetchMetadata should fetch more attr names
•CSCdt63281—No menu invoked on right click in Event Browser
•CSCdt63367—Absolute include path used in alarmSpecifier.h
•CSCdt63486—Dialogs status field is too short for more than one object
•CSCdt64584—Event Browser Information Dialog does not cancelAsync DABS calls
•CSCdt65068—misleading error messages about licensing issues
•CSCdt65966—Error Dialog displays objectId when setting a system attribute
•CSCdt67156—PerfPollTask::checkRaiseEvents incorrectly consumes list entries
•CSCdt67686—Core from ckItem when specifying interface
•CSCdt69681—Application problems when performing a cemf backup
•CSCdt70240—backup with insufficient disk space, messages are incorrect
•CSCdt70976—lochness request install script contains errors
•CSCdt71031—FMWs and FMRs in Edit Filter service
•CSCdt72869—backup with insufficient disk space, an empty directory created
•CSCdt73757—local interfaces should be used in preference to proxies
•CSCdt75001—backup directory not created during cemf installation
•CSCdt75125—Misleading timestamp for alarms in event browser
•CSCdt75129—backup script cant create backup directory
•CSCdt76808—backup.log miss relevant information during the backup
•CSCdt76830—misleading messages in backup.log about directory name
•CSCdt79853—CGM2.1:asyncSnmpDataRe dumps core.
•CSCdt82398—AsyncSnmpDataRep crashes with core trying to get SNMP table
•CSCdt85904—CDM core dumped while creating a CAP profile
•CSCdt86163—Orphan package warning on install mentions AV, not CEMF
•CSCdt87579—Corba client cant find the GroupName while it exists
•CSCdt87940—It takes about 45 mins to open some windows
•CSCdt89295—CORBA system exception and CorbaGatewayMan cores
•CSCdt89984—Autodiscovery of existing DSLAM causes window crash and core dump
•CSCdt91510—correct restore process generates error messages
•CSCdt91728—trapBuilder core dumps when cant resolve host
•CSCdt93931—event type message is missing
•CSCdt94683—Can create QoS profile with a name that is blank
•CSCdt97561—When applying a ADSL profile receive a core dump
•CSCdu03223—Backup should capture OS patch level and check on restore
•CSCdu06847—GUI Failure during database load using object file parser
•CSCdu07725—Event browser launched from a single chassis displays wrong info.
•CSCdu08920—abstractionServer core dumped during sub-racking discovery.
•CSCdu12631—Access-Manager: User Wizard has no entry boxes
•CSCdu13593—Poller getObjectsToPoll method causes core.
•CSCdu14555—Cannot load backup after performing cemf reset command
•CSCdu15028—failed backup of db not showing in sysmgr.log
•CSCdu15067—Attempted backup while installing patch doesnt display error
•CSCdu15332—cemf stop hangs during alarm suspension
•CSCdu17230—coordinator core-dumped in unusual situation
•CSCdu18449—nbinterface core dump when objects are moved within/between scope
•CSCdu18452—DB Backup gives error msg if filesToBackup contains missing files
•CSCdu18456—crontab backup fails, reason not given in backup.log
•CSCdu18462—DB Backup gives _ps_ error message
•CSCdu18468—DB Backup on rawfs gives error after cataloging system info
•CSCdu18482—Core dump while moving dialog box
•CSCdu19485—rawfs DB backup greater than 2GB prompts for additional file name
•CSCdu19524—Able to run two CEMF DB backups at the same time
•CSCdu19526—rawfs DB incremental backup calculates disk space incorrectly
•CSCdu19572—Simultaneous toolkitGui invocation lockups
•CSCdu19640—./cemf restore -x /dev/rmt/0 gives errors
•CSCdu19888—corbaGatewayManager core dumps during daily garbage collection
•CSCdu19944—BOM information for Object Store incorrect for RTP builds
•CSCdu21919—restoring CEMF v3.0.4 DB on v3.2 system does not give warning msg
•CSCdu21958—Cannot register the filter
•CSCdu21974—MLK when removing alarm severity
•CSCdu22355—Event Browser: doesnt updated with latest events when its full
•CSCdu24386—./cemf restore ignore tape device if not on /dev/rmt/0
•CSCdu24555—sh: /usr/platform/SUNW,Ultra-80/sbin/prtdiag: not found
•CSCdu26654—cant start CEMF right after CEMF and Object Store are stopped
•CSCdu28001—SNMP set requests attrFailValue has nil errormessage
•CSCdu28783—CGM2.1PR6:ATMCM Manager dumps Core while Configuring PVC Connecti
•CSCdu31247—common users may find it hard to set date parameter for restoring
•CSCdu31307—cemf restore does not report ipAddrChanger error
•CSCdu31997—Window crashes while using short cut keys through empty menu.
•CSCdu32048—PVC info/create/delete dialog crashes while adding/deleting PVC.
•CSCdu40797—Configurable parameters for removing old backups
•CSCdu41106—Cant remove EMs whose avinstall directory name includes :
•CSCdu46880—nbinterface core dump when alarms were raised/cleared first time
•CSCdu49246—Cemf treats rawfs as ufs in /cemf/db, rawfs doesnt work
•CSCdu50360—object group removal not handled in LocalAttributeHistoryServer
•CSCdu51636—EM removal fails on Solaris 8
•CSCdu51728—appsServer and eventBrowser consume ~100% cpu
•CSCdu51965—UInt/Int comparison causes trap-mapping to fail
•CSCdu57489—if not use cemf save button to save, cemf doesnt know its saved
•CSCdu57763—CEMF Corba Gateway: Cant receive snmpTrapEvent
•CSCdu57780—corbaGatewayMan cores when invalid user/passwd is used
•CSCdu58981—Lochness calls callback twice for single call
•CSCdu59132—/opt/cemf/config/scripts/restoreWrapper: test: argument expected
•CSCdu60945—cemf restore without -f or -c doesnt work
•CSCdu68216—General Bugs In Backup/Restore
•CSCdu68240—Details of locking should be presented to user during back
•CSCdu68473—BulkDownLoad class return success when download fails
•CSCdu68513—BulkDownLoad class API no access to sysUpTime
•CSCdu68514—BulkDownload class doesnt provide an API to change remote filena
•CSCdu68524—AVVTranslator doesnt parse SNMP scalar objects
•CSCdu70283—cemf stop problem when participation cant be locked
•CSCdu70783—All Loch Ness calls fail due to missing expect
•CSCdu71398—Restore from tape fails
•CSCdu71544—Restore with ostore not running fails
•CSCdu71627—Missing parameter for the command line tool nbadmin
•CSCdu71641—Profiles not reliably displayed
•CSCdu71648—Duplicate traps were forwarded by NbSNMPForwarder
•CSCdu72894—Alarm propagation takes place when the object is decommissioned
•CSCdu83337—Cannot peform cemf restore after reset. err msg:unknown oper -l
•CSCdu85971—UGM:Performance manager dialog diplays bar chart which isnt there
•CSCdu86820—Inconsistent status on interfaces--possible corruption
•CSCdu88769—Java Plgins 1.3 not supported in CEMF 3.2 netscape
•CSCdv03967—corbaEventChannelManager has memory leak
•CSCdv04020—6160 Chassis gets stuck in discovery state
•CSCuk21316—Lochness must take schema ADB file from SDK
•CSCuk21328—CEMF and SCM dump core.
•CSCuk21345—SNMP Table iteration not working for varbinds < no of cols.
•CSCuk21371—Access manager cores when closing parent window
•CSCuk21383—Infrastructure changes required for Solaris8 compatibility
•CSCuk21404—Restore logs missing after a successful restore
•CSCuk21406—cemf usage needs updated to include cemf status
•CSCuk21419—Lochness doesnt build due to makefile problems
•CSCuk21436—incorrect display of hierarchies and maps
•CSCuk21450—CEMF status option should report when system not running.
•CSCuk21465—Bulk File Transfer : Core dump in bulk downloader
•CSCuk21479—addToVariable script -tidyall option sometimes misses a dir.
•CSCuk21487—Attribute values left in controller DB after object deletion
•CSCuk21489—Attempt to install unsuitable jumbo should not stop system.
•CSCuk21503—data repository user proxy calls fail unacceptably
•CSCuk21505—AttrVectorValue::copyRow can be improved
•CSCuk21508—Renamed folders can duplicate existing folders.
•CSCuk21529—Event Browser exits when close error dialog with untranslated msg
•CSCuk21536—objectFileParser create/delete fails when upgrading an EM
•CSCuk21537—SNMP copyright message is out of date
•CSCuk21573—Threshold Regimes dont function correctly during backup
•CSCuk21575—ARL socket receive buffer size not displayed correctly
•CSCuk21576—core dump when editing Event Group during backup
•CSCuk21577—Unable to commission objects on 2 network card h/w
•CSCuk21581—Notification Profile not functioning correctly during backup
•CSCuk21582—Read only Object Group is editable.
•CSCuk21583—No message written to terminal/logs when old backup files deleted
•CSCuk21589—Event Browser MLK when use toggles to ack/unack
•CSCuk21590—TrapManager hardwired to port 162, needs to be configurable
•CSCuk21602—If alarms fails to be cleared toggle is not redrawn
•CSCuk21603—Serialize/deserialize errors in log files
•CSCuk21635—Power loss during backup renders cemf unusable
•CSCuk21636—CGM: Line cards are deployed under shelf
•CSCuk21660—Filter editor sometime returns success when should return cancel
•CSCuk21662—Rebranding issue with templateVerifier error message
•CSCuk21677—backup not failing correctly when disk becomes full
•CSCuk21711—Restore and restoreWrapper clobber PATH variable
•CSCuk21714—LocalDB server using 99% of CPU after deletion.
•CSCuk21730—Dialogs do not seem to support 64 bit counter attributes
•CSCuk21733—Bulk File Transfer : Download time calculation is incorrect.
•CSCuk21740—restoreDataset doesnt incorporate tapedrive backups
•CSCuk21755—Core dump when creating a Event Group Query.
•CSCuk21757—DataAbstractorUser destructor should contain a cancelAsync call
•CSCuk21760—Unable to select multiple Objects via the Object Scope Selector.
•CSCuk21779—DeploymentInitiator should use DeployInitiatorHelper
•CSCuk21781—ObjectStore directories not found whilst doing rawfs install
•CSCuk21799—Archive to tape doesnt work on rawfs
•CSCuk21819—Sysmgr retrieves wrong Process after constant restart.
•CSCuk21820—Attribute history server purges the 12th poll, should be 11th
•CSCuk21850—Apparent merge problem with ContainmentServer.cc
•CSCuk21853—need to remove reference to lochness in cemf install
•CSCuk21856—core dump when launching Viewer from Event Browser
•CSCuk21857—createGroupsResult method in alarm group app could cause core
•CSCuk21859—Lochness Dev Kit cant be packaged
•CSCuk21867—restore.log lives in <CEMFROOT> despite other logs being elsewher
•CSCuk21888—COM: Core Dump in Commissioning GSR(12008) Chassis
•CSCuk21909—Users, User Groups, and access spec lists should be ordered
•CSCuk21931—Possible to close OG Editor while busied out for async operations
•CSCuk21935—OGEditEditorPolicy: inconsistence between adding and removing obj
•CSCuk21936—Restore should prompt before attempting restore from tape
•CSCuk21940—Various Cisco EMF binaries do not work under Quantify
•CSCuk21948—Some Dialog class methods do not check for NULL pointers
•CSCuk21961—FUM occuring when launching the event browser
•CSCuk21974—get_enum methods in MibObjectDef are not defined
•CSCuk21978—./cemf updateName doesnt work for substrings
•CSCuk21989—Bulk File Transfer : Broken for var binds one
•CSCuk21994—./cemf session -h no longer works.
•CSCuk21998—Performance issue introduced during fix of CSCdt06698
•CSCuk22008—install fails when object store is installed
•CSCuk22029—Option re-run query in the object group editor takes long time
•CSCuk22036—User should not be able to delete own user account
•CSCuk22040—macAddressHandler::setValue cores if passed null value
•CSCuk22043—Event Browser crashes on some occasions when ack/unack
•CSCuk22044—Event browser core dumps when objectServer very busy
•CSCuk22064—Alarmdeleter not functioning.
•CSCuk22065—Notifications database corruption
•CSCuk22067—Select change password with no user selected app stays busiedOn
•CSCuk22072—queryServer terminated with exception address space is full
•CSCuk22095—Cisco90i config dialog prompts save when no changes are made?
•CSCuk22100—objectConfig Quit dialog remains open when Yes is selected
•CSCuk22101—Warning message from sysmgrClient upon CEMF startup.
•CSCuk22125—Object deletion causes database to corrupt and shows junk Objects
•CSCuk22159—avinstall script causes bogus AVMT installation error
•CSCuk22180—After CGM 2.1 install, CEMF object deletion fails
•CSCuk22205—Scheduled Auto-discovery logged time record 1 hour behind?
•CSCuk22255—Autodiscovery does not inform user if deployment process fails
•CSCuk22256—MapServer is not informed when the participation cycle is reversd
•CSCuk22275—Unable to edit regime/profile whilst the system is very busy.
•CSCuk22278—updateIP script shouldnt log update if not needed.
•CSCuk22281—Thresholding Regimes With a Generic Cisco device unusable
•CSCuk22314—No services available to objects via the object grps app
•CSCuk22332—CEMF package description parameter is incorrect
•CSCuk22359—Alarm Group Server exit with ObjectStore exception
•CSCuk22387—Remove unnecessary errors from log files
•CSCuk22389—Alarm deletion could be more efficient
•CSCuk22412—CEMF Stop when CEMF is not initialised, sets state to failed.
•CSCuk22427—cemf updateServer doesnt resolve DNS name if IP address is used
•CSCuk22429—name and IP addr dont match if invalid server name is specified
•CSCuk22430—systemConfig calls causing database placement problems
•CSCuk22450—There is no indication that service has failed within mapviewer
•CSCuk22453—File Descriptors not freed after script run via Notification
•CSCuk22457—avstatus stays as backup after backup -h
•CSCuk22466—An integer data member in ogServer containing junk value
•CSCuk22469—SystemConfig::getString could cause core if passed null
•CSCuk22477—Possible perf mgr crash (NPR) in v. unusual circumstances
•CSCuk22483—Lochness vob not labelled automatically by script
•CSCuk22491—metdataServer logs error repeadly Attempt to redefine keyword...
•CSCuk22505—SerialMeta::read should report a warning not a error
•CSCuk22511—./cemf updateStackInfo boundary errors, and permission problem
•CSCuk22514—Perf object groups should be hidden from the user
•CSCuk22549—DiscoverySession class needs Doc++ format to publish
•CSCuk22562—apps should not create metadata on launch
•CSCuk22566—serivce manager should build hash of services during add/rm
•CSCuk22567—service cache registers two timers
•CSCuk22569—serviceManager should cache features for each service
•CSCuk22572—Core dump when parsing trap mapping files
•CSCuk22574—system info file contains strings of the type [[myVar]]
•CSCuk22583—agent poller memory leak fixes
•CSCuk22588—If TR has 2 triggers on multiple objects, 1st only triggers 1 obj
•CSCuk22626—Perf Manager fails to display summarised data, and stops working
•CSCuk22646—Event Information Dialog cannot be invoked through popup menu.
•CSCuk22657—preinstall.patch incorrectly attempts to chmod Orbix files
•CSCuk22684—CEMF packaging tools use non standard tools
•CSCuk22687—/vobs/SI-T does not get labelled as part of release
•CSCuk22702—objectGui becomes maxed out on CPU when deselecting objects
•CSCuk22705—Cemf3.1Patch3-6 package loops during re-installation
•CSCuk22716—ComponentmanagedView region/site/bay SMARTIES blank
•CSCuk22725—A script is required to automate part of the code review.
•CSCuk22784—not sufficient longging when decoding of SNMP value fails
•CSCuk22788—Configuration of broker disabling breaks on move from 3.0.4
•CSCuk22794—Last line of .ini ignored if not CR terminated
•CSCuk22796—Launching create event group from EB does not launch wizard
•CSCuk22799—ATM connection upload performance deteriorates unacceptably
•CSCuk22801—Profiles remain after deinstalling unix manager
•CSCuk22842—Tool required to emulate multiiple active users
•CSCuk22864—Object groups Object Selector is available for Query pop grps
•CSCuk22867—agent poller should warn if process becomes blocked
•CSCuk22894—TRManager does not update the status of a failed remove spec
•CSCuk22897—Removing EM does not remove perf group from ObjGrp Mgr
•CSCuk22906—Lochness doesnt build on other sites
•CSCuk22914—object deletion can cause system deadlock
•CSCuk22944—Need database versioning to help manage upgraded systems
•CSCuk22951—Clicking cancel when loading events, does not cancel
•CSCuk22958—DataAbstractorUser header contains misleading comments
•CSCuk22960—CEMF upgrade procedure for 3.2 and appsServer needs automated
•CSCuk22968—Apps not exiting on client when pulled off network
•CSCuk22990—ObjectServer exited during object deletion with ObjectStore excep
•CSCuk23026—New customer use of AD API can lead to crash due to async i/f
•CSCuk23062—AHC using all the CPU on lostcomms—regainedcomms.
•CSCuk23066—Debug logging for coordinator is wrong for kill -USR1
•CSCuk23067—CGM:SCAL—Can get situation where Prop is broken in Map Viewer
•CSCuk23068—Installed packages dont appear as removal options
•CSCuk23139—afCommon.dbm invalid format in CEMF-3.2-48
•CSCuk23147—Regexp too strict for OG Names
•CSCuk23152—ProLint suppression file does not include object store dir
•CSCuk23158—PersistentAttributeStore deletion is inefficient.
•CSCuk23182—Extraneous warning in eventBrowser.log every time processes event
•CSCuk23188—Misleading logging messages when corbaGatewayManager starts up
•CSCuk23218—ServiceUser cannot deregister with AppServiceMgr
•CSCuk23251—Inappropriate, persistent prompt to save changes on dialog close
•CSCuk23271—CGM:SCAL:Deletion of a Single Chassis objects takes a more time
•CSCuk23277—Event Browser Infinite loop when closing during constant traprate
•CSCuk23282—Controller code doesnt share OSAllocator between PAS and OGMgr
•CSCuk23289—Need a performance issue logging level
•CSCuk23305—ContainmentNodeVector::getDisplayableValue leaks memory
•CSCuk23311—Need OS migration facility for OS allocator problem
•CSCuk23312—Object Groups application may crash while closing the OG Manager
•CSCuk23357—Backup, Restore & Upgrade logs not written to non-default locale
•CSCuk23361—Memory errors in the Object Groups app
•CSCuk23364—watchDog script shouldnt start ObjectStore.
•CSCuk23367—Unnecessary counting of alarm list in Controller
•CSCuk23387—subSecondTimer pauseTimer allows negative time in nano seconds
•CSCuk23398—Cant restore more than one volume of backup.
•CSCuk23399—GenObjAttrFilter could be more efficient
•CSCuk23407—FMR in ContainmentHierarchy when launching map from event browser
•CSCuk23410—removeObjectDefFromContext API should have a clearer description
•CSCuk23462—MapServer & PartitioningMgr instantiate 2 OSAllocators.
•CSCuk23466—clearCorrelationServer memory leak
•CSCuk23476—clearing alarm specs are not bulked up
•CSCuk23481—No process in the Unix manager processes tab
•CSCuk23482—genericCisco EM causes core after deleting objects
•CSCuk23492—Misleading error message from MDSClassClasses in objectServer.log
•CSCuk23499—Discovery cores on start
•CSCuk23512—mkpkg.CEMF doesnt strip binaries
•CSCuk23525—Removing an EM for upgrade removes the History Criteria and Data
•CSCuk23526—Remove data partitioning feature from access manager
•CSCuk23530—License error message during cemf start on server
•CSCuk23536—Controller trap mapping can cause process heap to grow
•CSCuk23542—IpAddress & DiscoveryTaskId both need Doc++ API
•CSCuk23557—cemf script continually starts itself—cemf never starts.
•CSCuk23566—Sysmgr shouldnt remove pid of stopped processes.
•CSCuk23574—Sysmgr uses up 99% CPU trying to exec stopped processes.
•CSCuk23582—Name lost on SNMP Devices when Reparenting objects
•CSCuk23593—core when clicking on link that was connected to deleted object
•CSCuk23595—Migration tool required to remove Object groups from Access Specs
•CSCuk23610—command drep logs error if no va impls found
•CSCuk23612—Federating data repository should use event filter
•CSCuk23613—templateVerifier core dumps on UnixManager templates
•CSCuk23641—incorrect version of OStore SP specified when cemf session is run
•CSCuk23652—de-installing on a cemf client, the cemf install -r doesnt work
•CSCuk23668—QueryServer ERRORs need investigation.
•CSCuk23671—Metadata ERRORs shouldnt be logged for attr removal
•CSCuk23696—Help files not getting launched in solaris 8 system
•CSCuk23717—Newly create PASs should create drop index root
•CSCuk23721—Participation logging not adeqaute to debug deployed EM
•CSCuk23730—attributeHistoryServer cores during historyAdmin remove
•CSCuk23738—containmentTestRig test fails
•CSCuk23740—Update to makefile for asyncDRepPerfTestRig as files moved dir
•CSCuk23752—vectorServer process grows during trap processing
•CSCuk23754—Coordinator stopContext API is broken
•CSCuk23769—Update of CEMF license does not work
•CSCuk23783—Object store request script problems
•CSCuk23784—Object names corrupted after deletion in Map Editor
•CSCuk23786—cemf stop takes long time to stop during alarm suspension
•CSCuk23788—MGB adaptor errors in objectGui.log caused by clicking on objects
•CSCuk23805—Missing config file cemfInfo.ini
•CSCuk23806—AppServer fails to initialise, conflicting transaction types
•CSCuk23811—Autodiscovery launches an empty Object Selector
•CSCuk23812—Developer install broken : header bom problem
•CSCuk23821—Cemf client doesnt always work with 2 networks cards
•CSCuk23832—Header file Bom needs to be updated
•CSCuk23833—incorrect CEMF object class inheritance
•CSCuk23858—CGM: controller core dump in trap processing code
•CSCuk23867—MLKs in Wizard framework classes
•CSCuk23872—cemf script doesnt find S80ostore script.
•CSCuk23883—Installing an EM for upgrade doesnt upgrade the History Criteria
•CSCuk23899—Two users creating the same OG folder at the same time.
•CSCuk23915—alarm deletor process not working
•CSCuk23942—updateIP script should use [[NAME]] substitution.
•CSCuk23956—cant get 50 users on system;running out of file descriptors
•CSCuk23980—Server ping test on client installation was wrongly removed
•CSCuk23982—corbaGatewayManager restarting constantly after cemf start
•CSCuk23984—MLKs in OLEntryViewer
•CSCuk23988—Map exits when you select all on a map that contains a link
•CSCuk23992—os_utils::openOrDie should not use static transaction pointer.
•CSCuk23994—users unable to use new features if access spec is edited
•CSCuk23997—AsyncSnmpDR cores when clearing ovSuccessList after get operation
•CSCuk24018—core dump when launching Object Group from OG Manager
•CSCuk24023—Abstractions are not removed when objects are reparented
•CSCuk24038—ERROR message in appsServer.log after simple object deletion
•CSCuk24042—coredump in agServer when testing multi-user EBrowser capability!
•CSCuk24060—EB cores and obj selector remains open when og editor is closed
•CSCuk24066—toolkitGui cores if the user cancels a login via a double click
•CSCuk24080—Core from alarmGroupApp during automated sanity testing
•CSCuk24106—Installation of EM causes error when running cemf script
•CSCuk24116—Some help files dont launch & those that do have no images
•CSCuk24117—inconsistencies in code for validating names
•CSCuk24135—Additional CL params required to support automation
•CSCuk24139—changeOperation script ERROR msg seen when CEMF is deinstalled
•CSCuk24151—Useless info provided after restore from u10 to u5 machine
•CSCuk24153—restore from u-10 to u-5 gives OStore Errors and IP problems
•CSCuk24157—core dumps from agServer with multi user sessions
•CSCuk24165—Sysmgr fails to notify clients of start process result.
•CSCuk24176—Validating system error when restoring RawFS dbs?
•CSCuk24183—CGM:ObjectGrps—Failed to get Values for View Path Name for PVCs
•CSCuk24185—partitioningTool indicates success, when CEMF not running
•CSCuk24189—50 user testing cores sessionMgrServer after 16 hours
•CSCuk24203—updateName script does not rename <HOSTNAME>ServerParameters file
•CSCuk24223—Event browser population non performant
•CSCuk24243—Session colour problems, login screen bitmap needs cleaned
•CSCuk24276—Clear correlation cannot keep up with 10 traps/sec rate
•CSCuk24280—Cannot restore after trying a restore with an invalid dir/tape
•CSCuk24289—Core dumps in cisco[Platform,Module,IF]Man
•CSCuk24303—SNMP DREP core dump on table get.
•CSCuk24338—Upgrade fails due to syntax error in p.histcriteria file
•CSCuk24342—Deployment wizard ignores contextComplete status value
•CSCuk24351—table get itterator miss-matches table get results
•CSCuk24358—Cannot install com—ciscoPlatformCon cores
•CSCuk24364—queryServer defines newFailHandler but never sets it
•CSCuk24365—ServiceUser does not deregister from appServiceMgr on deletion
•CSCuk24371—TrapAlarmMapper needs to be able to dump IP cache for debugging
•CSCuk24377—avload script calls myErrorExit too many times
•CSCuk24381—fix to CSCat21357 has made trap mapping inefficient
•CSCuk24389—self management should parse og specs before object specs
•CSCuk24416—cannot remove object groups from command line
•CSCuk24425—586 bytes leaked when you add items to hierarchy
•CSCuk24426—Launchpad cores when exit attempted while CEMF is stopping
•CSCuk24449—UMR and MLK in ServiceMgrServer
•CSCuk24454—Core in discoveryScheduler caused by uncaught return state
•CSCuk24468—perf mgr table display incorrect when start/stop perf polling
•CSCuk24488—coredump and system freeze seen on cemf start with disk full
•CSCuk24496—Profile Monitor does not work with multiply users.
•CSCuk24503—reg exp in History Criteria upgrade script are incorrect.
•CSCuk24504—DialogLauncher does not allow individual dialogs to be closed
•CSCuk24539—Last trap from burst takes 90 secs to display in cemf apps
•CSCuk24563—ObjectStore cache sizes for some processes are innapropriate
•CSCuk24590—Dialog::internalInit leaking memory
•CSCuk24596—Login password does not accept more than 31 characters
•CSCuk24599—New User Group creation does not work properly.
•CSCuk24606—Object Group App refreshes object list wrongly
•CSCuk24610—Metadata attributes should not log ERROR for rootId gets.
•CSCuk24616—Restore script does not allow multiple hostnames
•CSCuk24617—updateIP script should check whether dbs exist
•CSCuk24625—objectServer deadlocks when uploading connections.
•CSCuk24633—Passing alarmSpec through controller cannot be done asynchronousl
•CSCuk24638—Passing null char* to logger::log causes core
•CSCuk24649—Query Pop OG doesnt update on Upgraded CEMF
•CSCuk24695—Core if you close Access Manager while delete dialog open
•CSCuk24737—New views are not loaded at upgrade time
•CSCuk24738—DeleteHelper should only store deletion attrs if context=forward
•CSCuk24777—serviceMgrserver OUT OF MEMORY
•CSCuk24779—ObjectServer reversing context but not erroring objectDefs
•CSCuk24785—COM-D17 did not install correctly on CEMF-3.2-84
•CSCuk24793—Trap burst processing time increases with sustained trap load
•CSCuk24796—MapViewers tree not consistent with the map after adding object
•CSCuk24798—Need to update scripts for 3.1 to 3.2 upgrade
•CSCuk24804—GUI process core dumps while session being closed
•CSCuk24818—sessionMgrServer dumps core when 50 sessions connected
•CSCuk24822—frequent orbix/jre messages in sysmgr.log
•CSCuk24827—Ilog getLabel calls resulting in core if null in EventMgr vob
•CSCuk24834—discoveryScheduler.log file not found
•CSCuk24853—Config syncing is occuring at a rate 5 times than expected
•CSCuk24857—containment proxy returns an invalid asyncHandle
•CSCuk24867—containmentAccessor should be removed from common em
•CSCuk24868—EM may close unexpectedly when open new screen-rare condition
•CSCuk24874—If 1st Threshold in regime fails all subsequent thresholds fail
•CSCuk24880—FMR in access manager when failed to change admin password
•CSCuk24883—FUM in access manager when launching Access Spec Editor
•CSCuk24887—restorePath file error in log is incorrect
•CSCuk24888—Controller processes all events as SnmpTrapEvents
•CSCuk24890—Trap burst processing inefficient for many source objects
•CSCuk24894—Multiuser:Listing garbage values in Windows option frm any dialog
•CSCuk24899—Partitioning data not retrieved on first open of editor dialog
•CSCuk24923—DialogLauncher session not closed when DialogLauncher complete
•CSCuk24931—ERRORs on first time start-up
•CSCuk24940—Trap Mapping cache does not handle object index changes
•CSCuk24959—CSCds73973 fix incorrect and should be removed.
•CSCuk24975—AttributeHistoryServer exits—objectstore cache full.
•CSCuk24977—FilterEditor caused core when using ag and parsing partitioning f
•CSCuk25006—Cleared alarms exist in the event browser
•CSCuk25013—updateName script has hard-coded paths for /opt/cemf
•CSCuk25021—In EventBrowser,progress dialog stays without loading events
•CSCuk25025—OGManager doesnt initialise some member variables
•CSCuk25040—Possible MLKs in standard em
•CSCuk25067—SNMP errors logged as debug
•CSCuk25068—Event Browser not staying busied on while child dialog open
•CSCuk25070—Query Editor and Print not working from right click on EB
•CSCuk25090—backup to users home directory leaves system locked up!
•CSCuk25091—ECM not cleaning up locations
•CSCuk25092—ObjectDef should be errored for OGUnknown operations.
•CSCuk25093—Deployment of QSGuide unixManager -> objectGui full CPU usage.
•CSCuk25099—ObjectStore wont start—non-default install & multi-homed box
•CSCuk25105—cemf script uses non-existent path /tools/gnu/bin
•CSCuk25131—Toolkit GUI core dump
•CSCuk25139—attributeHistoryCollector OUT OF MEMORY!!!
•CSCuk25143—Need support in build scripts to configure binary stripping
•CSCuk25146—core dump when deleting large numbers of objects using map
•CSCuk25190—Unable to start CEMF on client machine
•CSCuk25194—cemfinstall doesnt complete:Orbix 2000 errors
•CSCuk25213—Coordinator locking should proceed if contextCB not received
•CSCuk25216—apps server config could cause needless load on object server
•CSCuk25229—dbm string not getting translated when creating an empty object
•CSCuk25238—restore from tape quest. should be asked until valid b/up is pres
•CSCuk25243—Command cemf produces errors
•CSCuk25256—Bugs arising from running through Test doc EDCS-125162
•CSCuk25261—ObjectIdFilter: assignment does not work properly
•CSCuk25291—OG app cores when object deleted
•CSCuk25292—Partitioning specs fail to load during upgrade
•CSCuk25293—FMR in processControl.cc because of fix CSCuk23574
•CSCuk25331—Thresholds fail to poll if one object in OG is errored
•CSCuk25367—Purify errors found whilst running containmentTestRig
•CSCuk25396—agServerLocker preventing backups from being carried out
•CSCuk25406—dialogLauncher does not require authentication to close a session
•CSCuk25420—ObjectType File Parser too strict on Multi- definitions of AMVs
•CSCuk25439—Access Manager core dumps in getObjectNames if name is NULL
•CSCuk25440—client login will send plain text authentication data to server
•CSCuk25490—IP address entered at install time is not validated
•CSCuk25496—EventBrowser: Full object name On by default toggle is broken
•CSCuk25529—Snmp unable to decode oid, doesnt log OID value
•CSCuk25533—Bulk File Transfer: Not responding to failure
•CSCuk25575—Errors in objectGui log when opening map builder to edit map
•CSCuk25587—Upgrade fails. OFP cannot parse object spec files.
•CSCuk25615—two osAllocator instance methods are available
•CSCuk25617—Array Bounds Read on AttrOctetStringValue::set
•CSCuk25626—TaskBulkChanger should also maintain group operation ordering
•CSCuk25670—/cemf/dbs: No such file or directory msg seen during backup
•CSCuk25683—Traps sent during sanity test not fully reflected in Evnt Browsr.
•CSCuk25688—Order dependent behaviour in filter editor
•CSCuk25697—Memory leaks when launch map viewer service selected
•CSCuk25699—Pkgbuild requires to support patches, +
•CSCuk25702—Memory leaks in objectGui when object config launched
•CSCuk25704—objectGui process runs high CPU while 1000 objects deleted.
•CSCuk25725—Changing a scoreboards name does not take effect due to an FMR
•CSCuk25783—Memory leaks when deleting objects from hierarchy
•CSCuk25802—Memory leaks in objectGui when deploying from class palette
•CSCuk25805—FUM errors when creating links on map
•CSCuk25806—Query optimisation should be off by default in controller
•CSCuk25817—ABR and FMR in map operations
•CSCuk25820—cemfCatalog incorrect for restoring onto full disk
•CSCuk25829—SOAKtest: vectorServer causes system to run out of swap space
•CSCuk25840—Access Manager cores under exceptional circumstance
•CSCuk25842—When tried to install patch during restore, restoration fails.
•CSCuk25843—Coordinator should log no contextCompleteCB at WARN level.
•CSCuk25844—OGManager class not binary compatible with CEMF 3.0/3.1
•CSCuk25899—rename should default to object selected in mapviewer
•CSCuk25912—CEMF Client will not start after installation
•CSCuk25920—containment server logs errors during creation in multi views
•CSCuk25921—Dynamic cache scaling not working on some machines.
•CSCuk25933—disk space required message will result in TAC calls
•CSCuk25948—MDSClassAllDerviedHelper Does not update cache to reflect model
•CSCuk25958—Apps should not directly pull in .o files from other areas
•CSCuk25959—Leak in AttributeDispactcher when issuing setAsync.
•CSCuk25969—session not launched if hostname is invalid but IP address valid
•CSCuk26012—EB exits-alarms raised on unused obj ids & obj then deployed:id
•CSCuk26015—Unable to commission EM objects
•CSCuk26021—AttributeHistoryCollector database needs investigation.
•CSCuk26023—Small performance degradation from CSCuk22784
•CSCuk26034—Memory leak in mapServer when deleting from map
•CSCuk26041—AsyncSNMPDrep core dumps upon completion of chassis commissioning
•CSCuk26058—Threshold is incorrectly spelt in backup screen output
•CSCuk26112—Multiselection feature on dialogs malfunctioning
•CSCuk26148—ObjectGui coredump with dialog Launcher script
•CSCuk26169—Deinstallation of last sanity EM hanging at prepareport stage.
•CSCuk26170—Some Event Browser DBM strings exibiting strange behaviour.
•CSCuk26177—agServer log reporting large Number of events stillToBeProcessed
•CSCuk26249—Error when installing package
•CSCuk26333—Unable to dynamically select columns in BulkFileTransfer
•CSCuk26366—EventBrowser opened against container non performant
•CSCuk26377—AlarmDir server core dumps on start-up therfore causing update pr
•CSCuk26404—ocd manager apis should be marked as deprecated
•CSCuk26422—MLKs and 1 UMR present in Map Viewer
•CSCuk26425—&progressDialog displayed when inconise progress dialog in evgrps
•CSCuk26426—Warning message when user edits a SB or EG does not make sense
•CSCuk26474—During containment,rmParentFromChild may produce incorrect result
•CSCuk26573—CEMF cannot successfully deinstall.
•CSCuk26806—QoS Dialog crashes and kills cemf session
•CSCuk26810—EB can core due to rare timing issue during a refresh cancel
•CSCuk26815—Help fails to launch if cemf not installed in /opt/cemf/
•CSCuk26923—Copyright message still says 2000 on cemf startup
•CSCuk26952—UMR when launching EB from an object
Troubleshooting sections are provided in the Cisco EMF Installation and Administration Guide and the Cisco EMF User Guide.
The Cisco EMF Knowledge Base (formerly Atlantech Technologies Knowledge Base) and the Communications Software Group Knowledge Base are sources of additional technical information on Cisco EMF. Information is collated together as a result of responses to frequently asked questions and other common issues raised during the development of Cisco EMF-based Element Managers. The Knowledge Bases also feature guidelines and tips from INSMBU engineers and Engineering Services. New entries are added to the Knowledge Bases regularly.
The Cisco EMF Knowledge Base is available at http://www.cisco.com/kobayashi/technotes/CEMF/knowledgebase/
You can access the Communications Software Group Knowledge Base at http://www.johann.cisco.com/csg/topten_9_0.shtm
Cisco Element Management Framework Release Note, 78-13584-01
Cisco Element Management Framework Installation and Administration Guide v3.2, 78-12539-01
Cisco Element Management Framework User Guide v3.2, 78-12536-01
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to email@example.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
Contacting TAC by Telephone
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
P1 and P2 level problems are defined as follows:
•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0201R)
Copyright © 2000-2002, Cisco Systems, Inc.
All rights reserved.