TCP/IP (Parallel Library) Configuration and Management Manual
Configuring Parallel Library TCP/IP for Complex and
Heavy-Use Environments
HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual—522271-006
3-26
Example for Two Gateways — Standard Listening
Model
The SCFSBNT2 File
The SCFSBNT2 file adds and starts subnets and routes.
For the ADD SUBNET command, the subnet name can be anything under seven
alphanumeric characters long beginning with an alpha character. The DEVICENAME
attribute, which specifies the logical interface (LIF) name associated with the adapter
that the Parallel Library TCP/IP process accesses, is required. (See step e on page 1-4
for determining an appropriate LIF.)
In SCFSBNT2, four subnets are started (SN0, SN1, SN2, and SN3). Because
LISTNER binds to the socket with INADDR_ANY, it listens for incoming connections on
all configured subnets. So in this configuration, incoming connection requests are
accepted from both subnets.
Example 3-8. SCFSBNT2 File for TCPIPUP6
=== SCFSBNT2 ===== SCFSBNT2 ==== SCFSBNT2 ========
== SCF command file to ADD and START SUBNETs Example 3-7
ALLOW ALL ERRORS
ALLOW ALL WARNINGS
==
ASSUME PROCESS $ZZTCP
== Add subnets
ADD SUBNET SN0,TYPE ETHERNET,DEVICENAME LAN01,IPADDRESS 150.50.130.2, &
SUBNETMASK %HFFFFFF00
STOP SUBNET LOOP0
ALTER SUBNET LOOP0, IPADDRESS 127.1
ADD SUBNET SN1,TYPE ETHERNET,DEVICENAME LAN02,IPADDRESS 150.60.64.2, &
SUBNETMASK %HFFFFFF00
ADD SUBNET SN2,TYPE ETHERNET,DEVICENAME LAN03,IPADDRESS 150.60.64.3, &
SUBNETMASK %HFFFFFF00
ADD SUBNET SN3,TYPE ETHERNET,DEVICENAME LAN04,IPADDRESS 150.50.130.4, &
SUBNETMASK %HFFFFFF00
== Add route ROU0 to direct traffic destined for network 128 to GTWY1
ADD ROUTE ROU0, DESTINATION 128.30.0.0, GATEWAY 150.50.130.1
==
== Add route ROU2 to direct all other traffic to GTWY2
ADD ROUTE ROU2, DESTINATION 0.0.0.0, GATEWAY 150.60.64.1
== Start subnets & routes
START SUBNET *
START ROUTE *
==
=========== END OF SCFSBNT2 ============= END OF SCFSBNT2 ===========
Note. If the LISTNER had bound to the IP address specified for the subnet (in this case
150.60.64.3), instead of INADDR_ANY, the LISTNER would have been limited to accepting
incoming connections only on SN1. While LISTNER would not do this, other applications
following this model might. Hence, you should configure the listener with INADDR_ANY to
accept connections on all subnets. (See Subnet-Level Binding: How to Isolate Subnets in a
Single-IP Environment on page 2-4 for a related discussion of INADDR_ANY.)