Continentalclusters Version A.07.
Legal Notices © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Continentalclusters Version A.07.00 Release Notes 1 Chapter 1 Continentalclusters Version A.07.
Continentalclusters Version A.07.00 Release Notes Announcements Announcements Continentalclusters is a Hewlett-Packard high availability solution that provides disaster tolerant clustering with no distance limitation. Version A.07.00 of Continentalclusters, which contains enhancements and defect fixes, is being released on HP-UX 11i v2 and HP-UX 11i v3 with the following product number: • T2346BA - license, media, and documentation Version A.07.
Continentalclusters Version A.07.00 Release Notes Announcements Table 1-1 Metrocluster Version Requirements for Continentalclusters Oracle RAC Support (Continued) Continentalcluster Version A.07.00 Metrocluster Continuous Access XP Version HP-UX Versions HP-UX 11i v2 and HP-UX 11i v3 SGeRAC Versions A.11.17. and A.11.18 Supported Oracle Versions 9i, 9i RAC, 10g, and 10g RAC Metrocluster Continuous Access EVA Version HP-UX 11i v2 A.11.17. and A.11.
Continentalclusters Version A.07.00 Release Notes What’s In This Version What’s In This Version Continentalclusters employs semi-automatic failover of Serviceguard packages from one cluster to another following a cluster event that indicates serious disruption of service on one of the clusters. The product consists of a set of configuration, management commands, and a set of daemons that monitors and sends notification of cluster events. Continentalclusters version A.07.
Continentalclusters Version A.07.00 Release Notes What’s In This Version pre-integrated data replication solution a customer-selected data replication solution can be chosen by following the integration guidelines. • A recovery pair in a Continentalclusters consists of one primary cluster and one recovery cluster. One or more recovery pairs can be configured in a continental cluster with a common recovery cluster.
Continentalclusters Version A.07.00 Release Notes What’s In This Version NOTE The maintenance mode is an optional feature. To enable the maintenance mode, configure a shared disk (non-replicated) with a file system on all recovery clusters and the Continentalclusters configuration file must be specified using the CONTINENTAL_CLUSTER_STATE_DIR parameter.
Continentalclusters Version A.07.00 Release Notes What’s In This Version Support for Cluster File System and Cluster Volume Manager Recovery Continentalclusters environment now supports recovering applications running as Serviceguard packages that use Veritas Cluster File System (CFS) 4.1 or Veritas Cluster Volume Manager (CVM) 4.1 from Symantec for storage management.
Continentalclusters Version A.07.00 Release Notes What’s In This Version • If /etc/cmconcl/ccrac/ccrac.config file is configured, you must specify the CCRAC_CLUSTER parameter for every recovery pair in the ccrac.config file. If you do not specify this parameter, the recovery process does not complete and the following error message is displayed: Cluster name is not specified as a set.
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements Compatibility Information and Installation Requirements The same version of Continentalclusters and Serviceguard must be installed on all nodes in all the clusters of the configuration. To use Continentalclusters, the following hardware and software must be installed and configured on all nodes.
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements Software Requirements There are both HP software and disk array management software requirements. HP Software Requirements • Serviceguard version A.11.17 or A.11.18 For HP-UX 11i v3, Serviceguard version A.11.17.01 or later. • Serviceguard Extension for RAC version A.11.17 or A.11.18 for configuring Oracle RAC in Continentalclusters.
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements For the Bastille security setup requirements all Serviceguard mandatory HP-UX IP filter rules apply. In addition, the rules for remote command execution and cluster object manager (COM) must include all participating Continentalcluster nodes for as designated in the section on “Remote Failover” of Chapter 8 (Using HP-UX IPFilter with Serviceguard user’s guide).
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements Upgrading from Earlier Versions... If upgrading Continentalclusters from an earlier version, the following steps are required: 1. Halt the ccmon package: # cmhaltpkg ccmonpkg 2. Delete the old Continentalclusters configuration: # cmdeleteconcl 3. Install to a new version of Continentalclusters. 4.
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements Compatibility Issues Configuration with a metropolitan cluster as the primary cluster is supported in the cascading failover configuration using Metrocluster with EMC SRDF and Continuous Access XP. For information on configuration and setup, refer to the Cascading Failover in a Continental Cluster white paper on www.docs.hp.com -> High Availability -> Continentalclusters.
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements If you are using the EVA disk array with Continuous Access EVA for data replication, refer to the following: • HP StorageWorks Continuous Access and Data Replication Manager SAN Extensions Reference Guide • HP StorageWorks Continuous Access EVA Replication Performance Estimator V3.0 Application Notes. • HP StorageWorks Continuous Access EVA User Interface V1.2 Installation Guide Addendum.
Continentalclusters Version A.07.00 Release Notes Compatibility Information and Installation Requirements Further Reading Additional information about Continentalclusters and related high availability topics may be found on Hewlett-Packard’s HA web page. Support information, including current information on patches and known problems, is available from Hewlett-Packard IT center: http://itrc.hp.
Continentalclusters Version A.07.00 Release Notes Patches and Fixes in this Version Patches and Fixes in this Version There are no patches required for Continentalclusters version A.07.00 at the time of publication. However, this is subject to change without notice. For the most current information, contact your HP support representative or Hewlett Packard IT Resource Center.
Continentalclusters Version A.07.00 Release Notes Patches and Fixes in this Version Fixes There are no known fixes at the time of this publication. However, this is subject to change without notice. For the most current information contact your HP support representative.
Continentalclusters Version A.07.00 Release Notes Known Problems and Workarounds Known Problems and Workarounds The following describes known problems with the Continentalclusters version A.07.00 and workarounds for them. This is subject to change without notice. For the most current information contact your HP support representative. More recent information on known problems and workarounds may be available on the Hewlett Packard IT Resource Center: http://itrc.hp.
Continentalclusters Version A.07.00 Release Notes Known Problems and Workarounds Persistent “cmomd” Processes • What is the problem? If the node where the monitor process (cmclsentryd) is running goes down and then comes back up (as in a power failure), the cmomd process will remain on one or more nodes in the cluster that is being monitored. In these circumstances, the cmomd process will continue on the system until terminated by a user.
Continentalclusters Version A.07.00 Release Notes Known Problems and Workarounds The default behavior of LVM is to retry access forever following a failure. There are a number of ways to recover from this application hang problem: — Reboot the node. The package will then move to another node in the cluster. — Fix the problem so that one or more PV Links is restored. The application will then continue normally. — It is also possible to change the default LVM behavior so that it will not retry forever.
Continentalclusters Version A.07.00 Release Notes Software Availability in Native Languages Software Availability in Native Languages Continentalclusters and manuals are not available in native language versions.
Continentalclusters Version A.07.
