Conference azur::mcc

4915.0. "Problem with Alarm Manager from EMS v2.3 kit" by BACHUS::FOLENS () Tue Apr 20 1993 11:40

    I've installed the alarm manager supplied with the EMS v2.3 kit.
    Before this installation the field test alarm manager worked fine.
    After installation I can't find any templates in my window interface.
    I reinstalled the alarm amanger specifying it was a new installation
    but nothing has changed.
    The command indicated during installation to check out the templates
    gives the following error:
    
    MCC> SHOW RULE_TEMPLATE * all char
    %MCC-I-NOENTREG, No entities of the specified class are currently registered.
                                                                             
    When I specify a particular template it works:
    MCC> SHOW RULE_TEMPLATE .Node4Status all char
    
    Rule_Template DECTOWN:.Node4Status
    AT 20-APR-1993 16:28:52 Characteristics
    
    Examination of attributes shows
                  Descriptive Template Name = "Node4 Status"
                             Entity Classes = ( Node4 )
                           Entity Instances = { Wildcard Supported }
                          Template Severity = Major
                          Template Category = "reachability"
                       Template Description = "This rule uses the state attribute
                                              to monitor the status of a node and
                                              determine when it is no longer
                                              reachable, which is then reported as
                                              an exception"
                              Template Help = "Node4 devices do not have a
                                              reachability attribute, so
                                              reachability is implied based on 
    					      if the device responds to a
    					      request. The state attribute is used
    					      because it is quick and easy to
                                              retrieve."
                                 Value Help = "State has values of ON and OFF,
                                              though OFF is never returned."
                   Rule Exception Procedure = "MCC_SYSTEM:MCC_Alarms_Mail_Exception.
                                               com"
                       Procedure Parameters = "nodename::UserName"
                                  Rule Type = Attribute Comparison
                             Attribute Name = "state"
                        Comparison Operator = Not Equals
                           Comparison Value = "on"
    
    Any ideas what can be wrong? The IVP works ok, except it indicates that
    all templates already exists.
    
    -Geert-

    I have created via the alarm manager application a template and after
    restarting the alarm manager I can still see the template and use
    it to create alarm rules.
    Any suggestions?
    I have also a colleague who tries to use the alarm manager at a
    customer site and get's the follwing error when an attempt is made
    to create a rule:  parse error, validate entity and argument values.
    
    -Geert-
    

    
    Sorry for the inconvenience you have hit. The problem did not get into
    the release notes (an oversite on might part). The problem has to do
    with a change to the installation procedure that now places the default
    database files in MCC_COMMON, the previous installation placed the
    files
    in MCC_SPECIFIC.  Due to recent changings in the database handling
    routines within MCC this installation change is causing the MIR
    routines to have difficulty finding the correct files. If you delete
    the mcc_alm*.dat files from the MCC_SPECIFIC directory your problem
    should
    go away. Please let me know if this does not correct your problem
    (there is an instance where you may have to also remove the
    mcc_mir_directory.dat file).
    
    Sorry for the delay in responding, I have been on vacation.
    
    jill

    Thanks for the reply Jill. After deleting the alarm files in
    mcc_specific everything was ok.
    What about the problem mentioned in .1. Here the alarm mgr was
    installed from scratch.
    
    -Geert-