Conference azur::mcc

3408.0. "Can't show/delete "phantom" alarms rule..." by KAOFS::BOIVIN (Moi, j'viens du nord!) Wed Jul 22 1992 12:58

Good day,

I've running MCC V1.2 on VMS V5.5-1.

I've got an alarm rule that I can't show/delete but it sure fires
when an event occurs. I've set up a Data Collector (MHO_DC)
and wanted to alarm from it. So I created a rule called DC_event with the
expression = OCCURS(Collector *, Any event). 

I then switched over to the iconic map and (mistakenly) inserted the same
rule twice in my domain (2 DC_event rules showed up in the domain).
So, I tried deleting BOTH... The IMPM complained it couldn't find the
rule... I tried FCL... same thing.

Now I can't seem to find it anywhere (with FCL or IMPM)...
Here's a short example:

MCC> show domain NEWF_NS:.DOMAIN.MOHAWK_OIL_VANCOUVER Rule DC_event
Using default ALL IDENTIFIERS

Domain NEWF_NS:.DOMAIN.MOHAWK_OIL_VANCOUVER Rule DC_event
AT 22-JUL-1992 11:38:54 Identifiers

No such entity: Domain NEWF_NS:.DOMAIN.MOHAWK_OIL_VANCOUVER Rule DC_event
                         Unknown Entity = Domain
                                          NEWF_NS:.DOMAIN.MOHAWK_OIL_VANCOUVER
                                          Rule DC_event ,

MCC>

*********** Yet, I still get an alarm from this "phantom" rule!! ********
*********** I created the event using MCC_EVC_SEND		*********

!!!!!!!!!!!!!! Alarm, 22-JUL-1992 11:34:54 !!!!!!!!!!!!!! [2]
Domain: NEWF_NS:.DOMAIN.MOHAWK_OIL_VANCOUVER          Severity: Indeterminate
Notification Entity: Collector NEWF_NS:.mho_dc
Event Source: Domain NEWF_NS:.DOMAIN.MOHAWK_OIL_VANCOUVER Rule DC_event
Event: OSI Rule Fired

                             Event Type = QualityofServiceAlarm
                             Event Time = 22-JUL-1992 11:34:53.45
                         Probable Cause = Unknown
                        Additional Info = { (
                               significance = True,
                                information = "The last event detected:
                                              Collector NEWF_NS:.mho_dc General
                                              Event  22-JUL-1992 11:34:52.83" ),
                                            (
                               significance = True,
                                information = "Event: General Event ""Test
                                              Title""  Event Text = ""BC is
                                              booting""" ),
                                            (
                               significance = True,
                                information = "(Occurs (Collector * any event))"
 ) }
                         Managed Object = Collector NEWF_NS:.mho_dc
                     Perceived Severity = Indeterminate



MCC> 

I even tried running MCC_ALARMS_EXTRACT_RULES:

NEWF> run SYS$COMMON:[SYSEXE]MCC_ALARMS_EXTRACT_RULES

MCC_ALARMS_EXTRACT_RULES - V1.2.0
  - Generating a Procedure to Rebuild the DECmcc Alarms MIR
  - Output File: mcc_alarms_rules.com

0 Rules processed.

>>> EXIT - Alarms MIR is empty; No Rules extracted

So, if the Alarms MIR is empty, why am I still getting alarms for
a supposedly deleted rule?

Any hints?

Thanks,

Ed

Entered as QAR 3300.

This is the SSB kit, right?

Thanks Erik,

Yes, it's the SSB kit dated 2-Jul-1992.

Any idea how I can work around this problem for now?

Thanks,

Ed

Ed-

  Sorry, I don't know why this would be happening.
When one of the module developers has been able to look at your QAR,
perhaps they can get you a workaround.

-- Erik

As an update:

I rebooted the node MCC was running on... Yes, everything is back to
normal. The rule is really gone.

Thanks,

Ed

For the record - we believe that this situation was due to the number
of processes involved.  On VMS, it is possible to remove a rule from
the on-disk alarms MIR without disabling that rule in a different process which
currently has that rule enabled.  This would explain why a reboot clears
the problem.

-- Erik