Sun Cluster 3.1 Release Notes Supplement
This page supplements the standard user documentation, including the Sun Cluster 3.1 Release Notes that shipped with the Sun™ Cluster 3.1 product. These “online release notes” provide the most current information on the Sun Cluster 3.1 product. This page includes the following information.
- Revision Record
- New Features
- Fixed Problems
- Restrictions and Requirements
- Known Problems
- Known Documentation Problems
Revision Record
The following tables list the information contained in this page and provides the revision date for this information.
Sun Cluster 3.1 Release Notes Supplement Revision Record: 2007
| Revision Date | New Information |
|---|---|
| September 2007 | Support of Sun StorageTek 9900 Systems as Quorum Devices in Campus Clusters |
Sun Cluster 3.1 Release Notes Supplement Revision Record: 2006
| Revision Date | New Information |
|---|---|
| June 2006 | Use of the Sun Cluster PatchPro site to obtain patches is replaced by Sun Patch Manager and Sun Update Connection. See Change to Patch Management. |
| April 2006 | Upgrade Procedure Uses scsetup Which Does Not Yet Exist in Sun Cluster 3.0 (6349292) |
| January 2006 | Correction to procedures for mirroring the root disk. See CR 6341573. |
Sun Cluster 3.1 Release Notes Supplement Revision Record: 2005
| Revision Date | New Information |
|---|---|
| September 2005 | Support is added for VxVM 4.1 and VxFS 4.1. See SPARC: Support for VxVM 4.1 and VxFS 4.1 in Sun Cluster 3.1 9/04 Release Notes Supplement. |
| June 2005 | Support is added for VxVM 4.0 and VxFS 4.0. See SPARC: Support for VxVM 4.0 and VxFS 4.0 in Sun Cluster 3.1 4/04 Release Notes Supplement. |
| March 2005 | Process accounting log files on global file systems cause the node to hang. See Bug ID 6210418 in Sun Cluster 3.1 9/04 Release Notes Supplement. |
Sun Cluster 3.1 Release Notes Supplement Revision Record: 2004
| Revision Date | New Information |
|---|---|
| November 2004 | Cabling restrictions apply when including Sun StorEdge 6130 arrays in a Sun Cluster environment. See Bug ID 5095543 for more information. |
| July 2004 | Restrictions apply to the compilation of data services that are written in C++. See Compiling Data Services That Are Written in C++. |
| March 2004 | Troubleshooting tip to correct stack overflow with VxVM disk device groups. See Correcting Stack Overflow Related to VxVM Disk Device Groups. |
| Restriction against using the Live Upgrade method to upgrade Solaris software. See Step 5 of “How to Upgrade the Solaris Operating Environment” in Appendix F, Upgrading Sun Cluster Software From Solaris 8 to Solaris 9 Software. | |
| February 2004 | Lack of support for Sun StorEdge 3310 JBOD array in a split-bus configuration has been fixed. See BugId 4818874 for details. |
| Conceptual material and example configurations for using storage-based data replication in a campus cluster. Refer to Chapter 7, Campus Clustering With Sun Cluster Software, in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS. | |
| January 2004 | Added a brief description of the newly supported 3–room, 2–node campus cluster. See Chapter 7, Campus Clustering With Sun Cluster Software, in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS. |
Sun Cluster 3.1 Release Notes Supplement Revision Record: 2003
| Revision Date | New Information |
|---|---|
| December 2003 | Sun StorEdge 6120 storage arrays in dual-controller configurations and Sun StorEdge 6320 storage systems were limited to four nodes and 16 LUNs. The bug was fixed (see Bug ID 4840853). |
| November 2003 | The onerror=lock and onerror=umount mount options are not supported on cluster file systems. See Bug ID 4781666. |
| To upgrade a cluster that uses mediators, you must remove the mediators before you upgrade to Sun Cluster 3.1 software, then recreate the mediators after the cluster software is upgraded. See Upgrading a Cluster That Uses Mediators. | |
| Additional information about the restriction on IPv6 addressing. See Clarification of the IPv6 Restriction. | |
| Logical volumes are not supported with the Sun StorEdge 3510 FC storage array. See the Preface of the Sun Cluster 3.0-3.1 With Sun StorEdge 3510 or 3511 FC RAID Array Manual for more information. | |
| October 2003 | Certain RPC program numbers are reserved for Sun Cluster software use. See Reserved RPC Program Numbers. |
| Clarification about which name to use for disk slices when you create state database replicas. See How to Create State Database Replicas. | |
| Upgrade from Sun Cluster 3.0 software on the Solaris 8 Operating System to Sun Cluster 3.1 software on the Solaris 9 Operating System removes dual-string mediators. See Bug ID 4920156. | |
| Updated VxVM Dynamic Multipathing (DMP) restrictions. See Dynamic Multipathing (DMP) for more information. | |
| August 2003 | Procedures to enable Sun Cluster Support for Oracle Real Application Clusters on a subset of cluster nodes. See Sun Cluster Support for Oracle Real Application Clusters on a Subset of Cluster Nodes. |
| July 2003 | Revised support for Multiple Masters configuration of Sun Cluster HA for Sun ONE Application Server. See Sun Cluster 3.1 Data Service for Sun ONE Application Server. |
| June 2003 | Procedures to upgrade a Sun Cluster 3.0 configuration to Sun Cluster 3.1 software, including upgrading from Solaris 8 to Solaris 9 software. See Appendix F, Upgrading Sun Cluster Software From Solaris 8 to Solaris 9 Software. |
| Modifications to make to the /etc/system file to correct changes made by VxFS installation. See Changing Quorum Device Connectivity. | |
| Procedures to support Sun StorEdge 6320 storage systems. See Chapter 1, Installing and Maintaining a Sun StorEdge 6320 System, in Sun Cluster 3.0-3.1 With Sun StorEdge 6320 System Manual for Solaris OS. | |
| Sun StorEdge 6120 storage arrays in dual-controller configurations and Sun StorEdge 6320 storage systems were limited to four nodes and 16 LUNs. (See Bug ID 4840853.) This restriction has been removed for clusters using the 3.1 firmware. |
|
| Procedures to support Sun StorEdge 3510 FC storage device. See the Sun Cluster 3.0-3.1 With Sun StorEdge 3510 or 3511 FC RAID Array Manual. | |
| Sun StorEdge 3510 FC storage arrays are no longer limited to 256 LUNs per channel. See Bug ID 4867584. | |
| Sun StorEdge 3510 FC storage arrays are limited to one node per channel. See Bug ID 4867560. | |
| Requirements for storage topologies. See Storage Topologies Replaced by New Requirements. | |
| Relaxed requirements for shared storage. See Shared Storage Restriction Relaxed. |
New Features
In addition to features documented in the Sun Cluster 3.1 Release Notes, this release now includes support for the following features.
Sun Cluster Support for Oracle Real Application Clusters on a Subset of Cluster Nodes
To enable Sun Cluster Support for Oracle Real Application Clusters on a subset of cluster nodes, see Sun Cluster Support for Oracle Real Application Clusters on a Subset of Cluster Nodes.
Restrictions and Requirements
The following restrictions and requirements have been added or updated since the Sun Cluster 3.1 release.
Compiling Data Services That Are Written in C++
If you are using Sun Cluster 3.1 and are writing data services in C++, you must compile these data services in ANSI C++ standard mode.
Reserved RPC Program Numbers
If you install an RPC service on the cluster, the service must not use any the following program numbers:
- 100141
- 100142
- 100248
These numbers are reserved for the Sun Cluster daemons rgmd_receptionist, fed, and rgmd, respectively. If the RPC service you install also uses one of these program numbers, you must change that RPC service to use a different program number.
Changing Quorum Device Connectivity
When you increase or decrease the number of node attachments to a quorum device, the quorum vote count is not automatically recalculated. You can reestablish the correct quorum vote if you remove all quorum devices and then add them back into the configuration.
Required VxFS Default Stack Size Increase
The default stack size that Veritas File System (VxFS) sets during installation is 0x4000. However, this is inadequate for Sun Cluster software and might lead to a system panic. If you install VxFS on a Sun Cluster configuration, you must reset the stack size by making the following modifications to entries in the /etc/system file on each cluster node.
set rpcmod:svc_default_stksize=0x{{8}}000
set lwp_default_stksize=0x6000
- The first line changes the value for the rpcmod:svc_default_stksize variable from 0x4000 to 0x8000.
- The second line sets the value of the lwp_default_stksize variable to 0x6000.
Clarification of the IPv6 Restriction
Sun Cluster software does not support IPv6. However, network interfaces on a cluster node can host IPv6 addressing as long as those interfaces are not used by Sun Cluster services or facilities.
Support of Sun StorageTek 9900 Systems as Quorum Devices in Campus Clusters
Sun StorageTek 9900 systems are now supported as quorum devices in campus cluster configurations. The following patches are required:
- 117950-31 Sun Cluster 3.1: CORE patch for Solaris 8
- 117949-31 Sun Cluster 3.1: CORE patch for Solaris 9
- 117909-31 Sun Cluster 3.1_x86: CORE patch for Solaris 9_x86
- 120500-16 Sun Cluster 3.1: CORE patch for Solaris 10
- 120501-16 Sun Cluster 3.1_x86: CORE patch for Solaris 10_x86
Support of Sun StorageTek 9900 Systems as Quorum Devices in Campus Clusters
Sun StorageTek 9900 systems are now supported as quorum devices in campus cluster configurations. The following patches are required:
- Sun Cluster 3.1: 117950-31 CORE patch for Solaris 8
- Sun Cluster 3.1: 117949-31 CORE patch for Solaris 9
- Sun Cluster 3.1: 117909-31 CORE patch for Solaris 9x
(For the above 3 patches, the original rev the fix went
into was not released. Please use the rev listed here
which incorporates the fix required.) - Sun Cluster 3.1: 120500-15 CORE patch for Solaris 10
- Sun Cluster 3.1: 120501-15 CORE patch for Solaris 10x
Fixed Problems
The following problems identified in previous release notes supplements are now resolved.
Bug ID 4840853
Problem Summary: Due to memory segmentation issues, if you configured the StorEdge 6120 or StorEdge 6320 storage system with four nodes and more than 16 LUNs, the storage device might fail and cause your data to be compromised.
Problem Fixed: When using a StorEdge 6120 or StorEdge 6320 storage system with the version 3.1 firmware (or later), you no longer must limit your configuration to 16 LUNs. Instead, the limit is 64 LUNs.
Bug ID 4867584
Problem Summary: If you had 512 LUNs in a direct-attach storage configuration with Sun StorEdge 3510 FC storage arrays, LUNs might be lost when the server rebooted.
Problem Fixed: This bug is fixed when using both of the following items:
- 3.27R firmware or later (which is contained in patch 113723-07 or later)
- SAN Foundation Kit 4.3 Software or later
Known Problems
In addition to known problems documented in the Sun Cluster 3.1 Release Notes, the following known problems affect the operation of the Sun Cluster 3. 1 release.
Bug ID 4781666
Problem Summary: Use of the onerror=umount mount option or the onerror=lock mount option might cause the cluster file system to lock or become inaccessible if the cluster file system experiences file corruption. Or, use of these mount options might cause the cluster file system to become unmountable. The cluster file system might then cause applications to hang or prevent them from being killed. The node might require rebooting to recover from these states.
Workaround: Do not specify the onerror=umount or onerror=lock}}mount option. The {{onerror=panic mount option, which is supported by Sun Cluster software, does not need to be specified. It is already the default value.
Bug ID 4863254
Problem Summary: Due to a Solaris bug (4511634), Sun Cluster 3.1 does not provide the ability to auto-create IPMP groups when you add a logical host.
Workaround: You must manually create an IPMP group when you add a logical host.
Bug ID 4867560
Problem Summary: When two nodes are connected to the same channel of a Sun StorEdge 3510 FC storage array, rebooting one node causes the other node to lose the SCSI-2 reservation.
Workaround: You can only connect one node per channel on the Sun StorEdge 3510 FC storage arrays.
Bug ID 4920156
Problem Summary: When performing an upgrade from Sun Cluster 3.0 software on Solaris 8 software with Solstice DiskSuite 4.2.1 to Sun Cluster 3.1 software on Solaris 9 software with Solaris Volume Manager, the dual-string mediators are removed.
Workaround: Remove mediators before you upgrade the cluster, then recreate them after the cluster is upgraded.
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.1 Release Notes.
Software Installation Guide
The following subsections describe omissions or new information that will be added to the next publication of the Sun Cluster 3.1 Software Installation Guide.
Correcting Stack Overflow Related to VxVM Disk Device Groups
If you experience a stack overflow when a VxVM disk device group is brought online, the default value of the thread stack size might be insufficient. To increase the thread stack size, add the following entry to the /etc/system on each node. Set the value for size to a number that is greater than 8000, which is the default setting.
set cl_comm:rm_thread_stacksize=0x_size_
Upgrading a Cluster That Uses Mediators
To upgrade a Sun Cluster 3.0 configuration that uses mediators to Sun Cluster 3.1 software, you must unconfigure the mediators before you upgrade the cluster software. Then after you upgrade the cluster software you must reconfigure the mediators. Add the following steps to the procedures that you perform from Upgrading Sun Cluster Software in Sun Cluster 3.1 Software Installation Guide.
How to Upgrade a Cluster That Uses Mediators
- Perform the steps to prepare the cluster for upgrade but do not shut down the cluster.
- Unconfigure the mediators.
- Run the following command to verify that no mediator data problems exist.
# medstat -s setname
-s setname-
Specifies the diskset name
If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure to fix bad mediator data in Configuring Mediators in Sun Cluster 3.1 Software Installation Guide. - List all mediators.
Use this information for when you restore the mediators during Step 4. - For a diskset that uses mediators, take ownership of the diskset if no node already has ownership.
# metaset -s setname -t
-t
Takes ownership of the diskset
- Unconfigure all mediators for the diskset.
# metaset -s setname -d -m mediator-host-list
-s setname-
Specifies the diskset name
-d
Deletes from the diskset
-m mediator-host-list-
Specifies the name of the node to remove as a mediator host for the diskset
See the mediator(7D) man page for further information about mediator-specific options to the metaset command. - Repeat Step 3 through Step 4 for each remaining diskset that uses mediators.
- Run the following command to verify that no mediator data problems exist.
- Shut down the cluster and continue to follow procedures to upgrade Sun Cluster software.
- After all nodes are upgraded and booted back into the cluster, reconfigure the mediators.
- Determine which node has ownership of a diskset to which you will add the mediator hosts.
# metaset -s setname
-s setname-
Specifies the diskset name
- If no node has ownership, take ownership of the diskset.
# metaset -s setname -t
-t
Takes ownership of the diskset
- Recreate the mediators.
# metaset -s setname -a -m mediator-host-list
-a
Adds to the diskset
-m mediator-host-list-
Specifies the names of the nodes to add as mediator hosts for the diskset
- Repeat Step 1 through Step 3 for each diskset in the cluster that uses mediators.
- Determine which node has ownership of a diskset to which you will add the mediator hosts.
- Perform any remaining upgrade tasks to complete cluster upgrade.
How to Create State Database Replicas
When you use the metadb -af command to create state database replicas on local disks, use the physical disk name (cNtXdYsZ), not the device-ID name (dN), to specify the slices to use.
Sign up or Log in to add a comment or watch this page.