DEC_Network_Integration_Server________________ Installation and Configuration for OpenVMS, ULTRIX and DEC OSF/1 Order Number: AA-Q61BA-TE Revision/Update Information: This is a new manual Software Version: DECNIS[TM] V2.3 __________________________________________________________ First Printing, March 1994 While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Possession, use, or copying of the software described in this documentation 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. © Digital Equipment Corporation 1994. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha AXP, Bookreader, DEC, DECmcc, DECnet, DECNIS, DECstation, DECterm, DECwindows, Digital, MicroVAX, OpenVMS, ULTRIX, VAX, VAXcluster, VAXstation, VMS, VT200, VT220, VT300, and the DIGITAL Logo. IBM is a registered trademark of International Business Machines Corporation. MS-DOS is a registered trademark of Microsoft Corporation. OSF and OSF/1 are registered trademarks of Open Software Foundation, Inc. OSI is a registered trademark of CA Management, Inc. UNIX is a registered trademark of Unix System Laboratories, Inc. a wholly owned subsidiary of Novell, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. xi 1 Introduction 1.1 Summary of Steps Required.................... 1-1 Part I OpenVMS Load Hosts: Installation and Configuration 2 Installing: OpenVMS Load Hosts 2.1 OpenVMS Background Information............... 2-1 2.2 Parameter Values on DECnet-VAX Extensions Load Hosts................................... 2-2 2.2.1 Setting VIRTUALPAGECNT (Virtual Page Count)................................... 2-2 2.2.1.1 VIRTUALPAGECNT Values.................. 2-2 2.2.1.2 How to Set VIRTUALPAGECNT.............. 2-2 2.2.2 Setting PGFLQUO.......................... 2-3 2.2.2.1 PGFLQUO Values......................... 2-3 2.2.2.2 How to Set PGFLQUO..................... 2-3 2.2.3 Setting BYTLM Quota...................... 2-3 2.2.3.1 Loading: Calculating the BYTLM Quota... 2-3 2.2.3.2 Finding Receive Buffers and Device Buffer Size............................ 2-4 2.2.3.3 Finding the Service Enabled Circuits... 2-4 2.2.3.4 Receiving Dumps: BYTLM Quota........... 2-4 2.2.3.5 How to Set the BYTLM Quota Value....... 2-4 2.3 OpenVMS Installation Procedure............... 2-5 2.4 OpenVMS Online Documentation................. 2-5 2.4.1 DECNIS Problem Solving Manual............ 2-5 iii 2.5 After Installation .......................... 2-6 2.5.1 Configuring a DECNIS for the First Time..................................... 2-6 2.5.2 Updating a Previously Installed DECNIS... 2-6 2.5.3 Verifying the Installation............... 2-7 2.5.4 Deleting Installed Files................. 2-7 2.5.5 Checking Your Terminal Setup............. 2-7 2.5.5.1 Type of Terminal....................... 2-7 2.5.5.2 Terminal Setup......................... 2-8 2.5.6 Reporting Problems....................... 2-8 2.6 VAXcluster Load Hosts........................ 2-8 2.7 Installing on Multiple Load Hosts............ 2-9 3 Using the Load-Host Configurator: OpenVMS Load Hosts 3.1 What Is the Load-Host Configurator?.......... 3-1 3.1.1 Definition of a Load Host................ 3-1 3.1.2 Load Protocol............................ 3-1 3.2 Starting the Load-Host Configurator.......... 3-2 3.3 Menu Options................................. 3-2 3.4 How to Enter Load Information................ 3-3 3.5 DECnet/OSI Load Hosts: Load Information...... 3-3 3.5.1 Load Client Name ........................ 3-3 3.5.1.1 Finding the Load Client Name........... 3-3 3.5.2 Hardware Address......................... 3-4 3.5.2.1 Finding the Hardware Address........... 3-4 3.5.3 MOP Circuit ............................. 3-4 3.5.3.1 Finding the MOP Circuit Name........... 3-4 3.5.3.2 Requirement for MOP Circuit............ 3-4 3.5.4 Phase IV Address......................... 3-4 3.5.5 Type of Loading.......................... 3-5 3.5.5.1 Definition of Nonvolatile (Flash) Memory................................. 3-5 3.5.5.2 Advantages of Nonvolatile Memory Loading................................ 3-5 3.5.6 Specifying a Dump File................... 3-5 3.5.7 Use of DNS by the Configurators.......... 3-6 3.5.7.1 Background: the DECNIS and DECdns...... 3-6 3.5.7.2 Generating KNOWN TOWER Commands........ 3-6 3.5.8 DNS Node Name (DECdns Users Only)........ 3-7 3.5.9 DNS Node Synonym (DECdns Users Only)..... 3-7 3.6 DECnet-VAX Extensions Load Hosts: Loading Information.................................. 3-8 iv 3.6.1 Load Client Name......................... 3-8 3.6.1.1 Requirements for the Load Client Name................................... 3-8 3.6.2 Hardware Address......................... 3-8 3.6.3 MOP Circuit ............................. 3-8 3.6.3.1 Finding the Circuit Name............... 3-8 3.6.3.2 Requirement for MOP Circuit............ 3-9 3.6.4 Phase IV Address......................... 3-9 3.6.5 Port Name................................ 3-9 3.6.5.1 Format of Port Name.................... 3-10 3.6.5.2 Load Client Names and Port Names....... 3-10 3.6.5.3 Phase IV Addresses and Port Names...... 3-11 3.6.6 Type of Loading.......................... 3-11 3.6.7 Specifying a Dump File................... 3-11 3.6.8 Use of DNS by the Configurators.......... 3-11 3.6.9 DNS Node Name (DECdns Users Only)........ 3-11 3.6.10 DNS Node Synonym (DECdns Users Only)..... 3-11 3.7 Delete a Router ............................. 3-11 3.7.1 Effect of Deleting....................... 3-12 3.8 Modify a Router ............................. 3-12 3.8.1 Information that Cannot Be Modified...... 3-12 3.8.2 Running the DECNIS Configurator After Modifying................................ 3-13 3.8.3 Modifying the Type of Loading............ 3-13 3.8.3.1 Results of Changing Back to Load Host Loading................................ 3-13 3.9 Restore a Router ............................ 3-13 3.9.1 Automatic Restore........................ 3-14 3.10 Update a Router ............................. 3-14 3.10.1 Automatic Update......................... 3-14 3.10.1.1 Update Command: Full Nonvolatile Memory Loading................................ 3-14 3.10.1.2 Update Command: Part Nonvolatile Memory Loading................................ 3-15 3.10.1.3 Update Command: Load Host Loading...... 3-15 3.11 Getting Help in the Load-Host Configurator... 3-15 3.12 Errors when Running the Load-Host Configurator................................. 3-15 3.13 The Load-Host Data File...................... 3-15 3.13.1 Saving the Load-Host Data File........... 3-16 3.14 What the Load-Host Configurator Does with Load Information............................. 3-16 v 4 Starting the DECNIS Configurator: OpenVMS Load Hosts 4.1 Introduction to the DECNIS Configurator...... 4-1 4.2 Before You Start............................. 4-1 4.3 How to Start................................. 4-1 4.4 Configurator Keys............................ 4-2 4.5 Online Help.................................. 4-3 4.5.1 How to Get Online Help................... 4-3 4.5.2 Help on Fields and Menu Choices.......... 4-3 4.5.3 Help on the Configurator................. 4-3 4.5.4 Keys to Get Help......................... 4-3 4.6 More Information About the DECNIS Configurator................................. 4-4 Part II ULTRIX and DEC OSF/1 Load Hosts: Installation and Configuration 5 Installing: ULTRIX and DEC OSF/1 Load Hosts 5.1 ULTRIX Background Information................ 5-1 5.2 DEC OSF/1 Background Information............. 5-2 5.3 ULTRIX and DEC OSF/1 Installation Procedure.................................... 5-3 5.4 ULTRIX and DEC OSF/1 Online Documentation.... 5-3 5.4.1 DECNIS Problem Solving Manual............ 5-4 5.5 After Installation........................... 5-4 5.5.1 Configuring a DECNIS for the First Time..................................... 5-4 5.5.2 Updating a Previously Installed DECNIS... 5-4 5.5.3 Verifying the Installation............... 5-5 5.5.3.1 ULTRIX Load Hosts...................... 5-5 5.5.3.2 DEC OSF/1 Load Hosts................... 5-5 5.5.4 Deleting Installed Files................. 5-6 5.5.4.1 ULTRIX Load Hosts...................... 5-6 5.5.4.2 DEC OSF/1 Load Hosts................... 5-6 5.5.5 Checking Your Terminal Setup............. 5-6 5.5.5.1 Type of Terminal....................... 5-6 5.5.5.2 Terminal Setup......................... 5-6 5.5.6 Reporting Problems....................... 5-7 vi 6 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6.1 What Is the Load-Host Configurator?.......... 6-1 6.1.1 Definition of a Load Host................ 6-1 6.1.2 Load Protocols........................... 6-1 6.2 Starting the Load-Host Configurator.......... 6-2 6.3 Load-Host Configurator Menu Options.......... 6-2 6.4 How to Enter Load Information................ 6-3 6.5 Load Information............................. 6-3 6.5.1 Load Client Name ........................ 6-3 6.5.1.1 Finding the Load Client Name........... 6-4 6.5.2 Hardware Address......................... 6-4 6.5.2.1 Finding the Hardware Address........... 6-4 6.5.3 MOP Circuit (MOP Loading Only)........... 6-4 6.5.3.1 Finding the MOP Circuit Name........... 6-4 6.5.3.2 Requirement for MOP Circuit............ 6-4 6.5.4 IP Address (BOOTP Loading Only).......... 6-4 6.5.5 Phase IV Address......................... 6-5 6.5.6 Type of Loading.......................... 6-5 6.5.6.1 Definition of Nonvolatile (Flash) Memory................................. 6-5 6.5.6.2 Advantages of Nonvolatile Memory Loading................................ 6-5 6.5.7 Specifying a Dump File................... 6-6 6.5.8 Use of DNS by the Configurators.......... 6-6 6.5.8.1 Background: the DECNIS and DECdns...... 6-6 6.5.8.2 Generating KNOWN TOWER Commands........ 6-7 6.5.9 DNS Node Name (DECdns Users Only)........ 6-7 6.5.10 DNS Node Synonym (DECdns Users Only)..... 6-7 6.6 Delete a Router ............................. 6-7 6.6.1 Effect of Deleting....................... 6-8 6.7 Modify a Router ............................. 6-8 6.7.1 Information that Cannot Be Modified...... 6-8 6.7.2 Running the DECNIS Configurator After Modifying................................ 6-9 6.7.3 Modifying the Type of Loading............ 6-9 6.7.3.1 Results of Changing Back to Load Host Loading................................ 6-9 6.8 Restore a Router............................. 6-9 6.8.1 Automatic Restore........................ 6-10 6.9 Update a Router ............................. 6-10 vii 6.9.1 Automatic Update......................... 6-10 6.9.1.1 Update: Full Nonvolatile Memory Loading................................ 6-10 6.9.1.2 Update: Part Nonvolatile Memory Loading................................ 6-11 6.9.1.3 Update: Load Host Loading.............. 6-11 6.10 Getting Help ................................ 6-11 6.11 Errors when Running the Load-Host Configurator................................. 6-11 6.12 The Load-Host Data File...................... 6-11 6.12.1 Saving the Load-Host Data File........... 6-12 6.13 What the Load-Host Configurator Does with Load Information............................. 6-12 7 Setting Up BOOTP on Load Hosts 7.1 Introduction................................. 7-1 7.2 Setting Up ULTRIX Systems for BOOTP Loading...................................... 7-1 7.2.1 Basic Steps.............................. 7-1 7.2.2 Starting TFTP in Restricted Mode......... 7-2 7.2.2.1 Example................................ 7-2 7.3 Setting Up DEC OSF/1 Systems for BOOTP Loading...................................... 7-3 7.3.1 Basic Steps.............................. 7-3 7.4 Setting Up Non-Digital UNIX[[R]] Systems as BOOTP Load Hosts............................. 7-4 8 Starting the DECNIS Configurator: ULTRIX and DEC OSF/1 Load Hosts 8.1 Introduction to the DECNIS Configurator...... 8-1 8.2 Before You Start............................. 8-1 8.3 How to Start................................. 8-1 8.4 Configurator Keys............................ 8-2 8.5 Online Help.................................. 8-3 8.5.1 How to Get Online Help................... 8-3 8.5.2 Help on Fields and Menu Choices.......... 8-3 8.5.3 Help on the Configurator................. 8-3 8.5.4 Keys to Get Help......................... 8-3 8.6 More Information About the DECNIS Configurator................................. 8-4 viii Part III Appendixes A Information Required for Load-Host Configuration A.1 Dump File Names.............................. A-5 B Files Installed on an OpenVMS Load Host B.1 Introduction................................. B-1 B.2 Required Files............................... B-1 B.2.1 SYS$HELP Directory....................... B-1 B.2.2 SYS$EXAMPLES Directory................... B-1 B.2.3 MOM$SYSTEM Directory..................... B-2 B.2.4 SYS$TEST Directory....................... B-2 B.2.5 SYS$MANAGER Directory.................... B-2 B.2.6 SYS$SYSTEM Directory..................... B-2 B.2.7 SYS$MESSAGE Directory.................... B-3 B.2.8 DECW$BOOK Directory...................... B-3 B.3 Optional Files............................... B-3 B.3.1 SYS$LIBRARY Directory.................... B-3 B.3.2 MCC_COMMON Directory..................... B-3 C Example Installation on an OpenVMS Load Host D Files Installed on ULTRIX Load Hosts D.1 Introduction................................. D-1 E Example Installation on an ULTRIX Load Host F Files Installed on DEC OSF/1 Load Hosts F.1 Introduction................................. F-1 G Example Installation on a DEC OSF/1 Load Host ix Index Tables 1-1 Steps to Set Up the DECNIS............... 1-1 2-1 Location of Online Information: OpenVMS.................................. 2-5 4-1 OpenVMS Configurator Keys................ 4-2 4-2 Keys Used to Get Help.................... 4-4 5-1 Location of Online Information: ULTRIX and DEC OSF/1............................ 5-3 8-1 ULTRIX and DEC OSF/1 Configurator Keys... 8-2 8-2 Keys Used to Get Help.................... 8-4 A-1 Load-Host Configuration Information: DECnet-VAX Extensions Load Hosts......... A-2 A-2 Load-Host Configuration Information: DECnet/OSI Load Hosts ................... A-3 x ________________________________________________________________ Preface This manual explains how to: o Install the software for the DEC[TM] Network Integration Server on OpenVMS[TM], ULTRIX[TM] and DEC OSF/1[[R]] load hosts. o Configure OpenVMS, ULTRIX and DEC OSF/1 so that they can downline load the DECNIS software. o Start the DECNIS configurator on OpenVMS, ULTRIX and DEC OSF/1 load hosts. The DEC Network Integration Server is referred to throughout this manual as the DECNIS. Audience This manual is intended for network managers. It assumes that you understand and have some experience of: o Local Area Networks (LANs) o Wide Area Networks (WANs) o OpenVMS (if using an OpenVMS load host) o ULTRIX (if using an ULTRIX load host) o DEC OSF/1 (if using a DEC OSF/1 load host) xi Associated Documentation Product Documentation o DEC Network Integration Server Introduction and Glossary o DEC Network Integration Server Configuration and Loading o DEC Network Integration Server Management o DEC Network Integration Server Problem Solving This is only available on line through the Bookreader[TM]. o DEC Network Integration Server Event Messages (supplied on line) o DEC Network Integration Server Release Notes (supplied on line) Hardware Documentation The following documents are supplied with the DECNIS hardware: o Installation and Service Manual o Configuration card The following documents are supplied with each Network Interface Card: o Cabling Instructions and Specifications card o Problem Solving card o Configuration card Related Documentation o Router Configuration and Management from PCs This manual describes how to install and configure the software for supported routers on an IBM[[R]]- compatible Personal Computer running MS-DOS[[R]]. Supported routers include the DECNIS. o Network management documentation for the load-host operating system you are using. o RFCs (for IP routing) xii RFCs are the working notes for the Internet research and development community. These notes are available in a three-volume set, the DDN Protocol Handbook, which can be ordered from the following address: Network Solutions, Inc. Attn: InterNIC Registration Service 505 Huntmar Park Drive Herndon, VA 22070, USA Tel. 1-800-444-4345 or 619-455-4600 Documentation Comments If you have comments or suggestions for this manual or any of the DECNIS documents and you have access to the Internet, please mail your comments electronically to the DECNIS writing group within Digital at the following address: doc_quality@lkg.mts.dec.com Alternatively, you can complete the postpaid Reader's Comments form at the end of this document. Thank you. Conventions The following conventions are used in this manual: Key names are shown enclosed to indicate that you press a key on the keyboard. This symbol indicates that you press the key at the same time as you press another key. For example, , , and so on. Italics This indicates variable information. decnis This indicates that you should substitute the node name of the DECNIS. If you are using DECdns, enter the name registered in DECdns. xiii Prompts The following prompts precede commands that you enter: For OpenVMS: $ For ULTRIX and DEC OSF/1: # For NCL: NCL> For NCP: NCP> xiv 1 ________________________________________________________________ Introduction This manual describes how to do the following on OpenVMS, ULTRIX and OSF/1 load hosts. o Install DECNIS software. o Run the load-host configurator to set up downline loading information. o Start the DECNIS configurator. You use this configura- tor to set up your DECNIS as a bridge/router. In addition to reading this manual, you will also need to refer to the manual DECNIS Configuration and Loading, which gives more detailed information on running the DECNIS configurator and on loading the DECNIS hardware unit. 1.1 Summary of Steps Required In order to set up your DECNIS hardware unit as a working system, carry out the steps shown in Table 1-1. Table_1-1_Steps_to_Set_Up_the_DECNIS______________________ Step_Action____________________Refer_to:__________________ 1 Install the DECNIS Chapter 2 and Chapter 5 software 2 Run the load-host Chapter 3 and Chapter 6 configurator and enter the required information (continued on next page) Introduction 1-1 Table_1-1_(Cont.)_Steps_to_Set_Up_the_DECNIS______________ Step_Action____________________Refer_to:__________________ 3 Run the DECNIS Chapter 4, Chapter 8 configurator and enter and the manual DECNIS the required information Configuration and Loading 4 Create the DECNIS DECNIS Configuration and configuration files Loading 5 Downline load the DECNIS Configuration and configured software Loading onto the DECNIS hardware _____unit_________________________________________________ 1-2 Introduction Part I ________________________________________________________________ OpenVMS Load Hosts: Installation and Configuration This part describes how to do the following on OpenVMS load hosts: o Install the DECNIS software. o Run the load-host configurator. o Start the DECNIS configurator. It contains the following chapters: o Chapter 2 describes how to install the DECNIS software on OpenVMS load hosts. o Chapter 3 describes how to use the load-host config- urator to configure OpenVMS load hosts for downline loading to the DECNIS. o Chapter 4 describes how to start the DECNIS configura- tor on OpenVMS load hosts. 2 ________________________________________________________________ Installing: OpenVMS Load Hosts This chapter describes how to install the DECNIS software on an OpenVMS load host. 2.1 OpenVMS Background Information The following table gives the background information needed before you install the DECNIS software on an OpenVMS load host. __________________________________________________________ Item_____________Value/Description________________________ Prerequisite OpenVMS V5.4 or later software DECnet[TM]-VAX[TM] Extensions or DECnet /OSI[[R]] for OpenVMS Prerequisite VAX with VT220[TM] or later terminal, or hardware VAXstation[TM] running DECwindows[TM] DECNIS hardware unit Kit description 1 TK50 or 1 mag tape Use of multiple Install the kit on at least 2 load hosts load hosts so that a backup host is available Required Account with SYSTEM privileges privileges Disk space DECnet-VAX Extensions: 70,000 blocks (+ requirements up to 64,000 blocks per dump); DECnet /OSI for OpenVMS: 55,000 blocks (+ up to 64,000 blocks per dump) Time required 30 minutes for installa- tion Installing: OpenVMS Load Hosts 2-1 __________________________________________________________ Item_____________Value/Description________________________ Stopping the Enter installation Backup Back up system before installing the procedures_______software_________________________________ 2.2 Parameter Values on DECnet-VAX Extensions Load Hosts On DECnet-VAX Extensions load hosts, you need to do the following: o Adjust the values of the parameters VIRTUALPAGECNT, PGFLQUO and BYTLM in order to receive dumps from the DECNIS. o Adjust the value of BYTLM in order to load the DECNIS. This does not apply to DECnet/OSI for VMS load hosts. 2.2.1 Setting VIRTUALPAGECNT (Virtual Page Count) You must adjust the value of the system parameter VIRTUALPAGECNT in order to accommodate the MOM process which performs dumps. If the MOM process does not have a high enough VIRTUALPAGECNT, a DECnet event is signalled, indicating that the MOM process has run out of virtual memory. 2.2.1.1 VIRTUALPAGECNT Values The VIRTUALPAGECNT values required are as follows: VIRTUALPAGECNT value for DECNIS 45,000 configuration VIRTUALPAGECNT value to receive 64,000 DECNIS dumps 2.2.1.2 How to Set VIRTUALPAGECNT Use the OpenVMS AUTOGEN utility to raise the value of VIRTUALPAGECNT. 2-2 Installing: OpenVMS Load Hosts 2.2.2 Setting PGFLQUO The page file quota (PGFLQUO) controls the number of pages allocated to NETACP (network ancillary control process). You must set the PGFLQUO value correctly. 2.2.2.1 PGFLQUO Values The PGFLQUO values required are as follows: PGFLQUO value for DECNIS configura- 45,000 tion PGFLQUO value to receive DECNIS 64,000 dumps 2.2.2.2 How to Set PGFLQUO PGFLQUO is derived from the system logical name NETACP$PAGE_ FILE. Define this logical name in the file SYS$MANAGER:SYLOGICALS.COM. 2.2.3 Setting BYTLM Quota The BYTLM quota adjusts the amount of resources allocated to the NETACP process. The NETACP requires a large BYTLM quota for the DECNIS to load from DECnet-VAX Extensions load hosts, and for dumps to be received. 2.2.3.1 Loading: Calculating the BYTLM Quota To calculate the BYTLM quota for loading, follow these steps: 1. Allow 3500 bytes to start up DECnet. 2. Add to this the following value: total_receive_buffers * total_device_buffer_size wheretotal_receive_buffers is the total value over all lines of the NCP Line characteristic Receive buffers total_device_buffer_size is the total value over all lines of the NCP Line characteristic Device buffer size 3. Finally, increase BYTLM by 7200 bytes for each circuit which has service enabled. Installing: OpenVMS Load Hosts 2-3 2.2.3.2 Finding Receive Buffers and Device Buffer Size To find the value of Receive buffers and Device buffer size for each line on the load host, follow these steps: 1. Run the Network Control Program (NCP). 2. Enter the NCP command: NCP> SHOW KNOWN LINE CHARACTERISTICS The Receive buffers and Device buffer size values for each line will be displayed. 3. To find total_receive_buffers, add together the Receive buffers values for all lines. 4. To find total_device_buffer_size, add together the Device buffer size values for all lines. 2.2.3.3 Finding the Service Enabled Circuits To find out how many circuits on the load host have service enabled, follow these steps: 1. Run NCP. 2. Enter the following NCP command: NCP> SHOW KNOWN CIRCUIT CHARACTERISTICS The screen will display whether service is enabled or disabled for each circuit. 2.2.3.4 Receiving Dumps: BYTLM Quota To receive dumps, the BYTLM quota must be at least 20,000. 2.2.3.5 How to Set the BYTLM Quota Value The BYTLM value is derived from the system logical name NETACP$BUFFER_LIMIT. Define this logical name in the file SYS$MANAGER:SYLOGICALS.COM. 2-4 Installing: OpenVMS Load Hosts 2.3 OpenVMS Installation Procedure To install the DECNIS software, do the following: __________________________________________________________ Step_Action_______________________________________________ 1 Issue the following command: $ @SYS$UPDATE:VMSINSTAL NIS023 device-name OPTIONS N where device-name is the device where the kit is mounted 2 Select the option you require from the Release Notes Menu 3____Read_the_Release_Notes_before_using_the_product______ 2.4 OpenVMS Online Documentation Table 2-1 lists the online information contained in the documentation kit. You can edit and print the text files if you wish. Table_2-1_Location_of_Online_Information:_OpenVMS_________ Item________________Location______________________________ X.25 Network SYS$HELP:FCNS$NI.TXT information Event messages SYS$HELP:NIS$EVENTS.TXT Release notes SYS$HELP:NIS023.Release_notes DECNIS Problem NIS$PROBLEM_SOLVING.DECW$BOOK in Solving manual SYS$COMMON:[DECW$BOOK] Bookshelf for NIS$PROBLEM_SOLVING.DECW$BOOKSHELF in DECNIS Problem SYS$COMMON:[DECW$BOOK] Solving_manual____________________________________________ 2.4.1 DECNIS Problem Solving Manual The DECNIS installation automatically does the following: o Installs the online DECNIS Problem Solving manual and its bookshelf, as shown in Table 2-1. Installing: OpenVMS Load Hosts 2-5 o Edits the file LIBRARY.DECW$BOOKSHELF to include the contents of NIS$PROBLEM_SOLVING.DECW$BOOKSHELF. LIBRARY.DECW$BOOKSHELF is in the DECW$BOOK directory on a standard OpenVMS system. 2.5 After Installation This section describes postinstallation tasks. 2.5.1 Configuring a DECNIS for the First Time If you are configuring a DECNIS for the first time, you need to carry out the following tasks: 1. Run the load-host configurator, as described in Chapter 3. 2. Run the DECNIS configurator, as described in Chapter 4 and the manual DECNIS Configuration and Loading. 2.5.2 Updating a Previously Installed DECNIS If you have previously set up DECNIS systems using the load-host configurator, you must update these systems so they can use the current version of DECNIS software. You need to do this even if you do not want to change your configuration. Procedure After you have installed a new version of the DECNIS software, follow these steps: 1. Run the automatic Update procedure, as described in Section 3.10. 2. Start the DECNIS configurator, as described in Chapter 4. 3. Select Modify an existing configuration from the Main Menu. 4. The screen shows a list of load client names. Select the DECNIS that you are updating. 5. The screen now shows the Sections Menu. Select NCL Script. You will go to the Create NCL Script section. 2-6 Installing: OpenVMS Load Hosts 6. Select Create an NCL Script. This will create a master NCL script file that is valid for the new version of the DECNIS software. 7. Create a new load file: either a CMIP file or an image /CMIP/profile file, depending on what is displayed on the menu. 8. Repeat steps 2 to 7 for each DECNIS that will use the new version of the software. 9. Reload your DECNISs, as described in the manual DECNIS Configuration and Loading. 2.5.3 Verifying the Installation To verify the installation, run the installation verification procedure. Enter: $ @SYS$TEST:NIS$IVP.COM 2.5.4 Deleting Installed Files To delete the files installed by the installation procedure, enter: $ @SYS$MANAGER:NIS$DEINSTALL.COM 2.5.5 Checking Your Terminal Setup In order to run the load-host configurator and the DECNIS configurator, you must use one of the types of terminal listed in Section 2.5.5.1, and set up the terminal as described in Section 2.5.5.2. 2.5.5.1 Type of Terminal You can run the configurators on the following types of terminal: o A VT220 (or later) terminal o A VAXstation terminal window Installing: OpenVMS Load Hosts 2-7 2.5.5.2 Terminal Setup You must set up your terminal as follows: o Set the tab stops on your terminal or terminal window to 8-column tabs. o Set the terminal parameter NEW LINE to NO NEW LINE. o Issue the terminal command, SET TERM/INQUIRE. 2.5.6 Reporting Problems For instructions on reporting problems to Digital, refer to the manual DECNIS Problem Solving. 2.6 VAXcluster Load Hosts To set up several nodes in a VAXcluster[TM] as load hosts, follow these steps: 1. Install the DECNIS software on a node in the VAXcluster, as described in Section 2.3. 2. Run the program NIS$PROVIDE_NCL.EXE on all of the other nodes in the VAXcluster. Enter the following command on each node: $ RUN SYS$SYSTEM:NIS$PROVIDE_NCL.EXE This program enables a system to use the latest version of the NCL command parsing tables which have been installed. The program is automatically run by the DECNIS installation procedure on the node on which you install the DECNIS software. However, you must run the program separately on the other nodes in a VAXcluster on which NCL is going to be used to manage the DECNIS. 3. Run the load-host configurator on one node within the VAXcluster, and enter loading information. 4. On the other VAXcluster nodes that will be used as load hosts, enter the command: $ @SYS$MANAGER:NIS$HOST_CONFIG RESTORE This creates loading information for the DECNIS on each of these nodes. 2-8 Installing: OpenVMS Load Hosts 5. Run the DECNIS configurator on one node within the VAXcluster and configure the DECNIS. 2.7 Installing on Multiple Load Hosts You should install the DECNIS software on at least two load hosts, so that a backup load host is available. Refer to DECNIS Configuration and Loading for instructions on copying files between load hosts. Installing: OpenVMS Load Hosts 2-9 3 ________________________________________________________________ Using the Load-Host Configurator: OpenVMS Load Hosts This chapter describes how to use the load-host configu- rator to configure the DECNIS to load from OpenVMS load hosts. 3.1 What Is the Load-Host Configurator? The load-host configurator is a menu-based program, supplied with the DECNIS software. You use the program to: o Enter information required for a load host to downline load DECNIS software and configuration files onto DECNIS hardware, and to receive upline dumps. o Delete, modify, list, update and restore load information. You must run the load-host configurator before you run the DECNIS configurator. 3.1.1 Definition of a Load Host A load host is a system which can downline load the configured DECNIS software to the DECNIS hardware in response to a load request. 3.1.2 Load Protocol Both DECnet/OSI for OpenVMS load hosts and DECnet-VAX Extensions load hosts use MOP (Maintenance Operations Protocol) for loading and dumping. MOP is a Digital-specific protocol used for loading and dumping. Using the Load-Host Configurator: OpenVMS Load Hosts 3-1 3.2 Starting the Load-Host Configurator To start the load-host configurator, follow these steps: 1. Log into any account which has OPER and SYSPRV privileges. 2. Enter the command: $ @SYS$MANAGER:NIS$HOST_CONFIG 3.3 Menu Options When you run the load-host configurator, it displays a menu with these options: o Add a router To enter DECNIS load information for the first time. o Delete a router To delete loading information for a DECNIS. o Modify a router To modify load information previously entered using the load-host configurator. o List a router To display a list of all DECNIS systems configured by the load-host configurator. o Restore a router To recreate loading and dumping information for a DECNIS. o Update a router To update load information to the latest version of DECNIS software. 3-2 Using the Load-Host Configurator: OpenVMS Load Hosts 3.4 How to Enter Load Information To enter load configuration information about a DECNIS for the first time, follow these steps: 1. Select Add a router from the Main Menu. 2. The screen will display: Select the type of router, or return to the Main Menu. Return to Main Menu DECNIS 600 DECNIS 500 Select the type of router to load to. 3. Enter load information on the screens. The information is described in the following sections: o Section 3.5 describes the information required when loading from a DECnet/OSI for OpenVMS load host. o Section 3.6 describes the information required when loading from a DECnet-VAX Extensions load host. 3.5 DECnet/OSI Load Hosts: Load Information This section describes the information you enter in the load-host configurator on DECnet/OSI load hosts. 3.5.1 Load Client Name The load client name identifies the DECNIS for downline loading and upline dumping. 3.5.1.1 Finding the Load Client Name You create the load client name yourself. The only restrictions are: o The name must be unique to this DECNIS. o The maximum length of the name is 32 characters. Using the Load-Host Configurator: OpenVMS Load Hosts 3-3 3.5.2 Hardware Address This is the hardware address of the DECNIS. The format is six pairs of hexadecimal digits, separated by hyphens, with a 0 (zero) as the final digit. For example: 08-00-2B-02-AA-20 3.5.2.1 Finding the Hardware Address The address is printed on the label on the Processor Card on your DECNIS system. Enter the address just as it is on the label, including the 0. 3.5.3 MOP Circuit This is a circuit defined specifically for downline loading. A MOP circuit is automatically created during DECnet/OSI installation. 3.5.3.1 Finding the MOP Circuit Name To find the MOP circuit name, follow these steps: 1. Enter the following NCL command: NCL> SHOW MOP CIRCUIT * ALL IDENTIFIER 2. Use the name, or one of the names, displayed. 3.5.3.2 Requirement for MOP Circuit The MOP circuit must exist before you enter it. The load-host configurator will check that it does exist. If it does not exist, the configurator will not let you continue. 3.5.4 Phase IV Address Enter a DECnet Phase IV address for the DECNIS if you want the DECNIS to communicate with DECnet Phase IV systems. Format The format of the Phase IV address is: area-number.node-number where:area-number is the number of the area where the DECNIS is located 3-4 Using the Load-Host Configurator: OpenVMS Load Hosts node-number is the node number of the DECNIS Example: 21.47 3.5.5 Type of Loading The load-host configurator asks how the DECNIS is to be loaded when it is rebooted: Nonvolatile memory for both CMIP and image Load host for CMIP; nonvolatile memory for image Load host for both CMIP and image 3.5.5.1 Definition of Nonvolatile (Flash) Memory The term nonvolatile memory refers to an area of DECNIS memory that is used to store its software image and (as an option) its CMIP and profile files. Nonvolatile memory is sometimes referred to as flash memory. 3.5.5.2 Advantages of Nonvolatile Memory Loading The main advantages of nonvolatile memory loading are: o It is quicker than loading from a load host. o Once the DECNIS is loaded, you do not need a load host on the network to reload it when it is rebooted. Refer to the manual DECNIS Configuration and Loading for more information. 3.5.6 Specifying a Dump File The load-host configurator asks if you want a dump file to be created on the load host. o If you select No, the load host will not be able to receive dumps from the DECNIS. o If you select Yes, the DECNIS will dump to the file: SYS$COMMON:[MOM$SYSTEM]NIS_load-client-name.DMP It is important to check that there is enough disk space on your load host to receive dumps. The table in Section 2.1 shows the amount of disk space required for dumps. Using the Load-Host Configurator: OpenVMS Load Hosts 3-5 3.5.7 Use of DNS by the Configurators The load-host configurator asks the question: You can choose whether or not the configurators use information in the DECdns namespace to set up addresses. Only select Yes if a DECdns name server is reachable from this load host, or you have a local namespace. Do you wish DECdns to be used? No Yes This section explains how you decide what to answer. 3.5.7.1 Background: the DECNIS and DECdns The DECNIS does not use DNS lookups to find the location of the DECnet systems to which it sends messages (for example, event sinks). Instead, it uses NCL commands in the master NCL script file generated by the DECNIS configurator. These NCL commands set up a complete specification of each DECnet system the DECNIS sends messages to. The commands are CREATE SESSION CONTROL KNOWN TOWER commands. 3.5.7.2 Generating KNOWN TOWER Commands The question on the screen is asking you to name the method the configurator should use to generate these commands. There are two alternative methods: o If you choose Yes, the DECNIS configurator uses DNS or local namespace lookups to generate the commands. In this case, you must supply a DNS name or node synonym for the DECNIS. The configurator then extracts addressing information from the namespace entry, and uses this information to generate the required commands. o If you choose No, the DECNIS configurator uses addressing information you supply. 3-6 Using the Load-Host Configurator: OpenVMS Load Hosts 3.5.8 DNS Node Name (DECdns Users Only) If you choose to use DECdns, you must enter the DECdns node name of the DECNIS system. The name you specify must conform to DECdns naming conventions. For details about the syntax of DNS names, refer to the DNS manual for your load host. 3.5.9 DNS Node Synonym (DECdns Users Only) This is an alternative DNS node name for the DECNIS. For convenience, you may use the Phase IV node name. The DNS node synonym is optional. Using the Load-Host Configurator: OpenVMS Load Hosts 3-7 3.6 DECnet-VAX Extensions Load Hosts: Loading Information This section describes the information you enter in the load-host configurator on DECnet-VAX Extensions load hosts. 3.6.1 Load Client Name The load client name identifies the DECNIS for downline loading and upline dumping. 3.6.1.1 Requirements for the Load Client Name The requirements for the load client name are: o The load client name must be the same as the Phase IV node name of the DECNIS. o The maximum length is six characters. o You must enter a load client name for each DECNIS port that will receive a downline load. 3.6.2 Hardware Address This is the same as for DECnet/OSI load hosts. See Section 3.5.2. 3.6.3 MOP Circuit This is the Ethernet routing circuit to be used for downline loading. Ethernet routing circuits are created during DECnet-VAX Extensions installation. 3.6.3.1 Finding the Circuit Name To find the routing (MOP) circuit name, follow these steps: 1. Enter the following NCP command: NCP> SHOW KNOWN CIRCUIT 2. Choose an Ethernet routing circuit. The load-host configurator will enable service on the circuit you enter, if it is not already enabled. 3-8 Using the Load-Host Configurator: OpenVMS Load Hosts 3.6.3.2 Requirement for MOP Circuit When you add or modify a DECNIS, and enter a MOP circuit name, the load-host configurator checks that the MOP circuit already exists. If it does not exist, the configurator will not let you continue. The configurator does the same check when you restore or update a DECNIS. However, in these cases, if the MOP circuit does not exist, the configurator also does the following: 1. Translates the environment variable NIS$MOP_CIRCUIT. If this variable is defined, it is used as the MOP circuit name. To define the variable, enter: $ DEFINE/SYSTEM NIS$MOP_CIRCUIT circuit-name 2. If NIS$MOP_CIRCUIT is not defined, the configurator searches for an Ethernet circuit. If it finds one, it uses it as the MOP circuit. Note that even if the specified MOP circuit does not exist, the MOP circuit entry in the load-host data file remains unchanged. This allows a DECNIS to be configured on one VAXcluster node, and then restored on a different VAXcluster node which has a different Ethernet device. 3.6.4 Phase IV Address You must enter a Phase IV address for each DECNIS port that will receive a downline load. See Section 3.6.5.3 for details. 3.6.5 Port Name Port name is the name of a DECNIS hardware port that will receive the downline loaded software. Note the following: o You can enter the names of several hardware ports. o Each port must be either a LANcontroller port or an FDDI port. Using the Load-Host Configurator: OpenVMS Load Hosts 3-9 3.6.5.1 Format of Port Name For the LANcontroller cards, the format for the port name is: card-slot-port For the F621 card, the format for the port name is: card-slot/slot o card is an acronym for a Network Interface Card. Valid acronyms are: _______________________________________________________ Acronym___Name_of_Network_Interface_Card_______________ L601 DEC LANcontroller 601 L602 DEC LANcontroller 602 F621______DECNIS_FDDIcontroller_621____________________ o slot is the number of the slot into which the Network Interface Card is inserted. Each slot has the slot number etched above it. The F621 card uses two slots. Enter the slots in the form slot/slot. For example, if the F621 card is in slots 4 and 5, enter the slot number as 4/5. o port is the hardware port number. On the L601 and L602 cards, hardware port numbering starts from the top of the card, with 0. Examples of port names are: L601-3-0 F621-5/6 3.6.5.2 Load Client Names and Port Names You must enter the names of one (or more ports) on the DECNIS that you want to receive the downline load. For each port name, you must enter a separate load client name. 3-10 Using the Load-Host Configurator: OpenVMS Load Hosts 3.6.5.3 Phase IV Addresses and Port Names Note the following: o On the first screen on which you enter a port name, enter the correct Phase IV address of the DECNIS. o If you choose to enter further port names, enter a Phase IV address for each port name. You can use any Phase IV address that is not assigned to another DECnet node. 3.6.6 Type of Loading This is the same as for DECnet/OSI load hosts, as described in Section 3.5.5. 3.6.7 Specifying a Dump File This is the same as for DECnet/OSI load hosts, as described in Section 3.5.6. 3.6.8 Use of DNS by the Configurators This is the same as for DECnet/OSI load hosts, as described in Section 3.5.7. 3.6.9 DNS Node Name (DECdns Users Only) This is the same as for DECnet/OSI load hosts, as described in Section 3.5.8. 3.6.10 DNS Node Synonym (DECdns Users Only) If you wish, enter the DECnet Phase IV node name of the DECNIS. It must be the same as the load client name associated with the first port name you entered. 3.7 Delete a Router When you select Delete a router, the screen displays a list of routers that were previously entered using the load-host configurator. You select the name of the router you wish to delete. Using the Load-Host Configurator: OpenVMS Load Hosts 3-11 3.7.1 Effect of Deleting If you delete a DECNIS, the load-host configurator renames the DECNIS configuration files, as follows: o The master NCL script file for the deleted DECNIS is renamed: SYS$COMMON:[MOM$SYSTEM]NIS_load-client-name.NCL_OLD o The CMIP file for the deleted DECNIS is renamed: SYS$COMMON:[MOM$SYSTEM]NIS_load-client-name.CMIP_OLD o The data file for the deleted DECNIS is renamed: SYS$COMMON:[MOM$SYSTEM]NIS_load-client-name.DAT_OLD where load-client-name is the load client name of the DECNIS. Example In the load-host configurator, you set up a DECNIS with the load client name EASTERN. You then configure EASTERN using the DECNIS configurator. A master NCL script file is created with the name: NIS_EASTERN.NCL If you delete EASTERN in the load-host configurator, the master NCL script will be renamed: NIS_EASTERN.NCL_OLD 3.8 Modify a Router When you select Modify a router, the screen displays a list of routers that were previously entered using the load-host configurator. Select the name of the DECNIS you wish to modify. 3.8.1 Information that Cannot Be Modified The only DECNIS load information you cannot modify is: o The load client name. 3-12 Using the Load-Host Configurator: OpenVMS Load Hosts o On DECnet-VAX Extensions load hosts, port information. If you want to change port information, you must delete the port and add it again, with the changed information. 3.8.2 Running the DECNIS Configurator After Modifying It is strongly recommended that you rerun the DECNIS configurator after using the Modify option. This is because changes to loading information may affect or even invalidate information entered in the DECNIS configurator. Refer to the manual DECNIS Configuration and Loading for details. 3.8.3 Modifying the Type of Loading If you change the type of loading-for example, from nonvolatile memory loading to load-host loading-you must do the following for your changes to take effect: 1. Run the DECNIS configurator. 2. Go to the Create NCL Script section, and create an NCL script file. 3. In the same section, create a new CMIP file or combined image/CMIP/profile file. 3.8.3.1 Results of Changing Back to Load Host Loading If you change from nonvolatile memory to load host loading, the combined image/CMIP/profile file is deleted on the load host. 3.9 Restore a Router The Restore option reissues the NCL or NCP commands which set up MOP loading information. Restore is useful if the permanent information is lost or deleted. You also use it when setting up VAXcluster nodes as load hosts, as described in Section 2.6. There are two ways of using the Restore option: o Restore a router option in the load-host configurator, to restore an individual DECNIS. Using the Load-Host Configurator: OpenVMS Load Hosts 3-13 o The automatic Restore procedure, to restore all the DECNIS systems set up by the load-host configurator. 3.9.1 Automatic Restore To use automatic Restore, enter the following: $ @SYS$MANAGER:NIS$HOST_CONFIG RESTORE 3.10 Update a Router When you install a new version of DECNIS software, you need to update existing DECNIS systems so that they can use the new version of the software. There are two kinds of update procedure: o Update a router option in the load-host configurator, to update an individual DECNIS. o The automatic Update procedure, to update all DECNIS systems. 3.10.1 Automatic Update To use automatic Update, enter the update command. When you start this procedure, you can also specify the type of loading for the updated DECNIS systems, as shown in Section 3.10.1.1 to Section 3.10.1.3. The default type of loading is full nonvolatile memory loading. Note that if you change the type of loading from the one previously specified, you must follow the instructions in Section 3.8.3. 3.10.1.1 Update Command: Full Nonvolatile Memory Loading To update all DECNIS systems and specify that the combined image and configuration file be loaded from nonvolatile memory, enter the following: $ @SYS$MANAGER:NIS$HOST_CONFIG UPDATE You can achieve the same result by entering: $ @SYS$MANAGER:NIS$HOST_CONFIG UPDATE FLASH_FULL 3-14 Using the Load-Host Configurator: OpenVMS Load Hosts 3.10.1.2 Update Command: Part Nonvolatile Memory Loading To update all DECNIS systems, and specify that CMIP and profile files be loaded from the load host and the software image from nonvolatile memory, enter the following: $ NIS$HOST_CONFIG UPDATE FLASH_PART 3.10.1.3 Update Command: Load Host Loading To update all DECNIS systems, and specify that the CMIP and profile files and the software image be loaded from the load host, enter the following. $ NIS$HOST_CONFIG UPDATE NETWORK 3.11 Getting Help in the Load-Host Configurator You can get online help at any time while running the configurator by pressing . Help in the load-host configurator works in a similar way to help in the DECNIS configurator. See Section 4.5 for details. 3.12 Errors when Running the Load-Host Configurator If there are any errors when you are running the load-host configurator, they will be recorded in the following log file: MOM$SYSTEM:NIS_DECNIS.LOG 3.13 The Load-Host Data File The load-host configurator saves all load-host configu- ration information in a private data file, known as the load-host data file. When you select a menu option, the load-host configurator uses the load-host data file to find the information that was previously entered. The name of the load-host data file is: SYS$COMMON:[MOM$SYSTEM]NIS_HOST_CONFIG.DAT Using the Load-Host Configurator: OpenVMS Load Hosts 3-15 3.13.1 Saving the Load-Host Data File Each time you run the load-host configurator and add, modify or delete information, the configurator creates a new load-host data file. It also saves the previous version of the load-host data file. The name of the previous version is the same as the name of the current one, except that it has the suffix .OLD instead of the suffix .DAT. 3.14 What the Load-Host Configurator Does with Load Information When you have finished entering information in the load- host configurator, it does the following: o Saves the information in the load-host data file, as described in Section 3.13. o Issues NCL or NCP commands to set up load details, and enters the commands in permanent configuration files. o If you have entered DNS information during load-host configuration, sets up DNS information for the DECNIS in the DNS namespace. 3-16 Using the Load-Host Configurator: OpenVMS Load Hosts 4 ________________________________________________________________ Starting the DECNIS Configurator: OpenVMS Load Hosts 4.1 Introduction to the DECNIS Configurator The DECNIS configurator is a utility supplied with the DECNIS. You use the DECNIS configurator to enter the information needed for the DECNIS to communicate with other systems. For example, you use it to enter information about addresses, protocols, and circuits. 4.2 Before You Start Before you start the DECNIS configurator, make sure that you do the following: 1. Check Section 2.5.5. This gives the terminal settings required to run both the load-host configurator and the DECNIS configurator. 2. Run the load-host configurator, and set up load information for the DECNIS you want to configure. 4.3 How to Start To start the DECNIS configurator, follow these steps: 1. Log into any account which has OPER and SYSPRV privileges. 2. Enter the command: $ @SYS$MANAGER:NIS$DECNIS_CONFIG Starting the DECNIS Configurator: OpenVMS Load Hosts 4-1 4.4 Configurator Keys Table 4-1 shows the keys you can use to enter and change information, and to move through the configurator sections. Table_4-1_OpenVMS_Configurator_Keys_______________________ Key______________Function_________________________________ Up Arrow Moves the cursor to the field above Down Arrow Moves the cursor to the field below Left Arrow Moves the cursor to the left in a field Right Arrow Moves the cursor to the right in a field or Enters the option you have chosen or Gives you help on a field or section Takes you out of Help and back to entering data Takes you out of the configurator without saving any data Takes you to the previous data entry screen in a section Takes you to the next data entry screen in a section or Toggle between insert and overstrike when typing data or Removes all text in a field Refreshes the screen Moves cursor to the previous column (on _________________screens_with_two_columns)________________ 4-2 Starting the DECNIS Configurator: OpenVMS Load Hosts 4.5 Online Help You can get online help when running the load-host configurator and your DECNIS configurator. This section describes how to get online help, how to leave online help, and the different types of online help you can get. 4.5.1 How to Get Online Help To get help in the load-host configurator or the DECNIS configurator, press . 4.5.2 Help on Fields and Menu Choices If you press when the cursor is on a field or menu, three lines of text appear near the bottom of the screen, telling you what sort of value to enter, or what the results are of making a menu choice. If you press again, another screen appears with more information. If there are several screens of information, you can page through them by pressing or . If you look in the upper righthand corner of a Help screen, it will say how many pages of Help text there are. For example, Page 1 of 2. To leave a Help information screen, press . 4.5.3 Help on the Configurator You can get help on the configurator (for example, the keys you can use) by pressing while you are on any other Help screen. 4.5.4 Keys to Get Help Table 4-2 lists the keys you can use to get Help, or to leave Help. Starting the DECNIS Configurator: OpenVMS Load Hosts 4-3 Table_4-2_Keys_Used_to_Get_Help___________________________ Pressing this key...______From_this_screen...____Gives_you_this...______ or Data entry screen 3-line Help or Data entry screen Full Parameter Help with 3-line Help displayed or Full screen of help Procedures Help menu Procedures Topic Return to Procedures Help menu Full screen of Help, Leave Help and return Procedures Help menu, to entering data ____________Procedures_Topic______________________________ 4.6 More Information About the DECNIS Configurator For more information about running the DECNIS configura- tor, see the manual DECNIS Configuration and Loading. 4-4 Starting the DECNIS Configurator: OpenVMS Load Hosts Part II ________________________________________________________________ ULTRIX and DEC OSF/1 Load Hosts: Installation and Configuration This part describes how to do the following on ULTRIX and DEC OSF/1 load hosts: o Install the DECNIS software. o Run the load-host configurator. o Start the DECNIS configurator. It contains the following chapters: o Chapter 5 describes how to install the DECNIS software on ULTRIX and DEC OSF/1 load hosts. o Chapter 6 describes how to configure ULTRIX and DEC OSF/1 load hosts for downline loading to the DECNIS. o Chapter 7 describes additional steps needed to set up ULTRIX and DEC OSF/1 load hosts for BOOTP loading. o Chapter 8 describes how to start the DECNIS configura- tor on ULTRIX and DEC OSF/1 load hosts. 5 ________________________________________________________________ Installing: ULTRIX and DEC OSF/1 Load Hosts This chapter describes how to install the DECNIS software on ULTRIX and DEC OSF/1 load hosts. 5.1 ULTRIX Background Information The following table gives the background information needed before you install the DECNIS software on ULTRIX load hosts. __________________________________________________________ Item________________Value/Description_____________________ Prerequisite ULTRIX and DEC OSF/1 V4.2 (or later). software For BOOTP loading, subset UDTINET 4.2 or later. DECnet/OSI for ULTRIX V5.1 (or later), with the following subsets: DNPBASE5nm (DECnet/OSI base components), DNPMOP5nm (DECnet/OSI MOP Utilities) and DNPNETMAN5nm (DECnet/OSI Network Management) where n is 1-9 and m is 0-9 Prerequisite RISC system with VT220 or later hardware terminal, or DECstation[TM] running DECwindows DECNIS hardware unit Kit description 1 TK50 or 1 mag tape Use of multiple Install the kit on at least 2 load load hosts hosts so that a backup host is available Installing: ULTRIX and DEC OSF/1 Load Hosts 5-1 __________________________________________________________ Item________________Value/Description_____________________ Required Superuser account privileges Disk space 14,000 Kbytes + 25,000 Kbytes per dump required Time required for 10 minutes installation Backup procedures Back up system before installing the ____________________software______________________________ 5.2 DEC OSF/1 Background Information The following table gives the background information needed before you install the DECNIS software on DEC OSF/1 load hosts. __________________________________________________________ Item________________Value/Description_____________________ Prerequisite DEC OSF/1 V1.3 (or later). For BOOTP software loading, subset OSFINET1n, where n is 2-9 DECnet/OSI for DEC OSF/1 AXP[TM] V1.1 (or later), with the following subsets: DNABASE1nm (DECnet/OSI base components), DNAMOP1nm (DECnet/OSI MOP Utilities) and DNANETMAN1nm (DECnet /OSI Network Management) where n is 0-9 and m is 0-9 Prerequisite Alpha AXP system hardware DECNIS hardware unit Kit description 1 TK50 or 1 mag tape Use of multiple Install the kit on at least 2 load load hosts hosts so that a backup host is available Required Superuser account privileges 5-2 Installing: ULTRIX and DEC OSF/1 Load Hosts __________________________________________________________ Item________________Value/Description_____________________ Disk space 14,000 Kbytes + 25,000 Kbytes per dump required Time required for 10 minutes installation Backup procedures Back up system before installing the ____________________software______________________________ 5.3 ULTRIX and DEC OSF/1 Installation Procedure To install the DECNIS software on ULTRIX and DEC OSF/1 load hosts, do the following: __________________________________________________________ Step______Action__________________________________________ 1 Issue the following commands: # cd / # setld -l /dev/device-name where device-name is the device where the kit is mounted 2_________Read_the_Release_Notes_before_using_the_product_ 5.4 ULTRIX and DEC OSF/1 Online Documentation Table 5-1 lists the online information contained in the documentation kit. You can edit and print the text files if you wish. Table 5-1 Location of Online Information: ULTRIX and DEC __________OSF/1___________________________________________ Item_______________________Location_______________________ X.25 Network information /usr/lib/dnet/fcns_ni.txt Event messages /usr/lib/dnet/nis_event.txt (continued on next page) Installing: ULTRIX and DEC OSF/1 Load Hosts 5-3 Table 5-1 (Cont.) Location of Online Information: ULTRIX __________________and_DEC_OSF/1___________________________ Item_______________________Location_______________________ Release Notes /usr/lib/dnet/nis023.release_ notes DECNIS Problem Solving /usr/lib/dxbook/decnispsg.decw_ manual book Bookshelf for DECNIS /usr/lib/dxbook/decnispsg.decw_ Problem_Solving____________bookshelf______________________ 5.4.1 DECNIS Problem Solving Manual The installation automatically installs the online DECNIS Problem Solving manual, as shown in Table 5-1. To access this manual using the Bookreader, you need to edit the file /usr/lib/dxbook/library.decw_bookshelf to include the contents of decnispsg.decw_bookshelf. 5.5 After Installation This section describes postinstallation tasks. 5.5.1 Configuring a DECNIS for the First Time If you are configuring a DECNIS for the first time, you need to carry out the following tasks: 1. Run the load-host configurator, as described in Chapter 6. 2. Run the DECNIS configurator, as described in Chapter 8 and the manual DECNIS Configuration and Loading. 5.5.2 Updating a Previously Installed DECNIS If you have previously set up DECNIS systems using the load-host configurator, you must update these systems so they can use the current version of DECNIS software. You need to do this even if you do not want to change your configuration. 5-4 Installing: ULTRIX and DEC OSF/1 Load Hosts Procedure After you have installed the new version of the software, follow these steps: 1. Run the automatic Update procedure, as described in Section 6.9. 2. Start the DECNIS configurator, as described in Chapter 8. 3. Select Modify an existing configuration from the Main Menu. 4. The screen shows a list of load client names. Select the DECNIS that you are updating. 5. The screen now shows the Sections Menu. Select NCL Script. You will go to the Create NCL Script section. 6. Select Create an NCL Script. This will create a master NCL script file that is valid for the new version of the DECNIS software. 7. Create a new load file: either a CMIP file or an image /CMIP/profile file, depending on what is displayed on the menu. 8. Repeat steps 2 to 7 for each DECNIS that will use the new version of the software. 9. Reload your DECNISs, as described in the manual DECNIS Configuration and Loading. 5.5.3 Verifying the Installation 5.5.3.1 ULTRIX Load Hosts To verify the installation, enter the following: # setld -v NIRNIS230 5.5.3.2 DEC OSF/1 Load Hosts To verify the installation, enter the following: # setld -v NIANIS230 Installing: ULTRIX and DEC OSF/1 Load Hosts 5-5 5.5.4 Deleting Installed Files 5.5.4.1 ULTRIX Load Hosts To delete the files installed by the installation procedure, enter: # setld -d NIRNIS230 5.5.4.2 DEC OSF/1 Load Hosts To delete the files installed by the installation procedure, enter: # setld -d NIANIS230 5.5.5 Checking Your Terminal Setup In order to run the load-host configurator and the DECNIS configurator, you must use one of the types of terminal listed in Section 5.5.5.1, and set up the terminal as described in Section 5.5.5.2. 5.5.5.1 Type of Terminal You can run the configurators on the following types of terminal: o A VT220 (or later) terminal o For ULTRIX load hosts, a terminal window on a DECstation o For DEC OSF/1 load hosts, a terminal window on an Alpha AXP workstation 5.5.5.2 Terminal Setup Set up your terminal as follows: o Set the tab stops on your terminal or terminal window to 8-column tabs. o If you are using a terminal window, set it up as follows: 1. On the terminal window menu bar, select Custom. 2. Select General. Set the Terminal ID to VT200[TM] or above, or to DECterm[TM] ID. 5-6 Installing: ULTRIX and DEC OSF/1 Load Hosts If you set Terminal ID to DECterm ID, then check that this is VT200 or above. 3. Set the Mode to VT300[TM] Mode 7-bit controls. 5.5.6 Reporting Problems For instructions on reporting problems to Digital, refer to the manual DECNIS Problem Solving. Installing: ULTRIX and DEC OSF/1 Load Hosts 5-7 6 ________________________________________________________________ Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts This chapter describes how to use the load-host configu- rator to configure the DECNIS to load from ULTRIX and DEC OSF/1 load hosts. 6.1 What Is the Load-Host Configurator? The load-host configurator is a menu-based program, supplied with the DECNIS software. You use the program to: o Enter information required for a load host to downline load DECNIS software and configuration files onto DECNIS hardware, and to receive upline dumps. o Delete, modify, list, update and restore load information. You must run the load-host configurator before you run the DECNIS configurator. 6.1.1 Definition of a Load Host A load host is a system which can load the configured DECNIS software to the DECNIS hardware in response to a load request. 6.1.2 Load Protocols ULTRIX and DEC OSF/1 load hosts can use MOP (Maintenance Operations Protocol), BOOTP/TFTP, or both for loading and dumping. o MOP is a Digital-specific protocol used for loading and dumping. Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6-1 o BOOTP/TFTP is a set of protocols used for loading and dumping, defined in RFCs 783 and 951. 6.2 Starting the Load-Host Configurator To start the load-host configurator, follow these steps: 1. Log in as a superuser. 2. Enter the command: # /usr/lib/dnet/nis_host_config 6.3 Load-Host Configurator Menu Options When you run the load-host configurator, it displays a menu with these options: o Add a router To set up DECNIS load information for the first time. o Delete a router To delete load information for a DECNIS. o Modify a router To modify load information previously set up using the load-host configurator. o List a router To display a list of all DECNIS systems configured by the load-host configurator. o Restore a router To recreate the loading and dumping information for a DECNIS, by reissuing NCL commands, by recreating the file etc/bootptab, or both. o Update a router To update load information to the latest version of DECNIS software. 6-2 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6.4 How to Enter Load Information To enter load configuration information about a DECNIS for the first time, follow these steps: 1. Select Add a router from the Main Menu. 2. If your load host can run BOOTP, the screen displays: Select the method to be used for downline loading: MOP BOOTP Both MOP and BOOTP Choose the method you want to use. Note the following: o ULTRIX load hosts can only use BOOTP if the optional subset UDTINET42 (or later) is installed. o DEC OSF/1 load hosts can only use BOOTP if the subset OSFINET12 or later is installed. If the appropriate subset is not installed, you go directly to step 3. 3. The screen displays: Select the type of DECNIS, or return to the Main Menu. Return to Main Menu DECNIS 600 DECNIS 500 Select the type of DECNIS to load to. 4. Enter load information. 6.5 Load Information This section describes the information you enter in the load-host configurator. 6.5.1 Load Client Name The load client name identifies the DECNIS for downline loading and upline dumping. Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6-3 6.5.1.1 Finding the Load Client Name You create the load client name yourself. The only restrictions are: o The name must be unique to this DECNIS. o The maximum length of the name is 32 characters. 6.5.2 Hardware Address This is the hardware address of the DECNIS. The format is six pairs of hexadecimal digits, separated by hyphens, with a 0 (zero) as the final digit. For example: 08-00-2B-02-AA-20 6.5.2.1 Finding the Hardware Address The address is printed on the label on the Processor Card on your DECNIS system. Enter the address just as it is on the label, including the 0. 6.5.3 MOP Circuit (MOP Loading Only) This is a circuit defined specifically for downline loading. A MOP circuit is automatically created during DECnet/OSI installation. 6.5.3.1 Finding the MOP Circuit Name To find the MOP circuit name, follow these steps: 1. Enter the following NCL command: NCL> SHOW MOP CIRCUIT * ALL IDENTIFIER 2. Use the name, or one of the names, displayed. 6.5.3.2 Requirement for MOP Circuit The MOP circuit must exist before you enter it. The load-host configurator will check that it does exist. If it does not exist, the configurator will not let you continue. 6.5.4 IP Address (BOOTP Loading Only) If you use BOOTP for loading, you must supply an IP address for the DECNIS. 6-4 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts Format The format of the IP address is four decimal integers, separated by decimal points. For example, 24.45.21.8. 6.5.5 Phase IV Address Enter a DECnet Phase IV address for the DECNIS if you want the DECNIS to communicate with DECnet Phase IV systems. Format The format of the Phase IV address is: area-number.node-number where:area-number is the number of the area where the DECNIS is located node-number is the node number of the DECNIS Example: 21.47 6.5.6 Type of Loading The load-host configurator asks how the DECNIS is to be loaded when it is rebooted: Nonvolatile memory for both CMIP and image Load host for CMIP; nonvolatile memory for image Load host for both CMIP and image 6.5.6.1 Definition of Nonvolatile (Flash) Memory The term nonvolatile memory refers to an area of DECNIS memory used to store its software image and (as an option) its CMIP and profile files. Nonvolatile memory is sometimes referred to as flash memory. 6.5.6.2 Advantages of Nonvolatile Memory Loading The main advantages of nonvolatile memory loading are: o It is quicker than loading from a load host. o Once the DECNIS is loaded, you do not need a load host on the network to reload it when it is rebooted. Refer to the manual DECNIS Configuration and Loading for more information. Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6-5 6.5.7 Specifying a Dump File The load-host configurator asks if you want a dump file to be created on the load host. o If you select No, the load host will not be able to receive dumps from the DECNIS. o If you select Yes, the DECNIS will dump to the file: /usr/lib/mop\nis_load-client-name.dmp It is important to check that there is enough disk space on your load host to receive dumps. The tables in Section 5.1 and Section 5.2 show the amount of disk space required for dumps. 6.5.8 Use of DNS by the Configurators The load-host configurator asks the question: You can choose whether or not the configurators use information in the DECdns namespace to set up addresses. Only select Yes if a DECdns name server is reachable from this load host, or you have a local namespace. Do you wish DECdns to be used? No Yes This section explains how you decide what to answer. 6.5.8.1 Background: the DECNIS and DECdns The DECNIS does not use DNS lookups to find the location of the DECnet systems to which it sends messages (for example, event sinks). Instead, it uses NCL commands in the master NCL script file generated by the DECNIS configurator. These NCL commands set up a complete specification of each DECnet system the DECNIS sends messages to. The commands are CREATE SESSION CONTROL KNOWN TOWER commands. 6-6 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6.5.8.2 Generating KNOWN TOWER Commands The question on the screen is asking you to name the method the configurator should use to generate these commands. There are two alternative methods: o If you choose Yes, the DECNIS configurator uses DNS or local namespace lookups to generate the commands. In this case, you must supply a DNS name or node synonym for the DECNIS. The configurator then extracts addressing information from the namespace entry, and uses this information to generate the required commands. o If you choose No, the DECNIS configurator uses addressing information you supply. 6.5.9 DNS Node Name (DECdns Users Only) If you choose to use DECdns, you must enter the DECdns node name of the DECNIS system. The name you specify must conform to DECdns naming conventions. For details about the syntax of DNS names, refer to the DNS manual for your load host. 6.5.10 DNS Node Synonym (DECdns Users Only) This is an alternative DNS node name for the DECNIS. For convenience, you may use the Phase IV node name. The DNS node synonym is optional. 6.6 Delete a Router When you select Delete a router, the screen displays a list of DECNIS systems that were previously entered using the load-host configurator. You select the name of the DECNIS you wish to delete. Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6-7 6.6.1 Effect of Deleting If you delete a DECNIS, the load-host configurator renames the DECNIS configuration files, as follows: o The master NCL script file for the deleted DECNIS is renamed: /usr/lib/dnet/nis_load-client-name.ncl_old o The CMIP file for the deleted DECNIS is renamed: /usr/lib/mop/nis_load-client-name.cmip_old o The data file for the deleted DECNIS is renamed: /usr/lib/dnet/nis_load-client-name.dat_old where load-client-name is the load client name of the DECNIS. Example In the load-host configurator, you set up a DECNIS with the load client name EASTERN. You then configure EASTERN using the DECNIS configurator. A master NCL script file is created with the name: NIS_EASTERN.NCL If you delete EASTERN in the load-host configurator, the master NCL script will be renamed: NIS_EASTERN.NCL_OLD 6.7 Modify a Router When you select Modify a router, the screen displays a list of DECNIS systems that were previously entered using the load-host configurator. Select the name of the DECNIS you wish to modify. 6.7.1 Information that Cannot Be Modified The only DECNIS load information you cannot modify is the load client name. 6-8 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6.7.2 Running the DECNIS Configurator After Modifying You must rerun the DECNIS configurator after using the load-host configurator Modify option. This is because changes to loading information may affect or even invalidate information entered in the DECNIS configurator. Refer to the manual DECNIS Configuration and Loading for details. 6.7.3 Modifying the Type of Loading If you change the type of loading-for example, from nonvolatile memory loading to load-host loading-you must do the following for your changes to take effect: 1. Run the DECNIS configurator. 2. Go to the Create NCL Script section, and create an NCL script file. 3. In the same section, create a new CMIP file or image /CMIP/profile file. 6.7.3.1 Results of Changing Back to Load Host Loading If you change from nonvolatile memory to load host loading, the combined image/CMIP/profile file is deleted on the load host. 6.8 Restore a Router The Restore option does the following: o For MOP loading, reissues the NCL or NCP commands which set up MOP loading information. o For BOOTP loading, reenters information in the file etc/bootptab. Restore is useful if the permanent information is lost or deleted. There are two ways of using the Restore option: o Restore a router option in the load-host configurator, to restore an individual DECNIS. o The automatic Restore procedure, to restore all the DECNIS systems recorded by the load-host configurator. Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6-9 6.8.1 Automatic Restore To use automatic Restore, enter the following: # /usr/lib/dnet/nis_host_config -r 6.9 Update a Router When you install a new version of DECNIS software, you need to update existing DECNIS systems so that they can use the new version of the software. There are two kinds of update procedure: o Update a router option in the load-host configurator, to update an individual DECNIS. o The automatic Update procedure, to update all DECNIS systems. 6.9.1 Automatic Update To use automatic Update, run the automatic Update procedure. When you start this procedure, you can also specify the type of loading for the updated systems, as shown in Section 6.9.1.1 to Section 6.9.1.3. The default type of loading is full nonvolatile memory loading. Note: If you change the type of loading from that previously specified for a DECNIS, you must then follow the instructions in Section 6.7.3. 6.9.1.1 Update: Full Nonvolatile Memory Loading To update all DECNIS systems and specify that the combined image and configuration file be loaded from nonvolatile memory, enter the following: # /usr/lib/dnet/nis_host_config -u You can achieve the same result by entering: # /usr/lib/dnet/nis_host_config -u flash_full 6-10 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6.9.1.2 Update: Part Nonvolatile Memory Loading To update all DECNIS systems, and specify that CMIP and profile files be loaded from the load host and the software image from nonvolatile memory, enter the following: # /usr/lib/dnet/nis_host_config -u flash_part 6.9.1.3 Update: Load Host Loading To update all DECNIS systems, and specify that the CMIP and profile files and the software image be loaded from the load host, enter the following: # /usr/lib/dnet/nis_host_config -u network 6.10 Getting Help You can get online help at any time while running the configurator by pressing . Help in the load-host configurator works in a similar way to help in the DECNIS configurator. See Section 8.5 for details. 6.11 Errors when Running the Load-Host Configurator If there are any errors when you are running the load-host configurator, they will be recorded in the log file: /usr/lib/dnet/nis_decnis.log 6.12 The Load-Host Data File The load-host configurator saves all load-host configu- ration information in a private data file, known as the load-host data file. When you select a menu option, the load-host configurator uses the load-host data file to find the information that was previously entered. The name of the load-host data file is: /usr/lib/dnet/nis_host_config.dat Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 6-11 6.12.1 Saving the Load-Host Data File Each time you run the load-host configurator and add, modify or delete information, the configurator creates a new load-host data file. It also saves the previous version of the load-host data file. The name of the previous version is the same as the name of the current one, except that it has the suffix .old instead of the suffix .dat. 6.13 What the Load-Host Configurator Does with Load Information When you have finished entering information in the load- host configurator, it does the following: o Saves the information in the load-host data file, as described in Section 6.12. o For MOP loading, issues NCL commands to set up load details, and enters the commands in permanent configuration files. o For BOOTP loading, writes load details into the file /etc/bootptab. o If you have entered DNS information during load-host configuration, sets up DNS information for the DECNIS in the DNS namespace. 6-12 Using the Load-Host Configurator: ULTRIX and DEC OSF/1 Load Hosts 7 ________________________________________________________________ Setting Up BOOTP on Load Hosts 7.1 Introduction This chapter describes how to set up ULTRIX and DEC OSF/1 load hosts for BOOTP loading. 7.2 Setting Up ULTRIX Systems for BOOTP Loading To set up ULTRIX systems for BOOTP loading, check the steps in Section 7.2.1. 7.2.1 Basic Steps 1. When you run the load-host configurator, select either BOOTP or MOP and BOOTP. 2. If your load host is not already configured as a BOOTP server, ensure that the BOOTP and TFTP daemons are started on system startup. To do this, follow these steps: a. Edit the file /etc/services to include the following lines: bootp 67/udp tftp 69/udp b. Edit the file /etc/inetd.conf to include the following lines: bootp dgram udp wait /usr/etc/bootpd bootpd -i tftp dgram udp wait /usr/etc/tftpd tftpd 3. If you wish, set up TFTP to start in restricted mode, as described in Section 7.2.2. Setting Up BOOTP on Load Hosts 7-1 7.2.2 Starting TFTP in Restricted Mode You may wish to start the TFTP daemon on the load host using restricted mode (also known as the -r directory option). This is a security feature. It ensures that only the directory tree starting with directory is searched for the load files. To use this feature, follow the steps below. 1. On the load host, create the following directory: /directory/load-directory where:directory is at the top of the directory tree to be searched load-directory is the directory in which the load files are stored, as specified by /etc/bootptab 2. Copy the load files to load-directory. The load files can be either of the following: o The software image, CMIP file and profile files o The combined image/CMIP/profile file 3. Start TFTP by entering -r directory. 7.2.2.1 Example In this example: tftp is directory (the directory at the top of the directory tree) /usr/local is load-directory (the directory in which the /bootfiles load files are stored) nis_north1 is the load client name of the DECNIS You have specified that the DECNIS load all files from the load host. Follow these steps: 1. Create a directory called /tftp/usr/local/bootfiles. 2. In the file /etc/bootptab, specify that the load files are in /usr/local/bootfiles. 7-2 Setting Up BOOTP on Load Hosts 3. Copy the software image and load files to /usr/local /bootfiles, as follows: # cp /usr/lib/mop/nis022.sys\ /tftp/usr/local/bootfiles/system.nis_north1 # cp /usr/lib/mop/nis_load-client-name.cmip\ /tftp/usr/local/bootfiles/script.nis_north1 # cp /usr/lib/mop/digital/fcns/mcnm_prf\ /tftp/usr/local/bootfiles/mcnm_prf # cp /usr/lib/mop/digital/fcns/x25l2_prf\ /tftp/usr/local/bootfiles/x25l2_prf # cp /usr/lib/mop/digital/fcns/x25l3_prf\ /tftp/usr/local/bootfiles/x25l3_prf 4. Start TFTP by entering -r tftp 7.3 Setting Up DEC OSF/1 Systems for BOOTP Loading To set up DEC OSF/1 systems for BOOTP loading, check the steps in Section 7.3.1. 7.3.1 Basic Steps 1. When you run the load-host configurator, select either BOOTP or MOP and BOOTP. 2. If your load host is not already configured as a BOOTP server, ensure that the BOOTP and TFTP daemons are started on system startup. To do this, follow these steps: a. Edit the file /etc/services to include the following lines: bootps 67/udp tftp 69/udp b. Edit the file /etc/inetd.conf to include the following lines: bootps dgram udp wait root /usr/sbin/bootpd -s tftp dgram udp wait root /usr/sbin/tftpd tftpd Setting Up BOOTP on Load Hosts 7-3 7.4 Setting Up Non-Digital UNIX[[R]] Systems as BOOTP Load Hosts To set up a non-Digital UNIX system as a BOOTP load host, follow these steps: 1. Run the load-host configurator on a DECnet/OSI for ULTRIX system, as described in Chapter 6. For each DECNIS to be loaded, select the BOOTP option. 2. Run the DECNIS configurator to generate NCL script files for each DECNIS. 3. Generate either a combined image/CMIP/profile file or a CMIP file for each DECNIS. Refer to DECNIS Configuration and Loading for details. 4. Copy either the combined image/CMIP/profile file, or the software image and the CMIP and profile files, to the UNIX load host. 5. If the UNIX load host is not already configured as a BOOTP server, ensure that the BOOTP and TFTP daemons are started on system startup. Refer to the load-host operating system documentation for details of how to do this. 7-4 Setting Up BOOTP on Load Hosts 8 ________________________________________________________________ Starting the DECNIS Configurator: ULTRIX and DEC OSF/1 Load Hosts 8.1 Introduction to the DECNIS Configurator The DECNIS configurator is a utility supplied with the DECNIS. You use the DECNIS configurator to enter the information needed for the DECNIS to communicate with other systems. For example, you use it to enter information about addresses, protocols, and circuits. 8.2 Before You Start Before you start the DECNIS configurator, make sure that you do the following: 1. Check Section 5.5.5. This gives the terminal settings required to run both the load-host configurator and the DECNIS configurator. 2. Run the load-host configurator, and set up load information for the DECNIS you want to configure. 8.3 How to Start To start the DECNIS configurator, follow these steps: 1. Log in as a superuser. 2. Enter the command: # /usr/lib/dnet/nis_decnis_config Starting the DECNIS Configurator: ULTRIX and DEC OSF/1 Load Hosts 8-1 8.4 Configurator Keys Table 8-1 shows the keys you can use to enter and change information, and to move through the configurator sections. Table_8-1_ULTRIX_and_DEC_OSF/1_Configurator_Keys__________ Key______________Function_________________________________ Up Arrow Moves the cursor to the field above Down Arrow Moves the cursor to the field below Left Arrow Moves the cursor to the left in a field Right Arrow Moves the cursor to the right in a field or Enters the option you have chosen or Gives you help on a field or section Takes you out of Help and back to entering data Takes you out of the configurator without saving any data Takes you to the previous data entry screen in a section Takes you to the next data entry screen in a section or Toggle between insert and overstrike when typing data or Removes all text in a field Refreshes the screen Moves cursor to the previous column (on _________________screens_with_two_columns)________________ 8-2 Starting the DECNIS Configurator: ULTRIX and DEC OSF/1 Load Hosts 8.5 Online Help You can get online help when running the load-host configurator and your DECNIS configurator. This section describes how to get online help, how to leave online help, and the different types of online help you can get. 8.5.1 How to Get Online Help To get help in the load-host configurator or the DECNIS configurator, press . 8.5.2 Help on Fields and Menu Choices If you press when the cursor is on a field or menu, three lines of text appear near the bottom of the screen, telling you what sort of value to enter, or what the results are of making a menu choice. If you press again, another screen appears with more information. If there are several screens of information, you can page through them by pressing or . If you look in the upper righthand corner of a Help screen, it will say how many pages of Help text there are. For example, Page 1 of 2. To leave a Help information screen, press . 8.5.3 Help on the Configurator You can get help on the configurator (for example, the keys you can use) by pressing while you are on any other Help screen. 8.5.4 Keys to Get Help Table 8-2 lists the keys you can use to get Help, or to leave Help. Starting the DECNIS Configurator: ULTRIX and DEC OSF/1 Load Hosts 8-3 Table_8-2_Keys_Used_to_Get_Help___________________________ Pressing this key...______From_this_screen...____Gives_you_this...______ or Data entry screen 3-line Help or Data entry screen Full Parameter Help with 3-line Help displayed or Full screen of help Procedures Help menu Procedures Topic Return to Procedures Help menu Full screen of Help, Leave Help and return Procedures Help menu, to entering data ____________Procedures_Topic______________________________ 8.6 More Information About the DECNIS Configurator For more information about running the DECNIS configura- tor, see the manual DECNIS Configuration and Loading. 8-4 Starting the DECNIS Configurator: ULTRIX and DEC OSF/1 Load Hosts Part III ________________________________________________________________ Appendixes This part contains the following appendixes: o Appendix A summarizes the information required for load-host configuration on the following types of load host: - DECnet/OSI for OpenVMS - DECnet-VAX Extensions - DECnet/OSI for ULTRIX - DEC OSF/1 o Appendix B lists the files installed on OpenVMS load hosts. o Appendix C is an example log of an installation on an OpenVMS load host. o Appendix D lists the files installed on ULTRIX load hosts. o Appendix E is an example log of an installation on an ULTRIX load host. o Appendix F lists the files installed on DEC OSF/1 load hosts. o Appendix G is an example log of an installation on a DEC OSF/1 load host. A ________________________________________________________________ Information Required for Load-Host Configuration Table A-1 and Table A-2 list the information needed when running the load-host configurator. Write down your values in the last column, headed Your Value. See Chapter 3 and Chapter 6 for explanatory notes on load- host configuration. Default Values The column labelled Default in the tables shows the default value supplied by the configurators for each item of information. If the Default column shows -, this means that the configurator does not provide a default. If the value is required, you need to provide it yourself. The column labelled Required/Optional shows whether the value is required or optional. Information Required for Load-Host Configuration A-1 Table A-1 Load-Host Configuration Information: DECnet-VAX __________Extensions_Load_Hosts_________________________________ R(equired) Information / Your Required______Notes______________________O(ptional)Default_____Value Type of Select from list R - DECNIS Load client DECnet Phase IV node R - name name of the DECNIS. Max. 6 characters Hardware LAN address of the R - address DECNIS, as printed on the label on the Processor Card. Example: 08-00-2B-02-AA-20 MOP Circuit Routing circuit used R - name to load the DECNIS. Examples: SVA-0, QNA-0 DECnet Area number.node number R - Phase IV Example: 2.43 address of DECNIS Port name DECNIS hardware port to R - receive loads. Examples: L601-3-0, F621-4/5 Type of Select one: load host R Nonvolatile loading for CMIP, nonvolatile memory memory for image; for both nonvolatile memory for CMIP and both CMIP and image; image load host for both CMIP and image Create a Select Yes or No R - dump file? Should con- Select Yes or No R No figurator use DNS? DNS node Full DNS node name of R if - name DECNIS DNS chosen DNS node DECnet Phase IV node O - A-2oInformationaRequiredeforCLoad-Host Configuration 6 characters. Use the same name as entered for ______________the_load_client_name._____________________________ Table A-2 Load-Host Configuration Information: DECnet/OSI Load __________Hosts_________________________________________________ R(equired) Information / Your Required________Notes_____________________O(ptional)Default_____Value Type of Select from list R - DECNIS Load protocol Select one: MOP; BOOTP; R - (if both MOP Both and BOOTP supported) Load client Create a name to R - name identify the DECNIS for loading. Max. 32 characters Hardware LAN address of the R - address DECNIS, as printed on the label on the Processor Card. Example: 08-00-2B-02- AA-20 MOP Circuit Name of the MOP R - name (MOP circuit used to load loading only) the DECNIS. Max. 32 characters IP address IP address for the R - (BOOTP DECNIS loading only) DECnet Phase Area number.node number O (but - IV address of Example: 2.43 R to DECNIS commu- nicate with Phase IV sys- tems) (continued on next page) Information Required for Load-Host Configuration A-3 Table A-2 (Cont.) Load-Host Configuration Information: DECnet __________________/OSI_Load_Hosts_______________________________ R(equired) Information / Your Required________Notes_____________________O(ptional)Default_____Value Type of Select one: nonvolatile R Nonvolatile loading memory for both CMIP memory and image; load host for both for CMIP, nonvolatile CMIP and memory for image; load image host for both CMIP and image Create a dump Select Yes or No R - file? Should Select Yes or No R Yes configurator use DNS? DNS node name Full DNS node name of R if - DECNIS DNS chosen DNS node An alternative name O - synonym by which the DECNIS will be known to DNS on the network. Max. 6 ________________characters______________________________________ A-4 Information Required for Load-Host Configuration A.1 Dump File Names The dump file names are: o For OpenVMS systems: SYS$COMMON:[MOM$SYSTEM]NIS_load-client-name.DMP o For ULTRIX and DEC OSF/1 systems: /usr/lib/mop\nis_load-client-name.dmp Information Required for Load-Host Configuration A-5 B ________________________________________________________________ Files Installed on an OpenVMS Load Host B.1 Introduction This appendix lists the files installed on an OpenVMS load host by the DECNIS installation procedure. B.2 Required Files This section lists the files that are always installed in the DECNIS installation procedure. B.2.1 SYS$HELP Directory o NCLHELP.HLP-NCL help o W3_NCL_HELP.HLP-NCL help for DECnet/OSI for OpenVMS systems o NIS023.RELEASE_NOTES-Release Notes o NIS$HOST_HELP.BIN-Load-host configurator help o NIS$DECNIS_CONFIG_HELP.BIN-DECNIS configurator help o NIS$EVENTS.TXT-Event messages o FCNS$NI.TXT-Documentation for X.25 network profiles B.2.2 SYS$EXAMPLES Directory o NIS$NCL_EXAMPLE.NCL-NCL examples o NIS$OSPF_EXAMPLE1.NCL-OSPF NCL examples o NIS$OSPF_EXAMPLE2.NCL-OSPF NCL examples o NIS$OSPF_EXAMPLE3.NCL -OSPF NCL examples o DEC_ELAN_MIB.V27_TXT-DEC specific MIB Files Installed on an OpenVMS Load Host B-1 B.2.3 MOM$SYSTEM Directory o NIS023.SYS-System image o NIS$TEST_SCRIPT.NCL-Test script o NIS$IMAGES.DAT -List of supported NIS images o FCNS$MCNM_PRF.DAT-Modem connect profile file o FCNS$X25L2_PRF.DAT-X.25 level 2 profile file o FCNS$X25L3_PRF.DAT-X.25 level 3 profile file B.2.4 SYS$TEST Directory o NIS$IVP.COM-Installation verification procedure B.2.5 SYS$MANAGER Directory o NIS$CMIP_FILE.FDL-Exchange file o NIS$DECNIS_CONFIG.COM-DECNIS configurator procedure o NIS$DEINSTALL.COM-Delete installation file o NIS$HOST_CONFIG.COM-Load-host configuration procedure o NIS$SCRIPT_COMPILE.COM-CMIP file creation procedure o NIS$IMAGE_COMPRESS.COM-Flash file creation procedure B.2.6 SYS$SYSTEM Directory o NIS$PROVIDE_NCL.EXE-Updates the NCL parse tables available to the NCL utility o NIS$SCRIPT_COMPILER.EXE-CMIP file creation program o NIS$HOST_CONFIG.EXE-Load-host configurator o NIS$DECNIS_CONFIG.EXE-DECNIS configurator program o NIS$FLASH.EXE-Flash compression utility o NIS$BRIDGE_MGMT.EXE-Bridge management utility B-2 Files Installed on an OpenVMS Load Host B.2.7 SYS$MESSAGE Directory o NIS$HOST_CONFIG.BIN-Load-host configurator messages o NIS$DECNIS_CONFIG.BIN-DECNIS configurator messages o NIS$DECNIS_NCL_TEMPLATE.BIN-NCL command messages B.2.8 DECW$BOOK Directory o NIS$PROBLEM_SOLVING.DECW$BOOK-Problem solving manual o NIS$PROBLEM_SOLVING.DECW$BOOKSHELF-Problem solving bookshelf B.3 Optional Files The files listed in the following sections will be optionally installed, based on the installation state of NCL. B.3.1 SYS$LIBRARY Directory o CTF$*.*-To enable tracing using the Common Trace Facility o NCLPRS.BIN-Parsing information for the bridge management utility o NCL_PROTOID.MAP-Protocol identifiers for the bridge management utility o NCL_DICTIONARY.DAT-Parse tables for the bridge management utility o NIS$GLOBALSECTION_WAVE1.DAT-NCL global section for DECnet-VAX Extensions load hosts. o NCL$GLOBALSECTION_WAVE2.DAT-NCL global section for DECnet/OSI for OpenVMS load hosts B.3.2 MCC_COMMON Directory o MCC_DECNIS_APPL.DAT-Customization file for DECmcc[TM] application menu V1.2 of DECmcc o MCC_APPL_DECNIS.DEF-Customization file for DECmcc application menu V1.3 of DECmcc Files Installed on an OpenVMS Load Host B-3 C ________________________________________________________________ Example Installation on an OpenVMS Load Host This appendix contains an example installation of DECNIS software on an OpenVMS load host. Throughout this appendix, text you type in is indicated by a bold typeface. $ sys$update:vmsinstal VAX/VMS Software Product Installation Procedure V5.5-2 It is 26-JAN-1994 at 10:37. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: decnis$v23_export: Enter the products to be processed from the first distribution volume set. * Products: nis023 * Enter installation options you wish to use (none): The following products will be processed: NIS V2.3 Beginning installation of NIS V2.3 at 10:38 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. DEC Network Integration Server T2.3 Installation Procedure. ) Digital Equipment Corporation, 1993. All rights reserved. You should read the Release Notes immediately AFTER installing this product. The release notes for the DECNIS are in a file called NIS023.RELEASE_NOTES which is in the SYS$HELP directory. * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? Example Installation on an OpenVMS Load Host C-1 The IVP will be placed in the directory SYS$TEST. You can run the IVP with the DCL command @SYS$TEST:NIS$IVP. No further questions will be asked until the IVP. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %NIS-I-PROVIDING, PROVIDING TAILORING - Providing DECNIS deinstallation routines %NIS-I-PROVIDING, PROVIDING IMAGE - Providing DECNIS Image and Configuration programs %NIS-I-PROVIDING, INSERTING HELP - Inserting DECNIS help into NCL help library %NIS-I-PROVIDING, PROVIDING NCL - Providing NCL support for DECNIS NCL$GLOBALSECTION.DAT will be renamed to DSA10:[SYS4.syscommon.][SYSLIB]N CL$GLOBALSECTION.OLD NIS$GLOBALSECTION.DAT will be renamed to DSA10:[SYS4.syscommon.][SYSLIB]N IS$GLOBALSECTION.OLD %NIS-I-PROVIDING, CTF SUPPORT - Providing CTF support for DECNIS %NIS-I-PROVIDING, PROVIDING FLASH - Providing Flash support for DECNIS %NIS-I-PROVIDING, BRIDGE MANAGEMENT - Providing Bridge Entity management utility %NIS-I-PROVIDING, MCC CUSTOMIZING - Providing customization file for DECmcc Applications menu %NIS-I-MCC_CUSTOMIZING, Providing customization file for DECmcc Applications menu %NIS-I-PROVIDING, DOCUMENTATION - Providing DECNIS documentation %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %NIS-I-MCC_CUSTOMIZING, Adding DECNIS Configurators to MCC Applications menu Application <===== DECNIS Load Host Configurator <==== already exists Application <===== DECNIS Configurator <==== already exists Beginning the DECNIS T2.3 Installation Verification Procedure. Copyright Digital Equipment Corporation, 1993. All rights reserved. C-2 Example Installation on an OpenVMS Load Host You will now be asked whether you wish to execute the Configurators. If you answer YES, this procedure will execute the Host Configurator, followed by the DECNIS Configurator. When executing the Configurators, you should press RETURN at the first screen and then select EXIT. *** DO NOT proceed to configure your DECNIS, at this stage *** You should check, in each Configurator, that :- o No error messages are reported. o The help file is successfully read in by the Configurator. If the above checks are successful, the IVP has succeeded. Otherwise the IVP has failed. Do you wish to execute the Configurators [Y/N ]? Y LOAD HOST CONFIGURATION Copyright Digital Equipment Corporation 1989,1993. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (C) (1) (ii) of DFARS 252.227-1013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Press RETURN to continue Reading in the help file, sys$help:nis$host_help.bin. The help file, sys$help:nis$host_help.bin, has been read in. Arrow keys to move cursor HELP for Help RETURN to select F8 to quit LOAD HOST CONFIGURATION Introduction You use this program to enter information in the load-host data file. This information enables supported routers to be downline loaded from this load host. Example Installation on an OpenVMS Load Host C-3 Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit C-4 Example Installation on an OpenVMS Load Host LOAD HOST CONFIGURATION Main Menu Add a router Delete a router Modify a router List a router Update a router Restore a router Exit this program Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Copyright Digital Equipment Corporation 1989,1993. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (C) (1) (ii) of DFARS 252.227-1013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Press RETURN to continue Reading in the help file, sys$help:nis$decnis_config_help.bin. The help file, sys$help:nis$decnis_config_help.bin, has been read in. Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Introduction Example Installation on an OpenVMS Load Host C-5 This procedure allows you to configure a DEC Network Integration Server system. The procedures take you through a series of menus and data entry screens. They allow you to change or delete the data you enter. When you have provided all the information required, the procedures will create an NCL initialization script for your system. Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Main Menu Create a new configuration Modify an existing configuration Exit from this procedure Arrow keys to move cursor HELP for Help RETURN to select F8 to quit This procedure will now execute the Script Compiler. The file MOM$SYSTEM:NIS$TEST_SCRIPT.LOG contains a log of the script compilation. If any errors appear in this log, you should consider the IVP to have failed. The IVP will search this log for errors, and report that it has completed with errors if any are found. C-6 Example Installation on an OpenVMS Load Host NCL errors are indicated by the message : Command failed due to: Running the Script Compiler... %NCL-I-PRIVATESECTION, using private parse table section %SEARCH-I-NOMATCHES, no strings matched This procedure will now execute the Image Compression utility. This utility builds compressed images which can then be loaded into nvram within the DECNIS, removing the need for the DECNIS to load its software from the network. Performing test compression, please wait... Compress Done - Image version 2.3-83 The DECNIS T2.3 Installation Verification Procedure has completed successfully. Installation of NIS V2.3 completed at 11:04 Enter the products to be processed from the next distribution volume set. * Products: Example Installation on an OpenVMS Load Host C-7 D ________________________________________________________________ Files Installed on ULTRIX Load Hosts D.1 Introduction This appendix lists the files installed on an ULTRIX load host by the DECNIS installation procedure. __________________________________________________________ Pathname_and_File__________Description____________________ /etc/bootptab.default Default bootptab file /usr/bin/ncl.nis230 NCL image /usr/etc/bootpd.nis BOOTP daemon /usr/etc/dnaevld.nis230 Event logger for DECnet /usr/lib/dna/dict/ncl_ Bridge module dna5_bridge.dd /usr/lib/dna/dict/ncl_ Bridge module text file dna5_bridge.ms /usr/lib/dna/dict/ncl_ CHDLC module dna5_chdlc.dd /usr/lib/dna/dict/ncl_ CHDLC module text file dna5_chdlc.ms /usr/lib/dna/dict/ncl_ CSMA-CD module dna5_csmacd.dd /usr/lib/dna/dict/ncl_ CSMA-CD module text file dna5_csmacd.ms /usr/lib/dna/dict/ncl_ FDDI module dna5_fddi.dd /usr/lib/dna/dict/ncl_ FDDI module text file dna5_fddi.ms /usr/lib/dna/dict/ncl_ Frame relay module dna5_frbs.dd Files Installed on ULTRIX Load Hosts D-1 __________________________________________________________ Pathname_and_File__________Description____________________ /usr/lib/dna/dict/ncl_ Frame relay module text file dna5_frbs.ms /usr/lib/dna/dict/ncl_ Hardware module dna5_hardware.dd /usr/lib/dna/dict/ncl_ Hardware module text file dna5_hardware.ms /usr/lib/dna/dict/ncl_ HDLC module dna5_hdlc.dd /usr/lib/dna/dict/ncl_ HDLC module text file dna5_hdlc.ms /usr/lib/dna/dict/ncl_ LAPB module dna5_lapb.dd /usr/lib/dna/dict/ncl_ LAPB module text file dna5_lapb.ms /usr/lib/dna/dict/ncl_ MOP module dna5_mop.dd /usr/lib/dna/dict/ncl_ MOP module text file dna5_mop.ms /usr/lib/dna/dict/ncl_ Node module dna5_node.dd /usr/lib/dna/dict/ncl_ Node module text file dna5_node.ms /usr/lib/dna/dict/ncl_ PPP module dna5_ppp.dd /usr/lib/dna/dict/ncl_ PPP module text file dna5_ppp.ms /usr/lib/dna/dict/ncl_ Routing module dna5_routing.dd /usr/lib/dna/dict/ncl_ Routing module text file dna5_routing.ms /usr/lib/dna/dict/ncl_ SNMP module dna5_snmp.dd /usr/lib/dna/dict/ncl_ SNMP module text file dna5_snmp.ms D-2 Files Installed on ULTRIX Load Hosts __________________________________________________________ Pathname_and_File__________Description____________________ /usr/lib/dna/dict/ncl_ X.25 Relay module x25_relay.dd /usr/lib/dna/dict/ncl_ X.25 Relay module text file x25_relay.ms /usr/lib/dna/dict/bridge_ Bridge module help module.hlp /usr/lib/dna/dict/csmacd_ CSMA-CD module help module.hlp /usr/lib/dna/dict/device_ Device module help module.hlp /usr/lib/dna/dict/fddi_ FDDI module help module.hlp /usr/lib/dna/dict/frbs_ Frame relay module help module.hlp /usr/lib/dna/dict Hardware module help /hardware_module.hlp /usr/lib/dna/dict/mop_ MOP module help module.hlp /usr/lib/dna/dict/ppp_ PPP module help module.hlp /usr/lib/dna/dict Routing module help /routing_module.hlp /usr/lib/dna/dict Session control module help /session_module.hlp /usr/lib/dnet/dec_elan_ DEC Vendor MIB mib.v27_txt /usr/lib/dnet/fcns_ni.txt X.25 Network information /usr/lib/dnet/nis023.releasRelease notes notes /usr/lib/dnet/nis_decnis_ DECNIS configurator config /usr/lib/dnet/nis_decnis_ DECNIS configurator messages config.bin /usr/lib/dnet/nis_decnis_ DECNIS configurator help config_help.bin Files Installed on ULTRIX Load Hosts D-3 __________________________________________________________ Pathname_and_File__________Description____________________ /usr/lib/dnet/nis_decnis_ NCL template ncl_template.bin /usr/lib/dnet/nis_ Event messages text events.txt /usr/lib/dnet/nis_flash Flash compression utility /usr/lib/dnet/nis_host_ Load-host configurator config /usr/lib/dnet/nis_host_ Load-host configurator messages config.bin /usr/lib/dnet/nis_host_ Load-host configurator help help.bin /usr/lib/dnet/nis_image_ Shell script for image compress compression utility /usr/lib/dnet/nis_ivp Installation verification procedure /usr/lib/dnet/nis_script_ Script compiler compile /usr/lib/dnet/nis_ Example NCL script example.ncl /usr/lib/dnet/nis_ospf_ OSPF example NCL script example1.ncl /usr/lib/dnet/nis_ospf_ OSPF example NCL script example2.ncl /usr/lib/dnet/nis_ospf_ OSPF example NCL script example3.ncl /usr/lib/dnet/nis_ System image images.dat /usr/lib/dnet/mcc_add_ Shell script to add the new applications.sh_new.dat application menu /usr/lib/dnet/mcc_decnis_ Customization file for DECmcc appl.dat application menu DECmcc V1.2 /usr/lib/dxbook Bookreader file for DECNIS /decnispsg.decw_book Problem Solving manual /usr/lib/dxbook Bookshelf for DECNIS Problem /decnispsg.decw_bookshelf Solving manual D-4 Files Installed on ULTRIX Load Hosts __________________________________________________________ Pathname_and_File__________Description____________________ /usr/lib/mop/digital/fcns Modem connect profile file /mcnm_prf /usr/lib/mop/digital/fcns X.25 Level 2 profile file /x25l2_prf /usr/lib/mop/digital/fcns X.25 Level 3 profile file /x25l3_prf /usr/lib/mop/nis023.sys System image /usr/man/man8/nis_decnis_ Configurator manpages config.8 /usr/man/man8/nis_host_ Load-host manpages config.8 /usr/man/man8/nis_image_ Compression utility manpages compress.8 /usr/man/man8/nis_script_ NCL script compiler manpages compile.8 /usr/mcc/mcc_appl_ Customization file for DECmcc decnis.def_________________application_menu_DECmcc_V1.3___ Files Installed on ULTRIX Load Hosts D-5 E ________________________________________________________________ Example Installation on an ULTRIX Load Host This appendix contains an example installation of DECNIS software on an ULTRIX load host. Throughout this appendix, text you type in is indicated by a bold typeface. # setld -l . NIRNIS230 ******************************************************************************* The Event Dispatcher (dnaevld) is running on this system. This installation modifies the data dictionary used by ncl and the event dispatcher. This requires that the event dispatcher be restarted. If you choose to *CONTINUE* with the installation, the event dispatcher will be left running during the installation, but will be *KILLED* and *RE-STARTED* when the data dictionary has been updated. Any events received while the data dictionary is being modified will be lost. ******************************************************************************* Do you wish to continue with the installation? (y/n) [y]: y --------------------------- The event dispatcher will be killed when the dictionary has been updated and will be restarted using /etc/dna/start_event_dispatcher.ncl --------------------------- Example Installation on an ULTRIX Load Host E-1 ************************************************************************** * DEC Network Integration Server V2.3 Installation Procedure * * * * Copyright Digital Equipment Corporation. 1993. All rights reserved. * * * * An example installation log for this product is included in the * * Installation and Configuration manual. This log contains all the * * messages displayed by this installation procedure. * * * * You should read these notes and this log immediately AFTER installing * * this product, because it contains important information about how to * * use the DECNIS software. * * * * * * NIRNIS230 Installation started at Wed 26 Jan 1994, 10:06:35 * * * ************************************************************************** Installing an ULTRIX (RISC) kit onto an ULTRIX (RISC) system Saving /usr/lib/dna/dict/bridge_module.hlp... Saving /usr/lib/dna/dict/csmacd_module.hlp... Saving /usr/lib/dna/dict/fddi_module.hlp... Saving /usr/lib/dna/dict/frbs_module.hlp... Saving /usr/lib/dna/dict/hardware_module.hlp... Saving /usr/lib/dna/dict/mop_module.hlp... Saving /usr/lib/dna/dict/ppp_module.hlp... Saving /usr/lib/dna/dict/routing_module.hlp... Saving /usr/lib/dna/dict/device_module.hlp... Saving /usr/lib/dna/dict/session_module.hlp... DECNIS V2.3 for RISC ULTRIX (NIRNIS230) Copying from . (disk) Working....Wed Jan 26 10:06:58 GMT 1994 Verifying Do you want to run the IVP after the installation? (y/n) [y]: y E-2 Example Installation on an ULTRIX Load Host **** Checking dates of profile files **** `/usr/lib/mop/digital/fcns/mcnm_prf' is up to date. `/usr/lib/mop/digital/fcns/x25l2_prf' is up to date. `/usr/lib/mop/digital/fcns/x25l3_prf' is up to date. `/usr/lib/dnet/fcns_ni.txt' is up to date. mkdir: /usr/lib/mop/digital/FCNS: File exists /usr/lib/mop/digital/FCNS/MCNM_PRF: File exists /usr/lib/mop/digital/FCNS/X25L2_PRF: File exists /usr/lib/mop/digital/FCNS/X25L3_PRF: File exists mcc_add_applications: Application 'DECNIS Load Host Configurator' already exists. No changes made to resource file. mcc_add_applications: Application 'DECNIS Configurator' already exists. No changes made to resource file. No further questions will be asked until the IVP phase. Killing the Event Dispatcher daemon (dnaevld)... *** Updating with new DECNIS NCL modules... **** Checking dates of data dictionary source files **** **** Installing (newer) kit file: ncl_dna5_bridge.dd... **** Installing (newer) kit file: ncl_dna5_fddi.dd... **** Installing (newer) kit file: ncl_dna5_frbs.dd... **** Installing (newer) kit file: ncl_dna5_hardware.dd... **** Installing (newer) kit file: ncl_dna5_ppp.dd... **** Installing (newer) kit file: ncl_dna5_routing.dd... **** Installing (newer) kit file: ncl_dna5_x25_relay.dd... **** Installing (newer) kit file: ncl_dna5_csmacd.dd... **** Installing (newer) kit file: ncl_dna5_chdlc.dd... **** Installing (newer) kit file: ncl_dna5_hdlc.dd... **** Installing (newer) kit file: ncl_dna5_mop.dd... **** Installing (newer) kit file: ncl_dna5_node.dd... **** Installing (newer) kit file: ncl_dna5_snmp.dd... **** Installing (newer) kit file: ncl_dna5_lapb.dd... **** Modifying /usr/lib/dna/dict/ddfiles to add DECNIS-relevant NCL entities /usr/lib/dna/dict/ddfiles updated *** New DECNIS NCL entities successfully added into /usr/lib/dna/dictionary.dat ***** Starting dnaevld image... *** Modifying /usr/lib/dna/dict/helpfiles to add DECNIS help entities *** /usr/lib/dna/dict/helpfiles updated - now re-making /usr/lib/dna/ncl_help.txt.. /usr/lib/dna/ncl_help.txt updated Example Installation on an ULTRIX Load Host E-3 ---------------------------- Beginning DECNIS V2.3 Installation Verification Procedure (IVP) ) Digital Equipment Corporation. 1993. All rights reserved. ...all component files for the DECNIS subset verified present. ---------------------------- Checking version numbers of installed software... Software Image.............DECNIS T2.3-83 HOST Configurator..........DECNIS Host Configurator Version T2.3-83 DECNIS Configurator........DECNIS Configurator Version T2.3-83 As a final check, the IVP now executes the Host Configurator, and then DECNIS Configurator. In each, press RETURN at the first screen, then select EXIT. *DO NOT* proceed to configure your DECNIS at this stage. ------ In each Configurator, check that: o No error messages are reported o The help file is successfully read in by the Configurator. ************************* NOTE *************************** If the above checks are successful, the IVP has succeeded. Otherwise, the IVP has failed. ********************************************************** Press return when ready.. LOAD HOST CONFIGURATION Copyright Digital Equipment Corporation 1989,1993. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (C) (1) (ii) of DFARS 252.227-1013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Press RETURN to continue E-4 Example Installation on an ULTRIX Load Host Reading in the help file, /usr/lib/dnet/nis_host_help.bin. The help file, /usr/lib/dnet/nis_host_help.bin, has been read in. Arrow keys to move cursor HELP for Help RETURN to select F8 to quit LOAD HOST CONFIGURATION Introduction You use this program to enter information in the load-host data file. This information enables supported routers to be downline loaded from this load host. Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit LOAD HOST CONFIGURATION Main Menu Add a router Delete a router Modify a router List a router Update a router Restore a router Exit this program Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Example Installation on an ULTRIX Load Host E-5 Copyright Digital Equipment Corporation 1989,1993. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (C) (1) (ii) of DFARS 252.227-1013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Press RETURN to continue Reading in the help file, /usr/lib/dnet/nis_decnis_config_help.bin. The help file, /usr/lib/dnet/nis_decnis_config_help.bin, has been read in. Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Introduction This procedure allows you to configure a DEC Network Integration Server system. The procedures take you through a series of menus and data entry screens. They allow you to change or delete the data you enter. When you have provided all the information required, the procedures will create an NCL initialization script for your system. Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Main Menu Create a new configuration E-6 Example Installation on an ULTRIX Load Host Modify an existing configuration Exit from this procedure Arrow keys to move cursor HELP for Help RETURN to select F8 to quit Checking the image compression utility Creating a sample ncl script Creating a cmip file from the ncl script Generating CMIP file from /usr/lib/dnet/nis_tmptmp.ncl... - Logfile: /usr/lib/dnet/nis_tmptmp.log Creating a compressed image Compress Done - Image version 2.3-83 Successfully created the compressed image Providing DECNIS problem solving guide for Bookreader Old library retained as /usr/lib/dxbook/library.decw_bookshelf_old Decnis Problem Solving Guide available for Bookreader. ---------------------------- Notes ----- Example Installation on an ULTRIX Load Host E-7 1. If you have configured DECNIS servers using previous versions of the DECNIS software, you may wish to upgrade them to use the latest version of the DECNIS software: - to do this for an individual DECNIS server, use the UPDATE option in the DECNIS Host Configurator. - to do this for all your previously configured DECNIS servers, use the following command :- # /usr/lib/dnet/nis_host_config -u Any DECNIS servers which are updated will need to be rebooted to load the new software image into the server. 2. The installation may be verified at any time by typing: # setld -v NIRNIS230 Note: this also gives you the image reference number of your kit; from this, you can determine the relative ages of different images, and hence whether to update your subset. DECNIS On-Line Documentation ---------------------------- This subset places files called: 1. nis023.release_notes in /usr/lib/dnet These are the release notes for the DECNIS kit and may be printed or displayed on the screen. *********************************************************************** ** ** *** NIRNIS230 Installation Completed at Wed 26 Jan 1994, 10:10:24 *** ** ** *********************************************************************** E-8 Example Installation on an ULTRIX Load Host F ________________________________________________________________ Files Installed on DEC OSF/1 Load Hosts F.1 Introduction This appendix lists the files installed on an OSF/1 load host by the DECNIS installation procedure. __________________________________________________________ Pathname_and_File__________Description____________________ /etc/bootptab.default Default bootptab /usr/bin/ncl.nis230 NCL image /usr/etc/bootpd.nis BOOTP daemon /usr/lib/dnet/dec_elan_ DEC Vendor MIB mib.v27_txt /usr/lib/dnet/fcns_ni.txt X.25 Network information /usr/lib/dnet/mcc_add_ Shell script to add the new applications.sh_new application menu /usr/lib/dnet/mcc_decnis_ Customization file for DECmcc appl.dat application menu DECmcc V1.2 /usr/lib/dnet/nis023.releasRelease notes notes /usr/lib/dnet/nis_decnis_ DECNIS configurator config /usr/lib/dnet/nis_decnis_ DECNIS configurator messages config.bin /usr/lib/dnet/nis_decnis_ DECNIS configurator help config_help.bin /usr/lib/dnet/nis_decnis_ NCL template ncl_template.bin /usr/lib/dnet/nis_ Event messages text events.txt Files Installed on DEC OSF/1 Load Hosts F-1 __________________________________________________________ Pathname_and_File__________Description____________________ /usr/lib/dnet/nis_ Example NCL Script example.ncl /usr/lib/dnet/nis_flash Flash compression utility /usr/lib/dnet/nis_host_ Load-host configurator config /usr/lib/dnet/nis_host_ Load-host configurator messages config.bin /usr/lib/dnet/nis_host_ Load-host configurator help help.bin /usr/lib/dnet/nis_image_ Shell script for image compress compression utility /usr/lib/dnet/nis_ System image images.dat /usr/lib/dnet/nis_ivp Installation verification procedure /usr/lib/dnet/nis_ospf_ OSPF NCL examples example1.ncl /usr/lib/dnet/nis_ospf_ OSPF NCL examples example2.ncl /usr/lib/dnet/nis_ospf_ OSPF NCL examples example3.ncl /usr/lib/dnet/nis_script_ NCL script compiler compile /usr/lib/dxbook Bookreader file for DECNIS /decnispsg.decw_book Problem Solving manual /usr/lib/dxbook Bookshelf for DECNIS Problem /decnispsg.decw_bookshelf Solving manual /usr/lib/mop/digital/fcns Modem connect profile file /mcnm_prf /usr/lib/mop/digital/fcns X.25 Level 2 profile file /x25l2_prf /usr/lib/mop/digital/fcns X.25 Level 3 profile file /x25l3_prf /usr/lib/mop/nis023.sys DECNIS System image F-2 Files Installed on DEC OSF/1 Load Hosts __________________________________________________________ Pathname_and_File__________Description____________________ /usr/man/man8/nis_decnis_ DECNIS configurator manpages config.8 /usr/man/man8/nis_host_ Load-host configurator manpages config.8 /usr/man/man8/nis_image_ Compression utility manpages compress.8 /usr/man/man8/nis_script_ NCL script compiler manpages compile.8 /usr/mcc/mcc_system/mcc_ Customization file for DECmcc appl_decnis.def application menu DECmcc V1.3 /usr/share/dna/dict Bridge help /bridge_module.hlp /usr/share/dna/dict CHDLC help /chdlc_module.hlp /usr/share/dna/dict CSMA-CD help /csmacd_module.hlp /usr/share/dna/dict Device help /device_module.hlp /usr/share/dna/dict/fddi_ FDDI help module.hlp /usr/share/dna/dict/frbs_ Frame relay help module.hlp /usr/share/dna/dict Hardware help /hardware_module.hlp /usr/share/dna/dict/mop_ MOP help module.hlp /usr/share/dna/dict/ncl_ Bridge module dna5_bridge.dd /usr/share/dna/dict/ncl_ Bridge module text file dna5_bridge.ms /usr/share/dna/dict/ncl_ CHDLC module dna5_chdlc.dd /usr/share/dna/dict/ncl_ CHDLC module text file dna5_chdlc.ms Files Installed on DEC OSF/1 Load Hosts F-3 __________________________________________________________ Pathname_and_File__________Description____________________ /usr/share/dna/dict/ncl_ CSMA-CD module dna5_csmacd.dd /usr/share/dna/dict/ncl_ CSMA-CD module text file dna5_csmacd.ms /usr/share/dna/dict/ncl_ FDDI module dna5_fddi.dd /usr/share/dna/dict/ncl_ FDDI module text file dna5_fddi.ms /usr/share/dna/dict/ncl_ Frame relay module dna5_frbs.dd /usr/share/dna/dict/ncl_ Frame relay module text file dna5_frbs.ms /usr/share/dna/dict/ncl_ Hardware module dna5_hardware.dd /usr/share/dna/dict/ncl_ Hardware module text file dna5_hardware.ms /usr/share/dna/dict/ncl_ HDLC module dna5_hdlc.dd /usr/share/dna/dict/ncl_ HDLC module text file dna5_hdlc.ms /usr/share/dna/dict/ncl_ LAPB module dna5_lapb.dd /usr/share/dna/dict/ncl_ LAPB module text file dna5_lapb.ms /usr/share/dna/dict/ncl_ MOP module dna5_mop.dd /usr/share/dna/dict/ncl_ MOP module text file dna5_mop.ms /usr/share/dna/dict/ncl_ Node module dna5_node.dd /usr/share/dna/dict/ncl_ Node module text file dna5_node.ms /usr/share/dna/dict/ncl_ PPP module dna5_ppp.dd F-4 Files Installed on DEC OSF/1 Load Hosts __________________________________________________________ Pathname_and_File__________Description____________________ /usr/share/dna/dict/ncl_ PPP module text file dna5_ppp.ms /usr/share/dna/dict/ncl_ Routing module dna5_routing.dd /usr/share/dna/dict/ncl_ Routing module text file dna5_routing.ms /usr/share/dna/dict/ncl_ SNMP module dna5_snmp.dd /usr/share/dna/dict/ncl_ SNMP module text file dna5_snmp.ms /usr/share/dna/dict/ncl_ X.25 relay module dna5_x25_relay.dd /usr/share/dna/dict/ncl_ X.25 relay module text file dna5_x25_relay.ms /usr/share/dna/dict/ncl_ NCL module help module.hlp /usr/share/dna/dict/ppp_ PPP module help module.hlp /usr/share/dna/dict Routing module help /routing_module.hlp /usr/share/dna/dict Session control module help /session_module.hlp /usr/share/dna/dict/snmp_ SNMP module help module.hlp /usr/share/dna/dict/w3_ DECnet/OSI module help ncl_module.hlp____________________________________________ Files Installed on DEC OSF/1 Load Hosts F-5 G ________________________________________________________________ Example Installation on a DEC OSF/1 Load Host This appendix contains an example installation of DECNIS software on an DEC OSF/1 load host. Throughout this appendix, text you type in is indicated by a bold typeface. # setld -l . NIANIS230 Checking file system space required to install specified subsets: File system space checked OK. ************************************************************************** * DEC Network Integration Server V2.3 Installation Procedure * * * * Copyright Digital Equipment Corporation. 1993. All rights reserved. * * * * An example installation log for this product is included in the * * Installation and Configuration manual. This log contains all the * * messages displayed by this installation procedure. * * * * You should read these notes and this log immediately AFTER installing * * this product, because it contains important information about how to * * use the DECNIS software. * * * * * * NIANIS230 Installation started at Wed 26 Jan 1994, 10:19:49 * * * ************************************************************************** Installing DECnis DEC OSF/1 AXP kit onto a DEC OSF/1 AXP system Example Installation on a DEC OSF/1 Load Host G-1 Saving original /etc/bootptab file. Saving /usr/share/dna/dict/bridge_module.hlp... Saving /usr/share/dna/dict/csmacd_module.hlp... Saving /usr/share/dna/dict/fddi_module.hlp... Saving /usr/share/dna/dict/frbs_module.hlp... Saving /usr/share/dna/dict/hardware_module.hlp... Saving /usr/share/dna/dict/mop_module.hlp... Saving /usr/share/dna/dict/ppp_module.hlp... Saving /usr/share/dna/dict/routing_module.hlp... Saving /usr/share/dna/dict/device_module.hlp... Saving /usr/share/dna/dict/chdlc_module.hlp... Saving /usr/share/dna/dict/ncl_module.hlp... Saving /usr/share/dna/dict/w3_ncl_module.hlp... Saving /usr/share/dna/dict/snmp_module.hlp... Saving /usr/share/dna/dict/session_module.hlp... DECNIS V2.3 for DEC OSF/1 AXP Copying from . (disk) Working....Wed Jan 26 10:20:24 GMT 1994 Verifying Do you want to run the IVP after the installation? (y/n) [y]: y No further questions will be asked **** Checking dates of profile files **** `/usr/lib/mop/digital/fcns/mcnm_prf' is up to date. `/usr/lib/mop/digital/fcns/x25l2_prf' is up to date. `/usr/lib/mop/digital/fcns/x25l3_prf' is up to date. `/usr/lib/dnet/fcns_ni.txt' is up to date. *** Updating with new DECNIS NCL modules... G-2 Example Installation on a DEC OSF/1 Load Host **** Checking dates of data dictionary source files **** **** Installing (newer) kit file: ncl_dna5_bridge.dd... **** Installing (newer) kit file: ncl_dna5_fddi.dd... **** Installing (newer) kit file: ncl_dna5_frbs.dd... **** Installing (newer) kit file: ncl_dna5_hardware.dd... **** Installing (newer) kit file: ncl_dna5_ppp.dd... **** Installing (newer) kit file: ncl_dna5_routing.dd... **** Installing (newer) kit file: ncl_dna5_x25_relay.dd... **** Installing (newer) kit file: ncl_dna5_csmacd.dd... **** Installing (newer) kit file: ncl_dna5_chdlc.dd... **** Installing (newer) kit file: ncl_dna5_hdlc.dd... **** Installing (newer) kit file: ncl_dna5_mop.dd... **** Installing (newer) kit file: ncl_dna5_node.dd... **** Installing (newer) kit file: ncl_dna5_lapb.dd... ** New DECNIS NCL entities successfully added into /usr/share/dna/dictionary.dat /usr/share/dna/dict/helpfiles not found ---------------------------- Beginning DECNIS V2.3 Installation Verification Procedure (IVP) ) Digital Equipment Corporation. 1993. All rights reserved. ...all component files for the DECNIS subset verified present. ---------------------------- Checking version numbers of installed software... Software Image.............DECNIS T2.3-83 HOST Configurator..........DECNIS Host Configurator Version T2.3-83 DECNIS Configurator........DECNIS Configurator Version T2.3-83 As a final check, the IVP now executes the Host Configurator, and then DECNIS Configurator. In each, press RETURN at the first screen, then select EXIT. *DO NOT* proceed to configure your DECNIS at this stage. ------ In each Configurator, check that: o No error messages are reported o The help file is successfully read in by the Configurator. Example Installation on a DEC OSF/1 Load Host G-3 ************************* NOTE *************************** If the above checks are successful, the IVP has succeeded. Otherwise, the IVP has failed. ********************************************************** Press return when ready.. LOAD HOST CONFIGURATION Copyright Digital Equipment Corporation 1989,1993. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (C) (1) (ii) of DFARS 252.227-1013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Press RETURN to continue Reading in the help file, /usr/lib/dnet/nis_host_help.bin. The help file, /usr/lib/dnet/nis_host_help.bin, has been read in. Arrow keys to move cursor HELP for Help RETURN to select F8 to quit G-4 Example Installation on a DEC OSF/1 Load Host LOAD HOST CONFIGURATION Introduction You use this program to enter information in the load-host data file. This information enables supported routers to be downline loaded from this load host. Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit LOAD HOST CONFIGURATION Main Menu Add a router Delete a router Modify a router List a router Update a router Restore a router Exit this program Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Copyright Digital Equipment Corporation 1989,1993. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (C) (1) (ii) of DFARS 252.227-1013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Unpublished rights reserved under applicable copyright laws. Example Installation on a DEC OSF/1 Load Host G-5 This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Introduction This procedure allows you to configure a DEC Network Integration Server system. The procedures take you through a series of menus and data entry screens. They allow you to change or delete the data you enter. When you have provided all the information required, the procedures will create an NCL initialization script for your system. Press RETURN to continue Arrow keys to move cursor HELP for Help RETURN to select F8 to quit DECNIS CONFIGURATION Main Menu Create a new configuration Modify an existing configuration Exit from this procedure G-6 Example Installation on a DEC OSF/1 Load Host Arrow keys to move cursor HELP for Help RETURN to select F8 to quit Checking the image compression utility Creating a sample ncl script Creating a cmip file from the ncl script Generating CMIP file from /usr/lib/dnet/nis_tmptmp.ncl... - Logfile: /usr/lib/dnet/nis_tmptmp.log Creating a compressed image Compress Done - Image version 2.3-83 Successfully created the compressed image... Providing DECNIS problem solving guide for Bookreader Old library retained as /usr/lib/dxbook/library.decw_bookshelf_old Decnis Problem Solving Guide available for Bookreader. ---------------------------- Notes ----- 1. If you have configured DECNIS servers using previous versions of the DECNIS software, you may wish to upgrade them to use the latest version of the DECNIS software: - to do this for an individual DECNIS server, use the UPDATE option in the DECNIS Host Configurator. - to do this for all your previously configured DECNIS servers, use the following command :- # /usr/lib/dnet/nis_host_config -u Any DECNIS servers which are updated will need to be rebooted to load the new software image into the server. 2. The installation may be verified at any time by typing: # setld -v NIANIS230 Note: this also gives you the image reference number of your kit; from this, you can determine the relative ages of different images, and hence whether to update your subset. Example Installation on a DEC OSF/1 Load Host G-7 DECNIS On-Line Documentation ---------------------------- This subset places files called: 1. decnispsg.decw_book in /usr/lib/dxbook This is the DECwindows Bookreader version of the DECNIS Problem Solving Guide. 2. nis023.release_notes in /usr/lib/dnet These are the release notes for the DECNIS kit and may be printed or displayed on the screen. *********************************************************************** * * * NIANIS230 Installation Completed at Wed 26 Jan 1994, 10:24:04 * * * *********************************************************************** # G-8 Example Installation on a DEC OSF/1 Load Host ________________________________________________________________ Index A DEC OSF/1 load hosts ___________________________ (cont'd) Add a router, 3-2, 3-3, installation procedure, 6-2, 6-3 5-3 Address towers, 3-6, 6-6 installing on, 5-1 to 5-7 starting DECNIS B__________________________ configurator on, 8-1 BOOTP starting load-host daemon, 7-1, 7-3, 7-4 configurator on, 6-2 load hosts, 7-1 to 7-4 DECdns server, 7-1, 7-3 See also DNS BOOTP loading, 6-3, 6-4 to Name server, 3-6, 6-7 6-5, 6-12, A-3 DECnet-VAX Extensions load BOOTP/TFTP protocols, 6-2 hosts load information, 3-8 to C__________________________ 3-11 CMIP file, 7-2, 7-4 DECnet/OSI load hosts loading, 3-5, 6-5 load information, 3-3 to 3-7 D__________________________ DECNIS Data file definition, 6-5 load-host, 3-16, 6-2, steps to configure, 1-1 DECNIS configurator, 1-2, 6-12 4-1, 8-1 DEC Network Integration starting, 8-1 Server. using, 4-1 to 4-4, 8-1 to See DECNIS 8-4 DEC OSF/1 load hosts DECNIS Problem Solving files installed, F-1 to OpenVMS load hosts, 2-5 F-5 ULTRIX and DEC OSF/1 load information needed to hosts, 5-4 install on, 5-2 Index-1 Default values, A-1 Files installed (cont'd) Delete a DECNIS, 6-2 OpenVMS load hosts, B-1 Delete a router, 3-2, 3-11 to B-3 to 3-12, 6-7 to 6-8 ULTRIX load hosts, D-1 to Deleting installed files D-5 OpenVMS load hosts, 2-7 ULTRIX and DEC OSF/1 load H hosts, 5-6 ___________________________ DNS Hardware address, 3-4, See also DECdns 3-8, 6-4, A-2, A-3 lookups, 3-6, 6-6 Help namespace, 3-6, 3-16, configurator, 4-3, 8-3 6-7, 6-12 in DECNIS configurator, node name, 3-6, 3-7, 4-3 to 4-4, 8-3 to 8-4 3-11, 6-7, A-2, A-4 in load-host configurator node synonym, 3-7, 3-11, , 3-15, 6-11 6-7, A-2, A-4 keys used, 4-3 to 4-4, use of by configurators, 8-3 to 8-4 3-6, 3-11, 6-6, A-2, leaving, 4-3, 8-3 A-4 I ___________________________ E__________________________ Image/CMIP/profile file, Errors 7-2, 7-4 when running Information required configurators, 3-15, DEC OSF/1 load host 6-11 installation, 5-2 Ethernet routing circuit, load-host configuration, 3-8 3-3 to 3-11, 6-3 to Event messages 6-7, A-1 to A-4 OpenVMS load hosts, 2-5 OpenVMS load host ULTRIX and DEC OSF/1 load installation, 2-1 hosts, 5-4 ULTRIX load host Example installation installation, 5-1 DEC OSF/1, G-1 to G-8 Installation procedure OpenVMS, C-1 to C-7 DEC OSF/1 load hosts, 5-3 ULTRIX, E-1 to E-8 OpenVMS load hosts, 2-5 ULTRIX load hosts, 5-3 F Installing ___________________________ DEC OSF/1 load hosts, 5-2 FDDIcontroller 621, 3-10 to 5-7 Files installed OpenVMS load hosts, 2-1 DEC OSF/1 load hosts, F-1 to 2-9 to F-5 ULTRIX load hosts, 5-1 to 5-7 Index-2 IP address, A-3 Load-host configurator, 1-1, 3-1 to 3-16, 6-1 to K__________________________ 6-12 Keys menu options, 6-2 used in configurators, options, 3-2 4-28-2 starting on OpenVMS load used in Help, 4-3 to 4-4, host, 3-2 8-3 to 8-4 starting on ULTRIX and KNOWN TOWER, 3-6, 6-6 DEC OSF/1 load hosts, 6-2 L Load-host data file, 3-15 ___________________________ to 3-16, 6-11 to 6-12 LAN hardware address, 3-4, saving, 3-16, 6-12 3-8, 6-4, A-2, A-3 Loading LANcontroller 601, 3-10 protocols used for, 6-1 LANcontroller 602, 3-10 types of, 3-5, 6-5 List a DECNIS, 6-2 Local namespace, 3-6, List a router, 3-2 3-16, 6-6, 6-7, 6-12 Load client name, 2-6, Log file 3-3, 3-8, 5-5, 6-3, A-2, configurator errors, A-3 3-15, 6-11 Load hosts Log of installation. BOOTP, 7-1 to 7-4 See Example installation definition, 3-1, 6-1 multiple, 2-9 M non-Digital UNIX systems, ___________________________ 7-4 Menus Load protocol, 3-1 DECNIS configurator Main Load-host configuration Menu, 2-6, 5-5 information required, 3-3 load-host configurator to 3-11, A-1 Main Menu, 3-2, 3-3, modifying, 3-16, 6-12 6-2, 6-3 Load-host configuration Modify a router, 3-2, 3-12 information to 3-13, 6-2, 6-8 to 6-9 DECnet-VAX Extensions MOP circuit, 3-4, 6-4, load host, 3-8 to 3-11 A-2, A-3 DECnet/OSI load hosts, MOP loading, 3-1, 3-4, 3-3 to 3-7 3-16, 6-1, 6-3, 6-4, ULTRIX and DEC OSF/1 load 6-12 hosts, 6-3 to 6-7 Multiple load hosts, 2-9 Index-3 OpenVMS load hosts (cont'd) N__________________________ starting DECNIS Namespace configurator on, 4-1 DNS, 3-16, 6-12 starting load-host local, 3-16, 6-12 configurator on, 3-2 NCL script files, 3-6, OSF/1. 3-12, 3-13, 6-6, 6-8, See DEC OSF/1 6-9 for deleted DECNIS, 3-12, P__________________________ 6-8 Phase IV address, 3-4, Network information 3-9, 6-5, A-2 OpenVMS load hosts, 2-5 DECnet-VAX Extensions ULTRIX and DEC OSF/1 load hosts, 5-4 load host, 3-11 Network Interface Cards Port name, 3-9 to 3-11, slot number, 3-10 A-2 NIS$DECNIS_CONFIG, 4-1 Postinstallation NIS$HOST_CONFIG, 3-2 information nis_decnis_config, 8-1 OpenVMS load hosts, 2-6 nis_host_config, 6-2 ULTRIX and DEC OSF/1 load Node synonym, A-2, A-4 hosts, 5-4 Nonvolatile memory loading, Problem Solving manual 3-5, 6-5 location on ULTRIX and advantages, 3-5, 6-5 DEC OSF/1 load hosts, definition, 3-5, 6-5 5-4 modifying, 3-13, 6-9 location on VMS load updating choice of, 3-15, hosts, 2-5 6-11 Processor card, 3-4, 6-4 O__________________________ R__________________________ Online documentation Release notes OpenVMS load hosts, 2-5 OpenVMS load hosts, 2-5 ULTRIX and DEC OSF/1 load ULTRIX and DEC OSF/1 load hosts, 5-3, 5-4 hosts, 5-4 OpenVMS load hosts Restore a router, 3-2, files installed, B-1 to 3-13 to 3-14, 6-2, 6-9 B-3 to 6-10 information needed to install on, 2-1 installation procedure, 2-5 installing on, 2-1 to 2-9 Index-4 VMS load hosts. S__________________________ See OpenVMS load hosts Script files See NCL script files SESSION CONTROL KNOWN TOWER commands, 3-6, 6-6 Slot number, 3-10 Synonym, DNS node, 3-6, 6-7 T__________________________ TFTP, 6-2 -r option, 7-2 to 7-3 daemon, 7-1, 7-3, 7-4 restricted mode, 7-2 to 7-3 Type of loading, 3-11, 6-5 U__________________________ ULTRIX load hosts files installed, D-1 to D-5 information needed to install on, 5-1 installation procedure, 5-3 installing on, 5-1 to 5-7 starting DECNIS configurator on, 8-1 starting load-host configurator on, 6-2 Update a router, 3-2, 3-14 to 3-15, 6-2, 6-10 to 6-11 V__________________________ VAXcluster installing on, 2-8 to 2-9 Verifying the installation OpenVMS load hosts, 2-7 ULTRIX and DEC OSF/1 load hosts, 5-5 Index-5