| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1068.1 | just a guess | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Thu May 30 1991 13:41 | 6 |
| Christine wrote that code, and she is out off enjoying her vacation
right now. But, my guess is that the color change code probably searchs
the map content lists to find which domain the entity is in, I bet
it searchs until it finds a match, but only one map. I'll ask christine
when she gets back, hopefully I won't forget.
|
| 1068.2 | | TOOK::F_MESSINGER | | Thu May 30 1991 13:51 | 5 |
|
I'll just forward this note to her. She'll answer
when she returns.
Fred
|
| 1068.3 | more info please | TOOK::HAO | | Mon Jun 03 1991 12:57 | 12 |
| Hi there,
I'm back, and I need some more info. Just skimming the code quickly,
it doesn't look like it stops after finding the first match, but does
search the entire domain hierarchy.
Could you specify what your alarm rule was? And which domain it was
defined in?
Thanks,
Christine
|
| 1068.4 | Here is the info. | SNOC01::MISNETWORK | They call me LAT | Tue Jun 04 1991 21:45 | 32 |
|
Thanks for the help Christine.
Below is the actual alarm rule -
create mcc 0 alarms rule SNO-ZKO-DECnet-DOWN -
expression=(change_of(node4 SNOR04 circ zko-1
substate,none,synchronizing), -
at every 00:01:00),-
procedure=disk$userdisk:[tassone.mcc]sprnet_decnet_alarms_broadcast.com;,-
parameter="user=(tassone,engineer)",queue="MCC_ALARMS$BATCH",-
category="SNO-ZKO-DECnet-DOWN",-
description="SNOR04 Nashua DECnet circuit has gone down",-
exception
handler=disk$userdisk:[tassone.mcc]SPRNET_ALARMS_BROADCAST_EXCEPTION.
perceived severity=critical, in domain nashua
The alarm is defined/enabled in domain NASHUA. The map hierarchy is as
follows from the top -
SPR (which contains domain NASHUA)
.
SYDNEY
.
NETWORK (which contains domain NASHUA)
When the alarm fires, the NASHUA domain icon only lights up in the SPR
map, and not in the NETWORK map.
Cheers,
Louis
|
| 1068.5 | works here; check Membertype again | TOOK::HAO | | Thu Jun 06 1991 11:39 | 28 |
| Hi,
I just tried the following, which is not exactly the same alarm rule as
yours, but the same domain hierarchy setup:
TEST
/ \
D1 TEST1
\
TEST2
\
D1
I have an alarm rule defined in Domain D1, which fired. Domain D1
in both TEST and TEST2 changed color. Are you sure that all your
domain membertype is set to Dynamic? In FCL, do the following
commands:
Show domain SPR member NASHUA all char
Show domain NETWORK member NASHUA all char
The Membertype attribute should be dynamic in order for both instances
of NASHUA to change color. Also, the domain hierarchy from SPR down to
NETWORK has to have dynamic membertype. As long as there's one static
domain in the hierarchy, notification gets cut off at that level.
Christine
|
| 1068.6 | %BINGO-E-USER, memory dump | SNOC01::MISNETWORK | They call me LAT | Fri Jun 07 1991 04:25 | 12 |
| Bingo!!
The domain NETWORK (TEST2 equivalent) in SYDNEY (TEST1 equivalent) was
setup as static. I didn't look at this because I had previously set
this domain up as dynamic, and had actually seen alarms up on it.
Somewhere along the line I must have changed it to be
static ( but what worries me is I can't remember doing that ).
Thanks for your help Christine, and sorry for the wild goose chase .
Cheers,
Louis
|