![[Return to Library]](../books.gif)
![[Contents]](../toc.gif)
![[Previous Topic]](../prev.gif)
![[Bottom of Topic]](../bot.gif)
This file documents new features, upgrade procedures, and remaining limitations associated with the initial General Availability (GA) release of AFS(R) 3.6 (build level afs3.6 2.0).
| Note: | This document includes all product information available at the time the document was produced. For additional information that became available later, see the README.txt file included on the AFS CD-ROM. |
AFS 3.6 includes the following new features.
The AFS 3.6 distribution includes a single CD-ROM for each system type, which contains all AFS software. There is no CD-ROM labeled Encryption Files or Domestic Edition in the AFS 3.6 distribution.
Because they were produced before the change in export restrictions, the IBM AFS Administration Guide and IBM AFS Administration Reference still distinguish between United States and international editions of AFS. However, AFS customers in any country can ignore the distinction and use the United States instructions if they choose.
Note that smaller volumes are still more practical than large ones in general. The larger a volume, the longer it takes to move or clone it, which introduces greater potential for an outage to halt the operation before it completes.
AFS supports the following system types.
| alpha_dux40 | DEC AXP system with one or more processors running Digital UNIX 4.0d, 4.0e, or 4.0f |
| hp_ux110 | Hewlett-Packard system with one or more processors running the 32-bit or 64-bit version of HP-UX 11.0 |
| i386_linux22 | IBM-compatible PC with one or more processors running Linux kernel version 2.2.5-15 (the version in Red Hat Linux 6.0), 2.2.10, 2.2.12, 2.2.12-20 (the version in Red Hat Linux 6.1), 2.2.13, or 2.2.14 |
| rs_aix42 | IBM RS/6000 with one or more 32-bit or 64-bit processors running AIX 4.2, 4.2.1, 4.3, 4.3.1, 4.3.2, or 4.3.3 |
| sgi_65 | Silicon Graphics system with one or more processors running IRIX 6.5 or 6.5.4. Support is provided for the following CPU board types, as reported by the IRIX uname -m command: IP19, IP20, IP21, IP22, IP25, IP26, IP27, IP28, IP30, IP32 |
| sun4x_56 | Sun SPARCstation with one or more processors running Solaris 2.6 |
| sun4x_57 | Sun SPARCstation with one or more processors running the 32-bit or 64-bit version of Solaris 7 |
For a list of requirements for both server and client machines, see the chapter titled Installation Overview in the IBM AFS Quick Beginnings document.
The AFS Binary Distribution includes a separate CD-ROM for each supported operating system, containing all AFS binaries and files for both server and client machines, plus the documentation set in multiple formats. At the top level of the CD-ROM is a directory called Documentation plus a directory containing the system-specific AFS binaries, named using the values listed in Supported System Types. The CD-ROM for some operating systems has more than one system-specific directory; for example, the Solaris CD-ROM has sun4x_56 and sun4x_57.
The instructions in Upgrading Server and Client Machines to AFS 3.6 specify when to mount the CD-ROM and which files or directories to copy to the local disk or into an AFS volume.
The documents are also available online at <A HREF="http://www.transarc.com/Library/documentation/afs_doc.html">http://www.transarc.com/Library/documentation/afs_doc.html</A>. The documentation set includes the following documents:
Documents are provided in the following formats:
If you do not already have the Acrobat Reader program, you can download it for free at <A HREF="http://www.adobe.com/products/acrobat/readstep.html">http://www.adobe.com/products/acrobat/readstep.html</A>.
Adobe provides only an English-language version of Acrobat Reader for UNIX platforms. The program can display PDF files written in any language. It is the program interface (menus, messages, and so on) that is available in English only.
To make Reader's interface display properly in non-English language locales, use one of two methods to set the program's language environment to English:
If your Reader distribution includes the script, it is installed by convention as AcroRead_Dir/bin/acroread, where AcroRead_Dir is the installation directory for Reader files.
Add the following line to the script, directly after the #!/bin/sh statement:
LANG=C; export LANG
% setenv LANG C
Note that this setting affects all programs started in the command shell, with possibly undesirable results if they also use the LANG variable. The preceding method affects Reader only.
The following sections summarize limitations and requirements that pertain to all system types and to individual system types, and describe revisions to the AFS documents:
AFS supports up to 15 addresses on a multihomed file server machine. If more interfaces are configured with the operating system, AFS uses only the first 15.
AFS supports up to 32 addresses on a multihomed client machine. Do not configure more interfaces.
AFS supports up to 256 server (/vicep) partitions on a file server machine. This corresponds to directory names /vicepa through /vicepz and /vicepaa through /vicepiv.
The VLDB can store up to 255 server entries, each representing one file server machine (single- or multihomed). This effectively determines the maximum number of file server machines in the cell. To make room in the VLDB for new server entries, use the vos changeaddr command's -remove argument to remove the entries for decommissioned file server machines.
AFS supports a maximum file size of 2 GB.
AFS supports a maximum volume size of 8 GB. In AFS version 3.5 and earlier, the limit is 2 GB. There is no limit on partition size other than the one imposed by the operating system.
AFS supports a maximum disk cache size of 1 GB. In AFS version 3.1 and earlier, the limit is 700 MB.
The File Server (fileserver process) can use up to 128 threads, unless the operating system imposes a lower limit. Testing for the AFS 3.6 GA release indicates that HP-UX sometimes imposes a lower limit, depending on the resources available on a machine. See Product Notes for HP-UX Systems.
The File Server always reserves seven threads for special uses, so the maximum effective value for the fileserver command's -p argument is seven less than the actual limit. On most systems, the effective maximum is therefore 121.
The VLDB entry for a volume can accommodate a maximum of 13 site definitions. The site housing the read/write and backup versions of the volume counts as one site, and each read-only site counts as an additional site (even the read-only site defined on the same partition as the read/write site counts as a separate site).
AFS does not support use of the VxFS file system as either a client cache partition or server (/vicep) partition. It is acceptable to use both VxFS and AFS on the same machine, but the cache partition and all AFS server partitions must use a supported file system type such as UFS. See the following sections of this document for similar restrictions affecting particular operating systems.
For predictable performance, run the same version of an AFS server process on all server machines in a cell. For example, if you upgrade the Volume Location Server process on a database server machine to AFS 3.6, you must upgrade it on all of them. The upgrade instructions in Upgrading Server and Client Machines to AFS 3.6 have you upgrade the binaries for all server processes on all machines to the same version, and in general that is the best policy. Unless otherwise noted, it is acceptable to run different build levels of a major version on different machines (for example, AFS 3.5 build 3.0 on one machine and AFS 3.5 build 3.11 on another).
There is a single edition of AFS 3.6 for both North American and international customers. For details, see Summary of New Features.
The AFS 3.6 Backup System can communicate with one XBSA server, the Tivoli Storage Manager (TSM). There are several requirements and limitations associated with its use, as detailed in Product Notes for Use of TSM.
If using a Netscape browser to read the HTML version of an AFS document, use version 4.0 or higher. Some fonts used in the documents possibly do not display properly in earlier versions.
The user interface to the Adobe Acrobat Reader program for displaying PDF files works correctly only when the program's language environment is set to English. Users in non-English language locales probably need to adjust the language setting. See Accessing the AFS Binary Distribution and Documentation.
AFS does not support version 6 of the Internet Protocol (IPv6). You must continue to specify the IPv4 protocol names udp and tcp in the entries for AFS-modified services in the inetd configuration file, rather than the IPv6 names upd6 and tcp6. If you use the IPv6 version, the AFS-modified inetd daemon cannot locate the service and does not open the service's port.
The inetd configuration file included with some operating system revisions possibly specifies IPv6 protocols by default. You must modify or replace the file in order to use the AFS-modified version of remote services.
If the name of every file system element (file, link, or subdirectory) in a directory is 16 characters or more, then when there are about 31,700 elements it becomes impossible to create any more elements with long names. It is still possible to create elements with names shorter than 16 characters. This limitation is due to the way AFS implements directories. For a more detailed explanation, contact your AFS product support representative.
Only members of the system:administrators group can turn on the setuid or setgid mode bit on an AFS file or directory. However, AFS generates an error message only when a regular user attempts to set the bit on a directory. Attempts on a file fail silently.
The documentation specifies the following syntax for creating an authentication-only account (entries in the Authentication and Protection Databases only) by using an add instruction in the uss bulk template file:
add username[:]
However, you must in fact follow the username value with two colons for the uss bulk command to create the account:
add username::
The Backup Server locks the Backup Database as it performs the backup savedb command, which can take a long time. Because other backup operations cannot access the database during this time, they appear to hang. Avoid running other backup operations after issuing the backup savedb command.
Actually, this limitation applies to any operation that locks the Backup Database for a significant amount of time, but most other operations do not. In any case, running the backup savedb command is appropriate only in the rare case when the Backup Database is corrupted, so this limitation usually does not have a significant impact.
The NFS/AFS Translator does not always perform well under heavy load. Sometimes the translator machine hangs, and sometimes NFS client machines display the following error message.
NFS Stale File Handle
The AFS distribution does not include the sample files referred to in the chapter of the IBM AFS Administration Guide about the package program (the files formerly installed by convention in the etc, lib, and src subdirectories of the /afs/cellname/wsadmin directory). IBM AFS Quick Beginnings therefore does not include instructions for installing the sample files. If you wish to use the package program and the discussion in the IBM AFS Administration Guide is not sufficient to guide you, contact your AFS product support representative for assistance.
To use the klog command's -setpag flag, you must install the indicated AIX APAR (Authorized Program Analysis Report), available from IBM, on a machine running the indicated AIX version:
To determine if the APAR is installed, issue the following command:
% instfix -i -k APAR_identifier
IBM provides an APAR for the indicated (latest) AIX versions only. Therefore, the -setpag flag does not work correctly on machines running the base level of AIX 4.2 or 4.3, or AIX 4.3.1 or 4.3.2.
If version 4.3.3.0 or higher of the AIX bos.rte.security fileset is installed (usually true on a machine using the AIX 4.3.3 kernel), you must modify the procedure documented in IBM AFS Quick Beginnings for enabling integrated AFS login. Instead of editing the /etc/security/login.cfg file, you edit the /usr/lib/security/methods.cfg file.
To determine which version of the bos.rte.security fileset is installed, issue the following command:
# lslpp -L bos.rte.security
The change affects Step 3 in the section titled Enabling AFS Login on AIX Systems in each of two chapters in IBM AFS Quick Beginnings: Installing the First AFS Machine and Installing Additional Client Machines. For the complete text of the modified step, see Documentation Notes.
AFS does not support the use of machines running the base level of AIX 4.2 as NFS/AFS Translator machines. The AFS distribution does not include the required kernel extensions file, formerly installed by convention as /usr/vice/etc/dkload/afs.ext.trans. Do not set the NFS variable to the value $NFS_NFS in the AFS initialization script (by convention, /etc/rc.afs).
Machines running AIX 4.2.1 and higher are supported as NFS/AFS Translator machines. They use the afs.ext.iauth kernel extensions file instead.
A machine running AIX 4.2.1 or higher cannot act as both an NFS/AFS Translator and a NFS/DFS Gateway Server at the same time, because both translation protocols must have exclusive access to the AIX iauth interface. An attempt by either file system to access the iauth interface when the other file system is already using it fails with an error message.
Do not run NFS Version 3 software on NFS client machines that use an NFS/AFS Translator machine running AIX. The NFS3 client software uses the readdir+ NFS command on directories, which can cause excessive volume lookups on the translator machine. This can lead to timeouts, especially when used in the /afs directory or other directories with many volume mount points. Use NFS Version 2 instead.
AFS does not support use of AIX's Large File Enabled Journalled File System as an AFS server (/vicep) partition. If you configure a partition that uses that file system as an AFS server partition, the File Server ignores it and writes the following message to the /usr/afs/logs/FileLog file:
/vicepxx is a big files filesystem, ignoring it
AFS supports use of the Large File Enabled Journalled File System as the cache partition on a client machine.
The AIX secondary authentication system does not support setting the PASSWORD_EXPIRES environment variable during login.
The chuser, chfn, and chsh commands are inoperative on AFS machines running AIX. AFS authentication uses the AIX secondary authentication system, and sets the registry variable in the /etc/security/user file to DCE for the default user. That is, the setting is
registry = DCE
as described in the sections of IBM AFS Quick Beginnings that discuss enabling AFS login on AIX systems. However, when the registry variable has any value other than registry = files, AIX does not allow edits to /etc/passwd and related files, and so disallows the chuser, chfn and chsh commands. Attempts to edit entries by running these commands on the command line result in error messages like the following.
You can only change the HOME directory on the name server.
You can only change the User INFORMATION on the name server.
You can only change the Initial PROGRAM on the name server.
From within SMIT, using the chuser function results in an error message like the following:
3004-716: You can only change the HOME directory on the name server
It is not possible for AFS Development to alter this behavior, because AIX imposes the restriction. Sites that wish to run these commands must develop a solution appropriate for their needs.
AFS does not support use of Digital UNIX machines as NFS/AFS Translator machines.
AFS does not support use of Digital UNIX's Advanced File System (AdvFS) as either a client cache partition or a server (/vicep) partition. It is acceptable to use both AdvFS and AFS on the same machine, but the cache partition and all AFS server partitions must be UFS partitions.
AFS does not function correctly on a Digital UNIX machine when real-time preemption of system calls is enabled in the kernel. Do not enable this feature in any manner, including the following:
options RT_PREEMPT_OPT
rt_preempt_opt=1 rt-preempt-opt=1
Also, AFS does not function correctly when the value of the kernel lockmode option is other than 0 (zero, the default) or 2. Lock mode values 1, 3, and 4 are unsupported because they imply that real-time preemption is enabled (indeed, enabling real-time preemption sets the lock mode to 1 automatically).
Building AFS from source for Digital UNIX requires that certain header files (such as cpus.h) reside in the local /usr/sys/AFS directory. This directory exists only if you have previously incorporated AFS modifications into the kernel of the machine on which you are performing the compilation. Otherwise, the required header files reside only in the local directory called /usr/sys/machine_name.
If the /usr/sys/AFS directory does not exist, issue the following command to create it as a link:
# ln -s /usr/sys/machine_name /usr/sys/AFS
When the compilation is complete, remove the link.
AFS does not support use of HP-UX 11.0 machines as NFS/AFS Translator machines.
The AFS 3.6 version of the File Server uses the native HP-UX threading package. When upgrading to the new File Server on a machine that previously ran File Server version 3.5 or earlier, you must also upgrade the AFS kernel extensions to the AFS 3.6 version.
For instructions on upgrading server and client machines, see Upgrading Server and Client Machines to AFS 3.6.
On some machines, HP-UX reduces the number of threads available to the File Server to fewer than the AFS default of 128. To determine the maximum number of threads available to the File Server (or any single process) on an HP-UX machine, issue the following command:
% getconf _SC_THREAD_THREADS_MAX
As on other system types, the HP-UX File Server reserves seven threads for special uses, so the maximum effective value for the fileserver command's -p argument is seven less than the number reported by the getconf command.
For AFS authentication to work correctly for a service, all entries for the service in the HP-UX PAM configuration file (/etc/pam.conf by convention) must have the value optional in the third field, as specified in IBM AFS Quick Beginnings. However, when you make the login entry that invokes the pam_dial_auth module optional in this way, it can mean that PAM succeeds (the user can login) even when the user does not meet all of the pam_dial_auth module's requirements. This is not usually considered desirable.
If you do not use dial-up authentication, comment out or remove the entry for the login service that invokes the pam_dial_auth module. If you do use dial-up authentication, you must develop a configuration that meets your needs; consult the HP-UX documentation for PAM and the pam_dial_auth module.
You must install Hewlett-Packard patch PHCO_18572 to enable HP-UX's standard PAM to change to a user's home directory during login. The patch is accessible for download via the UNIX File Transfer Protocol (ftp) at the following address:
ftp://hpatlse.atl.hp.com/hp-ux_patches/s700_800/11.X/PHCO_18572
The patch is also available from HP Electronic Support Centers at the following URLs.
The AFS kernel dump program, kdump, cannot retrieve kernel information from an IRIX system on which the dynamic kernel loader, ml, was used to load AFS extensions. The kdump program can read only static kernels into which AFS is built.
The AFS distribution for IRIX machines does not include AFS-modified versions of any of the remote (r*) commands except inetd.afs. Silicon Graphics has already modified the IRIX versions of the remote commands to be compatible with AFS.
Do not run the IRIX File System Reorganizer (fsr program) on a client cache partition (/usr/vice/cache directory or equivalent) or AFS server partition (/vicep directory). The program can corrupt or remove AFS data.
The IRIX 6.5 distribution includes and starts the timed time-synchronization daemon by default. If you want to use the runntp program and the Network Time Protocol Daemon (NTPD) on AFS server machines, as documented in IBM AFS Quick Beginnings, issue the following commands. They disable the timed daemon and remove it from the machine's startup sequence.
# /etc/chkconfig -f timed off # /sbin/killall timed
The IRIX 6.5 distribution includes the clogin program as the default login utility. This graphical utility does not grant AFS tokens. If you want your users to obtain tokens during login, you must disable the clogin program and substitute either the standard command-line login program or the xdm graphical login utility, both of which grant AFS tokens if AFS modifications have been incorporated into the kernel. Issue the following command to disable the clogin program.
# /etc/chkconfig -f visuallogin off
The General Availability release of AFS 3.6 supports Red Hat Software's Linux 6.0 (which incorporates kernel version 2.2.5-15) and Linux 6.1 (which incorporates kernel version 2.2.12-20). The distribution also includes AFS kernel extensions for kernel versions 2.2.10, 2.2.12, 2.2.13, and 2.2.14. The AFS initialization script included in the AFS 3.6 distribution automatically selects the appropriate kernel extensions for the kernel version in use on the local machine.
Red Hat Linux 6.0 and 6.1 include a compiled kernel, but for the other supported kernel versions you must obtain kernel source and compile the kernel yourself. In this case, you must use version 2.7.2.3 or higher of the gcc program, which is part of the Linux distribution. Do not use other compilers.
The Linux kernel-building tools by default create a symmetric multiprocessor (SMP) kernel, which can run on both uniprocessor and multiprocessor machines. However, a uniprocessor machine generally performs best with a uniprocessor kernel.
You can obtain Linux kernel source via the UNIX File Transfer Protocol (ftp) at ftp.kernel.org or one of its mirror sites. There is also kernel upgrade information at <A HREF="http://www.kernel.org">http://www.kernel.org</A>.
For correct AFS performance, the operating system must use the C library called libc6 (or glibc2), rather than libc5 (glibc1).
If using an SMP kernel or a uniprocessor kernel configured to use more than 1 GB of memory, you must use a modified version of the insmod program. You do not need the modified program if using a standard uniprocessor kernel.
You can download the modified insmod program at the following URLs:
AFS does not support the use of Linux machines as NFS/AFS Translator machines.
The Authentication Server running on a Linux machine creates and writes messages to the /usr/afs/logs/AuthLog file, just as on other system types. However, it does not create or use the two files which constitute the auxiliary AuthLog database on other system types (AuthLog.dir and AuthLog.pag). The kdb command is therefore inoperative on Linux machines. The auxiliary database is useful mostly for debugging and is not required for normal operations.
For the afsmonitor, scout and fms programs to work properly, the dynamic library /usr/lib/libncurses.so must be installed on the machine. It is available in most Linux distributions.
As noted in Upgrading Server and Client Machines to AFS 3.6, the 64-bit version of Solaris 7 uses a different location for kernel extension library files than previous versions of Solaris: /kernel/fs/sparcv9/afs. The 32-bit version of Solaris 7 uses the same location as Solaris 2.6, /kernel/fs/afs.
As part of replacing the standard fsck program on an AFS file server machine that runs Solaris, you make two changes in the /sbin/mountall script. If you use Solaris 7 and apply SunSoft Patch 10654, it replaces the /sbin/mountall script. This has two implications:
For more details, see Documentation Notes.
For AFS authentication to work correctly for a service, all entries for the service in the Solaris PAM configuration file (/etc/pam.conf by convention) must have the value optional in the third field, as specified in IBM AFS Quick Beginnings. However, when you make the login entry that invokes the pam_dial_auth module optional in this way, it can mean that PAM succeeds (the user can login) even when the user does not meet all of the pam_dial_auth module's required conditions. This is not usually considered desirable.
If you do not use dial-up authentication, comment out or remove the entry for the login service that invokes the pam_dial_auth module. If you do use dial-up authentication, you must develop a configuration that meets your needs; consult the Solaris documentation for PAM and the pam_dial_auth module.
The AFS Development group has filed a Request for Enhancement (RFE #4122186) with SunSoft for a design change that eliminates this problem with the pam_dial_auth module. There is no projected solution date. For further information, contact your AFS product support representative.
There were several defects in the initial release of the Solaris 2.6 implementation of the Common Desktop Environment (CDE). They prevented integrated AFS login from working consistently under CDE. SunSoft now provides patches that correct the problems. You must install them in order to obtain support for use of CDE from your AFS product support representative.
Use the following command to determine which version of CDE you are running:
% pkginfo -l SUNWdtdte
As noted in Summary of New Features, the IBM AFS Administration Guide and IBM AFS Administration Reference distinguish between United States and international editions of AFS, because the documents were produced before a relaxation of United States government export restrictions. AFS 3.6 includes just one edition. AFS customers in any country can ignore the documented distinction between editions and use the United States instructions if they choose.
The AFS documents refer you to the AFS Product Support group for technical assistance with AFS problems and questions. This is intended to be a generic term. To learn how to obtain technical support, consult your AFS license agreement or other materials from your AFS vendor.
If version 4.3.3.0 or higher of the AIX bos.rte.security fileset is installed (usually true on a machine using the AIX 4.3.3 kernel), edit the /usr/lib/security/methods.cfg file instead of the /etc/security/login.cfg file as documented in IBM AFS Quick Beginnings.
The change affects Step 3 in the section titled Enabling AFS Login on AIX Systems in each of two chapters in IBM AFS Quick Beginnings: Installing the First AFS Machine and Installing Additional Client Machines. The corrected text follows.
Create or edit the DCE and AFS stanzas in one of two files on the local disk:
Edit the stanzas as follows:
If you use the AFS Authentication Server (kaserver process):
DCE:
program = /usr/vice/etc/afs_dynamic_auth
If you use a Kerberos implementation of AFS authentication:
DCE:
program = /usr/vice/etc/afs_dynamic_kerbauth
If you use the AFS Authentication Server (kaserver process):
AFS:
program = /usr/vice/etc/afs_dynamic_auth
If you use a Kerberos implementation of AFS authentication:
AFS:
program = /usr/vice/etc/afs_dynamic_kerbauth
In two sections of IBM AFS Quick Beginnings, there are instructions for editing the /sbin/mountall script on Solaris machines as part of replacing the standard fsck program. The two sections are Configuring the AFS-modified fsck Program on Solaris Systems in the chapter about the first AFS machine and Getting Started on Solaris Systems in the chapter about additional server machines.
If you use Solaris 7 and apply SunSoft Patch 10654, it replaces the /sbin/mountall script. In the replacement script, the appearance of one of the sections of code that you must alter is different than in the original script and as specified in IBM AFS Quick Beginnings, which is as follows:
# For fsck purposes, we make a distinction between ufs and
# other file systems
#
if [ "$fstype" = "ufs" ]; then
ufs_fscklist="$ufs_fscklist $fsckdev"
saveentry $fstype "$OPTIONS" $special $mountp
continue
fi
In the replacement script, the code is instead similar to the following:
# For fsck purposes, we make a distinction between ufs and
# other file systems. Here we check that the file system is
# not mounted using fsck -m before adding it to the list to
# be checked
#
if [ "$fstype" = "ufs" ]; then
/usr/sbin/fsck -m -F $fstype $fsckdev >/dev/null 2>&1
if [ $? != 33 ]; then
ufs_fscklist="$ufs_fscklist $fsckdev"
saveentry $fstype "$OPTIONS" $special $mountp
continue
else
echo "$fsckdev already mounted"
continue
fi
fi
You still need to change the first if statement (the one directly after the comment) to check for both the UFS and AFS file system types, as specified in IBM AFS Quick Beginnings:
if [ "$fstype" = "ufs" -o "$fstype" = "afs" ]; then
The section of IBM AFS Quick Beginnings titled Storing AFS Documents in AFS (in the chapter about the first AFS machine) incorrectly describes the organization of the top-level Documentation directory on the AFS CD-ROM. It states that there is a subdirectory for each document format. Instead, there is a subdirectory for each language in which the documents are available, named using the following codes:
de_DE for German
en_US for United States English
es_ES for Spanish
ko_KR for Korean
pt_BR for Brazilian Portuguese
zh_CN for Simplified Chinese
zh_TW for Traditional Chinese
In each language directory is a subdirectory for each available document format. In each format directory is a subdirectory for each document. For example, the path on the CD-ROM to the English-language HTML version of the IBM AFS Quick Beginnings is Documentation/en_US/HTML/QkBegin.
| Note: | Not all documents are available in every language, as determined by the IBM translation center responsible for each language. All documents are available in English. |
Assuming that you want to install the documentation for one language only, substitute the following text for Step 5 in the instructions in Storing AFS Documents in AFS:
Copy the AFS documents in one or more formats from the CD-ROM into subdirectories of the /afs/cellname/afsdoc directory. Repeat the commands for each format.
# mkdir format_name # cd format_name # cp -rp /cdrom/Documentation/language_code/format .
If you choose to store the HTML version of the documents in AFS, note that in addition to a subdirectory for each document there are several files with a .gif extension, which enable readers to move easily between sections of a document. The file called index.htm is an introductory HTML page that contains a hyperlink to each of the documents. For online viewing to work properly, these files must remain in the top-level HTML directory (the one named, for example, /afs/cellname/afsdoc/HTML).
The IBM AFS Administration Guide and IBM AFS Administration Reference incorrectly state that the value 255 acts as a wildcard in IP addresses that appear in the NetRestrict file (client or server version). Wildcarding does not work and is not supported. For corrected documentation, see NetRestrict (client version) and NetRestrict (server version).
The IBM AFS Administration Guide and IBM AFS Administration Reference do not document the interoperation of the AFS Backup System and the Tivoli Storage Manager (TSM), because support for TSM was added after the documents were produced.
For a complete description of the new TSM-related features and configuration procedures, see Support for Backup to TSM and the indicated reference pages:
The IBM AFS Administration Guide and IBM AFS Administration Reference incorrectly state that the vos delentry command accepts the name or volume ID number of any type of volume (read/write, read-only, or backup). In fact, it accepts only a read/write volume's name or ID. Because a single VLDB entry represents all versions of a volume (read/write, readonly, and backup), the command removes the entire entry even though only the read/write volume is specified. For complete documentation, see vos delentry.
This section briefly describes commands, command options, and functionality that are new or changed in AFS 3.6. Unless otherwise noted, the IBM AFS Administration Guide and IBM AFS Administration Reference include complete documentation of these items.
AFS 3.6 includes the new fs flushmount command. The command's intended use is to discard information about mount points that has become corrupted in the cache. The next time an application accesses the mount point, the Cache Manager must fetch the most current version of it from a File Server. Data cached from files or directories in the volume is not affected. The only other way to discard the information is to reinitialize the Cache Manager by rebooting the machine.
Symptoms of a corrupted mount point included garbled output from the fs lsmount command, and failed attempts to change directory to or list the contents of the volume root directory represented by the mount point.
AFS 3.6 adds the following new options and functionality to existing commands and files.
Several backup commands and configuration files include new features that support backup to XBSA servers such as TSM. See New Command and File Features that Support TSM.
There are new instructions in the CFG_tcid file that apply to all types of backup media: CENTRALLOG, GROUPID, LASTLOG, MAXPASS, and STATUS. (There are also new instructions that apply only to XBSA servers, as documented in New Command and File Features that Support TSM.)
The new instructions are not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See CFG_tcid. (Note that this is a new way of referring to this file, called CFG_device_name in the IBM AFS Administration Guide and IBM AFS Administration Reference. For a Tape Coordinator that communicates with an XBSA server, the variable part of the filename is a port offset number rather than a device name, so the more generic tcid is a better description of possible values in this part of the filename.)
The backup addvolset command has a new -temporary flag. A temporary volume set is not recorded in the Backup Database and exists only during the lifetime of the interactive session in which it is created.
There are new options to the backup deletedump command: the -groupid argument specifies the group ID number associated with the dump records to delete, and the -noexecute flag displays a list of the records to be deleted rather than actually deleting them. (There are also new options that apply only to records for data dumped to an XBSA server, as documented in New Command and File Features that Support TSM.)
The new options are not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See backup deletedump.
When both the -id and -verbose options to the backup dumpinfo command are provided, the output is divided into several sections. In the first section, headed by the label Dump, the new Group id field replaces the id field that previously appeared about halfway down the list of fields (the first field in the section is still labeled id). The Group id field reports the dump's group ID number, which is recorded in the Backup Database if the GROUPID instruction appears in the Tape Coordinator's /usr/afs/backup/CFG_tcid file when the dump is created.
(The command's output also includes a new message that reports whether the dump data is stored on an XBSA server, as detailed in New Command and File Features that Support TSM.)
The new output is not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See backup dumpinfo.
The AFS 3.6 BOS Server sends additional information to notifier programs when an AFS server process exits. The bnode_proc structure now includes the lastExit field, which reports the exit code associated with the process's most recent exit. Previously, the only information about exit codes available to the notifier program was in the bnode structure's errorCode field, which records the exit code generated when the process last exited due to an error. The BOS Server does not clear the errorCode field, so the value set at the last exit due to error is reported even for exits that are not due to error.
If your notifier program currently checks the errorCode field but you really want a notification only when the most recent exit is due to an error, change the program to check the lastExit field in the bnode_proc structure instead. An error code appears in the lastExit field only if the most recent exit really was due to an error (in which case the same code also appears in the errorCode field).
The bos create command's reference page in the IBM AFS Administration Reference describes all of the fields that the BOS Server can include in the bnode_proc and bnode structures. As noted there, the BOS Server does not necessarily include every field in the structures it sends to a notifier program, because some of them are for internal use. For best results, the notifier program must correctly handle the absence of a field that it expects to find.
As in AFS 3.5, the AFS 3.6 Authentication Server does not require that you disable authorization checking on its database server machine before it returns the octal digits that constitute the encrypted password or key stored in an Authentication Database entry, which was the requirement with earlier versions of AFS. Instead, it always returns the octal digits, as long as the connection between the kas command interpreter and Authentication Server is encrypted. AFS 3.5 introduced the -showkey flag to make the kas examine command display the octal digits.
This change in requirements creates a potential security exposure, however, in that earlier versions of the kas examine command always display the octal digits (instead of a checksum) when directed to an AFS 3.5 or 3.6 Authentication Server. To eliminate this exposure, in AFS 3.6 the Authentication Server returns octal digits only for a principal that has the ADMIN flag in its Authentication Database entry.
The main effect of the new requirement is that only administrators can include the -showkey flag on the AFS 3.6 kas examine command. It does not effectively change the privilege required to display the octal digits when using versions of the kas examine command before AFS 3.5 Patch 2 (build level afs3.5 3.17), because it was assumed with earlier versions that only administrators were able to disable authorization checking. It also does not affect the automated installation and configuration tool provided for AFS for Windows, which still can be used only by administrators.
The AFS 3.6 version of the vos delentry command accepts only read/write volume names or volume ID numbers as values for its -id or -prefix arguments. The new restriction is not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See vos delentry.
AFS 3.6 introduces support for backing up AFS data to media managed by the Tivoli Storage Manager (TSM), a third-party backup program which implements the Open Group's Backup Service application programming interface (API), also called XBSA. TSM was formerly called the ADSTAR Distributed Storage Manager, or ADSM. It is assumed that the administrator is familiar with TSM; explaining TSM or XBSA concepts or terminology is beyond the scope of this document.
See the following subsections:
The AFS 3.6 version of the following commands and configuration files include new options or instructions to support backup to TSM.
Several new or modified instructions in the CFG_tcid file support backup of AFS data to XBSA servers such as TSM: MGMTCLASS, NODE, PASSFILE, PASSWORD, SERVER, and TYPE. (There are also new instructions that apply to automated tape devices and backup data files as well as XBSA servers, as detailed in New File or Command Functionality.)
The new instructions are not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See CFG_tcid. (Note that this is a new way of referring to this file, called CFG_device_name in the IBM AFS Administration Guide and IBM AFS Administration Reference. For a Tape Coordinator that communicates with XBSA server such as TSM, the variable part of the filename is a port offset number rather than a device name, so the more generic tcid is a better description of possible values in this part of the filename.)
The backup deletedump command has new options that enable you to delete dump records stored on an XBSA server such as TSM, as well as the corresponding Backup Database records:
There are also two new options that apply to automated tape devices and backup data files as well as XBSA servers, as detailed in New File or Command Functionality.
The new options are not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See backup deletedump.
When the -id option is provided to the backup dumpinfo command, the following line appears in the output if a TSM server was the backup medium for the dump:
Backup Service: TSM: Server: hostname
where hostname is the name of the TSM server machine. (There is also new output for dumps to all types of backup media, as detailed in New File or Command Functionality.)
The new output is not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See backup dumpinfo.
If the Tape Coordinator is communicating with a TSM server, the following message appears last in the output from the backup status command:
TSM Tape coordinator
The new output is not documented in the IBM AFS Administration Guide or IBM AFS Administration Reference. See backup status.
To communicate with a TSM server, the Tape Coordinator must run on a machine that uses one of the following operating systems: AIX 4.3 or higher, Solaris 2.6, Solaris 7.
The AFS 3.6 Tape Coordinator uses version 3.7.1 (Version 3, Release 7) of the TSM client API. Use of other versions of the API is not supported or tested. For instructions on obtaining the API, see Configuring the Backup System and TSM.
To communicate with a TSM server, a Tape Coordinator must have a CFG_tcid file that includes the following fields: SERVER, TYPE, and PASSWORD or PASSFILE. For instructions on creating the file, see Configuring the Backup System and TSM.
Do not create an entry in the /usr/afs/backup/tapeconfig file for a Tape Coordinator that communicates with an XBSA server such as TSM. Creating the CFG_tcid file is sufficient.
In AFS 3.6, there is one acceptable value for the TYPE instruction in the CFG_tcid file: tsm.
If the NODE instruction is not included in the /usr/afs/backup/CFG_tcid file, the TSM dsm.sys file must define a value for the NODENAME variable.
The following commands are not supported for XBSA servers such as TSM. In other words, the commands fail with an error message when their -port argument specifies a Tape Coordinator that communicates with an XBSA server:
In addition, the -append flag to the backup dump command is ignored when the -port argument specifies a Tape Coordinator that communicates with an XBSA server (the notion of appended dumps does not apply to XBSA servers).
Perform the following steps to configure TSM and the AFS Backup System for interoperation.
| Note: | You possibly need to perform additional TSM configuration procedures unrelated to AFS. See the TSM documentation. |
% su root Password: root_password
ftp> bin
ftp> cd storage/tivoli-storage-management-maintenance/client/v3r7
ftp> cd AIX/v371 ftp> get tivoli.tsm.client.api.aix43.32bit
ftp> cd Solaris/v371 ftp> get IP21804.tar.Z
# uncompress IP21804.tar.Z | tar xvf -
Do not put a final slash ( / ) on the directory name. Examples of appropriate values are /opt/tivoli/tsm/client/api/bin on Solaris machines and /usr/tivoli/tsm/client/api/bin on AIX machines.
ServerName machine_name
CommMethod tcpip
TCPPort TSM_port
TCPServerAddress full_machine_name
PasswordAccess prompt
Compression yes
The following is an example of appropriate values:
ServerName tsm3
CommMethod tcpip
TCPPort 1500
TCPServerAddress tsm3.abc.com
PasswordAccess prompt
Compression yes
ServerName machine_name
tapeprompt no
compressalways yes
# backup addhost <tape machine name> <TC port offset>
where
For more detailed descriptions of the instructions, and of other instructions you can include in the configuration file, see CFG_tcid.
This section explains how to upgrade server and client machines from AFS 3.5 or AFS 3.6 Beta to AFS 3.6. Before performing an upgrade, please read all of the introductory material in this section.
If you are installing AFS for the first time, skip this chapter and refer to the IBM AFS Quick Beginnings document for AFS 3.6.
AFS provides backward compatibility to the previous release only: AFS 3.6 is certified to be compatible with AFS 3.5 but not necessarily with earlier versions.
| Note: | This document does not provide instructions for upgrading from AFS 3.4a or earlier directly to AFS 3.6. A file system conversion is required on some system types. See the AFS Release Notes for AFS 3.5 and contact your AFS product support representative for assistance. |
You must meet the following requirements to upgrade successfully to AFS 3.6:
Use one of the following methods to obtain the AFS distribution of each system type for which you are licensed.
It is conventional to store many of the programs and files from the AFS binary distribution in a separate volume for each system type, mounted in your AFS filespace at /afs/cellname/sysname/usr/afsws. These instructions rename the volume currently mounted at this location and create a new volume for AFS 3.6 binaries.
Repeat the instructions for each system type.
% vos create <machine name> <partition name> sysname.3.6 -maxquota 0
% fs mkmount /afs/.cellname/temp sysname.3.6
% cd /cdrom/sysname
% cd temp_afs36_dir
% cp -rp bin /afs/.cellname/temp
% cp -rp etc /afs/.cellname/temp
% cp -rp include /afs/.cellname/temp
% cp -rp lib /afs/.cellname/temp
% cp -rp root.client /afs/.cellname/temp
If you do not plan to retain the old volume, you can substitute the vos remove command in this step.
% vos rename sysname.usr.afsws sysname.usr.afsws.extension
% vos rename sysname.3.6 sysname.usr.afsws
% fs rmmount /afs/.cellname/temp
AFS 3.6 supports the 64-bit version of HP-UX 11.0 and Solaris 7. To upgrade from the 32-bit version, you possibly need to reinstall the operating system completely before installing AFS 3.6. When performing any operating system upgrade, you must take several actions to preserve AFS functionality, including the following:
The instructions in this section explain how to use the Update Server to distribute server binaries from a binary distribution machine of each system type.
Repeat the steps on each binary distribution machine in your cell. If you do not use the Update Server, repeat the steps on every server machine in your cell. If you are copying files from the AFS product tree, the server machine must also be configured as an AFS client machine.
% su root Password: root_password
# mkdir /usr/afs/bin.36
# cd /cdrom/sysname/root.server/usr/afs/bin
# cd temp_afs36_dir/root.server/usr/afs/bin
# cp -p * /usr/afs/bin.36
# cd /usr/afs
# mv bin bin.old
# mv bin.36 bin
Repeat the following instructions on each server machine. Perform them first on the database server machine with the lowest IP address, next on the other database server machines, and finally on other server machines.
The AFS data stored on a server machine is inaccessible to client machines during the upgrade process, so it is best to perform it at the time and in the manner that disturbs your users least.
If you do not use binary distribution machines, perform the instructions in Distributing Binaries to Server Machines on this machine.
% su root Password: root_password
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
| Note: | Some files in the /usr/vice/etc directory, such as the AFS initialization file (called afs.rc on many system types), do not necessarily need to change for a new release. It is a good policy to compare the contents of the distribution directory and the /usr/vice/etc directory before performing the copying operation. If there are files in the /usr/vice/etc directory that you created for AFS 3.5 or 3.6 Beta and that you want to retain, either move them to a safe location before performing the following instructions, or alter the following instructions to copy over only the appropriate files. |
# cp -p usr/vice/etc/* /usr/vice/etc # cp -rp usr/vice/etc/C /usr/vice/etc
If you have not yet incorporated AFS into the machine's authentication system, perform the instructions in the section titled Enabling AFS Login for this system type in the IBM AFS Quick Beginnings chapter about configuring client machines. If this machine was running the same operating system revision with AFS 3.5 or AFS 3.6 Beta, you presumably already incorporated AFS into its authentication system.
First issue the following command to shut down the server processes, preventing them from restarting accidently before you incorporate the AFS 3.6 extensions into the kernel.
# bos shutdown <machine name> -localauth -wait
Then perform the instructions in Incorporating AFS into the Kernel and Enabling the AFS Initialization Script, which have you reboot the machine. Assuming that the machine's AFS initialization script is configured to invoke the bosserver command as specified in IBM AFS Quick Beginnings, the BOS Server starts itself and then the other AFS server processes listed in its local /usr/afs/local/BosConfig file.
There are two circumstances in which you must incorporate the kernel extensions and reboot now rather than later:
In any other circumstances, you can choose to upgrade the kernel extensions later. Choose one of the following options:
# bos restart <machine name> -localauth -bosserver
# bos prune <machine name> -bak -old -localauth
Step 5 of Distributing Binaries to Server Machines had you move the previous version of the binaries to the /usr/afs/bin.old directory. You can also remove that directory on any machine where you created it.
# rm -rf /usr/afs/bin.old
% su root Password: root_password
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
| Note: | Some files in the /usr/vice/etc directory, such as the AFS initialization file (called afs.rc on many system types), do not necessarily need to change for a new release. It is a good policy to compare the contents of the distribution directory and the /usr/vice/etc directory before performing the copying operation. If there are files in the /usr/vice/etc directory that you created for AFS 3.5 or 3.6 Beta and that you want to retain, either move them to a safe location before performing the following instructions, or alter the following instructions to copy over only the appropriate files. |
# cp -p usr/vice/etc/* /usr/vice/etc # cp -rp usr/vice/etc/C /usr/vice/etc
If you have not yet incorporated AFS into the machine's authentication system, perform the instructions in the section titled Enabling AFS Login for this system type in the IBM AFS Quick Beginnings chapter about configuring client machines. If this machine was running the same operating system revision with AFS 3.5 or AFS 3.6 Beta, you presumably already incorporated AFS into its authentication system.
As part of upgrading a machine to AFS 3.6, you must incorporate AFS 3.6 extensions into its kernel and verify that the AFS initialization script is included in the machine's startup sequence. Proceed to the instructions for your system type:
The AIX kernel extension facility is the dynamic kernel loader provided by IBM Corporation. AIX does not support incorporation of AFS modifications during a kernel build.
For AFS to function correctly, the kernel extension facility must run each time the machine reboots, so the AFS initialization script (included in the AFS distribution) invokes it automatically. In this section you copy the script to the conventional location and edit it to select the appropriate options depending on whether NFS is also to run.
After editing the script, you verify that there is an entry in the AIX inittab file that invokes it, then reboot the machine to incorporate the new AFS extensions into the kernel and restart the Cache Manager.
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
# cd usr/vice/etc # cp -rp dkload /usr/vice/etc
If the initialization file is not already in place, copy it now.
# cp -p rc.afs /etc/rc.afs
NFS=$NFS_NONE
NFS must already be loaded into the kernel. It is loaded automatically on machines running AIX 4.1.1 and later, as long as the file /etc/exports exists.
NFS=$NFS_IAUTH
rcafs:2:wait:/etc/rc.afs > /dev/console 2>&1 # Start AFS services
# cd /usr/vice/etc # rm rc.afs # ln -s /etc/rc.afs
# shutdown -r now
login: root Password: root_password
On Digital UNIX machines, you must build AFS modifications into a new static kernel; Digital UNIX does not support dynamic loading. If the machine's hardware and software configuration exactly matches another Digital UNIX machine on which AFS 3.6 is already built into the kernel, you can choose to 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.
If the machine was running a version of Digital UNIX 4.0 with a previous version of AFS, the configuration changes specified in Step 1 through Step 4 are presumably already in place.
# cd /usr/sys/conf # cp machine_name AFS
. .
. .
options UFS
options NFS
options AFS
. .
. .
. . .
. . .
OPTIONS/nfs optional nfs define_dynamic
OPTIONS/afs optional afs define_dynamic
OPTIONS/cdfs optional cdfs define_dynamic
. . .
. . .
. . . .
. . . .
#
MODULE/nfs_server optional nfs_server Binary
nfs/nfs_server.c module nfs_server optimize -g3
nfs/nfs3_server.c module nfs_server optimize -g3
#
MODULE/afs optional afs Binary
afs/libafs.c module afs
#
. .
. .
#include <afs.h>
#if defined(AFS) && AFS
extern struct vfsops afs_vfsops;
#endif
. .
. .
. . .
. . .
&fdfs_vfsops, "fdfs", /* 12 = MOUNT_FDFS */
#if defined(AFS)
&afs_vfsops, "afs",
#else
(struct vfsops *)0, "", /* 13 = MOUNT_ADDON */
#endif
#if NFS && INFS_DYNAMIC
&nfs3_vfsops, "nfsv3", /* 14 = MOUNT_NFS3 */
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
If the initialization file is not already in place, copy it now. Note the removal of the .rc extension as you copy.
# cp -p usr/vice/etc/afs.rc /sbin/init.d/afs
The AFS 3.6 distribution includes only the libafs.nonfs.o version of the library, because Digital UNIX machines are not supported as NFS/AFS Translator machines.
# cp -p bin/libafs.nonfs.o /usr/sys/BINARY/afs.mod
# doconfig -c AFS
# mv /vmunix /vmunix_orig # cp -p /sys/AFS/vmunix /vmunix
# ln -s ../init.d/afs /sbin/rc3.d/S67afs # ln -s ../init.d/afs /sbin/rc0.d/K66afs
# cd /usr/vice/etc # rm afs.rc # ln -s /sbin/init.d/afs afs.rc
# shutdown -r now
login: root Password: root_password
On HP-UX machines, you must build AFS modifications into a new kernel; HP-UX does not support dynamic loading. If the machine's hardware and software configuration exactly matches another HP-UX machine on which AFS 3.6 is already built into the kernel, you can choose to 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.
# cp -p /stand/vmunix /stand/vmunix.noafs # cp -p /stand/system /stand/system.noafs
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
If the initialization file is not already in place, copy it now. Note the removal of the .rc extension as you copy.
# cp -p usr/vice/etc/afs.rc /sbin/init.d/afs
# cp -p usr/vice/etc/afs.driver /usr/conf/master.d/afs
HP-UX machines are not supported as NFS/AFS Translator machines, so AFS 3.6 includes only libraries called libafs.nonfs.a (for the 32-bit version of HP-UX) and libafs64.nonfs.a (for the 64-bit version of HP-UX). Change the library's name to libafs.a as you copy it.
For the 32-bit version of HP-UX:
# cp -p bin/libafs.nonfs.a /usr/conf/lib/libafs.a
For the 64-bit version of HP-UX:
# cp -p bin/libafs64.nonfs.a /usr/conf/lib/libafs.a
# ln -s ../init.d/afs /sbin/rc2.d/S460afs # ln -s ../init.d/afs /sbin/rc2.d/K800afs
# cd /usr/vice/etc # rm afs.rc # ln -s /sbin/init.d/afs afs.rc
# sam -display local_hostname:0
login: root Password: root_password
# cd /stand/build
# mk_kernel
# mv /stand/build/vmunix_test /stand/vmunix
# cd /
# shutdown -r now
login: root
Password: root_password
login: root Password: root_password
To incorporate AFS into the kernel on IRIX machines, choose one of two methods:
The ml program is the dynamic kernel loader provided by SGI for IRIX systems. If you use it rather than building AFS modifications into a static kernel, then for AFS to function correctly the ml program must run each time the machine reboots. Therefore, the AFS initialization script (included on the AFS CD-ROM) invokes it automatically when the afsml configuration variable is activated. In this section you activate the variable and run the script.
# uname -m
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
You can choose to copy all of the kernel library files into the /usr/vice/etc/sgiload directory, but they require a significant amount of space.
# cd usr/vice/etc/sgiload
If the machine is not to act as an NFS/AFS translator:
# cp -p libafs.IPxx.nonfs.o /usr/vice/etc/sgiload
If the machine is to act as an NFS/AFS translator, in which case its kernel must support NFS server functionality:
# cp -p libafs.IPxx.o /usr/vice/etc/sgiload
If you prefer to build a kernel, and the machine's hardware and software configuration exactly matches another IRIX machine on which AFS 3.6 is already built into the kernel, you can choose to 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.
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
# uname -m
# cd bin
If the machine is not to act as an NFS/AFS translator:
# cp -p libafs.IPxx.nonfs.a /var/sysgen/boot/afs.a
If the machine is to act as an NFS/AFS translator, in which case its kernel must support NFS server functionality:
# cp -p libafs.IPxx.a /var/sysgen/boot/afs.a
# cp -p afs.sm /var/sysgen/system # cp -p afs /var/sysgen/master.d
# cp -p /unix /unix_orig # autoconfig
If the initialization file is not already in place, copy it now. If the machine is configured as a client machine, you already copied the script to the local /usr/vice/etc directory. Otherwise, change directory as indicated, substituting sgi_65 for the sysname variable.
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
Now copy the script. Note the removal of the .rc extension as you copy.
# cp -p script_location/afs.rc /etc/init.d/afs
If you are using the ml program:
# /etc/chkconfig -f afsml on
If you built AFS into a static kernel:
# /etc/chkconfig -f afsml off
If the machine is to function as an NFS/AFS Translator, the kernel supports NFS server functionality, and the afsxnfs variable is not already set appropriately, set it now.
# /etc/chkconfig -f afsxnfs on
# ln -s ../init.d/afs /etc/rc2.d/S35afs # ln -s ../init.d/afs /etc/rc0.d/K35afs
# cd /usr/vice/etc # rm afs.rc # ln -s /etc/init.d/afs afs.rc
# shutdown -i6 -g0 -y
login: root Password: root_password
The insmod program is the dynamic kernel loader for Linux. Linux does not support incorporation of AFS modifications during a kernel build.
For AFS to function correctly, the insmod program must run each time the machine reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. The script also includes commands that select the appropriate AFS library file automatically. In this section you run the script.
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
# cd usr/vice/etc # cp -rp modload /usr/vice/etc
# cp -p afs.rc /etc/rc.d/init.d/afs
The afsd options file possibly already exists as /etc/sysconfig/afs from running a previous version of AFS on this machine. Compare it to the version in the root.client/usr/vice/etc directory of the AFS 3.6 distribution to see if any changes are needed.
If the options file is not already in place, copy it now. Note the removal of the .conf extension as you copy.
# cp -p afs.conf /etc/sysconfig/afs
If necessary, edit the options file to invoke the desired arguments on the afsd command in the initialization script. For further information, see the section titled Configuring the Cache Manager in the IBM AFS Quick Beginnings chapter about configuring client machines.
# /sbin/chkconfig --add afs
# cd /usr/vice/etc
# rm afs.rc afs.conf
# ln -s /etc/rc.d/init.d/afs afs.rc
# ln -s /etc/sysconfig/afs afs.conf
# shutdown -r now
login: root Password: root_password
The modload program is the dynamic kernel loader provided by Sun Microsystems for Solaris systems. Solaris does not support incorporation of AFS modifications during a kernel build.
For AFS to function correctly, the modload program must run each time the machine reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. In this section you copy the appropriate AFS library file to the location where the modload program accesses it and then run the script.
# cd /afs/cellname/sysname/usr/afsws/root.client
# cd /cdrom/sysname/root.client
# cd temp_afs36_dir/root.client
If this machine is running the 64-bit version of Solaris 7, the AFS initialization file differs from the AFS 3.5 version. Copy it from the AFS 3.6 distribution.
Note the removal of the .rc extension as you copy.
# cd usr/vice/etc
# cp -p afs.rc /etc/init.d/afs
If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7 and is not to act as an NFS/AFS translator:
# cp -p modload/libafs.nonfs.o /kernel/fs/afs
If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7 and is to act as an NFS/AFS translator, in which case its kernel must support NFS server functionality and the nfsd process must be running:
# cp -p modload/libafs.o /kernel/fs/afs
If the machine is running the 64-bit version of Solaris 7 and is not to act as an NFS/AFS translator:
# cp -p modload/libafs64.nonfs.o /kernel/fs/sparcv9/afs
If the machine is running the 64-bit version of Solaris 7 and is to act as an NFS/AFS translator, in which case its kernel must support NFS server functionality and the nfsd process must be running:
# cp -p modload/libafs64.o /kernel/fs/sparcv9/afs
# ln -s ../init.d/afs /etc/rc3.d/S99afs # ln -s ../init.d/afs /etc/rc0.d/K66afs