Your delay is the problem. nvcorrd is designed for real-world processin and
he cannot be checking on your ruleset every second. Remember that all
events go thru him before they are displayed. So he does not check his
reset/pass timers but every 15 seconds. So you cannot have an interval
finer than that.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Ken Freeman, IT Dept, x4318 FREEMAK - WEBS" <GBWBSJHS@IBMMAIL.COM> on
03/18/99 05:31:35 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: Reset on Match
---------------------------------------------------------------------------
----
Is anyone able to assist me in creating a ruleset using the 'Reset on
Match'
node as I am completely stumped by the results that I am getting.
Backgroud
?????????
We have configured some of our Madge CAUs to alert when selected thresholds
are exceeded - resulting in RMON Rising and Falling alerts to be sent.
Our Network Services people have decided that they don't want to be
notified
if the situation occurs for less than a predetermined period of time
(probably
3 seconds).
Ruleset definition
??????????????????
1) Default Action - Block
2) Trap Settings - RMON Rising Alarm
3) Trap Settings - RMON Falling Alarm
4) Reset on Match - Input 1 = Rising Alarm
Input 2 = Falling Alarm
Comparisons = Origin & MIB variable ($2)
Delay Time = 1 second for testing
5) Forward - For any alerts that are passed by the Reset on
Match
Problems
????????
1) Whilst running this ruleset in a Dynamic Workspace I noted an
inconsistent
set of results:
Rising Trap Falling Trap Delay Event Action
Timestamp Timestamp (Seconds)
????????? ????????? ????????? ????????????
09:23:22 09:23:24 2 Forwarded Correct
09:26:44 09:26:45 1 Blocked Correct
09:27:00 09:27:01 1 Blocked Correct
09:39:08 09:39:10 2 Blocked Incorrect
09:39:21 09:39:22 1 Blocked Correct
09:40:19 09:40:21 2 Blocked Incorrect
09:41:16 09:41:18 2 Blocked Incorrect
09:45:43 09:45:44 1 Forwarded Incorrect
09:49:43 09:49:44 1 Forwarded Incorrect
2) The Falling alarm is never passed for display even if the Rising alarm
was
forwarded.
Any pointers on what I am doing wrong would be greatly appreciated. I
apologise
for the length of the note but I thought it best to include as much
information
as possible.
Thanks
Ken Freeman
Principal Technical Specialist
Woolwich plc
|