multiple sites

[Tom Mitchell <tmitchel@VAX.BBN.COM>]

The mailer bounced this message, so I'll send it to slug and you'll
get it that way.  Hope it's useful for someone else too.

-tom
  
	  Date: Tue, 28 Nov 89 17:51:11 CST
	  From: "BUCKMAN%ALAN.LAAC-AI.Dialnet.Symbolics.COM %ALAN.kahuna.DECNET.LOCKHEED.COM"@warbucks.ai.sri.com
  
      Eric,
  
	This is the original message from Shirley Kao.  I found it helped quite
      a bit, and as you can see, it is much more detailed than Steve Saeedi's
      instructions.  Again, if you have more questions, let me know.
  
      -tom
  
      p.s.  Shirley left out the internet network needing the global
      network name be the same.  This caused some me some trouble, so
      don't forget it if you use IP-TCP.
  
      Date: Thu, 23 Feb 89 06:35 PST
      From: kao@vermithrax.sch.symbolics.com
      Subject: Letting two sites talking to each other procedur 
      To: Tmitchell%bbn.com@stony-brook.scrc.symbolics.com
  
      Let's say you have two physically different sites and two seperate
      namespaces and two namespace server machines. 
  
	Site-1 has a namespace server called Machine-1, subnet 1
	Site-2 has a namespace server called Machine-2, subnet 2
  
      1.  Boot a configured world on machine-1 and machine-2.
  
      2.  On machine-2 do (NETI:FIND-SITE :site-1)
  
      3.  Edit and save the namespace on machine-2 with the following changes.
  
	    If you have secure subnets then edit Site object Site-2
		     -  edit the secure subnets field with network CHAOS
			and	subnets 1 and 2.
  
	    NAMESPACE Namespace object for Site-2
		     -  edit the Search Rules field and add Site-1 add a
			secondary server of Site-1|Machine-1 
  
		    The NAMESPACE object should look like this
  
			    NAMESPACE SITE-2
			    DESCRIPTOR-FILE Machine-2:>sys>site>site-2-namespace.text.newest
			    SEARCH-RULES SITE-2 SITE-1
			    SECONDARY-NAME-SERVER SITE-1|Machine-1
			    PRIMARY-NAME-SERVER Machine-2
  
	    Network object Chaos - add a global network name that will common to 
		    both sites.  THIS IS ESSENTIAL...THE MACHINES WILL NOT TALK IF YOU LEAVE OUT THIS STEP.
  
		    The Network object Chaos should look something like this.
			    NETWORK CHAOS
			    GLOBAL-NETWORK-NAME SHARED
			    TYPE CHAOS
			    SITE SITE-2
  
      4.  Reboot Machine-2 with a distribution world.
      [This could be a recent site-set world but a distribution world is a bit
      safer.]
  
      5.  On Machine-2 do (neti:find-site :site-1)
  
      6.  On Machine-2 Set Site Site-2.  IF YOU ATTEMPT TO SET SITE BEFORE DOING THE FIND SITE,
	  YOU GET ERRORS WHEN IT READS THE SEARCH RULES AND SEES SITE-1.
  
      7.  Save the world on Machine-2.
  
      8.  Go to Machine-1 and do a (neti:find-site :site-2)
  
      9.  Edit and save the namespace on machine-2 with the following changes.
  
	    If you have secure subnets then edit Site object Site-1
		     -  edit the secure subnets field with network CHAOS
			and	subnets 1 and 2.
  
	    NAMESPACE Namespace object for Site-1
		     -  edit the Search Rules field and add Site-2 add a
			secondary server of Site-2|Machine-2 
  
		    The NAMESPACE object should look like this
  
			    NAMESPACE SITE-1
			    DESCRIPTOR-FILE Machine-1:>sys>site>site-1-namespace.text.newest
			    SEARCH-RULES SITE-1 SITE-2
			    SECONDARY-NAME-SERVER SITE-2|Machine-2
			    PRIMARY-NAME-SERVER Machine-1
  
	    Network object Chaos - add a global network name that will common to 
		    both sites.  THIS IS ESSENTIAL...THE MACHINES WILL NOT TALK IF YOU LEAVE OUT THIS STEP.
  
		    The Network object Chaos should look something like this.
			    NETWORK CHAOS
			    GLOBAL-NETWORK-NAME SHARED
			    TYPE CHAOS
			    SITE SITE-1
  
      10.  Reboot Machine-1 with a distribution world.
  
      11.  On Machine-1 do a (neti:find-site :site-2)
  
      12.  On Machine-1 Set Site site-1.
  
      13.  Save the world on Machine-1.