| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4971.1 | Anybody care to help me???? | STKHLM::BERGGREN | Nils Berggren EIS/Project dpmt, Sweden DTN 876-8287 | Mon May 10 1993 03:21 | 0 |
| 4971.2 | Try here | TNPUBS::JONG | The Nostalgia Tour | Mon May 10 1993 13:11 | 1 |
| Have you looked at Note 4662?
|
| 4971.3 | No help from #4662 | STKHLM::BERGGREN | Nils Berggren EIS/Project dpmt, Sweden DTN 876-8287 | Tue May 11 1993 03:13 | 16 |
| The basic questions are:
1. Can alarm rules be based on historical events?
if yes, then
2. How would the syntax be for the OCCURS-rule?
I assume YES on 1., and syntax according to .0 and
I can't cet it to work.....
Probably it's some simnple error in the expression,
but I can't figure it out.
So, can someone please help me out?
|
| 4971.4 | Working on it | TOOK::MINTZ | Erik Pavlik Mintz | Tue May 11 1993 09:35 | 7 |
| We are trying to find some time to reproduce this problem, but
the people with alarms expertise are overbooked at the moment.
(Among other things, we are in the middle of a facility move.)
There may be a problem with time handling by occurs rules.
Someone will post an answer as soon as we have time to investigate.
-- Erik
|
| 4971.5 | Will get back to you asap.. | TOOK::NAVKAL | | Tue May 18 1993 10:35 | 16 |
| Hi Nils,
I am very sorry that it took so long for me to get back to you. As Erik said
your question came right at the middle of the move for us. I did how ever
try to do exactly what you had attempted. There is nothing wrong with your
syntax. If the rule gets accepted the syntax is right. Since I have not had
the time to record the events and then apply the rule, I am unable to confirm
your suspicion.
Now that we have move to TAY2, I will record events and see what happens
to Alarms. In case you are interested I can mail you a note that Samuil
Shmuylovich and I have written on using historian and Alarms.
Again sorry for the delay. I will get back to you within a week.
Anil
|
| 4971.6 | Try this ... | TOOK::NAVKAL | | Thu Jun 03 1993 10:37 | 65 |
| Hi Nils,
Can you try the following?
"create domain history_domain rule history_events -
expression=(occurs(node4 saddam remote node saddam any events), -
in domain history_domain,
for start=(-00:10:00) duration 00:10:00)"
As you can see I have interchanged the qualifiers. I did not get a chance to
record decnet events and then make a rule on them. But I did record Alarms
rules them selves and then made a rule on historicaly recoded alarms rule
event. The expression looks as follows:
MCC> create domain anil rule past_time -
expression = (occurs(domain foo rule event_2 OSI Rule Fired), -
in domain foo, for (-00:02:00))
Domain WAKEME_NS:.anil Rule past_time
AT 1-JUN-1993 15:48:28
Rule created and enabled successfully.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The above rule work exactly as you would have expected it to
work. Here is the noticifation I got when I enabled the
notification.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
!!!!!!!!!!!!!! Alarm, 1-JUN-1993 15:50:35 !!!!!!!!!!!!!! [2]
Domain: WAKEME_NS:.ANIL Severity: Indeterminate
Notification Entity: Node4 WAKEME_NS:.dna_node.wakeme
Event Source: Domain WAKEME_NS:.ANIL Rule past_time
Event: OSI Rule Fired
Event Type = QualityofServiceAlarm
Event Time = 1-JUN-1993 15:50:32.77
Probable Cause = Unknown
Additional Info = { (
significance = True,
information = "The last event detected: Domain WAKEME_NS:.foo Rule event_2 OSI Rule Fired
1-JUN-1993 15:50:32.75" ),
(
significance = True,
information = "Event: OSI Rule Fired Event Type = QualityofServiceAlarm Event Time =
1-JUN-1993 15:50:32.51 Probable Cause = Unknown Additional Info = { (
significance = True, information = ""Rule fired: Node4
WAKEME_NS:.dna_node.wakeme Maximum Address = 1023 1-JUN-1993 15:50:28.65"" ),
( significance = True, information = ""(node4 wakeme max add > 0, at every
00:01)"" ) } Managed Object = Node4 WAKEME_NS:.dna_node.wakeme Perceived
Severity = Indeterminate" ),
(
significance = True,
information = "(occurs(domain foo rule event_2 OSI Rule Fired), in domain foo, for
(-00:02:00))" ) }
Managed Object = Domain WAKEME_NS:.foo Rule event_2
Perceived Severity = Indeterminate
-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-
Let me know if interchanging the qualifiers does not give you
the desired effect. And if it does work, don't ask me to explain
why it works the way it works :-)
Anil
|
| 4971.7 | no luck! | STKHLM::BERGGREN | Nils Berggren EIS/Project dpmt, Sweden DTN 876-8287 | Thu Jun 03 1993 17:33 | 170 |
| Hi Anil,
I tried your way with no luck. Look at the log. My comments are on
the right side and marked '<<<<'
It looks like the 'scope of interest' does not work properly; I'm
asking for events for the last 10 minutes, but I get older events as well...
==================== DECmcc log ====================
create domain history_domain rule history_events -
expression=(occurs(node4 saddam remote node saddam any events), -
in domain history_domain, for start=(-00:10:00) duration 00:10:00)
!
!
!Domain ANTIK_NS:.history_domain Rule history_events
!AT 3-JUN-1993 21:58:05
!
!Rule created and enabled successfully.
!
getevent node4 saddam remote node saddam any events, -
in domain history_domain, -
for start=(-00:10:00) duration 00:10:00
!
!
!Node4 saddam Remote Node saddam <<<< current time is now: 21:58:50.
!AT 3-JUN-1993 21:46:56 Any Event <<<< How come I get this event which is
! <<<< older than 10 minutes when scope
!Successfully received events: <<<< of interset is 10 minutes????
!Event: Counters Zeroed
! Remote Node counters
! Seconds Since Last Zeroed = 387 Seconds
! User Bytes Received = 0 Bytes
! User Bytes Sent = 0 Bytes
! Total Messages Received = 0 Messages
! Total Messages Sent = 0 Messages
! Connects Received = 0 Connects
! Connects Sent = 0 Connects
! Response Timeouts = 0 Timeouts
! Received Connect Resource Errors = 0
!
!Node4 saddam Remote Node saddam <<<<
!AT 3-JUN-1993 21:52:45 Any Event <<<< this event is expected, since
! <<<< it's younger than 10 minutes
!Successfully received events: <<<<
!Event: Counters Zeroed <<<<
! Remote Node counters
! Seconds Since Last Zeroed = 348 Seconds
! User Bytes Received = 0 Bytes
! User Bytes Sent = 0 Bytes
! Total Messages Received = 0 Messages
! Total Messages Sent = 0 Messages
! Connects Received = 0 Connects
! Connects Sent = 0 Connects
! Response Timeouts = 0 Timeouts
! Received Connect Resource Errors = 0
!
show domain history_domain rule history_events state
!
!
!Domain ANTIK_NS:.history_domain Rule history_events <<<<
!AT 3-JUN-1993 21:59:34 Status <<<< why hasn't it
! <<<< fired
! State = Enabled <<<<
! <<<<
disable domain history_domain rule history_events <<<< try disable/enable
! <<<< the rule again
! <<<<
!Domain ANTIK_NS:.history_domain Rule history_events
!AT 3-JUN-1993 21:59:50
!
!Normal operation will be terminated.
!
enable domain history_domain rule history_events
!
!
!Domain ANTIK_NS:.history_domain Rule history_events
!AT 3-JUN-1993 22:00:00
! <<<< here the rule
!Normal operation has begun. <<<< should fire....
! <<<<
! <<<< check again that
! <<<< we have events
! <<<< in the past 10 min.
getevent node4 saddam remote node saddam any events, -
in domain history_domain, -
for start=(-00:10:00) duration 00:10:00
!
!
!Node4 saddam Remote Node saddam
!AT 3-JUN-1993 21:46:56 Any Event <<<< again, why do we
! <<<< get this event??
!Successfully received events:
!Event: Counters Zeroed
! Remote Node counters
! Seconds Since Last Zeroed = 387 Seconds
! User Bytes Received = 0 Bytes
! User Bytes Sent = 0 Bytes
! Total Messages Received = 0 Messages
! Total Messages Sent = 0 Messages
! Connects Received = 0 Connects
! Connects Sent = 0 Connects
! Response Timeouts = 0 Timeouts
! Received Connect Resource Errors = 0
!
!Node4 saddam Remote Node saddam <<<<
!AT 3-JUN-1993 21:52:45 Any Event <<<< expected event
! <<<<
!Successfully received events:
!Event: Counters Zeroed
! Remote Node counters
! Seconds Since Last Zeroed = 348 Seconds
! User Bytes Received = 0 Bytes
! User Bytes Sent = 0 Bytes
! Total Messages Received = 0 Messages
! Total Messages Sent = 0 Messages
! Connects Received = 0 Connects
! Connects Sent = 0 Connects
! Response Timeouts = 0 Timeouts
! Received Connect Resource Errors = 0
!
! <<<<
! <<<< here I do a
! <<<< ZERO EXECUTOR
! <<<< on SADDAM and then
! <<<< the rule fires...
!!!!!!!!!!!!!!! Alarm, 3-JUN-1993 22:01:05 !!!!!!!!!!!!!! [1]
!Domain: ANTIK_NS:.history_domain Severity: Indeterminate
!Notification Entity: Node4 ANTIK_NS:.saddam Remote Node SADDAM
!Event Source: Domain ANTIK_NS:.history_domain Rule history_events
!Event: OSI Rule Fired
!
! Event Type = QualityofServiceAlarm
! Event Time = 3-JUN-1993 22:01:04.53
! Probable Cause = Unknown
! Additional Info = { (
! significance = True,
! information = "The last event detected: Node4
! ANTIK_NS:.saddam Remote Node
! SADDAM Counters Zeroed
! 3-JUN-1993 22:01:03.57" ),
! (
! significance = True,
! information = "Event: Counters Zeroed Remote
! Node counters Seconds Since
! Last Zeroed = 498 Seconds User
! Bytes Received = 0 Bytes User
! Bytes Sent = 0 Bytes Total
! Messages Received = 0 Messages
! Total Messages Sent = 0 Messages
! Connects Received = 0 Connects
! Connects Sent = 0 Connects
! Response Timeouts = 0 Timeouts
! Received Connect Resource Errors
! = 0" ),
! (
! significance = True,
! information = "(occurs(node4 saddam remote node
! saddam any events), in domain
! history_domain, for start=(-00:10:00)
! duration 00:10:00)" ) }
! Managed Object = Node4 ANTIK_NS:.saddam Remote Node
! SADDAM
! Perceived Severity = Indeterminate
!
!
use log off
!
!
|