Configuring an Ignite-UX Server under HP Serviceguard

ManualsBrandsHP ManualsSoftwareHP Serviceguard Software

Configuring an Ignite-UX server under HP Serviceguard

Table of Contents

About this document............................................................................................................................. 3

Intended audience ............................................................................................................................... 3

Advantage of running Ignite-UX under Serviceguard ................................................................................ 3

Setting up Ignite-UX to run under Serviceguard ........................................................................................ 3

Serviceguard packages and scripts .................................................................................................... 3

Procedure to set up Ignite under Serviceguard ..................................................................................... 4

1. Create an LVM volume group to manage the shared file systems ................................................... 4

2. Create logical volumes for the shared file systems ........................................................................ 5

3. Create mount points for the shared file systems ............................................................................ 6

4. Add the -s option to /usr/lbin/tftpd .................................................................................. 7

5. Mount /var/opt/ignite and create required directories on the first cluster node ........................ 7

6. Unmount /var/opt/ignite on the first cluster node and deactivate the volume group .................. 8

7. Configure group for exclusive access and export ......................................................................... 8

8. Import volume group data on all cluster nodes ............................................................................. 8

9. Copy NFS toolkit cluster scripts in place ...................................................................................... 8

10. Create package config and scripts .......................................................................................... 9

11. Edit parameters in Ignite scripts and config files on the first node as follows. ................................ 9

12. Copy completed package directory to all nodes ..................................................................... 11

13. Add the new package to the cluster on the first node ............................................................... 11

14. Bring up the package on each node and install Ignite-UX ......................................................... 12

15. Update the Ignite server IP address ........................................................................................ 18

16. Create archive directories for cluster nodes ............................................................................ 19

17. Add clients and create recovery archives ............................................................................... 19

Best practices .................................................................................................................................... 19

Upgrading Ignite-UX ....................................................................................................................... 19

Inactive cluster nodes and swverify .............................................................................................. 19

Other depots under shared file systems ............................................................................................. 19

Booting from the cluster using /etc/bootptab ................................................................................ 20

Edit scripts on all cluster nodes for NFS client mounts ......................................................................... 20

When using the Ignite UI or commands, always use the virtual server hostname and IP for the package ... 20

Managing recovery images for cluster nodes..................................................................................... 20

Summary of content (22 pages)

PAGE 1
Configuring an Ignite-UX server under HP Serviceguard Table of Contents About this document............................................................................................................................. 3 Intended audience ............................................................................................................................... 3 Advantage of running Ignite-UX under Serviceguard ................................................................................
PAGE 2
For more information ..........................................................................................................................
PAGE 3
About this document This white paper describes the procedure for installing Ignite-UX on an HP Serviceguard cluster running HP-UX 11i v3. It is assumed you have a cluster up and running, there is shared storage available for recovery archives, Serviceguard NFS Toolkit is installed, and Ignite-UX is not installed. This paper covers configuring Ignite-UX to use an LVM shared volume and was written using the September, 2008 DCOE, which contains Serviceguard A.11.18.00 (T1905CA) and Serviceguard NFS Toolkit A.
PAGE 4
 File systems to export - only the active cluster node has exported file systems Procedure to set up Ignite under Serviceguard 1. Create an LVM volume group to manage the shared file systems This volume group will contain /etc/opt/ignite, /opt/ignite/boot, and /var/opt/ignite. This must be on a RAID array and must be accessible by each of the other cluster nodes. You must have approximately 1 GB of free disk space available in /opt/ignite/boot. For this example, we have a 104 GB disk.
PAGE 5
The name of the volume group is not important; you may use any name supported by Serviceguard instead of vg01. If you do use an alternative name, substitute any reference to vg01 in this documentation with the name you have chosen. 2. Create logical volumes for the shared file systems You will need logical volumes for /etc/opt/ignite, /var/opt/ignite, and /opt/ignite/boot on the first cluster node.
PAGE 6
Mirror copies Consistency Recovery Schedule LV Size (Mbytes) Current LE Allocated PE Stripes Stripe Size (Kbytes) Bad block Allocation IO Timeout (Seconds) # lvdisplay /dev/vg01/lvol2 --- Logical volumes --LV Name VG Name LV Permission LV Status Mirror copies Consistency Recovery Schedule LV Size (Mbytes) Current LE Allocated PE Stripes Stripe Size (Kbytes) Bad block Allocation IO Timeout (Seconds) # lvdisplay /dev/vg01/lvol3 --- Logical volumes --LV Name VG Name LV Permission LV Status Mirror copies Consis
PAGE 7
# # # # # # # # # 4. mkdir mkdir mkdir chown chmod chown chmod chown chmod –p /etc/opt/ignite –p /var/opt/ignite –p /opt/ignite/boot bin:bin /var/opt/ignite 555 /var/opt/ignite bin:bin /etc/opt/ignite 755 /etc/opt/ignite bin:bin /opt/ignite/boot 555 /opt/ignite/boot Add the -s option to /usr/lbin/tftpd Add the -s option to the /usr/lbin/tftpd file on all cluster nodes that can run the Serviceguard package containing Ignite-UX. Each cluster node that can run Ignite-UX must have an entry in /etc/inetd.
PAGE 8
# # # # # # # 6. chmod chown chmod chown chmod chown chmod 755 /var/opt/ignite/clients bin:bin /var/opt/ignite/data 755 /var/opt/ignite/data bin:bin /var/opt/ignite/recovery 755 /var/opt/ignite/recovery bin:bin /var/opt/ignite/recovery/archives 755 /var/opt/ignite/recovery/archives Unmount /var/opt/ignite on the first cluster node and deactivate the volume group # umount /var/opt/ignite # vgchange -a n vg01 Volume group "vg01" has been successfully changed. 7.
PAGE 9
10. Create package config and scripts Create the package configuration file and the package control script template for Ignite on the first node. # cmmakepkg -p /etc/cmcluster/ha-iux/nfs.conf The package template has been created. This file must be edited before it can be used. # cmmakepkg -s /etc/cmcluster/ha-iux/nfs.cntl Package control script is created. This file must be edited before it can be used. 11. Edit parameters in Ignite scripts and config files on the first node as follows.
PAGE 10
if [[ ! -f /etc/dhcptab && -f /etc/opt/ignite/dhcptab ]];then # If it's not a if [[ rm ln fi fi symlink at this point it should be. ! -L /etc/dhcptab ]];then /etc/dhcptab -s /etc/opt/ignite/dhcptab /etc/dhcptab # If /etc/dhcptab exists and so does the /etc/opt/ignite/dhcptab # move the original dhcptab aside and symlink it to the ignite # one. if [[ -f /etc/dhcptab && -f /etc/opt/ignite/dhcptab ]];then mv /etc/dhcptab /etc/dhcptab.iux.
PAGE 11
test_return 52 } /etc/cmcluster/ha-iux/nfs.conf PACKAGE_NAME ha-iux NODE_NAME * RUN_SCRIPT /etc/cmcluster/ha-iux/nfs.cntl HALT_SCRIPT /etc/cmcluster/ha-iux/nfs.cntl MONITORED_SUBNET 15.1.48.0 MONITORED_SUBNET_ACCESS FULL SERVICE_NAME nfs.monitor SERVICE_FAIL_FAST_ENABLED no SERVICE_HALT_TIMEOUT 300 /etc/cmcluster/ha-iux/nfs.flm NFS_FLM_HOLDING_DIR="/var/opt/ignite/sm" /etc/cmcluster/ha-iux/nfs.mon NFS_FILE_LOCK_MIGRATION=1 12.
PAGE 12
NODE sgiux3 sgiux4 sgiux5 sgiux6 STATUS up up up up STATE running running running running UNOWNED_PACKAGES PACKAGE ha-iux STATUS down STATE halted AUTO_RUN disabled NODE unowned # 14. Bring up the package on each node and install Ignite-UX Bring up your package on the first node, followed by a swinstall of IGNITE. Execute /opt/ignite/lbin/pkg_rec_depot to create the recovery_cmds depot on the first node.
PAGE 13
* Target connection succeeded for "sgiux3:/". * Source connection succeeded for "iuxbld:/depot/Ignite-UX/WEB/opt/trunk/curr". * Source: iuxbld:/depot/Ignite-UX/WEB/opt/trunk/curr * Targets: sgiux3:/ * Software selections: IGNITE,r=C.7.9.90,a=HP-UX_B.11.00_32/64,v=HP Ignite-UX.BOOT-COMMON-IA,r=C.7.9.90,a=HPUX_B.11.11_32/64,v=HP,fr=C.7.9.90,fa=HP-UX_B.11.11_32/64 Ignite-UX.BOOT-COMMON-PA,r=C.7.9.90,a=HPUX_B.11.11_32/64,v=HP,fr=C.7.9.90,fa=HP-UX_B.11.11_32/64 Ignite-UX.BOOT-KRN-11-11,r=C.7.9.90,a=HPUX_B.11.
PAGE 14
* The execution phase succeeded for "sgiux3:/". * Analysis and Execution succeeded. NOTE: More information may be found in the agent logfile using the command "swjob -a log sgiux3-0001 @ sgiux3:/". ======= 02/19/09 14:11:38 MST interactive) (jobid=sgiux3-0001) END swinstall SESSION (non- Execute pkg_rec_depot on the first node only: # /opt/ignite/lbin/pkg _rec _depot * Generating the product specification file.
PAGE 15
NOTE: Creating new target depot "/var/opt/ignite/depots/recovery_cmds". * Selection Phase succeeded. * Beginning Analysis Phase. * Analysis Phase succeeded. * Beginning Package Phase. NOTE: You have specified the "package_in_place" option. The software you have selected will be packaged with references to the actual source files. No source files will be copied into the target depot "/var/opt/ignite/depots/recovery_cmds". * Packaging the product "Ignite-UX". * Packaging the fileset "Ignite-UX.
PAGE 16
* Session started for user "root@sgiux3". * Beginning Selection * Targets: sgiux3 * Objects: /var/opt/ignite/depots/recovery_cmds * Selection succeeded. ======= 03/12/09 09:40:39 MDT interactive) END swreg SESSION (non- * Creating IUX Recovery bundles. ======= 03/12/09 09:40:40 MDT BEGIN swpackage SESSION * Session started for user "root@sgiux3.fc.hp.com". * Source: sgiux3:/var/opt/ignite/tmp/psf.
PAGE 17
* * Beginning Selection Phase. * Reading the Product Specification File (PSF) "/var/opt/ignite/tmp/psf.3605". * Reading the bundle "Ignite-UX-11-23" at line 11. * Selection Phase succeeded. * Beginning Analysis Phase. * Analysis Phase succeeded. * Beginning Package Phase. * Packaging the bundle "Ignite-UX-11-23,r=C.7.8.201,a=HPUX_B.11.11_32/64,v=HP". * Package Phase succeeded.
PAGE 18
======= 03/12/09 09:40:42 MDT BEGIN swpackage SESSION * Session started for user "root@sgiux3.fc.hp.com". * Source: sgiux3:/var/opt/ignite/tmp/psf.3664 * Target: sgiux3:/var/opt/ignite/depots/recovery_cmds * Software selections: * * Beginning Selection Phase. * Reading the Product Specification File (PSF) "/var/opt/ignite/tmp/psf.3664". * Reading the bundle "IUX-Recovery" at line 11. * Selection Phase succeeded. * Beginning Analysis Phase. * Analysis Phase succeeded. * Beginning Package Phase.
PAGE 19
16. Create archive directories for cluster nodes Log into the virtual service for the package and create archive directories for all cluster nodes. # # # # 17. cd /var/opt/ignite/recovery/archives mkdir -p sgiux3 sgiux4 sgiux5 sgiux6 chown bin:bin * cd / Add clients and create recovery archives Add all cluster nodes as clients and then create recovery archives for each inactive node (not running the ha-iux package).
PAGE 20
Booting from the cluster using /etc/bootptab All bootptab entries must be maintained on the active cluster node, as this copy is linked to the shared version /etc/opt/ignite/bootptab. The local copies of /etc/bootptab on the inactive cluster nodes must not contain entries for clients that will be booting from the Ignite server. Edit scripts on all cluster nodes for NFS client mounts The /etc/dfs/dfstab file is not used in this configuration; the Serviceguard control scripts will export all file systems.
PAGE 21
Managing Serviceguard Ignite-UX Administration Guide HP-UX 11i v3 Release Notes HP-UX System Administrator’s Guide Some or all of these documents are available on the Instant Information media and in printed form. Product information regarding Ignite-UX is available at: http://www.hp.
PAGE 22
© Copyright 2009, 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.