(English) Sun Cluster 3.2 1-09 Release Notes

{anchor:top}This document provides the following information for Sun™ Cluster 3.2 1/09 software.
* [What's New in the Sun Cluster 3.2 1/09 Software|#GCVSS]
* [Features Nearing End of Life|#EOL]
* [Compatibility Issues|#FRYNU]
* [Commands Modified in This Release|#FNCMB]
* [Product Name Changes|#ProductNameChanges]
* [Supported Products|#RELNOTES-6-PRODUCTS]
* [Sun Cluster Security Hardening|#CJAEBGFD]
* [Known Issues and Bugs|#CHDGGECB]
* [Patches and Required Firmware Levels|#CHDHEHGF]
* [Sun Cluster 3.2 1/09 Documentation|#CHDGCEDD]
* [Documentation Issues|#CJACJJJD]

[Top|#top]

h1. {anchor:GCVSS} What's New in the Sun Cluster 3.2 1/09 Software

This section provides information related to new features, functionality, and supported products in the Sun Cluster 3.2 1/09 software.

h2. {anchor:GCVSV} New Features and Functionality

The following new features and functionality are provided in patches to Sun Cluster 3.2 1/09 software:

* [EMC SRDF Data Recovery|#emcsrdf]
* [Sun Storage 7000 Unified Storage Systems With Oracle RAC|#ss7000]
* [Sun Storage J4200/J4400 SATA Arrays|#j4200]
{excerpt:hidden=true}\*[Native SKGXN Support|#SKGXN]
{excerpt}

The following new features and functionality are provided in the initial Sun Cluster 3.2 1/09 release:

* [Cluster Configuration Checker|#check]
* [Data Service for Informix|#informix]
* [Exclusive-IP Zones Support|#xip]
* [Global-Devices Namespace on a {{lofi}} Device|#opt-gdfs]
* [IPsec on the Cluster Interconnect|#ipsec]
* [Optional Fencing|#opt-fencing]
* [PostgreSQL WAL Shipping Support|#wal]
* [Quorum|#quorum]
** [Quorum Monitoring|#qmonitor]
** [Software Quorum|#swquorum]
** [New Automated Response to a Change in Quorum-Device Status|#autoq]
* [Solaris Containers Clusters, or Zone Clusters|#zc]
* [ZFS Root File Systems, Except the Global-Devices Namespace|#zfsboot]

[Top|#top]

h3. {anchor:check} Cluster Configuration Checker{excerpt:hidden=true}1535{excerpt}

The {{sccheck}} command is replaced by the {{cluster check}} command. The new {{check}} subcommand performs the same role as {{sccheck}}. In addition, a new {{cluster list-checks}} command is added, which displays a list of all available cluster configuration checks.

For details about the {{check}} and {{list-checks}} subcommands, see the [{{cluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cluster-1cl] man page.

[Top|#top]

h3. {anchor:informix} Data Service for Informix

A new data service is added for Informix. This data service is supported on the Solaris 10 OS for both SPARC® based platforms and x86 based platforms.

[Top|#top]

h3. {anchor:emcsrdf}Support EMC SRDF Data Recovery After a Complete Failure in a Primary Room

A patch to Sun Cluster 3.2 1/09 software changes Sun Cluster behavior so that if the primary campus cluster room fails, Sun Cluster automatically fails over to the secondary room. The patch makes the secondary room's storage device readable and writable, and enables the failover of the corresponding device groups and resource groups. When the primary room returns online, you can manually run the procedure that recovers the data from the EMC Symmetrix Remote Data Facility (SRDF) device group by resynchronizing the data from the original secondary room to the original primary room.

The following are the minimum patch versions that contain this new functionality:
* Solaris 10 SPARC - 126106-30
* Solaris 10 x86 - 126107-31
* Solaris 9 - 126105-29

For more information, see the procedure in the Documentation Issues section for the [System Administration Guide|#SYSADMIN].

[Top|#top]

h3. {anchor:xip} Exclusive-IP Zones Support

Support of {{SUNW.LogicalHostname}} resources is added for non-global zones with {{ip-type=exclusive}}. Such zones can have complete network isolation from the global zone and from one another, with their own network interfaces, routing, filtering, IPMP groups, and so forth. You can now use zones with {{ip-type=exclusive}} to host network resources of type {{SUNW.LogicalHostname}} that are used by failover data services. The use of zones with {{ip-type=exclusive}} is not available for scalable data services or with zone clusters.

For clusters that upgrade to the Sun Cluster 3.2 1/09 release, you must upgrade the {{SUNW.LogicalHostname}} resource to version 3 to make this feature available to the cluster. For new installations of Sun Cluster 3.2 1/09 software, this feature is automatically available.

[Top|#top]

h3. {anchor:opt-gdfs} Global-Devices Namespace on a {{lofi}} Device {excerpt:hidden=true}1483{excerpt}

On the Solaris 10 OS, as an alternative to creating the global-devices namespace on a dedicated partition, you can instead choose to create the namespace on a lofi device. This feature is particularly useful if you are installing Sun Cluster software on systems that are pre-installed with the Solaris 10 OS.

This feature is not available on the Solaris 9 OS.

For more information, see [New Choice for the Location of the Global-Devices Namespace|#opt-gdfs-info].

[Top|#top]

h3. {anchor:ipsec} IPsec on the Cluster Interconnect

Support is added to use IP Security Architecture (IPsec) on the cluster private interconnect. For details, see ["How to Configure IP Security Architecture (IPsec) on the Cluster Interconnect"|http://docs.sun.com/app/docs/doc/820-4677/ghqmg] in the _Sun Cluster Software Installation Guide_.

[Top|#top]

h3. {anchor:opt-fencing} Optional Fencing

You can now use the {{cluster}} command to set a default value for fencing that is applied to all storage devices. You can also now use the new {{default_fencing}} property with the {{cldevice}} command to enable or disable fencing for particular devices. If you disable fencing on a device, Sun Cluster software performs neither SCSI-2 nor SCSI-3 reservation-related operations on that device.

The {{default_fencing}} property replaces the {{localonly}} raw-disk device group property that you used to turn off fencing for devices in specific situations. The {{localonly}} property remains available, however, as you still need it to create local VxVM device groups.

For details, see ["Administering the SCSI Protocol Settings for Storage Devices"|http://docs.sun.com/app/docs/doc/820-4679/6ng4k5s24?a=view] in the _Sun Cluster System Administration Guide_ and the [{{cluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cluster-1cl] and [{{cldevice}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cldevice-1cl] man pages.{excerpt:hidden=true}IS THIS A HOLE IN THE DOCS? This feature also introduces to the {{clquorum}} command the new quorum type {{software_quorum}}.{excerpt}[Top|#top]

h3. {anchor:wal} PostgreSQL WAL Shipping Support

The Sun Cluster data service for PostgreSQL now supports PostgreSQL Write Ahead Log (WAL) shipping. WAL shipping provides the ability to support log shipping functionality as a replacement for shared storage, thus eliminating the need for shared storage in a cluster when using PostgreSQL databases. This feature provides support for PostgreSQL database replication between two different clusters or between two different PostgreSQL failover resources within one cluster.

For details, see the [_Sun Cluster Data Service for PostgreSQL Guide_|http://docs.sun.com/app/docs/doc/820-5074].

[Top|#top]

h3. {anchor:quorum} Quorum Enhancements

New quorum features are available, as described in the following sections.

h4. {anchor:swquorum} Software Quorum

Sun Cluster software now supports a new protocol called "software quorum". Software quorum implements all Sun Cluster quorum device operations entirely in software. Software quorum does not use SCSI-2 or SCSI-3 reservation-related operations. Consequently, you can now use any kind of shared disk with Sun Cluster software. For example, you can now use Serial Advanced Technology Attachment (SATA) devices as well as solid-state storage devices as quorum devices.

To use a shared disk with software quorum, you first need to turn off SCSI fencing for that device. When you subsequently configure the device as a quorum device, Sun Cluster software determines that SCSI fencing for the device is turned off and automatically uses software quorum. Note, however, that Sun Cluster still supports the SCSI-2 and SCSI-3 protocols with shared disks.

Software quorum provides a level of data-integrity protection comparable to SCSI-2-based fencing.

[Top|#top]

h4. {anchor:qmonitor} Quorum Monitoring

This new feature periodically probes all configured quorum devices and sends notification to {{syslog}} if a quorum device fails. You can monitor {{syslog}} for quorum-device failures and proactively replace a failed quorum device before node reconfiguration occurs.

[Top|#top]

h4. {anchor:autoq} New Automated Response to a Change in Quorum Device Status

In previous Sun Cluster releases, if a configured quorum device stopped working, the cluster would subsequently ignore the quorum device completely. If such a quorum device became functional again, the user needed to unconfigure and then reconfigure the device, to return it to use as a quorum device in the cluster. Alternatively, the user could reboot the entire cluster.

This release changes the quorum device behavior. Now when the cluster encounters a problem with a quorum device, such as during a node reconfiguration, the cluster automatically takes the quorum device offline.

The new quorum-monitoring feature periodically checks the status of all configured quorum devices and initiates the following actions:

* Takes offline any quorum device that is not working properly.
* Brings online any formerly nonfunctional quorum device whose problem is resolved, and loads the quorum device with the appropriate information.

Any changes in the status of quorum devices are accompanied by notifications on {{syslog}}.

The following is one example of how this feature can affect cluster behavior. When a quorum device is located on a different network than the cluster nodes, transient network problems might cause communication failures. The quorum-monitoring feature automatically detects a communication
failure and takes the quorum device offline. Similarly, when communications are restored, the quorum-monitoring feature automatically brings the quorum device back online.

If you check the status of quorum devices by using the {{clquorum status}} command, or if the cluster undergoes a reconfiguration, the software performs the same actions that the quorum monitor does upon detecting a change in quorum-device status.

In addition, if you check the status of quorum devices by using the {{clquorum status}} command, the command now reports the present status of quorum devices, rather than report the status as of the last cluster reconfiguration.

[Top|#top]

h3. {anchor:zc} Solaris Containers Clusters, or Zone Clusters

On the Solaris 10 OS, with this release of Sun Cluster software you can now create a Solaris Containers cluster, simply called a _zone cluster_. The new zone-cluster feature is a virtual cluster, where each virtual node is a {{cluster}} brand zone. A zone cluster provides the following primary features:
* Cluster application fault isolation
* Security isolation
* Resource management
* License fee cost containment
* Cluster application consolidation

A zone cluster is a simplified cluster that only contains those resources that are directly used by applications. There can be any number of zone clusters, and each zone cluster can run any number of applications.

The first data service that has been qualified to run in a zone cluster is Oracle RAC, including all RAC software, such as the data base instances, CRS, and ASM. You can also run user-developed applications that run with RAC. As additional data services become qualified to run in a zone cluster, they will be added to [Zone Cluster Support|#zcsupport] in this Release Notes.

For details about configuring a zone cluster, see ["Configuring a Zone Cluster"|http://docs.sun.com/app/docs/doc/820-4677/ggzen?a=view] in the _Sun Cluster Software Installation Guide_ and the [{{clzonecluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/clzonecluster-1cl] man page.

For a discussion of the terminology that was changed related to virtual clusters, see ["Introduction to the Sun Cluster Environment"|http://docs.sun.com/app/docs/doc/820-4676/6ng4haa94?a=view] in the _Sun Cluster Concepts Guide_.

[Top|#top]

h3. {anchor:ss7000}Support for Sun Storage 7000 Unified Storage Systems With Oracle RAC

Sun Cluster 3.2 1/09 software now supports Sun Storage 7000 Unified Storage Systems, for use with Oracle RAC in the following configurations:

* Up to four SPARC nodes
* At least Oracle RAC 10.2.0.4 10g Release 2 or Oracle RAC 11.1.0.7 11g software
* NFS file systems are used for Oracle RAC database files

No data services other than Oracle RAC are currently supported for use with these storage systems.

Observe the following guidelines when you use Sun Storage 7000 Unified Storage Systems with NFS file systems in a cluster configuration:

* You can use an iSCSI LUN from the storage system as a cluster quorum device. You must disable fencing for the LUN, which automatically enables the use of the software quorum protocol. For information about configuring a quorum device with fencing disabled, follow instructions in [How to Configure Quorum Devices |http://docs.sun.com/app/docs/doc/820-4677/cihecfab?a=view] in the _Sun Cluster Software Installation Guide_.

* When Oracle RAC is installed in the global zone, you can also use NFS file systems for Oracle Clusterware OCR and Voting disks.

* When Oracle RAC is installed in a zone cluster, you must use iSCSI LUNs from Sun Storage 7000 Unified Storage Systems as OCR and Voting devices. You cannot use NFS file systems in this configuration due to a problem with Oracle Clusterware's detection of NFS mount options when running inside a non-global zone.

* If you use iSCSI LUNs for Oracle Clusterware OCR and Voting disks, either in the global zone or in a zone cluster, configure the corresponding Sun Cluster DID devices with fencing disabled. Use Sun Cluster DID device paths, not Solaris device paths, to reference those LUNs. For instructions to disable fencing globally or for individual disks, see procedures in [Administering the SCSI Protocol Settings for Storage Devices |http://docs.sun.com/app/docs/doc/820-4679/gbmid?a=view]. For instructions to add a raw device to a zone cluster, see [How to Add a Raw-Disk Device to a Zone Cluster |http://docs.sun.com/app/docs/doc/820-4677/ghsby?a=view].

* Use the mount options that are required by Oracle RAC for NFS file systems. See [Oracle{_}MetaLink_|https://metalink.oracle.com/] bulletin 359515.1, "Mount Options for Oracle Files When Used with NAS Devices".

* Set the {{mount at boot}} option to {{yes}} in the {{/etc/vfstab}} file to automate the NFS file systems mount.

Example:
{code}
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
...
qualfugu:/export/oracrs - /data/crs nfs 2 yes rw,bg,forcedirectio,wsize=32768,rsize=32768,hard,noac,nointr,proto=tcp,vers=3
qualfugu:/export/oradb - /data/db nfs 2 yes rw,bg,forcedirectio,wsize=32768,rsize=32768,hard,noac,nointr,proto=tcp,vers=3
{code}

* At this time, you cannot use the Sun Cluster {{clnas}} command to register Sun Storage 7000 Unified Storage Systems with the cluster.

* When you configure the RAC framework and RAC proxy resources, either by using the RAC wizard or by using maintenance commands, use the procedure for hardware RAID storage management and not for NAS NFS. See [Sun Cluster Data Service for Oracle RAC Guide |http://docs.sun.com/app/docs/doc/820-5043].

[Top|#top]

h3. {anchor:j4200}Support for Sun Storage J4200/J4400 SATA Arrays

{excerpt:hidden=true}This information needs to be moved to the appropriate user manual in the next release.{excerpt}Sun Cluster 3.2 1/09 software now supports the use of Sun Storage J4200 and J4400 arrays with SATA HDDs in a cluster configuration. Sun Storage J4200 and J4400 storage arrays with SATA drives rely on an internal STP/SATA bridge, which handles the mapping to SATA. Storage arrays with SATA drives have certain limitations that must be taken into consideration in a Sun Cluster configuration. Observe the following requirements and guidelines when you configure dual-ported Sun Storage J4200 and J4400 SATA drives for use in a Sun Cluster configuration:

* *SATA constraint* \- Because of the SATA protocol's point-to-point nature, only one initiator can be affiliated with a SATA drive on each J4200 or J4400 array's SIM card.
* *Cabling*\- To work around the SATA protocol constraints, the cabling layout from hosts to the J4200 or J4400 arrays might expose the SIMs and the HBAs as a single point of failure in certain configurations. Figure 2 shows an example of such a configuration.
* *Initiators* \- You must use one initiator from a host to a SIM card, as shown in Figures 1 and 2.

* *Disabling global fencing*\- You must disable global fencing for all disks in the SATA storage array. This is required regardless of whether any SATA disks are to be used as a quorum device or simply as shared storage.
** To disable fencing during initial cluster configuration, run the {{scinstall}} utility in Custom Mode. When prompted by the utility whether to disable global fencing, respond "Yes".
** To disable fencing of all storage devices in the cluster after the cluster is established, follow instructions in ["How to Change the Default Global Fencing Protocol Settings for All Storage Devices"|http://docs.sun.com/app/docs/doc/820-4679/gbyxq?a=view] in the _Sun Cluster System Administration Guide_ to set the {{global_fencing}} property to {{nofencing_noscrub}}. Alternatively, follow instructions in ["How to Change the Fencing Protocol for a Single Storage Device"|http://docs.sun.com/app/docs/doc/820-4679/gbmhm?a=view] to set the {{default_fencing}} property of each SATA disk to {{nofencing_noscrub}}.

For more information about setting up Sun Storage J4200 or J4400 arrays, see the _Sun Storage J4200/J4400 Array System Overview_ at [http://docs.sun.com/source/820-3223-11/] and the _Sun Storage J4200/J4400 Array System Hardware Installation Guide_ at [http://docs.sun.com/app/docs/doc/820-3218-11].

[Top|#top]

h3. {anchor:zfsboot}ZFS Root File Systems, Except the Global-Devices Namespace

This release supports the use of ZFS for root file systems, with one significant exception. If you use a dedicated partition of the boot disk for the global-devices file system, you must use only UFS as its file system. The global-devices namespace requires the proxy file system (PxFS) running on a UFS file system.

However, a UFS file system for the global-devices namespace can coexist with a ZFS file system for the root ({{/}}) file system and other root file systems, for example, {{/var}} or {{/home}}. Alternatively, if you instead use a [lofi device|#opt-gdfs] to host the global-devices namespace, there is no limitation on the use of ZFS for root file systems.

[Top|#top]


h1. {anchor:EOL} Features Nearing End of Life

The following feature is nearing end of life in Sun Cluster software.

h2. Solaris 9

Sun Cluster support for the Solaris 9 OS might no longer be supported in a future release.

[Top|#top]

h1. {anchor:FRYNU} Compatibility Issues

* [Accessibility Features for People With Disabilities|#GAEIL]
* [GlassFish with Sun Cluster Data Service for Sun Java System Application Server|#GlassFish]
* [Loopback File System (LOFS)|#GEEES]
* [SAP 7.1 with Sun Cluster Data Service for SAP Web Application Server|#SAP7.1]
* [Oracle RAC Clusters With Solaris Volume Manager|#rac16node]
* [Shared QFS With Solaris Volume Manager for Sun Cluster|#sharedQFS]
* [Solaris 10 Patch 137137-09/137138-09 Causes ZFS Pool Corruption|#zfspoolpatch]
* [Solaris Trusted Extensions|#trusted]
* [Solaris Volume Manager GUI|#GEEER]
* [ZFS Root Disk Encapsulation|#zfsrootdg]

This section contains information about Sun Cluster compatibility issues.
* Additional Sun Cluster framework compatibility issues are documented in ["Planning the Sun Cluster Configuration"|http://docs.sun.com/app/docs/doc/820-2555/6ne5aih74?a=view] in _Sun Cluster Software Installation Guide for Solaris OS_.
* Additional Sun Cluster upgrade compatibility issues are documented in ["Upgrade Requirements and Software Support Guidelines"|http://docs.sun.com/app/docs/doc/820-2270/6ndsqp0sv?a=view] in _Sun Cluster Upgrade Guide for Solaris OS_.
* For other known problems or restrictions, see [Known Issues and Bugs|#CHDGGECB].

[Top|#top]

h2. {anchor:GAEIL}Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments that are available from Sun on request to determine which versions are best suited for deploying accessible solutions.

[Top|#top]

h2. {anchor:GlassFish}GlassFish with Sun Cluster Data Service for Sun Java System Application Server

In GlassFish V2 UR2, the Domain Administration Server (DAS) takes a long time to start if the node agent's host is not online. This behavior is due to an existing bug in GlassFish. To support GlassFish V2 UR2 in a Sun Cluster environment, ensure that node-agent hosts are online before you bring the DAS resource online. For detailed information about the bug, see [GlassFish Bug 5057|https://glassfish.dev.java.net/issues/show_bug.cgi?id=5057].

[Top|#top]

h2. {anchor:GEEES}Loopback File System (LOFS)

Sun Cluster 3.2 1/09 software does not support the use of LOFS under certain conditions. If you must enable LOFS on a cluster node, such as when you configure non-global zones, first determine whether the LOFS restrictions apply to your configuration. See the guidelines in ["Solaris OS Feature Restrictions"|http://docs.sun.com/app/docs/doc/820-2555/6ne5aih77?a=view#ch1planning-5003] in _Sun Cluster Software Installation Guide for Solaris OS_ for more information about the restrictions and workarounds that permit the use of LOFS when restricting conditions exist.

[Top|#top]

h2. {anchor:rac16node}(SPARC) Oracle RAC Clusters With Solaris Volume Manager

Due to CR 6580729, Solaris Volume Manager support is not available on SPARC based clusters with more than eight nodes that run Oracle RAC.

[Top|#top]

h2. {anchor:SAP7.1}SAP 7.1 with Sun Cluster Data Service for SAP Web Application Server

The following SAP 7.1 issues affect the operation of the Sun Cluster Data Service for SAP:
* In the Sun Cluster environment for SAP 7.1, the SAP Web Application Server goes to {{STOP_Failed}} mode after a public-network failure. After a public-network failure, the resource should fail over instead of going to {{STOP_Failed}} mode. Refer to SAP note 888312 to resolve this issue.
* {excerpt:hidden=true}CR 6759302{excerpt} The SAP Web Application Server probe returns an error message with status {{Degraded}} after switchover of the {{enq-msg}} resource group. Once the switchover of the {{enq-msg}} resource is complete, the SAP Web Application Server restarts due to a dependency on the messaging server. The restart of the SAP Web Application Server fails and returns the error message {{error 503 service unavailable}}. Refer to SAP note 966416 and follow the instructions to remove all {{krnlreg}} entries from the profile, to prevent deadlock situations.

[Top|#top]

h2. {anchor:sharedQFS}Shared QFS With Solaris Volume Manager for Sun Cluster

The following behavior has been reported on x86 Oracle RAC configurations with one or more Sun StorageTek QFS shared file systems that mount devices from multiowner disksets of Solaris Volume Manager for Sun Cluster (CR 6655081).

If the QFS file system metadata server is located on a node that is not the master node of the disk set and that node loses all storage connectivity, Oracle CRS will reboot the node. At the same time, the other nodes that are QFS metadata client nodes might experience errors writing to related database files. The write error condition corrects itself when the Oracle RAC instances are restarted. This restart should be an automatic recovery action by Oracle CRS, after the QFS metadata server and Solaris Volume Manager automatic recovery has been completed by Sun Cluster software.

[Top|#top]

h2. {anchor:zfspoolpatch}Solaris 10 Patch 137137-09/137138-09 Causes ZFS Pool Corruption

A change to the {{zpool_import()}} management of the {{zpool.cache}} file, as delivered by Solaris 10 kernel patches 137137-09 (for SPARC) or 137138-09 (for x86), might cause systems that have their shared ZFS (zfs(1M)) storage pools under the control of HAStoragePlus to be simultaneously imported on multiple cluster nodes. Importing a ZFS storage pool on multiple cluster nodes will result in pool corruption, which might cause data integrity issues or cause a cluster node to panic.

To avoid this problem, install Solaris 10 patch 139579-02 (for SPARC) or 139580-02 (for x86) immediately after you install 137137-09 or 137138-09 but before you reboot the cluster nodes.

Alternatively, only on the Solaris 10 5/08 OS, remove the affected patch before any ZFS pools are simultaneously imported to multiple cluster nodes. You cannot remove patch 137137-09 or 137138-09 from the Solaris 10 10/08 OS, because these patches are preinstalled on that release.

For more information, see Sun Alert 245626.

[Top|#top]

h2. {anchor:trusted}Solaris Trusted Extensions

Starting with the Solaris 10 11/06 release, the Solaris 10 OS includes support for Solaris Trusted Extensions, including with the use of non-global zones. The interaction between Sun Cluster and Solaris Trusted Extensions when using non-global zones is not yet tested and is not supported.

[Top|#top]

h2. {anchor:GEEER}Solaris Volume Manager GUI

The Enhanced Storage module of Solaris™ Management Console (Solaris Volume Manager) is not compatible with Sun Cluster software. Use the command-line interface or Sun Cluster utilities to configure Solaris Volume Manager software.

[Top|#top]

h2. {anchor:zfsrootdg}VxVM and ZFS Root Disk

h1. {anchor:FNCMB} Commands Modified in This Release

This section describes changes to the Sun Cluster command interfaces that might cause user scripts to fail.

h2. clzonecluster Utility {anchor:clzc}

A new {{clzonecluster}} utility is added to the Solaris 10 version of the Sun Cluster 3.2 1/09 software. This command is used to create and administer a zone cluster. This utility is similar to the {{zonecfg}} utility and accepts resources that are used by the {{zonecfg}} and {{sysidcfg}} utilities. See the {{clzonecluster}}(1M) man page for usage details.

[Top|#top]

h2. {anchor:num_zoneclusters} New {{num_zoneclusters}} Network Property for the {{cluster}} Command

A new network property, {{num_zoneclusters}}, is introduced for use with the {{cluster set-netprops}} command. This property specifies the number of zone clusters that you expect to include in the global cluster. The cluster infrastructure uses this value to modify the private-network IP address range, to support the additional number of addresses that the specified number of zone clusters would require. Unlike the other network properties, you can set this property while the global cluster is in cluster mode as well as in noncluster mode. This property is valid only on the Solaris 10 OS.

[Top|#top]


h2. New {{check}} and {{list-checks}} Subcommands for the {{cluster}} Command

The new {{cluster check}} subcommand replaces the {{sccheck}} command and performs the same role as {{sccheck}}. For any procedures that use {{sccheck}}, run {{cluster check}} instead, except continue to use the sccheck command to verify the existence of mount points when you configure a cluster file system. For details about the {{check}} subcommand, see the [{{cluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cluster-1cl] man page.

The new {{list-checks}} subcommand is also added. Use {{cluster list-checks}} to display a list of all available cluster configuration checks. For details about the {{list-checks}} subcommand, see the [{{cluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cluster-1cl] man page.

[Top|#top]

h2. {{pnmd}} Daemon

The {{pnmd}} daemon is replaced by the {{cl_pnmd}} daemon, and the {{pnmd}}(1M) man page is replaced by the [{{cl_pnmd}}(1M)|http://docs.sun.com/app/docs/doc/820-4685/cl_pnmd-1m] man page. This change has little to no user impact, as this daemon is used only by the system.

[Top|#top]

h1. {anchor:ProductNameChanges} Product Name Changes

This section provides information about product name changes for applications that Sun Cluster software supports. Depending on the Sun Cluster software release that you are running, your Sun Cluster documentation might not reflect the following product name changes.
{info:title=Note}Sun Cluster 3.2 1/09 software is distributed under Solaris Cluster 3.2 1/09 and Sun Java Availability Suite.
{info}

|| Current Product Name || Former Product Name ||
| Sun Cluster HA for MaxDB | Sun Cluster HA for SAP DB |

[Top|#top]

h1. {anchor:RELNOTES-6-PRODUCTS} Supported Products

This section describes the supported software and memory requirements for Sun Cluster 3.2 1/09 software.
* [Common Agent Container|#cacao]
* [Data Services|#ds]
* [File Systems|#fs]
* [Memory Requirements|#memory]
* [Solaris Operating System (OS)|#os]
* [Sun Management Center |#sunmc]
* [Sun StorageTek Availability Suite |#sstavs]
* [Sun StorEdge Availability Suite |#sseavs]
* [Volume Managers |#vm]

h2. {anchor:cacao} Common Agent Container

This Sun Cluster release supports the common agent container version 2.1.

[Top|#top]

h2. {anchor:ds} Data Services

Contact your Sun sales representative for the complete list of supported data services (agents) and application versions.
{info:title=Note}Data service documentation, including man pages and wizard online help, is no longer translated from English to other languages.
{info}

* [HA-Containers Brand Support|#hazones]
* [Non-Global Zones Support|#zonessupport]
* [Zone Cluster Support|#zcsupport]
* [Resource Type Names|#rtnames]

h3. {anchor:hazones}HA-Containers Brand Support

The Sun Cluster Data Service for Solaris Containers supports non-global zones of the following brands:
* {{lx}}
* {{native}}
* {{solaris8}}
* {{solaris9}}

h3. {anchor:zonessupport}Non-Global Zones Support

The following Sun Cluster data services are supported to run in non-global zones that are not part of a zone cluster.
{info:title=Note}This support is available only for {{native}} brand non-global zones.
{info}

* Sun Cluster Data Service for Apache
* Sun Cluster Data Service for Apache Tomcat
* Sun Cluster Data Service for DHCP
* Sun Cluster Data Service for Domain Name Service (DNS)
* Sun Cluster Data Service for Kerberos
* Sun Cluster Data Service for MaxDB
* Sun Cluster Data Service for mySQL
* Sun Cluster Data Service for N1 Grid Service Provisioning Server
* Sun Cluster Data Service for Oracle
* Sun Cluster Data Service for Oracle Application Server
* Sun Cluster Data Service for PostgreSQL
* Sun Cluster Data Service for Samba
* Sun Cluster Data Service for SAP
* Sun Cluster Data Service for SAP liveCache
* Sun Cluster Data Service for SAP Web Application Server
* Sun Cluster Data Service for Sun Java System Application Server
* Sun Cluster Data Service for Sun Java System Message Queue Server
* Sun Cluster Data Service for Sun Java System Web Server
* Sun Cluster Data Service for SWIFTAlliance Access
* Sun Cluster Data Service for SWIFTAlliance Gateway
* Sun Cluster Data Service for Sybase ASE

The {{SUNW.gds}} resource type is supported in a {{native}} brand non-global zone.

{info:title=Note}Procedures for the version of Sun Cluster HA for Sun Java™ System Directory Server that uses Sun Java System Directory Server 5.0 and 5.1 are located in [_Sun Cluster 3.1 Data Service for Sun ONE Directory Server_|http://docs.sun.com/app/docs/doc/817-1529].
Beginning with Version 5.2 of Sun ONE Directory Server, see the Sun ONE Directory Server or Sun Java System Directory Server installation documentation.
{info}
{info:title=Note}The Sun Cluster Data Service for Agfa IMPAX 6.3 is supported only on the Solaris 10 OS in this Sun Cluster release. This data service is not supported on the Solaris 9 OS.
{info}

[Top|#top]

h3. {anchor:zcsupport}Zone Cluster Support

The following Sun Cluster data services are supported in a zone cluster:

* Sun Cluster Data Service for Apache (failover and scalable)
* Sun Cluster Data Service for MySQL - requires the following minimum patch version to run in a zone cluster:
** SPARC: 126032-06
** x86: 126033-07
* Sun Cluster Support for Oracle RAC

The {{SUNW.gds}} resource type is supported in a zone cluster.

[Top|#top]

h3. {anchor:rtnames}Resource-Type Names

The following is a list of Sun Cluster data services and their resource types.
|| Data Service || Sun Cluster Resource Type ||
| Sun Cluster HA for Agfa IMPAX | {{SUNW.gds}} |
| Sun Cluster HA for Apache | {{SUNW.apache}} |
| Sun Cluster HA for Apache Tomcat | {{SUNW.gds}} |
| Sun Cluster HA for DHCP | {{SUNW.gds}} |
| Sun Cluster HA for DNS | {{SUNW.dns}} |
| Sun Cluster HA for Informix | {{SUNW.gds}}\] |
| Sun Cluster HA for Kerberos | {{SUNW.krb5}}\] |
| Sun Cluster HA for MaxDB | {{SUNW.sapdb}}, {{SUNW.sap_xserver}} |
| Sun Cluster HA for MySQL | {{SUNW.gds}} |
| Sun Cluster HA for N1 Grid Service Provisioning System | {{SUNW.gds}} |
| Sun Cluster HA for NFS | {{SUNW.nfs}} |
| Sun Cluster HA for Oracle | {{SUNW.oracle_server}}, {{SUNW.oracle_listener}} |
| Sun Cluster HA for Oracle Application Server | {{SUNW.gds}} |
| Sun Cluster HA for Oracle E-Business Suite | {{SUNW.gds}} |
| Sun Cluster Support for Oracle Real Application Clusters | {{SUNW.rac_framework}}, {{SUNW.rac_udlm}},{{SUNW.rac_svm}}, {{SUNW.rac_cvm}}, {{SUNW.oracle_rac_server}}, {{SUNW.oracle_listener}}, {{SUNW.scaldevicegroup}}, {{SUNW.scalmountpoint}}, {{SUNW.crs_framework}}, {{SUNW.scalable_rac_server_proxy}} |
| Sun Cluster HA for PostgreSQL | {{SUNW.gds}} |
| Sun Cluster HA for Samba | {{SUNW.gds}} |
| Sun Cluster HA for SAP | {{SUNW.sap_ci}}, {{SUNW.sap_ci_v2}}, {{SUNW.sap_as}}, {{SUNW.sap_as_v2}} |
| Sun Cluster HA for SAP liveCache | {{SUNW.sap_livecache}}, {{SUNW.sap_xserver}} |
| Sun Cluster HA for SAP Web Application Server | {{SUNW.sapenq}}, {{SUNW.saprepl}}, {{SUNW.sapscs}}, {{SUNW.sapwebas}} |
| Sun Cluster HA for Siebel | {{SUNW.sblgtwy}}, {{SUNW.sblsrvr}} |
| Sun Cluster HA for Solaris Containers | {{SUNW.gds}} |
| Sun Cluster HA for Sun Grid Engine | {{SUNW.gds}} |
| Sun Cluster HA for Sun Java System Application Server supported versions before 8.1 | {{SUNW.s1as}} |
| Sun Cluster HA for Sun Java System Application Server supported versions as of 8.1 | {{SUNW.jsas}}, {{SUNW.jsas-na}} |
| Sun Cluster HA for Sun Java System Application Server EE (supporting HADB versions before 4.4) | {{SUNW.hadb}} |
| Sun Cluster HA for Sun Java System Application Server EE (supporting HADB versions as of 4.4) | {{SUNW.hadb_ma}} |
| Sun Cluster HA for Sun Java System Message Queue | {{SUNW.s1mq}} |
| Sun Cluster HA for Sun Java System Web Server | {{SUNW.iws}} |
| Sun Cluster HA for SWIFTAlliance Access | {{SUNW.gds}} |
| Sun Cluster HA for SWIFTAlliance Gateway | {{SUNW.gds}} |
| Sun Cluster HA for Sybase ASE | {{SUNW.sybase}} |
| Sun Cluster HA for WebLogic Server | {{SUNW.wls}} |
| Sun Cluster HA for WebSphere Message Broker | {{SUNW.gds}} |
| Sun Cluster HA for WebSphere MQ | {{SUNW.gds}} |

[Top|#top]

h2. {anchor:fs} File Systems


h3. Solaris 10 SPARC

|| File System || Additional Information ||
| Solaris UFS | |

h3. Solaris 10 x86

|| File System || Additional Information ||
| Solaris UFS | |

h3. Solaris 9 SPARC

|| File System || Additional Information ||

h2. {anchor:memory} Memory Requirements

Sun Cluster 3.2 1/09 software requires the following memory requirements for every cluster node:
* Minimum of 1 Gbytes of physical RAM (2 Gbytes typical)
* Minimum of 6 Gbytes of available hard drive space

Actual physical memory and hard drive requirements are determined by the applications that are installed. Consult the application's documentation or contact the application vendor to calculate additional memory and hard drive requirements.

[Top|#top]

h2. {anchor:os} Solaris Operating System (OS)

[Top|#top]

h2. {anchor:sunmc}Sun Management Center

This Sun Cluster release supports Sun Management Center software versions 3.6.1 and 4.0.

[Top|#top]

h2. {anchor:sstavs}Sun StorageTek™ Availability Suite

This Sun Cluster release supports Sun StorageTek Availability Suite 4.0 software on the Solaris 10 OS only.

[Top|#top]

h2. {anchor:sseavs}Sun StorEdge™ Availability Suite

This Sun Cluster release supports Sun StorEdge Availability Suite 3.2.1 software on the Solaris 9 OS only.

[Top|#top]

h2. {anchor:vm}Volume Managers

This Sun Cluster release supports the following volume managers.

h3. Solaris 10 SPARC

|| Volume Manager || Cluster Feature ||
| Solaris Volume Manager | Solaris Volume Manager for Sun Cluster |
| Veritas Volume Manager components that are delivered as part of Veritas Storage Foundation 5.0. This support requires VxVM 5.0 MP3 RP1. | Veritas Volume Manager 5.0 cluster feature (with RAC only) |

h3. Solaris 10 x86

|| Volume Manager || Cluster Feature ||
| Solaris Volume Manager | Solaris Volume Manager for Sun Cluster |
| Veritas Volume Manager components that are delivered as part of Veritas Storage Foundation 5.0.  This support requires VxVM 5.0 MP3 RP1. | Not applicable - Sun Cluster 3.2 1/09 software does not support the VxVM cluster feature on the x86 platform. |

h3. Solaris 9 SPARC

|| Volume Manager || Cluster Feature ||
| Solaris Volume Manager | Solaris Volume Manager for Sun Cluster |
| Veritas Volume Manager components that are delivered as part of Veritas Storage Foundation 5.0. This support requires VxVM 5.0 MP3 RP1. | Veritas Volume Manager 5.0 cluster feature (with RAC only) |
[Top|#top]

h2. {anchor:CJAEBGFD} Sun Cluster Security Hardening

Sun Cluster Security Hardening uses the Solaris Operating System hardening techniques recommended by the Sun BluePrints™ program to achieve basic security hardening for clusters. The Solaris Security Toolkit automates the implementation of Sun Cluster Security Hardening.

The Sun Cluster Security Hardening documentation is available at [http://www.sun.com/blueprints/0203/817-1079.pdf|http://www.sun.com/blueprints/0203/817-1079.pdf]. You can also access the article from [http://www.sun.com/software/security/blueprints|http://www.sun.com/software/security/blueprints]. From this URL, scroll down to the Architecture heading to locate the article "Securing the Sun Cluster 3.x Software." The documentation describes how to secure Sun Cluster 3.x deployments in a Solaris environment. The description includes the use of the Solaris Security Toolkit and other best-practice security techniques recommended by Sun security experts. The following data services are supported by Sun Cluster Security Hardening:
* Sun Cluster HA for Apache
* Sun Cluster HA for Apache Tomcat
* Sun Cluster HA for DHCP
* Sun Cluster HA for DNS
* Sun Cluster HA for MySQL
* Sun Cluster HA for N1 Grid Engine
* Sun Cluster HA for NFS
* Sun Cluster HA for Oracle
* Sun Cluster HA for Oracle E-Business Suite
* Sun Cluster Support for Oracle Real Application Clusters
* Sun Cluster HA for PostgreSQL
* Sun Cluster HA for Samba
* Sun Cluster HA for Siebel
* Sun Cluster HA for Solaris Containers
* Sun Cluster HA for SWIFTAlliance Access
* Sun Cluster HA for SWIFTAlliance Gateway
* Sun Cluster HA for Sun Java System Directory Server
* Sun Cluster HA for Sun Java System Message Queue
* Sun Cluster HA for Sun Java System Messaging Server
* Sun Cluster HA for Sun Java System Web Server
* Sun Cluster HA for Sybase ASE
* Sun Cluster HA for WebLogic Server
* Sun Cluster HA for WebSphere MQ
* Sun Cluster HA for WebSphere MQ Integrator

[Top|#top]

h1. {anchor:CHDGGECB} Known Issues and Bugs

The following known issues and bugs affect the operation of the Sun Cluster 3.2 1/09 release. Bugs and issues are grouped into the following categories:
* [Administration|#GEBBO]
* [Data Services|#GEAYZ]
* [GUI|#GGCGJ]

[Top|#top]

h2. {anchor:GEBBO} Administration

*Problem Summary*: The creation of a logical-hostname or shared-address resource in a zone cluster fails if any public adapter in the cluster is not part of an IPMP group. The action fails with the following message:
{panel}
Failed to retrieve the ipmp group name for adapter ...
{panel}{*}Workaround*: Configure in IPMP groups all public adapters that are available on the cluster nodes, including those that are not currently used by Sun Cluster software.
[Top|#top]

h3. An Update to HAStoragePlus Resources Fails in Sun Cluster 3.2 1/09 on Solaris 9 (6787430)

*Problem Summary*: On the Solaris 9 OS, an update to HAStoragePlus resources fails with the {{hastorageplus_validate}} method being killed with the {{SIGSEGV}} signal.

*Workaround*: Delete the failing resource and recreate the HAStoragePlus resource with the latest required property values.

[Top|#top]

h3. Validate Method Core Dumps While Creating Logical-Hostname/Shared-Address Resource in Zone Cluster (6784809)

*Problem Summary*: The creation of a logical-hostname resource or a shared-address resource in a zone cluster fails when there are no other resource groups configured in the cluster. The validate method dumps core and the resource is not created. This problem is not seen if any resource groups already exist in the cluster, either in the global zone or in {{native}} brand non-global zones.

*Workaround*: Before you create a logical-hostname resource or a shared-address resource in a zone cluster, if no resource group already exists in the cluster, create an empty resource group in the global zone by using the {{clesourcegroup}} command.

[Top|#top]

h3. Removal of Last Quorum Device From Two-Host Cluster Does Not Work for a Quorum Server or NAS Device (6775391)

*Problem Summary*: On a two-node cluster with installmode disabled, the last quorum device cannot be removed by using {{clquorum remove _quorum_device_name{_}}}, which is the usual procedure to remove a quorum device. It is necessary to use the {{force}} option, {{\-F}}, to remove the last quorum device on a two-node cluster with installmode disabled. The usage is {{clquorum remove \-F _quorum_device_name{_}}}. However, this {{force}} option works only for {{scsi2}}, {{scsi3}}, and {{software_quorum}} types of quorum devices.

If the last quorum device configured on a two-node cluster with installmode disabled is a quorum server or a NAS quorum device, it cannot be removed by using {{clquorum remove _quorum_device_name{_}}} or {{clquorum remove \-F _quorum_device_name{_}}}. If the user attempts this action, error messages similar to the following would be shown (in these examples, the last quorum device is a quorum server named {{qs1}}, and {{clq}} is the short form equivalent of {{clquorum}}):
* For {{clquorum remove qs1}}:
{panel}
{{clq:  (C115344) Cluster quorum could be compromised if you remove "qs1".}}
{panel}
* For {{clquorum remove \-F qs1}}:
{panel}
{{Warning: Force option used.}}{{{}This cluster is at risk of experiencing a serious outage.}}{{{}Configure a new quorum device to prevent loss of cluster quorum and outages.}}{{{}clq:  (C115344) Cluster quorum could be compromised if you remove "qs1".}}
{panel}

*Workaround*: If the last quorum device configured on a two-node cluster, with installmode disabled, is a quorum server or a NAS quorum device, do the following to remove this last quorum device:
# *Become superuser on a node running in cluster mode.*
# *Enable installmode.*
{panel}
{{\# *cluster set \-p installmode=enabled{*}}}
{panel}
# *Remove the last quorum device.*
{panel}
{{\# *clquorum remove* *{_}quorum_device_name{_}{*}}}
{panel}

[Top|#top]

h3. Scalable Services Fail to Fail Over When There Is a Network Outage (6774504)

*Problem Summary*: The failover of scalable resources does not happen if there is a network outage on the nodes where the resources are currently online. Due to this issue, the resources do not fail over to a healthy node and the resource's status still shows as online on the failed node.

*Workaround*: There is no workaround for this issue. Contact your Sun service representative to determine whether a patch is available.

[Top|#top]

h3. clresourcegroup create and add-node Subcommands Cannot Prevent Mixing Global-Cluster Nodes With Zone-Cluster Nodes (6762845)

*Problem Summary*: When zone clusters are configured, the {{clresourcegroup create}} and {{clresourcegroup add-node}} subcommands do not prevent the node list from containing both the global-cluster nodes and the zone-cluster nodes. You will see the following error message when you try to bring a resource group with mixed nodes online:
{panel}
{{\# *clresourcegroup online rg1{*}{}}}{{{}clrg:  (C135343) No primary node could be found for resource group rg1; it remains offline}}
{panel}{*}Workaround*: If a resource group's node list contains both global-cluster nodes and zone-cluster nodes, change the node list so that the list contains only global-cluster nodes or only zone-cluster nodes. Use the {{clresroucegroup add-node}} or {{clresourcegroup remove-node}} commands to add or remove nodes from the node list.
[Top|#top]

h3. Resource Groups Might Come Online on Less-Preferred Nodes When a Zone Cluster is Rebooted. (6761158)

*Problem Summary*: When an entire zone cluster is rebooted at once, for example, by executing the {{clzonecluster reboot}} command, resource groups might fail to come online on their most-preferred nodes. For example, you might find that all resource groups come online on the same node, even though their node lists indicate a preference for different nodes.

*Workaround*: There are two simple workarounds. However, neither of them exactly matches the behavior that should occur when this bug is fixed:
* Manually execute the {{clresourcegroup remaster}} command on all resource groups, after the zone cluster has booted up:
{panel}
{{\# *clresourcegroup remaster \-Z* *{_}myzonecluster{_}* *+*}}
{panel}This will cause all resource groups in the zone cluster to switch onto their most-preferred master, if they are not already mastered by that node. This command should be executed just once after a zone cluster reboot, when all of the zone-cluster nodes are up and running. However, on an unattended cluster, this workaround will not automatically take effect, for example, after a power outage when power is restored, since the {{clresourcegroup remaster}} command must be executed manually.

* Set the {{Failback}} property to {{TRUE}} on all resource groups in the zone cluster:
{panel}
{{\# *clresourcegroup set \-Z* *{_}myzonecluster{_}* *\-p Failback=TRUE +*}}
{panel}With this setting, a resource group might initially come online on a less-preferred node, but will automatically switch over to a more-preferred node that joins the cluster membership. However, the automatic switchover will be performed any time a more-preferred node joins the zone-cluster membership, not only when the zone cluster is initially booted.

[Top|#top]

h3. rpcbind Authentication Errors When JASS is Deployed with Sun Cluster 3.2 1/09 (6727594)

*Problem Summary*: When JASS is installed and enabled on a cluster node, the Sun Cluster commands to retrieve IPMP group status, {{scstat \-i}} or {{clnode status \-m}}, might fail with the following message:
{panel}
{{scrconf: RPC: Rpcbind failure - RPC: Authentication error}}
{panel}{*}Workaround*: Add IP addresses that correspond to all cluster nodes' private hostnames to the rpcbind line in the {{/etc/hosts.allow}} file. By default, the cluster nodes' private hostnames are of the form {{clusternode{_}N_\-priv}}. Their corresponding IP addresses can be determined by using the following command:
{panel}
{{\# *getent hosts clusternode{*}{*}{_}N{_}{*}*\-priv{*}}}
{panel}For instance, on a four-node cluster, you might update the {{rpcbind}} line in {{/etc/hosts.allow}} to be:
{panel}
{{rpcbind:        172.16.4.1 172.16.4.2 172.16.4.3 172.16.4.4}}
{panel}[Top|#top]

h3. Whole-Root Zones of ip-type=exclusive Do Not Have Access to SUNW.LogicalHostname Resource Methods (6711918)

*Problem Summary*: Attempts to create {{SUNW.LogicalHostname}} resources for whole-root zones with {{ip-type=exclusive}} fail. Error messages similar to the following can be found in the syslog:
{panel}
Jun  6 23:01:24 lzkuda-4a Cluster.RGM.fed: \[ID 838032 daemon.error\] lzkuda-4a.test-rg.kuda-3.2: Couldn't run method tag. Error in execve: No such file or directory.
{panel}{*}Workaround*: For each whole-root zone with {{ip-type=exclusive}} that might host a {{SUNW.LogicalHostname}} resource, configure a file-system resource that mounts the method directory from the global zone.
{panel}
\# *zonecfg \-z myzone*
zonecfg:myzone> *add fs*
zonecfg:myzone:fs> *set dir=/usr/cluster/lib/rgm*
zonecfg:myzone:fs> *set special=/usr/cluster/lib/rgm*
zonecfg:myzone:fs> *set type=lofs*
zonecfg:myzone:fs> *end*
{panel}[Top|#top]

h2. {anchor:GEAYZ} Data Services


h3. The START_TIMEOUT for WebAS Instance Needs to be Changed to 600 (6808410)

*Problem Summary*: The default START_TIMEOUT value for the SAP WebAS resource is 300 seconds. The Sun Cluster agent for  SAP WebAS starts the instance and then waits for the server to be completely up (by probing for the server) before successfully returning from the start method. Depending on your system resources and the load on your server, the startup of the SAP WebAS instance might take longer than 300 seconds.

*Workaround*: If the WebAS instance needs more than 300 seconds to start up on the cluster nodes, create the SAP WebAS resource with a higher value for the START_TIMEOUT property, for example, 600, 

[Top|#top]

h3. Scalable WebAS Resource Fails to Come Online if Wrapper Script Is Not Used in Webas_start_up_script (6808403)

*Problem Summary*: For the SAP Web Application Server (WebAS) scalable data service, as of the SAP 6.4 release it should no longer be necessary to create wrapper scripts when you create the WebAS instances. But even in SAP 64 and later versions the WebAS resource does not come online if no wrapper scripts are created.

*Workaround*: To make the SAP Web Application Server (WebAS) instances highly available as a scalable service, create wrapper scripts as described in Step 7 of  ["How to Install and Configure the SAP Web Application Server and the SAP J2EE Engine"|http://docs.sun.com/app/docs/doc/820-2568/installconfig-52?a=view] from the _Sun Cluster HA for SAP Web Application Server Guide_. You must use these wrapper scripts as the startup\- and shutdown-script extension properties when you create the WebAS instances, regardless of which version of SAP software you run.

[Top|#top]

h3. BEA WLS Managed Server Went to Admin State After Fault Injection, Client Access Failed (6626817)

*Problem Summary*: When a non-global zone that runs BEA WebLogic Server managed servers panics and goes down, the data service for WebLogic Server fails over and starts all its resources in another available non-global zone in the cluster. In some situations, after the failover the WebLogic Managed Servers might go into in the Admin state instead of the Running state and require operator assistance.

*Workaround*: Use the WebLogic Server administration interface to manually change the state to the Running state.

[Top|#top]


h2. {anchor:GGCGJ} GUI

h3. RAC Wizard Under Some Scenarios Tries to Create Configuration in a Zone Cluster Even When Global Cluster Is Selected (6801490)

*Problem Summary*: The RAC wizard sometimes attempts to create the configuration for a zone cluster even when the user selects global cluster.

*Workaround*: Perform the following steps:

# Remove the state file {{/opt/cluster/lib/ds/history/RacStateFile}}, if present.
# Restart the common agent container.
{panel}
\# *cacaoadm restart*
{panel}

[Top|#top]


h3. The RAC GUI Storage Wizard Does Not Create the Resources in a Zone Cluster when Solaris Volume Manager Is Selected (6799694)

*Problem Summary*: The web-based RAC storage wizard attempts to create the scalable device group resources and resource groups for the Solaris Volume Manager for Sun Cluster disk groups in the global cluster, when the user selects Solaris Volume Manager from the storage-scheme selection panel.

*Workaround*: Use the text-based wizard. The problem exists only in the web-based wizard.


[Top|#top]


h3. clsetup Does Not Display Existing VxVM Device Groups in the Global Zone (6798909)

*Problem Summary*: The wizards do not list the existing VxVM device groups in the global zone.

*Workaround*: Use the command-line interface for RAC configuration on VxVM storage.

[Top|#top]


h3. Configuration of RAC Framework Fails in a Zone Cluster with a {{Resource type not found}} Error (6768473)

*Problem Summary*: The Oracle RAC wizard fails to create the configuration for a zone cluster with a {{Resource type not found}} error message.

*Workaround*: Copy the RTR files that are used by the RAC configuration, which are present in the directories {{/usr/cluster/lib/rgm/rtreg}} and {{/opt/cluster/lib/rgm/rtreg}}, from the global cluster to the {{{_}zoneclusterpath_/root/usr/cluster/lib/rgm/rtreg}} and {{{_}zoneclusterpath_/root/opt/cluster/lib/rgm/rgtreg}} directories, respectively. Namely, the following RTR files need to be copied:

From {{/usr/cluster/lib/rgm/rtreg}} in the global zone:
{panel}
SUNW.ScalMountPoint
SUNW.ScalDeviceGroup
SUNW.crs_framework
SUNW.rac_framework
SUNW.rac_udlm
SUNW.LogicalHostname
{panel}From {{/opt/cluster/lib/rgm/rtreg}} in the global zone:
{panel}
SUNW.scalable_rac_server
SUNW.scalable_rac_server_proxy
SUNW.scalable_rac_listener
{panel}[Top|#top]

h2. {anchor:GEAZH} Installation

h3. Auto Discovery During Installation for Sun Cluster/Transport Does Not Work for igb Interfaces on Solaris OS x64 Platforms (6821699)

*Problem Summary:* During a Sun Cluster installation, auto discovery for Sun Cluster/transport does not work for igb interfaces on Solaris OS x64 platforms.

*Workaround:* When you run scinstall and you are prompted for the interconnect adapters, select *Other* and type each igb interface name.

[Top|#top]


h3. {{sczonecfg}} Should Set {{name_service}} to {{NONE}} if Global Zone Does Not Use Name Service (6798938)

*Problem Summary*: When you create a new zone cluster, the only common system identification parameter that the user is required to specify is the root password. The zone cluster software obtains the values for any other {{sysid}} parameters, such as {{name_service}} and {{timezone}}, from the global zone's {{/etc/sysidcfg}} file.

If the {{/etc/sysidcfg}} file does not exist on the system or the zone-cluster software cannot open the file to obtain the parameter values, the {{name_service}} parameter is left unspecified. Because a value of {{name_service=}} is invalid, system initialization of the new zone cluster fails and the boot process does not complete. The user is prompted to supply the missing parameter value.

*Workaround*: When you create a new zone cluster, manually specify a value for the {{name_service}} parameter. Specify either the name service to use or {{NONE}} if no name service is used.


[Top|#top]

h3. Common Agent Container Dependency on RGM Service Was Removed in rgm_starter Service (6779277)

*Problem Summary*: When you install Sun Cluster 3.2 1/09 software and establish the cluster, the service {{svc:/application/management/common-agent-container-1:default}} might be in the maintenance state. If so, Sun Cluster Manager and some of the command-line interfaces will not work.

*Workaround*: Add the cluster Resource Group Manager (RGM) service {{rgm-starter}} as a dependency of the cluster-management service on all cluster nodes right after Sun Cluster 3.2 1/09 software is installed and configured. Perform the following steps on each node of the cluster:
# Become superuser on a node of the cluster.
# Add a property group of dependents to the {{rgm-starter}} SMF service.
{panel}
\# *svccfg \-s rgm-starter:default addpg dependents framework*
{panel}
# Add the value for the dependents property group for the {{rgm-starter}} SMF service.
{panel}
\# *svccfg \-s rgm-starter:default addpropvalue dependents/rgm_cacao fmri: svc:/application/management/common-agent-container-1:default*
{panel}
# Verify that the value is correctly set for the dependent property group for the {{rgm-starter}} SMF service.
{panel}
\# *svccfg \-s rgm-starter:default listprop \| grep dependents*
{panel}
# If the service {{svc:/application/management/common-agent-container-1:default}} is in the maintenance state, clear the {{common-agent-container}} SMF service from the maintenance state and enable the SMF service.
{panel}
\# *svcadm clear svc:/application/management/common-agent-container-1:default*
\# *svcadm enable svc:/application/management/common-agent-container-1:default*
{panel}
# Verify that Sun Cluster Manager now works properly by using a web browser to connect to the URL {{[https://_nodename_:6789]}}.

[Top|#top]

h2. {anchor:l10n}Localization


h3. \[zh_CN\]:Result of System Requirements Checking Is Wrong (6495984)

*Problem Summary*: When you use the {{installer}} utility to install Sun Cluster software, the software that checks the system requirements incorrectly reports that the swap space is 0 Mbytes in the Simplified Chinese and Traditional Chinese locales.

*Workaround*: Ignore this reported information. In these locales, you can run the following command to determine the correct swap space:
{panel}
\# *df \-h \| grep swap*
{panel}

[Top|#top]

h3. Rebooting Multiple Upgraded Nodes Into the Cluster During Rolling Upgrade Panics Nodes on Old Software (6788866)

*Problem Summary*: In a rolling upgrade, old software nodes are taken out of cluster mode and upgraded to the new software, and then booted back into cluster mode. Depending on the quorum configuration and availability of operational quorum on the running cluster, the user could take one or more than one nodes out of the cluster at a time for upgrades, and then boot them back into cluster after upgrade.

While performing rolling upgrade of a cluster to Sun Cluster 3.2 1/09 software, if more than one upgraded node is booted back into the cluster at the same time, then one or more of the nodes running the older software version in the cluster might panic.

*Workaround*: After nodes are upgraded to run Sun Cluster 3.2 1/09, boot only one node at a time into cluster mode to join the running cluster.

[Top|#top]

h3. Common Agent Container Dependency on RGM Service Was Removed in rgm_starter Service (6779277)

*Problem Summary*: When you upgrade to Sun Cluster 3.2 1/09 software by using the live upgrade method, the service {{svc:/application/management/common-agent-container-1:default}} might be in the maintenance state. If so, Sun Cluster Manager and some of the command-line interfaces will not work.

*Workaround*: Add the cluster Resource Group Manager (RGM) service {{rgm-starter}} as a dependency of the cluster-management service on all cluster nodes right after Sun Cluster 3.2 1/09 software is upgraded. Perform the following steps on each node of the cluster:
# Become superuser on a node of the cluster.
# Add a property group of dependents to the {{rgm-starter}} SMF service.
{panel}
\# *svccfg \-s rgm-starter:default addpg dependents framework*
{panel}
# Add the value for the dependents property group for the {{rgm-starter}} SMF service.
{panel}
\# *svccfg \-s rgm-starter:default addpropvalue dependents/rgm_cacao fmri: svc:/application/management/common-agent-container-1:default*
{panel}
# Verify that the value is correctly set for the dependent property group for the {{rgm-starter}} SMF service.
{panel}
\# *svccfg \-s rgm-starter:default listprop \| grep dependents*
{panel}
# If the service {{svc:/application/management/common-agent-container-1:default}} is in the maintenance state, clear the {{common-agent-container}} SMF service from the maintenance state and enable the SMF service.
{panel}
\# *svcadm clear svc:/application/management/common-agent-container-1:default*
\# *svcadm enable svc:/application/management/common-agent-container-1:default*
{panel}
# Verify that Sun Cluster Manager now works properly by using a web browser to connect to the URL {{[https://_nodename_:6789]}}.

[Top|#top]

h3. Sun Cluster Manager Does Not Work After Upgrading From Pre-3.2 2/08 Release to 3.2 1/09 Release (6768115)

*Problem Summary*: After performing a live upgrade from the Sun Cluster 3.2 release or earlier to Sun Cluster 3.2 1/09 software, activating the new BE, and booting the nodes, the service {{svc:/system/cluster/rgm:default}} is in maintenance state and the service {{svc:/application/management/common-agent-container-1:default}} is offline. Due to these states, Sun Cluster Manager cannot display the cluster configuration data.

*Workaround*: Become superuser and issue the following commands on all nodes:
{panel}
\# *svccfg delete \-f svc:/system/cluster/rgm:default*
\# *svcadm enable svc:/application/management/common-agent-container-1:default*
{panel}You can then verify that Sun Cluster Manager works properly by connecting to the URL {{[https://_nodename_:6789]}}.
[Top|#top]

h3. Upgrade From 3.2 Plus Patch 126107-15 Failed; pkgrm of SUNWscr Fails (6747530)

*Problem Summary*: On the Solaris 10 OS, upgrading Sun Cluster software from the 3.2 2/08 release to the 3.2 1/09 release fails when removing the package {{SUNWscr}}.
{panel}
\# *scinstall \-u update*

Starting upgrade of Sun Cluster framework software
Saving current Sun Cluster configuration
Do not boot this node into cluster mode until upgrade is complete.

Renamed "/etc/cluster/ccr" to "/etc/cluster/ccr.upgrade".

\*\* Removing Sun Cluster framework packages \*\*
        Removing SUNWsctelemetry..done
        Removing SUNWscderby..done
...
       Removing SUNWscr.....failed
scinstall:  Failed to remove "SUNWscr"
        Removing SUNWscscku..done
        Removing SUNWscsckr..done
        Removing SUNWsczu....done
        Removing SUNWsccomzu..done
        Removing SUNWsczr....done
        Removing SUNWsccomu..done
        Removing SUNWscu.....done

scinstall:  scinstall did NOT complete successfully\!
{panel}{*}Workaround*: Before starting the upgrade, install one of the following pairs of patches as appropriate, which provide a new {{pkg_preremove}} script that resolves this problem. The patch version numbers shown are the minimum required:
140017-01 and 126538-02 (S10 Sparc)
140018-01 and 126539-02 (S10 X86)
If you have already started the upgrade and it fails with the above error, you can install the appropriate patches, then restart the upgrade by running {{scinstall \-u update}}.
[Top|#top]

h3. Zones With ip-type=exclusive Cannot Host SUNW.LogicalHostname Resources After Upgrade (6702621)

*Problem Summary*: Resource type {{SUNW.LogicalHostname}} is registered at version 2 (use the {{clresourcetype list}} command to display the version). After upgrade, logical-hostname resources can be created for zones with {{ip-type=exclusive}}, but network access to the logical hostname, for example, telnet or rsh, does not work.

*Workaround*: Perform the following steps:
# Delete all resource groups with a node list that contains a zone with {{ip-type=exclusive}} that hosts logical-hostname resources.
# Upgrade the {{SUNW.LogicalHostname}} resource type to version 3:

{panel}
{{\# *clresourcetype register SUNW.LogicalHostname:3{*}}}
{panel}[Top|#top]

h1. {anchor:CHDHEHGF} Patches and Required Firmware Levels

This section provides information about patches for Sun Cluster configurations, including the following subsections:
* [Applying the Sun Cluster 3.2 1/09 Core Patch|#GEZEZ]
* [Removing the Sun Cluster 3.2 1/09 Core Patch|#GEZDN]
* [Patch Management Tools|#patch]
* [SunSolve Online|#X-1DIMK]
* [Sun Cluster Patch Lists|#patchklatch]

If you are upgrading to Sun Cluster 3.2 1/09 software, see the _Sun Cluster Upgrade Guide for Solaris OS_. Applying a Sun Cluster 3.2 1/09 Core patch does not provide the same result as upgrading the software to the Sun Cluster 3.2 1/09 release.
{info:title=Note}Read the patch {{README}} file before applying or removing any patch.
{info}If you are using the rebooting patch (node) method to install the Sun Cluster core patch 126105 (S9/SPARC), 126106 (S10/SPARC), or 126107 (S19/x64), you must have the 125510-02, 125511-02, or 125512-02 core patch, respectively, installed before you can install the 126105, 126106, or 126107 patch. If you do not have the 125510-02, 125511-02, or 125512-02 patch installed and want to install 126105, 126106, or 126107, you must use the rebooting cluster method.
See the following list for examples of patching scenarios:
* If you have Sun Cluster 3.2 1/09 software using the Solaris 10 Operating System on SPARC _with_ patch 125511-02 installed and want to install 126106, use the rebooting node or rebooting cluster method.

* If you have Sun Cluster 3.2 1/09 software using the Solaris 10 Operating System on SPARC _without_ 125511-02 installed and want to install 126106, choose one of the following methods:
** Use the rebooting cluster method to install 126106.
** Install 125511-02 by using the rebooting node method and then install 126106 by using the rebooting node method.
{info:title=Note}You must be a registered SunSolve™ user to view and download the required patches for the Sun Cluster product. If you do not have a SunSolve account, contact your Sun service representative or sales engineer, or register online at [http://sunsolve.sun.com|http://sunsolve.ebay.sun.com].
{info}[Top|#top]

h2. {anchor:GEZEZ} Applying the Sun Cluster 3.2 1/09 Core Patch

Complete the following procedure to apply the Sun Cluster 3.2 1/09 core patch. Ensure that all nodes of the cluster are maintained at the same patch level.

h3. {anchor:GEZEH} How to Apply the Sun Cluster 3.2 1/09 Core Patch

# Install the patch by using the usual rebooting patch procedure for a core patch.
# Verify that the patch has been installed correctly on all nodes and is functioning properly.
# Register the new version of resource types {{SUNW.HAStoragePlus}}, {{SUNW.ScalDeviceGroup}}, {{and SUNW.ScalMountPoint}} that are being updated in this patch. Perform resource type upgrade on any existing resources of these types to the new versions.

For information about registering a resource type, see "Registering a Resource Type" in the _Sun Cluster Data Services Planning and Administration Guide for Solaris OS_.
{note:title=Caution}If the Sun Cluster 3.2 1/09 core patch is removed, any resources that were upgraded in Step 3 must be downgraded to the earlier resource type versions. The procedure for downgrading requires planned downtime of these services. Therefore, do not perform Step 3 until you are ready to commit the Sun Cluster 3.2 1/09 core patch permanently to your cluster.
{note}[Top|#top]

h2. {anchor:GEZDN} Removing the Sun Cluster 3.2 1/09 Core Patch

Complete the following procedure to remove the Sun Cluster 3.2 1/09 core patch.

h3. {anchor:GEZEC} How to Remove the Sun Cluster 3.2 1/09 Core Patch

[Top|#top]
# List the resource types on the cluster.
{panel}
{{\# *clresourcetype list{*}}}
{panel}
# If the list returns {{SUNW.HAStoragePlus:5}}, {{SUNW.ScalDeviceGroup:2}}, or {{SUNW.ScalMountPoint:2}}, you must remove these resource types. For instructions about removing a resource type, see "How to Remove a Resource Type" in the _Sun Cluster Data Services Planning and Administration Guide for Solaris OS_.
# Reboot all nodes of the cluster into noncluster, single-user mode.
For instructions about rebooting cluster nodes into noncluster, single-user mode, see "How to Boot a Cluster Node in Noncluster Mode" in the _Sun Cluster System Administration Guide for Solaris OS_.
# Remove the Sun Cluster 3.2 1/09 core patch from each node on which you installed the patch.
{panel}
{{\# *patchrm* _patch-id{_}}}
{panel}
# Reboot into cluster mode all of the nodes from which you removed the Sun Cluster 3.2 1/09 core patch.
Rebooting all of the nodes from which you removed the Sun Cluster 3.2 1/09 core patch before rebooting any unaffected nodes ensures that the cluster is formed with the correct configuration information on all nodes. If all nodes on the cluster were patched with the core patch, you can reboot the nodes into cluster mode in any order.
# Reboot any remaining nodes into cluster mode.

For instructions about rebooting nodes into cluster mode, see "How to Reboot a Cluster Node" in the _Sun Cluster System Administration Guide for Solaris OS_.

[Top|#top]

h2. {anchor:patch} Patch Management Tools

Information about patch management options for the Solaris OS is available at the web sites for [Sun xVM Ops Center|http://www.sun.com/software/products/xvmopscenter/] and [Sun Connection Update Manager|http://www.sun.com/download/products.xml?id=4457d96d].

The following tools are part of the Solaris OS. Refer to the version of the manual that is published for the Solaris OS release that is installed on your system:
* Information for using the Solaris patch management utility, {{patchadd}}, is provided in _Solaris Administration Guide: Basic Administration_ at [http://docs.sun.com|http://docs.sun.com/app/docs/prod/solaris].
* Information for using Solaris Live Upgrade to apply patches is provided in the Solaris installation guide for Live Upgrade and upgrade planning at [http://docs.sun.com|http://docs.sun.com/app/docs/prod/solaris].

If some patches must be applied when the node is in noncluster mode, you can apply them in a rolling fashion, one node at a time, unless a patch's instructions require that you shut down the entire cluster. Follow procedures in [How to Apply a Rebooting Patch (Node)|http://docs.sun.com/app/docs/doc/820-4677/6ne5de338?a=view] in Sun Cluster System Administration Guide for Solaris OS to prepare the node and boot it into noncluster mode. For ease of installation, consider applying all patches at once to a node that you place in noncluster mode.

[Top|#top]

h3. {anchor:patch} Patch for Cluster Support for StorageTek 2530 Array

The Sun StorageTek Common Array Manager (CAM) software, Version 6.0.1, provides SCSI3 or PGR support for the Sun StorageTek 2530 array for up to three nodes. The patch is not a required upgrade for the Sun StorEdge 6130, 2540, 6140, and 6540, and StorageTek FLX240, FLX280 and FLX380 platforms. The CAM 6.0.1 patch is available from the Sun Download Center.

[Top|#top]

h2. {anchor:X-1DIMK} SunSolve Online

The SunSolve™ Online Web site provides 24-hour access to the most up-to-date information regarding patches, software, and firmware for Sun products. Access the SunSolve Online site at [http://sunsolve.sun.com|http://sunsolve.ebay.sun.com] for the most current matrixes of supported software, firmware, and patch revisions.

Sun Cluster 3.2 1/09 third-party patch information is provided through a SunSolve Info Doc. This Info Doc page provides any third-party patch information for specific hardware that you intend to use in a Sun Cluster 3.2 1/09 environment. To locate this Info Doc, log on to SunSolve. From the SunSolve home page, type {{{*}Sun Cluster{*}}} {{{*}3.x Third-Party Patches{*}}} in the search criteria box.

Before you install Sun Cluster 3.2 1/09 software and apply patches to a cluster component (Solaris OS, Sun Cluster software, volume manager software, data services software, or disk hardware), review each {{README}} file that accompanies the patches that you retrieved. All cluster nodes must have the same patch level for proper cluster operation.

For specific patch procedures and tips on administering patches, see Chapter 10, ["Patching Sun Cluster Software and Firmware"|http://doc.sun.com/app/docs/doc/820-2558/6ne5de333?a=view] in _Sun Cluster System Administration Guide for Solaris OS_.

[Top|#top]

h2. {anchor:patchklatch}Sun Cluster Patch Lists

The [Sun Cluster Patch Klatch|http://wikis.sun.com/display/SunCluster/The+Patch+Klatch+-+Patches+That+Affect+Sun+Cluster] provides a complete and up-to-date list of patches that you need to apply to the Solaris OS, to Sun Cluster software, and to other software in your cluster configuration, based on the versions of the particular software that you are using.

[Top|#top]

h1. {anchor:CHDGCEDD} Sun Cluster 3.2 1/09 Documentation

The Sun Cluster 3.2 1/09 user documentation set consists of the following collections:
* [Sun Cluster 3.2 1/09 Software Manuals for Solaris OS|#RELNOTES-39S]
* [Sun Cluster 3.2 1/09 Reference Manuals for Solaris OS|#refmans]
* [Sun Cluster 3.2 1/09 Data Service Manuals for Solaris OS (SPARC Platform Edition)|#GEBEX]
* [Sun Cluster 3.2 1/09 Data Service Manuals for Solaris OS (x86 Platform Edition)|#RELNOTES-35]
* [Sun Cluster 3.1-3.2 Hardware Collection for Solaris OS (SPARC Platform Edition)|#RELNOTES-35S]
* [Sun Cluster 3.1-3.2 Hardware Collection for Solaris OS (x86 Platform Edition)|#RELNOTES-35X]
{info:title=Note}Procedures for the version of Sun Cluster HA for Sun Java™ System Directory Server that uses Sun Java System Directory Server 5.0 and 5.1 are located in [_Sun Cluster 3.1 Data Service for Sun ONE Directory Server_|http://docs.sun.com/app/docs/doc/817-1529].
Beginning with Version 5.2 of Sun ONE Directory Server, see the Sun ONE Directory Server or Sun Java System Directory Server installation documentation.
{info}Some manuals were not updated since the previous Sun Cluster 3.2 release. Their content, however, also applies to the Sun Cluster 3.2 1/09 release.

The Sun Cluster 3.2 1/09 user documentation is available in PDF and HTML format at the following web site:

[http://docs.sun.com/app/docs/prod/sun.cluster32|http://docs.sun.com/app/docs/prod/sun.cluster32]
{info:title=Note}Beginning with the Sun Cluster 3.2 release, documentation for individual data services is not translated. Documentation for individual data services is available only in English.
{info}[Top|#top]

h2. {anchor:RELNOTES-39S} Sun Cluster 3.2 1/09 Software Manuals for Solaris OS

|| Part Number || Book Title ||
| 820-4683 | [Sun Cluster 3.2 1/09 Documentation Center |http://docs.sun.com/app/docs/doc/820-4683] |
| 820-4676 | [Sun Cluster Concepts Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4676] |
| 820-4680 | [Sun Cluster Data Services Developer's Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4680] |
| 820-4682 | [Sun Cluster Data Services Planning and Administration Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4682] |
| 820-4681 | [Sun Cluster Error Messages Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4681] |
| 820-4675 | [Sun Cluster Overview for Solaris OS |http://docs.sun.com/app/docs/doc/820-4675] |
| 819-6811 | [Sun Cluster Quick Reference |http://docs.sun.com/app/docs/doc/819-6811] |
| 820-4989 | [Sun Cluster Quick Start Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4989] |
| 820-4677 | [Sun Cluster Software Installation Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4677] |
| 820-4679 | [Sun Cluster System Administration Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4679] |
| 820-4678 | [Sun Cluster Upgrade Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-4678] |
[Top|#top]

h2. {anchor:refmans} Sun Cluster 3.2 1/09 Reference Manuals for Solaris OS

|| Part Number || Book Title ||
| 820-4685 | [Sun Cluster Reference Manual for Solaris OS|http://docs.sun.com/app/docs/doc/820-4685] |
| 820-4684 | [Sun Cluster Data Services Reference Manual for Solaris OS|http://docs.sun.com/app/docs/doc/820-4679] |
| 820-3381 | [Sun Cluster Quorum Server Reference Manual for Solaris OS |http://docs.sun.com/app/docs/doc/820-3381] |
[Top|#top]

h2. {anchor:GEBEX} Sun Cluster 3.2 1/09 Data Service Manuals for Solaris OS (SPARC Platform Edition)

|| Part Number || Book Title ||
| 820-5026 | [Sun Cluster Data Service for Agfa IMPAX Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5026] |
| 820-2092 | [Sun Cluster Data Service for Apache Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2092] |
| 819-3057 | [Sun Cluster Data Service for Apache Tomcat Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3057] |
| 819-3058 | [Sun Cluster Data Service for DHCP Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3058] |
| 819-2977 | [Sun Cluster Data Service for DNS Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-2977] |
| 820-5024 | [Sun Cluster Data Service for Informix Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5024] |
| 819-5415 | [Sun Cluster Data Service for Kerberos Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-5415] |
| 820-5034 | [Sun Cluster Data Service for MaxDB Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5034] |
| 820-5027 | [Sun Cluster Data Service for MySQL Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5027] |
| 819-3060 | [Sun Cluster Data Service for N1 Grid Service Provisioning System for Solaris OS |http://docs.sun.com/app/docs/doc/819-3060] |
| 820-2565 | [Sun Cluster Data Service for NFS Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2565] |
| 820-3041 | [Sun Cluster Data Service for Oracle Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-3041] |
| 820-2572 | [Sun Cluster Data Service for Oracle Application Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2572] |
| 820-2573 | [Sun Cluster Data Service for Oracle E-Business Suite Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-7404] |
| 820-5043 | [Sun Cluster Data Service for Oracle RAC Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5043] |
| 820-5074 | [Sun Cluster Data Service for PostgreSQL Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5074] |
| 820-3040 | [Sun Cluster Data Service for Samba Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-3040] |
| 820-5033 | [Sun Cluster Data Service for SAP Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5033] |
| 820-5035 | [Sun Cluster Data Service for SAP liveCache Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5035] |
| 820-2568 | [Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2568] |
| 820-5036 | [Sun Cluster Data Service for Siebel Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5036] |
| 820-5025 | [Sun Cluster Data Service for Solaris Containers Guide |http://docs.sun.com/app/docs/doc/820-5025] |
| 820-3042 | [Sun Cluster Data Service for Sun Grid Engine Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-3042] |
| 820-5032 | [Sun Cluster Data Service for Sun Java System Application Server EE (HADB) Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5032] |
| 820-5029 | [Sun Cluster Data Service for Sun Java System Application Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5029] |
| 820-5031 | [Sun Cluster Data Service for Sun Java System Message Queue Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5031] |
| 820-5030 | [Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5030] |
| 820-5038 | [Sun Cluster Data Service for SWIFTAlliance Access Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5038] |
| 820-5039 | [Sun Cluster Data Service for SWIFTAlliance Gateway Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5039] |
| 820-2570 | [Sun Cluster Data Service for Sybase ASE Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2570] |
| 820-5037 | [Sun Cluster Data Service for WebLogic Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5037] |
| 819-3068 | [Sun Cluster Data Service for WebSphere Message Broker Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3068] |
| 819-3067 | [Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3067] |
[Top|#top]

h2. {anchor:RELNOTES-35} Sun Cluster 3.2 1/09 Data Service Manuals for Solaris OS (x86 Platform Edition)

|| Part Number || Book Title ||
| 820-7092 | [Sun Cluster Data Service for Apache Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-7092] |
| 819-3057 | [Sun Cluster Data Service for Apache Tomcat Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3057] |
| 819-3058 | [Sun Cluster Data Service for DHCP Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3058] |
| 819-2977 | [Sun Cluster Data Service for DNS Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-2977] |
| 820-5024 | [Sun Cluster Data Service for Informix Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5024] |
| 819-5415 | [Sun Cluster Data Service for Kerberos Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-5415] |
| 820-5034 | [Sun Cluster Data Service for MaxDB Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5034] |
| 820-5027 | [Sun Cluster Data Service for MySQL Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5027] |
| 819-3060 | [Sun Cluster Data Service for N1 Grid Service Provisioning System for Solaris OS |http://docs.sun.com/app/docs/doc/819-3060] |
| 820-2565 | [Sun Cluster Data Service for NFS Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2565] |
| 820-3041 | [Sun Cluster Data Service for Oracle Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-3041] |
| 820-2572 | [Sun Cluster Data Service for Oracle Application Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2572] |
| 820-5043 | [Sun Cluster Data Service for Oracle RAC Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5043] |
| 820-5074 | [Sun Cluster Data Service for PostgreSQL Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5074] |
| 820-3040 | [Sun Cluster Data Service for Samba Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-3040] |
| 820-5033 | [Sun Cluster Data Service for SAP Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5033] |
| 820-5035 | [Sun Cluster Data Service for SAP liveCache Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5035] |
| 820-2568 | [Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2568] |
| 820-5025 | [Sun Cluster Data Service for Solaris Containers Guide |http://docs.sun.com/app/docs/doc/820-5025] |
| 820-3042 | [Sun Cluster Data Service for Sun Grid Engine Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-3042] |
| 820-5032 | [Sun Cluster Data Service for Sun Java System Application Server EE (HADB) Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5032] |
| 820-5029 | [Sun Cluster Data Service for Sun Java System Application Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5029] |
| 820-5031 | [Sun Cluster Data Service for Sun Java System Message Queue Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5031] |
| 820-5030 | [Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5030] |
| 820-2570 | [Sun Cluster Data Service for Sybase ASE Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-2570] |
| 820-5037 | [Sun Cluster Data Service for WebLogic Server Guide for Solaris OS |http://docs.sun.com/app/docs/doc/820-5037] |
| 819-3067 | [Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3067] |
| 819-3068 | [Sun Cluster Data Service for WebSphere Message Broker Guide for Solaris OS |http://docs.sun.com/app/docs/doc/819-3068] |
[Top|#top]

h2. {anchor:RELNOTES-35S} Sun Cluster 3.1-3.2 Hardware Collection for Solaris OS (SPARC Platform Edition)

|| Part Number || Book Title ||
| 819-2993 | [Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-2993] |
| 819-2994 | [Sun Cluster 3.1 - 3.2 With Fibre Channel JBOD Storage Device Manual |http://docs.sun.com/app/docs/doc/819-2994] |
| 819-3024 | [Sun Cluster 3.1 - 3.2 With Network-Attached Storage Devices Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3024] |
| 819-2995 | [Sun Cluster 3.1 - 3.2 With SCSI JBOD Storage Device Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-2995] |
| 820-1692 | [Sun Cluster 3.1 - 3.2 With StorageTek 2540 RAID Arrays Manual for Solaris OS |http://docs.sun.com/app/docs/doc/820-1692] |
| 819-7306 | [Sun Cluster 3.1 - 3.2 With StorageTek RAID Arrays Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-7306] |
| 819-3015 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 3310 or 3320 SCSI RAID Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3015] |
| 819-3016 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 3510 or 3511 FC RAID Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3016] |
| 819-3017 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 3900 Series or Sun StorEdge 6900 Series System Manual |http://docs.sun.com/app/docs/doc/819-3017] |
| 819-3018 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 6120 Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3018] |
| 819-3019 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 6130 Array Manual |http://docs.sun.com/app/docs/doc/819-3019] |
| 819-3020 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 6320 System Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3020] |
| 819-3021 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 9900 Series Storage Device Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3021] |
| 819-2996 | [Sun Cluster 3.1 - 3.2 With StorEdge A1000 Array, Netra st A1000 Array, or StorEdge A3500 System Manual |http://docs.sun.com/app/docs/doc/819-2996] |
| 819-3022 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge A3500FC System Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3022] |
| 819-3023 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge T3 or T3\+ Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3023] |
[Top|#top]

h2. {anchor:RELNOTES-35X} Sun Cluster 3.1-3.2 Hardware Collection for Solaris OS (x86 Platform Edition)

|| Part Number || Book Title ||
| 819-2993 | [Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-2993] |
| 819-3024 | [Sun Cluster 3.1 - 3.2 With Network-Attached Storage Devices Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3024] |
| 819-2995 | [Sun Cluster 3.1 - 3.2 With SCSI JBOD Storage Device Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-2995] |
| 820-1692 | [Sun Cluster 3.1 - 3.2 With StorageTek 2540 RAID Arrays Manual for Solaris OS |http://docs.sun.com/app/docs/doc/820-1692] |
| 819-7306 | [Sun Cluster 3.1 - 3.2 With StorageTek RAID Arrays Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-7306] |
| 817-0180 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 3310 or 3320 SCSI RAID Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/817-0180] |
| 819-3016 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 3510 or 3511 FC RAID Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3016] |
| 819-3018 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 6120 Array Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3018] |
| 819-3019 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 6130 Array Manual |http://docs.sun.com/app/docs/doc/819-3019] |
| 819-3020 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 6320 System Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3020] |
| 819-3021 | [Sun Cluster 3.1 - 3.2 With Sun StorEdge 9900 Series Storage Device Manual for Solaris OS |http://docs.sun.com/app/docs/doc/819-3021] |
[Top|#top]

h1. {anchor:CJACJJJD} Documentation Issues

This section discusses errors or omissions for documentation, online help, or man pages in the Sun Cluster 3.2 1/09 release.
* [Software Installation Guide|#SWIG]
* [System Administration Guide|#SYSADMIN]
* [Data Services Developer's Guide|#GDYMM]
* [Upgrade Guide|#upgrade]
* [Network-Attached Storage Devices Manual|#nas]
* [Man Pages|#X-1DINF]

[Top|#top]

h2. {anchor:SWIG}Software Installation Guide

This section discusses errors and omissions in the _Sun Cluster Software Installation Guide for Solaris OS_.

h3. Change to Restriction of ZFS for Root ({{/}}) File Systems

In "Guidelines for the Root ({{/}}) File System" in Chapter 1, a Note states that no file-system type other than UFS is valid for the root file system. This restriction is no longer valid. However, the {{/globaldevices}} partition for the global-devices namespace still requires the UFS file system.

[Top|#top]

h3. Restriction for Encapsulation of a ZFS Root Disk

The procedure "SPARC: How to Encapsulate the Root Disk" in Chapter 5, "Installing and Configuring Veritas Volume Manager", is not valid when the root disk uses ZFS rather than UFS. For a ZFS root disk, you must instead create the root disk group on local nonroot disks, or choose to not create a root disk group.

[Top|#top]

When you establish a new cluster or new cluster node on the Solaris 10 OS, you can now choose between using a dedicated partition or using a lofi-based file on which to create the global-devices namespace.

Use one of the following methods to choose a lofi device for the global-devices namespace:
* Run the interactive {{scinstall}} utility in Custom mode and, when prompted, specify the use of a lofi device.
* If a {{/globaldevices}} entry does not exist in the {{/etc/vfstab}} files on the hosts that you are configuring as cluster nodes, run the interactive {{scinstall}} utility in Typical mode and, when prompted, choose to use a lofi device.
{info:title=Note:}If the {{scinstall}} utility in Typical mode finds an {{/etc/vfstab}} entry for {{/globaldevices}}, the utility creates the namespace on that file system, the same as in previous Sun Cluster releases. If you choose not to use lofi and no {{/etc/vfstab}} entry for {{/globaldevices}} exists, the installation fails.
{info}
* Add the {{\-G lofi}} option to the {{scinstall}} command in noninteractive mode or the {{clnode add}} command.

If you use a lofi device to create the global-devices namespace, no {{/global/.devices/node@_nodeID{_}}} entry is added to the {{/etc/vfstab}} file. The root file system must have 100 MBytes of free space to create a lofi-based global-devices namespace.

See the following for additional information:

* For information about specifying a lofi device when you establish a cluster or cluster node from the command line, see the [{{scinstall}}(1M)|http://docs.sun.com/app/docs/doc/820-4685/scinstall-1m] and [{{clnode}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/clnode-1cl] man pages.
* For more information about lofi devices, see the [{{lofi}}(7D)|http://docs.sun.com/app/docs/doc/816-5177/lofi-7d] man page.
* For procedures to migrate the global-devices namespace from a dedicated partition to a lofi device or the reverse, see [Migrating the Global-Devices Namespace|#migrategd].

[Top|#top]

h3. {excerpt:hidden=true}1535, for 3.2u2{excerpt} Replacement Command for {{sccheck}}

The {{sccheck}} command is replaced by the {{cluster check}} command. This new {{check}} subcommand performs the same role as {{sccheck}} with the exception of checking the existence of mount points. In the procedure "How to Create Cluster File Systems", continue to use the {{sccheck}} command.

For details about the {{check}} subcommand, see the [{{cluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cluster-1cl] man page.

[Top|#top]

h3. Setting the IPsec {{p2_idletime_secs}} Parameter

phys-schost# *vi /etc/inet/ike/config*

\}
{panel}

This section discusses errors and omissions in the _Sun Cluster System Administration Guide for Solaris OS_.

h3. Restoring an Encapsulated Root File System for VERITAS Volume Manager

The instructions in Chapter 11 for [restoring an encapsulated root file sytem|http://docs.sun.com/app/docs/doc/820-4679/cfhefabj?a=view] for VERITAS Volume Manager are incorrect. Replace Step #14 with the following step:

14. Run the {{clvxvm encapsulate}}  command to encapsulate the disk and reboot.

[Top|#top]

h3. EMC SRDF Data Recovery for Failed Campus Cluster Primary Room

A patch to Sun Cluster 3.2 1/09 software changes Sun Cluster behavior so that if the primary campus cluster room fails, Sun Cluster automatically fails over to the secondary room. The patch makes the secondary room's storage device readable and writable, and enables the failover of the corresponding device groups and resource groups. When the primary room returns online, you can manually run the procedure that recovers the data from the EMC Symmetrix Remote Data Facility (SRDF) device group by resynchronizing the data from the original secondary room to the original primary room.

The following are the minimum patch versions that contain this new functionality:
* Solaris 10 SPARC - 126106-30
* Solaris 10 x86 - 126107-31
* Solaris 9 - 126105-29

In the procedure below, {{dg1}} is the SRDF device group name. At the time of the failure, the primary room in this procedure is {{phys-campus-1}} and the secondary room is {{phys-campus-2}}.

h4. How to Recover EMC SRDF Data After a Primary Room's Complete Failure

# Log in to the campus cluster's primary room and become superuser or assume a role that provides {{solaris.cluster.modify}} RBAC authorization.
# From the primary room, use the {{symrdf}} command to query the replication status of the RDF devices and view information about those devices.
{panel}
phys-campus-1# *symrdf \-g dg1 query*
{panel}A device group that is in the split state is not synchronized.
# If the RDF pair state is split and the device group type is {{RDF1}}, then force a failover of the SRDF device group.
{panel}
phys-campus-1# *symrdf \-g dg1 \-force failover*
{panel}
# View the status of the RDF devices.
{panel}
phys-campus-1# *symrdf \-g dg1 query*
{panel}
# After the failover, you can swap the data on the RDF devices that failed over.
{panel}
phys-campus-1# *symrdf \-g dg1 swap*
{panel}
# Verify the status and other information about the RDF devices.
{panel}
phys-campus-1# *symrdf \-g dg1 query*
{panel}
# Establish the SRDF device group in the primary room.
{panel}
phys-campus-1# *symrdf \-g dg1 establish*
{panel}
# Confirm that the device group is in a synchronized state and that the device group type is {{RDF2}}.
{panel}
phys-campus-1# *symrdf \-g dg1 query*
{panel}

[Top|#top]

h3. Replacement Command for {{sccheck}} {excerpt:hidden=true}1535, for 3.2u2{excerpt}

The {{sccheck}} command is replaced by the {{cluster check}} command. This new {{check}} subcommand performs the same role as {{sccheck}}. For any procedures that use {{sccheck}}, run {{cluster check}} instead. The exception is that, to check the existence of mount points when you create a cluster file system, continue to use the {{sccheck}} command.

In addition, a new {{list-checks}} subcommand is added. Use {{cluster list-checks}} to display a list of all available cluster checks.

For details about the {{check}} and {{list-checks}} subcommands, see the [{{cluster}}(1CL)|http://docs.sun.com/app/docs/doc/820-4685/cluster-1cl] man page.

[Top|#top]

h3. {anchor:migrategd} Migrating the Global-Devices Namespace

The following procedures describe how to move an existing global-devices namespace from a dedicated partition to a {{lofi}} device or the opposite:
* [How to Migrate the Global-Devices Namespace From a Dedicated Partition to a {{lofi}} Device|#tolofi]
* [How to Migrate the Global-Devices Namespace From a {{lofi}} Device to a Dedicated Partition|#fromlofi]

h4. {anchor:tolofi}How to Migrate the Global-Devices Namespace From a Dedicated Partition to a {{lofi}} Device

# Become superuser on the global-cluster voting node whose namespace location you want to change.
# Ensure that no file named {{/.globaldevices}} already exists on the node. If the file does exist, delete it.
# Create the {{lofi}} device.
{panel}
{{\# *mkfile 100m /.globaldevices{*}{}}}{{\# *lofiadm \-a /.globaldevices{*}{}}}{{\# *LOFI_DEV=`lofiadm /.globaldevices`*{}}}{{\# *newfs `echo $\{LOFI_DEV\} \| sed \-e 's/lofi/rlofi/g'` < /dev/null{*}{}}}{{\# *lofiadm \-d /.globaldevices{*}}}
{panel}
# In the {{/etc/vfstab}} file, comment out the global-devices namespace entry. This entry has a mount path that begins with {{/global/.device/node@_nodeID{_}}}.
# Unmount the global-devices partition {{/global/.devices/node@_nodeID{_}}}.
# Disable and re-enable the {{globaldevices}} and {{scmountdev}} SMF services.
{panel}
{{\# *svcadm disable globaldevices{*}{}}}{{\# *svcadm disable scmountdev{*}{}}}{{\# *svcadm enable scmountdev{*}{}}}{{\# *svcadm enable globaldevices{*}}}
{panel}A {{lofi}} device is now created on {{/.globaldevices}} and mounted as the global-devices file system.
# Repeat these steps on any other nodes whose global-devices namespace you want to migrate from a partition to a {{lofi}} device.
# From one node, populate the global-device namespaces.
{panel}
{{\# */usr/cluster/bin/cldevice populate{*}}}
{panel}On each node, verify that the command has completed processing before you perform any further actions on the cluster.
{panel}
{{\# *ps \-ef \| grep scgdevs{*}}}
{panel}The global-devices namespace now resides on a {{lofi}} device.

[Top|#top]

h4. {anchor:fromlofi}How to Migrate the Global-Devices Namespace From a {{lofi}} Device to a Dedicated Partition

# Become superuser on the global-cluster voting node whose namespace location you want to change.
# On a local disk of the node, create a new partition that meets the following requirements:
#* Is at least 512MB in size
#* Uses the UFS file system
# Add an entry to the {{/etc/vfstab}} file for the new partition to be mounted as the global-devices file system.
## Determine the current node's node ID.
{panel}
{{\# */usr/sbin/clinfo \-n{*}{}}}{{{}{_}nodeID{_}}}
{panel}
## Create the new entry in the {{/etc/vfstab}} file, using the following format:
{panel}
{{{_}blockdevice_ _rawdevice_ /global/.devices/node@_nodeID_ ufs 2 no global}}
{panel}For example, if the partition that you choose to use is {{/dev/did/rdsk/d5s3}}, the new entry to add to the {{/etc/vfstab}} file would then be as follows:
{panel}
{{/dev/did/dsk/d5s3 /dev/did/rdsk/d5s3 /global/.devices/node@3 ufs 2 no global}}
{panel}
# Unmount the global devices partition {{/global/.devices/node@_nodeID{_}}}.
# Remove the {{lofi}} device that is associated with the {{/.globaldevices}} file.
{panel}
{{\# *lofiadm \-d /.globaldevices{*}}}
{panel}
# Delete the {{/.globaldevices}} file.
{panel}
{{\# *rm /.globaldevices{*}}}
{panel}
# Disable and re-enable the {{globaldevices}} and {{scmountdev}} SMF services.
{panel}
{{\# *svcadm disable globaldevices{*}{}}}{{\# *svcadm disable scmountdev{*}{}}}{{\# *svcadm enable scmountdev{*}{}}}{{\# *svcadm enable globaldevices{*}}}
{panel}The partition is now mounted as the global-devices namespace file system.
# Repeat these steps on any other nodes whose global-devices namespace you want to migrate from a {{lofi}} device to a partition.
# From one node in the cluster, run the {{cldevice populate}} command to populate the global-devices namespace.
{panel}
{{\# */usr/cluster/bin/cldevice populate{*}}}
{panel}Ensure that the process completes on all nodes of the cluster before you perform any further action on any of the nodes.
{panel}
{{\# *ps \-ef \| grep scgdevs{*}}}
{panel}The global-devices namespace now resides on the dedicated partition.

[Top|#top]

h2. {anchor:GDYMM} Data Services Developer's Guide

This section discusses errors and omissions in the _Sun Cluster Data Services Developer's Guide for Solaris OS_.

h3. Method Timeout Behavior Is Changed

A description of the change in the behavior of method timeouts as of the Sun Cluster 3.2 release is missing. If an RGM method callback times out, the process is now killed by using the {{SIGABRT}} signal instead of the {{SIGTERM}} signal. Terminating the process by using the {{SIGABRT}} signal causes all members of the process group to generate a core file.
{info:title=Note}Avoid writing a data service method that creates a new process group. If your data service method does need to create a new process group, also write a signal handler for the {{SIGTERM}} and {{SIGABRT}} signals. Write the signal handlers to forward the {{SIGTERM}} or {{SIGABRT}} signal to the child process group before the signal handler terminates the parent process. This increases the likelihood that all processes that are spawned by the method are properly terminated.
{info}[Top|#top]

h2. {anchor:upgrade}Upgrade Guide

This section discusses errors and omissions in the _Sun Cluster Upgrade Guide for Solaris OS_.

h3. Incorrect Command to Change the Private-Network IP Address Range

In Step 9 of "How to Finish Upgrade to Sun Cluster 3.2 1/09 Software", an incorrect command is provided to change the IP address range of the private network.

*Incorrect*:
{panel}
{{phys-schost# *cluster set net-props num_zonecluster=*{*}{_}N{_}{*}}}
{panel}{*}Correct*:
{panel}
{{phys-schost# *cluster set-netprops \-p num_zoneclusters=*{*}{_}N{_}{*}}}
{panel}[Top|#top]

h2. {anchor:nas}Network-Attached Storage Devices Manual

The section "Requirements When Configuring Sun NAS Devices as Quorum Devices" omits the following requirement:

The Sun NAS device must be located on the same network as the cluster nodes. If a Sun NAS quorum device is not located on the same network as the cluster nodes, the quorum device is at risk of not responding at boot time within the timeout period, causing the cluster bootup to fail due to lack of quorum.


{excerpt:hidden=true}

h2. {anchor:Oracle RAC}Oracle RAC Data Services Guide

This section discusses the omissions in Oracle RAC data services guide.

h3. Implementing the Sun Cluster Native SKGXN for Oracle RAC

Oracle RAC specifies a set of APIs for distributed process monitoring and cluster configuration services. This set of APIs is known as System Kernel Generic Interface Node membership(SKGXN). Sun Cluster and other cluster softwares use this API to communicate with Oracle RAC.

While using Sun Cluster with Oracle RAC on a SPARC machine, SKGXN is implemented through the ULDM package provided by Oracle. In the latest version of Sun cluster software for SPARC, you can also implement the Sun Cluster native SKGXN instead of Oracle ULDM. This section provides information on how to implement the Sun Cluster native SKGXN with Oracle RAC on a SPARC machine.

h4. Installing Sun Cluster Native SKGXN

Native SKGXN is part of the existing Oracle RAC framework.You should install the RAC framework to get the native SKGXN functionality and ensure that the required patches are applied for the corresponding Oracle version to make the Oracle installation compatible with native SKGXN.


h4. Upgrading the Oracle RAC Resource Type

The patch can be applied in a rolling fashion and the Oracle RAC framework continues to use the Oracle UDLM based SKGXN until patches are applied to all nodes and the resource type upgraded to version 4.
Perform the following steps to apply the patch:
\# *clresourcetype register SUNW.rac_framework:4*
\# *clresource set \-p Type_version=4 rac_fw*
After the upgrade, the new capability to run either the Oracle UDLM or Sun Cluster native SKGXN is enabled.

h4. Preparing the Cluster to change the SKGXN interfaces

Ensure that you have performed the following steps before changing the SKGXN
interface:

# Upgraded the RAC framework resource to version 4.
\# *clresourcetype register SUNW.rac_framework:4*
\# *clresource set \-p Type_version=3 rac_fw*
# Disabled Oracle 10g CRS to prevent it from automatically starting on all nodes.
\# *$\{CRS_HOME}/bin/crsctl disable crs*

For more information on performing this step, see Oracle documentation corresponding to the Oracle version you are using.
# Stopped CRS and all DBMS processes on all nodes.
Note: For more information on performing this step, see Oracle documentation corresponding
to the Oracle version you are using.
\# *$\{CRS_HOME}/bin/crsctl stop crs*
\# */etc/init.d/init.crs stop*
# Unmanaged the Oracle RAC framework resource group.
\# *clresource disable +*
\# *clresourcegroup offline +*
\# *clresourcegroup unmanage +*
# Rebooted the cluster to ensure that the Oracle RAC framework processes have exited.
\# *scshutdown \-g0 \-y*

h4. Converting SKGXN from Oracle UDLM to Sun Cluster native SKGXN

Perform the steps in this procedure to convert the SKGXN interface from Oracle UDLM to Sun Cluster native SKGXN.

Note: You should prepare the cluster to change the SKGXN interface before you perform the steps in this procedure.

# Remove the UDLM resource from the Oracle RAC framework resource group.
\# *clresource delete rac_udlm*
# Remove the Oracle UDLM package from all nodes.
\# *pkgrm ORCLudlm*
# Enable the resources.
\# *clresource enable +*
# Manage the resource groups.
\# *clresourcegroup manage +*
# Bring the resource groups online.
\# *clresourcegroup online +*

h4. Converting SKGXN from Sun Cluster Native SKGXN to Oracle UDLM

Perform the steps in this procedure to convert the SKGXN interface from Sun Cluster native SKGXN to Oracle UDLM.

Note: You should prepare the cluster to change the SKGXN interface before you
perform the steps in this procedure.
Note: For more information, see "Installing Oracle ULDM" in Oracle RAC data services guide.

# Install the Oracle UDLM package on all nodes.
\# *pkgadd \-d . ORCLudlm*
# Create the Oracle UDLM resource in the RAC framework resource group.
\# *clresource create \-g rac-fw-rg \-t SUNW.rac_udlm \-y resource_dependencies=rac_fw rac_udlm*
# Enable the resources.
\# *clresource enable +*
# Manage the resource groups.
\# *resourcefulnesses manage +*
# Bring the resource groups online.
\# *clresourcegroup online +*

h4. Bringing Oracle Online After Switching the SKGXN

Perform the steps in this procedure to bring Oracle online after switching the SKGXN interface.
Note: You should also refer the Oracle documentation corresponding to your Oracle version for information on bringing Oracle online.

# Enable CRS to allow it to start automatically in the future.
\# *$\{CRS_HOME}/bin/crsctl enable crs*

h2. {anchor:X-1DINF} Man Pages

This section discusses errors, omissions, and additions in the Sun Cluster man pages.

h3. clnode(1CL) {excerpt:hidden=true}6747481{excerpt}

The {{clnode}}(1CL) man page states that the {{clnode evacuate}} subcommand works only in a global cluster. However, functionality was added to the {{clnode evacuate}} subcommand so that it does work within a zone cluster.

[Top|#top]

h3. {anchor:clquorum}clquorum(1CL)

The {{status}} subcommand command has been enhanced to actively check the state of quorum devices. The updated description of the {{status}} subcommand should read as follows:

Checks and displays the current status and vote counts of quorum devices.

You can use this subcommand in the global zone or in a non-global zone to immediately check the status of quorum devices that are connected to the specified node. For quorum devices that are not connected to the node, this subcommand displays the status that was true during the previous cluster reconfiguration. For ease of administration, use this form of the command in the global zone.

[Top|#top]

h3. clquorumserver(1CL)


h4. {{disable}} and {{enable}}

Disregard the information previously reported here about {{disable}} and {{enable}} subcommands to the {{clquorumserver}} command. That information was reported in error; these subcommands were not added to the {{clquorumserver}} command.


h4. {{stop}}

The new {{\-d}} option to the {{stop}} subcommand is not documented in the {{clquorumserver}}(1CL) man page. The following is the updated syntax for the {{stop}} subcommand:

{{/usr/cluster/bin/clquorumserver stop \[-d\] {\+ \| _quorumserver_ \[...\]\}}}

The {{\-d}} option disables the automatic restarting of the quorum server after a reboot.

[Top|#top]

h3. clresource(1CL)

The inter-cluster dependencies are not documented in the {{clresource}}(1CL) man page.

A resource in a zone cluster can have a dependency on a resource in another zone cluster or on a resource on the global cluster. Also, a resource from the global cluster can have a dependency on a resource in any of the zone clusters on that global cluster. The inter-cluster dependencies can be set only from the global cluster.

You can use the following command to specify the inter-cluster dependencies:
{panel}
{{\# *clresource set \-p resource_dependencies=*{*}{_}target-zc{_}{*}*:*{*}{_}target-rs{_}* *{_}source-zc{_}{*}*:*{*}{_}source-rs{_}{*}}}
{panel}For example, if you need to specify a dependency from resource {{R1}} in zone cluster {{ZC1}} to a resource {{R2}} in zone cluster {{ZC2}}, use the following command:
{panel}
{{\# *clresource set \-p resource_dependencies=ZC2:R2 ZC1:R1{*}}}
{panel}If you need to specify a dependency of zone cluster {{ZC1}} resource {{R1}} on global-cluster resource {{R2}}, use the following command:
{panel}
{{\# *clresource set \-p resource_dependencies=global:R2 ZC1:R1{*}}}
{panel}The existing resource dependencies ({{Strong}}, {{Weak}}, {{Restart}},and {{Offline-Restart}}) are supported.

[Top|#top]

h3. clresourcegroup(1CL)

The zone cluster affinities are not documented in the {{clresourcegroup}}(1CL) man page.

The cluster administrator can specify affinities between a resource group in a zone cluster and a resource group in another zone cluster or a resource group on the global cluster. You can use the following command to specify the affinities between resource groups in different zone clusters:
{panel}
\# *clresourcegroup set \-p RG_affinities=*{*+*\|*\+\+*\|*\-*\|*\-\-*}{_}target-zc_:_target-rg_ _source-zc_:_source-rg_
{panel}The affinity types can be one of the following:
* + (weak positive)
* \+\+ (strong positive)
* \- (weak negative)
* \-\- (strong negative)

*Note*: The affinity type \++\+ (strong positive with failover delegation) is not supported in this release.

For example,if you need to specify a strong positive affinity ({{\+\+}}) between resource group {{RG1}} in zone cluster {{ZC1}} and resource group {{RG2}} in zone cluster {{ZC2}}, use the following command:
{panel}
{{\# *clresourcegroup set \-p RG_affinities=++ZC2:RG2 ZC1:RG1{*}}}
{panel}If you need to specify a strong negative affinity ({{\-\-}}) between resource group {{RG1}} in zone cluster {{ZC1}} and resource group {{RG2}} in the global cluster, use the following command:
{panel}
{{\# *clresourcegroup set \-p RG_affinities=--global:RG2 ZC1:RG1{*}}}
{panel}

[Top|#top]

h3. clresourcetype(1CL)

The description of the {{set}} subcommand currently states, "The only resource type property that you can set is the Installed_nodes property." This property is no longer the only property that is tunable at any time. See the {{rt_properties}}(5) man page for the descriptions of resource-type properties, including when each is tunable.

[Top|#top]

h3. cluster(1CL)


h4. {{\-f}} Option

The {{check}} and {{list-checks}} subcommands support the following option, which is not documented in the {{cluster}}(1CL) man page:

{{\-F{}}}{{\--force}}

Forces the execution of the subcommand by ignoring the {{/var/cluster/logs/cluster_check/cfgchk.lck}} file, if it exists. Use this option only if you are sure that the {{check}} and {{list-checks}} subcommands are not already running.

h4. Zone Cluster Compatibility {excerpt:hidden=true}(6747519){excerpt}

The {{cluster}}(1CL) man page states that the {{cluster}} command does not work in a zone cluster. However, functionality was added to the following {{cluster}} subcommands to make them work within a zone cluster:

* {{cluster show}} \- Lists the zone cluster, nodes, resource groups, resource types,and resource properties.
* {{cluster status}} \- Displays the status of zone cluster components.
* {{cluster shutdown}} \- Shuts down the zone cluster in an orderly fashion.
* {{cluster list}} \- Displays the name of the zone cluster.
* {{cluster list-cmds}} \- Lists the following commands, which are supported inside a zone cluster:
** {{clnode}}
** {{clreslogicalhostname}}
** {{clresource}}
** {{clresourcegroup}}
** {{clresourcetype}}
** {{clressharedaddress}}
** {{cluster}}

h3. {{scdpmd.conf}}(4)

The following new man page describes how to tune the {{scdpmd}} daemon.

h5. Name

scdpmd.conf - Disk-path-monitoring daemon configuration file

h5. Synopsis

{{/etc/cluster/scdpm/scdpmd.conf}}

h5. Description

The {{scdpmd}} daemon monitors the disk paths and takes appropriate action upon path failures. You can tune this daemon by creating or modifying the configuration file {{/etc/cluster/scdpm/scdpmd.conf}} with tunable properties and send a {{SIGHUP}} signal to the {{scdpmd}} daemon to read the configuration file.

{panel}\# *pkill \-HUP scdpmd{*}{panel}

You can tune the following properties in the {{scdpmd.conf}} file:

{{ping_interval}}

&nbsp;&nbsp;&nbsp; Description
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Interval, in seconds, between disk-path status checks

&nbsp;&nbsp;&nbsp; Default
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 600

&nbsp;&nbsp;&nbsp; Minimum
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 60

&nbsp;&nbsp;&nbsp; Maximum
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3600

{{ping_retry}}

&nbsp;&nbsp;&nbsp; Description
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Number of retries to query the disk-path status on failure

&nbsp;&nbsp;&nbsp; Default
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3

&nbsp;&nbsp;&nbsp; Minimum
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2

&nbsp;&nbsp;&nbsp; Maximum
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 10

{{ping_timeout}}

&nbsp;&nbsp;&nbsp; Description
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Timeout, in seconds, to query any disk-path status

&nbsp;&nbsp;&nbsp; Default
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 5

&nbsp;&nbsp;&nbsp; Minimum
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 1

&nbsp;&nbsp;&nbsp; Maximum
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 15

h5. Examples

The following is an example of a valid {{scdpmd.conf}} file:

ping_interval = 120
ping_retry = 5
ping_timeout = 10

h5. Attributes

See {{attributes}}(5) for descriptions of the following attributes:
|| ATTRIBUTE TYPE || ATTRIBUTE VALUE ||
| Interface Stability | Evolving |

h5. See Also

{{cldevice}}(1CL), {{clnode}}(1CL)

[Top|https://wikis.sun.com/display/SunCluster/Sandbox+for+Release+Notes#SandboxforReleaseNotes-top]Labels parameters

h2. Labels


[Top|#top]