| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
T1.2.7 VMS V5.5 VAXstation 3100/38 16MB memory.
I've defined a few notification events as follows:
Notify Domain DWO Entity List = (NODE4 * CIRCUIT *),
Events = (COUNTERS ZEROED,AUTOMATIC COUNTERS) ! Severity = major
Notify Domain DWO Entity List = (NODE4 *),
Events = (AUTOMATIC COUNTERS, COUNTERS, COUNTERS ZEROED)
! Severity = warning
Notify Domain DWO Entity List = (NODE4 * LINE *),
Events = (AUTOMATIC COUNTERS, COUNTERS ZEROED) ! Severity = minor
It appears that when the child entities fire, two notification events are
reported....that of the child and that of the parent. I can understand
given the way they are setup, why this would occur, but it is a bit misleading
as to why the parent reports the event for the child when there is a seperate
event defined for the parent alone.
Type: ^ Event ID: 1223 Request ID: 2
Domain: Domain LOCAL_NS:dwo
Entity: Node4 LOCAL_NS:seldon Circuit ISA-0
Event Source: Node4 LOCAL_NS:seldon Circuit ISA-0
Severity: warning
Timestamp: 7-MAY-1992 08:31:07.2
Text: Counters Zeroed
Details:
Type: ^ Event ID: 1224 Request ID: 1
Domain: Domain LOCAL_NS:dwo
Entity: Node4 LOCAL_NS:seldon Circuit ISA-0
Event Source: Node4 LOCAL_NS:seldon Circuit ISA-0
Severity: major
Timestamp: 7-MAY-1992 08:31:07.4
Text: Counters Zeroed
Details:
Is this the way it is supposed to happen or is there a way in which the parent
could be prevented from reporting child events. I would image there would
be instances where you would want both parent and child notification events.
Just curious.
Al
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2955.1 | notify requests look at children entities | DADA::DITMARS | Pete | Thu May 07 1992 18:43 | 30 |
The answer to this question is the same reason why the behavior of the alarms occurs format rules is inconsistent with the behavior of a notify request. When you supply an "entity list" argument to a notify request, it listens for events from the specified entities and all of their children who support the events specified (or defaulted) in the "events" argument. It's similar (sort of) to the "expand" argument which controls whether a notify request applies only the specified domain or that domain and all of its dynamic subdomain. There is no way to tell the notify request not to go listen to children entities (i.e. no equivalent to "expand = false"). The eft update documentation probably isn't very clear on this. In the case of the Node4 entity, several levels of the children support the "counters zeroed" event, so request 2, which is listening to "node4 *" is also going to pick up "counters zeroed" for "node4 * circuit *" and "node4 * line *". Given this explanation, I would expect you could acheive what you want by doing the following: Notify Domain DWO Entity List = (NODE4 *), Events = (AUTOMATIC COUNTERS, COUNTERS, COUNTERS ZEROED) And use targetting to set up the appropriate severities for each event, e.g. assign target domain dwo event source = node4 *, - event name = "AUTOMATIC COUNTERS", - target severity = warning | |||||
| 2955.2 | FOUR62::LICAUSE | Al Licause (338-5661) | Fri May 08 1992 09:30 | 4 | |
thanks very much....I haven't really understood the target concept, but I'll play with it a bit educate myself. Al | |||||
| 2955.3 | correction: notification only walks down the entity tree for GLOBAL entities | DADA::DITMARS | Pete | Fri May 08 1992 11:40 | 12 |
>It's similar (sort of) to the "expand" argument which controls whether a >notify request applies only the specified domain or that domain and all of >its dynamic subdomain. There is no way to tell the notify request not >to go listen to children entities (i.e. no equivalent to "expand = false"). Not quite correct: it will only look down the entity hierarchy when a GLOBAL entity is specified. Also, if you specify an event list and the event names are unique to the global entity level, then we won't go listening to child entities. So, you can usually restrict the walk of the entity tree if you want to by either specifying child entity classes explicitly or by specifying event names that only apply to the levels you're interested in. | |||||