Chapter 1 Sun Cluster 3.0 12/01 Release Notes Supplement

This document supplements the standard user documentation, including the Sun Cluster 3.0 12/01 Release Notes shipped with the Sun^TM Cluster 3.0 product. These "online release notes" provide the most current information on the Sun Cluster 3.0 product. This document includes the following information.

• "Revision Record"

• "New Features"

• "Restrictions and Requirements"

• "Known Problems"

• "Known Documentation Problems"

Revision Record

The following table lists the information contained in this document and provides the revision date for this information.

New Features

In addition to features documented in Sun Cluster 3.0 12/01 Release Notes, this release now includes support for the following features.

Generic Data Service

Appendix A, Generic Data Services provides information on the generic data service (GDS) and shows you how to create a service that uses GDS using either the command line interface or the SunPlex Agent Builder.

Scalable Cluster Topology

Appendix G, Scalable Cluster Topology provides information and procedures for using the scalable cluster topology. By using this topology with Oracle Parallel Server/Real Application Clusters (OPS/RAC) software installed on all nodes, the connectivity of up to four cluster nodes to one storage array is now supported.

Restrictions and Requirements

The following restrictions and requirements have been added or updated since the Sun Cluster 3.0 7/01 release.

Data Service Restrictions and Requirements

• Oracle 9i - Sun Cluster 3.0 software requires Patch 110651-07 or higher to support Oracle 9i. Patch 110651-07 will be available with Sun Cluster 3.0 5/02 and replaces 110651-04, which was found to break Oracle 8i functionality. Read the special installation instructions that accompany 110651-07 before you install the patch.

Upgrade Restrictions and Requirements

• Oracle Parallel Server - Sun Cluster 3.0 software does not support upgrade for Sun Cluster 2.2 configurations that run Oracle Parallel Server (OPS).

Known Problems

In addition to known problems documented in Sun Cluster 3.0 12/01 Release Notes, the following known problems affect the operation of the Sun Cluster 3.0 12/01 release.

Bug ID 4362925

Problem Summary:

nodeA# scshutdown -g0 -y
scshutdown: Unmount of /dev/md/sc/dsk/d30 failed: Device busy.
scshutdown: Could not unmount all PxFS filesystems.

The Networker packages were bundled and installed during the Oracle installation. Therefore, the nsrmmd daemon is running and mounting the /global/oracle directory, which prevents the unmount of all cluster file systems.

nodeA# umount /global/oracle
umount: global/oracle busy
nodeA# fuser -c /global/oracle
/global/oracle: 335co 317co 302co 273co 272co
nodeA# ps -ef|grep 335
 root 335 273 0 17:17:41 ?       0:00 /usr/sbin/nsrmmd -n 1
 root 448 397 0 17:19:37 console 0:00 grep 335

This problem occurs during Sun Cluster shutdown when the shutdown tries to unmount a cluster file system that the process nsrmmd is still referencing.

Workaround: Run the fuser(1M) command on each node to establish a list of all processes still using the cluster file systems that cannot be unmounted. Check that no Resource Group Manager resources have been restarted since the failed scshutdown(1M) command was first run. Kill all these processes with the kill -9 command. This kill list should not include any processes under the control of the Resource Group Manager. After all such processes have terminated, rerun the scshutdown command, and the shutdown should run to successful completion.

Bug ID 4525403

Problem Summary: VxFS installation adds the following line to the /etc/system file:

* vxfs_START -- do not remove the following lines:
*
* VxFS requires a stack size greater than the default 8K.
* The following values allow the kernel stack size
* for nfs threads to be increased to 16K.
*
set rpcmod:svc_default_stksize=0x4000
* vxfs_END

If you install VxFS after Sun Cluster software has been installed, the VxFS installation overrides the following required Sun Cluster 3.0 12/01 setting in the /etc/system file:

* Start of lines added by SUNWscr
set rpcmod:svc_default_stksize=0x6000

Workaround: Change the setting value from 0x4000 to 0x6000.

set rpcmod:svc_default_stksize=0x6000

Bug ID 4511699

Problem Summary: Sun Cluster HA for NFS requires files [SUCCESS=return] for the hosts lookup entry in the /etc/nsswitch.conf file, and requires that all cluster private IP addresses be present in the /etc/inet/hosts file on all cluster nodes.

Otherwise, Sun Cluster HA for NFS will not be able to fail over correctly in the presence of public network failures.

Workaround: Perform the following steps on each node of the cluster.

1. Modify the hosts entry in the /etc/nsswitch.conf file so that, upon success in resolving a name locally, it returns success immediately and does not contact NIS or DNS.

   hosts: cluster files [SUCCESS=return] nis dns

2. Add entries for all cluster private IP addresses to the /etc/inet/hosts file.

You only need to list the IP addresses plumbed on the physical private interfaces in the /etc/nsswitch.conf and /etc/inet/hosts files. The logical IP addresses are already resolvable through the cluster nsswitch library.

To list the physical private IP addresses, run the following command on any cluster node.

% grep ip_address /etc/cluster/ccr/infrastructure

Each IP address in this list must be assigned a unique hostname that does not conflict with any other hostname in the domain.

Sun Cluster software already requires that any HA IP addresses (LogicalHostname/SharedAddresses) be present in /etc/inet/hosts on all cluster nodes and that files is listed before nis or dns. The additional requirements mandated by this bug is to also list [SUCCESS=return] after files and to list all cluster private IP addresses in the /etc/inet/hosts file.

Bug ID 4626010

Problem Summary: In a Sun StorEdge 3900 Series system, the preconfigured, default hard zones that are used on the Sun StorEdge Network FC Switch-8 and Switch-16 switches are incompatible for use with host-based mirroring in a cluster. The hard zones prevent the cluster nodes from seeing all attached storage because there are only two ports per zone.

Workaround: Remove the default hard zones from the Sun StorEdge Network FC Switch-8 and Switch-16 switches (this is documented as a necessary step in the procedures in Appendix C, Installing and Maintaining a Sun StorEdge 3900 or 6900 Series System. See the SANbox-8/16 Switch Management User's Manual for instructions on removing the preconfigured hard zones on all Sun StorEdge Network FC Switch-8 and Switch-16 switches.

Known Documentation Problems

This section discusses documentation errors you might encounter and steps to correct these problems. This information is in addition to known documentation problems documented in the Sun Cluster 3.0 12/01 Release Notes.

Hardware Guide

The following subsections describe omissions or new information that will be added to the next publishing of the Hardware Guide.

Dynamic Reconfiguration Operations For Sun Cluster Nodes

The Sun Cluster 3.0 12/01 release supports Solaris 8 dynamic reconfiguration (DR) operations on qualified servers. The current Sun Cluster 3.0 12/01 Hardware Guide does not specifically consider scenarios in which the cluster nodes have been enabled with the DR feature.

In the Sun Cluster 3.0 12/01 Hardware Guide, some procedures require that the user add or remove host adapters or public network adapters in a cluster node. Contact your service provider for a list of storage arrays that are qualified for use with DR-enabled servers.

Review the documentation for the Solaris 8 DR feature on your hardware platform before using the DR feature with Sun Cluster software. All of the requirements, procedures, and restrictions that are documented for the Solaris 8 DR feature also apply to Sun Cluster 3.0 12/01 DR support (except for the operating environment quiescence operation).

Documentation for DR on currently qualified server platforms are listed here.

• Sun Enterprise 10000 Dynamic Reconfiguration User Guide

• Sun Enterprise 10000 Dynamic Reconfiguration Reference Manual

• Sun Fire 6800, 4810, 4800, and 3800 Systems Dynamic Reconfiguration User Guide

• Sun Fire 6800, 4810, 4800, and 3800 Systems Dynamic Reconfiguration Release Notes

• Sun Fire 15K Dynamic Reconfiguration (DR) User Guide

• Sun Fire 15K Dynamic Reconfiguration Release Notes

DR Operations in a Cluster With DR-Enabled Servers

Some procedures in the current Sun Cluster 3.0 12/01 Hardware Guide instruct the user to shut down and power off a cluster node before adding, removing, or replacing a host adapter or a public network adapter (PNA).

However, if the node is a server that is enabled with the DR feature, the user does not have to power off the node before adding, removing, or replacing the host adapter or PNA. Instead, do the following:

1. Follow the procedure steps in the Hardware Guide, including any steps for disabling and removing the host adapter or PNA from the active cluster interconnect.

   See the Sun Cluster 3.0 12/01 System Administration Guide for instructions on removing cluster host adapters (transport adapters) or PNAs from the cluster configuration.

2. Skip any step that instructs you to power off the node, where the purpose of the power-off is to add, remove, or replace a host adapter or PNA.

3. Perform the DR operation (add, remove, or replace) on the host adapter or PNA.

4. Continue with the next step of the procedure in the Hardware Guide.

For conceptual information about Sun Cluster 3.0 12/01 support of the DR feature, see the Sun Cluster 3.0 12/01 Concepts document.

Sun Netra st D1000

The Netra^TM st D1000 has been qualified for use with Sun Cluster 3.0, but maintenance procedures do not yet exist in the Sun Cluster 3.0 12/01 Hardware Guide specifically for the Netra st D1000. However, you can use the existing Sun Cluster 3.0 12/01 Hardware Guide procedures for the StorEdge D1000 to maintain a Netra st D1000 in a cluster environment. Substitute the following document references in place of the StorEdge D1000 document references if you are maintaining a Netra st D1000.

• Netra st A1000 and Netra st D1000 Installation and Maintenance Manual (805-7147)

• Netra st A1000 and Netra st D1000 Product Notes (805-7148)

Sun StorEdge T3/T3+ (Partner-Group Configuration)

Quorum Device Restriction Removed

When the Sun Cluster 3.0 12/01 Hardware Guide was published, it noted a restriction against using Sun StorEdge T3/T3+ arrays as quorum devices, when the arrays are used in a partner-group configuration.

That restriction has since been removed. That is, you can use Sun StorEdge T3/T3+ arrays as quorum devices, whether the arrays are used in a partner-group configuration or a single-controller configuration.

Sun StorEdge T3/T3+ (Single-Controller Configuration)

The Sun Cluster 3.0 12/01 Hardware Guide chapter on "Installing and Maintaining a Sun StorEdge T3 or T3+ Array Single-Controller Configuration" incorrectly indicates that the procedure for upgrading a Sun StorEdge T3 array controller to a Sun StorEdge T3+ array controller does not require any cluster-specific steps. The correct procedure should be as follows.

How To Upgrade a StorEdge T3 Controller to a StorEdge T3+ Controller

Perform this procedure on one array at a time. This procedure requires that you take the array in which you are upgrading the controller offline. If you take more than one array offline, your cluster will lose access to data, if the arrays are submirrors of each other.

1. On one node attached to the StorEdge T3 array in which you are upgrading the controller, detach that array's submirrors.

   For more information, see your Solstice DiskSuite^TM or VERITAS Volume Manager documentation.

2. Upgrade the StorEdge T3 array controller to a StorEdge T3+ array controller.

   See the Sun StorEdge T3 Array Controller Upgrade Manual for instructions.

3. Reattach the submirrors to resynchronize them.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

Software Installation Guide

The following subsections describe omissions or new information that will be added to the next publishing of the Software Installation Guide.

Maximum Number of Metadevice Names Per Diskset

The Sun Cluster 3.0 12/01 Software Installation Guide incorrectly states that the maximum number of metadevice names per diskset is 8192. The correct maximum is 1024 metadevice names per diskset.

Maximum Number of Disksets Per Cluster

The Sun Cluster 3.0 12/01 Software Installation Guide statement, "The cluster can have a maximum of 32 disksets" is misleading. The maximum number of disksets per cluster is 31, not including the diskset for private disk management.

Upgrading to a Sun Cluster 3.0 Software Update Release

The following is a correction to Step 8 of "How to Upgrade to a Sun Cluster 3.0 Software Update Release" in the Sun Cluster 3.0 12/01 Software Installation Guide.

(Optional)

(Optional) Upgrade Solaris 8 software.

1. Temporarily comment out all global device entries in the /etc/vfstab file.

   Do this to prevent the Solaris upgrade from attempting to mount the global devices.

2. Shut down the node to upgrade.

   # shutdown -y -g0 ok

3. Follow instructions in the installation guide for the Solaris 8 Maintenance Update version you want to upgrade to.

   ---

   Note -

   Do not reboot the node when prompted to reboot.

   ---

4. Uncomment all global device entries that you commented out in Step a in the /a/etc/vfstab file.

5. Install any Solaris software patches and hardware-related patches, and download any needed firmware contained in the hardware patches.

   If any patches require rebooting, reboot the node in non-cluster mode as described in Step f.

6. Reboot the node in non-cluster mode.

   Include the double dashes (--) and two quotation marks (") in the command.

   # reboot -- "-x"

Data Services Installation and Configuration Guide

The "How to Configure an iPlanet Web Server" procedure in the Sun Cluster 3.0 12/01 Data Services Installation and Configuration Guide is missing the following step, which is not dependent on any other step in the procedure.

Create a file that contains the secure key password you need to start this instance, and place this file under the server root directory. Name this file keypass.

Because this file contains the key database password, protect the file with the appropriate permissions.

Release Notes

• The following Sun Cluster 3.0 12/01 Release Notes restriction has been changed.

  Original:

  Storage devices with more than two physical paths to the enclosure - More than two paths are not supported. The Sun StorEdge A3500, for which two paths are supported to each of two nodes, is an exception.

  Revised:

  Storage devices with more than two physical paths to the enclosure - More than two paths are not supported. There are two exceptions: the Sun StorEdge^TM A3500, for which two paths are supported to each of two nodes, and EMC storage devices that use EMC PowerPath software.

• The following cluster-file-system restriction in the Sun Cluster 3.0 12/01 Release Notes has been revised to add clarification.

  Original:

  The cluster file system does not support any of the file system features of Solaris by which one would put a communication end-point in the file system name space. Therefore, you cannot create a UNIX domain socket whose name is a path name into the cluster file system, nor can you create fifos or named pipes, nor should you attempt to use fattach.

  Revised:

  The cluster file system does not support any of the file-system features of Solaris software by which one would put a communication end-point in the file-system name space. Therefore, although you can create a UNIX domain socket whose name is a path name into the cluster file system, the socket would not survive a node failover. In addition, any fifos or named pipes you create on a cluster file system would not be globally accessible, nor should you attempt to use fattach from any node other than the local node.