Conference azur::mcc

3398.0. "Alarm rule terminates with: %MCC, Invalid handle parameter" by ANTIK::WESTERBERG (Stefan Westerberg DS Stockholm) Tue Jul 21 1992 12:24

Hello, I have a problem using a wildcard alam rule. In the domain I have
2 DECbridge 500, 6 LANbridge 200 and 2 LANbridge 100. The alarm rule attributes
look like this when the rule terminates:

DetMCC> show mcc 0 alarms rule * all attr, in domain Bridge_auto_config

MCC 0 ALARMS RULE Bridge_test
AT 21-JUL-1992 16:55:05 All Attributes

                                   NAME = Bridge_test
                                  State = Disabled
                               Substate = Disabled by error condition
                           Disable Time = 21-JUL-1992 16:48:45.05
                        Error Condition = "%MCC, software error: invalid handle
                                          parameter, The rule has been disabled
                                          "
                Time of Last Evaluation = 21-JUL-1992 16:48:44.68
              Result of Last Evaluation = Error
                       Current Severity = Indeterminate
                           Error Entity = Bridge ANTIK_NS:.HUVUDSTA_DES LINE 1
                     Creation Timestamp = 21-JUL-1992 16:42:40.62
                       Evaluation Error = 1
                        Evaluation True = 0
                       Evaluation False = 198
                             Expression = (Bridge * line * port module state <>
                                          forwarding, at every 00:00:40)
                     Perceived Severity = Critical
                         Probable Cause = Unknown

It always seems to fail at the 199 poll when using 40s polling intervall. This
problem has been reproduced on two separate system running on the same hardware
and software platforms. 

Also if the rule is enabled from the iconic map you can't look into any bridge
line attributs after the rule has failed.  It always fails with the error 
meaasge:

Map Window Message: Software error: Invalid handle parameter

All user quotas are higher or equal to the minimum required.


Hardware:	VAX Station 4000 m60 with 32 or 16 Mbyte of memory
Software:	VAX/VMS 5.5
		DECmcc BMS V1.2
		DECmcc ELM AM V1.2
		DECmcc ELM FM V1.2
		DECmcc TS AM V1.0

Regards Stefan

I have entered this as QAR 3298.
However, what do you mean by

>		DECmcc TS AM V1.0

>However, what do you mean by
>
>		DECmcc TS AM V1.0
				  => DECmcc TSAM V1.0.0 SSB

/Stefan

>		DECmcc TS AM V1.0
				  => DECmcc TSAM V1.0.0 SSB

Of course.  I misread your note the first time.  Sorry.

-- Erik

    Hi,
    
    I also have a customer who is seeing this problem...was QAR 3298
    resolved ? - can anyone give me a pointer as to where I can find 
    this information?..If it was resolved  has a patch been produced
    or  will we have to  wait for MCC  v1.3 ,if this is the MUP that
    is  mentioned elsewhere in this Notesfile ?...
    
    Thanks,
    
    Sandie../  (7833 3833, UK CSC)

QAR 3298 is in an old internal database, so unfortunately there is no
way for you to look at it directly.  There is no answer yet.  I have
added your note to the QAR text.

FYI, V1.3 is a future release, not a MUP.

    
    It appears that the problem was caused by the Bridge AM.
    I was able to get INVALID Handle problem by issuing Show command
    fro FCL w/o using Alarms FM:
      MCC> sho bridge 08-00-2B-0F-2F-48 line * port module state, at every
           00:00:05
    
      ... This command ran for about 8 minutes and stopped with an error:
      %MCC-E-INV_HANDLE, software error: invalid handle parameter
      MCC>
    
    This error is the same error as seen in .0
    
    The QAR 3298 is the same problem as the QAR 502 of MCC012_EXT database.
    I have entered an answer to the QAR 502. 
    The QAR will be transferred to the Bridge AM.
    
    William

Thanks!!

Lee Roth (with this problem)

    
    The INVALID HANDLE problem was in the Bridge AM, and had been fixed
    for V1.3 SSB of Bridge AM.

    William