HP HP-UX SNAplus2, Administration Manual

Page: 369 / 398

Appendix D 369
Using SNAplus2 in a High Availability Environment
Using SNAplus2 with MC/ServiceGuard
Table D-2 Suggestions for Defining the SNAplus2 Package
Specifying the Service Command
The Service Command starts a Service, which is an HP-UX process that
ServiceGuard monitors. The termination of the process indicates to
ServiceGuard that the package has failed, and that the package needs to
be migrated to another system. The Service can be the main process that
makes up the package, but for SNAplus2 it is a process that monitors
whether the SNAplus2 software is providing SNA network connectivity.
The best way to determine if an SNAplus2 server is providing SNA
network connectivity is to check the status of each SNAplus2 LS that the
server uses.
One way to check the status of an SNAplus2 LS is with the
snapadmin
start_ls
command. For example,
Item Suggestion
Package Name Use a name that identifies how the SNAplus2
package is being used. For example,
sna
.
Service Name Use the name of the SNAplus2 LS that you are
making highly available. For example,
HALS
.
Service
Command This command will be used to monitor the
SNAplus2 LS. Use the
snapmon
command which
has been designed for this purpose. For example,
/opt/sna/bin/snapmon HALS
. See “Specifying
the Service Command” below for more
information
Package Control
Script Location This is the location of the script to start and stop
the SNAplus2 package on a server. For example,
/etc/cmcluster/sna/sna.cntl
. See
“Customizing the SNAplus2 Package Control
Script” below for more information
IP Address An IP Address must be associated with the
SNAplus2 package even if you are not using the
LAN for SNA network connectivity. See
“Specifying a Package IP Address” for more
information.