HP NonStop TCP/IP (Parallel Library) Migration Guide Abstract This manual provides an overview of Parallel Library TCP/IP and compares it to conventional TCP/IP for configuration tasks including considerations for migrating from conventional TCP/IP to Parallel Library TCP/IP. Product Version Parallel Library TCP/IP G06 Supported Release Version Updates (RVUs) This manual supports G06.17 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 427650-001 Parallel Library TCP/IP G06 November 2000 429158-001 Parallel Library TCP/IP G06 April 2001 522272-001 Parallel Library TCP/IP G06 November 2001 522272-002 Parallel Library TCP/IP G06 August 2002 522272-003 Parallel Library TCP/IP G06 February 2005
HP NonStop TCP/IP (Parallel Library) Migration Guide Glossary Index Tables What’s New in This Manual iii Manual Information iii New and Changed Information About This Guide v How This Guide is Organized Related Manuals vi Notation Conventions vii iii v 1. Introduction Overview 1-1 Definitions 1-1 System Requirements 1-2 Product Components and Product Numbers 1-2 Summary of Differences Between Conventional TCP/IP and Parallel Library TCP/IP 1-3 Constraints 1-5 Compatibility 1-5 2.
3. Migration Considerations (continued) Contents 3. Migration Considerations (continued) Error Treatment 3-4 Fault-Tolerant Behavior 3-4 Firewall Considerations 3-5 Guardian Socket Migration 3-5 Management Interfaces 3-6 Persistence Manager 3-10 Resource Management 3-11 Round-Robin Filtering 3-12 Shared Run-Time Library (SRL) 3-12 SNMP 3-12 SPI Interface 3-12 SWAN 3-12 Telserv 3-12 Trace 3-13 Tips 3-13 4.
What’s New in This Manual Manual Information HP NonStop TCP/IP (Parallel Library) Migration Guide Abstract This manual provides an overview of Parallel Library TCP/IP and compares it to conventional TCP/IP for configuration tasks including considerations for migrating from conventional TCP/IP to Parallel Library TCP/IP. Product Version Parallel Library TCP/IP G06 Supported Release Version Updates (RVUs) This manual supports G06.
What’s New in This Manual New and Changed Information HP NonStop TCP/IP (Parallel Library) Migration Guide —522272-003 iv
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 Parallel Library TCP/IP. Network and system administrators who are going to configure the Parallel Library TCP/IP environment and application programmers who plan to use Parallel Library TCP/IP should use this guide to find out about any migration issues that affect your configuration or applications.
Related Manuals About This Guide Related Manuals This subsection lists manuals that are referred to in this guide and related manuals that serve as prerequisites or corequisites to this guide. Other Manuals and Books about TCP/IP • • • • • The TCP/IP Configuration and Management Manual provides some background information about TCP/IP fundamentals and complete information on the NonStop TCP/IP product (conventional TCP/IP).
Notation Conventions About This Guide 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.
General Syntax Notation About This Guide 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 can 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.
Change Bar Notation About This Guide 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 ]...
Change Bar Notation About This Guide HP NonStop TCP/IP (Parallel Library) Migration Guide —522272-003 x
1 Introduction This section provides an overview of the Parallel Library TCP/IP product, definitions of the terms used in this guide, system requirements, product components and product numbers, summary of the differences between conventional TCP/IP and Parallel Library TCP/IP, a list of the current constraints of Parallel Library TCP/IP, product compatibility, and coexistence and fallback strategy.
System Requirements Introduction Table 1-1. Comparison of Features This Library TCP/IP feature replaces... ... from Conventional TCP/IP Shared Runtime Library (SRL) the protocol processing that happens in the TCP/IP process TCPSAM the Guardian socket open and close processing of the TCP/IP process TCPMAN the configuration and management processing of the TCP/IP process TCPMON the error recovery and adjunct protocol processing of the TCP/IP Process Persistence Manager None.
Summary of Differences Between Conventional TCP/IP and Parallel Library TCP/IP Introduction The products Parallel Library TCP/IP depends upon are listed in Table 1-3: Table 1-3.
Introduction • • • • • • • • • • • • • • • • Summary of Differences Between Conventional TCP/IP and Parallel Library TCP/IP Fault-tolerance: Fault-tolerant behavior is different in some circumstances. See Event Management Service (EMS) on page 2-3 and Fault-Tolerant Behavior on page 3-4. Guardian Socket Migration: There are programming considerations for enhancing performance when an application migrates a Guardian socket to another processor. See Guardian Socket Migration on page 3-5.
Constraints Introduction Constraints The following list of constraints is alphabetically organized by a keyword that describes the topic. Cross-references are provided for items that need further explanation. • • • • • • • • • • Adapter Support: Token-ring ServerNet adapter (TRSA) is not yet supported. Applications: Applications must run in processors that have a TCPMON configured in them. Customer-Replaceable Units (CRUs): IOMF and PMF CRUs are not supported.
Compatibility Introduction HP NonStop TCP/IP (Parallel Library) Migration Guide —522272-003 1 -6
2 The New Socket Provider This section describes the new socket provider, TCP Socket Access Method (TCPSAM). To migrate conventional TCP/IP socket applications to Parallel Library TCP/IP, read this section to familiarize yourself with how to access and manage TCPSAM. This section also describes fault-tolerant behavioral differences between TCPSAM and the conventional TCP/IP process that you should be aware of when using Parallel Library TCP/IP for socket applications.
The New Socket Provider Configuring Applications to Use Parallel Library TCP/IP In this example, the processes $ZTC02 and $ZTC03 are TCPSAM processes. Select these processes when specifying the transport-service provider name for your applications to access Parallel Library TCP/IP. To create one or more TCPSAM processes, see the TCP/IP (Parallel Library) Configuration and Management Manual.
The New Socket Provider Compatibility Compatibility Consider these compatibility issues when using TCPSAM: • • • • Event Management Service (EMS) Fault-Tolerant Behavior SCF on page 2-5 Trace on page 2-5 Event Management Service (EMS) TCPSAM uses the same subsystem ID (ZTCI) as conventional TCP/IP. The EMS messages issued by TCPSAM are a subset of the ones issued by conventional TCP/IP.
Fault-Tolerant Behavior The New Socket Provider Table 2-1. Fault-Tolerant Behavior; Conventional TCP/IP Process Compared to TCPSAM Failure Description TCP/IP primary process goes down Conventional TCP/IP as Transport-Service Provider • • • TCP/IP primary processor goes down • • • TCP/IP backup process goes down • • TCP/IP backup processor goes down • • • Application primary dies • Backup process takes over.
SCF The New Socket Provider SCF TCPSAM cannot be used for configuring Parallel Library TCP/IP. TCPMAN must be used for configuration commands. For more information about SCF for Parallel Library TCP/IP, see the TCP/IP (Parallel Library) Configuration and Management Manual. TCPSAM supports some SCF commands, which are shown in Table 2-2. TCPSAM supports the PROCESS, SUBNET, and ROUTE objects but does not support ENTRY, ADDRMAP, and SERVER objects.
The New Socket Provider HP NonStop TCP/IP (Parallel Library) Migration Guide —522272-003 2 -6 Trace
3 Migration Considerations This section discusses the differences between the Parallel Library TCP/IP and conventional TCP/IP which you should consider when migrating to Parallel Library TCP/IP. Sample startup procedures for both subsystems are compared side-by-side to show the SCF differences as well as some procedural differences (such as a new system DEFINE). Finally, some tips are provided for consideration when migrating to Parallel Library TCP/IP.
Applications: Restricting to Listen on Only Some Subnets Migration Considerations • • • SWAN on page 3-12 Telserv on page 3-129 Trace on page 3-13 Applications: Restricting to Listen on Only Some Subnets Subnets are managed by TCPMON, not by TCPSAM.
Attribute Defaults and SCF Object Differences Migration Considerations ADD ROUTE Command Attribute Conventional TCP/IP Parallel Library TCP/IP CLONING No such attribute No default GENMASK No such attribute No default SUBNET No such attribute No default ADD SUBNET Command Attribute Conventional TCP/IP Parallel Library TCP/IP TYPE {LOOPBACK | ATM | ETHERNET | X25 | SNAP} No default Only TYPE ETHERNET is supported SUNAME No default No such attribute ARPSERVER Default OFF No such attrib
Error Treatment Migration Considerations ALTER SUBNET Command Attribute Conventional TCP/IP Parallel Library TCP/IP ASSOCIATESUB No such attribute No default MAX-EPHEMERAL-PORT No such attribute Default 65024 RESERVEDIP No such attribute No default TRACE SUBNET Command Attribute Conventional TCP/IP Parallel Library TCP/IP BULKIO | NOBULKIO No such attribute Default BULKIO Error Treatment An application programmatic interface (API) difference in Parallel Library TCP/IP involves the EADDRI
Migration Considerations Firewall Considerations 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 to GCSC. • • Upon failure of any Parallel Library TCP/IP processor or TCPMON 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 conventional TCP/IP.
Management Interfaces Migration Considerations Management Interfaces This subsection describes differences in the management interfaces between the conventional TCP/IP and Parallel Library TCP/IP. There is a different subsystem name described in Subsystem Name on page 3-6. The subsection about SCF describes the key differences in this interface, followed by a description of the new SCF attribute, Master TCPMON on page 3-7.
Migration Considerations Management Interfaces SCF Commands The following SCF commands from conventional TCP/IP are not supported in Parallel Library TCP/IP: • • ALTER PROCESS STATS/RESET PROCESS Equivalent commands in Parallel Library TCP/IP are: • • ALTER MON STATS/RESET MON New SCF Object Attributes A new attribute, MASTER, has been added and applies to the TCPMON object. See Master TCPMON. Naming Conventions The PROCESS object has the reserved name of $ZZTCP.
Management Interfaces Migration Considerations The following lists summarizes, in order of occurrence, the differences between configuring the two environments: • • • • • • • • You start a manager process in Parallel Library TCP/IP. Do not use a pound sign (#) for the ROUTE, ENTRY, and SUBNET objects for Parallel Library TCP/IP. Specify the subnet mask in the ADD SUBNET command in Parallel Library TCP/IP. In conventional TCP/IP, issue a separate ALTER SUBNET command to specify the subnet mask.
Management Interfaces Migration Considerations Parallel Library TCP/IP Command File + START MON * ==Run monitors in every processor. If you do not, ==then modify Steps 4 and 5 for the LISTNER, ==TCPSAM, and TELSERV processes to run only in ==those processors which have a monitor running in ==them. Conventional TCP/IP Command File ==There is no MON object +DELAY 2 ==Pause to allow MONs to start + ALTER MON *, HOSTNAME “breeze” + ALTER,HOSTNAME "breeze" + ALTER MON *, HOSTID 150.20.30.
Persistence Manager Migration Considerations 6. Start LISTNER and TELSERV. Parallel Library TCP/IP Conventional TCP/IP ADD DEFINE =TCPIP^PROCESS^NAME, class & map, file $ZTC1 ADD DEFINE =TCPIP^PROCESS^NAME, class & map, file $ZTC0 PARAM TCPIP^PROCESS^NAME $ZTC1 PARAM TCPIP^PROCESS^NAME $ZTC0 LISTNER/TERM $ZHOME, OUT $ZHOME, & NAME $LSN0,CPU 0,NOWAIT,& PRI 160/$SYSTEM.ZTCPIP.PORTCONF LISTNER/TERM $ZHOME, OUT $ZHOME, & NAME $LSN0,CPU 0,NOWAIT,& PRI 160/$SYSTEM.ZTCPIP.
Migration Considerations Resource Management T0470AAB or subsequent SPR, you do not need to start Parallel Library TCP/IP by running your startup script. If you are falling back to G06.09 or G06.08 (or to T0460AAA), you also need to run your Parallel Library TCP/IP startup scripts again to repopulate the configuration database.
Migration Considerations Round-Robin Filtering Round-Robin Filtering Parallel Library TCP/IP provides a new feature that enables listening applications running in different processors and sharing the same port (LIF) to share incoming connections. For information about this feature, see the TCP/IP (Parallel Library) Configuration and Management Manual. Shared Run-Time Library (SRL) Parallel Library TCP/IP places most of the protocol stack in a private SRL rather than in a process.
Migration Considerations Trace and retained by the new Telserv primary process when the primary Telserv process dies. However, in Parallel Library TCP/IP with round-robin enabled, the new TCPMON in the reloaded processor runs an automatic script to relaunch the Telserv process but the newly created Telserv process does not have knowledge of the previous configured STATIC service and STATIC window.
Migration Considerations HP NonStop TCP/IP (Parallel Library) Migration Guide —522272-003 3- 14 Tips
4 Procedures for Migrating Applications to Parallel Library TCP/IP This section lists, at a high level, the steps for migrating your applications to Parallel Library TCP/IP to familiarize you with the process. This section does not provide complete instructions; use the TCP/IP (Parallel Library) Configuration and Management Manual for subsystem configuration procedures. Tasks for Starting Parallel Library TCP/IP 1. Before starting Parallel Library TCP/IP, save the system configuration database. 2.
Procedures for Migrating Applications to Parallel Library TCP/IP Tasks for Migrating Your Environment c. Check all TCP/IP processes and find the one that has your TELSERV process listed as an opener. This is the conventional TCP/IP process that you do not want to migrate. >SCF ->LISTDEV TCPIP d. Select one of the TCP/IP processes from the list of processes. You can identify a Parallel Library TCP/IP process by looking at the name after the last period (.) in the Program field.
Procedures for Migrating Applications to Parallel Library TCP/IP Tasks for Migrating Your Application 5. ABORT any processes using the TCP/IP process whose IP address you want to migrate. Caution. Be careful if you use the wild-card (*) notation to abort processes in the following command; you can accidentally abort processes with similar names that are not openers of the process you want to migrate. ->ABORT PROCESS $opener-process-name 6.
Procedures for Migrating Applications to Parallel Library TCP/IP Tasks for Migrating Your Application 3. Determine the name of the TCPSAM process for use as the transport-service provider. See Determining the Name of the Socket Access Method on page 2-1. 4. Add the DEFINE, set the PARAM, or issue the procedure call to set the transport-service provider to the TCPSAM process name. See Guardian Socket Applications on page 2-2 and OSS Socket Applications on page 2-2.
Glossary This glossary defines the terms used in this manual. attribute. In DSM, a characteristic of an entity. For example, two attributes of a communications line might be its baud rate and its retry count. In a token-oriented interface based on SPI, an attribute of an object is usually expressed as either a simple token or as a field within an extensible structured token. BSD. Berkeley Software Distribution. connection. The path between two protocol modules that provides reliable stream delivery service.
driver/interrupt handler (DIH) Glossary driver/interrupt handler (DIH). QIO-based drivers used by the SLSA subsystem to communicate with the appropriate adapter type over the ServerNet system area network (SAN). The DIHs control the ServerNet adapters and use system-library routines accessible to LAN service-provider processes (such as TCP/IP). DSM. See Distributed Systems Management. E4SA. See Ethernet 4 ServerNet adapter (E4SA). EMS. See Event Management Service (EMS). error.
event message Glossary event message. Text intended for a system operator that describes a change in some condition in the system or network, whether minor or serious. The change of condition is called an event. Events can be operational errors, notifications of limits exceeded, requests for actions needed, and so on. Expand.
ICMP Glossary • 3865 GESA-F (T523572): a single-port fiber version compliant with the 1000 Base-SX standard (802.z). ICMP. See Internet control message protocol (ICMP). IEEE. See Institute of Electrical and Electronics Engineers (IEEE). IEEE 802.3. A local area network protocol suite commonly known as Ethernet. Ethernet has either a 10Mbps or 100Mbps throughput and uses Carrier Sense Multiple Access bus with Collision Detection (CSMA/CD. This method allows users to share the network cable.
Internet Protocol Glossary Internet Protocol. A data communications protocol that handles the routing of data through a network, which typically consists of many different subnetworks. IP is connectionless. It routes data from a source address to a destination address. interoperability. (1) Within an HP NonStop™ node, the ability to use the features or facilities of one environment from another.
MAC address (Media Access Control Address) Glossary MAC address (Media Access Control Address). A value in the Medium Access Control sublayer of the IEEE/ISO/ANSI LAN architecture, that uniquely identifies an individual station that implements a single point of physical attachment to a LAN. management applications. In DSM, an application process that opens a management or subsystem process to control a subsystem.
nowait mode Glossary nowait mode. In Guardian file-system operations and in some APS operations, the mode in which the called procedure initiates an I/O operation but does not wait for it to complete before returning control to the caller. To make the called procedure wait for the completion of the operation, the application calls a separate procedure. object.
persistence Glossary persistence. For the Subsystem Control Facility (SCF), the capability of a generic process to restart automatically if it was stopped abnormally. You configure this capability by specifying a nonzero AUTORESTART value in an ADD command. persistence manager. A NonStop Kernel subsystem process ($ZPM) that starts generic processes on G-series RVUs and manages their persistence. physical interface (PIF). The hardware components that connect a system node to a network. PIF.
scalable Glossary scalable. The architectural capacity to grow to accommodate growing computing demands. When an architecture is “scalable,” that means you can keep adding processing power as your computing needs grow. SCF. See Subsystem Control Facility (SCF). SCP. See Subsystem Control Point (SCP). sensitive command.
SMTP Glossary SMTP. See Simple Mail Transfer Protocol (SMTP). SNAP. See Subnetwork Access Protocol (SNAP). SPI. See Subsystem Programmatic Interface (SPI). subnet address. An extension of the Internet protocol (IP) addressing scheme that allows a site to use a single IP address for multiple physical networks.
summary state Glossary interface procedures; and definition files in Data Definition Language (DDL) for programmers writing their own subsystems. summary state. In DSM interfaces to HP data communications subsystems, one of the generally defined possible conditions of an object, with respect to the management of that object. A summary state differs from a state in two ways.
TELNET Glossary TELNET. The Internet standard protocol for remote terminal connection service. TELNET allows a user at one site to interact with remote timesharing systems at another site just as if the user's terminal is connected directly to the remote machine.
WAN manager process Glossary WAN manager process. The WAN manager process starts and manages the WAN subsystem objects including the ConMgr and WANBoot processes. WAN subsystem. See wide area network (WAN) subsystem. Warning. In DSM interfaces, a condition encountered in performing a command or other operation, that can be significant but does not cause the command or operation to fail. A warning is less serious than an error. Compare error. well-known port.
Glossary X25AM (X.
Index A D Adapter support 1-5 ADD command ENTRY 3-2 ROUTE 3-3 SUBNET 3-3 ADDRMAP, TCPSAM 2-5 ALTER command PROCESS 3-3 SUBNET 3-3 Applications constraints 1-5 differences 1-3 restricting, subnets to 3-2, 3-13 ARP packets, gratuitous, considerations 4-1 DEFINE new 1-3 SRL 3-9 SRL, for 3-8 TCPIP host file 3-10 transport-service provider 2-2 Definitions 1-1 Differences error treatment 3-4 fault-tolerance 2-3 management interfaces 3-6 persistence 1-4 resources 3-11 NonStop™ DOM 1-4, 3-10 SCF 3-6/3-10 shared
F Index Event Management Service (EMS) 2-3 Expand 2-1 F Fault 3-4 Fault tolerance behavior 2-3, 3-4/3-5 differences 1-4 Features 1-1 File system, product number 1-3 Firewall consideration 3-5 Firewall considerations 4-1 G Gratuitous ARP packets, considerations 4-1 Guardian socket applications 2-2 N Name, subsystem 3-6 Naming conventions 3-7 Network File System (NFS) 1-5 NFS See Network File System (NFS) NonStop S-series servers 1-1 NonStop™ Distributed Object Manager/MP 1-4, 3-10 NonStop™ DOM 1-4, 3-10
Q Index PTrace product number 1-2 version 1-2 Q QIO, product number 1-3 QIO, using functions of 3-12 R Resources, management of 3-11 Round-robin filtering 1-4, 3-12 ROUTE configuration 3-8 ROUTE, TCPSAM 2-5 RUN TCPMAN 3-8 RUN TCPSAM 3-9 S SCF commands 3-7 differences 1-4 differences in 3-6/3-10 new object attributes 3-7 object name syntax 3-6 objects 3-6 product number 1-2 TCPSAM, for 2-5 version 1-2 Security 1-5 ServerNet 1-1 ServerNet wide area network (SWAN) 3-12 SERVER, TCPSAM 2-5 Service provider,
U Index TCPMAN (continued) RUN 3-8 version 1-2 TCPMON function 1-2 master attribute 3-7 migration task 4-3 product number 1-2 version 1-2 TCPSAM determining the name of 2-1 function 1-2 product number 1-2 restriction 1-5 RUN 3-9 socket access method 2-1/2-5 starting 3-9 version 1-2 TCP/IP native socket library, product number 1-3 Telserv differences 1-4, 3-8 migration considerations 3-12 starting 3-10 Tips, configuration 3-13 Trace 2-5 TRACE command SUBNET 3-3, 3-4 Trace differences 3-13 Tracing 1-4 Trans
