HP Serviceguard Toolkit for Integrity Virtual Servers User Guide HP Part Number: 5900-1966 Published: September 2011 Edition: 1
© Copyright 2011 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.
Contents 1 HP Serviceguard Toolkit for Integrity Virtual Servers.........................................4 Overview................................................................................................................................4 Advantages.............................................................................................................................4 Dependencies......................................................................................................................
1 HP Serviceguard Toolkit for Integrity Virtual Servers Overview HP Serviceguard toolkit for Integrity Virtual Servers (SG IVS Toolkit) is a toolkit that facilitates seamless integration of HP Integrity Virtual Machines with HP Serviceguard. It has a set of shell scripts that aids in creating Serviceguard package for VM (that is VM-as-Serviceguard-packages) and helps to start, stop, and monitor VM on VM Hosts.
This section identifies the differences between HP Integrity VM Serviceguard toolkit and SG IVS toolkit. HP Integrity VM Serviceguard toolkit SG IVS Toolkit It is part of HP Integrity VM bundle of B.04.30 and earlier It is a new product from HP, and must be installed versions. separately. It supports the legacy and modular style packaging of VM. It supports only modular style packaging. It does not provide any module (ADF file). It provides one module of toolkit-with-toolkit specific attributes.
2 Supported configuration This section explains the supported configuration for VM-as-Serviceguard-packages. Figure 1 (page 6) represents a basic VM-as-a-Serviceguard-package (or, VM guest as packages) model configuration as supported with the SG IVS toolkit. Figure 1 VM as Serviceguard packages In this configuration, a Serviceguard cluster is formed by using VM Host systems as nodes in the cluster.
this case, the shared storage must be defined as VM guest storage devices that are exclusively used by a specific VM guest. The easy deployment script, cmdeployvpkg, offered by the toolkit is used to create the Serviceguard package configuration file to deploy high availability solution to VM guests in Serviceguard environment. This script determines the cluster shared backing store and application data storage used by the VM guest to be packaged.
3 Installing and uninstalling HP Serviceguard toolkit for Integrity virtual servers To install the HP Serviceguard toolkit for Integrity virtual servers: 1. Run the command: # swinstall -s The “SD Install - Software Selection” user interface appears. 2. 3. 4. On the “SD Install - Software Selection” screen, mark the product, “SG-IVS-Toolkit”. To mark the product for installation, select Action > Mark For Install (m) Select Action > Install , to initiate the installation.
Table 3 Scripts for monitoring virtual switch File Name Description Available in Directory vswitchmgr This script is used to monitor and reconfigure “vswitch” during physical networking link (NIC) failover. /sbin/init.d/ K004vswitchmgr Soft link to “vswitchmgr”. /sbin/rc2.d/ S802vswitchmgr Soft link to “vswitchmgr” /sbin/rc3.
4 Using SG IVS toolkit Creating packages You must perform the preconfiguration steps, and then configure the VM guest into an HP Serviceguard package by using either of the following ways: • Using Serviceguard Commands • Using Easy Deployment For information on the preconfiguration steps, see www.hp.com/go/virtualization-manuals→ HP Integrity Virtual Machines and Online VM Migration > HP Integrity Virtual Machines 4.3: Installation, Configuration, and Administration > Creating the Package Configuration.
Attributes 5. 6. Description MONITOR_INTERVAL This is the time interval (in seconds) between the monitor cycles and the default value is 30 seconds. The toolkit monitors the health of the package every [MONITOR_INTERVAL ]seconds. vg This attribute must be assigned to the volume group name, if the VM guest or VM guest application is using the volume group for the backing store. service_name Name of the service that Serviceguard monitors while the package is up.
NOTE: • This script does not include information about attached I/O devices, such as tape, DVD, burner, and changer devices into the package configuration file. • The VM guest must be running when you run the cmdeployvpkg command. Managing packages Running packages To start the VM guest package use the following command: # cmrunpkg Maintaining packages When a package is set to the maintenance mode, the toolkit stops monitoring the status of the VM.
NOTE: HP recommends that you must not use the HP Serviceguard command, cmdeleteconf, because you need to de-associate VM from the Serviceguard package. Converting packages You can convert packages created using the HP Integrity VM Serviceguard toolkit to the SG IVS Toolkit. This depends on the criticality of the downtime for the application running on the VM guest. • Offline package conversion: You can opt for an offline package conversion, if the application downtime is permitted.
3. 4. 5. Run cmcheckconf -P . Run cmapplyconf -P . Run cmrunpkg . NOTE: This method uses the OVMM technique. Therefore, all the OVMM requirements must be considered. Keep a backup of the package directory before you run the cmdeployvpkg command. After cmdeployvpkg command creates the new package configuration file, you must edit, apply, and then run the package.
5 Configuring guest application monitoring service HP Serviceguard VM guest application monitoring service is a program or an agent configured within a VM guest that checks the status of applications configured within the same VM guest. HP supports the monitoring and control of applications within a VM guest configured as an HP Serviceguard package.
In this architecture, the Application Managers and the Application Servers communicate via SSL connections using the JSSE. The Application Manager cmappmgr initiates and maintains a connection with the application server process cmappserver in the monitored VM guest using TCP or IP port 5315 for communications. Its primary function is to launch the specified command and monitor the execution of the same by: • Sending requests to cmappserver, to execute specified processes.
the service_restart value, set for the cmappmgr service in the guest package. If the number of restart attempts exceeds the service_restart value, HP Serviceguard fails over the VM guest package to its configured VM Host failover node, as shown in Figure 4 (page 17). Figure 4 Failover of a VM guest due to an application failure To configure the VM guest application monitoring service: 1. Create and distribute client or server security keys. 2. Configure the cmappmgr.conf file on VM Hosts. 3.
certificate distributed to the client; client public certificate distributed to the server). The default locations for the generated key files are: • For VM Hosts: /etc • For VM guests: ◦ HP-UX/Linux: /opt/hp/cmappserver ◦ Windows: C:\Program Files\Hewlett-Packard\cmappserver Key generation on the VM Host The following three commands must be executed on one VM Host to generate the client.private, client.public and temp.key security keys by using the keytool program.
NOTE: This command prompts for a user name, organization and physical location information to document the use of the key. b. c. keytool -export -alias serverprivate -keystore server.private -file temp.key -storepass serverpw keytool -import -noprompt -alias serverpublic -keystore server.public -file temp.key -storepass public SSL key distribution After the keys are initially created on one VM Host, all other VM Hosts must use the same client.public key. Each VM guest generates its own server.
For Linux VM guests (subdirectory redhat or sles): • Copy the rpm file from the VM Host to a local directory on the VM guest. • To install the required files in the /opt/hp/cmappserver directory in the VM guest, run the command rpm -i cmappserver_rhel5_ia64.rpm (for Red Hat) or rpm -i cmappserver_sles_ia64.rpm (for SLES 10), NOTE: If cmappserver is already installed, use —u instead of I. • Add /opt/hp/cmappserver to the path. • Verify that Java 1.4.2 or 1.5 or 1.
5. To modify the VM guest package to start or monitor specific applications in the VM guests, do one of the following: • Manually edit the existing VM guest package configuration file: To monitor specific applications in a VM guest, a cmappmgr entry is added to the services section of the VM guest package for each monitored application.
NOTE: With the HP Serviceguard A.11.20 release, application monitoring is now supported for VM guests that use online VM guest migration. It is not supported with the HP Serviceguard A.11.19. To support online VM guest migration, all service command strings sent to the VM guest must be unique. This means, if two instances of the same application are started and monitored in the VM guest using cmappmgr, the service strings must be different, even if a space needs to be added to one of them. 6.
You have enter the following application monitor values: Name: Run command: Application timeout: Service restart: Service halt timeout: ping_mon /apps/ping_mon 10 none 300 Hit return to confirm this entry: Enter an additional application monitor? (y/n):n Checking communications with the application monitor server on : slvm1 Merging application monitor service with existing package configuration file Review and/or modify the package configuration file (optional)? (y/n): y Invoking editor : vi on file /etc/
NOTE: 2. 3. This is a requirement of HP Serviceguard A.11.20. To disable application monitoring (that is, comment out cmappmgr calls), edit all the packages. Reapply the packages. Application monitoring is not used while reapplying, therefore, these VM guests can now be live-migrated. NOTE: 4. Check and ensure that the various cmappmgr services are stopped. Live-migrate all the VM guests from one node and upgrade the HP Serviceguard on that node.
NOTE: 6. 7. The services in the VM guests will not be running. Update cmappserver in every guest. For each HP Integrity VM guest package that used VM guest monitoring, do the following: • Halt the package. • Re-enable all the cmappmgr calls in each package. • Reapply the package. • Start the package.
6 Online VM guest package migration Online VM Migration (OVMM) enables a running VM guest and its applications to be moved from one VM Host to another without service interruption. SG IVS toolkit aids OVMM of VM-as-Serviceguard-package for HP-UX guests. OVMM provides minimal application downtime during planned maintenance periods on VM Hosts and manual workload balancing between VM Hosts, while HP Serviceguard provides protection against unplanned hardware and software failures.
7 Troubleshooting This section explains some of the problem scenarios that you might encounter while working with the SG IVS toolkit in a Serviceguard Cluster. Problem Scenario Possible Cause Recommended Action If the syslog/package log contains the When you start a package, the VM Check the network or DNS following error: guest OS is still not up, therefore, configurations on the VM Host or VM cmappmgr fails to communicate with guest or the SSL setup.
8 Limitations This section lists the limitations of SG IVS toolkit in a Serviceguard Cluster: 28 • The online package conversion does not add the custom services and configurations, such as application monitor services, configured for the old package. • The cmdeployvpkg command does not add NFS as backing store in the configuration file. You must manually add it to the configuration file.
9 Support and other resources Information to collect before contacting HP Ensure that the following information is available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact HP Un
HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator website: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://welcome.hp.com/country/us/en/wwcontact.html Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.
IMPORTANT An alert that calls attention to essential information. NOTE An alert that contains additional or supplementary information. TIP An alert that provides helpful information.
A Sample package configuration file for HP Integrity VM guest package This section provides with a sample package configuration file for HP Integrity VM guest package: # # # # # # # ********************************************************************** ****** HIGH AVAILABILITY PACKAGE CONFIGURATION FILE (template) ******* ********************************************************************** ******* Note: This file MUST be edited before it can be used.
service_cmd service_restart service_fail_fast_enabled service_halt_timeout ~ /usr/sbin/cmappmgr -node slvm1 -cmappserver_timeout 10 -service /apps/ping_mon none no 300 33
Glossary ADF Attribute definition file Guest OS Operating system instance installed on the VM Integrity VM HP Integrity Virtual Machines product JRE Java Runtime Environment JSSE Java Secure Socket Extension LVM Logical Volume Manager MSE Multi Server Environment NFS Network File System OVMM Online Virtual Machine Migration Package A grouping of application services (individual HP-UX Processes) under Serviceguard Physical node A single server or nPar (hard partition) SLVM Shared Logic
Index C Configuration guest application monitoring service, 15 Serviceguard Guest Application Monitoring architecture, 15 Creating packages using easy deployment, 11 using Serviceguard commands, 10 I Installation uninstallation, 8 M Managing packages halting packages, 12 maintaining packages, 12 running packages, 12 S SG IVS Toolkit Advantages, 4 Comparison between HPVM toolkit and SG IVS toolkit, 5 Dependecies, 4 Overview, 4 Prerequisites, 4 SG IVS toolkit limitations, 28 Online VM package migration, 26
