Conference azur::mcc

2530.0. "Notification events problem" by ROM01::PROFETI (Livia Profeti - SWAS Rome) Wed Mar 11 1992 08:13

    I've some problem to get configuration event from MCC BMS/VMS.
    
    My intention was both to receive a notification when a certain event
    occurs on a remote node and to issue an alarm about that.
    
    I've carefully read the note 2137 and I've followed the instruction put
    in the .1.
    
    For first I'd like to know if I've understood well the commands meaning:
    
    
    > from note 2137.1
>    MCC> !
>    MCC> ! set up to sink events to MCC from router
>    MCC> !
>    MCC> pass node4 <routing_node> outbound stream <mcc_node> -
>    _MCC> remote sink monitor class=4, event type = -
>    _MCC> (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18), database=permanent
 
    I suppose this command is to allow the <routing node> to send event to
    the MCC node. 
    
>    MCC> ! set up to sink routing host events to itself
>    MCC> !
>    MCC> pass node4 <routing_node> outbound stream <routing_node> -
>    _MCC> remote sink monitor class=4, event type = -
>    _MCC> (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18), database=permanent
>    MCC> !
    
    I supposed this command is to allow the <routing node> to receive events
    on itself, so, if anyone doesn't need it he can not to do it.
     
>    MCC> ! set up local sink monitor
>    MCC> !
>    MCC> set node4 0 local sink monitor initial name mcc_dna4_evl, -
>    _MCC> initial state off
>    MCC> !
    
    I suppose this command is to allow the MCC to receive events.
    
>    MCC> ! set up the event filtering
>    MCC> !
>    MCC> pass node4 <mcc_nod> outbound stream <mcc_node> -
>    _MCC> remote sink monitor class = 4, event type = -
>    _MCC> (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18), -
>    _MCC> database = permanent
    
    I suppose this command is to allow the MCC node to receive its own
    event, so I don't need it I can not to do it.
    
>    MCC> !
>    MCC> ! enable the sink
>    MCC> !
>    MCC> enable node4 0 local sink monitor
    
    That's obvious.    
    
    I made all these command (changing the class, I specified class 0). One
    problem I had to issue this command was not to able to specify
    DATABASE=PERMANENT, I received a "UNKNOW QUALIFIER ERROR", so I leaved
    this argument (for me is an argument and not a qualifier ...) and the
    command was ok.
    
    Also I've let the MCC enabled to receive notification, but nothing
    appear on the MCC window, althoght I regulary receive event messages on
    normal terminals with the $ REPLY/ENA command issued.
    
    Also I tried with an alarm rule issued, here it is the expression rule:
    
    (OCCURS(NODE4 x CIRCUIT Y ANY CONFIGURATION EVENT))
    
    I put "any configuration event" instead "counters zerod" I needed becouse 
    I've understood there's some parsing problem with the FT version.  
    Nothing happens with the rule too.
    Also I've tried to "CREATE" commands before and "PASS" commands after, 
    no results.
    
    As I've noticed other collegues don't have problem with the events
    notification , is there anything wrong or missing in my procedure ?
    
    Many thanks in advance,
    Livia