IBM eServer Certification Study Guide: Cluster 1600 Managed by PSSP

Chapter 7. User and data management 251

SP User Management (SPUM) must be set up to ensure that there is a single

user space across all nodes. It ensures that users have the same account, home

directory, and environment across all nodes in the cluster configuration.

7.3 SP User data management

The following three options may be used to manage the user data on the Cluster

1600 managed by PSSP:

 SP User Management (SPUM)

 Network Information System (NIS)

 Manage each user individually on each machine on the network

The first two are more commonly used; SPUM is discussed in this chapter.

7.3.1 SP User Management (SPUM)

The following information is covered in this chapter:

 How to set up SPUM

 How to add, change, delete, and list SP users

 How to change SP user passwords

 SP user login and access control

7.3.2 Set up SPUM

Attributes need to be enabled, depending on which features you want to use in

the SP User Management; you can choose one of the following:

 Automounter

 User administration

 File collection

You can activate SPUM by entering the SMIT fastpath smit site_env_dialog,

depending on which attribute you want to use; set the fields to

true:

 Automounter Configuration

 User Administration Interface

 File Collection Management

For more detailed information about the SP User Management, see the sections

“Managing file collections”, “Managing user accounts“, or “Managing the

automounter” in PSSP Administration Guide, SA22-7348, or look in RS/6000 SP

252 IBM Eserver Certification Study Guide: Cluster 1600 Managed by PSSP

Planning, Volume 2: Control Workstation and Software Environment,

GA22-7281.

7.3.3 Add, change, delete, and list SP users

Using the SP User Management commands, you can add and delete users,

change account information, and set defaults for your users' home directories.

Specify the user management options you wish to use in your site environment

during the installation process, or change them later, either through SMIT panels

or by using the spsitenv command, or through SMIT by entering smit spmkuser.

The “Managing user accounts” section in the PSSP Administration Guide,

SA22-7348

contains detailed instructions for entering site environment

information.

The following are the steps for adding an SP user by entering smit spmkuser:

 Check the /usr/lpp/ssp/bin/spmkuser.default file for defaults for primary group,

secondary groups, and initial programs.

 The user’s home directory default location is retrieved from the SDR SP

class, homedir_server, and homedir_path attributes.

 spmkuser only supports the following user attributes: id, pgrp, home (as in

hostname: home_directory_path format), groups, gecos, shell, and login.

 A random password is generated and stored in the

/usr/lpp/ssp/config/admin/newpass.log file.

The following example shows how to list SP users using the spluser command:

spluser spuser1

The output will be as shown in Example 7-1.

Example 7-1 spluser spuser1

spuser1 id=201 pgrp=1 groups=staff home=/u/spuser1 on

sp3en0:/home/sp3en0/spuser1 shell=/bin/ksh gecos= login=true

7.3.4 Change SP user passwords

The SP user passwords may be changed in the following manner:

 The user must log on to the system where the master password file is.

Normally, it is on the CWS.

 Use the passwd command to change the password.

 The /etc/passwd and /etc/security /password files must be updated on all

nodes.