DFS Configuration Guide v4.2

1 — Introduction to DFS Configuration


[Previous] [Next] [Contents] [Index]


1.1 Overview

This chapter describes the preparations you must make before you configure the Gradient® DFS for Tru64™ UNIX® software.

Gradient DFS is fully functional on the Tru64 UNIX v5.0, 5.0a and 5.1 operating systems.

1.2 Verifying That the DCE and DFS Subsets Have Been Installed

In order to configure Gradient DFS on a system, the DCE layered product must be installed and configured on the system then the DCE DFS subsets should be installed. See Gradient DCE for Tru64 UNIX Installation and Configuration Guide, Section 1.12 for information on installing and configuring DCE and installing the DCE DFS subsets.

NOTE: Ensure that the proper DFS subset, specific to the operating system, is installed before beginning DFS configuration.

1.3 Verifying That a New Kernel Has Been Built

After Gradient DFS has been installed on a system, you must rebuild the kernel, using the doconfig command, to include DFS support in the kernel. Then reboot the system using the new kernel.

1.4 Verifying Necessary Privileges

In order to configure Gradient DFS on a system, you need root privileges on that system.

1.5 Identifying Your System's Role in the DFS Environment

A system can have the following roles in a DCE DFS environment:

See Understanding DCE, Introduction to OSF DCE, and OSF DCE DFS Administration Guide and Reference for more information.

1.6 Preparing for the Configuration

After the DFS subset is installed, configure the DFS services by running /usr/sbin/dfssetup, a script that generates the initial configuration using default information and information you provide.

Appendix A contains the DFS Configuration Worksheet for you to copy and use as you prepare to configure DFS. Before you begin, write the cell name on the top line of each worksheet completed. This enables you to keep all worksheets for a particular cell together.

The following sections explain the additional information to record on the worksheet. Choose the sections that apply to your particular machine.

1.6.1 Information for FLDB Server Configuration

Each DCE cell using DFS requires at least one Fileset Location Database (FLDB) Server. This machine is also usually the System Control Machine. Figure 1-1 shows the server section of the DFS Configuration Worksheet. Table 1-1 explains how to use this form when configuring FLDB Servers.

If the FLDB Server is also going to be a DFS Client or a DFS Server, see Section 1.6.2 on page 12 and Section 1.6.3 on page 12, respectively, after filling out this part of the worksheet.

Figure 1-1: Server Section of the DFS Configuration Worksheet


Table 1-1: Using the DFS Configuration Worksheet for FLDB Servers

Cell Administrator's Principal Name

The principal name for the DCE cell administrator. This is the same default principal name used in DCE installation and configuration, cell_admin.

Password

The password for cell_admin. This is the same password that is specified in the DCE cell configuration.

System Control Machine Name

The name of the machine that distributes common configuration files to other server machines in the cell or administrative domain. The default is the name of the FLDB Server or another machine, depending on how you chose to set up your DFS environment.

File System Type

The file system type for the DFS root fileset. This can be either the UFS file system or the POLYCENTER Advanced File System (AdvFS).

Device Name

The block device name of the DFS root fileset. For example, /dev/rz3h (for UFS file system only).

AdvFS Fileset Name

The AdvFS fileset specification of the DFS root fileset, in the form domain_name#fileset_name (for AdvFS file system only).

Fileset Mount Point

The local mount point for the DFS root fileset. Enter 1 to 31 alphanumeric characters. For example, /dfs.root.

Caution: Do not specify the local system root directory (/\) as the mount point for the DFS root fileset. If you do, serious data corruption might occur.

Aggregate ID

A positive integer to identify the root aggregate. This ID is unique for each DFS server and cannot be used by any other entries in the dfstab file.

1.6.2 Information for DFS Client Configuration

DFS client machines are those machines that request DFS filesets from DFS File Servers, import the filesets, and keep track of operations on those filesets. Figure 1-2 shows the Client part of the DFS Configuration Worksheet. Table 1-2 describes how to use the worksheet.

Figure 1-2: Client Section of the DFS Configuration Worksheet


Table 1-2: Using the DFS Configuration Worksheet for FLDB Servers

Cache Type

The type of cache your system will use for DFS caching. The choices are disk or memory. If you choose a memory cache, the system will not perform disk caching even if there is disk space available. In addition, a memory cache is permanently allocated from system memory and is typically smaller than a disk cache.

Cache Size

The size of the DFS cache in kilobytes. For disk caching, the default is 10,000 kilobytes (10 MB). For memory caching, the default is 1000 kilobytes (1 MB).

Cache Directory

The name of the caching directory. The default is /opt/dcelocal/var/adm/dfs/cache. Entegrity recommends that you dedicate a disk partition for DFS caching and use that directory name as the cache directory (for disk caching only).

1.6.3 Information for DFS File Server Configuration

A DFS File Server receives requests from DFS clients and serves the requested DFS filesets to them. Figure 1-3 shows the File Server part of the DFS Configuration Worksheet. Table 1-3 explains how to use this form when configuring File Servers.

Figure 1-3: Server Section of the DFS Configuration Worksheet


Table 1-3: Using the DFS Configuration Worksheet for File Servers

Cell Administrator's Principal Name

The principal name for the DCE cell administrator. This is the same default principal name used in DCE installation and configuration, cell_admin.

Password

The password for cell_admin. This is the same password that is specified in the DCE cell configuration.

System Control Machine Name

The name of the machine that distributes common configuration files to other server machines in the cell or administrative domain. The default is the name of the FLDB Server or another machine, depending on how you chose to set up your DFS environment.

File System Type

The file system type for the exported DFS fileset. This can be either the UFS file system or the POLYCENTER Advanced File System (AdvFS).

Device Name

The block device name of the exported DFS fileset. For example, /dev/rz3h (for UFS file system only).

AdvFS Fileset Name

The AdvFS fileset specification of the exported DFS fileset, in the form domain_name#fileset_name (for AdvFS file system only).

Fileset Mount Point

The local mount point for the exported DFS fileset.

Aggregate ID

A positive integer to identify the exported aggregate. This ID is unique and cannot be used by any other entries in the dfstab file.

1.6.4 Information for DFS System Control Machine Configuration

A DFS System Control Machine updates other machines in the cell domain with common Configuration files such as administrative lists. Figure 1-4 shows the System Control Machine part of the DFS Configuration Worksheet. Table 1-4 describes the worksheet.

Figure 1-4: System Control Machine Section of the DFS Configuration Worksheet


Table 1-4: Using the System Contol Section of the DFS Configuration Worksheet

Cell Administrator's Principal Name

The principal name for the DCE cell administrator. This is the same default principal name used in DCE installation and Configuration, cell_admin.

Password

The password for cell_admin. This is the same password that is specified in the DCE cell configuration.

1.6.5 Information for DFS Client Configuration

DFS client machines are those machines that request DFS filesets from DFS File Servers, import the filesets, and keep track of operations on those filesets. Figure 1-5 shows the Client part of the DFS Configuration Worksheet. Table 1-5 describes how to use the worksheet.

Figure 1-5: Client Section of the DFS Configuration Worksheet


Table 1-5: Using the DFS Configuration Worksheet for DFS Clients

Cache Type

The type of cache your system will use for DFS caching. The choices are disk or memory. If you choose a memory cache, the system will not perform disk caching even if there is disk space available. In addition, a memory cache is permanently allocated from system memory and is typically smaller than a disk cache.

Cache Size

The size of the DFS cache in kilobytes. For disk caching, the default is 10,000 kilobytes (10 MB). For memory caching, the default is 1000 kilobytes (1 MB).

Cache Directory

The name of the caching directory. The default is /opt/dcelocal/var/adm/dfs/cache. Entegrity recommends that you dedicate a disk partition for DFS caching and use that directory name as the cache directory (for disk caching only). For cluster configurations, the cache directory must be member specific. The dfssetup script will make the cache directory member specific (CDSL) during cluster configuration.

1.7 Modifying the Configuration for Startup

Most DFS configurations use default settings when starting DFS processes on various machines. Thus, most users can skip the information in this section and proceed to the configuration instructions in Chapter 2.

Gradient DFS provides a configuration file called opt/dcelocal/etc/setup_state. This file lets advanced users specify non-default options for commands (dfsd, dfsbind, and fxd) that dfssetup executes to start DFS processes on the local server or client machine.

The setld process that installs the DCE software subsets checks whether the setup_state file is present, and installs it if it is not present. The unmodified setup_state file includes the following default settings:

DFSD_OPTS=""
DFSBIND_OPTS=""
DFSFXD_OPTS="-mainprocs 7"

Use any ASCII editor to modify the file. The following example shows a modified setup_state file.

DFSD_OPTS="-mainprocs 2 -tokenprocs 2 -files 300"

DFSBIND_OPTS="-expressprocs 1 -regularprocs 1 -junctionlife 86400 
-prefixlife 86400 -notfoundlife 3600"

DFSFXD_OPTS="-mainprocs 4"

Use the setup_state file to set any options to the dfsd, dfsbind, and fxd commands as necessary. Refer to the appropriate reference pages in the OSF DCE DFS Administration Guide and Reference.

NOTE: The setld program does not overwrite the setup_state file if it exists. However, some operations like clobber delete this file. If you modify the file, be sure to keep a copy of the modified file in a safe place.


[Previous] [Next] [Contents] [Index]


To make comments or ask for help, contact support@entegrity.com.

Copyright © 1997-2002 Entegrity Solutions Corporation & its subsidiaries