Re: [Nagios-users] Passive monitoring multiple servers with 1 NAT IP (SOLVED)
Hi, thanks to those who replied, the issue is now resolved. I had 2 clients configured on the Nagios server with the same IP, as soon as I changed those IPs on the server side to invented IPs that were different everything started to work as expected, cheers Andy. -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Passive monitoring multiple servers with 1 NAT IP
On 02/12/11 18:14, a.sm...@ukgrid.net wrote: Hi, in the case where I want to monitor several servers in a remote office where all outbound traffic from that office originates from a single IP (NAT) is there any way I can monitor those with Nagios without putting a Nagios server in the remote office? On the face of it it would seem impossible as Nagios identifies hosts by their IP (and therefore each needs a unique IP) but would be good to get that confirmed or otherwise, thanks for any ideas, Andy. I've had a similar situation in one of my projects ,and it is solvable in one of 2 methods : 1 ) if you NAT server is a linux box - use the nrpe on that box to trigger the checks to all other boxes in the network and send back to the Nagios box. 2) Port forwarding - assign each machine a port and configure the host with the custom macro _NRPEPORT and thus the firewall send a query on the port to the assigned hosts in the NAT listing . Assaf -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Passive monitoring multiple servers with 1 NAT IP
Quoting Jim Avery: The send_nsca transmission identifies the host to Nagios so it won't matter if the address is NATted. Hi Jim, ok great if its possible, however I did try setting this up and it didnt seem to work. I am using the NSClient++ on Windows servers, and under the NSCA section I have defined what is described as LOCAL HOST NAME correctly on each client. However when both clients are configured on the Nagios server updates are received to one and not the other, which makes me think its just asscoiating all inbound messages with the first matching IP (I have defined each host with an IP, I guess that is required too isnt it?), If it isn't to do with the host definition having an IP defined then maybe I made some other config mistake, I can double check it all on Monday. thanks Andy. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Passive monitoring multiple servers with 1 NAT IP
On 3 December 2011 17:46, a.sm...@ukgrid.net wrote: ok great if its possible, however I did try setting this up and it didnt seem to work. I am using the NSClient++ on Windows servers, and under the NSCA section I have defined what is described as LOCAL HOST NAME correctly on each client. However when both clients are configured on the Nagios server updates are received to one and not the other, which makes me think its just asscoiating all inbound messages with the first matching IP (I have defined each host with an IP, I guess that is required too isnt it?), The 'address' directive in the host definition is mandatory, yes, but you can put anything in there you like. If you are not doing any active checks (and the active checks you might end up doing are check_dummy anyway), then you can put what you like in there - it won't be used for anything. If it isn't to do with the host definition having an IP defined then maybe I made some other config mistake, I can double check it all on Monday. It sounds like it's probably some simple problem with the config on the host which isn't working, yes. Sometimes it helps to get nsca (on the Nagios server) to write some debug to syslog. I can't remember off-hand how to do that, but it's probably found in /usr/local/nagios/etc/nsca.ini or similar or if not, in the xinetd entry for nsca which if I recall is in /etc/xinetd.d/nsca . Check the nsclient.log file on the Windows system too, and make sure there's nothing obvious in there. Upper/Lower case is important for the host name so what you have in the Nagios host definition must match what the agent is sending. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Nagios-users mailing list Nagios-users@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
[Nagios-users] Passive monitoring multiple servers with 1 NAT IP
Hi, in the case where I want to monitor several servers in a remote office where all outbound traffic from that office originates from a single IP (NAT) is there any way I can monitor those with Nagios without putting a Nagios server in the remote office? On the face of it it would seem impossible as Nagios identifies hosts by their IP (and therefore each needs a unique IP) but would be good to get that confirmed or otherwise, thanks for any ideas, Andy. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Passive monitoring multiple servers with 1 NAT IP
On 2 December 2011 18:14, a.sm...@ukgrid.net wrote: Hi, in the case where I want to monitor several servers in a remote office where all outbound traffic from that office originates from a single IP (NAT) is there any way I can monitor those with Nagios without putting a Nagios server in the remote office? On the face of it it would seem impossible as Nagios identifies hosts by their IP (and therefore each needs a unique IP) but would be good to get that confirmed or otherwise, Yes you can do that no problem. Send the checks to the Nagios server using send_nsca and configure all the hosts in Nagios with passive host and service checks. You can use freshness checking to alert you if no checks have been received at all lately from the remote host. The send_nsca transmission identifies the host to Nagios so it won't matter if the address is NATted. Note that for the active check in Nagios you will need to use check_dummy or similar so that if the freshness check fails then Nagios will run this and alert you to the fact the freshness check has failed. I normally use something like .. check_dummy!3 UNKNOWN: Nagios didn't receive a check result lately from the server! You haven't said if the servers are Unix, Windows or what. If Windows, then it's easy to configure the NSClient++ agent to send checks using NSCA. If Unix or linux you will need to install send_nsca and the relevant plugins and run the checks from cron, maybe using the nsca_wrapper script which you'll find on Nagios Exchange. You will of course need to configure NSCA on your Nagios server to receive the incoming checks. hth, Jim -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Nagios-users mailing list Nagios-users@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
