
378
Appendix D
Using SNAplus2 in a High Availability Environment
Using SNAplus2 with MC/ServiceGuard
start the node on the backup server until SNAplus2 recognizes that
the primary server is down. This time period can be lengthy (up to 30
minutes).
Therefore, if the backup server is running SNAplus2, it is safest to
completely stop the SNAplus2 software on the backup server before
issuing the activation commands. The complete command set, then is:
function customer_defined_run_cmds
{
snap stop
snap start
snapadmin init_node
snapadmin start_port, port_name=HAPORT
snapadmin start_ls, ls_name=HALS
}
With these commands specified in your Package Control Script, you will
be able to start an SNAplus2 LS called
HALS
on a backup server when
the primary server fails to keep the LS active. These commands work
best in an SNAplus2 client/server environment where the applications
run on client systems and automatically attempt to reestablish LU-LU
sessions anytime a session outage occurs. For standalone environments,
you will also have to consider how your applications will be impacted by
various failures, including entire server system failures.
I/O Compatibility Constraints
The previous section described how to customize your Package Control
Script for the best level of application transparency. To allow the same
SNAplus2 node, port , and LS to run on multiple systems, it is important
that they have compatible networking hardware. In a client/server
configuration, SNAplus2 uses only one configuration file for all of the
SNAplus2 systems defined to be part of the same logical network. To
have more than one server capable of activating the same node, port and
LS , the SNA networking hardware must be installed and configured
similarly on each system. The requirements are different for each type of
link.
LANS
For 802.3, Token Ring, and FDDI LANs, both servers must have the
same type of LAN card installed. The LAN cards on both systems must
be identified by the same SNAplus2 card number.
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 ...