376
Appendix D
Using SNAplus2 in a High Availability Environment
Using SNAplus2 with MC/ServiceGuard
Customizing the SNAplus2 Package Control
Script
The last step in defining an SNAplus2 package is customizing the
Package Control Script to instruct ServiceGuard how to start and stop
the SNAplus2 software associated with the package. The example file
that we used in our list of suggestions is
/etc/cmcluster/sna/sna.cntl.
See Table D-2, “Suggestions for
Defining the SNAplus2 Package.” To customize the Package Control
Script, you must use an editor like vi. Package Control Script
customization cannot be done using SAM.
Modifying the PATH variable
Since the run and halt commands will use SNAplus2 executable
programs, you must add the SNAplus2 executable directory to the PATH
variable in the Package Control Script. Add the directory
/opt/sna/bin
to the PATH variable.
Adding Customer Defined Functions
To finish the SNAplus2 package definition, add commands to start and
stop the SNAplus2 package to the Package Control Script. The
commands you will use depend on your specific SNA network
configuration. If possible, design the run and halt commands to migrate
the SNAplus2 package to another server transparently; that is, without
impacting the applications. For the best level of application
transparency, we recommend that you use a client/server configuration,
and that you configure ServiceGuard to activate the same SNAplus2
node, port, and LS on the backup server that is configured to run on the
primary server. This way, the SNAplus2 applications can access the same
set of LUs whether the SNA network connectivity is being provided by
the primary server or the backup server.
NOTE
We recommend that you use a client/server configuration in high
availability environments.
The run and halt commands must be designed to allow ServiceGuard to
migrate the SNAplus2 package from the primary server to the backup
server. If the SNAplus2 package fails on the primary server (which is
indicated by the termination of the snapmon process), ServiceGuard
will invoke the halt commands on the primary server. Most often the
command,
snap stop
, is sufficient because that command will halt all of
Summary of Contents for HP-UX SNAplus2
Page 4: ...4 ...
Page 14: ...14 Contents ...
Page 22: ...22 ...
Page 23: ...23 1 SNA Terms and Concepts ...
Page 65: ...65 2 Introduction to SNAplus2 ...
Page 107: ...107 3 Administering SNAplus2 ...
Page 132: ...132 Chapter3 Administering SNAplus2 Using the Command Line Administration Program ...
Page 133: ...133 4 Basic Configuration Tasks ...
Page 142: ...142 Chapter4 Basic Configuration Tasks Configuring Logging ...
Page 143: ...143 5 Defining Connectivity Components ...
Page 167: ...167 6 Configuring Dependent LUs ...
Page 174: ...174 Chapter6 Configuring Dependent LUs Defining LU Pools ...
Page 175: ...175 7 Configuring APPC Communication ...
Page 208: ...208 Chapter7 Configuring APPC Communication Configuring APPC Security ...
Page 209: ...209 8 Configuring User Applications ...
Page 222: ...222 Chapter8 Configuring User Applications Configuring RJE Workstations ...
Page 223: ...223 9 Configuring Passthrough Services ...
Page 235: ...235 10 Managing SNAplus2 from NetView ...
Page 248: ...248 Chapter10 Managing SNAplus2 from NetView Using UCF ...
Page 249: ...249 11 Managing SNAplus2 Clients ...
Page 300: ...300 Chapter11 Managing SNAplus2 Clients Managing HP UX Clients ...
Page 301: ...301 A Configuration Planning Worksheets ...
Page 337: ...337 B APPN Network Management Using the Simple Network Management Protocol ...
Page 343: ...343 C Configuring an Invokable TP Using snaptpinstall ...
Page 353: ...353 D Using SNAplus2 in a High Availability Environment ...