Ref: 09930017
Title: Replacing 3+Name Server Without Changing Ethernet Chips
date: 9/28/90

Copyright 3Com Corporation, 1991.  All rights reserved.

Suppose the Name server on a 3+ LAN develops a disk or a motherboard
problem and crashes.  There is an extra server on site that can be used as
a replacement.  The network administrator is not capable of replacing the
failed component, but is able to swap the Name server with the replacement
server.

The following procedure explains how to bring the replacement server on line
as the Name server without swapping the Ethernet chips.  The procedure assumes
that both 3Servers have backup units and are at 3+ version 1.3.1 or later.

NOTE:  This procedure has not been subjected to exhaustive testing and
may not, in all circumstances, provide a complete solution.

1.  Make sure you have a full backup of the original 3+Name server.

2.  Swap the servers.

3.  Boot the replacement server in console mode and establish
a console connection using the 3C program.  (Refer to the server guide
for instructions on making a console connection.)

4.  From the original 3+Name server's backup tape, restore the server tape to
the replacement server using 3BMENDOS for the off-line restore of the Name
server tape.  (Refer to the 3+ Administrator's Guide, volume 1, for
instructions on performing an off-line restore.)

5.  Using a text editor, change the name in the file C:\3PLUS\S_NAME to a
temporary name such as temp:original domain:original organization.  For
example, Server1:HQOPS:3Com to Temp:HQOPS:3Com.

6.  Reboot the server in server mode.

7.  Log in as Admin and use 3N to delete both the original and temporary
server entries in the name service:

     3N DEL SERVER [server name]

8.  Reboot the server in console mode and establish a console connection
using the 3C program.

9.  Change the name in the file C:\3PLUS\S_NAME to the original name of
the Name server; for example, Temp:HQOPS:3Com to Server1:HQOPS:3Com.

10. Reboot the server in server mode.

The name server is back on-line with a different Ethernet address
and no changes have to be made to the Shrlist or the NS_DOM files.
