[[!toc levels=3]] # Installing Additional Server Machines Instructions for the following procedures appear in the indicated section of this chapter. - Installing an Additional File Server Machine - Installing Database Server Functionality - Removing Database Server Functionality The instructions make the following assumptions. - You have already installed your cell's first file server machine by following the instructions in Installing the First AFS Machine - You are logged in as the local superuser root - You are working at the console - A standard version of one of the operating systems supported by the current version of AFS is running on the machine - 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 attached to a machine that is accessible by network - All files on the CD-ROM are owned by root. i.e. The files that you install should be owned by root, or the standard application user for the system. # Installing an Additional File Server Machine The procedure for installing a new file server machine is similar to installing the first file server machine in your cell. There are a few parts of the installation that differ depending on whether the machine is the same AFS system type as an existing file server machine or is the first file server machine of its system type in your cell. The differences mostly concern the source for the needed binaries and files, and what portions of the Update Server you install: - On a new system type, you must load files and binaries from the AFS CD-ROM. You install the server portion of the Update Server to make this machine the binary distribution machine for its system type. - On an existing system type, you can copy files and binaries from a previously installed file server machine, rather than from the CD-ROM. You install the client portion of the Update Server to accept updates of binaries, because a previously installed machine of this type was installed as the binary distribution machine. These instructions are brief; for more detailed information, refer to the corresponding steps in Installing the First AFS Machine. To install a new file server machine, perform the following procedures: 1. Copy needed binaries and files onto this machine's local disk 1. Incorporate AFS modifications into the kernel 1. Configure partitions for storing volumes 1. Replace the standard fsck utility with the AFS-modified version on some system types 1. Start the Basic [[OverSeer]] (BOS) Server 1. Start the appropriate portion of the Update Server 1. Start the fs process, which incorporates three component processes: the File Server, Volume Server, and Salvager 1. Start the controller process (called runntp) for the Network Time Protocol Daemon, which synchronizes clocks After completing the instructions in this section, you can install database server functionality on the machine according to the instructions in Installing Database Server Functionality. # Creating AFS Directories and Performing Platform-Specific Procedures Create the /usr/afs and /usr/vice/etc directories on the local disk. Subsequent instructions copy files from the AFS distribution CD-ROM into them, at the appropriate point for each system type. # mkdir /usr/afs # mkdir /usr/afs/bin # mkdir /usr/vice # mkdir /usr/vice/etc # mkdir /cdrom As on the first file server machine, the initial procedures in installing an additional file server machine vary a good deal from platform to platform. For convenience, the following sections group together all of the procedures for a system type. Most of the remaining procedures are the same on every system type, but differences are noted as appropriate. The initial procedures are the following. - Incorporate AFS modifications into the kernel, either by using a dynamic kernel loader program or by building a new static kernel - Configure server partitions to house AFS volumes - Replace the operating system vendor's fsck program with a version that recognizes AFS data - If the machine is to remain an AFS client machine, modify the machine's authentication system so that users obtain an AFS token as they log into the local file system. (For this procedure only, the instructions direct you to the platform-specific section in Installing the First AFS Machine.) To continue, proceed to the section for this system type: - Getting Started on AIX Systems - Getting Started on Digital UNIX Systems - Getting Started on HP-UX Systems - Getting Started on IRIX Systems - Getting Started on Linux Systems - Getting Started on Solaris Systems # Getting Started on AIX Systems [[Loading AFS into the AIX Kernel|LoadingAFSIntoTheAIXKernel]] ## Replacing the fsck Program Helper on AIX Systems Never run the standard fsck program on AFS server partitions. It discards AFS volumes. [[Replacing the fsck Program Helper on AIX Systems|ReplacingTheFsckProgramHelperOnAIXSystems]] ## Configuring Server Volumes on AIX Systems If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step. [[Configuring Server Volumes on AIX|ConfiguringServerVolumesOnAIX]] If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on AIX Systems|EnablingAFSLoginOnAIXSystems]]. Proceed to Starting Server Programs. # Getting Started on Digital UNIX Systems Begin by building AFS modifications into the kernel, then configure server partitions and replace the Digital UNIX fsck program with a version that correctly handles AFS volumes. If the machine's hardware and software configuration exactly matches another Digital UNIX machine on which AFS is already built into the kernel, you can copy the kernel from that machine to this one. In general, however, it is better to build AFS modifications into the kernel on each machine according to the following instructions. [[Building AFS into the Digital UNIX Kernel|BuildingAFSIntoTheDigitalUNIXKernel]] ## Replacing the fsck Program on Digital UNIX Systems Never run the standard fsck program on AFS server partitions. It discards AFS volumes. [[Replacing the fsck Program on Digital UNIX Systems|ReplacingTheFsckProgramOnDigitalUNIXSystems]] ## Configuring Server Volumes on Digital UNIX Systems If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step. [[Configuring Server Volumes on Digital UNIX|ConfiguringServerVolumesOnDigitalUNIX]] If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Digital UNIX Systems|EnablingAFSLoginOnDigitalUNIXSystems]]. Proceed to Starting Server Programs. # Getting Started on HP-UX Systems Begin by building AFS modifications into the kernel, then configure server partitions and replace the HP-UX fsck program with a version that correctly handles AFS volumes. [[Building AFS into the HP-UX Kernel|BuildingAFSIntoTheHP-UXKernel]] ## Configuring the AFS-modified fsck Program on HP-UX Systems Never run the standard fsck program on AFS server partitions. It discards AFS volumes. [[Configuring the AFS-modified fsck Program on HP-UX Systems|ConfiguringTheAFS-modifiedFsckProgramOnHP-UXSystems]] ## Configuring Server Volumes on HP-UX Systems If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step. [[Configuring Server Volumes on HP-UX|ConfiguringServerVolumesOnHP-UX]] If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on HP-UX Systems|EnablingAFSLoginOnHP-UXSystems]]. Proceed to Starting Server Programs. # Getting Started on IRIX Systems Begin by incorporating AFS modifications into the kernel. Either use the ml dynamic loader program, or build a static kernel. Then configure partitions to house AFS volumes. AFS supports use of both EFS and XFS partitions for housing AFS volumes. SGI encourages use of XFS partitions. You do not need to replace IRIX fsck program, because the version that SGI distributes handles AFS volumes properly. [[Loading AFS into the IRIX Kernel|LoadingAFSIntoTheIRIXKernel]] ## Configuring Server Volumes on IRIX Systems If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step. [[Configuring Server Volumes on IRIX|ConfiguringServerVolumesOnIRIX]] 1. If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on IRIX Systems|EnablingAFSLoginOnIRIXSystems]]. 1. Proceed to Starting Server Programs. # Getting Started on Linux Systems [[Loading AFS into the Linux Kernel|LoadingAFSIntoTheLinuxKernel]] ## Configuring Server Volumes on Linux Systems If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step. [[Configuring Server Volumes on Linux|ConfiguringServerVolumesOnLinux]] If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Linux Systems|EnablingAFSLoginOnLinuxSystems]]. Proceed to Starting Server Programs. # Getting Started on Solaris Systems [[Loading AFS into the Solaris Kernel|LoadingAFSIntoTheSolarisKernel]] ## Configuring the AFS-modified fsck Program on Solaris Systems Never run the standard fsck program on AFS server partitions. It discards AFS volumes. [[Configuring the AFS-modified fsck Program on Solaris Systems|ConfiguringTheAFS-modifiedFsckProgramOnSolarisSystems]] ## Configuring Server Volumes On Solaris If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step. [[Configuring Server Volumes on Solaris|ConfiguringServerVolumesOnSolaris]] If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Solaris Systems|EnablingAFSLoginOnSolarisSystems]]. Proceed to Starting Server Programs. # Starting Server Programs In this section you initialize the BOS Server, the Update Server, the controller process for NTPD, and the fs process. You begin by copying the necessary server files to the local disk. - Copy file server binaries to the local /usr/afs/bin directory. - On a machine of an existing system type, you can either load files from the AFS CD-ROM or use a remote file transfer protocol to copy files from an existing server machine of the same system type. To load from the CD-ROM, see the instructions just following for a machine of a new system type. If using a remote file transfer protocol, copy the complete contents of the existing server machine's /usr/afs/bin directory. - On a machine of a new system type, you must use the following instructions to copy files from the AFS CD-ROM. - - On the local /cdrom directory, mount the AFS CD-ROM for this machine's system type, if it is not already. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system documentation. - - Copy files from the CD-ROM to the local /usr/afs directory. `# cd /cdrom//dest/root.server/usr/afs` `# cp -rp * /usr/afs` 1. Copy the contents of the /usr/afs/etc directory from an existing file server machine, using a remote file transfer protocol such as ftp or NFS. If you use a system control machine, it is best to copy the contents of its /usr/afs/etc directory. If you choose not to run a system control machine, copy the directory's contents from any existing file server machine. 1. Change to the /usr/afs/bin directory and start the BOS Server (bosserver process). Include the -noauth flag to prevent the AFS processes from performing authorization checking. This is a grave compromise of security; finish the remaining instructions in this section in an uninterrupted pass. # cd /usr/afs/bin # ./bosserver -noauth & 1. If you run a system control machine, create the upclientetc process as an instance of the client portion of the Update Server. It accepts updates of the common configuration files stored in the system control machine's /usr/afs/etc directory from the upserver process (server portion of the Update Server) running on that machine. The cell's first file server machine was installed as the system control machine in Starting the Server Portion of the Update Server. (If you do not run a system control machine, you must update the contents of the /usr/afs/etc directory on each file server machine, using the appropriate bos commands.) By default, the Update Server performs updates every 300 seconds (five minutes). Use the -t argument to specify a different number of seconds. For the machine name argument, substitute the name of the machine you are installing. The command appears on multiple lines here only for legibility reasons. # ./bos create upclientetc simple \ "/usr/afs/bin/upclient \ [-t