HP NonStop Networking Overview

HP NonStop Networking Overview

HP Part Number: 529874-005Published: March 2009Edition: J06.06 and all subsequent J-series RVUs, H06.17 and all subsequent H-series RVUs

© Copyright 2009 Hewlett-Packard Development Company, L.P.

Legal Notice

Confidential computer software. Valid license fromHP required for possession, use or copying. Consistentwith FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor’s standard commercial license.

The information contained herein is subject to changewithout notice. The onlywarranties forHP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPshall not be liable for technical or editorial errors or omissions contained herein.

Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.

Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Intel, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and othercountries.

Java is a U.S. trademark of Sun Microsystems, Inc.

Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks, and IT DialTone and The Open Group are trademarks of The OpenGroup in the U.S. and other countries.

Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, andMotif are trademarks of the Open Software Foundation, Inc. OSFMAKESNOWARRANTYOF ANYKINDWITH REGARD TO THEOSFMATERIAL PROVIDEDHEREIN, INCLUDING, BUTNOT LIMITED TO, THEIMPLIEDWARRANTIESOFMERCHANTABILITYAND FITNESS FORA PARTICULARPURPOSE. OSF shall not be liable for errors containedherein or for incidental consequential damages in connection with the furnishing, performance, or use of this material.

© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. The OSF documentation and the OSF software to which it relates are derived in partfrom materials supplied by the following:© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation. ©1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc. © 1987, 1988, 1989, 1990, 1991 Hewlett-PackardCompany. © 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute ofTechnology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. © 1990, 1991SiemensNixdorf InformationssystemeAG.© 1986, 1989, 1996, 1997 SunMicrosystems, Inc. © 1989, 1990, 1991 Transarc Corporation.OSF softwareand documentation are based in part on the Fourth Berkeley SoftwareDistribution under license fromThe Regents of theUniversity of California.OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, ConradC. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the Universityof California.

Table of Contents

About This Document.........................................................................................................7Supported Release Version Updates (RVUs)..........................................................................................7Intended Audience.................................................................................................................................7New and Changed Information in This Edition.....................................................................................7Document Organization.........................................................................................................................7Related Information................................................................................................................................7Publishing History..................................................................................................................................8HP Encourages Your Comments............................................................................................................8

1 Networking on Integrity NonStop Systems..................................................................9Networking Hardware Products Available on H-Series and J-Series RVUs..........................................9Networking Software Products Available on H-Series and J-Series RVUs..........................................12Platform Interoperability .....................................................................................................................13What’s Unique About Networking on Integrity NonStop Systems.....................................................15

Integrity NonStop System Networking Compared to NonStop S-Series Server Networking.......15Integrity NonStop System Networking Compared to Other Platforms ........................................16

Network Scalability ...................................................................................................................17Application Scalability ..............................................................................................................18Scaling Your Application on the NonStop System ....................................................................19Fault-Tolerance and Scalability on the NonStop Server ...........................................................20Ethernet Failover: Fault-Tolerant Connectivity .........................................................................20Logical Network Partitioning (LNP) and Providers..................................................................20Persistence .................................................................................................................................22

What's Unique About Networking on Integrity NonStop BladeSystems............................................22Summary Comparison of NonStop TCP/IP Products on H-Series and J-Series RVUs........................22

2 Networking Concepts ................................................................................................25Address Resolution ..............................................................................................................................25Name Resolution ..................................................................................................................................25

HOSTS File ......................................................................................................................................25Domain Name System (DNS) .........................................................................................................26

Allocation of IP Addresses ...................................................................................................................26Routers .................................................................................................................................................26Switches ................................................................................................................................................27Gateways ..............................................................................................................................................27Network Interface Name .....................................................................................................................27Firewalls ...............................................................................................................................................28IP Security (IPSec).................................................................................................................................28IPv6.......................................................................................................................................................29

3 Planning for Migrating Networking Solutions to H-Series and J-Series RVUs........31Planning Your Networking Solutions ..................................................................................................31

SNAX/XF (Includes Function From SNAX/APN) ..........................................................................31X.25 Communications .....................................................................................................................32Selecting Your TCP/IP Product .......................................................................................................33

Migrating From a Platform Other Than a NonStop Server..................................................................33Internet Application Product Documentation .....................................................................................34

Table of Contents 3

Index.................................................................................................................................35

4 Table of Contents

List of Figures1-1 Integrity NonStop System P-Switch Connection to a NonStop S-Series I/O Enclosure...............111-2 Integrity NonStop BladeSystem Connection to a NonStop S-Series I/O Enclosure.....................111-3 Connecting Legacy Systems With Integrity NonStop Systems Running H-Series RVUs............131-4 Connecting Legacy Systems With Integrity NonStop BladeSystems (J-Series RVUs)..................151-5 Connecting Legacy SystemsWith IntegrityNonStopNS-Series SystemsRunning J-Series RVUs

(NonStop NS2000).........................................................................................................................151-6 Transparent Network Scalability, Multiple Hosts.........................................................................171-7 DNS Round-Robin Address Rotation...........................................................................................181-8 Round-Robin Filtering in the NonStop TCP/IPv6 and CIP Environments...................................191-9 Conventional TCP/IP:Data From the Interface is Restricted toApplicationsUsing theAssociated

Process ..........................................................................................................................................212-1 IPv6 Tunneling..............................................................................................................................293-1 Products for SNAX/XF Using the IOAM Enclosure.....................................................................323-2 Products for X.25 Communications for H-Series or J-Series RVUs...............................................33

5

List of Tables1-1 Comparison of NonStop TCP/IP Products....................................................................................221-2 Comparison of Communications Adapters and CLIMs...............................................................243-1 Internet Application Product Documentation..............................................................................34

6 List of Tables

About This DocumentThis manual provides an overview of networking on the J-series and H-series release versionupdates (RVUs) on Integrity NonStop systems, including supported hardware configurationsand migration and planning information.

Supported Release Version Updates (RVUs)This manual supports J06.06 and all subsequent J-series RVUs and H06.17 and all subsequentH-series RVUs until otherwise indicated in a replacement publication.

Intended AudienceThismanual is for network administrators new to theNonStop server environment and for thosemigrating from the G-series RVUs to the H-series or J-series RVUs, information technologyplanners (both customer and sales support), andGlobalMissionCritical SolutionCenter (GMCSC)analysts looking for information about the Integrity NonStop systems.Information about other kinds of networking solutions, information about the Expand subsystem,and background information about NonStop server concepts and components such as theinput/output processes and the ServerNet LAN Systems Access (SLSA) subsystem are includedin the Introduction to Networking for HP NonStop S-Series Servers. For a broader networkingbackground, see that manual.

New and Changed Information in This EditionThis manual has been updated to incorporate support of the NonStop NS2000.

Document Organization

ContentTitle

Describes fundamentals of networking on Integrity NonStop Systems. Providesnetwork interoperability topology diagrams.

Chapter 1 “Networking onIntegrity NonStop Systems”

Describes IP networking concepts.Chapter 2 “NetworkingConcepts ”

Describes migrating your networking implementations from a G-series RVUs toH-series and J-series RVUs as well as from other environments.

Chapter 3 “Planning forMigrating NetworkingSolutions to H-Series andJ-Series RVUs”

Related InformationTo plan for networking on Integrity NonStop systems, use this manual. Depending on the tasksyou are performing, you might also need these related manuals:• Cluster I/O Protocols (CIP) Configuration and Management Manual• DNS Configuration and Management Manual• LAN Configuration and Management Manual• Expand Configuration and Management Manual• Gigabit Ethernet 4-Port Adapter Installation and Support Guide• Introduction to Networking for NonStop S-Series Servers• SWAN Concentrator Installation and Support Guide• SWAN 2 Concentrator Installation and Support Guide• TCP/IP Configuration and Management Manual

Supported Release Version Updates (RVUs) 7

• TCP/IPv6 Configuration and Management Manual• WAN Subsystem Configuration and Management ManualAlso see the planning guide for your system (for example, the NonStop BladeSystem PlanningGuide) for a list of all related manuals.

Publishing History

Publication DateProduct VersionPart Number

July 2005N.A.529874-001

May 2006N.A.529874-002

November 2006N.A.529874-003

November 2008N.A.529874-004

March 2009N.A.529874–005

HP Encourages Your CommentsHP encourages your comments concerning this document. We are committed to providingdocumentation that meets your needs. Send any errors found, suggestions for improvement, orcompliments to:[email protected] the document title, part number, and any comment, error found, or suggestion forimprovement you have concerning this document.

8

[email protected]

1 Networking on Integrity NonStop SystemsThis section provides a high-level overview of networking on H-series and J-series RVUs onIntegrity NonStop systems. Topics discussed in this section include:• Networking Hardware Products Available on H-Series and J-Series RVUs• Networking Software Products Available on H-Series and J-Series RVUs (page 12)• Platform Interoperability (page 13)• What’s Unique About Networking on Integrity NonStop Systems (page 15)• What's Unique About Networking on Integrity NonStop BladeSystems (page 22)• SummaryComparison ofNonStop TCP/IP Products onH-Series and J-Series RVUs (page 22)

Networking Hardware Products Available on H-Series and J-Series RVUsThe Gigabit Ethernet 4-port ServerNet adapter (G4SA) is the only Ethernet adapter that can beinstalled in an I/O Adapter Module (IOAM) enclosure. There are two IOAMs in an IOAMenclosure. The IOAMalso supports the Fibre Channel ServerNet adapter (FCSA),which providesaccess to various storage devices.The Internet Protocol (IP) Cluster I/O Module (CLIM) provides Ethernet connectivity for theseH-series and J-series environments:• H-series RVUs on NonStop NS16000 series servers, where the IP CLIM can be used in

addition to the IOAM for connectivity, but cannot replace all functionality of the IOAM• J-series RVUs on NonStop BladeSystems, where it can be used in addition to the IOAM or,

in combinationwith the StorageCLIMandCLIM-attacheddevices, to replace the functionalityof the IOAM

• J-series RVUs on NonStop NS2000 series systems, where it can be used in combination withthe Versatile I/O (VIO). (In this environment, the StorageCLIM is required because all storageis CLIM-attached. See the NonStop Storage Overview for more information about storageoptions.)

The installation slots for G4SAs, FCSAs andCLIMs differ by servermodel. Formore information,see the planning guide for your server model (for example, the Integrity NonStop NS16000 SeriesPlanning Guide).You can use other networking hardware products by connecting some Integrity NonStop servermodels to aNonStop S-series I/O enclosure that has IOMF2 components installed. This connectionis made from the system processor switch (p-switch) or ServerNet switch. This option is notavailable on the NonStop NS2000 series server.

Networking Hardware Products Available on H-Series and J-Series RVUs 9

Figure 1-1 Integrity NonStop System P-Switch Connection to a NonStop S-Series I/O Enclosure

10 Networking on Integrity NonStop Systems

Figure 1-2 Integrity NonStop BladeSystem Connection to a NonStop S-Series I/O Enclosure

Legacy NonStop S-series networking I/O adapters supported through the NonStop S-series I/Oenclosure include:

NOTE: Support for these products is only for legacy adapters already existing in theenvironment. These products have reached end-of-sale status.

• GESA, FESA, and E4SA (Ethernet adapters)• TRSA (Token-ring)• ATM3SA (Asynchronous Transfer Mode 3–port ServerNet adapter)The Versatile I/O (VIO) enclosure provides connectivity on some servers. The VIO enclosuresupports Ethernet and, for some servers, fibre channel connectivity.On NonStop NS-series servers, ServerNet wide area network (SWAN) concentrators use TCP/IPto connect through the G4SA or CLIM, through Ethernet ports in the VIO enclosure or throughother Ethernet adapters in a NonStop S-series I/O enclosure. On NonStop BladeSystems, SWANconcentrators connect through the CLIM or G4SA. On NonStop NS2000 systems, SWANconcentrators connect through the VIO or CLIM.

Networking Hardware Products Available on H-Series and J-Series RVUs 11

Networking Software Products Available on H-Series and J-Series RVUsMost of the networking software available for the G-series RVUs is also available on H-seriesand J-series RVUs, including:• AM3270 Access Method• Asynchronous Terminals and Printer Processes• ATM• ATP6100 WANPRINT• Cluster I/O Protocols (CIP) (Not all IntegrityNonStop systems support CIP; see “Networking

Hardware Products Available on H-Series and J-Series RVUs” (page 9))• DNS 9.x• Envoy• EnvoyACP/XF• Expand• NonStop TCP/IPv6• NonStop TCP/IP (conventional)• OSI/AS• OSI/FTAM• OSI/MHS• OSI/TS• Port Access Method (PAM)• QIO• ServerNet LAN Systems Access (SLSA)• SNAX High Level Support (SNAX/HLS)• SNAX/XF (includes SNAX/APN functionality)• SNMP• Spooler• Spooler FastP Network Print Processes• Spooler Plus• TELSERV• TN3270e• TR3271 Tributary Access Method• Wide area network (WAN) subsystemNetworking software available only on G-series RVUs includes:• 6100 TINET Multi-PT Supervisor-PDG• 6100 UTS-40 Multi-PT Supervisor• 6100 UTS-40 Multi-PT Tributary• 6100 VIP Multi-PT Supervisor• Domain Name Server (DNS) (T6021) (Replaced by DNS 9.x)• Enform• Fiber Optic Extension (FOX) Gateway• Multilan Access method and File Server• NonStop IPX/SPX• Novell LAN Print Spooler• Parallel Library TCP/IP (functionality available in NonStop TCP/IPv6 on Integrity

NonStop servers)• TANDEMNBT NETBIOS for IPX• TANDEMNBT NETBIOS for TCP


Platform InteroperabilityIntegrityNonStop systems can communicate directlywith aNonStopK-series server over Expand.SomeNonStopNS-series servers can also communicate indirectlywith aNonStopK-series serverthrough a NonStop S-series server or a ServerNet cluster switch.

NOTE: Not all IntegrityNonStop systems support ServerNet clustering. Formore information,see the planning guide for your server model (for example, the Integrity NonStop NS16000 SeriesPlanning Guide).

Figure 1-3 shows interoperability between multiple NonStop servers.

Figure 1-3 Connecting Legacy Systems With Integrity NonStop Systems Running H-Series RVUs

The ServerNet cluster switch connects to the p-switch of some Integrity NonStop systems. Forinformation about including the IntegrityNonStop system in a ServerNet cluster, see the ServerNetCluster Supplement for NonStop NS-Series Servers.Figure 1-4 shows interoperability between multiple NonStop servers.

Platform Interoperability 13

Figure 1-4 Connecting Legacy Systems With Integrity NonStop BladeSystems (J-Series RVUs)


Figure 1-5 Connecting Legacy Systems With Integrity NonStop NS-Series Systems Running J-SeriesRVUs (NonStop NS2000)

What’s Unique About Networking on Integrity NonStop SystemsIf you are new to the Integrity NonStop systems, you should be aware of differences betweenits networking architecture and solutions and the architecture of other platforms, including otherNonStop systems. This subsection explains:• Integrity NonStop System Networking Compared to NonStop S-Series Server Networking• Integrity NonStop System Networking Compared to Other Platforms

Integrity NonStop System Networking Compared to NonStop S-Series ServerNetworking

Themain difference to be aware of between theNonStop S-series server and the IntegrityNonStopsystems is that some of the networking technology of theNonStop S-series server has been portedto the Integrity NonStop system, but the hardware for that legacy networking technology isaccessible only by connecting to the NonStop S-series server I/O enclosure. (See NetworkingSoftware Products Available on H-Series and J-Series RVUs (page 12) for a list of all networkingproducts available.)

What’s Unique About Networking on Integrity NonStop Systems 15

Integrity NonStop System Networking Compared to Other PlatformsThe Integrity NonStop system clustering technology makes it possible for the system to appearas multiple hosts. Also, the system, when combined with the parallel processing architecture oftheNonStop TCP/IPv6 or CIP product, can appear as a single hostwhile allowing all 16 processorsto service one port. The latter feature allows for high scalability of TCP/IP client applications.The NonStop TCP/IPv6 and CIP products offer the unique ability to bind multiple servers to asingle port. The listening application instances can run in different processors, bind to a sharedIP address and port, and so service a single IP image with 16 processors of computing power.This feature, called round-robin filtering, allows for scalability of the listening application (inthis example, the web server process). By sharing a port, the web server process can provide asingle-IP host image to the world through either a single IP address or, in the multi-homedsituation, usingDNS round-robin address rotation throughmultiple IP addresses. In the scenariowhere theweb server processes are sharing an IP address, the answer that the authoritative nameserver process provides for the web server process is the same for all 16 instances of thatapplication server. Requests that come into the web server process at that IP address aredistributed among the 16 web server processes.For example, you can run a website using iTP Secure WebServer on your Integrity NonStopsystem, enable round-robin filtering with NonStop TCP/IPv6 or CIP, and benefit in two waysfrom the parallel TCP/IP architecture. First, you can run multiple httpd server processes (thelistening processes) each bound to the same port and IP address; this action scales your httpdserver process up to 16 processors. Second, no interprocess hop occurs from the processorcontaining the listening process and a processorwith TCP/IP access to the communication adapter.CIP extends this functionality to allow more than one process per processor to serve a single IPaddress.

NOTE: Round-robin filtering needs to be enabled for NonStop TCP/IPv6 and CIP.

NOTE: NonStop TCP/IPv6 had a limitation of one listening process per processor per port. CIPdoes not have this limitation. There can be many listening processes per processor per port.

Additionally, theNonStopTCP/IPv6 andCIP architectures allowdirect access fromeach processorin a node to the adapter or CLIM. Direct access to the adapter is distinct from the architecture ofconventionalNonStop TCP/IP,which can involve an interprocess hop fromaprocessor containingthe TCP/IP stack to the processor containing the application.Formore information about the parallel TCP/IP architecture available onNonStop servers, aboutthe models for listening applications and how they benefit from this architecture, and forprocedures for configuring the networking environment for round-robin filtering, see theTCP/IPv6Configuration andManagementManual. For information about configuring CIP, see the Cluster I/OProtocols (CIP) Configuration and Management Manual.

NOTE: The models for listening applications described in the TCP/IPv6 Configuration andManagement Manual also apply to CIP.

For information about the iTP Secure WebServer, see the iTP Secure WebServer SystemAdministrator’s Guide.The remainder of this subsection details the unique characteristics of networking in theNonStopserver environment.You can use various methods for scaling your DNS implementation, some of which are uniqueto the NonStop server and some of which are enhanced by the NonStop server architecture. Youcan also use various methods for scaling your network interface capacity as well as scaling yourapplication through DNS capabilities.


For the purposes of this discussion we make the distinction between:• Network Scalability• Application Scalability

Network ScalabilityNetwork scalability refers to the use of multiple physical interfaces to accommodate bandwidthrequirements for which a single network interface is insufficient. You can achieve networkscalability by having multiple network interfaces on multiple hosts or by having a multi-homedhost (a single system that has multiple network interfaces). You canmake this form of scalabilityeither explicit or transparent. If explicit, then both ends of the connection simply accommodatemultiple interfaces by specifying a list of IP addresses.To make network scalability transparent with a multi-homed host or with multiple hosts, youcan use theDomainName System (DNS) andhave themultiple interfaces share a single, externallyvisible name. One way to have multiple interfaces share a name, is to have a DNS name serverprocess on each of the subnets and configure each of those name server processes to return theIP address of the host that is also on that subnet (Figure 1-6).

Figure 1-6 Transparent Network Scalability, Multiple Hosts

In the example shown in Figure 1-6, there are four DNS name server processes, one on eachsubnet. Each name server process is configured to return the IP address of the host’s interface


on that subnet. All clients requesting an IP address on that subnet are returned the IP addressof the host that is also on that subnet.• Clients on subnet 192.168.1.1 requesting the IP address of MyCompany.com receive the IP

address of Webserver 1.• Clients on subnet 192.168.2.1 requesting the IP address of MyCompany.com receive the IP



address of Webserver 4.Figure 1-6 (page 17) shows transparent network scalability on multiple hosts.The otherway of achieving transparent network-level scaling is to useDNS round-robin addressrotation where one DNS name server process returns different IP addresses for a given resourceservice. With this technique, you would ensure there is a different network interface associatedwith each IP address; one name server process would then answer requests for the name withthose IP addresses on a rotating basis. In Figure 1-7, the DNS server process rotates Webserverrequests for Mycompany.com among interfaces 1.1.1.1, 1.1.2.1, 1.1.3.1 and 1.1.4.1. (On amulti-homed NonStop server, the separate systems shown in Figure 1-7 are contained in onesystem.)

Figure 1-7 DNS Round-Robin Address Rotation

See the DNS Configuration and Management Manual for more information about configuring aDNS name server process on your NonStop server.

Application ScalabilityApplication scalability refers to distributing application-service load across multiple instancesof the application server process. In the example of the scaling mechanism provided by DNS,the service application (the web server process) is limited when the server instances need toshare data that is not resident on all the hosts. For example, a set of web server processesdistributed over n hosts must either have the data it is servicing duplicated across those hostsor connect to a back-end shared database so that all the web server processes are accessing


up-to-date information. In a NonStop server environment, those n hosts can be consolidatedonto a single system and have access to a shared database on that same system.Returning to the Nonstop TCP/IPv6 and CIP subsystems' architectural features of allowingmultiple server processes to bind to a shared port and IP address, the web server process in canrun 16 copies of itself and access a shared databasewhile presenting a single image to the network.

NOTE: NonStop TCP/IPv6 had a limitation of one listening process per processor per port. CIPdoes not have this limitation. There can be many listening processes per processor per port.

Figure 1-8 shows round-robin filtering on a single IP address. Incoming connection requests aredistributed among 16 instances of the server process in 16 different processors.

Figure 1-8 Round-Robin Filtering in the NonStop TCP/IPv6 and CIP Environments

Scaling Your Application on the NonStop SystemSeveral listenermodels are discussed in the TCP/IPv6 Configuration andManagementManual, eachwith unique configuration requirements depending on how that particular listenermodelworks.CIP also supports the listening models and scaling techniques described in the TCP/IPv6Configuration andManagementManual. By configuring yourNonStop TCP/IPv6 or CIP subsystemto use round-robin filtering, you can cause incoming connection requests to be distributed amongdifferent application instances running in different processors.

NOTE: To enableNonStop TCP/IPv6 andCIP round-robin filtering only for certain applications,you can limit the ports upon which round-robin filtering is enabled by adding a DEFINE. SeetheTCP/IPv6 Configuration andManagementManual or theCluster I/O Protocols (CIP) Configurationand Management Manual for an explanation of this DEFINE.

Round-robin filtering configuration for an application requires that you configure the NonStopTCP/IPv6 or CIP environmentwith round-robin filtering and that you define the transport-serviceproviders (TCP6SAM or CIPSAM processes) in the same TACL session in which you define thefilter key.You configure NonStop TCP/IPv6 or CIP with round-robin filtering enabled in the Guardianenvironment and the OSS environment inherits the DEFINE that establishes the environment.


Fault-Tolerance and Scalability on the NonStop ServerWhen you have configured for scalability, the failure of one or more processors does not impactthe 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 availableso 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 arereloaded and applications are restarted, the applications automatically resume their scaledconfigurationwithout disruption to the single IP view. The re-instantiated applications startusing the IP address that had been configured previously.

Ethernet Failover: Fault-Tolerant ConnectivityNonStop TCP/IPv6 provides failover at the adapter level by using a feature called Ethernetfailover. Ethernet failover allows a second Ethernet interface to take over connections fromanother interface if the other interface fails.Unlike other failover implementations, NonStop TCP/IPv6 Ethernet failover does not requireone of the interfaces to act as a “hot standby” in anticipation of a failure. Both interfaces are activeand allow inbound and outbound network traffic to be distributed between them. Hence, inaddition to having fault-tolerance at the interface level by using Ethernet failover, you also gainscalability when all your interfaces are performing correctly.For more information about Ethernet failover, see the TCP/IPv6 Configuration and ManagementManual.The CIP subsystem can be configured to provide failover between Ethernet interfaces on a CLIMand can provide failover between two CLIMs. Failover between two CLIMs results in a loss ofTCP and SCTP connections so applications need to reestablish those connections. However oncesessions have been reestablished, all other configuration aspects of the failed-over interface,including IP addresses, routes, tunnels,multicast groups, and sockets to other CLIMs, are restored.

Logical Network Partitioning (LNP) and ProvidersIn theNonStop TCP/IPv6 environment, all applications have access to all interfaces (IP addresses)unless you configure logical-network partitioning (LNP). TheCIP environment shares this feature,except you use Providers to restrict applications to certain CLIMs (each of which contain fiveinterfaces).One of the most important differences between conventional TCP/IP and NonStop TCP/IPv6and CIP is that NonStop TCP/IPv6 and CIP have onemanager process ($ZZTCP or $ZZCIP) andall interfaces are associatedwith that single process. This difference influences howyou configurethe subsystem. In conventional TCP/IP, you can have multiple TCP/IP processes, each havingone or more interfaces uniquely associated with them, as shown in Figure 1-9.


Figure 1-9 Conventional TCP/IP: Data From the Interface is Restricted to Applications Using theAssociated Process

InNonStopTCP/IPv6, if you do not configure the environment to use logical-network partitioningand in CIP if you did not configure the environment to use Providers, applications using thosesubsystems cannot determine which interface they will get because the interface is no longerassociated with the TCP/IP process used by the applications.LNP and ProvidersmakeNonStop TCP/IPv6 andCIP similar to conventional TCP/IP in the sensethat you can restrict an application’s view of the network by associating the application with aTCP/IP process. LNP and Providers allow flexible security configurations in the subsystembecause you can prevent unwanted applications in the system from using interfaces or CLIMsin a configured partition or Provider. (Providers only restrict applications to particular CLIMsin CIP, whereas LNP restricts them to particular interfaces on an adapter in NonStop TCP/IPv6.)In NonStop TCP/IPv6, each LNP has its own set of IP addresses and SLSA logical interfaces(LIFs). In CIP, each Provider has its own set of IP addresses and Ethernet interfaces. An IP addressused on one Provider or in one LNP cannot be used on a different Provider or different LNP,and an interface cannot be shared between Providers or LNPs. Applications on one Provider orLNP are isolated from applications on different Providers or LNPs on the same system in thesameway theywould be isolated if usingdifferent conventional TCP/IPprocesses. Communicationbetween such applications is only possible through the attached local area networks. CIP andNonStop TCP/IPv6 do not forward packets between Providers or LNPs internally.The difference between conventional TCP/IP and NonStop TCP/IPv6 with LNP or CIP withProviders is that the NonStop TCP/IPv6 transport process (TCP6SAM process) and the CIPtransport process (CIPSAM), unlike the NonStop TCP/IP process, span all the processors in thewhole system. The result is that an application in any processor, even when using LNP orProviders to restrict itself to specific interfaces, has direct access (with no interprocess,message-system hop) to the network adapter.For more information about LNP, see the TCP/IPv6 Configuration and Management Manual. Formore information about Providers, see theCluster I/O Protocols (CIP) Configuration andManagementManual.Most of the aspects of logical network partitioning that apply to NonStop TCP/IPv6 also applyto CIP with these differences:• Network partitions are called Providers in CIP.• InNonStop TCP/IPv6 you can assign individual interfaces to a partitionwhereas CIP assigns

whole CLIMs, each of which is a group of five interfaces to a Provider.In CIP, if you need to partition your network into a large number of partitions, each with onlyone or two interfaces, you can avoid needing a lot of CLIMs by using various strategies. A white


paper on this topic provides more detail. Ask your HP sales representative for the white papercalled IP CIP Compared to Other NonStop TCP/IP Products.

PersistenceThe NonStop TCP/IPv6 and CIP products on the Integrity NonStop systems participate in thesystem configuration database as generic processes and can be managed by the persistencemanager. If you add their processes as generic processes, they start automatically upon systemreload and restore their stored and subordinate objects.For more information about configuring NonStop TCP/IPv6 to be persistent, see the TCP/IPv6Configuration andManagementManual. Formore information about configuringCIP to be persistent,see the Cluster I/O Protcols (CIP) Configuration and Management Manual. For more informationabout managing generic processes, see the SCF Reference Manual for the Kernel Subsystem.

What's Unique About Networking on Integrity NonStop BladeSystemsNetworking on a NonStop BladeSystem offers the same features as networking on a NonStopNS-series server with these exceptions:• The NonStop BladeSystem connects directly to the NonStop S-series server I/O enclosure

but only the 6763CommonCommunication ServerNet adapter (CCSA-2)with up to 4 SS7TE3plug-in cards (PICs) is supported. No other configurations of the CCSA are supported andno other ServerNet adapters are supported.

• Other differences in features exist. (See the Cluster I/O Protcols (CIP) Configuration andManagementManual for information about networking feature differences and see theNonStopBladeSystem Planning Guide for more information about features and differences of thissystem.)

NOTE: Only some Integrity NonStop systems support the S-series I/O enclosure. Check theplanning guide for your system.

Summary Comparison of NonStop TCP/IP Products on H-Series and J-SeriesRVUs

This section compares at a high level, the three TCP/IP subsystems available on the H-series andJ-series RVUs.

Table 1-1 Comparison of NonStop TCP/IP Products

Cluster I/O Protocols (CIP)NonStop TCP/IPv6Conventional TCP/IP

10M / 100M / 1G Ethernet10M / 100M / 1G Ethernet• 10M / 100M / 1GEthernet

• ATM

• SNAP (token-ring orEthernet)

• X.25

Interface Types

YesYesNoJumbo Frames Supported


Table 1-1 Comparison of NonStop TCP/IP Products (continued)

Cluster I/O Protocols (CIP)NonStop TCP/IPv6Conventional TCP/IP

CLIM• MFIOB• IOAM+E4SA• IOAM+FESA• IOAM+GESA• IOAM+G4SA• VIO+G4SA

• MFIOB• IOAM+E4SA• IOAM+FESA• IOAM+GESA• IOAM+G4SA• VIO+G4SA• IOAM+ATM3SA• IOAM+TRSA• IOAM+CCSA

Adapters

48604Maximum Adapters

2402404 per process pairMaximum HardwareInterfaces

IPv4, IPv6IPv4, IPv6IPv4IP versions

YesNoNoSCTP Support

LinuxBSD/DECBSD4.3Protocol Stack Ancestry

Offloaded to CLIMOne per NonStop systemprocessor

One NonStop Process PairProtocol Stack Location

NoNoYesRemote Socket Support

NoNoYesFault-Tolerant SocketsSupport1

Yes, no limit per processorper port

Yes, maximum one perprocessor per port

NoRound-Robin ListenersSupport

YesYesYesNetwork PartitioningSupport

CLIMInterfaceInterfaceMaximum Partition Size

CLIMInterfaceInterfaceMinimum Partition Size

PartialFullNoneInterface Failover

YesNoNoIPSec Support

NoFor IPv6NoAutomatic DNS Updates

• $ZZCIP through SCF• climconfig through

CLIMCMD• CIPSAM through SCF• NonStop I/O Essentials

plug-in to HP SystemsInsight Manager (SIM)

• $ZZTCP through SCF• $ZZLAN through SCF• TCP6SAM through SCF

• TCP/IP through SCF• $ZZLAN through SCF

Configuration Commands

• ABORT• INFO•• NAMES• PRIMARY•• STATUS• STOP• TRACE• VERSION

• ABORT• INFO• LISTOPENS• NAMES• PRIMARY• STATS• STATUS• STOP• TRACE• VERSION

N/ACompatible Commands inSAM

Summary Comparison of NonStop TCP/IP Products on H-Series and J-Series RVUs 23

1 Fault-Tolerant Sockets transfer a socket from an application in one processor to its backup in another. OnlyConventional TCP/IP supports them.

Unlike previous TCP/IP products, CIP does not use the SLSA subsystem.CIP uses aCLIM instead,which has higher speed and functionality than any of the SLSA-supported Ethernet adapters.

Table 1-2 Comparison of Communications Adapters and CLIMs

CLIMVIOG4SAGESAFESAE4SA

584114Number ofHardwareInterfaces

5 10/100/1000Mbps

• 210/100/1000Mbs

• 2 10/100Mbps

• 2 10/100/1000Mbs

• 2 10/100 Mbps

10/100//1000Mbps

10/100 Mbps10 MbpsHardwareInterfaceSpeeds

5 copper or 3copper, 2 fiber



1 copper1 copper4 copperHardwareInterfaceMedia

YesYesYesYesYesNoJumboFrames

Full protocolstack

FiltersFiltersFiltersFiltersFiltersOnboardProcessing

Previous TCP/IP products also support the MFIOB, which is usually used for access to thededicated service LAN. In addition to the five ports shown in Table 1-2, eachCLIMhas a separateport that is used for the dedicated service LAN.


2 Networking ConceptsThis section provides a brief overview of networking concepts including the following topics:• Address Resolution• Name Resolution• Allocation of IP Addresses (page 26)• Routers (page 26)• Switches (page 27)• Gateways (page 27)• Network Interface Name (page 27)• Firewalls (page 28)• “IP Security (IPSec)” (page 28)• IPv6 (page 29)Formore detailed information about Internet concepts and services, see the TCP/IP Configurationand Management Manual.

Address ResolutionAddress resolution refers to the mapping of IP addresses to lower-level addresses and isaccomplished by the static binding of addresses or the dynamic binding of addresses. Staticbinding of addresses is used for the NonStop TCP/IP product over X.25. Dynamic binding ofaddresses is implementedwith the Address Resolution Protocol (ARP) for IPv4 (defined in IEEERFC 826) and is used for NonStop TCP/IP, NonStop TCP/IPv6 and CIP over Ethernet.Address resolution with the dynamic binding of addresses for networks involves the use of theNeighbor Discovery Protocol. Using theNeighbor Discovery Protocol and stateless address autoconfiguration, an Integrity NonStop system configured as an IPv6 host discovers other nodeson the link, determines their link-layer addresses, finds routers, and maintains reachabilityinformation about the paths to active neighbors. See the TCP/IPv6 Configuration andManagementManual or Cluster I/O Protocols (CIP) Configuration and Management Manualfor more informationabout the Neighbor Discovery Protocol and stateless address auto configuration in the IPv6network. See also, IPv6 (page 29).

Name ResolutionFor convenience, hosts are often referred to by name; in addition, for the world wide web,universal resource locators (URLs) locate awebsite location. The process of finding the IP addressassociated with either a host or a URL is a process of name-to-address mapping, is also calledname resolution. There are two methods of resolving names, by:• HOSTS File• Domain Name System (DNS)

HOSTS FileAHOSTS file is an ASCII file on your system, by default in ZTCPIP (Guardian) or /etc (OSS) thatlists the various host names associated with the IP addresses on the system. To use a HOSTS filefor address resolution, you must configure the TCP/IP subsystem to use that HOSTS file; thedefault is for the TCP/IP subsystems is to use the Domain Name System (DNS) .For procedures about configuring the various subsystems to use the HOSTS file, see the:• TCP/IPv6 Configuration and Management Manual• TCP/IP Configuration and Management Manual• Cluster I/O Protocols (CIP) Configuration and Management Manual

Address Resolution 25

Domain Name System (DNS)The Internet has created an ever-increasing demand for IP addresses, and IP addressmanagementhas presented a challenging task for administrators. In the past, administrators could managethe IP addresses in a single file containing all the host information (HOSTS File ) withname-to-address mappings for every host connected to the network. Now assigning andmaintaining new IP addresses and resolving domain names to IP addresses have become difficultand cumbersome tasks.An effective solution to this problem is the Domain Name System (DNS), a distributed databasethat implements a name hierarchy for TCP/IP-based networks. DNS defines the rules for namesyntax in a hierarchical name space and for delegation of authority over names. A name serveris a server program thatmaps domain names to IP addresses. A set ofDNSname servers operatingat multiple sites co-operatively solve the domain name to IP address mapping problem.Every time you use a domain name, a DNS service translates the name into the correspondingIP address. For example, the domain name www.sample.com translates to 188.135.212.3.To use the domain name system, you must assign a name, in ARPANET standard format, toeach system on the network or internetwork. You configure this name in your networkconfiguration scripts. (See the TCP/IPv6 Configuration and Management Manual and the ClusterI/O Protocols (CIP) Configuration and Management Manual for details.)You also need to create a set of ASCII files on each system which contains the addressinginformation the system needs. Instructions for creating these files are in the TCP/IP Configurationand Management Manual.Once you have configured the domain name services, the network can access the node using thenode’s domain name and the domain name service routines will resolve the domain name to thenode’s IP address.

Allocation of IP AddressesIP addresses are allocated in severalways. First, it is important to distinguish between IP addressesfor components associatedwith a system and attached to themaintenance LAN (formerly knownas the private LAN) and interfaces on components used for data communication between thesystem and other devices on the network. Devices in an Integrity NonStop system that areattached to the maintenance LAN include maintenance switches, NSC consoles, processorswitches, ServerNet switch boards, CLIMs, and Uninterruptible Power Supply (UPS) units.Maintenance entity IP addresses come as statically configured IP addresses but can also bechanged to dynamically configured IP addresses.Address allocation has becomemore complexwith the implementation of IPv6 (see IPv6 (page 29))which introduced stateless address auto configuration, a process in which IP addresses actuallyexpire, and with the increasing use of Dynamic Host Configuration Protocol (DHCP) servers.IP address allocation for network interfaces on your NonStop systems can be obtained bycontacting your Internet Service Provider (ISP) for an IPv6 address range for your site. See theIANA web page at:http://www.iana.org/ipaddress/ip-addresses.htm

for more information about regional registries and address allocations.

RoutersA router is a device that has multiple network interfaces and transfers Internet Protocol (IP)packets from one network or subnet to another within an internetwork. (In many IP-relateddocuments, this device is also referred to as a “gateway.”)Routing protocols find a path between network nodes. If multiple paths exist for a given protocol,the shorter paths are usually chosen. Each protocol has a cost or a metric that it applies to eachpath. In most cases, the lower the cost or metric for a given path, the more likely a protocol will

26 Networking Concepts

http://www.iana.org/ipaddress/ip-addresses.htm

choose it. In large local networks, there are oftenmultiple paths to other parts of the local network.Routing daemons can be used to maintain near optimal routing to the other parts of the localnetwork, and to recover from link failures in paths.

SwitchesA switch receives messages from various devices on the network and routes the messages overthe network to their appropriate destinations. The public telephone network provides the mostobvious example of the use of switching, but switches are widely used in private networks aswell.

GatewaysNetworks that use different types of hardware and different protocols, such as TCP/IP and OSI,can communicate with each other through a gateway. Unlike a router, a gateway can translatethe protocol of one network to a different protocol used by another network.When it is not beingused to translate protocols, “gateway” is used interchangeably with “router”.

Network Interface NameAnetwork interface is a communication device throughwhichmessages can be sent and received.Interface names on a G4SA are the logical interfaces (LIFs). On the CLIM, interface names areassigned by the operating system to the Ethernet interfaces. The names are eth1 through eth5and are assigned left to right, top to bottom. For diagrams showing the layout of the Ethernetinterfaces on the CLIM, see the Cluster I/O Protocols (CIP) Configuration Management Manual. Todetermine the interface nameswhen usingNonStop TCP/IPv6 or NonStop TCP/IP, issue the SCFINFO LIF $ZZLAN.* command to the ServerNet LAN Systems Access (SLSA) subsystem andlook at the “Name” column in the resulting display. For example:1-> INFO LIF $ZZLAN.*SLSA Info LIFAssociatedName Object MAC Address Type$ZZLAN.CC10A CC1.0.A 00:00:00:00:00:00 WAN$ZZLAN.LANY M0IE1.0.A 08:00:8E:00:7A:D9 Ethernet$ZZLAN.LANX M0IE1.0.A 08:00:8E:00:7B:BA Ethernet$ZZLAN.L018 E0153.0.A 08:00:8E:00:78:3A Ethernet$ZZLAN.L019 E0153.0.B 08:00:8E:00:78:2D Ethernet$ZZLAN.L01A E0153.1.A 08:00:8E:00:78:2C Ethernet$ZZLAN.L01B E0153.1.B 08:00:8E:00:78:1C Ethernet$ZZLAN.L112I G1123.0.A 08:00:8E:00:97:B0 Ethernet$ZZLAN.L01C T0154.0.A 08:00:8E:80:12:CE Token Ring$ZZLAN.L01A E0152.0.A 08:00:8E:AB:CD:EF Ethernet

To determine the interface names when using CIP, issue the SCF STATUS CLIM DETAILcommand. For example:->STATUS CLIM $ZZCIP.* , DETAIL

.

.

.

Data Interface Status & IP Addresses: Flg Name Status LkP Master / IP Family & Address eth5 UP UP IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182e IPv6: 3ffe:1200:190:2:21f:29ff:fe57:182e IPv6: fe80::21f:29ff:fe57:182e eth4 UP UP IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182f IPv6: 3ffe:1200:190:2:21f2:9ff:fe57:182f IPv6: fe80::21f:29ff:fe57:182f

Switches 27

eth3 UP UP IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182c IPv6: 3ffe:1200:190:2:21f:29ff:fe57:182c IPv6: fe80::21f:29ff:fe57:182c eth2 UP UP IPv6: 3ffe:1200:190:2:21f:29ff:fe57:182d IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182d IPv6: fe80::21f:29ff:fe57:182d...

FirewallsA firewall is a system or group of systems that enforces an access control policy between two ormore networks. The actual means by which access control is accomplished varies widely, but inprinciple, the firewall can be thought of as a pair ofmechanisms: Onewhich exists to block traffic,and the other which exists to permit traffic. Some firewalls place a greater emphasis on blockingtraffic, while others emphasize permitting traffic. The most important thing to recognize abouta firewall is that it implements an access control policy. Before you install a firewall, you needto know what kind of access you want to allow or deny. Also note that because the firewall is amechanism for enforcing policy, it imposes its policy on everything behind it. Administratorsfor firewalls managing the connectivity for a large number of hosts have a heavy responsibility.

IP Security (IPSec)IPSec is a feature available only in the CIP product.The IP security architecture (IPSec) defines basic security mechanisms at the network level sothey can be available to all the layered applications. The security techniques adopted in IPSechave been designed to be easily inserted in both IPv4 and IPv6.IPSec security services are offered by means of two dedicated extension headers, theAuthentication Header (AH) and the Encapsulating Security Payload (ESP), and through theuse of cryptographic key management procedures and protocols.TheAHheaderwas designed to ensure authenticity and integrity of the IP packet. It also providesan optional anti-replay service. Its presence guards against illegal modification of the IP fixedfields, packet spoofing and, optionally, against replayed packets. On the other hand, the ESPheader provides data encapsulation with encryption to ensure that only the destination nodecan read the payload conveyed by the IP packet. ESP may also provide packet integrity andauthenticity, and an anti-replay service. The two headers can be used separately or they can becombined to provide the desired security features for IP traffic.Each header can be used in one of the two definedmodalities: transport mode and tunnel mode.While in transport mode the security headers provide protection primarily for upper layerprotocols, in tunnelmode the headers are applied to tunneled IP packets, thus providingprotectionto all fields of the original IP header.Both AH and ESP exploit the concept of security association (SA) to agree upon the securityalgorithms, transforms and parameters shared by the sender and the receiver of a protectedtraffic flow. Each IP node manages a set of SAs, with at least one SA for each securecommunication. The SAs currently active are stored inside a database, known as the securityassociation database (SAD). An entry in the SAD (for example, a security association) is uniquelyidentified by a triplet consisting of a security parameter index (SPI), an IP destination address,and a security protocol (AH or ESP) identifier. The security parameter index (SPI) is transmittedinside both the AH and ESP headers since it is used to choose the right SA to be applied fordecrypting and authenticating the packet.In unicast transmissions, the SPI is normally chosen by the destination node and sent back to thesender when the communication is set up. In multicast transmissions, the SPI must be common

28 Networking Concepts

to all the members of the multicast group. Each node must be able to correctly identify the rightSA by combining the SPI with the multicast address. The negotiation of a SA (and the relatedSPI) is an integral part of the protocol for the exchange of security keys.Specific security requirements are defined at each node usually by means of an ordered list ofadmission rules (or policies), which form the node’s security policy database (SPD). The protectionprovided to each incoming and outgoing traffic flow is verified by consulting the SPD. In general,packets are selected for one of three processing modes based on IP and transport layer headerinformation matched against entries in the SPD. Each packet is either afforded IPSec securityservices, discarded, or allowed to bypass IPSec, based on the applicable policies found in thedatabase.

IPv6The IPv6 protocol extends the IP address to 128 bits compared to the 32 bits of IPv4 addresses.The NonStop TCP/IPv6 subsystem provides IPv6 functionality on the Integrity NonStop systemusing three modes of operation: pure IPv6, in which the system supports only IPv6communications, DUAL, in which the system supports both IPv4 and IPv6 communications,and pure IPv4, in which the system provides only IPv4 communications. The CIP subsystemalso supports IPv6with an attribute in the Provider object, which can be set to either INET (IPv4)or DUAL.Much of the Internet consists of IPv4 networks; an IPv6-enabled system can communicate acrossIPv4 networks by using tunneling. IPv6 tunneling requires an IPv4 address on both ends of thecommunication; IPv6 packets are then encapsulated in IPv4 packets so that they can be transmittedacross an IPv4 network. The IPv6-aware host or router decapsulates the IPv6 datagrams,forwarding them as needed. IPv6 tunneling eases IPv6 deployment bymaintaining compatibilitywith the large existing base of IPv4 hosts and routers. Figure 2-1 depicts an IPv6 tunnelingscenario.

Figure 2-1 IPv6 Tunneling

For more information about IPv6, see the TCP/IPv6 Configuration and Management Manual.

IPv6 29

30

3 Planning for Migrating Networking Solutions to H-Seriesand J-Series RVUs

This section provides examples of product-suite requirements for some legacy networkingsolutions on H-series and J-series RVUs. These examples were chosen to show the generalplacement and relationships of legacy networking software and hardware in the H-series andJ-series RVU environments.In addition, this section provides guidance for finding Internet application documentation.Topics covered in this section include:• Planning Your Networking Solutions• Migrating From a Platform Other Than a NonStop Server (page 33)• Internet Application Product Documentation (page 34)

Planning Your Networking SolutionsThis subsection provides information aboutwhich subsystems, products andmanuals youmightneed for various networking solutions on the Integrity NonStop system, including:• SNAX/XF (Includes Function From SNAX/APN)• X.25 Communications (page 32)In addition, this subsection addresses Selecting Your TCP/IP Product (page 33)

SNAX/XF (Includes Function From SNAX/APN)To use SNAX/XF on H-series RVUs and J-series RVUs, you need these hardware products andsubsystems:• SNAX/XF• NonStop TCP/IP, NonStop TCP/IPv6 or CIP• Port Access Method (PAM) or Wide Area Network WAN subsystem• SLSA (unless using CIP)• CLIM, G4SA, FESA, GESA, E4SA, or TRSA• NonStop S-series I/O enclosure (optional, used for TRSA, E4SA, FESA, orGESA connectivity)

Planning Your Networking Solutions 31

Figure 3-1 Products for SNAX/XF Using the IOAM Enclosure

The manuals you might need for running SNAX/XF include:• Introduction to Networking for HP NonStop S-Series Servers• SNAX/XF and SNAX/APN Configuration and Management Manual• Cluster I/O Protocols (CIP) Configuration and Management Manual• LAN Configuration and Management Manual• Port Access Method (PAM) Configuration and Management Manual• Token Ring Adapter Installation and Support Guide• Gigabit Ethernet 4-Port Adapter Installation and Support Guide• Gigabit Ethernet Adapter Installation and Support Guide• Ethernet Adapter Installation and Support Guide• Token Ring Adapter Installation and Support Guide• WAN Subsystem Configuration and Management Manual• Planning guide for your system

X.25 CommunicationsFor X.25 communications on H-series or J-series RVUs, you need:• X25AM• CIP, NonStop TCP/IP, or NonStop TCP/IPv6• WAN subsystem• SLSA (for NonStop TCP/IP and NonStop TCP/IPv6 only)• CLIM, G4SA, E4SA, FESA, or GESA• A SWAN or SWAN 2 Concentrator• NonStop S-series I/O enclosure (optional, used for TRSA, E4SA, FESA, orGESA connectivity)

32 Planning for Migrating Networking Solutions to H-Series and J-Series RVUs

Figure 3-2 Products for X.25 Communications for H-Series or J-Series RVUs

The manuals you might need for X.25 communications may include:

Selecting Your TCP/IP ProductHP recommends using NonStop TCP/IPv6 or CIP for your TCP/IP needs because of the superiorprocessing power of the parallel architecture that underlies these products. (See IntegrityNonStopSystem Networking Compared to NonStop S-Series Server Networking (page 15), the TCP/IPv6Configuration and Management Manual, and the Cluster I/O Protocols (CIP) Configuration andManagementManual.) Because you can useNonStop TCP/IPv6 and CIP for IPv6 communications(see IPv6 (page 29)) you can use these products to gain the benefits of the architecture withoutimplementing IPv6 communications in your environment. If you want to use IPv6communications, you must use NonStop TCP/IPv6 or CIP.To use any data communication protocols other than Ethernet or X.25, you must use NonStopTCP/IP instead of NonStop TCP/IPv6 or CIP. NonStop TCP/IP provides access to these:• Token Ring• ATM

Migrating From a Platform Other Than a NonStop ServerIf you are migrating to the Integrity NonStop system from another platform and do not haveNonStop S-series servers in your environment, your networking options will be restricted toGigabit Ethernet and you should plan tomigrate your applications to run over TCP/IP, ServerNetWAN, or CLIM connections.If you are migrating to the Integrity Nonstop NS-series server from the NonStop S-series server,you can retain most of your existing networking solutions, including token ring and ATM, butyou will not be able to use IPX/SPX or ServerNet/FX directly. (However, ServerNet/FX canprovide inter connectivity between NonStop S-series servers and NonStop K-series servers inan environment that includes Integrity NonStop systems. See Figure 1-3 (page 13).) If you aregoing to use token ring orATM, you can run your applications on the IntegrityNonStopNS-series

Migrating From a Platform Other Than a NonStop Server 33

server andmanage the subsystems for each of those protocols on the IntegrityNonStopNS-seriesserver as well. You do not need to do anything to your applications to make them run on theIntegrityNonStopNS-series server but your hardwaremust include a connection from the IOAMto the NonStop S-series I/O enclosure.This option of attaching to the NonStop S-series I/O enclosure is not available for NonStopBladeSystems.If you are using NonStop TCP/IPv6 and want to tune it by configuring the QIO subsystem torun in the global privileged space, you can take advantage of the Integrity NonStop system’sincrease of this memory location to 256 MB. See the QIO Configuration and Management Manualfor information about how and when to make this adjustment.

Internet Application Product DocumentationYou can find general information about the products listed in Table 3-1 in the Introduction toNetworking for HP NonStop S-Series Servers.

Table 3-1 Internet Application Product Documentation

ManualsProduct

HP NonStop Server Platform Guide for WebLogic Server 8.1BEAWebLogic Server for the NonStop Server

iTP Secure WebServer System Administrator’s GuideiTP Secure WebServer

iTP Active Transaction Pages (iTP ATP) Programmer’s GuideiTP Active Transaction Pages (ATP)

NonStop Servlets for JSP System Administrator’s GuideNonStop Servlets for JavaServer Pages (NSJSP)

NonStop SOAP User’s ManualNonStop SOAP

NonStop SOAP for Java User’s ManualNonStop SOAP for Java

34 Planning for Migrating Networking Solutions to H-Series and J-Series RVUs

Index

Symbols6100 TINET Multi-PT Supervisor-PDG, 126100 UTS-40 Multi-PT Supervisor, 126100 UTS-40 Multi-PT Tributary, 126100 VIP Multi-PT Supervisor, 12

AAddress resolution, 25AM3270 Access Method, 12Asynchronous Terminals and Printer Processes, 12ATM, 12ATP6100 WANPRINT, 12

BBEAWebLogic Server, 34

CCLIM, 9CLuster I/O Module (CLIM), 9Cluster I/O Protocols (CIP), 12

DDNSoverview, 26scaling, 17supported versions, 12

Documentation for Internet application products, 34Domain Name Server (DNS) (T6021), 12Domain name system (DNS) (see DNS)

EEnform, 12Envoy, 12EnvoyACP/XF, 12Ethernet failover, 20Expand, 12

FFault tolerance, 20Firewalls, IP securityfirewalls, 28

FOX Gateway, 12

GGigabit Ethernet 4-port ServerNet adapter (G4SA), 9

II/O Essentials, 23Internet Protocol (IP) Cluster I/O Module (CLIM)overview, 9

Internet protocol security (IPSec)overview, 28

IP CIP Compared to Other NonStop TCP/IP Products,white paper, 22

IPv6, 29

IPX, TANDEMNBT NETBIOS, 12iTP Active Transaction Pages (ATP), 34iTP Secure WebServer, 34

MMultilan Access Method and File Server, 12

NNetwork partitioning, 21NetworkingNonStop NS-series server compared to NonStopS-series server, 15

NonStopNS-series server compared to other platforms,16

products supported on NonStop NS-series, 9NonStop BladeSystemand interoperability with other NonStop servers., 13overview, 9

NonStop IPX/SPX, 12NonStop NS-seriescompared to NonStop S-series server , 15compared to other platforms, 16

NonStop Servlets for JavaServer Pages (NSJSP), 34NonStop SOAP, 34NonStop SOAP for Java, 34NonStop TCP/IPv6, 12NonStop K-series server interconnectivity, 13Novell LAN Print Spooler, 12

OOSI/AS, 12OSI/FTAM, 12OSI/MHS, 12OSI/TS, 12

PParallel Library TCP/IP, 12Port Access Method (PAM), 12Providers, CIP partitioning, 21

QQIO, 12

RRound-robin filtering, 16

SS-series I/O supportand p-switch systems, 11overview, 9

Scalability for DNS, 17ServerNet LAN Systems Access (SLSA), 12SNAX High Level Support (SNAX/HLS), 12SNAX/APN, 12SNAX/XF, 12SNMP, 12

35

Spooler, 12Spooler FastP Network Print Processes, 12Spooler Plus, 12Systems Insight Manager (SIM), 23

TTANDEMNBT NETBIOS, 12TCP, TANDEMNBT NETBIOS, 12TCP/IP (conventional), 12TELSERV, 12TN3270e, 12TR3271 Tributary Access Method, 12

VVersatile I/O (VIO) enclosure, 11

WWhite paper, CLIM strategies, 22Wide area network (WAN) subsystem, 12

36 Index

37

Documents

HP NonStop Networking Overview