With AFS 3.4 you don't need to run "vos changeaddr".
You may find on:
http://www.transarc.com/afs/transarc.com/public/www/Public/Support/afs/admin/change_ip.html
the following info:
Changing the IP Address of an AFS Server or Client
To change the IP address of a file server machine that is not a database
server machine, and is running AFS 3.3 or higher:
1. Change the IP address.
NOTE: if while changing the IP address, you also change the *name* of
the system control machine (SCM) or a binary distribution machine
(BDM), remember to change the upclientetc and upclientbin instances on
other file server machines that point to that SCM or BDM.
2. Issue the "vos changeaddr" command, which is documented on page 41 of
the AFS 3.3 Release Notes (document number FS-D200-00.04.12). This
changes the VLDB and volume headers as necessary.
NOTE: not necessary with AFS 3.4, which registers all of a file server
machine's addresses in the VLDB as part of its support for multihoming.
3. It may be necessary to use "fs checkvolumes" on all clients to force
them to recognize the new name-to-location mapping. These mappings are
updated automatically within 2 hours even if "fs checkvolumes" is not
issued.
4. If you've defined any Protection Database IP-groups to include the
machine under its old address, you must change them manually.
To change the IP address of a database server machine running AFS 3.3 or
higher:
1. Modify /usr/afs/etc/CellServDB on every file server machine to reflect
the machine's new IP address. Customers using the United States edition
of AFS can make the change on the system control machine, and wait 5
minutes for the upserver to propagate it. International customers must
make the change by hand on each machine.
2. Use "bos shutdown" on all server processes on the machine. If the
machine is also a fileserver, volumes will be inaccessible for a while.
3. Change the IP address.
4. Use "bos restart" on the server processes on the machine. At the same
time, issue "bos restart" on the database server processes
(Authentication Server, Backup Server, Protection Server and VL Server)
on all other database server machines. Issue the commands in quick
succession so that all servers vote in the quorum election.
5. Restart the fs process on each of your cell's machines at some point,
to redistribute connections across all database server machines. You've
already done this on the machine whose address is changing.
NOTE: If you're changing the IP addresses of ALL database server
machines, then you must restart the fs process on all file server
machines to resume normal operations of your cell.
6. Issue the "vos changeaddr" command, which is documented on page 41 of
the AFS 3.3a Release Notes (document number FS-D200-00.04.12). This
changes the VLDB and volume headers as necessary.
NOTE: not necessary with AFS 3.4, which registers all of a file server
machine's addresses in the VLDB as part of its support for multihoming.
7. On all client machines, change /usr/vice/etc/CellServDB. Then either
run "fs newcell -s +" or reboot the machine.
8. If you've defined any Protection Database IP-groups to include the
machine under its old address, you must change them manually.
To change the IP address of server machines running AFS 3.2b or earlier:
If the machine is a database server machine, follow steps 1 - 5 and 7 and 8
from the instructions above for AFS 3.3 database server machines. Then
follow the instructions just below, which apply to all file server machines.
For all types of file server machines:
1. Change the IP address, if you have not already.
2. Issue "vos syncvldb " to tell the VLDB that the volumes are at a
different IP address.
3. If the machine houses any ReadOnly volumes, use "vos remsite " to
remove those references and then "vos addsite to redefine them. Use
"vos listvldb -server " to find all the VLDB entries that mention the
old address.
4. When you're finished removing old sites, make sure that "vos listvldb
-server " shows no entries.
5. It may be necessary to use "fs checkvolumes" on all clients to force
them to recognize the new name-to-location mapping. These mappings are
updated automatically within 2 hours even if "fs checkvolumes" is not
issued.
To change the IP address of AFS client-only machines:
1. Change the IP address.
2. Reboot the machine. Restarting the Cache Manager in this way guarantees
that all callbacks held by file servers for the client's old address
will be broken.
As always, if you have questions or concerns about any of the information
you read, please don't hesitate to contact Product Support.
Copyright * Transarc Corporation 1997
Danilo Fossati - Tel. 8-6130 - Bldg. 13.1 - MIVIM222 - IBM Italia - Vimercate
Internet: [EMAIL PROTECTED]
---------------------- Forwarded by Danilo Fossati/Italy/IBM on 19/01/98 14:38
---------------------------
[EMAIL PROTECTED]
19/01/98 12:38
Please respond to [EMAIL PROTECTED] @ internet
To: [EMAIL PROTECTED] @ internet
cc: [EMAIL PROTECTED] @ internet
Subject: vos changeaddr, how to do ?
We need to change one file server's IP tomorrow. According to
the AFS 3.4a release notes, there is "vos changeaddr" command for this
purpose. I'm really positive to use this command, however, I want to
cross-check the usage of the command. Would you please check the following
procedure.
1. disable AFS file server process
2. change IP address of the server
3. vos changeaddr OLDIP NEWIP
4. enable AFS file server process
Is that all? Can I issue "vos changeaddr" command while the file
server processes are running?
Please comment this ASAP. Thanks in advance.
Sincerely,
Jay Kim
--
___________________________________________________________________________
_____ ___ __ __
__/\__ |_ _| / _ \ \ \_/ / Remember Yesterday, Dream about Tomorrow
\ / | | | /_\ | \ / but ... LIVE TODAY !!!
/_ _\ | | | _ | | |
\/ __| | | | | | | | [EMAIL PROTECTED] (Jae-young Kim)
|___/ |_| |_| |_| Researcher, Computer Center/POSTECH, KOREA
___________________________________________________________________________
Danilo Fossati - Tel. 8-6130 - Bldg. 13.1 - MIVIM222 - IBM Italia - Vimercate
Internet: [EMAIL PROTECTED]
