******************************************************************************************
This message has been scanned and verified as virus free by Symantec
AntiVirus and Filtering
******************************************************************************************
What if you had situations where server was shut down gracefully that were
not normal operating conditions?
E.g.
1) UPS software that triggers graceful shutdown
2) Operator error - an admin that accidentally shut down a server (don't
scoff, I've seen this more times that I can count...)
I personally think having a client on a server automatically putting a SA
host check into Maintenance is a pretty bad idea. I admit we have problems
where I work with admins forgetting to put hosts into maintenance before
working on them but that comes down to providing easy ways for people to do
it and conditioning them that before they do anything they check if the
system they are working on is being monitored by SA and then put it into
maintenance and just as importantly, remember to set it back to active when
it's back up.
I tend to find that if you have a person that is a repeat offender on this
sort of thing the best remedy is to perform maintenance on a system when
*they* are on call and see how much they appreciate other people forgetting
when they get woken up at 2am by a pager/SMS alert. ;-)
I do a lot of my maintenance from home via VPN so the telnet interface of
SA is definitely the simplest and quickest way of putting a host into
maintenance.
Another thing that helps is to ensure that if you have multiple host checks
for a system that you create 1 check that all others are dependent on, eg.
a ping check. This means when you want to put that system into maintenance
you're only having to do it for 1 host check (all the dependent checks will
go into unavailable mode which won
t generate any alerts) which is a lot easier and therefore people are more
likely to find it less of a chore to do.
If all this still fails, threaten to beat discipline into the offending
admin ;-)
Cheers,
Anthony
"Dirk Bulinckx"
<[EMAIL PROTECTED] To: <[EMAIL PROTECTED]>
u> cc:
Sent by: Fax to:
salive-owner@wood Subject: RE: [SA-list] Maintenance
Mode thought
stone.nu
03/01/03 03:00
Please respond to
salive
"client" could act on shutdown and on start of the OS.
dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of gene Martinez
Sent: Thu Jan 02 4:54 PM
To: [EMAIL PROTECTED]
Subject: Re: [SA-list] Maintenance Mode thought
How would the client know if the server was DOWN or if YOU had shut
it down?
At 04:27 PM 1/2/03 +0200, you wrote:
>>>>
<?fontfamily><?param Arial><?smaller>I was just thinking if it
were at all possible for someone to come up with a "client"
that, if when a server is shutdown for maintenance, that this
"client" would put the relevant server in to maintenance mode
and then when the server comes back up the "client" changes the
mode back to active. So as to avoid the administrator's
forgetfulness to do so and getting unwanted alerts.
<?/smaller><?/fontfamily>
<?fontfamily><?param Arial><?smaller>Just a thought for the
programming brains to ponder over.
<?/smaller><?/fontfamily>
<?fontfamily><?param Arial><?smaller>Andr�
South Africa<?/smaller><?/fontfamily>
<<<<
Regards,
Gene [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.eclipse.net/~njkat To unsubscribe from a list, send a mail
message to [EMAIL PROTECTED] With the following in the body of
the message: unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
