Managing SunLink FTAM 8.0.2

Transcription

1 Managing SunLink FTAM A Sun Microsystems, Inc. Business 2550 Garcia Avenue Mountain View, CA U.S.A. Part No: Revision A, October 1994

2 1994 Sun Microsystems, Inc Garcia Avenue, Mountain View, California U.S.A. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX and Berkeley 4.3 BSD systems, licensed from UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and the University of California, respectively. Third-party font software in this product is protected by copyright and licensed from Sun s font suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, the Sun logo, Sun Microsystems, Solaris and SunLink are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and certain other countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademark of Novell, Inc. PostScript and Display PostScript are trademarks of Adobe Systems, Inc. All other product names mentioned herein are the trademarks of their respective owners. All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International, Inc. SPARCstation, SPARCserver, SPARCengine, SPARCstorage, SPARCware, SPARCcenter, SPARCclassic, SPARCcluster, SPARCdesign, SPARC811, SPARCprinter, UltraSPARC, microsparc, SPARCworks, and SPARCompiler are licensed exclusively to Sun Microsystems, Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun s written license agreements. X Window System is a product of the Massachusetts Institute of Technology. THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME. Please Recycle

3 Contents Part 1 Setting up and Maintaining SunLink FTAM 1. Introducing SunLink FTAM FTAM Specifications SunLink FTAM Architecture Overview SunLink FTAM Concepts and Terminology Virtual File Store Document Types File Attributes Functional Units and Service Classes Shadow Files Shadow File Templates Recovery Access Restriction DR SunLink FTAM Directories and Files iii

4 2. Planning your SunLink FTAM Configuration Example Configurations Exchanging Files between Remote Systems Sharing a Local File Server Interoperating with Other Implementations of FTAM Configuring SunLink FTAM Overview Starting ftamtool Staring ftamtool Locally Starting ftamtool Remotely Creating a Remote Systems Database (RSDB) Adding an Entry to the RSDB Modifying an Existing Template Adding a Completely New Entry Deleting an Entry from the RSDB Printing the RSDB Closing and Opening Systems Configuring the Local Initiator Modifying the Default Initiator Configuration Saving the Initiator Configuration Printing the Initiator Configuration Configuring the Local Responder Modifying the Default Responder Configuration Saving the Responder Configuration iv Managing SunLink FTAM October 1994

5 Printing the Responder Configuration Using the FTAM Responder (osiftr) Starting and Stopping the FTAM Responder Daemon Starting Responder Daemon Automatically Starting the Responder Daemon Manually Stopping the Responder Daemon Manually Restricting Remote Access Troubleshooting Problems Opening a Connection Interoperability Problems SunLink FTAM initiator and non-sun Responder Non-Sun Initiator and SunLink FTAM Responder Problems with Licensing Problems Starting the License Installation Tool Unable to Change License Server(s) Mistyped License Information Errors Executing the License Configuration Script Removing the License System Recovering a Lost License Unlocking a Stopped License System SunLink OSI Specific Errors Part 2 Reference 6. SunLink FTAM Parameters Remote Systems Database Parameters Contents v

6 RSDB Templates Current System Name Application Process Title Application Process Qualifier Presentation Selector (PSEL) Session Selector (SSEL) Transport Selector (TSEL) Network Address Network Access System Status Local Initiator and Responder Parameters Supported Service Classes Functional Units New OID for NBS DR Traces Error Messages and Codes Primary Error Messages Local Error Codes Diagnostic Error Codes General FTAM Diagnostics Protocol and Supporting Service Diagnostics Association-Related Diagnostics Selection Regime-Related Diagnostics vi Managing SunLink FTAM October 1994

7 File Management-Related Diagnostics Access-Related Diagnostics Recovery-Related Diagnostics FTAM Trace Files Trace Format Trace Example A. SunLink FTAM Command Summary B. Configuring the RSDB without ftamtool rdb add add remote system rdb change change remote system rdb close close remote system rdb delete delete remote system rdb list list remote system database rdb open open remote system rdb show show remote host address Contents vii

8 viii Managing SunLink FTAM October 1994

9 Preface Purpose and Audience Before You Read This Book This manual describes how to configure SunLink FTAM so that it can transfer, access, and manage files between two communicating systems, through a userinterface that resembles the UNIX command ftp(1). It is intended for system administrators familiar with the SunOS operating system and OPEN LOOK graphical user interfaces. You must install and configure the SunLink OSI Communications Platform (Stack) in order to use SunLink FTAM. Before reading this manual, refer to: SunLink OSI Communication Platform Administrator s Guide (Part No ) ix

10 How This Book Is Organized Part 1, Setting up and Maintaining SunLink FTAM. Chapter 1, Introducing SunLink FTAM, provides an overview of the SunLink FTAM software architecture and the related FTAM protocols. Chapter 2, Planning your SunLink FTAM Configuration, makes some suggestions for planning your configuration, and provides information about interoperating with other vendors products. Chapter 3, Configuring SunLink FTAM, describes how to use the OPEN LOOK graphical user interface for SunLink FTAM (ftamtool) to set up a list of recognized systems and to configure the initiator and responder portions of SunLink FTAM. Chapter 4, Using the FTAM Responder (osiftr), describes how to start the SunLink FTAM responder (osiftam) on a remote system. Chapter 5, Troubleshooting, provides some tips for resolving common problems with SunLink FTAM and the licensing system. Part 2, Reference. Conventions Used in this Manual Chapter 6, SunLink FTAM Parameters, is a reference section, giving detailed information about available parameters. Chapter 7, Error Messages and Codes, is a reference section, giving an alphabetical list of error messages and error codes, together with some suggested remedies. Chapter 8, FTAM Trace Files, describes the use and format of FTAM trace files which are used to log an FTAM session. Appendix A, SunLink FTAM Command Summary, is an alphabetical list of the available FTAM Initiator commands. Appendix B, Configuring the RSDB without ftamtool, describes the commands that add entries to the RSDB, without using ftamtool. The following typographic conventions are used in this manual: x Managing SunLink FTAM October 1994

11 Typewriter font Represents what appears on your workstation screen and is used for program names, file names, and UNIX commands. Boldface typewriter font Indicates user input, commands and responses to prompts that you type in exactly as they appear in the manual. Italic font Indicates variables or parameters that you replace with an appropriate word or string; also used for emphasis. hostname% or % Represents the system s prompt for a non-privileged user s account. hostname# or # Represents the system s prompt for the root (superuser) account. Boxes Contain text that represents listings, part of a configuration file, or program output. Boxes are also used to represent interactive sessions. In this case, user input is indicated by boldface typewriter font. For example: % df -k /usr Filesystem kbytes used avail capacity Mounted on /dev/sd0g % /usr Product Documentation The other documents in the SunLink OSI documentation set are: Using SunLink FTAM (Part Number: ) SunLink FTAM Programmer s Guide (Part Number: ) xi

12 You may also need to refer to Getting Started with SunLink FTAM 8.0.2, which is delivered with the product CD-ROM. xii Managing SunLink FTAM October 1994

13 Part 1 Setting up and Maintaining SunLink FTAM

14

15 Introducing SunLink FTAM 1 FTAM Specifications page 1 SunLink FTAM Architecture Overview page 2 SunLink FTAM Concepts and Terminology page 4 SunLink FTAM Directories and Files page 12 SunLink FTAM is an implementation of the ISO FTAM protocols, that provides the feature-set defined in the US GOSIP requirements. It is used to transfer, access, and manage files between two communicating systems. This chapter provides a summary of the relevant ISO FTAM protocols and an overview of the SunLink FTAM concepts and architecture. FTAM Specifications The ISO FTAM specification (8571) defines a method of handling the transfer, access, and management of files between two communicating systems based on the principle of a virtual file store. The FTAM specification is divided into five parts: ISO 8571/1 Introduces FTAM concepts ISO 8571/2 Explains the terms, concepts, and vocabulary used by FTAM ISO 8571/3 Describes the two file transfer entities ISO 8571/4 Defines the rules applied to the transfer of files ISO 8571/5 Describes the conformance statement 1

16 1 SunLink FTAM Architecture Overview SunLink FTAM is an implementation of the ISO FTAM protocols. It is used to transfer, access, and manage files between two communicating systems through a user-interface that resembles the UNIX command ftp(1). It adheres to a client-server model (where the client system requests and receives services from a remote server) and consists of two parts osiftam and osiftr: The SunLink FTAM initiator (osiftam) is the client process. It resides on the local system and initiates connections (called associations) with remote systems running an FTAM server. The SunLink FTAM responder (osiftr) is the server process. It is launched by a daemon (osiftrd) each time an association request is received from an FTAM client such as the SunLink FTAM initiator (osiftam). There is one FTAM responder daemon (osiftrd) for each of the three subnetwork types supported by SunLink OSI (LAN, WAN, and TCP/IP). Figure 1-1 shows how an osiftrd daemon launches an osiftr process when it receives an association request from an FTAM client such as osiftam. command-line interface FTAM Responder (osiftr) FTAM Initiator (osiftam) daemon (osiftrd) User Space Kernel OSI STREAMS multiplexor Figure 1-1 Establishing an Association 2 Managing SunLink FTAM October 1994

17 1 The SunLink FTAM initiator (osiftam) is accessed through a simple command-line interface. In addition to file transfer facilities, SunLink FTAM supports extensive file access and management functions. Refer to Appendix A, SunLink FTAM Command Summary, for a comprehensive list of the osiftam commands. Each instance of the osiftam initiator manages one association at a time; however, the osiftrd daemon launches an osiftr responder process each time it receives an association request. In this way, the SunLink FTAM handles multiple concurrent associations as shown in Figure 1-2. Each instance of the osiftr responder remains active until the association is closed explicitly, using the close command, or it times out. command-line interface command-line interface FTAM Responder (osiftr) FTAM Responder (osiftr) FTAM Initiator (osiftam) FTAM Initiator (osiftam) daemon (osiftrd) User Space Kernel OSI STREAMS multiplexor Figure 1-2 Establishing Concurrent Associations Introducing SunLink FTAM 3

18 1 SunLink FTAM Concepts and Terminology The FTAM protocols describe a method of managing files between potentially diverse file systems based on the principle of a virtual file store, which maps different file systems to a common model. SunLink FTAM implements a virtual file store and the associated services used to access files remotely or to transfer files between systems. Virtual File Store The virtual file store defined by the FTAM protocols provides a mapping of the data and characteristics of a real file to a common model the virtual file. By describing only the virtual file store and not the files themselves, the FTAM protocols define a method of managing files between dissimilar environments. The concept of the FTAM virtual file store is illustrated in Figure 1-3. Real File System A Real File System B SunLink FTAM Environment FTAM Virtual File Store FTAM Virtual File Store FTAM Virtual File Store FTAM Virtual File Store Real File System D Real File System C Figure 1-3 FTAM Virtual File Store 4 Managing SunLink FTAM October 1994

19 1 Document Types The FTAM protocols define a small number of specific document types that describe a file based on a set of common attributes. This enables communicating systems to access files in a consistent manner. Three of the national standards committees ISO (International Standards Organization), NIST (US National Institute of Standards and Technology), and INTAP (Interoperability Technology Association for Information Processing, Japan) have cooperated to define the ten standard document types. Implementations of the FTAM protocols such as SunLink FTAM, support a subset of the ten defined document types. The document types supported by Sunlink FTAM are listed in Table 1-1: Table 1-1 Supported Document Types Document Type FTAM-1 FTAM-2 FTAM-3 NBS-9 INTAP-1 Description Unstructured text Sequential text Unstructured binary File directory INTAP records If a document type is not defined explicitly, files are assumed to be of document type FTAM-3 (unstructured binary). File Attributes File attributes describe the properties and characteristics of a file. The FTAM protocols define four groups of file attributes, of which SunLink FTAM supports the kernel group and the storage group: The kernel group consists of properties that are common to all files. For example, name, document type, access restrictions. The storage group consists of properties of files that are stored. For example, date and time last read, identification of creator. Introducing SunLink FTAM 5

20 1 Functional Units and Service Classes The FTAM architecture is described in terms of functional units and service classes. Functional units describe the services implemented by the FTAM protocols. The FTAM specification (ISO 8571/3) defines ten functional units; however, because common functional units are negotiated by the two communicating systems at the time an association is requested, implementations of the FTAM protocols do not need to support all of the functional units defined by the FTAM specification. The functional units supported by SunLink FTAM are listed in Table 1-2: Table 1-2 Supported Functional Units Code U1 U2 U3 Functional Unit Kernel Read Write U4 File Access (requires U2 or U3) U5 Limited File Management U6 Enhanced File Management (requires U5) U7 U9 Grouping Recovery Service classes are groups of functional units and are defined by the type of functional units they contain. The FTAM specification (ISO 8571/3) defines five service classes, of which SunLink FTAM supports the four classes listed in Table 1-3: Table 1-3 Code T A M TM Supported Service Classes Service Class Transfer class Access class Management class Transfer and Management class 6 Managing SunLink FTAM October 1994

21 1 Shadow Files Shadow files are special files that are specific to the SunLink FTAM implementation of the FTAM protocols. They are used to handle the FTAM file attributes that are not supported by the UNIX file system. Under most circumstances, shadow files are transparent to the user. The attributes maintained in the shadow file are: access permissions: Specifies the access permissions assigned to the associated file. These permissions can be overridden by setting the file permissions explicitly. r: read permission i: insert permission p: replace permission x: extend permission e: erase attributes permission t: read attributes permission c: change attributes permission d: delete permission document type: Specifies the FTAM document type for the associated file: F1: FTAM-1 unstructured text file F2: FTAM-2 sequential text file F3: FTAM-3 unstructured binary file I1: INTAP-1 record file universal class no: Universal Class Number. This is an integer value that specifies the content type (text, binary, etc.): 4: octet string 19: printable string Introducing SunLink FTAM 7

22 1 20: teletex string 21: videotex string 22: IA5 string 25: graphic string 26:visible string 27: general string string length: Integer value specifying the maximum string length. A value of zero specifies an unbounded string length. string significance: Specifies whether the string is of fixed length, variable length, or whether length is insignificant. f: fixed v:variable n: not significant A shadow file is created for each file that is managed using the Sunlink FTAM initiator and responder. A shadow file is created on a remote system when a file is created on it, or transferred to it. A shadow file is created on the local system when the get command is used to transfer a file onto it. Figure 1-4 on page 9 shows the how shadow files are created and transferred between local and remote systems. The shadow file is given the extension.shf and is paired with the original file as part of a single FTAM file entity. The shadow file is copied, renamed, and deleted in association with the original file for as long as the original file is managed using SunLink FTAM. However, if the original file is copied, renamed, or deleted with a UNIX command, or using any other FTAM application, the associated remote shadow file will remain on the system. You can display the attributes for a remote file, including the FTAM attributes contained in the remote shadow file using the ratt command. 8 Managing SunLink FTAM October 1994

23 1 local system remote system create file1 + file1.shf file1.shf + file1 get file1 + file1.shf file2.shf + file2 get file2 file3 put file3 + file3.shf file4.shf + file4 put file4 + file4.shf Figure 1-4 Shadow Files on Local and Remote Systems Shadow File Templates The attributes set in a shadow file are dependent on the document type of the original file. Unless specified otherwise, shadow files are created with the default values shown in Table 1-4: Table 1-4 Default Shadow File Attributes Document Type Permissions Universal Class No. String Length String Significance F1 r-pxetcd 25 0 (unbounded) v (variable) F2 ri--etcd 25 0 (unbounded) v (variable) F3 r-pxetcd 4 0 (unbounded) v (variable) I1 r-pxetcd v (variable) Shadow file templates are used to override the default attributes listed in Table 1-4 at the time the shadow file is created. Introducing SunLink FTAM 9

24 1 You can set different default attributes for each document type by creating a generic shadow file template using the shf command. If a generic shadow file exists for a given document type, it is used in preference to the default attributes listed in Table 1-4 on page 9. Generic shadow file templates are located in the directory /var/sunwconn/osiroot/ftam/shf and are named after the four document types as shown in Table 1-5: Table 1-5 Shadow File Templates Shadow File Templates /var/sunwconn/osiroot/ftam/shf/ftam1.shf /var/sunwconn/osiroot/ftam/shf/ftam2.shf /var/sunwconn/osiroot/ftam/shf/ftam3.shf /var/sunwconn/osiroot/ftam/shf/intap1.shf Document Type Used for FTAM-1 documents Used for FTAM-2 documents Used for FTAM-3 documents Used for INTAP-1 documents You can customize the attributes for an individual file by using the create command with the s option to specify a shadow file template. You can use the shadow file that is associated with an existing file as a shadow file template. You can also create a specific shadow file template using the shf command. Recovery The recovery mechanism runs provided that the recovery functional unit is supported by the FTAM applications running on both systems, and is negotiated at the time the association is established. This mechanism completes interrupted file transfers, without the need to repeat the transfer from the beginning. Recoverable errors are errors that temporarily interrupt the file transfer, for example, lack of disk space, congested network resources and network problems. The recovery mechanism can resume file transfers after the cause of the error has been resolved. Unrecoverable errors either prevent a file transfer from being started (for example, file does not exist) or interrupt the file transfer definitively (for example, unexpected end-of-file). File transfer cannot be resumed even if recovery is enabled. 10 Managing SunLink FTAM October 1994

25 1 The FTAM recovery mechanism relies upon the use of special files called dockets. There is a docket associated with the local and remote ends of each file transfer. Dockets contain synchronization information that records how much data has been sent, and how much data has been received. In the event of a recoverable error, any discrepancy that exists between the dockets (the amount of information sent and received) is used to calculate the amount of data that must be resent in order to guarantee that the transfer is completed successfully. Figure 1-5 illustrates the principle of the FTAM recovery mechanism. local system remote system put data sent lost data to be resent data received Figure 1-5 FTAM Error Recovery Mechanism Access Restriction Sunlink FTAM imposes a login procedure to restrict access to remote file systems. To access a file system on a remote system running the SunLink FTAM responder daemon (osiftrd), the operator s user name (login) and password must be entered in the /etc/passwd file on the remote system. hostname% /opt/sunwconn/bin/osiftam papyrus user name: <enter login> password: <enter password or press Return> account: <enter account or press Return> Refer to Using SunLink FTAM for more detailed information on logging in to remote systems using SunLink FTAM. Introducing SunLink FTAM 11

26 1 DR10 SunLink FTAM Directories and Files DR10, an addendum to ISO 8571, modifies the sequence of primitives returned on group error, and the associated diagnostics. Instead of generating a message for each primitive, a system using DR10 generates a single, group error message. DR10 can cause interoperability problems if only one end of a connection uses it. By default, SunLink FTAM does not use DR10. It is possible to enable it, to interoperate with an implementation of FTAM that does use it. There are five classes of dynamic files associated with SunLink FTAM. The environment variables that set the default location of these files are used by both the initiator and the responder. For example, if you define the variable FTIINID to be /home/user1, osiftam looks for the file /home/user1/fti.init on startup, and osiftr looks for /home/user1/ftr.init. The responder can only use variables that are defined in the root environment at startup, so, if you redefine the environment variable, you must stop and restart the osiftrd daemon. Configuration Files (/var/sunwconn/osiroot/ftam/conf/*.init) There is one configuration file associated with each part of the SunLink FTAM implementation. These files are modified using the OPEN LOOK graphical user interface for SunLink FTAM (ftamtool). The file fti.init is read each time the SunLink FTAM initiator (osiftam) is started. The file ftr.init is read each time the SunLink FTAM responder (osiftr) is started. The default location for these files can be changed by setting the environment variable FTIINID. 12 Managing SunLink FTAM October 1994

27 1 RSDB Files (/var/sunwconn/osiroot/ftam/rdb/*.rdb) The remote systems database contains a list of all the remote systems recognized by the SunLink FTAM initiator (osiftam). It consists of a directory containing a file entry that corresponds to each remote system in the database. The default location for these files can be changed by setting the environment variable FTIRDBD. Shadow Files (/var/sunwconn/osiroot/ftam/shf/*.shf) Shadow files are SunLink FTAM-specific files that are used to handle the FTAM attributes which are not supported by the UNIX file system. See Shadow Files on page 7 for more information. The default location for these files can be changed by setting the environment variable FTISHFD. Docket Files (/var/sunwconn/osiroot/ftam/doc/*.doc) Dockets are special FTAM files that contain the synchronization information which enables the recovery of interrupted file transfers. See Recovery on page 10 for more information. The default location for these files can be changed by setting the environment variable FTITRFD. Trace Files (/var/sunwconn/osiroot/ftam/log/*.log) Traces are logging files that are generated automatically by the SunLink FTAM local responder and local initiator. See Chapter 8, FTAM Trace Files for more information. The default location for these files can be changed by setting the environment variable FTILOGD. Introducing SunLink FTAM 13

28 1 14 Managing SunLink FTAM October 1994

29 Planning your SunLink FTAM Configuration 2 Example Configurations Example Configurations page 15 Interoperating with Other Implementations of FTAM page 17 Use the information in this chapter to help plan your SunLink FTAM configuration. This section suggests a few possible configurations using SunLink FTAM. Exchanging Files between Remote Systems If you install SunLink FTAM on all of the machines on your network, users of UNIX and non-unix machines can exchange and manipulate files regardless of whether the remote device is on the same LAN or on a remote network reachable using a public data network. 15

30 2 UNIX system gateway X.25 WAN (CLNP) Non-UNIX system Figure 2-1 Exchanging files between remote systems For example, in Figure 2-1, above, machines A and B can exchange files as easily as they could if they were both on the same LAN, regardless of the fact that there is a public service network between them and that they have different operating systems. To set up a configuration like this: 1. Install SunLink FTAM on machine A. 2. Add an entry to the Remote System Database (RSDB) on machine A, giving information for reaching machine B. 3. Configure machine B, so that it can reach machine A. Sharing a Local File Server If you install only the FTAM Initiator (osiftam) on a machine, it can initiate FTAM exchanges, but not respond to them. This might be appropriate if you have a group of workstations that need to be able to access files from a local server. 16 Managing SunLink FTAM October 1994

31 2 server Figure 2-2 Sharing a Local File Server In this case, you would only need to enable the FTAM Responder (osiftr) on the File Server. To set up a configuration like this: 1. Install SunLink FTAM on the server and the workstations. 2. Optionally, disable the FTAM Responder (osiftr) on the workstations. 3. On each workstation, make an entry in the RSDB providing information about the server. You can also include non-unix machines in configurations like the one shown in Figure 2-2. Interoperating with Other Implementations of FTAM SunLink FTAM can interoperate with any standard-compliant version of the FTAM protocols. However, take particular care when configuring SunLink FTAM, so that the parameters you set are all appropriate to the other version of FTAM. Pay particular attention to setting the Local Initiator and Local Responder parameters to work with the other version of FTAM. Check the following: Are the Supported Service Classes the same? Are the Functional Units the same? Do you need to change the list of Configurable Document Types? Does the remote version of FTAM use the New Object Identifier for NBS-9? If it does, as well as selecting this feature using ftamtool, you must also install version of the SunLink OSI Communications Platform. Planning your SunLink FTAM Configuration 17

32 2 Does the other version of FTAM use DR10? For further information on the above parameters, see Chapter 6, SunLink FTAM Parameters. 18 Managing SunLink FTAM October 1994

33 Configuring SunLink FTAM 3 Starting ftamtool page 20 Creating a Remote Systems Database (RSDB) page 22 Configuring the Local Initiator page 34 Configuring the Local Responder page 38 The OPEN LOOK graphical user interface for configuring SunLink FTAM is called ftamtool. This chapter describes how to use ftamtool to create a remote systems database (RSDB) and to configure the SunLink FTAM initiator and responder processes running on the local machine. Overview This section summarizes the steps involved in configuring SunLink FTAM. You do not need to carry out all of these steps if SunLink FTAM is not interoperating with any other implementations of FTAM. In this case, the default configuration described in Getting Started with SunLink FTAM should be sufficient. There are three parts to configuring SunLink FTAM, configure them in the following order: 19

34 3 1. Create the Remote Systems Database. Every remote destination that you want to be able to reach must appear in the remote systems database. For destinations that also use SunLink FTAM, you only need to configure the Network Address. Follow the instructions in Creating a Remote Systems Database (RSDB) on page Configure the Local Initiator. The local initiator defines the functional units and service classes proposed by the SunLink FTAM initiator (osiftam) during the negotiation phase. You only need to change the default configuration if you are interoperating a different implementation of the FTAM responder. Follow the instructions in Configuring the Local Initiator on page Configure the Local Responder. The local responder defines the functional units and service classes proposed by the SunLink FTAM responder (osiftr) during the negotiation phase. You only need to change the default configuration if you are interoperating with a different implementation of the FTAM responder. Follow the instructions in Configuring the Local Responder on page 38. Note If you do not have access to ftamtool, you can make changes to the Remote Systems Database while running the FTAM initiator. The commands for doing this are described in Appendix A, SunLink FTAM Command Summary. Starting ftamtool You can run ftamtool either locally or remotely. Staring ftamtool Locally To start and use ftamtool on your local machine, type: hostname% /opt/sunwconn/bin/ftamtool & The ftamtool main window looks like this: 20 Managing SunLink FTAM October 1994

35 3 Starting ftamtool Remotely To use ftamtool to configure a remote machine, start it remotely and display the output on your local monitor: 1. On your local machine, disable access restrictions for the remote machine so you are able to display ftamtool on your local monitor. localhost% $OPENWINHOME/bin/xhost + <remotehost> 2. Log in to the remote machine. localhost% rlogin <remotehost> Password: <your password> 3. On the remote machine, start ftamtool so that it displays on your local monitor. remotehost% /opt/sunwconn/bin/ftamtool -display <localhost>:0 & Configuring SunLink FTAM 21

36 3 Creating a Remote Systems Database (RSDB) The remote systems database (RSDB) contains a list of the remote systems recognized by the local FTAM initiator (osiftam). It creates a mapping between the host names used to reference remote hosts, and the OSI addresses used to reach them. To activate the RSDB configuration window, click SELECT on the Remote Systems Database icon in the ftamtool main window. 22 Managing SunLink FTAM October 1994

37 3 The scrolling-list displays an alphabetical list of the host names of all the systems currently entered in the RSDB. To display an entry, double-click it in the scrolling list, or type the name at the Enter System Name prompt. To change directory, type in the path to the directory and click SELECT on the Goto button. Type in the name of the directory and click SELECT on Goto Click SELECT to choose a system Type name of existing system Adding an Entry to the RSDB There are two ways of adding an entry to the RSDB. The simplest way to add entries RSDB is to modify one of the three templates. You cannot overwrite or delete the RSDB templates, unless you change the default access permissions for these files. You can also create a completely new entry. Modifying an Existing Template To add an entry to the RSDB by modifying one of the templates: 1. Display the Remote Systems Database configuration window. Click SELECT on the RSDB icon in the main window. Configuring SunLink FTAM 23

38 3 2. Click SELECT on the name of the appropriate RSDB template. Choose between: SUN_llc1: for LAN connections (for example, Ethernet, FDDI) SUN_rfc: for TCP/IP connections (RFC 1006) SUN_x25: for WAN connections (for example, X.25) Click SELECT to choose an RSDB template 3. Modify the Current System Name. This is the host name used to reference the remote system establishing an association. You cannot save your modifications using the existing system name, as this would overwrite the template. Type in a new system name 24 Managing SunLink FTAM October 1994

39 3 4. Modify the Application Process Title (APT). You only need to do this if the remote system is not running the SunLink FTAM responder daemon, osiftrd. The default APT, which is displayed when you load an RSDB template, corresponds to the SunLink FTAM responder daemon (osiftrd). To find out the correct APT for a non SunLink FTAM responder daemon, check with the system administrator responsible for the remote system. See Application Process Title on page 62 for a more detailed description of the APT. Enter the components of the APT separated by blank spaces, dots, or dashes. 5. Modify the Application Entity Qualifier (AEQ). You only need to do this if the remote system is running a different implementation of the FTAM responder daemon. The default AEQ, which is displayed when you load an RSDB template, corresponds to the SunLink FTAM responder daemon (osiftrd). To find out the correct AEQ for a non SunLink FTAM responder daemon, check with the system administrator responsible for the remote system. See Application Process Title on page 62 for a more detailed description of the AEQ. Type the correct APT Click SELECT to change the AEQ 6. Modify the OSI address elements. The default OSI address, which is displayed when you load an RSDB template, corresponds to the SunLink FTAM responder daemon (osiftrd). Configuring SunLink FTAM 25

40 3 If osiftrd is running on the remote system, then you need only modify the Network Address element. If there is a different FTAM responder running on the remote system, then you must enter all of the OSI address elements that correspond to that application. You may need to obtain the OSI address from the system administrator who set up the remote system. Refer to the Remote Systems Database Parameters on page 61 for a description of each of the elements in an OSI address. Enter the OSI address in either hexadecimal or ASCII format. Type in an ASCII value Change to hex format Type in a hex value The network address is the part of the OSI address that identifies the physical connection to the network: For a LAN (LLC1) connection (for example, Ethernet, FDDI), enter the network address in hexadecimal format. It is the NSAP address assigned for the OSI protocol stack. If the remote system is running SunLink FTAM, this is the NSAP assigned using ositool. By default it takes the form 49<hostid>01, as shown below: 26 Managing SunLink FTAM October 1994

41 3 Network address of the form: 49<hostid>01 Network type set to LLC1 For a WAN connection (for example, X.25) the network address is the NSAP address of the remote OSI protocol stack. If the remote system is running SunLink FTAM, this is the NSAP assigned using ositool. Network address of the form: Network type set to X.25 For a TCP/IP connection (RFC 1006), enter the network address in ASCII. It is the IP address (entered in dot notation) for the remote system. You cannot enter the host name in the place of an IP address. If the remote system is running SunLink FTAM, this is the IP address assigned using ositool. Configuring SunLink FTAM 27

42 3 Network address of the form: Network type set to RFC Click SELECT on Apply to confirm your changes and to add a new entry to the Remote Systems Database (RSDB). New entry added to the scrolling-list (based on template) Add an entry in the RSDB for every remote system that you want to be able to access using the SunLink FTAM initiator. Adding a Completely New Entry Use the New button to add a completely new entry to the Remote Systems Database (RSDB), instead of basing the entry on one of the three RSDB templates (SUN_llc1, SUN_rfc, and SUN_x25). To add a new entry to the RSDB: 28 Managing SunLink FTAM October 1994

43 3 1. Click SELECT on the RSDB icon to activate the RSDB configuration window. 2. Click SELECT on the New button to add a new (blank) entry to the RSDB. Click SELECT on New 3. Click SELECT on the Network Type that corresponds to the connection between the local system and the remote system as shown in. Choose one of the three supported subnetwork types: X.25: WAN connections LLC1: LAN connections (for example, Ethernet, FDDI) RFC1006:TCP/IP connections Configuring SunLink FTAM 29

44 3 Click SELECT to choose a network type 4. Enter a System Name, Application Entity Title (AET) and OSI Address. Follow the instructions in Modifying an Existing Template on page Click SELECT on Apply to confirm your changes and to add a new entry to the Remote Systems Database (RSDB), as shown below: New entry added to the scrolling-list Deleting an Entry from the RSDB To delete an entry from the Remote Systems Database: 1. Click SELECT on the RSDB icon to activate the RSDB configuration window. 2. Click SELECT on one the entries in the scrolling-list that you want to delete. 30 Managing SunLink FTAM October 1994

45 3 3. Click SELECT on the Delete button to remove the system from the Remote Systems Database. You cannot recover a deleted system once you have confirmed the delete operation. You cannot delete the RSDB templates unless you have modified the permissions for these files. Printing the RSDB To print a list of all the systems registered in the Remote Systems Database: 1. Click SELECT on the RSDB icon to activate the RSDB configuration window. 2. Click SELECT on the Print... button to activate the Print window. 3. Choose a printer from the Printer list, or click SELECT on the Print to File checkbox and specify the name of a file. Press MENU Drag and release MENU on the chosen printer 4. Click SELECT on Print to send the file to the specified printer (or file). Configuring SunLink FTAM 31

46 3 The output looks like this: SUN_llc1.rdb Application Process Title: Application Entity Qualifier: 1 PSEL: ftr SSEL: prs TSEL: ses Network Address: 0x Network Type: CLNP System Status: Open SUN_rfc.rdb Application Process Title: Application Entity Qualifier: 1 PSEL: ftr SSEL: prs TSEL: Empty Network Address: Network Type: TCP-IP System Status: Open SUN_x25.rdb Application Process Title: Application Entity Qualifier: 1 PSEL: ftr SSEL: prs TSEL: ses Network Address: x25_address Network Type: CONS System Status: Open rasputin.rdb Application Process Title: Application Entity Qualifier: 1 PSEL: ftr SSEL: prs TSEL: ses Network Address: Network Type: CONS System Status: Open 32 Managing SunLink FTAM October 1994

47 3 Closing and Opening Systems Closing a system in the Remote Systems Database temporarily prevents the SunLink FTAM initiator (osiftr) from opening an association with it. The system remains in the Remote Systems Database, and can be reopened later. To close a system: 1. Click SELECT on the RSDB icon to activate the RSDB configuration window. 2. Click SELECT on the entry in the scrolling-list that you want to close. 3. Press MENU on the System Status button to display the pull-down menu. Drag MENU to the Close item and release MENU to close the currently selected system. 4. Click SELECT on Apply to confirm your changes. To open a closed system: 1. Click SELECT on the RSDB icon to activate the RSDB configuration window. 2. Click SELECT on the entry in the scrolling-list that you want to open. 3. Press MENU on the System Status button to display the pull-down menu. Drag MENU to the Open item and release MENU to open the currently selected system. 4. Click SELECT on Apply to confirm your changes. Closing an open system Opening a closed system Configuring SunLink FTAM 33

48 3 Configuring the Local Initiator To open an association, the SunLink FTAM initiator (osiftam) negotiates with the FTAM responder running on the remote system to define a common set of functional units and services classes. (See Functional Units and Service Classes on page 6.) The local initiator options define the functional units and service classes proposed by the SunLink FTAM initiator (osiftam) running on the local system during this negotiation phase. By default, osiftam proposes all of the functional units and service classes that it supports. If the SunLink FTAM responder (osiftr) is running on the remote system, do not alter the default configuration for the local initiator. If there is any other type of FTAM responder running on the remote system, you may need to modify the default configuration of the local initiator to match the configuration of the remote responder. Check with the system administrator responsible for the remote responder to find out whether you need to do so. Note Proposing a functional unit or service class that is not supported by the FTAM responder does not prevent an association from being established. Failing to propose a supported functional unit or service class reduces the versatility of your file management system, and might reduce the chance that association negotiation will be concluded successfully. Modifying the Default Initiator Configuration To modify the default configuration for the local initiator: 1. Click SELECT on the Local Initiator icon to activate the Local Initiator configuration window. 2. Click SELECT on the checkboxes to disable the service classes that you do not want the initiator to propose when negotiating an association. 34 Managing SunLink FTAM October 1994

49 3 Indicates that the service class will not be proposed Indicates that the service class will be proposed 3. Click SELECT on the checkboxes to disable the functional units that you do not want the initiator to propose when negotiating an association. Indicates that the functional unit will not be proposed Indicates that the functional unit will be proposed 4. Click SELECT on the Configurable Document types you do not want the initiator to propose when negotiating an association. Indicates that INTAP-1 will not be used Configuring SunLink FTAM 35

50 3 5. Click SELECT on the New Object Identifier for NBS-9 parameter, if you require this Object Identifier type: You only require this Object Identifier type if you are interoperating a different implementation of FTAM, that implements the version of this parameter defined in the published version of the ISO FTAM Specification (8571), rather than the version given in the preliminary draft. If you do require this option, you must also use version or later of the SunLink OSI Communications Platform (Stack). 6. Click SELECT on the DR10 and Traces checkboxes if you want to enable Defect Report 10 or tracing (logging). Do not enable DR10 unless you are interoperating with an implementation of FTAM that uses it. Indicates that DR10 will not be used Indicates that the tracing will be done 7. Click SELECT on Apply to confirm your changes to the local initiator configuration. If you have configured an invalid combination of service classes and functional units, the system generates an error message when you apply your changes. Follow the instructions included in the error message to correct the error, and click SELECT on Apply to confirm your changes. Saving the Initiator Configuration The local definitions are stored in a configuration file called fti.init which is read each time osiftam is started. This file is normally located in the directory /var/sunwconn/osiroot/ftam/conf. 36 Managing SunLink FTAM October 1994

51 3 To save a copy of the initiator configuration in a different file: 1. Click SELECT on the Local Initiator icon to activate the Local Initiator configuration window. 2. Press MENU on the File button and drab MENU to the Save as... item. Release MENU to activate the Save as file selection window. 3. Enter the name of a new file or choose an existing file from the scrollinglist. You cannot overwrite the configuration file fti.init. To modify this file, make and apply the changes to the local initiator configuration. 4. Click SELECT on Save to save a copy of the configuration to file. To use the contents of the backup file to configure the SunLink FTAM initiator (osiftam), manually copy the backup file into the configuration file fti.init. Printing the Initiator Configuration To print the local initiator configuration: 1. Click SELECT on the Local Initiator icon to activate the Local Initiator configuration window. 2. Press MENU on the File button and drag MENU to the Print... item. Release MENU to activate the Print window. 3. Choose a printer from the Printer list, or click SELECT on the Print to File checkbox and specify the name of a file. Press MENU Drag and release MENU on the chosen printer Configuring SunLink FTAM 37