HP-UX SNAplus2 R7 Administration Guide

Appendix DUsing SNAplus2 in a High Availability Environment
D.3.7 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.
Figure D–11 Client/Server configuration using Token Ring LAN DLC
Client Client Client Client
3xxx
Communications
Controller
IBM
Host
LAN
Primary HP-UX Server hp_pri
Token Ring Adapter
Backup HP-UX Server hp_back
Token Ring
Token Ring Adapter
Card 0Card 0
QLLC
If you are using QLLC links, both servers must have the same name configured in the X.25 interface card
configuration file. This name is also used in the Interface Card field of the SNAplus2 configuration in the QLLC
Port configuration screen. For example, you might have the following line in the /etc/x25/x25config_0 file
on the primary server:
name card0
which would correspond to the following entry in the QLLC Port configuration screen
220