RSC/MP 7.3 Installation and Configuration Guide

Best Practices Guide
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011
F-9
Scenario 2
Possible improvements to this configuration
•
To alleviate the heavy loading on the PIPEMAN process, consider running
additional instances of PIPEMAN, each with its own set of TDPs and NIFs (see
Figure F-6). Use PARAM PIPEINI to direct each TDP to its intended instance of
PIPEMAN. Give each PIPEMAN instance its own SystemName setting, and
configure each workstation to use one of those names. Configure DNS to resolve
each host name appropriately (in the example shown in the diagram, DNS resolves
each of two host names to two different IP addresses using the round-robin
method).
Figure F-6. Scenario 2 improved with multiple PIPEMAN instances
Network
Servers
Servers
Servers
NonStop host
HOST1
CDT017
TDP
PIPEMAN
NIF
TDP
NIF NIFNIF
$ZTC0 $ZTC1 $ZTC2 $ZTC3
TDP
PIPEMAN
Application
NIF
RSCPIPE
workstation
(group “B”)
TCP/IP
workstation
(group “A”)
PIPEMAN
Application
NIF
TCP/IP
RSCPIPE
10.1.90.23
10.1.90.2210.1.90.2110.1.90.20
DNS serves addresses round-robin:
Workstations calling HOST1A get
10.1.90.20 or 10.1.90.21
Workstations calling HOST1B get
10.1.90.22 or 10.1.90.23
PIPEMAN
TDP
SystemName
HOST1B
SystemName
HOST1A
Group A workstations use HOST1A
Group B workstations use HOST1B