OSI/AS Configuration and Management Manual Abstract This manual describes how to configure and manage the Compaq OSI/AS subsystem, which provides OSI Session Layer, Presentation Layer, and ACSE (in the Application Layer) communication services. It is intended for those who need to configure, monitor, and tune for performance, troubleshoot, and manage OSI networks. Product Version OSI/AS D43 Supported Releases This manual supports OSI/AS D43 and all future D-series releases and G06.
Document History Part Number Product Version Published 424119-001 OSI/AS 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. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
OSI/AS Configuration and Management Manual Glossary Index Figures Tables What’s New in This Manual xv Manual Information xv New and Changed Information xv About This Manual xvii Manual Audience xvii Manual Contents xviii OSI/AS and OSI/TS Supported Standards OSI/AS Manual Set Related Manuals xix xix xxii Your Comments Invited xxii Notation Conventions xxiii 1.
1. Introduction (continued) Contents 1.
2. Management Environment (continued) Contents 2.
2. Management Environment (continued) Contents 2.
3. NSAP Addressing (continued) Contents 3.
4. Installing and Configuring the Subsystem (continued) Contents 4.
5. Routine Management Tasks (continued) Contents 5.
6. Performance Considerations (continued) Contents 6.
6. Performance Considerations (continued) Contents 6. Performance Considerations (continued) Ongoing Monitoring and Analysis 6-12 What Tools to Use 6-13 What Performance Indicators to Monitor 6-13 When to Monitor Performance 6-14 Corrective Actions 6-14 7.
8. Troubleshooting Guide Contents 8.
8. Troubleshooting Guide (continued) Contents 8. Troubleshooting Guide (continued) Getting Help 8-68 Command File for Resetting Statistics Counters 8-68 Command File for Obtaining Diagnostic Information 8-69 A. Examples of Configuration Command Files OSI/AS Over an X.25 Network A-2 OSI/AS Over an X.25 Network, Using SNDCF A-5 OSI/AS Over a LAN A-7 OSI/AS Over a LAN, Using ES-IS Routing Exchange Protocol A-9 OSI/AS Over a LAN, Using IP null A-11 OSI/AS, Large Application, Over an X.
Figures (continued) Contents Figures (continued) Figure 2-3. Process States 2-17 Figure 3-1. NSAP Addressing Domains Figure 3-2. NSAP Network Addressing Domain Hierarchy 3-6 Figure 3-3. NSAP Address Components Figure 3-4. NSAP Address Example 1 3-15 Figure 3-5. NSAP Address Example 2 3-16 Figure 3-6. NSAP Address Example 3 3-17 Figure 4-1. Connection With No Loopback Figure 4-2. Loopback Connection 4-25 Figure 4-3. Step-by-Step Configuration Example Figure 4-4.
Tables (continued) Contents Tables (continued) Table 2-8. SERVICE Default Values Set by the OSI Manager Process— Layer 4 (page 1 of 2) 2-28 Table 2-9. SERVICE Default Values Set by the OSI Manager Process— Layer 5 2-29 Table 2-10. SERVICE Default Values Set by the OSI Manager Process— Layer 6 2-30 Table 2-11. SERVICE Default Values Set by the OSI Manager Process— Layer 7 2-30 Table 2-12. Selection Hierarchy of Object Attributes—Layer 3 2-35 Table 2-13.
Contents OSI/AS Configuration and Management Manual—424119-001 xiv
What’s New in This Manual Manual Information OSI/AS Configuration and Management Manual Abstract This manual describes how to configure and manage the Compaq OSI/AS subsystem, which provides OSI Session Layer, Presentation Layer, and ACSE (in the Application Layer) communication services. It is intended for those who need to configure, monitor, and tune for performance, troubleshoot, and manage OSI networks. Product Version OSI/AS D43 and OSI/AS G06.
What’s New in This Manual New and Changed Information OSI/AS Configuration and Management Manual—424119-001 xvi
About This Manual The OSI/AS Configuration and Management Manual describes how to configure and manage the Compaq OSI/AS subsystem, which provides OSI Session Layer, Presentation Layer, and ACSE (in the Application Layer) communication services. This manual is intended for those who need to configure, monitor, and tune for performance; troubleshoot; and manage OSI networks. The OSI/AS subsystem and the OSI/TS subsystem together provide core services that support the seven-layer OSI Reference Model.
Manual Contents About This Manual Manual Contents Table i lists the sections and appendixes in this manual. Table i. Manual Contents (page 1 of 2) Section or Appendix Contents Section 1, Introduction This section briefly describes the components of the OSI/AS subsystem, lists the services the subsystem provides and the OSI protocols it supports, and lists the required and optional hardware and software used with OSI/AS.
OSI/AS and OSI/TS Supported Standards About This Manual Table i. Manual Contents (page 2 of 2) Section or Appendix Contents Appendix A, Examples of Configuration Command Files This appendix contains example command files for configuring OSI/AS over an X.25 wide area network (WAN) and over a local area network (LAN). Appendix B, Examples of EMS Filters This appendix contains example Event Management Service (EMS) filters and an example command file for compiling EMS filters.
Related Manuals About This Manual • • The OSI/AS Programming Manual shows programmers how to use the OSI Session Layer, Presentation Layer, and ACSE procedural interface provided by the Compaq OSI/AS subsystem. This interface allows applications to communicate in the OSI environment. The Operator Messages Manual describes system messages and provides an explanation of the cause, a discussion of the effect on the system, and suggestions for corrective action.
Related Manuals About This Manual The following manuals contain background information on the Compaq environment: • • • • The Introduction to Networking and Data Communications for Himalaya S-Series Servers provides an overview of Compaq networking and data communications products for G-series systems. The Introduction to Distributed Systems Management (DSM) introduces the products and components collectively known as Distributed Systems Management.
Your Comments Invited About This Manual 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. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Notation for Messages About This Manual Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in 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.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The %þnotation precedes an octal number. The %Bþnotation precedes a binary number. The %Hþnotation precedes a hexadecimal number.
1 Introduction The Compaq Open Systems Interconnection/Application Services (OSI/AS) subsystem is a collection of software components that allow Compaq NonStop systems to function as open systems in standard OSI networks.
OSI/AS Architecture Introduction OSI/AS Architecture The Compaq OSI/AS subsystem includes the OSI manager process along with one or more Compaq application, presentation, and session service provider (TAPS) processes. TAPS processes provide Session Layer, Presentation Layer, and ACSE services. OSI/AS also requires other subsystems that provide lower-layer services: the Compaq OSI/TS subsystem and the X25AM, NonStop TCP/IP, or TLAM ( for D-series releases) or PAM (for G06 and above releases) subsystem.
OSI/AS Architecture Introduction Figure 1-1 illustrates how the various layers of the OSI Reference Model are supported for users of Compaq OSI/AS over both WANs and LANs. Figure 1-1. Compaq OSI Architecture: OSI/AS and Underlying Subsystems Layer Application (ACSE) Presentation Session OSI/AS Subsystem Transport OSI/TS Subsystem Network Data Link X25AM Subsystem TLAM/PAM Subsystem Controllers Controllers RS-232C, RS-449, X.21, V.35 50-ohm Baseband WAN LAN Physical CDT 011.
OSI/AS Architecture Introduction Figure 1-2 illustrates the data flow between the OSI/AS subsystem and underlying subsystems, showing the processes and controllers that provide OSI services and protocols. Figure 1-2. Data Flow Between OSI/AS and Underlying Subsystems Layer Application (ACSE) Presentation Session TAPS Transport TSP Network IP 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 012.
OSI/AS Subsystem Components Introduction OSI/AS Subsystem Components Each OSI/AS subsystem consists of an OSI manager process and three different types of subordinate processes. There can be many instances of each type within the same subsystem. The different types of protocol processes are responsible for services in the different OSI layers. Figure 1-3 illustrates the architecture of the main OSI/AS subsystem components. Figure 1-3. OSI/AS Subsystem Components TAPS TSP OSI Manager NSP MIB CDT 013.
OSI/AS Subsystem Components Introduction You can have several OSI/AS subsystems within one Compaq NonStop system. Figure 1-3 on page 1-5 illustrates a single OSI/AS subsystem. The figure shows a complete set of the components that work together to provide OSI services.
NSP Processes Introduction NSP Processes NSP processes handle the OSI Network Layer and Data Link Layer protocols. X25AM or TCP/IP NSP processes provide Network Layer services, and TLAM NSP processes (for D-series releaes) or PAM and SLSA processes together (for G06 and above releases) provide Data Link Layer services to the TSP processes within the same OSI/AS subsystem. Each line controlled by an NSP process can support multiple simultaneous transport connections.
TAPS Processes Introduction TAPS Processes TAPS processes manage Session Layer, Presentation Layer, and ACSE connections with remote peer entities. TAPS processes are Transport Layer users and providers of session, presentation, and ACSE services. That is, they use the transport connections provided by the TSP processes (via the OSI/TS subsystem) to establish Session Layer, Presentation Layer, and ACSE connections with peer entities.
MIB Introduction MIB The MIB (Management Information Base) is a key-sequenced file that contains management information for the subsystem. Two types of information are included in this database: Local Management Information Base (LMIB) information and Local Directory Information Base (LDIB) information. The OSI manager process writes configuration information (LMIB) to the MIB as you add and configure subsystem components.
Access to ACSE, Presentation Layer, and Session Layer Introduction Access to ACSE, Presentation Layer, and Session Layer Application programs can directly request and receive ACSE services through the API, via APS procedure calls. The API procedures provide application programmers with a procedural interface to the subsystems ACSE, Presentation Layer, and Session Layer services.
Implemented Standards Introduction Implemented Standards The following subsections list some of the standards implemented by the OSI/AS processes: • • • • • Subnetwork Protocols on this page Transport Layer Protocols on page 1-12 Session Layer Protocol on page 1-12 Presentation Layer Protocol on page 1-13 ACSE Protocol on page 1-13 Subnetwork Protocols Subnetwork protocols compose Layer 1 through Layer 3 of the OSI Reference Model.
Transport Layer Protocols Introduction Note. Please refer to the PAM Configuration and Management Manual. Transport Layer Protocols OSI/AS uses OSI/TS processes (TSP processes) to provide Transport Layer services. These TSP processes conform to the ISO 8072 service definitions and the ISO 8073 protocol specification. The TSP processes implement transport protocol classes 0, 1, 2, 3, and 4.
Presentation Layer Protocol Introduction Presentation Layer Protocol The OSI Presentation Layer protocol is organized into a set of functional units. Each functional unit provides a related set of Presentation Layer services. TAPS processes implement the ISO 8322 service definitions and the ISO 8323 protocol specifications, and provide the kernel functional unit. TAPS processes support both normal mode and X.410 1984 mode. They do not support the context management or context restoration functional units.
DSC Introduction DSC The Dynamic System Configuration (DSC) program allows you to change the configuration of X25AM and TLAM peripherals, controllers, and communication processes interactively, without stopping the system. The user interface to DSC is the Configuration Utility Program (COUP). You can use this tool to add X.25 and LAN subnetwork lines to OSI/AS without having to bring your NonStop system down to generate a new operating system image.
Inspect Introduction Inspect Inspect is a tool for debugging program code. It is used to check application program code when troubleshooting problems in your OSI/AS subsystem. More detailed information on Inspect is in the INSPECT Manual. ServerNet Adapters and Communication Devices Communications controllers cannot migrate to G-series systems. Special adapters and the ServerNet wide area network (SWAN) concentrator replace D-series communications controllers.
ServerNet Adapters and Communication Devices Introduction Table 1-3. Migrating From D-Series Controllers to G-Series Communications Devices (page 1 of 2) K-Series Controller Replacement: S-Series Communications Device Supported for the Following G-Series Releases Supported Software G02.00 and later G-series releases SLSA subsystem and NBT or NBX. Multilan Attachment Device E4SA 3223 SCSI ports on the system enclosures G03.
ServerNet Adapters and Communication Devices Introduction Table 1-3. Migrating From D-Series Controllers to G-Series Communications Devices (page 2 of 2) K-Series Controller Replacement: S-Series Communications Device Supported for the Following G-Series Releases Supported Software 3614 No functional equivalents for S-series systems. Not applicable A replacement for token-bus connections is not available. 3615 E4SA G02.
Software Requirements Introduction Software Requirements Table 1-4 lists the software products you need to have running on your system to take advantage of all the features documented in the OSI/AS manual set. Table 1-4. Software Requirements Product Number Product Name Description T9570 Compaq OSI/AS OSI application services T9083 Compaq OSI/TS OSI transport services T9060 X25AM X.25 access method T9317 X25AM X.
G-Series and D-Series Compatibility Introduction G-Series and D-Series Compatibility The Network Service Providers (NSPs) for OSI/TS are X25AM, TCP/IP, or TLAM (for D-series releases) or PAM (for G06 and above releases). An application running over OSI/TS can use any of these NSPs. Some Expand networks may include both D-series and G-series systems.
G-Series and D-Series Compatibility Introduction Figure 1-5 shows OSI/TS running on a G-series system communicating with an NSP running on a D-series system through Expand lines. The NSP on D-series can be X25AM, TCP/IP, or TLAM (for D-series releases of OSI/TS) or PAM (for G06 and above releases). Figure 1-5. OSI/TS on a G-Series System Communicating With an NSP on a D-Series System G-Series D-Series OSI/TS OSI/TS NSP NSP CDT 015.
Communication Between D-Series and G-Series Systems Introduction Communication Between D-Series and G-Series Systems Figure 1-6 shows a OSI stack running on a G-series system communicating with another OSI stack running on a D-series system. The NSP on G-series can be X25AM, TCP/IP, or PAM; the NSP on the D-series can be X25AM, TCP/IP, or TLAM. Figure 1-6. G-Series OSI Stack Communicating With a D-Series OSI Stack G-Series OSI/AS D-Series OSI/AS OSI/TS OSI/TS NSP NSP CDT 016.
Introduction Communication Between D-Series and G-Series Systems OSI/AS Configuration and Management Manual—424119-001 1- 22
2 Management Environment This section describes the OSI/AS management components (the OSI manager process and configuration database) and the DSM components that make up the OSI management environment.
DSM Facilities Management Environment For commands and event messages, OSI/AS supports both interactive and programmatic interfaces. This manual uses the interactive SCF and EMS interfaces for all examples.
DSM Facilities Management Environment Figure 2-2. Event Management Interface to the OSI/AS Subsystem Event Management Service (EMS) OSI Subsystem Processes OSI Manager Event Messages Collector TAPS Event Messages TSP Event Log Event Management Interface Printing Distributor Filter Event Messages NSP Terminal Processes for Other Subsystems CDT 022.
Management Environment OSI/AS Management Components OSI/AS Management Components The following subsections describe the role of the OSI manager process and the MIB in the OSI/AS management environment: • • OSI Manager Process on this page Management Information Base (MIB) on this page OSI Manager Process The OSI manager process is central to the OSI management environment and is the focal point for configuration and management requests that you send to the OSI/AS subsystem.
Management Environment DSM Management Components DSM Management Components The following paragraphs describe the role of SCF, SCP, EMS, and PTrace in the OSI/AS management environment: • • • • • SCF SPI SCP EMS Trace Facility and PTrace SCF SCF (Subsystem Control Facility) is a DSM product that provides a common, interactive management interface for a variety of Compaq data communications products, including OSI/AS.
Management Environment EMS EMS EMS (Event Management Service) provides event collection, event logging, and event distribution facilities for OSI/AS. EMS has both an interactive and a programmatic interface. All the OSI/AS subsystem processes, as well as other subsystem processes you may have running, report significant events in the form of event messages and send them to the EMS collector, which logs the messages. You can view all or selected event messages reported to EMS.
Management Environment Using SCF to Manage Your OSI/AS Subsystem Using SCF to Manage Your OSI/AS Subsystem SCF commands are your means of controlling an OSI/AS subsystem. You use the SCF command interface to configure the subsystem, to monitor and evaluate its performance, and to make alterations when necessary. For simple subsystem management functions, you can use the SCF command interface interactively.
Management Environment Using Wildcards Using Wildcards The OSI/AS SCF commands support both full wildcard substitution (for example, * specified instead of all or part of a process name) and partial substitution (for example, $OSIM.#TAPS.TAP? to specify any process name beginning with $TAP). See the OSI/AS SCF Reference Manual for details on how to use wildcards with each command. Note. Use caution when using wildcards with sensitive commands.
Managing TSP Processes Management Environment Managing TSP Processes The TSP processes available to your OSI/AS subsystem, via the OSI/TS subsystem, provide Transport Layer services, including the OSI IP and the ES-IS routing exchange protocol for LANs and SNDCF for X.25 WANs. The TSP processes available to your OSI/AS subsystem, via the OSI/TS subsystem, provide Transport Layer services, including the OSI IP and the ES-IS routing exchange protocol for LANs, SNDCF for X.
Nonsensitive Commands Management Environment STOPOPENS Disables the creation of links (access to objects) by preventing a process or subdevice from being opened by an application request. SUSPEND Changes the state of a started process to the suspended state. The process continues to run. TRACE Generates trace records for a process. Nonsensitive Commands Nonsensitive commands do not change the state or configuration of objects; they are primarily informational commands.
null Objects Management Environment Seven types of objects are common to all OSI/AS subsystems: • • • • • • • null object ENTRY object PROCESS object PROFILE object SERVICE object SU (subdevice) object SUBSYS (subsystem) object During the connection-establishment phase, the OSI manager process selects attribute values from these objects according to a predetermined set of rules. These rules are discussed in Selection Hierarchy of Object Attributes on page 2-35.
ENTRY Objects Management Environment ENTRY Objects ENTRY objects allow you to register TAPS, TSP, and NSP processes; local and remote addresses; application entity titles; and locally defined application names with the OSI manager process (that is, to enter them into the MIB). Each ENTRY object is an entry in the MIB. The OSI manager process uses the information that you supply with ENTRY objects to select processes and to set connection attributes at different protocol layers.
Management Environment Naming ENTRY Objects Naming ENTRY Objects You must give each ENTRY object that you add to your OSI/AS subsystem a name that uniquely identifies it. Later, if you want to check its attribute values, modify some of these values, or delete this ENTRY object altogether, you refer to it by using the same identifier with the appropriate command syntax. An ENTRY object name consists of three parts. The first part is the name of the OSI manager process that controls the subsystem.
Management Environment SNPA ENTRY Objects SNPA ENTRY Objects You use SNPA ENTRY objects to configure NSP processes. You add an SNPA ENTRY object to your subsystem to do the following: • • • Register a local SNPA address with the OSI manager process. Assign an NSP process to handle all connections that use this SNPA address. If the NSP process is provided by X25AM, assign a Network Layer profile (a Layer 3 subdevice configuration) that characterizes all X.25 connections that use this SNPA address.
Management Environment TSEL ENTRY Objects Registering Remote NSAP Addresses You also add NSAP ENTRY objects to your subsystem to do the following: • • Register a remote NSAP address with the OSI manager. (This is required for outgoing connections, but optional if your application is waiting for incoming connections.) Assign a remote Transport Layer profile (a Layer 4 subdevice configuration) that characterizes all transport connections that use this remote NSAP address.
Management Environment APPL ENTRY Objects APPL ENTRY Objects You use the APPL ENTRY object to register the application names and OSI addresses used by local and remote applications. The application name, or APPL ENTRY name, is the name used by an application and refers to a particular, complete OSI address, a PSAP, which is the combination of the NSAP, TSEL, SSEL, and PSEL. The OSI manager process stores this name and address information in the MIB.
PROCESS Objects Management Environment PROCESS Objects PROCESS objects identify processes within OSI/AS or within one of its supporting subsystems. By using SCF commands with PROCESS objects, you can add protocol processes to or delete them from your subsystem, you can get information on various processes, or you can change the state of certain subsystem processes. PROCESS objects allow you to control the OSI manager process and also allow you various levels of control over NSP, TSP, and TAPS processes.
SCF Commands for PROCESS Objects Management Environment SUSPENDED means that the process is running, but does not accept user requests. NSP processes cannot be in the SUSPENDED state. UNDEFINED means that the process has not been defined to the OSI manager process with the ADD command. The OSI manager process itself is never in the UNDEFINED state. If you attempt to perform an SCF operation on an process in an UNDEFINED state, SCF returns object name not found error.
Management Environment SCF Commands for PROCESS Objects ALTER Changes process attributes. You can alter process attributes only if the process is in the STOPPED state. you can alter NSP, TSP, and TAPS processes. DELETE Causes the OSI manager to delete configuration information for the process. A process must be in the STOPPED state before you can delete it. you can delete NSP, TSP, and TAPS processes. INFO Displays the attributes of a process.
Types of PROCESS Objects Management Environment Types of PROCESS Objects OSI/AS defines three different types of PROCESS objects. Each of these types has an associated type identifier that you must use in SCF commands to identify the process you want to manage. Table 2-3 shows each PROCESS object type identifier. Table 2-3.
Management Environment Naming PROCESS Objects The OSI manager name is a valid Guardian process name. Local TAPS and TSP process names can be up to six characters ($ followed by five characters). Remote TAPS and TSP process names can be up to five characters ($ followed by four characters). Local NSP process names can be up to seven characters ($ followed by six characters). Remote NSP process names can be up to six characters ($ followed by five characters).
Management Environment PROFILE Objects Note, however, that if two or more TSP processes share the same X25AM line, only the first four characters after the $ are used by the TSP process to build the SU name and must be unique. PROFILE Objects PROFILE objects allow you to define sets of values for protocol configuration attributes within the Network Layer, Transport Layer, and Session Layer of your subsystem.
Relationship of PROFILE Objects to ENTRY Objects Management Environment Relationship of PROFILE Objects to ENTRY Objects You assign PROFILE objects to specific OSI address components and to specific OSI/AS subsystem processes by means of ENTRY objects. Table 2-4 shows the relationship between the Network Layer, Transport Layer, and Session Layer PROFILE objects; the OSI/AS processes affected; and the ENTRY object types you use to make the assignments. Table 2-4.
Types of PROFILE Objects Management Environment Types of PROFILE Objects OSI/AS defines three different types of PROFILE objects (profile-type). Table 2-5 shows the identifier that you use for each type of PROFILE object. Note that Network Layer PROFILE objects determine both X.25 protocol values and some LAN values; that is, these PROFILE objects affect NSP processes that are implemented by X25AM and TLAM (with D-series releases) or PAM (with G06 and above releases). Table 2-5.
SERVICE Objects Management Environment SERVICE Objects SERVICE objects are sets of default protocol configuration attributes and thresholds, and statistics within the Network Layer, Transport Layer, Session Layer, Presentation Layer, and ACSE of your OSI/AS subsystem. There is one SERVICE object associated with each of these layers: one Network Layer SERVICE object, one Transport Layer SERVICE object, and so on. You cannot add or delete SERVICE objects.
Types of SERVICE Objects Management Environment Types of SERVICE Objects SERVICE objects define protocol attributes within the Network Layer through the Application Layer. Table 2-6 shows how you identify in SCF commands the SERVICE object for each service layer. Table 2-6.
Default Values Set by OSI Manager Process Management Environment Table 2-7. SERVICE Default Values Set by the OSI Manager Process— Layer 3 (page 1 of 2) SERVICE Attribute Default Value Set by OSI Manager Process ESISCHECKSUM OFF ESISENABLE ON ESISESCONFTIME 60.000 (60 seconds) ESISESGROUPMACADDR 09002B000004 ESISHOLDTIME 60.000 (60 seconds) ESISISGROUPMACADDR 09002B000005 ESISNOTIFYIS OFF ESISQUERYRETRY 3 retries ESISQUERYTIME 1.
Default Values Set by OSI Manager Process Management Environment Table 2-7. SERVICE Default Values Set by the OSI Manager Process— Layer 3 (page 2 of 2) SERVICE Attribute Default Value Set by OSI Manager Process X25PRICALL OFF X25PVC NA* X25REMOTENET NA* X25REVERSECHG OFF X25RPOA NA* X25THRUPUT NA* X25TRANSITDELAY NA* *The OSI manager process does not set a default value for this attribute; it defaults to the value set by the X25AM subsystem. Table 2-8.
Default Values Set by OSI Manager Process Management Environment Table 2-8. SERVICE Default Values Set by the OSI Manager Process— Layer 4 (page 2 of 2) SERVICE Attribute Default Value Set by OSI Manager Process MAXREMIT 3 MULTIPLEX OFF NETTYPE A OUTBOUNDCRCONFERRTHLD 0 OUTBOUNDCRERRTHLD 0 OUTBOUNDTPDUPROTOERRTHLD 0 PASSIVEMUX OFF RECVSECURITY Initialized with blanks REFTIMEOUT 30.000 (30 seconds) REXMITTIMEOUT 10.
Command Examples Management Environment Table 2-10. SERVICE Default Values Set by the OSI Manager Process—Layer 6 SERVICE Attribute Default Value Set by OSI Manager Process ARPPPDUSENTPROTERRORGROUPTHLD 0 CPRPPDURECVPERMANENTGROUPTHLD 0 CPRPPDURECVTRANSIENTGROUPTHLD 0 CPRPPDUSENTPERMANENTGROUPTHLD 0 Table 2-11.
Management Environment SU (Subdevice) Objects SU (Subdevice) Objects . OSI/AS SU (subdevice) objects are logical constructs between two processes through which the processes can communicate with each other (sometimes thought of as a kind of port). Subdevices created by each process (TAPS, TSP, and NSP) form a kind of logical channel that is mapped onto a physical communications line and through which applications can communicate with each other.
SCF Commands for SU Objects Management Environment SCF Commands for SU Objects You can use the following SCF commands with the SU object: ABORT Stops the subdevice unconditionally. User requests are canceled and current opens are unusable. LISTOPENS Lists the current opens on a subdevice. NAMES Lists the names of all the SU objects currently registered with the specified TAPS process. STATS Displays statistical counters for an SU object. STATUS Displays status information for an SU object.
Management Environment Sensitive Command Examples Sensitive Command Examples The following examples illustrate the sensitive commands you can use with SU objects: ABORT SU $TAPS1.#Z123456 STOP SU $X25X.#ZAD1234 Of these two commands, ABORT is the stronger—and the more dangerous, since it deletes a subdevice immediately, even when it is currently in use. Before you issue an ABORT SU command, make sure that you will not disrupt critical application communications. Note.
SCF Commands for the SUBSYS Object Management Environment SCF Commands for the SUBSYS Object You can use the following SCF commands with the SUBSYS object: ALTER Modifies one or more attributes of the subsystem. INFO Lists the attribute values for the subsystem. NAMES Lists the names and object types of all objects configured within the subsystem. STATS Displays statistics information for the subsystem. STATUS Displays the current status of the subsystem.
Management Environment Selection Hierarchy of Object Attributes In its default configuration, OSI/AS looks for TAPS and TSP object code files in the subvolume from which the OSI manager process was started. The default names for TAPS and TSP code files are TAPSOBJ and TSPOBJ, respectively. • The following example specifies a new location for the MIB file: ALTER SUBSYS $OSIM, MIB $DATA.OSICONFG.MIB3 The OSI manager process must be in the SUSPENDED state before you can issue this command.
Selection Hierarchy of Object Attributes Management Environment Table 2-13. Selection Hierarchy of Object Attributes—Layer 4 Attribute Values #L4 Server (TSP Process) 1. L4 PROFILE in remote #APPL ENTRY 1. Local #APPL ENTRY 2. L4 PROFILE in remote #TSEL ENTRY 2. Local #NSAP ENTRY 3. L4 PROFILE in remote #NSAP ENTRY 4. L4 PROFILE in local #APPL ENTRY 5. L4 PROFILE in local #TSEL ENTRY 6. L4 PROFILE in local #NSAP ENTRY 7. Local #L4 SERVICE 8.
3 NSAP Addressing This section provides background information on network service access point (NSAP) addressing in the lower layers (needed when configuring an OSI/AS subsystem). This section is intended for anyone who must construct an NSAP address or use an NSAP address in a command, or who must write an application that uses OSI/AS. If you are already familiar with how NSAP addresses are constructed and how network addressing authorities and domains work, then you do not need to read this section.
SNPA Addresses Over LANs NSAP Addressing LAN SNPA Address Consists of... FE string followed by the TLAM station address (MAC address; hardwired into the controller) Programmatically Fetched Using SCF Command... INFO SERVICE L2-service name (this is optional, however, since the TSP process automatically fetches the SNPA address) Configured Using SCF...
SNPA Addresses Over X.25 WANs NSAP Addressing 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 in “X.25 1980 Versus 1984 Addressing.”. X25AM does not provide an SNPA address parameter that the TSP process can use. Conceptually, however, the SNPA address can be described as follows: WAN (X.25) SNPA Address Consists of...
NSAP Addresses NSAP Addressing NSAP Addresses An NSAP (network service access point) address (sometimes called a network address or a global network address) is used by the Network Layer to identify the Transport Layer user of its service.
Network Addressing Domains NSAP Addressing Figure 3-1 shows an example network and some possible addressing domains within that network. This example shows the global network addressing domain, four subdomains, and a subsubdomain. Figure 3-1. NSAP Addressing Domains Global Network Addressing Domain Subdomain 1 Subdomain 2 Subsubdomain System System Subdomain 3 System System System Subdomain 4 System System System System System CDT 031.
X25 1980 Versus 1984 Addressing NSAP Addressing Figure 3-2 shows the hierarchy of the network addressing domains in Figure 3-1 on page 3-5. Figure 3-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 032.CDD A single network addressing authority can govern one or more domains.
X25 1980 Versus 1984 Addressing NSAP Addressing X25AM supports extended addresses (1984 addressing standards) for the following types of packets, described in the following subsections on this page: • • • • Outgoing Call Request Packets Incoming Call Request Packets Outgoing Call Accepted Packets Incoming Call Connected Packets Extended called addresses are not used in clear request packets and are ignored in clear indication packets.
Specifying NSAP Addresses in OSI/AS NSAP Addressing Specifying NSAP Addresses in OSI/AS The meaning of an NSAP ENTRY object differs depending upon the addressing standard used and the type of network used. The OSI/AS subsystem interprets NSAP ENTRY objects as follows: • NSAP over X.25 using 1980 addressing standards: The NSAP address only represents an internal number used for look-up. • NSAP over X.25 using 1984 addressing standards: The NSAP address is a real NSAP address.
AFI Component NSAP Addressing The parts of an NSAP address are as follows: • • IDP DSP Initial domain part (IDP) Unambiguously identifies a subdomain at the highest level. This field is always expressed as a range of 2 through 17 decimal digits. AFI: The authority and format identifier (AFI) contains information on the network addressing authority that regulates the domain specified in the IDP along with information on the format of the IDI and the DSP.
IDI Component NSAP Addressing Possible AFI values are shown in Table 3-1. Table 3-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.164 44 58 45 59 ISO ICD 46 47 Local 48 49 Character (ISO 646) National Character 50 51 39 * First significant digit of variable length IDI values.
DSP Component NSAP Addressing Possible IDI values are shown in Table 3-2. Table 3-2. IDI Values If the IDP Format (Authority) Is... The IDI Length Is... And the Meaning Is... X.121 (CCITT X.121) 14 digits maximum X.121 number ISO DCC (ISO 3166) 3 digits Data country code F.69 (CCITT F.69) 8 digits maximum Telex number E.163 (CCITT E.163) 12 digits maximum Public switched telephone network E.164 (CCITT E.
DSP Component NSAP Addressing The maximum length of the DSP is shown in Table 3-3. Table 3-3. DSP Values If the IDI Format (Authority) Is... Maximum DSP Length Is... Binary Octets Decimal* Digits X.121 (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.
Converting NSAP Addresses NSAP Addressing Converting NSAP Addresses Theoretically, an NSAP address constructed according to the rules provided by the network addressing authority must be converted before it can be included in an NPDU (network protocol data unit) for transmission over a physical link, as follows: 1. Convert it into computer-readable format—from the basic NSAP address (the concept) to a format recognized by the Network Layer protocols. 2.
Notational Format for Encoded NSAP Addresses NSAP Addressing that use the national character set, the network addressing authority must define and publish the binary encoding rules to be used by the Network Layer protocols. Notational Format for Encoded NSAP Addresses HRPF (hexadecimal reference publication format) is the designated notational format used in written and verbal communication to convey encoded NSAP addresses.
Example 2: Locally Defined and Binary Syntax DSP NSAP Addressing Figure 3-4. NSAP Address Example 1 NSAP Address /399990100000000FF0008008E0002E301 AFI IDI DSP CDT 034.CDD The AFI in this example, as in those previous, is 39. Once again, Table 2-1 (wrong) shows that an AFI value of 39 identifies the IDI format as ISO DCC and the DSP syntax type as binary.
Example 2: Locally Defined and Binary Syntax DSP NSAP Addressing Figure 3-5. NSAP Address Example 2 NSAP Address /49010203040506070808008E0002E301 AFI (IDI null) DSP CDT 035.CDD The AFI in this example is 49. Table 3-1 on page 3-10 shows that an AFI value of 49 identifies the IDI format as locally defined and the DSP syntax type as binary. Table 3-2 on page 3-11 shows that a locally defined format has a null IDI length. The DSP is the rest of the address.
Example 3: Locally Defined and ISO 646 DSP NSAP Addressing Example 3: Locally Defined and ISO 646 DSP Figure 3-6 shows the third example NSAP address and its components. Figure 3-6. NSAP Address Example 3 NSAP Address /5021222324252627282930313233343536373839 AFI (IDI null) DSP CDT 036.CDD The AFI in this example is 50. Table 3-1 on page 3-10 shows that an AFI value of 50 identifies the IDI format as locally defined and the DSP syntax type as ISO 646 character.
Suggestions for Network Addressing Administrators NSAP Addressing Suggestions for Network Addressing Administrators A network addressing administrator is the person who implements the rules specified by the network addressing authority. This subsection provides some practical suggestions for OSI network addressing administrators.
4 Installing and Configuring the Subsystem This section describes how to install the software components of an OSI/AS subsystem and how to configure attributes for the OSI protocol layers that the subsystem implements. The section also includes information on the tools and commands to use, the interrelationships to consider, and the general procedures you need to follow to get all the components of your OSI/AS subsystem up and running.
Installing and Configuring the Subsystem Sequence of Tasks 2. Configure OSI protocol attributes: a. b. c. d. e. Configure Layer 3 attributes. Configure Layer 4 attributes. Configure Layer 5 attributes. Configure Layer 6 attributes. Configure Layer 7 ACSE attributes. For these tasks, you need to know what values to set for protocol attributes within different OSI layers and the effect of those attributes on performance. You need to know how to configure Transport Layer protocols.
Installing and Configuring the Subsystem Other Useful Manuals Other Useful Manuals In addition to Section 2, Management Environment (which contains information to help you install and configure your OSI/AS subsystem), other Compaq manuals can be useful to you during various stages of installation.
Installing and Configuring the Subsystem • • Configuring and Starting Subsystem Processes The system generation (SYSGEN) and Install programs help you configure the operating system image to include the controllers and lines used by your OSI/AS subsystems. The Dynamic System Configuration (DSC) program enables you to change the configuration of certain peripherals, controllers, and communications processes without stopping your system operation.
Installing and Configuring the Subsystem • • X25AM Considerations X25AM provides wide-area, connection-mode subnetwork services over standard X.25 networks. TLAM (for D-series release) or PAM and SLSA (for G06 and above releases) provides local-area, connectionless-mode subnetwork services over standard 802.3 and 802.4 networks. Installation of either of these access methods requires changes to your current operating system image.
Installing and Configuring the Subsystem X25AM Considerations circuit first must be established. If you are having problems establishing the Network Layer connection, check your NSAP ENTRY addresses and your profile or service requirements. See Section 8, Troubleshooting Guide, for a more detailed discussion on problem solving.
Installing and Configuring the Subsystem TLAM Considerations Deleting X25AM Subdevices During the connection-release phase, the TSP process determines whether to retain the network connection used by the transport connection or to discard it, based on the following criteria: • • Value of the MULTIPLEX attribute Network connection ownership If an X25AM subdevice is not reused by either local or remote transport entities, actual deletion of an X25AM subdevice occurs after the timeout of the X25DISCONNECT
Installing and Configuring the Subsystem TLAM Considerations Naming TLAM Subdevices No special service or profile setting is required for TLAM, but the TLAM process must be in the STARTED state. TSP adds and deletes TLAM ports dynamically in response to TAPS requests for services.
Installing and Configuring the Subsystem PAM Considerations Maximum TPDU Size 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.
Installing and Configuring the Subsystem Creating the MIB Database To avoid this problem, always do the following: • • Abort all transport subdevices before stopping TSP processes. This should be part of your normal shutdown procedure. Assign the same PAM to the same TSP process. Deleting PAM Ports PAM ports can be deleted only by aborting all the TSP subdevices; otherwise, PAM ports are retained for the lifetime of the TSP process. Note.
Installing and Configuring the Subsystem Installing the OSI Manager Process The OSI/AS software includes an input file called DBFUP that creates a MIB file with the correct attributes. Use the VOLUME command to move to the volume in which you want the MIB file located, then issue the following FUP command: FUP / in $volume.subvolume.DBFUP / $volume.subvolume is the volume and subvolume in which your OSI/AS software is installed.
Installing and Configuring the Subsystem Adding NSP, TSP, and TAPS Processes 2. Specify Location of MIB, If Necessary If the MIB is not in the same subvolume from which OSIMGR was executed, then you must alter the SUBSYS object to direct OSIMGR to the correct subvolume. Issue an SCF command like the following: ALTER SUBSYS $OSIM, MIB $SYSTEM.OSI.ZOSIDB 3. Start the OSI Manager Process Start the OSI manager process by using the SCF START PROCESS command.
Installing and Configuring the Subsystem Adding NSP, TSP, and TAPS Processes Notice that you use indirect-process-name to perform this task. • The first attribute-spec names the process, using process-name (the direct process name) NAME $NETA NAME $LANB NAME \B.$L4B NAME $TSP2 NAME $L5A NAME $TAPS2 Notice that the name of the NSP process must correspond to the device name (an I/O name) under which the NSP process was installed.
Installing and Configuring the Subsystem • Starting TSP and TAPS Processes With TSP and TAPS processes, you can specify a code file that contains the object code from which these processes are started. For example: ADD PROCESS $OSIM.#TAPS.TAPS1, NAME $TAPS1 & , CODEFILE $DATA.OSICODE.TAPS If you do not specify a CODEFILE parameter, the OSI manager looks for object code in the default locations. Default locations for TSP and TAPS process object code, respectively, are: $volume.subvolume.TSPOBJ $volume.
Configuring OSI Protocol Attributes Installing and Configuring the Subsystem Considerations • • When the OSI manager process starts a TSP process, it uses default values set in OSI/TS (for example, the buffer pool size and the swap disk). If you want to change these values, see the PARAM command parameters in the OSI/TS Configuration and Management Manual. Notice that there is no corresponding SCF command to start the NSP processes. NSP PROCESS objects do not accept the SCF START PROCESS command.
Installing and Configuring the Subsystem • Configuring Layer 3 Attributes Use the Layer 3 PROFILE object to set X25AM subdevice attributes for particular SNPA addresses or to set TLAM or PAM subdevice attributes for IP null subset or ES-IS routing exchange protocol, for example. See Section 2, Management Environment, for more information on the use of the SERVICE and PROFILE objects.
Installing and Configuring the Subsystem • Configuring Layer 4 Attributes After adding X.25 PROFILE objects, you associate them with particular SNPA addresses using SNPA ENTRY objects. See Adding SNPA ENTRY Objects on page 4-26. Configuring Layer 4 Attributes Configure Layer 4 service characteristics for TSP processes by using either the Layer 4 SERVICE object or the Layer 4 PROFILE object. (To configure these objects, you should understand the meaning of Transport Layer protocol values.
Installing and Configuring the Subsystem Configuring Layer 5 Attributes Class 4 is required for Transport Layer subdevices when your OSI/AS subsystem runs over a LAN; it automatically implements the transport class 4 protocol over a type C subnetwork with multiplexing allowed. The second attribute-spec sets the TSP retransmission timer to 20 seconds: REXMITTIMEOUT 20 This means that TSP waits 20 seconds for an AK-TPDU before retransmitting an unacknowledged TPDU.
Installing and Configuring the Subsystem Configuring Layer 6 Attributes This means that the session service provider waits 60 seconds for a T-DISCONNECT indication, after issuing an ABORT request or a RELEASE response, before sending a T-DISCONNECT request of its own. Example 2: ADD PROFILE The following command adds a Session Layer PROFILE object: ADD PROFILE $OSIM.#L5.
Installing and Configuring the Subsystem Configuring Layer 7 ACSE Attributes Consideration Notice that you alter the SERVICE object; there is no PROFILE object to add. Configuring Layer 7 ACSE Attributes You configure Layer 7 ACSE service characteristics by using the ACSE SERVICE object. To configure this object, you should understand the meaning of ACSE protocol values. Use the ACSE SERVICE object to set default application service characteristics.
Configuring Connections Installing and Configuring the Subsystem Table 4-2. Relationships Defined in ENTRY Objects This ENTRY Object... Specifies This Address Components... Can Specify This PROCESS Object... And Can Specify This PROFILE Object...
Servers and Profiles in APPL ENTRY Objects Installing and Configuring the Subsystem Other connection options that can be configured at this time are loopback and static subdevices. These configuration strategies and options are discussed below, followed by detailed descriptions of how to configure the OSI addresses, PROCESS objects, and PROFILE objects.
Installing and Configuring the Subsystem Servers and Profiles in Separate ENTRY Objects Servers and Profiles in Separate ENTRY Objects Another common method of configuring an OSI/AS subsystem is to put the serverprofile information for each layer in the ENTRY object for that layer. If you want to configure only one server and one profile for each layer, configure the ENTRY objects as shown in Table 4-4. Table 4-4. Configuring Servers and Profiles in Separate ENTRY Objects Specifies (for Each Local Entry).
Configuring Loopback Connections Installing and Configuring the Subsystem Figure 4-1. Connection With No Loopback Connect Request on System A Attach Request on System B Application Application TAPS TAPS TSP TSP NSP NSP LAN or X.25 CDT 041.
Configuring Loopback Connections Installing and Configuring the Subsystem Figure 4-2. Loopback Connection Connect Request on System A Attach Request on System B Application Application Expand TAPS TAPS TSP TSP NSP NSP LAN or X.25 CDT 042.CDD Notice in Figure 4-2 that the called end (the end that issues an attach request) still creates TAPS, TSP and NSP subdevices, but the calling end (the end that issues a connect request) creates only a TAPS subdevice.
Installing and Configuring the Subsystem Configuring Static Subdevices After a loopback connection is made, what happens to the connections between the lower layers on the called end depends upon how the subdevices are configured, as follows: • • If the system is configured for static subdevices, the connections between the TAPS and TSP processes, between the TSP and NSP processes, and between the NSP processes and the Physical Layer are maintained.
Installing and Configuring the Subsystem Adding SNPA ENTRY Objects The command and object-spec register the SNPA address 02 (not a real address, but an index) with the OSI manager process $OSIM: ADD ENTRY $OSIM.#SNPA.02 The first attribute-spec identifies the NSP process $OSIM.#NSP.NSP1 as the server process for the SNPA address registered in the first part: L3SERVER $OSIM.#NSP.NSP1 This means that this NSP process handles all connections that use SNPA address 02.
Adding NSAP ENTRY Objects Installing and Configuring the Subsystem • • If you do not specify a profile for an SNPA address, all X25AM subdevices that use that address are configured with default values, which are defined by the Layer 3 SERVICE object. For D-series TLAM subsystems, SNPAs are managed by an OSI network authority. You obtain a LAN SNPA address by concatenating the LSAP address FE with the media access control (MAC) station address.
Installing and Configuring the Subsystem Adding NSAP ENTRY Objects The first attribute-spec associates SNPA address FE08008E000023 with the local NSAP address that you registered in the first part: SNPA FE08008E000023 The OSI manager process enters into the MIB the association between these two addresses. The second attribute-spec assigns the TSP process $OSIM.#TSP.TSP1 as the server process for the NSAP address identified in the first part: L4SERVER $OSIM.#TSP.
Installing and Configuring the Subsystem Adding NSAP ENTRY Objects Notice that NETADDR-MODE is not specified. If you do not specify the addressing mode for an NSAP address, all transport subdevices that use that NSAP address are configured with the default value, which is NORMAL. Example 3: 1980 X.25 The following command registers an NSAP address with the OSI manager process, assigns it to an SNPA address, assigns it to a TSP process, and specifies addressing for a network that implements the 1980 X.
Installing and Configuring the Subsystem Adding NSAP ENTRY Objects The command and object-spec register the remote NSAP address 9A1112 with the OSI manager process $OSIM: ADD ENTRY $OSIM.#NSAP.
Installing and Configuring the Subsystem Adding TSEL ENTRY Objects connections to the address are configured with protocol values associated with the local NSAP address. • • Register remote SNPA addresses at the same time that you register remote NSAP addresses. You do not have to add remote SNPA addresses separately, as you do in the case of local NSAP and SNPA addresses. If you are using an X.25 network that implements the 1980 X.
Installing and Configuring the Subsystem Adding APPL ENTRY Objects Considerations • • • Make sure that you have added any L5SERVER process that you refer to in these commands. For example, the commands in the last example refer to TAPS process $OSIM.#TAPS.OSI5A. You must register this process with the OSI manager, using the SCF ADD PROCESS command. Also make sure that you have added any L5PROFILE objects that you refer to in these commands.
Installing and Configuring the Subsystem Adding APPL ENTRY Objects matter, administered within your NonStop system environment and not by any external OSI network administration authority. The first attribute-spec assigns the NSAP address 9A0001 to both local applications: NSAP 9A0001 NSAP 9A0001 Although both applications in this example use the same NSAP address, this need not be the case. You can assign different NSAP addresses to different applications.
Installing and Configuring the Subsystem Adding APPL ENTRY Objects The last two attribute-specs assign application-specific information that is passed by ACSE, as is, to the peer application: APTITLE (1 3 9999 1 7), AEQUALIFIER 0329 The OSI/AS subsystem does not use this information. Registering Remote Applications APPL ENTRY objects for remote applications assign application names to OSI addresses served by remote NSAPs.
Step-by-Step Configuration Example Installing and Configuring the Subsystem Step-by-Step Configuration Example Figure 4-3 gives a step-by-step example of configuring an application over an X.25 network. Figure 4-3. Step-by-Step Configuration Example PROCESS ENTRY 1 2 ADD ENTRY $OSIM.#APPL.LOCAL, & PSEL 666601, & SSEL 555501, & TSEL 444401, & NSAP 30104085551212 In your application, define the application name: LOCAL Application services are selected and controlled by your application.
Installing and Configuring the Subsystem Step-by-Step Configuration Example 1. Your application must first define LOCAL as the name used to identify the application name (or the APPL ENTRY object) and define OSIM as the name of the OSI manager process. 2. Add the APPL ENTRY object, $OSIM.#APPL.LOCAL. Identify the PSEL, SSEL, TSEL, and NSAP addresses to go with that application name.
Installing and Configuring the Subsystem Step-by-Step Configuration Example 8. Add the Layer 4 PROFILE object, $OSIM.$L4.TPF2, if you specified it in step 7. An example set of attributes for the Layer 4 profile might be CLASS 2, MULTIPLEX ON, NETTYPE B. This step completes the configuration of the Transport Layer. 9. At the Network Layer, add the NSP process $OSIM.#NSP.NSP1.
Installing and Configuring the Subsystem Configuring Large X.25 Applications Configuring Large X.25 Applications This subsection describes some options for configuring OSI/AS, OSI/TS, and X25AM to support large applications. To control X25AM lines, there are two options: • • One TSP process supports multiple X25AM lines; one or more TAPS processes may use that TSP process. A separate TSP process supports each X25AM line; one or more TAPS processes may use each TSP process.
Installing and Configuring the Subsystem Single TSP Process Supporting Multiple X25AM Lines Single TSP Process Supporting Multiple X25AM Lines In this configuration, multiple X25AM lines are controlled by a single TSP process; one or more TAPS processes use the single TSP process. Figure 4-5 illustrates this type of configuration. Figure 4-5.
Installing and Configuring the Subsystem Single TSP Process Supporting Multiple X25AM Lines The following subsections contain a discussion of the advantages and limitations of this type of configuration and an example command file. Advantages The most obvious advantage is that this is a simple configuration. The operation and management of one TSP process is straightforward.
Installing and Configuring the Subsystem One TSP Process Supporting Each X25AM Line One TSP Process Supporting Each X25AM Line In this configuration, each X25AM line is controlled by a separate TSP process; one or more TAPS processes use each TSP process. Figure 4-6 illustrates this type of configuration. Figure 4-6.
Installing and Configuring the Subsystem Verifying Your Configuration Limitations Due to the greater number of processes, this kind of configuration is more complex to manage. In addition, for users of transport class 1 or class 3, the Transport Layer recovery mechanism can possibly fail when the X.25 network is not very reliable and generates many network disconnections.
Installing and Configuring the Subsystem Checking the Contents of the MIB Not all errors displayed by the CHECK ENTRY command point to problems in your configuration. For example, Layer 3 and Layer 4 servers are not required in local APPL ENTRYs for loopback configurations. However, if you have specified the PROFILES and SERVERS attributes using a wild card, the CHECK ENTRY command displays errors for those missing server specifications. See Loopback Connections on page 4-46.
Installing and Configuring the Subsystem Checking Connection Attributes Examples The following examples show various uses of the CHECK ENTRY command: • To display a summary validation of all APPL ENTRY objects, showing only profile information, use the CHECK ENTRY command with the PROFILES attribute, as follows: ALLOW ERRORS CHECK ENTRY $OSIM.#APPL.
Installing and Configuring the Subsystem Checking Connection Attributes Loopback Connections To fully verify a loopback configuration, you need to do the following: • Use the CHECK ENTRY command with the PROFILES attribute (and, optionally, the SERVERS and DETAIL attributes), specifying the called APPL ENTRY name (which acts as the remote in this case).
5 Routine Management Tasks As with any other complex subsystem that consists of several interrelated hardware and software components, Compaq OSI/AS needs to be managed so that it always runs efficiently and satisfies the needs of its users (in this case, application programs). This section discusses a set of management tasks that you perform using SCF and EMS.
Routine Management Tasks Displaying Current Event Messages Displaying Current Event Messages Assuming that EMS is installed correctly and is running successfully, and assuming that the log files are secured so that you can access them, it is easy to run a printing distributor. The simplest case is to run a printing distributor to your terminal by entering a TACL command like the following: EMSDIST /NAME $DIST1/ TYPE PRINTING, COLLECTOR $0, & TEXTOUT $TERM1, FILTER $SYSTEM.MYFLTR.
Routine Management Tasks Creating Simple Event Filters Creating Simple Event Filters You write filters to select the event messages you want to display or print. Filtering strategies involve organizing the messages that are collected into logical groupings to which you can refer. For example, you might want to select all the messages sent by OSI/AS, OSI/TS, TLAM on D-series releases (or PAM on G06 and above releases), and X25AM or only the OSI/AS event messages.
Routine Management Tasks Modifying a Configuration Command File Nevertheless, these two configuration files are independent of one another and may not always be consistent with each other. Inconsistencies between these two files can occur in two ways: 1. You can edit a command file at any time. You can remove SCF commands, add new ones, or make changes to command parameters. However, unless you invoke a newly edited command file, your changes have no effect on the current MIB. 2.
Routine Management Tasks Retrieving Configuration Information The following sequence of SCF commands causes the OSI manager to invoke the configuration contained in MIB1: SUSPEND PROCESS $OSIM ALTER SUBSYS $OSIM, MIB $SYSTEM.CONFIG.MIB1 ACTIVATE PROCESS $OSIM The following sequence of SCF commands causes the OSI manager to invoke the configuration contained in MIB2: SUSPEND PROCESS $OSIM ALTER SUBSYS $OSIM, MIB $SYSTEM.CONFIG.
Routine Management Tasks What Objects Are Defined Within Each Type? Configuration: TAPS Process TSP Process NSP Process APPL Entry TSEL Entry NSAP Entry SNPA Entry L3 Profile L4 Profile L5 Profile Current 24 20 12 100 50 40 24 12 4 3 MaximumEver 50 50 12 150 75 40 25 15 5 3 What Objects Are Defined Within Each Type? Use the SCF NAMES command to find out the names of the objects defined within an OSI/AS subsystem.
Routine Management Tasks What Objects Are Defined Within Each Type? OSIAS Names \MARS.$OSIM SUBSYS $OSIM PROCESS $OSIM $OSIM.#TSP.L4A SERVICE $OSIM.#L3 $OSIM.#NSP.L3A $OSIM.#TAPS.L5A $OSIM.#L4 PROFILE $OSIM.#L3.PROF3 ENTRY $OSIM.#APPL.LOCAL1 $OSIM.#NSAP.0004 $OSIM.#L5 $OSIM.#NSP.L3B $OSIM.#TAPS.L5B $OSIM.#L6 $OSIM.#L4.PROF4 $OSIM.#ACSE $OSIM.#L5.PROF5 $OSIM.#APPL.REMOTE1 $OSIM.#NSAP.0003 $OSIM.#SNPA.0005 $OSIM.#TSEL.
Routine Management Tasks What Objects Are Defined Within Each Type? The NAMES SU command does not display subdevice names associated with NSP processes.
Routine Management Tasks What Are the Guardian Attributes of Processes? NAMES ENTRY simply limits the amount of information displayed. The second command displays only the names of the NSAP ENTRY objects: NAMES ENTRY $OSIM.*.* NAMES ENTRY $OSIM.#NSAP.* What Are the Guardian Attributes of Processes? Use the SCF INFO command to display Guardian attributes of OSI/AS processes.
Routine Management Tasks How Are the SERVICE Objects Currently Defined? How Are the SERVICE Objects Currently Defined? You can use the INFO SERVICE command to display the current configuration for each OSI/AS SERVICE object. The following examples display configuration attributes for Layer 3, Layer 4, Layer 5, Layer 6, and ACSE SERVICE objects: INFO INFO INFO INFO INFO INFO INFO SERVICE SERVICE SERVICE SERVICE SERVICE SERVICE SERVICE $OSIM.#L3 $OSIM.#L3, DETAIL $OSIM.#L4 $OSIM.#L4, DETAIL $OSIM.
Routine Management Tasks What Versions Are the Processes? and TSP processes to reside. This command also displays where the OSI manager process expects the MIB file to be located. The following example illustrates this command: INFO SUBSYS $OSIM, DETAIL This command produces a display like the following. Notice that you must use the DETAIL option to display code file location information: OSIAS Detailed Info SUBSYS \MARS.$OSIM *MaxNSP.......... 128 *MaxTSP.......... 128 *MaxTAPS......... 128 *MIB........
Routine Management Tasks Adding and Deleting Processes Adding and Deleting Processes You can add more processes (for example, to increase the performance of an OSI/AS subsystem), or you can delete processes that are no longer needed.
Routine Management Tasks Adding and Deleting Processes If you delete an NSP process, be sure to delete or alter any SNPA ENTRY objects that refer to it. Adding and Deleting TSP Processes You can add or delete TSP processes whenever the OSI manager process is in the STARTED state. If you add a TSP process and do not specify the CODEFILE attribute, the subsystem looks for the TSP object code in the same subvolume in which the OSI manager process object code is located (as shown by the INFO SUBSYS screen).
Routine Management Tasks Altering Process Attributes Since the ADD command in this example does not include the CPU or BACKUPCPU attributes, the values assigned are the same as the values specified for the OSI manager process. Note that when you add a TAPS process, it can be used by the subsystem only after you have defined it as the server process for a TSEL identifier. You make this assignment by adding a new TSEL ENTRY object, or by altering an existing one, as described later in this section.
Routine Management Tasks Altering Process Attributes to perform similar functions. You can control NSP LINE objects using SCF. They have the same names as the NSP processes with which they are associated. Thus, to abort an X25AM LINE object, you issue a command like the following: ABORT LINE $X25A X25AM is the name defined for the process in the SYSGEN PERIPHERALS paragraph.
Routine Management Tasks Managing Protocol Services Some of the important attributes of TSP and TAPS processes that you can change using the SCF ALTER PROCESS command are the following: • • • • • • • The Guardian process name The network node in which the process runs The primary and backup CPUs in which the process runs The priority at which the process runs The code file from which the process is run The location of the process swap file The maximum number of simultaneous connections that the process
Routine Management Tasks Altering SERVICE Objects Altering SERVICE Objects SERVICE objects set default protocol values for the network, transport, session, and presentation layers and ACSE of an OSI/AS subsystem. Use the SCF ALTER command to alter the attributes of SERVICE objects—the OSI manager process must be started. To alter the Layer 3 SERVICE object, you could use a command like the following: ALTER SERVICE $OSIM.
Routine Management Tasks Adding PROFILE Objects Assigning Layer 3 Profiles You assign Layer 3 PROFILE objects to SNPA addresses by altering or adding SNPA ENTRY objects. (If your configuration allows APPL ENTRY objects, you can specify L3PROFILES in APPL ENTRY objects instead. See Configuring Connections on page 4-20.) In the case where you add an SNPA ENTRY object, you also need to assign the SNPA address to an NSAP ENTRY object.
Routine Management Tasks Adding PROFILE Objects The first command configures the Layer 4 PROFILE object TPFILE1 with transport class 3 protocol and with multiplexing. The second command associates this PROFILE object with the NSAP address 9B0001. At the same time, this command assigns the TSP process $OSIM.#TSP.X25A to handle connections through this NSAP. The effect is that subdevices that use NSAP 9B0001 implement transport class 3 protocol with multiplexing.
Routine Management Tasks Altering PROFILE Objects Altering PROFILE Objects Use the SCF ALTER command to alter PROFILE objects. Current connections are not affected, but the next connection that uses the profile is configured with the new attributes. The following command modifies a Layer 3 PROFILE object: ALTER PROFILE $OSIM.#L3.PROF3, X25DESTADDR "654321" The effect of this command is that connections using SNPA addresses to which the Layer 3 profile PROF3 is assigned send outgoing calls to the X.
Routine Management Tasks Adding ENTRY Objects Adding ENTRY Objects You can add ENTRY objects at any time to an OSI/AS subsystem. The following paragraphs discuss the effects of adding each type of ENTRY object and some of the important dependencies. Adding SNPA ENTRY Objects You add SNPA ENTRY objects to register new SNPA addresses to an OSI/AS subsystem or to add new configurations for X25AM or TLAM on D-series releases (or PAM on G06 and above releases) subdevices.
Routine Management Tasks Adding ENTRY Objects Note that before SNPA ENTRY objects can be used by the subsystem, you need to assign them to NSAP addresses. You make this assignment by adding or altering NSAP ENTRY objects, as described in the following subsection. Adding NSAP ENTRY Objects You add NSAP ENTRY objects to add local NSAP addresses to an OSI/AS subsystem or to register additional remote NSAP addresses with the OSI manager process.
Routine Management Tasks Adding ENTRY Objects Adding TSEL ENTRY Objects You add TSEL ENTRY objects to register new TSEL identifiers with your subsystem. The following two commands add two new TSEL identifiers and assign them to the same TAPS process. Since a Layer 5 PROFILE object is not assigned, all Session Layer subdevices that use either of these TSEL addresses are configured with the default parameters defined by the Layer 5 SERVICE object: ADD ENTRY $OSIM.#TSEL.0010, L5SERVER $OSIM.#TAPS.
Routine Management Tasks Altering ENTRY Objects $OSIM.#TSP.L4A and NSP process $OSIM.#NSP.L3A to provide Layer 3 and Layer 4 protocol services to users of this APPL ENTRY. It is assumed that this example uses either a LAN or an X.25 network that implements the 1984 X.25 standard, so that the default NETADDR-MODE setting (NORMAL) applies. • The command to add a TSEL ENTRY object assigns a TAPS server process to the TSEL. For example: ADD ENTRY $OSIM.#TSEL.0011, L5SERVER $OSIM.#TAPS.
Routine Management Tasks Deleting ENTRY Objects The following command changes the TSEL associated with an APPL ENTRY object: ALTER ENTRY $OSIM.#APPL.LOCAL1, TSEL 0013 In this case, applications that use APPL.LOCAL1 are always associated with TSEL 0013. Deleting ENTRY Objects You can delete ENTRY objects from an OSI/AS subsystem anytime the OSI manager process is started. Current connections are not affected. • The following command deletes an SNPA ENTRY object: DELETE ENTRY $OSIM.#SNPA.
Routine Management Tasks Deleting ENTRY Objects OSI/AS Configuration and Management Manual—424119-001 5- 26
6 Performance Considerations This section describes factors that must be taken into account when installing, configuring, and tuning your OSI/AS subsystem for optimal performance. This information is intended to help you monitor performance levels and make decisions about how to configure the subsystem components to best serve your specific subsystem performance requirements.
Performance Considerations Factors That Affect Performance Factors That Affect Performance There are many factors in an OSI/AS subsystem that affect performance. They include configuration attributes, hardware, software, NonStop Kernel operating system version, applications design, traffic mix and volume of messages, line speeds, and OSI layers used. You must consider not only these variables, but how these variables affect the interrelationships among the components of the subsystem.
Performance Considerations Default Attribute Values 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. In some situations, changing an attribute may not substantially affect performance unless the congestion of the overcommitted resource or resources is reduced.
Performance Considerations Process Attributes Process Attributes The processes in your OSI/AS subsystem include • • • • • OSI manager process TAPS processes (provided by OSI/AS) TSP processes (provided by OSI/TS) NSP processes (provided by X25AM or TLAM on D-series releases and PAM on G06 and above releases) Application processes For each process you add to your subsystem, you should consider the following OSI/AS PROCESS and SUBSYSTEM attributes, as described in the following subsections: • • • • MAX
Performance Considerations MAXTAPS, MAXTSP, and MAXNSP Attributes MAXTAPS, MAXTSP, and MAXNSP Attributes The MAXTAPS, MAXTSP, and MAXNSP attributes specify the maximum number of TAPS, TSP, and NSP processes that can be started in your OSI/AS subsystem. To provide satisfactory throughput, you should define the appropriate number of processes of each type, and then try to locate the processes in different CPUs.
Performance Considerations MULTIPLEX Attribute MULTIPLEX Attribute The MULTIPLEX attribute allows multiple Transport Layer connections to use one Network Layer connection. Multiplexing transport connections on a single line makes more effective use of your network connections and reduces the overhead involved in setting up a new connection. You should, however, look carefully at the amount of traffic on the network connections.
Performance Considerations CIRCUITS and X25PORT Attributes CIRCUITS and X25PORT Attributes The CIRCUITS attribute specifies the total number of circuits allowed on an X25AM line. It is a SYSGEN attribute. When setting this value, you should consider the frequency of connections, the amount of traffic involved on the X25AM line, and the amount of multiplexing of transport connections that may be taking place. If this value is set too high, the X25AM lines could get overloaded.
Performance Considerations • • Checksum Attributes Window-Size Attributes on page 6-9 ° L4WINDOW (Layer 4) ° L3WINDOW (Layer 3, X25AM) ° L2WINDOW (X25AM SYSGEN) Protocol-Overhead Attributes on page 6-9 ° EXTENDEDFORMAT (Layer 4) ° RECVSECURITY (Layer 4) ° SENDSECURITY (Layer 4) Checksum Attributes OSI/TS provides a checksum capability in the transport class 4 protocol (CHECKSUM), the ES-IS routing exchange protocol (ESISCHECKSUM), and the IP (IPCHECKSUM).
Performance Considerations Window-Size Attributes two ends of a connection. In addition, the protocol only sends as much data as it can fit in a TPDU; it does not pad the TPDU with filler bytes. Window-Size Attributes You can specify window size for the Transport Layer (using OSI/TS), and the Network Layer and Data Link Layer (using X25AM).
Performance Considerations Transport Class 4 Attributes The RECVSECURITY and SENDSECURITY attributes specify that security checking is to be performed on incoming CR-TPDUs. The security field adds up to 16 characters per CR-TPDU. These additional bytes increase both CPU overhead (calculating the field and processing the additional characters) and line overhead. However, this increase in overhead is not likely to be significant unless there is a consistently excessive number of connections being initiated.
Performance Considerations Event Thresholds value. If you set MAXREMIT too high, excessive unnecessary traffic may be generated on the line if the line is bad. Event Thresholds The OSI/AS subsystem provides many threshold values that can be used for EMS event generation. This includes thresholds for layers 3, 4, 5, and 6, plus ACSE. Most of these thresholds act as gauges of error conditions arising from congestion, protocol errors, or incompatibilities between peer-level entities.
Performance Considerations ESISESCONFTIME Attribute 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.
Performance Considerations What Tools to Use At first, monitoring should be frequent and very comprehensive. When the system stabilizes, monitoring activity may be reduced. Your monitoring activity must always be frequent enough and comprehensive enough to detect problems before they affect the users.
Performance Considerations • When to Monitor Performance Internal operations and events. The SCF TRACE command provides the ability to capture information on the internal processing of the application processes. It records information on the procedure calls that are made, as well as on the internal state messages. It is recommended only for this use. Although the SCF TRACE command can seriously reduce the throughput of the entire system, it is the best way of obtaining this type of information.
Performance Considerations Corrective Actions should analyze what is happening in the system, determine the causes, and then attempt to treat the problems—not the symptoms. The various performance indicators that you can monitor describe different aspects of the behavior of a subsystem. However, these indicators are generally not independent of each other; they are interrelated.
Performance Considerations OSI/AS Configuration and Management Manual—424119-001 6- 16 Corrective Actions
7 OSI/AS Subsystem Description To understand the interaction of the OSI/AS subsystem components when configuring, monitoring, or troubleshooting, you must first have a good understanding of each of the processes that relate to OSI/AS: • • • • OSI manager process (OSI/AS) TAPS process (OSI/AS) TSP process (OSI/TS) NSP process: X25AM or TLAM on D-series releases and PAM on G06 and above releases This section provides a high-level description of the main functions of each OSI layer, as provided by the Com
OSI/AS Subsystem Description OSI Layer Information Flow OSI Layer Information Flow In the OSI Reference Model, requests (in the general sense) are sent from the top layer down, until the request is sent as data over a physical communications medium to a remote peer. Responses (in the general sense) are received at the bottom, physical layer and forwarded up to the local user. A generalized view of the data flow is shown in Figure 7-1. Figure 7-1.
OSI/AS Subsystem Description Connection Phases Each layer, as provided by the appropriate process, is described in terms of the following three categories: • • • Downward information flow. A description of what the layer receives from the layer above, and what the layer sends to the layer below, as shown in Figure 7-1 on page 7-2. Upward information flow. A description of what the layer receives from the layer below, and what the layer sends to the layer above, as shown in Figure 7-1 on page 7-2.
OSI/AS Subsystem Description Application Program Interface (API) Application Program Interface (API) The API is the interface between an application and the TAPS process. An application accesses this interface by calling the APS (application, presentation, and session) procedures. This interface becomes part of your application (as part of the system library) when the APS procedures are bound into your program. For more information on the APS procedures and the API, see the OSI/AS Programming Manual.
OSI/AS Subsystem Description TAPS Process TAPS Process The TAPS process accepts request and response primitives from the API, communicates with the OSI manager process to request and control subdevices, and provides Session Layer, Presentation Layer, and ACSE services. Downward Information Flow Requests are received by TAPS, from the API, as request and response primitives. The TAPS provider replies with I/O completions (sometimes called replies).
OSI/AS Subsystem Description Upward Information Flow Upward Information Flow There are two types of completions that the TAPS process returns to the user: indication or confirm primitives, and I/O completions. Incoming SPDUs are received by the TAPS process and returned to the API as indication or confirm primitives. The following PTrace example shows an incoming CN-SPDU (connect session protocol data unit): 15:45:52:580 >000.
OSI/AS Subsystem Description Upward Information Flow The following PTrace example shows a connect indication primitive received by the TAPS process associated with local SSEL 555501 (from remote SSEL 555502) and forwarded to session ID 2. The TAPS process also indicates that half-duplex transfer was negotiated in this connection: 15:45:52:900 >000.140 #113 TAPS L5 USER L5 Event Su Name #Z000002 Session ID 2 MCB Addr %H000A5E9E DCB Addr %H001c6312 DCB Len 03925 Event Code 00001 (Connect Ind) zcalling^ref.
OSI/AS Subsystem Description State Machine State Machine The TAPS process implements three protocol state machines: session, presentation, and ACSE. The Session Layer protocol (described in the ISO 8327 specification) consists of a set of key states and events that allow for synchronized data transfer between two end systems. The Presentation Layer protocol (described in the ISO 8323 specification) consists of a set of key states and events that establish and maintain a context for data interchange.
OSI/AS Subsystem Description TSP Process TSP Process The TSP process (OSI/TS) provides reliable end-to-end data transfer. It acts as the provider for the Session Layer (the TAPS process) and is the user of the Network Layer (X25AM) and Data Link Layer (TLAM for D-series releases and PAM and SLSA for G06 and above releases) services. The TSP process has its own trace capability.
OSI/AS Subsystem Description Upward Information Flow Upward Information Flow Incoming TPDUs are received by the TSP process and returned to the TAPS process in file-system calls. Errors (such as 140) are returned when the TSP subdevice detects an error. The following PTrace example shows an incoming CR-TPDU: 17:11:53.790 >000.
OSI/AS Subsystem Description NSP Process: X25AM NSP Process: X25AM X25AM manages a connection through an internal subdevice. The TSP process adds subdevices to X25AM using internal names that are different from those used by the upper layers. Subdevices are added at connection time; each subdevice is assigned a unique logical channel number (LCN) for each connection. X25AM acts as the service provider for the TSP process, and provides services to the Network Layer.
OSI/AS Subsystem Description NSP Process: TLAM NSP Process: TLAM In an OSI/AS 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. Downward Information Flow TLAM accepts primitives from the TSP process connectionless-oriented OSI IP in file-system calls to the TLAM port.
8 Troubleshooting Guide This section contains general troubleshooting information; it does not contain all possible combinations of what can go wrong in an OSI network.
Troubleshooting Guide Using the CHECK SU Command Using the CHECK SU Command You can use the SCF command CHECK SU to display information about all the subdevices (controlled by OSI/AS, OSI/TS, X25AM, and TLAM on D-series releases or PAM on G06 and above releases) that match the selection criteria in the command. CHECK SU displays active subdevices, subdevices waiting for a connection to be established, and inactive static subdevices.
Troubleshooting Guide Benefits of Using CHECK SU The format for the CHECK SU display with the DETAIL option for a G-series system is as follows: OSIAS Detailed CHECK SU \MARS.$TAPS.* ASU: \MARS.$x400 ----------------------------------------------------------------TAP: OSI/AS Status SU \MARS.$TAP1.#Z000001 <...a copy of the entire STATUS SU TAPS, DETAIL screen...> ----------------------------------------------------------------TSP: OSI/TS Tsp Detailed Status SU \MARS.$TSP1.#Z000001 <...
Troubleshooting Guide • • • • Examples When a connection configured for dynamic subdevices (in other words, the DELETETIME attribute for the APPL ENTRY object is set to 0) terminates, all subdevices created for that connection are terminated. In this case, CHECK SU wont show anything useful unless the connection is established. In other words, error information cannot be displayed on dynamic subdevices if you are having trouble establishing a connection or the connection has failed.
Troubleshooting Guide Using TRACE and PTrace Commands The following command displays information about only the TAPS subdevices associated with the server $TAP1 that were created by local applications using the APPL ENTRY object called MYAPP: CHECK SU $TAP1.
Troubleshooting Guide Using TRACE and PTrace Commands Figure 8-1. Relationship of TRACE Command and PTrace to OSI/AS and Underlying Subsystems User Application OSI/AS Subsystem PTrace SCF TRACE OSI/TS Subsystem X25AM Subsystem OSI Manager TAPS TSP TLAM or PAM Subsystem NSP X.25 Network NSP LAN CDT 081.CDD For general information about the PTrace utility, see the PTrace Reference Manual.
Troubleshooting Guide Running the TRACE Command Note. The formatted trace files that you create may not appear exactly as shown in this manual. Trace records provide a mix of internal and user information and, therefore, reflect your network configuration and the type of applications you are running. Trace records are used for product development and maintenance as well as for tracking down protocol problems in user applications.
Troubleshooting Guide An Approach to Troubleshooting An Approach to Troubleshooting The OSI/AS subsystem includes various processes—the processes NSP, TSP, TAPS, and the OSI manager process—as well as the API. The interaction of these processes with each other and with the peer protocols at each layer can lead to difficulties when your subsystem is configured improperly, or when an application loses its synchronization with the connection.
Troubleshooting Guide Concentrate on the Layer Exhibiting the Problem If your application receives errors from the API, you can assume that the error is occurring between the TAPS process and the API. If the error reported is a connection error (for example, error 140), then you would check the Transport Layer to see if it returned an error.
Troubleshooting Guide PTrace and Trace Analysis OSIAS Stats SUBSYS \MARS.$OMGR Reset Time..... 15 Oct 1991, 10:00:36.074 Sample Time.... 15 Oct 1991, 10:03:55.258 Configuration: TAPS Process... TSP Process.... NSP Process.... APPL Entry..... TSEL Entry..... NSAP Entry..... SNPA Entry..... L3 Profile..... L4 Profile..... L5 Profile..... Current 2 2 4 4 4 4 4 2 2 2 Maximumever 2 2 4 4 4 4 4 2 2 2 Register Requests: Received....... Succeeded...... 13D 13D Failure Reasons: Loc Name Not Found.
Troubleshooting Guide API Troubleshooting Example The following steps are used to solve this problem: • • • • • Step 1: Reset the Statistics Counters and Rerun the Application on this page Step 2: Analyze the Application Using Inspect on this page Step 3: Review the Statistics Using SCF on page 8-13 Step 4: Correct the Problem on page 8-14 Step 5: Return to the Inspect Session Log on page 8-14 Step 1: Reset the Statistics Counters and Rerun the Application Reset all the statistics counters.
Troubleshooting Guide API Troubleshooting Example The Inspect command L5HALFO-d local_appl_1.zappl^name displays the following: ZAPPL^NAME= ZLEN= 6 ZC= BYTE[0]= "LOCALZ" The next step is to call APS_STATUS_ to find out why the operation failed.
Troubleshooting Guide API Troubleshooting Example Tracking down the error further, the Inspect command L5HALFO-d error_subcode displays the following: ERROR_SUBCODE= 101 You can see that the error subcode is 101 (ZAPS-ERR-MGR-LOCAL-NAME). This means that the local application name is not configured. Step 3: Review the Statistics Using SCF The next step is to check the configuration of the OSI/AS subsystem to verify whether the application name is configured.
Troubleshooting Guide API Troubleshooting Example The screen shows that the APS_ATTACH_ call did send a register request to the OSI manager process to establish a connection. That request failed; the reason given is “Loc(al) Name Not Found.” You can also see that $OMGR is configured for four APPL object entries. The next step is to look at those entries. The SCF command names entry $omgr.#appl.* displays the following: OSIAS Names ENTRY \MARS.$OMGR.#APPL.* ENTRY $OMGR.#APPL.LOCALL $OMGR.#APPL.
Troubleshooting Guide API Troubleshooting Example The Inspect command L5HALFO-d status displays the following: STATUS= 0 You can see that now no error is returned (ZAPS-VAL-STATUS-OK); the ATTACH request completed successfully. Next you should call APS_STATUS_ to verify further.
Troubleshooting Guide TAPS Process And now for one last check; the Inspect command L5HALFO-d service_id displays the following: SERVICE_ID= 5 The service ID of 5 (ZAPS-VAL-SERVICE-SESSION) now fully verifies that TAPS is configured for session service. (This is the default value resulting from the previous APS_ASSOC_ATTACH_ call.
Troubleshooting Guide SCF Commands OSIAS Stats SERVICE \MARS.$TAP1.#L5 Reset Time.... Sample Time... 15 Oct 1991, 10:00:46.637 15 Oct 1991, 10:04:13.157 Refuse SPDUs: No reason.............. Permanent.............. Temporary.............. Other.................. Received 0 0 0 0 Threshold -0 0 -- Sent 0 0 0 0 Threshold -0 --- Abort SPDUs: No reason.............. Protocol Error......... Other.................. 0 0 0 ---- 0 0 2 -0 -- Connect SPDUs............ Accept SPDUs.............
Troubleshooting Guide SCF Commands OSIAS Stats SU \MARS.$TAP1.#Z000000 Session Start Time.. 15 Oct 1991, 9:59:10.418 Resettime........... 15 Oct 1991, 9:59:10.418 Sampletime.......... 15 Oct 1991, 10:04:04.995 Received Total SPDUs................ Total SPDU Bytes........... Total SS-Userdata Bytes.... 1 79 0 Sent 1 8 0 The following command takes a detailed look at the status for that same subdevice (you can use the CHECK SU command to also get this information): STATUS SU $TAP1.
Troubleshooting Guide SCF Commands OSIAS Detailed Status SU \MARS.$TAP1.#Z000000 State............... STARTED Opens............... 1 Opener.............. \SYSTEM.$PROG Opener Id........... 165,17 Loopback............ OFF DeleteTime.......... -1 (Static SU) L4 or Loopback SU.... \MARS.$TSP1.#Z000000 Last Error.......... 0 Last Error Subcode.. 0 Last Error Source... L5 Protocol Version. 1 L5 Protocol State... STA01 Idle, no transport connection DisconnTimer.. 0:00:03.000 Expedited...........
Troubleshooting Guide PTrace and Trace Analysis Called Address: (REMOTE) Application-Name.. AE-Title: AE-Title format. 0 AE-Qual......... AP-Title........ PSEL.............. SSEL.............. 5555 01 TSEL.............. 4444 4444 01 NSAP.............. 4083 3311 1101 Responding Address: (REMOTE) Application-Name.. AE-Title: AE-Title format. 0 AE-Qual......... AP-Title........ PSEL.............. SSEL.............. TSEL.............. NSAP..............
Troubleshooting Guide Troubleshooting Example Troubleshooting Example The following is a Session Layer TAPS process problem that you may encounter. The steps in this example illustrate the logic you might follow when using a top-down problem-solving approach. (Problems in the Presentation Layer and ACSE are diagnosed and corrected in a similar manner.) Symptoms The application is waiting to accept a session connection.
Troubleshooting Guide Troubleshooting Example APS_STATUS_ is called to determine the type of event (evt), and the name of the subdevice (dev). After the following typical line of code ret := aps_status_ ( cepi1, evt, dev, err, errsub, svcid, diagnostic^buf, orig^err ); the Inspect command display DEV displays the following: DEV = BYTE[0] = "\" #249 "TAP1 #Z00000P " This tells you that the application is using TAPS process TAP1 and subdevice #Z00000P.
Troubleshooting Guide Troubleshooting Example Step 3: Review the Statistics Using SCF It might be helpful to check the statistics for the subsystem. This gives you an overview of whether the OSI manager process was able to register subdevices to the TAPS process as a result of the application call to APS_ATTACH_. The SCF command stats subsys $omgr displays the following: OSIAS Stats SUBSYS \MARS.$OMGR Resettime............. 15 Oct 1999, 13:39:14.384 Sampletime............ 15 Oct 1999, 13:40:28.
Troubleshooting Guide Troubleshooting Example The SCF command stats service $tap1.#l5 displays the following: OSIAS Stats SERVICE \MARS.$TAP1.#L5 Reset Time.... Sample Time... 15 Oct 1991, 13:39:46.637 15 Oct 1991, 13:40:13.157 Refuse SPDUs: No reason.............. Permanent.............. Temporary.............. Other.................. Received 0 0 0 0 Threshold -0 0 -- Sent 0 1 0 0 Threshold -0 --- Abort SPDUs: No reason.............. Protocol Error......... Other..................
Troubleshooting Guide Troubleshooting Example Next, you should find out if this subdevice really did receive an incoming connect request SPDU. The SCF command stats su $tap1.#z00000p displays the following: OSIAS Stats SU \MARS.$TAP1.#Z00000P Session Start Time.. 16 Oct 1991, 13:39:14.384 Reset Time.......... 16 Oct 1991, 13:39:14.384 Sample Time......... 16 Oct 1991 13:40:28.009 Received Total SPDUs............... Total SPDU Bytes.......... Total SS-Userdata Bytes...
Troubleshooting Guide Troubleshooting Example The SCF command info entry $omgr.#appl.localx displays the following: OSIAS Info ENTRY \MARS.$OMGR.#APPL.LOCALX *AEQualifier....... *APTitle........... *PSEL.............. *SSEL.............. *TSEL.............. *NSAP.............. *Loopback.......... *Deletetime........ *L5Profile......... *L4Profile......... *L3Profile......... *L5Server.......... *L4Server.......... *L3Server.......... 01020304 { 2 2 0 1 } 555501 4444444401 408333111101 OFF 0 \MARS.$OSIM.
Troubleshooting Guide Troubleshooting Example Session Variables... Vact Vnextact Vsc True False False Token Settings...... Sync-Minor NotAvailable V(A) V(M) Major/Activity NotOwned (see note) V(R) Release Owned Data RemoteChoice Functional Units Selected: L6 Protocol State... STAIO Idle - no connection L6 Normal Mode...... True ACSE Protocol State. STA0 Idle - Unassoc (Awaiting Discard) ACSE Normal Mode.... True Calling Address: (LOCAL) Application Name.. LOCALX AE Title: AETitle Format..
Troubleshooting Guide Troubleshooting Example This screen also displays the name of the subordinate Layer 4 subdevice, $TSP1.#Z00000P. Use the STATS command to check the number of TPDUs sent and received in Layer 4. The SCF command stats su $tsp1.#z00000p displays the following: OSITS Stats SU $TSP1.#Z00000P Reset Time.. 16 Oct 1991, 13:39:14.305 Sample Time. 16 Oct 1991, 13:49:40.004 TPDUsSent.. TPDUsResent UserBytesSt ExpBytesSt. 4 0 8 0 TPDUsRecv.. 4 UserBytesRc 547 ExpBytesRc.
Troubleshooting Guide Troubleshooting Example The SCF command status su $tsp1.#z00000p,detail displays the following: OSITS Detailed Status SU \MARS.$TSP1.#Z00000P State........ TC State..... TC Substate.. Opener....... NSP SU....... STARTED tcon in progress waiting for CR-TPD \MARS.$6,190 \MARS.$X251.#TSP100N NSP Subsys....... FileError........ NSPDSMRetCode.... NSPDSMSubCode1... NSPDSMSubCode2... NSPFSErrorCode... X25ClearCause.... X25DiagCode...... X25DisconReason..
Troubleshooting Guide Troubleshooting Example Step 4: Collect Trace Information Using SCF In this case, the error messages have not been very helpful, and you can only make guesses about the problem from the SCF commands. To find out the real nature of the problem, you need a trace. Use a command like the following to start the trace: trace process $tap1, to tracefil, recsize 1000 While the trace is on, try again to establish a connection from the remote side.
Troubleshooting Guide Troubleshooting Example The following PTrace commands set up the trace filters: filter l5prov filter l5user The PTrace command find "Attach" displays the following: 10/16/91 13:39:14:430 >000.000 #47 TAPS L5 USER L5 Request Su Name #Z00000P Session ID 14 Request Addr %H000A36E8 Request Tag %H0001F8D4 Request Code -32767 (Attach Req) local^addr: zappl^name.zlen = 6 zappl^name.zc = 000: 4C4F 4341 4C58 LOCALX zpsap.zssel.zlen = 3 000: 5555 0100 zpsap.zssel.zc = UU. zpsap.ztsel.
Troubleshooting Guide Troubleshooting Example Pressing the N key continues the search and displays the following: 10/16/91 13:39:56:680 >000.
Troubleshooting Guide Troubleshooting Example Step 6: Correct the Problem Now that you know what the problem is, you need to correct it. Since the local SSEL fields don't match, you need to reconfigure so they do match. Use the INFO ENTRY #APPL command to check on the application entry LOCALX. The SCF command info entry $omgr.#appl.localx displays the following: OSIAS Info ENTRY \MARS.$OMGR.#APPL.LOCALX *AEQualifier....... *APTitle........... *PSEL.............. *SSEL.............. *TSEL..............
Troubleshooting Guide Troubleshooting Example starts the PTrace trace formatter from the file TRACEFIL and displays the following: Trace of: \MARS.$TAP1, Type (55,5). Ptrace Data File: $DIAG.MYSTUFF.TRACEFIL Trace started: 10/17/91 15:18:31.36 First trace entry: 10/17/91 15:18:31.36 Last trace entry: 10/17/91 15:19:10.70 Trace file is an extended format. Trace entry size limit: 1008 The PTrace command log to logptr1 displays the following: Ptrace Log File: $DIAG.MYSTUFF.
Troubleshooting Guide TSP Process 15:19:02:480 >000.
Troubleshooting Guide PTrace and Trace Analysis The following command displays information on the TPDUs transferred through a specific subdevice: STATS SU $TSP2.#Z000001 PTrace 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. Attach requests from TAPS processes are WRITEREAD calls to a TSP subdevice, with the MCW set to signify a specific operation.
Troubleshooting Guide Troubleshooting Example You can check specific TPDUs by specifying them in the FILTER command. The following command specifies all CR-TPDUs, DR-TPDUs, and ER-TPDUs: SELECT L4; FILTER TPDU CR, DR, ER The following command lists the Network Layer primitives traced by the TSP process: SELECT L3; FILTER L3SERVICES A typical record displayed by this command is as follows: 17:11:53:780 >000.
Troubleshooting Guide Troubleshooting Example Step 1: Reset the Statistics Counters and Rerun the Application Reset all the statistics counters. See Command File for Resetting Statistics Counters on page 8-68. Rerun the application. This ensures that the statistics screens are as free from irrelevant information as possible, and makes it easier to identify information pertaining to the particular problem you are trying to diagnose.
Troubleshooting Guide Troubleshooting Example Step 3: Review the Statistics Using SCF It might be helpful to check the statistics for the subsystem. This gives you an overview of whether the OSI manager process was able to register subdevices to the TAPS processes as a result of the application call to APS_ASSOC_ATTACH_. The SCF command stats subsys $omgr displays the following: OSIAS Stats SUBSYS \MARS.$OMGR Reset Time..... 15 Oct 1991, 4:16:19.040 Sample Time.... 15 Oct 1991, 4:17:10.
Troubleshooting Guide Troubleshooting Example Now it would be helpful to take a quick look at the service statistics for Layer 5. The SCF command stats service $tap2.#l5 displays the following: OSIAS Stats SERVICE \MARS.$TAP2.#L5 Resettime........... 15 Oct 1991, 4:16:32.629 Sampletime.......... 15 Oct 1991, 4:17:22.069 Refuse SPDUs: Received No reason................ 0 Permanent................ 0 Temporary................ 0 Other....................
Troubleshooting Guide Troubleshooting Example Now you can check the service statistics for that TSP process. The SCF command stats service $tsp2.#l4 displays the following: OSITS Stats SERVICE $TSP2.#L4 Reset Time.. 15 Oct 1991, 4:16:42.651 Sample Time. 15 Oct 1991, 4:17:33.238 TPDUs-sent................................... 1 TPDUs-received............................... 2 TPDUs-resent................................. 0 UserBytes-sent............................... UserBytes-received......................
Troubleshooting Guide Troubleshooting Example 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.* ,detail displays a status screen from which you can get the line name. The screen is the same as shown in the previous TAPS example, and shows that the line name is $X252. Now you can check the service statistics for that TSP process.
Troubleshooting Guide Troubleshooting Example The SCF command stats su $tap2.#z000022 displays the following: OSIAS Stats SU \MARS.$TAP2.#Z000022 Session Start Time.. 15 Oct 1991, 19:31:21.882 Resettime........... 15 Oct 1991, 19:31:21.882 Sampletime.......... 15 Oct 1991, 19:32:57.988 Received Total SPDUs................ Total SPDU Bytes........... Total SS-Userdata Bytes.... Sent 0 0 0 0 0 0 You can see that no SPDUs have been exchanged.
Troubleshooting Guide Troubleshooting Example Now that you know TPDUs were sent and received, you should check the status of the TSP subdevice in more detail. Either of the SCF commands status su $tsp2.#z000022,detail check su $tsp2.#z000022,detail displays the following: OSITS Detailed Status SU \MARS.$TSP2.#Z000022 State........ TC State..... TC Substate.. Opener....... NSP SU....... STARTED tcon in progress waiting for CR-TPDU \MARS.$6,190 \MARS.$X252.#TSP2014 NSP Subsys....... FileError........
Troubleshooting Guide Troubleshooting Example After recording the problem, be sure to stop the trace. The following SCF command stops the trace: trace process $tsp2, stop Step 5: Analyze the Trace Using PTrace The SCF command ptrace from tr1 starts the PTrace trace formatter on the trace in 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/16/91 04:32:53.
Troubleshooting Guide Troubleshooting Example Record #57 shows the incoming CR-TPDU. The attributes include the TSAP IDs, TPDU size, and the security protection field. 10/16/91 04:36:04:920 >000.010 #58 TCB: 1 Class: 2 S4^CO2^WFCR :E4^CO2^TP^CR =>A4^CHK^CR L4 SM SU: #Z00001S Record #58 indicates that the state machine has begun to verify the CR-TPDU (A4^CHK^CR). 10/16/91 04:36:04:920 >000.
Troubleshooting Guide Troubleshooting Example The attribute values in Record #57 need to be verified against the SCF attributes. Table 8-1 shows the correspondences between the PTrace display of the negotiation parameters and the SCF attributes. Table 8-1.
Troubleshooting Guide Troubleshooting Example The SCF command info su $tsp2.#z000022,detail displays the following: OSITS Detailed Info SU $TSP2.#Z000022 *AltClass.......... *Class............. *DeleteTime........ *Expedited......... *InactiveTimeout... *IPX25SNDCF........ *LANlocalSNPA...... *LANremoteSNPA..... *LocalNSAP......... *LocalTSEL......... *MaxRexmit......... *NetType........... *RecvSecurity...... *RefTimeout........ *RemoteNSAP........ *RemoteTSEL........ *RexmitTimeout..... *SendSecurity..
Troubleshooting Guide Troubleshooting Example Step 6: Correct the Problem Now that you know what the problem is, you need to correct it. You could alter the TSP SU #Z000022, but that would only work for one connection. You really need to alter the field in either the Layer 4 SERVICE object or the Layer 4 PROFILE object.
Troubleshooting Guide Troubleshooting Example The SCF command INFO PROFILE $OMGR.#L4.PROF1,DETAIL displays the following: OSIAS Detailed Info PROFILE \MARS.$OMGR.#L4.PROF1 *AltClass ........ *Class............ *DisconnTimeout... *Expedited........ *InactiveTimeout.. *MaxRexmit........ *NetType.......... *RecvSecurity..... *RefTimeout....... *RexmitTimeout.... *SendSecurity..... *TConPri.......... *TTRTimeout....... *WindowTimeout.... 2 2 0:02:00.00 OFF 0:00:30.00 3 B PASSWART 0:01:40.00 0:00:10.
Troubleshooting Guide NSP Process: X25AM The following PTrace command records all the trace records selected: record all The following are the two trace records of interest: 10/16/91 16:07:20.380437 >000.
Troubleshooting Guide PTrace and Trace Analysis The following command displays the configuration of an X25AM subdevice as it is added dynamically by the TSP process: INFO SU $X251.#TSP10001, DETAIL The screen returned displays X.25-related information taken from either the Layer 3 SERVICE object or the Layer 3 PROFILE object. Some common causes of problems can be easily examined on this screen. In particular, you should look at the following items: • • • X25DESTADDR attribute.
Troubleshooting Guide Troubleshooting Example The following command limits the display to a specific logical channel number (an X.25 circuit): FILTER LCN circuit-number You can use the SELECT L2 mask to determine the LAPB information frames transmitted to and from the Data Link Layer. The following commands omit all the RR frames, thus reducing the display traffic: SELECT L2 FILTER NOTRR The following shows a trace of a typical incoming call request in a Layer 2 information frame: 02:48:44:600 >000.
Troubleshooting Guide Troubleshooting Example Step 2: Analyze the Application Using Inspect Use Inspect to check for error types reported to the application.
Troubleshooting Guide Troubleshooting Example OSIAS Detailed Status SU \MARS.$TAP1.#Z000000 State............... Opens............... Opener.............. Opener Id........... Loopback............ DeleteTime.......... L4 or Loopback SU... Last Error.......... Last Error Subcode.. Last Error Source... STARTED 1 \SYSTEM.$PROG 165,17 OFF -1 (Static SU) \MARS.$TSP1.#Z000000 0 0 L5 Protocol Version. 1 L5 Protocol State... STA01 Idle, no transport connection DisconnTimer........ Expedited...........
Troubleshooting Guide Troubleshooting Example Calling Address: (LOCAL) Application Name.. LOCALX AE Title: AETitle Format.. AEQualifier..... APTitle......... PSEL.............. SSEL.............. 555501 TSEL.............. 4444444401 NSAP.............. 408333111101 Called Address: (REMOTE) Application Name.. AE Title: AETitle Format.. 0 AEQualifier..... APTitle........ PSEL.............. SSEL.............. TSEL.............. 4444444402 NSAP.............. Responding Address: (REMOTE) Application Name..
Troubleshooting Guide Troubleshooting Example The SCF command stats service $tap1.#l5 displays the following: OSIAS Stats SERVICE \MARS.$TAP1.#L5 Reset Time.... Sample Time... 15 Oct 1991, 13:39:46.637 15 Oct 1991, 13:40:13.157 Refuse SPDUs: No reason.............. Permanent.............. Temporary.............. Other.................. Received 0 0 0 0 Threshold -0 0 -- Sent 0 1 0 0 Threshold -0 --- Abort SPDUs: No reason.............. Protocol Error......... Other..................
Troubleshooting Guide Troubleshooting Example The SCF command STATS SERVICE $TSP1.#L4 displays the following: OSITS Stats SERVICE $TSP1.#L4 Reset Time.. 16 Oct 1991, 5:21:42.651 Sample Time. 16 Oct 1991, 5:24:33.238 TPDUs-sent................................... 0 TPDUs-received............................... 0 TPDUs-resent................................. 0 UserBytes-sent............................... UserBytes-received........................... ExpBytes-sent................................
Troubleshooting Guide Troubleshooting Example Now you can check the NSP statistics. The SCF command stats line $x251 displays the following: X25AM STATS Line $X251 Resettime 5:21:41.013 10/16/91 Sampletime 5:25:05.
Troubleshooting Guide Troubleshooting Example Step 5: Analyze the Trace Using PTrace The SCF command ptrace from trx1; select l3 starts the PTrace trace formatter on the trace in TRX1, selects the Layer 3 mask, and displays the following: Trace of: \MARS.$X251, Type (61,0). Ptrace Data File: $DIAG.MYSTUFF.TRX1 Trace started: 10/16/91 05:23:05.79 First trace entry: 10/16/91 05:23:05.79 Last trace entry: 10/16/91 05:24:20.47 Trace file is an extended format.
Troubleshooting Guide Troubleshooting Example 10/16/91 05:23:13:430 >000.010 #68 SDN #000/%000 LEN #0003 GFI(0001) Clear^conf 000: 1001 17 L3 Pkt Out MOD8 LGN/LCN $001 Record #68 shows that X25AM correctly responded to the clear packet with a clear confirm packet. Step 6: Analyze the Problem Further Using SCF You now know there is a problem with the remote subdevice for the application entity REMOTEX. The next step is to get some information about that entity. The SCF command info entry $omgr.#appl.
Troubleshooting Guide Troubleshooting Example The SCF command info entry $omgr.#snpa.02,detail displays the following: OSIAS Detailed Info ENTRY \MARS.$OMGR.#SNPA.02 *L3Profile........... \MARS.$OMGR.#NSP.x252 *L3Server............ \MARS.$OMGR.#L3.NSPX252 This screen shows the name of the profile used to configure the NSAP. You need to check the values of this Layer 3 profile. The SCF command info profile $omgr.#L3.nspx252,detail displays the following: OSI/AS Detailed Info PROFILE \MARS.$OMGR.#L3.
Troubleshooting Guide Troubleshooting Example The X25 process should now accept the connect request; you might take another trace to confirm this. First, stop the application and then start the trace by using the SCF command: trace line $x251,to trx While the trace is running, rerun the application. Stop the trace using the following SCF command: trace line $x251,stop Use PTrace to analyze the trace. This time you need to look only at Layer 3.
Troubleshooting Guide NSP Process: TLAM Record #107 shows that this time the call was confirmed by the remote side. 10/16/91 09:57:10.10700 7000.020000 #133 SDN #001/%001 LEN #0043 GFI(0001) MOD8 Data M=0 P(S)=0 P(R)=0 000: 1001 0027 E400 0000 0520 C105 4444 008: 01C2 0544 4444 4402 C001 09C6 0100 010: 01C5 0870 6173 7377 6F72 64 L3 Pkt Out LGN/LCN $001 4444 C401 Record #133 shows that a network connection was established and that the Network Layer progressed into the data transfer phase.
Troubleshooting Guide SCF Commands Remember that this command returns information on all the protocols running on the LAN controller, not just those related to OSI/AS. The following command displays the total number of 802.3 frames transmitted and received for the NSP process $LAM2. This command also returns a count of the number of frames that were discarded, overruns, FCS errors, and collisions detected: STATS SERVICE $LAM2.
Troubleshooting Guide PTrace and Trace Analysis The following command displays the number and types of IPPDUs sent and received. This command also returns the number of frames that were discarded, checksum errors, and so on: STATS SERVICE $TSP1.#L3 The following screen is returned for this example: OSITS Stats SERVICE $TSP1.#L3 Reset Time.. 16 OCT 1991, 10:53:40.901 Sample Time. 16 OCT 1991, 12:23:33.373 IPPDUs-sent....................... IPPDUs-received................... IPOctets-sent..................
Troubleshooting Guide NSP Process: PAM The screen returned for this command is as follows: ?FIND "LSAP : 000254" 02:49:29:370 >000.
Troubleshooting Guide Getting Help Getting Help If you have attempted the troubleshooting procedures outlined in this section and a problem persists, follow the standard procedures at your site for contacting appropriate support personnel. These procedures might involve contacting your Global Customer Support Center (GCSC) or your local Compaq support representative. To gather the information that will help during further analysis, follow these steps: 1. Reset the statistics for all layers and processes.
Troubleshooting Guide Command File for Obtaining Diagnostic Information comment - (subdevices do not need to be reset). stats process $tap1,reset stats process $tap2,reset stats process $tsp1,reset stats process $tsp2,reset comment - Reset service for all layers. stats service $tap1.#acse,reset stats service $tap2.#acse,reset stats service $tap1.#l6,reset stats service $tap2.#l6,reset stats service $tap1.#l5,reset stats service $tap2.#l5,reset stats service $tsp1.#l4,reset stats service $tsp2.
Troubleshooting Guide Command File for Obtaining Diagnostic Information allow all errors comment - Start up the LOG file (very important). log osiconf comment - Display OSI manager process register requests. stats subsys $omgr comment - Display TSP and TAPS process file system counters. comment - To display the status su and the stats su for $tap1 comment - and $tap2, you need to first get the names of the comment - subdevices via the names su or the check su comment - command.
Troubleshooting Guide Command File for Obtaining Diagnostic Information info entry $omgr.#snpa.01, detail info entry $omgr.#snpa.02, detail comment info entry $omgr.#appl.localx, detail info entry $omgr.#appl.remotex, detail info entry $omgr.#tsel.4444444411, detail info entry $omgr.#tsel.4444444412, detail info entry $omgr.#nsap.408333111111, detail info entry $omgr.#nsap.408333222212, detail info entry $omgr.#snpa.FE08008E000264, detail info entry $omgr.#snpa.
Troubleshooting Guide Command File for Obtaining Diagnostic Information OSI/AS Configuration and Management Manual—424119-001 8- 72
A Examples of Configuration Command Files This appendix contains examples of command files of Guardian and SCF commands to set up particular subsystem configurations. Since each of these examples contains a mixture of SCF and non-SCF commands, use the OBEY command to invoke the appropriate file. The six example configurations are as follows: • • • • • • OSI/AS Over an X.25 Network on page A-2 OSI/AS Over an X.
Examples of Configuration Command Files OSI/AS Over an X.25 Network Note. To use these command files, you must change the file and process names to reflect your environment. In addition, you must be logged on as a member of the super-ID. OSI/AS Over an X.25 Network The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG1.
Examples of Configuration Command Files OSI/AS Over an X.25 Network add process $OSIM.#nsp.X251, name $X251 add process $OSIM.#tsp.TSP1, name $TSP1 & , codefile $SYSTEM.SYS01.TSPOBJ add process $OSIM.#taps.TAPS1, name $TAPS1 & , codefile $SYSTEM.SYS01.TAPSOBJ ============================================================ == Define profiles. (If you want to configure VSN1 ON, == then use the default #L5 service.) ============================================================ add profile $OSIM.#L5.
Examples of Configuration Command Files OSI/AS Over an X.25 Network ============================================================ ==== ==== Add SNPA to local NSAP. ==== add entry $OSIM.#nsap.33a1, snpa a1b1 ==== ==== Add address information for remote NSAP. ==== (SNPA assignment is not needed for remote NSAPs.) ==== add entry $OSIM.#nsap.33b1 add entry $OSIM.#snpa.a1b1 add entry $OSIM.#tsel.44a1 ==== ==== Add a name for the local application. ==== add entry $OSIM.#appl.
Examples of Configuration Command Files OSI/AS Over an X.25 Network, Using SNDCF OSI/AS Over an X.25 Network, Using SNDCF The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG2. ============================================================= == File: EXCFG2 == == Example command file for configuring OSI/AS over an X.25 == network using SNDCF. == SCF must be running before you use the SCF OBEY command == to invoke this file.
Examples of Configuration Command Files OSI/AS Over an X.25 Network, Using SNDCF ==== Assign X25AM NSP process and profile to SNPA. ==== add entry $OSIM.#snpa.a1b1 & , server $OSIM.#nsp.x251 & , profile $OSIM.#L3.L3p1 ==== ==== Add TSP process, SNPA, and profile to local NSAP. ==== add entry $OSIM.#nsap.33a1, server $OSIM.#tsp.TSP1 & , snpa a1b1, profile $OSIM.#L4.L4p1 ==== ==== Add address information for remote NSAP. ==== (SNPA assignment is not needed for remote NSAPs.) ==== add entry $OSIM.#nsap.
Examples of Configuration Command Files OSI/AS Over a LAN OSI/AS Over a LAN The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG3. ============================================================= == File: EXCFG3 == == Example command file for configuring OSI/AS over a LAN. == SCF must be running before you use the SCF OBEY command == to invoke this file.
Examples of Configuration Command Files OSI/AS Over a LAN ==== ==== Assign TLAM (PAM for G06 and above releases) NSP process to remote SNPA. ==== add entry $OSIM.#snpa.fe08008e000a3e ==== ==== Add TSP process, SNPA, and profile to local NSAP. ==== add entry $OSIM.#nsap.33a1, server $OSIM.#tsp.TSP1 & , snpa fe08008e000010 & , profile $OSIM.#L4.L4p1 ==== ==== Add address information for remote NSAP. ==== add entry $OSIM.#nsap.33b1, snpa fe08008e000a3e ==== ==== Add TSEL information for local TSEL.
Examples of Configuration Command Files OSI/AS Over a LAN, Using ES-IS Routing Exchange Protocol OSI/AS Over a LAN, Using ES-IS Routing Exchange Protocol The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG4. ============================================================= == File: EXCFG4 == == Example command file for configuring OSI/AS over a LAN, == using ES-IS routing exchange protocol.
Examples of Configuration Command Files OSI/AS Over a LAN, Using ES-IS Routing Exchange Protocol ==== ==== Assign TLAM (PAM for G06 and above releases) NSP process to local SNPA. ==== add entry $OSIM.#snpa.fe08008e000010 & , server $OSIM.#nsp.LAM1 ==== ==== Assign TLAM (PAM for G06 and above releases) NSP process to remote SNPA. ==== This is not needed with ES-IS routing exchange protocol.) ==== Add TSP process, SNPA, and profile to local NSAP. ==== add entry $OSIM.#nsap.33a1, server $OSIM.#tsp.
Examples of Configuration Command Files OSI/AS Over a LAN, Using IP null OSI/AS Over a LAN, Using IP null The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG5. ============================================================= == File: EXCFG5 == == Example command file for configuring OSI/AS over a LAN, == using the inactive subset of the IP. == SCF must be running before you use the SCF OBEY command == to invoke this file.
Examples of Configuration Command Files OSI/AS Over a LAN, Using IP null add profile $OSIM.#L5.L5p1, vsn1 off, vsn2 on add profile $OSIM.#L4.L4p1, class 4 add profile $OSIM.#L3.L3p1, ipnulllayer on ============================================================= == Define entries. ============================================================= ==== ==== Assign TLAM (PAM for G06 and above releases) NSP process to local SNPA. add entry $OSIM.#snpa.fe08008e000010 & , server $OSIM.#nsp.LAM1 & , profile #L3.
Examples of Configuration Command Files OSI/AS, Large Application, Over an X.25 Network OSI/AS, Large Application, Over an X.25 Network The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG6. This example shows a configuration for a large X.25 application running without SNDCF, requiring three TAPS processes, three TSP processes, and three NSP processes, all controlled by a single OSI manager process.
Examples of Configuration Command Files OSI/AS, Large Application, Over an X.25 Network add process $OSIM.#tsp.TSP2, name $TSP2 & , codefile $SYSTEM.SYS01.TSPOBJ add process $OSIM.#tsp.TSP3, name $TSP3 & , codefile $SYSTEM.SYS01.TSPOBJ ============================================================= == Define TAPS processes. ============================================================= add process $OSIM.#taps.TAPS1, name $TAPS1 & , codefile $SYSTEM.SYS01.TAPSOBJ add process $OSIM.#taps.
Examples of Configuration Command Files OSI/AS, Large Application, Over an X.25 Network ==== add entry $OSIM.#tsel.44b1 ==== ==== Add a name for each local application specify servers ==== and profiles as required. ==== ==== Note that the same address can be supported by ==== different servers. This allows many connections ==== to a single address.
Examples of Configuration Command Files OSI/AS, Large Application, Over an X.25 Network start process $OSIM.#taps.
B Examples of EMS Filters The Event Management Service (EMS) distributor takes in event messages from the subsystems running in your system or network, stores them in an event log, and returns to you (through a printing distributor or to your management application) only those event messages that pass the filter you have installed. By using filters, you can limit the event messages your application receives to those of interest to you. Note.
Examples of EMS Filters Selecting All OSI-Related Messages Selecting All OSI-Related Messages The following filter selects all event messages reported by OSI/AS, OSI/TS, X25AM, and TLAM (on D-series releases) or PAM (on G06 and above releases) subsystems on the system \MYSYS. The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXFLT1.
Examples of EMS Filters Selecting Process-Started Messages Selecting Process-Started Messages The following filter selects the event messages that reflect “process started” events originating from OSI/AS on system \MYSYS. The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXFLT2. == File: EXFLT2 == == This EMS filter selects those event messages, == originating from OSI/AS on system \MYSYS, that == reflect "process started" events.
Examples of EMS Filters Selecting Process-Started and Selected L5 Threshold Messages Selecting Process-Started and Selected L5 Threshold Messages The following filter selects the event messages, originating from OSI/AS on system \MYSYS, that reflect either one of the following: • • A “process started” event An event reporting that the number of Session Layer “aborts sent” protocol errors exceeded the set threshold The source code file for this example is provided as part of the OSI/AS software.
Examples of EMS Filters Selecting Internal and State-Machine Errors Selecting Internal and State-Machine Errors The following filter selects all event messages that report internal errors (ZOSI^EVT^INTL^ERR) and state-machine errors (ZOSI^EVT^SM^ERR) originating from OSI/AS on system \MYSYS. These event messages should be reported to the Global Customer Support Center (GCSC). The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXFLT4.
Examples of EMS Filters TACL Macro File to Compile Filter Examples TACL Macro File to Compile Filter Examples Before installing a filter, you must compile it using the EMS filter compiler. Since filters are based on TACL, compilation requires that you load in the TACL versions of the definition files containing the definitions you use in your filter. You can use the following TACL macro file to load the definitions and compile the four example filters.
Glossary The following glossary defines terms used in this manual and in the other Compaq OSI product manuals. Not all terms listed here are used in this particular manual . action event. An event that requires operator intervention. Each subsystem determines which events are action events by including a unique Event Management Service (EMS) token in the event message.
Glossary Compaq OSI/FTAM address component of the Application Layer, allowing Compaq applications to communicate with other applications in a multivendor environment. Compaq OSI/FTAM. A communications subsystem that provides file transfer, access, and management (FTAM) functions across a heterogeneous network, in conformance with the International Standards Organization (ISO) FTAM standard. Compaq OSI/FTAM supports the transfer of files between Himalaya S-series servers and other kinds of computers.
Glossary data-transfer phase arrives at the next layer without any errors. OSI/TS is an example of an application that uses the Data Link Layer. data-transfer phase. The phase of an Open Systems Interconnection (OSI) connection in which data is transferred. This phase begins when the connection-establishment phase is completed. Compare connection-release phase. dialog unit. In the Session Layer, the work carried out between two major synchronization points chosen by the application.
Glossary Event Management Service (EMS) Event Management Service (EMS). A part of Distributed Systems Management (DSM) used to provide event collection, event logging, and event distribution facilities. EMS has a programmatic interface based on the Subsystem Programmatic Interface (SPI) for both reporting and retrieving events. flow control. A function that regulates the flow of data within a layer or between adjacent layers. global network address.
Glossary link access protocol - balanced (LAP-B) link access protocol - balanced (LAP-B). International Telecommunications Union– Telecommunications (ITU–T) standards that define in the Data Link Layer the requirements for X.25 connections over wide area networks (WANs). 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 that is considered local with respect to the user. Management Information Base (MIB).
Glossary Open Systems Interconnection (OSI) Open Systems Interconnection (OSI). A set of standards used for the interconnection of heterogeneous computer systems, thus providing universal connectivity. Open Systems Interconnection (OSI) address. The address of an object on the network, which includes the network service access point (NSAP), transport selector (TSEL), session selector (SSEL), and presentation selector (PSEL). See also Open Systems Interconnection (OSI).
Glossary Presentation Layer Method (TLAM) lines (for D4x-series releases) or Port Access Method (PAM) lines (for G06 and later releases), the address used by TLAM or PAM to specify the address of the connection to a local area network (LAN) controller. Presentation Layer. Layer 6 in the Open Systems Interconnection (OSI) Reference Model. This layer resolves the differences of varying data formats between systems of different vendors.
Glossary Session Layer Session Layer. Layer 5 in the Open Systems Interconnection (OSI) Reference Model. It allows the setup and termination of and controls communication sessions between nodes on the network. session selector (SSEL). A logical address in the Session Layer through which session services are made available. A single SSEL can service one or more connections simultaneously. session service access point (SSAP).
Glossary subsystem ID (SSID) few commands itself. It provides security features, version compatibility, support for tracing, and support for applications implemented as NonStop process pairs. subsystem ID (SSID). In Distributed Systems Management (DSM) programmatic interfaces, a data structure that uniquely identifies a subsystem to the Subsystem Programmatic Interface (SPI).
Glossary ViewPoint ViewPoint. An extensible, interactive console application for operators, provided as part of Distributed Systems Management (DSM). X.25 Access Method (X25AM). A Compaq product that implements, for wide area networks (WANs), the services of the Network Layer and layers below. X.25 network. Any network or subnetwork linked using X.25 standards. X.
Index Numbers 3223 controller 1-16 3601 controller 1-16 3602 controller 1-16 3603 controller 1-16 3604 controller 1-16 3605 controller 1-16 3606 controller 1-16 3614 controller 1-17 3615 controller 1-17 3616 controller 1-17 3650 controller 1-17 3651 controller 1-17 3840 controller 1-17 6710-6 controller 1-17 6710-7 controller 1-17 A ABORT commands ABORT LINE examples 5-15 ABORTING process state 2-18 ACSE associations, defined 1-8 configuring service attributes 4-20 connection phases 7-3 direct access to 1-
Index C APPL ENTRY objects, specifying profiles and servers 4-22 Application names configuring 2-16 Applications characteristics of large 4-39 configuring names 2-16 suggestions for large 4-39 user, sample configuration 4-36 APTITLE attributes, in APPL ENTRY 2-16 Associations, with ACSE 1-8 Attach requests relationship to ports 4-8 relationship to subdevices 4-6 Attributes checksum 6-8 CIRCUITS 6-7 CLASS 6-6 connection-related 6-5/6-7 CONNECTTIMEOUT 6-6 default values 6-3 DELETETIME 6-5 DISCONNECTTIMEOUT
Index D Command files (continued) making changes to 5-4 TACL 5-3 X.25 large application example A-13 X.25 network example A-2 X.
Index E DELETETIME attribute 6-5 DEVICE NAME parameter, in SYSGEN 5-12 DISCONNECTTIMEOUT attribute 6-6 Distributors, for EMS 5-2 Domains, addressing 3-4, 3-6 DSC description 4-4 DSC utility 1-14, 2-4, 5-12 DSM 1-14 facilities 2-1 programmatic interface 2-1 DSP address component description 3-9, 3-11, 3-12 encoding by Network Layer 3-13 examples 3-14, 3-17 nonstandard values 3-14 DTE addresses 3-3, 3-6 Dynamic subdevices 4-26 E EIA standards implemented 1-11 EMS 2-6 as a management tool 1-14 creating filt
Index G G Guardian altering process attributes 5-14 Guardian 90 configuring 1-13 file-system procedures 1-10 H Help troubleshooting 8-68 Help, online 2-7 High PIN processes 1-6 HRPF 3-13, 3-14 I IDI address component description 3-9, 3-10 encoding by Network Layer 3-13 examples 3-14, 3-17 IDP address component description 3-9 examples 3-14, 3-17 IEEE standards implemented 1-11 INACTIVETIMEOUT attribute 6-10 Incoming call packet addresses 3-7 INFO commands file for collecting diagnostics 8-69 INFO ENTRY
Index M Lines starting network 4-5 LMIB 1-9, 2-4 Load distribution one TSP supporting each X25AM line 4-42 single TSP for multiple X25AM lines 4-41 Loads, distributing 6-2 LOOPBACK attribute 6-5 Loopback connections 4-23 LSAP selectors 3-3 L#WINDOW attribute 6-9 M MAC addresses 3-1 MAC station addresses, finding 4-28 Macros, TACL 2-7 Management and configuration tools 1-13 Managing TAPS processes 5-14 MAXCONNECTIONS attribute 6-4 MAXNSP attribute 6-4 MAXREMIT attribute 6-10 MAXTAPS attribute 6-4 MAXTSP a
Index O Network Layer (continued) configuring protocol attributes 4-15, 4-16 connection phases 7-3 direct access to 1-10 encoding NSAP addresses 3-13 installing 4-4, 5-12 PTP interface 4-7 services 4-5 standards implemented 1-11 NEWPROCESS procedure 1-13, 4-4 Nonsensitive commands, table of 2-10 NonStop process pairs 4-4, 4-11 NonStop systems 1-6 NPDU 3-13 NSAP addresses address components 3-8 AFI component 3-9 configuring local 4-28 configuring local 2-14, 4-30 configuring remote 2-15, 4-32 converting fo
Index P selection hierarchy 2-35 SERVICE 2-25 SU naming conventions 2-32 SUBSYS 2-33 subsystem performance 6-4 Online help 2-7 Operating system image 4-5 OSI addresses 1-9 OSI manager process altering attributes of 5-15 as subsystem component 1-6 default service values set 2-26 functions 2-4 installing 4-11 overview of functions 1-8 process selection 1-10 starting 5-15 OSI Reference Model 1-2 information flow in 7-2 OSIMGR file 4-11 OSI/AS subsystem architecture 1-2 components 1-5, 1-9 configuring 4-4/4-1
Index R STOPPING 2-18 SUSPENDED 2-18 SUSPENDING 2-18 UNDEFINED 2-18 Processes adding 4-12 adding and deleting 5-11 as subsystem components 1-6 high PIN 1-6 registering 5-12 selecting 1-10 starting 4-14, 5-16 states 2-17 Product numbers, software 1-18 PROFILE objects 2-22 adding 5-17 deleting 5-20 displaying names 5-8 finding attributes of 5-10 Layer 3 protocol 4-15, 4-16 Layer 4 protocol 4-17, 4-18 Layer 5 protocol 4-18, 4-19 naming 2-24 relationship to ENTRY objects 2-23 relationship to SERVICE objects 2
Index S as a management tool 1-14 as a performance-monitoring tool 6-13 commands for PROCESS objects 2-18 for SERVICE objects 2-25 table of nonsensitive 2-10 table of sensitive 2-9 compared with PTrace negotiation parameters 8-47 description 2-1, 2-5, 4-3 managing NSP processes 2-8 managing TAPS processes 2-9 managing TSP processes 2-9 objects 2-10 online help 2-7 wildcards, using 2-8 SCF commands for PROFILE object 2-23 SCF objects ENTRY 2-12 naming conventions 2-13 PROCESS 2-17 SCP 2-5 SCP process 1-14,
Index T examples 5-13, 5-15 START PROCESS examples 4-14 STARTED process state 2-17 Starting processes 1-13 STARTING process state 2-18 State machines in TAPS processes 7-8 in TLAM NSP processes 7-12 in TSP processes 7-10 in X25AM NSP processes 7-11 Static subdevices 4-26 Statistics, resetting counters 8-68 STATS commands file for collecting diagnostics 8-69 file for resetting counters 8-68 STATS LINE examples 8-42 STATS PORT examples 8-65 STATS SERVICE examples 8-16, 8-24, 8-40, 8-64, 8-65 STATS SU exampl
Index T overview of functions 1-8 starting 1-13, 4-14 troubleshooting strategy 8-16/8-35 TAPSOBJ file 4-14 The 6-11 Timers default values 6-3 TLAM addresses 3-1 creating ports 4-8 deleting ports 4-8 finding MAC station addresses 4-28, 5-21 installing 4-7 managing 2-8 naming subdevices 4-8 NSP process provider 1-7 protocols supported 1-11 subdevices, displaying names 5-8 troubleshooting example 8-64/8-67 TPDU size TLAM vs. OSI/TS 4-9 X25AM vs.
Index U U UNDEFINED process state 2-18 User applications accessing specific layers 1-10 configuring and registering 2-16 interface to TAPS process 7-4 services provided to 1-9, 1-10 Utilities DSC 2-4 V VERSION commands examples 5-11 ViewPoint program 5-1 W WANs 1980 vs.
Index Z OSI/AS Configuration and Management Manual— 424119-001 Index -14
