HP-UX SNAplus2 R7 Administration Guide

Appendix DUsing SNAplus2 in a High Availability Environment

Figure D–3 Applications using multiple servers

Client

3xxx

Communications

Controller

S800

Server

IBM

Host

LAN

S800

Server

The second way an application can use multiple servers is to have one SNAplus2 conﬁguration that is used by

multiple HP 9000 systems. For example, suppose two server systems are connected to an SNA network through

Token Ring ports. The SNAplus2 conﬁguration contains information about the deﬁnition of SNAplus2 nodes, ports,

and LSs. Since it is a client/server conﬁguration, it does not contain information about which server will activate

those components. Let’s suppose one system is designated a primary server and another is designated a backup

server. Most often the primary server is used in production to provide SNA connectivity for mission critical SNA

applications that run on client systems. The backup server provides non-critical connectivity to the SNA network

for development purposes. When the primary system is not available, the same node, ports, and LSs are activated

on the backup system without any SNAplus2 conﬁguration changes.

For example, suppose the following names are used for the SNAplus2 conﬁguration:

Table D–1 Example SNA system names

Component Primary Server Backup Server

System Name hp_pri hp_back

SNAplus2 Node HANODE DEVNODE

SNAplus2 Port HAPORT DEVPORT

SNAplus2 LS HALS DEVLS

Local LU aliases HALU01...HALU09 DEVLU01...DEVLU05

Note

The above example will be used throughout this appendix to explain many different aspects

of high availability systems.

208