Digital PDFs

AA-EA87E-TE

May 1990

61 pages

Original

2.7MB

Document:	DECnet—-ULTRIX installation
Order Number:	AA-EA87E-TE
Revision:	000
Pages:	61
Original Filename:

OCR Text

DECnet-ULTRIX

Installation

Order Number: AA-EA87E-TE

DECnet-ULTRIX

Installation

May 1990
This manual shows you step by step how to install your
DECnet-ULTRIX software and how to configure and test your
node's operation in the network.
Supersession/Update Information:

This is a revised
manual.

Operating System and Version:

ULTRIX V4.0

Software Version:

DECnet-ULTRIX V4.0

o
Order Number: AA-EA87E-TE

AA-EA87E-TE
May 1990

The information in this document is subjectto change without notice and should not be construed as
a commitment by Digital Equipment Corporation. Digital Equipment assumes no responsibility for
any errors that may appear in this document.
The software described in this document is furnished under a license and may only be used or
copied in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied
by Digital or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions
as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013.

The following are trademarks of Digital Equipment Corporation:
DEC
DECnet
DECUS

PDP
ULTRIX
UNIBUS

VAX
VMS

~DmDDmD1M

UNIX is a registered trademark of AT&T in the USA and other countries.

This manual was produced by Networks and Communications Publications.

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1

vii

Before You Start

1.1

Checking Whether DECnet Is Already Configured . . . . . . . . . . . . . . . . . . . . .

1-2

1.2

Registering Your Software Before Installation. . . . . . . . . . . . . . . . . . . . . . . .

1-2

1.3

Choosing the Installation Procedure ..............................

1-3

1.4

Deciding Which Software Subsets to Install . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

1.5

How to Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4

('"

Chapter 2

Installing DECnet-ULTRIX onto a Node

2.1

DECnet-ULTRIX Basic Installation Requirements

2-1

2.2

Installing or Reinstalling DECnet-ULTRIX . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1
Installing DECnet-ULTRIX for the First Time . . . . . . . . . . . . . . . . . .
2.2.2
Reinstalling DECnet-ULTRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4
2-4
2-5

2.3

Mounting the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-5

2.4

Selecting the Software Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-5

2.5

Copying the DECnet-ULTRIX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-6

2.6

Configuring the Node for DECnet-ULTRIX Base Software . . . . . . . . . . . . . . .
2.6.1
Configuring the DECnet Nodes Database. . . . . . . . . . . . . . . . . . . . .
2.6.2
Modifying System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.3
Preparing to Restart the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-7
2-9
2-1 0
2-10

2.7

Configuring the Node to Run Gateway Software ..................... .

2-12

2.8

Deleting the DECnet-ULTRIX Software ............................ .

2-13

2.9

Restarting the Installation ..................................... .

2-13

2.10

Correcting Errors After the Installation Is Complete .................. .

2-14

2.11

Verifying the Installation ...................................... .

2-14

iii

Chapter 3

Installing DECnet-ULTRIX into a Diskless Environment

3.1

DECnet-ULTRIX Diskless Installation Requirements .................. .

3-1

3.2

Running the DECnet-ULTRIX Diskless Installation Procedure ........... .

3-:3

3.3

Mounting the Distribution Media ................................ .

3-4

3.4

Selecting Software Subsets .................................... .

3-4

3.5

Configuring the Client for DECnet-ULTRIX Base Software .............. .
3.5.1
Configuring the DECnet Nodes Database .................... .
3.5.2
Modifying System Files ................................ .
3.5.3
Preparing to Start the Client ............................ .

3-5
3-7
3-8
3-9

3.6

Configuring the System to Run the Gateway Software ................ .

3-10

3.7

Correcting Errors After the Installation Is Complete .................. .

3-11

3.8

Verifying the Installation ...................................... .

3-12

./-.~\

"'.
Chapter 4

Checking Your Node's Operation on the Network

4.1

Overview of Checkout Tests ................................... .

4-1

4.2

DECnet-ULTRIX Installation Checkout Procedure .................... .

4-6

Appendix A

DECnet-ULTRIX Distribution Files

Index

Figures

4-1

DDCMP Point-to-Point Connection ................................ .

4-1

4-2
4-3

Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Node Loopback Test ..................................... .

4-4

Controller Loopback Test ....................................... .

4-5

Datalink Loopback Test to Remote Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6

Node-Level Loopback Test to Remote Node .......................... .

4-7

DECnet File Transfer to Local Node ............................... .

4-8
A-1

DECnet File Transfer to Remote Node ............................. .

4-2
4-3
4-3
4-4
4-4
4-5
4-5
A-1

DECnet-ULTRIX Directory Tree .................................. .

Tables

1-4
2-2
2-4
2-4

1-1
2-1
2-2

Summary of the DECnet-ULTRIX Software Subsets . . . . . . . . . . . . . . . . . . . . .

2-3

Commands to Reinstall DECnet-ULTRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1

DECnet-ULTRIX Diskless Installation Requirements . . . . . . . . . . . . . . . . . . . . .

3-2

A-1

DECnet-ULTRIX Distribution Files by Directory . . . . . . . . . . . . . . . . . . . . . . . . .

A-2

DECnet-ULTRIX Basic Installation Requirements . . . . . . . . . . . . . . . . . . . . . . .
Commands to Install DECnet-ULTRIX for the First lime . . . . . . . . . . . . . . . . . .

o
v

Preface
This manual explains how to install DECnet-ULTRIX V4.0 software on any
ULTRIX V4.0 system.
Using this manual, you can determine which type of installation procedure to
use and which software subsets to install. The exam pIes lead you step by step
through the installation procedures.
This manual also tells you how to configure both the server and the system to run
the optional DECnet-Intemet Gateway software.
Finally, you learn how to verify that your node is running properly on the network.

Intended Audience
This manual is for the user who is either installing DECnet-ULTRIX software
onto a running ULTRIX V4.0 system or testing a new DECnet-ULTRIX node
in the network. Ideally, the person who installs the software has had system
administration experience. Be aware that most of the procedures described in
this manual require superuser privileges.

Structure of This Manual

This manual contains four chapters and an appendix:
Chapter 1

Reviews the four questions you must answer before you begin the
DECnet-ULTRIX installation: Has DEC net been configured into the
kernel yet? Have you used LMF to register your DECnet-ULTRIX V4.0
software license? Are you installing DECnet--ULTRIX onto a node or into
a diskless environment? Which software subsets do you want to install?

Chapter 2

Explains how to install DECnet--ULTRIX software onto a node.

Chapter 3

Explains how to install DECnet-ULTRIX for a client to use in a diskless
environment.

Chapter 4

Describes how to check the node's operation on the network.

Appendix A

Lists all files that the DECnet-ULTRIX installation procedure copies to
your system.

o
vii

Related Documents
For more information about DECnet-ULTRIX software, see the following documents:

•

DECnet-ULTRIX Release Notes
This document contains miscellaneous information and updates not included
in other books in the DECnet-ULTRIX documentation set.

•

DECnet-ULTRIX DECnet-Internet Gateway Use and Management
This manual describes how to use and manage the DECnet-Internet Gateway.

•

DECnet-ULTRIX Programming
This manual explains application programming concepts and guidelines to use
in the DECnet-ULTRIX environment. The manual also describes DECnetULTRIX system calls and subroutines and shows DECnet-ULTRIX data
structures and programming examples.

•

DECnet-ULTRIX Network Management
This manual describes procedures for managing the network, such as defining
the permanent and volatile databases, node identifications and addresses,
and lines and circuits; enabling event logging; displaying network counter
information; operating and controlling a DECnet-ULTRIX node; and testing
the network operation.

•

DECnet-ULTRIX NCP Command Reference
This manual tells network managers how to use the Network Control
Program (ncp)to perform network management functions.

1b obtain a detailed description of the Digital Network Architecture, see DECnet
Digital Network Architecture (Phase IV), General Description.
For a detailed description of the License Management Facility (LMF), see Guide
to Software Licensing.
For a beginner's introduction to the ULTRIX operating system, see The Little
Gray Book: An ULTRIX Primer.

Graphic Conventions
This manual uses the following conventions:
•

All numbers are decimal unless otherwise noted.

•

All Ethernet addresses are hexadecimal.

Convention

Meaning

special

In running text, commands, command options, user names, file
names, and directory names appear in special type.

example

Indicates an example of system output or user input. System
output is in black type; user input is in red type.

c
viii

(-:-

Convention

Meaning

10wercaselUPPERCASE

Because the ULTRIX software is case sensitive, type all literal input in the case shown. In running text, UPPERCASE
is also used for the names of all DECnet nodes, including
DECnet--ULTRIX nodes. This convention follows DECnet protocol, which names and recognizes all nodes in UPPERCASE.
However, node names are not case sensitive and need not be
typed in the case shown.

italic

Indicates a variable, for which either you or the system specifies a value.

[ ]

Within the installation procedure, indicates the default value.
Do not type the square brackets.
Indicates a key on your keyboard. I cTRLlkey I represents a
CONTROL key sequence, where you press the CONTROL key
at the same time as the specified key. Note that keyboard keys
are represented by this symbol, <key>, on line.
Indicates the RETURN key.

c
ix

Chapter 1

Before You Start
Using this manual, you can install DECnet-ULTRIX V4.0 software onto VAX
or RISC systems. There are only three differences between the two types of
installations:
•

C~I

•

The ULTRIX and DECnet-ULTRIX software subset names begin with a
three-letter prefix, which indicates whether the subset is for a VAX. or RISC
system, as follows:

System Type

DECnet·ULTRIX
Subset
Names Prefix

ULTRIX Subset
Names Prefix

VAX.

DNU

ULT

RISe

DNP

UDT

The DECnet-ULTRIX configuration files are named according to the type of
system you have, as follows:
System Type

Configuration File Name

VAX.

Isys/conf/VAXI HOSTNAME

RISe

Isys/conflmipsl HOSTNAME

The amount of memory needed to install DECnet-ULTRIX software onto
VAX and RISC systems differs. (Tables 2-1 and 3-1 list the installation
requirements.)

Before you start the DECnet-ULTRIX installation procedure, answer the
following questions:

•

Has DECnet been configured into the kernel already? See Section 1.1.

•

Have you already used the License Management Facility (LMF) to register
your DECnet-ULTRIX V4.0 software license? See Section 1.2.

•

Which of the two types of installation procedures do you want to use:
the DECnet-ULTRIX basic installation or the DECnet-ULTRIX diskless
environment installation? See Section 1.3.

•

Which software subsets do you want to install: the DECnet-ULTRIX Base
Software, the DECnet-Internet Gateway, the DECnet-ULTRIX On-Line
Manual Pages, or the DECnet-ULTRIX Unsupported Software? See Section
1.4.

Section 1.5 explains how to use this manual.

Before You Start

1-1

1.1 Checking Whether DECnet Is Already Configured
Before you begin the DECnet-ULTRIX installation, check to see whether DECnet
has already been configured in the ULTRIX kernel. You can install and configure
DECnet-ULTRIX without configuring DECnet in the kernel; however, to run
DECnet-ULTRIX, DECnet must be so configured.
The installation procedure automatically checks whether DECnet is already
configured in the kernel. If DECnet is not configured, a message tells you to
rebuild the kernel after the configuration is complete.
'1b see whether DECnet is already configured into the kernel before you start the
DECnet-ULTRIX installation, enter this command:
% nm /vmunix I fgrep -s nsp_usrreq && echo yes

If the system displays yes, then DECnet is already configured. If not, configure
DECnet in the kernel. You can rebuild the kernel now or after the installation
and configuration are complete. ('1b add DECnet to the kernel, specify "options
DECNET" and "pseudo-device decnet" in the appropriate configuration file and
rebuild the kernel.)

1.2 Registering Your Software Before Installation
Use the ULTRIX LMF utility to register your software license for DECnetULTRIX V4.0. You must register your software license before you can perform
any remote access. Use the information from your Product Authorization Key
(PAK) to register your software.
Register and load your authorization key before you begin the DECnet-ULTRIX
installation procedure. If you do not register beforehand the installation
procedure reminds you to do so as soon as the installation is complete.
The License Management Facility (LMF) is a system management software tool
that you use to comply with your license agreement. The LMF utility offers
options for many kinds of license agreements. The terms and conditions of your
contract determine your legal use of this software.
The LMF does the following:
•

Maintains the file of registered PAKs (Product Authorization Keys)

•

Updates the kernel cache

•

Maintains a library of functions used by licensed software
NOTE

You need superuse~ privileges to use the LMF utility.
The Guide to Software Licensing introduces the LMF utility and describes how
you use it. You can also refer to the LMF man page, Imf(8), for information.

1-2

Before You Start

1.3 Choosing the Installation Procedure
How you plan to use DECnet-ULTRIX (on a node with a disk or in a diskless
environment) determines which installation procedure you choose. In a diskless
environment, diskless client nodes can use DECnet-ULTRIX.
•

If you are installing DECnet-ULTRIX onto a node that has its own disk
but does not support clients, use the DECnet-ULTRIX basic installation
procedure described in Chapter 2.

•

If you are installing DECnet-ULTRIX for a client to use in a diskless
environment, use the installation procedure described in Chapter 3.

•

If you are installing DECnet-ULTRIX onto a server node for the server's own
use, use the basic installation procedure described in Chapter 2. You can
perfonn this procedure even if you have already installed DECnet-ULTRIX
into a diskless environment on the server.

1.4 Deciding Which Software Subsets to Install
Before you begin the installation, decide which subsets you want to install. The
DECnet-ULTRIX software distribution media contains the following subsets:
•

DECnet-ULTRIX Base Software

•

DECnet-Intemet Gateway

•

DECnet-ULTRIX On-Line Manual Pages

•

DECnet-ULTRIX Unsupported Software

Use the descriptions in Table 1-1 to determine which subsets to install. Tables
2-1 and 3-1 describe the software installation requirements for each subset.

o
Before You Start 1-3

Table 1-1:

Summary of the DECnet-ULTRIX Software Subsets

Subset

DECnet-ULTRIX.
Base Software

DECnet-Internet
Gateway

DECnet-ULTRIX
On-Line Manual
Pages

DECnet-ULTRIX
Unsupported Software

Function

Provides the
DECnet-ULTRIX
functions that let
you share information with remote
DECnet users and
programs over the
network. Also required to install the
DECnet-Internet
Gateway.

Lets UNIX users on
Internet networks
and DECnet users
exchange data.
To set up your
ULTRIX. node to
act as a DEenetInternet Gateway,
install the Gateway
software.

Is an on-line reference manual.
Gives the syntax, description,
diagnostic messages, restrictions,
and examples for
DECnet-ULTRIX.
commands, systern calls, and
subroutines.

Contains utilities and
sample programs that
Digital Equipment
Corporation supplies
on an "as_is" basis for
general customer use.
However, Digital neither
supports these utilities
nor covers them under
any Digital support
contracts.

Subset
For VAX
Systems

DNUBASE400

DNUINETGW400

DNUMAN400

DNUUNS400

Subset
For RISe
Systems

DNPBASE400

DNPINETGW400

DNPMAN400

DNPUNS400

1.5 How to Use This Manual
This manual discusses the two kinds of installations you can perfonn in a
separate chapter. Chapter 2 guides you through a DECnet-ULTRIX basic
installation, and Chapter 3, a DECnet-ULTRIX diskless installation. Before
you start an installation, make sure you meet the requirements shown at the
beginning of the respective chapter. To check your progress during installation,
see the examples in the chapter. For a complete list of the files that the
installation procedure copies to your system, see Appendix A.
To make sure your node is operating on the network, follow the test procedures
described in Chapter 4. The checkout procedures verify that your node can
communicate with itself and other nodes on the network.

1-4 Before You Start

Chapter 2

Installing DECnet-ULTRIX onto a Node
This chapter tells you how to install DECnet-ULTRIX onto a node, including:

•

What to do first

•
•
•
•
•

How to install the software
How to delete the installed software
How to restart the installation
How to correct installation errors
How to verify the installation

Before you start the installation, make sure you meet the requirements outlined
in the next section.

2.1

DECnet-ULTRIX Basic Installation Requirements
For any DECnet-ULTRIX installation, you need superuser privileges. To install
DECnet-ULTRIX. onto a node, you must also meet the requirements in Table 2-1.

c
Installing DECnet-ULTRIX onto a Node

2-1

Table 2-1:

DECnet-ULTRIX Basic Installation Requirements
Requirements

Software Subset

For VAX Systems

For RISe Systems

DECnet-ULTRIX. V4.0
Distribution media or network
kit

1 1600-bpi nine-track magnetic tape, CDROM, or 1 TK50
cartridge

1 1600-bpi nine-track magnetic
tape, CDROM, or 1 TK50 cartridge

Operating system

ULTRIX. V4.0

Installed software

ULTRlX V4.0 Base Software
(ULTBASE400)

ULTRIX. V4.0 Base Software
(UDTBASE400)

ULTRIX. V4.0 Kernel
Configuration Files (ULTBIN400)

ULTRIX V4.0 Kernel Configuration
Files (UDTBIN400)

DECnet-ULTRIX Base
SoJfware

Privileges

Superuser

Disk space during installation

1750 kilobytes (KB) in lusr

2730 KB in lusr

+ 15 KB in the root file system

Disk space after installation

Same as during installation

Storage device on a MicroVAX

1 RD53 disk or equivalent

Estimated time

10 to 30 minutes

DECnet~Internet Gateway

Installed software

10 to 30 minutes

Additional Requirements
DECnet-ULTRIX. V4.0 Base
Software (DNUBASE400)

DECnet-ULTRIX V4.0 Base
Software (DNPBASE400)

ULTRIX. V4.0 Communications
Utilities (ULTCOMM400)

ULTRIX V4.0 Communications
Utilities (UDTCOMM400)

Disk space

205 KB in lusr

340 KB in lusr

Estimated time

5 to 10 minutes

DECnet On~Line
Manual Pages
Installed software

Additional Requirements
DECnet-ULTRIX. V4.0 Base
Software (DNUBASE400)

DECnet-ULTRIX V4.0 Base
Software (DNPBASE400)

ULTRIX V4.0 On-Line Manual
Pages (ULTMAN400)

ULTRIX V4.0 On-Line Manual
Pages (UDTMAN400)

Disk space

135 KB in lusr/man

Estimated time

5 minutes

DECnet-ULTRlX Unsupported
SoJfware

Additional Requirements

Installed software

DECnet-ULTRIX. V4.0 Base
Software (DNUBASE400)

DECnet-ULTRIX V4.0 Base
Software (DNPBASE400)

Disk space

370 KB in lusr

535 KB in /usr

Estimated time

5 minutes

2-2

Installing. DECnet-ULTRIX onto a Node

Before you install DECnet-ULTRIX:
1. Make sure you have enough free disk space to install the software subsets of
your choice. To check the available disk space in lusr and root (/), enter the
commands:

* df /usr
* df / I@J

2. Make a backup copy of your system disk.
3. If you are using the distribution media to install the software, make sure that
you have a complete distribution kit. Each DECnet-ULTRIX distribution kit
consists of one or more volumes of software and a set of documentation. The
Bill of Materials (BOM) included in the kit specifies its contents. Compare
the items in the kit against those listed in the BOM.

If you are using an Internet network kit to install DECnet-ULTRIX, see
the ULTRIX Remote Installation Service for requirements. The Internet
network kit lets you install the software subsets on MicroVAX, VAXstation,
and DECstation 3100 products over the network.
4. Make sure you have a guest account in your system password file. The guest
account enables you to use DECnet-ULTRIX features without supplying
access control information. The default user account for DECnet-supplied
objects and the Gateway is defined as guest.

To define a guest account, log in as superuser and enter the adduser
command. When the command prompts you for the login name of the new
user, enter the name guest in lowercase. For example:

* adduser

Enter login name for new user (initials, first or last
name): gue st IJ3.§TI

The adduser command then prompts you for information about the new user.
For further instructions on using adduser to create a new account, see the
Guide to System Environment Setup in your ULTRIX documentation set.
Mter setting up the guest account, use the ULTRIX vipw command to enter
the string NoLogin in the password field. Otherwise, you will have a guest
account with no password.

5. Check if you are currently running DECnet. To do so, enter this command:

* ncp show executor

If the system display includes "State = On," then DECnet is running. Turn
DECnet off by entering the following command:

* ncp set executor state off

6. The DECnet installation procedure uses one of the following configuration
files:
•

Isys/conf/vaxl HOSTNAME, if you are installing DECnet-ULTRIX onto a
VAX system.

•

Isys/conf/mipslHOSTNAME, if you are installing DECnet-ULTRIX onto a

RISC system.

For the variable HOSTNAME, enter the name of your host in uppercase letters. Make sure that the communication device names and other information
in this configuration file are current.

Installing DECnet-UlTRIX onto a Node

2-3

7. Make sure that you know this information about your node:

•
•
•
•

Node name

,r<- ."',
\,,-_/

Node address
DECnet node identification
Device name

2.2 Installing or Reinstalling DECnet-ULTRIX
You can use either the DECnet-ULTRIX. software distribution media or an
Internet network kit to install DECnet-ULTRIX onto a node. Refer to the
ULTRIX Remote Installation Service and ris(8) in the ULTRIX Reference Pages,
Section 8, for information about setting up a network kit.
'lb start the installation script, first use cd to change the working directory to
root. Then enter the ULTRIX setld(8) (set load) command.

The setld command requires different options, depending on whether you are
installing the software for the first time or reinstalling it. Tables 2-2 and 2-3
summarize these options, and the next sections explain them in more detail.
Table 2-2:

Commands to Install DECnet-ULTRIX for the First Time

From the distribution media:
From a network kit:
From disk or CDROM:

Table 2-3:

Commands to Reinstall DECnet-ULTRIX

From the distribution media:
From a network kit:
From disk or CDROM:

2.2.1

setld -l/deVldevice
setld -I hostname:
setld -I/mount.."point

setld -d subset [...J
setld -l/deVldevice subset [... ]
setld -d subset [ ...]
setld -I hostname: subset [... J
setld -d subset [...]
setld -l/mountJJoint subset [... ]

Installing DECnet-ULTRIX for the First Time
•

If you are using the distribution media to install the software for the first
time, use the following setld format:
setld -I /dev/device

where
device

is the name of the device where you mount the distribution media.

For example:
:It cd / ~
:It /etc/set1d -1 /dev/rmtOh

2-4

Installing DECnet-ULTRIX onto a Node

•

If you are using a network kit over an Internet network to install the software
for the first time, use this setld fonnat:
setld -I hostname:

where
hostname

2.2.2

is the name of the host from which you are loading the software.

Reinstalling DECnet-ULTRIX
If you are reinstalling DECnet-ULTRIX, use setld with the -d option to delete
the product before installing it again. Then, restart the installation and specify
the DECnet-ULTRIX subsets you wish to reinstall using setld with the -I option.
For a more detailed explanation on how to use setld with the -d and -I options,
see Sections 2.8 and 2.9.

(

For more infonnation about setld(8), see the ULTRIX Guide to System
Environment Setup.

2.3 Mounting the Distribution Media
If you are installing DECnet-ULTRIX from the distribution media, the installation script tells you to make sure the media is mounted. The script then asks if
you are ready. When you have mounted the media, type y (yes) to answer the
question.
If you are installing the software from a CDROM disk, specify the mount point of
the disk. The DECnet kit is located in the c partition under the IVAX/DECNET
and IRISCIDECN ET subdirectories. Mount this partition before starting the
installation. For example, if your CDROM is in drive rz1 and the mount point
Imnt is free, you would enter the following commands:
•

If you are installing DECnet-ULTRIX onto a VAX system:
.:fI:
.:fI:

"
'
·
'
C
/

•

mount /dev/rzlc /mnt ~
set1d -1 /mnt/VAX/DECNET ~

If you are installing DECnet-ULTRIX onto a RISC system:
/dev/rzlc /mnt ~
set1d -1 /mnt/RISC/DECNET ~

.:fI: mount
.:fI:

2.4 Selecting the Software Subsets
If you are reinstalling DECnet-ULTRIX, skip this section and go to Section 2.5.
If you are installing DECnet-ULTRIX for the first time, the script asks you to
choose the software subsets that you want to install. Select the DECnet-ULTRIX
Base Software and any of the optional subsets:

Installing DECnet-ULTRIX onto a Node

2-5

*** ENTER SUBSET SELECTIONS ***
The subsets listed below are optional:
1) DECnet-ULTRIX Base Software
3) DECnet On-Line Manual Pages

2) DECnet-Internet Gateway
4) DECnet-ULTRIX Unsupported
Software

5) All of the above
6) None of the above
7) Exit without installing subsets
Enter your choice(s):

Type the numbers of the options that you want to install. If you type more than
one number, separate each number with a space, not a comma. Next, the script
allows you to verify your choice. For example:
You are installing the following subsets:
DECnet-ULTRIX Base Software
DECnet-Internet Gateway
DECnet On-line Manual Pages
DECnet-ULTRIX Unsupported
Software
Is this correct (yin)?

If you chose the wrong options, type n to indicate that the subsets are not correct;
the subset menu redisplays, and you can reselect your subsets. If you chose the
correct options, type y.

2.5 Copying the DECnet-ULTRIX Software
If you have not turned off DECnet, the installation script turns it off. The system
copies the software subsets to your disk and verifies them. If you are installing
more than one subset, the system copies and verifies the Base Software before
the Gateway or DECnet On-line Manual Pages software.
In this example, the script displays the following messages as it copies all the
software subsets onto a VAX system:
Copying DECnet-ULTRIX Base Software (DNUBASE400) from media
Verifying DECnet-ULTRIX Base Software (DNUBASE400)
Copying DECnet-Internet Gateway (DNUINETGW400) from media
Verifying DECnet-Internet Gateway (DNUINETGW400)
Copying DECnet On-line Manual Pages (DNUMAN400) from media
Verifying DECnet On-line Manual Pages (DNUMAN400)

;--"'\
",--//'

Copying DECnet-ULTRIX Unsupported Software (DNUUNS400) from media
Verifying DECnet-ULTRIX Unsupported Software (DNUUNS400)

NOTE

If you are installing DECnet-ULTRIX onto a RISC system, the prefix
DNP, rather than DNU, appears in the subsets.
If verification fails, look in lusrlvar/adm/fverifylog and letc/setldlog for information to help you correct the error. Make the correction and restart the installation
by using the setld command with the -I option. See Section 2.9 for details.

c
2-6

Installing DECnet-ULTRIX onto a Node

2.6 Configuring the Node for DECnet-ULTRIX Base Software
'Ib configure the node to run the DECnet-ULTRIX base software, the script
prompts you for your node name, node address, DECnet node identification,
and device name. If you need help responding to any of these prompts, type a
question mark ( ?) and press ~.
If you type the wrong answer for any question, you can change it by typing n
when asked to verify your answer. The procedure then redisplays the question so
that you can enter the correct information.
The script begins the configuration by displaying these informational messages:
Configuring the node to run DECnet-ULTRIX V4.0 base software.
You will be asked a few questions during the DECnet-ULTRIX V4.0
configuration.
If you need more information to answer a question, you can type ?
at the prompts, or consult the DECnet-ULTRIX Installation manual.
The DECnet library routines are now located in their own
library, -ldnet.

If you have not registered your DECnet-ULTRIX license, the script displays this
message:
*****************

WARNING

********************

* You have NOT registered the DECnet-ULTRIX License !!
* You will not be able to perform any remote access
* through DECnet-ULTRIX.
*
* In order to do remote access, use the lmf utility to
* register a licensed DECnet-ULTRIX PAK.
*

*
*
*
*
*

*
*
*

**********************************************************
[ Press the RETURN key to continue :]

This message is simply a reminder that you must register your DECnet-ULTRIX
license after the installation and configuration are complete. You do not have to
interrupt the configuration at this point.
The script then displays question 1:
The next question confirms that you are ready to configure your
system to run DECnet at this time. To configure DECnet you need to
know what your DECnet node name and address are. Also, if you want
to configure your DECnet nodes database during this configuration
process, you need to know the DECnet names and addresses of those
nodes you wish to define.
If you answer n (no) to this question now, you are told how
you can configure DECnet later.
1. Do you want to configure your system to run DECnet? (yin)

[y]:

'Ib answer "yes," press~. The script moves on to question 2.
If you do not wish to configure the system to run DECnet, answer "no" by typing
n. The following message appears before you automatically exit the script:

You chose not to configure your system to run DECnet at this time.
If you decide to configure DECnet later, issue the command:
setld -c DNUBASE400 INSTALL

Installing DECnet-ULTRIX onto a Node

2-7

If you are installing DECnet-ULTRIX onto a RISC system, the installation
displays this command instead:
setld -c DNPBASE400 INSTALL

With question 2, the script prompts you for your DECnet node name.
2. What is your DECnet node name (1-6 chars)? []: node
Your node name is node
Is this correct? (yin)

[n]:

Enter a node name of 1 to 6 alphanumeric characters, including at least one
alphabetic character. If possible, use the same node name that you specified
as your Internet host name when you installed ULTRIX. Consult your DECnet
network manager before choosing your node name and address. Respond by
typing a y or n, as appropriate.
3. What is your DECnet node address (aa.nnnn)? []: aa.nnnn

Your node address is aa.nnnn
Is this correct? (yin)

[n]:

Your DECnet node address consists of an area number, a period, and a node
number. The area number is a decimal integer from 1 to 63; the node number is
a decimal number from 1 to 1023. Note that this address is different from your
Internet host address. Respond by typing a y or n, as appropriate.
4. What is your DECnet Node Identification string? (1-32 chars) []: identification string ~
Your node identification string is
identification string

Is this correct? (yin)

,/ ".

[n]:

Enter a string of 1 to 32 ASCII characters. You can include blanks but not shell
metacharacters (! ? ' " *). The node identification string is a short message that
appears next to the node ID in network management displays. Its purpose is to
establish the node's identity on the network by indicating its type, use, users, or
some other distinguishing feature. Respond by typing a y or n, as appropriate.
5. What is the name of the device on which you will be
running the DECnet software (dev-c)? []: dev-c ~

The script asks question 5 only if it finds more than one DECnet-supported
network device in the system configuration file. The name of the configuration
file depends on the type of system (VAX or RISC) you have, as follows:
System Type

Configuration File Name

VAX

Isys/conf/vaxl HOSTNAME

RISe

Isys/conf/mipsl HOSTNAME

The variable HOSTNAME is the host name of your system in uppercase letters.
The device name consists of three alphabetic characters, a dash, and an integer
from 0 to 65535. Following is a list of the possible DECnet device names and
ULTRIX equivalents:

2-8

Installing DECnet-ULTRIX onto a Node

2.6.1

DECnet Device Name

Equivalent ULTRIX Device Name

una-n

den

qna-n

qen

dmc-n

dmcn

dmv-n

dmvn

sva-n

Inn

bnt-n

nin

xna-n

xnan

Configuring the DECnet Nodes Database
Each node has a DECnet nodes database that may contain the following information:

C'
/

•

The DECnet names and addresses for the nodes on your DECnet network.

•

The names, addresses, and down-line loading information for clients that you
add to a diskless environment.

If any nodes or diskless clients are already defined in your database, the installation procedure keeps the database and displays this message:
A nodes database has been found on your system and will be retained.
If you wish to define new nodes, use the ncp define node command after
the installation is complete.

If the database does not exist, the installation procedure gives you the option of
defining some DECnet nodes in the permanent nodes database. This message
appears:
This part of the installation procedure builds your DECnet nodes database.
Questions 6 and 7 prompt you for a DECnet node and address for each node
that you want to define in the database.
Questions 6 and 7 will reoccur until you type <RET> at question 6.

If you plan to copy an existing database from another node, define that node when
the script prompts you with questions 6 and 7. You add the node to your database
so you can access it later to copy its nodes database. Mter the installation, you
can use the update_nodes -f node command to copy the database. (The update_
nodes command is an unsupported utility in the DECnet-ULTRIX Unsupported
Software subset and documented in the DECnet-ULTRIX Release Notes.)
Questions 6 and 7 appear as follows:
6. Enter node name (1-6 chars or <RET> to continue): node

Enter a node name of 1 to 6 alphanumeric characters, including at least one
alphabetic character.
7. Enter node's node address (aa.nnnn): aa.nnnn

If you enter a node name or address incorrectly, just reenter both the node name
and address when the questions redisplay. The script deletes the error for you.

Installing DECnet-ULTRIX onto a Node

2-9

When you have finished entering the nodes in the database, press ~ in response
to question 6.
After installation, you can define nodes in the permanent database by using the
ncp define node command. Also, you can delete node names and addresses by
using the ncp purge node command. For more information, see the DECnetULTRIX Network Management manual and the DECnet-ULTRIX NCP Command

/~-"\
,

'--/

Reference.

2.6.2

Modifying System Files
The installation procedure then modifies your system files. This generally takes
no longer than 10 minutes.
Before the installation procedure edits any files, it saves each one in a file of the
name:
filename.savn

where n is a version number that is incremented on each installation.
As the script modifies the files, it displays the following messages, as appropriate:
Modifying rc.local
Creating DECnet proxy file, /etc/dnet-proxy
Initializing DECnet database
After verifying that the system is operating properly with DECnet
installed you may wish to remove the following saved file:
- /etc/rc.local.sav[n]

If a proxy file already exists on your system, the script does not display the
message about creating a proxy file. For information about creating a proxy file,
see the DECnet-ULTRIX Network Management manual.
If you have edited any system file to customize it prior to this installation, check
the new file to make sure the modifications are compatible with your previous
edits.

2.6.3

Preparing to Restart the Node
At this time, the installation procedure performs several checks and displays
information messages as needed. Before you start DECnet on the node, you may
need to make some final changes to your environment. For example:
•

If DECnet is not already configured into your ULTRIX kernel, the script
displays this message:
DECnet is not built into the currently running kernel. After
configuration, you should rebuild your kernel with DECnet and
then reboot to complete the installation.

This message is simply a reminder that you must rebuild the kernel when the
configuration is complete. Do not interrupt the configuration to rebuild the
kernel.
'lb add DECnet to the kernel, specify "options DECNET" and "pseudo-device
decnet" in the appropriate configuration file and rebuild the kernel.
•

If DECnet has already been configured into your kernel, the script reminds
you to start DECnet:
8. Do you want to start DECnet now (y/n)? [y]:

2-10

Installing DECnet-ULTRIX onto a Node

Press ~ or type y to answer "yes". If you answer "yes", the script automatically starts DECnet for you. If you answer "no", the script displays this
message:
You can turn DECnet on manually by rebooting your system
or by entering the following command:
/usr/bin/ncp set exec state on

•

If you have a lat control program (lcp) command line in letc/rc.local, the
script displays this message:
Alat control program (lcp) command line was found in
/etc/rc.local. When this procedure is finished, you should
edit rc.local and move the lcp line(s) to follow the ncp command.
If the lcp command precedes the ncp command, your lat terminal
lines may not work properly.

•

If you do not have a guest account in your system, the script displays this
message:
There is no guest account in your system.
If you wish to access
this system from remote systems, you should have a guest account
specified. A guest account is needed for the proper operation of
dlogind, dtermd, and dtr.

You should set a password for this account to prevent unauthorized
access to your system.

If you need instructions on how to create a new account, see the ULTRIX
Guide to System Environment Setup.

•

If you have not already registered your software license, the script displays
this message:
Don't forget to register your DECnet-ULTRIX PAK
(Product Authorization Key) using lmf. Otherwise
you won't be able to access remote systems.
After you register your DECnet-ULTRIX PAK, you must
either reboot or issue the following commands:
/usr/etc/lmf reset
/usr/bin/ncp set exec state on

When you start DECnet, your system displays the following message:
starting DECnet

Your system comes up with the executor and circuit states set to on, as reported
by the following event messages:
Event type 2.0, Local node state change
Occurred 12-0CT-90 16:47:30.0 on node aa.nnnn (NODE)
Operator commands
Old state = off
New state = on
Event type 4.10, Circuit up
Occurred 12-0CT-80 16:47.32.0 on node aa.nnnn (NODE)
Circuit DEV-C
Adjacent node = aa.nnnn (NODE)

The default logging device for all events is the console. For instructions on how to
disable logging or redirect it to another device, see the DECnet-ULTRIX Network
Management manual.

Once your DECnet-ULTRIX node is running, you can log in and use the checkout
procedure as described in Chapter 4. This procedure tests your node's operation
in the network.
Installing DECnet-ULTRIX onto a Node

2-11

2.7 Configuring the Node to Run Gateway Software
If you chose to install the DECnet-Internet Gateway subset, the script now
configures the node to run the DECnet-Internet Gateway software.
The script begins with question 1, which reads as follows:
The next question confirms that you are ready to configure your system
to run the DECnet-Internet Gateway at this time. In order to run the
Gateway you must have already configured your system to run DECnet.
The configuration procedure asks no questions.
If you decide not to
configure the Gateway at this time you will be told how to configure
it at a later date.
1. Do you want to configure your system to run the
DECnet-Internet Gateway? (y/n) [y]:

To answer lIyes,II press~. The script stops asking questions.
If you do not wish to configure the system to run the DECnet-Internet Gateway,
answer IIno to question 1. The following message appears before you automatically exit the script:
ll

You chose not to configure your system to run the Gateway at this
time. If you decide to configure the Gateway at a later date, you
can issue the command:
setld -c DNUINETGW400 INSTALL

If you are installing DECnet-ULTRIX software onto a RISC system, the
installation displays this command instead:
setld -c DNPINETGW400 INSTALL
ll

If you answer lIyes to question 1, the installation script edits the /etc/inetd.conf
file and displays this message:
The file /etc/inetd.conf will be edited to use
/usr/etc/ftpd.gw and /usr/etc/telnetd.gw instead
of /usr/etc/ftpd and /usr/etc/telnetd.
Editing /etc/inetd.conf
After verifying that the system is operating properly as a
gateway you may wish to remove the following saved file:
- /etc/inetd.conf.sav[n]

NOTE

If you are installing the DECnet-ULTRIX Base Software and DECnetInternet Gateway software for the first time, you must reboot the
system to start the Gateway. If DECnet-ULTRIX was previously
installed and you are installing only the Gateway, you can either kill
and restart inetd without rebooting or send a hang-up signal to the
inetd daemon.
The DECnet-Internet Gateway, by default, is configured as a bidirectional
gateway, with access enabled in two directions: from DECnet to Internet systems,
and from Internet to DECnet systems. When the installation and configuration
are complete, you can configure the DECnet-Internet Gateway as a unidirectional
gateway by disabling either DECnet-to-Internet or Internet-to-DECnet access.
See the DECnet-Internet Gateway Use and Management manual for specific
instructions on how to do this.

2-12

Installing DECnet-ULTRIX onto a Node

2.8 Deleting the DECnet-ULTRIX Software
1b delete the DECnet-ULTRIX software from your system, log in as superuser
and issue the setld command with the -d option, as follows:
setld -d subset [. .. J

where
subset

is the name of the DECnet-ULTRIX software subsets that you are
deleting. If you are reinstalling subsets, delete any subsets that you
are reinstalling. You can include the names of one or more of the
DECnet-ULTRIX subsets, as shown in the following table:
Subset Names for subset Variable

Software Subset

For VAX Systems

For RISe Systems

DECnet-ULTRIX Base Software

DNUBASE400

DNPBASE400

DECnet-Internet Gateway
Software

DNUINETGW400

DNPINETGW400

DECnet On-Line Manual Pages

DNUMAN400

DNPMAN400

DECnet-ULTRIX Unsupported
Software

DNUUNS400

DNPUNS400

If you select any of the optional subsets, make sure you list them before the
base subset. The following command deletes the DECnet-Internet Gateway, the
On-Line Manual Pages, and the Base Software from a VAX system:

( '"
/

# /etc/setld -d DNUINETGW400 DNUMAN400 DNUBASE400

The system lists the subsets you are deleting. It then asks if you want to delete
the DECnet database:
Do you want to delete the DECnet database from
your system (yin)?

Answer y (yes) to remove the DECnet database from lusr/lib/dnet. The system
then displays the following messages:

The nodes database (/usr/lib/dnet/nodes-p and /usr/lib/dnet/nodes_v)
has been retained for possible use by MOP. These files can be
deleted manually if they are not needed.
Your DECnet software subset has been deleted.
You may also want to remove the following saved file:
- /etc/rc.local.sav[n]

Note that the files nodes_v and nodes_p, which contain down-line loading
information, are not removed when you delete the DECnet database. However,
you can remove them separately.

2.9 Restarting the Installation
You can restart the installation by entering setld with the -I option and specifying
the DECnet-ULTRIX subsets that you want to reinstall:

0 ,',

setld -I Idev/device subset [. .. J

I',

Installing DECnet-ULTRIX onto a Node

2-13

where
IdevIdevice

is the name of the distribution media from which you are
loading the software.

subset

is the name of the DECnet-ULTRIX software subset that you
are installing. You can include the names of one or more of the
DECnet-ULTRIX subsets, as shown in the following table:
Subset Names for subset Variable

Software Subset

For VAX Systems

For RISe Systems

DECnet-ULTRIX Base Software

DNUBASE400

DNPBASE400

DECnet-Internet Gateway
Software

DNUINETGW400

DNPINETGW400

DECnet On-Line Manual Pages

DNUMAN400

DNPMAN400

DECnet-ULTRIX Unsupported
Software

DNUUNS400

DNPUNS400

If you install any of the optional subsets with the base software, list the base
software subset first. The following command deletes the Base Software and the
DECnet-Internet Gateway from a VAX. system:

'#* cd
/ ~
/etc/set1d -1 /dev/rmtOh DNUBASE400 DNUINETGW400

Notice that when you restart an installation, the order in which you list the
subsets is opposite to the order in which you list them during a deletion.

2.10 Correcting Errors After the Installation Is Complete
This section describes how to correct errors after the installation is complete.
For information on how to correct minor errors during the installation, see the
respective sections in this chapter that describe the steps in the installation
process. All such sections contain instructions for correcting errors.
If you receive an error message when you reboot the node, look in the
lusrllib/dnet/ncp.log file. The only errors you are likely to find when you
reboot are ncp errors. You will be notified of any other errors as they occur.
If the installation software detects a serious error, it displays a message on your
terminal and stops the procedure. In the event that the procedure stops, look for
error messages in letc/setldlog. When you have corrected the problem, restart
the installation as described in the next paragraph.
After correcting any installation errors, restart installation by entering the setld
command with the -I option. You will reinstall only the subsets that did not
install correctly the first time. For a more detailed explanation of how to use the
setld command with the -I option, see Section 2.9.

2.11

Verifyi ng the Installation
To verify that DECnet-ULTRIX. has been installed correctly on your node, run the
checkout procedures described in Chapter 4. These procedures test whether your
node can communicate with itself and with other nodes on the network. Before
you begin testing your node, complete any postinstallation tasks that the script
reminded you to do. For details, refer to Section 2.6.3.

2-14

Installing DECnet-ULTRIX onto a Node

Chapter 3

Installing DECnet-ULTRIX into a Diskless
Environment
If you are installing DECnet-ULTRIX software for a client to use in a diskless
environment, be sure to make the following preparations:

•

Designate a server node for the DECnet-ULTRIX installation.

•

Make sure that the diskless environment already exists on the server node.

•

Check that each registered client is licensed to use the software that the
server provides.

You can add registered clients to the diskless environment either before or after
installing DECnet-ULTRIX software. Each client is configured when you boot it
for the first time after you install DECnet-ULTRIX software on the server.
To install DECnet-ULTRIX software into a diskless environment, run the
Diskless Management Services (dms) utility from the server node. (You can run
dms only on the server.) The following sections describe the full procedure.

Before starting with the installation, make sure you meet the requirements
outlined in the next section.

3.1

DECnet-ULTRIX Diskless Installation Requirements
To install DECnet-ULTRIX into a diskless environment, you must meet the
requirements in Table 3-1.

o
Installing DECnet-ULTRIX into a Diskless Environment 3-1

Table 3-1:

DECnet-ULTRIX Diskless Installation Requirements
Requirements
For VAX Systems

For RISe Systems

DECnet-ULTRIX V4.0
Distribution media

1 1600-bpi nine-track magnetic tape, CDROM, or 1 TK50
cartridge

1 1600-bpi nine-track magnetic
tape, CDROM, or 1 TK50 cartridge

Diskless environment (OS)

ULTRIXV4.0

Installed software

ULTRIX V4.0 Base Software
(ULTBASE400)

ULTRIX V4.0 Base Software
(UDTBASE400)

ULTRIX V4.0 Kernel
Configuration Files (ULTBIN400)

ULTRIX V4.0 Kernel Configuration
Files (UDTBIN400)

Privileges

Superuser

Disk space during installation

1750 KB in the environment

2730 KB in the environment

+ 15 KB per client root file
system

+ 15 KB per client root file system

Disk space after installation

Same as during installation

Estimated time

30 minutes for base installation

Software Subset

DECnet-ULTRIX. Base
Software

DECnet-Internet Gateway
Installed software

Additional Requirements
DECnet-ULTRIX V4.0 Base
Software (DNUBASE400)

DECnet-ULTRIX V4.0 Base
Software (DNPBASE400)

ULTRIX V4.0 Communications
Utilities (ULTCOMM400)

ULTRIX V4.0 Communications
Utilities (UDTCOMM400)

Disk space

205 KB in lusr

340 KB in lusr

Estimated Time

5 to 10 minutes

DECnet-ULTRlX On-Line
Manual Pages
Installed software

Additional Requirements
DECnet-ULTRIX V4.0 Base
Software (DNUBASE400)

DECnet-ULTRIX V4.0 Base
Software (DNPBASE400)

ULTRIX V4.0 On-Line Manual
Pages (ULTMAN400)

ULTRIX V4.0 On-Line Manual
Pages (UDTMAN400)

Disk space

135 KB in lusr/man

Estimated time

5 minutes

DECnet-ULTRlX Unsupported
Software

Additional Requirements

Installed software

DECnet-ULTRIX V4.0 Base
Software (DNUBASE400)

DECnet-ULTRIX V4.0 Base
Software (DNPBASE400)

Disk space

370 KB in /usr

535 KB in /usr

Estimated time

5 minutes

3-2

Installing DECnet-ULTRIX into a Diskless Environment

Before you install DECnet-ULTRIX. into a diskless environment on a server node:

C"":
J"

1. Set up a diskless environment for the clients. This is equivalent to installing
ULTRIX V4.0 software for the clients. See the ULTRIX Guide to Diskless
Management Services for details.
2. Make sure you have enough free disk space to install the software subsets of
your choice. To check the available disk space in the environment or the root
file system, enter the df command. For example:
# df /usr/var/diskless/dlenvO

# df /usr/var/diskless/dlclientO

3. Make a backup copy of the diskless environment.
4. Make sure you have the complete software distribution kit. Each DECnetULTRIX kit consists of one or more volumes of software and a set of
documentation. The Bill of Materials (BOM) included with the kit specifies
its contents. Compare the items in the kit with those listed in the BOM.

5. If DECnet-ULTRIX is already installed in the diskless environment, log in to
each client using that environment and turn DECnet off. Do not turn DECnet
off on the server node.

3.2 Running the DECnet-ULTRIX Diskless Installation Procedure
To start the DECnet-ULTRIX diskless installation procedure, log in to the server
node as superuser. Then change to the root directory (/) and start the Diskless
Management Service (dms) utility:
# cd /

# dms

~
~

The dms utility displays a licensing notice, then prompts you for the superuser
password. When you type the superuser password and press~, dms displays a
menu of its services:
DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU

",
C
/

a - Add Client Processor
m - Modify Client Parameters
r - Remove Client Processor
1 - List Registered Clients
s - Show Products in Diskless Environments
i-Install Software
c - Create Diskless Area on Disk
k - Kernel Rebuild or Copy
e - Exit
Enter your choice:

NOTE

Either before or after you install DECnet-ULTRIX, define the client
nodes on which you will be using DECnet-ULTRIX. The a option
defines a client. Refer to the ULTRIX documentation for more
information about defining or adding clients.

o
Installing DECnet-ULTRIX into a Diskless Environment 3-3

To install DECnet-ULTRIX, type the i option at the prompt. This menu appears:
1 Install Operating System to New Area
2 Add Software to Existing Area
3 Return to Previous Menu

\\0,
, y.

Enter your choice:

Choose option 2 to add DECnet-ULTRIX to an existing diskless area that already
contains an operating system. This message appears with a list of the installation
directories available:
You have chosen to install additional software into an existing diskless
environment. These are the available installation directories:
1 /dlenvO/rootO.vax
2 /dlenvO/rootO.mips
3 /dlenvl/rootl.mips
Enter your choice:

Choose the diskless environment into which you want to install the software by
typing the appropriate option and pressing ~.
Next, dms prompts you for the name of the device special file or the mount point
of the distribution media:

Enter the device special file name or mount point of the
distribution media, for example, /dev/rmtOh

If the distribution kit is on a TK50 cartridge tape or a magnetic tape, enter the
device special file name.
If the kit is on a CDROM disk, specify the mount point of the disk. The DECnetULTRIX kit is located in the c partition. Mount this partition before starting
the installation (if you have not already mounted the partition, press ICTRUZ I to
suspend the installation, type the mount command, and type fg to resume the
installation). For example, if your CDROM is in drive ra1 and the mount point
Imnt is free, you would enter this mount command:
# mount /dev/ralc /ront

If diskless clients have already been added to the chosen diskless environment,
the dms utility asks the following question:
The product software will automatically by propagated to every
registered client.
Is that all right? (y/n):

If you answer yes, dms copies the software to each diskless client. If you answer
no, dms terminates the installation.

3.3 Selecting Software Subsets
The script then asks you to choose the software that you want to install: the
DECnet-ULTRIX Base Software, the DECnet-Internet Gateway software, the,
DECnet On-Line Manual Pages, the DECnet-ULTRIX Unsupported Software, or
all four subsets:

c
3-4

Installing DECnet-ULTRIX into a Diskless Environment

*** ENTER SUBSET SELECTIONS ***
The subsets listed below are optional.
1) DECnet-ULTRIX Base Software
3) DECnet On-Line Manual Pages

2) DECnet-Internet Gateway
4) DECnet-ULTRIX Unsupported
Software

5) All of the Above
6) None of the Above
7) Exit without installing subsets
Enter your choice(s):

Type the number of the option that you want to install. If you type more than
one number, separate each number with a space, not a comma. Next, the script
allows you to verify your choice. For example:
You are installing the following subsets:
DECnet-ULTRIX Base Software
DECnet On-Line Manual Pages

DECnet-Internet Gateway
DECnet-ULTRIX Unsupported
Software

Is this correct (yin)?

If you chose the wrong option, type n to indicate that the subsets are not correct.
The subset menu redisplays, and you can reselect your subsets. If you chose the
correct option, type y.
The installation script then copies and verifies the software subsets. If you are
installing all subsets, it copies and verifies the base software, then the other
subsets.

In this example, the script displays the following messages as it copies all the
software subsets onto a VAX system:
Copying DECnet-ULTRIX Base Software (DNUBASE400) from media
Verifying DECnet-ULTRIX Base Software (DNUBASE400)
Copying DECnet On-Line Manual Pages (DNUMAN400) from media
Verifying DECnet On-Line Manual Pages (DNUMAN400)
Copying DECnet-Internet Gateway (DNUINETGW400) from media
Verifying DECnet-Internet Gateway (DNUINETGW400)
Copying DECnet-ULTRIX Unsupported Software (DNUUNS400) from media
Verifying DECnet-ULTRIX Unsupported Software (DNUUNS400)

NOTE

If you are installing DECnet-ULTRIX onto a RISC system, the prefix
DNP, rather than DNU, appears in the subsets.
If verification fails, look in the diskless environment's lusr/var/adm/fverify log file
for information to help you correct the error. Make the correction and restart the
installation by using the dms utility. See Section 3.2 for details.

3.4 Configuring the Client for DECnet-ULTRIX Base Software
Clients are configured when you boot them for the first time after you install
DECnet-ULTRIX software on the server. This section describes the configuration
script.

'1
,1'\

If you type the wrong answer for any question, you can change it by typing n
when asked to verify your answer. The procedure then redisplays the question so
that you can enter the correct information. If you need help responding to any of
these prompts, type a question mark (? ) and press ~.
Installing DECnet-ULTRIX into a Diskless Environment

3-5

The script begins the configuration by displaying some informational messages:
Configuring the node to run DECnet-ULTRIX V4.0 base software.
You will be asked a few questions during the DECnet-ULTRIX V4.0
configuration.
If you need more information to answer a question, you can type ?
at the prompts, or consult the DECnet-ULTRIX Installation manual.
The DECnet library routines are now located in their own
library, -ldnet.

If you have not registered your DECnet-ULTRIX license, the script displays this
message:
*****************

WARNING

********************

*
* You have NOT registered the DECnet-ULTRIX License !!
* You will not be able to perform any remote access
* through DECnet-ULTRIX.
*
* In order to do remote access, use the lmf utility to
* register a licensed DECnet-ULTRIX PAK.
*

*
*
*
*
*
*
*
*

**********************************************************
[ Press the RETURN key to continue :]

This message is simply a reminder that you must register your DECnet-ULTRIX
license after the installation and configuration are complete. You do not have to
interrupt the configuration at this point.
The script then displays question 1:
The next question confirms that you are ready to configure your
system to run DECnet at this time. To configure DECnet you need to
know what your DECnet node name and address are. Also, if you want
to configure your DECnet nodes database during this configuration
process, you need to know the DECnet names and addresses of those
nodes you wish to define.
If you answer "no" to this question now, you will be told how you can
configure DECnet later.
1. Do you want to configure your system to run DECnet? (yin)

[y]:

To answer "yes," press~. The script moves on to question 2.

If you do not wish to configure the system to run DECnet, answer "no" by typing
n. The following message appears before you automatically exit the script:
You chose not to configure your system to run DECnet at this time.
If you decide to configure DECnet later, issue the command:
setld -c DNUBASE400 INSTALL

If you are installing DECnet-ULTRIX software onto a RISC system, the
installation displays this command instead:
setld -c DNUBASE400 INSTALL

With question 2, the script prompts you for your DECnet node name:
2. What is your DECnet node name (1-6 chars)? []:

node

Your node name is node
Is this correct? (yin)

3-6

[n]:

Installing DECnet-ULTRIX into a Diskless Environment

To specify the client's DEC net node name, enter a node name of 1 to 6 alphanu-

meric characters, including at least one alphabetic character. If possible, use the
same node name that you specified as your Internet host name. Consult your
DECnet network manager before choosing your node name and address. Respond
by typing a y or n, as appropriate.
3. What is your DECnet node address (aa.nnnn)? []: aa.nnnn

Your node address is aa.nnnn
Is this correct? (yin)

en]:

Your DECnet node address consists of an area number, a period, and a node
number. The area number is a decimal integer in the range of 1 to 63; the node
number is a decimal number from 1 to 1023. Note that this address is different
from your Internet host address. Respond by typing a y or n, as appropriate.
4. What is your DECnet Node Identification string (1-32 chars)? [J: identification string ~
Your node identification string is

identification string
1

~/"

Is this correct? (yin)

en]:

The device name consists of three alphabetic characters, a dash, and an integer
from 0 to 65535. Here is a list of the possible DECnet device names and ULTRIX
equivalents:

3.4.1

DECnet Device Names

Equivalent ULTRIX Device Names

qna-nn

qenn

dmv-nn

dmvnn

Bva-nn

Inn

xna-nn

xnan

Configuring the DECnet Nodes Database
The root area for each client in a diskless environment contains a DECnet node
database. The DECnet node database contains the DECnet names and addresses
for the nodes on your DECnet network. If any nodes are already defined in
your database, the installation procedure keeps the database and displays this
message:
A nodes database has been found on your system and will be retained.
If you want to define new nodes, use the ncp define node command after
the installation is complete.

If the database does not exist, the installation procedure gives you the option of
defining some DECnet nodes in the permanent nodes database. This message
appears:

Installing DECnet-ULTRIX into a Diskless Environment

3-7

This part of the installation procedure builds your DECnet nodes database.
Questions 6 and 7 prompt you for a DECnet node and address for each node
that you want to define in the database.
Questions 6 and 7 will reoccur until you type <RET> at question 6.

Enter a node name of 1 to 6 alphanumeric characters, including at least one
alphabetic character.
7. Enter salem's node address (aa.nnnn): aa.nnnn ~

The DECnet node address consists of an area number, a period, and a node
number. The area number is a decimal integer from 1 to 63; the node number is
a decimal number from 1 to 1023. Note that this address is different from the
Internet host address.
If you enter a node name or address incorrectly, just reenter both the node name
and address when the questions redisplay. The script deletes the error for you.
When you have finished specifying the nodes in your network, press ~ in
response to question 6.
Mter installation, you can define nodes in the client's permanent database with
the ncp define node command. Also, you can delete node names and addresses
with the ncp purge node command. For more information, see the DECnetULTRIX Network Management manual and the DECnet-ULTRIX NCP Command
Reference.

3.4.2

Modifying System Files
The installation procedure then modifies the client's system files. This generally
takes no longer than 10 minutes.

Before the installation procedure edits any files, it saves each one in a file of the
name:
filename.savn

3-8

Installing DECnet-ULTRIX into a Diskless Environment

If any of the client's system files were edited to customize them prior to this
installation, check the new files to make sure the modifications are compatible
with your previous edits.

3.4.3 Preparing to Start the Client
At this time, the installation procedure performs several checks and displays
informational messages as needed. Before you start DECnet on the client, you
may need to make some final changes to your environment. For example:
•

If DECnet is not already configured into your ULTRIX kernel, the script
displays the following message:
DECnet is not built into the currently running kernel. After
configuration, you should rebuild your kernel with DECnet and
then reboot to complete the installation.

This message is simply a reminder that you must rebuild the kernel when the
configuration is complete. Do not interrupt the configuration to rebuild the
kernel.
To include DECnet in the kernel, specify "options DECNET" and "pseudodevice decnet" in the appropriate configuration file and rebuild the kernel.

•

If DECnet has already been configured into your kernel, the following
question is displayed:
8. Do you want to start DECnet now (y/n)? [y]:

Press ~ or type y to answer "yes". If you answer "yes," the script automatically starts DECnet for you. If you answer "no," the script displays this
message:

( ""

You can turn DECnet on manually by rebooting your system
or by entering the following command:

/usr/bin/ncp set exec state on

•

If you have a lat control program (lcp) command line in letc/rc.local, the
script displays this message:
A lat control program (lcp) command line was found in
/etc/rc.local. When this procedure is finished, you should
edit rc.local and move the lcp lines to follow the ncp command.
If the lcp command precedes the ncp command, your lat terminal
lines may not work properly.

•

If you need instructions on how to create a new account, see the ULTRIX
Guide to System Environment Setup.
•

If you have not already registered your software license, the script displays
this message:

Installing DECnet-ULTRIX into a Diskless Environment

3-9

Don't forget to register your DECnet-ULTRIX PAK
(Product Authorization Key) using lmf. Otherwise
you won't be able to access remote systems.
After you register your DECnet-ULTRIX PAK, you must
either reboot or issue the following commands:
/usr/etc/lmf reset
/usr/bin/ncp set exec state on

When you start DECnet, your system displays the following message:
Starting DECnet

Your system comes up with the executor and circuit states set to on, as reported
by the following event messages:
Event type 2.0, Local node state change
Occurred 14-0CT-90 16:34:30.0 on node aa.nnnn (NODE)
Operator commands
Old state = off
New state = on
Event type 4.10, Circuit up
Occurred 14-0CT-90 16:34:32.0 on node aa.nnnn
Circuit DEV-C
Adjacent node = aa.nnnn (NODE)

The default logging device for all events is the console. For instructions on how to
disable logging or redirect it to another device, see the DECnet-ULTRIX Network
Management manual.
Once your DECnet-ULTRIX node is running, you can log in and use the checkout
procedure as described in Chapter 4. This procedure tests your node's operation
in the network.

3.5 Configuring the System to Run the Gateway Software
If you chose to install the DECnet-Internet Gateway subset, the script must
configure each client to run the DECnet-Internet Gateway software. The clients
are configured when they are booted for the first time after the DECnet-ULTRIX
software has been installed on the server. The configuration script is described in
this section.

'-,

The script begins with question 1, which reads as follows:
The next question confirms that you are ready to configure your system
to run the DECnet-Internet Gateway at this time.
In order to run the
Gateway you must have already configured your system to run DECnet.
The configuration procedure asks no questions.
If you decide not to
configure the Gateway at this time you will be told how to configure
it at a later date.
1. Do you want to configure your system to run the
DECnet-Internet Gateway? (y/n) [y):

To answer "yes," press~. The script stops asking questions.
If you do not wish to configure the system to run the DECnet-Internet Gateway,
answer "no" to question 1. The following message appears before you automatically exit the script:
(-~

3-10

Installing DECnet-ULTRIX into a Diskless Environment

You ohose not to oonfigure your system to run the Gateway at this
time. If you deoide to oonfigure the Gateway at a later date, you
oan issue the oommand:
setld -0 DNUINETGW400 INSTALL

If you are installing DECnet-ULTRIX software onto a RISC system, the
installation displays this command instead:
setld -0 DNPINETGW400 INSTALL

If you answer "yes" to question 1, the installation script edits the letc/lnetd.conf
file and displays the following message:
The file /eto/inetd.oonf will be edited to use
/usr/eto/ftpd.gw and /usr/eto/telnetd.gw instead
of /usr/eto/ftpd and /usr/eto/telnetd.
Editing /eto/inetd.conf
After verifying that the system is operating properly as a
gateway you may wish to remove the following saved file:
- /eto/inetd.conf.sav[n]

NOTE

()

The DECnet-Internet Gateway, by default, is configured as a bidirectional
gateway, with access enabled in two directions: from DECnet to Internet systems,
and from Internet to DECnet systems. When the installation and configuration
are complete, you can configure the DECnet-Internet Gateway as a unidirectional
gateway by disabling either DECnet-to-lntemet or Internet-to-DECnet access.
See the DECnet-Internet Gateway Use and Management manual for specific
instructions on how to do this.

3.6 Correcting Errors After the Installation Is Complete
This section describes how to correct errors after the installation is complete.
For information on how to correct minor errors during the installation, see the
respective sections in this chapter that describe the steps in the installation
process. All such sections contain instructions for correcting errors.
If you receive an error message when you reboot the client, look in the
lusrllib/dnet/ncp.log file for the respective system. The only errors you are
likely to :find when you reboot are ncp errors. You will be notified of any other
errors as they occur during installation.
If the installation software detects a serious error, it displays a message on your
terminal and stops the procedure. In the event that the procedure stops, look for
error messages in letc/setldlog.
Mter you have corrected the problem, restart the installation by running dms, as
described in Section 3.2.

o
Installing DECnet-ULTRIX into a Diskless Environment 3-11

3.7 Verifying the Installation
To verify that DECnet-ULTRIX. has been installed correctly on your node, run the
checkout procedures described in Chapter 4. These procedures test whether your
node can communicate with itself and with other nodes on the network. Before
you begin testing your node, complete any postinstallation tasks that the script
reminded you to do. For details, see Section 3.5.3.

c
3-12

Installing DECnet-ULTRIX into a Diskless Environment

c
Chapter 4

Checking Your Node's Operation on the Network
After installing DECnet-ULTRIX software onto your ULTRIX system, you can
run a series of tests verifying that your node can communicate with itself and
other nodes on the network. If you want to test the performance of an operating
network, see the test procedures described in the DECnet-ULTRIX Network
Management manual.

4.1

Overview of Checkout Tests
You can connect your node to a DECnet network using an Ethernet cable or
a DDCMP point-to-point line. Figure 4-1 depicts a DDCMP point-to-point
connection; Figure 4-2 depicts an Ethernet connection.
Figure 4-1:

DDCMP Point-to-Point Connection

DDCMP
POINT-TO-POINT
DECnet-ULTRIX
NODE

VMS ROUTING
NODE

" " -__---'D~==~q. .___. .tr ~~TWORK
LKG-3694-891

o
Checking Your Node's Operation on the Network 4-1

Figure 4-2:

Ethernet Connection

DECnet-UL TRIX
NODE

1---. NETWORK
VMS ROUTING
NODE

LKG-04B2-87

You can use the checkout tests to verify both types of connections. If you have
both Ethernet and DDCMP point-to-point hardware on your node, first run the
checkout procedure on one device, then reconfigure the DECnet database and
run the procedure on the second device. See the DECnet-ULTRIX Network
Management manual for details about using ncp to list and define DECnet lines
and circuits.

Figures 4-3 through 4-8 illustrate the series of tests that make up the checkout
procedure. These figures illustrate tests on Ethernet connections; but tests on
DDCMP point-to-point connections run in the same paths and test the same
hardware components. Tests appear in the order you perform them (see steps 5,
6, and 7 in Section 4.2). In each figure, a broken line represents the test path for
any of the tests described in the following list.
1. Local node loopback test (Figure 4-3). Tests the local node software.

2. Controller loopback test (Figure 4-4). Tests operation of the local line
controller (do not perform this test if you are connected to the system over the
network or through LAT). Do not use this test on a diskless client.
3. Datalink loopback test to remote node (Figure 4-5). Tests the physical
connection to the Ethernet or DDCMP point-to-point wire and the remote
system line controller and/or the datalink software.
4. Node-Ievelloopback test to remote node (Figure 4-6). Tests your access
to the remote network software (remote object mirror).
5. DECnet file transfer to local node (Figure 4-7). Tests your access to the
local File Access Listener (fal).
6. DECnet file transfer to remote node (Figure 4-8). Tests your access to
the remote File Access Listener (fal). You can use this test to check access
from the Ethernet or a DDCMP point-to-point wire through a routing node to
another remote node.
4-2

Checking Your Node's Operation on the Network

Figure 4-3:

Local Node Loopback Test

ETHERNET
LOCAL NODE

I L~OP~R I
I MIRROR I
,

REMOTE NODE

LKG-0267-87

C'"

Figure 4-4:

Controller Loopback Test

LOCAL NODE

REMOTE NODE

LKG-369S-89I

o
Checking Your Node's Operation on the Network 4-3

Figure 4-5:

Datallnk Loopback Test to Remote Node

LOCAL NODE

LINE
CONTROLLER

I LOOPER[
REMOTE NODE

LKG-3696-891

Figure 4-6:

Node-Level Loopback Test to Remote Node

LOCAL NODE

ETHERNET

REMOTE NODE

LKG-0270-87

4-4

Checking Your Node's Operation on the Network

Figure 4-7:

DECnet File Transfer to Local Node

C~
ETHERNET
LOCAL NODE

~
I

REMOTE NODE

U<G-0271-87

Figure 4-8:

DECnet File Transfer to Remote Node

ETHERNET
LOCAL NODE

REMOTE NODE

U<G-0272-87

o
Checking Your Node's Operation on the Network

4-5

4.2 DECnet-ULTRIX Installation Checkout Procedure
To perform the checkout procedure described in this chapter, you must be a
superuser and have a guest account on your system. The following pages describe
each step in the checkout procedure and include examples of user input (red type)
and system output (black type).

Follow the instructions and answer the questions that display on your terminal.
If you need more information to answer a question, enter a question mark (?) at
the prompt. Enter ICTRUZI to interrupt the test at any time. When you are ready to
resume the checkout procedure, enter 19.
Press ~ to end all input lines. If you press ~ without entering any input, the
script prompts you again, unless you are waiving a password specification (see
step 6).
If the checkout program detects an error, it instructs you to use an ncp command
to correct it. For more information about ncp, refer to the DECnet-ULTRIX
Network Management manual.

"-.

1. Enter lusrletc/dnet_check. If you do not have a guest account set up on

your system, the checkout program displays a message and exits so that you
can create one. Once the checkout program confirms that you have a guest
account, it displays some introductory text and then checks to see that dcp,
drm, and ncp are properly installed. If they are not, the checkout program
displays a message. You must then reinstall DECnet on your ULTRIX system
before continuing (see Chapter 2 for basic installation procedures and Chapter
3 if you are installing DECnet-ULTRIX into a diskless environment).
2. If dcp and ncp are properly installed, the checkout program prompts you to
specify the device that you want to test (UNA-n, QNA-n, DMC-n, DMV-n,
BNT-n, SVA-n, or XNA-n, where n is a value from 0 to 65535). The program
then displays swnmary information showing the device and its state, as in
the following example:
Enter communication device to be tested (dev-c): una-O

Line Volatile Summary as of Tue Mar 26 10:57:30 EST 1990
Line

State

UNA-O

3. Next, the program prompts you to enter the name of your local node for use
in the first series of tests. If you are not sure of your node name, enter ICTRIJZI
and execute the ncp show executor command.
If you enter a name that is not defined in the database, the program displays
a message and exits. If the error was a typing mistake, rerun dnet_check
and enter the correct name. If the local node is not defined in the database,
use the ncp set node command to define the local node before you rerun
dnet_check.
When you enter a valid local node name, the program displays summary
information about the node.
Enter the name of your local node: boston

Node Volatile Summary as of Tue Mar 26 10:59:45 EST 1990
Executor node

3.18 (BOSTON)

Identification

4-6

C-"'·'
.

State = On
DECnet-ULTRIX System

Checking Your Node's Operation on the Network

4. The checkout program prompts you to enter the name of a remote node
for use in testing. Specify a DECnet node on your Ethernet or DDCMP
point-to-point wire. You can display a list of known nodes by enteringlcTRuzl
and executing the ncp show known nodes command. This command lists
all nodes known to your node, which can include those beyond your local
Ethernet or DDCMP point-to-point wire. You must remember which nodes
are on your local wire and specify one of those for the test.
Enter the remote node to be used in test:
Stopped
:ff: ncp show known nodes ~

ICTRUZI

Known Node Volatile Summary as of Tue Mar 26 10:59:45 EST 1990
Executor node =

3.18 (BOSTON)

State = On
Identification
DECnet-ULTRIX System
Node
State
Active
Delay
Circuit
Links
UNA-O
UNA-O
UNA-O

3.20 (SALEM)
3.21 (WESTON)
3.22 (GROTON)

Next Node

3.4 (STOW)
3.4 (STOW)
3.4 (STOW)

:ff: fg ~
dnet check
salem

If you enter a name that is not defined in the database, the checkout
procedure displays a message and exits. If the error was a typing mistake,
or if you want to specify a different remote node that is defined, rerun
dnet_check. If you want to use a remote node not currently defined in the
database, use the ncp set node command to define the node before you rerun
dnet_check.
When you enter a valid remote node name, the system displays summary
information for that node. If your Ethernet has a designated router, its name
appears in the Next Node field of the display.
Node Volatile Summary as of Tue Mar 26 10:59:45 EST 1990
Node
Links

State

3.20 (SALEM)

Active

Delay

Circuit

Next Node

UNA-O

3.4 (STOW)

5. Mter you have specified both the local node and a remote node, the checkout
program begins a series of tests (see Figures 4-3 through 4-8). As it performs
each test, the program displays the actual ncp commands that it is executing.
The program gives you the option to bypass the second test, which is a
controller loopback test. This test disconnects the communications device
from the Ethernet or DDCMP point-to-point wire. Do not perform the
test while connected to the host over the network using LAT (Local Area
Transport), rlogin, or dlogin. Do not perform the test if you are a diskless
client.
If all tests are performed and all succeed, the program displays the following
sequence of test reports:

o
Checking Your Node's Operation on the Network

4-7

Performing local DECnet node loopback tests.
ncp loop executor
ncp loop node boston length 1 count 10 with zero
ncp loop node boston length 2047 count 50
Warning:

answer "no" to this question if you are
running as a diskless client, or you
are logged in from a terminal server (LAT)
as you will lose your file system and/or
all currently connected LAT connections!

Do you want to perform a controller loopback test on
device una-O? (y == yes, n = no) Y .I!!§!J
ncp set line una-O controller loopback
ncp loop circuit una-O count 10 length 1486
ncp set line una-O controller normal
Performing datalink loopback tests to node salem.
ncp loop circuit una-O node salem length 5 count 20 with
ones
ncp loop circuit una-O node salem length 1486 count 20
Performing node level loopback tests to node salem.
ncp loop node salem length 1 count 10 with zero
ncp loop node salem count 50

If a test fails, follow these suggestions for isolating the error condition:

•

Verify that the node is up on the network. Check the display
resulting from the ncp show executor command to determine the state of
the local node. If the executor node state is off, issue an ncp set executor
state on command to turn the executor on.

To check the state of a remote node, consult the system manager for that
node.
•

Verify that the circuit is turned on. Check the display resulting from
the ncp show circuit command to determine the circuit's state. If the
circuit state is off, execute an ncp set circuit circuit-id state on command
to turn the circuit on.
If the circuit is on, check with the system manager at the remote node to
see if the remote node is up on the network and to make sure that access
control for the remote mirror is set properly.

4-8

•

Verify that your device is correctly connected to the Ethernet or
DDCMP point-to-point wire. Make sure the DDCMP wire is connected
to the controller board, or that the Ethernet wire is connected to the
transceiver or DELNI or DECOM.

•

Verify that access control for the target system's mirror object
is properly set. Check with the system manager on the target node to
verify that connections can be made to the object mirror.

•

Verify that the service is properly enabled in the remote node, if
applicable.

•

Verify a problem with the remote node. Rerun the checkout tests
with a different remote node, if possible, and notify the original remote
node of a possible problem.

•

Verify that the device's vector and csr switches are set to the
correct addresses. Make sure that the switch settings on the interface
board of your device match the addresses defined in the system configuration file for your system. For more information, consult the user's
guide for your device and refer to the ULTRIX system documentation for
information on building configuration files.

Checking Your Node's Operation on the Network

•

Device failure. Run the designated stand-alone diagnostics for the
device, or call your local field service representative.

•

Rebuild the kernel. Refer to the ULTRIX base system documentation
for details.

•

Reinstall DECnet. Follow the instructions in Chapter 2 if you are
installing DECnet-ULTRIX onto a node and Chapter 3 if you are
installing DECnet-ULTRIX into a diskless environment.

Mter you have corrected the error, rerun lusr/etc/dnet_check.
6. When the checkout program has successfully performed the preceding series
of tests, it displays instructions for a second set of tests. It prompts you to
enter the node name, user name, and password for the nodes you want to
test. Enter this information for your local node first (see Figure 4-7). When
you have completed that test, the program asks whether you want to test
another node. Enter the corresponding data for a remote node (see Figure
4-8). You can repeat this test for as many remote nodes as you want.

c
( '"
/

For security reasons, your response to the password prompt does not echo.
However, you can still display help information about passwords by typing a
question mark (?). If no password is required on the account, just press ~
If the program accepts your specification without a password, it displays a
message saying that it will not use a password in the test.
Mer you enter the data for the node you want to test, the program copies the
file dnet_check to the specified node and back again. The checkout program
then compares the contents of the original file to the one that was returned
during the test. If the two files differ or if the test fails for some other reason,
the program displays a message and prompts you for another node name.
When the test completes, the program deletes the test file from your directory.
If it cannot delete the test file, the checkout program displays a message
asking you to delete the file when you complete the checkout test procedure.
Enter name of node for test: boston ~
Enter user login-name on node boston: jean ~
Enter password for user jean on node boston: ~
dcp dnet check boston/jean/password/::dnetcheck.rnd
dcp bost~n/jean/password/::dnetcheck.rnd dnetcheck.lnd
cmp -s dnet check dnetcheck.lnd
drm boston/jean/password/::dnetcheck.rnd

7. Mter you have performed the test described in step 6 on your local node, you
can perform it on as many remote nodes as you want. When you are finished,
enter n in response to the prompt for another test.
Do you want to run this test with another
node? (y = yes, n = no) n I!!§!]
The installation test is finished.
Your current working directory is /etc.
:fI:

o
Checking Your Node's Operation on the Network

4-9

Appendix A

DECnet-ULTRIX Distribution Files
This appendix lists the DECnet-ULTRIX. distribution files by directory. Figure
A-I shows the overall structure of the directories.
Figure A-1:

DECnet-ULTRIX Directory Tree

c
/

I
I

usr

etc

lib

dnet_shared

bin

dnet

I
I
I

I
I

examples

include

deenet

n etd net

man

man1

man2 man3 manS

gatethru
LKG-3784-901

NOTE

Digital Equipment Corporation supplies some of the files discussed in
this appendix on an "as-is" basis for general customer use. Note that
Digital does not offer any support for them, nor does Digital cover them
under any of its support contracts.
Table A-I shows the DECnet-ULTRIX. distribution files by directory. The following key indicates which software subset each file belongs in:

0"
"

B = DECnet-ULTRIX. Base System
G = DECnet-Internet Gateway
U = Unsupported Utilities
M = On-Line Manual Pages

DECnet-ULTRIX Distribution Files

A-1

Table A-1:

DECnet-ULTRIX Distribution Flies by Directory

lusr/etc:
dlogindB

mira

dnet_checkB

evlB
falB

dnet_spawnera

ftpd.gwG

telnetd.gwG

GetnodeentServer
maillldv3B

update_nodesU

dtermd

dtro

nmlB

lusrllib:
libdnet_p.aB

libdnet.aB

lusrllib/dnet_shared:
area.txtB

exec.txtB

mod_xp5_ct~txtB

exec_ctr. tabB

circ.tabB
circ.txtB

exec_ctr. txtB

mod_xs5.tabB
mod_xs5.txtB

circ_ctr.tabB
circ_ctr.txtB

keyword_table. txtB
line.tabB

mod_xs9.tabB
mod_xs9.txtB

dap.errorsB

line.txtB

DECnet_release_notesB
DECnet-ULTRIX.PAKB

line_ctr.tabB

nm_help.txtB
node.tabB

dtshlp.ln~

dtsmsg.lngB
dtsprs.lngB
evl_errs. txtB
evl_evts.txtB
exec.tabB

line_ctr.txtB
log.txtB
mai111v3.fatalB
mod.txtB
mod_xac. tabB
mod_xac. txtB

node.txtB
node_ctr.tabB
node_ctr.txtB
obj.tabB
obj.txtB

mod_xp5.txtB

lusrllib/dnet:
dnet_vers B
exec_vB

lusrllibllint:
llib-Idnet.lnU

lusrlbin:
dcatB

llib-ldnetU

dCpB

drmB
dts B

netwatchU
nfiu

dloginB
dlsB

mai111v3B
ncpB

nodenameB
tellU

(continued on next page)

c
A-2

DECnet-ULTRIX Distribution Files

Table A-1 (Cont.):

DECnet-ULTRIX Distribution Files by Directory

lusr/exam.ples/decnet:
dnet_echol.cU

dnet_echo2.cU

tell.cU

dnet_echold.cu

dnet_echo2d.cu

TELL.COMu

Makefileu

READMEU

lusr/exam.ples/dli:
d1C802.cu

dlCeth.cU

dli_setsockopt.cU

dlC802d.cu

dlCethd.cu

lusr/exam.ples/decnetlgatethru:
gatewaydU
gatewayd.cu

lusr/manlmanl:

nodename.ldnM

dls.ldnM

dcat.ldnM

drm.ldnM

dcp.ldnM

nfi.ldnM
M

errors.ldn

tell.ldnM

accept.2dnM

getsockopt.2dnM

send.2dnM

bind.2dnM

listen.2dnM

setsockopt.2dnM

close.2dnM

read.2dnM

shutdown.2dnM

recv.2dnM

socket.2dnM

dlogin.ldn

lusr/manlmau2:

connect.2dnM

select.2dn

write.2dnM

dnet_addr.3dnM

dnet_htoa.3dnM

getnodeent.3dnM

dnet_conn.3dnM

dnet_ntoa.3dnM

getnodename.3dnM

getpeemame.2dn

getsockname.2 dnM

lusr/manlman3:

nerror.3dnM

dnet_otoa.3dnM

dnet_eof.3dnM
M

dnet_getalias.3dn

getnodeadd.3dn

lusr/manlman8:
dts.8dnM
ncp.8dnM

lusr/include/netdnet:
dn.hB

x25db.hB

dnetdb.hB

Note: If you are installing DECnet-ULTRIX onto a RISC processor, you do not
receive the lusr/lib/libdnet_p.a file.

c
DECnet-ULTRIX Distribution Files

A-3

Index
A
Adding clients, 3-1

Checkout procedure, 4-1, 4-6
Checkout tests, 4-1
Client node, defined, 1-3
Configuration
of clients, 3-5
of DECnet database, 2-9
of node, 2-6, 2-11, 3-10
of unidirectional gateway, 2-12, 3-11
Configuration file, 2-8, 3-7
Controller loopback test, 4-2
Customizing system files, 3-8

Database, permanent, 2-10,3-8
Datalink loopback test, 4-2
DDCMP point-to-point connection, 4-1
DECnet-lnternet Gateway, 1-4
DECnet node database, 3-7
DECnet-ULTRIX distribution files, A-1
DECnet-ULTRIX distribution kit, 2-4
DECnet-ULTRIX On-Line Manual Pages subset, 1-4
Default logging device, 2-11
Deleting DECnet database, 2-13
Deleting DECnet-ULTRIX software, 2-13
Diskless client, 1-3
Diskless environment, 1-3,3-1,3-2,3-5,3-7
Diskless Management Service (dms) utility, 3-3
Disk space, 2-2,2-4,3-2
Distribution media, 1-3,2-2,3-3,3-4
file groups on, A-1
mounting, 2-5

E
Error correction, 2-14, 3-11
Errors, serious, 2-14
Estimated time, 2-2, 2-4, 3-2
Ethernet connection, 4-2

fal, 4-2
Files, DECnet-ULTRIX, A-1
File transfer
to local node test, 4-2

File transfer (Cont.)
to remote node test, 4-2

G
Gateway, installation of, 1-1
Gateway software
running, 2-11,3-10
unidirectional configuration, 2-12,3-11
Gateway software, running, 3-10
Guest account, 2-4,2-10,3-9

H
hostname, 2-5
HOSTNAME, 2-3,2-8

Installation
basic procedure for, 2-1
client, 1-1
first, 2-4, 2-5
Gateway, 1-1
server, 1-1
verifying, 2-14,3-11
Installation, Gateway, 3-10
Installation checkout procedure, 4-1,4-6
Installation requirements
for a node, 2-1
for client node, 3-1
for remote functions, 1-2
for software license registration, 1-2
Internet network kit, 2-3,2-4

L
License Management Facility, 1-2
Licensing
See Software license registration
LMF
See License Management Facility
Local node loopback test, 4-2

M
Maintenance Operations Protocol (mop), 1-3

N
Node level loopback test, 4-2

Index-1

Node names
defining, 2-10, 3-8
deleting, 2-10,3-8

o
On-line reference manual
See DECnet-ULTRIX On-Line Manual Pages
subset

p
PAK
See Product Authorization Key
Performance testing, 4-1
Privileges, superuser
see Superuser privileges
Product Authorization Key, 1-2
Proxy file, 2-10, 3-8

R
Reinstallation, 2-5
Restarting installation, 2-14,3-5
Restarting the system, 3-11

Set load command options
setld -d, 2-4
setld -I, 2-4
Software license registration, 1-2
Software subsets, 1-1
Superuser password, 3-3
Superuser privileges, 1-2,2-1,3-3
System configuration file, 2-8,3-7
and multiple DECnet-supported devices, 3-7
System files, 3-8
customizing, 2-10,3-8
modifying, 2-10

T
Test
controller" loopback, 4-2
datalink loopback, 4-2
file transfer to local node, 4-2
file transfer to remote node, 4-2
local node loopback, 4-2
node levelloopback, 4-2
Time
See Estimated time

v
Verifying installation, 4-1

Server node, defined, 1-1
Set load command, 2-4

(

Index-2

~'\

HOW TO ORDER ADDITIONAL DOCUMENTATION

IDIRECT TELEPHONE ORDERS I
In Continental USA
call 80Q-DIGITAL

In Canada
call 800-267~215

In New Hampshire
Alaska or Hawaii
call 603-884-6660

In Puerto Rico
call 809-754-7575

IELECTRONIC ORDERS (U.S. ONLY) I
Dial 80Q-DEC-DEMO with any VT100 or VT200
compatible terminal and a 1200 baud modem.
If you need assistance, call 1-800-DIGITAL.

DIRECT MAIL ORDERS (U.S. and Puerto Rico*)
DIGITAL EQUIPMENT CORPORATION
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (Canada)

DIGITAL EQUIPMENT OF CANADA LTD.
940 Belfast Road
Ottawa, Ontario, Canada K1G 4C2
Attn: A&SG Business Manager

I INTERNATIONAL I
DIGITAL
EQUIPMENT CORPORATION
A&SG Business Manager
c/o Digital's local subsidiary
or approved distributor
Internal orders should be placed through the Software Distribution Center (SOC),
Digital Equipment Corporation, Westminster, Massachusetts 01473

0·:';
,

*Any prepaid order from Puerto Rico must be placed
with the Local Digital Subsidiary:
809-754-7575 x2012

C. -.~."
'

c
DECnet-ULTRIX
Installation
AA-EA87E-TE

READER'S COMMENTS
What do you think of this manual? Your comments and suggestions will help us to improve the
quality and usefulness of our publications.

Please rate this manual:
Poor
Accuracy
Readability
Examples
Organization
Completeness

Excellent

1
1
1

2
2
2

3
3
3
3
3

4
4
4
4
4

5
5
5
5
5

Did you find errors in this manual? If so, please specify the error(s) and page number(s).

c
General comments:

Suggestions for improvement:

Name
Date - - - - - - - - _
litle
Department _ _ _ _ _ _ __
Company _ _ _ _ _ _ _ _ _ _ _ _ Street _ _ _ _ _ _ _ _ _ _ __

City _ _ _ _ _ _ _ _ _ _ _ _ _ State/Country

Zip---

DO NOT CUT - FOLD HERE AND TAPE

111111

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

BUSINESS REPLY LABEL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

~DmDDmDTM

Networks and
Com m un ications Publ ications
550 King Street
Littleton, MA 01460-1289

DO NOT CUT - FOLD HERE