| It is probably too late for your class (sorry I missed your note
earlier -- I am still catching up).
What to check. Okay if the rules are firing, and they we created
using the domain rule interface, or with a create mcc 0 alarm rule
xxx, in domain yyy; then they should work.
The most common problem is people create the rules without the
in domain qualifier. check this by doing a show command.
1) they must be created with either the in domain qualifier,
or through the domain rule interface (create domain xxx rule yyy;
which is how the iconic map does it).
2) the domain must be open on the map with notification enabled
(opening the parent of a map hierarchy that is dynamic is
sufficient).
|
| Thanks for reply.
Since the course has finished and the system has been blown away I
can't recreate the problem or checkout your comments. The rules were
created using Iconic Map.
Further investigation revealed the following:-
the student in question had a 4-level domain hierarchy within Iconic
Map. If he went in at the top level and double clicked his way down to
the domain in question, alarm notification did not work. If he went in
at the top level and then selected "Open Domain" to go directly to the
domain, alarm notification DID work. Does this provide any further clue
as to the problem?
|
| Sounds like the domain is a static member of its parent domain. If
Domain A contains Domain B, and you're interested in Domain B alarms,
then you must do either one of the following:
1) Open Domain B as the top-level domain
2) Add Domain B as a dynamic member of its parents (all the way up
to the top-level domain).
Christine
|