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 August 2011 Patches...............
Cluster-wide Device Special Files (cDSFs)..........................................................................19 Points To Note..........................................................................................................19 Where cDSFs Reside.................................................................................................19 Checking the Cluster Configuration and Components.........................................................20 Limitations.................................
If You Need To Disable identd.............................................................................................41 Upgrading from an Earlier Serviceguard Release...................................................................41 Upgrade Using DRD......................................................................................................42 Rolling Upgrade Using DRD.......................................................................................42 Non-Rolling Upgrade Using DRD.....
Publishing History Table 1 Publishing History Printing Date Part Number Edition August 2011 5900-1872 First Edition This new edition provides information on Serviceguard A.11.20 August 2011 patches that add new features to it, as well as features first added in A.11.20 and its subsequent patches, 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 27). Platform Dependencies IMPORTANT: This new version of Serviceguard is supported on 11i v3 only.
This product structure allows Serviceguard customers who subscribe to Update services to download Serviceguard from the web (along with the sub-products classed as Serviceguard components and listed above) via Software Update Manager (SUM). 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.
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.
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.20, new package features are being implemented only in modular packages (those created using the method introduced in A.11.18).
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). HP-UX 11i v3 does not support these two technologies.
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.
• New Serviceguard capabilities allow you allow you to check the soundness of the cluster configuration, and the health of its components, more thoroughly than you could in the past, and to do so at any time, rather than only when changing the configuration of the cluster or its packages. See “Checking the Cluster Configuration and Components” (page 20). • You can now you can use NFS-mounted (imported) file systems as shared storage in packages. See “NFS-mounted File Systems” (page 22).
• 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. • Serviceguard supports vgchange -T, which allows multi-threaded activation of volume groups. See “About vgchange -T” (page 28).
NOTE: Generic resources can also be configured in modular style CFS packages. To configure generic resources in Modular Style CFS packages, the Serviceguard CFS A.11.20 patch PHSS_42136 must be installed. Advantages of Generic Resources • Custom defined monitors can also be integrated. • Provides better control, options, and flexibility in terms of getting and setting the status of a resource.
improvement is directly dependent on the number of nodes on which the package needs to be halted; the performance benefit increases as the number of nodes increases. cmhaltpkg (1m) defaults to this behavior and the feature is automatically enabled once all the nodes in the cluster are upgraded to Serviceguard A.11.20 April 2011 patch (PHSS_41628) or later. Support for Veritas 5.
• Does not configure access control policies. • Does not install or configure firewall and related software. • Does not support cross-subnet configurations. • Does not configure packages. • Does not discover or configure a quorum server (but can deploy one that is already configured). • Does not support asymmetric network configurations (in which a given subnet is configured only on a subset of nodes).
For more information, including important rules and restrictions, see “Halting a Node or the Cluster while Keeping Packages Running” in chapter 7 of Managing Serviceguard. Cluster-wide Device Special Files (cDSFs) Under agile addressing on HP-UX 11i v3, each device has a unique identifier as seen from a given host; this identifier is reflected in the name of the Device Special File (DSF). See “About Device Special Files (DSFs)” (page 30) for more information.
• cDSFs do not support disk partitions. Such partitions can be addressed by a device file using the agile addressing scheme, but not by a cDSF. • cDSFs are not supported by Ignite-UX in a Serviceguard Cluster environment. Volume groups configured with a cDSF will not be archived using Ignite-UX recovery archive creation tools. For more information, see the latest Ignite-UX Frequently Asked Questions document at http:// www.hp.com/go/ignite-ux-docs.
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.
volumes managed by HP-UX Logical Volume Manager (LVM), because a physical volume failure is not always a critical failure that triggers failover (for example, the failure of a mirrored volume is not considered critical). For this reason, it can be very difficult to determine which physical disks must be monitored to ensure that a logical volume is functioning properly. The HP Serviceguard Volume Monitor provides a means for effective and persistent monitoring of storage volumes.
• Standard German • Standard Italian • Standard Spanish What You Can Do Depending on your SMH and Serviceguard security privileges, you can do the following: • Monitor, create, modify, run, and halt a cluster. • Monitor, run, and halt nodes. • Create and modify failover and multi-node packages, including configuring package dependencies. You can also modify Auto Run and Node Switching settings. • Monitor, run, halt, and move failover, multi-node, and system multi-node packages.
Browser and SMH Issues Pages Launched into New Window rather than Tabs with Firefox Tabbed Browsing By design, the Serviceguard Manager logging windows are launched with a pre-specified window size that will not obscure the original window when they are displayed. With the Firefox tabbed browsing preference selected, if a new window has a specified size, the tabbed browsing preference is ignored and the target page is launched in a new window instead.
• Version A.3.0.1, or a higher version of A.3.0., of SMH (System Management Homepage), for HP–UX 11i v3. • A web browser (Internet Explorer 6.0 or higher or Firefox 2.0 or higher) with access to SMH. • Have launched SMH (settings -> Security -> User Groups) to configure user roles for SMH. ◦ A user with HP SMH Administrator access has full cluster management capabilities.
• Support for Shared LVM (SLVM) in an HPVM environment only — that is, when the cluster includes virtual machines (either as nodes or within packages) that are managed by HPVM. For more information, see HP Integrity Virtual Machines Installation, Configuration, and Administration at http://www.hp.com/go/hpux-hpvm-docs. For more information about using HPVM in a Serviceguard cluster, see “Support for HP Integrity Virtual Machines (HPVM)” (page 31). • Improved support for nested mount points.
IMPORTANT: Make sure you read the configuration file comments for both concurrent_vgchange_operations and enable_threaded_vgchange before configuring these options, as well as the vgchange (1m) manpage. About the Alternate Quorum Server Subnet Serviceguard A.11.20 allows you to configure an alternate subnet for communication between the cluster nodes and the Quorum Server. You can do this from the command line or in Serviceguard Manager.
HPVM 4.1 Support for Windows 2008 Guests HPVM 4.1 supports Windows 2008 guests, and you can use cmappmgr to monitor processes on these guests. To enable this capability you need to do the following: • Install the HPVM 4.1 July patches. See the latest version of the HP Integrity Virtual Machines Version 4.1 Release Notes, which you can find on http://www.hp.com/go/hpux-hpvm-docs. • Install the Windows 2008 guest operating system on the host.
configuration files such as/etc/fstab and /etc/lvmtab will contain references to persistent device files, but Serviceguard’s functioning will not be affected by this. CAUTION: You cannot migrate to the agile addressing scheme during a rolling upgrade if you are using cluster lock disks as a tie-breaker, because that involves changing the cluster configuration. But you can migrate the cluster lock device file names to the new scheme without bringing the cluster down.
The additional time Serviceguard needs to wait depends in part on whether or not a VM guest depot is installed on the VM node. (See HP Integrity Virtual Machines Installation, Configuration, and Administration, at the address given below, for information on installing a guest depot.) Serviceguard uses information it derives from the VM guest depot to set the timeout to the optimal value.
Documents for This Version For information about the current version of Serviceguard, and about older versions, see the Serviceguard documents posted at http://www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard. The following documents, which can all be found at http://www.hp.com/go/ hpux-serviceguard-docs, are particularly useful. • Managing Serviceguard Twentieth Edition. This manual has been revised for the current A.11.20 August 2011 patches. • HP Serviceguard Quorum Server Version A.04.
http://www.hp.com/go/hpsc Compatibility Information and Installation Requirements Read this entire document (and any other Release Notes or READMEs for related products you may have) before you begin an installation. Compatibility For complete compatibility information see the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature Matrix posted at http://www.hp.com/go/hpux-serviceguard-docs. Mixed Clusters “Mixed cluster” has several meanings in the context of Serviceguard.
For more information about mixed-hardware-architecture clusters, see Configuration Rules for a Mixed HP 9000 /Integrity Serviceguard Cluster at http://www.hp.com/go/hpux-serviceguard-docs. Mixed HP-UX Operating-System Revisions A Serviceguard A.11.19 cluster can contain a mix of nodes running HP-UX 11i v2 and 11i v3, with certain restrictions. You may want to take advantage of this fact when preparing to upgrade the cluster to A.11.
It is also possible to upgrade the HP-UX version without upgrading Serviceguard, and so avoid the rolling upgrade restrictions. In this case you must make sure that: • The Serviceguard version bundled with the HP-UX Operating Environment (OE) matches the version already installed. CAUTION: You need to pay careful attention to the Serviceguard patch level as well as the Serviceguard version.
• If you are updating nodes from HP–UX 11i v2 to 11i v3, you must use update-ux; cold install is not supported in this context. • If you are updating nodes from HP–UX 11i v2 to 11i v3, and the Serviceguard version bundled with the HP-UX Operating Environment (OE) is later than the one already installed, rolling upgrade restrictions apply (see “Rules and Restrictions for Clusters in Transition” (page 35)).
pass in quick proto tcp from any to any port = 2301 pass in quick proto tcp from any to any port = 2381 pass in quick from to any pass out quick from any to In the above rules, are all nodes in the cluster, including the local node. The ipf.customrules file is located under the Bastille directory itself. IPFilter-Serviceguard rules are documented in the latest HP-UX IPFilter Administrator’s Guide, which you can find under http://www.hp.
• hacl-probe 5303/udp • hacl-local 5304/tcp • hacl-local 5304/udp • hacl-test 5305/tcp • hacl-dlm 5408/tcp Serviceguard also uses port identd 113/tcp for user verification and to authenticate Serviceguard commands. For more information about identd, see the white paper Securing Serviceguard at http:// www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard, and the identd (1M) manpage.
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 41) for more information. • If you intend to use an alternate Quorum Server subnet “About the Alternate Quorum Server Subnet” (page 29), 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 33); see also “Non-Rolling Upgrade Using DRD” (page 42). 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 29), 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 33). Restrictions for DRD Upgrades • DRD is available only on HP-UX 11i v3.
• Serviceguard does not support booting from a clone disk made on another system (sometimes referred to as DRD re-hosting). • The cluster must meet both general and release-specific requirements for a rolling or non-rolling upgrade; see the remainder of this section and the sections “Guidelines for Rolling Upgrade” and “Guidelines for Non-Rolling Upgrade” in Appendix D of the latest edition of Managing Serviceguard.
Requirements for Rolling Upgrade to A.11.19 IMPORTANT: Although you can upgrade to Serviceguard A.11.19 while still on HP-UX 11i v2, you must upgrade to HP-UX 11i v3 in order to upgrade to Serviceguard A.11.20. Rolling upgrade to Serviceguard A.11.19 is supported only if you are upgrading from: • Serviceguard A.11.15 or greater on HP Integrity systems running HP-UX 11i v2 or 11i v3; or • Serviceguard A.11.16 or greater on HP 9000 systems running HP-UX 11i v2 or 11i v3.
You can perform a non-rolling upgrade (that is, an upgrade performed while the cluster is down) from any HP-UX/Serviceguard release. Uninstalling Serviceguard To uninstall the Serviceguard software, run the SD-UX swremove command. Before removing software, note the following: 1. Serviceguard must be halted (not running) on the node from which the swremove command is issued. 2. The system from which the swremove command is issued must be removed from the cluster configuration.
Table 2 Patches (continued) Patch Number Description NOTE: This patch is needed only if SG Storage Management Suite A.03.01, A.04.00, or A.04.00.01 is installed on the node. To install this patch, PHSS_42137 must be installed.
• QXCR1001125497: When cmgetconf is run on a SGeSAP package, some of the package attributes configured for that package will be commented in the output • QXCR1001108352: Package IP addresses for MNPs should result in cmapplyconf failures • QXCR1001121630: IC363-cmcheckconf generated confusing output messages • QXCR1001109401: cmrunpkg and cmhaltpkg should handle duplicate entries in package ascii file • QXCR1001151026: cmnetd error message needs more comments or be suppressed • QXCR1001145485: cm
• QXCR1001011472: Modular packages are at risk of failure during online reconfiguration • QXCR1001009221: Serviceguard 11.19 cmproxyd reports cluster is not configured when it is • QXCR1001007814: port scan brings down cmcld • QXCR1001007803: SG 11.20 unlimited modular package service restarts is impossible online • QXCR1001007809: Nodes cannot be removed from cross subnet CFS cluster online • QXCR1001007816: Serviceguard 11.
• QXCR1000924001: cmfileassistd should not die after 1min of inactivity • QXCR1000924069: Serviceguard does not detect cluster lock recovery • QXCR1000924116: cmdisklock core dumps if the open fails on a locklun • QXCR1000923632: cmcld aborts after short hangs on one-node-cluster • QXCR1000923641: cmcld aborts after short hangs on one-node-cluster Additional fixes are listed in the patch form text, which is delivered with the patches.
Known Problems for Serviceguard • QXCR1001132671: cmcld dumps core: SEGV_ACCERR - Invalid Permissions for object • QXCR1001131688: cmappmgr error messages are not helpful for troubleshooting • QXCR1001074974: Assertion failed: In package reconfiguration code path • QXCR1001158391: Program terminates on PA boxes when cmdeleteconf core occurs • QXCR1001063125: SGWBEMProviders A.03.10.
About Serviceguard Releases Types of Releases and Patches Versions of Serviceguard are provided as platform releases, feature releases, or patches. Platform Release A platform release is a stable version of Serviceguard, which is the preferred environment for the majority of Serviceguard customers. Platform releases may also contain new Serviceguard features. These releases are supported for an extended period of time, determined by HP.
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. Release Notes Revisions Occasionally, important new information warrants revising the Release Notes after they have gone to press. In such cases HP updates the Release Notes at http://www.hp.com/go/ hpux-serviceguard-docs. Versions with the same part number are differentiated by the publication date.
