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.......................................................................
What’s in this Release.........................................................................................................19 New Features for October 2009 Patches........................................................................19 Features Introduced in A.11.19.....................................................................................21 Serviceguard on HP-UX 11i v3......................................................................................22 What’s Not in this Release.........
About vgchange -T..................................................................................................45 Alternate Quorum Server Subnet............................................................................45 About LVM 2.0.........................................................................................................46 About olrad..............................................................................................................
Upgrading from an Earlier Release if You Are Not Using Rolling Upgrade (Non-Rolling Upgrade).................................................................................................67 Uninstalling Serviceguard..................................................................................................68 Patches for this Version.......................................................................................................
List of Tables 1 1-1 1-2 Printing History............................................................................................................9 Accessing Serviceguard Manager...............................................................................38 Patches.........................................................................................................................
Printing History Table 1 Printing History Printing Date Part Number Edition March 2009 T1905-90000 First Edition July 2009 T1905-90003 Second Edition October 2009 T1905-90004 Third 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 39). 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 45), 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 32).
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 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).
Serviceguard Extension for Faster Failover Obsolete Performance improvements in the New Cluster Manager (page 12) make the Serviceguard Extension for Faster Failover (SGeFF) obsolete. If SGeFF is present, it will be removed from the system when you install Serviceguard A.11.19. 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).
Cluster Name Restrictions The following characters must not be used in the cluster name if you are using the Quorum Server: at-sign (@), equal-sign (=), or-sign (|), semicolon (;). 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 (.
Announcements for HP-UX 11i v2 Possible Problem when Upgrading from HP-UX 11i v1 to 11i v2 Under certain rare conditions the Serviceguard daemon /usr/lbin/cmclconfd could abort with a core dump during a system update from HP-UX 11i v1 to 11i v2 on a system on which EMS is installed. 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.
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.3 Release Notes. The identd (1M) manpage. 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.
are supported, but will be inactive unless you turn off native multipathing (in that case they will function as they did in previous releases of HP-UX). PCI Error Recovery PCI Error Recovery enables an HP-UX system to detect, isolate, and automatically recover from a PCI error.
• • Support for CFS, VxVM and CVM version 5.0.1 on HP-UX 11i v3 only. See “Support for Veritas 5.0 on HP-UX 11i v2 and 5.0/5.0.1 on 11i v3” (page 24) for more information. Improved support for IPv6, including support for IPv6–only hosts. See “New Support for IPv6” (page 26). • Improved support for online package maintenance. See “Package Maintenance Mode” (page 30). • Support for Dynamic Root Disk (DRD) on HP-UX 11i v3. See “Upgrade Using DRD” (page 63).
Features Introduced in A.11.19 The features being introduced in the October 2009 patches are listed in the previous subsection; see (page 19). The following features were introduced in the initial release of A.11.19: • • • • • • • • • • • • You can configure new types of dependencies between packages. See “New Kinds of Package Dependency” (page 25). You can configure package weights and node capacities, allowing you to control broadly which packages can run simultaneously on a given node.
See the section “Serviceguard Daemons” in Chapter 3 of the latest edition Managing Serviceguard for more information about these daemons. • • 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.
• • Serviceguard A.11.19 on HP-UX 11i v3 supports LVM 2.0 volume groups, both for data and the cluster lock. See “About LVM 2.0” (page 46). 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://docs.hp.com -> High Availability -> Serviceguard -> White Papers.
About the New Features The subsections that follow discuss the major new capabilities introduced in the initial A.11.19 release, as well as those that require the October 2009 patches. Information on using these capabilities is in the latest version of Managing Serviceguard, which you can find at the address given under “Documents for This Version ” (page 50). Support for Veritas 5.0 on HP-UX 11i v2 and 5.0/5.0.
NOTE: For more information about SMS support for version 5.0.1, including information about new capabilities, and patches that are required in addition to those listed under “October 2009 Patches” (page 11), see the HP Serviceguard Storage Management Suite A.03.00 Release Notes at the address given above. The HP Serviceguard Storage Management Suite Version A.03.
Dependencies”. See also the white paper Serviceguard’s Package Dependency Feature, which you can find at the address given under “Documents for This Version ” (page 50). Package Weights Package weights and node capacities allow you to restrict the number of packages that can run concurrently on a given node, or, alternatively, to limit the total package “weight” (in terms of resource consumption) that a node can bear.
• All addresses used by the cluster must be in each node's /etc/hosts file. In addition, the file must contain the following entry: ::1 localhost ipv6-localhost ipv6-loopback • • All addresses must be IPv6, apart from the node's IPv4 loopback address, which cannot be removed from /etc/hosts. The node's public LAN address (by which it is known to the outside world) must be the last address listed in /etc/hosts.
NOTE: CFS and CVM should not be installed on any system in an IPv6–only cluster, even if they are not configured. This also means that the Serviceguard component of bundles that include Serviceguard cannot be configured in IPv6 mode. • • HPVM is not supported in IPv6-only mode. You cannot configure a virtual machine either as a node or a package in an IPv6-only cluster. Serviceguard Manager does not yet support IPv6-only mode; see “Current Limitations of Serviceguard Manager” (page 36).
NOTE: • This also applies if HOSTNAME_ADDRESS_FAMILY is set to IPV6. HPVM is not supported. You cannot have a virtual machine that is either a node or a package if HOSTNAME_ADDRESS_FAMILY is set to ANY or IPV6. Restrictions if You Have Not Applied the July or later 2009 Patch A.11.19 without the patch supports only IPv4–only and mixed-mode clusters; you cannot configure an IPv6–only cluster.
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. New Online Package Configuration Capabilities Serviceguard A.11.19 allows you to perform most configuration changes to modular packages, and many changes to legacy packages, while the package is running.
CAUTION: No package can be in maintenance mode, whether it is running or not, when you perform an upgrade from Serviceguard A.11.19 to any later version, including an upgrade from the initial release of A.11.19 to the July or later 2009 patch. This means that: • You must make sure no packages are in maintenance mode when you start the upgrade. • You must not put any package in maintenance mode until all the nodes have been upgraded. Breaking this rule will leave the cluster in an inconsistent state.
cmappmgr cmappmgr is an utility that allows you launch and monitor processes on HP Virtual Machine (HPVM) guest nodes. For information about HPVM, See “Support for HP Integrity Virtual Machines (HPVM)” (page 48). cmappmgr is operating-system-independent, supporting HP-UX, Linux, and Windows VMs. cmappmgr on the host communicates via SSL connections with a lightweight module on the VM guest, cmappserver. cmappmgr exits when the process that is being monitored does.
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.
New Features HP Serviceguard Manager version B.02.00 supports Serviceguard A.11.19 on HP-UX 11i v2 and HP-UX 11i v3 (as well as Linux Red Hat RHEL 5.2 and SUSE SLES 10 and 11). The following are new capabilities in B.02.00: • Enhanced cluster monitoring: — Summarize package status iconically with drill-down to specific problem descriptions — Identify packages that cannot failover — Identify whether nodes and packages are halted or failed — Identify package type (e.g.
◦ ◦ ◦ HP Virtual Machines Manager (VM Manager) version A.03.50 or later must be installed on the VM host system. The VM Manager software must be installed on the VM Host node which hosts the VM guest nodes where VM Manager will be launched. To launch VM Manager on an HPVM guest, HPVM-Guest Bundle software must be installed on the guest node. Refer to HP Integrity Virtual Machines Installation, Configuration, and Administration on docs.hp.com for additional information.
• Display Site Information for Metrocluster. Display of site information in the Serviceguard Manager Map View and Table View makes it easy to identify sites and nodes configured in a site-aware Metrocluster at a glance. • Display Metrocluster Modular Package Properties. Display properties of Metrocluster packages including data replication and the site controller package, in half the time. • Authorization Enhancement.
site (http://support.mozilla.com/en-US/kb/ Options+window+-+Tabs+panel): Note: If you have chosen to open pages in new tabs, Firefox will ignore this option/preference and will open a new window from a link if the page author specified that the new window should have a specific size, because some pages can only be displayed correctly at a specific size. Firefox 3.0 does not provide an API that Serviceguard Manager can use to detect or alter this behavior.
• Version B.5.5.23.02 or later of 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 A.3.0.1, or a higher version of A.3.0., of SMH (System Management Homepage), for HP–UX 11i v3; Version 2.2.7 or higher 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.
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 73).
see the white paper Migrating Packages from Legacy to Modular Style at the address given under “Documents for This Version ” (page 50). 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.
• 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.
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. IMPORTANT: Although cross-subnet topology can be implemented on a single site, it is most commonly used by extended-distance clusters, and specifically site-aware disaster-tolerant clusters, which require Metrocluster (HP add-on software).
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.
Scope of Monitoring The VxVM Volume Monitor detects the following failures: • • • Failure of the last link to a storage device or set of devices critical to volume operation Failure of a storage device or set of devices critical to volume operation An unexpected detachment or disablement of a volume The VxVM Volume Monitor does not detect the following failures: • • • Failure of a redundant link to a storage device or set of devices where a working link remains Failure of a mirrored plex within a volume
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.0 Logical Volume Manager (LVM) 2.0 volume groups, which remove some of the limitations imposed by LVM 1.
Features First Introduced Before Serviceguard A.11.18 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).
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.
See also “cmappmgr” (page 32). About HPVM and Cluster Re-formation Time When a node fails and the cluster re-forms, Serviceguard must wait a certain amount of time to allow I/O from the failed node to be written out to the target storage device. Only after that time has elapsed can Serviceguard allow an adoptive node access to that device; otherwise data corruption could occur. The amount of time Serviceguard waits is calculated by Serviceguard and is not user-configurable.
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.
management-station version of Serviceguard Manager, are also on the High Availability page.) • • • • • • • • • • Managing Serviceguard, 17th Edition. This manual has been revised for the current A.11.19 release. HP Serviceguard Quorum Server Version A.04.00 Release Notes Serviceguard Extension for RAC Version A.11.
NOTE: For HP-UX 11i v2 systems, continue to use Managing Systems and Workgroups in the HP-UX 11i v2 Operating Environments section of docs.hp.com. • • The latest HP Auto Port Aggregation Release Notes and other APA documentation under Auto Port Aggregation (APA) in the I/O Cards and Networking Software section of docs.hp.com. The latest version of Using HP-UX VLANs and other documentation under Virtual LAN in the I/O Cards and Networking Software section of docs.hp.com.
The sole exception to this rule is a rolling upgrade, during which Serviceguard versions can be mixed temporarily, but no cluster configuration changes are allowed. See “Upgrading from an Earlier Serviceguard Release” (page 62) , and Appendix D of Managing Serviceguard, at the address given under “Documents for This Version ” (page 50). Mixed Hardware Architecture As of HP-UX 11i v2 Update 2 (0409) and Serviceguard A.11.
can contain a mix of nodes running HP-UX 11i v2 and 11i v3, with certain restrictions. Future versions of Serviceguard may or may not support such a mix of HP-UX 11i v2 and 11i v3 nodes. For the purposes of this discussion we'll identify three broad cases: homogeneous clusters, clusters in transition, and heterogeneous clusters. NOTE: In all three cases, the discussion refers to mixing HP-UX versions 11i v2 and 11i v3.
• 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 54)).
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.
• • • • • • hacl-cfg 5302/udp hacl-probe 5303/tcp 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.
Installing Serviceguard on HP-UX Dependencies The following are required by Serviceguard. They are part of the HP-UX Base Operating Environment: • • Open SSL, which includes the OPENSSSL-RUN and OPENSSL-LIB filesets. The EventMonitoring bundle, which contains the EMS-CORE and EMS-CORE-COM filesets. Installing Serviceguard Serviceguard will automatically be installed when you install the HP-UX Mission Critical Operating Environment (MCOE).
• • • • • • • • • • • • • • • • • SGWBEMProviders.SGPROV-MOF CM-Provider-MOF.CM-MOF CM-Provider-MOF.CM-PROVIDER Cluster-OM.CM-DEN-MOF Cluster-OM.CM-DEN-PROV Cluster-OM.CM-OM Cluster-OM.CM-OM-AUTH Cluster-OM.CM-OM-AUTH-COM 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.
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.
• If you are upgrading both the Quorum Server and Serviceguard, upgrade the Quorum Server before you upgrade Serviceguard. CAUTION: — Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A.11.19; see “New Cluster Manager” (page 12). — If you are using an Alternate Quorum Server Subnet (page 45), 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).
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 50). Non-Rolling Upgrade Using DRD In a non-rolling upgrade with DRD, you clone each node's root disk and apply the upgrade to the clone, then halt the cluster and reboot each node from its updated clone root disk.
IMPORTANT: supported. Upgrades from earlier releases via DRD are not currently DRD upgrades to version A.11.19 require that you make a manual fix to a checkinstall script in the software depot. — You need to make this fix if: ◦ you are using drd runcmd update-ux to upgrade to Serviceguard A.11.19; OR ◦ you are using drd runcmd swinstall to upgrade to Serviceguard A.11.19. — You do not need to make this fix if you are simply using drd runcmd swinstall to upgrade from one revision of Serviceguard A.11.
IMPORTANT: The following information is additional to the instructions in Appendix D of Managing Serviceguard. If the install depot is on tape (or is a single file) you must copy it onto the clone disk or an upgrade server before running swinstall or update-ux to upgrade the clone.
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 62), and the Rolling Upgrade Exceptions that follow. Rolling Upgrade Exceptions HP-UX Cold Install A rolling upgrade cannot include a cold install of HP-UX on any node.
Uninstalling Serviceguard To uninstall the Serviceguard software, run the SD-UX swremove command. Before removing software, note the following: 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.
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 Patches 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.
• • • • • • • • • • • • • • • • • • QXCR1000753242 Serviceguard 11.
• • • • QXCR1000924513: cmcld SIGSEGV when starting a 1 node cluster after upgrade to A.11.19 QXCR1000938745: Serviceguard 11.19 cmproxyd reports cluster is not configured when it is QXCR1000939674:: cmcld abort due to closing the same fd twice after QS failure QXCR1000941884: Serviceguard 11.19 unlimited modular package service restarts is impossible Additional fixes are listed in the patch form text, which is delivered with the patches.
• • QXCR1000886789: cmquerycl -w full routing restrictions not fully documented - command may fail QXCR1000901306: SG 11.19 SW install to the clone during DRD modification gives global error See also “Restrictions for DRD Upgrades” (page 64). • • • • QXCR1000924513: cmcld SIGSEGV when starting a 1 node cluster after upgrade to A.11.19: QXCR1000938745: Serviceguard 11.
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. See also “Compatibility Information and Installation Requirements” (page 52) of this document. Feature Release A feature release contains new Serviceguard features. Feature releases are for customers who want to use the latest features of Serviceguard.
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). Versions with the same part number are differentiated by the publication date.
