Conference azur::mcc

5561.0. "Software logic error V1.3" by COPCLU::SANDGREN (Keep it simple) Fri Sep 03 1993 09:31

    System SDN1 is a VAX 4000-300.

    DECmcc V1.3 VAX/VMS V5.5-2.

Customer has the following problem with several alarms. This particular alarm
is on circuit state between a DMB32 and a DECrouter 250. He gets exactly the
same problem on other types of equipment, f.ex. CISCO and Vanfleet routers:



CREATE DOMAIN StatensDatanet RULE Prout2_3_state -
 EXPRESSION = (circuit prout2_3 nmfoperationalstate = Disabled, at every 00:10:0
0), -
 CATEGORY = "Circuit state", -
 DESCRIPTION = "Circuit state changed PROUT2 port 3", -
 ALARM FIRED PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM, -
 ALARM EXCEPTION PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM, -
 ALARM FIRED PARAMETER = "@mcc_disk:[mcc.alarm_rules]mail_alarm.dis", -
 BATCH QUEUE = MCC_ALARMS, -
 AUTO ENABLE = NO, -
 SEVERITY = Major

which is based on 'CIRCUIT entities', which are registrated like this:


Examination of Attributes shows:
                          aEndpointName = (
                                 instance = Node4 SDN_NS:.dna_node.prout2
                                            Circuit serial-2 ,
                                 objectid = %X303030,
                               objectname = "circuit
                                            .statensdatanet:.not_set_yet" )
                    administrativeState = Unknown
                       circuitBandwidth = (
               		      azBandwidth = 9.6,
                              zaBandwidth = 9.6 )
                            circuitType = (
                                     Mode = Unknown,
                                     type = unspecified )
                         componentNames = (
                                     type = null,
                               components = (  ) )
                  compositeCircuitNames = {  }
                  transmissionDirection = Unknown
                          zEndpointName = (
                                 instance = Node4 SDN_NS:.dna_node.shae Circuit
                                            dmb-0 ,
                                 objectid = %X303030,
                               objectnam = "circuit
                                            .statensdatanet:.not_set_yet" )
                    ComponentDomainName = SDN_NS:.NOT_SET_YET

 Hundreds of mails like the following are generated:


From:   SDN1::SYSTEM       "Circuit state changed PR" 27-AUG-1993 11:54:19.76
To:      @mcc_disk:[mcc.alarm_rules]mail_alarm.dis
CC:
Subj:   Notification of exception " Domain SDN_NS:.STATENSDATANET Rule Prout2_2_
state  27-AUG-1993 11:54:42.10"

    Rule name:     Domain SDN_NS:.STATENSDATANET Rule Prout2_2_state
Managed Object:    MCC 0 ALARMS RULE Prout2_2_state
    Domain:        Domain SDN_NS:.STATENSDATANET
  Occurred at:     27-AUG-1993 11:54:42.10
     Category:     Circuit state
  Description:     Circuit state changed PROUT2 port 2
     Severity:     Indeterminate
   Expression:     (circuit prout2_2 nmfoperationalstate <> Enabled, at every 00
:10:00)
    Exception:     Software logic error detected   <--------------------
                   %MCC-S-SPECIALIZED_EXC, success with management module-specif
ic exception reply

	This is extremely confusing, the operators at the customer don't
	have a clue about what this means..


	Thanks for your help,

	Poul Sandgren, Network Group /Denmark

    the fastest way to track an "alarms" problem is to do the command
    oustide of the alarm rule. In this case do the circuit show command
    and see what type of error is being returned. It might shed more
    light on the problem.  But the software logic errors are usually
    something returned in desperation. 
    
    Have to think about this one some more.
    

    Hello,
    
    Did anyone manage to resolve this problem.
    
    I have a customer getting similar exceptions on circuit alarms -
    Software logic error detected.
     %mcc-f-specialised_exc; success with management specific exception
    reply
    
    A show on the entity attribute works fine.
    
    MCC 1.3, VMS 5.5-2.
    
    The alarm is almost identical to the one in the Circuit AM user manual
    on page 3.29.
    
    
    Any help appreciated,
    
    Thanks 
    
    Jon