Sun Cluster 3.1 8/05 Release Notes for Solaris OS

Compatibility Issues

This section contains information on 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 Overview of Upgrading a Sun Cluster Configuration in Sun Cluster Software Installation Guide for Solaris OS.

For other known problems or restrictions, see Known Issues and Bugs.

Features Nearing End of Life

Solstice DiskSuite

Solstice DiskSuite software might not be supported in a future release of Sun Cluster software. If you use Solstice DiskSuite software, upgrade to the Solaris 9 or Solaris 10 OS, which will upgrade you automatically to Solaris Volume Manager software. For upgrade information, see Solaris 9 9/04 Installation Guide or Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Sun Fire Link

Sun Fire Link might not be supported in a future release of Sun Cluster software. If you use Sun Fire Link, use another interconnect technology that Sun Cluster software supports. For information about interconnect hardware that Sun Cluster software supports, see Chapter 3, Installing Cluster Interconnect Hardware and Configuring VLANs, in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS.

SunPlex Installer

SunPlex Installer might not be supported in a future release of Sun Cluster software. To establish a new Sun Cluster configuration, use the scinstall utility instead. The scinstall utility supports, through the command line interface, all functionality that SunPlex Installer provides.

SunPlex Manager/Configuration of IPMP Groups

The configuration of IPMP groups (add or remove) might not be included in a future release. This function is available through the Solaris ifconfig(1M) command. See the ifconfig(1M) man page for information on specific options.

SUNW.RGOffload

The SUNW.RGOffload resource type might not be available in future Sun Cluster releases. All functions provided by this resource type are available through the RG_affinities resource group property and its "negative affinity" option.

If you have currently configured a SUNW.RGOffload resource, perform the following actions to use the "negative affinity" option of the RG_affinities resource group property.

How to Use the Negative Affinity Option of RG_affinities

Steps

Remove the dependency of the critical resource on the SUNW.RGOffload resource.
# scrgadm -cj critical-rs -y Resource_dependencies=""

Remove the SUNW.RGOffload resource and resource type.

# scrgadm -nj rgofl
# scrgadm -rj rgofl
# scrgadm -rt SUNW.RGOffload

Change the non-critical resource group property to have a negative affinity towards the critical resource group (which contains critical-rs).
# scrgadm -c -g non-critical-rg -y RG_affinities=--critical-rg
Note –
This example shows only a strong negative affinity. You may be able to set weak negative affinity, and other type of dependencies across online resource groups. Please refer to Distributing Online Resource Groups Among Cluster Nodes in Sun Cluster Data Services Planning and Administration Guide for Solaris OSfor details on configuring online resource group dependencies feature.

Solstice DiskSuite/Solaris Volume Manager GUI

DiskSuite Tool (Solstice DiskSuite metatool) and the Enhanced Storage module of Solaris Management Console (Solaris Volume Manager) are not compatible with Sun Cluster software. Use the command-line interface or Sun Cluster utilities to configure Solstice DiskSuite or Solaris Volume Manager software.

Non-Global Zones

Sun Cluster 3.1 8/05 software does not support non-global zones. All Sun Cluster software and software that is managed by the cluster must be installed only on the global zone of the node. Do not install cluster-related software on a non-global zone. In addition, all cluster-related software must be installed in a way that prevents propagation to a non-global zone that is later created on a cluster node. For more information, see Adding a Package to the Global Zone Only in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

However, Sun Cluster 3.1 8/05 software does support applications that run in a non-global zone and that are managed by the Sun Cluster HA for Solaris Containers data service. See Sun Cluster HA for Solaris Containers for more information.

Loopback File System (LOFS)

Sun Cluster 3.1 8/05 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 under Sun Cluster HA for Solaris Containers, first determine whether the LOFS restrictions apply to your configuration. See Cluster File Systems in Sun Cluster Software Installation Guide for Solaris OS for more information about the restrictions and workarounds that permit the use of LOFS when the restricting conditions exist.

Upgrade to Solaris 10

Sun Cluster 3.1 8/05 software does not support upgrade to the original release of the Solaris 10 OS, which was distributed in March 2005. You must upgrade to a compatible version of Solaris 10. Contact your Sun service representative for more information.

Change to VxVM Installation Procedures

The scvxinstall command and Sun Cluster procedures have changed for installing VxVM software in a Sun Cluster configuration. See Installing and Configuring VxVM Software in Sun Cluster Software Installation Guide for Solaris OS.

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 available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at: http://sun.com/software/javaenterprisesystem/get.html. For information on Sun's commitment to accessibility, visit http://sun.com/access.