DEC_Network_Integration_Server________________ Installation and Configuration for OpenVMS and DIGITAL UNIX Order Number: AA-Q61BE-TE Revision/Update Information: This is a revised manual Software Version: DECNIS[TM] V4.1 First_Printing,_March_1994________________________________ Revised, September 1997 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, 1997. 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 ................................................. xv 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.1 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-Plus 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-8 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-9 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-10 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 II DIGITAL UNIX Load Hosts: Installation and Configuration Installing: DIGITAL UNIX Load Hosts 4.1 DIGITAL UNIX Background Information.......... 4-1 4.2 DIGITAL UNIX Installation Procedure.......... 4-2 4.3 DIGITAL UNIX Online Documentation............ 4-2 4.3.1 DECNIS Problem Solving Manual............ 4-3 4.4 The DECNIS V4.1 Software Images.............. 4-3 4.4.1 Which Internal Image Is Loaded?.......... 4-4 4.4.2 Deleting an Internal Image from the Double Image............................. 4-4 4.4.2.1 Load Host Loading or Part Nonvolatile Memory Loading......................... 4-4 4.4.2.2 Full Nonvolatile Memory Loading........ 4-5 4.5 After Installation........................... 4-5 4.5.1 Registering the DECNIS in DECdns......... 4-5 4.5.2 Configuring a DECNIS for the First Time..................................... 4-6 v 4.5.3 Updating a Previously Installed DECNIS... 4-6 4.5.4 Verifying the Installation............... 4-7 4.5.5 Deleting Installed Files................. 4-7 4.5.6 Checking Your Terminal Setup............. 4-8 4.5.6.1 Type of Terminal....................... 4-8 4.5.6.2 Terminal Setup......................... 4-8 4.5.7 Reporting Problems....................... 4-8 the Load-Host Configurator: DIGITAL UNIX Load 5.1 What Is the Load-Host Configurator?.......... 5-1 5.1.1 Definition of a Load Host................ 5-1 5.1.2 Load Protocols........................... 5-1 5.2 Before You Begin............................. 5-2 5.3 Starting the Load-Host Configurator.......... 5-2 5.4 Load-Host Configurator Menu Options.......... 5-2 5.5 How to Enter Load Information................ 5-3 5.6 Load Information............................. 5-3 5.6.1 Load Client Name ........................ 5-3 5.6.1.1 Finding the Load Client Name........... 5-4 5.6.2 Hardware Address......................... 5-4 5.6.2.1 Finding the Hardware Address........... 5-4 5.6.3 MOP Circuit (MOP Loading Only)........... 5-4 5.6.3.1 Finding the MOP Circuit Name........... 5-4 5.6.3.2 Requirement for MOP Circuit............ 5-4 5.6.4 IP Address (BOOTP Loading Only).......... 5-4 5.6.5 Phase IV Address......................... 5-5 5.6.6 Type of Loading.......................... 5-5 5.6.6.1 Definition of Nonvolatile (Flash) Memory................................. 5-5 5.6.6.2 Advantages of Nonvolatile Memory Loading................................ 5-5 5.6.7 Specifying a Dump File................... 5-6 5.6.8 Use of DECdns and the Local Namespace by the Configurators........................ 5-6 5.6.8.1 Background: the DECNIS and the DECnet-Plus (DECnet/OSI)Naming Services............................... 5-6 5.6.8.2 Generating KNOWN TOWER Commands........ 5-7 5.6.9 Node Name (Naming Service Users Only).... 5-7 5.6.10 Node Synonym (Naming Service Users Only).................................... 5-7 5.7 Delete a Router ............................. 5-7 5.7.1 Effect of Deleting....................... 5-8 5.8 Modify a Router ............................. 5-8 5.8.1 Information that Cannot Be Modified...... 5-8 5.8.2 Running the DECNIS Configurator After Modifying................................ 5-9 5.8.3 Modifying the Type of Loading............ 5-9 5.8.3.1 Results of Changing Back to Load Host Loading................................ 5-9 5.9 Restore a Router............................. 5-9 5.9.1 Automatic Restore........................ 5-10 5.10 Update a Router ............................. 5-10 5.10.1 Automatic Update......................... 5-10 5.10.1.1 Update: Full Nonvolatile Memory Loading................................ 5-10 5.10.1.2 Update: Part Nonvolatile Memory Loading................................ 5-11 5.10.1.3 Update: Load Host Loading.............. 5-11 5.11 Getting Help ................................ 5-11 5.12 Errors when Running the Load-Host Configurator................................. 5-11 5.13 The Load-Host Data File...................... 5-11 5.13.1 Saving the Load-Host Data File........... 5-12 5.14 What the Load-Host Configurator Does with Load Information............................. 5-12 Setting Up BOOTP on Load Hosts 6.1 Introduction................................. 6-1 6.2 Setting Up DIGITAL UNIX Systems as BOOTP Load Hosts........................................ 6-1 6.2.1 Basic Steps.............................. 6-1 6.3 Setting Up Non-DIGITAL UNIX Systems as BOOTP Load Hosts................................... 6-2 III Configuring the DECNIS vii the DECNIS Text-Based Configurator 7.1 Before You Start............................. 7-1 7.2 Starting the DECNIS Text-Based Configurator: OpenVMS Load Hosts........................... 7-1 7.3 Starting the DECNIS Text-Based Configurator: DIGITAL UNIX Load Hosts...................... 7-2 7.4 Configurator Keys............................ 7-2 7.5 Online Help.................................. 7-3 7.5.1 How to Get Online Help................... 7-4 7.5.2 Help on Fields and Menu Choices.......... 7-4 7.5.3 Help on the Configurator................. 7-4 7.5.4 Keys to Get Help......................... 7-4 Text-Based Configurator Sections 8.1 Identify the DECNIS Node..................... 8-1 8.2 Select Network Interface Cards............... 8-1 8.3 Configuration Options........................ 8-2 8.4 Routing...................................... 8-2 8.4.1 System IP Address........................ 8-2 8.5 Lines........................................ 8-2 8.6 X.25 Circuits................................ 8-3 8.6.1 Special Points About X.25 DA Circuits.... 8-4 8.7 Frame Relay Connections...................... 8-4 8.8 Bridge Filtering............................. 8-5 8.9 OSI Reachable Addresses...................... 8-5 8.10 IP Reachable Addresses....................... 8-5 8.11 PVCs......................................... 8-5 8.12 Groups....................................... 8-6 8.13 LLC2 ........................................ 8-6 8.14 X.25 Server Clients ......................... 8-6 8.14.1 Definitions of X.25 Gateway Systems and Client Systems........................... 8-6 8.14.2 Filters.................................. 8-7 8.15 X.25 Security................................ 8-7 8.16 Incoming Security for X.25 Server Clients ... 8-7 8.17 Outgoing Security for Client Systems ........ 8-8 8.18 Event Logging................................ 8-8 8.19 Database Sizing.............................. 8-9 8.20 NCL Script................................... 8-9 Using the DECNIS Text-Based Configurator 9.1 Introduction and Main Menu................... 9-1 9.1.1 The Sections............................. 9-1 9.1.2 The Options Menu......................... 9-2 9.1.3 Meaning of the Options in the Options Menu..................................... 9-2 9.2 Entering Information......................... 9-2 9.2.1 Selecting from a Menu.................... 9-2 9.2.2 Horizontal Menus......................... 9-3 9.2.2.1 Series of Horizontal Menus............. 9-4 9.2.3 Typing in Data........................... 9-5 9.3 Moving Within and Between Sections........... 9-5 9.3.1 Moving Forward Within a Section.......... 9-5 9.3.2 Moving Back Within a Section............. 9-5 9.3.3 Moving to a New Section.................. 9-6 9.3.4 Moving to a Previous Section............. 9-6 9.3.5 Restriction on Leaving a Section......... 9-6 9.4 What You Can Do from the Options Menu........ 9-6 9.4.1 Adding an Item........................... 9-6 9.4.2 Modifying a Completed Section............ 9-7 9.4.3 Deleting an Item......................... 9-7 9.4.4 Using the Sections Menu.................. 9-7 9.4.5 Saving an Incomplete Configuration....... 9-7 9.5 Exiting and Quitting the DECNIS Configurator................................. 9-8 9.5.1 Definition of Exiting.................... 9-8 9.5.2 How to Exit from the Configurator........ 9-8 9.5.3 Definition of Quitting................... 9-8 9.5.4 How to Quit the Configurator............. 9-8 9.6 Errors when Running the DECNIS Configurator................................. 9-9 Creating the Configuration Files 10.1 Introduction................................. 10-1 10.1.1 More About NCL Script Files.............. 10-2 10.2 Creating the Master NCL Script File.......... 10-2 10.2.1 Create NCL Script Section................ 10-2 10.2.2 How to Create the Master NCL Script File..................................... 10-3 10.2.3 Errors when Creating the NCL Script File..................................... 10-3 ix 10.3 User NCL Script Files........................ 10-3 10.3.1 Purpose of the User NCL Script Files..... 10-3 10.3.2 Why Use the User NCL Script Files?....... 10-4 10.3.3 User NCL Script File Names............... 10-4 10.3.4 General Recommendations for Editing User NCL Script Files......................... 10-4 10.3.5 Long NCL Commands........................ 10-5 10.4 Creating a Configuration Load File........... 10-5 10.4.1 Methods for Creating the CMIP File or the Combined File............................ 10-6 10.4.2 Creating the CMIP File Within the Configurator............................. 10-6 10.4.3 Creating a CMIP File After Exiting from the Configurator......................... 10-7 10.4.4 Creating the Combined File Within the Configurator............................. 10-7 10.4.5 Creating a Combined File After Exiting from the Configurator.................... 10-8 10.4.6 Creating a Combined File................. 10-8 10.5 DECNIS Data Files............................ 10-8 10.5.1 Saved Version of the DECNIS Data File.... 10-9 Your Configuration in the DECNIS Text-Based 11.1 Introduction................................. 11-1 11.2 How to Modify Your Configuration............. 11-1 11.2.1 Completing an Incomplete Configuration... 11-2 11.3 Steps to Take After Modifying a DECNIS Configuration................................ 11-2 11.4 Effects of Modifying a DECNIS Configuration................................ 11-3 11.5 Effects of Modifying Load-Host Information... 11-5 11.5.1 Steps to Take After Modifying a Load-Host Configuration............................ 11-5 11.5.2 How the DECNIS Configurator Uses Load-Host Information.................... 11-6 11.5.3 Load-Host Modifications Affecting DECNIS Configuration............................ 11-6 11.6 Copying and Modifying a Configuration........ 11-8 11.6.1 Before You Copy.......................... 11-8 11.6.2 Copying the Configuration to Another DECNIS................................... 11-8 11.6.3 Sections to Check........................ 11-10 IV Information Used in the Configurators Information Required for Load-Host Configuration 12.1 Dump File Names.............................. 12-3 Information Required for DECNIS Configuration V Appendixes Configuration and Load Files A.1 Files Created by the Configurators........... A-1 A.2 DECNIS Load Files............................ A-6 A.3 Location of DECNIS Load Files on DIGITAL UNIX BOOTP Load Hosts............................. A-8 A.3.1 Directory Used for Storing Load Files.... A-8 A.3.1.1 Softlinks Automatically Created........ A-8 A.3.2 Load files on Non-DIGITAL BOOTP Load Hosts.................................... A-8 A.3.3 File Names Required on DIGITAL UNIX BOOTP Load Hosts............................... A-9 Files 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 xi 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 Installed on DIGITAL UNIX Load Hosts D.1 Introduction................................. D-1 Installation on a DIGITAL UNIX Load Host DECdns and the Local Namespace with the DECNIS F.1 Introduction................................. F-1 F.2 Specifying the Use of a Naming Service....... F-2 F.3 DECdns or Local Namespace?................... F-2 F.4 Registering the DECNIS in a Namespace........ F-2 F.4.1 Requirements for Successful Registration............................. F-3 F.4.2 Errors When Registering the DECNIS in the Namespace................................ F-3 F.4.3 Adding Tower Sets to the DECNIS Entry.... F-3 F.4.4 Errors When Adding Tower Sets to the DECNIS Entry............................. F-4 F.5 Naming Service Error Log File................ F-4 F.6 Completing Name Service Registration......... F-4 F.6.1 Managing the DECNIS Before Registration Is Complete.............................. F-5 F.7 Swapping the DECNIS Hardware................. F-5 from a DECnet-VAX Phase IV Load Host G.1 Introduction................................. G-1 G.2 Procedure.................................... G-1 G.2.1 Hardware Address......................... G-3 G.2.1.1 Finding the Hardware Address........... G-3 G.2.1.2 Procedure.............................. G-4 G.2.1.3 Example................................ G-4 G.2.2 Example.................................. G-4 8-1 DECNIS Configurator Sections............. 8-1 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 Location of Online Information: DIGITAL UNIX..................................... 4-2 4-2 Images and Management Processor Cards.... 4-4 7-1 OpenVMS Configurator Keys................ 7-3 7-2 Keys Used to Get Help.................... 7-5 10-1 User NCL Script File Names............... 10-4 11-1 Effect of Modifying DECNIS Information... 11-3 11-2 Effect of Modifying Load-Host Information on DECNIS Information ................... 11-7 12-1 Load-Host Configuration Information: DECnet-Plus Load Hosts .................. 12-2 13-1 Configuration Information: DECNIS Node... 13-2 13-2 Configuration Information: Network Interface Cards ......................... 13-2 13-3 Configuration Information: Configuration Options.................................. 13-3 13-4 Configuration Information: Routing....... 13-6 13-5 Configuration Information: Lines......... 13-10 13-6 Configuration Information: Bridge Filtering................................ 13-27 13-7 Configuration Information: X25 Routing Circuits................................. 13-29 13-8 Configuration Information: Tunnel Circuits................................. 13-38 13-9 Configuration Information: Frame Relay Connections.............................. 13-40 xiii 13-10 Configuration Information: OSI Reachable Addresses................................ 13-44 13-11 Configuration Information: IP Reachable Addresses................................ 13-45 13-12 Configuration Information: PVCs.......... 13-46 13-13 Configuration Information: Groups........ 13-46 13-14 Configuration Information: LLC2.......... 13-47 13-15 Configuration Information: X.25 Server Clients.................................. 13-49 13-16 Configuration Information: Filters....... 13-50 13-17 Configuration Information: X.25 Security................................. 13-51 13-18 Configuration Information: Incoming Security for X.25 Server Clients ........ 13-51 13-19 Configuration Information: Outgoing Security for Client Systems ............. 13-53 13-20 Configuration Information: Event Logging.................................. 13-54 13-21 Configuration Information: Database Sizing................................... 13-56 A-1 DECNIS File Names on OpenVMS Systems..... A-2 A-2 DECNIS File Names on DIGITAL UNIX Systems.................................. A-4 A-3 Files Loaded from OpenVMS Load Hosts..... A-6 A-4 Files Loaded from DIGITAL UNIX Load Hosts.................................... A-7 A-5 File Names Required for DIGITAL UNIX BOOTP Loading............................ A-9 F-1 Naming Service Error Log Files........... F-4 G-1 Hardware Address Assignment.............. G-3 G-2 Examples of Hardware Address Assignment............................... G-4 _____________________________________________________________ Preface This manual explains how to: o Install the software for the DEC[TM] Network Integration Server (DECNIS) on OpenVMS[TM] and DIGITAL[TM] UNIX[[R]] systems. o Configure OpenVMS and DIGITAL UNIX systems so that they can downline load the DECNIS software. o Configure the DECNIS software, using 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. Refer to the clearVISN DECNIS Configurator User Guide for information about configuring the DECNIS on Windows 95/NT systems. Refer to the DECNIS Management manual for information about loading 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 DECnet[TM] routing o OSI[[R]] routing o IP routing (if using the Internet protocols) o X.25 (if using the CCITT X.25 protocols) xv o OpenVMS (if using an OpenVMS load host) o DIGITAL UNIX (if using a DIGITAL UNIX load host) Documentation Product Documentation o DEC Network Integration Server Introduction and Glossary o DEC Network Integration Server Management o DTF (DIGITAL Trace Facility) User Guide 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) o Network Information (supplied on line) This supplies profile information about all the public Packet Switching Data Networks that DIGITAL supports. 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 Network management documentation for the load-host operating system you are using. o X.25 Security manual This manual explains the underlying concepts of X.25 security. You can order this manual through your local DIGITAL office. o Bridge and Extended LAN Reference manual This manual provides a general description of bridging and extended LANs. You can order this manual through your local DIGITAL office. 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 xvii The following conventions are used in this manual: Key names are shown enclosed to indicate that you press a key on the keyboard. This symbol indicates that you press the key at the same time as you press another key. For example, , , and so on. Italics This indicates variable information. decnis This indicates that you should substitute the node name of the DECNIS. If you are using 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 and run the DECNIS text-based configurator. You use this configurator to set up your DECNIS as a bridge /router. Refer to the manual DECNIS Management for information about loading the DECNIS, and managing it once it is loaded. ________________________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 4 software 2 Make a note of the Chapter 12 information you will need when running the load-host configurator 3 Run the load-host Chapter 3 and Chapter 5 configurator and enter the required information 4 Make a note of the Chapter 13 information you will need when running the DECNIS text-based configurator 5 Run the DECNIS text- Chapter 7 to Chapter 9 based configurator and enter the required information 6 Create the DECNIS Chapter 10 configuration files 7 Downline load the DECNIS Management configured software onto the DECNIS hardware _____unit_________________________________________________ Part I _____________________________________________________________ OpenVMS Load Hosts: Installation and Configuration This part describes how to install the DECNIS software and run the load-host configurator on OpenVMS load hosts. 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 configura- tor to configure DECnet-Plus for OpenVMS load hosts for downline loading to the DECNIS. 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-Plus 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-Plus 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 NIS041 device-name OPTIONS N On OpenVMS Alpha hosts: $ @SYS$UPDATE:VMSINSTAL NIS041 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:NIS041.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.1 Software Image The DECNIS software image, NIS041.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 NIS041.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 Chapter 10. 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 NIS041_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 Section 7.2. 3. Create a load file, as described in Chapter 10. Installing: OpenVMS Load Hosts 2-7 4. Load the DECNIS, as described in the manual DECNIS Management. 5. 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 Section 7.2. 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 Management. 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-Plus (formerly 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-Plus 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 Management for more informa- tion. 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-Plus 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 Section 11.5 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. the Load-Host Configurator: OpenVMS Load Hosts 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. 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. Using the Load-Host Configurator: OpenVMS Load Hosts 3-9 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 7.5 for details. 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 Configurator: OpenVMS Load Hosts 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. Section 2.5.1 describes how the load-host configurator decides whether to register the DECNIS in the local or DECdns namespace. Using the Load-Host Configurator: OpenVMS Load Hosts 3-11 Part II _____________________________________________________________ DIGITAL UNIX Load Hosts: Installation and Configuration This part describes how to install the DECNIS software and run the load-host configurator on DIGITAL UNIX load hosts. It also describes how to configure UNIX systems for BOOTP loading. It contains the following chapters: o Chapter 4 describes how to install the DECNIS software on DIGITAL UNIX load hosts. o Chapter 5 describes how to configure DIGITAL UNIX load hosts for downline loading to the DECNIS. o Chapter 6 describes additional steps needed to set up DIGITAL UNIX load hosts for BOOTP loading. 4 _____________________________________________________________ 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 Alpha V3.1 (or later). software For BOOTP/TFTP loading, subset OSFCLINET031 DECnet/OSI for DIGITAL UNIX [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 4-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 4-1 lists the online information contained in the documentation kit. You can edit and print the text files if you wish. Table_4-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/nis041.release_ notes (continued on next page) DIGITAL UNIX Load Hosts Table 4-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 4-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.1 Software Images The DECNIS software image, NIS041.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 4-2 for the part numbers of the management processor cards. Installing: DIGITAL UNIX Load Hosts 4-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 4-2: Table_4-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 nis041.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 4.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 Chapter 10 for details. 2. Run the program MOD_FLSH, giving the name of the combined file: # /usr/lib/dnet/mod_flsh nis041client-name.sys where client-name is the client name of the DECNIS. 3. Follow steps 2 and 3 in Section 4.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. 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. Installing: DIGITAL UNIX Load Hosts 4-5 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 6.2.1 for details. 2. Run the load-host configurator, as described in Chapter 5. 3. Run the DECNIS text-based configurator, as described in Section 7.3. 4. Create a load file, as described in Chapter 10. 5. Load the DECNIS, as described in the manual DECNIS Management. 6. 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 5.10. 2. Start the DECNIS text-based configurator, as described in Section 7.3. 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 the DECNIS systems, as described in the manual DECNIS Management. Verifying the Installation To verify the installation, enter the following: # setld -v NIANIS410 Deleting Installed Files To delete the files installed by the installation procedure, enter: # setld -d NIANIS410 Installing: DIGITAL UNIX Load Hosts 4-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 4.5.6.1, and set up the terminal as described in Section 4.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 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 5 _____________________________________________________________ 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 5-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 6.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 5-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-Plus (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 Management for more informa- tion. the Load-Host Configurator: DIGITAL UNIX Load Hosts 5-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 4.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-Plus (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 5-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 Section 11.5 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 5-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 5.10.1.1 to Section 5.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 5.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 7.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 5-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 5.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 4.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 6 _____________________________________________________________ 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 6.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 6-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 5. 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 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 Chapter 10 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 Part III _____________________________________________________________ Configuring the DECNIS This part describes how to start and use the DECNIS text- based configurator, and create configuration files. It contains the following chapters: o Chapter 7 describes how to start the DECNIS text-based configurator on supported load hosts. o Chapter 8 gives an overview of the sections in the DECNIS text-based configurator. o Chapter 9 describes how to use the DECNIS text-based configurator. o Chapter 10 describes how to create the configuration files. o Chapter 11 describes how to modify a DECNIS configura- tion in the DECNIS text-based configurator. 7 _____________________________________________________________ Starting the DECNIS Text-Based Configurator This chapter describes: o How to start the DECNIS text-based configurator. o The keys you can use. o How to get online help. Before You Start Before you start, check that you have done the following: o Set up your terminal as described in Section 2.5.6 and Section 4.5.6. o Run the load-host configurator. You must do this before you run the DECNIS text-based configurator. Starting the DECNIS Text-Based Configurator: OpenVMS Load Hosts 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 Text-Based Configurator 7-1 the DECNIS Text-Based Configurator: DIGITAL UNIX Hosts 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 Keys Table 7-1 shows the keys you can use to enter and change information, and to move through the configurator sections. the DECNIS Text-Based Configurator Table_7-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)________________ Online Help You can get online help when running the load-host configurator and the 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. Starting the DECNIS Text-Based Configurator 7-3 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 7-2 lists the keys you can use to get Help, or to leave Help. the DECNIS Text-Based Configurator Table_7-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______________________________ Starting the DECNIS Text-Based Configurator 7-5 8 _____________________________________________________________ DECNIS Text-Based Configurator Sections When you run the DECNIS text-based configurator, you go through a series of sections, each corresponding to a type of information used for configuration. Sections 8.1 to 8.20 describe the purpose of each section in the configurator. Figure 8-1 gives an overview of the sections. Identify the DECNIS Node In this section, you choose which DECNIS to configure. The screen displays a menu of the DECNIS hardware units listed in the load-host data file. These are the DECNIS systems previously set up with the load-host configurator. In the menu, each DECNIS is designated by a load client name. This is a name entered during load-host configuration. It is used simply to identify the DECNIS for the purpose of downline loading and upline dumping. Select Network Interface Cards In this section, you indicate which type of Network Interface Card will occupy each slot on the DECNIS hardware unit. You can find the types of card supported on your DECNIS in the System Support Addendum (SSA) for your DECNIS. DECNIS Text-Based Configurator Sections 8-1 Options In this section, you choose whether you want to use: o Internet Protocol (IP) routing o Bridging o X.25 gateway functions o Special X.25 gateway options o VCP (Vitalink[[R]] Communications Protocol) You also supply other basic information. In this section, you provide information to set up the DECNIS for OSI routing, DECnet routing and IP routing. The information you are asked for depends on the options you have selected in the Configuration Options section. For example, you are only asked for IP information if you selected IP routing in Configuration Options. System IP Address If you supplied an IP address in the load-host configura- tor, the DECNIS will use it as a system IP address. All IP packets transmitted by the DECNIS must contain a source IP address. The DECNIS uses the system IP address as the source IP address for any IP packets that do not have their own source IP address. You must set up at least one line in this section. A line corresponds to a DECNIS hardware port. The lines you configure can be used for: o DECnet routing o IP routing protocols: - Integrated IS-IS (only if the DECNIS is running the Phase V routing algorithm at one or both levels - RIP Text-Based Configurator Sections - EGP (only if the DECNIS is a Level 2 router) - OSPF o NetWare IPX routing (only CSMA/CD, FDDI, VCP, PPP or CHDLC lines) o AppleTalk routing (only CSMA/CD, FDDI or VCP lines) o X.25 routing circuits (only synchronous lines) o X.25 gateway switched virtual circuits (only syn- chronous lines) o LLC2 communications (only CSMA/CD or FDDI lines) o Bridging ports, on the following Network Interface Cards and lines: - For local bridging: CSMA/CD or FDDI lines. - For remote bridging on W622 cards: HDLC, PPP, CHDLC or VCP lines. - For remote bridging on W614 and W618 cards: HDLC, PPP or CHDLC lines. o Frame relay channels (only on W622 cards) X.25 Circuits If you selected X.25 as the protocol for any of the lines, you are asked if you want to set up X.25 routing circuits. You can use these circuits for any or all of the following: o DECnet routing o IP routing o Connecting to another OSI domain, using static addresses o Connecting to another IP network, using static addresses There are four types of X.25 circuit: o Static Outgoing, to call a DTE on a DECnet router. o Static Incoming, to receive calls from a DTE on a DECnet router. DECNIS Text-Based Configurator Sections 8-3 o Permanent, to connect to a DECnet Phase IV system, using a Permanent Virtual Circuit (PVC). o Dynamically Assigned (DA), to connect to DTEs in other OSI routing domains and/or other IP networks. Each circuit defines a link between specified DTEs on the DECNIS and a DTE on another system. Special Points About X.25 DA Circuits Note that: o You can only create X.25 DA circuits on the DECNIS if it is a Level 2 router. o For every DA circuit to an OSI domain, you must set up an OSI reachable address (see Section 8.9). o For every DA circuit to an IP host, subnet or network, you must set up an IP reachable address (see Section 8.10). o You can set up DA circuits regardless of whether the DECNIS is using the link state (Phase V) or the routing vector (Phase IV) algorithm. Relay Connections In the Lines section, you can set up a line as a frame relay channel-that is, a physical connection to a frame relay network. In this section, you create frame relay connections on the frame relay channels. Frame relay connections are virtual circuits that operate over a frame relay channel. You must create these connections in order to be able to use a channel. On the DECNIS, you can create up to 32 frame relay connections on each frame relay channel. You can use a frame relay connection for DECnet Phase IV, OSI IP and IPX routing, and for bridging. Text-Based Configurator Sections Bridge Filtering In this section, you define the way the DECNIS does bridge filtering. You can specify that the DECNIS only forwards named protocol types, or that it only blocks named protocol types. This is the only type of filtering you can specify in the configurator. For information about other kinds of bridge filtering, see the DECNIS Management manual. OSI Reachable Addresses In this section, you can specify static routes to other OSI routing domains. You only see this section if you have specified Level 2 routing for the DECNIS. You must set up an OSI reachable address for each X.25 Dynamically Assigned (DA) circuit with an OSI template that you have set up. IP Reachable Addresses In this section, you can specify static routes to other IP hosts, subnets or networks. You must set up an IP reachable address for each X.25 Dynamically Assigned (DA) circuit with an IP template that you have set up. PVCs In this section, you can set up nonrouting Permanent Virtual Circuits (PVCs). A PVC is a permanent association between two specific DTEs. Two DTEs connected by a PVC can communicate without the need for call clearing or call setup. Complete this section only if you have subscribed to this facility from a PSDN. DECNIS Text-Based Configurator Sections 8-5 If a DTE belongs to a Closed User Group (CUG), it can communicate freely with remote DTEs that are also members of that CUG. Its communications with DTEs outside the group may be restricted, depending on your PSDN subscription options. Complete this section only if you have subscribed to this facility from a PSDN. LLC2 is a data link protocol which enables the X.25 packet-level protocol to run over an ISO 8802-2 LAN, rather than a synchronous line. On the DECNIS, LLC2 links use CSMA/CD or FDDI ports. Normally, you only set up the DECNIS to use LLC2 if you want the DECNIS to act as a CONS LAN/WAN relay. When acting as a CONS LAN/WAN relay, the DECNIS switches calls between LLC2 systems on the LAN and one or more PSDNs. The LLC2 systems must be capable of running the ISO 8802-2 Class II protocol over the ISO 8802-3 protocol. If you want to use LLC2, you must set up an LLC2 DTE for each remote system you want to connect to on the LAN. Server Clients X.25 server clients identify Client systems using the DECNIS system as an X.25 gateway. You must set up X.25 server clients if you want Client systems to be able to use the DECNIS as an X.25 gateway. Definitions of X.25 Gateway Systems and Client Systems An X.25 gateway is a Connector system allowing Client systems to connect to a PSDN or communicate across an X.25 point-to-point link. Examples of Client systems are VAX[TM] P.S.I. Access systems and DEC X.25 for ULTRIX Gateway Client systems. You do not need to set up X.25 server clients for systems on the network that are only using LLC2 to communicate with the DECNIS. Text-Based Configurator Sections Filters You must set up at least one filter to associate with each X.25 server client. A filter is a mechanism for matching incoming calls to Client systems. Each filter contains a list of characteristics corre- sponding to fields in an incoming call request packet. You assign values to the characteristics you want matched. If the characteristics in an incoming call match those listed in a filter, then the call is passed to the server client associated with that filter. X.25 Security In this section, you specify whether or not you want to set up X.25 security. You only see this section if you are using the X.25 gateway function. If you choose to set up X.25 security, you will need to define X.25 security in detail for incoming and/or outgoing calls; see Section 8.16 and Section 8.17. If you choose not to set up X.25 security, the configura- tor will set up open security. This means that the DECNIS will: o Accept all incoming calls, provided that they match a filter that is in use. o Allow all outgoing calls from any of the Client systems using the DECNIS to any remote DTE. If you set up open security, you do not see the other security sections described below. Incoming Security for X.25 Server Clients You use incoming X.25 security to prevent unauthorized incoming calls to either or both of the following: o X.25 server clients served by the DECNIS. o PVCs set up on the DECNIS. You only set up incoming security if you are using the X.25 gateway function. DECNIS Text-Based Configurator Sections 8-7 To set up incoming security, you specify the remote DTEs that you expect to send calls to X.25 server client systems. You also specify the type of access: ALL, NONE or REMOTE CHARGE. If setting up PVC security, you specify remote DTEs that are using DECNIS PVCs. In this case, the only types of access are ALL or NONE. You are only asked to supply the remote DTEs that have ALL access; any you do not supply have NONE. Security for Client Systems You use outgoing X.25 security to prevent unauthorized outgoing calls from either or both of the following: o Client systems using the DECNIS. o PVCs set up on the DECNIS. You only set up outgoing security if you are using the X.25 gateway function. In this section, you specify Client systems using the DECNIS. You also specify the type of access they should have to remote DTEs: ALL, NONE or REMOTE CHARGE. If setting up PVC security, you specify local DECNIS PVCs. In this case, the types of access are ALL or NONE. Logging Event logging is used to monitor your system and help in problem solving. In this section, you may set up event streams and event sinks. An event stream contains events generated by the DECNIS. An event sink is a node to which event streams are sent. The configurator produces event streams with a standard, predefined set of events. You cannot alter these event streams within the configurator. To alter the event streams, you modify the user NCL script files produced by the configurator. Text-Based Configurator Sections Database Sizing In this section, you can adjust the amount of memory resources allocated to DECNIS database components The routing database on the DECNIS is split into a number of components that interoperate to provide routing information. Each component has a value which specifies how much memory is allocated to it. The configurator provides a default value for each component. This section allows you to change those values. Note that if you increase some values, you may need to reduce others, so as not to use up the total amount of memory. NCL Script When you have entered all your configuration information, the configurator creates an NCL script using this information. Refer to Chapter 10 for details. DECNIS Text-Based Configurator Sections 8-9 9 _____________________________________________________________ Using the DECNIS Text-Based Configurator This chapter describes how to run the DECNIS text-based configurator. You should read Chapter 7 before you read this chapter. Introduction and Main Menu When you start the DECNIS text-based configurator, you will see first the copyright screen, and then a brief explanation of the configurator. Press . The Main Menu appears: Create a new configuration Modify an existing configuration Exit from this procedure If you are configuring a DECNIS for the first time, choose Create a new configuration. You then see the first configurator sections. The Sections The DECNIS text-based configurator is divided into sections, each corresponding to a logical group of information. Each section contains a series of screens on which you enter information. Using the DECNIS Text-Based Configurator 9-1 The Options Menu When you complete the last screen in a section, the screen displays an Options Menu. For example: Meaning of the Options in the Options Menu The following list gives a brief explanation of each option in Options Menus. o Continue to new section takes you to the next uncompleted section. o Add lets you set up an item. For example, an additional X.25 routing circuit. o Modify lets you change information previously entered. o Delete lets you delete an item set up previously. o Sections Menu takes you to a menu of completed sections. If you select a section, you go to the Options Menu for that section. o Save the current configuration lets you save your configuration so far. o Save the current configuration and EXIT is the same as Save, except that when the configuration is saved, you exit from the configurator. Information This section describes how to enter information in the DECNIS configurator. Selecting from a Menu On some screens, you select from a menu. For example: 1. Move the cursor to the item you want, using the up or down arrow keys. 2. Press . the DECNIS Text-Based Configurator Horizontal Menus Some screens have a horizontal menu: 1. Move the cursor to the item you want, using the left or right arrow keys. 2. Press . Using the DECNIS Text-Based Configurator 9-3 Series of Horizontal Menus A more complicated example of horizontal menus is in the Network Interface Card section. Here, you select from a series of horizontal menus, as shown in the following example screen: On each line, you do the following: 1. Move the cursor to the card you want, using the left or right arrow key. 2. Press . The cursor moves to the first column on the next line. 3. Repeat for every line. Changing a Selection To change a selection on a previous line, use the up arrow key to get to the line. You can then use the left or right arrow key to move to a new selection. Restrictions on Leaving a Line If you have moved the cursor horizontally on a line, you must press before you can move to another line, or move to the next screen. For example, on line 6, you move the cursor from None to W622. You then decide to move back to line 5 to change your previous selection. You cannot do this until you have pressed on line 6. the DECNIS Text-Based Configurator Typing in Data On some screens, you type information into a field. For example: Type data into the field, and press . Horizontal Scrolling Usually, when you type in data, you can see the entire field. However, sometimes the maximum length you are allowed to type in is too long to fit into the field - for example, a node name, which may be up to 400 characters. In such cases, the field horizontally scrolls as you enter data. Horizontal scrolling only works if the keyboard is in "Insert" mode, not if it is in "Overstrike" mode. The words "Insert" or "Overstrike" appear in the upper righthand corner of the screen. To change between modes press . Moving Within and Between Sections The next sections describe how you can move within and between configurator sections. Moving Forward Within a Section When you have filled in the required fields on a screen, a new screen automatically appears. You cannot move forward until you have completed the required fields. If the fields are filled in already, or are optional, you can move to the next screen by pressing . Moving Back Within a Section To move back within a section, press . You can move backwards only as far as the first screen of the section. To get to another section, select Go to Sections Menu from any Options Menu. Then select a section. Using the DECNIS Text-Based Configurator 9-5 Moving to a New Section From the Options Menu, choose: Continue to new section You move to the first screen of the next section you have not seen. If you have completed all the sections, you move to the final section, Create NCL Script. If you have modified previously completed sections, always use this option after you have finished making your changes. Moving to a Previous Section You can move to any section previously completed. This includes optional sections you previously chose to skip. From the Options Menu, choose: Go to Sections Menu You see a menu listing the completed sections. When you select a section, you go to the Options Menu for that section. Restriction on Leaving a Section You cannot jump to the Options Menu from the middle of a section, even if the section was previously completed. You must go through all the screens. If the section is complete, you can move quickly through the screens, by pressing . You Can Do from the Options Menu Adding an Item You use Add to create several of the same type of item-for example, lines, X.25 circuits, reachable addresses. From the Options menu, choose: Add an item You go to the first screen on which you can enter data. the DECNIS Text-Based Configurator Modifying a Completed Section You can change information previously entered. From the Options Menu, choose: Modify an item You go to the first screen on which you can enter data. All screens will display the information previously entered. Deleting an Item You can delete an item previously created. From the Options Menu, choose: Delete an item Using the Sections Menu You use the Sections Menu to: o Go back to a section you previously completed. o Go back to a section you previously chose to skip. o Go to the NCL Script section. This section only appears if you have completed all other sections. When you select a section from the Sections Menu, you go to the Options Menu for that section. The only exception is when you select the NCL Script section. In that case, you go to the first screen of the section. Saving an Incomplete Configuration You can save a configuration without completing it. To do this, select either of the following from any Options Menu: o Save the current configuration. This saves the information you have entered so far, and leaves you on the Options Menu. o Save the current configuration and EXIT. This saves the information you have entered so far, and then returns you to the operating system. Both options save your configuration information to a special data file. They do not create a new NCL script file. See Section 10.5 for details. Using the DECNIS Text-Based Configurator 9-7 Once you have saved your incomplete configuration, you can complete it by using the Modify option; see Section 11.2.1. and Quitting the DECNIS Configurator To leave the DECNIS configurator, you can either exit or quit. Definition of Exiting Exiting means that the configurator saves all the informa- tion you have entered since starting the configurator and then returns you to the operating system. How to Exit from the Configurator You can save your configuration and exit at any of the following points: o On any Options Menu, by selecting Save the current configuration and EXIT. o In the NCL Script section, after you have created an NCL script file. o In the NCL Script section, after you have created a CMIP file. Definition of Quitting Quitting means that: o You leave the configurator and return to the operating system. o The configurator does not save any information you have entered since the last time you saved your configuration or created an NCL script file. How to Quit the Configurator To quit the DECNIS text-based configurator, press . This will delete all of the information you have entered since the last time you selected a Save option, or created an NCL script file. the DECNIS Text-Based Configurator Errors when Running the DECNIS Configurator If there are any errors when you are running the DECNIS text-based configurator, they will be recorded in the following log files: o On OpenVMS systems: MOM$SYSTEM:NIS_DECNIS.LOG o On DIGITAL UNIX systems: /usr/lib/dnet/nis_decnis.log Using the DECNIS Text-Based Configurator 9-9 10 _____________________________________________________________ Creating the Configuration Files Introduction When you finish configuring the DECNIS, you need to do the following: 1. Create a master NCL script file. See Section 10.2. This is a text file holding the commands needed to configure your DECNIS. You create this within the DECNIS text-based configurator. 2. As an option, edit the user NCL script files. See Section 10.3. These are empty NCL script files. You use them to add NCL commands to modify your configuration (for example, if you want to add facilities that are not in the configurator). 3. Create a binary configuration file. See Section 10.4. This is the file that will be downline loaded to the DECNIS. This chapter describes these files, how to create them and how they are used. This chapter also describes the DECNIS data files. These are private files created by the DECNIS text-based configurator. Each holds a configuration for a DECNIS. See Section 10.5 for details. Creating the Configuration Files 10-1 More About NCL Script Files The DECNIS text-based configurator uses the information you enter, together with system defaults, to create an initialization file for the DECNIS. This initialization file is a text file of Network Control Language (NCL) commands, known as the NCL script file. This file contains the commands necessary for configuring the DECNIS. The NCL script file produced by the DECNIS text-based configurator is known as the master NCL script file. In addition, the first time the DECNIS is configured, the configurator generates three user NCL script files. You can enter additional NCL commands in the user NCL script files. the Master NCL Script File You create a master NCL script file in the final section in the configurator, Create NCL Script. Create NCL Script Section Requirement Before you can go to the Create NCL Script section, you must complete all the configurator sections. This means that for each section, you must do one of the following: o Supply the required information on the screens. o Select No on the introduction screen, to say that you want to skip that section. How to Reach the Create NCL Script Section Once you have completed all the configurator sections, you will go to the Create NCL Script section if you select either of the following: o Continue to a new section from any Option Menu. o NCL Script from any Sections Menu. The Create NCL Script section will not appear on the Sections Menu unless you have completed all the sections. the Configuration Files How to Create the Master NCL Script File In the Create NCL Script section, follow these steps: 1. The first menu asks you to select an option: Create an NCL Script Go to Sections Menu 2. Select Create an NCL Script. Only select Go to Sections Menu if you want to modify any information you have already entered. Errors when Creating the NCL Script File If the configurator cannot create the master NCL script file, a failure message appears at the foot of the screen, and the cursor stays on the option Create an NCL Script. You must correct the problem before reselecting the option. User NCL Script Files The user NCL script files are generated by the config- urator the first time a DECNIS is configured. When they are first generated, they are empty files. The master NCL script file contains calls to the user NCL script files. Purpose of the User NCL Script Files The purpose of the user NCL script files is to allow you to change your DECNIS configuration without editing the master NCL script file. Edit the user NCL script files if you want to: o Change default information that you cannot change from within the configurator, for example, timer values. o Set up facilities that you cannot set up within the configurator, for example, setting up the DECNIS as a CONS LAN/WAN Relay. Creating the Configuration Files 10-3 Why Use the User NCL Script Files? The master NCL script file is recreated whenever you run the DECNIS text-based configurator. If you edit the master NCL script file, and then rerun the configurator, any changes you have made will be lost. If you insert additional NCL commands in the user NCL script files instead, your changes will be preserved. User NCL Script File Names Table 10-1 lists the user NCL script file names. In the table, client-name is the load client name of the DECNIS. See Section A.1 for the full file specifications of these files. Table_10-1_User_NCL_Script_File_Names_____________________ File Names: OpenVMS and Where Called in Master NCL DIGITAL_UNIX_____Contain_______Script_File________________ NIS_client- CREATE After standard entities name_EXTRA_ commands have been created CREATE.NCL NIS_client- SET commands After standard entities name_EXTRA_ have been set SET.NCL NIS_client- ENABLE After standard entities name_EXTRA_ commands have been enabled ENABLE.NCL________________________________________________ General Recommendations for Editing User NCL Script Files Follow these recommendations: o Do not edit the master NCL script file. o Do not delete the user script files, even if you will not use them. The master NCL script file contains calls to the user script files. The CMIP file will not compile if the user script files are not present. the Configuration Files Long NCL Commands The maximum input for NCL commands is as follows: o On OpenVMS systems, 1024 characters o On DIGITAL UNIX systems, 2048 characters The DECNIS text-based configurator may generate NCL commands that exceed this maximum length, if you provide sufficient input for certain configuration options. If this happens, the command will fail. This failure will be reported in the configurator log file. To correct this problem, you will need to edit the NCL master script file and replace the long command with several separate commands. Example You can replace this long NCL command in the NCL script file: set routing circuit L602-3-1 - alternative subnet addresses - {{ address = 1.1.50.50, mask = 255.255.255.0 }, - {address = 1.1.50.51, mask = 255.255.255.0 }} by the following separate commands: add routing circuit L602-3-1 - alternative subnet addresses - {{ address = 1.1.50.50, mask = 255.255.255.0 }} add routing circuit L602-3-1 - alternative subnet addresses - {{ address = 1.1.50.51, mask = 255.255.255.0 }} Creating a Configuration Load File Before you can load the DECNIS software, you must compile the NCL script and user NCL files into a loadable configuration file. This can be either a separate CMIP file or a combined file. o A CMIP (Common Management Information Protocol) file is the binary, loadable version of the NCL script files. It can be loaded as a separate file, together with the software image and profile files. Creating the Configuration Files 10-5 o A combined file consists of the CMIP file, software image and profile files combined into one file. Create this file if you want the DECNIS to reload all files from its own nonvolatile (flash) memory. Requirement to Create CMIP or Combined File Note that if you edit the user NCL script files, you must create a new CMIP or combined file before you reload the DECNIS. Methods for Creating the CMIP File or the Combined File There are two ways to create the CMIP file or the combined file: o From within the DECNIS text-based configurator. o After exiting from the configurator. Use this method if you want to edit the user NCL script files. Creating the CMIP File Within the Configurator You can create a CMIP file in the DECNIS text-based configurator only if you requested load-host loading in the load-host configurator. If you requested nonvolatile memory loading, go to Section 10.4.4. To create a CMIP file in the DECNIS text-based configura- tor, follow these steps: 1. Go to the Create NCL Script section. 2. Create the NCL script file. 3. After the NCL script file is created, the following menu is displayed: Create a CMIP file from the NCL script Return to Sections Menu Return to Main Menu Exit from the configurator 4. Select Create a CMIP file. the Configuration Files Creating a CMIP File After Exiting from the Configurator To create a CMIP file after exiting from the configurator, follow these steps: 1. In the Create NCL Script section of the configurator, create an NCL script file. 2. On the CMIP file menu, select Exit from the configura- tor. 3. Edit the user NCL script files if you wish, as described in Section 10.3. 4. Enter the command to create a CMIP file: o On OpenVMS load hosts: $ @SYS$MANAGER:NIS$SCRIPT_COMPILE NIS_client-name.NCL o On DIGITAL UNIX load hosts: # /usr/lib/dnet/nis_script_compile nis_client-name where client-name is the DECNIS load client name) Creating the Combined File Within the Configurator You can create a combined file in the DECNIS text-based configurator only if you requested nonvolatile memory loading in the load-host configurator. If you requested load-host loading, go to Section 10.4.2. To create a combined file in the DECNIS text-based configurator, follow these steps: 1. Go to the Create NCL Script section of the DECNIS text- based configurator. 2. Create the NCL script file. 3. After the NCL script file is created, the following menu is displayed: Create a combined image/CMIP/profile file Return to Sections Menu Return to Main Menu Exit from the configurator 4. Select Create a combined image/CMIP/profile file. Creating the Configuration Files 10-7 Creating a Combined File After Exiting from the Configurator To create a combined file after exiting from the configurator, follow these steps: 1. Create a CMIP file, either within the configurator, or as described in Section 10.4.3. 2. Run the combine procedure, as described in Section 10.4.6. Creating a Combined File To combine the software image, CMIP file and profile files into a single combined file, enter the following command: o OpenVMS load hosts: $ @SYS$MANAGER:NIS$COMBINE.COM NIS041 client-name o DIGITAL UNIX load hosts: # /usr/lib/dnet/nis_combine nis041 client-name where client-name is the load client name of the DECNIS. Data Files The DECNIS text-based configurator saves each DECNIS configuration in its own DECNIS data file. When you modify a configuration, the DECNIS text-based configurator uses the data file to show the data previously entered. This data file is independent of any NCL script files or CMIP files. The DECNIS data file name is: NIS_client-name.DAT where client-name is the load client name of the DECNIS. For the full specification of this file, see Section A.1. The DECNIS data file is also used for saving an incomplete configuration; see Section 9.4.5. Do not delete the DECNIS data files. You must have a data file in order to use the DECNIS text-based configurator to modify a configuration or complete an incomplete configuration. the Configuration Files Saved Version of the DECNIS Data File When the DECNIS text-based configurator creates a new DECNIS data file, it saves the old one, with a different file name extension. Normally, the previous DECNIS data file is saved with the file name: NIS_client-name.BAK However, if you install a new version of DECNIS software, and use the DECNIS configurator to modify an existing configuration, the configurator saves the previous DECNIS data file with a different file name: NIS_client-name.DAT_Vnn where:client-name is the load client name for the DECNIS. nn is the version number of the previous version of DECNIS software. Refer to Table A-1 and Table A-2 for the full file specifications. Creating the Configuration Files 10-9 11 _____________________________________________________________ Modifying Your Configuration in the DECNIS Text-Based Configurator Introduction This chapter describes how to modify a completed configuration in the DECNIS text-based configurator. How to Modify Your Configuration You can use the DECNIS text-based configurator to modify an existing configuration. Follow these steps: 1. Start the DECNIS text-based configurator, as described in Chapter 7. 2. Select Modify an existing configuration from the Main Menu. 3. The screen shows a list of load client names. Select the DECNIS you wish to reconfigure. 4. The screen shows the Sections Menu. Select a section to modify. 5. The screen shows the Options Menu for that section. You can add, delete, or modify information in that section. 6. To make changes to another section, select Go to Sections Menu from any Options Menu. Then select a section. 7. When you have finished making changes, create the NCL script file. You will go to the Create NCL Script section if you do either of the following: o Select Continue to new section from any Options Menu. o Select NCL Script from the Sections Menu. Your Configuration in the DECNIS Text-Based Configurator 11-1 8. When you reach the Create NCL Script section, follow the instructions in Section 10.2. Completing an Incomplete Configuration If you have saved an incomplete configuration, and then want to complete it, follow these steps: 1. Start the DECNIS text-based configurator, as described in Chapter 7. 2. Select Modify an existing configuration from the Main Menu. 3. The screen shows a list of load client names. Select the DECNIS you want. You will go to the Options Menu for the next section you need to complete. 4. Complete the section, by selecting Add, Configure or Modify, as appropriate. 5. When you have completed the section, select Continue to new section from the Options Menu. You will go to the next section you need to complete. 6. Repeat steps 4 and 5 until the configurator takes you to the NCL Script section. 7. Create an NCL script, as described in Section 10.2.2. to Take After Modifying a DECNIS Configuration Sometimes, if you delete or modify information in one section, it will change or delete information in another section. To make sure that you have entered all necessary information, do the following: 1. After you have made a modification, finish the section you are in. 2. Select Continue to new section on the Options Menu. This will always take you to the next uncompleted or unseen section. 3. If it takes you to another Options Menu, complete the section by selecting Add, Configure or Modify, as appropriate. Your Configuration in the DECNIS Text-Based Configurator 4. Select Continue to new section on every Options Menu until you arrive at the NCL Script section. Effects of Modifying a DECNIS Configuration Table 11-1 lists the modifications and deletions that have an important effect on the rest of your configuration. Table_11-1__Effect_of_Modifying_DECNIS_Information________ In this Modification__section___Affects_these_sections:___________ Change type Network Lines, X25 Circuits, OSI and IP of Network Interface Reachable Addresses, PVCs, Groups, Interface Cards LLC2 - Deletes all information for Card in a lines/DTEs on the previous Card slot Change from Routing Routing-Deletes IP route Level 1 to propagation information Level 2 Lines, X25 Circuits, Reachable Addresses- You may need to add information, as more functions are available to Level 2 routers Change from Routing Routing-Deletes IP route Level 2 to propagation information and Level Level 1 2 specific information Lines - Deletes Level 2 specific information, such as Level 2 cost, interphase links X25 Circuits-Deletes DA circuits OSI Reachable Addresses-Deletes all information IP Reachable Addresses-Deletes all IP reachable addresses for DA circuits (continued on next page) Your Configuration in the DECNIS Text-Based Configurator 11-3 Table_11-1_(Cont.)_Effect_of_Modifying_DECNIS_Information_ In this Modification__section___Affects_these_sections:___________ Change Routing Routing-Deletes route propagation routing information. Changing from Phase algorithm V only to Phase IV only deletes Phase V area addresses Lines-Changing from Level 2, Phase V to Level 2, Phase IV deletes interphase links Change from Lines Lines-Deletes information about X.25 to DTEs and DTE Classes for the line another X25 Circuits-Deletes X.25 routing protocol circuits for the line Reachable Addresses (OSI or IP)- Deletes reachable addresses for circuits using the line PVCs-Deletes PVCs using the line CUGs-Deletes CUGs using the line Change to Lines Lines-Deletes all HDLC/PPP circuit X.25 from information another Reachable Addresses (OSI or IP)- protocol Deletes reachable addresses for the circuit using the line Deleting a Lines Reachable Addresses (OSI or IP)- line (except Deletes all reachable addresses X.25) for the circuit using the line Deleting an Lines Lines - Deletes all DTEs/DTE X.25 line Classes for the line X25 Circuits-Deletes X.25 routing circuits using the line Reachable Addresses-Deletes reachable addresses for circuits using the line PVCs - Deletes PVCs using the line ________________________CUGs-Deletes_CUGs_using_the_line__ Your Configuration in the DECNIS Text-Based Configurator Effects of Modifying Load-Host Information If you modify information in the load-host configurator, the modifications may affect or even invalidate informa- tion entered in the DECNIS text-based configurator. For this reason, always rerun the DECNIS text-based configurator after changing the load-host configuration for a DECNIS. o If DECNIS information has been deleted, you will need to reenter it. o If DECNIS information has not been deleted, you will simply need to rerun the configurator. Follow the steps in Section 11.5.1. Steps to Take After Modifying a Load-Host Configuration This section describes how to update the DECNIS configura- tion after changing load-host information. 1. Exit the load-host configurator. 2. Run the DECNIS configurator. 3. Select the Modify option from the Main Menu. 4. Select the load client name for the DECNIS that you have just modified in the load-host configurator. 5. You will now see a list of sections. Select any section. 6. On the Options Menu for the section, select Continue to new section. 7. If the DECNIS text-based configurator has been able to update the DECNIS configuration automatically, you will go to the NCL script section. Go to step 10. 8. If the DECNIS text-based configurator cannot update the DECNIS configuration automatically, you will go to the Options Menu of a section where information has been deleted. Go to step 9. 9. Follow these steps: o If you are on the Routing Options Menu, select Modify. Your Configuration in the DECNIS Text-Based Configurator 11-5 If you are on any other Options Menu, select Add, to set up new items, for example, event streams. o Enter the required information. o When you have finished modifying, select Continue to new section from the Options Menu. o If you go to an Options Menu for another section, repeat this step. 10.In the NCL Script section, follow the instructions on the screen. How the DECNIS Configurator Uses Load-Host Information The DECNIS text-based configurator uses the information you entered during load-host configuration to find out: o The DECNIS hardware units set up for loading. o The DECNIS hardware type for each hardware unit. o The DECNIS Phase IV address (if present). o The DECNIS system IP address (if present). o Whether or not the DECNIS configurator will use naming service namespaces to find addressing information. This load-host information affects the information you enter during DECNIS configuration. Load-Host Modifications Affecting DECNIS Configuration Table 11-2 lists the modifications in load-host con- figuration that will affect or invalidate your DECNIS configuration. Your Configuration in the DECNIS Text-Based Configurator Table 11-2 Effect of Modifying Load-Host Information on ____________DECNIS_Information____________________________ Change to Load-Host Effect on DECNIS Configuration____Configuration_________What_You_Need_to_Do Changing Changes the CREATE Rerun the DECNIS Hardware SESSION CONTROL text-based Address and KNOWN TOWER command configurator, /or Phase IV for the DECNIS as described in address in the master NCL Section 11.5.1 script Deleting Invalidates Phase Rerun the DECNIS the Phase IV IV routing on the text-based address DECNIS configurator. Reenter information in the Routing section Entering Allows selection of Rerun the DECNIS the Phase IV Phase IV routing for text-based address (where Level 1 routers, and configurator. there was none of Phase IV routing Reenter information previously) at both levels for in the Routing Level 2 routers section Changing IP Changes the DECNIS Rerun the DECNIS Address system IP address text-based in the master NCL configurator, script as described in Section 11.5.1 Changing from Deletes the Rerun the DECNIS BOOTP loading system IP address text-based to MOP only previously set up configurator. loading in the load-host Reenter system configurator IP address in the Routing section Changing from The DECNIS IP Rerun the DECNIS MOP only address that you text-based loading to enter during load- configurator BOOTP loading host configuration replaces the system IP address previously entered during DECNIS configuration Your Changing Deletes all Rerun the DECNIS between Use information in the text-based of a naming following sections: configurator. service and X.25 Server Clients Reenter the Nonuse of a Event Logging information naming service Incoming Security _________________Outgoing_Security________________________ and Modifying a Configuration You may want to use similar configurations for several DECNIS systems, for example, if they have identical hardware configurations. One way to do this by copying an existing configuration and then modifying it. This section describes how you do this. Note that in the instructions: o The DECNIS system from which you are copying the configuration is called the first DECNIS. o The system to which you are copying is called the second DECNIS. Before You Copy Before you can copy a configuration, you need to do the following: 1. On a load host, install the DECNIS software, as described in the installation chapter for your load host. 2. Configure both the first DECNIS and the second DECNIS for loading. To do this, run the load-host configurator and set up downline loading details, as described in the installation chapter for your load host. 3. Configure the first DECNIS, as follows: o Run the DECNIS text-based configurator, and configure the DECNIS. o Create an NCL script (and a CMIP file, if you wish). o Select Exit from the configurator. Copying the Configuration to Another DECNIS To copy the configuration so that it applies to the second DECNIS, follow these steps: 1. Copy the DECNIS data file for the first system to a new file. In the file name of the new file, substitute the load client name of the second system for that of the first system. Your Configuration in the DECNIS Text-Based Configurator For example, the load client name is SOUTH1 for the first DECNIS and NORTH2 for the second DECNIS. On an OpenVMS system, use this command: $ COPY SYS$COMMON:[MOM$SYSTEM]NIS_SOUTH1.DAT - _$ SYS$COMMON:[MOM$SYSTEM]NIS_NORTH2.DAT Refer to Appendix A for the location and name of the DECNIS data file on all supported load hosts. 2. Start the DECNIS configurator. 3. Select Modify an existing configuration from the Main Menu. 4. Select the load client name of the second DECNIS. In the example above, this would be NIS_NORTH2.DAT. 5. Now, modify the configuration so that it is correct for the second DECNIS: o From the DECNIS Node Options Menu, select Go to Sections Menu. o Select the first section to be modified. ________________________Note ________________________ You must modify the configuration. The addresses entered for the system you copy from will not be correct for the system you copy to. _____________________________________________________ o When you reach the Options Menu, select the Sections Menu, and select another section to modify. o When you have finished modifying, select Continue to Next Section from any Options Menu. This will take you to the NCL Script section. Your Configuration in the DECNIS Text-Based Configurator 11-9 Sections to Check Be sure to check the addressing information in the following sections: o Routing o Lines and DTEs o X.25 Circuits (if configured) o Tunnel Circuits (if configured) o X.25 Server Clients (if configured) o Event Logging o Incoming Security (if configured) o Outgoing Security (if configured) It is safest to go through each section in turn, beginning with Network Interface Cards. Modifying Your Configuration in the DECNIS Text-Based Configurator Part IV _____________________________________________________________ Information Used in the Configurators This part contains the following chapters: o Chapter 12 summarizes the information required for load-host configuration on DECnet-Plus for OpenVMS and DECnet-Plus for DIGITAL UNIX load hosts. o Chapter 13 lists the information required to configure the DECNIS in the DECNIS text-based configurator. 12 _____________________________________________________________ Information Required for Load-Host Configuration Table 12-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 5 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 12-1 12-1 Load-Host Configuration Information: DECnet-Plus 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 12-1 (Cont.) Load-Host Configuration Information: DECnet- Plus 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 5.6.7 for the dump file name and location on DIGITAL UNIX load hosts. Information Required for Load-Host Configuration 12-3 13 _____________________________________________________________ Information Required for DECNIS Configuration This chapter lists the information you need to supply when you run the DECNIS text-based configurator. Tables 13-1 to 13-21 list this information. Write down your values in the last column, headed Your Value. Note that the tables list all the information required for all cases. The information you actually need to supply depends on your configuration. For example, you do not need to supply X.25 circuit information if you do not wish to use any X.25 routing circuits. 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 DECNIS Configuration 13-1 13-1 Configuration Information: DECNIS Node__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ Select the load R - client name (entered during load-host configuration) that identifies this DECNIS__________________________________________________________ 13-2 Configuration Information: Network Interface Cards__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ DECNIS slot listed on the screen: Select one of the R None Card card acronyms, or None (for an empty slot). Examples: W614, W618, W622, L601, L602, F621__________________________________________________________ Required for DECNIS Configuration 13-3 Configuration Information: Configuration Options_____________________________________________________________ R(equired) / Your Notes O(ptional)Default Value_____________________________________________________________ Internet Select Yes or No R - (IP) for X.25 Select Yes or No R - Bridging? Select Yes or No R - NetWare IPX Select Yes or No R - AppleTalk Select Yes or No R - DECNIS Select Yes or No R Yes a Bridging DECNIS have Select Yes or No R Yes license? X.25 Select Yes or No R No for: Nonrouting for PVCs; Closed User each Groups; LLC2 Priority Decimal digits. R for 128 (Bridging Range: 0-255. Bridging Determines whether the DECNIS will be the root bridge user name Protects use R - of Common Trace Facility (CTF). Up to 16 characters password Protects use of CTF. R - Up to 16 characters (continued on next page) Information Required for DECNIS Configuration 13-3 13-3 (Cont.) Configuration Information: Configuration Options__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ Management Protects use of NCL R - commands. Up to 16 characters Management Protects use of NCL R - commands. Up to 16 characters name Name of person O - managing the DECNIS. Max. 255 characters name Name for the DECNIS. O - Max. 255 characters Description of O - physical location of the DECNIS. Max. 255 characters Access Enter RO (read only) R - or RW (read and write) name(s) Additional community O - name(s). Max. 255 characters access Enter RO (read only) R if - or RW (read and com- write) munity name entered SNMP Select Yes or No R - (continued on next page) Required for DECNIS Configuration 13-3 (Cont.) Configuration Information: Configuration Options_____________________________________________________________ R(equired) / Your Notes O(ptional)Default Value_____________________________________________________________ address(es) IP address of R for - system(s) to which first the DECNIS will send ad- traps dress; O for the rest trap Community name R "public" name included in traps authenti- Select Yes or No R - failure _____________________________________________________________ Information Required for DECNIS Configuration 13-5 13-4 Configuration Information: Routing__________________________________________________________ R(equired)/ Your Notes O(ptional) Default Value__________________________________________________________ level Select Level 1 or R - Level 2[1] __________________________________________________________ 1 Router Information__________________________________________________________ Select Phase IV or R Phase Phase V IV Prefix IDP + optional R if Phase - preDSP of a Phase IV address IV compatible NSAP supplied address, in DEC format. Up to 22 digits. Example 1: 37:12345: Example 2: 49:: V area The IDP, preDSP R if no - (Phase (optional) Phase IV and Local Area address (up fields of an NSAP to three). address, in DEC Otherwise, O format. Up to 40 (up to two) digits. Example: 41:23456789:00-A5 for System IP address R if not - [2] for IP circuits entered with no IP address. during load- n.n.n.n (n is a host config- decimal number) uration RIP Select Yes or No R - Default Select Yes or No R Yes __________________________________________________________ 2 asked if you selected IP. (continued on next page) Required for DECNIS Configuration 13-4 (Cont.) Configuration Information: Routing_____________________________________________________________ R(equired)/ Your Notes O(ptional) Default Value_____________________________________________________________ 1 Router Information_____________________________________________________________ Select Yes or No R No RIP up RIP Yes or No R - address of n.n.n.n (n is a R - source[2] decimal number) of route IS-IS to RIP? RIP R No for to IS-IS? both RIP Select Yes or No R - if OSPF _____________________________________________________________ 2 Router Information_____________________________________________________________ Select one of: R - L1 Phase IV, L2 Phase IV L1 Phase IV, L2 Phase V L1 Phase V, L2 Phase IV L1 Phase V, L2 Phase V _____________________________________________________________ asked use IS-IS, you must run Phase V routing at one or both (continued on next page) Information Required for DECNIS Configuration 13-7 13-4 (Cont.) Configuration Information: Routing__________________________________________________________ R(equired)/ Your Notes O(ptional) Default Value__________________________________________________________ 2 Router Information__________________________________________________________ Prefix IDP + optional R if Phase - preDSP of a Phase IV address IV compatible NSAP supplied for address, in DEC load-host format. Up to 22 configura- digits. Example 1: tion 37:12345: Example 2: 49:: V area IDP, preDSP R if there - (if (optional), and is no Phase V) local area fields IV address. of an NSAP, in DEC Otherwise, O format. Up to 40 digits. Example: 41:23456789:00-A5 for System IP address R if not - [2] for IP circuits entered with no IP address. during load- n.n.n.n (n is a host config- decimal number) uration Select Yes or No R Yes Select Yes or No R Yes Select Yes or No R Yes Select Yes or No R Yes Default Select Yes or No R Yes __________________________________________________________ asked (continued on next page) Required for DECNIS Configuration 13-4 (Cont.) Configuration Information: Routing_____________________________________________________________ R(equired)/ Your Notes O(ptional) Default Value_____________________________________________________________ 2 Router Information_____________________________________________________________ Select Yes or No R No RIP up RIP Yes or No[2] R Yes address n.n.n.n (n is a R - each RIP decimal number) number (EGP Number of R - autonomous system to which DECNIS belongs. Range 1-65535 of route Choice depends on R No for protocols selected. all if Any or all of: IS- than one ISRIP; IS-ISEGP; protocol EGPRIP Select Yes or No R - if OSPF _____________________________________________________________ asked use IS-IS, you must run Phase V routing at one or both _____________________________________________________________ Information Required for DECNIS Configuration 13-9 13-5 Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ line to Select from list R - displaying all ports set up previously (see Table 13-2) (Lines Select one of: HDLC; R - NIC PPP; Frame Relay; X.25; CHDLC; VCP (Lines Select one of: HDLC; R - or W618 PPP; DDCMP[TM]; X.25; CHDLC (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ _____________________________________________________________ CSMA/CD and FDDI information_____________________________________________________________ name Max. 32 characters R port name circuit Select Yes or No R No system DECnet Select Yes or No R No following information only applies if you choose to supply DECnet information____________________________________________________________________ of routing Select Level 1 and 2 or R Level 2 only) Level 2 only 1 and Level 2 1 cost Decimal number from R 20 1-63 2 cost Decimal number from R 20 1-63 1 Decimal number from R 64 1-127 2 Decimal number from R 64 1-127 following information only applies if you selected IP routing____________________________________________________________________ RIP on this Select Yes or No R No EGP on this Select Yes or No R No (Level (continued on next page) Information Required for DECNIS Configuration 13-11 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ CSMA/CD and FDDI information__________________________________________________________ Circuit IP address. O (but - n.n.n.n (n is a decimal R on number) at least one CSMA /CD cir- cuit) mask n.n.n.n (n is a decimal R if Depends number). You can use ad- on the digits 255 to show dress subnet which part of the IP sup- class address is the network plied address. Example 1: 255.255.255.0: First three bytes are the network address. Last byte identifies the host. IP Alternative local O - (Only address(es) for this address circuit. n.n.n.n (n is a decimal number) n.n.n.n (n is a decimal O - mask number). See IP subnet mask for more details Only receive; Only R - send; Send and Receive (EGP AS number of an EGP R - neighbor (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ CSMA/CD and FDDI information_____________________________________________________________ address of n.n.n.n (n is a decimal R - neighbor number) only) following information only applies if you selected Bridging____________________________________________________________________ line as Select Yes or No R Yes port? name Create a name. Max. 32 R Port-n characters number Decimal number from R Lowest 1-15 avail- able The lower the cost, R 10 the more likely that the DECNIS will be the designated bridge. Decimal number from 0-255 following information only applies if you selected NetWare IPX____________________________________________________________________ NetWare Select Yes or No R - network Up to 8 hexadecimal R - digits of For CSMA/CD, select: R Ethernet Ethernet, 802.2, SNAP or Novell[[R]]. For FDDI, select 802.2 or SNAP (continued on next page) Information Required for DECNIS Configuration 13-13 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ CSMA/CD and FDDI information__________________________________________________________ update Number of seconds R 60 between periodic RIP and SAP updates on this circuit. Decimal integer in range 60- 65535 Select Yes to accept R - incoming NetBIOS broadcasts on this circuit information only applies if you selected AppleTalk _________________________________________________________________ Select Yes or No R - Network number plus O 0.0 network node ID. Format: for the number.node-id Range: 1-65279 for network number. 128-253 for node ID. The value 0.0 means there is no network address. Range of contiguous O - range AppleTalk network numbers. Format: number.number Range: 1- 65279 for each number. Example: 225-3000 (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ CSMA/CD and FDDI information_____________________________________________________________ Name of AppleTalk zone O - zone to be used for nodes with no preassigned zone or with an invalid zone name AppleTalk Name(s) of zones valid O - (if for this circuit zone (continued on next page) Information Required for DECNIS Configuration 13-15 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your __________________________________________________________alue_ HDLC information__________________________________________________________ name Max. 32 characters R Line name circuit Select Yes or No R No DECnet Select Yes or No R No information only applies if you choose to supply DECnet information_________________________________________________________________ The characters %x O - followed by an even number of up to 38 hex digits The characters %x O - followed by an even number of up to 38 hex digits 1 cost Decimal number from R 20 1-63 2 cost Decimal number from R 20 1-63 link Choose one of: Phase IV R No (only if Level 2 router; Phase inter- V routing V router running Phase phase 2) IV routing protocols at link Level 2; No interphase link (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ HDLC information_____________________________________________________________ IV areas Enter list of area R - by numbers. Example: 23, circuit[1] 30-35, 40 cost for Decimal number from R 20 IV areas 1-63 by Phase IV Enter list of area R - reachable numbers. Example: 10, DECNIS[1] 15-22, 41-45 cost for Decimal number from R 20 Phase IV 1-63 following information only applies if you selected IP routing____________________________________________________________________ RIP on this Select Yes or No R No EGP on this Select Yes or No R No (Level IP n.n.n.n (n is a decimal R for - number). IP address of RIP IP host to which this or EGP circuit connects. if no local IP ad- dress _____________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-17 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ HDLC information__________________________________________________________ IP Local address for this R for - circuit. n.n.n.n (n is RIP a decimal number). or EGP if no neigh- bor IP ad- dress subnet n.n.n.n (n is a decimal R if Depends number). You can use local on the digits 255 to show IP ad- subnet which part of the IP dress class address is the network sup- address. Example: plied 255.255.255.0: First three bytes are the network address. Last byte identifies the host. Only receive; Only R - send; Send and Receive (EGP AS number of an EGP R - neighbor of n.n.n.n (n is a decimal R - number) information only applies if you selected Bridging_________________________________________________________________ line Select Yes or No R No (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ HDLC information_____________________________________________________________ name Create a name. Max. 32 R Port-n characters number Decimal number from R Lowest 1-15 avail- able The lower the cost, the R 10 more likely the DECNIS is to be the designated bridge. Decimal number 0-255 Spanning Select Yes or No R Yes _____________________________________________________________ PPP information_____________________________________________________________ routing Select any or all of: R Yes for OSI routing; DECnet each Phase IV routing; IP routing; IPX routing (IP and IPX appear only if selected in Configuration Options) name Max. 32 characters R Line name circuit Select Yes or No R No system (continued on next page) Information Required for DECNIS Configuration 13-19 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ PPP information__________________________________________________________ DECnet Select Yes or No R No information only applies if you choose to supply DECnet information_________________________________________________________________ 1 cost Decimal number from R 20 1-63 2 cost Decimal number from R 20 1-63 link Choose one of: Phase IV R No (only Level 2 router; Phase inter- Phase V router running Phase phase at IV routing protocols at link 2) Level 2; No interphase link IV areas Enter list of area R - by numbers. Example: 23, 30-35, 40 for Decimal number from R 20 IV areas 1-63 by Phase IV Enter list of area R - reachable numbers. Example: 10, 15-22, 41-45 for Decimal number from R 20 Phase IV 1-63 __________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ PPP information_____________________________________________________________ information is the same as for HDLC circuits____________________________________________________________________ following information only applies if you selected NetWare IPX____________________________________________________________________ NetWare Select Yes or No R - network Up to 8 hexadecimal R - digits update Number of seconds R 60 between periodic RIP and SAP updates on this circuit. Decimal integer in range 60- 65535 NetBIOS Select Yes to accept R - incoming NetBIOS broadcasts on this circuit following information only applies if you selected Bridging____________________________________________________________________ this line Select Yes or No R No bridging name Create a name. Max. 32 R Port-n characters number Decimal number from R Lowest 1-15 avail- able (continued on next page) Information Required for DECNIS Configuration 13-21 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ PPP information__________________________________________________________ The lower the cost, the R 10 more likely the DECNIS is to be the designated bridge. Decimal number 0-255 Spanning Select Yes or No R Yes Select Yes or No R - frame __________________________________________________________ DDCMP information__________________________________________________________ name Max. 32 characters R Line name circuit Select Yes or No R No Select synchronous or R - asynchronous Select from 1200, 2400, R - if 4800, 9600, 19200, 38400, 56K, 64K, 128K modem Select Full modem R Full (only control or Data leads modem only control DECnet Select Yes or No R No (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ DDCMP information_____________________________________________________________ routing and Internet Protocol information are both the same as HDLC circuits _____________________________________________________________ Frame Relay information_____________________________________________________________ data Select CHDLC or PPP R - protocol Select one of: LMI R - /Joint; ANSI T1.617, Annex D; CCITT Q.933, Annex A _____________________________________________________________ X.25 information_____________________________________________________________ name Max. 32 characters R DTE- slot- port DTE DTE address. Max. 15 R - digits. Obtain from your PSDN channel Obtain from PSDN. R - Numbers or range(s) of numbers. Example: 1024-1048, 30 name Name of network profile R - for this DTE's PSDN. Supplied by DIGITAL. See also online Network Information (NI) control Select Yes or No R Yes _____________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-23 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ X.25 information__________________________________________________________ Select Yes or No R - sequence packet Decimal number (power R As in of 2). See profile and profile PSDN subscription packet Decimal number (power R As in of 2). See profile and profile PSDN subscription packet Decimal number (power R As in of 2). See PSDN profile subscription window Decimal number 1-127. R As in See PSDN subscription profile window Decimal number 1-127. R As in See PSDN subscription profile window Decimal number 1-127. R As in See PSDN subscription profile Select DTE or DCE R - size Decimal number. See R As in PSDN subscription profile Max. 32 characters. The R Profile name of a DTE Class to name which this DTE belongs __________________________________________________________ are only need to enter values if you have chosen flow control are only asked for this if the Profile is ISO8208 or (continued on next page) Information Required for DECNIS Configuration 13-5 (Cont.) Configuration Information: Lines_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ CHDLC information_____________________________________________________________ routing Select any or all of: R Yes for OSI routing; DECnet each Phase IV routing; IP routing; IPX routing (IP and IPX appear only if selected in Configuration Options) name Max. 32 characters R Line name circuit Select Yes or No R No system IP and NetWare IPX information are all the same as for PPP ____________________________________________________________________ information is the same as for HDLC circuits _____________________________________________________________ VCP information_____________________________________________________________ Turbo or Select type of Network R - Interface Card used by the Vitalink system to which the VCP line connects name Max. 32 characters R port name circuit Select Yes or No R No system (continued on next page) Information Required for DECNIS Configuration 13-25 13-5 (Cont.) Configuration Information: Lines__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ VCP information__________________________________________________________ IP, NetWare IPX and AppleTalk information are all the same as and FDDI circuits_________________________________________________________________ information is the same as for PPP circuits_________________________________________________________________ __________________________________________________________ Information Required for DECNIS Configuration 13-6 Configuration Information: Bridge Filtering_____________________________________________________________ R(equired) / Your Notes O(ptional)Default Value_____________________________________________________________ of Choose either: Enter R - protocols to be types forwarded or enter protocols to be blocked format List the protocol O - types types the DECNIS be forwarded should forward forwarded 802.2 List the protocol O - protocol types the DECNIS to be should forward forwarded 802.2 List the protocol O - format types the DECNIS types should forward be forwarded forwarded format List the protocol O - types types the DECNIS be blocked should block blocked 802.2 List the protocol O - protocol types the DECNIS to be should block (if chosen) (continued on next page) Information Required for DECNIS Configuration 13-27 13-6 (Cont.) Configuration Information: Bridge Filtering__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ SNAP List the protocol O - protocol types the DECNIS to be should block (if chosen)__________________________________________________________ Information Required for DECNIS Configuration 13-7 Configuration Information: X25 Routing Circuits_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ type Select one of: X25 R - Static Outgoing, X25 Static Incoming, X25 Permanent, X25 DA name Max. 32 characters R - _____________________________________________________________ X25 Static Outgoing Circuits_____________________________________________________________ name Max. 32 characters R circuit- name-out Class A local DTE Class R - containing the DTE this circuit will use for making calls. Max. 32 characters DTE address of remote R - address system to which this circuit will connect data The characters %x O %xff0000004445 followed by up to 254 hex digits 436e65742d444c4d size Decimal number (power O - of 2). See PSDN subscription size 1-127. See PSDN O - subscription Select Yes or No R No Incoming and O - Request outgoing baud rates for circuit. [incoming..outgoing] Example: [48..64] (continued on next page) Information Required for DECNIS Configuration 13-29 13-7 (Cont.) Configuration Information: X25 Routing Circuits__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ X25 Static Outgoing Circuits__________________________________________________________ DECnet Select Yes or No R No information only applies if you choose to supply DECnet information____________________________________________________________________ The characters %x O - followed by an even number of up to 38 hex digits The characters %x O - followed by an even number of up to 38 hex digits 1 cost Decimal number from R 20 1-63 2 cost Decimal number from R 20 1-63 Choose one of: Phase R No IV Level 2 router; interphase if Phase V router link Phase V running Phase IV state) routing protocols at at Level 2; No 2) interphase link IV Enter list of area R - numbers. Example: 23, 30-35, 40 __________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-7 (Cont.) Configuration Information: X25 Routing Circuits_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ X25 Static Outgoing Circuits_____________________________________________________________ cost Decimal number from R 20 Phase 1-63 areas by Phase Enter list of area R - areas numbers. Example: 10, by 15-22, 41-45 cost for Decimal number from R 20 Phase 1-63 areas[1] following information only applies if you selected IP routing______________________________________________________________________ RIP on Select Yes or No R No circuit? EGP on Select Yes or No R No circuit? IP n.n.n.n (n is a R for - decimal number). RIP IP address of IP host or EGP to which this circuit if no connects. local IP address _____________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-31 13-7 (Cont.) Configuration Information: X25 Routing Circuits__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ X25 Static Outgoing Circuits__________________________________________________________ IP Local address for R for - this circuit. n.n.n.n RIP (n is a decimal or EGP number). if no neigh- bor IP address subnet n.n.n.n (n is a R if Depends decimal number). local on subnet You can use the IP class digits 255 to address show which part sup- of the IP address plied is the network address. Example: 255.255.255.0: First three bytes are the network address. Last byte identifies the host. Only receive; Only R - send; Send and Receive AS number of an EGP R - neighbor of n.n.n.n (n is a R - decimal number) __________________________________________________________ X25 Static Incoming Circuits__________________________________________________________ (continued on next page) Information Required for DECNIS Configuration 13-7 (Cont.) Configuration Information: X25 Routing Circuits_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ X25 Static Incoming Circuits_____________________________________________________________ name Create a name. Max. R circuit- 32 characters name-IN size Decimal number 16- O - 4096 (power of 2) size 1-127. See PSDN O - subscription Incoming and O - Request outgoing baud rates for circuit. [incoming..outgoing] Example: [48..64] name Max. 32 characters R circuit- name-IN data The characters %x O %xff0000004445 followed by up to 254 hex digits 436e65742d444c4d data The characters %x O %xfffffffffffff followed by up to 254 hex digits ffffffffffffff Range of decimal O - numbers from 0 to 65535. Example: [[2..24]] DTE Calling address O - field of incoming call packet. Max. 15 digits Class DTE Class used for O - receiving call. Max. 32 characters (continued on next page) Information Required for DECNIS Configuration 13-33 13-7 (Cont.) Configuration Information: X25 Routing Circuits__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ X25 Static Incoming Circuits__________________________________________________________ DTE Called address field O - of incoming call packet. Max. 15 digits information is the same as for X25 Static Outgoing from the question, Supply DECnet routing information? onward __________________________________________________________ X25 Permanent Circuits__________________________________________________________ DTE to Select DTE name R - Max. 32 characters R - size Decimal number (power R Default of 2). See PSDN for DTE subscription size 1-127. See PSDN R Default subscription for DTE Channel assigned by R - PSDN DECnet Select Yes or No R No information only applies if you choose to supply DECnet information____________________________________________________________________ The characters %x O - followed by an even number of up to 38 hex digits (continued on next page) Information Required for DECNIS Configuration 13-7 (Cont.) Configuration Information: X25 Routing Circuits_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ X25 Permanent Circuits_____________________________________________________________ The characters %x O - followed by an even number of up to 38 hex digits 1 cost Decimal number from R 20 1-63 2 cost Decimal number from R 20 1-63 Choose one of: Phase R No choice IV Level 2 router; Interphase if Phase V router link Phase V running Phase IV state) routing protocols at at Level 2; No 2) interphase link IV Enter list of area R - numbers. Example: 23, 30-35, 40 circuit[1] cost Decimal number from R 20 Phase 1-63 areas by Phase Enter list of area R - areas numbers. Example: 10, by 15-22, 41-45 _____________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-35 13-7 (Cont.) Configuration Information: X25 Routing Circuits__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ X25 Permanent Circuits__________________________________________________________ for Decimal number from R 20 Phase 1-63 __________________________________________________________ X25 Dynamically Assigned (DA) Circuits__________________________________________________________ Select one of: OSI R - data; IP data; Both OSI and IP Max. 32 characters R circuit- name-DA- OSI Max. 32 characters R circuit- name-DA-IP Local DTE Class R - containing the DTE the circuit will use for making calls. Max. 32 characters Data The characters %xcc O %xcc followed by an even number of up to 252 hex digits Data The characters %x81 O %x81 followed by an even number of up to 252 hex digits __________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-7 (Cont.) Configuration Information: X25 Routing Circuits_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ X25 Dynamically Assigned (DA) Circuits_____________________________________________________________ size Decimal number 16- O - 4096 (power of 2). See PSDN subscription size Decimal number 1-127. O - See PSDN subscription Select Yes or No R No Incoming and O - Request outgoing baud rates for circuit. [incoming..outgoing] Example: [48..64] Filter Max. 32 characters R circuit- name-DA- OSI Filter Max. 32 characters R circuit- name-DA-IP Call data The characters %x81 O %x81 followed by an even number of up to 252 hex digits. Call data The characters %xcc O %xcc followed by an even number of up to 252 hex digits data The characters %xff O %xff followed by an even number of up to 252 hex digits. Same size as call data value (continued on next page) Information Required for DECNIS Configuration 13-37 13-7 (Cont.) Configuration Information: X25 Routing Circuits__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ X25 Dynamically Assigned (DA) Circuits__________________________________________________________ DTE Class used for O - receiving call. Max. 32 characters DTE Called address field O - of incoming call packet. Max. 15 digits__________________________________________________________ 13-8 Configuration Information: Tunnel Circuits__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ to send Select Yes or No R - circuit for NetWare IPX and AppleTalk Circuit Select Point-to- R - asked point or Broadcast IPX only circuit Max. 32 characters R - (continued on next page) Information Required for DECNIS Configuration 13-8 (Cont.) Configuration Information: Tunnel Circuits_____________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value_____________________________________________________________ IP Point-to-point: R - one address. Broadcast (NetWare IPX only): no restriction on the number of addresses. n.n.n.n (n is a decimal number) network Up to 8 hexadeci- R - mal digits_____________________________________________________________ Information Required for DECNIS Configuration 13-39 13-9 Configuration Information: Frame Relay Connections__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ frame Select from list R - channel of lines previously figured as frame relay channels Max. 32 characters R - Up to four decimal O - digits. Range: 16- 1007 Select any or all of: R Yes for OSI routing; DECnet each Phase IV routing; IP routing; IPX routing (IP and IPX appear only if selected in Configuration Options) DECnet Select Yes or No R No information only applies if you choose to supply DECnet information____________________________________________________________________ 1 cost Decimal number from R 20 1-63 2 cost Decimal number from R 20 1-63 (continued on next page) Information Required for DECNIS Configuration 13-9 (Cont.) Configuration Information: Frame Relay Connections_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ Choose one of: Phase R No choice IV Level 2 router; interphase if Phase V router link Phase V running Phase IV state) routing protocols at at Level 2; No 2) interphase link IV Enter list of area R - numbers. Example: 23, 30-35, 40 circuit[1] cost Decimal number from R 20 Phase 1-63 areas by Phase Enter list of area R - areas numbers. Example: 10, by 15-22, 41-45 cost for Decimal number from R 20 Phase 1-63 areas[1] following information only applies if you selected IP routing______________________________________________________________________ RIP on Select Yes or No R No circuit? EGP on Select Yes or No R No circuit? _____________________________________________________________ are (continued on next page) Information Required for DECNIS Configuration 13-41 13-9 (Cont.) Configuration Information: Frame Relay Connections__________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value__________________________________________________________ IP n.n.n.n (n is a R for - decimal number). RIP IP address of IP host or EGP to which this circuit if no connects. local IP address IP Local address for R for - this circuit. n.n.n.n RIP (n is a decimal or EGP number). if no neigh- bor IP address subnet n.n.n.n (n is a R if Depends decimal number). local on subnet You can use the IP class digits 255 to address show which part sup- of the IP address plied is the network address. Example: 255.255.255.0: First three bytes are the network address. Last byte identifies the host Only receive; Only R - send; Send and Receive AS number of an EGP R - neighbor (continued on next page) Information Required for DECNIS Configuration 13-9 (Cont.) Configuration Information: Frame Relay Connections_____________________________________________________________ R(equired) Notes /O(ptionalDefault Your Value_____________________________________________________________ address of n.n.n.n (n is a R - neighbor decimal number) only) following information only applies if you selected Bridging_______________________________________________________________________ this Select Yes or No R No bridging name Create a name. Max. R Port-n 32 characters number Decimal number from R Lowest 1-15 available The lower the cost, R 10 the more likely the DECNIS is to be the designated bridge. Decimal number 0-255 Select Yes or No R Yes minimum Select Yes or No R - frame if selected the data _____________________________________________________________ Information Required for DECNIS Configuration 13-43 13-10 Configuration Information: OSI Reachable Addresses__________________________________________________________ R(equired) / Your Notes O(ptionalDefault Value__________________________________________________________ name Select from list R - Max. 32 characters R - name All or leading R - Prefix digits of NSAP address, up to 40 digits. DEC, OSI or HRPF format. Examples: DEC format: 37:32655678:3214: HRPF format: /37326556783214 OSI format: 3732655678+3214 Cost of reaching R 20 cost the destination node. Decimal number, 1-63 Six pairs of R - of node hexadecimal to digits, with domain hyphen separating circuit each pair. Example: 08-00-2B- 65-BB-43 of DTE address R - node DA circuit __________________________________________________________ Information Required for DECNIS Configuration 13-11 Configuration Information: IP Reachable Addresses_____________________________________________________________ R(equired) / Your Notes O(ptional) Default Value_____________________________________________________________ used to Select from list R - Reachable Max. 32 characters R - name n.n.n.n (n is a R - to be decimal number). Address of host, subnet or network n.n.n.n (n is a R Depends mask decimal number) on subnet class Address of n.n.n.n (n is a R for - IP router decimal number) CSMA for X.25 /CD and FDDI; O for other proto- cols address of DTE address of R - IP router the next gateway DA only) on path. Up to 15 digits Reachable Cost of reaching the O 20 cost destination for this reachable address. Decimal number_____________________________________________________________ Information Required for DECNIS Configuration 13-45 13-12 Configuration Information: PVCs__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ Select from list R - Max. 32 characters R PVC-n number Decimal number. See R - PSDN subscription size Decimal number R Default (power of 2). See packet PSDN subscription size for DTE size Decimal number. See R Default PSDN subscription window size for DTE__________________________________________________________ 13-13 Configuration Information: Groups__________________________________________________________ R(equired) / Your Notes O(ptional)Default Value__________________________________________________________ name Max. 32 characters R GROUP-n type BCUG or CUG. See R BCUG PSDN subscription DTE you want to place in the Group, enter: Decimal number. See R - PSDN subscription DTE DTE address of R - other system in BCUG. Max. 15 digits __________________________________________________________ will __________________________________________________________ Information Required for DECNIS Configuration Table_13-14__Configuration_Information:_LLC2______________ R(equired) Information / Your Required__________Notes_______________O(ptionalDefault__Value For each LLC2 system you want to connect to: LAN device to Select CSMA/CD R - be used port from list LLC2 DTE name Max. 32 charac- R DTE-n ters LLC2 DTE Max. 15 digits R - address Logical channel Number(s) or R - range(s) range(s) of numbers, decided in consultation with remote system. Range: From 1 to 4095. Example: 1024- 1048, 30 Local LSAP 2 hex digits R 7E Remote LSAP 2 hex digits R 7E Remote MAC LAN hardware R - address address. Example: 08-00-2B-02-AA-23 Flow control Select Yes or No R No negotiation? Extended Select Yes or No R No packet sequence numbering? Minimum packet Decimal number. R 16 size[1] Power of 2 in range 16 to 4096 Maximum packet Decimal number. R 1024 size[1] Power of 2 in range 16 to 4096 Default packet Decimal number. R 128 size Power of 2 in range 16 to 4096 Minimum window Decimal number. R 1 size (pInformationRRequiredtfor2DECNIS Configuration 13-47 level)[1] Maximum window Decimal number. R 7 size (packet Range: 1 to 127 level)[1] Default window Decimal number. R 2 size (packet Range: 1 to 127 level) DTE class Max. 32 charac- R LLC2- ters CLASS- n [1]You_only_need_to_enter_values_if_you_have_chosen_flow__ control negotiation. __________________________________________________________ Information Required for DECNIS Configuration Table 13-15 Configuration Information: X.25 Server _____________Clients______________________________________ R(equired) Information / Your Required_________Notes_______________O(ptional)_Default_Value If you wish the configurator to use a naming service (DECdns_or_local)_to_find_X.25_server_client_addresses:___ Supply the following for each X.25 server client system: Server client Create a R CLIENT- name name. Max. 32 n characters Server client Node name of R - node name Client system associated with this X.25 server client. Max. 400 characters __________________________________________________________ If the configurator will not use a naming service (DECdns or_local)_to_find_Client_system_addresses:________________ Supply one and only one of the following for each Client system associated with an X.25 server client: NSAP address NSAP address O - of Client format. Example: system 41:23456789:00- A5:07-CA-4B-65- BB-43 Phase IV Phase IV address. O - address__________Example:_34.3____________________________ Information Required for DECNIS Configuration 13-49 Table_13-16_Configuration_Information:_Filters____________ R(equired) Information / Your Required_________Notes_______________O(ptional)_Default_Value Filter name Max. 32 charac- R - ters Priority Decimal number, R 1 0-65535 Incoming DTE Called address O - address field of incoming call packet. Max. 15 digits Call data The characters O - value %x followed by an even number of up to 254 hex digits Call data mask The characters O - %x followed by an even number of up to 254 hex digits Subaddress Range of decimal O - range numbers from 0 to 65535. Example: [[2..24]] DTE Class DTE Class used O - for receiving call. Max. 32 characters Sending DTE Max. 15 digits O - address Receiving DTE Max. 15 digits O - address Group name Max. 32 charac- O - ters Originally Max. 15 digits O - called address Redirect One of: Busy; O Not reason Out of order; spec- Systematic; Not ified specified Called address Hex digits O - Information extension value Called address Hex digits O - extension mask Called NSAP The characters O - %x, followed by an even number of up to 128 hex _________________digits___________________________________ 13-17 Configuration Information: X.25 Security_____________________________________________________________ R(equired) / Your Notes O(ptional) Default Value_____________________________________________________________ up X.25 Select Yes (to R Yes set up detailed X.25 security) or No (for open X.25 security)_____________________________________________________________ 13-18 Configuration Information: Incoming Security for X.25 Server Clients_____________________________________________________________ R(equired) / Your Notes O(ptional) Default Value_____________________________________________________________ Server client Select from list R - which to set up address The leading digits O - of remote of a DTE address, that can up to 15 digits the X.25 client's system only they pay for call (Remote access)[1] _____________________________________________________________ a address, or the leading digits of a DTE address to stand for DTEs with an address beginning with these digits. (continued on next page) Information Required for DECNIS Configuration 13-51 13-18 (Cont.) Configuration Information: Incoming Security for X.25 Server Clients__________________________________________________________ R(equired) / Your Notes O(ptional) Default Value__________________________________________________________ of The leading digits O - that can of a DTE address, X.25 up to 15 digits client's system pays for (All The leading digits O Wildcard that of a DTE address, (*)[2] allowed up to 15 digits the X.25 client's system (No __________________________________________________________ a or the leading digits of a DTE address to stand for with an address beginning with these digits. wildcard character (*) means all unspecified DTEs. If * to stand for DTEs with Remote Charge or All access, DTEs will have access except those that you specify __________________________________________________________ Information Required for DECNIS Configuration 13-19 Configuration Information: Outgoing Security for Client Systems_____________________________________________________________ R(equired) / Your Notes O(ptional) Default Value_____________________________________________________________ system on Node name. Max. R - to set up 256 characters to Enter either a R - Client Phase IV address (only if no or an NSAP address service) Name for Max. 32 characters R - system addresses of The leading digits O - systems of a DTE Address, can be called up to 15 digits this Client only if remote systems for the call Charge addresses of The leading digits O - that can of a DTE address, called by this up to 15 digits system who pays for call (All of PVCs that Max. 32 characters O - be accessed by Client system _____________________________________________________________ a address or the leading digits of a DTE address, to stand for DTEs with an address beginning with these digits. (continued on next page) Information Required for DECNIS Configuration 13-53 13-19 (Cont.) Configuration Information: Outgoing Security for Client Systems__________________________________________________________ R(equired) / Your Notes O(ptional) Default Value__________________________________________________________ The leading digits O Wildcard of a DTE address, (*)[2] be up to 15 digits by this system (No of PVCs that Max. 32 characters O - be accessed Client __________________________________________________________ a or the leading digits of a DTE address, to stand for with an address beginning with these digits. wildcard character (*) means all unspecified DTEs. If you the * to stand for DTEs or PVCs with Remote Charge or All then all DTEs or PVCs can be accessed except those that explicitly. __________________________________________________________ 13-20 Configuration Information: Event Logging__________________________________________________________ R(equired) / Your Notes O(ptional) Default Value__________________________________________________________ stream Max. 32 characters R - (continued on next page) Information Required for DECNIS Configuration 13-20 (Cont.) Configuration Information: Event Logging_____________________________________________________________ R(equired) / Your Notes O(ptional) Default Value_____________________________________________________________ _____________________________________________________________ you wish the configurator to use a naming service (DECdns or to find event sink addresses:_____________________________________________________________ the following for each event sink: sink name Node name R - of sink DECdns node name R Node or DECdns object name name _____________________________________________________________ the configurator will not use a naming service (DECdns or to find event sink addresses:_____________________________________________________________ one and only one of the following for each event sink: address of NSAP address O - sink format. Example: 41:23456789:00- A5:07-CA-4B-65-BB- 43 IV Phase IV address. O - of Example: 34.3 sink_____________________________________________________________ Information Required for DECNIS Configuration 13-55 13-21 Configuration Information: Database Sizing__________________________________________________________ R(equired) Your Notes /O(ptionDefault Value__________________________________________________________ system For each LAN circuit R 2480 displayed, enter the number of end systems on the LAN of router Number of routers R 170 directly connected to the DECNIS of Number of nonrouting R 5120 systems reachable over all DECNIS circuits of manual Systems in the local R 60 area that do not exchange adaptive routing information with the DECNIS of Unique NSAP addresses R 5280 1 routing in the local area of Level 1 Number of OSI Level 1 R 100 in local routers 1 average Average number of R 20 routers from which the DECNIS learns about nodes in the local area, multiplied by 10 of IP Number of IP subnets R 50 adjacencies to which the DECNIS is directly connected, plus neighbor IP addresses (continued on next page) Information Required for DECNIS Configuration 13-21 (Cont.) Configuration Information: Database Sizing_____________________________________________________________ R(equired) Your Notes /O(ptionDefault Value_____________________________________________________________ of IP Reachable Addresses R 200 reachable set up on the DECNIS (IP of Number of unique IP R 250 Level 1 subnet addresses in the (IP same area as the DECNIS area con- Average number of R 20 (IP routers from which the DECNIS learns about each IP host within the local area, multiplied by 10 of Maximum number of R 500 external IP destinations the (IP DECNIS will learn from protocols other than Integrated IS-IS the DECNIS is a Level 2 Router, you will also see the following:___________________________________________________________________ of DA Number of X.25 DA R 160 circuits created on the DECNIS of DECnet-Plus area R 456 2 routing addresses plus OSI reachable addresses of Level Number of Level 2 R 512 in the routers in the same routing domain as the DECNIS (continued on next page) Information Required for DECNIS Configuration 13-57 13-21 (Cont.) Configuration Information: Database Sizing__________________________________________________________ R(equired) Your Notes /O(ptionDefault Value__________________________________________________________ 2 average Average number of R 20 routers from which the DECNIS learns about nodes in the domain, multiplied by 10 of OSI reachable addresses R 200 set up on the DECNIS of Number of unique IP R 890 2 subnet addresses within (IP the routing domain Average number of R 20 (IP routers from which the DECNIS learns about each IP host within the routing domain, multiplied by 10 selected OSPF, you will also see the following:________________________________________________________________ Max. number of OSPF R 2 areas areas that the DECNIS can connect to directly Average number of OSPF R 10 routers routers in each area that the DECNIS is connected to directly area Max. number of OSPF R 3 interfaces to a single area on any OSPF router in a connected area (continued on next page) Information Required for DECNIS Configuration 13-21 (Cont.) Configuration Information: Database Sizing_____________________________________________________________ R(equired) Your Notes /O(ptionDefault Value_____________________________________________________________ average area Average number of R 40 OSPF transit and stub networks in each area that the DECNIS is connected to directly maximum Max. number of OSPF R 5 routers routers in any OSPF network in a connected area maximum Max. number of OSPF R 25 networks networks in the autonomous system (AS) maximum Max. number of OSPF R 4 routers autonomous system boundary routers in the AS maximum Max. number of OSPF R 50 routes external routes in the AS average Average number of R 2 discrete forwarding addresses provided by each boundary router for OSPF external routes maximum Max. number of R 300 destinations the OSPF protocol can have in the DECNIS routing table maximum Max. number of R 25 adjacencies the OSPF protocol can form_____________________________________________________________ Information Required for DECNIS Configuration 13-59 Part V _____________________________________________________________ Appendixes This part contains the following appendixes: o Appendix A lists the files created by the DECNIS text- based configurator, and the files loaded to the DECNIS. 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. o Appendix F contains information about using DECdns with the DECNIS. o Appendix G describes how to set up DECnet Phase IV system as a MOP load host for the DECNIS. A _____________________________________________________________ Configuration and Load Files This appendix contains tables listing the files created by the DECNIS text-based configurator, and the files loaded to the DECNIS. In these tables, client-name is the load client name of the DECNIS. Files Created by the Configurators Table A-1 and Table A-2 give the file names and locations of the DECNIS NCL script files, configuration load files, log files, data files and dump files for OpenVMS and DIGITAL UNIX load hosts, respectively. Configuration and Load Files A-1 Table_A-1_DECNIS_File_Names_on_OpenVMS_Systems____________ File____________Location_______________File_Name__________ Master NCL SYS$COMMON:[MOM$SYSTEM]NIS_client-name.NCL script file Master NCL SYS$COMMON:[MOM$SYSTEM]NIS_client- script file name.NCL_OLD for deleted DECNIS CREATE NCL SYS$COMMON:[MOM$SYSTEM]NIS_client-name_ script file EXTRA_CREATE.NCL SET NCL script SYS$COMMON:[MOM$SYSTEM]NIS_client-name_ file EXTRA_SET.NCL ENABLE NCL SYS$COMMON:[MOM$SYSTEM]NIS_client-name_ script file EXTRA_ENABLE.NCL CMIP file SYS$COMMON:[MOM$SYSTEM]NIS_client- name.CMIP CMIP file for SYS$COMMON:[MOM$SYSTEM]NIS_client- deleted DECNIS name.CMIP_OLD Combined file SYS$COMMON:[MOM$SYSTEM]NIS041_client- name.SYS Log file MOM$SYSTEM NIS_client-name.LOG for CMIP conversion Log file for MOM$SYSTEM NIS_DECNIS.LOG configurator errors DECNIS data SYS$COMMON:[MOM$SYSTEM]NIS_client-name.DAT file DECNIS data SYS$COMMON:[MOM$SYSTEM]NIS_client- file for name.DAT_OLD deleted DECNIS Previous SYS$COMMON:[MOM$SYSTEM]NIS_client- DECNIS data name.BAK[1] file DECNIS data SYS$COMMON:[MOM$SYSTEM]NIS_client- file for name.DAT_Vnn[1] last software version Load-host data SYS$COMMON:[MOM$SYSTEM]NIS_HOST_CONFIG.DAT file DECNIS dump SYS$COMMON:[MOM$SYSTEM]NIS_client-name.DMP file [1]See_Section_10.5.1_for_details.________________________ __________________________________________________________ Configuration and Load Files A-3 Table_A-2_DECNIS_File_Names_on_DIGITAL_UNIX_Systems_______ File_____________Location______File_Name__________________ Master NCL /usr/lib nis_client-name.ncl script /dnet Master NCL /usr/lib nis_client-name.ncl_old script for /dnet deleted DECNIS CREATE NCL /usr/lib nis_client-name_extra_ script file /dnet create.ncl SET NCL script /usr/lib nis_client-name_extra_ file /dnet set.ncl ENABLE NCL /usr/lib nis_client-name_extra_ script file /dnet enable.ncl CMIP file /usr/lib/mop nis_client-name.cmip CMIP file for /usr/lib/mop nis_client-name.cmip_old deleted DECNIS Combined file /usr/lib/mop nis041_client-name.sys Log file for /usr/lib nis_client-name.log CMIP conversion /dnet Log file for /usr/lib nis_client-name.lis NCL checking /dnet Log file for /usr/lib nis_decnis.log configurator /dnet errors DECNIS data /usr/lib nis_client-name.dat file /dnet DECNIS data /usr/lib nis_client-name.dat_old file for /dnet deleted DECNIS Previous DECNIS /usr/lib nis_client-name.bak[1] data file /dnet DECNIS data /usr/lib nis_client-name.dat_vnn[1] file for /dnet last software version Load-host data /usr/lib nis_host_config.dat file /dnet DECNIS dump /usr/lib/mop nis_client-name.dmp file [1]See_Section_10.5.1_for_details.______________________and Load __________________________________________________________ Configuration and Load Files A-5 Load Files Table A-3 and Table A-4 show the names and locations of the files loaded to the DECNIS on OpenVMS, and DIGITAL UNIX load hosts, respectively. A-3 Files Loaded from OpenVMS Load Hosts__________________________________________________________ Description__________________________________________________________ from a Load Host Selected__________________________________________________________ System image CMIP file .CMIP Modem Connect profile file (only if serial lines configured) X.25 profile files (only if lines configured for X.25) __________________________________________________________ from Nonvolatile Memory Selected__________________________________________________________ Combined file .SYS__________________________________________________________ and Load Files Table_A-4__Files_Loaded_from_DIGITAL_UNIX_Load_Hosts______ File_Name_________________________Description_____________ Loading_from_a_Load_Host_Selected_________________________ /usr/lib/mop/nis041.sys System image /usr/lib/mop/nis_client- CMIP file name.cmip /usr/lib/mop/digital/fcns/mcnm_ Modem Connect profile prf file (only if serial lines configured) /usr/lib/mop/digital/fcns/x25l2_ X.25 profile files prf (only if X.25 lines /usr/lib/mop/digital/fcns/x25l3_ configured) prf __________________________________________________________ Loading_from_Nonvolatile_Memory_Selected__________________ /usr/lib/mop/nis041_client- Combined file name.sys__________________________________________________ Configuration and Load Files A-7 of DECNIS Load Files on DIGITAL UNIX BOOTP Load This section specifies the directory and filenames that need to be in the /etc/bootptab file in order for DIGITAL UNIX BOOTP load hosts to respond correctly to load and dump requests from the DECNIS. Directory Used for Storing Load Files The BOOTP client database /etc/bootptab, specifies where the BOOTP load files are stored. On DIGITAL UNIX systems, by default, the load directory listed in /etc/bootptab is /usr/local/bootfiles. However, the DECNIS load files are not actually installed in the directory specified in /etc/bootptab. Instead, they are installed in the directories required for MOP loading (see Table A-2). Softlinks Automatically Created The load-host configurator automatically sets up softlinks from the files in the MOP directories to the file names and directory in /etc/bootptab. This allows the same files to be loaded no matter which protocol is specified. Load files on Non-DIGITAL BOOTP Load Hosts If your BOOTP load host is a non-DIGITAL UNIX system, note the following: o If the BOOTP/TFTP implementation is compatible with that on DIGITAL UNIX load hosts, you must use the file names in Table A-5. o If the BOOTP/TFTP implementation is not compatible with that on DIGITAL UNIX load hosts, you do not need to use these file names. Refer to the load host documentation for details of file names and directories. and Load Files File Names Required on DIGITAL UNIX BOOTP Load Hosts Table A-5 lists the file names required for BOOTP loading, and the files in the MOP directories to which they are linked. Note that the load-host configurator automatically places the correct entries in /etc/bootptab. In the table, client-name is the BOOTP load client name of the DECNIS. DIGITAL recommends that you make the BOOTP load client name the same as the MOP client name (the load-host configurator does this automatically). The directory for the files listed in column 1 is the one specified in etc/bootptab. Table A-5 File Names Required for DIGITAL UNIX BOOTP ___________Loading________________________________________ BOOTP_File_Name___Linked_to_this_MOP_file__Description____ Loading_from_a_Load_Host_Selected_________________________ system.client- /usr/lib/mop/nis041.sys System image name script.client- /usr/lib/mop/nis_ CMIP file name client-name.cmip mcnm_prf /usr/lib/mop/digital Modem connect /fcns/mcnm_prf profile file x25l2_prf /usr/lib/mop/digital X.25 profile x25l3_prf /fcns/x25l2_prf files /usr/lib/mop/digital /fcns/x25l3_prf __________________________________________________________ Loading_from_Nonvolatile_Memory_Selected__________________ system.client- /usr/lib/mop/nis041_ Combined file name______________client-name.sys_________________________ Configuration and Load Files A-9 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 NIS041.SYS - DECNIS double system image o NIS041B.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-DIGITAL 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 NIS041.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. NISAXP041 installation options you wish to use (none): following products will be processed: V4.1 Beginning installation of NISAXP V4.1 at 15:01 Restoring product save set A ... Product's release notes have been moved to SYS$HELP. DECNIS version V4.1 will take approximately 45 minutes install, depending on hardware configuration. Example Installation on an OpenVMS Load Host C-1 Network Integration Server V4.1 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 NIS041.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.1 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 [N]? y Host Configurator.... DECNIS Configurator.... DECNIS V4.1 Installation Verification Procedure completed successfully. Installation of NISAXP V4.1 completed at 15:15 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]NISAXP041.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.1 Beginning installation of NIS V4.1 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.1 will take approximately 45 minutes depending on hardware configuration. Network Integration Server V4.1 Installation Procedure. Digital Equipment Corporation 1991, 1997. 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 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- III, applicable. software is proprietary to and embodies the confidential of Digital Equipment Corporation. Possession, use, copying of this software and media is authorized only pursuant a valid written license from Digital or an authorized sublicensor. should read the Release Notes immediately AFTER installing product. The release notes for the DECNIS are in a file NIS041.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.1 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.1 Installation Verification Procedure completed successfully. Installation of NIS V4.1 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.nis410 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 DIGITAL 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/nia410_ivp Installation verification procedure /usr/lib/dnet/nis041.releasRelease notes notes /usr/lib/dnet/nisfix041.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/nis041.sys DECNIS double system image /usr/lib/mop/nis041b.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 . NIANIS410 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 V4.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 V4.1 for for Digital UNIX this correct? (y/n): y file system space required to install selected subsets: system space checked OK. DECNIS version 4.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 V4.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 1997, 15:33:57 * * DECNIS Digital UNIX kit onto a OSF1 alpha system DECNIS specific files... original etc/bootptab file. V4.1 for Digital UNIX from . (disk) Working....Thu Oct 27 15:34:14 BST 1997 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 V4.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 V4.1 HOST Configurator..........DECNIS Host Configurator Version V4.1 DECNIS Configurator........DECNIS Configurator Version V4.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 4.1 Successfully created the combined image... V4.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 NIANIS410 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. *********************************************************************** * * * NIANIS410 Installation Completed at Thu 27 Oct 1997, 15:40:06 * * * *********************************************************************** "DECNIS V4.1 for Digital UNIX" (NIANIS410) Example Installation on a DIGITAL UNIX Load Host E-5 F _____________________________________________________________ Using DECdns and the Local Namespace with the DECNIS Use this appendix if the DECnet-Plus naming services, DECdns and/or the local namespace, are used on your network. Introduction The DECNIS router does not use the DECnet-Plus naming services to find the location of the DECnet systems to which it sends messages (for example, event sinks). Instead, it uses node specifications contained in the master NCL script file generated by the DECNIS configurator. However, the load-host configurator and the DECNIS text- based configurator do make use of the naming services. If you specify in the load-host configurator that you want to use a naming service, then the configurators will do the following: o Register the DECNIS node in the local or DECdns namespace. o Use the local or DECdns namespace to find the node specifications of the systems to which the DECNIS sends messages. It then uses those specifications to write NCL SESSION CONTROL KNOWN TOWERS commands for these systems in the DECNIS NCL script. Using DECdns and the Local Namespace with the DECNIS F-1 the Use of a Naming Service In the load-host configurator, you are asked whether or not you want to use a naming service to generate node specifications. If you select Yes, then you are asked for the following: o The node name of the DECNIS. o The node synonym of the DECNIS. This is optional. If you select No, you are not asked for a node name or synonym, as the configurator will not then register the DECNIS in a namespace. Refer to the manual DECNIS Installation and Configuration for OpenVMS and DIGITAL UNIX for details. or Local Namespace? When you request the use of a naming service, the load- host configurator needs to decide whether to use the local namespace or the DECdns namespace. By default, the local namespace is used. However, you can override the default so that the config- urators use the DECdns namespace. To do this, insert the following command in the decnet_register initialization command file: SET DEFAULT DIRECTORY_SERVICE DECdns You must do this before you run the load-host and DECNIS configurators. See the manual DECNIS Installation and Configuration for OpenVMS and DIGITAL UNIX for more information. the DECNIS in a Namespace The configurators use the DECnet-Plus utility decnet_ register as follows: o The load-host configurator uses the utility to register the DECNIS in a namespace. DECdns and the Local Namespace with the DECNIS o The DECNIS text-based configurator uses the utility to update the DECNIS node object in the namespace with the DECNIS address towers. See the manual DECnet/OSI Network Management for more information about decnet_register. Requirements for Successful Registration In order for the load-host and DECNIS configurators to successfully create and update the DECNIS object in a namespace, writeable access to the parent directory where the object is going to reside must be available. Errors When Registering the DECNIS in the Namespace If there are any errors when the load-host configurator is trying to register the DECNIS, the following will be displayed: The node name listed below could not be registered in the namespace, press RETURN. Node name : namespace_name:.nodename where: namespace_name is the name of the namespace and .nodename is the fullname of the DECNIS. Adding Tower Sets to the DECNIS Entry You are asked in the DECNIS text-based configurator if you want addressing information for the DECNIS to be added to the namespace. If you select Yes, the configurator will try to add the DECNIS tower set(s) to its namespace entry. However, if you know that writeable copies of the relevant DECdns directories will not be available when the DECNIS text-based configurator is run, you should answer No to this question. The naming service commands will not then be issued, and the DECNIS configurator will go on to create the NCL script file. When the directories become available, rerun the DECNIS text-based configurator and select Yes to the question. Using DECdns and the Local Namespace with the DECNIS F-3 Errors When Adding Tower Sets to the DECNIS Entry If the configurator cannot update the DECNIS namespace entry with tower sets for any reason, the following will be displayed: Cannot add tower sets for this DECNIS. Look in the log file log-file-name for details. where log-file-name is the name of the log file; see Table F-1 for details. If this error is displayed, the rest of the configuration process should complete, but there will be no address information for the DECNIS in the namespace. Service Error Log File If the load-host configurator cannot register the DECNIS, or the DECNIS text-based configurator cannot update the DECNIS namespace entry, any errors will be written to the log file shown in Table F-1. Table_F-1_Naming_Service_Error_Log_Files__________________ Load_Host________Log_File_Name____________________________ OpenVMS MOM$SYSTEM:NIS_client-name_DNS.LOG DIGITAL_UNIX_____usr/lib/dnet/nis_client-name_dns.log_____ where client-name is the load client name of the DECNIS. Name Service Registration If the naming service registration of node name and address information fails, then you can do one of the following: o Rerun the configurators when the master copy of the naming service directories are available. If the path to these directories is through the DECNIS that is being configured, then it may be necessary to boot the DECNIS and manage it as described in Section F.6.1 before the registration can be completed. DECdns and the Local Namespace with the DECNIS o Use the decnet_register utility to register the DECNIS, as described in the manual DECnet/OSI Network Management. Managing the DECNIS Before Registration Is Complete It is not possible to manage a DECNIS using its node name if you are using a naming service to store node information and the naming service registration is not complete. In these circumstances, you need to specify the address of the DECNIS in NCL commands until the DECNIS has been registered. For example: o To manage a DECNIS with a Phase IV compatible address 1.3, you could issue the following command: ncl> show node 1.3 all attributes o To manage a DECNIS with only extended NSAP addresses, one of which was 49::98-76:08-00-2b-00-12-34:20, then you could issue the following command: ncl> SHOW NODE %x49987608002B00123420 ALL ATTRIBUTES Swapping the DECNIS Hardware If you replace the DECNIS hardware unit with another unit, and the DECNIS is using any extended NSAP addresses, you must do the following before you attempt to downline load: o Run the load-host configurator and change the hardware address for the DECNIS. o Run the DECNIS text-based configurator, and create a new NCL script and CMIP or combined file. The configurator will update the namespace entry with a new NSAP address which contains an ID field based on the new hardware address. Using DECdns and the Local Namespace with the DECNIS F-5 G _____________________________________________________________ Loading from a DECnet-VAX Phase IV Load Host Introduction This chapter describes how to set up a DECnet-VAX Phase IV system as a MOP load host for a DECNIS. Definition of DECnet-VAX Phase IV The term DECnet-VAX Phase IV refers to the version of DECnet-VAX that preceded DECnet-VAX Extensions. Procedure To set up a DECnet-VAX Phase IV system for MOP loading, follow these steps: 1. Install the DECNIS software on a DECnet-Plus system. 2. Run the configurators. In the NCL Script section of the DECNIS text-based configurator, create a CMIP file or a combined image/CMIP/profile file. 3. Copy the load files (either the combined file or the software image, CMIP file and profile files) to the DECnet-VAX Phase IV system. See Table A-3 for the file locations. Now, on the DECnet-VAX Phase IV system, follow these steps: 1. Run NCP by entering the following: $ RUN SYS$SYSTEM:NCP 2. Enter these commands: NCP> CLEAR NODE client-name ALL NCP> PURGE NODE client-name ALL Loading from a DECnet-VAX Phase IV Load Host G-1 3. Enter the DECnet address of the DECNIS: NCP> DEFINE NODE client-name ADDRESS decnet-address 4. Enter the hardware address of the DECNIS. Section G.2.1 explains how to find the correct hardware address. NCP> DEFINE NODE client-name HARDWARE ADDRESS hardware-address 5. Enter the name of the Ethernet circuit to be used for downline loading: NCP> DEFINE NODE client-name SERVICE CIRCUIT circuit-id 6. Check that the service circuit is enabled. If it is disabled, do the following: a. Turn the circuit off by entering: NCP> SET CIRCUIT circuit-id STATE OFF b. Enable the service by entering: NCP> DEFINE CIRCUIT circuit-id SERVICE ENABLED NCP> SET CIRCUIT circuit-id SERVICE ENABLED c. Now turn the circuit on again by entering: NCP> SET CIRCUIT circuit-id STATE ON 7. To specify the software image, CMIP file and profile files, enter the following commands. To specify the combined file, go to Step 8. NCP> DEFINE NODE client-name LOAD FILE - _NCP> sys$common:[mom$system]nis041.SYS) NCP> DEFINE NODE client-name MANAGEMENT FILE - _NCP> sys$common:[mom$system]nis_client-name.cmip 8. To specify a combined file, enter the following: NCP> DEFINE NODE client-name LOAD FILE - _NCP> sys$common:[mom$system]nis041_client-name.sys 9. To define the DECNIS dump file, enter: NCP> DEFINE NODE client-name DUMP FILE - _NCP> sys$common:[mom$system]nis_client-name.dmp from a DECnet-VAX Phase IV Load Host 10.Enter the following: NCP> SET NODE client-name ALL NCP> EXIT In these commands, client-name is the load client name of the DECNIS. Hardware Address The DECNIS has 16 hardware addresses available. It assigns one hardware address to each port on its CSMA/CD and FDDI Network Interface Cards. It uses a standard scheme to do this. When installing from a DECnet-VAX Phase IV system, you must specify the hardware address of the port on the DECNIS which will receive the downline load. Section G.2.1.1 to Section G.2.1.3 describe how to do this. Finding the Hardware Address The first 11 digits of the DECNIS hardware addresses are the same. The last digit depends on the type of Network Interface Card, its slot number, and the port number. Table G-1 shows how the last digit is assigned. Table_G-1__Hardware_Address_Assignment____________________ Card_______Last_Digit_____________________________________ L601 The number of the slot in which the card is inserted L602 Assigned as follows: _______________________________________________ If_slot_number_is:__3__4__5__6__7__8__9________ The last digit for 3 4 5 6 7 8 9 Port 0 is: The last digit for A B C D E F 2 Port_1_is:_____________________________________ F621 DECNIS 600: the higher number of the two slots ___________DECNIS_500:_the_lower_number_of_the_two_slots__ Loading from a DECnet-VAX Phase IV Load Host G-3 Procedure To find the correct hardware address, follow these steps: 1. Take the first 11 digits of the hardware address from the hardware address on the label on the DECNIS Processor Card. Ignore the last digit (which is always zero on the label). 2. Decide which port on which card will be used to receive the downline load. 3. Use Table G-1 to find the correct last digit for the port. Example Table G-2 shows examples of hardware address assignment on a DECNIS 600. Table_G-2_Examples_of_Hardware_Address_Assignment_________ Address on Processor Card Label___________Card______Slot____Port_Hardware_Address___ 08-00-2B-C3- L601 5 0 08-00-2B-C3-66-12- 66-12-50 55 08-00-2B-C3- L602 5 1 08-00-2B-C3-66-12- 66-12-50 5C 08-00-2B-D4- F621 6 and 0 08-00-2B-D4-76-22- 76-22-80__________________7____________87_________________ Example This section gives example commands to configure a DECnet-VAX Phase IV system as a DECNIS load host. In this example, the following information is available: from a DECnet-VAX Phase IV Load Host DECNIS load SOUTH1 client name DECnet address 44.6 Hardware address 08-00-2B-0A-11-33 Service circuit SVA-0 Combined file SYS$COMMON:[MOM$SYSTEM]NIS041_SOUTH1.SYS Dump file SYS$COMMON:[MOM$SYSTEM]NIS041_SOUTH1.DMP Example Commands $ RUN SYS$SYSTEM:NCP CLEAR NODE south1 ALL PURGE NODE south1 ALL DEFINE NODE south1 ADDRESS 44.6 DEFINE NODE south1 HARDWARE ADDRESS 08-00-2B-0A-11-33 DEFINE NODE south1 SERVICE CIRCUIT sva-0 SET CIRCUIT sva-0 STATE OFF DEFINE CIRCUIT sva-0 SERVICE ENABLED SET CIRCUIT sva-0 SERVICE ENABLED SET CIRCUIT sva-0 STATE ON DEFINE NODE south1 LOAD FILE sys$common:[mom$system]nis041_ DEFINE NODE south1 DUMP FILE sys$common:[mom$system]nis041_ SET NODE south1 ALL EXIT Loading from a DECnet-VAX Phase IV Load Host G-5 __________________________________________________________ Index Bridging (cont'd) _____________________ port cost, 13-19, 13-21, router, 3-2, 3-3, 13-43 , 5-3 protocol types, 8-5 spanning tree, 13-19, configurator, 9-2, 13-22, 13-43 prefix, 13-6, 13-8 C__________________________ towers, 3-6, 5-6 Call data, 13-29 Phase V, IP, 13-36, 13-37 OSI, 13-36, 13-37 system) Call data mask, 13-33, 13-9, 13-37, 13-50, 13-32, Call data value, 13-33, 13-37, 13-50 _____________________ Call request, 8-7 13-46 Called address extension mask, 13-50 6-1, 6-2 value, 13-50 file locations, A-9 Called NSAP, 13-50 hosts, 6-1 to 6-2 Channel number 5-3, 5-4 to 5-5, permanent circuits, 13-34 PVCs, 13-46 6-1 CHDLC A-8 bridge port, 8-3 loading, 12-2 Client systems, 8-6 protocols, 5-1 security, 8-8, 13-53 filtering, 13-27 Closed User Group. See CUG 8-3, Index-1 6-2, 10-5, CSMA/CD (cont'd) , A-9, G-1, G-2 information for 10-6, 10-7 configurator, 13-10 3-5, 5-5 port, 8-6 A-2, A-4 CTF procedure, 10-8 password, 13-3 file, 2-5, 6-2, user name, 13-3 , G-1, G-2 CUG, 8-6, 13-46 10-6, 10-7, configuration option, 13-3 A-2, A-4 number, 13-46 Maintenance section, 13-46 Protocol. D__________________________ CMIP file NCL script files. DCE mode DA adjacencies, 13-57 Convert DA circuits, 8-4, 13-36 Data file Options DECNIS, 11-9, A-2, A-4 8-2, load-host, 3-11, 5-2, frame 5-12, A-2, A-4 Database sizing, 8-9, 13-56 to 13-59 1, DEC Network Integration 2, system, 8-6 Server. See DECNIS with MPC-II, DECdns, 2-7, 4-5 lookups, 3-6, 5-6, F-1 with MPC-II, Name server, 3-6, 5-7 namespace, 3-6, 3-11, to new section, 5-7, 5-12, F-1 , 9-6 node name, 12-3, 13-55 NCL script files, object name, 13-55 use of by configurators, configuration, 11-8 3-6, 5-6, 12-3 using with the DECNIS, 11-10 option F-1 to F-5 configurator, 9-1 DECdns namespace, F-2 text-based DECnet-VAX Phase IV load hosts, G-1 to G-5 9-1 port, 8-3 13-12, 13-44 2-7, 4-5, Delete option F-2 to F-3 DECNIS configurator, 9-2, 9-7 environment variable, Deleting an internal image, 2-7, 4-6 2-5, 4-4 Deleting installed files information DIGITAL UNIX load hosts, required, 13-2 to 4-7 13-59 OpenVMS load hosts, 2-9 Destination address 5-5 IP reachable address, unit, to configure, 1-1 13-45 configurator, 1-2 tunnel circuits, 13-38 node Destination DTE address 8-1 OSI reachable address, Problem Solving 13-44 UNIX load hosts, X.25 static outgoing 4-3 circuit, 13-29 load hosts, 2-4 Destination subnet mask text-based IP reachable address, configurator 13-45 of modifying DIGITAL UNIX load hosts information, 11-3 files installed, D-1 to required for, D-6 13-2 information needed to 8-1 install on, 4-1 7-2 installation procedure, 7-2 to 7-5, 9-1 to 4-2 9-9 installing on, 4-1 to 4-8 packet size, starting load-host 13-24, 13-46, 13-47 configurator on, 5-2 RIP route, 13-6 Domain connectivity, 13-58 values, 12-1, 13-1 Double image window size, editing, 2-5 to 2-7, 4-4 13-24, 13-46, 13-47 to 4-5 DTE address on other called, 13-50 information, 11-2, destination on X.25 DA 11-3 to 11-4 circuit, 13-44 Menu, 9-7 destination on X.25 a router, 3-2, 3-7 static outgoing to 3-8, 5-7 to 5-8 circuits, 13-29 incoming, 13-34, 13-38, 13-50 Index-3 Ethernet format protocol (cont'd) types, 13-27 13-47 Event logging, 8-8, 13-54 13-23 Event messages IP DIGITAL UNIX load hosts, 13-51, 4-3 13-50 OpenVMS load hosts, 2-4 for Event sink, 8-8, 13-54, 13-33, 13-55 13-38, 13-50 Event stream, 8-8, 13-54 13-24 Example installation 13-47 DIGITAL UNIX, E-1 to E-5 circuits, 13-29, OpenVMS, C-1 to C-5 Example NCL script files, 13-36 DIGITAL UNIX load hosts, 3-1 3-5, 5-6, 12-3 4-3 Assigned OpenVMS load hosts, 2-4 Exit option 8-4, DECNIS configurator, 9-1 DECNIS text-based_____________________ configurator, 9-1 of Exiting DECNIS 11-3 configuration, 9-8 Extended packet sequence numbering, 13-24 13-18, F__________________________ 8-2, FDDI port, 8-3, 13-31, File names adjacencies, DIGITAL UNIX, A-3 to A-5, A-6, A-9 OpenVMS, A-1 to A-3, A-6 file Files installed F-4 DIGITAL UNIX load hosts, registration, D-1 to D-6 OpenVMS load hosts, B-1 creating to B-5 10-3 Filters, 8-7 running call data mask, 13-50 3-10, call data value, 13-50, 9-9, called address extension mask, 13-50 G-2 value, 13-50 13-13 called NSAP, 13-50 (cont'd) Hardware unit requirement when swapping class, , F-5 X.25 8-6, 13-50 HDLC port, 8-3 name, Help DTE ad 13-50 DECNIS text-based configurator, 7-3 on to 7-5 13-50 keys used, 7-4 to 7-5 static circuits, 13-33 leaving, 7-4 load-host configurator, called , 13-50 3-10, 5-11 Horizontal menus, 9-3 on series of, 9-4 13-50 Horizontal scrolling, 9-5 DTE 13-50 I__________________________ reason, 13-50 DTE address, IEEE 802.2 13-50 encapsulation, 13-13 range, 13-50 IEEE 802.2 format protocol control negotiation, types, 13-27 13-23 IEEE 802.2 SNAP format relay connections, protocol types, 13-27 8-4, 13-40 Image loaded, 2-5 Image/CMIP/profile file See combined file________________________ Client, DEC X.25 Image/CMIP/profile file. for ULTRIX, 8-6 See combined file 8-6, 13-46 Images for DECNIS, 2-4, 13-46, 13-50 4-3 DTE address, 13-46 Incoming call request, 8-7 13-46 Incoming DTE address, 13-34, 13-38, 13-50 Incoming security________________________ X.25 server client, 8-7, address, 5-4, 12-2, 13-44, 13-47, 13-51 G-2 Incomplete configuration saving, 9-7 to G-4 Index numbers, 2-6, 4-5 Information required F-5 DECNIS configuration, 13-2 to 13-59 Index-5 IP external destinations, required 13-57 IP Level 1 destinations, UNIX 13-57 4-1 IP Level 2 destinations, configuration, 13-58 to IP local adjacencies, to 13-56 load IP reachable address, 8-5 2-1 cost, 13-45 file, name, 13-45 mode, number of, 13-57 procedure IP routing, 8-2, 8-4 UNIX IP subnet mask, 13-12, 13-45 local, 13-18, 13-32, UNIX 13-42 to IS-IS load link state routing 2-10 required, 8-3 mode, image, 2-5, 4-4 K__________________________ Protocol. Keys IP used in configurators, link, 7-2 to 7-3, 13-30, used in Help, 7-4 to 7-5 KNOWN TOWER, 3-6, 5-6, F-2 12-2 L__________________________13-12, 13-32, LAN device, 13-47 LAN end system adjacencies, neighbor, 13-56, 13-32, LAN hardware address, 3-3, 13-17 13-17, 13-31, 5-4, 12-2, 13-47 OSI reachable address, IP router, 13-45 13-44 source, 13-7, 13-9 Level 1 average 13-8 connectivity, 13-56 connectivity, Level 1 cost, 13-11, 13-16, 13-20, 13-30, 13-35, 13-40 1 routing Load-host configuration destinations, 13-56 information 2 average DIGITAL UNIX load hosts, connectivity, 13-58 5-3 to 5-7 2 cost, 13-16, OpenVMS load hosts, 3-3 13-20, 13-30, 13-35, to 3-7 13-40 required, 12-2 to 12-3 Load-host configurator, 2 2 routing 1-2, 5-1 destinations, 13-57 menu options, 5-2 options, 3-2 of starting on DIGITAL UNIX of section, 8-2 load hosts, 5-2 state starting on OpenVMS load for Integrated host, 3-2 IS-IS, 8-3 using, 3-1 to 3-11, 5-1 a DECNIS, 5-2 to 5-12 a router, 3-2 Load-host data file, 3-11, 8-6 5-11 to 5-12, 8-1, A-2, information A-4 , 13-46 to 13-47 saving, 3-11, 5-12 option, Loading 13-3 CMIP file, 10-5 client name, 2-8, from a Phase IV load 3-3, 4-7, 5-3, 8-1, host, G-1 to G-5 10-7, 10-8, 11-1, 11-2, from load host, 3-5, 5-5 12-2, 13-2 nonvolatile memory, 3-5, hosts 5-5 6-1 to 6-2 protocols used, 3-1, 5-1 file locations, A-8 Local IP address, 13-17, Phase IV, G-1 13-31, 13-42 to G-5 Local IP subnet mask, 3-1, 5-1 13-32, 13-42 UNIX, A-9 Local namespace, 2-7, 3-6, 2-10 3-11, 4-5, 5-6, 5-7, UNIX systems, 5-12, F-1, F-2 6-2 use of by configurators, A-1 3-6, 5-6 configuration Local subnet mask, 13-18 of modifying, Log file 11-5, 11-6 CMIP conversion, A-2, A-4 configurator errors, 3-10, 5-11, 9-9, A-2, A-4, F-4 Index-7 (cont'd) Minimum window size lines, 13-24 checking, LLC2, 13-47 channel Modify Channel effect on other channel information, 11-2,, 13-47 11-3 to 11-4 load-host information, 13-47 11-5 to 11-10 13-47 Modify a router, 3-2, 3-8, 5-2, 5-8 to 5-9 _____________________ Modify option 13-47 DECNIS configurator, 9-1, 9-2, 9-7, 9-8 configurator, DECNIS configurator Main processor Menu, 9-6, 11-2, 4-3, DECNIS text-based adjacencies, configurator, 9-1 NCL MOD_FLSH program, 2-6 to, 10-2, 2-7, 4-4 to 4-5 to MOP circuit, 3-4, 5-4, 10-2 12-2 packet MOP client name. 13-24 See Load client name 13-47 MOP loading, 3-1, 3-4, window 3-11, 5-1, 5-3, 5-4, 13-24 13-47 5-12 MOP protocol, 3-1 configurator Main Move to previous section in DECNIS configurator, 2-8, 9-6 MPC 9-4 part numbers, 2-5, 4-4 configurator MPC-II, 4-3, 4-4 Menu, MPC-I, 2-5, 5-3 MPC-II, 2-5 Menu, MPC-III, 2-4, 2-5 Menu, Multiple load hosts, 2-10 from, packet size 13-24 13-47 NetWare network number, 13-13, 13-21________________________ Network information DIGITAL UNIX load hosts, 3-6, 5-12, F-1, F-2, F-3 4-3 OpenVMS load hosts, 2-4 3-6, 5-12, F-1, F-2 Network Interface Cards, 8-1, G-3 the in, 2-7, 4-5 changing a selection, 9-4 information required, service, 4-5, 5-6 13-2 selecting, 9-4 log Network Management 3-6 password, 13-5 with F-1 to F-5 user name, 13-4 NIC. checking See Network Interface file, Cards script NIS$DECNIS_CONFIG, 7-1 by 8-9 NIS$HOST_CONFIG, 3-2 nis041.sys, 4-3 script NIS041.SYS, 2-4 10-2 NIS_DECNIS.LOG, 9-9 script 3-7, 3-8, 5-6, 5-8, 5-9 nis_decnis_config, 7-2 nis_host_config, 5-2 to Node name, 3-7, 5-7, deleted 5-8 13-49, 13-55 Client system, 13-53 A-2, event sink, 13-55 10-2 X.25 server client, 13-49 10-3 Node synonym, 3-7, 5-7, commands, 12-3 Nonvolatile memory loading, 13-13, 13-43 3-5, 5-5 advantages, 3-5, 5-5 IP 13-17, 13-31, 13-42 definition, 3-5, 5-5 modifying, 3-8, 5-9 13-14, updating choice of, 3-10, IPX 13-13 5-11 Novell IPX 13-13, 13-21 encapsulation, 13-13 NSAP called, 13-50 Index-9 Outgoing security system, 13-49, Client systems, 8-8, 13-53 sink, 13-55 Overstrike mode, 9-5 13-6, 13-8 in OSI reachable P__________________________ 13-44 Packet call request, 8-7 Packet size, 13-24, 13-29,_____________________ name, 13-55 13-33 documentation DA circuit, 13-37 UNIX load hosts, LLC2, 13-47 permanent circuits, 13-34 to PVCs, 13-46 load X.25 line, 13-24 2-4 Part number for MPC, 2-5, load 4-4 installed, Path cost interphase links, 13-17, needed 13-20, 13-31, 13-35, on, 13-41 on, Periodic update interval, 13-14, 13-21 information, Permanent circuits, 13-34 Permanent Virtual Circuits. load-host on, 3-2 See PVCs sections, 9-6 Phase IV address, 3-4, Menu, 9-2, 9-6 to 5-5, 13-49, 13-55 Phase IV node name, 13-49 9-7 Phase V address. called address, See NSAP address Phase V area address, 13-6, 13-8 DIGITAL UNIX Phase V routing algorithm 8-4 required for Integrated address, IS-IS, 8-3 , 13-44 Port 13-44 hardware address, G-3 13-44 Postinstallation of, 13-58 information 13-44 DIGITAL UNIX load hosts, 4-5 OpenVMS load hosts, 2-7 bridge port, 8-3 Release notes (cont'd) for filters, OpenVMS load hosts, 2-4 13-50 Remote Address Prefix. card, 3-4, 5-4 See RAP files, 10-8, A-9 Remote DTE address, 13-46 name, 13-23 Remote MAC address, 13-47 route, 13-7 Restore a router, 3-2, types 3-9, 5-2, 5-9 to 5-10 format, 13-27 Reverse charging, 13-29, 802.2 format, 13-27 13-37 802.2 SNAP format, RIP 13-27 default route, 13-7 8-5 options, 13-18, 13-32, number, 13-46 13-42 option, protocol, 8-2, 13-6, 13-3 13-8, 13-17, 13-31, 13-46 13-41 size, 13-46 source, 13-7 8-8, 13-53 Root priority number, 13-3 size, 13-46 Route propagation, 13-7 routing circuits, Router adjacencies, 13-56 13-34 Routing algorithm, 13-6, 13-7 ________________________ Routing domains, 8-4, 8-5 the configuration, Routing section, 8-2 9-8 S__________________________ ________________________ Save options, 9-2, 9-7 to 13-52, 13-53, 13-54 9-8 addresses Script files 8-5, 13-45 See NCL script files 8-5, 13-44 Scrolling, horizontal, 9-5 password, 13-16, Sections 13-30, 13-35 moving to new, 9-6 DTE address, Sections in the DECNIS 13-50 text-based configurator, 11-1 8-1 to 8-9 reason, 13-50 Sections Menu, 9-2, 9-5, the DECNIS in a 9-6, 9-7 namespace, 2-7, 4-5 Security notes incoming calls, 13-51 UNIX load hosts, outgoing calls, 8-8, 4-3 13-53 Index-11 (cont'd) Type of loading, 5-5 13-53 U_________________________8-7 DTE address, ULTRIX Gateway Client, 8-6 , 13-50 UNIX load hosts, 6-2 client. Update a router, 3-2, 3-9 to 3-10, 5-2, 5-10 to X.25 CONTROL KNOWN TOWER 5-11 Updating DECNIS software, 3-6, sections, 9-7 2-8 to 2-9, 4-6 to 4-7 User NCL script files, 13-13 10-3, 10-4 A-8 Tree, 13-19, V__________________________ , 13-43 VAX P.S.I. Access, 8-6 range, 13-33, VAXcluster installing on, 2-10 mask, VCP bridge port, 8-3, 13-45 Verifying the installation node, DIGITAL UNIX load hosts, 4-7 IP OpenVMS load hosts, 2-9 VMS load hosts. See OpenVMS load hosts _____________________ W__________________________ DA Window size for DA circuit, 13-37 incoming frame, 13-24 LLC2, 13-47 outgoing packet, 13-24 permanent circuits, 13-34 5-1 PVCs, 13-46 6-1, static incoming circuit, class 13-33, 13-33, static outgoing circuit, sets, 13-29 password, , 13-34 circuit, 13-38 IP address, 13-38 X.25 routing circuits, 8-3, 13-29________________________ X.25 security. DA See Security DA X.25 server client, 8-6, DTE 13-49 gateway, filters, 8-6, 13-50 information, name, 13-49 options, security, 8-7, 13-51 permanent circuits, 8-3, 13-34 X.25 static circuits, 8-3, 13-29, 13-33 Index-13