I have just a simple maitenence window set on an individual windows
server so far, and it seems to work right for me... I set state to
maitenence and then end state to Production...
Maybe you are moving to "Original" rather than Production? I'm not sure,
may just be unclear in your original message.
That's all I did, I have no idea why it doesn't switch back for you.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
crosse wrote:
Here's the scenario:
I'm trying to set up Maintenance Windows in Zenoss 2.1. (For the record, what
I'm about to describe also happened in 2.0.x so I don't think it was introduced
in 2.1). Here's what some of our blackout times look like in our current
monitoring product:
1am-3am daily for Windows ServerGroupA;
4:30am-6:30am daily for Windows ServerGroupA again;
5am-6am daily for backup servers;
1:50am-3am Sundays for Domain Controller rolling reboot;
2:45am-4am Sundays for Windows Server reboots;
etc, etc...
This is just a small subset, but as you can see there are a many windows that overlap each other, some involving the
same servers. This works beautifully in our current product, mainly because we just tell it to not page during that
time--it really doesn't have the concept of a "maintenance window", you just write a "don't page"
rule. When I try to duplicate this functionality with Zenoss, I set up a Maintenance Window for each of the times
listed above and set the production state to "Maintenance" and the ending state to "Original". In
my mind, this should work.
Unfortunately, the behavior I see is somewhat different. Usually I come in
Monday morning and wonder why I have no events showing on the dashboard, only
to discover that all of my Windows servers are still in Maintenance mode!
After this happened for a few weeks I thought that maybe it was the overlapping
windows that were throwing it off (although I don't see how or why) so I
disabled all the windows except the Sunday Reboot, yet I'm still seeing this
behavior. Also, it used to be just my Windows servers that were affected. The
Linux boxen that were affected by the window would return to Production before,
but now even some of the Linux servers seem to be affected. I just don't get
it.
All that to say: is anyone else seeing this behavior? Is anyone using Maintenance Windows successfully? And if so, how complex are your windows, etc?
And to the Zenoss guys: should I be able to use overlapping Maintenance
Windows like this? Any suggestions for testing purposes? This is a test
environment and no one is relying on it for alerts (yet), so if there's
anything you'd like me to test I'm all for it.
Thank you!
seth wright ([EMAIL PROTECTED])
windows engineer
540.568.2912 (office)
james madison university
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=12547#12547
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
