The analysis.cfg file is used to analyze the results sent by the client
monitor. Since you do not have a Xymon client on the client side, you need
to instead do the port testing from the Xymon server. This would be put in
the hosts.cfg file. See
https://xymon.sourceforge.io/xymon/help/manpages/man5/hosts.cfg.5.html
under the "Simple Network Tests" section. FTP, ssh and https tests are
already standardly built-in. Since you want to make sure ssh is closed,
use "!ssh" on the hosts.cfg line for the host. For your custom ports, you
could use syntax like ftp:571 if the response on port 571 is similar to
FTP. You can experiment by using telnet to the ports to see what kind of
response they give, such as "telnet host 571".
Tom
On Mon, Apr 22, 2024 at 8:37?AM <user-adff70a40333@xymon.invalid> wrote:
I may not fully understand, but I thought that analysis.cfg uses client
data sent from the xymon client on the system it is monitoring and
analysis.cfg controls what colors etc. that is generated from the client
data?
On Mon, Apr 22, 2024, at 9:51 AM, Kris Springer wrote:
analysis.cfg has built-in PORT tests. See instructions at
https://xymon.sourceforge.io/xymon/help/manpages/man5/analysis.cfg.5.html
Kris Springer
On 4/22/24 6:44 AM, user-adff70a40333@xymon.invalid wrote:
Hello,
I have a system that is running a rsyslog server on a non standard
port and is an appliance. I need to check that the several ports are
up and listening, however I can not install a client on the system.
The test would need to be initiated from the xymon server. I assume I
need a custom script, can someone point me in the right direction for
this. Heres nmap output. Preferably I'd like to check if the port
443, 517,8001, 8002,and 80003 are all open. If any of those are not
open, go red.
PORT STATE SERVICE
22/tcp closed ssh
443/tcp open https
517/tcp open XXXX
8001/tcp open XXXX
8002/tcp open XXXX
8003/tcp open XXXX