Quick Beginnings
This chapter describes the type of instructions provided in
this guide and the hardware and software requirements for installing
AFS(R).
Before beginning the installation of your cell's first machine, read
this chapter and the material from the IBM AFS Administration Guide
listed in Recommended Reading List. It is also best to read through Installing the First AFS Machine before beginning the installation, so that
you understand the overall scope of the installation procedure.
Similarly, before installing additional server or client machines it is best
to read through Installing Additional Server Machines and Installing Additional Client Machines.
If you are already running a version of AFS, consult the upgrade
instructions in the IBM AFS Release Notes or contact the AFS
Product Support group before proceeding with the installation.
This guide describes two types of installation
procedures: initial procedures (such as installing the first AFS machine
or incorporating AFS into the kernel) and as-needed procedures (such as
installing additional server machines or client machines).
You must perform the following basic procedures to start using
AFS.
You must incorporate AFS modifications into the kernel of every AFS
file server and client machine. Depending on the operating system, you
either use a program for dynamic kernel loading, build a new static kernel, or
can choose between the two. For your convenience, the instructions for
incorporating AFS into the kernel appear in full in every chapter where you
need to use them.
You install the first AFS machine in your cell to function as both an
AFS server and client machine. You can disable the client functionality
after completing the installation, if you wish.
The first server machine in a cell performs several functions:
- It acts as the system control machine (if your AFS distribution
includes the required encryption files), distributing certain configuration
files to the other server machines in the cell
- It acts as the binary distribution machine for its system type,
distributing AFS binaries to other server machines of its system type
- It acts as the first database server machine, running the
server processes that maintain the AFS administrative databases
After you install server and client functionality, you complete other
procedures specific to the first machine, including setting up the top levels
of your cell's AFS filespace.
Upgrading the operating system requires you to take several steps to
protect data and AFS-modified binaries from being lost or overwritten.
For guidelines, see About Upgrading the Operating System.
See Installing an Additional File Server Machine.
See Installing Database Server Functionality and Removing Database Server Functionality.
See Installing Additional Client Machines.
See Appendix A, Building AFS from Source Code.
To develop the best understanding of the overall scope of an
installation procedure, read through the entire chapter or section that
describes it before performing any actions.
In addition, familiarity with some basic AFS concepts can make the
installation more efficient, because you understand better the purpose of the
steps. The following is a prioritized list of material to read before
installing the first AFS machine. At minimum, read the first chapter of
the IBM AFS Administration Guide. Then continue your reading
in the indicated order, as extensively as you can. It is more important
at this point to read the conceptual material in each section than the
instructions.
Selected Topics in the IBM AFS Administration Guide
- The chapter titled An Overview of AFS Administration
- Selected sections in the Administering Server Machines
chapter: Local Disk Files on a Server Machine, The Four
Roles for a Server Machine, Maintaining the Server CellServDB
File
- Selected sections in the Monitoring and Controlling Server
Processes chapter: Controlling and Checking Process
Status
- Selected sections in the Managing Server Encryption Keys
chapter: About Server Encryption Keys
- Selected sections in the Managing Volumes chapter:
About Volumes, Creating Read/write Volumes, Clones
and Cloning, Mounting Volumes
- Selected sections in the Administering Client Machines and the Cache
Manager chapter: Overview of Cache Manager
Customization, Configuration and Cache-related Files on the Local
Disk, Determining the Cache Type, Size, and Location
- Selected sections in the Managing Access Control Lists
chapter: Protecting Data in AFS
More Selected Topics in the IBM AFS Administration
Guide
- Selected sections in the Managing Volumes chapter:
Creating and Releasing Read-only Volumes (Replication),
Creating Backup Volumes
- Selected sections in the Administering the Protection Database
chapter: About the Protection Database
- Selected sections in the Administering User Accounts
chapter: The Components of an AFS User Account
- Selected sections in the Managing Administrative Privilege
chapter: An Overview of Administrative Privilege
You must comply with the following requirements to install AFS
successfully.
Log into the machine you are installing as the local superuser
root. When instructed, also authenticate with AFS as the
administrative user admin.
- You must have the AFS Binary Distribution for each system type you are
installing. Unless otherwise noted, the Binary Distribution includes
software for both client and server machines. If you are using the
CD-ROM version of the distribution, the machine you are installing must be
able to access the CD-ROMs, either through a local CD drive or via an
NFS(R) mount of a CD drive attached to a machine that is
accessible by network.
- All AFS machines that belong to a cell must be able to access each other
via the network.
- The machine must be running the standard, vendor-supplied version of the
operating system supported by the current version of AFS. The operating
system must already be installed on the machine's root partition.
- You must be familiar with the current operating system and disk
configuration of the machine you are installing.
- All hardware and non-AFS software on the machine must be functioning
normally.
- No critical processes can be running on the machine you are installing,
because you must reboot it during the installation.
- Cell configuration is simplest if the first machine you install has the
lowest IP address of any database server machine you currently plan to
install. If you later configure a machine with a lower IP address as a
database server machine, you must update the
/usr/vice/etc/CellServDB file on all of your cell's client
machines before the installation. For further discussion, see Installing Database Server Functionality.
- The partition mounted on the /usr directory must have at least
18 MB of disk space available for storing the AFS server binaries (stored by
convention in the /usr/afs/bin directory). If the machine is
also a client, there must be additional local disk space available, as
specified in Client Machine Requirements. The complete set of AFS binaries requires yet more
space, but they are normally stored in an AFS volume rather than on a
machine's local disk.
More significant amounts of space on the partition are required by the
administrative databases stored in the /usr/afs/db directory and
the server process log files stored in the /usr/afs/logs
directory. The exact requirement depends on many factors, such as the
size of your cell and how often you truncate the log files.
- There must be at least one partition (or logical volume, if the operating
system and AFS support them) dedicated exclusively to storing AFS
volumes. The total number and size of server partitions on all file
server machines in the cell determines how much space is available for AFS
files.
- The partition mounted on the /usr directory must have at least
4 MB of disk space available for storing the AFS client binaries and kernel
library files (stored by convention in the /usr/vice/etc
directory). The complete set of AFS binaries requires more space, but
they are normally stored in an AFS volume rather than on a machine's
local disk. For most system types, the instructions have you copy only
the one kernel library file appropriate for the machine you are
installing. If you choose to store all of the library files on the
local disk, the space requirement can be significantly greater.
- On a client machine that uses a disk cache, there must be enough free
space on the cache partition (by convention, mounted on the
/usr/vice/cache directory) to accommodate the cache. The
minimum recommended cache size is 10 MB, but larger caches generally perform
better.
- On a client machine that uses a memory cache, there must be at least 5 MB
of machine memory to devote to caching, but again more memory generally leads
to better performance. For further discussion, see the sections in Installing Additional Client Machines about configuring the cache.
The IBM AFS Release Notes for each AFS release
list the supported system types. Support for subsequent revisions of an
operating system often becomes available between AFS releases. The AFS
Product Support group can provide details.
It is the goal of the AFS Development and Product Support groups to support
AFS on a wide range of popular system types. Furthermore, each time an
operating system vendor releases a new general availability version of a
supported operating system, it is a goal to certify and support AFS on it
within a short time. Support can be delayed a bit longer if it is
necessary to generate completely new binaries.
It is not always possible to support AFS on every intermediate version of
an operating system or for certain processor types. In some cases,
platform limitations make certain AFS functionality (such as file server or
NFS/AFS translator functionality) unavailable on one or more platforms.
For a list of limitations, see the IBM AFS Release Notes or ask the
AFS Product Support group.
Whenever you upgrade an AFS machine to a different operating
system, you must take several actions to maintain proper AFS
functionality. These actions include, but are not necessarily limited
to, the following.
- Unmount the AFS server partitions (mounted at /vicepxx
directories) on all file server machines, to prevent the vendor-supplied
fsck program from running on them when you reboot the machine
during installation of the new operating system. Before upgrading the
operating system, it is prudent to comment out commands in the machine's
initialization file that remount the server partitions, to prevent them from
being remounted until you can replace the standard fsck program
with the AFS-modified version. The instructions in this guide for
installing AFS server machines explain how to replace the fsck
program.
- Protect the AFS-modified versions of commands and configuration files from
being overwritten by vendor-supplied versions. These include
vfsck (the AFS version of fsck), binaries for the UNIX
remote services such as inetd, and configuration files such as the
one for the Pluggable Authentication Module (PAM). After you have
successfully installed the operating system, remember to move the AFS-modified
commands and files back to the locations where they are accessed during normal
functioning.
- Reformat the server partitions to accommodate AFS-specific information, in
certain cases. The upgrade instructions that accompany the new AFS
binaries for an affected platform always detail the required procedure.
The AFS Binary Distribution includes a separate CD-ROM for
each supported system type, containing all AFS binaries and files for both
server and client machines. The instructions in this guide specify when
to mount the CD-ROM and which files or directories to copy to the local disk
or into an AFS volume.
If you are installing the first AFS machine in your cell,
proceed to Installing the First AFS Machine.
If you are installing an additional file server machine, or configuring or
decommissioning a database server machine, proceed to Installing Additional Server Machines.
If you are installing an additional client machine, proceed to Installing Additional Client Machines.
© IBM Corporation 2000. All Rights Reserved