Creating Users; Defining Unix Users And Groups - IBM totalstorage 326 User Reference

In allowing failback of groups, there is a slight delay in the resources moving from
one node to the other. The group can also be instructed to allow failback when the
preferred node becomes available or to failback during specific off-peak usage
hours.
Each resource under each disk group has individual resource properties. The
properties range from restart properties, polling intervals to check if a resource is
operational, to a timeout to return to an online state. The default settings for these
properties are selected from average conditions and moderate daily use.

Creating users

The creation of users is performed through normal procedures. Users do not need
to be created exclusively for use on the cluster resources. You must define
properties of the resources for users to access the resources within the domain
policies. All user-accessible cluster resources have the same properties as standard
Microsoft Windows resources, and should be set up following the same policies.
Note: If your storage will be accessed by UNIX or UNIX-based clients and servers,

Defining UNIX users and groups

This section describes how to set up UNIX users and groups to access the Model
326 storage through the Network File System (NFS) protocol.
"Microsoft Services for UNIX and NFS Support" on page 72 has more information
on Services for UNIX and NFS.
Support for NFS is provided in the Model 326 by a preloaded and preconfigured
software component, Microsoft Services for UNIX. The levels of NFS supported by
Services for UNIX, and in turn the Model 326, are NFS Versions 2 and 3. Any client
or server that is using an NFS software stack supporting NFS Version 2 or NFS
Version 3, regardless of the operating system, can connect to the Model 326 and
access its storage through NFS.
You administer NFS file shares and other attributes with standard Windows
administration tools, including those provided as part of the IBM NAS desktop and
the Microsoft Windows 2000 for NAS user interface. Additional configuration of the
User Name Mapping component of Services for UNIX, which maps the UNIX user
name space to the Windows user name space, is required to support NFS security.
You can define a local UNIX name space on the Model 326 by configuring the
Server for PCNFS component of Services for UNIX. Alternately, you can point
Services for UNIX to an existing Network Information Service (NIS) domain that
defines the UNIX name space. In both cases, you must configure the User Name
Mapping component to map the UNIX name space that you select to the Windows
name space, because file shares and individual file and directory permissions on
the Model 326 are defined in the context of the Windows name space.
To define a local UNIX name space, continue with "Using a local UNIX name
space" on page 44. To use a UNIX name space defined on a NIS domain, continue
with "Using the UNIX name space on an NIS domain" on page 45.
continue with "Defining UNIX users and groups". The Model 326 is on a
Windows domain and inherits those Windows users, eliminating the need to
define local Windows users and groups. Also, shares are created in the
clustering setup.
Chapter 5. Completing networking, clustering, and storage access setup
43