Description

DFM 2.0.12 is a collection of updated files necessary to provide support for the devices listed in New Device Support.

Caution You cannot remove DFM 2.0.12 after installing it; to return to your original configuration, you will have to uninstall and reinstall DFM. Therefore, you should save your configuration before installing DFM 2.0.12 as described in
Installing DFM 2.0.12.

Downloading DFM 2.0.12

DFM 2.0.12 files are downloaded in a compressed form. To prevent overwriting of files in existing directories as well as ensure that adequate disk space is available, you should download the files to a temporary working area of your server, and then uncompress the files.

Note You can also use the Common Services Device Update function to download DFM 2.0.12. For more information, from the Common Services home page, select Software Center > Software Update and click Help.

Installing DFM 2.0.12

Caution You cannot remove DFM 2.0.12 after installing it; to return to your original configuration, you will have to uninstall and reinstall DFM. Therefore, you should save your configuration before installing DFM 2.0.12 as described in
Step 1.

Step 1 Make sure that you have a backup of your configuration, in case you need to revert back to it. (DFM 2.0.12 cannot be uninstalled.)

Step 2 Verify that DFM 2.0.10 or 2.0.11 is installed:

a. From the Common Services home page, select Software Center > Software Update.

b. In the Products Installed table, verify that the Device Fault Manager row lists version 2.0.10 or 2.0.11.

Step 3 Move to the directory in which the unzipped DFM files reside, and run the installation script by double-clicking cwdfm2_0_12_win.exe.

Step 4 Follow the prompts in the installation script. The options displayed by the installation script depend on your configuration.

Step 5 When the installation is finished, click Finish to exit the installer.

Step 6 Verify the installation:

a. From the Common Services home page, select Software Center > Software Update.

b. In the Products Installed table, click Device Fault Manager.

c. In the Patches Installed table, verify that the version corresponding to Device Fault Manager is 2.0.12.

Step 7 Rediscover any devices that are in the Unsupported state using Device Management > Rediscover/Delete from the DFM home page.

Step 8 Remove the distribution files from the temporary working area on your server.

Known DFM2.0.12 Problems

The following table describes the known problems in DFM 2.0.12. Unless otherwise specified, there is no workaround for these problems.

For a list of known problems in Device Fault Manager 2.0.11, refer to Readme for CiscoWorks Device Fault Manager 2.0.11 on Windows. You can view this document on Cisco.com by going to:

IDU20 and IDU21: Warning alert is not generated for Operationally Down Card.

When the Module Status is set to 3 for 1.3.6.1.4.1.9.5.1.3.1.1.10, Warning alert should be generated for an Operationally Down Card as per the Syntax of the MIB. It is not generated. But a Critical alarm is generated when the Module Status is set to 4.

CSCso70635

IDU20: In Normal state, a Critical alert is generated for Temperature.

When the value for chassisTempAlarm is set as 2 for this OID, Critical alert is generated for the following devices:

•2960-PD-8TT-L - 1.3.6.1.4.1.9.1.952

•2960-24LT-L - 1.3.6.1.4.1.9.1.951

Alerts must not be generated and the status must be Normal.

CSCso70617

IDU20: Card Operationally Down alarm is displaying two events instead of one.

When a card operationallydown alarm is generated for 1.3.6.1.4.1.9.9.117.1.2.1.1.2, AAD is displaying two events instead of one.

CSCsu44536

IDU21:Managed state is not displayed correctly in DDV page.

Launch the DDV page and click Processor or any other component. Change the Managed state from True to False. Component goes to Unmanaged state. But the status remains as True. It should be False.

CSCso52084

Support for revised MIB values should be provided.

Alerts are not generated for the Environment components like temperature, power, fan, and voltage of some revised Mib values. Warning alert is not generated for Fan in IDU21. Support for revised MIB values should be provided.

Resolved DFM Problems

The following table describes DFM problems that are resolved in DFM 2.0.12.