DECnet forOpenVMSNetwork

DECnet for OpenVMSNetwork
Management Utilities
Order Number: AAPV61ATK
May 1993
Thi s document contai ns i nformati on about commands for the Network
Control Program (NCP) and for the DTS/DTR uti l i ty. Thi s document i s
for users responsi bl e for DECnet for OpenVMS network management.
Revision/Update Information: Thi s i s a new manual .
Software Version: OpenVMS AXP Versi on 1.5
OpenVMS VAX Versi on 6.0
Digital Equipment Corporation
Maynard, Massachusetts
May 1993
The i nformati on i n thi s document i s subject to change wi thout noti ce and shoul d not be construed
as a commi tment by Di gi tal Equi pment Corporati on. Di gi tal Equi pment Corporati on assumes no
responsi bi l i ty for any errors that may appear i n thi s document.
The software descri bed i n thi s document i s furni shed under a l i cense and may be used or copi ed
onl y i n accordance wi th the terms of such l i cense.
No responsi bi l i ty i s assumed for the use or rel i abi l i ty of software on equi pment that i s not suppl i ed
by Di gi tal Equi pment Corporati on or i ts afl i ated compani es.
Di gi tal Equi pment Corporati on 1993.
Al l Ri ghts Reserved.
The postpai d Reader s Comments forms at the end of thi s document request your cri ti cal eval uati on
to assi st i n prepari ng future documentati on.
The fol l owi ng are trademarks of Di gi tal Equi pment Corporati on: AXP, Bookreader, CI , DDCMP,
DEC, DECnet, DECnet RSX, DELUA, DEQNA, DEUNA, Di gi tal , DECdns, OpenVMS, VAX, VAX
P.S.I ., VMS, VMScl uster, VMS RMS, and the Di gi tal l ogo.
The fol l owi ng i s a thi rd-party trademark:
Tel enet i s a regi stered trademark of GTE Tel enet Communi cati on Corporati on.
Al l other trademarks and regi stered trademarks are the property of thei r respecti ve hol ders.
Thi s document was prepared usi ng VAX DOCUMENT, Versi on 2.1.
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Part I The Network Control Program Utility
1 Description
1.1 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Enteri ng Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3 Command Prompti ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.1 Exi ti ng the Prompti ng Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.2 Prompti ng Exampl es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 Component and Parameter Syntax Rul es . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5 NCP HELP Faci l i ty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
2 Using NCP
2.1 Hi nts for Usi ng Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3 NCP Commands
CLEAR/PURGE CI RCUI T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
CLEAR/PURGE EXECUTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CLEAR EXECUTOR NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
CLEAR/PURGE LI NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
CLEAR/PURGE LOGGI NG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
CLEAR/PURGE LOGGI NG EVENTS . . . . . . . . . . . . . . . . . . . . . . . . . 317
CLEAR/PURGE LOGGI NG NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
CLEAR/PURGE MODULE CONFI GURATOR . . . . . . . . . . . . . . . . . . . 320
CLEAR/PURGE MODULE X25-ACCESS (Remote management
onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
CLEAR/PURGE MODULE X25-PROTOCOL (Remote management
onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
CLEAR/PURGE MODULE X25-SERVER/X29-SERVER (Remote
management onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
CLEAR/PURGE NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
CLEAR/PURGE NODE CI RCUI T . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
CLEAR/PURGE OBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
CONNECT NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
CONNECT VI A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
COPY KNOWN NODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DI SCONNECT LI NK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
iii
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
LOAD NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
LOAD VI A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
LOOP CI RCUI T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
LOOP EXECUTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
LOOP LI NE (Remote management onl y) . . . . . . . . . . . . . . . . . . . . . . . 352
LOOP NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
SET CI RCUI T ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
SET/DEFI NE CI RCUI T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
SET EXECUTOR ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
SET/DEFI NE EXECUTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
SET EXECUTOR NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
SET KNOWN PROXI ES ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
SET LI NE ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
SET/DEFI NE LI NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
SET LOGGI NG ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
SET/DEFI NE LOGGI NG EVENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
SET/DEFI NE LOGGI NG STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
SET/DEFI NE MODULE CONFI GURATOR . . . . . . . . . . . . . . . . . . . . . 390
SET/DEFI NE MODULE X25-ACCESS (Remote management onl y). . . 392
SET/DEFI NE MODULE X25-PROTOCOL (Remote management
onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
SET/DEFI NE MODULE X25-SERVER/X29-SERVER (Remote
management onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3100
SET NODE ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3105
SET/DEFI NE NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3106
SET/DEFI NE NODE CI RCUI T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3111
SET OBJECT ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3112
SET/DEFI NE OBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3113
SHOW AREA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3118
SHOW/LI ST CI RCUI T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3120
SHOW/LI ST EXECUTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3125
SHOW/LI ST LI NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3128
SHOW LI NKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3131
SHOW/LI ST LOGGI NG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3133
SHOW/LI ST MODULE CONFI GURATOR . . . . . . . . . . . . . . . . . . . . . . 3136
SHOW/LI ST MODULE X25-ACCESS (Remote management onl y) . . . 3139
SHOW/LI ST MODULE X25-PROTOCOL (Remote management
onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3141
SHOW/LI ST MODULE X25-SERVER/X29-SERVER (Remote
management onl y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3145
SHOW/LI ST NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3147
SHOW/LI ST OBJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3152
TELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3154
TRI GGER NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3156
TRI GGER VI A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3158
ZERO CI RCUI TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3159
iv
ZERO EXECUTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3160
ZERO LI NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3161
ZERO MODULE X25-PROTOCOL (Remote management onl y) . . . . . . 3162
ZERO MODULE X25-SERVER (Remote management
onl y)/X29-SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3163
ZERO NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3164
Part II DECnet for OpenVMS DTS/DTR Utility
4 DECnet Test Sender/DECnet Test Receiver (DTS/DTR) Commands
4.1 DTS Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.2 DTS/DTR Usage Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3 DTS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
DI SCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
I NTERRUPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
A DECnet Circuit and Line Devices
B Network Counter Summary
B.1 Overvi ew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B1
B.2 Ci rcui t Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B4
B.3 Li ne Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B7
B.4 Node Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B11
B.5 X.25 Protocol Modul e DTE Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B13
B.6 X.25 and X.29 Server Modul e Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . B14
C States and Transitions
C.1 Overvi ew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C1
C.2 Ci rcui t and Li ne States and Transi ti ons . . . . . . . . . . . . . . . . . . . . . . . . . . C1
C.3 Li nk States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C5
C.4 DTE States and Transi ti ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C5
C.5 X.25 Server Modul e States and Transi ti ons . . . . . . . . . . . . . . . . . . . . . . . . C8
D Event Class and Type Summary
D.1 Network Management Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D2
D.2 Sessi on Control Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D4
D.3 End Communi cati ons Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D4
D.4 Routi ng Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D4
D.5 Data Li nk Layer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D9
D.6 X.25 Packet Level Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D11
D.7 System-Speci c Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D12
D.8 Di gi tal Di stri buted Name Servi ce (DECdns) Cl erk Events . . . . . . . . . . . . D12
v
Index
Tables
11 Command Syntax Exampl e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
12 NCP Syntax Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
21 Pri vi l eges for NCP Operati ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
31 Object Type Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116
A1 Ethernet Ci rcui t and Li ne Devi ces . . . . . . . . . . . . . . . . . . . . . . . . . . . . A1
A2 DDCMP and CI Ci rcui t and Li ne Devi ces . . . . . . . . . . . . . . . . . . . . . . A1
A3 X.25 Ci rcui t and Li ne Devi ces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A2
A4 FDDI Ci rcui t and Li ne Devi ces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A2
C1 Ci rcui t and Li ne States and Substates . . . . . . . . . . . . . . . . . . . . . . . . . C1
C2 Ci rcui t and Li ne State Transi ti ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . C2
C3 Li nk States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C5
C4 DTE States and Substates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C6
C5 DTE State Transi ti ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C6
C6 X.25 Server States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C8
C7 X.25 Server State Transi ti ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C8
vi
Preface
Intended Audience
The DECnet for OpenVMS Network Management Utilities i s a reference to the
formats and syntax of NCP and DTS/DTR commands. Thi s manual i s for users
al ready fami l i ar wi th DECnet for OpenVMS concepts. System managers can use
NCP to congure, control , moni tor, or test DECnet for OpenVMS software.
Document Structure
Thi s document consi sts of four chapters and one appendi x:
Chapter 1 provi des a ful l descri pti on of the NCP uti l i ty, i ncl u the fol l owi ng
topi cs:
Command syntax
Enteri ng commands
Command prompti ng
Component and parameter syntax rul es
NCP HELP
Chapter 2 outl i nes the fol l owi ng NCP i nformati on:
I nvoki ng the uti l i ty
Exi ti ng the uti l i ty
Di recti ng output
Restri cti ons or pri vi l eges for speci c operati ons
Chapter 3 descri bes NCP commands, i ncl udi ng format, paramete qual i ers,
and exampl es.
Chapter 4 provi des a descri pti on of the DTS/DTR uti l i ty
Appendi x A l i sts DECnet for OpenVMS ci rcui t and l i ne devi ces.
Appendi x B i ncl udes descri pti ons of ci rcui t, l i ne and node counters.
Appendi x C contai ns descri pti ons of ci rcui t, l i ne, and l i nk states, and thei r
substates and transi ti ons.Thi s secti on al so descri bes X25-SERVER modul e
and DTE states, substates, and thei r transi ti ons.
Appendi x D i ncl udes a summary of NCP events i n terms of thei r cl ass and
type.
vii
Associated Documents
Before usi ng NCP, you shoul d be fami l i ar wi th the basi c networki ng concepts
descri bed i n the DECnet for OpenVMS Guide to Networking. DECnet for
OpenVMS concepts and NCP usage i nformati on are presented i n the DECnet
for OpenVMS Networking Manual, whi ch al so descri bes the procedures needed
to congure, manage, test, and moni tor your network. Refer to that manual for
more i nformati on about any NCP command l i sted i n thi s manual .
The fol l owi ng functi onal speci cati ons dene Di gi tal Network Archi tecture (DNA)
Phase I V protocol s to whi ch al l i mpl ementati ons of DECnet Phase I V adhere:
DECnet Digital Network ArchitectureGeneral Description
Digital Data Communications MessageProtocol Functional Specication
Network Services Protocol Functional Specication
MaintenanceOperation Protocol Functional Specication
Data Access Protocol Functional Specication
Routing Layer Functional Specication
DNA Session Control Functional Specication
DNA PhaseI V Network Management Functional Specication
Ethernet NodeProduct ArchitectureSpecication
Ethernet Data Link Functional Specication
Conventions
I n thi s manual , every use of OpenVMS AXP means the OpenVMS AXP operati ng
system, every use of OpenVMS VAX means the OpenVMS VAX operati ng system,
and every use of OpenVMS means both the OpenVMS AXP operati ng system and
the OpenVMS VAX operati ng system.
The fol l owi ng conventi ons are used to i denti fy i nformati on speci c to OpenVMS
AXP or to OpenVMS VAX:
AXP
The AXP i con denotes the begi nni ng of i nformati on
speci c to OpenVMS AXP.
VAX
The VAX i con denotes the begi nni ng of i nformati on
speci c to OpenVMS VAX.
The di amond symbol denotes the end of a secti on of
i nformati on speci c to OpenVMS AXP or to OpenVMS
VAX.
The fol l owi ng conventi ons are al so used i n thi s manual :
Ctrl /x A sequence such as Ctrl /x i ndi cates that you must hol d down
the key l abel ed Ctrl whi l e you press another key or a poi nti ng
devi ce button.
viii
. . . A hori zontal el l i psi s i n exampl es i ndi cates one of the fol l owi ng
possi bi l i ti es:
Addi ti onal opti onal arguments i n a statement have been
omi tted.
The precedi ng i tem or i tems can be repeated one or more
ti mes.
Addi ti onal parameters, val ues, or other i nformati on can be
entered.
.
.
.
A verti cal el l i psi s i ndi cates the omi ssi on of i tems from a code
exampl e or command format; the i tems are omi tted because
they are not i mportant to the topi c bei ng di scussed.
[ ] I n format descri pti ons, brackets i ndi cate opti onal el ements.
You can choose one, none, or al l of the opti ons. (Brackets are
not opti onal , however, i n the syntax of a di rectory name i n
an OpenVMS l e speci cati on, or i n the syntax of a substri ng
speci cati on i n an assi gnment statement.)
{} I n format descri pti ons, braces surround a requi red choi ce of
opti ons; you must choose one of the opti ons l i sted.
boldface text Bol dface text i s used to show user i nput i n Bookreader versi ons
of the manual .
italic text I tal i c text emphasi zes i mportant i nformati on, i ndi cates
vari abl es, and i ndi cates compl ete ti tl es of manual s. I tal i c
text al so represents i nformati on that can vary i n system
messages (for exampl e, I nternal error number), command l i nes
(for exampl e, /PRODUCER=name), and command parameters
i n text.
UPPERCASE TEXT Uppercase text i ndi cates a command, the name of a routi ne,
the name of a l e, or the abbrevi ati on for a system pri vi l ege.
- A hyphen i n code exampl es i ndi cates that addi ti onal
arguments to the request are provi ded on the l i ne that fol l ows.
numbers Al l numbers i n text are assumed to be deci mal , unl ess
otherwi se noted. Nondeci mal radi xesbi nary, octal , or
hexadeci mal are expl i ci tl y i ndi cated.
Notes
I n thi s document, di scussi ons that refer to VMScl uster envi ronments
appl y to both VAXcl uster systems that i ncl ude onl y VAX nodes and
VMScl uster systems that i ncl ude at l east one AXP node unl ess i ndi cated
otherwi se.
I n thi s document, di scussi ons that refer to DECdns appl y to the
Di stri buted Name Servi ce (DNS) V1.1.
ix
Part I
The Network Control Program Utility
1
Description
The Network Control Program (NCP) i s the uti l i ty program used by system and
network managers to congure and control DECnet nodes. System managers can
al so use NCP to moni tor network resources and test network components. Thi s
manual presents the syntax of the NCP commands used to perform these tasks.
Consul t the DECnet for OpenVMS Networking Manual for detai l ed descri pti ons
expl ai ni ng the use of the NCP commands. After you read the appropri ate
secti ons of the DECnet for OpenVMS Networking Manual and know whi ch NCP
command (or seri es of commands) you need, use thi s manual for the syntax of the
commands.
The descri pti on of NCP covers the fol l owi ng topi cs:
Command syntax
Enteri ng commands
Command prompti ng
Component and parameter syntax rul es
NCP HELP Faci l i ty
The DECnet for OpenVMS Networking Manual al so contai ns an overvi ew of
networki ng concepts and descri pti ons of the components that make up the
network.
1.1 Command Syntax
To i nvoke NCP, type RUN SYS$SYSTEM:NCP at the DCL prompt. The NCP>
prompt i ndi cates that you are usi ng the NCP uti l i ty program. When you recei ve
thi s prompt, you can enter NCP commands.
11
Description
1.1 Command Syntax
The NCP command syntax has four parts: a command verb, a component, one or
more parameters and, opti onal l y, one or more qual i ers. Tabl e 11 i s an exampl e
of thi s syntax.
Table 11 Command Syntax Example
Command Verb Component Parameter Qualier
SHOW ACTI VE LI NES CHARACTERI STI CS TO l espec
KNOWN LI NES COUNTERS
LI NE l i ne-i d STATUS
SUMMARY
For each command, you must suppl y a command verb and a component. Some
commands al so requi re one or more parameters. Command qual i ers are
opti onal . Unl ess otherwi se i ndi cated, you can speci fy parameters i n any order.
1.2 Entering Commands
Enter NCP commands as verbs, components, parameters, and qual i ers separated
by spaces or tabs. To conti nue a l ong command to the next l i ne, use the standard
conti nuati on l i ne conventi on (a hyphen as the l ast character i n the l i ne). The
NCP>prompt i s not di spl ayed on conti nuati on l i nes; i nstead, conti nuati on l i nes
prompt wi th an underscore character. For exampl e:
NCP>SET EXECUTOR -
_ ADDRESS 11 -
_ INCOMING TIMER 30 -
_ STATE ON
NCP>
I n command l es, use an excl amati on poi nt (! ) to desi gnate a comment l i ne. NCP
i gnores hyphens wi thi n and at the end of a comment l i ne. However, NCP does
not i gnore l i nes begi nni ng wi th an excl amati on poi nt i f they fol l ow a command
l i ne endi ng wi th a hyphen.
When enteri ng an NCP command, you can truncate any command verb,
component name, parameter name, or qual i er name to i ts fewest uni que l etters.
For exampl e, the fol l owi ng two commands perform the same functi on:
NCP>SET EXECUTOR ADDRESS 11 STATE ON
NCP>SET EXE AD 11 STA ON
For cl ari ty, al l exampl es show the ful l command syntax.
Recalling Commands
You can recal l NCP commands that you previ ousl y entered by pressi ng Ctrl /B or
the arrow keys i n response to the NCP>prompt.
You can press Ctrl /B or the up-arrow key up to 20 ti mes to recal l the l ast 20
commands you have typed. After you recal l an NCP command, you can edi t i t
and then reenter i t. You can press the down-arrow key to recal l the next (most
recent) command i n the NCP command recal l buffer.
12
Description
Using Wildcard Characters to Enter Commands
You can use the asteri sk (*) and the percent si gn (%) as wi l dcard characters i n
an NCP command l i ne to represent NCP components by a general name, rather
than speci fy each component name i ndi vi dual l y.
You can use the wi l dcard characters to represent the fol l owi ng component names:
Node name
Node address
Ci rcui t name
Li ne name
Object name
Events
The asteri sk wi l dcard represents one or more characters, whi l e the percent si gn
represents a si ngl e character.
Rules for Using Wildcard Characters
The fol l owi ng rul es dene how you can use wi l dcard characters wi th component
names:
I f the component name i s a stri ng, the wi l dcard character may occur at any
l ocati on i n the stri ng. For exampl e:
NCP>LIST NODE ST%R STATUS
NCP>SHOW OBJECT M* CHARACTERISTICS
The rst command requests a l i st of status i nformati on for al l nodes wi th
four-l etter node names begi nni ng wi th ST and endi ng wi th R. The second
command requests a l i sti ng of characteri sti cs for al l objects wi th names
begi nni ng wi th M.
For node addresses, whi ch are represented by the format area-number.node-
number, onl y the node-number porti on of the node address (the numeral
on the ri ght si de of the peri od) can contai n a wi l dcard. For exampl e, the
fol l owi ng command sets a COUNTER TI MER val ue of 45 seconds for al l
nodes i n area 4:
NCP>SET NODE 4.* COUNTER TIMER 45
Speci fyi ng a node address such as *.5 i s i nval i d because the area-number
cannot contai n a wi l dcard.
I n a node address, a wi l dcard character cannot be combi ned wi th a numeral
to represent a parti al node-number. The node addresses 4.* and 4.% contai n
val i d uses of the wi l dcard characters, but the node addresses 4.%2 and 4.1*
are i nval i d.
For events, whi ch are represented by the format class.type, onl y the type
porti on of the event (the numeral on the ri ght si de of the peri od) can contai n
a wi l dcard. For exampl e, the fol l owi ng command speci es that al l cl ass 2
events are to be l ogged:
NCP>SET KNOWN LOGGING EVENTS 2.*
13
Description
Except i n the case of events, onl y component names can contai n wi l dcards.
Parameter val ues cannot contai n wi l dcards. The fol l owi ng command i s i nval i d
because the ci rcui t name UNA-* i s not the component name i n the command.
Rather, i t i s a parameter used to modi fy the component named BOSTON.
Onl y component names can be represented by wi l dcard characters.
NCP>SET NODE BOSTON SERVICE CIRCUIT UNA-* !INVALID COMMAND
The component name EVENT i s used as a parameter to the LOGGI NG
commands and can contai n wi l dcard characters, as l ong as onl y the type
porti on of the event number (the numeral to the ri ght of the peri od) contai ns
the wi l dcard.
For exampl e, the fol l owi ng command cl ears l oggi ng to the l oggi ng l e for al l
cl ass 2 events:
NCP>CLEAR LOGGING FILE EVENTS 2.*
Uni t numbers of ci rcui t and l i ne devi ces can contai n wi l dcard characters,
but devi ce names of ci rcui ts and l i nes cannot contai n wi l dcard characters.
Ci rcui t and l i ne devi ces are typi cal l y i denti ed by the format dev-c, where dev
i s a mnemoni c devi ce name, and c i s a devi ce uni t number. I n the fol l owi ng
exampl e, the asteri sk repl aces the uni t number i n thi s request for ci rcui t
i nformati on for al l DMC devi ces:
NCP>SHOW CIRCUIT DMC-*
However, the device-name porti on of a ci rcui t or l i ne name cannot contai n
wi l dcard characters. Therefore, the fol l owi ng commands are i nval i d:
NCP>SHOW CIRCUIT D* STATUS !INVALID COMMAND
NCP>SHOW LINE %NA-0 SUMMARY !INVALID COMMAND
Note that substi tuti ng a wi l dcard character for an enti re component name i s
equi val ent to speci fyi ng the command component KNOWN. For exampl e:
NCP>SHOW NODE * STATUS
Thi s command i s equi val ent to the fol l owi ng command:
NCP>SHOW KNOWN NODES STATUS
1.3 Command Prompting
NCP prompts for sel ected components and parameters i f you do not suppl y them
when you enter the command. These components and parameters are those that
you use most often. Each prompt i s ei ther a l i st of val i d choi ces for that posi ti on
i n the command stri ng or the name of a parameter and a descri pti on of the val ue
requi red.
Note
Prompti ng does not occur when NCP recei ves i nput from a command l e.
Parameter names must be suppl i ed i n command l es.
14
Description
Each prompt consi sts of two parts: the component or parameter desi red, and i ts
format. The syntax i s as fol l ows:
component (format):
The component part i ndi cates the name of ei ther the component or parameter.
The format part i ndi cates the range of acceptabl e val ues. The format part
presents command words i n uppercase, val ue cl asses i n l owercase as descri pti ve
stri ngs, and numeri c ranges as two numbers separated by a hyphen. Commas
i ndi cate al ternati ves that are mutual l y excl usi ve.
Prompti ng does not guarantee that you are enteri ng a val i d command. Even
i f parameters are requi red to make the command meani ngful , prompti ng does
not demand a response for al l the requi red parameter val ues or names, as the
fol l owi ng exampl e i ndi cates:
NCP>SET OBJECT NML Return
Object number (0-255): Return
File name (filename.type): Return
Privileges (List of VMS privileges): Return
User ID (1-16 characters): Return
Password (1-8 characters): Return
Account (1-16 characters): Return
Proxy access INCOMING, OUTGOING, BOTH, NONE:) Return
%NCP-F-NOPARM, no parameters
NCP>
1.3.1 Exiting the Prompting Sequence
You can exi t a prompti ng sequence by pressi ng Ctrl /Z. When you do so, the NCP>
prompt returns, and you can then enter another NCP command. To exi t NCP
compl etel y, press Ctrl /Z at the NCP> prompt.
The fol l owi ng exampl e shows how to i nterrupt a prompti ng sequence and exi t
NCP.
NCP>SET Return
(CIRCUIT, EXECUTOR, KNOWN, LINE,
LOGGING, MODULE, NODE, OBJECT): LINE
Line ID (dev-c-u.t): FZA-1
Number of receive buffers (1-1024): Ctrl/Z
.
.
.
NCP> Ctrl/Z
$
I f, after respondi ng to one or more prompts, you want to exi t the prompti ng
sequence but retai n whatever i nformati on you have provi ded i n the database, you
can respond to the next prompt wi th _DONE, as fol l ows:
NCP>DEFINE OBJECT Return
Object Name (12 characters): TALOS
Object Number (0-255): 101
File name (filename): TALOS.EXE
Privileges (List of VMS privileges): _DONE
NCP>
I n thi s exampl e, NCP makes a new entry i n the permanent database for object
TALOS. Because _DONE i s used i n response to a prompt, NCP wri tes no
other parameter i nformati on to the database for thi s object, and NCP exi ts the
prompti ng sequence. Note that NCP returns a success message whenever i t
modi es the permanent database successful l y.
15
Description
Usi ng _DONE may not be successful , however, i f you do not provi de al l of the
necessary parameters for a gi ven component. For exampl e:
NCP>DEFINE OBJECT Return
Object Name (12 characters): RIGEL
Object Number (0-255): Return
File name (filename): RIGEL.EXE
Privileges (List of VMS privileges): _DONE
%NCP-I-NMLRSP, listener response - Parameter missing, number
Object = RIGEL
NCP>
Thi s exampl e i s si mi l ar to the previ ous exampl e except that the object number
i s omi tted. Because each object must have an object number dened i n the
database, and because none currentl y exi sts for object RI GEL, NCP does not
update the database wi th thi s i nformati on.
1.3.2 Prompting Examples
The fol l owi ng exampl es i l l ustrate three types of prompti ng that NCP provi des:
Prompts to suppl y mi ssi ng component
NCP>CLEAR Return
(CIRCUIT, EXECUTOR, KNOWN, LINE, LOGGING, MODULE, NODE, OBJECT):
No component i s speci ed for the CLEAR command. The prompt format
i s a l i st of val i d components separated by commas. Note that the pl ural
component KNOWN i s i ncl uded i n thi s l i st.
Prompts to suppl y parameter val ues
NCP>CLEAR LINE Return
LINE ID (dev-c-u):
NCP prompts for the line-id for thi s component because i t i s not provi ded
wi th the command.
The fol l owi ng exampl e shows vari ati ons of the prompti ng scheme for
parameter val ues:
NCP>SET EXECUTOR Return
Node address (1.1-63.1023): 2.11
State (ON, OFF, SHUT, RESTRICTED): ON
System id string (32 characters:) "DECnet for OpenVMS"
.
.
Prompts to sel ect parameter names
NCP>CLEAR LINE Return
Line ID (dev-c-u.t): FZA-1
All line parameters (Y,N):
NCP prompts for the sel ected parameter names whose val ues are to be
removed from the database. I n thi s case, no parameter name i s gi ven;
consequentl y, NCP asks i f al l val ues shoul d be removed. The Y parameter
i ndi cates that al l val ues shoul d be removed. Usi ng N or RETURN causes
NCP to provi de a di fferent response.
16
Description
NCP> CLEAR NODE BOSTON Return
All node parameters (Y,N): Return
Host node (Y,N): Y
.
.
.
Service password (Y,N): Y
Tertiary loader (Y,N): N
Because RETURN i s the response to the rst prompt, NCP prompts for al l of
the parameter names.
1.4 Component and Parameter Syntax Rules
When you enter NCP commands, many components, parameters, and qual i ers
requi re you to suppl y addi ti onal i nformati on. For the most part, thei r syntax
fol l ows a standard set of rul es. Excepti ons to these rul es are documented i n the
descri pti on of the component, parameter, or qual i er to whi ch they appl y.
The syntax of the vari ous component-name, parameter, and qual i er val ues
i s summari zed i n Tabl e 12. I n the fol l owi ng tabl e, al l numeri c val ues are i n
deci mal and have a range of 0 to 65,535 unl ess otherwi se speci ed:
Table 12 NCP Syntax Summary
account A stri ng of up to 39 al phanumeri c and hyphen characters.
OpenVMS operati ng systems do not currentl y use thi s
stri ng for access control .
area-number A deci mal val ue i n the range 1 to 63 to be speci ed i n the
begi nni ng of the node-address and separated from the node
number by a peri od. I f you do not speci fy an area number,
the area number of the executor i s used. The defaul t area
number for the executor i s 1.
(conti nued on next page)
17
Description
Table 12 (Cont.) NCP Syntax Summary
ci rcui t-i d A stri ng of characters whose exact syntax i s that for a
DECnet for OpenVMS ci rcui t. The stri ng may al so be
that for an X.25 ci rcui t i denti cati on. For X.25 ci rcui ts,
circuit-id i s a stri ng of up to 15 characters begi nni ng wi th
X25-.
Ci rcui t i denti cati on takes one of the fol l owi ng formats:
dev-c
dev-c-u
dev-c.t
dev-c-u.t
dev I s a devi ce name. Refer to the descri pti on of device-
type for a l i st of devi ce mnemoni c names. For
a compl ete l i st of DECnet for OpenVMS ci rcui t
devi ces and descri pti ons, see Appendi x A.
c I s a deci mal number (0 or a posi ti ve i nteger)
desi gnati ng the devi ces hardware control l er.
u I s a deci mal uni t or ci rcui t number (0 or a posi ti ve
i nteger) i ncl uded onl y i f more than one uni t i s
associ ated wi th the control l er.
t I s a deci mal number (0 or a posi ti ve i nteger) that
i denti es a tri butary on a mul ti poi nt ci rcui t. Thi s i s
a l ogi cal tri butary number, not to be confused wi th
the tri butary address used to pol l the tri butary.
cpu-type A stri ng of characters consi sti ng of one of the fol l owi ng:
DECSYSTEM1020
PDP11
PDP8
VAX
dest-name An i denti cati on stri ng consi sti ng of 1 to 16 al phanumeri c
characters.
devi ce-type A stri ng of characters representi ng the mnemoni c name
for the devi ce. Appendi x A i n thi s book contai ns a l i st of
devi ces, current as of thi s publ i cati on date. The fol l owi ng
l i st represents typi cal devi ces:
BNA FZA MFA MNA
QNA SVA UNA
dte-address A stri ng of up to 15 deci mal di gi ts. See the Public Network
I nformation manual for the exact format of thi s parameter
on your network.
18
Description
event-l i st A l i st of event types for a gi ven cl ass i n the format
cl ass.type. When speci fyi ng an event l i st, you may speci fy
onl y one cl ass; however, you can speci fy a range of types by
usi ng commas and hyphens, for exampl e, 4.35,710. You
can use the asteri sk wi l dcard character i n an event l i st, but
onl y to repl ace an event type. The fol l owi ng tabl e provi des
exampl es of these formats.
Event List Meaning
4.4 I denti es event cl ass 4, type 4.
4.57 I denti es event cl ass 4, types 5 through
7.
4.5,79,11 I denti es event cl ass 4, types 5, 7
through 9, and 11. Note that types must
be speci ed i n ascendi ng order.
4.* I denti es al l event types for cl ass 4
events.
l espec A l e speci cati on stri ng i n the fol l owi ng general format:
node-spec::device:[directory]lename.type;version
Logi cal names are permi tted.
Refer to the VMS DCL Concepts Manual for the format
of a l e speci cati on, and the Guide to OpenVMS File
Applications for more i nformati on about speci fyi ng l es.
h-address A stri ng of 6 pai rs of hexadeci mal di gi ts separated by
hyphens (for exampl e 08002B2BAFF3). The stri ng
represents the hardware address of a LAN devi ce control l er.
hex-byte A stri ng of exactl y 2 hexadeci mal di gi ts.
hex-password A stri ng of up to 8 hexadeci mal di gi ts.
hex-val ue A stri ng of up to 32 hexadeci mal di gi ts.
i d-stri ng A stri ng of up to 32 characters. I f the stri ng i ncl udes spaces
or tabs, encl ose i t wi thi n quotati on marks.
19
Description
l i ne-i d A stri ng of characters whose exact syntax i s that for a
DECnet for OpenVMS l i ne i denti cati on. The stri ng may
al so be that for an X.25 l i ne i denti cati on. For OpenVMS
operati ng systems, line-id takes one of the fol l owi ng
formats:
dev-c
dev-c-u
dev I s a devi ce name. Refer to the descri pti on of device-
type for a l i st of devi ce mnemoni c names. For a
compl ete l i st of DECnet for OpenVMS l i ne devi ces
and descri pti ons, see Appendi x A.
c I s a deci mal number (0 or a posi ti ve i nteger)
desi gnati ng the devi ces hardware control l er.
u I s a deci mal uni t or l i ne number (0 or a posi ti ve
i nteger) i ncl uded onl y i f more than one uni t i s
associ ated wi th the control l er.
mi croseconds A deci mal numeri c val ue.
mi l l i seconds A deci mal numeri c val ue.
network-name For X.25 ci rcui ts, speci es a 1- to 16-character
al phanumeri c i denti er that i ndi cates the network to be
used.
node-address A numeri c val ue i n the range 1.1 to 63.1023, composed
of an area number to the l eft of the peri od fol l owed by a
node number to the ri ght of the peri od. (The node number
i ndi cates the address of the node wi thi n the speci ed area.)
I f the area number i s not suppl i ed, the area number of the
executor node i s used. The defaul t area number for the
executor i s 1.
node-i d Ei ther a node-nameor a node-address.
node-name A stri ng of up to si x al phanumeri c characters contai ni ng at
l east one al phabeti c character.
node-spec A node-id fol l owed by opti onal access control i nformati on i n
the fol l owi ng format:
node-i d"user password"
node-i d"user password account"
node-type A stri ng of characters consi sti ng of one of the fol l owi ng:
Nonrouti ng I I I
Nonrouti ng I V
Routi ng I V
Routi ng I I I
Area
number A deci mal numeri c val ue.
object-name A stri ng of up to 16 pri ntabl e characters, consi sti ng of
al phanumeri c characters, the dol l ar si gn ($ ), or the
underscore (_).
VAX speci c
110
Description
p-address A stri ng of 6 pai rs of hexadeci mal di gi ts separated by
hyphens (for exampl e AA0004000310). The val ue i s
the uni que physi cal address that the node has set for i tsel f
or, i f the node has not set a physi cal address, the hardware
address associ ated wi th the nodes devi ce control l er.
password A stri ng of up to 39 pri ntabl e characters.
pri vi l ege-l i st A l i st of OpenVMS pri vi l ege names del i mi ted by space
characters.
seconds A deci mal numeri c val ue.
si nk-name A stri ng of al phanumeri c characters that speci es the name
of an event si nk. The l oggi ng consol e name i s a stri ng i n
the form TTcnn (i f a termi nal ) or a l e speci cati on i f i t i s a
l e that recei ves events i n the consol e format. The l oggi ng
l e name i s a l e speci cati on. The l oggi ng moni tor name
i s a 1- to 9-character name. I f the stri ng i ncl udes spaces or
tabs, encl ose i t i n quotati on marks.
software-i d A stri ng of up to 16 characters.
software-type A stri ng of characters consi sti ng of one of the fol l owi ng:
MANAGEMENT FI LE
SECONDARY LOADER
SYSTEM
TERTI ARY LOADER
tri butary-address A numeri c val ue i n the range of 0 to 255.
user-i d A stri ng of up to 39 al phanumeri c and hyphen characters.
The operati ng system may i ncl ude addi ti onal restri cti ons;
for exampl e, OpenVMS systems l i mi t the stri ng to 12
characters.
VAX speci c
Quotati on mark del i mi ters are val i d for the node-spec format. I n addi ti on, you
can use quotati on marks as del i mi ters when provi di ng recei ve and transmi t
passwords for the SET NODE and DEFI NE NODE commands. For exampl e:
NCP>SET NODE TRANSMIT PASSWORD "HI OpenVMS"
Al so, use quotati on marks to dene a software i denti cati on stri ng wi th text and
spaces for the I DENTI FI CATI ON parameter of the SET EXECUTOR command.
For exampl e:
NCP>SET EXECUTOR IDENTIFICATION "VMS HOST SYSTEM"
111
Description
1.5 NCP HELP Facility
1.5 NCP HELP Facility
NCP provi des an extensi ve HELP Faci l i ty that contai ns i nformati on about each
NCP command and i ts parameters and qual i ers, i ncl udi ng general exampl es
of i ts use. The i nformati on i n the HELP l e i s tree structured, whi ch makes i t
easy to retri eve i nformati on qui ckl y and efci entl y. The HELP descri pti on i n the
Command Secti on of thi s manual provi des exampl es to i l l ustrate the use of the
HELP command for a typi cal termi nal sessi on.
Use the HELP command to di spl ay i nformati on at vari ous l evel s of detai l .
For exampl e, each HELP di spl ay i ncl udes a l i st of command words under an
Addi ti onal I nformati on Avai l abl e secti on. These command words serve as topi cs
for the next l evel of i nformati on accessi bl e by the HELP command. I n the general
format of the HELP command shown i n the fol l owi ng exampl e, the topi c i s a
command word from the l i st:
NCP>HELP
Information available:
CLEAR Commands CONNECT COPY DEFINE DISCONNECT EVENTS
EXIT HELP LIST LOAD LOOP PARAMETERS Prompting
PURGE SET SHOW TELL TRIGGER ZERO
Topic?
You can abbrevi ate command words when you enter the command. When you
enter a parti cul ar l evel of detai l , that l evel becomes the current l evel for accessi ng
i nformati on. Through the use of the prompts Topic? and Subtopic?, you can
return to a hi gher or l ower l evel of i nformati on, respecti vel y. The hi ghest l evel of
i nformati on i s the general descri pti on of the HELP Faci l i ty.
ertai n
112
2
Using NCP
The Network Control Program (NCP) i s a DECnet for OpenVMS uti l i ty that
accepts commands to congure, control , moni tor, and test a DECnet network.
Entering Commands
To i nvoke NCP, enter the fol l owi ng DCL command:
$ RUN SYS$SYSTEM:NCP
NCP returns the fol l owi ng prompt:
NCP>
Al ternati vel y, you can enter a si ngl e NCP command from DCL by rst enteri ng a
DCL stri ng assi gnment statement. For exampl e:
$ NCP=="$NCP"
$ NCP SHOW EXECUTOR STATUS
Node Volatile Status as of 12-JUL-1992 11:57:59
Executor node = 4.306 (INTER)
State = on
Physical address = AA-00-04-00-32-11
Active links = 2
Delay = 0
$
NCP executes the SHOW EXECUTOR STATUS command and returns control to
DCL.
To exi t from an NCP sessi on, type EXI T or press CTRL/Z after the NCP>prompt.
Output for the SHOW and LI ST commands i s normal l y di spl ayed on the defaul t
output devi ce, SYS$OUTPUT. Al ternati vel y, you may di rect output to a speci ed
l e usi ng the TO qual i er wi th the SHOW or LI ST command.
Certai n NCP commands requi re pri vi l eges, as shown i n Tabl e 21. For DECnet
purposes, an account i s consi dered pri vi l eged i f any pri vi l eges other than
NETMBX and TMPMBX are hel d.
21
Using NCP
Table 21 Privileges for NCP Operations
Operation Required Privileges
Start the network ACNT, CMKRNL, SYSNAM, and DETACH
Perform task-to-task communi cati on NETMBX i s requi red to assi gn a channel to the
NET devi ce. TMPMBX i s requi red to opti onal l y
associ ate a temporary mai l box wi th a network
channel .
Create a l ogi cal l i nk NETMBX
Decl are a name or object number i n
a user task
SYSNAM (Refer to DECnet for OpenVMS
Networking Manual for i nformati on about user
tasks.)
CLEAR parameters from the
vol ati l e database
NETMBX and OPER
I ssue CONNECT commands NETMBX
COPY KNOWN NODES NETMBX, TMPMBX and OPER (SYSPRV i s al so
needed i f access to the permanent node database i s
requi red or i f the WI TH opti on i s used.)
DEFI NE parameters i n the
permanent database
SYSPRV and OPER
1
DI SCONNECT LI NKs NETMBX and OPER
LI ST parameters kept i n the
permanent database
SYSPRV
1
LI ST servi ce passwords kept i n the
permanent database
SYSPRV and OPER
1
LI ST recei ve passwords, transmi t
passwords, and object and executor
access control passwords kept i n the
permanent database
BYPASS
I ssue LOAD commands NETMBX, TMPMBX and OPER
Use LOOP CI RCUI T NETMBX, TMPMBX and OPER
Use LOOP EXECUTOR NETMBX and TMPMBX
PURGE parameters from the
permanent database
SYSPRV and OPER
1
SET parameters kept i n the vol ati l e
database
NETMBX and OPER
I ssue SET EXECUTOR NODE Requi res NETMBX and TMPMBX pri vi l eges on
the l ocal node, and NML on the executor node
must have appropri ate pri vi l eges to perform the
commands i ssued after the SET EXECUTOR
NODE command.
Use "SET component ALL" to l oad
parameters from the permanent
database to the vol ati l e database
NETMBX, OPER and SYSPRV
1
SHOW parameters kept i n the
vol ati l e database
NETMBX
1
You can perform operati ons requi ri ng access to the permanent database wi thout the SYSPRV
pri vi l ege i f you have read and wri te access to al l congurati on database l es or hol d BYPASS
pri vi l ege. However, Di gi tal recommends that you protect these network congurati on l es from
unauthori zed access by requi ri ng SYSPRV to access these l es.
22
Using NCP
Table 21 (Cont.) Privileges for NCP Operations
Operation Required Privileges
SHOW servi ce passwords kept i n
the vol ati l e database
NETMBX and OPER
SHOW recei ve passwords, transmi t
passwords, and access control
passwords kept i n the vol ati l e
database
NETMBX and BYPASS
I ssue TELL commands Requi res NETMBX and TMPMBX on the l ocal
node, and NML on the executor node must have
sufci ent pri vi l eges to perform the command that
fol l ows TELL.
I ssue TRI GGER commands NETMBX, TMPMBX and OPER
ZERO counters NETMBX and OPER
2.1 Hints for Using Commands
You can abbrevi ate any command verb, component, parameter, or qual i er as
l ong as the abbrevi ati on i s not ambi guous.
Commands that have the same components and parameters, yet di fferent
command verbsdependi ng upon whether they access the vol ati l e or the
permanent databaseare l i sted together i n Chapter 3. Exampl es of commands
l i sted together are CLEAR and PURGE, SET and DEFI NE, and SHOW and LI ST,
where CLEAR, SET, and SHOW verbs appl y to the vol ati l e database and PURGE,
DEFI NE and LI ST verbs appl y to the permanent database. When two commands
are grouped together, components and parameters are descri bed for the command
that accesses the vol ati l e database. Typi cal l y, the acti ons descri bed for the
vol ati l e database al so appl y to the permanent database. However, i f certai n
commands appl y onl y to a parti cul ar database or i f a di fferent acti on i s requi red
for the vol ati l e and permanent databases, these excepti ons are speci cal l y noted
i n the command descri pti on.
I n general , the NCP commands and parameters are common to most network
congurati ons. Excepti ons to thi s general rul e are noted under the command
or parameter to whi ch they appl y. The VAX margi n i con i ndi cates functi ons
supported onl y on VAX systems. Other restri cti ons are noted as part of the
command or parameter descri pti on.
Note
Al though NCP may accept a parti cul ar command syntax, thi s i s no
guarantee that some other DECnet i mpl ementati on supports the functi on.
For a compl ete descri pti on of the network components speci ed i n NCP
commands, see the DECnet for OpenVMS Networking Manual. That manual
al so expl ai ns how to use the NCP commands to manage the DECnet network.
23
3
NCP Commands
Thi s chapter presents NCP command descri pti ons. Commands are presented
i n al phabeti cal order wi th the associ ated command parameters and appropri ate
exampl es.
NCP al l ows for management of the l ocal node and for remote management of any
DECnet node that you speci fy as the executor. When you i ssue NCP commands,
there are two ways to speci fy the executor the l ocati on at whi ch the command
executes:
Begi n i ndi vi dual NCP commands wi th the TELL prex.
Set the executor wi th the SET EXECUTOR NODE command. Al l subsequent
NCP commands execute at the remote node unti l you:
I ssue another SET EXECUTOR NODE command,
I ssue a CLEAR EXECUTOR NODE command, or
Exi t NCP.
To enter one or two NCP commands for remote executi on, i t i s probabl y easi er to
use the TELL prex. To execute mul ti pl e NCP commands at a remote node, rst
i ssue the SET EXECUTOR NODE command, speci fyi ng that node.
Note
NCP commands and command parameters are not al l supported on every
hardware pl atform. I n some cases, NCP al l ows you to set and di spl ay
an unsupported parameter. However, the unsupported parameter i s not
functi onal and has no effect on the operati on of the DECnet software.
31
CLEAR/PURGE CIRCUIT
CLEAR/PURGE CIRCUIT
The CLEAR CI RCUI T command resets ci rcui t parameters i n the vol ati l e database
to the defaul t val ue (i f any), or removes them from the vol ati l e database. The
PURGE CI RCUI T command removes ci rcui t parameters from the permanent
database.
Format
CLEAR circuit-component parameter [...]
PURGE circuit-component parameter [...]
Circuit Components
CIRCUIT KNOWN CIRCUITS
Circuit Components
CIRCUIT circuit-id
Resets to the defaul t val ue (i f any) or removes from the database the parameters
for a speci c ci rcui t. The circuit-id speci es the name of the ci rcui t you want to
cl ear.
KNOWN CIRCUITS
Resets to the defaul t val ue (i f any) or removes from the database the parameters
for al l known ci rcui ts.
Command Parameters
ACTIVE BASE (VAX only)
VAX
Appl i es onl y to DDCMP CONTROL ci rcui ts. Resets to i ts defaul t val ue the
ACTI VE BASE val ue i n vol ati l e the database. Removes the ACTI VE BASE
parameter from the permanent database.
ACTIVE INCREMENT (VAX only)
ACTI VE I NCREMENT val ue i n the vol ati l e database. Removes the ACTI VE
I NCREMENT parameter from the permanent database.
ALL
Removes from the database the speci ed ci rcui t or al l known ci rcui ts. The ci rcui t
must be i n the OFF state before you speci fy thi s parameter.
VAX
BABBLE TIMER (VAX only)
BABBLE TI MER val ue i n the vol ati l e database. Removes the BABBLE TI MER
COST
Resets to i ts defaul t val ue the COST val ue i n the vol ati l e database. Removes the
COST parameter from the permanent database. Does not appl y to X.25 PVCs.
32
CLEAR/PURGE CIRCUIT
COUNTER TIMER
Cancel s the event l oggi ng ti mer. Thi s cancel l ati on prevents any further ci rcui t
counter event l oggi ng for the i ndi cated ci rcui t or ci rcui ts.
VAX
DEAD THRESHOLD (VAX only)
DEAD THRESHOLD number i n the vol ati l e database. Removes the DEAD
THRESHOLD parameter from the permanent database.
DTE (Remote management only)
Appl i es onl y to DLM ci rcui ts. Al l ows the X.25 cal l to be set up usi ng any l ocal
DTE.
VAX
DYING BASE (VAX only)
DYI NG BASE val ue i n the vol ati l e database. Removes the DYI NG BASE
DYING INCREMENT (VAX only)
DYI NG I NCREMENT val ue i n the vol ati l e database. Removes the DYI NG
DYING THRESHOLD (VAX only)
DYI NG THRESHOLD number i n the vol ati l e database. Removes the DYI NG
HELLO TIMER
Resets to i ts defaul t val ue the HELLO TI MER val ue i n the vol ati l e database.
Removes the HELLO TI MER parameter from the permanent database.
VAX
INACTIVE BASE (VAX only)
I NACTI VE BASE val ue i n the vol ati l e database. Removes the I NACTI VE BASE
INACTIVE INCREMENT (VAX only)
I NACTI VE I NCREMENT val ue i n the vol ati l e database. Removes the I NACTI VE
INACTIVE THRESHOLD (VAX only)
I NACTI VE THRESHOLD val ue i n the vol ati l e database. Removes the I NACTI VE
MAXIMUM BUFFERS (VAX only)
MAXI MUM BUFFERS val ue i n the vol ati l e database. Removes the MAXI MUM
BUFFERS parameter from the permanent database.
MAXIMUM RECALLS (Remote management only)
Appl i es onl y to X.25 DLM ci rcui ts. Resets to i ts defaul t val ue the l i mi t on
the number of cal l retri es i n the vol ati l e database. Removes the MAXI MUM
RECALLS parameter from the permanent database.
33
CLEAR/PURGE CIRCUIT
MAXIMUM ROUTERS
Appl i es onl y to Ethernet and FDDI ci rcui ts. Resets to i ts defaul t val ue the
MAXI MUM ROUTER val ue i n the vol ati l e database. Removes the MAXI MUM
ROUTERS parameter from the permanent database.
VAX
MAXIMUM TRANSMITS (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Resets to i ts defaul t val ue
the MAXI MUM TRANSMI T number i n the vol ati l e database. Removes the
MAXI MUM TRANSMI TS parameter from the permanent database.
NETWORK (Remote management only)
Appl i es onl y to purgi ng X.25 PVCs and X.25 DLM ci rcui ts. Removes the ci rcui ts
network parameters from the permanent database.
NUMBER (Remote management only)
Appl i es onl y to i ncomi ng DLM ci rcui ts. Removes the restri cti on on accepti ng cal l s
onl y from a parti cul ar remote DTE number.
RECALL TIMER (Remote management only)
Appl i es onl y to X.25 DLM ci rcui ts. Resets to i ts defaul t val ue the RECALL
TI MER val ue i n the vol ati l e database. Removes the RECALL TI MER parameter
from the permanent database.
ROUTER PRIORITY
Appl i es onl y to Ethernet and FDDI ci rcui ts. Resets to i ts defaul t val ue the
pri ori ty assi gned to the router i n the vol ati l e database. Removes the ROUTER
PRI ORI TY parameter from the permanent database.
VAX
TRANSMIT TIMER (VAX only)
TRANSMI T TI MER val ue i n the database.
34
CLEAR/PURGE CIRCUIT
Examples
VAX
1.
NCP>CLEAR CIRCUIT DMB-0 ALL
Thi s command removes al l parameter entri es for ci rcui t DMB0 i n the
vol ati l e database. As a resul t, the ci rcui t no l onger exi sts for the l ocal
DECnet software.
2. NCP>CLEAR CIRCUIT DMP-0.4 COUNTER TIMER
Thi s command removes the COUNTER TI MER parameter for ci rcui t
DMP0.4 from the vol ati l e database.
3. NCP>PURGE CIRCUIT SVA-0 ALL
Thi s command removes al l parameter entri es i n the permanent database for
the Ethernet ci rcui t SVA-0.
4. NCP>CLEAR CIRCUIT SVA-* ALL
Thi s command cl ears al l SVA ci rcui ts and the associ ated parameters for al l
SVA ci rcui ts i n the vol ati l e database.
35
CLEAR/PURGE EXECUTOR
The CLEAR EXECUTOR command resets sel ected parameters to the defaul t
val ue (i f any) or removes them from the vol ati l e database. You cannot cl ear
the BUFFER SI ZE, SEGMENT BUFFER SI ZE, MAXI MUM BROADCAST
ROUTERS, ALI AS NODE, or STATE parameters from the vol ati l e database
when the executor i s i n the ON state.
The PURGE EXECUTOR command removes sel ected parameters from the
permanent database.
Format
CLEAR EXECUTOR parameter [...]
PURGE EXECUTOR parameter [...]
Command Parameters
ALIAS INCOMING
Removes from the database the ALI AS I NCOMI NG parameter.
ALIAS MAXIMUM LINKS
Resets to i ts defaul t val ue the ALI AS MAXI MUM LI NKS val ue i n the vol ati l e
database. Removes the ALI AS MAXI MUM LI NKS parameter from the
permanent database.
ALIAS NODE
Removes from the permanent database the al i as node i denti er.
ALL
Removes from the permanent database al l executor parameters.
VAX
AREA MAXIMUM COST (VAX only)
Resets to i ts defaul t val ue the AREA MAXI MUM COST val ue for the l ocal node
i n the vol ati l e database. Removes the AREA MAXI MUM COST parameter for the
l ocal node from the permanent database.
AREA MAXIMUM HOPS (VAX only)
Resets to i ts defaul t val ue the AREA MAXI MUM HOPS val ue for the l ocal node
i n the vol ati l e database. Removes the AREA MAXI MUM HOPS parameter for
the l ocal node from the permanent database.
BROADCAST ROUTING TIMER
Resets to i ts defaul t val ue the BROADCAST ROUTI NG TI MER val ue i n the
vol ati l e database. Removes the BROADCAST ROUTI NG TI MER parameter from
the permanent database.
BUFFER SIZE
Removes from the permanent database the BUFFER SI ZE val ue.
COUNTER TIMER
Removes from the database the l oggi ng ti mer to prevent any further counter
l oggi ng for the l ocal node.
36
DEFAULT ACCESS
Resets to i ts defaul t val ue the DEFAULT ACCESS val ue i n the vol ati l e database.
Removes the DEFAULT ACCESS parameter from the permanent database.
DELAY FACTOR
Resets to i ts defaul t val ue the DELAY FACTOR val ue for the l ocal node i n the
vol ati l e database. Removes the DELAY FACTOR parameter for the l ocal node
DELAY WEIGHT
Resets to i ts defaul t val ue the DELAY WEI GHT val ue for the l ocal node i n the
vol ati l e database. Removes the DELAY WEI GHT parameter for the l ocal node
VAX
DNS INTERFACE (VAX only)
Removes from the database the DNS I NTERFACE parameter.
DNS NAMESPACE (VAX only)
Removes from the database the DNS NAMESPACE parameter.
IDENTIFICATION
Removes from the database the i denti cati on stri ng.
VAX
IDP (VAX only)
Removes from the database the I DP parameter.
INACTIVITY TIMER
Resets to i ts defaul t val ue the I NACTI VI TY TI MER val ue for the l ocal node i n
the vol ati l e database. Removes the I NACTI VI TY TI MER parameter for the l ocal
node from the permanent database.
INCOMING PROXY
Resets to i ts defaul t val ue the I NCOMI NG PROXY val ue for the l ocal node i n the
vol ati l e database. Removes the I NCOMI NG PROXY parameter for the l ocal node
INCOMING TIMER
Resets to i ts defaul t val ue the I NCOMI NG TI MER val ue for the l ocal node i n the
vol ati l e database. Removes the I NCOMI NG TI MER parameter for the l ocal node
MAXIMUM ADDRESS
Resets to i ts defaul t val ue the MAXI MUM ADDRESS val ue for the l ocal node
i n the vol ati l e database. Removes the MAXI MUM ADDRESS parameter for the
VAX
MAXIMUM AREA (VAX only)
Resets to i ts defaul t val ue the MAXI MUM AREA val ue for the l ocal node i n the
vol ati l e database. Removes the MAXI MUM AREA parameter for the l ocal node
MAXIMUM BROADCAST NONROUTERS
Resets to i ts defaul t val ue the MAXI MUM BROADCAST NONROUTERS val ue
i n the vol ati l e database. Removes the MAXI MUM BROADCAST NONROUTERS
parameter for the l ocal node from the permanent database.
37
MAXIMUM BROADCAST ROUTERS
Removes the MAXI MUM BROADCAST ROUTERS parameter from the
permanent database.
MAXIMUM BUFFERS
Resets to i ts defaul t val ue the MAXI MUM BUFFERS val ue for the l ocal node
i n the vol ati l e database. Removes the MAXI MUM BUFFERS parameter for the
MAXIMUM CIRCUITS
Removes the MAXI MUM CI RCUI TS parameter from the permanent database.
MAXIMUM COST
Resets to i ts defaul t val ue the MAXI MUM COST val ue for the l ocal node i n the
vol ati l e database. Removes the MAXI MUM COST parameter for the l ocal node
MAXIMUM DECLARED OBJECTS
Resets to i ts defaul t val ue the MAXI MUM DECLARED OBJECTS parameter
i n the vol ati l e database. Removes the MAXI MUM DECLARED OBJECTS
parameter for the l ocal node from the permanent database.
MAXIMUM HOPS
Resets to i ts defaul t val ue the MAXI MUM HOPS val ue for the l ocal node i n the
vol ati l e database. Removes the MAXI MUM HOPS parameter for the l ocal node
MAXIMUM LINKS
Resets to i ts defaul t val ue the MAXI MUM LI NKS val ue for the l ocal node i n the
vol ati l e database. Removes the MAXI MUM LI NKS parameter for the l ocal node
VAX
MAXIMUM PATH SPLITS (VAX only)
Resets to i ts defaul t val ue the MAXI MUM PATH SPLI TS val ue for the l ocal node
i n the vol ati l e database. Removes the MAXI MUM PATH SPLI TS parameter for
the l ocal node from the permanent database.
MAXIMUM VISITS
Resets to i ts defaul t val ue the MAXI MUM VI SI TS val ue for the l ocal node i n the
vol ati l e database. Removes the MAXI MUM VI SI TS parameter for the l ocal node
NONPRIVILEGED item
Removes from the database the speci ed nonpri vi l eged access control i nformati on.
Speci fy any or al l of the fol l owi ng i tems for removal :
ACCOUNT
PASSWORD
USER
OUTGOING PROXY
Resets to i ts defaul t val ue the OUTGOI NG PROXY val ue for the l ocal node i n the
vol ati l e database. Removes the OUTGOI NG PROXY parameter for the l ocal node
38
OUTGOING TIMER
Resets to i ts defaul t val ue the OUTGOI NG TI MER val ue for the l ocal node i n the
vol ati l e database. Removes the OUTGOI NG TI MER parameter for the l ocal node
VAX
PATH SPLIT POLICY (VAX only)
Resets to i ts defaul t val ue the PATH SPLI T POLI CY val ue for the l ocal node i n
the vol ati l e database. Removes the PATH SPLI T POLI CY parameter for the l ocal
node from the permanent database.
PIPELINE QUOTA
Resets to i ts defaul t val ue the PI PELI NE QUOTA val ue for the l ocal node i n the
vol ati l e database. Removes the PI PELI NE QUOTA parameter for the l ocal node
PRIVILEGED item
Removes from the database the speci ed pri vi l eged access control i nformati on.
ACCOUNT
PASSWORD
USER
RETRANSMIT FACTOR
Resets to i ts defaul t val ue the RETRANSMI T FACTOR val ue for the l ocal node
i n the vol ati l e database. Removes the RETRANSMI T FACTOR parameter for the
VAX
ROUTING TIMER
Resets to i ts defaul t val ue the ROUTI NG TI MER val ue for the l ocal node i n the
vol ati l e database. Removes the ROUTI NG TI MER parameter for the l ocal node
SEGMENT BUFFER SIZE
Removes the SEGMENT BUFFER SI ZE parameter for the l ocal node from the
permanent database.
STATE
Removes from the permanent database the l ocal nodes state.
SUBADDRESSES (Remote management only)
Removes from the database the val ue of the range of l ocal DTE subaddresses.
TYPE
Removes the TYPE parameter for the l ocal node from the permanent database.
39
Examples
1. NCP>PURGE EXECUTOR IDENTIFICATION INCOMING TIMER
Thi s command removes the l ocal nodes i denti cati on stri ng and i ncomi ng
ti mer val ue from the permanent database.
2. NCP>PURGE EXECUTOR COUNTER TIMER
Thi s command removes the l ocal nodes counter ti mer val ue from the
permanent database.
VAX
3.
NCP>CLEAR EXECUTOR AREA MAXIMUM COST
Thi s command resets to i ts defaul t val ue the AREA MAXI MUM COST
parameter i n the vol ati l e database for the executor.
310
CLEAR EXECUTOR NODE
CLEAR EXECUTOR NODE
The CLEAR EXECUTOR NODE command cl ears the defaul t executor
desi gnati on. The executor of commands becomes the l ocal node. You cannot
use the TELL prex wi th the CLEAR EXECUTOR NODE command.
After you enter the CLEAR EXECUTOR NODE command, NCP on the l ocal node
performs al l operati ons usi ng the pri vi l eges of your current process i nstead of the
pri vi l ege associ ated wi th the defaul t nonpri vi l eged or pri vi l eged accounts.
Format
CLEAR EXECUTOR NODE
Parameters
None.
Examples
1. NCP>SET EXECUTOR NODE TRNTO"GRAY MARY"
.
.
.
NCP>CLEAR EXECUTOR NODE
The rst command sets the executor node to node TRNTO. The second
command cl ears the defaul t executor node desi gnati on speci ed previ ousl y by
the SET EXECUTOR NODE command. The executor node i s now the l ocal
node.
311
CLEAR/PURGE LINE
CLEAR/PURGE LINE
The CLEAR LI NE command resets l i ne parameters to the defaul t val ue (i f any)
or removes the entri es and parameters from the vol ati l e database.
The PURGE LI NE command removes l i ne parameters from the permanent
database.
Format
CLEAR line-component parameter [...]
PURGE line-component parameter [...]
Line Components
LINE KNOWN LINES
Line Components
LINE line-id
I denti es the speci c l i ne whose parameters are to be reset to thei r defaul t val ues
(i f any) or removed from the database.
KNOWN LINES
Resets the parameters to the defaul t val ue (i f any) or removes them for al l known
l i nes from the database.
Command Parameters
ALL
Removes the speci ed l i ne or al l known l i nes from the database. The l i ne must
be i n the OFF state before you speci fy thi s parameter.
CONTROLLER
Resets to i ts defaul t val ue the CONTROLLER parameter i n the vol ati l e database.
Removes the CONTROLLER parameter from the permanent database.
COUNTER TIMER
Removes the event l oggi ng ti mer. Thi s prevents any further l i ne counter event
l oggi ng for the i ndi cated l i ne(s).
VAX
DEAD TIMER (VAX only)
Appl i es onl y to DDCMP l i nes. Resets the DEAD TI MER parameter to i ts defaul t
val ue i n the vol ati l e database. Removes the DEAD TI MER parameter from the
permanent database.
DELAY TIMER (VAX only)
Appl i es onl y to DDCMP l i nes. Removes the DELAY TI MER parameter from the
database.
ECHO DATA
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the ECHO DATA
parameter i n the vol ati l e database. Permanent database operati ons cannot
be performed on thi s parameter.
312
CLEAR/PURGE LINE
ECHO LENGTH
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the ECHO LENGTH
parameter i n the vol ati l e database. Permanent database operati ons cannot be
performed on thi s parameter.
ECHO TARGET
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the ECHO TARGET
parameter i n the vol ati l e database. Permanent database operati ons cannot be
performed on thi s parameter.
VAX
HANGUP (VAX only)
Appl i es onl y to asynchronous DDCMP l i nes. Removes the HANGUP parameter
from the database.
HOLDBACK TIMER (Remote management only)
Appl i es onl y to X.25 l i nes. Removes the HOLDBACK TI MER parameter from the
database, causi ng the X.25 software to acknowl edge recei ved data i mmedi atel y.
VAX
LINE SPEED (VAX only)
Appl i es onl y to asynchronous DDCMP l i nes. Removes the LI NE SPEED
parameter from the database.
MAXIMUM BLOCK (Remote management only)
Appl i es onl y to X.25 l i nes. Resets to i ts defaul t val ue the MAXI MUM BLOCKS
parameter i n the vol ati l e database. Removes the MAXI MUM BLOCKS parameter
MAXIMUM RETRANSMITS (Remote management only)
Appl i es onl y to X.25 l i nes. Resets the maxi mum number of retransmi ssi ons
of a frame to the defaul t val ue for the speci ed l i ne or al l known l i nes i n the
vol ati l e database. Removes the MAXI MUM RETRANSMI TS parameter from the
permanent database.
NIF TARGET
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the NI F TARGET
parameter i n the vol ati l e database. Permanent database operati ons cannot
be performed on thi s parameter.
PROTOCOL
Removes the val ue for the PROTOCOL parameter from the permanent database.
RECEIVE BUFFERS
Resets the RECEI VE BUFFERS parameter to i ts defaul t val ue i n the vol ati l e
database. Removes the RECEI VE BUFFERS parameter from the permanent
database. The l i ne must be i n the OFF state i n order to CLEAR thi s parameter.
REQUESTED TRT
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the REQUESTED TRT
parameter i n the vol ati l e database. Removes the REQUESTED TRT parameter
RESTRICTED TOKEN TIMEOUT
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the RESTRI CTED TOKEN
TI MEOUT parameter i n the vol ati l e database. Removes the RESTRI CTED
TOKEN TI MEOUT parameter from the permanent database.
313
CLEAR/PURGE LINE
RING PURGER ENABLE
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the RI NG PURGER
ENABLE parameter i n the vol ati l e database. Removes the RI NG PURGER
ENABLE parameter from the permanent database.
VAX
SCHEDULING TIMER (VAX only)
Appl i es onl y to DDCMP l i nes. Resets the SCHEDULI NG TI MER parameter to
i ts defaul t val ue i n the database.
SERVICE TIMER
Resets to i ts defaul t val ue the SERVI CE TI MER parameter i n the vol ati l e
database. Removes the SERVI CE TI MER parameter from the permanent
database.
SIF CONFIGURATION TARGET
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the SI F CONFI GURATI ON
TARGET parameter i n the vol ati l e database. Permanent database operati ons
cannot be performed on thi s parameter.
SIF OPERATION TARGET
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the SI F OPERATI ON
TARGET parameter i n the vol ati l e database. Permanent database operati ons
cannot be performed on thi s parameter.
STATE
Resets to i ts defaul t val ue the STATE parameter i n the vol ati l e database.
Removes the STATE parameter from the permanent database.
VAX
STREAM TIMER (VAX only)
Appl i es onl y to DDCMP l i nes. Resets the STREAM TI MER parameter to i ts
defaul t val ue i n the database.
SWITCH (VAX only)
Appl i es onl y to asynchronous DDCMP l i nes. Removes the SWI TCH parameter
from the database.
TRANSMIT PIPELINE (VAX only)
Appl i es onl y to DMR11 l i nes. Removes the TRANSMI T PI PELI NE parameter
from the database.
VALID TRANSMISSION TIME
Appl i es onl y to FDDI l i nes. Resets to i ts defaul t val ue the VALI D
TRANSMI SSI ON TI ME parameter i n the vol ati l e database. Removes the
VALI D TRANSMI SSI ON TI ME parameter from the permanent database.
314
CLEAR/PURGE LINE
Examples
1. NCP>CLEAR LINE SVA-0 ALL
Thi s command removes the Ethernet l i ne cal l ed SVA0 from the vol ati l e
database.
VAX
2.
NCP>CLEAR LINE DMB-0 ALL
Thi s command removes DDCMP l i ne DMB0 from the vol ati l e database.
VAX
3.
NCP>CLEAR LINE DMB-* ALL
Thi s command removes al l DDCMP DMB l i nes from the vol ati l e database.
315
CLEAR/PURGE LOGGING
CLEAR/PURGE LOGGING
The CLEAR LOGGI NG command removes l oggi ng parameters from the vol ati l e
database. The PURGE LOGGI NG command removes l oggi ng parameters from
Format
CLEAR logging-component parameter
PURGE logging-component parameter
Logging Components
KNOWN LOGGING LOGGING FILE
LOGGING CONSOLE LOGGING MONITOR
Logging Components
KNOWN LOGGING
Removes from the database the parameters for al l known l oggi ng.
LOGGING CONSOLE
Removes from the database al l parameters for l oggi ng to the consol e.
LOGGING FILE
Removes from the database al l parameters for l oggi ng to a l e.
LOGGING MONITOR
Removes from the database al l parameters for l oggi ng to a moni tor.
Command Parameters
ALL
Removes al l parameters from the database. After you enter the CLEAR/PURGE
LOGGI NG command wi th thi s parameter, the l oggi ng component i s no l onger
recogni zed by the network.
CIRCUIT circuit-id
Removes from the database al l l oggi ng parameters for the speci ed ci rcui t.
LINE line-id
Removes from the database al l l oggi ng parameters for the speci ed l i ne.
NODE node-id
Removes from the database al l l oggi ng parameters for the speci ed node.
Examples
1. NCP>CLEAR LOGGING CONSOLE ALL
Thi s command cl ears l oggi ng to the l oggi ng consol e, after whi ch the l oggi ng
component i s no l onger recogni zed by the network.
316
CLEAR/PURGE LOGGING EVENTS
The CLEAR LOGGI NG EVENTS command removes event-source l oggi ng
parameters from the vol ati l e database. The PURGE LOGGI NG EVENTS
command removes event-source l oggi ng parameters from the permanent database.
I f no source i s speci ed i n the command, the source speci c events wi l l not be
affected.
Format
CLEAR logging-component parameter [...]
PURGE logging-component parameter [...]
Logging Components
Logging Components
KNOWN LOGGING
Removes from the database the parameters for al l known l oggi ng.
LOGGING CONSOLE
Removes from the database the parameters for l oggi ng to the consol e.
LOGGING FILE
Removes from the database the parameters for l oggi ng to a l e.
LOGGING MONITOR
Removes from the database the parameters for l oggi ng to a moni tor program.
Command Parameters
EVENTS event-list
KNOWN EVENTS
Removes from the database an event cl ass and type or al l event cl asses and types.
You can associ ate any of the fol l owi ng source parameters when you speci fy the
EVENTS parameter.
CI RCUI T ci rcui t-i d I denti es the ci rcui t to whi ch the events appl y.
Events wi l l not be l ogged for thi s ci rcui t.
LI NE l i ne-i d I denti es the l i ne to whi ch the events appl y. Events
wi l l not be l ogged for thi s source.
NODE node-i d I denti es the node to whi ch the events appl y.
Events wi l l not be l ogged for thi s source.
317
SI NK I denti es the node where the event l ogger runs to
l og the events. There are two possi bi l i ti es:
EXECUTOR I denti es the l ocal node
NODE node-i d I denti es the node at whi ch
events are bei ng l ogged
Onl y events bei ng l ogged to thi s node are removed
from the database. I f thi s parameter i s omi tted, the
l ocal node i s assumed to be the si nk node affected.
Examples
1. NCP>CLEAR LOGGING FILE EVENTS 2.*
Thi s command cl ears l oggi ng to the l oggi ng l e for al l cl ass 2 events.
2. NCP>CLEAR LOGGING CONSOLE KNOWN EVENTS LINE SVA-1
Thi s command cl ears l oggi ng to the consol e for al l known events currentl y
bei ng l ogged for l i ne SVA1, an Ethernet l i ne.
318
CLEAR/PURGE LOGGING NAME
CLEAR/PURGE LOGGING NAME
The CLEAR LOGGI NG NAME command removes the name of the l oggi ng si nk
from the vol ati l e database. The PURGE LOGGI NG NAME command removes the
name of the l oggi ng si nk from the permanent database.
You must enter a SET LOGGI NG component STATE OFF command before
attempti ng to use the CLEAR command.
Format
CLEAR logging-component NAME
PURGE logging-component NAME
Logging Components
Logging Components
KNOWN LOGGING
I ndi cates that the name of the l oggi ng si nk for al l known l oggi ng i s to be removed
from the database.
LOGGING CONSOLE
I ndi cates that the name of the l oggi ng consol e i s to be removed from the database.
LOGGING FILE
I ndi cates that the name of the l oggi ng l e i s to be removed from the database.
LOGGING MONITOR
I ndi cates that the name of the l oggi ng moni tor i s to be removed from the
database.
Examples
1. NCP>CLEAR LOGGING CONSOLE NAME
Thi s command cl ears the name of the l oggi ng consol e from the vol ati l e
database.
319
CLEAR/PURGE MODULE CONFIGURATOR
CLEAR/PURGE MODULE CONFIGURATOR
The CLEAR MODULE CONFI GURATOR KNOWN CI RCUI TS ALL command
removes from the vol ati l e database the Ethernet congurator modul e component
parameters for al l ci rcui ts. The CLEAR command can not be used to remove
i ndi vi dual ci rcui ts. The PURGE MODULE CONFI GURATOR ALL command
removes from the permanent database the Ethernet congurator modul e
component parameters for al l ci rcui ts. The PURGE command can be used to
remove i ndi vi dual ci rcui ts.
Format
PURGE MODULE CONFIGURATOR circuit-component ALL
CLEAR MODULE CONFIGURATOR KNOWN CIRCUITS ALL
Circuit Components
Circuit Components
CIRCUIT circuit-id
For the PURGE command onl y. Appl i es onl y to Ethernet ci rcui ts. Removes from
the permanent database at the l ocal node al l congurator modul e parameters
rel ated to the speci ed ci rcui t.
KNOWN CIRCUITS
Appl i es onl y to Ethernet ci rcui ts. Removes from the vol ati l e database al l
congurator modul e parameters rel ated to al l known Ethernet ci rcui ts.
Command Parameter
ALL
Removes al l parameters for the speci ed ci rcui t or ci rcui ts from the vol ati l e
database. After you i ssue thi s parameter, the ci rcui t component i s no l onger
recogni zed by the congurator.
Examples
1. NCP>PURGE MODULE CONFIGURATOR KNOWN CIRCUITS ALL
Thi s command removes from the permanent database at the l ocal node al l
congurator modul e parameters rel ated to al l known Ethernet ci rcui ts.
2. NCP>PURGE MODULE CONFIGURATOR CIRCUIT SVA-0 ALL
Thi s command removes from the permanent database at the l ocal node al l
congurator modul e parameters rel ated to the SVA-0 ci rcui t.
3. NCP>CLEAR MODULE CONFIGURATOR KNOWN CIRCUITS ALL
Thi s command removes from the vol ati l e database al l congurator modul e
parameters rel ated to al l known Ethernet ci rcui ts.
320
CLEAR/PURGE MODULE X25-ACCESS (Remote management only)
CLEAR/PURGE MODULE X25-ACCESS (Remote management only)
The CLEAR MODULE X25-ACCESS command removes from the vol ati l e
database network names and parameters used by the host node to access a
speci ed X.25 network or networks through a connector node. The PURGE
MODULE X25-ACCESS command removes these same network names and
parameters from the permanent database.
Note
Use thi s command to manage VAX P.S.I . on remote nodes. To manage a
remote node, enter thi s command as a parameter to the TELL command,
or use the SET EXECUTOR NODE command rst.
Format
CLEAR MODULE X25-ACCESS qualier
parameter [...]
PURGE MODULE X25-ACCESS qualier
parameter [...]
Qualiers
NETWORK KNOWN NETWORKS
Qualiers
NETWORK network-name
KNOWN NETWORKS
The name of a speci c network or al l of the network names to be removed from
the database. After you speci fy the NETWORK qual i er, you shoul d fol l ow i t
wi th one or more of these parameters:
ACCOUNT Removes user account access control i nformati on from the
database.
ALL Removes al l X25-ACCESS modul e parameters from the
database.
PASSWORD Removes the password access control i nformati on from the
database.
USER Removes the user i denti cati on from the access control
i nformati on i n the database.
Examples
1. NCP>CLEAR MODULE X25-ACCESS NETWORK TELENET1 ALL
Thi s command removes the network TELENET1 from the vol ati l e database
i n the l ocal node. The l ocal node can no l onger connect to X.25 network
TELENET1 through the connector node.
2. NCP>CLEAR MODULE X25-ACCESS NETWORK TELENET1 PASSWORD
Thi s command removes the password access control i nformati on for the
network TELENET1 from the vol ati l e database.
321
CLEAR/PURGE MODULE X25-PROTOCOL (Remote management only)
The CLEAR MODULE X25-PROTOCOL command removes the protocol
modul e component from the vol ati l e database or resets i ndi vi dual parameters.
(Parameters are reset to thei r defaul t val ues; the network val ues are speci ed
by the PROFI LE parameter of the SET MODULE X25-PROTOCOL command.)
The PURGE MODULE X25-PROTOCOL command removes the parameters of
the protocol modul e component from the permanent database. Note that the word
MODULE i s opti onal .
Use separate CLEAR or PURGE MODULE X25-PROTOCOL commands to cl ear
or purge the network, the DTE, or the group.
You may not be abl e to change the val ues of some of the network parameters.
(Refer to Public Network I nformation manual ).
Note
Format
CLEAR MODULE X25-PROTOCOL [qualier] parameter [...]
PURGE MODULE X25-PROTOCOL [qualier] parameter [...]
Qualiers
DTE KNOWN DTES
GROUP KNOWN GROUPS
Qualiers
DTE dte-address
KNOWN DTES
Removes parameters for the speci ed DTE or al l known DTEs i n the database. I f
you speci fy the DTE qual i er, you must associ ate wi th i t ei ther of the fol l owi ng
parameters.
NETWORK network-name Sel ects the DTE(s) speci ed on a parti cul ar
network. Wi th the PURGE command, you can
omi t the network part of the qual i er i f there
i s onl y one network dened.
KNOWN NETWORKS Sel ects the DTE(s) on al l known networks.
Addi ti onal l y, you must fol l ow the DTE qual i er wi th one or more of the fol l owi ng
parameters:
ALL Removes the speci ed DTE or al l known DTEs from
the database.
322
CALL TI MER Resets the cal l ti mer to i ts defaul t val ue i n the
database.
CLEAR TI MER Resets the cl ear ti mer to i ts defaul t val ue i n the
database.
COUNTER TI MER Removes the counter ti mer for the speci ed DTE or
al l known DTEs from the database.
DEFAULT DATA Resets the defaul t packet si ze to i ts defaul t val ue i n
the database.
DEFAULT WI NDOW Resets the defaul t wi ndow si ze to i ts defaul t val ue i n
the database.
I NTERRUPT TI MER Resets the i nterrupt ti mer to i ts defaul t val ue i n the
database.
MAXI MUM CI RCUI TS Resets the maxi mum number of vi rtual ci rcui ts
al l owed at once on the DTE to i ts defaul t val ue i n the
database.
MAXI MUM CLEARS Resets to the defaul t val ue i n the database the
maxi mum number of attempts to cl ear a ci rcui t.
MAXI MUM DATA Resets the maxi mum packet si ze to i ts defaul t val ue
i n the database.
MAXI MUM RESETS Resets to the defaul t val ue i n the database the
maxi mum number of attempts to reset a ci rcui t.
MAXI MUM RESTARTS Resets to the defaul t val ue i n the database the
maxi mum number of attempts to restart the DTE.
MAXI MUM WI NDOW Resets the maxi mum wi ndow si ze to i ts defaul t val ue
i n the database.
RESET TI MER Resets the reset ti mer to i ts defaul t val ue i n the
database.
RESTART TI MER Resets the restart ti mer to i ts defaul t val ue i n the
database.
GROUP group-name
KNOWN GROUPS
Removes parameters for the speci ed cl osed user group (CUG) or bi l ateral cl osed
user group (BCUG), or al l known groups, i n the database. I f you speci fy a group
qual i er, you must fol l ow i t wi th the fol l owi ng parameter:
ALL Removes al l parameters for the speci ed group or al l known groups.
KNOWN NETWORKS
Removes al l DTEs, groups, and parameters for the speci ed network or al l known
networks i n the database. You must speci fy the fol l owi ng parameter:
ALL Removes al l parameters for the network or networks.
323
Examples
1. NCP>CLEAR MODULE X25-PROTOCOL GROUP ESECUG ALL
Thi s command removes the cl osed user group ESECUG from the vol ati l e
database.
2. NCP>PURGE MODULE X25-PROTOCOL GROUP ESECUG ALL
Thi s command removes the parameters of the cl osed user group ESECUG
from the permanent database. When the system i s rebooted, the group no
l onger exi sts for VAX P.S.I .
3. NCP>CLEAR MODULE X25-PROTOCOL DTE 123789456 NETWORK PSS1 ALL
Thi s command removes the speci ed DTE bel ongi ng to the network PSS1
from the vol ati l e database.
4. NCP>PURGE MODULE X25-PROTOCOL DTE 123789456 KNOWN NETWORKS ALL
Thi s command removes al l parameter entri es for al l the DTEs of that DTE
number, for al l networks i n whi ch the DTE exi sts, from the permanent
database. When the network i s restarted, the DTE no l onger exi sts for VAX
P.S.I .
5. NCP>CLEAR MODULE X25-PROTOCOL ALL
Thi s command removes al l network, DTE, group, and X25-PROTOCOL
modul e parameters from the vol ati l e database.
6. NCP>CLEAR MODULE X25-PROTOCOL NETWORK PSS1 ALL
Thi s command removes al l DTEs and groups on network PSS1 and then
removes the network name i tsel f.
7. NCP>CLEAR MODULE X25-PROTOCOL KNOWN DTES -
_ KNOWN NETWORKS COUNTER TIMER
Thi s command removes the COUNTER TI MER parameter for al l DTEs on al l
networks from the vol ati l e database.
324
CLEAR/PURGE MODULE X25-SERVER/X29-SERVER (Remote management only)
CLEAR/PURGE MODULE X25-SERVER/X29-SERVER (Remote management
only)
The CLEAR MODULE X25-SERVER or CLEAR MODULE X29-SERVER
command resets or removes the X.25 or X.29 cal l handl er from the vol ati l e
database or removes i ndi vi dual parameters. The PURGE MODULE X25-
SERVER or PURGE MODULE X29-SERVER command removes the parameters
of the X.25 or X.29 cal l handl er from the permanent database.
Note
Format
CLEAR MODULE X25-SERVER [qualier]
parameter [...]
CLEAR MODULE X29-SERVER [qualier]
parameter [...]
PURGE MODULE X25-SERVER [qualier]
parameter [...]
PURGE MODULE X29-SERVER [qualier]
parameter [...]
Qualiers
DESTINATION KNOWN DESTINATIONS
Qualiers
DESTINATION dest-name
KNOWN DESTINATIONS
I denti es the desti nati on or al l known desti nati ons whose parameters are to be
reset or removed from the database. I f you speci fy a desti nati on qual i er, you
must fol l ow i t wi th one or more of the fol l owi ng parameters.
ACCOUNT Removes from the database the account for the
speci ed desti nati on or al l known desti nati ons.
ALL Removes from the database al l parameters for the
CALL MASK Removes from the database the cal l mask for the
CALL VALUE Removes from the database the cal l val ue for the
CALLED ADDRESS Removes from the database the cal l ed DTE address for
the speci ed desti nati on or al l known desti nati ons.
325
CLEAR/PURGE MODULE X25-SERVER/X29-SERVER (Remote management only)
EXTENSI ON MASK Removes from the database the extensi on mask for the
EXTENSI ON VALUE Removes from the database the extensi on val ue for the
GROUP Removes from the database the group name for the
I NCOMI NG ADDRESS Removes from the database the i ncomi ng address for
NETWORK Removes from the database the network name for the
OBJECT Removes from the database the object i denti cati on for
PASSWORD Removes from the database the password for the
PRI ORI TY Resets to the l owest val ue the pri ori ty for the speci ed
desti nati on or al l known desti nati ons.
RECEI VI NG DTE Removes from the database the recei vi ng DTE address
for the speci ed desti nati on or al l known desti nati ons.
REDI RECT REASON Removes from the database the redi rect reason code for
SENDI NG ADDRESS Removes from the database the sendi ng DTE address
for the speci ed desti nati on or al l known desti nati ons.
SUBADDRESSES Removes from the database the subaddress range for
USER Removes from the database the user i denti cati on for
Command Parameter
COUNTER TIMER
Resets the modul e counter ti mer to 0. Thi s i s the onl y parameter wi th whi ch you
are not requi red to suppl y a desti nati on qual i er.
Examples
1. NCP>CLEAR MODULE X25-SERVER KNOWN DESTINATIONS ALL
Thi s command removes al l X.25 desti nati ons from the vol ati l e database.
2. NCP>PURGE MODULE X25-SERVER KNOWN DESTINATIONS ALL
Thi s command removes al l parameters for al l X.25 desti nati ons from the
permanent database.
326
CLEAR/PURGE NODE
CLEAR/PURGE NODE
The CLEAR NODE command removes node parameters from the vol ati l e
database. The PURGE NODE command removes node parameters from the
permanent database on the l ocal node.
To remove a l oop node name from the database, use the CLEAR/PURGE NODE
node-i d command and speci fy ei ther the ALL parameter (wi th the l oop node name
or address as the node-i d), or the CI RCUI T parameter.
Format
CLEAR node-component parameter [...]
PURGE node-component parameter [...]
Node Components
NODE KNOWN NODES
Node Components
NODE node-id
I denti es the node (l ocal or remote) whose parameters are to be removed from
the database.
KNOWN NODES
Removes from the database the speci ed parameters for al l known nodes.
Command Parameters
ACCESS
Removes from the database the val ue for the ACCESS parameter.
ALL
Removes from the database al l parameters for the speci ed node or al l known
nodes. The component i s no l onger recogni zed by the network.
Caution
The PURGE KNOWN NODES ALL command purges both the executor
and remote node databases.
COUNTER TIMER
Removes the COUNTER TI MER val ue from the database.
CPU
Removes the nodes CPU i denti cati on from the database.
DIAGNOSTIC FILE
Removes from the database the i denti cati on of the downl i ne l oadi ng di agnosti cs
l e.
DUMP ADDRESS
Removes from the database the upl i ne dump address of the adjacent node.
327
CLEAR/PURGE NODE
DUMP COUNT
Removes the upl i ne dump count from the database.
DUMP FILE
Removes the upl i ne dump l e i denti cati on from the database.
HARDWARE ADDRESS
Removes from the database the hardware address that i s associ ated wi th a LAN
control l er that i s connected to the node.
HOST
Removes from the database the i denti cati on of the host node.
VAX
INBOUND (VAX only)
Appl i es onl y to nodes connected by DDCMP poi nt-to-poi nt ci rcui ts. Removes the
I NBOUND parameter from the database.
LOAD ASSIST AGENT
Removes from the database the i denti cati on of the i mage used to assi st i n
performi ng a downl i ne l oad. The LOAD ASSI ST AGENT appl i es onl y when the
target i s a VMScl uster satel l i te.
LOAD ASSIST PARAMETER
Removes from the database the val ue to be passed to the l oad assi st agent. The
LOAD ASSI ST PARAMETER val ue appl i es onl y when the target i s a VMScl uster
satel l i te.
LOAD FILE
Removes from the database the name of the l e to be downl i ne l oaded.
MANAGEMENT FILE
Removes from the database the i denti cati on of the downl i ne l oadi ng
management i nformati on l e.
NAME
Removes from the database the node name parameter for the node.
NONPRIVILEGED item
Removes the speci ed nonpri vi l eged access control i nformati on from the database.
ACCOUNT
PASSWORD
USER
PRIVILEGED item
Removes the speci ed pri vi l eged access control i nformati on from the database.
ACCOUNT
PASSWORD
USER
RECEIVE PASSWORD
Removes from the database the recei ve password expected from the remote node
duri ng a Routi ng i ni ti al i zati on sequence.
328
CLEAR/PURGE NODE
SECONDARY LOADER
Removes from the database the i denti cati on of the secondary downl i ne l oadi ng
l e.
SERVICE CIRCUIT
Removes from the database the ci rcui t name associ ated wi th the node for
downl i ne l oadi ng purposes.
SERVICE DEVICE
Removes the servi ce devi ce type from the database. See Appendi x A for a l i st of
the DECnet for OpenVMS ci rcui t and l i ne devi ces.
VAX
Onl y the synchronous port on the DMF may be used for servi ce operati ons.
SERVICE NODE VERSION
Removes from the database the software versi on number of the node to be
downl i ne l oaded.
SERVICE PASSWORD
Removes from the database the password requi red to tri gger the bootstrap
mechani sm of the node to be downl i ne l oaded.
SOFTWARE IDENTIFICATION
Removes the i denti cati on of the software from the database.
SOFTWARE TYPE
Removes the i ni ti al l oad software program type from the database.
TERTIARY LOADER
Removes from the database the i denti cati on of the terti ary downl i ne l oadi ng l e.
TRANSMIT PASSWORD
Removes from the database the transmi t password sent to the remote node
duri ng a Routi ng i ni ti al i zati on sequence.
329
CLEAR/PURGE NODE
Examples
1. NCP>CLEAR NODE TRNTO ALL
Thi s command removes al l parameter entri es for node TRNTO from the
vol ati l e database. As a resul t, the node no l onger exi sts i n the vol ati l e
database.
2. NCP>CLEAR NODE 14 NAME
.
.
.
NCP>SET NODE 15 NAME DENVER
The rst command di sassoci ates the name DENVER from node 1.14. The
second command associ ates the same name wi th node 1.15. I n si ngl e area
networks the defaul t area i s 1.
3. NCP>CLEAR NODE 5.14 NAME
.
.
.
NCP>SET NODE 5.15 NAME DENVER
The rst command di sassoci ates the name DENVER from node 5.14. The
second command associ ates the same name wi th node 5.15. Use thi s exampl e
i n pl ace of the previ ous exampl e when the network i s di vi ded i nto mul ti pl e
areas.
4. NCP>CLEAR NODE BOSTON RECEIVE PASSWORD
Thi s command removes the recei ve password from the record for the l ocal
node from the vol ati l e database.
5. NCP>CLEAR NODE 5.* NAME
Thi s command di sassoci ates the node names from thei r addresses for al l
nodes i n area 5.
330
CLEAR/PURGE NODE CIRCUIT
CLEAR/PURGE NODE CIRCUIT
The CLEAR NODE CI RCUI T command removes a l oop node from the vol ati l e
database. The PURGE NODE CI RCUI T command removes a l oop node from the
permanent database on the executor node.
Format
CLEAR node-component CIRCUIT
PURGE node-component CIRCUIT
Node Components
NODE KNOWN NODES
Node Components
NODE node-id
I denti es the l oop node to be removed from the database.
KNOWN NODES
I ndi cates that al l l oop nodes are to be removed from the database.
Examples
1. NCP>SET NODE TESTER CIRCUIT FZA-0
.
.
.
NCP>CLEAR NODE TESTER ALL
The rst command sets a l oop node for ci rcui t FZA0. The second command
removes the l oop node from the vol ati l e database.
331
CLEAR/PURGE OBJECT
CLEAR/PURGE OBJECT
The CLEAR OBJECT command removes object parameters from the vol ati l e
database on the l ocal node. The PURGE OBJECT command removes object
parameters from the permanent database.
Format
CLEAR object-component parameter [...]
PURGE object-component parameter [...]
Object Components
KNOWN OBJECTS OBJECT
Object Components
KNOWN OBJECTS
I ndi cates that parameters for al l known objects are to be removed from the
database.
OBJECT object-name
I denti es the object whose parameters are to be removed from the database.
Command Parameters
ACCOUNT
Removes the account access control i nformati on from the database.
ALIAS INCOMING
Removes the ALI AS I NCOMI NG parameter for the speci ed object or for al l
known objects from the database.
ALIAS OUTGOING
Removes the ALI AS OUTGOI NG parameter for the speci ed object or for al l
known objects from the database.
ALL
Removes al l parameters for the speci ed object or al l known objects from the
database. After you enter thi s parameter, the component i s no l onger recogni zed
by the network.
FILE
Removes the name of the objects startup command l e from the database.
OUTGOING CONNECT PRIVILEGES
Removes from the database the pri vi l eges requi red to make an outbound
connecti on to the object.
PASSWORD
Removes the password access control i nformati on from the database.
PRIVILEGES
Removes from the database the pri vi l eges requi red to access the object.
332
CLEAR/PURGE OBJECT
PROXY
Removes from the database the proxy access i nformati on for the object.
USER
Removes the user access control i nformati on from the database.
Examples
1. NCP>CLEAR OBJECT MYOBJ ALL
Thi s command removes al l parameter entri es for the object MYOBJ from
the vol ati l e database. Thi s command removes the object from the vol ati l e
database.
333
CONNECT NODE
CONNECT NODE
The CONNECT NODE command sets up a l ogi cal connecti on between the host
node and the consol e i nterface on a speci ed target node. Both the host node and
the target node must be on the same Ethernet or FDDI ci rcui t.
To dene i nformati on for the target node i n the database, use the NCP
command SET NODE to speci fy the ADDRESS, SERVI CE CI RCUI T, SERVI CE
PASSWORD, and HARDWARE ADDRESS parameters. Once you set these
parameters, you can overri de them by speci fyi ng new parameters i n the
CONNECT command.
Format
CONNECT node-component [parameter] [...]
Node Component
NODE
Node Component
NODE node-id
I denti es the node name or address of the target node to be connected to the l ocal
node.
Command Parameters
PHYSICAL ADDRESS p-address
Speci es the physi cal address of the target node. The val ue i s the physi cal
address that the target node has set for i tsel f or, i f the target node has not set a
physi cal address, the hardware address associ ated wi th the target nodes devi ce
control l er.
SERVICE PASSWORD hex-password
I denti es the password requi red to create the l i nk between the host node and the
target node. The password i s a 16-di gi t hexadeci mal number i n the range 0 to
FFFFFFFFFFFFFFFF.
VIA circuit-id
Speci es the ci rcui t to be used to create the l ogi cal l i nk between the host node
and the target node. Thi s ci rcui t must be an Ethernet or FDDI ci rcui t.
Examples
1. NCP>CONNECT NODE RTRDEV SERVICE PASSWORD FEFEFEFEFEFEFEFE -
_ VIA UNA-0 PHYSICAL ADDRESS AA-00-04-00-38-04
Thi s command connects the host node to the consol e i nterface on the target
node RTRDEV speci fyi ng the servi ce password FEFEFEFEFEFEFEFE, the
servi ce ci rcui t UNA0, and the physi cal address AA0004003804.
334
CONNECT VIA
CONNECT VIA
The CONNECT VI A command sets up a l ogi cal connecti on between the host
node and the consol e i nterface on a target node usi ng the speci ed ci rcui t. I f the
DECnet node address of the target node i s not known, use the CONNECT VI A
command i nstead of the CONNECT NODE command. Both the host node and the
target node must be on the same ci rcui t.
Format
CONNECT VIA circuit-id PHYSICAL ADDRESS p-address parameter
Command Parameters
Speci es the physi cal address of the target node. The val ue i s the physi cal
address that the target node has set for i tsel f. I f the target node has not set a
physi cal address, the val ue i s the hardware address associ ated wi th the nodes
control l er. Thi s parameter i s requi red.
I denti es the password requi red to create the l i nk between the host node and
the target node. The password i s a hexadeci mal number i n the range 0 to
FFFFFFFFFFFFFFFF.
Examples
1. NCP>CONNECT VIA UNA-0 PHYSICAL ADDRESS AA-00-04-00-38-00
Thi s command connects the host node to the consol e i nterface on the target
node by speci fyi ng the ci rcui t over whi ch the connecti on i s to be made and the
physi cal address of the target node.
335
COPY KNOWN NODES
COPY KNOWN NODES
The COPY KNOWN NODES command updates the node database on the l ocal
node. You can copy the vol ati l e or permanent node database from a remote node
to ei ther or both the vol ati l e and permanent node databases on the l ocal node.
You al so have the opti on of cl eari ng or purgi ng the node database on the l ocal
node before begi nni ng the copy operati on.
Onl y the node name and node address are copi ed. A node entry wi l l not be copi ed
i nto the node database i f a node wi th the same name or address al ready exi sts i n
the database.
You cannot use the TELL prex wi th the COPY KNOWN NODES command.
Format
COPY node-component parameter [qualier] [...]
Node Component
KNOWN NODES
Qualiers
USING WITH
TO
Node Component
KNOWN NODES
I ndi cates that names and addresses of al l known nodes stored i n the database of
the speci ed remote node are to be copi ed.
Command Parameter
FROM node-id
Speci es the remote node from whi ch node database i nformati on i s to be copi ed.
The remote node can be any node i n the network to whi ch you have access. The
word FROM i s opti onal .
Qualiers
USING option
Speci es the node database on the remote node from whi ch the i nformati on i s to
be copi ed. There are two possi bl e opti ons:
VOLATI LE I ndi cates that the vol ati l e database on the remote node i s to be
copi ed.
PERMANENT I ndi cates that the permanent database on the remote node i s to
be copi ed.
The defaul t i s VOLATI LE.
TO option
Speci es the node database on the l ocal node to whi ch the i nformati on i s to be
copi ed. There are three possi bl e opti ons:
336
COPY KNOWN NODES
VOLATI LE I ndi cates that the i nformati on i s to be copi ed to the vol ati l e
database on the l ocal node.
PERMANENT I ndi cates that the i nformati on i s to be copi ed to the permanent
database on the l ocal node.
BOTH I ndi cates that the i nformati on i s to be copi ed to both the vol ati l e
and permanent databases on the l ocal node.
The defaul t i s VOLATI LE.
WITH option
Cl ears or purges the node database on the l ocal node before the copy operati on i s
performed. Retai ns the executor node characteri sti cs and the name and address
of the remote node from whi ch the node i nformati on i s to be copi ed. The node
database to be cl eared or purged i s the l ocal database to whi ch the i nformati on
wi l l be copi ed. There are two opti ons:
CLEAR Cl ears the vol ati l e node database at the l ocal node.
PURGE Purges the permanent node database at the l ocal node.
Note that you can speci fy CLEAR or PURGE for ei ther database or for both
databases.
I f you do not speci fy the WI TH qual i er, the node entri es copi ed are added to the
exi sti ng node databases.
Examples
1. NCP>LIST KNOWN NODES
Known Node Permanent Summary as of 15-JUN-1992 13:50:20
Executor node = 2.20 (ROBIN)
State = on
Remote node = 2.21 (THRUSH)
No information available
Remote node = 2.22 (LARK)
NCP>TELL LARK LIST KNOWN NODES
Executor node = 2.22 (LARK)
State = on
Remote node = 2.20 (ROBIN)
Remote node = 2.23 (DOVE)
NCP>COPY KNOWN NODES FROM LARK USING PERMANENT -
_ TO PERMANENT WITH PURGE
337
COPY KNOWN NODES
%NCP-I-SUCCESS - Success
%NCP-I-RECDELET, Database entry deleted
NCP>LIST KNOWN NODES
State = on
Remote node = 2.23 (DOVE)
Thi s copy command copi es the node i nformati on from the permanent node
database on node LARK i nto the permanent node database on the l ocal node
(ROBI N). The node database i s purged before the copy operati on i s begun.
2. NCP>SHOW KNOWN NODES
Known Node Volatile Summary as of 15-JUN-1992 13:50:20
State = on
Identification = DECnet for OpenVMS
Active links = 2
Node State Active Delay Circuit Next node
Links
2.21 (THRUSH) QNA-0 2.19 (EGRET)
2.22 (LARK) QNA-0 2.19 (EGRET)
NCP>TELL LARK SHOW KNOWN NODES
Executor node = 2.22 (LARK)
State = on
Active links = 2
Links
2.20 (ROBIN) QNA-0 2.19 (EGRET)
2.23 (DOVE) QNA-0 2.19 (EGRET)
NCP>COPY KNOWN NODES FROM LARK
338
COPY KNOWN NODES
NCP>SHOW KNOWN NODES
State = on
Active links = 2
Links
2.21 (THRUSH) QNA-0 2.19 (EGRET)
2.22 (LARK) QNA-0 2.19 (EGRET)
2.23 (DOVE) QNA-0 2.19 (EGRET)
Thi s COPY command copi es the node i nformati on from the vol ati l e nodes
database on node LARK i nto the vol ati l e nodes database on the l ocal node
(ROBI N). I n thi s exampl e, the vol ati l e nodes database on the l ocal node i s not
cl eared before the copy operati on i s begun.
339
DISCONNECT LINK
DISCONNECT LINK
The DI SCONNECT LI NK command di sconnects the l ogi cal l i nks acti ve on the
l ocal node.
Format
DISCONNECT link-component [qualier]
Link Components
LINK KNOWN LINKS
Qualier
WITH NODE
Link Components
KNOWN LINKS
I ndi cates that al l l i nks are to be di sconnected.
LINK number
I denti es the parti cul ar l ogi cal l i nk to be di sconnected. Use the SHOW KNOWN
LI NKS command to di spl ay the acti ve l ogi cal l i nks.
Qualier
WITH NODE node-id
I denti es the node wi th whi ch al l l ogi cal l i nks are to be di sconnected. The node-
id i s ei ther a node name or a node address. You can use thi s command verb onl y
wi th the KNOWN LI NKS component.
Examples
1. NCP>SHOW KNOWN LINKS
Known Link Volatile Summary as of 15-JUN-1992 15:53:42
Link Node PID Process Remote link Remote user
4104 11.9 (DALLAS) 20600090 GRAY 3116 MAIL
8229 3.5 (TRNTO) 2060014C DAVIS 7217 NML
3125 2.17 (NYC) 2060023D REMACP 5175 THOMPSON_1
NCP>DISCONNECT KNOWN LINKS WITH NODE DALLAS
The rst command, SHOW KNOWN LI NKS, di spl ays the l i nk addresses. The
second command di sconnects al l known l i nks to remote node DALLAS.
340
DISCONNECT LINK
2. NCP>SET EXECUTOR NODE DENVER
.
.
.
NCP>DISCONNECT KNOWN LINKS
The rst command sets the executor node to DENVER. The DI SCONNECT
KNOWN LI NKS command di sconnects the l i nk to node DENVER. As a resul t,
you must ei ther enter the SET EXECUTOR NODE command agai n, or you
must enter the CLEAR EXECUTOR NODE command to reestabl i sh the l ocal
node as executor.
341
HELP
HELP
The HELP command di spl ays general i nformati on about NCP commands and
parameters. See Secti on 1.5 for more i nformati on about the NCP HELP Faci l i ty.
Format
HELP [topic...]
Command Parameter
topic
Speci es one or more NCP keywords that refer to a topi c or subtopi c on whi ch
you can obtai n i nformati on from the NCP hel p l i brary. I nformati on i n the NCP
hel p l i brary i s organi zed i n a hi erarchi al manner, i n topi cs and subtopi cs. You
can speci fy up to ei ght topi cs and subtopi cs, separated by spaces.
Examples
1. NCP>HELP
CLEAR Commands CONNECT COPY DEFINE DISCONNECT EVENTS
EXIT HELP LIST LOAD LOOP PARAMETERS Prompting
PURGE SET SHOW TELL TRIGGER ZERO
Topic?
Thi s command di spl ays al l command verbs for whi ch further i nformati on
exi sts.
2. NCP>HELP CLEAR CIRCUIT
CLEAR
CIRCUIT
The CLEAR CIRCUIT command resets circuit parameters in the
volatile database to the default value (if any), or
removes them from the volatile database on the local node or DTE.
The PURGE CIRCUIT command always removes circuit parameters from
the permanent database on the local node or DTE.
CLEAR KNOWN CIRCUITS (parameters...)
CIRCUIT circuit-id
Additional information available:
KNOWN CIRCUITS CIRCUIT circuit-id ACTIVE BASE
ACTIVE INCREMENT ALL BABBLE TIMER COUNTER TIMER
DEAD THRESHOLD DYING BASE DYING INCREMENT DYING THRESHOLD
INACTIVE BASE INACTIVE INCREMENT INACTIVE THRESHOLD
MAXIMUM BUFFERS MAXIMUM RECALLS MAXIMUM ROUTERS
MAXIMUM TRANSMITS NETWORK RECALL TIMER ROUTER PRIORITY
TRANSMIT TIMER Examples
Thi s command provi des a descri pti on of the NCP command CLEAR CI RCUI T
and di spl ays command words for whi ch further i nformati on exi sts.
342
HELP
3. NCP>HELP SHOW
SHOW
Use the SHOW command to display information from the volatile database
on the executor node. Use the LIST command to display information
from the permanent database on the executor node.
Additional information available:
CHARACTERISTICS COUNTERS EVENTS STATUS SUMMARY
TO file-id AREA CIRCUIT EXECUTOR LINE LINKS LOGGING
MODULE NODE OBJECT
Thi s command provi des a descri pti on of the NCP command SHOW and
di spl ays command words for whi ch further i nformati on exi sts.
343
LOAD NODE
LOAD NODE
The LOAD NODE command downl i ne l oads software to a target node, usi ng
ei ther the i denti ed ci rcui t (i f speci ed) or the ci rcui t obtai ned from the vol ati l e
database. Any parameter l eft unspeci ed i n the command defaul ts to whatever
entry i s speci ed i n the vol ati l e node database on the executor node.
Format
LOAD node-component parameter [...]
Node Component
NODE
Node Component
NODE node-id
I denti es the node name or address of the target node to be downl i ne l oaded.
Command Parameters
ADDRESS node-address
I denti es the address that the target node i s to use (when i t comes up).
CPU cpu-type
I denti es the nodes CPU type. There are four possi bi l i ti es:
DECSYSTEM1020
PDP11
PDP8
VAX
FROM lespec
I denti es the l e speci cati on of the l oad l e contai ni ng the system software to
be downl i ne l oaded.
HOST node-id
I denti es the defaul t host that the target node i s to use (when i t comes up).
LOAD ASSIST AGENT lespec
Speci es the i mage that denes the system software to be downl i ne l oaded to the
target node. The l oad assi st agent can be used to tai l or the system software to be
l oaded. The LOAD ASSI ST AGENT parameter appl i es onl y when the target i s a
VMScl uster satel l i te.
LOAD ASSIST PARAMETER item
Speci es a parameter to be passed to a l oad assi st agent. The LOAD ASSI ST
PARAMETER val ue appl i es onl y when the target i s a VMScl uster satel l i te.
MANAGEMENT FILE lespec
Speci es a l e contai ni ng the management i nformati on to be downl i ne l oaded to
the target node.
NAME node-name
I denti es the name that the target node i s to use (when i t comes up).
344
LOAD NODE
Appl i es onl y to nodes on Ethernet or FDDI ci rcui ts. Speci es the address that
the target node to be downl i ne l oaded currentl y uses to i denti fy i tsel f. The val ue
i s the physi cal address that the target node has set for i tsel f or, i f the target node
has not set a physi cal address, the hardware address associ ated wi th the target
nodes devi ce control l er.
SECONDARY LOADER lespec
I denti es the l e speci cati on of a secondary l oad l e contai ni ng the software to
SERVICE DEVICE device-type (VAX only)
I denti es the target nodes l i ne control l er for the servi ce l i ne over whi ch the
operati on i s to take pl ace. See Appendi x A for a l i st of the DECnet for OpenVMS
ci rcui t and l i ne devi ces and what they support.
VAX
Onl y the synchronous port on the DMF servi ce devi ce may be used for servi ce
operati ons.
I denti es the password requi red to tri gger the bootstrap mechani sm on the target
node. The password i s a hexadeci mal number. For FDDI or Ethernet ci rcui ts, the
number i s i n the range 0 to FFFFFFFFFFFFFFFF.
VAX
For DDCMP ci rcui ts, the number i s i n the range 0 to FFFFFFFF.
SOFTWARE IDENTIFICATION software-id
I denti es the name of the software to be downl i ne l oaded.
SOFTWARE TYPE software-type
I denti es the parti cul ar l e type to be l oaded rst. There are four possi bi l i ti es:
MANAGEMENT FI LE
SECONDARY LOADER
SYSTEM
TERTI ARY LOADER
TERTIARY LOADER lespec
I denti es the l e speci cati on of a terti ary l oad l e contai ni ng the software to be
downl i ne l oaded.
VIA circuit-id
I denti es a ci rcui t over whi ch the l oadi ng sequence i s to take pl ace.
345
LOAD NODE
Examples
1. NCP>LOAD NODE NYC HOST BOSTON VIA FZA-1
Thi s command i ni ti ates a downl i ne l oad operati on for node NYC over ci rcui t
FZA-1. When l oaded, node NYC has node BOSTON as i ts defaul t host
speci cati on.
2. NCP>LOAD NODE BANGOR
Thi s command i ni ti ates a downl i ne l oad operati on for node BANGOR. Any
requi red defaul t i nformati on i s retri eved from the vol ati l e database on the
executor node.
3. NCP>LOAD NODE SWIFT PHYSICAL ADDRESS AA-00-04-00-07-04
Thi s command i ni ti ates a downl i ne l oad operati on for node SWI FT on an
Ethernet ci rcui t. The executor node uses the physi cal address speci ed i n the
command to address node SWI FT.
346
LOAD VIA
LOAD VIA
The LOAD VI A command downl i ne l oads software to a target node over the
speci ed ci rcui t. The target node i denti cati on that i s associ ated wi th the
servi ce ci rcui t i s obtai ned from the vol ati l e database on the executor node. I f the
target node i s on an Ethernet or FDDI ci rcui t, you must speci fy the PHYSI CAL
ADDRESS parameter i n thi s command.
Format
LOAD VIA circuit-id parameter [...]
Command Parameters
I denti es the address that the target node i s to use (when i t comes up).
CPU cpu-type
DECSYSTEM1020
PDP11
PDP8
VAX
FROM lespec
I denti es the l e speci cati on of the l oad l e contai ni ng the system software to
HOST node-id
I denti es the defaul t host that the target node i s to use (when i t comes up).
Speci es the i mage that denes the system software to be downl i ne l oaded to the
target node. The l oad assi st agent can be used to tai l or the system software to be
l oaded. The LOAD ASSI ST AGENT parameter appl i es onl y when the target i s a
VMScl uster satel l i te.
PARAMETER val ue appl i es appl i es onl y when the target i s a VMScl uster
satel l i te.
the target node.
NAME node-name
I denti es the name that the target node i s to use (when i t comes up).
Appl i es onl y to nodes on Ethernet or FDDI ci rcui ts. Speci es the physi cal address
that the target node to be downl i ne l oaded currentl y uses to i denti fy i tsel f. The
val ue i s the address that the target node has set for i tsel f, or, i f the target node
has not set a physi cal address, the hardware address associ ated wi th the target
nodes devi ce control l er.
347
LOAD VIA
I denti es the l e speci cati on of a secondary l oad l e contai ni ng the software to
SERVICE DEVICE device-type (VAX only)
operati on i s to take pl ace. See Appendi x A for a l i st of the DECnet for OpenVMS
VAX
Onl y the synchronous port on the DMF servi ce devi ce may be used for servi ce
operati ons.
node. The password i s a hexadeci mal number. For Ethernet or FDDI ci rcui ts, i t
i s i n the range 0 to FFFFFFFFFFFFFFFF.
VAX
For DDCMP ci rcui ts, i t i s i n the range 0 to FFFFFFFF.
I denti es the name of the software to be downl i ne l oaded.
I denti es the parti cul ar l e type to be l oaded rst. There are four possi bi l i ti es:
MANAGEMENT FI LE
SECONDARY LOADER
SYSTEM
TERTI ARY LOADER
I denti es the l e speci cati on of a terti ary l oad l e contai ni ng the software to be
downl i ne l oaded.
Examples
VAX
1.
NCP>LOAD VIA DMP-0.4
Thi s command i ni ti ates a downl i ne l oad operati on over ci rcui t DMP-0.4. Any
requi red defaul t i nformati on i s retri eved from the vol ati l e database on the
executor node. The node database i s scanned unti l a node i s found whose
servi ce ci rcui t matches the l oad ci rcui t.
2. NCP>LOAD VIA DMC-0 SOFTWARE TYPE SECONDARY LOADER
Thi s command i ni ti ates a downl i ne l oad operati on over ci rcui t DMC0,
commenci ng wi th the secondary l oader l e.
3. NCP>LOAD VIA SVA-0 PHYSICAL ADDRESS AA-00-04-00-07-04
Thi s command i ni ti ates a downl i ne l oad operati on over Ethernet ci rcui t
SVA0, to the target node whose physi cal address i s speci ed i n the command.
348
LOOP CIRCUIT
LOOP CIRCUIT
The LOOP CI RCUI T command tests a ci rcui t by transmi tti ng test bl ocks of data
over a speci ed ci rcui t. The parameters are opti onal and can be entered i n any
order.
Format
LOOP circuit-component [parameter] [...]
Circuit Component
CIRCUIT
Circuit Component
CIRCUIT circuit-id
I denti es the ci rcui t for l oopback testi ng.
Command Parameters
ASSISTANT NODE node-id
Appl i es onl y to Ethernet and FDDI ci rcui ts. I denti es the name or the address of
the node that i s to perform the rol e of l oopback assi stant for thi rd-party l oopback
testi ng.
ASSISTANT PHYSICAL ADDRESS p-address
Appl i es onl y to Ethernet and FDDI ci rcui ts. I denti es the physi cal address of
the node that i s to perform the rol e of l oopback assi stant for thi rd-party l oopback
testi ng. I f the HELP parameter i s i ncl uded i n thi s command, you must speci fy
ASSI STANT PHYSI CAL ADDRESS. The address cannot be a mul ti cast address.
COUNT number
Speci es the number of bl ocks to be sent duri ng l oopback testi ng over the ci rcui t.
The number must be a deci mal i nteger i n the range of 1 through 65,535. I f you
omi t thi s parameter, onl y one bl ock i s l ooped.
HELP help-type
Appl i es onl y to Ethernet and FDDI ci rcui ts. I ndi cates the type of assi stance
to be provi ded duri ng l oopback testi ng by the assi stant node, whose address i s
speci ed i n the ASSI STANT PHYSI CAL ADDRESS or node-id as speci ed i n the
ASSI STANT NODE parameter. There are three possi bl e val ues for help-type.
FULL The assi stant node rel ays the request and the repl y between the
executor node and the desti nati on node.
RECEI VE The executor node sends the request di rectl y to the desti nati on
node, whi ch rel ays the repl y to the assi stant node for transmi ssi on
to the executor node.
TRANSMI T The assi stant node rel ays the request to the desti nati on node,
whi ch repl i es di rectl y to the executor node.
I f you speci fy the HELP parameter, you must al so speci fy the ASSI STANT
PHYSI CAL ADDRESS or ASSI STANT NODE parameter.
349
LOOP CIRCUIT
LENGTH number
Speci es the l ength (i n bytes) of the bl ocks to be sent duri ng l oopback testi ng.
The l ength must be a deci mal i nteger i n the range of 1 through 4096. I f you omi t
thi s parameter, a bl ock l ength of 4096 bytes i s used.
For further i nformati on on i ncreasi ng the l oop l ength, refer to the descri pti on of
the MI RROR$SI ZE l ogi cal i n the DECnet for OpenVMS Networking Manual.
VAX
The LENGTH parameter must be l ess than 50 for the DMC11 ci rcui t operati ng
i n ei ther control l er l oopback mode or cabl e l oopback (a DMC11 wi th an attached
l oopback cabl e).
NODE node-id
Appl i es onl y to Ethernet and FDDI ci rcui ts. I denti es the desti nati on node to
be used for l oopback testi ng of the speci ed broadcast ci rcui t. You can use thi s
parameter i nstead of the PHYSI CAL ADDRESS parameter.
Appl i es onl y to Ethernet and FDDI ci rcui ts. I denti es the physi cal address of the
desti nati on node to be used for l oopback testi ng of the speci ed broadcast ci rcui t.
WITH data-type
Speci es the type of bi nary i nformati on to be sent duri ng testi ng. I f you omi t thi s
parameter, a combi nati on of ones and zeros (the MI XED data type) i s sent. There
are three types of data:
MI XED
ONES
ZEROS
Examples
VAX
1.
NCP>LOOP CIRCUIT DMB-0 COUNT 5 LENGTH 20
Thi s command i ni ti ates a ci rcui t-l evel l oopback test over ci rcui t DMB0.
The software l oops ve messages, 20 bytes i n l ength wi th mi xed bi nary
i nformati on.
2. NCP>LOOP CIRCUIT SVA-0 PHYSICAL ADDRESS AA-00-04-00-FF-04
Thi s command i ni ti ates a ci rcui t-l evel l oopback test wi th a node whose
physi cal address i s AA000400FF04.
3. NCP>LOOP CIRCUIT SVA-0 NODE 224
Thi s command i ni ti ates a ci rcui t-l evel l oopback test wi th a node whose
address i s 1.224. I n thi s exampl e, the NODE parameter wi th a node-id val ue
of 1.224 i s used i n pl ace of the PHYSI CAL ADDRESS parameter. I n si ngl e
area networks the defaul t area i s 1.
4. NCP>LOOP CIRCUIT SVA-0 PHYSICAL ADDRESS -
_ AA-00-04-00-12-04 ASSISTANT NODE GULL HELP RECEIVE
Thi s command i ni ti ates a ci rcui t-l evel l oopback test by transmi tti ng a
message di rectl y to a node whose physi cal address i s AA0004001204.
Addi ti onal l y, the command requests the assi stance of an Ethernet node
named GULL to recei ve the message from the target node and then rel ay the
message back.
350
LOOP EXECUTOR
LOOP EXECUTOR
The LOOP EXECUTOR command tests the executor node by causi ng test data
to be transmi tted to the executor node. The parameters are opti onal and can be
entered i n any order. You can suppl y expl i ci t access control i nformati on for the
LOOP EXECUTOR command.
Format
LOOP EXECUTOR [parameter] [...]
Command Parameters
ACCOUNT account
I denti es the user s account for access control veri cati on for the executor node.
COUNT number
Speci es the number of bl ocks to be sent duri ng l oopback testi ng over the
executor node. The number must be a deci mal i nteger i n the range of 1 through
65,535. I f you omi t thi s parameter, onl y one bl ock i s l ooped.
LENGTH number
PASSWORD password
I denti es the user s password for access control veri cati on for the executor node.
USER user-id
Speci es the user s i denti cati on for access control veri cati on for the executor
node.
WITH data-type
MI XED
ONES
ZEROS
Examples
1. NCP>LOOP EXECUTOR
Thi s command i ni ti ates a l oopback test on the executor node.
351
LOOP LINE (Remote management only)
The LOOP LI NE command i ni ti ates l oopback tests of X.25 l i nes onl y. The
parameters are opti onal and can be entered i n any order. Before begi nni ng
l oopback testi ng of an X.25 l i ne, use the SET LI NE command to set the STATE
SERVI CE and CONTROLLER LOOPBACK parameters for i nternal l oopback
testi ng or the STATE SERVI CE and CONTROLLER NORMAL parameters for al l
other l oopback testi ng.
Note
Format
LOOP line-component [parameter] [...]
Line Component
LINE
Line Component
LINE line-id
Appl i es onl y to VAX P.S.I . I denti es the X.25 l i ne for l oopback testi ng. Speci fy a
l i ne name usi ng the dev-c-u format for the line-id.
Command Parameters
COUNT number
Speci es the number of bl ocks to be sent duri ng l oopback testi ng over the l i ne.
The number must be a deci mal i nteger i n the range of 1 through 65,535. I f you
omi t thi s parameter, onl y one bl ock i s l ooped.
LENGTH number
WITH data-type
MI XED
ONES
ZEROS
352
Examples
1. NCP>LOOP LINE DUP-0
Thi s command i ni ti ates a l i ne-l evel l oopback test over X.25 l i ne DUP0.
The software l oops one message, 4096 bytes i n l ength, wi th mi xed bi nary
i nformati on.
2. NCP>LOOP LINE DUP-1 COUNT 10 WITH ONES
Thi s command i ni ti ates a l i ne-l evel l oopback test over X.25 l i ne DUP1.
The software l oops 10 messages, 4096 bytes i n l ength, wi th al l bi nary ones
i nformati on.
353
LOOP NODE
LOOP NODE
The LOOP NODE command tests a speci ed node i n the network by causi ng test
bl ocks of data to be transmi tted to the node and then l ooped back to the executor.
The parameters are opti onal and can be entered i n any order. You can suppl y
expl i ci t access control i nformati on for the LOOP NODE command.
To test the executor node, use the LOOP EXECUTOR command.
Format
LOOP node-component [parameter] [...]
Node Component
NODE
Node Component
NODE node-id
I denti es the node on whi ch the l oopback mi rror i s to run.
Command Parameters
ACCOUNT account
I denti es the user s account for access control veri cati on on the desi gnated node.
COUNT number
Speci es the number of bl ocks to be sent duri ng the l oopback test wi th the remote
node. The number must be a deci mal i nteger i n the range of 1 through 65,535. I f
you omi t thi s parameter, onl y one bl ock i s l ooped.
LENGTH number
VAX
The LENGTH parameter must be l ess than 50 for the DMC11 ci rcui t operati ng
i n ei ther control l er l oopback mode or cabl e l oopback (a DMC11 wi th an attached
l oopback cabl e).
PASSWORD password
I denti es the user s password for access control veri cati on on the desi gnated
node.
USER user-id
Speci es the user s i denti cati on for access control veri cati on on the desi gnated
node.
354
LOOP NODE
WITH data-type
MI XED
ONES
ZEROS
Examples
NCP>LOOP NODE TESTER
.
.
.
NCP>CLEAR NODE TESTER ALL
The rst command creates a l oop node name, TESTER, for the associ ated
ci rcui t. The second command i ni ti ates a node-l evel l oopback test wi th the l oop
node. The thi rd command removes the l oop node from the vol ati l e database
when the l oop test i s compl eted.
355
SET CIRCUIT ALL
SET CIRCUIT ALL
The SET CI RCUI T ALL command updates the vol ati l e copy of the database on
the l ocal node wi th al l the ci rcui t parameters stored for a parti cul ar ci rcui t or for
al l known ci rcui ts i n the permanent database on the l ocal node.
Format
SET circuit-component ALL
Circuit Components
Circuit Components
CIRCUIT circuit-id
Updates the parameters for a speci c ci rcui t.
KNOWN CIRCUITS
Updates al l parameters for al l known ci rcui ts.
Examples
1. NCP>SET KNOWN CIRCUITS ALL
Thi s command l oads al l permanent database entri es stored for al l known
ci rcui ts i nto the vol ati l e database.
356
SET/DEFINE CIRCUIT
SET/DEFINE CIRCUIT
The SET CI RCUI T command creates or modi es ci rcui t parameters i n the
vol ati l e database. The DEFI NE CI RCUI T command creates or modi es ci rcui t
parameters i n the permanent database. Most parameters cannot be SET whi l e
the ci rcui t i s i n the ON state. Excepti ons to thi s are the COST, COUNTER
TI MER, HELLO TI MER, MAXI MUM ROUTERS, STATE, and TRANSMI T
TI MER parameters. These parameters can be changed whi l e the ci rcui t i s i n the
ON state.
Format
SET circuit-component parameter [...]
DEFINE circuit-component parameter [...]
Circuit Components
Circuit Components
CIRCUIT circuit-id
I denti es the ci rcui t whose parameters are to be updated.
KNOWN CIRCUITS
I ndi cates that parameters for al l known ci rcui ts are to be updated.
Command Parameters
ACTIVE BASE base (VAX only)
VAX
Appl i es onl y to DDCMP CONTROL ci rcui ts. Sets the base pri ori ty of an ACTI VE
tri butary after the tri butary has been pol l ed. You can set a separate base for each
of the i ndi cated pol l i ng states. The base val ue must be a deci mal i nteger from 0
to 255. The defaul t i s 255.
ACTIVE INCREMENT increment (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Sets the i ncrement val ue added
to the ACTI VE tri butary pri ori ty each ti me the schedul i ng ti mer expi res. The
increment val ue must be a deci mal i nteger from 0 to 255. The defaul t i s 0.
BABBLE TIMER milliseconds (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Represents the number of
mi l l i seconds that a sel ected tri butary or remote hal f-dupl ex stati on i s al l owed
to transmi t. The milliseconds val ue must be a deci mal i nteger i n the range 1 to
65,535. The defaul t i s 6000 (6 seconds).
CHANNEL number (Remote management only)
Appl i es onl y to X.25 and DLM permanent vi rtual ci rcui ts (PVCs). I denti es the
l ogi cal channel number for the X.25 PVCs. Speci fy a val ue i n the range 1 to 4095.
When you speci fy an X.25 PVC or a DLM PVC for the rst ti me, thi s parameter
i s mandatory.
COST cost
Does not appl y to X.25 PVCs. Speci es the routi ng cost of the ci rcui t. Messages
travel between nodes al ong the path wi th the smal l est total cost. The cost val ue
must be a deci mal i nteger i n the range 1 to 63. The defaul t i s 10.
357
SET/DEFINE CIRCUIT
COUNTER TIMER seconds
Speci es the number of seconds that the ci rcui t counter ti mer wi l l run. When
the counter ti mer expi res, a ci rcui t counter l oggi ng event occurs. The seconds
val ue must be a deci mal i nteger i n the range 0 to 65,535. I f no val ue i s set for
COUNTER TI MER, the ci rcui t counters are not l ogged automati cal l y.
VAX
DEAD THRESHOLD number (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Denes the number of ti mes to pol l
the acti ve, i nacti ve, or dyi ng tri butary before changi ng that tri butarys pol l i ng
state to DEAD because of recei ve ti meouts. The number val ue must be a deci mal
i nteger i n the range 0 to 255. The defaul t i s 8.
DTE dte-address (Remote management only)
Appl i es onl y to X.25 PVCs and DLM ci rcui ts. I denti es the l ocal DTE for the
ci rcui t. Speci fy a deci mal i nteger of 1 to 15 di gi ts. See the Public Network
I nformation manual for the format of the address on your network. Thi s
parameter i s opti onal for DLM swi tched vi rtual ci rcui ts (SVCs) and mandatory
when you speci fy an X.25 PVC or DLM PVC for the rst ti me.
VAX
DYING BASE base (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Sets the base pri ori ty of a DYI NG
of the pol l i ng state parameters. The baseval ue must be a deci mal i nteger from 0
DYING INCREMENT increment (VAX only)
to the DYI NG tri butary pri ori ty each ti me the schedul i ng ti mer expi res. The
DYING THRESHOLD number (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Speci es the number of ti mes to pol l
the acti ve or i nacti ve tri butary before changi ng that tri butarys pol l i ng state to
dyi ng because of recei ve ti meouts. The count val ue must be a deci mal i nteger i n
the range 0 to 255. The defaul t i s 2.
HELLO TIMER seconds
Speci es the frequency of Routi ng Hel l o messages sent to adjacent nodes on the
ci rcui t. The seconds val ue must be a deci mal i nteger i n the range 0 to 8191. The
defaul t i s 15. The val ue of the read-onl y ci rcui t parameter LI STEN TI MER i s
three ti mes the val ue of the HELLO TI MER parameter. Does not appl y to X.25
PVCs.
VAX
INACTIVE BASE base (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Sets the base pri ori ty of an i nacti ve
of the i ndi cated pol l i ng states. The baseval ue must be a deci mal i nteger from 0
INACTIVE INCREMENT increment (VAX only)
to the i nacti ve tri butary pri ori ty each ti me the schedul i ng ti mer expi res. The
358
SET/DEFINE CIRCUIT
INACTIVE THRESHOLD number (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Speci es the number of ti mes to
pol l the acti ve tri butary before changi ng that tri butarys pol l i ng state to i nacti ve
because of no data response. The number val ue must be a deci mal i nteger i n the
range 0 to 255. The defaul t i s 8.
MAXIMUM BUFFERS number (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Speci es the maxi mum number of
buffers from a common buffer pool that the tri butary can use. I f you do not set
thi s parameter, there i s no common buffer pool and the hi gher l evel wi l l expl i ci tl y
suppl y the buffers. The number val ue must be a deci mal i nteger up to 254 or the
word UNLI MI TED.
MAXIMUM DATA number (Remote management only)
Appl i es onl y to X.25 PVCs and DLM ci rcui ts. Speci es the maxi mum packet si ze
for the X.25 ci rcui t. Thi s val ue must be at l east 5 bytes l ess than the MAXI MUM
BLOCK val ue that you speci fy i n the SET or DEFI NE LI NE command and must
be a power of 2. Speci fy a val ue i n the range 16 to 4096 bytes. By defaul t, the
packet size takes the val ue speci ed by the PROFI LE parameter of the SET
or DEFI NE MODULE X25-PROTOCOL command. See the Public Network
I nformation manual for the network val ue of thi s parameter.
MAXIMUM RECALLS number (Remote management only)
Appl i es onl y to DLM outgoi ng swi tched vi rtual ci rcui ts (SVCs). Speci es the
maxi mum number of cal l retri es generated on an outgoi ng DLM ci rcui t before the
ci rcui t i s decl ared nonoperati onal . The range of possi bl e val ues for MAXI MUM
RECALLS i s 0 to 255. A number val ue of 0 speci es an i nni te number of cal l
retri es. The defaul t i s 100.
MAXIMUM ROUTERS number
Appl i es onl y to Ethernet and FDDI ci rcui ts. Speci es the maxi mum number of
routers (i ncl udi ng the executor node) al l owed by the Routi ng l ayer on thi s ci rcui t.
Use a number i n the range 1 to 33. The defaul t i s 33.
VAX
MAXIMUM TRANSMITS number (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Speci es the maxi mum number of
data messages that can be transmi tted at one ti me. The number val ue must be a
deci mal i nteger i n the range 1 to 255. The defaul t i s 4.
MAXIMUM WINDOW number (Remote management only)
Appl i es onl y to X.25 PVCs and DLM ci rcui ts. Speci es the maxi mum wi ndow si ze
al l owed for the X.25 ci rcui tthat i s, the maxi mum number of packets for whi ch
outstandi ng acknowl edgments are al l owed. Speci fy a val ue i n the range 1 to 127.
By defaul t, window sizetakes the val ue speci ed by the PROFI LE parameter
of the SET or DEFI NE MODULE X25-PROTOCOL command. See the Public
Network I nformation manual for the network val ue of thi s parameter.
NETWORK network-name (Remote management only)
Appl i es onl y to X.25 PVCs and DLM ci rcui ts. Speci es the network that the
ci rcui t runs through. I f onl y one network i s set up, thi s parameter i s not
requi red. Otherwi se, the parameter i s mandatory.
NUMBER dte-address (Remote management only)
Appl i es onl y to DLM swi tched vi rtual ci rcui ts. For outgoi ng ci rcui ts, speci es
the remote DTE address and subaddress that thi s DLM ci rcui t wi l l cal l . For
i ncomi ng ci rcui ts, speci es the address of the remote DTE from whi ch thi s ci rcui t
359
SET/DEFINE CIRCUIT
wi l l accept cal l s. I f the NUMBER parameter i s not speci ed for an i ncomi ng
ci rcui t, a cal l from any remote DTE can be di rected to thi s ci rcui t. Speci fy a
deci mal i nteger of 1 to 15 di gi ts.
OWNER EXECUTOR (Remote management only)
Appl i es onl y to DLM ci rcui ts. I denti es the ci rcui t owner as the executor. Thi s
parameter i s mandatory for a DLM ci rcui t.
VAX
POLLING STATE polling-state (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. I denti es the mul ti poi nt pol l i ng
state of the tri butary. There are ve possi bl e states:
ACTI VE The tri butary i s l ocked i n the ACTI VE state.
AUTOMATI C The tri butarys state vari es accordi ng to the operati on of the
pol l i ng al gori thm. Thi s i s the defaul t.
DEAD The tri butary i s l ocked i n the DEAD state.
DYI NG The tri butary i s l ocked i n the DYI NG state.
I NACTI VE The tri butary i s l ocked i n the I NACTI VE state.
RECALL TIMER seconds (Remote management only)
Appl i es onl y to outgoi ng DLM swi tched vi rtual ci rcui ts (SVCs). Sets a ti mer
whose expi rati on causes a remote DTE to be cal l ed agai n duri ng an attempt to
set up a DLM ci rcui t. Speci fy a deci mal i nteger up to a maxi mum of 65,535.
ROUTER PRIORITY number
Appl i es onl y to Ethernet and FDDI ci rcui ts. Speci es the pri ori ty thi s router (the
executor node on thi s ci rcui t) i s to have i n the sel ecti on of a desi gnated router for
thi s ci rcui t. Use a val ue i n the range 0 to 127. The defaul t i s 64.
SERVICE service-mode
Speci es whether servi ce operati ons (l oadi ng and l oop testi ng) are al l owed for the
ci rcui t. Does not appl y to X.25 ci rcui ts.
There are two possi bl e modes:
DI SABLED The ci rcui t cannot be put i nto servi ce state and cannot perform
servi ce functi ons. The defaul t mode i s DI SABLED.
ENABLED The ci rcui t can be put i nto servi ce state and perform servi ce
functi ons.
STATE circuit-state
Speci es the ci rcui ts operati onal state. There are three possi bl e states:
OFF The ci rcui t i s not i n use.
ON The ci rcui t i s avai l abl e for normal use or servi ce functi ons.
SERVI CE The ci rcui t i s avai l abl e for servi ce functi ons onl y.
VAX
TRANSMIT TIMER milliseconds (VAX only)
Appl i es to DDCMP ci rcui ts. Denes the number of mi l l i seconds to del ay between
data message transmi ts. The milliseconds val ue must be a deci mal i nteger up to
65,535. The defaul t i s 0.
TRIBUTARY tributary-address (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Denes the data l i nk physi cal
tri butary address of the ci rcui t. The tributary-address val ue must be a deci mal
i nteger up to 255.
360
SET/DEFINE CIRCUIT
TYPE X25 (Remote management only)
Appl i es onl y to X.25 ci rcui ts. Speci es the type of ci rcui t.
USAGE usage-type (Remote management only)
Appl i es onl y to X.25 ci rcui ts. Denes the usage type of an X.25 vi rtual ci rcui t.
There are three possi bl e usage types:
I NCOMI NG Appl i es onl y to DLM swi tched vi rtual ci rcui ts (SVCs). The
ci rcui t i s used onl y for i ncomi ng cal l s.
OUTGOI NG Appl i es onl y to DLM SVCs. The ci rcui t i s used onl y for
outgoi ng cal l s.
PERMANENT Mandatory for X.25 PVCs. The ci rcui t i s permanentl y
connected to a remote DTE and does not need to be swi tched
dynami cal l y.
VAX
VERIFICATION option (VAX only)
Appl i es onl y to synchronous and asynchronous ci rcui ts. Determi nes whether the
remote node needs to send i ts routi ng i ni ti al i zati on password. There are three
opti ons:
DI SABLED Does not requi re the remote node to send i ts routi ng i ni ti al i zati on
password. Thi s i s the defaul t.
ENABLED Requi res the remote node to send i ts routi ng i ni ti al i zati on
password.
I NBOUND Appl i es to any DDCMP poi nt-to-poi nt ci rcui t. Speci es that the
executor node expects to recei ve a routi ng i ni ti al i zati on password
for veri cati on from a remote node before a connecti on i s made
between the nodes. Thi s parameter i s speci ed automati cal l y
for dynami c asynchronous DDCMP ci rcui ts. I f you speci fy the
VERI FI CATI ON I NBOUND parameter for a ci rcui t, you must
speci fy the I NBOUND node parameter (by usi ng the SET/DEFI NE
NODE command) for the remote node.
361
SET/DEFINE CIRCUIT
Comments (VAX only)
VAX
I f you pl an to run DECnet over a CI , you must rst i nstal l the dri ver CNDRI VER.
To do thi s, add the fol l owi ng l i nes to the si te-speci c startup procedure i n
SYS$MANAGER:
$ RUN SYS$SYSTEM:SYSGEN
CONNECT CNA0/NOADAPTER
Refer to the DECnet for OpenVMS Networking Manual for a tabl e of ci rcui t
parameters grouped accordi ng to ci rcui t type.
Examples
VAX
1.
NCP>SET CIRCUIT DMB-0 COST 4 STATE ON
Thi s command sets the STATE to ON and the ci rcui t cost to 4 for ci rcui t
DMB0.
2. NCP>SET CIRCUIT MNA-0 STATE ON MAXIMUM ROUTERS 5
Thi s command sets Ethernet ci rcui t MNA0 to ON and sets the maxi mum
number of routers permi tted on the ci rcui t to 5.
VAX
3.
NCP>SET CIRCUIT DMB-* COST 5
Thi s command sets the ci rcui t cost to 5 for al l DMB ci rcui ts.
362
SET EXECUTOR ALL
SET EXECUTOR ALL
The SET EXECUTOR ALL command updates the vol ati l e copy of the l ocal nodes
database wi th al l the l ocal node parameters stored for that node i n i ts permanent
database.
Format
SET EXECUTOR ALL
Parameters
None.
Examples
1. NCP>SET EXECUTOR ALL
Thi s command l oads al l permanent database entri es stored for the l ocal node
i nto the vol ati l e database.
363
SET/DEFINE EXECUTOR
SET/DEFINE EXECUTOR
The SET EXECUTOR command creates or modi es parameters i n the vol ati l e
database. The DEFI NE EXECUTOR command creates or modi es parameters i n
After the executor nodes state i s set to ON, you cannot change i ts ADDRESS,
ALI AS NODE, BUFFER SI ZE, MAXI MUM BROADCAST ROUTERS, MAXI MUM
CI RCUI TS, NAME, SEGMENT BUFFER SI ZE, or TYPE parameter.
Format
SET EXECUTOR parameter [...]
DEFINE EXECUTOR parameter [...]
Command Parameters
Establ i shes a node address for the l ocal node, i n the fol l owi ng format:
area-number.node-number
where:
area-number I s i n the range 1 to 63.
node-number I s i n the range 1 to 1023.
I f you do not speci fy area-number, the defaul t area i s 1. You need not suppl y the
area number i n the node-address i f your node i s i n area 1. When you congure
the l ocal node, thi s parameter i s requi red.
ALIAS INCOMING option
Speci es whether the l ocal node accepts i ncomi ng connect requests di rected to
the al i as node i denti er speci ed for the l ocal node. The al i as node i denti er i s
descri bed under the ALI AS NODE parameter. There are two opti ons for ALI AS
I NCOMI NG:
DI SABLED Speci es that the l ocal node wi l l not accept
i ncomi ng connect requests di rected to the al i as
node i denti er.
ENABLED Speci es that the l ocal node wi l l accept i ncomi ng
connect requests di rected to the al i as node
i denti er. Thi s i s the defaul t i f an al i as node
i denti er has been speci ed.
ALIAS MAXIMUM LINKS number
Speci es the maxi mum number of l ogi cal l i nks for the l ocal node that can use
the al i as node i denti er. The al i as node i denti er i s descri bed under the ALI AS
NODE parameter. The maxi mum val ue for ALI AS MAXI MUM LI NKS i s 200.
The defaul t i s 32.
ALIAS NODE node-id
Establ i shes a cl uster al i as node i denti er for use by the l ocal node. The node-id
i s a DECnet node i denti er that can be ei ther a node name or a node address.
Thi s al i as permi ts the l ocal node to be associ ated wi th a cl uster node i denti er
common to some or al l nodes i n the cl uster, i n addi ti on to i ts own uni que node-id.
364
SET/DEFINE EXECUTOR
I f you do not speci fy thi s parameter, the l ocal node i s not associ ated wi th a cl uster
al i as node i denti er. I f a node name i s to be used as the al i as node-id, the node
name must previ ousl y have been dened i n the database.
VAX
AREA MAXIMUM COST number (VAX only)
Appl i es onl y to an executor node whose type i s AREA. Speci es the maxi mum
total path cost al l owed from the executor to any other l evel 2 routi ng node (area
router). You can speci fy a deci mal val ue i n the range 1 to 1022. The defaul t i s
1022.
AREA MAXIMUM HOPS number (VAX only)
Appl i es onl y to an executor node whose type i s AREA. Speci es the maxi mum
number of routi ng hops al l owabl e from the executor to any other l evel 2 routi ng
node. You can speci fy a deci mal val ue i n the range 1 to 30. The defaul t i s 30.
BROADCAST ROUTING TIMER seconds
Speci es the maxi mum amount of ti me al l owed between routi ng updates on
Ethernet or FDDI ci rcui ts. When the ti mer expi res before a routi ng update
occurs, a routi ng update i s forced. The routi ng update produces a routi ng
congurati on message for each adjacent node. You can speci fy a number i n the
range 1 to 65,535. The defaul t i s 180.
BUFFER SIZE number
Speci es the si ze of the recei ve buffers i n bytes, thereby control l i ng the maxi mum
si ze of NSP message segments that can be recei ved and forwarded. (The si ze
i ncl udes protocol overhead down to and i ncl udi ng the End Communi cati on l ayer,
but does not i ncl ude the Data Li nk l ayer overhead.)
The val ue of the BUFFER SI ZE parameter must be greater than or equal to the
val ue of the SEGMENT BUFFER SI ZE parameter. The two val ues are normal l y
equal but may di ffer to permi t the network manager to al ter the buffer si ze
on al l nodes wi thout i nterupti on of servi ce. Refer to the DECnet for OpenVMS
Networking Manual for i nformati on about how to modi fy buffer si zes. Thi s buffer
si ze appl i es to al l ci rcui ts known to the executor. The defaul t i s equal to the val ue
of the SEGMENT BUFFER SI ZE, i f speci ed; otherwi se i t i s 576.
Speci es a ti mer whose expi rati on causes a node counter l oggi ng event.
DEFAULT ACCESS option
Assi gns the defaul t access to al l nodes that do not have a speci c node ACCESS
entry i n the vol ati l e database. There are four opti ons:
BOTH Al l ows i ncomi ng and outgoi ng l ogi cal l i nk
connecti ons. Thi s i s the defaul t.
I NCOMI NG Al l ows l ogi cal l i nk connecti ons from the remote
node.
NONE Does not al l ow i ncomi ng or outgoi ng l ogi cal l i nk
connecti ons to thi s node.
OUTGOI NG Al l ows the l ocal node to i ni ti ate connecti ons to
the remote node, but does not al l ow connecti ons
from the remote node.
I f you have OPER pri vi l ege on the l ocal system, you can overri de the defaul t
access restri cti on speci ed by thi s parameter.
365
SET/DEFINE EXECUTOR
DELAY FACTOR number
Speci es the number by whi ch to mul ti pl y one-si xteenth of the esti mated round
tri p del ay to a node to set the retransmi ssi on ti mer to that node. Use a number
rangi ng from 16 to 255. The defaul t i s 80.
DELAY WEIGHT number
Speci es the wei ght to appl y to a new round-tri p del ay data poi nt when updati ng
the esti mated round-tri p del ay to a node. The range i s from 1 to 255. The defaul t
i s 5.
VAX
DNS INTERFACE option (VAX only)
Speci es whether the node wi l l obtai n node and address i nformati on from the
DECdns namespace to update the vol ati l e node database. For i nformati on about
usi ng an exi sti ng DECdns namespace for node-name-to-address mappi ng, see
DECnet for OpenVMS Networking Manual.
ENABLED Enabl es the use of the DECdns namespace,
whi ch must al ready exi st, for updati ng the
vol ati l e node database.
DI SABLED Speci es that the node wi l l not use the DECdns
namespace to search for node name and address
i nformati on. Onl y the l ocal node database i s
searched for thi s i nformati on. Thi s i s the defaul t.
DNS NAMESPACE string (VAX only)
Set thi s parameter i f you want to use the DNS I NTERFACE. Speci es an
exi sti ng DECdns namespace. I f DNS I NTERFACE i s enabl ed and you omi t the
DNS NAMESPACE parameter, DECnet for OpenVMS uses the defaul t DECdns
namespace for node name and address l ookups. The stri ng val ue must be 1 to
256 al phanumeri c characters and can i ncl ude the dol l ar si gn ($), underscore (_),
and hyphen (-) characters.
IDENTIFICATION id-string
Speci es a text stri ng that descri bes the executor node (for exampl e, VMS Host
System). The stri ng can be a maxi mum of 32 characters. I f i t contai ns bl anks
or tabs, you must encl ose the stri ng i n quotati on marks. I f you do not set thi s
parameter, the defaul t stri ng i ncl udes the name and versi on of the product.
VAX
IDP string (VAX only)
Set thi s parameter i f you want to use the DNS I NTERFACE. Speci es the I DP of
the networks network servi ce access poi nt (NSAP) (gl obal network address). The
stri ng val ue must be 1 to 22 hexadeci mal di gi ts. The defaul t i s 49.
INACTIVITY TIMER seconds
Speci es the maxi mum durati on of i nacti vi ty (no data i n ei ther di recti on) on a
l ogi cal l i nk before the node checks to see i f the l ogi cal l i nk sti l l works. The range
i s between 1 and 65,535. The defaul t i s 60.
INCOMING PROXY option
I ndi cates whether proxy l ogi n requests present on i ncomi ng l ogi cal l i nks are to be
honored. There are two opti ons for I NCOMI NG PROXY:
366
SET/DEFINE EXECUTOR
DI SABLED I gnores al l i ncomi ng proxy requests. I nstead,
val i dates the l ogi cal l i nk by usi ng the access
control i nformati on i n the connect request or the
access control i nformati on associ ated wi th the
object.
ENABLED I nvokes the appropri ate proxy, based on the
source user, source node, and suppl i ed access
control i nformati on (i f any). Thi s i s the defaul t.
Note that proxy access characteri sti cs establ i shed i n the object database take
preference over the proxy access characteri sti cs establ i shed i n the executor
database.
INCOMING TIMER seconds
Speci es the maxi mum amount of el apsed ti me between the ti me a connecti on i s
recei ved for a process and the ti me that process accepts or rejects the connecti on.
For very busy systems, use a val ue i n the range of 45 to 60 seconds. Otherwi se
use a val ue of 30 seconds. The defaul t i s 45.
MAXIMUM ADDRESS number
Denes the hi ghest node address and, consequentl y, the greatest number of nodes
that can be addressed by the l ocal node. The defaul t i s 1023.
I f you recei ve an i nval i d val ue error, you probabl y have not al l ocated enough
nonpaged pool space. You must l ower the MAXI MUM ADDRESS val ue or
i ncrease the NPAGEDYN val ue. (Use the System Generati on uti l i ty (SYSGEN)
to change the NPAGEDYN parameter.)
VAX
MAXIMUM AREA number (VAX only)
Appl i es onl y to an executor node whose type i s AREA. Speci es the l argest area
number and, therefore, the greatest number of areas that can be known about by
the executor nodes Routi ng l ayer. You can speci fy a deci mal val ue up to 63. The
defaul t i s 63.
MAXIMUM BROADCAST NONROUTERS number
Speci es the maxi mum total number of nonrouti ng nodes (end nodes) the
executor node can have on i ts broadcast ci rcui ts. Use a number from 1 to 1023.
The defaul t i s 64.
MAXIMUM BROADCAST ROUTERS number
Speci es the maxi mum total number of routers the executor node can have on i ts
broadcast ci rcui ts. The val ue of thi s parameter shoul d be obtai ned by mul ti pl yi ng
32 by the val ue of the executor MAXI MUM CI RCUI TS parameter. The defaul t i s
32.
MAXIMUM BUFFERS number
Speci es the maxi mum number of buffers i n the transmi t buffer pool . DECnet
normal l y al l ocates onl y what i t needs. At mi ni mum, use a val ue that i s 15 ti mes
the square root of the number of l i nes. I ncrease thi s val ue i f you experi ence
congesti on l oss. The defaul t i s 100.
MAXIMUM CIRCUITS number
Denes the maxi mum number of ci rcui ts that the l ocal node can use. The number
must be i n the range 1 to 127. The defaul t i s 16.
367
SET/DEFINE EXECUTOR
MAXIMUM COST number
Speci es the maxi mum total path cost al l owed from the l ocal node to any node.
The path cost i s the sum of the ci rcui t costs al ong a path between two nodes. Use
as smal l a number as possi bl e i n the range of 1 to 1022. The defaul t i s 1022.
MAXIMUM DECLARED OBJECTS number
Speci es the maxi mum number of objects that al l processes on a system can
decl are. To determi ne the current number of decl ared objects on your system,
use the NCP SHOW KNOWN OBJECTS command. Each of the objects wi th a
PI D di spl ayed i s one decl ared object. A si ngl e process can decl are more than one
object. The defaul t i s 31, whi ch i s sufci ent for most congurati ons. The val i d
range of objects i s 8 to 16383. Dynami cal l y setti ng the number l ower than the
number of decl ared objects currentl y i n use has no effect on those objects.
MAXIMUM HOPS number
Speci es the maxi mum routi ng hops from the l ocal node to any other reachabl e
node. A hop i s the l ogi cal di stance over a ci rcui t between two adjacent nodes.
Use as smal l a number as possi bl e i n the range of 1 to 30, and be sure that thi s
val ue i s l ess than or equal to the MAXI MUM VI SI TS parameter. The defaul t i s
30.
MAXIMUM LINKS number
Speci es the maxi mum number of l ogi cal l i nks for the l ocal node. The maxi mum
val ue for MAXI MUM LI NKS i s 3885. The defaul t i s 32.
VAX
MAXIMUM PATH SPLITS number (VAX only)
I ndi cates the maxi mum number of equal cost paths to a gi ven desti nati on node
among whi ch the packet l oad may be spl i t. The range i s from 1 to 31. The defaul t
i s 1.
MAXIMUM VISITS number
Speci es the maxi mum number of nodes a message can vi si t before i t i s
recei ved by the desti nati on node. Use a number i n the range of the val ue of
the MAXI MUM HOPS parameter to 63. You shoul d speci fy a number that i s
twi ce the MAXI MUM HOPS val ue. The defaul t i s 63.
NAME node-name
Speci es the node name to be associ ated wi th the executor node. You can assi gn
onl y one name to a node address.
NONPRIVILEGED item
Speci es nonpri vi l eged i nbound access control i nformati on for the node. Associ ate
any of the fol l owi ng parameters wi th the NONPRI VI LEGED parameter:
ACCOUNT account I denti es the account for the defaul t nonpri vi l eged
DECnet account on the executor node.
PASSWORD password I denti es the password for the defaul t nonpri vi l eged
USER user-i d I denti es the user name for the defaul t nonpri vi l eged
368
SET/DEFINE EXECUTOR
OUTGOING PROXY option
I ndi cates whether proxy l ogi n may be used on outgoi ng connect requests. There
are two opti ons for OUTGOI NG PROXY.
DI SABLED Speci es that proxy l ogi n i s not requested on any
outgoi ng l ogi cal l i nks.
ENABLED Speci es that proxy l ogi n i s requested on
outgoi ng l ogi cal l i nks. Thi s i s the defaul t.
Note that proxy access characteri sti cs establ i shed i n the object database take
preference over the proxy access characteri sti cs establ i shed i n the executor
database.
OUTGOING TIMER seconds
Speci es the ti meout val ue for the el apsed ti me between the moment a connecti on
i s requested and the moment that connecti on i s acknowl edged by the desti nati on
node. A val ue i n the range of 30 to 60 seconds i s recommended. The defaul t i s
60.
VAX
PATH SPLIT POLICY policy (VAX only)
Speci es the pol i cy for equal cost path spl i tti ng of network trafc. There are two
val ues for PATH SPLI T POLI CY:
I NTERI M Speci es that trafc wi l l be spl i t over al l equal -
cost paths whi l e forci ng packets for i ndi vi dual
network sessi ons to fol l ow the same paths i n
order to guarantee that packets wi l l be recei ved
by the desti nati on node i n the correct order.
The I NTERI M val ue shoul d be set i f some of
the nodes i n the network do not support out-of-
order packet cachi ng. (DECnetVAX Versi on 4.5
and earl i er versi ons do not support out-of-order
packet cachi ng.)
NORMAL Speci es that al l trafc wi l l be spl i t equal l y
over al l equal -cost paths to a desti nati on
node. Al l desti nati on nodes must support
out-of-order packet cachi ng (supported by
DECnetVAX Versi on 4.6 or l ater and by DECnet
for OpenVMS); otherwi se, network performance
may suffer. NORMAL i s the defaul t.
PIPELINE QUOTA quota
Speci es the maxi mum number of bytes of nonpaged pool that DECnet wi l l use
for transmi ssi on over l ogi cal l i nks. Use thi s parameter for bufferi ng at the NSP
l evel . The defaul t i s 10000 bytes. For satel l i te communi cati ons, a val ue of 6000
or greater i s recommended.
369
SET/DEFINE EXECUTOR
PRIVILEGED item
Speci es pri vi l eged i nbound access control i nformati on for the node. Associ ate
any of the fol l owi ng parameters wi th the PRI VI LEGED parameter:
ACCOUNT account I denti es the account for the defaul t pri vi l eged
PASSWORD password I denti es the password for the defaul t pri vi l eged
USER user-i d I denti es the user name for the defaul t pri vi l eged
These parameters are not needed unl ess the PRI VI LEGES parameter i s used
expl i ci tl y i n any nodes object database.
RETRANSMIT FACTOR number
Denes the maxi mum number of ti mes any gi ven message (except a connect
i ni ti ate message) wi l l be retransmi tted before the l ogi cal l i nk i s di sconnected.
The range i s 1 to 65,535. The defaul t i s 10.
VAX
ROUTING TIMER seconds (VAX only)
Speci es the maxi mum amount of el apsed ti me before a routi ng update i s forced
on non-broadcast ci rcui ts. The routi ng update produces a routi ng congurati on
message for each adjacent node. You can use a number up to a maxi mum of
65,535. The defaul t i s 600.
SEGMENT BUFFER SIZE number
Speci es the maxi mum si ze of transmi t buffers i n bytes, thereby control l i ng the
maxi mum si ze NSP message segment that can be transmi tted. (Thi s val ue i s the
maxi mum si ze message the End Communi cati ons l ayer can transmi t; i t does not
i ncl ude Data Li nk l ayer overhead.) The defaul t i s equal to the val ue of BUFFER
SI ZE, i f speci ed; otherwi se, i t i s 576.
The SEGMENT BUFFER SI ZE must al ways be l ess than or equal to the BUFFER
SI ZE. The two val ues are normal l y equal but may di ffer to permi t the network
manager to al ter buffer si zes on al l nodes wi thout i nterrupti on of servi ce. Refer
to the DECnet for OpenVMS Networking Manual for i nformati on about how to
modi fy buffer si zes.
STATE node-state
Speci es the operati onal state of the executor node. There are four possi bl e
states:
OFF Al l ows no new l ogi cal l i nks, termi nates exi sti ng l i nks, and stops
route-through trafc.
ON Al l ows l ogi cal l i nks.
RESTRI CTED Al l ows no new i nbound l i nks from other nodes.
SHUT Al l ows no new l ogi cal l i nks, does not destroy exi sti ng l i nks, and
goes to the OFF state when al l l ogi cal l i nks are di sconnected.
I f you have OPER pri vi l ege, you can overri de the state val ue speci ed i n thi s
parameter.
SUBADDRESSES range (Remote management only)
Appl i es onl y to DLM ci rcui ts. Speci es a range of l ocal DTE subaddresses that
the Routi ng l ayer accepts as X.25 DLM cal l s. VAX P.S.I . routes al l i ncomi ng X.25
370
SET/DEFINE EXECUTOR
cal l s wi thi n the speci ed subaddress range to the Routi ng l ayer to be handl ed as
DLM cal l s.
TYPE node-type
I ndi cates the type of the executor node. There are ve possi bl e node types:
Nonrouti ng I I I
Nonrouti ng I V
Routi ng I V
Routi ng I I I
Area
VAX speci c
A ROUTI NG I V node has ful l routi ng capabi l i ty. A NONROUTI NG I V node (or
end node) can del i ver packets to or recei ve them from any node over one ci rcui t,
but cannot route packets from other source nodes through to desti nati on nodes.
AXP
Note
DECnet for OpenVMS AXP supports l evel 1 routi ng on onl y one ci rcui t
and does not support l evel 2 (area) routi ng.
An AREA node i s a l evel 2 router that can route packets wi thi n i ts own area and
between areas.
Comments
You can use the SET and DEFI NE EXECUTOR commands to create or modi fy
executor node parameters, i ncl udi ng certai n parameters common to both the
executor and remote nodes. Refer to the DECnet for OpenVMS Networking
Manual for a tabl e of node parameters that i ndi cates those used for the executor
node onl y and those common to the executor and remote nodes.
Examples
1. NCP>SET EXECUTOR ADDRESS 2.11
Thi s command sets the executor nodes address to 2.11.
2. NCP>SET NODE 2.13 NAME BIRDY
.
.
.
NCP>SET EXECUTOR ALIAS NODE BIRDY
The SET NODE command establ i shes a node address 2.13 wi th the associ ated
node name BI RDY. The SET EXECUTOR ALI AS NODE command then
establ i shes the node name BI RDY as the al i as node i denti er.
3. NCP>SET EXECUTOR ALIAS INCOMING ENABLED
Thi s command speci es that i ncomi ng connect requests di rected to the al i as
node i denti er are permi tted.
371
SET/DEFINE EXECUTOR
4. NCP>SET EXECUTOR ADDRESS 11
.
.
.
NCP>SHOW EXECUTOR SUMMARY
Node Volatile Summary as of 15-JUN-1992 15:40:20
Executor node = 1.11 (BOSTON)
State = on
Thi s command sets the executor nodes address to 1.11. As the di spl ay
i ndi cates, the system defaul t val ue i s 1 i f the area-number i s not speci ed.
5. NCP>SET EXECUTOR STATE ON
Thi s command turns on the executor node.
6. NCP>SET EXECUTOR NAME ROBIN
Thi s command sets the executor nodes name to ROBI N.
372
SET EXECUTOR NODE
SET EXECUTOR NODE
The SET EXECUTOR NODE command sets the defaul t executor unti l you
expl i ci tl y reset i t. The executor i s the node on whi ch the network management
l i stener (NML) runs to perform NCP commands. (Do not use the TELL prex
wi th the SET EXECUTOR NODE command.)
Format
SET EXECUTOR NODE parameter [...]
Command Parameter
NODE node-spec
Speci es a node name or address opti onal l y fol l owed by access control i nformati on
as speci ed for OpenVMS operati ng systems. Use one of the fol l owi ng formats:
node-id
node-id"user password account"
The node-spec may be a l ogi cal name. You can overri de access control i n a l ogi cal
name by speci fyi ng access control i nformati on expl i ci tl y i n the command.
Associ ate any or al l of the fol l owi ng opti onal access control parameters wi th thi s
parameter:
ACCOUNT account Speci es the user s account for access control
veri cati on at the desi gnated executor node.
PASSWORD password Speci es the user s password for access control
USER user-i d Speci es the user s username for access control
Description
For thi s command, you must enter the command verb SET EXECUTOR fol l owed
by the NODE node-spec parameter. You can then enter the opti onal access control
parameters i n any order.
I f the SET EXECUTOR NODE command fai l s, you must expl i ci tl y use the
CLEAR EXECUTOR NODE or the SET EXECUTOR NODE command wi th a
di fferent node name or address.
373
SET EXECUTOR NODE
Examples
1. NCP>SET EXECUTOR NODE 5.14
.
.
.
The rst command sets the executor to node 5.14. The second resets the
executor to the l ocal node.
2. NCP>SET EXECUTOR NODE 14"GRAY MARY"
Thi s command uses access control i nformati on to set the executor node to
node 1.14. Thi s exampl e assumes a defaul t area number of 1 for the executor
node.
3. NCP>SET EXECUTOR NODE TRNTO USER GRAY PASSWORD MARY
Thi s command uses an al ternate access control format to set the executor to
node TRNTO.
4. $ DEFINE NODE$MY TRNTO"""GRAY MARY"""
$ RUN SYS$SYSTEM:NCP
NCP>SET EXECUTOR NODE NODE$MY
The rst command denes a l ogi cal name (NODE$MY) for the gi ven node-
spec. When runni ng NCP, you can use thi s l ogi cal name wi th the SET
EXECUTOR NODE command. Note that you must use three sets of quotati on
marks to del i mi t access control i nformati on (i f suppl i ed) i n the node-spec.
374
SET KNOWN PROXIES ALL
SET KNOWN PROXIES ALL
The SET KNOWN PROXI ES ALL command cl ears the contents of the vol ati l e
proxy database and rebui l ds the vol ati l e proxy database from the contents of the
permanent proxy database.
Format
SET proxy-component ALL
Proxy Component
KNOWN PROXIES
Proxy Component
KNOWN PROXIES
I ndi cates that al l proxy val ues are to be updated.
Examples
1. NCP>SET KNOWN PROXIES ALL
Thi s command rebui l ds the vol ati l e database of proxy val ues from the
permanent database.
375
SET LINE ALL
SET LINE ALL
The SET LI NE ALL command updates the vol ati l e database wi th al l the l i ne
parameters stored for a parti cul ar l i ne i n the permanent database.
Format
SET line-component ALL
Line Components
LINE KNOWN LINES
Line Components
LINE line-id
I denti es the l i ne whose parameters are to be updated.
KNOWN LINES
I ndi cates that al l parameters for al l known l i nes are to be updated.
Examples
1. NCP>SET KNOWN LINES ALL
l i nes i nto the vol ati l e database.
376
SET/DEFINE LINE
SET/DEFINE LINE
The SET LI NE command creates or modi es l i ne parameters i n the vol ati l e
database. The DEFI NE LI NE command creates or modi es l i ne parameters i n
Most parameters canont be SET when the l i ne i s i n the ON state except for
the COUNTER TI MER, SERVI CE TI MER, and STATE parameters. These
parameters can be changed when the l i ne i s ON.
Format
SET line-component parameter [...]
DEFINE line-component parameter [...]
Line Components
LINE KNOWN LINES
Line Components
LINE line-id
I denti es the l i ne for whi ch speci ed parameters are to be created or modi ed i n
the database.
KNOWN LINES
I ndi cates that the speci ed parameters for al l known l i nes are to be created or
modi ed i n the database.
Command Parameters
BUFFER SIZE number
Speci es i n bytes the si ze of recei ve buffers for the speci ed l i ne, thereby
control l i ng the maxi mum si ze of NSP message segments that can be recei ved
from or forwarded to an adjacent node that has accepted the l i ne buffer si ze. Use
a val ue up to a maxi mum of 65,535 for non-broadcast l i nes. On Ethernet and
FDDI l i nes, BUFFER SI ZE shoul d not be rai sed to a val ue hi gher than 1498
bytes. For Ethernet and FDDI l i nes, the val ue of 1498 bytes i s provi ded as the
defaul t. For al l other types of l i ne, the defaul t i s the executor BUFFER SI ZE
val ue (as speci ed i n the SET EXECUTOR command). Thi s parameter does not
appl y to X.25 l i nes.
You can use BUFFER SI ZE to i ncrease the si ze of NSP messages for l ogi cal l i nks
over thi s l i ne.
VAX
CLOCK clock-mode (VAX only)
Appl i es onl y to synchronous DDCMP l i nes. Speci es the hardware cl ock mode for
the l i ne. There are two val ues for clock-mode:
EXTERNAL For normal cl ock operati ng mode. The cl ock si gnal i s suppl i ed
external l y to the control l er.
377
SET/DEFINE LINE
I NTERNAL For use of the cl ock i n test mode. Setti ng thi s val ue causes the
l i ne devi ce to suppl y a cl ock si gnal that wi l l al l ow al l transmi tted
messages to be l ooped back from outsi de the devi ce. Note that, i n
order to use thi s parameter, the operator may have to connect a
l oopback pl ug i n pl ace of the normal l i ne.
CONTROLLER mode
Speci es the control l er mode for the l i ne. There are two possi bl e modes:
LOOPBACK I nternal devi ce l oopback mode. Note that not al l devi ces support
thi s mode.
NORMAL Normal operati ng mode, whi ch i s the defaul t
Speci es a ti mer whose expi rati on causes a l i ne counter l oggi ng event. Speci fy a
deci mal i nteger up to 65,535.
VAX
DEAD TIMER milliseconds (VAX only)
Appl i es onl y to DDCMP CONTROL l i nes. Speci es the number of mi l l i seconds
between pol l s of one of the sets of dead tri butari es. The milliseconds val ue must
be a deci mal i nteger up to 65,535. The defaul t i s 10,000 (10 seconds).
DELAY TIMER milliseconds (VAX only)
Appl i es onl y to DDCMP CONTROL l i nes. Denes the mi ni mum number of
mi l l i seconds to del ay between pol l s. Thi s ti mer l i mi ts the effect of a very fast
control stati on on sl ower tri butari es. The milliseconds val ue must be a deci mal
i nteger up to 65,535. I f you do not set thi s parameter, there i s no del ay.
DUPLEX mode (VAX only)
Appl i es to DDCMP l i nes. Speci es the hardware dupl ex mode of the l i ne. There
are two possi bl e modes:
FULL Ful l -dupl ex (defaul t)
HALF Hal f-dupl ex
ECHO DATA value
Appl i es onl y to FDDI l i nes. Speci es the val ue, i n hexadeci mal , used as data
i n an echo request frame. The si ze of the frame i s determi ned by the ECHO
LENGTH parameter. The frame i s sent to the address speci ed by the ECHO
TARGET parameter.
The val ue must be a stri ng of exactl y two hexadeci mal di gi ts. The defaul t i s 55.
ECHO DATA can be set i n the vol ati l e database, but i t cannot be dened i n the
permanent database.
ECHO LENGTH number
Appl i es onl y to FDDI l i nes. Speci es the number of bytes used i n an echo request
frame. The val ue of the bytes i s speci ed by the ECHO DATA parameter. The
frame i s sent to the address speci ed by the ECHO TARGET parameter.
The number must be a deci mal val ue from 0 to 4478. The defaul t i s 1. ECHO
LENGTH can be set i n the vol ati l e database, but i t cannot be dened i n the
permanent database.
378
SET/DEFINE LINE
ECHO TARGET p-address
Appl i es onl y to FDDI l i nes. Speci es the address to whi ch an echo request frame
wi l l be sent. The defaul t echo target i s 00-00-00-00-00-00. The ECHO TARGET
can be set i n the vol ati l e database, but i t cannot be dened i n the permanent
database.
VAX
HANGUP option (VAX only)
Appl i es onl y to asynchronous DDCMP l i nes. I ndi cates whether the modem
si gnal s are dropped when the l i ne i s shut down. There are two possi bl e opti ons:
DI SABLED I ndi cates that modem si gnal s shoul d not be dropped when the l i ne
i s shut down. Thi s i s the defaul t for stati c asynchronous DDCMP
l i nes.
ENABLED I ndi cates that modem si gnal s shoul d be dropped when the l i ne i s
shut down.
Thi s parameter i s suppl i ed automati cal l y for dynami c asynchronous DDCMP
l i nes. The defaul t i s HANGUP ENABLED i f the /HANGUP qual i er was
speci ed for the DCL command SET TERMI NAL, and HANGUP DI SABLED i f
/NOHANGUP was speci ed.
HOLDBACK TIMER milliseconds (Remote management only)
Appl i es onl y to X.25 l i nes. Speci es the maxi mum del ay before the X.25 software
acknowl edges successful recei pt of data. I f you do not speci fy thi s parameter,
then the acknowl edgment i s sent i mmedi atel y. I f you speci fy a hol dback ti mer,
performance may be i mproved by al l owi ng the acknowl edgment to be i ncl uded
wi th a subsequent data message transmi tted. Thi s parameter cannot be set to a
val ue l arger than one hal f the val ue of the RETRANSMI T TI MER parameter.
INTERFACE interface-code (Remote management only)
Appl i es onl y to X.25 l i nes usi ng the I SO8208 prol e. Speci es the way i n whi ch
the X.25 l evel 2 software acts when i t uses the l i ne. There are two val ues for the
interface-code:
DCE Speci es that the software operates as a DCE.
DTE Speci es that the software operates as a DTE.
The defaul t i s DTE.
VAX
LINE SPEED number (VAX only)
Appl i es onl y to asynchronous DDCMP l i nes. Speci es the speed of the l i ne
i n baud. Thi s parameter must be set to the same val ue on both si des of an
asynchronous DDCMP connecti on. I t i s speci ed automati cal l y for dynami c
asynchronous DDCMP l i nes. I f not speci ed, the val ue of thi s parameter i s equal
to the current speed of the l i ne.
379
SET/DEFINE LINE
MAXIMUM BLOCK number (Remote management only)
Appl i es onl y to X.25 l i nes. Speci es the maxi mum si ze i n bytes of the frame for
the l i ne. Thi s val ue must be at l east 5 bytes l arger than the maxi mum packet si ze
you speci fy i n the SET CI RCUI T (for PVCs) or SET MODULE X25-PROTOCOL
(for SVCs) command. Speci fy a val ue i n the range 21 to 4103. By defaul t, the
si ze of the frame takes the val ue speci ed by the PROFI LE parameter of SET
MODULE X25-PROTOCOL commands. See the Public Network I nformation
manual for the network val ue of thi s parameter.
MAXIMUM RETRANSMITS number (Remote management only)
Appl i es onl y to X.25 l i nes. Speci es the maxi mum number of retransmi ssi ons
of a frame on the speci ed l i ne. Speci fy a val ue up to 255. By defaul t, the
retransmi ssi on val ue takes the val ue speci ed by the PROFI LE parameter of the
SET MODULE X25-PROTOCOL command. See the Public Network I nformation
manual for the network val ue of thi s parameter.
MAXIMUM WINDOW number (Remote management only)
Appl i es onl y to X.25 l i nes. Speci es the maxi mum number of frames for whi ch
outstandi ng acknowl edgments are al l owed. Speci fy a val ue up to 127. By defaul t,
the outstandi ng frame val ue takes the val ue speci ed by the PROFI LE parameter
of the SET MODULE X25-PROTOCOL command. See the Public Network
I nformation manual for the network val ue of thi s parameter.
MICROCODE DUMP lespec (Remote management only)
Appl i es onl y to X.25 l i nes. Dumps the mi crocode of the speci ed KMS11, KMS1P,
or KMV1A devi ce to the i ndi cated l e. By defaul t, the output l e takes the
fol l owi ng format:
SYS$ERRORLOG:leid.DMP
The KMS/KMV Dump Anal yzer (PSI KDA) i s the uti l i ty program used to process
the dump l e created by the MI CROCODE DUMP parameter. Refer to the VAX
P.S.I . Problem Solving Guidefor more i nformati on about PSI KDA.
NETWORK network-name (Remote management only)
Appl i es onl y to X.25 l i nes. Speci es the network to whi ch the l i ne i s connected.
I f onl y one network i s set up, that network i s the defaul t. Otherwi se, the
NETWORK parameter i s mandatory.
NIF TARGET p-address
Appl i es onl y to FDDI l i nes. Speci es the address to whi ch the next Nei ghborhood
I nformati on Frame (NI F) request frame wi l l be sent. The defaul t NI F target
i s 00-00-00-00-00-00. You can set the NI F TARGET parameter i n the vol ati l e
database, but you cannot dene i t i n the permanent database.
380
SET/DEFINE LINE
PROTOCOL protocol-name
Denes the Data Li nk protocol to be used on thi s l i ne. The fol l owi ng val ues can
be used for protocol-name:
DDCMP CONTROL Speci es thi s l i ne as a mul ti poi nt control stati on. You
can speci fy mul ti pl e ci rcui ts for CONTROL l i nes, but
each ci rcui t must have a uni que physi cal tri butary
address.
DDCMP DMC Speci es that thi s l i ne i s i n DMC emul ator mode.
DMC i s si mi l ar to POI NT, except that DMC uses an
ol der versi on of DDCMP (Versi on 3.2). Thi s protocol
shoul d be set for the l ocal l i ne when the remote l i ne
i s a DMC. Note that thi s protocol i s val i d onl y when
a DMP11 or DMV11 i s bei ng used.
DDCMP POI NT Denes thi s l i ne as one end of a poi nt-to-poi nt
DDCMP connecti on. You can speci fy onl y one ci rcui t
per POI NT l i ne.
DDCMP TRI BUTARY Speci es that thi s l i ne i s a tri butary end of a DDCMP
mul ti poi nt group. You may speci fy onl y one ci rcui t
per TRI BUTARY l i ne.
ETHERNET Speci es that thi s l i ne uses the Ethernet protocol .
FDDI Speci es that thi s l i ne uses the FDDI protocol .
LAPB Speci es that the l i ne uses the X.25 l evel 2 protocol .
The l i ne must be a l i ne for the X25-PROTOCOL
modul e.
LAPBE Speci es that the l i ne uses the X.25 l evel 2 protocol
wi th extended sequenci ng. The l i ne must be used by
the X25-PROTOCOL modul e.
VAX speci c
Remote management onl y
Defaul t l i ne protocol s are based on l i ne names. See Appendi x A for a l i st of the
DECnet for OpenVMS ci rcui t and l i ne devi ces.
RECEIVE BUFFERS number
Speci es the l ength of the l i nes recei ve queue. Use a val ue i n the range 1 to 32.
REQUESTED TRT microseconds
Appl i es onl y to FDDI l i nes. Speci es the val ue for the token rotati on ti mer i n
mi croseconds. Mi croseconds must be a deci mal i nteger i n the range of 4000 to
167772. The defaul t i s 8000 mi croseconds.
RESTRICTED TOKEN TIMEOUT milliseconds
Appl i es onl y to FDDI l i nes. Speci es the l i mi t on how l ong a si ngl e restri cted
mode di al og may l ast before bei ng termi nated. Mi l l i seconds must be a deci mal
i nteger i n the range of 0 to 10000. The defaul t i s 1000 mi l l i seconds.
RETRANSMIT TIMER milliseconds
381
SET/DEFINE LINE
VAX
For a DDCMP mul ti poi nt l i ne, speci es the maxi mum amount of ti me al l owed to
el apse before a retransmi ssi on i s necessary. Thi s i s the amount of ti me a control
stati on wi l l wai t for a tri butary to respond. The number of mi l l i seconds must be
a deci mal i nteger up to 65,535. The defaul t val ue i s the network defaul t.
For a remotel y managed X.25 l i ne, thi s parameter speci es the ti me before a
frame i s retransmi tted. By defaul t, the ti me takes the val ue speci ed i n the
PROFI LE parameter of the SET MODULE X25-PROTOCOL command. See the
Public Network I nformation manual for the network val ue of thi s parameter. The
RETRANSMI T TI MER cannot be set to a val ue smal l er than twi ce the val ue of
the HOLDBACK TI MER parameter (i f speci ed).
RING PURGER ENABLE option
Appl i es onl y to FDDI l i nes. The opti on val ues are:
ON Parti ci pate i n the Ri ng Purger el ecti on and, i f el ected, perform the
Ri ng Purger functi on. Thi s i s the defaul t.
OFF Do not parti ci pate i n the Ri ng Purger el ecti on.
Thi s parameter i s to al l ow operati on when stati ons on your ri ng do not conform
to the FDDI speci cati on. Except for thi s case, i t shoul d be l eft ON for i mproved
ri ng rel i abi l i ty.
VAX
SCHEDULING TIMER milliseconds
between recal cul ati on of tri butary pol l i ng pri ori ti es. The number of mi l l i seconds
must be a deci mal i nteger up to a maxi mum of 65,535. The defaul t i s 50.
SERVICE TIMER milliseconds
Speci es the maxi mum amount of ti me al l owed to el apse before a recei ve request
compl etes whi l e performi ng servi ce operati ons on a l i ne. Mi l l i seconds i s a deci mal
i nteger from 1 to 65,535. The defaul t i s 4000 (4 seconds). Does not appl y to X.25
l i nes.
SIF CONFIGURATION TARGET p-address
Appl i es onl y to FDDI l i nes. Speci es the address to whi ch a Status I nformati on
Frame (SI F) congurati on request frame wi l l be sent upon request. The defaul t
SI F congurati on target i s 00-00-00-00-00-00. SI F CONFI GURATI ON TARGET
can be set i n the vol ati l e database, but i t cannot be dened i n the permanent
database.
SIF OPERATION TARGET p-address
Appl i es onl y to FDDI l i nes. Speci es the address to whi ch a Status I nformati on
Frame (SI F) operati on request frame wi l l be sent upon request. The defaul t SI F
operati on target i s 00-00-00-00-00-00. SI F OPERATI ON TARGET can be set i n
the vol ati l e database, but i t cannot be dened i n the permanent database.
STATE line-state
Speci es the l i nes operati onal state. The possi bl e states i ncl ude the fol l owi ng:
OFF The l i ne i s not i n use.
ON The l i ne i s avai l abl e for normal use or servi ce functi ons.
SERVI CE The l i ne i s avai l abl e for acti ve servi ce functi ons.
382
SET/DEFINE LINE
VAX
STREAM TIMER milliseconds (VAX only)
that a tri butary or hal f-dupl ex remote stati on i s al l owed to hol d the l i ne. The
number of mi l l i seconds must be a deci mal i nteger up to 65,535. The defaul t i s
1000 (1 second).
SWITCH option (VAX only)
Appl i es onl y to asynchronous DDCMP l i nes. Speci es i f a l i ne currentl y bei ng
used as a DECnet asynchronous communi cati ons l i ne shoul d be swi tched back to
a termi nal l i ne. There are two val ues for option:
DI SABLED The l i ne i s not swi tched to a termi nal l i ne. Thi s i s the defaul t for
stati c l i nes.
ENABLED The l i ne i s swi tched to a termi nal l i ne after i t i s di sconnected from
the network (when the channel to the network i s deassi gned). Thi s
i s the defaul t for dynami c l i nes.
TRANSMIT PIPELINE number (VAX only)
Appl i es onl y to DMR11 l i nes. Speci es the maxi mum number of DDCMP
messages for whi ch outstandi ng acknowl edgments are al l owed. Speci fy a val ue i n
the range 1 to 32. By defaul t, the val ue for outstandi ng DDCMP messages i s 7.
To avoi d excessi ve use of system memory, do not arbi trari l y set thi s val ue hi gher
than necessary. Refer to the DECnet for OpenVMS Networking Manual for the
procedure for determi ni ng an opti mum TRANSMI T PI PELI NE val ue.
VALID TRANSMISSION TIME microseconds
Appl i es onl y to FDDI l i nes. Speci es the maxi mum ti me between arri val s of a
val i d frame or unrestri cted token. Mi croseconds must be a deci mal i nteger i n the
range of 2500 to 5222. The defaul t i s 2621 mi croseconds.
Comments
VAX
Note that no protocol i s speci ed for a CI l i ne. The CI uses i ts own pri vate
protocol for communi cati on between nodes. I f you pl an to run DECnet for
OpenVMS over a CI , you must i nstal l the dri ver CNDRI VER. To do thi s, add the
fol l owi ng l i nes to the si te-speci c start up procedure i n SYS$MANAGER:
$ RUN SYS$SYSTEM:SYSGEN
CONNECT CNA0/NOADAPTER
Refer to the DECnet for OpenVMS Networking Manual for a tabl e of l i ne
parameters grouped accordi ng to l i ne type.
383
SET/DEFINE LINE
Examples
1. NCP>SET LINE SVA-0 STATE ON
Thi s command sets Ethernet l i ne SVA0 to the ON state.
2. NCP>SET LINE FZA-1 SIF CONFIGURATION TARGET AA-00-04-00-03-10
Thi s command sets the SI F CONFI GURATI ON TARGET of FDDI l i ne FZA1
to AA-00-04-00-03-10.
VAX
3.
NCP>SET LINE DMC-0 DUPLEX FULL STATE ON
Thi s command sets l i ne DMC0 to the ON state i n ful l dupl ex mode.
4. NCP>SET LINE DMC-0 PROTOCOL DDCMP POINT
Thi s command sets the l i ne protocol to DDCMP POI NT for l i ne DMC0.
5. NCP>TELL REMNOD SET LINE DUP-1 -
_ RETRANSMIT TIMER 500 MAXIMUM RETRANSMITS 10 -
_ MAXIMUM BLOCK 133 MAXIMUM WINDOW 2 STATE ON
Thi s command sets up a l i ne cal l ed DUP1 on remote node REMNOD that
uses the LAPB protocol and has an associ ated DUP11DA synchronous l i ne
i nterface wi th control l er number 1. I f a frame i s not acknowl edged wi thi n
500 mi l l i seconds, i t i s retransmi tted, and thi s operati on i s to be performed
a maxi mum of 10 ti mes. The maxi mum frame si ze i s 133 bytes, and the
maxi mum number of frames for whi ch outstandi ng acknowl edgments are
al l owed i s 2. The l i ne i s operati onal .
6. NCP>TELL REMNOD SET LINE KMX-0-0 MICROCODE DUMP BARRY
Thi s command dumps the mi crocode of the KMX to the l e
SYS$ERRORLOG:BARRY.DMP on node REMNOD.
7. NCP>TELL REMNOD SET LINE KMV-0 NETWORK PSS STATE ON
Thi s command sets up the l i ne KMV-0 on remote node REMNOD to the PSS
network.
VAX
8.
NCP>SET LINE DMF-* CONTROLLER LOOPBACK
Thi s command sets the control l er mode to l oopback for al l DMF l i nes.
384
SET LOGGING ALL
SET LOGGING ALL
The SET LOGGI NG ALL command updates the vol ati l e copy of the database
on the executor node wi th al l the l oggi ng parameters stored for the l oggi ng
component i n the permanent database on the executor node.
Format
SET logging-component ALL
Logging Components
Logging Components
KNOWN LOGGING
I ndi cates that al l parameters for al l known l oggi ng si nks are to be updated.
LOGGING CONSOLE
I ndi cates that al l parameters for the l oggi ng consol e are to be updated.
LOGGING FILE
I ndi cates that al l parameters for the l oggi ng l e are to be updated.
LOGGING MONITOR
I ndi cates that al l parameters for the l oggi ng moni tor are to be updated.
Examples
1. NCP>SET LOGGING CONSOLE ALL
Thi s command l oads al l permanent database entri es stored for the l oggi ng
consol e i nto the vol ati l e database.
385
SET/DEFINE LOGGING EVENTS
The SET LOGGI NG EVENTS command creates or modi es event-source l oggi ng
parameters i n the vol ati l e database. The DEFI NE LOGGI NG EVENTS command
creates or modi es event-source l oggi ng parameters i n the permanent database
on the l ocal node.
The l oggi ng state (i n the SET/DEFI NE LOGGI NG STATE command) must be
set to ON for al l the l oggi ng components for whi ch you are deni ng events.
Event-source and event-si nk parameters are mutual l y excl usi ve; you cannot use
parameters from both categori es i n a si ngl e command.
Format
SET logging-component parameter [...]
DEFINE logging-component parameter [...]
Logging Components
Logging Components
KNOWN LOGGING
I ndi cates that the speci ed parameters for al l known l oggi ng are to be created or
LOGGING CONSOLE
I ndi cates that the speci ed parameters for the l oggi ng consol e are to be created
or modi ed i n the database.
LOGGING FILE
I ndi cates that the speci ed parameters for the l oggi ng l e are to be created or
LOGGING MONITOR
I ndi cates that the speci ed parameters for the l oggi ng moni tor are to be created
Command Parameters
EVENTS event-list
KNOWN EVENTS
I ndi cates a speci c event or al l known events to be l ogged. The EVENTS
parameter may be fol l owed by one or more of the fol l owi ng event-source
parameters:
CI RCUI T ci rcui t-i d I denti es the ci rcui t from whi ch events are l ogged.
LI NE l i ne-i d I denti es the l i ne from whi ch events are l ogged.
386
NODE node-i d I denti es the node from whi ch events are l ogged.
SI NK node I denti es the node that i s to recei ve events. There
are two possi bi l i ti es:
EXECUTOR I denti es the l ocal node
(defaul t).
NODE node-i d I denti es a node i n the
network.
Comments
For a tabl e of the event-source parameters used wi th the SET/DEFI NE
LOGGI NG EVENTS command, refer to the DECnet for OpenVMS Networking
Manual. For a descri pti on of event-l i sts, refer to Secti on 1.4. For a summary
of event cl ass and types and i nformati on about speci c events that operati ng
systems wi l l l og, refer to Appendi x D.
Examples
1. NCP>SET LOGGING MONITOR LINE FZA-1 KNOWN EVENTS
Thi s command causes al l events for l i ne FZA1 to be l ogged to OPCOM, the
defaul t moni tor.
2. NCP>SET LOGGING CONSOLE KNOWN EVENTS SINK NODE TRNTO
Thi s command causes al l events generated l ocal l y to be l ogged to the l oggi ng
consol e on remote node TRNTO.
3. NCP>SET LOGGING CONSOLE EVENTS 4.* SINK EXECUTOR
Thi s command causes al l cl ass 4 events to be l ogged on the consol e of the
executor node.
4. NCP>SET LOGGING MONITOR EVENTS 7.*
Thi s command causes al l X25-rel ated events to be l ogged to OPCOM, the
defaul t moni tor.
387
SET/DEFINE LOGGING STATE
The SET LOGGI NG STATE command creates or modi es event-si nk l oggi ng
parameters i n the vol ati l e database. The DEFI NE LOGGI NG STATE command
creates or modi es event-si nk l oggi ng parameters i n the permanent database on
the l ocal node. The STATE parameter i s requi red for al l l oggi ng.
Format
SET logging-component parameter [...]
DEFINE logging-component parameter [...]
Logging Components
Logging Components
KNOWN LOGGING
I ndi cates that the speci ed parameters for al l known l oggi ng are to be created or
LOGGING CONSOLE
I ndi cates that the speci ed parameters for the l oggi ng consol e are to be created
LOGGING FILE
I ndi cates that the speci ed parameters for the l oggi ng l e are to be created or
LOGGING MONITOR
I ndi cates that the speci ed parameters for the l oggi ng moni tor are to be created
Command Parameters
NAME sink-name
I denti es the name of a consol e, l e, or moni tor program to whi ch events wi l l
be l ogged. For the moni tor si nk, al l network operator termi nal s (enabl ed by
the command REPLY/ENABLE=NETWORK) recei ve formatted events. You can
change thi s parameter onl y i f the si nk i s i n the OFF state.
STATE sink-state
Speci es the operati onal state of the si nk. There are three possi bl e states:
HOLD The si nk i s temporari l y unavai l abl e and events are queued.
OFF The si nk i s unavai l abl e for recei vi ng events; they are di scarded.
ON The si nk i s avai l abl e for recei vi ng events.
388
Comments
Refer to the DECnet for OpenVMS Networking Manual for a tabl e of event-si nk
l oggi ng parameters and thei r functi ons.
Examples
1. NCP>SET LOGGING CONSOLE NAME SYS$MANAGER:EVENTS.LOG
Thi s command establ i shes a l oggi ng l e, EVENTS.LOG, on the l ocal node.
2. NCP>SET LOGGING MONITOR STATE ON
Thi s command turns on l oggi ng to OPCOM, the defaul t moni tor. Al l operator
termi nal s that were previ ousl y decl ared as network operator termi nal s (wi th
REPLY/ENABLE=NETWORK) wi l l now recei ve al l formatted events.
389
SET/DEFINE MODULE CONFIGURATOR
The SET MODULE CONFI GURATOR command creates or modi es the
parameters of the Ethernet congurator modul e component i n the vol ati l e
database. The DEFI NE MODULE CONFI GURATOR command creates or
modi es the parameters of the congurator modul e component i n the permanent
database. You must speci fy a qual i er fol l owi ng the CONFI GURATOR command
verb.
The congurator modul e constructs a l i st of systems acti ve on the Ethernet
ci rcui ts speci ed.
Format
SET MODULE CONFIGURATOR [qualier] parameter
DEFINE MODULE CONFIGURATOR [qualier] parameter
Qualiers
Qualiers
CIRCUIT circuit-id
Appl i es onl y to Ethernet ci rcui ts. Speci es that congurator i nformati on on the
ci rcui t i denti ed by circuit-id i s to be stored i n the database.
KNOWN CIRCUITS
Appl i es onl y to Ethernet ci rcui ts. Speci es that congurator i nformati on on al l
known Ethernet ci rcui ts i s to be stored i n the database.
Command Parameters
ALL
Copi es congurator modul e i nformati on from the permanent database i nto the
vol ati l e database.
SURVEILLANCE control
I ndi cates whether a l i st of acti ve systems i s to be kept for the Ethernet ci rcui t or
ci rcui ts speci ed. There are two control val ues:
DI SABLED The l i st i s not to be kept. Thi s i s the defaul t val ue.
ENABLED The l i st i s to be kept.
390
Examples
1. NCP>SET MODULE CONFIGURATOR KNOWN CIRCUITS -
_ SURVEILLANCE ENABLED
Thi s command speci es that a l i st of acti ve systems on al l known Ethernet
ci rcui ts i s to be kept.
2. NCP>SET MODULE CONFIGURATOR CIRCUIT MNA-0 SURVEILLANCE ENABLED
Thi s command speci es that a l i st of acti ve systems on Ethernet ci rcui t
MNA0 i s to be kept.
3. NCP>SET MODULE CONFIGURATOR KNOWN CIRCUITS ALL
Thi s command l oads al l permanent database entri es for the congurator
modul e i nto the vol ati l e database.
391
SET/DEFINE MODULE X25-ACCESS (Remote management only)
The SET MODULE X25-ACCESS and DEFI NE MODULE X25-ACCESS
commands associ ate the host node wi th the speci ed mul ti host connector node for
the purpose of accessi ng a speci ed X.25 network.
Note
Format
SET MODULE X25-ACCESS qualier parameter [...]
DEFINE MODULE X25-ACCESS qualier
parameter [...]
Qualiers
Qualiers
KNOWN NETWORKS
I denti es the name of a network or al l known networks to be accessed by the
host node. The network name must be the same network name speci ed on the
mul ti host node to whi ch the access node connects. After you speci fy the network
qual i er, you must i ncl ude one or more of the fol l owi ng access control parameters:
ACCOUNT account I denti es the user account for use when
connecti ng to the mul ti host connector node.
Speci fy a stri ng from 1 to 39 characters. By
defaul t, no account i s used.
ALL Copi es the access parameters from the
permanent database i nto the vol ati l e database.
Use thi s parameter onl y wi th the SET MODULE
X25-ACCESS command.
NODE node-i d I denti es a mul ti host connector node connected
to the PSDN that you want to access. When you
speci fy an X25-ACCESS network for the rst
ti me, thi s parameter i s mandatory.
392
PASSWORD password Speci es the password for use by the access
routi nes when connecti ng to the mul ti host
connector node. Speci fy a stri ng from 1 to 39
characters. The defaul t i s that no password i s
used.
USER user-i d Speci es the user i denti cati on for use by the
access routi nes i n connecti ng to the mul ti host
connector node. Speci fy a stri ng from 1 to
16 characters. The defaul t i s that no user
i denti cati on i s used.
Examples
1. NCP>SET MODULE X25-ACCESS NETWORK TELENET1 NODE FRED
NCP>SET MODULE X25-ACCESS NETWORK PSS1 NODE GINGER
These two commands al l ow users on the host node to access the network
cal l ed TELENET1 through node FRED, and the network cal l ed PSS1 through
node GI NGER.
2. NCP>SET MODULE X25-ACCESS KNOWN NETWORKS ALL
Thi s command l oads al l permanent database entri es stored for the X25-
ACCESS database i nto the vol ati l e database.
393
SET/DEFINE MODULE X25-PROTOCOL (Remote management only)
The SET MODULE X25-PROTOCOL command creates or modi es the
parameters of the protocol modul e component i n the vol ati l e database.
The DEFI NE MODULE X25-PROTOCOL command creates or modi es the
parameters of the protocol modul e component i n the permanent database.
Use separate SET MODULE X25-PROTOCOL commands to speci fy a DTE
wi th i ts associ ated parameters, a group wi th i ts associ ated parameters, and the
network prol e. The X25-PROTOCOL modul e contai ns records that i denti fy the
packet swi tchi ng data networks (PSDNs) your DTE i s connected to, associ ate
your l ocal DTE (and possi bl y a group name) wi th VAX P.S.I ., and control the
transmi ssi on of packets.
Note
Format
SET MODULE X25-PROTOCOL qualier [...] parameter [...]
DEFINE MODULE X25-PROTOCOL qualier [...] parameter [...]
Qualiers
DTE KNOWN DTES
GROUP KNOWN GROUPS
Qualiers
DTE dte-address
KNOWN DTES
I denti es a l ocal DTE or speci es al l known DTEs. See the Public Network
I nformation manual for the format of the DTE address. I f you speci fy the DTE
qual i er, you must associ ate wi th i t ei ther of the fol l owi ng parameters.
network.
I f you have onl y one network set up, that network i s the defaul t for SET
commands. For DEFI NE commands the NETWORK parameter i s mandatory. I f
you have more than one network set up, the NETWORK parameter i s mandatory.
I n ei ther case, you must fol l ow the DTE qual i er wi th one or more of the
fol l owi ng parameters:
ALL Copi es DTE parameters from the permanent
database i nto the vol ati l e database. Used onl y
wi th the SET MODULE X25-PROTOCOL
command.
394
CALL TI MER seconds Speci es a ti mer that starts when a request to
set up an X.25 vi rtual ci rcui t i s transmi tted,
and whose termi nati on cl ears the request
i f no response has been recei ved. Speci fy
a val ue up to 255. By defaul t, the ti mer
takes the network val ue speci ed by the
PROFI LE parameter. See the Public Network
I nformation manual for the network val ue of
thi s parameter.
CHANNELS l i st Speci es a l i st of l ogi cal channel numbers
(LCNs) reserved for outgoi ng cal l s. The
list val ue i s one or more LCNs. Separate
mul ti pl e channel numbers wi th hyphens to
i ndi cate ranges and wi th commas to i ndi cate
i ndi vi dual numbers. Speci fy a val ue up to
4095 for each number i n the l i st. I f the DTE
i s to make outgoi ng cal l s, thi s parameter i s
mandatory when you speci fy a DTE for the
rst ti me. The LCN range at the DTE i s
dened by PSDN authori ti es at subscri pti on
ti me.
CLEAR TI MER seconds Speci es a ti mer that starts when a request
to cl ear an X.25 vi rtual ci rcui t i s transmi tted,
and whose termi nati on retransmi ts the cl ear
request i f no response has been recei ved.
Speci fy a val ue up to 255. By defaul t, the
ti mer takes the network val ue speci ed by the
thi s parameter.
COUNTER TI MER seconds Sets a ti mer whose expi rati on causes a DTE
counter l oggi ng event. Speci fy a deci mal
i nteger up to 65,535.
DEFAULT DATA bytes Speci es the defaul t packet si ze for X.25
vi rtual ci rcui ts. Thi s val ue must be at l east 5
bytes l ess than the MAXI MUM BLOCK val ue
you speci fy i n the SET LI NE command and
must be a power of 2. Speci fy a val ue i n the
range 16 to 4096 bytes. By defaul t, packet
si ze takes the network val ue speci ed by the
thi s parameter.
395
DEFAULT WI NDOW number Speci es the defaul t wi ndow si ze for X.25
vi rtual ci rcui ts, that i s, the maxi mum
number of packets for whi ch outstandi ng
acknowl edgments are al l owed. Speci fy a
val ue up to 127. By defaul t, wi ndow si ze
thi s parameter.
I NTERFACE i nterface-code Speci es the way i n whi ch the processor
operates. Thi s parameter can be used onl y
wi th the I SO8208 prol e. The parameter can
take one of the fol l owi ng val ues:
DTE The processor operates as a
DTE.
DCE The processor operates as a
DCE.
NEGOTI ATED The processor can operate
ei ther as a DTE or DCE. The
restart protocol determi nes
the appropri ate method of
operati on.
The defaul t i s DTE.
I NTERRUPT TI MER seconds Thi s i s the i nterrupt ti mer (I SO T26 ti mer).
Thi s parameter can be used onl y wi th the
I SO8208 prol e. Speci fy a val ue up to 255. I f
you do not speci fy a val ue, there i s no ti me
l i mi t on i nterrupt acknowl edgments.
LI NE l i ne-i d I denti es the l i ne associ ated wi th the DTE.
Use the format dev-c[-u] to speci fy a l i ne
name. Thi s parameter i s mandatory when
you speci fy a DTE for the rst ti me.
MAXI MUM CI RCUI TS number Speci es the maxi mum number of vi rtual
ci rcui ts for the DTE. By defaul t, the number
thi s parameter.
MAXI MUM CLEARS number Speci es the maxi mum number of attempts
to cl ear an X.25 vi rtual ci rcui t. Speci fy a
val ue up to 255. By defaul t, the number
thi s parameter.
396
MAXI MUM DATA bytes Speci es the maxi mum packet si ze for X.25
vi rtual ci rcui ts. Thi s val ue must be at l east 5
bytes l ess than the MAXI MUM BLOCK val ue
you speci fy i n the SET LI NE command and
must be a power of 2. Speci fy a val ue i n the
range 16 to 4096 bytes. By defaul t, packet
thi s parameter.
MAXI MUM RESETS number Speci es the maxi mum number of attempts to
reset an X.25 vi rtual ci rcui t. I f thi s number
i s exceeded, the vi rtual ci rcui t wi l l be cl eared.
Speci fy a val ue up to 255. By defaul t, the
number takes the network val ue speci ed
by the PROFI LE parameter. See the Public
Network I nformation manual for the network
val ue of thi s parameter.
MAXI MUM RESTARTS number Speci es the maxi mum number of attempts
to restart an X.25 vi rtual ci rcui t. Speci fy
a val ue up to 255. By defaul t, the number
thi s parameter.
MAXI MUM WI NDOW number Speci es the wi ndow si ze al l owed for X.25
vi rtual ci rcui ts, that i s, the maxi mum
number of packets for whi ch outstandi ng
acknowl edgments are al l owed. Speci fy a
val ue up to 127. By defaul t, the wi ndow
thi s parameter.
RESET TI MER seconds Speci es a ti mer that starts when a reset
i s transmi tted, and whose termi nati on
retransmi ts the reset i f no response has been
recei ved. Speci fy a val ue up to a maxi mum of
255. By defaul t, the ti mer takes the network
val ue speci ed by the PROFI LE parameter.
See the Public Network I nformation manual
for the network val ue of thi s parameter.
397
RESTART TI MER seconds Speci es a ti mer that starts when a restart
i s transmi tted, and whose termi nati on
retransmi ts the restart i f no response has
been recei ved. Speci fy a val ue up to 255. By
defaul t, the ti mer takes the network val ue
speci ed by the PROFI LE parameter. See the
Public Network I nformation manual for the
network val ue of thi s parameter.
STATE dte-state Speci es the operati onal state of the DTE.
Thi s parameter takes one of the fol l owi ng
val ues:
ON The DTE i s avai l abl e for normal
use.
OFF The DTE i s not i n use. Thi s i s the
defaul t state.
SHUT The DTE i s to be cl osed down
but onl y when al l present acti vi ty
has ceased. Used onl y wi th the
SET MODULE X25-PROTOCOL
command.
GROUP group-name
KNOWN GROUPS
I denti es a cl osed user group (CUG) or bi l ateral cl osed user group (BCUG) or
speci es al l known groups. Each group speci ed shoul d have a uni que group-
name, from 2 to 16 characters l ong. I f you speci fy the GROUP qual i er, you must
fol l ow i t wi th one or more of the fol l owi ng parameters:
ALL Copi es the group parameters from the
permanent database i nto the vol ati l e
database. Used onl y wi th the SET MODULE
X25-PROTOCOL command.
DTE dte-address I denti es the l ocal DTE associ ated wi th the
group name. Thi s parameter i s mandatory
when you are creati ng a group.
NETWORK network-
name(Remote management
onl y)
I denti es a network to whi ch the DTE i s
connected. Thi s parameter i s mandatory
when you are creati ng a group.
NUMBER group-number Speci es the CUG or BCUG number. You
can omi t l eadi ng zeros. Thi s parameter i s
mandatory when you are associ ati ng a DTE
wi th a group.
TYPE BI LATERAL Speci es the user group as a BCUG. Thi s
parameter i s mandatory when you are
associ ati ng a DTE wi th a BCUG. I t i s omi tted
i f the user group i s a CUG.
KNOWN NETWORKS
I denti es a network or speci es al l known networks. I f you speci fy the
NETWORK qual i er, you must fol l ow i t wi th one of the fol l owi ng parameters.
398
ALL Copi es the prol e name from the permanent
database to the vol ati l e database. Use onl y
wi th the SET MODULE X25-PROTOCOL
command.
PROFI LE prol e-name Speci es a prol e to be used on the network.
The prole-namei s a character stri ng of up to
32 characters. Thi s parameter i s mandatory.
Refer to the Public Network I nformation
manual for the val i d prole-name.
Examples
1. NCP>SET MODULE X25-PROTOCOL DTE 123789456 NETWORK TELENET -
_ CHANNELS 20-10,3,9 LINE DUP-0 MAXIMUM CIRCUITS 400 STATE ON
Thi s command creates a record for your l ocal DTE (DTE address 123789456)
and associ ates a l i ne DUP0 and a set of l ogi cal channel s wi th thi s DTE.
2. NCP>SET MODULE X25-PROTOCOL NETWORK NET1 PROFILE PSDNC
Thi s command speci es that you are goi ng to use PSDNC, and that you are
goi ng to connect to thi s PSDN through the network NET1.
3. NCP>SET MODULE X25-PROTOCOL GROUP ESECUG DTE 123789456 -
_ NETWORK NET1 NUMBER 12
Thi s command speci es that your DTE i s a member of cl osed user group
ESECUG wi th group number 12.
399
SET/DEFINE MODULE X25-SERVER/X29-SERVER (Remote management only)
The SET MODULE X25-SERVER and SET MODULE X29-SERVER commands
create or modi fy the parameters of the X.25 or X.29 cal l handl er i n the vol ati l e
database. The DEFI NE MODULE X25-SERVER and DEFI NE MODULE X29-
SERVER commands create or modi fy the parameters of the X.25 or X.29 cal l
handl er i n the permanent database.
Use separate SET MODULE X25-SERVER or DEFI NE MODULE X29-
SERVER commands to speci fy the modul e parameters and the desti nati ons.
The server modul es contai n records that i denti fy and speci fy parameters for a
desti nati on, speci fy the maxi mum number of ci rcui ts that each modul e (that i s,
al l desti nati ons for a parti cul ar modul e) may have, and speci fy the state of the
modul e.
Note
Format
SET MODULE X25-SERVER [qualier]
parameter [...]
SET MODULE X29-SERVER [qualier]
parameter [...]
DEFINE MODULE X25-SERVER [qualier] parameter [...]
DEFINE MODULE X29-SERVER [qualier] parameter [...]
Qualiers
Command Parameters
ALL MAXIMUM CIRCUITS
COUNTER TIMER STATE
Qualiers
DESTINATION dest-name
KNOWN DESTINATIONS
I denti es a desti nati on or speci es al l known desti nati ons. I f you speci fy the
desti nati on qual i er, you must fol l ow i t wi th one or more of the fol l owi ng
parameters:
ACCOUNT account I denti es the user account used i n
connecti ng to a host node for i ncomi ng
cal l s to a desti nati on. Speci fy a stri ng
from 1 to 39 characters. By defaul t, no
account i s used.
3100
ALL Copi es the desti nati on parameters
from the permanent database i nto the
vol ati l e database. Use onl y wi th the
SET MODULE X25-SERVER or the
SET MODULE X29-SERVER command.
CALL MASK hex-val ue Speci es the mask appl i ed to the
i ncomi ng cal l data before i t i s tested.
By defaul t, no val ue i s used.
CALL VALUE hex-val ue Speci es the stri ng used to test the
i ncomi ng cal l data. By defaul t, no val ue
i s used.
CALLED ADDRESS dte-address For redi rected cal l s, i denti es the
DTE that was ori gi nal l y cal l ed. The
parameter val ue i s used to sel ect a
desti nati on for a redi rected cal l . By
defaul t, no cal l ed DTE i s used.
EXTENSI ON MASK hex-stri ng Provi des a mask for the cal l ed address
extensi on faci l i ty. Usi ng l ogi cal AND,
the mask i s merged wi th the cal l ed
address extensi on i n the i ncomi ng
cal l and the resul t i s compared wi th
the extensi on val ue. By defaul t, no
extensi on mask i s used.
EXTENSI ON VALUE hex-stri ng Provi des a val ue for the cal l ed address
extensi on faci l i ty. The val ue i s
compared wi th the address extensi on
i n the i ncomi ng cal l (after mergi ng as
descri bed for EXTENSI ON MASK). By
defaul t, no extensi on mask i s used.
GROUP group-name I denti es a cl osed user group (CUG) or
bi l ateral cl osed user group (BCUG). The
group-namei s an I D stri ng. By defaul t,
no group name i s used.
I NCOMI NG ADDRESS I denti es the address of the DTE
recei vi ng the cal l (as speci ed i n the
cal l packet).
NETWORK network-name Speci es the network for whi ch cal l s are
accepted. By defaul t, no network name
i s used.
3101
NODE node-i d I denti es the P.S.I . Access node that i s
to be the desti nati on of the i ncomi ng
X.25 cal l . Speci fy thi s parameter
i f the executor node i s a node wi th
VAX P.S.I . software i n mul ti host mode
i nstal l ed, servi ng as a connector node.
Thi s parameter i s mandatory when
you speci fy thi s desti nati on for the
rst ti me. Used onl y wi th the SET
MODULE X25-SERVER command or
the DEFI NE MODULE X25-SERVER
command.
OBJECT object-i d I denti es the object used i n connecti ng
to a host node for i ncomi ng cal l s to
a desti nati on. The object-id i s an I D
stri ng. I f the object name l ooks l i ke a
number, encl ose the stri ng i n quotati on
marks. Thi s parameter i s mandatory
when you speci fy a desti nati on for the
rst ti me.
PASSWORD password Speci es the password used i n
connecti ng to a host node for i ncomi ng
cal l s to a desti nati on. Speci fy a stri ng
from 1 to 39 characters. The defaul t i s
that no password i s used.
PRI ORI TY pri ori ty Speci es the pri ori ty of the desti nati on
record and i s used to sel ect one of a set
of desti nati ons for whi ch the i ncomi ng
cal l may be val i d. Speci fy a val ue up to
255, where 255 i s the hi ghest pri ori ty.
By defaul t, priority takes a val ue of 0.
RECEI VI NG DTE dte-address I denti es the l ocal DTE. I t i s used to
sel ect a desti nati on for cal l s recei ved on
the l ocal DTE. By defaul t, no recei vi ng
DTE i s used.
REDI RECT REASON reason-code I denti es a reason for redi recti ng an
i ncomi ng cal l . The reason-codecan take
one of the fol l owi ng val ues:
BUSY The ori gi nal DTE was
busy and coul d not
accept any more cal l s.
OUT OF
ORDER
The ori gi nal DTE was
out of order.
SYSTEMATI C Al l cal l s to the ori gi nal
DTE are automati cal l y
rerouted.
The reason-code i s used to sel ect a
desti nati on for a redi rected cal l . By
defaul t, no reason-codei s used.
3102
SENDI NG ADDRESS dte-address I denti es the address of the remote
DTE that ori gi nated a cal l . By defaul t,
no sendi ng DTE i s used.
SUBADDRESSES range Speci es the range of l ocal DTE
subaddresses that i denti fy the
desti nati on for the i ncomi ng cal l .
The range consi sts of one or two
subaddresses. The subaddress i s a
deci mal i nteger up to 9999. See the
Public Network I nformation manual for
the maxi mum l ength of the subaddress
on your network. Separate two
subaddresses wi th a si ngl e hyphen to
i ndi cate a range. The second subaddress
must be greater than the rst. By
defaul t, no subaddress range i s used.
USER user-i d Speci es the user i denti cati on for use
by i ncomi ng cal l s to the desti nati on.
Speci fy a stri ng from 1 to 16 characters.
The defaul t i s that no user i denti cati on
i s used.
Command Parameters
ALL
Copi es the cal l handl er parameters from the permanent database i nto the vol ati l e
database. Used onl y for the SET MODULE X25-SERVER command or the SET
MODULE X29-SERVER command.
Sets a ti mer whose expi rati on causes a server modul e counter l oggi ng event.
Speci fy a deci mal i nteger up to 65,535.
MAXIMUM CIRCUITS number
Speci es the maxi mum number of ci rcui ts that the modul e (that i s, al l
desti nati ons) may have. By defaul t, the maxi mum i s 512.
STATE module-state
Speci es the operati onal state of the server modul e. Thi s parameter takes one of
the fol l owi ng val ues:
OFF The modul e i s not i n use. For the X.29 server modul e, OFF i s the
defaul t state.
ON The modul e i s avai l abl e for normal use. For the X.25 server modul e,
ON i s the defaul t state.
SHUT The modul e i s to be cl osed down but onl y when al l present acti vi ty
has ceased. The SHUT val ue appl i es onl y to the SET MODULE X25-
SERVER or X29-SERVER command.
3103
Examples
1. NCP>SET MODULE X25-SERVER DESTINATION JOE SUBADDRESSES 12-24 -
_ SENDING ADDRESS 987321654 PRIORITY 3 OBJECT OBJONE
Thi s command creates a desti nati on cal l ed JOE that wi l l handl e i ncomi ng
X.25 cal l s from a DTE wi th an address of 987321654 and a subaddress i n the
range 12 to 24 speci ed i n the DECnet object database.
2. NCP>SET MODULE X25-SERVER DESTINATION DEFDES -
_ OBJECT LAST PRIORITY 0
Thi s command modi es the desti nati on cal l ed DEFDES that wi l l handl e any
i ncomi ng cal l s. The desti nati on has the l owest pri ori ty and wi l l onl y handl e
cal l s that fai l to nd another desti nati on.
3. NCP>SET MODULE X25-SERVER DESTINATION THRUSH SUBADDRESSES 11-20 -
_ OBJECT 36 NODE THRUSH
Thi s command creates a desti nati on cal l ed THRUSH for node THRUSH that
wi l l match i ncomi ng X.25 cal l s wi th a subaddress i n the range 11 to 20. Thi s
command i s used i f the executor node i s a node wi th VAX P.S.I . software i n
mul ti host mode i nstal l ed, servi ng as a connector node. Object 36 i s the object
number for VAX P.S.I . Access on the remote node.
3104
SET NODE ALL
SET NODE ALL
The SET NODE ALL command updates the vol ati l e node database on the
executor node wi th al l the parameters stored for a parti cul ar node i n the
permanent database on the executor node.
Format
SET node-component ALL
Node Components
NODE KNOWN NODES
Node Components
NODE node-id
I denti es the node whose parameters are to be updated.
KNOWN NODES
I ndi cates that al l parameters for al l known nodes are to be updated.
Examples
1. NCP>SET KNOWN NODES ALL
nodes i nto the vol ati l e database.
3105
SET/DEFINE NODE
SET/DEFINE NODE
The SET NODE command creates or modi es node parameters i n the vol ati l e
database. The DEFI NE NODE command creates or modi es node parameters i n
the permanent database on the l ocal node.
Format
SET node-component parameter [...]
DEFINE node-component parameter [...]
Node Components
NODE KNOWN NODES
Node Components
NODE node-id
I denti es the node (l ocal or remote) for whi ch speci ed parameters are to be
created or modi ed i n the database.
KNOWN NODES
I ndi cates that the speci ed parameters for al l known nodes are to be created or
Command Parameters
ACCESS option
Speci es the al l owed l ogi cal l i nk connecti ons for the node. There are four opti ons:
BOTH Al l ows i ncomi ng and outgoi ng l ogi cal l i nk connecti ons. Thi s i s
the defaul t.
I NCOMI NG Al l ows l ogi cal l i nk connecti ons from the remote node.
NONE Does not al l ow i ncomi ng or outgoi ng l ogi cal l i nk connecti ons to
thi s node.
OUTGOI NG Al l ows the l ocal node to i ni ti ate connecti ons to the remote node,
but does not al l ow connecti ons from the remote node.
I f you have OPER pri vi l ege, you can overri de the access restri cti on speci ed i n
thi s parameter.
Speci es the address of the node.
Speci es a ti mer whose expi rati on causes a node counter l oggi ng event. Seconds
must be a deci mal i nteger from 1 to 65,535.
3106
SET/DEFINE NODE
CPU cpu-type
DECSYSTEM1020
PDP11
PDP8
VAX
DIAGNOSTIC FILE lespec
Appl i es to nodes on Ethernet ci rcui ts. I denti es the l e to be read when the
adjacent node has been downl i ne l oaded and has requested di agnosti cs. The
lespec i s i nterpreted accordi ng to the l e system of the executor node.
DUMP ADDRESS number
I denti es the address i n memory to begi n an upl i ne dump of the adjacent node.
DUMP COUNT number
Speci es the defaul t number of memory uni ts to upl i ne dump from the adjacent
node.
DUMP FILE lespec
I denti es whi ch l e to wri te to when the adjacent node i s dumped upl i ne.
HARDWARE ADDRESS h-address
I denti es the address ori gi nal l y assi gned to the control l er for the system on the
adjacent node. Used duri ng operati ons such as downl i ne l oadi ng to communi cate
wi th the system before the system has set up i ts physi cal address.
HOST node-id
I denti es the host node. For an adjacent node, the host address i s a parameter
that the adjacent node recei ves when i t i s downl i ne l oaded. I f no host i s speci ed,
the defaul t i s the executor node.
VAX
INBOUND node-type (VAX only)
Requi red for nodes when the VERI FI CATI ON I NBOUND parameter i s speci ed
for the DDCMP ci rcui t over whi ch the connecti on i s to be made. Speci es
the type of the node. The node-type i s checked by the executor node i f the
speci ed node attempts to form a dynami c connecti on wi th the executor node.
I f VERI FI CATI ON I NBOUND i s not speci ed for the ci rcui t, the I NBOUND
parameter for the node i s i gnored. There are two possi bl e node types:
ENDNODE Al l ows the remote node to be connected onl y i f i t i s congured as
an end node.
ROUTER Al l ows the remote node to be connected whether i t i s congured as
an end node or a router.
Speci es the i mage that wi l l dene the system software to be downl i ne l oaded to
an adjacent node. The l oad assi st agent can be used to tai l or the system software
to be l oaded. The LOAD ASSI ST AGENT parameter appl i es onl y when the target
i s a VMScl uster satel l i te.
PARAMETER val ue appl i es onl y when the target i s a VMScl uster satel l i te.
3107
SET/DEFINE NODE
LOAD FILE lespec
Speci es a l e contai ni ng the system software to be downl i ne l oaded to an
adjacent node.
an adjacent node.
NAME node-name
Speci es the node name to be associ ated wi th the node i denti cati on. You can
assi gn onl y one name to a node address.
NONPRIVILEGED item
Speci es nonpri vi l eged i nbound access control i nformati on for the node. Associ ate
any of the fol l owi ng parameters wi th the NONPRI VI LEGED parameter:
ACCOUNT account I denti es the account for the defaul t nonpri vi l eged
DECnet account on the desi gnated node.
PASSWORD password I denti es the password for the defaul t nonpri vi l eged
USER user-i d I denti es the user name for the defaul t
nonpri vi l eged DECnet account on the desi gnated
node.
PRIVILEGED item
Speci es pri vi l eged i nbound access control i nformati on for the node. Associ ate
any of the fol l owi ng parameters wi th the PRI VI LEGED parameter:
ACCOUNT account I denti es the account for the defaul t pri vi l eged
PASSWORD password I denti es the password for the defaul t pri vi l eged
USER user-i d I denti es the user name for the defaul t pri vi l eged
VAX
RECEIVE PASSWORD password
Does not appl y to nodes on a broadcast ci rcui t. Denes the password (1 to 8
characters) that i s expected from the remote node duri ng a routi ng i ni ti al i zati on
sequence. You use thi s parameter onl y i f veri cati on i s enabl ed or set to
I NBOUND for the ci rcui t.
Speci es a l e contai ni ng the secondary boot l oader to be downl i ne l oaded to an
adjacent node.
SERVICE CIRCUIT circuit-id
Speci es the ci rcui t to be used for downl i ne l oadi ng. Thi s ci rcui t i s the defaul t
val ue for the VI A parameter of the LOAD command. The node i denti cati on
must be that of the target node.
SERVICE DEVICE device-type
operati on i s to take pl ace. See Appendi x A, for a l i st of the DECnet for OpenVMS
3108
SET/DEFINE NODE
VAX
Onl y the synchronous port on the DMF may be used for servi ce operati ons.
SERVICE NODE VERSION version
Speci es the DECnet for OpenVMS software versi on of the node that downl i ne
l oads i ts software to a target node. The two possi bi l i ti es are PHASE I I I and
PHASE I V. The defaul t i s PHASE I V.
Denes the password requi red to tri gger the bootstrap mechani sm on the target
node. The password i s a hexadeci mal number. For broadcast ci rcui ts, the
password i s i n the range 0 to FFFFFFFFFFFFFFFF.
VAX
For DDCMP ci rcui ts, the password i s i n the range 0 to FFFFFFFF.
Speci es the I D of the software to be downl i ne l oaded. You i ncl ude thi s parameter
onl y i f the SOFTWARE TYPE parameter i s speci ed.
I denti es a parti cul ar l e type to be downl i ne l oaded. There are four possi bi l i ti es:
MANAGEMENT FI LE
SECONDARY LOADER
SYSTEM
TERTI ARY LOADER
The defaul t i s SECONDARY LOADER.
You i ncl ude thi s parameter onl y i f the SOFTWARE I DENTI FI CATI ON parameter
i s speci ed.
Speci es a l e contai ni ng a terti ary boot l oader to be downl i ne l oaded to an
adjacent node.
VAX
TRANSMIT PASSWORD password
Does not appl y to nodes on an Ethernet or FDDI ci rcui t. Speci es a password (1
to 8 characters) sent to the remote node duri ng a routi ng i ni ti al i zati on sequence.
Thi s parameter i s used onl y i f the VERI FI CATI ON parameter has been set to
ENABLED or I NBOUND for the ci rcui t.
Comments
You can use thi s command to create or modi fy parameters for a l ocal or remote
node. Refer to the DECnet for OpenVMS Networking Manual for a tabl e of the
parameters used wi th the SET NODE command accordi ng to thei r functi ons.
3109
SET/DEFINE NODE
Examples
1. NCP>SET NODE 5.14 NAME DENVER
Thi s command sets the node name of node 5.14 to DENVER.
2. NCP>SET NODE 2.11 -
_ NONPRIVILEGED -
_ USER NETNONPRIV -
_ PASSWORD NONPRIV -
_ PRIVILEGED -
_ USER NETPRIV -
_ PASSWORD PRIV
Thi s command establ i shes defaul t pri vi l eged and nonpri vi l eged access control
i nformati on for node 2.11.
3. NCP>SET NODE 14 ADDRESS 2
Thi s command associ ates the i nformati on for node 1.14 wi th a new node
whose address i s 1.2. The executor i s assumed to be i n area 1.
4. NCP>SET NODE LARK HARDWARE ADDRESS 08-00-2B-2D-88-7B
Thi s command associ ates wi th the node LARK the hardware address of the
control l er at node LARK. Thi s i nformati on i n the vol ati l e database can be
used duri ng downl i ne l oadi ng of target node LARK over a broadcast ci rcui t.
5. NCP>SET NODE 8.* ACCESS NONE
Thi s command prevents i ncomi ng or outgoi ng l ogi cal l i nk connecti ons to al l
nodes i n area 8.
3110
SET/DEFINE NODE CIRCUIT
SET/DEFINE NODE CIRCUIT
The SET NODE command wi th the CI RCUI T parameter creates or modi es
l oop node parameters i n the vol ati l e database. The DEFI NE NODE command
wi th the CI RCUI T parameter creates or modi es l oop node parameters i n the
permanent database.
The CI RCUI T parameter i s the onl y val i d parameter for l oop nodes. You can
assi gn onl y one l oop node name to a parti cul ar ci rcui t.
Format
SET NODE node-id CIRCUIT circuit-id
DEFINE NODE node-id CIRCUIT circuit-id
Node Component
NODE node-id
I denti es the l oop node name or address for whi ch the CI RCUI T parameter i s to
be created or modi ed i n the database.
Command Parameter
CIRCUIT circuit-id
I denti es whi ch ci rcui t to use for al l trafc to the node.
Examples
Thi s command sets the l oop node name (TESTER) and i denti es the ci rcui t
over whi ch l oop i nformati on i s to be transmi tted.
3111
SET OBJECT ALL
SET OBJECT ALL
The SET OBJECT ALL command updates the vol ati l e database wi th al l the
object parameters stored for a parti cul ar object i n the permanent database.
Format
SET object-component ALL
Object Components
OBJECT KNOWN OBJECTS
Object Components
OBJECT object-name
I denti es the object whose parameters are to be updated.
KNOWN OBJECTS
I ndi cates that al l parameters for al l known objects are to be updated.
Examples
1. NCP>SET KNOWN OBJECTS ALL
Thi s command l oads al l permanent database parameter entri es stored for al l
known objects i nto the vol ati l e database.
3112
SET/DEFINE OBJECT
SET/DEFINE OBJECT
The SET OBJECT command creates or modi es object parameters i n the vol ati l e
database. The DEFI NE OBJECT command creates or modi es object parameters
i n the permanent database on the l ocal node.
Format
SET object-component parameter [...]
DEFINE object-component parameter [...]
Object Components
Object Components
OBJECT object-name
I denti es the object for whi ch speci ed parameters are to be created or modi ed
i n the database.
KNOWN OBJECTS
I ndi cates that the speci ed parameters are appl i cabl e to al l known objects.
Command Parameters
ACCOUNT account
I denti es the defaul t user s account for access control on i nbound connects to the
object when no access control i s speci ed by the remote node.
ALIAS INCOMING option
Speci es how a parti cul ar object responds to i ncomi ng connect requests di rected
to the al i as node address. You establ i sh the al i as node address usi ng the SET
EXECUTOR command. There are two opti ons for ALI AS I NCOMI NG.
DI SABLED Does not al l ow a speci ed object to recei ve i ncomi ng connect
requests that have been di rected to the al i as node address. An
object whose resources are not accessi bl e cl usterwi de shoul d have
ALI AS I NCOMI NG di sabl ed. I f an attempt i s made to connect
to an object that does not have ALI AS I NCOMI NG enabl ed, the
status of NO SUCH OBJECT i s returned.
ENABLED Al l ows a speci ed object to recei ve i ncomi ng connect requests that
have been di rected to the al i as node address. An object such as
PHONE, whi ch uses a protocol that depends on mul ti pl e l i nks,
shoul d not be enabl ed for ALI AS I NCOMI NG. By defaul t, i f an
al i as node i denti er has been speci ed, ALI AS I NCOMI NG i s
enabl ed for al l objects except for PHONE.
ALIAS OUTGOING option
Speci es whether a parti cul ar object uses the al i as node i denti er speci ed i n the
SET EXECUTOR command i n i ts outgoi ng connect requests and other protocol s.
Speci fy ei ther of the fol l owi ng two opti ons:
3113
SET/DEFINE OBJECT
DI SABLED Does not al l ow a speci ed object to use the al i as node address i n
outgoi ng connect requests.
ENABLED Al l ows a speci ed object to use the al i as node address i n i ts
outgoi ng connect requests. An object such as PHONE, whi ch
uses a protocol that depends on mul ti pl e l i nks, shoul d not have
the ALI AS OUTGOI NG parameter enabl ed. By defaul t, onl y the
object MAI L has ALI AS OUTGOI NG enabl ed.
FILE lespec
Speci es the l e name of the command procedure or i mage that i s run as a
resul t of an i ncomi ng connecti on to the object. I f not speci ed, the defaul t i s
SYS$SYSTEM:object-name.COM. When you speci fy an object for the rst ti me,
thi s parameter i s mandatory.
NUMBER number
Speci es the object number. Numbers 1 through 127 are for use by Di gi tal
Equi pment Corporati on. Numbers 0 and 128 through 255 are for customer use.
See Tabl e 31 for a comprehensi ve l i st of reserved object numbers. When you
speci fy an object for the rst ti me, thi s parameter i s mandatory.
OUTGOING CONNECT PRIVILEGES privilege-list
Speci es those pri vi l eges that a user must have i n order to make an outbound
connecti on to the object.
PASSWORD password
I denti es the defaul t password for access control on i nbound connects to the
object when no access control i s speci ed by the remote node. Thi s password
must match the password establ i shed for the username associ ated wi th the
object.
PRIVILEGES privilege-list
Speci es those pri vi l eges normal l y requi red by the object. A user wi th those
pri vi l eges may be suppl i ed wi th defaul t outbound pri vi l eged access control
i nformati on when connecti ng to the object on a remote node.
3114
SET/DEFINE OBJECT
PROXY option
Assi gns the proxy l ogi n access defaul ts to i ndi vi dual objects. Speci fy one of the
fol l owi ng four opti ons:
BOTH Al l ow both i ncomi ng and outgoi ng proxy l ogi n access. Thi s i s the
defaul t opti on.
I NCOMI NG Al l ows proxy l ogi n to the object.
NONE Does not al l ow i ncomi ng or outgoi ng proxy l ogi n access.
OUTGOI NG Al l ows l ogi cal l i nks usi ng the object to request proxy l ogi n on the
remote node.
USER user-id
I denti es the defaul t username for access control on i nbound connects to the
object when no access control i s speci ed by the remote node.
Description
A DECnet object i s i denti ed by object name and object type. (The type i s
speci ed i n the NUMBER parameter.)
The pri vi l ege l i st i n the SET/DEFI NE OBJECT PRI VI LEGES command i s used
to val i date the user pri vi l eges for outbound connecti ons to that object. The access
control i nformati on i s used as the defaul t access control for i nbound connecti ons.
Refer to the DECnet for OpenVMS Networking Manual for a tabl e of object
parameters and thei r functi ons. Tabl e 31 l i sts the object type codes used wi th
the SET OBJECT and DEFI NE OBJECT commands. Al l val ues i n Tabl e 31 are
expressed i n deci mal .
3115
SET/DEFINE OBJECT
Table 31 Object Type Codes
Object Type
Code Mnemonic Description
0 TASK Di gi tal or customer use
116 Reserved for Di gi tal use
17 FAL Fi l e Access Li stener for remote l e and
record access
18 HLD Host l oader for RSX11S downl i ne task
l oadi ng requests
19 NML Network Management Li stener object
20 RSTS/E medi a transfer program
(NETCPY)
23 REMACP Network termi nal handl er
(host si de)
24 Network termi nal handl er
(termi nal si de)
25 MI RROR Loopback mi rror
26 EVL Event recei ver
27 MAI L Mai l uti l i ty
29 PHONE VMS Phone uti l i ty and
RSX11M/MPLUS Phone uti l i ty
42 CTERM Network termi nal handl er
63 DTR DECnet Test Recei ver object
128255 Reserved for customer use
3116
SET/DEFINE OBJECT
Examples
1. NCP>SET OBJECT NML NUMBER 19
Thi s command sets an object number, 19, for the NML object.
2. NCP>SET OBJECT NML -
_ PRIVILEGES OPER DIAGNOSE -
_ USER NET_NONPRIV -
_ PASSWORD NET_NONPRIV
Thi s command establ i shes defaul t access control i nformati on for the
NML object and sets those pri vi l eges requi red for pri vi l ege access control
i nformati on to be sent to a remote node when connecti ng to the object.
3. NCP>SET OBJECT OBJONE FILE OBJONE.COM NUMBER 0 -
_ USER NET PASSWORD NET
Thi s command creates an object cal l ed OBJONE wi th a command procedure
cal l ed OBJONE.COM. The i ncomi ng connecti on uses a password and user
i denti cati on of NET.
4. NCP>SET EXECUTOR ALIAS NODE 2.13
.
.
.
NCP>SET OBJECT FOX ALIAS OUTGOING ENABLED
The SET EXECUTOR ALI AS NODE command establ i shes address 2.13 as
the al i as node i denti er for the l ocal node. The SET OBJECT command
associ ates the object FOX wi th the al i as node i denti er for al l outgoi ng
connect requests.
5. NCP>SET OBJECT T* PROXY NONE
Thi s command prevents i ncomi ng or outgoi ng proxy l ogi n access for al l objects
wi th names begi nni ng wi th T.
6. NCP>SET OBJECT TEST OUTGOING CONNECT PRIVILEGES READALL OPER
Thi s command speci es that a user process must have pri vi l eges READALL
and OPER i n order to make an outbound connecti on to object TEST.
3117
SHOW AREA
SHOW AREA
The SHOW AREA command di spl ays area i nformati on from the vol ati l e database.
Format
SHOW area-component parameter [qualier]
Area Components
ACTIVE AREAS KNOWN AREAS
AREA
Qualier
TO
Area Components
ACTIVE AREAS
I ndi cates that i nformati on for al l acti ve areas i s to be di spl ayed.
AREA area-id
I denti es a parti cul ar area for whi ch i nformati on i s to be di spl ayed.
KNOWN AREAS
I ndi cates that i nformati on for al l known areas i s to be di spl ayed.
Command Parameters
CHARACTERISTICS
I ndi cates that stati c area i nformati on i s to be di spl ayed.
STATUS
I ndi cates that dynami c area i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates that onl y a summary of area i nformati on i s to be di spl ayed. Thi s i s the
defaul t di spl ay type.
Qualier
TO lespec
Speci es the output l e. I f none i s speci ed, SYS$OUTPUT i s the defaul t.
Interpreting the Display
CIRCUIT circuit-id
Thi s read-onl y parameter i denti es the ci rcui t used to get to a remote area.
COST cost
Thi s read-onl y parameter represents the total cost over the current path to the
desti nati on area. Thi s val ue i s di spl ayed onl y on routi ng nodes. The cost i s a
posi ti ve i nteger val ue associ ated wi th usi ng a ci rcui t. The Routi ng l ayer routes
messages (data) al ong the path between two areas wi th the l east cost.
3118
SHOW AREA
HOPS hops
Thi s read-onl y parameter represents the number of hops over to a desti nati on
area. A hop i s the routi ng val ue representi ng the l ogi cal di stance between two
areas i n a network.
NEXT NODE node-id
Thi s read-onl y val ue i ndi cates the next node on the ci rcui t used to get to the
desti nati on area.
STATE state
Thi s read-onl y val ue i ndi cates the state of the area. The two possi bl e states are
REACHABLE and UNREACHABLE.
Examples
1. NCP>SHOW KNOWN AREAS STATUS
Known Area Volatile Status as of 15-JUN-1992 09:50:34
Area State Cost Hops Circuit Next node to area
2 reachable 0 0 2.11 (BOSTON)
3 reachable 4 1 SVA-0 3.5 (TRNTO)
5 reachable 7 2 UNA-0 3.5 (TRNTO)
11 reachable 4 1 SVA-1 11.9 (DALLAS)
44 reachable 11 1 FZA-0 44.2 (LONDON)
Thi s command di spl ays status i nformati on for al l known areas i n the network.
2. NCP>SHOW KNOWN AREA CHARACTERISTICS
Known Area Volatile Characteristics as of 30-JAN-1992 11:16:27
Area = 2
State = reachable
Next node to area = 2.11 (BOSTON)
Area = 3
State = reachable
Circuit = SVA-0
Next node to area = 3.5 (TRNTO)
Area = 5
State = reachable
Circuit = UNA-0
Next node to area = 3.5 (TRNTO)
Area = 11
State = reachable
Circuit = SVA-1
Next node to area = 11.9 (DALLAS)
Area = 44
State = reachable
Circuit = FZA-0
Next node to area = 44.2 (LONDON)
Thi s command di spl ays characteri sti cs for al l known areas i n the network.
3. NCP>SHOW AREA 11 SUMMARY
Known Area Volatile Summary as of 15-JUN-1992 11:16:44
Area State Circuit Next node to area
11 reachable FZA-3 11.9 (DALLAS)
Thi s command di spl ays onl y the most useful i nformati on for area 11 i n the
network.
3119
SHOW/LIST CIRCUIT
SHOW/LIST CIRCUIT
The SHOW CI RCUI T command di spl ays ci rcui t i nformati on from the vol ati l e
database. The LI ST CI RCUI T command di spl ays ci rcui t i nformati on from the
permanent database.
Format
SHOW circuit-component parameter [qualier] [...]
LIST circuit-component parameter [qualier] [...]
Circuit Components
ACTIVE CIRCUITS KNOWN CIRCUITS
CIRCUIT
Qualiers
ADJACENT NODE TO
Circuit Components
ACTIVE CIRCUITS
I ndi cates that i nformati on for al l acti ve ci rcui ts i s to be di spl ayed (SHOW onl y).
CIRCUIT circuit-id
I denti es a parti cul ar ci rcui t for whi ch i nformati on i s to be di spl ayed.
KNOWN CIRCUITS
I ndi cates that i nformati on for al l known ci rcui ts i s to be di spl ayed.
Command Parameters
CHARACTERISTICS
I ndi cates that stati c ci rcui t i nformati on i s to be di spl ayed.
COUNTERS
I ndi cates that ci rcui t error and performance stati sti cs are to be di spl ayed.
STATUS
I ndi cates that dynami c ci rcui t i nformati on i s to be di spl ayed, i ncl udi ng end node
adjacenci es and routi ng node adjacenci es.
SUMMARY
I ndi cates that dynami c ci rcui t i nformati on i s to be di spl ayed, i ncl udi ng the
routi ng adjacenci es avai l abl e to thi s ci rcui t. SUMMARY i s the defaul t di spl ay
type.
Qualiers
ADJACENT NODE node-id
I ndi cates that the di spl ay of a l i st of ci rcui ts i s to be restri cted to those ci rcui ts
l eadi ng to the speci ed adjacent node.
TO lespec
3120
SHOW/LIST CIRCUIT
Adjacent node node-id
Thi s read-onl y parameter i ndi cates an adjacent node on the ci rcui t. There can be
many adjacent nodes on an Ethernet or FDDI ci rcui t.
Block size number
Thi s read-onl y parameter i s the bl ock si ze i n bytes for the adjacent node, as
negoti ated wi th the adjacent Routi ng l ayer duri ng routi ng i ni ti al i zati on.
Designated router node-id
Thi s read-onl y val ue i s the Routi ng l ayer i denti cati on of the node that i s to be
used for routi ng to nonrouti ng nodes (end nodes) on thi s ci rcui t.
Listen timer seconds
Thi s read-onl y parameter determi nes the maxi mum ti me al l owed to el apse
before a message (a Routi ng Hel l o message or a user message) i s recei ved from
an adjacent node on the ci rcui t. The val ue can be up to 65,535. Note that
the LI STEN TI MER val ue i s three ti mes that of the HELLO TI MER ci rcui t
parameter.
Loopback name
Thi s read-onl y parameter i s the node name associ ated wi th a ci rcui t for l oopback
testi ng. I t i denti es the ci rcui t to be used for al l trafc to the l oop node.
Polling substate (VAX only)
Appl i es onl y to DDCMP CONTROL ci rcui ts. Thi s read-onl y val ue represents the
state of the tri butary as determi ned by the pol l i ng al gori thm when the mul ti poi nt
pol l i ng state i s AUTOMATI C. The pol l i ng substate i s di spl ayed as a tag on the
pol l i ng state (for exampl e, AUTOMATI C-I NACTI VE). Possi bl e val ues of the
pol l i ng substate are as fol l ows:
Acti ve
I nacti ve
Dyi ng
Dead
Substate
Thi s read-onl y val ue i s the operati onal substate of the ci rcui t. The
substate i s di spl ayed as a tag on the STATE parameter (for exampl e, ON-
SYNCHRONI ZI NG). See Tabl e C1 for a compl ete l i st of ci rcui t/l i ne substates.
Possi bl e substate val ues are as fol l ows:
Synchroni zi ng
Starti ng
Reecti ng
Loopi ng
Loadi ng
Dumpi ng
Tri ggeri ng
Autoservi ce
Autol oadi ng
Autodumpi ng
Autotri ggeri ng
Fai l ed
3121
SHOW/LIST CIRCUIT
Examples
1. NCP>SHOW KNOWN CIRCUITS STATUS
Known Circuit Volatile Status as of 15-JUN-1992 15:39:04
Circuit State Loopback Adjacent Block
Name Node Size
DMC-0 on 3.5 (TRNTO) 576
DMC-1 on -starting
UNA-0 on 2.22 (LARK) 576
2.23 (DOVE) 576
2.20 (ROBIN) 576
2.21 (THRUSH) 576
X25-INC on INC 44.2 (LONDON) 576
X25-INC2 on -synchronizing
X25-RY1 off RY1
X25-RY2 off RY2
X25-ZK off ZK
Thi s command di spl ays status i nformati on for al l known ci rcui ts connected
to a DECnet for OpenVMS node. Thi s i nformati on i ncl udes the current state
of the ci rcui t; a l oop node name (i f any) associ ated wi th the ci rcui t; and the
address, name, and bl ock si ze of the adjacent node on that ci rcui t.
2. NCP>SHOW ACTIVE CIRCUITS CHARACTERISTICS
Active Circuit Volatile Characteristics as of 15-JUN-1992 15:39:21
Circuit = DMC-0
State = on
Service = enabled
Cost = 12
Hello timer = 15
Listen timer = 30
Maximum buffers = 255
Verification = disabled
Adjacent node = 3.5 (TRNTO)
Listen timer = 30
Circuit = UNA-0
State = on
Designated router = 2.20 (ROBIN)
Cost = 1
Maximum routers allowed = 33
Router priority = 64
Hello timer = 15
Adjacent node = 2.22 (LARK)
Listen timer = 45
Circuit = X25-INC
State = on
Loopback name = INC
Cost = 20
Hello timer = 15
Listen timer = 30
Owner = Executor
Usage = incoming
Type = X.25
Adjacent node = 44.2 (LONDON)
Listen timer = 30
3122
SHOW/LIST CIRCUIT
Thi s command di spl ays ci rcui t characteri sti cs for al l ci rcui ts whose states are
ON.
3. NCP>SHOW CIRCUIT MNA-0 STATUS
Circuit Volatile Status as of 30-JAN-1992 15:45:04
Circuit State Loopback Adjacent Block
Name Node Size
MNA-0 on 2.22 (LARK) 576
MNA-0 2.23 (DOVE) 576
MNA-0 2.20 (ROBIN) 576
MNA-0 2.21 (THRUSH) 576
Thi s command di spl ays status i nformati on for ci rcui t MNA0.
4. NCP>TELL DOVE SHOW CIRCUIT MNA-0 CHARACTERISTICS
Circuit Volatile Characteristics as of 15-JUN-1992 15:46:20
Circuit = MNA-0
State = on
Designated router = 2.20 (ROBIN)
Cost = 1
Maximum routers allowed = 33
Router priority = 64
Hello timer = 15
Adjacent node = 2.20 (ROBIN)
Listen timer = 45
Circuit = MNA-0
Adjacent node = 2.11 (BOSTON)
Listen timer = 45
Circuit = MNA-0
Adjacent node = 2.22 (LARK)
Listen timer = 45
Circuit = MNA-0
Adjacent node = 2.21 (THRUSH)
Listen timer = 45
Thi s command di spl ays ci rcui t characteri sti cs for ci rcui t MNA0 on node
DOVE.
5. NCP>TELL MYNODE SHOW CIRCUIT TX-0-5 CHARACTERISTICS
Circuit Volatile Characteristics as of 30-JAN-1992 15:35:12
Circuit = TX-0-5
State = on
Substate = -synchronizing
Service = enabled
Cost = 10
Hello timer = 15
Verification = inbound
Thi s command di spl ays ci rcui t characteri sti cs for ci rcui t TX-0-5 on MYNODE.
3123
SHOW/LIST CIRCUIT
6. NCP>SHOW KNOWN CIRCUIT ADJACENT NODE BOSTON
Known Circuit Volatile Summary as of 15-JUN-1992 15:50:19
Circuit State Loopback Adjacent
Name Node
FZA-0 on 2.11 (BOSTON)
SVA-0 on 2.11 (BOSTON)
Thi s command di spl ays summary i nformati on for al l ci rcui ts connected to
adjacent node BOSTON.
7. NCP>SHOW ACTIVE CIRCUIT COUNTERS
Active Circuit Counters as of 30-JAN-1992 16:10:31
Circuit = FZA-0
>65534 Seconds since last zeroed
695803 Terminating packets received
1847598 Originating packets sent
0 Terminating congestion loss
201179 Transit packets received
200122 Transit packets sent
0 Transit congestion loss
0 Circuit down
0 Initialization failure
0 Adjacency down
1 Peak adjacencies
2057126 Data blocks sent
1975840666 Bytes sent
903317 Data blocks received
32194824 Bytes received
0 Unrecognized frame destination
0 User buffer unavailable
Circuit = MNA-0
1 Circuit down
Thi s command di spl ays counter i nformati on for al l acti ve ci rcui ts. See
Appendi x B for a descri pti on of each ci rcui t counter.
8. NCP>SHOW CIRCUIT SVA-* SUMMARY
Thi s command di spl ays dynami c ci rcui t i nformati on for al l SVA ci rcui ts,
i ncl udi ng the routi ng adjacenci es avai l abl e to those ci rcui ts.
3124
SHOW/LIST EXECUTOR
SHOW/LIST EXECUTOR
The SHOW EXECUTOR command di spl ays node i nformati on from the vol ati l e
database. The LI ST EXECUTOR command di spl ays l ocal node i nformati on from
Format
SHOW EXECUTOR parameter [qualier]
LIST EXECUTOR parameter [qualier]
Qualier
TO
Command Parameters
CHARACTERISTICS
I ndi cates that stati c l ocal node i nformati on i s to be di spl ayed.
COUNTERS
I ndi cates that l ocal node error and performance stati sti cs are to be di spl ayed.
STATUS
I ndi cates that dynami c l ocal node i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates that a summary of l ocal node i nformati on i s to be di spl ayed. Thi s i s the
Qualier
TO lespec
Active links number
Thi s read-onl y parameter represents the number of acti ve l ogi cal l i nks from the
executor to the desti nati on node.
Delay seconds
Thi s read-onl y parameter i s the average round-tri p del ay i n seconds from the
Management version n.n.n
Thi s read-onl y parameter i denti es the versi on number of the Network
Management l ayer.
NSP version n.n.n
Thi s read-onl y parameter i denti es the versi on number of the End
Communi cati on l ayer.
Physical address p-address
Thi s read-onl y parameter i s the uni que physi cal address used on a LAN to
i denti fy the executor node.
3125
SHOW/LIST EXECUTOR
Routing version n.n.n
Thi s read-onl y parameter i denti es the versi on number of the Routi ng l ayer.
Examples
1. NCP>SHOW EXECUTOR CHARACTERISTICS
Node Volatile Characteristics as of 15-JUN-1992 15:37:32
Executor node = 2.11 (RAVEN)
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 45
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.0.0
Maximum links = 128
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = routing IV
Routing timer = 600
Broadcast routing timer = 40
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 15
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Buffer size = 576
Default access = incoming and outgoing
Pipeline quota = 1500
Alias incoming = Enabled
Alias maximum links = 32
Alias node = 2.10 (CROW)
Path split policy = Normal
Maximum Declared Objects = 31
DNS interface = Enabled
IDP of ISO address = 33
DNS namespace = ENTERPRISE
Thi s command di spl ays characteri sti cs for the executor, a DECnet for
OpenVMS routi ng node. Thi s di spl ay shows val ues that you have set for thi s
node. I n addi ti on, i t provi des suppl emental i nformati on about the software
versi ons of Network Management, NSP, Routi ng, and the use of the DECdns
namespace.
3126
SHOW/LIST EXECUTOR
2. NCP>SHOW EXECUTOR STATUS
Node Volatile Status as of 15-JUN-1992 15:37:53
State = on
Physical address = AA-00-04-00-AB-04
Thi s command di spl ays status i nformati on for the executor node. Thi s format
i ncl udes the operati onal state and the physi cal address.
3. NCP>SHOW EXECUTOR SUMMARY
Node Volatile Summary as of 15-JUN-1992 15:38:04
State = on
Thi s command di spl ays summary i nformati on for the executor.
4. NCP>SHOW EXECUTOR COUNTERS
Node Counters as of 15-JUN-1992 15:38:17
1069826 Bytes sent
96120 Messages received
96120 Messages sent
1267 Connects received
1267 Connects sent
11 Response timeouts
0 Received connect resource errors
15 Maximum logical links active
34 Aged packet loss
70 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
Thi s command di spl ays counter i nformati on for both the l ocal node and the
executor node. The counters for the executor node are al ways di spl ayed. The
counters for the l ocal node are onl y di spl ayed after the rst l i nk i s establ i shed
between the executor and i tsel f.
Refer to Appendi x B for a descri pti on of each node counter.
3127
SHOW/LIST LINE
SHOW/LIST LINE
The SHOW LI NE command di spl ays l i ne i nformati on from the vol ati l e database.
The LI ST LI NE command di spl ays l i ne i nformati on from the permanent
database.
Format
SHOW line-component parameter [qualier]
LIST line-component parameter [qualier]
Line Components
ACTIVE LINES LINE
KNOWN LINES
Qualier
TO
Line Components
ACTIVE LINES
I ndi cates that i nformati on for al l acti ve l i nes i s to be di spl ayed (SHOW onl y).
KNOWN LINES
I ndi cates that i nformati on for al l known l i nes i s to be di spl ayed.
LINE line-id
I denti es a parti cul ar l i ne for whi ch i nformati on i s to be di spl ayed.
Command Parameters
CHARACTERISTICS
I ndi cates that stati c l i ne i nformati on i s to be di spl ayed.
COUNTERS
I ndi cates that l i ne error and performance stati sti cs are to be di spl ayed.
STATUS
I ndi cates that dynami c l i ne i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates that a summary of l i ne i nformati on i s to be di spl ayed. Thi s i s the
Qualier
TO lespec
3128
SHOW/LIST LINE
Examples
1. NCP>SHOW ACTIVE LINES CHARACTERISTICS
Active Line Volatile Characteristics as of 30-JAN-1992 17:54:19
Line = FZA-0
Receive buffers = 10
Controller = normal
Protocol = FDDI
Service timer = 4000
Hardware address = 08-00-2B-2D-88-7B
Device buffer size = 1498
Requested TRT = 8000
Valid transmission time = 2620
Restricted token timeout = 1000
Ring purger enable = on
NIF target = 00-00-00-00-00-00
SIF configuration target = 00-00-00-00-00-00
SIF operation target = 00-00-00-00-00-00
Echo target = 00-00-00-00-00-00
Echo data = 55
Echo length = 1
Thi s command di spl ays l i ne characteri sti cs for al l acti ve l i nes (l i nes i n ON
state) for the executor. Thi s di spl ay shows val ues for l i ne parameters that
you have set for i ndi vi dual l i nes.
2. NCP>SHOW KNOWN LINES STATUS
Known Line Volatile Status as of 15-JUN-1992 10:21:27
Line = MFA-0
State = on
Negotiated TRT = 99840
Duplicate address flag = unknown
Upstream neighbor = 08-00-2B-1C-0D-BB
Old upstream neighbor = 00-00-00-00-00-00
Upstream neighbor DA flag = unknown
Downstream neighbor = 00-00-00-00-00-00
Old downstream neighbor = 00-00-00-00-00-00
Ring purger state = off
Ring error reason = no error
Neighbor PHY type = A
Link error estimate = 15
Reject reason = none
Thi s command di spl ays status i nformati on for al l known l i nes connected to
the l ocal node. Thi s di spl ay shows the current state of the l i ne.
3. NCP>SHOW LINE MNA-0 SUMMARY
Line Volatile Summary as of 15-JUN-1992 10:22:11
Line State
MNA-0 on
Thi s command di spl ays summary i nformati on for l i ne MNA0.
3129
SHOW/LIST LINE
4. NCP>TELL LARK SHOW LINE MNA-0 CHARACTERISTICS
Line Volatile Characteristics as of 15-JUN-1992 10:23:41
Line = MNA-0
Receive buffers = 9
Controller = normal
Protocol = Ethernet
Hardware address = AA-00-03-00-00-C0
Buffer size = 1498
Thi s command di spl ays l i ne characteri sti cs for l i ne MNA0 on node LARK.
5. NCP>SHOW LINE FZA-0 COUNTERS
Line Counters as of 30-JAN-1992 10:25:43
Line = FZA-0
13438 Multicast blocks received
0 Receive failure
1846203 Multicast bytes received
0 Data overrun
9386 Multicast blocks sent
1058642 Multicast bytes sent
0 Send failure
0 System buffer unavailable
>4294967294 MAC frame count
0 MAC error count
0 MAC lost count
1 Ring initializations initiated
2 Ring initializations received
1 Ring beacons initiated
0 Duplicate address test failures
0 Duplicate tokens detected
0 Ring purge errors
0 FCI strip errors
0 Traces initiated
0 Traces received
0 Directed beacons received
0 Elasticity buffer errors
0 LCT rejects
0 LEM rejects
0 Link errors
2 Connections completed
Thi s command shows the l i ne counters for FDDI l i ne FZA0. Refer to
Appendi x B for a compl ete descri pti on of each l i ne counter.
VAX
6.
NCP>SHOW LINE DMC-* STATUS
Thi s command di spl ays status i nformati on for al l DMC l i nes connected to the
executor.
3130
SHOW LINKS
SHOW LINKS
The SHOW LI NKS command di spl ays l i nk i nformati on from the vol ati l e
database.
Format
SHOW link-component parameter [qualier]
Link Components
KNOWN LINKS LINK
KNOWN LINKS WITH NODE
Qualier
TO
Link Components
KNOWN LINKS
I ndi cates that i nformati on for al l known l i nks i s to be di spl ayed.
KNOWN LINKS WITH NODE node-id
I ndi cates that i nformati on for al l known l i nks to the desi gnated node i s to be
di spl ayed.
LINK link-number
Di spl ays i nformati on about the speci c l i nk.
Command Parameters
CHARACTERISTICS
Di spl ays stati c l i nk i nformati on.
STATUS
Di spl ays dynami c l i nk i nformati on.
SUMMARY
Di spl ays a summary of l i nk i nformati on. Thi s i s the defaul t di spl ay type.
Qualier
TO lespec
State
Thi s read-onl y val ue i s the operati onal state of the l i nk. See Appendi x C for a
compl ete l i st of l i nk states. Possi bl e state val ues are as fol l ows:
CI sendi ng
CI ACKed
CI recei vi ng
Cl osed
CC sendi ng
3131
SHOW LINKS
Run
DI recei ved
DI sendi ng
Examples
1. NCP>SHOW KNOWN LINKS
4104 11.9 (DALLAS) 20600090 GRAY 3116 MAIL
8229 3.5 (TRNTO) 2060014C DAVIS 7217 NML
3125 2.17 (NYC) 2060023D REMACP 5175 THOMPSON_1
Thi s command di spl ays l i nk i nformati on for al l l i nks known to the l ocal
node. Thi s format i s the same for al l three di spl ay types. The di spl ay shows
the l ocal l i nk number, node name and address to whi ch the l i nks appl y, the
process i denti cati on number (PI D), the process associ ated wi th the l i nk, the
remote l i nk, and the remote object or process name.
2. NCP>SHOW KNOWN LINKS WITH NODE DALLAS
4104 11.9 (DALLAS) 20600090 GRAY 3116 MAIL
Thi s command di spl ays l i nk i nformati on for al l acti ve l i nks wi th remote node
DALLAS.
3. NCP>SHOW KNOWN LINKS CHARACTERISTICS
Known Link Volatile Characteristics as of 30-JAN-1992 15:00:42
Link = 8245
State = run
PID = 264006AB
Delay time = 1
Remote link = 9270
Remote user = TERM
Username = MARTIN
Process name = MARTIN
Link = 9270
State = CI received
PID = 26400091
Delay time = 1
Remote link = 8245
Remote user = BARNETT
Username = SYSTEM
Process name = REMACP
Thi s command di spl ays l i nk characteri sti cs for al l l i nks. Refer to Appendi x C
for a compl ete descri pti on of each l i nk state.
3132
SHOW/LIST LOGGING
SHOW/LIST LOGGING
The SHOW LOGGI NG command di spl ays l oggi ng i nformati on from the vol ati l e
database. The LI ST LOGGI NG command di spl ays l oggi ng i nformati on from the
permanent database.
Format
SHOW logging-component parameter [qualier] [...]
LIST logging-component parameter [qualier] [...]
Logging Components
ACTIVE LOGGING LOGGING FILE
KNOWN LOGGING LOGGING MONITOR
LOGGING CONSOLE
Qualiers
KNOWN SINKS TO
SINK NODE
Logging Components
ACTIVE LOGGING
I ndi cates that i nformati on for al l acti ve l oggi ng i s to be di spl ayed (SHOW onl y).
KNOWN LOGGING
I ndi cates that i nformati on for al l known l oggi ng i s to be di spl ayed.
LOGGING CONSOLE
I ndi cates that i nformati on for the l oggi ng consol e i s to be di spl ayed.
LOGGING FILE
I ndi cates that i nformati on for the l oggi ng l e i s to be di spl ayed.
LOGGING MONITOR
I ndi cates that i nformati on for the l oggi ng moni tor i s to be di spl ayed.
Command Parameters
EVENTS
I ndi cates that al l stati c l oggi ng i nformati on i s to be di spl ayed.
STATUS
I ndi cates that dynami c l oggi ng i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates that a summary of l oggi ng i nformati on i s to be di spl ayed. Thi s i s the
3133
SHOW/LIST LOGGING
Qualiers
KNOWN SINKS
I ndi cates that i nformati on for al l known si nks i s to be di spl ayed.
SINK NODE node-id
I denti es a parti cul ar si nk node for whi ch i nformati on i s to be di spl ayed. I f you
do not i ncl ude thi s parameter, NCP di spl ays onl y l ocal node l oggi ng.
TO lespec
Examples
1. NCP>SHOW LOGGING FILE EVENTS KNOWN SINKS
Logging Volatile Events as of 15-JUN-1992 13:40:54
Logging sink type = file
Sink node = 3.5 (TRNTO)
Events = 4.0-5
Sink node = 11.9 (DALLAS)
Events = 0.0-7
Events = 2.0-1
Events = 5.0-4
Thi s command di spl ays events bei ng l ogged to the l oggi ng l e component as
speci ed for al l known si nks. Thi s di spl ay l i sts the si nk node, the source for
events, and the actual events that are l ogged to the l oggi ng l e at that node.
2. NCP>SHOW ACTIVE LOGGING STATUS KNOWN SINKS
Active Logging Status as of 15-JUN-1992 14:02:15
Logging sink type = console
Sink Node Source Events State Name
3.5 (TRNTO) DMC-0 4.0-5,8-10 on
5.0-4
3.5 (TRNTO) DMC-0 4.0-5,8-10 on NET.LOG
5.0-4
11.9 (DALLAS) DMC-3 5.0-4
11.9 (DALLAS) 0.0-7
2.0-1
Thi s command di spl ays status i nformati on for al l acti ve l oggi ng at al l known
si nks for executor TRNTO. Thi s di spl ay i denti es each l oggi ng component
and i nformati on parti cul ar to that component. The status format i s si mi l ar to
the events format, except that the name of the component and i ts operati onal
state are i ncl uded i n thi s di spl ay.
3134
SHOW/LIST LOGGING
3. NCP>SHOW KNOWN LOGGING SUMMARY SINK NODE TRNTO
Known Logging Volatile Summary as of 15-JUN-1992 15:30:20
Logging sink type = monitor
4.430 (TRNTO) (All sources) 0.0-9 on
(All sources) 2.0-1
(All sources) 4.2-13 15-16
18-19
(All sources) 5.0-18
(All sources) 128.0-4
Thi s command di spl ays summary i nformati on for al l known l oggi ng to node
TRNTO. The summary format i s the same as the events format.
3135
SHOW/LIST MODULE CONFIGURATOR
The SHOW MODULE CONFI GURATOR command di spl ays i nformati on about
the Ethernet congurator modul e from the vol ati l e database. The LI ST MODULE
CONFI GURATOR command di spl ays i nformati on about the congurator modul e
Format
SHOW MODULE CONFIGURATOR circuit-qualier parameter [qualier]
LIST MODULE CONFIGURATOR circuit-qualier parameter [qualier]
Circuit Qualiers
Qualier
TO
Circuit Qualiers
CIRCUIT circuit-id
Appl i es onl y to Ethernet ci rcui ts. I ndi cates that congurator i nformati on shoul d
be di spl ayed onl y for the Ethernet ci rcui t i denti ed by circuit-id.
KNOWN CIRCUITS
Appl i es onl y to Ethernet ci rcui ts. I ndi cates that congurator i nformati on shoul d
be di spl ayed for al l known Ethernet ci rcui ts.
Command Parameters
CHARACTERISTICS
I ndi cates that dynami c i nformati on about al l acti ve systems on the speci ed
Ethernet ci rcui ts i s to be di spl ayed. (Speci fyi ng CHARACTERI STI CS or STATUS
resul ts i n a si mi l ar di spl ay.)
STATUS
I ndi cates that dynami c i nformati on about al l acti ve systems on the speci ed
Ethernet ci rcui ts i s to be di spl ayed. (Speci fyi ng CHARACTERI STI CS or STATUS
resul ts i n a si mi l ar di spl ay.)
SUMMARY
I ndi cates that the onl y i nformati on to be di spl ayed i s the l i st of ci rcui ts bei ng
moni tored and the l ength of ti me survei l l ance has been mai ntai ned. Thi s i s the
Qualier
TO lespec
3136
Circuit name
Thi s read-onl y parameter i denti es the ci rcui t for whi ch survei l l ance i s bei ng
mai ntai ned.
Device type device-type
Thi s read-onl y val ue i denti es the type of devi ce over whi ch the remote system
i s communi cati ng on the ci rcui t. The device-type val ue represents one of the
standard l i ne devi ces (for exampl e, UNA or FZA.)
Elapsed time hours:minutes:seconds
Thi s read-onl y val ue i ndi cates the amount of ti me that survei l l ance has been
enabl ed on the ci rcui t. The hours val ue i s a deci mal i nteger up to 65,535;
the minutes and seconds val ues are deci mal i ntegers i n the range 0 to 59 (for
exampl e, 19:48:24).
Function list
Thi s read-onl y parameter l i sts the mai ntenance functi ons that the remote system
supports. The l i st consi sts of one or more of the fol l owi ng i tems:
Item Meaning
Boot Remote control l ed boot
Counters Data l i nk counter can be read
Dump Upl i ne dump
Load Mul ti bl ock downl i ne l oad
Loop Loopback
Pri mary Pri mary l oader
Hardware address h-address
Thi s read-onl y val ue i s the hardware address assi gned to the Ethernet control l er
at the remote system.
Maintenance version n.n.n
Thi s read-onl y val ue i ndi cates the mai ntenance protocol versi on of the remote
system.
Thi s read-onl y val ue represents the physi cal address of a remote system on the
Ethernet. The val ue i s the uni que physi cal address that the node has set for i tsel f
or, i f the node has not set a physi cal address, the hardware address associ ated
wi th the nodes devi ce control l er.
Surveillance ag
Thi s read-onl y val ue i ndi cates whether survei l l ance i s enabl ed or di sabl ed for the
system i ndi cated.
Surveillance control
Thi s read-onl y val ue i ndi cates whether a l i st of acti ve systems i s to be kept for
the i ndi cated ci rcui t. A control val ue of di sabl ed means that the l i st i s not bei ng
kept (thi s i s the defaul t val ue). A control val ue of enabl ed means that the l i st i s
bei ng kept.
3137
Time of last report day-month hour:minute:second
Thi s read-onl y val ue i s the date and ti me the remote system l ast reported i n on
a ci rcui t under survei l l ance. The day val ue i s a deci mal i nteger i n the range 1 to
31, month i s the name of the month, hour i s a deci mal i nteger i n the range 0 to
23, and minuteand second are deci mal i ntegers i n the range 0 to 59 (for exampl e,
16-JUL 14:30:03).
Examples
1. NCP>SHOW CONFIGURATOR KNOWN CIRCUITS SUMMARY TO PRINTFILE
Module Configurator Volatile Summary as of 15-JUN-1992 08:55:21
Circuit Surveillance Elapsed Time
MNA-0 enabled 00:12:31
Thi s command causes summary i nformati on about survei l l ance on al l known
Ethernet ci rcui ts to be di rected to the l e PRI NTFI LE.
2. NCP>SHOW MODULE CONFIGURATOR KNOWN CIRCUITS STATUS
Module Configurator Volatile Status as of 10-Jul-1992 13:01:23
Circuit name = SVA-0
Surveillance flag = enabled
Elapsed time = 02:29:11
Physical address = AA-00-04-00-5D-FF
Time of last report = 10-Jul 13:03:35
Maintenance version = V3.0.0
Function list = Loop, Data link counters
Hardware address = 08-00-2B-02-39-0F
Device type = SVA
Physical address = AA-00-04-00-42-DD
Function list = Loop, Console carrier, Data link counters
Hardware address = 08-00-2B-18-38-E2
Device type = MNA
Physical address = 08-00-2B-24-42-21
Function list = Loop
Hardware address = 08-00-2B-24-42-21
Device type = MFA
Thi s command di spl ays i nformati on about acti ve systems on al l Ethernet
ci rcui ts known to the executor node.
3138
SHOW/LIST MODULE X25-ACCESS (Remote management only)
The SHOW MODULE X25-ACCESS command di spl ays network names and
parameters of the X.25 Access modul e from the vol ati l e database. The LI ST
MODULE X25-ACCESS command di spl ays networks and parameters of the X.25
Access modul e from the permanent database.
Note
Format
SHOW MODULE X25-ACCESS network-qualier parameter [qualier]
LIST MODULE X25-ACCESS network-qualier parameter [qualier]
Network Qualiers
Qualier
TO
Network Qualiers
KNOWN NETWORKS
Di spl ays i nformati on about a speci c X.25 network or about al l of the X.25
networks accessed through any connector nodes.
Command Parameters
CHARACTERISTICS
I ndi cates that stati c X25-ACCESS i nformati on i s to be di spl ayed.
STATUS
I ndi cates that dynami c X25-ACCESS i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates that a summary of X25-ACCESS i nformati on i s to be di spl ayed. Thi s i s
the defaul t di spl ay type.
Qualier
TO lespec
Examples
1. NCP>SHOW MODULE X25-ACCESS KNOWN NETWORKS STATUS TO MYFILE.NET
Thi s command wri tes status i nformati on for al l known X.25 networks to the
l e named MYFI LE.NET.
3139
2. NCP>SHOW MODULE X25-ACCESS NETWORK PSS1 SUMMARY
Module X25-Access Volatile Summary as of 30-JAN-1992 12:00:56
Network = PSS1
Node = 13.4 (EGRET)
Thi s command di spl ays stati c network i nformati on about the X.25 network
named PSS1.
3140
SHOW/LIST MODULE X25-PROTOCOL (Remote management only)
The SHOW MODULE X25-PROTOCOL command di spl ays the parameters of the
protocol modul e from the vol ati l e database. The LI ST MODULE X25-PROTOCOL
command di spl ays the protocol modul e parameters stored i n the permanent
database. Note that the component qual i er i s opti onal .
Note
Format
SHOW MODULE X25-PROTOCOL [component-qualier] parameter [qualier]
LIST MODULE X25-PROTOCOL [component-qualier] parameter [qualier]
Component Qualiers
DTE KNOWN DTES
GROUP KNOWN GROUPS
Qualier
TO
Component Qualiers
DTE dte-address
KNOWN DTES
Di spl ays i nformati on about the speci ed DTE or about al l known DTEs.
I f you speci fy the DTE qual i er, you must associ ate wi th i t ei ther of the fol l owi ng
parameters:
network.
GROUP group-name
KNOWN GROUPS
Di spl ays i nformati on about the speci ed group or about al l known groups.
KNOWN NETWORKS
Di spl ays i nformati on about the speci ed network or about al l known networks.
Command Parameters
CHARACTERISTICS
Di spl ays stati c modul e i nformati on.
3141
COUNTERS
Di spl ays DTE error and performance stati sti cs. Does not appl y to the LI ST
MODULE X25-PROTOCOL command.
STATUS
Di spl ays dynami c modul e i nformati on. Does not appl y to the LI ST MODULE
X25-PROTOCOL command.
SUMMARY
Di spl ays a summary of modul e i nformati on. Thi s i s the defaul t di spl ay type.
Qualier
TO lespec
Speci es the output l e. I f you omi t thi s parameter, the defaul t l e i s
SYS$OUTPUT.
Active channels count
Thi s read-onl y parameter i s the count of known swi tched vi rtual ci rcui t (SVC)
l ogi cal channel numbers currentl y i n use. Thi s counter appl i es onl y to those
channel s dened by the CHANNELS parameter of the SET MODULE X25-
PROTOCOL command. The channel s can be i n use for ei ther outgoi ng or
i ncomi ng SVCs.
Active switched count
Thi s read-onl y parameter i s the count of swi tched vi rtual ci rcui ts (SVCs)
currentl y i n use.
Maximum channels number
Thi s read-onl y parameter i ndi cates the number of l ogi cal channel s dened.
Examples
1. NCP>SHOW MODULE X25-PROTOCOL NETWORK FRED CHARACTERISTICS
Module X25-Protocol Volatile Characteristics as of 30-JAN-1992 17:55:24
Network = FRED
Profile = PSS
Thi s command di spl ays modul e characteri sti cs for the X25-PROTOCOL
modul e.
3142
2. NCP>SHOW MODULE X25-PROTOCOL KNOWN DTES CHARACTERISTICS
Known Module X25-Protocol Volatile Characteristics as of 30-JAN-1992 18:07:49
DTE = 12345
Network = TALOS
Line = KMV-0-0
Channels = 31-1
Maximum channels = 31
Default data = 128
Default window = 2
Maximum data = 1024
Maximum window = 7
Maximum clears = 6
Maximum resets = 6
Maximum restarts = 6
Call timer = 200
Clear timer = 180
Reset timer = 180
Restart timer = 180
Interface mode = DTE
DTE = 54321
Network = FRED
Line = DPV-0-0
Channels = 64-1
Maximum channels = 64
Default data = 128
Default window = 2
Maximum data = 1024
Maximum window = 7
Maximum clears = 6
Maximum resets = 6
Maximum restarts = 6
Call timer = 200
Clear timer = 180
Reset timer = 180
Restart timer = 180
Interface mode = DTE
Thi s command di spl ays characteri sti cs for al l DTEs known to the X25-
PROTOCOL modul e.
3. NCP>SHOW MODULE X25-PROTOCOL DTE 123456789 NETWORK -
_ PSS-COMBINATION STATUS
Module X25-Protocol Volatile Status as of 30-JAN-1992 11:50:12
DTE Network State Active Active
Channels Switched
123456789 PSS_COMBINATION on -running 0 0
Thi s command di spl ays the status of DTE 123456789 i n the network PSS-
COMBI NATI ON.
3143
4. NCP>SHOW MODULE X25-PROTOCOL DTE 123456789 NETWORK FRED COUNTERS
Module X25-Protocol Counters as of 30-JAN-1992 18:08:26
DTE = 54321
Network = FRED
7144 Seconds since last zeroed
11705 Bytes sent
2 Calls received
2 Calls sent
0 Fast selects received
0 Fast selects sent
2 Maximum switched circuits active
1 Maximum channels active
0 Received call resource errors
0 Locally initiated resets
0 Remotely initiated resets
0 Network initiated resets
0 Restarts
Thi s command di spl ays i nformati on about each DTE counter. Refer to
Appendi x B for a descri pti on of each DTE counter.
5. NCP>SHOW MODULE X25-PROTOCOL KNOWN GROUPS CHARACTERISTICS
Known Module X25-Protocol Volatile Characteristics as of 30-JAN-1992 18:13:50
Group DTE Network Number Type
SEALS 54321 FRED 54 bilateral
WALES 54321 FRED 6
Thi s command di spl ays i nformati on about each cl osed user group.
3144
SHOW/LIST MODULE X25-SERVER/X29-SERVER (Remote management only)
The SHOW MODULE X25-SERVER and SHOW MODULE X29-SERVER
commands di spl ay the parameters of the X.25 and X.29 cal l handl ers stored i n the
vol ati l e database. The LI ST MODULE X25-SERVER and LI ST MODULE X29-
SERVER commands di spl ay the parameters of the X.25 and X.29 cal l handl ers
stored i n the permanent database.
Note
Format
SHOW MODULE X25-SERVER [component-qualier] parameter [qualier]
SHOW MODULE X29-SERVER [component-qualier] parameter [qualier]
LIST MODULE X25-SERVER [component-qualier] parameter [qualier]
LIST MODULE X29-SERVER [component-qualier] parameter [qualier]
Component Qualiers
Qualier
TO
Component Qualiers
DESTINATION name
KNOWN DESTINATIONS
Di spl ays i nformati on about the speci ed desti nati on or about al l known
desti nati ons.
Command Parameters
CHARACTERISTICS
Di spl ays stati c modul e i nformati on.
COUNTERS
Di spl ays modul e error and performance stati sti cs. Does not appl y to the LI ST
MODULE X25-SERVER or LI ST MODULE X29-SERVER command.
STATUS
Di spl ays dynami c modul e i nformati on. Does not appl y to the LI ST MODULE
X25-SERVER or LI ST MODULE X29-SERVER command.
SUMMARY
Di spl ays a summary of modul e i nformati on. Thi s i s the defaul t di spl ay type.
3145
Qualier
TO lespec
Speci es the output l e. I f you omi t thi s parameter, the defaul t l e i s
SYS$OUTPUT.
Active circuits count
Thi s read-onl y parameter i ndi cates the number of ci rcui ts the modul e currentl y
has open.
Examples
1. NCP>SHOW MODULE X25-SERVER CHARACTERISTICS
Module X25-Server Volatile Characteristics as of 30-JAN-1992 12:04:58
Thi s command di spl ays characteri sti cs for the X25-SERVER modul e.
2. NCP>LIST MODULE X25-SERVER DESTINATION XTR CHARACTERISTICS
Module X25-Server Permanent Characteristics as of 30-JAN-1992 12:04:27
Destination = XTR
Object = PSIXTR
Priority = 30
Sending DTE = 234273412345
Subaddresses = 33-35
Thi s command di spl ays server modul e characteri sti cs from the permanent
database for desti nati on XTR.
3. NCP>SHOW MODULE X25-SERVER STATUS
Module X25-Server Volatile Status as of 30-JAN-1992 12:05:13
Active circuits = 1
State = on
Thi s command di spl ays status i nformati on for the X25-SERVER modul e.
4. NCP>SHOW MODULE X25-SERVER COUNTERS
Module X25-Server Counters as of 30-JAN-1992 12:05:21
7 Maximum circuits active
2 Incoming calls rejected, no resources
Thi s command di spl ays counter i nformati on for each server modul e. See
Appendi x B for a descri pti on of each server modul e counter.
3146
SHOW/LIST NODE
SHOW/LIST NODE
The SHOW NODE command di spl ays node i nformati on from the vol ati l e
database. The LI ST NODE command di spl ays node i nformati on from the
permanent database avai l abl e to the l ocal node.
Format
SHOW node-component parameter [qualier]
LIST node-component parameter [qualier]
Node Components
ACTIVE NODES LOOP NODES
ADJACENT NODES NODE
KNOWN NODES
Qualier
TO
Node Components
ACTIVE NODES
For a routi ng node, i ndi cates that i nformati on about al l reachabl e nodes i s to be
di spl ayed. For a nonrouti ng node (end node), i ndi cates that i nformati on about the
executor i s to be di spl ayed. Opti onal l y, you can associ ate the fol l owi ng CI RCUI T
parameter wi th thi s parameter:
CI RCUI T ci rcui t-i d Speci es that the di spl ay of a l i st of nodes i s to be
restri cted to those nodes adjacent to the speci ed ci rcui t.
ADJACENT NODES
I ndi cates that i nformati on about al l adjacent nodes i s to be di spl ayed. Adjacent
nodes are those the executor percei ves Routi ng can reach that are separated from
the executor by a si ngl e ci rcui t. Each occurrence of a node on a di fferent ci rcui t
appears as a separate adjacent node. Opti onal l y, you can associ ate the fol l owi ng
CI RCUI T parameter wi th thi s parameter:
KNOWN NODES
I ndi cates that i nformati on about al l known nodes i s to be di spl ayed. Opti onal l y,
you can associ ate the fol l owi ng CI RCUI T parameter wi th thi s parameter:
LOOP NODES
I ndi cates that i nformati on about al l l oop nodes i s to be di spl ayed.
NODE node-id
I denti es a parti cul ar node about whi ch i nformati on i s to be di spl ayed.
3147
SHOW/LIST NODE
Command Parameters
CHARACTERISTICS
I ndi cates that stati c node i nformati on i s to be di spl ayed.
COUNTERS
I ndi cates that node error and performance stati sti cs are to be di spl ayed.
STATUS
I ndi cates that dynami c node i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates a summary of node i nformati on i s to be di spl ayed. Thi s i s the defaul t
di spl ay type.
Qualier
TO lespec
Active links number
Thi s read-onl y parameter represents the number of acti ve l ogi cal l i nks from the
Circuit circuit-id
Thi s read-onl y parameter i denti es the ci rcui t used to get to a remote node.
Cost number
Thi s read-onl y parameter represents the total cost over the current path to the
desti nati on node. The DECnet Routi ng l ayer routes messages (data) al ong the
path between two nodes wi th the smal l est cost. Cost i s a posi ti ve i nteger val ue.
Delay seconds
Thi s read-onl y parameter i s the average round-tri p del ay i n seconds from the
Hops number
Thi s read-onl y parameter i ndi cates the number of hops from the executor node
to a desti nati on node. A hop i s a val ue assi gned by the Routi ng l ayer that
represents the l ogi cal di stance between two nodes on a network.
Management version n.n.n
Thi s read-onl y parameter i denti es the versi on number of the Network
Management l ayer.
Next node node-id
Thi s read-onl y parameter i ndi cates the address and name of the next node on the
ci rcui t used to get to the node whose status i s bei ng di spl ayed. Knowi ng whi ch
node i s the partner on the next hop of the path to the desti nati on node ai ds i n
traci ng the path to that desti nati on over a l arge number of hops.
NSP version n.n.n
Thi s read-onl y parameter i denti es the versi on number of the End
Communi cati on l ayer (ECL).
3148
SHOW/LIST NODE
Thi s read-onl y parameter i s the physi cal address that i denti es the executor
node.
Routing version n.n.n
Thi s read-onl y parameter i denti es the versi on number of the Routi ng l ayer.
Type node-type
Thi s read-onl y parameter i ndi cates the type of the speci ed node. The val ues of
node-typeare as fol l ows:
Nonrouti ng I I I
Nonrouti ng I V
Routi ng I V
Routi ng I I I
Area
I f the speci ed node i s not adjacent to the l ocal node, the node-typewi l l be bl ank.
Examples
1. NCP>SHOW ACTIVE NODES CHARACTERISTICS
Active Node Volatile Characteristics as of 15-JUN-1992 13:38:34
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 45
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V3.2.0
Maximum links = 128
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = routing IV
Routing timer = 600
Maximum address = 1023
Maximum cost = 1022
Maximum hops = 15
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Buffer size = 576
Default access = incoming and outgoing
Pipeline quota = 1500
Alias maximum links = 32
Alias node = 2.10 (CLUSTR)
Path split policy = Normal
3149
SHOW/LIST NODE
Remote node = 3.5 (TRNTO)
Nonprivileged user id = NETNONPRIV
Remote node = 11.9 (DALLAS)
Remote node = 12.34 (MYNODE)
Inbound = router
Remote node = 2.13 (KANSAS)
Remote node = 2.17 (NYC)
Loop node = 0 (TESTER)
Thi s command di spl ays characteri sti cs for al l acti ve nodes. Thi s di spl ay
shows val ues that you have set for both the l ocal node and remote nodes.
2. NCP>SHOW NODE TRNTO STATUS
Node Volatile Status as of 15-JUN-1992 13:39:05
Node State Active Delay Type Cost Hops Line
Links
3.5 (ROBIN) reachable 1 2 routing IV 1 1 DMC-0
Thi s command di spl ays status i nformati on about remote node ROBI N. Thi s
format i ncl udes the fol l owi ng i nformati on:
Node name and address
Routi ng state (reachabl e or unreachabl e)
Acti ve l i nks associ ated wi th the node
Del ay ti me requi red to set the retransmi ssi on (esti mated round tri p
del ay).
Node type (phase I I , routi ng I I I , routi ng I V, nonrouti ng I I I , nonrouti ng I V,
or area).
Mi ni mum total path cost to the node. Thi s val ue represents the cost of
the actual path a packet wi l l use to get to thi s node.
Mi ni mum total hops to the node. Note that the mi ni mum cost path may
be di fferent from the mi ni mum hops path. Thi s val ue does not necessari l y
prevent the actual path from bei ng used.
Li ne associ ated wi th the node, that i s, the l i ne over whi ch trafc to the
node i s currentl y bei ng routed.
Ful l status i nformati on i s di spl ayed onl y for reachabl e nodes.
3150
SHOW/LIST NODE
3. NCP>SHOW KNOWN NODES SUMMARY
State = on
Active links = 2
Links
1.2 (TRNTO) reachable FZA-0 1.55
1.3 (DALLAS) reachable 1 2 FZA-0 1.55
1.4 (KANSAS) reachable 1 4 FZA-0 1.55
1.9 (DENVER) unreachable
1.15 (BANGOR) unreachable
1.17 (NYC) reachable FZA-0 1.55
Thi s command di spl ays summary i nformati on for al l known nodes. The
summary format contai ns a subset of the i nformati on di spl ayed i n the status
format. Note that the di spl ay al so shows l oop nodes and the l i ne associ ated
wi th the l oop node name.
4. NCP>SHOW NODE TRNTO COUNTERS
Node Counters as of 15-JUN-1992 13:40:08
Remote node = 3.5 (TRNTO)
231849 Bytes sent
27703 Messages received
27556 Messages sent
56 Connects received
5 Connects sent
12 Response timeouts
0 Received connect resource errors
Thi s command di spl ays counter i nformati on about remote node TRNTO. Note
that remote node counters are a subset of those mai ntai ned for the l ocal node.
Refer to Appendi x B for a descri pti on of each node counter.
5. NCP>SET NODE LOCAL LINE DMC-0
NCP>SHOW LOOP NODES STATUS
Loop Node Volatile Status as of 15-JUN-1992 13:43:19
Node State Active Delay Type Cost Hops Line
Links
0 (LOCAL) DMC-0
Thi s command di spl ays status i nformati on about al l l oop nodes.
6. NCP>SHOW NODE M* STATUS
Thi s command di spl ays status i nformati on about al l nodes whose names
begi n wi th M.
7. NCP>SHOW NODE %SU STATUS
Thi s command requests a di spl ay of status i nformati on of al l nodes that have
three-l etter node names and SU as the second and thi rd characters of thei r
names.
3151
SHOW/LIST OBJECT
SHOW/LIST OBJECT
The SHOW OBJECT command di spl ays object i nformati on from the vol ati l e
database. The LI ST OBJECT command di spl ays object i nformati on from the
permanent database.
Format
SHOW object-component parameter [qualier]
LIST object-component parameter [qualier]
Object Components
Qualier
TO
Object Components
KNOWN OBJECTS
I ndi cates that i nformati on about al l known objects i s to be di spl ayed.
OBJECT object-name
I denti es a parti cul ar object about whi ch i nformati on i s to be di spl ayed.
Command Parameters
CHARACTERISTICS
I ndi cates that stati c object i nformati on i s to be di spl ayed. The SHOW OBJECT
CHARACTERI STI CS command di spl ays onl y those parameters that you have
dened.
STATUS
I ndi cates that dynami c object i nformati on i s to be di spl ayed.
SUMMARY
I ndi cates that a summary of object i nformati on i s to be di spl ayed. Thi s i s the
Qualier
TO lespec
Examples
1. NCP>SHOW OBJECT MAIL CHARACTERISTICS
Object Volatile Characteristics as of 15-JUN-1992 13:46:22
Object = MAIL
Number = 27
File id = MAIL.EXE
User id = NETNONPRIV
Proxy access = outgoing
Alias outgoing = Enabled
3152
SHOW/LIST OBJECT
Thi s command di spl ays object characteri sti cs for the MAI L object on a
DECnet for OpenVMS node. Thi s di spl ay shows val ues that you have set for
the object.
2. NCP>SHOW OBJECT MAIL CHARACTERISTICS TO MAIL_CHARS.NET
Thi s command copi es MAI L object characteri sti cs from the vol ati l e database
to a l e named MAI L_CHARS.NET.
3. NCP>SHOW OBJECT NML SUMMARY
Object Volatile Summary as of 15-JUN-1992 12:07:44
Object Number File/PID User Id Password
NML 19 NML.EXE NML$SERVER BLUESKIES
Thi s command di spl ays object characteri sti cs for the NML object.
4. NCP>SHOW OBJECT I* SUMMARY
Thi s command di spl ays object characteri sti cs for al l objects whose names
begi n wi th I .
3153
TELL
TELL
The TELL command speci es an NCP command for executi on at a remote node.
The NCP command i s entered as a parameter to the TELL command. Note that
the TELL command sets the executor to the remote node onl y for a si ngl e NCP
command.
Format
TELL node-component parameter [...] command
Node Component
node-spec
Node Component
node-spec
Speci es a node name or address opti onal l y fol l owed by access control
i nformati on. Use one of the fol l owi ng formats:
node-id
node-id"user password account"
The node-id can be a l ogi cal name. You can overri de access control i n a l ogi cal
name by speci fyi ng expl i ci t access control i nformati on i n the command.
Command Parameters
ACCOUNT account
I denti es the user s account for access control veri cati on at the desi gnated
executor node. Thi s parameter i s not requi red for DECnet for OpenVMS nodes
si nce DECnet for OpenVMS does not use thi s i nformati on to val i date access
control .
PASSWORD password
I denti es the user s password for access control veri cati on at the desi gnated
executor node.
USER user-id
I denti es the user s I D for access control veri cati on at the desi gnated executor
node.
Comments
You cannot use the TELL prex wi th the CLEAR EXECUTOR NODE, COPY
KNOWN NODES, or SET EXECUTOR NODE commands.
3154
TELL
Examples
1. NCP>TELL 3.5 SET KNOWN LINES ALL
Thi s command sets the executor to node 3.5 where the SET KNOWN LI NES
ALL command executes.
2. NCP>TELL TRNTO"GRAY MARY" SHOW KNOWN LINES
.
.
.
Thi s command uses access control i nformati on to set the executor to
node TRNTO where the SHOW KNOWN LI NES command executes. The
i nformati on i s di spl ayed l ocal l y.
3. NCP>TELL TRNTO USER SYSTEM PASSWORD MANAGER ZERO EXECUTOR
Thi s command uses an al ternate access control format to set the executor to
node TRNTO where the ZERO EXECUTOR command executes.
3155
TRIGGER NODE
TRIGGER NODE
The TRI GGER NODE command starts the bootstrap mechani sm of a target node
to al l ow the node to l oad i tsel f. Use thi s command to i ni ti ate the l oadi ng sequence
for an unattended system.
Format
TRIGGER node-component parameter [...]
Node Component
NODE
Node Component
NODE node-id
I denti es the node whose bootstrap i s to be tri ggered.
Command Parameters
Appl i es onl y to nodes on FDDI and Ethernet ci rcui ts. Speci es the physi cal
address that the target node currentl y uses to i denti fy i tsel f. The val ue i s the
physi cal address that the target node has set for i tsel f or, i f the target node has
not set a physi cal address, the hardware address associ ated wi th the target nodes
devi ce control l er.
SERVICE PASSWORD password
node. The password i s a hexadeci mal number, 8 to 16 di gi ts l ong. For broadcast
ci rcui ts, i t i s i n the range 0 to FFFFFFFFFFFFFFFF.
VAX
VIA circuit-id
I denti es the ci rcui t over whi ch the operati on i s to take pl ace.
3156
TRIGGER NODE
Examples
1. NCP>TRIGGER NODE NYC
Thi s command tri ggers the bootstrap mechani sm on node NYC to i ni ti ate a
downl i ne l oad operati on.
2. NCP>TRIGGER NODE NYC SERVICE PASSWORD FEFEFEFEFEFEFEFE VIA FZA-1
Thi s command provi des a servi ce password i n order to tri gger the bootstrap
mechani sm on node NYC and to i ni ti ate a downl i ne l oad operati on over FDDI
ci rcui t FZA1.
3. NCP>TRIGGER NODE SWIFT PHYSICAL ADDRESS AA-00-04-00-07-04 -
_ VIA MNA-0
Thi s command tri ggers the bootstrap mechani sm on node SWI FT to i ni ti ate
a downl i ne l oad operati on. The executor node uses the physi cal address
speci ed i n the command to address the node SWI FT on Ethernet ci rcui t
MNA0.
4. NCP>TRIGGER NODE SWIFT VIA MNA-0
Thi s command tri ggers the bootstrap mechani sm on node SWI FT on Ethernet
ci rcui t MNA0 to i ni ti ate a downl i ne l oad operati on. DECnet for OpenVMS
at the executor node attempts to address node SWI FT usi ng a physi cal
address deri ved from the node number. I f node SWI FT does not recogni ze
thi s address, the executor node uses the hardware address for node SWI FT i f
speci ed i n the vol ati l e database at the executor node.
3157
TRIGGER VIA
TRIGGER VIA
The TRI GGER VI A command starts the bootstrap mechani sm of a target node
usi ng the speci ed ci rcui t to al l ow the node to l oad i tsel f. Use thi s command to
i ni ti ate the l oadi ng sequence for an unattended system.
Format
TRIGGER VIA circuit-id parameter [...]
Command Parameters
Appl i es onl y to target nodes on FDDI and Ethernet ci rcui ts. Speci es the physi cal
address that the target node currentl y uses to i denti fy i tsel f. The val ue i s the
physi cal address that the target node has set for i tsel f or, i f the target node has
not set a physi cal address, the hardware address associ ated wi th the target nodes
devi ce control l er. Thi s parameter must be i ncl uded i f an FDDI or Ethernet ci rcui t
i s speci ed i n VI A circuit-id.
SERVICE PASSWORD password
node. The password i s a hexadeci mal number. For broadcast ci rcui ts, i t i s i n the
range 0 to FFFFFFFFFFFFFFFF. The word SERVI CE i s opti onal .
VAX
Comments
Thi s command tri ggers the target node through the speci ed ci rcui t. The target
node i denti cati on i s obtai ned from the vol ati l e database on the executor node.
Examples
VAX
1.
NCP>TRIGGER VIA DMC-0
Thi s command tri ggers the bootstrap mechani sm on the node connected to
ci rcui t DMC0.
2. NCP>TRIGGER VIA MNA-0 PHYSICAL ADDRESS AA-00-04-00-07-04
Thi s command tri ggers the bootstrap mechani sm at the target node whose
physi cal address on ci rcui t MNA0 i s speci ed i n the command.
3158
ZERO CIRCUITS
ZERO CIRCUITS
The ZERO CI RCUI TS command resets ci rcui t counters. Note that the word
COUNTERS i s opti onal .
Format
ZERO circuit-component [COUNTERS]
Circuit Components
Circuit Components
CIRCUIT circuit-id
I denti es a parti cul ar ci rcui t for whi ch counters are to be reset.
KNOWN CIRCUITS
I ndi cates that counters for al l known ci rcui ts are to be reset.
Examples
1. NCP>ZERO KNOWN CIRCUITS COUNTERS
Thi s command resets al l ci rcui t counters for al l known ci rcui ts.
3159
ZERO EXECUTOR
ZERO EXECUTOR
The ZERO EXECUTOR command resets al l counters. Note that the word
Format
ZERO EXECUTOR [COUNTERS]
Examples
1. NCP>ZERO EXECUTOR COUNTERS
Thi s command resets al l counters for the l ocal node.
3160
ZERO LINE
ZERO LINE
The ZERO LI NE command resets l i ne counters. Note that the word COUNTERS
i s opti onal .
Format
ZERO line-component [COUNTERS]
Line Components
LINE KNOWN LINES
Line Components
LINE line-id
I denti es a parti cul ar l i ne for whi ch counters are to be reset.
KNOWN LINES
I ndi cates that counters for al l known l i nes are to be reset.
Examples
1. NCP>ZERO KNOWN LINES COUNTERS
Thi s command resets al l l i ne counters for al l known l i nes.
2. NCP>ZERO LINE FZA-0
Thi s command resets l i ne counters for the FDDI l i ne FZA0.
3161
ZERO MODULE X25-PROTOCOL (Remote management only)
ZERO MODULE X25-PROTOCOL (Remote management only)
The ZERO MODULE X25-PROTOCOL command zeroes the counters for a
parti cul ar DTE or for al l known DTEs. Note that the word COUNTERS i s
opti onal .
Note
Format
ZERO MODULE X25-PROTOCOL parameter [qualier] [COUNTERS]
Command Parameters
DTE KNOWN DTES
Qualiers
Command Parameters
DTE dte-address
Zeroes the counters for the speci ed DTE onl y.
KNOWN DTES
Zeroes the counters for al l known DTEs.
You must associ ate the DTE parameter wi th ei ther of the fol l owi ng qual i ers:
network.
Examples
1. NCP>ZERO MODULE X25-PROTOCOL KNOWN DTES COUNTERS
Thi s command zeroes al l DTE counters for al l known DTEs on the defaul t
network.
2. NCP>ZERO MODULE X25-PROTOCOL KNOWN DTES NETWORK TELENET COUNTERS
Thi s command zeroes counters for al l DTEs on the network Tel enet.
3162
ZERO MODULE X25-SERVER (Remote management only)/X29-SERVER
ZERO MODULE X25-SERVER (Remote management only)/X29-SERVER
The ZERO MODULE X25-SERVER and ZERO MODULE X29-SERVER
commands zero the counters for the X.25 and X.29 cal l handl ers. Note that
the word COUNTERS i s opti onal .
Note
Format
ZERO MODULE X25-SERVER [COUNTERS]
ZERO MODULE X29-SERVER [COUNTERS]
Examples
1. NCP>ZERO MODULE X25-SERVER COUNTERS
Thi s command zeroes al l modul e counters associ ated wi th the X.25 cal l
handl er.
3163
ZERO NODE
ZERO NODE
The ZERO NODE command resets node counters. Note that the word
Format
ZERO node-component [COUNTERS]
Node Components
NODE KNOWN NODES
Node Components
NODE node-id
I denti es a parti cul ar node for whi ch counters are to be reset.
KNOWN NODES
I ndi cates that counters for al l known nodes are to be reset.
Examples
1. NCP>ZERO NODE TRNTO COUNTERS
Thi s command resets al l node counters mai ntai ned on the l ocal node for
remote node TRNTO.
3164
Part II
DECnet for OpenVMS DTS/DTR Utility
4
DECnet Test Sender/DECnet Test Receiver
(DTS/DTR) Commands
DTS and DTR are cooperati ng tasks that perform vari ous functi ons to exerci se
the DECnet software and test communi cati on l i nes. DTS i ni ti ates each test by
i ssui ng a connecti on request to DTR. DTS passes parameters perti nent to the
type of test request to DTR. The user i nterface to DTS consi sts of a group of
commands. These commands enabl e you to sel ect the type of test and subtest
and to speci fy opti ons rel ati ve to the operati on of the test. These opti ons i ncl ude
parameters to regul ate the durati on of the test, the type of i nformati on to be used
for the test, and buffer-l evel control .
Note
The OpenVMS DECnet Test Recei ver i mage (DTRECV) cannot perform
mul ti pl e bufferi ng. I n addi ti on, i t does not support any negati ve
acknowl edgment (NAK) or BACK opti ons nor ow control other than
segment. The OpenVMS DECnet Test Sender i mage (DTSEND) does not
support mul ti pl e bufferi ng ei ther.
4.1 DTS Command Syntax
Thi s secti on descri bes the DTS command syntax for al l tests. Each command
consi sts of a command keyword, opti onal general command qual i ers, each
preceded by a sl ash (/) character, and opti onal command-speci c qual i ers, each
preceded by a sl ash character. You may abbrevi ate DTS commands and qual i ers,
as l ong as the command i s unambi gi ous.
Note that, when usi ng DTS commands i n a batch job, you must use uppercase
characters i n the command.
The general DTS command syntax and the deni ti on of each command component
i s as fol l ows.
command-keyword/general-qualifier,.../command-specific-qualifier,...
command-keyword Speci es the general test to be performed.
CONNECT I ndi cates a connect test
DI SCONNECT I ndi cates a di sconnect test
DATA I ndi cates a data test
I NTERRUPT I ndi cates an i nterrupt test
41
DECnet Test Sender/DECnet Test Receiver (DTS/DTR) Commands
4.1 DTS Command Syntax
general -qual i er Speci es one or more general test
characteri sti cs regardl ess of the test to be
performed. These qual i ers and thei r defaul t
val ues are descri bed i n each command
(CONNECT, DATA, DI SCONNECT, and
I NTERRUPT) where they appl y.
command-speci c-qual i er Speci es one or more test-speci c qual i ers that
regul ate the operati on of the test.
The general command syntax adheres to the DCL rul es for comments and
conti nuati on l i nes, as shown i n the fol l owi ng exampl e:
$ RUN SYS$SYSTEM:DTSEND
_TEST: DATA/PRINT/TYPE=SEQ !Perform Data Test
.
.
.
_TEST: INTERRUPT/NODENAME=DALLAS -
_/PRINT/TYPE=PAT !Perform Interrupt Test
.
.
.
_TEST: EXIT
$
4.2 DTS/DTR Usage Summary
DECnet Test Sender (DTS) and DECnet Test Recei ver (DTR) are the DECnet
transmi tter and recei ver test programs that exerci se network task-to-
task capabi l i ti es. DTSEND and DTRECV are the DECnet for OpenVMS
i mpl ementati ons of these programs. The i mages and command l es to use
DTSEND and DTRECV are i ncl uded wi th the DECnet for OpenVMS software.
There are four basi c network tests provi ded by DTS and DTR:
Connecti on tests
Data tests
Di sconnecti on tests
I nterrupt tests
Each test i s composed of a set of subtests. See the fol l owi ng secti ons for a
descri pti on of each test and i ts subtests.
Format
The fol l owi ng shows of the DCL command that i nvokes DTSEND:
RUN SYS$SYSTEM:DTSEND
Command Parameters
Thi s command has no command parameters.
Before i nvoki ng DTS, be sure that the necessary l i ne (i f any) i s i n the ON state.
To i nvoke DTS, type RUN SYS$SYSTEM:DTSEND i n response to the DCL
prompt.
DTS returns wi th the fol l owi ng i nformati on and prompt:
DTS Version xxx initiated on dd-mmm-yy hh:mm:ss
_Test:
42
DECnet Test Sender/DECnet Test Receiver (DTS/DTR) Commands
4.2 DTS/DTR Usage Summary
DTS accepts i nput entered i nteracti vel y at the termi nal . DTS al so accepts a
command procedure as i nput.
To exi t DTS and thereby termi nate the test, enter EXI T at the _Test: prompt. For
exampl e:
_Test: EXIT
DTS terminated on dd-mmm-yy hh:mm:ss
$
Use the /PRI NT qual i er to pri nt test resul ts. Al so, you can use the /STATI STI CS
and /DI SPLAY qual i ers to pri nt stati sti cs and messages transmi tted to DTR,
respecti vel y. The /STATI STI CS and /DI SPLAY qual i ers appl y onl y to the data
and i nterrupt tests. See the i ndi vi dual commands for more i nformati on.
4.3 DTS Commands
Thi s secti on expl ai ns how to use the four DTS tests. Exampl es are provi ded for
each test.
DTS Commands
CONNECT
DATA
DI SCONNECT
VAX
HELP
I NTERRUPT
43
CONNECT
CONNECT
I nvokes a connecti on test.
Format
CONNECT [/general-qualier[,...] /command-specic-qualier[,...]]
General Qualiers
/NODENAME=node-id
I denti es the node (by name or address) on whi ch DTR i s to run. The defaul t i s
the l ocal node. Because you cannot use access control i nformati on as part of the
node name, DTR runs on the defaul t nonpri vi l eged account on the remote node.
To run DTR on an account other than the defaul t, you associ ate the account wi th
the DTR object.
/PRINT
I nstructs DTS to pri nt (or l og) test resul ts.
/NOPRINT
Di sabl es pri nti ng of test resul ts. The defaul t i s /NOPRI NT.
/SPEED=number
I ndi cates the l i ne speed (bi ts per second) of the test l i ne. DTS uses thi s qual i er
for reporti ng stati sti cs (DTS does not control l i ne speeds). The defaul t i s
/SPEED=1000000.
Command- Specic Qualiers
/TYPE=test-type
I ndi cates the subtest for the connecti on test. There are two subtests:
ACCEPT I ndi cates a connect accept test. The defaul t i s /TYPE=ACCEPT.
REJECT I ndi cates a connect reject test.
/RETURN=return-option
I ndi cates the type of opti onal user data DTR returns. There are two possi bi l i ti es:
STANDARD I ndi cates standard user data.
RECEI VED I ndi cates recei ved user data.
/NORETURN
Di sabl es return of user data. The defaul t i s /NORETURN.
Description
Connecti on tests eval uate the abi l i ty of the DECnet software to process connect,
connect accept, and connect reject requests wi th and wi thout opti onal user data.
Connecti on tests that you may perform i ncl ude the fol l owi ng:
Connect reject wi thout user data
Connect accept wi thout user data
Connect reject wi th 16 bytes of standard user data
Connect accept wi th 16 bytes of standard user data
44
CONNECT
Connect reject wi th recei ved user data used as reject user data
Connect accept wi th recei ved user data used as accept user data
Examples
1. _Test: CONNECT/TYPE=ACCEPT/RETURN=RECEIVED
Thi s command i nvokes the connecti on test wi th the connect accept subtest.
DTS attempts to connect to DTR on the l ocal node (by defaul t). Connect user
data i s to be returned as part of the test.
2. _Test: CONNECT/NODENAME=TRNTO
Thi s command i nvokes the connecti on test wi th the connect accept subtest.
DTS attempts to connect to DTR on remote node TRNTO. DTR returns no
opti onal user data.
45
DATA
DATA
I nvokes a data test.
Format
DATA [/general-qualier[,...] /command-specic-qualier[,...]]
General Qualiers
/NODENAME=node-id
To run DTR on an account other than the defaul t, you must associ ate the account
wi th the DTR object.
/PRINT
/NOPRINT
/STATISTICS
I nstructs DTS to pri nt stati sti cs on data and i nterrupt tests. The defaul t i s
/STATI STI CS.
/NOSTATISTICS
Di sabl es the output of stati sti cs.
/DISPLAY=number
I nstructs DTS to pri nt the speci ed number of bytes (i n hexadeci mal ) of data and
i nterrupt messages transmi tted to DTR.
/NODISPLAY
Di sabl es the di spl ay of data and i nterrupt messages that are transmi tted to DTR.
The defaul t i s /NODI SPLAY.
/SPEED=number
for reporti ng stati sti cs. (DTS does not control l i ne speeds.) The defaul t i s
/SPEED=1000000.
/TYPE=test-type
I ndi cates the subtest for the data test. There are four subtests:
SI NK I ndi cates a si nk test. The defaul t i s /TYPE=SI NK.
SEQ I ndi cates a sequence test.
PAT I ndi cates a pattern test.
ECHO I ndi cates an echo test.
46
DATA
/SIZE=number
I ndi cates the data message l ength i n bytes. The l ower bounds are 0 for a si nk or
echo test; 4 for a sequence test; and 5 for a pattern test. The upper bound i s 4096
bytes for al l tests. The defaul t i s /SI ZE=128.
/[test-duration]
I ndi cates the durati on of the test. There are three uni ts of ti me for thi s
parameter:
/SECONDS=number
/MI NUTES=number
/HOURS=number
The number speci es the durati on of the test. The defaul t uni t i s /SECONDS=30.
The maxi mum test durati on i s 3,600,000 seconds or 1000 hours.
Description
Data tests provi de a ful l spectrum of test capabi l i ti es, rangi ng from data si nk
operati ons to data i ntegri ty checki ng. Data tests that you may perform i ncl ude
the fol l owi ng:
Si nk Test. DTR i gnores al l data recei ved duri ng thi s test. DTR performs
nei ther sequence nor content val i dati on.
Sequence Test. Data messages transmi tted by DTS to DTR i ncl ude a
4-byte sequence number. Duri ng the sequence test, i f a message i s recei ved
out of sequence, DTR aborts the l ogi cal l i nk and the test.
Pattern Test. Data messages transmi tted to DTR have both a sequence
number and a standard data pattern. Duri ng the pattern test, i f ei ther the
sequence number or the recei ved data does not match the expected data, DTR
aborts the l ogi cal l i nk and the test.
Echo Test. DTR transmi ts al l data messages recei ved back to DTS duri ng
thi s test. DTS performs data val i di ty tests.
Example
_Test: DATA/PRINT/TYPE=SEQ/SIZE=128/SECONDS=10
_DTS-S-NORMAL, normal successful completion
Test parameters:
Test duration (sec) 10
Target nodename ""
Line speed (baud) 1000000
Message size (bytes) 128
Summary statistics:
Total messages XMIT 788 RECV 0
Total bytes XMIT 100864
Messages per second 78.8
Bytes per second 10086
Line throughput (baud) 80691
_ Line utilization 8.0
Thi s command i nvokes the data test wi th the sequence subtest. DTS sends
messages to DTR on the l ocal node where test i nformati on i s to be pri nted. The
message si ze i s 128 bytes, and the durati on of the test i s 10 seconds.
47
DISCONNECT
DISCONNECT
I nvokes a di sconnecti on test.
Format
DISCONNECT [/general-qualier[,...] /command-specic-qualier[,...]]
General Qualiers
/NODENAME=node-id
/PRINT
/NOPRINT
/TYPE=test-type
I ndi cates the subtest for the di sconnecti on test. There are two subtests:
SYNCHRONOUS I ndi cates a synchronous di sconnect test.
ABORT I ndi cates a di sconnect abort test. The defaul t i s
/TYPE=ABORT.
/RETURN=return-option
I ndi cates the type of opti onal user data DTR returns. There are two possi bi l i ti es:
STANDARD I ndi cates standard user data.
RECEI VED I ndi cates recei ved user data.
/NORETURN
Di sabl es return of user data. The defaul t i s /NORETURN.
48
DISCONNECT
Description
Di sconnecti on tests eval uate whether DTS detects the di fference between
di sconnecti on and abort sequences generated by DTR as wel l as the abi l i ty of
DTS to recei ve the proper opti onal user data. Di sconnecti on tests that you can
perform i ncl ude the fol l owi ng:
Di sconnect wi thout user data
Abort wi thout user data
Di sconnect wi th 16 bytes of standard user data
Abort wi th 16 bytes of standard user data
Di sconnect wi th recei ved connect user data used as di sconnect user data
Abort wi th recei ved connect user data used as abort user data
Example
_Test: DISCONNECT/NODENAME=DENVER/TYPE=ABORT
Thi s command i nvokes the di sconnecti on test wi th the di sconnect abort subtest.
DTS performs thi s test wi th DTR on remote node DENVER. No opti onal user
data i s to be returned.
49
HELP
HELP
The HELP command di spl ays general i nformati on about DTS commands and
parameters.
Format
HELP [topic]
Command Parameter
topic
Speci es DTS and DTR keyword that refers to a topi c or subtopi c on whi ch you
can obtai n i nformati on.
Example
_Test: HELP
CONNECT DATA DISCONNECT DTS INTERRUPT
Topic? dts
DTS
DTS and DTR are cooperationg tasks that perform various functions to
exercise network software. DTR functions as a slave to DTS. DTS
initiates each test by issuing a connection request to DTR. DTS
passes parameters pertinent to the type of test request to DTR in
the optional data of the connection request. The user interface to
DTS consists of a group of commands:
CONNECT
DATA
DISCONNECT
INTERRUPT
You may abbreviate command keywords and qualifiers to four characters
or less (if unique).
Note that, when using DTS commands in a batch job, you must use uppercase
characters in the command.
Topic?
Thi s command i nvokes HELP and di spl ays i nformati on about DTS.
410
INTERRUPT
INTERRUPT
I nvokes an i nterrupt test.
Format
INTERRUPT [/general-qualier[,...] /command-specic-qualier[,...]]
General Qualiers
/NODENAME=node-id
/PRINT
/NOPRINT
/STATISTICS
I nstructs DTS to pri nt stati sti cs on data and i nterrupt tests. The defaul t i s
/STATI STI CS.
/NOSTATISTICS
Di sabl es the output of stati sti cs.
/DISPLAY=number
I nstructs DTS to pri nt data and i nterrupt messages transmi tted to DTR.
/NODISPLAY
Di sabl es the di spl ay of data and i nterrupt messages that are transmi tted to DTR.
The defaul t i s /NODI SPLAY.
/SPEED=number
for reporti ng stati sti cs. (DTS does not control l i ne speeds.) The defaul t i s
/SPEED=1000000.
/TYPE=test-type
I ndi cates the subtest for the i nterrupt test. There are four subtests:
SI NK I ndi cates a si nk test. The defaul t i s /TYPE=SI NK.
SEQ I ndi cates a sequence test.
PAT I ndi cates a pattern test.
ECHO I ndi cates an echo test.
411
INTERRUPT
/SIZE=number
I ndi cates the data message l ength i n bytes. The l ower bounds are 0 for a si nk or
echo test; 4 for a sequence test; and 5 for a pattern test. The upper bound i s 16
bytes for al l tests. The defaul t i s /SI ZE=16.
/[test-duration]
I ndi cates the durati on of the test. There are three uni ts of ti me for thi s
parameter:
/SECONDS=number
/MI NUTES=number
/HOURS=number
The number speci es the durati on of the test. The defaul t uni t i s /SECONDS=30.
The maxi mum test durati on i s 3,600,000 seconds or 1000 hours.
Description
As wi th data tests, i nterrupt tests provi de a ful l range of test capabi l i ti es from
data si nk operati ons to data i ntegri ty checki ng. I nterrupt tests that you can
perform i ncl ude the fol l owi ng:
Si nk Test. DTR i gnores al l i nterrupt data recei ved duri ng thi s test. DTR
performs nei ther sequence nor content val i dati on.
Sequence Test. I nterrupt messages transmi tted by DTS to DTR i ncl ude a
4-byte sequence number. Duri ng the sequence test, i f a message i s recei ved
out of sequence, DTR aborts the l ogi cal l i nk and the test.
Pattern Test. I nterrupt messages transmi tted to DTR have both a sequence
number and a standard data pattern. Duri ng the pattern test, i f ei ther the
sequence number or the recei ved data does not match the expected data, DTR
aborts the l ogi cal l i nk and the test.
Echo Test. DTR transmi ts al l i nterrupt messages recei ved back to DTS
duri ng thi s test. DTS performs data val i di ty tests.
Example
_Test: INTERRUPT/NODENAME=DALLAS/PRINT/TYPE=PAT/SIZE=16
_DTS-S-NORMAL, normal successful completion
Test parameters:
Test duration (sec) 30
Target nodename "DALLAS"
Line speed (baud) 1000000
Message size (bytes) 16
Summary statistics:
Total messages XMIT 2734 RECV 0
Total bytes XMIT 43744
Messages per second 91.1
Bytes per second 1458
Line throughput (baud) 11665
__ Line utilization 1.1
Thi s command i nvokes the i nterrupt test wi th the pattern subtest. DTS sends
i nterrupt messages to DTR on node DALLAS where test i nformati on i s to be
pri nted. The i nterrupt message si ze i s 16 bytes, and the durati on of the test i s 30
seconds (by defaul t).
412
A
DECnet Circuit and Line Devices
Thi s appendi x l i sts DECnet for OpenVMS ci rcui t and l i ne devi ces. NCP al l ows
for management of the l ocal node and for remote management of any DECnet
node that you speci fy as the executor. The di spl ay that you see and the devi ces
that you manage depend on the supported features of the parti cul ar DECnet
system that you are managi ng.
Note that some of the devi ces shown may not be supported on the your system.
Check the Software Product Descri pti on for the l atest devi ce i nformati on.
Tabl e A1 shows the devi ces for Ethernet ci rcui ts and l i nes. Devi ces on thi s tabl e
conform to the Ethernet and/or I EEE 802.3 protocol .
Table A1 Ethernet Circuit and Line Devices
Mnemonic Driver Description
BNA ET DEBNA, DEBNI communi cati ons l i nk
I SA EZ SGEC communi cati ons l i nk
KFE EF VAXft 3000 communi cati ons l i nk
MNA EX DEMNA communi cati ons l i nk
MXE EC PMAD communi cati ons l i nk
QNA XQ DEQNA, DELQA, DESQA, DEQTA communi cati ons l i nk
SVA ES DESVA communi cati ons l i nk
UNA XE DEUNA, DELUA communi cati ons l i nk
VAX
Tabl e A2 shows the devi ces for DDCMP and CI ci rcui ts and l i nes. DDCMP
devi ces i n thi s tabl e conform to the DDCMP protocol . CI devi ces communi cate
usi ng protocol s dened by the System Communi cati ons Archi tecture (SCA).
Table A2 DDCMP and CI Circuit and Line Devices
DI V SD DI V32, I SDN control l er
DMB SI DMB32 synchronous l i ne uni t
DMC XM DMC11, DMR11 synchronous l i ne uni ts
DMF XG DMF32 synchronous l i ne uni t
DMP XD DMP11, DMV11 synchronous poi nt-to-poi nt or mul ti poi nt l i ne
devi ce
DSB SL DSB32 synchronous l i ne uni t
A1
DECnet Circuit and Line Devices
Table A2 (Cont.) DDCMP and CI Circuit and Line Devices
DSF SF VAXft 3000 synchronous communi cati ons control l er
DST ZS DST32, DSH32 synchronous devi ce
DSV SJ DSV11 synchronous l i ne i nterface
DSW ZT DSW-21, DSW-41, DSW-42 synchronous communi cati on devi ce
TT NO DZ11, DZ32, DZQ11, DZV11 asynchronous devi ce
TX NO DMB32, DHB32, DHU11, DHV11, DHT32, DMF32 or DMZ32,
DHQ11, DSH32,CXY08 asynchronous devi ce
CI CN CI 780, CI 750, CI BCA, or CI BCI computer i nterconnect
Tabl e A3 shows the devi ces for X.25 ci rcui ts and l i nes. Devi ces on thi s tabl e
conform to the LAPB protocol .
Note
Al though some systems do not support VAX P.S.I ., you can manage
remote VAX P.S.I . systems from the l ocal node.
Table A3 X.25 Circuit and Line Devices
DMB SI DMB32 synchronous l i ne uni t
DMF XG DMF32 synchronous l i ne uni t
DPV UE DPV11DA synchronous l i ne i nterface
DSB SL DSB32 synchronous l i ne uni t
DSV SJ DSV11 synchronous l i ne i nterface
DSW ZT DSW-21, DSW-41, DSW-42 synchronous communi cati on devi ces
DUP XW DUP11DA synchronous l i ne i nterface
KMV UV KMV1A synchronous l i ne i nterface combi ned wi th X.25 l evel 2
mi crocode
KMX XS KMS11BD or BE synchronous l i ne i nterface combi ned wi th
X.25 l evel 2 mi crocode
KMY XN KMS1P synchronous l i ne i nterface combi ned wi th X.25 l evel 2
mi crocode
Tabl e A4 shows the devi ces for FDDI ci rcui ts and l i nes. Devi ces on thi s tabl e
conform to the FDDI protocol .
Table A4 FDDI Circuit and Line Devices
FZA FC DEFZA FDDI communi cati ons l i nk
MFA FX DEMFA FDDI communi cati ons l i nk
A2
B
Network Counter Summary
B.1 Overview
Thi s appendi x i ncl udes descri pti ons of ci rcui t, l i ne and node counters. Where
possi bl e, the descri pti on of each counter i ncl udes the probabl e causes for the
parti cul ar type of occurrence that causes the counter to be i ncremented. I n
some cases, the counters correspond to network events. The events and event
descri pti ons provi de addi ti onal i nformati on rel ati ve to the speci c occurrence.
The i ndi vi dual counter descri pti ons state whi ch counters correspond to events.
NCP al l ows for management of the l ocal node and for remote management of
any DECnet node that you speci fy as the executor. The di spl ays, counters, and
messages that you recei ve by i ssui ng NCP commands ori gi nate at the executor
node. Thi s appendi x shows al l the i nformati on that DECnet for OpenVMS can
di spl ay. The actual di spl ay you recei ve depends on the supported features of the
parti cul ar DECnet system that you are managi ng.
To see what management features are supported on DECnet for OpenVMS, see
Chapter 3.
NCP reports the contents of al l counters i n deci mal notati on. Counter content
di spl ays wi th an angl e bracket (>) i ndi cate that the counter has overowed. I n
some cases where the counter has more than one error associ ated wi th i t, the
standard counter i s expanded to i ncl ude a reason.
B1
B.1 Overview
The fol l owi ng exampl e i l l ustrates the di spl ay of ci rcui t counters:
NCP>SHOW KNOWN CIRCUITS COUNTERS
Known Circuit Counters as of 12-JUN-1992 06:45:10
Circuit = FZA-0
0 Circuit down
0 Adjacency down
1 Peak adjacencies
Circuit = SVA-0
0 Circuit down
0 Adjacency down
0 Peak adjacencies
0 Data blocks sent
0 Bytes sent
0 Bytes received
B2
B.1 Overview
Thi s exampl e i l l ustrates the di spl ay of l i ne counters:
NCP>SHOW KNOWN LINE COUNTERS
Known Line Counters as of 12-JUN-1992 06:42:51
Line = FZA-0
0 Receive failure
0 Data overrun
0 Send failure
>4294967294 MAC frame count
0 MAC error count
0 MAC lost count
1 Ring initializations initiated
2 Ring initializations received
1 Ring beacons initiated
0 Duplicate address test failures
0 Duplicate tokens detected
0 Ring purge errors
0 FCI strip errors
0 Traces initiated
0 Traces received
0 Directed beacons received
0 Elasticity buffer errors
0 LCT rejects
0 LEM rejects
0 Link errors
2 Connections completed
Line = SVA-0
0 Receive failure
0 Data overrun
436 Blocks sent, multiple collisions
329 Blocks sent, single collision
2201 Blocks sent, initially deferred
4990338 Bytes sent
0 Send failure
0 Collision detect check failure
B3
B.2 Circuit Counters
Thi s secti on contai ns a descri pti on of each ci rcui t counter.
Adjacency down
Thi s counter i ndi cates a l oss of connecti on to an adjacent node that may resul t
from any of the fol l owi ng:
Node l i stener ti meout
I nval i d data recei ved at a node l i stener
Unexpected control (i ni ti al i zati on or veri cati on) message recei ved
Adjacency i dl ed
Routi ng message recei ved wi th a checksum error
Node i denti cati on from a routi ng message or a Hel l o message that i s not the
one expected
Hel l o message recei ved i ndi cati ng that connecti vi ty became one-way
Bytes received
Thi s counter i ndi cates the number of bytes of data recei ved by the l ocal node over
the ci rcui t. You can use thi s i nformati on together wi th the data bl ocks recei ved
counter to determi ne the i nbound trafc l oad.
Bytes sent
Thi s counter i ndi cates the number of bytes of data sent by the l ocal node over the
ci rcui t. You can use thi s i nformati on together wi th the data bl ocks sent counter
to determi ne the outbound trafc l oad.
Circuit down
Thi s counter i ndi cates the number of fai l uresoperator or software i nduced
for the ci rcui t. These fai l ures may i ncl ude any number of hardware- software-
or operator-caused probl ems. Thi s counter corresponds to events 4.79 (ci rcui t
down).
Data blocks received
Thi s counter i ndi cates the number of data bl ocks recei ved by the l ocal node. You
can use thi s i nformati on as a stati sti cal base when eval uati ng the number of
i nbound data errors, remote repl y ti meouts, and l ocal buffer errors.
Data blocks sent
Thi s counter i ndi cates the number of data bl ocks sent by the l ocal node. You
can use thi s i nformati on as a stati sti cal base when eval uati ng the number of
outbound data errors, l ocal repl y ti meouts, and remote buffer errors.
Data errors inbound
Thi s counter i ndi cates the number of data errors that normal l y resul t from
errors on the i nbound communi cati ons channel to the l ocal node. These errors
are caused usual l y by a noi sy communi cati ons l i ne or a poorl y functi oni ng
modem. Thi s counter may i ncl ude ei ther or both of the fol l owi ng qual i ers i f
they contri bute any of the fol l owi ng errors:
NAKs sent, header bl ock check error
NAKs sent, data el d bl ock check error
B4
Data errors outbound
Thi s counter i ndi cates the number of data errors that normal l y resul t from errors
on the outbound communi cati ons channel from the l ocal node. These errors are
caused usual l y by a noi sy communi cati ons l i ne or a poorl y functi oni ng modem.
Thi s counter represents the sum of al l NAKs recei ved.
Initialization failure
Thi s counter i ndi cates the number of ti mes the ci rcui t fai l ed to i ni ti al i ze wi th
remote Routi ng software. These fai l ures may i ncl ude any number of hardware-
software- or operator-caused probl ems. Thi s counter corresponds to events
4.1113 (i ni ti al i zati on fai l ure).
Local buffer errors
Thi s counter i ndi cates the number of l ocal buffer errors that normal l y resul t from
a l ocal recei ve buffer that i s too smal l . These errors are caused when a remote
node sends a bl ock that i s too bi g for the l ocal nodes recei ve buffer. Thi s counter
may i ncl ude the fol l owi ng qual i er i f i t contri butes to the error:
NAKs sent, buffer unavai l abl e
Thi s counter corresponds to event 5.9 (l ocal buffer too smal l ) and event 4.3
(oversi zed packet l oss).
Local reply timeouts
Thi s counter i ndi cates the number of ti meouts that normal l y resul t from the
fol l owi ng:
The l oss of communi cati on between nodes whi l e the l ocal node has data to
transmi t
An i nappropri ate val ue set for the repl y ti mer on the l ocal node
Locally initiated resets
Thi s counter i ndi cates the number of resets sent over the ci rcui t.
Network initiated resets
Thi s counter i ndi cates the number of resets ori gi nated by the PSDN recei ved over
the ci rcui t.
Originating packets sent
Thi s counter i ndi cates the number of data packets sent by the Routi ng l ayer on
the l ocal node.
Peak adjacencies
Thi s counter i ndi cates the maxi mum number of nodes that have been up on a
ci rcui t.
Remote buffer errors
Thi s counter i ndi cates the number of remote buffer errors that normal l y resul t
from a remote recei ve buffer that i s too smal l .
Remote reply timeouts
Thi s counter i ndi cates the number of ti meouts that normal l y resul t from the
fol l owi ng:
The l oss of communi cati on between nodes whi l e the remote node has data to
transmi t
An i nappropri ate val ue set for the repl y ti mer on the remote node
B5
Remotely initiated resets
Thi s counter i ndi cates the number of resets recei ved over the ci rcui t.
Seconds since last zeroed
Thi s counter i ndi cates the number of seconds that have el apsed si nce the ci rcui t
counters were zeroed. Thi s counter provi des a ti me frame for other counter
val ues. The software i ncrements thi s counter every second and cl ears i t when
other counters are cl eared.
Selection intervals elapsed
Thi s counter i ndi cates the number of sel ecti on i nterval s for hal f-dupl ex and
mul ti poi nt control stati ons. Thi s i s the number of ti mes a stati on sel ects another
stati on. You can use thi s i nformati on as a stati sti cal base when eval uati ng
sel ecti on ti meout errors.
Selection timeouts
Thi s counter i ndi cates the number of sel ecti on ti meouts that normal l y resul t from
the fol l owi ng:
Loss of communi cati on wi th a remote stati on.
Data errors on the communi cati ons channel to or from that stati on.
An i nappropri ate val ue for the stati ons sel ect ti mer. Thi s counter corresponds
to event 5.5 (sel ect error threshol d) and may i ncl ude ei ther the No reply to
select or the I ncomplete reply to select qual i ers i f they contri bute to the
errors.
Terminating congestion loss
Thi s counter i ndi cates the number of packets i ntended for the node that were
di scarded because Routi ng coul d not buffer them.
Terminating packets received
Thi s counter i ndi cates the number of data packets recei ved by the Routi ng l ayer
on the l ocal node.
Transit congestion loss
Thi s counter i ndi cates the number of transi t data packets di scarded for congesti on
reasons. Thi s counter i s mai ntai ned onl y on ful l -routi ng nodes. I f congesti on l oss
i ncreases, i ncrease the MAXI MUM BUFFERS parameter for the l ocal node.
Transit packets received
Thi s counter i ndi cates the number of data packets recei ved over the ci rcui t and
to be routed through the l ocal node to another node. I t i s mai ntai ned onl y on
ful l -routi ng nodes.
Transit packets sent
Thi s counter i ndi cates the number of data packets sent over the ci rcui t and
bei ng routed through the l ocal node to another node. I t i s mai ntai ned onl y on
ful l -routi ng nodes.
Unrecognized frame destination
Thi s counter i ndi cates the number of ti mes a frame was di scarded because the
frame was addressed to a mul ti cast address not enabl ed on the ci rcui t.
User buffer unavailable
Thi s counter i ndi cates the total number of ti mes that no user buffer was avai l abl e
for an i ncomi ng frame that passed al l l teri ng. User buffers are suppl i ed by users
on recei ve requests.
B6
B.3 Line Counters
B.3 Line Counters
Thi s secti on contai ns a descri pti on of each l i ne counter. The counters i n thi s
secti on may be di spl ayed for devi ces other than the DMC11 on remote nodes
other than DECnet for OpenVMS.
Blocks sent, initially deferred
Thi s counter i ndi cates the total number of ti mes a frame transmi ssi on was
deferred on i ts rst transmi ssi on attempt. Used i n measuri ng Ethernet
contenti on wi th no col l i si ons.
Blocks sent, multiple collisions
Thi s counter i ndi cates the total number of ti mes a frame was successful l y
transmi tted on the thi rd or l ater attempt after normal col l i si ons on previ ous
attempts.
Blocks sent, single collision
Thi s counter i ndi cates the total number of ti mes a frame was successful l y
transmi tted on the second attempt after a normal col l i si on on the rst attempt.
Bytes received
Thi s counter i ndi cates the number of bytes of data recei ved over the l i ne.
Bytes sent
Thi s counter i ndi cates the number of bytes of data sent over the l i ne.
Collision detect check failure
Thi s counter i ndi cates the approxi mate number of ti mes a col l i si on detect was not
sensed after a transmi ssi on. Thi s counter i s al so reported each ti me a packet i s
transmi tted usi ng ei ther a DEUNA or DELUA on a broadband Ethernet.
Connections completed
An FDDI counter that i ndi cates the number of ti mes the PHY Port entered the I n
Use state, after havi ng compl eted the i ni ti al i zati on process.
Thi s counter i ndi cates the number of data bl ocks recei ved over the l i ne.
Data blocks sent
Thi s counter i ndi cates the number of data bl ocks sent over the l i ne.
Data errors inbound
Thi s counter i ndi cates the number of i ncomi ng data errors that resul t from faul ts
on the channel between the l ocal DTE and DCE. The counter can i ncl ude any of
the fol l owi ng qual i ers:
Bl ock too l ong
Bl ock check error
Reject sent
Data errors outbound
Thi s counter i ndi cates the number of outgoi ng data errors that resul t from faul ts
on the channel between the l ocal DTE and DCE. The counter can i ncl ude the
fol l owi ng qual i er:
Reject recei ved
Data overrun
Thi s counter i ndi cates the total number of ti mes the hardware l ost an i ncomi ng
frame because i t was unabl e to keep up wi th the data rate.
B7
B.3 Line Counters
Directed beacons received
An FDDI counter that i ndi cates the number of ti mes the l i nk recei ved a uni que
di rected beacon.
Duplicate address test failures
An FDDI counter that i ndi cates the number of ti mes the dupl i cate address test
detected that the l i nk address was a dupl i cate.
Duplicate tokens detected
An FDDI counter that i ndi cates the number of ti mes the medi a access control
(MAC) detected a dupl i cate token ei ther by means of the dupl i cate token-detecti on
al gori thm or by the recei pt of a token whi l e al ready hol di ng one.
Elasticity buffer errors
An FDDI counter that i ndi cates the number of ti mes the El asti ci ty Buffer
functi on i n the PHY Port had an overow or underow. Thi s i ndi cates a transmi t
cl ock error somewhere on the ri ng.
FCI strip errors
An FDDI counter that i ndi cates the number of ti mes the recei pt of a token
termi nated a Frame Content I ndependent Stri p.
Local buffer errors
Thi s counter i ndi cates the number of recei ve-not-ready (RNR) frames sent. The
counter can i ncl ude the fol l owi ng qual i er:
RNR sent, buffer unavai l abl e
Local process errors
Thi s counter i ndi cates errors for both VAX P.S.I . and DDCMP l i nes. For VAX
P.S.I . operati ons, thi s counter i ndi cates that a frame reject (FRMR) has been
recei ved over the l i ne or that your system i s bei ng overl oaded. The counter can
i ncl ude any of the fol l owi ng qual i ers:
Transmi t underrun
Recei ve overrun
FRMR recei ved, header format error
The rst two qual i ers usual l y i ndi cate that the system i s overl oaded and the
thi rd usual l y i ndi cates that the VAX P.S.I . software may be i ncorrectl y congured.
For DDCMP operati ons, thi s counter i ndi cates the number of l ocal DDCMP
processi ng errors. DECnet for OpenVMS mai ntai ns thi s counter onl y for DMP
and DMF l i nes. For a mul ti poi nt ci rcui t, thi s counter reects the total errors for
the control stati on, and not for each tri butary. These errors may be caused by a
programmi ng error at the l ocal node, or by a ci rcui t error that was not detected by
the Data Li nk protocol . Thi s counter may i ncl ude any of the fol l owi ng qual i ers
i f they contri bute to the errors:
NAKs sent, recei ve overrun
Recei ve overrun, NAK not sent
Transmi t overruns
NAKs recei ved, header format error
For DDCMP l i nes, thi s counter corresponds to events 5.34 and 5.6.
Local reply timeouts
Thi s counter i ndi cates the number of ti mes a frame wi th a pol l bi t set has been
recei ved over the l i ne, that i s, the number of errors that resul t from faul ts on the
l i ne.
B8
B.3 Line Counters
LCT rejects
An FDDI counter that i ndi cates the number of ti mes a connecti on on thi s PHY
Port was rejected because the Li nk Condence Test (LCT) at ei ther end of the
physi cal connecti on fai l ed. The LCT rejects counter onl y counts rejecti ons that
cause the l i nk to enter i nto the Watch State. The counter, therefore, i ndi cates the
number of distinct l i nk qual i ty probl ems rather than the total l ength of ti me such
probl ems persi sted.
LEM rejects
An FDDI counter that i ndi cates the number of ti mes an acti ve connecti on on thi s
PHY Port was di sconnected because the Li nk Error Moni tor at thi s end of the
physi cal connecti on rejected the connecti on, or because the Noi se ti mer (TNE)
expi red.
Link errors
An FDDI counter that i ndi cates the total number of raw Li nk Error i nput events
detected by the Li nk Error Moni tor.
MAC error count
An FDDI counter that i ndi cates the total number of ti mes the MAC Layer
changed the error i ndi cator i n a frame from reset to set. Thi s tel l s you the
number of ti mes the l ocal FDDI adapter detected an error i n a frame.
MAC frame count
An FDDI counter that i ndi cates the total number of frames on the FDDI medi a,
other than tokens.
MAC lost count
An FDDI counter that i ndi cates the total number of ti mes a frame (other than a
token) was i mproperl y termi nated.
Multicast blocks received
Thi s counter i ndi cates the total number of mul ti cast bl ocks successful l y recei ved.
Multicast bytes received
Thi s counter i ndi cates the total number of mul ti cast data bytes successful l y
recei ved (i ncl udes bytes i n Ethernet data el d but not the Ethernet data l i nk
headers).
Multicast blocks sent
Thi s counter i ndi cates the total number of mul ti cast bl ocks successful l y sent.
Multicast bytes sent
Thi s counter i ndi cates the total number of mul ti cast data bytes successful l y sent
(i ncl udi ng bytes i n the Ethernet data el d, but not i n the Ethernet data l i nk
headers).
Receive failure
Thi s counter i ndi cates the total number of bl ocks recei ved wi th some data error
(the bl ocks are data frames) that passed ei ther physi cal or mul ti cast address
compari son. For each i ncrement of the counter, a type of fai l ure i s recorded, as
fol l ows:
Bl ock check error
Frami ng error
Frame too l ong
B9
B.3 Line Counters
Remote buffer errors
Thi s counter i ndi cates the number of recei ve-not-ready (RNR) frames recei ved.
The counter can i ncl ude the fol l owi ng qual i er:
RNR recei ved, buffer unavai l abl e
Remote process errors
Thi s counter i ndi cates errors for both VAX P.S.I . and DDCMP l i nes. For VAX
P.S.I . operati ons, thi s counter i ndi cates an i nval i d n(R) and a frame reject (FRMR)
sent over the l i ne. The counter can i ncl ude the fol l owi ng qual i ers:
I nval i d n(R) recei ved
FRMR sent, header format error
These errors usual l y i ndi cate that the DCE i s functi oni ng i ncorrectl y.
For DDCMP operati ons, thi s counter i ndi cates the number of remote DDCMP
processi ng fai l ures. DECnet for OpenVMS mai ntai ns thi s counter onl y for DMP
and DMF l i nes. For a mul ti poi nt ci rcui t, thi s counter reects the total errors for
the control stati on, and not for each tri butary. These errors may be caused by a
programmi ng error or a hardware mal functi on at the adjacent node. They coul d
al so be caused by a ci rcui t error that was not detected by the Data Li nk protocol .
Thi s counter may i ncl ude any of the fol l owi ng qual i ers i f they contri bute to these
errors:
NAKs recei ved, recei ve overrun
NAKs sent, header format error
Sel ecti on address errors
Streami ng tri butari es
For DDCMP l i nes, thi s counter corresponds to events 5.4 and 5.68.
Ring beacons initiated
An FDDI counter that i ndi cates the number of ti mes thi s stati on i ni ti ated the
ri ng beacon process.
Ring initializations initiated
An FDDI counter that i ndi cates the number of ti mes thi s stati on i ni ti ated a ri ng
rei ni ti al i zati on.
Ring initializations received
An FDDI counter that i ndi cates the number of ti mes another stati on i ni ti ated
ri ng rei ni ti al i zati on.
Ring purge errors
An FDDI counter that i ndi cates the number of ti mes the ri ng purger recei ved a
token whi l e sti l l i n the ri ng purge state.
Remote reply timeouts
Thi s counter i ndi cates the number of ti mes the retransmi t ti mer for that l i ne has
expi red. Ei ther the l i ne i s not connected to a modem, the PSDN i s not respondi ng
fast enough, or the retransmi t ti mer i s set too l ow.
Thi s counter i ndi cates the number of seconds that el apsed si nce the l i ne counters
were zeroed. Thi s counter provi des a ti me frame for other counter val ues. The
software i ncrements thi s counter every second and cl ears i t when other counters
are cl eared.
B10
B.3 Line Counters
Send failure
Thi s counter i ndi cates the total number of ti mes a transmi t attempt fai l ed. For
each i ncrement of the counter, a type of fai l ure i s recorded, as fol l ows:
Excessi ve col l i si ons
Carri er check fai l ed
Short ci rcui t
Open ci rcui t
Frame too l ong
Remote fai l ure to defer
The short ci rcui t fai l ure i s al so reported each ti me a packet i s transmi tted usi ng
a DEQNA wi th a DECOM transcei ver.
System buffer unavailable
Thi s counter i ndi cates the total number of ti mes no system buffer was avai l abl e
for an i ncomi ng frame. Thi s can be any buffer between the hardware and the
user buffers (those suppl i ed on recei ve requests).
Traces initiated
An FDDI counter that i ndi cates the number of ti mes thi s l i nk i ni ti ated the
PC-Trace process.
Traces received
An FDDI counter that i ndi cates the number of ti mes another l i nk i ni ti ated the
PC-Trace process.
Unrecognized frame destination
Thi s counter i ndi cates the number of ti mes a frame was di scarded because there
was no portal wi th the protocol enabl ed. The count i ncl udes frames recei ved for
the physi cal address onl y. I t does not i ncl ude frames recei ved for the mul ti cast or
broadcast address.
User buffer unavailable
Thi s counter i ndi cates the total number of ti mes no user buffer was avai l abl e for
an i ncomi ng frame that passed al l l teri ng. The user buffer i s one suppl i ed by
the user on a recei ve request.
B.4 Node Counters
Thi s secti on contai ns a descri pti on of each node counter.
Aged packet loss
Thi s counter i ndi cates the number of data packets di scarded for vi si ti ng too
many nodes. Thi s usual l y occurs whi l e the nodes throughout the network are
recoveri ng from a di srupti on (for exampl e, when a ci rcui t or l i ne goes down) i n
the former path to a desti nati on. Thi s counter i s mai ntai ned onl y on routi ng
nodes and corresponds to event 4.0 (aged packet l oss).
Buffer unavailable
Thi s counter i ndi cates the number of data segments transferred from the remote
node that were di scarded because of i nsufci ent cache bufferi ng.
Bytes received
Thi s counter i ndi cates the number of user data bytes recei ved from a remote
node. Thi s i ncl udes i nterrupt messages, but excl udes Connect, Accept, Reject,
and Di sconnect messages.
B11
B.4 Node Counters
Bytes sent
Thi s counter i ndi cates the number of user data bytes sent to a remote node.
Connects received
Thi s counter i ndi cates the number of l ogi cal l i nk connecti on requests recei ved by
the l ocal node.
Connects sent
Thi s counter i ndi cates the number of l ogi cal l i nk connecti on requests sent by the
l ocal node.
Maximum logical links active
Thi s counter i ndi cates the l argest number of l ogi cal l i nks that have been acti ve
si nce DECnet for OpenVMS software was started or si nce executor counters were
zeroed.
Messages received
Thi s counter i ndi cates the number of NSP messages recei ved from a remote node.
Messages sent
Thi s counter i ndi cates the number of NSP messages sent to a remote node.
Node out-of-range packet loss
Thi s counter i ndi cates the number of data packets di scarded because the
desti nati on nodes address i s greater than the maxi mum address dened for
the l ocal node. Thi s counter corresponds to event 4.2 (node out-of-range packet
l oss).
Node unreachable packet loss
Thi s counter i ndi cates the number of data packets l ost because the desti nati on
node coul d not be accessed. Thi s counter i s mai ntai ned onl y on routi ng nodes.
Thi s counter corresponds to event 4.1 (node unreachabl e packet l oss).
Oversized packet loss
Thi s counter i ndi cates the number of recei ved data packets that were too l arge
to forward because of the bl ock si ze of the data l i nk that woul d be used. Thi s
counter i s mai ntai ned onl y on routi ng nodes, and corresponds to event 4.3
(oversi zed packet l oss).
Packet format error
Thi s counter i ndi cates the number of packet format errors that occur because of
i nval i d packet control i nformati on. Thi s counter corresponds to event 4.4 (packet
format error).
Partial routing update loss
Thi s counter i ndi cates the number of recei ved routi ng messages that were too
l ong to process. Part of a routi ng update may be l ost i f i t contai ns a reachabl e
node wi th an address greater than the maxi mum address dened for the l ocal
node. Thi s counter i s mai ntai ned onl y on routi ng nodes, and corresponds to event
4.5 (parti al routi ng update l oss).
Received connect resource errors
Thi s counter i ndi cates the number of i nbound connect messages for whi ch the
l ocal node di d not have sufci ent resources. These errors may resul t from
dynami c memory probl ems or too few l ogi cal l i nk sl ots; that i s, the MAXI MUM
LI NKS parameter val ue i s too smal l .
B12
B.4 Node Counters
Response timeouts
Thi s counter i ndi cates the number of ti mes there was no response to an NSP
segment wi thi n the al l otted ti meout peri od. Thi s i mpl i es that the l ocal node i s
havi ng to retransmi t messages. Such retransmi ssi on can be caused ei ther by
messages bei ng di scarded i n the network or by a wi de vari ance i n the round-tri p
del ay to the node. Normal l y, i t i ndi cates an overl oad condi ti on i n the network.
Thi s counter i ndi cates the number of seconds that have el apsed si nce the node
counters were zeroed. I t provi des a ti me frame for other counter val ues. The
software i ncrements thi s counter every second and cl ears i t when other counters
are cl eared.
Verication reject
Thi s counter i ndi cates the number of recei ved veri cati on messages that were
i nval i d. I t corresponds to event 4.6 (veri cati on reject).
B.5 X.25 Protocol Module DTE Counters
Thi s secti on contai ns a descri pti on of each X.25 protocol modul e DTE counter.
These counters appl y onl y to VAX P.S.I . operati ons.
Note
Al though some systems do not support VAX P.S.I ., you can manage remote
VAX P.S.I . systems from the l ocal node.
Bytes received
Thi s counter i ndi cates the number of bytes of data recei ved by the l ocal DTE.
You can use thi s i nformati on together wi th the data bl ocks recei ved counter to
determi ne the total trafc l oad.
Bytes sent
Thi s counter i ndi cates the number of bytes of data sent by the l ocal DTE. You can
use thi s i nformati on together wi th the data bl ocks sent counter to determi ne the
total trafc l oad.
Calls received
Thi s counter i ndi cates the number of i ncomi ng cal l s recei ved.
Calls sent
Thi s counter i ndi cates the number of outgoi ng cal l s made.
Thi s counter i ndi cates the number of data bl ocks recei ved by the l ocal DTE.
Data blocks sent
Thi s counter i ndi cates the number of data bl ocks sent by the l ocal DTE.
Fast selects received
Thi s counter i ndi cates the number of cal l s recei ved wi th the fast sel ect faci l i ty
speci ed.
Fast selects sent
Thi s counter i ndi cates the number of cal l s sent wi th the fast sel ect faci l i ty
speci ed.
B13
B.5 X.25 Protocol Module DTE Counters
Locally initiated resets
Thi s counter i ndi cates the number of resets sent by the l ocal DTE.
Maximum channels active
Thi s counter i ndi cates the maxi mum number of channel s from the l ogi cal
channel s l i st that were acti ve at any one ti me si nce the counters were l ast
zeroed.
Thi s counter appl i es onl y to those channel s dened by the CHANNELS parameter
of the SET MODULE X25-PROTOCOL command.
Maximum switched circuits active
Thi s counter i ndi cates the number of swi tched vi rtual ci rcui ts that were acti ve at
any one ti me si nce the counters were l ast zeroed.
Network initiated resets
Thi s counter i ndi cates the number of resets (ori gi nated by the PSDN) recei ved by
the l ocal DTE.
Received call resource errors
Thi s counter i ndi cates the number of ti mes an i ncomi ng cal l has been rejected
because of i nsufci ent resources or an i ncorrect congurati on (for exampl e, no
desti nati on or object speci ed).
Remotely initiated resets
Thi s counter i ndi cates the number of resets (ori gi nated by a remote DTE) recei ved
by the l ocal DTE.
Restarts
Thi s counter i ndi cates the number of ti mes the restart protocol procedure was
used on the DTE.
Thi s counter i ndi cates the number of seconds that have el apsed si nce the modul e
val ues. The VAX P.S.I . software i ncrements thi s counter every second and cl ears
i t when the counters are zeroed.
B.6 X.25 and X.29 Server Module Counters
Thi s secti on contai ns a descri pti on of each X.25 and X.29 server modul e counter.
These counters appl y onl y to VAX P.S.I . operati ons.
Note
Incoming calls rejected, no resources
Thi s counter i ndi cates the number of ti mes the i ncomi ng cal l handl er rejected a
request to set up a vi rtual ci rcui t because of i nsufci ent resources. I t i ncl udes
cal l s rejected by securi ty for the X.25 server modul e.
Maximum circuits active
Thi s counter i ndi cates the number of swi tched vi rtual ci rcui ts that have been set
up si nce the counters were l ast zeroed.
B14
B.6 X.25 and X.29 Server Module Counters
Thi s counter i ndi cates the number of seconds that have el apsed si nce the modul e
val ues. The VAX P.S.I . software i ncrements thi s counter every second and cl ears
i t when the counters are zeroed.
B15
C
States and Transitions
C.1 Overview
Each ci rcui t, l i ne, and l ogi cal l i nk has sets of states and substates that reect
i nternal network software acti vi ty. The fol l owi ng secti ons contai n descri pti ons of
ci rcui t, l i ne, and l i nk states, and thei r substates and transi ti ons.Thi s secti on al so
descri bes X25-SERVER modul e and DTE states, substates, and thei r transi ti ons.
You cannot set or cl ear these substates, but you can di spl ay them by usi ng NCP.
NCP al l ows for management of the l ocal node and for remote management of any
DECnet node that you speci fy as the executor. The di spl ay that you see for the
ci rcui t, l i ne, or l i nk state you speci fy depends on the supported features of the
parti cul ar DECnet system that you are managi ng.
Chapter 3.
C.2 Circuit and Line States and Transitions
Tabl e C1 l i sts al l possi bl e network management ci rcui t and l i ne states and
substates. Tabl e C2 provi des a l i st of state transi ti ons that take pl ace i n
response to certai n user-i ni ti ated NCP functi ons. Some substates i n these
tabl es have an AUTO- prex. These substates occur when ci rcui t or l i ne
servi ce operati ons take pl ace. Refer to the DNA PhaseI V Network Management
Functional Specication for further i nformati on about ci rcui t or l i ne states,
substates, and thei r transi ti ons.
Table C1 Circuit and Line States and Substates
State Substate Meaning
OFF None The ci rcui t/l i ne cannot be used.
ON None The ci rcui t/l i ne i s i n normal use by the
owner.
-SYNCHRONI ZI NG The ci rcui t/l i ne i s i n the hardware
i ni ti al i zati on cycl e. For X.25 permanent
vi rtual ci rcui ts, the ci rcui t i s bei ng reset,
restarted, or an error has occurred.
-STARTI NG The ci rcui t/l i ne i s i n the owner routi ng
i ni ti al i zati on cycl e.
-REFLECTI NG The ci rcui t/l i ne i s i n use for passi ve
l oopback testi ng.
-AUTODUMPI NG The ci rcui t/l i ne i s reserved for upl i ne
dumpi ng.
C1
Table C1 (Cont.) Circuit and Line States and Substates
-AUTOSERVI CE The ci rcui t/l i ne i s reserved for servi ce use.
-AUTOLOADI NG The ci rcui t/l i ne i s i n use for automati c
l oadi ng.
-AUTOTRI GGERI NG The ci rcui t/l i ne i s i n use for automati c
tri ggeri ng.
-DUMPI NG The ci rcui t/l i ne i s i n use by the operator for
upl i ne dumpi ng.
-LOADI NG The ci rcui t/l i ne i s i n use by the operator for
l oadi ng.
-LOOPI NG The ci rcui t/l i ne i s i n use by the operator for
acti ve ci rcui t or l i ne l oopback testi ng.
-TRI GGERI NG The ci rcui t/l i ne i s i n use by the operator for
tri ggeri ng.
-FAI LED The DLM SVC has not been abl e
successful l y to cal l the remote DTE, and the
maxi mum recal l s l i mi t has been reached.
SERVI CE None The ci rcui t/l i ne i s reserved by the operator
for an acti ve servi ce functi on.
-REFLECTI NG The ci rcui t/l i ne i s i n use for passi ve
l oopback testi ng.
-LOADI NG The ci rcui t/l i ne i s i n use by the operator for
l oadi ng.
-LOOPI NG The ci rcui t/l i ne i s i n use by the operator for
l oopback testi ng.
-TRI GGERI NG The ci rcui t/l i ne i s i n use by the operator for
tri ggeri ng.
Table C2 Circuit and Line State Transitions
Old State New State Cause of Change
Any OFF Operator commands for non-
X.25 l i nes and ci rcui ts: SET
LI NE STATE OFF, SET
CI RCUI T STATE OFF
OFF ON-STARTI NG Operator command for non-X.25
l i nes and ci rcui ts: SET LI NE
STATE ON, SET CI RCUI T
STATE ON
ON-SYNCHRONI ZI NG Operator command for X.25
l i nes and ci rcui ts: SET LI NE
STATE ON
SERVI CE Operator command: SET LI NE
STATE SERVI CE
C2
Table C2 (Cont.) Circuit and Line State Transitions
ON OFF Operator command: SET LI NE
STATE OFF and SET CI RCUI T
STATE OFF
ON-STARTI NG Routi ng restarted the data l i nk
(from ei ther end).
ON-SYNCHRONI ZI NG Hardware i s bei ng restarted on
ei ther end of the l i nk, or X.25
vi rtual ci rcui t has been cl eared.
ON-REFLECTI NG The l ocal node recei ved a ci rcui t
/l i ne l oopback message from a
remote system.
ON-AUTOSERVI CE NETACP recei ved a servi ce
request.
ON-LOADI NG Operator command: LOAD
ON-LOOPI NG Operator command: LOOP
CI RCUI T
ON-TRI GGERI NG Operator command: TRI GGER
SERVI CE Operator command: SET
LI NE STATE SERVI CE, SET
CI RCUI T STATE SERVI CE
ON-STARTI NG ON Routi ng i ni ti al i zati on
compl eted.
ON-REFLECTI NG The l ocal node recei ved a ci rcui t
remote node.
request.
CI RCUI T
ON-SYNCHRONI ZI NG None The ci rcui t/l i ne i s attempti ng to
come up.
OFF Operator command: SET
CI RCUI T STATE OFF
ON For an X.25 PVC, the hardware
has been restarted and both
ends of the PVC have agreed to
communi cate.
ON-FAI LED For an outgoi ng DLM SVC,
the MAXI MUM RECALLS
l i mi t has been reached and
the remote DTE sti l l cannot be
cal l ed successful l y.
C3
ON-REFLECTI NG ON-SERVI CE A passi ve ci rcui t/l i ne l oopback
operati on termi nated.
request.
CI RCUI T
ON-AUTOSERVI CE ON-STARTI NG NML rel eased the l i ne.
ON-AUTOLOADI NG NML i ni ti ated a l oad operati on.
ON-AUTOTRI GGERI NG NML i ni ti ated a tri gger
operati on.
ON-AUTOLOADI NG ON-AUTOSERVI CE The l oad operati on compl eted.
ON-AUTOTRI GGERI NG ON-AUTOSERVI CE The tri gger operati on
compl eted.
ON-LOADI NG ON-STARTI NG The l oad operati on compl eted.
ON-LOOPI NG ON-STARTI NG The acti ve ci rcui t/l i ne l oopback
test compl eted.
ON-TRI GGERI NG ON-STARTI NG The tri gger operati on
compl eted.
SERVI CE SERVI CE-
SYNCHRONI ZI NG
The ci rcui t/l i ne i s attempti ng to
come up i n MOP mode.
SERVI CE-REFLECTI NG The l ocal node recei ved a ci rcui t
remote node.
SERVI CE-LOADI NG Operator command: LOAD
SERVI CE-LOOPI NG Operator command: LOOP
CI RCUI T
SERVI CE-TRI GGERI NG Operator command: TRI GGER
OFF Operator command: SET LI NE
STATE OFF, SET CI RCUI T
STATE OFF
ON-STARTI NG Operator command: SET LI NE
STATE ON
SERVI CE-REFLECTI NG SERVI CE A passi ve ci rcui t/l i ne l oopback
test compl eted.
SERVI CE-LOADI NG Operator command: LOAD
SERVI CE-LOOPI NG Operator command: LOOP
CI RCUI T
SERVI CE-TRI GGERI NG Operator command: TRI GGER
C4
SERVI CE-LOADI NG SERVI CE The l oad operati on compl eted.
SERVI CE-LOOPI NG OFF Operator command: SET
CI RCUI T STATE OFF
SERVI CE The acti ve ci rcui t/l i ne l oopback
test compl eted.
SERVI CE-TRI GGERI NG SERVI CE The tri gger operati on
compl eted.
C.3 Link States
Tabl e C3 l i sts al l possi bl e network management states for l ogi cal l i nks. Refer
to the Network Services Protocol Functional Specication for further i nformati on
about l i nk states.
Table C3 Link States
State Meaning
CC sendi ng Connect conrm sendi ng. Conrmati on of a connecti on i s
bei ng sent from the desti nati on node i n response to a connect
i ni ti ate from the ori gi nati ng node.
CI ACKed Connect i ni ti ate acknowl edged. The ori gi nati ng node has
recei ved a connect conrm from the desti nati on node.
CI recei ved Connect i ni ti ate recei ved. The desti nati on node has recei ved
a connect i ni ti ate from the ori gi nati ng node.
CI sendi ng Connect i ni ti ate sendi ng. The ori gi nati ng node i s sendi ng a
connect i ni ti ate request to the desti nati on node.
cl osed The desti nati on port i s not avai l abl e. The l ogi cal l i nk has
been di sconnected, but the user program has not yet desti ned
the channel to the network devi ce.
DI recei ved Di sconnect i ni ti ate recei ved. The desti nati on node has
recei ved a di sconnect i ni ti ate message from the ori gi nati ng
node.
DI sendi ng Di sconnect i ni ti ate sendi ng. The ori gi nati ng node i s sendi ng
a di sconnect i ni ti ate message to the desti nati on node.
run The l ogi cal l i nk may be used for sendi ng and recei vi ng data.
C.4 DTE States and Transitions
Tabl e C4 l i sts al l possi bl e VAX P.S.I . management states and substates for
DTEs. Tabl e C5 provi des a l i st of DTE state transi ti ons that take pl ace.
Note
C5
Table C4 DTE States and Substates
OFF RUNNI NG X.25 l evel 2 and l evel 3 software i s operati onal but
the DTE i s not avai l abl e for use. I ncomi ng cal l s are
cl eared.
SYNCHRONI ZI NG X.25 l evel 2 software i s operati onal but l evel 3
software i s not. The DTE i s not avai l abl e for use.
UNSYNCHRONI ZED X.25 l evel s 2 and 3 are not operati onal and the DTE
i s not avai l abl e for use.
ON RUNNI NG The DTE i s avai l abl e for normal use.
SYNCHRONI ZI NG X.25 l evel 2 software i s operati onal , l evel 3 software
i s starti ng up, and the DTE wi l l soon be avai l abl e
for use.
UNSYNCHRONI ZED X.25 l evel 2 software i s starti ng up and the DTE
wi l l soon be avai l abl e for use.
SHUT RUNNI NG X.25 l evel s 2 and 3 are operati onal but the DTE
i s not to be used for any new acti vi ty; that i s, al l
exi sti ng vi rtual ci rcui ts wi l l be al l owed to compl ete
thei r operati ons. I ncomi ng cal l s are cl eared.
SYNCHRONI ZI NG X.25 l evel 2 software i s operati onal and l evel 3
software i s starti ng up. When the DTE i s avai l abl e
for use, no ci rcui ts may be establ i shed.
UNSYNCHRONI ZED X.25 l evel 2 software i s starti ng up. When the DTE
i s avai l abl e for use, no ci rcui ts may be establ i shed.
Table C5 DTE State Transitions
OFF-RUNNI NG ON-RUNNI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE ON
OFF-SYNCHRONI ZI NG X.25 l evel 3 software i s
resynchroni zi ng.
OFF-UNSYNCHRONI ZED X.25 l evel 2 software i s
resynchroni zi ng.
OFF-
UNSYNCHRONI ZED
ON-UNSYNCHRONI ZED Operator command: SET
MODULE X25-PROTOCOL
DTE STATE ON
OFF-SYNCHRONI ZI NG X.25 l evel 2 startup has
compl eted.
OFF-SYNCHRONI ZI NG ON-SYNCHRONI ZI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE ON
OFF-RUNNI NG X.25 l evel 3 startup has
compl eted.
OFF-UNSYNCHRONI ZED X.25 l evel 2 software i s
resynchroni zi ng.
C6
Table C5 (Cont.) DTE State Transitions
ON-RUNNI NG OFF-RUNNI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE OFF
SHUT-RUNNI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE SHUT
ON-SYNCHRONI ZI NG X.25 l evel 3 software i s
resynchroni zi ng.
ON-UNSYNCHRONI ZED X.25 l evel 2 software i s
resynchroni zi ng.
ON-
UNSYNCHRONI ZED
OFF-UNSYNCHRONI ZED Operator command: SET
MODULE X25-PROTOCOL
DTE STATE OFF
SHUT-UNSYNCHRONI ZED Operator command: SET
MODULE X25-PROTOCOL
DTE STATE SHUT
ON-SYNCHRONI ZI NG X.25 l evel 2 startup has
compl eted.
ON-SYNCHRONI ZI NG OFF-SYNCHRONI ZI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE OFF
SHUT-SYNCHRONI ZI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE SHUT
ON-RUNNI NG X.25 l evel 3 startup has
compl eted.
ON-UNSYNCHRONI ZED X.25 l evel 2 software i s
resynchroni zi ng.
SHUT-RUNNI NG OFF-RUNNI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE OFF
ON-RUNNI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE ON
SHUT-SYNCHRONI ZI NG X.25 l evel 3 software i s
resynchroni zi ng.
SHUT-UNSYNCHRONI ZED X.25 l evel 2 software i s
resynchroni zi ng.
SHUT-
UNSYNCHRONI ZED
OFF-UNSYNCHRONI ZED Operator command: SET
MODULE X25-PROTOCOL
DTE STATE OFF
ON-UNSYNCHRONI ZED Operator command: SET
MODULE X25-PROTOCOL
DTE STATE ON
SHUT-SYNCHRONI ZI NG X.25 l evel 2 startup has
compl eted.
C7
Table C5 (Cont.) DTE State Transitions
SHUT-
SYNCHRONI ZI NG
OFF-SYNCHRONI ZI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE OFF
ON-SYNCHRONI ZI NG Operator command: SET
MODULE X25-PROTOCOL
DTE STATE ON
SHUT-RUNNI NG X.25 l evel 3 startup has
compl eted.
SHUT-UNSYNCHRONI ZED X.25 l evel 2 software i s
resynchroni zi ng.
C.5 X.25 Server Module States and Transitions
Tabl e C6 l i sts al l possi bl e VAX P.S.I . management states for the X.25 server
modul e. Tabl e C7 summari zes state transi ti ons that take pl ace.
Note
Table C6 X.25 Server States
State Meaning
OFF The modul e i s not i n use.
ON The modul e i s avai l abl e for normal use.
SHUT The modul e i s to be cl osed down but onl y when al l present acti vi ty has ceased.
Table C7 X.25 Server State Transitions
OFF ON Operator command: SET MODULE X25-SERVER
STATE ON
ON OFF Operator command: SET MODULE X25-SERVER
STATE OFF
SHUT Operator command: SET MODULE X25-SERVER
STATE SHUT
SHUT ON Operator command: SET MODULE X25-SERVER
STATE ON
OFF Operator command: SET MODULE X25-SERVER
STATE OFF
C8
D
Event Class and Type Summary
Thi s appendi x i ncl udes a summary of NCP events i n terms of thei r cl ass and
type. I n general , event cl asses rel ate to speci c l ayers of the DNA archi tecture.
The event l oggi ng components support the event cl asses summari zed.
NCP al l ows for management of the l ocal node and for remote management of
any DECnet node that you speci fy as the executor. The di spl ay that you see for
the event that you speci fy depends on the supported features of the parti cul ar
DECnet system that you are managi ng.
Chapter 3.
Event Class Description
0 Network Management l ayer
1 Appl i cati ons l ayer
2 Sessi on Control l ayer
3 End Communi cati ons l ayer
4 Routi ng l ayer
5 Data Li nk l ayer
6 Physi cal Li nk l ayer
7 X.25 packet l evel events
831 Reserved for other common cl asses
3263 RSTS system speci c
6495 RSX system speci c
96127 TOPS 10/20 system speci c
128159 OpenVMS system speci c
160191 RT system speci c
192223 CT system speci c
224255 Communi cati on server speci c
256352 Reserved for future use
353 Di gi tal Di stri buted Name Servi ce (DECdns) cl erk events
354479 Reserved for future use
480511 Customer speci c
DECnet for OpenVMS l ogs events onl y for event cl asses 0, 3, 4, and 128159. I f
you attempt to turn on l oggi ng for any other event, i t does not get l ogged. Al l
other cl asses are supported for l oggi ng of processed events from other remote
nodes. Events i n cl ass 353 are l ogged onl y i n networks where the Di gi tal
Di stri buted Name Servi ce (DECdns) software i s runni ng.
D1
Events i n cl ass 7 are l ogged onl y on nodes that have VAX P.S.I . i nstal l ed.
I f the l oggi ng si nk i s the moni tor and no name i s speci ed, DECnet for OpenVMS
uses the OPCOM faci l i ty to di spl ay event messages on al l termi nal s enabl ed as
NETWORK (by means of REPLY/ENABLE=NETWORK), i ncl udi ng the consol e.
Event messages have the fol l owi ng format:
event type class.type, event-text
from node address [(node-name)] dd-mmm-yy hh:mm:ss.ms
component-type, event-qualifiers,...
The event text i s a standard text message for each event cl ass and type. The
message format al so i ncl udes the source node (address and node name, i f
avai l abl e) and ti me stamp for when the event occurred. For most events, the
message format i ncl udes the component type and name for whi ch the event
appl i es. Fi nal l y, the message format may i ncl ude one or more event qual i ers
that provi de addi ti onal i nformati on as to the cause of the event. The fol l owi ng
exampl e i s a typi cal message that may be di spl ayed on the consol e:
%%%%%%%%%%% OPCOM 29-JUN-1992 13:49:05.45 %%%%%%%%%%%
Message from user DECNET on FALSE
DECnet event 4.15, adjacency up
From node 4.884 (FALSE), 29-JUN-1992 13:49:02.09
Circuit BNA-0, Adjacent node = 4.894 (PASSWD)
The i nformati on accompanyi ng each event descri pti on i n Secti on D.1 i ncl udes a
bri ef descri pti on of event qual i ers that may be di spl ayed for the event.
Note that OPCOM does not di spl ay l i ne or node counters on the termi nal devi ce.
However, they can be wri tten to the consol e si nk.
D.1 Network Management Layer Events
The fol l owi ng speci c event cl asses and types are supported for the network
management l ayer. Onl y those events and enti re event cl asses marked wi th an
asteri sk (*) are l ogged by DECnet for OpenVMS components.
0.0 Event records lost*
Events occurred too rapi dl y for the event l ogger to buffer them.
0.1 Automatic node counters
A node counter ti mer expi red, thus prompti ng thi s event. Thi s message di spl ays
the name of the node to whi ch the event appl i es, al ong wi th the node counters for
that node.
0.2 Automatic line counters
A l i ne counter ti mer expi red, thereby produci ng thi s event. Thi s message di spl ays
the name of the l i ne to whi ch the event appl i es, al ong wi th the l i ne counters for
that l i ne.
0.3 Automatic circuit service*
An adjacent node requested an automati c ci rcui t servi ce operati on. Thi s message
di spl ays the name of the ci rcui t to whi ch the event appl i es, al ong wi th the
fol l owi ng event qual i ers: the servi ce functi on performed (l oad or dump), the
status of the operati on (requested, successful , or fai l ed), the node address, the l e
speci cati on, and the software type. I f the operati on fai l s, thi s status i ncl udes an
NML error message and detai l s.
D2
D.1 Network Management Layer Events
0.4 Line counters zeroed
Li ne counters were zeroed. Thi s message di spl ays the name of the l i ne to whi ch
the event appl i es. The event l ogger l ogs these counters pri or to the executi on of a
request to zero them.
0.5 Node counters zeroed
Node counters were zeroed. Thi s message di spl ays the name of the node to whi ch
the event appl i es. The event l ogger l ogs these counters pri or to the executi on of a
request to zero them.
0.6 Passive loopback*
The software i ni ti ated or termi nated a passi ve l oopback test on behal f of an
adjacent node. Thi s message di spl ays the name of the l i ne to whi ch the event
appl i es, al ong wi th one event qual i er that speci es the state of the operati on
(i ni ti ated or termi nated).
0.7 Aborted service request*
An adjacent node requested a servi ce operati on over a l i ne connected to the l ocal
node. However, a probl em prevented i t from bei ng processed at the l ocal node.
Thi s message di spl ays the name of the l i ne to whi ch the event appl i es, al ong wi th
one event qual i er that speci es the reason for the fai l ure. The reason may be
one of the fol l owi ng:
Li ne open error
DECnet recei ved an MOP message and was unabl e to acqui re control of the
l i ne.
Li ne state change by hi gher l evel
The l i ne was preempted by a hi gher pri ori ty functi on. For exampl e, you used
NCP to turn off the l i ne.
Recei ve error
A l i ne error occurred whi l e the Network Management l ayer was tryi ng to
recei ve the request.
Recei ve ti meout
The l i ne message recei ve ti mer expi red before the request coul d be recei ved
from the adjacent node. Ei ther the ti mer was too short, the l i ne error l evel
was too great for any message to get through, or the adjacent node stopped
requesti ng.
Unrecogni zed request
A message was recei ved but was not recogni zabl e as a request for upl i ne
dumpi ng, downl i ne l oadi ng, or passi ve l oopback testi ng. The adjacent node
may be runni ng an i ncompati bl e versi on of the l i ne servi ce protocol .
0.8 Automatic counters*
A counter ti mer for a node, ci rcui t, or l i ne has expi red, thereby produci ng thi s
event. Thi s message di spl ays the name of the component to whi ch the event
appl i es, al ong wi th the counters for that component.
0.9 Counters zeroed*
Counters were zeroed for the node, ci rcui t, or l i ne. Thi s message di spl ays the
name of the component to whi ch the event appl i es. The event l ogger l ogs these
events pri or to the executi on of a request to zero them.
D3
D.2 Session Control Layer Events
D.2 Session Control Layer Events
The fol l owi ng speci c event cl asses and types are supported for the sessi on
control l ayer.
2.0 Local node state change
The operati onal state of the l ocal node changed because of an operator command.
Note, however, that the transi ti on from SHUT to OFF al so happens automati cal l y
when the l ast l ogi cal l i nk i s di sconnected (under normal operati on).
Thi s message di spl ays three event qual i ers: the reason for the state change
(operator command or normal operati on), the ol d state (ON, OFF, SHUT, or
RESTRI CTED), and the new state.
2.1 Access control reject
The l ocal node rejected a connecti on request because of i nval i d access control
i nformati on.
Thi s message di spl ays four event qual i ers: the name and address of the source
node, the object type number and process I D of the source process requesti ng the
connecti on, the object type number and process I D of the desti nati on process to
recei ve the connecti on request, and the i nval i d access control i nformati on.
D.3 End Communications Layer Events
The fol l owi ng speci c event cl asses and types are supported for the End
Communi cati ons l ayer. The Network Servi ces Protocol (NSP) i s the protocol that
operates wi thi n the End Communi cati ons l ayer. Onl y those events and enti re
event cl asses marked wi th an asteri sk (*) are l ogged by DECnet for OpenVMS
components.
3.0 Invalid message*
NSP recei ved a message that coul d not be i nterpreted. Thi s may i ndi cate a
software mal functi on i n ei ther the l ocal or remote NSP. Thi s message di spl ays
one event qual i erthe NSP message that was i nval i d. Refer to the Network
Services Protocol Functional Specication for a descri pti on of NSP messages.
3.1 Invalid ow control*
The remote NSP attempted to modi fy the l ocal ow control val ue i n an i nval i d
manner. Thi s may i ndi cate a software mal functi on i n ei ther the l ocal or remote
NSP. Thi s message di spl ays one event qual i erthe current ow control val ue.
Refer to the Network Services Protocol Functional Specication for a descri pti on
of ow control .
3.2 Database reused
The l ocal node recei ved a connecti on request from a node for whi ch there i s no
counter bl ock. Al l counter bl ocks have been previ ousl y used, and one of the
previ ousl y used bl ocks i s avai l abl e for thi s new node. Thi s resul ts i n the l oss of
node counters for the node that formerl y occupi ed the database entry.
Thi s message di spl ays the name of the node for whi ch the database entry was
formerl y used, al ong wi th the node counters for that node.
D.4 Routing Layer Events
The fol l owi ng speci c event cl asses and types are supported for the Routi ng l ayer.
Onl y those events and enti re event cl asses marked wi th an asteri sk (*) are
l ogged by DECnet for OpenVMS components.
D4
4.0 Aged packet loss*
Routi ng di scarded a packet because i t had vi si ted too many nodes. Thi s can be
a normal occurrence when the network i s reconguri ng i ts routi ng databases.
I t can be a fai l ure when the MAXI MUM HOPS val ue i s set too smal l . Thi s can
cause the MAXI MUM VI SI TS val ue to be too smal l for a path that shoul d be
usabl e.
one event qual i erthe packet header. Thi s i s i nformati on from the begi nni ng of
the packet. For non-broadcast packets, i t consi sts of a hexadeci mal byte of ags,
the deci mal desti nati on and source node addresses, and a hexadeci mal byte of
forwardi ng data. For broadcast packets, i t al so i ncl udes the physi cal address of
the desti nati on and source, the servi ce type, and the protocol type. Refer to the
Routing Layer Functional Specication for addi ti onal i nformati on.
4.1 Node unreachable packet loss*
Routi ng di scarded a packet because the l ocal node found that the desti nati on node
was unreachabl e. Thi s event provi des a trace of what has happened to packets
that are not reachi ng thei r desti nati on.
one event qual i erthe packet header (as descri bed for event 4.0).
4.2 Node out-of-range packet loss*
Routi ng di scarded a packet because the desti nati on node number was greater
than the maxi mum node number known to the l ocal node. Typi cal l y, thi s
resul ts from the addi ti on of a new node to the network wi thout i ncreasi ng the
MAXI MUM ADDRESS val ue on the l ocal node, yet expecti ng the l ocal node to
route packets to that node.
one event qual i erthe packet header (as descri bed for event 4.0).
4.3 Oversized packet loss*
Routi ng di scarded a packet because i t was too l arge to forward to the appropri ate
adjacent node. Typi cal l y, thi s occurs when the adjacent nodes buffer si ze i s too
smal l or when the source node sends a packet that i s too l arge.
Thi s message di spl ays the name of the l i ne over whi ch the packet was to be
forwarded, al ong wi th one event qual i erthe packet header (as descri bed for
event 4.0).
4.4 Packet format error*
Routi ng di scarded a packet because of a format error i n the packet header.
Thi s usual l y resul ts from a programmi ng error i n the packet formatti ng by the
adjacent node, though i t coul d resul t from a l i ne error that was not detected by
the l i ne protocol .
one event qual i erthe packet begi nni ng. Thi s consi sts of the rst 6 bytes of the
packet, di spl ayed as hexadeci mal .
4.5 Partial routing update loss*
Routi ng recei ved a routi ng message that contai ned node addresses greater than
the maxi mum address known to the l ocal node. Subsequentl y, i nformati on on
these nodes was l ost. Thi s occurs when the MAXI MUM ADDRESS val ue on
an adjacent node has been i ncreased to accommodate more nodes, but the l ocal
nodes has not.
D5
Thi s message di spl ays the name of the l i ne over whi ch thi s message was recei ved,
al ong wi th two event qual i ersthe packet header (as descri bed for event 4.0)
and the hi ghest node address i n the routi ng update that was l ost.
4.6 Verication reject*
An attempt to i ni ti al i ze wi th another node fai l ed. The l ocal node recei ved an
i nval i d password i n the veri cati on requested of the adjacent node duri ng routi ng
i ni ti al i zati on over the l i ne. Ei ther the l ocal node expected the wrong recei ve
password, or the adjacent node sent the wrong transmi t password.
one event qual i erthe address of the adjacent node that fai l ed to i ni ti al i ze.
4.7 Circuit down, circuit fault*
An error has occurred for the ci rcui t. Thi s message di spl ays the name of the
ci rcui t to whi ch the event appl i es, al ong wi th one event qual i erthe reason for
the event. The reason coul d be one of the fol l owi ng:
Adjacent node address change
The adjacent node changed addresses wi thout goi ng through the normal
i ni ti al i zati on sequence. Thi s i s al so l ogged when an adjacent node attempts
to i ni ti al i ze wi th the l ocal node, but the address of the adjacent node i s not i n
the database.
Adjacent node address out of range
The adjacent nodes address i s greater than the maxi mum address dened for
the l ocal node. Thi s may be caused by an i ncorrectl y dened node address or
by a fai l ure to update the l ocal nodes database when a new node was added.
Adjacent node bl ock si ze too smal l
The l i ne bl ock si ze provi ded by the adjacent node i s too smal l for normal
network operati on. The bl ock si ze may be set i ncorrectl y at the adjacent node.
Adjacent node l i stener recei ve ti meout
The node has recei ved no message over the data l i nk wi thi n the l ast 30
seconds. Thi s usual l y means that the remote node i s not runni ng.
Adjacent node l i stener recei ved i nval i d data
A test message sent by the adjacent node contai ned i nval i d or corrupted data.
Thi s i s most l i kel y caused by a hardware probl em.
Cal l fai l ed
An outgoi ng SVC cal l fai l ed. Thi s i s an X.25 event.
Data errors
The l i ne was decl ared down by the l i ne protocol of the l ocal node handl er
when the l i ne exceeded an error threshol d.
Dropped by adjacent node
The adjacent node was responsi bl e for breaki ng the ci rcui t connecti on.
I nval i d veri cati on seed val ue
A Routi ng i ni ti al i zati on message sent by an adjacent node i s not formatted
properl y. Thi s i s most l i kel y caused by a remote network software probl em.
Li ne synchroni zati on l ost
D6
The normal l i ne protocol was restarted or termi nated by the adjacent node.
Ei ther a l i ne exceeded an error threshol d, or network management i ni ti ated a
l i ne state change. DMR/DMC fai l ures that cause a l i ne synchroni zati on error
are as fol l ows:
Threshol d errors, i ncl udi ng more than ei ght attempts to transmi t a
message, or ei ght NAKs recei ved i n a row.
Start message recei ved i n the ON state (that i s, the remote system
detected an error and restarted the l i ne).
Mai ntenance requested whi l e i n the ON state (that i s, the remote system
tri ed to perform a mai ntenance operati on such as LOOP CI RCUI T).
Message was l ost because no buffer was avai l abl e i n CPU memory.
Nonexi stent memory error.
Procedure error, because of dri ver fai l ure or hardware fai l ure.
Ti meout on request to transmi t a message i n 255 seconds.
Power fai l ure.
Routi ng update checksum error
A routi ng update packet fai l ed i ts i nternal i ntegri ty test.
Unexpected packet type
A packet was recei ved out of the normal protocol sequence. For exampl e,
the l ocal node recei ved a normal data packet when i t expected a veri cati on
packet.
Veri cati on password requi red from Phase I I I node
A requi red routi ng i ni ti al i zati on password was not speci ed before an attempt
was made to i ni ti al i ze the Phase I I I node i n a Phase I V network.
Veri cati on recei ve ti meout
A requi red veri cati on packet was not recei ved from the adjacent node wi thi n
the requi red response ti me. Ei ther packets were l ost on the l i ne or a fai l ure
occurred at the adjacent node.
Versi on skew
The routi ng versi on of the adjacent node i s unacceptabl e to the l ocal node.
The operator may have i nstal l ed i ncorrect software at the adjacent node.
4.8 Circuit down*
An error has occurred for the ci rcui t. Thi s message di spl ays the name of the
ci rcui t to whi ch the event appl i es, al ong wi th the fol l owi ng event qual i ers: the
packet header (as descri bed for event 4.0), the reason (as descri bed for event 4.7),
and the address of the adjacent node.
4.9 Circuit down, operator initiated*
An operator i ni ti ated state change has occurred for the ci rcui t. Thi s message
fol l owi ng event qual i ersthe packet header (as descri bed for event 4.0), the
reason (as descri bed for event 4.7), and the addresses of the expected node and
the adjacent node.
D7
4.10 Circuit up*
A remote node has i ni ti al i zed on one of the physi cal l i nes connected to the l ocal
node. Thi s message di spl ays the name of the l i ne to whi ch the event appl i es,
al ong wi th one event qual i erthe address of the newl y i ni ti al i zed node.
Be sure to note that thi s event does not i mpl y that the node i s reachabl e.
Reachabi l i ty i s determi ned by the hi gher-l evel routi ng al gori thms.
4.11 Initialization failure, line fault*
A remote node fai l ed to i ni ti al i ze wi th the l ocal node because of a physi cal l i ne
error. Thi s message di spl ays the name of the l i ne to whi ch the event appl i es,
al ong wi th one event qual i erthe reason for the event (as descri bed for event
4.7).
4.12 Initialization failure*
A remote node fai l ed to i ni ti al i ze wi th the l ocal node because of a software error.
Thi s message di spl ays the name of the l i ne to whi ch the event appl i es, al ong
wi th two event qual i ersthe packet header (as descri bed for event 4.0) and the
reason (as descri bed for event 4.7).
4.13 Initialization failure, operator initiated*
A remote node fai l ed to i ni ti al i ze wi th the l ocal node because of an operator error.
three event qual i ersthe packet header (as descri bed for event 4.0), the reason
(as descri bed for event 4.7), and the versi on recei ved from the adjacent node.
4.14 Node reachability change*
Because of Routi ng operati on, the reachabi l i ty of a remote node has changed.
Thi s message di spl ays the name of the node to whi ch the event appl i es,
al ong wi th one event qual i erthe routi ng status of the node (reachabl e or
unreachabl e).
4.15 Adjacency up*
The adjacent node on the ci rcui t i s i ni ti al i zed. Thi s message di spl ays the name of
the ci rcui t to whi ch the event appl i es, and one event qual i erthe address of the
adjacent node.
4.16 Adjacency rejected*
The adjacent node on the ci rcui t i s not i ni ti al i zed. Thi s message di spl ays the
name of the ci rcui t to whi ch the event appl i es, and two event qual i ersthe
address of the adjacent node and the reason for the event (as descri bed for event
4.7).
4.17 Area reachability change*
Because of Routi ng operati on, the reachabi l i ty of an area has changed. Thi s
message di spl ays the name of the area to whi ch the event appl i es, al ong wi th one
event qual i erthe routi ng status of the area (reachabl e or unreachabl e).
4.18 Adjacency down*
An error has occurred for an adjacency on the ci rcui t. Thi s message di spl ays
the name of the ci rcui t to whi ch the event appl i es, al ong wi th the fol l owi ng event
qual i ersthe reason (as descri bed for event 4.7), the packet header (as descri bed
for event 4.4), and the address of the adjacent node on the ci rcui t.
D8
4.19 Adjacency down, operator initiated*
An adjacency on the ci rcui t i s down because of an operator request. Thi s message
fol l owi ng event qual i ersthe reason (as descri bed for event 4.7), the packet
header (as descri bed for event 4.0), and the addresses of the expected node and
the adjacent node on the ci rcui t.
D.5 Data Link Layer Events
The fol l owi ng speci c event cl asses and types are supported for the Data Li nk
l ayer. Onl y those events and enti re event cl asses marked wi th an asteri sk (*) are
l ogged by DECnet for OpenVMS components.
5.0 Locally initiated state change
The l i ne state changed because of an operator command. Thi s message
di spl ays the name of the l i ne to whi ch the event appl i es, al ong wi th two
event qual i ersthe ol d DDCMP state (HALTED, I STRT, ASTRT, RUNNI NG,
or MAI NTENANCE) and the new DDCMP state. Refer to the Digital Data
Communications Message Protocol Functional Specication for a descri pti on of
these states.
5.1 Remotely initiated state change
A remote user changed the l i ne state. Thi s message di spl ays the name of the l i ne
to whi ch the event appl i es, al ong wi th two event qual i ers (see event 5.0).
5.2 Protocol restart received in maintenance mode
The remote node restarted normal operati on whi l e the l ocal node had the l i ne
i n mai ntenance mode. Thi s message di spl ays the name of the l i ne to whi ch the
event appl i es.
5.3 Send error threshold
Too many data transmi ssi on errors occurred. Thi s message di spl ays the name of
the l i ne to whi ch the event appl i es, al ong wi th the l i ne counters for that l i ne and
one event qual i erthe address of the recei ved stati on (node).
5.4 Receive error threshold
Too many data recepti on errors occurred. Thi s message di spl ays the name of the
l i ne to whi ch the event appl i es, al ong wi th the l i ne counters for that l i ne and one
event qual i er (see event 5.3).
5.5 Select error threshold
Too many sel ecti on errors occurred. Thi s message di spl ays the name of the l i ne to
whi ch the event appl i es, al ong wi th the l i ne counters for that l i ne and one event
qual i er (see event 5.3).
5.6 Block header format error
DDCMP recei ved an i nval i d bl ock header. Thi s message di spl ays the name of the
l i ne to whi ch the event appl i es, al ong wi th one event qual i erthe i nval i d bl ock
header. Refer to the Digital Data Communications MessageProtocol Functional
Specication for a descri pti on of the bl ock header format.
5.7 Selection address error
The wrong tri butary responded i n the pol l i ng process. Thi s event occurs onl y for
a mul ti poi nt control stati on when one recei ves a message that does not match the
address of the currentl y sel ected tri butary.
D9
Thi s message di spl ays the name of the l i ne to whi ch the event appl i es, al ong
wi th three event qual i ersthe tri butary addresses of the sel ected tri butary, the
recei ved tri butary, and the previ ous tri butary.
5.8 Streaming tributary
A tri butary on the l i ne i s i mpedi ng the use of that l i ne. Thi s message di spl ays the
name of the l i ne to whi ch the event appl i es, al ong wi th two event qual i ersthe
tri butary address of the recei ved tri butary and the status of the tri butary. The
status may be any of the fol l owi ng:
Streami ng
Conti nued send after ti meout
Conti nued send after desel ect
Ended streami ng
5.9 Local buffer too small
A l ocal buffer i s too smal l for recei vi ng a bl ock of data. Thi s message di spl ays the
name of the l i ne to whi ch the event appl i es, al ong wi th two qual i ersthe l ength
(i n bytes) of the recei ved bl ock and the l ength (i n bytes) of the buffer.
5.13 Line initialization failure
An i ni ti al i zati on fai l ure occurred over a broadcast l i ne. Thi s message di spl ays the
name of the l i ne to whi ch the event appl i es.
5.14 Send failure on line
A data transmi ssi on attempt fai l ed on a broadcast l i ne. Thi s message di spl ays
the name of the l i ne to whi ch the event appl i es, al ong wi th two event qual i ers
the reason for the fai l ure and the di stance. Fai l ure reasons can i ncl ude
excessi ve col l i si ons, short or open ci rcui ts, too l ong a frame, a frami ng error,
an unrecogni zed frame desti nati on, a remote fai l ure to defer, a bl ock check error,
or data overrun.
5.15 Receive failed on line
Data was not recei ved on a broadcast l i ne. Thi s message di spl ays the name of the
l i ne to whi ch the event appl i es, al ong wi th two event qual i ersthe reason for
the fai l ure (as descri bed i n event 5.14) and the header, whi ch i ncl udes the source
and desti nati on node addresses and the protocol type.
5.16 Collision detect check failed on line
A check for col l i si on detecti on fai l ed on a broadcast l i ne. Thi s message di spl ays
the name of the l i ne to whi ch the event appl i es.
5.17 DTE up*
A l ocal DTE has synchroni zed X.25 l evel s 2 and 3. The DTE address and network
name are di spl ayed.
5.18 DTE down*
A l ocal DTE i s resynchroni zi ng X.25 l evel s 2 and 3. The DTE address and
network name are di spl ayed.
5.19 Retransmit maximum exceeded*
A frame has been retransmi tted the maxi mum number of ti mes for thi s l i ne
wi thout havi ng recei ved an acknowl edgment. Thi s means that ei ther the PSDN
or the l i ne to the PSDN has fai l ed.
D10
5.20 FRMR received*
A frame reject was recei ved. Thi s i s an error that you cannot correct by
retransmi tti ng the same frame agai n. Thi s i s usual l y due to a protocol vi ol ati on.
5.21 Illegal frame received*
The frame recei ved was not correctl y formatted, or was not the frame expected by
the X.25 protocol .
D.6 X.25 Packet Level Events
The fol l owi ng speci c event cl asses and types are supported for X.25 packet l evel
events. Onl y those events and enti re event cl asses marked wi th an asteri sk (*)
are l ogged by DECnet for OpenVMS components on nodes that have VAX P.S.I .
i nstal l ed.
7.0 DTE state change*
The operator has al tered the DTE state to that di spl ayed.
7.1 Illegal packet received*
VAX P.S.I . has recei ved a packet from the PSDN that i s i nval i d i n some way. Thi s
i s usual l y because of a protocol vi ol ati on by the PSDN.
7.2 Invalid LCN*
Thi s i s used whenever the l ogi cal channel number (LCN) i n the recei ved packet i s
i nval i d. For exampl e: the network has sent a restart packet wi th a nonzero LCN,
a cal l request packet on an LCN al ready i n use, or a packet on an unused LCN,
or tri ed to use an LCN reserved for a PVC. Thi s i s usual l y because of a protocol
vi ol ati on by the PSDN, but can be caused by not correctl y conguri ng the PVCs
i n the database.
7.3 Flow control invalid*
I nval i d P(S) recei ved or i nval i d P(R) recei ved. Thi s i s because of a protocol error.
7.4 Restart*
Ei ther a restart packet was recei ved or sent (i n whi ch case another event may
al so be l ogged). Thi s i ndi cates ei ther a protocol error or that the DCE or DTE has
rei ni ti al i zed.
7.5 Clear*
A cl ear packet wi th a nonzero cause code was ei ther recei ved or sent because of a
protocol error. See the PSDN documentati on for the cause of the message and the
di agnosti c codes di spl ayed.
7.6 Reset*
A reset packet wi th a nonzero cause code was ei ther recei ved or sent because of a
protocol error. See the PSDN documentati on for the cause of the message and the
di agnosti c codes di spl ayed.
7.7 Diagnostic*
A di agnosti c packet was ei ther recei ved or sent because of a protocol error. See
the PSDN documentati on for the cause of the message and the di agnosti c codes
di spl ayed.
7.8 Reject*
A reject packet was recei ved. VAX P.S.I . does not support recei vi ng reject packets,
because PSDNs are not permi tted to send them.
D11
D.6 X.25 Packet Level Events
7.9 Retransmission maximum exceeded*
The speci ed control packet has been transmi tted the maxi mum number of ti mes
wi thout bei ng acknowl edged by the PSDN. Usual l y thi s i s caused by a fai l ure by
the PSDN or the connecti on to the PSDN, but may be because the DTE i s not
correctl y congured.
7.10 Call failed*
The cal l (i ncomi ng or outgoi ng) has fai l ed because of one of the fol l owi ng reasons:
the appl i cati on process has exi ted, the appl i cati on has rejected the cal l , no
desti nati on has been set up, i nsufci ent resources are avai l abl e, a cal l has
col l i ded, securi ty checks have fai l ed, or a PSDN or a remote DTE has cl eared the
cal l .
7.11 State change*
The operator has i ni ti ated a state change, such as shutti ng down the node. Thi s
event i s di spl ayed when you shut down VAX P.S.I . (or a part of VAX P.S.I ., such
as the X.29 server).
D.7 System-Specic Events
The fol l owi ng system-speci c event cl asses and types are supported for OpenVMS
operati ng systems.
128.1 DAP CRC error detected
A CRC error was detected at the DAP l evel by the l e access l i stener (FAL) or
by RMS. The event di spl ays the name of the node to whi ch the connecti on was
establ i shed.
128.2 Duplicate PHASE 2 address error
A ci rcui t connecti on was attempted to a PHASE 2 node that was al ready
reachabl e. You are al l owed onl y one ci rcui t connecti on to any PHASE 2 node.
128.3 Process created
A process has been created to handl e an i ncomi ng X.25 cal l . The message di spl ays
the process name, process I D, and the status returned by the $CREPRC system
servi ce.
128.4 Process terminated
A process created to handl e an i ncomi ng X.25 cal l has termi nated. The message
di spl ays the process I D and the exi t status of the process.
D.8 Digital Distributed Name Service (DECdns) Clerk Events
The fol l owi ng speci c event cl asses and types are supported for the Di gi tal
Di stri buted Name Servi ce (DECdns) cl erk.
353.5 DECdns clerk unable to communicate with server
The DECdns cl erk was unabl e to communi cate wi th a DECdns server. Thi s
message di spl ays the name of the cl eari nghouse where the communi cati on fai l ed,
the node on whi ch the DECdns server servi ci ng the cl eari nghouse exi sts, and the
reason why the communi cati on fai l ed, whi ch may be any of the fol l owi ng:
Unknown cl eari nghouse
The requested cl eari nghouse i s not servi ced by the DECdns server that was
contacted. Thi s may happen when the cache mai ntai ned by the l ocal DECdns
cl erk contai ns outdated i nformati on for a di rectory.
Cl eari nghouse down
D12
D.8 Digital Distributed Name Service (DECdns) Clerk Events
A DECdns server i s unabl e to servi ce a request because the cl eari nghouse i s
not operati onal (stopped state).
Wrong state
A DECdns server i s unabl e to servi ce a request because the cl eari nghouse i s
currentl y starti ng up or shutti ng down.
Data corrupti on
A DECdns server i s unabl e to servi ce the request because the cl eari nghouse
l e has been corrupted.
No communi cati on
A network error occurred on the l ocal system or on the system contai ni ng
the DECdns server. The l ocal OpenVMS error i s di spl ayed as a part of thi s
message.
353.20 Local DECdns Advertiser error
Thi s event communi cates errors that are l ocal to the DECdns Adverti ser. Al l of
these errors have the prex ADV. The DECdns Adverti ser (DNS$ADVER) has
encountered an error that prevents proper operati on of the process. Exact errors
are l i sted i n the system error messages chapter i n the OpenVMS SystemMessages
and Recovery Procedures ReferenceManual.
D13
Index
A
Abbrevi ati ng NCP commands, 12
Abort, 47, 48, 49, 412
Addresses
physi cal , 19, 110
AUTO prex, C1
C
Ci rcui t and l i ne devi ces
BNA, A1
CI , A1
DI V, A1
DMB, A1, A2
DMC, A1
DMF, A1, A2
DMP, A1
DPV, A2
DSB, A1, A2
DSF, A1
DST, A1
DSV, A1, A2
DSW, A1, A2
DUP, A2
FZA, A2
I SA, A1
KFE, A1
KMV, A2
KMX, A2
KMY, A2
MFA, A2
MNA, A1
MXE, A1
QNA, A1
SVA, A1
TT, A1
TX, A1
UNA, A1
Ci rcui ts
cl eari ng counters, 3159
counters, 3159, B1, B4
devi ces, A1
i nformati on, 3120
states, C1 to C4
testi ng, 331, 349, 3111
transi ti ons, C1 to C4
CLEAR CI RCUI T command, 32
CLEAR EXECUTOR command, 36
CLEAR EXECUTOR NODE command, 311
CLEAR LI NE command, 312
CLEAR LOGGI NG command, 316
CLEAR LOGGI NG EVENTS command, 317
CLEAR LOGGI NG NAME command, 319
CLEAR MODULE X25-ACCESS command, 321
CLEAR MODULE X25-PROTOCOL command,
322
CLEAR MODULE X25-SERVER command, 325
CLEAR MODULE X29-SERVER command, 325
CLEAR NODE CI RCUI T command, 331
CLEAR NODE command, 327
CLEAR OBJECT command, 332
Command prompti ng
See Prompt syntax
Command syntax
See Syntax
Component names
usi ng wi l dcards wi th, 13
CONNECT command, 44
Connecti on tests, 44
i nvoki ng, 44
types of, 44
CONNECT NODE command, 334
CONNECT VI A command, 335
Consol es
connecti ng to host node, 334
connecti ng to host node on a speci ed ci rcui t,
335
COPY KNOWN NODES command, 336
Counters
ci rcui t, 3120, B1, B4
l i ne, 3161, B7
node, 3160, 3162, 3164, B11
summary of network, B1
X.25 protocol modul e, B13
X.25 server modul e, B14
D
Databases
ci rcui t
cl eari ng permanent val ues, 32
creati ng vol ati l e or permanent parameters,
357
Index1
Databases
ci rcui t (contd)
l oadi ng vol ati l e area wi th al l permanent
parameters, 356
resetti ng vol ati l e parameters to defaul t,
32
setti ng vol ati l e or permanent parameters,
357
cl eari ng sel ected permanent parameters, 36
copyi ng remote node data, 336
364
Ethernet congurator modul e
cl eari ng permanent val ues of a speci ed
ci rcui t, 320
390
executor node
cl eari ng vol ati l e or permanent l oop node
and ci rcui t val ues, 3111
creati ng vol ati l e or permanent network
control parameters, 364
parameters, 363, 385
setti ng vol ati l e or permanent network
control val ues, 364
host node
accessi ng X.25 target node parameters,
321
l i ne
cl ear and l oad vol ati l e parameters wi th
permanent data, 376
cl eari ng al l val ues, 312
creati ng parameters, 377
312
setti ng parameters, 377
l oggi ng
cl eari ng event-source val ues, 317
cl eari ng si nk-name, 319
cl eari ng vol ati l e data, 316
creati ng event-si nk parameters, 388
creati ng event-source parameters, 386
resetti ng event-source val ues, 317
resetti ng vol ati l e data, 316
setti ng event-si nk parameters, 388
setti ng event-source parameters, 386
l oop node
cl eari ng vol ati l e or permanent val ues on
executor node, 331
3111
setti ng vol ati l e or permanent val ues, 3111
node
cl eari ng vol ati l e or permanent val ues,
327
3106
Databases
node (contd)
setti ng vol ati l e or permanent val ues,
3106
object
3113
parameters, 3112
setti ng vol ati l e or permanent val ues,
3113
proxy
cl ear and l oad vol ati l e area wi th al l
permanent parameters, 375
resetti ng sel ected vol ati l e parameters to defaul t,
36
setti ng vol ati l e or permanent parameters, 364
updati ng al l vol ati l e or permanent data, 336
X.25 network connector-node access
cl eari ng vol ati l e or permanent names and
parameters, 321
for host node, 321, 392
X.25 or X.29 server modul e
cl eari ng vol ati l e or permanent cal l handl er
val ues, 325
creati ng vol ati l e or permanent cal l handl er
parameters, 3100
resetti ng vol ati l e or permanent cal l handl er
val ues, 325
setti ng vol ati l e or permanent cal l handl er
val ues, 3100
X.25 protocol modul e
cl eari ng vol ati l e or permanent val ues,
322
394
322
setti ng vol ati l e or permanent val ues, 394
Databases on l ocal node
di spl ayi ng
See Di spl ayi ng network parameters
DATA command, 46
Data i ntegri ty checki ng, 47
Data Li nk l ayer
events, D9
Data message l ength, 46, 411
Data tests, 46
DECdns
event messages, D12
events, D12
I DP, 37
i nterface, 37, 366
namespace, 37, 366
DECnet
ci rcui t and l i ne devi ces, A1
devi ces supported by, A1
event cl ass and type summary, D1 to D13
Index2
DECnet (contd)
usi ng the Network Control Program to control ,
11, 21
DECnet for OpenVMS
See DECnet
DECnet Test Sender/DECnet Test Recei ver uti l i ty
(DTS/DTR), 41
abort, 47, 48, 49, 412
commands, 43 to 412
abbrevi ati ng, 41
qual i ers, 41
syntax, 41
usi ng i n a batch job, 41
di recti ng output, 43
i nvoki ng, 42
pri nti ng, 43
testi ng network, 44 to 412
tests
connecti on, 44
data, 46
di sconnecti on, 48
exi ti ng, 43
i nterrupt, 411
subtests, 42
termi nati ng, 43
usi ng, 43
DEFI NE CI RCUI T command, 357
DEFI NE EXECUTOR command, 364
DEFI NE LI NE command, 377
DEFI NE LOGGI NG EVENTS command, 386
DEFI NE LOGGI NG STATE command, 388
DEFI NE MODULE CONFI GURATOR command,
390
DEFI NE MODULE X25-ACCESS command, 392
DEFI NE MODULE X25-PROTOCOL command,
394
DEFI NE MODULE X25-SERVER command,
3100
DEFI NE MODULE X29-SERVER command,
3100
DEFI NE NODE CI RCUI T command, 3111
DEFI NE NODE command, 3106
DEFI NE OBJECT command, 3113
Di recti ng output, 21
DI SCONNECT command, 48
Di sconnecti on tests, 48
types of, 49
DI SCONNECT LI NK command, 340
Di spl ayi ng network parameters
ci rcui t i nformati on, 3120
Ethernet congurator data, 3136
l i ne i nformati on, 3128
l ocal node i nformati on, 3125
l oggi ng i nformati on, 3133
network names and parameters from the X.25
access modul e, 3139
node i nformati on, 3147
object i nformati on, 3152
Di spl ayi ng network parameters (contd)
vol ati l e database i nformati on, 3118
vol ati l e l i nk i nformati on, 3131
X.25 and X.29 server parameters for cal l
handl er, 3145
X.25 protocol modul e parameters, 3141
DNS
See DECdns
DTE (data termi nal equi pment)
states and transi ti ons, C5
state transi ti ons, C6
DTE (Data Termi nal Equi pment)
database parameters
See Database on l ocal node
DTR
See DECnet Test Sender/DECnet Test Recei ver
uti l i ty (DTS/DTR)
DTRECV (DECnet Test Recei ver i mage), 41
DTS
DTS/DTR uti l i ty
DTSEND (DECnet Test Sender i mage), 41
DTSEND command, 42
Durati on tests, 47, 412
E
Echo tests, 47, 412
End Communi cati ons l ayer events, D4
Enteri ng NCP commands, 12
Event cl ass and type summary, D1 to D13
Event l i sts, 19
Events
Data Li nk l ayer, D9
DNS (Di stri buted Name Servi ce), D12
End Communi cati ons l ayer, D4
Network Management l ayer, D2
OpenVMS speci c, D12
Routi ng l ayer, D4
Sessi on Control l ayer, D4
X.25 Packet l evel , D11
Executor nodes
commands
prex i denti er, 3154
management l i stener (NML), 373
setti ng as the defaul t command poi nt, 373
testi ng, 351
Exi ti ng NCP, 21
External cl ock, 377
Index3
F
FDDI (Fi ber Di stri buted Data I nterface), 381
ECHO DATA, 312, 378
ECHO LENGTH, 312, 378
ECHO TARGET, 313, 378
NI F TARGET, 313, 380
REQUESTED TRT, 313, 381
RESTRI CTED TOKEN TI MEOUT, 313, 381
RI NG PURGER ENABLE, 313, 382
SI F CONFI GURATI ON TARGET, 314, 382
SI F OPERATI ON TARGET, 314, 382
VALI D TRANSMI SSI ON TI ME, 314, 383
H
h-addresses
See Physi cal addresses
Hardware addresses
HELP command, 342
Hel p faci l i ty, 112
Hex password, 19
I
I denti ers
downl i ne l oad, 345, 348
I DP stri ng parameter, 366
I nternal cl ock, 377
I NTERRUPT command, 411
I nterrupt tests, 411
types of, 412
I nvoki ng NCP, 11
K
KMS/KMV DUMP Anal yzer
See PSI KDA
L
Li ne counters summary, B7
Li nes
counters, 3161, B7
devi ces, A1
states, C1 to C4
transi ti ons, C1 to C4
X.25 testi ng, 352
Li ne speeds
setti ng, 46, 411
Li nks
di sconnecti ng, 340
di sconnecti ng l ogi cal from l ocal node, 340
states, C5
LI ST CI RCUI T command, 3120
LI ST EXECUTOR command, 3125
LI ST LI NE command, 3128
LI ST LOGGI NG command, 3133
LI ST MODULE CONFI GURATOR command,
3136
LI ST MODULE X25-ACCESS command, 3139
LI ST MODULE X25-PROTOCOL command,
3141
LI ST MODULE X25-SERVER command, 3145
LI ST MODULE X29-SERVER command, 3145
LI ST NODE command, 3147
LI ST OBJECT command, 3152
LOAD NODE command, 344
LOAD VI A command, 347
Loopback mi rrors
See MI RRORs
LOOP CI RCUI T command, 349
Loop ci rcui t for testi ng, 349
LOOP EXECUTOR command, 351
LOOP LI NE command, 352
LOOP NODE command, 354
Loop nodes, 354
M
MI RRORs (l oopback mi rrors), 354
Mul ti pl e bufferi ng, 41
N
NCP (Network Control Program)
usage summary, 21
NCP commands
conti nui ng, 12
enteri ng, 12
recal l i ng, 12
Network counter summary, B1 to B15
Network management
l ayer events, D2
Networks
ci rcui t devi ces, A1
l i ne devi ces, A1
parameters
See Database on l ocal node
testi ng, 349, 351, 352, 354, 41
Node counters, 3160, 3164, B11
summary, B11
Nodes
address, 48, 411
cl eari ng al l counters, 3160, 3164
name, 48, 411
remote, 48
Nonpri vi l eged DECnet accounts, 48
Index4
O
Object code val ues, 3116
Objects
code val ues, 3115
parameters, 3112, 3113, 3152
OpenVMS systems
events speci c to, D12
Opti onal user data, 44, 48
P
P.S.I . DTEs
See al so X.25 server modul es
states and substates, C5
P.S.I . server modul es
states, C8
p-addresses
Pattern tests, 47, 412
Physi cal addresses, 19, 110
PI PELI NE QUOTA parameter, 369
Pi pel i ne quotas, 369
Pri nti ng
test resul ts, 44, 46, 48, 411
Prompti ng sequence
exampl es, 16 to 17
exi ti ng, 15
Prompt syntax, 14
Protocol modul e counters, B13
Proxi es
parameters, 375
PURGE CI RCUI T command, 32
PURGE EXECUTOR command, 36
PURGE LI NE command, 312
PURGE LOGGI NG command, 316
PURGE LOGGI NG EVENTS command, 317
PURGE LOGGI NG NAME command, 319
PURGE MODULE CONFI GURATOR command,
320
PURGE MODULE X25-ACCESS command, 321
PURGE MODULE X25-PROTOCOL command,
322
PURGE MODULE X25-SERVER command, 325
PURGE MODULE X29-SERVER command, 325
PURGE NODE CI RCUI T command, 331
PURGE NODE command, 327
PURGE OBJECT command, 332
Q
Quotas
pi pel i ne, 369
R
Recal l i ng NCP commands, 12
Routi ng l ayer events, D4
S
Sequence tests, 47, 412
Server modul e counters, 3163, B14
Sessi on Control l ayer events, D4
SET CI RCUI T ALL command, 356
SET CI RCUI T command, 357
SET EXECUTOR ALL command, 363
SET EXECUTOR command, 364
SET EXECUTOR NODE command, 373
SET KNOWN PROXI ES ALL command, 375
SET LI NE ALL command, 376
SET LI NE command, 377
SET LOGGI NG ALL command, 385
SET LOGGI NG EVENTS command, 386
SET LOGGI NG STATE command, 388
SET MODULE CONFI GURATOR command, 390
SET MODULE X25-ACCESS command, 392
SET MODULE X25-PROTOCOL command, 394
SET MODULE X25-SERVER command, 3100
SET MODULE X29-SERVER command, 3100
SET NODE ALL command, 3105
SET NODE CI RCUI T command, 3111
SET NODE command, 3106
SET OBJECT ALL command, 3112
SET OBJECT command, 3113
SHOW AREA command, 3118
SHOW CI RCUI T command, 3120
SHOW EXECUTOR command, 3125
SHOW LI NE command, 3128
SHOW LI NKS command, 3131
SHOW LOGGI NG command, 3133
SHOW MODULE CONFI GURATOR command,
3136
SHOW MODULE X25-ACCESS command, 3139
SHOW MODULE X25-PROTOCOL command,
3141
SHOW MODULE X25-SERVER command, 3145
SHOW MODULE X29-SERVER command, 3145
SHOW NODE command, 3147
SHOW OBJECT command, 3152
Si nk tests, 47, 411, 412
Software transmi ssi ons
l oadi ng downl i ne to target node, 344
l oadi ng downl i ne to target node on speci ed
ci rcui t, 347
Index5
States
substates, C1
transi ti ons, C2
Stati sti cs
pri nti ng, 46, 411
reporti ng, 44, 46, 411
Syntax
for event l i st i denti cati on, 19
of NCP commands, 12
rul es for nami ng NCP components and
parameters, 17 to 111
T
Target nodes
starti ng bootstrap and sel f-l oad program,
3156
through a speci ed ci rcui t, 3158
testi ng, 354
TELL command, 3154
Testi ng
the network, 41
Tests
uti l i ty (DTS/DTR) tests
TRI GGER NODE command, 3156
TRI GGER VI A command, 3158
U
User data
See Opti onal user data
V
VAX P.S.I .
See P.S.I .
W
Wi l dcard characters
usi ng wi th NCP, 13
X
X.25 networks
accessi ng wi th speci ed mul ti host connector,
392
cl eari ng DTE counters, 3162
testi ng l i nes, 352
X.25 packet l evel events, D11
X.25 protocol modul es
counters, 3162, B13
parameters, 322, 394, 3141
X.25 server modul es
See al so P.S.I .
cl eari ng cal l handl er counters, 3163
counters, 3163, B14
X.25 server modul es (contd)
parameters, 325, 3100, 3145
states, C8
X.29 server modul es
See X.25 server modul es
Z
ZERO CI RCUI TS command, 3159
ZERO EXECUTOR command, 3160
ZERO LI NE command, 3161
ZERO MODULE X25-PROTOCOL command,
3162
ZERO MODULE X25-SERVER command, 3163
ZERO MODULE X29-SERVER command, 3163
ZERO NODE command, 3164
Index6

DECnet forOpenVMSNetwork

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DECnet forOpenVMSNetwork

Uploaded by

Copyright:

Available Formats

DECnet for OpenVMSNetwork

You might also like