Re: [Nagios-users] Reporting for redundant hosts
On 05/20/2010 06:28 PM, Stephan Tesch wrote: Am 20.05.2010 11:32, schrieb Assaf Flatto: Hello Assaf, One approach is to monitor a VIP for the service (i.e. the clustered ip of the external facing IP address of the routers) for finding if the service is up , and the individual devices by their direct IP for each device activity . This will give you both the business view ( if the VIP is down then the business is impacted) , and the operational view ( one device impacted ). This is for sure a good idea. On the other hand this would mean that we have to monitor another host and also plan for downtimes of this host, too. An approach where I just define the redundant hosts and get the report that I need would in my opinion be the better one. The data is all there, it just has to be evaluated. I really can't believe, that I'm the only one with this problem? You're not. Ninja has cluster-mode capabilities in its reporting tool. Check it out if you're interested. Adding such a feature to the cgi's would be more hassle than it's worth, and I sure as hell won't get the time for it from work since we already have it in our own reporting solution. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- ___ 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] Reporting for redundant hosts
Stephan Tesch wrote: Hello everyone, I'm facing a problem for a long time now, having done some research on this, but never been able to find a solution: We're monitoring a lot of redundant network hosts (routers, firewalls, etc.) where we have to report the uptime of the whole setup, not only the uptime of a single component. An example: We have routerA and routerB, that form a HA setup. If one router is taken down, for example to update its firmware, or simply crashes, the whole setup still should have a reported uptime of 100%. What I've already tried is to configure a cluster service. The problem with this approach is, that I can't distinguish in the reporting whether the host was down or unreachable, which is another crucial number to report, also the downtimes don't get reflected very well. I'm running Nagios 3.2.1 with NDOutils if that matters for the question. Is there any plugin or addon that provides this functionality? Many thanks, Stephan One approach is to monitor a VIP for the service (i.e. the clustered ip of the external facing IP address of the routers) for finding if the service is up , and the individual devices by their direct IP for each device activity . This will give you both the business view ( if the VIP is down then the business is impacted) , and the operational view ( one device impacted ). -- Never,Ever Cut A Deal With a Dragon I am doing a Charity Bike ride On the 27 of June for the Capital to Coast Charity. Please help by Donating http://www.justgiving.com/Lovefilm-capital-to-coast -- ___ 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] Reporting for redundant hosts
Am 20.05.2010 11:32, schrieb Assaf Flatto: Hello Assaf, One approach is to monitor a VIP for the service (i.e. the clustered ip of the external facing IP address of the routers) for finding if the service is up , and the individual devices by their direct IP for each device activity . This will give you both the business view ( if the VIP is down then the business is impacted) , and the operational view ( one device impacted ). This is for sure a good idea. On the other hand this would mean that we have to monitor another host and also plan for downtimes of this host, too. An approach where I just define the redundant hosts and get the report that I need would in my opinion be the better one. The data is all there, it just has to be evaluated. I really can't believe, that I'm the only one with this problem? Best regards, Stephan -- Stephan TeschPhone + 49 (0)7071-9457-608 science + computing ag FAX + 49 (0)7071-9457-511 Hagellocher Weg 73 D-72070 TuebingenEmail: s.te...@science-computing.de -- Vorstand/Board of Management: Dr. Bernd Finkbeiner, Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech Vorsitzender des Aufsichtsrats/ Chairman of the Supervisory Board: Michel Lepert Sitz/Registered Office: Tuebingen Registergericht/Registration Court: Stuttgart Registernummer/Commercial Register No.: HRB 382196 -- ___ 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] Reporting for redundant hosts
Stephan Tesch wrote: Am 20.05.2010 11:32, schrieb Assaf Flatto: Hello Assaf, One approach is to monitor a VIP for the service (i.e. the clustered ip of the external facing IP address of the routers) for finding if the service is up , and the individual devices by their direct IP for each device activity . This will give you both the business view ( if the VIP is down then the business is impacted) , and the operational view ( one device impacted ). This is for sure a good idea. On the other hand this would mean that we have to monitor another host and also plan for downtimes of this host, too. An approach where I just define the redundant hosts and get the report that I need would in my opinion be the better one. The data is all there, it just has to be evaluated. I really can't believe, that I'm the only one with this problem? I don't know about your case, but what I do here if there are multiple devices which support a single address is put all of them in Nagios as Assaf mentioned. I'll then set the real hosts as the parents of the virtual one, and if things are set up that way you *don't* need to worry about setting downtimes for the virtual address, because it will automatically be marked unreachable if all of the real addresses are down. In my case, though, I primarily want to know if the VIP is working, and am not quite as concerned with the individual hosts serving it (though those are important as well, just not as important as if the service they provide is available). Based on your statement that you'd have to monitor another host, it sounds like knowing the state of this service isn't really as important to you as knowing if the individual hosts that serve it are working. Frankly, that seems a bit backwards to me, but I don't really know your environment. -- ___ 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] Reporting for redundant hosts
On Thu, May 20, 2010 at 6:28 PM, Stephan Tesch s.te...@science-computing.de wrote: Am 20.05.2010 11:32, schrieb Assaf Flatto: Hello Assaf, One approach is to monitor a VIP for the service (i.e. the clustered ip of the external facing IP address of the routers) for finding if the service is up , and the individual devices by their direct IP for each device activity . This will give you both the business view ( if the VIP is down then the business is impacted) , and the operational view ( one device impacted ). This is for sure a good idea. On the other hand this would mean that we have to monitor another host and also plan for downtimes of this host, too. An approach where I just define the redundant hosts and get the report that I need would in my opinion be the better one. The data is all there, it just has to be evaluated. I really can't believe, that I'm the only one with this problem? I'm not sure if there is an easy way to do just this for vanilla Nagios, but op5:s Ninja project includes SLA reports with this exact functionality: http://www.op5.org/community/projects/ninja Best regards, Martin Melin -- ___ 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
