Looks compelling. What do others here use to monitor round trip time? I hate having my users tell me email doesn't work when all I can really do it look at Exchange queues and only hop to the SPAM filter when someone tells me they've been expecting something but haven't seen it...
Dave > Ten bucks a month. Have not used them in a long time but they worked well > back in the old days. > > https://www.site24x7.com/mail-server-monitoring.html > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey > Sent: Monday, December 1, 2014 2:15 PM > To: '[email protected]' > Subject: [Exchange] Monitor Ex2010: > > Just had an issue over the weekend where two separate environments running > on top of our DMZ cluster stopped receiving external email after a > networking change on the ESX hosts. Both environments are setup with one > edge server and one HUB/CAS server (Ex2010 SP3 UR4 across all VMs). Emails > were timing out and senders were receiving 4.4.7 NDRs from their servers. > Restarting the Microsoft Exchange Transport service allowed mail to begin > flowing again. We understand how/why the issue occurred, however, none of > our regular SCOM alerts flagged any issues (no queue growth, ports are > open, services were running, etc.). After the fact, we noticed our 3rd > party spam filter was receiving "Message refused" errors. We are working > with the vendor to see if we can setup a baseline alert if/when this issue > comes up, but from a strictly Exchange perspective, we are lacking any > alerting on an event such as this. > > I'm curious if anyone else has setup either a SCOM monitor or perhaps > PowerShell script for testing external connectivity for something like > this? I use the Exchange connectivity test a lot in troubleshooting, but > that has to be performed manually. We'd like to setup an automated monitor > confirming mail delivery and returning values based on outcome. The part > I'm trying to figure out is the external portion, and how best to test > against it, since all internal traffic was fine and nothing on the server > itself showed any obvious problems. I have skimmed through a few of the > logs on the Edge server but do not see any real differences from pre/post > ESX host change that caused email to stop flowing. > > Any insight or even general direction is greatly appreciated. Thank you! > > -Geoff > Confidentiality Notice: This is a transmission from Community Hospital of > the Monterey Peninsula. This message and any attached documents may be > confidential and contain information protected by state and federal > medical privacy statutes. They are intended only for the use of the > addressee. If you are not the intended recipient, any disclosure, copying, > or distribution of this information is strictly prohibited. If you > received this transmission in error, please accept our apologies and > notify the sender. Thank you. > >
