Serviceguard Extension for RAC Version A.11.
Legal Notices © Copyright 2010 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.
Announcements SGeRAC (formerly known as Serviceguard OPS Edition or MC/LockManager) is a specialized facility that provides the framework for using Oracle Real Application Cluster (RAC) software on HP 9000 and HP Integrity servers. This section announces the most important features and limitations of Serviceguard Extension for RAC (SGeRAC) A.11.19. For more information, see “What’s in this Version” on page 7. SGeRAC Version and Components: Product Numbers The following SGeRAC version A.11.
• Serviceguard version A.11.19 must be installed as a prerequisite product for SGeRAC version A.11.19. Or, if the correct version of Serviceguard is not installed on the system, but present on the media from which SGeRAC is going to be installed, Serviceguard will be selected for the installation as well. (See the latest version of the Serviceguard Version A.11.19 Release Notes at the address given above for more information about Serviceguard.) • Version A.11.
For information about capabilities available only on HP-UX 11i v3, see “Announcements for HP-UX 11i v3” on page 5 . Hardware Dependencies Oracle 11gR2 is supported only on HP Integrity servers running HP-UX 11i v3. Serviceguard Features not yet Supported Serviceguard cross-subnet configurations are currently not supported with SGeRAC outside of Site Aware Disaster Tolerant Architecture (SADTA).
This means that you are not required to migrate to agile addressing when you upgrade to 11i v3, though you should seriously consider its advantages (see the white paper The Next Generation Mass Storage Stack at http://www.hp.com/go/hpux-core-docs —> HP-UX 11i v3 —> white papers). Migration involves modifying system and application configuration files and scripts to use persistent device files and in some cases new commands and options.
For more information about mult-ipathing in HP-UX 11i v3, see the white paper HP-UX 11i v3 Native Multi-Pathing for Mass Storage, and the HP-UX System Administrator's Guide: Logical Volume Management HP-UX 11i Version 3 at http://www.hp.com/go/hpux-core-docs —> HP-UX 11i v3. What’s in this Version • “Support for Oracle 11gR2 RAC with SLVM and ASM” on page 10 NOTE: Oracle 11gR2 is supported ONLY on HP Integrity servers with HP-UX 11i v3.
• Support for a maximum of four nodes over distances up to 100 kilometers in an extended-distance cluster with CFS/CVM 5.0 or 5.0.1 and LVM 2.1. The previous maximum in this configuration was two nodes. • Hostnames for SGeRAC cluster nodes can be up to 39 characters (bytes) long. (The former limit was 31 characters). NOTE: The SLVM subsystem on HP-UX 11i v2 only supports hostnames up to 31 characters long in an SGeRAC configuration.
NOTE: MORE is available only for LVM Version 2.1 volume groups. For earlier versions, you can still use the Single-Node Online Reconfiguration (SNOR) method. This method works on all LVM versions and requires the deactivation of the volume group on all but one node in a cluster. For more information, see the white paper SLVM Online Volume Reconfiguration at http://www.hp.com/go/ hpux-core-docs —> HP-UX 11i v3 —> white papers.
For the most up-to-date compatibility information, see the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature Matrix at http://www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard —> General reference. NOTE: Single-instance Oracle is not supported with CFS for RAC if instance startup and shutdown is outside of Serviceguard package control.
Support for the SGeRAC Toolkit The SGeRAC Toolkit provides documentation and scripts to simplify the integration of SGeRAC and the Oracle 10gR2/11gR1/11gR2 RAC stack. It also manages the dependency between Oracle Clusterware and Oracle RAC instances with a full range of storage management options (CFS, SLVM, CVM, ASM over SLVM). • The README file that accompanies the SGeRAC Toolkit, which will be on your system after the installation as /opt/cmcluster/SGeRAC/toolkit/README.
You can obtain the DRD software free from software.hp.com—search for DynRootDisk. For more information, go http://www.hp.com/go/hpux-core-docs —> HP-UX 11i v3. (You can also reach the information library from www.hp.com/go/drd, or go to www.hp.com and search for Dynamic Root Disk Information Library). IMPORTANT: Use the clone disk only on the system on which it was created. At present, Serviceguard does not support booting from a clone disk made on another system (sometimes referred to as DRD re-hosting).
• As of the date of these release notes, DRD upgrade is supported for clusters that use the LVM or VxVM volume manager. IMPORTANT: See the HP Serviceguard Storage Management Suite A.03.00 Release Notes for information about DRD upgrades in CVM/CFS environments. • Use the DRD software released with the September 2009 release of HP-UX 11i v3 or later. You do not have to upgrade the operating system itself to the September 2009 release, so long as you are running 11i v3.
• Enterprise Cluster Master Toolkit Version B.05.00 Release Notes at www.hp.com/go/hpuxserviceguard-docs —> HP Enterprise Cluster Master Toolkit —> Getting started. • HP Serviceguard Storage Management Suite Version A.02.01 for HP-UX 11i v2 Release Notes at http://www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard Storage Management Suite —> Getting started. • HP Serviceguard Storage Management Suite Version A.03.00 for HP-UX 11i v3 Release Notes at http://www.hp.
Installing Serviceguard Extension for RAC To install Serviceguard Extension for RAC independently, follow these steps: 1. Install or upgrade to HP-UX 11i v2 or 11i v3 before loading Serviceguard Extension for RAC Version A.11.19. 2. Use the swinstall command to install SGeRAC, product number T1907BA. 3. Verify the installation. Use the following command to display a list of all installed components: # swlist -R T1907BA Serviceguard version A.11.
5. Restart the cluster. Performing a Rolling Upgrade Using DRD CAUTION: All the limitations listed in Appendix A of Using Serviceguard Extension for RAC also apply to a rolling upgrade with DRD. In addition, there are special conditions that apply to upgrading a system to Serviceguard A.11.19.
If you are upgrading from a qualifying A.11.18 version, make sure you have implemented the workaround for defect QXCR1000906197 as described under “Restrictions for DRD Upgrades” on page 12. • Make sure that you have downloaded the latest DRD software and are thoroughly familiar with the DRD documentation. See “Rolling Upgrade Using DRD” on page 12 for more information. • There are some restrictions on where the install depot can reside.
12. Verify that the applications are functioning properly. • If the applications do not function properly and this is not the last node to be upgraded, you can revert to the previous release on this node. This is called hot recovery, and it will allow you to keep the node up and running in the cluster while you upgrade the other nodes, though. You will still need to investigate and solve the problems on this node before the cluster upgrade can complete.
In addition, all the limitations for non-rolling upgrades listed in Appendix A of Using Serviceguard Extension for RAC also apply to non-rolling upgrades using DRD. You should also read the section on “Non-Rolling Software Upgrades” in that Appendix before you proceed. Steps for a Non-Rolling Upgrade Using DRD Use the following steps for a non-rolling software upgrade using DRD: 1. Create a clone root disk for each node. 2.
1. 2. Halt the cluster services on the node(s) to be removed. Edit the cluster ASCII file to remove the nodes from which you removed SGeRAC, and then re-apply the configuration. The cluster remains up and running. Issue the swremove command to remove the software. Offline Node Reconfiguration: 1. 2. 3. Halt the cluster and remove the node from the configuration.
To see the most up-to-date information on these items, log in to ITRC.hp.com -> Search Knowledge base, enter the QXCR number, and search against “Engineering notes, solutions, bug reports, FAQs.” Required and Recommended Patches The following are patches required or recommended for use with SGeRAC version A.11.19 on HP-UX 11i v2. This list is subject to change without notice. Contact your HP support representative for up-to-the-moment information.
To view details on these items: Login to ITRC.hp.com —> Search Knowledge base —> enter QXCR number and search against engineering notes, solutions, bug reports, FAQs. Table 2 SGeRAC A.11.19 Fixes QXCR Number QXCR Title QXCR1000816558 The configured nodes have to register cmgmsd version when cluster starts. If any of the node does not register, the failure message will be logged and try again to register.
Platform Release A platform release is a stable version of the product, which is the preferred environment for the majority of customers. Platform releases may also contain new features. These releases are supported for an extended period of time, determined by HP. Patches will be made available within the extended support time frame even though a newer version of the product is available. Feature Release A feature release contains new product features.
