Table G-1 DFM 1.2 Navigation Compared to DFM 2.0 Navigation
DFM 1.2.x
|
DFM 2.0
|
DFM 2.0 Description
|
Device Fault Manager > Monitoring Console
|
Device Fault Manager > Alerts and Activities
|
Alarm display from which you can:
• Launch tools, such as Fault History and Common Services Device Center
•Export data to a PDF file or a comma-separated-values file
•Print data
You can also change the display to show the information that interests you most, as follows:
•Select and create views, groups of device groups; use a view that contains the device groups of interest to you.
•Filter the display to show alerts based on their severity, status, and originating device.
|
Device Fault Manager > Administration > Administration Console
|
Device Fault Manager > Alerts and Activities
(From the Alerts and Activities display, click a device to open a Detailed Device View.)
|
From the Detailed Device View, you can:
•View device detail information
•Manage and unmanage devices
•Acknowledge alerts
•Annotate events
|
(From the CiscoWorks home page) Common Services > Device & Credentials Administration > Device Management
Device Fault Manager > Device Management > Device Selector
|
Device management, such as add, import, and delete.
Note In DFM 2.0, you import devices into a Device Credentials Repository (DCR) that is shared by CiscoWorks applications. You select devices from the DCR (or automatically synchronize devices with the DCR) for DFM to manage.
|
Device Fault Manager > Device Management >View Device Details
|
View device inventory.
|
Device Fault Manager > Configuration > Polling and Thresholds
|
Configure polling parameters and manage thresholds.
|
Device Fault Manager > Configuration > Polling and Thresholds > Operations
|
Reconfigure DFM to use updated polling parameters and threshold values.
|
Device Fault Manager > Administration > Device Discovery > Change Probe
|
Device Fault Manager > Device Management > Device Selector
Note The change probe process is obsolete in DFM 2.0.
|
Select devices manually or configure DFM to automatically synchronize device inventory with Device Credentials Repository (DCR).
Note Applications on different servers can use the same master DCR. For more information, see User Guide for CiscoWorks Common Services.
|
Device Fault Manager > Administration > Device Discovery > Rediscovery Schedule
|
Device Fault Manager > Configuration > Other Configurations > Rediscovery Schedule
|
•Edit the default rediscovery schedule.
•Create additional rediscovery schedules.
|
Device Fault Manager > Administration > Trap Configuration > Trap Receiving
|
Device Fault Manager > Configuration > Other Configurations > SNMP Trap Receiving
|
Change the port number that DFM uses to listen for SNMP traps.
Note Although the SNMP trap adapter file used in DFM 1.2 is still present in the DFM 2.0 filesystem, DFM 2.0 does not use it.
|
Device Fault Manager > Administration > Trap Configuration > Trap Forwarding
|
Device Fault Manager > Configuration > Other Configurations > SNMP Trap Forwarding
|
Configure hostnames and port numbers for trap forwarding.
Note Although the SNMP trap adapter file used in DFM 1.2 is still present in the DFM 2.0 filesystem, DFM 2.0 does not use it.
|
Device Fault Manager > Administration > Fault Notification > File Notifier
|
—
|
If you need to log events to a file, contact the Technical Assistance Center for the workaround for CSCsa83426.
|
Device Fault Manager > Administration > Fault Notification > Mail Notifier
|
Device Fault Manager > Notification Services > E-Mail Notification
|
Configure e-mail notifications for alarms.
Note Although the mail notifier file used in DFM 1.2 is still present in the DFM 2.0 filesystem, DFM 2.0 does not use it.
|
Device Fault Manager > Administration > Fault Notification > Trap Notifier
|
Device Fault Manager > Notification Services > Trap Notification
|
Configure trap notifications for alarms.
Note Although the trap notifier file used in DFM 1.2 is still present in the DFM 2.0 filesystem, DFM 2.0 does not use it.
|
Device Fault Manager > Administration > Fault History Database Sizing
|
Device Fault Manager > Configuration > Other Configurations > Daily Purging Schedule
|
Trim the Fault History database.
Note DFM 2.0 keeps 31 days of history and trims the database daily at the time you specify.
|
Device Fault Manager > Fault History:
•Search by Devices
•Search by Fault Conditions
|
Device Fault Manager > Fault History:
•Alert Filtering
–Search Alarm ID
–Search by Device
–Search by Group
•Event Filtering
–Search by Event ID
–Search by Device
–Search Alert ID
–Search by Group
|
Generate a 31-day Fault History report based on search criteria.
|
Device Fault Manager > Alerts and Activities > Tools > Fault History
|
Generate a 24-hour Fault History report for all alerts in your current view.
|
Device Fault Manager > Alerts and Activities
Click an an alert ID. The Alerts and Activities Detail display appears. In the Tools column next to the device component of interest, select Fault History.
|
Generate a 24-hour Fault History report for all events on a device component.
|
