| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3358.1 | try NOTIFY without severity | CTHQ4::WOODCOCK | | Wed Jul 15 1992 09:42 | 27 |
| Hi Peter,
Is the NOTIFY request below is the severity really set to WARNING. I ask
because of the "!". In any case for the NOTIFY command, set NO SEVERITY. That
is, let it default to INDETERMINATE.
The TARGETTING commands will then override the indeterminate on the TARGET
node. FWIW, you will probably need two target commands (one for each event)
to set one to CRITICAL and the other to CLEAR.
This works for us in a similar fashion for circuit events except the target
doesn't change. Give it a spin it might do the trick.
best regards,
brad...
>notify domain xxx entity list=(node4 router circuit qna-0 adjacent node 30.144),
>events=(adjacency up, adjacency down) !severity=warning
>To then cause these events to trigger the node with the correct severity
>I then have a target assigned as follows...
>assign target domain xxx event source=(node4 * circuit * adjacent node *),
>event name ="adjacency down", managed object="node4 * circuit * adjacent node #1",
>target entity = "node4 #1", target severity = critical
|
| 3358.2 | Tried it... | PJWL::LAMB | Peter Lamb - GSG Santa Clara MAIL=MUTTON::LAMB | Wed Jul 15 1992 12:23 | 21 |
| Hi,
Thanks for getting back to me so quickly!!!
The ! for severity level is what the iconic_map assign target/show
target displays. Just for grins I will try creating the target at
the mcc_fcl level and see if it makes any difference but again it
looks like the mcc_fcl has it right anyway...
I origionally had the notify set to INDETERMINATE. and only changed
it to warning to see if that new level also got xfered to the target.
In both cases either indeterminate or warning etc. the target receives
the level set by the notification not by the target assignment.
Thanks for the suggestions!! I will play with it some more today...
If you have any more ideas please let me know!!!
Thanks!
Peter
|
| 3358.3 | Fixed it... | MUTTON::LAMB | Peter Lamb - GSG Santa Clara | Wed Jul 15 1992 15:27 | 19 |
| Brad,
Setting no severity did the trick!! It turns out that previously I had it set
to indeterminate but had the togle turned on such that it included a severity.
So I guess my next question is shouldn't targeting override the notification
severity level????
Additionally, I just noticed something else strange with notification...
I left the mcc_fcl mode running overnight with the notification
notify domain xxx event=(any config event)
and received the following errors sometime durring the night...
DECnet IV am internal error - unfortunatly I lost the origional messages
Peter
|
| 3358.4 | haven't seen error with this kit | CTHQ3::WOODCOCK | | Wed Jul 15 1992 15:47 | 20 |
| Peter,
>So I guess my next question is shouldn't targeting override the notification
>severity level????
That would make sense to me but maybe the engineers had their reasons for
doing it this way. Right now I'm more worried about things that don't work
with the SSB rather than things that don't look right.
>DECnet IV am internal error - unfortunatly I lost the origional messages
I haven't seen the above error to date with this kit but I'm getting ALARM
errors which may be caused by DECnet IV am when ALARMS is doing global
wildcard rules. I'm actually getting so many errors I have rules turned off
so I'm only about 80% production. I'm thinking of punting back to T1.2.7 if
I can't get it fixed :-(.
best regards,
brad
|
| 3358.5 | targetting severity override strategy | TOOK::CALLANDER | MCC = My Constant Companion | Tue Aug 11 1992 13:34 | 27 |
| well engineers always have reasons, the question is simply "are the
reasons any good?" Well we thought so but you decide (BTW we have
updated the notification manual for the EMS release so as to
better describe the targetting stuff).
This is how targetting is decided:
1) the entity returns the severity
2) the user does an assign target to override the severity set
by the entity
3) the user tells the notify command what severity to associate with
a notification, overriding any other value previously associated
with it.
In other words, we took a top down approach for the overrides. The
higher up in the food chain the more powerful your override. So,
if you say NOTIFY from the iconic map with an override severity of
warning, EVERY event that is returned for that NOTIFY will have
a severity of warning. If instead you tell notify to pass up
the severity (don't override with the PM switch) then you get the
retargetting from the assign target, and if no assignments exist
you get the entity supplied severity.
hope this helps
|