HP Serviceguard Version A.11.
Legal Notices © Copyright 1998-2009 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.
Table of Contents Printing History..............................................................................................................................9 1 Serviceguard Version A.11.19 Release Notes................................................................................11 Announcements..................................................................................................................11 Platform Dependencies.......................................................................
Features Introduced in A.11.19.....................................................................................20 Serviceguard on HP-UX 11i v3......................................................................................21 What’s Not in this Release.............................................................................................22 About the New Features...............................................................................................23 New Kinds of Package Dependency....
Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3................................................43 Features First Introduced Before Serviceguard A.11.18 ...............................................43 About Device Special Files (DSFs)...........................................................................43 Support for HP Integrity Virtual Machines (HPVM)..............................................45 About HPVM and Cluster Re-formation Time..................................................
QXCR1000575890: OLR of a LAN Card in SG cluster fails on HP-UX 11i v3...............64 Fixed in This Version..........................................................................................................64 Defects Fixed in A.11.19................................................................................................64 A.11.19 Defects Fixed in the July 2009 Patches.............................................................
List of Tables 1 1-1 1-2 Printing History............................................................................................................9 Accessing Serviceguard Manager...............................................................................34 Patches.........................................................................................................................
Printing History Table 1 Printing History Printing Date Part Number Edition March 2009 T1905-90000 First Edition July 2009 T1905-90003 Second Edition This new edition provides information on Serviceguard A.11.19 and patches that add new features to it, as well as new features first added in patches to A.11.18.
1 Serviceguard Version A.11.19 Release Notes Announcements This section announces the most important features and limitations of Serviceguard A.11.19. For more information, see “What’s in this Release” (page 19). NOTE: These Release Notes also include information about features first introduced in A.11.18 patches; see “Features First Introduced in Serviceguard A.11.18 Patches” (page 35). Platform Dependencies This new version of Serviceguard is supported on HP-UX 11i v2 and 11i v3.
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. New Cluster Manager Serviceguard A.11.19 introduces a new cluster manager.
Quorum Server Upgrade Required if You Are Using an Alternate Address If you are using an Alternate Quorum Server Subnet (page 41), you must upgrade the Quorum Server to version A.04.00 before you upgrade the cluster to Serviceguard A.11.19. CAUTION: If you fail to do this, the upgraded cluster will be running without a cluster lock until you have upgraded the Quorum Server. Serviceguard Manager Available from the System Management Homepage (SMH) For details, see “Serviceguard Manager” (page 30).
Legacy Packages In A.11.19, you can still create new packages using the legacy method (the method used before Serviceguard A.11.18; see “Configuring a Legacy Package” in Chapter 7 of Managing Serviceguard). In some cases new capabilities provided in modular packages (those created by the method introduced in A.11.18) have been added to legacy packages as well. But after A.11.19, new features will be implemented only in modular packages.
RS232 Heartbeat Obsolete The current version of Serviceguard does not support RS232 for the cluster heartbeat (Serviceguard A.11.17 on HP-UX 11i v2 and A.11.16 on HP-UX 11i v1 were the last versions that did).
These characters are deprecated, meaning that you should not use them, even if you are not using the Quorum Server, because they will be illegal in a future Serviceguard release. Future releases will require the cluster name to: • Begin and end with an alphanumeric character • Otherwise use only alphanumeric characters, or dot (.
This can happen if the Serviceguard node being updated receives a Serviceguard probe request from another Serviceguard node on the subnet while the EMS product is being updated. During the EMS product update, the EMS libraries on which cmclconfd depends are removed and re-installed, leaving a very short period during which the system does not have an EMS library.
Announcements for HP-UX 11i v3 Serviceguard A.11.19 supports HP-UX 11i v3, which introduces important improvements, particularly in regard to the I/O subsystem. See the subsections that follow, and “What’s in this Release” (page 19). New Bundles Serviceguard A.11.19 is now available as a recommended product in the HP-UX 11i v3 HA-OE and DC-OE bundles. Native Multipathing, Veritas DMP, and Related Features in HP-UX 11i v3 The HP-UX 11i v3 I/O subsystem provides multipathing and load balancing by default.
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 in the High Availability collection on docs.hp.com.
• Improved support for nested mount points. Serviceguard now ensures that a package will never attempt to mount a nested directory concurrently with the parent, no matter what concurrent_mount_and_umount_operations is set to. (In earlier releases, this could happen if concurrent_mount_and_umount_operations was set to a value greater than 1.) • Support for the target port congestion control capability in HP-UX 11i v3.
• • • A new utility allows you to monitor applications running inside Virtual Machine (VM) guests. See “cmappmgr” (page 29). You can now configure a maximum of 300 packages in a cluster. The previous limit was 150. A quorum server can now support up to 150 clusters comprising up to 300 nodes. The previous limits were 50 clusters and 100 nodes. The new limits are supported in Quorum Server versions A.02.04 and later.
• There are new networking capabilities: — The HP-UX olrad -C command now identifies network interface cards (NICs) that are part of the Serviceguard cluster configuration. You can remove a NIC from the cluster configuration, and then from the system, without bringing down the cluster. See “About olrad” (page 42). — Serviceguard now also supports the LAN Monitor mode of APA.
• The cmviewcl command no longer supports the -r 11.09 option. -r 11.12 and -r 11.16 are still supported. See the cmviewcl (1m) manpage for details • Serviceguard no longer supports versions of Veritas products from Symantec earlier than 5.0. See “Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3” (page 43).
Package Weight Feature, which you can find at the address given under “Documents for This Version ” (page 47). New Support for IPv6 Serviceguard A.11.19 allows you to choose either the IPv4 or the IPv6 address family for any subnet configured into the cluster, including subnets that carry the cluster heartbeat, and those connected to a Quorum Server.
NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to ANY. See “Allowing Root Access to an Unconfigured Node” in Chapter 5 of Managing Serviceguard for more information. • If you use a Quorum Server, you must make sure that the Quorum Server hostname (and the alternate Quorum Server address specified by QS_ADDR, if any) resolve to IPv6 addresses. IMPORTANT: You must use Quorum Server version A.04.00 or later. See the latest Quorum Server release notes for more information; you can find them at docs.
Recommendation for IPv6-Only Mode If you decide to migrate the cluster to IPv6-only mode, you should plan to do so while the cluster is down. Rules and Restrictions for Mixed Mode • The hostname resolution file on each node (for example, /etc/hosts) must contain entries for all the IPv4 and IPv6 addresses used throughout the cluster, including all STATIONARY_IP and HEARTBEAT_IP addresses as well any private addresses.
a cluster template file, edit it to set the appropriate (IPv6) values for QS_HOST and QS_ADDR and set HOSTNAME_ADDRESS_FAMILY to ANY, and then use cmapplyconf to apply the configuration. See the latest version of the HP Serviceguard Quorum Server Version A.04.00 Release Notes on docs.hp.com —> High Availability —> Quorum Server for more information. IMPORTANT: Quorum Server Version A.04.00 is required if you are configuring a second Quorum Server address (QS_ADDR).
New Preview Capabilities Many variables affect package placement, including the availability of cluster nodes; the availability of networks and other resources on those nodes; failover and failback policies; and package weights, dependencies, and priorities, if you have configured them. You can preview the effect on packages of certain actions or events before they actually occur. Serviceguard A.11.
• You can perform maintenance on the running package. This is chiefly useful for making networking and EMS changes. • You can halt the package and start it again in partial start-up maintenance mode, in which you start up some modules, not others, and perform maintenance on the modules you have not started. This is useful for performing maintenance on package services, file systems, and volume groups.
For more information see the white paper Designing High Availability Solutions with HP Serviceguard and HP Integrity Virtual Machines, which you can find at the address given under “Documents for This Version ” (page 47). 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.
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.02.
• Configuration enhancements — Modular package configuration wizard — Enhanced package dependencies configuration — Improved cluster and package configuration validation — Tooltips for cluster and package configuration parameters — Cluster configuration wizard — Advanced cluster configuration options • Ease-of-use improvements: — Preview Administration operations (e.g.
Current Limitations of Serviceguard Manager You cannot configure a site-aware Metrocluster or Continentalcluster, but you can monitor and administer a site-aware Metrocluster, and monitor (but not administer) a Continentalcluster. In addition, Serviceguard Manager does not yet support the following Serviceguard capabilities, introduced in the July 2009 patch: • IPv6–only clusters (see “New Support for IPv6” (page 24)).
• The hpuxswTOMCAT product. hpuxswTOMCAT is installed by default with HP-UX. To check that it is on your system, use a command such as: swlist -l fileset | grep TOMCAT • • • • Version 2.2.7 (SysMgmtWeb A.2.2.7) or higher of SMH (System Management Homepage) for HP-UX 11i v2. A web browser (Internet Explorer 6.0 or higher or Firefox 2.0 or higher) with access to SMH. Version 2.2.9 (SysMgmtWeb A.2.2.9) or higher of SMH for HP-UX 11i v3.
TIP: To speed up the time it takes to launch a session of HP Serviceguard Manager, do the following from the command line: 1. Stop hpsmh /opt/hpsmh/bin/hpsmh stop 2. Edit the file /etc/rc.config.d/hpsmh. Set the value of START_TOMCAT to 1. For example: START_TOMCAT=1 3. Start hpsmhd. /opt/hpsmh/bin/hpsmh autostart Patches and Fixes No patches are required for Serviceguard Manager B.02.00. For information about known problems and workarounds, see “Known Problems for Serviceguard Manager” (page 67).
legacy packages.) Many, but not all, packages can be migrated in this way; for details, see the white paper Migrating Packages from Legacy to Modular Style at the address given under “Documents for This Version ” (page 47). NOTE: The cmmigratepkg command requires Perl version 5.8.3 or higher on the system on which you run the command. It should already be on the system as part of the HP-UX base product. Other Package Changes First Introduced in Serviceguard A.11.
• node joined the cluster, or was not run since the package was configured to run on the node; otherwise it is yes. A new parameter in the package configuration file, vxvm_dg_retry, allows you specify that a failed VxVM import should be retried; see “Package Modules and Parameters” in Chapter 6 of Managing Serviceguard. About Cross-Subnet Configurations New Serviceguard capabilities, first introduced in a patch to A.11.
• Each heartbeat subnet on each node must be physically routed separately to the heartbeat subnet on another node; that is, each heartbeat path must be physically separate: — The heartbeats must be statically routed; static route entries must be configured on each node to route the heartbeats through different paths. — Failure of a single router must not affect both heartbeats at the same time.
in Chapter 4, and (for legacy packages only) “Configuring Cross-Subnet Failover” in Chapter 7. See also the white paper Technical Considerations for Creating a Serviceguard Cluster that Spans Multiple IP Subnets, which you can find at the address below. This paper discusses and illustrates supported configurations, and also potential mis-configurations.
[-t, --poll-interval ] [...] A brief description of each parameter follows: -h or --help Displays the usage, as listed above, and exits. NOTE: Do not include the help or version parameters in your service command; this will result in immediate package failure at runtime. -v or --version Displays the monitor version and exits. -O or --log-file Specifies a file for logging (log messages are printed to the console by default). -D or --log-level Specifies the log level.
This command monitors a single volume at log level 0, with a polling interval of 10 seconds, and prints all log messages to the console.
Quorum Server Version A.04.00 Release Notes at http://docs.hp.com -> High Availability -> Quorum Server. IMPORTANT: As of Serviceguard A.11.19, this capability requires Quorum Server Version A.04.00. (It is also provided in a patch to Serviceguard A.11.18 with Quorum Server Version A.03.00, but Quorum Server Version A.03.00 does not support an alternate subnet with Serviceguard A.11.19.) See “Quorum Server Upgrade Required if You Are Using an Alternate Address” (page 13). About LVM 2.
Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3 Serviceguard A.11.19 supports versions 4.1 and 5.0 of Veritas VxVM from Symantec, and version 5.0 (only) of CVM and CFS, on both HP-UX 11i v2 and 11i v3. IMPORTANT: For the most up-to-date information about supported versions, check the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature Matrix, at the address given under “Compatibility Information and Installation Requirements” (page 49).
Agile addressing is the default on new 11i v3 installations, but the I/O subsystem still recognizes pre-11i v3 device files, which as of 11i v3 are referred to as legacy device files. Device files using the new nomenclature are called persistent device files, When you upgrade to HP-UX 11i v3, a set of new, persistent device files is created, but the existing, legacy device files are left intact and by default will continue to be used by HP-UX and Serviceguard.
— HP-UX 11i v3 Native Multi-Pathing for Mass Storage — LVM Migration from Legacy to Agile Naming Model HP-UX 11i v3 See also the HP-UX 11i v3 intro(7) manpage. Support for HP Integrity Virtual Machines (HPVM) As of A.11.16, Serviceguard supports HP Integrity Virtual Machines (HPVM). HPVM runs only on HP Integrity systems; it does not run on HP 9000 systems. IMPORTANT: Serviceguard A.11.19 supports only version 3.5, 4.0, or 4.1 of HPVM.
IMPORTANT: This additional timeout extension represents a net addition to the time it takes for the cluster to re-form. For example, if the cluster typically took 40 seconds to re-form before any VM nodes were added, it will take about 80 seconds when one or more VM nodes are members of the cluster, if all those nodes have a VM guest depot. If any VM node without a VM guest depot is a member of the cluster, it will take about 110 seconds.
After you complete the upgrade, use cmgetconf to create and save a copy of the new configuration. If you do a cmapplyconf, you want to be sure it applies the newly migrated Access Control Policies. Considerations when Installing Serviceguard When you install Serviceguard for the first time on a node, the node is not yet part of a cluster, and so there is no Access Control Policy.
For information about the Event Monitoring Service, see the following documents at http://www.docs.hp.com -> High Availability -> Event Monitoring Service and HA Monitors -> Installation and User’s Guide: • • Using the Event Monitoring Service Using High Availability Monitors The Event Monitoring Service (EMS) and the Event Monitoring Service (EMS) Developer’s Kit are available free from http://www.hp.com/go/softwaredepot -> High Availability. Other relevant HP-UX documentation posted at http://docs.hp.
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.docs.hp.com -> High Availability -> Serviceguard -> Support Matrixes.
NOTE: HP-UX version in this context means major release, such as 11i v2. It is acceptable to have a mix of different HP-UX Fusion releases for the same major revision (for example, 11i v2 September 2004 and 11i v2 September 2006), although it is generally best to have all nodes running the same Fusion release. A mix of HP-UX 11i v2 and 11i v3 nodes is also allowed, but entails some restrictions; see “Mixed HP-UX Operating-System Revisions” (page 50).
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 51).
• 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 install Serviceguard at a patch level lower than the one the cluster was running, any new features introduced in the higher-level patch will cease to be available; you will need to re-install the higher-level patch on all nodes before you can use its features again.
• • • The cluster must not be using Veritas CVM or CFS. 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 51)).
Bastille Compatibility To ensure compatibility between Serviceguard (and Serviceguard Manager) and Bastille, do the following, depending on your environment. The files (host.config, for example) are under /etc/opt/sec_mgmt/bastille/defaults/configs/. • If Bastille is started using Sec10Host (host.config) level lock down, change SecureInetd.deactivate_ident=Y to SecureInetd.deactivate_ident="N" If you are using the Serviceguard SNMP subagent, set MiscellaneousDaemons.
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, posted at http://docs.hp.com/-> Internet and Security Solutions -> IPFilter For information on how to configure HP-UX Bastille Sec10Host to allow the identd daemon to run, see the latest HP-UX 11i v3 Installation and Update Guide posted at http://docs.
• • • • hacl-probe 5303/udp hacl-local 5304/tcp hacl-test 5305/tcp hacl_poll 5315/tcp Serviceguard also uses port 9/udp discard during network probing setup when running configuration commands such as cmcheckconf or cmapplyconf and cmquerycl. If the port 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.
Installing Serviceguard Serviceguard will automatically be installed when you install the HP-UX Mission Critical Operating Environment (MCOE). To install Serviceguard independently, follow these broad steps: CAUTION: If you intend to use an Alternate Quorum Server Subnet (page 41), and the new cluster will use an existing Quorum Server, you must upgrade the Quorum Server to version A.04.00 before you proceed; see “Quorum Server Upgrade Required if You Are Using an Alternate Address” (page 13).
• • • • • • • • • Cluster-OM.CM-OM-COM Cluster-OM.CM-OM-MAN Package-CVM-CFS.CM-CVM-CFS Package-CVM-CFS.CM-CVM-CFS-COM Package-Manager.CM-PKG Package-Manager.CM-PKG-MAN Cluster-Monitor.CM-CORE Cluster-Monitor.CM-CORE-COM Cluster-Monitor.CM-CORE-MAN 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.
Upgrading from an Earlier Serviceguard Release • • • For information about supported Serviceguard upgrade paths, see the support matrix at docs.hp.com -> High Availability -> Support Matrixes. This release of Serviceguard requires HP-UX 11i v2 or 11i v3. For information about HP-UX upgrade paths, see the HP-UX Installation and Upgrade Guide for the target version of HP-UX at http://www.docs.hp.com -> -> Installing and Updating.
If, after reading and understanding the restrictions, you decide to perform a rolling upgrade using DRD, follow the instructions under “Performing a 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 47).
• “Guidelines for Rolling Upgrade” and “Guidelines for Non-Rolling Upgrade” in Appendix D of the latest edition of Managing Serviceguard. You must follow the instructions for DRD upgrades in Managing Serviceguard; see “Performing a Rolling Upgrade Using DRD” or “Performing a Non-Rolling Upgrade Using DRD” in Appendix D of the latest edition of that manual.
HP Serviceguard Storage Management Suite and standalone CVM product In many cases you cannot do a rolling upgrade if you are upgrading the HP Serviceguard Storage Management Suite. Specifically you cannot do a rolling upgrade if you are using the Veritas clustering capabilities — CVM and CFS. In the case of CVM, this applies whether you purchase it as part of a Storage Management bundle, or as a standalone product. For more information, see the Veritas 5.
1. 2. 3. Serviceguard must be halted (not running) on the node from which the swremove command is issued. The system from which the swremove command is issued must be removed from the cluster configuration. (If the node is not removed from the cluster configuration first, swremove will cause the current cluster to be deleted.) The swremove command should be issued from one system at a time.
QXCR1000575890: OLR of a LAN Card in SG cluster fails on HP-UX 11i v3 Problem: Online replacement (OLR) of a LAN card in a Serviceguard cluster fails on a system running HP-UX 11i v3 because the Critical Resource Analysis (CRA) performed as part of the OLR operation returns CRA_SYS_CRITICAL. You will encounter this problem on an unpatched HP-UX 11i v3 system whether you use the Peripheral Device Tool (pdweb) or the HP-UX olrad command. Workaround: Apply patch PHNE_35894.
• • • • • • • • • • • • • • • • • • • • • • • • QXCR1000578801 (JAGag31490): Modular package fails with the error: 'Unable to retrieve package attribute' QXCR1000579524 (JAGag32406) fr: 11.
• • • • • • • QXCR1000836610 cmgetconf and cmquerycl fail when VG's with names > 39 char exist on a SG node QXCR1000839798 Serviceguard rolling upgrade fails with convert errors when APA configured QXCR1000844258 cmdisklockd does not detect recovered lock disk QXCR1000846447 local lan failover to standby lan not initiated QXCR1000847502 cmcld logs Could not get ticks from system clock using times() QXCR1000869689 Cluster node fails to join the cluster due to cdb not synced QXCR1000873145 cmviewcl/cmviewcon
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. See “Fixed in This Version” (page 64) for instructions on looking up a defect.
of time, determined by HP. Patches will be made available within the extended support time frame even though a newer version of Serviceguard is available. Serviceguard A.11.19 is a platform release. NOTE: You are encouraged to move to the A.11.19 release. For compatibility information for this and earlier releases, see the Serviceguard Compatibility and Feature Matrix at http://www.docs.hp.com -> High Availability -> Serviceguard -> Support Matrixes.
• 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. 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 on docs.hp.com (http://www.docs.hp.com -> High Availability -> Serviceguard -> Release Notes).
