Conference azur::mcc

3363.0. "OCCURs, Notification not firing, OPCOM is fine" by ANOSWS::COMFORT (Spent a little time on the hill) Wed Jul 15 1992 11:42

    
    Hi,
    
    I seem to be having a problem getting OCCURs rules to fire (at all)
    w/ MCC EFT 1.2.7.  I have read the notes about the startup problems
    and so I do a run/detached.  The objects is being declared and when
    I reply/ena=net, I get all the events via opcom, however nothing
    is happening w/ MCC.  I have the occurs rule running and notification
    enabled for that domain.
    
    
NCP>sh k links
    
Known Link Volatile Summary as of 15-JUL-1992 10:36:42
    
Link       Node           PID     Process     Remote link  Remote user
    
16796   1.34 (PHMCC)     000001CD  EVL              16797  MCC_DNA4_EVL  
16797   1.34 (PHMCC)     000002AA  MCC_DNA4_EVL     16796  DECNET
8202    1.59 (PHVMCC)    00000096  DECW$SERVER_0     8367  COMMSYS
8584    4.206 (FRV206)   00000096  DECW$SERVER_0      258  COMMSYS
NCP>
    
    MCC> show mcc 0 alarms rule phrtr1_reach_change all attr, in domain
    upper_merion
    
    MCC 0 ALARMS RULE phrtr1_reach_change
    AT 15-JUL-1992 09:52:21 All Attributes
    
                                       NAME = phrtr1_reach_change
                                      State = Enabled
                                   Substate = Running
                  Result of Last Evaluation = In progress
                           Current Severity = Indeterminate
                         Creation Timestamp = 15-JUL-1992 09:52:04.47
                           Evaluation Error = 0
                            Evaluation True = 0
                           Evaluation False = 0
                                 Expression = (occurs(node4 .dna_node.phrtr1 
					       remote node * node reachability
					       change))
                         Perceived Severity = Indeterminate
                             Probable Cause = Unknown
    MCC>

    
    NCP>
    %%%%%%%%%%%  OPCOM  15-JUL-1992 10:34:26.62  %%%%%%%%%%%
    Message from user DECNET on PHMCC
    DECnet event 4.14, node reachability change
    From node 1.36 (PHRTR1), 15-JUL-1992 10:36:30.66
    Node 1.966, Unreachable
    
NCP>show k logging
    
    
    Known Logging Volatile Summary as of 15-JUL-1992 10:41:56
    
    
     Logging sink type = monitor
    
        Sink Node       Source               Events          State Name
    
                                                                on
        1.34 (PHMCC)    (All sources)        0.0-9         MCC_DNA4_EVL 
                        (All sources)        2.0-1
                        (All sources)        3.0-2
                        (All sources)        4.0-19
                        (All sources)        5.0-21
                        (All sources)        6.0-5
                        (All sources)        7.0-11
    NCP>                                                                   

    Am I doing something wrong here?  This seems to look the same as
    with MCC V1.1, which is working with no problems.
    
    Thanks and regards,
    
    Dave Comfort

  Could you try the GETEVENT directive - to see if the event is getting
  into the system ...

  MCC> getevent node4 .dna_node.phrtr1 remote node * node reachability

  /keith

    
    It is working today...after I issued a 
    
    	set logging monitor state off
    	set logging monitor state  on
    
    I thought I had done this yesterday, but cannot be sure.
    
    Thanks,
    
    Dave