Conference azur::mcc

    Hi Raj,
    
    The '*' character is one of the legal characters you can use to name
    your domains; but, it is not a wildcard character, it is just a
    character.  I'm not really up on how to name domains, so maybe
    someone else could provide more information here.
    
    It looks like you want to create a rule in ALL domains.  Unfortunately
    this can not be done.  The IN DOMAIN qualifier can not be wildcarded.
    
    Since ALARMS does not check to see if a domain exists, you can create
    rules in whichever domains you choose.  In this case you are telling
    ALARMS that you are creating a rule in domain '*'.
    
    When the rule fires, your command procedure will execute.  (In the
    next release, the sample MAIL and LOG procedures will display the
    domain.)  ALARMS then generates the event that the rule fired in
    domain '*'.
    
    Since '*' is not a wild card (it does not mean ANY and EVERY) and
    there are no domains on your map named '*', there is no MAP change.
    
    Could you describe a little more about what your customer needs are?
    
    Thanks,
    
    		aud...

    Hi Aud,
    
    My customer wants to create multiple domain and some of the entities in
    those domain may be the same.
    
    So if the alarm fires, he wants to be notified, in both domains.  He
    could be looking at both domains or just one domain at that time.
    
    Is it possible to state IN DOMAIN = xxx,yyy,zzz
    
    The above might help.
    
    Thanks
    Raj

    The domain name that is specified for the IN DOMAIN qualifier is of
    datatype fullname, such that '*' really should mean wildcard.  However,
    Audrey is right in that wildcarded fullnames is not supported for
    the IN DOMAIN qualifier.  The PMs should add a check for the qualifier
    processing to reject any fullname wildcard characters (as defined in
    the SRM).
    
    At this point, the FCL will support IN DOMAIN x, DOMAIN y, DOMAIN Z ...
    etc.  However, I don't know if any AMs  or FMs are able to handle 
    retrieving the multiple domains.
    
    Is this really important?
    
    Christine
    

    Hi Christine,
    
    Yes, it is pretty important.  I have demonstrated DECmcc to about 6
    customers in Singapore so far; these are more or less confirmed sales 
    and they all have asked for this feature.
    
    They are mainly government ministries where systems are shared and thus
    multiple domains need to be created and managed.  So the notification should
    reach both domains when viewed through the Iconic PM.
    
    Raj

       Ramaraj,

       From your notes .0, .2, and .4 its very clear to me that you have a
       requirement on the Notification services to do a notification to
       multiple domains based on an Alarms Rule firing,  in a perticular
       domain.

       What I am not so clear about is if you need to CREATE a rule and
       associate the rule with multiple domains. 

       In past both requirements have surfaced in various design meetings
       but due to the resource constrains we put them off for future
       versions. 

       Have I captured your requirements right? If so   is it possible for
       you to put some priority on the above two requirements. 

       Thanks,

       Anil Navkal

I have also spoken to several customers who all really like MCC and all
asked about support for wild card alarms.   It significantly simplifies 
the maintenance of rules.  /Claudia

    A real useful feature as an extention to the above discussion would be
    to allow a creation of a rule like the following;
    
    CREATE MCC 0 ALARMS RULE BAD_TYPE -
      EXPRESSION=(NODE4 * TYPE <> EndNodeIV, AT EVERY 12:00:00), -
      PROCEDURE=MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM, -
      EXCEPTION HANDLER=MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM, -
      CATEGORY="Configuration problem", -
      DESCRIPTION="This checks to ensure that end nodes do not inadvertently -
      become routing nodes. This can cause MAJOR problems in your network.", -
      QUEUE="ALARMS$BATCH", -
      PARAMETER="NODE_ALARMS.LOG", -
      IN DOMAIN = some-domain-name
    
    This would permit a common rule to be applied to all nodes in a domain
    without having to type in and enable each rule.
    
    s/rob

    Hi Anil,
    
    Looking at the replies this seems like a must have feature.  
    
    Create mcc 0 alarms rule xxx
    ....
    ....
    in DOMAIN = domaina, domainb, domainc (or maybe *)
    * will mean check all domains for existence of that entity.
    
    The user only has to activate one alarm rule and if it fires it should
    notify all the domains which has that entity.
    
    Enabling an alarm to monitor, eg all node4 entities for a specified
    condition as mentioned in .7 is another priority.
    
    Thanks
    Raj
    
    For my customers, this is a very high priority.

    Hi Ramaraj,

    Let me try to clear some confusion here. The entity that you
    make your rule on, does not have to be in the domain under which
    you are creating the rule. There is no restriction on the entities
    existence on any particular domain. What we don't do when such a
    rule fires is notify a set of domains about the rule firing.

    That's the requirement I tried to identify in my previous note.

        
    >Enabling an alarm to monitor, eg all node4 entities for a specified
    >condition as mentioned in .7 is another priority.
    
    This translates in to a support for Global wild cards in a rule expression.
    We are hoping to offer this functionality in V1.2!

>    For my customers, this is a very high priority.

     By this statement I gather you are referring to the requirement of 
     MCC's ability to Notify a set of Domains about Alarms rule firing. 
     Am I right?

    Did I miss any thing?

    - Anil
    

    Hi Anil,
    
    That's my mistake.  Your statement is absolutely correct.  Looking
    forward to V1.2!! and all the goodies that are to come with it.
    
    Is there a list that you could give as to what are the goodies we can
    expect in V1.2 and the expected date of release.
    
    This product is creating alot of excitement and customers are impressed
    with architecture.  It's an excellent product.  
    
    My salute to those who designed and developed it.
    
    Regards
    Raj