HP Service Guard Version a.11.20 Release

HP Serviceguard Version A.1 1.20 Release Notes HP Part Number: 5900-1493 Published: April 201 1 Edition: 1 Legal Notices © Copyright 1998-201 Hewlett-Packard Development Company, L.P. 1 Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. UNIX® is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. Contents Publishing History..........................................................................................6 1 Serviceguard Version A.1 1.20 Release Notes..................................................7 Announcements........................................................................................................................7 Platform Dependencies.........................................................................................................7 April 201 Patches...............................................................................................................7 1 Serviceguard Bundled Components - New Product Structure......................................................7 Serviceguard Optional Products Not Bundled..........................................................................8 Serviceguard A.1 1.19 Is the Required Basis for Rolling Upgrades.................................................8 New Cluster Manager..........................................................................................................8 Quorum Server Upgrade Required if You Are Using an Alternate Address...................................9 Serviceguard Manager Available from the System Management Homepage (SMH)......................9 Support for Mixed-OS Clusters (HP–UX 1 v2 and 1 v3).........................................................9 1i 1i New Support for Version 5.1 Service Pack 1 (SP1) of Veritas Products from Symantec....................9 Support for Veritas Products from Symantec.............................................................................9 Version 4.1, 4.2, or 4.3 of HPVM Required.............................................................................9 ipnodes Entries Needed in /etc/nsswitch.conf.......................................................................10 Legacy Packages...............................................................................................................10 STORAGE_GROUP Deprecated......................................................................................10 Do Not Use .rhosts ............................................................................................................10 cmviewconf Obsolete.........................................................................................................10 Serviceguard Extension for Faster Failover Obsolete...............................................................10 RS232 Heartbeat Obsolete.................................................................................................10 Token Ring and FDDI Obsolete............................................................................................11 Parallel SCSI Dual Cluster Lock Obsolete...............................................................................11 Parallel SCSI Not Supported for Lock LUN.............................................................................11 Cluster Name Restrictions....................................................................................................11 Optimizing Performance when Activating LVM Volume Groups.................................................11 High Availability Consulting Services....................................................................................12 HP-UX 1 v3 Features Important to Serviceguard....................................................................12 1i New Bundles................................................................................................................12 Support for Veritas 5.1 SP1 from Symantec.......................................................................12 Native Multipathing, Veritas DMP, and Related Features in HP-UX 1 v3..............................12 1i PV Links..................................................................................................................12 PCI Error Recovery....................................................................................................12 Online Replacement of LAN Cards Requires Patch.............................................................13 What’s in this Release.............................................................................................................13 New Features for A.1 1.20 April 201 Patches.........................................................................13 1 New Features for A.1 1.20....................................................................................................13 Serviceguard on HP-UX 1 v3.............................................................................................14 1i What’s Not in this Release..................................................................................................15 About the New Features.....................................................................................................15 Modular CFS Packages for Reducing Package Usage.........................................................15 Advantages of Modular CFS Packages........................................................................16 Improved Performance while Halting a Non-detached Multi-node Package............................16 Support for Veritas 5.1 SP1 on HP-UX 1 v3 Only.............................................................16 1i Easy Deployment...........................................................................................................16 Advantages of Easy Deployment.................................................................................17 Limitations of Easy Deployment...................................................................................17 Halting a Node or the Cluster while Keeping Packages Running (Live Application Detach)......18 Contents 3 What You Can Do....................................................................................................18 Cluster-wide Device Special Files (cDSFs)..........................................................................18 Points To Note..........................................................................................................19 Where cDSFs Reside.................................................................................................19 Checking the Cluster Configuration and Components.........................................................20 Limitations...............................................................................................................21 Cluster Verification and ccmon...................................................................................22 NFS-mounted File Systems..............................................................................................22 The LVM and VxVM Volume Monitor...............................................................................24 Serviceguard Manager...........................................................................................................24 DSAU Integration...............................................................................................................24 Native Language Support...................................................................................................25 What You Can Do.............................................................................................................25 New Features....................................................................................................................26 Current Limitations of Serviceguard Manager.........................................................................27 Browser and SMH Issues................................................................................................27 Pages Launched into New Window rather than Tabs with Firefox Tabbed Browsing...........27 Internet Explorer 7 Zooming Problem..........................................................................28 HP System Management Homepage (HPSMH) Timeout Default.......................................28 Help Subsystem.................................................................................................................28 Before Using HP Serviceguard Manager: Setting Up...............................................................28 Launching Serviceguard Manager........................................................................................29 Patches and Fixes...............................................................................................................29 Features Introduced Before A.1 1.20............................................................................................29 Features First Introduced in Serviceguard A.1 1.19 Patches.........................................................29 Features First Introduced Before Serviceguard A.1 1.19 .............................................................30 About olrad..................................................................................................................30 About vgchange -T........................................................................................................30 About the Alternate Quorum Server Subnet.......................................................................30 About LVM 2.x..............................................................................................................30 About cmappmgr..........................................................................................................31 HPVM 4.1 Support for Windows 2008 Guests.............................................................31 About Device Special Files (DSFs)....................................................................................32 Support for HP Integrity Virtual Machines (HPVM).............................................................33 About HPVM and Cluster Re-formation Time.................................................................33 Access changes as of A.1 1.16..........................................................................................33 Considerations when Upgrading Serviceguard.............................................................34 Considerations when Installing Serviceguard................................................................34 Documents for This Version......................................................................................................34 Further Information..................................................................................................................35 Compatibility Information and Installation Requirements...............................................................35 Compatibility....................................................................................................................35 Mixed Clusters..............................................................................................................35 Mixed Serviceguard Versions.....................................................................................35 Mixed Hardware Architecture.....................................................................................36 Mixed HP-UX Operating-System Revisions....................................................................36 Compatibility with Storage Devices..................................................................................39 Bastille Compatibility.....................................................................................................39 Before Installing Serviceguard A.1 1.20 .................................................................................40 Memory Requirements........................................................................................................40 Port Requirements...............................................................................................................40 Ports Required by Serviceguard Manager.........................................................................41 System Firewalls.................................................................................................................41 Installing Serviceguard on HP-UX..............................................................................................41 Dependencies...................................................................................................................41 4 Contents Installing Serviceguard.......................................................................................................41 If You Need To Disable identd.............................................................................................43 Upgrading from an Earlier Serviceguard Release...................................................................43 Upgrade Using DRD......................................................................................................44 Rolling Upgrade Using DRD.......................................................................................44 Non-Rolling Upgrade Using DRD................................................................................44 Restrictions for DRD Upgrades....................................................................................45 Veritas Storage Management Products.............................................................................46 Rolling Upgrade............................................................................................................46 Requirements for Rolling Upgrade to A.1 1.20................................................................47 Requirements for Rolling Upgrade to A.1 1.19.................................................................47 Obtaining a Copy of Serviceguard A.1 1.19...................................................................47 Rolling Upgrade Exceptions............................................................................................47 HP-UX Cold Install.....................................................................................................47 HP Serviceguard Storage Management Suite and standalone CVM product.....................47 Migrating to Agile Addressing if Using Cluster Lock Disk...............................................47 Upgrading from an Earlier Release if You Are Not Using Rolling Upgrade (Non-Rolling Upgrade)..........................................................................................................................48 Uninstalling Serviceguard........................................................................................................48 Patches for this Version............................................................................................................48 QXCR1000575890: OLR of a LAN Card in SG cluster fails on HP-UX 1 v3.............................49 1i Fixed in This Version...............................................................................................................49 A.1 1.20 Defects Fixed in the April 201 Patches......................................................................50 1 Defects Fixed in A.1 1.20......................................................................................................50 Problems Fixed in this Version of the Serviceguard Manager Plug-in..........................................52 Known Problems.....................................................................................................................53 Known Problems for Serviceguard........................................................................................53 Known Problems for Serviceguard Manager..........................................................................54 About Serviceguard Releases...................................................................................................54 Types of Releases and Patches.............................................................................................54 Platform Release............................................................................................................54 Feature Release.............................................................................................................54 Patch...........................................................................................................................54 Supported Releases............................................................................................................54 Version Numbering............................................................................................................55 Release Notes Revisions..........................................................................................................55 Native Languages ..................................................................................................................55 Contents 5 Publishing History Table 1 Publishing History Printing Date April 201 1 Part Number 5900–1493 Edition First Edition This new edition provides information on Serviceguard A.1 1.19.1 1.1 1. as well as features first added in A.20 and in patches to A. 6 .20 April 201 patches that add new 1 features to it. 20 on HP-UX 1 v3 and Serviceguard Storage 1i Management Suite A.1 SP1 Veritas).xx (with 5. 1i April 201 Patches 1 See “New Features for A.1 1. version B.com/go/hpux-serviceguard-docs —> HP Serviceguard Storage Management Suite A. NOTE: These Release Notes also include information about features first introduced in A.00 for HP-UX 1 v3 Release 1i Notes at http://www.20 HP Package-Manager SD Product. See “Serviceguard 1i on HP-UX 1 v3” (page 14). Serviceguard Bundled Components .1 1. For more information.20 Release Notes Announcements This section announces the most important features and limitations of Serviceguard A. as components of the Serviceguard product.1 1. version A.1 1.1 1. • • • • • The Cluster Object Manager (COM).20 on HP-UX 1 v3 1i For information about patches required to support HP Storage Management Suite (SMS) bundles. see “Features First Introduced in Serviceguard A. T1905CA: • HP Serviceguard Manager version B. see “What’s in this Release” (page 13).00 HP Serviceguard WBEM Providers SD product.20 — software and license The following products are bundled with Serviceguard.20 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).19 patches.1 SP1 Veritas) on HP-UX 1 v3 only 1i PHSS_41674 for Serviceguard CFS A. See “Serviceguard Manager” (page 24).1 Serviceguard Version A.07.20.10 This version of the web-based graphical user interface (GUI). version.03.20 April 201 Patches” (page 13) for information about new features 1 introduced in the following April 201 patches: 1 • • PHSS_41628 for Serviceguard A.1 1.1 1. version A.10 HP SG Cluster CVM CFS SD Product.20 HP Cluster-Monitor SD Product.00 (with 5.03. version A.New Product Structure The following Serviceguard components are now available for HP-UX 1 v3: 1i • Product T1905CA — A.hp. Platform Dependencies IMPORTANT: This new version of Serviceguard is supported on 1 v3 only.1 1.1 1. Announcements 7 .1 1.04. see the HP Serviceguard Storage Management Suite Version A.04. is also known as the SMH Plug-in.04. or simply plug-in.19 Patches” (page 29).1 1. version A. 19. It is recommended to use this method as it is easier and is less disruptive because each node is down for a shorter time. you can do a rolling upgrade from A.1 1. including Serviceguard A.Serviceguard Optional Products Not Bundled The following optional product is not bundled with Serviceguard.1 1.19 release.18 to A. Serviceguard Extension for Faster Failover is no longer being offered as a separate product (starting with A.1 1.1 1.19 is the only version of Serviceguard that will allow both the older version of the cluster manager and the New Cluster Manager (page 8) to coexist during a rolling upgrade.19).20. and can also be downloaded from http://www. providing significant performance improvements.com/go/softwaredepot/ha: • Quorum Server.1 1.19 release to a post-A. 8 Serviceguard Version A.19 before you can do a rolling upgrade to any later release.20.20 Release Notes . but is delivered free with Serviceguard on the Serviceguard Distributed Components CD. and the Quorum Server Version A.1 1. you must upgrade to A.19. For more information.20. New Cluster Manager IMPORTANT: Serviceguard A. or from A.1 1. but you cannot do a rolling upgrade from A.1 1. This means that though you can perform a rolling upgrade to A.1 1.1 1. You can also do a rolling upgrade using a Dynamic Root Disk (DRD).19.19.1 1. If you are already running A. NOTE: Because of these built-in performance improvements. Because of this change.00 Release Notes.19 to A.1 1.19 Is the Required Basis for Rolling Upgrades A. you can skip the discussion that follows. the new cluster manager affects node timeout and failover and cluster re-formation.1 1. In a running cluster. you cannot do a rolling upgrade from a pre-A. For example.1 1. see “Upgrade Using DRD” (page 44).18 directly to A.1 1.hp. See “Upgrading from an Earlier Serviceguard Release” (page 43) and “Rolling Upgrade” (page 46).19 first. There is also a one-time effect on upgrade to Serviceguard A.1 1. you must upgrade to Serviceguard A.04. Serviceguard A.1 1.1 1.1 1. see the discussion of MEMBER_TIMEOUT under “Cluster Configuration Parameters” in the latest version of Managing Serviceguard for more information.19 introduced a new cluster manager. This transition can take up to one second.1 1.19 on HP-UX 1 v2 and want to upgrade the nodes to 1 v3 over a period 1i 1i of time.1 1.01 on HP-UX 1 v3). Serviceguard A. For further caveats that apply to specific upgrade paths make sure you read the following sections in these Release Notes: “Compatibility Information and Installation Requirements” (page 35) and “Upgrading from an Earlier Serviceguard Release” (page 43). See the section “Special Considerations for Upgrade to Serviceguard A.17. station-management version of Serviceguard Manager is obsolete (as of Serviceguard A. at the address given under “Compatibility Information and Installation Requirements” (page 35). and CFS from Symantec.19. CAUTION: From the time when the old cluster manager is shut down until the new cluster manager forms its first cluster. 1i Support for Veritas Products from Symantec For the most up-to-date information.19” in Appendix D of the latest version of Managing Serviceguard for more information.1 1.1 1.3 of HPVM Required If you intend to use HP Integrity Virtual Machines (HPVM) with Serviceguard A. or 4. during which time the old cluster manager will shut down and the new cluster manager will start. Quorum Server Upgrade Required if You Are Using an Alternate Address If you are using an alternate address on a Serviceguard version earlier than A.04. check the HP Serviceguard/SGeRAC/Serviceguard Storage Management Suite/Serviceguard Manager Plug-in Compatibility and Feature Matrix.1 1 1. see “Serviceguard Manager” (page 24).1 SP1 of Veritas VxVM. you must install or upgrade to HPVM 4.1 1. HPVM 4.1 1. HP strongly recommends that you use no Serviceguard commands other than cmviewcl (1m) until the new cluster manager successfully completes its first cluster re-formation.00 before you upgrade the cluster.20 does not run on HP–UX 1 v2. a node failure will cause the entire cluster to fail. 4. 1i Support for Mixed-OS Clusters (HP–UX 1 v2 and 1 v3) 1i 1i With some limitations.20. CVM.1 1.1 Service Pack 1 (SP1) of Veritas Products from Symantec With the patches listed under “April 201 Patches” (page 7) Serviceguard A.1 1. New Support for Version 5.1 1.1 or 4. You may want to take advantage of this if you are currently running 1i 1i Serviceguard A.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. 1i For more information.1 1. Version 4.3 is supported with Serviceguard A.19. The last version of Serviceguard that supports that product is A. in preparation for upgrading to Serviceguard A.1 1.18). CAUTION: If you fail to do this. you must upgrade the Quorum Server to version A.2. HP now supports Serviceguard clusters in which some nodes are running HP-UX 1 v2 and some 1 v3.20 on HP-UX 1 v3 supports version 5. see “Mixed Clusters” (page 35). the upgraded cluster will be running without a cluster lock until you have upgraded the Quorum Server.1.20 April Announcements 9 .2.20. IMPORTANT: The cluster must be running Serviceguard A.1 1.17 (A. Serviceguard Manager Available from the System Management Homepage (SMH) For details. See About the Alternate Quorum Server Subnet (page 30) for more information.19. NOTE: The earlier. A package using Veritas Cluster Volume manager from Symantec (CVM) disk groups for raw access (without Veritas Cluster File System from Symantec.20. 1i A minimum Serviceguard configuration needs two network interface cards for the heartbeat in all cases. See “Safeguarding against Loss of Name Resolution Services” in Chapter 5 of Managing Serviceguard for more information.20 Release Notes . cmviewconf Obsolete cmviewconf is obsolete as of Serviceguard A.1 1. IMPORTANT: Support for legacy packages (created using the earlier method) will be withdrawn altogether in a future release.conf Beginning with version A. new package features are being implemented only in modular packages (those created using the method introduced in A.1 1. See “Reviewing Cluster and Package Status” in Chapter 7 of Managing Serviceguard for more information.1 1. Use $SGCONF/cmclnodelist instead. If SGeFF is present. see “Creating the Storage Infrastructure with Veritas Cluster Volume Manager (CVM)” in Chapter 5 of Managing Serviceguard for more information. See also “About cmappmgr” (page 31). See Chapter 6 of Managing Serviceguard for more information.17 on HP-UX 1 v2 and A.1 1.20.rhosts file as a means of allowing root access to an unconfigured node. or CFS) needs to declare a dependency on SG-CFS-pkg. Use the modular method to create new packages whenever possible. See “Allowing Root Access to an Unconfigured Node” in Chapter 5 of Managing Serviceguard for more information. ipnodes Entries Needed in /etc/nsswitch.20. it will be removed from the system when you upgrade to Serviceguard A.conf.19 (preparatory to a rolling upgrade to A.1 1. Serviceguard uses calls that require ipnodes entries to be configured in the /etc/nsswitch. Do Not Use . RS232 Heartbeat Obsolete The current version of Serviceguard does not support RS232 for the cluster heartbeat (Serviceguard A. Use cmviewcl (1m) to obtain information about the cluster. 10 Serviceguard Version A.16 on HP-UX 1 v1 were the last versions that did).1 1. or one heartbeat subnet with a standby.201 patches. or one heartbeat subnet using APA with two physical ports in hot standby mode or LAN monitor mode. Support for it will be withdrawn in a future release. Serviceguard Extension for Faster Failover Obsolete Performance improvements in the New Cluster Manager (page 8) make the Serviceguard Extension for Faster Failover (SGeFF) obsolete.1 1.20) or A.1 1.19. using one of the following configurations: • • • two heartbeat subnets.1 1i 1.rhosts Do not use . See “Support for HP Integrity Virtual Machines (HPVM)” (page 33) for more 1 information about HPVM.19.18). Legacy Packages As of Serviceguard A.1 1. STORAGE_GROUP Deprecated The STORAGE_GROUP parameter (in the package configuration file for legacy packages) is deprecated as of Serviceguard A.1 1. the amount of available memory. Token Ring and FDDI Obsolete Serviceguard A. stop increasing it. semicolon (. for legacy packages). or underscore (_) Optimizing Performance when Activating LVM Volume Groups If a package activates a large number of volume groups. Parallel SCSI Dual Cluster Lock Obsolete You must use Fibre Channel connections for a dual cluster lock. equal-sign (=). These characters are deprecated. and failover groups of Token Ring and FDDI interfaces in the LAN Monitor Mode of the APA product.16 on HP-UX 1 v1 were 1i the last versions that did).17 on HP-UX 1 v2 and A. Virtual LAN (VLAN) interfaces over FDDI or Token Ring.1 1. Tune performance by increasing this parameter a little at a time and monitoring the effect on performance at each step.hp. hyphen (-). use an LVM cluster lock disk.). because they will be illegal in a future Serviceguard release. Factors you need to take into account include the number of CPUs.20 does not support Token Ring and FDDI technologies for the cluster heartbeat and data networks (Serviceguard A.1 1. as a failover or other unexpected circumstances could result in that node running the package. or reset it to a lower level.18). and the number and characteristics of other packages that will be running on the node. For more information. the HP-UX kernel settings for nfile and nproc. NOTE: Remember to do this exercise not only on the node on which the package will normally run. Cluster Name Restrictions The following characters must not be used in the cluster name if you are using the Quorum Server: at-sign (@).com/go/hpux-serviceguard-docs) and the comments in the package configuration file. see the section “Optimizing for Large Numbers of Storage Units” in Chapter 6 of the latest edition of Managing Serviceguard (in the High Availability collection on http://www. meaning that you should not use them.1 1i 1. or-sign (|). Announcements 1 1 . as soon as performance starts to level off or decline. See “Dual Lock Disk” in Chapter 3 of Managing Serviceguard for more information about dual cluster locks. HP-UX 1 v3 does not support these two technologies. even if you are not using the Quorum Server. you must use Fibre Channel for a lock LUN. or dot (. you can improve the package’s start-up and shutdown performance by carefully tuning the concurrent_vgchange_operations parameter in the package configuration file (or control script. Future releases will require the cluster name to: • • Begin and end with an alphanumeric character Otherwise use only alphanumeric characters.To provide the required redundancy for both networking and mass storage connectivity on servers with fewer than three I/O slots.). you can no longer implement it in a parallel SCSI configuration (as of Serviceguard A. you may need to use multifunction I/O cards that contain both networking and mass storage ports. or a Quorum Server. but also on the node with the least resources in the cluster. 1i The unsupported configurations include physical Token Ring and FDDI interfaces. Parallel SCSI Not Supported for Lock LUN The lock LUN functionality does not support parallel SCSI. For more information about the cluster lock. see “Cluster Lock” in Chapter 3 of the latest edition of Managing Serviceguard. If you need to use parallel SCSI.1 1. High Availability Consulting Services Because Serviceguard configurations can be complex to configure and maintain. but will be 1i inactive unless you turn off native multipathing (in that case they will function as they did in previous releases of HP-UX). See “Support for Veritas 5. You should also work with your HP representative to ensure that you have the latest firmware revisions for disk drives. LAN controllers. you do not have to take any additional steps to make this happen. Serviceguard A.20 Release Notes . the I/O subsystem by default will start performing 1i load balancing and multipathing for all multipath devices (whether or not they are managed by VxVM/DMP. isolate. DMP acts as a pass-through 1i driver. and “What’s 1i in this Release” (page 13). which introduces important improvements over 1i 1 v2. This is 1i often referred to as native multipathing.1 1.20 runs only on HP-UX 1 v3. When you upgrade a system to HP-UX 1 v3.1 SP1 from Symantec With the April 201 Patches (page 7). HP-UX 1 v3 Features Important to Serviceguard 1i Serviceguard A. See also “About Device Special Files (DSFs)” (page 32).1 1 1. and the Logical Volume Management volume of the HP-UX System Administrator’s Guide at http://www. but do not provide multipathing and load balancing. CVM. PCI Error Recovery PCI Error Recovery enables an HP-UX system to detect. 1i Native Multipathing. particularly in regard to the I/O subsystem.20 is now available as a recommended product in the HP-UX 1 v3 HA-OE 1i and DC-OE bundles. Support for Veritas 5. New Bundles Serviceguard A. Veritas Volume Manager (VxVM) and Dynamic Multipathing (DMP) from Symantec are supported on HP-UX 1 v3.1 1. HP strongly recommends that you use its high availability consulting services to ensure a smooth installation and rollout. but HP recommends 1i that it remain enabled in a Serviceguard cluster only if your storage devices are configured with multiple paths and you have not disabled HP-UX native multipathing.0.hp. PV Links Previous editions of Managing Serviceguard recommended creating LVM PV links for LUNs defined in disk arrays. On HP-UX 1 v3. and whether or not you decide to migrate the system to agile addressing). For more information about multipathing in HP-UX 1 v3. See the subsections that follow. and Related Features in HP-UX 1 v3 1i The HP-UX 1 v3 I/O subsystem provides multipathing and load balancing by default. PCI Error Recovery is enabled on HP-UX 1 v3 systems by default.1 1. these PV Links are redundant.1 and 5. Veritas DMP. allowing multipathing and load balancing to be controlled by the HP-UX I/O subsystem instead. they are supported. and CFS. disk controllers. contact your HP representative for more information.1 SP1 of VxVM/VxFS.20 on HP-UX 1 v3 supports versions 1i 5. 12 Serviceguard Version A. see the white paper HP-UX 1 v3 Native 1i 1i Multipathing for Mass Storage. and automatically recover from a PCI error.com/go/hpux-core-docs.1 SP1 on HP-UX 1 v3 Only” (page 16). and other hardware. 1 1.hp. see also the “Announcements” (page 7).20 April 201 Patches 1 Serviceguard A. What’s in this Release 13 .20. you must apply patch PHNE_35894 or a later cumulative patch.20 runs only on 1 v3 (see “Serviceguard on HP-UX 1 v3” 1i 1i (page 14)) and adds new functionality. See “Patches for this Version” (page 48) and “QXCR1000575890: OLR of a LAN Card in SG cluster fails on HP-UX 1 v3” (page 49). • A new capability in Serviceguard allows a package's applications to remain running (unmonitored) while you do maintenance on the node or cluster on which the package is running. For information about documentation. CVM.com/go/hpux-networking-docs —> HP-UX 11i v3 Networking Software.03. see the Interface Card OL* Support Guide for HP-UX 1 v3. 1i For more information about replacing interface cards online.1 1.1 1.hp. What’s in this Release This release of Serviceguard A.20 • New commands (and equivalent capabilities with Serviceguard Manager) provide a quick and easy way to configure and deploy a Serviceguard cluster. provides 1 the following new capabilities: • • • • • • “Modular CFS Packages for Reducing Package Usage” (page 15) “Improved Performance while Halting a Non-detached Multi-node Package” (page 16) Support for VxVM.IMPORTANT: If your storage devices are configured with only a single path. See the subsections that follow for details. otherwise Serviceguard may not detect when connectivity is lost and cause a failover. with the patches listed under “April 201 Patches” (page 7). and CFS version 5. you should disable PCI Error Recovery. See “Halting a Node or the Cluster while Keeping Packages Running (Live Application Detach)” (page 18). New Features for A. See “Easy Deployment” (page 16). at http://www. For instructions on using the pci_eh_enable parameter to disable PCI Error Recovery.10 (See “Serviceguard Manager” (page 24) ) New Features for A. see “Documents for This Version” (page 34).1 SP1 on HP-UX 1 1iv3 only (See “Support for Veritas 5.1 1.1 SP1 on HP-UX 1 v3 Only” (page 16) 1i Enhancements to Easy Deployment commands (See “Easy Deployment” (page 16)) Updates to NFS-mounted File System (See “NFS-mounted File Systems” (page 22)) New Serviceguard Manager capabilities in B. see the “Tunable Kernel Parameters” section of the latest edition of the PCI Error Recovery Product Note which you can find at http://www.com/go/hpux-core-docs -> HP-UX 11i v3 -> 1i User guide. or you have disabled multipathing. Online Replacement of LAN Cards Requires Patch Before you can replace a LAN card online (without bringing down the cluster) as described under “Replacing LAN or Fibre Channel Cards” in Chapter 8 of Managing Serviceguard. which identifies network interface cards (NICs) that are part of the Serviceguard cluster configuration. see the white paper Number of Processes and Process ID Values 1i on HP-UX at http://www. See “Native Multipathing. • New Serviceguard capabilities allow you allow you to check the soundness of the cluster configuration.• A new type of device file allows you to deploy a set of persistent device special files that is consistent across the cluster. and Related Features in HP-UX 1 v3” (page 12). See “Cluster-wide Device Special Files (cDSFs)” (page 18). These new device special files are called cluster device special files or cDSFs.20 Release Notes .hp. at http:// www. ◦ • The LAN Monitor mode of APA. For more information. sometimes also called persistent LUN binding. Previous versions of HP-UX imposed a limit of 30. which prevents automatic failover of a package across SITEs. New capabilities in Serviceguard and HPVM allow online migration of a virtual machine. and the health of its components. 14 Serviceguard Version A.1 1. Serviceguard supports Process IDs (PIDs) of any size. This capability can be used only in a site-aware disaster-tolerant cluster. and then from the system. See the section “Online VM Migration with Serviceguard” in the white paper Designing high-availability solutions with HP Serviceguard and HP Integrity Virtual Machines. without bringing down the cluster. 1i Serviceguard supports the following networking capabilities: ◦ The HP-UX olrad -C command. this limit has been removed as of HP-UX 1 v3. the maximum number of volume groups you can configure in a 1i Serviceguard cluster is the maximum supported by HP-UX. See the HP-UX documentation for details.01.20 supports a new failover policy. • • Serviceguard supports HP-UX native multipathing and load balancing.hp. more thoroughly than you could in the past. which requires Metrocluster (additional HP software). and to do so at any time. Veritas DMP. for device special files (DSFs). You can remove a NIC from the cluster configuration. up to the maximum value supported by HP-UX and the node’s underlying hardware architecture. rather than only when changing the configuration of the cluster or its packages. 1i • Serviceguard supports HP-UX agile addressing. The following is a list of some important 1 v3 capabilities that Serviceguard supports.com/go/hpux-serviceguard-docs —> HP Serviceguard —> White papers.17. • Serviceguard A.000.com/go/hpux-core-docs —> HP-UX 11i v3 —> White papers. Serviceguard on HP-UX 1 v3 1i Serviceguard support for HP-UX 1 v3 was first introduced in Serviceguard version A. • • You can now you can use NFS-mounted (imported) file systems as shared storage in packages.1 1. site_preferred_manual. See “About olrad” (page 30).1 1i 1. See “About Device Special Files (DSFs)” (page 32). eliminating to risk of name-space collisions amongst the cluster nodes. See “Checking the Cluster Configuration and Components” (page 20). See “NFS-mounted File Systems” (page 22). • Serviceguard supports the increased number of LVM volume groups supported as of the HP-UX 1 v3 0809 Fusion release. 1 1.20 release. -r 11. As a result. both for data and the cluster lock. You can also merge all the checkpoints and snapshot packages into individual modular checkpoint and snapshot packages respectively. • • • Serviceguard A.x volume groups.x” (page 30). see “Announcements” (page 7). For the most up-to-date information.09 option. which allows multi-threaded activation of volume groups.com/go/hpux-serviceguard-docs —> HP Serviceguard. check the HP Serviceguard/SGeRAC/Serviceguard Storage Management Suite/Serviceguard Manager Plug-in Compatibility and Feature Matrix. Serviceguard provides the flexibility to combine all the CVM disk groups and CFS mount points required by an application into a single package using the modular style of packaging.16 are still supported.1 1. See the cmviewcl (1m) manpage for details Serviceguard A.20 no longer supports versions of Veritas CVM and CFS from Symantec 5.1 1. see the fsweb (1m) manpage. See also “Rolling Upgrade Exceptions” (page 47). at the address given under “Compatibility Information and Installation Requirements” (page 35). What’s in this Release 15 . 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).12 and -r 11. For more information about using Serviceguard with partitioned systems. Information on using these capabilities is in the latest version of Managing Serviceguard. About the New Features The subsections that follow discuss the major new capabilities introduced in the A.20 does not currently support the target port congestion control capability in HP-UX 1 v3.• • Serviceguard supports LVM 2.20 does not currently support parallel resynchronization of LVM volume groups. see the white paper HP Serviceguard Cluster Configuration for HP-UX 1 or Linux Partitioned Systems at http:// 1i www.1 1. See also “What’s Not in this Release” (page 15). See “About LVM 2.1 1. See “About vgchange -T” (page 30). For other obsolete and deprecated features. Serviceguard now supports cell OL* (online addition and deletion of cells) on HP Integrity servers that support them). 1i Serviceguard A. • Serviceguard supports the following recently added HP-UX 1 v3 capabilities: 1i ◦ Dynamic Root Disk (DRD). What’s Not in this Release • • The cmviewcl command no longer supports the -r 11. For more information about FSWeb. This helps in easy management of the packages in that cluster and leaves more packages for other applications.hp. which you can find at the address given under “Documents for This Version” (page 34). because of an LVM issue. as well as those introduced in patches to A. see “Upgrade Using DRD” (page 44).0 and earlier.20. because of an LVM issue. • • Serviceguard supports vgchange -T. Modular CFS Packages for Reducing Package Usage With modular CFS packages. the number of packages used for configuring disk groups and mount points in that cluster reduces significantly compared to the packages used for configuring the same in the legacy style of packaging. com/go/hpux-serviceguard-docs —> HP Serviceguard Storage Management Suite A.Using the modular style of packaging provides flexibility and can be managed better compared to the legacy style of packaging.1 1.20 on HP-UX 1 v3 with the patches listed under “April 201 Patches” 1i 1 (page 7) supports versions 5.04. Serviceguard A. Advantages of Modular CFS Packages • • A single multi-node package can include multiple disk groups and mount points.1 1. CVM. 1i Easy Deployment In the past you had two main choices for configuring a cluster: using Serviceguard commands.04. The Serviceguard cluster and package information displayed by cmviewcl (1m) output is more compact. 1 Support for Veritas 5.20 patch (PHSS_41628) and Serviceguard CFS A.20 April 201 patch (PHSS_41628). NOTE: For this feature to be enabled. and not 5.1 of Veritas VxVM. Supports parallel activation of disk groups and parallel mounting of mount points. and is the highly recommended approach to create CFS packages.1 1.1 SP1 of Veritas VxVM.1 SP1 Veritas).xx (with 5. thus reducing the number of packages required to build a CVM/CFS storage configuration.0.1 and 5. as described in detail in chapter 5 of Managing Serviceguard. including information about new capabilities.20 patch (PHSS_41674) must be installed. the performance benefit increases as the number of nodes increases.1 1.0.00 for HP-UX 1 v3 Release Notes at the address given above.1 1. see “Creating a Storage Infrastructure with Veritas Cluster File System (CFS)” and “Managing Disk Groups and Mount Points Using Modular Packages” in chapter 5 of Managing Serviceguard Nineteenth Edition manual. Modular CFS packages can also be configured and managed by Serviceguard Manager.1 SP1 on HP-UX 1 v3 Only 1i IMPORTANT: For information about patches required to support HP Storage Management Suite (SMS) bundles see the HP Serviceguard Storage Management Suite Release Notes for your version of the Storage Management Suite at http://www. or using the Serviceguard Manager 16 Serviceguard Version A.1 1. • Serviceguard A. the package is halted simultaneously on all the nodes or the list of the nodes specified. • NOTE: For more information about SMS support for version 5.20 on HP-UX 1 v3 with the September 2010 patch supports version 1i 5. see the HP Serviceguard Storage Management Suite Version A. thus reducing the down time in halting the packages.hp.1 SP1. This performance improvement is directly dependent on the number of nodes on which the package needs to be halted. both patches.20 Release Notes . Disk groups and mount points can also be placed in separate multi-node packages. and CFS from Symantec. When cmhaltpkg (1m) is run on a non-detached multi-node package. Improved Performance while Halting a Non-detached Multi-node Package The command cmhaltpkg (1m) has been modified so that you will now see a performance improvement while halting a non-detached multi-node package. CVM. • • • For more information on modular CFS packages. but dependencies between the mount points and disk groups must be configured explicitly in the configuration files. cmhaltpkg (1m) defaults to this behavior and the feature is automatically enabled once all the nodes in the cluster are upgraded to Serviceguard A. and CFS from Symantec. and patches that are required in addition to those listed under “April 201 1 Patches” (page 7).0 and earlier. Serviceguard A. cmdeploycl (1m) is enhanced with the following options: • A new -s [site] option that can be used to configure site-aware disaster-tolerant clusters. Limitations of Easy Deployment • • • • • • • • Does not install or verify Serviceguard software.1 1. Does not configure access control policies. The commands: • • • Configure networking and security (cmpreparecl (1m)) Create and start the cluster with a cluster lock device (cmdeploycl (1m)) Create and import volume groups as additional shared storage for use by cluster packages (cmpreparestg (1m)). there is a new -N option to cmquerycl. See “About Device Special Files (DSFs)” (page 32). When -g is used. Does not install or configure firewall and related software. cmdeploycl (1m) can be used to configure a single site cluster using either a quorum server or lock LUN. Advantages of Easy Deployment • • • • Quick and simple way to create and start a cluster.20. In addition. which requires Metrocluster software to be installed. cmpreparestg (1m) will fail if cDSFs and persistent DSFs are mixed in a volume group.GUI (or some combination of these two methods). which you can use to obtain networking information for the cluster heartbeat. See also “Cluster-wide Device Special Files (cDSFs)” (page 18). Does not configure packages. For more information. there is a third option. Simplifies creation of shared storage for packages. See “Cluster-wide Device Special Files (cDSFs)” (page 18) for more information about cDSFs. Automates security and networking configuration that must always be done before you configure nodes into a cluster. Requires agile addressing for disks. A new -cfs option is used to deploy a Serviceguard cluster with SG-CFS-pkg. you can specify the disk group options using the -o dg_opts option. and cmpreparestg (1m). Does not support cross-subnet configurations. Simplifies cluster lock configuration. cmdeploycl (1m). see the man pages of cmdeploycl (1m) and cmpreparestg (1m). It also mandates the use of quorum server when sites are specified. The Easy Deployment tool consists of three commands: cmpreparecl (1m). These commands allow you to get a cluster up and running in the minimum amount of time. • cmpreparestg (1m) is enhanced to support the creation and modification of VxVM/CVM disk groups. Does not discover or configure a quorum server (but can deploy one that is already configured). called Easy Deployment. As of Serviceguard A. This is a required option if you intend to enable CVM/CFS on a cluster by configuring SG-CFS-pkg. In the April 201 patch (PHSS_41628). A new -g option is included to serve this purpose. What’s in this Release 17 . the cmdeploycl (1m) and cmpreparestg (1m) 1 commands have been enhanced as part of further development to the Easy Deployment feature. including instances of detached multi-node packages. IMPORTANT: • This capability applies only to modular failover packages and modular multi-node packages. • When you have done the necessary maintenance. When upgrading to future releases. • Halt the cluster (cmhaltcl (1m) with the -d option) without causing its running packages to halt. see “Using Easy Deployment” in chapter 5 of Managing Serviceguard. 18 Serviceguard Version A. Cluster-wide Device Special Files (cDSFs) Under agile addressing on HP-UX 1 v3. See “About Device Special Files (DSFs)” (page 32) for more information.20.1 1.20 Release Notes . this identifier is reflected in the name of the Device Special File (DSF). When cmdeploycl (1m) is used on a cluster where SGeRAC is installed. Such maintenance might consist of anything short of rebooting the node or nodes.20 (collectively known as Live Application Detach (LAD)) allow you to do this kind of maintenance while keeping the packages running. The packages are no longer monitored by Serviceguard. Halting a Node or the Cluster while Keeping Packages Running (Live Application Detach) There may be circumstances in which you want to do maintenance that involves halting a node. • • Halt a detached package. cmdeploycl (1m) provides a warning if the cluster being deployed does not meet SGeRAC specific requirements. • Halt a node (cmhaltnode (1m) with the -d option) without causing its running packages to halt or fail over. but you cannot use it when upgrading to A. and normal monitoring will resume on the packages.1 1. but a likely case is networking changes that will disrupt the heartbeat. For more information. Restart normal package monitoring by restarting the node (cmrunnode) or the cluster (cmruncl). For more information and instructions.. see “Halting a Node or the Cluster while Keeping Packages Running” in chapter 7 of Managing Serviceguard. What You Can Do You can do the following. New command options in Serviceguard A. but the applications continue to run. For more information. including important rules and restrictions. Packages in this state are called detached packages. without halting or failing over the affected packages. or the entire cluster. you will be able to use LAD in conjunction with rolling upgrade.20. Until you restart the node (cmrunnode (1m)) these packages are detached — not being monitored by Serviceguard. each device has a unique identifier as seen from a given 1i host.• • Does not support asymmetric network configurations (in which a given subnet is configured only on a subset of nodes). because the capability is not available until all the nodes are running A. see “Halting a Node or the Cluster while Keeping Packages Running” in chapter 7 of Managing Serviceguard.1 1.1 1. Until you restart the cluster (cmruncl (1m)) these packages are detached — not being monitored by Serviceguard. you can restart the node or cluster. Such partitions can be addressed by a device file using the agile addressing scheme. NOTE: Software that assumes DSFs reside only in /dev/disk and /dev/rdisk will not find cDSFs and may not work properly as a result. cDSFs do not support disk partitions. provided that Serviceguard A. Persistent DSFs that are not cDSFs continue to reside in /dev/disk and /dev/rdisk. and swap devices. VxVM. Recovery support for such a configuration is not supported.1 1. Limitations of cDSFs • • • • • cDSFs are supported only within a single cluster. and removes a potential source of configuration errors.Because DSF names may be duplicated between one host and another. If you require support for recovery archives in a Serviceguard environment do not implement Ignite-UX with cDSFs. but not by a cDSF. It is possible that a 1i storage device on an 1 v3 system could be addressed by DSFs of all three types of device — 1i but if you are using cDSFs. such as root. as of the date of this document. this was true of the Veritas Volume Manager. A node can belong to only one cDSF group. which ensure that each storage device used by the cluster has a unique device file name. Once you have created cDSFs for the cluster. See “Creating Cluster-wide Device Special Files (cDSFs)” and “Using Easy Deployment” in chapter 5 of Managing Serviceguard for instructions. Where cDSFs Reside cDSFs reside in two new HP-UX directories. • • cDSFs apply only to shared storage. or any other application that assumes DSFs reside only in /dev/disk and /dev/rdisk. it is possible for different storage devices to have the same name on different nodes in a cluster. cDSFs are not supported by VxVM. Serviceguard A. you should ensure that you use them exclusively as far as possible. CFS. LVM Commands and cDSFs Some HP-UX commands have new options and behavior to support cDSFs.20 September 2010 patch (PHSS_41225) and later supports Cluster-wide device files (cDSFs).1 1. specifically: What’s in this Release 19 . HP recommends that you use cDSFs for the storage devices in the cluster because this makes it simpler to deploy and maintain a cluster. you cannot define a cDSF group that crosses cluster boundaries. Oracle ASM cannot detect cDSFs created after ASM is installed. the group should comprise the entire cluster. and legacy DSFs (DSFs using the naming convention that was standard before HP–UX 1 v3) in /dev/dsk and /dev/rdsk. CVM. boot. Points To Note • cDSFs can be created for any group of nodes that you specify. • cDSFs are not supported by Ignite-UX in Serviceguard Cluster environment. cDSFs are available on HP-UX as of the September 2010 Fusion Release. Using cDSFs with Easy Deployment (page 16) further simplifies the configuration of storage for the cluster and packages. HP-UX automatically creates new cDSFs when you add shared storage.20 and the required patch are installed on each node. /dev/cdisk for cluster-wide block devicefiles and /dev/rcdisk for cluster-wide character devicefiles. they will not be generated for local storage. and for the same piece of storage to be addressed by different names. Normally. In past releases. In addition.20. much of this was done by cmcheckconf (1m) and/or cmapplyconf (1m) and could be done only when you were changing the configuration of the cluster or packages. These checks help you to ensure that packages will start up and fail over successfully.1 1.• vgimport –C causes vgimport (1m) to use cDSFs • vgscan –C causes vgscan (1m) to display cDSFs See the manpages for more information. see the manpage.1 1. • io_cdsf_config (1m) displays information about cDSFs.20 Release Notes . and the health of its components. The following capabilities are new as of Serviceguard A.20. you can check configuration of the cluster and all of its packages at any time by running cmcheckconf (1m) without arguments (or with -v.hp. For more information on vgcdsf.1 1. See the manpage for more information. Legacy DSFs in the volume group will not be converted. but you can use the HP-UX vgdsf script to convert these legacy DSFs to persistent DSFs if you need to. The following new HP-UX commands handle cDSFs specifically: • vgcdsf(1m) converts all persistent DSFs in a volume group to cDSFs. See also cmcheckconf (5). see below). Checking the Cluster Configuration and Components Serviceguard provides tools that allow you to check the soundness of the cluster configuration. As of Serviceguard A. and a new command. cmcompare (1m) allows you to compare the contents and characteristics of cluster-wide files to make sure they are consistent. 20 Serviceguard Version A. see the white paper LVM Migration from Legacy to Agile Naming Model at http://www.com/go/hpux-core-docs. these commands perform additional checks. For more information on the vgdsf script. with or without -k or -K). Serviceguard does not check /etc/fstab) Shared volume groups configured to activate on boot Volume group major and minor numbers unique Redundant storage paths functioning properly What’s in this Release 21 .conf user-created files (if you specify them) • • LVM logical volumes VxVM disk groups: ◦ ◦ • File consistency: ◦ For more information.) These new checks are not done for legacy packages.conf /etc/services package control scripts for legacy packages (if you specify them) /etc/cmcluster/cmclfiles2check /etc/cmcluster/cmignoretypes. (This new version of the command also performs all of the checks that were done in previous releases.conf /etc/cmcluster/cmknowncmds /etc/cmcluster/cmnotdisk. see chapter 6 of Managing Serviceguard. For information about legacy and modular packages. LVM volume groups: ◦ ◦ ◦ • ◦ • Check that each volume group contains the same physical volumes on each node Check that each node has a working physical connection to the physical volumes Check that volume groups used in modular packages are cluster-aware Check that file systems have been built on the logical volumes identified by the fs_name parameter in the cluster's packages. Check that each node has a working physical connection to the disks. Limitations Serviceguard does not check the following conditions: • • • • • Access Control Policies properly configured (see chapter 5 of Managing Serviceguard for information about Access Control Policies) File systems configured to mount automatically on boot (that is. see “Checking the Cluster Configuration and Components” in chapter 7 of Managing Serviceguard. cmcheckconf (1m) validates the current cluster and package configuration. including external scripts and pre-scripts for modular packages. Check that files including the following are consistent across all nodes: – – – – – – – – – /etc/hosts (must contain all IP addresses configured into the cluster) /etc/nsswitch.NOTE: • All of the checks below are performed when you run cmcheckconf (1m) without any arguments (or with only -v. Check that each disk group contains the same number of disks on each node. and runs cmcompare (1m) to check file consistency across nodes. • So that Serviceguard can ensure that all I/O from a node on which a package has failed is flushed before the package restarts on an adoptive node. NFS-mounted File Systems As of Serviceguard A.sec Consistency across cluster of major and minor numbers device-file numbers Nested mount points Staleness of mirror copies Cluster Verification and ccmon The Cluster Consistency Monitor (ccmon) provides even more comprehensive verification capabilities than those described in this section. The following rules and restrictions apply. where the virtual machine itself uses a remote NFS share as backing store. after which packets and frames are dropped.20 Release Notes . see the HP Integrity Virtual Machines 4. and Administration guide at http://www.• • • • • • • 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 .1 1. it is now possible to create a Multi-Node 1 Package that uses an NFS file share. IMPORTANT: Find out the MBTD value for each affected router and switch from the vendors' documentation. see the discussion of this parameter under “Cluster Configuration Parameters” in chapter 4 of Managing Serviceguard.1 1. For instructions. Switches and routers that do not support MBTD value must not be used in a Serviceguard NFS configuration. and use the resulting value to set the Serviceguard CONFIGURED_IO_TIMEOUT_EXTENSION parameter.1 1. • • NFS mounts are supported for modular.20 (April 201 patch). For details on how to configure NFS as a backing store for HPVM. This timeout is known as the Maximum Bridge Transit Delay (MBTD). This might lead to delayed packets that in turn could lead to data corruption. ask your HP Sales Representative for details. With Serviceguard A. all the network switches and routers between the NFS server and client must support a worst-case timeout.rhosts and /var/admin/inetd. Configuration. find the worst case sum of the MBTD values on these paths.20.hp. you can use NFS-mounted (imported) file systems as shared storage in packages. 22 Serviceguard Version A. and can use both cluster-local shared storage and NFS imports. available for purchase. • Networking among the Serviceguard nodes must be configured in such a way that a single failure in the network does not cause a package failure. determine all of the possible paths. The same package can mount more than one NFS-imported file system.3: Installation. See chapter 6 of Managing Serviceguard for a discussion of types of packages.com/ go/virtualization-manuals —> HP Integrity Virtual Machines and Online VM Migration. failover packages. ccmon is a separate product. and this is useful only if you want to create a HP Integrity Virtual Machine (HPVM) in a Serviceguard Package. see the NFS Services Administrator's Guide HP-UX 1 version 3 at 1i http://www.hp. in chapter 6 of Managing Serviceguard. See also the description of the new parameter fs_server.20 on HP-UX 1 v3 which you can find at http://www. you should take the following precautions to ensure that data is not accidentally overwritten. An NFS file system should not be mounted on more than one mount point at the same time. • CacheFS and AutoFS should be disabled on all nodes configured to run a package that uses NFS mounts. The only exception to this restriction is when you want to use the NFS file system as a backing store for HPVM. Server-side locks are not supported. it should be mounted only as part of the startup for the package that uses it. 1i This paper includes instructions for setting up a sample package that uses an NFS-imported filesystem. For more information. do not attempt to restart it manually until you have verified that the file system has been unmounted properly. the file system should be used exclusively by the package. In this case. Because exclusive activation is not available for NFS-imported file systems. Access to an NFS file system used by a package should be restricted to the nodes that can run the package. • HP recommends that you avoid a single point of failure by ensuring that the NFS server is highly available. If storage is directly connected to all the cluster nodes and shared. The same NFS file system should be used by only one package. otherwise package startup may fail. For more information. see the white paper Using NFS as a file system type with Serviceguard 1 1.com/go/hpux-serviceguard-docs. the NFS file system is configured as the filesystem type in a multi-node package and is imported on more than one node in the cluster. you should observe the following guidelines. ◦ ◦ ◦ ◦ In addition. the applications using the imported file system may hang and it may not be possible to kill them. NOTE: If network connectivity to the NFS Server is lost.• • Only NFS client-side locks (local locks) are supported. configure it as a local filesystem rather than using NFS. and of fs_type and the other filesystem-related package parameters. The NFS file system used by a package must not be imported by any other system. While the package is running. it may not halt successfully • • • • Do not use the automounter. including other nodes in the cluster. ◦ ◦ The server should be configured so that only the cluster nodes have access to the file system. What’s in this Release 23 . If the package attempts to halt at this point. If the package fails. The nodes should not mount the file system on boot.hp.com/go/hpux-networking-docs. and is still supported.20. or logical volumes managed by HP-UX Logical Volume Manager (LVM).20 is supported from the September 2010 patch (PHSS_41225) and later. The VxVM monitoring capability (cmvxserviced) was first introduced in a patch to A. see “About the Volume Monitor” in chapter 4 of Managing Serviceguard. You can use this monitor is an alternative to using Event Monitoring Service (EMS) resource dependencies to monitor LVM storage. For this reason.1 1. The LVM and VxVM Volume Monitor Simply monitoring each physical disk in a Serviceguard cluster does not provide adequate monitoring for volumes managed by Veritas Volume Manager from Symantec (VxVM). The HP Serviceguard Manager Main Page provides you with a summary of the health of the cluster including the status of each node and its packages. 24 Serviceguard Version A. because a physical volume failure is not always a critical failure that triggers failover (for example. Instead. DSAU Integration HP Serviceguard Manager uses Distributed Systems Administration Utilities (DSAU) to display consolidated cluster log (syslog) and consolidated package logs.10 is a web-based.1 1. this in turn may affect your programs and scripts that parse cmviewcl -f line output.20 Release Notes .NOTE: The addition of the fs_server package parameter alters the output of cmviewcl -f line. For more information. EMS does not currently provide a monitor for VxVM volumes. Although cmvxserviced will still work in A. You can find more information on DSAU in the Distributed Systems Administration Utilities User’s Guide. at the address given under “Documents for This Version” (page 34). IMPORTANT: • • • The LVM monitoring capability (cmvolmond) for Serviceguard A. using your browser. HP System Management Homepage (HP SMH) tool. cmvolmond replaces cmvxserviced. you log into an HP Systems Management Homepage (SMH) and access the HP Serviceguard Manager tool.1 1.18. Serviceguard Manager HP Serviceguard Manager B. administer and configure a Serviceguard cluster from any system with a supported web browser. 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. combining the VxVM monitoring capabilities of cmvxserviced with the new capabilities needed to support LVM monitoring. HP recommends you use cmvolmond instead. Serviceguard Manager allows you to monitor. that replaces the functionality of the earlier Serviceguard management tools. at the address given under “Documents for This Version” (page 34). Serviceguard Manager does not require additional software installation.03. as well as other system management tools. the failure of a mirrored volume is not considered critical).1 1. including configuring package dependencies. halt. create. You can also modify Auto Run and Node Switching settings. Monitor.03. modify. multi-node. Monitor. run. and system multi-node packages. Native Language Support HP Serviceguard Manager Version B. Serviceguard Manager 25 . Create and modify failover and multi-node packages. run. run.10 is available in the following languages: • • • • • • • • Japanese Simplified Chinese Korean Traditional Chinese Standard French Standard German Standard Italian Standard Spanish What You Can Do Depending on your SMH and Serviceguard security privileges. you can do the following: • • • • Monitor. and halt a cluster. you can setup a remote log consolidation server on the Quorum Server node or cluster.NOTE: DSAU does not support a local log consolidation server in a cross-subnet cluster. and halt nodes. Instead. and move failover. an alert is displayed when a package fails and manual intervention is required to start the package in the same site or another site. • Support for Serviceguard Extension for Oracle E-business Suite Toolkit B.02. you will have the option to deploy a CFS cluster. Support for Site Controller Package configuration. then you will be informed of the results.1 1.New Features HP Serviceguard Manager version B. 26 Serviceguard Version A. from the Toolkits configuration page for more information on it and its parameters. Support for moving the Site Controller package within site and across site.20 on HP-UX 1 v3. SG-CFS-pkg. • Support for SG-CFS-pkg (SMNP) Configuration ◦ Configure the SMNP package. • Easy deployment of CFS Cluster (SG-CFS-pkg SMNP package) ◦ If the appropriate SG SMS bundle is found to be installed.1 1. • Support for Serviceguard Toolkit for Oracle Data Guard B. The SG-CFS-pkg (SMNP) will be automatically created. to get the latest information on the progress of the commands as well as for better troubleshooting. administration and monitoring of modular packages with Serviceguard toolkits for Oracle Data Guard and ECMT Oracle/SGeRAC. The 1i following are new capabilities in B. • Single-click Access to Package Logs ◦ Launch a Package log window from the Operation log window for each of the packages involved in a particular Administration operation. the network configuration will be analyzed to determine if the cluster that is being deployed is a candidate SGeRAC cluster.03.10 supports Serviceguard A. for CVM/CFS environments.03. • SGeRAC Cluster Easy Deployment ◦ If the SGeRAC bundle is found to be installed during cluster configuration. • Support for Co-existence of SGeRAC with ECMT ◦ Support for Oracle RAC (SGeRAC toolkit) packages to co-exist with Oracle Single instance (ECMT Oracle toolkit) packages in the same Serviceguard cluster. • Support to open Toolkit README files ◦ Open the README file for any installed toolkit. • Run cDSF while adding new node ◦ To allow users to run the cDSF command while adding a new node to the cluster to have uniform cDSF names in the cluster. Monitoring and Administration Support for the new Serviceguard Extension for Oracle E-business Suite (SGeEBS) Toolkit.20 Release Notes . Manual Site switching Enhancement ◦ If the failover policy is SITE_PREFERRED_MANUAL.01.00 and the April 201 Patch 1 (PHSS_41640) or later ◦ Support for configuration.10: • Support for Site-aware Metrocluster Configuration (Site Aware Cluster + Site Controller package) ◦ ◦ ◦ • Support for configuration of sites to form a site-aware Cluster.00 ◦ Configuration. com/go/hpux-serviceguard-docs —> HP Serviceguard —> White papers. See the following excerpt from Firefox support site (http://support.mozilla. Metrocluster Easy Deployment (SiteAware + NonSiteAware) ◦ If the appropriate Metrocluster. • NFS Toolkit Enhancement ◦ • A new parameter "SUPPORTED_NETIDS" is added in the Serviceguard Manager GUI on HA NFS toolkit.0 does not provide an API that Serviceguard Manager can use to detect or alter this behavior. and SGeRAC bundles are found to be installed. the Serviceguard Manager logging windows are launched with a pre-specified window size that will not obscure the original window when they are displayed. There is no workaround for this problem at this time. • Package Easy Deployment Effortlessly deploy the following modular packages with minimal user input and automatic package dependency configuration: ◦ ◦ ◦ ◦ ◦ SGeRAC OC Toolkit package easy deployment SGeRAC RAC DB Toolkit package easy deployment ECMT Oracle Toolkit package easy deployment SGeEBS Toolkit package easy deployment Site Controller package easy deployment For more information. SMS. Firefox 3. if a new window has a specified size. Serviceguard Manager 27 . see the white paper Using Easy Deployment in Serviceguard and Metrocluster environments at http://www. With the Firefox tabbed browsing preference selected. Browser and SMH Issues Pages Launched into New Window rather than Tabs with Firefox Tabbed Browsing By design. SGeRAC ASM disk group package Enhancements ◦ Displays actual values in the SGeRAC RAC database and ASM disk group packages property sheet.• • Cluster Verification for Metrocluster ◦ An enhancement to the existing cluster verification feature for Metrocluster specific checks. because some pages can only be displayed correctly at a specific size. you will be given options for configuring a site aware Metrocluster with minimal steps. These parameters are removed from the configuration page display since the user need not enter values. • Modular CFS Package Integration (Multiple CVM Disk Groups and CFS Mount Points) ◦ You can merge multiple CVM Disk Group (DG) and CFS Mount Point (MP) packages that are needed for a single application Current Limitations of Serviceguard Manager You can only monitor a Continentalcluster. but cannot configure or administer it.com/en-US/kb/ Options+window+-+Tabs+panel): Note: If you have chosen to open pages in new tabs. the tabbed browsing preference is ignored and the target page is launched in a new window instead. 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.hp. <x>.1 1. Internet Explorer 8 fixed most of these problems and behaves in the same way as Firefox 3. Once Serviceguard Manager is running. Serviceguard Manager information will not be loaded correctly into the HPSMH.10 installed. for HP–UX 1 v3. Before Using HP Serviceguard Manager: Setting Up You must have.5. as it explains HP Serviceguard Manager Access Control Policies. Have launched SMH (settings -> Security -> User Groups) to configure user roles for SMH. You can also access the online help by clicking the button located in the upper-right hand corner of the screen to view overview and procedure information. as well as root privileges. ◦ • See the online help topic “About Security” for more information.1 1. ◦ ◦ A user with HP SMH Administrator access has full cluster management capabilities. Serviceguard commands may take longer than 30 seconds to return.0 UI timeout value is left at its default value (20 seconds).0. See “Configuring Root-Level Access” in Chapter 5 of the Managing Serviceguard manual for instructions. A user with HP SMH User access does not have any cluster management capabilities. You should read the help topic About Security. of SMH (System Management Homepage).x. use a command such as: swlist -l fileset | grep TOMCAT • • • Version A.0 (5. Java JDK 5.Internet Explorer 7 Zooming Problem Internet Explorer 7 introduced a "zoom" feature which allows the user to zoom in/out the page being viewed.03. However.0 or higher) with access to SMH.3. use the tooltips by moving your mouse over a field from the read-only property pages for a brief definition for each field. As a result. Start with the help topic Understanding the HP Serviceguard Manager Main Page. or have done.0 or higher or Firefox 2.20 Release Notes . if the HPSMH 3.20 and Serviceguard Manager B. Help Subsystem Use this section to help you become familiar with Serviceguard Manager. HTML elements in a page are not zoomed proportionally. HP System Management Homepage (HPSMH) Timeout Default In some situations (for example. the resulting page is displayed in a unpredictable manner.1.5. or a higher version of A. Have created the security “bootstrap” file cmclnodelist.16 or later) Version B. 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. when a remote cluster node is disconnected from the network).0.3. To check that it is on your system. the following before you can start using HP Serviceguard Manager: • • • At least one cluster member node with Serviceguard A. hpuxswTOMCAT is installed by default with HP-UX.23. increase the UI timeout value to 60 seconds (Settings -> Security -> Timeouts -> UI timeout).0. To ensure Serviceguard Manager has sufficient time to execute Serviceguard commands. its implementation is known to have problems.02 or later of the hpuxswTOMCAT product. In this case. 1i A web browser (Internet Explorer 6. 28 Serviceguard Version A. 19. See “Maintaining a Package: Maintenance Mode” in chapter 7 of Managing Serviceguard.1 1. see “Known Problems for Serviceguard Manager” (page 54). See cmgetconf (1m) for more information. Features First Introduced in Serviceguard A. • • Support for CFS.Launching Serviceguard Manager See Appendix I of Managing Serviceguard. at the address given under “Documents for This Version” (page 34). Support for Dynamic Root Disk (DRD) on HP-UX 1 v3. • Support for Shared LVM (SLVM) in an HPVM environment only — that is. VxVM and CVM version 5. Patches and Fixes No patches are required for Serviceguard Manager B. New -K option for cmgetconf.10. IPv6-Only. Configuration. This causes cmgetconf to skip probing of volume groups.com/go/hpux-hpvm-docs. • • • • Improved support for online package maintenance. • Improved support for nested mount points. New Serviceguard Manager capabilities. see HP Integrity Virtual Machines Installation.) See also: • • “About LVM 2.20. 1i Improved support for IPv6. (In earlier releases. including support for IPv6–only hosts. 1i See “Upgrade Using DRD” (page 44). See the section “About Hostname Address Families: IPv4-Only. Serviceguard now ensures that a package will never attempt to mount a nested directory concurrently with the parent. see “Serviceguard Manager” (page 24). no matter what concurrent_mount_and_umount_operations is set to.19 Patches Listed below are features originally introduced in patches to Serviceguard version A.1 1. for instructions on launching Serviceguard Manager. For information about known problems and workarounds. when the cluster includes virtual machines (either as nodes or within packages) that are managed by HPVM. and other useful information. allowing the command to complete faster.hp. and Mixed Mode” in chapter 4 of Managing Serviceguard. For more information about using HPVM in a Serviceguard cluster.1 1.03. the resulting cluster configuration file will not contain a list of cluster-aware volume groups.20 The following subsections discuss important features that were added to Serviceguard in recent releases and patches. and Administration at http://www.1 1.20 29 .x” (page 30) “Serviceguard on HP-UX 1 v3” (page 14) 1i Features Introduced Before A. see “Support for HP Integrity Virtual Machines (HPVM)” (page 33). at the address listed under “Documents for This Version” (page 34). For more information.1 on HP-UX 1 v3 only. All of these features have been carried forward into A.1 1. Features Introduced Before A.0. this could happen if concurrent_mount_and_umount_operations was set to a value greater than 1. 19 About olrad You must remove a LAN or VLAN interface from the cluster configuration before removing it from the system.19. and mirror copies of logical volumes are synchronized in parallel. this affects the way physical volumes are activated within a volume group. About vgchange -T Serviceguard supports vgchange -T. physical volumes (disks or LUNs) are attached to the volume group in parallel. (It was also provided in a patch to Serviceguard A. 1i This means that when the volume group is activated. IMPORTANT: Make sure you read the configuration file comments for both concurrent_vgchange_operations and enable_threaded_vgchange before configuring these options.03. which remove some of the limitations imposed by LVM 1.Features First Introduced Before Serviceguard A. After removing the NIC from the cluster configuration. If the NIC is part of the cluster configuration. meaning that multi-threaded activation is disabled).20 Release Notes . controls how many volume groups the package can activate simultaneously. Note that.04.1 1. See “Removing a LAN or VLAN Interface from a Node” in Chapter 7 of Managing Serviceguard for more information.1 1.hp. you’ll see a warning message telling you to remove it from the configuration before you proceed.20 allows you to configure an alternate subnet for communication between the cluster nodes and the Quorum Server. can be used on systems running HP-UX 1 v3 0803 Fusion or later 1i 30 Serviceguard Version A. IMPORTANT: This capability requires Quorum Server Version A. HP-UX 1 v3 provides a new option for the olrad command. see the HP Serviceguard Quorum Server Version A.1 1. but Quorum Server Version A. About LVM 2.0 volume groups.) See “Quorum Server Upgrade Required if You Are Using an Alternate Address” (page 9). you can remove it from an HP-UX 1 v3 1i cluster node without shutting down the system by running olrad -d. set enable_threaded_vgchange to 1 in the package configuration file (the default is 0. olrad -C. to help you determine 1i whether or not an interface is part of the cluster configuration: run olrad -C with the affected I/O slot ID as argument. About the Alternate Quorum Server Subnet Serviceguard A.com/go/hpux-serviceguard-docs —> HP Serviceguard Quorum Server Software.20 or A.00 does not support an alternate subnet with Serviceguard A. which allows multi-threaded activation of volume groups on HP-UX 1 v3 systems. as well as the vgchange (1m) manpage.x Logical Volume Manager (LVM) 2.00. For details and instructions.03.1 1.04. rather than serially.1 1. That can improve a package’s startup performance if its volume groups contain a large number of physical volumes. concurrent_vgchange_operations.1 1. in the context of a Serviceguard package.x volume groups.00 Release Notes at http://www. See the olrad(1M) manpage for more information about olrad. another package parameter. You can do this from the command line or in Serviceguard Manager.18 with Quorum Server Version A.00. You can do this without bringing down the cluster. To enable vgchange -T for all of a package’s volume groups. For information about all other aspects of LVM on HP-UX 1 1i v3. For information about HPVM. cmappmgr is operating-system-independent.) cmappmgr is packaged as a Serviceguard command. cmappserver.java.1=-Dos. new options are available for some commands.1 Release Notes.com/go/hpux-core-docs. see the white paper LVM 2.com/go/hpux-hpvm-docs. See “Support for HP Integrity Virtual Machines (HPVM)” (page 33). See the latest version of the HP Integrity Virtual Machines Version 4. although you may have to make minor changes to any scripts you use that parse the output of lvdisplay. see the Logical Volume Management volume (volume 3) of the HP-UX System Administrator’s Guide. About cmappmgr cmappmgr is an utility that allows you launch and monitor processes on HP Virtual Machine (HPVM) guest nodes.1 1. HPVM 4.1 July patches. and you can use cmappmgr to monitor processes on these guests. as the output of these commands has changed slightly.19 or later.) NOTE: You are not required to move to LVM 2.additional.hp. or exe (for HP-UX.hp.bat Features Introduced Before A.with LVM version B.1 1.18. cmappmgr on the host communicates via SSL connections with a lightweight module on the VM guest.0 Volume Groups in HP-UX 1 v3 at http:// 1i www. which you can find at the address given under “Documents for This Version” (page 34). For more information. and Windows VMs. Linux. If you do use LVM 2.additional.20 31 .1 1.0809 and Serviceguard A. • • Install the Windows 2008 guest operating system on the host.name=C:\Program Files\Hewlett-Packard\cmappserver\cmappserver.1=-Dprogram. pvdisplay or vgscan. you can still manage them with the same commands as before.1 supports Windows 2008 guests. at the same address. or Windows respectively) which can be copied from the host to a VM guest and installed there.name="Windows 2003" This should go after the following lines: #Java Additional Parameters #wrapper. which you can find on http://www.31. For more information see the white paper Designing High Availability Solutions with HP Serviceguard and HP Integrity Virtual Machines.x volume groups and everything will work as before if you do nothing. Linux. or invoked from an external script in a modular package or from a run and halt script in a legacy package. edit C:\Program Files\Hewlett-Packard\cmappserver\conf\wrapper. rpm.1 1. To enable this capability you need to do the following: • Install the HPVM 4.java. cmappserver is packaged as a depot.1 Support for Windows 2008 Guests HPVM 4. It can be run as a service in a Serviceguard package.x volume groups. (See Chapter 6 of Managing Serviceguard for information about modular and legacy packages.conf on the Windows 2008 guest to insert the following line: wrapper. vgdisplay. cmappmgr exits when the process that is being monitored does. supporting HP-UX. In addition. (This support was first introduced in a patch to Serviceguard A. that does not need to change when the hardware path does. In this case. 1i 32 Serviceguard Version A. For example. by default the installation process will configure system devices such as the boot. 1i though you should seriously consider its advantages (see the white paper The Next Generation Mass Storage Stack which you can find at http://www. Under the agile addressing convention. if necessary. for example /dev/[r]disk/disk3. For more information about agile addressing. Agile addressing is the default on new 1 v3 installations.hp.About Device Special Files (DSFs) HP-UX releases up to and including 1 v2 use a naming convention for device files that encodes 1i their hardware path. instead.1 1. but the existing.hp. 1i If you cold-install HP-UX 1 v3. and dump devices to use persistent device files. the process is described in the white paper LVM Migration from Legacy to Agile Naming Model HP-UX 1 v3 at http://www. a set of new. CAUTION: You cannot migrate to the agile addressing scheme during a rolling upgrade if you are using cluster lock disks as a tie-breaker. swap. When you upgrade to HP-UX 1 v3. Device files using 1i 1i the new nomenclature are called persistent device files.com/go/hpux-core-docs. though not a best practice. HP-UX 1 v3 introduces a new nomenclature for device files. For the requirements and a procedure. to use legacy DSFs on some nodes after migrating to agile addressing on others. but the I/O subsystem still recognizes 1i pre-1 v3 device files. This means that you are not required to migrate to agile addressing when you upgrade to 1 v3. the hardware path name is no longer encoded in a storage device’s name. see “Updating the Cluster Lock Configuration” in Chapter 7 of Managing Serviceguard. each device file name reflects a unique instance number.20 Release Notes .com/ go/hpux-core-docs: • • • the Logical Volume Management volume of the HP-UX System Administrator’s Guide the HP-UX 1 v3 Installation and Update Guide 1i the following white papers: ◦ ◦ ◦ The Next Generation Mass Storage Stack HP-UX 1 v3 Native Multi-Pathing for Mass Storage 1i LVM Migration from Legacy to Agile Naming Model HP-UX 1 v3 1i See also the HP-UX 1 v3 intro(7) manpage. this allows you to migrate different nodes at different times. but Serviceguard’s functioning will not be affected by this. which as of 1 v3 are referred to as legacy device files. sets of both legacy and persistent device files are automatically 1i created. see following documents at http://www. But you can migrate the cluster lock device file names to the new scheme without bringing the cluster down. SCSI target 15.hp. persistent device files is created. root. known as agile addressing (sometimes 1i also called persistent LUN binding). Migration involves modifying system and application configuration files and scripts to use persistent device files and in some cases new commands and options. This means that system configuration files such as/etc/fstab and /etc/lvmtab will contain references to persistent device files. NOTE: It is possible. 1i legacy device files are left intact and by default will continue to be used by HP-UX and Serviceguard. because that involves changing the cluster configuration. a device file named /dev/dsk/c3t15d0 would indicate SCSI controller instance 3.com/go/hpux-core-docs —> Overview: The Next Generation Mass Storage Stack ). and SCSI LUN 0. For more information about Access Control Policies.hp. it will take about 1 seconds. if the cluster typically took 40 seconds to re-form before any VM nodes were added. and Administration at http://www.1 1. (See HP Integrity Virtual Machines Installation. at the address given below. it will take about 80 seconds when one or more VM nodes are members of the cluster. About HPVM and Cluster Re-formation Time When a node fails and the cluster re-forms. and Administration. if all those nodes have a VM guest depot. For example. IMPORTANT: For the most up-to-date compatibility information. to authenticate users. whether or not the re-formation is caused by the failure of a VM node. This additional wait can increase cluster re-formation time by as much as 70 seconds. Features Introduced Before A.) Serviceguard uses information it derives from the VM guest depot to set the timeout to the optimal value. This is true whenever VM nodes are 10 cluster members. rather than cmclnodelist or . As of A. The amount of time Serviceguard waits is calculated by Serviceguard and is not user-configurable. HPVM runs only on HP Integrity systems.16 Serviceguard version A.1 1. the amount of time Serviceguard needs to wait for a failed node’s I/O to complete increases.1 1. For more information about HP Integrity Virtual Machines. The additional time Serviceguard needs to wait depends in part on whether or not a VM guest depot is installed on the VM node. the Serviceguard Manager help.com/go/hpux-hpvm-docs. If any VM node without a VM guest depot is a member of the cluster. see Chapter 5 of the Managing Serviceguard manual. Configuration. see “About HPVM and Cluster Re-formation Time” (page 33).rhosts. If any VM node does not have a VM guest depot.hp. see the Serviceguard/SGeRAC/SMS/Serviceguard Mgr Plug-in Compatibility and Feature Matrix. for information on installing a guest depot. Configuration. and the cluster and package configuration files themselves. IMPORTANT: This additional timeout extension represents a net addition to the time it takes for the cluster to re-form. Serviceguard A. See also the “Integrity VM/Serviceguard Support Matrix” in the white paper Designing high-availability solutions with HP Serviceguard and HP Integrity Virtual Machines on the same web page under White papers. but using VMs as Serviceguard nodes increases the amount of time Serviceguard needs to wait before it is safe to allow another node access to the same storage. Access changes as of A. 70 seconds. Serviceguard may not be able to obtain the information it needs to set the optimal timeout. see HP Integrity Virtual Machines Installation. 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.16. The above is true whether or not the cluster includes virtual machines (VMs). it does not run on HP 9000 systems.1 1.Support for HP Integrity Virtual Machines (HPVM) Serviceguard supports HP Integrity Virtual Machines (HPVM). Only after that time has elapsed can Serviceguard allow an adoptive node access to that device.20 33 . If any Serviceguard cluster node is a virtual machine. otherwise data corruption could occur. and in that case it sets the additional timeout to the maximum value. also known as Role-Based Access. Serviceguard uses Access Control Policies. at http://www. under the heading General reference. See also “About cmappmgr” (page 31).20 supports an HPVM either as a package or as a cluster node.1 1.com/go/hpux-serviceguard-docs —> HP Serviceguard.16 introduced a new access method. 20 Release Notes Using Serviceguard Extension for RAC Understanding and Designing Serviceguard Disaster Tolerant Architectures Designing Disaster Tolerant HA Clusters Using Metrocluster and Continentalclusters Enterprise Cluster Master Toolkit Version Release Notes Serviceguard/SGeRAC/SMS/Serviceguard Mgr Plug-in Compatibility and Feature Matrix.com/go/hpux-serviceguard-docs —> HP Serviceguard.com/go/ hpux-serviceguard-docs. For information on the Distributed Systems Administration Utilities (DSAU). The following documents.rhosts for access in the previous version of the cluster.1 1. you want to be sure it applies the newly migrated Access Control Policies. • cmclnodelist When you upgrade from an earlier version. you must now configure Access Control Policies for the cluster users. This manual has been revised for the current A.1 1. Securing Serviceguard and other Serviceguard white papers.Considerations when Upgrading Serviceguard • .04. see the latest version of the Distributed Systems Administration Utilities Release Notes and the Distributed Systems 34 Serviceguard Version A. the node is not yet part of a cluster. For instructions on how to proceed.rhosts If you relied on . see the subsection “Allowing Root Access to an Unconfigured Node” under “Configuring Root-Level Access” in Chapter 5 of the Managing Serviceguard manual. Considerations when Installing Serviceguard When you install Serviceguard for the first time on a node. If you do a cmapplyconf.hp. use cmgetconf to create and save a copy of the new configuration. For instructions on how to proceed. and about older versions.00 Release Notes Serviceguard Extension for RAC Version A. • • • • • • • • • Managing Serviceguard Nineteenth Edition.20 Release Notes . and so there is no Access Control Policy. see the Serviceguard documents posted at http://www. 1 HP Serviceguard Quorum Server Version A. Serviceguard converts cmclnodelist entries into new entries written into the cluster configuration file during the upgrade. as follows: USER_NAME <user_name> USER_HOST <host_node> USER_ROLE Monitor A wildcard + (plus) is converted as follows: USER_NAME ANY_USER USER_HOST ANY_SERVICEGUARD_NODE USER_ROLE Monitor After you complete the upgrade.1 1.hp. Documents for This Version For information about the current version of Serviceguard. see the subsection “Allowing Root Access to an Unconfigured Node” under “Configuring Root-Level Access” in Chapter 5 of the Managing Serviceguard manual. are particularly useful. which can all be found at http://www.20 April 201 Patch release. The latest version of HP-UX VLAN Administrator's Guide and other VLAN documentation at http://www.hp. Mixed Clusters “Mixed cluster” has several meanings in the context of Serviceguard. but no cluster configuration changes are allowed.hp. during which Serviceguard versions can be mixed temporarily. This multi-volume manual replaces Managing Systems and Workgroups as of HP-UX 1 v3.com (Europe) 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.com/go/hpux-ha-monitoring-docs —> HP Event Monitoring Service: • • 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 for download at http://www.com (Americas and Asia Pacific) http://europe-support.com/go/hpux-core-docs: go to the HP-UX 11i v3 collection and scroll down to Getting started.hp.com/go/hpux-serviceguard-docs.com/go/hpux-networking-docs —> HP-UX 11i v3 Networking Software.hp.hp.hp. Further Information 35 . see the following documents at http:// www.hp.com/go/softwaredepot -> High Availability Online versions of user’s guides and white papers are available at: http://www.external.com/go/hpux-networking-docs —> HP-UX 11i v3 Networking Software.external.hp. The sole exception to this rule is a rolling upgrade.com/go/hpux-serviceguard-docs Support tools and information are available from the Hewlett-Packard IT Resource Centers: http://us-support.hp.hp.com/go/hpux-core-docs. Other relevant HP-UX documentation includes: • HP-UX System Administrator’s Guide at http://www. The following are support statements for various types of mixed cluster. • • The latest HP Auto Port Aggregation Release Notes and other APA documentation at http:// www. all nodes must be running the same version of Serviceguard.hp. Further Information Additional information about Serviceguard and related high availability topics can be found at: http://www. 1i For information about the organization of the set.com/go/softwaredepot -> High Availability. see the Preface to the Overview volume. For information about the Event Monitoring Service. See “Upgrading from an Earlier Serviceguard Release” (page 43) . Mixed Serviceguard Versions You cannot mix Serviceguard versions in the same cluster. and Appendix D of Managing Serviceguard. at the address given under “Documents for This Version” (page 34).Administration Utilities User’s Guide at http://www. such as 1 v2. consisting of HP 9000 and Integrity servers. see Configuration Rules for a Mixed HP 9000 /Integrity Serviceguard Cluster at http://www. You may want to take advantage of this fact when preparing to upgrade the cluster to A. Serviceguard supports mixed-hardware-architecture clusters.1 1i 1. The cluster cannot use Oracle RAC. 1i ◦ ◦ ◦ ◦ • • The same version of Serviceguard The same version of any volume manager or file system that is independent of HP-UX The same patch level for LVM and SLVM The same patch level for HP-UX. A mix of HP-UX 1 v2 and 1 v3 nodes 1i 1i is also allowed.1 1. and heterogeneous clusters. but entails some restrictions.1 1. The following restrictions apply: • Except during a rolling upgrade.hp. HP strongly recommends that all nodes be running: All applications running in the cluster must adhere to the vendor’s requirements for mixed Integrity and HP 9000 environments. (SGeRAC is not supported in a mixed-hardware-architecture cluster because Oracle RAC does not support mixing hardware architectures within a single RAC cluster. see “Mixed HP-UX Operating-System Revisions” (page 36).1 1. clusters in transition.16. 1 v2 September 2004 and 1 v2 September 2006). 36 Serviceguard Version A.19 cluster can contain a mix of nodes running HP-UX 1 v2 and 1 v3. Serviceguard. It is acceptable 1i to have a mix of different HP-UX Fusion releases for the same major revision (for example. and volume managers and related subsystems (for example Veritas VxVM. as Serviceguard clusters in which the server hardware is of a single type. 1i 1i with certain restrictions.1 1.com/go/hpux-serviceguard-docs.20 Release Notes .) For more information about mixed-hardware-architecture clusters. although it is generally best to 1i 1i have all nodes running the same Fusion release. Mixed HP-UX Operating-System Revisions A Serviceguard A. all nodes must be running: ◦ The same HP-UX version NOTE: HP-UX version in this context means major release. Keep in mind that Serviceguard A. 1i For the purposes of this discussion we'll identify three broad cases: homogeneous clusters. Mixed-hardware-architecture clusters support the same volume managers.Mixed Hardware Architecture As of HP-UX 1 v2 Update 2 (0409) and Serviceguard A.20. see in particular “Rules and Restrictions for Clusters in Transition” (page 37) and “Rules and Restrictions for Heterogeneous Clusters” (page 38).1 1.20 is supported only on HP-UX 1 v3. IMPORTANT: Serviceguard A. at the same version level. and VxFS) and in addition.20 is supported only on HP-UX 1 v3. 1 1. It is also possible to upgrade the HP-UX version without upgrading Serviceguard. Cluster in transition refers to a cluster whose HP-UX version is being upgraded as part of a normal rolling upgrade that occurs over a relatively short period. you may decide to 1i upgrade the nodes to HP–UX 1 v3 over a period of time. If you install Serviceguard at a patch level lower than the one the cluster was running. even though the 1i 1i Serviceguard version is the same. “version” in this subsection means HP-UX version.1 1. and so avoid the rolling upgrade restrictions. which you can find at the address given under “Documents for This Version” (page 34). not Serviceguard version. 1 v2 September 2004 and 1 v2 September 2006). you will need to re-install the higher-level patch on all nodes before you can use its features again. It is acceptable to have a mix of different HP-UX Fusion releases for the same 1i 1i major revision (for example. Heterogeneous cluster refers to a cluster that contains a mix of nodes running HP-UX 1 v2 1i and 1 v3. 1i 1i Unless explicitly stated otherwise. HP Recommendation for Homogeneous Clusters • • All nodes should be running the same major HP-UX version. 1i Rules and Restrictions for Clusters in Transition You can upgrade a cluster from HP-UX 1 v2 to 1 v3 as part of a rolling upgrade. and which has no need to include nodes running different major versions of HP-UX. and restrictions for rolling upgrades are in Appendix D of Managing Serviceguard. the discussion refers to mixing HP-UX versions 1 v2 and 1 v3.1 1. See also “Upgrading from an Earlier Serviceguard Release” (page 43). Major version means a release such as 1 v2 or 1 v3. and then upgrade the cluster to 1i Serviceguard A.) Compatibility Information and Installation Requirements 37 . See “Rules and Restrictions for Heterogeneous Clusters” (page 38).20. 1i 1i or for some other reason needs to accommodate nodes running both versions of HP-UX. 1i Such a cluster is either being upgraded from HP-UX 1 v2 to 1 v3 over an extended period. In this case you must make sure that: • The Serviceguard version bundled with the HP-UX Operating Environment (OE) matches the version already installed. guidelines. • Homogeneous cluster refers to a cluster that is not being upgraded. CAUTION: You need to pay careful attention to the Serviceguard patch level as well as the Serviceguard version. • The Serviceguard product bundled with the HP-UX OE is installed along with the HP-UX filesets.NOTE: In all three cases. although it 1i 1i is generally best to have all nodes running the same Fusion release at the same patch level. Rules. See “Rules and Restrictions for Clusters in Transition” (page 37). and are planning 1i to upgrade to Serviceguard A.20 is supported only on HP-UX 1 v3.20. Serviceguard A. which runs only on HP-UX 1 v3. any new features introduced in the higher-level patch will cease to be available. if you are running Serviceguard A.1 1.19 on HP-UX 1 v2. For example. (The Serviceguard binary files differ between HP-UX 1 v2 and 1 v3. See “HP Recommendation for Homogeneous Clusters” (page 37). A rolling 1i 1i upgrade includes upgrading to a new version of Serviceguard. for example. which is enabled by default on HP-UX 1 v3. See also “Recommendations” (page 38). with the following restrictions. can be used on 1i 1 v3 nodes in a heterogeneous cluster. Rules and Restrictions for Heterogeneous Clusters IMPORTANT: Serviceguard A.1 1i 1. you may want to upgrade the nodes from 1 v2 to 1 v3 over time. 1i • The cluster must not be using Oracle RAC. 1i 1i A Serviceguard A. (SGeRAC is not supported in a heterogeneous cluster because Oracle RAC does not support mixing HP-UX versions within a single RAC cluster.1 1. NOTE: Native multipathing. all the nodes must be running Serviceguard A. 1i Except during a rolling upgrade of Serviceguard (see “Rules and Restrictions for Clusters in Transition” (page 37)). Agile addressing (see “About Device Special Files (DSFs)” (page 32) for more information about agile addressing). at the same patch level. • • • Recommendations In addition to the above Rules and Restrictions for Heterogeneous Clusters.19 installed. • Some HP–UX 1 v3 features must not be used as long as any nodes are running 1 v2.20. In preparation for an upgrade to Serviceguard A. or 1i 1i operating-system version (such as 1 v1) is permitted.x volume groups.NOTE: You can apply Serviceguard patches without doing a rolling upgrade.1 1. and the Serviceguard version bundled 1i 1i with the HP-UX Operating Environment (OE) is later than the one already installed.1 1. No other operating system. that is. the 1 v2 nodes should all be running the same 1 v2 Fusion 1i 1i 38 Serviceguard Version A. rolling upgrade restrictions apply (see “Rules and Restrictions for Clusters in Transition” (page 37)). 1i 1i These features specifically must not be used: ◦ ◦ LVM 2. HP strongly recommends the following: • All the nodes on a given HP-UX version should be running the same Fusion release. that before you can add a node running HP-UX 1 1i v3 to a cluster in which the existing nodes are running 1 v2.1 1.1 1i 1.1 1. so all cluster nodes 1i must be running 1 v3 before you can complete a rolling upgrade to A. The rules that follow provide guidance. all the 1 v2 nodes.20 Release Notes .20 is supported only on HP–UX 1 v3.19 cluster can accommodate a mix of nodes running HP-UX 1 v2 and 1 1i 1i v3. If you are updating nodes from HP–UX 1 v2 to 1 v3. IMPORTANT: This means. cold 1i 1i install is not supported in this context.) The cluster must not be using Veritas CVM or CFS. If you are updating nodes from HP–UX 1 v2 to 1 v3. must have Serviceguard A. • • Each node must be running either HP–UX 1 v2 or 1 v3.19. you must use update-ux.20. and the 1i 1i new 1 v3 node. IPFilter-Serviceguard rules are documented in the latest HP-UX IPFilter Administrator’s Guide. for example) are under /etc/opt/sec_mgmt/bastille/defaults/configs/. change SecureInetd. The ipf.release at the same patch level. depending on your environment. set MiscellaneousDaemons.config) level lock down.deactivate_ident=Y to SecureInetd.config.1 1. Keep in mind that Serviceguard A. which you can find under http://www. and the 1 v3 nodes should all be running the same 1 v3 1i 1i Fusion release at the same patch level. change SecureInetd.snmpd="N" If you are using the Serviceguard WBEM Provider. The files (host.pdf. see http:// h71028. set MiscellaneousDaemons.customrules file is located under the Bastille directory itself.block_wbem="N" (default) If you are using Serviceguard IP Monitoring. set MiscellaneousDaemons.config) level lock down.com/enterprise/downloads/External-SG-Storage6. set IPFilter. Bastille Compatibility To ensure compatibility between Serviceguard (and Serviceguard Manager) and Bastille. any new functionality introduced in the higher-level patch will cease to be available until that higher-level patch is installed on all nodes. including the local node. do the following.block_ping="N" (default) Add the following rules to ipf.deactivate_ident=N If you are using the Serviceguard SNMP subagent.deactivate_ident=N If you are using the Serviceguard SNMP subagent. set IPFilter.deactivate_ident=Y to SecureInetd.20 is supported only on HP-UX 1 v3. set MiscellaneousDaemons. • All nodes should be running the same patch levels for other products used by the cluster.hp. <clusternodes> are all nodes in the cluster. set IPFilter. • If Bastille is started using Sec10Host (host. 1i • All nodes should be at the same Serviceguard patch level. set IPFilter.www7.snmpd="N" • If Bastille is started using Sec20MngDMZ (mandmz.deactivate_ident=Y to SecureInetd. Compatibility with Storage Devices For the matrix of currently supported storage devices and volume managers.deactivate_ident="N" If you are using the Serviceguard SNMP subagent. CAUTION: If you introduce a node running a lower patch level than that of the existing nodes.config) level lock down.deactivate_ident=Y to SecureInetd.hp.snmpd="N" • If Bastille is started using Sec30DMZ (dmz. change SecureInetd.snmpd="N" If you are using the Serviceguard WBEM Provider.deactivate_ident=N If you are using the Serviceguard SNMP subagent.config. change SecureInetd.block_ping="N" (default) • If Bastille is started using SIM.block_wbem="N" (default) If you are using Serviceguard IP Monitoring.com/go/hpux-security-docs —> HP-UX IPFilter Software Compatibility Information and Installation Requirements 39 .customrules: 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 <clusternodes> to any pass out quick from any to <clusternodes> In the above rules. NOTE: Remember to tune the swap space and the HP-UX kernel parameters nfile.20 Release Notes .5 MB of lockable memory on each cluster node.1 1.20. See also the HP-UX Bastille User’s Guide installed on your system: /opt/sec_mgmt/bastille/ docs/user_guide. Memory Requirements Serviceguard needs approximately 15. check /etc/services and be sure no other program has reserved these ports. maxfiles and maxfiles_lim to ensure that they are set high enough for the number of packages you are configuring.hp.1 1.1 1. Before installing. see the latest version of the Security Management volume of the HP-UX System Administrator's Guide under http://www. Port Requirements Serviceguard uses the ports listed below. make sure your HP representative reviews the firmware levels of SCSI controller cards and installs the latest versions.com/go/hpux-core-docs. If the port 40 Serviceguard Version A. • • • • • • • • • • • • • • • • • • • • discard 9/udp snmp 161/udp snmp 162/udp clvm-cfg 1476/tcp hacl-qs 1238/tcp hacl-qs 1238/udp hacl-monitor 3542/tcp hacl-monitor 3542/udp hacl-hb 5300/tcp hacl-hb 5300/udp hacl-gs 5301/tcp hacl-gs 5301/udp hacl-cfg 5302/tcp hacl-cfg 5302/udp hacl-probe 5303/tcp hacl-probe 5303/udp hacl-local 5304/tcp hacl-local 5304/udp hacl-test 5305/tcp hacl-dlm 5408/tcp Serviceguard also uses port 9/udp discard during network probing setup when running configuration commands such as cmcheckconf or cmapplyconf and cmquerycl.20 Before you install Serviceguard A.txt. you need to make sure that your cluster has the correct hardware upgrades. Before Installing Serviceguard A.For information on how to configure HP-UX Bastille Sec10Host to allow the identd daemon to run. If you are upgrading older systems. They are part of the HP-UX Base Operating Environment: • • Open SSL.com/ go/hpux-security-docs —> HP-UX IPFilter Software. Installing Serviceguard Serviceguard will automatically be installed when you install an HP-UX Operating Environment that includes it (HAOE or DCOE). if port 1775 is already being used by another application. you must leave open the ports listed above and follow specific IPFilter rules required by Serviceguard. make sure the following ports are open in addition to the ports listed above: • • • • compaq-https 2381/tcp compaq-https 2381/udp cpq-wbem 2301/tcp cpq-wbem 2301/udp In addition. If you have adjusted the dynamic port range using ndd (1M) . which includes the OPENSSSL-RUN and OPENSSL-LIB filesets.network tuning.conf). alter your rules accordingly. if you are using DSAU consolidated logging and decide to use the TCP transport. The EventMonitoring bundle. Installing Serviceguard on HP-UX Dependencies The following are required by Serviceguard. available from http://www.65535) for some cluster services.hp. Ports Required by Serviceguard Manager If you will be using Serviceguard Manager via HPSMH. To install Serviceguard independently. these are documented in the latest version of the HP-UX IPFilter Administration Guide. System Firewalls When using a system firewall such as HP-UX IPFilter with Serviceguard. This port is configurable.is disabled (in inetd. follow these broad steps: Installing Serviceguard on HP-UX 41 . HP recommends you use TCP port 1775. Serviceguard also uses dynamic ports (typically in the range of 49152 . the network probing may be slower and under some conditions error messages may be written to syslog. configure and open another free port when you configure the firewall. which contains the EMS-CORE and EMS-CORE-COM filesets. see “Quorum Server Upgrade Required if You Are Using an Alternate Address” (page 9).CM-CVM-CFS Package-CVM-CFS.CM-PKG-MAN Cluster-Monitor. If not.SGPROV-CORE SGWBEMProviders.CM-MOF CM-Provider-MOF.SGPROV-MOF CM-Provider-MOF. Use the swinstall command to install Serviceguard.04.CM-OM-MAN Package-CVM-CFS. If you intend to use an alternate Quorum Server subnet “About the Alternate Quorum Server Subnet” (page 30). The filesets that make up the Serviceguard product are: • • • • • • • • • • • • • • • • • • • • • Serviceguard.CM-CORE Cluster-Monitor.CM-CORE-COM Cluster-Monitor.SGMGRPI SGWBEMProviders. you must upgrade the before you proceed.20 Release Notes .00.CAUTION: • This release of Serviceguard requires 1 v3. see the HP-UX Installation and Update Guide for the target release at http://www. For more information about swinstall. product number T1905CA. 2. Use the following command to display a list of all installed components: swlist -R T1905CA • 1.CM-CVM-CFS-COM Package-Manager.CM-DEN-PROV Cluster-OM.CM-CORE-MAN 42 Serviceguard Version A.CM-PROVIDER Cluster-OM. and the new cluster will use an existing Quorum Server.1 1.CM-PKG Package-Manager. Verify the installation. see “Upgrading from an Earlier Serviceguard Release” (page 43) for more information.SGPROV-DOC SGWBEMProviders.CM-DEN-MOF Cluster-OM.CM-OM Cluster-OM. Install or upgrade to HP-UX 1 v3 before loading Serviceguard Version A.CM-OM-AUTH-COM Cluster-OM.com/go/hpux-core-docs.1 1i 1. For information and instructions.hp.CM-OM-COM Cluster-OM.20. 1i 1i 3.CM-SG SGManagerPI. see the swinstall(1M) manpage and the Software Distributor Administration Guide for HP-UX 1 v2 or 1 v3.CM-OM-AUTH Cluster-OM. make sure you are running Quorum Server version A. If you are already running earlier versions of 1i Serviceguard and HP-UX. See “Rolling Upgrade” (page 46).20 from any earlier release (whether or not that release is still in support life).1 1. do it after installing Serviceguard but before each node rejoins the cluster (for example. the installation will proceed correctly. but you may see error or warning messages such as: Bad binary config file directory format. Upgrading from an Earlier Serviceguard Release You can upgrade to Serviceguard A. If you must disable identd. but you can perform a rolling upgrade only from A. under the heading “Disabling identd” in the section “Managing the Running Cluster”.pl /var/adm/cmcluster/frdump. alter. see Appendix D of Managing Serviceguard. Instructions are in Chapter 5 of the Managing Serviceguard manual. Do not change these files.NOTE: There are files in CM-CORE that are reserved for HP support.cmcld. For information about HP-UX upgrade 1i paths.20. or delete the following: • • • • • /usr/contrib/bin/cmcorefr /usr/contrib/bin/cmdumpfr /usr/contrib/bin/cmfmtfr /usr/contrib/Q4/lib/q4lib/cmfr. Read the bullets that follow carefully before proceeding.19. • This release of Serviceguard requires HP–UX 1 v3. as it maintains the integrity and high availability of your data.20.x (where x is a digit) NOTE: If you did a swremove of an older version of Serviceguard before the swinstall. In order to do a rolling upgrade to Serviceguard A. For more information about non-rolling upgrade. you must be running A. Remove this file before you issue the swinstall command. If You Need To Disable identd CAUTION: HP does not recommend disabling this security feature. This restriction does not apply to non-rolling upgrades.hp.1 1. which you can find at the address • Installing Serviceguard on HP-UX 43 . If you do not remove the zero-length binary configuration file.19 before attempting a rolling upgrade to A.1 1. just before issuing the cmrunnode or cmruncl command). Could not convert old binary configuration file. Do not move.com/go/ hpux-core-docs —> HP-UX 11i v3.1 1. see the HP-UX Installation and Upgrade Guide at http://www. upgrade to A. If you are running an earlier version. These messages may safely be ignored.1 1.19.1 1. a zero-length binary configuration file (/etc/cmcluster/cmclconfig) may be left on your system. This method is the least disruptive. follow the instructions under “Performing a Rolling Upgrade Using DRD” in Appendix D of the latest edition of Managing Serviceguard.00. you must upgrade to version A. upgrade the Quorum Server before you upgrade Serviceguard.00 before you proceed. if something goes wrong you can roll back to the original (pre-upgrade) state by rebooting from the original disk.1 1. But you must make sure your cluster is eligible. see the support matrix at http:// www.20 Release Notes . see also “Non-Rolling Upgrade Using DRD” (page 44). but is even less disruptive because each node is down for a shorter time. and is particularly safe because the nodes can be quickly rolled back to their original (pre-upgrade) root disks. and you are not already running Quorum Server version A.04. see “Maintaining a Package: Maintenance Mode” in chapter 7 of Managing Serviceguard for more information about maintenance mode. CAUTION: If you are using an alternate Quorum Server subnet (page 30). This method involves much less cluster down time than a conventional non-rolling upgrade. after reading and understanding the restrictions. Rolling Upgrade Using DRD A rolling upgrade using DRD is like a rolling upgrade. then halt the cluster and reboot each node from its updated clone root disk.20” (page 47) and “Restrictions for DRD Upgrades” (page 45). If.19.com/go/hpux-serviceguard-docs —> HP Serviceguard. • • If you are upgrading from a release earlier than A. see “Requirements for Rolling Upgrade to A. which you can find at the address given under “Documents for This Version” (page 34). CAUTION: Special considerations apply to a rolling or non-rolling upgrade to Serviceguard A. 44 Serviceguard Version A.16” (page 33). see “Quorum Server Upgrade Required if You Are Using an Alternate Address” (page 9).1 1. For information about supported Serviceguard versions.hp. IMPORTANT: Use the clone disk only on the system on which it was created.1 1. Serviceguard does not support booting from a clone disk made on another system (sometimes referred to as DRD re-hosting).given under “Documents for This Version” (page 34). you clone each node's root disk and apply the upgrade to the clone. • If you are upgrading both the Quorum Server and Serviceguard.16.1 1.com/go/drd. see “Access changes as of A. Non-Rolling Upgrade Using DRD In a non-rolling upgrade with DRD. see “Restrictions for DRD Upgrades” (page 45). you decide to perform a rolling upgrade using DRD. You can obtain the latest version of the DRD software free from http://www. Upgrade Using DRD DRD stands for Dynamic Root Disk.04. Using a Dynamic Root Disk on HP-UX 1 v3 allows you to 1i perform the update on a clone of the root disk.hp. but you need to make sure your cluster is eligible.1 1. CAUTION: Make sure that no package is in maintenance mode when you upgrade Serviceguard. see “New Cluster Manager” (page 8). It is also very safe. then halt the node and reboot it from the updated clone root disk. If.19.1 1. As of the date of these release notes. you decide to perform a non-rolling upgrade using DRD.1 1.1 1.20. DRD upgrade is supported for clusters that use the LVM or VxVM volume manager.19 an A.hp. or You are using drd runcmd swinstall to upgrade from one revision of Serviceguard A.1 1.20 patch release an A. follow the instructions under “Performing a Non-Rolling Upgrade Using DRD” in Appendix D of the latest edition of Managing Serviceguard.1 1.1 1.1 1.1 1.20 patch release from Serviceguard version A. For instructions on making the fix.1 1.1 1. You do not need to make this fix if: – – – • You are upgrading from Serviceguard A. see “Fixed in This Version” (page 49) for more information about looking up defects. Installing Serviceguard on HP-UX 45 .1 1.19 to: IMPORTANT: ◦ ◦ Upgrades from earlier releases via DRD are not currently supported.1 1.18 with patch PHSS_37602 (or a later cumulative patch) to: – – – – ◦ – – – A. You need to make this fix if: – You are using drd runcmd update-ux to upgrade to Serviceguard A.1 1.19 patch release A.18 or A. see the Workaround Notes for defect QXCR1000901306 at ITRC. 1i As of the date of these release notes. which you can find at the address given under “Documents for This Version” (page 34).1 1.19 to A.19 require that you make a manual fix to a checkinstall script in the software depot.1 1.19 to a later revision.20 an A. or – You are using drd runcmd swinstall to upgrade to Serviceguard A. or You are using drd runcmd update-ux to upgrade to an HP-UX OE containing SG A. after reading and understanding the restrictions. Restrictions for DRD Upgrades • • DRD is available only on HP-UX 1 v3.1 1. the only paths that are supported for DRD upgrade are: ◦ from Serviceguard version A.com.20 an A.20. DRD upgrades to version A.19 patch release A.19.1 1. Veritas Storage Management Products For information about installing and updating VxVM.00 Release Notes for information about DRD upgrades in CVM/CFS environments.03. in a file system mounted on the active root disk). In addition.1.com/go/hpux-core-docs —> 11i v3 — Setup and install — general. 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.1 1. then clone the disk. or use swcopy to copy the depot to an external server. then use the depot on the external server to install the software onto the clone disk • You should also do this if you are going to use update-ux and the install depot is on a CD mounted on the local system.00 Release Notes and HP Serviceguard Storage Management Suite A. The process is referred to as a rolling upgrade. You must follow the instructions for DRD upgrades in Managing Serviceguard. 1i HP recommends using the latest version of the DRD software. 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. and not all earlier Disk Layout versions are supported on HP-UX 1 v3. while that node’s applications are running on an alternate node. 1i Rolling Upgrade In some cases you can upgrade Serviceguard and HP-UX without bringing down the cluster.0 Installation Guide for details. 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.) • • Serviceguard does not support booting from a clone disk made on another system (sometimes referred to as DRD re-hosting). IMPORTANT: The following information is additional to the instructions in Appendix D of Managing Serviceguard.IMPORTANT: See the HP Serviceguard Storage Management Suite A. The cluster must meet both general and release-specific requirements for a rolling or non-rolling upgrade. which you can obtain free from HP (see “Upgrade Using DRD” above. NOTE: A new default Disk Layout Version was introduced in VxVM 4.04. or is a directory in the active system (for example. see the appropriate version of the Veritas Installation Guide at http://www.20 Release Notes . See the Veritas 5. then install the software from the depot on the clone disk. Do one of the following: ◦ ◦ use swcopy to copy the depot onto the active root disk. make sure you do not use control-C to escape from a runcmd drd swinstall command. 1i You do not have to upgrade the operating system itself. 46 Serviceguard Version A. you do this by upgrading one node at a time. and is described in Appendix D of the Managing Serviceguard manual. • Use the DRD software released with the September 2009 release of HP-UX 1 v3 or later. so long as you are running 1 v3. as this can cause problems.hp. 16 or greater on HP 9000 systems running HP-UX 1 v2 or 1 v3. See “Updating the Cluster Lock Configuration” in Chapter 7 of Managing Installing Serviceguard on HP-UX 47 . or as a standalone product. and you need to obtain a copy of A.1 1.19 If you are running a release earlier than A. See the next two subsections.19.1 1.1 1.20.1 1. Migrating to Agile Addressing if Using Cluster Lock Disk You cannot migrate to the HP-UX 1 v3 agile addressing scheme for device files during a rolling 1i upgrade if cluster lock disks are used as a tie-breaker.com/go/hpux-serviceguard-docs —> HP Serviceguard Storage Management Suite. and the Rolling Upgrade Exceptions that follow.hp. In the case of CVM.1 1.20. you may be able to do a rolling upgrade to A. you must be running: • • HP-UX 1 v3 and 1i Serviceguard A. Obtaining a Copy of Serviceguard A.19 while still on HP-UX 1 v2.1 1. Log in as follows: User name: ESS_SG1119_KIOSK Password: upgrade21120 Rolling Upgrade Exceptions HP-UX Cold Install A rolling upgrade cannot include a cold install of HP-UX on any node.19 is supported only if you are upgrading from: • • Serviceguard A.19. Specifically you cannot do a rolling upgrade if you are using the Veritas clustering capabilities — CVM and CFS.1 1. or 1i 1i Serviceguard A.02.19 If you are not already running A.1 1.1 1.01 Release Notes at http://www.20.16 on HP-UX 1 v2. you can download the software from web at http:// www.com/kiosk. and from A.20 To perform a rolling upgrade to Serviceguard A.1 1. Requirements for Rolling Upgrade to A. you must first install 1i patch PHSS_31072 or a later patch.1 1.Requirements for Rolling Upgrade to A.0 Installation Guide and the HP Serviceguard Storage Management Suite A. device file names (DSFs) are not guaranteed to remain the same after a cold install. Rolling upgrade to Serviceguard A. 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.20. 1i 1i IMPORTANT: If you are upgrading from A. for example.19. see the Veritas 5. 1i you must upgrade to HP-UX 1 v3 in order to upgrade to Serviceguard A.19 IMPORTANT: Although you can upgrade to Serviceguard A.hp.1 1. this applies whether you purchase it as part of a Storage Management bundle.1 1. See also the requirements listed above under “Upgrading from an Earlier Serviceguard Release” (page 43).software.19 to A.15 or greater on HP Integrity systems running HP-UX 1 v2 or 1 v3. because that involves changing the cluster configuration.1 1. For more information.1 1.19 so that you can do a rolling upgrade to A.1 1. A cold install will remove configuration information.1 1.1 1i 1. hp.) The swremove command should be issued from one system at a time. (If the node is not removed from the cluster configuration first. Serviceguard must be halted (not running) on the node from which the swremove command is issued.1 1. Upgrading from an Earlier Release if You Are Not Using Rolling Upgrade (Non-Rolling Upgrade) If your cluster does not meet the requirements for a rolling upgrade. If a zero-length binary configuration file (/etc/cmcluster/cmclconfig) is left your system you should remove it. See Appendix D of the Managing Serviceguard manual. swremove will cause the current cluster to be deleted.1 1. you must bring down the cluster (cmhaltcl) and then upgrade Serviceguard and HP-UX on the nodes.hp. The system from which the swremove command is issued must be removed from the cluster configuration. 1. Patches for this Version The table below lists patches required or recommended for Serviceguard A. or you decide not to use rolling upgrade for some other reason.com (Europe) 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.Serviceguard for instructions in this case.x Table 2 Patches Patch Number PHNE_35894 or later cumulative patch PHKL_37458 or later cumulative patch Description Patch to enable online replacement of LAN cards on HP-UX 1 v3.com/go/hpux-core-docs.itrc. 2. it should be removed from one system at a time. 1i Patch to modify the GIO subsystem to export the wwid and uniq_name properties of a LUN. Fixes 1i QXCR1000575890. 48 Serviceguard Version A. see the section “Which Patches Are on a System?” in the Patch Management User Guide for 1 Systems. Before removing software. note the following: 1. if Serviceguard is being de-installed from more than one system. run the SD-UX swremove command.20 Release Notes . This patch is required. That is. See “About Device Special Files (DSFs)” (page 32) of these Release Notes for more information about agile addressing. see “QXCR1000575890: OLR of a LAN Card in SG cluster fails on HP-UX 1 v3” (page 49). You can perform a non-rolling upgrade (that is.com (Americas and Asia Pacific) http://europe. Uninstalling Serviceguard To uninstall the Serviceguard software.20 on HP-UX 1 1i v3. you should also check the Hewlett-Packard IT Resource Center web page for any new patch requirements: http://itrc.hp. at http://www. 3. Before installing Serviceguard. an upgrade performed while the cluster is down) from any HP-UX/Serviceguard release. com/go/hpux-serviceguard-docs. You can find more information about these defects at ITRC. bug reports. Fixed in This Version 49 .20 on HP-UX 1 1i v3 listed under “New Features for A.03. 1i Workaround: Apply patch PHNE_35894.19 also includes all fixes already included in patches to earlier Serviceguard versions.1 1. See “Replacing LAN or Fibre Channel Cards” in Chapter 8 of Managing Serviceguard for more information. 2. you will be able to perform online replacement of hot-swappable cards (without bringing down the cluster). You will encounter this problem on an unpatched HP-UX 1 v3 system whether you use the Peripheral Device Tool (pdweb) or the HP-UX olrad command. solutions.hp. (See “Patches for this Version” (page 48) for more information about patches.) NOTE: If for some reason you need to proceed without the patch.20 April 201 Patches” 1 (page 13).1 1i 1. On a system to which the patch has been applied.com Choose >> Search knowledge base in the left frame Enter the defect number beginning QXCR as the search string (for example QXCR1000472750). NOTE: Serviceguard A.com.20 on HP-UX 1 v3 listed under “New Features for A. you must follow the “Off-Line Replacement” procedure under “Replacing LAN or Fibre Channel Cards” in Chapter 8 of Managing Serviceguard.) NOTE: You can apply the patch without a reboot.hp. Search against Engineering notes.04. 4. QXCR1000575890: OLR of a LAN Card in SG cluster fails on HP-UX 1 v3 1i Problem: Online replacement (OLR) of a LAN card in a Serviceguard cluster fails on a system running HP-UX 1 v3 because the Critical Resource Analysis (CRA) performed as part of the OLR 1i operation returns CRA_SYS_CRITICAL. (You can find the manual at http://www. these fixes are not necessarily documented here. This patch is recommended. PHSS_41628 PHSS_41674 Patch to enable the features introduced in HP Serviceguard A.20 April 201 Patches” (page 13). 1 Patch to enable the Modular CFS Package feature introduced in HP Serviceguard CFS A. Proceed as follows. PHSS_41628 must be installed.1 1. To install this patch. NOTE: This patch is needed only if SG Storage Management Suite A. FAQs (uncheck the other items in the list). 1.1 1.1 1.hp. Fixed in This Version This section lists defects that have been fixed in this release.00 is installed on the node.01 or A. 3. Log in to ITRC. or the number beginning JAG if there is no QXCR number.Table 2 Patches (continued) Patch Number PHCO_39413 or later cumulative patch Description Patch to enable display of wwid and uniq_name properties in the output of ioscan (1m). 20 Release Notes .20 unlimited modular package service restarts is impossible online QXCR1001007809: Nodes cannot be removed from cross subnet CFS cluster online 50 Serviceguard Version A. which is delivered with the patches.19 does not clear cluster lock area when cluster starts QXCR1001017930: Removing an external script from a modular package QXCR1001017176: multi-threaded volume group activation may result in non-attached PV's QXCR1001016805 : cmcld core and node TOC after rolling upgrade from 11. QXCR1001011472: Modular packages are at risk of failure during online reconfiguration QXCR1001009221: Serviceguard 11.19 QXCR1001015586: SG PHSS_40152 may result in silent corruption on LVM versions lower than 0909 QXCR1001013739: Corrupt dlpi message can result in cmnetd failure and system TOC.20 Defects Fixed in the April 201 Patches 1 • • • • • • • QXCR1001047727: Out or order messages and aborts after lan failures with SG 11. Defects Fixed in A.1 1. QXCR1001037833: cmpreparecl: Serviceguard is not installed QXCR1000924066: System becomes unresponsive after repeated Serviceguard service failures QXCR1001015937: Modular packages are at risk of failure during online reconfiguration QXCR1001017615: Member timeout difference after rolling upgrade causes cmapplyconf failure Additional fixes are listed in the patch form text.19 QXCR1001046353: cmclconfd does not reset the hostname resolution family after deleting the cluster QXCR1001020964: CrossSubnet:Not able to form the cluster with IPv6 address.20 The following defects are fixed in Serviceguard A.A.1 1.19 cmproxyd reports cluster is not configured when it is QXCR1001007814: port scan brings down cmcld QXCR1001007803: SG 11.20 (some may also have been fixed in recent patches).17 to 11.1 1.1 1. • • • • • • • • • • • • • • QXCR1001024162: cmlvmd reports Unable to initialize ESCSI kernel interface: File exists (17) QXCR1001023633: cmsnmpd experiences fd leak if identd fails QXCR1001021604: EMS resources are not unregistered when cmcld exits after unsuccessful cmrunnod QXCR1001021711: SG A.11. 20 cmcld abort on unexpected UDP message version QXCR1001007347: Serviceguard 11.19 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.20 installation does not preserve hacl-cfg options QXCR1001005198: cmcld has a file descriptor and memory leak when connect errors occur QXCR1001005241: cmmodnet -t incorrectly plumbs secondary interface on lan QXCR1001005296: cmcld runs into an assertion at cluster start QXCR1001003944: SG cross subnet functionality breaks non symmetric cluster configurations QXCR1000984406: cmruncl -n may fail if MEMBER_TIMEOUT is 60 seconds or more QXCR1000984418: cmclconfd -p does not process query requests from commands after nessus scan QXCR1000984388: Packages may re-start if they are halted at the same time and have dependencies QXCR1000984408: cmproxyd does not clean up named pipe files in /var/adm/cmcluster/proxies dir QXCR1000984401: script_log_file does not resolve more than one $SG_PACKAGE variable QXCR1000984411: Serviceguard 11. which is delivered with the patches.19 clusters fail after quorum server re-configuration QXCR1000945173: all cmcld threads in ksleep() safetytimer expiration node TOC QXCR1000939872: cmcld abort due to closing the same fd twice after QS failure QXCR1000930233: 11.• • • • • • • • • • • • • • • • • • • • • • • • QXCR1001007816: Serviceguard 11.19 unlimited modular package service restarts is impossible QXCR1000957441: ALL nodes in ALL 11. Fixed in This Version 51 .cm_start_time message correctly in syslog after abort QXCR1000924958: cmcld SIGSEGV when starting a 1 node cluster after upgrade to A.19 cmclconfd liable to core dump and log messages omit hostname QXCR1000926553:cmclconfd hang QXCR1000924956: SG cmcld does not log .11. ASMDG parameters should be consistent with tooltip QXCR1001100700: SGeRAC Toolkit RAC DB Package configuration page should be updated QXCR1001101146: Configuration menu should be disabled while packages detached in the cluster Additional fixes are listed in the patch form text.Problems Fixed in this Version of the Serviceguard Manager Plug-in The following defects have been fixed in Version B. node and package in Internet Explorer QXCR1001098914: OLH page for SAP Database Instance Module must be updated for DB2 QXCR1001099255: SGeRAC packages maintenance mode tooltip should be consistent with OLH QXCR1001100699: OLH for SGeRAC Oracle RAC DB.0 refresh is very slow when node down or fails to start QXCR1001100842: SGMgr displays wrong warning on mouse over for SGeSAP alert QXCR1001086491: Tooltip for Package "State/Status" does not mention "Detached" state QXCR1001088102: Preview Halt node operation should display proper message QXCR1001090394: OLH page should be updated for Cluster and Node status QXCR1001093940: Message in SGMgr GUI should change after operation is complete QXCR1001096366: Running multiple Packages configured for different nodes in single run operation QXCR1001098626: Map View does not display icons for cluster. 52 Serviceguard Version A.10 of Serviceguard Manager: • • • • • • • • • • • • • • • • • • • • • QXCR1001103488: SGManager displays wrong status of SGeRAC as configured QXCR1001031495: DTS AR1009 FR: SG Mgr .Metrocluster configuration ease of use input QXCR1001047635: Package goes into maintenance if there is any .debug file in package directory QXCR1001061996: Toolkit maintenance mode state being incorrectly reported by SGMgrPI QXCR1001067056: Disallow Halt Package on node where it is not running QXCR1001075056: Add ASM PKG dependency automatically to ASM_DB package QXCR1001075087: RACDB and ASMDG pkgs should display maintenance status when CRS is in maintenance mode QXCR1001079529: ServiceguardManagerPI operations fail when launched from HP SIM on windows CMS QXCR1001081511: Serviceguard Manager PI 2. which is delivered with the patches.03.1 1.20 Release Notes . QXCR1001098295: Long mount point results in awk error for CFS MP DG pkg QXCR1001098287: Package incorrectly fails when using cfs_mount_options Known Problems 53 . You can find details of each defect on the ITRC web site.com (Europe).0.europe.com (Americas and Asia Pacific) or http://www. More-recent information may be available from your HP support representative.hp. syslog shows cmcld was running QXCR1001008705: cmclconfd & cmproxyd cored in sg_is_ipv6only_hostname () QXCR1001028611: SGProvider core when cmrunnode/cmruncl with detached packages fail QXCR1001019766: SGProvider: Caught CIM Exception messages in syslog QXCR1001026866: SGProvider logs Permission denied to 127.itrc.20 known at the time of publication. or on the Hewlett-Packard IT Resource Center (ITRC): http://www.03.10.00 reports installation error QXCR1000876609: member crashes during cluster reformation.1 msg in syslog when cluster is not configured QXCR1001020972: SG package validation script incorrectly thinks mount point is nested QXCR1001108352: Package IP addresses for MNPs should result in cmapplyconf failures QXCR1001107652: Regarding multiple entries issue using cmmakepkg -t option QXCR1001092092: The sg_log function for packages does not display the date correctly QXCR1001112638: cmcheckconf reports error for low member timeout on single node cluster QXCR1001111657: cmcheckconf dumps core for huge CONFIGURED_IO_TIMEOUT_EXTENSION QXCR1001113972: cmmodnet fails adding valid IP address ending on 255 QXCR1001105246: ST:cmcld core dump at in cl_list2_enqueue -at utils/cl_list2. See “Fixed in This Version” (page 49) for instructions on looking up a defect.c:184 QXCR1000992056: Changing polling interval online can result in false failovers QXCR1001109402: SafetyTimer getting terminated after 24 hours of run QXCR1001098978: cmapplyconf does not validate mount options for ckpt package.Known Problems This section lists problems in Serviceguard Version A.1 1.itrc. Known Problems for Serviceguard • • • • • • • • • • • • • • • • • • • QXCR1001063125: SGWBEMProviders A.0. This list is subject to change without notice.hp. (Such features do not affect the running of an existing Serviceguard cluster until you activate them. see the Serviceguard Compatibility and Feature Matrix at the address given under “Documents for This Version” (page 34).com/ go/hpux-serviceguard-docs. supported version. Serviceguard A. Patches will be made available within the extended support time frame even though a newer version of Serviceguard is available. See also “Compatibility Information and Installation Requirements” (page 35) in these Release Notes. OC package per site is allowed ONLY when configured through package easy deployment. In general.20 is a platform release.1 1. etc. the following is guaranteed: • • Patch-specific release testing is performed before the patch is posted. feature releases will be supported until a newer version of Serviceguard becomes available. will continue to operate without modification. About Serviceguard Releases Types of Releases and Patches Versions of Serviceguard are provided as platform releases. In order to receive fixes for any defects found in a feature release after a newer version is released. Patch A patch to a release may be issued in response to a critical business problem found by a Serviceguard customer. Existing functionality. or for new features that you intend to use.20 Release Notes . which is the preferred environment for the majority of Serviceguard customers. 54 Serviceguard Version A. scripts. Feature releases are for customers who want to use the latest features of Serviceguard. • • QXCR1001119074: Some SGMgr labels and notes need to be localized QXCR1001119063: In a site aware cluster. or a patch may enable new features. you will need to upgrade to the newer. for example by reconfiguring the cluster or reworking a package. NOTE: For compatibility information for this and earlier releases.hp. Feature Release A feature release contains new Serviceguard features. see the Serviceguard Compatibility and Feature Matrix. Certification testing for a patch is recommended only for those fixes that are important to your specific installation. Platform Release A platform release is a stable version of Serviceguard. or patches.Known Problems for Serviceguard Manager The following problems in Serviceguard Manager B.) In the case of a patch.1 1. feature releases. • All fixes from the previous patch are incorporated.03. 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.10 were known at the time of publication. at http://www. hp. IMPORTANT: Even though the command-line interface does not provide Native Language Support. Native Languages Serviceguard Manager provides Native Language Support. See “Serviceguard Manager” (page 24) for a list of the languages supported by Serviceguard Manager. The version string has 4 parts: • • • Alphabetic Prefix First Numeric Field Second Numeric Field • Third Numeric Field When a new release is issued. In such cases HP updates the Release Notes at http://www. Documentation for major releases of Serviceguard is translated into the following languages: • • Japanese Simplified Chinese Release Notes Revisions 55 . Release Notes Revisions Occasionally.Version Numbering Serviceguard releases employ a version numbering string that helps you identify the characteristics of the release. Versions with the same part number are differentiated by the publication date. important new information warrants revising the Release Notes after they have gone to press. but the command-line interface does not.com/go/ hpux-serviceguard-docs. different portions of the version string are incremented to show a change from a previous version of the product. Serviceguard functions correctly whether or not the LANG variable is set to C.