Conference azur::mcc

5870.0. "Overwritting and Clearing Severities" by ARRODS::GILLJ (John, DTN 847-5849) Wed Feb 16 1994 05:17

Hi,

VMS v5.5-2 
MCC v1.3

Our implementation of MCC will result in the management systems receiving a 
lot of data collector events.  

We are experiencing the following...

A data collector is sent to node4 in a domain severity critical (node icon 
changes colour to red).  Notification window displays text against the 
alarm.

A second event occurs against the same node (e.g. adjacency down)  this 
event is classed as major (node icon changes colour to yellow).  Notification 
window displays text against the alarm.

The second event has overridden the first (in terms of the icon colour).  

Our customer would like to be in a situation where event severities do not 
change the colour of an icon unless they are changing the icon colour to a 
more severe one.  e.g.  Critical alarms should always change the colour of 
an icon to red, but Major alarms should not change the colour of the icon 
if it is already displaying the Critical colour. 

It appears MCC always displays the latest event against an icon. Is there 
any way in which MCC can be configured to display the most severe event 
against an icon?

Also...

If an icon has a major alarm mapped against it, followed by a critical 
alarm - it's colour changes to yellow then to red.  If I select the 
critical notification and RESET it the icon changes back to GREEN, 
i.e. both the Major and Critical alarms get reset.

Our customer would like to be in a situation where only the current alarm 
was reset.  I.E. The Critical alarm would be reset but the Major alarm 
would still be displayed.  Is this possible?


Regards,

John

    

John,

The Iconic Map has 2 modes of severity propagation : Highest and Latest. From
what you are describing, it  looks like you are using the "Latest" mode. 

Can you check in the Options menu, submenu map the value of the propagation
switch ? 

I haven't used the "reset selected notifications" feature, so I can't help you
there, but if you are using this menu entry and not the "reset all notif" then
it sounds like a bug. If so, please report it. 

Best regards,

Marc. 

John,

In addition to Marc's suggestion, there is also another technique which can
be used for correlating DATA COLLECTOR events. After you ensure propagation is
set to HIGHEST note the following.

The TITLE field of the collector event controls correlation. Those events which
have 'identical' titles will overwrite each other, while those which have 
different titles will remain with the highest being displayed.

Example:

send_event node collector target "title1" "text" major decnet !icon=major
send_event node collector target "title2" "text" warning decnet !icon=major
send_event node collector target "title1" "text" clear decnet !icon=warning

This is very handy for 'pairing' up matching events which can clear each other
while still showing others. I'm not sure this is exactly what you're looking 
for but your customer may find uses for it.

cheers,
brad...

    Brad and Marc,
    
    Thank you for your quick responses.
    
    I had my propagation set to HIGHEST.  However all events were being
    sent through with the same Event Title.
    
    When I modified the titles everything worked as I wanted.
    
    Thanks again,
    
    John