Using SNAplus2 in a High Availability Environment

SNAplus2 High Availability Features

Figure D-4SNAplus2 on Primary and Backup Servers

 

 

 

 

 

 

 

 

 

 

Client

Client

 

Client

 

Client

 

 

 

 

 

 

 

Primary HP-UX Server hp_pri

Production Configuration

Node

.................HANODE

LS.....................

HALS

Port...................

HAPORT

LUs...................

HALUO1...HALU09

LAN

Backup HP-UX Server hp_back

Development Configuration

Node

................DEVNODE

LS....................

DEVLS

Port..................

DEVPORT

LUs..................

DEVUO1...DEVLU09

Token Ring

3xxx

Communications

Controller

IBM

Host

Whenever the primary server is about to become unavailable (during preventative maintenance periods, for example), the SNA connectivity is switched to the backup server through the following steps:

Step 1. The SNAplus2 Port HAPORT is started on the backup server using the command snapadmin start_port, port_name=HAPORT.

Step 2. The SNAplus2 LS HALS is started on the backup server, if it is configured to be operator started, using the command snapadmin start_ls, ls_name=HALS.

Appendix D

363