Configuring an Ignite-UX Server under HP Serviceguard

18
======= 03/12/09 09:40:42 MDT BEGIN swpackage SESSION
* Session started for user "[e-mail]".
* 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.
* Packaging the bundle
"IUX-Recovery,r=C.7.8.201,a=HP-
UX_B.11.11_32/64,v=HP".
* Package Phase succeeded.
======= 03/12/09 09:40:42 MDT END swpackage SESSION
Now move the package to the remaining nodes one at a time to
swinstall IGNITE on each.
15. Update the Ignite server IP address
Update the Ignite server IP address and execute optional setup_server customizations
on the cluster node where the ha-iux service is running. Note that the Ignite server IP
address defaults to the physical IP address of the last cluster node that Ignite was installed
on. This needs to be updated to the virtual IP address assigned to the Serviceguard
package for Ignite.
# /opt/ignite/bin/instl_adm –t [ha-iux virtual hostname or IP]
The setup_server command may be executed here. Note that the setup_server
option (-n) for NFS mounts does not apply, as these are managed by Serviceguard using
the entries from the control scripts.