On Sat, 13 Mar 2010, Digital Edge wrote: > > > > From: perld...@webwizarddesign.com > > Date: Fri, 12 Mar 2010 13:15:46 -0500 > > To: nagios-users@lists.sourceforge.net > > Subject: Re: [Nagios-users] Two IP for the Same server > > > > On Fri, Mar 12, 2010 at 11:52 AM, Digital Edge <reachta...@hotmail.com> > > wrote: > > > Dear List, > > > > > > I have a server , which is having 2 NIC with IP assign. I wanted to add in > > > nagios those two IP with same hostname & relevant service checks. > > > > > > Will it be possible. > > > > Not with a single host definition; however this can be modeled with 3 > > host definitions: > > * One virtual parent host object that has as a host check ping checks > > for both IPs > > * One virtual host object that represents NIC1 on the host > > * One virtual host object that represents NIC2 on the host > > > > Parent ------> A - NIC 1 > > | > > |-----------> B - NIC 2 > > > > The two hosts representing the NICs would have the parent host as > > their parent so that if the ping checks fail for the two hosts you > > only get notified that the parent host object is down. > > > > > What I mean to say that , > > define host{ > use generic-servers > host_name Example1 > alias Example1 - Used for Cookie > address 192.168.1.100 > address1 192.168.1.101 > } > > Is anyway it possible to add multiple address field in the host definition, > if the same server having more than one IP address.
To quote the original reply: > > Not with a single host definition ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ 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