Example - Creating a Cluster File System
The following example creates a UFS cluster file system on the Solstice DiskSuite metadevice /dev/md/oracle/rdsk/d1.
# newfs /dev/md/oracle/rdsk/d1 ... (on each node) # mkdir -p /global/oracle/d1 # vi /etc/vfstab #device device mount FS fsck mount mount #to mount to fsck point type ; pass at boot options # /dev/md/oracle/dsk/d1 /dev/md/oracle/rdsk/d1 /global/oracle/d1 ufs 2 yes global,logging (save and exit) (on one node) # sccheck # mount /global/oracle/d1 # mount ... /global/oracle/d1 on /dev/md/oracle/dsk/d1 read/write/setuid/global/logging/largefiles on Sun Oct 3 08:56:16 2000 |
How to Configure Internet Protocol (IP) Network Multipathing Groups
Perform this task on each node of the cluster. If you used SunPlex Manager to install Sun Cluster HA for Apache or Sun Cluster HA for NFS, SunPlex Manager configured IP Network Multipathing groups for the public network adapters those data services use. You must configure IP Network Multipathing groups for the remaining public network adapters.
Note - All public network adapters must belong to an IP Network Multipathing group.
Have available your completed Public Networks Worksheet.
Configure IP Network Multipathing groups.
Perform procedures for IPv4 addresses in "Deploying Network Multipathing" in IP Network Multipathing Administration Guide (Solaris 8) or"Administering Network Multipathing (Task)" in System Administration Guide: IP Services (Solaris 9).
Follow these additional guidelines to configure IP Network Multipathing groups in a Sun Cluster configuration:
Each public network adapter must belong to a multipathing group.
For multipathing groups that contain two or more adapters, you must configure a test IP address for each adapter in the group. If a multipathing group contains only one adapter, you do not need to configure a test IP address.
Test IP addresses for all adapters in the same multipathing group must belong to a single IP subnet.
Test IP addresses must not be used by normal applications because the test IP addresses are not highly available.
In the /etc/default/mpathd file, do no change the value of TRACK_INTERFACES_ONLY_WITH_GROUPS from yes to no.
The name of a multipathing group has no requirements or restrictions.
Do you intend to change any private hostnames?
If no, proceed to Step 4.
If yes, go to How to Change Private Hostnames.
Did you install your own /etc/inet/ntp.conf file before you installed Sun Cluster software?
If yes, proceed to Step 5.
If no, go to How to Configure Network Time Protocol (NTP) to install or create the NTP configuration file.
Do you intend to use Sun Management Center to monitor the cluster?
If yes, go to Installing the Sun Cluster Module for Sun Management Center.
If no, install third-party applications, register resource types, set up resource groups, and configure data services. Follow procedures in the Sun Cluster 3.1 Data Service Planning and Administration Guide and in the documentation that is supplied with your application software.
How to Change Private Hostnames
Perform this task if you do not want to use the default private hostnames, clusternodenodeid-priv, that are assigned during Sun Cluster software installation.
Note - Do not perform this procedure after applications and data services have been configured and have been started. Otherwise, an application or data service might continue to use the old private hostname after the hostname is renamed, which would cause hostname conflicts. If any applications or data services are running, stop them before you perform this procedure.
Become superuser on a node in the cluster.
To work with private hostnames, type 5 (Private hostnames).
To change a private hostname, type 1 (Change a private hostname).
Follow the prompts to change the private hostname.
Repeat for each private hostname to change.
Verify the new private hostnames.
# scconf -pv | grep "private hostname" (phys-schost-1) Node private hostname: phys-schost-1-priv (phys-schost-3) Node private hostname: phys-schost-3-priv (phys-schost-2) Node private hostname: phys-schost-2-priv
Did you install your own /etc/inet/ntp.conf file before you installed Sun Cluster software?
If yes, proceed to Step 8.
If no, go to How to Configure Network Time Protocol (NTP) to install or create the NTP configuration file.
Do you intend to use Sun Management Center to monitor the cluster?
If yes, go to Installing the Sun Cluster Module for Sun Management Center.
If no, install third-party applications, register resource types, set up resource groups, and configure data services. See the documentation that is supplied with the application software and the Sun Cluster 3.1 Data Service Planning and Administration Guide.