Conference azur::mcc

    There are several solutions on this question.
    
    You may draw your circuit as 2 lines, one from router A, one from
    routerB putting their child entities as
    ROUTING CIRCUIT XXX or HDLC LINK XXX STATION yyy visible as lines on
    the map.  If these child entities get events, the line on the map
    will change color automatically.
    
    Another way is to create alarm rules for these child entities, and
    execute a mcc_evc_send to a collector of the domain, retargetting
    the event to the circuit connecting the two endpoints.
    
    If that's not good enough, you may want to solve the question writing a
    special access module which does the work of remapping events.
    
    I wrote one like this, works quite well today, but it will take at least 3
    more months before I will put this in production in our network.
    The AM is developed on ULTRIX today. If there is enough interest I
    could make an ASSET out of it.
    
    
    	Regards,
    	Dominique.

    
    	Hye Dominique,
    
    	Thanks a lot for your so fast answer.
    
    	I tried to create a circuit like the documentation said.
    
    	But the examples speak about Phase IV Nodes, and 
    	
    	Phase V Nodes like our DECnis seems to be not so easy.
    
    
    	So these is what I've done :
    
    	1/ Opened the Toolbox
    	2/ Selected Circuit  and gave it the name EVT-BPS
    	3/ Took the line Icon
        4/ Draw the line between the both DECnis
    	5/ Selected the line and used set characteristics
    
    	I entered the following informations:
    
    	aEndpoint Instance = LOCAL_NS:.EVTNIS routing circuit EVT-BPS
    		  objectid = %303030
    		  objectname = .AREA52:.EVT-BPS
    
    		  The bandwith ha been set at 64 K
    
    	I have a validation error when I try to start .
    
    	The router name is EVTNIS        
    	The circuit name is EVT-BPS
    	
    
    	What do you think about .
    
    	Thanks for your help.
    
    	Patrick
    
    
    	PS: DECmcc V1.4 VAX VMS 6.1
    	
    
    	

    Patrick,
    
    At the first glance I see 1 error:
    
      aEndpoint Instance = node LOCAL_NS:.EVTNIS routing circuit EVT-BPS 
    			   ^^^^
    
    Note that creating a circuit will not as such allow events of the
    endpoints be directed to the circuit.
    Also if you use the data collector, you do not have to give any
    attribute to the circuit, although giving attributes only better
    describe the entity instance.
    
    Kind regards,
    	Dominique.
    

    Patrick,
    
    There are a couple of ways of putting lines on the map. One is to use
    the CIRCUIT entity drawn as a line. The other is to put on the map the
    SUB-entity of your node drawn as a line. We use to use the second
    method because it allowed color change directly from alarms or events
    with simple notify commands (it just seemed a LOT easier). I don't 
    remember all the specifics on how to do this and I no longer have a 
    station to work with. But if I remember right you have to navigate into
    the node down to the actual circuit entity by double-clicking, THEN
    open the toolbox (even if it is already open). This brings up a
    different toolset allowing you to add a line as the actual circuit
    sub-entity. Sorry I don't remember the details, it has been a couple of
    years since I have worked with the product. But I think this is what
    Dominique was refering to in the initial reply.
    
    hope this helps,
    brad...(who has come home again to DEC)