How To Troubleshoot NetGuardian Email Alarms - Part 2

Double-check email alarm configuration

If you're not getting email alarms, the first step is to double-check that the NetGuardian is correctly configured to send email notifications.

Connect to the NetGuardian using the Web Browser Interface and verify these four configuration items:

Configure the NetGuardian's email address
Figure 3: Confirm the NetGuardian's email address

Has the NetGuardian been assigned an email address in the correct format?
To check, click Edit to open the Edit menu and the System screen.
The username portion of the NetGuardian's email address (the part before the "@" sign should be entered in the Name field. The domain portion of the NetGuardian's email address (the part after the "@" sign) should be entered in the Location field.

Both parts of the NetGuardian's email address should be in the correct format -" that is, they can't contain the characters < > ( ) [   ] \ . , ; : @ " or any spaces, carriage returns or line feeds.

Note: Usually, the NetGuardian's email address doesn't have to correspond to an actual email account. But if your email server requires email validation, then the NetGuardian's address must be a working email address.

Configure email recipients' email addresses
Figure 4: Confirm the alarm recipient's email address

Is the email address of the alarm recipient entered correctly?
To check, click Pagers on the Edit menu. The Type should be set to Email. The recipient's domain should be entered in the Phone/Domain field. The recipient's username should be entered in the Pin/Rcpt/Port field. The IP address of the email server should be entered in the IPA field.

Make a note of the Pager ID assigned to the alarm recipient. You need to know this to check alarm configuration.

Enter the NetGuardian's password in the Pagers screen
Figure 5: If the NetGuardian needs to provide a password to access the email server, enter it in the Pagers screen

Does the NetGuardian need a password?
Check with your network administrator to see if the NetGuardian needs a password to access the email server. If it does, then you need to configure the Pagers screen differently. Enter the alarm recipient's full email address in the Phone/Domain field and the NetGuardian's password in the Pin/Rcpt/Port field, as shown in Figure 5.

Confirm alarms are set to page
Figure 6: Confirm that the alarm is configured to send a page

Are alarms configured to send a page?
To check, click Base Alarms and/or Analogs on the Edit menu. Every alarm point has an field for entering the Pager ID of the Primary and Secondary alarm recipients. Make sure the correct Pager ID is entered in each.

Ping the email server

If the NetGuardian's email configuration is OK, but email alarm notifications don't go through, ping the email server to verify you have an IP connection. (Important: ping from the NetGuardian, not from your own PC.)

Unsuccessful ping of the email server
Figure 7: If your email alarms aren't getting through, there may be a problem with the IP connection to the email server
  1. Start a new Telnet connection to the NetGuardian or press Esc to exit the debug tool.
  2. Choose C)onfig, then P)ing.
  3. You will be prompted to type the IP address of the email server. (See Figure 7.) Type the IP address and press Enter.
  4. If you can't ping the email server, you either don't have an IP connection to the server you don't have the correct IP address. Consult your network administrator.

If you can ping successfully, but email does not go through, your ping target is either not an email server or it's not the right kind of email server. The NetGuardian only supports Send Mail Transfer Protocol (SMTP) servers, not Outlook Exchange or Lotus Notes servers. Consult your network administrator to get access to an SMTP server.

Return to How to Troubleshoot NetGuardian Email Alarms, Part One ...


NetGuardian: SNMP Traps, Email Notification and More ...

Email alarm notification and comprehensive debug tools are just part of the NEBS-certified NetGuardian 832A.. Mediate contact closures to SNMP Traps access remote site equipment through terminal server ports ... learn everything the NetGuardian 832A can do for you.

See Full Specifications of the NetGuardian 832A

More Helpful Troubleshooting Articles

How to Identify Pinouts, with or without a Blinker Box
Alarm Monitoring Solutions from DPS Telecom
List Of Debug Options For The NetGuardian
Unable To Proxy Through NetGuardian To Another Device
Testing RS232 Serial Using A Screwdriver Or Paper Clip
Verify NetGuardian E-mail Notifications
Wiring Problems - RTU Doesn't Detect Alarms

Need a Quote?

Get it by: 6:45 PM Monday (today)

Now: 9:42 AM
Next Step:
Send Us Your Quote Request
9:47 AM Monday
We'll Start Work on Your Detailed Quote
6:45 PM Monday
Get Your Quote (Email PDF)

It's 9:42 AM on Monday at our Fresno, CA, USA headquarters. We can start on your quote right away.

Would you rather just call us? We're in the office right now. Call 1-800-693-0351.

Get a Quote