HP Serviceguard Version A.11.
Legal Notices © Copyright 1998-2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Printing History Table 1 Printing History Printing Date Part Number Edition October 2005 B3935-90085 First Edition December 2005 B3935-90085 First Reprint March 2006 B3935-90091 Second Reprint The last printing date and part number indicate the current edition. Changes in March 2006 reprint include part number and publication date revision.
Serviceguard Version A.11.17 Release Notes 1 Chapter 1 Serviceguard Version A.11.
Serviceguard Version A.11.17 Release Notes Announcements Announcements Serviceguard is a specialized facility for protecting mission critical applications from a wide variety of hardware and software failures. The following Serviceguard versions are now available: • For HP-UX 11i v2 Update 2 — Product T1905BA —A.11.17—software and license — Product T1906BA —A.11.
Serviceguard Version A.11.17 Release Notes Announcements Current and earlier versions of Serviceguard on HP-UX support using a serial line (RS232) as an alternate heartbeat in some configurations, but future Serviceguard and HP-UX releases will not: Serviceguard A.11.17 on HP-UX 11i v2 and A.11.16 on HP-UX 11i v1 are the last versions that will support RS232 for heartbeat messaging.
Serviceguard Version A.11.17 Release Notes What’s in this Version What’s in this Version This A.11.17 version of Serviceguard is a platform release. This release contains new functionality, defect repairs and support for new hardware configurations. Highlights of the release are as follows: Serviceguard A.11.17 supports the same configurations as previous versions. The following features are new for Serviceguard A.11.17: • Serviceguard A.11.17 has been tested with HP-UX 11i Security containment.
Serviceguard Version A.11.17 Release Notes What’s in this Version default is now 150, the maximum that Serviceguard supports. Previously the default was 0, so users had to set it before any packages could be configured. With Serviceguard A.11.17, you can change the value of MAX_CONFIGURED_PACKAGES without halting the cluster. • A new option for the cmviewcl command creates output that is formatted to be used by scripts.
Serviceguard Version A.11.17 Release Notes What’s in this Version This tool is especially useful for creating consolidated syslogs and package logs in a Serviceguard cluster. This simplifies system and package monitoring and problem diagnosis — Command fan-out tool provides high performance tools for executed shell commands and distributing files across the members of a Serviceguard cluster. The cluster-aware tools offer cluster-wide general purpose command fan-out, ps, copy, kill, and uptime operations.
Serviceguard Version A.11.17 Release Notes What’s in this Version 1. If a failover application package uses CFS, you put an entry in its configuration file to create a dependency on the CFS mount point package, SG-CFS-MP-ID#, so the failover package will not start on a node until the mount point is ready. 2. The mount point package has a dependency on the disk group package, SG-CFS-DG-ID#, so it will not try to establish a mount point on a node until the disk group is ready. 3.
Serviceguard Version A.11.17 Release Notes What’s in this Version — Add shared disk groups to a VERITAS CFS cluster configuration, or remove existing shared disk groups from the configuration. Serviceguard automatically creates the multi-node package SG-CFS-DG-ID# to regulate the disk groups, automatically incrementing and appending their ID numbers. This package has a dependency on the SG-CFS-pkg created by cfscluster command.
Serviceguard Version A.11.17 Release Notes What’s in this Version • Enterprise Cluster Master Toolkit Version B.03.00 Release Notes (T1909-90034) • Clusters for High Availability: A Primer of HP Solutions, second edition (HP Press: Prentice Hall, ISBN 0-13-089355-2). This guide describes basic cluster concepts.
Serviceguard Version A.11.17 Release Notes What’s in this Version If you will be using VERITAS CVM 4.1 or the VERITAS Cluster File System with Serviceguard, please refer to the HP Serviceguard Storage Management Suite Version A.01.00 Release Notes (T2771-90028). These release notes describe suite bundles for the integration of HP Serviceguard A.11.17 with Symantec’s VERITAS Storage Foundation.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements Compatibility Information and Installation Requirements Read this entire document and any other Release Notes or READMEs you may have before you begin an installation. Compatibility Serviceguard version A.11.17 is compatible with the HP-UX 11i v2 Update 2 operating system. The graphical user interface, Serviceguard Manager Version A.05.00, is being released at the same time. Serviceguard A.11.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements Types of Releases and Patches Versions of Serviceguard are provided as platform releases, feature releases, or patches. Platform Release A platform release is a stable version of Serviceguard, which is the preferred environment for the majority of Serviceguard customers. Platform releases may also contain new Serviceguard features. These releases are supported for an extended period of time, determined by HP.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements • First Numeric Field • Second Numeric Field • Third Numeric Field When a new release is issued, different portions of the version string are incremented to show a change from a previous version of the product. Before Installing Serviceguard A.11.17 Before you install Serviceguard A.11.17, you need to make sure that your cluster has the correct hardware upgrades.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements After you complete a rolling upgrade, be sure to create and save a copy of the new configuration, using the cmgetconf command. If a cmapplyconf is issued, you want to be sure it applies the newly migrated Access Control Policies. Newly installed Serviceguard When you install Serviceguard for the first time on a node, you do not have a cluster.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements In pre-A.11.16 clusters, the only role for a non-root user is Monitor. To monitor a cluster, modify a (pre-A.11.16) cluster node’s cmclnodelist file. Read-only access is granted by entering the pair . Or, you can enter a + (plus) wild card to allow any user. A command line user can issue the cmviewcl command with this entry.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements • USER_ROLE Monitor Memory Requirements Serviceguard needs 15.5MB of lockable memory on each cluster node. NOTE Remember to tune the swap space and the HP-UX kernel parameters nfile, maxfiles and maxfiles_lim to ensure that they are set high enough for the number of packages you are configuring. Port Requirements Serviceguard uses the ports listed below.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements In addition, Serviceguard also uses dynamic ports (typically in the range of 49152 - 65535) for some cluster services. If you have adjusted the dynamic port range using kernel tunable parameters, alter your rules accordingly. Serviceguard also uses port 9/udp discard during network probing setup when running configuration commands such as cmcheckconf or cmapplyconf and cmquerycl.
Serviceguard Version A.11.17 Release Notes Compatibility Information and Installation Requirements Additional firewall considerations enable execution of Serviceguard commands from nodes outside the cluster, such as those listed in cmclnodelist. To allow this, follow the guidelines below.
Serviceguard Version A.11.
Serviceguard Version A.11.17 Release Notes Installing Serviceguard on HP-UX 11i v2 Installing Serviceguard on HP-UX 11i v2 Open SSL is a dependency for the successful installation of Serviceguard. The Service Cluster Manager component COM (Cluster Object Manager) depends on OpenSSL. OpenSSL installs as part of the operating system; do not remove it.
Serviceguard Version A.11.17 Release Notes Installing Serviceguard on HP-UX 11i v2 NOTE There are files in CM-CORE that are reserved for HP support. Do not change these files. Do not move, alter, or delete the following: • /usr/contrib/bin/cmcorefr • /usr/contrib/bin/cmdumpfr • /usr/contrib/bin/cmfmtfr • /usr/contrib/lib/Q4/cmfr.pl • /var/adm/cmcluster/frdump.cmcld.x (where x is a digit) The Cluster Object Manager product (B8324BA) is installed along with Serviceguard.
Serviceguard Version A.11.17 Release Notes Installing Serviceguard on HP-UX 11i v2 Bad binary config file directory format. Could not convert old binary configuration file. These messages may safely be ignored. Enhanced Security HP does not recommend disabling this security feature in version A.11.16.00 or later, as it provides and maintains the integrity and high availability for your data.
Serviceguard Version A.11.17 Release Notes Installing Serviceguard on HP-UX 11i v2 3. The swremove command should be issued from one system at a time. That is, if Serviceguard is being de-installed from more than one system, it should be removed from one system at a time. If your system is left with a zero-length binary configuration file (/etc/cmcluster/cmclconfig), you should remove it. 4.
Serviceguard Version A.11.17 Release Notes Installing Serviceguard on HP-UX 11i v2 Table 1-1 Rolling Upgrade Paths Serviceguard Release HP-UX Release Serviceguard A.11.01 HP-UX 11.00 Serviceguard A.11.03 HP-UX 11.00 Serviceguard A.11.04 HP-UX 11.00 Serviceguard A.11.05 HP-UX 11.00 Serviceguard A.11.07 HP-UX 11.00 Serviceguard A.11.08 HP-UX 11.00 Serviceguard A.11.09 HP-UX 11.00, HP-UX 11.11 Serviceguard A.11.12 HP-UX 11.00, HP-UX 11.11 Serviceguard A.11.13 HP-UX 11.00, HP-UX 11.
Serviceguard Version A.11.17 Release Notes Patches and Fixes in this Version Patches and Fixes in this Version The following table lists patches required or recommended for Serviceguard A.11.17 on HP-UX 11i v2. This list is subject to change without notice. Contact your HP support representative for up-to-the-moment information. Patches can be superseded or withdrawn at any time, so always be sure to check the status of any patch before downloading it.
Serviceguard Version A.11.17 Release Notes Patches and Fixes in this Version Table 1-2 (Continued) Patch Number 30 Description PHSS_30688 040722 s700_800 11.23 OV EMANATE15.3 Agent Consolidated Patch. This is a required patch if using the SG SNMP cluster subagent. PHSS_33840 Enables CFS, with CVM 4.
Serviceguard Version A.11.17 Release Notes Fixed in This Version Fixed in This Version JAGaf71623 (SR8606411758): Aborting! Bad election state handling node failure What was the problem? Under rare circumstances, cmcld may abort with the following message: Bad election state handling node failure What was the resolution? Added handling the valid election state. JAGaf71616 (SR8606411751): Use of /etc/cmcluster/rc in /sbin/init.
Serviceguard Version A.11.17 Release Notes Fixed in This Version For example, if the DG is being used for SGeRAC, the messages would look like this: - Node "laurent": Activating disk group dbdg with non-exclusive option. - Node "laurent": Activating disk group ops_dg with non-exclusive option.
Serviceguard Version A.11.17 Release Notes Fixed in This Version What was the resolution? Ignore the status update message. JAGaf69163 (SR8606409265): mistake with ACP causes cmcld to abort on all nodes during cmapplyconf What was the problem? Invalid data can be specified in the USER_NAME field for the access control policies in the cluster ascii file and a cmapplyconf will complete without error.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf68807 (SR8606408905): Serviceguard lans can fail incorrectly when high polling interval used What was the problem? hen the network polling interval (NETWORK_POLLING_TIMEOUT in the cluster configuration file) is configured to 30 seconds, the LAN interface will be marked down even for single miss in the link level messages. Because of this, the LAN will be down for one poll interval.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf66489 (SR8606406583): cmsnmpd sends out trap too early before localswitch and it can get lost What was the problem? The cmsnmpd subagent trap, hpmcSGLocalSwitch may be lost if the trap destination IP address happens to be on the network interface that is in the process of doing a local LAN failover. The trap may be sent before the local LAN failover has completed, so it may be lost.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf63791 (SR8606403867): cmrunnode failed with an assertion What was the problem? If one node crashes while another node is joining the cluster, a third node in the cluster may also crash with the following message: Assertion failed: (cm_cluster->e_state == CM_COMM_VERIFY_COORDINATOR || cm_cluster->e_state == CM_COMM_VERIFY_MEMBER), file: cm/membership.c, line: 118 What was the resolution? Code changed to remove the assertion.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf60449 (SR8606400494): SB/ST: Assertion failed on run: Assertion failed: p_ptr->p_coord_state = What was the problem? A package run/halt/mod command could be processed when cluster reformation is still in progress. This could cause cmcld to hit an assertion, and the node would TOC. What was the resolution? Added additional checks to prevent Package Manager from accepting new commands when it is in reconfiguring state.
Serviceguard Version A.11.17 Release Notes Fixed in This Version A second defect in the code that does the ip address resolution via /etc/hosts made it fail to find the correct hostname if the addresses in the /etc/hosts file were not in the right order. This too would result in various command failures with the message "Permission Denied".
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf50940 (SR8606390795): latest SG patches prevent documented use of IP addresses in cmclnodelist What was the problem? DUPLICATE. See JAGaf56322: SG does not provide highest privileges for nodes with aliases A defect was introduced which broke the ability for Serviceguard to handle IP addresses in the cmclnodelist file. This resulted in seeing "Permission Denied" errors in response to commands.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf46442 (SR8606386288): ServiceGuard allows remote configuration What was the problem? Remote cluster configuration through cmapplyconf reports the following errors: Begin cluster verification... Adding node abc to cluster xyz. Error: Permission denied to abc. ... ... Unable to verify cluster configuration change completion, proceeding anyway.. Completed the cluster creation.
Serviceguard Version A.11.17 Release Notes Fixed in This Version What was the resolution? Code is corrected to now compare the ip address of the sender to any ip addresses listed in the cmclnodelist file. Also, the code was changed to keep searching the ACPs until the hostname with the highest privilege was found.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf42015 (SR8606381803): what(1m) does not show any output for package control scripts What was the problem? The what (1m) command will not display any information about Serviceguard package control scripts. What was the resolution? Correct the format in the package control script.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf40323 (SR8606380087): /etc/cmcluster/ cmknowncmds undocumented and prone to be deleted What was the problem? A new internal file called cmknowncmds now exists in /etc/cmcluster. The file was originally shipped as an empty file giving the customer no idea the importance of the file.
Serviceguard Version A.11.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf35681 (SR8606375378): snmpwalk shows empty hpmcClusterPrimaryNode What was the problem? DUPLICATE. See JAGaf31114: cl_run_node failed due to snmp walk failure In a stressed environment, the cmsnmpd may become unresponsive and log ***Error: get_all_status() failed in /var/adm/SGsnmpsuba.log.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf31114 (SR8606370692): cl_run_node failed due to snmp walk failure What was the problem? In a stressed environment, the cmsnmpd may become unresponsive and log ***Error: get_all_status() failed in /var/adm/SGsnmpsuba.log. When this happens, Serviceguard SNMP traps and mib table will no longer be maintained and the subagent may yield incorrect data about the cluster. What was the resolution? Added a 0.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf28700 (SR8606368136): utils: cl_flog_global_setup() does not close previous log file What was the problem? When cmgmsd log file is switched by gmsetlog -f command, the previous log file is not closed. What was the resolution? Use a new global variable global_flogh to keep the file handle and call cl_flog_destroy to close the old file handle before creating a new file handle when log switch happens. JAGaf26386 (SR8606365756): 11.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf19356 (SR8606358660): Assertion failed: icp->in_state == CL_CONN_INBOUND_READY What was the problem? Serviceguard daemon cmcld might abort if cluster is configured with multiple heartbeats and one of the networks is highly loaded or a local switch is happening on it. The following messages can be seen in syslog: node2 cmcld: Pausing HB connection to xx.xx.xx.xx node2 cmcld: Timed out node node1.
Serviceguard Version A.11.17 Release Notes Fixed in This Version JAGaf11664 (SR8606350852): file permissions (or file creation mask) issues with SG package logfile What was the problem? Package control script log files are created with incorrect permissions. What was the resolution? Control script file permissions are now correct. JAGaf08686 (SR8606347864): It is not possible to configure some combinations of roles What was the problem? In A.11.
Serviceguard Version A.11.17 Release Notes Fixed in This Version • What was the resolution? Made a code change so that LOG_PERIODIC messages no longer go to syslog no matter at what level. JAGae62205 (SR8606298706): Serviceguard package cannot be restarted after hardware monitoring is re-enabled.
Serviceguard Version A.11.17 Release Notes Known Problems and Workarounds Known Problems and Workarounds The following lists known problems for Serviceguard Version A.11.16, at time of publication. This list is subject to change without notice. Contact your HP support representative for up-to-the-moment information. More recent information on known problems and workarounds may be available on the Hewlett-Packard IT Resource Center: http://www.itrc.hp.com (Americas and Asia Pacific) or http://www.europe.
Serviceguard Version A.11.17 Release Notes Known Problems and Workarounds Checking nodes ... Done Checking existing configuration ... Done Interface lan2 on ptest90 has an IPv6 address on it (fec0:0:0:f08::36), but the configuration file doesn't have it. This may be caused by a local switch or changes in the network configuration. Interface lan2 on ptest90 has an IPv6 address on it (fec0:0:0:f08::36), but the configuration file doesn't have it.
Serviceguard Version A.11.17 Release Notes Known Problems and Workarounds • What is the workaround? If the overall disk configuration (number of LUNs) is not large, wait for the command to complete, otherwise terminate the command with CTRL-C. JAGaf36760 (SR8606376483): Uncorrectable write errors on vxvm volumes. • What is the problem? Configurations using greater than 256 LUNs with VxVM on 11i v2 September 2004 update experience uncorrectable write errors.
Serviceguard Version A.11.17 Release Notes Known Problems and Workarounds 1. Halt Serviceguard on one or more of the cluster nodes while the other nodes remain in the cluster, still running CVM 3.2. 2. Perform the upgrade from CVM 3.2 to 3.5 on the nodes which are not running in the Serviceguard cluster, but do not restart them in the Serviceguard cluster when the CVM upgrade is complete. 3.
Serviceguard Version A.11.17 Release Notes Known Problems and Workarounds by cmcld because of the package shutdown. When the customer issues the cmapplyconf, this service is permanently removed from cmcld although cmsrvassistd is still trying to re-start it. Therefore after the cmapplyconf the "ghost" service still cannot be stopped because cmcld denies its existence.
Serviceguard Version A.11.17 Release Notes Software Availability in Native Languages Software Availability in Native Languages The command line interface for Serviceguard Version A.11.17 does not provide Native Language Support. The Serviceguard graphical user interface does provide Native Language Support. See the Release Notes for your version of Serviceguard Manager for information.
