Conference azur::mcc

3953.0. "Customer feedback" by STKMCC::LUND (Niklas Lund) Fri Oct 23 1992 12:57

Hi !

This is the requirments of one of our customers who will choose MCC if these
changes are incorparated. How much can be done or is already done in 1.3 ?


Please make the severity text strings customizable in 
MCC_NOTIFICATION_RESOURCE.DAT ie critical = A-LARM , major = B-LARM .
All apperence of critical in iconic Map and notification window should be sub-
stituted with A-LARM.

Please make it possible to save the filtersettnings in the Notification Window  
on a per user basis.

Our customer needs a confirm of alarms function and it should work like this.
All incomming alarms should change the color of the object and also make it
blink. When the confirm function is used the object should keep the color and
stop the blinking. When one operator confirms an alarm with this function all
operators should see that the icon stops blinking.  

Please add a acknowledge button when deregistering domains from iconic map.

The possibility to always see the status of the network in a multidomain
hirarcy is also very importent. This has been discussed in many notes before
and i know that some work has been done for 1.3 in this area. 

My customer also have strong needs for a asset tracking database closely 
integrated with MCC, where you can define new objects with your own reference
attributes and create links between objects.

Last but not least this is the most importent one and it's about the exceptions
When some part of the monitored network becomes unreachable a lot of exceptions
start to fire on the objects in the unreacable area. This is a pain because you
have no easy way of disabling alarms in MCC (VMS) today. 

Define a new attribute on alarm rules called new_exception_handling.
= True/False. When it's false operation should be as it is today.

When it's true and the first and the second exception occurs operation should
be as it is today. But if the third "evaluation" in a row is a exception only
replace the line of the former exception in the notification window with this
one, no update of the icon color and no exception procedure should be executed.
Do the same for the forth, fifth exception and so on.
With this scheme you would only end up with two lines in the notification-
window, giving you the time of the first and last exception.
This would be a nice feature to prevent you from geting drowned in exceptions
if one critical gateway dies. 

Regards, Niklas

I normally try to be helpful, but it sounds like you cab probably kiss this one
goodbye...  Sorry.


I'm not going to tell you a lot of workarounds (there probably are a few to
*some* of your requirements) because almost all of the stuff is NOT done in
v1.3, nor is it going to happen for 1.3.  V1.3 is on a very short, very tight
release cycle and the code freeze is today.   Almost all of what you are
requesting will require changes *internal* to the product (i.e. can't be bagged
on later) and as such are an unacceptable schedule risk for V1.3.

Wish I could be more hopeful on this one.

/doug

>Please make the severity text strings customizable in 
>MCC_NOTIFICATION_RESOURCE.DAT ie critical = A-LARM , major = B-LARM .
>All apperence of critical in iconic Map and notification window should be sub-
>stituted with A-LARM.

Ugh.  I just checked, and these are hard-coded i.e. no possibility of
changing them even by playing with the dictionary.

>Please make it possible to save the filtersettnings in the Notification Window  
>on a per user basis.

Ta da!  Done for V1.3.

Everything else isn't going to be in V1.3.