Guest

CiscoWorks Device Fault Manager

Release Notes for Device Fault Manager 3.2 (With LMS 3.2)

  • Viewing Options

  • PDF (226.1 KB)
  • Feedback
Release Notes for Device Fault Manager 3.2 (With LMS 3.2)

Table Of Contents

Release Notes for Device Fault Manager 3.2 (With LMS 3.2)

New Features

Product Documentation

Related Documentation

Additional Information Online

Installing DFM 3.2

Known Problems in DFM 3.2

Resolved Problems in DFM 3.2

Obtaining Documentation and Submitting a Service Request

Notices

OpenSSL/Open SSL Project

License Issues


Release Notes for Device Fault Manager 3.2 (With LMS 3.2)


Published: J une 01, 2009
Revised: June 03, 2009 , OL-19663-01

These release notes are for use with Device Fault Manager (DFM) 3.2 running on Windows and Solaris platforms.

DFM 3.2 Incremental Device Updates (IDUs) and service packs can be downloaded from Cisco.com as they become available. (See Additional Information Online).

These Release Notes contain:

New Features

Product Documentation

Related Documentation

Additional Information Online

Installing DFM 3.2

Known Problems in DFM 3.2

Resolved Problems in DFM 3.2

Obtaining Documentation and Submitting a Service Request

Notices

New Features

In this release, DFM provides the following new features and enhancements:

Supports devices with SNMPv3 NoAuthNoPriv and SNMPv3 AuthPriv credentials

DFM allows you to import devices with SNMPv3 credentials from DCR. It discovers the devices successfully and groups them under All Known Devices in Inventory Group.

E-Mail Subject Customization

You can use the E-Mail Subject Customization page to customize the e-mail subject for forwarded alerts and events notifications.

10GE Interface Support

This feature helps you to configure and manage the 10 GE interfaces through the Polling and Threshold Settings page. It is applicable to all devices that support 10 GE and you will be notified if there is any fault on the 10 GE interfaces.

Enhancement in Polling and Threshold Configurations

Preview buttons are provided in Polling Parameters and Managing Thresholds pages. These buttons help you to see the edited polling and threshold parameters before you apply the changes.


Note Preview is supported only for Device Type Groups.


Enhancement in Discovery Status page

The discovery status of the devices in the Discovery Status page were previously displayed in a scrolling table. In DFM 3.2 it is displayed in a more user-friendly Paging table.

New Trap support—DFM supports the POWER-ETHERNET-MIB(POE) traps.

Event Severity Customization

The event severity can be customized using the New Event Severity feature. You can select either Critical or Informational from the drop-down list.


Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Product Documentation

Table 1 describes the product documentation that is available.

Table 1 Product Documentation 

Document Title
Available Formats

User Guide for Device Fault Manager 3.2

PDF on the product DVD

On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/dfm32ug_Book.html

In context-sensitive online help

Release Notes for Device Fault Manager 3.2

PDF on the product DVD

On Cisco.com at

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/release_notes/dfm32rn.html

Supported Devices Tables for LMS 3.2

PDF on the product DVD

On Cisco.com at

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html

Supported Operating Systems for Cisco Switches in Device Fault Manager 3.2

PDF on the product DVD

On Cisco.com at

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/device_support/table/dfm3_2os.html

Context-sensitive Online help

Select an option from the navigation tree, then click Help

Click the Help button in the dialog box

Note Most DFM dialog boxes do not include a Help button.


Related Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 2 describes the additional documentation that is available.

Table 2 Related Documentation 

Document Title
Description and Available Formats

Installation and Getting Started Guide for LAN Management Solution 3.2

PDF on the product DVD

On Cisco.com at
http://cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/install/guide1/lmsigsg.html

Data Migration Guide for LAN Management Solution 3.2

PDF on the product DVD

On Cisco.com at
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/data_migration/guide/lms32_dmg.html

User Guide for CiscoWorks Common Services 3.3

PDF on the product DVD

On Cisco.com at http://cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.3/user/guide/cs_33_ug.html

In context-sensitive Online help

User Guides for CiscoSecure Access Control Server

On Cisco.com at http://www.cisco.com/en/US/products/sw/secursw/ps2086/products_user_guide_list.html


Additional Information Online


Note We have adopted a new system for naming and numbering our patch/IDUs. For all releases after DFM 2.0 Patch/IDU 2.0.1, we will use the following conventions:
Patch/IDUs
will be called Service Packs, and instead of version x.y.z, it will be called version z. For example, instead of DFM 2.0 Patch/IDU 2.0.2, a release would be called DFM 2.0 Service Pack 2.


Incremental Device Updates (IDUs) or service packs contain updated files necessary for the latest device support and fixes to known problems that are not available in DFM 3.2. If you are a registered user, you can download IDUs/service packs for DFM from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm

To determine which packages are installed on your CiscoWorks Server, from the Common Services home page, select Software Center > Software Updates.

You can also obtain any published patches from the download site.

Installing DFM 3.2

An LMS 3.2 Installation Kit is available on the LMS 3.2 product DVD. The Kit contains everything needed to install DFM 3.2. Refer to Installing and Getting Started with CiscoWorks LAN Management Solution 3.2 for more information.

Known Problems in DFM 3.2

Table 3 and Table 4 describe problems known to exist in DFM 3.2 on Windows and Solaris respectively.

Table 3 Known Problems in DFM 3.2 (On Windows) 

Bug ID
Summary
Additional Information

CSCsk34741

DFM does not handle SNMP retries properly

DFM does not handle SNMP retries properly even if you have configured the device for three default retries. This problem occurs when you enter wrong SNMP credentials.

Workaround:

None

CSCsw90690

Error message regarding the licence limit in DFM is not displayed when the number of the imported devices exceeds the limit.

DFM has a licence that limits the number of the devices. When you import devices more than the license limit into DFM, an error message is not displayed.

Such a message should give details such as the total number of devices that can be managed by the existing license.

There should also be a link in the error message that allows you to go the licence page and update the licence.

Workaround:

None

CSCsq57830

Device based authorization does not work in AAD pages

This problem occurs when you:

1. Generate alerts for all the devices with full permissions.

2. Unauthorize some devices and launch the AAD page using Campus Crosslaunch.

The alerts are also displayed for unauthorized devices and the Clear and Acknowledge buttons are wrongly enabled. They should not be enabled because some devices are unauthorized.

Workaround:

None

CSCsq31553

DFM does not support processing of SNMP V3 Traps

DFM does not support processing of SNMP V3 Traps.

Workaround:

None

CSCsl11291

DFM does not co-exist with Install Shield 2008 software

When Install Shield 2008 is installed on a DFM 3.0.2 server, the DfmServer process continues to run. However, it creates a blank DFM.log and the device addition hangs at 10%.

Workaround:

Uninstall Install Shield 2008

CSCsz07447

Errors are found in the Incharge Engine's log files during Reconfiguration.

During the process of Reconfiguration, errors related to Configuration settings are logged in the Incharge Engine's log files. That is, they are logged in the DFM.log and DFM1.log files.

Workaround:

None

CSCsx72359

In DFM with 1500 SNMPv3 devices, SNMP requests are skipped when polling interval is set as 60 seconds.

This problem occurs when you:

1. Manage 1500 SNMPv3 devices in DFM.

2. Change Polling settings to 60 seconds for all components

3. Apply the changes

SNMP requests do not appear every 60 seconds. Also, there is a delay between any two polling cycles for SNMP requests. This occurs although the ICMP communication occur correctly.

Workaround:

None

CSCsw98735

After a rediscovery of devices, DFM Incharge Engine polls the SNMP timed out devices.

This problem occurs when you:

1. Import devices into DFM

2. Wait for the devices to be moved to Known state

3. Rediscover all the devices.

During Rediscovery, the devices are SNMP timed out. However, Incharge Engine polls the devices with the old data which was collected during the first discovery.

Workaround:

None

CSCsw98711

In DFM, when devices are not reachable, ICMP and SNMP requests are found during Rediscovery.

This problem occurs when you:

1. Add a real device into DFM and wait till polling happens

2. Rediscover the device when it is down

Discovery stops at 40% but Incharge Engine completes the discovery and logs a discovery error.

However, Incharge Engine continues to send ICMP and SNMP requests to the unreachable device.

If you Rediscover the device when it is reachable, the device goes to the SNMP Timed Out state and Polling continues.

If you Rediscover the device again, it is pushed to a Known state.

Workaround:

None

CSCsk36410

LMS5K: DFM Processes block the CPU while performing Fresh Device Import into DFM

If you import around 5000 devices into DFM, it overloads the CPU. The process takes approximately 3hours and 30minutes.

Workaround:

None

CSCsq70227

PIDM table does not get updated during Inline Upgrade.

When you perform an Inline Upgrade from LMS 3.0 to LMS 3.1, the PIDM table is not preserved. As a result, the DFM functions are lost in the Device Center and CiscoWorks Assistant.

This is not an Upgrade problem. It existed in DFM 3.0 and is carried over when you upgrade from LMS 3.0 to LMS 3.1.

Workaround:

Delete and add DFM devices.

CSCsw90699

In DFM, devices go to Data Collector timed out state after the Incharge Engine has completed Discovery.

During the Discovery of 5000 devices in DFM, some devices go to the Data Collector Timed Out state after the Incharge Engine has completed Discovery.

Workaround:

None

CSCsy34104

In DFM, during E-mail configurations, e-mail IDs are not properly validated.

During E-mail Configurations, DFM wrongly accepts special characters in the e-mail ID.

Ideally, it should not allow the special characters and should have a standard format for the e-mail IDs.

Workaround:

None

CSCsy79554

PIDM updates are not done for DFM after remote migration.

This problem occurs when you:

1. Install LMS 3.2

2. Restore the backup of LMS 3.1+IPv6 dropin

After the restore, PIDM entries for DFM are not updated. Devices are shown as associated with the server from which backup is taken. Hence the cross launches associated with DFM do not work.

You cannot launch DFM alerts for devices managed by DFM without alerts from N Hop view portlet and CM Topo.

Also CiscoWorks Assistant shows the devices as being managed by DFM of the backup server and not by the current server.

Workaround:

None

CSCsy84087

In a DFM server with 5000 devices, Delete button is not enabled immediately.

This problem occurs in a DFM server with 5000 devices. If you:

1. Disable the Auto Import option in the Device Import page,

2. Select the Rediscover/Delete option in Device Management page,

The Delete button is disabled. It takes more than three minutes for it to be enabled again.

The Delete button works well if you have only a few devices.

Workaround:

None

CSCsz13696

The report printed using the Print Friendly button in the Device Details page displays only 2000 records.

In DFM, if you click Print Friendly button in Device Details page, the following message is displayed:

Your Report resulted in 5002 records for printing.

However, only 2000 records are displayed in the report.

Workaround:

None

CSCsz21403

Cannot create User-defined groups if DFM has Voice and Telephony devices.

You cannot create any User-defined groups in DFM, if there are any Voice and Telephony devices. An error message appears if you try to create these user-defined groups.

Workaround:

Delete the Voice and Telephony devices from DFM

CSCsz21440

Auto allocation settings in DFM are sometimes not preserved.

This problem occurs when you:

1. From DFM, go to Device Management > Device Import > Auto Allocation.

2. Check the Enable Auto Mode check box.

3. Select Manage By Groups and check the System Defined Groups check box.

All the sub groups are selected.

4. Uncheck some of the sub groups, such as Routers and Wireless.

5. Apply the changes.

6. Browse through other pages and return back to the same page.

Manage All Devices option is selected instead of Manage By Groups.

Workaround:

None

CSCsz28940

In DFM, the Detailed Device View page displays the MSFC device as Suspended when its parent device is deleted.

This problem occurs when you:

1. Manage a Cat6509 parent device and an MSFC child device.

2. Delete the parent device from DFM.

The Detailed Device View page displays the MSFC device as Suspended with no polling.

Workaround:

Rediscover the device.

CSCsz21918

In DFM, an invalid alert is generated for the VSS device.

In DFM, the entSensorStatus value is displayed as UNKNOWN for the VSS switch and an invalid alert is generated.

Workaround: None

CSCsy21759

DLL conflicts occur after DFM is installed.

After installing DFM from the LMS bundle on a Windows Server 2003 Enterprise Edition (SP2), you cannot launch services such as ping, ipconfig, net stop/start, etc.

This is caused by a conflict of DLLs used by DFM with other versions of the DLLs. These similar DLLs are used by another application on the server.

Workaround:

Search for and remove the conflicting DLLs. They are usually located under C:\WINNT\WinSxS\.

CSCsu01718

In DFM, devices get stuck at 70% Learning state.

This problem occurs when you:

1. Schedule a daily Rediscovery job for 5000 devices

2. Start a Rediscovery for all 5000 devices

Some devices are moved to the Known state and others get stuck at 70% Learning state.

Workaround:

Rediscover the devices stuck at 70%. They are moved to the Known state.

CSCsz71786

LMS 3.2: PIDM entries are not removed in Slave server after deleting devices.

This problem occurs when you:

1. Manage 1500 devices in DFM.

2. Configure the server as slave in a multi-server setup.

3. Delete the devices from DFM.

Devices are not displayed in DFM UI.

However, the PIDM table lists all the devices as being managed. So, Device Center and CiscoWorks Assistant incorrectly show the devices as being managed by DFM.

Workaround:

Before adding devices into DFM, run the following perl script to clean up the PIDM entries for DFM: NMSROOT/etc/tis/scripts > perl DropPIDMentries.pl

CSCsx23656

DFM3.2: sm_server does not stop when daemons are stopped.

sm_server processes are not stopped when you stop the daemons. This issue occurs frequently when you manage a bulk of devices.

Workaround:

During Uninstallation of DFM3.2, when you access any file under NMSROOT\objects\smarts\, if a popup displays the following error message "Access is denied", then kill all sm_server.exe processes from Task Manager. The maximum number of processes is four.

Click OK.

Uninstallation continues.

During Reinstallation of DFM 3.2, if any files are listed as locked, then kill all sm_server.exe processes from Task Manager. The maximum number of processes is four.

Click Retry.

Reinstallation continues.

CSCsz77616

DFM3.2: After restoring the system backup, Alerts and Activities Detail View and Event Severity are not displayed.

This problem occurs when you:

1. Take a selective System Backup in DFM 3.2.

2. Restore in a different DFM 3.2 server.

Alerts and Activities Detail View is not restored.

In Notification Customization, current Event Severity is not restored.

Workaround:

None

CSCsz77669

When you are editing a Notification Group, Device Selection does not appear.

This problem occurs when you:

1. Select all devices.

2. Create a Notification Group.

3. Log into CiscoWorks again

4. Select the created Notification Group and click the Edit.

5. Expand All Devices.

The Device Selection is not displayed. However, the Device Type groups display the selected devices.

Workaround:

Refresh or launch the page again. Device selection is displayed.

CSCsz79389

DFM Goups are not created or updated when devices are deleted and added again.

This problem occurs when you:

1. Import a device into DFM.

It is listed under Device Type Groups.

2. Delete the device.

3. Immediately re-import the device.

The Device Type Group does not appear and polling for the device does not occur.

Workaround:

After you delete a device, wait for two or three minutes before adding it or attempting to rediscover it.

CSCta11852

Discovery not working when VPN concentrator devices are added

VPN Concentrator devices responds to SNMP V1 Get requests and not to SNMP GetBulk requests. If VPN Concentrator devices are added to DFM 3.1.2, DFM 3.1.3 and DFM 3.2, discovery will fail as there is no fall back from Get Bulk to Get Next requests.

Workaround:

1. Modify the file NMSROOT/objects/smarts/conf/discovery/discovery.conf and set SNMPGetBulkEnabled =FALSE.

2. Restart the DFM processes by running the following commands:

pdterm DfmServer DfmServer1

pdexec DfmServer DfmServer1

3. Rediscover the device.


Table 4 Known Problems in DFM 3.2 (On Solaris) 

Bug ID
Summary
Additional Information

CSCsq60989

Check point and null pointer exceptions are in the daemons.log

While running the scheduled Rediscovery job, DFM calls check points to check the databases.

However this call goes into a loop and does not get completed. A Null pointer error is displayed.

Workaround:

None

CSCsz13416

Performance issues occur with 200 OGS Groups

When OGS group contains 200 groups, the following OGS functionalities takes a longer time:

Creating a new group

Editing a user-defined group

During the above operations INVDbEngine uses almost 60-80% of CPU.

Editing the NOS group

Launching PTM pages and Group Administration pages

Workaround:

None

CSCsk34741

DFM does not handle SNMP retries properly

DFM does not handle SNMP retries properly even if you have configured the device for three default retries. This problem occurs when you enter wrong SNMP credentials.

Workaround:

None

CSCsw90690

Error message regarding the licence limit in DFM is not displayed when the number of the imported devices exceeds the limit.

DFM has a licence that limits the number of the devices. When you import devices more than the license limit into DFM, an error message is not displayed.

Such a message should give details such as the total number of devices that can be managed by the existing license.

There should also be a link in the error message that allows you to go the licence page and update the licence.

Workaround:

None

CSCsq57830

Device based authorization does not work in AAD pages

This problem occurs when you:

1. Generate alerts for all the devices with full permissions.

2. Unauthorize some devices and launch the AAD page using Campus Crosslaunch.

The alerts are also displayed for unauthorized devices and the Clear and Acknowledge buttons are wrongly enabled. They should not be enabled because some devices are unauthorized.

Workaround:

None

CSCsq31553

DFM does not support processing of SNMP V3 Traps

DFM does not support processing of SNMP V3 Traps.

Workaround:

None

CSCsz07447

Errors are found in the Incharge Engine's log files during Reconfiguration.

During the process of Reconfiguration, errors related to Configuration settings are logged in the Incharge Engine's log files. That is, they are logged in the DFM.log and DFM1.log files.

Workaround:

None

CSCsx72359

In DFM with 1500 SNMPv3 devices, SNMP requests are skipped when polling interval is set as 60 seconds.

This problem occurs when you:

1. Manage 1500 SNMPv3 devices in DFM.

2. Change Polling settings to 60 seconds for all components

3. Apply the changes

SNMP requests do not appear every 60 seconds. Also, there is a delay between any two polling cycles for SNMP requests. This occurs although the ICMP communication occur correctly.

Workaround:

None

CSCsw98735

After a rediscovery of devices, DFM Incharge Engine polls the SNMP timed out devices.

This problem occurs when you:

1. Import devices into DFM

2. Wait for the devices to be moved to Known state

3. Rediscover all the devices.

During Rediscovery, the devices are SNMP timed out. However, Incharge Engine polls the devices with the old data which was collected during the first discovery.

Workaround:

None

CSCsw98711

In DFM, when devices are not reachable, ICMP and SNMP requests are found during Rediscovery.

This problem occurs when you:

1. Add a real device into DFM and wait till polling happens

2. Rediscover the device when it is down

Discovery stops at 40% but Incharge Engine completes the discovery and logs a discovery error.

However, Incharge Engine continues to send ICMP and SNMP requests to the unreachable device.

If you Rediscover the device when it is reachable, the device goes to the SNMP Timed Out state and Polling continues.

If you Rediscover the device again, it is pushed to a Known state.

Workaround:

None

CSCsk36410

LMS5K: DFM Processes block the CPU while performing Fresh Device Import into DFM

If you import around 5000 devices into DFM, it overloads the CPU. The process takes approximately 3hours and 30minutes.

Workaround:

None

CSCsq70227

PIDM table does not get updated during Inline Upgrade.

When you perform an Inline Upgrade from LMS 3.0 to LMS 3.1, the PIDM table is not preserved. As a result, the DFM functions are lost in the Device Center and CiscoWorks Assistant.

This is not an Upgrade problem. It existed in DFM 3.0 and is carried over when you upgrade from LMS 3.0 to LMS 3.1.

Workaround:

Delete and add DFM devices.

CSCsw90699

In DFM, devices go to Data Collector timed out state after the Incharge Engine has completed Discovery.

During the Discovery of 5000 devices in DFM, some devices go to the Data Collector Timed Out state after the Incharge Engine has completed Discovery.

Workaround:

None

CSCsy34104

In DFM, during E-mail configurations, e-mail IDs are not properly validated.

During E-mail Configurations, DFM wrongly accepts special characters in the e-mail ID.

Ideally, it should not allow the special characters and should have a standard format for the e-mail IDs.

Workaround:

None

CSCsy79554

PIDM updates are not done for DFM after remote migration.

This problem occurs when you:

1. Install LMS 3.2

2. Restore the backup of LMS 3.1+IPv6 dropin

After the restore, PIDM entries for DFM are not updated. Devices are shown as associated with the server from which backup is taken. Hence the cross launches associated with DFM do not work.

You cannot launch DFM alerts for devices managed by DFM without alerts from N Hop view portlet and CM Topo.

Also CiscoWorks Assistant shows the devices as being managed by DFM of the backup server and not by the current server.

Workaround:

None

CSCsy84087

In a DFM server with 5000 devices, Delete button is not enabled immediately.

This problem occurs in a DFM server with 5000 devices. If you:

1. Disable the Auto Import option in the Device Import page,

2. Select the Rediscover/Delete option in Device Management page,

The Delete button is disabled. It takes more than three minutes for it to be enabled again.

The Delete button works well if you have only a few devices.

Workaround:

None

CSCsz13696

The report printed using the Print Friendly button in the Device Details page displays only 2000 records.

In DFM, if you click Print Friendly button in Device Details page, the following message is displayed:

Your Report resulted in 5002 records for printing.

However, only 2000 records are displayed in the report.

Workaround:

None

CSCsz21403

Cannot create User-defined groups if DFM has Voice and Telephony devices.

You cannot create any User-defined groups in DFM, if there are any Voice and Telephony devices. An error message appears if you try to create these user-defined groups.

Workaround:

Delete the Voice and Telephony devices from DFM

CSCsz21440

Auto allocation settings in DFM are sometimes not preserved.

This problem occurs when you:

1. From DFM, go to Device Management > Device Import > Auto Allocation.

2. Check the Enable Auto Mode check box.

3. Select Manage By Groups and check the System Defined Groups check box.

All the sub groups are selected.

4. Uncheck some of the sub groups, such as Routers and Wireless.

5. Apply the changes.

6. Browse through other pages and return back to the same page.

Manage All Devices option is selected instead of Manage By Groups.

Workaround:

None

CSCsz28940

In DFM, the Detailed Device View page displays the MSFC device as Suspended when its parent device is deleted.

This problem occurs when you:

1. Manage a Cat6509 parent device and an MSFC child device.

2. Delete the parent device from DFM.

The Detailed Device View page displays the MSFC device as Suspended with no polling.

Workaround:

Rediscover the device.

CSCsz21918

In DFM, an invalid alert is generated for the VSS device.

In DFM, the entSensorStatus value is displayed as UNKNOWN for the VSS switch and an invalid alert is generated.

Workaround:

None

CSCsu01718

In DFM, devices get stuck at 70% Learning state.

This problem occurs when you:

1. Schedule a daily Rediscovery job for 5000 devices

2. Start a Rediscovery for all 5000 devices

Some devices are moved to the Known state and others get stuck at 70% Learning state.

Workaround:

Rediscover the devices stuck at 70%. They are moved to the Known state.

CSCsz30972

LMS5K: Unable to create Notification Groups in a Solaris server with 5000 devices.

In a Solaris 5K server, you are not able to create Notification groups. The validation of the group takes a long time and this causes the GUI to slow down.

Workaround:

None

CSCsz71786

LMS 3.2: PIDM entries are not removed in Slave server after deleting devices.

This problem occurs when you:

1. Manage 1500 devices in DFM.

2. Configure the server as slave in a multi-server setup.

3. Delete the devices from DFM.

Devices are not displayed in DFM UI.

However, the PIDM table lists all the devices as being managed. So, Device Center and CiscoWorks Assistant incorrectly show the devices as being managed by DFM.

Workaround:

None

CSCsz77616

DFM3.2: After restoring the system backup, Alerts and Activities Detail View and Event Severity are not displayed.

This problem occurs when you:

1. Take a selective System Backup in DFM 3.2.

2. Restore in a different DFM 3.2 server.

Alerts and Activities Detail View is not restored.

In Notification Customization, current Event Severity is not restored.

Workaround:

None

CSCsz77669

When you are editing a Notification Group, Device Selection does not appear.

This problem occurs when you:

1. Select all devices.

2. Create a Notification Group.

3. Log into CiscoWorks again

4. Select the created Notification Group and click the Edit.

5. Expand All Devices.

The Device Selection is not displayed. However, the Device Type groups display the selected devices.

Workaround:

Refresh or launch the page again. Device selection is displayed.

CSCsz79389

DFM Goups are not created or updated when devices are deleted and added again.

This problem occurs when you:

1. Import a device into DFM.

It is listed under Device Type Groups.

2. Delete the device.

3. Immediately re-import the device.

The Device Type Group does not appear and polling for the device does not occur.

Workaround:

After you delete a device, wait for two or three minutes before adding it or attempting to rediscover it.

CSCta11852

Discovery not working when VPN concentrator devices are added

VPN Concentrator devices responds to SNMP V1 Get requests and not to SNMP GetBulk requests. If VPN Concentrator devices are added to DFM 3.1.2, DFM 3.1.3 and DFM 3.2, discovery will fail as there is no fall back from Get Bulk to Get Next requests.

Workaround:

1. Modify the file NMSROOT/objects/smarts/conf/discovery/discovery.conf and set SNMPGetBulkEnabled =FALSE.

2. Restart the DFM processes by running the following commands:

pdterm DfmServer DfmServer1

pdexec DfmServer DfmServer1

3. Rediscover the device.


Resolved Problems in DFM 3.2

Table 5 and Table 6 describe problems resolved since the last release of DFM on Windows and Solaris respectively.

Table 5 Resolved Problems in DFM 3.2 (On Windows) 

Bug ID
Summary
Additional Information

CSCsq02974

In DFM 3.1, Notifications were not sent when you selected and acknowledged an alert in the Alerts and Activities Detail page.

This problem has been resolved.

CSCso68258

DFM was polling for ASA cpmCPUTotal5minRev mib object. However, it supported only ASA cpmCPUTotal5min mib objects.

This problem has been resolved.

CSCsq46143

DFM Online Help contained general event code for all events. However, Component Event Codes for alerts were not documented in Online help.

This problem has been resolved.

CSCso55344

For all Resumed and Suspended devices in DFM, alerts were displayed in AAD. However, e-mail notifications were not sent for any of the Resumed devices and for some of the Suspended devices.

This problem has been resolved.

CSCsm89472

DFM did not support Power Over Ethernet (PoE) fault management.

This problem has been resolved.

CSCsk34630

When SNMP credentials of a device were changed in DCR, DFM discovered the device although it had wrong credentials.

This problem has been resolved.

CSCsq38090

For a switch interface, CUOM was displaying an incorrect High Utilization event value.

This problem has been resolved.

CSCsq55397

The community string used while sending notification traps needs to be hard-coded as Public. The users who need to customize the community strings, changed the name of the strings from Public to a name of their choice.

Hence, the SNMP managers did not process the notification traps sent by DFM.

This problem has been resolved.

CSCsq67843

DFM did not support 10 Gigabit devices.

This problem has been resolved.

CSCsv21221

DFM could not recognize a trunk between two devices that were managed by DFM and DFM 1 servers.

This problem has been resolved.

CSCsx65722

The 6509 MSFC devices were discovered and pushed to a Known state by DFM. However, they went to Suspended state and were not monitored anymore. When you clicked the Resume button, the card went into Questioned state.

This problem has been resolved.

CSCsy90443

When you changed the host name of CiscoWorks Server, the option Manage By Groups did not work.

This problem has been resolved.

CSCsz08953

Unmanaged Interfaces used to revert to a Managed state after Device Rediscovery.

This problem has been resolved.

CSCsb05350

You could not customize the subjects of e-mail notifications.

This problem has been resolved.

CSCsv13865

DFM 3.x upgrades added new local host entries to trapd.conf file.

This problem has been resolved.

CSCsv16566

DFM did not display Alerts and Events in GUI and Device Management page was not launched.

This problem has been resolved.

CSCsz45181

In DFM, for CE devices, the Managed state was not preserved after Rediscovery.

This problem has been resolved.


Table 6 Resolved Problems in DFM 3.2 (On Solaris) 

Bug ID
Summary
Additional Information

CSCsi32212

Device type groups were missing after an inline upgrade from LMS 2.6 to LMS 3.0 in SSL mode on Solaris. The Device Type groups that were displayed before the upgrade were not displayed after the upgrade.

This problem has been resolved.

CSCsq02974

In DFM 3.1, Notifications were not sent when you selected and acknowledged an alert in the Alerts and Activities Detail page.

This problem has been resolved.

CSCso68258

DFM was polling for ASA cpmCPUTotal5minRev mib object. However, it supported only ASA cpmCPUTotal5min mib objects.

This problem has been resolved.

CSCsq46143

DFM Online Help contained general event code for all events. However, Component Event Codes for alerts were not documented in Online help.

This problem has been resolved.

CSCso55344

For all Resumed and Suspended devices in DFM, alerts were displayed in AAD. However, e-mail notifications were not sent for any of the Resumed devices and for some of the Suspended devices.

This problem has been resolved.

CSCsm89472

DFM did not support Power Over Ethernet (PoE) fault management.

This problem has been resolved.

CSCsk34630

When SNMP credentials of a device were changed in DCR, DFM discovered the device although it had wrong credentials.

This problem has been resolved.

CSCsq38090

For a switch interface, CUOM was displaying an incorrect High Utilization event value.

This problem has been resolved.

CSCsq55397

The community string used while sending notification traps needs to be hard-coded as Public. The users who need to customize the community strings, changed the name of the strings from Public to a name of their choice.

Hence, the SNMP managers did not process the notification traps sent by DFM.

This problem has been resolved.

CSCsq67843

DFM did not support 10 Gigabit devices.

This problem has been resolved.

CSCsv21221

DFM could not recognize a trunk between two devices that were managed by DFM and DFM 1 servers.

This problem has been resolved.

CSCsx65722

The 6509 MSFC devices were discovered and pushed to a Known state by DFM. However, they went to Suspended state and were not monitored anymore. When you clicked the Resume button, the card went into Questioned state.

This problem has been resolved.

CSCsy90443

When you changed the host name of CiscoWorks Server, the option Manage By Groups did not work.

This problem has been resolved.

CSCsz08953

Unmanaged Interfaces used to revert to a Managed state after Device Rediscovery.

This problem has been resolved.

CSCsb05350

You could not customize the subjects of e-mail notifications.

This problem has been resolved.

CSCsz45181

In DFM, for CE devices, the Managed state was not preserved after Rediscovery.

This problem has been resolved.


Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].