SMTP on multiple ports
list Elizabeth Schwartz
Can xymon smtp test on multiple ports out of the box? And if so is there a way to see which port is being requested? We've got a separate test defined in protocols.cfg and that works, but if the syntax were the same as for other network test, this should work also: 10.0.1.1 mailer.example.com # smtp smtp:8025 However I see only one test result with no port identified. Maybe protocols.cfg is just the way to do it, but the docs imply that network tests can take a port as a parameter)
list Tim McCloskey
Hi, Without looking at the docs I think what you are seeing is a host entry getting parsed and picking up the first 'smtp' statement it sees. So, out of the box for an individual host entry with multiple smtp statements, probably no. Then again, it is an open source project, so 'out of the box' has a different meaning:) If you want to add your own tests it's fairly simple, but I don't think you can extend the single smtp gem with multiple ports on the same host. You can have tests with different host:port pairs or add a column with your own tests. Depends on if you want the screen to draw more gems horizontally, or increase the host count (vertically). Regards, Tim
▸
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Elizabeth Schwartz [user-c61747246f66@xymon.invalid]
Sent: Tuesday, May 03, 2011 12:05 PM
To: xymon at xymon.com
Subject: [Xymon] SMTP on multiple ports
Can xymon smtp test on multiple ports out of the box? And if so is
there a way to see which port is being requested?
We've got a separate test defined in protocols.cfg and that works, but
if the syntax were the same as for other network test, this should
work also:
10.0.1.1 mailer.example.com # smtp smtp:8025
However I see only one test result with no port identified.
Maybe protocols.cfg is just the way to do it, but the docs imply that
network tests can take a port as a parameter)
list Phil Crooker
▸
Can xymon smtp test on multiple ports out of the box? And if so is there a way to see which port is being requested? We've got a separate test defined in protocols.cfg and that works, but if the syntax were the same as for other network test, this should work also: 10.0.1.1 mailer.example.com # smtp smtp:8025 However I see only one test result with no port identified. Maybe protocols.cfg is just the way to do it, but the docs imply that network tests can take a port as a parameter)
Well at the risk of being wrong (yet again), I would think you'd need to call it by a different name, so smtp and smtp8025 (or whatever). You'd need to define this in protocols.cfg. You could then do a "chat" like the one for smtp in protocols.cfg and get a result, rather than just a connect. [smtp] send "mail\r\nquit\r\n" expect "220" options banner port 25 [smtp8025] send "mail\r\nquit\r\n" expect "220" options banner port 8025
list Buchan Milne
▸
On Tuesday, 3 May 2011 21:05:27 Elizabeth Schwartz wrote:
Can xymon smtp test on multiple ports out of the box? And if so is there a way to see which port is being requested? We've got a separate test defined in protocols.cfg and that works, but if the syntax were the same as for other network test, this should work also: 10.0.1.1 mailer.example.com # smtp smtp:8025 However I see only one test result with no port identified. Maybe protocols.cfg is just the way to do it, but the docs imply that network tests can take a port as a parameter)
Yes, but that doesn't mean that you can use the same "test" twice and get separate pages. If you just wanted to test SMTP on 8025, then smtp:8025 would be for you. In our case, we want to be able to separately monitor different SMTP services (e.g. report on their availability separately) and so we have duplicate definitions in bb-services (yes, the box testing our SMTP services is running 4.2.x). Regards, Buchan