OSI/TS Configuration and Management Manual

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series

OSI/TS Configuration and

Management Manual

Abstract

This manual is intended for programmers, system managers, and system operators. It describes

how to write Transport Layer applications that use the Compaq OSI/TS software to

communicate with remote transport users across an OSI network. It also describes how to

configure the Compaq OSI/TS subsystem and how to diagnose configuration and performance

problems.

Product Version

OSI/TS D43

Supported Releases

This manual supports D-series release D43 and later, and G-series release G06.05 and later.

Part Number Published

424831-001 December 1999

Summary of content (272 pages)

PAGE 1
OSI/TS Configuration and Management Manual Abstract This manual is intended for programmers, system managers, and system operators. It describes how to write Transport Layer applications that use the Compaq OSI/TS software to communicate with remote transport users across an OSI network. It also describes how to configure the Compaq OSI/TS subsystem and how to diagnose configuration and performance problems.
PAGE 2
Document History Part Number Product Version Published 82477 A00 OSI4AM April 1986 84142 OSI/TS C20 March 1989 22950 OSI/TS C20 March 1990 056782 OSI/TS C30 July 1992 421960-001 OSI/TS D40 June 1999 424831-001 OSI/TS D43 December 1999 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative.
PAGE 3
OSI/TS Configuration and Management Manual Glossary Index Figures Tables What’s New in This Manual xiii Manual Information xiii New and Changed Information xiii About This Manual xv xvi What Is in This Manual? Manual Contents xvii Related Manuals xix Your Comments Invited xxi Notation Conventions xxi Abbreviations xxvi 1.
PAGE 4
1. Introduction (continued) Contents 1. Introduction (continued) EMS 1-12 PTrace 1-13 Inspect 1-13 NonStop Programming Considerations G-Series Compatability 1-13 1-13 Communication between D-Series and G-Series Systems 1-15 2. Background Information About Addressing SNPA Addresses 2-1 SNPA Addresses Over LANs 2-2 SNPA Addresses Over X.25 WANs LSAP Selectors 2-3 2-3 NSAP Addresses 2-3 Network Addressing Authorities 2-3 Network Addressing Domains 2-4 X.
PAGE 5
2. Background Information About Addressing (continued) Contents 2. Background Information About Addressing (continued) Large or Established OSI Networks 2-16 OSI/TS Subdevices 2-16 What Are Subdevices? 2-17 Address Sharing vs. Multiplexing 2-17 3.
PAGE 6
3. Configuring the OSI/TS Subsystem (continued) Contents 3. Configuring the OSI/TS Subsystem (continued) Command File for Configuring OSI/TS Over an X.25 Network, Using SNDCF Command File for Configuring OSI/TS Over a LAN 3-25 3-26 Command File for Configuring OSI/TS Over a LAN, Using ES-IS Routing Exchange Protocol 3-28 Command File for Configuring OSI/TS Over a LAN, Using IP null 3-30 Configuring Large X.
PAGE 7
4. Performing Monitoring and Troubleshooting Guide (continued) Contents 4.
PAGE 8
5. OSI Transport Services (continued) Contents 5. OSI Transport Services (continued) Retransmission on Timeout 5-8 Resequencing 5-8 5-8 Inactivity Control Addressing 5-9 Address Sharing 5-9 5-11 Called/Calling and SRC-REF/DST-REF Addresses Multiplexing 5-12 Connection Multiplexing 5-12 Passive Multiplexing 5-14 6.
PAGE 9
7. NonStop Kernel File-System Interface Contents 7.
PAGE 10
7. NonStop Kernel File-System Interface (continued) Contents 7. NonStop Kernel File-System Interface (continued) Releasing a Transport Connection CONTROL 12 Procedure 7-37 7-37 WRITE Procedure or WRITEREAD Procedure 7-38 Remote Release Error Release 7-38 7-39 Closing a Subdevice 7-39 Requesting Status Information 7-39 Request Buffer 7-39 Response Buffer 7-40 A. Message Control Word Summary B. X.25 Status Code Tables Disconnect Reason Codes B-1 Clear Cause Codes B-2 Diagnostic Field Codes B-3 C.
PAGE 11
Figures (continued) Contents Figures (continued) Figure 1-7. Local Area Subnetworks: ES-IS Routing Exchange Protocol Enabled 1-10 Figure 1-8. Local Area Subnetworks: ES-IS Routing Exchange Protocol Disabled 1-10 Figure A-9. D to G Communication 1-14 Figure A-10. G to D Communication 1-15 Figure 2-1. NSAP Addressing Domains 2-5 Figure 2-2. NSAP Network Addressing Domain Hierarchy 2-6 Figure 2-3. NSAP Address Components Figure 2-4. NSAP Address Example 1 2-13 Figure 2-5.
PAGE 12
Figures (continued) Contents Figures (continued) Figure 7-11. WRITE or WRITEREAD Buffer: Accept Parameters 7-31 Figure 7-12. WRITE Buffer: Accept Connection and Send Data Figure 7-13. WRITE Buffer: Accept Connection, No Data Figure 7-14. WRITE Buffer: Figure 7-15. READ Buffer: Figure 7-16. WRITE or WRITEREAD Buffer: Figure 7-17. WRITEREAD Buffer: 7-32 7-32 Outgoing Data 7-35 Incoming Data 7-36 Connection Release 7-38 Status Request 7-40 Tables Table i.
PAGE 13
Tables (continued) Contents Tables (continued) Table 7-8. READ or WRITEREAD Call Completion Codes During Data Transfer 7-37 Table 7-9. READ Buffer Status Fields (Page 1 of 2) Table A-1. Write Buffer Message Control Word Summary A-1 Table A-2. Read Buffer Message Control Word Summary A-2 Table B-1. Reasons for Circuit Disconnection B-1 Table B-2. Clear Cause Codes Table B-3.
PAGE 14
Contents OSI/TS Configuration and Management Manual—424831-001 xii
PAGE 15
What’s New in This Manual Manual Information OSI/TS Configuration and Management Manual Abstract This manual is intended for programmers, system managers, and system operators. It describes how to write Transport Layer applications that use the Compaq OSI/TS software to communicate with remote transport users across an OSI network. It also describes how to configure the Compaq OSI/TS subsystem and how to diagnose configuration and performance problems.
PAGE 16
What’s New in This Manual New and Changed Information All technical updates since the previous version of this manual have been noted with change bars.
PAGE 17
About This Manual The OSI/TS Configuration and Management Manual describes how to write Transport Layer applications that use the Compaq OSI/TS software to communicate with remote transport users across an OSI network. It also describes the use of the SCF subsystem to configure the Compaq OSI/TS subsystem, and how to diagnose configuration and performance problems. The OSI/AS and OSI/TS subsystems together provide core services that support the seven-layer OSI reference model.
PAGE 18
What Is in This Manual? About This Manual Notes: How How To Information Ref Reference Information AS PR OSI/AS Programming Manual AS CM OSI/AS Configuration and Management Manual AS SCF SCF Reference Manual for OSI/AS AS MPM OSI/AS Management Programming Manual TS CM OSI/TS Configuration and Management Manual TS SCF OSI/TS SCF Reference Manual TS MPM OSI/TS Management Programming Manual What Is in This Manual? This manual is intended for programmers, system managers, and system operators
PAGE 19
Manual Contents About This Manual Manual Contents Table ii, Manual Contents lists the contents of each section and appendix in this manual. Table ii.
PAGE 20
Manual Contents About This Manual Table ii. Manual Contents (continued) Section or Appendix Contents Section 7, NonStop Kernel File-System Interface This section describes how your application uses NonStop Kernel file-system procedures to perform various tasks. Appendix A, Message Control Word Summary This appendix summarizes how your application uses the MCW in WRITE and WRITEREAD calls. Appendix B, X.
PAGE 21
Related Manuals About This Manual Related Manuals Figure i, Related Manuals shows some other manuals that contain helpful information on OSI/TS and related products. The manuals closest to the center of the figure are most closely related to this manual. Figure i. Related Manuals Introduction to Networking and Data Comm.
PAGE 22
Related Manuals About This Manual The following list describes each of the manuals shown in Figure i, Related Manuals: • • • Introduction to Networking and Data Communications for Himalaya S-Series Servers. This manual provides an overview of Compaq networking and data communications products. Introduction to Distributed Systems Management (DSM). This manual introduces the products and components collectively known as Distributed Systems Management.
PAGE 23
Your Comments Invited About This Manual • SCF reference manuals for OSI/AS, TLAM, PAM, and X25AM describe how to install, configure, and manage the underlying subsystems upon which Compaq OSI/TS depends. Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the User Documentation disc.
PAGE 24
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces.
PAGE 25
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 the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
PAGE 26
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered 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.
PAGE 27
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.
PAGE 28
Abbreviations About This Manual Abbreviations The following list defines abbreviations and acronyms used in this manual and in the other Compaq OSI/AS and Compaq OSI/TS manuals. Not all terms listed here are used in this particular manual.
PAGE 29
Abbreviations About This Manual COUP Configuration Utility Program CP-PPDU Connect presentation PPDU CPA-PPDU Connect presentation accept PPDU CPR-PPDU Connect presentation reject PPDU CR-PPDU Connect request PPDU CSMA Carrier sense multiple access CSMA/CD CSMA with collision detection CUG Closed user group DC-TPDU Disconnect confirm TPDU DCB Data control block DDL Data Definition Language DN-SPDU Disconnect SPDU DR-TPDU Disconnect request TPDU DSC Dynamic System Configuration
PAGE 30
Abbreviations About This Manual IDP Initial domain part (part of an NSAP address) IEEE Institute of Electrical and Electronics Engineers IID Invocation identifier IP OSI internet protocol IPPDU IP protocol data unit IS Intermediate system ISO International Organization for Standardization LAN Local area network LAPB Link access protocol—balanced LDIB Local Directory Information Base LLC1 Logical link control type 1 LMIB Local Management Information Base LSAP Link layer service acc
PAGE 31
Abbreviations About This Manual PDU Protocol data unit PIN Process identification number PLP Packet-level protocol PPDU Presentation protocol data unit PSAP Presentation service access point PSEL Presentation selector PVC Permanent virtual circuit RCB Request control block RF-SPDU Refuse SPDU RJ-TPDU Reject TPDU RLRE-APDU A-release response accept APDU RLRQ-APDU A-release request APDU RS-PPDU Resynchronize PPDU RSA-PPDU Resynchronize acknowledge PPDU SAP Service access point
PAGE 32
Abbreviations About This Manual TAL Transaction Application Language TAPS Tandem application, presentation, and session service provider TC-PPDU Capability data PPDU TCB Transport connection control block TCC-PPDU Capability data acknowledge PPDU TD-PPDU Presentation data PPDU TE-PPDU Expedited data PPDU TLAM Tandem LAN access method TMDS Tandem Maintenance and Diagnostic Subsystem TPDU-NR A TPDU field that contains the DT-TPDU number TPDU Transport protocol data unit TSAP Transport
PAGE 33
1 Introduction Compaq OSI software is the Compaq implementation of the International Standards Organizations (ISO) seven-layer model for standard network architecture. This model is the ISO Reference Model for Open Systems Interconnection (OSI).
PAGE 34
Implemented Standards Introduction • • • • ISO 9542 1988(E) end system to intermediate system (ES-IS) routing exchange protocol ISO 8208 packet-switched network protocol Data Link Layer (Layer 2) • • IEEE 802.2 Logical Link Control Type 1 (LLC1) CCITT X.25 link access protocol balanced (LAPB) Physical Layer (Layer 1) • IEEE 802.3 baseband Figure 1-1 illustrates the protocols supported by OSI/TS. Figure 1-1.
PAGE 35
OSI/TS Features Introduction Figure 1-2 shows the relationship between end systems and intermediate systems. Figure 1-2. OSI End Systems and Intermediate Systems Layer Application Presentation Session Transport Network ••• Data Link ••• Physical ••• End Intermediate System System Subnetwork Intermediate End System System CDT 102.CDD OSI/TS Features The OSI/TS subsystem implements the Transport Layer of the OSI Reference Model.
PAGE 36
K-Series Information Introduction K-Series Information Each subsystem requires the use of one or more hardware communications controller boards to control physical lines into communications subnetworks. OSI/TS uses standard Compaq communications controllers to implement subnetwork protocols. For attaching Compaq systems to OSI subnetworks, use the communications hardware listed in Table 1-1. Table 1-1.
PAGE 37
Software Architecture Introduction • • ServerNet Wide Area Network (SWAN) Concentrator Token-Ring ServerNet Adapter (TRSA) For further general information about G-series software and related S-series hardware consult the G-Series Highlights and Migration Planning Guide.
PAGE 38
Software Architecture Introduction Figure 1-3. Compaq OSI Architecture : OSI/TS and Underlying Subsystems Layer Transport OSI/TS Subsystem Network Data Link X25AM Subsystem LAN * Controllers LAN ** Controllers RS-232C, RS-449, X.21, V.35 LAN Driver /Interrupt Handler Physical WAN LAN CDT 103.CDD Figure 1-4 shows the data flow between the OSI/TS subsystem and underlying subsystems.
PAGE 39
Wide Area Networks Introduction Figure 1-4. Data Flow Between OSI/TS and Underlying Subsystems Layer Transport TSP IP Network ES-IS NSP Data Link NSP LAPB Controllers 802.3 CSMA/CD Controllers RS-232C, RS-449, X.21, V.35 50-ohm Baseband WAN LAN Physical CDT 104.CDD Wide Area Networks For communicating over WANs, the OSI/TS subsystem uses the connection-mode services of the X25AM access method.
PAGE 40
Wide Area Networks Introduction Transport protocol classes 0 through 4 can be used over wide area networks. Refer to the X.25 Access Method (X25AM) Manual for more information on Compaq’s implementation of X.25. Figure 1-5 illustrates how OSI/TS uses SNDCF to implement IP over X.25 wide area subnetworks (SNDCF is enabled). When SNDCF is enabled, the IPPDU is sent as data in the X.25 frame. Figure 1-5. X.
PAGE 41
Local Area Networks Introduction Local Area Networks For communicating over LANs, OSI/TS uses the connectionless services of the Tandem LAN Access Method (TLAM). For S-series systems, it is the Port Access Method (PAM). ES-IS routing exchange protocol is also supported to allow the dynamic exchange of routing information in LANs. This protocol facilitates the mapping of logical addresses (NSAP addresses) to physical addresses (LAN station addresses or MAC addresses).
PAGE 42
Interfaces Introduction Figure 1-7. Local Area Subnetworks: ES-IS Routing Exchange Protocol Enabled Transport Layer TSP IP Network Layer ES-IS Routing Information Data Data Link Layer PAM or TLAM CDT 107.CDD Figure 1-8. Local Area Subnetworks: ES-IS Routing Exchange Protocol Disabled Transport Layer TSP Network Layer IP Data Data Link Layer PAM or TLAM CDT 108.
PAGE 43
Configuration and Management Tools Introduction retrieve messages from the Event Management Service (EMS). The OSI/TS Management Programming Manual describes this interface. • The interactive interface (sometimes called the human interface) permits users to request status and configuration information, alter configuration parameters, and retrieve messages from the Event Management Service (EMS), interactively. Some practical configuration and event-message information is contained in this manual.
PAGE 44
Introduction TACL RUN and NEWPROCESS Procedures For S-series systems, use the Distributed Systems Management (DSM) subsystem for installation. For G06 and above releases use PAM instead of TLAM. TACL RUN and NEWPROCESS Procedures TSP processes are started in one of three ways, as follows: • • • By the Subsystem Control Facility (SCF), as described below. This is the preferred method. From the TACL (Tandem Advanced Command Language) command interpreter, using a RUN command.
PAGE 45
PTrace Introduction PTrace PTrace selects, formats, and displays trace data that has been gathered by the SCF TRACE command. More detailed information on the PTrace displays for the OSI/TS subsystem is in the OSI/TS SCF Reference Manual. Inspect Inspect is a tool for debugging program code. It is used to check application program code when troubleshooting problems in your OSI/TS subsystem. More detailed information on Inspect is in the INSPECT Manual.
PAGE 46
G-Series Compatability Introduction Figure A-9. D to G Communication D-Series G-Series OSI/AS OSI/AS OSI/TS OSI/TS NSP NSP CDT 700.
PAGE 47
Communication between D-Series and G-Series Systems Introduction Communication between D-Series and G-Series Systems Figure A-10, G to D Communication shows a OSI stack running on a G-series system communicating with another OSI stack running on a D-series system. The NSP on Gseries can be X25AM, TCP/IP, or PAM; and the NSP on the D-series can be X25AM, TCP/IP, or TLAM. Figure A-10. G to D Communication G-Series D-Series OSI/AS OSI/AS OSI/TS OSI/TS NSP NSP CDT 701.
PAGE 48
Introduction Communication between D-Series and G-Series Systems OSI/TS Configuration and Management Manual—424831-001 1-16
PAGE 49
2 Background Information About Addressing This section provides background information about NSAP addressing and OSI/TS subdevice addressing needed when configuring an OSI/TS subsystem. This section is intended for anyone who must construct an NSAP address, use an NSAP address in a command, or write an application that uses OSI/TS.
PAGE 50
Background Information About Addressing SNPA Addresses Over LANs SNPA Addresses Over LANs In a LAN environment, the SNPA address is the fixed hexadecimal string FE followed by the MAC (medium access control) address of the LAN controller. The MAC address is assigned and hardwired into the controller by the manufacturer. Note that due to the lack of a common, formal definition for SNPA addresses, other OSI implementations may interpret the SNPA address as the MAC address only.
PAGE 51
Background Information About Addressing SNPA Addresses Over X.25 WANs SNPA Addresses Over X.25 WANs In X.25 networks, the SNPA address is the DTE address plus the port number, if any. The SNPA address is assigned by the X.25 network addressing authority, described later in this section. X25AM does not provide an SNPA address parameter that OSI/TS can use. Conceptually, however, the SNPA address can be described as follows: WAN (25.25) SNPA Address Consists of ...
PAGE 52
Background Information About Addressing Network Addressing Domains domain and, in turn, regulated by its parent authority (which in turn, may be regulated by its parent authority, and so on). Each addressing authority is independent of other addressing authorities on the same hierarchical level. The highest addressing authority is the one that governs the global network addressing domain. This authority is defined in ISO 8348, Addendum 2.
PAGE 53
Network Addressing Domains Background Information About Addressing Figure 2-1. NSAP Addressing Domains Global Network Addressing Domain Subdomain 2 Subdomain 1 Subsubdomain System System Subdomain 3 System System System Subdomain 4 System System System System System CDT 201.CDD Figure 2-2 shows the hierarchy of the network addressing domains in Figure 2-3.
PAGE 54
X.25 1980 Versus 1984 Addressing Background Information About Addressing Figure 2-2. NSAP Network Addressing Domain Hierarchy Global Network Addressing Domain Subdomain 1 System (NSAP Address) Subdomain 2 System (NSAP Address) Subsubdomain Subdomain 3 System (NSAP Address) Subdomain 4 System (NSAP Address) System (NSAP Address) CDT 202.CDD A single network addressing authority can govern one or more domains.
PAGE 55
Background Information About Addressing Structure of NSAP Addresses Outgoing Call Request Packets For outgoing call request packets, X25AM inserts called and calling address extensions if the subdevice is configured with local/remote address extension. Incoming Call Request Packets If an incoming call request packet contains a 1980-format called address, X25AM selects only subdevices with 1980-format local address configured, using the port number.
PAGE 56
AFI Component Background Information About Addressing Figure 2-3. NSAP Address Components NSAP Address IDP (Decimal Digits) AFI DSP (Encoded Syntax) IDI CDT 203.CDD The parts of an NSAP address are as follows: IDP The IDP (initial domain part) unambiguously identifies a subdomain at the highest level. This field is always expressed as a range of 2 through 17 decimal digits.
PAGE 57
IDI Component Background Information About Addressing • Significance (or lack thereof) of leading zero digits in the IDI Possible AFI values are shown in Table 2-1. Table 2-1. AFI Values DSP Syntax Decimal Binary IDI Format (Authority) IDI* nonzero IDI* zero IDI* nonzero IDI* zero X.121 36 52 37 53 ISO DCC 38 F.69 40 54 41 55 E.163 42 56 43 57 E.
PAGE 58
DSP Component Background Information About Addressing Table 2-2. IDI Values If the IDP Format (Authority) Is ... X.121 (CCITT X.121) ISO DCC (ISO 3166) F.69 (CCITT F.69) E.163 (CCITT E.163) The IDI Length is ... 14 digits maximum 3 digits 8 digits maximum 12 digits maximum E.164 ISO ICD 15 digits maximum 4 digits (CCITT E.164) (ISO 6523) Local null And the Meaning is ... X.
PAGE 59
Converting NSAP Addresses Background Information About Addressing Table 2-3. DSP Values If the IDI Format (Authority) Is ... Maximum DSP Length Is ... Binary Octets Decimal* Digits X.21 (CCITT X.121) 9 24 ISO DCC (ISO 3166) 14 35 F.69 (CCITT F.69) 12 30 E.163 (CCITT E.163) 10 26 E.164 (CCITT E.
PAGE 60
Background Information About Addressing Step 1: Converting to Network Layer Format Step 1: Converting to Network Layer Format NSAP addresses first must be converted into a computer-readable format, as follows: • AFI, IDI, and decimal-syntax DSP values Since these values are expressed in decimal digits, they can be easily used as input, as is. • DSP values: binary syntax Binary-syntax DSP values are represented in hexadecimal (two digits per octet).
PAGE 61
Nonstandard NSAP Address Representation Background Information About Addressing The Network Layer in OSI/TS does not perform the encoding Step 2 described earlier. Instead, it uses a simple conversion algorithm to convert HRPF-encoded NSAP addresses to NPDU address information. Nonstandard NSAP Address Representation In networks that include systems from manufacturers other than Compaq, some systems may locally employ nonstandard, vendor-specific representations of DSP values (for example, ASCII).
PAGE 62
Example 2: Locally Defined and Binary Syntax DSP Background Information About Addressing length. The meaning of each DSP value in this example is determined by the addressing authority for country X, and are as follows: This Position ... Means (in Country X) ... And Has This Value in This Example ...
PAGE 63
Background Information About Addressing Example 3: Locally Defined and ISO 646 DSP The meanings of the DSP values in this example are determined by a local addressing authority, Network Address Committee “Y,” and are as follows: This position ... 8 binary octets 12 hex. digits 2 hex. digits Means (According to Committee Y) ... And Has This Value in This Example ... (unknown meaning) IEEE MAC address of the local system NSAP selector on local end system 0102030405060708 08008E0002E3 01 Note.
PAGE 64
Background Information About Addressing Suggestions for Network Addressing Administrators The encoding process for this example NSAP actually follows the binary encoding rule for ISO 646 character DSP syntax. Notice that each pair of hexadecimal digits does not resemble its ISO 646 character code (in other words, the digits “21” do not resemble the character code for “A”).
PAGE 65
Background Information About Addressing What Are Subdevices? What Are Subdevices? Each OSI/TS subdevice corresponds to a single transport connection, and can be thought of as part of a transport service access point (TSAP). Subdevices configured with the same local TSAP address (in other words, they have the same X.
PAGE 66
Background Information About Addressing Address Sharing vs.
PAGE 67
3 Configuring the OSI/TS Subsystem This section describes how to install, configure, and start your OSI/TS subsystem interactively, using SCF. A discussion of how to configure large applications is also included, at the end of the section.
PAGE 68
Configuring the OSI/TS Subsystem Installing the Network Layer (I/O Processes) 2. Configuring the OSI/TS subsystem (TSP processes) Use SCF to alter the service and add subdevices. 3. Starting TSP processes Use SCF to start the TSP processes. Installing the Network Layer (I/O Processes) The OSI/TS subsystem depends on a communications I/O process to provide Network Layer services.
PAGE 69
X25AM SYSGEN Considerations Configuring the OSI/TS Subsystem Figure 3-1. TSP Process Supporting Multiple NSP Processes Layer Transport TSP Network Data Link NSP (X25AM) NSP NSP (TLAM/PAM) CDT 301.CDD X25AM SYSGEN Considerations The following points are important for correctly installing X25AM lines to be used by OSI/TS. X25AM PTP Protocol The OSI/TS subsystem uses the PTP (process to process) interface of X25AM.
PAGE 70
Configuring the OSI/TS Subsystem X25AM Subdevice Management Applications that use X25AM open these subdevices directly and call NonStop Kernel procedures, such as WRITEREAD, to initiate connections and transfer data across an X.25 network. However, when X25AM is to be used exclusively by OSI/TS, you do not need to define any subdevices. TSP adds subdevices to and deletes subdevices from the I/O processes dynamically, in response to application requests for services.
PAGE 71
Configuring the OSI/TS Subsystem X25AM Connection Problems Creating X25AM Subdevices: Attach Requests If multiplexing is not possible or the PASSIVEMUX attribute is set to OFF, then each time an attach request is received, the TSP process adds a new X25AM subdevice and posts a network attach request to that subdevice.
PAGE 72
Configuring the OSI/TS Subsystem TLAM SYSGEN Considerations TLAM SYSGEN Considerations The maximum TPDU size to be used for Transport Layer connections over TLAM is limited to the maximum I/O size supported by TLAM, as specified by the MAXIOSIZE attribute the MAXIOSIZE default is 32000. Ordinarily, the OSI/TS subsystem automatically determines each TLAM line’s maximum I/O size.
PAGE 73
Configuring the OSI/TS Subsystem • • Starting Network Lines Abort all transport subdevices before stopping TSP processes. This should be part of your normal shutdown procedure. Assign the same TLAM IOP to the same TSP process. Deleting TLAM Ports TLAM ports can only be deleted by aborting all the TSP subdevices; otherwise, TLAM ports are retained for the lifetime of the TSP process. Note. To change the value of the ESISENABLE attribute, you must first abort all the TSP subdevices.
PAGE 74
Configuring the OSI/TS Subsystem Using PAM with OSI/TS Using PAM with OSI/TS PAM is a system process that provides local-area, connectionless-mode subnetwork service over standard 802.3 and 802.4 networks. It has an application interface and an interface to SLSA that runs the data-link protocols (logical link control and CSMA/CD). Note that when you configure Layer 4 attributes to operate with PAM processes, you must specify the transport class 4 protocol.
PAGE 75
Configuring the OSI/TS Subsystem OSI/TS Installation Considerations If the PAM device is not operative while a TSP process has the ports opened, the TSP process attempts to delete them as soon as the error condition is detected. The TSP process also tries to recreate the PAM ports during the next attempt to establish a connection. OSI/TS Installation Considerations OSI/TS does not need to be installed using SYSGEN as do the underlying subsystems.
PAGE 76
Configuring the OSI/TS Subsystem • • • Capacity The interactions of the OSI/TS subsystem with applications and the operating system The physical layout and attributes of the subnetwork being used The meaning of the system generation program (SYSGEN) and subdevice configuration attributes Capacity If a TSP process is running in a high-performance-class CPU (such as a Cyclone), the maximum number of subdevices that can be configured is 1024.
PAGE 77
Configuring the OSI/TS Subsystem Process Attributes Process Attributes The processes in your OSI/TS subsystem include TSP processes, NSP processes (provided by X25AM or TLAM/PAM), and application processes. For each TSP process you add to your subsystem, you should consider the following OSI/TS PROCESS attributes: • • • PRIORITY LANDFT LANDFC The following subsections discuss each one of these attributes. PRIORITY Attribute The PRIORITY attribute specifies the execution priority for the process.
PAGE 78
Configuring the OSI/TS Subsystem • • • • • • Connection-Related Attributes DISCONNECTTIMEOUT CLASS CIRCUITS (Layer 3, X25AM) X25PORT (Layer 3, X25AM) X25PVC (Layer 3, X25AM) X25NCONMULTIPLEX (Layer 3, X25AM) MULTIPLEX Attribute The MULTIPLEX attribute allows multiple Transport Layer connections to use one Network Layer connection. Multiplexing transport connections on a single X.
PAGE 79
Configuring the OSI/TS Subsystem Connection-Related Attributes DISCONNECTTIMEOUT Attribute The DISCONNECTTIMEOUT attribute is similar to CONNECTTIMEOUT it, too, negatively affects throughput if the value is set too high. This attribute defines the amount of time TSP waits for a response to a DR-TPDU. If this value is set too high, connections could be delayed by being unnecessarily tied up during the connection-release timeout period.
PAGE 80
Configuring the OSI/TS Subsystem Traffic and Protocol Overhead Attributes X25NCONMULTIPLEX Attribute The X25NCONMULTIPLEX attribute specifies the maximum number of outgoing transport connections that can be multiplexed on an X.25 network connection. This attribute is valid only if the MULTIPLEX attribute enables multiplexing. You should set X25NCONMULTIPLEX to reflect the average amount of traffic expected for a given number of connections so that the network connection is not overloaded.
PAGE 81
Configuring the OSI/TS Subsystem Traffic and Protocol Overhead Attributes Checksums are needed only when a line is unreliable. When considering the use of checksums, you need to weigh the overhead incurred against the value of checksums to detect errors. Since each of these three attributes generates a checksum on a different part of the PDUs, you should set all three of these attributes to ON if your subsystem requires the use of checksums.
PAGE 82
Configuring the OSI/TS Subsystem Transport Class 4 Attributes Transport class 1 is a special case because in this class, any L4WINDOW value greater than 1 can lead to contention problems. This can occur when the sending transport entity waits for an acknowledgment of each DT-TPDU before sending the next one. This is an obvious case in which both sides of the connection need to be aware of what the other side is expecting.
PAGE 83
Configuring the OSI/TS Subsystem Miscellaneous Attributes WINDOWTIMEOUT Attribute The WINDOWTIMEOUT attribute defines the amount of time TSP waits before retransmitting up-to-date window information. This establishes a limit on the maximum interval between window updates. You should set this value high enough to ensure that update information is transmitted as often as is useful, yet low enough to ensure that it is lower than the INACTIVETIMEOUT at the other end of the connection.
PAGE 84
Configuring the OSI/TS Subsystem Configuring TSP Processes ESISESCONFTIME Attribute The ESISESCONFTIME timer defines how often a system reports its availability to an intermediate system on the same subnetwork. The lower the value, the more quickly other systems on the subnetwork become aware of the reporting systems availability. You must consider the tradeoff between this increased responsiveness and the increased use of resources in the subnetwork and in the recipient system.
PAGE 85
Configuring the OSI/TS Subsystem Starting TSP Processes You can use SCF to alter and display the permanently configured attributes of a subdevice associated with a TSP process. You can also use SCF to alter some process attributes. After your application opens a subdevice, it can call the SETPARAM and SETMODE procedures to dynamically change some subdevice attribute values.
PAGE 86
Starting TSP Processes Configuring the OSI/TS Subsystem NAME process-name The name of the TSP process. Local TSP process names can be up to 6 characters (the $ sign followed by 5 characters). Remote TSP process names can be up to 5 characters (the $ sign followed by 4 characters). For more information on naming TSP processes, see the subsection X25AM Subdevice Management, earlier in this section. NOWAIT Indicates that the process is not interactive and that control returns to the initiator immediately.
PAGE 87
Starting TSP Processes Configuring the OSI/TS Subsystem Table 3-1.
PAGE 88
Configuring the OSI/TS Subsystem Creating Configuration Command Files Creating Configuration Command Files You can develop a configuration command EDIT file by making a log file of your interactive commands while they are executing. After executing the necessary configuration commands, edit the log file, deleting any messages or command output that was returned. Use the resulting file as your configuration command file.
PAGE 89
Command File for Configuring OSI/TS Over an X.25 Network Configuring the OSI/TS Subsystem Figure 3-2 illustrates this example configuration. Figure 3-2. Example X.25 Loopback Configuration SU $tsp1.#251c SU $tsp2.#252c SU $tsp1.#251b SU $tsp2.#252b SU $tsp1.#251a SU $tsp2.#252a TSP1 X25A TSP2 X.25 X25B CDT 302.CDD The source code file for this example is provided as part of the OSI/TS software. It resides (by default) in the volume and subvolume $SYSTEM.ZOSITS.
PAGE 90
Configuring the OSI/TS Subsystem Command File for Configuring OSI/TS Over an X.25 Network tspobj/name $tsp1, nowait, cpu 0, pri 170/1 tspobj/name $tsp2, nowait, cpu 1, pri 170/0 confirm on ============================================================= == Configure and start X25AM lines.
PAGE 91
Command File for Configuring OSI/TS Over an X.25 Network, Using SNDCF Configuring the OSI/TS Subsystem , altclass 2, , x25port 8 multiplex on & == start su ($tsp1.*, $tsp2.*) Command File for Configuring OSI/TS Over an X.25 Network, Using SNDCF This is an example of a command file to configure a loopback test over an X.25 network, using SNDCF. In this configuration, there are two TSP processes: $tsp1 is the local process (the initiator), and $tsp2 is the remote process (the responder).
PAGE 92
Command File for Configuring OSI/TS Over a LAN Configuring the OSI/TS Subsystem alter service ($tsp1.#L3, $tsp2.#L3), ipx25sndcf on alter service ($tsp1.#L4, $tsp2.#L4), class 4, multiplex on ============================================================= == Add and start local (initiating) subdevice. ============================================================= add su $tsp1.
PAGE 93
Configuring the OSI/TS Subsystem Command File for Configuring OSI/TS Over a LAN The source code file for this example is provided as part of the OSI/TS software. It resides (by default) in the volume and subvolume $SYSTEM.ZOSITS.
PAGE 94
Configuring the OSI/TS Subsystem Command File for Configuring OSI/TS Over a LAN, Using ES-IS Routing Exchange Protocol == Add remote (responding) subdevices. == The MAC address of $lam1 is 08008e000012. == The MAC address of $lam2 is 08008e000013. == (If you don't specify the LANLOCALSNPA address, it is == obtained automatically by the TSP process.) ============================================================= add su $tsp2.#lan2a, nspdevice $lam2 & , localtsel "4501" & , localnsap "4501" add su $tsp2.
PAGE 95
Configuring the OSI/TS Subsystem Command File for Configuring OSI/TS Over a LAN, Using ES-IS Routing Exchange Protocol == == Run TSPOBJ to create and start the TSP processes. == tspobj/name $tsp1, nowait, cpu 0, pri 170/1 tspobj/name $tsp2, nowait, cpu 1, pri 170/0 confirm on ============================================================= == Alter service to enable ES-IS routing exchange protocol.
PAGE 96
Configuring the OSI/TS Subsystem Command File for Configuring OSI/TS Over a LAN, Using IP null Command File for Configuring OSI/TS Over a LAN, Using IP null This is an example of a command file to configure a loopback test over a LAN, using the inactive subset of the IP. In this configuration, there are two TSP processes: $tsp1 is the local process (the initiator), and $tsp2 is the remote process (the responder).
PAGE 97
Configuring the OSI/TS Subsystem Configuring Large X.25 Applications alter service ($tsp1.#L4, $tsp2.#L4), class 4 ============================================================= == Add and start local (initiating) subdevice. == The MAC address of $lam1 is 08008e000018. == The MAC address of $lam2 is 08008e0002e3. ============================================================= add su $tsp1.
PAGE 98
Single TSP Process Supporting Multiple X25AM Lines Configuring the OSI/TS Subsystem • • The application and the application environment allow the possibility of distributing the load (in terms of the number of connections or the aggregate bandwidth) over the underlying hardware and software components. The application environment requires the hot standby approach to provide fault tolerance.
PAGE 99
Configuring the OSI/TS Subsystem Single TSP Process Supporting Multiple X25AM Lines Limitations This type of configuration has the following limitations: Fault tolerance A single TSP process can also be the single point of failure. Any problem with this one process, or with the CPU in which it runs, affects the whole application.
PAGE 100
Configuring the OSI/TS Subsystem Single TSP Process Supporting Multiple X25AM Lines abort su $tsp1.* == Allow time to clean up all SUs. delay 10 abort process $tsp1 == == Run TSPOBJ to create and start the TSP processes. == tspobj/name $tsp1, nowait, cpu 0, pri 170/1 confirm on ============================================================= == Configure and start X25AM lines.
PAGE 101
One TSP Process Supporting Each X25AM Line Configuring the OSI/TS Subsystem == Add subdevices for line $X25C ============================================================= add su $tsp1.#lcs01, like $tsp1.#las01, nspdevice $x25c add su $tsp1.#lcs02, like $tsp1.#lcs01 add su $tsp1.#lcs03, like $tsp1.#lcs01 ============================================================= == Add subdevices for line $X25D ============================================================= add su $tsp1.#lds01, like $tsp1.
PAGE 102
Configuring the OSI/TS Subsystem One TSP Process Supporting Each X25AM Line Advantages This type of configuration has the following advantages: Fault tolerance Problems with any one process cannot disrupt the whole application. Any faulty process can be restarted and the full throughput restored in a short time. Load distribution It is possible to balance the load between the TSP processes.
PAGE 103
Configuring the OSI/TS Subsystem One TSP Process Supporting Each X25AM Line == NOTE: To use this command file for your subsystem, you == must supply names and addresses that reflect your == environment. ============================================================= == allow all errors == == Abort any processes and subdevices that are running and == that have the same name as you are configuring. == abort su ($tsp1.*, $tsp2.*, $tsp3.*, $tsp4.*) == Allow time to clean up all SUs.
PAGE 104
Configuring the OSI/TS Subsystem One TSP Process Supporting Each X25AM Line ============================================================= == Add subdevices for line $X25A ============================================================= add su $tsp1.#las01, nspdevice $x25a, x25port 01 & , localtsel "31", class 2 add su $tsp1.#las02, like $tsp1.#las01 add su $tsp1.#las03, like $tsp1.
PAGE 105
4 Performing Monitoring and Troubleshooting Guide This section contains general information on performance monitoring and on troubleshooting; it does not describe all possible combinations of what can occur in an OSI network.
PAGE 106
Performing Monitoring and Troubleshooting Guide Why Measure Performance? performance analysis concepts to identify potential sources of problems and areas that need further investigation. Why Measure Performance? The level of performance of your OSI/TS subsystem directly affects the level of performance of your entire system and your network and, ultimately, your company’s ability to do business effectively. Good performance is a large part of the value of your system to its users.
PAGE 107
Performing Monitoring and Troubleshooting Guide Monitoring Performance CPU, disk, or communications line, or by scheduling parts of the workload to run at different times of the day. The operating attribute values can also cause performance problems if they are set incorrectly or are set at non-optimum values for your system. These attribute values are set at system generation and in the configuration.
PAGE 108
Performing Monitoring and Troubleshooting Guide • What Performance Indicators to Monitor Performance statistics You can determine the amount of data sent and received by using the SCF STATS command. (Use the SCF STATS command to also look at TLAM/PAM port statistics; the value of undelivered AG SDUs might be an indication of an improper configuration.) You can determine response time using response time monitors, or by manually clocking responses at the terminals.
PAGE 109
Performing Monitoring and Troubleshooting Guide When to Monitor Performance When to Monitor Performance Tuning your system to improve performance is an iterative process that begins with initial configuration. As you monitor the system and uncover problem areas, you adjust and reconfigure to improve performance. To obtain appropriate performance data, you need to carefully select the times when monitoring activities are performed. If possible, measure the system for a full day.
PAGE 110
Performing Monitoring and Troubleshooting Guide Impact of Changes Impact of Changes Finally, keep in mind that making changes to any one of the factors discussed in this section may have only a minor impact on total system performance. However, making changes to a number of these factors together can result in improved levels of performance.
PAGE 111
Benefits of Using CHECK SU Performing Monitoring and Troubleshooting Guide A typical CHECK SU display without the DETAIL option is as follows: OSITS Check SU Level SU/Process Name Last Error Error Source State TSU: TSP: NSP: $myap $tsp1.#z000001 $x25a.#tsp1345 0 0 TCon established Started/Ready TSU: TSP: NSP: \comm.$myap \comm.$tsp1.#z000002 \comm.$lam1.#tsp1fe 0 0 TCon established Started/Ready TSU: TSP: NSP: \comm.$app2 \tsii.$tsp1.#z000003 \tsii.$x25a.
PAGE 112
Performing Monitoring and Troubleshooting Guide Some Words of Caution being used by an particular application), then CHECK SU finds the related NSP subdevices . Some Words of Caution Before using CHECK SU, make sure you have planned for the following: • • • • • • Use the wild card option with great care, especially in a busy OSI network. Wild cards can have an effect on the performance levels of TSP processes that are queried. Use of wild cards alone, without a partial name, is not recommended.
PAGE 113
Performing Monitoring and Troubleshooting Guide Examples Examples The following examples show some of the different options that can be used with the CHECK SU command. The following command displays information about all subdevices being used by the application process $MYAPP and are associated with the TSP server $TSP1. Note that this command displays information for all levels because the command defaults to ALL: CHECK SU $TSP1.
PAGE 114
Performing Monitoring and Troubleshooting Guide Common Causes of Problems example, NSP processes support Layer 2 and the X.25 I/O operations in Layer 3; TSP processes support Layer 4 and the LAN I/O operations in Layer 3. One of the advantages of OSI is that problems can be diagnosed and tracked to a distinct layer; you don't always need to concentrate on the entire communications environment. Of course, no layer is completely independent.
PAGE 115
Performing Monitoring and Troubleshooting Guide • • Components of Problem Analysis Failure to receive transport connections Unexpected disconnection of transport connections The following subsections discuss these areas. Outgoing Transport Connection Request Failures The most frequent reasons for this kind of problem are errors in the configuration of remote addresses (NSAP, X.25 destination address, or remote TSEL) and local addresses. Check and verify these addresses by looking at a trace of the X.
PAGE 116
Performing Monitoring and Troubleshooting Guide TSP Process Problems Major Subsystem Components When discussing top-down troubleshooting strategies, it is helpful to break down the OSI/TS subsystem into three major components: • • • The user's application The TSP process (including IP in the Network Layer, if you are using TLAM/PAM) The NSP process (TLAM/PAM or X25AM) In the following subsections, problem-solving information for each of these three major components is broken down into the following cat
PAGE 117
Trace and Trace Analysis Performing Monitoring and Troubleshooting Guide STATS SERVICE $TSP1.* The following command displays information on the TPDUs transferred through a specific subdevice: STATS SU $TSP2.#Z000001 Trace and Trace Analysis The following PTrace commands are highly useful for obtaining Transport Layer information. The order of the items roughly follows a top-down troubleshooting method.
PAGE 118
Performing Monitoring and Troubleshooting Guide Troubleshooting Example SELECT L4; FILTER L4SERVICES; NEXT A typical record displayed by this command is as follows: 17:11:52:960 >000.040 #19 T-CON attach BufLen: 0 T-Primitive Addr: 1930676 SU: #Z000006 You can check specific TPDUs by specifying them in the FILTER command.
PAGE 119
Troubleshooting Example Performing Monitoring and Troubleshooting Guide 3. Analyze what the application is doing, using SCF. 4. Review the statistics, using SCF. 5. Collect trace information, using SCF. 6. Analyze the trace, using PTrace. 7. Correct the problem. Step 1: Reset the Statistics Counters and Rerun the Application Reset all the statistics counters. A discussion on how to set up an SCF command file to reset all your statistics counters is included at the end of this section.
PAGE 120
Troubleshooting Example Performing Monitoring and Troubleshooting Guide The screen does not show any errors for the TSP subdevice or for the NSP subdevice associated with the TSP subdevice. Note that if the TSP process has many subdevices opened and another Compaq OSI product is also being used, it may be difficult to associate a particular subdevice with a particular application. In this case, you might use the command CHECK SU $TSP.*, APPL to find the information.
PAGE 121
Troubleshooting Example Performing Monitoring and Troubleshooting Guide that the Network Layer must be intact. (Remember that no TPDUs can be exchanged until the Network Layer has established a connection and has moved into the data transfer phase.) You should now look at the X.25 statistics to prove your conclusion. But first you need to find out the name of the line. Either of the SCF commands status su $tsp2.*, detail check su $tsp2.
PAGE 122
Troubleshooting Example Performing Monitoring and Troubleshooting Guide This screen shows that data packets are being exchanged. This information definitely points to the Transport Layer as the source of the connection problem. Now you can check the statistics for the TSP subdevice. The SCF command stats su $tsp2.#z000022 displays the following: OSITS Stats SU $TSP2.#Z000022 Reset Time.. 10 Oct 1991, 19:31:21.795 Sample Time. 10 Oct 1991, 19:34:44.003 TPDUsSent......... TPDUsResent....... UserBytesSent..
PAGE 123
Performing Monitoring and Troubleshooting Guide Troubleshooting Example ptrace from tr1 starts the PTrace trace formatter on the trace located in the file TR1 and displays the following: Trace of: Ptrace Data File: Trace started: First trace entry: Last trace entry: Trace entry size limit: \MARS.$TSP2, Type (55,4). $DIAG.MYSTUFF.TR1 10/10/91 10:32:00.570714 10/10/91 10:32:00.139621 10/10/91 18:07:26.297123 1008 You should next set up the select mask and the filters for the trace.
PAGE 124
Performing Monitoring and Troubleshooting Guide Troubleshooting Example Record #70 indicates that the CR-TPDU is answered with a DR-TPDU. The reason given is that there is no Session Layer entity (in other words, no transport user) to accept the connection request. So far, you have established that: • • The TSP process refused an incoming connection. The reason is that there is no transport user to accept the connection.
PAGE 125
Troubleshooting Example Performing Monitoring and Troubleshooting Guide info su $tsp2.#z000022,detail displays the following: OSITS Detailed Info SU $TSP2.#Z000022 *AltClass.......... *Class............. 0:00:06.000 *DeleteTime........ 0:00:06.000 *Expedited......... *InactiveTimeout... *IPX25SNDCF........ *LANlocalSNPA...... *LANremoteSNPA..... *LocalNSAP......... *LocalTSEL......... *MaxRexmit......... *NetType........... $X252 *RecvSecurity...... *RefTimeout........ *RemoteNSAP........ *RemoteTSEL....
PAGE 126
Performing Monitoring and Troubleshooting Guide NSP Process Problems: X25AM trace process $tsp2, to tr1 While the trace is running, rerun the application. You can see that the transport connection is successful. Stop the trace: trace process $tsp2, stop Use PTrace to analyze the trace. This time you need to look only at the TPDUs, filtering for Layer 4.
PAGE 127
Performing Monitoring and Troubleshooting Guide • • • SCF Commands Clear packets in response to call requests Intermittent REJECT or RNR packets returned Frequent RESTART or RESET packets SCF Commands The STATS LINE command displays counters for all the different types of packets sent and received on an X25AM line. For example, the following command is issued on a line named $X251: STATS LINE $X251 Check for unusually high numbers of RNR, REJ, RESET, and RESTART packets.
PAGE 128
PTrace and Trace Analysis Performing Monitoring and Troubleshooting Guide CONTROL request is in P4 (in the range P1-6, the fourth word): Control 11 (%000013): 02:48:44:270 >000.010 #31 L4^LCB^In SDN #001/%001 Control LCB 77BF P1-6 %144000 %000026 %000000 %000013 %000020 %000000 When troubleshooting an OSI/TS subsystem using X25AM, you seldom need to look at more than the SELECT L3 mask. This mask causes all the packets to be displayed, along with most of the attributes related to the connection.
PAGE 129
Performing Monitoring and Troubleshooting Guide Troubleshooting Example Troubleshooting Example The following is an NSP (X25AM) problem that you may encounter. The steps in this example illustrate the logic you might follow when using a top-down problem-solving approach. Symptoms In this example, the application cannot establish a connection with a remote application. All attempts to initiate a connection end quickly with errors. The following steps are used to solve this problem: 1.
PAGE 130
Troubleshooting Example Performing Monitoring and Troubleshooting Guide status su $tsp1, detail displays the following: OSITS Detailed Status SU \MARS.$TSP1.#Z000022 State........ TC State..... TC Substate.. Opener....... NSP SU....... STARTED tcon not established ndis received \MARS.$6,190 \MARS.$251.#TSP1002 NSP Subsys....... FileError........ NSPDSMRetCode.... NSPDSMSubCode1... NSPDSMSubCode2... NSPFSErrorCode... X25ClearCause.... X25DiagCode...... X25DisconReason..
PAGE 131
Troubleshooting Example Performing Monitoring and Troubleshooting Guide included in Appendix B, X.25 Status Code Tables as a convenience. See the X.25 Access Method (X25AM) Manual for more information on disconnect reason codes.) This information points to a possible configuration error–the remote DTE address is probably not configured correctly into the subdevice. Since this is a pretty straightforward problem, you could skip the new few steps and fix the problem.
PAGE 132
Performing Monitoring and Troubleshooting Guide Troubleshooting Example Next you should take a look at the NSP statistics for Layer 3 to verify whether a connection occurred. But first you need to find out the line name. Either of the SCF commands status su $tsp1.#z000022, detail check su $tsp1.#z000022, detail displays a status screen from which you can get the line name. An example screen is included in the previous TSP example. In this case, the screen would show that the line name is $X251.
PAGE 133
Performing Monitoring and Troubleshooting Guide Troubleshooting Example Step 4: Collect Trace Information, Using SCF To find out the real nature of the problem, you need to generate a trace. Since you have narrowed the problem down to the Network Layer, you can concentrate on tracing the X.25 LINE object only. The following SCF command starts the trace: trace line $x251, to trx1 While the trace is running, rerun the application. After recording the problem, be sure to stop the trace.
PAGE 134
Performing Monitoring and Troubleshooting Guide Troubleshooting Example plus the subdevice port number) is 408333111102. The length of the facility field is 03 bytes. The facility field is 430202; this is the negotiated window size. 05:23:13:420 >000.030 #60 L3 Pkt In SDN #001/%001 LEN #0005 GFI(0001) MOD8 Clear 000: 1001 1300 81 CAUSE CODE: $00 DIAGNOSTIC CODE: $81/129 LGN/LCN $001 Record #60 shows that a clear packet was received with reason code 81, in response to the call request packet.
PAGE 135
Troubleshooting Example Performing Monitoring and Troubleshooting Guide ptrace from trx; select l3 displays the following: Trace of: \MARS.$X251, Type (61,0). Ptrace Data File: $DIAG.MYSTUFF.TRX Trace started: 10/16/91 05:36:16.46 First trace entry: 10/16/91 05:36:16.46 Last trace entry: 10/16/91 05:36:40.23 Trace file is an extended format.
PAGE 136
Performing Monitoring and Troubleshooting Guide NSP Process Problems: TLAM NSP Process Problems: TLAM In an OSI/TS subsystem, TLAM is not considered to be a network service provider; this function is included in the TSP process. Nevertheless, TLAM is a distinct process that can be analyzed separately when troubleshooting problems in the Data Link Layer and below. SCF Commands You can use the following command to display the total number of 802.
PAGE 137
SCF Commands Performing Monitoring and Troubleshooting Guide STATS SERVICE $LAM2.#L18023 The following screen is returned for this example command TLAM Stats SERVICE $LAM2.#L18023 Sample Time..... 10 Oct 1991, 12:05:08.244 Reset Time...... 10 Oct 1991, 0:00:46.734 802.3 (CSMA/CD) STATS FramesDiscarded......... 0D LackOfResourceErrors. 0D ReceiveOverruns......... 0D TransmitUnderruns.... 0D FramesTransmittedOK..... 6056D OctetsTransmittedOK..... 557100D FramesReceivedOK..... 17836D OctetsReceivedOK.....
PAGE 138
PTrace and Trace Analysis Performing Monitoring and Troubleshooting Guide STATS SERVICE $TSP1.#L3 The following screen is returned for this example command: OSITS Tsp Stats SERVICE $TSP1.#L3 Reset Time.. 10 Oct 1991, 10:53:40.901 Sample Time. 10 Oct 1991, 12:23:33.373 IPPDUs-sent....................... IPPDUs-received................... IPOctets-sent..................... IPOctets-received................. 92 96 6248 6906 IPDiscardAddr..................... IPDiscardAddrThld.................
PAGE 139
Performing Monitoring and Troubleshooting Guide PTrace and Trace Analysis The screen returned for this command is as follows: ?FIND "LSAP : 000254" 02:49:29:370 >000.
PAGE 140
Performing Monitoring and Troubleshooting Guide NSP Process Problems: PAM NSP Process Problems: PAM In an OSI/TS subsystem, PAM is not considered to be a network service provider; this function is included in the TSP process. Nevertheless, PAM is a distinct process that can be analyzed separately when troubleshooting problems in the Data Link Layer and below. SCF Commands The following command displays useful information about the aggregate SDUs: STATS PORT $LAM1.
PAGE 141
Performing Monitoring and Troubleshooting Guide Command File for Resetting Statistics Counters 3. Rerun the application to record the problem. 4. Stop the traces. 5. Make a log of all the statistics and configuration information. 6. Collect any other relevant information and supporting documentation, such as EMS logs, error-message codes, Inspect save files if appropriate, and a description of the problem and accompanying symptoms.
PAGE 142
Performing Monitoring and Troubleshooting Guide Command File for Resetting Statistics Counters comment - This SCF command file resets all service, process, comment - and subsystem statistics counters. comment - It can be used on a K-series system only comment - Reset TSP process AND SUBDEVICE comment - file system counters. stats process $tsp1,reset stats process $tsp2,reset stats su $tsp1.*,reset stats su $tsp2.*,reset comment - Reset service for all layers. stats service $tsp1.
PAGE 143
Performing Monitoring and Troubleshooting Guide Command File for Resetting Statistics Counters These commands are not generic. To use them, you must change the names to reflect your configuration. --------------------------------------------------------------------------COMMENT - THIS SCF COMMAND FILE DISPLAYS AND LOGS DIAGNOSTIC COMMENT - INFORMATION. COMMENT - This file can be used only in a K-series system. allow all errors detail logtime both COMMENT - START UP THE LOG FILE (VERY IMPORTANT).
PAGE 144
Performing Monitoring and Troubleshooting Guide Command File for Resetting Statistics Counters These commands are not generic. To use them, you must change the names to reflect your configuration. --------------------------------------------------------------------------COMMENT - THIS SCF COMMAND FILE DISPLAYS AND LOGS DIAGNOSTIC COMMENT - INFORMATION.
PAGE 145
Performing Monitoring and Troubleshooting Guide Command File for Obtaining Diagnostic Information Command File for Obtaining Diagnostic Information The following is a set of SCF commands that can be used in a K-series system to collect and display all the service and process statistics and other information needed by your service representative. We recommend that you set up an SCF command file and then use the OBEY command to invoke the file. You must be a super-group user to use this SCF command file.
PAGE 146
Performing Monitoring and Troubleshooting Guide Command File for Obtaining Diagnostic Information The following is a set of SCF commands that can be used in a S-series system with SUT G06 and above, to collect and display all the service and process statistics and other information needed by your service representative. We recommend that you set up an SCF command file and then use the OBEY command to invoke the file. You must be a super-group user to use this SCF command file.
PAGE 147
5 OSI Transport Services In an OSI network, the Transport Layer provides application processes with host-to-host data-transfer services. To provide these services, the Transport Layer uses the services provided by the Network Layer. This section explains how the OSI/TS subsystem uses and augments the services provided by the Network Layer.
PAGE 148
Transport Service Primitives OSI Transport Services Table 5-1.
PAGE 149
Protocol Classes OSI Transport Services Called address Responding address Disconnect reason Transport user data Specifies the transport service access point (TSAP) address of the responding (remote) transport user. Specifies the address (TSAP) of the responding (remote) transport user to which transport connection has been established. It must be the same as the called address in the connect request and indication service primitives.
PAGE 150
Class 1: Error Recovery OSI Transport Services Class 0 is best suited for nonmultiplexed applications for which the rate of errors generated by the subnetwork is acceptable. It provides the highest performance for applications that can tolerate the absence of error handling. Class 1: Error Recovery Protocol class 1 provides the services of class 0, plus error recovery. It provides mechanisms for recovering from subnetwork reset or disconnect indications.
PAGE 151
Corrupted TPDUs OSI Transport Services Table 5-3.
PAGE 152
Data TPDU Numbering OSI Transport Services Data TPDU Numbering OSI/TS assigns a sequence number (TPDU-NR) to all transmitted-data TPDUs (DT-TPDUs). The sequence begins with 0 and increments by 1, except in class 0, where TPDU-NR is always 0. After the maximum TPDU-NR is assigned, the counter returns to 0. The maximum counter number allowed depends on the protocol class and on whether extended format addressing is used.
PAGE 153
Resynchronizing the Data OSI Transport Services is confirmed, OSI/TS considers the transport connection released and informs users by issuing file-system error 140. The OSI/TS Subsystem as Responder As the responder, the OSI/TS subsystem does not try to reassign the transport connection, but waits for reassignment from the peer entity that initiated the connection. On receipt of a disconnect indication, OSI/TS starts the timer TWR.
PAGE 154
Retention of TPDUs OSI Transport Services The OSI/TS Subsystem as Responder The OSI/TS subsystem initiates passive resynchronization by starting the TWR timer. TWR determines the length of time OSI/TS waits for a valid TPDU. If TWR times out before a valid TPDU is received, OSI/TS considers the transport connection released and informs users by issuing file-system error 140.
PAGE 155
Addressing OSI Transport Services the transport connection to a new network connection and performs the resequencing procedure. Addressing TPDUs are sent through a network service access point (NSAP). NSAP addresses are globally defined by the authority responsible for the network addressing domain. See Section 2, Background Information About Addressing for a detailed explanation of addresses.
PAGE 156
Address Sharing OSI Transport Services Figure 5-1. Address Sharing TSAP Addresses NSAP Addresses (1984) or Ports (X.25 Subaddresses, 1980) X.25 DTE Address or LAN Station Address CDT 501.CDD Address sharing can be implemented at various levels, as discussed in the following subsections. Note that address sharing is not the same as multiplexing, which is discussed later in this section. Address Sharing for X.25 Networks There are several levels of address sharing possible for X.
PAGE 157
Called/Calling and SRC-REF/DST-REF Addresses OSI Transport Services Address Sharing for LANs For LANs, all transport connections by default share the same TLAM (for D-series and pre-G06 releases, or PAM, for G06 and above releases) port (LAN station address). The possible levels of multiplexing are as follows: • NSAP address The NSAP address provides the first level of address sharing. With this option, several NSAPs can share the same LAN station address.
PAGE 158
Multiplexing OSI Transport Services Figure 5-2. Relationship Between SRC-REF and DST-REF Initiating Transport Entity CR-TPDU SRC-REF DST-REF DT-TPDU DST-REF Responding Transport Entity 12 00 CC-TPDU SRC-REF DST-REF 46 12 DT-TPDU DST-REF 12 46 CDT 502.CDD Note that for the protocol classes that do not provide multiplexing (classes 0 and 1), SRC-REF and DST-REF are not used that is, they do not appear in the DT-TPDU.
PAGE 159
Connection Multiplexing OSI Transport Services Figure 5-3. Connection Multiplexing Transport Connection Network Connection (X.25 Virtual Circuit) Physical Connection CDT503.
PAGE 160
Passive Multiplexing OSI Transport Services Passive Multiplexing Passive multiplexing is a form of connection multiplexing in which only one X25AM subdevice is created instead of one subdevice for each incoming attach request. This type of multiplexing is done in anticipation of connection multiplexing by the remote system.
PAGE 161
6 Managing a Transport Connection The management of a transport connection is divided into three protocol phases: Connection establishment Data transfer Connection release During each phase, transport peer entities coordinate their activities and provide services by exchanging messages through subnetwork connections. These messages are transport protocol data units (TPDUs). This section describes these three protocol phases.
PAGE 162
Managing a Transport Connection Protocol Negotiation Protocol Negotiation During the connection-establishment phase, correspondent transport peer entities negotiate the services they will provide on the transport connection.
PAGE 163
Requesting a Connection Managing a Transport Connection Requesting a Connection After receiving a T-CONNECT service primitive over a connection-oriented subnetwork, OSI/TS determines whether a connection is already open to the same NSAP for this transport entity. If a connection exists, it is used, unless the transport connection currently assigned to it does not allow multiplexing. If no connection exists, OSI/TS requests one. No subnetwork connection is required in a connectionless environment.
PAGE 164
Building the CR-TPDU Managing a Transport Connection TPDU. The default value is 4. You can use SCF to alter this parameter. Note that this parameter is subject to change, based on the content of the CC-TPDU. DST-REF (Octets 3 and 4) OSI/TS sets the DST-REF (destination reference) parameter to 0. The remote transport entity uses this field to assign its own unique internal reference to the connection. Note that this parameter is subject to change, based on the content of the CC-TPDU.
PAGE 165
Building the CR-TPDU Managing a Transport Connection Variable Part The variable part of a CR-TPDU contains some or all of the following information: Alternate protocol class If no alternate class is configured, OSI/TS does not send a value in the CR-TPDU. Security Is included in the variable part of the CR-TPDU if you supply it maximum 16 octets. You can specify this sendsecurity parameter interactively using SCF, or your application can specify it dynamically in a SETPARAM 12 call.
PAGE 166
Successful Connection Initiation Managing a Transport Connection The number of fields in the variable part of the CR-TPDU varies according to the class and configuration. Successful Connection Initiation After sending a CR-TPDU, OSI/TS cannot complete connection establishment and enter the data-transfer phase until it receives a valid CC-TPDU from the remote transport peer entity. This TPDU contains response values for connection parameters that OSI/TS requested in the CR-TPDU.
PAGE 167
Managing a Transport Connection Connection-Initiation Failure The class in the response must have the same multiplexing capabilities as the requested class. If the transport protocol is operating over a local area subnetwork, OSI/TS accepts only class 4 in the response. Expedited Data If the connection request asks for transport-expedited data and the responder rejects it, OSI/TS does not use expedited data. If the connection request did not ask for expedited data, the responder cannot.
PAGE 168
Managing a Transport Connection Application Manages the Response Protocol users have to give OSI/TS permission to respond to incoming connection requests. This permission is a file-system call that does not correspond exactly to any OSI transport service primitive. OSI/TS allows you to specify whether the subsystem or your application manages the responder protocol. It is more convenient for the application if the OSI/TS subsystem manages the responder protocol.
PAGE 169
Managing a Transport Connection Application Retry 3. OSI/TS completes the CONTROL 11 call. This completion signals the application that a connection is established. Nevertheless, it does not correspond to the exchange of a transport service primitive. CC-TPDU Parameters The following paragraphs describe how OSI/TS sets CC-TPDU parameters as a connection responder. (See Figure 6-1 and the explanation that follows it.
PAGE 170
Managing a Transport Connection OSI/TS as Connection-Establishment Initiator OSI/TS as Connection-Establishment Initiator The application should try to determine the reason for the failure. You can get error information either by using a WRITEREAD request with the appropriate MCW or by using the SPI STATUS SU command. If the failure is permanent, the application should do the following: • • Not retry the connection attempt. Report the error to the user or operator via EMS.
PAGE 171
Managing a Transport Connection Concatenation and Separation of TPDUs Some services that transport peer entities provide during the data-transfer phase are: Concatenation Concatenation of multiple TPDUs into a single packet. The receiving transport entity separates the packet into TPDUs before passing the data to the local transport-service user. Segmentation Segmentation of user messages into smaller units that are compatible with the subnetwork.
PAGE 172
Managing a Transport Connection • • Flow Control Upon receipt of a T-EXPEDITED DATA request, OSI/TS sends the TSDU in an ED-TPDU. No segmentation and reassembly is performed on expedited data. EDTPDUs are placed ahead of other TPDUs in the output queue of a transport connection endpoint. Upon receipt of an incoming ED-TPDU from a remote peer, OSI/TS passes a T-EXPEDITED DATA indication to the transport user and acknowledges receipt by sending an EA-TPDU to the remote peer.
PAGE 173
Managing a Transport Connection Connection Release When receiving DT-TPDUs, OSI/TS uses AK-TPDUs to advance the remote transmit window. OSI/TS sends an AK-TPDU only if a READ call is outstanding. If OSI/TS cannot forward a received TPDU to the user because a READ call is not outstanding, no AK-TPDU is sent. Receipt of an AK-TPDU that sets the lower window edge to more than one greater than the TPDU-NR of the last TPDU is not considered an error, unless it acknowledges DT-TPDUs that have never been sent.
PAGE 174
Managing a Transport Connection Connection Release in Classes 1 Through 4 3. If DISCONNECTTIMEOUT expires before either a DC-TPDU or DR-TPDU has been received, OSI/TS considers the connection released. All pending file-system requests on the connection are completed with error 140. Over connectionless network service, OSI/TS transmits DR-TPDUs up to MAXREXMIT times, waiting for a DR-TPDU or DC-TPDU. If OSI/TS is using protocol classes 0 or 2, no recovery mechanisms are provided.
PAGE 175
7 NonStop Kernel File-System Interface Applications use procedure calls to access Compaq OSI/TS subdevices and communicate with remote transport users in an OSI network. Use standard filesystem procedure calls to manage transport connections and transfer data. The System Procedure Calls Reference Manual contains detailed descriptions of these calls.
PAGE 176
Setting and Modifying Subdevice Values NonStop Kernel File-System Interface TSP processes are started either by an operator, from the command interpreter, or by an application, using a file-system call. Use the following implicit RUN command to start TSP from the TACL command interpreter: TSPOBJ / run-option-list / [ backup-cpu ] See Section 3, Configuring the OSI/TS Subsystem for further details on starting the TSP process and configuring the OSI/TS subsystem.
PAGE 177
Setting and Modifying Subdevice Values NonStop Kernel File-System Interface Table 7-1.
PAGE 178
Setting and Modifying Subdevice Values NonStop Kernel File-System Interface Table 7-1. Setting Subdevice (SU) Parameters Subdevice (SU) Parameter SCF Attribute Window information retransmission timer WINDOWTIMEOUT X.25 accept charge X25ACCEPTCHG X.25 bilateral closed user group X25BCUG X.25 closed user group X25CUG X.25 type of closed user group X25CUGTYPE X.25 destination address X25DESTADDR X.25 parameter negotiation X25NEGOTIATE, X25NONEGOTIATE X.25 port address X25PORT X.
PAGE 179
Setting and Modifying Subdevice Values NonStop Kernel File-System Interface Table 7-2.
PAGE 180
Setting and Modifying Subdevice Values NonStop Kernel File-System Interface Table 7-2. Setting SERVICE Parameters SERVICE Parameter SCF Attribute X.25 port address X25PORT X.25 priority calling X25PRICALL X.25 PVC channel X25PVC X.25 network X25REMOTENET X.25 recognized private operating agency X25RPOA X.25 reverse charge X25REVERSECHG X.25 throughput class X25THRUPUT X.
PAGE 181
Preparing to Establish a Connection NonStop Kernel File-System Interface Table 7-2.
PAGE 182
NonStop Kernel File-System Interface Preparing to Establish a Connection OPEN procedure Establishes a communications path between the application and the OSI/TS subsystem. SETPARAM fetches and sets subdevice characteristics (optional). SETMODE and SETMODENOWAIT Initialize subdevice parameters to their configured values and enables out-of-sequence completions when nowait I/O is specified.
PAGE 183
Preparing to Establish a Connection NonStop Kernel File-System Interface Figure 7-1.
PAGE 184
Opening a Subdevice NonStop Kernel File-System Interface Figure 7-2.
PAGE 185
NonStop Kernel File-System Interface Setting and Retrieving Subdevice Parameters ) procedure performs this task. In the OPEN call, you specify the name of the OSI/TS subdevice and, in the flag word, several important parameters: Shared or exclusive access to the subdevice If more than one application uses the subdevice or if the application opens it more than once, you must indicate shared access. Read/write access mode You must specify this mode.
PAGE 186
SETPARAM 1 NonStop Kernel File-System Interface Table 7-3. SETPARAM Functions SETPARAM Operation Function Set or fetch TPDUs. Set or fetch Set or fetch Set or fetch 12 13 14 15 security parameter to be validated in incoming CRmultiplex parameter. local TSEL. local TSEL.15Set or fetch remote TSEL. The SETPARAM operations and examples of SETPARAM calls are discussed in the following subsections.
PAGE 187
SETPARAM 10 NonStop Kernel File-System Interface old^remote^dte is the current remote DTE address. SETPARAM 10 The subdevice status block contains a description of the current subdevice configuration and protocol state. After the connection-establishment phase, the subdevice status block contains the results of protocol negotiation.
PAGE 188
SETPARAM 10 NonStop Kernel File-System Interface Figure 7-3. Subdevice Status Block (SETPARAM 10) Octets 0-1 Size of Fixed Part (=20) Octets 2-9 Subdevice Name Octets 10-11 Current Connection State Octets 12-13 Protocol Class Octets 14-15 Maximum TPDU Size Octets 16-17 Version Number Octets 18-19 Additional Options Variable Length Variable-Length Records CDT 703.CDD The following subsections explain the fields in the subdevice status block.
PAGE 189
SETPARAM 10 NonStop Kernel File-System Interface Table 7-4.
PAGE 190
SETPARAM 10 NonStop Kernel File-System Interface Protocol Class (Octets 12 and 13) This field indicates the current protocol class. The value is not significant if the primary connection state is 4 (connection not established). Maximum TPDU Size (Octets 14 and 15) This field indicates the maximum TPDU size permitted, in octets. Version Number (Octets 16 and 17) This field specifies current Compaq version number of the OSI/TS software.
PAGE 191
SETPARAM 10 NonStop Kernel File-System Interface Figure 7-5. Subdevice Status Block Variable-Length Record • • • RecordLength Length Record Octet n Octet n + 1 Record Type Octet n + 2 Through Octet n + Length Data • • • CDT 705.CDD The following list describes the components of variable-length records. Record Length A one-octet field that indicates length of record (excluding this field) in octets. Record Type A one-octet code that indicates type of record.
PAGE 192
SETPARAM 11 NonStop Kernel File-System Interface If a subdevice is configured for a remote address and a connection has been established, the actual address of the remote TSEL or remote NSAP is returned in the status block. If a connection has not been established, the configured address of the remote TSEL or remote NSAP is returned. If a subdevice is not configured for a remote address, no remote address is returned, regardless of the connection mode.
PAGE 193
SETPARAM 13 NonStop Kernel File-System Interface rcv^security contains the new receive-security string to be associated with this subdevice. size contains the length of the string. To fetch the current receive-security string, your application issues the following: CALL SETPARAM old^size); ( filenum, 12, , , old^rcv^security, old^rcv^security and old^size contain the current receive-security and size values, respectively.
PAGE 194
SETPARAM 15 NonStop Kernel File-System Interface subdevice cannot be multiplexed with other transport connections onto the same network connection. You can use SCF to set this attribute, or your application can set it using the following: CALL SETPARAM ( filenum, 14, local^tsel, size ) local^tsel contains the local TSEL, a hexadecimal ASCII string up to 64 digits long. size contains the length of the address. If you set size to 0, the current local TSEL is cleared from the subdevice.
PAGE 195
Initializing the Subdevice and Preparing for Nowait I/O NonStop Kernel File-System Interface old^remote^tsel is the current remote TSEL. Initializing the Subdevice and Preparing for Nowait I/O You can use the SETMODE or the SETMODENOWAIT procedure to initialize all subdevice parameters to the values configured at the time the subdevice was opened.
PAGE 196
WRITEREAD Procedure NonStop Kernel File-System Interface The subdevice through which connection-establishment requests are issued must contain the correct address of the device with which you want to exchange data. You can assign a set of remote addresses to a subdevice by using SCF, or your application can alter the remote DTE or TSELs associated with your subdevice by issuing, respectively, a SETPARAM 1 call or a SETPARAM 15 call.
PAGE 197
CONTROL 17 Procedure NonStop Kernel File-System Interface If you expect the remote peer to send data with the CC-TPDU, be sure to provide enough space for the read buffer by specifying a large enough value in read-count. If the read buffer is not large enough to contain incoming data, OSI/TS discards the data and completes your request with file-system error 22. The maximum amount of user data that can be included in a CC-TPDU is 32 octets.
PAGE 198
NonStop Kernel File-System Interface Responding to Connection Requests The remote TSEL with which you want to establish a connection is an attribute of the subdevice. To make outgoing calls through the subdevice, this address must be specified. The remote TSEL is specified when the subdevice is added using SCF, or your application sets it by issuing a SETPARAM 15 call. The CONTROL request completes when the connection handshaking procedure completes successfully or aborts.
PAGE 199
NonStop Kernel File-System Interface OSI/TS Subsystem Manages the Response Protocol OSI/TS associates the connection request with the first subdevice that matches the local TSEL. Either of the following two conditions constitutes a match: • • Lengths and values are identical in the CR-TPDU and the subdevice. The local TSEL is unspecified. CR-TPDUs might not have TSELs specified. If a TSEL is not specified, NSAPs are used to determine the subdevice.
PAGE 200
CONTROL 11 Procedure NonStop Kernel File-System Interface connection requests. To indicate that OSI/TS is to manage the response protocol, insert the following values: Bit in MCW Value Meaning 0 1 Connection-establishment phase. 1 0 OSI/TS is responder. 2 0 OSI/TS controls response protocol. 3-15 0 Reserved. After the MCW, your application can include up to 32 octets of data. OSI/TS sends this data in the CC-TPDU. Figure 7-7 shows the contents of the WRITEREAD buffer. Figure 7-7.
PAGE 201
Application Manages the Response Protocol NonStop Kernel File-System Interface Application Manages the Response Protocol Your application can manage the response protocol. This procedure requires the application to issue two separate calls: a WRITEREAD, followed by a WRITE or a second WRITEREAD. WRITEREAD Procedure Use a WRITEREAD call to allow the OSI/TS subsystem to receive connection requests.
PAGE 202
WRITEREAD Procedure NonStop Kernel File-System Interface As soon as OSI/TS receives a CR-TPDU with matching TSELs, it completes the WRITEREAD call but does not send a response to the remote peer. Figure 7-9 shows the contents of the buffer that OSI/TS returns to the application. Figure 7-9. WRITEREAD Buffer: Octet 0 1 0 0 1 Negotiation Parameters 0 0 Octet 1 MCW Length Indicator Octet 2 Negotiation Parameters Variable Length Optional User Data CDT 709.
PAGE 203
WRITEREAD Procedure NonStop Kernel File-System Interface Figure 7-10. Form of Negotiation Parameters • • • Octet n Octet n + 1 Octet n + 2 Through Octet n + 1 + Length Type Length Value • • • CDT 710.CDD Table 7-5.
PAGE 204
NonStop Kernel File-System Interface WRITE Procedure or WRITEREAD Procedure Residual error rate, Priority, Transit delay, Throughput Define, as a group, the quality of service to be negotiated. OSI/TS does not interpret any of these values, but passes them transparently to the application. Calling TSEL Defines the remote TSEL that issued the connection request. If this value is omitted, the transport connection cannot share a subnetwork connection.
PAGE 205
WRITE Procedure or WRITEREAD Procedure NonStop Kernel File-System Interface Bit 3 must be set to 1 and bit 4 to 0. If bit 3 and bit 4 are not set correctly, the call is completed with file-system error 140 and the connection is not established. OSI/TS responds with a DR-TPDU. This buffer is organized similarly to the WRITEREAD completion buffer that contained CR-TPDU negotiation-request parameters: • • Following the MCW are any response values for connection-negotiation parameters.
PAGE 206
Connection-Establishment Completion NonStop Kernel File-System Interface Transit delay User data However, if the parameter field contains data that cannot be interpreted as one of the above parameters, OSI/TS sends the remote peer a DR-TPDU and completes your request by issuing file-system error 140. Figure 7-12 shows the format to use if you want to accept the connection and send data, but negotiate no parameters. Figure 7-12.
PAGE 207
Transferring Data NonStop Kernel File-System Interface Table 7-6. Connection-Establishment Completion Codes Code Significance 0 Successful operation. A connection is already associated with the subdevice. Connection handshake aborted (initiator only). Issue SETPARAM for reason. Remote NSAP address undefined (initiator only), or Invalid NSAP-SNPA mapping for local or remote addresses, or Trying to establish a LAN connection with class other than class 4.
PAGE 208
Sending Data NonStop Kernel File-System Interface The first two octets of the WRITE buffer contain the 16-bit MCW. The MCW indicates whether or not the data is being sent as an expedited packet and whether there is more data to send. To request data transfer, set the MCW as follows: Bit in MCW Value Meaning 0-7 0 Reserved. 8 0 1 Normal data-transfer request. Expedited data-transfer request. 9-14 1 Reserved. 15 0 1 Data transfer is complete.
PAGE 209
Preparing to Receive Data NonStop Kernel File-System Interface Figure 7-14. WRITE Buffer: 0 Octet 0 Octet 1 Outgoing Data MCW 0 X Octet 2 Through Octet n Y Outgoing Data Legend X = 0 Normal X = 1 Expedited Y = 0 Data Completed Y = 1 More Data to Follow CDT 714.CDD If you use a WRITEREAD call to send data, OSI/TS handles your request as a WRITE call followed by a READ call.
PAGE 210
Data Transfer Completion NonStop Kernel File-System Interface The read buffer contains an MCW that indicates whether or not the data was received in an expedited packet and whether there is more data to fetch. Interpret the MCW as follows: Bit in MCW Value Meaning 0-7 0 Undefined. 8 0 1 Data was received in a normal data packet. Data was received in an ED-TPDU. 9-14 1 Undefined. 15 0 1 Data transfer is complete. More data was received than allowed in the read buffer.
PAGE 211
Releasing a Transport Connection NonStop Kernel File-System Interface Table 7-7. WRITE Call Completion Codes During Data Transfer Code Significance 0 Successful operation. count-written indicates number of octets written, including MCW. 21 An illegal write-count is specified. Connection does not exist or has been aborted. Issue SETPARAM to fetch reason. Invalid MCW specified. 140 179 Table 7-8 shows completion codes for READ and WRITEREAD calls during data transfer. Table 7-8.
PAGE 212
WRITE Procedure or WRITEREAD Procedure NonStop Kernel File-System Interface WRITE Procedure or WRITEREAD Procedure You must use a WRITE or a WRITEREAD call if you wish to transfer data during the release phase. Issue a call similar to one of the following: CALL WRITE ( filenum, buffer, write-count ); or CALL WRITEREAD ( filenum, buffer, write-count ); Place a 16-bit MCW in the first two octets of the write buffer.
PAGE 213
Error Release NonStop Kernel File-System Interface Error Release If the transport connection is released because of a subnetwork reset or disconnect indication, OSI/TS signals your application by completing all outstanding requests to the subdevice, using file-system error 140. Issue a SETPARAM 10 call to retrieve the cause of the disconnect.
PAGE 214
Response Buffer NonStop Kernel File-System Interface Figure 7-17. WRITEREAD Buffer: Status Request Octet 0 0 Octet 1 0 MCW 1 0 CDT 717.CDD Response Buffer The response buffer is the READ portion of the WRITEREAD call and has the format (in TAL) shown in Table 7-9. (This format is the same structure as ZOS4^DDL^STATUS^TCON^DEF. For more detailed descriptions of these fields, see the OSI/TS Management Programming Manual.) Table 7-9.
PAGE 215
Response Buffer NonStop Kernel File-System Interface Table 7-9.
PAGE 216
NonStop Kernel File-System Interface OSI/TS Configuration and Management Manual—424831-001 7- 42 Response Buffer
PAGE 217
A Message Control Word Summary When you use the file-system calls WRITE, READ, and WRITEREAD to control a transport connection, the first two octets of the buffers contain the MCW (message control word). The MCW contains information passed in both directions between your application and the OSI/TS subsystem. Your application uses the MCW to issue specific transport service requests to OSI/TS and to configure the OSI/TS subsystem to be a connectionestablishment responder.
PAGE 218
Message Control Word Summary Table A-2. Read Buffer Message Control Word Summary MCW Bit Number* Value Meaning 0 0 1 Not defined. Connection-establishment phase active; data was received in a CR-TPDU. 8 0 1 Data received in a normal TPDU. 15 0 1 Data is complete. More data was received than you allowed space for in the read buffer; issue another READ call to retrieve more data. * Bits not listed are not defined.
PAGE 219
B X.25 Status Code Tables This appendix contains the following three tables of status information codes: • • • X.25 disconnect reason codes (from X25AM manual) X.25 clear cause codes (from ISO 8208) X.
PAGE 220
Clear Cause Codes X.25 Status Code Tables Table B-1. Reasons for Circuit Disconnection This Word ... With This Value ... Indicates This Reason for Circuit Disconnection ... 2 The line is logically up, but the physical circuit has not been established. The line is logically up, and the physical circuit has been established. If <2> = 1 or 2, then <3> contains the applicable error code.
PAGE 221
Diagnostic Field Codes X.25 Status Code Tables Table B-2. Clear Cause Codes Clear Cause Octet 4 Bits 8 7 6 5 4 3 2 1 Notes Gateway-detected Procedure Error 1 1 0 0 0 0 0 1 3 Gateway Congestion 1 1 0 0 0 0 1 1 3 NOTE 1: Used when the Diagnostic Code Field is coded in accordance with Figure 14-B [in ISO 8208]. NOTE 2: Used when the Diagnostic Code Field is not coded in accordance with Figure 14-B [in ISO 8208]. NOTE 3: These clearing causes apply only to a DTE/DCE environment.
PAGE 222
Diagnostic Field Codes X.25 Status Code Tables Table B-3. Diagnostic Field Codes (Page 1 of 6) Bits 8 7 6 5 4 3 2 1 Decimal Value Applicable Packets (Note 1) for state p4 0 0 0 1 0 1 1 1 23 C for state p5 0 0 0 1 1 0 0 0 24 C for state p6 0 0 0 1 1 0 0 1 25 C for state p7 0 0 0 1 1 0 1 0 26 C for state d1 0 0 0 1 1 0 1 1 27 Re for state d2 0 0 0 1 1 1 0 0 28 Re for state d3 0 0 0 1 1 1 0 1 29 Re Diagnostic . . . . . . . .
PAGE 223
Diagnostic Field Codes X.25 Status Code Tables Table B-3.
PAGE 224
Diagnostic Field Codes X.25 Status Code Tables Table B-3. Diagnostic Field Codes (Page 1 of 6) Diagnostic Bits 8 7 6 5 4 3 2 1 Decimal Value Applicable Packets (Note 1) Miscellaneous 0 1 0 1 0 0 0 0 80 Rr, C, Re improper cause code from DTE 0 1 0 1 0 0 0 1 81 D, Rr, C, Re non octet aligned 0 1 0 1 0 0 1 0 82 D, Rr, C, Re inconsistent Q-bit settings 0 1 0 1 0 0 1 1 83 Re . . . . . . . . Not assigned 0 1 0 1 1 1 1 1 95 0 1 1 0 0 0 0 0 96 . . . . . . . .
PAGE 225
Diagnostic Field Codes X.25 Status Code Tables Table B-3. Diagnostic Field Codes (Page 1 of 6) Bits 8 7 6 5 4 3 2 1 Diagnostic Decimal Value Applicable Packets (Note 1) . . . . . . . .
PAGE 226
Diagnostic Field Codes X.25 Status Code Tables Table B-3. Diagnostic Field Codes (Page 1 of 6) Bits 8 7 6 5 4 3 2 1 Decimal Value Applicable Packets (Note 1) connection rejection - NSAP unreachable (permanent condition) 1 1 1 0 1 0 0 0 232 C reset - reason unspecified 1 1 1 0 1 0 0 1 233 Re reset - congestion 1 1 1 0 1 0 1 0 234 Re Connection rejection - NSAP address unknown (permanent condition) 1 1 1 0 1 0 1 1 235 C Diagnostic . . . . . . . .
PAGE 227
Diagnostic Field Codes X.25 Status Code Tables Table B-3. Diagnostic Field Codes (Page 1 of 6) Diagnostic Bits 8 7 6 5 4 3 2 1 Decimal Value Applicable Packets (Note 1) . . . . . . . . 1 1 1 1 1 1 1 1 255 NOTE 1: A given diagnostic need not apply to all packet types.
PAGE 228
X.
PAGE 229
C Programming Examples This appendix contains an example application for transferring unstructured binary files (for example, object code files). The same file-transfer application is shown in both TAL and in C. In this example, each program—the requester and the responder—use file-system calls to access the services of its local OSI/TS transport entity. The transport entities exchange data and control information (TPDUs) over an OSI network.
PAGE 230
Programming Examples TAL Example File-Transfer Program, Requester INT .osi^dev^rcv[0:11] :=" "; INT .osi^dev^send[0:11] :=" "; INT .dest^file^name[0:11] :=" "; INT .source^file^name[0:11] :=" "; INT osnum,snum,ornum,dnum,count^read; INT rec^len^send :=1024; INT rec^len^rcv := 1024; INT .buffer := %100000; !I/O buffer ?NOLIST, source $system.system.
PAGE 231
TAL Example File-Transfer Program, Requester Programming Examples CALL close(rcv^num); END; ?page ! ****************************************************** ! * ! * Main program for the TSP requester ! * ! ****************************************************** PROC m MAIN; BEGIN ! ! *** Open $RECEIVE, read in the startup message and close ! *** $RECEIVE call startup; ! ! *** Reset the MCW to the normal data transfer mode buffer[0] := 0; ! ! *** Expand the TSP requester SU name call fnameexpand(ext^dev^send,
PAGE 232
TAL Example File-Transfer Program, Responder Programming Examples ! *** Close the TSP requester SU call close (osnum); END; TAL Example File-Transfer Program, Responder Before running this program, your OSI/TS subsystem must be configured and running. Before compiling the source code, you must first replace the file and process names with names that reflect your environment, as described in the first comment box in the code.
PAGE 233
TAL Example File-Transfer Program, Responder Programming Examples INT .buffer := %100000; !I/O buffer ?NOLIST, source $system.system.
PAGE 234
Programming Examples TAL Example File-Transfer Program, Responder ! * Main program for the TSP responder ! * ! ****************************************************** PROC m MAIN; BEGIN ! ! *** Open $RECEIVE, read in the startup message and close ! *** $RECEIVE call startup; ! ! *** Expand the destination file name call fnameexpand(dsex^file^name,dest^file^name,default^subvol); ! ! *** Expand the TSP responder SU name call fnameexpand(ext^dev^rcv,osi^dev^rcv,default^subvol); ! ! *** Open the TSP responder
PAGE 235
Programming Examples C Example File-Transfer Program, Requester C Example File-Transfer Program, Requester Before running this program, your OSI/TS subsystem must be configured and running. Before compiling the source code, you must first replace the file and process names with names that reflect your environment, as described in the first comment box in the code. The source code file for this example is provided as part of the OSI/TS software. It resides (by default) in $SYSTEM.ZOSITS.EXPRGC1A.
PAGE 236
C Example File-Transfer Program, Responder Programming Examples main () { /* Reset the MCW */ buffer[0] = 0; /* Copy the default subvol name */ strcpy((char *)&default_subvol[0],&s_subvol[0]); /* Convert the TSP su name */ FNAMEEXPAND(&ext_dev_send[0],&osi_dev_send[0], &default_subvol[0]); /* Convert the source file name */ FNAMEEXPAND(&srcex_file_name[0],&source_file_name[0], &default_subvol[0]); /* Open the TSP su and send a connection request */ OPEN(&osi_dev_send[0], &osnum); CONTROL(osnum,(int)17); /
PAGE 237
C Example File-Transfer Program, Responder Programming Examples The source code file for this example is provided as part of the OSI/TS software. It resides (by default) in $SYSTEM.ZOSITS.EXPRGTC1B. /********************************************************/ /* File: EXPRGC1B */ /* */ /* C file transfer program example: Responder */ /* */ /* 1) Replace "src" with the name of the file you */ /* want to transfer.
PAGE 238
C Example File-Transfer Program, Responder Programming Examples strcpy((char *)&default_subvol[0],&s_subvol[0]); /* Convert the external TSP su device name into an internal name */ FNAMEEXPAND(&ext_dev_rcv[0],&osi_dev_rcv[0], &default_subvol[0]); /* Convert the external destination file name into an internal name */ FNAMEEXPAND(&dsex_file_name[0],&dest_file_name[0], &default_subvol[0]); /* Open the TSP su and waiting for a connection request */ OPEN(&osi_dev_rcv[0], &ornum); SETMODENOWAIT(ornum,(int)30,(i
PAGE 239
Glossary The following glossary defines terms used both in this manual and in the other Compaq OSI/AS and Compaq OSI/TS manuals. Not all terms listed here are used in this particular manual. Abstract syntax. A representation of the way in which components of information are to be specified in a communication. It defines a set of primitive elements whose range of values is fully defined—for example, integers, characters, and Boolean values—and ways of combining these elements. Abstract Syntax Notation-1.
PAGE 240
Application entity. Glossary Application entity. The part of an application process that interacts with a remote application process. In an OSI application itself, the application entity is the part that represents the communication functionality necessary for interoperation. Application entity title. the OSI network. The name, used with ACSE, that identifies an application entity to Application Layer. Layer 7 of the OSI Reference Model.
PAGE 241
Calling address. Glossary Calling address. The address from which a connect request is initiated. Calling user. The application that initiates a request to establish a connection. For OSI/AS, an application is the calling user when it calls the APS_ASSOC_CONNECTREQ_ procedure. The calling user can, at the same time, be a called user for other connections. Capability data.
PAGE 242
Data chaining. Glossary is part of the Dynamic System Configuration (DSC) facility, which is not used to configure Compaq OSI subsystem objects, but which can be used to configure the underlying X25AM and TLAM objects. CSMA/CD (carrier sense multiple access with collision detection). An IEEE 802.3 standard for the Physical Layer of the OSI Reference Model that defines CSMA/CD data transmission over baseband or broadband LAN networks. Data chaining.
PAGE 243
EMS (Event Management Service). Glossary Name Service (DNS), and token-oriented programmatic interfaces to the management processes for various Compaq subsystems. EMS (Event Management Service). A part of DSM used to provide event collection, event logging, and event distribution facilities.
PAGE 244
Header token. Glossary Header token. In an SPI message, a token that provides information pertaining to the message as a whole. Header tokens differ from other tokens in several ways: they exist in the buffer at initialization and their values are usually set by SSINIT, they can occur only once in a buffer, they are never enclosed in a list, they cannot be moved to another buffer with SSMOVE, and programs cannot position to them or retrieve their values using the NEXTCODE or NEXTTOKEN operation.
PAGE 245
LMIB (Local Management Information Base). Glossary LMIB (Local Management Information Base). Base).. See MIB (Management Information Local address. The terms local address and remote address refer to the two endpoints of a connection. A local address is the address of the end-system which is considered local with respect to the user. Loopback connection. For qualifying applications, an improvement in throughput and performance can be accomplished by using a loopback connection.
PAGE 246
Nowait mode. Glossary Nowait mode. The mode in which the called procedure initiates an I/O operation but does not wait for it to complete before returning control to the caller. To have the called procedure wait for the completion of the operation, the application calls a separate procedure (AWAITIOX for the OSI/TS programmatic interface; MFM_AWAITIOX_ for the OSI/AS interface). NSAP (network service access point).
PAGE 247
Glossary PCI (protocol control information). PCI (protocol control information). Information exchanged between peer entities to coordinate their joint operation within a specific layer. PDU (protocol data unit). Information delivered as a unit between peer entities that contains data and/or control and address information. There are five types of PDUs used by OSI/AS and OSI/TS: PDV (presentation data value) list. The form in which the Presentation Layer transmits data.
PAGE 248
Profile. Glossary data in a system-independent manner, performing appropriate conversions at each system as necessary. Profile. A type of object defining a template that contains configuration parameters for OSI/AS dynamic subdevices. When a profile is specified for a connection, the configuration parameters in the profile take precedence over any corresponding parameters specified for the service as a whole. PSAP (presentation service access point).
PAGE 249
Service primitive. Glossary these operations are implemented. A service relates to an interface between two layers, with the lower layer being the service provider and the upper layer being the service user. Service primitive. An abstract, implementation-independent interaction between a service user and a service provider. Service primitives describe the sequences of events between adjacent layers that occur through the service access point (SAP).
PAGE 250
State-machine error. Glossary State-machine error. (1) In the programmatic interface to OSI/AS, an error caused by an applications making an APS procedure call that invokes a primitive at the wrong time or under the wrong conditions. (2) In the event-management interface to OSI/AS, an internal error in the OSI/AS software that causes the TAPS process to issue an event message. Station group address.
PAGE 251
Subsystem Programmatic Interface. Glossary subsystem version number. The subsystem ID is an argument to most of the SPI procedures. Subsystem Programmatic Interface. See SPI (Subsystem Programmatic Interface).. Summary state. In DSM interfaces to Compaq data communications subsystems, a summary state isone 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.
PAGE 252
Token bus. Glossary local application. There are four session tokens; each is associated with a functional unit: The availability of each token depends on which functional units are used on the connection. (2) In DSM terms, a distinguishable unit in an SPI message. Programs place tokens in an SPI buffer using the SSPUT or SSINIT procedures and retrieve them from the buffer with the SSGET procedure. A token has two parts: an identifying code, or token code, and a token value.
PAGE 253
TSDU (transport service data unit). Glossary TSDU (transport service data unit). transfer data. A unit of data used by transport peer entities to TSEL (transport selector). A logical address in the Transport Layer through which transport services are made available. A single TSEL can service one or more connections simultaneously. TSP (transport service provider) process.
PAGE 254
Glossary X25AM (X.25 Access Method).
PAGE 255
Index A Accept parameters 7-31 Accepting connection requests 7-30, 7-32 Access mode parameter 7-11 ADD command SU object 3-3 Additional options field in SU status block 7-16 negotiated parameters 7-30 Address sharing 2-17, 5-9, 5-11 Addressing address sharing 2-17, 5-9, 5-11 authorities 2-3 called and calling 5-11, 5-12 domains 2-4, 2-6 overview for OSI/TS 5-9 X.
PAGE 256
C Index C C example program file-transfer responder C-9 Call packet addresses 2-7 Call request packet trace examples 4-24, 429, 4-31 Called address description 5-11, 5-12 parameter 5-2 Called TSEL 7-30 Calling address description 5-11, 5-12 parameter 5-2 Calling TSEL 7-30 CCITT X25AM support of 1-7 X.
PAGE 257
C Index Configuration and management tools 1-11 Configuration, effect on class 4 attributes 3-16 connection attributes 3-11, 3-14 default values 3-10 initial attributes 3-9 other attributes 3-18 process attributes 3-11 traffic attributes 3-14, 3-16 Configuring LAN examples general 3-26, 3-28 with ES-IS protocol 3-28 with IP null 3-30, 3-31 large application examples 3-31 NSP processes general 3-2 TLAM 3-6, 3-7 X25AM 3-3, 3-5 sequence of tasks 3-1 TSP processes 3-18 X.
PAGE 258
D Index successful initiation 6-6, 6-7 types of TPDUs 6-1 WRITE buffer 7-31, 7-32 WRITEREAD buffe 7-26 WRITEREAD buffer 7-22, 7-27, 7-28, 7-31 Connection-mode network service 3-2, 5-3 Connection-release phase deleting subdevices 3-5 primitives, table of 5-2 programming overview 7-37 release due to error 7-39 remote release 7-38 services provided 6-13, 6-14 types of TPDUs 6-1 using CONTROL procedure 7-37 using WRITE or WRITEREAD procedures 7-38 WRITE buffer 7-38 WRITEREAD buffer 7-38 CONNECTTIMEOUT attribu
PAGE 259
E Index standards implemented 1-2 TLAM support for 1-9 X25AM support for 1-7 Data packet, outgoing, trace examples 4-31 Data-transfer phase expedited data option 6-11 primitives, table of 5-2 programming overview 7-33 receiving data 7-35, 7-36 resynchronizing data 5-7, 5-8 sending data 7-33, 7-35 services provided 6-10, 6-13 transfer completion 7-36 DC-TPDU 5-8, 6-1, 6-13, 7-38 during connection release 7-37 Default attribute values 3-10 DELETETIME attribute 7-3 Deleting TLAM ports 3-7 X25AM subdevices 3-
PAGE 260
F Index during connection release 6-13, 614, 7-38, 7-39 during data transfer 7-33, 7-37 example PTrace screen 4-13 error 178 7-33 error 179 7-34, 7-37 error 2 5-2 error 21 7-35, 7-37 error 22 7-23, 7-26 recovery during connection-establishment 69 protocols 5-4 resynchronizing data 5-7 retention of TPDUs 5-8 subnetwork failure 5-6 release of connection 7-39 release procedure 6-13 residual rate parameter 7-30 ER-TPDU 5-5, 6-1, 6-7, 6-9, 7-38 ESISCHECKSUM attribute 3-14 ESISENABLE attribute 3-7 ESISESCONFTIM
PAGE 261
H Index file system interface 7-1 relationship to Transport Layer 7-7 subdevice name field 7-14 subdevice naming conventions 7-1 H Hardware components 1-4 Help, troubleshooting 4-36 Heterogeneous systems 1-1 HIGHPIN attribute, altering 3-9 HIGHPIN parameter, RUN command 3-20 Host-to-host confirmation 6-13 HRPF 2-11, 2-12 I IDI address component description 2-8, 2-9 encoding by Network Layer 2-12 examples 2-13, 2-16 IDP address component definition 2-8 examples 2-13, 2-16 IEEE standards implemented 1-2,
PAGE 262
L Index L L2WINDOW attribute 3-16 L3IMMEDIATERR attribute 3-17 L3WINDOW attribute 3-16 L4PROTOCOL modifier, SYSGEN 3-3 L4TIMEOUTTHLD attribute 7-6 L4WINDOW attribute effect on performance 3-15 service attribute 7-6 subdevice attribute 7-3 L4^PTP^PROTOCOL modifier, SYSGEN 3-3 LANDFC attribute 3-11 LANDFT attribute 3-11 LANIOSIZE attribute 3-6 LANLOCALSNPA attribute 7-3 LANREMOTESNPA attribute 7-3 LANs address sharing 5-9, 5-11 addressing 5-9 controllers for 1-4 example command files ES-IS protocol 3-28 gen
PAGE 263
N Index factors in using multiplexing 5-13 service attribute 7-7 subdevice attribute 7-3 Multiplexing connections 5-12, 5-13 description 2-17 factors for 5-13 parameter 7-3 passive 5-14 protocols 5-4 setting via SETPARAM 7-19 N Naming OSI/TS subdevices 7-1 TLAM ports 3-6 TSP processes 3-20 wild card option with CHECK 4-8 X25AM subdevices 3-4 Negotiation of services accept parameters 7-31 additional options 7-30 general 6-2 length field 7-28 parameters, table of 7-28 WRITEREAD buffer 7-28 Negotiation para
PAGE 264
O Index subsystem performance 3-13, 3-14, 315, 3-16 troubleshooting example, X25AM 4-25, 4-31 troubleshooting strategy, TLAM 4-32, 4-35 troubleshooting strategy, X25AM 4-22, 4-25 NSPDEVICE attribute 3-2, 7-3 Numbering DT-TPDUs 5-6, 6-12 N-DISC primitive 6-7 N-DISCONNECT primitive 7-38 N-RESET primitive 6-7 O OPEN procedure 7-8, 7-10 examples C-1, C-4 procedure calls, table of 1-11 Opening subdevices programmatically 7-10 Operating system image 3-2 Options field in SU status block 7-16 Options parameter i
PAGE 265
P Index PASSIVEMUX attribute effect on performance 3-12 service attribute 7-7 Password 7-30 PDU-size attributes 3-15 Performance approach to measuring 4-1, 4-2 capacity 3-10 class 4 attributes, effect on 3-16 connection attributes, effect on 3-11, 314 default values, effect on 3-10 improving 4-5 initial configuration, effect on 3-9 other attributes, effect on 3-17, 3-18 process attributes, effect on 3-11 sources of problems 4-2 tools 4-3 traffic attributes, effect on 3-14, 3-16 warning signs 4-4 when to m
PAGE 266
Q Index stack 1-2 Protocol standards, Transport Layer 1-1 PTP interface of X25AM 3-3 PTrace negotiation parameters and SCF attributes comparison 4-20 PTrace examples commands, NSP traces 4-23, 4-25, 429, 4-30, 4-34 commands, TSP traces 4-13, 4-14, 4-18, 4-22 L3 Pkt In screen 4-24, 4-30, 4-31 L3 Pkt Out screen 4-29, 4-30, 4-31 L3 Primitive screen 4-14 L4 SM screen 4-19, 4-20 L4 TPDU IN screen 4-19, 4-20, 4-22 L4^LCB^In screen 4-23 LAPB In screen 4-24 LSAP screen 4-35 Msg IO screen 4-13 starting screen 4-19
PAGE 267
S Index OSI/TS 7-25, 7-26 Responding to connection-establishment 57 Response primitives, table of 5-2 Response protocol application manages 6-8, 7-10 general 6-8 managing overview 7-24 OSI/TS manages 6-8, 6-9, 7-9 Resynchronizing data 5-7, 5-8 Retention of TPDUs 5-8 Retransmission counter parameter 7-3, 7-7 Retransmission on timeout 5-8, 6-7 Retransmission timer parameter 7-3, 7-7 Retrieving subdevice parameters 7-11 REXMITTIMEOUT attribute effect on performance 3-16 general 6-7 service attribute 7-7 subd
PAGE 268
S Index SETPARAM procedure call SETPARAM 13 5-13 Shared access to subdevice parameter 7-11 Simple protocol, class 0 5-3 SNDCF addressing mode parameter 7-5 configuration example 3-25 enable parameter 7-5 OSI/TS feature 1-3 relationship to IPLIFETIME attribute 318 relationship to OSI/TS 1-8 subdevice parameter 7-3 X25AM support for 1-7 SNPA addresses contents on LANs 2-2 contents on WANs 2-3 description 2-1, 5-9 Software architecture of OSI/TS 1-5, 1-7 SRC-REF parameter CC-TPDU in 6-9 CR-TPDU in 6-4 descri
PAGE 269
T Index status blocks, fetching 7-13 status blocks, variable part 7-16, 7-18 Subdevices, closing examples C-1 Subdevices, closing, examples C-4 Subdevices, opening examples C-1, C-4 Subnetwork description 1-2 failure 5-6, 5-7 types of 6-4 SYSGEN CIRCUITS attribute 3-13 general 1-11 L4^PTP^PROTOCOL modifier 3-3 MAXIOSIZE modifier 3-3, 3-6 PACKETSIZE attribute 3-15 using for OSI/TS 3-9 System image 3-2 T TAL example program file-transfer requester C-1 file-transfer responder C-4 TCONPRI attribute 7-3, 7-7
PAGE 270
T Index TRACE command as a performance monitoring tool 4-3, 4-4 example commands 4-18, 4-21, 4-29, 430 Tracing facility 1-13 Traffic, effect on performance 3-14, 3-16 Transferring data general 6-10, 6-13 programmatically 7-33 Transit delay parameter 7-30 Transmission window size parameter 7-3, 7-6 Transmit window 6-12 Transmitted security parameters 7-3, 7-7 Transport connection priority parameter 7-3 connections, identifying 7-1 connections, reassigning 5-6, 5-7 expedited data parameter 7-3, 7-6 expedite
PAGE 271
U Index TSP^LANIOSIZE PARAM modifier, TLAM 3-6 TSP^MAXCONNECTIONS parameter 310 TTR time 5-7 TTR timer 5-6 TTRTIMEOUT attribute 7-3, 7-7 TWR timer 5-7, 5-8 TWRTIMEOUT attribute 7-3, 7-7 T-CONNECT primitive called/calling addresses 5-11, 5-12 confirm 6-2 general description 7-21 indication 6-8 request 6-1, 6-2 response 6-8 trace example 4-14, 4-19 T-DATA primitive 5-3, 7-33 T-DISCONNECT primitive class 0, in 6-13 general 7-37 maximum user data in 5-3 T-EXPEDITED DATA primitive data transfer, during 7-33 ge
PAGE 272
X Index accept service parameters 7-31 application manages response 7-27 connection establishment 7-22 negotiation parameters 7-28 OSI/TS manages response 7-26 release connection 7-38 WRITEREAD procedure accepting connections 7-30, 7-32 application manages response 6-8, 7-27, 7-30 data transfer completion codes 7-37 general description 7-21 OSI/TS manages response 7-25, 7-26 procedure calls, table of 1-11 releasing connections 7-38 requesting a connection 7-23 requesting connections 7-22 sending data 7-33