HP Serviceguard Version A.11.
Legal Notices © Copyright 1998-2011 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.
Contents Publishing History..........................................................................................6 1 Serviceguard Version A.11.20 Release Notes..................................................7 Announcements........................................................................................................................7 Platform Dependencies.........................................................................................................7 April 2011 Patches................
What You Can Do....................................................................................................18 Cluster-wide Device Special Files (cDSFs)..........................................................................18 Points To Note..........................................................................................................19 Where cDSFs Reside.................................................................................................
Installing Serviceguard.......................................................................................................41 If You Need To Disable identd.............................................................................................43 Upgrading from an Earlier Serviceguard Release...................................................................43 Upgrade Using DRD......................................................................................................
Publishing History Table 1 Publishing History Printing Date Part Number Edition April 2011 5900–1493 First Edition This new edition provides information on Serviceguard A.11.20 April 2011 patches that add new features to it, as well as features first added in A.11.20 and in patches to A.11.19.
1 Serviceguard Version A.11.20 Release Notes Announcements This section announces the most important features and limitations of Serviceguard A.11.20. For more information, see “What’s in this Release” (page 13). NOTE: These Release Notes also include information about features first introduced in A.11.19 patches; see “Features First Introduced in Serviceguard A.11.19 Patches” (page 29). Platform Dependencies IMPORTANT: This new version of Serviceguard is supported on 11i v3 only.
Serviceguard Optional Products Not Bundled The following optional product is not bundled with Serviceguard, but is delivered free with Serviceguard on the Serviceguard Distributed Components CD, and can also be downloaded from http://www.hp.com/go/softwaredepot/ha: • Quorum Server, and the Quorum Server Version A.04.00 Release Notes. Serviceguard A.11.19 Is the Required Basis for Rolling Upgrades A.11.
Upgrade will trigger a cluster membership transition from the old to the new cluster manager when the last node in the cluster has rolled to A.11.19. This transition can take up to one second, during which time the old cluster manager will shut down and the new cluster manager will start. CAUTION: From the time when the old cluster manager is shut down until the new cluster manager forms its first cluster, a node failure will cause the entire cluster to fail.
2011 patches. See “Support for HP Integrity Virtual Machines (HPVM)” (page 33) for more information about HPVM. See also “About cmappmgr” (page 31). ipnodes Entries Needed in /etc/nsswitch.conf Beginning with version A.11.19, Serviceguard uses calls that require ipnodes entries to be configured in the /etc/nsswitch.conf. See “Safeguarding against Loss of Name Resolution Services” in Chapter 5 of Managing Serviceguard for more information. Legacy Packages As of Serviceguard A.11.
To provide the required redundancy for both networking and mass storage connectivity on servers with fewer than three I/O slots, you may need to use multifunction I/O cards that contain both networking and mass storage ports. Token Ring and FDDI Obsolete Serviceguard A.11.20 does not support Token Ring and FDDI technologies for the cluster heartbeat and data networks (Serviceguard A.11.17 on HP-UX 11i v2 and A.11.16 on HP-UX 11i v1 were the last versions that did).
High Availability Consulting Services Because Serviceguard configurations can be complex to configure and maintain, HP strongly recommends that you use its high availability consulting services to ensure a smooth installation and rollout; contact your HP representative for more information. You should also work with your HP representative to ensure that you have the latest firmware revisions for disk drives, disk controllers, LAN controllers, and other hardware.
IMPORTANT: If your storage devices are configured with only a single path, or you have disabled multipathing, you should disable PCI Error Recovery; otherwise Serviceguard may not detect when connectivity is lost and cause a failover. For instructions on using the pci_eh_enable parameter to disable PCI Error Recovery, see the “Tunable Kernel Parameters” section of the latest edition of the PCI Error Recovery Product Note which you can find at http://www.hp.
• A new type of device file allows you to deploy a set of persistent device special files that is consistent across the cluster, eliminating to risk of name-space collisions amongst the cluster nodes. These new device special files are called cluster device special files or cDSFs. See “Cluster-wide Device Special Files (cDSFs)” (page 18).
• Serviceguard supports LVM 2.x volume groups, both for data and the cluster lock. See “About LVM 2.x” (page 30). • Serviceguard now supports cell OL* (online addition and deletion of cells) on HP Integrity servers that support them). For more information about using Serviceguard with partitioned systems, see the white paper HP Serviceguard Cluster Configuration for HP-UX 11i or Linux Partitioned Systems at http:// www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard.
Using the modular style of packaging provides flexibility and can be managed better compared to the legacy style of packaging, and is the highly recommended approach to create CFS packages. NOTE: For this feature to be enabled, both patches, Serviceguard A.11.20 patch (PHSS_41628) and Serviceguard CFS A.11.20 patch (PHSS_41674) must be installed.
GUI (or some combination of these two methods). As of Serviceguard A.11.20, there is a third option, called Easy Deployment. The Easy Deployment tool consists of three commands: cmpreparecl (1m), cmdeploycl (1m), and cmpreparestg (1m). In addition, there is a new -N option to cmquerycl, which you can use to obtain networking information for the cluster heartbeat. These commands allow you to get a cluster up and running in the minimum amount of time.
• Does not support asymmetric network configurations (in which a given subnet is configured only on a subset of nodes). • When cmdeploycl (1m) is used on a cluster where SGeRAC is installed, cmdeploycl (1m) provides a warning if the cluster being deployed does not meet SGeRAC specific requirements. For more information and instructions, see “Using Easy Deployment” in chapter 5 of Managing Serviceguard.
Because DSF names may be duplicated between one host and another, it is possible for different storage devices to have the same name on different nodes in a cluster, and for the same piece of storage to be addressed by different names. Serviceguard A.11.20 September 2010 patch (PHSS_41225) and later supports Cluster-wide device files (cDSFs), which ensure that each storage device used by the cluster has a unique device file name. cDSFs are available on HP-UX as of the September 2010 Fusion Release.
• vgimport –C causes vgimport (1m) to use cDSFs • vgscan –C causes vgscan (1m) to display cDSFs See the manpages for more information. The following new HP-UX commands handle cDSFs specifically: • vgcdsf(1m) converts all persistent DSFs in a volume group to cDSFs. Legacy DSFs in the volume group will not be converted, but you can use the HP-UX vgdsf script to convert these legacy DSFs to persistent DSFs if you need to.
NOTE: • All of the checks below are performed when you run cmcheckconf (1m) without any arguments (or with only -v, with or without -k or -K). cmcheckconf (1m) validates the current cluster and package configuration, including external scripts and pre-scripts for modular packages, and runs cmcompare (1m) to check file consistency across nodes. (This new version of the command also performs all of the checks that were done in previous releases.) • These new checks are not done for legacy packages.
• Kernel parameters and driver configurations consistent across nodes • Mount point overlaps (such that one file system is obscured when another is mounted) • Unreachable DNS server • Consistency of settings in .rhosts and /var/admin/inetd.
• Only NFS client-side locks (local locks) are supported. Server-side locks are not supported. • Because exclusive activation is not available for NFS-imported file systems, you should take the following precautions to ensure that data is not accidentally overwritten. ◦ The server should be configured so that only the cluster nodes have access to the file system. ◦ The NFS file system used by a package must not be imported by any other system, including other nodes in the cluster.
NOTE: The addition of the fs_server package parameter alters the output of cmviewcl -f line; this in turn may affect your programs and scripts that parse cmviewcl -f line output.
NOTE: DSAU does not support a local log consolidation server in a cross-subnet cluster. Instead, you can setup a remote log consolidation server on the Quorum Server node or cluster. Native Language Support HP Serviceguard Manager Version B.03.
New Features HP Serviceguard Manager version B.03.10 supports Serviceguard A.11.20 on HP-UX 11i v3. The following are new capabilities in B.03.10: • • Support for Site-aware Metrocluster Configuration (Site Aware Cluster + Site Controller package) ◦ Support for configuration of sites to form a site-aware Cluster. ◦ Support for Site Controller Package configuration. ◦ Support for moving the Site Controller package within site and across site.
• Cluster Verification for Metrocluster ◦ • Metrocluster Easy Deployment (SiteAware + NonSiteAware) ◦ • An enhancement to the existing cluster verification feature for Metrocluster specific checks. If the appropriate Metrocluster, SMS, and SGeRAC bundles are found to be installed, you will be given options for configuring a site aware Metrocluster with minimal steps.
Internet Explorer 7 Zooming Problem Internet Explorer 7 introduced a "zoom" feature which allows the user to zoom in/out the page being viewed. However, its implementation is known to have problems. HTML elements in a page are not zoomed proportionally. As a result, the resulting page is displayed in a unpredictable manner. Internet Explorer 8 fixed most of these problems and behaves in the same way as Firefox 3.x.
Launching Serviceguard Manager See Appendix I of Managing Serviceguard, at the address listed under “Documents for This Version” (page 34), for instructions on launching Serviceguard Manager, and other useful information. Patches and Fixes No patches are required for Serviceguard Manager B.03.10. For information about known problems and workarounds, see “Known Problems for Serviceguard Manager” (page 54). Features Introduced Before A.11.
Features First Introduced Before Serviceguard A.11.19 About olrad You must remove a LAN or VLAN interface from the cluster configuration before removing it from the system. You can do this without bringing down the cluster. HP-UX 11i v3 provides a new option for the olrad command, olrad -C, to help you determine whether or not an interface is part of the cluster configuration: run olrad -C with the affected I/O slot ID as argument.
with LVM version B.11.31.0809 and Serviceguard A.11.19 or later. (This support was first introduced in a patch to Serviceguard A.11.18.) NOTE: You are not required to move to LVM 2.x volume groups and everything will work as before if you do nothing. If you do use LVM 2.
About Device Special Files (DSFs) HP-UX releases up to and including 11i v2 use a naming convention for device files that encodes their hardware path. For example, a device file named /dev/dsk/c3t15d0 would indicate SCSI controller instance 3, SCSI target 15, and SCSI LUN 0. HP-UX 11i v3 introduces a new nomenclature for device files, known as agile addressing (sometimes also called persistent LUN binding).
Support for HP Integrity Virtual Machines (HPVM) Serviceguard supports HP Integrity Virtual Machines (HPVM). HPVM runs only on HP Integrity systems; it does not run on HP 9000 systems. IMPORTANT: For the most up-to-date compatibility information, see the Serviceguard/SGeRAC/SMS/Serviceguard Mgr Plug-in Compatibility and Feature Matrix, at http://www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard, under the heading General reference.
Considerations when Upgrading Serviceguard • .rhosts If you relied on .rhosts for access in the previous version of the cluster, you must now configure Access Control Policies for the cluster users. For instructions on how to proceed, see the subsection “Allowing Root Access to an Unconfigured Node” under “Configuring Root-Level Access” in Chapter 5 of the Managing Serviceguard manual.
Administration Utilities User’s Guide at http://www.hp.com/go/hpux-core-docs: go to the HP-UX 11i v3 collection and scroll down to Getting started. For information about the Event Monitoring Service, see the following documents at http:// www.hp.
Mixed Hardware Architecture As of HP-UX 11i v2 Update 2 (0409) and Serviceguard A.11.16, Serviceguard supports mixed-hardware-architecture clusters, consisting of HP 9000 and Integrity servers. Mixed-hardware-architecture clusters support the same volume managers, at the same version level, as Serviceguard clusters in which the server hardware is of a single type.
NOTE: In all three cases, the discussion refers to mixing HP-UX versions 11i v2 and 11i v3. Unless explicitly stated otherwise, “version” in this subsection means HP-UX version, not Serviceguard version. • Homogeneous cluster refers to a cluster that is not being upgraded, and which has no need to include nodes running different major versions of HP-UX. See “HP Recommendation for Homogeneous Clusters” (page 37).
NOTE: You can apply Serviceguard patches without doing a rolling upgrade. Rules and Restrictions for Heterogeneous Clusters IMPORTANT: Serviceguard A.11.20 is supported only on HP–UX 11i v3, so all cluster nodes must be running 11i v3 before you can complete a rolling upgrade to A.11.20. In preparation for an upgrade to Serviceguard A.11.20, you may want to upgrade the nodes from 11i v2 to 11i v3 over time. The rules that follow provide guidance. A Serviceguard A.11.
release at the same patch level, and the 11i v3 nodes should all be running the same 11i v3 Fusion release at the same patch level. Keep in mind that Serviceguard A.11.20 is supported only on HP-UX 11i v3. • All nodes should be at the same Serviceguard patch level. CAUTION: If you introduce a node running a lower patch level than that of the existing nodes, any new functionality introduced in the higher-level patch will cease to be available until that higher-level patch is installed on all nodes.
For information on how to configure HP-UX Bastille Sec10Host to allow the identd daemon to run, see the latest version of the Security Management volume of the HP-UX System Administrator's Guide under http://www.hp.com/go/hpux-core-docs. See also the HP-UX Bastille User’s Guide installed on your system: /opt/sec_mgmt/bastille/ docs/user_guide.txt. Before Installing Serviceguard A.11.20 Before you install Serviceguard A.11.20, you need to make sure that your cluster has the correct hardware upgrades.
is disabled (in inetd.conf), the network probing may be slower and under some conditions error messages may be written to syslog. Serviceguard also uses dynamic ports (typically in the range of 49152 - 65535) for some cluster services. If you have adjusted the dynamic port range using ndd (1M) - network tuning, alter your rules accordingly.
CAUTION: • This release of Serviceguard requires 11i v3. If you are already running earlier versions of Serviceguard and HP-UX, see “Upgrading from an Earlier Serviceguard Release” (page 43) for more information. • If you intend to use an alternate Quorum Server subnet “About the Alternate Quorum Server Subnet” (page 30), and the new cluster will use an existing Quorum Server, make sure you are running Quorum Server version A.04.00.
NOTE: There are files in CM-CORE that are reserved for HP support. Do not change these files. Do not move, alter, or delete the following: • /usr/contrib/bin/cmcorefr • /usr/contrib/bin/cmdumpfr • /usr/contrib/bin/cmfmtfr • /usr/contrib/Q4/lib/q4lib/cmfr.pl • /var/adm/cmcluster/frdump.cmcld.x (where x is a digit) NOTE: If you did a swremove of an older version of Serviceguard before the swinstall, a zero-length binary configuration file (/etc/cmcluster/cmclconfig) may be left on your system.
given under “Documents for This Version” (page 34); see also “Non-Rolling Upgrade Using DRD” (page 44). CAUTION: Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A.11.19; see “New Cluster Manager” (page 8). • If you are upgrading both the Quorum Server and Serviceguard, upgrade the Quorum Server before you upgrade Serviceguard. CAUTION: If you are using an alternate Quorum Server subnet (page 30), and you are not already running Quorum Server version A.04.
If, after reading and understanding the restrictions, you decide to perform a non-rolling upgrade using DRD, follow the instructions under “Performing a Non-Rolling Upgrade Using DRD” in Appendix D of the latest edition of Managing Serviceguard, which you can find at the address given under “Documents for This Version” (page 34). Restrictions for DRD Upgrades • DRD is available only on HP-UX 11i v3.
IMPORTANT: See the HP Serviceguard Storage Management Suite A.04.00 Release Notes and 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, so long as you are running 11i v3.
Requirements for Rolling Upgrade to A.11.20 To perform a rolling upgrade to Serviceguard A.11.20, you must be running: • HP-UX 11i v3 and • Serviceguard A.11.19 If you are not already running A.11.19, you may be able to do a rolling upgrade to A.11.19, and from A.11.19 to A.11.20. See the next two subsections. Requirements for Rolling Upgrade to A.11.19 IMPORTANT: Although you can upgrade to Serviceguard A.11.
Serviceguard for instructions in this case. See “About Device Special Files (DSFs)” (page 32) of these Release Notes for more information about agile addressing. Upgrading from an Earlier Release if You Are Not Using Rolling Upgrade (Non-Rolling Upgrade) If your cluster does not meet the requirements for a rolling upgrade, or you decide not to use rolling upgrade for some other reason, you must bring down the cluster (cmhaltcl) and then upgrade Serviceguard and HP-UX on the nodes.
Table 2 Patches (continued) Patch Number Description PHCO_39413 or later cumulative patch Patch to enable display of wwid and uniq_name properties in the output of ioscan (1m). This patch is recommended. PHSS_41628 Patch to enable the features introduced in HP Serviceguard A.11.20 on HP-UX 11i v3 listed under “New Features for A.11.20 April 2011 Patches” (page 13). PHSS_41674 Patch to enable the Modular CFS Package feature introduced in HP Serviceguard CFS A.11.
A.11.20 Defects Fixed in the April 2011 Patches • QXCR1001047727: Out or order messages and aborts after lan failures with SG 11.19 • QXCR1001046353: cmclconfd does not reset the hostname resolution family after deleting the cluster • QXCR1001020964: CrossSubnet:Not able to form the cluster with IPv6 address.
• QXCR1001007816: Serviceguard 11.20 cmcld abort on unexpected UDP message version • QXCR1001007347: Serviceguard 11.
Problems Fixed in this Version of the Serviceguard Manager Plug-in The following defects have been fixed in Version B.03.10 of Serviceguard Manager: • QXCR1001103488: SGManager displays wrong status of SGeRAC as configured • QXCR1001031495: DTS AR1009 FR: SG Mgr - Metrocluster configuration ease of use input • QXCR1001047635: Package goes into maintenance if there is any .
Known Problems This section lists problems in Serviceguard Version A.11.20 known at the time of publication. This list is subject to change without notice. More-recent information may be available from your HP support representative, or on the Hewlett-Packard IT Resource Center (ITRC): http://www.itrc.hp.com (Americas and Asia Pacific) or http://www.europe.itrc.hp.com (Europe). You can find details of each defect on the ITRC web site.
Known Problems for Serviceguard Manager The following problems in Serviceguard Manager B.03.10 were known at the time of publication. • QXCR1001119074: Some SGMgr labels and notes need to be localized • QXCR1001119063: In a site aware cluster, OC package per site is allowed ONLY when configured through package easy deployment. About Serviceguard Releases Types of Releases and Patches Versions of Serviceguard are provided as platform releases, feature releases, or patches.
Version Numbering Serviceguard releases employ a version numbering string that helps you identify the characteristics of the release. The version string has 4 parts: • Alphabetic Prefix • First Numeric Field • Second Numeric Field • Third Numeric Field When a new release is issued, different portions of the version string are incremented to show a change from a previous version of the product.
