1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Installing Additional Server Machines</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE="AFS Quick Beginnings"
11 HREF="book1.html"><LINK
13 TITLE="Installing the First AFS Machine"
14 HREF="c371.html"><LINK
16 TITLE="Installing Additional Client Machines"
17 HREF="c8044.html"></HEAD
28 SUMMARY="Header navigation table"
37 >AFS Quick Beginnings: Version 3.6</TH
74 >Chapter 3. Installing Additional Server Machines</H1
76 >Instructions for the following procedures appear in the indicated section of this chapter. <UL
80 HREF="c5467.html#HDRWQ100"
81 >Installing an Additional File Server Machine</A
87 HREF="c5467.html#HDRWQ114"
88 >Installing Database Server Functionality</A
94 HREF="c5467.html#HDRWQ125"
95 >Removing Database Server Functionality</A
101 >The instructions make the following assumptions. <UL
104 >You have already installed your cell's first file server machine by following the instructions in <A
106 >Installing the First AFS Machine</A
111 >You are logged in as the local superuser <SPAN
121 >You are working at the console</P
125 >A standard version of one of the operating systems supported by the current version of AFS is running on the
130 >You can access the data on the AFS CD-ROMs, either through a local CD-ROM drive or via an NFS mount of a CD-ROM drive
131 attached to a machine that is accessible by network</P
141 >Installing an Additional File Server Machine</A
144 >The procedure for installing a new file server machine is similar to installing the first file server machine in your
145 cell. There are a few parts of the installation that differ depending on whether the machine is the same AFS system type as an
146 existing file server machine or is the first file server machine of its system type in your cell. The differences mostly concern
147 the source for the needed binaries and files, and what portions of the Update Server you install: <UL
150 >On a new system type, you must load files and binaries from the AFS CD-ROM. You install the server portion of the
151 Update Server to make this machine the binary distribution machine for its system type.</P
155 >On an existing system type, you can copy files and binaries from a previously installed file server machine, rather
156 than from the CD-ROM. You install the client portion of the Update Server to accept updates of binaries, because a
157 previously installed machine of this type was installed as the binary distribution machine.</P
162 >These instructions are brief; for more detailed information, refer to the corresponding steps in <A
164 >Installing the First AFS Machine</A
167 >To install a new file server machine, perform the following procedures: <OL
171 >Copy needed binaries and files onto this machine's local disk</P
175 >Incorporate AFS modifications into the kernel</P
179 >Configure partitions for storing volumes</P
183 >Replace the standard <SPAN
189 > utility with the AFS-modified version on some system
194 >Start the Basic OverSeer (BOS) Server</P
198 >Start the appropriate portion of the Update Server</P
208 > process, which incorporates three component processes: the File
209 Server, Volume Server, and Salvager</P
213 >Start the controller process (called <SPAN
219 >) for the Network Time Protocol Daemon,
220 which synchronizes clocks</P
225 >After completing the instructions in this section, you can install database server functionality on the machine according
226 to the instructions in <A
227 HREF="c5467.html#HDRWQ114"
228 >Installing Database Server Functionality</A
236 >Creating AFS Directories and Performing Platform-Specific Procedures</A
252 the local disk. Subsequent instructions copy files from the AFS distribution CD-ROM into them, at the appropriate point for
255 CLASS="programlisting"
267 >mkdir /usr/afs/bin</B
281 >mkdir /usr/vice/etc</B
293 >As on the first file server machine, the initial procedures in installing an additional file server machine vary a good
294 deal from platform to platform. For convenience, the following sections group together all of the procedures for a system
295 type. Most of the remaining procedures are the same on every system type, but differences are noted as appropriate. The
296 initial procedures are the following. <UL
299 >Incorporate AFS modifications into the kernel, either by using a dynamic kernel loader program or by building a
304 >Configure server partitions to house AFS volumes</P
308 >Replace the operating system vendor's <SPAN
314 > program with a version that recognizes
319 >If the machine is to remain an AFS client machine, modify the machine's authentication system so that users obtain
320 an AFS token as they log into the local file system. (For this procedure only, the instructions direct you to the
321 platform-specific section in <A
323 >Installing the First AFS Machine</A
329 >To continue, proceed to the section for this system type: <UL
333 HREF="c5467.html#HDRWQ101"
334 >Getting Started on AIX Systems</A
340 HREF="c5467.html#HDRWQ102"
341 >Getting Started on Digital UNIX Systems</A
347 HREF="c5467.html#HDRWQ103"
348 >Getting Started on HP-UX Systems</A
354 HREF="c5467.html#HDRWQ104"
355 >Getting Started on IRIX Systems</A
361 HREF="c5467.html#HDRWQ106"
362 >Getting Started on Linux Systems</A
368 HREF="c5467.html#HDRWQ107"
369 >Getting Started on Solaris Systems</A
380 >Getting Started on AIX Systems</A
383 >Begin by running the AFS initialization script to call the AIX kernel extension facility, which dynamically loads AFS
384 modifications into the kernel. Then configure partitions and replace the AIX <SPAN
391 with a version that correctly handles AFS volumes. <OL
395 >Mount the AFS CD-ROM for AIX on the local <SPAN
401 > directory. For instructions on
402 mounting CD-ROMs (either locally or remotely via NFS), see your AIX documentation. Then change directory as indicated.
404 CLASS="programlisting"
409 >cd /cdrom/rs_aix42/root.client/usr/vice/etc</B
417 >Copy the AFS kernel library files to the local <SPAN
421 >/usr/vice/etc/dkload</B
424 and the AFS initialization script to the <SPAN
431 CLASS="programlisting"
436 >cp -rp dkload /usr/vice/etc</B
443 >cp -p rc.afs /etc/rc.afs</B
457 > script, setting the <SAMP
458 CLASS="computeroutput"
461 variable as indicated.</P
463 >If the machine is not to function as an NFS/AFS Translator, set the <SAMP
464 CLASS="computeroutput"
467 variable as follows.</P
469 CLASS="programlisting"
473 >If the machine is to function as an NFS/AFS Translator and is running AIX 4.2.1 or higher, set the
475 CLASS="computeroutput"
477 > variable as follows. Note that NFS must already be loaded into the kernel, which
478 happens automatically on systems running AIX 4.1.1 and later, as long as the file <SPAN
486 CLASS="programlisting"
487 > NFS=$NFS_IAUTH
498 > script to load AFS modifications into the kernel. You
499 can ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS client.
501 CLASS="programlisting"
514 >Create a directory called <SPAN
524 server partition you are configuring (there must be at least one). Repeat the command for each partition.
526 CLASS="programlisting"
548 > program to create a journaling file system on each partition to be
549 configured as an AFS server partition.</P
553 >Mount each partition at one of the <SPAN
563 directories. Choose one of the following three methods: <UL
582 > command to mount all partitions at once</P
592 > command on each partition in turn</P
597 >Also configure the partitions so that they are mounted automatically at each reboot. For more information, refer
598 to the AIX documentation. </P
608 > program helper to a safe location and install the version
609 from the AFS distribution in its place. The AFS CD-ROM must still be mounted at the <SPAN
616 CLASS="programlisting"
628 >mv v3fshelper v3fshelper.noafs</B
635 >cp -p /cdrom/rs_aix42/root.server/etc/v3fshelper v3fshelper</B
643 >If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
645 HREF="c371.html#HDRWQ25"
646 >Enabling AFS Login on AIX Systems</A
652 HREF="c5467.html#HDRWQ108"
653 >Starting Server Programs</A
665 >Getting Started on Digital UNIX Systems</A
668 >Begin by building AFS modifications into the kernel, then configure server partitions and replace the Digital UNIX
675 > program with a version that correctly handles AFS volumes.</P
677 >If the machine's hardware and software configuration exactly matches another Digital UNIX machine on which AFS is
678 already built into the kernel, you can copy the kernel from that machine to this one. In general, however, it is better to
679 build AFS modifications into the kernel on each machine according to the following instructions. <OL
683 >Create a copy called <SPAN
689 > of the basic kernel configuration file included in the
690 Digital UNIX distribution as <SPAN
703 > is the machine's hostname in all uppercase letters. <PRE
704 CLASS="programlisting"
733 >Add AFS to the list of options in the configuration file you created in the previous step, so that the result
734 looks like the following: <PRE
735 CLASS="programlisting"
748 >Add an entry for AFS to two places in the file <SPAN
752 >/usr/sys/conf/files</B
758 >Add a line for AFS to the list of <SAMP
759 CLASS="computeroutput"
761 >, so that the result looks like
763 CLASS="programlisting"
766 OPTIONS/nfs optional nfs
767 OPTIONS/afs optional afs
768 OPTIONS/nfs_server optional nfs_server
776 >Add an entry for AFS to the list of <SAMP
777 CLASS="computeroutput"
779 >, so that the result looks
780 like the following: <PRE
781 CLASS="programlisting"
785 MODULE/nfs_server optional nfs_server Binary
786 nfs/nfs_server.c module nfs_server optimize -g3
787 nfs/nfs3_server.c module nfs_server optimize -g3
789 MODULE/afs optional afs Binary
790 afs/libafs.c module afs
800 >Add an entry for AFS to two places in the file <SPAN
804 >/usr/sys/vfs/vfs_conf.c</B
810 >Add AFS to the list of defined file systems, so that the result looks like the following: <PRE
811 CLASS="programlisting"
814 #include <afs.h>
815 #if defined(AFS) && AFS
816 extern struct vfsops afs_vfsops;
825 >Put a declaration for AFS in the <SPAN
831 > table's MOUNT_ADDON slot, so
832 that the result looks like the following: <PRE
833 CLASS="programlisting"
836 &fdfs_vfsops, "fdfs", /* 12 = MOUNT_FDFS */
838 &afs_vfsops, "afs",
840 (struct vfsops *)0, "", /* 13 = MOUNT_ADDON */
842 #if NFS && INFS_DYNAMIC
843 &nfs3_vfsops, "nfsv3", /* 14 = MOUNT_NFS3 */
852 >Mount the AFS CD-ROM for Digital UNIX on the local <SPAN
859 instructions on mounting CD-ROMs (either locally or remotely via NFS), see your Digital UNIX documentation. Then
860 change directory as indicated. <PRE
861 CLASS="programlisting"
866 >cd /cdrom/alpha_dux40/root.client</B
874 >Copy the AFS initialization script to the local directory for initialization files (by convention, <SPAN
880 > on Digital UNIX machines). Note the removal of the <SPAN
886 > extension as you copy the script. <PRE
887 CLASS="programlisting"
892 >cp usr/vice/etc/afs.rc /sbin/init.d/afs</B
900 >Copy the AFS kernel module to the local <SPAN
908 >If the machine's kernel supports NFS server functionality:</P
910 CLASS="programlisting"
915 >cp bin/libafs.o /usr/sys/BINARY/afs.mod</B
920 >If the machine's kernel does not support NFS server functionality:</P
922 CLASS="programlisting"
927 >cp bin/libafs.nonfs.o /usr/sys/BINARY/afs.mod</B
934 >Configure and build the kernel. Respond to any prompts by pressing <<SPAN
940 >>. The resulting kernel resides in the file <SPAN
947 CLASS="programlisting"
960 >Rename the existing kernel file and copy the new, AFS-modified file to the standard location. <PRE
961 CLASS="programlisting"
966 >mv /vmunix /vmunix_noafs</B
973 >cp /sys/AFS/vmunix /vmunix</B
981 >Reboot the machine to start using the new kernel, and login again as the superuser <SPAN
988 CLASS="programlisting"
1019 >Create a directory called <SPAN
1029 server partition you are configuring (there must be at least one). Repeat the command for each partition.
1031 CLASS="programlisting"
1047 >Add a line with the following format to the file systems registry file, <SPAN
1053 >, for each directory just created. The entry maps the directory name to the disk
1054 partition to be mounted on it. <PRE
1055 CLASS="programlisting"
1066 >The following is an example for the first partition being configured.</P
1068 CLASS="programlisting"
1069 > /dev/rz3a /vicepa ufs rw 0 2
1074 >Create a file system on each partition that is to be mounted at a <SPAN
1083 > directory. The following command is probably appropriate,
1084 but consult the Digital UNIX documentation for more information. <PRE
1085 CLASS="programlisting"
1101 >Mount each partition by issuing either the <SPAN
1107 > command to mount all
1108 partitions at once or the <SPAN
1114 > command to mount each partition in turn. </P
1124 > binary to the <SPAN
1137 > directories. The AFS CD-ROM must still be mounted at the <SPAN
1144 CLASS="programlisting"
1149 >cd /cdrom/alpha_dux40/root.server/etc</B
1156 >cp vfsck /sbin/vfsck</B
1163 >cp vfsck /usr/sbin/vfsck</B
1171 >Rename the Digital UNIX <SPAN
1177 > binaries and create symbolic links to the
1185 CLASS="programlisting"
1197 >mv ufs_fsck ufs_fsck.noafs</B
1204 >ln -s vfsck ufs_fsck</B
1218 >mv ufs_fsck ufs_fsck.noafs</B
1225 >ln -s vfsck ufs_fsck</B
1233 >If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
1235 HREF="c371.html#HDRWQ30"
1236 >Enabling AFS Login on Digital UNIX Systems</A
1242 HREF="c5467.html#HDRWQ108"
1243 >Starting Server Programs</A
1255 >Getting Started on HP-UX Systems</A
1258 >Begin by building AFS modifications into the kernel, then configure server partitions and replace the HP-UX <SPAN
1264 > program with a version that correctly handles AFS volumes.</P
1266 >If the machine's hardware and software configuration exactly matches another HP-UX machine on which AFS is already
1267 built into the kernel, you can copy the kernel from that machine to this one. In general, however, it is better to build AFS
1268 modifications into the kernel on each machine according to the following instructions. <OL
1272 >Move the existing kernel-related files to a safe location. <PRE
1273 CLASS="programlisting"
1278 >cp /stand/vmunix /stand/vmunix.noafs</B
1285 >cp /stand/system /stand/system.noafs</B
1293 >Mount the AFS CD-ROM for HP-UX on the local <SPAN
1299 > directory. For instructions
1300 on mounting CD-ROMs (either locally or remotely via NFS), see your HP-UX documentation. Then change directory as
1302 CLASS="programlisting"
1307 >cd /cdrom/hp_ux110/root.client</B
1315 >Copy the AFS initialization file to the local directory for initialization files (by convention, <SPAN
1321 > on HP-UX machines). Note the removal of the <SPAN
1328 extension as you copy the file. <PRE
1329 CLASS="programlisting"
1334 >cp usr/vice/etc/afs.rc /sbin/init.d/afs</B
1342 >Copy the file <SPAN
1348 > to the local <SPAN
1352 >/usr/conf/master.d</B
1354 > directory, changing its name to <SPAN
1362 CLASS="programlisting"
1367 >cp usr/vice/etc/afs.driver /usr/conf/master.d/afs</B
1375 >Copy the AFS kernel module to the local <SPAN
1383 >If the machine's kernel supports NFS server functionality:</P
1385 CLASS="programlisting"
1390 >cp bin/libafs.a /usr/conf/lib</B
1395 >If the machine's kernel does not support NFS server functionality, change the file's name as you copy it:</P
1397 CLASS="programlisting"
1402 >cp bin/libafs.nonfs.a /usr/conf/lib/libafs.a</B
1409 >Incorporate the AFS driver into the kernel, either using the <SPAN
1416 series of individual commands. <UL
1435 > program, specifying the hostname of the local
1438 >local_hostname</VAR
1446 user interface pops up. <PRE
1447 CLASS="programlisting"
1456 >local_hostname</VAR
1473 >Kernel Configuration</B
1475 > icon, then the <SPAN
1481 > icon. From the list of drivers, select <SPAN
1491 >Open the pull-down <SPAN
1497 > menu and choose the <SPAN
1501 >Add Driver to Kernel</B
1513 > menu again and choose the <SPAN
1517 >Create a New Kernel</B
1523 >Confirm your choices by choosing <SPAN
1535 > when prompted by subsequent pop-up windows. The <SPAN
1541 > program builds the kernel and reboots the system.</P
1545 >Login again as the superuser <SPAN
1552 CLASS="programlisting"
1572 >To use individual commands: <OL
1576 >Edit the file <SPAN
1582 >, adding an entry for <SPAN
1589 CLASS="computeroutput"
1595 >Change to the <SPAN
1601 > directory and issue the <SPAN
1607 > command to build the kernel. <PRE
1608 CLASS="programlisting"
1628 >Move the new kernel to the standard location (<SPAN
1635 reboot the machine to start using it, and login again as the superuser <SPAN
1642 CLASS="programlisting"
1647 >mv /stand/build/vmunix_test /stand/vmunix</B
1686 >Create a directory called <SPAN
1696 server partition you are configuring (there must be at least one). Repeat the command for each partition.
1698 CLASS="programlisting"
1720 > program to create a file system on each partition. For
1721 instructions, consult the HP-UX documentation.</P
1725 >On some HP-UX systems that use logical volumes, the <SPAN
1731 > program automatically
1732 mounts the partitions. If it has not, mount each partition by issuing either the <SPAN
1739 > command to mount all partitions at once or the <SPAN
1746 each partition in turn. </P
1750 >Create the command configuration file <SPAN
1754 >/sbin/lib/mfsconfig.d/afs</B
1757 editor to place the indicated two lines in it: <PRE
1758 CLASS="programlisting"
1759 > format_revision 1
1760 fsck 0 m,P,p,d,f,b:c:y,n,Y,N,q,
1766 >Create and change directory to an AFS-specific command directory called <SPAN
1773 CLASS="programlisting"
1778 >mkdir /sbin/fs/afs</B
1793 >Copy the AFS-modified version of the <SPAN
1799 > program (the <SPAN
1805 > binary) and related files from the distribution directory to the new AFS-specific command
1807 CLASS="programlisting"
1812 >cp -p /cdrom/hp_ux110/root.server/etc/* .</B
1826 > binary's name to <SPAN
1833 the mode bits appropriately on all of the files in the <SPAN
1841 CLASS="programlisting"
1867 > file, changing the file system type for each AFS server
1868 partition from <SAMP
1869 CLASS="computeroutput"
1872 CLASS="computeroutput"
1874 >. This ensures that the
1881 > program runs on the appropriate partitions.</P
1883 >The sixth line in the following example of an edited file shows an AFS server partition, <SPAN
1891 CLASS="programlisting"
1892 > /dev/vg00/lvol1 / hfs defaults 0 1
1893 /dev/vg00/lvol4 /opt hfs defaults 0 2
1894 /dev/vg00/lvol5 /tmp hfs defaults 0 2
1895 /dev/vg00/lvol6 /usr hfs defaults 0 2
1896 /dev/vg00/lvol8 /var hfs defaults 0 2
1897 /dev/vg00/lvol9 /vicepa afs defaults 0 2
1898 /dev/vg00/lvol7 /usr/vice/cache hfs defaults 0 2
1903 >If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
1905 HREF="c371.html#HDRWQ35"
1906 >Enabling AFS Login on HP-UX Systems</A
1912 HREF="c5467.html#HDRWQ108"
1913 >Starting Server Programs</A
1925 >Getting Started on IRIX Systems</A
1928 >Begin by incorporating AFS modifications into the kernel. Either use the <SPAN
1935 loader program, or build a static kernel. Then configure partitions to house AFS volumes. AFS supports use of both EFS and
1936 XFS partitions for housing AFS volumes. SGI encourages use of XFS partitions. </P
1938 >You do not need to replace IRIX <SPAN
1944 > program, because the version that SGI
1945 distributes handles AFS volumes properly. <OL
1949 >Prepare for incorporating AFS into the kernel by performing the following procedures. <OL
1953 >Mount the AFS CD-ROM for IRIX on the <SPAN
1959 > directory. For instructions
1960 on mounting CD-ROMs (either locally or remotely via NFS), see your IRIX documentation. Then change directory as
1962 CLASS="programlisting"
1967 >cd /cdrom/sgi_65/root.client</B
1975 >Copy the AFS initialization script to the local directory for initialization files (by convention,
1982 > on IRIX machines). Note the removal of the <SPAN
1988 > extension as you copy the script. <PRE
1989 CLASS="programlisting"
1994 >cp -p usr/vice/etc/afs.rc /etc/init.d/afs</B
2008 > command to determine the machine's CPU board type. The
2018 > value in the output must match one of the
2019 supported CPU board types listed in the <SPAN
2023 >IBM AFS Release Notes</I
2025 > for the current version of
2027 CLASS="programlisting"
2043 >Incorporate AFS into the kernel, either using the <SPAN
2049 > program or by building AFS
2050 modifications into a static kernel. <UL
2063 >Create the local <SPAN
2067 >/usr/vice/etc/sgiload</B
2069 > directory to house the AFS
2070 kernel library file. <PRE
2071 CLASS="programlisting"
2076 >mkdir /usr/vice/etc/sgiload</B
2084 >Copy the appropriate AFS kernel library file to the <SPAN
2088 >/usr/vice/etc/sgiload</B
2090 > directory. The <SPAN
2099 > portion of the library file name must match the
2100 value previously returned by the <SPAN
2106 > command. Also choose the file
2107 appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for
2108 the machine to act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library
2111 >(You can choose to copy all of the kernel library files into the <SPAN
2115 >/usr/vice/etc/sgiload</B
2117 > directory, but they require a significant amount of
2120 >If the machine's kernel supports NFS server functionality:</P
2122 CLASS="programlisting"
2127 >cp -p usr/vice/etc/sgiload/libafs.IP</B
2136 >.o /usr/vice/etc/sgiload</B
2141 >If the machine's kernel does not support NFS server functionality:</P
2143 CLASS="programlisting"
2148 >cp -p usr/vice/etc/sgiload/libafs.IP</B
2164 >/usr/vice/etc/sgiload</B
2177 > command to activate the <SPAN
2183 > configuration variable. <PRE
2184 CLASS="programlisting"
2189 >/etc/chkconfig -f afsml on</B
2195 >If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server
2196 functionality, activate the <SPAN
2204 CLASS="programlisting"
2209 >/etc/chkconfig -f afsxnfs on</B
2222 > script to load AFS extensions into the
2223 kernel. The script invokes the <SPAN
2229 > command, automatically determining
2230 which kernel library file to use based on this machine's CPU type and the activation state of the
2239 >You can ignore any error messages about the inability to start the BOS Server or the Cache Manager
2242 CLASS="programlisting"
2247 >/etc/init.d/afs start</B
2255 HREF="c5467.html#LIWQ105"
2264 >If you prefer to build a kernel, and the machine's hardware and software configuration exactly matches
2265 another IRIX machine on which AFS is already built into the kernel, you can copy the kernel from that machine to
2266 this one. In general, however, it is better to build AFS modifications into the kernel on each machine according
2267 to the following instructions. <OL
2271 >Copy the kernel initialization file <SPAN
2277 > to the local <SPAN
2281 >/var/sysgen/system</B
2283 > directory, and the kernel master file <SPAN
2289 > to the local <SPAN
2293 >/var/sysgen/master.d</B
2297 CLASS="programlisting"
2302 >cp -p bin/afs.sm /var/sysgen/system</B
2309 >cp -p bin/afs /var/sysgen/master.d</B
2317 >Copy the appropriate AFS kernel library file to the local file <SPAN
2321 >/var/sysgen/boot/afs.a</B
2332 > portion of the library file name must match the
2333 value previously returned by the <SPAN
2339 > command. Also choose the file
2340 appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for
2341 the machine to act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library
2344 >If the machine's kernel supports NFS server functionality:</P
2346 CLASS="programlisting"
2351 >cp -p bin/libafs.IP</B
2360 >.a /var/sysgen/boot/afs.a</B
2365 >If the machine's kernel does not support NFS server functionality:</P
2367 CLASS="programlisting"
2372 >cp -p bin/libafs.IP</B
2381 >.nonfs.a /var/sysgen/boot/afs.a</B
2394 > command to deactivate the <SPAN
2400 > configuration variable. <PRE
2401 CLASS="programlisting"
2406 >/etc/chkconfig -f afsml off</B
2412 >If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server
2413 functionality, activate the <SPAN
2421 CLASS="programlisting"
2426 >/etc/chkconfig -f afsxnfs on</B
2433 >Copy the existing kernel file, <SPAN
2439 >, to a safe location. Compile
2440 the new kernel, which is created in the file <SPAN
2453 > file when the machine reboots in the next step.
2455 CLASS="programlisting"
2460 >cp /unix /unix_noafs</B
2475 >Reboot the machine to start using the new kernel, and login again as the superuser <SPAN
2482 CLASS="programlisting"
2494 >shutdown -i6 -g0 -y</B
2522 >Create a directory called <SPAN
2531 > for each AFS server partition you are configuring (there
2532 must be at least one). Repeat the command for each partition. <PRE
2533 CLASS="programlisting"
2549 >Add a line with the following format to the file systems registry file, <SPAN
2555 >, for each partition (or logical volume created with the XLV volume manager) to be
2556 mounted on one of the directories created in the previous step.</P
2558 >For an XFS partition or logical volume:</P
2560 CLASS="programlisting"
2561 > /dev/dsk/<VAR
2567 > xfs rw,raw=/dev/rdsk/<VAR
2573 >For an EFS partition:</P
2575 CLASS="programlisting"
2576 > /dev/dsk/<VAR
2582 > efs rw,raw=/dev/rdsk/<VAR
2588 >The following are examples of an entry for each file system type:</P
2590 CLASS="programlisting"
2591 > /dev/dsk/dks0d2s6 /vicepa xfs rw,raw=/dev/rdsk/dks0d2s6 0 0
2592 /dev/dsk/dks0d3s1 /vicepb efs rw,raw=/dev/rdsk/dks0d3s1 0 0
2597 >Create a file system on each partition that is to be mounted on a <SPAN
2606 > directory. The following commands are probably appropriate,
2607 but consult the IRIX documentation for more information. In both cases, <VAR
2611 device name like <SPAN
2615 >/dev/rdsk/dks0d0s0</B
2617 > for a single disk partition or <SPAN
2623 > for a logical volume.</P
2625 >For XFS file systems, include the indicated options to configure the partition or logical volume with inodes
2626 large enough to accommodate AFS-specific information:</P
2628 CLASS="programlisting"
2633 >mkfs -t xfs -i size=512 -l size=4000b</B
2641 >For EFS file systems:</P
2643 CLASS="programlisting"
2658 >Mount each partition by issuing either the <SPAN
2664 > command to mount all
2665 partitions at once or the <SPAN
2671 > command to mount each partition in turn.</P
2681 > If you have configured partitions or logical volumes to use XFS,
2682 issue the following command to verify that the inodes are configured properly (are large enough to accommodate
2683 AFS-specific information). If the configuration is correct, the command returns no output. Otherwise, it specifies the
2684 command to run in order to configure each partition or logical volume properly. <PRE
2685 CLASS="programlisting"
2690 >/usr/afs/bin/xfs_size_check</B
2698 >If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
2700 HREF="c371.html#HDRWQ40"
2701 >Enabling AFS Login on IRIX Systems</A
2707 HREF="c5467.html#HDRWQ108"
2708 >Starting Server Programs</A
2720 >Getting Started on Linux Systems</A
2723 >Begin by running the AFS initialization script to call the <SPAN
2730 dynamically loads AFS modifications into the kernel. Then create partitions for storing AFS volumes. You do not need to
2731 replace the Linux <SPAN
2741 >Mount the AFS CD-ROM for Linux on the local <SPAN
2747 > directory. For instructions
2748 on mounting CD-ROMs (either locally or remotely via NFS), see your Linux documentation. Then change directory as
2750 CLASS="programlisting"
2755 >cd /cdrom/i386_linux22/root.client/usr/vice/etc</B
2763 >Copy the AFS kernel library files to the local <SPAN
2767 >/usr/vice/etc/modload</B
2770 The filenames for the libraries have the format <SPAN
2789 > indicates the kernel build level. The string <SPAN
2799 > indicates that the file is appropriate for machines running a multiprocessor
2801 CLASS="programlisting"
2806 >cp -rp modload /usr/vice/etc</B
2814 >Copy the AFS initialization script to the local directory for initialization files (by convention, <SPAN
2818 >/etc/rc.d/init.d</B
2820 > on Linux machines). Note the removal of the <SPAN
2826 > extension as you copy the script. <PRE
2827 CLASS="programlisting"
2832 >cp -p afs.rc /etc/rc.d/init.d/afs</B
2840 >Run the AFS initialization script to load AFS extensions into the kernel. You can ignore any error messages
2841 about the inability to start the BOS Server or the Cache Manager or AFS client. <PRE
2842 CLASS="programlisting"
2847 >/etc/rc.d/init.d/afs start</B
2855 >Create a directory called <SPAN
2865 server partition you are configuring (there must be at least one). Repeat the command for each partition.
2867 CLASS="programlisting"
2883 >Add a line with the following format to the file systems registry file, <SPAN
2889 >, for each directory just created. The entry maps the directory name to the disk
2890 partition to be mounted on it. <PRE
2891 CLASS="programlisting"
2902 >The following is an example for the first partition being configured.</P
2904 CLASS="programlisting"
2905 > /dev/sda8 /vicepa ext2 defaults 0 2
2910 >Create a file system on each partition that is to be mounted at a <SPAN
2919 > directory. The following command is probably appropriate,
2920 but consult the Linux documentation for more information. <PRE
2921 CLASS="programlisting"
2937 >Mount each partition by issuing either the <SPAN
2943 > command to mount all
2944 partitions at once or the <SPAN
2950 > command to mount each partition in turn.</P
2954 >If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
2956 HREF="c371.html#HDRWQ44"
2957 >Enabling AFS Login on Linux Systems</A
2963 HREF="c5467.html#HDRWQ108"
2964 >Starting Server Programs</A
2976 >Getting Started on Solaris Systems</A
2979 >Begin by running the AFS initialization script to call the <SPAN
2986 dynamically loads AFS modifications into the kernel. Then configure partitions and replace the Solaris <SPAN
2992 > program with a version that correctly handles AFS volumes. <OL
2996 >Mount the AFS CD-ROM for Solaris on the <SPAN
3002 > directory. For instructions on
3003 mounting CD-ROMs (either locally or remotely via NFS), see your Solaris documentation. Then change directory as
3005 CLASS="programlisting"
3010 >cd /cdrom/sun4x_56/root.client/usr/vice/etc</B
3018 >Copy the AFS initialization script to the local directory for initialization files (by convention, <SPAN
3024 > on Solaris machines). Note the removal of the <SPAN
3031 extension as you copy the script. <PRE
3032 CLASS="programlisting"
3037 >cp -p afs.rc /etc/init.d/afs</B
3045 >Copy the appropriate AFS kernel library file to the local file <SPAN
3053 >If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, its kernel supports NFS server
3054 functionality, and the <SPAN
3060 > process is running:</P
3062 CLASS="programlisting"
3067 >cp -p modload/libafs.o /kernel/fs/afs</B
3072 >If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, and its kernel does not support NFS
3073 server functionality or the <SPAN
3079 > process is not running:</P
3081 CLASS="programlisting"
3086 >cp -p modload/libafs.nonfs.o /kernel/fs/afs</B
3091 >If the machine is running the 64-bit version of Solaris 7, its kernel supports NFS server functionality, and the
3098 > process is running:</P
3100 CLASS="programlisting"
3105 >cp -p modload/libafs64.o /kernel/fs/sparcv9/afs</B
3110 >If the machine is running the 64-bit version of Solaris 7, and its kernel does not support NFS server
3111 functionality or the <SPAN
3117 > process is not running:</P
3119 CLASS="programlisting"
3124 >cp -p modload/libafs64.nonfs.o /kernel/fs/sparcv9/afs</B
3131 >Run the AFS initialization script to load AFS modifications into the kernel. You can ignore any error messages
3132 about the inability to start the BOS Server or the Cache Manager or AFS client. <PRE
3133 CLASS="programlisting"
3138 >/etc/init.d/afs start</B
3144 >When an entry called <SAMP
3145 CLASS="computeroutput"
3147 > does not already exist in the local <SPAN
3151 >/etc/name_to_sysnum</B
3153 > file, the script automatically creates it and reboots the machine to start
3154 using the new version of the file. If this happens, log in again as the superuser <SPAN
3160 > after the reboot and run the initialization script again. This time the required entry
3165 >/etc/name_to_sysnum</B
3167 > file, and the <SPAN
3175 CLASS="programlisting"
3191 >/etc/init.d/afs start</B
3204 > directory to house the AFS-modified <SPAN
3210 > program and related files. <PRE
3211 CLASS="programlisting"
3216 >mkdir /usr/lib/fs/afs</B
3223 >cd /usr/lib/fs/afs</B
3237 > binary to the newly created directory, changing the name as you
3239 CLASS="programlisting"
3244 >cp /cdrom/sun4x_56/root.server/etc/vfsck fsck</B
3252 >Working in the <SPAN
3258 > directory, create the following links to Solaris
3260 CLASS="programlisting"
3265 >ln -s /usr/lib/fs/ufs/clri</B
3272 >ln -s /usr/lib/fs/ufs/df</B
3279 >ln -s /usr/lib/fs/ufs/edquota</B
3286 >ln -s /usr/lib/fs/ufs/ff</B
3293 >ln -s /usr/lib/fs/ufs/fsdb</B
3300 >ln -s /usr/lib/fs/ufs/fsirand</B
3307 >ln -s /usr/lib/fs/ufs/fstyp</B
3314 >ln -s /usr/lib/fs/ufs/labelit</B
3321 >ln -s /usr/lib/fs/ufs/lockfs</B
3328 >ln -s /usr/lib/fs/ufs/mkfs</B
3335 >ln -s /usr/lib/fs/ufs/mount</B
3342 >ln -s /usr/lib/fs/ufs/ncheck</B
3349 >ln -s /usr/lib/fs/ufs/newfs</B
3356 >ln -s /usr/lib/fs/ufs/quot</B
3363 >ln -s /usr/lib/fs/ufs/quota</B
3370 >ln -s /usr/lib/fs/ufs/quotaoff</B
3377 >ln -s /usr/lib/fs/ufs/quotaon</B
3384 >ln -s /usr/lib/fs/ufs/repquota</B
3391 >ln -s /usr/lib/fs/ufs/tunefs</B
3398 >ln -s /usr/lib/fs/ufs/ufsdump</B
3405 >ln -s /usr/lib/fs/ufs/ufsrestore</B
3412 >ln -s /usr/lib/fs/ufs/volcopy</B
3420 >Append the following line to the end of the file <SPAN
3424 >/etc/dfs/fstypes</B
3428 CLASS="programlisting"
3429 > afs AFS Utilities
3441 > file, making two changes. <UL
3444 >Add an entry for AFS to the <SAMP
3445 CLASS="computeroutput"
3447 > statement for option 2, so that it reads
3449 CLASS="programlisting"
3451 ufs) foptions="-o p"
3453 afs) foptions="-o p"
3455 s5) foptions="-y -t /var/tmp/tmp$$ -D"
3464 >Edit the file so that all AFS and UFS partitions are checked in parallel. Replace the following section of
3466 CLASS="programlisting"
3467 > # For fsck purposes, we make a distinction between ufs and
3468 # other file systems
3470 if [ "$fstype" = "ufs" ]; then
3471 ufs_fscklist="$ufs_fscklist $fsckdev"
3472 saveentry $fstype "$OPTIONS" $special $mountp
3478 >with the following section of code:</P
3480 CLASS="programlisting"
3481 > # For fsck purposes, we make a distinction between ufs/afs
3482 # and other file systems.
3484 if [ "$fstype" = "ufs" -o "$fstype" = "afs" ]; then
3485 ufs_fscklist="$ufs_fscklist $fsckdev"
3486 saveentry $fstype "$OPTIONS" $special $mountp
3496 >Create a directory called <SPAN
3506 server partition you are configuring (there must be at least one). Repeat the command for each partition.
3508 CLASS="programlisting"
3524 >Add a line with the following format to the file systems registry file, <SPAN
3530 >, for each partition to be mounted on a directory created in the previous step. Note
3532 CLASS="computeroutput"
3534 > in the fourth field, which tells Solaris to use the AFS-modified
3541 > program on this partition. <PRE
3542 CLASS="programlisting"
3543 > /dev/dsk/<VAR
3559 >The following is an example for the first partition being configured.</P
3561 CLASS="programlisting"
3562 > /dev/dsk/c0t6d0s1 /dev/rdsk/c0t6d0s1 /vicepa afs 3 yes
3567 >Create a file system on each partition that is to be mounted at a <SPAN
3576 > directory. The following command is probably appropriate,
3577 but consult the Solaris documentation for more information. <PRE
3578 CLASS="programlisting"
3583 >newfs -v /dev/rdsk/</B
3600 > command to mount all partitions at once.</P
3604 >If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
3606 HREF="c371.html#HDRWQ49"
3607 >Enabling AFS Login and Editing the File Systems Clean-up Script on Solaris
3614 HREF="c5467.html#HDRWQ108"
3615 >Starting Server Programs</A
3628 >Starting Server Programs</A
3631 >In this section you initialize the BOS Server, the Update Server, the controller process for NTPD, and the <SPAN
3637 > process. You begin by copying the necessary server files to the local disk. <OL
3641 >Copy file server binaries to the local <SPAN
3650 >On a machine of an existing system type, you can either load files from the AFS CD-ROM or use a remote file
3651 transfer protocol to copy files from an existing server machine of the same system type. To load from the CD-ROM,
3652 see the instructions just following for a machine of a new system type. If using a remote file transfer protocol,
3653 copy the complete contents of the existing server machine's <SPAN
3664 >On a machine of a new system type, you must use the following instructions to copy files from the AFS
3675 > directory, mount the AFS CD-ROM for this
3676 machine's system type, if it is not already. For instructions on mounting CD-ROMs (either locally or
3677 remotely via NFS), consult the operating system documentation.</P
3681 >Copy files from the CD-ROM to the local <SPAN
3689 CLASS="programlisting"
3703 >/root.server/usr/afs</B
3710 >cp -rp * /usr/afs</B
3724 >Copy the contents of the <SPAN
3730 > directory from an existing file server
3731 machine, using a remote file transfer protocol such as <SPAN
3737 > or NFS. If you use a system
3738 control machine, it is best to copy the contents of its <SPAN
3745 choose not to run a system control machine, copy the directory's contents from any existing file server machine.
3750 >Change to the <SPAN
3756 > directory and start the BOS Server (<SPAN
3762 > process). Include the <SPAN
3768 > flag to prevent the AFS
3769 processes from performing authorization checking. This is a grave compromise of security; finish the remaining
3770 instructions in this section in an uninterrupted pass. <PRE
3771 CLASS="programlisting"
3783 >./bosserver -noauth &</B
3794 >If you run a system control machine, create the <SPAN
3800 > process as an instance of the client portion of the Update Server. It accepts updates
3801 of the common configuration files stored in the system control machine's <SPAN
3808 directory from the <SPAN
3814 > process (server portion of the Update Server) running on
3815 that machine. The cell's first file server machine was installed as the system control machine in <A
3816 HREF="c371.html#HDRWQ61"
3817 >Starting the Server Portion of the Update Server</A
3818 >. (If you do not run a system control machine,
3819 you must update the contents of the <SPAN
3825 > directory on each file server machine,
3826 using the appropriate <SPAN
3834 >By default, the Update Server performs updates every 300 seconds (five minutes). Use the <SPAN
3840 > argument to specify a different number of seconds. For the
3844 > argument, substitute the name of the machine you are installing. The
3845 command appears on multiple lines here only for legibility reasons.</P
3847 CLASS="programlisting"
3861 >upclientetc simple</B
3868 >"/usr/afs/bin/upclient</B
3872 >system control machine</VAR
3887 >/usr/afs/etc" -cell</B
3906 >Create an instance of the Update Server to handle distribution of the file server binaries
3916 >If this is the first file server machine of its AFS system type, create the <SPAN
3922 > process as an instance of the server portion of the Update Server. It distributes
3923 its copy of the file server process binaries to the other file server machines of this system type that you
3924 install in future. Creating this process makes this machine the binary distribution machine for its type.
3926 CLASS="programlisting"
3947 >"/usr/afs/bin/upserver -clear /usr/afs/bin"</B
3971 >If this machine is an existing system type, create the <SPAN
3978 as an instance of the client portion of the Update Server. It accepts updates of the AFS binaries from the
3985 > process running on the binary distribution machine for its system type.
3986 For distribution to work properly, the <SPAN
3992 > process must already by running
4001 > argument to specify that the <SPAN
4007 > process requests unencrypted transfer of the binaries in the <SPAN
4013 > directory. Binaries are not sensitive and encrypting them is
4016 >By default, the Update Server performs updates every 300 seconds (five minutes). Use the <SPAN
4022 > argument to specify an different number of seconds.</P
4024 CLASS="programlisting"
4038 >upclientbin simple</B
4045 >"/usr/afs/bin/upclient</B
4049 >binary distribution machine</VAR
4064 >-clear /usr/afs/bin" -cell</B
4089 > process, which configures the Network Time Protocol Daemon
4090 (NTPD) to choose a database server machine chosen randomly from the local <SPAN
4094 >/usr/afs/etc/CellServDB</B
4096 > file as its time source. In the standard configuration, the first
4097 database server machine installed in your cell refers to a time source outside the cell, and serves as the basis for
4098 clock synchronization on all server machines. <PRE
4099 CLASS="programlisting"
4120 >/usr/afs/bin/runntp -cell</B
4141 >Do not run the <SPAN
4147 > process if NTPD or another time synchronization protocol
4148 is already running on the machine. Some versions of some operating systems run a time synchronization program by
4149 default, as detailed in the <SPAN
4153 >IBM AFS Release Notes</I
4157 >Attempting to run multiple instances of the NTPD causes an error. Running NTPD together with another time
4158 synchronization protocol is unnecessary and can cause instability in the clock setting.</P
4170 > process, which binds together the File Server, Volume Server, and
4172 CLASS="programlisting"
4193 >/usr/afs/bin/fileserver /usr/afs/bin/volserver</B
4200 >/usr/afs/bin/salvager -cell</B
4224 >Installing Client Functionality</A
4227 >If you want this machine to be a client as well as a server, follow the instructions in this section. Otherwise, skip to
4229 HREF="c5467.html#HDRWQ112"
4230 >Completing the Installation</A
4233 >Begin by loading the necessary client files to the local disk. Then create the necessary configuration files and start
4234 the Cache Manager. For more detailed explanation of the procedures involved, see the corresponding instructions in <A
4236 >Installing the First AFS Machine</A
4237 > (in the sections following <A
4238 HREF="c371.html#HDRWQ63"
4240 Installing Client Functionality</A
4243 >If another AFS machine of this machine's system type exists, the AFS binaries are probably already accessible in your
4244 AFS filespace (the conventional location is <SPAN
4268 >). If not, or if this is
4269 the first AFS machine of its type, copy the AFS binaries for this system type into an AFS volume by following the instructions
4271 HREF="c371.html#HDRWQ83"
4272 >Storing AFS Binaries in AFS</A
4273 >. Because this machine is not yet an AFS client, you must perform
4274 the procedure on an existing AFS machine. However, remember to perform the final step (linking the local directory <SPAN
4280 > to the appropriate location in the AFS file tree) on this machine itself. If you also want
4281 to create AFS volumes to house UNIX system binaries for the new system type, see <A
4282 HREF="c371.html#HDRWQ88"
4289 >Copy client binaries and files to the local disk. <UL
4292 >On a machine of an existing system type, you can either load files from the AFS CD-ROM or use a remote file
4293 transfer protocol to copy files from an existing server machine of the same system type. To load from the CD-ROM,
4294 see the instructions just following for a machine of a new system type. If using a remote file transfer protocol,
4295 copy the complete contents of the existing client machine's <SPAN
4306 >On a machine of a new system type, you must use the following instructions to copy files from the AFS
4317 > directory, mount the AFS CD-ROM for this
4318 machine's system type, if it is not already. For instructions on mounting CD-ROMs (either locally or
4319 remotely via NFS), consult the operating system documentation.</P
4323 >Copy files to the local <SPAN
4331 >This step places a copy of the AFS initialization script (and related files, if applicable) into the
4338 > directory. In the preceding instructions for incorporating
4339 AFS into the kernel, you copied the script directly to the operating system's conventional location for
4340 initialization files. When you incorporate AFS into the machine's startup sequence in a later step, you can
4341 choose to link the two files.</P
4343 >On some system types that use a dynamic kernel loader program, you previously copied AFS library files
4344 into a subdirectory of the <SPAN
4350 > directory. On other system types,
4351 you copied the appropriate AFS library file directly to the directory where the operating system accesses
4352 it. The following commands do not copy or recopy the AFS library files into the <SPAN
4358 > directory, because on some system types the library files consume a
4359 large amount of space. If you want to copy them, add the <SPAN
4372 > command and skip the second <SPAN
4381 CLASS="programlisting"
4395 >/root.client/usr/vice/etc</B
4402 >cp -p * /usr/vice/etc</B
4409 >cp -rp C /usr/vice/etc</B
4422 >Change to the <SPAN
4428 > directory and create the <SPAN
4434 > file as a copy of the <SPAN
4438 >/usr/afs/etc/ThisCell</B
4441 must first remove the symbolic link to the <SPAN
4445 >/usr/afs/etc/ThisCell</B
4448 Server created automatically in <A
4449 HREF="c5467.html#HDRWQ108"
4450 >Starting Server Programs</A
4452 CLASS="programlisting"
4457 >cd /usr/vice/etc</B
4471 >cp /usr/afs/etc/ThisCell ThisCell</B
4479 >Remove the symbolic link to the <SPAN
4483 >/usr/afs/etc/CellServDB</B
4486 CLASS="programlisting"
4503 >/usr/vice/etc/CellServDB</B
4505 > file. Use a network file transfer program
4512 > or NFS to copy it from one of the following sources, which are listed in
4513 decreasing order of preference: <UL
4516 >Your cell's central <SPAN
4522 > source file (the conventional location is
4536 >/common/etc/CellServDB</B
4548 > file maintained by the AFS Product Support
4553 >An existing client machine in your cell</P
4561 >CellServDB.sample</B
4563 > file included in the
4571 >/root.client/usr/vice/etc</B
4573 > directory of each AFS
4574 CD-ROM; add an entry for the local cell by following the instructions in <A
4575 HREF="c371.html#HDRWQ66"
4577 Client CellServDB File</A
4591 > file for either a disk cache or a memory cache. For a
4592 discussion of the appropriate values to record in the file, see <A
4593 HREF="c371.html#HDRWQ67"
4598 >To configure a disk cache, issue the following commands. If you are devoting a partition exclusively to caching,
4599 as recommended, you must also configure it, make a file system on it, and mount it at the directory created in this
4602 CLASS="programlisting"
4607 >mkdir /usr/vice/cache</B
4614 >echo "/afs:/usr/vice/cache:</B
4623 >" > cacheinfo</B
4628 >To configure a memory cache:</P
4630 CLASS="programlisting"
4635 >echo "/afs:/usr/vice/cache:</B
4644 >" > cacheinfo</B
4651 >Create the local directory on which to mount the AFS filespace, by convention <SPAN
4657 >. If the directory already exists, verify that it is empty. <PRE
4658 CLASS="programlisting"
4671 >On AIX systems, add the following line to the <SPAN
4677 > file. It enables AIX to
4678 unmount AFS correctly during shutdown. <PRE
4679 CLASS="programlisting"
4680 > afs 4 none none
4686 >On Linux systems, copy the <SPAN
4692 > options file from the <SPAN
4698 > directory to the <SPAN
4711 > extension as you do so. <PRE
4712 CLASS="programlisting"
4717 >cp /usr/vice/etc/afs.conf /etc/sysconfig/afs</B
4725 >Edit the machine's AFS initialization script or <SPAN
4731 > options file to set
4732 appropriate values for <SPAN
4738 > command parameters. The script resides in the indicated
4739 location on each system type: <UL
4742 >On AIX systems, <SPAN
4752 >On Digital UNIX systems, <SPAN
4756 >/sbin/init.d/afs</B
4762 >On HP-UX systems, <SPAN
4766 >/sbin/init.d/afs</B
4772 >On IRIX systems, <SPAN
4782 >On Linux systems, <SPAN
4786 >/etc/sysconfig/afs</B
4798 >On Solaris systems, <SPAN
4809 >Use one of the methods described in <A
4810 HREF="c371.html#HDRWQ70"
4811 >Configuring the Cache Manager</A
4813 following flags to the <SPAN
4819 > command line. If you intend for the machine to remain an
4820 AFS client, also set any performance-related arguments you wish. <UL
4829 > flag, because this is a file server machine that is also
4840 > flag if the machine is to use a memory cache.</P
4850 > flag to display a trace of the Cache Manager's
4851 initialization on the standard output stream.</P
4858 >If appropriate, follow the instructions in <A
4859 HREF="c371.html#HDRWQ83"
4860 >Storing AFS Binaries in AFS</A
4862 AFS binaries for this system type into an AFS volume. See the introduction to this section for further
4874 >Completing the Installation</A
4877 >At this point you run the machine's AFS initialization script to verify that it correctly loads AFS modifications into
4878 the kernel and starts the BOS Server, which starts the other server processes. If you have installed client files, the script
4879 also starts the Cache Manager. If the script works correctly, perform the steps that incorporate it into the machine's startup
4880 and shutdown sequence. If there are problems during the initialization, attempt to resolve them. The AFS Product Support group
4881 can provide assistance if necessary.</P
4883 >If the machine is configured as a client using a disk cache, it can take a while for the <SPAN
4889 > program to create all of the <SPAN
4899 in the cache directory. Messages on the console trace the initialization process. <OL
4909 > command to shut down the AFS server processes other than
4910 the BOS Server. Include the <SPAN
4916 > flag to delay return of the command shell prompt
4917 until all processes shut down completely. <PRE
4918 CLASS="programlisting"
4923 >/usr/afs/bin/bos shutdown</B
4946 > command to learn the BOS Server's process ID number (PID), and then
4953 > command to stop the <SPAN
4961 CLASS="programlisting"
4970 >appropriate_ps_options</VAR
4975 >| grep bosserver</B
4993 >Run the AFS initialization script by issuing the appropriate commands for this system type.</P
5005 >Reboot the machine and log in again as the local superuser <SPAN
5013 CLASS="programlisting"
5044 >Run the AFS initialization script. <PRE
5045 CLASS="programlisting"
5058 >Edit the AIX initialization file, <SPAN
5064 >, adding the following line
5065 to invoke the AFS initialization script. Place it just after the line that starts NFS daemons. <PRE
5066 CLASS="programlisting"
5067 > rcafs:2:wait:/etc/rc.afs > /dev/console 2>&1 # Start AFS services
5079 > There are now copies of the AFS initialization file in both the
5092 > directories. If you want
5093 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can
5094 always retrieve the original script from the AFS CD-ROM if necessary. <PRE
5095 CLASS="programlisting"
5100 >cd /usr/vice/etc</B
5114 >ln -s /etc/rc.afs</B
5123 HREF="c5467.html#LIWQ113"
5134 >On Digital UNIX systems:</B
5140 >Run the AFS initialization script. <PRE
5141 CLASS="programlisting"
5146 >/sbin/init.d/afs start</B
5154 >Change to the <SPAN
5160 > directory and issue the <SPAN
5167 > command to create symbolic links that incorporate the AFS initialization script into the Digital
5168 UNIX startup and shutdown sequence. <PRE
5169 CLASS="programlisting"
5181 >ln -s ../init.d/afs /sbin/rc3.d/S67afs</B
5188 >ln -s ../init.d/afs /sbin/rc0.d/K66afs</B
5202 > There are now copies of the AFS initialization file in both the
5216 you want to avoid potential confusion by guaranteeing that they are always the same, create a link between them.
5217 You can always retrieve the original script from the AFS CD-ROM if necessary. <PRE
5218 CLASS="programlisting"
5223 >cd /usr/vice/etc</B
5237 >ln -s /sbin/init.d/afs afs.rc</B
5246 HREF="c5467.html#LIWQ113"
5257 >On HP-UX systems:</B
5263 >Run the AFS initialization script. <PRE
5264 CLASS="programlisting"
5269 >/sbin/init.d/afs start</B
5277 >Change to the <SPAN
5283 > directory and issue the <SPAN
5290 > command to create symbolic links that incorporate the AFS initialization script into the HP-UX
5291 startup and shutdown sequence. <PRE
5292 CLASS="programlisting"
5304 >ln -s ../init.d/afs /sbin/rc2.d/S460afs</B
5311 >ln -s ../init.d/afs /sbin/rc2.d/K800afs</B
5325 > There are now copies of the AFS initialization file in both the
5339 you want to avoid potential confusion by guaranteeing that they are always the same, create a link between them.
5340 You can always retrieve the original script from the AFS CD-ROM if necessary. <PRE
5341 CLASS="programlisting"
5346 >cd /usr/vice/etc</B
5360 >ln -s /sbin/init.d/afs afs.rc</B
5369 HREF="c5467.html#LIWQ113"
5380 >On IRIX systems:</B
5386 >If you have configured the machine to use the <SPAN
5392 > dynamic loader program,
5393 reboot the machine and log in again as the local superuser <SPAN
5400 CLASS="programlisting"
5412 >shutdown -i6 -g0 -y</B
5437 > command to activate the <SPAN
5443 > configuration variable. <PRE
5444 CLASS="programlisting"
5449 >/etc/chkconfig -f afsserver on</B
5455 >If you have configured this machine as an AFS client and want to it remain one, also issue the <SPAN
5461 > command to activate the <SPAN
5470 CLASS="programlisting"
5475 >/etc/chkconfig -f afsclient on</B
5482 >Run the AFS initialization script. <PRE
5483 CLASS="programlisting"
5488 >/etc/init.d/afs start</B
5496 >Change to the <SPAN
5502 > directory and issue the <SPAN
5509 > command to create symbolic links that incorporate the AFS initialization script into the IRIX
5510 startup and shutdown sequence. <PRE
5511 CLASS="programlisting"
5523 >ln -s ../init.d/afs /etc/rc2.d/S35afs</B
5530 >ln -s ../init.d/afs /etc/rc0.d/K35afs</B
5544 > There are now copies of the AFS initialization file in both the
5558 you want to avoid potential confusion by guaranteeing that they are always the same, create a link between them.
5559 You can always retrieve the original script from the AFS CD-ROM if necessary. <PRE
5560 CLASS="programlisting"
5565 >cd /usr/vice/etc</B
5579 >ln -s /etc/init.d/afs afs.rc</B
5588 HREF="c5467.html#LIWQ113"
5599 >On Linux systems:</B
5605 >Reboot the machine and log in again as the local superuser <SPAN
5613 CLASS="programlisting"
5644 >Run the AFS initialization script. <PRE
5645 CLASS="programlisting"
5650 >/etc/rc.d/init.d/afs start</B
5664 > command to activate the <SPAN
5670 > configuration variable. Based on the instruction in the AFS initialization file that
5671 begins with the string <SAMP
5672 CLASS="computeroutput"
5674 >, the command automatically creates the symbolic
5675 links that incorporate the script into the Linux startup and shutdown sequence. <PRE
5676 CLASS="programlisting"
5681 >/sbin/chkconfig --add afs</B
5695 > There are now copies of the AFS initialization file in both the
5706 >/etc/rc.d/init.d</B
5709 and copies of the <SPAN
5715 > options file in both the <SPAN
5727 > directories. If you want
5728 to avoid potential confusion by guaranteeing that the two copies of each file are always the same, create a link
5729 between them. You can always retrieve the original script or options file from the AFS CD-ROM if necessary.
5731 CLASS="programlisting"
5736 >cd /usr/vice/etc</B
5743 >rm afs.rc afs.conf</B
5750 >ln -s /etc/rc.d/init.d/afs afs.rc</B
5757 >ln -s /etc/sysconfig/afs afs.conf</B
5766 HREF="c5467.html#LIWQ113"
5777 >On Solaris systems:</B
5783 >Reboot the machine and log in again as the local superuser <SPAN
5791 CLASS="programlisting"
5803 >shutdown -i6 -g0 -y</B
5822 >Run the AFS initialization script. <PRE
5823 CLASS="programlisting"
5828 >/etc/init.d/afs start</B
5836 >Change to the <SPAN
5842 > directory and issue the <SPAN
5849 > command to create symbolic links that incorporate the AFS initialization script into the Solaris
5850 startup and shutdown sequence. <PRE
5851 CLASS="programlisting"
5863 >ln -s ../init.d/afs /etc/rc3.d/S99afs</B
5870 >ln -s ../init.d/afs /etc/rc0.d/K66afs</B
5884 > There are now copies of the AFS initialization file in both the
5898 you want to avoid potential confusion by guaranteeing that they are always the same, create a link between them.
5899 You can always retrieve the original script from the AFS CD-ROM if necessary. <PRE
5900 CLASS="programlisting"
5905 >cd /usr/vice/etc</B
5919 >ln -s /etc/init.d/afs afs.rc</B
5939 > and its subdirectories on the new
5940 file server machine meet the ownership and mode bit requirements outlined in <A
5941 HREF="c371.html#HDRWQ96"
5943 Sensitive AFS Directories</A
5944 >. If necessary, use the <SPAN
5950 > command to correct the
5955 >To configure this machine as a database server machine, proceed to <A
5956 HREF="c5467.html#HDRWQ114"
5957 >Installing Database
5958 Server Functionality</A
5971 >Installing Database Server Functionality</A
5974 >This section explains how to install database server functionality. Database server machines have two defining
5975 characteristics. First, they run the Authentication Server, Protection Server, and Volume Location (VL) Server processes. They
5976 also run the Backup Server if the cell uses the AFS Backup System, as is assumed in these instructions. Second, they appear in
5983 > file of every machine in the cell (and of client machines in foreign cells, if
5984 they are to access files in this cell).</P
5986 >Note the following requirements for database server machines. <UL
5989 >In the conventional configuration, database server machines also serve as file server machines (run the File Server,
5990 Volume Server and Salvager processes). If you choose not to run file server functionality on a database server machine,
5991 then the kernel does not have to incorporate AFS modifications, but the local <SPAN
5998 directory must house most of the standard files and subdirectories. In particular, the <SPAN
6002 >/usr/afs/etc/KeyFile</B
6004 > file must contain the same keys as all other server machines in the cell. If
6005 you run a system control machine, run the <SPAN
6011 > process on every database server
6012 machine other than the system control machine; if you do not run a system control machine, use the <SPAN
6018 > command as instructed in the chapter in the <SPAN
6022 >IBM AFS Administration
6025 > about maintaining server encryption keys.</P
6027 >The instructions in this section assume that the machine on which you are installing database server functionality
6028 is already a file server machine. Contact the AFS Product Support group to learn how to install database server
6029 functionality on a non-file server machine.</P
6033 >During the installation of database server functionality, you must restart all of the database server machines to
6034 force the election of a new Ubik coordinator (synchronization site) for each database server process. This can cause a
6035 system outage, which usually lasts less than 5 minutes.</P
6039 >Updating the kernel memory list of database server machines on each client machine is generally the most
6040 time-consuming part of installing a new database server machine. It is, however, crucial for correct functioning in your
6041 cell. Incorrect knowledge of your cell's database server machines can prevent your users from authenticating, accessing
6042 files, and issuing AFS commands.</P
6044 >You update a client's kernel memory list by changing the <SPAN
6048 >/usr/vice/etc/CellServDB</B
6051 file and then either rebooting or issuing the <SPAN
6057 > command. For instructions, see
6058 the chapter in the <SPAN
6062 >IBM AFS Administration Guide</I
6064 > about administering client machines.</P
6066 >The point at which you update your clients' knowledge of database server machines depends on which of the database
6067 server machines has the lowest IP address. The following instructions indicate the appropriate place to update your client
6068 machines in either case. <UL
6071 >If the new database server machine has a lower IP address than any existing database server machine, update
6078 > file on every client machine before restarting the database server
6079 processes. If you do not, users can become unable to update (write to) any of the AFS databases. This is because the
6080 machine with the lowest IP address is usually elected as the Ubik coordinator, and only the Coordinator accepts
6081 database writes. On client machines that do not have the new list of database server machines, the Cache Manager
6082 cannot locate the new coordinator. (Be aware that if clients contact the new coordinator before it is actually in
6083 service, they experience a timeout before contacting another database server machine. This is a minor, and
6084 temporary, problem compared to being unable to write to the database.)</P
6088 >If the new database server machine does not have the lowest IP address of any database server machine, then it
6089 is better to update clients after restarting the database server processes. Client machines do not start using the
6090 new database server machine until you update their kernel memory list, but that does not usually cause timeouts or
6091 update problems (because the new machine is not likely to become the coordinator).</P
6104 >Summary of Procedures</A
6107 >To install a database server machine, perform the following procedures. <OL
6117 > suite of commands locally, as a precaution</P
6121 >Add the new machine to the <SPAN
6125 >/usr/afs/etc/CellServDB</B
6127 > file on existing file server
6132 >Update your cell's central <SPAN
6138 > source file and the file you make available
6143 >Update every client machine's <SPAN
6147 >/usr/vice/etc/CellServDB</B
6149 > file and kernel memory
6150 list of database server machines</P
6154 >Start the database server processes (Authentication Server, Backup Server, Protection Server, and Volume Location
6159 >Restart the database server processes on every database server machine</P
6163 >Notify the AFS Product Support group that you have installed a new database server machine</P
6183 >It is assumed that your PATH environment variable includes the directory that houses the AFS command binaries. If not,
6184 you possibly need to precede the command names with the appropriate pathname.</P
6191 >You can perform the following instructions on either a server or client machine. Login as an AFS administrator who
6192 is listed in the <SPAN
6196 >/usr/afs/etc/UserList</B
6198 > file on all server machines. <PRE
6199 CLASS="programlisting"
6212 >admin_password</VAR
6219 >If you are working on a client machine configured in the conventional manner, the <SPAN
6225 > command suite resides in the <SPAN
6232 symbolic link to an AFS directory. An error during installation can potentially block access to AFS, in which case it is
6233 helpful to have a copy of the <SPAN
6239 > binary on the local disk. This step is not necessary if
6240 you are working on a server machine, where the binary resides in the local <SPAN
6248 CLASS="programlisting"
6253 >cp /usr/afsws/bin/bos /tmp</B
6270 > command to add the new database server
6271 machine to the <SPAN
6275 >/usr/afs/etc/CellServDB</B
6277 > file on existing server machines (as well as the
6278 new database server machine itself).</P
6280 >Substitute the new database server machine's fully-qualified hostname for the <VAR
6284 argument. If you run a system control machine, substitute its fully-qualified hostname for the
6288 > argument. If you do not run a system control machine, repeat the <SPAN
6294 > command once for each server machine in your cell (including the new database server
6295 machine itself), by substituting each one's fully-qualified hostname for the <VAR
6299 argument in turn.</P
6301 CLASS="programlisting"
6317 >If you run a system control machine, wait for the Update Server to distribute the new <SPAN
6323 > file, which takes up to five minutes by default. If you are issuing individual <SPAN
6329 > commands, attempt to issue all of them within five minutes.</P
6337 >It is best to maintain a one-to-one mapping between hostnames and IP addresses on a multihomed database server
6338 machine (the conventional configuration for any AFS machine). The BOS Server uses the <SPAN
6342 >gethostbyname( )</B
6344 > routine to obtain the IP address associated with the <VAR
6348 > argument. If there is more than one address, the BOS Server records in the <SPAN
6354 > entry the one that appears first in the list of addresses returned by the routine. The
6355 routine possibly returns addresses in a different order on different machines, which can create inconsistency.</P
6374 server machine to verify that the new database server machine appears in its <SPAN
6382 CLASS="programlisting"
6401 >Add the new database server machine to your cell's central <SPAN
6407 > source file, if you use one. The standard location is <SPAN
6420 >/common/etc/CellServDB</B
6424 >If you are willing to make your cell accessible to users in foreign cells, add the new database server machine to
6425 the file that lists your cell's database server machines. The conventional location is <SPAN
6438 >/service/etc/CellServDB.local</B
6447 >If this machine's IP address is lower than any existing database server machine's, update
6448 every client machine's <SPAN
6452 >/usr/vice/etc/CellServDB</B
6454 > file and kernel memory list to include
6455 this machine. (If this machine's IP address is not the lowest, it is acceptable to wait until Step <A
6456 HREF="c5467.html#LIWQ123"
6460 >There are several ways to update the <SPAN
6466 > file on client machines, as
6467 detailed in the chapter of the <SPAN
6471 >IBM AFS Administration Guide</I
6473 > about administering client machines. One
6474 option is to copy over the central update source (which you updated in Step <A
6475 HREF="c5467.html#LIWQ116"
6478 without using the <SPAN
6484 > program. To update the machine's kernel memory list, you can
6485 either reboot after changing the <SPAN
6491 > file or issue the <SPAN
6505 >Start the Authentication Server (the <SPAN
6513 CLASS="programlisting"
6527 >kaserver simple /usr/afs/bin/kaserver</B
6538 >Start the Backup Server (the <SPAN
6544 > process). You must
6545 perform other configuration procedures before actually using the AFS Backup System, as detailed in the <SPAN
6550 Administration Guide</I
6553 CLASS="programlisting"
6567 >buserver simple /usr/afs/bin/buserver</B
6578 >Start the Protection Server (the <SPAN
6586 CLASS="programlisting"
6600 >ptserver simple /usr/afs/bin/ptserver</B
6611 >Start the Volume Location (VL) Server (the <SPAN
6619 CLASS="programlisting"
6633 >vlserver simple /usr/afs/bin/vlserver</B
6650 > command on every database server
6651 machine in the cell, including the new machine. The command restarts the Authentication, Backup, Protection, and VL
6652 Servers, which forces an election of a new Ubik coordinator for each process. The new machine votes in the election and is
6653 considered as a potential new coordinator.</P
6655 >A cell-wide service outage is possible during the election of a new coordinator for the VL Server, but it normally
6656 lasts less than five minutes. Such an outage is particularly likely if you are installing your cell's second database
6657 server machine. Messages tracing the progress of the election appear on the console.</P
6659 >Repeat this command on each of your cell's database server machines in quick succession. Begin with the machine with
6660 the lowest IP address.</P
6662 CLASS="programlisting"
6676 >kaserver buserver ptserver vlserver</B
6681 >If an error occurs, restart all server processes on the database server machines again by using one of the following
6691 > command with the <SPAN
6697 > flag for each database server machine</P
6701 >Reboot each database server machine, either using the <SPAN
6718 >If you did not update the <SPAN
6724 > file on client machines
6726 HREF="c5467.html#LIWQ117"
6735 >Send the new database server machine's name and IP address to the AFS Product Support
6738 >If you wish to participate in the AFS global name space, your cell's entry appear in a <SPAN
6744 > file that the AFS Product Support group makes available to all AFS sites. Otherwise,
6745 they list your cell in a private file that they do not share with other AFS sites.</P
6756 >Removing Database Server Functionality</A
6759 >Removing database server machine functionality is nearly the reverse of installing it.</P
6766 >Summary of Procedures</A
6769 >To decommission a database server machine, perform the following procedures. <OL
6779 > suite of commands locally, as a precaution</P
6783 >Notify the AFS Product Support group that you are decommissioning a database server machine</P
6787 >Update your cell's central <SPAN
6793 > source file and the file you make available
6798 >Update every client machine's <SPAN
6802 >/usr/vice/etc/CellServDB</B
6804 > file and kernel memory
6805 list of database server machines</P
6809 >Remove the machine from the <SPAN
6813 >/usr/afs/etc/CellServDB</B
6815 > file on file server
6820 >Stop the database server processes and remove them from the <SPAN
6824 >/usr/afs/local/BosConfig</B
6826 > file if desired</P
6830 >Restart the database server processes on the remaining database server machines</P
6850 >It is assumed that your PATH environment variable includes the directory that houses the AFS command binaries. If not,
6851 you possibly need to precede the command names with the appropriate pathname.</P
6858 >You can perform the following instructions on either a server or client machine. Login as an AFS administrator who
6859 is listed in the <SPAN
6863 >/usr/afs/etc/UserList</B
6865 > file on all server machines. <PRE
6866 CLASS="programlisting"
6879 >admin_password</VAR
6886 >If you are working on a client machine configured in the conventional manner, the <SPAN
6892 > command suite resides in the <SPAN
6899 symbolic link to an AFS directory. An error during installation can potentially block access to AFS, in which case it is
6900 helpful to have a copy of the <SPAN
6906 > binary on the local disk. This step is not necessary if
6907 you are working on a server machine, where the binary resides in the local <SPAN
6915 CLASS="programlisting"
6920 >cp /usr/afsws/bin/bos /tmp</B
6931 >Send the revised list of your cell's database server machines to the AFS Product Support
6934 >This step is particularly important if your cell is included in the global <SPAN
6940 > file. If the administrators in foreign cells do not learn about the change in your cell,
6941 they cannot update the <SPAN
6947 > file on their client machines. Users in foreign cells
6948 continue to send database requests to the decommissioned machine, which creates needless network traffic and activity on
6949 the machine. Also, the users experience time-out delays while their request is forwarded to a valid database server
6957 >Remove the decommissioned machine from your cell's central <SPAN
6963 > source file, if you use one. The conventional location is <SPAN
6976 >/common/etc/CellServDB</B
6980 >If you maintain a file that users in foreign cells can access to learn about your cell's database server machines,
6981 update it also. The conventional location is <SPAN
6994 >/service/etc/CellServDB.local</B
7003 >Update every client machine's <SPAN
7007 >/usr/vice/etc/CellServDB</B
7010 and kernel memory list to exclude this machine. Altering the <SPAN
7017 memory list before stopping the actual database server processes avoids possible time-out delays that result when users
7018 send requests to a decommissioned database server machine that is still listed in the file.</P
7020 >There are several ways to update the <SPAN
7026 > file on client machines, as
7027 detailed in the chapter of the <SPAN
7031 >IBM AFS Administration Guide</I
7033 > about administering client machines. One
7034 option is to copy over the central update source (which you updated in Step <A
7035 HREF="c5467.html#LIWQ116"
7038 without using the <SPAN
7044 > program. To update the machine's kernel memory list, you can
7045 either reboot after changing the <SPAN
7051 > file or issue the <SPAN
7071 > command to remove the
7072 decommissioned database server machine from the <SPAN
7076 >/usr/afs/etc/CellServDB</B
7081 >Substitute the decommissioned database server machine's fully-qualified hostname for the <VAR
7085 > argument. If you run a system control machine, substitute its fully-qualified hostname for the
7089 > argument. If you do not run a system control machine, repeat the <SPAN
7095 > command once for each server machine in your cell (including the decommissioned
7096 database server machine itself), by substituting each one's fully-qualified hostname for the
7100 > argument in turn.</P
7102 CLASS="programlisting"
7118 >If you run a system control machine, wait for the Update Server to distribute the new <SPAN
7124 > file, which takes up to five minutes by default. If issuing individual <SPAN
7130 > commands, attempt to issue all of them within five minutes.</P
7147 server machine to verify that the decommissioned database server machine no longer appears in its <SPAN
7154 CLASS="programlisting"
7179 > command to stop the database server
7180 processes on the machine, by substituting its fully-qualified hostname for the
7184 > argument. The command changes each process's status in the <SPAN
7188 >/usr/afs/local/BosConfig</B
7191 CLASS="computeroutput"
7193 >, but does not remove its
7194 entry from the file. <PRE
7195 CLASS="programlisting"
7209 >kaserver buserver ptserver vlserver</B
7233 > command to remove the entries for database server processes from the <SPAN
7239 > file. This step is unnecessary if you plan to restart the database server functionality
7240 on this machine in future. <PRE
7241 CLASS="programlisting"
7255 >kaserver buserver ptserver vlserver</B
7272 > command on every database server
7273 machine in the cell, to restart the Authentication, Backup, Protection, and VL Servers. This forces the election of a Ubik
7274 coordinator for each process, ensuring that the remaining database server processes recognize that the machine is no
7275 longer a database server.</P
7277 >A cell-wide service outage is possible during the election of a new coordinator for the VL Server, but it normally
7278 lasts less than five minutes. Messages tracing the progress of the election appear on the console.</P
7280 >Repeat this command on each of your cell's database server machines in quick succession. Begin with the machine with
7281 the lowest IP address.</P
7283 CLASS="programlisting"
7297 >kaserver buserver ptserver vlserver</B
7302 >If an error occurs, restart all server processes on the database server machines again by using one of the following
7312 > command with the <SPAN
7318 > flag for each database server machine</P
7322 >Reboot each database server machine, either using the <SPAN
7343 SUMMARY="Footer navigation table"
7382 >Installing the First AFS Machine</TD
7392 >Installing Additional Client Machines</TD