Re: Service polling issues

Hello.

yes, you can install both on the same box (and it is recomended,
actually, to run agent on server's box).

let me explain how it works:

all service checks a done thru the so-called "pooler node" -- box with
nxagentd+portcheck subagent. you can change pooler node on two levels:
node level(http://files.alk.lv/Clipboard01.png), or service level
(http://files.alk.lv/Clipboard02.png). default "pooler node" is set to
management server itself.

steps:
1) netxmsd send "Check SSH on host X.X.X.X port Y " command to nxagent
at "pooler node"
2) inside of nxagend this command in handled by portcheck subagent,
which connects to X.X.X.X:Y and then initiate ssh handshake
3) nxagend at "pooler node" sends responce back to the server

sorry for messy explanation, i'll write something more clear later on.
check wiki.netxms.org a bit later.

wbr, alex.

luc Van Hoeylandt wrote:
> Tnx for the info,
>
> Would it be possible to run nxagentd on the server that runs netxmsd and
> use that to poll the remote ssh service ? Or this there no other way
> then to install the nxagent on the machine itself ?
>
> Regards,
>
> Luc
>
> Near future netxms user :)
>
> On 12/1/05, *Igor Kopman* <igor.kopman_at_ctco.lv
> <mailto:igor.kopman_at_ctco.lv>> wrote:
>
> Hi,
>
>
>
> AFAIK You need service checker subagent to be complied and added
> into configuration of agent (if guys didn't implement it as part of
> core agent yet).
>
> At least in our environments only nodes with "Service Checker"
> subagent do the service polls.
>
>
>
> Regards,
>
> Igor Kopman,
>
> NetXMS user ;)
>
>
>
> ------------------------------------------------------------------------
>
> *From:* luc Van Hoeylandt [mailto:lucvht_at_gmail.com
> <mailto:lucvht_at_gmail.com>]
> *Sent:* Thursday, December 01, 2005 6:45 PM
> *To:* NetXMS Users
> *Subject:* [netxms-users] Service polling issues
>
>
>
> Hi,
>
> I have installed netxmsd on a debain sarge box and i am using the
> netxms console on windows xp to configure it. Monitoring through
> smnp seems to work fine. But adding services to a node (ssh for
> example) always results in status unknown, doing a manual poll ->
> status on the node shows:
>
> Statring status poll on network service ssh
> current status is unknown
> polling service from node xxx.xxx.xxx.xxx
> unable to check service status due to agent or communication error
> finished status poll on network service ssh
>
> Manually connecting to the ssh server from the monitor server works,
> the ssh server runs on port 8022 but i have updated this in the
> service TCP/UDP port settings as well
>
> Any clues what i'm doing wrong ?
>
> Regards,
>
> Luc
>
>
Received on Thu Dec 01 2005 - 22:22:52 EET