6.1 Adding a Logging UFS File System to a Logical Host

· How to Add a Logging UFS File System to a Logical Host

1. Add an entry for the logging UFS file system to the vfstab.logicalhost file using hafstab(1M).

2. Run mount(1M) to mount the new file system. Alternatively, you can wait until the next membership reconfiguration for the file system to be automatically mounted.

3. Add the HA-NFS file system to the logical host.

   You would perform this step only if the logging UFS file system is going to be an HA-NFS file system. If this is the case, follow the procedure in Section 6.3, "Adding an HA-NFS File System to a Logical Host," on page 6-2.

6.2 Removing a Logging UFS File System From a Logical Host

· How to Remove a Logging UFS File System From a Logical Host

1. Remove the logging UFS file system entry from the vfstab.logicalhost file by using the hafstab command.

   Refer to Chapter 10 of the SPARCcluster High Availability Software Planning and Installation Guide for instruction on using the hafstab command.

2. Run the umount(1M) command to unmount the file system.

3. (Optional) Clear the associated trans device and its mirrors using either the metaclear(1M) -r or the metatool(1M) command. Refer to the Solstice DiskSuite 4.0 Administration Guide or the Solstice DiskSuite Tool 4.0 User's Guide for instructions on clearing trans devices.

6.3 Adding an HA-NFS File System to a Logical Host

· How to Add an HA-NFS File System to a Logical Host

1. Make the appropriate entry for each logging UFS file system that will be shared by HA-NFS in the vfstab.logicalhost file by using the hafstab command.

2. Make the corresponding entry in the dfstab.logicalhost file by using the hafstab command.

   Refer to Chapter 10 of the SPARCcluster High Availability Software Planning and Installation Guide for instruction on using the hafstab command.

3. Execute a reconfiguration reboot of the server.

   Alternatively, the file system may shared manually. If the procedure is performed manually, the fault monitoring processes will not be started either locally or remotely until the next membership reconfiguration is performed.

host1# touch /reconfigure

6.4 Removing an HA-NFS File System From a Logical Host

· How to Remove an HA-NFS File System From a Logical Host

1. Remove the entry for the HA-NFS file system from the dfstab.logicalhost file by using the hafstab command.

   Refer to Chapter 10 of the SPARCcluster High Availability Software Planning and Installation Guide for instructions on using the hafstab command.

2. Run the unshare(1M)command.

   The fault monitoring system will try to access the file system until the next membership reconfiguration. Errors will be logged but a takeover of services will not be initiated by the Solstice HA software.

3. (Optional) Remove the logging UFS file system from the logical host. If you want to retain the UFS file system for a non-HA-NFS purpose, such as an HA-ORACLE file system, skip to Step 4.

   To perform this task, use the procedure in Section 6.2, "Removing a Logging UFS File System From a Logical Host," on page 6-2.

4. Execute a reconfiguration reboot of the server.

host1# touch /reconfigure

6.5 Changing Share Options on an HA-NFS File System

If you use the rw, rw=, ro, or ro= options to the share command, HA-NFS fault monitoring will work best if you grant access to all the physical hostnames associated with both Solstice HA servers. Refer to the list of hostnames you entered during the configuration of your Solstice HA servers.

If you use netgroups in the share command, rather than the names of individual hosts, add all of the Solstice HA hostnames to the appropriate netgroup. Ideally, you should grant both read and write access to all the Solstice HA hosts' hostnames to enable the NFS fault probes to do a complete job.

· How to Change Share Options on an HA-NFS File System

1. Make the appropriate share changes to the dfstab.logicalhost file using the hafstab(1M) command.

   Refer to Chapter 10 of the SPARCcluster High Availability Software Planning and Installation Guide for instruction on using the hafstab command.

2. Perform a membership reconfiguration using the instructions in Section 9.1, "Forcing a Membership Reconfiguration," on page 9-2.

   If a reconfiguration is not possible at this time, you can run the share(1M) command with the new options. Some changes may cause the fault monitoring subsystem to issue messages. For instance, a change from read-write to read-only will generate messages.