Sun Cluster 3.0 12/01 Release Notes

New Features and Functionality

The following table lists new features and functionality that require updates to the Sun Cluster documentation. The second column identifies the documentation that was updated. Contact your Sun sales representative for the complete list of supported hardware and software.

Table 1-1 New Features and Functionality


Feature or Functionality	Documentation Updates
Enhancements to installation	The Sun Cluster 3.0 12/01 Software Installation Guide was updated to include new functionality added to the `scinstall`(1M) and `scsetup`(1M) commands. During Sun Cluster software installation, `sccheck` checks and validates the node to ensure that it meets the very basic configuration required for it to be functional in a Sun Cluster configuration. The `sccheck`(1M) man page has also been updated to reflect this new functionality. The interactive `scinstall` installation method also now provides optional autodiscovery of installed cluster transport adapters.
Support for the Remote Shared Memory Application Programming Interface (RSMAPI)	The Sun Cluster 3.0 12/01 Software Installation Guide was updated with steps to install the software packages required to support the RSMAPI in a Sun Cluster configuration.
Dynamic reconfiguration support	A new section was added to the Sun Cluster 3.0 12/01 Concepts that describes the initial phase of Sun Cluster 3.0 support for the dynamic reconfiguration feature. Considerations and manual actions required by the user for this phase are described.
PCI-SCI interconnect support	The Sun Cluster 3.0 12/01 Hardware Guide chapter on interconnect hardware was updated to include sample cabling diagrams, considerations, and troubleshooting to support the use of PCI-SCI interconnect hardware in a cluster. The Sun Cluster 3.0 12/01 Software Installation Guide was also updated with steps to install PCI-SCI software packages.
Storage Area Network (SAN) support	The Sun Cluster 3.0 12/01 Hardware Guide was updated with SAN information, including sample cabling diagrams, supported SAN features, and considerations in each of the four chapters for the storage arrays on which the SAN functionality is supported. The arrays that support SANs are the Sun StorEdge A5200 array, the Sun StorEdge A3500FC array, and the Sun StorEdge T3/T3+ arrays in single-controller configuration and in partner-group configuration.
Sun StorEdge T3+ qualification	The two Sun Cluster 3.0 12/01 Hardware Guide chapters for Sun StorEdge T3 arrays in single-controller configuration and in partner-group configuration were updated to accommodate differences for the Sun StorEdge T3+ arrays. Some procedures in both chapters were also modified with improvements encountered during testing.
Sun Netra D130 and Sun StorEdge S1 qualification	The Sun Cluster 3.0 12/01 Hardware Guide was updated with a new chapter that describes procedures for the Sun Netra D130 and Sun StorEdge S1 storage enclosures.
Support for VERITAS File System (VxFS)	The Sun Cluster 3.0 12/01 Software Installation Guide and the Sun Cluster 3.0 12/01 System Administration Guide were updated to include instructions to create VxFS cluster file systems. See Guidelines to Support VxFS for more information.
Sun Cluster HA for BroadVision One-To-One Enterprise qualification	The Sun Cluster 3.0 12/01 Data Services Installation and Configuration Guide was updated with a new chapter required to support Sun Cluster HA for BroadVision One-To-One Enterprise. This data service uses fault monitoring and automatic failover to eliminate single points of failure in a BroadVision One-To-One Enterprise installation.
Support for Sun Cluster HA for Oracle on Oracle 9i.	The Sun Cluster 3.0 12/01 Data Services Installation and Configuration Guide was updated with new procedures required to support Sun Cluster HA for Oracle on Oracle 9i.
Support for Sun Cluster Security Hardening	The Sun Cluster Security Hardening documentation is available at http://www.sun.com/security/blueprints. From this URL, scroll down to the Architecture heading to locate the article on Sun Cluster Security Hardening. See Sun Cluster Security Hardening for more information.

Notes on New Features and Functionality

This section includes additional information on new features and functionality.

Sun Cluster Security Hardening

Sun Cluster Security Hardening uses the Solaris Operating Environment 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. Sun Cluster Security Hardening supports the following three agents.

Apache Web Server
iPlanet Web Server
iPlanet Mail Server

The Sun Cluster Security Hardening documentation is available at http://www.sun.com/security/blueprints. From this URL, scroll down to the Architecture heading to locate the article on Sun Cluster Security Hardening.

Guidelines to Support VxFS

The following VxFS features are not supported in a Sun Cluster 3.0 configuration.

Quick I/O
Snapshots
Storage checkpoints
Cache advisories (these can be used, but the effect will be observed on the given node only)
VERITAS CFS (requires VERITAS cluster feature & VCS)
VxFS-specific mount options
- convosync (Convert O_SYNC)
- mincache
- qlog, delaylog, tmplog

All other VxFS features and options that are supported in a cluster configuration are supported by Sun Cluster 3.0 software. See VxFS documentation and man pages for details about VxFS options that are or are not supported in a cluster configuration.

The following guidelines for how to use VxFS to create highly available cluster file systems are specific to a Sun Cluster 3.0 configuration.

Create a VxFS file system by following procedures in VxFS documentation.
Globally mount and unmount a VxFS file system from the primary node (the node that masters the disk on which the VxFS file system resides) to ensure that the operation succeeds. A VxFS file system mount or unmount operation that is performed from a secondary node might fail.
Perform all VxFS administration commands from the primary node of the VxFS cluster file system.

The following guidelines for how to administer VxFS cluster file systems are not specific to Sun Cluster 3.0 software. However, they are different from the way you administer UFS cluster file systems.

You can access and administer files on a VxFS cluster file system from any node in the cluster, with the exception of ioctls, which you must issue only from the primary node. If you do not know whether an administration command involves ioctls, issue the command from the primary node.
If a VxFS cluster file system fails over to a secondary node, all standard-system-call operations that were in progress during failover are re-issued transparently on the new primary. However, any ioctl-related operation in progress during the failover will fail. After a VxFS cluster file system failover, check the state of the cluster file system. There might be administrative commands that were issued on the old primary before failover that require corrective measures. See VxFS documentation for more information.