TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

Maximize the Benefit of the NonStop TCP/IPv6
Architecture
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
3-12
Configuration Examples for the Listening Models
spread the broker’s workload over as many processors as required, achieving
unlimited scalability while presenting a single IP host image to the outside world.

The architecture shortens the path length for data flow by eliminating the hop
between the broker processes and the TCP/IP process, as well as between the
server processes and the TCP/IP process, thereby improving performance.

The architecture lets you run multiple copies of the servers, allowing you to spread
the server’s workload over as many processors as required. This method allows
extensive scalability while presenting a single IP host image to the outside world.

By taking advantage of reactive distribution, you get scalability and performance.
A configuration example for the broker-listening model has not been provided;
however, NonStop CORBA is an example of the broker-listening model. For more
information, see the CORBA 2.6.1 Administration Guide.
Configuration Examples for the Listening
Models
This subsection provides examples of how to configure some of the listening models.
Configuration Example for the Standard Listening Model
This example demonstrates the standard listener model discussed in Standard
Listening Model on page 3-2 configured with round-robin filtering enabled. This
configuration example assumes that you have already configured the basic subsystem.
(See Section 1, Quick Start and Section 5, Example Illustrations and Adding Features
to the Basic Configuration for procedures for configuring the basic subsystem.) This
example only shows you how to configure the listening applications.
The first configuration example of a NonStop TCP/IPv6 environment is shown in
Figure 3-8
on page 3-13. One LISTNER is configured in Processor 0 and its backup
process is in Processor 1. As it receives connection requests on port 21, it spawns
FTPSERV processes and hands off the connection to those processes. The FTPSERV
processes then assume direct control of the connections.