HP Serviceguard for Linux Version A.11.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
Trademark Notices MC/Serviceguard® is a registered trademark of Hewlett-Packard Company, and is protected by copyright. NFS® is a registered trademark of Sun Microsystems, Inc. NIS™ is a trademark of Sun Microsystems, Inc. Red Hat® is a registered trademark of Red Hat Software, Inc. Linux® is a registered trademark of Linus Torvalds. UNIX® is a registered trademark of The Open Group. SUSE® is a registered trademark of SUSE AG, a Novell Business.
Serviceguard for Linux Version A.11.16 Release Notes Announcements 1 Serviceguard for Linux Version A.11.16 Release Notes Announcements HP Serviceguard for Linux is a specialized facility for protecting mission critical applications from a wide variety of hardware and software failures. Serviceguard A.11.16 is now available for the Linux operating system on HP Integrity Servers through the following product number: • T2391AA — A.11.
Serviceguard for Linux Version A.11.16 Release Notes Announcements — Installation and support services available • 305199-B26 — A.11.16 — software kit and license — 2 licenses for HP ProLiant servers - one license required per server — 2 CDs — Installation and support services available — Heartbeat cable. The heartbeat (crossover) cable is intended for use only in a two-node cluster that requires an additional heartbeat connection. It provides a direct connection between the two servers.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 What’s New in A.11.16 The following are new features or options available in this release: • Support for Red Hat 4 AS and ES (starting with Update 1). • New access control policies that you can configure using either the Serviceguard Manager graphical user interface or the command line. • Enhanced security (originally released as a patch to address security bulletin HPSBUX01080). • Serviceguard Manager A.05.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 Access Control Policy Non-root access to Serviceguard is now defined in the cluster and package configuration files, in a parameter called Access Control Policy. You can have up to 200 policies in a cluster. Policies can be added, modified, or deleted from the configuration without halting the cluster or the package. Conflicting or redundant policies will cause an error at cmapplyconf, and the configuration change will fail.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 Chapter 1 • Package Admin: Includes Monitor privileges. The user can issue commands to administer the package. On the command line, users can issue: cmrunpkg, cmhaltpkg, and cmmodpkg. In the graphical user interface, these menu choices are offered: run or halt a package, move a package from one node to another, and change the node- and package-switching flags.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 Enhanced Security Serviceguard now uses the pidentd daemon to enhance security. The pidentd daemon is installed as part of the Serviceguard product installation process. The white paper Securing Serviceguard, October 2004, available in the Serviceguard section of http://docs.hp.com, describes these enhancements in greater detail. Disabling Security It is possible to disable the security features.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 For Red Hat and SUSE: 1. Change the server_args parameter in the file /etc/xinetd.d/hacl-cfg from: server_args = -c to server_args = -c -i 2. Change the server_args parameter in the /etc/xinetd.d/hacl-probe file to include the -i For SUSE this would be changed from: server_args = -f /opt/cmom/log/cmomd.log -r /opt/cmom/run to server_args = -i -f /opt/cmom/log/cmomd.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 What’s New in A.11.16.07/8 The following are new features or options available in this release: • Support for SUSE SLES10. • VG activation protection for LVM2. When enabled, this function uses LVM2 “tagging” to to help prevent accidental activation of a package’s volume group on nodes that are not allowed to run that package.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 Chapter 1 • The information under “Using udev for Persistent Device Names” on page 23 has been added; it refers to a white paper showing how to get persistent device names in a Serviceguard for Linux cluster. (This information is in a white paper because it may change in the future.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 Further Information • The Serviceguard for Linux Order and Configuration Guide contains the latest information about supported configurations. The latest update information on supported hardware and Linux distributions is available in the HP Serviceguard for Linux Certification Matrix. Both documents are available at: http://www.hp.
Serviceguard for Linux Version A.11.16 Release Notes What’s New in A.11.16 http://forums1.itrc.hp.com/service/forums/home.do and then select Linux->more...->serviceguard.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Compatibility Information and Installation Requirements Read this entire document and any other Release Notes you may have before you begin an installation. NOTE All nodes must be on the same distribution, including errata level and architecture version (i.e. ia32, i686, x86_64, ia64). Using different distribution versions within the same cluster is supported only during rolling upgrade.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements System Requirements The memory requirement for HP Serviceguard for Linux A.11.16 depends on the number of packages configured in the cluster.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements System Firewalls When using a system firewall such as IPFilter with Serviceguard, specific communications must be allowed to ensure proper cluster operation. General guidelines for using a system firewall with Serviceguard are listed below.
Serviceguard for Linux Version A.11.
Serviceguard for Linux Version A.11.
Serviceguard for Linux Version A.11.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Multipath for Storage The method for achieving a multipath solution is dependent on the storage sub-system attached to the cluster and the HBA in the servers. Please check the documentation that accompanied your storage sub-system and HBA. For fibre channel attached storage, the multipath function within the HBA driver should be used, if it is supported by HP.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements NOTE MD also supports software RAID; but this is not currently supported with Serviceguard for Linux. Using udev for Persistent Device Names In a Linux system, device names are not necessarily consistent from one boot to another. Consider a system with LUNs /dev/sdg, /dev/sdh, and /dev/sdi. If /dev/sdh is removed, then after the system is rebooted the old /dev/sdi may be renamed to /dev/sdh.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements After Linux is correctly configured, install HP Serviceguard using the rpm command. Install Serviceguard, and then the Quorum Server and Serviceguard Manager if you choose to do so. For any version of Red Hat supported by this release, authd must be uninstalled. Do the following: Step 1. # rpm -e authd Step 2.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements # cd /media/cdrom/SLES10/rpms # rpm -i sgcmom-B.03.01.02-0.product.suse.i386.rpm # rpm -i serviceguard-A.11.16.08-0.product.suse.i386.rpm When the commands are complete, the prompt appears. NOTE It is not necessary to install pidentd on SUSE Linux Enterprise Server 10; Serviceguard uses the version that is part of the SLES 10 distribution.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements # rpm -i sgcmom-B.03.01.02-0.product.suse.x86-64.rpm # rpm -i serviceguard-A.11.16.08-0.product.suse.x86-64.rpm When the commands are complete, the prompt appears. NOTE It is not necessary to install pidentd on SUSE Linux Enterprise Server 10; Serviceguard uses the version that is part of the SLES 10 distribution. Use the following commands to install Serviceguard on HP Integrity Servers.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements # rpm -i serviceguard-A.11.16.08-0.product.suse.ia64.rpm When the commands are complete, the prompt appears. NOTE It is not necessary to install pidentd on SUSE Linux Enterprise Server 10; Serviceguard uses the version that is part of the SLES 10 distribution. Pidentd Setup To complete the installation of the pidentd service issue the following commands.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Installing Serviceguard Manager The Serviceguard Manager software is supplied on the separate HP Serviceguard Distributed Components CD. This CD includes versions for HP-UX, Linux, and Windows operating systems. Updated versions may be available from http://www.hp.com/go/softwaredepot. Click on high availability to locate the latest version. See the Serviceguard Manager Version A.05.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements De-Installing Serviceguard for Linux To deinstall your software, run the rpm -e command, as follows: # rpm -e serviceguard Before removing software, note the following: 1. Serviceguard for Linux must be halted (not running) on the node from which the rpm -e command is issued. 2. The node from which the rpm -e command is issued must be removed from the cluster. 3.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements • If the target version of Serviceguard does not support the version of the operating system currently on the node, then you must upgrade the operating system before upgrading Serviceguard. NOTE • The first Serviceguard release to be upgraded is A.11.14.02, and the OS upgrade for the node must be from the same Linux distribution (Example: Red Hat AS 2.1 to Red Hat EL 3; NOT Red Hat AS 2.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Upgrades” on page 43 before you start the upgrade, and keep in mind that the entire upgrade process has to complete successfully before you can use any Serviceguard commands. CAUTION Chapter 1 If a failure occurs on one node while you are upgrading another, packages - and the applications they contain - may not be able fail over to the node being upgraded.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Steps for Rolling Upgrades Preparation: IMPORTANT Make sure there is a supported upgrade path from your current Linux and Serviceguard versions to the new versions. See the Serviceguard Compatibility and Feature Matrix at http://docs.hp.com/hpux/ha. There is no upgrade path between some Linux OS releases; for example, there is no upgrade path from Red Hat AS 2.1 to Red Hat EL3.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements • SG files: $SGCONF/*: all current package control and configuration files, including their log files. Use the following steps to perform the rolling upgrade: 1. Halt the node you want to upgrade. This will cause the node's packages to start up on an adoptive node. In Serviceguard Manager, select the node; from the Actions menu, choose Administering Serviceguard, Halt node.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements For Serviceguard upgrade only, you can choose to install with one of the following options: Example: For a node not configured into a cluster: # rpm -i --force serviceguard-A.11.16.07-0.product.Redhat.i386.rpm For a node already configured into a cluster: # rpm -U --replacefiles serviceguard-A.11.16.07-0.product.Redhat.i386.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements where version represents the version number for the pidentd that was last installed. Follow the instructions in the README file in the directory of each driver. If you have installed a new OS version, you must run a convert program. This will convert the binary file (cmclconfig) to its new release format.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements NOTE Be sure to plan sufficient system capacity to allow moving the packages from node to node during the process without an unacceptable loss of performance.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Example of Rolling Upgrade While you are performing a rolling upgrade warning messages may appear while the node is determining what version of software is running. This is a normal occurrence and not a cause for concern. The following example shows a simple rolling upgrade on two nodes running one package each, as shown in Figure 1-1.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements This will cause PKG1 to be halted cleanly and moved to node 2. The Serviceguard daemon on node 1 is halted, and the result is shown in Figure 1-2. Figure 1-2 Running Cluster with Packages Moved to Node 2 Node1 SG 38 Node2 SG A.11.14.02 Pkg1 A.11.14.02 AS 2.1 Pkg2 AS 2.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Step 2. Upgrade node 1 to the next operating system release (in this example, Red Hat EL 3), and install the next version of Serviceguard, as shown in Figure 1-3. Figure 1-3 Node 1 Upgraded to Red Hat EL 3 Node1 Node2 Pkg1 Red Hat EL 3 Pkg2 SG A.11.14.02 Red Hat AS 2.1 Step 3.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements At this point, different versions of the Serviceguard daemon (cmcld) are running on the two nodes, as shown in Figure 1-4. Figure 1-4 Node 1 Rejoining the Cluster Step 4. Repeat the process on node 2.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements This causes both packages to move to node 1. Then upgrade node 2 to Red Hat 3 and the new version of Serviceguard. Figure 1-5 Running Cluster with Packages Moved to Node 1 Node1 Pkg1 Pkg2 Node2 SG SG A.11.15.02 A.11.15.02 Red Hat EL 3 Red Hat EL 3 Step 5. Move Pkg2 back to its original node.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements The cmmodpkg command re-enables switching of the package, which is disabled by the cmhaltpkg command. The final running cluster is shown in Figure 1-6. Figure 1-6 Running Cluster After Upgrades Node1 Pkg1 SG A.11.15.02 Red Hat EL 3 42 Node2 Pkg2 SG A.11.15.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Limitations of Rolling Upgrades The following limitations apply to rolling upgrades: Chapter 1 • During rolling upgrade, you should issue Serviceguard commands (other than cmrunnode and cmhaltnode) only on a node containing the latest revision of the software. Performing tasks on a node containing an earlier revision of the software will not work or will cause inconsistent results.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Linux Distribution Differences for Serviceguard The SUSE Linux Enterprise Server distribution of HP Serviceguard differs from the Red Hat distributions in a few details, which are described below. Directory Locations Serviceguard uses a special file, cmcluster.conf, to define the locations for configuration and log files within the Linux file system.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements Ensuring Clean Shutdown of Cluster Nodes Running SUSE SLES10 To ensure that the cluster nodes halt correctly when they are shut down, edit the file /etc/sysconfig/boot on each node and change the value of the RUN_PARALLEL parameter from yes to no.
Serviceguard for Linux Version A.11.16 Release Notes Compatibility Information and Installation Requirements # LVM initialization if [ -e /proc/lvm -a -x /sbin/vgchange -a -f /etc/lvmtab ]; then action $"Setting up LVM:" /sbin/vgscan && /sbin/vgchange -a y fi Commenting out these lines will prevent vgscan from removing the old volume group device files, and prevent automatic volume group activation on boot.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version Patches and Fixes in this Version This section describes patches that are required and defects that have been fixed in version A.11.16 of HP Serviceguard for Linux. Required Patches There are no patches required or recommended for HP Serviceguard for Linux A.11.16 at the time of publication.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version Fixes The following defects have been fixed in HP Serviceguard for Linux A.11.16.02. JAGaf49627, JAGaf50940, JAGaf46380, JAGaf56322: IP addresses in the cmclnodelist file and /etc/hosts are treated incorrectly • Problem: Serviceguard was not handling IP addresses in the cmclnodelist file correctly. This resulted in “Permission Denied” errors in response to commands.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version There was a deadlock in the code possible where one thread was holding a lock while waiting for another lock that created a deadlock condition with another thread. • Resolution: The fix is to have the thread release the lock before trying to acquire the other lock. JAGaf45937: The value here will be used when reporting dates in the log files of processes started directly or indirectly by cmcld.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version • Resolution: Copy the netmask from existing configuration to the new_cl after data is read from the ascii file, so that we can detect the differences during gather_network_config phase of the commands.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version JAGaf01170: cmresmond should kill agents during shutdown/restart/reload Problem: On cmresmond --shutdown, --restart, or --reload, the disk agents that were running before the command was executed may not be terminated and will be left running. The disk agents are never explicitly killed in these cases because they usually die on their own. Resolution: Kill agents explicitly upon reload, restart, or shutdown.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version cmmodnet command gets stuck in an infinite loop when zero subnet is passed as an argument since that case was not being accounted for and got stuck in a while(1) loop. Resolution: During the parsing of the command args, catch this case and error out right away with the message that non-zero arguments are required for cmmodnet. Modify the cmmodnet parsing to catch the zero subnet case and error out appropriately.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version JAGaf55446: Setting cmclconfd -i in inetd.conf logs too many messages in syslog Problem: When identd was disabled, a security warning message was written to syslog each time cmclconfd executed. Resolution: cmclconfd now writes the warning message to syslog only on first execution after the node joins the cluster and first execution after boot. JAGaf61355: SG 11.16.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version JAGaf78275: Kernel problem on 1 node resulted in catastrophic SG cluster failure Problem: Under rare circumstances, involving the timer loop thread or the system clock on one node, all the nodes in a cluster could halt (TOC) at the same time. Resolution: cmcld now checks the timestamps of heartbeat messages to ensure the clock is advancing, and aborts if it detects no advance over a set period.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version JAGaf97723: Serviceguard does not halt cleanly when a cluster node is brought down using shutdown -h Problem: When a cluster node was halted, the cmcluster halt scripts were not executed because they were not included in /etc/rc0.d. This could result in packages not being halted automatically as part of the shutdown and in packages not failing over to an adoptive node.
Serviceguard for Linux Version A.11.16 Release Notes Patches and Fixes in this Version Required Linux Network Drivers The minimum versions for network drivers supported by HP Serviceguard are provided with the base OS. Updated versions of all network drivers are available in the PSP (ProLiant Support Pack). These drivers are tested and approved Refer to http://www.hp.com/ click on support and drivers. Use driver supplied with base OS.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds Known Problems and Workarounds The following describes known problems with HP Serviceguard for Linux versions A.11.16.01 and A.11.16.02 with workarounds for them. However, this is subject to change without notice. For the most current information contact your HP support representative. NOTE Patches can be superseded or withdrawn at any time. Be sure to check the status of any patch before downloading it.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds Configuring multiple users with the same UID results in non-deterministic UID to username resolution. • What is the problem? When most database schemes are used with user/password lookup, configuring multiple users with the same UID results in non-deterministic UID to username resolution.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds JAGad39695: User error can result in “ghost” services • What is the problem? If a cluster has a package with a service that is failing but that is not actually needed, and the package ascii file and package script are edited and then a cmapplyconf is executed, this will result in an error since the package is still running.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds JAGae29576: cmviewcl takes 15 seconds to report cluster status • What is the problem? cmviewcl may take up to 15 seconds to report the cluster status if a cluster node is unreachable. • What is the workaround? The command will complete successfully. JAGaf09394: Embedded quotes in Service Command not carried into pkg ctrl script. • What is the problem? Customers won't be able to use quotes in SDF data.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds JAGaf41625: Failure to access the locklun device is reported as a lock denied. • What is the problem? Any failed attempts to access the locklun device for the purposes of obtaining a lock, will be reported as a lock denied. For example if the locklun device is unavailable (cable disconnected or other such reason), and an attempt to obtain the lock will fail.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds cmapplyconf : Unable to apply the configuration • What is the workaround? Make certain that the ip addresses for all interfaces are present in the /etc/hosts file. As documented for A.11.16.01.
Serviceguard for Linux Version A.11.16 Release Notes Known Problems and Workarounds JAGaf48214: SDFComponent.setName fails with keywords, such as 'package' Chapter 1 • What is the problem? The problem happens when a customer tries to create a cluster with cluster name = “cluster” or package name = “package”. The error SGMGR users get is “cannot create a package named 'package' “. The present implementation through Sgmgr does not support it.
Serviceguard for Linux Version A.11.16 Release Notes Software Availability in Native Languages Software Availability in Native Languages HP Serviceguard for Linux Version A.11.16 does not provide Native Language Support. However, the following documents are available in Japanese language editions, which are included on the HP Serviceguard for Linux CD: 64 • Managing HP Serviceguard for Linux, Sixth Edition (B9903-90052) • HP Serviceguard for Linux Version A.11.
