HP NonStop TCP/IPv6 Configuration and Management Manual Abstract This manual describes how to configure and manage the HP NonStop™ TCP/IPv6 subsystem on HP NonStop S-series servers and HP Integrity NonStop NS-series servers. Product Version NonStop TCP/IPv6 G06, and H01 Supported Release Version Updates (RVUs) This publication supports G06.29 and all subsequent G-series RVUs, H06.03 and all subsequent H-series RVUs, and J6.
Document History Part Number Product Version Published 524523-005 NonStop TCP/IPv6 G06 September 2004 524523-006 NonStop TCP/IPv6 G06 March 2005 524523-007 NonStop TCP/IPv6 G06 and H01 July 2005 524523-008 NonStop TCP/IPv6 G06 and H01 October 2005 524523-009 NonStop TCP/IPv6 G06 and H01 January 2007 524523-012 NonStop TCP/IPv6 G06 and H01 May 2012
Legal Notices © Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
HP NonStop TCP/IPv6 Configuration and Management Manual Glossary Index Examples Figures Tables Legal Notices What’s New in This Manual xiii Manual Information xiii New and Changed Information xiii About This Manual xvii Who Should Use This Manual xvii How to Use This Manual xvii Required Background xviii NonStop TCP/IPv6 Core Manuals xix Background Manuals and Prerequisite Materials Notation Conventions xxii xx 1. Quick Start I. Prepare to Install and Configure NonStop TCP/IPv6 1-1 1.
2. Overview of NonStop TCP/IPv6 Contents Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Ethernet Failover, Nonshared IP 1-17 Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Configured Tunneling 1-18 IVA. Prepare to Start the Applications (Without LNP) 1-20 IVB. Prepare to Start the Applications (With LNP) 1-20 VA. Start the Applications (Without LNP) 1-21 VB. Start the Applications (With LNP) 1-21 VI. Add More Features 1-23 2.
4. Plan Your IPv6 Implementation Contents Distributor Listening Model 3-6 Hybrid Listener Model 3-9 Broker Listener Model 3-10 Configuration Examples for the Listening Models 3-12 Configuration Example for the Standard Listening Model 3-12 Configuration Example for the Monolithic Listening Model 3-14 Configuration Example for the Distributor Listening Model 3-17 Configuration Example for the Hybrid Listening Model 3-19 4.
Contents 7.
Contents 8.
Contents 8.
A.
B. SCF Command Summary Contents Address Assignment A-9 Aggregatable Global Unicast Address Format A-9 Aggregatable Testing Address Format A-10 Stateless Address Autoconfiguration A-11 Address Lifetimes A-12 Stateless Address Autoconfiguration Behavior A-12 Neighbor Discovery Protocol A-13 How IPv6 Tunnels Work A-18 B. SCF Command Summary C. SCF Error Messages D.
Glossary Contents Domain Name Resolver E-3 Glossary Index Examples Example 1-1. Example 1-2. Example 1-3. Example 1-4. Example 1-5. Example 1-6. Example 1-7. Example 1-8. Example 1-9. Example 1-10. Example 2-1. Example 2-2. Example 3-1. Example 3-2. Example 3-3. Example 3-4. Example 6-1. Example 6-2. Example 6-3. Example 6-4. Example 8-1. Example 8-2. Example 8-3. Example 8-4. Example 8-5.
Figures Contents Example 8-6. Shared IP Ethernet Failover, DUAL Mode 8-58 Figures Figure i. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 2-8. Figure 2-9. 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 4-1. Figure 4-2. Figure 4-3. Figure 5-1. Figure 5-2. Figure 5-3. Figure 5-4.
Tables Contents Figure 5-5. Figure 6-1. Figure 8-1. Figure 8-2. Figure 8-3. Figure A-1. Figure A-2. Figure A-3. Figure A-4. Figure A-5. Figure A-6. Figure A-7. Figure A-8. Figure A-9. Figure A-10. Figure D-1. Figure D-2.
Contents HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 xii
Contents HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 xiii
What’s New in This Manual Manual Information HP NonStop TCP/IPv6 Configuration and Management Manual Abstract This manual describes how to configure and manage the HP NonStop™ TCP/IPv6 subsystem on HP NonStop S-series servers and HP Integrity NonStop NS-series servers. Product Version NonStop TCP/IPv6 G06, and H01 Supported Release Version Updates (RVUs) This publication supports G06.29 and all subsequent G-series RVUs, H06.03 and all subsequent H-series RVUs, and J6.
What’s New in This Manual Changes in the G06.30 manual: Added additional information about STATUS PROC command on page 8-2. Added additional information about TRACE SUBNET commands, Tracing a single SUBNET on page 8-207, Tracing multiple SUBNETs on page 8-207, and Tracing all the SUBNETs on page 8-208. Added additional information about TRACE SUBNET command usage on page 8-208. Added additional consideration information about ALTER SUBNET, ASSOCIATESUB command on page 8-59. Changes in the G06.
What’s New in This Manual Changes in the October 2005 Revision of the Manual Updated the SCF error messages TCPIPV6 00047 on page C-8, TCPIPV6 00048, TCPIPV6 00049, TCPIPV6 00050 on page C-9, TCPIPV6 00051, TCPIPV6 00052, and added the error message TCPIPV6 00053 on page C-10 Changes in the October 2005 Revision of the Manual Changed the description of the INFO SUBNET command for TCP6MAN with the OBEYFORM option under INFO SUBNET Command for TCP6MAN on page 8-89.
What’s New in This Manual Changes in the G06.26 and H06.03 Manual Corrected the text under IVA. Prepare to Start the Applications (Without LNP) on page 1-20. Reorganized the Section 2, Overview of NonStop TCP/IPv6 to make architectural topics more visible.
About This Manual This manual describes how to configure and manage the NonStop TCP/IPv6 subsystem. NonStop TCP/IPv6, when run in INET mode, is a direct replacement for Parallel Library TCP/IP. Note. Parallel Library TCP/IP is not supported on the Integrity NonStop NS-series server. Who Should Use This Manual System and network managers, operators, and others who configure and manage the NonStop TCP/IPv6 subsystem should use this manual.
Required Background About This Manual Section Overview Section 6, Manage the NonStop TCP/IPv6 Subsystem Provides information about management topics such as online software replacement, managing the configuration database, and fallback procedures. Section 7, Troubleshooting Tips for NonStop TCP/IPv6 Provides tips for solving common problems encountered when configuring NonStop TCP/IPv6.
NonStop TCP/IPv6 Core Manuals About This Manual NonStop TCP/IPv6 Core Manuals You should use this manual along with the TCP/IPv6 Migration Guide and, if you program applications to the sockets library, the TCP/IP Programming Manual, the Open System Services System Calls Reference Manual, and the Open System Services System Calls Library Calls Reference Manual. These are the core manuals for NonStop TCP/IPv6.
About This Manual NonStop TCP/IPv6 Application and Client Manuals NonStop TCP/IPv6 Application and Client Manuals The applications that are directly related to NonStop TCP/IPv6 are described in the TCP/IP Applications and Utilities User Guide. In addition, the Expand communications product, the ServerNet wide area network (SWAN) subsystem, and the iTP WebServer are clients of the NonStop TCP/IPv6 subsystem.
About This Manual NonStop S-Series System Configuration Manuals The TCP/IP Configuration and Management Manual provides some background information about TCP/IP fundamentals and complete information on the NonStop TCP/IP product. Introduction to Networking for HP NonStop S-Series Servers provides an overview of HP networking and data communications concepts, tasks, products, and manuals.
About This Manual Other Related Manuals Other Related Manuals The Interactive Upgrade Guide 2 provides migration considerations and highlights pertaining to G-series and H-series RVUs. The G06.nn Software Installation and Upgrade Guide and the H06.nn Software Installation and Upgrade Guide provide information about installing certain required files such as the PROTOCOL configuration file. The G06.nn Release Version Update Compendium and the H06.
About This Manual General Syntax Notation [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on 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 { } Braces.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
1 Quick Start This manual documents NonStop TCP/IPv6 only; it does not document Parallel Library TCP/IP. However, if you configure NonStop TCP/IPv6 in INET mode, NonStop TCP/IPv6 is a direct replacement for Parallel Library TCP/IP. This section provides examples for starting NonStop TCP/IPv6 in INET and DUAL modes.
2. Prepare to Install and Configure the Subsystem Quick Start TCP/IP (Parallel Library) Configuration and Management Manual, which has a procedure for stopping Parallel Library TCP/IP as a generic process. Note. Issue the SCF LISTDEV TCPIPV6 and LISTDEV PTCPIP commands to determine if either subsystem is running. (Parallel Library TCP/IP is not supported on Integrity NonStop servers.) You are running as user SUPER.SUPER. 2.
IIA. Install NonStop TCP/IPv6 (#ZZTCP is not in the Configuration Database) Quick Start e. Check if the TCP6MAN process has been added as a generic process to the system configuration database by entering this command at the SCF prompt. (If ZZTCP has not been added as a generic process, perform IIA. Install NonStop TCP/IPv6 (#ZZTCP is not in the Configuration Database) on page 1-3 for your installation step. If ZZTCP has been added as a generic process, perform IIB.
IIB. Install NonStop TCP/IPv6 (#ZZTCP is in the Configuration Database) Quick Start You should see a display like this: *AutoRestart...............0 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................Not Specified *Library...................Not Specified *MemPages..................Not Specified *Name................
IIIA. Configure the NonStop TCP/IPv6 Subsystem for INET Mode Quick Start 2. Check that $ZZTCP has been added to the system configuration database by entering this SCF command: ->INFO PROCESS $ZZKRN.#ZZTCP, DETAIL You should see a display like this: *AutoRestart...............0 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile........
Configure the Subsystem for INET-Mode, Ethernet Failover, and Shared IP Quick Start 2. Create the TCPIPUP command file: Example 1-1. TCPIPUP1 Command File, INET-Mode CLEAR ALL SCF/INLINE/ INLPREFIX + + ASSUME PROCESS $ZZTCP + START MON * + DELAY 30 == Configure the loopback subnet == + ABORT SUBNET LOOP0 + ALTER SUBNET LOOP0, IPADDRESS 127.1 + START SUBNET LOOP0 == Add Host Id and Host Name information (optional) + ALTER MON *, HOSTID 172.14.215.27, HOSTNAME "www.company.
Configure the Subsystem for INET-Mode, Ethernet Failover, and Shared IP Quick Start 2. Create the TCPIPUP command file: Note. Before following any of these procedures, you must have real values for the variables in the examples (indicated with italics). Example 1-2. TCPIPUP2 Command File, INET-Mode, Ethernet Failover Shared IP CLEAR ALL SCF/INLINE/ INLPREFIX + + ASSUME PROCESS $ZZTCP + START MON * + DELAY 30 == Configure the loopback SUBNET == + ABORT SUBNET LOOP0 + ALTER SUBNET LOOP0, IPADDRESS 127.
Configure the Subsystem for INET-Mode, Ethernet Failover, and Nonshared IP Quick Start Configure the Subsystem for INET-Mode, Ethernet Failover, and Nonshared IP 1. Find two LIFs for communication by following the procedure Select a LIF of TYPE ETHERNET for communications. on page 1-2. 2. Create the TCPIPUP command file: Note. Before following any of these procedures, you must have real values for the variables in the examples (indicated with italics). Example 1-3.
Configure the Subsystem for INET Mode With LNP Quick Start 4. Go to IVA. Prepare to Start the Applications (Without LNP) on page 1-20. Configure the Subsystem for INET Mode With LNP 1. Find multiple LIFs for communication by following the procedure Select a LIF of TYPE ETHERNET for communications. on page 1-2. (This example uses three LIFs.) 2. Create the TCPIPUP command file: Note.
Configure the Subsystem for INET Mode, Ethernet Failover, and Shared IP, With LNP Quick Start 1. Issue the TACL OBEY command on the TCPIPUP command file while running as the super ID user: >OBEY TCPIPUP4 2. Go to IVB. Prepare to Start the Applications (With LNP) on page 1-20. Configure the Subsystem for INET Mode, Ethernet Failover, and Shared IP, With LNP 1. Find two LIFs for communication by following the procedure Select a LIF of TYPE ETHERNET for communications. on page 1-2. 2.
Quick Start Configure the Subsystem for INET Mode, Ethernet Failover, and Shared IP, With LNP Example 1-5. TCPIPUP5 Command File, INET-Mode, Ethernet Failover, Shared IP, with LNP CLEAR ALL SCF/INLINE/ INLPREFIX + + ASSUME PROCESS $ZZTCP + START MON * + DELAY 30 == Configure the loopback SUBNET == + ABORT SUBNET LOOP0 + ALTER SUBNET LOOP0, IPADDRESS 127.1 + START SUBNET LOOP0 == Add Host Id and Host Name information (optional) + ALTER MON *, HOSTID 172.14.215.27, HOSTNAME "www.company.
Configure the Subsystem for INET-Mode, Ethernet Failover, Non-Shared IP, With LNP Quick Start 3. Issue the TACL OBEY command on the TCPIPUP command file while running as the super ID user: >OBEY TCPIPUP5 4. Go to IVA. Prepare to Start the Applications (Without LNP) on page 1-20. Configure the Subsystem for INET-Mode, Ethernet Failover, Non-Shared IP, With LNP 1. Find two LIFs for communication by following the procedure Select a LIF of TYPE ETHERNET for communications. on page 1-2. 2.
Quick Start Configure the Subsystem for INET-Mode, Ethernet Failover, Non-Shared IP, With LNP Example 1-6. TCPIPUP6 Command File, INET Mode, Ethernet Failover, Non-Shared IP, with LNP CLEAR ALL SCF/INLINE/ INLPREFIX + + ASSUME PROCESS $ZZTCP + START MON * + DELAY 30 == Configure the loopback SUBNET == + ABORT SUBNET LOOP0 + ALTER SUBNET LOOP0, IPADDRESS 127.1 + START SUBNET LOOP0 == Add Host Id and Host Name information (optional) + ALTER MON *, HOSTID 172.14.200.27, HOSTNAME "www.company.
IIIB. Configure the NonStop TCP/IPv6 Subsystem for DUAL Mode Quick Start 3. Issue the TACL OBEY command on the TCPIPUP command file while running as the super ID user: >OBEY TCPIPUP6 4. Go to IVA. Prepare to Start the Applications (Without LNP) on page 1-20. IIIB. Configure the NonStop TCP/IPv6 Subsystem for DUAL Mode These procedures show you how to configure the NonStop TCP/IPv6 subsystem in DUAL mode and include examples for failover configurations and configured tunneling.
Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Ethernet Failover, Shared IP Quick Start Example 1-7. TCPIPUP7 Command File, DUAL-Mode, Address Autoconfiguration CLEAR ALL SCF/INLINE/ INLPREFIX + + ASSUME PROCESS $ZZTCP + START MON * + DELAY 30 == Configure the loopback SUBNET == + ABORT SUBNET LOOP0 + ALTER SUBNET LOOP0, IPADDRESS 127.1 + START SUBNET LOOP0 + ALTER MON *, FAMILY DUAL == Add Host Id and Host Name information (optional) + ALTER MON *, HOSTID 172.14.200.
Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Ethernet Failover, Shared IP Quick Start 2. To bring up the SUBNETs, create the TCPIPUP command file: Note. Before following any of these procedures, you must have real values for the variables in the examples (indicated with italics). Example 1-8.
Quick Start Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Ethernet Failover, Nonshared Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Ethernet Failover, Nonshared IP This example provides the same features as Example 1-7 on page 1-15, with the addition of Ethernet failover with nonshared IP addresses.
Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Configured Tunneling Quick Start Example 1-9. TCPIPUP9 Command File, DUAL-Mode With Address Autoconfiguration and Ethernet Failover, Nonshared IP CLEAR ALL SCF/INLINE/ INLPREFIX + + ASSUME PROCESS $ZZTCP + START MON * + DELAY 30 + ALTER MON *, FAMILY DUAL == Configure the loopback subnet == + ABORT SUBNET LOOP0 + ALTER SUBNET LOOP0, IPADDRESS 127.
Configure the Subsystem for DUAL-Mode, Address Autoconfiguration and Configured Tunneling Quick Start (defined by the attribute IPTSRC) must be an IPv4 address belonging to a SUBNET on your system. In this example, IPTSRC is the IP address of SUBNET SN3. 1. Find a LIF for communication by following the procedure Select a LIF of TYPE ETHERNET for communications. on page 1-2. 2. Create the TCPIPUP command file: Note.
IVA. Prepare to Start the Applications (Without LNP) Quick Start 3. Issue the TACL OBEY command on the TCPIPUP command file while running as the super ID user: >OBEY TCPIPUPA 4. Go to IVA. Prepare to Start the Applications (Without LNP). IVA. Prepare to Start the Applications (Without LNP) Applications that use NonStop TCP/IPv6 require a TCP6SAM process to use instead of a NonStop TCP/IP process. This subsection shows you how to configure and start a TCP6SAM process. Note.
VA. Start the Applications (Without LNP) Quick Start 2. Go to VB. Start the Applications (With LNP) on page 1-21. VA. Start the Applications (Without LNP) This subsection shows you how to start the two basic TCP/IP applications, LISTNER and Telserv. 1. Start the LISTNER process. a. Add a DEFINE to establish the TCP6SAM process name as the transportservice provider for LISTNER by entering the TACL command: >ADD DEFINE =TCPIP^PROCESS^NAME, CLASS MAP, FILE $ZSAM1 b.
VB. Start the Applications (With LNP) Quick Start b. Start the LISTNER process for the default LNP by entering this TACL RUN command: >LISTNER/TERM $ZHOME, OUT $ZHOME, NAME $LSN0, CPU 0, NOWAIT, PRI 160/1 $SYSTEM.ZTCPIP.PORTCONF 2. Start the Telserv process for the default LNP. a. Add a PARAM to establish the TCP6SAM process name as the transportservice provider for a Telserv process in the default LNP by entering the TACL command: >PARAM TCPIP^PROCESS^NAME $ZSAM1 b.
VI. Add More Features Quick Start c. Start the Telserv process by entering the TACL RUN command: TELSERV/TERM $ZHOME, OUT $ZHOME, NAME $ZTN1, CPU 0, NOWAIT, PRI 170/ -BACKUPCPU 1 5. Start the LISTNER process for the second indexed LNP. a. ALTER the DEFINE to establish the TCP6SAM process name as the transportservice provider for a LISTNER process in the second indexed LNP by entering the TACL command: >ALTER DEFINE =TCPIP^PROCESS^NAME, CLASS MAP, FILE $ZSAM3 b.
Quick Start VI.
2 Overview of NonStop TCP/IPv6 This manual documents NonStop TCP/IPv6 only. For information about Parallel Library TCP/IP, see the TCP/IP (Parallel Library) Configuration and Management Manual. Note. Parallel Library TCP/IP is not supported on Integrity NonStop servers. If run in INET mode (see Table 2-5 on page 2-19), NonStop TCP/IPv6 is a direct replacement for Parallel Library TCP/IP.
High-Level Comparison of the Three NonStop Server TCP/IP Subsystems Overview of NonStop TCP/IPv6 Table 2-1. Summary of Differences Between Conventional TCP/IP, Parallel Library TCP/IP, and NonStop TCP/IPv6 Conventional TCP/IP Parallel Library TCP/IP NonStop TCP/IPv6 Supported on NonStop S-series and Integrity NonStop servers. Supported on NonStop S-series servers. Not supported on Integrity NonStop servers. Supported on NonStop S-series servers and Integrity NonStop servers.
High-Level Comparison of the Three NonStop Server TCP/IP Subsystems Overview of NonStop TCP/IPv6 Figure 2-1. NonStop TCP/IPv6 Routes Packets to Any Processor in the System Processor 0 Processor 1 Processor 15 App 1 App 2 App 16 TCP/IP Library TCP/IP Library TCP/IP Library ServerNet LAN Adapter VST129.
Single IP Overview of NonStop TCP/IPv6 Figure 2-2. Conventional TCP/IP Requires a Message-System Inter-Process Hop Message-System Inter-Process Hop Processor 0 Web 1 TCP/IP 1 Processor 1 Processor 15 Web 2 Web 16 TCP/IP 2 TCP/IP 16 Message-System Inter-Process Hop LAN Adapters VST120.vsd By eliminating message-system hops, NonStop TCP/IPv6 reduces the total path length from the application to the wire. This path-length reduction reduces individual request latency.
Single IP Overview of NonStop TCP/IPv6 Figure 2-3. In Conventional TCP/IP, Different Processes Present Multiple IP Hosts to the Network Processor 0 Processor 1 Processor 15 App 0 App 1 App F TCP/IP 0 TCP/IP 1 TCP/IP F LAN Adapters 1.2.3.4 1.2.3.5 1.2.3.6 VST128.vsd NonStop TCP/IPv6 enables you to configure the whole system to appear as one IP host, as shown in Figure 2-4. Figure 2-4.
Overview of NonStop TCP/IPv6 Round-Robin Filtering In a single-IP configuration, remote clients trying to connect to the NonStop TCP/IPv6 network only need to know a single IP address to receive the processing power of up to 16 processors. Round-Robin Filtering For multiple processors to share an interface (SLSA LIF), a NonStop TCP/IPv6 feature called round-robin filtering must be enabled.
Overview of NonStop TCP/IPv6 Logical-Network Partitioning (LNP) You can limit the shared ports by adding one or both of the DEFINEs: ADD DEFINE =PTCPIP^FILTER^TCP^PORTS, FILE Pstartport.Pendport ADD DEFINE =PTCPIP^FILTER^UDP^PORTS, FILE Pstartport.Pendport The startport and endport variables are integers specifying the allowable port range. The =PTCPIP^FILTER^TCP^PORTS key limits the shared TCP ports to the range defined in startport and endport.
Logical-Network Partitioning (LNP) Overview of NonStop TCP/IPv6 Figure 2-6. NonStop TCP/IPv6 Without LNP: Applications Have Access to all Interfaces Within the Subsystem Without Logical Network Partitioning CPU 0 BEA WebLogic Customer Billing NonStop TCP/IPv6 BEA WebLogic Servernet LAN01 Global Internet LAN02 LAN02 Finance Network VST158.
Logical-Network Partitioning (LNP) Overview of NonStop TCP/IPv6 Figure 2-7. Logical-Network Partitioning: Applications are Restricted to the Interfaces Within an LNP Logical Network Partitioning Enabled CPU 0 BEA WebLogic Customer Billing NonStop BEA WebLogic TCP/IPv6 LNP 11 LNP L018 Global Internet LNP 22 LNP Servernet L019 LAN02 Finance Network VST159.
Ethernet Failover, NonStop Operations Overview of NonStop TCP/IPv6 restrict itself to specific interfaces, has direct access (with no inter-process, messagesystem hop) to the network adapter. The loopback SUBNET is assigned logically to the default LNP, but each LNP can be viewed as having its own copy of the loopback interface. Applications on an LNP use the loopback interface to communicate with other applications on the same LNP without using the local area network as is done in the current product.
NonStop TCP/IPv6 Components Overview of NonStop TCP/IPv6 Table 2-3.
Overview of NonStop TCP/IPv6 TCP6MAN Note that in NonStop TCP/IPv6, the TCP6MON, TCP/IP library and application components are in the data path. Figure 2-8 on page 2-11 also shows that the TCP/IP library is pulled into the application context. Data transfer in the NonStop TCP/IPv6 occurs within the library. The conventional TCP/IP environment shown in Figure 2-8 on page 2-11 requires two message-system, inter-process communication hops.
Overview of NonStop TCP/IPv6 ZTCP6REL/ZTCP6SRL (for G-Series RVUs Only) on page 2-11. As of G06.22, the TCP6SAM process provides a feature from the conventional NonStop TCP/IP product: the ability to associate a TCP/IP process with specific IP addresses and, in turn, to associate applications with that process and set of IP addresses. This feature is called LNP (see Logical-Network Partitioning (LNP) on page 2-7).
Overview of NonStop TCP/IPv6 ZTCP6DLL ZTCP6DLL On Integrity NonStop servers, the functionality of the SRL is replaced by a dynamic linked library (DLL). The DLL requires no configuration steps; use of the DLL is fully automated. PTrace (ZTC6PTR) The PTrace product module formats the trace data records. SCF The SCF product module provides the command-line interface for managing the NonStop TCP/IPv6 subsystem.
SCF Overview of NonStop TCP/IPv6 Figure 2-9. NonStop TCP/IPv6 Subsystem Within the System SCF Commands and Responses SPI-formatted messages SCF DSM Management Applications ND6HOSTD SCP Open and Close Requests Application TCP6SAM TCP6MON QIO Shared Memory Segment Inbound Packets TCP6MAN Outbound Packets TCPLIB LAN Drivers/Interrupt Handlers SLSA/DIH ServerNet Fabrics LAN Adapter (IPv4 Only) SWAN Concentrator LAN Adapter X.
ND6HOSTD Process Overview of NonStop TCP/IPv6 Figure 2-9 on page 2-15 also shows the management interfaces involved in running TCP/IP. The lines between the terminal, SCF, SCP, DSM and TCP6MAN indicate management flow through the message system. The solid lines between the application and TCP6SAM is also a message system transfer. The application and TCP6MON communicate with each other through the TCP/IP library and transfer data within the library without message-system hops.
Fundamentals of IPv6 Overview of NonStop TCP/IPv6 Table 2-4. RFCs Supported by NonStop TCP/IPv6 (page 2 of 2) RFC Number RFC Title 2374 IPv6 Aggregatable Global Unicast Address Format. 2375 IPv6 Multicast Address. 2893 Transitions Mechanisms for IPv6 Hosts and Routers The list identifies some IPv6 features and how they are implemented on NonStop systems. (For more information about IPv6, see Appendix A, IPv6 Fundamentals.
Overview of NonStop TCP/IPv6 Fundamentals of IPv6 specify the IPV6RAENABLE attribute as ON as shown in the example (Note that the asterisk (*) specifies all TCPMONs on the system): ->ADD SUBNET $ZZTCP.*.
NonStop TCP/IPv6 ND6HOSTD Process for DNS Updates Overview of NonStop TCP/IPv6 link-local address, you can communicate between two hosts on the same link using just those addresses. NonStop TCP/IPv6 ND6HOSTD Process for DNS Updates NonStop TCP/IPv6 provides a process called ND6HOSTD that updates the DNS for IPv6 addresses (provided a DNS server that updates IPv6 addresses exists on the network). The ND6HOSTD process is managed by the persistence manager.
How to Access NonStop TCP/IPv6 Overview of NonStop TCP/IPv6 For DUAL mode, 1. Alter the MON to DUAL mode: ->ALTER MON $ZZTCP.*, FAMILY DUAL 2. Add the SUBNET and specify FAMILY as DUAL: ->ADD SUBNET $ZZTCP.*.SN1, TYPE ETHERNET, FAMILY DUAL, & DEVICENAME LAN02, IPADDRESS 1.2.3.4, IPV6RAENABLE ON For DUAL mode with Ethernet failover, in the ADD SUBNET command, specify FAMILY as DUAL. For examples of Ethernet failover in DUAL mode, see Section 1, Quick Start.
How to Access Online Help Overview of NonStop TCP/IPv6 Example 2-2. LISTDEV TCPIP Display Showing the Program Name of TCPSAM 1 2 3 4 5 6 7 8 9 SCF - T9082G02 - (05AUT99) (26JUL99) - 12/22/1999 14:52:00 System \MYSYS2 Copyright Hewlett-Packard Company LDev Name 107 $ZB01A 141 $ZSAM1 154 $ZTC0 158 $ZB018 190 $ZSAM2 PPID 0,285 3,269 0,299 1,293 1,310 BPID 1,287 1,286 0,302 Type (48,0) (48,0) (48,0) (48,0) (48,0) RSize 32000 57344 32000 32000 57344 Pri 200 201 200 200 201 Program \MYSYS2.$SYSTEM.SYS03.
Overview of NonStop TCP/IPv6 Programming With the TCP6SAM Socket Provider Programming With the TCP6SAM Socket Provider Applications rely on the transport-service provider for making socket requests. An application programmer can specify either the conventional TCP/IP or the NonStop TCP/IPv6 environment by choosing the appropriate transport-service provider. To select the NonStop TCP/IPv6 environment, see How to Access NonStop TCP/IPv6 on page 2-20.
Overview of NonStop TCP/IPv6 Programming With the TCP6SAM Socket Provider In this example, if you wanted to associate your application with IP address 172.17.215.49, you would select $ZSAM2 or $ZSAM3, then define that TCP6SAM process as the transport-service provider name for your application. For examples of starting applications to use an LNP, see IVB. Prepare to Start the Applications (With LNP) on page 1-20 and VB. Start the Applications (With LNP) on page 1-21.
Overview of NonStop TCP/IPv6 Programming With the TCP6SAM Socket Provider HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 2-24
3 Maximize the Benefit of the NonStop TCP/IPv6 Architecture This section provides planning information for maximizing the benefit of the NonStop TCP/IPv6 environment. If you are not familiar with the NonStop TCP/IPv6 or the Parallel Library TCP/IP architecture, read this section to learn how to take advantage of the product features. Note. Parallel Library TCP/IP is not supported on the Integrity NonStop server.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Listener Models: How They Benefit From the NonStop TCP/IPv6 Architecture Listener Models: How They Benefit From the NonStop TCP/IPv6 Architecture Networking applications fall into five listening-model types: Standard Listening Model Monolithic Listening Model on page 3-4 Distributor Listening Model on page 3-6 Hybrid Listener Model on page 3-9 Broker Listener Model on page 3-10 This subsection describes these networking application mod
Standard Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture Figure 3-1. Standard Listening Model Conventional TCP/IP NonStop TCP/IPv6 1. 1. LAN Adapter Processor 0 LISTNER Connection Req 1 LAN Adapter Connection Req 1 TCP/IP Processor 0 LISTNER TCP/IPv6 LIB 2. 2.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture 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 within the same process creating sockets for the connections.
Monolithic Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture Figure 3-2. Monolithic: Listening Model Conventional TCP/IP IPC hop Processor 0 Processor 1 TCP/IP Process Monolithic Server Sockets Port xxxx (Exclusive) LAN Adapter NonStop TCP/IPv6 Sockets Monolithic Server Port xxxx (Shared) TCP/IP Library Monolithic Server Port xxxx (Shared) TCP/IP Library Monolithic Server Port xxxx (Shared) TCP/IP Library LAN Adapter VST108.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Distributor Listening Model In the NonStop TCP/IPv6 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).
Distributor Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture 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. This situation creates a potential bottle-neck in the distributor. Figure 3-3 shows the distributor listener model in conventional TCP/IP.
Distributor Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture The distributor listener model can benefit from the NonStop TCP/IPv6 architecture in two ways: You can now run multiple distributor processes in multiple processors bound to the same port with round-robin filtering enabled. This arrangement lets you spread the distributor’s workload over as many processors as required achieving unlimited scalability while presenting a single IP host to the outside world.
Hybrid Listener Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Distributor Listening Model on page 3-17 shows you how to configure this listener model. Hybrid Listener Model This method still has a distributor process using Pathway for managing and loadbalancing server process instances, but it uses the standard listener approach, handing off connections, so that data does not have to flow through the distributor process.
Broker Listener Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture allowing reactive distribution. The servers have direct access to the TCP/IP library in their own processors, eliminating both the remote IPC hops and local IPC hops. All the distributors share the same port and present a single IP host to the outside world. Figure 3-6 shows a configuration (simplified for comparison) with two distributors: one in processor 0 and one in processor 2.
Broker Listener Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture Figure 3-7. Broker Listening Model in NonStop TCP/IPv6 Processor 0 Processor 1 Processor 2 Server 1 Broker 1 Server 2 TCP/IPv6 Library TCP/IPv6 Library TCP/IPv6 Library Processor 3 Broker 2 ServerNet TCP/IPv6 Library LAN Adapter Client 1 Client 2 Client 3 VST133.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Examples for the Listening Models spread the broker’s workload over as many processors as required, achieving unlimited scalability while presenting a single IP host image to the outside world. The architecture shortens the path length for data flow by eliminating the hop between the broker processes and the TCP/IP process, as well as between the server processes and the TCP/IP process, thereby improving performance.
Configuration Example for the Standard Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture Figure 3-8. Standard Listening Model Configuration Example: LISTNER NonStop Server With 4 Processors LAN Adapter 150.50.130.2 Processor 0 LISTNER A connection request comes into the LISTNER. 150.50.130.2 Four processors handling four connections. Processor 0 LISTNER FTPSERV TCP/IP Library Backup LISTNER LAN Adapter 2. LAN Adapter 4. TCP/IP Library 1.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Monolithic Listening Model Example 3-1. TCPIPUP11 for the LISTNER Process comment comment comment comment comment comment comment comment TACL command file to bring up NonStop TCP/IPv6 subsystem Use DNS for name resolution; (no host file DEFINE) DELETE DEFINE =TCPIP^HOST^FILE ADD and START SUBNETS SCF/IN $SYSTEM.TCPIP.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Monolithic Listening Model Figure 3-9. Configuration Example for Monolithic Listening Model: Telserv TCP/IP Services Processor 0 TCP/IP Services Processor 1 TCP/IP Services LAN Adapter Processor 2 TCP/IP Services Host Processor 3 TELSERV TELSERV TELSERV TELSERV VST104.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Monolithic Listening Model Example 3-2. TCPIPUP12 for the Telserv Process comment comment comment comment comment comment comment comment comment TACL command file to bring up the NonStop TCP/IPv6 subsystem Use DNS for name resolution; (no host file DEFINE) DELETE DEFINE =TCPIP^HOST^FILE ADD and START SUBNETS SCF/IN $SYSTEM.TCPIP.
Configuration Example for the Distributor Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Distributor Listening Model This example demonstrates the distributor listener model (see Distributor Listening Model on page 3-6) using a hypothetical distributor called “Distrib” configured with round-robin enabled. This configuration example assumes that you have already configured the basic subsystem.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Distributor Listening Model The first connection request establishes a connection to one of the distributor’s sockets. The adapter then routes the next connection request to the next distributor in the next processor, and so on. The TCPIPUP13 File In this example, TCPIPUP7, the main command file, does not include the complete configuration commands for Distrib Server.
Configuration Example for the Hybrid Listening Model Maximize the Benefit of the NonStop TCP/IPv6 Architecture The lines starting the Distrib processes, starting with: RUN DISTRIB /NAME $DIST1, NOWAIT, PRI 160, CPU 3/0 start a Distrib process in each of the processors. Note that the backup Distrib processes do not share any processors with other Distrib processes. Running Distrib processes in distinct processor pairs avoids potential port sharing conflicts in a failure situation.
Maximize the Benefit of the NonStop TCP/IPv6 Architecture Configuration Example for the Hybrid Listening Model The first connection request establishes a connection to one of the Distrib processes. The adapter then routes the next connection request to the next Distrib process in the next processor, and so on. The TCPIPUP14 File This TACL command file starts the processes, adds and starts subsystem objects through SCF, and sets appropriate parameters.
4 Plan Your IPv6 Implementation This section provides ideas for planning your IPv6 implementation. Obtain IPv6 Addresses IPv6 addresses are now being deployed by the regional registries. To obtain an IPv6 address or block of addresses, contact your Internet Service Provider (ISP).
Plan Your IPv6 Implementation Install IPv6-Capable Routers Install IPv6-Capable Routers This process depends on the hardware vendor you have chosen. You must define what address prefixes the router will advertise and the interfaces over which to advertise them. Configure NonStop Server IPv6 Hosts 1. Decide if you want to run in INET6 mode. You might use this mode if you are running IPv6 in a network that is restricted to IPv6. See Configure the Basic Subsystem for INET6 Mode on page 5-7. 2.
Plan Your IPv6 Implementation Intranet Scenario Intranet-to-Internet Scenario on page 4-5 Intranet-to-Internet-to-Intranet Scenario on page 4-6 Intranet Scenario In this scenario, you deploy IPv6 hosts on a small subnet in your network. These hosts communicate with each other using link-local addresses. If you add an IPv6 router to the subnet and advertise an address prefix, each IPv6 host autoconfigures a global IPv6 address and uses that address to communicate with other IPv6 hosts.
Intranet Scenario Plan Your IPv6 Implementation Figure 4-1. Deploying IPv6 in an Intranet Scenario Host A v4/v6 Host B v4/v6 Host C v4/v6 Router A v4/v6 Department A Router B v4/v6 v4 v4 Host D Host E v4/v6 Host F Router C v4 Department B Router D v4 v4 v4 Host G Host H v4/v6 Host I Department C VST138.vsd To communicate with Host I, Host A sends an IPv6 packet to Router A. Router A forwards the IPv6 packet to Router B.
Plan Your IPv6 Implementation Intranet-to-Internet Scenario IPv4 packet and routes the IPv6 packet to Host A. (For hosts, the host-to-router tunnel is efficient because it saves the Host A, Host B, and Host C administrators from having to create individual host-to-host tunnels for each destination host.) Intranet-to-Internet Scenario In this scenario, you add a v4/v6 router to your network and use it to communicate with the global Internet. The IPv6 hosts communicate with the v4/v6 router using IPv6.
Plan Your IPv6 Implementation Intranet-to-Internet-to-Intranet Scenario Figure 4-2. Deploying IPv6 in an Intranet-to-Internet Scenario Host A v4/v6 Host B v4/v6 Host C v4/v6 Host J Internet Router A v4/v6 Department A 6Bone Point of Entry Router B v4/v6 v4 v4 Host D Host E v4/v6 Host F Router C v4 Department B Router D v4 v4 v4 Host G Host H v4/v6 Host I Department C VST139.vsd To communicate with the 6bone, Host A sends the IPv6 packet to Router A.
Plan Your IPv6 Implementation Intranet-to-Internet-to-Intranet Scenario using IPv6. For IPv6 traffic between the v4/v6 routers on each subnet, you configure router-to-router tunnels. Figure 4-3 shows a scenario in which the corporation described in the previous sections wants to connect its corporate network with one of its geographically remote departments to create a VPN. To communicate with Host K, Host A sends the IPv6 packet to Router A.
Plan Your IPv6 Implementation Port Existing IPv4 Applications Port Existing IPv4 Applications The NonStop system provides the basic application programming interfaces (APIs) as defined in RFC 2553. You can use the APIs and the AF_INET6 sockets in your existing applications (or in new applications) to communicate with IPv4 nodes today. Your ported applications will continue to communicate with IPv4 nodes and be ready to communicate with IPv6 nodes.
5 Example Illustrations and Adding Features to the Basic Configuration This section explains the configuration examples in Section 1, Quick Start and shows you how to add more features to those basic examples. This section also shows you how to configure the subsystem in INET and INETD modes and discusses the benefits of NonStop TCP/IPv6 for WAN configurations. Illustrations of the Quick Start Examples This subsection provides figures to illustrate some of the examples provided in Section 1, Quick Start.
Example Illustrations and Adding Features to the Basic Configuration DUAL Mode In this configuration, you can configure applications so that they are restricted to listening to IP addresses 172.14.217.25 and 172.14.200.24, the configured LNPs. All other applications can share the default LNP represented by $ZSAM1. For background information about this feature, see Logical-Network Partitioning (LNP) on page 2-7.
Example Illustrations and Adding Features to the Basic Configuration DUAL Mode, Ethernet Failover The IPV6RAENABLE ON attribute enables router advertisements on the SUBNET, which allows the host to build the global IPv6 address from the router advertisement (RA) received from the router. DUAL Mode, Ethernet Failover Example 1-8 on page 1-16 shows how to configure a DUAL-mode SUBNET (supporting IPv4 and IPv6 networks) with Ethernet failover, shared IP. This configuration is shown in Figure 5-3.
Example Illustrations and Adding Features to the Basic Configuration DUAL Mode, Ethernet Failover, Nonshared IP The IPV6RAENABLE ON attribute enables the SUBNET to obtain a prefix from the router. This prefix is prepended to the interface ID. As the IP Ethernet failover configuration is shared, the IPv4 addresses are the same (172.14.215.27) and the IPv6 interface IDs are the same (::ABCD:1234).
Example Illustrations and Adding Features to the Basic Configuration DUAL-Mode, Configured Tunnel As you do not want the SUBNETs to share an IP address, each SUBNET can keep the IPv6 addresses automatically assigned to it. You do, however, have the option of specifying a prefix for the IPv6 addresses; the final addresses assigned to the SUBNETs still differ in this case as the interface IDs are different (different SUBNETs have different interface IDs).
Example Illustrations and Adding Features to the Basic Configuration Adding More Features The IPTSRC and IPTDST attributes set the IPv4 source and destination addresses in the encapsulating header. These addresses are local and destination end points for data communications. The local endpoint SUBNET, in this case SN3 with address 172.14.215.27, must be configured before you add the configured tunnel. (For more information about tunnels, see How IPv6 Tunnels Work on page A-18.
Example Illustrations and Adding Features to the Basic Configuration Specify IPv6 Addresses Specify IPv6 Addresses The examples in Section 1, Quick Start all use automatic address configuration; however, to add a specific IPv6 address to the configuration, you can specify a valid IPv6 address in the ADD SUBNET command by using the IPV6PREFIX or IPV6ADDRESS attributes: + ADD SUBNET *.SN3, TYPE ETHERNET, FAMILY DUAL, & IPADDRESS 172.14.215.27, DEVICENAME L019, & SUBNETMASK 255.255.255.
Example Illustrations and Adding Features to the Basic Configuration Plan Complex WAN Environments Plan Complex WAN Environments NonStop TCP/IPv6 provides improved scalability for the SWAN subsystem.
6 Manage the NonStop TCP/IPv6 Subsystem Considerations and Guidelines for Using NonStop TCP/IPv6 This subsection discusses considerations and guidelines for using these NonStop TCP/IPv6 features: Considerations for Round-Robin Filtering on page 6-2 Fault-Tolerant Operations, Ethernet Failover Guidelines on page 6-3 QIO Management Considerations on page 6-5 Application Isolation on page 6-6 HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 6-1
Manage the NonStop TCP/IPv6 Subsystem Considerations for Round-Robin Filtering Considerations for Round-Robin Filtering This subsection describes special considerations for round-robin filtering. Port Collision Considerations for Listening Processes When you configure a set of listening processes for round robin, do not allow their primary and backup processors to overlap. That is, if you configure primary and backup listening processes, do so in distinct pairs.
Manage the NonStop TCP/IPv6 Subsystem Fault-Tolerant Operations, Ethernet Failover Guidelines 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.
Manage the NonStop TCP/IPv6 Subsystem Fault-Tolerant Operations, Ethernet Failover Guidelines TCP/IPv6 assigns the outbound traffic to the SUBNET assigned to that IP address. Nonshared IP lets you control the inbound traffic load, forcing the connections to be distributed over the two interfaces presented by the different IP addresses. This is handy when you have limited hardware resources or you want to maximize the use of LIFs. Both LIFs of a failover pair must be cabled to the same network segment.
Manage the NonStop TCP/IPv6 Subsystem QIO Management Considerations Configuration Guidelines These are guidelines to use when configuring NonStop TCP/IPv6 with Ethernet failover: When selecting the LIF pair for the failover SUBNET pair, you should select LIFs on different adapters. When using Fast Ethernet adapters and Gigabit Ethernet adapters connected directly to Ethernet switches, the failover recovery time can be impacted by the spanning tree feature used in a switch.
Manage the NonStop TCP/IPv6 Subsystem Application Isolation Some constraints affecting NonStop TCP/IPv6 (as well as other QIO clients) include the reduction of QIO memory space to 128 MB when QIO is moved to Kseg2 on the NonStop S-series server. (On the Integrity NonStop server, the QIO memory space in global privileged space is 256 MB.) The available QIO memory space impacts the number of LIFs that you can configure on your system because LIFs use QIO memory.
Manage the NonStop TCP/IPv6 Subsystem Stopping NonStop TCP/IPv6 b. For an IPv6 address, NonStop TCP/IPv6 goes to IPNODES and looks for the address. To cause the socket library to use DNS, delete the TCPIP^HOST^FILE DEFINE. Adding or deleting a DEFINE for the IPNODES file does not affect whether the socket library uses DNS.
Manage the NonStop TCP/IPv6 Subsystem Preparing to Stop the NonStop TCP/IPv6 Subsystem Stopping NonStop TCP/IPv6 as a Generic Process on page 6-12 Use this procedure if the TCP6MAN process ($ZZTCP) is a persistent process otherwise the persistence manager will restart $ZZTCP every time you stop it. If you want to stop the NonStop TCP/IPv6 subsystem and clear the database of existing records, see the TCP/IPv6 Migration Guide for procedures.
Manage the NonStop TCP/IPv6 Subsystem Preparing to Stop the NonStop TCP/IPv6 Subsystem This 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.#0000382 Pages allocated: 24 Pages Maximum: 1024 Bytes Used: 32820 (1%) Bytes Maximum: 2097152 Current volume: $SYSTEM.SYSTEM Saved volume: $SYSTEM.SYSTEM Userid: 255,255 Username: SUPER.SUPER Security: "AAAA" Logon name: SUPER.
Manage the NonStop TCP/IPv6 Subsystem Preparing to Stop the NonStop TCP/IPv6 Subsystem This sample display results from the LISTOPENS PROCESS command and shows all the processes depending on $ZTC0: TCPIP Listopens PROCESS \HOME.
Manage the NonStop TCP/IPv6 Subsystem Stopping NonStop TCP/IPv6 and Preserving the Current Configuration This sample display results from the LISTOPENS MON command and shows all the processes depending on the NonStop TCP/IPv6 subsystem: -> listopens mon $zztcp.* TCPIPV6 Listopens MON \HOME.$ZZTCP.
Manage the NonStop TCP/IPv6 Subsystem Stopping NonStop TCP/IPv6 as a Generic Process processes you noted in Preparing to Stop the NonStop TCP/IPv6 Subsystem on page 6-8. Enter the command at the TACL prompt: >TEDIT TCPIPDN Example 6-1. TCPIPDN Command File ==Stop the opener processes.
Manage the NonStop TCP/IPv6 Subsystem Running Applications in Multiple Environments Tasks: Stopping NonStop TCP/IPv6 as a Generic Process 1. Stop all openers of the TCP6MONs. (Note that LISTNER and TELSERV do not support the SCF ABORT command so you must use the TACL STOP command to stop those processes.) Enter these commands at the TACL prompt: >STOP PROCESS $ZLIS3 >STOP PROCESS $ZTEL3 2. Abort all TCP6SAM processes. Enter these commands at the SCF prompt: ->ABORT PROCESS $ZTS0 ->ABORT PROCESS $ZTCPS1 3.
Manage the NonStop TCP/IPv6 Subsystem Managing the System Configuration Database Managing the System Configuration Database The system configuration database (CONFIG) is part of the NonStop Kernel subsystem on NonStop S-series servers and Integrity NonStop NS-series servers. The conventional TCP/IP subsystem (NonStop TCP/IP) does not participate in the system configuration database, but NonStop TCP/IPv6 does.
Manage the NonStop TCP/IPv6 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 this way, set the STARTMODE to SYSTEM.
Manage the NonStop TCP/IPv6 Subsystem How to Manage TCP6SAM-Dependent Applications Command File for Starting a TCP6SAM Process Because you have to start TCP6SAM processes yourself without the aid of the persistence manager, HP recommends that you create a command file for this purpose. However, before issuing the OBEY command on the file, ensure that your session is still in the subvolume of the SRL file by using the FILEINFO command shown in TACL Commands for Starting a TCP6SAM Process on page 6-15. 1.
Manage the NonStop TCP/IPv6 Subsystem How to Add TCP6MAN as a Generic Process to the System Configuration Database about adding a generic process, see the SCF Reference Manual for the Kernel Subsystem Example 6-3. Command File for Adding TCP6MAN as a Generic Process SCF/INLINE/ INLPREFIX + +ADD PROCESS $ZZKRN.#ZZTCP, AUTORESTART 10, BACKUPCPU 1, & DEFAULTVOL $SYSTEM.SYSTEM, HOMETERM $ZHOME, INFILE $ZHOME, & NAME $ZZTCP, OUTFILE $ZHOME, PRIMARYCPU 0, PRIORITY 180, & PROGRAM $SYSTEM.SYSTEM.
Manage the NonStop TCP/IPv6 Subsystem Managing the ND6HOSTD Process Change STARTMODE to DISABLED. In this case, the generic process ($ZZKRN.#ZZTCP) remains in the system configuration database, but is not started by the persistence manager. In addition, you cannot manually start the generic process ($ZZKRN.#ZZTCP) until the STARTMODE is changed back to SYSTEM or MANUAL.
Manage the NonStop TCP/IPv6 Subsystem Configure the ND6HOSTD Process for Address Resolution You need the ND6HOSTD process only when you want to update the DNS with your automatically generated IPv6 addresses. The ND6HOSTD process requires one INET6 SUBNET and one INET SUBNET to be configured in the system (For more information about DNS-query constraints, see the TCP/IPv6 Migration Guide). The ND6HOSTD process is a Guardian process that you configure the $ZPM persistence manager to start.
Manage the NonStop TCP/IPv6 Subsystem NAME $name Configure the ND6HOSTD Process for Address Resolution Specifies the process name, as recognized by TACL. $name cannot exceed three characters (after the dollar sign). This is because the two-digit processor number is appended to the process name. The recommended value is $ZHD. OUTFILE $device Specifies the output file or process name sent to this process (in the startup message) when it is started. $ZHOME should be specified for $device.
Manage the NonStop TCP/IPv6 Subsystem SAVEABEND ON Configure the ND6HOSTD Process for Address Resolution Specifies whether a saveabend file is created if this process stops abnormally. This attribute overrides the SAVEABEND setting in the PROGRAM file for this process. The value of ON should be specified to automatically create a saveabend file if the process ends abnormally.
Manage the NonStop TCP/IPv6 Subsystem Manage Configuration Errors Each LNP that a ND6HOSTD is run on also requires that at least one DUAL mode SUBNET exist in that LNP so that the ND6HOSTD can communicate with the DNS server.
Manage the NonStop TCP/IPv6 Subsystem Managing LNPs From a systems perspective, the overall processor utilization should be less than in the conventional TCP/IP environment because the number of dispatches and context switches is minimized. Managing LNPs Implementing LNP makes configuring NonStop TCP/IPv6 more complex because each LNP is considered independent of the others, each one must have its static routes configured individually.
Manage the NonStop TCP/IPv6 Subsystem Managing Applications Managing Applications Applications are not affected if LNP is not enabled, however after a SUBNET is configured with the attributes enabling logical-network partitioning all applications running on the TCP/IPv6 subsystem are affected. Coding changes are not needed in an application to support LNP, but how an application is run and perhaps configured can change.
Manage the NonStop TCP/IPv6 Subsystem LNP Guidelines SUBNETs configured as failover pairs must be assigned to the same LNP. A SUBNET can be configured with at most two TCP6SAM processes specified in its LNPTPLIST attribute. Route and ARP entries between LNPs cannot be shared, each is independent. Adding of route and ARP entries requires the use of the SUBNET attribute to assign the entry to a specific LNP.
Manage the NonStop TCP/IPv6 Subsystem Strategy for Coexistence With Conventional TCP/IP Special considerations apply for the ND6HOSTD process. See Managing the ND6HOSTD Process on page 6-18. You can add up to 64 SUBNETs to an LNP because you can only have 64 SUBNETs in the NonStop TCP/IPv6 subsystem, if you have 64 SUBNETs in one LNP, the default LNP only has the loopback interface. At the other extreme, you can have 64 LNPs, each with one SUBNET.
Manage the NonStop TCP/IPv6 Subsystem Falling Back to Conventional TCP/IP Falling Back to Conventional TCP/IP 1. Follow one of the shutdown procedures in this section. 2. Change your system configuration database back to the previous configuration database that you saved before installing NonStop TCP/IPv6 (in 2. Prepare to Install and Configure the Subsystem on page 1-2). The TSM or OSM system-load online help provides information about how to select a specific configuration file at system load. 3.
Manage the NonStop TCP/IPv6 Subsystem Software Replacement 4. Switch over to the Parallel Library TCP/IP environment. Reset the DEFINEs, PARAMs, and/or transport-service provider name-set procedure calls for your applications back to the conventional TCP/IP process name. a. Determine the name of a TCPSAM process name to use as a transportservice provider. Use the LISTDEV command to obtain a list of running TCP/IP processes, including TCPSAM processes: ->LISTDEV TCPIP b.
Manage the NonStop TCP/IPv6 Subsystem Monitoring the Network Monitoring the Network To monitor your network, use these management tools: ping command Tracer utility Event Management System (EMS) Messages Note. Before using the ping and tracer utilities, set the transport provider name to the appropriate TCP6SAM process by using the ADD DEFINE TCPIP^PROCESS^NAME command.
Manage the NonStop TCP/IPv6 Subsystem Displaying a Datagram’s Route to a Network Host by Using the Tracer Utility Examples: This command directs the output of a trace to be sent to a remote system named \IDEV to a disk file named $fiti.trace.traceout on the local system. >TACL TRACER/OUT $fiti.trace.traceout/IDEV This command directs the output of a trace to be sent to a remote system named \IDEV to a disk file named $wpo.trace.traceout on the system named \igate. >TACL TRACER/OUT \igate.$wpo.trace.
Manage the NonStop TCP/IPv6 Subsystem Displaying a Datagram’s Route to a Network Host by Using the Tracer Utility [-r ] specifies that the routing tables be bypassed and that probes should be sent directly to a host on an attached network. If the host is not on a directly attached network, an error message is returned. You can use this option to send an ICMP echo request to a local host through an interface that does not involve routing.
Manage the NonStop TCP/IPv6 Subsystem Event Management System (EMS) Messages LOG_GOTCONN LISTNER option. The following command logs got connection messages: TACL> run LISTNER [/run-options/] < backupcpu> LOG_GOTCONN By default, the got connection messages are not logged. Event Management System (EMS) Messages NonStop TCP/IPv6 generates event messages that are documented in the Operator Messages Manual.
7 Troubleshooting Tips for NonStop TCP/IPv6 This section provides some conditions to check if you encounter some problems with your NonStop TCP/IPv6 configuration. Review these suggestions that might pertain to your configuration: Check the adapter configuration and ensure that the SACs are configured with the correct Access List. Ensure that all processors running a TCP6MON process are listed in the Access List.
Troubleshooting Tips for NonStop TCP/IPv6 pair in processors 0 and 1 and another primary and backup TELSERV pair in processors 2 and 3. The TCP6SAM process must be in a processor that has a TCP6MON running. Ensure that all primary and backup TCP6SAM processes are configured in processors, which contain a running TCP6MON.
8 SCF Reference for NonStop TCP/IPv6 This section provides information about: The Subsystem Control Facility (SCF) SCF commands available for NonStop TCPIPv6 (To find a command quickly, see Table 8-4 on page 8-10.) The PTrace facility SCF for NonStop TCP/IPv6 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 NonStop TCP/IPv6 Object Types The SCF STATUS PROC command for TCP6SAM differs from the SCF STATUS MON $ZZTCP.* command. The SCF STATUS PROC command does not provide complete CPU information for the connections for which accept() was not posted. To obtain complete information about CPUs, use the SCF STATUS MON $ZZTCP.* command. Object Types You can monitor and control the NonStop TCP/IPv6 subsystem by issuing commands that act on one or more NonStop TCP/IPv6 subsystem objects.
SCF Reference for NonStop TCP/IPv6 ENTRY Object Type pertaining to a ROUTE, SUBNET, or ENTRY object type can be issued only when the process and monitor (TCP6MON) objects are in the STARTED summary state. Figure 8-1. TCP6MAN Process Object Hierarchy $PROCESS #MONITOR SUBNET ROUTE ENTRY VST013.vsd Figure 8-2 shows the object hierarchy for the TCP6SAM process. Figure 8-2. TCP6SAM Process Object Hierarchy $PROCESS #SUBNET #ROUTE VST101.
SCF Reference for NonStop TCP/IPv6 MONITOR Object Type MONITOR Object Type The MONITOR object (TCP6MON) provides the NonStop TCP/IPv6 environment in a processor. Only one TCP6MON can exist per processor. TCP6MON has the reserved name of $ZPTMn where n is the processor number (hexadecimal) where TCP6MON resides. null Object Type The null object is not an actual object type. The term “null” represents the lack of a specified object.
SCF Reference for NonStop TCP/IPv6 ROUTE Object Type the display is “Program.” A program name of TCP6SAM indicates a NonStop TCP/IPv6 process while a program name of TCPIP indicates a conventional TCP/IP process. To obtain a list of all running NonStop TCP/IPv6 processes, enter the SCF LISTDEV TCPIPV6 command. (This command also gives you a list of the running TCP6MON objects.) Again, the process type (TCP6MON or TCP6MAN) is identified in the program field.
SCF Reference for NonStop TCP/IPv6 SUBNET Object Type SUBNET Object Type The SUBNET is the point of connection between the NonStop TCP/IPv6 and an I/O device. All subnets are associated with the TCP6MAN process. Each SUBNET name must be unique within the system. The name can have at most seven alphanumeric characters. The first character must be a letter. The SUBNET object is also subordinate to the TCP6MON object. A SUBNET is accessible to all TCP6MONs in the system.
SCF Reference for NonStop TCP/IPv6 Naming Convention Summary Naming Convention Summary Table 8-2 summarizes the reserved names for each object type and the naming convention rules. Table 8-2. Object Naming Convention Summary and Reserved Names Starting Symbol (Required) First Character Requirement First Character Recommendation Character Limit Letter EA 7 Object Type Reserved Names ENTRY None MON #ZPTMx # Letter MON names are assigned automatically.
SCF Reference for NonStop TCP/IPv6 Summary States Object-name templates allow you to specify multiple objects by entering either a single wild-card character, or text and one or more wild-card characters. In the NonStop TCP/IPv6 subsystem, you can use these wild-card characters: * Use an asterisk (*) to represent a character string of undefined length. This example deletes all subnets subordinate to $ZZTCP: SCF> DELETE SUBNET $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 NonStop TCP/IPv6 SCF Commands The summary states supported by the NonStop TCP/IPv6 subsystem are STARTED, STARTING, and STOPPED. Table 8-3 shows the states for each object. Table 8-3. Object Summary States Object STOPPED ENTRY STARTED STARTING X null PROCESS X MON X ROUTE X X SUBNET X X X In the STARTED summary state, the object is available for data transfer.
SCF Reference for NonStop TCP/IPv6 Supported Commands and Object Types Supported Commands and Object Types This section describes the SCF commands that are interpreted specifically for the NonStop TCP/IPv6 subsystem. The SCF Reference Manual for G-Series RVUs and SCF Reference Manual for H-Series RVUs provide general information about SCF commands. You should be familiar with that information before reading the NonStop TCP/IPv6 subsystem-specific information provided here.
SCF Reference for NonStop TCP/IPv6 Entering SCF Commands Table 8-5. Commands and Object Types for TCP6SAM (page 2 of 2) Object Types SCF Command PROCESS NAMES Command, 8-106 ROUTE SUBNET X X PRIMARY Command, 8-111 X STATS Command, 8-115 X X X STATUS Command, 8-170 X X X STOP Command, 8-194 X TRACE Command, 8-198 X VERSION Command, 8-207 X Table 8-6 lists the sensitive and nonsensitive NonStop TCP/IPv6 SCF commands. Table 8-6.
SCF Reference for NonStop TCP/IPv6 Entering SCF Commands SCF waits for a command, followed by a carriage return. After the command has been received and processed, SCF displays its prompt for the next command. An SCF command always begins with a keyword identifying the command (such as ADD, ABORT, or ALTER). The keyword is followed by the object specifier, consisting of the object type and the object name, as in this example: SCF> ABORT SUBNET $ZZTCP.*.SN1 Note.
SCF Reference for NonStop TCP/IPv6 IP Address Notation IP Address Notation Several attributes defining the SCF ROUTE and SUBNET objects require the specification of an IP address. In the IPV4 environment, an IP address contains 32 bits. You represent such an IP address by using a text string in dotted decimal format: d.d.d.d where d is the decimal value of an 8-bit octet. For example: 130.28.88.7 In the IPV6 environment, an IP address contains 128-bits.
SCF Reference for NonStop TCP/IPv6 ABORT Command In an IPv6 environment, for example, you can represent the 60-bit hexadecimal prefix 12AB00000000CD3 in any of these ways: 12AB:0000:0000:CD30:0000:0000:0000:0000/60 12AB::CD30:0:0:0:0/60 12AB:0:0:CD30::/60 Note. When you specify an IPv6 address for an SCF attribute, you must enclose the address in quotation marks (““).
SCF Reference for NonStop TCP/IPv6 ABORT PROCESS Command for TCP6MAN Examples To abort the MON object named #ZPTMA: SCF> ABORT MON $ZZTCP.#ZPTMA To abort all running TCP6MONs: SCF> ASSUME PROCESS $ZZTCP SCF> ABORT MON * Considerations The ABORT MON command deletes the MON from the system configuration database. If you want to stop the MON but leave it in the system configuration database, use the STOP MON Command for TCP6MAN on page 8-194.
SCF Reference for NonStop TCP/IPv6 ABORT PROCESS Command for TCP6SAM Examples To abort and delete the TCP6MAN process (named $ZZTCP) and all subordinate MON objects: SCF> ABORT PROCESS $ZZTCP, SUB ALL Considerations If the TCP6MAN process has been added as a generic process, you must use the ABORT command under the Kernel subsystem (ABORT PROCESS $ZZKRN.#ZZTCP) to stop it. For more information about managing generic processes, see the SCF Reference Manual for the Kernel Subsystem.
SCF Reference for NonStop TCP/IPv6 ABORT ROUTE Command for TCP6MAN ABORT ROUTE Command for TCP6MAN The ABORT ROUTE command terminates the activity of the specified route. Only enough processing is done to ensure the integrity of the subsystem. The object is left in the STOPPED summary state. The ABORT ROUTE command does not delete the ROUTE from the system configuration database. (See DELETE SUBNET Command for TCP6MAN on page 8-61.) Command Syntax ABORT [ / OUT file-spec / ] [ROUTE $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 ABORT SUBNET Command for TCP6MAN ABORT SUBNET Command for TCP6MAN The ABORT SUBNET command terminates the operation of a SUBNET as quickly as possible; only enough processing is done to ensure the integrity of the subsystem. The object is left in the STOPPED summary state because SUBNETs are accessible to every processor with a configured TCP6MON, the SUBNET command must be applied to all processors. Command Syntax ABORT [ / OUT file-spec / ] [SUBNET $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 ADD Command ADD Command The ADD command adds a SUBNET, ROUTE or ENTRY to the NonStop TCP/IPv6 subsystem. You must enter an ADD SUBNET command for each SUBNET with which the NonStop TCP/IPv6 subsystem is to communicate. Each SUBNET defines a point of attachment through which data is sent or received. This is a sensitive command. ADD ENTRY Command for TCP6MAN The ADD ENTRY command creates an entry in an ARP table.
SCF Reference for NonStop TCP/IPv6 ADD ENTRY Command for TCP6MAN IPADDRESS ip addr specifies the internet address for the entry and is specified in dotted decimal notation. MACADDR mac address specifies the Ethernet address for the ENTRY. It is entered as a string of twelve hexadecimal digits preceded by a “%h”. ALLENTRY ON | OFF allows (ON) or disallows (OFF) the automatic configuration of the multiple ARP table entries through each interface when multiple subnets exist on the same subnetwork.
SCF Reference for NonStop TCP/IPv6 ADD ROUTE Command for TCP6MAN ADD ROUTE Command for TCP6MAN The ADD ROUTE command creates a route. INET (IPv4) Command Syntax ADD [ / OUT file-spec / ] [ ROUTE $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 ADD ROUTE Command for TCP6MAN DESTTYPE { HOST | BROADCAST } specifies whether the route is a connection to a specific host (HOST) or to a network (BROADCAST). This is an optional attribute. Default: If you do not specify DESTTYPE in an ADD ROUTE command, the default value is BROADCAST. If a route is added automatically as the result of an ADD SUBNET command, the default value is BROADCAST.
SCF Reference for NonStop TCP/IPv6 ADD ROUTE Command for TCP6MAN FAMILY INET6 (IPv6) Command Syntax ADD [ /OUT file-spec/ ] [ ROUTE route-spec ] , FAMILY INET6 , IPV6DESTINATION "ipv6-addr" , IPV6GATEWAY [, DESTTYPE HOST ] [, SUBNET subnet-name ] [, ALLROUTES { ON | OFF } ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE $ZZTCP.*.route-name is the name of the route. The route specifies the path on which data is sent to reach a destination.
SCF Reference for NonStop TCP/IPv6 ADD ROUTE Command for TCP6MAN SUBNET subnet-name specifies the SUBNET to be associated with the route to be configured. Without this attribute, the manually-added static route is only associated with the first SUBNET found on the same IP subnetwork. You do not need to specify the IPV6GATEWAY attribute if you are adding a route for a configured-tunnel SUBNET and you specify this attribute with the name of the tunnel SUBNET.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN Considerations Routes also can be created dynamically through internal routing logic. Routes created by internal route-redirect logic have names in the format: DDcpu_n where cpu is the processor number, in hexadecimal format, of the processor in which the route is generated and n is a decimal number.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN IPv4 only (INET mode) IPv6 only (INET6 mode) DUAL mode (Both IPv4 and IPv6) An IPv6 SUBNET created by using an ADD command cannot be altered to include IPv4 support; if you want the SUBNET to support both IPv6 and IPv4 communications, create the SUBNET by using an ADD command and specifying the FAMILY attribute as DUAL. See IPv6 Examples on page 8-24.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN for the monitors, it is assumed. The 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. There is no default. DEVICENAME lif-name is the name of the device to be opened to connect to the network.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN FAILOVER {SHAREDIP | NONSHAREDIP} enables the SUBNET to be failover-capable using these configurations: 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. MTU size alters the maximum transfer unit (MTU) for messages that the system transmits on the link. The minimum value is 512 bytes.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN To add a SUBNET and associated SUBNET with failover enabled for shared IP addresses: -> ADD SUBNET SN3, TYPE ETHERNET, DEVICENAME LANLIF4, IPADDRESS 172.17.217.44, SUBNETMASK 255.255.255.0, FAILOVER SHAREDIP -> ADD SUBNET SN4, TYPE ETHERNET, DEVICENAME LANLIF5, IPADDRESS 172.17.217.44, SUBNETMASK 255.255.255.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN TYPE ETHERNET is the type of SUBNET to be added. For IPv6 configurations that do not involve tunneling, the only valid type is ETHERNET. (TYPE TUN specifies a SUBNET of type TUNNEL.) DEVICENAME lif-name is the name of the device to be opened to connect to the network. This corresponds to the ServerNet LAN systems access (SLSA) logical interface (LIF). The LIF provides access to the Ethernet LAN.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN The default is ON for an Ethernet SUBNET whose TYPE is ETHERNET. The default is OFF for loopback and tunnel SUBNETs. IPV6MTU int alters the maximum transfer unit (MTU) for messages that the system transmits on the link. The specification for int can range from 1 through the default maximum MTU of the interface/SUBNET. The default maximum for int is 1500 for TYPE ETHERNET SUBNETs and 65535 for loopback SUBNETs. The minimum is 1280.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN Sending an RA message to ND6HOSTD process. Upon receipt of this message, ND6HOSTD process becomes responsible for automatically updating the global address information in DNS. Specifying this attribute as OFF disables the routing table and interface configuration update during the RA message processing. The default value is OFF.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN To create an AF_INET6-capable SUBNET and enable it for Ethernet failover, NONSHAREDIP mode: -> ADD SUBNET $ZZTCP.*.EN1, TYPE ETHERNET, & FAMILY INET6, IPV6PREFIX "3ffe:1200:214:1::/64", & FAILOVER NONSHAREDIP, DEVICENAME LAN21,& IPV6HOPLIMIT 255 To create an AF_INET6-capable SUBNET and enable it for Ethernet failover, SHAREDIP mode: The SUBNET is also enabled to process IPv6 router advertisement messages. -> ADD SUBNET $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN DUAL Mode Command Syntax ADD [ /OUT file-spec/ ] [ SUBNET subnet-spec ] , FAMILY DUAL , TYPE ETHERNET , IPADDRESS ip-addr , DEVICENAME lif-name [ , IRDP { ON | OFF } ] [ , SUBNETMASK mask-val ] [ , IPV6INTERFACEID ipv6-id ] [ , IPV6ADDRESS ipv6-addr ] [ , IPV6PREFIX ipv6-prefix ] [ , IPV6NUD { ON | OFF } ] [ , IPV6MTU int ] [ , IPV6REACHABLETIME int ] [ , IPV6RETRANSMITIMER int ] [ , IPV6DADRETRIES int ] [ , IPV6HOPLIMIT int ] [ , IPV6RAENA
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN DEVICENAME lif-name is the name of the device to be opened to connect to the network. This corresponds to the ServerNet LAN systems access (SLSA) logical interface (LIF). The LIF provides access to the Ethernet LAN. For information on how to choose a SLSA device name, see step 3 on page 1-2. When adding a SUBNET, the DEVICENAME for the SLSA SUBNET does not begin with a dollar sign ($) character. There is no default.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN IPV6ADDRESS "ipv6-addr" specifies the 128-bit Internet address of the IPv6 SUBNET. The address has the format of x:x:x:x:x:x:x:x. In this format, each x is the hexadecimal value of a 16-bit piece of the address. An IPv6 address typically consists of a 64-bit prefix followed by a 64-bit interface identifier. The IPV6ADDRESS attribute can be used to create IP aliases; for more information, see Stateless address autoconfiguration on page 2-17.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN IPV6DADRETRIES int specifies the number of consecutive neighbor solicitation messages that your system transmits when it performs duplicate address detection on a tentative IPv6 address. The specified value must be greater than zero. The default value is 1 for SUBNETs of TYPE ETHERTNET and zero for loopback SUBNETs. IPV6HOPLIMIT int sets the default number of hops to be included in the transmitted unicast IP packets.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN LNP. The maximum number of TCP6SAM processes for a configured LNP is two. The list is specified in quotations with the TCP6SAM processes separated by a comma. For example: LNPTPLIST "$ZSAM1, $ZSAM2" DUAL Mode Examples Note. Before configuring SUBNETs in DUAL mode, you must configure the monitors in DUAL mode. (See I. Prepare to Install and Configure NonStop TCP/IPv6 on page 1-1.).
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN (For examples of adding the associated SUBNET in a failover pair, see the ALTER SUBNET Command for TCP6MAN on page 8-49.) Configured Tunnel SUBNET Command Syntax ADD [ /OUT file-spec/ ] [ SUBNET subnet-spec ] , TYPE TUNNEL , FAMILY INET6 , IPTDST ip-addr , IPTSRC ip-addr OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $ZZTCP.*.subnet-name is the name of the SUBNET object.
SCF Reference for NonStop TCP/IPv6 ADD SUBNET Command for TCP6MAN Configured Tunnel Example This example creates a configured-tunnel SUBNET and enables it for IPv6 operation. You must have a DUAL-mode SUBNET on your host and you must know the IP address of your destination. You must also have a default route to the IPT destination (see ADD ROUTE Command for TCP6MAN on page 8-21). -> ADD SUBNET $ZZTCP.*.IPT1, TYPE TUNNEL, FAMILY INET6, & IPTSRC 16.140.16.86, IPTDST 16.140.16.91 -> ALTER SUBNET $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 ALTER Command To start the loopback SUBNET, you have to do an ALTER SUBNET command as follows (the first example is for INET mode and the second one is for INET6 mode): ->ASSUME PROCESS $ZZTCP ->ABORT SUBNET LOOP0 ->ALTER SUBNET LOOP0, IPADDRESS 127.1 ->ASSUME PROCESS $ZZTCP ->ABORT SUBNET LOOP0 ->ALTER SUBNET LOOP0, IPADDRESS 127.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN so on all configured TCP6MONs. Hence, only the wild card is supported for altering the TCP6MON object. Command Syntax ALTER [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ /OUT file-spec/ ] MON $ZZTCP.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN MON $ZZTCP.* specifies all configured TCP6MONs. When you alter the MON, you must do so on all configured MONs. 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.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN HOSTID int is the identification number (usually the host number part of the Internet address that is assigned to this host). It is a 32-bit number. 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 value is 75 seconds. The range is 1 to 7200. TCPKEEPINTVL int is the time interval in seconds between retransmissions of unacknowledged keepalive packets.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN EXPANDSECURITY { ON | OFF } is not supported in NonStop TCP/IPv6. 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. The default is 60 seconds. The range is 1 to 120.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN MIN-EPHEMERAL-PORT int is the starting port number to allocate for TCP and UDP ephemeral ports. Ephemeral ports are those assigned by NonStop TCP/IPv6 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 on page 8-48 and Examples on page 8-48. See also MAX-PRIV-PORT int on page 8-46.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN FAMILY { INET | INET6 | DUAL } specifies the network mode of the TCP6MON. You can specify these modes: INET TCP6MON is operated in IPv4 only mode. INET6 TCP6MON is operated in IPv6 only mode. DUAL TCP6MON is operated in both IPv4 mode andPv6 mode. TCP-MAX-REXMIT-TIMEOUT is the maximum time value in milliseconds allowed for a TCP retransmission timeout. The default is 64000 milliseconds. The range is 500 to 1200000 (.
SCF Reference for NonStop TCP/IPv6 ALTER MON Command for TCP6MAN The supported incoming ICMP packets (type, bit, hex value) are currently supported: ICMP packet type Bit code ICMP-FILTER-PKTS < Val> ICMP_REDIRECT ICMP_ECHO ICMP_TSTAMP 5 %h00000020 %h00000100 ICMP_IREQ ICMP_MASKREQ 15 8 %h00002000 %h00008000 %h00020000 13 17 The default value is %H00000000. Examples To alter the DELAYACKS and DELAYACKSTIME attributes on all configured TCP6MONs: -> ALTER MON $ZZTCP.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN ran in different processors, the bind succeeded. The successful bind for applications running in different processors and binding to the same port but to different addresses was non-standard behavior for most TCP/IP implementations. As of the G06.24 RVU, the default behavior for applications in different processors binding to the same port and different addresses is failure to bind.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for HSeries RVUs. FAMILY INET specifies that the socket-family type of the SUBNET as AF_INET (IPv4). The default value for the FAMILY attribute is INET. IPADDRESS ip_address is the 32-bit integer that identifies the SUBNET. This is the IPv4 address assigned to the SUBNET by the network administrator.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN For information about alias IP addresses in Ethernet failover considerations, see Considerations on page 8-58. DELETEALIAS ip-addr allows the deletion of alias IP addresses that have been added by the ADDALIAS attribute. MTU size alters the maximum transfer unit (MTU) for messages that the system transmits on the link. The minimum value is 512 bytes. The maximum value is 65535 bytes.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN alters all SUBNETs on all TCP6MONs. 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 or the SCF Reference Manual for HSeries RVUs. ADDIPV6ADDRESS "ipv6-addr" specifies the 128-bit IPv6) address to be added, in this format: x:x:x:x:x:x:x:x Each x represents the hexadecimal value of a 16-bit piece of the address.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN IPV6 UP | DOWN initializes (UP) or removes (DOWN) IPv6-related data structures and assigns an IPv6 link-local address to the interface. If this attribute is DOWN, it removes any IPv6 configuration associated with the interface, including all IPv6 addresses and IPv6 routes through the interface. IPV6NUD ON | OFF enables (ON) or disables (OFF) Neighbor Unreachability Detection.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN Sending an RA message to ND6HOSTD process. Upon receipt of this message, ND6HOSTD process becomes responsible for automatically updating the global address information in DNS. Specifying this attribute as OFF disables the routing table and interface configuration update during the RA message processing. The default value is OFF.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN INET and INET6 Command Syntax for Failover Association ALTER [ /OUT file-spec/ ] [SUBNET $ZZTCP.*.subnet-name ] [ , ASSOCIATESUB "subnet-name" ] [ { , RESERVEDIP ip-addr | IPV6RESERVEDID ipv6-id } ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $ZZTCP.*.subnet-name is the name of one of the SUBNETs you are associating. The fully-qualified SUBNET name is $ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN Failover Examples Example 8-1 links the two IPv4 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. Example 8-1. Nonshared IP Ethernet Failover, INET Mode -> ASSUME PROCESS $ZZTCP -> ADD SUBNET SN1,TYPE ETHERNET, DEVICENAME LANLIF2, & IPADDRESS 172.17.217.232, SUBNETMASK 255.255.255.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN IPV6INTERFACEDID specification. This is required when you use a SHAREDIP configuration. Example 8-4.
SCF Reference for NonStop TCP/IPv6 ALTER SUBNET Command for TCP6MAN Example 8-6. Shared IP Ethernet Failover, DUAL Mode -> ADD SUBNET EN1, TYPE ETHERNET, FAMILY DUAL, & IPADDRESS 172.17.215.232, SUBNETMASK 255.255.255.0, & IPV6RAENABLE OFF,& IPV6INTERFACEID "::ABCD:1234", & FAILOVER SHAREDIP, DEVICENAME LAN02,& IPV6HOPLIMIT 255 -> ADD SUBNET EN2, TYPE ETHERNET, FAMILY DUAL, & IPADDRESS 172.17.215.232, SUBNETMASK 255.255.255.
SCF Reference for NonStop TCP/IPv6 DELETE Command Alias IP addresses are added by using the ALTER SUBNET, ADDALIAS command. This consideration documents the failover behavior of alias IP addresses. If the SUBNET is configured for failover, all IP aliases are also configured for failover as long as the IP alias address is added to both SUBNETs in the failover pair. This arrangement is true for both SHARED and NONSHARED failover configurations.
SCF Reference for NonStop TCP/IPv6 DELETE ROUTE Command for TCP6MAN Command Syntax DELETE [ /OUT file-spec/ ] [ ENTRY $ZZTCP.*.entry-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. 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 TCP6MONs). You can delete all entries by substituting the wild card (*) for the entry-name.
SCF Reference for NonStop TCP/IPv6 DELETE SUBNET Command for TCP6MAN ROUTE $ZZTCP.#ZPTMn.route-name is the name of the route. When you delete a route, you must do so on all configured TCP6MONs (except dynamic routes, see the second example below. You can use the wild-card (*) notation for the TCP6MON name, but if you do not, it is assumed. For example, DELETE ROUTE *.RT1 is equivalent to DELETE ROUTE RT1. You can substitute the wild card (*) for the route-name to delete all routes.
SCF Reference for NonStop TCP/IPv6 INFO Command SUBNET $ZZTCP.*.subnet-name is the name of the SUBNET. Because you must delete SUBNETs on all configured TCP6MONs, the wild card (*) is assumed for the TCP6MON name. You can also substitute the wild card (*) for the subnet-name to delete all SUBNETs. If you omit the process name, or the SUBNET name, SCF uses the assumed object name.
SCF Reference for NonStop TCP/IPv6 INFO ENTRY Command for TCP6MAN INFO ENTRY Command for TCP6MAN The INFO ENTRY command displays: An entry or entries in the ARP table, or An entry or entries in the IPv6 Neighbor Discovery cache, or Entries in both the ARP table and the Neighbor Discovery Cache (environments in which IPv4 and IPv6 coexist). Note. In IPv4 environments an SCF ADD command can be used to define an ENTRY object. Such objects always begin with the alphabetic characters EA.
SCF Reference for NonStop TCP/IPv6 INFO ENTRY Command for TCP6MAN If you specify entry-name with a wild card (*) and also specify INET, the resulting display shows only information about ARP table entries. If you specify entry-name with a wild card (*) and also specify INET6, the resulting display shows only information about entries in the Neighbor Discovery cache.
SCF Reference for NonStop TCP/IPv6 INFO ENTRY Command for TCP6MAN Name is the name of the entry. The entry type is indicated in parentheses to the right. In this case, the type is ARP. IPADDRESS is the IP address for the entry in dotted decimal format. MacAddress is the MAC (physical) address of the entry in hexadecimal format. ALLENTRY indicates, when ON, that the entry was added through an SCF ADD command and that the command specified the ALLENTRY option.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN ALLENTRY should always display OFF for an entry in the neighbor discovery cache. An ENTRY object cannot be added for an entry in the neighbor discovery cache, and therefore, no ALLENTRY attribute can be specified through SCF. Associated Subnet indicates the SUBNET with which this entry is associated.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN Command Syntax INFO[ /OUT file-spec/] [ MON [, DETAIL | , OBEYFORM] $ZZTCP.#ZPTMn ] 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 TCP6MON. The TCP6MON is always named #ZPTMn where n is the hexadecimal number of the processor in which the TCP6MON is running. If you want to get info on a specific TCP6MON, you must specify the TCP6MON number.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN TCP Send Space is the space reserved for send operations for the TCP protocol. TCP Receive Space is the space reserved for receive operations for the TCP protocol. UDP Send Space is the space reserved for send operations for the UDP protocol. UDP Receive Space is the space reserved for receive operations for the UDP protocol. INFO MON, DETAIL Display Format The format of the display for the INFO MON $ZZTCP.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN Note. The ARPTIMER-REFRESHED, ICMP-FILTER-PKTS, and PORT-SHARE-ENABLE attributes are supported only on systems running G06.29 and later G-series TCP Send Space is the space reserved for send operations for the TCP protocol. TCP Receive Space is the space reserved for receive operations for the TCP protocol. UDP Send Space is the space reserved for send operations for the UDP protocol.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN Host Name is the official name the host upon which the NonStop TCP/IPv6 subsystem is running is known in the Internet. This is a character string no longer than 50 characters. The default is the EXPAND node name with the leading “\” stripped off. Program File Name is the name of the file that is being executed for this process. Debug is the current setting (ON or OFF) of the DEBUG attribute.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN TCP Time Wait is the amount of time in seconds that a TCP connection remains in the TIME_WAIT state. The default is 60 seconds. The range is 1 to 120. Trace Status is ON when the process is being traced using SCF. Trace Filename is the name of the current trace file. ARPTIMER-REFRESHED causes TCP to restart the ARP timer every time the ARP table entry is referenced when transmitting an IP packet. The default value is ON.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN otherwise the queue length in the socket request is used. The default value is 128. The range is 1 to 1024. Initial TTL specifies the initial value for UDP and TCP TTL (Time To Live). The default is 64, but can be altered to 30. Min-Ephemeral-Port is the starting port number to allocate for TCP and UDP ephemeral ports. Ephemeral ports are those assigned by NonStop TCP/IPv6 when an application has not bound to a specific port.
SCF Reference for NonStop TCP/IPv6 INFO MON Command for TCP6MAN NONSHAREDOUTDIST specifies whether or not the outbound data paths for connections over Nonshared IP failover pairs are distributed over both SUBNETs of the failover pair. On enables distribution over both SUBNETs. OFF disables it. FAMILY specifies the network mode of the TCP6MON. Possible values are INET, INET6, and DUAL. Total LNPs Configured is the number, not counting the default LNP, of logical-network partitions configured.
SCF Reference for NonStop TCP/IPv6 INFO PROCESS Command for TCP6MAN The default value is %H00000000. Note. The ICMP-FILTER-PKTS attribute is supported only on systems running G06.29 and later G-series RVUs. PORT-SHARE-ENABLE When set to ON allows applications running on different processors to bind to the same UDP or TCP port with different local address specifications. For example, a specific address versus INADDR_ANY. Before G06.
SCF Reference for NonStop TCP/IPv6 INFO PROCESS Command for TCP6MAN Command Syntax INFO [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [ , DETAIL ] 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 manager process (TCP6MAN). 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 or the SCF Reference Manual for H-Series RVUs.
SCF Reference for NonStop TCP/IPv6 INFO PROCESS Command for TCP6SAM BPID is the backup processor and PIN of the process. INFO PROCESS Command for TCP6SAM This command displays the current attribute settings for the TCP6SAM process. Command Syntax INFO [ / OUT file-spec / ] [ PROCESS TCP6SAM-name ] [, DETAIL] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. DETAIL specifies that the display is to include additional detailed information on the object.
SCF Reference for NonStop TCP/IPv6 INFO PROCESS Command for TCP6SAM INFO PROCESS, DETAIL for TCP6SAM Display Format The format of the display for the INFO PROCESS, DETAIL command for the second example is: TCPIP Detailed Info PROCESS \MYSYS.$SAM1 *TCP Send Space ...... 8192 *TCP Receive Space .. *UDP Send Space ...... 2048 *UDP Receive Space .. *Delay Ack Time....... 20 *Delay Ack........... *Keep Alive Idle...... 7200 *Keep Alive Retry Cnt *Keep Alive Interval.. 75 QIO Limit........... *Host Id..........
SCF Reference for NonStop TCP/IPv6 INFO PROCESS Command for TCP6SAM Delay Ack Time is the amount of time (in.01-second units) that acknowledgments are delayed. Delay Ack indicates whether the acknowledgment (ACK) should be delayed when a TCP packet is received from a remote site. 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 NonStop TCP/IPv6 INFO PROCESS Command for TCP6SAM All Nets Are Local The default is ON. ON causes TCP to use the interface MTU as a base for determining 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). If ALLNETSARELOCAL is OFF, TCP conforms to RFC-specified behavior and use 512 bytes as the default MSS for non-local segments.
SCF Reference for NonStop TCP/IPv6 INFO PROCESS Command for TCP6SAM RFC1323 Enable is ON to cause TCP to support TCP Large Windows as documented in RFC 1323. When this option is enabled, NonStop TCP/IPv6 uses the TCP Window Scale and Timestamp options as described in RFC 1323. The largest TCP window supported is 262144 bytes when this option is enabled, and 65535 when the option is disabled. The default for this option is ON.
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6MAN Considerations Although the detailed display option for the PROCESS object has an asterisk (*) in front of some fields, they are not alterable. TCP6SAM does not support the ALTER command. To alter those parameters which have an asterisk (*) in front of them in the display, alter the TCP6MON object instead. INFO ROUTE Command for TCP6MAN The INFO ROUTE command for TCP6MAN displays attribute values for the specified route(s).
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6MAN OBEYFORM causes the static route configuration to be displayed in ADD ROUTE format, so that this configuration can be re-created. Examples To return the attributes of routes configured on the TCP6MON in processor 2: -> INFO ROUTE $ZZTCP.#ZPTM2.
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6MAN INFO ROUTE Display Format This display shows the output of the first INFO ROUTE command: TCPIPV6 Info ROUTE \MYSYS.$ZZTCP.#ZPTM2.* AF_INET: Name Subnet RT1 RT4 RT8 RT9 DEF DA2_3 DR2_1 DEF RT7 LOOP0 EN1 EN1 EN1 EN1 EN1 EN2 EN1 EN1 Destination 127.0.0.1 172.17.0.0 172.17.215.0 172.17.215.232 0.0.0.0 172.17.215.1 0.0.0.0 0.0.0.0 130.186.72.
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6MAN where cpu is the processor number, in hexadecimal format, of the processor in which the route is generated and n is a decimal number. Routes created by ARP link-level logic have names in the format: DAcpu_n where cpu is the processor number, in hexadecimal format, of the processor in which the route is generated and n is a decimal number.
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6MAN Type indicates one of these: 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). 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 NonStop TCP/IPv6 INFO ROUTE Command for TCP6SAM Considerations The implicit route generated internally from the ADD SUBNET command has the cloning flag set. For a detailed description of the cloning capability of a route, see the ADD ROUTE help text. 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.
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6SAM INFO ROUTE Display Format This display shows the output of the INFO ROUTE command shown in the first example: TCPIP Info ROUTE \MYSYS.$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.
SCF Reference for NonStop TCP/IPv6 INFO ROUTE Command for TCP6SAM Subnetname specifies the name of the subnetwork interface that is used by a specific route. Destination is the remote machine or network that can be reached via the machine specified in the GATEWAY or IPV6GATEWAY. The specified destination appears in dotted decimal format. IPv6 addresses do not display for TCP6SAM.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN INFO SUBNET Command for TCP6MAN 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 | , FAMILY { INET | INET6 } ] | [, 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.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN OBEYFORM causes the SUBNET configuration to be displayed in ADD SUBNET and ALTER SUBNET formats so that this configuration can be re-created. Examples To return information about a specific SUBNET: -> INFO SUBNET $ZZTCP.#ZPTM1.SN1 To return information about all running SUBNETs on the system: -> INFO SUBNET $ZZTCP.#ZPTM3.* To return detailed information about a specific SUBNET: -> INFO SUBNET $ZZTCP.#ZPTM3.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN IPADDRESS is the Internet address of this SUBNET and all the IP addresses of the aliases associated with the SUBNET. TYPE is the SUBNET type. Possible values are Ethernet, loopback, and tunnel (either automatic or configured). 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.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN IPADDRESS is the IPv4 Internet address of this SUBNET and all the IPv4 addresses of the aliases associated with the SUBNET. TYPE is the SUBNET type. Possible values are Ethernet, loopback and tunnel (either automatic or configured). 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.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN INFO SUBNET, DETAIL for the TCP6MAN Display Format The format of the display for the INFO SUBNET, DETAIL is: TCPIPV6 Detailed Info SUBNET \MYSYS.$ZZTCP.#ZPTM3.* AF_INET: Name Devicename *IPADDRESS TYPE *SUBNETMASK *R SN2 \MYSYS.LAN14 172.16.214.28 ETHERNET %HFFFFFF00 Trace Status ........ OFF Trace Filename ...... Interface MTU ....... 1500 LNP ... $ZSAM1, $ZSAM2 INDEX ... 1 ---Multicast Groups-----State--224.0.0.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN Detailed INFO SUBNET display continued: SN1 \MYSYS.LAN12 fe80::a00:8eff:fe04:6ef2 ETHERNET *IPV6MTU................... 1500 *IPV6HOPLIMIT.............. 64 *IPV6REACHABLETIME......... 30000 ms *IPV6RETRANSMITIMER........ 1000 ms *IPV6DADRETRIES............ 1 *IPV6NUD................... ON *IPV6RAENABLE.............. ON LNP... DEFAULT INDEX ... 0 IPV6PREFIX........ 3ffe:1200:214:1::/64 IPV6ADDRESS.......
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN TYPE is the SUBNET type. Possible values are Ethernet, loopback, and tunnel (either automatic or configured). 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. Trace Status shows whether the SUBNET is being traced. ON indicates that it is being traced. Trace Filename is the name of the current trace file.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN IPV6ADDRESS is a IPv6 unicast address assigned to the interface/SUBNET. The Creation Type subfield indicated the creation or configuration type of the address.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6MAN IPV6RETRANSMITIMER is the number of milliseconds between solicitations. IPV6DADRETRIES is number of times to perform duplicate address detection IPV6NUD indicates whether neighbor unreachability detection is enables (ON) or disabled (OFF) IPV6RAENABLE indicates whether the TCP6MON process is enabled (ON) to perform these tasks when a router advertisement (RA) is received: Router Discovery.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6SAM INFO SUBNET for TCP6MAN with the OBEYFORM Display Format The format of the display for the INFO SUBNET, OBEYFORM command is: ALTER SUBNET LOOP0 , IPADDRESS 127.0.0.1 ADD SUBNET EN1 , TYPE ETHERNET,& IPADDRESS 172.17.222.15 , SUBNETMASK %HFFFFFF00 ,& DEVICENAME \MYSYS.LANLIF1, FAILOVER NONSHAREDIP ALTER SUBNET EN1 , ASSOCIATESUB "EN2" ALTER SUBNET EN1 , ADDALIAS 172.17.222.120 ALTER SUBNET EN1 , ADDALIAS 172.17.222.
SCF Reference for NonStop TCP/IPv6 INFO SUBNET Command for TCP6SAM Examples To return information about all running SUBNETs on the TCP6MON object running in TCP6SAM’s primary processor: -> INFO SUBNET $ZTC1.* INFO SUBNET for TCP6SAM Display Format The format of the INFO SUBNET display for TCP6SAM is (an asterisk (*) indicates an alterable attribute): TCPIP Info SUBNET \MYSYS.$ZTC1.* Name Devicename *IPADDRESS TYPE #LOOP0 \NOSYS.$NOIOP 127.0.0.
SCF Reference for NonStop TCP/IPv6 LISTOPENS Command 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. OFF indicates that the interface is not currently using QIO mode. 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).
SCF Reference for NonStop TCP/IPv6 LISTOPENS MON Command for TCP6MAN To request detailed information about the openers of the specified process: -> LISTOPENS MON $ZZTCP.#ZPTM1, DETAIL LISTOPENS MON Display Format The format of the display for the LISTOPENS MON $ZZTCP.#ZPTM1 command is: TCPIPV6 LISTOPENS MON \MYSYS.$ZZTCP.#ZPTM1 OPENERS $ZNET $ZPORT PPID 13,234 3,52 BPID PLFN 2 5 BLFN 0 0 PROTOCOL #ZSPI TCP LPORT * FTP Note. An asterisk (*) indicates an alterable attribute.
SCF Reference for NonStop TCP/IPv6 LISTOPENS MON Command for TCP6MAN LISTOPENS MON, DETAIL Display Format The format of the display for the LISTOPENS MON, DETAIL command is: TCPIPV6 LISTOPENS MON \MYSYS.$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 NonStop TCP/IPv6 LISTOPENS PROCESS Command for TCP6SAM 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.
SCF Reference for NonStop TCP/IPv6 LISTOPENS PROCESS Command for TCP6SAM DETAIL specifies that the display is to include additional detailed information on the object.
SCF Reference for NonStop TCP/IPv6 LISTOPENS PROCESS Command for TCP6SAM Ppid is the primary processor and process ID of the opener. 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 NonStop TCP/IPv6 NAMES Command Fport is the foreign port number for either TCP or UDP depending on the protocol listed in the PROTO field. FPORT 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. NAMES Command The NAMES command displays the names of the specified NonStop TCP/IPv6 objects. This is a nonsensitive command.
SCF Reference for NonStop TCP/IPv6 NAMES ROUTE Command for TCP6MAN NAMES ENTRY Display Format The display format of the NAMES ENTRY command is: TCPIPV6 Names ENTRY \MYSYS.$ZZTCP.#ZPTM2.* ENTRY DA2_1 EA01 NAMES ROUTE Command for TCP6MAN The NAMES ROUTE command displays the names of the routes for the NonStop TCP/IPv6 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.
SCF Reference for NonStop TCP/IPv6 NAMES ROUTE Command for TCP6SAM NAMES ROUTE Display Format The format of the display for the NAMES ROUTE command is: TCPIPV6 Names ROUTE \MYSYS.$ZZTCP.#zptm1.* ROUTE RT1 RT3 DEF The format of the display for the NAMES ROUTE command for all routes in the NonStop TCP/IPv6 is: TCPIPV6 Names ROUTE \MYSYS.$ZZTCP.*.
SCF Reference for NonStop TCP/IPv6 NAMES SUBNET Command for TCP6MAN NAMES ROUTE for TCP6SAM Display Format The format of the display for the NAMES ROUTE command (shown in the Example) is: TCPIP Names ROUTE \MYSYS.$ZTC1.* ROUTE #RT7 #RT8 #RT10 #DA2_2 #DEF NAMES SUBNET Command for TCP6MAN The NAMES SUBNET command for TCP6MAN displays the names of the SUBNETs for the NonStop TCP/IPv6 subsystem in a configured TCP6MON or in all configured TCP6MONs.
SCF Reference for NonStop TCP/IPv6 NAMES SUBNET Command for TCP6SAM NAMES SUBNET Command for TCP6SAM NAMES SUBNET for TCP6SAM displays the names of the SUBNETs configured on the TCP6MON process in the same processor. Command Syntax NAMES [ / OUT file-spec / ] [ SUBNET $TCP6SAM-name.* ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $TCP6SAM-name.subnet-name is the name of the SUBNET.
SCF Reference for NonStop TCP/IPv6 PRIMARY Command PRIMARY Command The PRIMARY command can be used when the NonStop TCP/IPv6 subsystem is running as a fault-tolerant process pair. This command causes the backup processor to become the primary processor and the primary processor to become the backup processor. This is a sensitive command.
SCF Reference for NonStop TCP/IPv6 PRIMARY PROCESS Command for TCP6SAM PRIMARY PROCESS Command for TCP6SAM The SCF PRIMARY PROCESS in TCP6SAM lets you switch connections to a backup processor. The information maintained about the Guardian sockets is checkpointed to the backup when the backup is started. This lets the TCP6SAM process switch the roles of the primary and backup processes.
SCF Reference for NonStop TCP/IPv6 START MON Command for TCP6MAN START MON Command for TCP6MAN The START MON command is used to start individual TCP6MON objects on each processor. MONs are automatically started by TCP6MAN if they were previously started by using SCF and were not aborted. Command Syntax START [ / OUT file-spec / ] MON $ZZTCP.#ZPTM{0-F } OUT file-spec causes any SCF output generated for this command to be directed to the specified file. $ZZTCP.#ZPTM{0-F } is the name of the TCP6MON.
SCF Reference for NonStop TCP/IPv6 START ROUTE Command for TCP6MAN START ROUTE Command for TCP6MAN The START ROUTE command creates implicit connections to and from a route. The successful completion of the START command leaves the route in the STARTED summary state. Command Syntax START [ / OUT file-spec / ] [ROUTE $ZZTCP.*.route-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE $ZZTCP.*.route-name is the name of the route.
SCF Reference for NonStop TCP/IPv6 STATS Command SUBNET $ZZTCP.#ZPTMn.subnet-name is the name of the SUBNET. The fully-qualified SUBNET name is $ZZTCP.*.subnet-name (you must alter the SUBNET on all configured TCP6MONs). If you do not substitute the wild card (*) for the TCP6MON name, it is assumed. If you omit the process or SUBNET name, SCF uses the assumed object name. For information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for H-Series RVUs.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Whenever a RESET option is included, the counters associated with the specified objects are displayed and reset to 0, and the timestamp for the reset is recorded. Any STATS command returns the time at which the current statistics were sampled and the time at which the counters were last reset. This is a nonsensitive command except when used with the reset option. When used with the reset option, it is a sensitive command.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN STATS MON Display Format The format of the display for the STATS MON command (shown in the example) is: TCPIPV6 Stats MON \MYSYS.$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...16 Connection Timeouts.1 Total PKTs Input.....12280 Total PKTs Output...
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN The STATS MON command display (continued) is: UDP LAYER STATS PKTS with no Chksum.0 Bad Packet Size.....0 Total PKTS Output...0 Output PKTs Dropped.0 No sock on port.....0 NotDeliver,Sockfull.0 IP LAYER STATS Bad Checksum.........0 Un Known/Supp Proto.7142 Invalid Header Size..0 Bad Packet Size.....0 Fragments Input......0 Fragments Dropped...0 Packets Cant Forward.0 ICMP Redirects Sent.0 Short Packets........0 Packets Too Small...
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN The STATS MON command display (continued) is: Total PKTs Output....0 Multicast PKTs Out...0 Fwd PKT Error........0 Fwd PKT Bad Dst......0 Fwd PKT No Buffers...0 IPv6 TRANSMIT LAYER STATS Transmit Failures...0 PKTs Forwarded......0 Looped Multicast....0 Fwd PKT Bad Src.....0 PKTs PKT Bad Size...0 Packets Fragmented...0 No Frag in PKT.......0 Unfrag Not Aligned...0 PKT Hdr Too Big......0 Allocation Failures..0 PKTs Reassembled.....
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN The STATS MON command display (continued) is: ICMPV6 and MLD LAYER STATS Total Error PKTs Sent. 0D Error PKTs Not Sent... 0D No Buffer Errors...... 0D Rate Limit Errors..... 0D Total Input PKTs...... 21D Total Info PKTs....... 21D Total Error PKTs...... 0D Short Packets......... 0D Bad Checksum.......... 0D Raw Socket Deliveries. 21D In Dest Unreachable... 0D Out Dest Unreachable.. 0D In PKT To Big......... 0D Out PKT To Big........
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Statistics Definitions (in Alphabetic Order) Reset Time is the time at which the counters were last initialized (set to zero). Sample Time is the time at which the statistics were sampled. Description of Statistics for the TCP Layer ACK Packets Sent is the number of ACK packets sent. Bad Checksum is the number of packets received with invalid checksum values.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Data Bytes Received is the number of bytes received in sequence. Data Bytes Sent is the total number of data bytes sent. Data Packets Received is the number of packets received in sequence. Data Packets Sent is the total number of data packets sent. Delayed ACKs Sent is the number of delayed ACKs sent. Duplicate Bytes Recv is the number of duplicate bytes received. Duplicate PKTs Recv is the number of duplicate packets received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN No Ports For Packets is the number of packets received for a connection that has been closed or does not exist. This event can be a normal occurrence or it can be caused by a faulty NonStop TCP/IPv6 implementation that does not conform to the NonStop TCP/IPv6 state table. Outgoing Connect is the number of connection requests sent to remote hosts. Out Of Order PKTs Rcv is the number of out-of-order packets received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Retransmit Timeouts is the number of retransmit timeouts. RTT Updated is the number of round-trip times updated. Segments RTT is the number of segments where round-trip time was attempted. Too Short is the number of packets received that were too short. Total PKTs Input is the number of packets received. Total PKTs Output is the number of packets sent down to the IP layer.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN SYN Cache Timed Out is the number of SYN cache entries timed out. SYN Cache Drop, OvF is the number of SYN cache entries dropped because of overflow. SYN Cache Drop, RST is the number of SYN cache entries dropped because of RST. SYN Cache Drop, UnR is the number of SYN cache entries dropped because of ICMP unreachable. SYN Cache Drop, BOvF is the number of SYN cache entries dropped because of bucket overflow.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN No sock on port is the number of sockets with no port. Nosock on port, Bdcst is the number of sockets with no port which arrived as broadcast. NotDeliver,Sockfull is the number of packets not delivered, input socket full. Output PKTs Dropped is the number of packets not sent because of interface problems. Pkts, Miss pcb Cach is the number of input packets missing pcb cache.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Discarded, No Route is the number of packets discarded because of no route. Fragments Dropped is the number of packet fragments dropped. A fragment is dropped either when memory cannot be allocated for the fragment or when the fragment is a duplicate of a fragment that has already been received. Fragments Input is the number of packet fragments received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Packets, Dont Fragment is the number of packets with don't fragment flag set. Packets Forwarded is the number of packets destined for another host that were forwarded. Packets Fragmented is the number of datagrams successfully fragmented. Packets,reassembled shows the total number of IP packets successfully reassembled.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Description of Statistics for IP Routing (in Alphabetic Order) Bad Route Redirects is the number of Redirect messages received. Dynamic Redirects is the number of dynamic route messages received. These messages indicate where the NonStop TCP/IPv6 subsystem should route messages for a specific destination. New Gateway Redirect is the number of messages received that established a route for a new or an unknown gateway.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Rcvd Local Addr is the number of packets with one of our addresses received. Rcvd Multicast is the number of multicast packets received. For information about multicast addressing, see the TCP/IP Programming Manual. Rcvd Non-Aligned is the number of times a packet was adjusted because the IPv6 header was not aligned correctly. The packet is still accepted.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Frag Jumbo Payload the number of received fragments with the jumbo payload option. Fragment Bad Length the number of packets that have the more-fragment flag set and whose packet length is not a multiple of 8. Fragment Overlap the number of partial fragment packets for which overlaps have been detected during reassembly. Fragments Received is the total number of fragments received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Total Frags Built is the total number of fragments built. Tx Unfrag Too Big is the number of transmit packets with an un-fragmented part that is too big. Unfrag Not Aligned is the number of packets with un-fragmented part not quad word aligned. Unfrag PKT Copied is the count of unfragmented part of packets copied for reassembly.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Bad ICMP Code is the number of packets received that contain invalid ICMP packet-type codes in the header.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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. The Echo message is sent from the source address to the destination address.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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/IPv6 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. In Source Quench is the number of Source Quench (type 4) messages received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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 NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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/IPv6 subsystem. The NonStop TCP/IPv6 subsystem either records these routes or ignore them, depending on how IRDP is configured and according to route preference.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN In Time Exceeded is the total number of Time Exceed Exceeded message received. In Total MLD Reports is the total number of Multicast Listener Discovery reports received. For information about multicast addressing, see the TCP/IP Programming Manual. MLD Bad Queries is the total number of Bad Multicast Listener Discovery Queries received. For information about multicast addressing, see the TCP/IP Programming Manual.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Out PKT To Big is the total number of Packet To Big messages sent. Out Time Exceeded total time exceeded message sent. Rate Limit Errors is the number of error packets not sent because of rate limit. Raw Socket Deliveries is the total number of packets passed to possible ICMPv6 listeners. Short Packets is the total number of short packets received. Total Error PKTs is the total number of ICMPv6 error class packets received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN Bad ND Options is the count of ND6 packets with bad options. Bad Redirect is the number of bad redirect messages received. Bad Rtr Advert is the number of bad ND6 router advertisement messages received. Bad Rtr Solicit is the number of bad ND6 router solicitation messages received. In ND Router Advert is the number of router advertisement packets received. In Neighbor Advert is the number of neighbor advertisement packets received.
SCF Reference for NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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 NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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 NonStop TCP/IPv6 STATS MON Command for TCP6MAN 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. Size 32769 and larger is the count of socket sends greater than 32769 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.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM Description of Statistics for IGMP Statistics (in Displayed Order) Total Packets Input is the total number of IGMP packets received. 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.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM PROCESS $TCP6SAM-name is the name of the TCP6SAM 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 or the SCF Reference Manual for H-Series RVUs.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM STATS PROCESS for TCP6SAM Display Format The format of the display for the STATS PROCESS command shown in the example is: TCPIP Stats PROCESS \SYSA.$ZSAM1 Sample Time ... 17 Oct 1999, 17:17:41.169 Reset Time .... Invalid date/time TCP LAYER STATS Bad Checksum.......... 0D Bad Offset............ Invalid Header Size... 0D Bad Segment Size...... Retransmitted Packets. 608D Connection Timeouts... Total Packets Input...
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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......... Bad Router Adv Subcode Bad Router Words/Addr.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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. Bad Offset is the number of packets received with invalid data offsets in their TCP headers.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM Connections Dropped is the number of connections dropped. Control Packets Sent is the number of SYN, FIN, and RST control packets sent. Data Bytes Received is the number of bytes received in sequence. Data Bytes Sent is the total number of data bytes sent. Data Packets Received is the number of packets received in sequence. Data Packets Sent is the total number of data packets sent.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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. Keep-Alive Timeouts is the number of keep-alive timeouts.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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 NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM Window Probe PKTs Recv is the number of window-probes packets received. Window Update Pkts is the number of window update packets received. Description of Statistics for the UDP Layer (in Alphabetic Order) Bad Checksum is the number of packets received with invalid checksum values. An invalid checksum is usually caused by a noisy link.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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. Fragments Dropped is the number of packet fragments dropped. A fragment is dropped either when memory cannot be allocated for the fragment or when the fragment is a duplicate of a fragment that has already been received.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM Short Packets is the number of packets that contained less data than specified in their header. This can be caused by noisy links, a protocol error by the sender of the packet, or a byte-swapping problem on the receiver. Total Packets Input is the number of packets received. Total Packets Output is the number of packets sent to the IP layer.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM Bad ICMP Code is the number of packets received that contain invalid ICMP packet-type codes in the header.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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. The Echo message is sent from the source address to the destination address.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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. In Source Quench is the number of Source Quench (type 4) messages received.
SCF Reference for NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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 NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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 NonStop TCP/IPv6 STATS PROCESS Command for TCP6SAM 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 NonStop TCP/IPv6 STATS ROUTE Command for TCP6MAN 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 NonStop TCP/IPv6 STATS ROUTE Command for TCP6MAN Command Syntax STATS [ / OUT file-spec / ] [ROUTE $ZZTCP.#ZPTMn.route-name] [, FAMILY { INET | INET6 } ] [, CPU n ] [, RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ROUTE $ZZTCP.#ZPTMn.route-name is the name of the route. The fully-qualified name for the ROUTE is $ZZTCP.#ZPTM{0-F}.route-name. If you omit the object name, SCF uses the assumed object name.
SCF Reference for NonStop TCP/IPv6 STATS ROUTE Command for TCP6MAN STATS ROUTE Display Format The format of the display for the STATS ROUTE command shown in the example is: TCPIPV6 Stats ROUTE \MYSYS.$ZZTCP.#ZPTM2.* Sample Time ... 04 Jan 2000, 9:59:02.491 Reset Time .... 03 Jan 2000, 9:35:14.535 Name RT1 AssociateSub EN2 Route Usage 0D FAMILY INET Sample Time ... 14 Nov 2002, 9:59:02.491 Reset Time .... 14 Nov 2002, 9:35:14.
SCF Reference for NonStop TCP/IPv6 STATS ROUTE Command for TCP6SAM STATS ROUTE Command for TCP6SAM The STATS ROUTE command displays the NonStop TCP/IPv6 subsystem statistics for the specified routes in the processor containing the TCP6SAM process. Note. STATS ROUTE with the RESET option is sensitive. Command Syntax STATS [ / OUT file-spec / ] [ROUTE $TCP6SAM-name.route-name] [, RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Reference for NonStop TCP/IPv6 STATS SUBNET Command for TCP6MAN Reset Time is the time when the counters were last reset to zero. Name is the name of the route. Route Usage is the number of times this route was used to send IP datagrams. STATS SUBNET Command for TCP6MAN The STATS SUBNET command displays the statistical information for the specified SUBNETs in a given TCP6MON or in all configured TCP6MONs. Command Syntax STATS [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.
SCF Reference for NonStop TCP/IPv6 STATS SUBNET Command for TCP6MAN To request statistics for all running SUBNETs: -> STATS SUBNET $ZZTCP.*.* STATS SUBNET Display Format The format of the display the STATS SUBNET command is: TCPIPV6 Stats SUBNET \MYSYS.$ZZTCP.#ZPTM3.SN* Sample Time ... 28 Jan 2000, 13:49:48.912 Reset Time .... 28 Jan 2000, 13:40:30.682 Name EN1 Filter Errors........0 Output Packets.......0 Output Errors........0 TCP filters Reg......0 TCP filters Dereg....0 UDP filters Error....
SCF Reference for NonStop TCP/IPv6 STATS SUBNET Command for TCP6MAN 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. Output Errors is the number of errors that occurred when packets were sent by the SUBNET.
SCF Reference for NonStop TCP/IPv6 STATS SUBNET Command for TCP6SAM 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 is a nonsensitive command without the RESET option; it is a sensitive command with the RESET option.
SCF Reference for NonStop TCP/IPv6 STATS SUBNET Command for TCP6SAM DETAIL requests the detailed status information for the SUBNET. Example To request statistics for all running SUBNETs in the processor containing the TCP6SAM process: ->STATS SUBNET $ZSAM1.* STATS SUBNET for TCP6SAM Display Format The format of the display for the STATS SUBNET command shown in the example is: TCPIP Stats SUBNET \MYSYS.$ZSAM1.* Sample Time ... 19 Feb 1998, 9:00:56:.054 Reset time ... 18 Feb 1998, 21:09:10.
SCF Reference for NonStop TCP/IPv6 STATUS Command 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. Each output error also generates one of these operator messages: DEVICE READ ERROR error ON IOP iopname DEVICE WRITE ERROR error ON IOP iopname ERROR error ON IOP iopname Input Errors is the number of errors detected when packets were received by the SUBNET.
SCF Reference for NonStop TCP/IPv6 STATUS ENTRY Command for TCP6MAN ENTRY $ZZTCP.#ZPTMn.entry-name is the name of the entry. The fully-qualified name of the entry object is $ZZTCP.#ZPTMn.entry-name. You can substitute the (*) for the TCP6MON name; doing so yields the status information for the specified entry on all TCP6MONs (in all processors).
SCF Reference for NonStop TCP/IPv6 STATUS ENTRY Command for TCP6MAN STATUS ENTRY Display The format of the display for the STATUS ENTRY command shown in the example is: Name:EA1 (ARP) IPADDRESS........ 172.16.119.1 Arp Timer........... 19 (Min) Arp Flags........ (INUSE,COM) MacAddress.......... %H00 000C 3920CE ALLENTRY - OFF Associated Subnet... EN1 Name: ND1_1 (ND6) ND6 Timer........... MacAddress.......... Associated Subnet...
SCF Reference for NonStop TCP/IPv6 STATUS MON Command for TCP6MAN ND6 timer is the number of seconds in which the entry in the neighbor discovery cache is scheduled to expire. ND6 state shows the state of the neighbor discovery cache. Possible values are INCOMPLETE The associated link local address is timing out. REACHABLE The neighbor discovery cache is currently reachable PROBE The entry is in the STALE state, but the NUD is not administratively disabled. TCP/IP is still able to transmit.
SCF Reference for NonStop TCP/IPv6 STATUS MON Command for TCP6MAN FAMILY { INET | INET6 } specifies that status of a specified type be displayed. INET signifies that only status related to IPv4 be displayed. INET6 specifies that only status related to IPv6 be displayed. If you omit the FAMILY attribute, the current attribute settings for both families are displayed. DETAIL requests the detailed status information for the TCP6MON.
SCF Reference for NonStop TCP/IPv6 STATUS MON Command for TCP6MAN STATUS MON, DETAIL Display Format The format of the display for the STATUS MON, DETAIL is: TCPIPV6 DETAILED STATUS MON \MYSY.$ZZTCP.#ZPTM1 STATUS: STARTED PID............ ( 1,323) PROTO STATE TCP LISTEN LADDR/OUTSUBNET LPORT FADDR FPORT SENDQ --------------- TELNET --------------- * 0 LADDR :: FADDR :: TCP6SAM $ZTC1 LNP INDEX 0 FILTERV4 1.T4A06 STATE STARTED FILTERV6 1.
SCF Reference for NonStop TCP/IPv6 STATUS MON Command for TCP6MAN 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. The possible values are: CLOSING if waiting for a terminate connection request acknowledgment from the remote site. CLOSE-WAIT if waiting for a terminate connection request from the local user.
SCF Reference for NonStop TCP/IPv6 STATUS MON Command for TCP6MAN 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. LPORT/OUTSUBNET is the local port number for either TCP or UDP, depending on the value of Proto. Common port values are displayed in text form; if the port value is not recognized as a common port, it is displayed in decimal format.
SCF Reference for NonStop TCP/IPv6 STATUS PROCESS Command for TCP6MAN STOPPED indicates that multicast is not operational for the group. TCP6SAM is the TCP6SAM process with which the socket is associated. LNP INDEX is the logical network partition index with which the TCP6SAM process is associated. Filterv4 is the IPv4 filter name and state of the filter being used. This field is used by support personnel for debugging purposes. This field does not appear if the socket is using the loopback interface.
SCF Reference for NonStop TCP/IPv6 STATUS PROCESS Command for TCP6SAM STATUS PROCESS Display Format The format of the display for STATUS PROCESS command shown in the Example is: TCPIPV6 Status PROCESS \MYSYS.$ZZTCP PPID............ ( 2,269) BPID................... ( 3, 272) Status always indicates that the process is STARTED. PPID is the processor and process ID of the TCP6MAN primary process. BPID is the processor and process ID of the TCP6MAN backup process.
SCF Reference for NonStop TCP/IPv6 STATUS PROCESS Command for TCP6SAM STATUS PROCESS, DETAIL for TCP6SAM Display Format The format of the display for STATUS PROCESS, DETAIL command shown in the example is: TCPIP Detailed Status PROCESS \MYSYS.$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.
SCF Reference for NonStop TCP/IPv6 STATUS PROCESS Command for TCP6SAM 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 NonStop TCP/IPv6 STATUS ROUTE Command for TCP6MAN 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.
SCF Reference for NonStop TCP/IPv6 STATUS ROUTE Command for TCP6MAN ROUTE $ZZTCP.#ZPTMn.route-name is the specification of the route name. The fully-qualified route name for TCP6MAN is $ZZTCP.#ZPTMn.route-name. To obtain status information about a route on all configured TCP6MONs, use the wild-card (*) notation for the TCP6MON name. For example, STATUS ROUTE *.RT1. To obtain status information about a ROUTE on one TCP6MON, qualify the TCP6MON name. For example, STATUS ROUTE #ZPTM1.RT1.
SCF Reference for NonStop TCP/IPv6 STATUS ROUTE Command for TCP6MAN STATUS ROUTE Display Format The format of the display for the STATUS ROUTE command shown in the Example is: TCPIPV6 Status ROUTE \MYSYS.$ZZTCP.#ZPTM1.
SCF Reference for NonStop TCP/IPv6 STATUS ROUTE Command INET Either a Host or Network route of the INET family INET6 Either a Host or Network route of the INET6 family ARP A route related to an ARP cache ND6 A route related to an ND6 neighbor discovery cache STATUS ROUTE Command This command displays the status of the routes configured in the TCP6MON on the TCP6SAM primary processor. This is a nonsensitive command. Command Syntax STATUS [ / OUT file spec / ] [ROUTE $TCP6SAM-name.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6MAN STATUS ROUTE for TCP6SAM Display Format The format of the display for the STATUS ROUTE command is: TCPIP Status ROUTE \MYSYS.$ZTC1.* Name #RT2 #RT3 #DA2_2 Status STARTED STARTED STARTED RefCnt 1D 0D 0D Name is the name of the route. Status is the summary state of the route. Considerations A pound sign (#) precedes the ROUTE name for backward compatibility with applications that expect this naming convention for ROUTEs.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6MAN 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 or the SCF Reference Manual for H-Series RVUs. Examples This example shows the command and display for STATUS SUBNET. The wild card (*) is used to obtain status information about all SUBNETs configured for the TCP6MON process of processor 3. -> STATUS SUBNET $ZZTCP.#ZPTM3.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6MAN YES-PRIMARY indicates that this SUBNET is failover-capable and has the same SUBNET IP address as another SUBNET. YES-BACKUP indicates that this SUBNET is failover-capable and has the same SUBNET IP address as another SUBNET. NO indicates that this SUBNET does not have the same SUBNET IP address as another SUBNET. Alias indicates that this SUBNET has been configured for IP aliasing addresses.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6MAN STATUS SUBNET, DETAIL Display Format The display format of the STATUS SUBNET, DETAIL command is: TCPIPV6 Detailed Status SUBNET \MYSYS.$ZZTCP.#ZPTM3.* Name Status FailOver SharedIP Alias A-Subnet M-State IPv6 IPv4 SN2 STARTED V4 NO NO SN1 UP YES IPV6PREFIX........ 3ffe:1200:214:1::/64 Prefix State....... PREFERRED Preferred Lifetime..604800 Valid Lifetime..... 2592000 Preferred Timer.... 604779 Valid Timer........
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6MAN FailOver indicates whether the SUBNET is failover enabled or not. When the SUBNET is failover enabled, possible values are: V4 The SUBNET is only IPv4 failover enabled V6 The SUBNET is only IPv46 failover enabled V4-V6 The SUBNET is failover enabled for both IPv4 and IPv6. SharedIP indicates whether the SUBNET has the same SUBNET IP address as its brother.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6MAN IPv6 Flags show the type of IPv6 address or scope (or both) of the IPv6 multicast address.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6SAM Prefix State indicates the current state of the IPv6 prefix address. Possible values are: NONE No state assigned PREFERRED IPv6 prefix in preferred state DEPRECATED IPv6 prefix in deprecated state STATIC Added by an operator Valid Lifetime indicates the maximum valid lifetime of the prefix. Preferred Timer indicates the time interval in seconds that the prefix remains in the preferred state.
SCF Reference for NonStop TCP/IPv6 STATUS SUBNET Command for TCP6SAM Command Syntax STATUS [ / OUT file spec / ] [SUBNET $TCP6SAM-name.#subnet-name] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SUBNET $TCP6SAM-name.#subnet-name is the specification of the SUBNET. The fully qualified SUBNET name for TCP6SAM is $TCP6SAM-name.#subnet-name.
SCF Reference for NonStop TCP/IPv6 STOP Command Considerations A pound sign (#) precedes the SUBNET name for backward compatibility with applications that expect this naming convention for SUBNETs. See Supported Commands and Object Types on page 8-10. STOP Command The STOP command terminates the operation of the specified NonStop TCP/IPv6 object. You can stop processes, SUBNETs, and routes. When the operation is complete, the object(s) is in the STOPPED summary state.
SCF Reference for NonStop TCP/IPv6 STOP PROCESS Command for TCP6MAN STOP PROCESS Command for TCP6MAN The STOP PROCESS command terminates the activity of the specified TCP6MAN 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 TCP6MAN process.
SCF Reference for NonStop TCP/IPv6 STOP ROUTE Command for TCP6MAN Command Syntax STOP [ / OUT file-spec / ] [ PROCESS $TCP6SAM-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $TCP6SAM-name is the name of the TCP6SAM 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 or the SCF Reference Manual for HSeries RVUs.
SCF Reference for NonStop TCP/IPv6 STOP SUBNET Command for TCP6MAN created. You can also substitute the wild card for the route name; doing so stops all routes on all TCP6MONs. Examples To terminate the operation of the specified route: SCF> STOP ROUTE $ZZTCP.#ZPTM1.RT1 Considerations Link-level routes, generated internally by the ARP logic, cannot be stopped externally by using the SCF ABORT/STOP ROUTE commands but can be deleted externally by using the SCF DELETE ROUTE command.
SCF Reference for NonStop TCP/IPv6 TRACE Command Examples To terminate 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 TCP6MON name, but if you do not, it is assumed.
SCF Reference for NonStop TCP/IPv6 TRACE MON Command for TCP6MAN Command Syntax TRACE [ /OUT file-spec/ ] {, STOP MON [ $ZZTCP.#ZPTMn ] | , TO file-spec } [ , [ , [ , [ , [ , [, [, COUNT count NOCOLL RECSIZE size SELECT select-spec PAGES pages NOBULKIO WRAP ] ] ] ] ] ] ] 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 TCP6MON you want to trace. The wild card (*) is not supported.
SCF Reference for NonStop TCP/IPv6 TRACE MON Command for TCP6MAN 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 or until the file-spec is full.
SCF Reference for NonStop TCP/IPv6 TRACE PROCESS Command for TCP6MAN TRACE PROCESS Command for TCP6MAN TRACE can request the capture of target-defined data items, alter trace parameters, and end tracing of the TCP6MAN PROCESS. This is a sensitive command.
SCF Reference for NonStop TCP/IPv6 TRACE PROCESS Command for TCP6MAN COUNT count count is an integer in the range -1 to (32k-1). It specifies the number of trace records to be captured. If COUNT is not specified (or is specified as -1), records are accumulated until the trace is stopped or the file file-spec is full. NOCOLL Indicates that the trace collector process should not be initiated. The disk file is to be written to by Guardian.
SCF Reference for NonStop TCP/IPv6 TRACE PROCESS Command for TCP6SAM To stop the tracing on the TCP6MAN process: -> TRACE PROCESS $ZZTCP, STOP Considerations The TCP6MAN trace facilities for the primary and the backup TCP6MAN processes are independent. The primary and the backup traces can be active at the same time.
SCF Reference for NonStop TCP/IPv6 TRACE PROCESS Command for TCP6SAM TO file-spec specifies the name of the file into which the results of the trace operation are to be placed. It is a required option if the STOP option is not used. BACKUP If BACKUP is specified, then the command applies to the back up TCP6SAM process (that is, the trace is stopped or started on the backup). If omitted the primary is assumed. The TCP6SAM process must be running as a fault-tolerant process pair if this syntax is used.
SCF Reference for NonStop TCP/IPv6 TRACE SUBNET Command for TCP6MAN Examples To trace the TCP6SAM process, write results into the file named $DATA1.TRC.TRCFILE, allow the trace data to be overwritten when the EOF is reached, and select tracing of all NonStop TCP/IPv6 process activity: -> TRACE PROCESS $ZTC1, SELECT (MEMORY, COMMON), TO $DAT11.TRC.
SCF Reference for NonStop TCP/IPv6 TRACE SUBNET Command for TCP6MAN SUBNET $ZZTCP.#ZPTMn.subnet-name is the name of the SUBNET. 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 or the SCF Reference Manual for H-Series RVUs. STOP ends the trace operation. A TRACE command must include either the STOP option or the TO option.
SCF Reference for NonStop TCP/IPv6 TRACE SUBNET Command for TCP6MAN PAGES pages designates how much space, in units of pages, is allocated in the extended data segment used for tracing. PAGES can be specified only when a trace is being initiated, not when its attributes are being modified. pages is an integer in the range 4 through 64, or it is equal to 0. If you omit this option or specify 0, the default value of 64 is applied to the trace.
SCF Reference for NonStop TCP/IPv6 Considerations Tracing all the SUBNETs To trace all configured IP SUBNETs, run the TRACE SUBNET command with a wildcard character. Example1: SCF> TRACE SUBNET #ZPTM1.*, TO $SYSA.TRACES.TCPSUB, SELECT ALL, RECSIZE 4050, PAGES 1024 To stop the trace, run the following command: SCF> TRACE SUBNET #ZPTM1.*, STOP Example2: SCF> TRACE SUBNET #ZPTM1.SN?, TO $SYSA.TRACES.
SCF Reference for NonStop TCP/IPv6 Example2: TRACE SUBNET #ZPTM1.*, SELECT ALL INVALID TRACE SUBNET #ZPTM1.SN?, STOP INVALID TRACE SUBNET #ZPTM1.*, STOP INVALID Example2: Consider the following TRACE SUBNET command: SCF> TRACE SUBNET #ZPTM1.*, TO $SYSA.TRACES.TCPSUB, SELECT ALL, PAGES 1024, RECSIZE 4050 The valid and invalid combinations are: Command Category TRACE SUBNET #ZPTM1.*,STOP VALID TRACE SUBNET #ZPTM1.SN2, SELECT ALL INVALID TRACE SUBNET #ZPTM1.
SCF Reference for NonStop TCP/IPv6 VERSION PROCESS Command for TCP6MAN Command Syntax VERSION [ /OUT file-spec/ ] [ MON $ZZTCP.#ZPTMn.mon-name ] [, DETAIL ] 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 MON object. 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 or the SCF Reference Manual for H-Series RVUs.
SCF Reference for NonStop TCP/IPv6 VERSION PROCESS Command for TCP6SAM Command Syntax VERSION [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $ZZTCP is the TCP6MAN 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 or the SCF Reference Manual for H-Series RVUs.
SCF Reference for NonStop TCP/IPv6 NonStop TCP/IPv6 Trace Facility Command Syntax VERSION [ /OUT file-spec/ ] [ PROCESS $TCP6SAM-name ] [, DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $TCP6SAM-name is the name of the TCP6SAM 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 or the SCF Reference Manual for HSeries RVUs.
SCF Reference for NonStop TCP/IPv6 Introduction to PTrace A description of the subsystem-specific PTrace commands and any special considerations for using these commands with the NonStop TCP/IPv6 An example of each type of trace record display Introduction to PTrace Trace files contain a record of the communications between processes. Each subsystem determines what information is recorded in its trace files.
SCF Reference for NonStop TCP/IPv6 PTrace Commands 4. Display the trace file with PTrace. For additional information on using PTrace, see the PTrace Reference Manual. Device Type and Subtype When a trace file is created, the type and subtype of the device being traced are recorded in that file. When PTrace opens the trace file, it uses this information to determine for which subsystem PTrace is formatting records. The device type and subtype for the TCP6MAN are 72 and 0, respectively.
SCF Reference for NonStop TCP/IPv6 PTrace Commands SETTRANSLATE TEST TRANSLATE Table 8-7 lists and describes all the PTrace commands supported by the NonStop TCP/IPv6 subsystem. Table 8-7.
SCF Reference for NonStop TCP/IPv6 DETAIL Command For a description of the notation scheme used here, see the Notation Conventions on page xxii. For information on starting PTrace and entering PTrace commands, and for more detailed descriptions of the standard PTrace commands available to all subsystems, see the PTrace Reference Manual. DETAIL Command The DETAIL command controls the detailed display option.
SCF Reference for NonStop TCP/IPv6 LABEL Command Command Syntax HEX [ ON | OFF ] ON turns on hexadecimal display mode. OFF turns off hexadecimal display mode. Considerations The NonStop TCP/IPv6 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.
SCF Reference for NonStop TCP/IPv6 OCTAL Command OCTAL Command The OCTAL command controls the octal display option. When OCTAL is set to ON, PTrace displays an octal dump of trace-file records (excluding the record header), with character equivalents printed to the right of the dump. Command Syntax OCTAL [ ON | OFF ] 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.
SCF Reference for NonStop TCP/IPv6 SELECT Command These keywords apply to the MONITOR object: ALL All records SOCKCMD Socket requests (bind, listen, accept, connect, send) MSGSYS Message system interface MALLOC Resource allocation and deallocation events ROUTING Requests for route changes UDP IDP 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) These
SCF Reference for NonStop TCP/IPv6 TEXT Command NonStop TCP/IPv6 and PTrace collect and decode detailed SOCKET and internal TCP control block information when SOCKCMD or TCP are selected for the PROCESS object.
SCF Reference for NonStop TCP/IPv6 Trace Record Formats Trace Record Formats This subsection describes the formatted NonStop TCP/IPv6 trace records. The records are presented in alphabetic order under the SELECT keyword used to display them.
SCF Reference for NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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. Can’t Create New TCPCB Record The can't create new TCPCB record is generated each time the NonStop TCP/IPv6 process cannot create a new control block for a TCP socket.
SCF Reference for NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 alphabetic order, based on their text format.
SCF Reference for NonStop TCP/IPv6 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 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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.
SCF Reference for NonStop TCP/IPv6 UDP Output Records 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 NonStop TCP/IPv6 IP Input Records UDP Sending to Record The UDP sending to record is generated each time the NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 Route Records ppppp indicates the IP number associated with the packet sent. For a list of the commonly used IP numbers, see the TCP/IP Programming Manual. For a complete list of the IP numbers, see the Request for Comments document 1010, “Assigned Numbers.” Fragmenting Record The fragmenting record is generated each time the IP must fragment a packet. header ip_output: fragmenting offset bbbbb bbbbb indicates the IP offset of the fragments (in bytes).
SCF Reference for NonStop TCP/IPv6 Socket Command Records 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. header req SIOCADDRT Route Deletion Record The route deletion record is generated each time a route is deleted. Note that this record does not return any values.
SCF Reference for NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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 NonStop TCP/IPv6 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.
SCF Reference for NonStop TCP/IPv6 UDP User Request Records HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 8-246
A IPv6 Fundamentals IPv6 Internet Addressing IPv6 internet addresses have 128 bits instead of the 32 bits of IPv4 addresses.
IPv6 Fundamentals Types of Addresses In this case, x is a hexadecimal value of a 16-bit piece of the address (six high-order pieces) and d is a decimal value of an 8-bit piece of address (four low-order pieces) in standard, dotted-quad IPv4 form. For example, these are IPv6 addresses: 0:0:0:0:0:0:13.1.68.3 0:0:0:0:0:FFFF:129.144.52.38 When compressed, these addresses are: ::13.1.68.3 ::FFFF:129.144.52.
IPv6 Fundamentals Types of Addresses Figure A-1. Unicast Node Address Node Address 0 127 VST144.vsd This address typically consists of a 64-bit prefix followed by a 64-bit interface ID as shown in Figure A-2: Figure A-2. Prefix and Interface ID Prefix Interface ID 0 127 64 bits 64 bits VST145.vsd An interface ID identifies an interface on a link. The interface ID must be unique on a link, but can also be unique over a broader scope.
IPv6 Fundamentals Types of Addresses Figure A-3. Creating an Interface ID from a MAC Address Company ID Expand to an EUI-64 Invert the universal/ local bit Manufacturer's Data 08 00 2B 36 70 1E FF FE 36 70 1E FE 36 70 1E 08 00 2B 0A 00 2B FF VST146.vsd These list describes commonly used unicast addresses and their values: Unspecified address Indicates the absence of an address, and is never assigned to an interface.
IPv6 Fundamentals Types of Addresses Figure A-4. IPv4-Compatible IPv6 Address 0000... ...0000 00000 IPv4 Address 0 127 80 bits 16 bits 32 bits VST147.vsd Note. Do not use IPv4-compatible IPv6 addresses in the Domain Name System (DNS) or the IPNODES file. The Sockets Library will handle the conversion of these addresses for an application. IPv4-mapped IPv6 address Used to represent an IPv4 address and to identify nodes that do not support IPv6 (IPv4-only nodes).
IPv6 Fundamentals Types of Addresses Figure A-6. Link-Local Address 1111111010 00...................................00 Interface ID 0 127 10 bits 64 bits 54 bits VST149.vsd Site-local Used for sites or organizations that are not connected to the global Internet. This address is assumed to be unique only in the site to which the interface is connected. The format of this address is: Figure A-7. Site-Local Address 1111111011 00.............
IPv6 Fundamentals Types of Addresses Figure A-8. Multicast Address Format Flags Scope Group ID 11..11 0 127 8 bits 4 4 bits bits 112 bits VST151.vsd In the preceding address format, the fields have this definition: 11111111 Identifies the address as multicast. Flags Can be either 0000, which indicates a permanently-assigned (well-known) multicast address, or 0001, which indicates a temporary (transient) multicast address. Scope Indicates the scope of the multicast group.
Address Prefixes IPv6 Fundamentals Address Prefixes Each IPv6 address has a unique pattern of leading bits that indicates its address type. These leading bits are named the format prefix (also referred to as a prefix). Table A-1 lists some of the IPv6 address types and their prefixes. Table A-1.
IPv6 Fundamentals Address Assignment AAAA query A query for a specified domain name in the Internet class returns all associated AAAA resource records in the response. IP6.INT domain for looking up a name for a specified address (address-to-name mapping) An IPv6 address is represented in reverse order as a sequence of 4-bit nibbles separated by dots with the suffix .IP6.INT appended. For example, the IPv6 address 4321:0:1:2:3:4:567:89ab has this inverse lookup domain name: b.a.9.8.7.6.5.0.4.0.0.0.
Aggregatable Testing Address Format IPv6 Fundamentals Figure A-9. Aggregatable Global Address Format Format Prefix TLA ID Reserved NLA ID SLA ID Interface ID 0 127 3 13 8 bits bits bits 24 bits 16 bits 64 bits VST152.vsd In the address format shown in Figure A-9, the fields have these definitions: Format Prefix The format prefix. For aggregatable global unicast addresses, the value for this field is 001. TLA ID The top-level aggregation identifier. Reserved Reserved for future use.
Stateless Address Autoconfiguration IPv6 Fundamentals Figure A-10. Aggregatable Testing Address Format 001 1111111111110 NLA ID SLA ID Interface ID 0 127 3 13 8 bits bits bits 32 bits 16 bits 64 bits VST153.vsd In the address format shown in Figure A-10, the fields have these definitions: 001 The Format Prefix for aggregatable global unicast addresses.
IPv6 Fundamentals Address Lifetimes information with Domain Name System (DNS) servers, these mechanisms provide a path toward network renumbering and provide network administrators with control over the use of network addresses without manual intervention on each host on the network. Address Lifetimes IPv6 addresses are leased to an interface for a fixed (possibly infinite) length of time. Each address has an associated lifetime that indicates how long the address is bound to an interface.
IPv6 Fundamentals Neighbor Discovery Protocol If a node determines that its tentative link-local address is not unique, autoconfiguration stops and manual configuration of the interface is required. To simplify recovery in this case, an administrator should supply an alternate interface identifier that overrides the default identifier in such a way that the autoconfiguration mechanism can then be applied using the new (presumably unique) interface identifier.
IPv6 Fundamentals Neighbor Discovery Protocol How hosts discover the set of address prefixes that define which destinations are on-link for an attached link. (Nodes use prefixes to distinguish destinations that reside on-link from those only reachable through a router.) Parameter discovery How a node learns such link parameters as the link MTU or such Internet parameters as the hop-limit value to place in outgoing packets.
IPv6 Fundamentals Neighbor Discovery Protocol advertisements contain prefixes that are used for on-link determination and/or address configuration, a suggested hop limit value, and so on. Neighbor solicitation Sent by a node to determine the link-layer address of a neighbor, or to verify that a neighbor is still reachable through a cached link-layer address. Neighbor solicitations are also used for duplicate address detection. Neighbor advertisement A response to a neighbor solicitation message.
IPv6 Fundamentals Neighbor Discovery Protocol Neighbor solicitation messages can also determine if more than one node has been assigned the same unicast address. Neighbor unreachability detection detects the failure of a neighbor or the failure of the forward path to the neighbor. Doing so requires positive confirmation that packets sent to a neighbor are actually reaching that neighbor and being processed properly by its IP layer. Neighbor unreachability detection uses confirmation from two sources.
IPv6 Fundamentals Neighbor Discovery Protocol Comparison With IPv4 The IPv6 neighbor discovery protocol corresponds to a combination of the IPv4 protocols ARP, ICMP Router Discovery, and ICMP Redirect. In IPv4 there is no generally agreed upon protocol or mechanism for neighbor unreachability detection, although Hosts Requirements [RFC 1122] does specify some possible algorithms for Dead Gateway Detection (a subset of the problems neighbor unreachability detection tackles).
IPv6 Fundamentals How IPv6 Tunnels Work Unlike ARP, neighbor discovery detects half-link failures (using neighbor unreachability detection) and avoids sending traffic to neighbors with which twoway connectivity is absent. Unlike IPv4 router discovery, the router advertisement messages do not contain a preference field. The preference field is not needed to handle routers of different stability; the neighbor unreachability detection will detect dead routers and switch traffic to a working one.
B SCF Command Summary ABORT [ / OUT file-spec / ] MON [$ZZTCP.#ZPTMn] ABORT [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [ , SUB ALL ] ABORT [ / OUT file-spec / ] [ PROCESS $tcp6sam-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 [ , ALLENTRY ON | OFF ] ADD [ / OUT file-spec / ] [ ROUTE $ZZTCP.*.
SCF Command Summary ADD [ /OUT file-spec/ ] [ ROUTE route-spec ] , FAMILY INET6 , IPV6DESTINATION "ipv6-addr" , IPV6GATEWAY [, DESTTYPE HOST ] [, SUBNET subnet-name ] [, ALLROUTES { ON | OFF } ] ADD [ /OUT file-spec/ ] [ SUBNET $ZZTCP.*.
SCF Command Summary ADD [ /OUT file-spec/ ] [ SUBNET subnet-spec ] , FAMILY DUAL , TYPE ETHERNET , IPADDRESS ip-addr , DEVICENAME lif-name [ , IRDP { ON | OFF } ] [ , SUBNETMASK mask-val ] [ , IPV6INTERFACEID ipv6-id ] [ , IPV6ADDRESS ipv6-addr ] [ , IPV6PREFIX ipv6-prefix ] [ , IPV6NUD { ON | OFF } ] [ , IPV6MTU int ] [ , IPV6REACHABLETIME int ] [ , IPV6RETRANSMITIMER int ] [ , IPV6DADRETRIES int ] [ , IPV6HOPLIMIT int ] [ , IPV6RAENABLE { ON | OFF } ] [ , FAILOVER { SHAREDIP| NONSHAREDIP } ] [ , LNPTPLIS
SCF Command Summary ALTER [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ /OUT file-spec/ ] MON $ZZTCP.
SCF Command Summary ALTER [ /OUT file-spec/ ] [SUBNET $ZZTCP.*.subnet-name ] , FAMILY INET6 [ , { ADDIPV6ADDRESS "ipv6-addr" | DELIPV6ADDRESS "ipv6-addr" | ADDIPV6PREFIX "ipv6-prefix" | DELIPV6PREFIX "ipv6-prefix" | IPV6INTERFACEID "ipv6-id "} ] [ , IPV6 { UP | DOWN } ] [ , IPV6NUD { ON | OFF } ] [ , IPV6MTU val ] [ , IPV6REACHABLETIME val ] [ , IPV6RETRANSMITIMER val ] [ , IPV6DADRETRIES val ] [ , IPV6HOPLIMIT val ] [ , IPV6RAENABLE { ON | OFF } ] ALTER [ /OUT file-spec/ ] [SUBNET $ZZTCP.*.
SCF Command Summary INFO [ / OUT file-spec / ] [ ROUTE $ZZTCP.#ZPTMn.route-name ] [ ,[ FAMILY {INET| INET6 } ] , OBEYFORM, DETAIL] INFO [ /OUT file-spec/ ] [ ROUTE $TCP6SAM-name.route-name ] INFO [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] [, DETAIL | , FAMILY { INET | INET6 } ] | [, OBEYFORM] INFO [ / OUT file-spec / ] [ SUBNET $TCP6SAM-name.subnet-name ] [, DETAIL ] LISTOPENS [ /OUT file-spec/ ] [ MON $ZZTCP.
SCF Command Summary NAMES [ / OUT file-spec / ][ SUBNET $ZZTCP.#ZPTMn.* ] NAMES [ / OUT file-spec / ] [ SUBNET $TCP6SAM-name.* ] PRIMARY [ / OUT file-spec / ] [ PROCESS $ZZTCP ] , CPU cpu-number PRIMARY [ / OUT file-spec / ] [ PROCESS $TCP6SAM-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 / ] [ROUTE $TCP6SAM-name.route-name] [, RESET ] STATS [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] [ , RESET ] [ , DETAIL ] STATS [ / OUT file-spec / ] [SUBNET $TCP6SAM-process.subnet-name] [ , RESET ] [ , DETAIL ] STATUS [ / OUT file-spec / ] [ ENTRY $ZZTCP.#ZPTMn.entry-name] [ , FAMILY { INET | INET6 } ] STATUS [ / OUT file spec / ] [ MON $ZZTCP.
SCF Command Summary STATUS [ / OUT file spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] [, DETAIL ] STATUS [ / OUT file spec / ] [SUBNET $TCP6SAM-name.#subnet-name] STOP [ /OUT file-spec/ ] MON $ZZTCP.#ZPTMn STOP [ / OUT file-spec / ] [ PROCESS $ZZTCP ] [, SUB ALL ] STOP [ / OUT file-spec / ] [ PROCESS $TCP6SAM-name ] STOP [ / OUT file-spec / ] [ROUTE $ZZTCP.#ZPTMn.route-name ] STOP [ / OUT file-spec / ] [SUBNET $ZZTCP.#ZPTMn.subnet-name] TRACE [ /OUT file-spec/ ] {, STOP MON [ $ZZTCP.
SCF Command Summary TRACE [ /OUT file-spec/ ] PROCESS $ZZTCP { , STOP [ , BACKUP ] | [ , TO file-spec [ , BACKUP ] [ , COUNT count ] [ , NOCOLL ] [ , RECSIZE size ] [ , SELECT select-spec ] [ , PAGES pages ] [ , WRAP ] TRACE [ /OUT file-spec/ ] PROCESS ] } $TCP6SAM-name { , STOP [ , BACKUP ] } | { [ , TO file-spec [ , BACKUP ] [ , COUNT count ] [ , NOCOLL ] [ , RECSIZE size ] [ , PAGES pages ] [ , WRAP ] ] TRACE [/OUT file-spec/] [SUBNET $ZZTCP.#ZPTMn.
SCF Command Summary VERSION [ /OUT file-spec/ ] [ PROCESS $TCP6SAM-name ] [, DETAIL ] HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 B-11
SCF Command Summary HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012 B-12
C SCF Error Messages This appendix contains a description of the TCP/IPv6 subsystem SCF error messages. For the operator display of event messages, see the Operator Messages Manual. TCPIPV6 00001 TCPIPV6 E00001 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. TCPIPV6 00002 TCPIPV6 E00002 INTERNAL ERROR: Case value out of range. Cause.
SCF Error Messages TCPIPV6 00005 TCPIPV6 E00005 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. For more information on valid ranges, see ALTER Command on page 8-41. TCPIPV6 00007 TCPIPV6 E00007 Duplicate address. Cause.
SCF Error Messages TCPIPV6 00010 TCPIPV6 E00010 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. TCPIPV6 00011 TCPIPV6 E00011 Invalid IP address. Cause. The IP address is invalid. Effect. The command is not executed. Recovery. Use a correct IP address. TCPIPV6 00012 TCPIPV6 E00012 Invalid CPU number. Cause. The processor number is invalid. Effect.
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. TCPIPV6 00015 TCPIPV6 E00015 Object #ZPTM*.GW1 Already Defined. Cause. This error occurs when a multiple CPU halt is caused by a SNAX issue. The first coldload fails because the operator selects an incorrect SYSnn. Effect. The default gateway for the TCP/IP will not be loaded. Recovery.
SCF Error Messages TCPIPV6 00018 TCPIPV6 E00018 Device access not available from any CPU. Cause. Physical access to the device does not exist. Either the device is not installed or a failure has occurred. Effect. The command is not executed. Recovery. Select a device that is available or correct the problem. TCPIPV6 00019 TCPIPV6 E00019 Unknown LIF device name. Cause. Incorrect device name specified. Effect. The command is not executed. Recovery. Select a device that is available or correct the problem.
SCF Error Messages Recovery. Use a correct SUBNET name or add the SUBNET and retry the request. TCPIPV6 00035 TCPIPV6 E00035 The subnets configured in the FAILOVER are invalid. Cause. The two SUBNETs configured for failover are not in the same LAN or the SUBNET is not failover-enabled. Effect. The command is rejected with the reason. Recovery. Configure two SUBNETs that have two IP addresses in the same SUBNET range with failover enabled.
SCF Error Messages Effect. The command is rejected with the reason. Recovery. Abort the associated SUBNET/brother and reissue the command. TCPIPV6 00039 TCPIPV6 E00039 The FAILOVER brother was already associated with other subnet. Cause. The failover brother was already associated with another SUBNET. Effect. The command is rejected with the reason. Recovery. Reissue the command using another SUBNET not linked in a failover pair.
SCF Error Messages TCPIPV6 00042 TCPIPV6 E00042 The subnet state is invalid for configuring AF_INET6. Cause. The SUBNET is not enabled for IPv6. Effect. The command is rejected with the reason. Recovery. : Reissue the command with the SUBNET in the correct state. TCPIPV6 00043 TCPIPV6 E00043 The IPv6 address specified in the command is not valid. Cause. The IPv6 address specified in the command is not valid. Effect. The command is rejected with the reason. Recovery.
SCF Error Messages TCPIPV6 00046 TCPIPV6 E00046 The IPv6 route destination or gateway address is invalid. Cause. The command is rejected because of an invalid IPv6 route destination or gateway address. Effect. The command is rejected with the reason. Recovery. Reissue the command with a correct IPv6 route destination or gateway address. TCPIPV6 00047 TCPIPV6 E00047 The system is not configured to operate in IPv4 mode. Cause.
SCF Error Messages The system was already configured with IPv4 SUBNETs and cannot be changed to IPv6-only mode. Effect. The command is rejected with the reason. Recovery. For a system already configured with IPv6 SUBNETs that tries to switch to IPv4-only mode, IPv6 for all the SUBNETs should be disabled first. Use the ALTER SUBNET subnet, FAMILY INET6, IPV6 DOWN command to disable IPv6 for the SUBNETs and then reissue the command.
SCF Error Messages Multiple entries created with the ALLENTRY ON attribute specified in the command results in one of the generated entry names exceeding the eightcharacter limit. Effect. The command is rejected with the reason. Recovery. Reissue the command with a correct entry name. TCPIPV6 00053 TCPIPV6 E00053 The MAC address has been changed with the current subnet configuration. Cause. MAC address is changed. Effect. The command is rejected with the reason. The SUBNET will be in STARTING state.
SCF Error Messages Effect. The ADD SUBNET command is not executed. Recovery. Reissue the command specifying no more than two TCP6SAM names in the LNPTPLIST attribute. TCPIPV6 00057 TCPIPV6 E00057 LNP TCP6SAM name format error. Cause. The ADD SUBNET command was rejected because the LNP name is not the correct format for a TCP6SAM name. Effect. The ADD SUBNET command is not performed. Recovery. Reissue the command in the correct TCP6SAM name format.
D NonStop TCP/IPv6 Protocols and Configuration Files This appendix provides background information about networking and material required for configuring the NonStop TCP/IPv6 subsystem.
NonStop TCP/IPv6 Protocols and Configuration Files Transmission Control Protocol (TCP) Transmission Control Protocol (TCP) The Transmission Control Protocol (TCP) is used by applications that require reliable end-to-end data transfer. It is a stream-oriented protocol that has no concept of packet boundaries. TCP guarantees that all data sent will be received and will arrive in the same order in which it was sent.
NonStop TCP/IPv6 Protocols and Configuration Files Internet Protocol (IP) As for TCP, (described in Transmission Control Protocol (TCP) on page D-2), application processes call a socket routine to request the NonStop TCP/IPv6 software to create a UDP socket when needed; the application specifies the type of service desired. The TCP and UDP protocols assume that the Internet Protocol (IP) is used for network layer services. Like IP, UDP is a connectionless protocol; it uses datagrams.
NonStop TCP/IPv6 Protocols and Configuration Files Raw Sockets Raw Sockets As for TCP and UDP, described earlier, application processes call a socket routine to request the NonStop TCP/IPv6 software to create a raw socket when needed. A raw socket provides direct access to the IP. Raw sockets allow applications to take advantage of protocol features not directly accessible through the TCP or UDP interfaces. Applications also can develop new protocols by using raw sockets.
NonStop TCP/IPv6 Protocols and Configuration Files Address Resolution Protocol (ARP) manually a static default route to the specific IP address of the router. If the router's IP address changes, the configuration files on the NonStop machine must change also. With IRDP, there is no need to change any configuration files other than initially enabling the IRDP feature.
NonStop TCP/IPv6 Protocols and Configuration Files Subnetwork Access Protocol (SNAP) that effectively hides physical addresses and allows the IP to use 32-bit Internet addresses. Figure D-1 shows ARP’s relationship to the Ethernet and Internet protocols. Figure D-1. Address Resolution Protocol Ethernet 48-Bit Address ARP Translation Internet 32-Bit Address VST033.vsd The caller (host A) broadcasts a special packet addressed to the receiver’s Internet address (host B).
NonStop TCP/IPv6 Protocols and Configuration Files File Transfer Protocol (FTP) Figure D-2.
NonStop TCP/IPv6 Protocols and Configuration Files TCP/IP Configuration Files TCP/IP Configuration Files There are several files that come on your system update tape (SUT) that are used for configuring your Internet environment. You need to customize some of these files to match your own environment.
NonStop TCP/IPv6 Protocols and Configuration Files HOSTS File Consider the example that follows: # HOSTS file 127.0.0.1 me loop geoff mark cyclone # \CB2 is the gateway between subnets for \ENC1 and \CB1 128.1.1.1 CB21 cb21 # on subnet 1.0, lan01 08008E0002A6 128.1.2.1 CB22 cb22 # on subnet 2.0, lan02 08008E000B2D # Notice that the first entry beginning with 127.0.0.1 has several aliases.
NonStop TCP/IPv6 Protocols and Configuration Files IPNODES File Sample HOSTS File: SMPLHOST The site update tape (SUT) comes with a sample HOSTS file that is installed into $SYSTEM.ZTCPIP. The name of this file is SMPLHOST and the contents are shown in the display: 127.54.12.203 127.54.12.208 127.54.12.209 127.0.0.1 dummy1 loghost dummy2 dummy3 localhost me Modify this file for your environment. IPNODES File The IPNODES file contains information regarding the known IPv6 (and IPv4) nodes on the network.
NonStop TCP/IPv6 Protocols and Configuration Files RESCONF File Items are separated by any number of blanks or tab characters, or both. The pound sign (#) indicates the beginning of a comment; characters up to the end of the line are not interpreted by routines that search the file. Network addresses, both IPv4 and IPv6, are converted to binary format by using the inet_pton() routine from the NonStop Guardian or NonStop Open System Services (OSS) sockets library.
NonStop TCP/IPv6 Protocols and Configuration Files NETWORKS File Using the Domain Name resolver is the preferred way of resolving names on the network. If a name server is not available on the network, use a HOSTS or IPNODES file, as described earlier. Note. All DNS name servers listed in the RESCONF file must have IPv4 addresses. Name servers with IPv6 addresses are not supported. Sample RESCONF File: SMPLRESC The site update tape (SUT) comes with a sample RESCONF file that is installed into $SYSTEM.
NonStop TCP/IPv6 Protocols and Configuration Files PROTOCOL File Sample NETWORKS File: SMPLNETW The site update tape (SUT) comes with a sample NETWORKS file that is installed into $SYSTEM.ZTCPIP. The name of this file is SMPLNETW and the contents are shown in the display: # # Network configuration file # loopback 127 xxx-ether 192.9.200 tdm-oldether 125 # # Internet networks # arpanet 10 ucb-ether 46 xxxether ethernet localnet tdmoldether arpa ucbether Modify this file for your environment.
NonStop TCP/IPv6 Protocols and Configuration Files SERVICES File Sample PROTOCOL File: SMPLPROT The site update tape (SUT) comes with a sample PROTOCOL file that is installed into $SYSTEM.ZTCPIP. The name of this file is SMPLPROT and the contents are shown in the display: # # @(#)protocols 1.
NonStop TCP/IPv6 Protocols and Configuration Files # # @(#)services 1.
NonStop TCP/IPv6 Protocols and Configuration Files PORTCONF File You may need to edit the SERVICES file for the DSM/SCM Planner Interface to work. For more information, see the G06.nn Software Installation and Support Guide or the H06.nn Software Installation and Support Guide. PORTCONF File The PORTCONF file specifies the ports that the LISTNER process listens to and the corresponding server program it invokes when the request comes in. Here is an example of the PORTCONF file: # ftp $system.ztcpip.
E Domain Name Server (DNS) This appendix describes DNS 4.x on the NonStop server. Topics include: DNS Overview Domain Name Resolver on page E-3 For information about DNS 9.x on the NonStop server, see the DNS Configuration and Management Manual and the BIND 9 Administrator Reference Manual. DNS Overview DNS serves as the yellow pages and white pages of an internet community. It provides the translation and mapping of human-readable machine names into IP addresses.
Domain Name Server (DNS) Types of Domain Name Servers For more information on domain names, refer to RFC 1034 and RFC 1035 available from the DDN Network Information Center. Also, refer to the book TCP/IP Illustrated by W. Richard Stevens, Prentice Hall, 1994. The Domain Name Server (DNS) was ported from BSD BIND 4.8. Note. You should read RFCs 819, 920, 974, 1032, 1033, 1034, 1035, and 1101 before you attempt to configure the server.
Domain Name Server (DNS) Remote Server Remote Server A remote server is an option given to people who would like to use a domain name server on their workstation or on a machine that has a limited amount of memory and CPU cycles. By using this option you can run all the networking programs that use the domain name server without having to run the domain name server on the local machine. All queries are serviced by a domain name server running on another machine on the network.
Domain Name Server (DNS) Domain Name Resolver The resolver uses information specified in a configuration file to provide access to a name server. The default name for this file is $SYSTEM.ZTCPIP.RESCONF. When an application sends a name_resolution request to the resolver, the resolver sends the request to the servers listed in the RESCONF file in order of their priority in a timed sequence. The server listed first in the RESCONF file (the primary server) has the highest priority.
Glossary This glossary defines terms used both in this manual and in other NonStop TCP/IP manuals. Both industry-standard terms and HP terms are included. address. An IP-layer identifier for an interface or a set of interfaces. See also, deprecated address, preferred address, valid address, and invalid address. address mask. A bit mask used to select bits from an Internet address for subnet addressing.
Glossary autonomous system autonomous system. A collection of gateways and networks that fall under one administrative entity and cooperate closely to propagate network reachability (and routing) information among themselves using an interior gateway protocol of their choice. Gateways within an autonomous system have a high degree of trust. At least one gateway in an autonomous system must advertise networks in that system to a core gateway using EGP. baseband.
Glossary Class D Class D. A Class D address is a 4-octet multicast group address. The four high-order bits of the address are always 1110; therefore, the first octet is a number in the range 224 through 239 (%HE0 through %HEF). This means that an Internet can have a total of 268,435,456 multicast groups. collector. An EMS process that accepts event messages from subsystems and logs them in the event log. See also Event Management Service (EMS). Compare distributor. command message.
Glossary control and inquiry 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.
Glossary deprecated address derived from the DDL definition file. Likewise, each subsystem that has a tokenoriented 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. deprecated address.
Glossary empty response record empty response record. In DSM programmatic interfaces, a response record containing only a return token with a value that means “no more response records.” See also return token. EMS . See Event Management Service (EMS). EMS standard definitions. The set of declarations provided by EMS for use in event management, regardless of the subsystem. Any application that retrieves tokens from event messages needs the EMS standard definitions. See also definition or definition files.
Glossary event log event log. A file or set of files maintained by EMS to store event messages generated by subsystems. Event Management Service (EMS). A part of DSM used to provide event collection, event logging, and event distribution facilities. It provides for different event descriptions for 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.
Glossary FDDI FDDI. See Fiber Distribution Data Interface (FDDI). FESA. See Fast Ethernet ServerNet adapter (FESA). 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).
Glossary GESA normal circumstances, all GGP participants reach a steady state in which the routing information at all gateways agrees. GESA. See Gigabit Ethernet ServerNet adapter (GESA). 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.
Glossary hierarchical routing specified set of header tokens; event messages, a different set with some overlap. See also SPI message. hierarchical routing. Routing based on a hierarchical addressing scheme. Most Internet routing is based on a two-level hierarchy in which an Internet address is divided into a network portion and a host portion. Gateways use only the network portion until the datagram reaches a gateway that can deliver it directly.
Glossary Institute of Electrical and Electronics Engineers (IEEE) Institute of Electrical and Electronics Engineers (IEEE). An international industry group that develops standards for many areas of electrical engineering and computers. interactive command. In DSM, a command entered by a human operator rather than by a program. See also programmatic command. interface. A node's attachment to a link. This is equivalent to a subnet object within the TCP/IPv6 subsystem and a LIF in the SLSA subsystem.
Glossary interoperability interoperability. The ability of software and hardware on multiple machines from multiple vendors to communicate meaningfully. invalid address. An address that is not assigned to any interface. A valid address becomes invalid when its valid lifetime expires. Invalid addresses should not appear as the destination or source address of a packet.
Glossary Level 2 Level 2. A reference to LINK LEVEL communication (for example, frame formats) or linklevel connections derived from the ISO 7-layer reference model. For long-haul networks, level 2 refers to the communication between a host computer and a network packet switch (for example, HDLC/LAPB). For local area networks, level 2 refers to physical packet transmission. Therefore, a level 2 address is a physical hardware address. Level 3.
Glossary media access control (MAC) address 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. management applications. In DSM, an application process that opens a management or subsystem process to control a subsystem.
Glossary noncritical event were local. The key advantage of NFS over conventional file transfer protocols is that NFS hides the differences between local and remote files by placing them in the same name space. NFS is used primarily on UNIX systems, but has been implemented for many systems, including personal computers like an IBM PC and Apple Macintosh. noncritical event. A DSM event not too crucial to system or network operations.
Glossary packet two systems, the services required to perform these functions, and the protocols associated with these services. packet. The unit of data sent across a packet switching network. While some Internet literature uses it to refer specifically to data sent across a physical network, other literature views the Internet as a packet switching network and describes IP datagrams as packets. Packet Internet Groper (PING).
Glossary process process. A running entity that is managed by the operating system, as opposed to a program, which is a collection of code and data. When a program is taken from a file on a disk and run in a processor, the running entity is called a process. programmatic command. In DSM, a command issued by a program rather than by a human operator. Compare interactive command. protocol. A formal description of message formats and the rules two or more machines must follow to exchange those messages.
Glossary SCF SCF. See Subsystem Control Facility (SCF). SCP. See Subsystem Control Point (SCP). secondary route. For multiple routes to the same destination, all the routes in addition to the primary route (the route visible to Radix Routing topology) are called shadow/secondary routes. Also called shadow route on page -18. sensitive command. In DSM, a command that can be issued only by a restricted set of Guardian users, such as the owner of a subsystem process.
Glossary Simple Mail Transfer Protocol (SMTP) Simple Mail Transfer Protocol (SMTP). The Internet standard protocol for transferring electronic mail messages from one machine to another. SMTP specifies how two mail systems interact, and specifies the format of control messages the two mail systems exchange to transfer mail. simple token.
Glossary subnetwork Internet portion and local portion. Gateways and hosts inside a site using subnet addressing interpret the local portion of the address by dividing it into a physical network portion and host portion. subnetwork. One or more intermediate systems that provide relaying and through which end open systems can establish network connections. Subnetwork Access Protocol (SNAP).
Glossary summary state summary state. In DSM interfaces to HP data communications subsystems, one of the generally defined possible conditions of an object, with respect to the management of that object. A summary state differs from a state in two ways. First, a summary state pertains to the management of an object, whereas a state can convey other kinds of information about the object.
Glossary token ring 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.
Glossary WAN subsystem WAN subsystem. See wide area network (WAN) subsystem. Warning. In DSM interfaces, a condition encountered in performing a command or other operation, that can be significant but does not cause the command or operation to fail. A warning is less serious than an error. Compare error. well-known port. Any of a set of protocol ports preassigned for specific uses by transport level protocols (that is, TCP and UDP).
Glossary See WAN manager process.
Index Numbers 001 field, aggregatable testing address format A-11 11111111 field, multicast identifier A-7 1111111111110 field, aggregatable testing address format A-11 A AAAA query A-9 AAAA resource record type A-8 ABORT command considerations 6-18 LISTNER, not supported 6-13 MON, specification 8-14 PROCESS, example 6-12 ROUTE, specification 8-17 SUBNET, specification 8-18 TCP6MAN process, specification 8-15 TCP6SAM process 6-13 TCP6SAM process, specification 8-16 TELSERV, not supported 6-13 Access list 7
Index B Applications (continued) socket-transport-service provider for 2-13 starting 1-22 transparency for 2-2 using the SRL 2-14 Architecture, conventional TCP/IP 2-4 ARP See Address Resolution Protocol Arp Flags 8-173 ARP table adding to 8-19 deleting from 8-60 entry type 8-19 viewing 8-3, 8-63 Arp Timer 8-173 ARPTIMER-REFRESHED 8-72 Associated subnet display field 8-66 ASSOCIATESUB attribute 8-56 ASSUME command 8-5 Assumptions for starting NonStop TCP/IPv6 1-2 Auto configuration 2-18 Automatic tunnelin
Index C Configuration configured tunneling example 1-19 default 2-7 distributor listening model 3-17, 3-19 DUAL mode 1-15 Ethernet failover, nonshared IP 1-9, 1-13 Ethernet failover, shared IP 1-7, 1-11, 1-16 hybrid listening model 3-19/3-20 monolithic listening model 3-14, 3-16 round-robin 2-7 standard listening model 3-12 Configuration example 3-14, 3-17, 3-19 Configured tunneling ADD SUBNET command 8-26 ALTER SUBNET command 8-26 command syntax 8-39 example 1-19, 8-40 how they work A-18 sample SCF comma
Index D CPUs with Data Path field 1-3 Current MBUFs used attribute 8-141, 8-160 Current pool allocation attribute 8-141, 8-160 D Data flow distributor listening model 3-6 hops 3-7 in hybrid listening model 3-9 monolithic listening model 3-4 shortening path-length for 3-8 standard listening model 3-2 Data Link Layer D-6 Data MDs in use attribute 8-142, 8-160 Data path 2-12, 2-13 Data Predictions OK 8-150 Datagrams Internet Protocol D-3 transmitting D-3 User Datagram Protocol D-2 Dead gateway detection 8-2
Index E DNS override parameter 6-21 DNS updates 2-20 Domain Name Resolver application layer E-3 presentation layer E-3 Domain Name Server address-to-name mapping E-1 application layer E-1 Caching Server E-2 description E-1 hardware/software information E-2 machine information E-2 mailbox information E-2 Master Server E-2 Primary Server E-2 Secondary Server E-2 name-to-address mapping E-1 Remote Server E-3 Slave Server E-3 types E-2 using E-3 DSAP See Destination Service Access Point DSM 2-17 See Distribut
Index F EXPANDSECURITY attribute 8-45 F Faddr attribute 8-178 FAILOVER attribute 8-28, 8-32, 8-38 Failover, Ethernet 2-11 FAMILY attribute 8-22, 8-23, 8-28, 8-47, 8-64, 8-82 FAMILY display field 8-185 Fast Ethernet 2-3 Fast Ethernet ServerNet adapter (FESA) and SLSA 2-16 sharing 6-13 FESA See Fast Ethernet ServerNet adapter (FESA) Files HOSTS E-3 PROTOCOLS D-4 RESCONF E-4 Filter inbound frames and 2-13 key, round-robin 2-7 Filter Errors statistic 8-168, 8-170 Filter Timeout statistic 8-168, 8-171 Finger,
Index H Good routes recorded attribute 8-134, 8-156 Group ID field, multicast address A-7 H Header formats 8-220 HEX command 8-215 Hexadecimal format 2-13 Hierarchy, SCF objects 8-2 Home terminal 6-9 Hop distributor listening model 3-7 elimination 3-8, 3-10 elimination of 3-2 in hybrid listening model 3-9 message-system 2-4/2-5, 2-13 monolithic listening model 3-5 Host ID display field 8-79 Host Id display field 8-70 Host name display field 8-70, 8-79 Host name override parameter 6-21 HOSTID attribute 8-
Index I Internet Protocol (continued) heterogeneous networks connection D-3 network layer D-3 using raw sockets D-4 Interprocess communication records 8-224 Inter-process communication (IPC) 3-6 Invalid header size attribute 8-137, 8-159 IP See Internet Protocol IP address 8-4 IP alias 8-51, 8-60 IP failover, fault-tolerant operations guidelines 6-3 IP failover, NonStop operations nonshared IP configuration example 1-9, 1-13/1-15 overview 2-11 shared IP configuration example 1-7/1-8, 1-11/1-13 IP hosts co
Index K IPV6MTU attribute 8-31, 8-37, 8-54, 8-97 IPV6NUD attribute 8-31, 8-36, 8-54, 8-98 IPV6PREFIX attribute 2-19, 8-31, 8-36, 8-97 IPV6RAENABLE attribute 8-32, 8-37, 8-54, 8-98 IPV6RAENEABLE attribute 2-19 IPV6REACHABLETIME attribute 8-32, 8-37, 8-54, 8-97 IPV6RESERVEDID attribute 8-56 IPV6RETRANSMITIMER attribute 8-37, 8-54, 8-98 IRDP attribute 8-28, 8-35 IRDP Protocol D-4 K Keep alive idle display field 8-70, 8-79 Keep alive interval display field 8-70, 8-79 Keep alive retry cnt 8-70 Keep alive retr
Index M Logical-network partitioning (LNP) (continued) determining the TCP6SAM process names for 6-24 guidelines 6-24 ND6HOSTD considerations 6-21 overview 2-8 starting applications 1-22/1-24 LOOP0, reserved name 8-7 Loopback address A-4 Loopback default name 8-7 Lport attribute 8-178 M MAC See Media Access Control MACADDR attribute 8-20 MacAddress display field 8-66 Manager process, definition 2-13 Managing NonStop TCP/IPv6 6-1/6-27 Master TCP6MON, assignment 2-13 Max dup driv MDs used attribute 8-142,
Index O Names, suggested 8-7 Naming conventions SCF 8-7 TCP6SAM 8-3 ND6HOSTD process 2-17, 2-20, 6-18 ND6HOSTD process considerations for LNP 6-21 Neighbor advertisement A-15 Neighbor discovery protocol 2-18, A-13/A-18 Neighbor solicitation A-15 Neighbor unreachability detection A-14 Network name space E-1 Network Layer Address Resolution Protocol D-5 Internet Control Message Protocol D-4 Internet Protocol D-3 Next-hop determination A-14 Next-level aggregation (NLA) identifier field, aggregatable testing
Index P OBEY file (continued) TCPIPUP13 (for ODBC) 3-18 TCPIPUP14 (for iTP WebServer) 3-20 OBEYFORM attribute 8-65, 8-68, 8-83, 8-87 Object specifiers 8-7 Object types descriptions 8-2/8-4 ENTRY 8-3 MON 8-4 null 8-4 PROCESS 8-4 ROUTE 8-5 SUBNET 8-6 Object-name templates, definition 8-7 OCTAL command 8-217 Online help 2-22 Openers of TCP6MONs 6-10 of TCP/IP process 6-10 Operating modes 2-20 Operator messages C-1 OUT attribute 8-27 Out dest unreachable attribute 8-137, 8-159 Out echo attribute 8-137, 8-159
Index Q Persistence manager (continued) function 6-15 PIF object and the distributor listening model 3-7 Pool allocation fails attribute 8-143, 8-161 Port binding to 3-8 ownership 3-2 sharing, caution 6-2 sharing, round-robin filtering 2-7 UDP sharing considerations 6-2 well-known, binding to 3-6 Port filters drop statistic 8-169 Port number associated with specific service D-2 to select a socket D-2 well-known D-2 PORT-SHARE-ENABLE 8-74 PORT-SHARE-ENABLE attribute 8-48 PPID attribute 8-176 PPID display f
Index S Request For Comment 1032 E-2 1033 E-2 1034 E-2 1035 E-2 1042 D-7 1101 E-2 1256 D-4 768 D-3 791 D-4 792 D-4, D-5 793 D-2 819 E-2 826 D-5 920 E-2 974 E-2 Requests latency reduction 2-5 processing speed 2-5 RESCONF file E-4 Reserved field, aggregatable global address A-10 Reserved names for ROUTEs 8-7 LOOP0 8-7 #ZPTM 8-7 $ZZTCP 8-7 RESERVEDIP attribute 8-56 RFC1323 enable display field 8-72, 8-81 RFC1323-ENABLE attribute 8-46 Round-robin filtering and shared ports 2-7 configuring, caution 6-2 default
Index S SCF commands (continued) INFO 8-63 LISTOPENS 8-101 NAMES 8-61, 8-107 PRIMARY 8-112 START 8-113 STATS 8-116, 8-162 STATUS 8-171 STOP 8-195 TRACE 8-199 VERSION 8-208 Scope field, multicast address A-7 SCP 2-17 SEL and SUM options, not supported by TCP/IP 8-11 SELECT command 8-217 Selecting, LIF 1-3 SendQ attribute 8-178 Sensitive commands 8-11 ABORT 8-14 ADD 8-19 ALTER 8-42 DELETE 8-60 PRIMARY 8-112 START 8-113 STATS command with RESET option 8-116 STOP 8-195 TRACE 8-199 ServerNet, use of 2-3 Server
Index S SPI subsystem number 2-3 SRL caution 2-14 programmatic interfaces to -xv SSAP See Source Service Access Point Standard listening model configuration example 3-12 definition 3-2 figure 3-3, 3-13 START command MON, specification 8-114 ROUTE, specification 8-115 SUBNET, example 1-7, 1-10, 1-16, 1-20, 5-8 SUBNET, specification 8-115 STARTED, multicast state 8-178, 8-183 Starting applications 1-22 Telserv 1-22, 1-23, 1-24 STARTING, multicast state 8-178, 8-183 State attribute 8-96 socket status 8-177 s
Index T SYN-SENT socket state 8-177 System configuration database clearing 2-22 managing 6-14 T T0372G08 product number 2-11, 2-12 T1265G06, product number 2-11, 2-12 T1266G06 product number 2-11, 2-12 T1267G06 product number 2-11, 2-12 T1268G06 product number 2-11, 2-12 T2701G06 product number 2-11, 2-12 T9550G08 product number 2-11, 2-12 TACL process 6-9 WHO command 6-9 Task summary stopping generic process 6-12 stopping, preserving configuration 6-11 Tasks stopping NonStop TCP/IPv6 as a generic proces
Index T TCP6SAM (continued) TRACE command 8-204 VERSION command 8-210 TCPCOMPAT42 attribute 8-45 TCPCOMPAT42 display field 8-71, 8-80 TCPCWNDMULTIPLIER attribute 8-47 TCPCWNDMULTIPLIER display field 8-73 TCPIPUP11 command file 3-13 TCPIPUP12 command file 3-15 TCPIPUP13 command file 3-18 TCPIPUP14 command file 3-20 TCPIPV6 in LISTDEV command 8-5 online help for 2-22 TCPIP^PROCESS^NAME adding 1-22, 1-23, 1-24 TCPIP^PROCESS^NAME, adding 1-22, 1-23 TCPKEEPCNT attribute 8-45 TCPKEEPIDLE attribute 8-45 TCPKEEPI
Index U Trace record formats (continued) socket creation 8-221 TCP records 8-225 UDP input records 8-232 UDP output records 8-234 UDP user request records 8-243 Trace status display field 8-71, 8-80 Tracing data records 2-15 Transmission Control Protocol connection-oriented protocol D-3 description D-2 identifying a connection D-2 selecting a socket D-2 socket interface to D-2 stream-oriented protocol D-2 transport layer D-2 Transport Layer TCP D-2 Transmission Control Protocol D-2 UDP D-2 User Datagram P
Index Z WHO command display 6-9 entering 6-8 Wild-card characters 8-7 Wild-card support 8-7 Z ZTCP6REL 2-11, 2-12, 2-14 ZTCP6SRL 2-14 ZTCPSRL, warning re replacing 7-2 ZTNT^TRANSPORT^PROCESS^NAME 122, 1-23, 1-24 Special Characters #LOOP0 8-6 #ZPTMx 8-7 $SYSTEM.ZTCPIP.HOSTS See HOSTS file $SYSTEM.ZTCPIP.PROTOCOLS See PROTOCOLS file $SYSTEM.ZTCPIP.RESCONF See RESCONF file $ZMnn 1-2 $ZNET 1-2 $ZPM 2-22 $ZTCx 8-4 $ZZKRN 1-3, 1-4 $ZZLAN 1-2, 1-3 $ZZTCP 8-7 $ZZTCP.
