test

Sun Cluster 3.2 Release Notes for Solaris OS

Compatibility Issues

This section contains information about Sun Cluster compatibility issues, such as features nearing end of life.

Features Nearing End of Life

The following features are nearing end of life in Sun Cluster 3.2 software.

Sun Cluster 3.0

As of the Sun Cluster 3.2 release, Sun Cluster 3.0 is being discontinued. The Sun Cluster 3.0 part number will no longer be available.

Solaris 8

As of Sun Cluster 3.2, Sun Cluster will not longer support Solaris 8.

Rolling Upgrade

The rolling upgrade functionality might not be available for upgrading Sun Cluster to the next minor release. In that case, other procedures will be provided that are designed to limit cluster outage during those software upgrades.

sccheck

The sccheck command might not be included in a future release. However, the corresponding functionality will be provided by the cluster check command.

Solaris 10 11/06 Operating System

The following known issues might affect the operation of the Sun Cluster 3.2 release with Solaris 10 11/06 operating system. Contact your Sun representative to obtain the necessary Solaris patches to fix these issues. For more information, refer to Infodoc 87995.

Caution – Caution –

You must upgrade your operating system to Solaris 10 11/06 before applying the Solaris patches.

6252216

metaset command fails after the rpcbind server is restarted.

6331216

disksets: devid information not written to a newly created diskset.

6345158

svm exited with error 1 in step cmmstep5, nodes panic.

6367777

fsck: svc:/system/filesystem/usr fails to start from milestone none.

6401357

Solaris Volume Manager (SVM) does not show metaset after cluster upgrade in x86.

6402556

commd timeout should be a percentage of metaclust timeout value.

6474029

metaset -s diskset -t should take ownership of a cluster node after reboot.

6496941

SVM still removes the diskset if the Sun Cluster nodeid file is missing.

6367777

fsck* svc:/systsem/filesystem/usr fails to start from milestone.

6367948

New fsck_ufs(1M) has nits when dealing with already mounted file.

6425930

Node panics with CMM:cluster lost operational quorum in amd64.

6361537

create_ramdisk: cannot seek to offset -1.

6393691

Add etc/cluster/nodeid entry to filelist.ramdisk.

6344611

create_ramdisk needs to react less poorly to missing files or directories.

6462748

devfsadm link removal does not provide full interpose support.

fssnap Support

Sun Cluster does not support fssnap which is a feature of UFS. You can use fssnap on local systems that are not controlled by Sun Cluster. The following restrictions apply to fssnap support:

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.

Loopback File System (LOFS)

Sun Cluster 3.2 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 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.

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 upon request to determine which versions are best suited for deploying accessible solutions.