HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual Abstract This manual describes how to configure and manage the Parallel Library TCP/IP subsystem on an HP NonStop™ S-series server. Product Version Parallel Library TCP/IP G06 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 522271-002 Parallel Library TCP/IP G06 August 2002 522271-003 Parallel Library TCP/IP G06 September 2003 522271-004 Parallel Library TCP/IP G06 February 2004 522271-005 Parallel Library TCP/IP G06 September 2004 522271-006 Parallel Library TCP/IP G06 February 2005
HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual Glossary Index What’s New in This Manual ix Manual Information ix New and Changed Information Examples Figures Tables x About This Manual xi Who Should Use This Manual xi How to Use This Manual xi Required Background xii Parallel Library TCP/IP Core Manuals xii Background Manuals and Prerequisite Materials Notation Conventions xvii Abbreviations xx xv 1.
1. Configuration Quick Start (continued) Contents 1. Configuration Quick Start (continued) Tasks: Stopping Parallel Library TCP/IP and Clearing the Database 1-24 Stopping Parallel Library TCP/IP as a Generic Process 1-29 Task Summary 1-29 Tasks: Stopping Parallel Library TCP/IP as a Generic Process 1-29 2.
Contents 3. Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments (continued) 3. Configuring Parallel Library TCP/IP for Complex and HeavyUse Environments (continued) Configuration Example for the Hybrid Listening Model 3-21 Example for Two Gateways — Standard Listening Model 3-23 Parallel Library TCP/IP for Complex, Heavy-Use WAN Environments 3-29 4.
Contents 5. SCF Reference for Parallel Library TCP/IP (continued) 5.
Contents 5. SCF Reference for Parallel Library TCP/IP (continued) 5.
5. SCF Reference for Parallel Library TCP/IP (continued) Contents 5.
B. SCF Error Messages (continued) Contents B. SCF Error Messages (continued) PTCPIP 00020 PTCPIP 00022 PTCPIP 00027 PTCPIP 00035 PTCPIP 00036 PTCPIP 00037 PTCPIP 00038 PTCPIP 00039 PTCPIP 00040 B-5 B-5 B-5 B-5 B-6 B-6 B-6 B-6 B-7 C. Tracer Utility Running the Tracer Utility from a Terminal C-1 Glossary Index Examples Example 1-1. Example 1-2. Example 1-3. Example 1-4. Example 3-1. Example 3-2. Example 3-3. Example 3-4. Example 3-5. Example 3-6. Example 3-7. Example 3-8. Example 3-9. Example 4-1.
Figures (continued) Contents Figures (continued) Figure 2-2. Figure 2-3. Figure 2-4. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 3-7. Figure 3-8. Figure 3-9. Figure 3-10. Figure 3-11. Figure 5-1. Figure 5-2. Figure 5-3. Single IP Appearance, Parallel Library TCP/IP 2-3 Data Path Comparison: Conventional vs.
What’s New in This Manual Manual Information HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual Abstract This manual describes how to configure and manage the Parallel Library TCP/IP subsystem on an HP NonStop™ S-series server. Product Version Parallel Library TCP/IP G06 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
What’s New in This Manual New and Changed Information New and Changed Information • • In subsection ALTER MON Command for TCPMAN: ° The default value for the attribute DELAYACKSTIME int on page 5-26 has been changed from 5 to 20. ° The default (128) for the TCP-LISTEN-QUE-MIN attribute has been added under TCP-LISTEN-QUE-MIN int on page 5-28.
About This Manual This manual describes how to configure and manage the Parallel Library TCP/IP subsystem. Who Should Use This Manual System and network managers, operators, and others who configure and manage the Parallel Library TCP/IP subsystem should use this manual. How to Use This Manual Use this manual to configure Parallel Library TCP/IP on your system in conjunction with the TCP/IP (Parallel Library) Migration Guide.
Required Background About This Manual Table i. Summary of Contents (page 2 of 2) Section Title This section... A SCF Command Summary provides a quick reference of the syntax for all the SCF commands documented in Section 5. B SCF Error Messages describes the SCF errors returned by the Parallel Library TCP/IP subsystem including recovery procedures. C Tracer Utility describes a utility that displays the path taken by IP packets enroute to a network host.
Adapter Manuals About This Manual Figure i. Parallel Library TCP/IP Core Manuals TCP/IP (Parallel Library) Configuration and Management Manual LAN Configuration and Management Manual TCP/IP (Parallel Library) Migration Guide Operator Messages Manual VST0001.
Parallel Library TCP/IP Application Programming Manuals About This Manual Parallel Library TCP/IP Application Programming Manuals In addition to the core manuals for Parallel Library TCP/IP shown above, there are several programming manuals that affect applications that interface to TCP/IP. These manuals are shown in Figure ii. Figure ii.
About This Manual • Background Manuals and Prerequisite Materials The Expand Configuration and Management Manual describes how to plan, configure, and manage the Expand subsystem on a NonStop S-series server. Use this manual for configuring Expand-over-IP lines. Background Manuals and Prerequisite Materials This subsection lists reference material that you can use to acquire the background required for managing TCP/IP on NonStop servers.
About This Manual NonStop S-Series System Configuration Manuals The following manuals provide background material that is helpful for fully using Parallel Library TCP/IP: • • • • • • • The Telserv Manual describes the TELSERV SCF interface. This guide is intended for configuration and support planners who are responsible for the operation of the TELSERV subsystem. This guide also provides information about the TN6530 terminal emulation utility.
About This Manual Notation Conventions system operations procedures. This guide is intended for experienced HP customers who want to quickly install, configure, and operate their initial NonStop S-series server as a stand-alone server or as a development node within an existing Expand/IP network. 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.
About This Manual General Syntax Notation 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.
Notation for Messages About This Manual 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 ]...
About This Manual Abbreviations 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: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
1 Configuration Quick Start This section provides concise examples of setting up the Parallel Library TCP/IP environment. If you prefer to read introductory information before configuring this subsystem, see Section 2, Introduction. In addition, before starting Parallel Library TCP/IP for the first time, see the TCP/IP (Parallel Library) Migration Guide for any considerations that affect your configuration.
Configuration Quick Start Key Differences Between Parallel Library TCP/IP and Conventional (HP NonStop) TCP/IP Key Differences Between Parallel Library TCP/IP and Conventional (HP NonStop) TCP/IP Parallel Library TCP/IP presents a new architectural paradigm that requires some relearning for users who are familiar with the NonStop TCP/IP product. The later sections of this manual as well as the TCP/IP (Parallel Library) Migration Guide explain these differences in detail.
Configuration Quick Start Starting Parallel Library TCP/IP With TELNET and LISTNER Using a HOSTS File Starting Parallel Library TCP/IP With TELNET and LISTNER Using a HOSTS File Use this procedure to start Parallel Library TCP/IP if you are starting it for the first time (or have cleared the system configuration database, see Stopping Parallel Library TCP/IP and Clearing the Database on page 1-24) and want to configure a HOSTS file. Note.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP With HOSTS c. Check that TCPMAN is not already running on the system. Enter the following command at the SCF prompt: ->LISTDEV PTCPIP $ZZTCP should not appear in the list of processes. If $ZZTCP does appear, you cannot start Parallel Library TCP/IP because Parallel Library TCP/IP is already running. If you want to make changes to the configuration, see Section 5, SCF Reference for Parallel Library TCP/IP. d.
Tasks: Starting Parallel Library TCP/IP With HOSTS Configuration Quick Start Configuration Form 1 Use the form in Table 1-3 to help collect the variables needed to start Parallel Library TCP/IP. This form lists the source of the variable including instructions, where appropriate, for obtaining it. The Line # column allows you to easily crossreference the variables in Example 1-1 on page 1-8 to the form in Table 1-3. Table 1-3.
Tasks: Starting Parallel Library TCP/IP With HOSTS Configuration Quick Start Table 1-3. Configuration Form 1 for HOSTS File Startup (page 2 of 2) Line # Variable Name/ Note Source Step or Example 1-1 Uses... 10. TCPSAM Name Arbitrary; you assign. $ZSAM1 11. LISTNER Name Arbitrary; you assign. $LSN1 12. TELSERV Name Arbitrary; you assign. $ZTN1 4. Save the system configuration database by entering the following SCF command.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP With HOSTS Note. If you receive an error saying that one or more of the LISTNER or TELSERV process file names is already in use, use the procedures for Stopping Parallel Library TCP/IP and Clearing the Database on page 1-24 to clear out Parallel Library TCP/IP environment, then use the TACL STOP command to stop the LISTNER and TELSERV processes that caused the error.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP With HOSTS Example 1-1. TCPIPUP Command File Using HOSTS file ==Clear the system of any DEFINEs and PARAMs DELETE DEFINE =_SRL_01 DELETE DEFINE =TCPIP^PROCESS^NAME CLEAR ALL ==Start the TCPMAN process TCPMAN/NAME $ZZTCP, TERM $ZHOME, OUT $ZHOME, CPU 0,NOWAIT/1 ==SCF commands SCF/INLINE/ INLPREFIX + ==Start TCPMON objects in all processors, establish the host ==name and host ID, and set up loopback.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP With HOSTS 7. Ensure that you are in the volume/subvolume that contains the SRL. a. First find out what the current SYSnn is: >STATUS 0,0 The STATUS command displays your subvolume information similarly to the sample display shown in Figure 1-1: Figure 1-1. TACL STATUS Display VST123.vsd In the display shown in Figure 1-1, the Program file column shows $SYSTEM.SYS00.OSIMAGE.
Configuration Quick Start Starting Parallel Library TCP/IP With TELNET and LISTNER Using DNS 10. Test that the Parallel Library TCP/IP subsystem is running on the desired IP address by issuing the following commands at the TACL prompt. You can use the INFO SUBNET Command for TCPMAN to get the IP address for use in the following command sequence: >TELNET ip-address >TACL >LOGON SUPER.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP With DNS b. Check that QIOMON is running. Enter the following command at the SCF prompt: ->STATUS MON $ZM* You should see a $ZMnn process running in every processor in which you plan to run Parallel Library TCP/IP. If you do not, refer to the QIO Configuration and Management Manual. c. Check that TCPMAN is not already running on the system.
Tasks: Starting Parallel Library TCP/IP With DNS Configuration Quick Start h. Ensure that the TCPMAN process has not been added as a generic process to the system configuration database by entering the following command at the SCF prompt: ->STATUS PROCESS $ZZKRN.#ZZTCP i. Ensure that DNS is configured properly and running on your system by checking with your DNS administrator. 3. Fill in Configuration Form 2.
Tasks: Starting Parallel Library TCP/IP With DNS Configuration Quick Start Table 1-4. Configuration Form 2 for HOSTS File Startup (page 2 of 2) Line # Variable Name/ Note Source Step or Example 1-2 Uses... 7. Route Name Arbitrary; you assign. ROUTE2 8. Gateway/router address Must be an IP address associated with a router on your network subnet (obtain from your network administrator.) 150.20.30.2 9. Location of TCPIPUP Get the location of your TACL command file from Step 5 on page 1-13.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP With DNS Example 1-2.
Configuration Quick Start Starting TCPMAN Using the RUN Command 7. Get the location of your TACL command file from Line 9 of Configuration Form 2 on page 1-12 and substitute this value for the variable location GUEST.USER in the following example command. Issue the following TACL OBEY command on the TCPIPUP command file while running as user SUPER.SUPER: >OBEY $GUEST.USER.TCPIPUP Note.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP Using RUN Command Task 5: Issue the TACL RUN command to start Parallel Library TCP/IP. Task 6: Start TCPSAM for socket programs. Task 7: Test the Parallel Library TCP/IP environment. Tasks: Starting Parallel Library TCP/IP Using RUN Command 1. Check for considerations that affect your configuration. See the TCP/IP (Parallel Library) Migration Guide. 2. Check that the following assumptions are met. a.
Configuration Quick Start Tasks: Starting Parallel Library TCP/IP Using RUN Command 3. Clear the system of DEFINEs and PARAMs by exiting SCF and entering the following commands at the TACL prompt: > > > > DELETE DEFINE =_SRL_01 DELETE DEFINE =TCPIP^PROCESS^NAME DELETE DEFINE =TCPIP^HOST^FILE CLEAR ALL 4. (Skip this step if you are using DNS.) If you are not using DNS for address resolution, set up the environment to use a HOSTS file by adding the following DEFINE to $SYSTEM.SYSTEM.
Configuration Quick Start Starting Parallel Library TCP/IP Using the Persistence Manager 7. Test the Parallel Library TCP/IP environment. You can use the INFO SUBNET Command for TCPMAN to get the IP address for use in the following command sequence: >TELNET ip-address >TACL >LOGON SUPER.SUPER Starting Parallel Library TCP/IP Using the Persistence Manager Use this procedure to start Parallel Library TCP/IP if TCPMAN has been added to the system configuration database as a persistent generic process.
Configuration Quick Start Stopping Parallel Library TCP/IP and Preserving the Current Configuration 3. Add a TCPSAM process by entering the following TACL command (replace the variables, indicated in italics, with real values): >ADD DEFINE =_SRL_01, CLASS MAP, FILE $SYSTEM.SYS03.
Configuration Quick Start Tasks: Stopping Parallel Library TCP/IP and Preserving the Database The above sample display shows that there are four TCPMONs running (shown in the Program column) named $ZPTM1, $ZPTM3, $ZPTM2, and $ZPTM0. Also, one TCPMAN process ($ZZTCP) is running. 2. Perform this step if you are not using TSM. Ensure that you do not stop the TCP/IP process that is running your home terminal. a.
Tasks: Stopping Parallel Library TCP/IP and Preserving the Database Configuration Quick Start The following sample display results from the LISTOPENS PROCESS command and shows all the processes depending on $ZTCO: TCPIP Listopens PROCESS \HOME.
Tasks: Stopping Parallel Library TCP/IP and Preserving the Database Configuration Quick Start The following sample display results from the LISTOPENS MON command and shows all the processes depending on the Parallel Library TCP/IP subsystem: -> listopens mon $zztcp.* PTCPIP Listopens MON \HOME.$ZZTCP.
Configuration Quick Start Tasks: Stopping Parallel Library TCP/IP and Preserving the Database 5. Create a TACL command file as shown in Example 1-3. Replace the italicized variables with the names of the applications and the TCPSAM processes you noted in the above steps. Enter the following command at the TACL prompt: >TEDIT TCPIPDN Example 1-3. TCPIPDN Command File ==Stop the opener processes. See Note on page 1-26.
Configuration Quick Start Stopping Parallel Library TCP/IP and Clearing the Database Stopping Parallel Library TCP/IP and Clearing the Database Follow this shut-down procedure when you want to stop the Parallel Library TCP/IP environment and later restart it using a new configuration. Note that you must stop the Parallel Library TCP/IP from a conventional TCP/IP environment in your system. Task Summary Use TSM to perform these tasks.
Configuration Quick Start Tasks: Stopping Parallel Library TCP/IP and Clearing the Database The above sample display shows that there are four TCPMONs running (shown in the Program column) named $ZPTM1, $ZPTM3, $ZPTM2, and $ZPTM0. Also, one TCPMAN process ($ZZTCP) is running. 2. Perform this step if you are not using TSM. Ensure that you do not stop the TCP/IP environment that is running your home terminal. a.
Tasks: Stopping Parallel Library TCP/IP and Clearing the Database Configuration Quick Start The following sample display results from the LISTOPENS PROCESS command and shows all the processes depending on $ZTC0: TCPIP Listopens PROCESS \HOME.
Tasks: Stopping Parallel Library TCP/IP and Clearing the Database Configuration Quick Start The following sample display results from the LISTOPENS MON command and shows all the processes depending on the Parallel Library TCP/IP subsystem: -> listopens mon $zztcp.* PTCPIP Listopens MON \HOME.$ZZTCP.
Configuration Quick Start Tasks: Stopping Parallel Library TCP/IP and Clearing the Database 5. Obtain the names of the subnets running in the Parallel Library TCP/IP environment by entering the following SCF command (ignore LOOP0): ->INFO SUBNET $ZZTCP.* Since you cannot delete the LOOPBACK subnet, Example 1-4 uses the DELETE SUBNET SN* command instead of DELETE SUBNET * to avoid receiving an error.
Stopping Parallel Library TCP/IP as a Generic Process Configuration Quick Start Stopping Parallel Library TCP/IP as a Generic Process Use this procedure to stop Parallel Library TCP/IP when TCPMAN has been added as a generic process to the system configuration database. Note that you must stop the Parallel Library TCP/IP from a conventional TCP/IP environment in your system. Task Summary Task 1: Check that there is a Parallel Library TCP/IP environment on your system.
Configuration Quick Start Tasks: Stopping Parallel Library TCP/IP as a Generic Process 3. Ensure that you do not stop the TCP/IP environment that is running your home terminal. a. Enter WHO at the TACL prompt: >WHO The following sample display results from the TACL WHO command: \HOME.$SYSTEM.SYSTEM 2> who Home terminal: $ZTNP1.#PTYPRAB TACL process: \HOME.$Z34A Primary CPU: 2 (NSR-G) Default Segment File: $SYSTEM.
Tasks: Stopping Parallel Library TCP/IP as a Generic Process Configuration Quick Start The following sample display results from the LISTOPENS PROCESS command and shows all the processes depending on $ZTC0: TCPIP Listopens PROCESS \HOME.
Tasks: Stopping Parallel Library TCP/IP as a Generic Process Configuration Quick Start -> listopens mon $zztcp.* PTCPIP Listopens MON \HOME.$ZZTCP.#ZPTM0 Openers $ZLIS3 $ZLIS3 $ZLIS3 $ZTEL3 PPID 0,295 0,295 0,295 0,277 BPID PLFN 5 6 7 3 BLFN 0 0 0 0 Protocol TCP TCP TCP TCP Lport echo finger ftp telnet In the above sample display, you would record all the opener processes: $ZPT0, $ZTN0, $ZTF0, $Z0KW, $Z0KX, $ZTN0, and $Z07S to be stopped in Step 6. 5.
2 Introduction This section describes the purpose of Parallel Library TCP/IP, its architecture, benefits, components, features, and relationship to other HP products, and gives some how-to information such as locating the name of a socket access method (TCPSAM) and configuring the subsystem for round-robin distribution of incoming connection requests. Parallel Library TCP/IP is a new HP product that provides increased performance and scalability.
Single IP Host Introduction request latency. In addition, more requests per second can be serviced using the same processor cost, resulting in higher throughput. Single IP Host In conventional TCP/IP, if you ran multiple process instances of a listening application in multiple processors (to increase computing power), you needed a different TCP/IP process (one per listening application process instance) in each processor.
Single IP Host Introduction Figure 2-1 on page 2-2 shows multiple instances of a Web application scaled to handle heavy traffic by running in all 16 processors. This configuration requires a different IP host for each of those Web applications. Figure 2-2 also shows multiple instances of a Web application scaled to handle heavy traffic by running in all 16 processors. However, in the Parallel Library TCP/IP environment shown in Figure 2-2, only one IP host is required for all those application instances.
Introduction Round-Robin Filtering robin feature, however, you must explicitly configure it; the default configuration is for non-round-robin. (See Round-Robin Filtering.) Subnet-Level Binding: How to Isolate Subnets in a Single-IP Environment When you configure the SUBNET object in both conventional TCP/IP and Parallel Library TCP/IP, you specify a subnet IP address which associates the subnet with a particular physical interface (PIF). (See ADD SUBNET Command for TCPMAN on page 5-21.
Introduction Round-Robin Filtering Configuring the System to use Round-Robin Filtering You must set the following DEFINE to enable round-robin filtering on your server processes: ADD DEFINE =PTCPIP^FILTER^KEY, class map, file file-name file-name is arbitrary but serves as the key or password. This key provides a measure of security: only users who know the key can access round-robin on the port. It can be up to eight alphanumeric characters; the first character must be a letter.
Introduction Scalability UDP Port Considerations If a process maintains a context for its messages, the process should not use roundrobin filtering on shared UDP ports. The processes sharing the UDP port should not maintain a context for previous messages because a sequence of messages might not be delivered to the same socket if the port is shared. In fact, with round-robin enabled, a sequence of messages is distributed to each of the port-sharing sockets, in turn.
Introduction Ethernet Failover Ethernet Failover Ethernet failover, available with the G06.10 RVU of Parallel Library TCP/IP, provides fault tolerance at the adapter level. With Ethernet failover, you can configure your network to continue running if an adapter fails or during maintenance and replacement of an adapter. Ethernet failover allows TCP and UDP sessions to continue operating if there are cabling or adapter failures.
Introduction Ethernet Failover A shared IP failover pair also requires that a second IP address, referred to as the reserved IP address, be configured on each SUBNET in the pair. This address must be unique in the network and must reside on the same network subnet as the shared IP address. Parallel Library TCP/IP uses the reserved IP address when issuing Address Resolution Protocol (ARP) requests to resolve the media access control (MAC) address to an IP address.
Introduction Architectural Overview selected by the application. In this case, static routes need to be added to both subnets of the pair if both LIFs are to participate. • • • • Ethernet failover may not function when directly connected to a firewall that uses Ethernet address (MAC) to IP address filtering. This problem can be overcome by adding a router between the LIFs and the firewall. When configuring multiple shared-IP failover pairs, the reserved IP address cannot be shared between pairs.
TCPMAN Introduction Figure 2-3. Data Path Comparison: Conventional vs. Parallel Library TCP/IP Conventional TCP/IP Parallel Library TCP/IP Application Inbound/Outbound Packets G06 TCP/IP Process Inbound/Outbound Packets TCPMON Inbound Packets Application TCPLIB Outbound Packets LAN Drivers/Interrupt Handlers SLSA DIH Legend Message system inter-process transfer Data transfer within the library VST0203.
Introduction TCPMON TCPMON The monitor object (TCPMON) provides the Parallel Library TCP/IP environment in each processor; one TCPMON exists in each configured processor. TCPMONs are controlled by the TCPMAN process. TCPMONs are named automatically. The naming convention for TCPMON is $ZZTCP.#ZPTMn where n is the processor number in which the TCPMON resides. The format for this processor number is hexadecimal (0-F). The TCPMON object has a MASTER attribute.
Introduction PTrace TCP/IP library, TCP/IP retains the context of the application while processing the request. Caution. Parallel Library TCP/IP uses a private shared runtime library (SRL). If you run programs that use private SRLs and you are running Parallel Library TCP/IP, do not create private SRLs that overlap the following memory segments: 0x75800000 through 0X759FFFFF and 0x7FE00000 through 0x7FE1FFFF. In addition, QIO reserves 0x20000000 through 0x41FFFFFF.
Introduction QIO Library TCP/IP subsystem and its relationship to the QIO and SLSA subsystems. The LAN drivers/interrupt handlers and the LAN adapters (for example, G4SA) are part of the SLSA subsystem. The Parallel Library TCP/IP subsystem components and part of the application run in the QIO shared memory segment. QIO The QIO subsystem has been enhanced as of G06.17 to allow you to have more control over certain aspects of memory management.
QIO Introduction Figure 2-4. Parallel Library TCP/IP Subsystem Within the System SCF Commands and Responses DSM Management Applications SCF SPI-formatted messages SCP Open and Close Requests TCPMON QIO Shared Memory Segment TCPLIB TCPMAN Application TCPSAM Outbound Packets Inbound Packets LAN Drivers/Interrupt Handlers SLSA/DIH ServerNet Fabrics LAN LAN LAN Adapter Adapter Adapter SWAN Concentrator X.
Introduction Parallel Library TCP/IP and Other Products The application, TCPMON, and TCPMAN communicate with each other through the TCP/IP library and transfer data within the library without message-system hops. See TCPMAN, TCPMON, and TCPSAM on page 2-11 for descriptions of these components of the Parallel Library TCP/IP subsystem. Parallel Library TCP/IP and Other Products Parallel Library TCP/IP allows transparent interactions with existing products.
Programming With the New Socket Provider (TCPSAM) Introduction Programming With the New Socket Provider (TCPSAM) Applications rely on the transport provider for making socket requests. With the choice of two different environments, the application programmer can now specify either the conventional TCP/IP or the Parallel Library TCP/IP environment just by choosing the appropriate transport-service provider.
3 Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments This section shows you how to configure your listening applications to take advantage of the architectural features of Parallel Library TCP/IP. The first part of this section describes different listening-application models and how those models can be configured to take advantage of Parallel Library TCP/IP. The second part provides configuration examples for each of the listener-application models.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Four Listening Methods Four Listening Methods Networking methods fall into four types: • • • • Standard Listening Model Monolithic Listening Model Distributor Listening Model Hybrid Listener Model Standard Listening Model In this method, you have a single process which listens for incoming connections.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Standard Listening Model Figure 3-1. Standard Listening Model Parallel Library TCP/IP Conventional TCP/IP 1. 1. Connection Req 1 LAN Adapter Processor 0 Connection Req 1 LAN Adapter LISTNER TCP/IP Processor 0 LISTNER TCP/IP Library 2. 2.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Monolithic Listening Model Monolithic Listening Model In this method, the listener binds to a well-known port, (for example port 23 for TELSERV). Next, the listening process issues a standard accept call. Finally, the monolithic listening model then uses multi-threading to handle all connections within the same process creating sockets for the connections.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Monolithic Listening Model Figure 3-2. Monolithic: Listening Model Conventional TCP/IP IPC hop Processor 0 TCP/IP Process Processor 1 Monolithic Server Sockets Port xxxx (Exclusive) LAN Adapter Parallel Library TCP/IP Sockets Monolithic Server Monolithic Server Monolithic Server TCP/IP Library Port xxxx (Shared) TCP/IP Library Port xxxx (Shared) TCP/IP Library Port xxxx (Shared) TCP/IP Library LAN Adapter VST0302.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Distributor Listening Model hop required in the conventional TCP/IP environment and also because TCP/IP often runs in a different processor than the listening process for load distribution. In the Parallel Library TCP/IP environment, with round-robin filtering enabled, you can have multiple copies of the monolithic listener running in different processors, all sharing the same port (shown in Figure 3-2 on page 3-5).
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Distributor Listening Model PATHSEND allows load-balancing algorithms to distribute the data to the back-end server instances. The distributor model achieves some parallelism and load-balancing because of the use of the multiple, back-end server instances. However, the distributor model is limited by the fact that all data must flow through the distributor to the back-end server processes through PATHSEND.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Distributor Listening Model Figure 3-3.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Hybrid Listener Model of connection requests performed by the adapter and the presentation of one IP host. Figure 3-4.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Hybrid Listener Model Figure 3-5 shows the hybrid listener model in conventional TCP/IP. The figure shows two distributors in processors 0 and 2 distributing connections and data and control flow to servers in their own and in one other processor. The servers inherit the connections and send data flow to the TCP/IP process. Note that each TCP/IP process represents a different IP host.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Standard Listening Model hop between the remote processors (1 and 3) is eliminated as data flows directly to the local TCP/IP library and then out to the adapter. Figure 3-6.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Standard Listening Model processes and hands off the connection to those processes. The FTPSERV processes then assume direct control of the connections. Figure 3-7. Standard Listening Model Configuration Example: LISTNER NonStop S-Series System With 4 Processors 1. Processor 0 LAN Adapter LISTNER A connection request comes in to the LISTNER 4. 150.50.130.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Standard Listening Model Startup Files You must start the Parallel Library TCP/IP environment and create a TCPSAM process before running TCPIPUP2. The command file TCPIPUP1 performs these tasks. The TCPIPUP1 File The following TACL command file starts the Parallel Library TCP/IP environment including the TCPMAN process, the monitors, and the TCPSAM process.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Standard Listening Model The TCPIPUP2 File The following TACL command file starts the processes, adds and starts subsystem objects through SCF, and sets appropriate parameters. To add comments, use the word “comment” or a double equal sign (==). Some lines are discussed separately after the example. Substitute real values for variables (indicated in italics).
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Monolithic Listening Model The SCFSBNT File The SCFSBNT file adds and starts subnets and routes. Substitute real values for variables (indicated in italics). (See the Configuration Form 1 on page 1-5 and 1-12 for procedures for determining these values.) Example 3-3.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Monolithic Listening Model Figure 3-8 shows the round-robin feature in this configuration. A TELSERV process is configured in each processor, the processes bound to the same port, and round-robin filtering enabled on those processes. (See Round-Robin Filtering on page 2-4.) Figure 3-8.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Monolithic Listening Model The TCPIPUP3 File The following TACL command file starts the processes, adds and starts subsystem objects through SCF, and sets appropriate parameters. To add comments, use the word “comment” or a double equal sign (==). Some lines are discussed separately after the example. Example 3-4.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Distributor Listening Model start TELSERV primary and backup processes in every other processor. Note that the backup TELSERV processes do not share any processors with other TELSERV processes. Running TELSERV processes in distinct processor pairs avoids potential port sharing conflicts in a failure situation. (See Port Collision Considerations for Listening Processes on page 2-5.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Distributor Listening Model Figure 3-9.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Distributor Listening Model The TCPIPUP4 File The following TACL command file starts the processes, adds and starts subsystem objects through SCF, and sets appropriate parameters. To add comments, use the word “comment” or a double equal sign (==). Some lines are discussed separately after the example. Example 3-5.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Hybrid Listening Model Configuration Example for the Hybrid Listening Model This example demonstrates the hybrid listener model discussed above (see Hybrid Listener Model on page 3-9) using iTP WebServer configured with round-robin filtering enabled. This configuration has four processors each running their own distributors.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Configuration Example for the Hybrid Listening Model The TCPIPUP5 File The following TACL command file starts the processes, adds and starts subsystem objects through SCF, and sets appropriate parameters. To add comments, use the word “comment” or a double equal sign (==). Some lines are discussed separately after the example. Example 3-6.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Example for Two Gateways — Standard Listening Model Example for Two Gateways — Standard Listening Model This example demonstrates the standard listener model discussed above (see Standard Listening Model on page 3-2). This example shows an environment that has two gateways leading to two subnets on a NonStop S-series server (host).
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Example for Two Gateways — Standard Listening Model Figure 3-11. Two Gateways With LISTNER Routers GTWY1 Host 150.50.130.1 150.50.130.2 LAN Adapter 150.50.130.4 GTWY2 LISTNER Processor 1 150.60.64.1 TCPLIB 128.30.128.2 Processor 0 TCPLIB 128.30.128.1 150.60.64.2 LAN Adapter 150.60.64.3 FTPSERV Backup LISTNER TCPLIB Processor 2 150.60.64.4 FTPSERV 150.60.64.5 TCPLIB Processor 3 FTPSERV VST0311.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Example for Two Gateways — Standard Listening Model The TCPIPUP6 File The following TACL command file starts the processes, adds and starts subsystem objects through SCF, and sets appropriate parameters. To add comments, use the word “comment” or a double equal sign (==). Some lines are discussed separately after the example. Example 3-7.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Example for Two Gateways — Standard Listening Model The SCFSBNT2 File The SCFSBNT2 file adds and starts subnets and routes. Example 3-8. SCFSBNT2 File for TCPIPUP6 === SCFSBNT2 ===== SCFSBNT2 ==== SCFSBNT2 ======== == SCF command file to ADD and START SUBNETs Example 3-7 ALLOW ALL ERRORS ALLOW ALL WARNINGS == ASSUME PROCESS $ZZTCP == Add subnets ADD SUBNET SN0,TYPE ETHERNET,DEVICENAME LAN01,IPADDRESS 150.50.130.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Example for Two Gateways — Standard Listening Model LOOPBACK When the monitors are started, a subnet named LOOP0 is added automatically. This subnet provides loopback capability without requiring the use of the TCP/IP network. When this LOOP0 subnet is created, it has an address of 0.0.0.0 in dotted decimal form. You must change this address; use the command: ALTER SUBNET LOOP0, IPADDRESS 127.1 The address 127.1 (or 127.0.0.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Example for Two Gateways — Standard Listening Model The HOSTS File The HOSTS file is the file used in the absence of a Domain Name Server for resolving the common names of hosts into their corresponding IP addresses. (The HOSTS file shown is customized for this example.) Example 3-9. HOSTS File for TCPIPUP6 ########## HOSTS FOR HOST ########## HOSTS FOR HOST ############ # Filename = \CB1.$SYSTEM.ZTCPIP.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Parallel Library TCP/IP for Complex, Heavy-Use WAN Environments Parallel Library TCP/IP for Complex, HeavyUse WAN Environments Parallel Library TCP/IP provides improved scalability for the SWAN subsystem.
Configuring Parallel Library TCP/IP for Complex and Heavy-Use Environments Parallel Library TCP/IP for Complex, Heavy-Use WAN Environments HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual— 522271-006 3- 30
4 Managing the Parallel Library TCP/IP Subsystem This section describes the following aspects of managing the Parallel Library TCP/IP subsystem: • • • • • • Running Applications in Both Environments on page 4-1 Managing the System Configuration Database on page 4-1 Managing Performance on page 4-7 Strategy for Coexistence with Conventional TCP/IP on page 4-7 Falling Back to Conventional TCP/IP on page 4-7 Dynamically Loading SPRs on page 4-8 There are some new system management tasks for Parallel Library
Managing the Parallel Library TCP/IP Subsystem Configuration Database Management stores your subsystem configuration and can be accessed at any time to restore the subsystem to its last configuration. However, the TCPSAM process is not stored in the system configuration database so you must always start TCPSAM processes by using the TACL RUN command. Note. No dynamically created entries or routes are recorded in the system configuration database.
Managing the Parallel Library TCP/IP Subsystem Managing Persistence Managing Persistence You can add a generic process to the system configuration database and define that generic process in such a way that the persistence manager ($ZPM) will restart the generic process whenever the generic process abends, is stopped through TACL, or the system is reloaded. To define the generic process, set the STARTMODE to SYSTEM.
Managing the Parallel Library TCP/IP Subsystem How to Manage TCPSAM-Dependent Applications 2. Change your session location to the subvolume of $SYSTEM.SYSnn by entering the following command (see also Locating the SRL on page 2-12): >VOLUME $SYSTEM.SYSnn 3. Enter the following command to tell the TCPSAM process the location of the Parallel Library TCP/IP private SRL: >ADD DEFINE =_SRL_01, CLASS MAP, FILE ZTCPSRL 4.
Managing the Parallel Library TCP/IP Subsystem How to Add TCPMAN as a Generic Process to the System Configuration Database How to Add TCPMAN as a Generic Process to the System Configuration Database Note. You can start the TCPMAN process from a RUN command rather than through the persistence manager and TCPMAN will restore the configuration of the subordinate objects from the system configuration database.
Managing the Parallel Library TCP/IP Subsystem How to Add TCPMAN as a Generic Process to the System Configuration Database The ABORT PROCESS command to $ZZKRN.#ZZTCP stops $ZZTCP and causes the persistence manager not to restart it until a system reload. To restart TCPMAN, issue the following SCF command: ->START PROCESS $ZZKRN.
Managing the Parallel Library TCP/IP Subsystem Managing Performance To manually restart all the TCPMAN subordinate objects, issue the following commands: ->START MON * ->DELAY 21 Remember to start your TCPSAM processes since they will not be started by TCPMON or TCPMAN. Managing Performance When using Parallel Library TCP/IP, processor utilization measurements of client applications may tend to exhibit higher numbers because the TCP/IP processing is now done in the context of the application.
Managing the Parallel Library TCP/IP Subsystem Dynamically Loading SPRs a. Determine the name of your preferred transport service provider name. Use either $ZTC0, (if that is the name of the default conventional TCP/IP process), or use the LISTDEV command to obtain a list of running TCP/IP processes: ->LISTDEV TCPIP b.
5 SCF Reference for Parallel Library TCP/IP This section provides information about: • • • The Subsystem Control Facility (SCF) SCF commands available for PTCPIP (to find a command quickly, see Table 5-4 on page 5-9.) The PTrace facility SCF for Parallel Library TCP/IP SCF provides an operator interface to an intermediate process, the Subsystem Control Point (SCP), which in turn provides the interface to the I/O processes of the various subsystems.
SCF Reference for Parallel Library TCP/IP Object Types get information about these objects on all configured processors, use the SCF commands for the TCPMAN process instead. Object Types You can monitor and control the Parallel Library TCP/IP subsystem by issuing commands that act on one or more Parallel Library TCP/IP subsystem objects. Each object has an object type and an object name. The object type describes the type of object. The object name uniquely identifies the object within the system.
ENTRY Object Type SCF Reference for Parallel Library TCP/IP Figure 5-1. TCPMAN Process Object Hierarchy $PROCESS #MONITOR SUBNET ROUTE ENTRY VST00501.vsd Figure 5-2 shows the object hierarchy for the TCPSAM process. Figure 5-2. TCPSAM Process Object Hierarchy $PROCESS #SUBNET #ROUTE VST0502.vsd Note that there is a pound sign (#) in front of the SUBNET and ROUTE objects for TCPSAM and there is no intermediate monitor (TCPMON) object.
SCF Reference for Parallel Library TCP/IP MONITOR Object Type MONITOR Object Type The MONITOR object (TCPMON) provides the Parallel Library TCP/IP environment in a processor. Only one TCPMON can exist in each configured processor. TCPMON has the reserved name of $ZPTMn where n is the processor number (hexadecimal) where TCPMON resides. Note. In the Parallel Library TCP/IP subsystem, a TCPMON can have more than one IP address associated with it (one per subnet).
ROUTE Object Type SCF Reference for Parallel Library TCP/IP names of the processes associated with each environment. The LISTDEV command displays all the TCP/IP processes running on the system. The last field in the display is Program. A program name of TCPSAM indicates a Parallel Library TCP/IP process while a program name of TCPIP indicates a conventional TCP/IP process. To obtain a list of all running PTCPIP processes, enter the SCF LISTDEV PTCPIP command.
SCF Reference for Parallel Library TCP/IP SUBNET Object Type The SUBNET object is also subordinate to the TCPMON object. A subnet is accessible to all TCPMONs in the system. You can view a subnet from a system-wide view or from a TCPMON/processor view. The fully-qualified subnet name includes the process name, a period, the TCPMON name, a period, and the subnet name. A STATUS on the $ZZTCP.#TCPMONname.subnet-name shows you the subnet status in one processor (the one where the specified TCPMON is running).
Naming Convention Summary SCF Reference for Parallel Library TCP/IP Naming Convention Summary Table 5-2 summarizes the reserved names for each object type and the naming convention rules. Table 5-2. Object Naming Convention Summary and Reserved Names Starting Symbol (Required) First Character Requirement First Character Recommendation Character Limit Letter EA 7 Object Type Reserve d Names ENTRY None MON #ZPTMx # Letter MON names are assigned automatically.
Summary States SCF Reference for Parallel Library TCP/IP SCF> DELETE SUBNET $ZZTCP.*.SN* The following example deletes all routes subordinate to $ZZTCP that start with R and end with 5: SCF> DELETE ROUTE $ZZTCP.*.R*5 ? Use the question mark to represent a single unknown character in a specific position. For example, $ZZTCP.*.S?1 selects all object names subordinate to $ZZTCP that begin with S, end with 1, and contain exactly one character between the S and the 1.
Parallel Library TCP/IP SCF Commands SCF Reference for Parallel Library TCP/IP • In the STARTING summary state, the object has been initialized and is attempting to start. Parallel Library TCP/IP SCF Commands This subsection contains the following information: • • • A table describing the Subsystem Control Facility (SCF) commands supported by the Parallel Library TCP/IP subsystem and the object types supported for each command. Detailed information on object specification syntax.
Supported Commands and Object Types SCF Reference for Parallel Library TCP/IP Table 5-4.
Entering SCF Commands SCF Reference for Parallel Library TCP/IP Table 5-6 lists the sensitive and nonsensitive Parallel Library TCP/IP SCF commands. Table 5-6.
SCF Reference for Parallel Library TCP/IP ABORT Command If additional attribute specifiers are required to define characteristics of the object, the object name is followed by a comma and the attribute name and value, as in the following example: SCF> ALTER MON $ZZTCP.#ZPTM*, DELAYACKS OFF Note. The SEL and SUM options, which apply to several of the SCF commands when used with other communications subsystems, cannot be used with the Parallel Library TCP/IP subsystem.
SCF Reference for Parallel Library TCP/IP ABORT PROCESS Command for TCPMAN TCPMON objects when open sockets exist. This command also deletes the MON object from the system configuration database. Command Syntax ABORT [ / OUT file-spec / ] MON [$ZZTCP.#ZPTMn] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON $ZZTCP.#ZPTM{0-F} is a valid MON name indicating the desired TCPMON. The MON object is always named $ZZTCP.
SCF Reference for Parallel Library TCP/IP ABORT PROCESS Command for TCPSAM command does not stop or delete the process from the system configuration database if the process has been added as a generic process. See Considerations. Command Syntax ABORT [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [ , SUB ALL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $ZZTCP is the name of the TCPMAN process.
SCF Reference for Parallel Library TCP/IP ABORT ROUTE Command for TCPMAN Command Syntax ABORT [ / OUT file-spec / ] [ PROCESS $tcpsam-process-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $tcpsam-process-name is a valid process name indicating the desired TCPSAM process. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
SCF Reference for Parallel Library TCP/IP ABORT SUBNET Command for TCPMAN For example, ABORT ROUTE *.RT1 is equivalent to ABORT ROUTE RT1. If you omit the process name, SCF uses the assumed process name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs. Examples The following commands abort the specified routes in all TCPMONs: SCF> ABORT ROUTE $ZZTCP.*.RT1 SCF> ASSUME PROCESS $ZZTCP SCF> ABORT ROUTE *.
SCF Reference for Parallel Library TCP/IP ADD Command The following commands abort a subnet named SN0: SCF> ASSUME PROCESS $ZZTCP SCF> ABORT SUBNET *.SN0 Considerations • • • • The object-name template (wild-card notation) is supported. All activities being performed by the specified objects are halted. Use the STOP command if you want to stop the operation of objects in a more controlled manner. The STOP command does not abruptly terminate activities in progress.
SCF Reference for Parallel Library TCP/IP ADD ROUTE Command for TCPMAN The naming convention for entries is seven characters. The first two characters must be EA. TYPE ARP specifies the ENTRY type. The only supported type is ARP. A TYPE of ARP maps an IP address with an Ethernet MAC address. The ARP type requires an IP address and the MACADDR attribute. IPADDRESS ip addr specifies the internet address for the entry and is specified in dotted decimal notation.
SCF Reference for Parallel Library TCP/IP ADD ROUTE Command for TCPMAN TCPMONs. You can use the wild-card (*) notation for the TCPMON name, but if you do not, it is assumed anyway. For example, ADD ROUTE *.RT1 is equivalent to ADD ROUTE RT1. Names starting with DA, DD, DR, EA, and RT are reserved. The naming convention for routes is seven characters. The first character must be a letter.
SCF Reference for Parallel Library TCP/IP ADD ROUTE Command for TCPMAN METRIC metric-val indicates the number of hops to the destination. The metric is optional for add commands; it defaults to zero if the destination is on a directly-attached network and the metric is not specified. It is non-zero if the route uses one or more gateways. The default is 1 if the destination is not on a directly-attached network and the metric is not specified.
SCF Reference for Parallel Library TCP/IP ADD SUBNET Command for TCPMAN Considerations Routes can also be created dynamically through internal routing logic. • • • • • • • Routes created by internal route-redirect logic start with DDcpu where cpu is the CPU number in hexadecimal format where the route is generated. Routes created by internal ARP link-level logic start with DAcpu where cpu is the processor number in hexadecimal format where the route is generated.
SCF Reference for Parallel Library TCP/IP ADD SUBNET Command for TCPMAN naming convention for subnets is seven characters. The first character must be a letter. HP recommends making the first two characters SN. TYPE ETHERNET specifies the type of subnet to be added. The only valid type is Ethernet. This parameter is required. Default: None. DEVICENAME lif-name is the name of the device to be opened to connect to the network. This corresponds to the SLSA logical interface (LIF).
SCF Reference for Parallel Library TCP/IP ADD SUBNET Command for TCPMAN FAILOVER {SHAREDIP | NONSHAREDIP} enables the SUBNET to be failover-capable using the following configuration: • • SHAREDIP has the same IP address as the associated SUBNET in the failover configuration. NONSHAREDIP has a different IP address than the associated SUBNET in the failover configuration. Examples The first example adds a subnet named SN1 of type Ethernet to all the TCPMONs in the system.
SCF Reference for Parallel Library TCP/IP • • • • • ADD SUBNET Command for TCPMAN The SLSA subsystem must be operational for the ADD command to complete successfully. Refer to the LAN Configuration and Management Manual for more information. When a subnet is added, a corresponding route to this subnet is added automatically. Both the subnet and the route are placed in the STOPPED state. To initiate the operation of the object, you must start it with the START command.
SCF Reference for Parallel Library TCP/IP ALTER Command ALTER Command The ALTER command changes attribute values associated with the specified PTCPIP object. This is a sensitive command. ALTER MON Command for TCPMAN The ALTER MON command is used to change the attribute values of the Parallel Library TCP/IP subsystem. When you alter attributes of a TCPMON process you must do so on all configured PTCPIP TCPMONs. Hence, only the wild card is supported for the TCPMON object.
SCF Reference for Parallel Library TCP/IP ALTER MON Command for TCPMAN TCPSENDSPACE int specifies the size of the window used for sending data for the TCP protocol. The recommended range for is 512 bytes to 12k bytes. The default value is 8K. TCPRECVSPACE int specifies the size of the window used for receiving data for the TCP protocol. This value affects the performance, as it is mapped to the advertised window. The recommended range is 512 bytes to 12k bytes. The default value is 8K.
SCF Reference for Parallel Library TCP/IP ALTER MON Command for TCPMAN TCPKEEPIDLE int is the amount of time in seconds before TCP issues a keep-alive packet on sockets that have enabled this option. The default is 45 seconds. The range is 1 to 7200. TCPKEEPINTVL int is the time interval in seconds between retransmissions of unacknowledged keepalive packets. The default is 45 seconds. The range is 1 to 1260.
SCF Reference for Parallel Library TCP/IP ALTER MON Command for TCPMAN has correct remote passwords. If the check fails, the SOCKET request is rejected with file error 48. The default for this option is OFF. TCPPATHMTU { ON | OFF } is ON to cause TCP to use PATH MTU discovery on all TCP-type sockets (SOCK_STREAM), unless disabled by the SETSOCKOPT for SO_PMTU. The default is ON. TCPTIMEWAIT int is the amount of time in seconds that a TCP connection remains in the TIME_WAIT state.
SCF Reference for Parallel Library TCP/IP ALTER MON Command for TCPMAN MIN-EPHEMERAL-PORT int is the starting port number to allocate for TCP and UDP ephemeral ports. Ephemeral ports are those assigned by Parallel Library TCP/IP when an application has not bound to a specific port. The default is 1024. The allowable range is 1024 to (MAX-EPHEMERAL-PORT - 16). See Considerations and Examples. Everything below min-ephemeral-port requires super-group privileges.
SCF Reference for Parallel Library TCP/IP ALTER SUBNET Command for TCPMAN ALTER SUBNET Command for TCPMAN The ALTER SUBNET command is used to change the attribute values of a subnet. Command Syntax ALTER [ /OUT file-spec/ ] [SUBNET $ZZTCP.*.subnet-name ] { [ ,IPADDRESS ip-addr ] [ ,SUBNETMASK %H0..FFFFFFFF ] [ ,IRDP { ON | OFF } ] [ ,ADDALIAS ip-addr,SUBNETMASK %H0..
SCF Reference for Parallel Library TCP/IP ALTER SUBNET Command for TCPMAN IRDP enables (ON) or disables (OFF) the ICMP Router Discovery Protocol on the subnet interface. IRDP is a mechanism for locating default routers and is specified in RFC 1256. IRDP must also be enabled on any local LAN routers. If redundant routers are configured with route hold-down times and advertisement intervals of approximately 30 seconds, IRDP can be used to provide a black hole, or dead gateway, detection mechanism.
SCF Reference for Parallel Library TCP/IP ALTER SUBNET Command for TCPMAN The following example links the two failover-enabled subnets, SN1 and SN2, together as an adapter failover pair. The subnets SN1 and SN2 are configured to have different subnet IP address. -> ASSUME PROCESS $ZZTCP -> ADD SUBNET SN1,TYPE ETHERNET, DEVICENAME LANLIF2, & IPADDRESS 172.17.217.232, SUBNETMASK 255.255.255.0, & FAILOVER NONSHAREDIP -> ADD SUBNET SN2,TYPE ETHERNET, DEVICENAME LANLIF3, & IPADDRESS 172.17.217.
SCF Reference for Parallel Library TCP/IP • • • • • DELETE Command No other option parameters are allowed in the ALTER SUBNET command when the ASSOCIATESUB parameter is present. For the two subnets configured as a failover pair, you cannot assign an alias address before the ASSOCIATESUB is done. For the two subnets configured as a failover pair, you cannot alter the subnet IP address or subnetmask once they are configured.
SCF Reference for Parallel Library TCP/IP DELETE ROUTE Command for TCPMAN ENTRY $ZZTCP.*.entry-name is the name of the ENTRY object to be deleted. The fully-qualified entry name is $ZZTCP.*.entry-name (you must alter the subnet on all configured TCPMONs). You can delete all entries by substituting the wild card (*) for the entry-name. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
SCF Reference for Parallel Library TCP/IP DELETE SUBNET Command for TCPMAN Examples The following example deletes the specified route from all TCPMONs. Note that the wild card (#) is assumed for the TCPMON. -> DELETE ROUTE $ZZTCP.*.RT0 The following command is valid because the dynamic route DR1_1 was created in processor 1. -> DELETE ROUTE $ZZTCP.#ZPTM1.DR1_1 Considerations • • • Only link-level routes, generated internally by the ARP logic, can be deleted without being brought to a STOPPED state.
SCF Reference for Parallel Library TCP/IP INFO Command Examples The following command deletes all subnets in the Parallel Library TCP/IP: SCF> DELETE SUBNET $ZZTCP.*.* Considerations • • • • • • • The object-name template (wild-card notation) is supported. When the DELETE operation is completed, the definition of the subnet you specified for deletion is removed from the system configuration database. Before you can delete a subnet, it must be in the STOPPED summary state.
SCF Reference for Parallel Library TCP/IP INFO ENTRY Command for TCPMAN Entry $ZZTCP.#ZPTMn.entry-name is the name of the entry. The fully-qualified entry name is $ZZTCP.#ZPTMn.entry-name. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs. IPADDRESS ip-addr is the IP address of the entry.
INFO MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP INFO ENTRY With OBEYFORM Display Format The format of the display for the INFO ENTRY command with the OBEYFORM attribute specified is: ADD ENTRY EA1 , TYPE ARP,& IPADDRESS 172.17.220.10 ,& MACADDR %H08008E003578 INFO MON Command for TCPMAN The INFO MON command displays the current attribute settings for the PTCPIP subsystem in a given TCPMON or in all configured TCPMONs.
SCF Reference for Parallel Library TCP/IP INFO MON Command for TCPMAN Examples The first command displays the current attribute settings for the TCPMON in processor 0. The second command displays the altered TCPMON attributes in ALTER MON format. -> INFO MON $ZZTCP.#ZPTM0, DETAIL -> INFO MON *, OBEYFORM INFO MON Display Format The format of the display for the INFO MON $ZZTCP.#ZPTM0 , DETAIL command is: TCPMAN Detailed Info MON \OSCAR.$ZPTM0 *TCP Send Space......... *UDP Send Space.........
SCF Reference for Parallel Library TCP/IP INFO MON Command for TCPMAN Delay Ack Time is the amount of time in 10 ms intervals that the acknowledgments are delayed. Delay Ack is a switch indicating if TCP is delaying acknowledgments. Keep Alive Idle is the amount of time in seconds before TCP issues a keep alive packet on sockets that have enabled this option.
SCF Reference for Parallel Library TCP/IP INFO MON Command for TCPMAN ALLNETSARELOCAL is ON to cause TCP to use the interface MTU as a base for the determination of the TCP Maximum Segment Size (MSS) for each non-local TCP connection. A non-local TCP connection is one that goes to another network (not just another subnetwork). The default is ON. If this switch is OFF, TCP conforms to RFCspecified behavior and use 512 bytes as the default MSS for non-local segments.
SCF Reference for Parallel Library TCP/IP INFO MON Command for TCPMAN TCP-INIT-REXMIT-TIMEOUT is the initial retransmit timer value in milliseconds to use on a TCP connection. When the first round-trip timer measurement is made on a TCP connection and the calculation is done to arrive at the retransmission timeout to use on the next packet sent, this value is used unless the calculated value is larger. This variable can be used to help reduce the number of premature retransmission timeouts.
SCF Reference for Parallel Library TCP/IP INFO PROCESS Command for TCPMAN INFO MON With OBEYFORM Display Format The format of the display for INFO MON * , OBEYFORM is: ALTER MON *, & TCPSENDSPACE 9120 ,& UDPSENDSPACE 41600,& RFC1323-ENABLE OFF,& TCP-LISTEN-QUE-MIN 64,& MIN-EPHEMERAL-PORT 1024,& MAX-EPHEMERAL-PORT 65024 INFO PROCESS Command for TCPMAN The INFO PROCESS command displays the current attribute values for the TCPMAN process. The INFO PROCESS display is the same as INFO PROCESS, DETAIL.
SCF Reference for Parallel Library TCP/IP INFO PROCESS Command for TCPSAM INFO PROCESS Display Format The format of the display for the INFO PROCESS command both with and without the DETAIL option is the same: TCPMAN Info Process \SYSTEM.$ZZTCP PPID............ ( 2,289) BPID................... ( 3,271) PROCESS $ZZTCP is the name of the manager process (TCPMAN). If you omit the object name, SCF uses the assumed object name.
SCF Reference for Parallel Library TCP/IP INFO PROCESS Command for TCPSAM Examples The following commands request the non-detailed and the detailed information for the TCPSAM process named $SAM1: -> INFO PROCESS $SAM1 -> INFO PROCESS $SAM1 , DETAIL INFO PROCESS Display Format The format of the display for the INFO PROCESS command without the DETAIL option is (an asterisk (*) an alterable attribute; however, see Considerations on page 5-48): TCPIP Info PROCESS \BOBAFET.
SCF Reference for Parallel Library TCP/IP INFO PROCESS Command for TCPSAM TCP Receive Space is the amount of data (in bytes) that can be buffered in the TCP layer when receiving data from a remote site. UDP Send Space is the amount of data (in bytes) that can be buffered in the UDP layer when sending data to a remote site. UDP Receive Space is the amount of data (in bytes) that can be buffered in the UDP layer when receiving data from a remote site. Delay Ack Time is the amount of time (in .
SCF Reference for Parallel Library TCP/IP INFO PROCESS Command for TCPSAM Program Filename is the name of the file being executed for this process. Debug is the current setting (ON or OFF) of the DEBUG attribute. Debug is used by HP support and development personnel. Full Dump is the current setting (ON or OFF) of the FULLDUMP attribute. All Nets Are Local The default is ON.
SCF Reference for Parallel Library TCP/IP INFO PROCESS Command for TCPSAM Trace Status is ON when the process is being traced using SCF. Trace Filename is the name of the current trace file. RFC1323 Enable is ON to cause TCP to support TCP Large Windows as documented in RFC 1323. When this option is enabled, Parallel Library TCP/IP uses the TCP Window Scale and Timestamp options as described in RFC 1323.
SCF Reference for Parallel Library TCP/IP INFO ROUTE Command for TCPMAN INFO ROUTE Command for TCPMAN The INFO ROUTE command for TCPMAN displays attribute values for the specified route(s). Command Syntax INFO [ / OUT file-spec / ] [ ROUTE $ZZTCP.#ZPTMn.route-name ] [, OBEYFORM ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE route-name is the name of the route.
INFO ROUTE Command for TCPMAN SCF Reference for Parallel Library TCP/IP INFO ROUTE Display Format The following display shows the output of the first example: PTCPIP Info ROUTE \BOBAFET.$ZZTCP.#ZPTM2.* Name Subnet Destination name RT2 EN1 172.17.215.0 RT3 EN2 172.17.215.0 RT4 EN3 172.17.195.0 RT5 DA2_2 DA2_3 MR3 MR4 MR5 DR2_1 DEF RT6 LOOP0 EN1 EN1 EN1 EN1 EN1 EN3 EN1 EN1 127.0.0.1 172.17.215.1 172.17.215.2 155.186.70.0 155.186.70.0 130.186.0.0 0.0.0.0 0.0.0.0 130.186.72.
INFO ROUTE Command for TCPMAN SCF Reference for Parallel Library TCP/IP Netmask is the subnetmask associated with the route entry. Gateway is the machine through which the remote machine or network specified in DESTINATION is to be reached. Type indicates one of the following: blank routes to a network. H host Route G gateway Route C route with cloning capability c route cloned from a Cloning Route. S manually generated route. L route generated by ARP logic (Link level route).
SCF Reference for Parallel Library TCP/IP INFO ROUTE Command for TCPSAM Considerations • • The implicit route generated internally from the ADD SUBNET command has the cloning flag set. See the ADD ROUTE help text for a detailed description of the cloning capability of a route. Link level routes, generated internally by the ARP logic, cannot be stopped externally through the SCF ABORT or STOP ROUTE commands but can be deleted externally through the SCF DELETE ROUTE command.
INFO ROUTE Command for TCPSAM SCF Reference for Parallel Library TCP/IP INFO ROUTE Display Format The display format for INFO ROUTE for TCPSAM is: TCPIP Info ROUTE \BOBAFET.$ZSAM2.* Name Subnetname Destination Gateway Type #RT2 #RT3 #RT4 #RT5 #DA2_2 #DA2_3 #MR3 #MR4 #MR5 #DR2_1 #DEF #RT6 #EN1 #EN2 #EN3 #LOOP0 #EN1 #EN1 #EN1 #EN1 #EN1 #EN3 #EN1 #EN1 172.17.215.0 172.17.215.0 172.17.195.0 127.0.0.1 172.17.215.1 172.17.215.2 155.186.70.0 155.186.70.0 130.186.0.0 0.0.0.0 0.0.0.0 130.186.72.0 172.17.
SCF Reference for Parallel Library TCP/IP INFO ROUTE Command for TCPSAM Gateway is the machine through which the remote machine or network specified in DESTINATION is to be reached. Type indicates one of the following: blank routes to a network. H host Route G gateway Route R route generated by IRDP logic. If ICMP Router Discovery Protocol (IRDP) is enabled on a subnet, default routes discovered by IRDP is indicated as Type Gateway/Router (G, R).
SCF Reference for Parallel Library TCP/IP INFO SUBNET Command for TCPMAN INFO SUBNET Command for TCPMAN The INFO SUBNET command displays the current attribute values for the specified subnets. Command Syntax INFO [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] [, DETAIL | , OBEYFORM] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $ZZTCP.#ZPTMn.subnet-name is the name of the subnet.
INFO SUBNET Command for TCPMAN SCF Reference for Parallel Library TCP/IP INFO SUBNET for TCPMAN Display Format The format of the display for the first example is the following (an asterisk (*) indicates an alterable attribute): PTCPIP Info SUBNET \BEAR.$ZZTCP.#ZPTM1.SN1 Name SN1 Devicename \BEAR.LANLIF2 *IPADDRESS 172.17.217.
SCF Reference for Parallel Library TCP/IP INFO SUBNET Command for TCPMAN TYPE is the subnet type. Possible values are Ethernet and loopback. SUBNETMASK is a 32-bit integer that specifies which portion of the network number and the IP host address is to be masked to define a subnet. QIO shows whether or not the subnet is currently using the QIO interface. QIO is always on for Ethernet type subnets. ON indicates that the interface is currently using QIO mode.
SCF Reference for Parallel Library TCP/IP INFO SUBNET Command for TCPSAM The format of the display for the fourth example, OBEYFORM, is: ALTER SUBNET LOOP0 , IPADDRESS 127.0.0.1 ADD SUBNET EN1 , TYPE ETHERNET,& IPADDRESS 172.17.222.15 , SUBNETMASK %HFFFFFF00 ,& DEVICENAME \SAMCAT.LANLIF1, FAILOVER NONSHAREDIP ALTER SUBNET EN1 , ASSOCIATESUB "EN2" ALTER SUBNET EN1 , ADDALIAS 172.17.222.120 ALTER SUBNET EN1 , ADDALIAS 172.17.222.121 ALTER SUBNET EN1 , ADDALIAS 172.17.222.122 ALTER SUBNET EN1 , ADDALIAS 172.
INFO SUBNET Command for TCPSAM SCF Reference for Parallel Library TCP/IP INFO SUBNET for TCPSAM Display Format The format of the INFO SUBNET display for TCPSAM is (an asterisk (*) indicates an alterable attribute): TCPIP Info SUBNET \OSCAR.$ZTC1.* Name Devicename *IPADDRESS #LOOP0 \NOSYS.$NOIOP 127.0.0.1 TYPE *SUBNETMASK SuName LOOP-BACK %HFF000000 QIO *R OFF N TCPIP Info SUBNET \OSCAR.$ZTC1.* Name Devicename *IPADDRESS #SN2 \OSCAR.LAN04 172.17.221.
SCF Reference for Parallel Library TCP/IP LISTOPENS Command R shows whether or not the ICMP Router Discovery Protocol (IRDP) has been enabled on the subnet. The displayed value can be Y (IRDP is ON), or N (IRDP is OFF). LISTOPENS Command The LISTOPENS command returns information on openers of the TCPMONs. This is a nonsensitive command. LISTOPENS MON Command for TCPMAN The LISTOPENS MON command displays information identifying the origins of the connections in a given TCPMON or in all TCPMONs.
LISTOPENS MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP LISTOPENS MON Display Format The format of the display for the LISTOPENS command without the DETAIL option is (an asterisk (*) indicates an alterable attribute): PTCPIP LISTOPENS MON \BEAR.$ZZTCP.#ZPTM1 OPENERS $ZNET $ZPORT PPID 13,234 3,52 BPID PLFN 2 5 BLFN 0 0 PROTOCOL #ZSPI TCP LPORT * FTP OPENERS is the process name of the opener of the TCPMON. PPID is the primary processor and PIN of the opener.
LISTOPENS MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP LISTOPENS MON Display Format With DETAIL The format of the display for the LISTOPENS MON command with the DETAIL option is: PTCPIP LISTOPENS MON \BEAR.$ZZTCP.#ZPTM3 OPENER OPENER $ZNET PROTO LADDR FADDR #ZSPI 0.0.0.0 0.0.0.0 $ZPORT PROTO TCP LADDR 0.0.0.0 FADDR 0.0.0.
SCF Reference for Parallel Library TCP/IP LISTOPENS PROCESS Command for TCPSAM RECVQ specifies the number of bytes of data in the send queue and receive queue of the socket. LADDR specifies the local internet address associated with the socket (IP addresses). LPORT is the local port number for either TCP or UDP depending on the protocol listed in the PROTO field. LPORT is displayed in text form for the more common port values. It is displayed in decimal if they are not recognized as a common port.
LISTOPENS PROCESS Command for TCPSAM SCF Reference for Parallel Library TCP/IP DETAIL specifies that the display is to include additional detailed information on the object. Examples The following commands request non-detailed and detailed information about the openers of the specified process: -> LISTOPENS PROCESS $ZTC1 -> LISTOPENS PROCESS $ZTC1, DETAIL LISTOPENS PROCESS Display Format The format of the display for the LISTOPENS command without the DETAIL option is: TCPIP Listopens PROCESS \BOBAFET.
SCF Reference for Parallel Library TCP/IP LISTOPENS PROCESS Command for TCPSAM Bpid is the backup processor and process ID of the opener. Plfn is the logical file number of the primary opener process. Blfn is the logical file number of the backup opener process. Proto is the protocol of the opener. State is the state a particular socket is in. Only sockets with TCP protocol have states associated with them.
SCF Reference for Parallel Library TCP/IP NAMES Command NAMES Command The NAMES command displays the names of the specified PTCPIP objects. This is a nonsensitive command. NAMES ENTRY Command for TCPMAN The NAMES ENTRY command displays the names of the ENTRY objects for the Parallel Library TCP/IP subsystem in a configured TCPMON or in all configured TCPMONs. Command Syntax NAMES [ /OUT file-spec/ ] [ ENTRY $ZZTCP.#ZPTMn.
SCF Reference for Parallel Library TCP/IP NAMES ROUTE Command for TCPMAN NAMES ROUTE Command for TCPMAN The NAMES ROUTE command displays the names of the routes for the Parallel Library TCP/IP subsystem. Command Syntax NAMES [ / OUT file-spec / ] [ROUTE $ZZTCP.#ZPTMn.* ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE ROUTE $ZZTCP.#ZPTMn.* is the name of the route. The route name is $ZZTCP.#ZPTMn.*.
NAMES ROUTE Command for TCPSAM SCF Reference for Parallel Library TCP/IP NAMES ROUTE Command for TCPSAM The NAMES ROUTE command for TCPSAM displays the names of the routes configured in the same processor as the TCPSAM process. Command Syntax NAMES [ / OUT file-spec / ] [ROUTE $tcpsam-name.*] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE $tcpsam-name.* is the name of the route.
SCF Reference for Parallel Library TCP/IP NAMES SUBNET Command for TCPMAN NAMES SUBNET Command for TCPMAN The NAMES SUBNET command for TCPMAN displays the names of the SUBNETs for the Parallel Library TCP/IP subsystem in a configured TCPMON or in all configured TCPMONs. Command Syntax NAMES [ / OUT file-spec / ] [ SUBNET $ZZTCP.#ZPTMn.* ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $ZZTCP.#ZPTMn.* is the name of the subnet.
SCF Reference for Parallel Library TCP/IP NAMES SUBNET Command for TCPSAM NAMES SUBNET Command for TCPSAM NAMES SUBNET for TCPSAM displays the names of the subnets configured on the TCPMON process in the same processor. Command Syntax NAMES [ / OUT file-spec / ] [ SUBNET $tcpsam-name.* ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $tcpsam-name.subnet-name is the name of the subnet.
SCF Reference for Parallel Library TCP/IP PRIMARY PROCESS Command for TCPSAM Command Syntax PRIMARY [ / OUT file-spec / ] [ PROCESS $ZZTCP ] , CPU cpu-number OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $ZZTCP is the name of the TCPMAN process. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
SCF Reference for Parallel Library TCP/IP START Command PROCESS tcpsam-name is the name of the TCPSAM process. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs. CPU cpu-number is the number of the processor of the backup process. This attribute is required.
SCF Reference for Parallel Library TCP/IP START ROUTE Command for TCPMAN $ZZTCP.#ZPTM{0-F } is the name of the TCPMON. The wild card (*) is supported. If you substitute the wild card for the TCPMON names, a TCPMON is started in every running processor. You can start TCPMONs in specific processors by listing a string of TCPMONs in parentheses, such as: ->ASSUME PROCESS $ZZTCP ->START MON (#ZPTM0, #ZPTM1, #ZPTM2, #ZPTM3) Caution.
SCF Reference for Parallel Library TCP/IP START SUBNET Command for TCPMAN ROUTE $ZZTCP.*.route-name is the name of the route. The fully-qualified route name is $ZZTCP.*. route-name (you must start the route on all configured TCPMONs). If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
SCF Reference for Parallel Library TCP/IP STATS Command The following command is valid even if you have not assumed the TCPMON name: -> START SUBNET $ZZTCP.SN1 Considerations • • • • • The object-name template (wild-card notation) is supported. When you use the START command, the object must be in the STOPPED summary state. The SLSA subsystem must be operational before subnets can be started successfully. To terminate the operation of subnets, use the STOP or ABORT command.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN STATS MON Command for TCPMAN The STATS MON command displays the PTCPIP subsystems statistics for each of the protocol layers in a given TCPMON or in all configured TCPMONs. Command Syntax STATS [ / OUT file-spec / ] [MON $ZZTCP.#ZPTMn.mon-name] [ , RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON $ZZTCP.#ZPTMn.mon-name is the name of the TCPMON.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN STATS MON Display Format The format of the display for the STATS MON command is: TCPMAN Stats MON \BEAR.$ZZTCP.#ZPTM2 Sample Time ... 16 Jun 1999, 6:46:37.534 Reset Time .... 16 Jun 1999, 6:28:26.279 TCP LAYER STATS Bad Checksum..........0 Bad Offset..........0 Too Short.............0 Bad Sequence........0 Retransmitted PKTs....6 Connection Timeouts.0 Total PKTs Input......310 Total PKTs Output...218 Incoming Connections..
STATS MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP The STATS MON command display (continued) is: IP Bad Checksum..........0 Invalid Header Size...0 Fragments Input.......0 Packets Cant Forward..0 Short Packets.........0 Fragments Timed Out...0 Total Packets Input...310 Deliverd to Upper.....310 PKTs Lost, No Buffer..0 Packets Fragmented....0 Packets, Dont Fragment.0 Discarded, No Route...0 PKTs, Raw IP Generate.0 Frags, Exceed Limit...0 Bad Route Redirects..0 New Gateway Redirect.
STATS MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP The STATS MON command display (continued) is: Data MDs In Use........ Dup MDs In Use......... Dup Driver MDs In Use.. No Data MDs Avail...... MD Queue Limits........ QIO Driver Errors...... Current Pool Allocation Pool Allocation Fails.. Size Size Size Size Size Size QIO STATS 1D 0D 0D 0D 0D 0D 497992D 0D SOCKET SEND SIZE HISTOGRAM 1-128............. 2D Size 129-256........... 0D 257-512........... 0D Size 513-1024..........
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Bad Offset is the number of packets received with invalid data offsets in their TCP headers. An invalid data offset usually indicates that either the sender of the packet made an internal error in generating the packet, or the receiver of the packet had a byteswapping problem. This error is rare and is usually seen only during the development of the protocol. Bad Sequence is the number of packets with bad sequence numbers.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Duplicate Bytes Recv is the number of duplicate bytes received. Duplicate PKTs Recv is the number of duplicate packets received. Embryonic Conn Dropped is the number of embryonic connections dropped. Established Connects is the number of connections established. Incoming Connections is the number of incoming connection requests. Keep-Alive Dropped is the number of connections dropped because of keep-alive timeouts.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Partial Dup PKTs is the number of packets received with some duplicate data. PCB Cache Missed is the number of input packets missing PCB cache. Persist Timeouts is the number of persistent timeouts. PKTs Rcv After Close is the number of packets received after close. PKTs Rcv After Window is the number of packets received exceeding the window boundary. PKTs Unacknowledged is the number of unacknowledged packets.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Total PKTs Input is the number of packets received. Total PKTs Output is the number of packets sent down to the IP layer. Urgent PKTs Recv is the number of packets received with the URG bit set. Urgent PKTs Sent is the number of packets sent with the URG bit set. Window Probes Sent is the number of window probes sent. Window Update PKT Sent is the number of window update packets sent.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN SYN CACHE DROP, BOvF is the number of SYN cache entries dropped due to bucket overflow. SYN CACHE ABORTED is the number of SYN cache aborted (no memory). SYN CACHE DUPLICATED is the number of duplicated SYNs received. SYN CACHE DROPPED is the number of SYNs dropped (no route/mem). Description of Statistics for the UDP Layer (in Alphabetical Order) Bad Checksum is the number of packets received with invalid checksum values.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Pkts, Miss pcb Cach is the number of input packets missing pcb cache. PKTS with no Chksum the number of packets received with no checksums. Total PKTs Input is the number of packets received. Total PKTs Output is the number of packets sent to the IP layer. Description of Statistics for the IP Layer (in Alphabetical Order) Bad Checksum is the number of packets received with invalid checksum values.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Fragments Timed Out is the number of packet fragments received that timed out before the whole packet was received. This is usually caused by congestion, noisy links, or some event that prevents one of the fragments from being received with the rest. Frags, Exceed Limit is the number of fragments that exceeded the limit. ICMP Redirects Sent is the number of ICMP Redirect messages sent.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Packets Too Small is the number of packets that contained less data than was expected when the packet was read into the local buffers. This error usually indicates a problem with the local machine's buffering scheme. Pkts, Ip Ver != 4 is the number of packets with IP version not equal to 4. PKTs, Generated Here is the total number of IP packets generated here. PKTs Lost, No Buffer is the number of IP packets lost here due to no buffer.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN New Gateway Redirect is the number of messages received that established a route for a new or an unknown gateway. Unreachable is the number of messages received that indicated that the specified destination was unreachable. wild-Card Matches is the number of wild-card matches found when zeros were given in the destination Internet address for a route.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Bad Router Words/ADDR is the number of IRDP messages with an incorrect address length. Errors is the number of times an ICMP error was generated. Note that Redirect messages are not included in the total. ICMP errors can be caused by any of the following reasons: invalid IP options, problems in IP packet forwarding, or a UDP server crash.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN In Info Request is the number of Information Request (type 15) messages received. A host or gateway can send this message—with the network portion of the source address and the destination address set to 0—to determine the number of the network on which it is running. Any host on the network can respond to this request with an Information Reply message. In Param Problem is the number of Parameter Problem (type 12) messages received.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN datagram. A destination host sends this message if the host cannot reassemble a fragmented datagram within the time limit because fragments are missing. The destination host then discards the datagram. When a Time Exceeded message is received, you should check for routing loops. In Timestamp is the number of Timestamp (type 13) messages received.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Out Info Reply is the number of Information Reply messages sent. Out Info Request is the number of Information Request messages sent. Out Param Problem is the number of Parameter Problem messages sent. Out Redirect is the number of Redirect messages sent. Out Source Quench is the number of Source Quench messages sent. Out Time Exceeded is the number of Time Exceeded messages sent. Out Timestamp is the number of Timestamp messages sent.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Data MDs In Use is the current number of data MDs in use by the process. Dup Driver MDs In Use is the current number of duplicate MDs assigned to inbound driver MDs in use by the process. Dup MDs in Use is the current number of duplicate MDs not assigned to inbound driver MDs in use by the process. Maximum Data MDs Used is the maximum number of data MDs that have been in use.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN No Dup MDs Avail is the number of times the process failed to obtain a duplicate MD. Pool Allocation Fails is the number of times a pool space request failed. QIO Driver Errors is the number of times the QIO driver returned an error. QIO Limit Warnings is the number of times the process received an event signifying a pool or an MD shortage from the QIO monitor. Total MBUFs Allocated is the current number of MBUFs allocated.
SCF Reference for Parallel Library TCP/IP STATS MON Command for TCPMAN Size 12289-16384 is the count of socket sends between 12289 and 16384 bytes. Size 16385-32768 is the count of socket sends between 16385 and 32768 bytes. Description of Statistics for the ARP STATS (in Displayed Order) In ARP Requests is the number of ARP requests received. Out ARP Requests is the number of ARP requests sent. In ARP Replys is the number of ARP replies received. Out ARP Replys is the number of ARP replies sent.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Total Reports Sent is the total number of IGMP report packets sent by this process. Short Packets is the total number of IGMP packets received that were too short. Bad Checksum is the total number of IGMP packets received that had an incorrect checksum. Total Queries Input is the total number of IGMP query packets received.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM PROCESS $tcpsam-name is the name of the TCPSAM process. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
STATS PROCESS Command for TCPSAM SCF Reference for Parallel Library TCP/IP STATS PROCESS Display Format The format of the display for the STATS PROCESS command is: TCPIP Stats PROCESS \SYSA.$ZSAM1 Sample Time ... 17 Oct 1999, 17:17:41.169 Reset Time .... Invalid date/time Bad Checksum.......... Invalid Header Size... Retransmitted Packets. Total Packets Input... Incoming Connections.. No Ports For Packets.. Packets Unacknowledged Connections Dropped... Connections Closed.... RTT Updated...........
STATS PROCESS Command for TCPSAM SCF Reference for Parallel Library TCP/IP The STATS PROCESS command display (continued): Bad Checksum.......... Invalid Header Size... Reflect Packets....... Bad ICMP Code......... In Echo Reply......... In Dest Unreachable... In Source Quench...... In Redirect........... In Echo............... In Time Exceeded...... In Parameter Problem.. In Timestamp.......... In Timestamp Reply.... In Info Request....... In Info Reply.........
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Description of Statistics for the TCP Layer (in Alphabetical Order) ACK Bytes Received is the number of ACK bytes acknowledged by received ACKs. ACK Packets Received is the number of ACK packets received. ACK Packets Sent is the number of ACK packets sent. ACK Predictions OK is the number of times the header predictions were correct for ACKs. Bad Checksum is the number of packets received with invalid checksum values.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM appropriate acknowledgments cannot be received and/or sent); or a corrupted packet (that is, a packet with an invalid checksum) is received. Connections Closed is the number of connections closed (this value includes the number of connections dropped). Connections Dropped is the number of connections dropped. Control Packets Sent is the number of SYN, FIN, and RST control packets sent.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Established Connects is the number of connections established. Incoming Connections is the number of incoming connection requests. Invalid Header Size is the number of packets received with an invalid header size. This error usually indicates a problem between IP and TCP. Keep-Alive Dropped is the number of connections dropped because of keep-alive timeouts. Keep-Alive Probes Sent is the number of keep-alive probes sent.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Persist Timeouts is the number of persistent timeouts. PKTs Recv After Close is the number of packets received after close. PKTs Recv After Window is the number of packets received exceeding the window boundary. Retransmitted Bytes is the number of bytes retransmitted. Retransmitted Packets is the number of packets retransmitted. Packets are retransmitted when a packet is not acknowledged within a certain time period.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Urgent Packets Sent is the number of packets sent with the URG bit set. Window Probes Sent is the number of window probes sent. Window Update PKT Sent is the number of window update packets sent. Window Probe PKTs Recv is the number of window-probes packets received. Window Update Pkts is the number of window update packets received.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Description of Statistics for the IP Layer (in Alphabetical Order) Bad Checksum is the number of packets received with invalid checksum values. An invalid checksum is usually caused by a noisy link. Bad Packet Size is the number of packets received with a packet length shorter than expected. This error is very similar to the Invalid Header Size and is usually caused by similar conditions.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Packets Too Small is the number of packets that contained less data than was expected when the packet was read into the local buffers. This error usually indicates a problem with the local machine's buffering scheme. Short Packets is the number of packets that contained less data than specified in their header.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Bad ICMP Code is the number of packets received that contain invalid ICMP packet-type codes in the header.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM unreachable. This message can be caused by the following reasons: either there is no route to the destination or the route to the destination has gone down; a nonexistent address has been specified; the process listening on the port has gone down; the destination host has crashed; or fragmentation is needed but the Don't Fragment flag is set. In Echo is the number of Echo (type 8) messages received.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM routing table to reflect the new route. If a host receives many Redirect messages in a short period of time, it is usually an indication that the host is not correcting its routing table. When the NonStop TCP/IP subsystem services the In Redirect messages, it adds a dynamic route entry of the name #DYRTn. This dynamic route is used in lieu of the previous route which has been redirected.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Invalid Header Size is the number of packets received with a length that is shorter than the length specified in the header. This error, usually caused by a noisy link, is rarely reported because the checksum routine also detects this problem. Packets Too Short is the number of packets received that were shorter than the minimum length allowed for an ICMP packet. Short packets are usually caused by a noisy link.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Out Timestamp is the number of Timestamp messages sent. Out Timestamp Reply is the number of Timestamp Reply messages sent. Router Advertisement is the number of IRDP discovery messages detected by the NonStop TCP/IP subsystem. The NonStop TCP/IP subsystem either records these routes or ignore them, depending on how IRDP is configured and according to route preference.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Max Dup Driv MDs Used is the maximum number of duplicate MDs assigned to inbound driver MDs in use by the process. Maximum MBUFs Used is the maximum number of MBUFs to be used. Maximum Pool Allocation is the maximum pool space used. MBUF Allocation Fails is the number of times an MBUF was not available. MD Queue Limits is the number of times the send or receive queue on a TCP session exceeded a predefined limit of MDs queued.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Description of Statistics for Socket Send Size Histogram Size 1-128 is the count of socket sends between 1 and 128 bytes. Size 129-256 is the count of socket sends between 129 and 256 bytes. Size 257-512 is the count of socket sends between 257 and 512 bytes. Size 513-1024 is the count of socket sends between 513 and 1024 bytes. Size 1025-2048 is the count of socket sends between 1025 and 2048 bytes.
SCF Reference for Parallel Library TCP/IP STATS PROCESS Command for TCPSAM Out ARP Replys is the number of ARP replies sent. In InARP Requests is the number of inverse ARP requests received. Out InARP Requests is the number of inverse ARP requests sent. In InARP Replys is the number of inverse ARP replies received. Out InARP Replys is the number of inverse ARP replies sent. In ARP Naks is the number of ARP Naks received. Out ARP Naks is the number of ARP Naks sent.
SCF Reference for Parallel Library TCP/IP STATS ROUTE Command for TCPMAN Total Reports Input is the total number of IGMP membership reports received. Bad Reports is the total number of bad IGMP membership reports received. Reports For Our Groups is the total number of IGMP membership reports received for groups we belong to. STATS ROUTE Command for TCPMAN The STATS ROUTE command displays the Parallel Library TCP/IP subsystem statistics for the specified routes. Note.
SCF Reference for Parallel Library TCP/IP STATS ROUTE Command for TCPMAN STATS ROUTE Display Format The format of the display for a ROUTE object is: TCPMAN Stats ROUTE \OSCAR.$ZPTM0.* Sample Time ... 04 Jan 2000, 16:53:45.447 Reset Time .... 03 Jan 2000, 10:55:16.071 Name RT1 Route Usage 0D Sample Time ... 04 Jan 2000, 16:53:45.447 Reset Time .... 03 Jan 2000, 10:55:16.091 Name RT3 Route Usage 0D Sample Time ... 04 Jan 2000, 16:53:45.447 Reset Time .... 04 Jan 2000, 15:56:52.
SCF Reference for Parallel Library TCP/IP STATS ROUTE Command for TCPSAM Name is the name of the route. Route Usage is the number of times this route was used to send IP datagrams. STATS ROUTE Command for TCPSAM The STATS ROUTE command displays the Parallel Library TCP/IP subsystem statistics for the specified routes in the processor containing the TCPSAM process. Note. STATS ROUTE with the RESET option is sensitive. Command Syntax STATS [ / OUT file-spec / ] [ROUTE $tcpsam-name.
SCF Reference for Parallel Library TCP/IP STATS SUBNET Command for TCPMAN STATS ROUTE Display Format The format of the display for a ROUTE object is: TCPIP Stats ROUTE \SYSA.$ZSAM1.* Sample Time ... 23 March 1996, 17:18:25.334 Reset Time .... 23 March 1996, 11:47:47.166 Name #ROU1 Route Usage 10709D Sample Time is the time when the statistics were sampled (displayed or written to a file). Reset Time is the time when the counters were last reset to zero. Name is the name of the route.
STATS SUBNET Command for TCPMAN SCF Reference for Parallel Library TCP/IP RESET resets the statistical counters to zero. DETAIL requests the detailed status information for the subnet. Examples The following example requests statistics for subnets for starting with SN: -> STATS SUBNET $ZZTCP.#ZPTM3.SN* The following example requests statistics for all running subnets: ->STAT SUBNET $ZZTCP.*.
SCF Reference for Parallel Library TCP/IP STATS SUBNET Command for TCPMAN Reset Time is the time when the counters were last initialized (set to zero). Name is the name of the subnet. Filter Errors indicates the number of errors received from SLSA for filter registrations. Filter Timeouts indicates that the filter registration is not receiving a reply from SLSA in the allowed time. Output Packets is the number of packets sent by the subnet. Input Packets is the number of packets received by the subnet.
SCF Reference for Parallel Library TCP/IP STATS SUBNET Command for TCPSAM UDP filters Reg is the number of UDP filters registered. UDP filters Error is the number of UDP filter registration errors. UDP filters Dereg is the number of UDP filters de-registered. Port filters Drop is the number of port filters dropped. Media State Down shows the total media down events received from the adapter. Considerations • • • • The object-name template (wild-card notation) is supported.
STATS SUBNET Command for TCPSAM SCF Reference for Parallel Library TCP/IP SUBNET $tcpsam-process.subnet-name is the name of the subnet. The fully-qualified name of the subnet is $tcpsamprocess.subnet-name. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs. RESET resets the statistical counters to zero. DETAIL requests the detailed status information for the subnet.
SCF Reference for Parallel Library TCP/IP STATUS Command Output Packets is the number of packets sent by the subnet. Input Packets is the number of packets received by the subnet. Filter Errors indicates the number of errors received from SLSA for filter registrations. Filter Timeouts indicates that the filter registration is not receiving a reply from SLSA in the allowed time. Output Errors is the number of errors that occurred when packets were sent by the subnet.
SCF Reference for Parallel Library TCP/IP STATUS ENTRY Command for TCPMAN STATUS ENTRY Command for TCPMAN The STATUS ENTRY command displays the dynamic status of the specified entry in a given TCPMON or in all configured TCPMONs. Command Syntax STATUS [ / OUT file-spec / ] [ ENTRY $ZZTCP.#ZPTMn.entry-name] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ENTRY $ZZTCP.#ZPTMn.entry-name is the name of the entry.
SCF Reference for Parallel Library TCP/IP STATUS MON Command for TCPMAN IPADDRESS is the IP address of the entry. Arp Timer is the time in minutes left to expire. Arp Flags is the state of the ARP table entry; possible values are: COMPLETED indicates a resolved entry. That is, the reply to an ARP request has been received. PERMANENT indicates a static entry that is never cleared from the ARP cache. INUSE indicates an entry that is currently in use. INCOMPL indicates an unresolved entry.
STATUS MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP Command Syntax STATUS [ / OUT file spec / ] [ MON $ZZTCP.#ZPTMn ] [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON $ZZTCP.#ZPTMn is the name of the TCPMON. The fully-qualified name of the TCPMON object is $ZZTCP.#ZPTMn. You may substitute the wild card (*) for the TCPMON name; doing so yields the status information on all TCPMONs (in all processors).
SCF Reference for Parallel Library TCP/IP STATUS MON Command for TCPMAN Status indicates the state of the TCPMON. PID is the process ID of the TCPMON in the PTCPIP subsystem. Proto is the protocol associated with the socket, which can be UDP (for a UDP socket), TCP (for a TCP socket), or a protocol number (for a raw IP socket). State is the current state of the socket; it applies only to sockets whose Proto value is TCP.
SCF Reference for Parallel Library TCP/IP STATUS MON Command for TCPMAN SYN-RCVD if waiting for an acknowledgment of a SYN-ACK sent in response to a SYN. SYN-SENT if waiting for a SYN-ACK after having sent a SYN. TIME-WAIT if waiting for sufficient time to pass (about two round trips) to be sure that stray packets are flushed from the network. UNKNOWN the socket was in the closing state when the command was issued.
STATUS PROCESS Command for TCPMAN SCF Reference for Parallel Library TCP/IP Multicast Group States is the state of the multicast groups. Possible values are: STARTED indicates that multicast is operational for the group. STARTING indicates that the multicast group is transitioning to the STARTED (and operational) state but is not yet fully operational. STOPPED indicates that multicast is not operational for the group.
SCF Reference for Parallel Library TCP/IP STATUS PROCESS Command for TCPSAM Status always indicates that the process is STARTED. PPID is the processor and process ID of the TCPMAN primary process. BPID is the processor and process ID of the TCPMAN backup process. If TCPMAN is running without a backup process, this field shows ( 0, 0). STATUS PROCESS Command for TCPSAM The STATUS PROCESS command displays the dynamic state of the TCPSAM process and any in-use ports.
STATUS PROCESS Command for TCPSAM SCF Reference for Parallel Library TCP/IP STATUS PROCESS Display Format The format of the display for STATUS PROCESS both with the detail option is: TCPIP Detailed Status PROCESS \BEAR.$SAM2 Status: STARTED PPID............( 1,54) BPID..................( 2, 32) Proto State Laddr Lport TCP ESTAB 50.0.0.3 ftp TCP LISTEN 0.0.0.0 echo UDP 0.0.0.0 8000 ---Multicast Groups--224.0.0.1 230.17.123.55 239.1.2.3 UDP 0.0.0.0 7000 Faddr 50.0.0.1 0.0.0.0 0.0.0.0 0.0.0.
SCF Reference for Parallel Library TCP/IP STATUS PROCESS Command for TCPSAM FIN-WAIT-1 if waiting for a terminate connection request from the remote TCP site or if waiting for acknowledgment of the terminate connection request that the process has sent previously. FIN-WAIT-2 if waiting for a termination of data to be received after having sent a FIN (termination of data being sent). LISTEN if waiting for a connection request from any remote TCP site.
SCF Reference for Parallel Library TCP/IP STATUS ROUTE Command for TCPMAN Fport is the foreign port number for either TCP or UDP, depending on the value of Proto. The more common port values are displayed in text form; others are displayed as four-decimal octets. SendQ is the number of bytes of data in the send queue of the socket. RecvQ is the number of bytes of data in the receive queue of the socket. Multicast Groups indicates the IP multicast group addresses that the PTCPIP connection is listening to.
STATUS ROUTE Command for TCPMAN SCF Reference for Parallel Library TCP/IP ROUTE $ZZTCP.#ZPTMn.route-name is the specification of the route name. The fully-qualified route name for TCPMAN is $ZZTCP.#ZPTMn.route-name. To obtain status information about a route on all configured TCPMONs, use the wild-card (*) notation for the TCPMON name. For example, STATUS ROUTE *.RT1. To obtain status information about a ROUTE on one TCPMON, qualify the TCPMON name. For example, STATUS ROUTE #ZPTM1.RT1.
STATUS ROUTE Command for TCPSAM SCF Reference for Parallel Library TCP/IP STATUS ROUTE Command for TCPSAM This command displays the status of the routes configured in the TCPMON on the TCPSAM primary processor. This is a nonsensitive command. Command Syntax STATUS [ / OUT file spec / ] [ROUTE $tcpsam-name.#route-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE $tcpsam-name.#route-name is the specification of the route name.
STATUS SUBNET Command for TCPMAN SCF Reference for Parallel Library TCP/IP Considerations A pound sign (#) precedes the ROUTE name for backward compatibility with applications that expect this naming convention for ROUTEs. See Supported Commands and Object Types on page 5-9. STATUS SUBNET Command for TCPMAN The STATUS SUBNET command displays the current status of the specified subnets. Command Syntax STATUS [ / OUT file spec / ] [SUBNET $ZZTCP.#ZPTMn.
SCF Reference for Parallel Library TCP/IP STATUS SUBNET Command for TCPSAM Name is the name of the subnet. Status is the summary state of the subnet. FailOver indicates whether the subnet is failover enabled or not. SharedIP indicates whether the subnet has the same subnet IP address as its brother. YES-PRIMARY indicates that this subnet is failover-capable and has the same subnet IP address as another subnet.
STATUS SUBNET Command for TCPSAM SCF Reference for Parallel Library TCP/IP Command Syntax STATUS [ / OUT file spec / ] [SUBNET $tcpsam-name.#subnet-name] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $tcpsam-name.#subnet-name is the specification of the subnet. The fully-qualified subnet name for TCPSAM is $tcpsam-name.#subnet-name.
SCF Reference for Parallel Library TCP/IP STOP Command STOP Command The STOP command terminates the operation of the specified PTCPIP object. You can stop processes, subnets, and routes. When the operation is complete, the object(s) is in the STOPPED summary state. If the specified objects are in use, the STOP command is not completed. If you attempt to stop an object that is in use or is already in the STOPPED summary state, the Parallel Library TCP/IP subsystem returns a warning.
SCF Reference for Parallel Library TCP/IP STOP PROCESS Command for TCPMAN STOP PROCESS Command for TCPMAN The STOP PROCESS command terminates the activity of the specified TCPMAN process in a normal, orderly manner. This is a sensitive command. Command Syntax STOP [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [, SUB ALL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $ZZTCP is the TCPMAN process.
SCF Reference for Parallel Library TCP/IP STOP ROUTE Command for TCPMAN Command Syntax STOP [ / OUT file-spec / ] [ PROCESS $tcpsam-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $tcpsam-name is the name of the TCPSAM process. If you omit the object name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs.
SCF Reference for Parallel Library TCP/IP STOP SUBNET Command for TCPMAN created. You can also substitute the wild card for the route name; doing so stops all routes on all TCPMONs. Examples The following command terminates the operation of the specified route: SCF> STOP ROUTE $ZZTCP.#ZPTM1.
SCF Reference for Parallel Library TCP/IP TRACE Command Examples The following command terminates the operation of the subnet SN2: SCF> STOP SUBNET $ZZTCP.*.SN2 Considerations • • • To stop a subnet immediately, use the ABORT command. To remove a subnet from the system configuration database, use the DELETE SUBNET command. You can use the wild-card (*) notation for the TCPMON name, but if you do not, it is assumed.
TRACE MON Command for TCPMAN SCF Reference for Parallel Library TCP/IP Command Syntax TRACE [ /OUT file-spec/ ] {, STOP } | {, TO file-spec MON [ $ZZTCP.#ZPTMn ] [ [ [ [ [ [ , , , , , , BULKIO / NOBULKIO COUNT count NOCOLL RECSIZE size SELECT select-spec PAGES pages ] ] ] ] ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON $ZZTCP.#ZPTMn, is the name of the TCPMON you want to trace. The wild card (*) is not supported.
SCF Reference for Parallel Library TCP/IP TRACE PROCESS Command for TCPMAN UDP UDP interface layer TCP Transmission Control Protocol message layer IP IP layer LOGIC Several of the above selections including socket requests (SOCKCMD) and message system interface (MSGSYS) COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If this option is omitted or if count equals -1, records are accumulated until you use the STOP option.
SCF Reference for Parallel Library TCP/IP TRACE PROCESS Command for TCPMAN Command Syntax TRACE [ /OUT file-spec/ ] PROCESS $ZZTCP { , STOP [ , BACKUP ] | [ , TO file-spec [ , BACKUP ] [ , COUNT count ] [ , NOCOLL ] [ , RECSIZE size ] [ , SELECT select-spec ] [ , PAGES pages ] ] } OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $ZZTCP is the name of the TCPMAN process. If you omit the object name, SCF uses the assumed object name.
SCF Reference for Parallel Library TCP/IP TRACE PROCESS Command for TCPMAN NOCOLL Indicates that the trace collector process should not be initiated. The disk file is to be written to by Guardian. The attributes WRAP and NOCOLL might not be specified together. PAGES pages pages specifies how many extended data segment pages are allocated when tracing. An integer value in the range 4 to 64 is expected. The default is 64 pages. RECSIZE size size is an integer in the range 1024 to 4050.
TRACE PROCESS Command for TCPSAM SCF Reference for Parallel Library TCP/IP Considerations The TCPMAN trace facilities for the primary and the backup TCPMAN processes are independent. The primary and the backup traces can be active at the same time. In the event of a primary/backup process switch, such as when the PRIMARY command is issued, the original primary TCPMAN process becomes the new backup process and the backup process becomes the primary.
SCF Reference for Parallel Library TCP/IP TRACE PROCESS Command for TCPSAM is assumed. The TCPSAM process must be running as a NonStop process pair if this syntax is used. If the primary TCPSAM is being traced when a takeover by the backup TCPSAM occurs, the trace of the same TCPSAM continues, but most events that were being traced prior to the TCPSAM switch is no longer traced. This is because the TCPSAM being traced is no longer the primary.
TRACE SUBNET Command for TCPMAN SCF Reference for Parallel Library TCP/IP Considerations The TCPSAM trace facilities for the primary and the backup TCPSAM processes are independent. The primary and the backup traces can be active at the same time. In the event of a primary/backup process switch, such as when the PRIMARY command is issued, the original primary TCPSAM process becomes the new backup process and the backup process becomes the primary.
SCF Reference for Parallel Library TCP/IP TRACE SUBNET Command for TCPMAN BULKIO / NOBULKIO specifies whether TRACE should use bulk I/O for tracing. BULKIO, the default parameter, specifies that the TRACE collector use bulk I/O to write data to the disk file, thus reducing the number of missing frame errors reported by PTRACE. BULKIO and NOBULKIO are optional parameters. SELECT selects the operations to be traced.
SCF Reference for Parallel Library TCP/IP VERSION Command Examples The following command traces the $ZZTCP.#ZPTM1.SN2 subnet, writes the results into the file $SYSA.TRACES.TCPSUB and traces all PTCPIP process activity on the subnet: SCF> TRACE SUBNET $ZZTCP.#ZPTM1.SN2, TO $SYSA.TRACES.TCPSUB,& RECSIZE 300, NOBULKIO VERSION Command The VERSION command displays the Parallel Library TCP/IP subsystem version number, product name, product number, and RVU date.
SCF Reference for Parallel Library TCP/IP VERSION PROCESS Command for TCPMAN Version Command Display Format VERSION MON \BEAR.$ZZTCP.#ZPTM1:T0470G06_15APR2000_G06_MO_A0614 Detailed VERSION MON \BEAR.$ZZTCP.#PTM2 SYSTEM \BEAR T0470G06_15APR2000_G06_MO_A0614 GUARDIAN - T9050 - (Q06) SCF KERNEL - T9082G02 - (24SEP99) (26JUL99) PTCPIP PM - T0473G40 - (01JAN2000) - (A0602) VERSION PROCESS Command for TCPMAN The VERSION PROCESS command displays the version level of the PTCPIP subsystem.
SCF Reference for Parallel Library TCP/IP VERSION PROCESS Command for TCPSAM VERSION Command Display Format The format of the display of the VERSION PROCESS command without the DETAIL option is: VERSION PROCESS \BOBAFET.$ZZTCP: T0468G40_01JAN2000_G40_MA_A0603 The format of the display of the VERSION PROCESS command with the DETAIL option is: Detailed VERSION PROCESS \BEAR.
SCF Reference for Parallel Library TCP/IP Parallel Library TCP/IP Trace Facility VERSION Command Display Format The format of the display of the VERSION command without the DETAIL option is: VERSION PROCESS \BOBAFET.$ZTC1: T0471G40_01JAN2000_G40_SA_A0603 The format of the display of the VERSION command with the DETAIL option is: Detailed VERSION PROCESS \BEAR.
SCF Reference for Parallel Library TCP/IP Introduction to PTrace Figure 5-3. Recording and Displaying Trace Data Start the trace interactively with the SCF TRACE command or programmatically through SPI. Collect trace data. Stop the trace with the SCF TRACE command or through SPI. Display the trace file with PTrace. VST0503.vsd 1. Start the trace interactively with the SCF TRACE command or programmatically with SPI. 2.
SCF Reference for Parallel Library TCP/IP PTrace Commands PTrace Commands The PTrace commands provide options for selecting trace records for display, so you can suppress those records that do not relate to the problem you are investigating. The PTrace commands also provide options for specifying the way in which the trace records are formatted. Although PTrace provides a common set of commands for displaying trace records, not all of the PTrace commands are supported by each subsystem.
SCF Reference for Parallel Library TCP/IP PTrace Commands Table 5-7.
SCF Reference for Parallel Library TCP/IP DETAIL Command DETAIL Command The DETAIL command controls the detailed display option. When DETAIL is set to ON, PTrace displays extended formatted versions of some records (for example, ARP traffic). Command Syntax DETAIL [ ON | OFF ] ON turns on detailed display mode. OFF turns off detailed display mode. Considerations • The Parallel Library TCP/IP DETAIL command is implemented in the standards defined in the PTrace Reference Manual.
LABEL Command SCF Reference for Parallel Library TCP/IP Considerations • The Parallel Library TCP/IP HEX command is implemented in the standards defined in the PTrace Reference Manual. • • • If the HEX command is not used, the OFF attribute is assumed. If HEX is specified without the ON or OFF attribute, the ON attribute is assumed. The RESET and FROM commands set the HEX command to OFF. LABEL Command The LABEL command controls the formatted display of trace records.
SCF Reference for Parallel Library TCP/IP SELECT Command ON turns on octal display mode. OFF turns off octal display mode. Considerations • • • If the OCTAL command is not used, the OFF attribute is assumed. If OCTAL is specified without the ON or OFF attribute, the ON attribute is assumed. The RESET and FROM commands set the OCTAL command to OFF. SELECT Command The SELECT command establishes the selection criteria that control which trace records are to be displayed.
SCF Reference for Parallel Library TCP/IP SELECT Command TCP Transmission Control Protocol message layer IP IP layer LOGIC Several of the above selections including socket requests (SOCKCMD) and message system interface (MSGSYS) The following keywords apply to the SUBNET object: ALL All records IPI IP input records IPO IP output records ARPI ARP input records ARPO ARP output records LOGIC A combination of all the above records USERDATA Used with IPI and IPO to display user data Conside
TEXT Command SCF Reference for Parallel Library TCP/IP 2. The following command sequence can be used to trace and decode ARP protocol traffic during a SUBNET object trace: TRACE SUBNET #E1,TO TRACEFL,RECSIZE 500,SELECT (ARPI,ARPO) 3.
SCF Reference for Parallel Library TCP/IP Trace Record Formats Trace Record Formats This subsection describes the formatted Parallel Library TCP/IP trace records. The records are presented in alphabetical order under the SELECT keyword used to display them.
SCF Reference for Parallel Library TCP/IP Socket Creation Records seq-no indicates the sequence number. The sequence number is included to keep track of records that are lost when the trace file is written to disk. The sequence number counts from 0 to 255 and then begins again. time indicates the time since the last trace run on this line. timestamp indicates the timestamp of the record. The timestamp reports the time at which the record was captured. The resolution is to one hundredth of a second.
SCF Reference for Parallel Library TCP/IP Socket Creation Records Soclose Record The soclose record is generated each time the SOCLOSE procedure is called. The SOCLOSE procedure completes the close of a socket. header procedure:soclose socket_handle nnnnaaaa line-num of file-name (time on date) is the edit-line number that caused the event, the fully-qualified edit-file name, and the last time the edit file was compiled. nnnnaaaa indicates the internal socket ID of the socket being closed.
SCF Reference for Parallel Library TCP/IP Socket Creation Records Allocating PCB Record The allocating PCB record is generated each time a protocol control block (PCB) is allocated for a TCP socket. header socket_handle nnnnaaaa allocating PCB for TCP socket nnnnaaaa indicates the internal ID of the socket for which the PCB is being allocated.
SCF Reference for Parallel Library TCP/IP Memory Buffer Allocation Records nnnnaaaa indicates the internal ID of the socket being reserved. Memory Buffer Allocation Records This subsection describes the formatted trace records displayed when the MBUF keyword is specified for the PTrace SELECT command. Note that there is only one memory buffer allocation record and that each memory buffer allocation record in the trace file is preceded by a header containing the record-type code 2.
SCF Reference for Parallel Library TCP/IP TCP Records nnnnaaaa indicates the internal ID of the socket to which the system call applies. bbb indicates the number of bytes of data received in the socket call. TCP Records This subsection describes the formatted trace records displayed when the TCP keyword is specified for the PTrace SELECT command. Note that TCP records are preceded by a header containing the record-type code 4. The records are presented in alphabetical order, based on their text format.
SCF Reference for Parallel Library TCP/IP TCP Records ack-bytes indicates the number of bytes of data acknowledged. unack-bytes indicates the number of bytes of data in the queue waiting to be acknowledged. Because the number of bytes acknowledged is greater than this value (>), all of the data in the queue has been acknowledged. After Changes Record The after changes record is generated each time data or an ACK is received for a TCP socket.
SCF Reference for Parallel Library TCP/IP TCP Records nnnnaaaa indicates the internal socket ID. snd-nxt indicates the next sequence number to be sent. snd-una indicates the oldest unacknowledged sequence number. ti-ack indicates the sequence number of the data currently being acknowledged. Receive State Change Record The receive send state change record is generated when data is received. header socket_handle nnnnaaaa tcp_handle nnnnn init-state: input (start-no..
SCF Reference for Parallel Library TCP/IP TCP Records end-no indicates the ending sequence number of the data received. ack-no indicates the acknowledgment number. urp indicates the urgent pointer. [f1,f2,f3,f4,f5,f6] indicates the control flags set. The possible flags that can be set are SYN, ACK, FIN, RST, PUSH, and URG. fin-state indicates the final state after the data was received.
SCF Reference for Parallel Library TCP/IP TCP Records snd-wl1 indicates the sequence number used for the last window update. snd-wl2 indicates the acknowledgment number used for the last window update. snd-wnd indicates the send window. Send State Change Record The send state change record is generated when a user sends data. header socket_handle nnnnaaaa tcp_handle nnnnn init-state: user req-type -> fin-state...
SCF Reference for Parallel Library TCP/IP TCP Records req-type indicates the request type. The possible request types are: ABORT PEERADDR ACCEPT PROTORCV ATTACH PROTOSEND BIND RCVD CONNECT RCVOOB CONNECT2 SEND CONTROL SENDOOB DETACH SENSE DISCONNECT SHUTDOWN FASTIMO SLOWTIMO LISTEN SOCKADDR fin-state indicates the final state after the data was sent.
SCF Reference for Parallel Library TCP/IP TCP Records snd-nxt indicates the next sequence number to be sent. snd-max indicates the maximum sequence number that can be sent. snd-wl1 indicates the sequence number used for the last window update. snd-wl2 indicates the acknowledgment number used for the last window update. snd-wnd indicates the send window. Accepting Connection Record The accepting connection record is generated each time an incoming connection is accepted on a local socket.
SCF Reference for Parallel Library TCP/IP UDP Input Records nnnnaaaa indicates the internal socket ID. forgn-addr indicates the remote Internet address associated with the incoming connection. forgn-port indicates the remote port number associated with the incoming connection. TCP Socket Request Record The TCP socket request record is generated each time a TCP socket request is made. header socket_handle nnnnaaaa: tcp_usrreq: socket request #nnnnn nnnnaaaa indicates the internal socket ID.
SCF Reference for Parallel Library TCP/IP Detailed UDP Input Records Sent UDP Packet to User Record The sent UDP packet to user record is generated each time a valid user is identified for an incoming UDP packet and the packet is delivered to the user. This record is preceded by a header containing the record-type code 5. header udp_input: Sent UDP packet to user --> udp_header_handle nnnnaaaa nnnnaaaa indicates the internal ID of the UDP packet.
UDP Output Records SCF Reference for Parallel Library TCP/IP lllll indicates the packet's length. nnnnaaaa indicates the internal ID of the UDP packet. Source Address and Port Record The source address and port record is generated each time a UDP packet is received. This record is preceded by a header containing the record-type code 5. header udp_input: src ip-addr, sport portno udp_header_handle nnnnaaaa ip-addr indicates the packet's source Internet address.
SCF Reference for Parallel Library TCP/IP IP Input Records UDP Sending to Record The UDP sending to record is generated each time the Parallel Library TCP/IP process sends a packet. header udp_output: sending to ip-addr.udp-port ip-addr indicates the destination IP address. udp-port indicates the destination UDP port number. IP Input Records This subsection describes the formatted trace records displayed when the IPI keyword is specified for the PTrace SELECT command.
SCF Reference for Parallel Library TCP/IP IP Input Records w Problem (12) Timestamp (13) Timestamp Reply (14) Information Request (15) Information Reply (16) Forwarding to IP Address Record The forwarding to IP address record is generated each time the IP input routines receive a packet destined for another destination. header ipintr: ip_handle nnnnaaaa forwarding to ip address ip-addr nnnnaaaa indicates the internal ID of the IP packet. ip-addr indicates the address to which the packet is forwarded.
SCF Reference for Parallel Library TCP/IP IP Output Records nnnnn indicates the IP protocol number (either 6 for TCP or 17 for UDP). Rebuilt Fragment Record The rebuilt fragment record is generated each time the IP input routines rebuild a packet from packet fragments. header ipintr: ip_handle nnnnaaaa rebuilt fragment len lllll nnnnaaaa indicates the internal ID of the IP packet. lllll indicates the rebuilt packet's total length.
SCF Reference for Parallel Library TCP/IP Route Records ppppp indicates the IP number associated with the packet sent. For a list of the commonly used IP numbers, refer to the TCP/IP and TCP/IPv6 Programming Manual For a complete list of the IP numbers, refer to Request for Comments document 1010, Assigned Numbers. Fragmenting Record The fragmenting record is generated each time the IP must fragment a packet.
SCF Reference for Parallel Library TCP/IP Socket Command Records indicates whether the route is to a gateway, bit 3 indicates whether the route is to a point-to-point connection, bit 4 indicates whether the route is marked down, and bit 5 indicates whether the route is a dynamic route. Route Addition Record The route addition record is generated each time a route is added. Note that this record does not return any values.
SCF Reference for Parallel Library TCP/IP Socket Command Records Accept Record The accept record is generated each time a connection is accepted on the local socket. header accept: socket_handle nnnnaaaa connection on 1234abcd.12345 nnnnaaaa indicates the internal socket ID. 1234abcd.12345 indicates the remote IP address and port number. Address Family Record The address family record is generated each time a connection request is received on the local socket.
SCF Reference for Parallel Library TCP/IP Socket Command Records Connection Request Record The connection request record is generated each time a connection request is received on the local socket. header connect: socket_handle nnnnaaaa, to address 1234abcd.12345 nnnnaaaa indicates the internal socket ID. 1234abcd.12345 indicates the remote IP address and port number. Connection Waiting Record The connection waiting record is generated each time the socket has to wait for a connection to complete.
SCF Reference for Parallel Library TCP/IP Socket Command Records Waiting for Reply Record The waiting for reply record is generated each time an accept call is not completed immediately (that is, if the socket has to wait for an incoming connection). header listen: socket_handle nnnnaaaa waiting for reply nnnnaaaa indicates the internal socket ID. Send Record The send record is generated each time a send call is made. header send: socket_handle nnnnaaaa bbbbb nnnnaaaa indicates the internal socket ID.
SCF Reference for Parallel Library TCP/IP UDP User Request Records Socket Family Record The socket family record is generated each time a socket is created. header sock_reply: family fffff, type ttttt, proto proto fffff indicates the address family specified by the programmer in the socket call. ttttt indicates the socket type specified by the programmer in the socket call. proto indicates the IP number specified by the programmer in the socket call (either 0 for IP, 6 for TCP, or 17 for UDP).
SCF Reference for Parallel Library TCP/IP UDP User Request Records nnnnn indicates the internal request number used to manipulate the UDP socket. The possible values that can appear and their meanings are explained in the PROTOSWH INCLUDE file. UDP Socket Request Completed Record The UDP socket request completed record is generated each time a UDP socket request is completed with an error.
6 Troubleshooting Tips This section provides some conditions to check if you encounter some problems with your Parallel Library TCP/IP configuration. Review the following list for suggestions that may pertain to your configuration: • • • Check the adapter configuration and ensure that the SACs are configured with the correct Access List. Make sure that all processors running a TCPMON process are listed in the Access List.
Troubleshooting Tips pair in processors 0 and 1 and another primary and backup TELSERV pair in processors 2 and 3. • • • • • • The TCPSAM process must be in a processor that has a TCPMON running. Check to ensure that all primary and backup TCPSAM processes are configured in processors which contain a running TCPMON.
Troubleshooting Tips ZTCPSRL with the original version from the archive. The DSM/SCM ZPHIRNM log file shows the fictitious file name. This replacement does not affect the subsystem. However, if after the replacement of ZTCPSRL by DSM/SCM, either TCPSAM alone or TCPMON alone is restarted, a mismatch occurs in the version of ZTCPSRL that the TCPSAM or TCPMON is bound to. This situation could lead to a malfunction in the subsystem.
Troubleshooting Tips HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual— 522271-006 6 -4
A SCF Command Summary ABORT [ / OUT file-spec / ] MON [$ZZTCP.#ZPTMn] ABORT [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [ , SUB ALL ] ABORT [ / OUT file-spec / ] [ PROCESS $tcpsam-process-name ] ABORT [ / OUT file-spec / ] [ROUTE $ZZTCP.*.route-name ] ABORT [ / OUT file-spec / ] [SUBNET $ZZTCP.*.subnet-name] ADD [ /OUT file-spec/ ] [ ENTRY $ZZTCP.*.entry-name ] , TYPE ARP , IPADDRESS ip-addr , MACADDR mac-address ADD [ / OUT file-spec / ] [ ROUTE $ZZTCP.*.
SCF Command Summary ADD [ /OUT file-spec/ ] [ SUBNET $ZZTCP.*.subnet-name ] , TYPE ETHERNET , DEVICENAME lif-name , IPADDRESS ip-addr [ , IRDP { ON | OFF } ] [ , SUBNETMASK mask-val ] [ , FAILOVER {SHAREDIP | NON-SHAREDIP} ] ALTER [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ /OUT file-spec/ ] MON $ZZTCP.
SCF Command Summary ALTER [ /OUT file-spec/ ] [SUBNET $ZZTCP.*.subnet-name ] { [ ,IPADDRESS ip-addr ] [ ,SUBNETMASK %H0..FFFFFFFF ] [ ,IRDP { ON | OFF } ] [ ,ADDALIAS ip-addr,SUBNETMASK %H0..FFFFFFFF ] [ ,DELETEALIAS ip-addr ] } | { [ ,ASSOCIATESUB "subnet-name" ] [, RESERVEDIP ip-addr] } DELETE [ /OUT file-spec/ ] [ ENTRY $ZZTCP.*.entry-name ] DELETE [ / OUT file-spec / ] [ROUTE $ZZTCP.#ZPTMn.route-name] DELETE [/ OUT file-spec / ] [ SUBNET $ZZTCP.*.
SCF Command Summary INFO [ / OUT file-spec / ] [ ROUTE $ZZTCP.#ZPTMn.route-name | OBEYFORM ] INFO [ /OUT file-spec/ ] [ ROUTE $tcpsam-name.route-name ] INFO [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] [, DETAIL | , OBEYFORM] INFO [ / OUT file-spec / ] [ SUBNET $tcpsam-name.subnet-name ] [, DETAIL ] LISTOPENS[ /OUT file-spec/ ] [ MON $ZZTCP.#ZPTM{0-F } ] [,DETAIL ] LISTOPENS[ /OUT file-spec/ ] [ PROCESS $tcpsam-name ] [,DETAIL ] NAMES [ /OUT file-spec/ ] [ ENTRY $ZZTCP.#ZPTMn.
SCF Command Summary NAMES [ / OUT file-spec / ] [SUBNET $tcpsam-name.*] PRIMARY [ / OUT file-spec / ] [ PROCESS $ZZTCP ] , CPU cpu-number PRIMARY [ / OUT file-spec / ] [ PROCESS $tcpsam-name ] , CPU cpu-number START [ / OUT file-spec / ] MON $ZZTCP.#ZPTM{0-F } START [ / OUT file-spec / ] [ROUTE $ZZTCP.*.route-name ] START [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] STATS [ / OUT file-spec / ] [MON $ZZTCP.#ZPTMn.
SCF Command Summary STATS [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] [ , RESET ] [ , DETAIL ] STATS [ / OUT file-spec / ] [SUBNET $tcpsam-process.subnet-name] [ , RESET ] [ , DETAIL ] STATUS [ / OUT file-spec / ] [ ENTRY $ZZTCP.#ZPTMn.entry-name] STATUS [ / OUT file spec / ] [ MON $ZZTCP.#ZPTMn ] [ , DETAIL ] STATUS [ / OUT file spec / ] [ PROCESS $ZZTCP ] STATUS [ / OUT file spec / ] [ PROCESS $tcpsam-name ] [, DETAIL] STATUS [ / OUT file spec / ] [ROUTE $ZZTCP.#ZPTMn.
SCF Command Summary STATUS [ / OUT file spec / ] [SUBNET $tcpsam-name.#subnet-name] STOP [ /OUT file-spec/ ] MON $ZZTCP.#ZPTMn STOP [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [, SUB ALL ] STOP [ / OUT file-spec / ] [ PROCESS $tcpsam-name ] STOP [ / OUT file-spec / ] [ROUTE $ZZTCP.#ZPTMn.route-name ] STOP [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] TRACE [ /OUT file-spec/ ] MON [ $ZZTCP.
SCF Command Summary TRACE [ /OUT file-spec/ ] PROCESS $tcpsam-name { , STOP [ , BACKUP ] } | { [ , TO file-spec [ , BACKUP ] [ , COUNT count ] [ , NOCOLL ] [ , RECSIZE size ] [ , PAGES pages ] ] TRACE [/OUT file-spec/] [SUBNET $ZZTCP.#ZPTMn.subnet-name] {, STOP } | {, TO file-spec [ [ [ [ [ , NOBULKIO , COUNT count , NOCOLL , RECSIZE size , SELECT select-spec , PAGES pages ] ] ] ] ] VERSION [ /OUT file-spec/ ] [ MON $ZZTCP.#ZPTMn.
B SCF Error Messages This appendix contains a description of the PTCPIP subsystem SCF error messages. For the operator display of event messages, see the Operator Messages Manual. PTCPIP 00001 PTCPIP 00001 Invalid file name. Cause. You specified a file with an invalid format. Effect. The command is not executed. Recovery. Verify the file-name format and retry the command. PTCPIP 00002 PTCPIP 00002 INTERNAL ERROR: Case value out of range. Cause.
PTCPIP 00005 SCF Error Messages PTCPIP 00005 PTCPIP 00005 Attribute value out of range attribute-name. attribute-name is the name of the attribute you specified in an ALTER PROCESS command. Cause. You specified a value for the ALTER PROCESS command that is outside the valid range. Effect. The command is not executed. Recovery. Enter a valid range for the command and retry it. Refer to the ALTER command in Section 5, SCF Reference for Parallel Library TCP/IP, for more information on valid ranges.
PTCPIP 00010 SCF Error Messages PTCPIP 00010 PTCPIP 00010 SNAP MTU not available. Cause. TCP/IP cannot communicate with the manager process to obtain the MTU size. Effect. The command is not executed. Recovery. Check or start the manager process. PTCPIP 00011 PTCPIP 00011 Invalid IP address. Cause. The IP address is invalid. Effect. The command is not executed. Recovery. Use a correct IP address. PTCPIP 00012 PTCPIP 00012 Invalid CPU number. Cause. The processor number is invalid. Effect.
PTCPIP 00016 SCF Error Messages Effect. The command is not executed. Recovery. Use the RECSIZE parameter while starting a trace. When a larger trace record size is used, there is less chance of trace records being truncated. PTCPIP 00016 PTCPIP 00016 Primary not allowed, some subnets still in STARTED state. Cause. This occurs when a Primary command is rejected because at least one subnet is still in the started state and switching to another CPU. This takes any started subnets out of service. Effect.
SCF Error Messages PTCPIP 00020 Effect. The command is not executed. Recovery. Select a device that is available or correct the problem. PTCPIP 00020 PTCPIP 00020 The Device selected for the subnet returned a NULL MAC address. Cause. The device selected for the subnet returned a NULL MAC address. Effect. The command is not executed. Recovery. Try the operation again. PTCPIP 00022 PTCPIP 00022 Invalid MAC address. Cause. MAC address is invalid. Effect. The command is not executed. Recovery.
SCF Error Messages PTCPIP 00036 PTCPIP 00036 PTCPIP 00036 The subnet intended to be used for FAILOVER is not configured. Cause. The subnet intended to be used for failover is not configured. Effect. The command is rejected with the reason. Recovery. Configure the subnet associated with the error and re-issue the command. PTCPIP 00037 PTCPIP 00037 The command issued to configure FAILOVER is not valid. Cause. The command issued to configure failover is not valid.
SCF Error Messages PTCPIP 00040 PTCPIP 00040 PTCPIP 00040 The command is not valid for FAILOVER enabled subnet. Cause. The command is invalid in the failover-enabled subnet. Causes include: • • • For a failover-enabled subnet, the ADDALIAS is not allowed until the subnet is associated with another subnet as a failover pair. For a failover-enabled subnet, the DELETEALIAS is not allowed. For a failover-enabled subnet, the ALTER subnet, IPADDDRESS or ALTER subnet, SUBNETMASK command is not allowed.
SCF Error Messages PTCPIP 00040 HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual— 522271-006 B- 8
C Tracer Utility The Tracer Utility displays the path taken by IP packets enroute to a network host. Use the Tracer Utility to determine any problems that these packets might encounter. From each gateway system along the path, the Tracer Utility attempts to elicit an ICMP TIME_EXCEEDED message. From the destination remote host, it attempts to elicit a ICMP_PORT_UNREACHABLE message. Running the Tracer Utility from a Terminal You can use Tracer Utility only if your user ID is SUPER.SUPER.
Running the Tracer Utility from a Terminal Tracer Utility [ -n ] specifies that the address of each gateway be printed numerically rather than both symbolically and numerically. Thus, only the IP address, rather than the address and gateway name, appears in the output. Specifying -n avoids having the Tracer Utility do a time-consuming address-to-name lookup. HP recommends use of this option. [ -p port-num ] specifies the base UDP port number used in probes.
Tracer Utility Running the Tracer Utility from a Terminal [ -v ] specifies verbose output. If you specify this option, all received ICMP packets are listed. If you do not specify this option, only the ICMP packets TIME_EXCEEDED and UNREACHABLE are listed. [ -w wait-time ] specifies the time, in seconds, that the Tracer Utility waits for a response to a probe. If you do not specify this option, the Tracer Utility uses the default value of 5 seconds for wait-time.
Tracer Utility Running the Tracer Utility from a Terminal HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual— 522271-006 C- 4
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 mask. A bit mask used to select bits from an Internet address for subnet addressing. The mask is 32 bits long and selects the network portion of the Internet address and one or more bits from the local portion. address resolution. Conversion of an Internet address into a corresponding physical address.
baseband Glossary one gateway in an autonomous system must advertise networks in that system to a core gateway using EGP. baseband. Characteristic of any network technology (like Ethernet) that uses a single carrier frequency and requires all stations attached to the network to participate in every transmission. See broadband. bridge. A router that connects two or more networks and forwards packets among them. Usually, bridges operate at the physical network level.
Class D Glossary host connected to the subnetwork. LANs connected by way of a gateway to the 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.
control and inquiry Glossary subsystem sends a response message that does not contain a context token, the series of response messages is complete. control and inquiry. In DSM, those aspects of object management that affect the state or configuration of an object, such as inquiries about the object and commands pertaining to the environment (for example, commands that set default values for the session). Compare event management. critical event.
Distributed Systems Management Glossary oriented programmatic interface has one definition file for DDL and one for each programming language. Some subsystems—for instance, data communications subsystems—have additional, shared definition files. See also SPI standard definitions, data communications standard definitions, or EMS standard definitions. Distributed Systems Management. A set of tools used to manage NonStop systems and EXPAND networks.
error Glossary error. In DSM interfaces, a condition that causes a command or other operation to fail. Contrast Warning. error list. In DSM programmatic interfaces, a group of tokens used within a response record to provide error and warning information. An error list consists of a list token that denotes an error list (different from the token that starts a data list or a generic list), followed by an error token, other tokens explaining the error (optional), and an end-list token.
event management Glossary interactive and programmatic interfaces, lets an operator or application select specific event-message data, and allows for the flexible distribution of event messages within a system or network. EMS has an SPI-based programmatic interface for both reporting and retrieving events. See also DSM or event message. event management.
Fiber Distribution Data Interface (FDDI) Glossary 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. The access control mechanism uses token-ring technology. File Transfer Protocol (FTP). The Internet standard, high-level protocol for transferring files from one machine to another.
GGP Glossary GGP. See Gateway to Gateway Protocol. Gigabit Ethernet 4-port ServerNet Adapter (G4SA). A multiport ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop S-series systems and Ethernet LANs. The G4SA is the only LAN adapter supported for the I/O Adapter Module (IOAM) enclosure, and it is installed in slots 1, 2, 3, 4, and 5 of an IOAM.
hop count Glossary datagram reaches a gateway that can deliver it directly. Subnetting introduces additional levels of hierarchical routing. hop count. A measure of distance between two points in the Internet. A hop count of n means that n gateways separate the source destination. 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.
Internet address Glossary Internet address. The 32-bit address assigned to hosts that want to participate in the Internet using TCP/IP. Internet addresses are the abstraction of physical hardware addresses, just as the Internet is an abstraction of physical networks. Actually assigned to the interconnection of a host to a physical network, an Internet address consists of a network portion and a host portion. The partition makes routing efficient. Internet Control Message Protocol (ICMP).
LAN monitor (LANMON) process. Glossary LAN monitor (LANMON) process. The process provided as part of the ServerNet local area network (LAN) systems access (SLSA) subsystem that has ownership of the Ethernet adapters controlled by the SLSA subsystem. LAPB (Link Access Protocol —Balanced). ITU-T standards that define in the Data Link Layer the requirements for X.25 connections over wide area networks (WANs). Level 2.
manager process Glossary manager process. In DSM, an HP subsystem process with which the SCP management process communicates to control a particular data communications subsystem. Media Access Control (MAC) Address. A MAC address is 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. MFIOB. See multifunction I/O board (MFIOB). MILNET (Military Network).
object Glossary before returning control to the caller. In order to make the called procedure wait for the completion of the operation, the application calls a separate procedure. Compare wait mode. object. (1) In general HP use, one or more of the devices, lines, processes, and files in a NonStop subsystem; any entity subject to independent reference or control by one or more subsystems.
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 PING. predefined value.
return token Glossary record can also contain error lists that include error tokens. A response can consist of multiple response records, spread across one or more response messages. A response record cannot be split between two response messages. If multiple response records are in a response message, each response record is enclosed in a data list. See also data list. Each response record is required to contain a return token. See also return token. return token.
service Glossary service. A set of primitives (operations) that a layer provides to the layer above it. The service defines what operations the layer can perform on behalf of its users, but not how these operations are implemented. A service relates to an interface between two layers: the lower layer is the service provider, and the upper layer is the service user. Compare protocol. session. For a management application, the period during which an application can issue commands to a subsystem.
Glossary subject token communicates. See also definition. Compare data communications standard definitions or EMS standard definitions. subject token. In event management, a device, process, or other named entity about which a given event message has information. subnet address. An extension of the Internet addressing scheme that allows a site to use a single Internet address for multiple physical networks.
Subsystem Programmatic Interface (SPI) Glossary Subsystem Programmatic Interface (SPI). In DSM, a set of procedures and associated definition files used to define common message-based programmatic interfaces for communication between requesters and servers—for instance, in a management application.
token ring Glossary token ring. 1)þþThe token access procedure used on a network with a sequential or ring topology. (2) A data link level protocol designed to transfer data over ring-oriented LANs. The token ring technique is based on the use of a particular bit pattern called a token that circulates around the ring when all stations are idle. token type. In DSM programmatic interfaces, the part of a DSM token code that identifies the data type and length of the token value.
Warning Glossary 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. Any of a set of protocol ports preassigned for specific uses by transport level protocols (that is, TCP and UDP). Servers follow the well-known port assignments so clients can locate them.
Glossary See WAN manager process.
Index A ABORT command LISTNER, not supported 1-32 MON, example 1-28 MON, specification 5-12 MON, summary A-1 PROCESS, example 1-23, 1-28 ROUTE, specification 5-15 ROUTE, summary A-1 SUBNET, example 1-14 SUBNET, specification 5-16 SUBNET, summary A-1 TCPMAN process, specification 5-13 TCPMAN process, summary A-1 TCPSAM process 1-32 TCPSAM process, specification 5-14 TCPSAM process, summary A-1 TELSERV, not supported 1-32 Access list 6-1 ACK Predictions OK 5-100 ADD command DEFINE, HOSTS file 1-9, 1-17 DEFINE
B Index B Backup CPU configuring 2-5, 3-14, 3-18, 3-20 distributor 3-20 LISTNER 3-14 TELSERV 3-18 Backward-compatibility 2-11 Bad checksum attribute 5-88, 5-106 Bad ICMP code attribute 5-88, 5-107 Bad ICMP packets attribute 5-88, 5-107 Bad router ADDR list attribute 5-88, 5-107 Bad router ADV subcode attribute 5-88, 5-107 Bad router words/ADDR attribute 5-89, 5-107 Balancing, load 3-1 Berkeley software design 2-16 Binding, subnet-level 2-6 BSD 4.
D Index Configuring backup processors 2-5 Ethernet failover 2-8/2-9 master TCPMON 2-10 primary processors 2-5 round-robin, caution 2-5 Connections, incoming distribution 2-4 Considerations for listening processes 2-5 UDP port 2-6 Context, maintaining, caution 2-6 Conventional TCP/IP coexistence 2-1 coexistence with 4-1 data path 2-9 definition 2-1 differences, where to find 2-1 distributor listening model definition 3-6 distributor listening model figure 3-8 hybrid listening model definition 3-9 message-s
E Index DEVICENAME attribute 5-22 description of 3-26 G-series considerations 5-24 Display example INFO PROCESS 5-36, 5-39, 5-44 INFO SUBNET 5-56, 5-59 LISTOPENS MON 5-61 LISTOPENS PROCESS 5-64 NAMES ROUTE 5-67 NAMES SUBNET 5-69 STATS PROCESS 5-77 STATS ROUTE 5-116, 5-118 STATS SUBNET 5-119, 5-122 STATUS PROCESS 5-129 STATUS ROUTE 5-134 STATUS SUBNET 5-136, 5-138 VERSION 5-154, 5-155 Distributed Systems Management 2-12 Distribution caution for UDP ports 2-6 incoming requests 2-3 of connections 3-6 of conn
G Index Fast Ethernet ServerNet adapter (FESA) sharing 4-1 support 2-1 FESA See Fast Ethernet ServerNet adapter (FESA) File already exists, error 1-21 Filter inbound frames and 2-11 key, round-robin 2-5 Filter Errors statistic 5-120, 5-123 Filter Timeout statistic 5-120, 5-123 Finger, determining name of opener 1-21 FINGSERV 3-25 FIN-WAIT-1 socket state 5-127 FIN-WAIT-2 socket state 5-127 Firewall workaround 5-24 Formats trace record header 5-164 trace records detailed UDP input records 5-177 interprocess
I Index HOSTS command file 3-28 HOSTS file altering 3-28 defining 1-9, 1-17 Hybrid listening model definition 3-9 figure 3-10 I ICMP 2-11 ICMP Router Discovery Protocol 5-22 identifying name of 2-16 In ARP Requests 5-113 In ARP requests attribute 5-95 In dest unreachable attribute 5-89, 5-107 In echo attribute 5-89, 5-108 In echo reply attribute 5-89, 5-108 In info reply attribute 5-89, 5-108 In info request attribute 5-90, 5-108 In parameter problem attribute 5-90, 5-108 In redirect attribute 5-90, 5-10
M Index LIF definition 2-1 determining name of 1-4, 1-11 in hybrid listening model 3-10 sharing 4-1 LISTDEV 1-4, 1-16, 1-19, 1-22, 1-27, 1-32, 2-16 LISTEN socket state 5-127 Listening models 3-2 distributor, definition 3-6 distributor, figure 3-8 hybrid, definition 3-9 hybrid, figure 3-10 monolithic 3-4 monolithic, figure 3-5 standard, configuration example 3-11 standard, figure 3-12 standard, startup file 3-13 Listening processes distribution among 2-4 distributor 3-6 hybrid 3-9 monolithic 3-4 port colli
N Index Media state attribute 5-137 Media state down attribute 5-121 Memory buffer allocation records 5-168 Memory management 2-13 Message system 2-14 Message system hop 2-10 Messages, context maintenance for, caution 2-6 Message-system hop 2-1 Migration, transparency 2-6 MIN-EPHEMERAL-PORT attribute 5-29, 5-42 MON definition 5-4 names 5-4 object 5-4 object type 5-4 Monolithic listening model definition 3-4 figure 3-5 Multicast groups 5-57, 5-128 Multicast groups attribute 5-133 N Name attribute 5-37 NAM
P Index Openers of TCPMONs 1-21, 1-26 of TCPMONs, stopping 1-28 of TCP/IP process 1-21, 1-25 Operator messages B-1 OSIMAGE file 2-12 Out dest unreachable attribute 5-91, 5-110 Out echo attribute 5-91, 5-110 Out echo reply attribute 5-91, 5-110 Out info reply attribute 5-92, 5-110 Out info request attribute 5-92, 5-110 OUT parameter in RUN command 1-8, 3-13 to file 5-13 Out parameter problem attribute 5-92, 5-110 Out redirect attribute 5-92, 5-110 Out source quench attribute 5-92, 5-110 Out time exceeded a
Q Index Parallel Library TCP/IP (continued) standard listening model startup file 3-13 startup files for standard listening model 3-11 throughput 2-2 transparency for existing applications 2-6 Parallel, definition 3-1 PARAM adding 1-14 clearing 1-8, 1-17 clearing all 1-17 Password, filter key 2-5 PATHSEND 3-6 Pathway 3-6, 3-9 Path-length reduction 2-1, 2-11 Persistence manager and system configuration database 2-15 function 4-3 starting using 1-18 Physical port, definition 2-1 PIF definition 2-1 distribut
R Index QIO limit warnings attribute 5-94, 5-112 QIO memory space 2-13 QIOMON, determining if running 1-3, 1-11, 1-16 QIO, determining where it runs in flat memory segment 2-13 QIO, reserved segment 2-12 QIO, use of 2-11 Quick start, configuration 1-1/1-32 R Recording and displaying trace data 5-155 RecvQ attribute 5-128 Reflect packets attribute 5-91, 5-110 Requests incoming 2-3 latency reduction 2-2 processing speed 2-2 Reserved names for ROUTEs 5-7 LOOP0 5-7 #ZPTM 5-7 $ZZTCP 5-7 RESERVEDIP attribute 5
S Index SCF commands (continued) PRIMARY 5-70 START 5-72 STATS 5-75, 5-115 STATUS 5-123 STOP 5-139 TCPSAM 5-130 TRACE 5-143 VERSION 5-152 SCFSBNT command file 3-15 SCFSBNT2 command file 3-26 SCP 2-14 SECONDARYROUTES attribute 5-134 SEL and SUM options, not supported by TCP/IP 5-11 SELECT command 5-161 SendQ attribute 5-128 Sensitive commands 5-11 ABORT 5-12 ADD 5-17 ALTER 5-25 DELETE 5-33 PRIMARY 5-70 START 5-72 STATS command with RESET option 5-75 STOP 5-139 TRACE 5-143 ServerNet 2-1 shared PIFs 2-2 use
S Index Standard listening model configuration example 3-11 definition 3-2 figure 3-3, 3-12 startup file 3-13 START command MON, example 1-8 MON, specification 5-72 MON, summary A-5 PROCESS, example 1-18 ROUTE, example 1-14, 3-26 ROUTE, specification 5-73 ROUTE, summary A-5 SUBNET, example 1-14, 3-26 SUBNET, specification 5-74 STARTED, multicast state 5-129, 5-133 Starting LISTNER 1-14 loopback 1-8 TCPMAN 1-8 TCPMON 1-8 TELSERV 1-14 using DNS 1-10/1-15 using HOSTS file 1-3/1-10 using persistence manager 1
T Index Stopping generic process 1-29/1-32 openers of TCPMON 1-28 preserving configuration 1-19/1-23 without preserving configuration 1-24/1-28 SUBNET and system configuration database 2-15 attribute 5-35 definition 5-5 maximum configurable 2-7, 5-23 names 5-5 object type 5-2, 5-6 starting 3-11 Subnet mask 3-27 SUBNETMASK attribute 5-30 Subnet-level binding 2-4 Subnet-level binding, and applications 2-6 Subsystem name PTCPIP 2-1 TCPIP 2-1 Summary states 5-8 SUPER.
T Index TCPIP^PROCESS^NAME adding 1-14, 1-17 deleting 1-8, 1-17 TCPLIB 2-9, 2-10 TCPMAN ABORT command 5-13 checking if generic process 1-18 definition 2-10 determining if running 1-4, 1-16, 1-19 INFO command 5-43 master, assignment 2-10 object types supported by 5-2 PRIMARY command 5-70 product module 2-9 SCF object hierarchy 5-3 starting 1-8 STATUS command 5-129 STOP command 5-140 TRACE command 5-145 VERSION command 5-153 TCPMON definition 2-11 determining if running 1-19 determining openers of 1-21, 1-2
U Index Testing, running Parallel Library TCP/IP 1-15 TEXT command 5-163 TIME-WAIT socket state 5-128 Token ring support 2-1 Token-ring, restriction 2-16 Total MBUFs allocated attribute 5-94, 5-112 TRACE command MON, specification 5-143 MON, summary A-7 SUBNET, specification 5-150 SUBNET, summary A-8 TCPMAN process, specification 5-145 TCPMAN process, summary A-7 TCPSAM process, specification 5-148 TCPSAM process, summary A-8 Trace filename attribute 5-41 Trace record formats detailed UDP input records 5-
Special Characters Index Special Characters #LOOP0 5-6 #ZPTMx 5-7 $SYSTEM.SYSTEM.TACLLOCL 1-9 $SYSTEM.ZTCPIP.HOSTS 3-25 $SYSTEM.ZTCPIP.PORTCONF 3-25 $ZHOME 1-8, 3-13 $ZM 1-3, 1-11, 1-16 $ZNET 1-3, 1-10, 1-16 $ZPM 2-15 $ZTCx 5-4 $ZZKRN.#ZZTCP 1-18 $ZZLAN 1-4, 1-11, 1-16 $ZZTCP 5-7 $ZZTCP.
Index Special Characters HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual— 522271-006 Index -18
