Posts Tagged ‘mail server’

Fix NetApp AutoSupport

November 20, 2015

I come across this issue too often. You need to fetch some information for the customer from the My AutoSupport web-site and can’t because the last AutoSupport message is from half a year ago.

Check AutoSupport State

When you list the AutoSupport history on the target system you see something similar to this:

# autosupport history show

autosupport

Mail Server Configuration

If AutoSupport is configured to use SMTP as in this case, then the first place to check is obviously the mail server. The most common cause of the issue is blocked relay.

There are two things you need to make sure are configured: NetApp controllers management IPs are whitelisted on the mail server and authentication is disabled.

To set this up on a Exchange server go to Exchange Management Console > Server Configuration > Hub Transport, select a Receive Connector (or create it if you don’t have one for whitelisting already), go to properties and add NetApp IPs on the network tab.

exchange.png

Then make sure to enable Externally Secured authentication type on the Authentication tab.

receiveconnector

Confirm AutoSupport is Working

To confirm that the issue is fixed send an AutoSupport message either from OnCommand System Manager or right from the console and make sure that status shows “sent-successfull”.

# options autosupport.doit Test

# autosupport history show

autosupport2

 

DB2 notifications

February 16, 2012

Notifications are used in two parts of DB2 – Health Center and Task Center. Configuration is pretty simple. Go to Control Center – Task Center – Tools – Contacts and click on SMTP Server button. Fill here the FQDN of your mail server.  Then add contacts. After that you can use them during scheduled task configuration on Notifications tab.

To configure Health Center notifications go to Control Center – Health Center – Health Center – Configure – Alert Notification. In Configure Health Alert Notification window select instance and add contacts to Health Notification Contact List.

It may look like this is it. However, there is one issue we ran into. Sometimes DB2 sends emails using just a host name, without the domain part, like db2admin@sqldb2. All modern servers won’t allow sender address not in FQDN format. So we had to add DB2 server IP into white list on our Postfix mail server using check_client_access parameter.

DPM not sending alerts

November 1, 2011

I had funny experience today configuring notifications in Microsoft Data Protection Manager 2010. We have Postfix mail server instead of Exchange. Also we use SMTP authentication for outgoing mail from our users. DPM notifications configuration page has Username and Password fields for this. But simply using username and password of account registered in Postfix doesn’t work. It just says:

ID 2013

Details: Logon failure: unknown username or password

DPM needs this user to be registered in Active Directory. I have no idea why. So the simple solution to this was adding this account to AD with same password as in Postfix users database.

One more thing I’ve discovered is that for some reason Windows Server 2008 sends computer name without domain part in HELO command. Even though domain part is configured at System Properties. It wasn’t allowed in our mail server configuration. Solution to this was shifting of reject_non_fqdn_hostname option to the end of smtpd_recipient_restrictions (but before permit option) rule and addition of permit_mynetworks before it.