Table Of Contents

Configuring and Administering DFM (Basic)

Using DFM Configuration

Applying Changes

Performing Scheduling Tasks

Configuring the Daily Purging Schedule

Configuring Rediscovery Schedules

Suspending a Rediscovery Schedule

Resuming a Rediscovery Schedule

Adding a Rediscovery Schedule

Editing a Rediscovery Schedule

Deleting a Rediscovery Schedule

Configuring SNMP Trap Receiving and Forwarding

Enabling Devices to Send Traps to DFM

Enabling Cisco IOS-Based Devices to Send Traps to DFM

Enabling Catalyst Devices to Send SNMP Traps to DFM

Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs

Updating the SNMP Trap Receiving Port

Configuring SNMP Trap Forwarding

Configuring a Default SMTP Server

Configuring and Administering DFM (Basic)

---

These topics provide an introduction and overview of Device Fault Manager (DFM) basic configuration and administration tasks:

•Using DFM Configuration

•Applying Changes

•Performing Scheduling Tasks

•Configuring SNMP Trap Receiving and Forwarding

•Configuring a Default SMTP Server

Advanced configuration and administration tasks are addressed in Administering DFM (Advanced).

Using DFM Configuration

When you select the Configuration tab on the DFM home page, DFM displays several choices.

---

Note Your login determines which applications and folders are displayed to you. See Understanding Your User Role.

---

Table 7-1 lists the choices, shows where you can find the instructions and procedures for using each, and provides a brief description of what you can accomplish using the application.

Table 7-1 Configuration Folder Options 

Choices in the Configuration Folder		Description
Polling and Thresholds: See Configuring Polling and Thresholds.		Contains all options for controlling polling and threshold settings.
	Polling Parameters	Change polling intervals, timeouts, and retries by device group
	Managing Thresholds	Change thresholds, resetting the limits against which polled data will be compared
	Setting Priorities	Reprioritize customizable groups for polling and thresholds
	Apply Changes	Apply your Polling and Threshold changes •Start using updated polling parameters and threshold values •Resume polling for devices or device elements that were previously suspended
Other Configurations		Contains all other DFM system configuration choices.
	Rediscovery Schedule See Configuring Rediscovery Schedules.	Add, edit, suspend, resume, and delete rediscovery schedules.
	Group Config See Managing Groups.	View the rules that govern system-defined device groups. Maintain customizable polling and threshold groups. Create and maintain user-defined device groups.
	Daily Purging Schedule See Configuring the Daily Purging Schedule.	Change the time at which to start purging the Fault History database.
	Alerts and Activities Defaults See Configuring Views for the Alerts and Activities Display.	Create views.
	Logging See Configuring Logging.	Change the level of messages written to log files.
	SNMP Trap Forwarding See Configuring SNMP Trap Forwarding.	Change the port on which DFM listens for SNMP traps.
	SNMP Trap Receiving See Updating the SNMP Trap Receiving Port.	Set a host and port number as a recipient for pass-through traps.
	Default SMTP Server See Configuring a Default SMTP Server.	Change or enter a default server to use for e-mail notifications.

Applying Changes

---

Note Your login determines whether you can perform this operation.

---

Changes to polling parameters and threshold values do not take effect until you apply changes, thereby reconfiguring DFM to use the new values. Similarly, after you resume devices or device components that were suspended from polling, you must apply changes for the device elements to be polled.

Before You Begin

Applying changes is a CPU-intensive event that may take between one and five minutes to complete. Therefore, to minimize system impact, consider doing the following when possible:

•Consolidating changes to polling parameters and threshold values, thereby limiting the number of times you will need to apply them.

•Applying changes during a low-usage time.

---

Step 1 Select the DFM Configuration tab and then select Polling and Thresholds > Apply Changes.

The Apply Changes page appears.

Step 2 Click Yes to apply the changes:

•If another user has already initiated applying changes, a message is displayed and changes are not applied again.

•If, since the last time changes were applied, polling parameter settings or threshold values have not changed and devices have not been suspended and then resumed, changes will not be applied.

---

---

Tip You cannot directly verify that changes have been applied. However, you can do so indirectly. For example, in response to an event, you change a threshold value and apply changes. After DFM finishes applying changes, you can see whether DFM clears the event.

---

For more information, see the following topics:

•Configuring Polling and Thresholds

•Saving and Applying Changes

Performing Scheduling Tasks

When DFM is first installed, most tasks listed in Table 7-2 are scheduled by default to ensure that they do not run concurrently. You can configure the schedules for these tasks to meet the requirements of your site. However, you should still avoid running them concurrently.

Table 7-2 Scheduling Considerations 

Configuration Task	Default Schedule	Comments and Notes
Database purging	Run daily at midnight.	The amount of time it takes to purge the database depends on the size of the database.
Rediscovery	Run weekly on Monday at 2:00 a.m.	By default, rediscovery starts 2 hours after database purging.

In addition to configuring schedules with DFM, a system administrator can schedule database backups. Be careful while coordinating the database backup schedule to avoid running concurrently with the tasks listed in Table 7-2.

For more information about schedules, see the following topics:

•Configuring the Daily Purging Schedule

•Configuring Rediscovery Schedules

Configuring the Daily Purging Schedule

---

Note Your login determines whether or not you can perform this task. See Understanding Your User Role.

---

Data for Fault History remains in the DFM database for 31 days. Purging occurs every day to maintain only 31 days of data. You can select the time of day that purging begins. By default, purging begins at 00:00.

Before You Begin

Review the information in Performing Scheduling Tasks to ensure that daily purging does not conflict with the other scheduled jobs listed there.

Do not use the Common Services Job Browser to manage Rediscovery Schedules; use the DFM Daily Purging Schedule interface. If you suspend the DFM:DataPurge job using the Job Manager, the job is deleted from the DFM Daily Purging Schedule interface, which can be confusing to users.

---

Step 1 Go to the DFM home page and select Data Purge.

Step 2 Select the Purge Time:

•Hour—From 0 to 23

•Minute—From 0 to 50 in ten-minute intervals

The default purge time is 00:00.

Step 3 Click Apply.

---

You can check the status of the DFM data purge job from the Job Manager page each day after the job runs. To do so, go to the Common Services home page and select Server > Administration > Job Browser and find DFM:DataPurge under Job Type.

---

Note In DFM 3.0.2, unlike the previous versions, the Data Purge Settings can be backed up and restored.

---

For more information, see the following topics:

•Performing Scheduling Tasks

•Configuring Rediscovery Schedules

Configuring Rediscovery Schedules

---

Note Your login determines whether or not you can perform this task. See Understanding Your User Role.

---

DFM rediscovery probes the devices to discover their configuration and verify their manageable elements in inventory.

DFM contains a default discovery schedule that starts rediscovery on a weekly basis. Although you cannot modify the default discovery schedule, you can suspend it and add, modify, or delete additional schedules.

Suspending a Rediscovery Schedule

DFM includes a default rediscovery schedule, Default_Schedule. You cannot edit or delete Default_Schedule, but you can suspend it. To completely suspend rediscovery for a period of time, you may have to repeat this procedure to suspend more than one schedule.

---

Step 1 Go to the DFM home page and select Rediscovery Schedule.

The Rediscovery Schedule page appears.

Step 2 From the Rediscovery Schedule page, select a schedule that does not show Suspended as its status, and click Suspend.

The status for the schedule changes to Suspended and the schedule does not run until you resume the schedule. The schedule remains listed on the Rediscovery Schedule page until you delete it.

---

Resuming a Rediscovery Schedule

---

Step 1 Go to the DFM home page and select Rediscovery Schedule.

The Rediscovery Schedule page appears.

Step 2 From the Rediscovery page, select a schedule with a status of Suspended and click Resume.

The status for the schedule changes to Scheduled.

---

Adding a Rediscovery Schedule

Before You Begin

See Performing Scheduling Tasks to plan the rediscovery schedule for maximum efficiency and minimum system impact.

---

Step 1 From the DFM home page, select Rediscovery Schedule and click Add.

Step 2 Enter a name for the schedule.

Step 3 Select how often the schedule should run:

•Once

•Daily

•Weekly

•Monthly

By default, the Weekly option is selected.

Step 4 Select the date, hour, and minute on which to start the rediscovery schedule and click Next.

Step 5 Review the information on the Schedule Summary: Add page and click Finish.

The Rediscovery Schedule page appears, listing the new schedule.

---

Editing a Rediscovery Schedule

Before You Begin

See Performing Scheduling Tasks to plan the rediscovery schedule for maximum efficiency and minimum system impact.

---

Step 1 From the DFM home page, select Rediscovery Schedule.

Step 2 Select a rediscovery schedule with a status of Scheduled and click Edit.

---

Note You cannot edit Default_Schedule.

---

Step 3 You can modify how often the schedule runs and when the schedule starts:

•You can select how often the schedule should run.

•You can select the date, hour, and minute on which to start rediscovery.

Step 4 Click Next.

Step 5 Review the information on the Schedule Summary: Edit page and click Finish.

The Rediscovery Schedule page appears, listing the modified schedule.

---

Deleting a Rediscovery Schedule

---

Step 1 From the DFM home page, select Rediscovery Schedule.

Step 2 Select a rediscovery schedule and click Delete.

A confirmation dialog box appears.

---

Note You cannot delete Default_Schedule.

---

Step 3 Click Yes.

The job is removed from this page. However, it will continue to be listed in the Common Services Job Browser.

---

Configuring SNMP Trap Receiving and Forwarding

DFM can receive traps on any available port and forward them to a list of devices and ports. This capability enables DFM to work with other trap processing applications. DFM will only forward SNMP traps from devices in the DFM inventory.

It will not change the trap format—it will forward the raw trap in the format in which the trap was received from the device. However, you must enable SNMP on your devices and you must do one of the following:

•Configure SNMP to send traps directly to DFM

•Integrate SNMP trap receiving with an NMS or a trap daemon

To send traps directly to DFM, perform the tasks in Enabling Devices to Send Traps to DFM. To integrate SNMP trap receiving with an NMS or a trap daemon, follow the instructions in Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs.

The versions of SNMP traps supported by DFM are described in SNMP and ICMP Polling. For information on forwarding processed and pass-through traps, see Processed and Pass-Through Traps, and Unidentified Traps and Events.

---

Note The ports and protocols used by CiscoWorks are listed in Installation and Getting Started Guide for LAN Management Solution 3.0.

---

Enabling Devices to Send Traps to DFM

---

Note If your devices send SNMP traps to a Network Management System (NMS) or a trap daemon, see Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs.

---

Since DFM uses SNMP MIB variables and traps to determine device health, you must configure your devices to provide this information. For any Cisco devices that you want DFM to monitor, SNMP must be enabled and the device must be configured to send SNMP traps to the DFM server.

Make sure your devices are enabled to send traps to DFM by using the command line or GUI interface appropriate for your device:

•Enabling Cisco IOS-Based Devices to Send Traps to DFM

•Enabling Catalyst Devices to Send SNMP Traps to DFM

Enabling Cisco IOS-Based Devices to Send Traps to DFM

For devices running Cisco IOS software, enter the following commands:

(config)# snmp-server [community string] ro

(config)# snmp-server enable traps

(config)# snmp-server host [a.b.c.d] traps [community string]

where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the DFM server).

For more information, see the appropriate command reference guide.

---

Step 1 Log into Cisco.com.

Step 2 Select Products & Services > Cisco IOS Software.

Step 3 Select the Cisco IOS software release version used by your IOS-based devices.

Step 4 Select Technical Documentation and select the appropriate command reference guide.

---

Enabling Catalyst Devices to Send SNMP Traps to DFM

For devices running Catalyst software, provide the following commands:

(enable)# set snmp community read-only [community string]

(enable)# set snmp trap enable all

(enable)# set snmp trap [a.b.c.d] [community string]

where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the DFM server).

For more information, see the appropriate command reference guide.

---

Step 1 Log into Cisco.com.

Step 2 Select Products & Services > Cisco Switches.

Step 3 Select the appropriate Cisco Catalyst series switch.

Step 4 Select Technical Documentation and select the appropriate command reference guide.

---

Integrating SNMP Trap Receiving with Other Trap Daemons or NMSs

You might need to complete one or more of the following steps to integrate SNMP trap receiving with other trap daemons and other Network Management Systems (NMSs):

•If you are integrating DFM with a remote version of HP OpenView or NetView, you must install the appropriate adapter on the remote HP OpenView or NetView (see Installing and Getting Started with CiscoWorks LAN Management Solution 3.0. This guide also provides information on supported versions). You do not need to install any adapters if HP OpenView or NetView is installed locally.

•Add the host where DFM is running to the list of trap destinations in your network devices. See Enabling Devices to Send Traps to DFM. Specify port 162 as the destination trap port. (If another NMS is already listening for traps on the standard UDP trap port (162), use port 9000, which DFM will use by default.)

•If your network devices are already sending traps to another management application, configure that application to forward traps to DFM.

Table 7-3 describes scenarios for SNMP trap receiving and lists the advantages of each.

Table 7-3 Configuration Scenarios for Trap Receiving 

Scenario	Advantages
Network devices send traps to port 162 of the host where DFM is running. DFM receives the traps and forwards them to the NMS.	•No reconfiguration of the NMS is required. •No reconfiguration of network devices is required. •DFM provides a reliable trap reception and forwarding mechanism. •NMS continues to receive traps on port 162. •Network devices continue to send traps to port 162.
NMS receives traps on default port 162 and forwards them to port 162 on the host where DFM is running.	•No reconfiguration of the NMS is required. •No reconfiguration of network devices is required. •DFM does not receive traps dropped by the NMS.

Updating the SNMP Trap Receiving Port

By default, DFM receives SNMP traps on port 162 (or, if port 162 is occupied, port 9000). If you need to change the port, you can do so. DFM supports SNMP V1, V2, and V3 traps for trap receiving (although DFM only supports authNoPriv for V3 traps).

---

Step 1 From the LMS portal, select Other Configurations > SNMP Trap Receiving.

Step 2 Enter the port number in the Receiving Port entry box.

Step 3 Click Apply.

---

For a list of ports that are already in use, see Installation and Getting Started Guide for LAN Management Solution 3.0. If you have two instances of the DfmServer process running, traps will be forwarded from the first instance to the second instance.

Configuring SNMP Trap Forwarding

---

Note Your login determines whether or not you can perform this task. See Understanding Your User Role.

---

DFM will only forward SNMP traps from devices in the DFM inventory. DFM will not change the trap format—it will forward the raw trap in the format in which it was received from the device. All traps are forwarded in V1 format.

---

Step 1 From the DFM home page, select Trap Forwarding.

Step 2 For each host, enter:

•An IP address or DNS name for the hostname.

•A port number on which the host can receive traps.

Step 3 Click Apply.

---

For additional information, see Processed and Pass-Through Traps, and Unidentified Traps and Events.

Configuring a Default SMTP Server

---

Note Your login determines whether or not you can perform this task.

---

This SMTP server is used by default when you add or edit subscriptions for e-mail notifications or send e-mail notifications from the Alerts and Activities display. Common Services also provides a facility for specifying a default SMTP server. Specifying a default server here will override the setting used by Common Services.

---

Step 1 After selecting the Configuration tab, select Other Configurations > Default SMTP Server.

Step 2 Enter a fully qualified SMTP server name.

Step 3 Click OK.

---