Installing and Administering HP OSI Transport Services Edition 6 32070-90030 HP 9000 Networking E0597 Printed in: United States © Copyright 1997 Hewlett-Packard Company. All rights reserved.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc.
Contents 1. HP OTS/9000 Resources HP-UX Manual Reference Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Logging Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Link Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 OTS Subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 OSI Transport Services Documentation. . . . . . . . . . . . . . . . . . . .
Contents Current NSAP Allocation Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ANSI Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AFNOR Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . United States GOSIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . United Kingdom GOSIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP/TOP 3.0. . . . . .
Contents Determine the Addressing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Network Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Application Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Naming Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Gather and Distribute Configuration Information . . . . . . . . . . . . . . . . .81 3.
Contents Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 If Not On HP-UX 10. 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 To Add a New Link to HP OTS/9000 for Series 700/800 . . . . . . . . . . .
Contents To Update HP OTS/9000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 To Verify HP OTS/9000 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .132 6. HP OTS/9000 Configuration Files About the Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 OTS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 Related Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 10
Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. the manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
Preface This booklet describes how to plan, install, and configure the HP OSI Transport Services product. It is divided into six chapters, which provide the following information: Chapter 1 “HP OTS /9000 Resources” introduces OTS, provides OSI concepts, and references other useful tools for installing, configuring, and maintaining OTS software. Chapter 2 “Installing OTS/9000” describes how to install OTS/9000 and RFC1006.
HP OTS/9000 Documentation Map The following documentation map is intended to be a general guideline to the manuals containing information related to HP OTS/9000. Figure 1 Installation Installing and Administering HP OTS/9000 Administration and Troubleshooting Installing and Administering HP Fibre Channel/9000 HP OSI Troubleshooting Guide Networks Managing MC/ServiceGuard Systems HP Models 712/715/735/755 owner's guides HP 9000 Models E, F, G, H, I owner's guides Upgrading from HP-UX 9.x to 10.
1 HP OTS/9000 Resources This chapter provides OTS concepts, network examples, and additional tools for installing, configuring, and maintaining HP OTS/9000.
HP OTS/9000 Resources HP-UX Manual Reference Pages HP-UX Manual Reference Pages While installing, configuring, or troubleshooting OTS/9000, you may need to refer to any of the following online manual reference pages (man pages) for useful HP-UX operating system or OTS commands.
HP OTS/9000 Resources HP-UX Manual Reference Pages • otsdelroute(1M) deletes the specified route entry. • otsshowes(1M) displays all end system entries for the specified subnetwork. • otsshowis(1M) displays all intermediate system entries for the specified subnetwork. • otsshownsaps(1M) provides the NSAPs configured for a given network service. • otsshowroute(1M) displays all route entries for the specified subnetwork.
HP OTS/9000 Resources Logging Messages Logging Messages HP OTS/9000 uses the nettl(1M) logging and tracing facility supplied with HP-UX. See the nettl(1M) manual (man) page for information on using the command line interface. NOTE All log message cause and action statements are now online and can be viewed with any ASCII text editor. The OTS cause and action statement file is /opt/ots/doc/ots_messages.txt. Listed below are some example commands. • To examine the log file: netfmt -file /var/adm/nettl.
HP OTS/9000 Resources Logging Messages Link Subsystems Use the following link subsystem names when logging and tracing OTS/ 9000: • NS_LS_DRIVER - This is the IEEE 802.3 LAN link. • FDDI - This is the FDDI LAN link. • SX25L2 - This is the level 2 high performance X.25 link tracing subsystem. • SX25L3 - This is the level 3 high performance X.25 link tracing subsystem.
HP OTS/9000 Resources OSI Transport Services Documentation OSI Transport Services Documentation There are two manuals provided with the HP OTS/9000 product: • Installing and Administering OSI Transport Services (the OTS manual). This manual provides information specific to OTS/9000. It covers: • Installation • Network planning • Gathering configuration data • Configuring and verifying • OSI Troubleshooting Guide (the OSI manual). This manual contains information relevant to the whole OSI stack.
HP OTS/9000 Resources Contacting Your HP Representative Contacting Your HP Representative If you have no service contract with HP, you may follow the procedure described below, but you will be billed accordingly for time and materials. If you have a service contract with HP, document the problem as a Service Request (SR) and forward it to your HP representative. Include the following information where applicable: • A characterization of the problem.
HP OTS/9000 Resources Contacting Your HP Representative • Try to determine the general area within the software where you think the problem exists. Refer to the appropriate reference manual and follow the guidelines on gathering information for that product. • Document your interim, or “workaround,” solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur.
HP OTS/9000 Resources HP OTS/9000 HP OTS/9000 HP OSI Transport Services/9000 (OTS/9000) networking software provides the Network, Transport, Session, Presentation, ROSE, and ACSE layers of the OSI reference model. OTS/9000 also provides OSI network layer services over the X.25/9000, FDDI/9000, or LAN/9000 link. These layers supply the necessary foundation to run OSI services, such as FTAM and X.400, as well as CMIP, which is part of the HP OpenView product.
HP OTS/9000 Resources HP OTS/9000 Figure 1-1 Open View (CMIS) X.400 X.500 FTAM Customer Application APRI Session API User Space Kernel Space XTI ACSE/Presentation/ROSE Session CLTS Transport MSDSG RFC1006 TCP/IP CONS CLNS X.25 IEEE 802.3 FDDI Supported TCP/IP Links OTS/9000 Components OTS/9000 resides in the kernel and is accessed through the streams facility.
HP OTS/9000 Resources HP OTS/9000 • MSDSG (Multi-System Distributed System Gateway) • RFC1006 (OSI Transport Class 0 over TCP Specification) • CONS (Connection Oriented Network Service) • CLNS (Connectionless Network Service) Chapter 1 27
HP OTS/9000 Resources The OSI/RFC1006 Stack The OSI/RFC1006 Stack RFC1006 allows OSI services, for example X.400, to run over TCP connections. RFC1006 provides the OSI Transport Protocol (TP) class 0 over TCP. RFC1006 does not, by itself, support OSI services. The upper layers of the OSI stack provided by OTS are still required. The graphic below shows the OSI protocol stack with and without RFC1006. The RFC1006 replaces the OSI transport connections with TCP connections.
HP OTS/9000 Resources How HP OTS/9000 Establishes a Connection How HP OTS/9000 Establishes a Connection Establishing a connection between local and remote systems involves the following: • Higher-layer applications, such as FTAM and X.400, require address information and NSAP values. The addresses determine the peer entity at each layer of the stack. See “Addressing” in the “Resources” chapter of this manual. • A user-created application uses the stream /dev/osipi or /dev/ositpi for primitive requests.
HP OTS/9000 Resources Supported Services and Functionality Supported Services and Functionality The OTS/9000 product includes the following: • ACSE/Presentation services (ISO 8649 and ISO 8822) • ROSE Service (ISO 9072-1, CCITT X.219) • OSI Session protocol and services (ISO 8326, 8327; CCITT X.215, X.225, T.62) • OSI Transport protocol and services (ISO 8072, 8073, 8602; CCITT X.214, X.224 and T.70 for Teletex terminals) • OSI Network services: CONS over X.25; CLNS over X.25, FDDI and IEEE 802.
HP OTS/9000 Resources Supported Services and Functionality Session Functionality The Session layer provides cooperating applications with a standard protocol to organize and synchronously exchange user data, and to map user-oriented Session addresses to network-oriented Transport addresses. The Session layer corresponds to layer 5 of the OSI reference model.
HP OTS/9000 Resources Supported Services and Functionality Transport Functionality The Transport layer corresponds to layer 4 of the OSI reference model. As with the Session layer, the Transport layer provides cooperating applications with a standard protocol to organize and exchange user data. Unlike Session, the Transport is implemented with a greater knowledge of the underlying network configuration. Therefore, its definition involves details hidden from the Session layer entity.
HP OTS/9000 Resources How OTS/9000 Finds a Remote End System How OTS/9000 Finds a Remote End System After a brief review of what an end system and an intermediate system are, this section describes how routing information is obtained and provided, and how OTS/9000 uses it. A system can act as an end system or as an intermediate system. OTS can function only as an ES. • An end system (ES) initiates or responds to a communication (it supports layers 1 through 7).
HP OTS/9000 Resources How OTS/9000 Finds a Remote End System The maximum number of routing entries (by type of subnetwork) is as follows: CONS/X.25 CLNS/X.25 CLNS/802.3 or FDDI LAN Number of ES entries 430 (default), 2550 (maximum)* 325 (default), 999 (maximum) 250 (default), 999 (maximum) Number of IS entries 430 (default), 2550 (maximum)* 15 (default), 999 (maximum) 15 (default), 999 (maximum) * Total number of routing ES and IS entries across all CONS/X.25 subnetworks.
HP OTS/9000 Resources How OTS/9000 Finds a Remote End System IF THEN 1 The destination NSAP belongs to an ES known through static configuration or dynamic addition through the ES-IS protocol or the otsaddes command OTS/9000 sends the PDU directly to the specified remote ES 2 The network ID of the destination NSAP matches a local LAN network ID configured in the osiadmin LAN Subnetwork screen. OTS/9000 will send the PDU to the first IS on the subnetwork, if known.
HP OTS/9000 Resources How OTS/9000 Finds a Remote End System NOTE In all cases, if multiple Network IDs match, the longest match is chosen, but local LAN Network IDs are always chosen over Network IDs configured as routes.
HP OTS/9000 Resources How OTS/9000 Uses Network Identifiers How OTS/9000 Uses Network Identifiers OTS/9000 will always check to see if it has a Destination system entry (either dynamically or statically created) for a given NSAP first. If no such entry exists, it will try to determine which subnetwork the destination may be reached on. This is accomplished using the Network ID field on the LAN (802.3 or FDDI) subnetwork configuration screens.
HP OTS/9000 Resources How OTS/9000 Uses the X.25 Network How OTS/9000 Uses the X.25 Network OTS/9000 supports the Connection-Oriented Network Service (CONS) and Connectionless Network Service (CLNS) over the X.25 network. The main objectives of X.25 are: • forming the control and data packets • exchanging these packets • establishing and supervising virtual circuits OTS/9000 is primarily concerned with the virtual circuit (VC) objective, leaving the other objectives to the X.25 product.
HP OTS/9000 Resources How OTS/9000 Uses the X.25 Network OTS/9000 uses the X.25 address to configure a logical mapping of the NSAP. For X.25 implementations using the 1984 specification or later, the NSAP is passed in the Extended Address (EA) facilities field in the X.25 call packets, if configured; the NSAP is the calling address. If the X.25 switch or X.25 network does not support the 1984 X.25 protocol, or the extended address facility is not configured, OTS/9000 will use the X.
HP OTS/9000 Resources Addressing Concepts Addressing Concepts SAP - A SAP, or Service Access Point , is a “pipe” between two OSI layers that allows one layer to obtain a set of services from another layer. The services obtained vary from layer to layer, but are usually management functions, such as connection establishment and termination, and data transfer functions.
HP OTS/9000 Resources Addressing Concepts Figure 1-4 ISO ARPA Application Data Data Application Socket BS XTI SAP T-selector Socket Port ID TCP Data Data ISO Transport IP NSAP SAP Socket IP SAP Data Data ISO Network Socket Selector - A selector is a sequence of octets (bytes) used to identify a SAP. Using the BSD socket analogy, a SAP is the socket, a selector is the two octet Port ID that is bound (using bind()) to the socket.
HP OTS/9000 Resources Addressing Concepts NOTE Because of the relationship between SAPs and selectors, the terms are sometimes used synonymously. If the term SAP (for example, PSAP, SSAP, TSAP) appears in HP documentation, it should be taken to mean the selector (that is, P-selector, S-selector, T-selector) representing the SAP. Address - An address is a sequence of selectors, plus at least one NSAP (network service access point), that identifies an entire “conduit” through a protocol stack.
HP OTS/9000 Resources Addressing Concepts FTAM Presentation Address Data FTAM Responder Data SAP ACSE P-selector SAP Data Presentation S-selector Session Data SAP T-selector SAP Data Transport NSAP SAP Network Chapter 1 Data Figure 1-5 43
HP OTS/9000 Resources Network Layer Network Layer Unlike the ARPA protocol suite that only has a single network protocol (IP), ISO has defined two network layer services: CONS (Connection-Oriented Network Service) and CLNS (Connectionless Network Service). OTS supports CONS over the X.25 protocol, and CLNS over the X.25 and 802.3/ FDDI protocols. The OTS programmatic interfaces, such as XTI, are designed to allow applications to communicate over either network service.
HP OTS/9000 Resources Network Layer Figure 1-6 CLNS CONS 02 01 Subaddress X.25 Switch 212234 Switch Address X.25 In this example, two X.121 addresses have been defined: the subnetwork address for the CONS entity is 21223401, and the subnetwork address for the CLNS entity is 21223402. NOTE Although the use of subaddresses is the recommended method to identify different X.25 users, some switches and X.25 networks do not support its use.
HP OTS/9000 Resources Network Layer Figure 1-7 ARPA IP CLNS 06 FE LSAP 802.2 / 802.3 08-00-09-12-34-56 MAC Address On an 802.3 subnetwork, a point of attachment is identified by an IEEE MAC address. Instead of configured subaddress portions, the 802.3 protocol uses embedded, well known LSAP (Link Service Access Point) values for the CLNS and ARPA IP entities.
HP OTS/9000 Resources Structure of NSAP Addresses Structure of NSAP Addresses A Network Service Access Point address (NSAP) is the ISO-defined Internet Address. It is used to identify real systems unambiguously on a network. NSAPs are used by OTS/9000 in much the same way as ARPA Internet addresses are used by TCP/IP. There are several documents that may help you better understand this section.
HP OTS/9000 Resources Structure of NSAP Addresses • Take into account the needs of different network types (individual or “small,” sophisticated or “big,” and intermediate). • Facilitate efficient routing in private networks. • Provide a strategy that takes advantage of dynamic routing protocols such as ES-IS and the emerging IS-IS protocols. • Minimize the risk of re-structuring, due to present lack of universally accepted standards for NSAP structures.
HP OTS/9000 Resources Structure of NSAP Addresses that begins with this value is ultimately under the control of NIST. NIST also owns the right to define how the DSP portion of its NSAP space is to be formatted and used. The IDP contains two fields. The authority and format identifier (AFI) field identifies the type of address used in the DSP. The initial domain identifier (IDI) field identifies which domain the DSP part belongs to.
HP OTS/9000 Resources Structure of NSAP Addresses 39840F010101. Any NSAP that begins with this value is under the control of Joe’s Grommet Shop. Joe’s Grommet Shop may also define the format for the rest of the DSP to suit their needs. The fields of an NSAP create a hierarchy where each field further divides the NSAP space into smaller, more manageable spaces. Also, the leftmost portion of an NSAP deals with the administration of NSAP spaces, not specifically with the identification of real systems.
HP OTS/9000 Resources Structure of NSAP Addresses Area - An area is a group of end systems and intermediate systems interconnected by one or more subnetworks. They have been grouped together by way of an autonomous routing mechanism. An autonomous routing mechanism is either a set of statically configured intermediate systems, or a set of intermediate systems that support a dynamic routing protocol, such as the ISO IS-IS protocol.
HP OTS/9000 Resources Structure of NSAP Addresses Reserved field - This is simply a portion of the PAP that is not in use, but has been reserved in case it is needed some time in the future. If the network administrator defines a PAP with a reserved field, a default value (usually all 00s) should be defined that the reserved field is always set to. NSAP selector - A one octet field at the rightmost portion of the PAP. It identifies the entity attached to the network layer.
HP OTS/9000 Resources Structure of NSAP Addresses Area ID A two octet field containing a unique ID for the area on which the NSAP resides. ES ID A six octet value, unique within the Area, which identifies the end system. NSel A one octet value. The recommended value is 01. This format is commonly called the 2/6/1 structure because of the sizes of the three defined fields. This is the format that NSAP addresses should obey in order to get the most use out of the automated routing protocols.
HP OTS/9000 Resources Current NSAP Allocation Formats Current NSAP Allocation Formats This section shows a number of examples for existing NSAP allocation formats. Other standards organizations may have additional formats that customers may want to use. Customers can contact standards organizations within their home country to obtain more information. NOTE HP recommends that customers use the binary format for NSAPs. Therefore, only this format is discussed here.
HP OTS/9000 Resources Current NSAP Allocation Formats AFNOR Format Figure 1-13 IDP 39 octet 0 DSP 250F Org ID 1 3-5 2 6 AP 19 (maximum) PAP AFNOR (Association Francaise de NORmalisation) is the standards body that controls the French Data Country Code (DCC) 250. Like ANSI, they have defined the first three octets of the DSP to be an Organization Identifier, leaving the other 14 octets (the PAP) to be defined by each controlling organization.
HP OTS/9000 Resources Current NSAP Allocation Formats DFI DSP Format Identifier. This is used to specify the structure, semantics and administration requirements for the remainder of the DSP. Currently, only one DSP Format exists. This field is similar in function to a Version field. Admin This field functions in much the same way as the Org ID field in the ANSI format. It is an Administration authority identifier. The values for this field are under the control of NIST.
HP OTS/9000 Resources Current NSAP Allocation Formats Telecommunications Customer Requirements Office U. S. General Services Administration IRMS Office of Telecommunications Services 18th & F Sts. N.W. Washington, D. C., 20405 A more complete discussion of this addressing format may be found in U.S. Government OSI Profile Specification Version 2. This document is produced by the National Institute of Standards and Technology, USA (NIST). It should be available through Omnicom or NIST.
HP OTS/9000 Resources Current NSAP Allocation Formats The Subnetwork Identifier may identify a physical subnetwork, or an area. The Subnetwork Address field may contain a real subnetwork address, such as a MAC or X.121 address, or a virtual end system identifier that uniquely identifies the end system for the specified Subnet ID. HP recommends that the NSel field be set to 01. A more complete discussion of this addressing format may be found in U.K. Government OSI Profile Specification Version 3.
HP OTS/9000 Resources Current NSAP Allocation Formats Unlike ANSI and AFNOR, which defined an AP and left the PAP undefined, MAP/TOP has defined a general format for the PAP portion. Their PAP may be used with any valid AP. MAP/TOP has decided to use subnetworks as their level of routing rather than areas. This is more in line with present ARPA routing procedures than the upcoming ISO routing protocols.
HP OTS/9000 Resources Building Temporary Administrative Prefixes Building Temporary Administrative Prefixes In many cases, the examples above will not fit the needs of many users. This is because they are not government organizations, the company does not reside in a country which has an NSAP authority, or the company does not wish to pay the registration fees required to obtain an NSAP space.
HP OTS/9000 Resources Building Temporary Administrative Prefixes As an example, suppose Joe’s Grommet Shop decides not to obtain an ANSI Org Id at this time. Instead, they use the E.163 format. The network administrator decides to use the International Telephone Number of their customer order department for the IDI value. Figure 1-19 IDP DSP 43 114085551122 AP PAP Use an X.121 Address Another option is to use an X.121 address as the IDI value. The AFI for this format is 37.
HP OTS/9000 Resources Building Temporary Administrative Prefixes Use the ISO Local Format ISO defines a format known as the Local format. HP recommends that you do not use this format because it can result in non-unique NSAP values. They should only be used for pilot networks or for diagnostic purposes on networks that are isolated, that is, not connected to any public networks.
HP OTS/9000 Resources A Recommended PAP Structure A Recommended PAP Structure Here is an example of a PAP structure that may either be used with a current allocation format that allows the PAP to be defined (such as ANSI), or with a temporary AP. The last portion of the PAP should have the following structure: Figure 1-23 IDP DSP User Defined length (octets) Domain Area 2 20 octets 2 ES NSel 6 1 User Defined A unique, user defined number.
HP OTS/9000 Resources A Recommended PAP Structure The above PAP allocation follows the structure used by the IS-IS protocol. It allows areas to be created that contain multiple subnetworks. The User Defined portion may be comprised of one or more of the following fields: • A version or DSP format identifier. This allows the format of the PAP to be redefined at some later point in time. These fields are usually two octets in length, but any size may be chosen.
HP OTS/9000 Resources General Recommendations for NSAP Addresses General Recommendations for NSAP Addresses Here is a list of recommendations by HP for the allocation of NSAPs for use with OTS: • Use an Administrative Prefix obtained from a national or international authority if at all possible. An authority does not have to reside in the same country as the petitioning organization (for example, a company in Spain could petition AFNOR for an Organization Identifier).
HP OTS/9000 Resources Non-standard NSAP Formats for Use in OTS Non-standard NSAP Formats for Use in OTS If the CONS network being used supports the 1984 X.25 Extended Address facility, the NSAPs configured should conform to the above recommendations. If the CONS network being used is version 1980, or does not support the Extended Address facility, use the X.121 address of the system’s attachment point onto the X.25 network in place of an NSAP.
2 Planning Your Network The process you should use to successfully bring up a new OSI network or add to an existing OSI network 67
Planning Your Network Planning Your Network Planning Your Network This chapter describes the process you should use to successfully bring up a new OSI network or add to an existing OSI network.
Planning Your Network Determine the Services Required Determine the Services Required The first step in planning your network is to identify what communication problems you are trying to solve and what OSI service or services best address your needs. This section describes each service provided by Hewlett-Packard and when it may be appropriate for meeting your communication needs. X.
Planning Your Network Determine the Services Required • Can act as a requestor of operations against a resource (a manager), or only as a responder to such requests (an agent), or both. • Provides a programmatic interface to CMIS, which allows you to write applications acting as either a requestor or a responder. FTAM Services Type of Service File Transfer Use if: You wish to move or manage files across an OSI network. • Allows transfer of files across an OSI network.
Planning Your Network Determine the Services Required High Availability Service Type of Service Create and manage highly available clusters Use if: You wish to create and manage highly available enterprise clusters of HP9000 Series 800 computers using the HP MC/ServiceGuard product. • Allows you to group programs in “packages” which run on particular nodes. • Monitors the health of your SPU, LAN cards, and application “packages” on each node.
Planning Your Network Determine the Vendors Involved Determine the Vendors Involved Another factor in determining the ultimate layout of your network is the equipment various vendors use to communicate. Not all vendors provide every OSI service. A given vendor may only provide some subset of functionality for a given layer. For example, HP does not currently provide the Virtual Terminal service. Another vendor may not provide X.500.
Planning Your Network Determine the Vendors Involved Verify that the underlying layers are compatible. The primary considerations are Session version and functional units, Transport Layer class, Network Layer protocol and link type. For more detailed questions about the links used, see “General LAN Questions” and “General X.25 Questions.
Planning Your Network General LAN Questions General LAN Questions • Is ES/IS (end system/intermediate system) protocol supported? Most systems today support the ES/IS protocol. This protocol allows systems to dynamically maintain information about the NSAP to MAC address mapping for systems on a LAN. By using this protocol, a great deal of configuration can be avoided.
Planning Your Network General X.25 Questions General X.25 Questions • Is ISO 8878 behavior supported? ISO 8878 defines how X.25 is to be used to provide CONS. Among other features: • It defines a mechanism for conveying NSAPs in 1984 and 1988 X.25 CALL packets. OTS supports full 8878 by default. • Defines a “special” mechanism, called SNDCP, which simulates this behavior on 1980 X.25 networks. Many OSI implementations do not support the SNDCP behavior.
Planning Your Network General X.25 Questions By default, OTS will also accept call packets with either the OSI or NULL PID values. Setting the “snet_bind_by_pid” parameter in the “ots_subnets” file will prevent OTS from accepting CALL requests using the NULL. If set, OTS will refuse calls with a PID other than the OSI standard PID.
Planning Your Network Determine the Network Structure Determine the Network Structure At this point, you have identified the nodes and the services you will be using for your network. The next step is to draw a network map to visualize the structure of your network. If this is an addition to an existing network, update the existing network map, otherwise, follow these steps to draw your map. A simple example of a network map is shown below. • Identify the subnetworks and nodes in your network.
Planning Your Network Determine the Network Structure NOTE Information beyond the node name, such as X.25 subaddresses, network addresses, and applications, can be kept separately by making copies of the “Remote System Worksheet.” See chapter 4, “Gathering Configuration Information.” Determine the Addressing Scheme Network Address At this point, you have determined the layout of your network. Now develop an addressing scheme that facilitates routing in your existing network, as well as future expansion.
Planning Your Network Determine the Network Structure After you have done the partition into domains and areas, you can then assign an appropriate network address prefix for each node, and the full address can be completed by using each node’s End System address. Application Addresses You may also want to dictate the selector values to be used for the upper layer addresses. (Note that HP OSI services use default addresses. For instance, FTAM uses 0x0001 (hex) for P-, S-, and T- selectors. X.
Planning Your Network Determine the Network Structure As an example, you might decide that the Country attribute will not be used, the Organization attribute will always be your company’s name in all lower case, and the Organization Unit will correspond to the node name given on the network map in all lower case. See the discussion of naming in the configuration manuals for the respective services for more information about what attribute classes are available and which ones are required.
Planning Your Network Gather and Distribute Configuration Information Gather and Distribute Configuration Information Now that you have determined the network topology and addressing scheme for your network, you are ready to compile the configuration information required for each system so that they may communicate with one another. HP has provided a worksheet for gathering information about each node on the network. It is contained in chapter 4, “Gathering Configuration Information.
Planning Your Network Gather and Distribute Configuration Information 82 Chapter 2
3 Gathering Configuration Information A discussion on collecting information to configure local nodes.
Gathering Configuration Information A Map to the Data Gathering Process A Map to the Data Gathering Process Before starting your data gathering, see chapter 3, “Planning Your Network.” Once your network is planned: • Make copies of the Remote System Worksheet, one for your local node and others to distribute to the other nodes on the network. • Make copies of your completed local node Remote System Worksheet to distribute to each of the other nodes you will communicate with.
Gathering Configuration Information A Map to the Data Gathering Process nodes need to know information about your local node, it is advisable to fill out a Remote System Worksheet for you node and send a copy of it along with blank worksheets to the remote nodes. • Local Parameter Worksheet. This worksheet is designed to help you collect the information you need to configure your local node. One of these worksheets is needed for every subnetwork you configure.
Gathering Configuration Information Using the Remote System Worksheet Using the Remote System Worksheet The Remote System Worksheet should be filled out for every OSI system you intend to connect to. This INCLUDES your local node. This worksheet represents parts of the OSI stack. The information is broken into six different sections. These six sections (described below) should be filled out by the network administrator for each remote node.
Gathering Configuration Information Using the Remote System Worksheet Subnetwork Addresses The subnetwork information is typically transparent to the end user, because the Network Layer (CONS or CLNS) determines this information from the NSAP. In some cases, this mapping must be configured on the system which is why this information is requested. If you have multiple X.25 or LAN cards, use additional worksheets. NSel The Network layer selector (typically 0x01).
Gathering Configuration Information Using the Remote System Worksheet ISO 8878 Support This indicates whether the remote supports the use of the X.25 extended addressing facility, as prescribed by ISO 8878 (Use of X.25 to provide CONS). Systems that do not use this facility should have their NSAP match their X.25 address (X.121 + Subaddress). Accept Reverse Charging If true, the vendor allows the call charges to be billed “collect.” Typically this is set to “N”. X.25 Standard This indicates which X.
Gathering Configuration Information Using the Remote System Worksheet Network Addresses (NSAPs) The last items you should provide are the Network Addresses (sometimes referred to as NSAPs) that are used to access this system. The full NSAP should be specified here if the remote configures the Network Address in components (IDP, DSP), or does not include the NSEL. These values should all be concatenated and written in the appropriate field. RFC1006 NSAP and IP Address OSI uses NSAP network addresses.
Gathering Configuration Information Using the Remote System Worksheet Address Header IP Address Port # (optional) 540072872203 123055077005 00103F If you use the standard NSAP address header, but an invalid IP address, the NSAP address is unreachable. RFC1006 Addressing Considerations • When addressing a remote, always use the remote’s IP address to construct the destination NSAP.
Gathering Configuration Information Remote System Worksheet Remote System Worksheet A blank Remote System Worksheet is shown below (in the next two graphics). You can print it and use it for your actual worksheet. General Information Node Name Vendor/Type Routing Info (Check one): ES________ IS________ Both __________ Application Addresses Appl Name Service P-selector S-selector T-selector Subnetwork Addresses NSel CONS Subaddr CLNS Subaddr X.121 802.
Gathering Configuration Information Remote System Worksheet LAN/X.25 Subnetwork Information X.25 Subnet information LAN Subnet Information ISO 8878 Support (y/n): CLNP Subset (check one): NULL____ Non-segmenting____ Full ____ Accept Reverse Charging (y/n): ES/IS Supported (y/n): X.25 standard (check one): 1980____ 1984____ 1988 ____ NSAPs Include NODE if used as part of the NSAP NSAP of 802.3 NSAP of FDDI NSAP of CONS/X.25 NSAP of CLNS/X.
Gathering Configuration Information Using the Local Parameter Worksheet Using the Local Parameter Worksheet Fill out a Local Parameter Worksheet for each subnetwork. Some of the information you collected on the Remote System Worksheet will be repeated here. Local Worksheet Organization Information on the Local Parameter Worksheet is organized as follows: General subnetwork information Lines 1 through 4 X.
Gathering Configuration Information Using the Local Parameter Worksheet Local Parameter Worksheet Fields The following information describes each field on the Local Parameter Worksheet. Subnetwork Name OTS uses a symbolic name you define to refer to each subnetwork. Use a name that is meaningful to you (for example, fddilan, site_8023, transpac). Local NSAP This value defines the NSAP (network address) that other systems on the network will use when establishing connections to your system.
Gathering Configuration Information Using the Local Parameter Worksheet X.25 If this subnetwork uses the X.25 link, then regardless of whether CONS or CLNS is used, you must provide the information requested. Specifically, indicate all the X.25 cards being used and a subaddress value (or the keyword NULL). At least one subaddress/programmatic access pair is required. Each card is identified by its programmatic access name. The programmatic access name is determined by the X.25 link configuration.
Gathering Configuration Information Using the Local Parameter Worksheet Device Interface Name For LAN-based subnetworks, you need to provide the device interface name for the card. This is not necessarily the same as the device file name. Typically, the interface name will be “lanx” where x is the logical unit number or the select code. To view existing LAN card interface names, run the utility lanscan(1M). The encapsulation method must be IEEE802.3 to allow OSI to run over an 802.3 LAN.
Gathering Configuration Information Using the Local Parameter Worksheet The Next Steps • Collect all Remote System Worksheets. • Collect Local Parameter Worksheet for each subnetwork. • Install OTS, if not already done. • Start configuring OTS.
Gathering Configuration Information Local Parameter Worksheet Local Parameter Worksheet Use this worksheet (shown in the next two graphics) to collect information you will need to configure your local network node parameters. One worksheet is required for each subnetwork. 1. Subnetwork name: ________________________________________ 2. Local NSAP: _____________________________________________ 3. Local Network ID (optional): _________________________________ 4.
Gathering Configuration Information Local Parameter Worksheet 9. Routing information Supply the full NSAP or a network ID (NSAP Prefix common to a group of destination NSAPs), and the NSAP of the intermediate system that will act as the router for the specified destinations.
Gathering Configuration Information Local Parameter Worksheet 100 Chapter 3
4 Installing HP OTS/9000 This chapter contains the step-by-step instructions for installing HP OTS/9000.
Installing HP OTS/9000 Installing HP OTS/9000 Installing HP OTS/9000 HP software, including HP OTS/9000, is installed using the swinstall program. If you’re installing software for the entire OSI stack, you should have already installed and configured any link products (for example, LAN or X.25) for your network. If the procedures to install the link components have not been completed, please complete them before proceeding with configuration.
Installing HP OTS/9000 Hardware and Software Requirements Hardware and Software Requirements Before installing or updating HP OTS/9000 (version C.07.00), you must have the following hardware and software components installed and operational. Hardware You must have the following hardware installed and operational. • HP9000 Series 800.
Installing HP OTS/9000 Hardware and Software Requirements • Networking link products, for example, HP LAN/9000, HP FDDI/9000, and HP X.25 products (and TCP/IP if you’re using the RFC1006 component of HP OTS/ 9000).
Installing HP OTS/9000 Installation Procedures Installation Procedures This section outlines the procedure for installing HP OTS/9000 on HP-UX release 10.30 using the SD utility swinstall. These instructions are for a new installation of OTS or on an existing 9.0 system on which HP-UX 10.x has been cold-installed. Either a LAN, FDDI, or X.25 link must also be installed and configured.
Installing HP OTS/9000 If Not On HP-UX 10. 30 If Not On HP-UX 10. 30 If you already have an HP-UX 9.x system running HP OTS/9000 and would be installing 10.30 or later on your system, you will need to backup your configuration and data files before cold-installing 10.x on your system. The configuration files for HP OTS/9000 on a 9.x system reside in the directory /etc/net/osi/conf. Backup all the files in this directory before installing 10.30. 1. Install HP-UX 10.x on your system.
Installing HP OTS/9000 To Add a New Link to HP OTS/9000 for Series 700/800 To Add a New Link to HP OTS/9000 for Series 700/800 If you want to add a new type of link to your system after the OTS product has been installed, and you have not configured your system for that type of link, follow these instructions. For example, your kernel is configured for LAN links only and you want to add an X.25 link. 1.
Installing HP OTS/9000 Installing HP OTS/9000 Software Installing HP OTS/9000 Software NOTE If your system is running HP-UX 10.01 or later, follow the instructions in “Installing and Upgrading HP OTS/9000 from HP-UX 10.01 or Later.” If your system is running HP-UX 9.x, follow the instructions in “Installing and Upgrading HP OTS/9000 from HP-UX 9.x.” On HP-UX 10.x systems, HP OTS/9000 is installed using the Software Distribution utility swinstall(1M).
Installing HP OTS/9000 Installing HP OTS/9000 Software When you mark the HP OTS/9000 software for installation you may see the following error message: The software “32070A,r=C.xx.xx,a=HPUX_B.10.xx_800,v=HP” refers to a bundle or to a product, subproduct or filesets within a bundle. The software specified was selected but there were problems selecting software that depends on it. The messages below show which items experienced these difficulties: The software “OTS9000,r=C.xx.xx,a=HPUX_B.10.
Installing HP OTS/9000 Installing HP OTS/9000 Software 10. Activate the OK button on the Note Window to reboot. The user interface disappears and the system reboots. 11. Once the system comes back up, log in as root and view the /var/adm/sw/swagent.log and /var/adm/sw/swinstall.log files to view any error or warning messages that may have occurred during the installation. 12. If this is a new installation, go to the chapter “Configuring and Verifying OTS/ 9000” in this manual. 13.
Installing HP OTS/9000 Installing HP OTS/9000 Software Continue with the upgrade. If, after upgrading your networking products, you still receive a startup failure for networking, use the lanscan command to verify the configuration in SAM and view the /etc/rc.log file for any failure statements. Also note the following: • Upgrade to HP-UX operating system version 10.01 and then to the latest version of HP-UX ONLY when compatible networking products are available.
Installing HP OTS/9000 Installing HP OTS/9000 Software 2. Upgrade HP-UX 10.01 to the latest version. Also upgrade applications to the latest versions; this includes upgrading OTS C.05.02 to the latest version. Refer to “Installing and Upgrading HP OTS/9000 from HP-UX 10.01” in this document. Upgrade from HP-UX 9.x to 10.01 Use the Upgrading from HP-UX 9.x to 10.x manual as the guide to upgrade HP-UX 9.x to 10.01. After you have upgraded HP-UX to 10.01, upgrade HP OTS/9000 to the 10.
Installing HP OTS/9000 Installing HP OTS/9000 Software will be modified depending on the conversions that happen during the LAN link upgrade. 5. If you have HP OTS/9000 configured over X.25 prior to the upgrade, the HP OTS/9000 upgrade may not include the driver required for running HP OTS/9000 over X.25 in the kernel. HP OTS/9000 may have to be reinstalled after the system has been upgraded and after making sure that the X.25 product has been installed and configured.
Installing HP OTS/9000 Installing HP OTS/9000 Software 6. Modify any entries to correct configuration discrepancies. Save the changes and exit osiadmin, reboot your system, and perform the verification steps described in the chapter “Configuring and Verifying HP OTS/9000” in this manual. You are done when you can successfully perform the verification steps.
Installing HP OTS/9000 De-installing HP OTS/9000 De-installing HP OTS/9000 On HP-UX 10.x systems, HP OTS/9000 can be de-installed using the Software Distribution utility swremove(1M). All HP OTS/9000 filesets, including the kernel fileset OTS-KRN, are now removable. swremove will remove the filesets, regenerate the kernel, then reboot the system.
Installing HP OTS/9000 De-installing HP OTS/9000 116 Chapter 4
5 Configuring and Verifying HP OTS/9000 This chapter contains step-by-step instructions for configuring and verifying HP OTS/9000.
Configuring and Verifying HP OTS/9000 Configuring and Verifying HP OTS/9000 Configuring and Verifying HP OTS/9000 At this point you should have completed the following tasks.
Configuring and Verifying HP OTS/9000 Configuring and Verifying HP OTS/9000 Figure 5-1 OTS Configuration Collect Appropriate Worksheets Verify that All Appropriate Software is Installed Verify that Link Layer is Installed Verify that Kernel is Correctly Configured Preparation Configuration Save Worksheets for your Records 1 Configure Using osiadmin Screens 2 Start OTS 3 Verify OTS Configuration Verify OTS 4 Interoperability Services Configure Service Level Components Chapter 5 Verify Servic
Configuring and Verifying HP OTS/9000 Configuring and Verifying HP OTS/9000 Overview of HP OTS/9000 Configuration • Start configuration by adding /opt/ots/bin and /opt/ots/man to your system path. This will save you some typing later. • Run the osiadmin program. This program calls up the osiconf program to do the OTS configuration tasks. When configuration is complete, you return to osiadmin. See “Finding Your Way Through OTS Configuration” for which configuration screens you’ll use.
Configuring and Verifying HP OTS/9000 Configuring and Verifying HP OTS/9000 Figure 5-2 Finding Your Way Through OTS Configuration OTS Menu osiadmin RFC1006 Configure OSI over TCP/IP OTS Configure osiconf Configure LAN Go to Add RFC1006 screen Configure X.25 Yes Go to Add CLNS over 802.3 screen No No FDDI? Go to Add CONS over X.25 screen CLNS? Yes Go to Add CLNS over FDDI LAN screen Go to Add CLNS over X.
Configuring and Verifying HP OTS/9000 To Configure HP OTS/9000 To Configure HP OTS/9000 1. Log in as root, then add /opt/ots/bin and /opt/ots/man to your system path. 2. At the system prompt, type osiadmin, then press [return]. 3. Highlight “OTS” and press “Select Item” or [return]. 4. Highlight “Configure OTS” and press “Select Item” or [return]. 5. Select the configuration mode and the file set (or accept the defaults shown) and press “Done.
Configuring and Verifying HP OTS/9000 To Configure RFC1006 To Configure RFC1006 RFC1006 is configured using the osiadmin tool. HP OTS /9000 does not have to be configured. TCP/IP and the appropriate links must already be configured. You will need your local IP Address for step 5. 1. Type osiadmin to start the configuration. The first screen presented to you is the osiadmin Main Menu. 2. Select “OTS” since the RFC1006 is part of the OTS product. 3.
Configuring and Verifying HP OTS/9000 To Add HP OTS/9000 CLNS Over 802.3 or FDDI LAN To Add HP OTS/9000 CLNS Over 802.3 or FDDI LAN 1. Under CLNS over 802.3 or CLNS over FDDI LAN, highlight “Add” and press “Select Item” or [return]. If you selected 802.3, the CLNS over 802.3 screen appears. If you selected FDDI, the CLNS over FDDI screen appears. 2. Enter the following parameters from your Local Parameter Worksheet for this subnetwork. a. Enter the Subnetwork Name from line 1. b.
Configuring and Verifying HP OTS/9000 To Add HP OTS/9000 CLNS Over X.25 To Add HP OTS/9000 CLNS Over X.25 1. Under CLNS over X.25 highlight “Add” and press “Select Item” or [return]. 2. Enter the following parameters from your Local Parameter Worksheet for this subnetwork. a. Enter the Subnetwork Name from line 1. b. Enter a Network ID, if applicable, from line 3. c. Enter Local Network Address (NSAP) from line 2. d. Enter Subaddress and X.25 Programmatic Access Name from line 5.
Configuring and Verifying HP OTS/9000 To Add HP OTS/9000 CONS Over X.25 To Add HP OTS/9000 CONS Over X.25 1. Under CONS over X.25 highlight “Add” and press “Select Item” or [return]. 2. Enter the following parameters from your Local Parameter Worksheet for this subnetwork. a. Enter the Subnetwork Name from line 1. b. Enter Local Network Address (NSAP) from line 2. c. Enter Y(es) for each applicable Subnetwork Standard from line 6. (ISO 8878 must be Y or N. At least one of the following must be Y: X.
Configuring and Verifying HP OTS/9000 To Add HP OTS/9000 Destination System To Add HP OTS/9000 Destination System 1. Select “Add” under Destination Systems on the OTS Configuration menu. 2. Enter the following parameters from your Remote System Worksheet. (One for each remote node to be configured.) a. Network Address (NSAP of destination system from the NSAPs box). b. Physical Address (If X.25, use the combination of any X.121 address concatenated with the subaddress.
Configuring and Verifying HP OTS/9000 To Add HP OTS/9000 Destination System An Outgoing Subnetwork Name Example If you named your X.25 CLNS subnetwork “x25clns” and this is the configuration for a remote reachable over X.25 CLNS, enter “x25clns” as the outgoing subnetwork name.
Configuring and Verifying HP OTS/9000 To Add an HP OTS/9000 Route To Add an HP OTS/9000 Route 1. Select “Add” under Routes on the OTS Configuration menu. 2. Enter the following parameters from your Local Parameter Worksheet for this subnetwork. a. Enter Network ID or Network Address (NSAP) from line 9. b. Enter Outgoing Subnetwork Name from line 1. c. Enter Primary Route NSAP from line 9. 3. Press “Perform Task” f4. You will see a pop-up screen displaying “Task completed...” 4.
Configuring and Verifying HP OTS/9000 To Start HP OTS/9000 To Start HP OTS/9000 1. Press “Exit Task” f8 until you are back on the OTS Menu. 2. Highlight “Start OTS” and press “Select Item” or [return]. This takes a few moments. You will see messages flashing on your screen as OTS verifies that the links are running and then starts itself. 3. Press [return] to continue. NOTE You only need to use the start option after initial configuration. OTS is automatically started by /sbin/rcz.
Configuring and Verifying HP OTS/9000 To Update HP OTS/9000 To Update HP OTS/9000 1. Press “Exit Task” f8 until you are back on the OTS Menu. 2. Highlight “Update OTS” and press “Select Item” or [return]. This takes a few moments. You will see messages flashing on your screen as OTS verifies that the links are running and then updates. 3. Press [return] to continue. You may update HP OTS/9000 if: • HP OTS/9000 is already running AND • Only dynamic parameters have been changed since the stack was started.
Configuring and Verifying HP OTS/9000 To Verify HP OTS/9000 Configuration To Verify HP OTS/9000 Configuration 1. Make sure the stack is started. 2. From the OTS menu in osiadmin, highlight “Test Connectivity” and press “Select Item” or [return]. 3. Highlight “Transport Tests” on the OSI Diagnostics main menu and press “Select Item”. 4. Highlight “Loopback” on the Transport Test Cases Menu and press “Select Item” or [return]. A window titled “Transport Destination TSAP” will appear.
6 HP OTS/9000 Configuration Files This chapter describes the HP OTS/9000 configuration files.
HP OTS/9000 Configuration Files About the Configuration Files About the Configuration Files The OTS/9000 configuration files are standard ASCII files. For a new installation, they are copied from /opt/ots/newconfig to /etc/opt/ots/conf. This is accomplished when swinstall runs during the installation. You can reset the configuration to its original (installed) condition by copying the needed files from opt/ots/newconfig. This erases prior configuration and customization.
HP OTS/9000 Configuration Files About the Configuration Files # #--------------------------------------------------------1 # Guidelines: # # The4 parameters route_id, route_id_mask,route_out_subnet, # & route_primary are grouped together, route_id must appear # first in each group.
HP OTS/9000 Configuration Files Configuration Files and the config_parms.txt File Configuration Files and the config_parms.txt File The most efficient way to configure HP OTS/9000 is by using the worksheets in chapter 4, “Gathering Configuration Information,” of this manual and the osiadmin facility. Using these will enable you to configure the minimum set of parameters.
HP OTS/9000 Configuration Files Configuration Files and the config_parms.txt File NOTE Although you can change the configuration files while HP OTS/9000 is running, only parameters that are listed as being dynamic can be changed without requiring a system reboot. The otsupdate command must be used to invoke these dynamic changes. See the section “To Update HP OTS/9000” in chapter 5 for more information. Steps for Changing Parameter Values 1.
HP OTS/9000 Configuration Files Multiple Configuration Sets Multiple Configuration Sets The nodal management tools can work with configuration files sets residing in directories other than the default directory /etc/opt/ots/conf. This is limited to the creation and management of files sets on the local node only. There is no limit to the number of sets that can exist, but each file set must contain a complete set of configuration files.
HP OTS/9000 Configuration Files To Create A New File Set To Create A New File Set To create and activate a new file set, use the following sequence of commands as an example. $ mkdir /tmp/myconfig $ cp /usr/opt/ots/newconfig/ * /tmp/myconfig $ ls /tmp/myconfig ap_user_app local_app ots_genrl ots_subnets o ts-parms remote_app ftam_parms ots_dests ots_routes $ OSI_CONFIG=/tmp/myconfig $ export OSI_CONFIG $ osiadmin From osiadmin you can modify the new active file sets.
HP OTS/9000 Configuration Files To Create A New File Set Figure 6-1 Multiple Configuration Sets osiadmin 1 osiconf osiconfchk 2 OSI_CONFIG or default directory Active Configuration File set Alternate Configuration File Set 1 oo Alternate Configuration File Set 2 otsstart 3 and otsupdate Configuration 4 Snapshot OSI Stack and Services 140 Chapter 6
HP OTS/9000 Configuration Files To Create A New File Set Multiple Configuration Diagram The following numbers refer to “Multiple Configuration Sets.” 1. The OTS tools (osiadmin, osiconf, osiconfchk), by default, manipulate the active configuration file set. They can also manipulate alternate configuration files sets which are not active. 2. The active configuration files set can reside in any directory.
HP OTS/9000 Configuration Files To Create A New File Set where is may read or write configuration information. This means that you can also select a file set that is not active and configure it. To select an alternate file set, enter the directory into the “Configuration File Set Path” field on the “Set Configuration Mode” pop-up screen. When working with an alternate file set, osiconf will prompt you to enable or disable the local parameter checks.
Glossary ACSE/Presentation and ROSE Interface See APRI Advanced Research Projects Agency See ARPA ANSI The American National Standards Institute that publishes standards for use by national industries. backbone The principal network segment to which all nodes are connected, or to which other segments are connected. BAS This subset is used with basic X.400 application and Session version 1.
Glossary CCITT Consultative Committee for International Telegraphy and Telephony. An international organization of communication carriers. CLNP subset Indicates the LAN subnetwork information. CLNS Connectionless-oriented network services. common management information service (CMIS) The interface for development of network management applications. CONS Connection-oriented network services. command A word or phrase that you type at the system prompt to carry out an action when you press the ENTER key.
Glossary Ethernet A 10 Mb/s LAN, developed by Digital Equipment Corporation, Intel, and Xerox Corporation, upon which the IEEE 802.3 network is based. GOSIP Government OSI Profile. An OSI-based network protocol used by governments (for example, the United States and United Kingdom). FDDI A specification for a fiberoptic ring network featuring a link speed of 100 Mb/s and fault tolerant capabilities.
Glossary ISO The International Standards Organization that created a network model identifying the seven commonly-used protocol levels for networking. MAC The ANSI FDDI standard that defines the data link layer function responsible for the scheduling, routing and delivery of frames on and off the FDDI ring. kernel The part of the HP-UX operating system that is an executable piece of code responsible for managing the computer’s resources.
Glossary NSAP A unique value that defines a system’s address for use when establishing network connections among various systems. open system interconnection See OSI OSI Open System Interconnection reference model defined by the International Standards Organization (ISO). It establishes a data communication architectural model for networks. OTS HP’s term for the OSI transport services. protocol A specification for transferring information between computers on a network. redundancy Duplication of service.
Glossary SAS A station in an FDDI network that connects to only one of the two FDDI network rings. An SAS must attach to the network through a concentrator. session interface An application program interface to the OSI session layer. single attachment station See SAS SMT The ANSI FDDI standard which manages connections with the ring as well as station and ring configuration.
Index Symbols /dev/osipi, 29 /etc/net/osi/conf, 134 /etc/net/osi/conf/template, 134 Numerics 1984 X.25, 30 A ACSE/Presentation layer functionality, 30 adding a destination system, 127 a route, 129 CLNS over 802.3 LAN, 124 CLNS over X.25, 125 CONS over X.25, 126 new link to OTS - series 800, 107 addresses extended, 39 system, 38 addressing, 42 determining the scheme, 78 planning application, 79 administrative prefix AP, 50 AFI, 49 AFNOR format NSAP, 55 ANSI format NSAP, 54 AP, 50 temporary, 60 using an X.
Index ACSE/Presentation layer, 30 session layer, 31 transport, 32 G GOSIP United Kingdom, 57 United States NSAP, 56 Government Open Systems Interconnection Profile GOSIP, 56 H hardware requirements, 103 how OTS/9000 uses X.25, 38 how to add a destination system, 127 add a route, 129 add CLNS over 802.3 LAN, 124 add CLNS over X.25, 125 add CONS over X.25, 126 configure OTS, 122 configure RFC1006, 123 start OTS, 130 update OTS, 131 upgrade OTS from HP-UX 10.
Index additional reference documents, 47 addresses, 47 AFNOR format, 55 allocation formats, 54 ANSI format, 54 domain specific part, 49 example of RFC1006, 89 initial domain part, 48 non-standard, 66 recommendations, 65 RFC1006, 89 selector, 52 syntax, 48 United Kingdom GOSIP, 57 United States GOSIP, 56 with CLNP, 66 with CONS, 66 NSel, 58, 63 null X.25 subaddresses, 38 O Omicom, Inc.
Index XTI, 71 Port ID, 41 presentation address P-address, 42 presentation selector P-selector, 41 privately allocated part PAP, 50 protocol identifiers, 39 P-selector, 41 PVC permanent virtual circuit, 38 R recommended PAP structure, 63 remote end system how OTS finds a, 33 remote system worksheet, 91 application addresses, 86 general information, 86 LAN subnetwork, 88 NSAPs, 89 subnetwork addresses, 87 using, 86 X.
Index using local parameter, 93 using remote system, 86 X X.121 address, 44 X.25 establishing connections, 38 general questions, 75 installed over OTS, 108 null subaddresses, 38 planning, 75 X.400 planning, 69 XPG.
