[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1643.0. "Change in node name vs. PARTITION" by GLOVES::ALLERTON (Steve Allerton 343-0205) Wed Oct 21 1992 21:30

    If a node on which ALL-IN-1 is installed has both DECNET node name and 
    address changed, what steps should be taken to update the partition?
    
    (i.e.  PARTITION name is the old decnet node name)
    
    Thanks,
    
    Steve
T.RTitleUserPersonal
Name		DateLines
1643.1None in PARTITIONIOSG::TALLETTGimmee an Alpha colour notebook...Thu Oct 22 1992 08:5915
    
    	If you're only interested in PARTITION, then I don't think there
    	is any change. The node name/address doesn't appear in PARTITION.
    
    	Of course, there are plenty of other related things to keep
    	you busy, I can think of a few:
    
    	- Remote FILECAB.DAT's pointing to shared drawers on this
    	  node (local pointers are okay, they have 0:: in them)
    	- Server system management, need to delete existing and
    	  add a new server probably on a new queue
    	- Probably a few more, but I got you started...
    
    Regards,
    Paul
1643.2Not a trivial thingCHRLIE::HUSTONThu Oct 22 1992 14:5842
    
    This is a very big problem that will take quite awhile to fix in all
    the correct places.
    
    First off, the server itself needs to be restarted since it caches
    things like the node name at startup.
    
    Then there are the things Paul mentioned in .1.
    
    Filecab.dat's are going to be the problem.  Local filecab's (those that
    physically exist on teh changed node) will nto be a problem. The 
    problem will be the other filecabs throughout the network, these could
    contain drawers that are physically located on your system, there is
    no way for the server (or IOS) to know what filecab's in the world
    point to a system. 
    
    In a small network this will be a manual, but doable task. You simply
    tell all users that if they have a drawer in their FC that is located
    on teh changed node that they need to remove it and re-add it with 
    the new name.
    
    On a large net, such as DECs, this would be a task of almost impossible
    magnitude. 
    
    Signs will show up as the node name/id are propagated through the net
    work. When a user goes to reference the drawer by teh old name, the
    FCS will attempt a connection based on the old name. Chances are that
    it won't exist in the node database and the user will be nicely told
    that there is an undefined node. A mis-leading problem could occur
    if another node with the same name is latter defined in the net, before
    a FC is updated. Then the FCS will happily attempt to talk to the FCs
    on the "new node" and the returned answer will be 1 of several things:
    
    	- server not available
    	- drawer does not exist
    	- if you are unluck enough you will get to a system that has a
          drawer with the same name, then what you get as an answer would
          be based on teh security on the drawer (anything from an error 
          about you not having access to all the info you want).
    
    --Bob