Document ID: 25833
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Test for SMTP Request Receipt
Configuring DFM Mail Notifier
Step-by-Step Instructions to Configure Forwarded Email
Step-by-Step Instructions for Automatic DFM Mail Notification
Verify the Configuration
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
You can use the GUI to configure the Device Fault Manager (DFM) to send emails for all entries that appear in the monitor console.
Prerequisites
Requirements
Readers of this document should be familiar with DFM.
Before you attempt this configuration, verify these requirements:
-
DFM 1.1 or DFM 1.2 is installed and works
-
The alarm entries you want appear in the Monitor Console
-
Your mail server is configured as an SMTP server
-
Your mail server can receive SMTP requests. Perform the Test for SMTP Request Receipt, to verify. If the test is not successful, contact your mail administrator. Your mail server must receive SMTP requests before you proceed further.
Note:
-
For this exercise, banyan.cisco.com is the SMTP server. Substitute the IP address of your SMTP server.
-
The commands that you must type are in bold.
-
The responses from SMTP server appear in machine font.
-
If your SMTP server setup prevents your typeface from appearing on the screen, you should still see valid responses when you Enter.
-
Hello is spelled with only one L: helo.
-
Do not forget the . (dot) to complete the mail composition.
Components Used
The information in this document is based on these software and hardware versions:
-
DFM 1.1 or DFM 1.2
-
1720 router
-
smtpd that runs on Solaris 7
Note: You can use MS-Exchange or any other popular mail software as long as you enable SMTP.
The information in this document was created from the devices in a specific lab environment. All the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Test for SMTP Request Receipt
telnet banyan.cisco.com 25 Trying 172.18.123.123... Connected to banyan.cisco.com. Escape character is '^]'. 220 banyan.cisco.com ESMTP Sendmail 8.11.2/8.11.2; Mon, 22 Oct 2001 10:03:16 -0500 (EST) helo banyan 250 banyan.cisco.com Hello walnut.cisco.com [172.18.123.235], pleased to meet you mail from: foo@cisco.com 250 2.1.0 foo@cisco.com... Sender ok rcpt to: bar@cisco.com 250 2.1.5 bar@cisco.com... Recipient ok data 354 Enter mail, end with "." on a line by itself From: foo@cisco.com To: bar@cisco.com Subject: Good luck with DFMJ DFM is cool!!! 250 f18GhPv04316 Message accepted for delivery quit |
Configuring DFM Mail Notifier
In order to configure the mail notifier, you must perform these functions:
-
Confirm that the smtp server is OK
-
Test if emails can be sent ad-hoc from the monitor console
-
Configure parameters that relate to forwarded email
-
Test and confirm that emails are received
Step-by-Step Instructions to Configure Forwarded Email
In order to configure how to forward email, perform these steps:
-
From the monitor console, right click the alarm entries for which you want email notification.
-
Click Mail and the Mail Action screen appears:
-
Select Configuration and the Recipient Editor screen appears:
-
Enter the IP address or FQDN of your SMTP server.
-
Select a username OR accept the default, admin.
-
Enter the recipient information.
-
Click Create and the Mail Action dialog box appears:
-
Click OK and the Mail Action pop-up screen appears:
-
Check the email INBOX for the recipient and confirm that the mail is received.
-
This step confirms that DFM is able to send emails successfully to recipients.
Step-by-Step Instructions for Automatic DFM Mail Notification
In order to automatically send emails when a new entry appears in the monitor console, perform these steps:
-
Login to CW2000
-
Go to DFM > Administration > Fault Notification > Mail Notifier.
-
Make these changes:
-
Enable the Adapter
-
Add recipient
-
Enter the SMTP server IP Address or FQDN
-
-
After entering the information, the DFM Mail Notifier screen appears:
-
Click OK and the DFM Mail Notifier Settings screen appears:
-
When a new entry appears in the monitor console, check the INBOX for the recipient.
-
If the recipient receives no email, perform these steps:
-
Go to Server Configuration > Administration > Process Management > Stop Process
-
Select DfmMailNotifier (as shown in this graphic).
-
Wait a few minutes and start the process.
-
Verify the Configuration
Perform these steps to verify the configuration
-
Login to CiscoWorks
-
Go to Server Configuration > Administration > Process Management > Process Status
-
Verify that these processes are active:
-
DfmServer
-
DfmMailNotifier
-
-
When purple alarms appear in the monitor console, verfiy that email is received.
Troubleshoot
If you are having difficulty getting the notifier to work, try these steps:
-
Stop and then restart DfmMailNotifier.
If stop/restart DfmMailNotifier does not resolve the problem, stop and then restart the DfmServer and the DfmMailNotifier.
-
Launch the monitor console, right click on any alarm, and send mail. Confirm that this mail is received. If not, follow up with your mail administrator.
-
If you can send mails from the monitor console and are still unable to receive emails, open a case with the Technical Assistance Center.
Provide this information with the case:
-
DFM Version (from DFM monitor/Admin console, look under Help > About)
-
Operating system version information
-
If it is a new installation OR an active DFM mail adapter stopped working suddenly, send these two files:
-
sm_mail_notifier.log from /CSCOpx/objects/smarts/logs directory
-
mail_notify.conf from /CSCOpx/objects/smarts/conf/notifier directory
-
-
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for Network Management |
| Network Infrastructure: Network Management |
| Virtual Private Networks: Network and Policy Management |
Related Information
| Updated: Oct 21, 2004 | Document ID: 25833 |
