Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+Ruleset\s+\+\s+up\s+event\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+Ruleset\s+\+\s+up\s+event\.\s*$/: 7 ]

Total 7 documents matching your query.

1. [nv-l] Ruleset + up event. (score: 1): Author: Tom Hallberg <gimli AT hhcrew DOT tk>; Date: Wed, 22 Sep 2004 09:41:28 +0200 (CEST); Hi I got some ruleset design problem. For the moment I got first a "Trap Settings" (for Router down events), then a "Inline Action" to check that its one of the routers I want to have status check on; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00132.html (11,649 bytes)
2. Re: [nv-l] Ruleset + up event. (score: 1): Author: James Shanks <jshanks AT us.ibm DOT com>; Date: Wed, 22 Sep 2004 09:19:30 -0400; What you see is what you get, Tom. If you want to pass a Router Up event, then you have to do it explicitly. The logic you are saying you want here is much more complicated than just a simple reset-o; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00137.html (15,092 bytes)
3. Re: [nv-l] Ruleset + up event. (score: 1): Author: Tom Hallberg <gimli AT hhcrew DOT tk>; Date: Wed, 22 Sep 2004 15:36:40 +0200 (CEST); Thank you, then I probably will go for the script file or ask my TEC friend to clear it there. //Tom; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00139.html (14,959 bytes)
4. RE: [nv-l] Ruleset + up event. (score: 1): Author: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>; Date: Wed, 22 Sep 2004 08:47:08 -0500; Here is a ruleset that does just what you need. It’s got some extra stuff in it because it processes a bunch of different groups node downs so you’ll want to strip out the extra query sma; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00140.html (23,157 bytes)
5. RE: [nv-l] Ruleset + up event. (score: 1): Author: James Shanks <jshanks AT us.ibm DOT com>; Date: Wed, 22 Sep 2004 08:32:10 -0600; Mighty complicated set of Reset-on-match and Pass-on-Match ruleset nodes back to back. Not sure I follow it all. But the key seems to be those scripts at the end so far as I can see. Whatever happens; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00142.html (21,075 bytes)
6. RE: [nv-l] Ruleset + up event. (score: 1): Author: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>; Date: Wed, 22 Sep 2004 09:51:13 -0500; Like I said, I don’t totally understand it but the ruleset author who reads this forum can give you the details. I totally agree with your concerns about the trap being “lost” if a; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00144.html (32,416 bytes)
7. RE: [nv-l] Ruleset + up event. (score: 1): Author: "Van Order, Drew $US - Hermitage$" <dvanorder AT deloitte DOT com>; Date: Wed, 22 Sep 2004 13:52:06 -0500; "Our approach is based on the fact that our different groups all have different requirements (re: insanity) so we had to accommodate all sorts of interesting down-wind considerations" That is about t; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-09/msg00156.html (38,035 bytes)

Current List: 1 - 7
Page: [1]