CiscoWorks Device Fault Manager

CiscoWorks Device Fault Manager 3.0

  • Viewing Options

  • PDF (104.1 KB)
  • Feedback

Product Overview

CiscoWorks Device Fault Manager (DFM) is an application provided in the CiscoWorks LAN Management Solution (LMS). CiscoWorks DFM offers real-time fault monitoring and management that allows network operations personnel to poll and monitor a network at each device level and to analyze device events for determining where and when a fault has happened. CiscoWorks DFM allows users to monitor the fault conditions from devices through an online graphical display system as well as through notification services that can forward events to other management stations.
CiscoWorks DFM offers a number of important management features that enhance the fault monitoring of a Cisco network. Its capabilities include:

• Device configuration and management

• Alerts and activities

• Notification services

• Fault history

• General configurations

New Features in CiscoWorks DFM 3.0

New features in CiscoWorks DFM 3.0 include:

• Increased scalability; CiscoWorks DFM now supports up to 5000 devices from a single server. The Alerts and Activities Details (AAD) window is also enhanced to cover all the device issues by providing paging tables.

• Integration with the CiscoWorks LMS Portaland CiscoWorks Assistant utilities for more complete device information. CiscoWorks LMS Portal replaces the CiscoWorks homepage as the default homepage for CiscoWorks LAN Management Solution. CiscoWorks LMS Portal provides quick status information on devices, the network, and the system. Similarly, CiscoWorks Assistant provides workflows that integrate key CiscoWorks LMS application functionality. These help users to deploy, operate, and troubleshoot the CiscoWorks LMS system.

• Capability of bulk managing and unmanaging ports, interfaces, IP addresses, memory, and processors.

• Capability of unmanaging IP addresses. The Detailed Device View (DDV) now lists IP addresses supported on all devices and allows users to unmanage them one at a time.

• Configurable filters for customized device import: Users can create customized filters that control device import. Devices must meet the filter criteria in order to be automatically imported rather than a simple bulk import when automatic synchronization is active.

• Usability enhancements to Fault History.

• Group creation based on interface and MIB types and also descriptions.

• Filtering over the Alerts and Activities Details window: Wildcard searches are now supported over AAD.

Device Configuration and Management

Device configuration and management involve keeping the inventory of devices that CiscoWorks DFM monitors up to date. Before devices can be in the CiscoWorks DFM inventory, they must be added to the Device and Credentials Repository (DCR). The DCR is a centralized device repository for sharing device information across multiple CiscoWorks management servers.
Users can configure whether all DCR devices are automatically added to the CiscoWorks DFM inventory or whether DCR devices must match customized filters that the user creates in order to be added; or the user can manually add individual DCR devices to the CiscoWorks DFM inventory. Synchronization is controlled using the Device Import page by default where CiscoWorks DFM adds all DCR devices to its inventory. The DCR is the front end for adding devices to and exporting devices from CiscoWorks management servers and for modifying device credentials.
CiscoWorks DFM provides a user interface for performing the following operations on devices in the CiscoWorks DFM inventory:

• Viewing device details

• Rediscovering devices

• Suspending and resuming CiscoWorks DFM device management

• Deleting devices (local delete) when manual DCR synchronization is being used

The following scenario describes the process for managing devices:

1. Devices are added from the DCR to the CiscoWorks DFM inventory.

2. CiscoWorks DFM obtains basic information from the DCR.

3. CiscoWorks DFM discovers a device and adds its manageable elements to its inventory, placing the device and its elements into the appropriate CiscoWorks DFM system-defined groups.

4. By default, CiscoWorks DFM performs rediscovery on a weekly basis. A user can update the default discovery schedule or add new discovery schedules.

Table 1 summarizes the major features and benefits for device configuration and management.

Table 1. Features and Benefits of CiscoWorks DFM Device Configuration and Management



Wide range of elements managed by CiscoWorks DFM

By default CiscoWorks DFM manages interfaces, ports, and IP addresses. CiscoWorks DFM also manages chassis, cards, fans, power supplies, route switch modules, memory, processors, Simple Network Management Protocol (SNMP) agents, and sensors.

Common device repository

CiscoWorks DFM uses DCR as a baseline repository for building the device inventory, and by default all DCR devices are managed by CiscoWorks DFM.

Importing and exporting of devices

Users can import all devices into the CiscoWorks DFM inventory from DCR or can even put a filter for selective import. Once the devices are part of the CiscoWorks DFM inventory, they can be rediscovered for verification. Users can manually import and export devices using CSV or XML formats too.

Viewing and editing configurations

Typically, after rediscovery, the manageability elements are configured in the inventory for regular polling. However, users can configure the SNMP timeout and retry counts as well as delete devices from the CiscoWorks DFM inventory if needed.

Collecting device events

CiscoWorks DFM collects data from devices by SNMP v1, SNMP v2C, and SNMP v3 and Internet Control Message Protocol (ICMP)-based polling. Data is collected by both active polling as well as by listening to traps. The frequency of collection depends on the user-defined configuration. The collected data is used for the management station to compute events and display the network status in terms of faults.

Alerts and Activities

The Alerts and Activities Details window provides a consolidated real-time view of the operational status of the user network. When a fault occurs in the network, CiscoWorks DFM generates an event. All events occurring on the same device are rolled up into a single alert. Users can also use notification services to change an event name to something that is more meaningful. When an alert occurs on an element in the users' active view (a logical group of devices), it is displayed on the AAD window. Users with the necessary privileges can customize the view to include only those device groups that are important.
From the AAD window, the user can also:

• Drill down into an alert to see what events caused the alert and add alert annotations for other users to read

• Drill down into specific events for MIB attribute values

• Open a Detailed Device View to examine device components and suspend or resume monitoring them

• Use tools such as CiscoWorks CiscoView, user tracking (if CiscoWorks Campus Manager is installed), and Fault History.

Users can see which components of the device are in the CiscoWorks DFM manageable inventory as follows: After a user locates the device on the AAD window, the user can select it and open a DDV. The DDV displays the manageable components of the device, and if users have the necessary privileges, they can suspend monitoring of a device component then resume monitoring once the device analysis or correction is made. Suspended devices are moved to the Suspended Devices View.

Notification Services

In addition to watching network conditions as they change on the AAD window, the user can use notification services to automatically notify other users and systems when specific changes occur on selected devices. To do so, users can create subscriptions for e-mail notifications, CiscoWorks DFM-generated SNMP trap notifications, or syslog notifications. Users can also change event names to names that are more meaningful, and these names will be reflected in the CiscoWorks DFM displays and notifications.
CiscoWorks DFM subscriptions consist of:

• Alerts and events: For events, the subscription can contain an event set, which lists the specific events of interest.

• A notification group: The notification group lists the devices (or device groups) and alert/event severity levels of interest.

Users can add, modify, and delete subscriptions at any time to disseminate the status and severity of alarm and event changes.

Fault History

Fault History provides the history of CiscoWorks DFM events and alerts. The stored history includes alert information and annotations (informational text entered by CiscoWorks DFM users) and event information and properties (component name and MIB attributes). The user can start Fault History in the following ways:

• From the CiscoWorks DFM AAD window, the user can generate a Fault History display with information about alerts and events from the last 24 hours.

• From the CiscoWorks DFM homepage, the user can select Faults - - Fault History. This method provides historical information about all alerts and events in the Fault History database. The Fault History database keeps information for the alerts and events that occurred within the last 31 days.

• From CiscoWorks LMS Portal, the user can select Device Troubleshooting - - Device Center. From here, the user can select a single device and generate a 24-hour or 31-day display.

The user can use Fault History to generate customized tabular displays of specific alerts, specific events, event dates, and event severity.

General Configurations

The configuration pages provide a centralized location for all CiscoWorks DFM configuration tasks. Configuration tasks are divided into two categories: Polling and Thresholds, and Other Configurations.

• Polling and Thresholds: Contains functions to adjust polling and threshold settings on devices, ports, and interfaces.

• Other Configurations: Includes system administration tasks, such as configuring rediscovery schedules; logging levels, views for the AAD window, trap forwarding and receiving; and selecting a Simple Mail Transfer Protocol (SMTP) server. In addition, the user can perform group management from Other Configurations.

System Requirements

Please refer to the CiscoWorks LAN Management Solution 3.0 product data sheet, under the Product Literature section at, for specific hardware and software server and client requirements.

Ordering Information

CiscoWorks Device Fault Manager is part of the CiscoWorks LAN Management Solution. CiscoWorks LMS is available for ordering through regular Cisco sales and distribution channels worldwide. To place an order, visit the Cisco Ordering Home Page.

Service and Support

Using the Cisco Lifecycle Services approach, Cisco and its partners provide a broad portfolio of end-to-end services and support that can help increase your network's business value and return on investment. This approach defines the minimum set of activities needed, by technology and by network complexity, to help you successfully deploy and operate Cisco technologies and optimize their performance throughout the lifecycle of your network.

For More Information

For more information about the CiscoWorks Device Fault Manager application, visit, contact your local Cisco account representative, or send an e-mail to the product marketing group at