Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Setting Up and Administering an HP-UX NFS Diskless Cluster
NFS Diskless Questions and Answers
Chapter 10 943
Answer: This is a case where SAM is not going to be much more help than if you
had a large collection of standalone systems and you wanted some of
them to have access to a resource. SAM helps you manage all of the
systems in a cluster consistently, with some flexibility to allow for
exceptions, but does not help you manage subsets of a cluster.
Question: Do I have to add and manage cluster-wide resources by running SAM on
the cluster server?
Answer: No, in fact with NFS Diskless there is much less of a distinction between
a cluster server and cluster clients.
In general, you can run SAM on any system in a cluster to manage
cluster-wide resources. You do have to run SAM on the system that a
resource is attached to in order to do a local add or remove of that
resource.
For example, if you attach a printer to a cluster client named zorro, then
you must run SAM on zorro to configure the printer on zorro. To make
the printer a cluster-wide resource you can either:
• Use the “Manage Cluster-Wide” option when doing the local add;
or
• Run SAM and do a cluster-wide remote add while on one of the other
members of the cluster;
or
• Change the cluster-wide state of the printer while running on the
system that the printer is attached to.
File Systems
Question: When a physical file system is made into a cluster-wide resource, what
does SAM do?
Answer: SAM uses the automounter to access the file system on the other systems
in the cluster. The steps are:
• SAM modifies /etc/exports to allow the other systems access to the
file system.
• SAM creates an entry in an automounter direct map that is managed
by SAM (/etc/auto_cluster).