HP NonStop TCP/IPv6 Migration Guide

Transcription

1 HP NonStop TCP/IPv6 Migration Guide Abstract Version This manual discusses the differences between HP NonStop TCP/IP and NonStop TCP/IPv6 and the differences between Parallel Library TCP/IP and NonStop TCP/IPv6. NonStop TCP/IPv6 G06, NonStop TCP/IPv6 G06 and H01 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs and H06.03 and all subsequent H-series RVUs until otherwise indicated in a new edition. Part Number Published July 2005

2 Document History Part Number Product Version Published NonStop TCP/IPv6 G06 May NonStop TCP/IPv6 G06 December NonStop TCP/IPv6 G06 December NonStop TCP/IPv6 G06, H01 July 2005

3 HP NonStop TCP/IPv6 Migration Guide Glossary Index Tables What s New in This Manual v Manual Information v New and Changed Information About This Guide vii How This Guide is Organized Related Manuals vii Notation Conventions ix v vii 1. Introduction Overview 1-1 Definitions 1-2 System Requirements 1-2 Product Components and Product Numbers 1-2 Summary of Differences Between NonStop TCP/IP and NonStop TCP/IPv6 1-4 Summary of Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 1-5 Constraints 1-6 Compatibility Transport-Service Provider Differences for NonStop TCP/IPv6 Determining the Name of the Socket Access Method 2-1 Logical Network Partitioning (LNP) 2-2 Configuring Applications to Use NonStop TCP/IPv6 2-5 Guardian Socket Applications 2-5 OSS Socket Applications 2-5 Compatibility 2-6 Event Management Service (EMS) 2-6 Fault-Tolerant Behavior 2-6 SCF 2-8 Trace 2-8 Hewlett-Packard Company i

4 Contents 3. Migration Considerations 3. Migration Considerations Differences Between NonStop TCP/IP and NonStop TCP/IPv6 3-1 Application Behavior 3-2 Applications: Restricting Access to Network Interfaces 3-2 Attribute Defaults 3-2 Configuration Files 3-4 DEFINEs 3-4 Error Treatment 3-4 Fault-Tolerant Behavior 3-5 Firewall Considerations 3-5 Management Interfaces 3-5 Modes 3-7 NonStop Operations 3-7 Persistence Manager 3-7 Platform 3-8 Resource Management 3-8 Retransmission Timer Enhancements 3-8 Round-Robin Filtering 3-9 Shared Run-Time Library (SRL) 3-9 SPI Interface 3-9 SWAN 3-9 System Configuration Database 3-9 Telserv 3-10 Trace 3-10 Tips for Migrating from NonStop TCP/IP to NonStop TCP/IPv Differences Between Parallel Library TCP/IP and NonStop TCP/IPv Addresses 3-11 Applications 3-11 Attribute Defaults 3-12 Configuration Files 3-12 DEFINEs 3-13 Dynamic Linked Library (DLL) 3-13 Event Messages 3-13 Management Interfaces 3-13 Modes 3-13 Multicast Operations 3-14 Name Changes 3-14 Processes and Protocols 3-15 ii

5 Contents 3. Migration Considerations (continued) 3. Migration Considerations (continued) Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 (continued) Retransmission Timer Enhancements 3-15 Tips for Migrating From Parallel Library TCP/IP to NonStop TCP/IPv Procedures for Migrating to NonStop TCP/IPv6 Migrating Conventional NonStop TCP/IP to NonStop TCP/IPv6 4-1 Migrating Parallel Library TCP/IP to NonStop TCP/IPv6 4-1 Migrating Your Application to NonStop TCP/IPv6 4-2 Glossary Index Tables Table 1-1. Comparison of Features 1-2 Table 1-2. NonStop TCP/IPv6 Components and Product Numbers on NonStop S-Series Servers 1-3 Table 1-3. NonStop TCP/IPv6 Components and Product Numbers on Integrity NonStop Servers 1-3 Table 2-1. Fault-Tolerant Behavior; NonStop TCP/IP Process Compared to TCP6SAM 2-7 Table 2-2. Commands and Object Types for TCP6SAM 2-8 Table 3-1. Names Comparison Between Parallel Library TCP/IP and NonStop TCP/IPv iii

6 Contents Tables iv

7 What s New in This Manual Manual Information Abstract Version HP NonStop TCP/IPv6 Migration Guide This manual discusses the differences between HP NonStop TCP/IP and NonStop TCP/IPv6 and the differences between Parallel Library TCP/IP and NonStop TCP/IPv6. NonStop TCP/IPv6 G06, NonStop TCP/IPv6 G06 and H01 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs and H06.03 and all subsequent H-series RVUs until otherwise indicated in a new edition. Part Number Published July 2005 Document History Part Number Product Version Published NonStop TCP/IPv6 G06 May NonStop TCP/IPv6 G06 December NonStop TCP/IPv6 G06 December NonStop TCP/IPv6 G06, H01 July 2005 New and Changed Information This manual has been updated to reflect support for the HP Integrity NonStop NS-series server. WAN Wizard Pro now supports NonStop TCP/IPv6 so that constraint was removed from Constraints on page 1-6. As of G06.24, you no longer have to add a DEFINE for the shared runtime library (SRL) before starting TCP6SAM so this DEFINE was removed from DEFINEs on page 3-4. The BPID field in the LISTDEV sample displays in the subsection Determining the Name of the Socket Access Method on page 2-1 has been changed to accurately reflect the current displays. v

8 What s New in This Manual New and Changed Information vi

9 About This Guide This guide is intended for network and system administrators, application programmers, and IT professionals seeking an overview of the migration considerations for NonStop TCP/IPv6. Network and system administrators who are going to configure the NonStop TCP/IPv6 environment and application programmers who plan to use NonStop TCP/IPv6 should use this guide to find out about any migration issues that affect their configuration or applications. This guide provides information about migrating your NonStop TCP/IP applications and your Parallel Library TCP/IP applications to the NonStop TCP/IPv6 environment including current restrictions of NonStop TCP/IPv6 and management considerations. This guide assumes that you have a working knowledge of industry-standard TCP/IP, and are familiar with HP NonStop S-series server and NonStop NS-series server architecture, NonStop TCP/IP or Parallel Library TCP/IP, and the ServerNet LAN systems access (SLSA) subsystem. How This Guide is Organized Use this manual as follows: Use Section 1, Introduction, to obtain a brief overview of the features offered by NonStop TCP/IPv6, definitions, system requirements, product components and product numbers, an overview of the main differences between NonStop TCP/IP and NonStop TCP/IPv6 and the differences between Parallel Library TCP/IP and NonStop TCP/IPv6, and the constraints of NonStop TCP/IPv6. Use Section 2, Transport-Service Provider Differences for NonStop TCP/IPv6, to learn about TCP6SAM, the socket access method provided by NonStop TCP/IPv6 for backward-compatibility with existing NonStop TCP/IP applications. Use Section 3, Migration Considerations, to get more detailed information about the differences between NonStop TCP/IP and NonStop TCP/IPv6 and between Parallel Library TCP/IP and NonStop TCP/IPv6. Finally, use Section 4, Procedures for Migrating to NonStop TCP/IPv6, for an overview of migrating applications to NonStop TCP/IPv6. Related Manuals This subsection lists manuals that are referred to in this guide as well as related manuals that serve as prerequisites or co-requisites to this guide. Other Manuals and Books about TCP/IP The TCP/IP Configuration and Management Manual provides information about the NonStop TCP/IP product. -vii

10 The TCP/IP (Parallel Library) Configuration and Management Manual describes the installation, configuration, and management of the Parallel Library TCP/IP subsystem. The TCP/IPv6 Configuration and Management Manual describes the installation, configuration, and management of the NonStop TCP/IPv6 subsystem. The TCP/IP Applications and Utilities User Guide describes the interactive interfaces and the utilities that work with all NonStop TCP/IP subsystems, including, ECHO, FINGER, FTP, LISTNER, TFTP, TELNET, and TN6530. Server information is included for FTP, TFTP, and TELNET. The TCP/IP Programming Manual describes how to program to the Guardian sockets library for NonStop TCP/IP, Parallel Library TCP/IP, and NonStop TCP/IPv6. For an overview of TCP/IP, see the book TCP/IP Illustrated by W. Richard Stevens, Prentice Hall, Other Related Manuals The Interactive Upgrade Guide 2 provides migration considerations and highlights pertaining to G-series and H-series RVUs. The G06.nn Software Installation and Upgrade Guide and the H06.nn Software Installation and Upgrade Guide provide information about installing certain required files such as the PROTOCOL configuration file. The G06.nn Release Version Update Compendium and the H06.nn Release Version Update Compendium provide overviews of the major changes in a G-series or H-series RVU. The Open System Services Programmer s Guide describes how to develop socket applications for the HP NonStop Open System Services (OSS) environment. The QIO Configuration and Management Manual describes how to install and manage a QIO data communications subsystem. This manual also describes the SCF command used to configure, control, and inquire about the QIO subsystem. This manual also provides procedures for running NonStop TCP/IPv6 in KSEG2. The Operator Messages Manual contains the operator messages distributed by the Event Management Service (EMS) for NonStop TCP/IPv6. The LAN Configuration and Management Manual describes the SLSA subsystem which provides parallel LAN I/O for NonStop S-series systems. In particular, read about logical interfaces (LIFs) and physical interfaces (PIFs) in that manual. -viii

11 Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on -ix

12 each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [, new-value ]... [ - ] { }... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name -x

13 Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [, attribute-spec ]...!i and!o. In procedure calls, the!i notation follows an input parameter (one that passes data to the called procedure); the!o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id!i, error ) ;!o!i,o. In procedure calls, the!i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ;!i,o!i:i. In procedure calls, the!i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length!i:i, filename2:length ) ;!i:i!o:i. In procedure calls, the!o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum!i, [ filename:maxlen ] ) ;!o:i Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. -xi

14 -xii

15 1 Introduction This section provides an overview of the NonStop TCP/IPv6 product, definitions of the terms used in this guide, system requirements, product components and product numbers, a summary of the differences between NonStop TCP/IP and NonStop TCP/IPv6 and the differences between Parallel Library TCP/IP and NonStop TCP/IPv6, a list of the current constraints of NonStop TCP/IPv6, and product compatibility. Note. Parallel Library TCP/IP is not supported on Integrity NonStop servers. Topics covered in this section include: Overview Definitions on page 1-2 System Requirements on page 1-2 Product Components and Product Numbers on page 1-2 Summary of Differences Between NonStop TCP/IP and NonStop TCP/IPv6 on page 1-4 Summary of Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 on page 1-5 Constraints on page 1-6 Compatibility on page 1-7 Overview NonStop TCP/IPv6 is an HP networking product that provides increased performance and scalability over NonStop TCP/IP and adds the option of TCP/IP version 6 capability to the Parallel Library TCP/IP product. The main features of NonStop TCP/IPv6 are: Runs on NonStop S-series servers and Integrity NonStop NS-series servers When run in INET mode (TCP/IP version 4 only), is a direct replacement for Parallel Library TCP/IP Coexists and can run simultaneously with NonStop TCP/IP on G06.20 and later G-series RVUs Cannot coexist with Parallel Library TCP/IP on the same NonStop S-series system (Parallel Library TCP/IP is not supported on Integrity NonStop servers) Runs in multiple processors Uses a distributed architecture that facilitates load distribution 1-1

16 Introduction Definitions Can be configured to make a multi-processor NonStop server appear as a single IP host to the outside world Uses ServerNet to route connection requests directly from the ServerNet adapter to the processor containing the listening application Supports Ethernet adapters Definitions The NonStop TCP/IPv6 architecture reassigns the functionality of the NonStop TCP/IP process to a shared runtime library (SRL) on NonStop S-series servers or a dynamic linked library (DLL) on Integrity NonStop servers, as well as to the manager process, to the monitor process, and to the socket access method process. Table 1-1 roughly identifies the equivalent features from NonStop TCP/IP that these new components replace. (An exact mapping is not required for a general understanding of the NonStop TCP/IPv6 components.) Table 1-1. Comparison of Features This NonStop TCP/IPv6 Feature Replaces... Shared Runtime Library (SRL) (NonStop S-series servers) Dynamic Linked Library (DLL) (Integrity NonStop servers) TCP6SAM TCP6MAN TCP6MON Persistence Manager... from NonStop TCP/IP the protocol processing that happens in the TCP/IP process the protocol processing that happens in the TCP/IP process the Guardian socket open and close processing of the TCP/IP process the configuration and management processing of the TCP/IP process the error recovery and adjunct protocol processing of the TCP/IP Process None. NonStop TCP/IP did not participate in this feature. System Requirements NonStop TCP/IPv6 requires a NonStop S-series system running the G06.20 or later RVU with at least 128 MB of processor memory or an Integrity NonStop server running H06.03 or later. Product Components and Product Numbers All product components listed in this subsection are shipped with G06.20 and later RVUs and H06.03 or later RVUs. 1-2

17 Introduction Product Components and Product Numbers Table 1-2. NonStop TCP/IPv6 Components and Product Numbers on NonStop S-Series Servers Product Module Object Code Name Product Number TCP/IPv6 Manager Process TCP6MAN T1266G06 TCP/IPv6 Monitor Process TCP6MON T1265G06 TCP/IPv6 Shared Resource Library ZTCP6SRL/ZTCP6REL T1265G06 TCP/IPv6 Socket Provider Process TCP6SAM T1265G06 TCP/IPv6 Ptrace Product Module ZTC6PTR T1267G06 TCP/IPv6 SCF Product Module ZTC6SCF T1268G06 TCP/IPv6 Neighbor Discovery Process ND6HOSTD T2701G06 Native Socket Library* T0372G08 Socket Library* T9550G08 Table 1-3. NonStop TCP/IPv6 Components and Product Numbers on Integrity NonStop Servers Product Module Object Code Name Product Number TCP/IPv6 Manager Process TCP6MAN T1266H01 TCP/IPv6 Monitor Process TCP6MON T1265H01 TCP/IPv6 Dynamic Linked Library ZTCP6DLL T1265H01 TCP/IPv6 Socket Provider Process TCP6SAM T1265H01 TCP/IPv6 Ptrace Product Module ZTC6PTR T1267H01 TCP/IPv6 SCF Product Module ZTC6SCF T1268H01 TCP/IPv6 Neighbor Discovery Process ND6HOSTD T2701H01 Native Socket Library* T0372H01 Socket Library* T9550H01 1-3

18 Introduction Summary of Differences Between NonStop TCP/IP and NonStop TCP/IPv6 Summary of Differences Between NonStop TCP/IP and NonStop TCP/IPv6 This subsection summarizes the differences between NonStop TCP/IP and NonStop TCP/IPv6. It lists behavioral differences but does not compare the architectural differences between the two subsystems. (Table 1-1 on page 1-2 provides a comparison of the architectural components of the two subsystems.) The following alphabetical list of differences between NonStop TCP/IP and NonStop TCP/IPv6 is organized by a keyword that describes the topic. Cross-references are provided for further explanation of the topic. Applications: Unless configured with logical network partitioning, subnets are available to all applications. See Applications: Restricting Access to Network Interfaces on page 3-2. Also, there are considerations for applications that can be spawned in any processor. See the Note on page 4-2. Configuration Files: There are required changes to PROTOCOL configuration file and there is a new configuration file. See Configuration Files on page 3-4. DEFINEs: There are new system DEFINEs. See DEFINEs on page 3-4. Also see Configuring Applications to Use NonStop TCP/IPv6 on page 2-5. Errors: Errors are handled differently. See Error Treatment on page 3-4. Fault-tolerance: Fault-tolerant behavior is different in some circumstances. See Fault-Tolerant Behavior on page 3-5. Also see NonStop Operations on page 3-7. Firewall Considerations: There is a migration consideration for firewalls. See Firewall Considerations on page 3-5. Guardian Socket Migration: There are programming considerations for enhancing performance when an application migrates a Guardian socket to another processor. See Management Interfaces on page 3-5. Management Interfaces: There are differences in the SCF and SPI interfaces to NonStop TCP/IPv6. See Management Interfaces on page 3-5. Modes: NonStop TCP/IPv6 has three operating modes; NonStop TCP/IP only has one operating mode. See Modes on page 3-7. NonStop Operations: NonStop TCP/IPv6 supports Ethernet failover which provides fault-tolerance at the adapter level. See the NonStop Operations on page 3-7. Persistence Manager: There are differences in how you manage the Persistence Manager for NonStop TCP/IPv6. See Persistence Manager on page 3-7. Platform: NonStop TCP/IPv6 does not run on NonStop k-series servers. See Platform on page

19 Introduction Summary of Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 Port Sharing: You can specify a port range for listening applications in NonStop TCP/IPv6. See DEFINEs on page 3-4. Resource Management: There are some differences in processor utilization for applications. See Resource Management on page 3-8. Retransmission Timer Enhancements: There are new attributes and new socket options available. See Retransmission Timer Enhancements on page 3-8. Round-Robin Filtering: Incoming connections can be distributed among applications that share a port and run in different processors. See Round-Robin Filtering on page 3-9. Shared Runtime Library: NonStop TCP/IPv6 uses a private SRL on NonStop S-series servers. See Shared Run-Time Library (SRL) on page 3-9 for considerations regarding the SRL. SPI: Subsystem Programmatic Interface (SPI) support is limited. See SPI Interface on page 3-9. SWAN: There are new procedures for the ServerNet wide area network (SWAN) subsystem. See SWAN on page 3-9. System Configuration Database: Configuration attributes are stored automatically in the system configuration database. See System Configuration Database on page 3-9. TELSERV: Static windows and servers in TELSERV must be added in your startup command file or by using SCF. In addition, the RESILIENT ON attribute of TELSERV does not work in combination with round-robin filtering. See Telserv on page Tracing: There are some new considerations for tracing. See Trace on page 2-8 and Trace on page Tips for Migrating: For general tips for migrating from NonStop TCP/IP to NonStop TCP/IPv6, see Tips for Migrating from NonStop TCP/IP to NonStop TCP/IPv6 on page Summary of Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 This subsection summarizes the differences between Parallel Library TCP/IP and NonStop TCP/IPv6. The following alphabetical list of differences between Parallel Library TCP/IP and NonStop TCP/IPv6 is organized by a keyword that describes the topic. Cross-references are provided for further explanation of the topic. Addresses: IPv6 addresses are available for NonStop TCP/IPv6 SUBNETs. See Addresses on page

20 Introduction Constraints Applications: Applications may need to change to run on NonStop TCP/IPv6. See Applications on page In addition, with NonStop TCP/IPv6, you can restrict access to network interfaces by using the logical network partitioning feature. See Applications: Restricting Access to Network Interfaces on page 3-2. Configuration Files: There is a new TCP/IP configuration file called IPNODES and a required change to an existing TCP/IP configuration file. See Configuration Files on page DEFINEs: There are new system DEFINEs. See Configuring Applications to Use NonStop TCP/IPv6 on page 2-5 and DEFINEs on page Dynamic Linked Library: NonStop TCP/IPv6 uses a DLL on H-series RVUs. You do not have to do anything for DLL usage; it is used automatically by the subsystem. See Dynamic Linked Library (DLL) on page EMS: There are some changes to EMS. See Event Messages on page Management Interfaces: There are differences in the SCF and SPI interfaces to NonStop TCP/IPv6. See Management Interfaces on page Modes: NonStop TCP/IPv6 has three operating modes. See Modes on page Multicast: There are changes to multicast operations. See Multicast Operations on page Name Changes: Many of the common objects in Parallel Library TCP/IP have changed. See Name Changes on page Processes and Protocols: There is a new process and new protocols available in NonStop TCP/IPv6. See Processes and Protocols on page Retransmission Timer Enhancements: There are new attributes and new socket options available. See Retransmission Timer Enhancements on page Constraints The following alphabetical list of constraints is organized by a keyword that describes the topic. Adapter Support: The token-ring ServerNet adapter (TRSA) and the ATM ServerNet adapter (ATM3SA) are not supported. (Only Ethernet adapters are supported by NonStop TCP/IPv6.) Domain Name System (DNS) Support: NonStop TCP/IPv6 in INET6 mode or in a pure IPv6 network does not support DNS queries. Parallel Library TCP/IP: Parallel Library TCP/IP and NonStop TCP/IPv6 cannot run on the same system. Protocol Support: ATM and X.25 and SNAP type SUBNETs are not supported. 1-6

21 Introduction Compatibility Security: Only a super-group user can start TCP6SAM and TCP6MAN from TACL. SNMP: The Simple Network Management Protocol is supported only in INET (IPv4) mode. SWAN: SWAN is supported only in INET (IPv4) mode. TCP6SAM: TCP6SAM must run in a processor with TCP6MON configured. Version Compatibility: The TCP6SAM version must match the QIO version. Compatibility NonStop TCP/IPv6 is binary-compatible with D30 and later versions of the socket library. TCP6SAM does not support pre-d30 socket library requests. If TCP6SAM receives a pre-d30 socket library request, it returns the error: FEDIALECTUNSUPPORTED. 1-7

22 Introduction Compatibility 1-8

23 2 Transport-Service Provider Differences for NonStop TCP/IPv6 This section describes the transport-service provider, TCP Socket Access Method (TCP6SAM). If you are migrating NonStop TCP/IP socket applications to NonStop TCP/IPv6, you should read this section to familiarize yourself with how to access and manage TCP6SAM. In addition, this section describes fault-tolerant behavioral differences between TCP6SAM and the NonStop TCP/IP process that you should be aware of when using NonStop TCP/IPv6 for your socket applications. TCP6SAM is a process pair provided for backward compatibility with NonStop TCP/IP socket applications. TCP6SAM is not in the data path but provides applications with a name for a socket transport-service provider. By specifying the TCP6SAM process as the name of the socket transport-service provider, the application programmer can access NonStop TCP/IPv6 without having to reconfigure the application (unless you want the application to use IPv6 sockets; see Migrating Your Application to NonStop TCP/IPv6 on page 4-2). No restriction exists on the number of instances of TCP6SAM processes running in a system unless you have configured logical network partitioning (LNP). For LNP, you can run an unlimited number of TCP6SAM processes in the default partition but only two TCP6SAM processes in each of the configured partitions. TCP6SAM names consist of any five alphanumeric characters. Note. The Expand application expects a TCP/IP process name to start with Z. This section covers the following topics: Determining the Name of the Socket Access Method Configuring Applications to Use NonStop TCP/IPv6 on page 2-5 Compatibility on page 2-6 SCF on page 2-8 Determining the Name of the Socket Access Method In NonStop TCP/IP, the transport-service provider was the name of the TCP/IP process (usually $ZTC0). In NonStop TCP/IPv6, the transport-service provider is the name of a TCP6SAM process. To use NonStop TCP/IPv6 for your socket applications, you need to know the name of a TCP6SAM process and set that name to be the transport-service provider. 2-1

24 Transport-Service Provider Differences for NonStop TCP/IPv6 Logical Network Partitioning (LNP) To determine the name of a TCP6SAM process for use as a transport-service provider, issue the following command: -> LISTDEV TCPIP This SCF LISTDEV command lists all the TCP/IP processes. A program name in the SCF LISTDEV display of TCPIP means that the program is a NonStop TCP/IP process; a program name of TCP6SAM means that the program is a NonStop TCP/IPv6 process. The following display shows a sample result of the SCF LISTDEV TCPIP command. LDev Name PPID BPID Type RSize Pri Program 107 $ZTCP0 0,285 1,287 (48,0) \MYSYS.$SYSTEM.SYS03.TCPIP 141 $ZSAM3 3,269 (48,0) \MYSYS.$SYSTEM.SYS03.TCP6SAM 154 $ZTC0 0,299 1,286 (48,0) \MYSYS.$SYSTEM.SYS03.TCPIP 158 $ZTCP1 1,293 0,302 (48,0) \MYSYS.$SYSTEM.SYS03.TCPIP 190 $ZSAM2 1,310 (48,0) \MYSYS.$SYSTEM.SYS03.TCP6SAM In this example, the processes $ZSAM3 and $ZSAM2 are TCP6SAM processes. These are the processes you would select when specifying the transport-service provider name for your applications to access NonStop TCP/IPv6. (It does not matter which TCP6SAM process you select as the transport-service provider unless you are using Logical Network Partitioning (LNP).) If no TCP6SAM process appears and you want to use NonStop TCP/IPv6, see the TCP/IPv6 Configuration and Management Manual for procedures for starting the subsystem. Logical Network Partitioning (LNP) You can configure NonStop TCP/IPv6 to use LNP, a feature that allows you to partition the system into separately addressed subnetworks. When you use this feature, be careful when selecting the TCP6SAM process to use as the transport-service provider for your application. When the subsystem is configured with LNP, applications are restricted to the network interfaces associated with the TCP6SAM process chosen as the application s transport-service provider. The LNP configuration is similar to conventional NonStop TCP/IP because the TCP6SAM process only provides access to the network interfaces of its associated SUBNET objects. To determine if you have LNP configured on your system, use the INFO MON *, DETAIL command. This command tells you how many LNPs are configured, not 2-2

25 Transport-Service Provider Differences for NonStop TCP/IPv6 Logical Network Partitioning (LNP) including the default LNP. In the following example, the field shown in bold in the display shows that one LNP is configured: TCPIPV6 DETAILED INFO MON \BEAR.$ZZTCP.#ZPTM2 *TCP SEND SPACE D *TCP RECEIVE SPACE D *UDP SEND SPACE D *UDP RECEIVE SPACE D *DELAY ACK TIME *DELAY ACK... ON *KEEP ALIVE IDLE *KEEP ALIVE RETRY CNT 8 *KEEP ALIVE INTERVAL.. 75 QIO LIMIT % *HOST ID... 0D *HOST NAME... TCP0 PROGRAM FILENAME... \BEAR.$SYSTEM.SYS02.TCPMON *DEBUG... OFF *FULL DUMP... ON *ALL NETS ARE LOCAL... ON *TCP COMPAT ON *EXPAND SECURITY... OFF *TCP PATH MTU... OFF *TCP TIME WAIT TRACE STATUS... OFF TRACE FILENAME... *RFC1323 ENABLE... ON *TCP INIT REXMIT TIMEOUT 1000 MS *TCP MIN REXMIT TIMEOUT MS *TCP LISTEN QUEUE MIN *INITIAL TTL *MIN-EPHEMERAL-PORT *MAX-EPHEMERAL-PORT *MAX-PRIV-PORT *TCPCWNDMULTIPLIER... 2 *TCP SACK... OFF *NONSHAREDOUTDIST... OFF *FAMILY DUAL TOTAL LNPS CONFIGURED.. 1 *TCP MAX REXMIT TIME MS *TCP MAX REXMIT COUNT *TCP TOTAL REXMIT DURATION MS To find out which TCP6SAM processes are configured for which LNPs, use the INFO SUBNET *, DETAIL command. In the following example, the fields shown in bold show that the TCP6SAM processes associated with LNP index 1 are $ZSAM1 and 2-3

26 Transport-Service Provider Differences for NonStop TCP/IPv6 Logical Network Partitioning (LNP) $ZSAM2. The INFO SUBNET DETAIL command also shows the IP addresses for the LNPs. TCPIPV6 DETAILED INFO SUBNET \MYSYS.$ZZTCP.#ZPTM0.SN1 AF_INET: NAME DEVICENAME *IPADDRESS/DST_IPADDR TYPE *SUBNETMASK *R SN1 \MYSYS.LAN ETHERNET %HFFFFFF00 N TRACE STATUS... OFF TRACE FILENAME... INTERFACE MTU LNP... DEFAULT INDEX > INFO SUBNET $ZZTCP.#ZPTM0.SN3, DETAIL TCPIPV6 DETAILED INFO SUBNET \MYSYS.$ZZTCP.#ZPTM0.SN3 AF_INET: NAME DEVICENAME *IPADDRESS/DST_IPADDR TYPE *SUBNETMASK *R SN3 \MYSYS.LAN ETHERNET %HFFFFFF00 N TRACE STATUS... OFF TRACE FILENAME... INTERFACE MTU LNP... $ZSAM1 $ZSAM2 INDEX... 1 AF_INET6: NAME DEVICENAME LINKLEVELADDRESS TYPE SN3 \MYSYS.LAN14 FE80::A10:8EFF:FE00:9B23 ETHERNET *IPV6MTU *IPV6HOPLIMIT *IPV6REACHABLETIME MS *IPV6RETRANSMITIMER MS *IPV6DADRETRIES... 1 *IPV6NUD... ON *IPV6RAENABLE... ON LNP... $ZSAM1 $ZSAM2 INDEX... 1 MULTICASTADDRESS.. FF02::1:FF00:9B23 MULTICASTADDRESS.. FF02::1 Note that you cannot determine the names of the TCP6SAM processes for the default partition in this manner because they are not listed in the INFO SUBNET DETAIL command. To determine the TCP6SAM process names for the default partition (partition index number 0), perform the following additional steps: 1. Write down the TCP6SAM process names that are listed in the LNP field of the INFO DEFAULT display. 2. Issue the SCF LISTDEV TCPIP command. 3. Use your list of TCP6SAM names to eliminate the LNP-assigned TCP6SAM processes. The remaining TCP6SAM processes are associated with the default LNP. These processes have access only to the SUBNETs in the default partition. 2-4

27 Transport-Service Provider Differences for NonStop TCP/IPv6 Configuring Applications to Use NonStop TCP/IPv6 Configuring Applications to Use NonStop TCP/IPv6 Before migrating your applications to NonStop TCP/IPv6, note that: The TCP6SAM process does not have to be in the same processor as the application. Applications using NonStop TCP/IPv6 can run only in processors in which a TCP6MON process is configured and running. Extra care is required for selecting TCP6SAM processes in an LNP-configured environment. See Logical Network Partitioning (LNP) on page 2-2 and the TCP/IPv6 Configuration and Management Manual. Once you have determined the name of the TCP6SAM process for your transport-service provider, use an ADD DEFINE or PARAM command, or run a procedure call to inform your application of that process name. The DEFINE and PARAM syntax and procedure calls required depend on the environment (Guardian or OSS) in which you are running your application. To use IPv6 sockets, you also must port your socket applications to IPv6. See the TCP/IP Programming Manual for procedures for porting applications to IPv6. If any of your applications use the program name to determine if a TCP/IP transportservice provider process is TCPSAM, you need to change the application to look for TCP6SAM. See Name Changes on page Guardian Socket Applications To set Guardian socket applications to access NonStop TCP/IPv6, you must use one of the following ADD DEFINE or PARAM commands or a call to the socket_set_inet_name procedure to set the TCPIP^PROCESS^NAME to the TCP6SAM process name: ADD DEFINE =TCPIP^PROCESS^NAME, class map, file & $TCP6SAM-process-name PARAM TCPIP^PROCESS^NAME $TCP6SAM-process-name OSS Socket Applications For OSS socket applications to access NonStop TCP/IPv6, you can either add a DEFINE in the Guardian environment, use the add_define in the OSS environment, or programmatically use the socket_transport_name_set call to set the TCP/IP process name to the TCP6SAM process name. The following example shows the add_define method: add_define =TCPIP^PROCESS^NAME class=map file=\$tcp6sam-process-name 2-5

28 Transport-Service Provider Differences for NonStop TCP/IPv6 Compatibility Compatibility Consider these compatibility issues when using TCP6SAM: Event Management Service (EMS) Fault-Tolerant Behavior SCF on page 2-8 Trace on page 2-8 Event Management Service (EMS) TCP6SAM uses the same subsystem ID, ZTCI, as NonStop TCP/IP. The EMS messages issued by TCP6SAM are a subset of the ones issued by NonStop TCP/IP. Fault-Tolerant Behavior The difference in implementation between NonStop TCP/IP and TCP6SAM in terms of where the actual socket is created and what a socket backup open does results in a slightly different fault-tolerant behavior in TCP6SAM than in the TCP/IP process of NonStop TCP/IP. TCP6SAM can be started as a continuously available process pair similar to NonStop TCP/IP. Similarities When the TCP6SAM primary processor fails, the backup takes over as the primary. When the processor is reloaded, the primary creates a backup on that processor. When the TCP6SAM backup processor fails, the TCP6SAM primary process restarts the backup when the processor is reloaded. Differences Applications can be fault-tolerant, but sockets are not fault-tolerant in the NonStop TCP/IPv6 environment. Table 2-1 on page 2-7 lists other differences in fault-tolerant behavior. 2-6

29 Transport-Service Provider Differences for NonStop TCP/IPv6 Fault-Tolerant Behavior Table 2-1. Fault-Tolerant Behavior; NonStop TCP/IP Process Compared to TCP6SAM Failure Description TCP/IP primary process goes down TCP/IP primary processor goes down TCP/IP backup process goes down TCP/IP backup processor goes down Application primary dies NonStop TCP/IP as Transport-Service Provider Backup process takes over. All TCP sockets in the established state return ECONNRESET to the application and send RST to the remote end. Listen and UDP sockets survive. Backup process takes over. All TCP sockets in the established state return ECONNRESET to the application and send RST to the remote end. Listen and UDP sockets survive. All sockets survive. Socket is non-fault-tolerant until the backup TCP/IP is brought up. All sockets survive. Socket is non-fault-tolerant until the backup TCP/IP is brought up. A non-fault-tolerant application on that backup processor goes away. Backup application can take over and continue on the existing sockets. TCP6SAM as Transport- Service Provider Backup process takes over. All sockets survive. Backup process takes over. All sockets survive if the application is not on the failed processor (because the sockets are on the application processor, and might not be on the TCP6SAM processor). All sockets survive. All sockets survive (if the application is not on the failed processor). Backup application, upon takeover, receives the ECONNRESET error and has to close the socket. 2-7

30 Transport-Service Provider Differences for NonStop TCP/IPv6 SCF SCF TCP6SAM cannot be used for configuring NonStop TCP/IPv6. TCP6MAN must be used for configuration commands. See the TCP/IPv6 Configuration and Management Manual for more information about SCF for NonStop TCP/IPv6. TCP6SAM supports some SCF commands, which are shown in Table 2-2. TCP6SAM supports the PROCESS, SUBNET, and ROUTE objects but does not support the ENTRY, ADDRMAP, and SERVER objects. The TCP6SAM SCF nonsensitive commands, when applied to the PROCESS, ROUTE, and SUBNET objects, yield information about those objects in the processor where the TCP6SAM process resides. (For information about these objects on all configured processors, use the SCF commands for the TCP6MAN process. See the TCP/IPv6 Configuration and Management Manual for more information about SCF for NonStop TCP/IPv6.) Note. The TCP6SAM process displays TCPIP instead of TCPIPV6 in SCF return displays and does not display IPv6 addresses. Trace Table 2-2. Commands and Object Types for TCP6SAM Object Types SCF Command PROCESS ROUTE SUBNET ABORT Command X INFO Command X X X LISTOPENS Command X NAMES Command X X PRIMARY Command X STATS Command X X X STATUS Command X X X STOP Command X TRACE Command X VERSION Command X The SCF commands that are supported by TCP6SAM are discussed in detail in the TCP/IPv6 Configuration and Management Manual. Tracing in TCP6SAM primary and backup processes is enabled or disabled using the SCF TRACE START or STOP command. The Trace records are compatible with those generated by NonStop TCP/IP. The Trace records can be viewed and printed by the same PTrace module used by NonStop TCP/IP (ZTCIPTR). 2-8

31 3 Migration Considerations This section discusses the differences between NonStop TCP/IP and NonStop TCP/IPv6 and the differences between Parallel Library TCP/IP and NonStop TCP/IPv6. Differences Between NonStop TCP/IP and NonStop TCP/IPv6 Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 on page 3-11 NonStop TCP/IPv6, when run in INET or DUAL mode, is transparent for Guardian and OSS socket applications; specifying a TCP6SAM process in place of the NonStop TCP/IP or the TCPSAM process is all that is required to access NonStop TCP/IPv6. However, there are considerations that affect different kinds of applications. Those considerations are explained in this section. In addition, there are changes that must be made for applications to use the IPv6 (INET6 mode) features of NonStop TCP/IPv6. For complete SCF command syntax as well as subsystem configuration information and methods of maximizing the benefits of the NonStop TCP/IPv6 architecture, see the TCP/IPv6 Configuration and Management Manual. For information about porting applications to IPv6, see the TCP/IP Programming Manual. Differences Between NonStop TCP/IP and NonStop TCP/IPv6 Application Behavior on page 3-2 Applications: Restricting Access to Network Interfaces on page 3-2 Attribute Defaults on page 3-2 Configuration Files on page 3-4 DEFINEs on page 3-4 Error Treatment on page 3-4 Fault-Tolerant Behavior on page 3-5 Firewall Considerations on page 3-5 Management Interfaces on page 3-5 NonStop Operations on page 3-7 Persistence Manager on page 3-7 Platform on page 3-8 Resource Management on page 3-8 Round-Robin Filtering on page 3-9 Shared Run-Time Library (SRL) on page

32 Migration Considerations Application Behavior SPI Interface on page 3-9 SWAN on page 3-9 System Configuration Database on page 3-9 Telserv on page Trace on page 3-10 Tips for Migrating from NonStop TCP/IP to NonStop TCP/IPv6 on page 3-10 Application Behavior For AF_INET sockets using conventional TCP/IP, a backlog parameter value of less than or equal to 0 (zero) allows the socket to accept the number of connections configured for the TCP-LISTEN-QUE-MIN parameter of the transport process. These values can allow up to 5 connections (the default value for TCP-LISTEN-QUE-MIN). For AF_INET or AF_INET6 sockets using NonStop TCP/IPv6, a backlog parameter value of less than or equal to 0 (zero) is ignored. The maximum number of pending connections is always 5. Applications: Restricting Access to Network Interfaces SUBNETs are managed by TCP6MON, not by TCP6SAM. Because TCP6MON runs in all NonStop TCP/IPv6-configured processors, all SUBNETs and IP addresses are available to all applications regardless of the TCP6SAM process name specified as the transport-service provider. If you want to restrict application access to network interfaces, you must configure the subsystem to use logical network partitioning (LNP). When you use LNP, you configure SUBNETs with a list of TCP6SAM processes. This configuration limits access to these SUBNETs to applications using the specified TCP6SAM processes as their transport-service providers. For more information about LNP, see Logical Network Partitioning (LNP) on page 2-2 and the TCP/IPv6 Configuration and Management Manual. Attribute Defaults There are differences between NonStop TCP/IP and NonStop TCP/IPv6 for some of the SCF attributes and their defaults. These differences are shown in the following tables. ADD ROUTE ADD ROUTE Attribute NonStop TCP/IP NonStop TCP/IPv6 SUBNET No such attribute No default value FAMILY No such attribute INET ALLROUTES No such attribute OFF 3-2

33 Migration Considerations Attribute Defaults ADD SUBNET ADD SUBNET Attribute NonStop TCP/IP NonStop TCP/IPv6 SUNAME No default No such attribute GATEWAY OFF No such attribute ATMSEL 0 No such attribute ARPSERVER OFF No such attribute FAILOVER No such attribute No default MTU No such attribute No default LNPTPLIST No such attribute No default ALTER PROCESS/MON ALTER PROCESS/MON Attribute NonStop TCP/IP NonStop TCP/IPv6 UDPRECVSPACE bytes bytes TCPPATHMTU OFF ON ARPTIMER No default No such attribute TCP-MIN-REXMIT- 400 milliseconds 1000 milliseconds TIMEOUT TCP-LISTEN-QUE-MIN INITIAL-TTL MIN-EPHEMERAL-PORT No such attribute 1024 MAX-EPHEMERAL-PORT No such attribute ALTER SUBNET ALTER SUBNET Attribute NonStop TCP/IP NonStop TCP/IPv6 MTU 4464 or No default X25IDLETIME 2 minutes No such attribute ASSOCIATESUB No such attribute No default RESERVEDIP No such attribute No default FAMILY No such attribute INET 3-3

34 Migration Considerations Configuration Files TRACE PROCESS TRACE PROCESS Attribute NonStop TCP/IP NonStop TCP/IPv6 BACKUP No such attribute Not selected Configuration Files The new configuration file, IPNODES, functions like the HOSTS file and holds IPv6 addresses and, optionally, IPv4 addresses. A change is also required to the PROTOCOL file to support NonStop TCP/IPv6. See the TCP/IPv6 Configuration and Management Manual for more information about these files and the G06.nn Software Installation and Upgrade Guide or H06.nn Software Installation and Upgrade Guide for information about updating this file during installation. DEFINEs NonStop TCP/IPv6 has the following DEFINEs that are not present in NonStop TCP/IP: =PTCPIP^FILTER^KEY =PTCPIP^FILTER^TCP^PORTS =PTCPIP^FILTER^UDP^PORTS =TCPIP^NODE^FILE Error Treatment Defines the key or password for round-robin. Limits the TCP ports that applications share in round-robin filtering. See Round-Robin Filtering on page 3-9. Limits the UDP ports that applications share in round-robin filtering. See Round-Robin Filtering on page 3-9. Specifies the name of the IPNODES file to be used to resolve names An application programmatic interface (API) difference in NonStop TCP/IPv6 involves the EADDRINUSE error message. Because of the NonStop TCP/IPv6 architecture, a bind may fail with EADDRINUSE if a port is already in use. However, the bind may complete without an error, but the error is returned on the next socket request after the bind. Applications using the pre-d30 socket library are not compatible with NonStop TCP/IPv6 and will receive the error FEDIALECTUNSUPPORTED. Applications on a different system (remote socket requests) cannot use the NonStop TCP/IPv6 environment and will receive the error FEREQUESTUNSUPPORTED. For fault-tolerant socket applications, if the application primary process fails, the backup application receives an ECONNRESET error upon its first socket request after takeover. 3-4

35 Migration Considerations Fault-Tolerant Behavior An application programmatic interface (API) difference in NonStop TCP/IPv6 involves the error message returned for unresolved host names. TCP/IPv6 uses the getaddrinfo() routine to resolve the host name instead of gethostbyname() which returned the error "unknown host." The getaddrinfo() routine returns the following error when a host name cannot be resolved: "Name does not resolve to supplied parameters." Fault-Tolerant Behavior Most fault-tolerant behavior differences relate to TCP6SAM. Those differences are described in Section 2, The New Socket Provider. Two additional considerations concerning fault-tolerant behavior are: Differences in failure information reporting As in NonStop TCP/IP, in NonStop TCP/IPv6, if the TCP6MON or TCP6SAM process detects a failure condition, TCP6MON or TCP6SAM dials out the failure information to the Global Customer Support Center (GCSC) using HP Tandem Failure Data System (TFDS). However, if the failure is detected in the TCP/IP library within the application context, the TCP/IP library cannot call TFDS to notify GCSC. Upon failure of any NonStop TCP/IPv6 processor or TCP6MON process, applications connected to Guardian TCP sockets which were on that failed processor or process do not have their TCP connection reset. This behavior is unlike NonStop TCP/IP. For fault-tolerant socket applications, if the application primary process fails, the backup application receives an ECONNRESET error upon its first socket request after takeover. Firewall Considerations When considering migration to NonStop TCP/IPv6, ensure that your firewall products support gratuitous ARP packets. Management Interfaces This subsection describes differences in the management interfaces between NonStop TCP/IP and NonStop TCP/IPv6. Subsystem Name and ID The subsystem ID for NonStop TCP/IP is ZTCI. The name for NonStop TCP/IPv6 is ZTC6. TCPIPV6 replaces TCPIP as the subsystem name and should be used when requesting SCF help. 3-5

36 Migration Considerations Management Interfaces SCF For complete reference information about SCF and the SCF command syntax, see the TCP/IPv6 Configuration and Management Manual. See also SCF on page 2-5 for information about the SCF interface to TCP6SAM. Object Name Syntax Another level of qualification is required for the SUBNET, ROUTE, and ENTRY objects. In NonStop TCP/IPv6, the name syntax for these objects includes the MON object. The pound sign (#) still precedes the MON name but the SUBNET, ROUTE, and ENTRY objects no longer require the pound sign. Although placing a pound sign (#) in front of those objects does not generate an error, the preferred way to specify the lowest-level object is without the pound sign (#) as shown in the following naming specifications: SUBNET ROUTE ENTRY $TCP6MAN-name.#TCP6MON-name.subnet-name $TCP6MAN-name.#TCP6MON-name.route-name $TCP6MAN-name.#TCP6MON-name.entry-name SCF Objects The following SCF objects from NonStop TCP/IP are not supported in NonStop TCP/IPv6: SERVER ADDRMAP The MON object is new for NonStop TCP/IPv6. SCF Commands The following SCF commands from NonStop TCP/IP are not supported in NonStop TCP/IPv6: ALTER PROCESS STATS/RESET PROCESS Equivalent commands in NonStop TCP/IPv6 are: ALTER MON STATS/RESET MON New SCF Object Attributes A new attribute, MASTER, has been added and applies to the TCP6MON object. See Master TCP6MON. 3-6