Notifying on a service when host is unreachable?
Subhendu Ghosh
sghosh at sghosh.org
Tue Jun 3 18:32:12 CEST 2003
You may have to restructure the way the host and services are related.
Draw a topology map from "nagios" out.
eg.
nagios <---> Rt1 <----> Rt2 <----> {rt3, rt4, rt5}
l1 l2 {l3,l4,l5}
link l2 should be a service of Rt1
link l3, l4,l5 should be a service of Rt2
This way if a link goes down, the service notification comes from the
near-side node and the remote nodes are unreachable.
if your network is more of a mesh with dynamic routing, then each router
should have all the links defined as services because the near-side node
will have an alternate path back.
-sg
On Fri, 30 May 2003, Jeff Smith wrote:
> Right... when the intermediate link goes down I would like it to tell me
> that the intermediate link (the service bound to the host) went down not
> just that the host itself is unreachable. Which is how it happens now.
> Here's a mockup of my scenario:
>
> define host{
> use net_host
>
> host_name Foo_Router_Edge
> alias Foo Router Edge Type:2611
> address 10.1.1.1
> notification_options d,u,r
> }
>
> define service{
> use net_service
>
> host_name Foo_Router_Edge
> service_description Bar T-1 Id:123456 Cn:800-555-1212
> Ip:10.2.2.2 In:Serial0/0
> check_command check_ping_svc!10.2.2.2
> notification_options w,u,c,r
> }
>
>
> when the service goes down nagios goes and checks the host. Then it
> notifies that the host is unreachable but never notifies me that the
> service bound to the host is down. What I'm looking for is a way to
> tell Nagios to not only tell me the host is unreachable but also tell me
> that the service bound to it is also critical.
>
> The only Notification I get is:
>
> PROBLEM Foo Router Edge Type:2611 DOWN 05-30-2003 15:22:00
>
> When what I want to be notified on is the above plus:
>
> PROBLEM Bar T-1 Id:123456 Cn:800-555-1212 Ip:10.2.2.2 In:Serial0/0
> CRITICAL 05-30-2003 15:22:00
>
> Thats basically what I'm after.
>
> Thanks,
> Jeff
>
> Carroll, Jim P [Contractor] wrote:
>
> > Ah. It seems I misunderstood the original question.
> >
> > When an intermediate link goes down and you have no way of knowing
> > what the status of the remote host (or services on that host) are,
> > what would you propose should happen? Just because Nagios can't
> > reach the service in question, doesn't mean that the service isn't
> > providing useful functionality.
> >
> > Having said that, is it possible that defining service dependencies
> > might help you achieve what you're looking for?
> >
> > jc
> >
> >
> >
> >>-----Original Message-----
> >>From: Jeff Smith [mailto:doc at neonova.net]
> >>Sent: Friday, May 30, 2003 2:34 PM
> >>To: Carroll, Jim P [Contractor]
> >>Cc: nagios-users at lists.sourceforge.net
> >>Subject: Re: [Nagios-users] Notifying on a service when host is
> >>unreachable?
> >>
> >>
> >>The Service Contacts and the Host Contacts are the same contact group.
> >>
> >>Thanks,
> >>Jeff
> >>
> >>Carroll, Jim P [Contractor] wrote:
> >>
> >>
> >>>What about adding the service contacts to the host contact list?
> >>>
> >>>jc
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Jeff Smith [mailto:doc at neonova.net]
> >>>>Sent: Friday, May 30, 2003 10:29 AM
> >>>>To: nagios-users at lists.sourceforge.net
> >>>>Subject: [Nagios-users] Notifying on a service when host is
> >>>>unreachable?
> >>>>
> >>>>
> >>>>At my site we monitor a lot of network links. Currently these are
> >>>>defined as services on the host router they connect to. This
> >>>>causes a
> >>>>problem when the link drops and the host becomes unreachable.
> >>>>The way
> >>>>it is currently setup all the contact information for the
> >>>>circuit is in
> >>>>the service definition such that when it pages the oncall
> >>
> >>person will
> >>
> >>>>have all the information neccessary to contact the proper provider.
> >>>>However, since they are defined as services (which I believe
> >>>>they should
> >>>>be) when the host goes unreachable because the link went down
> >>>>the only
> >>>>notification sent is for the host. Is there a way to force
> >>>>the service
> >>>>notification to be sent as well? If not, the only other
> >>>>solution, that
> >>>>I can think of, is to define these as hosts instead of
> >>
> >>services which
> >>
> >>>>I'd rather not be forced to do. Any other ideas?
> >>>>
> >>>>Thanks,
> >>>>Jeff
> >>>>--
> >>>>Jeffrey Smith
> >>>>Operations
> >>>>Neonova Network Services
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>-------------------------------------------------------
> >>>>This SF.net email is sponsored by: eBay
> >>>>Get office equipment for less on eBay!
> >>>>http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> >>>>_______________________________________________
> >>>>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
> >>
> >>>
> >>>
> >>>-------------------------------------------------------
> >>>This SF.net email is sponsored by: eBay
> >>>Get office equipment for less on eBay!
> >>>http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> >>>_______________________________________________
> >>>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
> >>
> >>--
> >>Jeffrey Smith
> >>Operations
> >>Neonova Network Services
> >>doc at neonova.net
> >>919.460.3330
> >>
> >
> >
>
>
--
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
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
More information about the Users
mailing list