HACMP Notes from Ray O'Reilly on 11/16/2005

HACMP controls PV's from coming online not by /etc/filesystems'
	mount		= true
stanza, but by never varying on the Volume Group at all, due to
the 'AUTO ON:' setting of the VG.

lsvg rootvg
VOLUME GROUP:   rootvg                   VG IDENTIFIER:  000b012dc439b47b
VG STATE:       active                   PP SIZE:        32 megabyte(s)
VG PERMISSION:  read/write               TOTAL PPs:      542 (17344 megabytes)
MAX LVs:        256                      FREE PPs:       303 (9696 megabytes)
LVs:            9                        USED PPs:       239 (7648 megabytes)
OPEN LVs:       8                        QUORUM:         2
TOTAL PVs:      1                        VG DESCRIPTORS: 2
STALE PVs:      0                        STALE PPs:      0
ACTIVE PVs:     1                        AUTO ON:        yes     <---- Note !!!
MAX PPs per PV: 1016                     MAX PVs:        32

Normally 'AUTO ON:' is set to yes 'cause you want the VG to come online, but
in a HACMP environment (dncdb1/2, 3/4) this is always set to "no".  Only
if and when HACMP decides to become the active server does it then vary on
the volume group (varyonvg) and mount the file systems.

================================================================================

There are two different terms used to refer to IP addresses in an HACMP
environment;

  - The Pervasive IP address is what you can always rely on to go to
    the machine in question, e.g. 10.225.48.132 for dncdb3 and 10.225.48.133
    for dncdb4.  This address is constant, as contrasted to

  - The Service IP address, which is what clients for this HACMP-controlled
    service know to use to connect to this service.  In the dncdb3/4 world,
    this Service address is 10.225.49.132.  This IP can be on either dncdb3
    or dncdb4, whichever one is active.

================================================================================

On dncdb3/4, see /local/HA_configs for the HACMP start/stop scripts, e.g.
start_apps, which calls hacmp-s1.sh, which does the actual db2start.