Sun Cluster 3.1 10/03 Release Notes Supplement
This chapter supplements the standard user documentation, including the Sun Cluster 3.1 10/03 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
- Restrictions and Requirements
- Known Problems
- Known Documentation Problems
Revision Record
The following tables list the information contained in this chapter and provides the revision date for this information.
Sun Cluster 3.1 10/03 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. |
| May 2006 | Upgrade Procedure Uses scsetup Which Does Not Yet Exist in Sun Cluster 3.0 (6349292) |
| Cluster Panics When Some Quorum Operations Are Attempted (6373967) | |
| January 2006 | Correction to procedures for mirroring the root disk. See CR 6341573. |
Sun Cluster 3.1 10/03 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 Chapter 2, 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 Chapter 3, Sun Cluster 3.1 4/04 Release Notes Supplement. |
| May 2005 | Restriction on quorum devices when using storage-based data replication. See Storage-Based Data Replication and Quorum Devices. |
| March 2005 | Process accounting log files on global file systems cause the node to hang. See Bug ID 6210418 in Chapter 2, Sun Cluster 3.1 9/04 Release Notes Supplement. |
Sun Cluster 3.1 10/03 Release Notes Supplement Revision Record: 2003/2004
| Revision Date | New Information |
|---|---|
| December 2004 | Restriction against rolling upgrade and VxVM. See Restriction on Rolling Upgrade and VxVM. |
| 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 | scsetup is not able to add the first adapter to a single-node cluster. See Bug ID 4983696. |
| Additional procedures to perform when you add a node to a single-node cluster. See Software Installation Guide. | |
| Troubleshooting tip to correct stack overflow with VxVM disk device groups. See Correcting Stack Overflow Related to VxVM Disk Device Groups. | |
| Restriction against using Live Upgrade. See Live Upgrade is Not Supported. | |
| February 2004 | Instruction to set the localonly property on any shared disks that are used to create a root disk group on nonroot disks. See Setting the localonly Property For a rootdg Disk Group on a Nonroot Disk. |
| Restriction against creating a swap file using global devices. See Create swap Files Only on Local Disks. | |
| 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 Additional Campus Cluster Configuration Examples in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS. |
| November 2003 | Procedure to upgrade Sun Cluster 3.1 10/03 software on a cluster that runs Sun StorEdge Availability Suite 3.1 . |
New Features
In addition to features documented in the Sun Cluster 3.1 10/03 Release Notes, this release now includes support for the following features.
There are no new features at this time.
Restrictions and Requirements
The following restrictions and requirements have been added or updated since the Sun Cluster 3.1 10/03 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.
Upgrading Sun Cluster 3.1 10/03 Software on Clusters That Run Sun StorEdge Availability Suite 3.1 Software
To ensure proper functioning of Sun StorEdge Availability Suite 3.1 software, you must place the configuration data for availability services on the quorum disk. Before you upgrade to Sun Cluster 3.1 10/03 software, perform the following procedure on one node in the cluster that runs Sun StorEdge Availability Suite 3.1 software.
- Use dscfg to find the device ID and the partition (slice) used by the Sun StorEdge Availability Suite 3.1 configuration file.
# /usr/opt/SUNWscm/sbin/dscfg
dev/did/rdsk/d11s7In this example, d11 is the device ID and s7 the slice of device d11.
- Identify the existing quorum device, if any.
# /usr/cluster/bin/scstat -q
–– Quorum Votes by Device ––
Device Name Present Possible Status
––––––––––- ––––––- –––––––– ––––––
Device votes: /dev/did/rdsk/d15s2 1 1 OnlineIn this example, d15s2 is the existing quorum device.
- Configure the Availability Suite 3.1 configuration data device as a quorum device.
# /usr/cluster/bin/scconf -a -q globaldev=/dev/did/rdsk/d11s2
Quorum devices do not use any of the partition space. The suffix s2 is displayed for syntax purposes only. Although they appear to be different, both Sun StorEdge Availability Suite configuration disk (for example, d11s7) and the Sun Cluster quorum disk (for example, d11s2) refer to the same disk.
- Unconfigure the original quorum device.
# /usr/cluster/bin/scconf -r -q globaldev=/dev/did/rdsk/d15s2
Note If you are installing Sun Cluster software for the first time, use a slice on the quorum disk for Sun StorEdge Availability Suite 3.1 configuration data.
Restriction on Rolling Upgrade and VxVM
Sun Cluster 3.1 10/03 software does not support rolling upgrade of a cluster that runs Veritas Volume Manager (VxVM) software. You must instead follow nonrolling upgrade procedures.
Known Problems
In addition to known problems that are documented in Sun Cluster 3.1 10/03 Release Notes, the following known problems affect the operation of the Sun Cluster 3.1 10/03 release.
Bug ID 4848612
Problem Summary: When all private interconnections fail in a two-node cluster which is running Oracle Real Application Clusters with VxVM, the first node might panic with one of the following messages:
- CMM: Cluster lost operational quorum: aborting.
- Reservation conflict.
The other node occasionally panics because the cluster reconfiguration step “cvm return” times out.
Workaround: Edit the default /opt/SUNWcvm/etc/cvm.conf file to increase the timing parameter cvm.return_timeout from 40 seconds to 160 seconds. For further inquiries, contact Brian Reynard, Software Engineering Manager OS Sustaining Escalations (Sun Cluster) at brian.reynard@sun.com.
Bug ID 4983696
Problem Summary: If scsetup is used in an attempt to add the first adapter to a single-node cluster, the following error message results: Unable to determine transport type.
Workaround: Create an empty install-db file. at least the first adapter manually:
# scconf -a -A trtype=type,name=nodename,node=nodename
After the first adapter is configured, further use of scsetup to configure the interconnects works as expected.
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 10/03 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 10/03 Software Installation Guide.
Preparing a Single-Node Cluster for Additional Nodes
How to Prepare a Single-Node Cluster for Additional Nodes
To add a node to a single-node cluster, you must first configure the cluster interconnect if it does not already exist. You must also add the name of the new node to the cluster's authorized-nodes list. In the procedure “How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall)”, perform the following additional steps before you run the scinstall command.
- From the existing cluster node, determine whether two cluster interconnects already exist.
You must have at least two cables or two adapters configured.
# scconf -p | grep cable
# scconf -p | grep adapter - Configure new cluster interconnects.
- On the existing cluster node, start the scsetup(1M) utility.
# scsetup
The Main Menu displays. - Select Cluster interconnect.
- Select Add a transport cable.
Follow the instructions to specify the name of the node to add to the cluster, the name of a transport adapter, and whether to use a transport junction. - If necessary, repeat Step c to configure a second cluster interconnect.
When finished, quit the scsetup utility. - Verify that the cluster now has two cluster interconnects configured.
# scconf -p | grep cable
# scconf -p | grep adapter
The command output should show configuration information for at least two cluster interconnects.
- On the existing cluster node, start the scsetup(1M) utility.
- Add the new node to the cluster authorized–nodes list.
- On any active cluster member, start the scsetup(1M) utility.
# scsetup
The Main Menu is displayed. - Select New nodes.
- Select Specify the name of a machine which may add itself.
- Follow the prompts to add the node's name to the list of recognized machines.
- Verify that the task has succeeded.
The scsetup utility prints the message Command completed successfully if the task completes without error. - Quit the scsetup utility.
- On any active cluster member, start the scsetup(1M) utility.
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_
Live Upgrade is Not Supported
In the procedure “How to Upgrade the Solaris Operating Environment (Nonrolling)”, the table in Step 5 is incorrect. For a cluster that uses Solstice DiskSuite/Solaris Volume Manager as the volume manager, the table's Procedure to Use column says, “Upgrading Solaris software”. It should instead say, “Any Solaris upgrade method except the Live Upgrade Method”. The Solaris Live Upgrade method is not yet supported in a Sun Cluster configuration.
Setting the localonly Property For a rootdg Disk Group on a Nonroot Disk
In the procedure “How to Create a rootdg Disk Group on a Nonroot Disk,” you must perform an additional step if the root disk group contains one or more disks that connect to two or more nodes. Perform the following step after vxinstall processing has completed.
How to Set the localonly Property For a rootdg Disk Group on a Nonroot Disk
- Enable the localonly property of the raw-disk device group for each shared disk in the root disk group.
When the localonly property is enabled, the raw-disk device group is used exclusively by the node in its node list. This usage prevents unintentional fencing of the node from the device that is used by the root disk group if that device is connected to multiple nodes.
# scconf -c -D name=dsk/dN,localonly=true
For more information about the localonly property, see the scconf_dg_rawdisk(1M) man page.
Create swap Files Only on Local Disks
If after installation you intend to create a swap file, do not create the swap file on a global device. Only use a local disk as a swap device for the node.
Sign up or Log in to add a comment or watch this page.