Digital PDFs

AA-PB62A-TE

May 1990

143 pages

Original

4.7MB

Document:	DECnet—ULTRIX NCP Command Reference
Order Number:	AA-PB62A-TE
Revision:	000
Pages:	143
Original Filename:

OCR Text

DECnet-ULTRIX

NCP Command Reference

Order Number: AA-PB62A-TE

DECnet-ULTRIX

NCP Command Reference

May 1990
This manual describes the Network Control Program (ncp)
commands you use to define, monitor, and test your network.
Supersession/Update Information:

This is a new manual.

Operating System and Version:

ULTRIX V4.0

Software Version:

DECnet-ULTRIX V4.0

o
Order Number: AA-PB62A-TE

AA-PB62A-TE
May 1990

The information in this document is subject to 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
~DmDDmDTM

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

c
This manual was produced by Networks and Communications Publications.

c
Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1

Understanding the Network Control Program

1.1

Getting Started with ncp ...................................... .
1.1.1
Invoking ncp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2
Exiting ncp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1
1-1
1-2

1.2

Executing ncp Commands .................................... .
1.2.1
Command Syntax ................................... .
1.2.2
Typing Command Lines ............................... .
1.2.3
Using the Help Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Prompting ................................. .
1.2.4
1.2.5
Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6
Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2
1-2

1.3

c:'

vii

1-3
1-3
1-4
1-4
1-4

Executing ncp Commands Remotely ............................. .
1.3.1
Using the tell Prefix .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2
Using the set executor Command . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3
Access Restrictions on Remote Nodes ..................... .

1-5
1-5

1.4

Network Management Privileges .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6

1.5

Issuing load and trigger Commands ............................. .

1-6

Chapter 2

1-5

1-6

NCP Command Descriptions
clear circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
clear executor ............................................. .
clear executor node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
clear logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
clear node ................................................ .
clear object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
define circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
define executor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
define line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
define logging ............................................. .
define node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
define object .............................................. .
help •.....................................................
list circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
list executor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
list line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4
2-5
2-6

2-7
2-9
2-11
2-12

2-13
2-16

2-18
2-20
2-22

2-24
2-26

2-27
2-28

iii

list logging ................................................ .
list node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
list object ............................................••....
load node .............•..........•............•...........
load via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
loop circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
loop executor ...............................................
loop node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
purge circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
purge executor .............................•................
purge logging ...............................................
purge node ................................................
purge object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
set circuit .................................................
set executor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . .
set executor node ................•...........................
set line ..............•....................................
set logging .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
set node ................................................. .
set object ................................................ .
show circuit ................................................ .
show executor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
show line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
show logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
show node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
show object ................................................
tell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
trigger node .....................•..........................
trigger via • . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zero circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zero executor .............................................. .
zero line ...........•......................................
zero node .................................................

Chapter 3

2-64

2-65
2-66
2-67
2-68
2-69
2-71
2-72

2-73
2-74
2-75

Error Messages

3.1

ncp Error Message Format

3-1

3.2

ncp Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1

Chapter 4

2-29
2-30
2-31
2-32
2-34
2-36
2-39
2-40
2-41
2-42
2-43
2-45
2-47
2-48
2-49
2-53
2-54
2-56
2-58
2-60
2-62
2-63

Event Messages

4.1

Event Classes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

4.2

Event Message Format ....................................... .

4-1

4.3

Network Management Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .

4-3

4.4

Session Control Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3

4.5

End Communications Layer Event ............................... .

4-3

4.6

Routing Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-4

4.7

Event Log Summary ......................................... .

4-5

Chapter 5

Network Counters

5.1

Circuit Counters ............................................ .
5.1.1
Network Management Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2
Routing Layer . . . . . . . . . . . . . . . . . • . . . . . . . . . . . . . . . . . . . . .
5.1.3
Data Link Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1
5-1
5-1
5-2

5.2

Line Counters ............................................. .
5.2.1
Network Management Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2
Data Link Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-4
5-4
5-4

5.3

Node Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1
Network Management Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2
End Communications Layer . • . . . . . • . . . . . . . . . . . . . . . . . . . . . .
5.3.3
Executor Node Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Appendix A

Command Summary

Appendix B

DECnet-Supplled Objects

Appendix C

Ethernet Addressing

C.1

Ethernet Address Format

C-1

C.2

Ethernet Multicast Address Types ............................... .

C-2

C.3

Ethernet Physical and Multicast Address Values ..................... .

C-2

4-1

Event Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

2-1
4-1
4-2

ncp Command Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . .
Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1
4-1
4-5

Index

Figures

Tables

B-1
B-2

Event Log Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital-Supplied DECnet-ULTRIX Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DECnet-ULTRIX Object Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-1
B-2

o
v

c
Preface

This manual explains how to use the Network Control Program (ncp) commands
to manage a Phase IV DECnet-ULTRIX node within the DECnet environment.

Manual Objectives
This manual describes the ncp commands that you can use to configure, monitor, and test your network. Additional reference information summarizes the
DECnet-ULTRIX network objects, event logging, network counters, and Ethernet
addressing information.

Intended Audience
\~· "

This manual is for anyone responsible for configuring, maintaining, and managing
the network. The manual refers to all such people as the network manager.

Structure of This Manual
This manual is divided as follows:

Chapter 1

Gives a detailed explanation of how to invoke the Network Control
Program and gives guidelines for using ncp commands.

Chapter 2

Describes each ncp command, including its function, syntax,
parameters, and gives an example.

Chapter 3

Lists and explains all error messages that can occur from the
execution of an ncp command.

Chapter 4

Lists and explains the network management event-logging messages.

Chapter 5

Lists and explains all network counters maintained by the
DECnetr-ULTRIX. software.

Appendix A

Summarizes all ncp commands and their parameters.

Appendix B

Defines all DECnet-ULTRlX objects by name, number, file, and
function.

Appendix C

Describes physical and multicast addressing for nodes on Ethernet
lines.

vii

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

•

DECnet-ULTRIX Release Notes
Contains information and updates not included in the
DECnet-ULTRIX documentation set.

•

DECnet-ULTRIX Installation
Contains step-by-step procedures for installing your DECnet-ULTRIX software and testing your node's operation in the network.

•

DECnet-ULTRIX Use
Describes the DECnet-ULTRIX user commands and explains how to use them

to perform file transfer and other user tasks.
•

DECnet-ULTRIX Network Management
Introduces the network manager to DECnet databases and components
and describes how to use the Network Control Program (ncp) to configure,
monitor, and test these components.

•

DECnet-ULTRIX Programming
Describes the DECnet-ULTRIX system calls and subroutines. Also provides information about application programming within the DECnet environment and contains supplemental information for programming the
DECnet-ULTRIX socket interface.

•

DECnet-ULTRIX DECnet-Internet Gateway Use and Management
Describes the DECnet-Internet Gateway and explains how to use, manage,
and install it.

To obtain a detailed description of the Digital Network Architecture, refer to the
following document:
•

DECnet Digital Network Architecture (Phase NJ, General Description

Acronyms
The following acronyms are used in this manual:

viii

DNA

Digital Network Architecture

dtr
dts
ECL
evl
fal
mir
ncp

DECnet Test Receiver

Event Logger

nml

Network Management Listener

NSP

Network Services Protocol

DECnet Test Sender
End Communication layer
File Access Listener
Loopback Mirror
Network Control Program

Conventions Used in This Manual
Convention

Meaning

Example

Examples appear in this special type.

Red type

Red type in examples indicates text that a user enters.

special

All commands and parameters appear in special type.

lowercase

If a command appears in lowercase type in a command format
or in an example, you must enter it in lowercase.

italic

Italic type in command formats and system displays indicates
a variable, for which either you or the system must supply a
value.

{ }

Braces indicate that you must specify one of the enclosed
options, but no more than one. Do not type the braces when
you enter the command.

[ ]

Square brackets indicate that you can use one, and only one, of
the enclosed options. Do not type the brackets when you enter
the command.

( )

Parentheses enclose a set of options that you must specify
together or not at all.

Vertical
list of
options

A vertical list of options not enclosed within braces, brackets,
or parentheses indicates that you can specify any number of
options, or none at all.

Ikeyl

This is a symbol for a keyboard key. I CTRukey I represents a
CTRL key sequence, where you press the CTRL key at the
same time as the specified key.

This is the default user prompt in multiuser mode.

This is the default superuser prompt.

All Ethernet addresses are hexadecimal; all other numbers are decimal unless
otherwise noted.

o
ix

~ ...

c
Chapter 1

Understanding the Network Control Program
This chapter tells you how to use the Network Control Program (ncp) on
DECnet-ULTRIX nodes in the following ways:

•

Invoke and exit the Network Control Program.

•

Execute ncp commands.

•

Issue ncp commands from your terminal for execution at a remote node.

•

Maintain network security with superuser privileges.

•

Down-line load a remote node using load and trigger commands.

1.1 Getting Started with ncp
The Network Control Program lets you issue ncp commands from a terminal
or from a shell script. You can execute most ncp commands either locally or
remotely.

1.1.1

Invoking ncp
You can invoke ncp in three ways:

•

Enter ncp at the prompt.
%ncp

The program then prompts you as follows:
ncp>

Enter your ncp command after the prompt and press ~.
•

Enter an entire ncp command line, for example:
% ncp show known circuits counters ~

where show known circuits counters is a valid ncp command. Mter the
command executes, you return to the shell.
•

Enter ncp with a shell script, for example:
% ncp <scripta

where scripta is the name of a shell script that contains a sequence of
ncp commands. Your shell script can use the exit status returned by ncp
commands.

Understanding the Network Control Program

1-1

The following example shows a sample shell script:
ncp sho line una-O
if ( $status != 0 ) then
echo ""
echo "This ncp command failed."
echo ""
endif

.r~

',-/,

This sample shell script uses the exit status from an ncp command to
detennine whether or not to echo a message. If the ncp show line command
fails, the shell script echoes the message.
NOTE

You can insert comment lines in an ncp shell script by prefacing each
comment line with a pound sign (#).

1.1.2

Exiting ncp
To exit ncp, use either the exit command, the quit command, or ICTRUO I at the ncp
prompt.

1.2 Executing ncp Commands
The following sections explain the ncp command syntax and procedures for
executing them.

1.2.1

Command Syntax
Most commands consist of three parts: the command verb, a component on which
the command operates, and one or more parameters that further qualify the
action to be taken on the component. You enter a command at the ncp prompt in
the following order:

ncp command-verb component parameter
EXAMPLE:
This example shows a list command.
list line una-O characteristics

For each command, you must supply one verb and one component option. The
number of parameters that you can supply varies with each command.
Some commands have a list of optional parameters, any number of which you
can specify. For example, the list line command lets you select one or more of the
following parameters:

characteristics ]
list { line line-id } counter
known lines
[ status
summary
Some commands have the all parameter. When you specify all, you cannot specify
any other parameters for that command. If you do not specify all, you can use
any number of the remaining parameters. For example, you can use all or you
can specify any other clear node command parameters:

1-2 Understanding the Network Control Program

c
clear { node node-id }
known nodes

all
diagnostic file
dump file
hardware address
host
load file
name
secondary loader
service circuit
service password
tertiary loader

EXAMPLE:
This example shows how you can use all to specify all clear node parameters for
an object.
ncp>clear node NAVAHO all

Some commands have a bracketed list of optional parameters of which you can
specify only one option. For example, the show object command lets you select
only one parameter for a specified object or for all known objects.

show { objects object-name } [Characteristics
known objects
summary

1.2.2

Typing Command Lines
Enter the command keywords separated by spaces. You can abbreviate any
keyword to the shortest number of unique characters that ncp accepts. For
example, the following versions of the same command are equally valid:
ncp>show logging console
ncp>sho log con

ncp>sh 10 c ~

C·-.'

1.2.3

USing the Help Facility
Enter help at the ncp prompt for assistance in selecting network management
commands and parameter options. The ncp utility returns a list of subjects for
which help information is available.

EXAMPLE:
This example shows how the help command displays available information.
ncp>help

Help available for:
clear
command
help
list
parameters
prompting
show
tell

define
load
purge
trigger

exit
loop
set
zero

Topic?

For additional information, enter one of the command verbs at the Topic?
prompt.

Understanding the Network Control Program

1-3

1.2.4

Command Prompting
Command prompting provides on-line assistance when you are entering ncp
commands. If you press ~ at the ncp prompt, ncp displays all legal options for
that command keyword.

EXAMPLE:
This example shows you the kind of information you must provide when you
press ~ after entering the show command.
>ncp ~
ncp>show

(active, adjacent, area, circuit, executor, known, line,
logging, loop, module, node, object):

If you enter known at the colon (:) prompt, ncp prompts you for additional
information, as shown in the following example:
(active, adjacent, area, circuit, executor, known, line,
logging, loop, module, node, object): known
(areas, circuits, lines, logging, nodes, objects):

If you enter an incomplete set or define command, ncp prompts you individually
for each possible parameter. You can respond in one of several ways:

1.2.5

•

Enter ~ to omit the current parameter and to be prompted for the next one.

•

Enter a parameter value and press ~ to set this parameter and to be
prompted for the next one.

•

Enter a period (.) and press ~ when you have specified the parameters that
you want and are ready to exit the prompting loop to execute the command.

•

Enter ICTRuol to cancel the entire command.

Error Reporting
If a command executes successfully, the ncp prompt appears on the next line.
If a command does not complete successfully, an error message is displayed to
indicate the reason for the failure. Chapter 3 lists ncp error messages.

1.2.6

/-"

Event Logging
The logging monitor interface from the DECnet event-logging facility provides a
mechanism by which a user-written program can process network events. You
must specify the name of the monitoring program and the events to be logged by
using the following ncp set logging commands:

set logging monitor name name state on
set logging monitor events event-list
where
name

Is the file descriptor of the program to receive the event information
(default: evl).

1-4 Understanding the Network Control Program

event-list

Identifies one or more event classes and types to be logged. (See
Chapter 4 for a list of event classes and types.)

NOTE

The event monitor facility can be used in conjunction with event
logging, either on the console or to a file.
When the monitor program is evl (default), events are logged at the logging
console. If you write your own monitor program to process network events, your
program starts when the network starts. When the network starts up, evl passes
two arguments to your monitor program:
Argument 1 - your monitor program file name
Argument 2 -

the file descriptor of a pipe from which to read

Your monitor program reads the events in ASCII from the pipe and then processes
them according to your specifications.

Cit

1.3 Executing ncp Commands Remotely
You can use ncp to modify parameters or display information at a remote node.
You can execute ncp commands on a remote node while logged in to your local
node by using either the ncp tell prefix or the ncp set executor node command.
Before attempting to execute an ncp command remotely:

1.3.1

•

Refer to network management documentation for the remote node to see
which commands it supports.

•

Check for any access restrictions.

Using the tell Prefix
1b execute a single ncp command at a remote node, issue the command with the
tell prefix. The following example shows how you can use the tell prefix to send
the ncp command show executor node to a remote node NAVAHO.
ncp>tell navaho show exec node char

1.3.2

Using the set executor Command
1b execute a series of ncp commands at a remote node, use the set executor
node command to set the specified remote node as the executor. Subsequent
commands that you issue are executed at that node until you restore control to
your own node by issuing a clear executor node command. If you exit ncp while
the executor is set to a remote node, control is automatically returned to the local
node when you reenter ncp. For example:
% ncp ~
ncp>set executor 2.95 ~
show executor characteristics

o
Understanding the Network Control Program

1-5

define executor address 2.95
set executor incoming timer

ncp> clear executor node

In this example, 2.95 is the node address.

1.3.3 Access Restrictions on Remote Nodes
Before you issue commands to be executed at a remote node, you may have to
supply access control information. Depending on the types of access restrictions
set up by the system manager of the remote node, you can gain access to a remote
node from a DECne1r-ULTRIX node in the following ways:
•

Append access control information to the node ID in the ncp command string.

•

Include access control information in an "alias" definition for the node.

•

Use proxy verification on the remote node.

For the procedure on how to supply access control information, see the
DECnet-ULTRIX Use manual.

1.4 Network Management Privileges
You must have superuser privileges to use an ncp command that modifies a
database. However, anyone can exercise the ncp show or list commands locally
to display component information from the databases.
On ULTRIX systems, some ncp commands (such as purge, define, set, and zero)
require superuser privileges. Other systems may also require privileges for the
same ncp commands. For example, some DECnet-VAX NCP commands require
system privileges (SYSPRV), others require operator privileges (OPER), and still
others do not require privileges. To determine the privileges you need to issue
commands at either a DECne1r-ULTRIX node for remote execution or a remote
node, see the Network Control Program documentation for the remote node.

1.5 Issuing load and trigger Commands
When you issue the load command, the load host must have service enabled
on its Ethernet circuit or it cannot perform a down-line load. When you issue
the trigger command, potential load hosts must have service enabled on their
Ethernet circuits or they cannot perform a down-line load.

To enable service, use the following command format:
set circuit circuit-id service enabled
where circuit-id identifies the Ethernet circuit for the host.
On the command line, enter either the DECnet node name or the DECnet node
address of the server. The load and trigger commands have a similar syntax:
load node node-name
trigger node node-name
or

1-6 Understanding the Network Control Program

load node node-address
trigger node node-address

The following examples use the load command to load a node named NAVAHO
with a node address of 55.1024.
ncp> load node NAVAHO

ncp> load node 55 .1024

If the remote node you want to load has an enabled password, you must specify
this password on the load and trigger command lines. For example, to load node
NAVAHO with service password FF55, type:
ncp>load node NAVAHO service password FF55

or
ncp>load node 55.1024 service password FF55

or
ncp>trigger node NAVAHO service password FF55

or
ncp>trigger node 55.1024 service password FF55

o
Understanding the Network Control Program

1-7

Chapter 2

NCP Command Descriptions

This chapter gives detailed descriptions and examples of each ncp command.
Table 2-1 summarizes ncp command functions:

Table 2-1: ncp Command Functions
Command

Function

clear circuit

Removes specified circuit parameters from the volatile
database.

clear executor

Resets specified executor parameters to their default values in
the volatile database.

clear executor node
clear logging

Resets the default executor to the local node.

clear node

Removes names associated with the nodes or removes specified
parameters from the volatile database.

clear object
define

Removes specified objects from the volatile database.
Creates or modifies specified parameters in the permanent
database.

define circuit

Modifies specified circuit parameters in the permanent
database.

define executor

Modifies specified executor node parameters in the permanent
database.

define line
define logging

Modifies specified line parameters in the permanent database.

define node

Changes the name or address associated with a node or resets
specified node parameters in the permanent database.

define object

Creates or modifies parameters for the specified objects in the
permanent database.

help
list
list ci rcu it
list executor

Removes specified logging parameters from the volatile
database.

Creates or modifies logging component parameters in the
permanent database.

Displays information about ncp commands and parameters.
Displays specified parameters in the permanent database.
Displays specified circuit information stored in the permanent
database.
Displays specified local node information stored in the
permanent database.

(continued on next page)

NCP Command Descriptions 2-1

Table 2-1 (Cant.): ncp Command Functions
Command

Function

list line

Displays specified line information stored in the permanent
database.

list logging

Displays specified logging information stored in the permanent
database.

list node

Displays specified node information stored in the permanent
database.

list object

Displays specified object information stored in the permanent
database.

load node
load via

Down-line loads a specified remote node on the same Ethernet.
Down-line loads a remote node on the same Ethernet by way of
the specified circuit.

loop circuit

Tests a circuit between the executor and another node in the
network.

loop node/executor
purge
purge circuit

Tests a node in the network.

purge executor

Resets specified executor parameters to their default values in
the permanent database.

purge logging

Removes specified logging parameters in the permanent
database.

purge node

Removes the names associated with the nodes or removes
specified node parameters from the permanent database.

purge object
set
set circuit
set executor
set executor node
set line
set logging

Removes specified parameters in the permanent database.
Removes specified circuit parameters in the permanent
database.

Removes specified objects from the permanent database.
Creates or modifies specified parameters in the volatile
database.
Modifies specified circuit parameters in the volatile database.
Creates or modifies specified executor node parameters in the
volatile database.
Sets a default executor for subsequent ncp commands.
Modifies specified line parameters in the volatile database.
Modifies logging component parameters in the volatile
database.

set node

Changes the name or address associated with a node or resets
specified node parameters in the volatile database.

set object

Creates or modifies parameters for specified objects in the
volatile database.

show
show circuit

Displays specified parameters in the volatile database.
Displays specified circuit information stored in the volatile
database.

show executor

Displays specified local node information stored in the volatile
database.

show line

Displays specified line information stored in the volatile
database.

(continued on next page)

2-2 NCP Command Descriptions

Table 2-1 (Cont.): ncp Command Functions
Command

Function

show logging

Displays specified logging information stored in the volatile
database.

show node

Displays specified node information stored in the volatile
database.

show object

Displays specified object information stored in the volatile
database.

tell
trigger

Sends an ncp command to a remote node for execution.
Starts the bootstrap operation of a remote node on the same
Ethernet so that the node multicasts a request for a down-line
load.

trigger via

Starts the bootstrap operation of a remote node on the same
Ethernet so that the node multicasts a request for a down-line
load through a specified circuit.

zero
zero circuit
zero executor

Sets counters to zero.

zero line
zero node

Sets line counters to zero for the specified line.

Sets circuit counters to zero for the specified circuit.
Sets node counters associated with and maintained on the
executor node to zero.
Sets line counters to zero for the specified node. The executor
node maintains node counters on a per-node basis.

o
NCP Command Descriptions 2-3

clear circuit
r~

\*0,..=.;/

clear circuit
DESCRIPTION
Removes specified circuit parameters from the volatile database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
"t"
'd [ receive password ]
c Iear ClrcUi ctrcutt-t
transmit password

where
ci rcu it circuit-id
receive password
transmit password

Specifies the circuit for which parameters are to be removed.
Removes the circuit's receive password.
Removes the circuit's transmit password.

EXAMPLE
This command deletes all parameters for circuit una-O from the volatile database.
nop>olear circuit una-O

c
2-4

NCP Command Descriptions

clear executor

clear executor
DESCRIPTION
Resets specified executor parameters to their default values in the volatile
database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
clear executor

identification
}
incoming timer
{ outgoing timer

where
identification
incoming timer

Removes the text identification string for the executor node.

outgoing timer

Resets the outgoing timer to its default value.

Resets the incoming timer to its default value.

EXAMPLE
This command resets the local node's incoming timer to its default value in the
volatile database.
ncp>

clear executor incoming timer

o
NCP Command Descriptions

2-5

clear executor node

clear executor node
DESCRIPTION
Resets the default executor to the local node.

RESTRICTION
Do not use the tell prefix with this command.

SYNTAX
clear executor node

EXAMPLE
This command returns ncp command execution from a remote node to the local
node.
ncp>clear executor node

c
2-6

NCP Command Descriptions

clear logging

c
clear logging
DESCRIPTION

Removes specified logging parameters from the volatile database.

RESTRICTIONS
You must have superuser privileges to execute this command.
Whenever you specify a circuit, line, node, or sink in a clear logging command,
you must also include an events list or known events parameter.

SYNTAX

clear

known logging }
logging ~onsole
{ logging file
logging monitor

name
events event-list
known events
circuit circuit-id ]
[ line line-id
node node-id
sink {executor . }
[
node node-td

where

circuit circuit-id
events event-list

Inhibits event logging for the specified circuit.

known events

Removes all known events that DECnet-ULTRIX can generate
for the specified component.

known logging
line line-id
logging console
logging file
logging monitor
name

Removes parameters for all known logging components.

Removes the event class and types specified in event-list for the
specified component.

Inhibits event logging for the specified line.
Removes parameters for the console--Iogging component.
Removes parameters for the file-logging component.
Removes parameters for the monitor-logging component.
Returns the specified logging component to its default name
(console: /device/console; file: /usr/adm/eventlog; monitor

evl.)
node node-id
sink

Inhibits event logging for the specified node.
Inhibits logging of the specified events at the specified node.
You must specify one of the following qualifiers:
executor
This is the default setting. Events
are not to be logged at the executor
node.

node node-id

Events are not to be logged at the
specified node.

NCP Command Descriptions 2-7

clear logging

EXAMPLE
This command ceases logging of event 2.1 to the console.
ncp>' clear logging console event 2. 1

c
2-8

NCP Command Descriptions

clear node

clear node
DESCRIPTION
Removes names associated with the nodes or removes specified node parameters
from the volatile database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
diagnostic file
dump file
hardware address
host
load file
name
secondary loader
service circuit
service password
tertiary loader

clear { node node-id }
known nodes

clear { node node-id } all
known nodes
where

all

Removes all parameters for the specified node(s) so that the
network no longer recognizes the nodes. Use of all precludes
the use of any other parameters.

diagnostic file
dump file
hardware address
host
known nodes
load file
name

Removes the identification of the down-line load diagnostic file.

node node-id
secondary loader

Removes the up-line dump file identification.
Removes the Ethernet address of the system hardware.
Removes the host node identification.
Performs the specified function for all known nodes.
Removes the identification of the down-line load file.
Removes the node name(s) associated with the specified
node(s).
Performs the specified function for the specified node only.
Removes the identification of the secondary down-line loading
file.

service circuit

Removes the circuit parameter associated with the node for
down-line loading purposes.

service password

Removes the password parameter. This password parameter is
required to trigger the bootstrap mechanism of the node to be
down-line loaded.

NCP Command Descriptions

2-9

clear node
tertiary loader

Removes the identification of the tertiary down-line loading
file.

EXAMPLE
This command removes all information for node BOSTON from the volatile
database.
ncp> clear node boston all ~

c
2-10

NCP Command Descriptions

clear object

clear object
DESCRIPTION
Removes specified objects from the volatile database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

clear { object object-name }
known objects

where
object object-name
known objects

C'
"

Specifies the object for which parameters are to be removed.
Specifies that parameters are to be removed for all known
objects.

EXAMPLE
This command removes the network terminal handler (dtermd) from the volatile
database.
ncp> clear object dtermd ~

o
NCP Command Descriptions

2-11

define circuit
~,
I,

define circuit
DESCRIPTION
Modifies specified circuit parameter(s) in the permanent database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
define circuit circuit-id

where
circuit circuit-id
hello timer seconds
receive password
password

state circuit-state

hello timer seconds
receive password password
. ·t-s ta te {Off }
st at e CLrcuz
on
transmit password password

Specifies the circuit for which parameters are to be modified.
Specifies the frequency of routing hello messages sent to
adjacent nodes on the circuit. The range is 1 through 8191.
Specifies a 1- to 8-character ASCII password associated with
the circuit that the executor expects to receive from the remote
node during a routing initialization sequence.
Specifies the circuit's operational state. There are two possible
states:
off
The circuit is not in use.

on
transmit password
password

The circuit is available for normal use or
service functions.

Specifies a 1- to 8-character ASCII password associated with
the circuit that the executor sends to the remote node during a
routing initialization sequence.

EXAMPLES
This command makes circuit una-O unavailable for use.
ncp>define circuit una-O state off

c
2-12

NCP Command Descriptions

define executor

c
define executor
DESCRIPTION

Creates or modifies specified executor node parameters in the permanent
database.
NOTE

If you use the define executor command to issue a series of commands
at a remote node, you can use the tell prefix to issue an ncp command
to yet another remote node.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

define executor-

address node-address
delay factor number
delay weight number
gateway access {diSable }
enable
gateway user login-name
identification id-string
inactivity timer seconds
incoming proxy {diSable }
enable
incoming timer seconds
maximum links number
maximum node counters number
name node-name
outgoing proxy {diSable }
enable
outgoing timer seconds
pipeline quota number
retransmit factor number
segment buffer size number

where
address
node-address

delay factor
number

delay weight
number

Specifies the address of the executor node. (Remember, define
commands do not take effect until the next time you start up
the network.)
Specifies a number to multiply times 1116 of the estimated
round-trip delay to a node in order to set the retransmission
timer for that node. The range is 1 through 255.
Specifies a value to apply to a current round-trip delay to a
remote node in order to update the estimated round-trip delay
time. The range is 1 through 255.

NCP Command Descriptions

2-13

define executor
gateway access

Specifies whether or not the executor allows the DECnet
objects fal and dloglnd to provide access to the Internet
network. Choose one of the following modes:
disable
Turns off file transfer and remote log-in
Internet access.

enable

Turns on file transfer and remote log-in
Internet access.
The default value is disable if you choose
not to install the Gateway during the
DECnet-ULTRIX. installation procedure.
Otherwise, the default value is enable.

gateway user
login-name

Identification
id-string

Inactivity timer
seconds

Incoming proxy

Specifies a default log-in name under which the DECnet
objects fal and dloglnd are to run if gateway access is enabled
and a gateway request is received. The range is 1 through 32
characters.
Specifies the text identification string for the executor node.
The range is 1 through 32 characters. You must use double
quotation marks (") to delimit any string containing blanks or
tabs. To include a quoted string within an identification string,
enclose it within single quotation marks to distinguish the
quotes from a string delimiter.
Specifies the maximum time the executor allows a link to
remain idle (no user data traffic) before it checks to see
whether the circuit still works. The range is 1 through 1024.
Specifies whether the executor honors or ignores proxy log-in
requests present on incoming logical Jinks. Choose one of the
following modes:
disable
All incoming proxy requests are ignored.
Instead, access control information supplied
in each connect request is used to validate the
request.

enable

Incoming timer
seconds

maximum links
number

maximum node
counters
number

2-14 NCP Command Descriptions

(Default.) Incoming proxy requests are
honored, based on the source user, the source
node, and the access control information.

Specifies the maximum time a process has to answer an
incoming connect request. If the process does not answer the
connect request within this time interval, the node rejects
the connect request on behalf of the process. The range is 1
through 1024.
Specifies the maximum number of active logical links for the
executor node. The range is 1 through 1024. If you use this
parameter in a set command, you must specify a value greater
than the current maximum number of links. To decrease the
value, you must issue a define command and restart the
system.
Specifies the maximum number of node counters allowed. The
range is 4 through 255, and the default is 32.
If you use this parameter in a set command, you must specify
a value that is greater than the current maximum number of
node counters. To decrease the value, you must issue a define
command and restart the system.

define executor
name node-name
outgoing proxy

Specifies the node name of the executor.
Specifies whether or not the executor requests proxy log-in on
outgoing connect requests. Choose one of the following modes:
disable
The executor does not request proxy log-in
on outgoing logical links, even when the user
process attempts to enable it.

enable
outgoing timer
seconds

pipeline quota
number

retransmit factor
number

segment buffer size
number

(Default.) The executor requests proxy log-in
on all outgoing logical links, unless the user
process explicitly disables it.

Specifies the maximum time the executor node waits for a
pending connect request to be answered at a destination node.
If the request is not answered in this time interval, the source
process receives an error indication. The range is 1 through
1024.
Specifies the maximum number of bytes of buffer space
that NSP can use for transmission and reception for each
logical link. The range is 2,000 to 16~OOO. For satellite
communications, you should use a value of 6,000 bytes or
greater. The default is 4~096.
Specifies the number of times the executor restarts the
retransmission timer before the logical link is disconnected.
The range is 1 through 1024.
Specifies the size of the NSP message segment to be sent.
This value is the maximum size message that the End
Communications layer can transmit; it does not include routing
or data link overhead. The range is 1 through 1,478, and the
default is 576.

EXAMPLES
1. This command defines the executor address to 4.21 in the pennanent database

the next time the network is started up.
ncp>define executor address 4.21

2. This command defines the maximum number of active logical links for the
executor node to 20 in the volatile database.
ncp>define executor maximum links 20

o
NCP Command Descriptions

2-15

define line

define line
DESCRIPTION
Modifies specified line parameters in the permanent database.

RESTRICTION
When you change the protocol and duplex parameter values of a point-to-point
device, the operation mode of the device does not change until you restart the
circuit. Therefore, you should turn the circuit off before changing the parameter,
and then turn it back on afterward. For example:
ncp>define circuit dmv-O state off ~
ncp>define line dmv-O protocol ddcmp dmc duplex half
ncp>define circuit dmv-O state on ~

SYNTAX

define line line-id

controller {IOOPback }
normal
duplex {fUll }
half
ddcmp dmc }
protocol
ddcmp point
{
ethernet

where
line line-id

Specifies the line for which parameters are to be modified.

controller

Specifies the controller mode for the line. Choose one of the
following modes:
loop back
Internal device loopback mode.

normal
duplex

protocol

2-16 NCP Command Descriptions

Normal operating mode.

Represents the Physical Link hardware duplex mode of the
line device. (Valid for DDCMP point-to-point devices only.)
Choose one of the following modes:
full
Full-duplex mode.

half
Half-duplex mode.
Specifies the Data Link protocol to be used on the line. Choose
one of the following modes:
ddcmp
Protocol for the DMC emulator. This setting is
dmc
valid for dmv lines only.
ddcmp
Protocol for one end of a DDCMP point-to-point
point
connection. This is the default for all DDCMP
point-to-point connections, including dmv, dmc,
and dmr lines.
ethernet
Protocol for an Ethernet line. This is the
default and the only valid choice for Ethernet
lines (una, qna, sva, and bnt).

define line

EXAMPLE
This command sets the controller for line una-O to the loopback state.
ncp> define line una-O controller loopback ~

c'
C"

o
NCP Command Descriptions

2-17

define logging

define logging
DESCRIPTION
Creates or modifies logging component parameters in the permanent database.

RESTRICTIONS
You must have superuser privileges to use this command.
Whenever you specify a circuit, line, node, or sink in a define logging command,
you must also specify an events list or known events parameter.

SYNTAX
name name

state {~~ }
known logging }
defne
logging console
I
{ logging file
logging monitor

events list
known events
circuit circuit-id ]
[ line line-id
node node-id
sink { executor
}
[
node node-id

where

circuit circuit-id
events list
known events

Logs the specified event(s) occurring on the specified circuit.

known logging

Indicates that the specified parameters are to be created or
modified for all known logging components.

line line-id
logging console

Logs the specified event(s) occurring on the specified line.

Specifies the event class and type(s) to be logged.
Specifies that all events that DECnet-ULTRIX. can generate
are to be logged.

Indicates that the specified parameters are to be created or
modified for the console logging component.

logging file

Indicates that the specified parameters are to be created or
modified for the file logging component.

logging monitor

Indicates that the specified parameters are to be created or
modified for the monitor logging component.

name name

Specifies the name of the console, monitor program, or file to
which events are to be logged. The default name for a console
is /device/console; for a monitor program it is evl and for a
file it is lusr/adm/eventlog.

node node-id

Logs the specified event(s) occurring on the specified node.

c
2-18 NCP Command Descriptions

define logging

C"
I:

sink

Identifies the node on which the specified events are to be
logged. Choose one of the following qualifiers:
executor
(Default) executor node.

node node-id
state

The specified remote node.

Sets the operational state of the logging component on the
executor node. When the state is off, events are discarded.

EXAMPLES
1. This command directs any known events on circuit una-O to node BOSTON.

\
C

ncp> define known logging known events circuit una-O
sink node boston ~

2. This command directs any occurrence of event 2.1 to the console at node
PARIS.
ncp> define logging console event 2.1 sink node paris

o
NCP Command Descriptions 2-19

define node

define node
DESCRIPTION
Adds or modifies a node specification in the permanent database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

define node node-id

address node-address
dlag nostic file file
dump file file
hardware address E-address
host node-id
load fi Ie file
name node-name
secondary [loader] file
service {diSable }
enable
service circuit circuit-id
[service] password service-password
tertiary [loader] file

where
address
node-address

diagnostic file
file

(For Ethernet nodes only.) Specifies the file to be read when
the node is down-line loaded and requests diagnostics.

dump file file

Specifies the file that is to receive a copy of the system at the
time of the crash when the node is up-line dumped.

hardware address

Identifies the Ethernet address that was originally assigned
to the Ethernet controller for the node. This address is used
during operations such as down-line load to communicate with
the system before it has set up its physical address.

E-address

host node-id

Specifies a host node for all service operations. The default
value is the executor node ID.

load file file

Specifies a file containing the system software for down-line
loading to a node.

name node-name

Specifies a new (unassigned) node name to be associated with
the node-address used as the node-id in this command.

node node-id

Specifies the node for which the specified function is to be
performed.

secondary [loader]

Specifies a file containing secondary loader software for
down-line loading to the node.

file

2-20

Specifies a new (unassigned) node address to be associated
with the node-name used as the node-id in this command.

NCP Command Descriptions

define node

c
service

Specifies whether the node is enabled or disabled for down-line
loading.

service circuit

Specifies the circuit to be used for down-line loading and
up-line dumping. This circuit is the default value for the via
parameter of the load command.

circuit-id

[service] password
service-password

tertiary [loader]
file

Specifies the password required to trigger the bootstrap
mechanism on the node. The password is a hexadecimal
value of 1 to 16 characters.
Specifies a file containing tertiary loader software for down-line
loading to the node.

EXAMPLE
This command associates the name BURGER with node 12.
ncp> define node 12 name burger

c"
c'

o
NCP Command Descriptions

2-21

define object

define object
DESCRIPTION
Creates or modifies parameters for specified object(s) in the pennanent database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

d fine { object objl?;ct-name }
e
known objects

accept {deferred
}
immediate
default user login-name
file file-id
number number
type { sequenced packet }
stream

where
accept

Specifies whether incoming connect requests are to be accepted
or rejected by the DECnet object spawner or whether they are
to be forwarded to the object for processing. Choose one of the
following modes:
deferred
The object processes any optional data sent
with a connect request and can set optional
data to be returned when it accepts or rejects
the connect.

immediate
default user
login-name

(Default.) The DECnet object spawner
determines whether to accept or reject all
connect requests.

Specifies a default log-in name under which the object is to
run if no access control information is supplied with a connect
request and no proxy information is defined locally.

file file-id

Specifies an executable file or shell script used to invoke the
specified object.

known objects

Specifies that parameters are to be created or modified for all
known objects.

number number

Specifies the object number to be identified with the specified
object name. The default is O. See Appendix B for a list of
object names and numbers.

object object-name

Specifies that parameters are to be created or modified for the
named object only (a maximum of 16 alphanumeric characters).

c
2-22

NCP Command Descriptions

define object

type

Identifies the socket type. Choose one of the socket types:
sequenced (Default) provides a bidirectional, reliable,
packet
sequenced, and unduplicated flow of data while
preserving record boundaries.

stream

provides same data flow properties as above
without record boundaries.

EXAMPLE
This command defines the Network Management Listener (nml) as object number
19 with /etc/nml as the executable file. It also specifies that nml is to run under
the log-in name "guest" if no access control information is supplied with a connect
request and no proxy information is defined locally.
ncp>define object nml number 19 file /etc/nml default user guest ~

o
NCP Command Descriptions 2-23

help

help
DESCRIPTION
Displays general infonnation about ncp commands and parameters. Typing help
displays the topics for which information is available; typing help and a specific
topic or command name displays information about that topic or command.

SYNTAX
help [topic ...J
A command word listed in the help display. You may specify
up to eight topics separated by spaces or tabs.

topic

EXAMPLES
1. This command displays all command verbs for which further infonnation

exists.
ncp>help

Help available for:
clear
command
help
list
parameters
prompting
show
tell
ncp>

define
load
purge
trigger

exit
loop
set
zero

2. This command provides a description of the ncp command clear circuit and
displays command words for which further information exists.
ncp>help clear circuit

clear circuit
Use the clear circuit command to remove circuit parameters from the
volatile database on the executor node. Use the purge circuit
command to remove circuit parameters from the permanent database
on the executor node.
clear

circuit circuit-id

Help available for:
circuit-id
all
examples
ncp>

(parameters ••• )
receive password

transmit password

3. This command provides a description of the ncp command show and displays
command words for which further information exists.
ncp>help show

show
Use the show command to display information from the volatile database
on the executor node. Use the list command to display information
from the permanent database on the executor node.

2-24 NCP Command Descriptions

help

Help available for:
characteristics
summary
line
module
ncp>

counters
known
logging

events
circuit
node

status
executor
object

o
NCP Command Descriptions 2-25

list circuit

list circuit
DESCRIPTION
Displays specified circuit infonnation stored in the pennanent database.

SYNTAX
characteristics ]
list { circuit circuit-id} status
known circuits
[ summary
where
characteristics
circuit circuit-id
known circuits
status

summary

Displays parameters that are currently set for the circuit.
Displays information for the specified circuit only.
Displays information for all known circuits.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the
characteristics and status display types.

EXAMPLE
This command displays circuit characteristics for all known circuits in the
permanent database.
ncp> list known circuits characteristics

Known Circuit Permanent Characteristics as of Tue Nov 21 10:57:23 EST 1990
Cirouit

UNA-O

Hello timer
Type

10
Ethernet

ncp>

o
2-26

NCP Command Descriptions

list executor

list executor
DESCRIPTION
Displays specified local node information stored in the permanent database.

SYNTAX
list executor

characteristics ]
status
[ summary

where

characteristics
status

summary

Displays parameters that are currently set for the executor.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the
characteristics and status display types.

EXAMPLE
This command displays local node status information from the permanent
database.
ncp> list executor status

Executor Permanent Status as of WED Nov 15 16:13:45 EST 1990

Executor node =
State
ncp>

2.95 (OHIO)
On

c
NCP Command Descriptions

2-27

list line
\~

list line
DESCRIPTION
Displays specified line information stored in the permanent database.

SYNTAX
characteristics ]
list { line line-id } status
known lines
[ summary
where
line line-id
known lines
characteristics
status

summary

Displays information for the specified line only.
Displays information for all known lines.
Displays parameters that are currently set for the line.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the
characteristics and status display types.

EXAMPLE
This command displays information about line una-O.
nap> list line una-O summary

Line Pe~anent Summary as of Wed Nov 15 16:17:06 EST 1990
Line

State

BNT-O
nap>

c
2-28 NCP Command Descriptions

list logging

list logging
DESCRIPTION
Displays specified logging information stored in the permanent database.

SYNTAX
list

{ known logging
logging console
logg Ing file
logging monitor

} [Chamcte~~ICS
] [ known sinks
status
summary
events

]

sink node node-id

where

characteristics

Displays parameters that are currently set for the executor,
line, or circuit.

events

Displays event class and type information for the given logging
component. Choose one of the following qualifiers:
known sinks (Default) displays logging information for all
known sink nodes.

sink node
node-id

known logging
logging console
logging file
logging monitor
status

C",-

summary

Displays logging information for the specified
sink node only.

Displays information for all known logging components.
Displays information for the console logging component.
Displays information for the file logging component.
Displays information for the monitor logging component.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays event class and type information for the logging file on
node N1834P.
ncp>list logging file events sink node n1834p

o
NCP Command Descriptions 2-29

list node

list node
DESCRIPTION
Displays specified node information stored in the permanent database.

SYNTAX
characteristics ]
list { node node-id } status
[ summary
known nodes
where

characteristics
known nodes
node node-id
status

summary

Displays parameters that are currently set for the node.
Displays information for all known nodes.
Displays information for the specified node only.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the
characteristics and status display types.

EXAMPLE
This command displays error and performance statistics for all known nodes in
the permanent database.
nap> list node art summary

Node Permanent Summary as of Tue Nov 21 11:03:24 EST 1990
Executor node
State
ncp>

= 2.39 (ART)
= On

o
2-30

NCP Command Descriptions

list object

c
list object
DESCRIPTION

Displays specified object information stored in the permanent database.

SYNTAX
list { object obj~ct-name } [Characteristics
known objects
summary

where

characteristics
counters
known objects
object object-name
status

summary

Displays parameters that are currently set for the object.
Provides counter information for circuits, lines, and nodes.
Displays information for all known objects.
Displays information for the specified object only.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the
characteristics and status display types.

EXAMPLE
This command displays information about the Network Management Listener
(nml).

ncp> list object nml ~
Object Permanent Summary as of Wed Nov 15 16:27:55 EST 1990
Object

Number

File

nml
ncp>

/usr/ect/nml

c
NCP Command Descriptions

2-31

load node

load node
DESCRIPTION
Down-line loads a specified remote node on the same Ethernet. Any parameter
that you do not specify defaults to the value in the volatile database on the
executor node.
With the load node command, the node that initiates the loading sequence is also
the load host that performs the down-line load.

RESTRICTIONS
Before you can execute this command:
•

You must have superuser privileges.

•

The mop_mom utility must be installed during the the ULTRIX. software
installation.

•

Service must be enabled on the remote node.

•

You must have the service password if a DECnet service password is defined
on the remote node.

SYNTAX

load node node-id

address node-address
from load-file
host node-id
name node-name
physical address E-address
secondary [loader] file
[service] password service-password
tertiary [loader] file
via circuit-id

where
address

Specifies the address that the node is to use when it comes up.

node-address

from load-file

Specifies the file containing the system software to be
down-line loaded.

host node-id

Specifies the default host that the node is to use when it comes
up.

name node-name
node node-id
physical address

Specifies the name that the node is to use when it comes up.

E-address

2-32

NCP Command Descriptions

Specifies the node to be down-line loaded.
(For Ethernet nodes only.) Identifies the Ethernet physical
address that the node currently uses to identify itself.
(Required for Ethernet circuits if the hardware address
parameter has not been specified in the volatile database;
see set node.)

load node
secondary [loader]
file

[service] password
service password

tertiary [loader]

Specifies a file containing secondary loader software for
down-line loading to the node.
Specifies the password required to trigger the bootstrap
mechanism on the node. The password is a hexadecimal
value of 1 to 16 characters.

file

Specifies a file containing tertiary loader software for down-line
loading to the node.

via circuit-id

Specifies the circuit over which the load is to take place.

EXAMPLE
This command loads node BOSTON using a service password.
ncp>load node boston service password FF55

c
c

o
NCP Command Descriptions 2-33

load via

load via
DESCRIPTION
Down-line loads a remote node on the same Ethernet by way of the specified
circuit. You must include the physical address in the command.
With the load via command, the node that initiates the loading sequence is also
the load host that perfonns the down-line load.

RESTRICTIONS
Before you can execute this command:
•

You must have superuser privileges.

•

The mop_mom utility must be installed during the ULTRIX. software
installa tion.

•

Service must be enabled on the remote node.

•

You must have the service password if a DECnet service password is defined
on the remote node.

SYNTAX

load via circuit-id

address address
from load-file
host node-id
name node-name
physical address E-address
secondary [loader] file
[service] password service-password
tertiary [loader] file

where
address

Specifies the address that the node is to use when it comes up.

node-address

from load-file

Specifies the file containing the system software to be
down-line loaded.

host node-id

Specifies the default host that the node is to use when it comes
up.

name node-name
physical address

Specifies the name that the node is to use when it comes up.

E-address

secondary [loader]
file

2-34 NCP Command Descriptions

(For Ethernet nodes only.) Identifies the Ethernet physical
address that the node currently uses to identify itself. If the
circuit is an Ethernet circuit, you must include the physical
address in the command.
Specifies a file containing secondary loader software for
down-line loading to the node.

load via

c
[service] password
seroice-password

tertiary [loader]

Specifies the password required to trigger the bootstrap
mechanism on the node. The password is a hexadecimal
value of 1 to 16 characters.

file

Specifies a file containing tertiary loader software for down-line
loading to the node.

via circuit-id

Specifies the circuit over which the load is to take place.

EXAMPLE
This command loads the node connected to the executor node by circuit una-O.
ncp>load via una-O physical address aa-OO-03-00-01-19 service password FF55~

C'
)

o
NCP Command Descriptions

2-35

loop ci rcuit

loop circuit
DESCRIPTION
Tests a circuit between the executor and another node in the network. You can
specify a destination node using either its node name or its physical address. If
you do not specify a destination node, the loop request is sent to the multicast
address and the first node to respond completes the loop test.
If you specify a destination node, you can also specify a third node to assist with
the test. The help parameter lets you specify the type of assistance you want.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

loop circuit

node node-name
physical address E-address
help help-type
node node-name
full .
assistant node node-name
receive.
physical address E-address
[

{transmit}

{assistant physical address E-address }

count count
length length
mixed
[ with { ones
zeros
where
assistant
physical address

Specifies the physical address (not a multicast address) of an
Ethernet node that is to assist in the loop circuit test.

E-address

assistant node
node-name

circuit
circuit-id

count count

Specifies the name of an Ethernet node that is to assist in the
loop circuit test.
(Does not apply to X.25 circuits.) Specifies the circuit to use for
the loopback test.
Specifies the number of blocks to be sent during loopback
testing. The valid range is 1 (default) through 1024.

c
2-36

NCP Command Descriptions

loop circuit

c
help help-type

Specifies the degree to which a third node is to assist with an
Ethernet loop circuit test. Choose one of the following types:
full
(Default if an assistant node is
specified but help is not.) The
assistant node is to both receive
and transmit the test packet (see
the example).

receive

The assistant node is only to
receive the test packet.

transmit

The assistant node is only to
transmit the test packet.

NOTE

If you specify help, you must
also specify either the physical
address and assistant
physical address parameters
or, if the addresses are not
known, the node and assistant
node parameters.
length length

LevelofABsutance

Maximum Length

No assistance

1486 bytes

Transmit or receive
assistance

1478 bytes

Full assistance

1470 bytes

node node-name

Specifies the name of an Ethernet node that is to be the
destination of a loop-test message.

physical address

Specifies the physical address (not a multicast address) of
an Ethernet node that is to be the destination of a loop-test
message.

E-address

with

Specifies the length in bytes of each block to be sent during
loopback testing. The default is 40 bytes. When testing
over the Ethernet, the allowable length is from 1 byte to the
maximum length of the data pattern, which varies according to
the level of assistance:

Specifies the type of binary information to be sent during
testing. If you omit this parameter, a combination of ones
and zeros (the mixed data type) is sent. Choose one of the
following data types:
mixed
(Default.) A combination of ones and zeros.

ones
zeros

NCP Command Descriptions

2-37

loop circuit

EXAMPLE
This command tests the circuit una-O with the assistance of the node specified in
assistant physical address by performing the following tasks:
1. The initiating node sends a test packet to the assistant node.

2. The assistant node processes the packet and passes the packet to the
destination node specified in the physical address.
3. The destination node receives the packet and transmits the packet back to
the assistant node.
4. The assistant node then returns the packet to the initiating node.
5. The count parameter indicates that this process is to be performed 10 times.
ncp>loop circuit una-O help full physical address aa-OO-04-00-f9-04
assistant physical address aa-OO-04-00-04-a9 count 10 ~

(-~/'~- ---"\

\,,_~7"

c
2-38

NCP Command Descriptions

loop executor

c
loop executor
DESCRIPTION

Tests the executor node in the network. You can include access control
infonnation if the node requires it. This command causes test blocks of data
to be transmitted to the specified node.

SYNTAX
count count
length length
loop executor
{ mixed
[ with ones
zeros
where

executor
count count

c
(~:

Specifies the executor node for loopback testing.
Specifies the number of blocks to be sent during loopback
testing. The valid range is 1 (default) through 1024.

length length

Specifies the length in bytes of each block to be sent during
loopback testing. The length must be a decimal integer in the
range of 1 through n, where n must be less than the smaller of
either the local looper buffer size or the remote mirror buffer
size. The default is 40 bytes.

node node-id
with

Specifies a node for loopback testing.
Specifies the type of binary information to be sent during
testing. If you omit this parameter, a combination of ones
and zeros (the mixed data type) is sent. Choose one of the
following data types:
mixed
(Default.) A combination of ones and zeros.

ones
zeros

EXAMPLE
This command loops 10 blocks of mixed test messages to executor node. Each
block is 40 bytes.
ncp> loop executor count 1 0

o
NCP Command Descriptions 2-39

loop node

loop node
DESCRIPTION
Tests a node in the network. You can include access control infonnation if the
node requires it. This command causes test blocks of data to be transmitted to
the specified node.

SYNTAX
count count
length length
loop { node node-id[acc-con-infol }
{ mixed
with
ones
[
zeros
where
ace-eon-info

Specifies access control information (if required by the remote
node).

count count

Specifies the number of blocks to be sent during loopback
testing. The valid range is 1 (default) through 1024.

length length

node node-id
with

ones
zeros

EXAMPLE
This command loops 10 blocks of mixed test messages to remote node OHIO.
Each block is 40 bytes.
ncp>loop node ohio count 10

c
2-40

NCP Command Descriptions

pu rge ci rcu it

purge circuit
DESCRIPTION
Removes specified circuit parameters from the permanent database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
. . . [reCeiVe password
purge circuit cl,rcul,t-td transmit password

where
circuit circuit-id
receive password
transmit password

Specifies the circuit for which parameters are to be removed.
Removes the circuit's receive password.
Removes the circuit's transmit password.

EXAMPLE
This command deletes all parameters for circuit una-O from the permanent
database.
ncp>purge circuit una-O

o
NCP Command Descriptions 2-41

purge executor

purge executor
DESCRIPTION
Resets specified executor parameters to their initial values in the permanent
database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
purge executor

identification
}
incoming timer
{ outgoing timer

where
identification

Removes the text identification string for the executor node.
The valid range is 1 to 32 alphanumeric characters.

incoming timer
outgoing timer

Resets the local node's incoming timer to its default value.
Resets the local node's outgoing timer to its default value.

EXAMPLE
This command resets the local node's incoming timer to its default value in the
volatile database.
ncp> purge executor incoming timer

c
2-42

NCP Command Descriptions

purge logging

c
purge logging
DESCRIPTION

Removes specified logging parameters from the permanent database.

RESTRICTIONS
You must have superuser privileges to execute this command.
Whenever you specify a circuit, line, node, or sink in a purge logging command,
you must also include an event list or known events parameter.

SYNTAX

,
·
C

known logging }
logging console
purge { logging file
logging monitor

name
events event-list
known events
circuit circuit-id ]
[ Ii ne line-id
node node-id
sink {executor .
[
node node-£d

where
cl rcu it circuit-id
events event-list

Inhibits event logging for the specified circuit.

known events

Removes all known events that DECnet-ULTRIX can generate
for the specified component.

known logging
line line-id
logging console
logging file
logging monitor
name

Removes parameters for all known logging components.

Removes the event class and types specified in event-list for the
specified component.

Inhibits event logging for the specified line.
Removes parameters for the console-logging component.
Removes parameters for the file logging component.
Removes parameters for the monitor logging component.
Returns the specified logging component to its default name
(console: /device/console; file: /usr/adm/eventlog; monitor

evl).
node node-id
sink

Inhibits event logging for the specified node.
Inhibits logging of the specified events at the specified node.
Choose one of the following parameters:
executor
This is the default setting. Events are not to
be logged at the executor node.

node

node-id

Events are not to be logged at the specified
node

NCP Command Descriptions 2-43

purge logging

EXAMPLE
This command ceases logging of event 2.1 to the console.
nop>purge logging console event 2.1

c
2-44 NCP Command Descriptions

purge node

C:
purge node
DESCRIPTION

Removes the names associated with the nodes or removes specified node
parameters from the permanent database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

purge { node node-id }
known nodes

diagnostic file
dump file
hardware address
host
load file
name
secondary loader
service circuit
service password
tertiary loader

or
purge { node node-id } all
known nodes
where

all

Removes all parameters for the specified node(s) so that the
network no longer recognizes the node(s). Use of all precludes
the use of any other parameters.

diagnostic file
dump file
hardware address
host
known nodes
load file
name

Removes the identification of the down-line load diagnostic file.

node node-id
secondary loader

Performs the specified function for the specified node only.

Removes the up-line dump file identification.
Removes the Ethernet address of the system hardware.
Removes the host node identification.
Performs the specified function for all known nodes.
Removes the identification of the down-line load file.
Removes the node name(s) associated with the specified
node(s).
Removes the identification of the secondary down-line loading
file.

service circuit

Removes the circuit parameter associated with the node for
down-line loading purposes.

service password

Removes the password parameter. This password parameter is
required to trigger the bootstrap mechanism of the node to be
down-line loaded.

NCP Command Descriptions 2-45

purge node

tertiary loader

Removes the identification of the tertiary down-line loading
file.

EXAMPLE
This command removes all information for node BOSTON from the permanent
database.
ncp>purge node boston all ~

c
2-46

NCP Command Descriptions

purge object

c
purge object
DESCRIPTION
Removes specified object(s) from the permanent database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
purge { object object-name }
known objects

where
known objects

Specifies that parameters are to be removed for all known
objects.

object object-name

Specifies the object for which parameters are to be removed.

EXAMPLE
This command removes the network terminal handler (dtermd) from the
permanent database.
ncp> purge object dtermd ~

o
NCP Command Descriptions

2-47

set circuit

set circuit
DESCRIPTION
Modifies specified circuit parameter(s) in the volatile database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

set circuit circuit-id

hello timer seconds
receive password password
state {~~ }

transmit password password

set circuit circuit-id all

where
all

Updates the volatile database with all of the parameters
defined for the specified circuit in the permanent database.
Use of all precludes use of any other parameters.

circuit circuit-id
hello timer

Specifies the circuit for which parameters are to be modified.

seconds

receive password
password

transmit password
password

Specifies the frequency of routing hello messages sent to
adjacent nodes on the circuit. The range is 1 through 8,191.
Specifies a 1- to 8-character ASCII password associated with
the circuit that the executor expects to receive from the remote
node during a routing initialization sequence.
Specifies a 1- to 8-character ASCII password associated with
the circuit that the executor sends to the remote node during a
routing initialization sequence.

EXAMPLES
1. This command updates the volatile database with all of the parameters
defined for circuit qna-O in the permanent database.
ncp>set circuit qna-O all

2. This command makes circuit una-O unavailable for use.
ncp>set circuit una-O state off

c
2-48 NCP Command Descriptions

set executor

set executor
DESCRIPTION
Creates or modifies specified executor node parameters in the volatile database.
NOTE

If you use the set executor command to issue a series of commands at
a remote node, you can use the tell prefix to issue an ncp command to
yet another remote node.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

set executor

address node-address
delay factor number
delay weight number
gateway access {diSable }
enable
gateway user login-name
identification id-string
Inactivity timer seconds
incoming proxy {diSable }
enable
incoming timer seconds
maximum links number
maximum node counters number
name node-name
outgoing proxy {diSable }
enable
outgoing timer seconds
pipeline quota number
retransmit factor number
segment buffer size number
state {

~~ut

}

restricted

or
set executor all
where
all

Updates the volatile database with all of the parameters
defined for the executor node in the permanent database. Use
of all precludes use of any other parameters.

NCP Command Descriptions

2-49

set executor

delay factor
number

delay weight
number

gateway access

Specifies a number to multiply times 1116 of the estimated
round-trip delay to a node in order to set the retransmission
timer for that node. The range is 1 through 255.
Specifies a value to apply to a current round-trip delay to a
remote node in order to update the estimated round-trip delay
time. The range is 1 through 255.
Specifies whether or not the executor allows the DECnet
objects fal and dlogind to provide access to the Internet
network. The default value is disable if you choose not to
install the Gateway during the DECnet--ULTRIX installation
procedure. Otherwise, the default value is enable. Choose one
of the following values:
disable
Turns off file transfer and remote log-in
Internet access.

enable
gateway user
login-name

identification
id-string

inactivity timer
seconds

incoming proxy

Specifies a default log-in name under which the DECnet
objects fal and dlogind are to run if gateway access is enabled
and a gateway request is received. The range is 1 through 32
characters.
Specifies a text identification string for the executor node.
The range is 1 through 32 characters. You must use double
quotation marks ('t) to delimit a string with blanks or tabs. To
include a quoted string within an identification string, enclose
the quoted string within single quotation marks.
Specifies the maximum time the executor will allow a link
to remain idle (no user data traffic) before it checks to see
whether the circuit still works. The range is 1 through 1024.
Specifies whether the executor honors or ignores proxy log-in
requests present on incoming logical links. Choose one of the
following values:
disable
All incoming proxy requests are ignored.
Instead, access control information supplied
in each connect request is used to validate the
request.

enable

incoming timer
seconds

maximum links
number

2-50

NCP Command Descriptions

Turns on file transfer and remote log-in
Internet access.

(Default.) Incoming proxy requests are
honored, based on the source user, the source
node, and the access control information.

Specifies the maximum time a process has to answer an
incoming connect request. If the process does not answer the
connect request within this time interval, the node will reject
the connect request on behalf of the process. The range is 1
through 1024.
Specifies the maximum number of active logical links for the
executor node. The range is 1 through 1024. If you use this
parameter in a set command, you must specify a value greater
than the current maximum number of links. To decrease the
value, you must issue a define command and restart the
system.

set executor

c
maximum node
counters

Specifies the maximum number of node counters allowed. The
range is 4 through 255, and the default is 32.

number

NOTE

If you use this parameter in a
set command, you must specify
a value that is greater than
the current maximum number
of node counters. To decrease
the value, you must issue a
define command and restart
the system.
name node-name
outgoing proxy

outgoing timer
seconds

pipeline quota
number

c:'

retransmit factor
number

segment buffer size
number

state

Specifies the node name of the executor.
Specifies whether or not the executor requests proxy log-in on
outgoing connect requests. Choose one of the following values:
disable
The executor does not request proxy log-in
on outgoing logical links, even when the user
process attempts to enable it.
enable
(Default.) The executor requests proxy log-in
on all outgoing logical links, unless the user
process explicitly disables it.
Specifies the maximum time the executor node waits for a
pending connect request to be answered at a destination node.
If the request is not answered in this time interval, the source
process receives an error indication. The range is 1 through
1024.
Specifies the maximum number of bytes of buffer space
that NSP can use for transmission and reception for each
logical link. The range is 2,000 to 16,000. For satellite .
communications, you should use a value of 6,000 bytes or
greater. The default is 4,096.
Specifies the number of times the executor restarts the
retransmission timer before the logical link is disconnected.
The range is 1 through 1024.
Specifies the size of the NSP message segment to be sent.
This value is the maximum size message that the End
Communications layer can transmit; it does not include routing
or data link overhead. The range is 1 through 1,478, and the
default is 576.
Specifies the executor node's operational state. Use of state
precludes use of any other parameters. Choose one of the
following values:
on
Allows logical links.

off

Does not allow new links, terminates existing
links, and stops route-through traffic.

restricted
shut

Does not allow new inbound links.
Does not allow new links but does not
terminate existing links switches to the off
state when all links have quit.

NCP Command Descriptions

2-51

set executor

EXAMPLE
This command sets the maximum number of active logical links for the executor
node to 20 in the volatile database.
ncp> set executor maximum links 20

c
2-52 NCP Command Descriptions

set executor node

c
set executor node
DESCRIPTION

Sets the default executor as the specified remote node. This causes subsequent
remotely executable ncp commands to be executed at the specified destination.

RESTRICTION
You cannot use the tell prefix with this command.

SYNTAX
set executor node node-id[acc-con-info]

where

ace-eon-info

Specifies access control information (if required by the remote
node).

node node-id

Specifies the remote node (by address, alias, or name) where
subsequent ncp commands will be executed.

l~.
I

EXAMPLE
This command sets remote node EARTH (user: people; password: peace) to
executor status. Future commands will be sent to node EARTH for execution.
ncp>set executor node earth/people/peace

c
NCP Command Descriptions

2-53

set line

set line
DESCRIPTION
Modifies the specified line parameter(s) in the volatile database.

RESTRICTION
When you change the protocol and duplex parameter values of a point-to-point
device, the operation mode of the device does not change until you restart the
circuit. Therefore, you should turn the circuit off before changing the parameter,
and then turn it back on afterward. For example:
ncp>set circuit dmv-O state off ~
ncp>set line dmv-O protocol ddcmp dmc duplex half
ncp>set circuit dmv-O state on
~

SYNTAX

set line line-id

controller { loopback }
normal
duplex {fUll }
half
ddcmp dmc }
protocol { ddcmp point
ethernet

set line line-id all
where

all

Updates the volatile database with the parameters defined for
the specified line in the permanent database.

controller

Specifies the controller mode for the line. Choose one of the
following qualifiers:
loopback
Internal device loopback mode.

duplex

Represents the Physical Link hardware duplex mode of the
line device. {Valid for DDCMP point-to-point devices only.}
Choose one of the following qualifiers:
full
Full-duplex mode.

normal

half
line line-id

Normal operating mode.

Half-duplex mode.

Specifies the line for which parameters are to be modified.

c
2-54 NCP Command Descriptions

set line

protocol

Specifies the Data Link protocol to he used on the line. Choose
one of the following parameters:
ddcmp dmc
Protocol for the DMC emulator.
This setting is valid for dmv lines
only.

ddcmp point

Protocol for one end of a DDCMP
point-to-point connection. This
is the default for all DDCMP
point-to-point connections,
including dmv, dmc, and dmr
lines.

ethernet

Protocol for an Ethernet line. This
is the default and the only valid
choice for Ethernet lines (una, qna,
sva, and hnt).

EXAMPLE
This command sets the controller for line una-O to the loopback state.
ncp> set line una-O controller loopback ~

C~,'"
/

o
NCP Command Descriptions

2-55

set logging

set logging
DESCRIPTION
Creates or modifies logging component parameters in the volatile database.

RESTRICTIONS
You must have superuser privileges to use this command.
Whenever you specify a circuit, line, node, or sink in a set logging command, you
must also include an events list or known events parameter.

SYNTAX
name name

state {~~ }
known logging }
logging console
logging file
logging monitor

events list
known events
circuit circuit-id ]
[ line line-id
node node-id
sink { executor
[
node node-id

} 1

where

circuit circuit-id
events list
known events

Logs the specified event(s) occurring on the specified circuit.
Specifies the event class and type(s) to be logged.
Specifies that all events that DECnet-ULTRIX. can generate
are to be logged.

known logging

Indicates that the specified parameters are to be created or
modified for all known logging components.

line line-id
logging console

Logs the specified event(s) occurring on the specified line.

logging file

Indicates that the specified parameters are to be created or
modified for the file logging component.

logging monitor

Indicates that the specified parameters are to be created or
modified for the monitor logging component.

name name

Specifies the name of the console, monitor program, or file to
which events are to be logged. The default name for a console
is Idevice/console; for a monitor program it is evl and for a
file it is /usr/adm/eventlog.

node node-id

Logs the specified event(s) occurring on the specified node.

Indicates that the specified parameters are to be created or
modified for the console logging component.

c
2-56

NCP Command Descriptions

set logging

sink

Identifies the node where the specified events are to be logged.
Choose one of t~e following qualifiers:
executor
(Default) executor node.

node node-id
state

The specified remote node.

Sets the operational state of the logging component on the
executor node. When the state is off, events are discarded.

EXAMPLES
1. This command directs any known events on circuit una-O to node BOSTON.

C'
/

nop>set known logging known events circuit una-O sink node boston ~

2. This command directs any occurrence of event 2.1 to the console at node

PARIS.
nop>set logging console event 2.1 sink node paris

o
NCP Command Descriptions 2-57

set node

set node
DESCRIPTION
Modifies a node specification in the volatile database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

set { node node-id}

address node-address
diag nostic file file
dump file file
hardware address E-address
host node-id
load file file
name node-name
secondary [loader] file
service {diSable }
enable
service circuit circuit-id
[service] password service-password
tertiary [loader] file

or
set { node node-id } all
where
all

Updates the volatile database with all of the parameters
defined in the permanent database. Do not use any other
parameter on the same command line.

address

Specifies a new node address for the node.

node-address

diagnostic file
file

dump file file

Specifies the file that is to receive a copy of the system at the
time of the crash when the node is up-line dumped.

hardware address

E-address

2-58

(For Ethernet nodes only.) Specifies the file to be read when
the node is down-line loaded and requests diagnostics.

host node-id

Specifies a host node for all service operations. The default
value is the executor node ID.

known nodes

(Valid for all only.) Specifies that the function is to be
performed for all known nodes.

NCP Command Descriptions

set node

c
load file file

Specifies a file containing the system software for down-line
loading to a node.

name node-name

Specifies a new (unassigned) node name to be associated with
the node-address used as the node-id in this command.

node node-id

Specifies the node for which the specified function is to be
performed.

secondary [loader]

Specifies a file containing secondary loader software for
down-line loading to the node.

file

service

Specifies whether the node is enabled or disabled for down-line
loading.

service circuit

Specifies the circuit to be used for down-line loading and
up-line dumping. This circuit is the default value for the via
parameter of the load command.

circuit-id

[service] password
service-password

tertiary [loader]
file

EXAMPLE
This command associates the name BURGER with node 12.
ncp>set node 12 name burger ~

o
NCP Command Descriptions

2-59

set object

set object
DESCRIPTION
Creates or modifies parameters for specified objects in the volatile database.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX

set { object obj~ct-name }
known objects

accept { deferred
}
Immediate
default user login-name
file file-id
number number
type { sequenced packet }
stream

or
set { object obj~ct-name } all
known objects

//--~-"

'---_/

where
accept

Specifies whether incoming connect requests are to be accepted
or rejected by the DECnet object spawner or whether they are
to be forwarded to the object for processing. Choose one of the
following modes:
The object processes any optional data sent
deferred
with a connect request and can set optional
data to be returned when it accepts or
rejects the connect.

immediate

(Default.) The DEC net object spawner
determines whether to accept or reject all
connect requests.

all

Updates the volatile database with all of the parameters
defined for the specified object in the permanent database. Use
of all precludes use of any other parameters.

default user

Specifies a default log-in name under which the object is to
run if no access control information is supplied with a connect
request and no proxy information is defined locally.

file file-id

Specifies an executable file or shell script used to invoke the
specified object.

number number

Specifies the object number to be identified with the specified
object name. The default is O. See Appendix B for a list of
object names and numbers.

known objects

Specifies that parameters are to be created or modified for all
known objects.

2-60 NCP Command Descriptions

set object

object object-name

Specifies that parameters are to be created or modified for the
named object only (a maximum of 16 alphanumeric characters).

type

Identifies the socket type. Choose one of the following socket
types:
(Default) provides a bidirectional, reliable,
sequenced
sequenced, and unduplicated flow of data
packet
while preserving record boundaries.

stream

Provides same data flow properties as
above without record boundaries.

EXAMPLE

This command defines the Network Management Listener (nml) as object number
19 with letc/nml as the executable file. It also specifies that nml is to run under
the log-in name "guest" if no access control information is supplied with a connect
request and no proxy information is defined locally.
ncp>set object nml number 19 file /etc/nml default user guest

o
NCP Command Descriptions

2-61

show circuit

show circuit
DESCRIPTION
Displays specified circuit information stored in the volatile database.

SYNTAX
characteristics ]
counters
show { circuit circuit-id
}
known circuits
[ status
summary
where

circuit circuit-id
characteristics
counters
known circuits
status

Displays information for the specified circuit only.
Displays parameters that are currently set for the circuit.
Provides counter information for circuits, lines, and nodes.
Displays information for all known circuits.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.

summary

(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays circuit error and performance statistics for all known
circuits in the volatile database.
ncp>show known circuits counters

Known Circuit Volatile Counters as of Thur Nov 16 10:30:56 EST 1990
Circuit

una-O
4127
6407
11736

o
o

o
o
o

9679324
61282059
75268
79489

o
ncp>

2-62

NCP Command Descriptions

Seconds since last zeroed
Terminating packets received
Originating packets sent
Terminating congestions lost
Transmit packets received
Transmit packets sent
Transmit congestion loss
Initialization failure
Bytes received
Bytes sent
Data blocks received
Data blocks sent
User buffer unavailable

show executor

show executor
DESCRIPTION
Displays specified local node information stored in the volatile database.

SYNTAX
characteristics ]
show executor

[

~~~~~ers
summary

where
characteristics
counters
status

Displays parameters that are currently set for the executor.
Provides counter information for circuits, lines, and nodes.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.

summary

(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays local node status information from the volatile database.
ncp>show executor status

Executor Volatile Status as of Thu Nov 16 10:37:23 EST 1990

Executor node

State
Physical address
ncp>

2.95 (OHIO)
On
aa-04-00-00-53-10

o
NCP Command Descriptions

2-63

show line

show line
DESCRIPTION
Displays specified line information stored in the volatile database.

SYNTAX
characteristics ]
counters
show { line line-id
}
known lines
[ status
summary
where

characteristics
counters
known lines
line line-id
status

summary

Displays parameters that are currently set for the line.
Provides counter information for circuits, lines, and nodes.
Displays information for all known lines.
Displays information for the specified line only.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays information about line una-O.
ncp> show line una-O surrunary

Line Volatile Summary as of Thu Nov 16 10:40:17 EST 1990
Line

State

UNA-O
ncp>

c
2-64

NCP Command Descriptions

show logging

show logging
DESCRIPTION
Displays specified logging information stored in the volatile database.

SYNTAX
known logging
characteristics ]
logging console
status
known sinks
show { logging file
summary
[
sink
node node-id ]
} [
logging monitor
events
where
characteristics

Displays parameters that are currently set for the executor,
line, or circuit.

events

Displays event class and type information for the given logging
component.

known logg ing
known sinks

Displays information for all known logging components.

logging console
logging file
logging monitor
sink node node-id
status

summary

(Default) displays logging information for all known sink
nodes.
Displays information for the console logging component.
Displays information for the file logging component.
Displays information for the monitor logging component.
Displays logging information for the specified sink node.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.
(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays event class and type information for the logging file on
node N1834P.
ncp> show logging file events sink node n1834p

Logging Volatile Events as of Thu Nov 16 10:44:04 EST 1990
Logging = file
No Information
ncp>

o
NCP Command Descriptions 2-65

show node

show node
DESCRIPTION
Displays specified node information stored in the volatile database.

RESTRICTION
No information is displayed for an end node until a link has been established to
it. The node may appear to be unreachable even when it is not.

SYNTAX
characteristics ]
node node-id
counters
show { active nodes }
[ status
known nodes
summary
where

active nodes

Displays information for all nodes that are adjacent,
designated routers, or connected to the executor by a logical
link.

characteristics
counters
known nodes
node node-id
status

Displays parameters that are currently set for the node.
Provides counter information for circuits, lines, and nodes.
Displays information for all known nodes.
Displays information for the specified node only.
Shows information that usually reflects network activity for
the running network. Depending on the component, this can
include the local node and its operational state, reachable and
unreachable nodes, and circuits and lines and their operational
states.

summary

(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays error and performance statistics for all known nodes in
the volatile database.
ncp> show node ohio counters

Node Volatile Counters as of Thu Nov 16 10:49:38 EST 1990
Executor node

2.95 (OHIO)

Aged packet loss

o Node unreachable packet loss

o
o

ncp>

2-66

NCP Command Descriptions

Node out-of-range packet loss
Oversized packet loss
Packet format error
Partial routing update loss
Verification reject

show object

show object
DESCRIPTION
Displays specified object information stored in the volatile database.

SYNTAX
show { object obj~ct-name } [CharacteriStiCS
known objects
summary

where

characteristics
known objects
object object-name
summary

Displays parameters that are currently set for the object.
Displays information for all known objects.
Displays information for the specified object only.
(Default) shows abbreviated information provided for the

characteristics and status display types.

EXAMPLE
This command displays information about the Network Management Listener
(nml).
ncp> show object nml ~
Object Volatile Summary as of Thu Nov 16 10:53:46 EST 1990
Object

Number

nml
ncp>

File
/usr/etc/nml

c
NCP Command Descriptions 2-67

tell

tell
DESCRIPTION
Sends an ncp command to a remote node for execution. tell sets the executor only
for the command that it prefixes.
NOTE

If you use the set executor or define executor command to issue a
series of commands at a remote node, you can still use the tell prefix to
issue an ncp command to yet another remote node.

SYNTAX
tell node-id [ace-eon-info] ncp-command

where
ace-eon-info

Specifies access control information required by the remote
node.

ncp command
node-id

Represents any ncp command that is remotely executable.
Specifies the node address or the node name of the remote
node.

EXAMPLE
This command sends the show executor command to node ART, and tells ART to
show characteristics of the executor node.
ncp>tell art show exec char~

'C.
I

2-68 NCP Command Descriptions

trigger node

c
trigger node
DESCRIPTION

Initiates a down-line load to the specified remote node. Initiates the loading
sequence for an unattended system.
NOTE

There is no way to determine the node that performs the down-line
load.

RESTRICTIONS
Before you can execute this command:
•

You must have superuser privileges.

•

The mop_moin utility must be installed during the ULTRIX software
installa tion.

•

Service must be enabled on the remote node.

•

You must have the service password if a DECnet service password is defined
on the remote node.

SYNTAX
trigger node node-id

}
physical address E-address
[service] password hex-password
{
via circuit-id

where
node node-id
physical address
E-address

[service] password

Specifies the remote node to be loaded.
Identifies the Ethernet physical address of the remote node.
Required for Ethernet circuits if the hardware address
parameter has not been specified in the volatile database.

hex-password

Specifies the DECnet service password for maintenance
operations such as down-line loading. Specify a hexadecimal
value of 16 digits.

via circuit-id

Specifies the circuit over which the operation is to take place.

o
NCP Command Descriptions

2-69

trigger node

EXAMPLE
This command initiates a down-line load to node BOSTON, whose DECnet service
password is aabb.
NOTE

Even though node BOSTON initiates the down-line load, there is no
way to determine which host will actually perlorm the down-line load.
ncp>trigger node boston password aabb

c
2-70

NCP Command Descriptions

trigger via

trigger via
DESCRIPTION
Initiates a down-line load to the specified remote node through the specified
circuit. Initiates the loading sequence for an unattended system through the
specified circuit. The circuit identification is obtained from the volatile database
on the executor node.
NOTE

There is no way to determine the node that performs the down-line
load.

RESTRICTIONS
Before you can execute this command:
•

You must have superuser privileges.

•

The mop_mom utility must be installed during the ULTRIX software
installation.

•

Service must be enabled on the remote node.

•

You must have the service password if a DECnet service password is disabled
on the remote node.

SYNTAX
trigger via circuit-id { physical address E-add~ess
}
[service] password servwe-password

where
via circuit-id
physical address
E-address

service password

Specifies the circuit over which the operation is to take place.
(For Ethernet nodes only.) Identifies the Ethernet physical
address that the node currently uses to identify itself. If the
circuit is an Ethernet circuit, you must include the physical
address in the command.
Specifies the remote node's service password.

service-password

EXAMPLE
This command initiates a down-line load sequence on the node connected to
circuit una-!. The node's service password is ffaa.
ncp>trigger via una-l physical address aa-OO-03-00-01 password ffaa

o
NCP Command Descriptions

2-71

zero circuit

zero circuit
DESCRIPTION
Sets circuit counters to zero for the specified circuit. The executor node maintains
these counters for each circuit.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
zero circuit circuit-id [counters]
where

circuit circuit-id

Specifies the circuit for which counters are to be zeroed.

EXAMPLE
This command sets circuit counters to zero for circuit una-O.
ncp> zero cireui t una-O

c
2-72

NCP Command Descriptions

zero executor

c
zero executor
DESCRIPTION

Sets node counters associated with and maintained on the executor node to zero.

RESTRICTION
You must have superuser privileges to execute this command.

c·

SYNTAX
zero executor [counters]

c
NCP Command Descriptions

2-73

zero line

zero line
DESCRIPTION
Sets line counters to zero for the specified line. The executor node maintains
these counters for each line.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
zero line line-id [counters]

where
line line-id

Specifies the line for which counters are to be zeroed.

EXAMPLE
This command sets the line counters to zero for line qna-O.
ncp> zero line qna-O

c
2-74 NCP Command Descriptions

zero node

zero node
DESCRIPTION
Sets node counters to zero for specified nodes in the volatile database. The
executor node maintains node counters for each node.

RESTRICTION
You must have superuser privileges to execute this command.

SYNTAX
zero { node node-id } [counters]
known nodes
where
known nodes
node node-id

C',/
I,

Zeros counters for all known nodes.
Zeros counters for the specified node.

EXAMPLE
This command sets the node counters to zero for node BOSTON.
ncp>zero node boston

o
NCP Command Descriptions

2-75

c
Chapter 3

Error Messages

This chapter outlines the ncp error message format and lists all messages in
alphabetical order, giving a short description of each. When possible, you should
correct the error condition and retry the command.

3.1

ncp Error Message Format

",,'

The ncp error messages have the following format:
ncp [ - Listener response]: error message[,error detail]
[extra text or command echo]
where

Listener response

Indicates when the error message is being displayed by the
Network Management Listener.

error message

Is the reason for the failure.

error detail

Is a detailed explanation of the failure (for certain error
messages.

extra text

Gives an additional system-specific explanation of the error
condition.

command echo

Is the command in error (if applicable). An arrow points to the
illegal condition.

The following example contains the error message, "Unrecognized keyword," and
the command echo, "tell boston sho lines." This message indicates an error in the
command line.
ncp: Unrecognized keyword
tell boston sho lines

The command should read, "tell boston sho known lines."

3.2 ncp Error Messages
This section lists the ncp error messages in alphabetical order, with a short
description of each message.

o
Error Messages 3-1

Bad loopback response
The message returned in a loopback test does not match the message sent. This
error is caused by a loopback protocol violation, bad data return, or bad message
length return. Check the integrity of the line. Make sure that you are not on a
noisy line.

Component in wrong state
The current operational state of the component precludes the requested operation.
The error detail identifies the component type. Check to see that the component
is in the correct state to perform the requested operation.

Connect failed
A logical link connect has failed for the reason described in one of the following
error details:

Access control rejected
The remote node could not understand or would not accept the access control
information. Make sure that you have a valid user name and password on
the remote system; then try again.

Insufficient network resources
Either the local node or the remote node had insufficient network resources
to create the logical link. You can increase the number of maximum links for
DECnet-ULTRIX by using the ncp set/define executor command, or reduce
the number of logical links in use.

Invalid node name format
The format of the specified node name is invalid. Use 1 to 6 alphanumeric
characters, including at least one alphabetic.

Invalid object name format
The remote node did not understand the object name format used by ncp to
identify the Network Management Listener. Contact the person responsible
for your network.

Local node shutting down
The local node is shutting down and will not allow any logical link
connections. Wait until your system resumes network activity, then try
again to connect.

No response from object
The Network Management Listener did not respond; for example, it may
have responded too slowly or terminated abnormally. Contact the person
responsible for your network.

Node unreachable
No path exists to the remote node. Make sure that DECnet is installed on
the remote node. Check to see that the DECnet circuit is running by using
the ncp show circuit status command. Check the status of the remote node
to see if it is up.
3-2

Error Messages

Object too busy
The remote nml object had insufficient resources available to accept the
connect request. Contact the person responsible for your network.

Remote node shutting down
The remote node is shutting down and will not accept any logical link
connections. Wait until the remote system reswnes network activity, then try
again to connect.

Unrecognized node name

The destination node name does not correspond to any known node address.
Enter a valid node name, which consists of from 1 to 6 alphanumeric
characters, including at least one alphabetic character. Check to see if the
node name is defined in the DECnet database by using the ncp show node
or show known nodes command. If the name is not defined, use the ncp set
command to define the node.

Unrecognized object
The remote node does not have a Network Management Listener. Contact the
person responsible for your network.

File 110 error
An error was encountered while reading or writing a file necessary to the
requested operation. The error detail identifies the database where the error
occurred. The file may be corrupted or may not exist. Make sure that the
DECnet files copied to your system at installation are in the right directories. See
DECnet-ULTRIX. Installation for a list of the files.

File open error
A file necessary for the requested operation could not be opened. The error
detail identifies the database where the error occurred. Make sure that the
DECnet files copied to your system at installation are in the right directories. See
DECnet-ULTRIX Installation for a list of the files.

Hardware failure
The hardware associated with the request could not perform the specified
operation. Contact the person responsible for your network, or call your Field
Service representative.

Incompatible management version
The Network Management Listener version is incompatible with ncp. You must
go to the remote system to execute the command.

Invalid file contents

The requested operation could not be performed because the files contained data
of an invalid form or value. The error detail identifies the database where the
error occurred. Look at the file to see if it is corrupted. See DECnet-ULTRIX
Installation for a list of the files.

Error Messages

3-3

Invalid identification
The identification of the component specified in the requested operation did not
have the proper syntax. For example, a device name that should have the syntax
dev-n, appears as unas. The error detail identifies the component type. Make
sure that the component name and unit number, if applicable, are correct and
configured into the system.
If this message is received on a loop circuit command, the following error detail
may be included:

Unable to find device
The device specified by the circuit ID does not exist.

Invalid message format
The information sent by ncp to a Network Management Listener was improperly
formatted or contained an invalid value. Submit an error report to your Digital
Software Services representative.

Invalid parameter grouping
The parameters furnished by the user for the requested operation cannot be
included in the same command. Check the appropriate ncp command description
in this manual. Often, use of the all parameter in an ncp command precludes the
use of any other command parameters.

Invalid parameter value
The value of a parameter furnished by the user for the requested operation was
not acceptable (for example, a numeric parameter was out of range). The error
detail identifies the type of parameter. Check the appropriate ncp command
description in this manual, and retry the command using a different parameter
value. If this message refers to the length parameter in a loop command, one
of the following error details may be included. In each of these cases, the length
was more than could be handled, and the maximum length is included with the
error message. Retry the command using a shorter length.

Ethernet message size exceeded
The length specified for blocks to be looped exceeds the maximum allowed.
(See the loop command descriptions in this manual for details.)

Looper size exceeded
The requested length exceeds the buffering capability of the active looper
task.

Mirror size exceeded
The requested length exceeds the buffering capability of the network
management loopback mirror.

Line communication error
The requested operation failed because of communication errors on the involved
line. Make sure that your system is properly attached to the network and that
the other node is up and running.

3-4

Error Messages

Line protocol error

The requested operation failed because of protocol errors on the involved
line. This condition usually implies either incompatible line protocols or
protocol-programming errors. It can also be caused by a line hardware error that
was not detected by the line protocol. (Line protocol can mean either the Data
Link Protocol or the Service Operation Protocol.)

Management program error
The network management software has detected an internal error. Contact
the person responsible for your network and/or submit a report to your Digital
Software Services representative.
If this error occurs on a loop command, one of the following error details may be
provided:

Bad data pattern developed
The software is unable to build a message because of a program error.

Incorrect optional data size on accept
The optional accept data from mir was improperly fonnatted.

Unable to get physical address from device
A request for a device's Ethernet physical address failed.

Mirror connect failed

"II\

The logical link to the network management loopback mirror could not be
connected. This error message usually has one of the following error details:

Abort by management
The connection was aborted by a third party, not by the user programs at
either end of the connection. Contact the person responsible for your network.

Abort by object

A programming error in the network management loopback mirror caused
it to abort the logical link. Submit an error report to your Digital Software
Services representative.

Access control rejected
Either the remote node or the network management loopback mirror could
not understand or would not accept the access control information. Make sure
you have a valid user name and password on the remote node; then try again.

Connection rejected by object

The logical link could not be connected because the network management
loopback mirror rejected the connection. This condition usually implies that
the loopback mirror is too busy to accept another logical link. Try to connect
later.

Error Messages 3-5

Disconnect by object
A programming error in the network management loopback mirror caused it
to disconnect the logical link. Submit an error report to your Digital Software
Services representative.

Insufficient network resources
Either the local node or the remote node had insufficient network resources
to connect the logical link. You can increase the number of maximum links
for DECnet-ULTRIX by using the ncp set executor and define executor
commands, or reduce the number of links in use.

Local node shutting down
The executor node is in the process of shutting down and is not accepting
any more logical link connections. Wait until your system resumes network
activity, and then try again to connect.

No response from object
The network management loopback mirror did not respond; for example, it
may have responded too slowly or terminated abnormally. Contact the person
responsible for your network.

Object too busy
The remote nml object had insufficient resources available to accept the
connect request. Contact the person responsible for your network.

Remote node shutting down
The remote node is shutting down and will not accept any logical link
connections. Wait until the remote node resumes network activity, then try
again to connect.

Unrecognized node name
The destination node name does not correspond to any known node address.
Enter a valid node name, which consists of from 1 to 6 alphanumeric
characters, including at least one alphabetic character. If the name is not
defined in the DECnet database, use the ncp set command to define the node.

Unrecognized object
The remote node does not have a network management loopback mirror.
Contact the person responsible for your network.

3-6

Error Messages

Mirror link disconnected
The logical link from ncp to the network management loopback listener was
unexpectedly disconnected. This error message usually has one of the error
details listed under "Mirror connect failed." See the error detail for a description
of the error and a recommended action.

No room for new entry
The requested operation could not be performed because it required the addition
of a new entry in a database that was already full. Contact the person responsible
for the remote system.

Operation failure
The requested operation failed. If an error detail is not provided, see the network
docwnentation for the remote system.

Oversized management command message
The ncp command message was too big to be received by the Network
Management Listener. Submit an error report to your Digital Software Services
representative.

Oversized management response
The message returned by the Network Management Listener was too big to
be received by ncp. Submit an error report to your Digital Software Services
representative.

Parameter missing

A necessary parameter for the requested operation was omitted. The error detail
identifies the type of parameter. Check the appropriate ncp command description
in this manual and reenter the command including the necessary parameter.

Parameter not applicable
The user supplied a parameter that is not applicable to the requested operation
on the specified component. The error detail identifies the type of parameter.
Check the appropriate ncp command description and reenter the command minus
the problem parameter.

Parameter value out of range
A numeric parameter value is outside the allowable range. Identify the
parameter by referring to the appropriate ncp command description; then
reenter the command.

Parameter value too long
The parameter value was too long to be accepted by the Network Management
Listener. The error detail identifies the type of parameter. Shorten the parameter
value, and then reenter the command.

Privilege violation
The user does not have sufficient privilege to perform the requested operation.
Log in as superuser and reenter the command, or contact the person responsible
for your network.

Redundant parameter
A parameter has been entered twice in the same command. Eliminate the extra
parameter and reenter the command.

Error Messages

3-7

Resource error
Network management had insufficient internal resources to perform the
requested operation.
On a loop command, the following error detail may also be provided:

Unable to check loopback state
The software could not open a socket to see whether the device is in loopback
state. Check to see that dli is configured into the system.

System-specific management function not supported
The requested operation is ULTRlX system-specific and is not supported by the
Network Management Listener. You must perform this operation on the remote
node.

Unrecognized command
The Network Control Program (ncp) does not support the command entered by
the user. Refer to the ncp command descriptions in this manual.

Unrecognized component
The component specified by the user does not exist. The error detail identifies
the component type. Make sure that the DECnet files copied to your system at
installation are in the right directories. See DECnet-ULTRIX Installation for a
list of the files.

Unrecognized function or option
The requested operation is not implemented by the executor. Refer to the ncp
command descriptions in this manual.

Unrecognized keyword
One of the keywords in a command is unknown to ncp. The command echo
flags the unrecognized keyword. Refer to the ncp command descriptions in this
manual.

Unrecognized parameter type
The command parameter identified in the error detail is not implemented by the
executor. Refer to the ncp command descriptions in this manual.

Unrecognized value
A parameter value specified by the user is unknown to ncp. The command echo
flags the faulty parameter value. Refer to the relevant ncp command description
in this manual.

c
3-8

Error Messages

c
Chapter 4

Event Messages

The DECnet-ULTRIX Event Logger (evl) is a network management tool that
records network activity. The Event Logger can record two categories of event
messages: event classes and event types. Event classes relate to specific layers
of the DECnet architecture, while event types relate to specific events within an
event class.

4.1

Event Classes
DECnet logging events fall into the event classes listed in Table 4-1. Events not
logged by DECnet-ULTRIX may be logged by other remote nodes. Check the
documentation for the remote system for details.
Table 4-1 : Event Classes

Event Class

Description

Network Management layer

Applications layer

Session Control layer

End Communications layer

4
51

Routing layer
Data Link layer

Physical Link. layer

7-479 1

Reserved for other DECnet products

480-511

Reserved for customer use

1Event class not logged by DECnet-ULTRIX.

4.2 Event Message Format
Event messages have the following format:
Event type class .type, [event-text]

Occurred dd-mon-yy hh:mm:ss.s on node address [(node-name)]
[component-type component-name]
[data]

Event Messages 4-1

where
Is the class in which the event occurred (see Table D-l.)

class
type

Is the specific event type number within that class.

event-text

Is the text describing the event (see Sections D.3 through D.6.)

dd-mon-yy

Is the date (day, month, and year) on which the event occurred.

hh:mm:ss.s

Is the time (hour, minutes, and seconds) at which the event
occurred.

address

Is the address of the node at which the event occurred.

node-name

Is the name of the node at which the event occurred.

component-type

Is either line, circuit, or node. If an event is not associated
with a particular component, this line is not present.

component-name

Is the name of the component that caused the event.

data

Is event-dependent text that gives more information about
the event. otten this text includes the name or address for
the component type for which the event applies. It may also
provide additional information about the cause of the event.

EXAMPLE:
This example shows an event-logging message indicating that an adjacent node is
unavailable.
Event type 4.18, Adjacency down
Occurred 21-May-87 08:17:11.0 on node 19.12 (PITSBG)
Circuit UNA-O
Adjacency listener receive timeout
Adjacent node = 19.160

The following sections list DECnetr-ULTRIX event messages by class and type for
each layer. Figure D-l shows the format in which the messages appear:

Figure 4-1: Event Message Format

0.0

EVENT CLASS

Event records lost
\._
_ _- J

EVENT MESSAGE TEXT

EVENT TYPE
LK~265-901

c
4-2

Event Messages

4.3 Network Management Layer Events
Event

Message

0.0

Event records lost
Events occurred too rapidly for the event logger to buffer them.
This message does not display any event qualifiers.

0.6

Passive loopback
The software initiated or terminated a passive loopback test on behalf of an
adjacent node.
This message displays the circuit name to which the event applies and the state
of operation qualifier (initiated or terminated).

4.4 Session Control Layer Events
Event

Message

2.0

Local node state change
The operational state of the local node changed because of an operator
command. Note that the transition from shut to off also happens automatically
when the last logical link is disconnected (under normal operation).

"\
C

This message displays the reason for the state change (operator command or
normal operation), the old state (on, off, shut, or restricted), and the new
state (on, off, shut, or restricted).
2.1

Access control failure
The local node rejected a connect request because of invalid access control
information.

This message displays the name and address of the source node, the object
type number and process ID of the source process requesting the connection,
the object type number and process ID of the destination process to receive the
connect request, and the invalid access control information (user ID, password,
and account information).

4.5 End Communications Layer Event
Event

Message

3.2

Node data base reused
The local node received a connect request from or tried to initiate an outgoing
connect to a node for which there is no counter block. All counter blocks have
been used, and one of the previously used blocks is available for this new node.
This results in the loss of node counters for the node that formerly occupied the
database entry.
This message displays the address and name of the node for which the database
entry was formerly used and the counters for that node.

c
Event Messages

4-3

4.6 Routing Layer Events
Event

4.3

Message
Oversized packet loss

A packet has been discarded because it was too large to forward to the
appropriate adjacent node. Nonnally, this condition occurs because the adjacent
node's buffer is too small or the source node sent a packet that was too large.
The latter condition can be handled by setting a smaller segment size at the
source node.
This message displays the packet header and the name of the circuit over
which the packet was to be forwarded. For contents of the packet header, refer
to the DECnet Digital Network Architecture (Phase lV), Network Management
Functional Specification.

4.4

Packet format error

A packet has been discarded because of a format error in the packet header.
Usually, this results from a programming error in packet fonnatting by the
adjacent node. It could also result from a circuit error not detected by circuit
protocol.
This message displays the first six bytes of the packet (in hexadecimal) and the
name of the circuit to which the event applies. For a point-to-point line this
message also displays the adjacent node.

4.6

Verification reject

This message is displayed for point-to-point lines only. It displays the first six
bytes of the packet header (in hexadecimal), the name of the circuit, and the
adjacent node to which the packet applies. An invalid verification message
was received. The password from the remote node does not match the 'circuit
receive password' set up in the database.
4.8

Circuit down

Under nonnal operating conditions, this event occurs when you set the circuit
or executor to the off state. It also occurs if there is a hardware problem with
the line or device. For point-to-point lines, this event can occur if the node
listen timer expires or invalid data is received in the hello message.
This message displays the name of the circuit to which the event applies. For
point-to-point lines, this message also displays the adjacent node name. In the
case of a hardware error, it also displays the following message:
Adjacent node listener received invalid data
4.9

Circuit down - operator initiated

This event is logged when the node identification in the hello message from the
remote node is not the expected one. This message displays the name of the
circuit and adjacent node to which the event applies. This message is displayed
for point-to-point lines only.
4.10

Circuit up

The basic initialization of a remote node has been completed by the device and
transceiver.
This message displays the name of the circuit to which the event applies, as
well as the name and address of the newly initialized node. For a point-to-point
line this message also displays the adjacent node.
4.11

Initialization failure - circuit fault

This event is logged when a verification message is not received within the
timeout period. This message is displayed for point-to-point lines only. It
displays the circuit, adjacent node, and reason for failure.

4-4

Event Messages

Event

Message

4.12

Initialization failure - software

This message is logged when the local node is unable to send the verification
message requested by the remote node due to lack of system resources. This
message is displayed for point-to-point lines only. It displays the circuit,
adjacent node, packet header, and reason for failure.
4.13

Initialization failure - operator initiated

The routing layer logs this message when it detects an area mismatch or
a version skew during the circuit initialization sequence. This message is
displayed for point-to-point lines only. It displays the circuit, adjacent node,
packet header, and reason for failure.
4.15

Adjacency up

For broadcast circuits (UNA and QNA), initialization has occurred with another
node on the Ethernet. End nodes log this message for only one node.
This message displays the adjacent node number.
4.18

Adjacency down

The remote node has recycled. This event could result from a remote node
restart or an invalid protocol message.
The message displays the reason why the adjacent node is down.

4.7 Event Log Summary
Table 4-2 summarizes the events logged by the event logger:

Table 4-2:

Event Log Summary

Class

Type

Entityl

Standard text

Counters

none

Event records lost

none

node

Automatic node counters

Node counters

node

Node counters zeroed

Node counters

any

Automatic counters

Counters

any

Counters zeroed

Counters

none

Access control reject

Source node, Source
process, Destination
process, User, Password,
Account

none

Invalid message

Message, Source node

none

Invalid flow control

Message, Source
node, Current flow
control

node

Data base reused

NSP node counters

none

Aged packet loss

Packet header

circuit

Node unreachable,
packet loss

Packet header, Adjacent
node

1 In this context, entity refers to a component or software module that can generate events.

(continued on next page)

Event Messages 4....5

Table 4-2 (Cont.):

Event Log Summary

Class

Type

Entityl

Standard text

Counters

circuit

Node out-of-range,
packet loss

Packet header, Adjacent
node

circuit

Oversized packet loss

Packet header, Adjacent
node

circuit

Packet format error

Packet beginning,
Adjacent node

circuit

Partial routing update
loss

Packet header, Highest
address, Adjacent
node

circuit

Verification reject

Node

circuit

Circuit down, circuit
fault

Reason, Adjacent node

circuit

Circuit down

Reason,Packet
header, Adjacent node

circuit

Circuit down, operator
initiated

Reason, Packet
header, Adjacent node

circuit

Circuit up

Adjacent node

circuit

Initialization failure,
line fault

Reason

circuit

Initialization failure,
operator fault, Reason,
Packet header, Received
version

Reason

node

Node reachability
change

Status

circuit

Adjacency up

Adjacent node

circuit

Adjacency rejected

Adjacent node, Reason

area

Area reachability change

Status

circuit

Adjacency down

Reason, Packet header,
Adjacent node

circuit

Adjacency down,
operator initiated,
Reason, Packet header

Adjacent node

circuit

Locally initiated state
change

Old state, New state

circuit

Remotely initiated state
change

Old state, New state

circuit

Protocol restart received
in maintenance mode

None

circuit

Send error threshold

Circuit counters

circuit

Select error threshold

Circuit counters

circuit

Block header format
error

Header (optional)

line

Send failed

Failure reason, Distance

(continued on next page)

Event Messages

,//

~'\

(-~

~_/

1In this context, entity refers to a component or software module that can generate events.

4-6

Table 4-2 (Cont.):

Event Log Summary

Class

Type

Entityl

Standard text

Counters

line

Receive failed

Failure reason, Ethernet
header

line

Collision detect check
failed

none

lIn this context, entity refers to a component or software module that can generate events.

c·
c

o
Event Messages

4-7

c
Chapter 5

Network Counters
The network software maintains counters for circuits, lines, and nodes. This
chapter lists all counters in alphabetical order within component groups. In
some cases, the counters respond to and reflect network events. In other cases,
the counters respond to and reflect normal activities such as messages sent and
messages received. Individual counter descriptions indicate whether that counter
increments when a corresponding event occurs (see Chapter 4 for a description
of event messages). Where possible, the description includes reasons why each of
the counters might be incremented.

A counter does not display a value greater than its maximum value. When
a counter overflows, it locks on the overflow value until it is zeroed. Counter
displays with an angle bracket (» indicate that the counter has overflowed. For
example, if the maximum value for a counter is 255, its overflow display is >255.
Each of the counter descriptions in this appendix includes the maximum value of
the counter.
Each category of counters maintains a timing counter (seconds since last zeroed)
that is zeroed when its associated counters are zeroed and starts when they start.
In this way, the timing counter logs the seconds since its associated counters were
zeroed to provide a time frame for them.

5.1 Circuit Counters
Circuit counters for DECnet-ULTRIX are maintained in the Network
Management layer, the Routing layer, and the Data Link layer.

5.1.1

Network Management Layer
Seconds since last zeroed
This counter is zeroed when the other circuit counters are zeroed. It then
increments by 1 every second so as to provide a time frame for the other
circuit counters. The overflow value is 65,535.

5.1.2

Routing Layer
Circuit down

This counter records the number of times that a circuit was declared down by
the executor. The overflow value is 255.

Network Counters 5-1

Initialization failure
This counter increments when the circuit could not be initialized by the
executor for network use. The overflow value is 255.

Originating packets sent
This counter records the number of packets sent by the executor over the
circuit. The overflow value is 4,294,967,295.

Terminating congestion loss
This counter records the number of packets intended for the node that were
discarded because the Routing layer could not buffer them. The overflow
value is 65,535.

Terminating packets received
This counter records the number of packets received by the executor with the
executor as the destination. The overflow value is 4,294,967,295.

Transit congestion loss
This counter records the number of packets received by the executor that were
to be routed to another node but were discarded because of heavy traffic on
the output circuit. The overflow value is 65,535.

Transit packets received
This counter increments when the executor receives a packet that is to be
routed to another node. The overflow value is 4,294,967,295.

Transit packets sent
This counter increments when the executor sends a packet through to another
node. The overflow value is 4,294,967,295.

5.1.3

Data Link Layer
Bytes received
This counter increments when a data byte is received on the circuit. The
count does not include Data Link Protocol overhead or bytes retransmitted
by the Data Link layer. It can be used with the Data blocks received counter
to determine the inbound traffic load on the circuit. The overflow value is
4,294,967,295.

Bytes sent
This counter increments when a data byte is sent on the circuit. The count
does not include Data Link Protocol overhead or bytes retransmitted by
the Data Link layer. It can be used with the Data blocks sent counter to
determine the outbound traffic load on the circuit. The overflow value is
4,294,967,295.

Data blocks received
This counter increments when a data block is received on the circuit. The
count does not include Data Link Protocol overhead. This counter can be used
as a statistical base for evaluating the other Data Link layer counters. The
overflow value is 4,294,967,295.

5-2

Network Counters

Data blocks sent
This counter increments when a data block is sent on the circuit. The count
does not include Data Link Protocol overhead or blocks retransmitted by the
Data. Link layer. It can be used as a statistical base for evaluating the other
Data. Link layer counters. The overflow value is 4,294,967,295.

Data errors inbound
This counter indicates the number of incoming data errors on the circuit. It
can have either of the following qualifiers: negative acknowledgments (NAKs)
sent, data field block check error NAKs sent, reply response. The overflow is
255.

Data errors outbound
This counter indicates the number of outgoing data errors on the circuit.
It can have any of the following qualifiers: NAKs received, header block
check error NAKs received, data field block check error NAKs received, reply
response. The overflow is 255.

Local buffer errors
This counter increments when a negative acknowledgment (NAK) is sent. It
can have either of the following qualifiers! NAKs sent, buffer unavailable;
NAKs sent, buffer too small. The overflow is 255.

Local reply time outs
This counter increments each time a message is retransmitted because the
retry timer for a sent message expired before a positive acknowledgment
(ACK) was received from the remote node. The overflow value is 255.

Remote buffer error
This counter increments when a negative acknowledgment (NAK) is
received. It can have either of the following qualifiers: NAKs received, buffer
unavailable; NAKs received, buffer too small. The overflow value is 255.

Remote reply timeouts
This counter increments each time a message is retransmitted because the
retry timer for a sent message expired before a positive acknowledgment
(ACK) from your node was received at the remote node. The overflow value is
255.

Selection intervals elapsed
This counter records the number of times that the executor turned a circuit
around or selected an adjacent node on both half-duplex and multipoint
circuits. This counter is used as a statistical base for the evaluation of the
counter for selection timeouts. The overflow value is 65,535.

Selection timeouts

This counter records the number of times that the executor turned a circuit
around or selected an adjacent node on both half-duplex and multipoint
circuits but the adjacent node failed to respond within the required time.
This can be caused by blocks being lost on the circuit in either direction
or by too small a value being specified for the executor's response timer.
Blocks are usually lost because of a partial, temporary, or total failure of the
communications line. This counter can have the following qualifier: No reply
to select. The overflow value is 255.

Network Counters

5-3

User buffer unavailable
This counter indicates the total number of times that a user buffer was not
available for an incoming frame that passed all filtering. User buffers are
supplied by users on receive requests. The overflow value is 65,535.

5.2 Line Counters
Line counters for DECnet-ULTRIX are maintained in the Network Management
layer and the Data Link layer.

5.2.1

Network Management Layer
Seconds since last zeroed
This counter is zeroed when the other line counters are zeroed. It then
increments by 1 every second so as to provide a time frame for the other line
counters. The overflow value is 65,535.

5.2.2

Data Link Layer
Blocks sentt initially deferred
This counter indicates the total number of times that a frame transmission
was deferred on its first transmission attempt. It is used to measure Ethernet
contention with no collisions. The overflow value is 4,294,967,295.

Blocks sentt multiple collisions
This counter indicates the total number of times that a frame was successfully
transmitted on the third or later attempt after normal collisions had occurred
on previous attempts. The overflow value is 4,294,967,295.

Blocks sent, single collision
This counter indicates the total number of times that a frame was successfully
transmitted on the second attempt after a normal collision had occurred on
the first attempt. The overflow value is 4,294,967,295.

Bytes received
This counter increments when a data byte is received on the line. The count
does not include Data Link Protocol overhead or bytes retransmitted by the
Data Link layer. It can be used with the Data blocks received counter
to determine the inbound traffic load on the line. The overflow value is
4,294,967,295.

Bytes sent
This counter increments when a data byte is sent on the line. The count does
not include Data Link Protocol overhead or bytes retransmitted by the Data
Link layer. It can be used with the Data blocks sent counter to determine
the outbound traffic load on the line. The overflow value is 4,294,967,295.

Collision detect check failure
This counter indicates the approximate number of times that a collision detect
was not sensed after a transmission. The overflow value is 65,535.

5-4

Network Counters

Blocks received
This counter increments when a data block is received on the line. The count
does not include Data Link Protocol overhead. It can be used as a statistical
base for evaluating the other Data Link layer counters. The overflow value is
4,294,967,295.

Data blocks sent
This counter increments when a data block is sent on the line. The count does
not include Data Link Protocol overhead or blocks retransmitted by the Data
Link layer. It can be used as a statistical base for evaluating the other Data
Link layer counters. The overflow value is 4,294,967,295.

Data overrun
This counter indicates the total number of times that the hardware lost an
incoming frame because it was unable to keep up with the data rate. The
overflow value is 65,535.

Local station errors

This counter records occurrences caused by a fault in a remote station or by
an undetected error on the channel inbound to this station. The overflow
value is 255. When this counter has a nonzero value, the type of failure is
listed:
Local receive overrun (LOVRN)

The local station experienced a receive overrun and sent out a negative
acknowledgment (NAK).
Local receive overrun (LOVR)

The local station experienced a receive overrun but did not send out a NAK.
Local transmit underruns (LUNDR)

The local station experienced a transmit underrun.
Local message header format error (LMBFE)

The local station sent a packet with a bad header for which the remote station
sent out a NAK.

Multicast blocks received
This counter indicates the total number of multicast blocks that have been
successfully received. The overflow value is 4,294,967,295.

Multicast bytes received
This counter indicates the total number of multicast data bytes that have
been successfully received (including bytes in the Ethernet data field but not
the Ethernet data link headers). The overflow value is 4,294,967,295.

Receive failure
This counter indicates the total number of blocks received with some data
error. (The blocks are data frames that passed either physical or multicast
address comparison.) The overflow value is 65,535. When this counter has a
nonzero value, the type of failure that has occurred is also listed:
Block check error

The frame failed the cyclic redundancy check (CRC). The problem can be
with either the local node or the remote node. The failure can be caused by
electromagnetic interference, late collisions, or a faulty hardware controller.
Use both circuit-levelloopback tests to see whether your node is working
correctly.

Network Counters 5-5

Framing error

The frame did not contain an integral number of 8-bit bytes. The problem can
be with either the local node or the remote node. The failure can be caused by
electromagnetic interference, late collisions, or a faulty hardware controller.
Use both circuit-levelloopback tests to see whether your node is working
correctly.
Frame too long

The frame was discarded because it was either longer than the maximum or
shorter than the minimum allowable length for the Ethernet. The remote
node is sending frame lengths that do not meet the requirements of the
Ethernet specification. The problem could be with the DEUNAlDEQNA, the
H4000 transceiver, the transceiver cable, the DELNI, or the transmitting
node.

Remote station error
This counter records occurrences caused by a fault in a remote station or by
an undetected data error on the channel inbound to this station. The overflow
value is 255. When this counter has a nonzero value, the type of failure that
has occurred is listed:
Remote receive overrun (ROVRN)

The remote station experienced a receive overrun and sent out a negative
acknowledgment (NAK).
Remote message header format errors (RMHFE)

The remote station sent a packet with a bad header for which the local station
sent out a NAK.
Remote streaming tributaries (RSTR)

The remote station failed to release the channel at the end of the selection
interval, or the maximum transmission interval (different for each
implementation) is exceeded without releasing the channel.

Send failure
This counter usually indicates the total number of times that a transmit
attempt failed. However, this counter can also increment on successful
transmissions when a DECOM (broadband transceiver) and DEQNA
controller are used together. The overflow value is 65,535. When this counter
indicates a failure, the type of failure that has OCCUlTed is also listed:
Carrier check failed

The data link did not sense a signal that must accompany transmission of
a frame. This condition indicates a failure during transmission because of a
problem with the DEUNAlDEQNA, the H4000 transceiver, or the transceiver
cable.
Excessive collisions

The maximum number of retransmissions resulting from collisions during
transmissions has been exceeded. Transmissions are failing because frames
being sent are colliding with frames being transmitted by other nodes. This
condition can occur if the network is overloaded or if there is a hardware
problem.
Frame too long

Either the DEUNAlDEQNA controller or the transceiver truncated the frame
at the maximum buffer size. Either your node tried to send a frame that was
too long, or the transceiver cut off the message too soon.

5-6

Network Counters

Open circuit

There is a break somewhere along the communications path. If this problem
exists on your node only, it is probably a fault with the DEUNAlDEQNA
option module, the H4000 transceiver, or the DELNI. In this case, use
the loopback tests to isolate the problem. If other nodes report the same
problem, the fault is probably with an H4000 transceiver connection, a
DELNI connection, or the Ethernet cable itself.

Remote failure to defer
A remote node began transmitting while your node was still actively
transmitting. Either there is a problem with the remote node's carrier
sense, or there is a weak transmitter on your node. Use the loopback test
with transmit assistance to determine whether the remote node can detect a
transmission from the assistant node.

Short circuit
There is a short circuit in either the Ethernet cable, the H4000 transceiver,
the DELNI, or the DEUNAlDEQNA option module. If this problem exists on
your node only, it is probably a faulty DEUNAlDEQNA. In this case, use the
loopback tests to isolate the problem.

System buffer unavailable
This counter indicates the total number of times that no system buffer was
available for an incoming frame. This can apply to any buffer between the
hardware and the user buffers (those supplied on receive requests). The
overflow value is 65,535.

Unrecognized frame destination
This counter indicates the number of times that a frame was discarded
because there was no enabled portal with the protocol type or multicast
address. The count includes frames received for the physical address,
broadcast address, or multicast address. The overflow value is 65,535.

User buffer unavailable
This counter indicates the number of times no user buffer was available for
an incoming frame that passed all filtering. The user buffer is one supplied
by the user on a receive request.

5.3 Node Counters
Node counters for DECnet-ULTRIX are maintained in the Network Management
layer and the End Communications layer. Additional counters are kept for the
executor node.

5.3.1

Network Management Layer
Seconds since last zeroed
This counter is zeroed when the other node counters are zeroed. It then
increments by 1 every second so as to provide a time frame for the other node
counters. The overflow value is 65,535.

o
Network Counters

5-7

5.3.2

End Communications Layer
Buffer unavailable
This counter indicates the total number of data segments discarded due to
insufficient cache buffering. The overflow value is 65,535.

Connects received
This counter increments when a connect initiation signal is received from the
associated node. The overflow value is 65,535.

Connects sent
This counter increments when a connect initiation signal is sent to the
associated node. The overflow value is 65,535.

Response timeouts
This counter increments when the associated node fails to respond within
the required time. This situation can be caused either by messages being
discarded in the network or by a wide variance in the round-trip delay to the
node. This condition normally indicates an overload condition in the network.
This should be considered a problem if 2 percent or more of the messages sent
are timed out. The overflow value is 65,535.

Total bytes received
This counter increments when bytes are received from the associated node at
the logical link level. The count includes bytes from both user messages and
logical link protocol messages. The overflow value is 4,294,967,295.

Total bytes sent
This counter increments when bytes are sent to the associated node at the
logical link level. The count includes bytes from both user messages and
logical link protocol control messages. The overflow value is 4,294,967,295.

Total messages received
This counter increments when a message is received from the associated
node at the logical link level. The count includes both user messages and
logical link protocol control messages. Furthermore, it includes internal
segmentation of user messages by the Network Services layer. The overflow
value is 4,294,967,295.
'

Total messages sent
This counter increments when a message is sent to the associated node at
the logical link level. The count includes both user messages and logical link
protocol control messages. It also includes the retransmission of a message.
The Network Services layer segments the user messages. The overflow value
is 4,294,967,295.

User bytes received
This counter increments when user data bytes are received from the
associated node at the logical link level. It includes only the user data from
data messages and from interrupt, connect, accept, reject, disconnect, and
abort functions. The overflow value is 4,294,967,295.

c
5-8 Network Counters

User bytes sent

This counter increments when user data bytes are sent to the associated node
at the logical link level. It includes only the acknowledged user data from
data messages and from interrupt, connect, accept, reject, disconnect, and
abort functions. It does not include retransmissions. The overflow value is
4,294,967,295.

User messages received
This counter increments when a user message is received from the associated
node at the logical link level. The overflow value is 4,294,967,295.

User messages sent
This counter increments when a user message is sent to the associated node
at the logical link level. The overflow value is 4,294,967,295.

5.3.3 Executor Node Counters
Aged packet loss
This counter increments when a packet is discarded because it has visited too
many nodes. The count is the total of all such discards by the executor node.
This counter is incremented each time the aged packet loss event occurs. The
overflow value is 255.

Node out-of-range packet loss
This counter increments when a packet is discarded because the destination
node address was greater than the maximum address defined for the executor.
The count is the total of all such discards by the executor node. This counter
is incremented each time the node out-of-range packet loss event occurs. The
overflow value is 255.

Node unreachable packet loss
This counter increments when a packet is discarded because its destination
node was unreachable. The count is the total of all such discards by the
executor node. The counter is incremented each time the node unreachable
packet loss event occurs. The overflow value is 65,535.

Oversized packet loss
This counter increments when a packet is discarded because it was larger
than the circuit buffer size. The circuit buffer size was previously established
between the executor node and the adjacent node. The counter is incremented
each time the oversized packet loss event occurs. The overflow value is 255.

Packet format error
This counter increments when a packet is discarded because of invalid packet
control information. The count is the total of all such discards by the executor
node. This counter is incremented each time the packet format error event
occurs. The overflow value is 255.

Partial routing update loss

This counter increments when part of a routing update is lost because it
contained a reachable node address that exceeded the maximum address
defined for the executor node. The count is the total of all such occurrences
at the executor node. Only routing nodes keep this counter. This counter
is incremented each time the partial routing update loss event occurs. The
overflow value is 255.

Network Counters 5-9

Peak logical links active
This counter records the number of active logical links between the executor
and all nodes (including itself). The overflow value is 65,535.

Verification reject
This counter increments when the executor rejects a verification request from
an adjacent node during routing initialization. The count is the total of all
such occurrences at the executor node. This counter is incremented each time
the verification reject event occurs. The overflow value is 255.

c
5-10

Network Counters

c
Appendix A

Command Summary
This appendix summarizes the ncp commands supported by DECnet-ULTRIX.

You may wish to review the graphic conventions listed in the Preface, especially
the use of braces { }, brackets [ ], and parentheses ( ). This summary also uses
the following notations:

* = Command cannot be used with the tell prefix.
S = Command can be used by someone with superuser privileges only.
A = Command can be used by all users.

I
ir i t ' "d [ receive password
c ear c CU Cl,rCUl,t-l,
transmit password

clear executor

clear executor node

identification
}
incoming timer
{ outgoing timer

c
S

clear

known logging }
logging console
{ logging file
logg ing monitor

name
events event-list
known events
circuit circuit-id ]
[ line line-id
node node-id
sink { executor
}
[
node node-id

c
Command Summary A-l

diagnostic file
dump file
hardware address
host
load file
name
secondary loader
service circuit
service password
tertiary loader

clear { node node-id }
known nodes

or
clear { node node-id } all
known nodes

clear { object obj~ct-name }
known objects

define circuit circuit-id

define executor

hello timer seconds
receive password password
service {diSable }
enable
state circuit-state {~~ }
transmit password password

c
A-2

Command Summary

define line line-id

controller {IOOPback }
normal
duplex {fUll }
half
ddcmp dmc }
protocol ddcmp point
{
ethernet

name name
state {~~ }

{ known logging
d f"
logging console
logging file
e me
logging monitor

}

events list
known events
[ circuit circuit-id
line line-id
node node-id
[ sink { executor
node node-id

]

define node node-id

address node-address
diagnostic file file
dump file file
hardware address E-address
host node-id
load file file
name node-name
secondary [loader] file
service {diSable }
enable
service circuit circuit-id
[service] password service-password
tertiary [loader] file

C"
'"

defn {Object object-name }
I e
known objects

accept {deferr~d
}
immediate
default user login-name
file file-id
number number
type { sequenced packet
stream

.
i " ""d
[CharacteriStiCS]
list { clrcu t c"rcu"~-,, } status
known circUits
summary

list executor

}

characteristics ]
status
[ summary

Command Summary

A-3

..
[Characteristics ]
list { line l"ne-td } status
known lines
summary

known logging } [CharacteriStiCS ]
logging console
status
[ known sinks
]
IS { logging file
summary
sink node node-id
logging monitor
events

r t

.
[CharacteriStiCS ]
list { node node-td } status
known nodes
summary

r t { object object-name } [CharacteriStiCS 1
IS

known objects

summary

load node node-id

address node-address
from load-file
host node-id
name node-name
physical address E-address
secondary [loader] file
[service] password service-password
tertiary [loader] file
via circuit-id

load via circuit-id

address address
from load-file
host node-id
name node-name
physical address E-address
secondary [loader] file
[service] password service-password
tertiary [loader] file

c
A-4

Command Summary

loop circuit

node node-name
physical address E-address
help
node node-name
full
assistant node node-name
receive
[ { transmit { physical address E-address
} assistant physical address E-address

count count
length length
mixed }
[ with { ones
zeros

c·

count
length
{miXed }
with ones
zeros

loop line line-id

cou nt count
length length
loop executor
{miXed }
[ with ones
zeros

count count
length length
loop { node node-id[acc-con-infol}
. {miXed}
[ with ones
zeros

. .. [reCeiVe password
purge circuit cl,rcul,t-l,d transmit password

purge executor

identification
}
incoming timer
{ outgoing timer

o
Command Summary

A-5

purge

name
events event-list
known events
circuit circuit-id ]
[ line line-id
node node-id
sink { executor
}
[
node node-id

known logging }
logging console
{ logging file
logging monitor

Spurge { node node-id }
known nodes

diagnostic file
dump file
hardware address
host
load file
name
secondary loader
service circuit
service password
tertiary loader

or
purge { node node-id } all
known nodes

purge { object object-name }
known objects

set circuit circuit-id

hello timer seconds
receive password password
state {~~ }

transmit password password

set circuit circuit-id all

c
A-6

Command Summary

address node-address
delay factor number
delay weight number
gateway access { disable
enable
gateway user login-name
Identification id-string
Inactivity timer seconds
incoming proxy { disable
enable
incoming timer seconds
maximum links number
maximum node counters number
name node-name
outgoing proxy { disable
enable
outgoing timer seconds
pipeline quota number
retransmit factor number
segment buffer size number

}

set executor

}

state

{ off
on
h t

}

:e~ricted

set executor all

set executor node node-id[acc-con-info]

set line line-id

controller { loopback }
normal
duplex {fUll }
half
ddcmp dmc }
protocol { ddcmp point
ethernet

or
set line line-id all

name name

state {~~ }

set

known logging }
logging console
{ logging file
logging monitor

events list
known events
circuit circuit-id ]
[ line line-id
node node-id
}]
sink { executor
[
node node-id

Command Summary A-7

set { node node-id}

address node-address
diagnostic file file
dump file file
hardware address E-address
host node-id
load file file
name node-name
secondary [loader] file
service circuit circuit-id
[service] password service-password
tertiary [loader] file

or
set { node node-id } all

set { object obj~ct-name }
known objects

accept {deferre.d
}
immediate
default user login-name
file file-id
number number
type { sequenced packet }
stream

or
set { object Object-name} II
known objects
a

characteristics ]
show { circuit circuit-id} counters
known circuits
[ status
summary

characteristics ]
A

A-8

show executor

[

~~~~~ers
summary

characteristics ]
show { line line-id } counters
known lines
[ status
summary

show

Command Summary

known logg ing } [Characteristics ]
logging console
status
[ known sinks
]
summary
sink node node-id
{ logging file
logging monitor
events

[CharacteriStiCS]
nod e nod e-l,Od
counters
show { active nodes }
status
known nodes
summary

h w { object object-name } [CharacteriStiCS
s 0
known objects
summary

tell node-id [acc-con-info] ncp-command

}
physical address E-address
trigger node node-id { [service] password hex-password
via circuit-id

°
°t°d l
{ physical
address E-address
}
I Cl,rcul,
,.
°
tr "I er v"a
gg
[service] password servwe-password

zero circuit circuit-id [counters]

zero executor [counters]

zero line line-id [countersl

zero { node node-id } [counters]
known nodes

o
Command Summary

A-9

c
Appendix 8

DECnet-Supplied Objects

This appendix lists and defines the DECnet-ULTRIX objects. Table B-1 lists
these objects and gives the following information about them: object number, file
name, default user, socket type, and accept mode.
Table 8-1:

Digital-Supplied DECnet-ULTRIX Objects

Object == tell
Number

File

= /usr /bin/tell

Default user
Accept

=
= Sequenced packet
= Immediate

Object == DEFAULT
Number

Type

File

Default user
Type

=
= Sequenced packet

= Immediate

Object == fal
Number
File

=17

=/usr/etc/fal

Default user

= guest

Type

=Sequenced packet

= Deferred

Object == nml

Number

=19

File

= /usr/etc/nml

Default user

=guest

Type

=Sequenced packet

=Deferred

Object == dterm
Number

=23

File

= /usr / etc/ dtermd

(continued on next page)

DEC net-Supplied Objects

B-1

Table B-1 (Cont.):

Digital-Supplied DECnet-ULTRIX Objects

Default user
Type

=guest

= Immediate

=Stream

Object = mir

Number

=25

File

= /usr/etc/mir

Default user

=guest
=Sequenced packet
=Deferred

Type
Accept
Object

=mallil

Number

=27

File

= /usr/etc/maillldv3

Default user

= daemon

Type

=Sequenced packet

= Deferred

Object = dlogin

Number

=42

File

Type

= /usr / etc/ dlogind
= guest
= Sequenced packet

= Immediate

Default user

Object = dtr

Type

= 63
= /usr/etc/dtr
= guest
= Sequenced packet

=Deferred

Number
File
Default user

Table B-2 describes the services of Digital-supplied DECnet-ULTRIX. objects.
Table B-2:

DECnet-ULTRIX Object Descriptions

DECnet Object

Service

Utility that lets you execute commands on a remote DECnet-ULTRIX
or DECnet-VAX. node.

DEFAULT

You can use the DECnet zero object named to create your own network
server programs without modifying the object database. If the DEC net
object spawner does not find a match for an object in the object
database, it searches for the program by using the path name specified
in the connect request. The path name can be absolute (the full path
name) or relative (the path defined by the user name and password).

INot to be confused with the tell prefix used with ncp commands.

(continued on next page)

B-2

DECnet-Supplied Objects

Table 8-2 (Cont.):
DECnet Object

DECnet-ULTRIX Object Descriptions

Service
Object numbers are equivalent to object names and can be used on
other networks unless the object number is zero. If the object number
is zero, you must use an object name.

fal

Allows a process running on any node in a DECnet network to access
another node's file system. The fal object uses the Data Access Protocol
(DAP) to communicate with other nodes.

nml

The process that performs network management services. The nml
object communicates with other nodes in the network by means of the
NICE protocol.

dterm

A homogeneous command terminal service. The dterm object uses the
TOPS-20 protocol.

mlr

The remote loopback mirror, which performs looping services for remote
users.

mail11
dlogln

The DECnet mail service.

dtr

The DECnet Test Receiver that is used with the DECnet Test Sender
(dtS) to test logical links.

The heterogeneous command terminal service. The dlog in object
uses the CTERM protocol, which supports connections from
DECnet-ULTRIX to all other DECnet nodes.

o
DECnet-Supplied Objects

8-3

c
Appendix C

Ethernet Addressing
A unique Ethernet address identifies each node on an Ethernet line. You can
send a message to any number of nodes on an Ethernet line, depending on the
type of Ethernet address you use, physical or multicast.
To configure your network you need not specify the Ethernet address of a node.
Whenever you execute the ncp set executor state on command, DECnet resets
the Ethernet physical address to correspond to the DECnet node address.

Whenever the DECnet software changes the Ethernet address of your Ethernet
controller, such as during DECnet startup, it invalidates the existing Internet
Ethernet address mapping for the node. The ULTRIX Ethernet driver detects the
change in address in 5 minutes. If you want to delete the mapping entry in the
address translation table manually, use the arp -d command. See the ULTRIX
arp(8) manual page.

C.1

Ethernet Address Format
Ethernet addresses are represented as six pairs of hexadecimal digits separated
by hyphens (for example, AA-OO-03-00-67-FF).

c·

Xerox Corporation assigns a block of addresses to a producer of Ethernet
interfaces upon application. Thus, every manufacturer has a unique set of
addresses to use. Normally, one address out of the assigned block of physical
addresses is permanently associated with each interface (usually in a read-only
memory). This address is known as the Ethernet hardware address of the
interface.
NOTE

You can use the show line line-id characteristics command to display
the hardware address.
Digital's interface to Ethernet (the DEUNA or DEQNA controller at the node)
has the ability to set a different logical address to be used by the interface. This
address is known as the Ethernet physical address. When a node on the Ethernet
initially starts up, the physical address is the same as the Ethernet hardware
address. Then, when DECnet turns on a DEUNA or DEQNA device, DECnet
constructs a physical address by appending the local node's node address to a
constant 8-digit number derived from the block addresses assigned to Digital
(AA-OO-04-00).

Once the Ethernet physical address has been set to its new value, it is reset to
its original hardware address value only when a reset is issued to the DEUNA or
DEQNA (for example, when the machine power is shut off).

Ethernet Addressing

C-1

C.2 Ethernet Multicast Address Types
Ethernet physical addresses and Ethernet multicast addresses are distinguished
by the value of the leading low-order bit of the first byte of the address:

•

Physical address. The unique address of a single node on any Ethernet
(low-order bit = 0).

•

Multicast address. A multidestination address of one or more nodes on a
given Ethernet (low-order bit = 1).

There are two types of multicast addresses:
•

A multicast group address is an address that is assigned to any number of
node groups so that they are all able to receive the same message in a single
transmission by a sending node.

•

A broadcast address is a single multicast group address (specifically,
FF-FF-FF-FF-FF-FF) to which a message can be sent if it must be received
by all nodes on a given Ethernet. (Use a broadcast address only for messages
to be acted upon by all nodes on the Ethernet, since all nodes must process
them.)

C.3 Ethernet Physical and Multicast Address Values
Digital physical addresses are in the range AA-OO-OO-OO-OO-OO through
AA-00-04-FF-FF-FF. Multicast group addresses assigned for use in cross-company
communications are as follows:
Value

.... ~

Meaning

FF-FF-FF-FF-FF-FF

Broadcast

CF-00-00-00-00-00

Loopback assistance

Digital multicast group addresses assigned to be received by other Digital nodes
on the same Ethernet are as follows:
Value

Meaning

AB-00-00-01-00-00

Dumplload assistance

AB-00-00-02-00-00

Remote console

AB-00-00-03-00-00

All Phase IV routers

AB-00-00-04-00-00

All Phase IV end nodes

AB-00-00-05-00-00

Reserved for future use

through

AB-00-04-FF-FF-FF

c
C-2

Ethernet Addressing

c
Index
A

Abbreviating command keywords, 1-3
Access control information, specifying, 2-53

Ethernet. See also Ethernet addresses
Ethernet addresses
and broadcast address, C-2
and hardware address, C-1
and multicast address types, C-2
and multicast group address values, C-2
and physical address, C-1, C-2
and physical address values, C-2
format of, C-1
general description of, C-1
Event messages
for End Communications layer, 4-3
format of, 4-1
for Network Management layer, 4-3
for Routing layer, 4-4
for Session Control layer, 4-3
Events
See also Event messages and Logging
and event classes (table), 4-1
and event message format, 4-1
Executor commands
clear executor, 2-5
clear executor node. 2-6
define executor, 2-13
list executor. 2-27
loop executor, 2-39
purge executor, 2-42
set executor, 2-49
set executor node, 2-53
show executor, 2-63
zero executor, 2-73

8
Bootstrap

trigger node command description for, 2-69
trigger via command description for, 2-71
Broadcast address, C-2

c
Circuit commands

clear circuit, 2-4
list circuit, 2-26
loop circuit, 2-36
purge circuit, 2-41
set circuit, 2-12,2-48
show circuit, 2-62
zero circuit, 2-72
Circuit counters, 5-1
clear circuit command, 2-4
clear executor command, 2-5
clear executor node command, 2-6
clear logging command, 2-7
clear node command, 2-9
clear object command, 2-11
Comment line format, 1-2
Counters
for circuits, 5-1
for lines, 5-4
for nodes, 5-7
general description of, 5-1
summary of, 5-1
to clear. See zero commands, 2-72

define circuit command, 2-12
define executor command, 2-13
define line command, 2-16
define logging command, 2-18
define node command, 2-20
define object command, 2-22
Display commands. See list commands
Display commands. See show commands

H
Hardware address, defined, C-1
help command, 2-24
Help information, 1-3

L
Line commands

define line, 2-16
list line, 2-28
set line, 2-54
show line, 2-64
zero line. 2-74
Line counters, 5-4
list circuit command, 2-26
list executor command, 2-27
list line command, 2-28

Index-1

list logging command, 2~29
list node command, 2-30
list object command, 2-31
Load commands

load node, 2-32
load via, 2-34
load node command, 2-32
load via command, 2-34
Logging
event classes (table), 4-1
event message format, 4-1
information, to display, 2-29,2-65
parameters, to specify, 2-18,2-56
Logging commands
clear logging, 2-7
define logging, 2-18
list logging, 2-29
purge logging, 2-43
set logging, 2-56

show logging, 2~5
loop circuit command, 2-36
lOOp executor command, 2-39
loop node command, 2-40

Object commands (Cont.)
clear object, 2-11
define object, 2-22
list object, 2-31
purge object, 2-47
set object, 2-60
show object, 2-67
Objects,
DEFAULT, B-3

dloglnd, B-3
dtermd, B-3
dtr, B-3
mall11 , B-3
mir, B-3
nml, B-3
nonzero, B-3
zero, B-3

Multicast address types, C-2
Multicast group address values, C-2

Physical address
defined, C-1
values for, C-2
purge circuit command, 2-41
purge executor command, 2-42
purge logging command, 2-43
purge node command, 2-45
purge object command, 2-47

ncp

Remote command execution
of ncp commands, 1-5
of single command (using tell prefix), 2~8
to initiate, 2-53
to return control to local node, 2-6

error messages, 3-1
error reporting, 1-4
general description of, 1-1
help facility, 1-3
how to exit, 1-2
how to invoke, 1-1
remote execution of, 1-5
ncp commands
abbreviating a keyword in, 1-3
and command prompting, 1-4
and comment lines, 1-3
and help command, 1-3
ncp command summary, A-1
Network management command use, 1-2
Node
access control information requirements, 1-5
counters, 5-7
Ethernet address, C-1
Node address for Ethernet, C-1
Node commands
clear node, 2-9
define node, 2-20
list node, 2-30
loop executor, 2-39
loop node, 2-40
purge node, 2-45
set node, 2-58

show node, 2~6
trigger node, 2-69
zero node, 2-75

o
Object commands

Index-2

s
set circuit command, 2-48
set executor command, 2-49
set executor node command, 2-53
use of, 1-5

set line command, 2-54
set logging command, 2-56
set node command, 2-58
set object command, 2-60
Show circuit command, 2-62
show executor command, 2-63
show line command, 2-64
show logging command, 2~5
show node command, 2~6
show object command, 2-67

T
tell command, 2-68
trigger node command, 2-69
trigger via command, 2-71

z
zero circuit command, 2-72
zero executor command, 2-73
zero line command, 2-74
zero node command, 2-75

HOW TO ORDER ADDITIONAL DOCUMENTATION

IDIRECT TELEPHONE ORDERS I
In Continental USA
call 800-DIGITAL

In Canada
call 800-267-6215

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

In Puerto Rico
call 809-754-7575

IELECTRONIC ORDERS (U.S. ONLY) I

DiaI800-DEC-DEMO with any VT100 or VT200
compatible terminal and a 1200 baud modem.
If you need assistance, call1-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 K1 G 4C2
Attn: A&SG Business Manager

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

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

r~~

'"''-,,,'/

c
DECnet-ULTRIX
NCP Command Reference
AA-PB62A-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:
Accuracy
Readability
Examples
Organization
Completeness

Poor
1
1
1
1
1

2
2
2
2
2

3
3
3
3
3

Excellent
4
5
4
5
4
5
4
5
4
5

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

General comments:

Suggestions for improvement:

Name
litle
Company

City

Date
Department
Street
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
Communications Publications
550 King Street
Littleton, MA 01460-1289
DO NOT CUT - FOLD HERE

(/,

~--j