Conference azur::mcc

4256.0. "DECmcc and DECatg inter-operatability ???" by USOPS::HARB () Tue Dec 15 1992 15:30

    We're attempting to connect an external network, a customer's network,
    to digital's Easynet so that the external network can me monitored and
    managed from the Easynet.  Our strategy is to use DEC Address 
    Translation Gateway (ATG) to resolve DECnet addressing conflicts and use DEC
    SecurityGate (DSG) to provide a secure connection.
    
    The connection has worked successfully and we are able to route DECnet
    traffic from one network to the other; however, I have come upon a
    problem.  It seems DECmcc does not like this strategy.
    
    If a try to manage the node4 entity, DECmcc successfully establishes a
    logical link with the node4 and querries it.  Unfortunately, the data
    returned includes the ACTUAL address of the node which is different
    from the TRANSLATED address.  DECmcc, at this point, assumes that you
    are managing a cluster alias and instructs you to specify a cluster
    member.  It goes so far as to even give you the address of the cluster
    member it just accessed:  The ACTUAL address of the registered entity.
    
    I realize this is not a limitation of DECmcc, but I was wondering if
    anyone has ever experienced this situation and if there a work-around.
    
    
    Thanks,
    
    George