Scheduled downtime for mass hosts?

[Daniel Wittenberg]

Another reason something like Multisite is handy :)

Dan

-----Original Message-----
From: C. Bensend [mailto:benny at bennyvision.com] 
Sent: Thursday, January 12, 2012 8:11 AM
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Scheduled downtime for mass hosts?


> Tonight I will be forming maintenance on over 50 of my servers and will be
> taking firewall and routing links out.
>
> I have 86 hosts that this will affect.
>
> Im going to put them into scheduled downtime in Nagios.
>
> I have my hosts divided into hostgroups.
>
> Is there a quick way to schedule all 86 hosts into Nagios downtime rather
> than having to click on each host in the web GUI and doing them
> individually?

This is precisely why I have a hostgroup that contains *all* my hosts.
I just issue a single downtime command for the host*group*, and voila.

Benny


-- 
"Cats land on their feet. Toast lands peanut butter side down. A cat
with toast strapped to its back will hover above the ground in a state
of quantum indecision."           -- Unknown


------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
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

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
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