Sun Cluster 3.1 Data Service 5/03 Release Notes

What's New in Sun Cluster 3.1 Data Services 5/03

This section describes new features and functionality. Contact your Sun sales representative for the complete list of supported hardware and software.

New Error Messages

For error messages that were not included on the Sun Cluster CD-ROM, see Sun Cluster 3.1 5/03 Release Notes.

Automatic End Backup Facility

This new Sun Cluster HA for Oracle feature recognizes when a database fails to start because of files left in hot backup mode. This feature takes the necessary action to reopen the database for use. You can turn this feature on and off. The default state is OFF.

For information on the Auto_End_Bkp extension property that enables this feature, see Sun Cluster 3.1 Data Service for Oracle.

Resource Type Upgrade

As newer versions of resource types are released, you will want to install and register the upgraded resource type. You may also want to upgrade your existing resources to the newer resource type versions. The Resource Type Upgrade feature enables you to upgrade an existing resource to a new resource type version. For documentation on this new feature, see “Upgrading a Resource Type” in Sun Cluster 3.1 Data Service Planning and Administration Guide.

Sun Cluster HA for SAP liveCache

Sun Cluster HA for SAP liveCache is a data service that makes liveCache highly available. Sun Cluster HA for SAP liveCache provides fault monitoring and automatic failover for liveCache and fault monitoring and automatic restart for SAP xserver, eliminating a single point of failure in an SAP Advanced Planner & Optimizer (APO) System. With a combination of Sun Cluster HA for SAP liveCache and other Sun Cluster data services, Sun Cluster software provides a complete solution to protect SAP components in a Sun Cluster environment.

For documentation on Sun Cluster HA for SAP liveCache, see Sun Cluster 3.1 Data Service for SAP liveCache.

Sun Cluster HA for Siebel

Sun Cluster HA for Siebel provides Fault Monitoring and automatic failover for the Siebel application. High availability is provided for the Siebel gateway and Siebel server. With a Siebel implementation, any physical node running the Sun Cluster agent cannot be running the Resonate agent as well. Resonate and Sun Cluster can co-exist within the same Siebel enterprise, but not on the same physical server.

For documentation on Sun Cluster HA for Siebel, see Sun Cluster 3.1 Data Service for Siebel.

Support for Sun ONE Proxy Server

Sun Cluster HA for Sun ONE Web Server now supports Sun ONE Proxy Server. For information about the Sun ONE Proxy Server product, see http://docs.sun.com/db/prod/s1.webproxys. For Sun ONE Proxy Server installation and configuration information, see http://docs.sun.com/db/coll/S1_ipwebproxysrvr36.

New Supported Data Services

Sun Cluster 3.1 Data Services 5/03 supports the following data services:

Sun Cluster HA for WebLogic Server – BEA WebLogic Server running on Sun Cluster systems delivers a highly available platform for developing and deploying mission-critical e-commerce applications across distributed, heterogeneous application environments.

The Sun Cluster HA for BEA WebLogic Server provides fault monitoring and high availability for the BEA WebLogic Server application. High availability is provided for the WebLogic Administration Server and WebLogic Managed Servers.
Sun Cluster HA for DHCP – Solaris DHCP provides dynamic TCP/IP configuration to a DHCP client. The Sun Cluster HA for DHCP data service uses the DHCP software that is bundled with Solaris 8 and Solaris 9.

The Sun Cluster HA for DHCP data service provides a mechanism for orderly startup and shutdown, fault monitoring and automatic failover of the DHCP service.
Sun Cluster HA for Samba – Samba is an Open Source/Freeware suite that provides seamless file and print services to SMB/CIFS clients.

The Sun Cluster HA for Samba data service provides a mechanism for orderly startup and shutdown, fault monitoring and automatic failover of the Samba service.
Sun Cluster HA for WebSphere MQ Integrator – WebSphere MQ Integrator works with WebSphere MQ messaging, extending its basic connectivity and transport capabilities to provide a powerful message broker solution driven by business rules.

The Sun Cluster HA for WebSphere MQ Integrator data service provides a mechanism for orderly startup and shutdown, fault monitoring and automatic failover for the WebSphere MQ Integrator service.
Sun Cluster HA for WebSphere MQ – WebSphere MQ messaging software enables business applications to exchange information across different operating platforms in a way that is easy and straightforward for programmers to implement. Programs communicate using the WebSphere MQ API that assures once only delivery and time independent communications.

The Sun Cluster HA for WebSphere MQ data service provides a mechanism for orderly startup and shutdown, fault monitoring and automatic failover of the WebSphere MQ service.

Supported Products

This section describes the supported software and memory requirements for Sun Cluster 3.1 software.

Operating environment and patches – Supported Solaris versions and patches are available at the following URL:

http://sunsolve.sun.com

For more details, see Patches and Required Firmware Levels.
Volume managers
- On Solaris 8 – Solstice DiskSuite^TM 4.2.1 and VERITAS Volume Manager 3.2 and 3.5.
- On Solaris 9 – Solaris Volume Manager and VERITAS Volume Manager 3.5.
Note –
If you are upgrading from VERITAS Volume Manager (VxVM) 3.2 to 3.5, the Cluster Volume Manger (CVM) feature will not be available until you install the CVM license key for version 3.5. In VxVM 3.5, the CVM license key for version 3.2 does not enable CVM and must be upgraded to the CVM license key for version 3.5.
File systems
- On Solaris 8 – Solaris UFS and VERITAS File System 3.4 and 3.5.
- On Solaris 9 – Solaris UFS and VERITAS File System 3.5.

Data services (agents) – Contact your Sun sales representative for the complete list of supported data services and application versions. Specify the resource type names when you install the data services by using the scinstall(1M) utility. You should also specify the resource type names when you register the resource types associated with the data service using the scsetup(1M) utility.

Note –

Procedures for Sun Cluster HA for Sun ONE Directory Server using iPlanet Directory Server 5.0 and 5.1 (plus Netscape HTTP, versions 4.11, 4.12, 4.13, and 4.16) are located in the Sun Cluster 3.1 Data Service for Sun ONE Directory Server. For later versions of iPlanet Directory Server (now known as Sun ONE Directory Server), see the Sun ONE documentation included with the data service.

Table 1–1 Supported Data Services for Sun Cluster 3.1 Software


Data Service	Sun Cluster Resource Type
Sun Cluster HA for Apache	`SUNW.apache`
Sun Cluster HA for BroadVision One-To-One Enterprise	`SUNW.bv`
Sun Cluster HA for DHCP	`SUNW.gds`
Sun Cluster HA for DNS	`SUNW.dns`
Sun Cluster HA for Sun ONE Web Server (This data service was formerly known as Sun Cluster HA for iPlanet Web Server)	`SUNW.iws`
Sun Cluster HA for NetBackup	`SUNW.netbackup`
Sun Cluster HA for NFS	`SUNW.nfs`
Sun Cluster HA for Sun ONE Directory Server (This data service was formerly known as Sun Cluster HA for iPlanet Directory Server)	`SUNW.nsldap`
Sun Cluster HA for Oracle	`SUNW.oracle_server` `SUNW.oracle_listener`
Sun Cluster HA for SAP	`SUNW.sap_ci` `SUNW.sap_ci_v2` `SUNW.sap_as` `SUNW.sap_as_v2`
Sun Cluster HA for Sun ONE Application Server	`SUNW.s1as`
Sun Cluster HA for Sun ONE Message Queue	`SUNW.s1mq`
Sun Cluster HA for Sybase ASE	`SUNW.sybase`
Sun Cluster Support for Oracle Parallel Server/Real Application Clusters	N/A
Sun Cluster HA for SAP liveCache	`SUNW.sap_livecache` `SUNW.sap_xserver`
Sun Cluster HA for Samba	`SUNW.gds`
Sun Cluster HA for Siebel	`SUNW.sblgtwy` `SUNW.sblsrvr`
Sun Cluster HA for WebLogic Server	`SUNW.wls`
Sun Cluster HA for WebSphere MQ	`SUNW.gds`
Sun Cluster HA for WebSphere MQ Integrator	`SUNW.gds`

Memory Requirements – Sun Cluster 3.1 software requires extra memory beyond what is configured for a node under a normal workload. The extra memory equals 128 Mbytes plus ten percent. For example, if a standalone node normally requires 1 Gbyte of memory, you need an extra 256 Mbytes to meet memory requirements.
RSMAPI – Sun Cluster 3.1 software supports the Remote Shared Memory Application Programming Interface (RSMAPI) on RSM-capable interconnects, such as PCI-SCI.

Sun Cluster Security Hardening

Sun Cluster Security Hardening uses the Solaris Operating Environment hardening techniques recommended by the Sun BluePrints^TM 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. You can also access the article from http://wwws.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.1 deployments in a Solaris 8 and Solaris 9 environment. The description includes the use of the Solaris Security Toolkit and other best-practice security techniques recommended by Sun security experts.

Table 1–2 Data Services Supported by Sun Cluster Security Hardening


Data Service Agent	Application Version: Failover	Application Version: Scalable	Solaris Version
Sun Cluster HA for BEA WebLogic Server	7.0	N/A	Solaris 8, Solaris 9
Sun Cluster HA for iPlanet Messaging Server	6.0	4.1	Solaris 8
Sun Cluster HA for Sun ONE Web Server	6.0	4.1	Solaris 8, Solaris 9 (version 4.1)
Sun Cluster HA for Apache	1.3.9	1.3.9	Solaris 8, Solaris 9 (version 1.3.9)
Sun Cluster HA for SAP	4.6D (32 and 64 bit) and 6.20	4.6D (32 and 64 bit) and 6.20	Solaris 8, Solaris 9
Sun Cluster HA for Sun ONE Directory Server	4.12	N/A	Solaris 8, Solaris 9 (version 5.1)
Sun Cluster HA for NetBackup	3.4	N/A	Solaris 8
Sun Cluster HA for Oracle	8.1.7 and 9i (32 and 64 bit)	N/A	Solaris 8, Solaris 9 (HA Oracle 9iR2)
Sun Cluster HA for Siebel	7.5	N/A	Solaris 8
Sun Cluster HA for Sybase ASE	12.0 (32 bit)	N/A	Solaris 8
Sun Cluster Support for Oracle Parallel Server/Real Application Clusters	8.1.7 and 9i (32 and 64 bit)	N/A	Solaris 8, Solaris 9
Sun Cluster HA for DNS	with OS	N/A	Solaris 8, Solaris 9
Sun Cluster HA for NFS	with OS	N/A	Solaris 8, Solaris 9

Restrictions

Running Sun Cluster HA for Oracle 3.0 on Sun Cluster 3.1

The Sun Cluster HA for Oracle 3.0 data service can run on Sun Cluster 3.1 only when used with the following versions of the Solaris operating environment:

Solaris 8, 32-bit version
Solaris 8, 64-bit version
Solaris 9, 32-bit version

Note –

The Sun Cluster HA for Oracle 3.0 data service cannot run on Sun Cluster 3.1 when used with the 64-bit version of Solaris 9.

Sun Cluster HA for Oracle Parallel Server/Real Application Cluster

Adhere to the documentation of Oracle Parallel Fail Safe/Real Application Clusters Guard option of Oracle Parallel Server/Real Application clusters because you cannot change hostnames after you install Sun Cluster software.

For more information on this restriction on hostnames and node names, see the Oracle Parallel Fail Safe/Real Application Clusters Guard documentation.

Sun Cluster HA for NetBackup

If the VERITAS NetBackup client is a cluster, only one logical host can be configured as the client because there is only one bp.conf file.
If the NetBackup client is a cluster and if one of the logical hosts on the cluster is configured as the NetBackup client, NetBackup cannot back up the physical hosts.
On the cluster running the master server, the master server is the only logical host that can be backed up.
Backup media cannot be attached to the master server, so one or more media servers are required.

Sun Cluster HA for NFS

No Sun Cluster node may be an NFS client of a Sun Cluster HA for NFS-exported file system being mastered on a node in the same cluster. Such cross-mounting of Sun Cluster HA for NFS is prohibited. Use the cluster file system to share files among cluster nodes.
Applications running locally on the cluster must not lock files on a file system exported via NFS. Otherwise, local blocking (for example, flock(3UCB) or fcntl(2)) might interfere with the ability to restart the lock manager (lockd). During restart, a blocked local process may be granted a lock which may be intended to be reclaimed by a remote client. This would cause unpredictable behavior.
Sun Cluster HA for NFS requires that all NFS client mounts be “hard” mounts.
For Sun Cluster HA for NFS, do not use hostname aliases for network resources. NFS clients mounting cluster file systems using hostname aliases might experience statd lock recovery problems.
Sun Cluster 3.1 software does not support Secure NFS or the use of Kerberos with NFS, in particular, the secure and kerberos options to the share_nfs(1M) subsystem. However, Sun Cluster 3.1 software does support the use of secure ports for NFS by adding the entry set nfssrv:nfs_portmon=1 to the /etc/system file on cluster nodes.