1 – Alias
Press the CONTINUE button to create the Alias entity on the node you are
managing, or press the CANCEL button to cancel this operation. In either
case, you will be returned to the main window.
1.1 – Port
This window allows the user to create a new Alias Port. Both the Name
field and Node ID fields must be set prior to pressing APPLY or OK.
Name is the full name to be associated with the port, for example,
DEC:.lkg.bulean. The Node ID is the LAN address associated with the
port, for example, AA-00-04-00-45-13.
The selection weight represents the number of sequential incoming connects
to be passed to this member node in the round-robin sequence before
proceeding to the next member node in the sequence. A value of zero means
this node is not eligible to receive incoming connections to this alias
address. Values between 0 and 10 are suggested.
Select the Enable Port radio button if you want this node to become an
active member of the alias you are specifying.
Pressing the OK button will create the specified Alias Port and return
you to the main window. Pressing the APPLY button will create the
specified alias port and leave the current window up. Pressing the RESET
button will reset the values back to what they were when you first
displayed the window. Pressing the CANCEL button will cancel this
operation and return you to the main window.
2 – CSMA-CD
Press the CONTINUE button to create a CSMA-CD entity on the node you are
managing, or press the CANCEL button to cancel this operation. In either
case, you will be returned to the main window.
2.1 – Station
Creates a CSMA-CD Station. The required arguments are:
o Station Name
The name of the CSMA-CD Station you wish to create. For example,
CSMACD-0.
o Communication Port
The system device name assigned to this station. The name must be
in the format ddc, where dd is the device name prefix, and c is the
controller letter. The following are examples of device prefixes.
For example, the Communications Port for the first controller on
an SGEC would be EZA. For the second controller it would be EZB, and
so on.
Device Type Prefix
DEBNA ET
DEBNI ET
DELQA XQ
DELUA XE
DEMNA EX
DEQTA XQ
DESVA ES
DEUNA XE
PMAD EC
SGEC EZ
TGEC TE
Press CONTINUE to create the CSMA-CD Station, or press CANCEL to cancel
this operation. In either case, you will be returned to the main window.
3 – DDCMP
Press the CONTINUE button to create the DDCMP entity on the node you are
managing, or press the CANCEL button to cancel this operation. In either
case, you will be returned to the main window.
3.1 – Link
Creates a DDCMP Link. The Name of the DDCMP Link you wish to create is
a required argument. Select one of the Protocol modes to be used by the
local station by single clicking on the associated radio button:
Point The local station is one end of a point-to-point link.
This is the default and only supported value.
Tributary The local station acts as a tributary of a multipoint
link.
Press CONTINUE to create the DDCMP Link, or press CANCEL to cancel
this operation. In either case, you will be returned to the main window.
3.1.1 – logical_station
Creates a Logical Station for the DDCMP Link you have selected. The
Name of the Logical Station you wish to create is a required argument.
Press CONTINUE to create the Logical Station, or press CANCEL to cancel
this operation. In either case, you will be returned to the main window.
4 – evd
Press the CONTINUE button to create the Event Dispatcher entity on the
node you are managing, or press the CANCEL button to cancel this
operation. In either case, you will be returned to the main window.
4.1 – outbound_stream
Creates an Event Dispatcher Outbound Stream. The Outbound Name is
a required argument. Maximum Buffer Size is an optional argument
that specifies the maximum number of octets to be used for event
processing of this stream. The current value is displayed in the
buffer size status attribute. You can specify a size smaller than the
implementation's default, provided it is still sufficient to hold the
events lost event. It is recommended that you use the default buffer
size.
Press CONTINUE to create the Event Dispatcher Outbound Stream, or press
CANCEL to cancel this operation. In either case, you will be returned
to the main window.
4.2 – Relay
The Event Dispatcher Relay entity processes events from Phase IV DECnet
systems.
Press the CONTINUE button to create an Event Dispatcher Relay entity on
the node you are managing, or press the CANCEL button to cancel this
operation. In either case, you will be returned to the main window.
4.3 – Sink
An Event Dispatcher Sink entity represents a sink. A sink manages
incoming connections and filters incoming events. Each sink maintains
a filter that is applied to all streams that are assigned to that link.
The Sink Name is a required argument specifying a simple name to be
assigned to the sink.
The Maximum Buffer Size is an optional argument that specifies the
maximum number of octets to be used for event processing of this sink.
The current value is displayed in the buffer size status attribute.
You can specify a size smaller than the implementation's default,
provided it is still sufficient to hold the events lost event. If the
value specified in this argument is inadequate for the events lost
event, an insufficient resources exception is returned.
Press the CONTINUE button to create an Event Dispatcher Sink entity on
the node you are managing, or press the CANCEL button to cancel this
operation. In either case, you will be returned to the main window.
5 – FDDI
Press the CONTINUE button to create the FDDI entity on the node you
are managing, or press the CANCEL button to cancel this operation.
In either case, you will be returned to the main window.
5.1 – Station
Creates an FDDI Station. The required arguments are:
o Station Name
The name of the FDDI Station you wish to create. For example,
FDDI-0.
o Communication Port
The system device name assigned to this station. The name must be
in the format ddc, where dd is the device name prefix, and c is the
controller letter. Below are some examples of device prefixes.
For example, the Communications Port for the first controller on
a DEMFA would be FXA.
Device Type Prefix
DEMFA fx
DEFZA fc
Press CONTINUE to create the FDDI Station, or press CANCEL to cancel
this operation. In either case, you will be returned to the main window.
6 – FRAME
Press the CONTINUE button to create the FDDI entity on the node you
are managing, or press the CANCEL button to cancel this operation.
In either case, you will be returned to the main window.
6.1 – Link
Creates a FRAME Link. The name of the FRAME Link, the control mode, and
the protocol are required arguments.
CONTROL MODE
Control mode in which the link operates. This argument determines the
value of the contol mode characteristic. The default is point-to-point.
multipoint master
multipoint tributary
point to point
PROTOCOL
Framing protocol to be used over the link. This argument determines the
value of the procotol characteristic.
bisync hdlc
chips sdlc
ddcmp swift
genbyte
7 – HDLC
Press the CONTINUE button to create the HDLC entity on the node you
are managing, or press the CANCEL button to cancel this operation.
In either case, you will be returned to the main window.
7.1 – Link
Creates an HDLC Link. The Name of the HDLC Link you wish to create is
a required argument.
The profile is an optional argument. It is a latin1 string of
information that can be used when the HDLC protocol is dependent on
network subscription time commitments pertinent to the Data Link layer.
When specified, the values of some link characteristics may be
overridden. This argument determines the value of the profile
characteristic. The default value of this argument is a null string,
meaning that no profile is used.
The Link Type specifies the operational mode of the HDLC link,
determining how the logical station operates. This value is negotiated
with the remote station. This argument determines the value of the link
type characteristic. Select the appropriate radio button:
Balanced The logical station operates in asynchronous response
balanced mode. This is the default value of the
argument.
Primary The logical station is the primary and operates in
normal response mode.
Secondary The logical station is a secondary and operates in
normal response mode.
Press CONTINUE to create the HDLC Link, or press CANCEL to cancel
this operation. In either case, you will return to the main window.
7.1.1 – logical_station
Creates a Logical Station for the HDLC Link you have selected. The
name of the Logical Station you wish to create is a required argument.
Press CONTINUE to create the Logical Station, or press CANCEL to cancel
this operation. In either case, you will be returned to the main window.
8 – Modem
Press the CONTINUE button to create the MODEM entity on the node you
are managing, or press the CANCEL button to cancel this operation.
In either case, you will be returned to the main window.
8.1 – Line
Creates a MODEM Connect Line. The line name, communications mode,
communication port, duplex, and profile are required arguments.
LINE NAME
Name to associate to this line.
COMMUNICATIONS MODE
Communications method used on the link. This argument determines the
value of the communications mode characteristic. The default value is
taken from the device capability. If that is unknown the default is
synchronous.
COMMUNICATION PORT
Name of the communications port to which the communications line is
connected. This argument determines the value of the communications port
characteristic.
DUPLEX
Specifies whether the line is full-duplex or half-duplex. This argument
determines the value of the duplex characteristic.
MODE
The method of startloop used on this line.
Press the CONTINUE button to create the MOP Circuit entity, or press
the CANCEL button to cancel this operation. In either case, you will
return to the main window.
9 – MOP
Pressing the CONTINUE button will create the MOP entity on the node you
are managing.
A NET$MOP process must already be present on the system before you can
successfully create the MOP entity. If a NET$MOP process does not
exist, you can start MOP using the following command:
$ @SYS$SYSTEM:STARTUP NETWORK MOP
The NET$STARTUP_MOP system logical should be defined in
SYS$MANAGER:NET$LOGICALS.COM if you want to automatically start up MOP
when the system reboots. See the SYS$MANAGER:NET$LOGICALS.TEMPLATE
file if your SYS$MANAGER:NET$LOGICALS.COM file does not already exist.
Pressing the CANCEL button will dismiss the window with no action taken.
9.1 – Circuit
Creates a MOP Circuit entity that represents a data link circuit on
which MOP services are available. Both the Circuit Name and the
Circuit Type are required arguments. An example of a Circuit Name
is CSMACD-0. An example of a Circuit Type is CSMA-CD.
Press the CONTINUE button to create the MOP Circuit entity, or press
the CANCEL button to cancel this operation. In either case, you will
return to the main window.
9.2 – Client
Creates a MOP Client entity. A MOP Client entity is a set of default
characteristics used by the MOP functions Dump Server, Load Server, Load
Requester, Loop Requester and Console Requester. When a command or
request for one of these services does not supply all of the required
arguments, the values stored by in the Client entity are used to
perform the operation.
The Client Name argument is a required argument.
Press the CONTINUE button to create the MOP Client entity with its
default values, or press the CANCEL button to cancel this operation.
In either case, you will return to the main window.
10 – nsp
Press the CONTINUE button to create the NSP Transport entity on the
node you are managing, or press the CANCEL button to cancel this
operation. In either case, you will be returned to the main window.
11 – OSAK
Press the CONTINUE button to create the OSAK Transport entity on the
node you are managing, or press the CANCEL button to cancel this
operation. In either case, you will be returned to the main window.
11.1 – application
Creates an OSAK Application. Press the OK button to create the OSAK
Application entity, or press the CANCEL button to cancel this operation.
In either case, you will return to the main window.
11.2 – invocation
Creates an OSAK Application. Press the OK button to create the OSAK
Application Invocation entity, or press the CANCEL button to cancel this
operation. In either case, you will return to the main window.
12 – osi_transport
Press the CONTINUE button to create the OSI Transport entity on the
node you are managing, or press the CANCEL button to cancel this
operation. In either case, you will be returned to the main window.
12.1 – Application
Creates an OSI Transport Application. An OSI Transport Application
entity stores information about an end user that is activated for
receipt of an incoming connection request when the request contains
that end user's name in its Destination Name field.
The following is a required argument:
o Application Name
Simple name to be assigned to the application.
The following arguments are optional:
o Filename
The name of the program to be invoked upon receipt of a connect
request containing a TSEL matching the "Called TSELS" attribute
of the Application entity.
o Username
The user name portion of the access control information that
identifies the account under with the application is to run.
If invalid information or no user name is specified, system
defaults are used to select the user.
Press the OK button to create the OSI Transport Application entity,
or press the CANCEL button to cancel this operation. In either case,
you will return to the main window.
12.2 – Template
An OSI Transport Template entity provides a collection of
characteristics that supply default values for certain parameters that
influence the operation of a port on a transport connection.
One template, with the reserved identifier "default", is automatically
created when the OSI Transport entity is created. This template is
used by default when a user does not specify a template identifier
in a call to establish a connection. The "default" template is also
used to determine the initial values for the attributes of any new
OSI Transport Template entity you create.
The OSI Template Name is a required argument.
Press the CONTINUE button to create the OSI Transport Template entity,
or press the CANCEL button to cancel this operation. In either case,
you will return to the main window.
13 – Routing
Creates the Routing entity.
The required arguments are:
o Protocols
Protocols supported by this router. The value of this argument is
a set containing either or both of the values IP or ISO8473. This
argument determines the value of the protocols characteristic.
The default value of this argument depends on the value of the
type argument.
o Type
Routing type for this node. This argument determines the value
of the type characteristic attribute.
endnode The node is an end system.
L1router The node is a level 1 router.
L2router The node is a level 2 router.
13.1 – Circuit
Creates a Routing Circuit entity that represents a data link to another
node. The Circuit Name is a required argument. Select the Circuit Type
radio button that describes that circuit.
Press the CONTINUE button to create the Routing Circuit entity, or press
the CANCEL button to cancel this operation. In either case, you will
return to the main window.
13.1.1 – Adjacency
Creates a Routing Circuit Adjacency entity for particular circuit you
have selected. A Routing Circuit Adjacency entity describes a
neighboring node that is accessible through a particular circuit.
The required arguments for this display are:
o Name
The simple name to be assigned to the adjacency.
o Endnode IDs
A set of source system IDs. To add new Endnode IDs to this set,
type the Endnode ID in the "End Node IDs to Add" field and push the
ADD button. To remove old Endnode IDs from this set, click on the
Endnode ID you wish to remove so that it becomes highlighted, then
push the REMOVE button. A scroll bar will appear to the right of
the Endnode IDs field whenever it is necessary to allow you to move
through the list of Endnode IDs.
o LAN address
The Data Link address from which the adjacency receives end
system hellos.
The optional argument is:
o Data Format
This string describes the format of the reachable address.
Press the CONTINUE button to create the Routing Circuit Adjacency entity,
or press the CANCEL button to cancel this operation. In either case, you
will return to the main window.
13.1.2 – ip_reachable_address
create [node node-id] routing circuit circuit-name ip reachable
address destination subnet-address
13.1.2.1 – Arguments
o destination subnet-address
Specifies the IP address and subnet mask to which this IP
reachable address corresponds. This argument determines the
value of the destination characteristic. Note that if the subnet
address is for an IP host, this argument also determines the
value of the next hop characteristic.
13.1.3 – reachable_address
create [node node-id] routing circuit circuit-name reachable
address simple-name address prefix address-prefix
13.1.3.1 – Arguments
o address prefix address-prefix
Address prefix to which this reachable address corresponds.
13.1.3.2 – Identifier
o name
Simple name assigned to the reachable address when it is created.
13.2 – egp_group
create [node node-id] routing egp group group-name
o name
Simple name assigned to the EGP group when it is created.
13.2.1 – egp_neighbor
create [node node-id] routing egp group group-name egp neighbor
neighbor-name ip address ip-address
13.2.1.1 – Arguments
o ip address ip-address
The IP address of the EGP neighbor.
13.2.1.2 – Identifier
o name
Simple name assigned to the EGP neighbor when it is created.
13.3 – ptd_neighbor
A Routing Permitted Neighbor entity represents a neighboring node on
a nonbroadcast circuit that is permitted to connect to this node.
The Neighbor Name and the Node ID of the permitted neighbor are
required arguments.
Press the CONTINUE button to create the Routing Permitted Neighbor entity,
or press the CANCEL button to cancel this operation. In either case, you
will return to the main window.
14 – session_control
14.1 – Application
Creates a Session Control Application. A Session Control Application
entity stores information about an end user that is activated for
receipt of an incoming connection request when the request contains
that end user's name in its Destination Name field.
The following is a required argument:
o Application Name
Simple name to be assigned to the application.
The following values will be set to false by default. You can set these
to true by pushing on their associated toggle buttons so that those
buttons are in the "on" state (filled in):
o Incoming Alias
Specifies how a particular application responds to incoming connect
requests directed to the alias node address. The default is to not
allow the application to receive incoming connect requests that
have been directed to the alias node address.
o Incoming Proxy
Specifies whether to honor incoming proxy requests. The default is
to ignore requests to invoke proxies on incoming requests. This
setting on the Session Control Application entity overrides the
setting of the same attribute on the Session Control entity.
o Outgoing Proxy
Specifies the default action to execute when the user does not
explicitly specify whether or not to invoke a proxy. The default
is not to invoke the proxy. This setting on the Session Control
Application entity overrides the setting of the same attribute on
the Session Control entity.
o Outgoing Alias
Specifies whether a particular application uses the alias node
identifier in its outgoing connect requests. The default is not
to use the alias node address in its outgoing connect requests.
o Node Synonym
Specifies the default form in which the remote node name is
passed to the application. The default is to use the fullname.
If this toggle is turned on (i.e., Node Synonym is set to true)
when there is no synonym available, then the fullname is used.
The following arguments are optional:
o Client Name
Identifies the name of the local user that will be activated upon
receipt of a connect request containing a destination name
matching one of the values in the destination names attribute.
o User Name
Identifies the default account under which the application is to
run. If this is null, then the system defaults are used to
select the user.
o Image Name
Filename of a program to be invoked upon receipt of a connection
request containing an address that matches one of the values
contained in the set described by the Addresses characteristic of
the Session Control Application entity.
o Incoming OSI TSEL
The TSEL this image will accept connections for. This is similar
to the destination names attribute. However, applications using
the access point for in-connection matching do not use DNA
Session Control protocol.
The TSEL must be entered as a hex octet, Example: '1234'H
o Network Priority
Press the OK button to create the Session Control Application entity,
or press the CANCEL button to cancel this operation. In either case,
you will return to the main window.
14.2 – transport_service
Creates a Session Control Transport Service entity that stores
information about modules in the Transport layer that support
Session Control.
If the NSP Transport is selected, then the '04'H Protocol ID should
be selected, and the TSEL field is not applicable.
If the OSI Transport is selected, then the '05'H Protocol ID should
be selected, and the TSEL defaults to DEC0, ('DEC0'H). The Transport
selector is used by the OSI Transport Module to bind incoming
connection requests to session control.
Press the OK button to create the Session Control Transport Service
entity, or press the CANCEL button to cancel this operation. In either
case, you will return to the main window.
15 – x25_access
Creates the X.25 Access entity. The Maximum Active Ports argument is
an optional argument.
o Maximum Active Ports
The total number of ports that can be active simultaneously. You can
not modify this characteristic, to set it it must be supplied at create
time.
Press the CONTINUE button to create the X.25 Access entity, or press
the CANCEL button to cancel this operation. In either case, you will
return to the main window.
15.1 – app
Creates a X.25 Access Application entity. The Application Name is a
required argument.
Press the CONTINUE button to create the X.25 Access Application entity,
or press the CANCEL button to cancel this operation. In either case, you
will return to the main window.
15.2 – dte
Creates a X.25 Access DTE Class entity. The Class Name, and Type values
are required arguments. The Profile value is optional.
o Class Name
The name of this new DTE Class
o Profile
The name of the profile that supplies the information to perform X.121
Mapping to or from a simpel DTE address. The profile supplies the default
vaules for the International prefix, Local prefix, DNIC and strip DNIC
o Type
The type of DTE class:
Local - The DTE class consists of local DTEs.
Remote - The DTE class consists of DTEs on a remote gateway system.
Press the CONTINUE button to create the X.25 Access DTE Class entity,
or press the CANCEL button to cancel this operation. In either case, you
will return to the main window.
15.3 – filter
Creates a X.25 Access Filter entity. The Filter Name is a required
argument.
Press the CONTINUE button to create the X.25 Access Filter entity,
or press the CANCEL button to cancel this operation. In either case, you
will return to the main window.
15.4 – reachable
Creates a X.25 Access Reachable Address entity. The Name and Address Prefix
are required arguments.
o Name
The Name of this new Reachable Address Entity
o Address Prefix
The Address Prefix to trigger the use of DTE class and destination.
Press the CONTINUE button to create the X.25 Access Reachable Address
entity, or press the CANCEL button to cancel this operation. In either
case, you will return to the main window.
15.5 – Security
15.5.1 – Flt
15.5.2 – rmt
15.6 – template
16 – x25_client
17 – x25_relay
17.1 – client
17.2 – pvc
18 – x25_server
18.1 – security
18.2 – client
19 – x25_protocol
19.1 – group
19.2 – dte
19.2.1 – pvc