DECnet/OSI_for_DEC_OSF/1____________________________ Installation and Configuration Part Number: AA-Q0H3C-TE December 1994 _______________ Documentation Comments _______________ If you have comments or suggestions for this manual or any of the DECnet/OSI documents and if you have access to the Internet, mail your comments electronically to the DECnet/OSI writing group within Digital at the following address: doc_quality@lkg.mts.dec.com ______________________________________________________ Revision/Update Information: This is a new manual. Operating System: DEC OSF/1 V3.0-0 Software Version: DECnet/OSI V3.0 for DEC OSF/1 AXP © Digital Equipment Corporation 1994. All Rights Reserved. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, DDCMP, DEC, DECnet, DECNIS, DECserver, DECsystem, DECwindows, DNA, OpenVMS, ULTRIX, VAX, VAXstation, VMS, VMScluster, the AXP logo, and the DIGITAL logo. The following are third party trademarks: OSF/1 is a registered trademark of Open Software Foundation, Inc. UNIX is a registered trademark licensed exclusively by X /Open Co. Ltd. _________________________________________________________________ Contents Preface................................................... ix 1 Planning for the Installation 1.1 Steps to a Successful Installation............ 1-1 1.1.1 Planning Tasks............................ 1-1 1.1.2 Installation Tasks........................ 1-2 1.1.3 Configuration Tasks....................... 1-2 1.1.4 Postinstallation Tasks.................... 1-3 1.2 Deciding Which Software Subsets to Install.... 1-3 1.3 Your Software License PAK..................... 1-7 1.3.1 The End System PAK........................ 1-7 1.3.2 The Extended System PAK................... 1-8 Part I DECnet/OSI Installation and Configuration 2 Installing DECnet/OSI for DEC OSF/1 2.1 Preparing Your System for Installation........ 2-1 2.1.1 Acquiring Superuser Privileges............ 2-2 2.1.2 Checking Your Disk Space.................. 2-2 2.1.3 Performing System Backup.................. 2-3 2.1.4 Deleting Old Versions of DECnet/OSI....... 2-3 2.1.4.1 Deleting Subsets........................ 2-4 2.1.5 Using LMF to Register Your Software License PAK............................... 2-4 2.1.6 Creating a Guest Account.................. 2-6 2.2 Copying the Subsets from the Distribution Media......................................... 2-6 2.2.1 CDROM Installation........................ 2-7 2.2.2 Using RIS Over a Local Area Network....... 2-7 iii 2.2.3 Selecting the Software Subsets............ 2-7 2.2.3.1 DECnet/OSI Standard Installation........ 2-9 2.2.3.2 RFC1006 Only Installation............... 2-10 2.2.4 Copying the Software to Your System....... 2-11 2.2.4.1 Completion Messages..................... 2-12 2.2.5 Subset Post-Installation Notes............ 2-14 2.3 Rebuilding the Kernel......................... 2-15 2.3.1 Standard Kernel Rebuild Command........... 2-15 2.3.2 RFC1006 Only Kernel Rebuild Command....... 2-16 2.3.3 Kernel Rebuild Completion................. 2-16 2.3.4 Upgrading DECnet/OSI...................... 2-18 2.3.5 Kernel Rebuild Errors..................... 2-18 2.3.6 Kernel Requirement - DEC OSF/1 X/Open Transport Interface....................... 2-19 2.4 Rebooting Your System......................... 2-19 2.5 Choosing a Configuration Procedure............ 2-19 3 Basic Configuration 3.1 When to Use the Basic Configuration........... 3-1 3.1.1 Basic Configuration Defaults.............. 3-1 3.1.1.1 Phase IV Prefix......................... 3-2 3.1.1.2 Node Synonym Directory.................. 3-2 3.1.1.3 Configuring the Name Service Search Path.................................... 3-2 3.1.1.4 Configuring Network Addresses........... 3-2 3.1.2 Use the Checklist......................... 3-2 3.1.3 About the Basic Configuration Procedure... 3-3 3.1.3.1 Changing Your Answers................... 3-3 3.1.3.2 Default Values.......................... 3-4 3.1.3.3 Stopping the Configuration Procedure.... 3-4 3.1.3.4 Getting Help............................ 3-4 3.1.4 The Name Service Search Path.............. 3-4 3.1.4.1 Configuring the Search Path Information............................. 3-5 3.1.4.2 Modifying the Naming and Backtranslation Search Paths............................ 3-6 3.2 Starting the Configuration Procedure.......... 3-7 3.3 Specifying Your DECnet/OSI Node Name.......... 3-7 3.3.1 Using a Local Namespace................... 3-9 3.3.2 Using a DECdns Distributed Namespace...... 3-10 3.4 Giving Your System a Node Synonym............. 3-10 3.4.1 Specifying your Node Synonym.............. 3-10 iv 3.5 Communicating with Phase IV Nodes............. 3-11 3.5.1 Supplying an Address...................... 3-11 3.6 Configuring a Token Ring Communications Device........................................ 3-11 3.6.1 Setting the Token Ring Station Speed...... 3-12 3.7 Running MOP Standalone........................ 3-13 3.8 Confirming Your Answers and Starting the DECnet/OSI Software........................... 3-13 3.9 Configuring Your Namespace.................... 3-15 3.9.1 Using Local Namespace..................... 3-16 3.9.2 DECdns Clerk Configuration................ 3-16 3.9.2.1 Connecting to a Remote Server In a Distributed Namespace................... 3-17 3.10 Verifying the Basic Configuration Procedure... 3-18 3.11 Configuring the DECnet-Internet Gateway....... 3-18 3.12 Configuring the OSI Applications Software..... 3-18 4 Advanced Configuration 4.1 When to Use the Advanced Configuration........ 4-1 4.1.1 About the Advanced Configuration Procedure................................. 4-3 4.1.1.1 Stopping the Configuration Procedure.... 4-3 4.1.1.2 Changing Your Answers................... 4-4 4.1.1.3 Default Values.......................... 4-4 4.1.1.4 Getting Help............................ 4-4 4.1.2 The Name Service Search Path.............. 4-4 4.1.2.1 Configuring the Search Path Information............................. 4-5 4.1.2.2 Modifying the Naming and Backtranslation Search Paths............................ 4-6 4.2 Starting the Configuration Procedure.......... 4-7 4.3 Specifying Your DECnet/OSI Node Name.......... 4-7 4.3.1 Using a Local Namespace................... 4-9 4.3.2 Using a Distributed Namespace............. 4-10 4.4 Giving Your System a Node Synonym............. 4-10 4.4.1 Specifying your Node Synonym.............. 4-10 4.5 Communicating with Phase IV Nodes............. 4-11 4.5.1 Supplying an Address...................... 4-11 4.5.2 Supplying a Phase IV Prefix............... 4-11 4.6 Using an Alternate Node Synonym Directory..... 4-12 4.7 Configuring Network Addresses................. 4-13 4.7.1 Choice 1: Autoconfiguring Addresses....... 4-13 v 4.7.2 Choice 2: Manually Configuring Addresses................................. 4-14 4.7.2.1 If You Have a Phase IV compatible Address................................. 4-14 4.7.2.2 If You Do Not Have a Phase IV compatible Address................................. 4-15 4.8 Selecting from Multiple Communications Devices....................................... 4-15 4.9 Configuring a Token Ring Communications Device........................................ 4-16 4.9.1 Setting the Token Ring Station Speed...... 4-17 4.10 Configuring DECdts............................ 4-17 4.10.1 Configuring Your System as a DECdts Clerk or Server................................. 4-18 4.11 Configuring Your Namespace.................... 4-19 4.11.1 Using a Local Namespace................... 4-19 4.11.2 DECdns Clerk Configuration................ 4-19 4.12 Configuring the DECnet-Internet Gateway....... 4-20 4.13 Running MOP Standalone........................ 4-20 4.14 Confirming Your Answers and Starting the DECnet/OSI Software........................... 4-20 4.15 Finishing the DECdns Configuration............ 4-23 4.15.1 Finishing the Local Namespace Configuration............................. 4-23 4.15.2 Finishing the DECdns Clerk Configuration............................. 4-24 4.15.2.1 Connecting to a Remote Server in a Distributed Namespace................... 4-24 4.16 Verifying the Advanced Configuration Procedure..................................... 4-25 4.17 Configuring DECnet/OSI to use X.25 Services... 4-25 5 Postinstallation Tasks - Namespace Activities 5.1 DECdns Distributed Namespace Tasks............ 5-1 5.1.1 Registering Subsequent DECnet/OSI Systems................................... 5-1 5.1.2 First DECnet/OSI System on a Network with Phase IV Nodes ........................... 5-2 5.1.3 First DECnet/OSI System on a Network with No Phase IV Nodes ........................ 5-3 5.2 Local Namespace Tasks......................... 5-3 5.3 Update_Nodes.................................. 5-4 vi 5.3.1 Running Update_Nodes...................... 5-4 5.3.1.1 Copying a DECnet Phase IV Node Database................................ 5-5 6 Running the Installation Verification Procedure 6.1 IVP Requirements.............................. 6-1 6.2 Running the IVP............................... 6-1 6.2.1 Supplying a Full Name..................... 6-1 6.2.2 Checking the State of DECnet/OSI.......... 6-2 6.2.3 Checking the DECdns Clerk................. 6-3 6.2.4 Reaching a Remote System.................. 6-4 6.2.5 Testing your Local System................. 6-4 Part II Installation and Configuration for FTAM and VT 7 Installing FTAM and Virtual Terminal 7.1 Preparing Your System for Installation........ 7-1 7.1.1 Acquiring Superuser Privileges............ 7-1 7.1.2 Checking Your Disk Space.................. 7-2 7.1.3 Performing System Disk Backup............. 7-2 7.1.4 Deleting Old OSI Applications Subsets..... 7-2 7.1.4.1 Deleting Subsets........................ 7-3 7.1.5 Using LMF to Register Your Software License PAK............................... 7-3 7.2 Installing FTAM and Virtual Terminal.......... 7-5 7.2.1 Installing the Subsets from the Distribution Media........................ 7-5 7.2.1.1 CDROM Installation...................... 7-5 7.2.1.2 Using RIS Over a Local Area Network..... 7-6 7.2.2 Selecting the Software Subsets............ 7-6 7.2.2.1 DECnet/OSI Standard Installation........ 7-7 7.2.3 Copying the Software to Your System....... 7-7 7.2.3.1 Completion Messages..................... 7-8 vii 8 Configuring FTAM and Virtual Terminal 8.1 FTAM and Virtual Terminal Terminology......... 8-1 8.2 About the OSI Application Entity Database..... 8-1 8.3 Steps To Configure Initiating and Responding Entities...................................... 8-2 8.3.1 Checklist for Responding Entity........... 8-2 8.3.2 Checklist for Initiating Entity........... 8-3 8.3.3 Example: Performing An FTAM File Copy..... 8-4 8.3.4 Example: Performing A Virtual Terminal Login..................................... 8-7 8.4 About /usr/sbin/osiapplsetup.................. 8-10 8.4.1 About Autoconfiguration and Manual Configuration............................. 8-11 8.4.2 Getting Help, Stopping the Configuration Procedure, and Using Defaults............. 8-12 8.5 Starting the OSI Applications Configuration Procedure..................................... 8-13 8.6 Configuring the Local FTAM and VT Application Addresses..................................... 8-13 8.6.1 DEC X.500 Directory Service............... 8-14 8.6.2 Autoconfiguring the Local FTAM or VT Application's Addresses................... 8-14 8.6.3 Manually Configuring the Local FTAM and VT Application Addresses..................... 8-17 8.7 Configuring Addresses for Remote FTAM and VT Applications.................................. 8-19 8.7.1 If You Configure To Use X.500............. 8-20 8.7.1.1 Adding Distinguished Name Format Entries................................. 8-20 8.7.1.2 Adding Address Format Entries........... 8-22 8.7.1.3 Adding Pattern Format Entries........... 8-23 8.7.2 If You Configure Not To Use X.500......... 8-25 8.8 Manually Configuring FTAM and VT Listeners.... 8-26 8.9 Starting FTAM and VT.......................... 8-27 8.10 Running the Installation Verification Procedure..................................... 8-28 8.10.1 If the IVP Fails.......................... 8-29 8.10.2 Reinstalling the Software................. 8-29 8.11 Rebuilding the Internal Table of Commands..... 8-30 8.12 Verifying the Installation.................... 8-30 8.13 Verifying the FTAM-FTP Gateway Installation .............................................. 8-30 viii 8.13.1 To Check the OSI Portion of the FTAM-FTP Gateway................................... 8-31 8.13.2 To Check the Internet Portion of the FTAM-FTP Gateway.......................... 8-31 Part III Appendixes A Sample Installation A.1 Sample Installation Log....................... A-1 B Sample Configurations B.1 Sample DECnet/OSI Advanced Configuration...... B-1 B.2 Sample Log File............................... B-1 B.3 Sample DECnet/OSI Basic Configuration......... B-5 B.4 Sample Log File............................... B-6 B.5 Sample Configuration Verification Procedure... B-9 C Sample FTAM and Virtual Terminal Configurations C.1 Sample FTAM and VT Autoconfiguration.......... C-1 C.2 Sample Manual Configuration................... C-8 D Creating NSAP Addresses D.1 IDP Values ................................... D-2 D.2 DSP Values ................................... D-3 D.3 NSAP Entry and Display Formats................ D-6 D.4 Converting Phase IV Addresses to NSAPs ....... D-7 D.5 Converting NSAPs to Phase IV Addresses ....... D-8 D.6 Forms of the NSAP Displayed by NCL ........... D-9 D.7 How to Obtain a Unique IDP and PreDSP ........ D-11 D.7.1 For a Private Network (AFI 49) ........... D-11 D.7.2 Allocation Authority for Single-Country Organizations (AFI 39) ................... D-11 D.7.3 Allocation Authority for International Organizations (AFI 47) ................... D-12 D.7.4 Using a Telex Number for the IDI (AFIs 41 and 55) .................................. D-12 D.7.5 Using a Telephone Number for the IDI (AFIs 43 and 57) ............................... D-13 ix D.7.6 Using an ISDN Number for the IDI (AFIs 45 and 59) .................................. D-13 D.8 Example: NSAP Fields ......................... D-14 D.9 Example: Using Values Allocated by ANSI ...... D-15 E Software Subsets and Installation Requirements E.1 DECnet/OSI for DEC OSF/1 Software Subsets..... E-1 Index Figures 3-1 Basic Configuration Checklist............. 3-3 4-1 Advanced Configuration Checklist.......... 4-1 4-2 Advanced Configuration Checklist (Part 2)........................................ 4-2 Tables 1-1 Summary of DECnet/OSI for DEC OSF/1 Software Subsets - Required............... 1-4 1-2 Summary of DECnet/OSI for DEC OSF/1 Software Subsets - Optional............... 1-5 2-1 Configuration Procedures.................. 2-20 8-1 Setup Tasks For The Responding Entity..... 8-2 8-2 Setup Tasks For The Initiating Entity..... 8-3 D-1 Information for Building Unique NSAPs..... D-2 D-2 Entering NSAP Field Values ............... D-16 E-1 Summary of DECnet/OSI Software Subsets and Disk Space................................ E-1 x _________________________________________________________________ Preface This book explains how to install DECnet/OSI software on a DEC OSF/1 system. If the system you are installing is the first DECnet/OSI node in your network, read the DECnet /OSI Planning Guide before attempting the installation. This book contains important planning activities you must perform to prepare for the DECnet/OSI installation. Intended Audience This book is for a user installing DECnet/OSI software on a running DEC OSF/1 system; ideally, a person who has system administration experience. Conventions This book uses the following conventions. ___________________________________________________________ Convention_______Meaning___________________________________ special type Indicates a literal example of system output or user input. In text, indicates command names, keywords, node names, filenames, directories, utilities, and tools. On a DEC OSF/1 system, enter the word or phrase in the exact case shown. italic Indicates a variable. bold Indicates a new term defined either in the text or in the DECnet/OSI Glossary. Indicates that you press the Return key. ix ___________________________________________________________ Convention_______Meaning___________________________________ Indicates that you press the Control key while you type the key noted by x. [ ] In command format descriptions, indicates optional elements. You can enter as many as you want. { } In command format descriptions, indicates you must enter at least one listed element. % The standard DEC OSF/1 system prompt. # The DEC OSF/1 superuser prompt. command() Cross-references to specific command documentation include the section number in the reference book where the commands are documented. For example, ocp(1) indicates that you can find the material on the ocp command in Section 1 of the reference pages. ... Indicate that the preceding item can be _________________repeated_one_or_more_times._______________ All Ethernet addresses are hexadecimal; all other numbers are decimal unless otherwise noted. x 1 _________________________________________________________________ Planning for the Installation This chapter discusses the major steps for planning a successful installation of DECnet/OSI. Before you begin, read DECnet/OSI Planning Guide and refer to DECdns Management to help you decide whether to use the Local Namespace or a DECdns distributed namespace. 1.1 Steps to a Successful Installation There are four major task areas necessary for installing your software: o Planning o Installation o Configuration o Postinstallation 1.1.1 Planning Tasks Before you set up a new DECnet/OSI network, you need to: o Document the proposed network configuration. o Develop an implementation strategy. o Evaluate software options. You should complete the appropriate checklist for your configuration. Refer to: o Figure 3-1 for basic configuration o Figure 4-1 for advanced configuration These checklists help to ensure you have all the information you need to configure the DECnet/OSI software on your system. Planning for the Installation 1-1 Consider these planning questions: o What namespace will you use? Will you use a Local Namespace? Or, will you make your system a DECdns clerk and join an existing DECdns distributed namespace? o How will you use DECdts? Will your system be a DECdts clerk or server? o Which configuration procedure will you use, basic or advanced? 1.1.2 Installation Tasks Prepare your system and load it with the software subsets. Chapter 2 describes how to perform these installation tasks: o Check your system's available disk space. o Choose the software subsets you want to install and copy the subsets from the distribution media to your system's disk. o Ensure you have the correct Product Authorization Key (PAK) and that your software license is registered. o Rebuild your system's DEC OSF/1 kernel and reboot your system. 1.1.3 Configuration Tasks Use the guidelines in Section 2.5 and Table 2-1 to determine the configuration procedure you should use; then refer to the indicated chapter for a description of the procedure. Configure the software using the appropriate procedure. Examples of configuration tasks include: o Specifying system name and address information. o Selecting a namespace for your own system. o Selecting how your system will use DECdts. o Specifying optional parameters such as multiple communications devices and distributed namespace information. o Configuring your system to use the FTAM and Virtual Terminal software. 1-2 Planning for the Installation 1.1.4 Postinstallation Tasks After configuration, there might be additional tasks to perform to ensure your system's operation in the network. The postinstallation tasks for your system will vary depending upon your system's configuration. Chapter 5 and Chapter 6 describe postinstallation tasks. Other tasks are described in DECnet/OSI Network Management. Examples of postinstallation tasks include: o Registering the first DECnet/OSI system on the network. o Running the installation verification procedure (IVP). 1.2 Deciding Which Software Subsets to Install Before you begin the installation, decide which subsets you need to install. Table 1-1 lists the required subsets that provide a minimum configuration. Planning for the Installation 1-3 Table 1-1 Summary of DECnet/OSI for DEC OSF/1 Software Subsets - __________Required_______________________________________________ Subset_________Function_____________________________Name_________ DECnet Provides the DECnet/OSI for DEC DNABASE300 /OSI Base OSF/1 function that enables you Components to share information with remote DECnet users and programs over the network. This subset includes the DECdns and DECdts components. DECnet/OSI Provides the Network Command DNANETMAN300 Network Language (NCL) components that Management you use to manage DECnet/OSI for DEC OSF/1. DECnet/OSI Provides the DNA Network Management DNADLI300 Datalink required to operate DECnet/OSI Components over the DLI (Datalink Interface) _______________software._________________________________________ Table 1-2 lists the optional DECnet/OSI for DEC OSF/1 subsets and the FTAM and Virtual Terminal subsets. 1-4 Planning for the Installation Table 1-2 Summary of DECnet/OSI for DEC OSF/1 Software Subsets - __________Optional_______________________________________________ Subset_________Function_____________________________Name_________ OSI Provides FTAM, the OSI application DNAAPP300 Applications that allows file operations Base with other systems that contain a FTAM implementation. Also provides Virtual Terminal, the OSI application that enables network terminal access to systems that are OSI-compliant. This subset includes the message catalog files, Trace utility, installation script, converter program for existing FTAM files, FTAM and Virtual Terminal release notes, and shell scripts of installation. OSI Provides online reference DNAAPPMAN300 Applications information for OSI applications. Reference Gives the syntax, description, Pages diagnostic messages, and restrictions for FTAM and Virtual Terminal commands and routines. OSI The FTAM-FTP gateway enables file DNAAPPGWY300 Applications operations between OSI systems Gateways and Internet (TCP/IP) systems. The VT/Telnet gateway provides bidirectional communications between an OSI system and an Internet system. The LAT/VT gateway provides communications from a LAT system to a remote OSI system. The VT/CTERM gateway provides bidirectional communications between an OSI system and a DECnet system. (continued on next page) Planning for the Installation 1-5 Table 1-2 (Cont.) Summary of DECnet/OSI for DEC OSF/1 Software __________________Subsets_-_Optional_____________________________ Subset_________Function_____________________________Name_________ DECnet/OSI Provides online system reference DNAMAN300 Reference information. Gives the diagnostic Pages messages, restrictions, and examples for commands, system calls, and subroutines. CTF User Provides utilities for analyzing CTAANAL120 Environment data used to trace local and remote DECnet/OSI end systems and routers. CTF Collector Provides utilities for collecting CTABASE120 Component data used to trace remote DECnet /OSI end systems and routers. DEC OSF/1 WAN Provides utilities used by the ZZAUTIL101 Utilities Common Trace Facilities. Also used by the WANDD and X.25 software. DECnet/OSI Downloads workstations and terminal DNAMOP300 MOP Utilities servers. Used by utilities like Remote Installation Service (RIS). DECnet- Provides mail, remote login, and DNAINETGW300 Internet file transfer interoperability Gateway between DECnet systems and Internet (TCP/IP) systems using your system as a gateway. DECnet/OSI Contains utilities and sample DNAUTIL300 Miscellaneous software supplied on an "as- Software is" basis for general customer use. However, Digital neither supports these utilities nor covers them under any Digital support contracts. DECnet/OSI Provides libraries and header files DNAPGMR300 Programming necessary to write programs to the Tools DECnet interfaces. (continued on next page) 1-6 Planning for the Installation Table 1-2 (Cont.) Summary of DECnet/OSI for DEC OSF/1 Software __________________Subsets_-_Optional_____________________________ Subset_________Function_____________________________Name_________ DECnet/OSI Enables the use of RFC 1006, which DNARFC1006300 RFC1006 allows OSI applications to run over Components_____a_TCP/IP_network_connection.______________________ 1.3 Your Software License PAK A software license Product Authorization Key (PAK) enables you to install and use specific software elements. There are two DECnet/OSI for DEC OSF/1 software PAKS: o End System PAK (DECNET-OSI-END) o Extended System PAK (DECNET-OSI-EXT) 1.3.1 The End System PAK The following list shows the functionality enabled by the End System PAK: o DECnet/OSI for DEC OSF/1 - Software that allows a DECnet/OSI system to act as an end node on a DECnet/OSI network. This software also provides the DECnet-Internet Gateway, which offers bidirectional functions between DECnet and Internet systems. o File Transfer, Access and Management (FTAM) - The OSI application that provides the ability to manipulate files in a multivendor environment. o Virtual Terminal (VT) - Software that supports the ISO Virtual Terminal protocol. Enables remote logins and access to other OSI-compliant systems. o The Digital Distributed Time Service (DECdts) - Provides precise, fault-tolerant clock synchronization for systems in local and wide area networks. o The Digital Distributed Name Service (DECdns) client - Enables a DECnet/OSI system to use DECdns to store and retrieve information. Planning for the Installation 1-7 o The Local namespace-A discrete, self-contained local namespace that provides a local database of names. The Local namespace stores all name and addressing information on the system that uses it. Depending on the number of address towers stored, the Local namespace is designed to scale to at least 100,000 nodes. o Wide Area Network device drivers - Provide Wide Area Network connectivity using the High Level Data Link Control (HDLC) protocol and device drivers for point- to-point full duplex connections. The DECnet/OSI license includes this functionality which is installed from the DEC X.25 for DEC OSF/1 software included on the Software CD-ROM. o LLC2 Services - ISO 8881 "Use of X.25 Packet Level Protocol in Local Area Networks" provides connection oriented network service over a Local Area Network to another suitably configured X.25 system on the same LAN. You can also make X.25 logical connections through a connector system using LLC2. The DECnet/OSI license includes this functionality that is installed from the DEC X.25 for DEC OSF/1 software included on the Software CD-ROM. o Online Manuals - All the DECnet/OSI and X.25 documentation is available in Bookreader format. The DECnet/OSI license includes this functionality, which is available from the Documentation CD-ROM. 1.3.2 The Extended System PAK The Extended System PAK enables these functions: o All components and functions of the End System PAK. o FTAM-FTP gateway - Allows OSI and Internet systems to exchange files with each other. o VT/Telnet gateway - Provides bidirectional communications between an OSI system and an Internet system. o VT/CTERM gateway - Provides bidirectional communications between an OSI system and a DECnet system. o LAT/VT gateway - Provides communications from a LAT terminal to a remote OSI system. 1-8 Planning for the Installation Part I _________________________________________________________________ DECnet/OSI Installation and Configuration Part I describes how to install and configure DECnet/OSI for DEC OSF/1. It includes the following chapters: o Chapter 2 - Installing DECnet/OSI for DEC OSF/1 o Chapter 3 - Basic Configuration o Chapter 4 - Advanced Configuration o Chapter 5 - Postinstallation Tasks - Namespace Activities o Chapter 6 - Running the Installation and Verification Procedure 2 _________________________________________________________________ Installing DECnet/OSI for DEC OSF/1 This chapter describes how to install the DECnet/OSI software on your system and how to prepare your system for the configuration process. It includes: o Preparing your system for the installation. o Copying the software from the distribution media. o Rebuilding your system's DEC OSF/1 kernel. o Rebooting your system. o Choosing the correct configuration procedures. 2.1 Preparing Your System for Installation The first part of the installation procedure is preparing your system. Preparing your system requires the following steps: 1. Make sure you have superuser privileges (Section 2.1.1). 2. Check your system's disk space (Section 2.1.2). 3. Back up your system disk (Section 2.1.3). 4. Delete previous versions of DECnet/OSI subsets (Section 2.1.4). 5. Register your Product Authorization Key (PAK) (Section 2.1.5). 6. Create a guest account in your system password file (Section 2.1.6). Installing DECnet/OSI for DEC OSF/1 2-1 2.1.1 Acquiring Superuser Privileges To install and configure DECnet/OSI, you must have superuser privileges. The command to acquire superuser privileges is su. You must then enter the root password. Refer to the DEC OSF Guide to System Administration for details on acquiring superuser privileges. 2.1.2 Checking Your Disk Space Verify that you have enough free disk space to install and configure the software subsets of your choice. The installation could fail if it runs out of disk space while copying the subsets from the distribution media. Additionally, you need enough free disk space to rebuild your DEC OSF/1 kernel or the installation will fail. The whole installation kit requires approximately 65 MB of total disk space including: o 10 MB in the / partition for the new kernel o 50 MB in the /usr partition for subsets o 5 MB in the /var partition for database files The minimum installation kit requires approximately 32 MB of total disk space including: o 10 MB in the / partition for the new kernel o 20 MB in the /usr partition for subsets o 2 MB in the /var partition for data files You can find a complete description of the space requirements for each subset in Appendix E. To check the available disk space in /usr, /var, and root (/), enter these commands: # df -k / # df -k /usr # df -k /var 2-2 Installing DECnet/OSI for DEC OSF/1 2.1.3 Performing System Backup Before you install the subsets back up your system disk. For information on backing up your system, refer to Guide to System Administration. 2.1.4 Deleting Old Versions of DECnet/OSI Before you begin the installation, check to see if a previous version of DECnet/OSI exists on your system. If it does, you must delete the subsets before you install the new DECnet/OSI for DEC OSF/1 subsets. ________________________ Note ________________________ When you delete existing DECnet/OSI for DEC OSF/1 subsets, the operation shuts down DECnet, saves any existing DECdns clerk data files, and leaves the existing NCL scripts. The existing DECdns clerk data files will be restored when you install the new DECnet /OSI for DEC OSF/1 subsets. ______________________________________________________ Use the following command to see if DECnet/OSI subsets are installed on the system, where DNA is the subset name prefix of DECnet/OSI: # setld -i | egrep "^DNA|^CTA|^ZZA" If any subsets with one of these product codes exists on your system, the utility displays an installed message, such as the following example for DECnet/OSI for DEC OSF/1 V1.1: DNABASE3000 installed DECnet/OSI Base Components If a previous version of DECnet/OSI exists, use the steps in Section 2.1.4.1 to delete all subsets. Then follow the instructions in Section 2.1.5 to ensure you have the correct PAK before you continue with the installation. Installing DECnet/OSI for DEC OSF/1 2-3 2.1.4.1 Deleting Subsets To delete the software from your system, log in as superuser and issue the setld command with the -d option, where subset is the name of the DECnet/OSI software subsets you want to delete: # setld -d subset [...] The following example deletes the DECnet/OSI Miscellaneous Software and DECnet-Internet Gateway subsets: # setld -d DNAUTIL300 DNAINETGW300 ________________________ Note ________________________ Because of software dependencies, delete the DECnet /OSI network management subset (DNANETMAN300) last. ______________________________________________________ 2.1.5 Using LMF to Register Your Software License PAK The next step in the installation procedure is to register your Product Authorization Key (PAK) using the License Management Facility (LMF). LMF is a system management software tool that enables you to comply with your license agreement. LMF offers options for the variety of license agreements. The terms and conditions of your contract determine your legal use of this software. LMF maintains the file of registered software license PAKs and keeps a library of functions used by licensed software. The following instructions show how you might register an End System software license PAK using LMF: 1. Make sure that you have your PAK. 2. Log on to your system as a superuser. 3. Issue an lmfsetup command: # lmfsetup 4. After you issue this command, you receive the following confirmation: # Register PAK ((type q or quit to exit) [template] 5. Press . 2-4 Installing DECnet/OSI for DEC OSF/1 After you do this, you are prompted to answer a series of questions. These questions correspond to the fields on your PAK form. Use the information from your DECnet /OSI for DEC OSF/1 PAK to reply to each question. Any fields that are left blank on the PAK should be left blank as you enter the data. 6. After you respond to all the questions, you should receive a completion message similar to the following: PAK registered for template successfully 7. Exit lmfsetup by entering quit: # Register PAK ((type q or quit to exit) [template] quit 8. Issue an lmf reset command: # lmf reset 9. Issue an lmf list command to verify your registration: # lmf list ________________________ Note ________________________ If you attempt to load a PAK and a PAK has already been loaded, you receive an error message similar to the following: Combine DECNET-OSI-END SQM014419 with DECNET-OSI-END SQM010892 If you receive this message, do the following: 1. List the license PAK templates using the following command: # lmf list full for DECNET-OSI-END 2. Compare the information in the templates, and note the authorization number of the software license PAK you want to delete. 3. Use the following command to delete the old PAK: # lmf delete DECNET-OSI-END DEC authorization-number 4. Issue another lmf reset command. ______________________________________________________ Installing DECnet/OSI for DEC OSF/1 2-5 If you want to know how to obtain a license and PAK or how you use the LMF facility, refer to the DEC OSF/1 Guide to Software License Management, or the lmf and lmfsetup man pages (lmf(8) and lmfsetup(8)) for additional information. 2.1.6 Creating a Guest Account A guest account allows remote DECnet users (who use the DECnet file transfer utility) access to world-readable files on your system without having to supply access control information for each remote operation. The default user account for the DECnet file transfer utility is guest. To define a guest account, log in as superuser and enter the adduser command. When the command prompts you for the login name of the new user, enter the name guest in lowercase letters. For example: # adduser Enter login name for new user (initials, first or last name): guest A prompt then asks you for you for information about the new user, including a password for this account. For further instructions on using adduser to create a new account, refer to the Guide to System Environment Setup in your operating system documentation set. To ensure that the guest cannot be used interactively by remote users (a potential security risk), use the vipw command to enter the string Nologin in the password field. 2.2 Copying the Subsets from the Distribution Media The next step in installing the software is to copy the DECnet/OSI subsets from the distribution media to the target system. The steps to accomplish this task vary, depending on whether you are using the DEC OSF/1 Layered Product Consolidated Software Distribution disk (CDROM) or the Remote Installation Service (RIS) over a local area network. After you copy the subsets on your system, rebuild your system's DEC OSF/1 kernel (see Section 2.3). 2-6 Installing DECnet/OSI for DEC OSF/1 2.2.1 CDROM Installation If you are installing the software from a CDROM, use this procedure: 1. Determine the directory of the DECnet/OSI files. Refer to the Master Index table in the Consolidated Software Distribution Disk User's Guide for the name of the directory on the CDROM that contains the DECnet/OSI software. 2. Insert the disk into the drive to determine the device name for the drive. The drive is either RRD40 or RRD42. Use the following command to list the available disk devices: # file /dev/rr*c 3. Mount the disk using the following command and device's name: # mount -r -d /dev/device_name /mnt 4. Copy the software to your system, using the software's directory name and this setld(8) command: # setld -l /mnt/directory_name 2.2.2 Using RIS Over a Local Area Network You can install DECnet/OSI for DEC OSF/1 over your network using the Remote Installation Service (ris) utility. Refer to the Remote Installation Service document and ris(8) in the Reference Pages, Section 8, for requirements. If you are using RIS over a local area network to install the software, use the command, setld -l hostname:, where hostname is the name of the host from which you are loading the software. 2.2.3 Selecting the Software Subsets The next task is to choose the subsets you need to copy from the distribution media. Run setld, then select from the following menu of subsets: Installing DECnet/OSI for DEC OSF/1 2-7 # setld -l /kits/osf1/DNA_V3.0/axp DECnet/OSI for DEC OSF/1 AXP V3.0-0 (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. To install and configure DECnet/OSI on this system, choose all subsets from the Standard Run-time Environment, and any of the other subsets desired for additional functionality. Please see the installation guide for further details on selecting subsets. Hit to continue: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. - Common Trace Facility Components: 1) CTF Collector Components 2) CTF User Environment 3) DEC OSF/1 WAN Utilities - DECnet/OSI Standard Run-time Environment: 4) DECnet/OSI Base Components 5) DECnet/OSI Datalink Components 6) DECnet/OSI Network Management --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): - OSI Applications: 7) OSI Application Gateways 8) OSI Application On-line Docs 9) OSI Applications - Optional DECnet/OSI Components: 10) DECnet-Internet Gateway 11) DECnet/OSI MOP Utilities 12) DECnet/OSI Miscellaneous Software 13) DECnet/OSI Programming Tools 14) DECnet/OSI RFC1006 (OSI/TCP) 15) DECnet/OSI Reference Pages 2-8 Installing DECnet/OSI for DEC OSF/1 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): Or you may choose one of the following options: 16) ALL of the above 17) CANCEL selections and redisplay menus 18) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. 2.2.3.1 DECnet/OSI Standard Installation For the minimum DECnet/OSI for DEC OSF/1 configuration, you must install the following three subsets: o DECnet/OSI Network Management o DECnet/OSI Base Components o DECnet/OSI Datalink Components The remaining subsets you select are optional. Type the numbers of the options that you want to install. Separate each number with a space, not a comma. You can specify a range of numbers using a hyphen to join them, as in the following example: Choices (for example, 1 2 4-6): 16 You are installing the following optional subsets: - Common Trace Facility Components: CTF Collector Components CTF User Environment DEC OSF/1 WAN Utilities - DECnet/OSI Standard Run-time Environment: DECnet/OSI Base Components DECnet/OSI Datalink Components DECnet/OSI Network Management - OSI Applications: OSI Application Gateways OSI Application On-line Docs OSI Applications Press RETURN to display the next screen: \ Installing DECnet/OSI for DEC OSF/1 2-9 - Optional DECnet/OSI Components: DECnet-Internet Gateway DECnet/OSI MOP Utilities DECnet/OSI Miscellaneous Software DECnet/OSI Programming Tools DECnet/OSI RFC1006 (OSI/TCP) DECnet/OSI Reference Pages After you specify the subsets, the procedure prompts you to verify your choice: Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. If you chose the wrong options, type no to indicate that the subsets are not correct; the subset menu redisplays, and you can reselect your subsets. If you chose the correct options, type yes. The procedure also checks to make sure you have enough file space to install the subsets you select. 2.2.3.2 RFC1006 Only Installation If you use only the RFC1006 feature to run OSI applications over TCP/IP, you need only copy the DECnet/OSI Network Management and the DECnet/OSI RFC1006 (OSI/TCP) subsets. The DECnet/OSI XTI extensions library, libxtiosi.so needed for RFC1006 is in the Network Management subset. After you copy these subsets, use the directions in Section 2.3.2 to rebuild the kernel. You may also want to select the OSI Applications subset which you can configure to use the RFC1006 functionality. You can install this subset at any later point since it does not require a kernel rebuild. 2-10 Installing DECnet/OSI for DEC OSF/1 2.2.4 Copying the Software to Your System After you select the subsets you want to install, the procedure copies them from the installation media to your disk. The following example shows a partial display as the procedure copies selected software subsets: DEC OSF/1 WAN Utilities Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Network Management Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Datalink Components Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Base Components Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet-Internet Gateway Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Reference Pages Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI MOP Utilities Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Miscellaneous Software Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Programming Tools Copying from /kits/osf1/DNA_V3.0/axp (disk) Working....Tue Nov 1 14:58:34 EST 1994 Verifying DECnet/OSI RFC1006 (OSI/TCP) Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying Installing DECnet/OSI for DEC OSF/1 2-11 OSI Applications Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying OSI Application Gateways Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying OSI Application On-line Docs Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying CTF Collector Components Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying CTF User Environment Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying Installing WAN Utilities V1.1 for DEC OSF/1 Systems (c) Digital Equipment Corporation. 1994. All Rights Reserved. If verification fails, look in /var/adm/fverify.log and /var/admin/setld.log for information to help you correct the error. Make the correction and restart the installation by using the setld -l command. 2.2.4.1 Completion Messages When the copy is complete, the procedure displays completion information on the subsets you chose to install. You must rebuild the kernel and reboot your system before you configure any of the DECnet/OSI software. Creating directories and symbolic links for ZZAUTIL110 ... done. Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) Creating directories and symbolic links for DNANETMAN300 ... done. Configuring "DECnet/OSI Network Management " (DNANETMAN300) Configuring DECnet/OSI Network Management over TCP/IP ... done. Creating directories and symbolic links for DNADLI300 ... done. Configuring "DECnet/OSI Datalink Components " (DNADLI300) Creating directories and symbolic links for DNABASE300 ... done. Configuring "DECnet/OSI Base Components " (DNABASE300) 2-12 Installing DECnet/OSI for DEC OSF/1 Creating directories and symbolic links for DNAINETGW300 ... done. Configuring "DECnet-Internet Gateway " (DNAINETGW300) Creating directories and symbolic links for DNAMAN300 ... done. Configuring "DECnet/OSI Reference Pages " (DNAMAN300) Creating directories and symbolic links for DNAMOP300 ... done. Configuring "DECnet/OSI MOP Utilities " (DNAMOP300) Creating directories and symbolic links for DNAUTIL300 ... done. Configuring "DECnet/OSI Miscellaneous Software " (DNAUTIL300) Creating directories and symbolic links for DNAPGMR300 ... done. Configuring "DECnet/OSI Programming Tools " (DNAPGMR300) Creating directories and symbolic links for DNARFC1006300 ... done. Configuring "DECnet/OSI RFC1006 (OSI/TCP) " (DNARFC1006300) Creating directories and symbolic links for DNAAPP300 ... done. Modifying /etc/magic ... done. Configuring "OSI Applications " (DNAAPP300) Creating directories and symbolic links for DNAAPPGWY300 ... done. Configuring "OSI Application Gateways " (DNAAPPGWY300) Creating directories and symbolic links for DNAAPPMAN300 ... done. Configuring "OSI Application On-line Docs " (DNAAPPMAN300) Installing CTF for DEC OSF/1 Systems Collector Components (c) Digital Equipment Corporation. 1994. All Rights Reserved. Creating directories and symbolic links for CTABASE130 ... done. Configuring "CTF Collector Components " (CTABASE130) Installing CTF for DEC OSF/1 Systems User Environment (c) Digital Equipment Corporation. 1994. All Rights Reserved. Creating directories and symbolic links for CTAANAL130 ... done. To complete your installation of DECnet/OSI for DEC OSF/1 AXP V3.0-0, please perform the following steps: - Build a new kernel by executing the command: # /usr/sbin/decnetsetup kernel - Reboot the system, to use this new kernel. - Configure or reconfigure DECnet/OSI by executing the command: # /usr/sbin/decnetsetup [basic|advanced] Installing DECnet/OSI for DEC OSF/1 2-13 Please refer to the Installation Guide for details. To complete your installation of the OSI Applications, please take the following steps: - Ensure that DECnet/OSI for DEC OSF/1 is properly installed and configured. - Configure the OSI Application software by executing the command: # /usr/sbin/osiapplsetup - After verifying that the system is operating properly, you may wish to remove the following saved file: /etc/magic.sav[n] Please refer to the Installation Guide for details. No further questions. 2.2.5 Subset Post-Installation Notes After the DECnet/OSI subsets have been installed, the procedure displays the remaining steps that are needed to finish the configuration of DECnet/OSI. If the installation procedure determines that your kernel has all the components required by DECnet/OSI, then a kernel rebuild is not necessary. The procedure instructs you to perform the following step: # /usr/sbin/decnetsetup [basic|advanced] However, if the installation procedure determines that your kernel does not meet the DECnet/OSI requirements, it will instruct you to perform the following steps: # /usr/sbin/decnetsetup kernel # reboot After the system has rebooted, perform this step: # /usr/sbin/decnetsetup [basic|advanced] 2-14 Installing DECnet/OSI for DEC OSF/1 2.3 Rebuilding the Kernel After you copy the subsets to your disk, rebuild the DEC OSF/1 kernel. The command you use to do this depends on the type of configuration you are performing: a standard configuration (see Section 2.3.1) or an RFC1006 only configuration (see Section 2.3.2). 2.3.1 Standard Kernel Rebuild Command Use the following command to perform a standard kernel rebuild: # /usr/sbin/decnetsetup kernel The script displays the following information. Answer yes when the prompt asks if you want to rebuild your kernel: DECnet/OSI for DEC OSF/1 AXP V3.0-0 DECnet/OSI Configuration Procedure. There will be a pause while this procedure gathers some information from your system. (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. Proposed Kernel Configuration Information DECnet/OSI Base (dynamically loaded) DECnet/OSI Datalink (dynamically loaded) DECnet/OSI Network Management (dynamically loaded) DECnet/OSI RFC1006 (OSI/TCP) (dynamically loaded) Common Trace Facility (CTF) (dynamically loaded) DEC OSF/1 X/Open Transport Interface (statically loaded) Your system's current kernel does not support the proposed configuration. The DEC OSF/1 X/Open Transport Interface kernel component, which is required by DECnet/OSI, is not built into this system's current kernel. A new kernel should be built at this time. This procedure can now either "build" the proposed kernel, "restart" the configuration process, or "exit" decnetsetup. Which would you like to do now? (build/exit/restart/?) [build]: The rest of the procedure will take approximately 15 minutes to rebuild your kernel, depending on the processor type. Installing DECnet/OSI for DEC OSF/1 2-15 If the DEC WAN Device Drivers (WANDD) or X.25 product is installed on your system, the configuration script displays a message asking if you want to build support for this software into your kernel. If you answer yes, the kernel rebuild script for the subset appears. Refer to the X.25 Configuration Guide for a description of the X.25 configuration procedure. Configuring "CTF Collector Components " (CTABASE120) Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL101) ZZAUTIL101 Configured. Checking for CTF support in sys/net/netaf_config.c Adding CTF support to sys/net/netaf_config.c ... done. CTABASE120 configured. 2.3.2 RFC1006 Only Kernel Rebuild Command To build rfc1006 support into the kernel, issue the following command: # rfc1006setup kernel Once the kernel builds and you reboot, see Chapter 7 and Chapter 8 for information on installing and configuring the FTAM and VT OSI applications, or refer to the installation guide for any layered product that uses RFC1006. 2.3.3 Kernel Rebuild Completion Both the standard configuration and the RFC1006 configuration procedures check to see if you have enough disk space to hold the new kernel. If there is not enough disk space, the procedure gives you an informational message and continues. Before the procedure builds the new kernel, it modifies your system files. Before modifying any files, the procedure saves each one in the file form: filename.savn where n is a version number that increments with each installation. 2-16 Installing DECnet/OSI for DEC OSF/1 Starting kernel rebuild... *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** Saving /sys/conf/AGN2AU as /sys/conf/AGN2AU.bck Do you want to edit the configuration file? (y/n) [n]: *** PERFORMING KERNEL BUILD *** Working....Tue Nov 1 15:04:43 EST 1994 Working....Tue Nov 1 15:06:43 EST 1994 Working....Tue Nov 1 15:08:44 EST 1994 The new kernel is /sys/AGN2AU/vmunix Kernel built successfully Saving /vmunix Moving /sys/AGN2AU/vmunix to /vmunix Please reboot the system now, then run /usr/sbin/decnetsetup BASIC or /usr/sbin/decnetsetup ADVANCED to configure DECnet/OSI on this system. decnetsetup completed successfully. If there is enough space in /, the procedure saves the current vmunix and moves the newly created kernel to the root partition /. If there is not enough space, the procedure provides directions on how to move the kernel manually. There is not enough space on your root partition (/) to hold the new kernel. Please make more space available on this partition. The new kernel is approximately 9448 KB in size. Please move your new kernel, /sys/EZ/vmunix, to the root partition after making more space available. WARNING: If you fail to successfully copy the new kernel to /vmunix, the current kernel, because of lack of space, then your system will fail to reboot. Use the command: # more /usr/share/dna/kernel_install_notes.txt to find out more about how to install your new kernel if you are not familiar with OSF kernel installation procedures. Creating /usr/share/dna/kernel_install_notes.txt Installing DECnet/OSI for DEC OSF/1 2-17 2.3.4 Upgrading DECnet/OSI If you previously installed DECnet/OSI onto your system, the installation procedure checks to see if the following files exist on your system: o /usr/sbin/decnetstartup o /usr/sbin/decnetshutdown o /var/dna/scripts/start_datalink.ncl o /var/dna/scripts/start_routing.ncl o /var/dna/scripts/start_*_transport.ncl (where * is NSP, OSI, or both) o /var/dna/decnetsetup_defaults If all of the files in the list are on your system, the following information appears: Your system currently has a DECnet/OSI startup procedure and NCL initialization scripts. If you have just finished upgrading your DECnet/OSI software and do not need to reconfigure your system, you may choose to start DECnet/OSI after the system is rebooted. Do you want to start DECnet/OSI when the system is rebooted? (y/n) [y] If yes, the DECnet/OSI startup commands are linked to /sbin /rc3.d/S28.60decnetosi and DECnet starts the next time you reboot the system. If no, the system prompts you to run decnetsetup after you reboot the system. Please reboot the system now, then run decnetsetup [basic|advanced] to configure DECnet/OSI on this system: 2.3.5 Kernel Rebuild Errors If the kernel does not build, the installation procedure stops. Check the contents of /sys/HOSTNAME/errs for the compile or load errors. Refer to the Guide to System Administration for additional information about kernel rebuild errors. When you have solved the problem, restart the kernel rebuild. 2-18 Installing DECnet/OSI for DEC OSF/1 2.3.6 Kernel Requirement - DEC OSF/1 X/Open Transport Interface DECnet/OSI requires that the DEC OSF/1 kernel contain the X/Open Transport Interface option before DECnet/OSI will allow configuration to take place. As outlined in the DEC OSF/1 release notes, choosing the "Advanced Installation" option in your DEC OSF/1 installation allows the easiest path to getting DECnet /OSI up and running. If the system was upgraded from DEC OSF/1 V2.0 or if you choose a "Basic Installation" of DEC OSF/1, then your kernel will not contain the X/Open Transport Interface. The DECnet/OSI installation process will notice this and guide you through adding it to your kernel. 2.4 Rebooting Your System Once you rebuild the kernel, reboot your system to configure DECnet and finish the installation process. To reboot your system, use your system specific shutdown procedure or issue this command: # /sbin/reboot 2.5 Choosing a Configuration Procedure Once you copy the subsets and rebuild your kernel, you must configure the software by supplying information about your system. The decnetsetup configuration utility has two modes, Basic and Advanced. Table 2-1 provides guidelines for choosing the appropriate configuration procedure. Installing DECnet/OSI for DEC OSF/1 2-19 Table_2-1_Configuration_Procedures_________________________ Chapter 3 Chapter 4 DECnet- Basic Advanced Internet ___________________________Config.____Config.____Gateway[1] You will use the Local namespace. Your system will be a DECdts clerk only. Your system will be a DECdts server. You will use multiple communications controllers. Your system will have WANDD devices. Your system will be a DECnet-Internet gateway. [1]The_DECnet-Internet_Gateway_can_be_configured_during____ the advanced configuration procedure (see Section 4.12) or after the basic configuration procedure (see Section 3.11). ___________________________________________________________ 2-20 Installing DECnet/OSI for DEC OSF/1 3 _________________________________________________________________ Basic Configuration This chapter discusses the following about basic configuration: o When to use the basic configuration procedure and how to start it. o Specifying your DECnet/OSI node name and node synonym. o Communicating with Phase IV nodes. o Configuring for token ring communications device. o Starting DECnet/OSI software. o Configuring DECdns or the Local namespace, the DECnet- Internet Gateway, and OSI applications software. 3.1 When to Use the Basic Configuration Use the basic DECnet/OSI configuration procedure if: o You are using a Local namespace, or your system is a DECdns clerk in a distributed namespace. o Your system is a DECdts clerk only. o You have only one communications device, or you have multiple devices, all of which are used for DECnet/OSI communications. 3.1.1 Basic Configuration Defaults The basic configuration procedure uses the default values described in the following sections to configure your system. Basic Configuration 3-1 3.1.1.1 Phase IV Prefix Basic configuration uses 49:: as the default value for the Phase IV prefix. Note that this is updated by an adjacent DECnet/OSI router if the network uses a different value. 3.1.1.2 Node Synonym Directory Basic configuration provides the default value for the node synonym directory. If you have an environment variable for decnet_migrate_dir_synonym defined, the default value for the node synonym directory is defined by that variable. If you do not use an environment variable, the default value is .DNA_NodeSynonym. 3.1.1.3 Configuring the Name Service Search Path During configuration, the system administrator specifies the node's full name properly formatted for the name service to be searched first. From this information decnetsetup constructs a properly formatted full name for the name service to be searched next and places this information in the search path file. See Section 3.1.4.1 for more information. The ordering of the name services is very important. The format of the full name you specify determines which name service is to be searched first when looking up namesand addressing information. The other name service is searched second. See Section 3.1.4 for more information about the search path. 3.1.1.4 Configuring Network Addresses Basic configuration allows the system to autoconfigure network addresses. 3.1.2 Use the Checklist Before you run the basic configuration procedure, fill out the checklist shown in Figure 3-1 to ensure you have all necessary information. 3-2 Basic Configuration Figure 3-1 Basic Configuration Checklist 3.1.3 About the Basic Configuration Procedure The configuration procedure displays a series of questions that prompt you for information about your system's configuration. Appendix A shows a log of a sample basic configuration. The following list describes the information you are asked to provide for your system during the basic configuration script. Some of the information is optional and depends upon your system's configuration. o DECnet/OSI (Phase V) node name o Phase IV compatible synonym o Phase IV compatible node address At the end of the configuration procedure, you are prompted to confirm the configuration values that you entered. You can: o Quit the procedure without saving the values. o Save the entries and exit the procedure. o Restart the procedure. o Continue with the configuration by starting the DECnet /OSI software. 3.1.3.1 Changing Your Answers Do not be concerned if you make a mistake or supply the wrong information for a question. You are asked to confirm your answers before DECnet/OSI is actually configured, so you can use that opportunity to restart the configuration procedure and change your answers. Basic Configuration 3-3 3.1.3.2 Default Values Many of the questions have default values associated with them. This information is contained in brackets at the end of the question, as in this example: What is the Phase IV compatible synonym? [WillyL]: If the default value, in this case WillyL, is correct, press . If you are rerunning this procedure, the default values are based on the information that you supplied previously. 3.1.3.3 Stopping the Configuration Procedure You can review your answers to the prompts and exit the configuration procedure before the system begins to configure DECnet by typing . Do not stop the configuration process once it starts to configure the DECnet/OSI software. To change any information after this point: finish the configuration, shut down DECnet, then rerun the procedure with the new information. 3.1.3.4 Getting Help The configuration procedure prompts you for information. If you need help responding to any of these prompts, type a question mark (?) and press to view the help text. 3.1.4 The Name Service Search Path The name service search path applies system-wide and allows DECnet/OSI to search a list of name services in a predetermined order when looking up names or addressing information. The primary name service (the name service to be searched first) is listed before the secondary name service (the name service to be searched second). The ordering of the name services is very important. The first name service listed is the primary name service to use on the system. The primary name service is considered the first choice to use when looking up names and addressing information. The remaining name services listed are considered to be the secondary services to use on the system. 3-4 Basic Configuration The search path contains a list of name service keywords each followed by a naming template that specifies a "defaulting rule" so that users can enter shorter node names. In each template, the user-supplied portion of the name (usually the node's terminating name or right- most simple name) is indicated with an asterisk (*). For example, if the DECdns template is: "ABCDE:.xyz.*" and a user supplies the name foo, then the following full name: ABCDE:.xyz.foo will be looked up in namespace ABCDE in the DECdns name service. Only one asterisk should be supplied per template. Only the first occurrence of an asterisk (*) in the template is substituted with the user-supplied name. Any additional asterisks are passed to the name service as part of the full name. When you specify a template without an asterisk, the template string is passed to the name service unchanged. If the user-supplied name should be passed to the name service as entered by the user, the template should simply be specified as follows: "*". Note that the search path information for a system is maintained in two separate search paths: o One search path is maintained for forward translation or naming (node name to address translation). o Another separate search path is maintained for backtranslation (address to node name translation). 3.1.4.1 Configuring the Search Path Information During DECnet/OSI configuration, the system administrator uses decnetsetup to set up one or more name services on each node. From the information provided by the system administrator, decnetsetup creates /var/dna/decnet- dirsvc.conf, which contains the name service search path information for the node. Do not edit this file. If it is necessary to make changes to /var/dna/decnet-dirsvc.conf, use the NCL set commands described in Section 3.1.4.2 to modify the naming templates or rerun decnetsetup to designate a new primary name service and reverse the order in which the name services are searched. Basic Configuration 3-5 The name service search path describes both the order in which the name services are to be searched and how DECnet /OSI should interpret any abbreviated node names entered by users. During DECnet/OSI configuration, the system administrator specifies the node's full name properly-formatted for the name service to be searched first. From this information decnetsetup constructs a properly-formatted full name for the name service to be searched next. With this release, DECnet/OSI supports the Local namespace, the DECdns distributed name service, or both. If both name services are used, they are searched in order as previously described. If the system administrator specified a full name beginning with the prefix LOCAL: (or local:), DECnet/OSI searches the Local namespace first for forward and back translation information. If DECnet/OSI either does not find a Local namespace or if the Local namespace does not contain name and addressing information for the specified node, then DECnet/OSI searches the DECdns namespace. Similarly, if the system administrator specified a full name containing a namespace nickname for a DECdns namespace (for example, ABCDE:.xyz.abc), then DECnet/OSI searches the specified DECdns namespace (ABCDE:) first for forward and back translation information. If it does not find information for the node, DECnet/OSI then searches the Local namespace. 3.1.4.2 Modifying the Naming and Backtranslation Search Paths Digital recommends that the system administrator rerun decnetsetup to create a revised /var/dna/decnet-dirsvc.conf file whenever the name service information for the node requires modification. Whenever you run decnetsetup, you are prompted to reenter your node full name including the Local: prefix or the DECdns namespace nickname to specify the primary name service. When you use NCL commands to modify the search path information, you cannot change the node full name; therefore, you cannot use NCL commands to change the order in which the name services are searched. 3-6 Basic Configuration The following NCL set commands modify existing naming and backtranslation naming templates for a system: > ncl set session control naming search path = { - [directory service=local,template=*], - [directory service=local,template=local:.*], - [directory service=local,template=LOCAL:*], - [directory service=DECdns,template=*]} > ncl set session control backtranslation search path = { - [directory service=local,template=*]} 3.2 Starting the Configuration Procedure Before starting the configuration procedure, create a log file of the configuration process to keep track of the configuration options you have selected. Use the following command to create the log file: #script /var/dna/filename.log After you complete the configuration procedure, press or type exit to save the log file. To start the basic configuration procedure, issue this command: #/usr/sbin/decnetsetup basic The procedure begins the configuration by displaying these informational messages: DECnet/OSI for DEC OSF/1 OSF AXP V3.0-0 DECnet/OSI Configuration Procedure. There will be a pause while this procedure gathers some information from your system. 3.3 Specifying Your DECnet/OSI Node Name As you continue the configuration, the next step is to specify your DECnet/OSI node name. The DECnet/OSI node name is the full name of the node in the DECdns namespace or Local namespace. You must include your namespace nickname as part of the full name. The node name uses the form: Basic Configuration 3-7 NamespaceNickname:.DirectoryPath.NodeObject For the Local namespace, use the prefix local: in place of the namespace nickname. DECnet/OSI recognizes that a node full name beginning with the local: in place of the DECdns namespace nickname is stored in the Local namespace. In this case, the node name uses the form: Local:.DirectoryPath.Nodename The ordering of the name services is very important. The format of the full name you specify determines which name service is to be searched first when looking up names and addressing information. The other name service is searched second. See Section 3.1.4 for more information about the search path. Enter your DECnet/OSI (Phase V) node name at the prompt: What is the Phase V node name? [no default]: These are the guidelines for selecting a node name: o The node name must begin with the nickname and a colon (:). o The directory path must begin with a dot (.). o The node name can be up to 255 characters long. o No part of the name can be a null string. o The only valid unquoted characters are letters, numbers, hyphens (-), underscores (_), and dollar signs ($). o Some other characters are allowed if they are enclosed in quotation marks. You can find a list of these characters in Appendix A of DECdns Management. The following are some examples of DECnet/OSI node names: LOCAL:.TomThumb vbo:.afsg.comms.werner XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter 3-8 Basic Configuration DECnet/OSI node names should be planned carefully and must be unique within the namespace. If your network administrator has not assigned a unique node name for your system, be sure that you read DECnet/OSI Planning Guide before you assign a node name for your system. This book also contains guidelines for using the Local namespace and information on how to set up a distributed or local namespace. 3.3.1 Using a Local Namespace The Local namespace is a discrete, nondistributed namespace that exists on a single node and provides that node with a local database of name and addressing information. Depending on the number of address towers stored, the Local namespace is designed to scale to at least 100,000 nodes. The prefix LOCAL: (or local:) is reserved to indicate that the information for a node is stored in the Local namespace. DECnet/OSI recognizes that a node full name beginning with LOCAL: is stored in a Local namespace. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum. Unlike DECdns, the Local namespace does not employ backtranslation directories for address to node name translation. You can configure a Local namespace on one node, selected nodes, or all nodes in the network. Use the following format to specify node names when you create a Local namespace: local:.your_nodename When the configuration procedure sees the namespace nickname, local:, the procedure creates the local name file. The file contains node name and addressing information for the nodes you need to access. The procedure then loads the local name file into the Local namespace database. Basic Configuration 3-9 3.3.2 Using a DECdns Distributed Namespace If you plan to use a distributed namespace, the namespace nickname that you specify is the actual name of the distributed namespace where your system is registered. You can find guidelines for using a distributed or local namespace in DECnet/OSI Planning Guide. 3.4 Giving Your System a Node Synonym This step is optional. You do not have to give your system a node synonym. This Phase IV style name is a synonym for the full name stored in the namespace. The node synonym is primarily a transition tool that allows you to use a Phase IV style node name for your DECnet/OSI node. Users and applications can then reference your node using this synonym rather than the full name of the node. If you were using DECnet Phase IV, consider using your Phase IV node name as your synonym. The synonym is required for Phase IV applications that can only handle Phase IV style node names. If your network has only DECnet/OSI or OSI systems, you may not need a synonym. 3.4.1 Specifying your Node Synonym The configuration asks if you want to give your system a node synonym. The default node synonym is the first six characters of the node object. The synonym can be between one and six characters long and must be unique within your namespace. The node object is the string that follows the last period of your full name. For example, if you specify XYZ_CORP:.sales.west_coast.WillyLoman as a DECnet/OSI full name, the node object is WillyLoman and your default node synonym is WillyL. The following example shows a default node synonym: What is the Phase IV compatible synonym? [WillyL] At this prompt, you can: o Accept the default synonym by pressing . o Enter a new synonym and press . o Type two quotation marks ("") and press if you do not want to specify a synonym at this time. 3-10 Basic Configuration If you want to give your system a node synonym later, use the decnet_register tool. 3.5 Communicating with Phase IV Nodes If your system needs to communicate with Phase IV nodes, you need a Phase IV compatible address. A DECnet Phase IV compatible address conforms to the Phase IV area and node limits; the area number is from 1 to 63, and the node number is from 1 to 1023, as in this example: 36.515. If there are no Phase IV systems on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV compatible address. If you do not want a Phase IV compatible address, go to Section 3.8. 3.5.1 Supplying an Address Supply a Phase IV compatible address at this prompt: What is the Phase IV compatible node address? [0]: If you want your system to be able to communicate with Phase IV nodes, enter a Phase IV compatible address in response to the question. If you do not want a Phase IV compatible address, enter the number 0 and press . If you are unsure of your Phase IV compatible node address, contact your network manager. 3.6 Configuring a Token Ring Communications Device If you have an unconfigured Token Ring communications device, you must supply a ring speed for the device at this prompt: The Token Ring interface operates at 16 Mbs or 4 Mbs. Please specify the speed at which the adapter should enter the ring. Enter the Token Ring speed [16]: Basic Configuration 3-11 The Token Ring interface operates at one of two speeds, 4 MB per second, or 16 MB per second. All stations connected to the same ring must be configured to operate at the same speed. Determine the correct speed at which this device should run, by checking the speed of existing Token Ring stations or checking with the network manager. If your device is already configured or you do not have token ring, you are not prompted for the information. 3.6.1 Setting the Token Ring Station Speed DECnet/OSI for DEC OSF/1 stations in a Token Ring LAN can operate on either 4 or 16 MB per second data rates. A station can insert onto a Token Ring only at the ring's established data rate (ring speed). The station's ring speed can be set either by using the netsetup utility to configure the station's Token Ring adapter, or by the decnetsetup utility. Be aware of the ring speed of the Token Ring LAN where the station is to be inserted. If the ring speed is set to the wrong value then the ring insertion process will fail. If the station fails to insert or connect correctly, messages appear in the Session Manager window: vmunix: tra0: MAC_OPEN : tra0: Ring status: Ring recovery vmunix: Open error: Phase: Physical insertion; You can also query the state of the Token Ring adapter. For example: # ifconfig tra0 tra0: flags=8822 This indicates that the adapter is not active and that the station failed to insert on to the ring. The station has successfully inserted on to the ring if the same command yields: # ifconfig tra0 tra0: flags=8863 3-12 Basic Configuration 3.7 Running MOP Standalone To configure and run MOP standalone without the rest of DECnet/OSI, do the following: 1. Install the DNANETMAN300, DNADLI300, and the DNAMOP300 subsets # setld -l DNANETMAN300 DNADLI300 DNAMOP300 2. Configure MOP (which also performs the needed DLI and NETMAN configuration): # /usr/sbin/mopsetup 3.8 Confirming Your Answers and Starting the DECnet/OSI Software Before the configuration procedure actually configures your system, it asks you to confirm your answers for these values for your system: o Full DECnet/OSI name o Node synonym (if you have one) o Phase IV address (if you have one) o DECdts role (clerk) o Namespace option (DECdns clerk or Local namespace) There are four ways to proceed: 1. If you are satisfied with your answers, to continue the configuration type continue and press . The procedure configures your system and saves your answers in a default file to use if you rerun the procedure. 2. If you want to change one (or more) of your answers, type restart and press . This action starts the configuration procedure again from the beginning with your previous answers supplied as default values to each question. 3. If you are satisfied with the answers but you do not want to continue to configure your system, type stop and press . This stops the configuration procedure and saves your answers in a defaults file. Basic Configuration 3-13 4. If you want to exit the configuration procedure and do not want to save your answers in a defaults file, type quit and press . This example shows how to respond if you are satisfied with the answers you supplied: Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: XYZ_CORP:.sales.west_coast.WillyLoman Node Synonym: WillyL Phase IV Address: 36.515 Phase IV Prefix: 49:: Network Devices: ln0 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will be a DECdns clerk in the XYZ_CORP namespace. Do you wish to complete this DECnet/OSI configuration? [continue] If you continue (c), the procedure: o Creates startup files. o Modifies system files. o Starts up the DECnet software. Once the procedure starts to configure DECnet, do not stop it. During the start-up process, you receive informational messages similar to these: Creating defaults file. Creating Initialization NCL scripts Creating /usr/sbin/decnetstartup Creating /usr/sbin/osi_applstartup Updating /var/dna/dna_version Creating /usr/sbin/decnetshutdown Event Logging ... 3-14 Basic Configuration Configuring "CTF Collector Components " (CTABASE130) Ensuring all underlying dependencies are configured. ++++++++++++++++++++++++++++++ Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) Adding WAN lock entries to /sys/kern/lockinfo.c ... done. ZZAUTIL110 Configured. ------------------------------ CTABASE130 configured. Creating Session Control Creating /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Attempting to contact local DNS server...please wait. DNS clerk successfully configured. Node name reset to XYZ_CORP:.sales.west_coast.WillyLoman DTSS ... Node Enabled ... Event Logging Event Logging ... The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/rfc1006 32 57 DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/xtiso/cots 32 58 /dev/streams/xtiso/clts 32 59 Setting Session Control attributes 3.9 Configuring Your Namespace Once DECnet/OSI starts, the configuration procedure configures your system and attempts to register it in the namespace you specified in your DECnet/OSI full name (see Section 3.3). Basic Configuration 3-15 3.9.1 Using Local Namespace If you are using a Local namespace, the configuration procedure configures your system, then registers it in the Local namespace. The script displays informational messages similar to the following: There will be a brief pause as the dec namespace is checked, to see if this node is already registered. This node is registered in the dec namespace. Updating address towers for node object XYZ_CORP:.sales.west_coast.WillyLoman ... done The configuration of DECnet/OSI is completed. Refer to DECnet/OSI Network Management for information on how to manage node names in the Local namespace. 3.9.2 DECdns Clerk Configuration If you are using a distributed namespace, the configuration procedure checks to see if a DECdns server for your namespace is on the same LAN as your system. If it is, the server is automatically recognized, and your system is registered using that server. In this case, you receive a completion message similar to this one: Attempting to contact local DNS server...please wait. DNS clerk successfully configured Next, the configuration procedure attempts to register your system in the distributed namespace and displays a message at the end of the operation similar to this: This node is registered in the XYZ_CORP namespace. If the automatic registration is successful, the basic configuration is complete. You can proceed to Chapter 6 for instructions on how to verify the configuration. If the procedure is unable to register your node, or if your namespace does not allow automatic registration, a message informs you that you must manually register your system. Your configuration has finished, however, you cannot fully communicate with other systems or run the installation verification procedure until your system is registered in the namespace. Refer to DECnet/OSI Network 3-16 Basic Configuration Management for information on manually registering a system in a distributed namespace. 3.9.2.1 Connecting to a Remote Server In a Distributed Namespace If a DECdns server for your distributed namespace is not found on your LAN, enter the address of the server you want at this prompt: What is the network address of the server: You can respond to this question with the server's Phase IV compatible address (if it has one) or with the server's network service access point (NSAP). The NSAP is the NET with a valid transport selector. To find this information, contact the system administrator for that server. The administrator can get this information by running the dnsconfigure utility on the server and selecting the menu option, Show address information of this node. The server system may have a number of different NSAPs. You can use any of these NSAPs to connect to the server system, but you must enter the NSAP in the displayed format. After you enter your server's address, your system connects to the server and displays a confirmation message listing your namespace nickname and its namespace creation time stamp (NSCTS), as in this example: Your default namespace nickname is XYZ_CORP Your default namespace NSCTS is 00-12-34-56-77-A0-A1-A2-A3-A4-A5-A6-A7-B0 If you fail to connect to the remote server, you must reboot your system before you try to reconfigure DECnet /OSI. ________________________ Note ________________________ If you are joining a DECdns Version 1.1 namespace, make sure you have access to the remote server's sys$system:dns$default_file.dat. Refer to DECdns Management for more information. ______________________________________________________ Basic Configuration 3-17 3.10 Verifying the Basic Configuration Procedure Once your system is registered in the namespace, the installation and configuration are finished. If necessary, perform the postinstallation tasks in Chapter 5, and then proceed to Chapter 6. Chapter 6 includes instructions on how to run the /usr/sbin/dnet_check installation verification procedure (IVP). This procedure tests and exercises your DECnet/OSI communications software to ensure that you configured the software properly. 3.11 Configuring the DECnet-Internet Gateway If you installed the DECnet-Internet Gateway subset, you can configure the software after you complete the basic installation. Use the following command: # /usr/sbin/decnetsetup gateway 3.12 Configuring the OSI Applications Software If you installed the OSI Applications subsets, you can configure the software after you complete the basic configuration. Use the following command to start the OSI Application configuration procedure: # /usr/sbin/osiapplsetup Chapter 7 and Chapter 8 contain detailed instructions on installing and configuring the OSI Applications. 3-18 Basic Configuration 4 _________________________________________________________________ Advanced Configuration 4.1 When to Use the Advanced Configuration Use the advanced configuration procedure with DECnet/OSI if you have any of the following configuration requirements: o You want to configure your system as a DECdts server. o Your system has multiple communication devices, and you want them to run a mix of protocols (some DECnet/OSI and some Internet, for instance). o You want to configure your DECnet/OSI software to use X.25 services. o You want to manually configure your network addresses. o You want to use an alternate node synonym directory. o You also want to configure the DECnet-Internet Gateway. Before you run the advanced configuration procedure, fill out the checklist shown in Figure 4-1 to ensure you have all necessary information. Figure 4-1 Advanced Configuration Checklist Advanced Configuration 4-1 Figure 4-2 Advanced Configuration Checklist (Part 2) 4-2 Advanced Configuration 4.1.1 About the Advanced Configuration Procedure The configuration procedure displays a series of questions that prompt you for information about your system's configuration. The following list describes the information you are asked to provide for your system during the configuration script. Some of the information is optional and depends on your system's configuration: o DECnet/OSI (Phase V) node name o Phase IV compatible synonym o Phase IV compatible node address o Phase IV Prefix value for this network o Network addresses (automatic or manual address configuration) o Communications devices o DECdts configuration (clerk or server?) o Namespace configuration (DECdns clerk or Local namespace?) o DECnet-Internet Gateway configuration At the end of the configuration procedure, you will be prompted to confirm the configuration values that you entered. You can then choose to quit the procedure without saving the values, save the entries and exit the procedure, restart the procedure, or continue with the configuration by starting the DECnet/OSI software. 4.1.1.1 Stopping the Configuration Procedure You can stop the configuration procedure by typing . You can also review all your answers and optionally exit the procedure before it actually configures DECnet. Do not stop the procedure once it starts to configure DECnet. To change any information after this point, finish the configuration, shut down DECnet, then rerun the procedure with the new information. Advanced Configuration 4-3 4.1.1.2 Changing Your Answers Do not be concerned if you make a mistake or supply the wrong information for a question. You are asked to confirm your answers before DECnet is actually configured and you can use that opportunity to restart the configuration procedure and change your answers. 4.1.1.3 Default Values Many of the questions have default values associated with them. This information is contained in brackets at the end of the question, as in the following example: What is the Phase IV compatible synonym? [WillyL]: If the default value, in this case WillyL, is what you want, just press . If you are rerunning this procedure, the default values are based on the information that you supplied previously. 4.1.1.4 Getting Help The configuration procedure prompts you for information. If you need help responding to any of these prompts, type a question mark (?) and press to view the help text. 4.1.2 The Name Service Search Path The name service search path applies system-wide and allows DECnet/OSI to search a list of name services in a predetermined order when looking up names or addressing information. The primary name service (the name service to be searched first) is listed before the secondary name service (the name service to be searched second). The ordering of the name services is very important. The first name service listed is the primary name service to use on the system. The primary name service is considered the first choice to use when looking up names and addressing information. The remaining name services listed are considered to be the secondary services to use on the system. The search path contains a list of name service keywords each followed by a naming template that specifies a "defaulting rule" so that users can enter shorter node names. In each template, the user-supplied portion of 4-4 Advanced Configuration the name (usually the node's terminating name or right- most simple name) is indicated with an asterisk (*). For example, if the DECdns template is: "ABCDE:.xyz.*" and a user supplies the name foo, then the following full name: ABCDE:.xyz.foo will be looked up in namespace ABCDE in the DECdns name service. Only one asterisk should be supplied per template. Only the first occurrence of an asterisk (*) in the template is substituted with the user-supplied name. Any additional asterisks are passed to the name service as part of the full name. When you specify a template without an asterisk, the template string is passed to the name service unchanged. If the user-supplied name should be passed to the name service as entered by the user, the template should simply be specified as follows: "*". Note that the search path information for a system is maintained in two separate search paths: o One search path is maintained for forward translation or naming (node name to address translation). o Another separate search path is maintained for backtranslation (address to node name translation). 4.1.2.1 Configuring the Search Path Information During DECnet/OSI configuration, the system administrator uses decnetsetup to set up one or more name services on each node. From the information provided by the system administrator, decnetsetup creates /var/dna/decnet- dirsvc.conf, which contains the name service search path information for the node. Do not edit this file. If it is necessary to make changes to /var/dna/decnet-dirsvc.conf, use the NCL set commands described in Section 4.1.2.2 to modify the naming templates or rerun decnetsetup to designate a new primary name service and reverse the order in which the name services are searched. The name service search path describes both the order in which the name services are to be searched and how DECnet /OSI should interpret any abbreviated node names entered by users. Advanced Configuration 4-5 During DECnet/OSI configuration, the system administrator specifies the node's full name properly-formatted for the name service to be searched first. From this information decnetsetup constructs a properly-formatted full name for the name service to be searched next. With this release, DECnet/OSI supports the Local namespace, the DECdns distributed name service, or both. If both name services are used, they are searched in order as previously described. If the system administrator specified a full name beginning with the prefix LOCAL: (or local:), DECnet/OSI searches the Local namespace first for forward and back translation information. If DECnet/OSI either does not find a Local namespace or if the Local namespace does not contain name and addressing information for the specified node, then DECnet/OSI searches the DECdns namespace. Similarly, if the system administrator specified a full name containing a namespace nickname for a DECdns namespace (for example, ABCDE:.xyz.abc), then DECnet/OSI searches the specified DECdns namespace (ABCDE:) first for forward and back translation information. If it does not find information for the node, DECnet/OSI then searches the Local namespace. 4.1.2.2 Modifying the Naming and Backtranslation Search Paths Digital recommends that the system administrator rerun decnetsetup to create a revised /var/dna/decnet-dirsvc.conf file whenever the name service information for the node requires modification. Whenever you run decnetsetup, you are prompted to reenter your node full name including the Local: prefix or the DECdns namespace nickname to specify the primary name service. When you use NCL commands to modify the search path information, you cannot change the node full name; therefore, you cannot use NCL commands to change the order in which the name services are searched. 4-6 Advanced Configuration The following NCL set commands modify existing naming and backtranslation naming templates for a system: > ncl set session control naming search path = { - [directory service=local,template=*], - [directory service=local,template=local:.*], - [directory service=local,template=LOCAL:*], - [directory service=DECdns,template=*]} > ncl set session control backtranslation search path = { - [directory service=local,template=*]} 4.2 Starting the Configuration Procedure Before starting the configuration procedure, you might want to create a log file of the configuration process. You can use this log file to keep track of the configuration options you have selected. Use the following command to create the log file: #script /var/dna/filename.log After you complete the configuration procedure, press or type exit to save the log file. To start the advanced configuration procedure, issue this command: #/usr/sbin/decnetsetup advanced The procedure begins the configuration by displaying these informational messages: DECnet/OSI for DEC OSF/1 AXP V3.0-0 DECnet/OSI Configuration Procedure. There will be a pause while this procedure gathers some information from your system. 4.3 Specifying Your DECnet/OSI Node Name As you continue the configuration, the next step is to specify your DECnet/OSI node name. The DECnet/OSI node name is the full name of the node in the DECdns namespace or the Local namespace. You must include your namespace nickname as part of the full name. The node name uses the form: NamespaceNickname:.DirectoryPath.NodeObject Advanced Configuration 4-7 For the Local namespace, use the prefix local: in place of the namespace nickname. DECnet/OSI recognizes that a node full name beginning with the local: in place of the DECdns namespace nickname is stored in the Local namespace. In this case, the node name uses the form: Local:.DirectoryPath.Nodename The ordering of the name services is very important. The format of the full name you specify determines which name service is to be searched first when looking up names and addressing information. The other name service is searched second. See Section 4.1.2 for more information about the search path. Enter your DECnet/OSI (Phase V) node name at the prompt: What is the Phase V node name? [no default]: These are the guidelines for selecting a node name: o The node name must begin with the nickname and a colon (:). o The directory path must begin with a dot (.). o The node name can be up to 255 characters long. o No part of the name can be a null string. o The only valid unquoted characters are letters, numbers, hyphens (-), underscores (_), and dollar signs ($). o Some other characters are allowed if they are enclosed in quotation marks. You can find a list of these characters in Appendix A of DECdns Management. The following are some examples of DECnet/OSI node names: XYZ_CORP:.sales.west_coast.WillyLoman Mbi:.MIS.Europe.Paris_headquarters.F_Drolet AU:.chemistry$lab.mike$tarantino local:.jharrington DECnet/OSI node names should be planned carefully and must be unique within the namespace. If your network administrator has not assigned a unique node name for your system, be sure that you read DECnet/OSI Planning Guide before you assign a node name for your system. This book also contains guidelines for using the Local namespace 4-8 Advanced Configuration and information on how to set up a distributed or local namespace. 4.3.1 Using a Local Namespace The Local namespace is a discrete, nondistributed namespace that exists on a single node and provides that node with a local database of name and addressing information. Depending on the number of address towers stored, the Local namespace is designed to scale to at least 100,000 nodes. The prefix LOCAL: (or local:) is reserved to indicate that the information for a node is stored in the Local namespace. DECnet/OSI recognizes that a node full name beginning with LOCAL: is stored in a Local namespace. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum. Unlike DECdns, the Local namespace does not employ backtranslation directories for address to node name translation. You can configure a Local namespace on one node, selected nodes, or all nodes in the network. Use the following format to specify node names when you create a local namespace: local:.your_nodename The configuration procedure generates the following local database files in /var/dna: dna_local_name_database_dat.dir dna_local_name_database_dat.pag dna_local_name_database_name.dir dna_local_name_database_name.pag dna_local_name_database_net.dir dna_local_name_database_net.pag dna_local_name_database_syn.dir dna_local_name_database_syn.pag Advanced Configuration 4-9 4.3.2 Using a Distributed Namespace If you plan to use a distributed namespace, the namespace nickname that you specify is the actual name of the distributed namespace where your system is registered. You can find guidelines for using a distributed or Local namespace in the DECnet/OSI Planning Guide. 4.4 Giving Your System a Node Synonym This step is optional. You do not have to give your system a node synonym. This Phase IV style name is a synonym for the full name stored in the namespace. The synonym can be between one and six characters long and must be unique within your namespace. The node synonym is primarily a transition tool that allows you to use a Phase IV style node name for your DECnet/OSI node. Users and applications can then reference your node using this synonym rather than the full name of the node. If you were using DECnet Phase IV, consider using your Phase IV node name as your synonym. The synonym is required for Phase IV applications that can only handle Phase IV style node names. If your network only has DECnet/OSI or OSI systems, you may not need a synonym. 4.4.1 Specifying your Node Synonym The configuration asks if you want to give your system a node synonym. The default node synonym is the first six characters of the node object. The synonym can be between one and six characters long and must be unique within your namespace. The node object is the string that follows the last period of your full name. For example, if you specify XYZ_CORP:.sales.west_coast.WillyLoman as a DECnet/OSI full name, the node object is WillyLoman and your default node synonym is WillyL. The following example shows a default node synonym: What is your Phase IV compatible synonym? [WillyL]: At this prompt, you can: o Accept the default synonym by pressing . o Enter a new synonym and press . 4-10 Advanced Configuration o Type two quotation marks ("") and press if you do not want to specify a synonym at this time. If you want to give your system a node synonym later, you can do so using the decnet_register tool. 4.5 Communicating with Phase IV Nodes If your system needs to communicate with Phase IV nodes, you need a Phase IV compatible address. A DECnet Phase IV compatible address conforms to the Phase IV area and node limits; that is, the area number is from 1 to 63, and the node number is from 1 to 1023, as in this example: 36.515. If there are no Phase IV systems on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV compatible address. If you do not want a Phase IV compatible address, go to Section 4.7. 4.5.1 Supplying an Address Supply a Phase IV compatible address at this prompt: What is your DECnet Phase IV compatible node address ? [0]: If you want your system to be able to communicate with Phase IV nodes, enter a Phase IV compatible address in response to the question. If you do not want a Phase IV compatible address, enter the number 0 and press . If you are unsure of your Phase IV compatible address, please contact your network manager. 4.5.2 Supplying a Phase IV Prefix If you choose to use a Phase IV compatible address, you must supply an additional piece of addressing information called a Phase IV prefix. DECnet/OSI systems reference all network addresses (including Phase IV addresses) using OSI address formats (NSAPs). The Phase IV prefix and the Phase IV node address are used to construct a complete NSAP for this system. The DECnet/OSI systems within a single routing domain use this Phase IV prefix to form the Phase IV compatible NSAP. This prefix consists of the OSI address initial domain part (IDP) and possibly the preDSP portion (sometimes known Advanced Configuration 4-11 as the high order DSP) of the domain specific part (DSP). Appendix D contains more information about NSAP formats. Enter your Phase IV prefix at this prompt: What is the Phase IV Prefix value for this network? [49::] The default value for the prefix is the number 49::, which specifies that your system will be part of a private local network. This value is generally appropriate for networks that will not be interconnected with other OSI networks. If your network is going to be connected with other OSI networks, you must enter a globally unique IDP. If your organization has allocated its own IDP, you can enter that value instead of 49::. If you are in doubt about which prefix value to use, contact your network manager. ________________________ Note ________________________ If you are using an IDP other than 49::, the IDP must be globally unique. Your IDP must be assigned by an authorized standards organization, like ANSI, or you must construct an IDP that you know will be unique (based on your telephone number, for instance). You can find out more information about IDPs by typing ? in response to the prompt. Appendix D contains a detailed description of how to construct an IDP and how to apply to a standards organization for an IDP. ______________________________________________________ 4.6 Using an Alternate Node Synonym Directory If you have a large network and would like to use an alternate node synonym directory rather than using the default node synonym directory of .DNA_NodeSynonym, you may enter one at the following prompt. The value for the alternate node synonym directory must be a DECdns directory full name (for example: .USA_Synonyms). What is the node synonym directory in the XYZ_CORP namespace? [.DNA_NodeSynonym]: 4-12 Advanced Configuration 4.7 Configuring Network Addresses Your system must have at least one unique network address in order to use DECnet/OSI communications features. DECnet /OSI systems can be multihomed, that is, they can have more than one network address. DECnet/OSI allows you to have up to three network addresses. Having multiple addresses allows you to have both a DECnet /OSI extended address and a Phase IV compatible address, so you can communicate with both Phase IV and DECnet/OSI systems on the same network. It also allows you to belong to more than one OSI network. This feature is particularly useful when you need to combine two (or more) networks. Rather than have all the systems in both networks get new addresses that reflect the new combined network, those systems that need to participate in both networks can have an address in each one. Network addresses are sometimes referred to in OSI terminology as network entity titles (NETs). NETs are NSAPs with a selector of 00. There are two ways to configure NETs: by autoconfiguring addresses, or by manually configuring addresses. 4.7.1 Choice 1: Autoconfiguring Addresses This method is the easiest way to configure NETs. If you have a DNA Phase V conformant router (or Intermediate System, IS) adjacent to your system (on the same LAN or connected to your system by a point-to-point link), you can let the router supply your node with network addresses. If you are configuring your system as part of a DNA Phase V environment, you should answer Yes to the autoconfiguration question. If the network is a heterogeneous OSI environment, answer No in order to manually configure your system's network address(es). If you select autoconfiguration, all IDPs are set to the IDP used by the router. Select autoconfiguration by answering yes to the following question. Then go to Section 4.8. Will this system autoconfigure its network addresses? [y]: Advanced Configuration 4-13 4.7.2 Choice 2: Manually Configuring Addresses If you answer no to the autoconfiguration question, you have to manually configure your NETs. In this case, your network manager must supply them to you or you must construct them yourself. If you know which NETs to use, you can continue to configure DECnet. If you have to construct your own NETs, refer to Appendix D for instructions and continue this configuration only when you know which NETs to use. When you manually configure NETs, the procedure prompts you for network addresses. You have to respond with at least one NET and you can supply up to three of them. This example shows how you would specify two NETs: This system's current Node ID is: 08-00-2B-16-A8-72 Enter a Network Entity Title [0] (Enter 0 to continue): 39:250:FF-00-41:08-00-2B-16-A8-72:00 Enter a Network Entity Title [0] (Enter 0 to continue): 49::00-70:08-00-2B-16-A8-72:00 Enter a Network Entity Title (Enter 0 to continue): 0 NETs must be entered in DNA format, which uses colons to separate fields and dashes to separate pairs of digits. Make sure that you include the 00 selector when you manually specify a NET. For more information on DNA and OSI NET formats, see Section D.3. The procedure presents you with a different series of prompts depending on whether you have specified a Phase IV compatible address. 4.7.2.1 If You Have a Phase IV compatible Address If you are using a Phase IV compatible address, your NETs are used for the following purposes: o The first NET is your Phase IV compatible address. Though this address is used to communicate with Phase IV systems, it is translated into OSI address format. When you supply a Phase IV compatible address and prefix, the configuration procedure uses them to build a NET for you, which it then displays. For example: 4-14 Advanced Configuration This system's current Node Id is 08-00-2B-16-A8-72 Setting the first NET (based on Phase IV compatible address and Phase IV Prefix) to: 49::00-24:AA-00-04-00-03-92:00 You cannot modify this NET. For more information on how Phase IV addresses are translated into OSI address format, see Appendix D. o The second NET is an additional DECnet/OSI address. You may enter a NET in response to the question. If you do not want another DECnet/OSI address, enter the number 0 and press . If you do this, you are not prompted for a third NET. o The third NET is also an additional DECnet/OSI address. If you do not want another DECnet/OSI address, enter the number 0 and press . 4.7.2.2 If You Do Not Have a Phase IV compatible Address If you are not using a Phase IV compatible address, your NETs are used for the following purposes: o The first NET is your first DECnet/OSI address. You must enter a NET in response to the question. o The second NET is an additional DECnet/OSI address. If you do not want another DECnet/OSI address, enter the number 0 and press . If you do this, you are not prompted for a third NET. o The third NET is also an additional DECnet/OSI address. If you do not want another DECnet/OSI address, enter the the number 0 and press . 4.8 Selecting from Multiple Communications Devices The configuration procedure can tell whether your system has more than one communications device. If there are multiple devices, the procedure displays the names of the devices and asks you to specify the devices you plan to use for DECnet/OSI communications. You can supply up to four communications device names. Advanced Configuration 4-15 The following example shows how you would select two of four communications devices to use with DECnet/OSI. Enter the list of communications devices where you will be running the DECnet/OSI software. If there is more than one device, separate them by spaces [te0 te1 fza0] fza0 If you only have one communications device, accept the default device by pressing . DECnet/OSI for DEC OSF/1 supports the following communications devices: o For CSMA/CD communications: xna, ln, ne, te o For HDLC communications: dsy, sscc o For FDDI communications: fza, fta, mfa o For Token Ring communications: tra 4.9 Configuring a Token Ring Communications Device If you have an unconfigured Token Ring communications device, you must supply a ring speed for the device at this prompt: The Token Ring interface operates at 16 Mbs or 4 Mbs. Please specify the speed at which the adapter should enter the ring. Enter the Token Ring speed [16]: The Token Ring interface operates at one of two speeds, 4 MB per second, or 16 MB per second. All stations connected to the same ring must be configured to operate at the same speed. Determine the correct speed at which this device should run, by checking the speed of existing Token Ring stations or checking with the network manager. If your device is already configured or you do not have token ring, you are not prompted for the information. 4-16 Advanced Configuration 4.9.1 Setting the Token Ring Station Speed DECnet/OSI for DEC OSF/1 stations in a Token Ring LAN can operate on either 4 or 16 MB per second data rates. A station can insert onto a Token Ring only at the ring's established data rate (ring speed). The station's ring speed can be set either by using the netsetup utility to configure the station's Token Ring adapter, or by the decnetsetup utility. Be aware of the ring speed of the Token Ring LAN where the station is to be inserted. If the ring speed is set to the wrong value, then the ring insertion process will fail. If the station fails to insert or connect correctly, messages appear in the Session Manager window: vmunix: tra0: MAC_OPEN : tra0: Ring status: Ring recovery vmunix: Open error: Phase: Physical insertion; You can also query the state of the Token Ring adapter. For example: # ifconfig tra0 tra0: flags=8822 This indicates that the adapter is not active and that the station failed to insert on to the ring. The station has successfully inserted on to the ring if the same command yields: # ifconfig tra0 tra0: flags=8863 4.10 Configuring DECdts Digital Distributed Time Service (DECdts) is included as part of the DECnet/OSI software to support components, like network management and DECdns, that require time stamps. DECdts provides both clerk and server components. A DECdts clerk requests the time from DECdts servers which can provide it with time synchronization services. DECdts servers have access to a list of synchronization services which they use to establish the network time. Advanced Configuration 4-17 Most systems in a network should be configured as clerks and only some need to be servers. Configuring a system as a server does not necessarily impose any additional overhead on the system. Only one server on a LAN actually services clerk requests; the other servers are backups and one of them would become active only if the current server is unavailable. A typical LAN configuration would have three systems configured as servers and the rest of the systems configured as clerks, but you can have as few as one server. If you do not know whether you should be a clerk or a server, contact your network administrator. For information on planning which systems should be clerks and which should be servers, refer to DECnet/OSI Planning Guide. You can find a complete description of DECdts and its options in DECdts Management. ________________________ Note ________________________ If you want, you can use a time synchronization service other than DECdts. If you are using such a service, you should not configure DECdts also. In that case, you should answer no to both the DECdts clerk and server questions. ______________________________________________________ 4.10.1 Configuring Your System as a DECdts Clerk or Server The configuration procedure presents you with the following question: Will this system be configured as a DTSS clerk only? (y/n) [y]: If you want your system to be only a clerk, accept the default (yes) by pressing . If you want your system to be a DECdts server, follow these steps: 1. Answer the DTSS clerk-only question with no. 2. Answer the DTSS server question with yes. 4-18 Advanced Configuration 4.11 Configuring Your Namespace DECdns is a network naming service that enables you to use either a distributed namespace or a Local namespace as your primary name service. The advanced configuration gives you the following name service configuration options: o You can use the DECdns Local namespace as your primary name service (see Section 4.11.1). o You can configure your system as a DECdns clerk in a distributed namespace (see Section 4.11.2). The DECnet/OSI for DEC OSF/1 Introduction and User's Guide contains more information about DECdns and the Local namespace. DECnet/OSI Network Management provides information and guidelines for using Local namespace. If you do not know which configuration to use, consult your network manager. 4.11.1 Using a Local Namespace If you are using a Local namespace, the configuration procedure configures your system, then registers it in the Local namespace. The script displays informational messages similar to the following: There will be a brief pause as the dec namespace is checked, to see if this node is already registered. This node is registered in the dec namespace. Updating address towers for node object dec:.lkg.agn2au ... done The configuration of DECnet/OSI is completed. Refer to DECnet/OSI Network Management for information on how to manage node names in the Local namespace. 4.11.2 DECdns Clerk Configuration In a DECnet/OSI network with a distributed namespace, your DECnet/OSI for DEC OSF/1 system can be a DECdns clerk. If you are using a distributed namespace, the configuration procedure defaults to this choice. If you will be using a remote DECdns server, the configuration script will prompt you for the server's address later (see Section 4.15.2.1). Advanced Configuration 4-19 4.12 Configuring the DECnet-Internet Gateway The next question appears only if you installed the DECnet- Internet Gateway subset. The question asks if you want to configure the DECnet-Internet Gateway software as follows: Will this system be configured as a DECnet-Internet Gateway? (y/n) [n]: If you want to configure the Gateway, answer yes to this question. If you are not going to use the Gateway, answer no. If you copied the subset, but you do not want to configure it at this time, you can answer no and configure the software later using the following command: # /usr/sbin/decnetsetup gateway 4.13 Running MOP Standalone To configure and run MOP standalone without the rest of DECnet/OSI, do the following: 1. Install the DNANETMAN300, DNADLI300, and the DNAMOP300 subsets # setld -l DNANETMAN300 DNADLI300 DNAMOP300 2. Configure MOP (which also performs the needed DLI and NETMAN configuration): # /usr/sbin/mopsetup 4.14 Confirming Your Answers and Starting the DECnet/OSI Software Before the configuration procedure actually configures your system, it asks you to confirm your answers for the following values for your system: o DECnet/OSI full name o Node synonym (if you have one) o Phase IV address (if you have one) o Phase IV prefix (if you have a Phase IV address) o Which device(s) will use DECnet/OSI protocols o NETs (if you manually configured the addresses) 4-20 Advanced Configuration o DECdts role (clerk or server) o DECdns clerk or Local namespace There are four ways that you can proceed at this point: 1. If you are satisfied with the answers you supplied, to continue the configuration, type continue and press . The procedure configures your system and saves your answers in a defaults file that it uses if you rerun the procedure. 2. If you want to change one (or more) of your answers, type restart and press . This action starts the configuration procedure over again from the beginning with your previous answers supplied as default values to each question. 3. If you are satisfied with the answers but you do not want to continue to configure your system, type stop and press . This stops the configuration procedure and saves your answers in a defaults file. 4. If you want to exit the configuration procedure and do not want to save your answers in a defaults file, type quit and press . This example shows how to respond if you are satisfied with the answers you supplied. Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: dec:.lkg.agn2au Node Synonym: agn2au Phase IV Address: 12.175 Phase IV Prefix: 49:: Network Devices: te0 Advanced Configuration 4-21 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will be a DNS clerk in the dec namespace. Do you wish to complete this DECnet/OSI configuration? [continue] If you choose to continue, the procedure creates startup files, modifies system files, and starts up the DECnet software. Once the procedure starts to configure DECnet, do not stop it. During this start-up process, you receive informational messages similar to these: Creating defaults file. Creating Initialization NCL scripts Creating /usr/sbin/decnetstartup Creating /usr/sbin/osi_applstartup Updating /var/dna/dna_version Modifying /usr/sbin/decnetshutdown Event Logging ... Configuring "CTF Collector Components " (CTABASE130) Ensuring all underlying dependencies are configured. ++++++++++++++++++++++++++++++ Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) Adding WAN lock entries to /sys/kern/lockinfo.c ... done. ZZAUTIL110 Configured. ------------------------------ CTABASE130 configured. Creating Session Control Creating /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Attempting to contact local DNS server...please wait. DNS clerk successfully configured. Node name reset to dec:.lkg.agn2au DTSS ... Node Enabled ... Event Logging Event Logging ... The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/rfc1006 32 57 DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. 4-22 Advanced Configuration rfc1006setup completed successfully. The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/xtiso/cots 32 58 /dev/streams/xtiso/clts 32 59 Setting Session Control attributes 4.15 Finishing the DECdns Configuration Once DECnet/OSI starts, the way the configuration completes depends on the namespace function you chose to use on your system. o If you are using a Local namespace, refer to Section 4.15.1. o If you are configuring your system as a DECdns clerk in a distributed namespace, refer to Section 4.15.2. 4.15.1 Finishing the Local Namespace Configuration If you are using a Local namespace, the configuration procedure configures your system, then registers it in the Local namespace database. The script displays informational messages similar to the following: There will be a brief pause as the dec namespace is checked, to see if this node is already registered. This node is registered in the dec namespace. Updating address towers for node object dec:.lkg.agn2au ... done The configuration of DECnet/OSI is completed. After the node is registered, the advanced configuration is complete and you can proceed to Section 4.16 for instructions on how to verify the configuration. Refer to DECnet/OSI Network Management for information on how to manage node names in the Local namespace. Advanced Configuration 4-23 4.15.2 Finishing the DECdns Clerk Configuration If you are using a distributed namespace, the configuration procedure checks to see if a DECdns server for your namespace is on the same LAN as your system. If the server exists, it is automatically recognized and your system is registered using that server. In this case, you receive a completion message similar to this one: Attempting to contact local DNS server...please wait. DNS clerk successfully configured The configuration procedure then attempts to register your system in the distributed namespace and displays a message similar to this at the end of the operation: This node is registered in the XYZ_CORP namespace. If the automatic registration is successful, the advanced configuration is complete. You can proceed to Chapter 6 for instructions on how to verify the configuration. If the procedure is unable to register your node or if your namespace does not allow automatic registration, a message informs you that you must manually register your system. Your configuration is finished, but you will not be able to fully communicate with other systems or run the installation verification procedure until your system is registered in the namespace. Refer to DECnet/OSI Network Management for information on manually registering a system in a distributed namespace. 4.15.2.1 Connecting to a Remote Server in a Distributed Namespace If a DECdns server for your distributed namespace is not found on your LAN, the procedure prompts you to enter the address of the server you want with this question: What is the network address of the server? You can respond to this question with the server's Phase IV compatible address (if it has one) or with the server's network service access point (NSAP). The NSAP is the NET with a valid transport selector. To find this information, contact the system administrator for that server. The administrator can get this information by running the dnsconfigure utility on the server and selecting to Show address information of this node. 4-24 Advanced Configuration The server system may have a number of different NSAPs. You can use any of these NSAPs to connect to the server system, but you must enter the NSAP in the displayed format. After you enter the server's address, your system connects to the server and displays a confirmation message listing your namespace nickname and its namespace creation time stamp (NSCTS), as in this example: Your default namespace nickname is XYZ_CORP Your default namespace NSCTS is 00-12-34-56-77-A0-A1-A2-A3-A4-A5-A6-A7-B0 If you fail to connect to the remote server, you must reboot your system before you try to reconfigure DECnet /OSI. ________________________ Note ________________________ If you are joining a DECdns Version 1.1 namespace, make sure you have access to the remote server's sys$system:dns$default_file.dat Refer to DECdns Management for more information. ______________________________________________________ 4.16 Verifying the Advanced Configuration Procedure Once your system is registered in the namespace, the installation and configuration are finished. If necessary, perform the postinstallation tasks in Chapter 5, and then proceed to Chapter 6. Chapter 6 includes instructions on how to run the /usr/sbin/dnet_check installation verification procedure. This procedure tests and exercises your DECnet/OSI communications software to ensure that you configured the software properly. 4.17 Configuring DECnet/OSI to use X.25 Services If you have installed the DEC X.25 for DEC OSF/1 product, you can configure DECnet/OSI to make use of the features it offers. This is optional, since DECnet/OSI and X.25 can be used independently on your system. Advanced Configuration 4-25 You can select either, or both, of the following configurations for DECnet/OSI to use X.25 services: o You can configure the OSI Transport entity to use the CONS interface to X.25, enabling the use of OSI Transport classes 0 and 2 (TP0 and TP2). o You can configure the DNA Routing entity, which provides CLNS, to use an X.25 circuit as a dynamically established data link to a remote system. If you want DECnet/OSI to use X.25 services, you should configure DECnet/OSI and X.25 separately. Also, make sure that both components work properly before you configure DECnet/OSI to use X.25 services. Use the instructions in this book to configure DECnet/OSI first. Then, refer to the X.25 Installation and the X.25 Configuration Guide for information about installing and configuring X.25 software After you configure both DECnet/OSI and X.25, you need to run an additional configuration procedure (dnax25setup) that sets up the underlying support for running DECnet /OSI over X.25. Use the following command to start this configuration procedure: #/usr/etc/dnax25setup Follow the prompts or refer to the X.25 Configuration Guide for explicit instructions on using this configuration procedure. 4-26 Advanced Configuration 5 _________________________________________________________________ Postinstallation Tasks - Namespace Activities There are two namespace tasks discussed in this chapter: distributed namespace tasks and Local namespace tasks. These are performed after installation. The type of postinstallation tasks you perform depends on whether you are using a distributed namespace or a Local namespace. 5.1 DECdns Distributed Namespace Tasks If you are using a DECdns distributed namespace, you might have to perform certain tasks after you configure the DECnet/OSI software on your system (the local node). This chapter serves as a checklist of these tasks. The tasks are documented in detail in the DECnet/OSI Network Management book. The namespace concepts are described in the DECdns Management book. o If your system is joining a network that has other DECnet/OSI systems, see Section 5.1.1. o If your system is the first DECnet/OSI system on the network, and your network includes Phase IV nodes, see Section 5.1.2. o If your system is the first DECnet/OSI system on the network, and your network does not include Phase IV nodes, see Section 5.1.3. 5.1.1 Registering Subsequent DECnet/OSI Systems For subsequent DECnet/OSI systems brought up on the network, the only namespace activity you might have to perform is registering the system in the distributed namespace. Postinstallation Tasks - Namespace Activities 5-1 Depending on several variables, decnetsetup might have registered the local node in the distributed namespace during configuration. o If decnetsetup did register the node, you do not have to perform any namespace tasks; go to Chapter 6, which describes how to verify the installation. o If decnetsetup did not register the node, manually register it now using decnet_register; after registering the system, you can go on to Chapter 6. This message appears if the registration failed: This node could not be registered in the namespace. When this procedure completes you will have to manually register this node in the namespace. Refer to the "Postinstallation Tasks" chapter of the installation guide for more details, or contact your network manager. 5.1.2 First DECnet/OSI System on a Network with Phase IV Nodes Immediately after you install the first DECnet/OSI system on the network, use decnet_register to perform these tasks: 1. Register all the existing Phase IV nodes in the distributed namespace. Refer to the DECnet/OSI Network Management book. 2. Manually register your node in the namespace using decnet_register if decnetsetup displayed this message: This node could not be registered in the namespace. When this procedure completes you will have to manually register this node in the namespace. See the "Postinstallation Tasks" chapter of the installation guide for more details, or contact your network manager. For instructions on registering the system, refer to the DECnet/OSI Network Management book. 3. Delete the local node's Phase IV name from .DNA_Node, if necessary. Your local node might be registered in .DNA_Node as a Phase IV node, if it was included in the nodes_p used to create the script for registering all existing Phase IV nodes. Refer to the DECnet/OSI Network Management book. 5-2 Postinstallation Tasks - Namespace Activities 4. Give authorized users access to the namespace by adding them to the .DNS_Admin and .DNA_Registrar access control groups. For information on the .DNS_Admin group, refer to DECnet/OSI Planning Guide. For information on adding members to .DNA_Registrar, refer to the DECnet/OSI Network Management book. After you complete each task, go to the next chapter to verify the installation. 5.1.3 First DECnet/OSI System on a Network with No Phase IV Nodes Immediately after you install the first DECnet/OSI system on the network, use decnet_register to perform these tasks: 1. Manually register your node in the namespace using decnet_register if decnetsetup displayed this message: This node could not be registered in the namespace. When this procedure completes you will have to manually register this node in the namespace. Refer to the "Postinstallation Tasks" chapter of the installation guide for more details, or contact your network manager. For instructions on registering the system, refer to the DECnet/OSI Network Management book. 2. Give authorized users access to the namespace by adding them to the .DNS_Admin and .DNA_Registrar access control groups. For information on the .DNS_Admin group, refer to DECnet/OSI Planning Guide. For information on adding members to .DNA_Registrar, refer to the DECnet/OSI Network Management book. After you complete each task outlined above, go to Chapter 6 to verify the installation. 5.2 Local Namespace Tasks If you are using a Local namespace, you have several options in modifying and using the Local namespace including: o Creating or re-creating a Local namespace file o Updating address tower information Postinstallation Tasks - Namespace Activities 5-3 o Loading the Local namespace file o Loading node definitions from a phase IV node database into a Local namespace file o Clearing all information from a Local namespace file o Adding new node definitions into a Local namespace file. You can find instructions on how to do these tasks in the DECnet/OSI Network Management book. 5.3 Update_Nodes The update_nodes utility lets you update or create a local nodes Phase IV database with information from a remote DECnet nodes database. In addition, it lets you load the information that is retrieved into either a Local or a distributed namespace. The Phase IV local nodes database is no longer used by DECnet/OSI; however, you may want to create one to aid in your transition: o You can use an existing local nodes database in conjunction with decnet_register to populate your namespace with the Phase IV nodes in your network. Refer to the DECnet/OSI Network Management guide for details. o You can convert the MOP information stored in the local nodes database to create the new MOP client database (using the update_mopdb tool). 5.3.1 Running Update_Nodes To run the update_nodes utility, you must become root and use this command format: update_nodes -d [Local|decdns] node-id where node-id is the DECnet node name or DECnet node address of the remote node whose database you are using for the update. Non-DECnet entries, such as terminal servers, and parameters, such as download parameters, are preserved except where conflicts occur. A conflict occurs when a node name received from the remote node already exists in the current database, but the node numbers do not match. In this case, the information received from the remote node 5-4 Postinstallation Tasks - Namespace Activities is entered in the new database. However, any parameters associated with the node name are not entered. A record of all conflicts and any dropped parameters is kept in the file /usr/lib/dnet/update_nodes.log. 5.3.1.1 Copying a DECnet Phase IV Node Database This example illustrates how to copy a DECnet Phase IV node database from another system and use it to populate the Local namespace file. # update_nodes 4.1002 -d Local Postinstallation Tasks - Namespace Activities 5-5 6 _________________________________________________________________ Running the Installation Verification Procedure The Installation Verification Procedure (IVP) tests your DECnet/OSI configuration to ensure that you can communicate properly with other DECnet/OSI systems. The IVP checks to see whether DECnet/OSI is running, tests whether your DECdns clerk is functioning, establishes a connection with another DECnet/OSI system, uses that connection to copy files between that system and your own system, and runs the loopback application to the remote system. 6.1 IVP Requirements To run the IVP, you must have both a user account and password on your local system, as well as a user account and password for a remote DECnet/OSI system. 6.2 Running the IVP To run the IVP, use the following command: # /usr/sbin/dnet_check 6.2.1 Supplying a Full Name Once you start the IVP, it prompts you to supply your DECnet/OSI full name. You can either accept the default full name by pressing or specify another full name (if you belong to an additional namespace for instance). The following example shows how you would accept the default full name: What is your Phase V node name? [XYZ_CORP:Sales.west_coast.WillyLoman]: If you specify a nondefault full name, the IVP prompts you to confirm it before you can continue, as in the following example: Running the Installation Verification Procedure 6-1 What is your Phase V node name? [XYZ_CORP:.Sales.west_coast.WillyLoman]: abc_corp:.sales_mamagement.wloman Your node name is abc_corp:.sales_management.wloman Is this correct? (y/n) [y]:y You can either accept this full name by pressing or reject it by typing n and pressing . If you reject the full name, you return to the full name prompt. 6.2.2 Checking the State of DECnet/OSI After you specify a full name, the IVP tests to see if DECnet/OSI works by checking the state of the Routing, Session Control, and Node entities, as in the following example: The first test checks that some of the DECnet/OSI network management entities are running. Each of the following displays should indicate that the entity is in state "On". # ncl show Routing state Node 0 Routing AT 1994-11-01-15:18:02.614-05:00I----- Status State = On # ncl show Session Control state Node 0 Session Control AT 1994-11-01-15:18:03.306-05:00I----- Status State = On # ncl show Node 0 state Node 0 AT 1994-11-01-15:18:03.933-05:00I----- Status State = On 6-2 Running the Installation Verification Procedure The state of all these entities should be On. If any of them are Off, DECnet/OSI is not running properly, and you should examine the /usr/sbin/decnetstartup script to verify that the entity in question is being started. (This script calls the /sbin/rc3.d/S28decnetosi script at reboot.) 6.2.3 Checking the DECdns Clerk If DECnet/OSI is running properly, the IVP then issues an NCL command to ensure that your DECdns clerk is functioning. It performs this test by looking up your node object in the namespace you specified as part of your full name, as in the following example: The following command attempts to look up your node object in the DNS namespace. This is a simple way to test that the DNS Clerk is functioning correctly. # decnet_register show node DEC:.lkg.agn2au directory_service decdns Directory Service: DECdns Node name: DEC:.lkg.agn2au Phase IV synonym: AGN2AU Node address: 49::00-0C:AA-00-04-00-AF-30:21 (12.175) Node address: 49::00-0C:AA-00-04-00-AF-30:20 (12.175) Node address: 41:45418715:00-41:08-00-2B-30-7D-E6:21 Node address: 41:45418715:00-41:08-00-2B-30-7D-E6:20 Number of nodes reported on: 1 If the IVP cannot display your node object entry, you should take the following steps: 1. Verify that the clerk is working by issuing the following command: # ncl show dns clerk state 2. If the clerk state is On, your system may not be registered in the namespace you specified. See Chapter 5. 3. Register your system in the namespace using the instructions in the DECnet/OSI Network Management book. After you register your system, issue the following command, substituting your full name for the one in this example: Running the Installation Verification Procedure 6-3 # ncl update session control tower maintenance - DEC:.lkg.agn2au 4. If the clerk state is Off or you receive a message stating that the clerk entity was not created, issue the following command: # ncl do /var/dna/scripts/start_dns_clerk.ncl 6.2.4 Reaching a Remote System If your DECdns clerk is functioning properly, the IVP checks to verify that your system can communicate with a remote system. In order to run this test, you must supply and verify the name of a remote system (you can also specify a Phase IV address), as in the following example: Enter the name of a remote node? [No Default]: notrix remote node notrix Is this correct? (y/n) [y]: The following command will check that the remote node you specified is reachable: # ncl show node notrix state Node notrix AT 1994-11-01-15:18:35.265-05:00I12.367 Status State = On If the IVP indicates that your system cannot reach the remote system, you should try to reach a different remote system. 6.2.5 Testing your Local System The next group of tests attempts to copy files over the network using DECnet/OSI, and to run the loopback application. The first test will copy a file to the local node using DECnet/OSI utilities, and if successful, the second test will copy a file to and from the remote system you specified earlier. For each test, you will be asked to provide the user account and password to be used for that system. For example: 6-4 Running the Installation Verification Procedure Enter user account on DEC:.lkg.agn2au [No Default]: thomas Enter password for user thomas on DEC:.lkg.agn2au [No Default]: # dcp /usr/sbin/dnet_check DEC:.lkg.agn2au/thomas/password/::dnetcheck.rnd # dcp DEC:.lkg.agn2au/thomas/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm DEC:.lkg.agn2au/thomas/password/::dnetcheck.rnd # ncl loop loopback application name DEC:.lkg.agn2au, length 1, count 10, format 00 # ncl loop loopback application name DEC:.lkg.agn2au, length 2047, count 50 If any of these tests fail, check the /tmp/dnet_check.log log file for additional information. After these tests complete, the IVP prompts you for the name of an user account and password on the remote system that you specified previously. Supply this information, as in the following example: Enter user account on notrix [No Default]: thomas Enter password for user thomas on notrix [No Default]: # dcp /usr/sbin/dnet_check notrix/thomas/password/::dnetcheck.rnd # dcp notrix/thomas/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm notrix/thomas/password/::dnetcheck.rnd # ncl loop loopback application name notrix, length 1, count 10, format 00 # ncl loop loopback application name notrix, length 2047, count 50 Removing log file /tmp/dnet_check.log Removing the file copied across the network # exit # If any of these tests fail, check the /tmp/dnet_check.log log file for additional information. The mirror application must run on both the local and the remote systems. If this test completes successfully, the IVP is finished and DECnet/OSI for DEC OSF/1 is functioning properly. Running the Installation Verification Procedure 6-5 Part II _________________________________________________________________ Installation and Configuration for FTAM and VT This part describes how to install and configure the FTAM and Virtual Terminal software. Part II includes these chapters: o Chapter 7 - Installing FTAM and Virtual Terminal o Chapter 8 - Configuring FTAM and Virtual Terminal 7 _________________________________________________________________ Installing FTAM and Virtual Terminal This chapter describes how to install the FTAM and Virtual Terminal (VT) software on your system. It includes: o Preparing your system for the installation. o Installing FTAM and Virtual Terminal. 7.1 Preparing Your System for Installation The first part of the installation procedure is preparing your system. Preparing your system requires the following steps: 1. Make sure you have superuser privileges (Section 7.1.1). 2. Check your system's disk space (Section 7.1.2). 3. Back up your system disk (Section 7.1.3). 4. Delete previous versions of DECnet/OSI subsets (Section 7.1.4). 5. Register your Product Authorization Key (PAK) if you are adding gateways (Section 7.1.5). 7.1.1 Acquiring Superuser Privileges To install and configure DECnet/OSI, you must have superuser privileges. The command to acquire superuser privileges is su. You must then enter the root password. Refer to the DEC OSF Guide to System Administration for details on acquiring superuser privileges. Installing FTAM and Virtual Terminal 7-1 7.1.2 Checking Your Disk Space Verify that you have enough free disk space to install and configure the software subsets of your choice. The installation could fail if it runs out of disk space while copying the subsets from the distribution media. Installation of all FTAM and Virtual Terminal subsets requires 3.4 MB of total disk space on the /usr partition. The minimum installation kit requires 3.2 MB of total disk space on the /usr partition. You can find a complete description of the space requirements for each subset in Appendix E. To check the available disk space in /usr, enter the following command: # df -k /usr 7.1.3 Performing System Disk Backup Before you install the subsets back up your system disk. For information on backing up your system, see the Guide to System Administration manual. 7.1.4 Deleting Old OSI Applications Subsets Before you begin installing OSI Applications subsets, you must ensure that the correct version of DECnet/OSI is installed on your system, and that the OSI Applications subsets from any previous versions of DECnet/OSI have been deleted. See Chapter 2 on how to delete old DECnet/OSI subsets. Use the following command to see if OSI Applications subsets are installed on the system, where DNAAPP is the subset name prefix of DECnet/OSI: # setld -i | egrep "^DNAAPP" If any subsets with one of these product codes exists on your system, the utility displays an installed message, such as the following example for DECnet/OSI for DEC OSF/1 V1.1: DNAAPP100 installed OSI Applications 7-2 Installing FTAM and Virtual Terminal If OSI Applications subsets from previous versions of DECnet/OSI exist, use the steps in Section 7.1.4.1 to delete these subsets. 7.1.4.1 Deleting Subsets To delete the OSI Application subsets from your system, log in as superuser and issue the setld command with the -d option, where subset is the name of the DECnet/OSI software subsets you want to delete: # setld -d subset [...] The following example deletes the OSI Applications and OSI Application Gateways subsets: # setld -d DNAAPPGWY200 DNAAPP200 ________________________ Note ________________________ Because of software dependencies, delete the OSI Applications subset (DNAAPP200) last. ______________________________________________________ 7.1.5 Using LMF to Register Your Software License PAK The next step in the installation procedure is to register your Product Authorization Key (PAK) using the License Management Facility (LMF). LMF is a system management software tool that enables you to comply with your license agreement. LMF offers options for the variety of license agreements. The terms and conditions of your contract determine your legal use of this software. LMF maintains the file of registered software license PAKs and keeps a library of functions used by licensed software. An Extended System PAK is needed to run the OSI Application Gateways. If you want to run the gateways, then perform the following instructions. Otherwise, continue the installation at Section 7.2.1. The following instructions show how you might register an End System software license PAK using LMF: 1. Make sure that you have your PAK. 2. Log on to your system as a superuser. Installing FTAM and Virtual Terminal 7-3 3. Issue an lmfsetup command: # lmfsetup 4. After you issue this command, you receive the following confirmation: # Register PAK ((type q or quit to exit) [template] 5. Press . After you do this, you are prompted to answer a series of questions. These questions correspond to the fields on your PAK form. Use the information from your DECnet /OSI for DEC OSF/1 PAK to reply to each question. Any fields that are left blank on the PAK should be left blank as you enter the data. 6. After you respond to all the questions, you should receive a completion message similar to the following: PAK registered for template successfully 7. Exit lmfsetup by entering quit: # Register PAK ((type q or quit to exit) [template] quit 8. Issue an lmf reset command: # lmf reset 9. Issue an lmf list command to verify your registration: # lmf list ________________________ Note ________________________ If you attempt to load a PAK and a PAK has already been loaded, you receive an error message similar to the following: Combine DECNET-OSI-EXT SQM014419 with DECNET-OSI-EXT SQM010892 If you receive this message, do the following: 1. List the license PAK templates using the following command: # lmf list full for DECNET-OSI-EXT 2. Compare the information in the templates, and note the authorization number of the software license PAK you want to delete. 7-4 Installing FTAM and Virtual Terminal 3. Use the following command to delete the old PAK: # lmf delete DECNET-OSI-EXT DEC authorization-number 4. Issue another lmf reset command. ______________________________________________________ If you want to know how to obtain a license and PAK or how you use the LMF facility, refer to the DEC OSF/1 Guide to Software License Management, or the lmf and lmfsetup man pages (lmf(8) and lmfsetup(8)) for additional information. 7.2 Installing FTAM and Virtual Terminal Now that you have prepared your system, you can proceed with the installation. 7.2.1 Installing the Subsets from the Distribution Media The next step is to install the DECnet/OSI subsets from the distribution media. The steps to accomplish this task vary, depending on whether you are using the DEC OSF/1 Layered Product Consolidated Software Distribution disk (CDROM) or the Remote Installation Service (RIS) over a local area network. 7.2.1.1 CDROM Installation If you are installing the software from a CDROM, use this procedure: 1. Determine the directory of the DECnet/OSI files. Refer to the Master Index table in the Consolidated Software Distribution Disk User's Guide for the name of the directory on the CDROM that contains the DECnet/OSI software. 2. Insert the disk into the drive to determine the device name for the drive. The drive is either RRD40 or RRD42. Use the following command to list the available disk devices: # file /dev/rr*c Installing FTAM and Virtual Terminal 7-5 3. Mount the disk using the following command and device's name: # mount -r -d /dev/device_name /mnt 4. Install the software on your system, using the software's directory name and this setld(8) command: # setld -l /mnt/directory_name 7.2.1.2 Using RIS Over a Local Area Network You can install DECnet/OSI for DEC OSF/1 over your network using the Remote Installation Service (ris) utility. Refer to the Remote Installation Service document and ris(8) in the Reference Pages, Section 8, for requirements. If you are using RIS over a local area network to install the software, use the following command: setld -l hostname: hostname is the name of the host from which you are loading the software. 7.2.2 Selecting the Software Subsets The next step is to choose the options you want to install from the distribution media. Run setld, then select from the following menu of subsets: # setld -l . The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. - OSI Applications: 1) OSI Application Gateways 2) OSI Application On-line Docs 3) OSI Applications Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. 7-6 Installing FTAM and Virtual Terminal Choices (for example, 1 2 4-6): 7.2.2.1 DECnet/OSI Standard Installation For the minimum OSI Application configuration, you must install the OSI Applications subset (DNAAPP200). The remaining subsets you select are optional. Type the numbers of the options that you want to install. Separate each number with a space, not a comma. To specify a range of numbers, use a hyphen to join them. Choices (for example, 1 2 4-6): 2 3 You are installing the following optional subsets: - OSI Applications: OSI Application On-line Docs OSI Applications After you specify the subsets, the procedure prompts you to verify your choice: Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. If you chose the wrong options, type no to indicate that the subsets are not correct; the subset menu redisplays, and you can reselect your subsets. If you chose the correct options, type yes. The procedure also checks to ensure that you have enough file space to install the selected subsets. 7.2.3 Copying the Software to Your System After you select the subsets, the procedure copies them from the installation media to your disk. The following example shows a partial display as the procedure copies selected software subsets: OSI Applications Copying from /usr/sterling/kits/ALPHA-OSF1/DNA_V2.0-preSSB (disk) Verifying Installing FTAM and Virtual Terminal 7-7 OSI Application On-line Docs Copying from /usr/sterling/kits/ALPHA-OSF1/DNA_V2.0-preSSB (disk) Verifying If verification fails, look in /var/adm/fverify.log and /var/admin/setld.log for information to help you correct the error. Make the correction and restart the installation by using the setld -l command. 7.2.3.1 Completion Messages When the installation is complete, the procedure displays completion information on the subsets you chose to install. If you need to rebuild the kernel or reboot your system, the procedure displays the appropriate instructions for you to follow at this time. Creating directories and symbolic links for DNAAPP200 ... done. Modifying ./etc/magic... done. After verifying that the system is operating properly, you may wish to remove the following saved file: - ./etc/magic.sav[n] Configuring "OSI Applications " (DNAAPP200) To complete your installation of the OSI Applications, please take the following steps: - Ensure that DECnet/OSI for DEC OSF/1 is properly installed and configured. - Configure the OSI Application software by executing the command: # /usr/sbin/osiapplsetup Please refer to the Installation Guide for details. Creating directories and symbolic links for DNAAPPMAN200 ... done. Configuring "OSI Application On-line Docs " (DNAAPPMAN200) To configure FTAM and Virtual Terminal, see Chapter 8. 7-8 Installing FTAM and Virtual Terminal 8 _________________________________________________________________ Configuring FTAM and Virtual Terminal This chapter describes how to configure the FTAM and Virtual Terminal (Virtual Terminal) software on a DEC OSF/1 system. 8.1 FTAM and Virtual Terminal Terminology o An initiator, or client, is the program on one system that initiates a request to a program on another system, and awaits a response. o A responder, or server, is the program on a system providing a response to a request initiated on another system. o A listener is a job running on the responding system that fulfills incoming requests from an initiating system. 8.2 About the OSI Application Entity Database The OSI application entity database on DEC OSF/1 is located at: /etc/isoapplications There are three types of formats that you can use in this isoapplications database. They are: o Address - Information on local listeners, remote applications, and source aliases. o Distinguished Name - X.500 Directory Service retrieval entries. o Pattern - X.500 Directory Service retrieval entries. The isoapplications database can contain any combination of these formats. Configuring FTAM and Virtual Terminal 8-1 For detailed information on the Address, Distinguished Name and Pattern formats in the isoapplications database, refer to Chapter 9 in DECnet/OSI FTAM and Virtual Terminal Use and Management. 8.3 Steps To Configure Initiating and Responding Entities This section provides configuration task checklist items and examples for setting up the initiating and responding systems, or entities. If you are already familiar with configuring FTAM and VT, then you can continue the configuration procedure, starting at Section 8.4 in this chapter. 8.3.1 Checklist for Responding Entity To communicate with a responding entity, you need to contact the person responsible for configuring the OSI application entity database on the responding system. Table 8-1 shows the tasks that person must perform on the system. Table_8-1_Setup_Tasks_For_The_Responding_Entity____________ StepTask___________________________________________________ 1 Determine the transport provider type to be used for the transport connection: a. For an OSI Provider (default): Determine the local NSAP. b. For an RFC1006 Provider: Determine the Internet address and RFC1006 daemon port (default RFC1006 daemon port is 102). (continued on next page) 8-2 Configuring FTAM and Virtual Terminal Table_8-1_(Cont.)_Setup_Tasks_For_The_Responding_Entity____ StepTask___________________________________________________ 2 Determine transport template to be used in the transport connection: a. For an OSI Provider: the default template is default. b. For an RFC1006 Provider: no template should be specified. 3 Determine the SAPs. For more information on determining SAPS, refer to Chapter 6 and Chapter 9 in FTAM and Virtual Terminal Use and Management . 4 Define an alias in the isoapplications database using the information collected in the prior steps. Note that you can edit this database using a text editor, or on DEC OSF/1 you can use the /usr/sbin/osiapplsetup ____procedure_described_in_Section_8.4_in_this_chapter.____ Once the setup is complete, you can start a listener on the alias defined in Step 4 of prior table. 8.3.2 Checklist for Initiating Entity Table 8-2 shows the tasks you need to perform on your system to initiate requests to a responding entity. Table_8-2_Setup_Tasks_For_The_Initiating_Entity____________ StepTask___________________________________________________ 1 Obtain the remote address and transport provider determined in Step 1 of the Responding Entity checklist. 2 Obtain SAPS determined in Step 3 of the Responding Entity checklist (continued on next page) Configuring FTAM and Virtual Terminal 8-3 Table_8-2_(Cont.)_Setup_Tasks_For_The_Initiating_Entity____ StepTask___________________________________________________ 3 Determine the local transport template to be used. See Step 2 of the Responding Entity checklist. 4 Assign SAPs and remote address information to an alias ____and_make_an_alias_entry_in_the_isoapplications_file.___ Once the setup is complete, you can invoke initiator requests using the alias as defined in Step 4 of the prior table. 8.3.3 Example: Performing An FTAM File Copy Use the appropriate checklists from Table 8-1 and Table 8-2 to configure your system to perform an FTAM file copy. In this example, you copy remote file system_a_filename on System-A, to file system_b_filename on System-B. System-A is the responding entity, and System-B is the initiating entity. System-A and System-B are DEC OSF/1 systems. Use the OSI Provider and use the following account information on System-A: username: system_a_user password: system_a_pwd Using Table 8-1, perform the following steps on responding entity System-A as superuser: 8-4 Configuring FTAM and Virtual Terminal ___________________________________________________________ StepTask___________________________________________________ 1 Determine NSAP of System-A: # ncl ncl> show osi transport local nsap * name Node 0 OSI Transport Local NSAP %X4145418715004108002B2FF29A21 AT 1994-10-26-16:26:42.446-04:00I8.506 Identifiers Name = %X4145418715004108002B2FF29A21 2 Determine transport template. For this example, use the default template. Determine what transport templates are available on System-A: # ncl ncl> show osi transport template * name Node 0 OSI Transport Template Default AT 1994-10-26-16:28:07.210-04:00I7.740 Identifiers Name = Default _______ Node 0 OSI Transport Template clns AT 1994-10-26-16:28:07.211-04:00I7.740 Identifiers Name = clns _______ Node 0 OSI Transport Template any AT 1994-10-26-16:28:07.211-04:00I7.740 Identifiers Name = any 3 Determine the SAPs. For this example, use: PSAP.SSAP.TSAP. Configuring FTAM and Virtual Terminal 8-5 ___________________________________________________________ StepTask___________________________________________________ 4 Define the following alias in the /etc/isoapplications database using the information collected from Steps 1-3: system_a_alias :FTAM:::PSAP.SSAP.TSAP. \ %X4145418715004108002B2FF29A21, \ ____________________________provider=osi,template=default:_ Once the setup is complete, you can start the FTAM listener on the alias defined in Step 4 of the prior table: # ftam_listener system_a_alias Using Table 8-2, perform the following steps on initiating entity System-B as superuser: ___________________________________________________________ StepTask___________________________________________________ 1 Obtain the remote address and provider from Step 1 in Table 8-1. Using this example, the information from Step 1 is: transport provider: OSI remote address: %X4145418715004108002B2FF29A21 2 Obtain the SAPs from Step 3 in the Responding Entity checklist. Using this example, they are: PSAP.SSAP.TSAP. 3 Determine the local transport template to be used to establish a remote connection to the address specified in Step 1 of this table. For this example, use the default template. 8-6 Configuring FTAM and Virtual Terminal ___________________________________________________________ StepTask___________________________________________________ 4 Use the information from Steps 1-3 in this table to create an alias in the /etc/isoapplications database on System-B: system_a_alias :FTAM:::PSAP.SSAP.TSAP. \ %X4145418715004108002B2FF29A21, \ ____________________________provider=osi,template=default:_ Once the setup is complete, you can start the FTAM copy command: # ocp system_a_alias/system_a_user/system_a_pwd::system_a_filename system_b_filename 8.3.4 Example: Performing A Virtual Terminal Login Use the checklists in Table 8-1 and Table 8-2 respectively to configure your system to perform a Virtual Terminal login. In this example, you perform a VT ologin from System-B to System-A. System-A is the responding entity, and System-B is the initiating entity. System-A and System-B are DEC OSF/1 systems. Use the RFC1006 provider and the following account information from System-A: username: system_a_user password: system_a_pwd Using Table 8-1, perform the following steps on responding entity System-A as superuser: Configuring FTAM and Virtual Terminal 8-7 ___________________________________________________________ StepTask___________________________________________________ 1 Determine Internet address of System-A: # nslookup system-a Server: named.lkg.dec.com Address: 16.20.0.10 Name: system-a.ftam.dec.com Address: 16.20.8.42 2 Determine transport template. Since you are using the RFC1006 provider, no template needs to be specified. Also, use the default RFC1006 daemon port of 102. 3 Determine the SAPs. For this example, use: %x0001.%x0002.%x0003. 4 Define the following alias in the /etc/isoapplications file using the information collected in Steps 1-3: system_a_alias :VT:::%x0001.%x0002.%x0003. \ 16.20.8.42.102. \ ___________________________provider=rfc1006:_______________ Once the setup is complete, you can start the VT listener on the alias just defined in Step 4 of the prior table: # vt_listener system_a_alias Using Table 8-2, perform the following steps on initiating entity System-B as superuser: ___________________________________________________________ StepTask___________________________________________________ 1 Obtain the remote address and provider from Step 1 in Table 8-2. For this example, the information from Step 1 is: transport provider: RFC1006 remote address: 16.20.8.42 remote port: 102 8-8 Configuring FTAM and Virtual Terminal ___________________________________________________________ StepTask___________________________________________________ 2 Obtain the SAPs from Step 3 of Responding Entity checklist. For this example, use: %x0001.%x0002.%x0003. 3 Determine the local transport template to be used to establish a remote connection to the address specified in Step 1 of this table. For this example, no template needs to be specified. 4 Use the information from Steps 1-3 of this table to create an alias in the /etc/isoapplications database on System-B: system_a_alias :VT:::%x0001.%x0002.%x0003. \ 16.20.8.42.102. \ ___________________________provider=rfc1006:_______________ Configuring FTAM and Virtual Terminal 8-9 Once the setup is complete, you can start the VT ologin command: $ ologin system_a_alias DEC OSF/1 V3.0 (system-a.ftam.dec.com) ttyp4 login: system_a_user Password: system_b_user 8.4 About /usr/sbin/osiapplsetup /usr/sbin/osiapplsetup is the OSI Applications configuration procedure. It can configure addressing information about local and remote FTAM and Virtual Terminal implementations. During the configuration, addressing information about local and remote FTAM and Virtual Terminal applications is added to the /etc/isoapplications file. Additionally, commands to start local FTAM and VT listeners automatically at system startup time are added to the /sbin/osi_applstartup file. Refer to DECnet/OSI FTAM and Virtual Terminal Use and Management for more information on the FTAM and Virtual Terminal listeners. If you have the DXDABASE subset of the DEC X.500 Directory Service product installed on your system, then you have the option of configuring the OSI Applications to retrieve addressing information from the X.500 Directory. If you also have the DXDADXIM subset of the X.500 Directory Service software installed, then you may also use /usr/sbin /osiapplsetup to register addressing information about your local listeners in the X.500 Directory. You may choose to autoconfigure or to manually configure the addressing information. If the /etc/isoapplications file already exists on your system, then you also have the option of bypassing a full configuration and simply adding more information to the /etc/isoapplications file. Whether you choose to autoconfigure or to manually configure the addressing information, you will need some information about the local and remote FTAM and Virtual Terminal applications. Therefore, you should complete the appropriate installation checklist before starting the configuration. The autoconfiguration checklist appears in 8-10 Configuring FTAM and Virtual Terminal Figure 8-1, and the manual configuration checklist appears in Figure 8-2. 8.4.1 About Autoconfiguration and Manual Configuration There are three main differences between the autoconfiguration and manual configuration procedures: 1. The setup of addressing information for your local FTAM and Virtual Terminal listeners. 2. The setup of addressing information for your local FTAM and Virtual Terminal initiators. 3. The setup of listeners that start automatically at system startup time. The various parts of an autoconfiguration and a manual configuration are as follows. Autoconfiguration consists of four main parts: 1. Choose a name (referred to as an alias) for the local FTAM and Virtual Terminal listeners. The autoconfiguration procedure determines the addresses of the local listeners. The alias and addresses are used to generate entries in the /etc/isoapplications file. If the DEC X.500 Directory Service product is installed on your system, then the alias and addresses can be used to register the addresses of the local listeners in the X.500 Directory. The alias is also used to insert commands in the /sbin/osi_applstartup file to automatically start up the local listeners. 2. Create entries in the /etc/isoapplications file for remote FTAM and Virtual Terminal applications. 3. Start the local listeners. 4. Run the FTAM and Virtual Terminal IVPs. Manual Configuration consists of five main parts: 1. Optionally assign addresses to the "source aliases." The source aliases are always "local_ftam" for FTAM and "local_vtp" for Virtual Terminal. The address associated with the source alias is provided by the initiator at connection time. If you choose not to assign addresses Configuring FTAM and Virtual Terminal 8-11 to the source aliases, then the address of the initiator is generated by the software at runtime. 2. Create entries in the /etc/isoapplications file for remote FTAM and Virtual Terminal applications. 3. Add commands to osi_applstartup to start FTAM and Virtual Terminal listeners at system startup. 4. Start the local listeners. 5. Run the FTAM and Virtual Terminal IVPs. 8.4.2 Getting Help, Stopping the Configuration Procedure, and Using Defaults The configuration procedure prompts you for information. If you need help responding to any of the configuration script prompts, type a question mark (?) and press to view the help text. You can stop the configuration procedure by typing . Many of the questions have default values associated with them. This information is contained in brackets at the end of the question. Press if you want to use the default value, which is osi in the following example. Enter Transport Provider #1 Name [osi]: Bold callouts (for example, 1) guide you through the sequence of steps that require your response or input during the configuration. 8-12 Configuring FTAM and Virtual Terminal 8.5 Starting the OSI Applications Configuration Procedure Before starting the configuration procedure, you can create a log file of the configuration process. You can use this log file to keep track of your configuration choices. Use the following command to create the log file: 1 #script /var/dna/filename.log After you complete the configuration procedure, type or exit to save the log file. To start the OSI applications configuration procedure, issue this command: 2 #/usr/sbin/osiapplsetup DECnet/OSI for DEC OSF/1 AXP V2.0 FTAM and Virtual Terminal Configuration Procedure (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. The FTAM and Virtual Terminal Configuration Procedure allows you to configure addressing information for FTAM and Virtual Terminal applications on both local and remote systems. 8.6 Configuring the Local FTAM and VT Application Addresses The procedure displays a menu and asks if you want to manually configure or autoconfigure the local application's addresses. 3 Please select one of the following choices: 1. Autoconfigure Application Addresses 2. Manually Configure Application Addresses 3. Exit the FTAM and Virtual Terminal Configuration Procedure For help at any time, enter a question mark at the prompt, or refer to the DECnet/OSI for DEC OSF/1 Installation Guide. Selection [1]: If you press to select 1, the following message displays: Starting the Autoconfiguration procedure... If you select 2, the following message displays: Starting the Manual Configuration procedure... Configuring FTAM and Virtual Terminal 8-13 Section 8.6.2 describes the autoconfiguration procedure and Section 8.6.3 describes the manual configuration procedure. See Section 8.6.1 to continue the installation. 8.6.1 DEC X.500 Directory Service If you have the DEC X.500 Directory Service software installed on your system, the following question appears. To be able to retrieve addressing information from the X.500 Directory, press . 4 The DEC X.500 Directory Service software is installed on your system. Would you like to configure DECnet/OSI FTAM and DECnet/OSI Virtual Terminal to be able to retrieve addressing information from the X.500 Directory? (y/n) [y] DECnet/OSI FTAM and DECnet/OSI Virtual Terminal will be configured to retrieve addressing information from the X.500 Directory. If you are autoconfiguring your system, see Section 8.6.2. If you are manually configuring your system, see Section 8.6.3. 8.6.2 Autoconfiguring the Local FTAM or VT Application's Addresses The first part of the autoconfiguration procedure is to enter the name (also known as the alias) that you want to use to represent the local FTAM and VT listeners. 5 Enter the name that will represent the local FTAM and Virtual Terminal applications on your system [srchr]: Press , or choose another name and press . The procedure prompts you to verify your choice. If correct, press . 6 The alias "srchr" will represent the FTAM and Virtual Terminal applications on your system. Is this correct? (y/n) [y]: If you answer with n, the procedure prompts you to re-enter the alias. If you answer with y, the values for the local applications' addresses appear. 8-14 Configuring FTAM and Virtual Terminal 7 The following values will be used as the presentation addresses of the FTAM and Virtual Terminal applications represented by the alias "srchr": %x0001.%x0001.%x0001.%X4145418715004108002B3873DD21 (FTAM) %x0001.%x0001.%x0002.%X4145418715004108002B3873DD21 (VT) Are these values correct? (y/n) [y]: If you have the DEC X.500 Administration Facility subset (DXDADXIM) installed on your system, and you elected to retrieve addressing information from the X.500 Directory, then you have the option of storing the addresses of the local FTAM and Virtual Terminal listeners in either the X.500 Directory, the /etc/isoapplications file, or both. Otherwise, if the DEC X.500 DXDADXIM is not installed on your system, the addresses will be stored in the /etc/isoapplications file. 8 The values displayed above may be stored in the X.500 Directory, the /etc/isoapplications file, or both. If you choose to store the addresses of the local applications in the X.500 Directory, then you are prompted for information that is used to generate the X.500 Distinguished Name of the local FTAM and Virtual Terminal applications. Would you like to register the local FTAM and Virtual Terminal applications represented by "srchr" in the X.500 Directory? (y/n) [y]: If you elected to register the addresses of the local listeners in the X.500 Directory, then you are prompted for information to generate the X.500 Distinguished Names of the local FTAM and Virtual Terminal listeners. The /usr/sbin/osiapplsetup procedure assumes that your organization's Directory Service schema follows the schema supplied by Digital's X.500 Directory Service product. If you type a question mark (?) at any of the prompts, you will receive information on valid values for a particular prompt. However, the /usr/sbin/osiapplsetup procedure will not check to make sure that the input you supply is valid. If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: Configuring FTAM and Virtual Terminal 8-15 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. 2. Manually add Distinguished Name and Pattern format entries to the /etc/isoapplications file. 9 You will be prompted for information that will be used to generate the X.500 Distinguished Name of the applications represented by "srchr". Enter the country name [return if done]: us Enter the organization name: local_org Enter the organizational unit [return if done]: local_org_unit Enter the organizational unit [return if done]: The following entries will be created in X.500, with corresponding Distinguished Name entries created in /etc/isoapplications: /c=us/o="local_org"/ou="local_org_unit"/cn="srchr"/cn="ftam" /c=us/o="local_org"/ou="local_org_unit"/cn="srchr"/cn="vt" Is this correct? (y/n) [y]: The configuration procedure will use the DEC X.500 Administration Facility to create one application process entry and two application entity entries in the X.500 Directory. The presentation address displayed previously will be used as the value of the presentation address attribute of the application entity entries. Agreements in International OSI Implementors groups regarding the storage of Form2 (Object Identifier) AE- titles in the X.500 directory are still in draft form. Therefore, the /usr/sbin/osiapplsetup procedure will not prompt you for a Form2 AE-title. If there are errors in creating the entries, the following messages appear: osiapplsetup - Warning: X.500 Directory entries created with errors osiapplsetup - Warning: Please check /var/dna/dna_install.log for more information. Please refer to the /var/dna/dna-install.log log file for more information on the errors that occurred. You may need to check your X.500 configuration to solve the problem. 8-16 Configuring FTAM and Virtual Terminal If there are no errors in creating the entries, the following message appears: Creating entries in the X.500 Directory ... done To store the presentation address in the /etc/isoapplications file, press . If you answer n, the address will not be stored in the file. 10Would you like to store the presentation address for the applications represented by srchr in the /etc/isoapplications file? [y]: Added entries to /etc/isoapplications. Commands to start the listeners identified by the alias you specified will be added to /sbin/osi_applstartup. An FTAM listener entry using the alias "srchr" will be added to the /sbin/osi_applstartup file. A VT listener entry using the alias "srchr" will be added to the /sbin/osi_applstartup file. Modifying /sbin/osi_applstartup ... done. Press any key to continue. See Section 8.7 to continue the installation. 8.6.3 Manually Configuring the Local FTAM and VT Application Addresses If you have chosen to manually configure your local FTAM and VT addresses, the procedure displays the following: 11You have chosen to configure the OSI applications manually. There are three parts to the manual configuration: 1. Define source aliases 2. Create entries in /etc/isoapplications for remote FTAM and VT applications 3. Add listener entries to /sbin/osi_applstartup using the previously defined aliases. Press the key to continue. The first part of the manual configuration procedure adds source aliases to /etc/isoapplications. Configuring FTAM and Virtual Terminal 8-17 The definition of source aliases is necessary only if you must always know the complete address of an initiator. If no source address is defined, then one is dynamically created at run time. For FTAM the source alias is always called local_ftam. For VT the source alias is always called local_vtp. The FTAM source alias "local_ftam" already exists in /etc/isoapplications. If you would prefer not to have the "local_ftam" alias in the /etc/isoapplications file, then you may use an editor to remove the entry from /etc/isoapplications. The configuration procedure prompts you for information on defining and adding the "local_vtp" source alias to /etc/isoapplications. If the script shows a default entry for a field, press to accept the default, or enter a new value and press . To leave a field blank when there is no default, simply press . If you choose to create the local_vtp alias, the first two fields are filled in automatically. No user input is necessary. 12Do you wish to create the local_vtp alias (y/n) [n]? y Enter the alias: local_vtp Enter Application (FTAM or VT): VT Enter AP title: Enter AE qualifier: Enter Presentation Selector: psap Enter Session Selector: ssap Enter Transport Selector: tsap Enter NSAP #1: %x4145418715008002b2c347621 Enter Transport Provider #1 Name [osi]: Enter Transport Template #1 Name [default]: 8-18 Configuring FTAM and Virtual Terminal The procedure displays the entry that will be added to /etc/isoapplications: 13You have entered the following alias: local_vtp :VT:::psap.ssap.tsap. \ %x4145418715008002b2c347621, \ provider=osi,template=default: Is this correct (y/n) [y]? If you answer n, you are prompted to re-enter the alias. If you answer y, the procedure displays the following message and continues with the configuration of FTAM or VT listeners. Modifying /etc/isoapplications...done. See Section 8.7 to continue the installation. 8.7 Configuring Addresses for Remote FTAM and VT Applications This part of the configuration procedure adds entries for remote applications on your network to the /etc/isoapplications file. If you have the DEC X.500 Directory Service product installed and you elected to retrieve addressing information from the X.500 Directory, you have the option of adding entries of the Distinguished Name format and the Pattern format to /etc/isoapplications. If you choose this option, you are prompted for information to generate the X.500 Distinguished Name of the remote application. The user has the option of adding entries of the Address format regardless of whether X.500 is installed. Section 8.7.1 describes configuring to use X.500, and Section 8.7.2 describes configuring not to use X.500. Configuring FTAM and Virtual Terminal 8-19 8.7.1 If You Configure To Use X.500 If you elected to configure to use the X.500 Directory, you have the option to enter Distinguished Name format and Address format entries to /etc/isoapplications. 14This part of the configuration procedure adds entries, for remote applications on your network, to the /etc/isoapplications file. You may choose to add entries of the Distinguished Name format, the Address format, or both. If you choose to add entries of the Distinguished Name format, then you will be prompted for the names of the relevant country, organization, organizational unit, application process and application entity. If you choose to add entries of the Address format, then you will be prompted for the AP-title, AE-qualifier, Presentation selector (PSEL), Session selector (SSEL), Transport selector (TSEL), NSAPS, and Transport template and Transport provider for each NSAP. Press at the alias prompt when you have finished adding aliases of a particular format. Section 8.7.1.1 describes adding Distinguished Name format entries, Section 8.7.1.2 describes adding Address format entries, and Section 8.7.1.3 describes adding Pattern format entries. 8.7.1.1 Adding Distinguished Name Format Entries To enter Distinguished Name format entries to /etc/isoapplications, press . Otherwise, type n and press . 15Would you like to add entries of the Distinguished Name format to /etc/isoapplications? (y/n) [y]: If you choose to enter Distinguished Name format entries, you are prompted for further information. Use the information you completed in the installation checklist to reply to the questions, and after each entry, press . If the script shows a default entry for a field, press to accept the default, or enter a new value and press . To leave a field blank when there is no default, simply press . 8-20 Configuring FTAM and Virtual Terminal The entries are displayed for your review before entering them into /etc/isoapplications. The procedure will then prompt you for information to add another Distinguished Name entry to /etc/isoapplications. If you choose not to add another entry, simply press . The /usr/sbin/osiapplsetup procedure assumes that your organization's Directory Service schema follows the schema supplied by Digital's X.500 Directory Service product. If you type a question mark (?) at any of the prompts, you will receive information on valid values for a particular prompt. However, the /usr/sbin/osiapplsetup procedure will not check to make sure that the input you supply is valid. If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. 2. Manually add Distinguished Name and Pattern format entries to the /etc/isoapplications file. 16You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: remote8 Enter the Application (FTAM or VT): ftam Enter the country name [return if done]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: Enter the transport templates to be used [return when done]: The following entries of the Distinguished Name format will be added to /etc/isoapplications: Configuring FTAM and Virtual Terminal 8-21 remote8 :FTAM:template=default:/c=us/o=dec/ou=lkg/cn=remote1/cn=ftam: Is this correct? (y/n) [y]: Added the following entries to /etc/isoapplications: remote8 :FTAM:template=default:/c=us/o=dec/ou=lkg/cn=remote1/cn=ftam: You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: 8.7.1.2 Adding Address Format Entries To enter Address format entries to /etc/isoapplications, press . Otherwise, type n and press . If you choose to enter Address format entries, you are prompted for further information. Use the information you completed in the installation checklist to respond to the questions, and after each entry, press . When you have completed entering NSAPs, press at the NSAP prompt. If the script shows a default entry for a field, press to accept the default, or enter a new value and press . To leave a field blank when there is no default, simply press . 17Would you like to add entries of the Address format to /etc/isoapplications? (y/n) [y]: Enter the alias: remote9 Enter Application (FTAM or VT): VT Enter AP title: Enter AE qualifier: Enter Presentation Selector: psap Enter Session Selector: ssap Enter Transport Selector: tsap Enter NSAP #1: 103p4985 8-22 Configuring FTAM and Virtual Terminal Enter Transport Provider #1 Name [osi]: Enter Transport Template #1 Name [default]: Enter NSAP #2: (A system that has multiple addresses is called "multihomed". DECnet/OSI Planning Guide discusses multihoming.) Press at the "Enter NSAP:" prompt after you enter all the NSAPs for the application. After you enter the applications addresses, the procedure displays the information you entered and asks you to confirm. 18You have entered the following alias: remote9 :VT:::psap.ssap.tsap. \ 103p4985, \ provider=osi,template=default: Is this correct (y/n) [y]? If you answer with n, you are prompted to re-enter the information for the remote application address. If you answer with y, the procedure prompts you to enter the alias for the next remote application. When you finish adding remote application addresses, press at the "Enter the alias:" prompt. The procedure responds: Modifying /etc/isoapplications...done. 8.7.1.3 Adding Pattern Format Entries If you have the DEC X.500 Directory Service product installed and you elected to retrieve addressing information from the X.500 Directory, you have the option of adding entries of the Pattern format entries to /etc/isoapplications. If you choose this option, you are prompted for information to generate the X.500 Pattern format entries. Configuring FTAM and Virtual Terminal 8-23 If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. 2. Manually add Distinguished Name and Pattern format entries to the /etc/isoapplications file. 19This part of the configuration procedure creates entries of the Pattern format in /etc/isoapplications. Entries of the Pattern format take the following form: * :application:template_list:/c=country/o=organization/ou=org_unit /cn=*/cn=application_entity_name The alias part of the Pattern entry matches all aliases passed to the FTAM and Virtual Terminal commands. The aliases passed to the FTAM and Virtual Terminal commands are assumed to be the value of the common name attribute of an application process entry in the X.500 Directory. Would you like to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: Enter the Application (FTAM or VT): vt Enter the country name [return if none]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: Enter the name of the VT entity [VT]: Enter the name of the transport templates to be used [return when done]: The following Pattern format entry will be added to the /etc/isoapplications file: * :VT:template=default:/c=us/o=dec/ou=lkg/cn=*/cn=vt: Is this correct? (y/n) [y]: Writing Patterns to /etc/isoapplications ... done. Do you want to continue to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: n 8-24 Configuring FTAM and Virtual Terminal 8.7.2 If You Configure Not To Use X.500 If you elected not to use X.500, you can now add entries for remote applications to the /etc/isoapplications file. At the prompt, enter the first alias and press . If you choose to enter an alias, you are prompted for further information. Use the information you completed in the installation checklist to respond to the questions, and after each entry, press . If the script shows a default entry for a field, press to accept the default, or enter a new value and press . To leave a field blank when there is no default, simply press . When you have completed entering NSAPs for the alias, press at the NSAP prompt. The entire alias will display. 20This part of the configuration procedure adds aliases, for remote applications on your network, to the /etc/isoapplications file. You will be prompted for the AP-title, AE-qualifier, Presentation selector (PSEL), Session selector (SSEL), Transport selector (TSEL), NSAPS, and Transport template and Transport provider for each NSAP. Press at the alias prompt when you have finished adding aliases. Enter the alias: remote1 Enter Application (FTAM or VT): VT Enter AP title: Enter AE qualifier: Enter Presentation Selector: psap Enter Session Selector: ssap Enter Transport Selector: tsap1 Enter NSAP #1: %X4145418715004108002B23569821 Enter Transport Provider #1 Name [osi]: Enter Transport Template #1 Name [default]: Configuring FTAM and Virtual Terminal 8-25 Enter NSAP #2: (A system that has multiple addresses is called "multihomed". DECnet/OSI Planning Guide discusses multihoming.) If the alias is correct, press . You can choose to add another alias at this point. Otherwise, to end the procedure, press . 21You have entered the following alias: remote1 :VT:::psap.ssap.tsap1. \ %X4145418715004108002B23569821, \ provider=osi,template=default: Is this correct (y/n) [y]? Enter the alias: Modifying /etc/isoapplications...done. 8.8 Manually Configuring FTAM and VT Listeners The following step only appears if you elected to manually configure the local application addresses. The procedure prompts you for an alias and a queue length for each FTAM or VT listener. These listeners are added into the /sbin/osi_applstartup, and are automatically invoked at system startup time. The listener translates the alias to an address that contains the transport address on which the listener will wait for incoming connection requests. Make sure the alias you enter here was added to the /etc/isoapplications file during the previous configuration steps. The queue length is the number of outstanding transport connection requests to the listener for this alias that can be pending at any one time. 22This part of the configuration procedure adds listener entries into the /sbin/osi_applstartup file. These listeners are automatically invoked at system startup time. The questions that follow prompt you for an an alias and a queue length. Press at the alias prompt when you have finished adding listeners. 8-26 Configuring FTAM and Virtual Terminal Adding listeners for FTAM Enter the alias for the ftam_listener: remote1 Enter queue length [10]: After you finish these configuration procedures, the software modifies the system startup command file. The following message appears: Modifying /sbin/osi_applstartup... done. Once the software is installed and functioning properly, you can delete the prior versions of /usr/sbin/osiapplstartup and /etc/isoapplications file. The files you can delete have a .sav* extension, where "*" represents a version number. 8.9 Starting FTAM and VT The procedure next asks if you want to start the OSI application that you just installed. 23Would you like to start the listeners that were added to the /sbin/osi_applstartup file now that the installation is complete? (y/n) [y]: If you answer y, the system starts the FTAM and VT listeners and responds: Listeners just added to the /sbin/osi_applstartup have been started. If you answer n, the system displays the following message: You chose not to start up any listeners at this time. The listeners listed in the /sbin/osi_applstartup will be started up only when this system is rebooted. The procedure displays an optional step you can choose to perform. After verifying that the system is operating properly with the OSI Applications installed, you may wish to remove the following saved files: - /sbin/osi_applstartup.sav[n] - /etc/isoapplications.sav[n] Configuring FTAM and Virtual Terminal 8-27 8.10 Running the Installation Verification Procedure The procedure now asks you if you would like to run the Installation Verification Procedure (IVP) to see whether your node can communicate with remote nodes on the network. Note that the password does not echo when entered. To run the IVP separately at any time after installing the software, see Section 8.12. 24The DECnet/OSI FTAM and DECnet/OSI Virtual Terminal Configuration Procedure is complete. Would you like to verify the configuration by running the FTAM and Virtual Terminal IVPs (y/n) [y]: Beginning the FTAM Installation Verification Procedure... This script is executed after FTAM has been installed on your system. It verifies that FTAM has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to list a file over the network using FTAM. You will be asked for the initiator id and password for the local system. If at any time you wish to interrupt this test, enter ^C. Enter initiator id: smith Enter password for smith: ols :::ivpppm.ivpspm.ivptpm.%X4145418715004108002B3873DD21:/smith/password::/ usr/opt/DNAAPP200/usr/sbin/ftam_check /usr/opt/DNAAPP200/usr/sbin/ftam_check IVP for FTAM is successful. The installation test is finished. Beginning the DECnet/OSI Virtual Terminal V2.0 Installation Verification Procedure... This script is executed after Virtual Terminal has been installed on your system. It verifies that Virtual Terminal has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to transfer data over the network using Virtual Terminal. If at any time you wish to interrupt this test, enter ^C. 8-28 Configuring FTAM and Virtual Terminal /usr/sbin/vt_ivp /usr/sbin/vt_ivp.script /var/dna/vt_ivp.log # /usr/bin/ologin $VT_IVP_ADDRESS DEC OSF/1 Version V2.0 (srchr.lkg.dec.com) ttyp6 Login: Login: ologin: control returned to local end system # Test successful IVP for Virtual Terminal is successful. The installation test is finished. # script done 8.10.1 If the IVP Fails If a subset does not install correctly, the IVP displays a message informing you that part of the installation failed. Refer to DECnet/OSI FTAM and Virtual Terminal Use and Management for a description of error messages and corrective action. IVP for FTAM failed. The installation test is finished. If the VT portion of the IVP fails, you can look at the log file in /var/dna/vt_ivp.log. To reinstall the software, see Section 8.10.2 8.10.2 Reinstalling the Software To reinstall the software, use the setld -d subset command before repeating the installation procedure from the beginning. The value for subset is the name of the subset that you just installed. Table 1-2 lists the FTAM and Virtual Terminal subset name. Configuring FTAM and Virtual Terminal 8-29 8.11 Rebuilding the Internal Table of Commands After you install the FTAM or Virtual Terminal software, enter the rehash command at the superuser prompt. This command tells the shell to rebuild its internal table of commands within the directories in your path. Refer to csh(1) in the reference pages for more information about this command. 25# rehash 8.12 Verifying the Installation As mentioned earlier, the Installation Verification Procedure (IVP) runs as part of the FTAM and Virtual Terminal software installation procedure. However, you can also run the IVP separately at any time after installing the software. You must be a superuser to run the IVP. There are two ways to run the IVP after installation: 1. You can use the setld -v subset command. The subset is the name of the subset that you wish to verify. 2. You can also run the IVP file by typing /usr/sbin/ftam_check or /usr/sbin/vt_check and pressing at the system prompt. In the FTAM IVP, you are prompted for a valid user ID on the local system (initiator id) and the password for the local user ID. The password that you type is not displayed on the screen. 8.13 Verifying the FTAM-FTP Gateway Installation The FTAM IVP verifies that the FTAM-FTP Gateway has been installed by checking if the files are in the correct locations. To verify the FTAM-FTP Gateway installation by checking its operation, use the following two-part procedure. The first part of the procedure checks the OSI portion of the FTAM-FTP Gateway /usr/sbin/ftam2ftpd and the second part checks the Internet portion /usr/sbin/ftp2ftamd. 8-30 Configuring FTAM and Virtual Terminal 8.13.1 To Check the OSI Portion of the FTAM-FTP Gateway 1. Start up a responder in the background by executing the following command: /usr/sbin/ftam2ftpd alias & 2. Use the following command as a test: ols alias/user@localhost/password::/usr/sbin/ftam_check The user is the login name of a user on the FTAM system and password is the password for the specified user. 8.13.2 To Check the Internet Portion of the FTAM-FTP Gateway 1. Verify that the DECnet-Internet Gateway has been configured on your system by using these steps: - Issue the following command: # grep ftp /etc/inetd.conf - If you see the line: ftp stream tcp nowait root /usr/sbin/ftpd.gw ftpd Then your system has been properly configured to run the DECnet-Internet Gateway. Go to Step 2. - If you do not see the expected output, then issue the following command: # /usr/sbin/decnetsetup gateway After decnetsetup completes, go to Step 2. 2. Start up a responder in the background using the following command: /usr/sbin/ftamd alias & 3. Use the following command to connect to your current node, which is used as the FTAM-FTP Gateway host: ftp localhost 4. At the name prompt (which displays localhost and the name of the user who initiated the FTP session), type in the FTAM alias and user name in the following format: Name (localhost::username): alias::user Configuring FTAM and Virtual Terminal 8-31 The user is the name of a user on that FTAM system. 5. At the password prompt, type in the password of the user. 6. Use the following command as a test: ls /usr/sbin/ftam_check 7. End the FTP session by using the close or bye commands. 8-32 Configuring FTAM and Virtual Terminal Part III _________________________________________________________________ Appendixes Part III, the Appendixes, shows sample installations and configurations, discusses NSAP addresses and software subsets, and installation requirements. This information can be found in the following appendixes: o Appendix A - Sample DECnet/OSI Installation o Appendix B - Sample DECnet/OSI Advanced and Basic Configurations o Appendix C - Sample FTAM/VT Installations and Configurations o Appendix D - Understanding and Creating NSAP Addresses o Appendix E - Software Subsets and Installation Requirements A _________________________________________________________________ Sample Installation A.1 Sample Installation Log The following is a sample installation log file. # setld -l /kits/osf1/DNA_V3.0/axp DECnet/OSI for DEC OSF/1 AXP V3.0-0 (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. To install and configure DECnet/OSI on this system, choose all subsets from the Standard Run-time Environment, and any of the other subsets desired for additional functionality. Please see the installation guide for further details on selecting subsets. Hit to continue: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. - Common Trace Facility Components: 1) CTF Collector Components 2) CTF User Environment 3) DEC OSF/1 WAN Utilities - DECnet/OSI Standard Run-time Environment: 4) DECnet/OSI Base Components 5) DECnet/OSI Datalink Components 6) DECnet/OSI Network Management Sample Installation A-1 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): - OSI Applications: 7) OSI Application Gateways 8) OSI Application On-line Docs 9) OSI Applications - Optional DECnet/OSI Components: 10) DECnet-Internet Gateway 11) DECnet/OSI MOP Utilities 12) DECnet/OSI Miscellaneous Software 13) DECnet/OSI Programming Tools 14) DECnet/OSI RFC1006 (OSI/TCP) 15) DECnet/OSI Reference Pages --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): Or you may choose one of the following options: 16) ALL of the above 17) CANCEL selections and redisplay menus 18) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 16 You are installing the following optional subsets: - Common Trace Facility Components: CTF Collector Components CTF User Environment DEC OSF/1 WAN Utilities - DECnet/OSI Standard Run-time Environment: DECnet/OSI Base Components DECnet/OSI Datalink Components DECnet/OSI Network Management - OSI Applications: OSI Application Gateways OSI Application On-line Docs OSI Applications A-2 Sample Installation Press RETURN to display the next screen: - Optional DECnet/OSI Components: DECnet-Internet Gateway DECnet/OSI MOP Utilities DECnet/OSI Miscellaneous Software DECnet/OSI Programming Tools DECnet/OSI RFC1006 (OSI/TCP) DECnet/OSI Reference Pages Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. DEC OSF/1 WAN Utilities Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. DECnet/OSI Network Management Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Datalink Components Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Base Components Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet-Internet Gateway Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Reference Pages Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI MOP Utilities Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying DECnet/OSI Miscellaneous Software Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying Sample Installation A-3 DECnet/OSI Programming Tools Copying from /kits/osf1/DNA_V3.0/axp (disk) Working....Tue Nov 1 14:58:34 EST 1994 Verifying DECnet/OSI RFC1006 (OSI/TCP) Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying OSI Applications Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying OSI Application Gateways Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying OSI Application On-line Docs Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying CTF Collector Components Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying CTF User Environment Copying from /kits/osf1/DNA_V3.0/axp (disk) Verifying Installing WAN Utilities V1.1 for DEC OSF/1 Systems (c) Digital Equipment Corporation. 1994. All Rights Reserved. Creating directories and symbolic links for ZZAUTIL110 ... done. Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) Creating directories and symbolic links for DNANETMAN300 ... done. Configuring "DECnet/OSI Network Management " (DNANETMAN300) Configuring DECnet/OSI Network Management over TCP/IP ... done. Creating directories and symbolic links for DNADLI300 ... done. Configuring "DECnet/OSI Datalink Components " (DNADLI300) Creating directories and symbolic links for DNABASE300 ... done. Configuring "DECnet/OSI Base Components " (DNABASE300) Creating directories and symbolic links for DNAINETGW300 ... done. Configuring "DECnet-Internet Gateway " (DNAINETGW300) A-4 Sample Installation Creating directories and symbolic links for DNAMAN300 ... done. Configuring "DECnet/OSI Reference Pages " (DNAMAN300) Creating directories and symbolic links for DNAMOP300 ... done. Configuring "DECnet/OSI MOP Utilities " (DNAMOP300) Creating directories and symbolic links for DNAUTIL300 ... done. Configuring "DECnet/OSI Miscellaneous Software " (DNAUTIL300) Creating directories and symbolic links for DNAPGMR300 ... done. Configuring "DECnet/OSI Programming Tools " (DNAPGMR300) Creating directories and symbolic links for DNARFC1006300 ... done. Configuring "DECnet/OSI RFC1006 (OSI/TCP) " (DNARFC1006300) Creating directories and symbolic links for DNAAPP300 ... done. Modifying /etc/magic ... done. Configuring "OSI Applications " (DNAAPP300) Creating directories and symbolic links for DNAAPPGWY300 ... done. Configuring "OSI Application Gateways " (DNAAPPGWY300) Creating directories and symbolic links for DNAAPPMAN300 ... done. Configuring "OSI Application On-line Docs " (DNAAPPMAN300) Installing CTF for DEC OSF/1 Systems Collector Components (c) Digital Equipment Corporation. 1994. All Rights Reserved. Creating directories and symbolic links for CTABASE130 ... done. Configuring "CTF Collector Components " (CTABASE130) Installing CTF for DEC OSF/1 Systems User Environment (c) Digital Equipment Corporation. 1994. All Rights Reserved. Creating directories and symbolic links for CTAANAL130 ... done. To complete your installation of DECnet/OSI for DEC OSF/1 AXP V3.0-0, please perform the following steps: - Build a new kernel by executing the command: # /usr/sbin/decnetsetup kernel - Reboot the system, to use this new kernel. - Configure or reconfigure DECnet/OSI by executing the command: # /usr/sbin/decnetsetup [basic|advanced] Please refer to the Installation Guide for details. Sample Installation A-5 To complete your installation of the OSI Applications, please take the following steps: - Ensure that DECnet/OSI for DEC OSF/1 is properly installed and configured. - Configure the OSI Application software by executing the command: # /usr/sbin/osiapplsetup - After verifying that the system is operating properly, you may wish to remove the following saved file: /etc/magic.sav[n] Please refer to the Installation Guide for details. No further questions. A-6 Sample Installation B _________________________________________________________________ Sample Configurations This appendix includes sample ADVANCED and BASIC Configuration logs, as well as a sample Configuration Verification Procedure log. B.1 Sample DECnet/OSI Advanced Configuration The following sample log file illustrates an advanced installation. In this case, the system has a Phase IV compatible address, configures its addresses manually, and selects a communications controller from those displayed. The system is configured as a DTSS backup courier. The user supplies the following information: o A DECnet/OSI node name o A Phase IV compatible address o A Phase IV prefix. o An alternate DECdns node synonym directory o Two network entity titles (NETs) o One communications controller B.2 Sample Log File # decnetsetup advanced DECnet/OSI for DEC OSF/1 AXP V3.0-0 DECnet/OSI Configuration Procedure. There will be a pause while this procedure gathers some information from your system. (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. Sample Configurations B-1 Now you will be asked a few questions. If you need more information to answer a question, you can type ? at the prompts, or consult the DECnet/OSI installation guide. To configure DECnet, you need to know your full Phase V node name and network address(es). Please review the installation guide, and the checklists in particular, before continuing. The Phase V node name is the full name of the node object in the DNS namespace. It includes the namespace nickname, and the full list of directories leading to the node object name. Examples of Phase V node names include: LOCAL:.TomThumb vbo:.afsg.comms.werner XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter The namespace nickname is terminated with a colon (:). The node object name must begin with a dot (.), and no element of the name (namespace name, directory, or node object name) can be a null string. What is the Phase V node name? [No Default]: dec:.lkg.agn2au The node synonym is an alphanumeric character string echo between 1 and 6 characters long that contains at least one alphabetic character. If this system had previously been running DECnet Phase IV software, then the old node name should be used as the synonym. If this system is joining a DECnet network for the first time, any name can be used for the synonym, as long as it meets the criteria listed above, and is unique within the network. If you do not enter a synonym, then this node will only be known by its full name. Enter a null string ("") to specify no synonym. What is the Phase IV compatible synonym? [agn2au]: A Phase V system may or may not use a DECnet Phase IV style node address. A node address of 0 indicates that this Phase V system will be communicating with Phase V nodes only. If your network contains some systems running DECnet Phase IV, you may wish to specify a compatible address in order to communicate with them. If your network consists solely of Phase V and/or OSI systems, this may not be required. The DECnet Phase IV node address consists of an area number (between 1 and 63), and a node number within the area (between 1 and 1023). Should you specify a Phase IV address, you will also be prompted for the Initial Domain Part (IDP) of your network's OSI address. What is the Phase IV compatible node address? [0]: 12.175 B-2 Sample Configurations Having chosen a Phase IV compatible address for this system, you may also specify a Phase IV Prefix, which together with the node address forms the complete network address for this system. All nodes within a single addressing domain contain the same IDP in their network addresses. The default value of "49::" is the "private network" IDP, which is appropriate for a Phase IV DECnet network that contains some Phase V systems. Please contact your network manager if you are in doubt as to your network's Phase IV Prefix value, or indeed if you are unsure how to answer this question at all. What is the Phase IV Prefix value for this network? [49::]: If you have a large network and would like to use an alternate node synonym directory rather than using the default node synonym directory of ".DNA_NodeSynonym", you may enter one at the following prompt. The value for the alternate node synonym directory must be a DECdns directory full name (for example: .USA_Synonyms). What is the node synonym directory in the dec namespace? [.DNA_NodeSynonym]: If this system is being configured in a DNA Phase V environment, you should answer "Yes" to the following question. If the network is a heterogeneous OSI environment, answer "No" in order to explicitly enter this system's network address(es). Will this system autoconfigure its network addresses? [y]: This procedure has attempted to determine what communications devices are configured on this system. If the default answer is chosen in the following question, all such devices will be initialized to run the DECnet/OSI software. If you wish to run DECnet on only certain devices, please choose them from the list below. Enter the list of communications devices on which you will be running the DECnet Phase V software. If there is more than one device, separate them by spaces. [te0 te1 ]: te0 Will this system be configured as a DTSS clerk only? (y/n) [y]: Will this system be configured as a DECnet/Internet Gateway? (y/n) [n] Do you want this system to service MOP requests? (y/n) [y] Sample Configurations B-3 Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: dec:.lkg.agn2au Node Synonym: agn2au Phase IV Address: 12.175 Phase IV Prefix: 49:: Network Devices: te0 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will be a DNS clerk in the dec namespace. Do you wish to complete this DECnet/OSI configuration? [continue] Creating defaults file. Creating Initialization NCL scripts Creating /usr/sbin/decnetstartup Creating /usr/sbin/osi_applstartup Updating /var/dna/dna_version Modifying /usr/sbin/decnetshutdown Event Logging ... Creating Session Control Creating /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Attempting to contact local DNS server...please wait. DNS clerk successfully configured. Node name reset to dec:.lkg.agn2au DTSS ... Node Enabled ... Event Logging The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/xtiso/cots 32 57 /dev/streams/xtiso/clts 32 58 The following STREAMS devices were created: Name Major Minor ---- ----- ----- B-4 Sample Configurations /dev/streams/rfc1006 32 59 Setting Session Control attributes There will be a brief pause as the dec namespace is checked, to see if this node is already registered. This node is registered in the dec namespace. Updating address towers for node object dec:.lkg.agn2au ... done The configuration of DECnet/OSI is completed. You can test DECnet functionality with the utility /usr/sbin/dnet_check . This performs various local and remote functions, and requires an account (and password) on this system and one other DECnet node. After verifying that the system is operating properly with DECnet installed you may wish to remove the following saved files: - /var/dna/scripts/start_*.ncl.sav[n] decnetsetup completed successfully. # B.3 Sample DECnet/OSI Basic Configuration The following sample log file illustrates a basic configuration that uses a Local namespace. In this case, the system has a Phase IV address, autoconfigures its addresses, and is a DTS clerk. The user supplies the following information: o A DECnet/OSI node name that includes local:. o A Phase IV node synonym o A Phase IV compatible address Sample Configurations B-5 B.4 Sample Log File # decnetsetup DECnet/OSI for DEC OSF/1 AXP V3.0-0 DECnet/OSI Configuration Procedure. There will be a pause while this procedure gathers some information from your system. (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. Now you will be asked a few questions. If you need more information to answer a question, you can type ? at the prompts, or consult the DECnet/OSI installation guide. To configure DECnet, you need to know your full Phase V node name and network address(es). Please review the installation guide, and the checklists in particular, before continuing. The Phase V node name is the full name of the node object in the DNS namespace. It includes the namespace nickname, and the full list of directories leading to the node object name. Examples of Phase V node names include: LOCAL:.TomThumb vbo:.afsg.comms.werner XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter The namespace nickname is terminated with a colon (:). The node object name must begin with a dot (.), and no element of the name (namespace name, directory, or node object name) can be a null string. What is the Phase V node name? [No Default]: dec:.lkg.agn2au The node synonym is an alphanumeric character string echo between 1 and 6 characters long that contains at least one alphabetic character. If this system had previously been running DECnet Phase IV software, then the old node name should be used as the synonym. If this system is joining a DECnet network for the first time, any name can be used for the synonym, as long as it meets the criteria listed above, and is unique within the network. If you do not enter a synonym, then this node will only be known by its full name. Enter a null string ("") to specify no synonym. What is the Phase IV compatible synonym? [agn2au]: B-6 Sample Configurations A Phase V system may or may not use a DECnet Phase IV style node address. A node address of 0 indicates that this Phase V system will be communicating with Phase V nodes only. If your network contains some systems running DECnet Phase IV, you may wish to specify a compatible address in order to communicate with them. If your network consists solely of Phase V and/or OSI systems, this may not be required. The DECnet Phase IV node address consists of an area number (between 1 and 63), and a node number within the area (between 1 and 1023). Should you specify a Phase IV address, you will also be prompted for the Initial Domain Part (IDP) of your network's OSI address. What is the Phase IV compatible node address? [0]: 12.175 The DECnet-Internet Gateway subset has not been installed on this system. If you wish to use this capability, please use the setld utility to load this subset. See the installation guide for details. Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: dec:.lkg.agn2au Node Synonym: agn2au Phase IV Address: 12.175 Phase IV Prefix: 49:: Network Devices: te0 te1 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will be a DNS clerk in the dec namespace. Do you wish to complete this DECnet/OSI configuration? [continue] Creating defaults file. Creating Initialization NCL scripts Creating /usr/sbin/decnetstartup Creating /usr/sbin/osi_applstartup Updating /var/dna/dna_version Creating /usr/sbin/decnetshutdown Event Logging ... Sample Configurations B-7 Configuring "CTF Collector Components " (CTABASE130) Ensuring all underlying dependencies are configured. ++++++++++++++++++++++++++++++ Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) Adding WAN lock entries to /sys/kern/lockinfo.c ... done. ZZAUTIL110 Configured. ------------------------------ CTABASE130 configured. Creating Session Control Creating /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Attempting to contact local DNS server...please wait. DNS clerk successfully configured. Node name reset to dec:.lkg.agn2au DTSS ... Node Enabled ... Event Logging Event Logging ... The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/rfc1006 32 57 DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. The following STREAMS devices were created: Name Major Minor ---- ----- ----- /dev/streams/xtiso/cots 32 58 /dev/streams/xtiso/clts 32 59 Setting Session Control attributes There will be a brief pause as the dec namespace is checked, to see if this node is already registered. This node is registered in the dec namespace. Updating address towers for node object dec:.lkg.agn2au ... done The configuration of DECnet/OSI is completed. B-8 Sample Configurations You can test DECnet functionality with the utility /usr/sbin/dnet_ check . This performs various local and remote functions, and requires an account (and password) on this system and one other DECnet node. After verifying that the system is operating properly with DECnet installed you may wish to remove the following saved files: - /var/dna/scripts/start_*.ncl.sav[n] decnetsetup completed successfully. B.5 Sample Configuration Verification Procedure The following is a sample configuration verification procedure log which you might see when you issue a /usr /sbin/dnet_check command. # /usr/sbin/dnet_check DECnet/OSI for DEC OSF/1 AXP V3.0-0 DECnet/OSI Configuration Verification Procedure. There will be a pause while this procedure gathers some information from your system. (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. This script should be executed after DECnet/OSI has been installed and configured on your system. It verifies that network communication can take place between your local node and other remote nodes on the network. It also verifies that your local node can communicate with itself. During the tests which follow you will be asked a few questions. If you require further information, enter a question mark (?) and explanatory text will be provided. Of course, you will be prompted again for the requested information. What is your Phase V node name? [DEC:.lkg.agn2au]: The first test checks that some of the DECnet/OSI network management entities are running. Each of the following displays should indicate that the entity is in state "On". # ncl show Routing state Node 0 Routing AT 1994-11-01-15:18:02.614-05:00I----- Status Sample Configurations B-9 State = On # ncl show Session Control state Node 0 Session Control AT 1994-11-01-15:18:03.306-05:00I----- Status State = On # ncl show Node 0 state Node 0 AT 1994-11-01-15:18:03.933-05:00I----- Status State = On The following command attempts to look up your node object in the DECdns namespace. This is a simple way to test that the DNS Clerk is functioning correctly. # decnet_register show node DEC:.lkg.agn2au directory_service decdns Directory Service: DECdns Node name: DEC:.lkg.agn2au Phase IV synonym: AGN2AU Node address: 49::00-0C:AA-00-04-00-AF-30:21 (12.175) Node address: 49::00-0C:AA-00-04-00-AF-30:20 (12.175) Node address: 41:45418715:00-41:08-00-2B-30-7D-E6:21 Node address: 41:45418715:00-41:08-00-2B-30-7D-E6:20 Number of nodes reported on: 1 Enter the name of a remote node? [No Default]: notrix remote node notrix Is this correct? (y/n) [y]: The following command will check that the remote node you specified is reachable: # ncl show node notrix state Node notrix AT 1994-11-01-15:18:35.265-05:00I12.367 B-10 Sample Configurations Status State = On The next group of tests attempts to copy files over the network using DECnet/OSI, and to run the loopback application. The first test will copy a file to the local node using DECnet/OSI utilities, and if successful, the second test will copy a file to and from the remote system you specified earlier. For each test, you will be asked to provide the user account and password to be used for that system. Enter user account on DEC:.lkg.agn2au [No Default]: thomas Enter password for user thomas on DEC:.lkg.agn2au [No Default]: # dcp /usr/sbin/dnet_check DEC:.lkg.agn2au/thomas/password/::dnetcheck.rnd # dcp DEC:.lkg.agn2au/thomas/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm DEC:.lkg.agn2au/thomas/password/::dnetcheck.rnd # ncl loop loopback application name DEC:.lkg.agn2au, length 1, count 10, format 00 # ncl loop loopback application name DEC:.lkg.agn2au, length 2047, count 50 Enter user account on notrix [No Default]: thomas Enter password for user thomas on notrix [No Default]: # dcp /usr/sbin/dnet_check notrix/thomas/password/::dnetcheck.rnd # dcp notrix/thomas/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm notrix/thomas/password/::dnetcheck.rnd # ncl loop loopback application name notrix, length 1, count 10, format 00 # ncl loop loopback application name notrix, length 2047, count 50 Removing log file /tmp/dnet_check.log Removing the file copied across the network # exit # Sample Configurations B-11 C _________________________________________________________________ Sample FTAM and Virtual Terminal Configurations This appendix contains sample configurations for the FTAM and Virtual Terminal software. Note that these are only examples. Your configuration may vary slightly. Refer to Section C.1 if you are performing an autoconfiguration. Refer to Section C.2 if you are performing a manual configuration. C.1 Sample FTAM and VT Autoconfiguration # /usr/sbin/osiapplsetup DECnet/OSI for DEC OSF/1 AXP V2.0 FTAM and Virtual Terminal Configuration Procedure (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. The FTAM and Virtual Terminal Configuration Procedure allows you to configure addressing information for FTAM and Virtual Terminal applications on both local and remote systems. There is already an /etc/isoapplications file installed on your system, which indicates that DECnet/OSI FTAM and DECnet/OSI Virtual Terminal have been previously configured on this system. Would you like to continue with the configuration? (y/n) [y]: You may elect to do a full configuration or to add aliases to the /etc/isoapplications database. Please select one of the following choices: 1. Autoconfigure Application Addresses 2. Manually Configure Application Addresses 3. Add aliases for remote applications to /etc/isoapplications 4. Exit the FTAM and Virtual Terminal Configuration Procedure Sample FTAM and Virtual Terminal Configurations C-1 For help at any time, enter a question mark at the prompt, or refer to the DECnet/OSI for DEC OSF/1 Installation Guide. Selection [1]: Starting the Autoconfiguration procedure... The DEC X.500 Directory Service software is installed on your system. Would you like to configure DECnet/OSI FTAM and DECnet/OSI Virtual Terminal to be able to retrieve addressing information from the X.500 Directory? (y/n) [y]: DECnet/OSI FTAM and DECnet/OSI Virtual Terminal will be configured to retrieve addressing information from the X.500 Directory. The first part of the configuration procedure will add entries for the local FTAM and Virtual Terminal listeners to the /etc/isoapplications database. Optionally, the addresses of these listeners will be stored in the X.500 Directory. Finally, commands to start the local listeners will be added to the /sbin/osi_applstartup file. Enter the name that will represent the local FTAM and Virtual Terminal listeners on your system [srchr]: The alias "srchr" will represent the FTAM and Virtual Terminal listeners on your system. Is this correct? (y/n) [y]: The following values will be used as the presentation addresses of the FTAM and Virtual Terminal applications represented by the alias "srchr": %x0001.%x0001.%x0001.%X4145418715004108002B3873DD21 (FTAM) %x0001.%x0001.%x0002.%X4145418715004108002B3873DD21 (VT) Are these values correct? (y/n) [y]: The values displayed above may be stored in the X.500 Directory, the /etc/isoapplications file, or both. Would you like to register the local FTAM and Virtual Terminal listeners represented by "srchr" in the X.500 Directory? (y/n) [y]: You will be prompted for information that will be used to generate the X.500 Distinguished Name of the applications represented by "srchr". C-2 Sample FTAM and Virtual Terminal Configurations Enter the country name [return if done]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: The following entries will be created in the X.500 Directory, with corresponding entries of the Distinguished Name format created in /etc/isoapplications: /c="us"/o="dec"/ou="lkg"/cn="srchr"/cn="ftam" /c="us"/o="dec"/ou="lkg"/cn="srchr"/cn="vt" Is this correct? (y/n) [y]: Creating entries in X.500 Directory ... done. Would you like to store the presentation addresses for the applications represented by "srchr" in the /etc/isoapplications file? [y]: Added entries to /etc/isoapplications. An FTAM listener entry using the alias "srchr" will be added to the /sbin/osi_applstartup file. A VT listener entry using the alias "srchr" will be added to the /sbin/osi_applstartup file. Modifying /sbin/osi_applstartup ... done. Press the key to continue. This part of the configuration procedure adds entries, for remote applications on your network, to the /etc/isoapplications file. You may choose to add entries of the Distinguished Name format, the Address format, or both. If you choose to add entries of the Distinguished Name format, then you will be prompted for the names of the relevant country, organization, organizational unit, application process, application entity and transport templates. If you choose to add entries of the Address format, then you will be prompted for the AP-title, AE-qualifier, Presentation selector (PSEL), Session selector (SSEL), Transport selector (TSEL), NSAPS, and Transport template and Transport provider for each NSAP. Sample FTAM and Virtual Terminal Configurations C-3 Press at the alias prompt when you have finished adding aliases of a particular format. Would you like to add entries of the Distinguished Name format to /etc/isoapplications? (y/n) [y]: You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: remote1 Enter the Application (FTAM or VT): FTAM Enter the country name [return if done]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: Enter the name of the FTAM entity [FTAM]: Enter the transport templates to be used [return when done]: default Enter the transport templates to be used [return when done]: The following Distinguished Name format entry will be added to /etc/isoapplications: remote1 :FTAM:template=default:/c=us/o=dec/ou=lkg/cn=remote1/cn=ftam: Is this correct? (y/n) [y]: Added the following entry to /etc/isoapplications: remote1 :FTAM:template=default:/c=us/o=dec/ou=lkg/cn=remote1/cn=ftam: You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: C-4 Sample FTAM and Virtual Terminal Configurations Would you like to add entries of the Address format to /etc/isoapplications? (y/n) [y]: Enter the alias: remote2 Enter Application (FTAM or VT): VT Enter AP title: Enter AP qualifier: Enter Presentation Selector: psap Enter Session Selector: ssap Enter Transport Selector: tsap Enter NSAP #1: %x41454187150028002b2c43215621 Enter Transport Provider #1 Name [osi]: Enter Transport Template #1 Name [default]: Enter NSAP #2: You have entered the following alias: remote2 :VT:::psap.ssap.tsap. \ %x41454187150028002b2c43215621, \ provider=osi,template=default: Is this correct (y/n)? [y]? Enter the alias: Modifying /etc/isoapplications...done. This part of the configuration procedure creates entries of the Pattern format in /etc/isoapplications. The osiapplsetup procedure will create Pattern format entries of the following form: * :application:template_list:/c=country/o=organization/ou=org_ unit /cn=*/cn=application_entity_name The alias part of the Pattern format entry matches all aliases passed to the FTAM and Virtual Terminal commands. osiapplsetup will assume that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Sample FTAM and Virtual Terminal Configurations C-5 Would you like to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: Enter the Application (FTAM or VT): VT Enter the country name [return if done]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: Enter the name of the VT entity [VT]: Enter the transport templates to be used [return when done]: The following Pattern format entry will be added to the /etc/isoapplications file: * :VT:template=default:/c=us/o=dec/ou=lkg/cn=*/cn=vt: Is this correct? (y/n) [y]: Writing Pattern entry to /etc/isoapplications ... done. Do you want to continue to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: n Would you like to start the listeners that were added to the /sbin/osi_applstartup file now that the installation is complete? (y/n) [y]: Listeners just added to the /sbin/osi_ applstartup have been started. After verifying that the system is operating properly with DECnet/OSI FTAM and DECnet/OSI Virtual Terminal installed, you may wish to remove the following saved files: - /sbin/osi_applstartup.sav[n] - /etc/isoapplications.sav[n] The DECnet/OSI FTAM and DECnet/OSI Virtual Terminal Configuration Procedure is complete. Would you like to verify the configuration by running the FTAM and Virtual Terminal IVPs (y/n) [y]: Beginning the FTAM Installation Verification Procedure... C-6 Sample FTAM and Virtual Terminal Configurations This script is executed after FTAM has been installed on your system. It verifies that FTAM has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to list a file over the network using FTAM. You will be asked for the initiator id and password for the local system. If at any time you wish to interrupt this test, enter ^C. Enter initiator id: smith Enter password for smith: ols :::ivpppm.ivpspm.ivptpm.%X4145418715004108002B3873DD21:/smith/password:: /usr/opt/DNAAPP200/usr/sbin/ftam_check /usr/opt/DNAAPP200/usr/sbin/ftam_check IVP for FTAM is successful. The installation test is finished. Beginning the DECnet/OSI Virtual Terminal V2.0 Installation Verification Procedure... This script is executed after Virtual Terminal has been installed on your system. It verifies that Virtual Terminal has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to transfer data over the network using Virtual Terminal. If at any time you wish to interrupt this test, enter ^C. /usr/sbin/vt_ivp /usr/sbin/vt_ivp.script /var/dna/vt_ivp.log # /usr/bin/ologin $VT_IVP_ADDRESS DEC OSF/1 Version V2.0 (srchr.lkg.dec.com) ttypd login: login: ologin: control returned to local end system # Test successful IVP for Virtual Terminal is successful. The installation test is finished. # script done Sample FTAM and Virtual Terminal Configurations C-7 C.2 Sample Manual Configuration # /usr/sbin/osiapplsetup DECnet/OSI for DEC OSF/1 AXP V2.0 FTAM and Virtual Terminal Configuration Procedure (c) Digital Equipment Corporation. 1993, 1994. All Rights Reserved. The FTAM and Virtual Terminal Configuration Procedure allows you to configure addressing information for FTAM and Virtual Terminal applications on both local and remote systems. There is already an /etc/isoapplications file installed on your system, which indicates that DECnet/OSI FTAM and DECnet/OSI Virtual Terminal have been previously configured on this system. Would you like to continue with the configuration? (y/n) [y]: You may elect to do a full configuration or to add aliases to the /etc/isoapplications database. Please select one of the following choices: 1. Autoconfigure Application Addresses 2. Manually Configure Application Addresses 3. Add aliases for remote applications to /etc/isoapplications 4. Exit the FTAM and Virtual Terminal Configuration Procedure For help at any time, enter a question mark at the prompt, or refer to the DECnet/OSI for DEC OSF/1 Installation Guide. Selection [1]: 2 Starting the Manual Configuration procedure... The DEC X.500 Directory Service software is installed on your system. Would you like to configure DECnet/OSI FTAM and DECnet/OSI Virtual Terminal to be able to retrieve addressing information from the X.500 Directory? (y/n) [y]: DECnet/OSI FTAM and DECnet/OSI Virtual Terminal will be configured to retrieve addressing information from the X.500 Directory. You have chosen to configure the OSI applications manually. There are three parts to the manual configuration: C-8 Sample FTAM and Virtual Terminal Configurations 1. Define source aliases 2. Create entries in /etc/isoapplications for remote FTAM and VT applications 3. Add listener entries to /sbin/osi_applstartup using the previously defined aliases. Press the key to continue. The first part of the manual configuration procedure adds source aliases to /etc/isoapplications. The definition of source aliases is necessary only if you must always know the complete address of an initiator. If no source address is defined, then one is dynamically created at run time. For FTAM the source alias is always called local_ftam. For VT the source alias is always called local_vtp. The FTAM source alias "local_ftam" already exists in /etc/isoapplications: local_ ftam:FTAM:{1314559}::PSAP.SSAP.TSAP.%x4145418715004108002b3873dd21: If you would prefer not to have the "local_ftam" alias in the /etc/isoapplications file, then you may use an editor to remove the entry from /etc/isoapplications. The VT source alias "local_vtp" already exists in /etc/isoapplications: local_ vtp:VT:{1314559}::PSAP.SSAP.TSAP.%x4145418715004108002b3873dd21: If you would prefer not to have the "local_vtp" alias in the /etc/isoapplications file, then you may use an editor to remove the entry from /etc/isoapplications. Press the key to continue. This part of the configuration procedure adds entries, for remote applications on your network, to the /etc/isoapplications file. You may choose to add entries of the Distinguished Name format, the Address format, or both. Sample FTAM and Virtual Terminal Configurations C-9 If you choose to add entries of the Distinguished Name format, then you will be prompted for the names of the relevant country, organization, organizational unit, application process, application entity and transport templates. If you choose to add entries of the Address format, then you will be prompted for the AP-title, AE-qualifier, Presentation selector (PSEL), Session selector (SSEL), Transport selector (TSEL), NSAPS, and Transport template and Transport provider for each NSAP. Press at the alias prompt when you have finished adding aliases of a particular format. Would you like to add entries of the Distinguished Name format to /etc/isoapplications? (y/n) [y]: You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: remote8 Enter the Application (FTAM or VT): ftam Enter the country name [return if done]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: Enter the name of the FTAM entity [FTAM]: Enter the transport templates to be used [return when done]: The following Distinguished Name format entry will be added to /etc/isoapplications: remote8 :FTAM:template=default:/c=us/o=dec/ou=lkg/cn=remote8/cn=ftam: Is this correct? (y/n) [y]: Added the following entry to /etc/isoapplications: remote8 :FTAM:template=default:/c=us/o=dec/ou=lkg/cn=remote8/cn=ftam: C-10 Sample FTAM and Virtual Terminal Configurations You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: Would you like to add entries of the Address format to /etc/isoapplications? (y/n) [y]: Enter the alias: remote9 Enter Application (FTAM or VT): vt Enter AP title: Enter AE qualifier: Enter Presentation Selector: psap Enter Session Selector: ssap Enter Transport Selector: tsap Enter NSAP #1: 103p4985 Enter Transport Provider #1 Name [osi]: Enter Transport Template #1 Name [default]: Enter NSAP #2: You have entered the following alias: remote9 :VT:::psap.ssap.tsap. \ 103p4985, \ provider=osi,template=default: Is this correct (y/n) [y]? Enter the alias: Modifying /etc/isoapplications...done. This part of the configuration procedure creates entries of the Pattern format in /etc/isoapplications. Sample FTAM and Virtual Terminal Configurations C-11 The osiapplsetup procedure will create Pattern format entries of the following form: * :application:template_list:/c=country/o=organization/ou=org_ unit /cn=*/cn=application_entity_name The alias part of the Pattern format entry matches all aliases passed to the FTAM and Virtual Terminal commands. osiapplsetup will assume that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Would you like to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: Enter the Application (FTAM or VT): vt Enter the country name [return if done]: us Enter the organization name: dec Enter the organizational unit [return if done]: lkg Enter the organizational unit [return if done]: Enter the name of the VT entity [VT]: Enter the transport templates to be used [return when done]: The following Pattern format entry will be added to the /etc/isoapplications file: * :VT:template=default:/c=us/o=dec/ou=lkg/cn=*/cn=vt: Is this correct? (y/n) [y]: Writing Pattern entry to /etc/isoapplications ... done. Do you want to continue to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: n This part of the configuration procedure adds listener entries into the /sbin/osi_applstartup file. These listeners are automatically invoked at system startup time. The questions that follow prompt you for an an alias and a queue length. Press at the alias prompt when you have finished adding listeners. Adding listeners for FTAM Enter the alias for the ftam_listener: C-12 Sample FTAM and Virtual Terminal Configurations Adding listeners for VT Enter the alias for the vt_listener: Modifying /sbin/osi_applstartup ... done. After verifying that the system is operating properly with the OSI Applications installed, you may wish to remove the following saved files: - /sbin/osi_applstartup.sav[n] - /etc/isoapplications.sav[n] The DECnet/OSI FTAM and DECnet/OSI Virtual Terminal Configuration Procedure is complete. Would you like to verify the configuration by running the FTAM and Virtual Terminal IVPs (y/n) [y]: Beginning the FTAM Installation Verification Procedure... This script is executed after FTAM has been installed on your system. It verifies that FTAM has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to list a file over the network using FTAM. You will be asked for the initiator id and password for the local system. If at any time you wish to interrupt this test, enter ^C. Enter initiator id: smith Enter password for smith: ols :::ivpppm.ivpspm.ivptpm.%X4145418715004108002B3873DD21:/smith/password:: /usr/opt=/DNAAPP200/usr/sbin/ftam_check /usr/opt/DNAAPP200/usr/sbin/ftam_check IVP for FTAM is successful. The installation test is finished. Beginning the DECnet/OSI Virtual Terminal V2.0 Installation Verification Procedure... Sample FTAM and Virtual Terminal Configurations C-13 This script is executed after Virtual Terminal has been installed on your system. It verifies that Virtual Terminal has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to transfer data over the network using Virtual Terminal. If at any time you wish to interrupt this test, enter ^C. /usr/sbin/vt_ivp /usr/sbin/vt_ivp.script /var/dna/vt_ivp.log # /usr/bin/ologin $VT_IVP_ADDRESS DEC OSF/1 Version V2.0 (srchr.lkg.dec.com) ttyq3 login: login: ologin: control returned to local end system # Test successful IVP for Virtual Terminal is successful. The installation test is finished. # script done C-14 Sample FTAM and Virtual Terminal Configurations D _________________________________________________________________ Creating NSAP Addresses This appendix discusses the format of NSAP addresses for DECnet/OSI systems and describes how to get unique identification for your DECnet/OSI network. You need this information to: o Plan for and perform the transition to DECnet/OSI. o Design or create a namespace. o Register DECnet/OSI systems in the namespace. o Configure DECnet/OSI systems for communications. The DECnet/OSI addressing scheme for DECnet/OSI nodes complies with the ISO 8348 Addendum 2 addressing standard. This scheme uses the concepts of global addressing, addressing authorities, and addressing domains. Global network addressing is an ISO scheme designed to provide unique network addresses throughout the world. A global network address is called a network service access point (NSAP). Because it is used to determine the destination node for all packets, the NSAP must be unique for each node in a network. Some NSAP field values are assigned by an allocation authority, and some you assign yourself for your organization. Every NSAP has two primary fields: o Initial domain part (IDP) - consists of two subfields o Domain-specific part (DSP) - consists of four subfields Figure D-1 shows the parts of an NSAP and Network Entity Title (NET).. Creating NSAP Addresses D-1 D.1 IDP Values The IDP helps ensure that NSAP values are globally unique. For this reason, IDP values are assigned by recognized authorities or are based on another value (such as a Telex number) that has already been assigned by some authority. The IDP has two fields: authority and format identifier (AFI) and initial domain identifier (IDI). o Authority and format identifier (AFI) This field identifies the authority that allocated the globally unique IDP. The AFI value always consists of two decimal digits (from 0 to 9). Table D-1 lists the recognized values and the corresponding allocation authorities. An AFI value of 49 indicates a private network, one that is not interconnected with other OSI networks and therefore does not need a globally unique IDP. Table D-1 shows the NSAP field lengths for each AFI. Table_D-1_Information_for_Building_Unique_NSAPs____________ Maximum Maximum Use AFI if the Digits Allocation AFI Digits in Leading Digit in Authority________Value__IDI_________of_the_IDI_is:___preDSP Private 49 0 (none) N/A 20 ISO DCC 39 3 (exact) N/A 16 (single-country organizations) ISO 6523-ICD 47 4 (exact) N/A 16 (international organizations) F.69 (Telex 41 8 nonzero 12 number) 55 (maximum) zero E.163 43 12 nonzero 8 (telephone 57 (maximum) zero number) E.164 (ISDN 45 15 nonzero 4 number)__________59_____(maximum)___zero___________________ D-2 Creating NSAP Addresses o Initial domain identifier (IDI) This field, combined with the AFI, makes the IDP globally unique for the allocating authority. Depending on the allocation authority identified in the AFI, the IDI value can be explicitly assigned by the authority, or it can be based on some other value that has already been assigned by that authority. The IDI value consists of zero or more decimal digits (from 0 to 9). The actual number of digits depends on the AFI. Some AFIs specify fixed-length IDIs, where you must enter all the digits in the IDI. Other AFIs specify variable-length IDIs, where you can enter up to the specified number of digits. Table D-1 gives the IDI lengths for each AFI. If you are using the private AFI (49), do not specify an IDI. AFI 49 indicates a private network not interconnected with other OSI networks. D.2 DSP Values The DSP provides unique addresses within a specific IDP value. Different routing architectures might format and use the DSP in different ways. The format used by DECnet/OSI IS-IS, based on OSI IS-IS (ISO 10589), divides the DSP into four fields: o Prefix to the DSP (preDSP) o Local area field (LocArea) o Node ID field o Selector field (SEL) o Prefix to the DSP (preDSP) Also called the high-order part of the DSP (HO-DSP), the format of this field is not defined by DECnet/OSI. If you assign a value to this field, it becomes part of the area, in conjunction with the IDP and local area values, and identifies the node's location for level 2 routing. If nodes have the same IDP and local area values, but different preDSP values, the nodes are in different routing areas. Creating NSAP Addresses D-3 The preDSP value is zero or more hexadecimal digits (from 0 to F). The actual number of digits that you can enter depends on the AFI. Table D-1 gives the preDSP sizes appropriate for each AFI. The American National Standards Institute (ANSI) is the ISO DCC allocation authority in the United States. For NSAPs with AFI 39, allocated by the ISO DCC, and AFI 47, allocated by ISO 6523-ICD, the allocating authorities may assign an additional value for you to enter into the preDSP field. The reason for this additional value is that they have available only a limited number of IDIs, and they may give the same IDI value to different organizations. When this occurs, the preDSP value ensures global uniqueness. Allocation authorities other than ANSI may format the preDSP in other ways. Digital recommends that you do not assign a value to the preDSP field when you use AFIs other than 39 and 47. ANSI formats the preDSP into the following subfields: - DSP Format Identifier (DFI) The value of this field is allocated by ANSI and consists of two hexadecimal digits. It indicates the format used for the rest of the high-order DSP, which is DFI-ORG-RES-RD. - Organization ID (ORG) The value of this field is allocated by ANSI and consists of six hexadecimal digits. This value is different for every organization and ensures global uniqueness. - Reserved (RES) The value of this field is allocated by ANSI and consists of four hexadecimal digits. This is a reserved field, whose value must always be zero. - Routing Domain (RD) The value of this field is allocated by each individual organization and consists of four hexadecimal digits. This field is used to separate an organization's network into multiple routing domains. It is defined so that routing domains can be D-4 Creating NSAP Addresses uniquely identified by intermediate systems using a single short address prefix, without the necessity of listing multiple address prefixes, one for each local area within that routing domain. If your network needs only one routing domain, Digital recommends that you use the value 0000. o Local area field (LocArea) This value represents the local area within the routing domain (the node's local network area). Use the LocArea value, in conjunction with the IDP and preDSP values, to identify the node's location for level 2 routing. This value is used as the next four digits (2 octets) in the DSP. The local area value is four hexadecimal digits (from 0 to F). Values 00-01 to 00-3F are reserved for use as Phase IV compatible area numbers for areas 1 to 63. o Node ID field This part of the DSP identifies a node within an area. It represents the node ID within the local area. Use it to identify the node for level 1 routing purposes. Use the node ID value as the next 12 digits (6 octets) in the DSP. This value is 12 hexadecimal digits (from 0 to F). Node IDs that range from AA-00-04-00- 00-00 to AA-00-04-00-FF-FF are reserved for use as Phase IV compatible node IDs (1.1 to 63.1023). o Selector field (SEL) This part of the DSP indicates the Transport protocol you want to use. The selector value consists of two hexadecimal digits (from 0 to F). This value is used as the next two digits (1 octet) in the DSP. DECnet/OSI uses these SEL values: o 20 (for NSAP specifying NSP Transport) o 21 (for NSAP specifying OSI Transport) o 00 (for a NET) Creating NSAP Addresses D-5 D.3 NSAP Entry and Display Formats Enter an NSAP using either of two standard formats, DNA format or OSI format. DNA format consists of: aa:iii...ii:pp-p...p-pp-ll-ll:nn-nn-nn-nn-nn-nn:ss OSI format consists of: aaiii...ii+ppp...pppllllnnnnnnnnnnnnss where: aa is the AFI value in decimal ii... is the IDI value in decimal pp... is the preDSP value in hexadecimal ll... is the local area value in hexadecimal nn... is the node ID value in hexadecimal ss is the selector value in hexadecimal DECnet/OSI always displays NSAPs in DNA format because this format separates the various fields, making the NSAP easier to read. The preDSP, local area, and node ID values are punctuated with hyphens after every two digits. When you enter an NSAP using DNA format: o You can type hyphens anywhere. o You can omit hyphens. o If the local area or node ID fields start with zeros, you can omit them. o You cannot omit leading zeros for the IDI and preDSP values. Leading zeroes in these fields affect the value of the NSAP when it is used in routing messages. When you enter an NSAP using OSI format, you must always enter the proper number of digits because there is no other way to indicate where one field ends and the next starts, except between the IDP and DSP. The following examples show NSAPs in both formats. NSAP with an IDP with the private AFI: DNA format: 49::00-01:12-34-56-78-9A-BC:21 OSI format: 49+0001123456789ABC21 D-6 Creating NSAP Addresses NSAP with an IDP with an allocated AFI and IDI: DNA format: 41:23456789:A5:08-00-2B-19-0E-6C:20 OSI format: 4123456789+00A508002B190E6C20 If an NSAP has an unrecognized AFI or does not have the correct number of digits in the IDP or DSP, it is displayed in binary format. This format represents the value of the NSAP as a string of hexadecimal digits, as follows: /3100A508002B190E6C20 D.4 Converting Phase IV Addresses to NSAPs To convert a Phase IV address to an NSAP, you encode the Phase IV address into the local area and node ID fields of the NSAP. Fill in all the other NSAP fields in the normal manner. To encode a Phase IV address into these fields, follow these steps: 1. Make the NSAP local area by using the Phase IV area in hexadecimal. For example, Phase IV area 1 becomes NSAP local area 00-01, and Phase IV area 63 becomes NSAP local area 00-3F. 2. The NSAP node ID represents the Phase IV area and ID. Construct it as follows: a. Convert the Phase IV area and ID to a single decimal value, using: (area * 1024) + ID b. Convert the resulting value to a four-digit hexadecimal number, and swap the first and last pairs of hexadecimal digits. Use these as the last four digits of the NSAP's node ID field, and prefix them with AA-00-04-00. For example, with: o Network IDP 41:45436192: o Phase IV address 43.258 Creating NSAP Addresses D-7 o The node using NSP Transport then create the NSAP as follows: IDP and selector = 41:45436192:local-area:node-id:20 43 decimal = 2B hexadecimal (local area) (43 * 1024) + 258 = 44290 decimal 44290 decimal = AD02 hexadecimal AD02 swapped = 02AD hexadecimal (node ID) The resulting NSAP is 41:45436192:00-2B:AA-00-04-00-02- AD:20. D.5 Converting NSAPs to Phase IV Addresses To convert an NSAP to a Phase IV address, reverse the process described in the previous section. You get the Phase IV area by converting the local area field from hexadecimal to decimal. If the resulting value is greater than 63, the NSAP does not contain a Phase IV address. Calculate the Phase IV node ID from the node ID field as follows: 1. If the node ID field does not begin with AA-00-04-00, the NSAP does not contain a Phase IV address. If it does begin with this value, extract the last four digits of the node ID field and use them in the following steps. 2. Swap the first and the last pairs of digits, and convert the value to decimal. 3. Calculate the Phase IV area and ID values, using: area = value / 1024 id = value - (area * 1024) If the calculated area value is not equal to the area value obtained from the NSAP's local area field, the NSAP does not contain a valid Phase IV address. For example, with NSAP 37:81076541234:00-19:AA-00-04-00-62- 64:21, calculate the Phase IV address by: D-8 Creating NSAP Addresses 19 hexadecimal (from local area) = 25 decimal 62-64 (from node ID) = 6462 hexadecimal 6462 hexadecimal = 25698 decimal 25698/1024 = area of 25 25698 - (25 * 1024) = id of 98 The resulting Phase IV address is 25.98. D.6 Forms of the NSAP Displayed by NCL Some NCL commands accept and display NETs, area addresses, node IDs, or address prefixes. These values are subsets of a node's full NSAP. This section defines these values and shows how the example NSAP in Figure D-2 is divided into these values. Creating NSAP Addresses D-9 Network Entity Title (NET) Same as the NSAP, with a selector field of 00. Identifies a node when the specific Transport protocol to be used is either unknown or irrelevant. Area Address Consists of the IDP, preDSP, and the local area fields of the NSAP. Identifies a level 2 routing area. Node ID Consists of the node ID field of the NSAP. Identifies a particular node within a level 2 routing area. D-10 Creating NSAP Addresses Address Prefix Consists of some leading portion of the NSAP, and can be of any length from zero digits up to the full length of the NSAP. Can be used in a reachable address table to indicate that packets with a destination NSAP beginning with a specified address prefix are to be routed through a specified circuit. Phase IV Prefix Consists of all values up to (but not including) the local area field. Includes the AFI, IDI, and, if used, the preDSP. This value is used by DECnet/OSI when converting between Phase IV addresses and NSAPs. D.7 How to Obtain a Unique IDP and PreDSP If your network is to be interconnected with other networks, its NSAP must have a unique IDP and, possibly, preDSP, to differentiate it from all other networks. For a unique IDP (and preDSP), you can contact an allocation authority, or you can create your own according to the guidelines in the following sections. The following sections describe where to obtain an IDI (and preDSP) for a specific AFI. D.7.1 For a Private Network (AFI 49) If your network will not be interconnected with other OSI networks, you do not need a unique IDP. Use the AFI 49 with no IDI. D.7.2 Allocation Authority for Single-Country Organizations (AFI 39) The IDI value is assigned directly for each country by an authorized registration agent, according to ISO Standard 3166. The registration authority agent in the United States is the American National Standards Institute (ANSI), with offices in New York City. In this case, the resulting IDP is entered as given by the allocation authority. This IDP might also require the allocation of a value to be placed in the preDSP. Creating NSAP Addresses D-11 D.7.3 Allocation Authority for International Organizations (AFI 47) The IDI value is assigned directly for each international organization by an authorized registration agent, according to ISO Standard 6523-ICD. One place where you can obtain information about registration authority agents is ANSI, with offices in New York City. In this case, the resulting IDP is entered as given by the allocation authority. This IDP might also require the allocation of a value to be placed in the preDSP. D.7.4 Using a Telex Number for the IDI (AFIs 41 and 55) The IDI value is based on CCITT Recommendation F.69 and is created from a Telex number that has been assigned to your company or organization. The parts of this IDI are: o Destination code (country or network number), either two or three digits See the appropriate CCITT reference for the list of destination codes. o Local Telex number, six or five digits (depending on the destination code) Choose one Telex number and use it to create a unique IDI value for your network. This number serves simply as a unique number that has been assigned to you. When choosing a Telex number, make sure it conforms to CCITT Recommendation F.69. Example: Destination code (for Switzerland) = 45 Local Telex number = 43 61 92 Resulting IDP value = 41:45436192: D-12 Creating NSAP Addresses D.7.5 Using a Telephone Number for the IDI (AFIs 43 and 57) The IDI value is based on CCITT Recommendation E.163 and is created from a public switched telephone network (PSTN) number that has been assigned to your company or organization. The parts of this IDI are: o World zone number o Country or geographic area number o Local number Consult your local PSTN for the world zone and the country numbers. Choose one telephone number and use it to create a unique IDI value for your network. This number serves simply as a unique number that has been assigned to you. Example: World zone number (for U.S.A.) = 1 Geographic area number (for Massachusetts) = 508 Local number = 555-1192 Resulting IDP value = 43:15085551192: D.7.6 Using an ISDN Number for the IDI (AFIs 45 and 59) The IDI value is based on CCITT Recommendation E.164 and is created from an integrated services digital network (ISDN) number that has been assigned to your organization. ISDN is a technology offered by the telephone carriers of the world that combines voice and digital network services in one media, allowing for digital data services through a single "wire." The standards that define ISDN are specified by CCITT. The parts of this IDI are: o Country code (CC) The country code is one to three digits and is administered by CCITT. o National destination code (NDC) For the U.S.A. and Canada, the NDC is the three-digit area code. o Subscriber number (SN) Creating NSAP Addresses D-13 For the U.S.A. and Canada, the SN is the local telephone number. The NDC and SN, which together make up the National Significant Number, are administered within each country, usually by the PTT organizations. Choose one ISDN number and use it to create a unique IDI value for your network. This number serves simply as a unique number that has been assigned to you. Example: Country code (for U.S.A.) = 1 National destination code (for New York) = 212 Subscriber number = 555-6172 Resulting IDP value = 45:12125556172 D.8 Example: NSAP Fields This section shows examples of how an ANSI-formatted NSAP is divided into its component fields. For all examples, except for the one that shows a Phase IV prefix, the fields have the following values: ___________________________________________________________ Field_______Value__________________________________________ AFI 39 IDI 840 DFI 80 ORG 01E240 RES 0000 RD 0000 LocArea 0001 Node ID 08002B143136 SEL_________21_____________________________________________ D-14 Creating NSAP Addresses The example showing the Phase IV prefix uses node ID and SEL values that are Phase IV compatible, and these fields have the following values: ___________________________________________________________ Field_______Value__________________________________________ NodeID AA0004000104 SEL_________20_____________________________________________ Figure D-3 shows the example NSAP using DNA format. Figure D-4 shows the same examples using OSI format. D.9 Example: Using Values Allocated by ANSI This section applies to users in the United States who have applied to ANSI for a unique network identifier in the ISO DCC format. With values assigned by ANSI, an NSAP has the following DNA format: AFI:IDI:DFI-ORG-RES-RD-LocArea:NodeID:SEL Table D-2 explains the NSAP fields used in this format. Creating NSAP Addresses D-15 Table_D-2_Entering_NSAP_Field_Values_______________________ Field__Value___________Meaning_____________________________ AFI 39 ANSI provides a decimal value. Enter as two decimal digits. IDI 840 ANSI provides a decimal value. Enter as three decimal digits. DFI 128 ANSI provides a decimal value. Enter as two hexadecimal digits. ORG dddddd ANSI provides a decimal value. Enter as six hexadecimal digits. RES 0000 Value reserved by ANSI for future use. Enter as four zeros. RD dddd Enter as four hexadecimal digits. LocAreadddd Enter as four hexadecimal digits. Node dddddddddddd Enter as 12 hexadecimal digits. ID SEL____dd______________Enter_as_two_hexadecimal_digits.____ All values supplied by ANSI are decimal numbers. Use the AFI and IDI in your NSAP as decimal values. However, due to the encoding rules of binary syntax NSAPs, you must convert the DFI and ORG values to hexadecimal. You can easily convert these two values from decimal to hexadecimal using a calculator or using the operating system's calculator feature. Use the bc command. For example, with an ORG value of 123456, use the following commands to convert the values: # bc obase=16 /* Set the output radix to base 16 (hex) */ 128 /* Enter the decimal DFI value */ 80 /* Resulting hex value */ 123456 /* Enter the decimal ORG value */ 1E240 /* Resulting hex value */ D-16 Creating NSAP Addresses Using these values, the resulting NSAP has the following DNA NSAP format: 39:840:80-01E240-0000-RD-LocArea:NodeID:SEL While this section discusses NSAP values from ANSI, the same information also applies to other DECnet/OSI addressing values, including the NET, Phase IV prefix, and address prefixes. In addition, this information is based upon the draft ANSI standard: "Data Communications - Structure and Semantics of the Domain Specific Part (DSP) of the OSI Network Service Access Point (NSAP) Address" ANSI might review and modify this standard. Creating NSAP Addresses D-17 E _________________________________________________________________ Software Subsets and Installation Requirements E.1 DECnet/OSI for DEC OSF/1 Software Subsets Table E-1 provides a description of the DECnet/OSI for DEC OSF/1 subsets. Use this information to determine the amount of disk space, as well as which subsets to install. Table E-1 Summary of DECnet/OSI Software Subsets and Disk __________Space____________________________________________ Subset___________Name__________________Dependencies________ DECnet/OSI Base DNABASE300 OSF/1 Base System Components (OSFBASE130). DECnet/OSI Datalink Components (DNADLI300). DECnet/OSI Network Management (DNANETMAN300). Disk space: 5.8 MB DECnet/OSI DNADLI300 OSF/1 Base System Datalink (OSFBASE130) Components Disk space: 25 KB (continued on next page) Software Subsets and Installation Requirements E-1 Table E-1 (Cont.) Summary of DECnet/OSI Software Subsets __________________and_Disk_Space___________________________ Subset___________Name__________________Dependencies________ DECnet-Internet DNAINETGW300 OSF/1 Basic Gateway Networking Services (OSFCLINET130). DECnet/OSI Base Components (DNABASE300). Disk space: 300 KB OSI DNAAPP300 OSF/1 Basic Applications Networking Services Base (OSFCLINET130). DECnet/OSI Base Components (DNABASE300). Disk space: 3.2 MB OSI DNAAPPGWY300 OSF/1 Basic Applications Networking Services Gateways (OSFCLINET130). DECnet/OSI Base Components (DNABASE300). Disk space: 125 MB DECnet/OSI DNAMAN300 OSF/1 Document Reference Pages Preparation Tools (OSFDCMT130) Disk space: 400 KB OSI DNAAPPMAN300 OSF/1 Document Applications Preparation Tools Reference Pages (OSFDCMT130) Disk space: 61 KB (continued on next page) E-2 Software Subsets and Installation Requirements Table E-1 (Cont.) Summary of DECnet/OSI Software Subsets __________________and_Disk_Space___________________________ Subset___________Name__________________Dependencies________ DECnet/OSI DNARFC1006 DEC OSF/1 Base RFC1006 (OSI System (OSFBASE130). /TCP) DECnet/OSI Network Management (DNANETMAN300). Disk space: 650 KB DECnet/OSI MOP DNAMOP300 DECnet/OSI Utilities Network Management (DNANETMAN100) Disk space: 525 KB DECnet/OSI DNANETMAN300 OSF/1 Base System Network (OSFBASE130) Management Disk space: 8 MB DECnet/OSI DNAPGMR300 OSF/1 Base System Programming (OSFBASE130) Tools Disk space: 22.5 MB DECnet/OSI DNAUTIL300 OSF/1 Base System Miscellaneous (OSFBASE130) Software Disk space: 1.6 MB CTF User CTAANAL120 OSF/1 Base System Environment (OSFBASE130). CTF Base (CTABASE120). Disk Space: 4900 KB CTF Collector CTABASE120 OSF/1 Base System Component (OSFBASE130). CTF Utilities (ZZAUTIL101). Disk Space: 870 KB (continued on next page) Software Subsets and Installation Requirements E-3 Table E-1 (Cont.) Summary of DECnet/OSI Software Subsets __________________and_Disk_Space___________________________ Subset___________Name__________________Dependencies________ DEC OSF/1 WAN ZZUTIL101 OSF/1 Base System Utilities (OSFBASE130) _______________________________________Disk_space:_85_KB___ E-4 Software Subsets and Installation Requirements _________________________________________________________________ Index A ANSI (cont'd) _______________________________ assigned values Address converting into NSAPs, defined, D-1 D-15 Address prefix field of NSAP authorized registration agent example, D-9 , D-11 Addressing getting an IDI from, D-11 creating NSAPs, D-1 to D-17 Answers standards, D-1 changing, 3-3, 4-4 Advanced configuration, 2-19 confirming, 3-13, 4-20 communication devices, 4-1 Area address field of NSAP DECdts server, 4-1 example, D-9 namespace, 4-1 Autoconfiguring network requirements, 4-1 addresses, 4-13 sample script, B-1 Autoregistration starting, 4-7 by decnetsetup, 3-16, 4-24 stopping, 4-3 AFI field of NSAP B defined, D-2 _______________________________ length, D-2 Backup Allocation authority, D-2 before starting installation, allocating unique IDP, D-2 2-3, 7-2 for international Basic configuration, 2-19 organizations, D-12 communication device, 3-1 for single-country DECdns clerk, 3-1 organizations, D-11 DECdts clerk, 3-1 ISO 6523-ICD, D-4 defaults, 3-1 ISO DCC, D-4 requirements, 3-1 providing IDP, D-11 to D-14 sample script, B-5 Alternate Node Synonym, 4-12 starting, 3-7 ANSI stopping, 3-4 allocation of AFIs, D-4 and registration authority agents, D-12 Index-1 Continuing the configuration, C______________________________ 3-13, 4-21 CCITT Converting ISDN recommendation NSAPs to Phase IV addresses, used for IDI field of D-8 NSAP, D-13 CTF Collector Component subset Changing answers, 3-3, 4-4 , 1-6 Characters, valid for full name, 3-8, 4-8 D______________________________ Checking for DECnet, 2-3 DEC OSF/1 WAN Utilities subset Checking for DECnet/OSI, 2-3, , 1-6 7-2 DECdns Choosing configuration clerk configuration, 3-15 procedures, 2-19 clerk role, 4-19 Clerk configuring, 4-19 DECdns, 3-14, 3-15, 4-19 full name, 3-7, 4-7 DECdts, 3-14, 4-18 Local namespace, 3-9, 4-9 CLNS, 4-25 Local Naming Option, 1-1 Communication devices namespace, 4-19 multiple, 4-15 remote server, 3-17, 4-24 selecting, 4-15 valid characters, 3-8, 4-8 supported, 4-16 DECdts Compliance clerk role, 4-18 with OSI, D-1 configuring, 4-17 configuration server role, 4-18 stopping, 8-12 DECnet-Internet Gateway Configuration configuring, 3-18, 4-20 procedures, 2-19 decnetsetup command, 3-18, tasks, 1-1 4-20 Configuring DECnet-Internet Gateway DECdns clerk, 4-19 configuration, 2-19 DECdts clerk, 4-18 DECnet-Internet Gateway subset DECdts server, 4-18 , 1-6 DECnet-Internet Gateway, DECnet/OSI 3-18, 4-20 node name, 3-7, 4-7 network addresses, 4-13 DECnet/OSI Base Components Confirming subset, 1-4 answers, 3-13, 4-20 DECnet/OSI CTF User example, 4-21 Environment subset, 1-6 Connecting to remote server, DECnet/OSI Datalink (DLI) 3-17, 4-24 Components subset, 1-4 CONS, 4-25 Index-2 DECnet/OSI for DECnet/OSI FTAM-FTP Gateway subsets, 1-3 verifying installation of, DECnet/OSI MOP Utilities 8-30 subset, 1-6 Full name, 3-7, 4-7 DECnet/OSI Network Management Local namespace, 3-9 subset, 1-4 Local Namespace, 4-9 DECnet/OSI Programming Tools valid characters, 3-8, 4-8 subset, 1-6 DECnet/OSI Reference Pages G______________________________ subset, 1-5 Guest account, 2-6 DECnet/OSI RFC 1006, 1-6 DECnet/OSI using X.25, 4-25 H______________________________ Default Help, 3-4, 4-4, 8-12 node synonym, 3-10, 4-10 values, 3-4, 4-4, 8-12 Deleting subsets, 2-4, 7-3 I______________________________ Disk space, 2-2, 7-2 IDI field of NSAP checking, 2-2, 7-2 defined, D-2 requirements, 2-2, 7-2 getting from authorized Distribution media, 2-2, 7-2 registration agent, D-11 CDROM, 2-6, 7-5 length, D-2 mounting, 2-6, 7-5 with ISDN number, D-13 DNA IDP format default, 4-12 displayed for NSAP, D-6 standards, 4-12 using in NSAP, D-6 supplying, 4-11 example, D-6, D-15 IDP field of NSAP DNA format for NETs, 4-14 using unique dnsconfigure, 3-17, 4-24 reason for, D-11 DSP field of NSAP with ISDN number, D-13 format, D-3 with telephone number, D-13 with Telex number, D-12 E______________________________ Installation End System PAK, 1-7 restarting, 2-18 Extended addresses, 4-13 sample script, A-1 Extended System PAK, 1-8, 4-1 verification program, 3-18 verifying, 8-28, 8-30 F______________________________ Installation tasks, 1-1 First DECnet/OSI system, 1-1, Installation Verification 4-1 Procedure FTAM configuration after installation, 8-30 sample script, C-1 during installation, 8-28 running, 8-30 See also IVP, 8-30 Index-3 Intermediate system, 4-13 MOP (cont'd) Internet network kit, 2-7, 7-6 running standalone, 3-13, IS-IS Routing Protocol, D-3 4-20 ISDN Multihoming systems, 4-13 CCITT recommendation, D-13 defined, D-13 N IVP, 3-18, 4-25, 6-1 _______________________________ requirements, 6-1 Name Service running, 6-1 primary, 3-4, 4-4 search path, 3-4, 4-4 J______________________________ secondary, 3-4, 4-4 Joining a namespace, 3-17, Namespace configuring, 4-19 4-25 distributed, 3-16, 4-24 local, 3-16, 4-19, 4-23 K______________________________ PAK requirements, 1-8 Kernel rebuild registering nodes in, 3-16, failure, 2-16 4-24 space requirements, 2-2 VAX DNS Version 1, 1-2 X.25 support, 2-15 Namespace nickname kernel rebuild command Local namespace, 3-9, 4-9 completion, 2-16 valid characters in, 3-8, RFC1006, 2-16 4-8 Kernel rebuild command NET, 4-13 standard, 2-15 autoconfiguring, 4-13 WANDD support, 2-15 default, 4-15 DNA format, 4-14 L______________________________ example, 4-14, D-9 LMF, 2-4, 7-3 manually configuring, 4-14 Local area field of NSAP, D-3 node identification Local namespace, 3-6, 3-9, example, D-10 4-6, 4-9 transport selector field, clerk configuration, 3-15 4-14 Local Namespace, 4-9 Network Local Naming Option, 1-1 private Log file required AFI, D-3, D-11 creating, 3-7, 4-7, 8-13 required IDI, D-11 Network address autoconfiguring, 4-13 M______________________________ configuring, 4-13 Manually configuring network manually configuring, 4-14 addresses, 4-14 Node ID, 4-14 MOP, 3-13, 4-20 Node ID field of NSAP, D-3 configuring without DECnet example, D-9 /OSI, 3-13, 4-20 Index-4 Node name, DECnet/OSI, 3-7, NSAP 4-7 IDI (cont'd) Node Object, 3-10, 4-10 defined, D-2 Node registration getting from authorized automatic, 3-16, 4-24 registration agent, Node synonym D-11 default, 3-10, 4-10 length, D-2 Phase IV compatible, 3-10, with ISDN number, D-13 4-10 IDP registering later, 3-10, defined, D-2 4-11 using unique specifying none, 3-10, 4-11 reason for, D-11 NSAP, 4-11, D-1 to D-17 with ISDN number, D-13 address prefix with telephone number, example, D-9 D-13 AFI with Telex number, D-12 defined, D-2 local area, D-3 length, D-2 NET allocation authorities, D-4 example, D-9 allocation authority, D-2, node ID, D-3 D-11, D-12 example, D-9 area address preDSP, D-3 example, D-9 PreDSP authorized registration agent subfields, D-4 , D-11 private network's AFI, D-11 converting Phase IV addresses private network's IDI, D-11 to NSAPs, D-7 transport selector, D-3 converting to Phase IV Transport selector addresses, D-8 defined, D-5 defined, D-1 use for, D-1 displayed by NCL, D-9 values assigned by ANSI DSP converting into NSAPs, format, D-3 D-15 example, D-9 NSP examples, D-6 to D-7, D-14 specified in Transport to D-17 selector field of NSAP, fields of, D-1 to D-5 D-5 format DNA, D-6 O______________________________ example, D-6, D-15 Online reference manual DNA displayed, D-6 OSI, D-6 See DECnet/OSI for DEC OSF/1 example, D-6, D-15 Reference Pages subset formats of, D-6 IDI Index-5 OSI compliance, D-1 Q______________________________ format Quitting the configuration, using in NSAP, D-6 3-13, 4-21 example, D-6, D-15 OSI Applications Base subset, R 1-5 _______________________________ OSI Applications Gateways, 1-5 Reboot, 2-19 OSI Applications Reference Rebuilding the internal table Pages, 1-5 of commands, 8-30 OSI configuration Registration agent, D-11 starting, 8-13 Reinstalling OSI Transport Service after failure, 8-29 specified in Transport Remote server, 3-17, 4-24 selector field of NSAP, access, 3-17, 4-25 D-5 address, 3-17, 4-24 Restarting the configuration, P 3-13, 4-21 _______________________________ Restarting the installation, PAK 2-18 End System, 1-7 RFC1006 only installation, Extended System, 1-8, 4-1 2-10 Phase IV RFC1006 only kernel rebuild compatible synonym, 3-10, command, 2-16 4-10 RFC1106 subset, 1-6 prefix, 4-11 Router, 4-13 Phase IV compatible address, 3-11, 4-11 S Planning _______________________________ addressing Search path, 3-4, 4-4 creating NSAPs, D-1 to backtranslation, 3-5, 4-5 D-17 configuring, 3-2, 3-5, 4-5 PreDSP field of NSAP, D-3 decnet-dirsvc.conf file, length, D-2 3-2, 3-5, 3-6, 4-5, 4-6 subfields, D-4 file, 3-2, 3-5, 4-5 Previous version of DECnet modifying, 3-6, 4-6 /OSI, 2-3, 7-3 naming, 3-5, 4-5 Private network naming template, 3-5, 4-4 AFI, D-11 primary name service, 3-4, required, D-3 4-4 IDI, D-11 secondary name service, 3-4, Privileges 4-4 See Superuser Server DECdts, 4-18 Index-6 Set load command, 2-7, 7-6 Set load command options T______________________________ setld -d, 8-29 TP0, 4-25 setld -v, 8-30 TP2, 4-25 Software subsets, 1-3 Transport selector field of Standard kernel rebuild NSAP, D-3 command, 2-15 defined, D-5 Standards example, D-10 addressing, D-1 compliance with CCITT U______________________________ ISDN recommendation, D-13 /usr/sbin/dnet_check, 3-18 OSI, D-1 Starting advanced configuration, 4-7 V______________________________ basic configuration, 3-7 Valid characters creating a log file, 3-7, for namespace nickname, 3-8, 4-7, 8-13 4-8 OSI applications VAX DNS Version 1 namespace, configuration, 8-13 1-2 Stopping Verifying installation, 8-28, advanced configuration, 4-3 8-30 basic configuration, 3-4 Version 1 name server, 3-17, configuration, 8-12 4-25 Stopping the configuration, Version checking, 2-3, 7-2 3-13, 4-21 Virtual Terminal configuration Subsets, 1-3 sample script, C-1 copying, 2-6 copying to disk, 2-6 W deleting, 2-4, 7-3 _______________________________ installing, 7-5 WANDD subset support, 2-15 previous version of DECnet WANrouter, 4-13 /OSI, 2-3, 7-3 selecting, 2-7, 7-6 X______________________________ verifying, 2-11, 7-7 X.25 Superuser, 2-2, 2-4, 7-1, 7-3 configuring, 4-25 System files, modifying, 2-15 X.25 subset support, 2-15 Index-7