HP NonStop TCP/IPv6 Migration Guide Abstract 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. Version 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.
Document History Part Number Product Version Published 524524-001 NonStop TCP/IPv6 G06 May 2003 524524-002 NonStop TCP/IPv6 G06 December 2003 524524-003 NonStop TCP/IPv6 G06 December 2004 524524-004 NonStop TCP/IPv6 G06, H01 July 2005
HP NonStop TCP/IPv6 Migration Guide Glossary Index 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 Tables v vii 1.
3. Migration Considerations Contents 3.
3. Migration Considerations (continued) Contents 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/IPv6 3-15 4.
Tables Contents HP NonStop TCP/IPv6 Migration Guide —524524-004 iv
What’s New in This Manual Manual Information HP NonStop TCP/IPv6 Migration Guide Abstract 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. Version 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.
What’s New in This Manual New and Changed Information HP NonStop TCP/IPv6 Migration Guide —524524-004 vi
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.
• • • • • 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.
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.
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.
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.
HP NonStop TCP/IPv6 Migration Guide —524524-004 -xii
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.
Definitions Introduction • • • 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 Integr
Product Components and Product Numbers Introduction Table 1-2.
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.
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.
Constraints Introduction • • • • • • • • • • • Applications: Applications may need to change to run on NonStop TCP/IPv6. See Applications on page 3-11. 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.
Compatibility Introduction • • • • • 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.
Compatibility Introduction HP NonStop TCP/IPv6 Migration Guide —524524-004 1 -8
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.
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.
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 ...... 61440D *TCP RECEIVE SPACE .. *UDP SEND SPACE ...... 9216D *UDP RECEIVE SPACE .. *DELAY ACK TIME....... 20 *DELAY ACK........... *KEEP ALIVE IDLE...... 75 *KEEP ALIVE RETRY CNT *KEEP ALIVE INTERVAL.. 75 QIO LIMIT.........
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 SN1 \MYSYS.LAN13 152.10.215.48 ETHERNET TRACE STATUS ........ OFF TRACE FILENAME ...... INTERFACE MTU ....... 1500 LNP... DEFAULT INDEX... 0 *SUBNETMASK %HFFFFFF00 *R N *SUBNETMASK %HFFFFFF00 *R N -> INFO SUBNET $ZZTCP.
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.
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.
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 NonStop 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.
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.
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.
Application Behavior Migration Considerations • • • • • • SPI Interface on page 3-9 SWAN on page 3-9 System Configuration Database on page 3-9 Telserv on page 3-109 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 proce
Attribute Defaults Migration Considerations 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 20800 bytes 41600 bytes TCPPATHMTU OFF ON A
Configuration Files Migration Considerations 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.
Fault-Tolerant Behavior Migration Considerations 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.
Management Interfaces Migration Considerations 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.
Modes Migration Considerations Naming Conventions The PROCESS object has the reserved name of $ZZTCP. The MON object has the reserved name of $ZPTMn, where n is the number (in hexadecimal) of the processor in which the MON resides. The ROUTE object has reserved names. The reserved names for ROUTE start with: EA, DDcpu-number, DAcpu-number, DRcpu-number, NDcpu-number, and RT. The names for ARP entries must start with EA.
Platform Migration Considerations persistence manger $ZPM after a system load. You must add the TCP6MAN process as a generic process to the NonStop Kernel subsystem to activate this feature. Note. TCP6SAM cannot be added as a generic process and therefore, even if TCP6MAN is restarted automatically by the persistence manager, you still must start TCP6SAM processes using interactive SCF or command files if you have applications that are using TCP6SAM as the transport-service provider.
Round-Robin Filtering Migration Considerations Round-Robin Filtering For NonStop TCP/IPv6, the round-robin filtering feature 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/IPv6 Configuration and Management Manual.
Telserv Migration Considerations TCP/IPv6 can be restarted automatically by the persistence manager. See Persistence Manager on page 3-7. Telserv If Telserv is running as a fault-tolerant pair in NonStop TCP/IPv6 environments, all configured Telserv static service information and static window information is captured and retained by the new Telserv primary process when the primary Telserv dies.
Differences Between Parallel Library TCP/IP and NonStop TCP/IPv6 Migration Considerations shipped with the SUT. See the G06.nn Software Installation and Upgrade Guide or the H06.nn Software Installation and Upgrade Guide for more information about installing these files and the TCP/IPv6 Configuration and Management Manual for more information about the TCP/IP configuration files.
Attribute Defaults Migration Considerations In Parallel Library TCP/IP, you cannot restrict access to the network interfaces; the network interfaces are available to all applications that are bound to INADDR_ANY. (You can bind an application to a specific IP address in either Parallel Library TCP/IP or NonStop TCP/IPv6.) In NonStop TCP/IPv6, you can configure the system in separately addressed subnetworks by using the logical network-partitioning feature.
DEFINEs Migration Considerations DEFINEs NonStop TCP/IPv6 has one new DEFINE: =TCPIP^NODE^FILE Specifies the name of the IPNODES file to be used to resolve names Dynamic Linked Library (DLL) Unlike Parallel Library TCP/IP, for NonStop TCP/IPv6, you do not need to define the shared runtime library (SRL) before using TCP6SAM. Event Messages Event messages show ZTC6 in the display, and new event messages have been introduced.
Multicast Operations Migration Considerations Multicast Operations Changes have been made to multicast operations in NonStop TCP/IPv6 when the subsystem is run in INET6 or DUAL mode. New socket options exist for the setsockopt and setsockopt_nw calls that support IPv6 multicast operations. See the TCP/IP Programming Manual for more information. Name Changes Many, though not all, names of the Parallel Library TCP/IP processes and IDs have changed for NonStop TCP/IPv6. Table 3-1.
Processes and Protocols Migration Considerations • • • Change application-startup files to specify the name of a TCP6SAM process for the transport-service provider. The TCP6SAM process displays TCPIP instead of TCPIPV6 in SCF return displays and does not display IPv6 addresses. Change the program name in the configuration database from $SYSTEM.SYSTEM.TCPMAN to $SYSTEM.SYSTEM.TCP6MAN, and change the DEFINE for SRL to ZTCP6SRL (you do not have to make these changes for Integrity NonStop servers).
Migration Considerations • • • • Tips for Migrating From Parallel Library TCP/IP to NonStop TCP/IPv6 Use TCPMAN (not TCPSAM) SCF commands to get a full description of the Parallel Library TCP/IP configuration. TCPSAM shows only partial configuration information about its own processor. To obtain a list of all running NonStop TCP/IP processes and all running TCP6SAM processes, enter LISTDEV TCPIP. To obtain a list of all TCP6MAN and TCP6MON processes, enter LISTDEV TCPIPV6.
4 Procedures for Migrating to NonStop TCP/IPv6 This section discusses migration at a high level and refers you to the TCP/IPv6 Configuration and Management Manual and the TCP/IP Programming Manual for detailed procedures.
Procedures for Migrating to NonStop TCP/IPv6 Migrating Your Application to NonStop TCP/IPv6 Migrating Your Application to NonStop TCP/IPv6 1. Find out if TCP6MON is running in all processors. Note. If your application can be spawned in any processor, and you do not configure a TCP6MON in every available processor, you need to change your application so that it does not spawn to a processor without a TCP6MON object. ->STATUS MON $ZZTCP.* 2. Decide whether to use logical network partitioning (LNP).
Glossary This glossary defines terms used both in this manual and in other NonStop TCP/IP manuals. Both industry-standard terms and HP terms are included. address. An IP-layer identifier for an interface or a set of interfaces. See also, deprecated address, preferred address, valid address and invalid address. address mask. A bit mask used to select bits from an Internet address for subnet addressing.
automatic tunneling Glossary automatic tunneling. IPv6-over-IPv4 tunneling where the IPv4 tunnel endpoint address is determined from the IPv4 address embedded in the IPv4-compatible destination address of the IPv6 packet being tunneled. autonomous system. A collection of gateways and networks that fall under one administrative entity and cooperate closely to propagate network reachability (and routing) information among themselves using an interior gateway protocol of their choice.
Class D Glossary INTERNET get their subnet class from the DCA's NIC (Network Information Center). The address classes of standalone, or entirely private, LANs are administered by the LAN administrator. Typical usage calls for all CLASS A addresses to have private LANs. Class D. A Class D address is a 4-octet multicast group address. The four high-order bits of the address are always 1110; therefore, the first octet is a number in the range 224 through 239 (%HE0 through %HEF).
context token Glossary context token. In DSM programmatic interfaces, a token in an SPI response message that indicates (by its presence or absence) whether or not the response is continued in the following message. If this token is present, the response is continued. To obtain the next message, the application program reissues the original command with one modification: the context token is included in the new command message.
definition Glossary definition. One of the declarations provided by HP for use in applications that call APS or SPI procedures. These definitions are provided in definition files. See also definition files. definition files. A set of files containing declarations for use in applications that call SPI procedures. SPI has a standard definition file for the Data Definition Language (DDL) and one for each of the programming languages supporting SPI; the latter files are derived from the DDL definition file.
ECHO Glossary ECHO. The name of a program used in the Internet to test the reachability of destinations by sending them an ICMP echo request and waiting for a reply. EGP (Exterior Gateway Protocol). The protocol used by a gateway in one autonomous system to advise the Internet addresses of networks in that autonomous system to a gateway in another autonomous system. Every autonomous system must use EGP to advertise network reachability to the core gateway system. empty response record.
Glossary Ethernet 4 ServerNet adapter (E4SA) Ethernet 4 ServerNet adapter (E4SA). A ServerNet adapter for Ethernet local area networks (LANs) that contains four Ethernet ports. event. In DSM terms, a significant change in some condition in the system or network. Events can be operational errors, notifications of limits exceeded, requests for action needed, and so on. event log. A file or set of files maintained by EMS to store event messages generated by subsystems. Event Management Service (EMS).
failover brother Glossary failover brother. The other SUBNET associated with the first SUBNET in a failover-enabled configuration. FDDI. See Fiber Distribution Data Interface (FDDI). Fiber Distribution Data Interface (FDDI). An emerging standard for a network technology based on fiber optics. FDDI specifies a 100-mbps data rate using 1300-nanometer light wavelength, and limits networks to approximately 200 km in length, with repeaters every 2 km or less.
GESA Glossary GESA. See Gigabit Ethernet ServerNet Adapter (GESA). GGP. See Gateway to Gateway Protocol. Gigabit Ethernet ServerNet Adapter (GESA). A single-port ServerNet adapter that provides Gigabit connectivity on a NonStop S-series server. The GESA installs directly into an existing Ethernet port, and multiple GESAs are supported in a system enclosure. global address. An address with unlimited scope. half-duplex mode.
host Glossary host. Any node that is not a router. ICMP. See Interior Gateway Protocol (IGP). 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. However, only one station can use the cable at a time.
International Telecommunications Union Telecommunications (ITU-T) Glossary International Telecommunications Union Telecommunications (ITU-T). An international body of member countries whose task is to define recommendations and standards relating to the international telecommunications industry. The fundamental standards for ATM have been defined and published by the ITU-T (previously CCITT). Internet.
ISO Glossary ISO. See International Organization for Standardization (ISO). ITU-T. See International Telecommunications Union Telecommunications (ITU-T). LAN (local area network). Any physical network technology that operates at high speed (usually tens of megabits per second through several gigabits per second) over short distances (up to a few thousand meters). LANMAN. See LAN manager (LANMAN) process. LAN. See local area network (LAN). LAN manager (LANMAN) process.
link-local address Glossary link-local address . An address having link-only scope that can be used to reach neighboring nodes attached to the same link. All interfaces have a link-local unicast address. link MTU. The maximum transmission unit, for example, maximum packet size in octets, that can be conveyed over a link. LLC (Logical Link Control). See Logical Link Control (LLC). LNP. See logical network partitioning. local area network (LAN).
MFIOB Glossary MFIOB. See multifunction I/O board (MFIOB). MILNET (Military Network). Originally part of the ARPANET, MILNET was partitioned in 1984 to make it possible for military installations to have reliable network service, while the ARPANET continues to be used for research. MILNET uses exactly the same hardware and protocol technology as ARPANET, and there are several interconnection points between the two. Thus, under normal circumstances, MILNET sites are part of the Internet. multicast.
object Glossary object. (1) In general HP use, one or more of the devices, lines, processes, and files in an HP subsystem; any entity subject to independent reference or control by one or more subsystems. (2) In DSM use, an entity subject to independent reference and control by a subsystem: for example, the disk volume $DATA or the data communications line $X2502. An object typically has a name and a type known to the controlling subsystem. object-name template.
PDN Glossary PDN. See Public Data Network (PDN). physical interface (PIF). The hardware components that connect a system node to a network. physical layer. Layer 1 in the OSI Reference Model. This layer establishes the actual physical connection between the network and the computer equipment. Protocols at the Physical Layer include rules for the transmission of bits across the physical medium and rules for connectors and wiring. PIF. See “physical interface (PIF).” PING. See Packet Internet Groper (PING).
response Glossary response. In DSM use, the information or confirmation supplied (as part of a response message) to an application by a subsystem in response to a DSM command. response message. An SPI message sent from a subsystem to an application program in reaction to a command message. Compare command message or event message. response record. In DSM programmatic interfaces, a set of response tokens usually describing the result when a command is performed on one object.
Glossary ServerNet LAN Systems Access (SLSA) subsystem processor multifunction (PMF) customer-replaceable unit (CRU), an I/O multifunction (IOMF) CRU, or a ServerNet adapter. ServerNet LAN Systems Access (SLSA) subsystem. A subsystem of the NonStop operating system. The SLSA subsystem enables the protocol I/O processes (IOPs) and drivers to access the ServerNet adapters. ServerNet wide area network (SWAN) concentrator.
SPI message Glossary SPI message. In DSM programmatic interfaces, a message specially formatted by the SPI procedures for communication between a management application and a subsystem or between one subsystem and another. An SPI message consists of a collection of tokens. Note that an SPI message is a single block of information sent at one time, as one interprocess message.
Glossary Subsystem Control Facility (SCF) Subsystem Control Facility (SCF). A part of DSM, used to provide a common, interactive management interface for configuring, controlling, and collecting information from HP data communications products. Subsystem Control Point (SCP). .n DSM, the management process for all HP data communications subsystems. There can be several instances of this process.
TELNET Glossary on the operating system and uses the IP protocol to transmit information across the Internet. It is possible to terminate (shut down) one direction of flow across a TCP connection, leaving a one-way (simplex) connection. The Internet protocol suite is often referred to as TCP/IP because TCP is one of the two most fundamental protocols. TELNET. The Internet standard protocol for remote terminal connection service.
unicast address Glossary unicast address. An identifier for a single interface. A packet sent to a unicast address is delivered to the interface identified by that address. User Datagram Protocol (UDP). The Internet standard protocol that allows an application program on one machine to send a datagram to an application program on another machine. UDP uses the Internet Protocol to deliver datagrams.
wild-card character Glossary wild-card character. A character that stands for any possible character(s) in a search string or in a name applying to multiple objects. In DSM object-name templates, two wild-card characters can appear: question mark (?) for a single character and asterisk (*) for zero, one, or more consecutive characters. See also object-name template. X.25. The CCITT standard protocol for transport-level network service. Originally designed to connect terminals to computers, X.
See WAN manager process.
Index A Adapter support 1-6 ADDRMAP, TCP6SAM 2-8 Applications differences 1-4, 1-6 migrating 4-2 restricting, to subnets 2-5, 3-11 ARP packets 3-5 ARP packets, gratuitous 4-1 C Caution, SRL 3-9 Class map 3-4 Coexistence, with conventional TCP/IP 1-1 Comparison, Parallel Library TCP/IP and NonStop TCP/IPv6 1-6 Compatibility 1-7, 2-6 Configuration files 1-4 Configuration tips 3-11 Constraints 1-5/1-7 D DEFINE IPNODES file 3-4 new 1-4, 1-6 transport-service provider 2-5 Define round-robin key 3-4 TCP port ra
G Index G O Gratuitous ARP packets 3-5, 4-1 Guardian socket applications 2-5 Guardian socket migration, differences 1-4 Open System Services (OSS) socket applications 2-5 OSM 4-1 I P IPNODES file define 3-4 PARAM tasks for migrating 4-2 transport-service provider 2-5 Persistence manager function 1-2 management differences 1-4 Platform 1-4 Port, sharing 1-5 Private SRL 3-9 Procedure call 2-5 Procedures, migration 4-2 Processor utilization 3-8 PROCESS, TCP6SAM 2-8 Product components 1-2 numbers 1-2 P
S Index S T SCF commands 3-6 new object attributes 3-6 object name syntax 3-6 objects 3-6 TCP6SAM, for 2-8 Security 1-7 ServerNet 1-2 ServerNet wide area network (SWAN) 3-9 SERVER, TCP6SAM 2-8 Service provider, transport 2-1 Shared runtime library (SRL) caution 3-9 definition 1-2 description 3-9 function 1-2 Single IP host 1-2 SNMP 3-9 Socket access method 2-1 Socket access method, TCP6SAM 2-1/2-8 Socket library product number 1-3 socket_set_inet_name 2-5 SPI differences 3-9 function 1-5 SRL See Shared
Z Index Z ZTCI 3-5, 3-13 ZTCP 3-5, 3-13 ZTCP6DLL 3-9 ZTCP6REL 1-3 ZTCP6SRL 3-9 Special Characters $ZTC0 2-1 HP NonStop TCP/IPv6 Migration Guide —524524-004 Index -4
