TS Supplement (Includes RFC-1006 Support)

Configuring OSI/TS

RFC-1006 Subsystem Configuration

107751 Tandem Computers Incorporated 2–11

TSP Process in Client Role

In the client role, the subdevices attached to TSP1 have a choice of which NSPDEVICE

to use, either TCP/IP1 or TCP/IP2. Once this assignment is decided, this example is

essentially the same as for a single TSP process client process interfacing with a single

TCP/IP process.

REMOTENSAP is required and specifies the remote IP address on the server side of the

connection. LOCALNSAP is optional. If you don’t specify it, TCP/IP uses its routing

table to determine which local IP address or subnet to use and will use whatever

subnet is available.

Examples 1 and 2 associate the SUs with the local TCP/IP process and the remote IP

addresses.

Example 1:

#lan1a with TCP/IP1 and with IPAddress5

#lan1b with TCP/IP2 and with IPAddress6

#lan1c with TCP/IP2 and with IPAddress7

Example 2:

#lan1a with TCP/IP1 and with IPAddress5

#lan1b with TCP/IP1 and with IPAddress5

#lan1c with TCP/IP2 and with IPAddress6

TSP Process in Server Role

In the server role, the subdevices attached to TSP2 have a choice of which NSPDEVICE

to use, either TCP/IP3 or TCP/IP4. Once this assignment is decided, this example is

essentially the same as for a single TSP process process interfacing with a single

TCP/IP process.

REMOTENSAP is ignored. LOCALNSAP is required and specifies the local IP address on

the server side of the connection.

Examples 1 and 2 associate the SUs with the local TCP/IP process and the local IP

addresses.

Example 1:

#lan2a with TCP/IP3 and with IPAddress5

#lan2b with TCP/IP3 and with IPAddress6

#lan2c with TCP/IP4 and with IPAddress7

Example 2:

#lan2a with TCP/IP3 and with IPAddress5

#lan2b with TCP/IP3 and with IPAddress5

#lan2c with TCP/IP3 and with IPAddress6