Collin, you're right - if it was just SMTP, that would be a great solution. I was using SMTP as an example service, but there are others in the clustered group that need to move, too.
Adam's point is exactly why I thought it would be good to throw the question out to the group... this exact situation has come up a bunch of times with our implementation of bb/hobbit/xymon, and every time the solution was an external cluster monitor script. The script checked the role of the server and reported data back from the active host using the hostname of an HA "host" (smtpHA in the example).
I was thinking was that if there is enough traction, we might come up with a group consensus of how xymon could handle this internally.
-dan
-----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Adam Goryachev Sent: Friday, June 22, 2012 3:08 AM To: xymon at xymon.com Subject: Re: [Xymon] Monitoring a simple cluster
On 22/06/12 15:51, Colin Coe wrote:
Crazy thought, but why don't you have smtp01 defined in DNS as an MX with priority or 10 and smtp02 defined in DNS as an MX with priority of 20.
You may have a perfectly valid reason for doing what you are doing, but simply having a primary and a secondary SMTP server would be simplest to administrator and to monitor.
Possibly due to the servers being used as the "smarthost" for random users sending emails via SMTP?
In any case, it would be interesting to see how this can be done, or how other people do it, since I've recently implemented a SAN system with an active + standby and would like to do a very similar thing.
Regards, Adam
-- Adam Goryachev Website Managers Ph: +61 2 8304 0000 adam at websitemanagers.com.au Fax: +61 2 8304 0001 www.websitemanagers.com.au
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon