HP Serviceguard Version A.11.
Legal Notices © Copyright 1998-2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Printing History ...........................................................................................................................11 1 Serviceguard Version A.11.18 Release Notes................................................................................13 Announcements..................................................................................................................13 Platform Dependencies........................................................................
What’s Not in this Release.............................................................................................25 Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3.....................................................25 About Modular Packages..............................................................................................26 Package Modules.....................................................................................................27 Base Package Modules..........................
Syntax:......................................................................................................................49 Examples..................................................................................................................50 Scope of Monitoring.................................................................................................51 About vgchange -T........................................................................................................
Requirements for Rolling Upgrade....................................................................75 Rolling Upgrade Exceptions....................................................................................75 HP-UX Cold Install.............................................................................................75 HP Serviceguard Storage Management Suite and standalone CVM product................................................................................................................
QXCR1000746305: Site controller pkg failed to start after cmhaltnode -f.....................83 QXCR1000747823: cmviewconf does not display managed packages for SC package..........................................................................................................................83 QXCR1000749527: cmmakepkg -l does not list non-SG modules.................................83 QXCR1000749924: Dependent packages started on non-primary nodes.....................
Known Problems and Workarounds for the Serviceguard Manager Plug-in..............90 JAGag35535: Adding a node to a cluster with Lock LUN fails...............................90 JAGag04773: Clicking on the browser refresh button takes you back to main page..........................................................................................................................91 JAGag32353: With Mozilla or Firefox browser, configuring a SGeRAC package is confusing...............................................
List of Figures 1-1 1-2 1-3 1-4 1-5 1-6 System Management Homepage Login......................................................................58 Serviceguard Cluster...................................................................................................59 System Management Homepage with Serviceguard Manager..................................60 Systems Insight Manager Sign-In Page.......................................................................62 Expanded Left Panel..........................
List of Tables 1 1-1 1-2 1-3 1-4 1-5 1-6 1-7 10 Printing History..........................................................................................................11 Base Modules..............................................................................................................28 Optional Modules.......................................................................................................29 Legacy Configuration-File Parameters and Modular Equivalents.............................
Printing History Table 1 Printing History Printing Date Part Number Edition June 2007 B3935-90108 First Edition October 2007 B3935-90108 Second Edition December 2007 B3935-90114 Third Edition April 2008 B3935-90119 Fourth Edition September 2008 B3935-90124 Fifth Edition The fifth edition includes information on new features included in patches PHSS_38423 and PHSS_38424.
1 Serviceguard Version A.11.18 Release Notes Announcements This section announces the most important features and limitations of Serviceguard A.11.18. For more information, see “What’s in this Release” (page 20). Platform Dependencies This new version of Serviceguard is supported on HP-UX 11i v2 and 11i v3.
classed as Serviceguard components and listed above) via Software Update Manager (SUM). Serviceguard Optional Products Not Bundled The following optional product is not bundled with Serviceguard, but is delivered free with Serviceguard on the Serviceguard Distributed Components CD, and can also be downloaded from http://www.hp.com/go/softwaredepot/ha: • Quorum Server, and the Quorum Server Version A.03.00 Release Notes. SMS A.01.
These new capabilities significantly reduce the number of maintenance tasks that require cluster downtime. See “New Online Networking-Configuration Capabilities” (page 43) and “New Online Timing-Configuration Capabilities” (page 45). Serviceguard Manager Available from the System Management Homepage (SMH) For details, see “What’s in this Release” (page 20) and “About the Serviceguard Manager SMH Plug-In” (page 53).
on HP-UX 11i v1 were the last versions that did). HP-UX 11i v3 does not support these two technologies. The unsupported configurations include physical Token Ring and FDDI interfaces, Virtual LAN (VLAN) interfaces over FDDI or Token Ring, and failover groups of Token Ring and FDDI interfaces in the LAN Monitor Mode of the APA product. Parallel SCSI Dual Cluster Lock Obsolete As of Serviceguard A.11.
NOTE: Remember to do this exercise not only on the node on which the package will normally run, but also on the node with the least resources in the cluster, as a failover or other unexpected circumstances could result in that node running the package. For more information, 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 docs.hp.com) and the comments in the package configuration file.
The download includes Release Notes; follow directions in that document to install the upgrade. Once you have downloaded the software, set the identd -T option to 120 (-T120); this ensures that a connection inadvertently left open will be closed after two minutes. identd is usually started by inetd from /etc/inetd.conf, so you would normally edit that file to set the identd -T option. The -T option may also be available in the form of a patch to earlier Sendmail versions; or for later HP-UX versions.
Support for Veritas Volume Manager (VxVM) Veritas (VxVM) 4.1 and 5.0 from Symantec are supported on HP-UX 11i v3, but VxVM 3.5 is not. If you are running VxVM 3.5 (as part of the Base Product included with HP-UX), you can do a rolling upgrade to Serviceguard A.11.18 on HP-UX 11i v3 with VxVM 4.1 or later. See “Upgrading from an Earlier Serviceguard Release” (page 75) for more information. See also “Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3” (page 25). NOTE: A file created with VxFS 5.
IMPORTANT: If your storage devices are configured with only a single path, or you have disabled multipathing, you should disable PCI Error Recovery; otherwise Serviceguard may not detect when connectivity is lost and cause a failover. For instructions on using the pci_eh_enable parameter to disable PCI Error Recovery, see the “Tunable Kernel Parameters” section of the latest edition of the PCI Error Recovery Product Note in the High Availability collection on docs.hp.com.
New Serviceguard Features Common to HP-UX 11i v2 and 11i v3 • Serviceguard A.11.18 on HP-UX 11i v2 and 11i v3 supports version 5.0 of the Veritas Volume Manager (VxVM), the Veritas Cluster Volume Manager (CVM), and the Veritas Cluster File System (CFS) from Symantec. The 4.1 versions of these products are also supported with Serviceguard A.11.18. See “Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3” (page 25).
— Serviceguard now supports the LACP_AUTO (IEEE 802.3ad Link Aggregation Control Protocol) mode of Auto Port Aggregation (APA), with up to 32 ports per link aggregate; and supports up to eight ports per link aggregate for the MANUAL and FEC_AUTO (Cisco proprietary Fast EtherChannel) modes. (The former maximum for MANUAL and FEC_AUTO was 4 ports per link aggregate, and LACP_AUTO mode was not supported.
• There are new Serviceguard demons: — Lock LUN Daemon: cmldisklockd If a lock LUN is being used, cmdisklockd runs on each node in the cluster and is started by cmcld when the node joins the cluster. — Network Manager Daemon: cmnetd Runs on every node on which cmcld is running. — Utility Daemon: cmlockd Runs on every node on which cmcld is running (though currently not actually used by Serviceguard on HP-UX systems). • Serviceguard A.11.
• Serviceguard now supports cell OL* (online addition and deletion of cells) on HP Integrity servers that support them). For more information about using Serviceguard with partitioned systems, see the white paper HP Serviceguard Cluster Configuration for HP-UX 11i or Linux Partitioned Systems at http://docs.hp.com -> High Availability -> Serviceguard ->White Papers.
What’s Not in this Release • • • • RS232 is no longer supported for the cluster heartbeat. Token Ring and FDDI are no longer supported for the cluster heartbeat and data networks. Version 3.5 of Veritas Volume Manager (VxVM) from Symantec is no longer supported on HP-UX 11i v3, but VxVM 4.1 and 5.0 are supported. The cmviewcl command no longer supports the -r 11.09 option. -r 11.12 and -r 11.16 are still supported.
NOTE: VxVM, CVM and CFS 4.1 are also supported with Serviceguard A.11.18. See the HP Serviceguard Storage Management Suite A.01.01 Release Notes. IMPORTANT: For information about required patches, see the HP Serviceguard Storage Management Suite Release Notes for your version of the Storage Management Suite. Serviceguard Extension for Faster Failover is supported with CVM and CFS 4.1 and 5.0. Serviceguard NFS Toolkit supports CFS 5.0.
Package Modules The tables that follows show the new package modules and the configuration parameters each module includes. You can use cmmakepkg -l (letter l) to see a list of all available modules, including non-Serviceguard modules such as those supplied in the HP Toolkits. Base Package Modules At least one base module (or default or all, which include the base module) must be specified on the cmmakepkg command line. Parameters in bold are new for A.11.
Table 1-1 Base Modules 28 Module Name Parameters Comments failover package_name module_name module_version package_type node_name auto_run node_fail_fast_enabled run_script_timeout halt_script_timeout successor_halt_timeout script_log_file operation_sequence log_level failover_policy failback_policy priority Base module. Use as primary building block for failover packages.
Optional Package Modules Add optional modules to a base module if you need to configure the functions in question. Table 1-2 Optional Modules Module Name Parameters Comments dependency dependency_name dependency_condition dependency_location Add to a base module to create a package that depends on one or more other packages.
Table 1-2 Optional Modules (continued) 30 Module Name Parameters Comments filesystem concurrent_fsck_operations concurrent_mount_and_umount_op-erations fs_mount_retry_count fs_umount_retry_count fs_name fs_directory fs_type fs_mount_opt fs_umount_opt fs_fsck_opt Add to a base module to configure filesystem options for the package. pev pev_ Add to a base module to configure environment variables to be passed to an external script.
NOTE: The default form for parameter names in the modular package configuration file is lower case; for legacy packages the default is upper case. There are no compatibility issues; Serviceguard is case-insensitive as far as the parameter names are concerned. These release notes use lower case, unless the parameter in question is used only in legacy packages, or the context refers exclusively to such a package. New Parameters The following parameters are new as of A.11.18.
operation_sequence Defines the order in which the scripts defined by the package’s component modules will start up. See the package configuration file for details. This parameter is not configurable; do not change the entries in the configuration file. log_level Determines the amount of information printed to stdout when the package is validated, and to the script_log_file when the package is started and halted.
ip_subnet_node In a cross-subnet configuration, specifies which nodes an ip_subnet is configured on. If no ip_subnet_nodes are listed under an ip_subnet, it is assumed to be configured on all nodes in this package’s node_name list. See also “monitored_subnet_access” and “About Cross-Subnet Configurations” (page 40). New for modular packages. For legacy packages, see “Configuring Cross-Subnet Failover” in Chapter 7 of Managing Serviceguard. cluster_interconnect_subnet Specifies an IPv4 address.
HP recommends setting this parameter to yes in Metrocluster installations using EMC SRDF. IMPORTANT: subsystem. vxdisk scandisks can take a long time in the case of a large IO New for modular packages as of the September 2008 Patch (page 13). Equivalent to VXVM_DG_RETRY in the legacy package control script. pev_ Specifies a package environment variable that can be passed to an external_pre_script, external_script, or both, by means of the cmgetpkgenv (1m) command.
If more than one external_script is specified, the scripts will be executed on package startup in the order they are entered into this file, and in the reverse order during package shutdown. HP supplies a template for external scripts: $SGCONF/examples/ external_script.template. For more information, see “About External Scripts” in Chapter 4 of Managing Serviceguard, and the comments in the package configuration file.
Table 1-3 Legacy Configuration-File Parameters and Modular Equivalents (continued) Legacy Parameter Modular Parameter SUBNET monitored_subnet * SERVICE_NAME service_name* SERVICE_FAIL_FAST_ENABLED service_fail_fast_enabled SERVICE_HALT_TIMEOUT service_halt_timeout RESOURCE_NAME resource_name RESOURCE_POLLING_INTERVAL resource_polling_interval RESOURCE_START resource_start RESOURCE_UP_VALUE resource_up_value VXVM_DG_RETRY vxvm_dg_retry STORAGE_GROUP USER_NAME user_name USER_HOST user_h
Table 1-4 Legacy Control-Script Parameters and Modular Equivalents (continued) Legacy Parameter Modular Parameter FS_TYPE[] fs_type FS_MOUNT_OPT[] fs_mount_opt FS_UMOUNT_OPT[] fs_umount_opt FS_FSCK_OPT[] fs_fsck_opt CONCURRENT_VGCHANGE_OPERATIONS concurrent_vgchange_operations VGCHANGE vgchange_cmd CVM_ACTIVATION_CMD cvm_activation_cmd VX_VOL vxvol_cmd VG[] vg CVM_DG[] cvm_dg VXVM_DG[] vxvm_dg DEACTIVATION_RETRY_COUNT deactivation_retry_count KILL_PROCESSES_ACCESSING_RAW_DEVICES k
IMPORTANT: These rules apply to both legacy and modular packages. Restrictions on the values of these parameters in previous Serviceguard releases were less stringent. Packages that use values for these parameters that do not conform to the new rules will continue to run, but if you reconfigure them, you will need to change the values; cmcheckconf and cmapplyconf will enforce the new rules.
Multi-node packages run simultaneously on more than one node in the cluster. Failures of package components such as applications, services, EMS resources, or subnets, will cause the package to be halted only on the node on which the failure occurred. Relocatable IP addresses cannot be assigned to multi-node packages. IMPORTANT: If the package uses volume groups, they must be activated in shared mode: vgchange -a s, which is available only if the SGeRAC add-on product is installed.
Other Package Changes The patches listed under “September 2008 Patch” (page 13) provide the following new capabilities: • Serviceguard now supplies information explaining why a package has shut down.
In addition, in a site-aware disaster-tolerant cluster, you can use the SITE_PREFERRED policy to configure packages to fail over to a node on a preferred site (for example, to prevent a package from failing over to a node at a remote site when a local node is eligible); and you can use the -S option to cmviewcl to restrict output to information about the local site.
• Because Veritas Cluster File System from Symantec (CFS) requires link-level traffic communication (LLT) among the nodes, Serviceguard cannot be configured in cross-subnet configurations with CFS alone. But CFS is supported in specific cross-subnet configurations with Serviceguard and HP add-on products such as Serviceguard Extension for Oracle RAC (SGeRAC); see the documentation listed below. • • • • • Each package subnet must be configured with a standby interface on the local bridged net.
IMPORTANT: Although cross-subnet topology can be implemented on a single site, it is most commonly used by extended-distance clusters, and specifically site-aware disaster-tolerant clusters, which require HP add-on software. Design and configuration of such clusters are covered in the disaster-tolerant documentation delivered with Serviceguard. For more information, see the following documents at http://www.docs.hp.
• You cannot add interfaces or modify their characteristics unless those interfaces, and all other interfaces in the cluster configuration, are healthy. There must be no bad NICs or non-functional or locally switched subnets in the configuration, unless you are deleting those components in the same operation.
The networking portion of the resulting clconfig.ascii file looks something like this: NODE_NAME ftsys9 NETWORK_INTERFACE lan1 HEARTBEAT_IP 192.3.17.18 #NETWORK_INTERFACE lan0 #STATIONARY_IP 15.13.170.18 NETWORK_INTERFACE lan3 # Possible standby Network Interfaces for lan1, lan0: lan2. NODE_NAME ftsys10 NETWORK_INTERFACE lan1 HEARTBEAT_IP 192.3.17.19 #NETWORK_INTERFACE lan0 # STATIONARY_IP 15.13.170.
(Network-Attached Storage) context to denote a virtual entity derived from one or more physical disks. As of Serviceguard A.11.18 you can configure a LUN as the cluster lock. Keep the following points in mind when choosing a device for a lock LUN: • • • • • • • • All the cluster nodes must be physically connected to the lock LUN. Connections between the nodes and the lock LUN must be Fibre Channel only; parallel SCSI is not supported.
system and application configuration files and scripts to use persistent device files and in some cases new commands and options; the process is described in the white papers Migrating from HP-UX 11i v2 to HP-UX 11i v3 and LVM Migration from Legacy to Agile Naming Model HP-UX 11i v3 at http://www.docs.hp.com. If you cold-install HP-UX 11i v3, sets of both legacy and persistent device files are automatically created.
NOTE: You are not required to move to LVM 2.0 volume groups and everything will work as before if you do nothing. If you do use LVM 2.0 volume groups, you can still manage them with the same commands as before, although you may have to make minor changes to any scripts you use that parse the output of lvdisplay, vgdisplay, pvdisplay or vgscan, as the output of these commands has changed slightly. In addition, new options are available for some commands. For more information, see the white paper LVM 2.
on installing a guest depot.) Serviceguard uses information it derives from the VM guest depot to set the timeout to the optimal value. If any VM node does not have a VM guest depot, Serviceguard may not be able to obtain the information it needs to set the optimal timeout, and in that case it sets the additional timeout to the maximum value, 70 seconds. IMPORTANT: This additional timeout extension represents a net addition to the time it takes for the cluster to re-form.
[-D, --log-level <1-7>] [-t, --poll-interval ] [...] A brief description of each parameter follows: -h or --help Displays the usage, as listed above, and exits. NOTE: Do not include the help or version parameters in your service command; this will result in immediate package failure at runtime. -v or --version Displays the monitor version and exits. -O or --log-file Specifies a file for logging (log messages are printed to the console by default).
This command monitors a single volume at log level 0, with a polling interval of 10 seconds, and prints all log messages to the console.
nodes and the Quorum Server. You can do this from the command line or in Serviceguard Manager. IMPORTANT: This capability requires Quorum Server Version A.03.00. For details and instructions, including patch information, see the HP Serviceguard Quorum Server Version A.03.00 Release Notes at http://docs.hp.com -> High Availability -> Quorum Server. Access changes as of A.11.16 Serviceguard version A.11.16 introduced a new access method. As of A.11.
Considerations when Installing Serviceguard When you install Serviceguard for the first time on a node, the node is not yet part of a cluster, and so there is no Access Control Policy. For instructions on how to proceed, see the subsection “Allowing Root Access to an Unconfigured Node” under “Configuring Root-Level Access” in Chapter 5 of the Managing Serviceguard manual. About the Serviceguard Manager SMH Plug-In HP Serviceguard Manager B.01.
New Features HP Serviceguard Manager version B.01.01 supports Serviceguard A.11.18 on HP-UX 11i v2 and HP-UX 11i v3. The following are new capabilities in B.01.
• • Openview integration is done via HP SIM. No file save – Serviceguard Manager A.05.01 had the ability to save a snapshot of the current clusters monitored, and display it later. This feature is mainly used for comparing configuration changes, which you can now do with DSAU. Limitations • Using Serviceguard Manager, you can create only legacy packages. But you can monitor and administer both legacy and modular packages.
Before Using HP Serviceguard Manager: Setting Up You must have, or have done, the following before you can start using HP Serviceguard Manager: • • At least one cluster member node with Serviceguard A.11.18 and Serviceguard Manager B.01.01 installed. The hpuxswTOMCAT product. hpuxswTOMCAT is installed by default with HP-UX. To check that it is on your system, use a command such as: swlist -l fileset | grep TOMCAT • • • Version 2.2.
Table 1-5 Accessing Serviceguard Manager Scenario Scenario Use Case Number of Clusters Serviceguard Version Serviceguard Manager Version See for more info 1 Single cluster management 1 A.11.18 B.01.01 (page 57) A.11.17.01 B.01.00 2 Multi-cluster management 1 or more cluster(s) A.11.16 A.11.17.01 A.05.01 (page 60) 3 Web-based multi-cluster management more than 1 cluster A.11.16 - A.11.18 A.05.01 with HP SIM 5.
1. Enter the standard URL “http://:2301/” For example http://clusternode1.cup.hp.com:2301/ Figure 1-1 System Management Homepage Login 2. When the System Management Homepage login screen appears, enter your login credentials and click Sign In. The System Management Homepage for the selected server appears. From the Serviceguard Cluster box, click the name of the cluster. 58 Serviceguard Version A.11.
Figure 1-2 Serviceguard Cluster NOTE: If a cluster is not yet configured, then you will not see the Serviceguard Cluster section on this screen. To create a cluster, from the SMH Tools menu, you must click Serviceguard Manager link in the Serviceguard box first, then click Create Cluster. The figure below shows a browser session at the HP Serviceguard Manager Main Page.
Figure 1-3 System Management Homepage with Serviceguard Manager Number Description 1 System Management Homepage (SMH) menus. 2 HP Serviceguard Manager pull-down menus. 3 HP Serviceguard Manger tabs. 4 Overall cluster status indicator. Click this icon to troubleshoot issues. 5 Easy to understand status icons. 6 Use the check boxes to multi-select nodes or packages from which to take action. • To select all, select the check box located in the left corner of the table header.
• • One or more clusters with Serviceguard version A.11.16 through A.11.17.01 Serviceguard Manager version A.05.01 installed Launching Serviceguard Manager from Windows Here are 2 ways to launch Serviceguard Manager in Windows: • • By default, a shortcut icon is placed on your desktop (labelled SG Manager). Click it to launch the program. When installed, it has the simple command without options. You will be prompted to enter the options once the program opens.
Figure 1-4 Systems Insight Manager Sign-In Page 2. When the Systems Insight Manager login screen appears, enter your login credentials and click Sign In. 3. From the left-hand panel, expand Cluster by Type. 62 Serviceguard Version A.11.
Figure 1-5 Expanded Left Panel 4. Expand HP Serviceguard, and click on a Serviceguard cluster. The following screen appears if you click on a Serviceguard cluster running A.11.
Figure 1-6 Serviceguard Manager Page NOTE: If you click on a cluster running an earlier Serviceguard release, the page will display a link that will launch Serviceguard Manager A.05.01 (if installed) via Java Webstart. Patches and Fixes No patches are required for Serviceguard Manager B.01.01. For information about known problems and workarounds, see “Known Problems and Workarounds for the Serviceguard Manager Plug-in” (page 90).
The following documents relate to Serviceguard A.11.18 and related high availability products. The latest versions can be found on the web at http://docs.hp.com-> High Availability. • • • • • • • • • • Managing Serviceguard, 15th Edition. This manual has been revised for the A.11.18 release and the additional new features announced in these Release Notes under “New Features for September 2008 Patch” (page 18) and (page 20). HP Serviceguard Quorum Server Version A.03.
NOTE: For HP-UX 11i v2 systems, continue to use Managing Systems and Workgroups in the HP-UX 11i v2 Operating Environments section of docs.hp.com. • • The latest HP Auto Port Aggregation Release Notes and other APA documentation under Auto Port Aggregation (APA) in the I/O Cards and Networking Software section of docs.hp.com. The latest version of Using HP-UX VLANs and other documentation under Virtual LAN in the I/O Cards and Networking Software section of docs.hp.com.
Mixed Clusters “Mixed cluster” has several meanings in the context of Serviceguard. The following are support statements for various types of mixed cluster. Mixed Serviceguard Versions You cannot mix Serviceguard versions in the same cluster; all nodes must be running the same version of Serviceguard. The sole exception to this rule is a rolling upgrade, during which Serviceguard versions can be mixed temporarily, but no cluster configuration changes are allowed.
For more information about mixed-hardware-architecture clusters, see Configuration Rules for a Mixed HP 9000 /Integrity Serviceguard Cluster at http://www.docs.hp.com -> High Availability -> Serviceguard —> White Papers. Mixed HP-UX Operating-System Revisions Before A.11.18, Serviceguard required all nodes in a cluster to be running the same HP-UX revision, except during a rolling upgrade. Serviceguard A.11.
and restrictions for rolling upgrades are in Appendix E of Managing Serviceguard, which you can find at http://www.docs.hp.com -> High Availability -> Serviceguard. See also “Upgrading from an Earlier Serviceguard Release” (page 75). It is also possible to upgrade the HP-UX version without upgrading Serviceguard, and so avoid the rolling upgrade restrictions.
NOTE: Native multipathing, which is enabled by default on HP-UX 11i v3, can be used on 11i v3 nodes in a heterogeneous cluster. • • • • The cluster is not using Oracle RAC. (SGeRAC is not supported in a heterogeneous cluster because Oracle RAC does not support mixing HP-UX versions within a single RAC cluster.) The cluster is not using Veritas CVM or CFS. If you are updating nodes from HP–UX 11i v2 to 11i v3, you must use update-ux; cold install is not supported in this context.
Bastille Compatibility To ensure compatibility between Serviceguard (and Serviceguard Manager) and Bastille, do the following, depending on your environment: • • • • If Bastille is started using Sec10Host (host.config) level lock down, change SecureInetd.deactivate_ident=Y to SecureInetd.deactivate_ident="N" If Bastille is started using Sec20MngDMZ (mandmz.config) level lock down, change SecureInetd.deactivate_ident=Y to SecureInetd.deactivate_ident=N If Bastille is started using SIM.
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. Before installing, check /etc/services and be sure no other program has reserved these ports.
Installing Serviceguard on HP-UX Dependencies The following are required by Serviceguard. They are part of the HP-UX Base Operating Environment: • • Open SSL, which includes the OPENSSSL-RUN and OPENSSL-LIB filesets. The EventMonitoring bundle, which contains the EMS-CORE and EMS-CORE-COM filesets. Installing Serviceguard Serviceguard will automatically be installed when you install the HP-UX Mission Critical Operating Environment (MCOE).
• • • • • • • • • • • • Cluster-OM.CM-OM Cluster-OM.CM-OM-AUTH Cluster-OM.CM-OM-AUTH-COM Cluster-OM.CM-OM-COM Cluster-OM.CM-OM-MAN Package-CVM-CFS.CM-CVM-CFS Package-CVM-CFS.CM-CVM-CFS-COM Package-Manager.CM-PKG Package-Manager.CM-PKG-MAN Cluster-Monitor.CM-CORE Cluster-Monitor.CM-CORE-COM Cluster-Monitor.CM-CORE-MAN NOTE: There are files in CM-CORE that are reserved for HP support. Do not change these files.
Upgrading from an Earlier Serviceguard Release • • • For information about supported Serviceguard upgrade paths, see the support matrix at docs.hp.com -> High Availability -> Support Matrixes. This release of Serviceguard requires HP-UX 11i v2 or 11i v3. For information about HP-UX upgrade paths, see the HP-UX Installation and Upgrade Guide for the target version of HP-UX at http://www.docs.hp.com -> -> Installing and Updating. If you are upgrading from a release earlier than A.11.
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. Specifically you cannot do a rolling upgrade if you are using the Veritas clustering capabilities - CVM and CFS. In the case of CVM, this applies whether you purchase it as part of a Storage Management bundle, or as a standalone product. For more information, see the Veritas 5.
1. 2. 3. Serviceguard must be halted (not running) on the node from which the swremove command is issued. The system from which the swremove command is issued must be removed from the cluster configuration. (If the node is not removed from the cluster configuration first, swremove will cause the current cluster to be deleted.) The swremove command should be issued from one system at a time.
Fixed in This Version This section shows which defects listed as known problems in the Release Notes for the previous release have now been fixed. Specifically, the fixes below are to defects reported in the A.11.17 and A.11.17.01 Release Notes, and earlier versions of the A.11.18 Release Notes. NOTE: Serviceguard A.11.18 also includes all fixes already included in patches to earlier Serviceguard versions; these fixes are not necessarily documented here.
Resolution: Fixed in patch PHNE_34671, “Cumulative ARPA Transport Patch” for HP-UX 11i v2 (see “Patches for this Version” (page 77)). Now if ENOMEM is encountered, the IP is left on the source interface and cleaned up on the destination interface.
Resolution: The select()system call is now retried a maximum of ten times when it fails because of an interrupted system call. JAGag25508 (SR8606470417): Log file permissions set to 666 Problem: Permissions for log files defined in /etc/cmcluster.conf were set to 666 (allowing anyone to read or write to the file). Resolution: These permissions are now set to 644, restricting writes to the owner of the file.
NIC teaming (bonding) as in the fourth case listed in the warning text (VMware ESX Server). JAGag46475 (SR8606494542): cmquerycl -f line output may display incorrect VG disk device files • • Problem: If a shared volume group used different device file names in /etc/lvmtab on different nodes, the output displayed by cmquerycl -f line showed the device files for all nodes as configured for the first node referenced in the -n option of cmquerycl.
QXCR1000739586: Serviceguard does not log .cm_start_time message correctly in syslog after abort • Problem: If cmcld aborted and you restarted the cluster without first rebooting the node on which the abort occurred, the following message appeared in syslog.log: It appears that package applications or resources may be active on this node. Re-starting the cluster could cause data corruption.
• packages configured for the cluster, not just for the package that was being configured or deleted via cmapplyconf or cmdeleteconf. Resolution: The warnings are now given correctly — only for a package that is being added or modified. QXCR1000741571: Hanging node problem causing cluster to go down • • Problem: A hang on one node could cause multiple cluster re-formations, until eventually the entire cluster failed.
QXCR1000766057: cmviewcl package state “blocked” is not documented • • Problem: cmviewcl shows the per-node state of multi-node packages as blocked, but the manpage does not explain what “blocked” means. Resolution: “Blocked” means that the multi-node package has never run on the node. This may be because a dependency has not been met, or auto_run is set to no. This information has been added to the cmviewcl manpage.
Unable to receive device query message from ogre: Software caused connection abort Unable to receive device query message from sweetee: Software caused connection abort cmquerycl -c willow2 Unable to receive device query message from ogre: Software caused connection abort Unable to receive device query message from sweetee: Software caused connection abort Failed to gather configuration information.
JAGag07820: Handling invalid cluster name with * / \ space characters is broken • • Problem: When you specified an invalid character such as * \ /or a space in the Cluster Name field and tried to jump to other tabs, Serviceguard Manager did not warn the user of the problem. Resolution: Serviceguard Manager now checks for valid cluster name before attempting to create a new cluster.
QXCR1000591254: Tooltip value incorrect • • Problem: The tooltip over the Service Status column in a Serviceguard Manager property page listed uninitialized as one of the possible values, which is not correct. Resolution: The incorrect value has been removed. QXCR1000741159: Incorrect error message • Problem: Serviceguard Manager displayed a misleading error message if you attempted to edit a Serviceguard modular package: Cannot modify A.11.
QXCR1000820311 SGMgr does not show that MetroCluster is configured when using the Site Aware Disaster Tolerant Architecture (SADTA) • • Problem: Serviceguard Manager Plug-in did not show that Metrocluster was configured when Site Aware Disaster Tolerant Architecture was being used. Serviceguard Manager also incorrectly showed that data replication was disabled for the Site Controller package (hrdb_sc).
This workaround involves managing the nodes in the cluster so that all nodes in the clusters are running only CVM 3.2 or only CVM 3.5, but never a combination of the two. To do this: 1. 2. 3. 4. 5. 6. Halt Serviceguard on one or more of the cluster nodes while the other nodes remain in the cluster, still running CVM 3.2. Perform the upgrade from CVM 3.2 to 3.
NOTE: You can apply the patch without a reboot. On a system to which the patch has been applied, you will be able to perform online replacement of hot-swappable cards (without bringing down the cluster). See “Replacing LAN or Fibre Channel Cards” in Chapter 8 of Managing Serviceguard for more information. (You can find the manual at http://docs.hp.com -> High Availability -> Serviceguard.
JAGag04773: Clicking on the browser refresh button takes you back to main page • • Problem: Clicking the browser refresh button from any Serviceguard Manager page takes you back to the Serviceguard Manager main page. Workaround: There is no workaround for this problem.
JAGag29458: In matrix views, empty columns are not displayed • • Problem: Matrix views do not display columns that are empty. Workaround: There is no workaround for this problem. JAGag31375: SGeSAP missing from cluster extensions • • Problem: You may have the SGeSAP extension installed or configured, but the Extension tab does not display SGeSAP in the list. Workaround: There is no workaround for this problem.
Patch A patch to a release may be issued in response to a critical business problem found by a Serviceguard customer, or a patch may enable new features. (Such features do not affect the running of an existing Serviceguard cluster until you activate them, for example by reconfiguring the cluster or reworking a package.) In the case of a patch, the following is guaranteed: • Patch-specific release testing is performed before the patch is posted. • Existing functionality, scripts, etc.
• • • • • • Korean Traditional Chinese Standard French Standard German Standard Italian Standard Spanish Serviceguard documentation is translated into the following languages: • Japanese • Simplified Chinese • Korean • Traditional Chinese 94 Serviceguard Version A.11.
