Host object redefinition

[Daniel Bareiro]

On Monday, 19 November 2007 23:25:52 -0600,
Marc Powell wrote:

> > I've several hosts behind a firewall and I'd like to monitoring they
> > with Nagios. These host haven't a public IP. Then, mi idea was to
> > configure the firewall to redirect the Nagios server conection at
> > specific port in the firewall ---one per host without public IP
> > behind the firewall--- to remote NRPE listen port from the remote
> > host.

> > Then, I'd like to redefine the host object to include a port
> > variable for call it in a general service definition.

> With nagios-3, yes, but not with nagios-2.

I'm using Nagios 3. Could you give me an example? I was searching
documentation about it, but I didn't found how to do it yet.

> With nagios-2, you could pass it as a $ARGx$ macro from each service
> definition or create an nrpe command{} definition per host.

Yes. It was first that I thought. But perhaps there would be a best form
to deal with it. :-)

Thanks for your answer, Marc.

Regards,
Daniel
-- 
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Etch - Linux user #188.598
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071121/6a8fdc32/attachment.sig>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
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