> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of ????? > Sent: Wednesday, January 03, 2007 10:42 PM > To: Nagios Users mailinglist > Subject: [Nagios-users] Notification for change in critical state > > Hi, > > I am running nagios 2.5, monitoring a network that has many > devices with multiple IPs (ie. routers). > Currently I have each IP registered as a separate host, which > works well, but is a pain to manage. > What I want to do is set up a multi-ping service that will > ping all the IPs and generate a critical state if one of the > IPs does not respond. > The problem is that, for example, one IP goes down and a > notification is sent out, there doesn't seem to be a way to > force a notification to be sent if another IP goes down, as > the service is already in a hard critical state. > I thought about generating an external command from the check > script, but the list of external commands > (http://nagios.org/developerinfo/externalcommands/commandlist.php) > doesn't list one that I could see helping...(like maybe one > to force the state type back to soft or something). Setting > the notification number to 0 didn't do the trick (see > SET_SVC_NOTIFICATION_NUMBER). > > Is such a scenario possible? or am I barking up the wrong tree?
What I'd do, which may or may not work for you, is to set up a service on a single host that pings each IP. That way one interface going down doesn't effect the notification status of the others. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
