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.......................................................................
New Serviceguard Features Common to HP-UX 11i v2 and 11i v3.............................20 Serviceguard Features Available Only on HP-UX 11i v3..............................................22 What’s Not in this Release.............................................................................................23 New Features for Serviceguard A.11.19........................................................................23 New Kinds of Package Dependency.......................................................
About HPVM and Cluster Re-formation Time..................................................41 Access changes as of A.11.16....................................................................................42 Considerations when Upgrading Serviceguard.................................................42 Considerations when Installing Serviceguard...................................................43 What Documents are Available for This Version ..............................................................
About Serviceguard Releases.............................................................................................62 Types of Releases and Patches.......................................................................................62 Platform Release.......................................................................................................62 Feature Release.........................................................................................................62 Patch....................
List of Tables 1 1-1 1-2 Printing History............................................................................................................9 Accessing Serviceguard Manager...............................................................................30 .....................................................................................................................................
Printing History Table 1 Printing History Printing Date Part Number Edition March 2009 T1905-90000 First Edition This new edition provides information on Serviceguard A.11.19, 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). Platform Dependencies This new version of Serviceguard is supported on HP-UX 11i v2 and 11i v3.
improvements; see the discussion of MEMBER_TIMEOUT under “Cluster Configuration Parameters” in the latest version of Managing Serviceguard for more information. NOTE: Because of these built-in performance improvements, Serviceguard Extension for Faster Failover is no longer being offered as a separate product. There is also a one-time effect on upgrade to Serviceguard A.11.19.
Quorum Server Upgrade Required if You Are Using an Alternate Address If you are using an Alternate Quorum Server Subnet (page 37), 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 “About Serviceguard Manager” (page 26).
Root Access to an Unconfigured Node” in Chapter 5 of Managing Serviceguard for more information. cmviewconf Deprecated cmviewconf is deprecated as of Serviceguard A.11.19; this command will be obsolete in a future release. Use cmviewcl to obtain information about the cluster. See “Reviewing Cluster and Package Status” in Chapter 7 of Managing Serviceguard for more information.
Lock Disk” in Chapter 3 of Managing Serviceguard for more information about dual cluster locks. Parallel SCSI Not Supported for Lock LUN The lock LUN functionality does not support parallel SCSI; you must use Fibre Channel for a lock LUN. If you need to use parallel SCSI, use an LVM cluster lock disk, or a Quorum Server. For more information about the cluster lock, see “Cluster Lock” in Chapter 3 of the latest edition of Managing Serviceguard.
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.
Serviceguard A.11.16 on HP-UX 11i v1, note that the -T option is available for that configuration.) Check the man page for identd to determine whether the -T option is supported for the version of identd currently on your system. For more information, see: • • • The section “Ensuring that the Root User on Another Node Is Recognized” in Chapter 5 of the 16th edition of Managing Serviceguard at http://docs.hp.com -> High Availability -> Serviceguard The section “What’s In This Version” in the Sendmail 8.13.
NOTE: A file created with VxFS 5.0 cannot be opened by 4.1 or later versions. 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. This is often referred to as native multipathing.
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.
New Serviceguard Features Common to HP-UX 11i v2 and 11i v3 The following features are new for A.11.19: • • • • • • • • • • • • You can configure new types of dependencies between packages. See “New Kinds of Package Dependency” (page 23). You can configure package weights and node capacities, allowing you to control broadly which packages can run simultaneously on a given node. See “About Package Weights” (page 23).
• • A new cluster parameter, NETWORK_AUTO_FAILBACK, tells Serviceguard how to handle the recovery of the primary LAN interface after it has failed over to the standby interface because of a link level failure. See the description of this parameter under “Cluster Configuration Parameters” in Chapter 4 of Managing Serviceguard. A new parameter, CONFIGURED_IO_TIMEOUT_EXTENSION, must be set for extended-distance clusters using iFCP interconnects between sites.
Serviceguard Features Available Only on HP-UX 11i v3 Serviceguard support for the following HP-UX 11i v3 capabilities was first introduced in Serviceguard version A.11.17.01: • Serviceguard A.11.19 on HP-UX 11i v3 supports HP-UX agile addressing, sometimes also called persistent LUN binding, for device special files (DSFs). See “About Device Special Files (DSFs)” (page 39). • Serviceguard A.11.19 on HP-UX 11i v3 supports HP-UX native multipathing and load balancing.
Systems at http://docs.hp.com -> High Availability -> Serviceguard ->White Papers. • You can use the FSWeb utility to configure LVM volumes in a Serviceguard cluster (and SLVM volumes if the add-on product Serviceguard Extension for Real Application Cluster (SGeRAC) is installed). For more information about FSWeb, see the fsweb (1m) manpage. What’s Not in this Release • • • • RS232 is no longer supported for the cluster heartbeat.
the same time, but, if the large node fails, you want only the critical packages to run on the smaller system. Package weights allow you to configure Serviceguard to enforce this behavior. For more information, see “About Package Weights” in Chapter 4 of the latest version of Managing Serviceguard, and the white paper Using Serviceguard’s Node Capacity and Package Weight Feature, which you can find on docs.hp.com under High Availability —> Serviceguard —> White Papers. New Support for IPv6 Serviceguard A.
New Online Cluster Configuration Capabilities Serviceguard A.11.19 introduces new online cluster-management capabilities. The new capabilities include: • Changing the Quorum Server configuration • Changing the lock disk configuration • Changing the lock LUN configuration • Changing an interface from IPv4 to IPv6, or vice versa For a summary of what can be changed online, with instructions and caveats, see the section “Reconfiguring a Cluster” in Chapter 7 of the latest version of Managing Serviceguard.
IMPORTANT: The package must be down and disabled before you can place it in, or take it out, of partial-startup maintenance mode. For more information, see “Maintaining a Package: Partial-Startup Maintenance Mode” in Chapter 7 of Managing Serviceguard. Other Package Changes NOTE: For information about legacy and modular packages, see Chapter 6 of Managing Serviceguard. Serviceguard A.11.
tools. Serviceguard Manager allows you to monitor, administer and configure a Serviceguard A.11.19 cluster from any system with a supported web browser. Serviceguard Manager does not require additional software installation. Instead, using your browser, you log into an HP Systems Management Homepage (SMH) and access the HP Serviceguard Manager tool, as well as other system management tools.
— Identify whether nodes and packages are halted or failed — Identify package type (e.g.
— Graphical view replacing table view as default view for the package dependencies — Improved run package operation — Enhanced access to consolidated logs Limitations 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. Help Subsystem Use this section to help you become familiar with Serviceguard Manager.
— A user with HP SMH Administrator access has full cluster management capabilities. — A user with HP SMH Operator access can monitor the cluster and has restricted cluster management capabilities as defined by the user’s Serviceguard role-based access configuration. — A user with HP SMH User access does not have any cluster management capabilities. See the online help topic “About Security” for more information. • Have created the security “bootstrap” file cmclnodelist.
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 61).
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.18 Patches NOTE: For information about legacy and modular packages, see Chapter 6 of Managing Serviceguard. Features first introduced in a patch to 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.
Restrictions The following restrictions apply: • • • • • • All nodes in the cluster must belong to the same network domain (that is, the domain portion of the fully-qualified domain name must be the same). The nodes must be fully connected at the IP level. A minimum of two heartbeat paths must be configured for each cluster node. There must be less than 200 milliseconds of latency in the heartbeat network.
For More Information For more information on the details of configuring the cluster and packages in a cross-subnet context, see the following sections in the 15th edition of Managing Serviceguard, at http://docs.hp.com -> High Availability -> Serviceguard: “Obtaining Cross-Subnet Information” in Chapter 5, “About Cross-Subnet Failover” in Chapter 4, and (for legacy packages only) “Configuring Cross-Subnet Failover” in Chapter 7.
[-O, --log-file ] [-D, --log-level <1-7>] [-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.
/usr/sbin/cmvxserviced -t 10 /dev/vx/dsk/cvm_dg2/lvol3 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 Veritas VxVM, CVM and CFS 5.0 from Symantec, on both HP-UX 11i v2 and 11i v3, with the following exception: • Serviceguard supports a maximum of eight nodes for CVM and CFS per site, up to a maximum of sixteen nodes across two sites.
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). IMPORTANT: Serviceguard A.11.19 supports only version 3.5, 4.0, or 4.1 of HPVM. See the Serviceguard/SGeRAC/SMS/Serviceguard Mgr Plug-in Compatibility and Feature Matrix, on docs.hp.
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.
to the Network and Systems Management collection and choose System Administration. For information about the Event Monitoring Service, see the following documents at http://www.docs.hp.
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). Versions with the same part number are differentiated by the publication date.
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 46).
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 47).
• 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 is not 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 47)).
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 37), 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.
• • 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. IMPORTANT: If you are upgrading from A.11.16 on HP-UX 11i v2 , you must first install patch PHSS_31072 or a later patch. See also the requirements listed above under “Upgrading from an Earlier Serviceguard Release” (page 55), and the Rolling Upgrade Exceptions that follow.
You can perform a non-rolling upgrade (that is, an upgrade performed while the cluster is down) from any supported HP-UX/Serviceguard release to any supported HP-UX/Serviceguard release. See the support matrix at docs.hp.com -> High Availability -> Support Matrixes. Uninstalling Serviceguard To uninstall the Serviceguard software, run the SD-UX swremove command. Before removing software, note the following: 1. 2. 3.
NOTE: One quick way to see which patches that have been applied to your system is a command such as the following: swlist -l patch | grep applied | more For complete information, see the section “Which Patches Are on a System?” in the Patch Management User Guide for 11.x Systems, at http://docs.hp.com: choose 11i v2 or 11i v3 under Operating Environments and then choose Patch Management. Table 1-2 Patch Number Description PHNE_35894 Patch to enable online replacement of LAN cards on HP-UX 11i v3.
NOTE: Serviceguard A.11.19 also includes all fixes already included in patches to earlier Serviceguard versions; these fixes are not necessarily documented here. You can find more information about these defects at ITRC.hp.com. Proceed as follows. 1. 2. 3. 4. Log in to ITRC.hp.com Choose >> Search knowledge base in the left frame Enter the defect number beginning QXCR as the search string (for example QXCR1000472750), or the number beginning JAG if there is no QXCR number.
• • • • • • • • • • • • • • • • • • • QXCR1000749924 dependent packages started on wrong nodes QXCR1000753242 Serviceguard 11.
• • JAGag32353: With Mozilla or Firefox browser, configuring a SGeRAC package is confusing JAGag35535: Adding a node to a cluster with lock LUN fails Known Problems and Workarounds This section lists problems in Serviceguard Version A.11.19 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.
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.
Supported Releases For information about the support life of a given release and its compatibility with versions of related products, see the Serviceguard Compatibility and Feature Matrix, on docs.hp.com -> High Availability, under the heading Serviceguard -> Support Matrixes. Version Numbering Serviceguard releases employ a version numbering string that helps you identify the characteristics of the release.
