[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

4703.0. "Alarm substate: shutdown in progress with v1.3" by BACHUS::FOLENS () Wed Mar 17 1993 04:15

    I've installed the SSB kit v2.3 of EMS. After some testing with alarms
    I've encountered the following problem that also existed in v1.2.3 of
    BMS.
    I've created a rule that is testing if the lines of a bridge is in 
    forwarding state.
    MCC> sho domain .geertf.keiberg rule bridge_bet112_118_forwarding all
    char
    
    Domain DECTOWN:.geertf.keiberg Rule bridge_bet112_118_forwarding
    AT 17-MAR-1993 10:07:30 Characteristics
    
    Examination of attributes shows:
                                 Expression = (Bridge
                                             
    DECTOWN:.mcc_bridges.bet112_118 LINE
                                              *  port module state =
    forwarding, at
                                               every=00:00:18)
                                   Severity = Minor
                             Probable Cause = Unknown
    
    The bridge is currently down which results in an exception alarm.
    The status of the rule shows it is enabled and running with the error
    condition: cannot communicate with target.
    Now I try to disable the rule because it is causing to much overhead.
    The status now shows me: 	state: enabled
    			        substate: shutdown in progress
    				error condition: management protocol error
    I don't think this situation is normal. Is this a known problem?
    
    -Geert-
     
T.RTitleUserPersonal
Name
DateLines
4703.1Looks like a bug - can you QAR this ?MOLAR::ROBERTSKeith Roberts - Network Management ApplicationsThu Mar 18 1993 11:3712
Geert,

>    The status now shows me: 	state: enabled
>    			        substate: shutdown in progress
>    				error condition: management protocol error
>    I don't think this situation is normal. Is this a known problem?

  No - this is not a normal situation.  Can you try doing a show 
  on the bridge (which is not up) and while waiting hit control/c ?

  /keith

4703.2results of commands requested.BACHUS::FOLENSMon Mar 22 1993 11:4422
    Without ctrl-c:
    
    MCC> show bridge .mcc_bridges.bet112_116 all char
    
    Bridge DECTOWN:.mcc_bridges.bet112_116
    AT 22-MAR-1993 17:33:48 Characteristics
    
    Cannot communicate with target
    
    With ctrl-c:
    MCC> show bridge .mcc_bridges.bet112_116 all char
    
    Bridge DECTOWN:.mcc_bridges.bet112_116
    AT 22-MAR-1993 17:34:21 Characteristics
    
    Management protocol error
    
    
    -Geert-
    
    p.s. Maybe thi s problem is solved with v1.3 of ELM AM?
    
4703.3Looks like bridge is not reachableQUIVER::HAROKOPUSMon Mar 22 1993 12:406
    I don't understand what the problem is here.  The first show
    command indicates that you can't communicate with this bridge.
    Have you been able to determine why the bridge is not reachable?
    I doubt it is an ELM issue.
    
    -Bob
4703.4Intended behaviour?BACHUS::FOLENSTue Mar 23 1993 03:048
    
    Please read .0 carefully. It is not normal you cannot disable an alarm
    rule for an entity that is not reachable or is this intended behaviour?
    I added the info in .2 because it was requested in .1.
    
    -Geert-
    	

4703.5Need to understand how Alarm rule is disabledQUIVER::HAROKOPUSTue Mar 23 1993 10:269
    OOps sorry.  I didn't read .0 too carefully.   I'm not sure why
    you can't disable the Alarm rule.  Can one of the Alarms developers
    explain the process that occurs when an Alarm rule is disabled?
    That way I can better understand if the Bridge AM is doing anything
    to prevent the rule from being disabled.
    
    Thanks,
    
    Bob
4703.6Enter - stage rightMOLAR::ROBERTSKeith Roberts - Network Management ApplicationsTue Mar 23 1993 13:0042
re: .2

>    Without ctrl-c:
>    
>    MCC> show bridge .mcc_bridges.bet112_116 all char
>    
>    Bridge DECTOWN:.mcc_bridges.bet112_116
>    AT 22-MAR-1993 17:33:48 Characteristics
>    
>    Cannot communicate with target

  A show to a bridge has timed out (or something) - the command
  completed with an exception (cannot communicate with target) returned.

>    
>    With ctrl-c:
>    MCC> show bridge .mcc_bridges.bet112_116 all char
>    
>    Bridge DECTOWN:.mcc_bridges.bet112_116
>    AT 22-MAR-1993 17:34:21 Characteristics
>    
>    Management protocol error

  The same show to the same bridge .. but this time before the timeout
  occured, Control/C was pressed.  The FCL issues a Thread Alert Termination
  which is caught by the Bridge AM.  The Bridge AM should cancel the request
  and return the MCC_S_ALERT_TERMREQ status.  But instead, somehow the
  Thread Alert Termination is causing the 'Management protocol error' 
  exception to pop out.

  When you disable an Alarm rule, the same Thread Alert Termination is sent
  to the Management Module (MM) which Alarms is calling .. again, in this case
  the Bridge AM.  The proper protocol is not followed.  Alarms is expecting
  the MM to return the MCC_S_ALERT_TERMREQ status, but instead is getting
  an exception.

  Because the MCC_S_ALERT_TERMREQ status is not being returned to Alarms, Alarms
  has no idea that the Rule is shutting down.  The bug appears to be in the
  Bridge AM, or the MCC ethernet sub-system.

  /keith
    
4703.7Will look ay Bridge AMQUIVER::HAROKOPUSWed Mar 24 1993 11:566
    Thanks Keith,
    
    I'll take a look at how the Bridge AM handles the thread termination
    request.
    
    -Bob
4703.8I'd be glad to help ...MOLAR::ROBERTSKeith Roberts - Network Management ApplicationsThu Mar 25 1993 08:217
>> Thanks Keith,
>> I'll take a look at how the Bridge AM handles the thread termination
>> request.

  Sure thing - let me know if I can be of any help

  /keith