Introduction to Networking for NonStop NS-Series Servers (H06.03+, J06.03+)

Networking on Integrity NonStop Servers
Introduction to Networking for HP Integrity NonStop NS-Series Servers—529874-003
1-11
Integrity NonStop Server Networking Compared to
Other Platforms
transport-service providers (TCP6SAM processes) in the same TACL session in which
you define the filter key.
You configure NonStop TCP/IPv6 with round-robin filtering enabled in the Guardian
environment and the OSS environment inherits the DEFINE that establishes the
environment. You must start the application process in the same TACL session in
which you set the filter key that establishes round-robin filtering for the port or, if you
use different TACL sessions to start the different application processes, you must
define the same filter key in each of those TACL sessions. The general steps for using
round-robin filtering are:
1. Find a TCP6SAM process by issuing the SCF LISTDEV command.
2. Find an IP address associated with the TCP6SAM process by issuing the SCF
INFO SUBNET command for the TCP6SAM process.
(The remainder of this example assumes that IP address 1.1.1.1 is available for
the $ZSAM6 process.)
3. Configure your application to listen on 1.1.1.1. This action is also known as
“binding” to a port and IP address. (See the TCP/IP Programming Manual for more
information about binding custom applications, or see the configuration manuals in
the NonStop Technical Library (NTL) for any NonStop applications you plan to use
for information about binding to a particular IP address as opposed to binding to
INADDR_ANY.)
4. Start your application processes in as many processors as you want. Note that
NonStop TCP/IPv6 must be configured in all the processors in which you intend to
run application instances. (In most cases, if NonStop TCP/IPv6 is configured on
the system at all, it is configured in all 16 processors.) Start each application
instance in a unique processor. (See the TCP/IPv6 Configuration and Management
Manual for more information about avoiding port collisions in round-robin
configurations.)
Fault-Tolerance and Scalability on the NonStop Server
When you have configured for scalability, the failure of one or more processors does
not impact the availability in any way:
•
Availability of an application is not impacted by a failed processor because the
application process is replicated.
•
Availability of Internet accessibility is not impacted by a failed processor because
you have running IP stacks configured on the running processors with the IP
address still available so clients do not have to talk to an alternate IP address.
•
Recovery of scalability is not affected by a failed processor because when the
processors are reloaded and applications are restarted, the applications
automatically resume their scaled configuration without disruption to the single IP
view. The re-instantiated applications start using the IP address that had been
configured previously.