A system manager will frequently want to move the /tmp file system to either a drive local to a cluster member or to another disk to improve file system performance. Another reason to move /tmp is because a user could potentially fill up the root file system by writing to /tmp. Making it a separate file system eliminates that possibility.
First create an AdvFS domain and fileset on the desired disk/partition.
# mkfdmn /dev/disk/dsk21c gilligan_tmp
# mkfset gilligan_tmp tmp
Then modify the /etc/fstab file to include this mount.
gilligan_tmp#tmp /cluster/members/member2/tmp advfs rw 0 0
You can verify that gilligan is indeed member2 by issuing the clu_get_info (8) command.
[gilligan] # clu_get_info -m 2 Cluster memberid = 2 Hostname = gilligan.alf.cpqcorp.net Cluster interconnect IP name = gilligan-mc0 Member state = UP
Now when gilligan boots, since it has access to dsk21, it will be able to mount the file system. Any other member will fail to mount the file system, but that's perfectly okay.
Another possibility is to create /tmp on a disk that happens to be on the shared bus. Again make the domain and fileset and add an entry to the /etc/fstab file as above. If you prefer having /tmp accessible only to the member that is using it, you can mount the file system with the mount (8) command using "-o server_only". This isn't necessary but may be desirable and will behave like the local bus example even though the file system is on a shared resource.