Digital PDFs

AA-X437A-TK

December 1983

254 pages

Original

52MB

view download

OCR Version

15MB

view download

Document:	DECnet Digital Network Architecture Phase IV Network Management Functional Specification
Order Number:	AA-X437A-TK
Revision:	0
Pages:	254
Original Filename:

OCR Text

DECnet Digital Network Architecture
Phase IV

Network Management Functional Specification
Order No. AA-X437A-TK

December 1983

This document describes the functions, structures, protocols, algorithms, and operation of the Digital Network Architecture Network Man-

agement modules. It is a model for DECnet implementations of Network
Management software. Network Management provides control and ob-

servation of DECnet network functions to users and programs.

SUPERSESSION/UPDATE INFORMATION: This is a new manual.

VERSION:

4.0.0

To order additional copies of this document, contact your local

Digital Equipment Corporation Sales Office.

digital equipment corporation - maynard, massachusetts

First Printing, December 1983

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 Corporation 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.

- The postage-prepaid READER’S COMMENTS form on the last page of this document requests the user’s
critical evaluation to assist us in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS

COMTEX
DDT

DECCOMM

ASSIST-11
VAX
- DECnet

DATATRIEVE

.
|

DECsystem-10
DECtape
DIBOL
EDUSYSTEM
FLIP CHIP
|
FOCAL

MASSBUS
OMNIBUS
0S/8
PHA
RSTS
RSX

LAB-8

TYPESET-11

INDAC

DECSYSTEM-20
RTS-8
VMS
IAS

TYPESET-8

TMS-11

ITPS-10
SBI
PDT

TRAX

Distributed ‘Systems Publications typeset this manual using DIGITAL’s
TMS-11 Text Management System.

MGTPEALL

Page

~Table
of Contents

and DNA
Protocols

and

Interfaces

for

Implementatlons

Networks
N LNN

. .
DECnet

Requirements

Documents

Relationship to DIGITAL Network Archltecture
Network Management Model of DNA from the User
PerspectlvVe
.« o« « o o o o o o s oo o o o
Nodes

OV
W N

®
[]

DESCRIPTION
Scope

Design

W N+

[

]
[]
[]
|]

B wWwWwwww

Intended Audience
. .
.
Network Management Archltecture,

FIUNCTIONAL

[]

8N DO NN

>
W

INTRODUCTION

CONTENTS

Areas

Logging
Circuits

. . . .
and Llnes

Modules

N=TWORK MANAGEMENT AS
Nodes
.
.

o
s

Node

in the DNA

Parameters

NI e

(NI

Logging

Circuilts
Circuilt

35
36
37
38
38
39
40
48
49

.
.

Circuit Counters
Lines
.
Line Parameters
Line Counters

49
54

and Line State

=N+

High Level Link User
Data Link States

and Substate Model

56
58
60

States

Network Management Data L1nk Serv1ce States
Controllable and Observable States and

63
65
65

Substates
Modules
.

X.25 Access Module
X.25 Protocol Module . .
X.25 Server Module . . .
Link Maintenance Modules

Events

«
.

o
.

e
.
«

Events Not Relateo to an Entlty

66
72

o«

Circult Events
Line Events
.

.
¢«

.
¢

¢
¢

o«
o

¢
o

o
o

Module

&«

o«

«
o«

o«

Event

Events

Parameters

Node

Node Counters
Areas
|
Logging
.

Circuit

SEEN BY THE USER

Source Quallflers

=W+

OO
U U E
R WWWN

Model of Network Management Components

g W+

WOoOOOODDODOOOMOWOMNIIdIJ

[]

]

[]

]

wawwwwwwwwwwwwwwwww

[]
]
®
®
[]
®

Layers

WWWWLWWWWLWWWLWWWW

o
o

80
81
81

OOl

.««

.
.
o
¢
¢«

.
.
«
¢
¢

«
.
«
«
«

¢
«
o«
«
¢«

«
«
o
o
«

«
«
o«
o«
@«

«
«
o«
o«
«

«
«
o«
«
«

«
«
«
o«
«

«
.
«
«
«

.
.
.
o
.

82
83

c«

+«

WO WWOWONOUTOTO
D DD
WN
=

(NCP)

Program

Functlons

NS OYOr
e W

.
.
«
«
«
.

«
.
«
«
«
.

¢«
.
o«
o
¢«
.

Control Program Operatlon
Specifying the Executor
. . . .
Program Invocation, Termination,
Privileged Commands
. « « +« « ¢

Input

5
6

Output

H OO
WN -

Network

.1
.2

.3
.4

.1
.2
0
1

SET

. .
« .
.
Prompting

91
91

o«

DEFINE

Characterlstlcs

and

.
.«
and

Status and Error Messages
.
«
Network Control Program Commands
Commands

«
.

o
.

94
96

.«

CLEAR and PURGE Commands

104

TRIGGER

108

LOAD

CommandsS

.«

o«

109

DUMP

Commands

.«

¢«

&«

o«

110

CommandsS

LOOP

Commands

SHOW QUEUE Command s
SHOW and LIST Commands .
.
.
«
¢
«
o«
o«
o
«
ZERO Commands
. .+
+
&
o
v
@«
&
o
o
o«
o«
«
«

I 2
112
118

EXIT

119

.
.
.
.
.
..

120
120
121
122

I
.
.
.
¢& o
.+
.
.
. « + « « « « . .
. . . . . . . « . .
. . . . « « . « . .

123
124
125
126

Command

.+«

MANAGEMENT OPERATION .
.
.
.
NICE Access Routines and Listener
Local Network Management Functions
Link Watcher . . .
e e
e

¢«

.
.
e

«
.
.
e

.
.
e

NETWORK

Data Link Service Functlons
States and Substates .
.
.
Priority Control . . . . .
Link State Algorithms
. .
Link Handling Functions
.
Logger

Event

Logger

Components

o«

Event

Formats

84
85
87

« « &« « « « « o
889
. . .. . . . . 859
o
o«
«
«
«
«« «
90
« « o« « « « « «
90
«
« « «
«
«
«
«
90
. . . . . . . .
90
B|

1
2
3

Control

Changing Parameters
. .
Gathering Information
.+
Down-1line LoadlnNg
.
.«
¢«
Up—-line DUMPING
. & « «
Triggering Bootstrap . «
Testing Link and Network
Zeroing Counters . .
.

Layer

Network

WWWWWWWWWWWRNNNNMNNN

ST S
Y
S
Y ST S
Y
Y
Y
Y
S
Y
S
Y
Y
S
YS
Y
S
S
Y
S
TS

Management

Page

Session Control Layer
.
End Communication Layer
Routing Layer
. .« + « v
Data Link Layer
. . ¢ ¢«
Physical Link Layer
. .

NETWORK CONTROL PROGRAM

e
S 1 N
NS N6 N
ES I N NG KS 1 NS N

Network

W+

WO WOWWOW

Contents

Wwwwww

IR IR NG NG IES NN

Table

.
.

Suggested Formats for Logging Data
Down-line Load Operation . . . .
e
Up-line Dump Operation . . . . ¢« ¢« «
Trigger Bootstrap Operation
. . . .
Loop Test Operation
. . . v o « «
o
Node Level Testing . . + ¢« v ¢ o« «
Data Link Testing
. .
e« e e e e+
Change Parameter Operatlon e« + o+ e« o
Read Information Operation .
. .
.
.

129

e o«
o« o
« «
« «
o
o
o« «
o e
o
&
.
.

o«
o
«
.
o«
«
o
o
.

o«
«
.
.
«
«
o
&
.

.
o
.
.
«
«
«
o
.

.
o
.
.
o«
o
o
o
.

132
133
138
139
140
140
149
152
154

Table

Contents

)

5.12

5.13
5.14
5.15
5.16

~Zero Counters Operation

.
&«

.
«

Trigger Bootstrap Message Format
Test Message Format
.
.
.
e«
Change Parameter Message Format
Read Information Message Format
—ero Counters Message Format .
«

6.11
6.12

NICE Response Message
NICE Connect Initiate

6.13
6.14
6.14.1
6.14.2

Event Message Blnary Data Format
Logical Loopback Message Formats
Connect Accept Data Format .
«
Command Message Format . .
.«
«

6.10

.
«
«
.
«

NICE System Specific Message Format

Response

.
s+
+
.
«

Format

.«

Introduction

Numbers

OO e W+

.10
.11
.12

o
e

B
o

&
e

B
e
e

e
e

«
«
«
+

«
«
«
«

.
«
«
.

.
«
o
.

159
159
160
161

163

.
+
+
.
«

.
«
«
.
«

.
o
<«
.
«

.
«
«
.
«

.
o
.«
.
.

.
o
.
.
.

164
165
166
167
168

169

. . . . . . 168
«

170

«
.
«
o«

.
.
o
o«

170
172
172
172

172

¢«

Data

@«

Binary

Format

Descriptions

. 173
.

173

e«

e« o«

173

«
¢«
«
o
«

e
«
o
o«
e«

e
«
«
e«
«

e
«
«
«
«

o«
.
«
o«
o«

o
o
.
o
«

173
174
174
175
175

176
176

and Descrlptlve
. . . « ¢« .+ « .

Information Types
. .
Applicability Restrlctlons
Setability Restrictions
.
Circult ParametersS . .« « +« «
Circult CoUNtersS .+« v v & o« o
Line ParameterS
. « « « o «

e e & e« 4 4 . « .
T
. « « « ¢« « « « « o
« « « « « o« « « « o
o o o« o o o o« « o« o
oo o o o s « « « o

179
S
179
180
183
185

Line Counters
. « «
o « o o
Logging Parameters . . .
.+« «
Module Parameters
.
.
e
Console Module Parameters
Loader Module Parameters .
Looper Module Parameters .

o
¢«
e
e
.
.

Encoding

154
155
157
157

<«
.
«
«

Numeric Range
. .
Parameter Display Format

154

.
o«
o«
.

«
.
«
«

7.1.7
7.1.8

«
.«
o«
«

e«

Entity Parameter Identlfler Format
String Identifier Format . . « ¢««
Node Identifier Formats . « ¢« « «
Area Identifier Format . . .
e e
Object Format for Entity Types e« «

«
«
e«
«

e«

7.1.2
7.1.3
7.1.4
7.1.5
7.1.6

««
« +
e «
« «

e« + e
. .. .
¢«
«
¢« «
«
¢«
¢«
o

Type

.
«

Format . . . .
and Connect Accept

Message

.
o«

7.1.1

PARPAMETER AND COUNTER BINARY FORMATS AND VALUES

7.1

Format

6.5
6.6
6.7
6.8
6.9

ONNSNNN
NNV O PN
- -

Request Up-line Dump Message Format

}
y

6.4

6.14.3

)

NETWORK MANAGEMENT MESSAGES
. .
NICE Function Codes
. « ¢ ¢ «
Message Format Notation
. .
Request Down-line Load Message

Formats

Loopback Mirror Operation
. . . « ¢«« «
NICE Logical Link Handling . . .
Algorithm for Acceptlng Version Numbers
Return Code Handling. . . + «v ¢ & v « &

6
6.1
6.2
6.3

Page

Notation

NICE Returns

se e

o
¢«
e
e
«
.

o
¢
o
o
«
¢«

o
«
o
s
«
«

o
«
e
o
«
¢«

Configurator Module Parameters

Access Module Parameters
.
Protocol Module Parameters
Server Module Parameters
.
Counters
.
v
v
¢
¢ o o o o

.
.
.
o

X.25
X.25
X.25
Module

|
«

176

o
«
o
e«
«
¢«

«
«
e
e
«
«

o«
«
«
o
«
«

o«
.
«
«
«
«

o«
.
o
o
o

187
1889
191
191
191
192

192

.
.
.
o

.
.
.«
o

.
.
«
o

.
.
«
«

.
.
.
«

194
194
196
197

Contents

Page
6

X.25

Protocol

X.25

Server

Node

Parameters

Node

Counters

rea

>
N

Parameters

Event

Definitions

Event

Parameters

197

o«

197

o«

201
202

202

205

Versions 2.0 and
Module Entity
Node Entity
.
Logging Entity

3.0 . .
.
.
+
.
.
.
.
.
.
.
¢«
¢«
¢
¢
v
v
v
.
.
.
e
C-rcuilt and Line Entltles
c
Event Logging
.
.
.«
«
«
¢
«
Versions 3.0 and R

APPENDIX

MINIMUM SUBSET

APPENDIX

STATE

APPENDIX

X.25

APPENDIX

MEMORY

APPENDIX

- NICE

RETURN

CODES

WITH

APPENDIX

NCP

COMMAND

STATUS

AND

MAPPING

NATIVE

IMAGE

o
e

e
«

e«
o«

o
.

.
.
.

TABLES

ONLY

SUBSET

FORMATS

APPENDIX H

JULIAN

APPENDIX
1

DMC DEVICE COUNTERS

APPENDIX

GLOSSARY

Counters

VERSION COMPATIBILITY

APPENDIX

Module

HALF-DAY

AND

FILE

CONTENTS

EXPLANATIONS

ERROR

ALGORITHMS

MESSAGES

RN
NN

>C>3’TCV3’>

Table

Introduction

1.1

Page

INTRODUCTION

Intended Audience

This document

Management

is written primarily

on DECnet systems.

for

However,

those

who

1mplement

it may also be of

Network

interest to

anyone ‘who wants
to
know
the
details
of
the
Network Management
structure.
Knowledge
of communications software technology, DECnet,
and X.25 is prerequisite to understanding this document.

Sections

1-4

- perspective.

1.2

describe

Network

Management

mainly

from

Sections
5-7 describe Network Management

the

internals.

user

Network Managem=nt Architecture, DECnet Networks, and DNA

This document
describes
the
structure,
functions,
operation,
and
protocols
of Network Management.
Network Management models software
that enables operators and programs to plan, control, and maintailn the

operation

centralized

distributed DECnet networks.

Networks

consist of software modules, data bases, and hardware components
that
connect
computing
systems
for
resource
sharing,
distributed
computation, or remote system communication.
DECnet networks connect
DIGITAL
computing
systems
together, and also connect to public data
networks with X.25

circuits.

Network Management is part of the DIGITAL Network Architecture
(DNA).
DNA
1s the model on which DECnet network software implementations are
based.

1.3

Protocols and Interfaces

DNA is a layered structure.

functions.

Modules

within

Modules

the

in each
layer
perform
distinct
same
layer
(either in the same or

different nodes) communicate using specific protocols.
The
protocols
specified
in
this
document
are the Network Information and Control
Exchange (NICE) protocol, the Loopback Mirror protocol, and the
Event
Receilver

protocol.

Modules in different layers interface
using
subroutine
<calls
or
a
similar
system-dependent
method.
This
document
describes Network
Management's interface to each layer by describing
elements
1in
each
layer that Network Management controls or examines.

1.4

Requirements

for

Implementations

This document describes user commands that can be standardized
across
different
DECnet
implementations.
An implementation may use only a
subset of the commands described herein.
(Appendix
B
describes
the
minimum
subset
of
Network
Management
functions
required
for

Introduction

Page

certification.)
Moreover, commands
and
functions
specific
particular operating system are not described herein.

one

This document uses both algorithms and English descriptions to explain
the
Network
Management functions.
An implementation is not required
to follow these algorithms exactly, as long as the
functions
operate
as described.
|

1.5

Documents

This

is one of

a series of

Network
Architecture,
specifications are:

functional

Phase

DNA Data Access Protocol
5.6.0,

DNA

Order

No.

1IV.

specifications
The

(DAP)

other
|

Functlonal

DIGITAL

functional

Version

Digital
Data
Communications
Message
Protocol
(DDCMP)
Functional Specification, Version 4.1.0, Order No. AA-K175A-TK
Specification,

DNA Ethernet
Noce
Product
Architecture
1.0.0, Order No. AA-X440A-TK

Maintenance
3.0.0,

Order

Operations
No.

Functional

No.

1.0.0,

Version

Specification,

Version

AA-X436A-TK

DNA Routing Layer Functional
No. AAX435A TK

DNA Session Control

Version

Specification,

DNA Network Services Protocol
Functional
4.0.0, Order No. AA-X439A-TK

The

the
DNA

Specification,

AA-K177A-TK

DNA Ethernet Data Link Functional
Order No. AA-Y298A-TK

DNA

for

current

Specification,

SpeC1f1cat10n

Functional

Version

Specification,

Version

Version
|

2.0.0,

Order

1.0.0, Order

AA-K182A-TK

Ethernet - A

_Local

Area

Layer

Specifications,

Xerox),

Order

No.

Network- Data

Link

Version

(

2.0,

Layer

and

Digital,

Physical

Intel,

and

AA-K759B-TK

The DECnet DIGITAL Network Architecture (Phase IV) General Description
(Order

No.

AA-N149A-TC)

architecture
and
specifications.

provides

1introduction
-

overview

each

the

network

functional

FUNCTIONAL

Page 9

Functional Description
DESCRIPTION

and
control
to
and programs
operators
Network Management enables
a
of
manager
the
helps
network operation. Network Management
monitor
facilitates
also
Network Management
network to plan its evolution.
1mpede
that
conditions
and resolution of
isolation,
detection,
effective

network use.

user

Network Management provides

commands

capability

and

programs for performing the following control functions:

can

A system in one node

wuser

down-line

Loading remote sYstems.

the
change
can
system manager
A
Configuring resources.
patterns.
traffic
message
modify
network conf-guration and

Setting parameters.

4.,

load a system in another node

Circuit,

(for example,

parameters

in the same network.

line, module, node, and logging

node names)

can be set and changed.

A system
functions.
network
terminating
Initiating and
off and
or
on
network
the
turn
can
operator
or
manager
functions.
other
and
tests
perform loopktack

Network Management also enables the user to monitor network functions,
TM

)

configurations,

and s:-ates,

follows:

Dumplng remote systems.

A systém in

dump a system to another node

one

node

can

in the same network.

up-line

and
Information about lines
Examining corfiguration status.
display
can
operator
an
example,
For
obtained.
be
can
nodes
of lines and nodes or the names of adjacent nodes.
the states

Examining

An operator can
Examining the status of network operations.
the operator can
example,
For
operations.
network
monitor
any have
whether
and
progress
in
are
operations
what
out
find

settings,

parameters,

line type,

Parameters

or node names)

(for

timer

failed.

5. Examining

example,

can be read.

performance

varilables.

system

manager

can

lower DNA layers to
in
counters
of
contents
the
examine
Network
addition,
In
performance.
network
measure
logging of
automatic
Logger provides
Management's Event
significant

network

events.

Besides controlling and monitoring the day-to-day operation of the
the functions 1listed above work to collect information for
network,
operations
basic
furnish
functions
These
planning.
future

(primitives) for detecting failures, isolating problems, and repairing

and restoring a network.,

Functional

2.1

Description

Design

Common

functions

satisfy

the

and

Common

programs,

the

compatibility of

Subsetability.

Nodes

and

memory

for

not

conflict

with

line

leaving

Network

user

effects
errors,

Security.
mechanisms

Network

the

control

Management

Network

Management

both

efficient

earlier

processing

where

this

does

of errors
such
as
and hardware errors

the

a basis

for

programs.

across

lines,

mixture

topologies,

Network Management

supports

additional

functions

operates

communication

Management

the

programmer.

network management

and

software.

operator
input
are minimized.

existing

security

DIGITAL Network Architecture (for example,
mechanism of the Session Control Layer).

Simplicity.
Complex algorithms
Functions
provided
elsewhere
duplicated.
|
|

subset

specification serves

versions

The

goals.

types,

protocol

access

This

Network

different

errors,

operator

sophisticated

node

heterogeneous

There is accommodation for future,

subset.

Robustness.

10.

support

Network Management 1is

functions,

network

among

the

other

topology

functions.

efficient.

Heterogeneity.

across

Invoking and understanding

building more

able

provided

network

system between network

easy

are

Extensibility.

functions

compatible

design

without
impacting
the
is a compromise between

Ease of use.

management

are

components

are

commands

compatibility within
system commands.

Network efficiency.

network

systems and the
and other local

Management

following

1interfaces

regardless

configuration. as much
as
possible
quality
of existing products. There

interfaces.

operators

Page

Scope

Network
Management
requlirements:
l.

Support

diverse management

covers

range

Dbetween

and data
1in
the

policies.

completely

bases
are
avoided.
architecture are not

Network
centralized

Management
and

fully

distributed management.

11.

Integrated abstractions.

Diverse

low level policies,

different
Data
Link
protocols, are combined where
into consistent higher level abstractions.
The

following

Management:

are

not

within

the

scope

this

version

such as
possible

Network

)

Functional

Description

Page

Accounting.
This specification
does
not
provide
for
the
recording
of
wusage data that would be used to keep track of
individual accounts for purposes of reporting on or
charging
users.

Automation.
This
specification
does
not
provide
for
automatic execution of complex algorithms that handle network
repair or reconfiguration.
More automation can
be
expected
‘in future revisions of this specification.

Protection agalinst malicious

protection
Oor

use.

against malicious

There

use Or

1s no

gross

errors

foolproof

by operators

programs.

Upward compatioility of user

interfaces.

The

1interfaces

the
User Layer are not necessarily frozen with this version.
Observable data may change with the
next
version.
Version
4.0

1is

compatible

with

Version

3.0

except

for

the

changes

necessary to distinguish network areas, while Version 3.0
1is
compatible
with
Version
2.0
except
for
those
changes
necessitated by

the

integration of

X.25

Network

Management

functions, the DMP device, and multipoint software functions.
(See Appendix A.) Compatibility with versions before
Version

2.0

;> 2.2

not

supvoorted.

Relationship
to DIGITAL Network Architecture

DIGITAL Network
Architacture
(DNA),
the
model
wupon
which
DECnet
implementations
are
based,
outlines several functional layers, each
with its own specific software components, protocols,
and
1interfaces

the

adjacent
three

layers.

highest

Network Management software components reside

layers.

The general design of DNA is as follows in order from the
the

lowest

layer:

The User Layer.
supports

Program
2.

user

(NCP)

The User Layer is

‘services

resides

The Network Management

and

in this
Layer.

the

programs.

highest

layer.

The Network

1in

highest

1layer.

The Network Control

Management

is
the
only
one that has direct access to each lower
for control purposes.
Software
components
in
this

Layer

layer
layer

provide
user control over, and access to, network parameters
and counters as well as up-line dumping,
down-line
loading,
and testing

functions.

The Network Application Layer.

Software

components

the

Network
Application Layer support I/0 device and file access
functions.
The Network Management software component 1in this
layer is the Loopback Mirror, providing logical link loopback
testing.

- Functional Déscription
4,

Control Layer.
The
system-dependent aspects of

Session Control

the

logical

controls
the
logical links,

route

source

The Data
Link
communications
protocol,
for

The

Layer.
over -a
example,
Protoccl (DDCMP)

Physical

L:nk

Layer.

and

1
DNA

shows

the

layers.

Layer manages
communication.

Communication

Layer

relationship of

in the. Routing

destination

Layer

nodes.

The
Data
Link
Layer
manages
the
physical
1link,
wusing
a
data link
the
Digital
Data
Communications
or the X.25 Protocol.
The

Physical

the
hardware interfaces (such as
to specific system devices.
Figure

End

Software components

messages between

Message

The

link

Page 12

<creation,
maintenance,
and
destruction
using the Network Services Protocol.

The Routing Layer.

other

The Session

The End Communication Layer.

the

Link

Layer

EIA RS-232-C or

Network Management

provides

CCITT V.24)

Layer
|

the

Functional Description

—

Network

:---->
|

T !
|

———

e e

!
t———=>
|

——

e e

——

—

e e e

wwan

—

om—

——

—— — —— — —— —

Management

Page 13

— —— — —— — ——————— —— —

Modules

gy
Sy
Uy U
UL SRUEp Ry '

Network Application Modules

ee
—

—

e. !
1
Session Control Modules
P!

!
!

{

!
————————————— >

!
!

e
b e
! End Communication Modules !

Y e~ '

!
!
!

!
Y
e bbb .
| Rouzing Modules
!

5
!
!

!
!
!

e
— — — !

P
!

!
\Y

!
Vv

ilil >

{

———— e

tm———
L

e ———_———————
- - .

Data Link Modules

e e e e
——
'

!
!

!
\Y

aia it >

bbb

e bt .

Physical Link Modules

Y Y Y '

Figure

Network Management Relation to DNA

Functional

Network

Description

Management

contains

simplified

two

network

management- use.

of
2.

DNA

The

(Section

model

for

Network

Because

one

ease

of
presented

models:

model

This

that

model

2.3).

1is

Management
of

Network

Model

the primarv

wuse,

the

with

Management

goals

person

who

different,

user

entity

view

part

DNA

from

the

User

DNA

(Section

Perspective

the

Network

Management

design

the

Network

Management

software

complicated

the

view

the

network

is addressed at
user program.

network mainly

two

entering

1is

than

levels:

commands

entity-option

verb

1s an English verb such as SET, CLEAR, SHOW, LOAD,
or
LOOP.
entity is one of five classes of controllable network elements:

Node - Each node
system

with

further

Area

areas

in a network represents a distinct operating

associated
described in the

CPU
and
peripherals.
section entitled Nodes.

An area is a group of nodes.
Nodes
for hierarchical routing purposes.

are

Nodes

are

grouped

1into

3..

- Loggin
1is
g
the
mechanism
that
keeps
track
automatically
of important aspects
of the network operation.
Logging is further explained in Section 2.3.3.

Circuits - Circuits
described in Section

Logging

are

logical

communications

2.3.4.

paths

Lines Section

Modules - Modules are any entity that does not fit
into
the
above
<classifications
but
represents
a
distinct function
and/or database.
For
the
present, all
the
modules
are
related to either X.25 or maintenance functions.

Note

that
"element"

The

network

less

manages

for

simplified

uses

form:

verb
The
The

interactive
the

sense

that
of the entire DNA model.
This model
the interactive user at a terminal and the
The

intended

2.4).

2.3

Page 14

user

entities.

Lines are
2.3.4.

physical

communications

in
particular
implementations,
may be used in place of "entity".

can

observe,

The

and,

some

cases,

entity-option qualifies

the

control

the

paths

word

described

"component"

various

aspect

the

aspects

entity

upon

Functional Description

Page

which the verb is to act.
For each entity, DNA
specifies
associated
parameters.
For some entities
DNA also specifies counters and events.
The parameters and counters are information kept in data bases.
Data bases are of two types:
volatile and
permanent.
The
volatile
data Dbase
describes
the
running network.
If the system crashes
or
shuts down, the volatile data base disappears.
The
permanent
data
base
specifies
the
1initial
content
of
the
volatile
data
base.
Counters are only kept in the volatile data base.
Events are not kept
event

1n any data base.

Events

logging mechanism as they occur.

are

captured

the

Parameters are values 1in a data
Dbase
1indicating characteristics
status of an entity. For =xample, some of the node parameters are:
NODE

STATE

NODE

NAME

NODE

ADDRESS

Some parameters can be changed or set.

Of these, some can be

to a default value or to no operation.

Counters are variables kept
counters

1in

Bytes

Examples

circuit

zeroed

sent

Counters can only be read,

zeroed,

Events are occurrences in the
events.

memory.

cleared

are:

Seconds since last
- Bytes received

event

main

Parameters can be read.

logging

or read and zeroed.

network

that

mechanism keeps track of.

Examples of

logging events are:

the

Network

Management

Only the logging entity has

Invalid message
Verification reject
"Line counters zeroed
Node reachability change

"The user cannot directly

wuser

can,

The user program interface uses specified messages
to

pass

control

aspects of

types of

2.3.1

the

control

logging of

requests as the

events.

The

interactive user can make.

however,

the

same

Nodes

Nodes are the major controllable entity of the network.

They are

the

addressable objects of the Routing algorithms.
From the standpoint of
Network Management, there are
two
major
<classifications of
nodes:
executor
and
remote.
The executor is the node actually executing a

Functional

Description

Network Management

function.

executor
are

remote.

document

described

Note

are

that

from

the

this

access

Network

All

Netwerk

from

the

node.

user

some

are

target

nodes

point

user,

set

his

terminal

functions

"remote"

also

node

referred

the

wusually

functions

Management

contexts,

vantage
of

nodes

and

This

should

"physically" local node
Network Management.

other

concepts

point
of view

1local

However,

Page

the

relation

the

described

this

executor

node.

terminal

also
as

the

the
|

loop,

node

are

looped

The

routed

command
some

A host

out

the

line

with

the

node
function

remote

node

node.

node

line

test

example,

host,

can

Jjust

use

target;

node

that

provides

some

entity

Communication,

area

or generate

service,

a dump.

operatior,

functions

down-line

system

host,

that

name

links

they

1is
to

will

1level
executor

Network
itself

such

file

can

load

loop back

distributed

can

wuse

among

different

low

nodes.

command,

and target nodes.
Alternatively, the
down-line
load
the executor and target nodes; or executor, command and

executor,

events

2.3.2

message,

any particular

and

his

view

executor,

‘The

then

This
logical

expectation

A target node 1s the node that is to receive a load,

For

command,

1is
the
node
requesting a
high
from the executor.
It can be the

system.

level

node.

terminal

back.

Management
or

wusing

nodes.

node 1s a special name for the
executor
node.
associated
with
one of tte executor's circuits, and

1is

node,

point

Loop
~that

executor

virtual

another

from

host,

and

target.

associated with

from

the

Network

and

Routing

layers

functions,
Management,

the

parameters,
Session

general

counters,

Control,

End

DNA model.

Areas

group

nodes.

The

Network

Manager

groups

nodes

into

areas
for
hierarchical
routing
purposes.
The
wuse
of areas 1n a
network allows node identification within an area to be independent of
node
1dentification
within
other
areas.
Each
area
1s
wuniquely
identified.
The
addition
of
an
area
1identification
to
a
node
identification
wuniquely
identifies a node within the network.
Nodes
in a single area network will, by convention, have
the
default
area
number
"1",
which will not be displayed, thus hiding the unnecessary

addressing

hierarchy

from

the

Network Manager.

Functional

2.3.3

Description

Page

Logging

Logging
1s
the
automatic
event
recording mechanism
of
Network
Management.
A logged even: 1s directed to a sink node for output.
A
sink may be a system console, a file, or a monitor program.
The
node
at which the event occurs is the source node.
The system manager must
use Network Management commands to tell the source node what kinds
of
events
are to be logged and to what kinds of sinks.
The sinks can be
located at one or more nodes.
These nodes are the destination
nodes.
The
Network
Management
software
at each destination node knows the

actual

name

and

state

Some examples of
LOGGING

1ts

resident

sinks.

logging entity-options are:

STATE

LOGGING

SINK. NODE

LOGGING

EVENTS

Logging sink functions and parameters,
of

event

2.3.4

data,

are

Circuits

completely within

and

other than the actual

the

Network Management

«creation
layer.

Lines

The circult and line entities are
of the close coupling of the Data

presented together as
Link and Physical Link

a
reflection
layers.

)/f

A circuilt i1s a
high
1level
communications
path.
Circuits
provide
logical communication between protocol handling modules.
They are the
communications paths that are visible, for example, to Routing and the
X.25
Gateway
server.
A
circult
may
be a permanent or switchable
connection.
Unknown to its high level
wuser,
a
<circuit
may
be
1in
one-to-one
correspondence
to
a physical link, multiplexed with many
other circuits, and/or traffic split
over
multiple
physical
1links.

Some
characteristics
of
<circuits
can
affect the way that they are
used, so in many cases the higher level can or must be aware of
these
differences.
In
other
words,
the
1line
to
circuit
mapping
1S
invisible, but other characteristics may not be.
|
A line 1is a low
communications.

There are
Ethernet.

level
They

communications
path.
Lines
provide
physical
are the media over which circuits operate.

currently three major
DDCMP
circuilts

multipoint

control,

subdivided
subdivided

into
permanent
and
switched,
into incoming and outgoing.
X.25

with
switched
further
<circuit
parameters
are

1level

line

from

X.25

level

the

and

classes of circuits -- DDCMP, X.25 and
are
subdivided
1into
point-to-point,

multipoint

the

frame

packet

DDCMP,

level.

X.25

<circuits

parameters

are

from

level.

DDCMP p01nt to- p01nt circuits
the circuit and the line.
For

tributary.

each multipoint

have

tributary

one-to-one

correspondence

separate

circuit,

and

between

all

Functional

the

Description

tributaries

1in

group use the same

line.

The

Page

line must be of

protocol type DDCMP CONTROL.
In other words, at the master end, there
ls
one DDCMP
control
line.
It
1s
associated
with
one or more
circuits, each of which has its own physical
tributary
address.
At

the

slave

DDCMP

end,

tributary

there

a one-to-one correspondence of

circuit

and a

line.

X.25 circuits differ from DDCMP circuits in that there
1is
no
direct
correspondence
between
cirzuit
and
line.
All
X.25 circuits pass
through the
X.25
protocol
handler
module.
Lines
belong to
the
protocol
handler
module, and it is responsible for establishment and
maintenance

the

circuits

zthat

use them.

X.25 permanent circuits are very similar to
DDCMP
both
have
predefined end points that are assumed
circuit.

X.25

switched circuits can only be

of
a
higher
no

individually named

higher level user, such as Routing.
level user parameters or counters.

individual

existence

that

circuits
1in
that
i1n the usage of the

visible

the

This provides a
For other users,

context

handle for
they
have

to Network Management.

Ethernet circuits are rather different from the other
types
1n
that
there
1s
not
a
single node
at
the
other end.
Rather, Ethernet
circuits are distinquished from one another according
to
the
higher
level
wuser's
protocol.
An Ethernet circuit 1s a path to many nodes
and the
visibility
of
these nodes
to
Network
Management
varies
according to the higher level user.

Use of an Ethernet circuit requires a
station
1identification.
This
station
1identification
1s an Ethernet address.
The address that the
station is currently using
1is
called
the ©physical
address.
Some
stations
will
also
respond
to
a
group
1identification
<called a
multicast address.
Some stations also have an address, or
addresses,
built
1into
their
hardware.
This hardware address may sometimes
be
used as the physical address.
DNA currently
requires
that
stations
cabable
o0of
anything other than maintenance operations use a physical
address that 1s
1s found in the

a function of the
DNA Ethernet Node

DNA node address.
Thls
requirement
Product Architecture Specification.

Circuit functions, parameters,
counters,
and
events
are
from
the
Network
Management,
Routing,
Data
Link,
and Physical Link layers.
Line functions, parameters, counters, and events are from the
Network
Management, Data Link, and Physical Link layers.

2.3.5

Modules

Modules currently comprise the access routines,
handler

The X.25

for

X.25,

access

and Network Management

routine

module

connect
the
program
wusing
desired public data network.

contains

the
This

server

maintenance

the

data

and

protocol

handlers.

base

needed

access routines to a server
data base is organized
by

for the
network

Functional Description

Page 19

1identification.
The

X.25 server module
incoming
X.25 call to
data base is organized
module

also

keeps

contains

the
data
base
needed
to
map
an
DECret process and form the connection.
This
by
destination
identification.
The
server

one

set

resourdes.
The

X.25

multiplex

protocol

lines.

module

name.

each

The

1ts

Network

links

them by

counters

relative

its

internal

protocol

local

DTE

the

X.25

from X.25

level

common

data

circuits

the

base

over

needed

1its

line

packet

level.

handler

module

also

keeps

counters

relative

addr=ssses.

Management

maintenance

modules

are

responsible

for

functions
on circuits and/or lines.
They have
for handling maintenance for all DDCMP and X.25

and specific
the

contains

permanent

1is organized by one or more local DTE (Data Terminal
X.25 equivalent of a node) addresses.
The
protocol
contains
an
X.25
wuser group data base organized by

handling
maintenance
implied responsibility

data

mocule

and

These parameters are

handler

switched

This
data
base
Equipment -- the
group

network

responsibility

manager.

The

for Ethernet

maintenance

circuits

modules

assigned

represent

simplification
for the netwcrk manager.
They actually cover parts of
the Network Management Link Watcher and Data
Link
Service
Functions
described 1n a later section.
.
Each of the maintenance modules
contains
the
1low
1level
data
base
necessary
to perform their respective functions on Ethernet circuits.
"Within the modules, the information is organized by circuit.
The

looper

module

necessary

for

Ethernet

loopback

testing.

The loader modulé is necessary for Ethernet up-line dump and down-line
load.

The console module

is necessary for Ethernet remote console functions.

The configurator module is
stations

an Ethernet

necessary

line.

for

user

determining
of

the

1list

Module functions, parameters, counters, and events are currently
the

2.4

Network

Applications,

Network Management,

console module.

and Data

Link

from

layers.

Model of Netwofk‘Management Components 1n the DNA Layers

The functional components of Network Management are as follows:
user

layer

components

Network Control
enables

terminal.

the

Program

operator

Section

(NCP).

to control

specifies

The

and

the NCP

Network

observe

Control

the

commands.

network

Program
from

Functional Description
Network Management

layer

Page 20

components

Section
5 specifies
the Network Management layer
their

operation.

Figure 2,

Network Management
The

components

following,

layer modules

in a

components and

shows the relationship of

single node.

are:

Network Management Access Routines.
These routines provide
user
programs
and
NCP with ceneric Network Management functions, and
either convert them to Network Information and
Control
Exchange
(NICE)
protocol
messages
or
pass them on to the Local Network
Management
Function.
Section
5.1
describes
the
Network
Management Access

Routine's

operation.

Network Management Listerer.

The

Network

Management

Listener

these requests to the Local Network Management Function.
5.1 describes the Network Management Listener,.

Section

receives
Network Management commands from the Network Management
level
of
remote
nodes.
via
the
NICE
protocol.
In
some
implementations
it also receives commands from the local Network
Management Access Routines via the
NICE
protocol.
It
passes

Local Network Management Functions.
These take function requests
from
the
Network Management Listener and the Network Management
Access Routines and convert them to system dependent calls.
They
also
provide
interfaces
to
lower
1level
modules directly for
control
purposes.
Section
5.2
describes
the Local
Network
Management Function's operation.

Link Watcher.
The Link Watcher is a component in a node that can
sense
service requests on a data link from a physically adjacent

node.
it controls automatically-sensed down-line load or up-line
dump requests.
Section 5.3 describes the Link Watcher operation.
Maintenance
operations,

specified

Functions.
These
are
the
actual
malntenance
such
as
down-line load or link loop test, that are
1in
the
DNA
Low
Level
Mailintenance
Operation

specification.

Data Link Service Functions.
These provide the Link Watcher
and
the
Local Network Management Functions with line services needed
for service functions that require a direct i1nterface to the data
link
layer
(line
level
testing,
down-line
1loading,
wup-line
dumping,
triggering
a
remote
system's
bootstrap
1loader
and

setting

the

1line

state).

The

Data Link Service software

(or

hardware) component maintains internal states
as
well
as
line
substates.
Section
5.4
describes
the Data
Link
Service
operation.

Event Logger.
The
Event
Logger
provides
the
capability
of
logging
significant
events
for operator intervention or future
reference.
The process concerned with the event
(for
example,
Routing)
provides
the
data to the Event Logger, which can then
record it.
Section 5.5 describes the Event Logger operation.

Functional Description

Page 21

Network Application layer components'
Loopback Mirror.
Access and service routines
communicate
using
the
Loopback
Mirror
Protocol
to provide node level loopback on
logical links.
Section 5.13 describes this
Network
Application
layer

Object

component.

Types

The

Network

object
The

Management architecture

types.

object

Each has

types

and

Type

Network

requires

a unique object

numbers

type

are:

Object Type Number

Management

Listener

Loopback Mirror

Event Receilver
Table

- Networkx Management

26
Object

three

number.

Types

separate

Functional

Description

Page

S ———————— .

/ \

)

e _———

Interfaces

for

requests

Control Interfaces

function

- -t
%$%5%%%\
\

|
\Y4

NCP

User

Program

USER LAYER

Link

commands

B ettt '
|

S ——— .
| Network

NICE
|
Protocol|

Management
Access

|
|

NICE
Protocol

from other

T.
|
|

Network

|
|

Network
Management

|
|
|

|
|

Management |<--"
Listener
|

||
|

|
|
N

|
|
|

|
\
-.

VAR
s

Local Network Management Functions

Functions

———

LAYER

{

|
|
|

|
|

<---- '

|
|

Events

|
|

<—=-————- ]
| Event
| <=

other nodes

e >|

3
|

|
|

Logger

|
|

======

(file access,

loopback,

set

logical

timer,

|
|

etc.)

|
V

interface to

read event

Layer Modules

and

=====

link

Control

|
|
|

System dependent calls to
application layer and local
operating system functions

etc.)

Network Management
Node.

Events from
other nodes---.

================

line state,

turn on NSP,
2.

|
|

Control over lower
level functions

Figure

\Y
|
Service interface
to
Data Link Layer

(examine

|
|

- o
|

==s===s====s============

| <-=—mm
|

LOWER LAYERS

0
|

NETWORK MANAGEMENT

‘————T —————— !
|

|
|
|

Service
Functions

====

|
|
|

Maintenancel|<-'

Data Link

|
|

|l
o
b

Interfaces

queues

in
|

Single

Network

Management

Seen

NETWORK MANAGEMENT

This

section describes

parameters,

SEEN

1in

counters,

descriptions are both an
commands
described
in

Management

functions

the

User

BY THE

detail

events

NCP

Page

USER

the

and

entities

other

commands

and

entity

introduction to and
Section 4.
Section

for

their

options.

These

a reference for
the
NCP
4.1 describes the Network

that

wuse

the

parameters

described
1in
this section.
User programs can access these functions
using the NICE protocol (Section 6).
The NICE protocol binary formats
associated
with the
entities,
parameters, counters, and events are
specified 1in Section 7.
The descriptions in this
secticn
relate
parameters,
counters,
and
events
to
the
architectural
layers
to
which
they
belong. Some
parameters are
specified
as
read-only.
This
means
that
Network
Management
can
only
read
the value, and cannot directly change 1it.
"Changes to parameter values are typlcally under
control
of
the
DNA
layer

that

"owns"

the

parameter.

In some of the descriptions 1in this section the term 1d-string 1s used
to
describe
an
1identification.
In all of these cases, an 1id-string
consists of one to sixteen
characters
from
the
set
of
upper-case
alphabetics,
numerics,
period and hyphen.
An id-string must contain
at least one alphabetic character.
Ethernet

addresses

ethernet-address.

digits,

bytes

to
right
address is

appear

several

times

ethernet-address

separated by hyphens.

as
transmitted
and
AA-00-04-00-0E-01.

parameters

string

The bytes are ordered

received on
|

the

Ethernet.

In the following descriptions keywords (words that Network

reserves
optional

3.1

for
input

wuse in NCP
or output.

commands)

are

capitalized.

called

hexadecimal

from

left

example

Management

Brackets

enclose

Nodes

A node 1s
an
1mplementation
of
a
computer
system
that
supports
Routing,
End
Communication,
and
Session
Control.
Each node has a
unique address assigned by the manager
of
each 'node.
The
Routing
layer
sends
user data to nodes according to the node address.
Since
1t 1s easiler for humans to address nodes by names, DNA allows one node
name
for
each
node.
The network manager should make sure that each

node name and address in the network is
unique.
(An
may also provide the ability to assign additional node
but these names can be known to the local node
only.
Routing specification.)
The user
groups.

can
To

identify nodes 1in two major ways:
identify a node individually, there

implementation
names to nodes,
Refer
to
the

individually
and
1in
are, again, two major

ways:

Specify

the

keyword NODE

along

with

node-identification

Network Management

the

as Seen by the User

Page

format:

NODE

node-identification

The node-identification
node—-name

is one of

the

following:

A node name consists of one to
alphanumeric
characters
with

six upper case
at
least one

alpha character.
A node name must be unique
within a node and should be unique within the

A node address 1s a hierarchically structured
number
assigned
to
a
particular node.
It
consists of two parts, an area number
and
a
node
number.
Each
of these is an unsigned
decimal
1integer.
They
are
displayed
or

entered separated by a 51ngle period.
area
the

number 1s
area
of

not
the

If the

specified, 1t defaults
to
executor node.
Each node

address must be unique.
unique
within
an area,

Node numbers must be
but may be re-used 1in

differert

the

areas.

Only

with

the

address

the

EXECUTOR,

executor node can be set.
Note:
In a single
area neztwork, the area number defaults to "1"
(by convention), and is hidden from the user.

Specify the executor

ncde

keyword

follows:
EXECUTOR

Node

group
ACTIVE

identifications
NODES

For

are
a

nonrouting

executor
link,

For

follows:

sees

node,

the

as adjacent,

all

that

as designated

routing

1intra-area

nodes

other end of
node,

the

logical

router.

all of

the

above
plus
all
nodes
that
the
executor
perceives as reachable within 1ts area.
For an
inter-area router, all of the
above
plus
all
nodes
the executor sees as adjacent 1nter-area
routers.

ADJACENT NODES

All nodes that the executor
perceives
Routing
can
reach
and
that
are
physically adjacent

(i.e.

separated from the executor by a

circuit).
different
adjacent
of a node
it
KNOWN NODES

single

Each
occurrence
of
a
node
on a
circult
appears
as
a
separate
node.
In other words, the adjacency
1is quallfled by the circuit on
which

adjacent.

As defined for ACTIVE
NODES,
plus
all
nodes
that have a name, including names that map to a

node—address

network.

Network Management

as Seen

the

circuit
LOOP

NODES

All
for

User

(i.e.,

Page

loop nodes).

nodes that are associated
loop testing purposes.

SIGNIFICANT NODES All nodes

that

associated with

When obtaining node
1s

returned

The

format

NODE
For

first,
for

information,
and

that

displaying

node-address

for

node

have

them

nodes,

with

significant

for

circuit
|

information

display purposes.

=-hat pertaining
loop

the executor

node

last.

identification

is:

[(node-name)]

example:

'NODE
=

NODE

(Elrond)

3.19

(Fargon)

A node-related routing concept that 1s visible in
Network
Management
is
that
of
an
adjacency.
An
adjacency
1s an
adjacent node as
reachable over a particular
circuit.
Each
different
circuit
that
leads
to
an
adjacent
node
<counts
as
a separate adjacency.
Each
different adjacent node on a circuit counts as a separate adjacency.

3.1.1

The

Node

node

according
layer that

The

Parameters

parameters

following

are

to
the DNA layer that owns
contains node parameters.

executor

node

keeps

base

two

data

its

own

bases

listed

them,

1in

alphabetical

starting with

relative

A data

A data base of remote node parameters (for
and of optional adjacent node parameters.

the

nodes:

node parameters

each

remote

Many types of parameters kept 1n the executor node data base
kept
some

1n
the
data
bases the executor
remote node parameters can only be

"Thus, 1n
applying

order

highest

are

keeps for remote nodes.
kept for adjacent nodes.

node)

not

Also,

the descriptions below some parameters are
distinguished
to the executor node, remote node, or the adjacent node.

Some parameters are described as loop-only.
This means that they
are
parameters
that only exist for use with the LOOP command and the Test
message.
Some of them have fixed, default values.
.

Network Management as Seen by the User

3.1.1.1

Network Management

Page 26

Layer

COUNTER TIMER seconds

This value is the number of
seconds
between
node
counter
1log
events.
The expiration
of
the timer
causes
a node counter
logging
event.
Refer
to
the
two
sections
entitled
"Node
Counters"”
and
"Events"
for
1lists of node counters and events.,.
When the counter timer expires, the node counters are recorded as
data
in
the
event
and
then zeroed.
If no value
1s set, node
counters are not automatically logged.
Seconds is specified as a
decimal

—

number

the

range

1-65535.

the

d=fault

CPU cpu-type

This value
down-line

indicates

loading the adjacent node.

target

node

CPU

typé

The possible values are:

for

PDP8
PDP11

DECSYSTEM1020
VAX

DIAGNOSTIC

FILE

file-1id

This is the identification of the file
to
read
from
when
the
adjacent
node
l1s
down-1line
loaded
and
has
requested
"diagnostics".
The file
1identification
1is
a
string
that
1s
interpreted depending

DUMP

the

file

This value represents the address
COUNT

the

executor.

adjacent

1n memory to begin

node.

up-line

number

This value

DUMP

the

ADDRESS octal-number
dump of

DUMP

system of

from

the

FILE

file-1id

the default

adjacent

This value

adjacent
node
string that is

the

number of memory units

to up-line

dump

node.

identification of

the

file to write

to when

1is
up-line dumped.
The file identification
interpreted according to the file
system
of

the

1s a
the

executor.

HARDWARE ADDRESS

ethernet—-address

This value is the Ethernet hardware address of the adjacent node.
It
1is
the
Ethernet address that 1s assigned to the node system
hardware.
This address is necessary for communication
with
the
system
for
such
purposes
as down-line load before 1t has been

able to meet
address.

the

DNA
-

requirements

for

setting

1its

physical

Network Management

)

HOST

as Seen by the User

Page 27

node-1id

For

the

executor

the
executor
executor node.

node,

this

receives

1ts

value

i1dentifies

services.
|

This

For adjacent nodes, this value is the

host

the

adjacent

value

node

defaults

IDENTIFICATION

This is a
example,

receives

the

when

executor

the

node

value
|

from

which

defaults

identification

down-line

that

loaded.

node.

the

This

string

text string
that
"Research
Lab").

cescribes
the
The
string is

executor
node
(for
32 characters of any

type.
When entered in NCP,
1f
the
string
contains
blanks or
tabs,
1t
must be enclosed ir quotation marks.
A quotation mark
within a quoted string is indicated
by
two
adjacent
quotation
marks ("").
|
LOAD

FILE

file-1id

This 1s the identification of the file
to
read
from when
the
adjacent
node
1is
down-line loaded and has requested "operating
system".
The file identification is a string that is interpreted
depending on the file system cof the executor.
LOOP

ASSISTANT
NODE node-id

This

identifies

LOOP

CIRCUIT

testing.
-

LOOP

This

the

CIRCUIT

for

parameter

parameter
Ethernet

applies

loop-only parameter

command

cannot be

executor
COUNT

This

used only

third-party

the

executor

input

circuit

node

the
loop

only.

the

executor

HELP

node

for

Ethernet

multicast

used only

third-party

address.

only.

This

input
circuit

the

loop

LOOP

testing.

parameter applies

the

count

loop

LOOP

loop-only

ASSISTANT PHYSICAL ADDRESS ethernet-address
This

LOOP

the

command

loop-only default

data
node

for

only.

loop

Its

count
test.

value

for
This

the

number

parameter

times

applies

to
the

help-type

This 1s the loop-only default help type for Ethernet circuit
testing.
This parameter applies to the executor node only.
value 1s FULL.
|

loop
Its

LOOP LENGTH length
This
in

is the loop-only default
a

loop

test.

This

length for the data that

parameter

applies

the

looped

executor

node

Network Management as Seen by the User
only.

Its value

Page 28

40.

LOOP NODE node-1id

This identifies the loop-only parameter used only as 1input on the
Ethernet circuit loop testing.

This

This is the loop-only default bplock type for loop testing.

This

LOOP

command

CIRCUIT

for

parameter applies to the executor node only.
LOOP WITH block-type

Its value 1s MIXED.

parameter applies to the executor node only.
PHYSICAL ADDRESS ethernet-address

This

MANAGEMENT

executor

read-only

in use to

currently

VERSION

paremeter

identify

1tself.

Ethernet

the

address

n.n.n

of
consisting
This is the read-only Network Management Version,
the Eng:neering Change Order (ECO) number,
the version number,
parameter
This
3.0.0).
example,
and the user ECO number (for
applies

the

executor node orly.

SECONDARY DUMPER file-id
This identifies the secondary cumper file for up-line dumping the
The file identification is interpreted depending
node.
adjacent
«
|
|
on the file system of the executor.
SECONDARY LOADER file-1id

down-line

This identifies the secondary loader file for
the adjacent node.

SERVICE CIRCUIT circuit-1id

This identifies the circuit to the adjacent
loading

and

up-line

is not
the circuit-id

dumping.

node for

down-line

This is the default parameter 1if

included in a down-line load command.

SERVICE DEVICE device-type

adjacent
the
This is the identification of the device type that
mode
slave
service
1in
functions when
service
for
uses
node

(Section 5.4).

device mnemonics

The device type
(Table 10,

1is

one

Section 7.4).

the

standard

line

~ SERVICE NODE VERSION node-version

to
wused
1s
This is the DNA version of the adjacent node, which
MOP
the
1n
parameter
SYSTEM ADDRESS
TARGET
the
determine
Parameter Load With Transfer Address message (see DNA Maintenance
The default value 1s 1
Specification).
Functional
Operations

Network Management as Seen by the User
(Phase

Page 29

1V).

SERVICE PASSWORD password
‘This is the password required to trigger the bootstrap

mechanism

on
the

number

the
adjacent
node. The password is
range 0 - FFFFFFFFFFFFFFFF 164 bits).

SOFTWARE

hexadecimal

IDENTIFICATION software-id

This 1dentifies the software to be loaded when the adjacent
node
1s down-line loaded.
Software-:d is a string of 1-16 characters.
SOFTWARE

TYPE

program-type

This value represents the targe= node
type
for
one of:

down-line

the

initial

adjacent

software

node.

Program

program
type

SECONDARY
TERTIARY

[LOADER]
[LOADER]
|

SYSTEM

STATE node-state

e the‘ executor node.
the operat| ional statof
ents are:
This repres
state

possible

ON
OFF

Allows

Allows no
and stops

SHUT
\W‘.—//

logical

links.

new 1links, terminates existing
routing traffic through.

LOADER

This

nodes.

file

for

identifies

ADDRESS

Session

other

file-id

the

tertiary loader

down-line

the
adjacent
node.
The
file
1dentification
according to the executor node file system.

- 3.1.1.2

1links,

Allows no new logical links,
does
not
destroy
exlisting
logical 1links,
and
goes
to the OFF
state when all logical links are gone.

RESTRICTED Allows no new incoming logical links from
TERTIARY

The

Control

1loading

1nterpreted

Layer

node-address

This value
applies to

is the address of
the executor node

the executor
only.

node.

This

parameter
|

Network Management as Seen by the User

Page 30

CIRCUIT circuit-1id

This value identifies a
loop
node
for
testing
and
sets
the
identification
of
the circuit to be used for all traffic to the
node.
The circuit-id can be associated with only one
1loop
node
name.
Refer to the section entitled Testing Link and Network.
INCOMING TIMER seconds

This value represents the maximum duration
between
the
time
a
connect
1is
received
for a process at the executor node and the
time that process accepts or rejects it.
If the connect
1s
not
accepted
or
rejected
by the user within the number of seconds
specified, Session Control rejects it for the user.
1If no
value
is

NAME

set,

there

1s no

timer.

node-name

This parameter represents the name to be associated with the node
identification.
Only one name can be assigned to a node address
or a circuit

once

identification.

network.

No name should be
Node-name
is
one
to

alphanumeric characters with at

wused

six

more
upper

least one alpha character.

than

case

OUTGOING TIMER seconds

This value represents the duration between the time the
requests

connect

and the time that connect

executor

1s acknowledged by

the destination node.
If the connect is not acknowledged
within
the
number
of
seconds
specified,
Session
Control returns an
error.
If no value is set, there is
no
timer. The
range 1s
1-65535.

3.1.1.3
ACTIVE

End Communication Layer
LINKS

number

This read-only parameter represents the number of active
links

from the executor

the destination node.

logical

DELAY seconds

This read-only parameter is
the
average
round
trip
delay
1in
seconds
to
the
destination
node.
This parameter 1s kept on a
remote

DELAY

FACTOR

node

basis.

number

This is the number by which to
multiply
one sixteenth
of
the
estimated round
trip
delay to a node to set the retransmission
timer to that node.
The round trip
delay
1s
wused 1n
an
NSP

algorithm

that

determines

Communication specification).

when

retransmit

The number

a message

is decimal

(End

in the range

‘Network Management

as Seen by the User

Page

1-255.
DELAY WEIGHT

This

number

represents

the

weight

trip
delay estimate
to a remote
round trip delay to a node.
The
1-255.

for

INACTIVITY

some

systems

computational
TIMER

the

apply

number must

efficiency

current

round

node when updating the estimated
number is decimal in
the
range
be

less

than

power

(End Communication specification).

seconds

This value represents the maximum duration of inactivity (no data
in
either direction) on a logical link before the node checks to

see

the

within

logical

link

the minimum number

artificial

traffic

specification).

still
of

seccnds,

works.

test

the

activity

occurs

End Communication generates

link

The value range is 1-65535.

(End

Communication

MAXIMUM LINKS number
This value represents
the
allowed
for
the executor.

NSP

range

1-65535,.

VERSION

n.n.n

maximum
active
1logical
1link
The count 1s a decimal number

This read-only parameter represents the
node
End
Communication.
The
format
Network Management version.
RETRANSMIT

FACTOR

This value

number
same as

of
for

the
the

number

represents the maximum number of

Communication
retransmission

at
the
timer when

1-65535.

times

the source

End

executor
node
will
restart
the
it expires.
If the number i1s exceeded,

Session
Control
disconnects
Communication specification).

3.1.1.4

version
1s
the

count
1in the

the logical link for the user (End
The number is decimal in the range
|

Routing Layer

AREA MAXIMUM

COST

number

This value represents the maximum total path
cost
allowed
from
the executor to any other level 2 routing node.
The AREA MAXIMUM
COST number is decimal in the range 1-1022.
This
parameter
1s
only applicable if the executor node is of type AREA.

AREA MAXIMUM HOPS number
This
value
represents
the
maximum
number
of
allowable
from
the
executor to any other level

routing
2 routing

hops
node.

Network Management as Seen by the User

Page 32

The AREA MAXIMUM HOPS number is decimal in the range 1-30.
This
parameter
is
only
applicable
=:f
the executor node 1s of type
AREA,

BROADCAST

ROUTING TIMER seconds

This value determines the maximum time
allowed
between
Routing
updates
on
Ethernet circuits.
When this timer expires before a
routing update occurs,
a
routina
wupdate
1is
forced.
With
a
standard
calculation,
Routing a-so uses this timer to enforce a
minimum delay between routing
upaates.
Seconds
1s
a
decimal
integer
BUFFER

SIZE

the

range

1-65535.

bytes

This parameter value determines tze maximum
size
of
a
Routing
message.
It
therefore determines the maximum size message that
can be forwarded.
The size 1s a decimal 1integer
1n
the
range
1-65535.
This
size
1s
1n bytes.
This size 1includes protoccel
overhead down to and including the End Communication layer,
plus
a
constant
value of 6.
(This value of 6 is included to provide

compatibility with the parameter cefinition in Phase
III,
which
included
the
Routing overhead.) It does not include Routing or
Data link overhead (except for the constant value of
6).
There
is one

buffer

size

for

all

circuics.

NOTE
The BUFFER SIZE defines the maximum size messages
that

the

Routing

layer

can

forward. The

SEGMENT

BUFFER SIZE (defined below) defines
the
maximum
size
messages
that
the End Communication layer
can transmit or receive.
The SEGMENT BUFFER SIZE
s
always less than or equal to the BUFFER SIZE,.
Normally the two parameters will be equal.
They
may be different to allow the network manager to

alter
buffer
sizes
on
all
nodes
wilthout
interruption
of
service.
They both include an
extra 6 bytes for compatibility with Phase III.
CIRCUIT

circuit-1d

This read-only parameter identifies the circuit
remote node.
Circuit-id is an id-string.

used

to get

This parameter can be used when displaying a
1list
of
nodes
to
indicate
that
the
display
1s
to be restricted to those nodes
adjacent on the specified circuit.
COST

cost

This

read-only parameter

represents

the

total

cost

over

the

current path to the destination node.
Cost 1s a positive 1nteger
value associated with using a circuit.
Routing
routes
messages
(data)
along
the path between two nodes with the smallest cost.

Network Management as Seen by the User
COST
HOPS

is kept on a remote node basis.

hops

This

read-only parameter

represents the number of hops over to

destination node.
A
hop
1is
Routing
value
logical distance between two nodes in a network.
a

Page 33

remote

node basis.

MAXIMUM ADDRESS

number

This value represents the largest
number
of
home area.

MAXIMUM AREA

representing the
HOPS is kept on

node

number

and,

therefore,

area

number

and,

therefore,

nodes
that can be known about by the executor node's
The number is an integer in the range 1-1023.

number

This value represents the largest

number
of
areas
that can be known about by the executor node's
Routing.
This parameter is only aoplicable if the executor
node
is of type AREA.
The number is an integer 1in the range 1-63.

MAXIMUM BROADCAST NONROUTERS

number

This value represents the maximum rotal number of nonrouters
the
The number 1is
can have on its Etaernet circuits.
node
executor
an

integer

in the

range 0-65535.

MAXIMUM BROADCAST ROUTERS number
This value represents the maximum total

executor
an

integer

node

MAXIMUM BUFFERS

number

can have on its Etaernet circuits.

in the

range

routers

the

The number 1is

0-65535.

number

This value represents the maximum number of transmit buffers that
number is a decimal
The
circuits.
all
for
Routing may use
integer

‘MAXIMUM CIRCUITS

the

range

1-65535.

number

This value represents the maximum number of Routing circuits that
is decimal in the
The number
node can know about.
executor
the
range

1-65535.

MAXIMUM COST number'
This value represents the maximum total path

cost

allowed

from

The path cost 1s the
the executor to any node within an area.
This
sum of the circuit costs along a path between two nodes.
parameter defines the point where the executor node's Routing
unreachable
another node
algorithm declares
routing decision
of the least costly path to the other node is
cost
because the
be
not
parameter must
For correct operation, this
excessive.

Network

Management

Seen

the

User

Page

less than the maximum path cost of the network.

number
MAXIMUM

HOPS

This

decimal

the

range

The MAXIMUM COST

1-1C22.

number

wvalue

allowable

represents

from

the

the maximum

executor

any

number

other

routing

reachable

node

hops

within

area.
(A hop is the logical distance over a
adjacent
nodes.)
This
parameter
defines

circuit between
the
point where

executor
another

between

node's
Routing
unreachable

node

the

parameter

two

nodes

must

not

routing
because

too

decision
length

long.

1less

For

than

correct

the

where reachability distance
between
a
given
pair
of
decimal in the range 1-30.
VISITS

is the length
nodes.)
The

two
the

algorithm
declares
the shortest path

tne

operation,

network diameter.

network diameter 1s the reachability
distance
between
nodes
of
the network having the agreatest reachability

MAXIMUM

this

(The

the
two
distance,

of
the
shortest
path
MAXIMUM HOPS number 1is

number

This value represents the
maximum
number
of
nodes
a
message
coming
1nto
the executor node can have visited.
1If the message
1s not for this node and the MAXIMUM VISITS number
1is
exceeded,
the
message
1s discarded.
The MAXIMUM VISITS parameter defines
the point where the packet lifetime control algorithm discards
a
packet that has traversed too many nodes.
For correct operation,
this parameter must not be less than the maximum path
length
of
the
network.
(The
maximum path length is the routing distance
between the two nodes of the network having the greatest
routing
distance, where
routing
distance
is the
1length of the least
costly path between a given pair of nodes.)
The
MAXIMUM
VISITS
number 1s decimal in the range MAXIMUM HOPS to 63,
NEXT

NODE

node-1id

This

read-only value

to
ROUTING

get

TIMER

the

node

indicates

under

the

node

the

circuit

used

scrutiny.

seconds

This value determines the maximum time
allowed
between
Routing
updates on non-Ethernet circuits.
When this timer expires before
a routing update occurs, a routing update is forced.
Seconds
1is
a decimal integer in the range 1-65535.
|
ROUTING

VERSION

n.n.n

This read-only parameter

identifies the executor

version
number.
The
format
Management version number,
SEGMENT -BUFFER

This

SIZE

bytes

parameter

value

determines

the

same

the

maximum

size

node's

Routing

for

Network

of an

the

end-to-end

Network

Management

segment.
This size

The
1s 1n

Seen

the

User

Page

size
1s
a decimal integer in the range 1-65535.
bytes.
This size ircludes protocol overhead down

to
and including
the
End Communication layer, plus a constant
value
of
6.
(This
value
of
6
1is
included
to
provide
compatibility
with
the
BUFFER
SIZE parameter definition.)
It
does not include Routing or Data link overhead
(except
for
the
constant value of 6).
See additional note for BUFFER SIZE.
SUBADDRESSES

subaddress-range

This parameter 1s the range of loca: DTE

acceptable
on
any
X.25
Subaddress-range consists of
subaddresses
separated by
decimal integer 1in the range
provided, the second must be
TYPE

subaddresses

that

are

circuilt
for
an
1incoming
call.
either
a single
subaddress
or
two
only
&
hyphen.
A subaddress 1is a
0-9999.
If
two
subaddresses
are
greater than the first.

node-type

This parameter indicates the type
node-type 1s one of the following:
ROUTING

the

executor

node.

The

III

NONROUTING
ROUTING

III

NONROUTING

AREA

A routing node has full routing capability.
A
nonrouting
node
contains
a subset of the Routing routing modules.
The III and IV
indicate the DNA phase of the node. Nonrouting nodes can deliver
and
receive
packets
to
and
from
any
node, but cannot route
packets from other nodes through to other nodes.
An
area
node
routes
between
areas.
Refer
to the Routing specification for
details.
~

3.1.

For adjacent nodes, this i1s a read-only parameter
- the type of the reachable adjacent node.

Node

that

Counters

Network Management displays or zeroes node counters as a
following

Network Management

Seconds
The

indicates

following

since

last

counter

User
User

bytes received
bytes sent
User messages received
messages

Total

bytes

kept

for

nodes:

are

kept

for

group.

zeroed

End Communication

User

sent

received

counters

nodes:

The

Network Management as Seen by the User
Total

bytes

Page 36

sent

Total messages received
Total messages sent
Connects received
Connects

sent

Response
Recelved

timeouts
connect resource

~Maximum logical
The

following
Aged
Node

links

Routing

loss
unreachable

errors

active

counters

are

(executor only)
kept

for

the

executor

node:

packet

lOSS—

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

Verification

reject

Refer to the relevant specifications
type
of information counted.

3.2

for

further

explanation

the

nodes

for

Areas

An area

is a group of nodes.

hierarchical

routing purposes.

The network
(Refer

manager

groups

the Routing

specification.)

The user can identify areas
1n two major ways:
individually
and
1in
groups.
To
1dentify
an area individuaily, use the area number.
An
area number i1s a decimal integer in the range
1-63.
By
convention,
Area
"1"
is
wused to designate a single area network and Area "0" 1s
used when communicating with a Phase III node.
Area

All

group

1dentifications

are

follows:

ACTIVE AREAS

All areas that the executor perceives Routing

KNOWN

Same

the

AREAS

can

reach,

area parameters

ACTIVE

are

AREAS.

owned

the

routing

layer

and

are

follows:

CIRCUIT

circuit-1id

This read-only parameter
remote area.
Circuit-i1d
COST

identifies the circuit
1s an 1d-string.

used to

get

cost

This read-only parameter
represents
current path to the destination area.

the
total
Cost is a

cost
over
the
positive 1nteger

Network Management

value

Seen

the

associated with using

(data)
HOPS

User

Page

circuit.

Routing

routes

messages

along the path between two areas with the smallest cost.

hops

This read-only parameter represents tne number of hops over to
a
destination
area.
A
hop
1s
Routing
value
representing the
logical distance between two areas 1in a network.

" NEXT NODE node-id
This read-only value indicates the next
to get to the area under scrutiny.
STATE

the

circuit

used

state

This

read-only value

REACHABLE,

3.3

node

indicates

the

state

the

area,

-either

UNREACHABLE.

Logging

Logging 1s the Network Management'automatic event—recording mechanism.
The logging entity identification 1is the sink type.
Logging
may
be
referred
to by individual sink types or by the sink types as a group.
The formats
for
specifying
1logging
entities
symbolically
are
as
follows:

LOGGING sink-type

A particular

KNOWN LOGGING

All logging sink types known to the

executor

ACTIVE LOGGING

All known sink types that are in ON

node

state

SIGNIFICANT LOGGING All

known sink

information

sink

type

one

logging sink type

the

types

that

HOLD
|

have

significant

for display purposes.

following:

CONSOLE
FILE

MONITOR

Network Management sends
nodes.

The user

identification

information

establishes
as

follows:

SINK NODE node-identification
or

SINK

EXECUTOR

about

logged

events

sink nodes with NCP commands.

sink

Sink node

Network Management as Seen by the User

Page 38

The default sink-node is the executor node.

3.3.1

Source Qualifiers

Events occur at logging sources.
Since loaging for a specific
entity
can be different from logging for that entity as a group, the user can
specify that specific sources be logged by using the
source-qualifier
option.
Source-qualifier can be one of the following:
AREA area-1id
CIRCUIT circuit-1d
LINE line-1id
MCDULE module-1id
NODE node-1id

Refer to Sections 3.1, 3.4,
circuit-1d,

3.3.2
All

line-i1d,

Logging

the

These

and 3.7

for descriptions of

node-id,

Parameters

logging parameters

parameters

EVENTS

3.5,

and modULe 1d.

are

owned by

the Network Management

follows:

layer.

event—list

This set of values indicates the
be
recorded
at
the sink-node.
specify event classes and types.

1lists
wusing
commas,
event-lists are:

O\ W

type(s).

hyphens,
Examples
l—-‘l—‘O

class.event
in
of

The

types and classes of
events
to
Tables 22 and 23, Section 7.12,
Event-list
consists
of
event

types

are

specified

ranges using

combilnation

both.

-2
-4,8,10

y 3,5

wild card notation indicates
class.
For example,

all

types of

events

for

partlcular

3.%

The

keywords

KNOWN EVENTS

can

replace

EVENTS

event-list

NCP

commands.
KNOWN
EVENTS
1imply all events known to the executor
node for the specified sink node and source.
If
no
source
1is
specified, source specific events are not affected.
NAME

sink-name
This is the identification of the executor
Sink-name has one of three forms depending

node's
on the

1logging
sink.
sink-type:

Network

Management

Seen

Type

User

Page

Sink-name

CONSOLE

device-id

FILE
MONITOR

The

the

sink

file-1id
process-1d

name

format

depends

what

the

This parameter identifies
the
sink
nrode
parameters 1in a command or response apply.
1s the executor.
Node-id is either a rode

to
The
name

executor

system

understands.

SINK NODE

node-1id
which
the
other
default sink node
or a node address

(Section 3.1).

STATE sink-state
This valye
sink type.

The

OFF

The sink 1is not available
1t should be discarded.

HOLD

The sink 1s
be queued.

sink

1logging

executor node's logging
state
values of sink-state are:

There
are
parameters.

3.4

indicates the
The possible

available

for

temporarily

counters.
|

receiving
and

Section

3.8

the

events.

any events

unavailable

for

and

destined

events

for

should

describes
|

event

Circuilts

Circults are logical
communications
paths
providing
communications
between
adjacent
nodes.
A
circuit
may be identical to a physical
link, multiplexed with many other circuits, and/or traffic split
over
multiple physical links.
L}

Circuit 1dentification 1s
a
circult
1d-string.
Network
Management keeps
ensuring their uniqueness for the Data

Circuits can be

identified

name
with
the
a master list of
Link layer.

in groups as

format
circuit

of
an
names,

follows:

.KNOWN CIRCUITS - All circuits that have a name.
ACTIVE CIRCUITS- All circuits in the ON or SERVICE state.
SIGNIFICANT CIRCUITS parameter,

circuilt

can

have

All

circuits

that

have

least

one

owner.

This means

that

the

circuit

reserved

Network Management as Seen
by the User
for

the

exclusive

use

executor node (Routing)

the

owner.

Page 40

For

example,

the

owner may be

the

or some other network component,

Whether or not it has an owner, a circuit has a user
whenever
1t
1s
open
for use through the mechanisms of the Data Link interface.
User
in this sense 1s a
user can be either

When

Network

overridden.

network component, not a
person.
Currently,
the owner or the X.25 prorocol module.

Management
For

uses

example,

circuit to execute such service
loop
testing.
When
Network
function,

3.4.1
There

the

circuilt

Circult
are

circuit,

the

Management

wuser's
must

returned

the

five

groups

circult

the

user.

parameters:

Common circuit
all
circuits
Parameters).

Executor node circuit parameters
apply
only
to
«circuits
whose

(Refer

parameters
(Refer
to

the

-- These are parameters
common to
the section entitled Common Circuit

section

-- These are parameters that
owner 1s the executor node.

entitled
|

Executor

Node

DDCMP circuit parameters -- These are parameters

X.25

to DDCMP circuits only.
Circuit Parameters.)
circuit

parameters

circuits
only
Parameters.)

3.4.1.1

are

over

functions
as
down-line
loading
and
Management
finishes
1ts prescribed

rights

take

Parameters

Parameters.)

The

Network

the

Ethernet

Ethernet
Ethernet

(Refer

«circuit

(Refer

These

the

apply

X.25

entitled X.25 Circuit

parameters -- These parameters

circuits
only
(Refer
Circuit Parameters.)

that

section entitled DDCMP
|

parameters

section

Circuit

the

section

apply

to.

entitled

Common Circult Parameters

following

COUNTER TIMER

parameters

are

common

all

circuilts:

seconds

This
value
represents
the
number
of
seconds
the
Network
Management counter timer will run.
The expiration of the counter
timer causes a circuit
counter
logging
event.
The
types
of
counters
logged
depends
on
the
circuit
protocol.
Circuit
counters are described in Section 3.4.2.
The
circuilit
counters

Network Management as Seen by the User

Page 41

are
recorded
as data in a logging event and then zeroed.
If no
counter timer value
1s
set,
the
<circuit's
counters
are
not
automatically
logged.
Seconds is a decimal integer 1in the range
1-65535.

OWNER owner-1id

This value identifies the circuilt owner.
Except
for
overrides
through Network Management, the owner has exclusive rights to use
the circuit. If no owner value is set, the circuit is
available
on a first-come, first-served basis.
To use

the

circuit,

the owner must

particular

open

Data Link interface.

according

the

rules

Ownership of
a circuit

has no implication as to whether the
its
owner
or
any
other
process.

circuit 1s actively open
by
Sez-ting the OWNER parameter

merely

reserves

the

circuilt.

An owner-id consists of an entity type and entity identification.
The executor node can be owner of any circuit.
This implies that
the circuit is
actually
reserved
the
DECnet
routing
module.
Ethernet
LOADER.

perform

circuits
These are

such

can
be
owned
by MODULE LOOPER, CONSOLE, or
circuits over which tae management module
can

management

functions

loop tests or down-line

loads.

From the standpoint
of
Network
Management,
Ethernet
circuilts
automatically
take
on
the
proper
Ethernet protocol types and
multicast addresses according to their owner's requirements.

STATE_circuit—state

This
wvalue
operational

represents
the
circuilt's
Network
Management
state
as
described in the state and substate model

presented

Section

3.6.

SUBSTATE
This

the

(Section 3.6).

TYPE

circuit's

read-only

Network

the

Management

substate

circuit-type

This

wvalue

circuits,

represents

the

type

the

value must be set to X25.

circuilt.

For

X.25

For DDCMP and Ethernet

circuits it is read only and is the same value as the protocol of
the associated line (see PROTOCOL in section entitled Common Line

Parameters).
USER

user-1id

This is the read-only identification of the active
wuser
of
the
circuilt.
It
tells the network manager what module 1s using the
circult.

Network

Management

the case

but

only

when

Seen

circuit
the

The

LOOPER,

Executor

following
node:

ADJACENT

NODE

has

the

user

Node

LOADER,

Circuilit

parameters

executor

with

Page

owner,

the

user

circuit

open.

the

network

1s
In

the

owner,

case

of
a

component

that

consists of an entity type and entity
identification.
wuser-ids
currently
defined
are EXECUTOR and MODULES

X25-SERVER,

3.4.1.2

User

owner

circult with no owner,
opened the circuit.
A user-1d
The
only

the

CONSOLE,

and

CONFIGURATOR.

Parameters

apply

circuits

that

are

owned

the

|
node-1id

This read-only value indicates an adjacent node on
the
«circuit.
For
Ethernet
<circuits
there
can be many adjacent nodes.
This
parameter can be used when
displaying
a
1list
of
«circuits
to
indicate
that
the display is to be restricted to those circuits
leading to the specified adjacent node.
BLOCK

SIZE

This

byte-count

read-only parameter

the block

size

that

was

negotiated

with
the
adjacent
Routing
layer during Routing initialization
over a particular circuit.
It includes the routing
header,
but
excludes
the
data
1link header.
This parameter is qualified by
ADJACENT

COST

NODE.

cost

This value represents the Routing
The
<cost 1s a decimal integer in
messages

along

the

path

between

routing cost
of
range 1-25.

the

two

nodes

the

circuit.
routes

Routing

having

the

smallest

cost.

HELLO

TIMER

seconds

This value determines the frequency
of
Routing
Hello
sent
to
the adjacent node on the circuit.
Seconds 1s
integer in the range 1-8191.
LISTEN

TIMER

This

read-only value
Dbefore

message

was

NAME

determines

Routing

user

agreed

Routing layer.
1-65535.
This
- LOOPBACK

messages
decimal

seconds

elapse
It

message)
during

Seconds
parameter

node-name

the

receives

from

Routlng

some

the

maximum

time

message

adjacent

node

allowed

(either

the

initialization with

the

Hello

circuit.

adjacent
1s
a
decimal
1integer 1in
the
range
is qualified by ADJACENT NODE.

Network Management as Seen by the User

Page 43

This parameter is the Session Control node name associated with a
circuit
as a result of the "SET NODE node-id CIRCUIT circuit-1id"
command.
From
the
circuit standpoint,
this
1s
a
read-only
parameter,

ORIGINATING QUEUE LIMIT queue-slze

This
parameter
1indicates
the
maximum
number
of
originating
packets
that
may be outstanding on this circuit.
This does not
include
RECALL

route-thru

TIMER

traffic.

seconds

This parameter represents the minimum number of seconds

wait

before
restarting
the circuit.
If no value 1s set, there
walt.
Seconds is a decimal integer 1n the range 1-65535.

3.4.1.3

DDCMP Circuit Parameters

DDCMP circuits support the Network
Management
service
dump,
load,
and
active and passive circuit _oopback.
parameters

\\_'/

LINE

apply to DDCMP

circuilts:

This value is the Data Link layer identification of the line that
for

(Section 3.5).
SERVICE

traffic on the

circuit.

Line-1d

line name

service-control

This value indicates whether or not
Network
service
operations on a circuit.
The values
J

functions
of
The following

line-1id

1s to be used

1s no

are

Management
allows
for service-control

follows:

ENABLED

SERVICE

DISABLED

SERVICE state

allowed.

state

and/or
and/or

service
service

functions

are

allowed.

TRIBUTARY

are
not
|

tributary-address

This value represents
the Data Link physical tributary address of
the

range

circuit.

The tributary address

is a decimal

1-255,

The following parameters apply to DDCMP CONTROL

1integer

in the

circuits.

In those

cases
where
a
value
1is
specified
in
milliseconds,
there
1s no
assumption that all implementations can provide such fine resolution.

ACTIVE/INACTIVE/DYING BASE base

Network Management as Seen by the User

Page 44

This value represents the base priority to which a
tributary
reset
each
time 1t has been polled.
A separate base can be

for

each of

integer
active,

the

1in
255;

indicated polling

states.

the
range
0-255.
If
inactive, 0; and dying,

not
O.

Base
set,

the

1is
set

decimal

defaults
|

are:

ACTIVE/INACTIVE/DYING INCREMENT increment
This value represents
the increment
added
to
priority
each time the scheduling timer expires.
decimal integer in the range 0-255.
If
not
set,
are:
active, 0; inactive,
64; and dying, i6.
BABBLE

TIMER milliseconds

This

value

represents

tributary

the

number

millis=conds

remote half-duplex station

Milliseconds is a decimal integer in the
set, the default is 6000 (6 seconds).
DEAD

the
tributary
Increment is a
the
defaults

THRESHOLD

selected

allowed to

transmit.

range

that

1-65535.

not

poll

active,

count

This value represents the number of times

the

inactive, or dying tributary before changing its polling state
dead because of receive timeouts.
Count is a decimal integer
~the range 0-255.
1If not set, the default :s 8.

to
1in

DYING THRESHOLD count

This value represents the number of times to poll the

active

inactive
tributary
before
changing
1its polling state
because of receive timeouts.
Count is a decimal integer
range 0-255.
If not set, the default is 2.

INACTIVE

to dying
1in
the

THRESHOLD count

This value represents the number of times
to
poll
the
active
tributary
before
changing its polling state to inactive because
of no data response.
Count 1s a decimal
1integer
1in
the
range
0-255.
If not set, the default 1s 8.
MAXIMUM

BUFFERS

count

This value represents the maximum number of buffers the tributary
can

use

common
higher
the
MAXIMUM

from

common

buffer pool and
level.
Count

keyword
TRANSMIT

buffer

buffers are
1s
a decimal

pool.

not

explicitly
integer in

set,

there

supplied
the range

i1s

by
the
1-254 or

UNLIMITED.
count

This value represents the maximum number of
data
messages
that
can
be
transmitted
at one time.
Count is a decimal integer in
the range 1-255.
1If not set, the default is 4.

Network

Management

Seen

the

User

Page

POLLING STATE polling-state
This value
multipoint
AUTOMATIC.

represents
polling
The

the state of
algorithm.

possible

states

the
If

tributary
not
set

relative to
the
default

the
1is

are:

AUTOMATIC

The
the

tributary's state
operation

the

allowed

polling

vary

according

to:

algorithm.

ACTIVE/INACTIVE/DYING/DEAD

The

tributary

locked

the

specified

state.

Polling-substate

This value represents the tributary's state as determined by

the

polling
algorithm,
This applies only when the polling state 1is
AUTOMATIC
and
1s
read-only
to
Network
Management.
Polling-substate
1s one of ACTIVE, INACTIVE, DYING, or DEAD.
It
is displayed as a tag on the polling state, for example:

AUTOMATIC- INACTIVE

TRANSMIT TIMER_milliseconds

This value represents the number of milliseconds to delay between

data message transmits.
range

3.4,1.4

0-65535.

X.25

Circuilt

not

Milliseconds

set,

the

is a decimal

default

integer

in the

Parameters

X.25

circuits do not support any of
functions.
The following parameters

the
Network
Management
apply to X.25 circuits:

service

MAXIMUM DATA byte-count
For permanent circuits,
this
value
represents
the
Data
Link
maximum
X.25
data
size
allowed
on the circuit.
For switched
circults owned by the executor node, this
value
represents
the
size
that
Routing
1is
to
request
from
X.25 for the circuit.
Byte-count 1s a decimal integer in the range 1-65535.
It must be
<=
to the
maximum
data
size allowed within the X.25 protocol
module.
MAXIMUM WINDOW

|
block-count

For permanent circults,
this
value
represents
the
Data
Link
maximum
number
of
X.25 blocks outstanding on the circuit. For
switched
circuits
owned
by
the
executor
node,
this
value
represents
the
window size that Routing is to request from X.25
for the circuit.
Block-count is a decimal integer in
the
range

Network

Management

Seen

the

User

Page

1-255.

USAGE;usage—tYpe
This Data Link parameter

defines

usage-type values

the

Useful only for

OUTGOING

Used only for switched outgoing calls.

Useful only for

circults

PERMANENT

Permanently

does
BLOCKING

that

not

are

owned by

owned
by

connected

need

the

executor

same

dynamically

X.25

Used only for switched incoming calls.
are

follows:

INCOMING

that

type

The

circuits

are

usage

circult.

node.

remote

station,

and

switched.

blocking-control

This parameter applies to X.25 circuits that
are
owned
by
the
executor
node.
The value 1ndicates whether or not Routing will
block messages before they are sent over the circuit.
The values
for blocking-control are as follows:
3
|
ENABLED
DISABLED

Perform blocking
No

possible.

blocking.

NUMBER call-number
This parameter
circuits
that
represents the
calls
and
to
integer of one
MAXIMUM

RECALLS

applies

either

incoming

outgoing

are
owned
by
the
executor
node.
Routing full remote DTE address
wused
call out on the circuit.
Call-number
to sixteen digits.

X.25

The
value
to
receive
i1s a decimal

retry-count

This parameter applies to outgoing X.25 circuits that
are
owned
by the executor node.
The value represents the maximum number of
Routing automatic call retries.
Retry-count is a decimal integer
in the range 0-255.
If no value 1s set, there is no maximum.
CHANNEL

channel-number

This

used

parameter
1is

only to
integer
DTE

running

the

Data Link X.25 logical channel
X.25 protocol on the circuit.

permanent
circuits.
in the range 0-4095.

channel-number
-

number to be
This applies

decimal

dte-address

This

parameter is the Data Link X.25 local DTE address
to
which
the
circuit
belongs.
This applies only to permanent circuits.
Dte-address 1s a decimal integer of one to sixteen digits.

Network Management

Seen

the

User

Page

‘,

CONNECTED NODE node-id
This parameter is the read-only Application module identification
of the node on which the DECnet object using the circuit resides.
Node-1id is a
standard
Network
Management
node
identification

(Section

crrcults

3.1).

being

CONNECTED OBJECT

This

parameter

applies only to permanent X.25

used by module X25-SERVER.

object-id

This parameter applies only to permanent X.25 circuits being used
by
module
X25-SERVER.
The
read-only Appiication module wvalue
‘1dentifies the DECnet object using the circuit.
Object-id is
as
described for module X25-SERVER.

3.4.1.5

Ethernet

Circuilt

Ethernet circuits
functions
through
or

LOADER.

DESIGNATED

The

Parameters

support
all
of
the
Network
Management
circuits that are owned by MODULE LOOPER,

following

ROUTER

parameters apply

node-1id

This read-only value is
node that is to be used
the executor node.

LINE

service
CONSOLE,
Ethernet. circuits:

the
for

Routing
routing

layer identification
on circuits that are

of
the
owned by

line-id

This value
1s

is the Data Link layer

used

for

traffic

the

identification of the line that
circuit.

Line-id

line

name

(Section 3.5).
MAXIMUM

ROUTERS

number

This parameter is the maximum number of routers (other
than
the
executor
1tself)
allowed on the circuit by Routing for circuits
that are owned by the executor node.
Number is a decimal integer
in the range 0-255.
ROUTER

PRIORITY

number

ThlS parameter
selection
of

1is the prlorlty that this
de51gnated router for the

are

owned

the

range

0-127.

SERVICE

PHYSICAL

the

executor

The

ADDRESS

node.

default

decimal

integer

1in

64.

ethernet-address

This parameter indicates the

adjacent
parameter

Number

value

router is to have 1n the
circuit on circuits that

node
that
1is
1s a qualifier

Ethernet

thsical

being
serviced
on this
for SERVICE SUBSTATE.

address

circuit.

This

Page 48

Network Management as Seen by the User
SUBSTATE

SERVICE

This is the <circuit's read-only Network Management substate
It identifies the kind of serwvice being performed
(Section 3.6).
This parameter is qualified by SERVICE

on the circuit.

PHYSICAL

ADDRESS.

Circuit Counters

Network Management displays or zeroes counters as
executor

node

(Routing)

Management counter
Seconds

since

is kept

last

owns

the

«circuit.

for circuits:

when

the

permanent

X.25

group

Tne following Network

zeroed

3.4.2

The following Routing counters are kept for all circuits:
Terminating packets received
Originating packets sent
Terminating congestion loss
Transit packets received
Transit packets sent
Transit congestion loss
Circult down
Adjacency down
Initialization failure

The following Data Link counters are kept for DDCMP circuits:
Bytes

received

Bytes

sent

Data blocks

received

Data

sent

blocks

Data errors 1nbound
Data errors outbound
Remote reply timeouts
Local reply timeouts
Remote

Local

buffer errors
buffer errors

Selection intervals elapsed
Selection timeouts

The following Routing counter is kept for X.25 circuits:
Corruption

loss

The following Data
circuilt:

Bytes

received

Bytes

sent

Link

Data blocks

received

Data

sent

blocks

counters

are
|

kept

for a

Network Management as Seen by the User

Page 489

" Locally initiated resets

Remotely initiated resets
Network initiated resets

The following Data Link counters are kept for Ethernet circuits:
Bytes

received

Bytes

sent

Data blocks

received

Data blocks

sent

User buffer unavailable

Lines

3.5

Lines

are

- physical

the

lowest

communications.

level

communications

Lines

are

the

path.

Lines

provide

media over which circuits

operate.

The Data Link
A line is identified individually with a line name.
1line names and ensures their
1list of
layer contains the master
uniqueness.
Group

line

A line name

is an

identifications are

ACTIVE LINES - All
KNOWN LINES

All

Many' line parameters,

follows:

lines that
lines

that

are
have

in the ON or SERVICE state.
a name.

known

lines

that

counters,

and

events

SIGNIFICANT LINES - All
parameter,

1id-string.

have

least

one

the

depend

There are
being used for a particular line.
protocol
communications
for
1s
DDCMP
DDCMP, LAPB, and Ethernet.
currently three protocols:
" DECnet communications.
LAPB is for DECnet and/or X.25 communications.
Ethernet

for DECnet or Ethernet communications.

Line Parameters

3.5.1

There are five groups‘of line pafameters:
1.

Common line parameters (Section 3.5.1.1)

2. Non-Ethernet line parameters (Section 3.5.1.2)‘
3. DDCMP line parametérs (Section 3.5.1.3)
4.

LAPB line parameters

(Section 3.5.1.4)

Network Management as Seen by the User

Page 50

Ethernet line parameters (Section 3.5.1.5)

3.5.1.1
The

Common

following

COUNTER

Line

“)

Parameters

parameters

TIMER

are

common

all

lines:

seconds

This
value. represents the
Network
Management
timer
whose
explration
causes
a
line
counter logging event.
The counters
logged depend on the line protocol and are
described
elsewhere.
The
1line
counters
are
recorded as data in a logging event and
then zeroed.
1If no
counter
timer
value
1is
set,
the
line's
counters
are
not
automatically
logged.
Seconds 1s
a decimal
integer in the range 1-65535.

N
)
’

DEVICE device-specification
This

value

- line.

represents

the

Physical Link

device

A device-specification contains
the

dev

A device mnemonic

(Table 10,

A controller number

A unit

used

Section

the

device

the

7.4)

)

number

These fields represent the actual local hardware
for the
If

following:

not

is not allowed.
The
following format:

a multiple

line

controller,

device-specification

the

unit

id-string

device.
number

the

dev-c
or

dev-c-u
PROTOCOL

protocol-name

This value represents the Data Link protocol to be
line.

The

protocol-name

values

are

follows:

DDCMP CONTROL
This

line

group.

which has

|
is
It

the
can

control
be

the

station
line

unique physical

for

DDCMP

multiple

tributary

DDCMP DMC
This

DMC

emulator

node.

multipoint

circuits,

each

address.

|
line

used

Network Management as Seen by the User
DDCMP

POINT

This line 1s one end of a point-to—point
It

DDCMP

Page 51

can be

the

line

for only one circuilt.

DDCMP

connection.

TRIBUTARY

This line is a tributary end of a
DDCMP
It can be the line for only one circult.

multipoint

group.

LAPB

This line uses the X.25 level 2 protocol and can be
for

the X25-PROTOCOL module.

line

ETHERNET

RECEIVE

This

line uses

BUFFERS

number

the Ethernet protocol

for

the Ethernet.

This value represents the number of receive buffers reserved
the line.
It is a decimal number 1n the range :1-65535.

for

STATE line-state

This value represents Network

Management

described in the state and substate model

operational

state

in Section 3.6.

Substate

‘\‘\\n—//’

This value represents the
1line's
read-only
substate as'described
in Section 3.6.

3.5.1.2

Network

Management

Non-Ethernet Line Parameters

The following parameters are common to all non-Ethernet lines:
CLOCK

clock-mode

This value represents the Physical Link hardware clock
the

line device.

INTERNAL

for clock-mode are:

mode

for

For software controllable loopback use
of
the
clock.
those devices that can support this mode, 1t causes
On
all
that
such
signal
clock
a
the device to supply
be looped back from outside
can
transmitted messages
This may require manual intervention other
the device.
than the setting of this parameter value.
For example,
1in°
loopback plug
a
the operator may have to connect
place of

EXTERNAL

The values

the normal

line.

For normal clock operating mode,

where the clock signal

Network

Management

1s
CONTROLLER

Seen

supplied

the

User

externally

Page

the

controller.

controller-mode

This value represents the Physical Link hardware controller
for

the

line

LOOPBACK

device.

The

For

software

those

values

for

controllable

devices

that

can

controller-mode
loopback

support

this

the

mode

are:
controller.

mode,

causes

all transmitted messages to be looped nack from
within
the
controller
1tself.
This 1s accomplished without
any manual intervention other than the setting of
this
parameter
NORMAL

DUPLEX

‘For

value.

normal

controller

operating

mode.

duplex-mode

This value represents
the line device.
The
FULL

Full-duplex

HALF

Half-duplex

RETRANSMIT

the Physical Link hardware
possible modes are:

duplex

mode

TIMER milliseconds

This value represents
retransmits
a block

the
on

amount of time
the
1line.
On

parameter is the select timer.
in
the
range
1-65535.
If

before
the
half-duplex

Data
lines,

Milliseconds is a decimal
not
set,
the
default is

Link
this

integer
3000 (3

seconds)
.

3.5.1.3

DDCMP

Line

Parameters

DDCMP lines support the Network Management‘service functions of
load,

and

applies

active

DDCMP

and

passive

line

loopback.

The

following

dump,

parameter

lines:

SERVICE,TIMER milliseconds

This value represents the amount
a
Data
Link
receive
request
operations.
Milliseconds is
a
1-65535.
-

of time allowed to elapse before
completes
while
doing
service
decimal
1integer
in
the
range

‘The following parameters apply to DDCMP CONTROL lines:
DEAD

TIMER milliseconds

This value represents the number of milliseconds between polls of
one
of
the
set of dead tributaries.
Milliseconds is a decimal
integer in the range 1-65535.
1If not set, the default
1is
10000

Page 53

Network Management as Seen by the User
(10 seconds).
DELAY TIMER milliseconds

This value represents the minimum number of milliseconds to delay
The delay timer limits the effect of a very fast
between polls.

control station on slow tributaries.
integer in the range 1-65535.

Milliseconds is

If not set,

decimal

there 1is no delay.

SCHEDULING TIMER milliseconds

This

wvalue

represents

number

the

milliseconds

between

Milliseconds is a
recalculation of tributary polling priorities.
the default
set,
not
If
decimal integer in the range 50-65535.
is

200.

STREAM TIMER milliseconds

This value represents the number of milliseconds a tributary or a
line.
allowed to hold the
is
station
remote
duplex
half
not
If
0-65535.
range
the
in
integer
Milliseconds is a decimal
seconds).
set, the default is 6000 (6
NOTE

half-duplex

3.5.1.4

lines of

be applied

can also
This parameter

type DDCMP POINT.

LAPB Line Parameters

LAPB lines support the Network Management service function of active
the LAPB
following parameters apply to 1lines wusing
The
loop.
~

protocol:

HOLDBACK TIMER milliseconds
This

parameter

acknowledgment

defines

can

the

length

held back

time

wait

for

Data

chance

Link
to

If no value is set, no holdback 18
piggy-back on a data message.
integer in the range 1-65535.
decimal
a
is
Milliseconds
allowed.
MAXIMUM BLOCK byte-count

the

size on
This value represents the Data Link maximum block
1-65535.
range
the
in
integer
decimal
a
is
Byte-count
line.
MAXIMUM RETRANSMITS block-count

This value represents the maximum number of Data Link retransmits
1If no value is set, there is no maximum.
of a block on the line.
Block-count is a decimal integer in the range 1-255.

Network Management as Seen by'the User
MAXIMUM WINDOW

Page 54

block-count

This
value
represents
the
Data
Link
unacknowledged
transmitted blocks on the
decimal integer in the range 1-255.
SERVICE

max lmum
number
line.
Block ccunt

of
a

service-control

This value

indicates whether or not

operations
the line.

(loading,
dumping, loopback testing) are
The service-control values are as follows:

Network

Management

service

alliowed

ENABLED

SERVICE state and/or service functions are allocwed.

DISABLED

SERVICE

3.5.1.5

Ethernet

Ethernet
1lines
functions.
The

Line

state

and/or

service

functions

are

for

not

allowed.

support
any
Network
Management
parameters apply to lines using the

service
Ethernet

Parameters

do
not
following

protocol:
HARDWARE

ADDRESS ethernet-address

" This read-only parameter is
the line device hardware.

3.5.2

Line

Network management

- The

Ethernet

address

associated

1line as
to LAPB

Management

displays

or zeroes

line

counters

pertaining

counter

kept

Seconds

since

last

zeroed

following

Data

Link

counters

following

Data

Bytes

received

Bytes

sent

Link

counters

Data

blocks

received

Data

blocks

sent

Data

errors

inbound

Data

errors

outbound

Remote

Local

a group.
Some line counters are specific
to DDCMP
lines, and some to Ethernet lines.
The
following
for

lines:

are

kept

for

DDCMP

are

kept

for

lines:

Remote station errors
Local station errors

The

with

Counters

particular
lines, some
Network

the

timeouts
timeouts

LAPB

line:

Network Management

Seen

the

User

Page

Remote buffer errors
Local buffer errors
Remote process errors
Local process errors

The fdllowing Data Link counters are kept for an Ethernet l:ine:
Bytes

received

Bytes

sent

"Data blocks received
Data blocks sent
Multicast bytes received
Multicast data blocks received
Data blocks sent, initially deferred
Data blocks sent, single collision
Data blocks sent, multiple collisions
Send failure
|
|
Collision detect check failure
Receive faillure

Unrecognized frame destination
Data

overrun

System buffer unavailable
User buffer unavaillable

3.6

Circuit and Line State and Substate Model

This section describes
the
Network
Management
state
and
substate
model.
This model
applies
to both circuits and lines, referred to
generically as links.
There
1s
one
model
for
the
relationships
between the states and substates.
This model 1is applied independently
to both circuits and lines.
In other words, all
of
the
states
and
substates
that
apply
to circuits apply equally and independently to
lines.
Note that this 1s an architectural model and the functions and
states
that
can be applied to a particular circuit or line will vary
depending upon the Data Link protocol and the actual implementation.
In the following discussion of the model, the term
1link
is
wused
include
eilther
circult or line.
This Network Management function
called Data Link Service
ito include both circuits and lines.

to
1is

There are three internal state machines that are of interest, one each
for
the
high
1level
wuser's
1internal
view of a link, the Data Link
protocol's exhibited view of a link, and the Network
Management
Data
Link Service view of a link.
These state machines are first presented
independently.
They are then
related
to
one
another
through
the
externally visible states and substates.
The
purpose
o0f
these
state
machines
1s
to
define
+the
Network
Management
abstractions
for
the
operation
of
1links.
These
abstractions can represent any high level user or low level Data Link,
within
the
bounds of the functions actually provided by that module.
A mapping of the Network Management
1link
state
machines
to
actual
internal states of other architectural components is in Appendix C.

Network Management

as Seen by

the User

Page

Operation
of
various
algorithms
on
<circuits
and
1lines
differs
according to how maintenance traffic is handled within theilir data link
protocol.
In
some
data
1link
protocols
(i.e.
DDCMP
and
LAPB)
maintenance
traffic
1is
exclusive
of normal traffic and vice versa.
The

1ink

(i.e.

1s either

in normal mode

Ethernet)

maintenance

traffic

maintenance

1is

mode.

others

completely independent of

normal traffic and thus can occur concurrently.
Whenever this makes a
difference
in
the
remainder
of
this
specification, these will be
referred to as exclusive maintenance or concurrent maintenance
links,
respectively.

3.6.1

High Level

Link User States

In the case of a circuit, the high level user is
either
the
<circuit
owner
for
a
circuit
that
has
an owner or the current user for an
opened circuilt that
does not have an owner.
For
a
line,
the
high
level
wuser
1s
the
Data
Link
protocol
module.
The state machine
presented here models the Network Management view of
the
high
level
user.
The
wuser's
internal operation may actually be different, but
Network Management must be able to view it
essentially
according
to
this model.

The high level user
four

internally considers

states:

the

link as being

the

link

Off

Start -

is not

the

link is

Fail --

the

link startup process

state may not

Run

the

exist

link

one

to be used.

to be

being

1nitialized.

failed

permanently.

includes
both
the
1low
level
going
to
initialization needed by the high level.

in some
in

normal

high

level

running

run

users.,.

state.

Figure 3 shows the states and the allowed transitions.

state

and

This

any

This

Network

Management

|
|
|

OFF

Seen

<mmmmmmmmm
e|
|
|

|
|
|
|

A\
|

FAIL

Page

|
|
|

RUN

N
N
\
N
NAVARRR

—_————e>
——
e
———

bt >|

START

I<=:==::===::'

Network

Management

====>

Protocol

Operation

®igure

Level

High

defines

Network

the

Command

Link

state

Management

User

State

transitions

commands

are

Diagram

and

the

represented

events

that

phrase

the

state" where state 1s the controllable state.
A hyphen
change of state, N/A indicates Not Allowed (impossible).
|

High

Event

Level

Link

Old State

them.
STATE

indicates

Transitions

and Their

Causes

- Fail

Run

SET STATE OFF

;

Off

Ooff

‘Off

SET

Start

SET STATE SERVICE

Of f

Off

Startup

N/A

Run

N/A

*Fail

N/A

Start-

successful

Lower level left'run state
|

"SET

Start

Startup failed

)

Table

State

cause

Off .

STATE

This

-——->

User

Y e '

Tanle

the

e .

________

transition

takes place according

not at all if not supported by the user.

the

user's

algorithms

Network Management

3.6.2

as Seen by the User

Page

Data Link States

The Data Link states are those exhibited for any
higher
1level
user.
The actual internal states may differ according to the particular Data
Link protocol, but Network Management and the high level user must
be
~able to perceive them as described here.

Data Link exhibits the link as being in one of four states.
In
this
context,
Data
Link means a lower level perception of the link, since
in the
Link.

case of a line the high level user 1s
the low level Data Link states are:
link

Synch --

Maint -- the link is to be
wused
for
maintenance purposes.
This state only applies to exclusive maintenance links.

Run -- the

link

i1s

not

Data

the

Off

shows

the

part

Figure 4

actually

to be used.

to be or

1n normal

the states and the

is being

running

initialized.

state.

allowed transitions.

Network

Management

—

——

ct—

—

Seen

——

—

——

the

—

User

—

——

—

——

—

——

TT =

OFF

.m=>

e--->|

. 0000000000 —> |

~——='

T T == '———o
| <+++++++++,

SYNCH

o
|
0
|
o

|
|
|
|
|
|
|

I
|
o
+
0
|
o
o+
|
|
|
o
v
0
|
|
.- —m—O————,
o)
|
|
<-00000000"
|
RS
| €mmmm
e|
|
|
MAINT
|

oo |

o
e
0

|
|

+
+

+
4+

v
o+
S +--—,

|
|
|
|
1

--—>

Network

oo->

Network Management

+++>

Protocol

Figure 4.

Management

Command

Operation

Data Link State Diagram

| ——-

|
|

RUN

+
4+
..

]

|
|
|

+Httttt,

t———0———,———"

w—

\.\\\_//

—

v
TT T T .

———

v
«

—

Page

T Tk T F T uE

Page 60

Network Management as Seen by the User

Table 2 defines the Data Link state transitions and

events

the

that

Network Management commands are represented by the phrase
cause them.
A hyphen
state.
controllable
"SET STATE state" where state 1s the

indicates no change of state, N/A indicates Not Allowed (impossible).
2

Run

Off

Synch

Maint

Off

~ Synch

Synch

Maint

N/A

- Synch

N/A

Maint

Data Link Service close

N/A

N/A 4 |

**Synch

N/A

Maintenance message received

N/A

Maint

Synchronizatidn‘successful

N/A

Run

N/A

Synch

Event

Old State

SET STATE OFF
SET STATE ON

Maint

SET STATE SERVICE

*Set state ON-AUTOSERVICE B N/A
*Reset ON—AUTOSERVICE state
|

Data Link Service open

Synchronization lost
*

Table

Data Link State Transitions and Their Causes

Maint

N/A

Controllable states for Link Watcher only.

** Tf controllable state in ON, otherwise no change.

3.6.3

Network Management Data Link Service States

Network Management Data Link Service is the arbiter
of
1link
states,
Network
Dby
required
as
relationships
proper
the
maintaining
Data Link service maintains its own internal states for a
Management.
link according to the following description.
|

This discussion is directed only
at
exclusive maintenance
1links.
Concurrent maintenance
links
are
either
on
or off, regardless of
all
Furthermore,
traffic.
whether they carry normal or maintenance
the 1link maintenance
handled by
are
functions
their maintenance
modules,
which
are
dedicated
to
the processing
of
maintenance
functions on- the

links

that

they own.

Network Management Data Link Service perceives the link

being

1in

Network Management

one

seven

Off

as Seen

the User

Page

states:

the

link

not

to be

Passive -- the link is in

used.

use

by its

user

and

monitored by Network Management Data Link Service.

Passive open -- the link
1is
temporarily
1in
wuse
for
Network Management operation such as down-line load and
return

being
some
1s to

its user when done.

Reflecting -- the link is reflecting loopback messages and is
to

return

its user when done.

Closed -- the link is reserved for
operation.

Open'fé the
operation.

1link

open

for

some

Network

Management

Network

Management

Closed reflecting -- the link is reflecting loopback messages
but

reserved

for

some

Network Management operation on

demand.

Figure

shows

the states and the

allowed transitions.

Network

Management

Seen

the

User

Page

T> |

OFF

<=~

|<-—-—-—— .

|
.—>|
| <-.
|
|
. eo
|
|
|
|
|
|
|
|
]
|
[T —— e S
T

PASSIVE

|<ooo0o00]|

|
]

OPEN

|ooocoo>|

|
|

A
o
o

|<------ |

|
|

REFL.

Y e

| 0c0000> |

/\
/1IN
| |

| |

OPEN

|
|

e e
__ v

| |
1/
\/

oo ————====,

| =====|
|

| - >|
| <
1
!

CLOSED

REFL

A
0
0
0O

| 00

| ————|

-—-—->

Network

Management

Command

ooo>

Network

Management

Operation

===>

Protocol

Operation

|
|
|
|
R
—.

|
===,

|=====""

_________

Figure

CLOSED

/\
/11N
Il

e |
|

PASSIVE

Y e e

| |
N1/
\/

| -————- > |

|
o====|

|
|
|

| <o0000 |

Network Management

Data

Link

Service

State

Diagram

Table 3 defines the state transitions and the events that cause
them.
Network
Management
commands are represented by the phrase "SET STATE
state" where state 1s the controllable state.
A hyphen
indicates
no
change of state, N/A indicates Not Allowed (i.e., impossible).

Data

Link

Table

Service

State

Transitions

and

Their

Causes

Pass

Clos

Event

Off

Pass

Open

Refl

Clos

Open

Refl

SET STATE OFF

Off

SET

Pass

| Pass

Pass Refl

STATE

Network Management

Seen

SET STATE SERVICE

Clos

Data Link Service open

N/A-

the

User

Page

Clos

Pass

N/A

Open

Clos

Refl

Pass

Open

N/A

Open

Data Link Service close

N/A

Pass

N/A

Clos N/A

Loop message received

N/A

Refl

N/A

Clos

N/A

Communication

N/A

Pass

N/A

Clos

failure

Refl

Or non-maint message
received

) .6.4

Controllable

and Observable

This section shows the

‘defined
that

state

can be

There

are

four

States

relationships

machines,

between

the

three

previously

and relates them to the states and substates

controlled and observed
link

and Substates

states

that

through Network Management.

can

controlled

through

Network

Management.

)

CLEARED -- Some space 1s reserved for the link, but no

other

data
bases or parameters for the link are present.
The link
cannot be used in any way.
If they exist,
all
three state

machines

are

the

off

state.

OFF -- The link data bases and parameters

are

present,

ON -- The

use,

with

link

the

1s avalilable

exception of

high

level

user

temporary overrides

for

There
>

normal

service

functions.
The high level user is
1in
any
state
but
Data
Link
1is in any state but off.
Data Link Service
passive, passive open, or reflecting state.

Dbut

the
1link 1s not to be used by any network or network-related
software.
The link 1s functionally non-existent.
All
three
state machines are in the off state.

off.
1s 1n

the
SERVICE -- The
1link
1s
reserved
for
active
service
functions:
load,
dump,
and
loop.
The
1link can provide
passive loop if no active service function
1s
1n
progress.
The high level user is in the off state.
Data Link is in the
maint state.
Data Link Service 1is 1in the
closed,
open,
or
- closed
reflecting
state.
This
state
does
not
apply to
concurrent maintenance links.
|

1is one additional

state

that

<can

requested

the

Link

Watcher:

ON-AUTOSERVICE -- The
functions.
service

link is temporarily reserved for the active
It is to be returned to its high level user

Network Management as Seen by the User

Page 64

when the Link Watcher is done.
The high level user 1s 1n the off
state.
Data Link is in the maint state.
Data Link Service 1is 1n
the closed state.
This
state
does
not
apply
to
concurrent
maintenance

links.

There are fourteen substates that
can
be
observed
through
Network
Management.
These substates apply to the ON and SERVICE states unless
otherwise noted.
OFF and CLEARED do not
have
substates.
The
only

substates

that

apply to

concurrent maintenance links

FAILED.

are

running

and

Running -- The link is 1in normal
This 1s the default substate of
Data Link are in the run state.
passive state.

Idle -- The link is not being used for anything.
This 1s the
default
substate
of SERVICE.
The high level user 1s 1in the
off state.
Data Link is
1in
the
maint
state.
Data
Link
Service

the

closed

use by i1ts high level
user.
ON.
The high level user and
Data Link Service is 1in
the

state.

SYNCHRONIZING -- The link is engaged in low level
Data
Link
synchronization.
This
1s a substate of ON.
The high level
user 1s in the start state.
Data Link 1s 1n any state except
run or off. Data Link Service is in the passive state.

STARTING -- The link 1s synchronized and is 1in 1ts high level
user's
startup cycle.
This 1s a substate of ON.
The high
level user is in the start state.
Data Link 1s
1n
the
run
state.
Data Link Service 1s in the passive state.

FAILED -- The link permanently failed its high level

startup
cycle.
This
1s a substate of ON.
The high
user 1s 1in the fail state.
Data Link 1s 1n any state.
Link Service is in the passive state.

user's

level
Data

REFLECTING -- The link is engaged in passive
loopback.
The
high
level
wuser is in the off or start state.
Data Link 1s
in the maint state.
Data Link Service 1s in
the
reflecting
or closed reflecting state.
~

LOADING -- The link 1s engaged in down-line load.

DUMPING -- The link is engaged in
up-line
dump.
The
high
level
wuser
1s
1in the off state.
Data Link i1s in the maint
state.
Data Link Service 1s 1n the open state.

LOOPING -- The link is engaged in active loopback.

level
state.

wuser
Data

level wuser
state.
Data

1s
1in the off state.
Link Service 1s in the

1s
in the off state.
Link Service 1s in the

Data
open

Link 1s
state.

Link is
state.

1in

The
the

The

high

maint

high

the maint

Network Management as Seen by the User
10.

- Page 65

TRIGGERING

-- The link 1s engaged
1in
a
The high level user is in the off state.
maint state.
Data Link Service is in the

11.

down-line

Data
open

trigger.
Link is in the
state.

AUTOSERVICE

-- The link 1s reserved
for
Link
Watcher
This
appears as a substate of ON.
The high level user
the off state.
Data Link 1s 1in the maint state.
Data
Service 1s 1n the closed state.

12.

|use.
is in
Link

AUTOLOADING

-- The link 1s engaged in down-line load for
the
Link Watcher.
This
appears as a substate of ON.
The high
level user 1s in the off state.
Data Link is
in
the
maint
state.
Data Link Service 1is in the open state.

13.

AUTODUMPING

14.
-~

AUTOTRIGGERING -- The link is engaged in a down-line
trigger
for the Link Watcher.
This appears as a substate of ON.
The
high level user 1s 1n the off state.
Data
Link
1is
in
the
maint state.
Data Link Service is in the open state.

3.7

-- The link 1s engaged in up-line
dump
for
the
Link
Watcher.
This
appears as a substate of ON.
The high
level user 1s 1n the off state.
Data Link is
in
the
maint
state.
Data Link Service is in the open state.

Modules

are

components

that

not

fit

1nto

the

other

entity

classifications.
Module identification is a module name.
The Network
Management layer contains the master list of module names and
ensures
their
uniqueness.
A module name is an id-string.
Since module names
are
predefined
by
Network
Management,
they can
be
abbreviated
according to the same rules applied to keywords (Section 4.2.4).

3.7.1

X;25,Access Module

The name of the X.25 access module 1s X25-ACCESS.
The access module data base
contains
the
information
necessary
to
connect to the X.25 Server for one or more networks.
This information
1s 1ndexed by network name.
Functions that reference this
data
base
must
1ndicate
to
which network name they apply, except for the case
where only one network name 1s defined.
The user

can

add

and

remove

network

can
also
modify
parameters
for
Management can display information
network

The

name

network

name

all

names

and

parameters.

a
network name
about the
X.25

known network names.

parameter

formats

are

follows:

The

user

or names.
Network
access
module
by

Network Management

as Seen by the User

Page

KNOWN NETWORKS
All,Of the network names known to -the access module.
NETWORK

network-name

The name of a specific network for the access module.
name

1id-string.

Each network name
1s
associated
with
a
optionally,
access
control
information.
network

name

are

network

node
The

1i1dentification
and,
parameters
kept
by

field

value.

follows:

ACCOUNT account

This is the access

control

account

The

access

routines
use
this
wvalue
when connecting to the server.
If no
account 1s set, none 1is 1included in the access control on connect
by
the
access
module.
Account
1s
a
string
of
one
to 39
characters.
|
|
|

NODE

node-1d

The identification of the node
in
connecting
to
a
server.
Management node identification
PASSWORD

to be used by the
Node-1id
1s
a
(Section 3.1).

access
routines
standard Network

password

The access control password field value to be used by the
routines
in
connecting
to
the server.
If no password
none 1s included in the access control on connect by
the
module.
Password 1s a string of one to 39 characters.
USER

user

The access control user field value to
be
wused
routines in connecting to the server.
If no user
included in the access control on connect by the
User is a string of one to 39 characters.

3.7.2

The

access
1s set,
access
|

X.25

name

Protocol

Module

the

protocol

X.25

module

by
the
access
is set, none 1s
access
module.

X25-PROTOCOL.

The protocol module data base contains the
1information
necessary
to
maintain switched and permanent virtual circuits through a public data
network over its assigned X.25 lines.
Most
of
this
1information
1is
indexed
by
the
1local
DTE addresses.
Functions that reference this
data base must indicate to which DTE address they
apply,
except
for
the case where only one local DTE address is defined.

The user can add and remove local DTE addresses and

parameters;

The

Network Management

Seen

the

User

Page

user
can also modify parameters for a local DTE address or addresses.
Network Management can display
information
from
the
X.25
protocol
module
data
base
by
1local
DTE
address or for all known local DTE

addresses.

Closed user group information is indexed
by
group
name.
Functions
that"
reference
this
part
of
the
protocol
module
data base must
indicate to which group they apply.
Groups can be added and
removed,
along
with
their
parameters.
Information can be requested by group
name

for

all

known

There are also
independent

3.7.2.1

The

groups.

protocol
local

module

DTE

X.25 Protocol

local DTE address

counters

and

addresses.

Module

parameters

that

are

Parameters

independent protocol module

parameters

are

follows:
CALL

TIMER

seconds

This value indicates the maximum elapsed seconds before the
X.25
protocol
module
will
send
a
<clear on outgoing calls from the
local DTE for which no response has been received.
If
no
timer
1s
set, there 1s no clear sent.
Seconds is a decimal integer in
the range 1-255,
|
CLEAR

TIMER

seconds

This.is the retransmit timer for outgoing clear packets from
local
DTE.
Seconds 1s a

DEFAULT

DATA

If
no
decimal

Byte-count
WINDOW

This

MAXIMUM

the default

data

integer

the

blocks

integer

the

retransmission.

size

the

for
range

switched

«circuits.

1-65535.

on
the

default

range

switched

number

<circuit.

unacknowledged

Block-count

1-255.

byte-count

This parameter
Byte-count
- MAXIMUM CLEARS

a decimal

parameter

DATA

set, there 1s no
the range 1-255.

block-count

transmitted

decimal

1s
in

byte-count

This parameter

DEFAULT

timer
integer

This value
handler 1s

1is

the

decimal

maximum

integer

data
the

size

range

for

all

1-65535.

«circuilts.

retry-count

is
to

the maximum number of times that
retry the sending of a clear for

the X.25
switched

protocol
circuits.

Network Management

as Seen by the User

If no value is set,

decimal
MAXIMUM

integer

RESETS

there

in the

range

1is

1-255.

maxilmum.

Page

Retry-count

retry-count

This value is the maximum number of times that the X.25
protocol
handler
1is
to retry
the sending of a reset.
If no maximum 1s
set, there is no maximum.
Retry-count
is a
decimal
1nteger
1in
the range 1-255.
|
|
”
MAXIMUM

RESTARTS

retry-count

This value is the maximum number of times that the X.25
protocol
handler
1is
to retry the sending of a restart.
If no maximum 1S

set,
the

there

range

is no maximum.

Retry-count

is a

decimal

1integer

1-255.

MAXIMUM WINDOW block-count

This value
blocks
on
in
NETWORK

the

is the maximum number
of
unacknowledged
transmitted
a switched circuit.
Block count is a decimal 1integer

range

1-255.

network-name

This

network name value

can be

used by

the

X.25

protocol

handler

to
determine network specific characteristics and values.
It
also used as the network name for outgoing and incoming calls.

The network-name
is an id string.
RESET TIMER

seconds

This parameter is the retransmit timer for outgoing reset packets
from
the
local
DTE.
If
no
timer
1s
set,
‘there.
1s
no
retransmission.
Seconds is a decimal integer 1in the range 1-255.
RESTART TIMER

seconds

This parameter is

the

retransmit timer

for

packets
from
the
local
DTE.
If no timer
retransmission.
Seconds 1s
a decimal integer

1s
1n

outgoing

restart

set, there 1s no
the range 1-255.

To access the local DTE indexed parameters,
a local DTE

address

must

be
specified
or assumed.
A local DTE address can only be assumed
only one is known.
The local DTE address parameter 1s as follows:

KNOWN

DTES

This parameter refers
the protocol module.

all

the

local

DTE

addresses

known

DTE dte—-address

This parameter represents a particular local DTE address for

the

Network Management as Seen by the User

protocol module.
to

A local DTE address
is a decimal

Page 69

integer of one

sixteen digits.

Each local DTE address is to be associated with the information needed
to process

The

the virtual

parameters

ACTIVE

kept

CHANNELS

circuits associated with that
local

DTE

address

are

local DTE.

follows:

count

This read-only value is the number of
switched
wvirtual
circuit
logical channel numbers that are currently in use.
These are the
channels specifically defined with the
channels
parameter
(see
below).
Active channels include those allocated from the channel
list for either outgoing or incoming switched virtual circuits.

ACTIVE SWITCHED circult-count
This read-only value is the number of currently
active
switched
circuits.
This is the total number of switched virtual circuilts
active.
It includes both those that were included in the
active
channels
count plus
any incoming calls that did not use one of
the channels

the

channel

list.

CHANNELS list

This parameter

is the list of logical channel numbers that can be
used for outgoing calls or possibly taken by incoming calls.

List is one or more logical channel
numbers.
Multiple
channel
numbers
are separated with hyphens to indicate ranges and commas
to indicate individual numbers.
The order of the numbers in
the
list
defines
the order in which the logical channel numbers are

" to be allocated by the protocol module.
For

example,

the

command

SET MODULE X25-PROTOCOL CHANNELS

20-10,8,3

Sets 20 as the first channel number to use,
there to

“

COUNTER

TIMER

10,

then 8,

and

finally 3.

counting» down

from

seconds

This parameter is the Network Management timer

whose

expiration

causes
a
module counter logging event. The module counters are
recorded as data in a logging
event
and
then
=zeroed.
If
no

counter

timer

1is set,

the module counters are not automatically

logged.

Seconds

is a decimal

integer

in the range 1-65535.

LINE line-1d
This value representsa LAPB line to be used by the X.25 protocol

Network Management

as Seen by

the User

Page

module.

MAXIMUM CHANNELS count

This value 1s the read-only number of logical channels.defined.
MAXIMUM

CIRCUITS

count

This 1s the
parameter
that
1indicates
the
maximum
number
of
circuits
that
the DTE can open at one time.
This includes both
outgoing and incoming calls.
Incoming calls can be given logical
channel
numbers outside the given channels list.
The count 1is a
decimal integer in the range 1-65535.
Default is 255.
STATE dte-state

This value represents the operational
possible states are as follows:

state

local

DTE.

The

all.

Any

'ON

The

DTE

1is

allowed

The

local DTE

operate

normally.

OFF

exlsting

1is

virtual

not

allowed

circuits

are

operate

terminated

immediately.

SHUT

The local DTE will
formed.
Existing
the final existing
automatically goes
SUBSTATE

not allow any new virtual circuits to
be
virtual
circuits are undisturbed.
When
virtual
«circuit
terminates,
the state
to OFF.

dte-substate

There are a number of

substates a DTE can be

in while

state.
The
the DCE.

substate

depicts

between

the

The possible

substates

are:

the

link

status
|

UNSYNC

The

link

The

packet

the

DCE

not

the "RUNNING"

state.

SYNC

level

RUNNING

Normal

operation.

has

initiated

RESTART

for

the

DTE.

in ON

DTE

and

Network Management

The

group name

KNOWN

Seen

parameter

the

User

Page

follows:

GROUPS

This represents all of
protocol
GROUP

the

<closed

user

groups

known

module.

the

group-name

This i1ndicates a partlcular
module.
A group-name is an

Each group name
the

group

The

parameters

DTE

dte-address

1is

through

to be
the

kept

associated with the

X.25

closed user
id string.

group

for

information

the

protocol

needed

use

network.

group

name

are

follows:

This value represents the local DTE address to
which
the
group
number
belongs.
When setting this value, 1t must be accompanied
by a group number parameter.
Dte-address is a decimal integer of
1l

digits.

NUMBER group-number

This is the closed user group number.
1t
1s

TYPE

this

value,

Group—-number

group-type

This 1s the 'closed user group type.
is BILATERAL.

3.7.2.2
These

When setting

must be accompanied by a dte address parameter.
a decimal integer 1n the range 0-9999.

X.25

Protocol

counters

Module

set,

Counters

zeroed

sent

Data blocks

received

Data

sent

Calls

type

are:

Seconds since last
Bytes received
Bytes

blocks

received

Calls sent
Fast selects

received

Fast

sent

selects

Maximum switched circults active
Maximum channels active
Received call resource errors
Locally initiated resets
Remotely 1nitlated resets

The only group type

the group

not

defined

bilateral.

Network

Management

Seen

Network 1nitiated

the

User

module

Page 72

resets

Restarts

3.7.3

The

X.25

name

Server

the

Module

X.25

Server

X25-SERVER.

The server module data base contains the information necessary to
map
incoming
X.25 calls to a DECnet process.
This information is indexed
by destination name.
Functions that reference
this
data
base
must
indicate
to
which
destination
name they apply, except for the case
that there 1s only one destination name defined.
|
Destination
names
can
be
added
and
removed,
along
with
parameters.
Parameters
for
a
destination
name
or
names
modified.
Information can be requested by destination name or
known destination names.

There are also server counters and some
independent

3.7.3.1

X.25

destination

Server

Module

The destination name

server

parameters

their
can be
for all

that

are

names.

Parameters

independent

server

parameters

are

follows:

ACTIVE CIRCUITS count
This 1s the read-only module parameter that indicates
of circuits
that the module currently has open.
COUNTER TIMER

This

module

the

number
|

seconds

the Network Management
counter

logging

event.

timer
The

whose

expiration

module

counters

causes

are

recorded

as data 1n a logging event and then zeroed.
1If no counter
timer
1s
set,
the
module
counters
are
not
automatically
logged.
Seconds 1s a decimal integer in the range 1-65535.
MAXIMUM CIRCUITS

count

This 1s the module parameter that indicates
circuits
that
the module can have open at
decimal integer in the range 1-65535.

The destination name parameter
KNOWN

is as

the maximum number of
one time.
Count is a

follows:

DESTINATIONS

This

refers

module.

all

the

destination

names

known

the

server

Network

Management

Seen

the

User

Page

DESTINATION destination-name

This indicates the name of a specific destination for the

module.

A destination

name

server

id-string.

Each destination name 1s to be
associated
with
a
DECnet
node
and
object
identification and with the necessary X.25 related information
to recognize the incoming call.
The
algorithms
for
incoming
call
recognition are in the X.25 Gateway Access specification.
The

parameters

ACCOUNT

kept

by destination

name

are

follows:

account

This is the
connecting

account
Account
CALL MASK

access
to the

control account field
wvalue
to
DECnet destination of an incoming
value is set, the server will not use one in
1s a string of 1 to 39 characters.

be
wused
call.
If

the

1in
no
connect.

hex-value

This
1is
the
«call
mask
value
to
be
wused
to
1identify
the
destination
for
an incoming call.
If no call mask 1s set, none
will be used in
the
1identification
process.
Hex-value
1s
a
hexadecimal number of 1 to 32 digits.
|
CALL VALUE

This

hex-value

the

destination

<call

for an

will be used in
the
hexadecimal number of
GROUP

data

value

incoming call.

wused

identify

If no call value is set,

1dentification
1 to 32 digits.

process.

Hex-value

the

none
1is

group-name

This is the closed user group name to be
wused
to
1identify
the
‘destination
for an incoming call.
1If no group name 1s set, none
will be used in the identification process.
The group—-name value
1s an 1id string.
\
NODE

node-1id

This is the identification of the node to be used
1in
connecting
to
the
DECnet
destination
of
an incoming call.
Node-id 1s a
- standard Network Management
NUMBER

node

identification.

call-number

This is the full
destination
for
set,
none
will
Call-number
is
asterisks (*).
OBJECT object-1id

remote DTE address to be used
to 1identify
the
an
1incoming call.
If no remote DTE address 1is
be
wused
1n
the
identification
process.
a
string
of
1
to
16
numeric
digits and/or

Network Management as Seen by the User

Page 74

This 1is the object identification to be used in connecting to the
DECnet
destination
of
an incoming call.
Object-id is either a
string of 1 to 16 characters
for
named
objects
or
a
decimal
number
1n
the
range
1-255
for
numbered objects.
If a named
object has a name that looks like a number for a numbered object,
the
name
1s
specified
on input in quotes to indicate that the
object-1d 1s a string rather than a number.
On output
there
1s
no differentiation.
|

PASSWORD password
This

the access

connecting
to
password value

connect.

control password

field value

the DECnet destination of an incoming
1s set,
the
server
will
not use

Password

a string
of 1

wused

1in

call.
1If ro
one
in
the

characters.

PRIORITY priority

This is the priority with which the X.25 set of information is to
be
used.
Priority 1is
SUBADDRESSES

The
highest
priority
1is
255
and the
a decimal integer in the range 0-255.

lowest

1is

range

This 1s the range
of
local DTE
subaddresses
to
be
wused
to
identify
the
destination
for
an
1incoming
call.
If
no
subaddresses
are
set,
none
are used 1n
the
1identification
process.
The range value consists of one or two subaddresses.
A
subaddress 1s a decimal integer in
the
range
0-9999.
If
two
subaddresses are provided, specifying a range, they are separated

by only
a single
first.
USER

hyphen

and

the

second must

greater

than

the

user

This 1s the access
control
wuser
field
wvalue
to
be
wused
1in
connecting to the DECnet destination of an incoming call.
1If no
user value 1s set, the server will not use one
1in
the
connect.
User 1s a string of 1 to 39 characters.

3.7.3.2
These

X.25 Server Module Counters

counters

are:

Seconds since last zeroed
Maximum circuits active
Incoming calls rejected, no resources
Logical links rejected, no resources

Network Management

3.7.4

as Seen by the User

Page 75

LOADER,

CONSCLE,

Link Maintenance Modules

The

names
of

and

CONFIGURATOR.

the

link management modules are LOOPER,

The link maintenance modules provide the network manager with entities
that can own Ethernet circuits for link service functions such as 1ioo0p
testing and down-line load.
Some of the link maintenance modules have
parameters for controlling or observing their operation.
The looper, loader, and console modules are the only link
maintenance
modules that
can
be
CIRCUIT
owners.
They each own one circult on
every Ethernet line that is to have their related service functions.
The configurator module is a user of the services represented
by
the
console
module.
The confiqurator module can provide information from
a single console request
for
system
1identification
or
can listen
through the console and construct a list of the systems on an Ethernet
line.
|

3.7.4.1
The

Console Module Parameter

console module parameter

follows:

RESERVATION TIMER seconds

This value indicates the number of secondsvthat the console will
stay

reserved

Seconds

3.7.4.2

without hearing from the system that reserved it.

is a decimal

Loader Module

integer

1n the

range

1-65535.

Parameter

The loader module parameter 1s as follows:
'ASSISTANCE control
This value indicates whether or not this node will respond to the
dump/load
assistance
multicast address.
The control values are
as

The

ENABLED

The node will

respond.

DISABLED

The

not

3.7.4.3

)

follows:

node will

respond.

Looper Module Parameter

looper module parameter

ASSISTANCE

control

follows:

Network Management as Seen by the User

Page 76

This value indicates whether or not this node will respond
loopback assistance multicast address.
The control values

o the
are as

follows:

ENABLED

The

node

will

respond.

DISABLED

The

node

will

not

3.7.4.4

respond.

Configurator Module Parameters

confiqgurator module parameters
are
qualified
with
identification
of
the
Ethernet
circuit
to which they
circult identification parameter is as follows:
|

parameters

ELAPSED

«c:rcuit
relate.
The
|

circuilt-id

This indicates the circuit
circuit.
Circuit-id is an
The

the

All

"CIRCUIT

TIME

This

kept

circuit

of interest.
id-string.

must

identification

are

Ethernet

follows:

hours:minutes:seconds

read-only value

been
range

enabled
0-65535,

range

0-59.

the amount of

time

that

surveillance

has

on the channel.
Hours 1s a decimal integer :n
minutes and seconds are decimal
integers
in

the
the

SURVEILLANCE control
This value
to be kept

indicates whether
for the circuit.

ENABLED

The

list

kept.

DISABLED

The

list

not

The

default

value

Within a circuit,
system's
follows:
PHYSICAL

kept.

DISABLED.

many parameters

physical

ADDRESS

or not a list of active
systems
1is
The control values are as follows:

address.
|

are

The

further qualified by the

physical
|

address

on
the
circuit.
When used as a qualifier on
1t causes an active request
to
the
console
address and returns the resulting information.

The parameters
SIZE

parameter

remote
1is

ethernet-address

This read-only value is the Ethernet address of a

COMMAND

)

qualified

bytes

physical

address

are

remote

system

a display request,
at
the
specified

follows:

Network Management

Seen

the

User

This read-only value
1is
the
number
of
bytes
1in
system's
console
carrier
protocol
command buffer.
decimal
CONSOLE

USER

This
has

number

1in

the

range

Page

the
remote
By:zes 1s a

1-65535.

ethernet-address

read-only value is the Ethernet
the
remote
system's
console

Ethernet

address

the

word

address of
reserved.

the
It

system
that
1s either an

"NONE".

DATA LINK data-link-type
This

read-only value

on
the
circuit
over
Its values are defined
specification.

the type of data

link protocol be:ng used

which the remote system is commun:cating.
in the DNA Low Level Maintenance Overation

DATA LINK BUFFER SIZE data-link-type

This

read-only value

the size of data

link buffer

being

used

on
the
circuit over
which the remote system is communicating.
Its values are defined in the DNA Low Level Maintenance Overation
specification.
DEVICE device-type

This read-only value is the type of device over which the
system

1is

standard

communicating

line devices.

the

circuit.

remote

one of

the

FUNCTIONS function-list
This read-only value is the list of
maintenance
functions
that
the
remote system supports.
The list of items 1s one or more of
the

following:

BOOT

Remote contfolled boot

CARRIER
COUNTERS
DUMP
LOAD
LOOP
PRIMARY
HARDWARE ADDRESS

Console carrier protocol
Data link counter read
Up-line dump
Multi-block down-line load
Loopback
Primary loader

ethernet-address

This read-only value is the Ethernet address that is attached to
the remote system hardware.
It may be relative to the particular
device through Wthh the remote system is
communicating on
the
circuit.

LAST REPORT day-month hour:minute:second

This read-only value is the date and time of the
remote
system
reported
in
on
a
circuit

1last
that

time
the
1s
under

Network Management

surveillance.

Seen

the

User

Day is a decimal

Page

integer

i1s the name of the month.
Hour 1s a
0-23.
Minute and second are decimal
MAINTENANCE

VERSION

in the range 1-31.

decimal integer
integers in the

Month

in the range
range 0-59.

n.n.n

This read-only value is the maintenance protocol version of
the
remote
system, consisting of the version number, the Engineering

Change Order
3.0.0).
TIMER

number,

and
'

the user ECO number

(for

example,

seconds

This read-only value 1s the maximum time that the remote system's
console
will
remain reserved without a message from tae console
user.
Seconds is a decimal integer in the range 1-65535.

RESPONSE SIZE bytes
This read-only value
1s
the
number
of
bytes
in
system's
console
carrier
protocol response buffer.
decimal number in the range 1-65535,
SYSTEM

PROCESSOR

the
remote
Bytes is a

processor-type

This read-only value 1s the type
system.
Its values are defined
Operation specification.

of main processor on tne
remote
1in the DNA Low Level Maintenance

SOFTWARE IDENTIFICATION software-id
This read-only value

identifies

system

SOFTWARE

3.8

supposed

the

runnlng

software
1s

defined

that

the

same

remote
as

NODE

IDENTIFICATION

Events

Events are
Management

significant occurrences in the DNA layers that the
Network
Event
Logger
records.
This
section
1lists
the events
recorded according to
the
entity
and
layer
with which
they
are

associlated.

Section

3.9 describes

the

event parameters.

Section

5.5

describes the operation of the Event Logger.
Section
6.13
specifies
the
Event
message
binary
data
format.
Section 7.12 specifies the
events.
Section 7.13 specifies the binary formats and values for
the
event

3.8.1

parameters.

Events

Not

Entity

The Event Logger records the following Network Management event.
Event

records

lost

RESERVATION

(ECO)

Network Management

The

Event

Logger

as Seen by the User

Page

records the following Session Control events:

Local node state change

Access
The

Event

control

reject

Logger records the following End Communication events:

Invalid message
Invalid flow control

Node

3.8.2
The

Event

Events

ds Network Management node events:
the following
Logger recor

Automatic counters
Counters zeroed
The

Event
Data

The

Event
Node

3.8.3
The

Logger

following End Communication node event:

the

base reused
Logger

following Routing

records the

reachability

Circuilt

Event

records

node

event:

change

Events

Logger records

the

following

Network

Management

events:

Automatic counters
Automatic service
Counters zeroed
Passive loopback
|
Aborted service request

The Event Logger records
the following Routing circult events:
unreachable packet loss
out-of-range packet loss
Oversized packet loss

Node

Packet

format

error

Partial routing update
Verification reject

loss

Circuit down, circuit fault
Circuilt down
Circuit down, operator initiated
Adjacency down

Adjacency down, operator‘initiated
Circult up
Adjacency up

circuilt

Network Management as Seen by the User |
Initialization

failure,

circuit

Logger

records

the

Page 80

fault

Initialization failure
Initialization failure, operator
Area reachability change
Adjacency rejected

The Event

following

initiated

events

for

DDCMP

circuits:

Locally initiated state change
Remotely 1nitiated state change
Protocol restart received in maintenance mode
Send error threshold
Receive error threshold
Select error threshold
Block

header

Selection
Streaming
Local

- 3.8.4

format

error

address error
tributary

buffer

too

small

Line Events

The Event Logger records the following events for all lines:
Automatic counters
Counters zeroed
Passive loopback
- The

Event Logger

records

the

following

Data

Link

LAPB

line

Data

Link

Ethernet

events:

Locally’initiated state change

Remotely initiated state change
Block header format error
The

Event

Logger

records

the

Initialization failed
Send failed
Collision detect check
Recelve failed
-

The

Event

Data

Logger

records

the

following

line

events:

|
failed

following

set ready transition
Ring indicator transition
Unexpected carrier transition
‘Memory access error
Communications interface error
Performance error

Physical

Link

line

events:

Network Managemeht as Seen by the User
3.8.5

Page 81

Module,Events

The Event Logger records the following Data Link X.25 protocol

module

events:

Restart

State change
Retransmit maximum exceeded
Block header format error

3.9
" This

DTE

down

Event Parameters
section

describes

described in Section 3.8.

the

event

parameters

events

The user cannot directly control or observe

these parameters.,
The
Event
occurrence
of related events,

Logger
if event

records
parameters
upon
the
logging of those parameters 1s

enabled.

There are also events that relate to
counters,
These
counters
those already described for nodes, circuits, lines, and modules.

event
parameters
are
described
1in
alphabetical
order
by
starting with the highest layer that maintailns event parameters.

3.9.1

Network Management

are
The
layer,

Layer

OPERATION

This parameter
‘\\‘v//

following

represents

the

operation

performed,

with

the

values:

INITIATED
TERMINATED

REASON
This parameter

indicates

the

reason the

function

aborted,

with

the following values:
Recelve timeout
Recelve error
Line state change by
Unrecognized request
Line open error

higher

level

SERVICE

This parameter represents the service type,
values:

with

the

following

Network_Management'as Seen by the User

Page 82

LOAD
DUMP

STATUS
This

parameter

the

operation

RETURN ERROR
CODE

status,

consis:ting

of:

ERROR

DETAIL

MESSAGE

where:
RETURN

CODE

standard

NICE

interpretation,

return

code

(Appendix

F),

with

added

follows:

REQUESTED

SUCCESSFUL
FAILED

ERROR

DETAIL

A standard NICE

error detail

(Appendix

F).

ERROR MESSAGE
A standard NICE optional error message (Appendix F).

3.9.2

Session

Control

Layer

ACCOUNT

This value contains any account information in
39
characters.
Account
1nformation 1s used

a string of one to
for access control

purposes.

DESTINATION

PROCESS

This identifies
~Management.

The

OBJECT TYPE

the

process

identification
-

object

connected

consists

type

of:

number.

- GROUP CODE - A group code number.

USER CODE - A user code number.
PROCESS

NAME

process

name.

The SesSion Control specification specifies these values.
NEW

STATE

Network

Network Management as Seen by the User
This

represents

Page 83

the

new node

state,

with

the

following

the

old

state,

with

the

same

values:

OFF
SHUT
RESTRICTED

OLD

STATE

This
NEW

represents
STATE.

node

values

for

PASSWORD

This
1s
the
access
control
password
connecting
to the DECnet destination of
password 1s specified, then none will be
string of 1 to 39 characters.

field
value
used
in
an :zncoming call.
TIf no
used.
Password
1is
a

REASON

This

represents

the

reason

for

the

state

change,

follows:

Operator command
Normal operation
SOURCE

NODE

This 1dentifies the source node, where the source process resides
which
sent the session control protocol message which caused the
event.
The identification consists of a node address followed by
a
node
name.
The
format
1s
the same as for the node entity

(Section 3.1).
SOURCE

PROCESS

This i1dentifies the source process on behalf of which the
source
node
sent
the session control protocol message which caused the
event.
The
1dentification
1s
the
same as
for
DESTINATION
PROCESS.

USER

This

3.9.3

string

End Communication

CURRENT

FLOW

characters

the

user.

Layer.

CONTROL

This is
the
<current
flow control
Communication specification).
MESSAGE

identifying

value

(refer

the

End

Network Management

This

Seen

is the message

consists

the

User

received

(NSP

of:

Page

information only).

The message

MESSAGE FLAGS - NSP messagé flags.
DESTINATION ADDRESS - Destination link address.

SOURCE ADDRESS - Source lifik address.
DATA

Message-type-dependent

SOURCE NODE

data.

This 1s the
source node

1dentity of the node
consists of:
|

SOURCE NODE ADDRESS

Node

sending

address
of

SOURCE NODE NAME - Name of the

'3.9.4

Routing

ADJACENT

tne

ECL

the

message.

source

source node

The

node.

(optional).

Layer

NODE

:This 1s the i1dentification of the adjacent node on the circuit.
HIGHEST

ADDRESS

This

the

highest

reachable

node

address.

NODE

|
This is the
SOURCE NODE

PACKET

of the node, in
Session Control

the
event

same
format
parameters.

BEGINNING

This
PACKET

identification
1n the list of

the

beginning

the

packet.

HEADER

This is the packet header.
of :

For non-Ethernet packets,
|

it consists

MESSAGE FLAGS - Message definition flags.
DESTINATION NODE ADDRESS
node.

The

address

the destination
-

SOURCE NODE ADDRESS - The address of the source nodeQ
VISIT COUNT - The number of nodes the packet has visited.

Network Management as Seen by the User
For

Ethernet

packets,

consists

Page 85
of:

MESSAGE FLAGS - Message definition flags.

DESTINATION AREA - The area number of the destination node.
DESTINATION SUBAREA

The

sub-area

number

the destination

node,

DESTINATION’ETHERNET ADDRESS - The Ethernet address
destination

node.

the

SOURCE AREA
- The area number of the destination node.
SOURCE SUBAREA - The

sub-area

number of

node.
SOURCE

the

destination

ETHERNET

ADDRESS

destination

node.

AREA

ROUTER

The

number

Ethernet

the

address

area

the

router.

VISIT COUNT - The numbér of nodes the packet has visited.
SERVICE

CLASS

The

packet

service

PROTOCOL

TYPE

The protocol

type

REASON

class.
of

the

This 1s the
Table 27 1n
RECEIVED

reason
section

for

failure.

The

packet

contents.

|
values

are

listed

7.13.

VERSION

This is the received version number,
Network

Management

version

(Section

with the same format as
3.1.1).

STATUS

This is the node status, with the following values:
REACHABLE

UNREACHABLE

3.9.5

Data

Link

Layer

BLOCK LENGTH
This
BUFFER

following

LENGTH

the

received block

length

from

header,

bytes.

for

Network Management as Seen by the User
This

is the buffer

length,

Page 86

in bytes.

CAUSE

" This represents the cause for the
X.Z5
protocol
module
event.
For
detailed
explanation of
the
wvalue
see
the
CCITT
X.25
Recommendation.

DIAGNOSTIC

This represents the

diagnostic

for

the

X.25

protocol

module

For detailed explanation of the value see the CCITT X.25

event.

Recommendation.

DISTANCE

is the distance,

This

an Ethernet

to a short or open

in bit times,

line.

cable

DTE

This identifies the DTE associated with the X.25 protocol
event.

ETHERNET

HEADER

This

1is

the

header

destination address,
FAILURE

module

the

Ethernet

source address,

block.

and protocol type.

includes-

REASON

This

is the reason for an Ethernet transmit or receive faillure.

HEADER

" This
NEW

the

block

header

STATE

This

is the new DDCMP state,

with the

following values:

HALTED

ISTRT
ASTRT

RUNNING
MAINTENANCE

' NEW STATE
This represents the X.25 protocol
5.12,

module

with the same values as

new

for the

state

associated

DDCMP NEW STATE.

with event
STATE

This is the old DDCMP state, with the

‘\

OLD

same

values

for

NEW

Network

Management

Seen

the

User

Page

STATE.

OLD

STATE

This 1s the X.25 protocol module old state associated with
5.12,
PARAMETER

with

same

values

for

tne

event

DDCMP NEW STATE.

TYPE

This 1s the
involved in
PREVIOUS

the

Network Management
the event.

parameter

type

the
.

parameter

TRIBUTARY

This 1s the previously Selected triputary address.
REASON

This is the reason for a stéte change.

RECEIVED TRIBUTARY
This
SELECTED

the

received

tributary

address.

TRIBUTARY

This 1s the selectéd tributary address.
TRIBUTARY

STATUS

This is the‘tributary status, with the following values:
Streaming
Continued send after
Continued send after
Ended streaming

3.9.6

Physical Link Layer

DEVICE

NEW

This

than

copy of
one,

the

they

timeout
deselect

contents

are

output

single

device

standard

order.

STATE

This

represents
OFF
ON

the

new modem

control

state,

follows:

When

Network Control Program
4

(NCP)

NETWORK CONTROL PROGRAM

Page 88

(NCP)

This section is divided into three parts.
Section 4.1
describes
the
NCP
functions.
Section 4.2 provides rules for the operation of NCP,
including such topics as input and output formatting
and
status and
error
messages.
Section 4.3 presents a complete list of all the NCP

commands as well as specific formats for the output on SHOW
commands.

4.1
There

and

LIST

Network Control Program Functions
are

two

types

NCP

commands:

Internal commands. These are
directed
to
NCP
1tself
and
cannot be sent to remote nodes.
These are the SET and DEFINE
EXECUTOR NODE node-1d, CLEAR and
PURGE
EXECUTOR
NODE,
and

SHOW QUEUE commands;

the TELL prefix;

and the EXIT command.

Commands that use the Network
Management 1nterface.
These
use
the
Network
Management
Listener,
via
the
Network
Information
and Control Exchange (NICE) protocol,
when
sent

across
logical links to remote nodes.
NCP commands directed
to the local node have the option of either using the Network
Management
Listener,
via
=the
Network
Management
Access

Routines and
the
NICE
protocol,
or
of
passing
requests
directly
to
the
Local Network Management Function from the
Network Management Access Routilnes.
The
method chosen
1s
implementation-specific; however, passing requests internally
1s

recommended.

The keyword ALL can be
general,
it

parameters

used with

means that

the

many

command

the

should

NCP

commands.

executed

in the appropriate data base associated with the

for all

specified

entity.

The NCP command language enables an operator to perform the ‘following
functions:

Changing parameters

Gathering

information

Down-line

(Section 4.1.1)

(Section 4.1.2)

(Section 4.1.3)

Up—line dumping (Section 4.1.4)

Triggering bootstrap

Testing

(Section 4.1.5)

link and network

(Section 4.1.6)

network

Network Control Pfogram (NCP)
o

4.1.1

Zeroing

Changing

counters

Page 89

(Section

4.1.7)

Parameters

NCP can set or change many of the parameters described in Section 3.
Some examples of changing parameters are:
O

Setting

Changing

Setting

the

Setting

a node

Parameters may be

line

state

node

name

routing

set

to be

either

associated with
cost

fcr

node

line

notified of certain

address

dynamic

logged events

values

volatile

memory

~using the SET command or as permanent values in a mass-storage default
data base using the DEFINE command.
The volatile data
base
1is
lost
when
the
node
shuts
down; the permanent data base remains from one
system 1nitialization to the next.
Parameters can be
either
status,
such
as
line
state,
or characteristics that are determined by SET,
DEFINE,

sense

CLEAR,

that

operator,

and

once

they

PURGE

commands.

set,

either

remain

Characteristics

constant

system

until

cleared

consists
of
dynamic
information
(such
as
automatically when functions are performed.

Permanent values take effect

whenever

re-read.

The

timing

‘implementation-dependent.

the

Volatile

the

line

static

time

reset.

state)
.

permanent

values

are

generation

take

the

Status
changes

data

taking

effect

that

base

effect

1s
ls

immediately.

Section 5.10 describes
the internal operation for changing parameters.

4.1.2

Gathering Information

NCP

can
display
current
values
described in Section 3.
Examples

Displaying

Reading

Displaying

the

and

state

then

zeroing

for
the
parameters
and counters
of gathering information are:

line
line

characteristics

counters
all

reachable

nodes

o Showing the status of all commands 1n progress at a node
Counters are error and performance statistics such as - messages sent
and received,
use.
Section

time
5.11

last zeroed, and maximum number of logical
describes the read information operation.

links

Network Control

4.1.3

Program

Down-line

(NCP)

- Page

Down-line loading 1is the process of transferring
a memory image from a
file
to
a
target system's memory.
This requires that the executor,
the node executing the command, have direct access to the link to
the
target.
The file may be located at another remote node, in which case
the executor uses its system-specific remote file
access
procedures.
The
executor
supports or has access to
load request.
Section 5.6 describes the
the Network Management layer.

4.1.4

Up-line

a data base of defaults for a
down-line load
operation
1n

Dumpilng

Up-line dumping is the process of transferring the dump
of
a
memory
image
from
a
target
system
to
a
destination
file.
Section 5.7
describes the up-line dump operation.

4.1.5
An

Triggering

operator

can

Bootstrap
use

NCP

unattended
remote
target
bootstrap operation.

4.1.6

Testing

Link

and

trigger

node.

the

Section

bootstrap

5.8

1loader

describes

the

trigger

Network

Testing link and network can be accomplished by message looping at the
line,
circuit,
and
node
levels.
Testing
transmitted message over a particular path that
local node by either hardware or software.

Node
data

requires
1s looped

receiving
a
back to
the

level testing uses logical links and normal data link usage.
1links involved are 1n the ON state, and the Session Control,

Communication,

and Routing

layers are

used.

The
End

During line loop testing,
the line being
tested
1is
1in
the
SERVICE
state.
As
with
the
<circuit
loop test, normal usage is precluded.
Network Management accesses the Data Link layer directly.
A LAPB line
loop 1s
at the physical connection level, but is limited to hardware
loopback only.
Section 5.9 further describes line, circuit, and
node
testing.
|
'

\w.,.-«/"

During circuit level testing, a DDCMP circuilt being tested is
in
the
SERVICE
state;
normal usage 1is precluded.
An X.25 circuit cannot be
loop tested.
An Ethernet circult to be tested must be 1n the ON state
and
be
owned
by
the LOOPER module.
For all circuit tests, Network
Management
accesses
the
Data
Link
= layer
directly,
bypassing
intermediate layers.
|
|

Network Control

4.1.7

Zeroing

Using NCP,
counters

4,2

(NCP)

operator

can

set

Control

Program

module,

circuit,

and

node

rules concerning the operation on NCP.

Multiple parameters on SET, DEFINE, 'CLEAR,
implementation

successfully

optional.

acted

Specifying
a

1line,

Operation

This section describes general

Since

zero.

Network

4.2.1

Page

Counters

Program

on,

and

they

are

executed

PURGE

allowed,

commands

either

all

must

command does

not

have

must
The

this:

the

node where

be able to designate on what
operator has
two
options

node
for

Specifying

a default

Naming

executor

the

executor
with

NCP start-up time, the defaulit
running
or
the
node
that
was
NODE
CLEAR,

command.
or

PURGE

the command
controlling

EXECUTOR

or none.

the Executor

typed the operator
1s to be processed

DEFINE,

are

The

the

set

commands

command

executor
is the

node on which NCP 1is
defined with the DEFINE

previously

default

EXECUTOR

for

executor

NODE

changed

using

the

SET

commands.

With any command, the operator can override the
default
executor
by
specifying which node is to execute the command.
This is accomplished
by entering "TELL node-identification" as a
prefix
to
the
command.
The
specified node identification applies only to the one command and
does not affect the default executor or any subsequent commands.

4.2.2

Program

The way NCP
is used for

Invocation,

Termination,

and

Prompting

1s invoked or terminated is system-dependent.
If
a
name
the program, it must be "NCP." The EXIT command terminates

NCP,

The

following

rules

apply

the

initial

NCP prompt:

For an NCP that accepts only a single outstanding command
1s

always

the

prompt

same:

NCP>

For an NCP that accepts

several

outstanding

commands

where

Network Control

obvious

Program

that NCP

(NCP)

is prompting,

the prompt

Page

1is:

#n>

For the multiple-outstanding-command case where it is not obvious that

NCP 1is prompting,

the

prompt

1:is:

NCP#n>
In any case,
the

output

n is the command‘s request number,

for

the

An implementation that cannot integrate the
prompt, can display the request number when

4,2.3

which

will

identify

command.

request
number
with
the
the command 1s accepted.

Privileged Commands

Network
limited

and system planners must determine which
commands
should
to privileged users.
The exact determination of privilege

be
1s

an
1mplementation-dependent
function.
Privilege
1s
generally
determined in a system-specif:c way according to the privileges of the
local user or the access control provided at logical
1link
connection
time,
‘
|

4.2.4

Input

Formats

Command input is in the form of arguments delimited by tabs or blanks.
Either

single

multiple

tab

blank may be used to delimit

arguments.,

Null command lines.
prompt

Null command

1lines

will

result

1in

being re-issued.

command
a

Node identification and
access
control.
Nodes
are
1identified
by
address or name.
The primary identification is the address (a Session
Control requirement).
The keyword EXECUTOR
can
be
substituted
for
NODE
executor-node-identification.
If
a
node
identification
represents a node to be connected to, access control
1information
may
be
necessary
or desired.
If so, the access control follows the node
identification, the maximum length
o0of
each
field
being
39
Dbytes.

Specific

systems

may

limit

the

they will

accept.

The

format

1is:

Command

| Entity

amount of

access

control

information

| Parameter

__________________ +__._..__..__._.____._+_....._._..___._._______.___._._....__.___._._.___.__.._._.__-———-—

LOOP NODE
|
SET EXECUTOR NODE |
TELL
|

node-id

|
|
|

[USER user-id]
[PASSWORD password]
[ACCOUNT account
]

__________________ +————.—_....__._._._+_._.-_—____._.___._..__._._.—.._..-———.—-—-————-—.—-—.—.———-—-—--—-

Network Control Program (NCP)
LOOP NODE node-id

|
Is

an NCP command

node

loopback

applies
SET

EXECUTOR NODE

node-id

Page 93

only

NCP

used

test.

the

command

The

1initiate

access

used

TELL

node-1id

Is
one

NODE

NCP

control for
access
changed
by
or
a
TELL
The

command prefix

used

command

and

access

a
specific
applies only

node

pass

control

node.
to that
‘

The
one

example:

TELL BOSS USER [211,1]
SET

the

command.

information to
access
control
command.
For

‘

set

1dentification
and
access
default executor node.
control
prevaills
until
another SET EXECUTOR command
LOOP

control

command.

the

EXECUTOR NODE

String input.
String
keyword
or
number)

PASSWORD secret ACCOUNT xyz CLEAR KNOWN LINES

ACCOUNT

xyz

input (every argument that is not
1is
defined
by the executor node

name,
length
limitations
of
the
NICE
protocol.
For
consistency
from
one
implementation
to another, the following rules apply to NCP's parsing
algorithm for these types of arguments:
o

Implementations
non-transparent

The
transparent
technique
will
act
on
any
string of
characters
enclosed
1in
quotation marks ("XXXXX").
A quote
within the string will be indicated
by
a
double
quotation
mark ("XXX""XX").

The non-transparent technique
will
act
on
any
string
of
characters
that
does
not
contain
blanks
or
tabs.
An
exception to thils occurs where it is
possible
to recognize
syntactically
that
blanks
or
tabs
are
not
intended
as
delimiters.

Keywords.
However,

minimum

will
provide
both
a
technique for specifying

a
node
and the

Implementations must accept
keywords
user
may abbreviate keywords when

the

abbreviation

transparent
and
these arguments.

1in

their
entirety.
them i1n.
The

typlng

system- spec1f1c.

The command formats specified

in this document

are

to be

the

formats

used
for
NCP
1input.
They
may
be modified only 1n the sense that
unsupported commands or options may be left out.
It is permissible to
prefix a
command
with an identifier such as OPR NCP.
However, this
prefix should not affect
the
remainder
of
the
command
syntax
or
semantics.
Optional system-specific guide words such as TO or FOR can
be added to NCP commands 1f they do not
interfere
with
defined
key
words.

Network Control Program

(NCP)

Page

The NCP command language does not use a question mark as

or
semantic
element.
‘according to operating

The
question
mark
system conventions.

left

syntactic

available

for use

An implementation may recognize locally defined
names
for
1lines
accept other non-standard line identifications as string 1inputs.

4.2.5

Output

The output

Characteristics

format

specified

in this document

is to be

considered

the

basic
pattern for all NCP output.
Implementations may differ as long
as common information is readily identifiable.
The following
example
shows
three
commands
and
their
resultant
output.
User-furnished
information is underlinea to distinguish 1t from the program output.

#23>LOAD NODE MANILA
#24>LOAD NODE TOKYO
#25
REQUEST #24;
SHOW

LOAD FAILED,

LINE COMMUNICATION ERROR

QUEUE

REQUEST

#25;

SHOW QUEUE

REQUEST
NUMBER

|
EXECUTOR

21
22
23
24

6
6
6
6

COMMAND

(HNGKNG)
(HNGKNG)
(HNGKNG)
(HNGKNG)

SHOW
SET
LOAD
LOAD

N/A

SHOW

STATUS

COMPLETE
COMPLETE
IN PROGRESS
FAILED
IN

#$26>

PROGRESS

REQUEST #23,

LOAD

COMPLETE

Passwords are not displayed.
Instead,
an
ellipsis
(...)
that
a
password 1s set.
Section 4. 3 8 contains output for
information (SHOW and LIST commands).

4,2.6

Status

and

Error

1indicates
requested

Messages

Status and error messages inform the NCP user of the consequence of
a
command
entry.
NCP
gives
each
command a request number, which 1t
displays with status and error messages.
NCP displays status or error
messages
when
the
status of the command changes as long as the user
does not begin to type a new command
The general form of status
and
error

messages

REQUEST
where:

1s:

[entity,]

command status

[,error-message]

Network Control

Program

(NCP)

Is the command's request number,

entity

specific

entity.

command

indicator.

status

'Is the status of
FAILED,

error-message

Commands
have

the
1ts

that

act

the

A s

NCP

fhaf

allows

e N

dlsplayed

output
LOAD

for

the

command

FAILED,

LINE

for

entities

this

only

and

an
a

one

case,

that

has

COMPLETE,

1is

example,

FAILED

each

failed

SET

individual

number

COMMUNICATION

one

there

NOT

error-message.

(for

command

request

failure.

message
for each

entire operation.
In
own status message.

are not

the operation,

ACCEPTED.

there

reason

on plural

separate status

NOT

error-message.

ACCEPTED,

Page

command

entity

1is

time,

not

XKNOWN

entity

and

LINES)
one

1identified

COMPLETE

included.

for

with

messages

ujx—u

follows:

example

ERROR

When a loop test succeeds on an Ethernet circuit and the user did
not
specify
a
physical
address,
the
command
output
1includes
the
ethernet-address of the respondlng system from the loopback
assistant
multicast group in the form:
|

PHYSICAL ADDRESS = ethernet-address
When a loop test
information,
UNLOOPED

fails,
the

COUNT

the error message contains

added

explanatory

form either
=

MAXIMUM

LOOP

DATA

Where the unlooped count:is the number of messages not
the
test
failed and maximum loop data is the maximum
be requested for the loop test data.
NCP prints unrecognized
numbers.
For example:

Request #5;
SET FAILED,

return

codes

error

yet looped when
length that can

details

decimal

SHOW failed, Management return #-34
parameter not applicable, detail #2300

Error messages are either those from the set of NCP error messages
in
Appendix
G,
the
NICE
error returns in Appendix F or implementation
specific.

Network Control Program (NCP)
4,3

Network Control

This

section describes

Page 96

Program Commands
NCP

commands.

The following symbols are used in NCP command syntax descriptions:

[]

Brackets indicate optional input.
these

are

rarameter

UPPER CASE
|

entity

options

for

Lower case

letters

aescription

are

part

{

command

between

input

variables

(not

parameters.

are

commands

"verb

have

entity

the

that

not

indicate

the

actual

following

common

keywords)

1in

hyphenated.

Braces
1ndicate
that
any
parameters are applicable.

All NCP

input,

commands.

variable,

variables

string delimit

Multi-word

}

cases

entity

Spaces

-~ hyphens

NCP

in a command string

“nput.

spaces

and

command.

letters signify actual

that

In most

parameters

Lpper case
keywords

lower case

the

enclosed
-

syntax:

entity-option(s)

where:

verb

Specifies the operation to be performed,
SHOW

LOAD.

entity

Specifies the

entity-option(s)

Qualifies

4.3.1

operation

SET

and

specific

DEFINE

such

entity

applies,

the

such

command

information.

(component)
as

LINE

which

KNOWN NODES.

providing

the

further

Commands

These commands modify volatile
and
permanent
parameters.
The
SET
command
modifies
the
wvolatile data base; the DEFINE command changes

the permanent data base.

parameter
The

general

SET

form of

the

entity

DEFINE

Entity

Section

5.10

operation.

parameter
.

is one of

the

commands

following:

1is:

describes

the

1internal

change

Network Control Program (NCP)
CIRCUIT

Page 97

circuit-1id

EXECUTOR
KNOWN

CIRCUITS

KNOWN

LINES

KNOWN

LOGGING

KNOWN

MODULES

KNOWN

NODES

LINE line-1id
LOGGING sink-tvpe
MODULE

NODE

module—-name

node-1d

Parameter 1s one (or more,
parameter

4.3.1.1

options

SET
and

and

aefined

DEFINE

the

specified

EXECUTOR NODE

implementation)

SET

executor node for subsequent commands.
Access
be supplied as described in Section 4.2.4.

commands,

processed

NCP,

control

change

information

SET and DEFINE KNOWN Entity Commands

These commands set volatile and permanent parameters
specified

Command

the

destination-node

the
may

the

entity.

The

4.3.1.2

DEFINE

if allowed by the
for

entities

known

Entity

the

________ e

SET

KNOWN plural-entity

DEFINE

system.

The

for each

one

format 1is:

Parameter

e e

ALL

parameter

________ +___.__._._.._._.__._____._.__.__+__.__._.._____._.____.__.__._.___..._._._.....____...__.._.._.__..___.._._.

Plural-entity is one of CIRCUITS, LINES, LOGGING, MODULES, or NODES.
-The

parameters are the
following.
However,

SET
the

same as
DEFINE

KNOWN plural- entlty ALL
volatile data base.

4.3.1.3

These

SET

and

DEFINE

commands control

entity.
Refer to

for the SET and DEFINE entity
commands
KNOWN plural-entity ALL has no meaning.

loads

CIRCUIT

the

all

entity parameters

1nto

Commands

setting

Some
of the parameters
Section 3.3.1.

| The format of these commands 1is:

permanent

only

parameters for
apply

certaln

the

«circuit

circuit

types.
|

Command

(NCP)

Entity

SET

CIRCUIT circuit-1id

DEFINE

KNOWN

CIRCUITS

Parameter

|
|
|

ACTIVE BASE base
ACTIVE INCREMENT
ALL

|
|
|
|
|
|
|
|

COST cost
COUNTER TIMER seconds
DEAD THRESHOLD count
DTE dte-address
DYING BASE base
DYING INCREMENT increment
DYING THRESHOLD count
HELLO TIMER seconds
INACTIVE BASE base
INACTIVE INCREMENT

|
increment

INACTIVE

count

|
|
|

LINE line-id
MAXIMUM BUFFERS count
MAXIMUM DATA byte-count

|
|
|

MAXIMUM ROUTERS number
MAXIMUM TRANSMITS count
MAXIMUM WINDOW block-count

|
|
|

ORIGINATING QUEUE LIMIT queue-size
OWNER owner-id
POLLING STATE polling-state

ROUTER PRIORITY number

|
|
|

|
|
|
|
|

SET

and

DEFINE

LINE

increment

BABBLE TIMER milliseconds
BLOCKING blocking-control
CHANNEL channel-number

|
|

4,3.1.4

Page

THRESHOLD

MAXIMUM RECALLS

NUMBER

retry-count

call-number

RECALL TIMER seconds

SERVICE service-control
STATE circuit-state
TRANSMIT TIMER milliseconds
TRIBUTARY tributary-address
TYPE circuit-type

USAGE usage-type

Commands

These commands control the setting of parameters for the line

entity.

Some
of the parameters are only applicable to certain line protocols.
Refer to Section 3.5.1 The format of these commands 1is:

Command

' SET
DEFINE

Entity

LINE line-id
KNOWN

LINES

Parameter

DEAD TIMER milliseconds

Network Control Program

Network Control

Program

(NCP)

Page

DELAY TIMER milliseconds
DEVICE device-specification
DUPLEX duplex-mode

HOLDBACK TIMER

milliseconds

MAXIMUM BLOCK byte-count
"MAXIMUM RETRANSMITS block-count
MAXIMUM WINDOW block-count
PROTOCOL protocol-name
RECEIVE BUFFERS number

RETRANSMIT TIMER milliseconds
SCHEDULING TIMER milliseconds
SERVICE service-control
SERVICE TIMER milliseconds
STATE line-state
STREAM TIMER milliseconds

4.3.1.5

SET

and DEFINE

LOGGING Commands

This set of commands is used to control event sinks (where events
logged)

and

event

command

format

1is:

Command

lists

(that control which events get

are

logged).

The

Entity

| Parameter

Qualifier

———————— e
et

SET

DEFINE

LOGGING sink-type

|
|

|
|
B

|
|

ALL

Fommmmm

eT
e

EVENT event-list
KNOWN EVENTS

NAME

STATE sink-state

These

SET

[source-qualifier]
[sink-node]
|

o
—

sink-name

Section 3.3 describes source qualifiers,

4.3.1.6

|
|

sink nodes,

and sink types.

and DEFINE MODULE Commands

commands vary considerably depending
on the module

named.

The

following
descriptions
take
this
into
account
by
describing the
options independently
for each defined module identification.

4.3.1.6.1

SET

and DEFINE MODULE CONSOLE Commands

These commands control the parameters
necessary
console.
The format of these commands 1is:

the

mailntenance

Network

Control

Command

Entity

________ e

SET
DEFINE

|
|

Program

.
e

These

|
e

e e

MODULE CONSOLE

________ e

4.3.1.6.2

(NCP)

SET

|
|

control

the

ALL
RESERVATION TIMER seconds
e

e e e e

parameters

format

Entity

________ e e e

DEFINE

100

SET and DEFINE MODULE LOADER Commands

commands

‘Page

Parameter

loader and dumper. The
Command

MCDULE LOADER

necessary

these commands

is:

the

maintenance

Parameter
e e e

e e

ALL

ASSISTANCE

e e

control

________ +_____._._._.._._._._...._—_+____._._..._.___..___._____._._....__..______..._...___.___.._..__._

4,3.1.6.3

SET

and

DEFINE

MODULE

LOOPER

These commands control the parameters
looper.

Command

The

format

DEFINE

these

Entity

________ gl

SET

|
gL

MODULE LOOPER

commands

Commands

necessary

the

maintenance

is:

Parameter

S
S
G

|
|

ALL
ASSISTANCE

control

________ +._..__.______.___.___..._.+____..___..____.__._____.._._....._._.._.._______..____.__.__.__._

4.3.1.6.4

SET

These commands
configurator.

and DEFINE MODULE CONFIGURATOR Commands
control the parameters
necessary
The format of these commands is:

Command

SET

| MODULE

DEFINE

Entity

CONFIGURATOR

Parameter

the

maintenance

| Qualifier

| ALL

SURVEILLANCE

| [CIRCUIT circuit-id]

control

[KNOWN CIRCUITS]

———————— +———————————————— e
e e
e
e —
-

If only one circuit is known,

circuit 1is known,

4,3.1.6.5
These

Access

SET

commands

and

the

DEFINE

control

Routines.

The

1t 1s the default.

qualifier must

the

included.

MODULE X25-ACCESS
parameters

format

these

than

one

Commands

necessary

commands

is:

the

X.25

Gateway

Network Control Program (NCP)
Command

Entity

———————— fm——

SET
DEFINE

|
|
!
l
|

Parameter

MODULE
X25-ACCESS

|
|
|
|
|

Page 101
Qualifier

e b

ACCOUNT account
ALL
NODE node-id
PASSWORD password
USER user

———————— e

|
|
o
|
|

[KNOWN NETWORKS]
[NETWORK network-name ]

If only ore network is known, 1t 1s the default.
network is known, the parameter must be included.

4.3.1.6.6

Command

The

than

one

SET and DEFINE MODULE X25-PROTOCOL Commands

These commands control the parameters for the

module.

format

of these

Entity

commands

X.25 protocol

1s:

Parameter

cbntrol

Qualifier

________ +.._.____.___..._._._.__._.__+_.._._...____._.__.__._____..______._+___._.__...__.___._._.___._

SET
DEFINE

MODULE
X25-PROTOCOL

|
|

ALL

|
|

[dte-qualifier]
[group-qualifier]

|
|
|

|
|

GROUP group-name group-options
CALL TIMER seconds
CLEAR TIMER seconds

DEFAULT DATA byte-count

DEFAULT WINDOW block-count

MAXIMUM DATA byte-count

|
|

MAXIMUM CLEARS
MAXIMUM RESETS

MAXIMUM WINDOW block-count

|
|

retry-count
retry-count

MAXIMUM RESTARTS

retry-count

NETWORK network-type
RESET TIMER seconds

RESTART TIMER seconds

e
e
—— —

|
|
|
|
|

CHANNELS list
COUNTER TIMER seconds
LINE line-id
|
MAXIMUM CIRCUITS count
STATE dte-state

|
|
I
|
|

[dte-qualifier]

________________________ +____.._____..—-—____.__..—_____—.._+_._.__.___._..____._.___._._

Dte—-qualifier
1indicates
to
applies.
It 1s of the form:

which

1local

DTE

address

the

command

KNOWN DTES
DTE dte-address

If only one local DTE address

is known,

Group-qualifier indicates to

which

than one local DTE address

is known,

1s the

default.

the parameter must be

closed

user

group

included.

the

command

Network Control

Program (NCP)

applies.

It 1is

the

KNOWN

GROUPS

GROUP

group-name

Page

102

form:

Group-options
are:
DTE

dte-address

NUMBER
TYPE

group-number

group-type

Both DTE and NUMBER must

4,3.1.6.7
These

SET

commands

Server.

The

and

DEFINE

control

format

MODULE

SET

X25-SERVER

TYPE

X25—SERVER

parameters

these

Entity

DEFINE

MODULE

the

included,

commands

Parameter

ALL

optional.

Commands

necessary

|
|

COUNTER TIMER seconds
MAXIMUM CIRCUITS count

|
|
|

ACCOUNT account
CALL MASK hex-value
CALL VALUE hex-value

|
|
|

the

KNOWN

X.25

Gateway

Qualifier

[destination-qual]

#—--—————————————
- ———— Tt

|
|
|

| GROUP group-name
| NODE node-id
| NUMBER dte-address
| OBJECT object-id

Destination-qual

the

1s:

1nd1cates

|
|
|
|

PASSWORD password

PRIORITY priority
SUBADDRESSES range
USER user
to

which

[destination-qual]

|
|
|

destination

the

form:

command

applies.

DESTINATIONS

DESTINATION destination-name
If

only

one

destination

4,.,3.1.7

SET

destination

known,

and

DEFINE

These commands set
Certain

parameters

the

known,

NODE

volatile
can

parameter must

the

default.

included.

than one

Commands

or
set

permanent
only

for

parameters for a
the

executor

node

node.
or

for

Network Control Program

adjacent nodes.
command 1S:

See

(NCP)

Table

20,

Section

7.9.

The

format

Parameter

SET

EXECUTER

DEFINE

KNOWN

NODES

NODE

node-1id

ADDRESS node-address
ALL

AREA MAXIMUM

COST

number

AREA MAXIMUM HOPS

number

BROADCAST

TIMER

BUFFER

ROUTING

SIZE

CIRCUIT

seconds

bytes

circuit-1id

COUNTER TIMER seconds
CPU

cpu- type

DELAY

FACTOR

number

DELAY

WEIGHT

number

DIAGNOSTIC

FILE

DUMP

ADDRESS

NIMAD

OCOTINTMT

LU UILIN

file-1id

number

nitMhaoar
1L ULt
C L

DUMP FILE file-id
HARDWARE ADDRESS ethernet-address
HOST node-1id
|

IDENTIFICATION id-string
INACTIVITY TIMER seconds
INCOMING

TIMER seconds

LOAD FILE

file-id

MAXIMUM

ADDRESS

MAXIMUM

AREA

number

MAXIMUM

BROADCAST

NONROUTERS

MAXIMUM

BROADCAST

ROUTERS

MAXIMUM

BUFFERS

number

CIRCUITS number
MAX IMUM COST number
MAXIMUM HOPS number
MAXIMUM LINKS number
MAXIMUM VISITS number
NAME node-name
MAXIMUM

OUTGOING TIMER seconds
RETRANSMIT FACTOR number

ROUTING

TIMER

seconds

SECONDARY DUMPER
'SECONDARY LOADER
SEGMENT

BUFFER

file-id
f1ile-1id

SIZE

bytes

CIRCUIT circuit-1d
SERVICE DEVICE device-type
SERVICE NODE VERSION node-version
SERVICE

SERVICE

PASSWORD

password

SOFTWARE

IDENTIFICATION

SOFTWARE

TYPE

software-1id

program-type

STATE node-state
SUBADDRESSES range
TERTIARY LOADER file-id
TYPE node-type

Page

103

for

the

Network Control Program (NCP)
4.3.2

CLEAR

and

PURGE

Page 104

Commands

These commands clear parameters from the volatile and
permanent
data
bases.
The
CLEAR
command affects the volatile data base; the PURGE
command affects the permanent data base.
Not all
parameters can
be

cleared
1individually.
A
cleared
or
purged
parameter
or
entilty
identification is the same as one that has not been
set
or
defined.

If
the
general

parameter has a default
form of the command 1is:

Command

Entity

value,

reverts

that

value.

The

Parameter

________ e
———_—_E—_E—_—_E—_—E—_—_—_————_—

CLEAR
PURGE

|
|

entity

|
|

parameter

________ +._._._._.___._..__._.___._.._+__..__.......__.___.._—._______._.._.______._..____.._.._.._.____..__.__—._

The entities
are the same

for

the SET and DEFINE commands

4.3.1).

(Section
|

CLEAR

and

PURGE

EXECUTOR NODE

Commands

The CLEAR EXECUTOR NODE command resets the
executor
to the
command
node.,
Note
that CLEAR EXECUTOR does not return the executor to that
defined in the permanent data base.
The PURGE EXECUTOR
NODE
command
redefines the executor in the permanent data base to the command node.
Access control 1s reset as well.
|

4.3.2.2

CLEAR and PURGE KNOWN Entity Commands

These commands clear and purge parameters for
entities known

Command

the

system.

Entity

The

format

all

the

command

the

1is:

specified

Parameter

________ +____._._.__.____.__._._.__.______+_._______._______.__..._._._____._.____.___.._..___.__._.___

CLEAR
PURGE

|
|

KNOWN plural-entity

| parameter
|

________ +_________.______.__._____._____+__.._____.___._._.__._.______..___.__.__.______._._.._..__.._._____.

Plural-entity

one

CIRCUITS,

LINES,

LOGGING,

MODULES,

Parameter is one or possibly more of the
parameters
the CLEAR and PURGE entity commands (following).

4,3.2.3

The

CLEAR

format

and

these

PURGE

CIRCUIT

commands

1s:

Commands

NODES.

associated

with

—

4.3.2.1

Network Control Program

Entity
e o e e e e o o o

(NCP)

CIRCUIT circuit-1id

PURGE

KNOWN

The

CLEAR and PURGE

format

Command

CIRCUITS

these

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

105

—————_——— ——— —

ACTIVE BASE
ACTIVE

INCREMENT

ALL
BABBLE TIMER
COUNTER TIMER
DEAD THRESHOLD
DYING BASE
DYING INCREMENT
DYING THRESHOLD
INACTIVE BASE
INACTIVE INCREMENT
MAXIMUM BUFFERS
MAXIMUM RECALLS
MAXIMUM TRANSMITS
OWNER
RECALL TIMER
TRANSMIT TIMER

LINE Commands

commands
1s:

Entity
LINE

line-id

KNOWN

LINES

Parameter

ALL

|
|
I
|
l

4,3.2.5

Page

Parameter

=
— —e

CLEAR

4.3.2.4

TIMER

COUNTER

DEAD | TIMER

DELAY TIMER

HOLDBACK

TIMER

MAXIMUM RETRANSMITS

SCHEDULING TIMER
STREAM

TIMER

CLEAR and PURGE MODULE Commands

These commands vary considerably depending on the module
named.
The
following
descriptions
take
this
1into
account
by
describing the
options independently for each defined module identification.

4.3.2.5.1

CLEAR and PURGE MODULE X25-ACCESS Commands

The format of these commands

1is:

Network Control Program

Command

Entity

———————— +-————_———_

CLEAR
PURGE

(NCP)

|
|

Page

Parameter

MODULE X25-ACCESS

I
|

Qualifier

|
|

ALL
ACCOUNT

|
|

PASSWORD
USER

|
|

106

e ——_———

- —

[KNOWN NETWORKS
]
[NETWORK network-name]

———————— e

only

network

one

network

known,

4,3.2.5.2

CLEAR

the

and

known,
it

network

PURGE

the default.

qualifier

MODULE

must

X25-PROTOCOL

than

one

included.

Commands

The format of these commands is:
|

Parameter

———————————————— b
I
E—

MODULE

X25-PROTOCOL

|
|
gy
S
S

|
|
|
|
|
I
|
|

Gm—

——

———not

—

——

—

——n

—

w—

CALL TIMER
CLEAR TIMER
GROUP group-name group-options
MAXIMUM CLEARS
MAXIMUM RESETS
MAXIMUM
RESET

RESTARTS

TIMER

RESTART

TIMER

| COUNTER TIMER
|
Dte-qualifier

applies.

1indicates

the

LINE line-id

which

1local

DTE

address

the

command

form:

KNOWN DTES
DTE dte-address

If only one
than

one

local DTE address

local

DTE

address

Group-qualifier

indicates to

applies.

the

GROUP

group-name

KNOWN

GROUPS

Group-options
DTE
TYPE

one

dte-address

is known,

known,

the

parameter

which

closed

form:

is the

wuser

default.
must

group

included.

the

command
|

of:

Network Control Program

4.3.2.5.3

CLEAR

The

format

Command

and

these

(NCP)

Page

PURGE MODULE

X25-SERVER Commands

commands

Entity

107

Qualifier

Parameter

———————— ———— ¢

CLEAR
PURGE

|
l

MODULE X25-SERVER

|
|
|
|
|
|
|
|
|

|
+

|
|
|
I
|
|
|
|
|

ACCOUNT
ALL

CALL

MASK

CALL

VALUE

GROUP
NUMBER

PASSWORD
PRIORITY

USER

———————— — ¢

Destination-qual 1indicates
It is of the form:
KNOWN

which destination the

command

applies.

DESTINATIONS

DESTINATION destination- name

If only one destination is known,
destination

4.3.2.6

known,

CLEAR and

These commands,
'in
commands,
control

the

PURGE

it is the default.

parameter must

LOGG ING

conjunct ion
event
si nks

sink-type,

the

apply

Command

LOGGING

command

Entity

than

one

1included.

Commands

definitions (sink-node,
SET

wilith
and

the
event

SET Aand
DEFINE
lists.
The same

and source-qualifier)

LOGGING

general

that apply

here.
Parameter

Qualifier

———————— — ¢

CLEAR
PURGE

|
|
|

LOGGING sink-type
-

|
|

[sink-node]

[source-qualifier]

———————— e
—

4.3.2.7

CLEAR and PURGE NODE Commands

These commands clear volatile (using CLEAR) or permanent (using PURGE)
parameters
for
the node.
Node identification can be either a node
name or a node address, except for the CIRCUIT option where it must be
a
name.
EXECUTOR
may
substitute
for
NODE
executor-nodeidentification.

Network Control

Command

Program

Entity

——,—
e
e

CLEAR

(NCP)

NODE

|
——

Page

108

Parameter

node-1id

PURGE

'4.3.3

SECONDARY

|
|
|
|
|
|

SERVICE DEVICE
SERVICE CIRCUIT
SERVICE PASSWORD
SOFTWARE IDENTIFICATION
SOFTWARE TYPE
TERTIARY LOADER

LOADER

TRIGGER Commands

These

commands trigger the bootstrap of the target node
so
that
the
node will load 1itself.
It initiates the load of an unattended system.
This command will work only if the target node either
recognizes
the
trigger
operation
with software or has the necessary hardware in the
correct state.
Parameters
specified
with
a
command
override
the
default
parameters
of
the same type.
If the circuit is an Ethernet
circuit, the PHYSICAL ADDRESS must be
included
1in
the
TRIGGER
VIA
command.

Command

The

format

Entity

TRIGGER | NODE node-id
|
|

| VIA circuit-id
|

the

commands

1is:

| Parameter

[PHYSICAL ADDRESS ethernet-address]

|
|
|

[[SERVICE] PASSWORD password]
[VIA circuit-1id]
[[SERVICE]

PASSWORD password]

Network Control Program (NCP)
4.3.4

LOAD Commands

These commands

Node

Page 109

initiate a down-line

identification

1is

either

the

load.

There are

node name or

the

two

node

varliations.

address

target node.
This command works only if the
conditions
for
are met, or if the target node has been triggered locally.

4.3;4.1

the

trigger

LOAD NODE Commands

These commands load the node identified on the circuit
1identified
or
on
the
circuit
obtained from the volatile data base.
Any parameter
not specified in the command line defaults to whatever 1is specified 1in
the volatile data base

the

executor

node.

Parameter

[ADDRESS node-address]

|
|
|
|
|

[SERVICE NODE VERSION node-version]
[[SERVICE] PASSWORD password]
[SOFTWARE IDENTIFICATION software-id]
[SOFTWARE TYPE program-type]
[TERTIARY [LOADER] file-1id]

|
|
|
|
|
|
|

[VIA circuit-id]

;

[CPU cpu-type]
[FROM load-file]
[HOST node-id]
[NAME node-name]
[PHYSICAL ADDRESS ethernet-address]
[SECONDARY [LOADER] file-1id]
[SERVICE DEVICE device-type]

4.3.4.2

LOAD VIA Commands

With these commands, the executor loads the target over the
specified
circuit, obtaining the node identification from the volatile data base
if necessary.
If the circuit is an
Ethernet
«circuit,
the
PHYSICAL
ADDRESS must be included in the command.
The command format 1is:
Entity

Parameter

VIA circuit-id

|
|
|
|

[ADDRESS node-address]
[CPU cpu-type]
[FROM load-file]l
[HOST node-id]

[PHYSICAL ADDRESS ethernet- address]

|
|

[NAME node-name
]

[SECONDARY [LOADER] file-1id]
[SERVICE DEVICE device-typel]

[SERVICE NODE VERSION node-version]

Network Control Program (NCP) |

|
|
|
|
|

—

——

—

C—

—

——

—

4.3.5

DUMP Commands

These

commands perform

——

—

w— tatve wmim

[[SERVICE] PASSWORD password]
[SOFTWARE IDENTIFICATION file-id]
[SOFTWARE TYPE program-type]
[TERTIARY [LOADER] file-id]

+ S

—

wup-line

default
to
those
1n
the
There are two variations.

4.3.5.1

—

Page 110

—

———

E—— T

APEm

dump.

wvolatile

data

—

——.

—

——

—

ogma

Parameters

base
»

the

—

——

wmeam

not

m—

——

—

——

—

supplied

executor

node.

DUMP NODE Commands

The format for these Commands 1S:
Entity

Parameter

[[DUMP]

|
|

|
|
|
|
|

4,.3.5.2

DUMP

[TO dump-file]
[SECONDARY [DUMPER] file- 1d]
[SERVICE DEVICE device-type]
[[SERVICE] PASSWORD password]
[VIA circuit-id]

VIA Commands

If the circuit is an Ethernet circuit,
included

ADDRESS number]

[[DUMP] COUNT number]
[PHYSICAL ADDRESS ethernet- address]

the

command.

The

format

|
+

the PHYSICAL

for

these

ADDRESS

commands

is:

Parameter
o

[[DUMP]

|
|
|
|

[TO Qump-file]
[SECONDARY [DUMPER] file-id]
[SERVICE DEVICE device-type]
[[SERVICE] PASSWORD password]

|
|

must

ADDRESS number]

[[DUMP] COUNT number]
[PHYSICAL ADDRESS ethernet-address]

Network Control Program (NCP)
4.,3.6

LOOP

- Page 111

Commands

These commands cause test blocks to loop back from the specified
or
node.
There are three variations, as described
in the next
sections.
|

4,3.6.1

1line
three

LOOP CIRCUIT Commands

These perform loop
testing
on
a
specific
circuit.
The
parameters
can
be
entered
1in
any order.
Parameters not
default to their values in the permanent data base
at
the
node.
The command format is as follows:

Command

Entity

Parameter

[ASSISTANT NODE node-id]

[ASSISTANT PHYSICAL ADDRESS

ethernet-address]

[COUNT count]

[PHYSICAL ADDRESS

|
|
|

optional
specified
executor
|

[HELP help-type]
[LENGTH length]
[NODE node-id]

ethernet-address]

[WITH block-type]l
If the circuit 1s an Ethernet circuit, and
PHYSICAL
ADDRESS 1s
not
included
in
the
command,
the
Ethernet
address
used
will be the
loopback assistant multicast address. This will result in
an
output
of the physical address that responded first.
-

HELP and ASSISTANT PHYSICAL ADDRESS can only

cilrcuilts.

If HELP

ASSISTANT NODE must

Dbe

specified,

ASSISTANT

used

with

PHYSICAL

Ethernet

ADDRESS

which

included.

- Ethernet circuits must be owned by MODULE LOOPER.

4.3.6.2 LOOP LINE Commands
The

line

loop performs

unavailable

for

loop

normal

testing

traffic

during

specific

the

test.

parameters can bée entered in
any
order.
Parameters
default
to their
wvalues
1n the permanent data base
node.

The

command format

Entity

follows:

Parameter

|
|
|

[COUNT count]
[LENGTH length]
[WITH block-type]

———————— +

LOOP

|
|
|
+

LINE line-id
D

1line,

The

optional

not
specified
at the executor

LOOP

NODE

Page 112

Commands

4.3.6.3

(NCP)

A node loop will not interfere with normal traffic, but

will

add

‘

Network Control Program

the
network
1load.
The
node loop can take place within one node or
between two nodes.
In the latter case, the remote
node
1s
the
one
specified
(Figures
9 and
10,
Section
5.9.1).
EXECUTOR
may
be
substituted for NODE executor-node-identification.
The command format
1s

follows:

Command

Entity

Parameter

________ +....___._..___.__.._._____....._.____.+_.._..____.__.__.._.___.__._.__...___..___.__._.___._._._.__._._.._._—

LOOP

NODE node-id

|
|
|

[access control]

| [COUNT count]
| [WITH block-type]l
| [LENGTH length]

________ +_._._._..._...___._._..__..._.._.__..____..__..+.._____.__.___._........_..______..___.___._____.___.___.___.___.._

4.3.7

SHOW QUEUE

Command

This command displays the status of the last few commands
the

default

executor.

entered

The number of commands displayed varies with

each implementation.
The executor for commands not
sent
across
the
network is shown as N/A (not applicable).
Completed commands need not
be displayed.
Every command in progress
must
be
shown
1n
request
number
order.
Implementations that do not allow multiple outstanding
commands do not need this command.
An

example

REQUEST

output
#13;

follows:

SHOW

QUEUE

REQUEST

NUMBER

9
10
11
12

EXECUTOR

COMMAND

6 (HNGKNG)
6 (HNGRKNG)
10 (MANILA)
6 (HNGKNG)
N/A

STATUS

LOAD
SHOW
LOAD
SET
.

FAILED
COMPLETE
IN PROGRESS
COMPLETE

SHOW

PROGRESS

4.,3.8 SHOW and LIST Commands
These commands are used to

displays

information

from

display
the

information.

volatile data

base.

displays information from the permanent data base.
SHOW

and

LIST

commands

1S:

The

SHOW

LIST

command

The format of

the

Network Control

Verb

Program

(NCP)

Entity

Page

Parameter

113

Qualifier

————— e
e
-

SHOW
LIST

| ACTIVE AREAS
| AREA area-number

KNOWN AREAS

ACTIVE CIRCUITS

|
|

KNOWN CIRCUITS
SIGNIFICANT CIRCUITS

CIRCUIT circuit-id

CHARACTERISTICS
COUNTERS

STATUS

SUMMARY

|
|

|
|
|
|
|
|

ACTIVE LINES
KNOWN LINES
LINE line-id
SIGNIFICANT LINES
ACTIVE MODULES
KNOWN MODULES

[ADJACENT NODE
node—-id]

————————— +

——

|
|

MODULE X25-ACCES
|

|
|

[KNOWN NETWORKS]
[NETWORK network-name]

+——————,—
e
———— — — +

+———_———_—,
e,
e,
—— —

|
|
I
|

|
|
|
|

MODULE X25-PROTOCOL

|
|
|
|

[DTE dte-address]
[GROUP group-name]
[KNOWN DTES]
[KNOWN GROUPS]

e +

|
|
I

|
|
|

MODULE X25-SERVER
|

|
|
|

[DESTINATION
destination-name]
[KNOWN DESTINATIONS]

- +

o
e
— -

|
|

SIGNIFICANT MODULES
ACTIVE NODES

t———

|
|
N

|
|

- — 4

ADJACENT NODES

- ——————— —————
e
—

|
|

| [CIRCUIT circuit-id]
| [KNOWN CIRCUITS]

e
+

EXECUTOR

NODE node-name

|
|

KNOWN NODES
LOOP NODES

SIGNIFICANT NODES

|
|

|
N

e
e
—
+—————————_——————— —

|
|
|
I

ACTIVE LOGGING
KNOWN LOGGING
LOGGING sink-type

|
|
|
|

CHARACTERISTICS
EVENTS
~
STATUS
SUMMARY

|
|
|
|

[SINK NODE node-id]
[KNOWN SINKS]

- —
--

|
|

MODULE CONSOLE

|
|

CHARACTERISTICS
SUMMARY

———————

Network Control Program (NCP)

Page 114

e
—— e +—-———_——————————————— -

MODULE CONFIGURATOR

STATUS

[KNOWN CIRCUITS]

SUMMARY

[CIRCUIT circuit-id]

e
+

|
|

MODULE LOADER
MODULE LOOPER

————— +t-———

|
|

e —_——— e

KNOWN plural

entities

are

all

those

state.
ACTIVE and SIGNIFICANT
defined in the glossary.
When
display
1is
returned
first,
returned last.

Sections 2

and 4.1.1 describe the

SUMMARY
returns
specified entity.

the

known

to the

system,

regardless

plural entities are subsets of KNOWN as
displaying plural nodes,
the
executor
1f
1t is included. Any loop nodes are
|
|

information types,

most important
|
|

except

information

The tables 1in Section 7 specify the parameters
returned for each information type and entity.

and/or

Qualifiers can be placed either before or after the
When
a
qualifier
1s
not specified in
a command,
"KNOWN" qualifier.
An
additional
qualifier
<can
entities:
|

SUMMARY.

relating

counters

the

information
type.
the default is the
be
used
for
all
|

TO alternate—output
This qualifier directs
device

(for

example,

the output
a disk

file

default terminal display.
The output
would
have on the
terminal.
The
specification is system-dependent.

When there is no
the

phrase

4.3.8.1

"no

alternate

line printer)

is text
format

information to display

information"

1is

displayed

output

in the
of the

rather

file

than

the

same
format
it
alternate output

in response to a SHOW command,
in

place

the

data.

Information Type Display Format

All of the SHOW and LIST command
same

general

REQUEST

For example:

output

format.

The

1information-type
header
of

that

options

format

‘have

the

is:

n; entity information-type AS OF dd-mon-yy hh-mm

| |

REQUEST

21; KNOWN LINES STATUS AS’OF 8-JUL-79 10:55

REQUEST

43; EXECUTOR NODE CHARACTERISTICS AS OF'lO—SEP—79 10:56

REQUEST

45; KNOWN NODES SUMMARY
AS OF 10-SEP-79 10:57

The requested information follows the header.

The genefal

format

Network Control Program (NCP)
the

information

Page‘llS

1is:

entity-type
=

entity-id

data

If the rentity
precede 1it.

type

NODE,
|

then
«

one

EXECUTOR,
|
|

REMOTE,

This information format repeats for each individual entity.
LIST command with

4.3.8.2

Counter

information

Display

type

should default

LOOP must

A SHOW or

SUMMARY.

Format

Counters are 1identified by standard type numbers as defined in
Tables
6-8,
11-13,
18,
and
19,
Section
7.
Counters
are
dlsplayed in
ascending order by type.
Thn dlsp1ay format for counters is:

value description(, INCLUDING ]
qualifier-1

qualifier-n

The value is the value of the counter, up to 10 digits
for
a
32-bit
counter.
It
1s a decimal number with no leading zeros.
Zero values
distinguish the case of no-counts from the case where a counter is not
kept.
If the counter has overflowed, 1t 1s displayed as
value minus one, preceded by a greater-than
sign.
For
overflowed 8-bit ‘counter would be displayed as ">254."

the overflow
example,
an
|

The description 1is the standard text that goes with the
counter
type
as
defined
1in Tables 6-8, 11-13, 18, and 19.
If the counter type 1s
not recognized, the descrlptlon "COUNTER #n" 1s used, where n
1s
the
counter type number.

If the counter has an associated bit

map,

the

word

"including"

appended
to
the description, with a list of qualifiers.
A qualifier
is the standard text for the bit position
in the bit map.
A qualifier
1s
displayed
only
1f the corresponding bit is set.
If the standard
text for the bit 1s not known the qualifier "QUALIFIER #n"
1s
used,
where n 1s the bit number.
|
For

example:

REQUEST #21;

CIRCUIT COUNTERS AS OF 20-MAY-83 15:29

CIRCUIT = DUP-6

532

416
0

TERMfNATING PACKETS RECEIVED

ORIGINATING PACKETS
TERMINATING

SENT

CONGESTION

LOSS

Program

Page

400

TRANSIT

353

TRANSIT

PACKETS
PACKETS

TRANSIT

CONGESTION

523789

BYTES RECEIVED

41640

BYTES

SENT
DATA BLOCKS
DATA BLOCKS

963
423

4,3.8.3

(NCP)

RECEIVED

SENT

LOSS

RECEIVED
SENT

DATA ERRORS INBOUND, INCLUDING:
NAK'S SENT REP RESPONSE

DATA ERRORS

Tabular

and

Sentence

116

OUTBOUND

Formats

Non-counter information permits two general
formats.
The
first
1is
easlier to scan, the second 1s more extensible.
The first 1s a tabular
form, with each individual entity fitting on one line under
a
global
- header.
Using
this
form,
unrecognized
parameter
types
are more
clumsily handled and the amount of information per individual
entity
1s
limited
to
what
will
fit
on one output line.
The second is a
sentence form.
It adapts easily to a large number of
parameters
per
individual entity and readily handles unrecognized parameter types.

In either

form,

the order of parameter

implementations,
parameters may be
parameters 1s:

even
though
unrecognized.

output

1is

the

same

all

1n
a
particular implementation, some
The output
format
for
unrecognized

PARAMETER #n = value
where n is the decimal parameter number and
value, formatted according to 1its data type.

value

1is

Section 7 describes parameter types and their output
sentence
form
of
output,
parameters
that
are
together should appear on the same
line.
Section
logical groupings.

The general

output format

the data

for

tabular

the

order.

form

is:

parameter-type

parameter-type...

entity-1d

parameter-value

parameter-value...

REQUEST

39;

KNOWN CIRCUITS

CIRCUIT

STATE

BOSTON-0

in tabular
STATUS

form follows:
OF

the

logically
grouped
7
details
these

entity-type

An example of output of the data

parameter

18-SEP-78

15:20

Network Control

Program

CHICAGO

NCP did

Page

117

OFF

CORUNNA

(NCP)

not

ON-LOADING

recognize

specify
the
type
the parameter data
numbers. )

adjacent

node

parameter,

the

output

would

number of the parameter and the value according to
type.
(See Tables 6 to 10,
Section
7,
for
type

The general output format of the data for sentence form is:
entity-type

entity-id

par-type

par-value,

par-type

par-value,

...

par-value,

...

An example of output of the data for sentence form follows.

REQUEST #39;

KNOWN CIRCUITS STATUS AS OF 18-SEP-78

CIRCUIT = BOSTON-0
STATE
CIRCUIT

=
=

STATE

CIRCUIT

STATE

The

output

For

example,
-

SHOW

‘

ON
CHICAGO

OFF

CORUNNA

format
for

for the logging entity
the following command:

LOGGING}CONSOLE

SUMMARY

KNOWN

dlffers

SINKS

A correct output would be

Logging Summary as of 7—MAR—79 10:55
Logging

15:20

CONSOLE

State

ON,

NAME

COO0:

Sink node = 15 (HALDIR), EVENTS =
0.0,6
Line KDZ-0-1.6,
3.6-13

Sink node
0.0

3.6-7

(EOWYN),

Events

the

event

display.

(NCP)

Page 118

Line KDZ-0-1.6,

4.3.8.4

Restrictions

6.0-1

and Rules

on Returns

The following restrictions and rules
entity information type commands.

apply to

returns

on SHOW and

LIST

Node parameters.
The parameters displayed for the
SHOW
and
LIST
NODE commands depend on which node is specified.
Table
20, Section 7, indicates these
restrictions.
The
keywords
EXECUTOR,
REMOTE or LOOP must precede NODE 1in a display of a
node to clarify what 1s displayed.

Line and circuit states.
The returns on the
LINE/CIRCUIT
STATUS
commands must show the
well

the

state.

Loop nodes.

SHOW
and
LIST
link substate as

Information for a single

loop node

returned

when
requested
by
the
1loop
node
name.
Information for
multiple loop nodes is returned at the end of the display for
KNOWN
or ACTIVE NODES.
It is the exclusive display for LOOP
NODES.

4,3.9
These
zero

Counters.

Events.

commands,

COUNTERS can

and with

line,

only

circuit,

EVENTS applies only to

node
1identification
must
be
exists), even for the executor.

displayed

module,

the

with

or node

1logging

the

entity.

address
-

and

name

counters

to be

set

SHOW

entities.

(if

Sink

a name

ZERO Cdmmands
commands

cause

command generates

specified
a

counters

set

zeroed

event

that

causes

zero.

counters

be logged before they are zeroed.
The counters zeroed are
those
the
executor
node
supports for the specified entity.
The command format
1S:

|
+

|
|
|

|
|

|
A

CIRCUIT circuit-id

EXECUTOR
LINE line-id
KNOWN CIRCUITS

KNOWN LINES

KNOWN MODULES
KNOWN NODES

I
I
|
I

MODULE module-name
NODE node-1id

Network Control Program

Network

For

Control

module

Program

X25-PROTOCOL

(NCP)

the

Page

following

qualifiers

are

119

added:

KNOWN DTES
DTE

dte—address

If only one local DTE address
than one local DTE address is

4.,3,.10

This

EXIT

command

is known, it is the
default.
" If
more
known, the parameter must be included.

Command

terminates

NCP

session.

Network Management Operation
5

Page 120

NETWORK MANAGEMENT OPERATION

This section specifies the functionally-correct operation
of Network
Management.
Implementations
may
use
algorithms
other
than those
The
here.
contained herein, as long as the function is as specified
operations described in this section are:

NICE Access Routines and Listener (Section 5.1)
Local Network Management Functions (Section 5.2)
Link Watcher (Section 5.3)
|
Data Link Service Functions (Section 5.4)
Event Logger (Section 5.5)
Down-Line Load (Section 5.6)
Up-Line Dump (Section 5.7)
Trigger Bootstrap (Section 5.8)
Loop Test (Section 5.9)
Change Parameter (Section 5.10)
Read Information (Section 5.11)
Zero Counters (Section 5.12)
Loopback Mirror (Section 5.13)

NICE Logical Link Handling

(Section 5.14)
Algorithm for Accepting Version Numbers (Section 5. 15)
Return Code Handling

(Section 5.16)

For Ethernet circuits there is a special algorithm necessary 1n
some
the
when
Operations
Load
or
Dump,
Trlgger
for
needed
1s
It
cases.
Ethernet address is not contained in the request.
In this case, there
are
two
possible
Ethernet addresses: the hardware address from the
node data base,

the

expansion of

the DNA node address.

To choose which of these addresses
to use, the executor runs a normal,
single
message
loop
test to the hardware address.
If this does not
succeed within 2 seconds, the executor aborts it and
tries
the
same
loop
test
to
the
expanded
DNA
address.
If this does not succeed
within 2 seconds, the executor
repeats
the
entire
process
3
more

times.

If at the end of this procedure no response has been received,

the original

received,

request

request.

5.1

fails with a communication error.
If a
response
Ethernet
address is used to satisfy the original

that

NICE Access Routines

and Listener

The Network Management Access Routines receive NICE commands from
the
Network
Control
Program (NCP) and user programs.
Network Management
Access Routines pass NICE messages to
the
remote
or
local
Network

Management
Listener via logical links.
They also pass local function
requests to the
Local
Network
Management
Functions.
The
Network
Management
Listener
receives NICE command messages via logical links
from the Network Management Access Routines in the local
node
or
1in.
other

nodes.

The method used for processing Network Management functions
single

node

1is

1mplementation-dependent.

The

Network

within

Management

Network Management

Operation

Network

Access Routines can pass all

local

function

requests

the

121

Local

Management Functions.
Alternatively, the access routines can
pass NICE messages to the Network Management Listener
via
a logical
link.
The latter method cannot be used for functions, such as turning
the network .on, that occur before a logical link is possible.

5.2
The

Local
Local

requests
O

Network Management
Network Management
other modules:

Functions
FUHCthHS

receive

the

SYstem—independent function requests from the local
the Network Management

Access

NICE function requests
Management Listener.,

from

Automatically-sensed

from

Routines.
other

other
O

types

NCP

via

nodes

via

the
|

Network

local

node

via

the

Network

requests

from

the

service

The Local Network Management Functions have the
to

following

from

NICE function requests
Management Listener.

Page

modules

the

Link Watcher.

following

interfaces

layers:

Maintenance
Functions
The
Local
Network
Management
functions
have
1interfaces
to
the Maintenance Functions as
described
in
the
DNA
Low Level
Maintenance
Operation

specification.

Link
Service
Functions
The
Local
Network
Management
Functions
have
a control interface to the Data Link Service
Functions for setting and changing circuit and
1line
states.
The
Local
Network
Management
Functions
have
a "user"”
interface to the Data Link
Service
Functions
for
handling
functions
that
are necessary for service functions (such as

up-line dumping,
to

down-line

loading,
and

line

level

testing)

be performed.

Control interfaces
to
lower
layers
The
Local
Network
Management Functions interface with lower layers directly for
control
and
observation
of
lower
level
counters
and
parameters.
An
example of such an interface 1s examining a
node counter,
|
Function requests to lower
layers
and
to
local
operating
system
The
Local
Network Management Functions pass such
function requests as file access, node
1level
1loopback,
and
timer
setting
to
the
application
1layer
or
to the local
operating system 1n the form of system-dependent calls.

- Network Management

Operation

Page

122

Event
logging
The
Local
Network
Management
Functions
interface with the Event Logging module in order to set event
logging parameters that control such things as
which
events
are logged and at what sink node they are logged.

Sections 5.6 to 5.16 supply algorithms for-handling Network Management
function

5.3

requests.

Link Watcher

The Link Watcher module senses data
up-line
dump
or load coming on an
adjacent node.

link
level
service
requests
to
exclusive maintenance
link from an

The Line Watcher senses a request by calling

the

Data

Link

Service

Functions.
Using parameters from that message, the Link Watcher then
determines the request type and calls
the
Local
Network
Management
Functions to accomplish the request.
St

The algorithm for
Call

Link Service

Set

link

implementing

link
Link Service

i
S
e

the Link Watcher

Functions

to get

is as

Data Link Service

requested

state

to perform needed
|

(Local Network Management

ENDIF

5.4

for

the

Functions)

Section 5.10 describes the algorithms for setting»and
states

for

(Local Network Management

Functions)
Determine function needed
Call Network Management Functions

to ON

request

to ON-AUTOSERVICE

function(s)
Reset link state

follows:

Link Watcher.

resetting

1link

malintenance

link

Data Link Service Functions

The Data Link Service Functions

provide

exclusive

Down-line

Up-line dump

state
changing and
1link
handling
services.
They
are
used
functions requiring a direct interface to the Data
Link
layer.
functions that use the Data Link Service Functions are:

Trigger bootstrap

Link

test

load

(Section

5.6)

5.7)

(Section
5.9.2)

5.8)

for
The

Network

Management

Passive

Set

Data

Link

link

Page

123

state

Service

the

target

(Section

Functions

node

(for

unattended

system)

5.10)
provide

the

following

services:

Condition a node to be dumped, loaded or have a loopback test
performed.
This
state of the target node is called service
slave mode, a mode in which the
entire
processor
1is
=-aken
over.
Control rests with the executor.

Notify a higher level that active link services (load,
are

aump)

needed.

Provide transmit/receive interface to higher level for active
link

Section

5.4.1

Active at the executor node

The

Operation

3.6

services.

describes

States

and

line

and

circuit

states

and

substates.

Substates

arbitrate the use of the link, Data Link Service Functions maintain
and
substates.
Table
4,
following, shows these as well as
corresponding link states and substates displayed with
the
NCP
SHOW
CIRCUIT/LINE
STATUS
command.
Table
4 also shows related Data Link
Service functions.
‘

states

The

link

can

from

any

substate

Table

Line

Service

Their

Link

States,

State

Substate

and Functions

Link

Link Service
Function 1in
Progress or

State

Substate

Allowed

idle

|
-STARTING

-REFLECTING
-

-LOADING

and

States

Link
Service

passive

~ON

mode.

Link
Service

slave

Substates

Relationship

Link

service

Pass

message

higher

passive

1dle

Pass

message

passive

|
reflecting

higher
Passive

level
loopback

open

Receive

and

transmit
-DUMPING

open

dump1ing

Receive

and

transmit

dumping

messages

-TRIGGERING

open

triggering

Receive

messages

level

and

Network Management Operation

Page 124
transmit
triggering
messages

open

-~-LOOPING

looping

Receive and

messages
|
Pass message to

transmit

~AUTOSERVICE

closed

1dle

ON
ON
|

-REFLECTING
—~AUTOLOADING

closed
open

reflecting
loading

ON
On

open

~AUTOTRIGGERING
|
|

dump1ing

open

messages

Receive and

transmit dumping

triggering

messages

Receive and
transmit
triggering

TMm

SERVICE
|

SERVICE
SERVICE

closed

-REFLECTING
-LOADING

SERVICE

closed
open

-DUMPING

open

idle

reflecting
loading
|

-~-TRIGGERING
|

SERVICE

- open

~LOOPING

open

5.4.2

Pass message.
to
higher level

Passive loopback
Receive and
transmit

Receive and

transmit dumping

messages

triggering
|
|

Receive and
transmit
triggering

messages

looping

Receive and
transmit

OFF

QAo
c

messages

dumping

SERVICE
|

level

Passive loopback
Receilve and
transmit .oading
~

-AUTODUMP ING
|

higher

loopilng

looping

messages

of f

idle

Priority Control

The Data Link Service Functions must make sure

that

higher

priority

functions
take
over,
and
that lower priority functions are resumed
when higher priority functions are complete.
The
priorities
are
as
follows from highest (1) to lowest (5):
‘

Enter service slave mode (MOP primary mode)

for passive

line

No line operation

implementations,

this

loopback, receiving down-line load, sending up-line dump, and
transferring control.
Control rests with the executor
node.
Some implementations may require hardware support.
is

the

(off state).

first priority.

In some

Network Management Operation
3.

‘Page 125

Active
service
functions
(send
down-line
1load,
trigger
bootstrap,
receilive
up-line
dump,
perform
active
line

loopback) .

5.4.3

Passive

Normal

line

loopback.

operation

(line

available

for

use

by owner).

Link State Algorithms

The algorithms
Link
Service

that follow are a model for implementation of the
Data
states.
If
these algorithms are followed, tne proper

state transitions will take place.
The algorithms refer to
maintenance
mode.
This
1is a Data Link layer mode (DDCMP
specification).
|
|
Set

link

state

off:

Call Data Link to halt
Set substate to 1dle

Set

link state

Data
Link
functional

link

to passive:

IF link state is off or closed
IF

substate 1s not reflecting
Set substate to 1i1dle

ENDIF

ELSE

Fail

Set

link state to closed:
IF

state 1s off, passive, or open
1link state 1s off or passive and substate
reflecting
Call Data Link to set link mode to maintenance
Set substate to 1idle

ENDIF

link
IF

ENDIF

ELSE

Fail
ENDIF

Set

link

state

open:

link state 1s passive or closed
Call Data Link to set link mode
IF substate 1s reflecting
Terminate passive loopback
ENDIF

Record

substate

to maintenance
-

according

open parameter

not

Network Management Operation

Page 126

ELSE

Fail
ENDIF

NOTE

The Data Link call to set the link mode to maintenance
is
a single operation that will succeed regardless of
the state in which Data Link has
the
1line
when
the
call

5.4.4

1ssued.

Link Handling

Functions

The link handling services of the Data Link Service Functions and
algorithms

for

implementing

them

follow.

Handling link in passive state (for

mode,

passive

loopback

entering

and passing

message

service
to

a higher

level):

WHILE

link state 1is passive
Call Data Link to see if

link mode

has

gone

maintenance
IF link mode

Call
IF

has gone to maintenance
Data Link to receive the service message

enter

service

Enter

slave mode message

service

slave mode

ELSE

IF loop data message
Perform passive loopback

ELSE

looped

algorithm

data message

Ignore

ELSE

On request,
ENDIF

pass message

higher

level

link state 1s still
Call Data Link to

passive
halt link

ENDIF
ENDIF

ENDWHILE

Handling link in closed state
(for
entering
mode and performing passive loopback):
WHILE

link state 1s closed
Call Data Link to receilve message
IF

enter service slave mode message
Enter service slave mode
ELSE IF loop data message
Perform passive loopback algorithm
ENDIF
ENDWHILE

service

Network Management Operation_
3.

Page 127

Handling link in open state (for entering service
receiving a messagde, and transmitting a message):
WHILE

link state
IF transmit

data

mode,

1s open
requested

Call Data Link to transmit
IF receive requested

ELSE

slave

overrun

Return

recorded

data

ELSE

message

overrun

error

Post

receive

requested

ENDIF
ENDIF

Call Data Link to receive message
IF enter service slave mode message
Enter service slave mode
ELSE

recelive

Return

posted

message

ELSE

Record

data

overrun

ENDIF
ENDIF

ENDWHILE

4.,

Handling passive link loopback
target

node):

(passive
|

the

remote
<

(Initial message already received)
Set substate to reflecting
WHILE substate is reflecting
IF loop data message

Call Data Link to transmit looped data message with
received data
Call Data Link to receive a message
IF timeout or start received or error or loopback

terminated
Set substate

ENDIF

1idle

ELSE

Set

substate

1idle

ENDIF
ENDWHILE

5.5

Event

Logger

This module,

diagrammed

Figure

following,

records

events

that

may
help maintain the system, recover from failures, and plan for the
future.
Events originate in each of the
DNA
layers.
Section
7.12

specifies event parameters.
A system manager controls event recording
with the SET LOGGING EVENT event-list command.
The event list entered
may
require
the
Event Logger to filter out the recording of certain

Network Management Operation

Page

128

_events.

—

———

W—

—_—

—

——

—

w—

—

A _________

|
|
from

Event

Transmitters

Event

Receiver

———

|
|
|

|
|
|
.|
| |

|
|
|

ty—

—

——

———

—

—pan

O_'

"\
Event

Filters

vents

|
|
"-—->|

Event

Logging

specified
logged

to be

| Event

|
|

Interface |
e '
=== .

= -------- '

:
:

Event
Queue

e .

|
| Event
o
|->| Transmitter |---

to
event
receivers

Queues

——————

Event
Queue

|
|
|->|

Event
Transmitter

|[<------- raw events

Architectural

to meet

the

Model

following

to multiple

logged

Event
Monitor

________ t

Event

|-->|
|

->| Queue [|->: Event
e'
File

|
|
- >|

Allow events to be
the source node.

Allow an event
sink node.

| <—=—~ ---|

DECnet Event Logging

Event
Queue

|
|
|

|
|

Figure

|
|

AYERS

|
|

|------ > |
|
|

______ '

|
|
|
|

R
T
|
|

O———=——————-- :
Event
Processor |
|
O=——==== :
|

—

| -->|
|--.|

|
|

d——

Event
Queue

Event
Recorder

| ]
.V

——————

| -—>|
|.->|

to multiple

sink

goals:

nodes

logging

including

sinks or

any

|
|---

Network

Management Operation

Allow the definition of subsets of events
node by event type and source node.

Include the following
monitor program.

1logging

sinks:

Allow sharing of sinks
between
local system event logging.
Minimize
required

Never block
progress
of
network
logging performance limitations.
of

Record loss of
limitations.

event

even

logging

sink

event
|

network

file,

and

logging

and

communication

functions

due

event

information

due

resource

1information

due

resource

When required due
to
resource
information
(which can often be
status) in favor of older.
Minimize impact

console,

network

©processing,
memory, and
to provide event logging.

Minimize loss
limitations.

for

Page 129

limitations,
discard
newer
regained bv checking current

an overloaded sink on other

sinks.

Standardize content and format of event
logging
1information
to the extent practical, providing a means of handling system
specific information.

Allow independent control of sinks at

sink

node,

including

the

following

sink
identification and sink state.
Sink states include use
of sink, non-use of sink,
and
temporary
unavailability
of
sink.

5.5.1

Event

Logger

Components

As shown in Figure 6, the
Event
Logger
- components, described in this section:
O

Event

queue

Event

processor

Event

transmitter

Event

receiver

Event

recorder

consists

Network Management

Operation

Event console

Event

Event monitor interface

Event

Page

file

monitor

Event queue —— There are several event queues (Figure
buffers events to be recorded or
and emptying of the queue.

transmitted,

following

event

130

queue

component

has

the

6).

and controls
|

It buffers events on a first—inffirst—out basis.

It fills a queue with one module;

It ensures
attempting

see

Since event queues are not of infinite length, events
The
filling
module must record the loss of an event

the

IF queue 1is
Discard

an error

must
as an

third characteristic above.
event.
An
event queue:

filling

empties it with another.

that the filling module does not
to put an event on the queue.

as an error because of

the

one

characteristics:

called
an
"events-lost"
following algorithm at each

Each

This

1implementation
|
|

when

be
lost.
event, not

event

1is

requires

the

full
the event

" ELSE
IF

this event would fill the queue
"Discard the event
IF last event on queue 1S not "events lost"

Queue

"events-lost"

event

(whlch

fills

the queue)

ENDIF

ELSE

Queue
-

the

event

ENDIF

The
the

event queue component
following rules.
1.

Consider
such
"processed"” for

handles

events

"events-lost"

events

according

"raw"
for
raw
event gqueues.

event

queues

and

processed

Flag such events for the sink types of the lost events.

Time stamp such events with the time of first loss.

Filter

such

filtered.
filtered

Event Processor

events

only

Specifically,
unless

all

other

all

events

for

the

this means

that

events

filtered.

are

queue

event

0.0

are

also

cannot

This component performs the following functions:

Network Management Operation

Scans the lower level

Modifies
raw
events
contain the following

event

records.

EVENT

CODE

Processed

ENTITY

events

queues,

collecting

1nto
processed
fields:
IDENTIFICATION

contain

the

events.

Raw

event
events

fields:

EVENT

SOURCE

SINK

ENTITY

DATE AND

CODE

NODE

FLAGS

NAME

TIME

raw

DATA

following

Page 131

STAMP

DATA
|

Compares the processed events with the event filters for each
defined sink node, including the executor.
Following are the
characteristics of the filters used to control event logging:
o

The

event

Each event
source

source

node maintains

sink node

has

node.

a
»

all

separate

filters.

set

filters

the

Each sink node set of filters contains a set

Each sink node set of filters contains a
set
of global
filters, one global filter for each event class.
It also
contalns
one
or
more
specific
filters,
each
for
a
particular entity within an event class.

Each filter contains one bit for each event
type
within
the class.
The bit reflects the event state:
SET 1f the
event 1s to be recorded, CLEAR 1if 1t 1s not.

The filtering algorithm sees first 1f there 1s a specific
filter
that applies to the event by looking for an event
mask whose
source
qualifier
matches
the
entity
name

for

each

sink

field.

If not,
class.

the

(monitor,

so,

file,

console).

filters

the algorithm uses the specific filter.

algorithm uses

the

global

filter

for

the

Commands from higher levels
create
and
change
filters
using
the
EVENTS
event-list option.
When the specific
filters match the
global
filter,
the
event
processor
deletes specific filters.
|

Although the filters are modeled 1in the event
processor,
in
some
1implementations,
to reduce information loss or
for efficiency reasons, i1t may be necessary
to filter raw
~events before they are put into the first event queue.
A
reasonable, low-overhead way
to
1implement
this
1s
by
providing
an
event on/off switch at the low level.
The
high level can turn this
switch
off
1f
the
event
1s
filtered
out
by
all
possible
filters.
This avolids a

Network Management

Operation

complex

Page

filter data base

prevents flooding

the

search at

low level

the

low

132

level,

Dbut

event queue with unwanted

events.

Passes

events

executor

nodes.

not

filtered out

the

the event

recorder

appropriate event queue

Event Transmitter.
Using a logical
1link,
event
records
from its queue to the event

for

the

for other

sink

this
component
receiver on its

transmits
associated

sink node.

Event

Receiver.

links
passes
Event

from
them

Recorder.

various
the

This

event
to the

component

event

Event

File.

This

coplies

events

append-only

is the event
recorded.

1is

the

are

event

then

queues

for

the

the sink flags

logging

sink

which

Network

human-readable

machine-readable

Management,

and may take

for

5.5.2

Formats

Following‘ are

The date field
context of the

Milliseconds
do
so.
If
possible for

algorithms

suggested

variations
terminology

reading

module
using

for

are

Logging

text

that do not
are allowed.

in the output is
logging output.

higher

has

seen.

undefined

for

the

Its

near

formats

for

obscure

optional

order.

the

logging

data.

necessary data

format:

event-text]

System
change

obvious

from

the

if it is
possible
to
not be printed.
It 1is
be logged and
printed
|

class.typel,

specific

term.

Data

can be used in the event time data
not
supported,
this
field will
two times given the same second to

EVENT TYPE

levels.

1s an "operator's
helper."
It
the
Network
Management Access

action based on what

and

Suggested

This interface makes events available to the

Functions

responsibilities

General

according

logging

recorded.

Event Monitor.
This user layer
monitors
1incoming
events
by

logical

nodes.

Event Monitor Interface.

out

events

over

source

file.

Network Management

specific
standard

sinks

records

event

records.

Event Console.
This
copies of events are

Routines

event

remote

This module distributes

implementations,

event

receives

transmitters 1in
event recorder.

Network Management Operation:

FROM NODE address[ (node-name) JOCCURRED
|
[entity-typelentity-name]]

)

Page

133

[dd-mon-yylhh:mm:ss:[. uuu]

[data]

For

example:

Event

type

From node
- Packet

Event

header

type

From node
Line

4.7,

Packet

27 (DOODAH),
=

0.3,

ageing

KDZ-0-1.3,

9-FEB-79

13:55:38

Automatic

(ELROND),

discard

occurred

line

service

occurred 9-FEB-79

Service

Load,

Status

16:09:10.009

Requested

Or, on a node that does not recognize the events:
Event

From

type 4.7
node 27, occurred

- Parameter

9-FEB-79

—
13:55:38

Event

type 0.3
|
|
From node 19, occurred 9-FEB-79 16:09:10.009
Line KDZ-0-1.3, Parameter #0 = 0, Parameter #1

5.6

Down-line

requirements

for

a down-line

load

are

The target node must be directly
node via

a physical

link

level

The

target

(refer

Load Operation

The down-line capability allows the loading of
file to a target node.
The file may reside at
another node.
Any node can 1initiate the load.
The

link.

The

a memory image
from
a
the executor node or at

follows:

connected

executor

the

node provides

access.

executor

the data

node must

running

a minimal

cooperating

program

to the DNA Low Level Maintenance specification).

program may be

a primary loader

from

bootstrap

ROM.

This

The

down-line load procedure may actually involve loading a series
of programs, each of which calls the next program
wuntil
the
operating
system
1itself
1s
loaded.
The
1nitial
program
request

information determines

The direct

access

1link

the

load

involved must be

file
1n

contents.

the ON

SERVICE

state.

The executor must have access to the file.
The
location
of
the file can be either specified in the load request or looked
up by the Maintenance

Functions.

'Maintenance Function modules are used to obtain
Remote

files

are obtained via remote

1local

file access

files.

techniques.

Network Management

Operation

Page

134

(Refer to the DAP functional specification.)

Figures 7A and 7B,
access
The

be
The

for

executor

either

load.

must

access

local

target

operation

following,

down-line
have

node

with

show

1local

and

remote

node

data

base,

which

must

software

able

EXECUTOR

recognize

hardware

must

the

trigger

triggered

Network

NODE

Management|------—————--——- |

Layer

Local

File

Accessing

Processes

|
|

———

System

NODE

LEGEND:

—

Maintenance

Operations Protocol

f o

MOP

Figure

7A.

can

remote.

locally.

~--——------—-|

file

Down-Line

Load

Local

File Access

Operation

Network Management Operation

Page 135
EXECUTOR

Network

NODE

Local File

|
|
I

S ———— | Management|-----——-—-—-—--—-—--- | Accessing
|
:
| Layer
|
| Processes

|
|

|
:

|
[
A
I
|
e | ——m———— "
L | -.
S ———
- | ———
|
[
RS
e.
|
|
TARGET
|
|
|
| HOST

|
|
MOP
|
NODE
|
||
|
|
|
-'
|
—————————————————————— "
|

LEGEND:
MOP - Maintenance Operations Protocol
FAL - File Access Listener

Figure 7B.

|
|
|
|

|
FAL
|
|
|
e'
|

Be'

|
|
|

File
System

|
|
|

NODE

v
o —————- .
Local

|
|
|
|

|
|

|
|
|

Down-Line Load Remote File Access Operation

Either the target or executor node (or
a
remote
command
node)
can
initiate
a
down-line
load.
The
target node initiates the load by
triggering
its boot ROM.
The executor node initiates
the
load
with
If the executor does not
a trigger command or a load request.
either
have the initial program request or the target does not respond to the
attempt to load

it,

the executor should trigger the target.

Once the target is triggered, it requests
the down-line
load.
The
node may be programmed to request the load over the line on
target
which the trigger message came.
Or, the target node could request the
load
from
another executor.
The Link Watcher at the executor senses
for
the first program request from the target node (usually a request
was
operation
the
if
Or,
below).
described
loader,
secondary
the
initiated by a Network Management load request, the program request 1s
received as
a response to that request.
Figures 8A and 8B, following,
show the down-line load request operation.
|

Network Management Operation

Page 136

EXECUTOR NODE

|
|

| Management
| Function

|
|
|------------->|

Line

Watcher

Local
Network

——_——_—_—————

TARGET
NODE

|
|

s'
|

——————— .

|
|

- '

|
|

m—

—

ct—

|
—————————— >|

|
S

Target-Initiated Down-Line

EXECUTOR

NODE

|
|

e '

Local

Function

| Network
|
|
——————————— | Management|--------------|

——— emmeman

——

—a—

———

Figure 8B.

Routines

COMMAND
NODE

osm——

—

|
|

m—

Network

Management
Access

S—

|
|

——

———

————

TARGET

NODE

——

——— ——

———

)

S—

——

Y e e

Management
Listener

——

Network

—

Operation

|
|
|

Load Request

8A.

Figure

Operator-initiated Down-Line Load Request Operation from a - /}
Remote

Command

Node

Network Management Operation

Page 137

The executor proceeds with the load according to the
initial

options

request.

the
|

may be
Several fields in the NICE request down-line load message es
1in the
" either furnished as overrides or defaulted to the valu
left
tion
Dump/Load Server portion of the node data base. Any informa
to default is first obtained from the data base.

.
The executor identifies the target node by address, name, Or circuit
those
to
des
The name and address parameters may be supplied as overri
in the data bases. The address or link identification key into the
If link is used, then address is obtained from the
node data base.
address 1s
data base entry. If a target is identified by name, then key
1into the
to
determined by normal name to address mapping and used
data

base.

durilng
The address the target is to have 1s always sent to the target
elther
is
s
addres
the down-line load request operation. Thils target
e.
obtained from the node data base or supplied as an overrid

is to have, if any, is either supplied with the
The name the target
request as an override or obtained by normal address-to-name mapping.

ication.
Host identification follows similar rules to target identif
name and
both
If
The host node address must be sent to the target.
base.
data
node
the
address are not supplied, address is obtained from
not
1f
,
mapping
ame
Name, if any, is obtained by normal address-to-n
-

supplied.

The executor controls the process of loading

the

requested

programs

responsible for
until the operating system is loaded. The executor is from
and to the
MOP)
e,
understanding the service protocol (for exampl

The first program to run
loader,

1is

target.

1in

the

target

node,

called

the

primary

typically loaded directly from its own bootstrap ROM.

program 1in the
then requests, over the communications line, the next may
have certailn
,
loader
This program, the secondary
sequence,
lities of
capabi
the
on
ing
restrictions on the way it is loaded, depend
tertiary
a
h
throug
extend
This process may
the primary loader.
ing
operat
the
as
d
define
is
loader. The final program to be loaded
a
being
of
e
capabl
be
to
system, although it does not necessarily have
ing
includ
bly
(possi
s
proces
network node. Within a single down-line
"loader loads") each program loaded is expected to request another,
except for the operating system, which does not.

words, the
Wwhen the down-line load has been completed (in other
error, the
an
to
due
d
aborte
or
operating system successfully loaded)
to finish
node
d
comman
the
to
executor sends the proper response back

~up

the process.

The content of the load image file is specified 1in Appendix E.
The algorithm for handling the down-line load is as follows:

Network

Management

Call
Call

The

Up-line
up-line

system

Page

Data Link Service Function to open link for
Maintenance Functions to perform load.
Data Link Service Function to close line.

Call

5.7

Operation

Dump
dump

dump

138

load.

Operation
capability

1ts

memory

the

file

Network
on

Management

network

layer

allows

node.

The‘requirements for such a dump correspond with those for a down-line
load:

The system being dumped must be

(executor)

The

connected

by
a specific physical

link.

network

node

system

being dumped must run a minimal cooperative program
can
communicate
over
the link with the executor.
The
protocol used
1s
in
the
Low
Level
Maintenance
Operation

that

specification.

the

executor

determines

must

supply

that

the

dumper.
0

the

The

link used must be in the ON or
afterwards to its original state.

The

executor

the

remote

SERVICE

possibility

e€xecutor
or

DUMP

and

command

this

Functions

Routines

dump

can
node

case,

receive

the

Network

pass

the

at
dump

executor

state

and

returned

node.

initiate

the

executor

request

from

Management

dump

node's

the

Maintenance
network
not

Functions

remote

respond,

secondary

the

dumping

Functions

file

and

the

then

local

transfer

executor

can

aborted,

memory

the

has

executor

Dbeing

senses
Local

facilities.

Local

Network

NCP

Management

according

that
base.

the

system's
If

the

remote

has

to
been

The

the
left

Local

dump

using

file

system

remote

system

system
and

the

or
does

load

initiated by the target node,

dumped

the

with

been

sends

operating
the

node
the

Listener.

accomplish

trigger

program.

In cases where the dump was not

requested

Functional

Network

Local
Network
Management Functions
proceed
options
in
the request.
Any required information
to default is first obtained from
the
node
data
Management

dump.
using

Alternatively,

the

The

Network

the
data

capable

the executor
request
to

can

then

secondary

Functions
at

remote

command.

Management

Access

Management

there,

the

have access to the file receiving
remote, the executor transfers the
access routines.
(Refer
to
the
DAP

The system to be dumped can indicate
that
dumped.
In this
case, the Link Watcher

the

not
1s

Specification.)

Network

This

must

file
file

program

program.

appropriate

file

response

the

back

dump

when the
has

the

been

node

Page 139

Network Management Operation
requesting the operation.

d Appendix E.
The content of the dump file is specifiein
The algorithm for performing the up-line dump is as follows:

Call Data Link Service Functioh to open line for dump.
Call Maintenance Functions to perform dump.
Call Data Link Service Function to close line.

5.8

Trigger Bootstrap Operation

The trigger bootstrap

capability

the

Network

layer

Management

‘allows remote control of an operating system's restart capability.
Since a system being booted is not necessarily a fully functional
network node, the operation must be performed over a specific physical

The node on the network side of the link 1s called the executor
|
|

link.
node.

trigger

bootstrap

function

Management

Functions

The NCP TRIGGER command can initiate the
via

the

Network

Access Routines.

Management

The

Local

Listener

Network

executor node receive the request.

and/or the Network Management

the

Wwhen the Local Network Management Functions receive a NICE trigger
bootstrap request, they proceed according to the options 1n the
request. Any required information which has been left to default 1s
obtained from the node data base.

The physical 1link being used must be in the ON or SERVICE state at the
executor

node's

end.

perform the operation.

The executor uses the Maintenance Functions to

When the operation is complete, the executor sends 1its response to the
command node.

it will then load itself 1n
' Once the target node 1is triggered,
1is programmed to operate. This
ROM
whatever manner its bootstrap
either from the executor
load
could include requestinga down-line
The target node could load
other.
that just triggered it or some
itself

from

i1ts own mass

storage.

The algorithm for implementing the trigger bootstrap 1s as follows:
call Data Link Service function to open link for trigger.
Call Maintenance Functions to perform trigger.
Call Data Link Service function to close link.

Network

5.9

Management

Loop

Test

There

are

two

Both

types

specified

Operation

Page

140

Operation
types
of

are

loop

1loopback

number

tests,

node

level

=zests

that

loop

and
a

times.

data

1link

standard

level.

test

block

If either test fails, the response explains the failure.
If the
test
fails
because
the
test
message
was
too long, the error return 1s
"invalid parameter value, length" (Appendix F) and the test data field
of
the
error
message
contains
the maximum length of the loop test
data, exclusive of test data overhead.
If
the
test
fails
for
any
other reason, the test data rield contains the number of messages that
had not been looped when the test was declared a failure.
The

unlooped

occur
message

case

the

not
can

content

value

return

test

need

looping

format,

that

requires
If

count

before

returned

begin

errors).

the

The

length

the maximum

Ethernet

for success or
example, connect

(for

only

for errors that
errors, command

exception

parameter

too

this

large,

since

length.

«circuit

and

physical

the

this

address

specified,
the
test
1is
done with the loopback assistance multicast
address.
The responding station's physical address is included in the
response,
|

5.9.1

Node

There

two general categories of node level tests (shown in Figures
10, following).
Both use normal traffic that requires logical
Both have variations that use the Loopback Mirror and NCP LOOP

commands.

called
node name

The

Testing

are

9
and
links.
NODE

Level

The

difference

that

the

first

communication, while the
established with the NCP SET NODE

four

ways

Local

local

Local

remote

Local

which

to
loopback

"normal"

node

1local

level

The first two
last two ways

CIRCUIT

travel

with

what

sets

might

loop

command.

are:

(using
an
loop node defined

uses

operator-controlled
with

the

circuit

Local
to remote
node

type

loopback

device

used)

loop

messages

type

second

loopback

defined with

ways are
are used

(using

the

used for the
for the loop

two connected

circuit

"normal"”
node

communication

name

file

that
generated

that

transferred

user

with

tests.

The

tests.

Test data can be a Loopback Mirror test»message

defined number of times, a
listed above, or a message

nodes

used)

task.

repeated

any

the

ways

The set up

commands

for

various

described in Figures 9A through 10D.

The operation of node

level

Page 141

Network Management Operation

types

testing

that

of node
|

wuses

level

Network

tests

are

Management

modules is as follows. The Local Network Management Functions receive
the NCP LOOP NODE command from the Network Management Listener and/or
Network Management Access Routines. If a circuit 1s involved in the
test, it must be in the ON state. If the Loopback Mirror is involved,
the message 1is passed to the Loopback Mirror Access Routines (see
Section 5.13). One logical link loop test uses a loop node with a
routing node on the remote end of the line (Figures 9A - 9D). This
test returns the test data on the circuit chosen by the Routing

algorithm at the routing node.

Network Management

SET LINE
SET NODE

Operation

Page

142

line-1id CONTROLLER LOOPBACK
FISHY CIRCUIT circuit-1d

(Transfer

file

from FISHY)

NODE

BOB

|
I
e
m
e.
|
|
USER
|
|
User Task |
|
User Task
I
|
|
MODULES
e'
e
T '
|
|
|
A
|
| -~ | —————————— | ————————— |
|
|
'
|
ettt
it e e TP
|
|
|

NETWORK
APPLICATION

|
|

File
]
Access Routines |

| -~
|
SESSION CONTROL
|-~
|
NETWORK SERVICES
| |
ROUTING
| ——————
|
DATA LINK
|-

|
PHYSICAL LINK
e
ee
|

| |
|
| |
||
| |
||
| |
| |
|

9A.

|
:

/) —mmmm e Hardware

Node

test

software

with

|
|

|
/ /
|
Device in
it /S Loopback
|
/ /|
\
Mode
|\ \
( (|
===\,
|\ \
N\
| - | |
\ O\
\
e | ———-.
|
|
AN\
e- | -——-.
|
|
|
\
e |- |
|
|l
e
- | -——-="
|
|
Communications Hardware
|
|

Local-to-Loopback

data,

File Access
Listener

- /S / mmmmmmm——
- |
/ /
|
- /S / mmmmm e
- |
//
|
- /) /) —mmmmm
e |
/ /
|
- / /) —mmm e |
/ /
|

Figure

|
|

Test,

| _________ | -

Single

Node

controlled

(using

loopback

files

capability)

Page

Network Management Operation

143

SET NODE FISHY CIRCUIT circuit-1id
LOOP

NODE

FISHY

BOB

NODE

| NCP
USER
it '
MODULES
——————— e | A m e

S mmm—mm——————— v | —mmm—m—m

|
|
l
%

|
| Network Management Access Routines
'
——————
—————
A
|
e
T ———— v | ———m——————————————— .
|
| Local Network Management Function

|
NETWORK
MANAGEMENT
o

|
|

——————————————————————— | A ———mm e|
v

NETWORK
APPLICATION

—————— —————— e

|
| Loopback
| Access Routines

—————————————————————————— T
SESSION CONTROL

NETWORK SERVICES

ROUTING

——————————————————————————

|
|

————————————,

Loopback
Mirror

/ /

|
:

|
|

}

-/ ) -

===

| e ) ) mmmmmm

—————————————————————————— |

—— -

/ /

=|
i kbbb || - /) / ——————m—m————————

|
/ /
|
DATA LINK
Loopback
--—----—------/
/
------~—————————————————————————— ||
PHYSICAL LINK

/ /

Hardware

—————————————————————————— ol -----/ /.--------------—--- Device

\
/ /|
|
==
=\
|
( (
N\
===
|
\ \
N\
-~ | = ~——.
\
N\
|
|
et | ——.
N\
|
-="
|
~
\
}

Figure 9B.

loopback mirror
Node Test, Single Node (using
messages, and a manually set loopback device)

Network Management Operation

Page 144

SET NODE FISHY CIRCUIT circuit-id

(Invoke user task using BOB and FISHY)

NODE
——

. m— v—

AP SE

t—

—

———

—

a—

w———

BOB
——

—

——— —

—

V—

—

NODE

——

—

——

—

——

—

——

TONY
—

—

——

—

——

—

USER

MODULES

User

—

——

User

—

NETWORK
MANAGEMENT

|
|

|
I

NETWORK
APPLICATION

l
|

I
|

|
|

'SESSION

NETWORK
SERVICES

|
|

ROUTING

DATA LINK

PHYSICAL
LINK

|
|

|
|
|

|
A

]

ettt

S—

—

CONTROL

|
|

Figure 9C.

Local-to-Loopback Node TeSt, Two Nodes (using user task)

Network Management Operation
D

Page

145

SET NODE FISHY CIRCUIT circuit-1id

LOOP NODE FISHY

NODE BOB

NODE

TONY

USER
MODULES

Network Management

| Access Routines

| Local Network

NETWORK
MANAGEMENT

|
|

NETWORK
APPLICATION

’)

| Management Function | |
T ——| A ,

|
|
|

Loopback
Access
Routines

|
|
|

|
1

Loopbackl||
Mirror
||
--------- '

SESSION
CONTROL

NETWORK

SERVICES

ROUTING
DATA

LINK

)

PHYSICAL

LINK

Figure 9D.

Local-to-Loopback Node Test,

mirror and text messages)

(using

loopback

Network Management Operation

(LOOP NODE BOB)

Page

146

(LOOP EXECUTOR)
NODE

BOB

|
|
[~
|
|

NETWORK
=
MANAGEMENT

————————————=- | A ——————
='
S v |
——————
-.
| Local Network Management Function
e'

mmm e
'

I
v
oo -

|
|

NETWORK
APPLICATION

NETWORK SERVICES

ROUTING

|
|

‘

Loopback
Access Routines

|
|

’

|
|

)

oo
Loopback
Mirror

|
|

)

——

. s

)

|.__. ________________________

Figure 10A.

Normal Local-to-Local (using loopback mirror)

|
|
|
|

|
|
|
|
|

Page 147

Network Management Operation

(Invoke user task using BOB)
NODE

|
|
|
|

USER
MODULES

mmmm
|
B

BOB

.
e mm
|
User Task
|
m e'
e

e ————
|
User Task
i bl !
]

|
|
|
o

- V ommmmm e |
||
|
|

|
A

| oo I

NETWORK SERVICES

| ____________________________

sttt

ottt

}

)

bt
i

——

SESSION CONTROL

| e-

——

e——

)

|
|

NETWORK
APPLICATION

|
|

Figure 10B.

Normal Local-to-Local

(using user tasks)

|
|
|
|

!
:

Network Management Operation

Page 148

LOOP NODE TONY

NODE

USER
MODULES

BOB

ettt

NODE

|
|

|
NCP
|
Cmm————- !

Network Management

]

|
|

| -~ | A —————————- |
|- |
| v | -.
|

NETWORK
MANAGEMENT

| | Access Routines
I
|- | A ———————- ol

|
|

|
|
|

,—--=—-—-—-- v

[ [

NETWORK
APPLICATION

SESSION
CONTROL

TONY

|
|

Loopback |
Access
|

Routines
|

————— '

| -—-—- |
|
:

NETWORK
SERVICES

|
|

|-|

DATA LINK

|
1

Loopback| |
Mirror
| |

|- -

||
: {

|
:
:

||
|

|
|

|
{

/ /
|
) [mmmm———— |

/ /

- |

NN
.
/ /
|
A
|
/
|
|
—————————— N\ \ -y
e =
)
!
N\
e S/
\ \
/ /

Figure

| ===

/ /
|
/ /
|
|- )
= I

| - \ \-—— - |

PHYSICAL
LINK

|
|

el
e

| ————- |
e
- |
|
s
|
| - ————- \ \ -I

ROUTING

10C.

Normal

Local-to-Remote

(using

loopback mirror)

Network Management

Operation

Page- 149

(Transfer files from BOB to TONY)

NODE BOB
|

USER
|
MODULES

———————

|
|

NETWORK
APPLICATION

SESSION
CONTROL

|
|
|

I
|

User
Task

|
|

|
e'
|
R | - I

SERVICES

ROUTING

| | | |

|
o

- ===

|
|

User
Task

- I

|
I

e'
I
| - |
|
A

|
|

File Access
Listener

- I

|
|

—————— '
I
A —————————- I
S —— | ————- .
I

- I

|
|

S m——————

———

———————— I

- I

.
|

———————— I

|
|

I
I

I
I
|
|
|

n—

—

am——

——

a—

—

)

PHYSICAL
LINK

|
|

| File Access
| Routines

I
v

DATA LINK

|
|

e'
|
————- | - I
S ——— vV ————— .
|

I
I

- NETWORK

NODE TONY

Figure 10D.

5.9.2

Data

Normal Local-to-Remote

(using

files as test data)

Link Testing

Data Link level testing requires a direct interface between
the
Data
Link
Service
Function and the Data Link layer.
Figures 11A and 11B,
at the end of this section, show two types of data link level tests:
1.

Direct link

loopback,

hardware

Direct link loopback, software looped

Link loopback requires the use of

data

The hardWare—looped option requires

‘example,

MOP),

controller,

with the

modem

looped

link to be tested

set

loopback

link

service

software

(for

i1n the ON or SERVICE state.

operator-controlled
mode,

ROM

1loopback

with loopback

Network Management Operation

Page 150

capabilities at the remote end, or some
other
equivalent
operation.
It is recommended that the operator turn off the link, reconfigure the
hardware,

may

and then turn the

link back on.

leave the link in the ON state,

problem will be

logged

Alternatively,

the operator

and any resulting synchronization

error.

Thevalgorithm for the active loop test 1s as follows:
Set

not

done

Call Data Link Service Functions to open link for active loop
WHILE

not

done

Call Maintenance Functions to loop message
Call Data Link Service Function to receilve message
IF error OR count exhausted OR message 1s not loop data or
looped data OR received data does not match sent data
Set

done

ENDIF

ENDWHILE

Call Data Link Service Function to close

link

Network Management

{
{
{
{

Operation

Page

[SET CIRCUIT circuit-id STATE OFF]
(manually set loopback device)
SET CIRCUIT circuit-id STATE ON/SERVICE
LOOP CIRCUIT circuit-id

151

}
}
}
}

{
{

(circuit
SET LINE

in ON or SERVICE state)
line-1id CONTROLLER LOOPBACK

{

(LOOP CIRCUIT circuit-id)

}

EXECUTOR

NODE

o.
| NCP |

-'
| A —————

}
}

e v

NETWORK

MANAGEMENT

--.

Network Management

Access Routines

S v

| <---->|

A |

|
|
e

Network Management
Listener

A —————- '

Local Network Management Functions,
Maintenance Functions, and

|
|

Link Service

|
DATA LINK
| -

—————

o
|
|
|
|
|

Figure

implementation
11A,

Functions

|
A - |
|
|

|
PHYSICAL LINK
|
B
i.

|
|

e
-

|
|
|

———

Loopback

|
Hardware
e Device

NN
e \---.
R
N s | - | \
e | ———~
|

dependent

Direct Line, Hardware
and Command Sequences

Looped, Data Link
Effecting Them

Loopback

Tests

Page 152

Network Management Operation

LOOP CIRCUIT circuit-id
(circuit at TARGET NODE in SERVICE or ON state * )

USER
MODULES

NETWORK
MANAGEMENT

|
——————
|
|
|
NCP
|
N
I
|
|
B
| -~ | A ———— - T
S ————- o
| -V | -—-.
N
Network
|
| | Network
|
|
|
|

| Management|
| Management||
| Access
|<->| Listener
||
| Routines
|
|
S
I
—— | A -———-"
e | A -=="|

|
|

| Local Network
| Management Function,

'l
||

|
|

———.]

| Maintenance Functions,

|
|

e
| Link Service Functions
-|
-——— | A -

_ v

PHYSICAL
LINK

|
|
| -—————~ D
|
\ O\
1
\ A\
————————— N

Maintenance
Functions and

|
|

Functions

Link Service

|
I
|
|

—————- ;

/ /
) [ —————
/ /
/ /

=/ )
e '/
/ /

Smmmmm——————

implementation dependent

Figure 11B.

5.10

N\ \
N\

and

DATA LINK

——————— .

e v |

TARGET NODE

EXECUTOR NODE

Direct Line,

Software Looped, Data Link Loopback Tests

and Command Sequences Effecting Them

Change Parameter Operation

the specified
1is received,
When a NICE change parameter request
local
interfacing with the
wusually by
are changed,
parameters
the
to
returned
then
An appropriate response is
operating system.

The options of the change parameter request indicate the
‘requester.
desired operation (either specifying a different value or removing the

value) and the entity it relates to.
for volatile or

permanent

The operation can be done either

parameters.

The request may contain zero or more parameters.

If there

are

none,

Network Management Operation

Page 153

the operation applies to the entire entity entry (in other words, the
checked
All parameters in the message should be
NCP ALL parameter).

If one parameter fails the
before any are changed in the data base.
A single response indicates
check, then the operation should fail.
success or failure for single-entity operations.

A change parameter request may apply to a group of entities.

this

The entire request does not
or failure is individual.
success
case,
An initial fail return implies
fail if a single entity request fails.
A special success return indicates
responses are coming.
further
no

more responses will follow,

one for each entity in the group.

Changing the link state requires the following capabilitiles:
For

operator:

state

Set

link

Set

link state

Set

link

state

to OFF

to ON
to SERVICE

For the Link Watcher:
link state

Set

Reset

to ON-AUTOSERVICE

link state

from ON-AUTOSERVICE

All of the algorithms 1imply recording the link state if they

The

link state algorithms

succeed.
|

follow.

Set link state to OFF:
Call link's high level user to set link state to off
Call Line Service Function to set link state to off

Set

state

link

to ON:

Call Data Link Service Function to set link state to passive
IF

success

- link's high level user to set link state to on
Call

ELSE

Fail
ENDIF

Set

link state

SERVICE:

Call Data Link Service Function to set link state to closed
IF

success

Call link's high level user to set link state to off

ELSE

Fail
ENDIF

Network Management

Set

Operation

link state
IF

1link

Page

154

to ON-AUTOSERVICE:

state

1s ON

Perform algorithm to set

link state

to service

ELSE

Fail
ENDIF

Reset

link

state

from ON-AUTOSERVICE:

link state 1s ON-AUTOSERVICE
Perform algorithm to set link

|
state

to on

ENDIF

5.11

Read

Information Operation

When a read information request is received, a response
1s
returned,
followed
by
the
requested
data
1in
the
form
of standard Network
Management data blocks (Section 7).
The data may be
obtained
either
from
within
the
Local
Network
Management
Function
1tself
or by
interfacing with the system as appropriate.
The many
specific

restrictions
parameters

Additional

information

and
or

special
situations
relating
counters
are
described
1n

in Section 4.3.8

(SHOW command).

A fail return in the first response implies no
coming.
A
special
success return indicates
accepted and more will follow.
|

5.12

appropriate

further
responses
are
the command message was

Zero Counters Operation

When a zero counters request is received, the
cleared
by
interfacing
with
the
local

read

to
reading
Section
7.

response

read and zero was
information

had

then

returned

requested,

been

the

appropriate
operating

counters
system.

are
An

requester.

counters

are

returned

requested.

A fail return on the first response implies no further
responses
are
coming.
Success is a single return for single-entity operations.
For
multiple-entity
operations,
success
1S
a
special
success
return
implying

5.13

further

responses.

Loopback Mirror Operation

The Loopback Mirror service tests logical links either

between

nodes

or
within
a
single node.
It consists of an access 1nterface -Loopback Access Routine; service routines -- the Loopback Mirror;

the
and

simple

protocol -- the

mirror functlon operates

- Page 155

Network Management Operation

Logical

Loopback

Protocol.

The loopback

in the Network Application DNA layer.

its maximum
returns
1t
When the Loopback Mirror accepts a connect,
This is the amount of data 1t can
accept data.
1in the
data size
handle,

not counting the

function code.

into the
changed
When a Logical Loopback message is received, 1t 1s
appropriate response message and returned to the user (Figure 10,
traffic
all
repeat
to
The Loopback Mirror continues
Section 5).
The initiator of the link disconnects 1it.
offered.

5.14

NICE Logical Link Handling

1link
logical
the
describes
This section
uses when sending NICE messages.
Management

are in Section 6.12.

Network
that
algorithms
The version data formats

The determination that a received version number

of the higher version
responsibility
always the
1s
acceptable
is
software, whether it is the command source or the listener.

The buffer size

for NICE messages

300 bytes.

The Network Management Listener algorithm follows:
Recelve

connect

request

on access control
(Optionally) Determine privilege level based

IF resources available and received version number OK
Send connect accept with version number 1n accept data
WHILE connected (see Note, below)
Receive command message
IF message receilved

Process command message accordlng to command and
privilege

Send response message(s)
ENDIF
ENDWHILE

ELSE

received version

number

not

Send connect wreject with version skew reason 1in reject
data

ELSE

Send connect
|

reject

ENDIF
ENDIF

NOTE

The algorithms used for connections are implementation
For example, connections can be maintained
dependent.
set,
1S
executor
the
while
only
permanently,
"timed-out, or one per command.

Network Management

The

Operation

Network Management

~Send connect
IF

connect

command

request

source

with version

Page

algorithm

follows:

number

connect

156

data

accepted

received version number OK
WHILE desired
Send command message
Receive response message(s)
ENDWHILE

ELSE

Failure

due

version

skew

ENDIPF

Disconnect

link

ELSE

connect rejected by listener
IF reject data indicates version
- Fallure due to version skew

skew

ELSE

Failure

due

liste er

resources

ENDIF

ELSE

Failure

due

network

connect

ENDIF

problem
~

Use

the

following

Send
IF

connect

algorithm
request

for

event

with version

transmitter:

number

connect

data

accepted

received version
WHILE desired

number

Send event message
ENDWHILE
ELSE

Failure

due to

version

skew

ENDIF

Disconnect

link

ELSE

Perform

implementation

specific

error

handling

ENDIF

Use

the

following

Receive
IF

algorithm

connect

resources

and

WHILE connected
Recelive event
ELSE

Send

connect

event

received

with version

messages

ENDWHILE

ENDIF

receiver:

request

avallable

Send connect

for

reject

version

number

data

ENDIF

Page 157

Network Management Operation
Algorithm for Accepting Version Numbers

5.15

of three parts -- version, ECO (Engineering
A version number consists
In general, another
and user ECO (Section 6.12).
Change Order),
~version 1is acceptable if it 1s greater than or equal to this wversion.
If less than this version, it is optionally acceptable as determined
by product

requirements.

When comparing two version numbers, compare the second parts only
and so on.

the first parts are equal,

1if

For Event Logging, the lack of a version number implies Version 2.0.

Return Code Handling

5.16

Use the'following return code handling algorithm to call

Management access routines:
function

Initiate

IF return code = more

the

Network

(2)

WHILE return code <> done (-128)
Perform next operation

Process success/failure (1, 3 <0)

ENDWHILE

ELSE

Process success/failure

(1,<0)

ENDIF

Note that an initiate call starts the function, and an operate call
performs the function (one entity at a time in the case of plural
|

entities).

Use the following algorithm

for

deciding

Network Management access routines:

return
~

codes

within the

IF multiple returns needed
Return "more" (2)
ENDIF

WHILE

returns

success

IF all response data for entlty in single return
OR last of multiple responses for this entity
ELSE

Return "success"

(1)

Return "partial"

(3)

ENDIF

ELSE

Return error code and other error information

ENDIF

ENDWHILE

IF multiple returns needed

Return "done"

ENDIF

(-128)

Network Management Operation

Page 158

Example:

The

following

SHOW

ACTIVE

(2)

UNA-0
UNA-0
UNA-Q0
UNA-1
UNA-1
UNA-1
UNA-2
DMC-2

(-128)

sequence

CIRCUITS

messages

command

1(RED) xxx
2(BLUE) yyy
3(PINK) zzz
91
(3)
92
(3)
93
(1)
(1)
(1)

(3)
(3)
(1)

might

returned

response

‘Page 159

Network Management Messages
6

NETWORK MANAGEMENT MESSAGES

NICE
the
This section describes the NICE and Event Logging Messages,
response message format, the NICE connect and accept data format, and
the Logical Link Message

format.

NICE is a command-response protocol.

Network

Because the

Management

is built on top of the End Communication and Data Link layers,
layer
error-free
and
which provide logical links that guarantee sequential
data delivery, NICE does not have to handle error recovery.

are
In the message descriptions that follow, any unused bits or bytes
to zero to allow compatibility with future
to be reserved and set
and
areas
reserved
non-zero
such as
Conditions
implementations.
unrecognized codes or unused bytes at the end of a field or message
should be performed
should be treated as errors, and no operation
.
other than an appropriate error response.

The entire message should be parsed and checked
any operation

for
|

1is performed.

.~ The method for indicating that a function should be

parameters

validity

Dbefore

executed

all

the data base for a particular entity (NCP ALL option)

is to not include any parameters in the NICE function request message.

Parameters in command and response messages must be 1in ascending order
that qualifiers must preceed the
except
type number,
by parameter
A parameter of the same type may be repeated
parameters they qualify.
for parameters that compose a

list.

Qualifiers are restricted to

one

same

the

parameter

type

per

If qualified parameters appear 1n a
command or response message.
Unqualified
message the qualifier must appear 1n the same message.
parameters may or may not be included in a message with a qualifier.
a qualifier must be
a message with
1in
All qualified parameters
In a sequence of multiple return
associated with that qualifier.
messages, when qualifiers are nested, the outer level qualifier 1s not
repeated until

6.1

changes.

NICE Function Codes

The NICE protocol performs the following message functions.

The

last

one is for system specific commands, not specified in this document.

Network Management

Messages

Function
Code

NICE

Request
Request
Trigger

down-line load
up-line dump
bootstrap

Test

Change parameter
Read 1information

20
21

Zero

System-specific

Message

Format

counters

function

Notation

The Network Management message format déscriptions use

the

notation.

FIELD

160

Function

6.2

Page

(LENGTH)

CODING

Description

following

field

where:
FIELD

the

name

the

field

the

length

number

meaning

number

followed

being

described

LENGTH
of

the

field

as:

number

"B"

8-bit

bytes.

meaning

number

bits.

The

letters "EX-n" meaning extensible field with n being
a
number meaning the maximum length in 8-bit bytes.
If
no number 1s specified the length is limited only by the
maxlmum NICE message.
Extensible fields are variable in
length consisting of 8-bit bytes, where
the
high-order
bit
of
each byte denotes whether the next byte is part
of the same field.
The -1 means the next byte
1s
part
of
this
field
while
a
0
denotes
the
1last
byte.
Extensible fields can be binary or bit map;
1if
Dbinary,
then
7
Dbits
from
each
byte
are concatenated into a

single binary

field;

bit map,

then

bits

from

each

byte
are
used
1ndependently as information bits.
The
bit
definitions
define
the
information
Dbits
after
removing extension bits and compressing the bytes.
The letters "I-n" meaning image field
with n
being
a
number which 1s the maximum length in 8-bit bytes of the
image.
The image is preceded by a l-byte count
of
the
length
of the remainder of the field.
1Image fields are

variable

length

byte

each

and may be

are

used

null

(count-0).

information bits.

All
The

Dbits

meaning

Network Management

Messages

Page

and interpretation of each image field
is
that

specific

The character

field.

"*"

defined

meaning

number following
the
field length 1in bytes.

remainder

asterisk

with

message.

1indicates

the

161l

minimum

CODING

Is the representation type used.
where:

7-bit

ASCII

B = Bilnary
BM =

Bit Map (where
each
independent meaning)

)
bit

group
.

Dbits

has

Constant

Notes:

If length and
field
with
descriptions.

Any bit or

field which

zero
unless
described 1s

All

coding are omitted, FIELD represents a
a
number
of
subfields
specified

is stated to be

otherwise
reserved.

numeric values

representation

specified.

in this

unless

document

otherwise

generic
1n
the

"reserved"
. shall
Any

bit

are

shown

fi1eld

be
not

decimal

noted.

All fields are presented to the physical link protocol
least
significant
byte
first.
In
an
ASCII field, the leftmost
character is in the low-order byte.
|
Bytes

this

(low-order,
(high-order,

other

lengths

document

are

numbered with bit

least-significant)
most-significant)
are

bit,
Dbit.

numbered similarly.

Request

FUNCTION
CODE

Down-line

OPTION

Load Message

NODE

CIRCUIT

Format

PARAMETER
ENTRIES

the

rightmost

and bit 7 the leftmost
Fields
and
bytes
of

Corresponding data type format notation used
described at the beginning of that section.

6.3

in Section

Network Management Messages
where:

FUNCTION CODE

OPTION (1) BM

- Page 162

(1)

B =

Is one of the following options:

Option bit

Value/Meaning

0-2

NODE

0
3

=
=

Identify target by node-1id.
Identify target by circuit-1id.

Is the target node identification (see Section

defaults data base (present only 1f
not
are
options
nodes
Plural

into
key
‘as
0).
=
option
allowed.

CIRCUIT

Is the circuit

Plural

if option

PARAMETER ENTRIES

1identification

circuits options not
=

(see

Section

allowed.

7).

Present only

are zero or more of PARAMETER ENTRY consisting of:
DATA

DATA

where:

DATA ID (2) : B
DATA

Is the parameter type number

(see

note

the

and Section

below

parameter

Section 7).

data

(see

NOTE

The

parameters

allowed

are

parameters:

the

following

node

ADDRESS
CPU
DIAGNOSTIC

HOST
LOAD

FILE

NAME

PHYSICAL

ADDRESS

SECONDARY

LOADER

SERVICE

DEVICE

SERVICE

PASSWORD

SERVICE CIRCUIT

(allowed only if option = 0)

SOFTWARE

IDENTIFICATION

SOFTWARE

TYPE

TERTIARY LOADER

)

Network Management Messages

6.4

Request Up-line Dump Message

FUNCTION

OPTION

NODE

Page

163

Format

CIRCUIT

PARAMETER

CODE

ENTRIES

where:

FUNCTION CODE

OPTION

(1)

(1):

one of

the

following

Option bits
0-2

NODE

options:

- Value/Meaning
0
3

= Identify target by node-1id.
= Identify target by circuit-id.

Identifies the node to be dumped (present only 1f

option

CIRCUIT

0).

Format

is defined

in Section

Specifies the circuit over which to dump
only

if option =

7.4,

PARAMETER ENTRIES

3).

Format

is defined

7.10.

(present

in Section

Are zero or more of PARAMETER ENTRY consisting of:
DATA

DATA

where:

DATA

(2)

the parameter

(see

7).

DATA

note

the

Section

below

parameter

7).

type

data

NOTE

The parameters are selected from the node
parameters.
Only
certain
parameters
are
allowed
1n
the
dump
message.

They

are:

DUMP

ADDRESS

DUMP

COUNT

DUMP FILE
PHYSICAL

ADDRESS

SECONDARY DUMPER

SERVICE CIRCUIT
SERVICE

PASSWORD

(allowed only

if option =

number

and Section

(see

Page 164

Network Management Messages

PARAMETER
ENTRIES

CIRCUIT

OPTION NODE

FUNCTION
CODE

6.5 Trigger‘Bootstrap Message Format
where:

)

FUNCTION CODE (1): B = 17
Is one of the following options:

Value/Meaning

‘Option bits

0-2
NODE

Identify target
circult—-i1d.

Identifies the node to trigger

only

Section

CIRCUIT

0 = Identify target by node-1id.

option

0).

boot

(present only if option = 3).

defined

PARAMETER ENTRIES

is defined

1in

trigger

the

Identifies the circuit over which to

on (present

The format

7.10.

in Section 7.4.

The

format

1is

Are zero or more of PARAMETER ENTRY consisting of:
DATA

DATA

\\\\_//

OPTION (1)

where:

DATA ID

(2)

DATA

the parameter

(see
7).

note

the

Section

type

number

and Section
|

below

parameter

7).

data

(see

)

NOTE

The parameters are selected from the node

Only

parameters

certain

message.

They

are

parameters.

allowed in the trigger

are:

PHYSICAL

ADDRESS

SERVICE

PASSWORD

SERVICE CIRCUIT

(allowed only if option = 0)

.
|

Network

6.6

Management

Test

FUNCTION

Messages

Message

Format

OPTION

NODE

CODE

USER

PASSWORD

Page

ACCOUNTING

LINK

PARAMETER

ENTRIES

165

where:

FUNCTION CODE

(1):

OPTION (1): BM

Is one of the following options:
Option bits

Value/Meaning

0-2

0
1l

=
=

Node
Line

type
loop

Circuilt

loop
test

loop

test

If nodé type loop test:
7

For

node

type

loop

tests

only

(option

Default

access

control

Access

control

1included

0),

four

parameters

are

follows:

NODE

USER (I-39):

Identifies the node
in
node-id format.
allowed.

PASSWORD (I-39):

ACCOUNTING
-

(I-39):A
»
|

to loopback the
test
Dblock
Plural node options are not

Is the user-id to use when connecting

node.

Is the password to use when connecting
Present only if option bit 7 = 1.

node.

Present

only

1if

option

Is
the
accounting
connecting
to node.
7

bit

information
to
Present only 1if

wuse
when
option bit

For line or circuit tests only (option l or 3), one
follows:

LINK

parameter

1is

Identifies the link
circuitor line-id

to
send
the
test
on
1in
format.
Plural options not

allowed.

PARAMETER ENTRIES

Are
Of

zero

or more

PARAMETER ENTRY,

consisting
|

DATA

ID
where:

DATA

(2)

1Is

the parameter

type

number

Network Management Messages

|
(see

7).

DATA

note

Is
the
Section

Page 166

below

parameter
7).

and Section

data

(see

NOTE

The

parameters

Only

certain

message.

6.7

Change

FUNCTION
CODE

are

selected

parameters

They

from

are

the

node

allowed

.1n

parameters.

the

test

are:

LOOP

ASSISTANT

NODE

LOOP

ASSISTANT

PHYSICAL

LOOP

COUNT

LOOP

HELP

LOOP

LENGTH

LOOP

NODE

LOOP

WITH

ADDRESS

PHYSICAL

ADDRESS

Parameter

Message

OPTION

ENTITY

PARAMETER

ENTRIES

Format

where:

FUNCTION CODE (1):
|

OPTION (1):

BM |

B = 19

Is one of thg following bptions:

Bits

Meaning

0 = Change volatile parameters.

1 = Change permanent parameters.

0 = Set/define parameters.
1

0-2
ENTITY

PARAMETER ENTRIES

Clear/purge

parameters.

Entity type (Sectiofi 7).

Identifies

the particular

entity

(Section

7).

A?E zefo or more of PARAMETER ENTRY consisting
of:

DATA

where:

DATA

Network Management Messages
\>

DATA ID

(2)

DATA

Page 167

Is the parameter

type

(see Section 7).

Is
the
Section

parameter
7).

data

number
(see
-

NOTE

The DATA field is not present when option bilt 6
unless
the parameter
1s
a
qualifier rather
parameter that 1s to be cleared.

6.8

1s set
than a

Read Information Message Format

FUNCTION

OPTION

CODE

ENTITY

PARAMETER

ENTRIES

where:

FUNCTION CODE
OPTION

(1):

(1): BM

B =

20
Is one of

following options:

Bits

Meaning

4-6

the

Read volatile parameter

Read

permanent

Information

)

type

parameter

0
1l

=
=

Summary

Characteristics

Events

Status

3 = Counters

0-2

ENTITY

PARAMETER ENTRIES

Entity type

(Section

(Section 7).

0 or more parameter entries,
formatted
as
for
change
parameter message.
These are limited to
the following qualifiers:
|

LOGGING

)

7).

Identifies the particular entity

CIRCUIT ADJACENT NODE

follows:

SINK

NODE

MODULE
MODULE

X25-ACCESS NETWORK
X25-PROTOCOL DTE GROUP

MODULE

X25-SERVER DESTINATION

NODE CIRCUIT

Network

6.9

Management

Zero

Counters

FUNCTION

Page

Messages

Message

OPTION

Format

ENTITY

PARAMETER

ENTRIES

CODE

168

where:

FUNCTION CODE

OPTION

(1l):

(1):

Is one of

the

Bits
7

0-2

"ENTITY ID

Meaning
1

Read

and

Zero

only

zero

Entity type (Section 7).
(Circuit, line, module,
or node only).

Identifies the particular

(Section 7).

MODULE

X25-PROTOCOL

NICE System Specific Message

CODE

1if

required

DTE

Format

REMA INDER

SYSTEM

FUNCTION

entity,

for
as
0 or more parameter entries,
formatted
change
parameter message.
These are limited to
the following qualifiers:

PARAMETER ENTRIES

6.10

following options:

TYPE

where:

FUNCTION CODE

'SYSTEM TYPE

(1)

Represents the type of operating
~to which command is specific.

REMAINDER

(*)

command

System

s W

RSX family
TOPS-10/20

NN OO

Value

system

RSTS

VMS
RT

Communications

Consists of data,
requirements.

Server

depending on
|

system

specific

6.11
RETURN
CODE

Page 169

Network Management Messages

NICE Response'Messagé Format
DATA
BLOCK

TEST
DATA

ENTITY
ID

ERROR
MESSAGE

ERROR
DETAIL

where:

RETURN CODE (1)

[ERROR DETAIL]

(2)

the

Is one

(Appendix F).

NICE

standard

B Is more detailed error

codes

return

according

information

code (e.g., a parameter typel.
error
the
to
Zero if not applicable.
If applicable but not
available, 1ts value is 65,535 (all bits set).
In this case it 1s
not
printed.
Applicable
only

RETURN CODE

-128.

that may
Is a system-dependent error message
standard error
the
be output in addition to

[ ERROR MESSAGE]
A
(I-255) :

message.

1is on plural entities,

operation
is

the

[TEST DATA]

1if

Identifies a particular entity (Section 7)

[ENTITY ID]

(2)

read

information or

entity is the executor node,

the

name

length

bit 7 of

set.

information

Is the

DATA,

resulting

from

test

is UNLOOPED COUNT or MAXIMUM LOOP

depending on ERROR DETAIL.

further

counters.

This is only
message only).
(Test
operation
1is
data
1if
and
failed
test
required if a
this
in
a data block is present
or
relevant,

message.

[ DATA BLOCK]

or operation

read and zero

1ts

explains

Section 5.9

contents.

Is one of the data blocks described in Section

read

for

(returned

information message Or

For Test messages
read and zero message).
may contain the parameter PHYSICAL ADDRESS.

field, the
any
terminated after
1is short
If a response message
existing fields may still be interpreted according to standard format.
to be
1s
return
a single byte
that
for example,
This means,
interpreted as

Responses to

messages

not

return code.

noted

responses indicating return code,

exceptions

error detail,

above

are

single

and error message.

A success response to a request for plural entities is indicated by a
2 with no other fields, followed by a separate
only
of
return code
Each of these messages contains the
response message for each entity.

basic response data (return code, error detail, and error message) and
the entity id. A return code of -128 indicates the end of multiple
responses.

Network

6.12

The

Management

NICE

first

Messages

Connect

three

Initiate

bytes

and

the

Connect

connect

Data

initiate
and

Page

170

Formats

connect

data

are:

VERSION

DEC

USER

ECO

‘where:

VERSION

(1)

1Is

the

version

number

DEC ECO

(1)

Is the

DIGITAL

ECO number

user

USER ECO

6.13

(1)

Event

the

Message

Binary

ECO number

Data

Format

This section describes the generalized binary format
of
It
applies
to messages on logical links and, as much as
files.
The

buffer

size

for

event

messages

200

event
data.
possible, to
'

bytes.

The format of an event logging message is:
FUNCTION

CODE

S INK

FLAGS

EVENT

SOURCE

EVENT

CODE

TIME

NODE

ENTITY

DATA

where:

FUNCTION CODE (1)

SINK

FLAGS

(1)

1, meaning

Are

flags

event

log

indicating

a copy of this event,
assignments are:
Bit

Sink

0
1

Console

(2)

BM Identifies

the

Bits

EVENT

TIME

one

sinks
bit

per
|

are

receive

sink.

The

bit

File
Monitor

EVENT CODE

which

specific

follows:

date

and

time

Meaning

0-4

Event

type

6—-14

Event

class

source

the

event

processing.

node

Consists

of:

event

'~ Network Management Messages

JULIAN
HALF

SECOND

Page 171

MILLISECOND

DAY

where:

JULIAN HALF DAY
|

(2)

Number
since

before

example,
of Jan 1,

(2)

MILLISECOND

(2)

2021

Nov

(0-32767).

SECOND

half
days
Jan 1977 and

For

morning
the
1977 1s 0.

Second within
current
half day (0-43199).

Millisecond

within

second

current

not

(0-999),

high order
supported,
remainder
bit 1s set,
and field
clear,
are
is
not
printed
when
formatted

SOURCE NODE

Identifies the source node.
NODE

output.

It consists of:

NODE
NAME

- ADDRESS
where:

NODE NAME

(I-6)

Node

(2)

NODE ADDRESS

EVENT ENTITY

for

Section

7.9).

Node name,

(see

address
0

length,

none.

Identifies the entity involved in the event,

applicable.

Consists of:

ENRITY

ENTITY

TYPE

where:

ENTITY TYPE

(2)

Represents

usual

EVENT DATA (*) :
|

the

defined

format.

B Is event specific data, zero or more data
as

type

value
-1
A
entity.
A
entity.
indicates no
0 is the entity
>=
value
by
followed
type and is
1ts
1in
1id
entity
the

for NICE data blocks,

entries

parameter

types

Network ManagementvMessages

Page

according
to

6.14

Logical

Loopback Message

event

172

class.

Formats

6.14.1

Connect Accept Data Format

MAXIMUM

DATA

where:

MAXIMUM DATA (2)

6.14.2

B Is

the

maximum

Loopback Mirror

length,

can

loop.

(1)

bytes,

Command»Message Format

FUNCTION

DATA

CODE

where:

FUNCTION CODE (1) ¢+

B =0

DATA

data to

(*)

6.14.3

RETURN

the

Response

CODE

Message

loop.

Format

DATA

where:

RETURN CODE
DATA

(*)

(1)
B

Indicates
Is

the

Success

data

received,

Failure
if

(-1).

success.

that

the

Page 173

Parameter and Counter Binary Formats and Values
PARAMETER AND COUNTER BINARY FORMATS AND VALUES

This section describes the binary formats of all entities, parameters,

counters, and events, as well as the returns used in the NICE protocol
to a request for information.
and Event Logging messages 1n response
s, events
Section 3 describes the entities, parameters, counterand
|

along with their user level formats.

Introduction to Binary Format Descriptions

7.1

Read this section before the rest of Section 7. This section explains
notation format, symbols, and other general information pertaining to
all entities. Since the symbols and notation are only explained 1n
this section, you may need to refer back to it when studying Tables 5
.

29.

thru

7.1.1

Type

Numbers

‘'Each entity, parameter and counter is assigned
entity type numbers are as

follows:

type
|

numper.

The

this

Keyword

g WM+
O

Type Number

NODE
LINE

LOGGING
CIRCUIT
MODULE
AREA

Entity type fields have 3-bit lengths.
The‘parameter and counter type numbers appear in the
section.

7.1.2

Entity Parameter

Identifier Format

The following format is for input (NCP

parameter:

ENTITY TYPE

tables

(1):

to NML)

)

entity

type

defined as type numbers in
ues
are
Is the entity type. The val
a
is NODE, it is followed by
type
entity
the
If
section 7.1.1.
|
|
|
tion.
node identifica

Parameter

7.1.3

and Counter

String

Binary

Identifier

Formats

and Values

this

ID FORMAT

(1):

format

the

identification

following
Number

-5
-2
-1
>0

ID:

7.1.4

When

Identifier

represented

1in

format

(Section

type,

with

6.1
the

values:

Meaning

Significant (if applicable)
Active (if applicable)
~ Known (if applicable)

Length of

Is the ASCII

Node

format.

notation.)

174

Format

The string type idehtifiers use the following

describes

Page

identification

identification if ID FORMAT >0.

Formats

binary,

node

1dentification

one

number

different
formats
(limited by the particular function).
All choices
begin with
a format type.
This applies to
all
occurrences
of
node
identification.
The input (NCP to NML) format is as follows:

NODE FORMAT (1):

B Represents the node format type, as follows:
Number

Type

-5
-4
-3
-2

Significant nodes, no further data
Adjacent nodes, no further data
Loop nodes, no further data
Active nodes, no further data

-1

Known

0
>0

Node address
|
|
Length of node name, followed by the
indicated number of ASCII characters.

nodes,

In the ENTITY ID field of a response message
node identification
1s the executor node.

NODE ADDRESS
-

NODE NAME:
The

usual

(2):

NODE

ADDRESS

NAME

further

bit

set

data

1indicates

the

Is the node address if NODE
FORMAT
=
0.
When
used as 1nput, a node address of zero implies the
executor node.
‘

Is the node name 1f NODE FORMAT >0.

binary output

NODE

(NML

to NCP)

format

follows:

Parameter

and Counter

Binary

Formats

and Values

Page

175

where:

NODE ADDRESS

NODE NAME

7.1.5

(2):

(I-6):

Area

1Is the node address.
When supplied as output
a
node address of 0 indicates a loop node.
|

Identifier

the

node

name,

length

implies none.

Format

When represented in binary, the format of an area identification 1s as
follows:

AREA FORMAT (l)i

B Represents
the area format type, as follows:
Number

Type

-2
-1

Active areas, no further data
‘Known area, no further data

AREA NUMBER (1):

7.1.6

The

Format

for

following

format

(1):

Entity Types

for

OBJECT

FORMAT

OBJECT NUMBER (1):
If

the

OBJECT

OBJECT NAME:

On output

parameter:

identification
values:

following

format

type,

with

object

name,

Meaning
Numeric object number
Length of object name

= 0=

>0:

the value

distinguishable

an object

B Is the object type number.

FORMAT

Is the object

0
>0

the

input

the

Value

number

B Is the area number if AREA FORMAT
= 0.

Object

OBJECT FORMAT

Area

the ASCII

object

is either an object
the

data

type.

number

Parameter

7.1.7

All

and Counter

Numeric

Formats

a numeric

range

1is:

(2):

END (2):

use

176

common

format.

input,

the

(disjoint)

ranges,

Each parameter

for a

range

Parameter

range beginning.

Is the range end.

format

for

the

number,

The output

7.1.8

Page

BEGINNING

numbers

and Values

Range

occurrences

format

Binary

END

range

equals

and one

number

If range consists of

BEGINNING,

coded
for

the parameter must be

multiple

with

two

For multiple

repeated.

Display Format and Descriptive

is assigned a data type

field

single value.

single

Encoding Notation

Network Management

layer

level
that
describes
the format of the parameter.
This information
allows NCP to format and output most parameter values
1n a simple way,
even 1if NCP does not recognize the parameter type.
-

The notation used in the parameter tables in this section to
these

data

types

“

Notation

Data

C-n
CM-n

Coded,
Coded,

Not

Al-n
DU-n
DS-n
H-n
HI-n

ASCII image field, maximum n bytes
Decimal number, unsigned, n bytes
Decimal number, signed, n bytes
Hexadecimal number, n bytes
Hexadecimal image, maximum n bytes

O-n

describe

follows:

Type

single field, n
multiple field,

coded (any of

Octal

number,

the

bytes
n fields

following)

bytes

Image formats (AI-n and HI-n) are displayed left to right in the order
in which the bytes of data appear in the NICE message, 1.e., the order
of printed text.
For Ethernet address or
protocol
type
parameters,
each byte
of an HI-n data image (two characters) 1is separated from the

next byte by a hyphen

(-).

digits
appear

first
with no
1n reverse byte

separation of bytes.
Hence, hexadecimal
order from hexadecimal numbers

Numbers

are

displayed

most

significant

7.1.9

NICE

images

Returns

A response
to a SHOW command consists of
the
1identification
of
the
particular
entity
to which 1t applies and zero or more data entries.
The data entries are either parameter or counter entrles depending on
the information requested.

Page 177

Parameter and Counter Binary Formats and Values

When an implementation recognizes the parameter type of a coded field,
the value output should be the keyword(s) or other interpretation that
corresponds to the code for that parameter

type.

parameter

the

type is not recognized, the field should be formatted as hexadecimal.

The format of a data entry is as follows:
DATA ID

(2):

BM =

Identifies particular data entity:
Bit Value Meaning

Meaning

Bits

Parameter type,

0-11

type.

Reserved

12-14

Value Meaning
Counter

0-11

13-14

type

not bit mapped

WNHOKHO

(1):

interpreted according to entity

The rest of the bits are as follows:

Counter data.
Bits

~ DATA TYPE

The rest of the bits are as follows:

Parameter data.

bit mapped
reserved
8 bit counter
16 bit counter
32 bit counter

BM =

Identifies data type, present only for parameter data:
Bit Value Meaning

Not coded.

The rest of the bits are as follows:

Bit Value Meaning
6

Binary number.

The rest of the bits are as

follows:

Bits Value Meaning

4-5

implies data is image field.
length.

data

2
3

Hexadecimal Number
Octal Number

0
1

Unsigned Decimal Number
Signed Decimal Number

Parameter

and

Counter

6
7

Binary

Coded,

and

1mage

field.

ASCII

interpreted

according

DATA:

Bits
to

0-5

Bit

Value

Single field.

bytes 1in the field.
Multiple field.
Bits 0-5
fields,
maximum 31; each

the

bits

are

Page

178

the

number

the

number
preceded

of
by

zero.

PARAMETER

rest

TYPE.

follows:

Meaning

DATA

Bits

0-5

are
are

field

TYPE.

Is the counter qualifier bit map,
counter

Values

The

BIT MAP_(Z):

Formats

and

counter

bit

included

only

1if

DATA

1is

mapped.

the

data,

according

data

and

type.

The

data required for setting a parameter or
counter
1is the
entity
identification,
the
DATA ID, and the DATA.
The information required
for clearing a parameter or counter is the entity
1identification
and
the DATA ID.
When a parameter is displayed, the information is entity
id, DATA ID, DATA TYPE, BITMAP (if applicable) and DATA.
The
purpose
of
the
data
type
field
1is
to
provide
information for an output
formatter.

value

even

Thus

the

1ts

formatter

parameter

can

type

know

how

format

parameter

unrecognized.

A coded multiple (CM) field cannot appear as a data
within a coded multiple type parameter value.

type

All
The

for

numbers are low byte first in binary form whether
1image
1mage option for numbers can only be used for parameters
1s explicitly required.
All number bases except
hexadecimal
maximum length of four bytes.
|
|

field

or
not.
where it
have
a

Indicate counter overflow by setting all bits in the DATA field.
The

following

ranges

are

reserved

for

system

parameters:

Range

Reserved

2100-2299

RSTS

2300-2499

for

specific

2500-2699

RSX specific
TOPS-10/20 specific

2700-28989

VMS

2900-3099

3100-3299
3300-3499
3500-3899

specific

specific
CT specific
Communication
Future

use

Server

|
specific

specific

counters

Parameter and Counter Binary Formats and Values

Page 179

Customer specific

3900-4095

Information Types

7.1.10

The
Each parameter is associated with one or more information types.
indicate
to
symbols
following
the
use
section
this
in
tables
parameter
information

types

Symbol
C
S
*

for

each parameter.

Keyword

Associated Entity

CHARACTERISTICS
STATUS
SUMMARY

‘All entities
All entities
All entities
LOGGING

EVENTS

Qualifier

Qualifier indicates that the parameter is used as a qualifier for

parameters that

7.1.11

1t.

the

Applicability Restrictions

nodej
every
at
All node parameters and counters cannot be displayed
In the
be displayed for every line-id.
counters
1line
can all
nor
counters,
and
following tables, which describe the entity parameters
the following symbols note these restrictions:
Applicability

A
DN

Adjacent node only
Destination node only

A0 ZMTM

Symbol

Executor node only
Node by name only
Loop nodes

(includes executor)

Remote nodes

(all

exacutor and

Sink node
Indicates

must

7.1.12

nodes

except

loop nodes)

only
a parameter

be qualified

Setability Restrictions

Some parameters have user setability restrictions,
section by the

)

Symbol

following notation:
Meaning

Read only

indicated 1in

this

Parameter

and Counter Binary Formats and Values

“WO
|

Write only, in the
different
form in
a node name can be
a node id.)
|

Loop

Page

sense
that
it appears
1in
a
a read function.
(For example,
set, but it is read as part
of
|

only

7.2 Circuit Parameters

The folloWing table~Specifies the circuit parameters;
Table

Circult

Type

Data

Number

Type = Type

Inf.

Parameters

App.

Set.

NCP

Rest.

Keywords

C-1

STATE

C-1

SUBSTATE

100

C-1

- C

110

DU-2

120
121

HI-6
Cc-1

200

SERVICE
|

S*,0Q
s*

CM-1/2
Ss*
-

DU-2

201

AI-6
CM-1/2

400
800

‘

object
object

S*
S*[1],0Q

RO
RO

node

|
RO

node

address

node

name

BLOCK

(optional)

810

DU-2

811
900
901
902
906

DU-2
DU-1
DU-1
DU-1
- DU-2

C
C
C
C
C

907

" DU-2

910

c-1

BLOCKING

520

DU-1

MAXIMUM RECALLS

921
930

DU-2
AI-16

C
C

NUMBER

address

node name (optional)
DESIGNATED ROUTER

AI-6

number
name

LOOPBACK NAME
ADJACENT NODE

AI-6
CM-1/2

NODE

address

'node name (optional)
- CONNECTED OBJECT

DU-2

CONNECTED

‘bu-2

801

AI-6=
CM-1/2

TIMER

SERVICE PHYSICAL ADDRESS
SERVICE SUBSTATE
»
node

- DU-1
AI-16

COUNTER

RO
RO

180

SIZE

ORIGINATING QUEUE
COST
MAXIMUM ROUTERS
ROUTER PRIORITY
HELLO TIMER

LISTEN TIMER

RECALL

TIMER

“
LIMIT

Parameter

and Counter

CM-2/3
C-1
AI-16

1000

Binary

Formats

and Values

USER
Entity type
Entity name

DU-2

(if

1010

C-1

1011

C-1
CM-2/3

S*
C

1110
1111

AI-16

C-1

USAGE

1112

C-1

- C

TYPE

1120

AI-16

DTE

1121

DU-2

CHANNEL

1122

DU-2

MAXIMUM

DATA

1123

DU-1

MAXIMUM

WINDOW

1140
-

DU-1

TRIBUTARY

1100

POLLING

STATE

Polling
OWNER

substate

(Format same as

1141

DU-2

BABBLE

11472

DU-2

TRANSMIT TIMER

1145

C-1

MAXIMUM

BUFFERS

1146

DU-1

- C

MAXIMUM

TRANSMITS

1150

DU-1

ACTIVE

BASE

1151

DU-1

ACTIVE

INCREMENT

1152

DU-1

INACTIVE BASE

1153

DU-1

INACTIVE

INCREMENT

1154

DU-1

INACTIVE

THRESHOLD

TIMER

1155

DU-1

DYING

1156

DU-1

DYING

INCREMENT

1157

DU-1

DYING

THRESHOLD

1158

DU-1

DEAD

[1]

SHOW CIRCUITS STATUS for broadcast

_The

The

nodes.

SHOW

CIRCUITS

router

adjacent

nodes.

values

for

STATE

Value

Keyword

OFF
- SERVICE

wvalues

vValue

SUMMARY

BASE

THRESHOLD

circuits

for broadcast

are:

CLEARED

for

for USER)

LINE

W+
O

181

entity is not
node)
Node address (if entity is
node)
Node name (if entity is node)

AI-6

Page

SUBSTATE

Keyword

STARTING
REFLECTING
LOOPING

and

SERVICE

SUBSTATE

are:

shows

all

circuits

adjacent

shows only

The

HOWOOJOYO
b W

Parameter

values

and Counter

Binary Formats

and Values

Page

182

LOADING
DUMPING

TRIGGERING
AUTOSERVICE
AUTOLOADING
AUTODUMPING

AUTOTRIGGERING

SYNCHRONIZING

FAILED

for

SERVICE

Value

Keyword

ENABLED

DISABLED

are:

The values for BLOCKING are:
Value
0
1

Meaning
ENABLED
DISABLED

The values for entity type and entity name can
7.101‘

The

values

= wnN
B+ O

Value

values

STATE

are:

Keyword
AUTOMATIC
ACTIVE
INACTIVE
DYING
DEAD

for

polling

Keyword

N+

Value

POLLING

ACTIVE

" The

for

DYING

INACTIVE
DEAD

substate

are:

found

section

Parameter and Counter Binary Formats and Values
The

values

for

Value
0

INCOMING

OUTGOING

values

for

Value

The

TYPE

are:

Meaning
DDCMP

POINT

DDCMP

CONTROL

DDCMP

TRIBUTARY

X25
DDCMP

DMC

Ethernet

CI
QP2

(DTEZ20)

BISYNC

values

for

MAXIMUM

Range

Meaning

1-254

Number

255

7.3

are:

PERMANENT

The

USAGE

Meaning

OO JOWUTEWNHO

)

Page 183

Circuit

BUFFERS

are:

buffers

UNLIMITED

Counters

The circuit entity counters are listed in Tables 6-8,

following.

The

definition
of
each counter and the way that it is 1incremented
can be
found in the functional specification for the appropriate layer.
Due
to hardware characteristics, some devices cannot support all counters.
In general, those counters that
make
sense
are
supported
for
all
devices.
Specific exceptions related to the DMC are noted in Appendix
I )

)

Circult counters are specifiedAfor the'followifig layers only:
Type
Layer

Network

Management

000

099

800
1000

899
1999

Rout ing
Data Link

The

counters

following
type

number

805,

Number

Range

are

which

kept
is

for

X.25

all

only.

circuits,

with

the

exception

Parameter and Counter Binary Formats and Values
Table

Circuit Counters Kept

counters

apply

Table

Data Link Circuit Counters
Type
Number

Bit
Width

1000

Bytes

Receilved

1001

Bytes

Sent

1010

Data Blocks Received

1011

1020

Data

Blocks

for DDCMP Circults
Bit Number
Standard Text

Standard Text

Data Errors

to DDCM

Sent

Inbound

1 NAKs Sent,
Block
2

1021

Data Errors Outbound

NAKs

Sent,

Block

NAKs

2
|

Check

Response

Header

error

Check

Data

Field

error

NAKs Received,

REP

Response

8
8
8

Remote Reply Timeouts
Local Reply Timeouts
Remote Buffer Errors

0
1
|

1041

error

REP

Received,

Block

1040
-

Data Field

Check

0 NAKs Received,

1030
1031

Link

following Data

Transit Packets Sent
Transit Congestion Loss
Circuit Down
Initialization Failure

'-1
N

The

Seconds Since Last Zeroed
Terminating Packets Receilved
Originating Packets Sent
Terminating Congestion LoOSS
Corruption Loss
Transit Packets Recelved

.._J

811
812
820
821

16
32
32
16
8
32
32
16
8
8

Standard Text

0
800
801
802
805
810

Bit
Width

for All Circuits

dv,

Type
Number

Page 184

Local Buffer Errors

Selection Intervals

1051

Selection Timeouts

Elapsed

NAKs

Received Buffer

Small

NAKs Sent Buffer
Unavallable

NAKs

1050

NAKs Received Buffer
Unavaillable

Sent
Small

Buffer

Too

0 No Reply to Select
1l

Incomplete
Select

Too

Parameter and Counter Binary Formats and Values

)

Page

185

The following Data Link counters apply to permanent X.25 circults:
Table

Data Link Circuit Counters for Permanent X.25 Circults
Bit
wWidth

Type

Number

32
32

1000
1001
1010

32
32
8
8
8

1011

1240
1241

1242

fol lowing

The

Standard Text

Bytes

received

Bytes

sent

Data

blocks

received

Data blocks

sent

Locally initiated resets
Remotely 1nitiated resets
Network initiated resets

table

Data

specifies

I.ink

for

circuilts

Table

Data Link Circuit Counters for Ethernet Circults
Bit
Width

Type

Number

32
32
32
32
16

1000
1001
1010
1011
1065

Line

7.4

Standard Text

Seconds Since Last Zeroed

Bytes Receilved
Bytes

Sent

Data Blocks Received
Data Blocks

Sent

User buffer unavailable

Parameters

The following table specifies the line parameters:

Line

Table 10
Parameters

Type

Data

Set.

NCP

Number

Type

Rest.’

Keywords

0
1
100

110
1100
1105
1110

C-1

Cc-1
C-1

DU-2
AI-16

DU-2
C-1

STATE

substate

(not a keyword)

SERVICE
COUNTER TIMER
DEVICE

RECEIVE BUFFERS
CONTROLLER

Ethernet

Parameter
and Counter Binary Formats and Values

1111

C-1

1112

C-1

PROTOCOL

1113

C-1

CLOCK

1120
1121

DU-2
DU-2

C
C

RETRANSMIT

1122
1130

DU-2
DU-2

C
C

MAXIMUM

1131

DU-1

MAXIMUM RETRANSMITS

1132

DU-1

MAXIMUM WINDOW

1150

DU-2

SCHEDULING

1151

DU-2

DEAD

1152

DU-2

DELAY

1153

DU-2

STREAM

1160

HI-6

The values
7.2

for

circuit

SERVICE

TIMER
TIMER

HOLDBACK

STATE,

TIMER

TIMER
TIMER

HARDWARE

substate,

TIMER
BLOCK

TIMER

ADDRESS

and SERVICE
are as

parameters.,

(names)

Section

are:

Name

Device

0
1

DP
UNA
DU

DP11-DA (OBSOLETE)
|
DEUNA multiaccess communication

link
line 1interface
|
asynchronous line 1interface

DU11-DA

synchronous

DL11-C,

-E

CNA
QONA

listed

Value

186

DUPLEX

Communication DEVICE mnemonics

2
3
4
5

Page

-WA

DQ11-DA

7
8
9
10
12

CI
DA
PCL
DUP
DMC

14
16

DN
DLV

Computer Interconnect interface
DA11-B or —-AL UNIBUS link
PCL11-B multiple CPU link
DUP11-DA synchronous line 1interface
|
DMC11-DA/AR, -FA/AR, -MA/AL or -MD/AL 1nterprocessor
link
DN11-BA or -AA automatic calling unit
.
DLV1l1-E, -F, -J, MXV11l-A or - B asynchronous line

18
20
22
24
28
30

DMP
DTE
DV
DZ
KDP
KDZ

32
34
36
38
40
42

KL
DMV
DPV
DMF
DMR
KMY

KMX

(OBSOLETE)

interface

DMP1ll multipoint 1interprocessor link
DTE20 PDP-11 to KL10 1interface
|
DV11-AA/BA synchronous line multiplexer
DZ11-A, -B, -C, or -D asynchronous line multiplexer
KMC11/DUP11-DA synchronous line multiplexer
KMC11/DZ11-A, -B, -C, or -D asynchronous
line
multiplexer
KL8-J (OBSOLETE)
|
DMV1l 1interprocessor link
DPV11l synchronous line 1interface
DMF-32 synchronous line unit
DMR11-AA, -AB, -AC, or -AE interprocessor link
KMS11-PX synchronous line interface with X.25 level
microcode
|
|
KMS11-BD/BE synchronous line interface with X.25

Parameter and Counter Binary Formats and Values
level

The values

CO~JOoOYOT
W
H+HO

Value

The values

Value
0
1

The values

‘

Page 187

2 microcode

for PROTOCOL are:

Meaning
DDCMP
DDCMP
DDCMP

POINT
CONTROL
TRIBUTARY

DDCMP

DMC

(reserved)

LAPB

Ethernet
CI

QP2

for

(DTEZ20)

DUPLEX

are:

Keyword
FULL
HALF

for CONTROLLER are:

Value | Keyword
0
1

NORMAL
LOOPBACK

The values for CLOCK are:

7.5

Value

Meaning

0
1

EXTERNAL
INTERNAL

_Line

Counters

The following table specifies the Data Link counters for LAPB lines.

Parameter and Counter Binary Formats and Values

Data

Type
Number

Bit
Width

Link

Line

Standard

"Table ll
Counters

for

Last

LAPB

Lines

Bit Number
Standard

Text

Since

Page 188

Seconds

1000

Bytes

1001
1010
1011

32
32

Data

Blocks

Received

1020

Data
Data

Blocks
Errors

Sent
Inbound

Text

Zeroed

Received
Sent

Bytes

1021

Data

1030

Remote

Errors

1031

Local

1040

Remote

1041

Local

1100

Remote

Outbound

Reply
Reply

Block

too

long

5
3

REJ
REJ

sent
received

RNR

received,

check

error

Timeouts
Timeouts

Buffer
Buffer

Errors
Errors

buffer

unavaillable

RNR

sent,

buffer

unavallable
Station

Errors

Invalid

FRMR

sent,

1101

Local

Station

Errors

=
N

format

N(R)

received

header

error

Transmit

underrun

Receive overrun
FRMR received, head
format

error

~The following table specifies Data Link counters
for DDCMP lines:

Data
Type
Number

Bit
Width

Link

Table 13
Counters for

Line

Standard

1020

Data Errors

1100

Remote

DDCMP

Lines

Text

Bit Number
Standard

Inbound

NAKs

check error
NAKs received,

NAKs

Station

Errors

Text

sent,

header

block

receive

overrun

sent,

format

header

error

Selection

address

3
0

Streaming tributaries
NAKs sent, receive

Recelve

errors

Local

Station

Errors
'

overrun

not
N

1101

overruns,

NAK

sent

Transmit underruns
NAKs received, header
format error
|

Page 189

Parameter and Counter Binary Formats and Values

The following table specifies Data Link counters for Ethernet lines:

‘>

Table

13.1

Data Link Line Counters for Ethernet Llnes

Bit
Width

0
1000

16
32

Seconds Since Last Zeroed
Bytes Received

1001

Bytes

1011

1002
1010

1012

1013

)

1014
1015

1060

Standard Text

Sent

32
32

Multicast Bytes Received
Data Blocks Receilved

Multicast Blocks Received

32
32

Blocks sent, single collision
Blocks sent, multiple collisions

Data Blocks Sent

1061

1062

‘>

7.6

1063

1065
1066

16
16

1064

)

Blocks sent, initially deferred

1 Carrier check
2 Short circult
3 Open circuilt
Frame

5 Remote

Collision detect check failure

too

|
]

failed

long

fallure to defer

1 Framing error

Frame

Unrecognized frame destination
Data

0 Block check error

Receive failure

0 Excessive colllslons

Send failure

Bit Number
Standard Text

Type
Number

too

long

overrun

System buffer unavallable
User buffer unavaillable

Logging Parameters

When represented in binary, sink type is:
SINK TYPE (1):

Represents the logging sink type as follows:
Value

Active sink types

-2

Known sink types

-1
1

CONSOLE

FILE
MONITOR

Sections 7.11
associated

parameters).

and

7.12

Meaning

define

all

the

event

classes

and

their

events and parameters (not to be confused with the logging

Parameter

and Counter

Binary

Formats

Line and node counters provide
are
no
logging
entity
characteristics, and events.

The

following

table

specifies

and Values

information
counters

the

logging

Page

for event
specified,

1logging.
just

There
status,

parameters:

Table 14
Logging Parameters
NICE
Param.

Data

Type

Info

Appl

NCP

Type

Restr.

Keywords

C-1

100

AI-255

200

CM-1/2
DU-2

CEV*

AI-6

201

E
E
S
|

CM-2/3/4/5

|
S

AI-6

|
AI-16

|
C-2
HI-8

The

values

Value

The

STATE

HOLD

-1
0

are:

Keyword

OFF

for

entity

type

are:

Meaning
No

entity

NODE

LINE

CIRCUIT

MODULE

AREA

event class

name

(optional)

EVENTS

|
Entity type
Node address

(if entity type
is node)
Node name (if entity type 1is
node) (optional)
Entity id (if entity type is
not node)
class
mask (if single
class indicated)

values

SINK NODE
Node address

Event
Event

0
1

Value

The

for

STATE

Node

EV*

C-1
DU-2

NAME

specification

is:

190

event

Parameter and Counter Binary Formats and Values
Bits

14-15

-8

Page

191

Meaning
0
2

= Single class
= All events for

KNOWN

class

EVENTS

Event class if bits 14-15 equal 0 or 2.

The event mask specification is:

Event mask, bits set to correspond
Low

7.11).

Section

bytes

order

event

first.

types

(Table

22,

High order bytes not

list
Format for NCP input or output is a
present imply 0 value.
Only
3.2).
(Section
set
bits
the
to
ng
correspondi
of numbers
present if EVENT CLASS is for a single class (bits 14-15 = 0).

NOTE
for
The wild card and KNOWN EVENTS specifications are
class
a
as
events
read
Return
only.
events
changing
|

and mask.

7.7

Module

7.7.1

The

Parameters

Console Module

Parameters

table

specifies

following

malntenance

the

console

module

parameters.

Table

l4a

Parameters

Console Module

Type

Data

Inf.

Number

Type

110

DU-2

7.7.2

The

Loader Module

following

parameters.

table

App.

Rest.

NCP

Set.

Keywords

Rest.
~

RESERVATION TIMER

the

maintenance

Parameters

specifies

loader

module

Parameter and Counter Binary Formats and Values
Table

Page 192

14Db

“)

Loader Module Parameters
Type

Data

Inf.

App.

Number

Type

Rest.

c-1

10
The

for

value

Meaning

ENABLED

DISABLED

The

Set.

NCP

Rest.

Keywords

ASSISTANCE

values

7.7.3

ASSISTANCE

are:

Looper Module Parameters
following

table

parameters.,

specifies

malntenance

looper

module

Table l4c

Looper

Type

Data
Type

Type

c-1

Number

the

Inf.

Module

App.

Set.

Rest.

Rest.
*

Parameters

)

NCP

Keywords
ASSISTANCE

The values for ASSISTANCE are:
Value

Meaning

ENABLED

DISABLED

7.7.4

Configurator Module

The following
parameters.

table

Parameters

specifies

the

|
maintenance

configurator

module

Page 193

'Parameter and Counter Binary Formats and Values
Table

14d

Configurator Module Parameters

Data

Type

Inf.

Number

Type

100

AI-16

C-1
CM-3

110
111

App.

Rest.

Set.

Rest.

CIRCUIT

S*
S*

Q
Q

SURVEILLANCE
ELAPSED TIME

RO
RO

Minutes
Seconds
PHYSICAL ADDRESS
LAST REPORT

DU-2

DU-1
DU-1
HI-6
CM-5

120
130

S,Q
S

Q
Q

DU-1

1002

1003
1004
1005
1006
1007
1100

CM-1-16 S

C-1

HI-6
DU-2
DU-2
DU-2
HI-6
C-1

DU-1

‘

S
S
S
S
S
S

CM-1/2 S
C-1

1200

Q
Q
Q
Q
Q
Q

RO
RO
RO
RO
RO
RO

C-1

1401

DU-2

C-1

1400

The values

for

Minute
Second
MAINTENANCE VERSION
Version number
ECO number

User ECO number

FUNCTIONS

1-16 functions

CONSOLE USER
RESERVATION TIMER
COMMAND SIZE
RESPONSE SIZE
- HARDWARE ADDRESS
o
DEVICE

|
ATION
IDENTIFIC
SOFTWARE
Generic Software type

Software ID string (present

AI-16

1300

Day

Hour

DU-1

1001

Hours

Month

C-1

DU-1
DU-1
CM-3
DU-1
DU-1

NCP

Keywords

only if generic
type > 0)

software

SYSTEM PROCESSOR.

- Q

DATA LINK BUFFER SIZE

DATA LINK

are:
SURVEILLANCE

Value

Meaning

0
1

ENABLED
DISABLED

The values for SYSTEM PROCESSOR and DATA LINK are found in the DNA Low
The values for DEVICE are
Level Maintenance Operation specification.

The format and
the same as for the node parameter SERVICE DEVICE,
DNA Low level
the
in
found
are
values of SOFTWARE IDENTIFICATION

Maintenance Operation specification.

Parameter

and Counter Binary Formats and Values

Page

NOTE

194

The parameter type values for
the
1information
taken
from
the
DNA
Low Level Maintenance Operation System
Identification message are the
parameter
types
from
that message plus

1000.

The values for FUNCTIONS are the corresponding
bit
numbers
for
the
functions in the similar fields in the System Identification message.
The values for LAST REPORT
month
are
keywords JAN through DEC, respectively.

The

X.25

Access Mcdule

following

the X.25

Type
Number

Table

Access

Data
Type

Inf.
Type

320

CM-1/2

330

AI-39

332
1110

AI-39
AI-16

C
Q

DU-2

App.
Rest.

AI-6

331
331

AI-39
C-1

Set.
Rest.

7.7.6

The

If it

node address
node

WO
RO

Password

X.25

Protocol

following

table

name

USER

PASSWORD
- PASSWORD

(optional

|
if

none)

there

(to set)
(to read)

1ts value

not

1is:

present 1f

set

Module

ACCOUNT
NETWORK

is present,

Meaning

Parameters

NODE

Q
0

Value

NCP
Keywords

On output, the PASSWORD'parameter 1s
password.

month

access module parameters.

Module

C
C

Parameters

table specifies

X.25

corresponding

7.7.5

1-12

Parameters

specifies

the X.25

protocol module parameters.

Parameter and Counter Binary Formats and Values
Table

“}

Type

Number

100
1000

1010

1100
1101
1110
1120

1130

Type

C-1

C
S*

Q
Q

DU-2

AI-16
AI-16
AI-16
AI-16

CM-1/2

DU-2

Q
Q
C
C

Rest.

RO
RO

1151
1152

1154

DU-1

Value
0
1
2

The values

DTE
GROUP
NETWORK
LINE

range beginning

beginning)

MAXIMUM CHANNELS
MAXIMUM CIRCUITS

STATE

MAXIMUM RESETS

Q
Q
Q
are:

ON
OFF

SHUT

Substate

Running

Unsync

Sync

DEFAULT DATA
DEFAULT WINDOW
MAXIMUM DATA

MAXIMUM RESTARTS

Value Meaning

ACTIVE SWITCHED

Meaning

for

Substate (not a keyword)

COUNTER TIMER
ACTIVE CHANNELS

MAXIMUM WINDOW
MAXIMUM CLEARS

C
C
C

for

STATE

C
C

C
C
C
C

AI-16
DU-2
Cc-1

Thevvalues

Q
Q

DU-1
DU-1
DU-1
DU-1

Keywords

range end (none 1f same as

C
C
C

DU-1

1153

NCP

CHANNELS

C
C

DU-2
DU-2

1170
1171
1172

Set.

DU-2

1160
1161
1162
1163

)

Rest.

DU-2
DU-2

App.

C-1

DU-2
DU-1
DU-2
DU-1
DU-1

1140
1141
1150

Inf.

Data

Type

|
1131
1132

X.25 Protocol Module Parameters

Page 195

are:

CALL TIMER
CLEAR TIMER
RESET TIMER
RESTART TIMER

- DTE (qualified by GROUP)
NUMBER (qualified by GROUP)
TYPE (qualified by GROUP)

Parameter

and

Counter

The

for

TYPE

value

Value

The

Formats

and

Values

1is:

X.25 ServervModule‘Parameters
table

specifies

the

X.25

Table
X.25

Server

server

module

Parameters

Type

Data

1Inf.

App.

Set.

NCP

Type

Rest.

Keywords

100

DU-2

COUNTER

TIMER

200

DU-2

ACTIVE

CIRCUITS

300

AI-16

310
320

C
C

352

DU-2
CM-1/2
DU-2
AI-6
"AI-39
AI-39
C-1
AI-39
CM-1/2
DU-1
AI-16
DU-1
HI-16
HI-16

353

AI-16

354
355
|

C
C

Q
Q

DESTINATION
MAXIMUM CIRCUITS
NODE
node address
node name (optional)
USER user
|
|
PASSWORD (to set)
PASSWORD (to read)
ACCOUNT
OBJECT
object number
object name
PRIORITY
CALL MASK
CALL VALUE

GROUP

AI-16

NUMBER

CM-1/2
DU-2

SUBADDRESSES
range beginning

C
C
C
C
C

Q
Q
Q
Q
Q

WO
RO

DU-2

parameters.

Module

Number

350
351

196

BILATERAL

following

- 330
331
331
332
340

Page

Meaning

7.7.7

Binary

output,

password.

the

range

end (none
beginning)

PASSWORD

parameter

present,

Value

Meaning

Password

set

its

not

value

1is:

present

same

there

Parameter and Counter Binary Formats and Values
Module

7.8

Page 197

Counters

X.25 Protocol Module Counters

7.8.1

the

The following table specifies

X.25

protocol

module

local

counters.

Table

X.25 Protocol Module Counters
|

Bit

Type

Standard Text

Number

Width

0
1000

16
32

Seconds since last zeroed
Bytes received

Data blocks received

1001

1011

1010

Bytes sent

Data blocks sent

1200

Calls received

1210

Fast selects receilved

1201

1211

1221

1220

1230
1240

Fast selects sent

Maximum switched circuits activ

16
8

Received call resource errors
Locally initiated resets

8
8
8

1241
12472
1250

Calls sent

Maximum channels active

Remotely initiated resets
Network initilated resets
B
Restarts

X.25 Server Module Counters

7.8.2

The following table specifies the X.25 server module counters.
Table

X.25 Server Module Counters
Type

Bit

Number

Width

0
200
210
211

16
16
8
8

7.9

Node

Standard Text

Seconds since last zeroed
Maximum circuits active
Incoming calls rejected, no resources
Logical links rejected, no resources

Parameters

The following table specifies the node parameters:

DTE

Parameter and Counter Binary Formats and Values

Table

Node
Param.

NICE

Type

Data

Number

Type

Parameters

Inf.

Appl.

Set.

NCP

Type

Rest.

Keywords

PHYSICAL

IDENTIFICATION
MANAGEMENT VERSION

C-1

E,R

HI-6

100
101

AI-32
CM-3

C*
C

E
B

STATE
ADDRESS

DU-1

version

DU-1

ECO

number

User

ECO

DU-1

110

Page 198

number
number

AI-16

SERVICE

CIRCUIT

H-8

SERVICE

PASSWORD

C-1

SERVICE

DEVICE

113

C-1

CPU

114

HI-6

HARDWARE

115

C-1

SERVICE

120

AI-255

LOAD

111

112

ADDRESS
NODE

VERSION

FILE

121

AI-255

SECONDARY

122

AI-255

C(C

TERTIARY

LOADER

123

AlI-255

DIAGNOSTIC

125

C-1

SOFTWARE

LOADER
FILE

TYPE

126

AI-16

SOFTWARE IDENTIFICATION

130

AI-255

C(C

DUMP

131

AI-255

SECONDARY

O-4

DUMP

ADDRESS

DUMP

COUNT

135

136

DU-4

140

CM-1/2

DU-2

AI-6

141

(node-1id)

A,E

150

DU-2

151

DU-2

152

C-1

FILE
DUMPER

HOST
Node

address

Node

name

HOST

LOOP

LENGTH

LOOP

WITH

(optional)

COUNT

153

HI-6

LOOP

ASSISTANT

154

C-1

- LO

LOOP

HELP

155
156

(node-1id)
(node-1id)

E
E

LO
LO

LOOP NODE
LOOP ASSISTANT NODE

E,R

NAME

160

DU-2

500

(id-string)

E,R

501

AlI-16
DU-2
DU-2
DU-2
DU-2

C*
n/a
C
- C
S*

Q,L,N
E
E
E
E,R

DU-2
CM-3

S*
C

R
E

502
510
511
600

601
700

COUNTER TIMER

CIRCUIT.
ADDRESS
INCOMING TIMER
OUTGOING TIMER
ACTIVE LINKS

RO
RO

DELAY
NSP VERSION

DU-1

version

DU-1 -

ECO

number

User

ECO

DU-1

710

DU—2V

720

DU-1

C
C

E
E

PHYSICAL

number
number

MAXIMUM LINKS
DELAY FACTOR

ADDRESS

Page 199

Parameter and Counter Binary Formats and Values

TYPE

COST

HOPS

CIRCUIT

C
C

E
E

TYPE

SUBADDRESSES

C
C
C
C
C
C
c
C
C
C
C
C
C
C

BROADCAST ROUTING TIMER
MAXIMUM ADDRESS
MAXIMUM CIRCUITS

STATE

are:

ROUTING

Version number
ECO number
User ECO number

912
920
921
922
923
924
925
1926
927
928
929
930
931
932

DU-2
DU-2
DU-2
DU-2
DU-1
DU-1
DU-1
DU-2
DU-2
DU-2
DU-1
DU-2
DU-2
DU-2

The values

N WO

Value

for

o))
)]

N
o)

beginning)

HOPS

MAXIMUM

VISITS

MAXIMUM

AREA

MAXIMUM

BROADCAST

MAXIMUM

SEGMENT

Executor

OFF

Executor

SHUT

Executor

RESTRICTED

Executor

Mailintenance

NONROUTERS
ROUTERS

BUFFERS

BUFFER SIZE

Node

UNREACHABLE

COST

MAXIMUM

MAXIMUM BROADCAST
AREA MAXIMUM COST
AREA MAXIMUM HOPS

Keyword

REACHABLE

MAXIMUM

BUFFER SIZE

Destination
Destination

The values for SERVICE DEVICE are the same as found
Level

beginning
|..-J

range

DU-2
DU-2

)]

CM-1/2

TIMER

911

ROUTING

DU-1

)

DU-1

c-1
DU-2

VERSION

DU-1

901
910

(optional)

Do EHHEDEENEEEE

CM-3

address

Node name

AI-6

900

NODE

Node

DU-2

)

R
R

S*
S*

INACTIVITY TIMER
RETRANSMIT FACTOR

AI-16
CM-1/2

DELAY WEIGHT

)

822
830

E
BE
E
A
R
R

C
- C
C
S
S
S

DU-1
DU-2
DU-2
c-1
DU-2
- DU-1

o))
3
Vo)
(D

721
7272
723
810
820
821

Operation specification.

the

DNA

Low

They are also defined 1n

section 7.4, following Table 10, under Communication DEVICE mnemonics.

)

Parameter

values

for

Value

Type
PDP8

values

are:

for SOFTWARE TYPE

SECONDARY LOADER
TERTIARY

LOADER

SYSTEM

for

NODE NAME

HOST

are:

(2):

node

address.

(I-6):

Host node name,

Type

The

for

LOOP

WITH

zero length if none.
are:

~Contents

0
1

ONES

MIXED

values

are:

Program Type

Host

values

and Values

DECSYSTEM1020

NODE ADDRESS

The

Formats

VAX

Value
0
1
2

Binary

PDP11

The values

The

CPU

W N~
O

The

and Counter

ZEROES

for

LOOP

HELP

Type

Contents

0
1

TRANSMIT
RECEIVE

FULL

are:

Page

200

Parameter and Counter Binary Formats and Values

Page 201

The values for executor and adjacent node TYPE are:

‘)

WwWH O

Keyword
ROUTING III
NONROUTING III

Value

ROUTING IV
NONROUTING

AREA

The values for SERVICE NODE VERSION are:
Value

PHASE III

PHASE IV

)

Keyword

Node Counters

7.10

The definition of each
Table 21, below, lists the node counters.
counter and the way it is to be incremented 1is given in the functional
specifications for the layer containing the counter.

Node counters are specified for the following layers only:

Type Number

Range

Layer

000 - 09°S
600 - 700
900 - 999

Network Management
End Communication
Rout ing

Type Number

Bit width

Standard Text

Seconds Since Last Zeroed

600

User Bytes Recelved

602

User Messages Recelved

608

601

603

610

611

- DN

DN
DN
B

609

)
i

Node Counters

Appl.

Table 21

620

621

630
640
700

16
16
16

User Bytes Sent

User Messages Sent

Total Bytes Received
Total Bytes Sent

Total Messages Received

Total Messages Sent

Connects Received
Connects Sent

Response Timeouts
Received Connect Resource Errors
Maximum Logical Links Active

Parameter and Counter Binary Formats and Values

Page 202

900

Aged

Packet

901

Node

Unreachable

902

Node

Out-of-Range

903

Oversized

910

Packet

E
E

920
930

8
8

Partial Routing Update
Verification Reject

7.11

Area

The

following

table

specifies

the

area

Table

Format

Loss

Packet

Loss

Error

Loss

parameters:

21l1a

Parameters

Param.

NICE

Appl.

Set.

NCP

Type

Data

Type

Rest.

Keywords

Number

Type

0
820

C-1
DU-2

S*
S

RO
RO

STATE
COST

821

DU-1

HOPS

822
830

AI-16
CM-1/2

S*
S*

RO
RO

CIRCUIT
NEXT NODE

DU-2

Node

address.

AI-6

Node

name

values

Value

7.12

Packet

Parameters

Area

- The

Loss

Event

for

STATE

(optional)

are:

Keyword

Node

REACHABLE
UNREACHABLE

Destination

Definitions

Table

22, following, defines the event classes.
The
event
shown
1n
Table
22
1S a composlite of the system type and
specific event class.

Table
Event

Classes

Event

Class

0
1

Description

Network Management Layer
Applications

Layer

class

the

system

Page 203

Parameter and Counter Binary Formats and Values
2

Session Control Layer

Routing

End Communication Layer

Layer

Data Link Layer
Physical Link Layer

5
6

Reserved for other common classes
RSTS System specific
RSX System specific
TOPS 10/20 System specific
VMS System specific
RT System specific
CT System specific
Communication Server specific

7-31
32-63
64-95
96-127
128-159
160-191
192-223
224-255

Reserved for

256-479

future use

Customer specific

480-511

In the following descriptions, an entlty related to an event 1nd1cates
that the event can be filtered specific to that entity. Binary
logging data is formatted under the same rules as the data 1n NICE

data

(see Section 7.1).

Table 23 shows the events for each class.
Table

Events

Class Type
0

none

circuit

0
0
-

1
2

Standard Text

Entity

Event records lost

Automatic node counters
Automatic line counters

node
line

)

Automatic service
/

Event

Parameters

and Counters
|

none

Node counters
Line counters

Service
Status

Node

Filespec

Software

type

0
0

4
5

line
node

Line counters zeroed
Node counters zeroed

Circuit counters
Node counters

circuit
«

Aborted service request

Reason
Node

0
0
2

8
9
0

circuit

any

any
none

Passive loopback

Automatic counters
A

Counters zeroed
v

Local node state change
:

Operation

Qualifier
Counters

DTE

Qualifier
Counters
DTE

Reason

Old state

New

state

Parameter

and Counter

‘none

Binary

Access

Formats

control

and Values

reject

Page

Source

node

Source

process

Destination

process

User

Password
Account

‘Invalid message

none

Message

Source
Invalid

none

flow control

Source
node

Data

base

none

cilrcuilt

Aged
Node

circuilt

Node

circult

packet loss
Oversized packet

circult

Packet

circuit

Partial

Current flow control
node counters

packet

loss

error

routing update

Verification reject
Circuilt

down,

circuilt

Circuilt

header

down

Adjacent node
Packet header
Adjacent node
Packet beginning
Adjacent node
Packet header
Highest address
Adjacent node
Node
Reason

Circuilt down,
initiated

TSNS

circuit
circuilt

clrcult

Circuit up
Initialization
line fault
Initialization

cilrcult

operator

node

Reason

Packet

header

Adjacent

circuilt

node

header

Adjacent

fault

circuilt

header

Packet

loss

circuit
circuilt

Packet

Adjacent

out-of-range

format

Node

NSP

reused

packet loss
unreachable
|
loss

Node

Message

node

Reason

Packet header
Adjacent node
Adjacent node

failure,

Reason

failure,

Reason

software fault
Initialization failure,

Packet

operator

Packet

fault

header

Reason

header

N
TS

Received version
14

node

clrcuilt
circuilt

Node reachability change Status
Adjacency up
- Adjacent
Adjacent
Adjacency rejected

area

Area reachability change

16
17

circuit

Adjacency down

node
node

Reason

Status
Reason

Packet header
Adjacent node
19

circuilt

Adjacency down,

Reason

operator

Packet header
Adjacent node
Old state

Locally
change

initiated
initiated

state

New

state

204

Parameter and Counter Binary Formats and Values
5

circuit

New

Protocol

restart

received

3
4
5

circult
circuilt
circult
circuilt

1n malntenance

Send error threshold
Receive error threshold
Select error threshold
Block

header

format

error

address

circuilt

Selection

circult

Streaming tributary

circuit

Local

module

Restart

module

5
5

13
14

module

buffer

too

line

Selected tributary
Received tributary
Previous tributary
Tributary

Block length
Buffer length

DTE

(X.25 protocol)

Reason

Retransmit maxilmum

Cld

state

New

state

DTE

Parameter

failure

Receive failed

5
5
6

module
module

DTE

down

line

Unexpected carrier

6
6

3
4

line
line

Memory

DTE

Data set ready
transition
Ring indicator
transition

transition
access

Communications

error

1interface

DTE

New

state

New

state

New

state

Device
Device

Device

error

7.13

Event

line

Performance

error

Parameters

The following parameter types are defined for the
Layer

header

check

Collision detect
failed
|

type

none
Failure reason
Distance
Failure reason
Ethernet

line

status

Received tributary

Diagnostic

change

line

(optional)

Cause

18
0

counters
counters
counters

DTE

Initialization
Send failed

circult

small

(X.25 protocol)

exceeded

line
line

Circult
Circult
Circuilt

" Header

error

State

state

none

mode

5
5
5
5

205

initiated state 0Old state

Remotely
change

Page

(class 0):

Network

Management

Parameter

and

Type

Counter

Binary

Formats

Network

Management

and

Values

Table 24
Layer Event

Data

Type

Keywords

c-1

SERVICE

CM-1/2/3

STATUS

(as

- Page

Parameters

in NICE)

C-1

Return

code

C-2

Error

detail

(optional

if no

message

AI-72
W N

C-1
C-1

REASON

CM-2
C-2
AI-16

Qualifier

CM-1/2
DU-2
AI-6
AI-16
AI-255

NODE

0 O L N Y o)

The

for

values

Value

The

address

name

(optional)
.
|

Filespec

SERVICE

TYPE

are:

LOAD
-

DUMP

for

Return

code

added

Keyword
REQUESTED

SUCCESSFUL

FAILED

Value

Node
DTE

SOFTWARE

values

type

string

Node
-

(optional)

Keyword

0
1

Parameter

C-1

value

The

Error message
OPERATION

for

OPERATION

Keyword

INITIATED

TERMINATED

are:

interpretation

are:

error

206

Page 207

Parameter and Counter Binary Formats and Values
\)

The

values

Value

for

REASON

are:

Reason

Receive timeout
error

Receive

Unrecognized request

Line state change by higher level
Line

error

open

1n Node Parameters.
The values for SOFTWARE TYPE are the same as those
The

following parameter

are

types

defined

for

Session

the

Control

layer (class 2):

- Table

Session Control Layer Event Parameters

Type
0
1
2
3

Data Type

Keywords

C-1
C-1
C-1
CM-1/2
DU-2

REASON
OLD STATE
NEW STATE
SOURCE NODE
node address

AI-6

CM-1/2/3/4
DU-1

DU-2

name present)

CM-1/2/3/4

6
7
8

AI-39
C-1
AI-39

Value
0
1

for

REASON

(if spec1f1ed and group

code present)

AI-16

values

Group code (if spec1f1ed and process

~ User code

DU-2

The

node name (optional if none)

SOURCE PROCESS
Object type

Process name (if specified)

DESTINATION PROCESS

Same as
USER
PASSWORD
ACCOUNT

are:

Meaning
Operator command
Normal operation

for SOURCE PROCESS

Parameter and Counter Binary Formats and Values
The

values

for

Value

OLD

STATE

and

NEW

STATE

Page 208

are:

Meaning
ON

OFF
SHUT
RESTRICTED

A value
of zero for PASSWORD indicates a password was set.
the

parameter

The

following

layer

(class

indicates

password was

parameter

types

are

set.

defined

for

3):

Data

CM-4
H-1

End

Communication

Table 26
Communication Layer Event

End
Type

the

Absence of

Type

MESSAGE
- Message

DS-1

CM-1/2

flags

Destination logical
Source logical link

HI-6
1

Parameters

Keywords

DU-2
DU-2

Message
-~

CURRENT

SOURCE

type

FLOW

link

dependent

CONTROL

address

data

REQUEST

NODE

COUNT

‘

DU-2

Node

address

AI-6

Node

name

(optional)

The following parameter types are defined for the Routing layer (class
4):

- Table

Routing
Type

Data

Type

CM-2/4
- H-1

DU-2

Layer

Event

Parameters

Keywords

PACKET

HEADER

Message

(non-Ethernet)

flags

Destination

node

(not present
DU-2

Source

node

DU-1

Visit

count

address

for

control packet)

address

(not present

for control packet)

Parameter and Counter Binary Formats

Page

and Values

CM-11

PACKET HEADER
Message

DU-1
DU-1
HI-6

Destination area
Destination subarea
Destination Ethernet

DU-1
HI-6

Source
Source

DU-1

DU-1
H-1

Visit count
Service class

DU-1

flags

Source area

subarea
Ethernet

area

PACKET

DU-2
CM-1/2
DU-2

HIGHEST ADDRESS
NODE
node address

CM-1/2
DU-2

EXPECTED NODE
node address

C-1

REASON

CM-3

RECEIVED VERSION

.
address

Protocol type
BEGINNING

HI-6

AI-6

node name

AI-6

(optional

node name (optional

DU-1
DU-1
DU-1
Q0 ~J

address

router

DU-1

none)

if none)
|

Version number
ECO number
User ECO number

c-1

STATUS

CM-1/2
DU-2

ADJACENT NODE
node address

node name

AI-6

(optional

none)

Meaning

Circuit

=
W

Value
O
N = OWoOONOWTOTEEWNDEH

The values for REASON are:

—
D

(Ethernet)

H-1

Data

synchronization

lost

errors

Unexpected packet type
Routing update checksum error

Adjacency address change’

Verification

receive

timeout

Version skew
Adjacency address out of range
Adjacency block size too small
Invalid verification seed value

Adjacency listener receive timeout
Adjacency listener received 1invalid data
Call failed
Verification password required from Phase
Dropped by adjacent node

III

node
~

209

Parameter

The

values

and Counter Binary Formats

for

Value

STATUS

and Values

Meaning
REACHABLE

UNREACHABLE

The following parameter types are defined
(class 5):

Data
Type

Data

0
1
2

C-1
C-1
HI-6

3
5
6
7

Type

Table 28
Layer Event

DU-1

SELECTED
PREVIOUS

C-1

TRIBUTARY

STATUS
RECEIVED TRIBUTARY
BLOCK LENGTH

DU-1
DU-2
DU-2

BUFFER

AI-16
c-1

DTE
REASON

11
12

C-1
c-1

OLD STATE
NEW STATE

13
14
15
16
17
18

C-2
DU-1
DU-1

PARAMETER TYPE
CAUSE
DIAGNOSTIC

LENGTH

C-1

FAILURE

DU-2

DISTANCE

CM-3
HI-6

for

STATE

Meaning

0
1
2

HALTED
ISTRT
ASTRT

event
event

REASON

Source address
Protocol type

Value

(for
(for

ETHERNET HEADER
Destination address

OLD

Parameters

TRIBUTARY
TRIBUTARY

S
10

values

the

Keywords

DU-1

for

- OLD STATE
NEW STATE
HEADER

HI-6
HI-2

The

Link

-8

210

are:

Page

RUNNING

MAINTENANCE

HARDWARE STATUS

and

NEW

STATE

are:

5.12)
5.12)

Data

Link

layer

Parameter and Counter Binary Formats and Values

211

The values for FAILURE REASON are:
VOO OTkWwWwdNEFHO

Value

The

values
Value

0
1

The

wvalues
Value

Meaning

Excessive collisions
Carrier check failed

(OBSOLETE)

Short circuilt
Open circuit
Frame

Data

for

are:

Meaning

Operator command
Normal

operation

for OLD STATE and NEW STATE are:
Meaning

OFF

SHUT

overrun

REASON

to defer

System buffer unavailable
User buffer unavailable
Unrecognized frame destination

0
1

long

failure

Block check error
Framing error

Value

too

Remote

/> The values
;

Page

for

TRIBUTARY

STATUS

are:

‘Meaning

|
Streaming
Continued send after timeout
Continued send after deselect
Ended streaming

The following parameter types are defined for the Physical
(class 6):

Link

layer

Parameter and Counter Binary Formats and Values

Physical
Type
0
1

The

values

Value
0
1

Data

Type

NC
c-1

for

NEW STATE

Meaning
OFF
ON

Link

Table

Layer

Event

Keywords
DEVICE REGISTER
STATE

NEW

are:

Page

Parameters

212

APPENDIX

VERSION COMPATIBILITY

This

appendix

compatibility

describes

between

has separate sections for 2.0 and

mapping

sections.

A.1

between

Versions

2.0

mapping

the

and

4.0

necessary

3.0

and

maintailn

of Network Management.
versions

different

1is

3.0

and

for

4.0.

The

simply the combination of the two

and 3.0

version 3.0 NCP
There are two cases where compatibility is at issue:
with version 3.0
NCP
2.0
version
.and
Listener
2.0
version
with
the module with
of
ity
responsibil
the
is
it
cases,
both
In
Listener.

the later version to provide compatibility, if such compatibility 1is
When possible,
part of the individual products requirements.
new version 3.0
but
versions,
between
mapped
be
to
are
functions
functions are not available from version 2.0 modules.

If it
Version 3.0 NCP supports only the version 3.0 command syntax.
3.0
map
must
it
Listener,
2.0
version
a
with
compatible
be
to
is
s 2.0 NICE protocol and 2.0 responses to
commandto

3.0

output.

Any

2.0 responses that do not map to 3.0 output should be handled through
|
the normal unrecognized response logic.

Version 3.0 Listener supports version 2.0 commands by mapping them to
In
It then maps the 3.0 responses into 2.0 responses.
3.0 functions.
a
with
conflict
not
does
and
mapped
be
cannot
response
a
where
cases
it can be returned unmapped to be handled by the 2.0
2.0 response,
systems normal unrecognized response logic.

In the folloWing mapping specifications, parameters that did not
change between version 2.0 and 3.0 are not mentioned. All mappings
apply to both commands and responses unless otherwise stated.

A.1.1

None

The

Module Entity

A.1.2

the

3.0 module

entity

functions
can be mapped

to version

2.0,

Node Entity

following mappings
Version

3.0

apply to

the

Parameter

CIRCUIT

A.1.3

Page A-2

Version Compatibility

node

Version

entity.
2.0

Parameter

LINE

SERVICE CIRCUIT |

SERVICE LINE

MAXIMUM CIRCUITS

MAXIMUM

Logging

LINES

Entity

For
the 1logging
entity,
the
only
mapping
identification that goes with specific filters.

1is

for

the

entity

For a version 3.0 NCP with a version 2.0 Listener, version 3.0 circuit
and

line

identifications

become

For a version 2.0 NCP with a
line
1dentification becomes

version

2.0

line

identifications.

version 3.0
Listener,
the
version
a version 3.0 circuit identification

where necessary,
1s applied to

the

associated

version

3.0

2.0
and,

1line

NCP with

implication.

A.l.4

Circuit

and Line

The following statements
version 2.0 Listener.

Entities

apply

The following version 3.0 circuit
line parameters of the same name.
STATE

Substate
SERVICE
COUNTER

TIMER

the case

parameters map
,

version

the

3.0

wversion

2.0

Version Compatibility

LOOPBACK

NAME

ADJACENT

NODE

BLOCK

Page A-3

SIZE

- COST
TYPE

TRIBUTARY

None ofi the other version
version 2.0 line.

3.0

The

line parameters map to the vers1on 2. O

following version 3.0

parameters

the

same

circult parameters

can be mapped to

name.

the

line
|

DUPLEX

CONTROLLER
SERVICE

The

TIMER

following version 3.0

parameters of

Version

line parameters

a different

3.0

Version

PROTOCOL

line

version

2.0

line

2.0

TYPE

RETRANSMIT

None of

map

name.

TIMER

NORMAL

the other version 3.0

TIMER

line parameters map to version

2.0

parameters.

The version 3.0 LOOP CIRCUIT and LOOP LINE commands both
version

2.0

line

as do the SHOW,

LIST,

TRIGGER,

LOAD,

commands.

map

and DUMP

The following statements apply to
with a version 3.0 Listener.

the

case of

a version

2.0

NCP

Version 2.0 commands can only be applied to version 3.0 circuits.

Their
application
to
version
3.0 1lines
occurs only by
implication.
The version
3.0
1line
parameters
are
referenced
indirectly
by
the
1line's association with the circuit and thus

appear to the version
Version 3.0 lines that
are

not visible

The

following version

circult

parameters

STATE

Substate
SERVICE
COUNTER

TIMER

LOOPBACK

NAME

ADJACENT

NODE

BLOCK

SIZE

COST
TRIBUTARY

2.0
system
to
belong to
the
«circuit.
are not directly associated W1th a circuilt

the version

2.0

system.

2.0

line parameters map to

the

same

name.

the version

3.0

Version Compatibility

Page A-4

The following version 2.0 line parameters map to the version 3.0

parameters

the

same

line

name,

CONTROLLER
DUPLEX

SERVICE

TIMER

The following version 2.0 line parameters
parameters of a different name.

Version 2.0

A.1.5

version

RETRANSMIT

Logging

to
a
version
2.0 event receiver.
Version
version 2.0 line events unless they are X.25
are

not

link

A.2

Versions

3.0

events

3.0 circult events become
specific, in
which
case

sent.

A version 3.0 event receiver translates version 2.0
data

line

TIMER

A version 3.0 event transmitter does not send new version
they

3.0

PROTCCOL

TIMER

Event

Version 3.0

TYPE
NORMAIL

map

and above

3.0

i1nto

and

circuilt

events.

1line

events

for

4.0

The only mapping between
version
3.0
and
version
4.0
1s
handling
of
area
numbers.
Version 3.0 does not recognize
byte of the address field as the area number.
Therefore,
a

1n
the
the high
version
4.0
node
sending
NICE messages to a version 3.0 node must zero the
area portion of any address field for nodes in the same
area
as
the
version 3.0 node.
|
o
|

Otherwise, the normal
parameters, etc. will

responses
suffice.

unrecognized

functions,

options,

)

B
APPENDIX

MINIMUM

SUBSET

The intent of the Network Management minimum subset is to ensure
provide sufficient
will
products
DNA
all
nodes and
individual
both
manage
capabilities to

whole.
Network

It places
Management

strict requirements
and
architecture
-

configuring nodes and networks.

that

Network Management
the network as a

on the implementers of the
for
guidelines
provides

The minimum subset must be interpreted in the 1light of specific
The Network Management = requirements of an
product requilrements.
a centrally managed network are obviously
in
node
routing
unattended
attended non-routing node in a network with
an
of
those
from
different
t.. Before the proper minimum subset can be
managemen
ed
distribut
fully
r network product, its potential uses as a
particula
a
for
d
determine
|

network node must be defined.

The minimum subset defines those capabilities that must be provided Dby
If the product 1is capable of widely
the product 1mplementers.
the network, the implementers should
within
bilities
responsi
t
differen
t subsets within the product, so
Managemen
Network
different
for
allow
functions are not burdened
fewer
require
that
ations
configur
the
that
o
.
situations
complex
more
of
nts
requireme
the
by
The minimum subset contains the smallest

set

Network

Management

functions necessary to diagnose network problems that have a general
level of negative effect, and remove the communications paths or nodes
It does not contain sufficient functions to
that are at fault.
general
provide complete fault diagnosis, network planning, or
control.

Following are the minimum, general capabilities that are required for
node and network management. Unattended nodes, nodes with no console,
or nodes that are to be remotely controlled must provide these
Nodes that are to be locally
capabilities wvia the NICE protocol.
managed must provide the capabilities via NCP. Nodes that are to be
both remotely and locally controlled must provide these capabilities
via both NCP and the NICE protocol.

Each capability below is followed by the NICE
syntax that

implements 1t.

messages

and

the

NCP

Minimum Subset

Display

and

zero of

all

existing

Page B-2

counters.

The Data Link layer counters must exist on all multipoint control
nodes and on at least one end of each point-to-point link.

All DECnet nodes must
of

the Ethernet data
NICE

support
link

remote and local

counters via

read

capabilities

the NICE protocol.

messages:

Read information
counter

message,

circuit

counter

and

line

options.

Zero counters message, circuit and line options.

'NCP commands:

‘

SHOW CIRCUIT Cifcuit—id COUNTERS
SHOW LINE line-1id COUNTERS
ZERO CIRCUIT

ZERO

" The

Routing
NICE

LINE

layer

circuit—id COUNTERS

line-1id COUNTERS

counters must

exist

all

routing

nodes.

messages:

Read information message,
counters options.
Zero
counters message,
counters options.

circult
|
cilrcult

counters

and

node

NCP commands:

SHOW CIRCUIT circuit-id COUNTERS
SHOW NODE node-id COUNTERS
ZERO CIRCUIT
ZERO NODE

The
any

CirCUitfid

node-id

COUNTERS

End Communication layer counters must exist
palr
of
nodes that will communicate via

node
of
links and
that are more than one hop away from each
other.
Communicating
nodes that are only one hop away from each other are not required
- to support the End Communication Layer counters.
NICE

on
one
logical

messages:

Read

information message,

node

counters

option.

Page

Minimum Subset

B-3

Zero counters message, node counters option.
NCP

commands:

SHOW NODE

node-1id COUNTERS

ZERO NODE

node-1d COUNTERS

All other counters not mentioned above must

exist
1f
the
node
which the counters are defined.
For
provides
the
service
for
provide
example a node that provides an X.25 gateway server must
the corresponding counters.

Display and control of Routing events for all routing nodes.
logging
and
control
on non-routing nodes.

Display,

optional

sending

routing event messages

set

to be

any node

the

event
messages
are
routing
of
Routing nodes must be capable of
to at least a sink node, which can

network.

(Note:

routing node

The

sending the message is not required to serve as a sink node.) Any

network

incorporating

that may serve
NICE

sink

routing nodes must
for

least one node

messages:

logging

clear
Change parameter message, set
and
parameters for FILE, CONSOLE or MONITOR.

all

Read information message,

option

sink node qualifier.

NCP

have at

events,

logging summary

with

commands:

SET

LOGGING

sink-type

EVENTS

event-list

[source-qualifier]
[sink-node]

NAME sink-name
STATE sink-state

CLEAR LOGGING

sink-type

EVENTS

event-list

[source-qualifier]

[sink-node]

NAME

SHOW LOGGING sink-type

SUMMARY

[sink-node]

Test communication using the node level logical link loop test.

Note that this
-

implies that

all nodes must

implement

Mirror.
NICE

the Loopback
|

messages:

Test message,

node

level

loop test option.

Minimum Subset

- Change parameter message,
circuit and name

Page B-4

set and clear node option,

parameters.

Read
NCP

information message,

node summary option.

commands:

SET NODE node-1id

NAME node-name
CIRCUIT circuit-1d

CLEAR NODE

NAME

node-1id

CIRCUIT

SHOW NODE node-1id

SUMMARY

LOOP NODE node-id [access-control]

Disable a point-to-point communications
to

[WITH block-type]

[COUNT count]
[LENGTH length]

link by setting

1ts state

OFF.
NICE

NCP

messages:

Change parameter message,

set - circult

parameter,

commands:

off

value.

option,

state

SET CIRCUIT circuit—-1d STATE OFF
5.

Disable

a node by setting

NICE messagesfi
Change

parameter

parameter,
NCP

Display minimal
link

off

message,

value.

set

option;

state

node-1d STATE OFF

information about a point-to-point communications

node.

NICE

messages:

Read

information

message,

circuit

options.
NCP

node

commands:

SET NODE

1ts state
to OFF.

commands:

SHOW CIRCUIT circulit-i14d SUMMARY

and

node

summary

- Page B-5

Minimum Subset

SHOW NODE node-1id SUMMARY

From NCP, send command to remotely ‘managed

from

nodes

central

Note that any product that could be a central
management nodes.
management node must be able to parse all possible NCP commands
This must be true even though
and format all possible responses.
the product does not itself implement the particular options.
NCP

commands:

TELL node-id [access-control] command
'SET EXECUTOR NODE node-id [access-control]

CLEAR EXECUTOR NODE

8.
~

Display and control minimal ‘multipoint

control

lines running protocol type DDCMP control.

parameters for

NICE messages:

Change parameter message, set line option,‘ dead

timer

and delay timer parameters.

Read information message, line summary option.
NCP

commands:

SET LINE line-id DEAD TIMER milliseconds

DELAY TIMER milliseconds

SHOW LINE

line-1d SUMMARY

It is the responsibility of Product Management to set the product
requirements so that the applicability of the minimum subset can be
|

determined.

It 1s the responsibility of Development to build products that can

configured to minimum subset requirements.

It is the responsibility of Software Services or the user to configure
nodes so that the requirements are met for the network. This has to
be done while taking into account the specific characteristics of the
node and network

involved.

APPENDIX

STATE

MAPPING

TABLES

following
relate
tables
the
Network
controllable/observable
states
to the Network Management
and to the states from the actual spec1f1catlons for
the
users and data link protocols.

The

The
The
the

high level circuit users are Routing and
high level line users are point-to-point
X.25 protocol handler.

Management

llnk

states
level

the X.25 Gateway
Server.,
and multi-point DDCMP and

Mapping

Net.

Number

State

Substate

State

CLEARED

N/A

off

OFF

N/A

off

running

passive

run

STARTING

passive

start

run

synchronizing

passive

start

synch

FAILED

passive

fail

REFLECTING

refl

start

malnt

pass-open

off

maint

DUMPING

pass-open

off

maint

LOOPING

pass-open

off

maint

TRIGGERING

pass-open

off

maint

AUTOSERVICE

closed

off

maint

REFLECTING

clos-refl

off

maint

Man.

Net.

Man.

D.L.

Serv.

High

Lev.

Page C-2

State Mapping Tables
14

AUTOLOADING

open

off

maint

AUTODUMP ING

open

off

maint

AUTOTRIGGERING

open

off

maint

idle

closed

off

maint

| SERVICE

SERVICE

REFLECTING

clos-refl

Of f

maint

SERVICE

open

off

maint

SERVICE

DUMPING

open

off

maint

SERVICE

TRIGGERING

open

of f

maint

SERVICE

LOOPING

openv

off

maint

The following tables relate the internal states from each

component's

own specification to the Network Management states.
is indicated through the

preceding

mapping

numbers

which

the

circuit

This relationship
to

the

owner

correspond

table.

The following mappings

apply

when

user

EXECUTOR.

Perm Cir.

Inc. Cir.

Out. Cir.

X.25 P.L.

unaloc
unun

listening
clearing

open
clearing

cleared

Mapp1ing

Rout1ing

DDCMP

1-2

OP
HA

halt

run

running

run

running

Number

State

TI
TV
TC

halt

astrt

istrt

synch

unsynch
no—-Ccom

synch

unsynch

called
taken

no-com
listening

no-com
calling

N/A

‘N/A

listening

open

7-22

maint

N/A

State Mapping Tables

Page C-3

8-9

N/A

halt

11-12

N/A

halt

14-16

N/A

17-18

halt

19-21

N/A

22 |

halt

The

maint

following table applies when the

line

belongs

the

X.25

protocol

Mapping

Low Level

- 1-2

halted
disconnecting

Number

Link

5
~

State

unun

trans.

running

connecting

unsynch

re-synch

synch

loopback

unsync

inf.

18-21

State

running

N/A

Low Level

Port

inf. trans.

6-9

11-16

line protocol

handler

unsynch

N/A
loopback

~unload

N/A
loopback
=~

running

module.

1is

LAPB

and

the

APPENDIX D

X.25 NATIVE
ONLY SUBSET

In the case of a system that only provides native

many

Network

Management

functions

not

mode

apply.

X.25 usage,

These

are the

functions that relate to a node that is part of a DECnet network.. The
functions
that do apply should still be available through NCP but are
not

subject

The

following functions apply to an X.25 native only system.

any architectural minimum subset.

For the circult entity, the following parameters:
CHANNEL

)

CONNECTED

OBJECT
COUNTER TIMER
DTE

MAX IMUM

BLOCK

MAXIMUM WINDOW
STATE

Substate

USER.

The X.25 permanent virtual circuilt counters.

For the

line entity,

the

CLOCK

CONTROLLER

COUNTER

TIMER

DEVICE
HOLDBACK

TIMER

MAXIMUM

DATA

MAXIMUM

RETRANSMITS

MAXIMUM WINDOW
RETRANSMIT

SERVICE

TIMER

”

STATE

Substate

The LAPB line

counters.

following parameters.

"X;25°Native Only Subset

“ ”. -

Page D-2

M_Thé1follow1ng-Data Link events.

Locally initiated
state change

‘Remotely initiated state

change

For the logging entity, all parameters éxcept SINK NODE.

AAAAAA

vFQrmodulé-X25¥ACCESS,»the“NETWORK parametef.
For

’modulé"X2S—PROTOCOL;7 all parameters,

counters,

and

- events.

eters
all param
and
ers,
module X25-SERVER, all count
|
For
o
except the"following. ”
ACCOUNT
NODE

PASSWORD

USER

10,

- The following»NCP‘commands, supporting
the
entities and parameters.
CLEAR

DEFINE
PURGE

LIST
LOOP

LINE

SET

“

SHOW
ZERO

above

mentioned

APPENDIX

MEMORY

IMAGE FORMATS AND FILE CONTENTS

or 'DECSYSTEM-20
Since the PDP-8, PDP-11, VAX-11], and DECsystem-10,
memory addressing requirements differ, different formats are required
to know the
1s essential
In each case, 1t
for memory image data.
number of ‘bytes that represent-the smallest individually addressable
|
memory location. A format summary 1S prov1ded below.
Each three bytes represents two 12-bit words that
the memory address is incremented by two for
is,

PDP-8
|

each three bytes. Byte 1

1.
memory word
1

words

PDP-11

VAX-11

and

Byte 2

is the

8-bits

1low

That'is,

Each byte.represents‘one memory byte.

the memory address is incremented with each byte.

Eachfifivebytes repreSents one 36-bit word.

DECsystem-10
DECSYSTEM-20

low 8-bits of memory

That

is, the memory address” is incremented by

one for

4-bits of byte 5 are discarded.

Byte 1 1s the ‘highest 8-bits of
five bytes.
~each
high
The
follow.
4
Bytes 2 through
the word.

The files containing memory images for a down-line load or an up-line
dump have the same contents. The format may vary from one operatlng
1n all
system to another, but the contents are functlonally the same
cases.

The minimum control information required 1s as follows:
L}

The

type

of the

target

system

DECsystem-10, or DECSYSTEM-20).

(PDP-8,

VAX-ll,

PDP-11, -

This 1s necessary to know how

to interpret and update memory address information.

Transfer

program.

address.

This

the

startup

address

for

the

This field is generally meaningless for a dump file.

The image information required is as follows:
goes

Memory address. This is the address where image
load or comes

from a dump.

Block length.

Number of memory units in image block.

for

Memory Image Formats and File Contents
O

Page E-2

Memory
1mage.
This
1s
the
contiguous
block
associated
with
the
above address.
The format
are as specified in Appendix B.
The memory image
any length.

of
MEemory
requirements
can be
of
|

APPENDIX

e
iy
e
e

'NICE RETURN CODES WITH EXPLANATIONS
RSN

This appendix specifies the NICE return codes."

s, specified is for the firSt:byte of the return
the number
In all case

codes 1s two Dbytes
The error detaill that"Sometimes'fbllows the return
e implementing the error
long.

some systems

Since

may

have troubl

details, a value of 65,535 (all 16 bits set) in the error detail fieldl

‘means no error detail.

~will be printed.

message

a response
If
‘existing

fields may

in this case, no error deta1i
In other words,

is short

terminatéd, after any fie1d,'.the

still Dbe interpreted according’to'the standard

format.

rd text for the first
A printed error message consists of the standa
have'a defined value, this 1s

"If the second and third bytes
s) the values.
a blank, and the keyword(for
a comma,
~followed by
‘byte,

Standard teSt

vNumber_
1

(none)_

(none)

' Meaning
~ Success.

d are
nses
te
respo
ra
data
and sepa
S

coming.-

(none)

been; accepted;

The'réquest'has
Success,

partial reply.

parameters for entity 1n next
message. Can only be embedded
Each
a more/done sequence.
in
up
ds
fiel
ins
message still conta
to and including ENTITY ID.

-1

Unrecognized funCtion or
option

Either

the

function code

a
field = requested
option
the
by
nized
recog
capability not
Management
Network
Local

Also, the error code
Function.
(Phase
for function codes 2-14

NICE Return Codes With Explanations

| Page F-2
II),

- and

commands

matches

-2

Invalid message format

the
system
type
the rece1v1ng system

Message too long

(i.e.,
data),

or too

for

data

expected

. The requester does not have the

‘vPrivilegeviolation.'

privilege

required

perform

~ the requested function.
-4

Oversized Management
-

command

message

size

too

long

‘Management

»Management program error
-

for

Listener

too long

the Network

to receive.

A software error occurred

in the

could

fail.

Network
Management
software.
For
example,
a
function
that

not

Generally

- -6 _*

was

The NICE message for the command g

message

~was

-5

short

extra data
or not enough
or a
field
improperly

_formatted

-3

for system- specific

when

fail

did

1indicates
a

Management software bug.

Unrecognized parameter:type

A parameter
for

example,

Network

type included

in,

recognized

the

change parameter

message

not

Network

Management

Function.

The'error'detail-is,the low
-

| -7
|

Incompatlble Management

The

functlon

~performed

_ver31on

- Management
-

the

requested

because

Invalid identification

The

(component)

contalns

'format'

example,
-

where

node.

the

too
*

type

entltyd-

1nvalid.

a node - name

character,

not
‘

of
was

was

The error

entlty

1dent1f1catlon

alpha

- the

the

“flnumber*

-9

between

and

~ An entity
Hdetall

skew

source

destlnatlon

great.

known

cannot be

the Network

Version

command

- —8-d* Unrecognized;component*

and

high bytes of the parameter type
number,1interpreted accordlng to
the entlty involved.

not
allowed.
detail
contalns the
number.*

with

For

KNOWN‘usedf
- The "error

entlty

type

"’fPaée'Ff3 7'

NICE Return Codes With Explanations

Error in transmlt or recelve - on
Can only occur during.
line.
dlrected useof thesfiData L1nk

’,user

-11

COmponent inewrong state

1nterface.

An entlty (component) was in an

unacceptable = state. ~ For .
example, a down line = load
attempted over a line that is

used

'~OFF or a node. name to be

for a loop node already assigned

The error
f“to a node address.
detail - contains the entlty type‘
.

Anumber *x -

File open error

A flle could not be'opened

The error detall 1s deflned as *
e

follows'”'

'_Value*- Keywofds"u“
' PERMANENT DATABASE -

O
W

)

-10 " LLine communication error

QO U

d
contents
fileli
14 Inva

LOAD FILE

DUMP FILE

SECONDARY LOADER
~ TERTIARY LOADER
~ SECONDARY DUMPER

- VOLATILE DATABASE o
- DIAGNOSTIC FILE

o
The data in a file was‘winValid
as

The error

detall is deflned

for error # 13

-15

Resource error

- Some resource was not avallable
- For example, an operating system_{w
wresource not’ ava1lable

16 Invalid parametervalne

‘Improper

type, load

llne 1dent1f1catlon’
address,

memory

type
according

number,
to the

length, etc. ‘The error detall
1is the low and high bytes of the

parameter
interpreted

entity 1nvolved

-17 Line protocol error

Inva11d 11ne protocol message or

occur
only
Can
operatlon.
In
s.
acces
‘during direct line -

the case of a line loop test, it
was
- indicates that an error
detected

- during

message

comparison. that should have been
caught by the llne protocol

NiCEiRetnrn Codes With Explanations
—18.'anile I/0 error

.'[:_

I/0 error in a
read

error

Page F-4

file,

such as

system

1mage

loader during down line load

' The error detail is
for

7—19-'

]Mifrorslink disconnected

error

deflned

#-13.

das

A successful connect was made to

the

Loopback

logical

Mirror,

link

then

but

failed.

the

The error detail is:

Value

Standard text

Invalid node name

format

-2

Unrecognized node
name
I

|
3
4
5

Invalid object
format

-8

Access

object
Remote node

Node or object
failed
|
Disconnect - by ob]ect
Abort by object

Abort

.16‘_

Mirror
-

connect

failed

A
-

table

Parameter
|

not

applicable
.
|

the

same

not
For

could

error

set

for

error

'
applicable

example,

tributary
address
~ point-to-point
line
loopback

Network

The

entity.

attempt

new

Mirror

completed.

‘Parameter
-

for

the

Loopback

#-19.
=22

space

connect

detail

shut down

Management

~not

by Management

Local node

Insufficient
entry.

shut

down

-21

control

rejected

too busy
No- response from

new entry

.. Object

No room for

name

Unrecognized ObjeCt.~'

-20

name set

Node unreachable
Network resources
Rejected by object.

6
|

node

setting

for
or

a
an

a controller to
~mode
when
the

NICE Return Codes With Explanations.

Page

F-5

controller
does not support that
function.

contains
the

Parameter value too ldng_

=23

=~ The

parameter

A parameter

value

was

low

and

-25

Operation

failure

requested.

~ Invalid parameter groupi

code.

error

May

further

a system-specific

message.

The

request

for

changing

multiple parameters contained
- some that cannot be changed with

Bad lobpback response

A‘loopback message did not match
what

was

content

Parameter

others.

‘A

missing

required

included.

expected,

either

length.

parameter

The

‘parameter

type

interpreted according
entity involved.

:(none)-

was

not

the

error detail

‘3the low and high bytes

-128

the

not perform
the

Error return for system-specific
functions unless the system type
i1s for the system receiving the

not supported

=29

number,
to
the

associated with

function

explained

—-28

could

command.

=27

long

A requested operation failed,
and
there 1s no more specific

,System—specific'Management'
function

too

the
the

request

error

=26

not

error detail 1s
high
bytes
of

,nThe hardware

failure

type
~
according
1involved.

entity

detail

type

implementation

parameter
lnterpreted

Hardware

that

applicable.

for
the
handle.
The

-24

error

the parameter

number,

to
the
R
|

e with
printed. Don
No message response
~ ‘multiple
= commands
;", gt

(e.g.,

read

known lines).

information
o

*NOTE

Error codes fS, -9, and -11 indicate problems,With the
primary
entity
to which a command applies.
also apply to a secondary entity, such as the

They may
line
1in

for

- NICE Return Codes With Explanatiohs;,;
a LOAD NODE command.

e S "f“Page F-6

APPENDIX G

'NCP COMMAND STATUS AND ERROR MESSAGES

NCP

has the follOW1ng

standard status and

error

'Standard Text

messages

Mean1ng

Status Messages .

COMPLETE
- FAILED

~ The command was processed successfully.

The

command

successfully.

' NOT ACCEPTED

~did

‘semantic

checking.

to’execute it.

Error

~ Unrecognized keyword

Value out of range

' Unrecognized‘ value

The

~ Bad management response

AListener'link:disconnected

and"

No attempt
was made

text

long

the

error

the meanlng

Messages

The command typed by the
recognlzed

nser‘lWaS"not
-

Somethlng in the command keyword was not»
recognlzed

A parameter

value was

out of range.

a blank

the parameter keyword(s)

This message may be followed by a comma,
and

A parameter

value was unrecognlzable.

This message may be followed by

’a blank

~ Not remotely executable'

execute

~The command did not get past‘syntax
~ message may. vary as
1s clearly the same.

Unrecognized command

not

and

a comma,

the parameter keyword(s)

NCP is funct1onally
unable: to send
S
h
command to a remote node.

' The Network Management

‘Access

fRoutlnes

. received unrecognlzable_1nformation,;g

| Aisuccessful_conneCt - was

made

the

NCP Command Status and Errer Messages

Network Management
1link then
logical
1s

error detail

A connect

to the

in NICE error message.

Network Management

be completed.
could not
Listener
as _in
optional error detail 1s
error message -21 (Appendlx F).

The
NICE

maximum
overflows.
.command
message for this implementation.

= NICE

‘Total parameter data too long NCP

‘Oversized Management response

but the
Optional

Listener,
failed.

-19 (Appendlx F)

Listener connect failed

Page G-2

NCP could not

it was
because

receive

too long.

NICE message
|

"APPENDIX

JULIAN

HALF-DAY

ALGORITHMS

The follOwing algorithms will convert to and from a Julian half-day in
the range

format of

January

event

1977

logging

through

records.

November

2021

as used

the

binary

The algorithms will operate correctly with
16
bit
arithmetic.
The
arithmetic
expressions are
to
be
evaluated using FORTRAN operator
precedence and integer arithmetic.
In all cases, the input is assumed to be correct, i.e., the day is
1n
the
range 1l to maximum for the month, the month is in the range 1-12,
the year 1s 1n the range 1977 2021 and the Julian half-day 1s
1in
the
range

0-32767.

convert

to Julian

JULIAN =

convert

half-day:

(3055*(MONTH+2)/100-(MONTH+10)/13*2-91

+(1-(YEAR-YEAR/4*4+3)/4)*(MONTH+10)/13+DAY-1
+(YEAR-1977)*365+(YEAR-1977)/4)
*2

from Julian

half-day:

HALF = JULIAN/2
TEMP1 = HALF/1461
TEMP2 = HALF-TEMP1
YEAR = TEMP2/365

IF TEMP2/1460*1460

= TEMP2

YEAR

ENDIF

TEMP1

YEAR-1

TEMP2-(YEAR*365)+1

YEAR = YEAR+1977
IF YEAR/4*4 = YEAR
TEMP2

ELSE

TEMP2
ENDIF

TEMP1 > 59+TEMP2
= DAY+2-TEMP?2

DAY
ELSE

DAY
ENDIF-

TEMP1

AND

(HALF+1)/1460

> TEMP1

Page H-2

Julian Half-day Algorithms

MONTH = (DAY+91)*100/3055
DAY = DAY+91-MONTH*3055/100
|
MONTH = MONTH-2
IF

HALF*2 =
HALF = 0

JULIAN

ELSE
HALF

ENDIF

The algorithm was
program

running

certified

in 'FORTRAN

INTEGER*4
INTEGER*2

IV+

work

wusing

on RSX-11M:

the

following

FORTRAN

COUNT
JULTES,JULIAN, DAY MONTH, YEAR, JULTEM HALF

DO 1099 COUNT=0,32767
JULTES=COUNT

CALL UNJUL(JULTES, HALF, DAY ,MONTH, YEAR)

JULTEM=JULIAN(DAY, MONTH YEAR) +HALF
IF

TYPE

GOTO 1099

(x,

)

'Error" 617)

CONTINUE
-

10,JULTES,JULTEM, HALF,DAY ,MONTH, YEAR

FORMAT

1099

(JULTEM.EQ. JULTES)

END

INTEGER FUNCTION TO CONVERT DAY,

MONTH AND YEAR TO JULIAN HALF-DAY

INTEGER*2 FUNCTION JULIAN(DAY MONTH YEAR)
INTEGER*2

&
&

DAY ,MONTH, YEAR

JULIAN = (3055*(MONTH+2)/100—(MONTH+1O)/13*2—91
+(1-(YEAR- YEAR/4*4+3)/4)*(MONTH+1O)/13+DAY—1
+(YEAR-1977)*365+(YEAR- 1977)/4)
RETURN
END

! SUBROUTINE TO CONVERT JULIAN HALF-DAY TO DAY, MONTH AND YEAR

SUBROUTINE UNJUL(JULIAN,HALF,DAY,MONTH,
YEAR)
INTEGER*2

JULIAN,HALF,DAY,MONTH,
YEAR, TEMP1, TEMP?

HALF = JULIAN/2
TEMPl = HALF/1461
TEMP2 = HALF-TEMP1
YEAR-=
TEMP2/365
&

IF (TEMP2/1460*1460}EQ TEMP2.AND. (HALF+1)/146O GT. TEMPl)

YEAR

TEMP1

YEAR-1

= TEMP2-(YEAR*365)+1

YEAR=YEAR+1977
TEMP2 = 0
|

IF
DAY

(YEAR/4*4, EQ YEAR)
=

TEMPl1

TEMP2 =
|

1
-

IF (TEMPl.GT.59+TEMP2) DAY = DAY+2-TEMP2
MONTH = (DAY+91)*100/3055
DAY = DAY+91-MONTH*3055/100

Julian Half-day Algoritfims

MONTH = MONTH-2
TEMP1

(HALF*2.NE.JULIAN)

= 0

TEMP1l

'HALF = TEMP1
RETURN
END

‘

-Page:H—3

APPENDIX I
DMC DEVICE COUNTERS

‘The following counters are the only ones applicable to the DMC device.

Number Standard Text
1000
1001
1010
1011
1020

1021

1030
1031
1041

Bytes received
Bytes sent
|
Data blocks received
Data blocks sentData errors inbound
.
|
0
NAKs sent, header block check error
1
NAKs sent, data field block check error
Data ‘errors outbound
|
|
Remote reply timeouts
Local reply timeouts
Local buffer errors
0
NAKs sent, buffer unavailable

None of the other standard counters can be kept due to the
the
DMC hardware.
The "Data errors outbound" counter
bitmap.
It represents the sum of all NAKs received.

nature
kept

with no
)

Since the counters kept by the DMC firmware cannot be
zeroed
1in
the
way
that
driver-kept
counters
can,
the
recommended technique for
providing
the zero capability is to copy the base table counters
when
a zero 1s requested.
The numbers returned when counters are requested
are then the difference between the saved
counters
and
the
current
base

table.

APPENDIX

- GLOSSARY

NOTE
Terms that
derive
from
other
related
specifications
(such
as
hops,
cost,
delay,
etc.)
are
defined
in
those
specifications.

active

areas

Active areas
active

are known areas which are currently reachable.

circults

Active circuits are known circuits
active

1n the ON or SERVICE state.

lines

Active

lines

are

known

lines

the ON or SERVICE

state.

active logging

Activevlogging describes all known sink types that are in the
or

active

HOLD

state.

nodes

'All reachable nodes as
active nodes.

adjacent

perceived

(See Section 3.1)

from

the

executor

node

are

node

A node removed from the executor node by a single physical line.
characteristics

Parameters that are generally static values

in volatile memory or

GLOSSARY

permanent

Page J-2

values 1n a permanent data base.

information

type.

Characteristics

can

A Network Management.

set

defined.

circuilt

logical

communications

path

providing

communications

connection between adjacent nodes.
A circuit may be identical to
a physical link, multiplexed with
many
other
circuits,
and/or
traffic split over multiple physical links.
(See Section 3.4)

circult

level

loopback

Testing a specific
data
1link
<circuit
by
sending
message
directly
to
the
data
1link layer and over
device that returns the message to the source.
cleared

a
a

repeated
wire to a

state

Applied to a line:
bases,
command

but

none

a state where space is reserved for line data

of them

1is

present.

node

The node where

an NCP command originates.

controller

The part of a device

identification

hardware
for
a line.
responsible for one Oor

For
more

that

a multiline
units.

denotes

device

that

the

control

controller

counters

Error

and

information

performance

statistics.

Network

Management

type.

entity
- AREA,

CIRCUIT,

LINE,

LOGGING,

MODULE

NODE.

These

are

the

major
Network Management keywords.
Each one has parameters with
options, and most have specified counters.
There are also plural
entities,
such
as,
KNOWN
LINES,
ACTIVE
LOGGING, SIGNIFICANT
NODES,

etc.

executor

node

The

node

which

the

active

Local

Network

Management

Function

running
(that
1is, the node actually executing the command);
active network node physically connected to one end of a line
circuit being used for a load, dump, or line loop test.

the
or

filter
A

set

each

flags

event

type

for

1in

event

that

class

that

indicates

recorded.

whether

not

global

Page J-3

GLOSSARY
filter

A filter that applies to all entities within an event class.
hold

state

sink

The node that provides services for another

node

unavailable and events for

host

where

state

temporarily

1is

the

Applied to logging.

it should be queued.

node

during a down-line task load).
information

(for

example,

SUMMARY.

type

COUNTERS,

One of CHARACTERISTICS,

STATUS

EVENTS,

Used in the SHOW command to control the type of information
Each entity parameter and counter 1s associated with
returned.
one or more

known

information types.

circuits

All circuits addressable by Network Management in the appropriate
They may
data base (volatile or permanent) on the executor node.
not

known

all

a usable

state.

lines

in the appropriate
All lines addressable by Network Management
node. They may
executor
the
on
permanent)
or
(volatile
data base
not

known

all

a usable

state.

logging

All logging sink-types addressable by Network Management

the

appropriate data base.

known

nodes

All nodes with address 1
reachable

circuit

have a

node

maximum

name

address

that

Network

plus

are

eilther

all names that map to a

line.

line

A physical communications path.

Line

1is

Management

entity.

line

level

loopback

Testing a specific physical link by sending

‘directly

repeated message

the physical link layer and over a wire to a device

that returns the message

to the source.

GLOSSARY

Page J-4

logging

Recording information

from

occurrence that

has

potential

significance
1in
the operation and/or maintenance of the network
in a potentially permanent form
where
it
can
be
accessed
by

persons
and/or
programs
long-term decisions.

logging

tod

aid

them

1in

making

real-time

record

console

A logging sink that is
events, for example, a

logging

event

receive
terminal or

a
human-readable
printer.

type

The 1dentification of a particular type of event,
restarted

node

down.

such

1line

logging file
A

logging

events

logging

sink

for

that

later

receive

or monitor).

sink

set
which

logging
The

logging

record

logging entity

(file,
|

console

sink

A place

logging

machine-readable

1dentification

The sink type associated with the

logging

retrieval.

that

copy

event

recorded.

flags

the

sink

1in

event

record
recorded.

that

indicate

the

sinks

node

source

from

which

logging

information

comes.

process

The process that recdgnized an event.

logical link

A connection between two nodes that is established and
by the Session Control, End Communication, and Routing
loopback

controlled
layers.

node

A special

name

loop
testing
loopback node

for

a node,

purposes.
name.

that

The

SET

associated
NODE

LINE

with a
command

1line
sets

for
the

GLOSSARY

Page J-5

1into

other

module

A module is a component that
classifications.

does

not

fit

entity

monitor

a machine-readable
An event sink that is to receive
events for possible real-time decision making.

record

node

that supports Routing, End
An implementation
Session Control.

node

and

Communication,

Node is a Network Management entity.

address

The required unique numeric identification of a specific node.
node

identification

Either a node name or a node address.

must be used as a node identification.
be used as a node identification.
node

In some cases

address

In some cases a name must

name

node
An optional alphanumeric identification associated with a
more
used
be
may
name
No
mapping.
address in a strict one-to-one
one
least
at
contain
The node name must
than once in a node.
node level

letter.

loopback

flow with
Testing a logical link using repeated messages that
End
Control,
Session
the
through
traffic
data
normal
one
from
or
node
one
within
layers
Communication, and Routing
loopback
level
node
cases
some
In
Dback.
and
another
to
node
involves using a loopback node name associated with a particular
off

state

Applied to a node:
network traffic.

a state
Applied

process
longer
no
will
it
where
a state where
to a line or circuit:

the line is unavailable for any

" logging:
for

line.

kind

traffic.

a state where the sink is not available,

Applied

and any events

should be discarded.

state

Applied
a state of normal network operation.
Applied to a node:
usage.
normal
for
availability
of
state
a
to a line or circuit:
for
available
1is
sink
a
where
state
a
logging:
Applied to
receiving

events.

GLOSSARY

Page J-6

processed event
An
raw

event

after

local

processing,

final

form.

event

An
of

event

total

information

reachable

recorded

the

source

process,

incomplete

terms

node

A node to which the executor node's Routing
usable

remote

required.

communications

believes

path.

has

node

one

restricted

node,

any

other

network

node.

state

A node state where no new'logical

links

from

allowed.

service

other

nodes

are

password

The password required to permit triggering of a node's
ROM.

bootstrap

service slave mode
The

mode where the processor is
taken
over
and
the
adjacent,
executor
node
1s
1n
control,
typically
for
execution
of a
bootstrap program for down-line loading or for up-line dumping.

service

state

A line or circuit state where such operations as down-line
up-line
dump, or line loopback are performed.
This state
direct access by Network Management to the line,
shut

1load,
allows
|

state
A

state where existing logical links or X.25
undisturbed, but new ones are prevented.

wvirtual

calls

are

least

one

significant

A subset of known entities
parameter

counter,

sink
(see
specific

logging sink)
filter

for

which

there

1is

GLOSSARY

A filter that
and type.

applies

specific

Page J-7

entity within

event
|

class
|

station

A physical termination on a line,
saftware

having

both

hardware

and

implementation.

status

Dynamic

information

Network
whether

Management information type.
Also,
or not an NCP command succeeded.

relating

entities,

such as

their

a message

state.

indicating

substate

An intermediate
display.

state

that

displayed

tag

state

down-line

load,

SUmMmMary
An
target

information

type

meaning

most

useful

information.

node

The node
generates

that

receives

an up-line

a memory

dump,

image during

loops

back

test message.

tributary

A station on a multipoint line that 1is not a control station.

DECnet Digital Network Architecture Phase IV
Network Management Functional Specification

AA-X437A-TK

READER’S COMMENTS

) B

NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company’s discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.
|

- Did »you' find this manual unders'tandable, usable, and well-organized? Please make suggestions for improvement.

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

- Please indicate the type of user/reader that you most nearly represent.

Assembly language progrzimmer

Higher-level language programmer

Occasional programmer (experienced)

User with little programming experience

Student programmer

‘0O

Other (please specify)

Name

Date

Orgénization
Street

City.

)
e

|
-

State

Zip Code

or
Country

== —— = —-DoNotTear-I*‘oldHerean.dTapef- —_——
e
— — — — — —

No Postage

Necessary

if Mailed in the

United States

BUSINESS REPLY MAIL
.

FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

{

1925 ANDOVER STREET TW/EOQ7

SOFTWARE DOCUMENTATION
|

TEWKSBURY, MASSACHUSETTS 01876

Do Not Tear - Fold Here and Tape

— — —

—

___ __

— — — —

Cut Along Dotted Line

Printed in U.S.A.