Conference azur::mcc

5419.0. "SNMP linkup alarm and targeting deletion problem" by GIDDAY::WAN (Denny Wan, Sydney CSC) Mon Aug 02 1993 23:45

Hi, 

I have encountered two problems under DecMcc V1.3.

1. I created the following alarm rule

Create Domain WAVE3_NS:.IP-HOSTS Rule tl350_linkup  -
  Expression   = (OCCURS (SNMP TL350  linkup,2,  00:00:02.00)), -
  Severity     = Clear, -
  Category     = "linkup", -
  Description  = "Translan TL350  - Link up rule fired.", -
  Alarm Fired Procedure        = USER$DISK:[MCC]MCC_ALARMS_MAIL_ALARM.COM, -
  Alarm Exception Procedure    = USER$DISK:[MCC]MCC_ALARMS_MAIL_EXCEPTION.COM, -
  Alarm Fired Parameters       = "chong"

and notification request for "SNMP * ANY EVENTS"


I found that the alarm rule does not get fired even though the traps are shown
to have been received in the notification window. By disabling notification,
the alarm linkup alarm rule get fired. Linkdown alarm rule doesn't seem to be
affected. 

Moreover, a customer reported a slightly different sympton. In his case, the
alarm rule get fired but the icon does not change colour.

2. A customer reported a problem whereby he cannot delete a targeting entry.
The entry looks like this :

	source 	SNMP ABC:.translan.*
	event 	linkdown
	object	snmp #1
	target	snmp #1
	severity major

He is able to create a new one with exactly the same details and delete it.
This implies that DecMcc though they are different entries. Trying to delete
the old one result in "specified entity not defined" error. Trying to define 
the entity twice, Mcc says "there is no change in the entity". It would appears
to me that the old entry has indeed been deleted from the MIR but however the
directory operation somehow retained a record for the old entry. Any ideas
how I might be able to re-synchronize the records?


Regards,


Denny.