HP b2600 Instruction Manual

HP Enterprise File System
HP DCE/9000 Enhanced DFS Version 3.0
Release Note
HP Part No. B6863-IE001-E0302
Edition 1
© Hewlett-Packard Company, 1997-2002. All rights reserved.

2
Legal Notices
Legal Notices
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
document, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard shall
not be held liable for errors contained herein or direct, indirect, special,
incidental or consequential damages in connection with the furnishing,
performance, or use of this material.
Warranty.A copy of the specific warranty terms applicable to your Hewlett-
Packard product and replacement parts can be obtained from your local Sales
and Service Office.
Restricted Rights Legend. Use, duplication or disclosure by the U.S.
Government is subject to restrictions as set forth in subparagraph (c) (1) (ii)
of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) ofthe
Commercial Computer Software Restricted Rights clause at FAR 52.227-19
for other agencies.
HEWLETT-PACKARD COMPANY
3000 Hanover Street
Palo Alto, California 94304 U.S.A.
Use of this document and the CD-ROM(s) supplied for this pack is restricted
to this product only. Additional copies of the programs may be made for
security and back-up purposes only. Resale of the programs in their present
form or with alterations, is expressly prohibited.
Copyright Notices. ©copyright 1983-2001 Hewlett-Packard Company, all
rights reserved.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright laws.
©copyright 1979, 1980, 1983, 1985-93 Regents of the University of
California

3
Legal Notices
This software is based in part on the Fourth Berkeley Software Distribution
under license from the Regents of the University of California.
©copyright 1980, 1984, 1986 Novell, Inc.
©copyright 1986-1992 Sun Microsystems, Inc.
©copyright 1985-86, 1988 Massachusetts Institute of Technology.
©copyright 1989-93 The Open Software Foundation, Inc.
©copyright 1986 Digital Equipment Corporation.
©copyright 1990 Motorola, Inc.
©copyright 1990, 1991, 1992 Cornell University
©copyright 1989-1991 The University of Maryland
©copyright 1988 Carnegie Mellon University
Trademark Notices UNIX is a registered trademark in the United States and
other countries, licensed exclusively through X/Open Company Limited.
X Window System is a trademark of the Massachusetts Institute of
Technology.
MS-DOS and Microsoft are U.S. registered trademarks of Microsoft
Corporation.
OSF/Motif is a trademark of the Open Software Foundation, Inc. in the U.S.
and other countries.

4
Legal Notices

Contents
5
HP DCE/9000 Enhanced DFS Version 3.0 1
Release Note 1
1What’sinThisVersion
Overview of HP DCE/9000 Enhanced DFS Version 3.0 10
Benefits 11
Features 12
Restricting RPC Addresses 12
DCE/DFS TCL Configuration Functions 14
Global variables 18
HP Enterprise File System Admin Web 20
2 Information About This Version
Known Problems and Workarounds 22
Problems Accessing Foreign Cell 22
FTS Produces Core Dump 22
Local LFS Mount Not Supported 22
Exporting VxFS File System Not Supported 22
DCM Tool Not Supported 22
GDS Required for X.500 Cell Name 23
UDP/IP Required 23
Using the HP-UX mkdir -p Command 23
Visibility of Global Cell Name Space 23
New Version of kload Command Needed for AFS 24
DCE Credentials Not Forwarded by CDE 25
Maximum Episode Aggregate and Fileset Sizes 26

6
Contents
ClearCase Incompatibility 26
Issues with DFS as a UNIX Filesystem 26
Differences Between 1.5.2 and 3.0 29
Important: System Name Change 29
Software Availability in Native Languages 29
Location of DFS Administration Tools 29
Client Only Available 29
Patches and Fixes in This Version 30
3 Compatibility Information and Installation Requirements
Prerequisite Software 32
Patches Required 33
Integrated Login 33
VxFS as File System for DFS Cache 33
Patches Strongly Recommended 34
Cache Space Requirements 35
Enhanced DFS 3.0 Interoperability 36
NIS and Integrated Login Interoperability 37
4 What Manuals are Available for This Version
Online Documentation for Enhanced DFS 3.0 40

Contents
7

8
Contents

9
1
What’s in This Version
HP DCE/9000 Enhanced DFS Version 3.0 is a distributed file system
functionally equivalent to Version 1.2.2 of The Open Group’s (formerly
Open Software Foundation) DCE Distributed File Service (DFS). Enhanced
DFS is one component of the HP Enterprise File System product family.

10
What’s in This Version
Overview of HP DCE/9000 Enhanced DFS Version 3.0
Overview of HP DCE/9000 Enhanced DFS Version 3.0
HP DCE/9000 Enhanced DFS 3.0 is a distributed client/server application
that presents DCE with a global view of a set of files and directories,
independent of machine boundaries. This global view is called the Enhanced
DFS filespace. Within this filespace, users can share files stored on any of
the computers that are part of this global view.
Enhanced DFS requires the HP-UX 11.0 operating system and the
HP DCE/9000 Version 1.7 product. Enhanced DFS supports all
HP DCE/9000 DFS 1.7 functionality and protocols, and interoperates fully
with other DFS servers.
The client and server components of Enhanced DFS 3.0 are available as
separately orderable components.
NOTE: For this version of Enhanced DFS 3.0, only the client is available.

11
What’s in This Version
Benefits
Benefits
Enhanced DFS 3.0 provides a number of benefits, including the following:
• Allows faster restarts after abnormal system shutdowns using the DCE LFS log-
based file system
• Uses tokens to ensure that users are working with the most-recent copy of a file
and to track who is working on the file
• Allows administrators to replicate commonly used DCE LFS filesets on multiple
File Server machines
• Allows easier recovery from severe system failures
• Provides increased availability of files through replication and caching
• Improves load balancing of data
• Tracks the location of every fileset
• Extends the UNIX permissions to provide more precise definitions of access
permissions for directories and files using ACLs
• Allows the use of data from non-LFS file systems
• Allows the addition of server and client machines to an HP DCE/9000 DFS
configurationwith little impacton other servers or clients and with few additional
administrative responsibilities
• Supports enhanced administration and security
• Stores central copies of system configuration and binary files on designated
machines and distributes these files to other server machines in the network
• Backs up and restores system and user data as needed
Enhanced DFS 3.0 operates on top of and interacts with the following HP
DCE 1.7 components:
• DCE Security Service
• DCE Directory Service
• DCE Distributed Time Service
• DCE Remote Procedure Call facility

12
What’s in This Version
Features
Features
Enhanced DFS 3.0 offers complete HP DCE/9000 1.7 DFS server
functionality for distributed computing environments, which can include:
• Server machines
• Client machines
• Data access management
• Administrative domains
• Administrative lists and groups
• Local file system
• Database distribution
• The scout program
• Authenticated access from NFS via the gateway
In addition, Enhanced DFS 3.0 includes all extended DFS features.
Restricting RPC Addresses
Enhanced DFS 3.0 includes restricting RPC addresses with the use of the
environment variable, RPC_SUPPORTED_NETADDRS. See the HP
DCE 1.5 planning and configuration guide for a description of this
environment variable.
The runtime looks for a RPC_SUPPORTED_NETADDRS environment
variable, which allows a user or administrator to restrict the network
addresses that a DFS host advertises in the name-space or endpoint-map.
If you set this environment variable, only addresses in the list will be
advertised in the namespace or endpoint map. Addresses not found on the
list are excluded from the server’s list of available addresses. The format of
the RPC_SUPPORTED_NETADDRS string is as follows:
RPC_SUPPORTED_NETADDRS=protseq:netaddr
For example, assuming that host myhost is located at IP address 10.3.2.1, the
Korn shell statements:

13
What’s in This Version
Features
export RPC_SUPPORTED_NETADDRS=ip:myhost
or
export RPC_SUPPORTED_NETADDRS=ip:10.3.2.1
forces any servers started in the current shell to support only the addresses
associated with the name myhost and the network address 10.3.2.1
Since both DCE and DFS respond to RPC_SUPPORTED_NETADDRS, it
may be best to set it in a file that is sourced by both /sbin/init.d/dce and
/sbin/init.d/dfs. For example, the Korn shell statement above could be
placed in the file /etc/rc.config.d/rpc_supported_netaddrs, and the lines
such as
if [ -r ${OS_DCE_ETC}/rpc_supported_netaddrs ]
then
. . ${OS_DCE_ETC}/rpc_supported_netaddrs
fi
could be included in both /sbin/init.d/dce and /sbin/init.d/dfs.
You may use the RPC_SUPPORTED_NETADDRS environment variable to
restrict DFS/DCE/EFS interfaces to a single interface, but you may not
specify any entries for the CN protocol sequence, nor may you specify more
than a single network address. The RPC_SUPPORTED_NETADDRS
environment variable should be consistent between all DCE and all
DFS/EFS processes.

14
What’s in This Version
Features
DCE/DFS TCL Configuration Functions
1Configure a DCE client:
tcl_dce_config_dceclient (hostname sec_server \
> cds_server dts_type celladmin celladmin_pw)
The local host name is passed for users that would like to specify a full domain
name (for example, oddball.ch.apollo.hp.com) instead of the short name you get
from the system hostname command. The cds_server parameter is passed
in order to cache if dcecp can’t figure out one for itself. (This is a necessity and
something that seems to happen all too often). The dts_type is one of ‘client’,
‘local’, ‘global’ or ‘none’.
For example:
dcecp> tcl_dce_config_dceclient oddball harpoon \
> harpoon client cell_admin -dce-
:
dcecp>
2Configure a single-machine DCE server:
tcl_dce_config_dceserver (hostname cellname dts_type \
> celladmin celladmin_pw)
The hostname parameter can be passed as either the full domain name (for
example, blech.ch.apollo.hp.com) or the short name (for example, blech).
Specify the cellname parameter without the /.../ in front. The dts_type
parameter should be one of ‘client’, ‘local’, ‘global’ or ‘none’. Choose your own
celladmin account name (usually ‘cell_admin’) and password. This function
calls tcl_dce_config_dced(),tcl_dce_config_secserver(),
tcl_dce_config_cdsserver() and
tcl_dce_config_dtsserver().
For example:
dcecp> tcl_dce_config_dceserver oddball gumby1 \
> global cell_admin -dce-
:
dcecp>

15
What’s in This Version
Features
3Configure dced:
tcl_dce_config_dced (hostname cellname sec_server)
The hostname parameter can be passed as either the full domain name (for
example, blech.ch.apollo.hp.com) or the short name (for example, blech).
Specify the cellname parameter without the /.../in front.If you are configuring
the dced on a machine to be a client in an existing cell, sec_server would be
the name of the security server in that cell. If you are configuring the dced on a
machine to be its own cell, sec_server should be the same as hostname.If
you are configuring the local host into an existing cell, you can pass “NULL” as
the cellname if you would like the function to internally figure out the name of
the cell using the sec_server parameter.
For example:
dcecp> tcl_dce_config_dced oddball gumby1 oddball
:
dcecp>
4Configure secd:
tcl_dce_config_secserver (hostname cellname \
> celladmin celladmin_pw)
The hostname parameter can be passed as either the full domain name (for
example, blech.ch.apollo.hp.com) or the short name (for example, blech).
Specify the cellname parameter without the /.../ in front. The dts_type
parameter should be one of ‘client’, ‘local’, ‘global’ or ‘none’. Choose your own
celladmin account name (usually ‘cell_admin’) and password.
For example:
dcecp> tcl_dce_config_secserver oddball gumby1 \
> cell_admin -dce-
:
dcecp>

16
What’s in This Version
Features
5Configure cdsd:
tcl_dce_config_cdsserver (hostname cellname \
> sec_server celladmin celladmin_pw)
The hostname parameter can be passed as either the full domain name (for
example, blech.ch.apollo.hp.com) or the short name (for example, blech).
Specify the cellname parameter without the /.../ in front. The dts_type
parameter should be one of ‘client’, ‘local’, ‘global’ or ‘none’. Choose your own
celladmin account name (usually ‘cell_admin’) and password. If you are
configuring a single-node server, sec_server shouldbethesameas
hostname.
For example:
dcecp> tcl_dce_config_cdsserver oddball gumby1 \
>oddball cell_admin -dce-
:
dcecp>
6Configure dtsd:
tcl_dce_config_dtsserver (hostname dts_type \
> celladmin celladmin_pw)
The hostname parameter can be passed as either the full domain name (for
example, blech.ch.apollo.hp.com) or the short name (for example, blech).
Specify the cellname parameter without the /.../ in front. The dts_type
parameter should be one of ‘client’, ‘local’, ‘global’ or ‘none’. Choose your own
celladmin account name (usually ‘cell_admin’) and password.
For example:
dcecp> tcl_dce_config_dtsserver oddball client \
> cell_admin -dce-
:
dcecp>

17
What’s in This Version
Features
7Configure security replica:
tcl_dce_config_secreplica (hostname celladmin \
> celladmin_pw)
This function allows an existing dce client machine to become a security replica.
The hostname will be the used as the name of the replica. The node you run
this function on must be an existing dce client machine.
For example:
dcecp> tcl_dce_config_secreplica oddball cell_admin \
> -dce-
:
dcecp>
8Configure cds replica:
tcl_dce_config_cdsreplica (hostname cds_server \
> celladmin celladmin_pw cds_dirlist)
Will create a CDS replica server on an existing dce clientmachine. The node you
run this function on must be an existing dce client. The hostname will be used
as the name of the clearinghouse (with ‘_ch’ appended). The cds_dirlist
parameter is a space-separated list (in braces) of CDS directories that should be
replicated in the new CDS server. The “/.:” directory is always automatically
replicated.
For example:
dcecp> tcl_dce_config_cdsreplica oddball harpoon
cell_admin -dce- \> {/.:/hosts /.:/hosts/oddball /.:/
hosts/blech}: dcecp>

18
What’s in This Version
Features
9Unconfigure a client (only) machine from an existing cell:
tcl_dce_unconfig (hostname force celladmin \
> celladmin_pw)
Where force is either ‘y’ or ‘n’, and it tells the function whether to continue
with the unconfiguration when it gets an error (y) or whether to stop and report
the error (n). tcl_dce_unconfig simply removes the dce entries in the
registry and namespace, it does not touch the files on the machine being
unconfigured, and it does not stop any running processes.
For example:
dcecp> tcl_dce_unconfig oddball y cell_admin -dce-
:
dcecp>
10 Remove a machine from an existing cell:
tcl_dce_remove (hostname)
On a client, do this after an tcl_dce_unconfig.Onaserver,dothisto
completely remove the server and destroy the cell. It doesn’t touch the registry or
namespace, but does stop any running daemons and then removes all the files it
can find that werecreatedby dce while itran. Because all existing credentials are
also removed, you should exit the current ‘dcecp’ process before attempting any
additional configuration work. hostname must be the local host.
Global variables
Global variables include directory variables, execution variables, and
security server variables. Global variables may be defined by the user if the
default setting is not correct for whatever reason. If none are defined, the
configuration scripts will still work correctly.

19
What’s in This Version
Features
Directory variables should only have to be changed by the user if they
somehow customize their dce installation and required files are not in the
default directories.
• DCELOCAL - Default is “/opt/dcelocal”
• OS_DCE_ETC - Default is “/etc/rc.config.d”
• DCE_ETC - Default is “/etc/opt/dce”
• DCE_VAR - Default is “/var/opt/dce”
• DCE_OPT - Default is “/opt/dce”
Execution variables can be changed by the user to modify the behavior of
the configuration scripts.
• CLEAN_UP - y or n. “y” means that when an error is encountered during
configuration, the clean-up code will be executed. “n” means that the node will
be left in the state it was in when the configuration script failed. Default is “y”.
• EXIT_ERR - y or n. “y” means that when an error is encountered in certain areas
(such asa principal already existing when configuring a dce client), the code will
exit immediately. “n” means an error of this kind will be ignored and the
configuration will continue. Default is “y”.
• DISPLAY - Legal value is a number between ‘1’ and ‘5’ inclusive. This variable
determines how much detail is output to the screen during configuration. The
lower the number the fewer the messages. Errors are always reported. Debug
level messages are only displayed when DISPLAY is 4 or greater. Default is “5”.
Security server variables can change how the security server is eventually
configured.
• LOW_UID - This is the starting UID value to use when new entries are made in
the security registry. Default is ‘100’.
• LOW_GID - This is the starting GID value to use when new entries are made in
the security registry. Default is ‘100’.
• KEYSEED - This is the key value to use when creating a security server or
security replica. It can be any random string of characters. Default is
‘randomstring’.

20
What’s in This Version
HP Enterprise File System Admin Web
HP Enterprise File System Admin Web
The Enterprise File System (EFS) Admin web is a group of HTML files and
CGI scripts shipped with the Enhanced DFS product. You can use these files
to create your own EFS web server site, or integrate them into an existing
web server.
You can run the EfsStatus tool directly from a command line by entering
efsstatus.dcp. You can run the Sentinel tool directly from a command line
by entering sentinel. Sentinel has online help accessible from its graphical
interface.
The files are contained in the installation fileset EFS-WEB and are installed
in the directory /opt/dce/usr/contrib/efsadmin.
Once you have the EFS Admin web up, it allows you to:
• run Sentinel, a graphical file server monitoring tool
• run EfsStatus, a dcecp script that prints status information about DCE and
Enhanced DFS servers in your cell
• view DCE and Enhanced DFS log information for a specified node
• access the HP Corporate and HP EFS home pages
• view Information on product updates and new additions to the Resource Kit via
theHPEFShomepage
• send mail about Enhanced DFS to HP
Note that you can access a copy of the HP DCE/9000 Enhanced DFS
Version 3.0 Release Note (in HTML format) from the HP EFS home page.
See the “What Manuals are Available for This Version” chapter in this
manual for complete information about the documentation provided with HP
DCE/9000 Enhanced DFS 3.0.