good luck
Jack
----- Original Message ----- From: "Michael D. Shook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 08, 2004 8:00 AM
Subject: RE: [SA-list] features for the far future ?
Check 1 is Switch A ping Check 2 is Switch B ping Check 3 is Server ping
I could set it up how you suggested IF I only 1 or two switch / server combos
We have a series of switches; any server will be connected to a near-random
set of 2 switches to minimize potential damage from a loss of a single
switch.
Plus, I always want all the switches checked, not some only when others are
down.
Michael D. Shook Technical Analyst [EMAIL PROTECTED] 863 668 4477 (work) 863 860 4070 (cell) 863 665 1261 (fax) www.saddlecrk.com
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Jack Lyons
Sent: Friday, October 08, 2004 5:44 AM
To: [EMAIL PROTECTED]
Subject: Re: [SA-list] features for the far future ?
2) can't you do it like: check 1 is nic 1 up check 2 is dependant on check 1 being down check 3 is dependant on check 2 being down and will alert if it is up.
cases: check 1 check 2 check 3 Action up not checked not checked none down up not checked none down down up alert
are you checking the port status? Not sure why you need to check two things first?
Jack
----- Original Message ----- From: "Michael D. Shook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 07, 2004 8:36 AM
Subject: RE: [SA-list] features for the far future ?
1) Actually, I already have HTML features implemented for this from a lookup POV, I was hoping for something in the GUI to make updates and changes easier. What happened was we got an alert sent out to the wrong team, but then I spent quite a few minutes trying to find the offending check entry so I could fix it.
2) Sounds like you understand what is needed on this one. Check C would be
dependant on Check A AND Check B being UP.
Michael D. Shook Technical Analyst [EMAIL PROTECTED] 863 668 4477 (work) 863 860 4070 (cell) 863 665 1261 (fax) www.saddlecrk.com
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Thursday, October 07, 2004 7:21 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] features for the far future ?
1) From a configuration point this looks difficult....what I do see as a possibility is to have within the HTML output something for this. We could add an <sa... Parameter that gives the number of cycles that an entry is within the current status, with the possibility to sort by that parameter too, that way you could get the "new"-downs before the "old"-downs, what do you think?
2) Something that we're looking at (no not for v5.0 :-)) is depending on a
group. This comes close to what you need I think. From what I understand
the entries can be only be checked if NIC_1 OR(AND) NIC_2 are OK, correct?
Dirk.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael D. Shook Sent: Thursday, October 07, 2004 2:14 PM To: [EMAIL PROTECTED] Subject: [SA-list] features for the far future ?
I just ran across a couple of situations that didn't quite fit the current
SA.
1) Would it be possible for the GUI to offer a new color choice or icon or
something for those checks that are newly changed in status? Like if it's
gone from UP to DOWN or Down to unavailable? Maybe have a 3 or 5 cycle
limit
before it just displays the status as it does now? With a great wad of
similar checks it's kind of hard to find the server that just went UP.
2) We now have all of our servers using teamed NICs for network
redundancy.
Each NIC is patched to a different switch. This means that I really need
the
server check dependant on TWO other checks. Is this functionality possible
for the future?
Thanks!!!!!!!
Michael D. Shook Technical Analyst [EMAIL PROTECTED] 863 668 4477 (work) 863 860 4070 (cell) 863 665 1261 (fax) www.saddlecrk.com
-------------------------
[This E-mail scanned for viruses by Declude Virus]
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
-------------------------
[This E-mail scanned for viruses by Declude Virus]
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
-------------------------
[This E-mail scanned for viruses by Declude Virus]
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
-------------------------
[This E-mail scanned for viruses by Declude Virus]
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
-------------------------
[This E-mail scanned for viruses by Declude Virus]
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
-------------------------
[This E-mail scanned for viruses by Declude Virus]
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
