DEC_Network_Integration_Server________________ Installation and Configuration for OpenVMS and Digital UNIX Order Number: AA-Q61BD-TE Revision/Update Information: This is a revised manual Software Version: DECNIS[TM] V4.0 First_Printing,_March_1994________________________________ Revised, October 1996 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, 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha, AXP, Bookreader, DEC, DECmcc, DECnet, DECNIS, DECstation, DECterm, DECwindows, Digital, MicroVAX, OpenVMS, 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 in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Windows NT is a trademark, and Windows and Windows 95 are registered trademarks of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________ Contents ................................................. xi Summary of Steps Required.................... 1-1 OpenVMS Load Hosts: Installation and Configuration OpenVMS Load Hosts OpenVMS Background Information............... 2-1 Setting System Parameters................ 2-2 OpenVMS Installation Procedure............... 2-3 OpenVMS Online Documentation................. 2-3 DECNIS Problem Solving Manual............ 2-4 The DECNIS V4.0 Software Image............... 2-4 Which Internal Image Is Loaded?.......... 2-5 Deleting an Internal Image from the Double Image............................. 2-5 Load Host Loading or Part Nonvolatile Memory Loading......................... 2-6 Full Nonvolatile Memory Loading........ 2-6 After Installation .......................... 2-7 Registering the DECNIS in a Namespace.... 2-7 Configuring a DECNIS for the First Time..................................... 2-7 Assigning a Name to the DECNIS......... 2-8 Updating a Previously Installed DECNIS ......................................... 2-8 Verifying the Installation............... 2-9 iii 2.5.5 Deleting Installed Files................. 2-9 2.5.6 Checking Your Terminal Setup............. 2-9 2.5.6.1 Type of Terminal....................... 2-9 2.5.6.2 Terminal Setup......................... 2-9 2.5.7 Reporting Problems....................... 2-10 2.6 VAXcluster Load Hosts........................ 2-10 2.7 Installing on Multiple Load Hosts............ 2-10 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 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-3 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 DECdns and the Local Namespace by the Configurators........................ 3-6 3.5.7.1 Background: the DECNIS and the DECnet/OSI Naming Services............. 3-6 3.5.7.2 Generating KNOWN TOWER Commands........ 3-6 3.5.8 Node Name (Naming Service Users Only).... 3-7 3.5.9 Node Synonym (Naming Service Users Only).................................... 3-7 3.6 Delete a Router ............................. 3-7 3.6.1 Effect of Deleting....................... 3-7 3.7 Modify a Router ............................. 3-8 3.7.1 Information that Cannot Be Modified...... 3-8 3.7.2 Running the DECNIS Configurator After Modifying................................ 3-8 3.7.3 Modifying the Type of Loading............ 3-8 3.7.3.1 Results of Changing Back to Load Host Loading................................ 3-9 3.8 Restore a Router ............................ 3-9 3.8.1 Automatic Restore........................ 3-9 3.9 Update a Router ............................. 3-9 3.9.1 Automatic Update......................... 3-10 3.9.1.1 Update Command: Full Nonvolatile Memory Loading................................ 3-10 3.9.1.2 Update Command: Part Nonvolatile Memory Loading................................ 3-10 3.9.1.3 Update Command: Load Host Loading...... 3-10 3.10 Getting Help in the Load-Host Configurator... 3-10 3.11 Errors when Running the Load-Host Configurator................................. 3-11 3.12 The Load-Host Data File...................... 3-11 3.12.1 Saving the Load-Host Data File........... 3-11 3.13 What the Load-Host Configurator Does with Load Information............................. 3-11 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 II Digital UNIX Load Hosts: Installation and Configuration v Digital UNIX Load Hosts 5.1 Digital UNIX Background Information.......... 5-1 5.2 Digital UNIX Installation Procedure.......... 5-2 5.3 Digital UNIX Online Documentation............ 5-2 5.3.1 DECNIS Problem Solving Manual............ 5-3 5.4 The DECNIS V4.0 Software Images.............. 5-3 5.4.1 Which Internal Image Is Loaded?.......... 5-4 5.4.2 Deleting an Internal Image from the Double Image............................. 5-4 5.4.2.1 Load Host Loading or Part Nonvolatile Memory Loading......................... 5-4 5.4.2.2 Full Nonvolatile Memory Loading........ 5-5 5.5 After Installation........................... 5-5 5.5.1 Registering the DECNIS in DECdns......... 5-5 5.5.2 Configuring a DECNIS for the First Time..................................... 5-6 5.5.3 Updating a Previously Installed DECNIS... 5-6 5.5.4 Verifying the Installation............... 5-7 5.5.5 Deleting Installed Files................. 5-7 5.5.6 Checking Your Terminal Setup............. 5-8 5.5.6.1 Type of Terminal....................... 5-8 5.5.6.2 Terminal Setup......................... 5-8 5.5.7 Reporting Problems....................... 5-8 the Load-Host Configurator: Digital UNIX Load 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 Before You Begin............................. 6-2 6.3 Starting the Load-Host Configurator.......... 6-2 6.4 Load-Host Configurator Menu Options.......... 6-2 6.5 How to Enter Load Information................ 6-3 6.6 Load Information............................. 6-3 6.6.1 Load Client Name ........................ 6-3 6.6.1.1 Finding the Load Client Name........... 6-4 6.6.2 Hardware Address......................... 6-4 6.6.2.1 Finding the Hardware Address........... 6-4 6.6.3 MOP Circuit (MOP Loading Only)........... 6-4 6.6.3.1 Finding the MOP Circuit Name........... 6-4 6.6.3.2 Requirement for MOP Circuit............ 6-4 6.6.4 IP Address (BOOTP Loading Only).......... 6-4 6.6.5 Phase IV Address......................... 6-5 6.6.6 Type of Loading.......................... 6-5 6.6.6.1 Definition of Nonvolatile (Flash) Memory................................. 6-5 6.6.6.2 Advantages of Nonvolatile Memory Loading................................ 6-5 6.6.7 Specifying a Dump File................... 6-6 6.6.8 Use of DECdns and the Local Namespace by the Configurators........................ 6-6 6.6.8.1 Background: the DECNIS and the DECnet/OSI Naming Services............. 6-6 6.6.8.2 Generating KNOWN TOWER Commands........ 6-7 6.6.9 Node Name (Naming Service Users Only).... 6-7 6.6.10 Node Synonym (Naming Service Users Only).................................... 6-7 6.7 Delete a Router ............................. 6-7 6.7.1 Effect of Deleting....................... 6-8 6.8 Modify a Router ............................. 6-8 6.8.1 Information that Cannot Be Modified...... 6-8 6.8.2 Running the DECNIS Configurator After Modifying................................ 6-9 6.8.3 Modifying the Type of Loading............ 6-9 6.8.3.1 Results of Changing Back to Load Host Loading................................ 6-9 6.9 Restore a Router............................. 6-9 6.9.1 Automatic Restore........................ 6-10 6.10 Update a Router ............................. 6-10 6.10.1 Automatic Update......................... 6-10 6.10.1.1 Update: Full Nonvolatile Memory Loading................................ 6-10 6.10.1.2 Update: Part Nonvolatile Memory Loading................................ 6-11 6.10.1.3 Update: Load Host Loading.............. 6-11 6.11 Getting Help ................................ 6-11 6.12 Errors when Running the Load-Host Configurator................................. 6-11 6.13 The Load-Host Data File...................... 6-11 6.13.1 Saving the Load-Host Data File........... 6-12 6.14 What the Load-Host Configurator Does with Load Information............................. 6-12 vii Up BOOTP on Load Hosts 7.1 Introduction................................. 7-1 7.2 Setting Up Digital UNIX Systems as BOOTP Load Hosts........................................ 7-1 7.2.1 Basic Steps.............................. 7-1 7.3 Setting Up Non-Digital UNIX Systems as BOOTP Load Hosts................................... 7-2 the DECNIS Configurator: Digital UNIX Load 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 Appendixes Required for Load-Host Configuration A.1 Dump File Names.............................. A-3 Installed on an OpenVMS Load Host B.1 Introduction................................. B-1 B.2 Required Files............................... B-1 B.2.1 SYS$COMMON:[DECW$BOOK] Directory......... B-1 B.2.2 SYS$COMMON:[MOM$SYSTEM] Directory........ B-1 B.2.3 SYS$EXAMPLES Directory................... B-2 B.2.4 SYS$HELP Directory....................... B-3 B.2.5 SYS$LIBRARY Directory.................... B-3 B.2.6 SYS$MANAGER Directory.................... B-3 B.2.7 SYS$MESSAGE Directory.................... B-3 B.2.8 SYS$SYSTEM Directory..................... B-4 B.2.9 SYS$TEST Directory....................... B-4 B.3 Optional Files............................... B-4 B.3.1 SYS$LIBRARY Directory.................... B-4 B.3.2 MCC_COMMON Directory..................... B-5 Example Installation on an OpenVMS Load Host C.1 Example Installation on OpenVMS Alpha Load Host......................................... C-1 C.2 Example Installation on OpenVMS VAX Load Host......................................... C-3 Files Installed on Digital UNIX Load Hosts D.1 Introduction................................. D-1 Example Installation on a Digital UNIX Load Host 1-1 Steps to Set Up the DECNIS............... 1-2 2-1 Location of Online Information: OpenVMS.................................. 2-4 2-2 Images and Management Processor Cards.... 2-5 4-1 OpenVMS Configurator Keys................ 4-2 4-2 Keys Used to Get Help.................... 4-4 5-1 Location of Online Information: Digital UNIX..................................... 5-2 5-2 Images and Management Processor Cards.... 5-4 8-1 Digital UNIX Configurator Keys........... 8-2 8-2 Keys Used to Get Help.................... 8-4 A-1 Load-Host Configuration Information: DECnet/OSI Load Hosts ................... A-2 ix _____________________________________________________________ Preface This manual explains how to: o Install the software for the DEC[TM] Network Integration Server on OpenVMS[TM] and Digital[TM] UNIX[[R]] systems. (Digital UNIX was formerly called DEC OSF /1.) o Configure OpenVMS and Digital UNIX systems so that they can downline load the DECNIS software. o Start the DECNIS text-based configurator on OpenVMS and Digital UNIX load hosts. The DEC Network Integration Server is referred to throughout this manual as the DECNIS. This manual is intended for network managers who 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 Digital UNIX (if using a Digital UNIX load host) xi 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 DEC Network Integration Server Configuration and Management from PCs This manual describes how to install and configure DECNIS software on an IBM[[R]]-compatible Personal Computer running MS-DOS[[R]]. o DEC Network Integration Server clearVISN DECNIS Configurator User Guide This manual describes how to install and configure DECNIS software on a Windows NT[TM] or Windows 95[[R]] PC. o Network management documentation for the load-host operating system you are using. o RFCs (for IP routing) 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 Comments About this Documentation We would like to know what you think about the DECNIS documentation set and online help. If you have any comments, or suggestions, please return them in any of the following ways: o Send an electronic mail message to the Internet address books@reo.mts.dec.com o Send an electronic mail message to the X.400 address S=IDC BOOKS; O=digital; OU1=reo; P=digital; A=CWMail; C=gb o Send a fax to (+44)1734 206018 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. xiii Italics This indicates variable information. decnis This indicates that you should substitute the node name of the DECNIS. If you are using a DECdns namespace or a local namespace, enter the name registered in the namespace. Prompts The following prompts precede commands that you enter: For OpenVMS: $ For Digital UNIX: # For NCL: NCL> For NCP: NCP> 1 _____________________________________________________________ Introduction This manual describes how to do the following on OpenVMS and Digital UNIX load hosts. o Install DECNIS software. o Run the load-host configurator to set up downline loading information. o Start the DECNIS text-based configurator. You use this configurator 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 text-based configurator and on loading the DECNIS hardware unit. ________________________Note ________________________ You cannot run the clearVISN DECNIS configurator on OpenVMS or Digital UNIX load hosts. _____________________________________________________ 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. Introduction 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 3 Run the DECNIS text- Chapter 4, Chapter 8 based configurator and the manual DECNIS and enter the required Configuration and Loading information 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_________________________________________________ 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 text-based 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 text-based configurator on OpenVMS load hosts. 2 _____________________________________________________________ Installing: OpenVMS Load Hosts This chapter describes how to install the DECNIS software on OpenVMS load hosts. OpenVMS Background Information The following table gives information needed before you install the software. Installing: OpenVMS Load Hosts 2-1 __________________________________________________________ Value/Description___________ OpenVMS V6.2 or later OpenVMS VAX systems: DECnet[TM]/OSI[[R]] for OpenVMS VAX V6.2 or later. OpenVMS Alpha systems: DECnet/OSI for OpenVMS Alpha V6.2 or later OpenVMS VAX systems: VT220[TM] or later termi- nal, or VAXstation[TM] running DECwindows[TM] OpenVMS Alpha systems: VT220 or later terminal, or Alpha Workstation or AlphaStation running DECwindows DECNIS hardware unit OpenVMS VAX: 1 TK50 OpenVMS Alpha: 1 CD-ROM multiple Install the kit on at least 2 load hosts so that a backup host is available Account with SYSTEM privileges OpenVMS VAX: 150,000 blocks (+ up to 64,000 blocks per dump) OpenVMS Alpha: 105,000 blocks (+ up to 64,000 blocks per dump) 30 minutes the Enter Back up system before installing the software __________________________________________________________ Setting System Parameters On OpenVMS VAX load hosts, you should set system parameters as follows: o VIRTUALPAGECNT must be at least 56000. OpenVMS Load Hosts o It is recommended that GBLPAGES and PGFLQUOTA be increased from the minimum DECnet/OSI values, as compilation will then be faster. On OpenVMS Alpha load hosts, you do not need to make any changes to the minimum values for system parameters or process quotas. OpenVMS Installation Procedure To install the DECNIS software, do the following: __________________________________________________________ Step_Action_______________________________________________ 1 Mount the DECNIS kit on a suitable device 2 Issue the following command: On OpenVMS VAX hosts: $ @SYS$UPDATE:VMSINSTAL NIS040 device-name OPTIONS N On OpenVMS Alpha hosts: $ @SYS$UPDATE:VMSINSTAL NIS040 device-name:[KITS] OPTIONS N where device-name is the device where the kit is mounted. 3 Select the option you require from the Release Notes Menu 4____Read_the_Release_Notes_before_using_the_product______ 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. Installing: OpenVMS Load Hosts 2-3 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:NIS040.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 Example NCL script SYS$EXAMPLES:*.NCL files_____________________________________________________ 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. o Edits the file LIBRARY.DECW$BOOKSHELF to include the contents of NIS$PROBLEM_SOLVING.DECW$BOOKSHELF. On a standard OpenVMS system, LIBRARY.DECW$BOOKSHELF is in the DECW$BOOK directory. DECNIS V4.0 Software Image The DECNIS software image, NIS040.SYS, is a double image. It contains two system images, with the following internal names: __________________________________________________________ Internal_Name_________Description_________________________ NIS_version-number Only supports MPC-I features NIS_version-numberB___Supports_MPC-II/III_features________ where version-number is the version number of the DECNIS software. OpenVMS Load Hosts Console Supported with MPC-II/MPC-III Only Note that the DECNIS console is supported only if either the MPC-II or MPC-III management processor card is installed. Refer to Table 2-2 for the part numbers of the management processor cards. Which Internal Image Is Loaded? The DECNIS only loads one of the internal images into nonvolatile memory. Which internal image is loaded depends on which management processor card is installed, as shown in Table 2-2: Table_2-2__Images_and_Management_Processor_Cards__________ If this This internal card image is is in- used..._________stalled..._Part_Number_of_MPC_____________ NIS_version- MPC-I DNSAN-AH number NIS_version- MPC-II DNSAN-BH or numberB Upgrade to MPC-II: contact Digital Services NIS_version- MPC-III DNSBN-AH (16 MB DRAM) or numberB DNSBN-BH (32 MB DRAM) or Upgrade to MPC-III: contact ___________________________Digital_Services_______________ Deleting an Internal Image from the Double Image If you wish, you can delete one of the internal images from the double image. You may want to do this to save disk space on the load host, or loading time to the DECNIS. To delete an image, you use the program MOD_FLSH. Section 2.4.2.1 and Section 2.4.2.2 describe how to do this. Refer to the DECNIS Management manual for a detailed description of MOD_FLSH. Installing: OpenVMS Load Hosts 2-5 Load Host Loading or Part Nonvolatile Memory Loading If you have specified load host or part nonvolatile memory loading, follow these steps on the load host: 1. Enter the following command to define MOD_FLSH as a foreign command: $ MOD_FLSH :== $ SYS$SYSTEM:MOD_FLSH.EXE This equates MOD_FLSH to the command RUN SYS$SYSTEM:MOD_ FLSH. 2. Now, enter the following command to run MOD_FLSH: $ MOD_FLSH NIS040.SYS 3. The display will show the images, with their index numbers. The MPC-II/III image (NIS_version-numberB) is index 1; the MPC-I image (NIS_version-number) is index 2. 4. Enter the following command: delete n where n is the index number of the image. Full Nonvolatile Memory Loading If you have specified full nonvolatile (flash) memory loading, the configurator will create a combined file. If you wish, you can delete the unwanted internal image from the double image, before you run the configurator, by following the steps in Section 2.4.2.1. Alternatively you can delete the internal image from the combined file. To delete an internal image from the combined file, follow these steps: 1. When you have configured your DECNIS, create a combined file for loading, as described in the manual DECNIS Configuration and Loading. 2. Enter the following command: $ MOD_FLSH :== $ SYS$SYSTEM:MOD_FLSH.EXE 3. Now, run MOD_FLSH, giving the name of the combined file: $ MOD_FLSH NIS040_client-name.SYS OpenVMS Load Hosts where client-name is the load client name of the DECNIS. 4. Follow steps 3 and 4 in Section 2.4.2.1. After Installation This section describes postinstallation tasks. Registering the DECNIS in a Namespace If you specified the use of a naming service in the load- host configurator, the configurator will attempt to register the DECNIS node in either the local namespace or the DECdns namespace. This section describes how you determine which namespace it will use. By default, the load-host configurator will attempt to register the DECNIS in the local namespace, even if DECdns is listed as the primary naming service. To override the default and register the DECNIS in DECdns, complete the following steps before you run either configurator: 1. Create a decnet_register initialization command file, and define the environment variable DECNET_REGISTER_ INIT to point to its file name. 2. Insert the following command in the file: SET DEFAULT DIRECTORY_SERVICE DECdns For more information about DECNET_REGISTER initialization files, refer to the online help provided with decnet_ register. 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 text-based configurator, as described in Chapter 4. Installing: OpenVMS Load Hosts 2-7 3. Create a configuration load file, and load the DECNIS, as described in the manual DECNIS Configuration and Loading. 4. Assign a name to the DECNIS, as described in Section 2.5.2.1. Assigning a Name to the DECNIS When you first load a DECNIS, by default it does not know its name. You need to assign a name to the DECNIS. After the DECNIS is first loaded, enter the following command: NCL> RENAME NODE p4-name NEW NAME decnis where p4-name is the Phase IV name for the DECNIS, and decnis is its DECdns name (including the namespace name) or local namespace name. 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.9. 2. Start the DECNIS text-based 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. 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. OpenVMS Load Hosts 7. Create a new load file: either a CMIP file or a combined file. 8. Repeat steps 2 to 7 for each DECNIS that will use the new version of the software. 9. Reload the DECNIS systems, as described in the manual DECNIS Configuration and Loading. Verifying the Installation To verify the installation, run the installation verification procedure. Enter: $ @SYS$TEST:NIS$IVP.COM Deleting Installed Files To delete the files installed by the installation procedure, enter: $ @SYS$MANAGER:NIS$DEINSTALL.COM Checking Your Terminal Setup In order to run the load-host configurator and the DECNIS text-based configurator, you must use one of the types of terminal listed in Section 2.5.6.1, and set up the terminal as described in Section 2.5.6.2. 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 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. Installing: OpenVMS Load Hosts 2-9 Reporting Problems For instructions on reporting problems to Digital, refer to the manual DECNIS Problem Solving. 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.2. 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, 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. 5. Run the DECNIS text-based configurator on one node within the VAXcluster and configure the DECNIS. on Multiple Load Hosts You should install the DECNIS software on at least two load hosts, so that a backup load host is available. OpenVMS Load Hosts 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. 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 text-based configurator. 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. Load Protocol DECnet/OSI for OpenVMS 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 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 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. the Load-Host Configurator: OpenVMS Load Hosts 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. Load Information This section describes the information you enter in the load-host configurator. Load Client Name The load client name identifies the DECNIS for downline loading and upline dumping. Finding the Load Client Name You create the load client name yourself. The only restrictions are: o The name must be unique to this router on the network. o The maximum length of the name is 32 characters. 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 Using the Load-Host Configurator: OpenVMS Load Hosts 3-3 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. MOP Circuit This is a circuit defined specifically for downline loading. A MOP circuit is automatically created during DECnet/OSI installation. 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. 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. 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 the Load-Host Configurator: OpenVMS Load Hosts 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 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. 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. 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 Use of DECdns and the Local Namespace by the Configurators The load-host configurator asks the question: You can choose whether or not the configurators use information from a naming service 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 a naming service to be used? No Yes This section explains how you decide what to answer. Background: the DECNIS and the DECnet/OSI Naming Services The DECNIS does not use naming service 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. 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 text-based configurator uses DECdns or local namespace lookups to generate the commands. In this case, you must supply the full node 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 text-based configurator uses addressing information you supply. the Load-Host Configurator: OpenVMS Load Hosts Node Name (Naming Service Users Only) If you choose to use a naming service, you must enter the full node name of the DECNIS system. The name you specify must conform to DECdns naming conventions. For details about the syntax of DECdns names, refer to the DECdns manual for your load host. Node Synonym (Naming Service Users Only) This is an alternative node name for the DECNIS. For convenience, you may use the Phase IV node name. The node synonym is optional. 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. 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_client-name.NCL_OLD o The CMIP file for the deleted DECNIS is renamed: SYS$COMMON:[MOM$SYSTEM]NIS_client-name.CMIP_OLD o The data file for the deleted DECNIS is renamed: SYS$COMMON:[MOM$SYSTEM]NIS_client-name.DAT_OLD where 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 Using the Load-Host Configurator: OpenVMS Load Hosts 3-7 If you delete EASTERN in the load-host configurator, the master NCL script will be renamed: NIS_EASTERN.NCL_OLD 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. Information that Cannot Be Modified The only DECNIS load information you cannot modify is the load client name. Running the DECNIS Configurator After Modifying It is strongly recommended that you rerun the DECNIS text- based configurator after using the Modify option. This is because changes to loading information may affect or even invalidate information entered in the DECNIS text-based configurator. Refer to the manual DECNIS Configuration and Loading for details. 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 text-based 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 file. the Load-Host Configurator: OpenVMS Load Hosts Results of Changing Back to Load Host Loading If you change from nonvolatile memory to load host loading, the combined file is deleted on the load host. Restore a Router The Restore option reissues the NCL 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. o The automatic Restore procedure, to restore all the DECNIS systems set up by the load-host configurator. Automatic Restore To use automatic Restore, enter the following: $ @SYS$MANAGER:NIS$HOST_CONFIG RESTORE 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. Using the Load-Host Configurator: OpenVMS Load Hosts 3-9 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.9.1.1 to Section 3.9.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.7.3. 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 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: $ @SYS$MANAGER:NIS$HOST_CONFIG UPDATE FLASH_PART 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. $ @SYS$MANAGER:NIS$HOST_CONFIG UPDATE NETWORK 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 text-based configurator. See Section 4.5 for details. the Load-Host Configurator: OpenVMS Load Hosts 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 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 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. 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.12. o Issues NCL commands to set up load details, and enters the commands in permanent configuration files. o If you have entered naming service information during load-host configuration, registers the DECNIS in the local namespace or the DECdns namespace. Using the Load-Host Configurator: OpenVMS Load Hosts 3-11 Section 2.5.1 describes how the load-host configurator decides whether to register the DECNIS in the local or DECdns namespace. the Load-Host Configurator: OpenVMS Load Hosts 4 _____________________________________________________________ Starting the DECNIS Configurator: OpenVMS Load Hosts Introduction to the DECNIS Configurator The DECNIS text-based configurator is a utility supplied with the DECNIS. You use the DECNIS text-based config- urator 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. This chapter describes how to start the configurator, the keys you can use, and how to get online help. For more detailed information, see the manual DECNIS Configuration and Loading. Before You Start Before you start the DECNIS text-based configurator, make sure that you do the following: 1. Check Section 2.5.6. This gives the terminal settings required to run both the load-host configurator and the DECNIS text-based configurator. 2. Run the load-host configurator, and set up load information for the DECNIS you want to configure. How to Start To start the DECNIS text-based 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 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_______________________ Use_this_key...__To_do_this...____________________________ Up Arrow Move the cursor to the field above Down Arrow Move the cursor to the field below Left Arrow Move the cursor to the left in a field Right Arrow Move the cursor to the right in a field or Enter the option you have chosen or Get help on a field or section Leave Help and go back to entering data Leave the configurator without saving any data Go to the previous data entry screen in a section Go to the next data entry screen in a section or Toggle between insert and overstrike when typing data or Remove all text in a field Refresh the screen Move cursor to the previous column (on _________________screens_with_two_columns)________________ the DECNIS Configurator: OpenVMS Load Hosts Online Help You can get online help when running the load-host configurator and your DECNIS text-based configurator. This section describes how to get online help, how to leave online help, and the different types of online help you can get. How to Get Online Help To get help in the load-host configurator or the DECNIS text-based configurator, press . 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 . 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. 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______________________________ the DECNIS Configurator: OpenVMS Load Hosts Part II _____________________________________________________________ Digital UNIX Load Hosts: Installation and Configuration This part describes how to do the following on Digital UNIX load hosts: o Install the DECNIS software. o Run the load-host configurator. o Start the DECNIS text-based configurator. It contains the following chapters: o Chapter 5 describes how to install the DECNIS software on Digital UNIX load hosts. o Chapter 6 describes how to configure Digital UNIX load hosts for downline loading to the DECNIS. o Chapter 7 describes additional steps needed to set up Digital UNIX load hosts for BOOTP loading. o Chapter 8 describes how to start the DECNIS text-based configurator on Digital UNIX load hosts. 5 _____________________________________________________________ Installing: Digital UNIX Load Hosts This chapter describes how to install the DECNIS software. Digital UNIX Background Information The following table gives information needed before you install the software on Digital UNIX load hosts. __________________________________________________________ Item________________Value/Description_____________________ Prerequisite Digital UNIX V3.1 (or later). software For BOOTP/TFTP loading, subset OSFCLINET031 DECnet/OSI for Digital UNIX AXP[TM]V3.1 (or later), with the following subsets: DNABASE031 (DECnet/OSI base components), DNAMOP031 (DECnet/OSI MOP Utilities) and DNANETMAN031 (DECnet /OSI Network Management) Prerequisite VT220 or later terminal, or Alpha hardware Workstation or AlphaStation running DECwindows DECNIS hardware unit Kit description 1 CD-ROM 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 Installing: Digital UNIX Load Hosts 5-1 __________________________________________________________ Disk space 22,000 Kbytes + up to 32,000 Kbytes required per dump Time required for 10 minutes installation Backup procedures Back up system before installing the ____________________software______________________________ UNIX Installation Procedure To install the DECNIS software on Digital UNIX 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_ UNIX 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:_Digital_UNIX____ Item_______________________Location_______________________ X.25 Network information /usr/lib/dnet/fcns_ni.txt Event messages /usr/lib/dnet/nis_event.txt Release Notes /usr/lib/dnet/nis040.release_ notes (continued on next page) Digital UNIX Load Hosts Table 5-1 (Cont.) Location of Online Information: Digital ___________________UNIX___________________________________ Item_______________________Location_______________________ DECNIS Problem Solving /usr/lib/dxbook/decnispsg.decw_ manual book Bookshelf for DECNIS /usr/lib/dxbook/decnispsg.decw_ Problem Solving bookshelf Example_NCL_script_files___/usr/lib/dnet/*.ncl____________ 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. The DECNIS V4.0 Software Images The DECNIS software image, NIS040.SYS, is a double image. It contains two system images, with the following internal names: __________________________________________________________ Internal Name______Description_____________________________________ nis_ Only supports MPC-I features version- number nis_ Supports MPC-II/III features version- numberB___________________________________________________ where version-number is the version number of the DECNIS software. Console Supported with MPC-II/MPC-III Only Note that the DECNIS console is supported only if either the MPC-II or MPC-III management processor card is installed. Refer to Table 5-2 for the part numbers of the management processor cards. Installing: Digital UNIX Load Hosts 5-3 Which Internal Image Is Loaded? The DECNIS only loads one of the internal images into nonvolatile memory. Which internal image is loaded depends on which management processor card is installed, as shown in Table 5-2: Table_5-2_Images_and_Management_Processor_Cards___________ If this This internal card image is is in- used..._________stalled..._Part_Number_of_MPC_____________ NIS_version- MPC-I DNSAN-AH number NIS_version- MPC-II DNSAN-BH or numberB Upgrade to MPC-II: contact Digital Services NIS_version- MPC-III DNSBN-AH (16 MB DRAM) or numberB DNSBN-BH (32 MB DRAM) or Upgrade to MPC-III: contact ___________________________Digital_Services_______________ Deleting an Internal Image from the Double Image If you wish, you can delete one of the internal images from the double image. You may want to do this to save disk space on the load host, or loading time to the DECNIS. To delete an image, you use the program MOD_FLSH. Section 2.4.2.1 and Section 2.4.2.2 describe how to do this. For a detailed description of MOD_FLSH, refer to the DECNIS Management manual. Load Host Loading or Part Nonvolatile Memory Loading If you have specified load host loading (or part nonvolatile memory loading), follow these steps on the load host: 1. Run the program MOD_FLSH: # /usr/lib/dnet/mod_flsh nis040.sys Digital UNIX Load Hosts 2. The display will show the images, with their index numbers. The MPC-II/III image (NIS_version-numberB) is index 1; the MPC-I image (NIS_version-number) is index 2. 3. Enter the following command: delete n where n is the index number of the image. Full Nonvolatile Memory Loading If you have specified full nonvolatile (flash) memory loading, the configurator will create a combined file. If you wish, you can delete the unwanted internal image from the double image, before you run the configurator, by following the steps in Section 5.4.2.1. Alternatively you can delete the internal image from the combined file. To delete an internal image from the combined file, follow these steps: 1. When you have configured the DECNIS, create a combined file. Refer to the manual DECNIS Configuration and Loading for details. 2. Run the program MOD_FLSH, giving the name of the combined file: # /usr/lib/dnet/mod_flsh nis040client-name.sys where client-name is the client name of the DECNIS. 3. Follow steps 2 and 3 in Section 5.4.2.1. After Installation This section describes postinstallation tasks. Registering the DECNIS in DECdns If you specified the use of a naming service in the load- host configurator, the DECNIS text-based configurator will attempt to register the DECNIS node in either the local namespace or the DECdns namespace. This section describes how you determine which namespace it will use. Installing: Digital UNIX Load Hosts 5-5 By default, the load-host configurator will attempt to register the DECNIS node name in the local namespace, even if DECdns is listed as the primary naming service. To override the default and register the DECNIS in DECdns, complete the following steps before you run either configurator: 1. Create a decnet_register initialization command file, and define the environment variable DECNET_REGISTER_ INIT to point to its file name. 2. Insert the following command in the file: SET DEFAULT DIRECTORY_SERVICE DECdns For more information about decnet_register initialization files, refer to the online help provided with decnet_ register. 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. If you plan to use BOOTP/TFTP for loading, check that the BOOTP and the TFTP daemons are started. Refer to Section 7.2.1 for details. 2. Run the load-host configurator, as described in Chapter 6. 3. Run the DECNIS text-based configurator, as described in Chapter 8. 4. Create a configuration load file, and load the DECNIS, as described in the manual DECNIS Configuration and Loading. 5. Assign a name to the DECNIS, as described in Section 2.5.2.1. 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. Digital UNIX 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.10. 2. Start the DECNIS text-based 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 a combined file. 8. Repeat steps 2 to 7 for each DECNIS that will use the new version of the software. 9. Reload your DECNIS systems, as described in the manual DECNIS Configuration and Loading. Verifying the Installation To verify the installation, enter the following: # setld -v NIANIS400 Deleting Installed Files To delete the files installed by the installation procedure, enter: # setld -d NIANIS400 Installing: Digital UNIX Load Hosts 5-7 Checking Your Terminal Setup In order to run the load-host configurator and the DECNIS text-based configurator, you must use one of the types of terminal listed in Section 5.5.6.1, and set up the terminal as described in Section 5.5.6.2. Type of Terminal You can run the configurators on the following types of terminal: o A VT220 (or later) terminal o A terminal window on an Alpha AXP workstation 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. 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. Reporting Problems For instructions on reporting problems to Digital, refer to the manual DECNIS Problem Solving. Digital UNIX Load Hosts 6 _____________________________________________________________ Using the Load-Host Configurator: Digital UNIX Load Hosts This chapter describes how to use the load-host configura- tor to configure the DECNIS to load from Digital UNIX load hosts. 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 text-based configurator. 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. Load Protocols Digital UNIX 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. o BOOTP/TFTP is a set of protocols used for loading and dumping, defined in RFCs 783 and 951. the Load-Host Configurator: Digital UNIX Load Hosts 6-1 You Begin If you plan to use BOOTP/TFTP for loading, check that the BOOTP and the TFTP daemons are started. Refer to Section 7.2.1 for details. 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 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. the Load-Host Configurator: Digital UNIX Load Hosts 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 that Digital UNIX 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. Load Information This section describes the information you enter in the load-host configurator. Load Client Name The load client name identifies the DECNIS for downline loading and upline dumping. the Load-Host Configurator: Digital UNIX Load Hosts 6-3 Finding the Load Client Name You create the load client name yourself. The only restrictions are: o The name must be unique to this router on the network. o The maximum length of the name is 32 characters. 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 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. MOP Circuit (MOP Loading Only) This is a circuit defined specifically for downline loading. A MOP circuit is automatically created during DECnet/OSI installation. 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. 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. IP Address (BOOTP Loading Only) If you use BOOTP for loading, you must supply an IP address for the DECNIS. the Load-Host Configurator: Digital UNIX Load Hosts Format The format of the IP address is four decimal integers, separated by decimal points. For example, 24.45.21.8. 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 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 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. 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. the Load-Host Configurator: Digital UNIX Load Hosts 6-5 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_client-name.dmp where client-name is the load client name of the DECNIS. It is important to check that there is enough disk space on your load host to receive dumps. The table in Section 5.1 shows the amount of disk space required for dumps. Use of DECdns and the Local Namespace by the Configurators The load-host configurator asks the question: You can choose whether or not the configurators use information from a naming service 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 a naming service to be used? No Yes This section explains how you decide what to answer. Background: the DECNIS and the DECnet/OSI Naming Services The DECNIS does not use naming service 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. the Load-Host Configurator: Digital UNIX Load Hosts 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 text-based configurator uses DECdns or local namespace lookups to generate the commands. In this case, you must supply a full node 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. Node Name (Naming Service Users Only) If you choose to use a naming service, you must enter the full node name of the DECNIS system. The name you specify must conform to DECdns naming conventions. For details about the syntax of DECdns names, refer to the DECdns manual for your load host. Node Synonym (Naming Service Users Only) This is an alternative node name for the DECNIS. For convenience, you may use the Phase IV node name. The node synonym is optional. 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. the Load-Host Configurator: Digital UNIX Load Hosts 6-7 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_client-name.ncl_old o The CMIP file for the deleted DECNIS is renamed: /usr/lib/mop/nis_client-name.cmip_old o The data file for the deleted DECNIS is renamed: /usr/lib/dnet/nis_client-name.dat_old where 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 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. Information that Cannot Be Modified The only DECNIS load information you cannot modify is the load client name. the Load-Host Configurator: Digital UNIX Load Hosts Running the DECNIS Configurator After Modifying You must rerun the DECNIS text-based 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 text-based configurator. Refer to the manual DECNIS Configuration and Loading for details. 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 text-based 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 file. Results of Changing Back to Load Host Loading If you change from nonvolatile memory to load host loading, the combined file is deleted on the load host. 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. the Load-Host Configurator: Digital UNIX Load Hosts 6-9 Automatic Restore To use automatic Restore, enter the following: # /usr/lib/dnet/nis_host_config -r 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. 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.10.1.1 to Section 6.10.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.8.3. 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 the Load-Host Configurator: Digital UNIX Load Hosts 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 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 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 text-based configurator. See Section 8.5 for details. 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 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 the Load-Host Configurator: Digital UNIX Load Hosts 6-11 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. 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.13. 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 naming service information during load-host configuration, registers the DECNIS in the local namespace or the DECdns namespace. Section 5.5.1 describes how the load-host configurator decides whether to register the DECNIS in the local or DECdns namespace. the Load-Host Configurator: Digital UNIX Load Hosts 7 _____________________________________________________________ Setting Up BOOTP on Load Hosts Introduction This chapter describes how to set up Digital UNIX and non-Digital UNIX[[R]] systems for BOOTP loading. Setting Up Digital UNIX Systems as BOOTP Load Hosts To set up Digital UNIX systems for BOOTP loading, check the steps in Section 7.2.1. Basic Steps 1. When you run the load-host configurator, select either BOOTP or MOP and BOOTP. 2. Ensure that the BOOTP and TFTP daemons are started on system startup. 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 c. Enter the following command to force the inetd daemon to reread the inetd.conf file: kill -1 process-id where process-id is the process number of the inetd process. Setting Up BOOTP on Load Hosts 7-1 Up Non-Digital UNIX 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 Digital UNIX 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 the required load file, and copy it to the load UNIX load host: o If you are using nonvolatile memory loading, generate a combined image/CMIP/profile file, and copy it to the UNIX load host. o If you are using load host loading, generate a CMIP file. Then copy the CMIP file, the image file, and any profile files to the UNIX load host. Refer to DECNIS Configuration and Loading for details. 4. 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. Up BOOTP on Load Hosts 8 _____________________________________________________________ Starting the DECNIS Configurator: Digital UNIX Load Hosts Introduction to the DECNIS Configurator The DECNIS text-based configurator is a utility supplied with the DECNIS. You use the DECNIS text-based config- urator 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. This chapter describes how to start the configurator, the keys you can use, and how to get online help. For more detailed information, see the manual DECNIS Configuration and Loading. Before You Start Before you start the DECNIS text-based configurator, make sure that you do the following: 1. Check Section 5.5.6. This gives the terminal settings required to run both the load-host configurator and the DECNIS text-based configurator. 2. Run the load-host configurator, and set up load information for the DECNIS you want to configure. How to Start To start the DECNIS text-based configurator, follow these steps: 1. Log in as a superuser. 2. Enter the command: # /usr/lib/dnet/nis_decnis_config Starting the DECNIS Configurator: Digital UNIX Load Hosts 8-1 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_Digital_UNIX_Configurator_Keys__________________ Use_this_key...__To_do_this...____________________________ Up Arrow Move the cursor to the field above Down Arrow Move the cursor to the field below Left Arrow Move the cursor to the left in a field Right Arrow Move the cursor to the right in a field or Enter the option you have chosen or Get help on a field or section Leave Help and go back to entering data Quit the configurator without saving any data Go to the previous data entry screen in a section Go to the next data entry screen in a section or Shift between insert and overstrike when typing data or Remove all text in a field Refresh the screen Move cursor to the previous column (on _________________screens_with_two_columns)________________ the DECNIS Configurator: Digital UNIX Load Hosts Online Help You can get online help when running the load-host configurator and your DECNIS text-based configurator. This section describes how to get online help, how to leave online help, and the different types of online help you can get. How to Get Online Help To get help in the load-host configurator or the DECNIS text-based configurator, press . 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 . 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. Keys to Get Help Table 8-2 lists the keys you can use to get Help, or to leave Help. Starting the DECNIS Configurator: Digital UNIX 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______________________________ the DECNIS Configurator: Digital UNIX 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/OSI for Digital UNIX 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 Digital UNIX load hosts. o Appendix E is an example log of an installation on a Digital UNIX load host. A _____________________________________________________________ Information Required for Load-Host Configuration Table A-1 lists 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 A-1 Load-Host Configuration Information: DECnet/OSI Load Hosts__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ Select from list R - Select one: MOP; BOOTP; R - MOP Both Create a name to R - identify the DECNIS for loading. Max. 32 characters LAN address of the R - DECNIS, as printed on the label on the Processor Card. Example: 08-00-2B-02- AA-20 Name of the MOP R - circuit used to load only) the DECNIS. Max. 32 characters IP address for the R - DECNIS only) Phase Area number.node number O (but - of Example: 2.43 R to commu- nicate with Phase IV sys- tems) (continued on next page) Required for Load-Host Configuration A-1 (Cont.) Load-Host Configuration Information: DECnet /OSI Load Hosts_____________________________________________________________ R(equired) / Your Notes O(ptional)Default Value_____________________________________________________________ of Select one: nonvolatile R Nonvolatile memory for both; memory load host for CMIP, for both nonvolatile memory for image; load host for both a dump Select Yes or No R - Select Yes or No R Yes naming name Full node name of R if - DECNIS naming service chosen synonym Alternative name for O - the DECNIS, recorded in DECdns or the local namespace. Max. 6 characters_____________________________________________________________ Dump File Names Refer to Section 3.5.6 for the dump file name and location on OpenVMS load hosts. Refer to Section 6.6.7 for the dump file name and location on Digital UNIX load hosts. Information Required for Load-Host Configuration A-3 B _____________________________________________________________ Files Installed on an OpenVMS Load Host Introduction This appendix lists the files installed on an OpenVMS load host by the DECNIS installation procedure. Required Files This section lists the files that are always installed in the DECNIS installation procedure. SYS$COMMON:[DECW$BOOK] Directory o NIS$PROBLEM_SOLVING.DECW$BOOK-Problem solving manual o NIS$PROBLEM_SOLVING.DECW$BOOKSHELF-Problem solving bookshelf SYS$COMMON:[MOM$SYSTEM] Directory 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 o NIS040.SYS - DECNIS double system image o NIS040B.SYS-DECNIS system image (no console NCL) o NIS$TEST_SCRIPT.NCL-Test script (Not on OpenVMS Alpha) o NIS$IMAGES.DAT -List of supported NIS images Files Installed on an OpenVMS Load Host B-1 SYS$EXAMPLES Directory o NIS$ATM_DS3.NCL-ATM on DS3 lines NCL example o NIS$ATM_E3.NCL-ATM on E3 lines NCL example o NIS$ATM_OC3.NCL-ATM on OC3 lines NCL example o NIS$ATM_OC3_CLASS_IP.NCL-ATM Classical IP on OC3 lines NCL example o NIS$BACKUP.NCL-Backup circuits NCL example o NIS$PACK_FILT.NCL-IP packet filtering NCL example o NIS$DNS_NAME_SERVER.NCL -IP services NCL example o NIS$IP_MULTICAST.NCL- IP multicast NCL example o NIS$ICMP_RD.NCL-ICMP router discovery NCL example o NIS$IPX_WAN.NCL-IPX WAN NCL example o NIS$IP_PRIORITY_PATT.NCL-IP pattern matching prioriti- zation NCL example o NIS$IP_STANDBY.NCL-IP standby NCL example o NIS$LAT_PRIORITY_PATT.NCL-LAT pattern matching prioritization NCL example o NIS$NCL_EXAMPLE.NCL-Simple NCL example o NIS$OSPF_MINIMUM.NCL-OSPF NCL example o NIS$OSPF_MULTI_AREA.NCL-OSPF NCL example o NIS$OSPF_VIRTUAL.NCL-OSPF NCL example o NIS$PRIORITY.NCL-Prioritization NCL example o NIS$SMDS.NCL-SMDS NCL example o NIS$X25_LANWAN_RELAY.NCL-LAN/WAN relay NCL example o NIS$X25_LOCAL_RELAY.NCL-X.25 local relay NCL example o NIS$X25_REMOTE_RELAY.NCL-X.25 remote relay NCL example o DTF.TXT-DECNIS Trace Facility manual o DTFAXP.A-DTF for OpenVMS Alpha hosts o DTFOSF.TAR-DTF for Digital UNIX hosts Installed on an OpenVMS Load Host o DTFULTRIX.TAR-DTF for ULTRIX hosts o DTFVMS.A-DTF for OpenVMS VAX hosts o DTFW32.ZIP-DTF for Windows[[R]] NT hosts SYS$HELP Directory o DEC_ELAN_MIB.V27_TXT-DEC specific MIB o NIS$DECNIS_CONFIG_HELP.BIN-DECNIS configurator help o NIS$EVENTS.TXT-Event messages o NIS$HOST_HELP.BIN-Load-host configurator help o NIS040.RELEASE_NOTES-Release Notes o NCLHELP.HLP-NCL help o FCNS$NI.TXT-Documentation for X.25 network profiles SYS$LIBRARY Directory o CTF$*.*-To enable tracing using the Common Trace Facility SYS$MANAGER Directory o NIS$CMIP_FILE.FDL-Exchange file o NIS$DECNIS_CONFIG.COM-DECNIS configuration 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$COMBINE.COM-Combined file creation procedure SYS$MESSAGE Directory o NIS$DECNIS_CONFIG.BIN-DECNIS configurator messages o NIS$DECNIS_NCL_TEMPLATE.BIN-NCL command messages o NIS$HOST_CONFIG.BIN-Load-host configurator messages Files Installed on an OpenVMS Load Host B-3 SYS$SYSTEM Directory o DECROU$NCL.EXE-DECNIS NCL utility (not on OpenVMS VAX) o DICTARY.DAT-Parse tables for the bridge management utility o MOD_FLSH.EXE-Utility for editing the combined file o NIS$NCHK.EXE-NCL checking utility (Not on OpenVMS VAX) o NCLPRS.BIN-Parsing information for the bridge management utility o NIS$BRIDGE_MGMT.EXE-Bridge management utility o NIS$DECNIS_CONFIG.EXE-DECNIS configurator program o NIS$DECNIS_SMDS_CONFIG.EXE -SMDS configurator program o NIS$FLASH.EXE-Flash compression utility o NIS$HOST_CONFIG.EXE-Load-host configurator 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 PROTOID.MAP-Protocol identifiers for the bridge management utility SYS$TEST Directory o NIS$IVP.COM-Installation verification procedure Files The files listed will be optionally installed, based on the installation state of NCL. SYS$LIBRARY Directory o NCL$GLOBALSECTION.DAT-NCL global section (NCL dictionary) Installed on an OpenVMS Load Host 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-5 C _____________________________________________________________ Example Installation on an OpenVMS Load Host This appendix contains an example installation of DECNIS software on OpenVMS Alpha and OpenVMS VAX load hosts. Throughout this appendix, text you type in is indicated by a bold typeface. Example Installation on OpenVMS Alpha Load Host OpenVMS AXP Software Product Installation Procedure V6.1 is 27-OCT-1996 at 15:01. a question mark (?) at any time for help. you satisfied with the backup of your system disk [YES]? will the distribution volumes be mounted: VANGOF$DKA500:[DECNIS_ the products to be processed from the first distribution volume set. NISAXP040 installation options you wish to use (none): following products will be processed: V4.0 Beginning installation of NISAXP V4.0 at 15:01 Restoring product save set A ... Product's release notes have been moved to SYS$HELP. DECNIS version V4.0 will take approximately 45 minutes install, depending on hardware configuration. Example Installation on an OpenVMS Load Host C-1 Network Integration Server V4.0 Installation Procedure. Digital Equipment Corporation 1991, 1996. All rights reserved. Rights: Use, duplication, or disclosure by the U.S. Government subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS or in FAR 52.227-19, or in FAR 52.227- III, as software is proprietary to and embodies the confidential technology of Equipment Corporation. Possession, use, or copying of this software media is authorized only pursuant to a valid written license from or an authorized sublicensor. should read the Release Notes immediately AFTER installing product. The release notes for the DECNIS are in a file NIS040.RELEASE_NOTES which is in the SYS$HELP directory. want to purge files replaced by this installation [YES]? want to run the IVP after the installation [YES]? 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. Restoring product save set B ... Restoring product save set C ... Files will now be moved to their target directories... the DECNIS V4.0 Installation Verification Procedure. Digital Equipment Corporation 1991, 1996. All rights reserved. will now be asked whether you wish to execute the Configurators. you answer YES, this procedure will execute the Host Configurator, by the DECNIS Configurator. executing the Configurators, you should press RETURN at the screen and then select EXIT. DO NOT proceed to configure your DECNIS, at this stage *** should check, in each Configurator, that :- No error messages are reported. The help file is successfully read in by the Configurator. Installation on an OpenVMS Load Host If the above checks are successful, the IVP has succeeded. Otherwise the IVP has failed. you wish to execute the Configurators [Y/N ]? y Host Configurator.... DECNIS Configurator.... DECNIS V4.0 Installation Verification Procedure completed successfully. Installation of NISAXP V4.0 completed at 15:15 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]NISAXP040.VMI_ the products to be processed from the next distribution volume set. VMSINSTAL procedure done at 15:16 Example Installation on OpenVMS VAX Load Host OpenVMS VAX Software Product Installation Procedure V6.2 is 27-OCT-1996 at 14:49. a question mark (?) at any time for help. you satisfied with the backup of your system disk [YES]? will the distribution volumes be mounted: VELA$DUA1:[NIS_ the products to be processed from the first distribution volume set. * installation options you wish to use (none): following products will be processed: V4.0 Beginning installation of NIS V4.0 at 14:49 Example Installation on an OpenVMS Load Host C-3 Restoring product save set A ... Product's release notes have been moved to SYS$HELP. version V4.0 will take approximately 45 minutes depending on hardware configuration. Network Integration Server V4.0 Installation Procedure. Digital Equipment Corporation 1991, 1996. All rights reserved. Rights: Use, duplication, or disclosure by the U.S. Government subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS or in FAR 52.227-19, or in FAR 52.227- III, as software is proprietary to and embodies the confidential technology of Equipment Corporation. Possession, use, or copying of this software media is authorized only pursuant to a valid written license from or an authorized sublicensor. should read the Release Notes immediately AFTER installing product. The release notes for the DECNIS are in a file NIS040.RELEASE_NOTES which is in the SYS$HELP directory. want to purge files replaced by this installation [YES]? want to run the IVP after the installation [YES]? 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. Restoring product save set B ... Restoring product save set C ... Files will now be moved to their target directories... the DECNIS V4.0 Installation Verification Procedure. Digital Equipment Corporation 1991, 1996. All rights reserved. will now be asked whether you wish to execute the Configurators. you answer YES, this procedure will execute the Host Configurator, by the DECNIS Configurator. Installation on an OpenVMS Load Host 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. you wish to execute the Configurators [Y/N ]? y Host Configurator.... DECNIS Configurator.... DECNIS V4.0 Installation Verification Procedure completed successfully. Installation of NIS V4.0 completed at 15:17 the products to be processed from the next distribution volume set. VMSINSTAL procedure done at 15:17 Example Installation on an OpenVMS Load Host C-5 D _____________________________________________________________ Files Installed on Digital UNIX Load Hosts Introduction This appendix lists the files installed on a Digital UNIX load host by the DECNIS installation procedure. __________________________________________________________ Pathname_and_File__________Description____________________ /etc/bootptab.default Default bootptab /usr/bin/ncl.nis400 NCL image /usr/lib/dnet/dec_elan_ DEC Vendor MIB mib.v27_txt /usr/lib/dnet/decrou_ncl Work file used for NCL checking /ncl/dictary.dat usr/lib/dnet/dtf/dtf.txt DECNIS Trace Facility (DTF) manual usr/lib/dnet/dtf/dtfaxp.a DTF for OpenVMS Alpha hosts usr/lib/dnet/dtf DTF for Digital UNIX hosts /dtfosf.tar usr/lib/dnet/dtf DTF for ULTRIX hosts /dtfultrix.tar /usr/lib/dnet/dtf DTF for OpenVMS VAX hosts /dtfvms.a usr/lib/dnet/dtf DTF for Windows NT hosts /dtfw32.zip /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 Files Installed on Digital UNIX Load Hosts D-1 __________________________________________________________ /usr/lib/dnet/nia400_ivp Installation verification procedure /usr/lib/dnet/nis040.releasRelease notes notes /usr/lib/dnet/nisfix040.relRelease 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/decnis_ SMDS configurator smds_config /usr/lib/dnet/nis_combine Shell script for combine utility /usr/lib/dnet/nis_ Event messages text events.txt /usr/lib/dnet/nis_ Example NCL Script example.ncl /usr/lib/dnet/mod_flsh Edit combined file utility /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_ System image images.dat usr/lib/dnet/nis_nchk NCL checking utility Installed on Digital UNIX Load Hosts __________________________________________________________ usr/lib/dnet/nis_atm_ ATM on DS3 lines NCL example ds3.ncl usr/lib/dnet/nis_atm_ ATM on E3 lines NCL example e3.ncl usr/lib/dnet/nis_atm_ ATM on OC3 lines NCL example oc3.ncl usr/lib/dnet/nis_atm_oc3_ ATM Classical IP on OC3 lines class_ip.ncl NCL example /usr/lib/dnet/nis_ Backup circuit NCL example backup.ncl /usr/lib/dnet/nis_dns_ IP services NCL example name_server.ncl /usr/lib/dnet/nis_icmp_ ICMP router discovery NCL rd.ncl example usr/lib/dnet/nis_ip_ IP multicast NCL example multicast.ncl /usr/lib/dnet/nis_ip_ IP pattern matching prioritiza- priory_patt.ncl tion NCL example /usr/lib/dnet/nis_ip_ IP standby MAC mode NCL example standby.ncl /usr/lib/dnet/nis_ipx_ IPX WAN link NCL example wan.ncl /usr/lib/dnet/nis_lat_ LAT pattern matching prioriti- priority_patt.ncl zation NCL example usr/lib/dnet/nis_pack_ IP packet filtering NCL example filt.ncl /usr/lib/dnet/nis_ospf_ OSPF NCL example minimum.ncl /usr/lib/dnet/nis_ospf_ OSPF NCL example multi_area.ncl /usr/lib/dnet/nis_ospf_ OSPF NCL example virtual.ncl /usr/lib/dnet/nis_ Prioritization NCL example priority.ncl Files Installed on Digital UNIX Load Hosts D-3 __________________________________________________________ /usr/lib/dnet/nis_ SMDS NCL example smds.ncl /usr/lib/dnet/nis_x25_ LAN/WAN relay NCL example lanwan_relay.ncl /usr/lib/dnet/nis_x25_ X.25 local relay NCL example local_relay.ncl /usr/lib/dnet/nis_x25_ X.25 remote relay NCL example remote_relay.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/nis040.sys DECNIS double system image /usr/lib/mop/nis040b.sys DECNIS system image (no console NCL) /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_ Combine utility manpages combine.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 Installed on Digital UNIX Load Hosts __________________________________________________________ /usr/share/dna/dict/ncl_ ATM connection management dna5_atm_connection_ module text file management.ms /usr/share/dna/dict/ ncl_ ATM multiprotocol encapsulation dna5_atm_multiprotocol_ module text file encap.ms /usr/share/dna/dict/ncl_ Bridge module text file dna5_bridge.ms /usr/share/dna/dict/ncl_ CHDLC module text file dna5_chdlc.ms /usr/share/dna/dict/ncl_ CSMA-CD module text file dna5_csmacd.ms /usr/share/dna/dict/ncl_ FDDI module text file dna5_fddi.ms /usr/share/dna/dict/ncl_ Frame relay module text file dna5_frbs.ms /usr/share/dna/dict/ncl_ Hardware module text file dna5_hardware.ms /usr/share/dna/dict/ncl_ HDLC module text file dna5_hdlc.ms /usr/share/dna/dict/ncl_ IP Services module text file dna5_ips.ms /usr/share/dna/dict/ncl_ LAPB module text file dna5_lapb.ms /usr/share/dna/dict/ncl_ MOP module text file dna5_mop.ms /usr/share/dna/dict Multiplexed Interface module /ncl_dna5_multiplexed_ text file interface.ms /usr/share/dna/dict/ncl_ NSP module text file dna5_nsp.ms /usr/share/dna/dict/ncl_ PPP module text file dna5_ppp.ms /usr/share/dna/dict/ncl_ Priority module text file dna5_priority.ms Files Installed on Digital UNIX Load Hosts D-5 __________________________________________________________ /usr/share/dna/dict/ncl_ Routing module text file dna5_routing.ms /usr/share/dna/dict/ncl_ Session module text file dna5_session.ms /usr/share/dna/dict/ncl_ SMDS module text file dna5_smds.ms /usr/share/dna/dict/ncl_ SNMP module text file dna5_snmp.ms /usr/share/dna/dict/ncl_ Supervisor module text file dna5_supervisor.ms /usr/share/dna/dict/ncl_ TCP module text file dna5_tcp.ms /usr/share/dna/dict/ncl_ X25 Access module text file dna5_x25_access.ms /usr/share/dna/dict/ncl_ X25 Protocol module text file dna5_x25_protocol.ms /usr/share/dna/dict/ncl_ X.25 Relay module text file dna5_x25_relay.ms /usr/share/dna/dict/ncl_ NCL help help.hlp__________________________________________________ Installed on Digital UNIX Load Hosts E _____________________________________________________________ Example Installation on a Digital UNIX Load Host This appendix contains an example installation of DECNIS software on an Digital UNIX load host. Throughout this appendix, text you type in is indicated by a bold typeface. -l . NIANIS400 subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DECNIS V3.1 for Digital UNIX you may choose one of the following options: 2) ALL of the above 3) CANCEL selections and redisplay menus 4) EXIT without installing any subsets your choices or press RETURN to redisplay menus. (for example, 1 2 4-6): 1 are installing the following optional subsets: DECNIS V3.1 for for Digital UNIX this correct? (y/n): y file system space required to install selected subsets: system space checked OK. DECNIS version 3.1 SSB Kit will take approximately 20 minutes install, depending on hardware configuration. Example Installation on a Digital UNIX Load Host E-1 Network Integration Server V3.1 Installation Procedure * * Digital Equipment Corporation. 1994. All rights reserved. * * Rights: Use, duplication, or disclosure by the U.S. * is subject to restrictions as set forth in subparagraph * of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR * Alt. III, as applicable. * * software is proprietary to and embodies the confidential * of Digital Equipment Corporation. Possession, use, or * of this software and media is authorized only pursuant to a * written license from Digital or an authorized sublicensor. * * * example installation log for this product is included in the * and Configuration manual. This log contains all the * displayed by this installation procedure. * * should read these notes and this log immediately AFTER installing * product, because it contains important information about how to * the DECNIS software. * * * Installation started at Thu 27 Oct 1996, 15:33:57 * * DECNIS Digital UNIX kit onto a OSF1 alpha system DECNIS specific files... original etc/bootptab file. V3.1 for Digital UNIX from . (disk) Working....Thu Oct 27 15:34:14 BST 1996 want to run the IVP after the installation? (y/n) [y]: Installation on a Digital UNIX Load Host Checking dates of profile files **** is up to date. is up to date. is up to date. is up to date. is up to date. Updating with new DECNIS NCL modules... old dictionary.... dictionary.... updated ncl_dna5_bridge.ms updated ncl_dna5_chdlc.ms updated ncl_dna5_csmacd.ms updated ncl_dna5_fddi.ms updated ncl_dna5_frbs.ms updated ncl_dna5_hardware.ms updated ncl_dna5_hdlc.ms updated ncl_dna5_lapb.ms updated ncl_dna5_mop.ms updated ncl_dna5_ppp.ms updated ncl_dna5_routing.ms updated ncl_dna5_x25_relay.ms updated ncl_dna5_snmp.ms updated ncl_dna5_smds.ms updated ncl_dna5_supervisor.ms updated ncl_dna5_tcp.ms updated ncl_dna5_priority.ms DECNIS NCL help updated into usr/share/dna/ncl_help.txt ---------------------------- Beginning DECNIS V3.1 Installation Verification Procedure (IVP) Copyright Digital Equipment Corporation 1994. All rights reserved. ...all component files for the DECNIS subset verified present. ---------------------------- version numbers of installed software... Software Image.............DECNIS V3.1 HOST Configurator..........DECNIS Host Configurator Version V3.1 DECNIS Configurator........DECNIS Configurator Version V3.1 Example Installation on a Digital UNIX Load Host E-3 a final check, the IVP now executes the Host Configurator, then DECNIS Configurator. each, press RETURN at the first screen, then select EXIT. NOT* proceed to configure your DECNIS at this stage. each Configurator, check that: o No error messages are reported o The help file is successfully read in by the Configurator. NOTE *************************** the above checks are successful, the IVP has succeeded. the IVP has failed. return when ready.. LOAD HOST CONFIGURATION DECNIS CONFIGURATION the image combine utility a sample ncl script a cmip file from the ncl script CMIP file from /usr/lib/dnet/nis_tmptmp.ncl... /usr/lib/dnet/nis_tmptmp.log script, profiles and compressed image Done - Image version 3.1 Successfully created the combined image... V3.1 SSB Kit Verification Procedure Completed Succesfully. DECNIS problem solving guide for Bookreader retained as usr/lib/dxbook/library.decw_bookshelf_old Problem Solving Guide available for Bookreader. ---------------------------- Notes ----- Installation on a Digital UNIX Load Host 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 update_type - the valid update types are flash_full, flash_part and network. 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 NIANIS400 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 ---------------------------- 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. nis040.release_notes in usr/lib/dnet These are the release notes for the DECNIS kit and may be printed or displayed on the screen. *********************************************************************** * * * NIANIS400 Installation Completed at Thu 27 Oct 1996, 15:40:06 * * * *********************************************************************** "DECNIS V3.1 for Digital UNIX" (NIANIS400) Example Installation on a Digital UNIX Load Host E-5 __________________________________________________________ Index DEC Network Integration _____________________ Server. router, 3-2, 3-3, See DECNIS , 6-3 DECdns, 2-7, 5-5 towers, 3-6, 6-6 lookups, 3-6, 6-6 Name server, 3-6, 6-7 namespace, 3-6, 3-11,_____________________ 6-7, 6-12 node name, A-3 7-1, use of by configurators, hosts, 3-6, 6-6, A-3 6-3, Decnet_register, 2-7, 5-6 DECNET_REGISTER_INIT 7-1 environment variable, loading, 2-7, 5-6 protocols, DECNIS definition, 6-5_____________________ steps to configure, 1-1 7-2 DECNIS configurator, 1-2 3-5, DECNIS Problem Solving file, Digital UNIX load hosts, 5-3 with OpenVMS load hosts, 2-4 DECNIS text-based with configurator, 4-1, 8-1 starting, 8-1 using, 4-1 to 4-4, 8-1 to 8-4_____________________ Default values, A-1 3-11, 6-2, Index-1 a router, 3-2, 3-7 F__________________________ 3-8, 6 an internal image, Files installed , 5-4 Digital UNIX load hosts, installed files D-1 to D-6 UNIX load hosts, OpenVMS load hosts, B-1 to B-5 load UNIX load hosts H ___________________________ installed, Hardware address, 3-3, 6-4, A-2 needed Help on, 5-1 DECNIS text-based procedure, configurator, 4-3 to 4-4, 8-3 to 8-4 on, keys used, 4-3 to 4-4, DECNIS 8-3 to 8-4 on, leaving, 4-3, 8-3 load-host load-host configurator, on, 3-10, 6-11 image 2-5 to 2-7, 5-4 I__________________________ 5-5 3-1 Image loaded, 2-5 3-5, 6-6, A-3 Image/CMIP/profile file. See combined file _____________________ Images for DECNIS, 2-4, 5-3 running Index numbers, 2-6, 5-5 3-11, Information required Digital UNIX load host messages installation, 5-1 UNIX load hosts, load-host configuration, 3-3 to 3-7, 6-3 to 6-7, load hosts, 2-4 A-1 to A-3 installation OpenVMS load host UNIX, E-1 to E-5 installation, 2-1 C-1 to C-5 Installation procedure NCL script files Digital UNIX load hosts, UNIX load hosts, 5-2 Installing load Digital UNIX load hosts, 5-1 to 5-8 (cont'd) Load-host configurator (cont'd) load to 2-10 using, 3-1 to 3-12, 6-1 image, 2-5, 5-4 to 6-12 address, A-2 Load-host data file, 3-11, 6-11 to 6-12 saving, 3-11, 6-12________________________ Loading from load host, 3-5, 6-5 in 4-2, 8-2 nonvolatile memory, 3-5, 6-5 in 8-3 to 8-4 protocols used, 3-1, 6-1 Local namespace, 2-7, 3-6, TOWER, 3-11, 5-5, 6-6, 6-7, 6-12________________________ use of by configurators, hardware 6-4, A-2 3-6, 6-6 Log file a configurator errors, a 3-11, 6-11 client 3-3, 5-7, 6-3, A-2 M ___________________________ hosts Management processor cards, 7-1 2-5, 5-3, 5-4 3-1, Menus 2-10 DECNIS configurator Main UNIX 7-2 Menu, 2-8, 5-7 load-host configurator configuration information Main Menu, 3-2, 3-3, 6-2, 6-3 UNIX 6-3 to 6-7 Modify a router, 3-2, 3-8 to 3-9, 6-2, 6-8 to 6-9 load to 3-7 MOD_FLSH program, 2-6 to 2-7, 5-4 to 5-5 A-2 MOP circuit, 3-4, 6-4, A-2 configurator, 1-2, 6-1 MOP loading, 3-1, 3-4, 3-11, 6-1, 6-3, 6-4, options, 3-2 6-12 on Digital UNIX MOP protocol, 3-1 load hosts, 6-2 MPC part numbers, 2-5, 5-4 on host, 3-2 Index-3 5-3, 5-4 O__________________________ 2-5 2-5 Online documentation 2-4, 2-5 Digital UNIX load hosts, load hosts, 2-10 5-2 to 5-3 OpenVMS load hosts, 2-3 _____________________ to 2-4 OpenVMS load hosts 3-6, 3-11, 6-6, files installed, B-1 to B-5 3-6, 3-11, 6-6, information needed to install on, 2-1 the DECNIS installing on, 2-1 to 2-7, 5-5 2-10 service, 2-7, 3-6, load information, 3-3 to , 6-6 3-7 3-6 starting DECNIS files, 3-6, configurator on, 4-1 , 3-8, 6-6, 6-8, 6-9 starting load-host deleted DECNIS, 3-7, configurator on, 3-2 OSF/1. information See Digital UNIX UNIX load hosts, P__________________________ load Part number for MPC, 2-5, 4-1 5-4 3-2 Phase IV address, 3-4, 6-5 5-3 Postinstallation 2-4 information 8-1 Digital UNIX load hosts, 6-2 3-7, 6-7 5-5 3-7, 6-7, OpenVMS load hosts, 2-7 Processor card, 3-4, 6-4 memory loading, R,_________________________ 6-5 3-5, 6-5 Registering the DECNIS in a 3-5, 6-5 namespace, 2-7, 5-5 3-8, 6-9 Release notes choice of, 3-10, Digital UNIX load hosts, 5-3 OpenVMS load hosts, 2-4 a router, 3-2, 3-9, 6-2, 6-9 to 6-10 U__________________________ UNIX load hosts, 7-2 Update a router, 3-2, 3-9________________________ to 3-10, 6-2, 6-10 to files 6-11 NCL Updating DECNIS software, CONTROL commands, 3-6, 6-6 2-8 to 2-9, 5-6 to 5-7 node, 3-6, 3-7, 6-7 V__________________________ VAXcluster installing on, 2-10________________________ Verifying the installation 6-1 Digital UNIX load hosts, 7-1, 5-7 of OpenVMS load hosts, 2-9 VMS load hosts. See OpenVMS load hosts Index-5