Conference azur::mcc

    
    MCC> !
    MCC> ! set a host up as a router
    MCC> !
    MCC> set node4 <routing_node> routing type routine iv 
    MCC> set node4 <routing_node> max broadcast nonrouting 1023
    MCC>        ! 1023 is the worst case scenario per area
    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
    MCC> !
    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> !
    MCC> ! set up local sink monitor
    MCC> !
    MCC> set node4 0 local sink monitor initial name mcc_dna4_evl, -
    _MCC> initial state off
    MCC> !
    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
    MCC> !
    MCC> ! enable the sink
    MCC> !
    MCC> enable node4 0 local sink monitor
    
    
    
    MCC> !
    MCC> ! now to do what you asked, you want to use the retargetting
    MCC> ! commands to have the remote node events trigger the right
    MCC> ! icon color change
    MCC> !
    MCC> assign target domain <domain_your_nodes_in> -
    _MCC> event source = node4 <routing_node> circuit * adjacent node *, -
    _MCC> managed object =(node4 * circuit * adjacent node #1), -
    _MCC> event name=(adjacency down), -
    _MCC> target entity = (node4 #1), -
    _MCC> target severity = <severity_of_your_choice_or_none>
    MCC> !
    MCC> ! now startup a notify command to wait for the events
    MCC> !
    MCC> notify domain <domain_your_nodes_in> -
    _MCC> entity list = (node4 <routing_node> circuit * adjacent node *),-
    _MCC> events=(adjacency down)
    
    From the iconic map, use the "Applications" menu to bring up the
    notification application. From the notification display window 
    use the "Notify Requests" button to bring up the forms for starting
    up a new notify command.
    
    As an FYI the "#1" in the assign target command is what provides the
    ability to use the name returned in the adjacent node child entity as
    the name for the node4 to turn a color.
    
    We suggest this mechanism so as to reduce the overhead associated with
    starting a rule. BUT** if you want to take an action when the event
    occurs then you do need to define an occurs rule for the adjacency down
    event. You would then use the following targeting directive to cause
    the right icon to turn a color:
    
    MCC> assign target domain <domain_your_nodes_in> -
    _MCC> event source = domain <domain_your_nodes_in> rule <occurs_rule>, -
    _MCC> managed object =(node4 * circuit * adjacent node #1), -
    _MCC> event name=(adjacency down), -
    _MCC> target entity = (node4 #1), -
    _MCC> target severity = <severity_of_your_choice_or_none>
    
    
    Please note, that this example is being incorporated into the
    notification use manual. If you have any additional ideas or
    information that you think would be useful please let us know.
    (Of course the manual will provide more explaination about what the
    commands are doing.)
    
    jill
    

    
    
    OOOOOOOOOOOOOOOOOOPPPPPPPPS!!!
    
    I COPIED THE COMMANDS!!! I admit it I just copied the commands off
    of the existing write up! and the ()'s in the ASSIGN TARGET commands
    are wrong! they should be quotes "" instead. 
    
    Sorry about that.
    

Hi,

I thought this part of the discussion was better fitted to this note rather
than 2082.

I have yet to get ANY function to work with Adjacency Down/Up events with
this kit. This includes both ALARMS and NOTIFY. We can deal with targetting
once I get over this hump. From FORMS mode if I do a GETEVENT NODE4 BBPK99
CIRCUIT SYN-0 <Help> this is a partial listing I receive:

    Automatic Service
    Passive Loopback
    Aborted Service Request
    Automatic Counters
    Counters Zeroed
    Node Unreachable Packet Loss
    Node Out of Range Packet Loss
    Oversized Packet Loss
    Packet Format Error
    Partial Routing Update loss
    Verification Reject

Please note there is NO adjacency events listed here and hence when I try
to create a rule I get errors. When I try a NOTIFY command this is the
result:


notify domain .pko-24 -
entity list=(node4 bbpk99 circuit * adjacent node *),-
events=(adjacency down)
!
!%MCC-S-NOTIFSTART, Notify request 4 started
!
display noti
!
!Notify requests currently in progress:
!
!Entry  Status   Command
!-----  ------   -------
!    4  Starting notify domain .pko-24 entity list=(node4 bbpk99 circuit * 
!                adjacent node *),events=(adjacency down)
!
!
!%MCC-E-NOTIFEXCP, notify request 4 encountered an exception
!No entities in this domain support the requested events.
!
!%MCC-W-NOTIFABORT, notify request 4 aborted due to error condition
!
use log off
!

When I try to set this up via IMPM I get the same message. I don't think I 
have a syntax problem but I'll try anything at this point.

Please note I am using an AM installed by Jean just to get the events in.

time is short....help...
brad...

    retry the notify with events = (any configuration event)
    
    I just check the events, and they have some non unique event names
    that will cause parsing problems in the notify. This may also
    be effecting alarms, depending upon how they did their parsing.
    
    I will look into the parse problem.

Hi Jill, thanks for the pointer;

And the results are:

1. The notify request from fcl for "any configuration event" worked and I
   got the adjacency event when received. The disturbing part is that I
   receive no notification in IMPM. Is this by design??? The impact is that
   I can't put NOTIFY requests in batch (also I couldn't figure out a syntax
   for SEVERITY from fcl, if there is one).

2. I then set up the same NOTIFY from IMPM using "any configuration event" and
   I do receive the event and a color change for an adjacency event. So your
   thoughts of a parsing problem could be true when submitting the request.

3. I then set up an ASSIGN TARGET from fcl to indicate the node troubled. I
   used the symbol substitution and it worked!! But...I noticed the color
   for both icons (sender of event and receiver of target) was the same
   because I hadn't defined a severity in the ASSIGN command. So I went back
   to DEASSIGN the target and reASSIGN it and I couldn't deassign. From IMPM
   I got 'internal error in IMPM' and from fcl it says 'normal successful
   completion' but the assignment doesn't go away!

4. If I can't put the notify commands in batch I'd like to try TARGETs from
   the ALARMS FM. The docs indicate (here and there) it is supported but I
   couldn't figure out the syntax. Is it supported and does it have the same
   type of symbols support??? Syntax???


kind regards,
brad...

    I recently found a deassignment error (in the code) when attempting
    to deassign a target on a child entity (like adjacent node). I have
    fixed and tested this, it should hopefully make the next kit we
    release.
    
    jill