![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
This appendix provides additional examples for some common management tasks.
It includes scripts for the following tasks:
The following NCL script sets up the event dispatcher.
The following example creates the event dispatcher.
ncl> create event dispatcher
The following example creates and enables the default local event sink.
ncl> create event dispatcher sink local_sink ncl> enable event dispatcher sink local_sink
The following example creates and enables the default local outbound stream.
ncl> create event dispatcher outbound stream local_stream ncl> enable event dispatcher outbound stream local_stream
The following example creates and enables an additional sink on the local node. Note that sales_sink_device is a logical name that corresponds to printer lpa0:. The logical name was defined with a standard DCL define/system command.
ncl> create event dispatcher sink sales_sink ncl> set event dispatcher sink sales_sink end user = number = 200 ncl> set event dispatcher sink sales_sink client type = device ncl> set event dispatcher sink sales_sink device - _ncl> name = "sales_sink_device" ncl> enable event dispatcher sink sales_sink
The following example creates an outbound stream to node usa.sales.admin by means of the end-user name, admin_sink.
ncl> create event dispatcher outbound stream admin_obs ncl> set event dispatcher outbound stream admin_obs sink node - _ncl> usa.sales.admin ncl> set event dispatcher outbound stream admin_obs sink end user - _ncl> = name = admin_sink ncl> enable event dispatcher outbound stream admin_obs
The following example creates a sink corresponding to the outbound stream admin_obs on node usa.sales.admin. Note that the end-user name of both the sink and the outbound stream must correspond.
ncl> create event dispatcher sink admin_sink ncl> set event dispatcher sink admin_sink end user - _ncl> = name = admin_sink ncl> enable event dispatcher sink admin_sink
The following example creates an outbound stream to a node identified by the DECdns object name, usa.sales.finance_sink.
ncl> create event dispatcher outbound stream finance_obs ncl> set event dispatcher outbound stream finance_obs sink object - _ncl> usa.sales.finance_sink ncl> enable event dispatcher outbound stream finance_obs
The following example creates an outbound stream to a node by means of an address. The example first creates an outbound stream on route66.
ncl> create node route66 event dispatcher outbound stream sales_obs
ncl> set node route66 event dispatcher outbound stream sales_obs -
_ncl> sink address -
_ncl> { -
_ncl> ( -
_ncl> [DNA_CMIP-MICE], -
_ncl> [DNA_sessioncontrolV3, number = 82], -
_ncl> [DNA_nsp], -
_ncl> [DNA_osinetwork, 49::00-13:aa-00-04-00-8a-4f:20 (dec:.zk0.ilium)] -
_ncl> ) -
_ncl> }
ncl> enable node route66 event dispatcher outbound stream sales_obs
The following example enables the event dispatcher.
ncl> enable event dispatcher
The following NCL script creates and sets up several applications.
ncl> create session control application fal
ncl> set session control application fal addresses = {number=17}, -
_ncl> client, -
_ncl> incoming alias true, -
_ncl> incoming proxy true, -
_ncl> outgoing alias true, -
_ncl> outgoing proxy true, -
_ncl> node synonym true, -
_ncl> image name sys$system:fal.exe, -
_ncl> incoming osi tsel
ncl> create session control application mail
ncl> set session control application mail addresses {number=27} -
_ncl> client, -
_ncl> incoming alias true, -
_ncl> incoming proxy true, -
_ncl> outgoing alias true, -
_ncl> outgoing proxy true, -
_ncl> node synonym true, -
_ncl> image name sys$system:mail_server.exe, -
_ncl> user name "mail$server", -
_ncl> incoming osi tsel
ncl> create node 0 session control application task
ncl> set node 0 session control application task addresses {name=task} -
_ncl> client, -
_ncl> incoming alias true, -
_ncl> incoming proxy true, -
_ncl> outgoing alias true, -
_ncl> outgoing proxy true, -
_ncl> node synonym true, -
_ncl> incoming osi tsel
The NCL script example creates and sets up nsp.
ncl> create nsp ncl> set nsp maximum window 8 ncl> set nsp maximum transport connections 200 ncl> set nsp maximum receive buffers 2000 ncl> enable nsp ncl> create session control transport service nsp protocol %x04
The following NCL script creates and sets up OSI Transport, including connection-oriented (CONS) and connectionless (CLNS) services.
ncl> create osi transport
ncl> set osi transport cons filters {}
ncl> create osi transport application osit_ivp
ncl> set osi transport application osit_ivp -
_ncl> image name sys$test:osit$ivpresp.com, -
_ncl> user name "systest", -
_ncl> called tsels {%x564F5453495650}
ncl> create osi transport template osi_loop_clns
ncl> set osi transport template osi_loop_clns -
_ncl> network service clns, -
_ncl> classes {4}, -
_ncl> cons template "", -
_ncl> expedited data true, -
_ncl> checksums false, -
_ncl> inbound false, -
_ncl> loopback true
ncl> create osi transport template osi_loop_cons
ncl> set osi transport template osi_loop_cons -
_ncl> network service cons, -
_ncl> classes {4,2,0}, -
_ncl> cons template "", -
_ncl> expedited data true, -
_ncl> checksums false, -
_ncl> inbound false, -
_ncl> loopback true
ncl> enable osi transport
The following NCL script shows the commands you need to set up a routing initialization password.
ncl> create routing type endnode ncl> enable routing ncl> create routing circuit hdlc-0 - _ncl> type hdlc ncl> set routing circuit hdlc-0 - _ncl> transmit verifier %x2222222 - _ncl> explicit receive verification false - _ncl> receive verifier %x5555555 ncl> enable routing circuit hdlc-0 ncl> create routing permitted neighbor - _ncl> boston id 08-00-2b-12-34-56 ncl> set routing permitted neighbor - _ncl> boston verifier %x5555555
The following NCL script sets up MOP on a VAXstation 3100 with an integral Ethernet adapter. This example assumes that the entity csma station sva-0 has already been created and enabled. For the example, the mop circuit name is identical to the csma station name, but this is not necessary. The circuit is enabled for downline loading (load server), upline dumping (dump server), and for the use of the load and boot directives (console requester).
ncl> create mop
ncl> enable mop
ncl> create mop circuit sva-0 type csma
ncl> set mop circuit sva-0 link name csma station sva-0
ncl> enable mop circuit sva-0 function {load server, dump server, -
_ncl> console requester}
The following NCL commands configure an OpenVMS Cluster satellite client. Only the system image file specification characteristic is needed, and this is given in the special quoted form for an OpenVMS Cluster load. The characteristics phase iv client name, phase iv client address, phase iv host name, and phase iv host address are not required, but they are used to display information in the OpenVMS Cluster satellite banner when the downline load of the system image completes.
ncl> create mop client mopsy
ncl> set mop client mopsy -
_ncl> circuit sva-0, -
_ncl> system image {"@net$niscs_laa(sys$sysdevice:<sys10.>)"}, -
_ncl> address {08-00-2b-0d-b9-81}, -
_ncl> phase iv client name valis, -
_ncl> phase iv client address 4.620, -
_ncl> phase iv host name mu, -
_ncl> phase iv host address 4.260
The following NCL commands configure a DECnet/SNA Gateway-CT client node. The gateway runs DECnet Phase IV software, so the Phase IV client characteristics are needed. Also, the example uses two Ethernet addresses: the hardware address, and the Phase IV extended DECnet address.
ncl> create mop client valis
_ncl> set mop client valis -
_ncl> circuit sva-0, -
_ncl> phase iv client name valis, -
_ncl> phase iv client address 4.620, -
_ncl> phase iv host name mu, -
_ncl> phase iv host address 4.260, -
_ncl> system image {sys$common:<sna$csv>snacsa021.sys}, -
_ncl> diagnostic image {mop$load:snacsa$desnx.sys}, -
_ncl> dump file {sys$common:<sna$csv>valis.dmp}, -
_ncl> address {08-00-2b-0f-9e-ca, aa-00-04-00-6c-12}
The console carrier provides access to the remote console subsystem (ASCII console) of a network server on a LAN. The console carrier interface does not use NCL. Instead, you enter commands at the operating system to use the console carrier.
To use the console carrier, specify the console requester function when you enable the mop circuit (discussed in Section 10.2.). The console carrier user interface does not use NCL. Instead, DECnet-Plus uses the DCL command, set host/mop, to run the console carrier requester program.
In addition, the target system must support remote console access. See your network server documentation for information about remote console access support.
The following command examples show how to invoke the set host/mop command:
$ set host/mop client-name - _$ /disconnect = disconnect-character - (1) _$ /break = break-character (2)
Alternatively, you can use the following format to access a client system that is not defined in the client database. For example:
$ set host/mop - _$ /circuit = circuit-name - (1) _$ /address = lan-address - (2) _$ /verification = octet-string - (3) _$ /disconnect = disconnect-character - _$ /break = break-character
The console prompt for the network server to which you have connected appears on your terminal. For example:
>>>
At the server prompt, you can enter commands appropriate to your server. For information about what commands your network server supports, see your server documentation.
For example:
$ set host/mop slug /address=aa-00-04-00-33-30
Connection established to remote system AA-00-04-00-33-30 Press Ctrl/\ to disconnect, Ctrl/] to send break DEMSA Console ROM Firmware Version: 8-AUG-1995 16:08 Processor State: *RUNNING* Software state : Running >>>
Note
OpenVMS Cluster satellites do not provide remote console support.
This appendix describes the correspondence between DECnet Phase IV (NCP) and DECnet Phase V (NCL) network management commands for network managers who use VAX P.S.I. (X.25) in their networks.
The material is organized from the Phase IV network manager's viewpoint. Each section describes the changes made in a specific area of Phase IV network management to support DECnet Phase V. For more information about DECnet Phase V network management, refer to the DECnet-Plus Network Control Language Reference.
For X.25 network managers, the major Phase IV manageable structures are:
In DECnet Phase V, network management operates on manageable entities. These entities are organized in a hierarchical structure. The topmost entity in this structure is the node entity. Below this entity is a series of modules, each of which provides a particular network service. The following DECnet Phase V modules are used by X.25:
The X25 Access module provides management directives for creating and deleting the entity and starting and stopping its operation.
The x25 access entity has the following subordinate entities:
You can create X25 Access filters with the VAX P.S.I. configuration procedure. Use the Declaring a Network Process Section, as follows:
Do you want X.25 or X.29 programs to specify filter names in $QIO(IO$_ACPCONTROL) calls?
Do you want IO$_ACPCONTROL calls issued by your programs to name any dynamic filters?
Do you want IO$_ACPCONTROL calls issued by your programs to name any dynamic filters?
Do you want IO$_ACPCONTROL calls issued by your programs to name any static filters?
Note
On OpenVMS Alpha systems, the entities needed for OSI transport over X.25 are created automatically by the configuration utility.
The X25 Client module provides management directives for creating and deleting the entity and starting and stopping its operation.
The x25 client entity has no subordinate entities.
The X25 Server module provides management directives for creating and deleting the entity and starting (or restarting) its operation.
The x25 server entity has the following subordinate entities:
The X25 Protocol module provides management directives for creating and deleting the entity. Because it is essentially a collection of dte entities, it does not provide directives for starting and stopping the module as a whole.
The x25 protocol entity has the following subordinate entities:
The LAPB module provides management directives for creating and deleting the entity.
The lapb entity has the following subordinate entities:
The LLC2 module provides management directives for creating and deleting the entity.
The llc2 entity has the following subordinate entities :
The Modem Connect module provides management directives for creating and deleting the entity.
The modem connect entity has the following subordinate entities:
The following sections show the association between Phase IV network management parameters and their equivalent DECnet Phase V attributes.
Each section contains a table listing the parameters that could be set by Phase IV network management. The columns in the table denote the following:
The footnotes describe additional points to consider when converting from DECnet Phase IV to DECnet Phase V network management.
The X25-ACCESS NETWORK database points to the X.25 protocol networks on remote connector systems. It also contains session control access control information. Table H-1 shows the parameter mapping rules.
| Phase IV Name | Phase IV Entity | Attribute | Type |
|---|---|---|---|
| NETWORK | x25 access dte class ¹ | Identifier | Simple name |
| NODE | x25 access dte class | node | DNS full name |
| USER + | x25 access dte class | user ² | Latin1String |
| PASSWORD + | x25 access dte class | password ² | Latin1String |
| ACCOUNT + | x25 access dte class | account ² | Latin1String |
For example:
NCP> set x25-access network MYNET node GWYNOD
ncl> create x25 access dte class MYNET type remote ncl> set x25 access dte class MYNET node LOCAL:.GWYNOD
The X25-PROTOCOL NETWORK database defines the base operating characteristics (including default values) for a collection of DTEs and their associated lines. The same profile can be used by more than one network name. Table H-2 shows the parameter mapping rules.
| Phase IV Name | Phase V Entity | Attribute | Type |
|---|---|---|---|
| NETWORK | x25 access dte class ¹ | Identifier | Simple Name |
| PROFILE | x25 protocol dte | profile ² | Latin1String |
| lapb link | profile ² | Latin1String |
The X25-PROTOCOL DTE database contains the operating characteristics of each connection to the PSDN at X.25 level 3 (packet level). Default values are taken mostly from the profile; customers can modify these values so that their system configurations match their PSDN subscription options. Table H-3 shows the parameter mapping rules.
| Phase IV Name | Phase V Entity | Attribute | Type |
|---|---|---|---|
| DTE | x25 protocol dte | x25 address | DTE address |
| NETWORK | x25 access dte class | Identifier | Simple name |
| x25 protocol dte | inbound dte class ¹ | Simple name | |
| x25 protocol dte | profile | Latin1String | |
| LINE | x25 protocol dte | link service provider ² | Local entity name |
| CALL TIMER + | x25 protocol dte | call timer | Unsigned |
| CHANNELS + | x25 protocol dte | outgoing list | Set of range of unsigned |
| CLEAR TIMER + | x25 protocol dte | clear timer | Unsigned |
| COUNTER TIMER + | N/A | ||
| DEFAULT DATA + | x25 protocol dte | default packet size | Unsigned |
| DEFAULT WINDOW + | x25 protocol dte | default window size | Unsigned |
| INTERFACE + | x25 protocol dte | interface type | Enumerated {[DTE], DCE, negotiated} |
| INTERRUPT TIMER + | x25 protocol dte | interrupt timer | Unsigned |
| MAXIMUM CIRCUITS + | x25 protocol dte | maximum active circuits | Unsigned |
| MAXIMUM CLEARS + | x25 protocol dte | maximum clear attempts | Unsigned |
| MAXIMUM DATA + | x25 protocol dte | maximum packet size | Unsigned |
| MAXIMUM RESETS + | x25 protocol dte | maximum reset attempts | Unsigned |
| MAXIMUM RESTARTS + | x25 protocol dte | maximum restart attempts | Unsigned |
| MAXIMUM WINDOW + | x25 protocol dte | maximum window size | Unsigned |
| RESET TIMER + | x25 protocol dte | reset timer | Unsigned |
| RESTART TIMER + | x25 protocol dte | restart timer | Unsigned |
| STATE + | x25 protocol dte | N/A ³ |
PROFILE_VMS_025.HTML OSSG Documentation 2-DEC-1996 12:35:28.84
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.