NSClient++. Monitoring the devices behind the Firewall.

[Jim Avery]

On 15 March 2011 13:47, C. Bensend <benny at bennyvision.com> wrote:
>
>> If you're looking to do this without cooperation from the client
>> and their security folks, you're going to run into problems.  If
>> they want you to monitor their hosts, they have to provide some
>> manner of accessing them.
>
> Just to be thorough, passive monitoring is also a possibility.
> In that case, each of the clients would be configured to send the
> service check results to the Nagios server, and would probably
> not require any changes to the firewall.
>
> However, I choose to use active monitoring, so I cannot help
> with that setup, nor would I necessarily recommend it.


I would echo what Benny said there having tried it myself.  Passive
monitoring is possible, and fairly easy to set up using the NSClient++
agent, but can be more trouble than it is worth as whenever you need
to make any change you have to log on to the remote server to change
the NSClient++ config.  If it's behind two firewalls then I would
guess that might not be easy.

If it's a large site with lots of servers, I would maybe consider
deploying a Nagios server on that site so there is only then one node
which needs to communicate back and forth with your central Nagios
server.  As ever, there are lots of different ways you can slice and
dice this problem.

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null