| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2385.1 | use a rule on a rule. | TOOK::CALLANDER | MCC = My Constant Companion | Thu Feb 20 1992 20:50 | 12 |
| ah but you do have the rule events to trap on.
rule1 monitors for the attribute of the ethernet device,
monitoring it for a condition you always expect it to
pass as long as it is accessible and running.
rule2 monitors (using the occurs function) rule1 for
the rule exception event to occur 3 times.
This should do just what you are looking for.
|
| 2385.2 | retarget the rule output entity as well | TOOK::CALLANDER | MCC = My Constant Companion | Thu Feb 20 1992 20:52 | 8 |
| oops,
you can tell it is getting late, you wil want to set up
a target entity for the rule so that when rule 2 fires
the righ icon turns a color on the map.
assign target domain foo eve source=domain foo rule rule2, -
event name="any notification event", target entity= "station foo"
|
| 2385.3 | Syntax for rule2 please | WILARD::ATTERBERRY | | Fri Feb 21 1992 11:11 | 63 |
| Hi,
Sorry, I'm obviously missing something here. The target syntax
looks good, its the OCCURS_N_TIMES that I can't get to work.
I've tried the following syntax. Maybe you can tell me what I'm
doing wrong. This is what I've tried for rule2
MCC> @ev
%MCC-S-VERIFYENTER, entering command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;13
CREATE DOMAIN pw.eh.domain.adr RULE xt_detect_xterm4 -
OCCURS_RULE_FORMAT_4 = ( -
ENTITY = DOMAIN pw.eh.domain.adr RULE
xt_unreachable_xterm4 -
EVENT NAME = OSI Rule Exception -
COUNT = 3 -
DELTA TIME = 00:20:00), -
SEVERITY = CRITICAL, -
AUTO ENABLE = YES
%MCC-I-INVENTITY, invalid entity specified; reenter with correct entity
%MCC-S-VERIFYEXIT, exiting command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;13
MCC> @xt_alarm_xterm4
%MCC-S-VERIFYENTER, entering command procedure
VCSMCC$DISK:[LANMON.MCC]XT_ALARM_
XTERM4.COM;17
!=======================================================================
! XT_ALARM_XTERM4.COM
!=======================================================================
!
! =: X-Terminal has become ALARM :=
!
! Domain: PW.EH.DOMAIN.ADR
! Entity Class MCC 0 ALARMS RULE
! Instance PW.EH.WS.XTERM4
!
!DISABLE MCC 0 ALARMS RULE XT_ALARM_XTERM4, IN DOMAIN PW.EH.DOMAIN.ADR
!
!DELETE MCC 0 ALARMS RULE XT_ALARM_XTERM4, IN DOMAIN PW.EH.DOMAIN.ADR
!
CREATE MCC 0 ALARMS RULE XT_ALARM_XTERM4 -
EXPRESSION = (OCCURS_N_TIMES (MCC 0 ALARMS RULE
XT_UNREACHABLE_XTERM4,-
OSI RULE EXCEPTION,-
3,-
00:20:00)),-
CATEGORY = "X-Terminal problem" ,-
DESCRIPTION = "PWA_MCC_FILES:XT_ALARM.TEXT" ,-
QUEUE = "ALARMS$BATCH" ,-
PERCEIVED SEVERITY = CRITICAL ,-
IN DOMAIN = PW.EH.DOMAIN.ADR
MCC 0 ALARMS RULE XT_ALARM_XTERM4
AT 21-FEB-1992 11:10:18
Valid entity specification not found in alarm expression.
So what an I missing ?
Thanks.
Joe
|
| 2385.4 | I think you are missing commas | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Fri Feb 21 1992 17:05 | 25 |
| RE: .3
> CREATE DOMAIN pw.eh.domain.adr RULE xt_detect_xterm4 -
> OCCURS_RULE_FORMAT_4 = ( -
> ENTITY = DOMAIN pw.eh.domain.adr RULE xt_unreachable_xterm4 -
> EVENT NAME = OSI Rule Exception -
> COUNT = 3 -
> DELTA TIME = 00:20:00), -
> SEVERITY = CRITICAL, -
> AUTO ENABLE = YES
I think you need commas after: entity, event name, and count
Try this:
CREATE DOMAIN pw.eh.domain.adr RULE xt_detect_xterm4 -
OCCURS_RULE_FORMAT_4 = ( -
ENTITY = DOMAIN pw.eh.domain.adr RULE xt_unreachable_xterm4, -
EVENT NAME = OSI Rule Exception, -
COUNT = 3, -
DELTA TIME = 00:20:00), -
SEVERITY = CRITICAL, -
AUTO ENABLE = YES
/keith
|
| 2385.5 | No luck | MCDONL::ATTERBERRY | | Mon Feb 24 1992 10:59 | 42 |
| Hi Keith,
I tried what you said with no luck. Here are the results.
Any other suggestions ?
MCC> @ev
%MCC-S-VERIFYENTER, entering command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;26
CREATE DOMAIN pw.eh.domain.adr RULE xt_detect_xterm4 -
OCCURS_RULE_FORMAT_4 = ( -
ENTITY = DOMAIN pw.eh.domain.adr RULE
xt_unreachable_xterm4, -
EVENT NAME = "OSI Rule Exception", -
COUNT = 3, -
DELTA TIME = 00:20:00), -
SEVERITY = CRITICAL, -
AUTO ENABLE = YES
%MCC-E-RECORD_FIELD_NA, no such Record field name
%MCC-S-VERIFYEXIT, exiting command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;26
If I remove the double quotes I get a Latin1String error
MCC> @ev
%MCC-S-VERIFYENTER, entering command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;27
CREATE DOMAIN pw.eh.domain.adr RULE xt_detect_xterm4 -
OCCURS_RULE_FORMAT_4 = ( -
ENTITY = DOMAIN pw.eh.domain.adr RULE
xt_unreachable_xterm4, -
EVENT NAME = OSI Rule Exception, -
COUNT = 3, -
DELTA TIME = 00:20:00), -
SEVERITY = CRITICAL, -
AUTO ENABLE = YES
%MCC-E-LATIN1STRING_ER, error in Latin1String value
%MCC-S-VERIFYEXIT, exiting command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;27
Thanks.
Joe
|
| 2385.6 | Another suggestion | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Mon Feb 24 1992 14:05 | 17 |
| This time try a different syntax:
create domain pw.eh.domain.adr RULE xt_detect_xterm4 -
expr = (OCCURS(DOMAIN pw.eh.domain.adr RULE xt_unreachable_xterm4 -
osi rule exception, 3, 00:20:00)), SEVERITY = CRITICAL, AUTO ENABLE = YES
This syntax (which I personally prefer) uses the OCCURS function in more
of a programming style:
OCCURS( <entity>, <count>, <delta-time> )
Give it a try and let me know. I just tried it and it worked.
As far as the other syntax which you were using ... we'll have to look
into some more.
/keith
|
| 2385.7 | Still No Luck ! | MCDONL::ATTERBERRY | | Mon Feb 24 1992 14:29 | 28 |
| Hi,
Tried it, doesn't work for me. Are you running T1.2.4 ?? If you are
and it works, then X1.2.15 (which I'm running) broke it.
Here's what I get
MCC> @EV
%MCC-S-VERIFYENTER, entering command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;38
CREATE DOMAIN pw.eh.domain.adr RULE xt_detect_xterm4 -
EXPR=(OCCURS(DOMAIN pw.eh.domain.adr RULE
xt_unreachable_xterm4 -
osi rule exception, 3, 00:20:00)), -
SEVERITY = CRITICAL, -
AUTO ENABLE = YES
Domain PW_NS:.pw.eh.domain.adr Rule xt_detect_xterm4
AT 24-FEB-1992 14:26:25
Count and Delta-Time is not allowed with wildcard in alarm expression.
%MCC-S-VERIFYEXIT, exiting command procedure
VCSMCC$DISK:[LANMON.MCC]EV.COM;38
Should I fall back to T1.2.4 ?
Joe
|
| 2385.8 | Oh .. now its making a bit more sense | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Mon Feb 24 1992 16:00 | 20 |
| RE: .7
> Count and Delta-Time is not allowed with wildcard in alarm expression.
There was a bug in the parsing of the OCCURS funtion with the additional
count and delta-time arguments. It was fixed recently, but it probably
wasn't in x1.2.15 ... 8(
I am running x1.2.16 -- thus why it worked for me.
I suspect there will be another kit made available soon. The fix
will be in there.
As to why the 'other' command format you were using didn't work (the record
problem) ... I don't know and will have to talk with someone on the
console team to find out.
/keith
|
| 2385.9 | I guess I will have to wait, but thanks | MCDONL::ATTERBERRY | | Mon Feb 24 1992 17:21 | 26 |
| hi,
many, many thanks for your help. I will wait patiently for X1.2.16 to
be released. Oh, by the way I did get the other syntax to create the
same error. At least now the error is consistent for both kinds of
syntax.
Joe
!
CREATE MCC 0 ALARMS RULE XT_ALARM_XTERM4 -
EXPRESSION = (OCCURS(DOMAIN pw.eh.domain.adr -
RULE XT_UNREACHABLE_XTERM4 -
OSI Rule Exception,3,00:20:00)),-
CATEGORY = "X-Terminal problem" ,-
DESCRIPTION = "PWA_MCC_FILES:XT_ALARM.TEXT" ,-
QUEUE = "ALARMS$BATCH" ,-
PERCEIVED SEVERITY = CRITICAL ,-
IN DOMAIN = PW.EH.DOMAIN.ADR
MCC 0 ALARMS RULE XT_ALARM_XTERM4
AT 24-FEB-1992 17:11:30
Count and Delta-Time is not allowed with wildcard in alarm expression.
|