This section contains information about Sun Cluster compatibility issues, such as features nearing end of life.
Additional Sun Cluster framework compatibility issues are documented in Chapter 1, Planning the Sun Cluster Configuration, in Sun Cluster Software Installation Guide for Solaris OS.
Additional Sun Cluster upgrade compatibility issues are documented in Upgrade Requirements and Software Support Guidelines in Sun Cluster Software Installation Guide for Solaris OS.
For other known problems or restrictions, see Known Issues and Bugs.
The following features are nearing end of life in Sun Cluster 3.2 software.
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.
As of Sun Cluster 3.2, Sun Cluster will not longer support Solaris 8.
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.
The sccheck command might not be included in a future release. However, the corresponding functionality will be provided by the cluster check command.
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.
You must upgrade your operating system to Solaris 10 11/06 before applying the Solaris patches.
metaset command fails after the rpcbind server is restarted.
disksets: devid information not written to a newly created diskset.
svm exited with error 1 in step cmmstep5, nodes panic.
fsck: svc:/system/filesystem/usr fails to start from milestone none.
Solaris Volume Manager (SVM) does not show metaset after cluster upgrade in x86.
commd timeout should be a percentage of metaclust timeout value.
metaset -s diskset -t should take ownership of a cluster node after reboot.
SVM still removes the diskset if the Sun Cluster nodeid file is missing.
fsck* svc:/systsem/filesystem/usr fails to start from milestone.
New fsck_ufs(1M) has nits when dealing with already mounted file.
Node panics with CMM:cluster lost operational quorum in amd64.
create_ramdisk: cannot seek to offset -1.
Add etc/cluster/nodeid entry to filelist.ramdisk.
create_ramdisk needs to react less poorly to missing files or directories.
devfsadm link removal does not provide full interpose 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:
Supported on local filesystems not managed by Sun Cluster software
Not supported on global filesystems
Not supported on local filesystems under the control of HAStoragePlus
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.
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.
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.