Conference help::decnet-osi_for_vms

3899.0. "outbound IP cluster alias address ??" by MEO78A::BARNHOORN (Barney to his friends) Wed Mar 12 1997 01:29

  How does the outbound cluster alias work in a DECnet/OSI (using TCP/IP as
the transport layer) network?

  The customer I'm working with is migrating/upgrading to DECnet/OSI (6.3) and
using TCP/IP as the transport layer. He will have a IP only backbone, so
DECnet/OSI with TCP is the solution.

  The nodes/systems we have upgraded have not been using the (outbound) cluster
alias as yet. Shortly we will be upgrading the Teamlinks/MessageRouter clusters
and message router has been configure to use the Cluster Alias.


Example
    Current Config

    HOSA  (1.70) Cluster Alias                 MEBA  (62.2)  Alais
     HOSN01  (1.71) member                      MEBO01 (62.3) Member
     HOSN02  (1.72) member                      MEBO02 (62.4) Member
          *                                       *
          ***************DECnet Link/Path**********


    Message Router, Transfer service and DDS, send out all connections using
the cluster alias.  
    
    In the current configuration, using DECnet routers, everything works.

(we do have tcp/ip configured but only using the LOCAL naming option, so all
traffic still uses the decnet IV path, but we can do $set h IP address, 
$dir ipaddress:: and that works fine) 

Soon the config will be

    HOSA  (1.70) Cluster Alias                 MEBA  (62.2)  Alais
     HOSN01  (1.71) member                      MEBO01 (62.3) Member
     HOSN02  (1.72) member                      MEBO02 (62.4) Member
      192.168.1.10 HOSA (Cluster addr)           192.168.5.10 MEBA
      192.168.1.11  HOSN01 member                192.168.5.11  MEBO01
      192.168.1.12  HOSN02 member                192.168.5.12  MEBO02
          %                                       %
          %%%%%%%%%%%%%%%TCP/IP Link/Path%%%%%%%%%%


   The question I/customer have is how do I configure message router, fal etc
to use the "clusters" IP address in the outbond connections?

doing a 

NCL>show address

Node 0
at 1997-03-12-17:08:05.490+11:00Iinf

Identifiers

    Address                           =
       {
          (
          [ DNA_CMIP-MICE ] ,
          [ DNA_SessionControlV3 , number = 19 ] ,
          [ DNA_OSItransportV1 , 'DEC0'H ] ,
          [ DNA_OSInetwork , 49::00-01:AA-00-04-00-47-04:21 (LOCAL:.HOSN01) ]
          ) ,
          (
          [ DNA_CMIP-MICE ] ,
          [ DNA_SessionControlV3 , number = 19 ] ,
          [ DNA_OSItransportV1 , 'DEC0'H ] ,
          [ DNA_OSInetwork , 49::00-01:AA-00-04-00-46-04:21 (LOCAL:.HOSA) ]
          ) ,
          (
          [ DNA_CMIP-MICE ] ,
          [ DNA_SessionControlV2 , number = 19 ] ,
          [ DNA_OSItransportV1 , 'DEC0'H ] ,
          [ DNA_IP , 192.168.1.11 ]
          ) ,
          (
          [ DNA_CMIP-MICE ] ,
          [ DNA_SessionControlV3 , number = 19 ] ,
          [ DNA_NSP ] ,
          [ DNA_OSInetwork , 49::00-01:AA-00-04-00-47-04:20 (LOCAL:.HOSN01) ]
          ) ,
          (
          [ DNA_CMIP-MICE ] ,
          [ DNA_SessionControlV3 , number = 19 ] ,
          [ DNA_NSP ] ,
          [ DNA_OSInetwork , 49::00-01:AA-00-04-00-46-04:20 (LOCAL:.HOSA) ]
          )
       }

NCL>
 

Displays the DECnet Phase IV and DECnet/OSI node and cluster address but only
the node's ip address not the clusters address.



   Has anyone else seen this problem or make comments?


   Thanks

	Mark.



PS the HOSA cluster is using UCX (4.0), the MEBA cluster is using TGV 4.0.


    



  

Mark,

Outbound Cluster Alias does not work (and as far as I know it was never
intended to work) when the "network" layer is provided by TCP/IP.

If you were running UCX and using TELNET then outbound IP Cluster Alias
would not work ... It's the same idea!

Regards,

	John