I have identified and confirmed with 2 different HPE MSA 2040 SANs an issue with SMTP notifications. I’ve identified the issue with multiple firmware versions (even the latest version as of the date of this article being written). The issue stops e-mail notifications from being sent from the MSA 2040 when the SAN is configured with some SMTP relays. This issue also occurs on HPE MSA 2050 arrays, as well as HPE MSA 2052 arrays.
The main concern is that some administrators may configure the notification service believing it is working, when in fact it is not. This could cause problems if the SAN isn’t regularly monitored and if e-mail notifications alone are being used to monitor its health.
Configuration:
-MSA 2040 (2050/2052) Dual Controller SAN configured with SMTP notifications
-SMTP destination server configured as EXIM mail proxy (in my case a Sophos UTM firewall)
Symptoms:
-Test notifications are not received (even though the MSA confirms OK on transmission)
-Real notifications are not received
-Occasionally if numerous tests are sent in a short period of time (5+ tests within 3 seconds), one of the tests may actually go through.
Events and Logs observed:
/var/log/smtp/2016/06/smtp-2016-06-20.log.gz:2016:06:20-20:44:29 SERVERNAME exim-in[16539]: 2016-06-20 20:44:29 SMTP connection from [SAN:CONTROLLER:IP:ADDY]:36977 (TCP/IP connection count = 1)
/var/log/smtp/2016/06/smtp-2016-06-20.log.gz:2016:06:20-20:44:29 SERVERNAME exim-in[18615]: 2016-06-20 20:44:29 SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[SAN:CONTEROLLER:IP:ADDY]:36977 input=”NOOP\r\n”
Resolution:
To resolve this issue, I tried numerous things however the only fix I could come up with, is configuring the SAN to relay SMTP notifications through a Exchange 2013 Server. To do this, you must create a special connector to allow SMTP relaying of anonymous messages (security must be configured on this connector to stop SPAM), and further modify security permissions on that send connector to allow transmission to external e-mail addresses. After doing this, e-mail notifications (and weekly SMTP reports) from the SAN are being received reliably.
Additional Notes:
-While in my case the issue was occurring with EXIM on a Sophos UTM firewall, I believe this issue may occur with other E-mail servers or SMTP relay servers.
-Tried configuring numerous exceptions on the SMTP relay with no effect.
-Rejected e-mail messages do not appear in the mail manager, only the SMTP relay log on the Sophos UTM.
-Always test SMTP notifications on a regular basis.
While most of us frequently deploy new ESXi hosts, a question and task not oftenly discussed is how to properly decommission a VMware ESXi host. Some might be surprised to… Read More
This guide will outline the instructions to Disable the VMware Horizon Session Bar. These instructions can be used to disable the Horizon Session Bar (also known as the Horizon Client… Read More
Normally, any VMs that are NVIDIA vGPU enabled have to be manually migrated with manual vMotion if a host is placed in to maintenance mode, to evacuate the host. While… Read More
You may experience GPU issues with the VMware Horizon Indirect Display Driver in your environment when using 3rd party applications which incorrectly utilize the incorrect display adapter. This results with… Read More
Today we're going to cover a powerful little NAS being used with VMware; the Synology DS923+ VMware vSphere Use case and Configuration. This little (but powerful) NAS is perfect for… Read More
Today we'll go over how to install the vSphere vCenter Root Certificate on your client system. Certificates are designed to verify the identity of the systems, software, and/or resources we… Read More
View Comments
Ha, it's funny because I identified the same email issue with my HP MSA 2040 last week.
The notification emails come through the SMTP relay but the weekly log emails do not.
I am using the Server 2012 built in relay service.
I've only had one log email come through but the attachments were unreadable.
Hi Dave,
I know, it's kind of a big issue... I'm kind of surprised it hasn't been fixed.
As far as the weekly reports go, do you have them turned on? By default I don't think they are.
Cheers
Stephen,
Yes I turned the weekly reports on, and they are not coming through.
Also I do not have an exchange server as we use Google for our email, so I'm kind of between a rock and a hard place at the moment.
I guess I have to log into the device and check the logs manually.
Hi Dave,
Does your ISP have an SMTP relay that it allows it's customers to use?
The trick is to keep trying different SMTP Servers or Relays that you have access to, until you find one that works! :)
I'm actually super thankful that it worked with Exchange, I was lucky that it was an easy work-around for me!
Cheers
do we know if this has been resolved yet? as we don't have exchange only an internal smtp relay server.
I used postfix instead of exim, the problem has been resolved.
Hi Naoki,
Thanks for letting us know! This information will help others!
Cheers,
Stephen
Still an issue today with latest firmware (GL225R003)
Hello all,
it seems, there is the same problem with HPE ILO...
Regards
Andreas
Yeah, it seems that it doesn't work at all. It doesn't even send a shred of a packet to anywhere. That's a real shame. Like a real one. The firmware of every part of the system is up to date btw.
Hi
We are experiencing the same issue with HP MSA 2052. What gives? We are using exchange 2010 anonymous relay receive connector. Also tried free smtp2go open relay.
None of them works!!! What gives??
We are on the latest firmware
OK
I think I found the answer and it is SO STUPID. Thank you HP for making simple things so difficult!
I configured out exchange 2010 to allow relaying and tested it successfully using a different server. Then I went to HP MSA 2052 and configured notification but it refused to work. Here is how I fixed it
1. If you are making a change under MSA notification screen; click on APPLY first before clicking on "test" button
2. here is the answer to this whole problem. At least for me. Under MSA notifications settings; you must choose "critical, error, warning, resolved, informational" > Ensure that it is applied > click on "Send Test Event" = Success
If you choose any option other than "critical, error, warning, resolved, informational" then your test will fail.
Set it back to "critical, error, warning" and save it when you are happy with test results. I wish I can paste screen shots but I can't.
Thanks
Thank you all
Wow, simply amazing! Same issue here, pulling my hair out trying to get a test email. set it to ....., informational and I get the test email. Mikey, are you saying that you are now receiving critical, error, warning, resolved emails properly after changing it from ...,..., informational?
Thanks
Rob
Hi
Correct. Setting the option to “critical, error, warning, resolved, informational” will allow the test emails to go through and work properly. Assuming that you have setup a server such as exchange to allow relaying.
I did forget to mention that we have the latest & greatest firmware too.
This is so stupid and beyond idiotic......
Thanks
Thank you, Mikey! I was also banging my head against this one. Never had to do this with my HP P2000 or 2012i arrays. The test used to work on any setting. This is dumb.
yes, thanks a lots, I try selecting all event, and instantly work fine.