1 – Boot
1.1 – MOP
1.1.1 – Circuit
Causes the system you are managing to send a boot message to an
adjacent system so the adjacent system will load itself. (The Phase V
NCL BOOT MOP CIRCUIT command is roughly equivalent to the Phase IV
NCP TRIGGER VIA command.)
If you chose optionally to enter a Client name in the previous menu, the
default boot parameters for this operation are obtained by looking up the
information for that MOP Client, and the parameters present in the current
display.
The required arguments for this boot operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit you have currently selected for the boot operation.
The optional arguments for this boot operation are:
o Client
A client entity to be used for this operation, if you provided one
in the previous display.
o Device
Provides some information required by the target system for the
boot operation.
o Script ID
Script file required by the target system for boot.
o Software ID
System image required by the target system for boot.
o Verification
A hex string that must match a verification code at the receiving
system in order to trigger the bootstrap mechanism so that the
downline load can be performed. The default is '0000000000000000'H,
or %x00-00-00-00-00-00-00-00.
Pressing the OK button will cause the boot command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No boot
command will be issued.
1.1.2 – Client
Causes the system you are managing to send a boot message to an
adjacent system so that the adjacent system will load itself. (The
Phase V NCL BOOT MOP CLIENT command is roughly equivalent to the
Phase IV NCP TRIGGER NODE command).
The required arguments for this boot operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit over which the boot operation is to occur.
The optional arguments for this boot operation are:
o Device
Provides some information required by the target system for the
boot operation.
o Script ID
Script file required by the target system for boot.
o Software ID
System image required by the target system for boot.
o Verification
A hex string that must match a verification code at the receiving
system in order to trigger the bootstrap mechanism so that the
downline load can be performed. The default is '0000000000000000'H,
or %x00-00-00-00-00-00-00-00.
Pressing the OK button will cause the boot command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No boot
command will be issued.
2 – Connect
2.1 – evd
2.1.1 – outbound_stream
Pushing the CONTINUE button causes the outbound stream entity to request
a connection to its sink partner. This directive causes the entity to issue
a single session connect request to its sink partner, unless the state is
already OnConnected, in which case the directive has no effect and returns
the success response.
Pushing the CANCEL button will cancel the operation.
In either case, you will be returned to the main window.
3 – Create
3.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.
3.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.
3.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.
3.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.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.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.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.13.1.2 – ip_reachable_address
create [node node-id] routing circuit circuit-name ip reachable
address destination subnet-address
3.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.
3.13.1.3 – reachable_address
create [node node-id] routing circuit circuit-name reachable
address simple-name address prefix address-prefix
3.13.1.3.1 – Arguments
o address prefix address-prefix
Address prefix to which this reachable address corresponds.
3.13.1.3.2 – Identifier
o name
Simple name assigned to the reachable address when it is created.
3.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.
3.13.2.1 – egp_neighbor
create [node node-id] routing egp group group-name egp neighbor
neighbor-name ip address ip-address
3.13.2.1.1 – Arguments
o ip address ip-address
The IP address of the EGP neighbor.
3.13.2.1.2 – Identifier
o name
Simple name assigned to the EGP neighbor when it is created.
3.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.
3.14 – session_control
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.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.
3.15.5 – Security
3.15.5.1 – Flt
3.15.5.2 – rmt
3.15.6 – template
3.16 – x25_client
3.17 – x25_relay
3.17.1 – client
3.17.2 – pvc
3.18 – x25_server
3.18.1 – security
3.18.2 – client
3.19 – x25_protocol
3.19.1 – group
3.19.2 – dte
3.19.2.1 – pvc
4 – Delete
4.1 – Alias
Pushing the CONTINUE button will delete the Alias entity and return you
to the main window. Any existing Alias Ports must be disabled and
deleted before the Alias entity can be successfully deleted.
Pushing the CANCEL button will dismiss the window with no action taken.
4.1.1 – Port
Pushing the CONTINUE button will cause the specified Alias Port to be
deleted from the system. The Alias Port must be disabled before it can
be successfully deleted.
Pushing the CANCEL button will dismiss the window with no action taken.
4.2 – CSMA-CD
Pushing the CONTINUE button will cause the CSMA-CD entity to be deleted.
Any existing CSMA-CD Stations must be disabled and deleted before you can
successfully delete the CSMA-CD entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.2.1 – Station
Pushing the CONTINUE button will cause the CSMA-CD Station entity to be
deleted. The CSMA-CD Station must be disabled and all ports associated
with this station must have gone away before you can successfully delete
this CSMA-CD Station entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.3 – DDCMP
Pushing the CONTINUE button will cause the DDCMP entity to be deleted.
Any existing DDCMP Link entities must have been disabled and deleted
before this DDCMP entity can be successfully removed.
Pushing the CANCEL button will dismiss the window with no action taken.
4.3.1 – Link
Pushing the CONTINUE button will cause the DDCMP Link entity to be
deleted. This DDCMP Link must be disabled, all of its Logical Stations
must be disabled and deleted, and all ports associated with this link
must have gone away before you can successfully delete this DDCMP Link
entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.3.1.1 – LOGICAL_STATION
Pushing the CONTINUE button will cause this DDCMP Link Logical Station
entity to be deleted. This DDCMP Link Logical Station must be disabled
before you can successfully delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.4 – evd
4.4.1 – outbound_stream
Pushing the CONTINUE button will cause the specified Event Dispatcher
Outbound Stream to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.4.2 – Relay
Pushing the CONTINUE button will cause the specified Event Dispatcher
Relay to be deleted.
Pushing the CANCEL button will dismiss the window with no action taken.
4.4.3 – Sink
Pushing the CONTINUE button will cause the specified Event Dispatcher
Sink to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.5 – FDDI
Pushing the CONTINUE button will cause the FDDI entity to be deleted.
Any existing FDDI Stations must be disabled and deleted before you can
successfully delete the FDDI entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.5.1 – Station
Pushing the CONTINUE button will cause the FDDI Station entity to be
deleted. The FDDI Station must be disabled and all ports associated
with this station must have gone away before you can successfully delete
this FDDI Station entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.6 – FRAME
Pushing the CONTINUE button will cause the FRAME entity to be deleted.
Any existing FRAME links must be disabled and deleted before you can
successfully delete the FRAME entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.6.1 – LINK
Pushing the CONTINUE button will cause the FRAME Link entity to be
deleted. The FRAME Link must be disabled and all ports associated
with this Link must have gone away before you can successfully delete
this FRAME Link entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.7 – HDLC
Pushing the CONTINUE button will cause the HDLC entity to be deleted.
Any existing HDLC Link entities must have been disabled and deleted
before this HDLC entity can be successfully deleted.
Pushing the CANCEL button will dismiss the window with no action taken.
4.7.1 – Link
Pushing the CONTINUE button will cause the HDLC Link entity to be
deleted. This HDLC Link must be disabled, all of its Logical Stations
must be disabled and deleted, and all ports associated with this link
must have gone away before you can successfully delete this HDLC Link
entity.
Pushing the CANCEL button will dismiss the window with no action taken.
4.7.1.1 – LOGICAL_STATION
Pushing the CONTINUE button will cause this HDLC Link Logical Station
entity to be deleted. This HDLC Link Logical Station must be disabled
before you can successfully delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.8 – MODEM
Pushing the CONTINUE button will cause the MODEM Connect entity to be
deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.8.1 – Line
Pushing the CONTINUE button will cause the MODEM Connect Line entity to be
deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.9 – MOP
Pushing the CONTINUE button will cause the specified MOP Circuit to be
deleted from the system. All MOP Clients must have been deleted, all
MOP Circuits must have been disabled and deleted, and the MOP entity
itself must be disabled before you can successfully delete MOP.
Pushing the CANCEL button will dismiss the window with no action taken.
4.9.1 – Circuit
Pushing the CONTINUE button will cause the specified MOP Circuit to be
deleted from the system. This MOP Circuit must be disabled before you
can successfully delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.9.2 – Client
Pushing the CONTINUE button will cause the specified MOP Client to be
deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.10 – NSP
Pushing the CONTINUE button will cause the NSP Transport to be deleted
from the system. NSP must be disabled before you can successfully delete
it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.11 – osi_transport
Pushing the CONTINUE button will cause the OSI Transport to be deleted
from the system. OSI must be disabled before you can successfully delete
it.
The delete command disconnects the connection if the port direction is
either incoming or outgoing, and deletes the port. A local transport
disconnection event will also be generated.
The port that represents the session control listener (local transport
selector 'DEC0'H) is a special case and cannot be deleted. An error is
not returned if an attempt is made to delete the session control listener.
Pushing the CANCEL button will dismiss the window with no action taken.
4.11.1 – Application
Pushing the CONTINUE button will cause the selected OSI Transport
Application entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.11.2 – Port
Pushing the CONTINUE button will cause the specified OSI Transport Port
to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.11.3 – Template
Pushing the CONTINUE button will cause the specified OSI Transport
Template to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12 – Routing
Pushing the CONTINUE button will cause the Routing entity to be deleted
from the system. All Routing Circuit entities must have been disabled
and deleted and the Routing entity itself must be disabled before you can
successfully delete Routing.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.1 – Circuit
Pushing the CONTINUE button will cause the specified Routing Circuit to
be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.1.1 – Adjacency
Pushing the CONTINUE button will cause the specified Routing Circuit
Adjacency entity to be deleted from the system. You cannot delete an
automatic adjacency, or an adjacency on a circuit that is not a
dynamically assigned X.25 circuit.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.1.2 – ip_address_translation
Pushing the CONTINUE button will cause the specified Routing Circuit IP
Address Translation to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.1.3 – ip_reachable_address
Pushing the CONTINUE button will cause the specified Routing Circuit IP
Reachable Address to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.1.4 – reachable_address
Pushing the CONTINUE button will cause the specified Routing Circuit
Reachable Address to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.2 – egp_group
Pushing the CONTINUE button will cause the specified Routing EGP Group
to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.2.1 – egp_neighbor
Pushing the CONTINUE button will cause the specified Routing EGP Group
EGP Neighbor to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.12.3 – permitted_neighbor
Pushing the CONTINUE button will cause the specified Routing Permitted
Neighbor to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.13 – session
4.13.1 – control
4.13.1.1 – Application
Pushing the CONTINUE button will cause the specified Session Control
Application to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.13.1.2 – backtranslation_softlink
Pushing the CONTINUE button will cause the specified Session Control
Backtranslation Softlink to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.13.1.3 – Port
Pushing the CONTINUE button will cause the specified Session Control
Port to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.13.1.4 – tower_maintenance
Pushing the CONTINUE button will cause the specified Session Control
Tower Maintenance entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.13.1.5 – transport_service
Pushing the CONTINUE button will cause the specified Session Control
Transport Service to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14 – x25_access
Pushing the CONTINUE button will cause the X.25 Access entity to be deleted
from the system. X.25 Access must be disabled before you can delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.1 – dte
Pushing the CONTINUE button will cause the specified X.25 Access DTE Class
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.2 – filter
Pushing the CONTINUE button will cause the specified X.25 Access Filter
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.3 – reachable
Pushing the CONTINUE button will cause the specified X.25 Access Reachable
Address entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.4 – template
Pushing the CONTINUE button will cause the specified X.25 Access Template
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.5 – Security
Pushing the CONTINUE button will cause the specified X.25 Access Security
DTE entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.6 – app
Pushing the CONTINUE button will cause the specified X.25 Access Application
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.6.1 – rmt
Pushing the CONTINUE button will cause the specified X.25 Access Security
DTE Remote DTE to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.14.7 – security Flt
Pushing the CONTINUE button will cause the specified X.25 Access Security
Filter entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.15 – x25_client
Pushing the CONTINUE button will cause the X.25 Client entity to be deleted
from the system. X.25 Client must be disabled before you can delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.16 – x25_relay
Pushing the CONTINUE button will cause the X.25 Relay entity to be deleted
from the system. X.25 Relay must be disabled before you can delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.16.1 – client
Pushing the CONTINUE button will cause the specified X.25 Relay Client
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.16.2 – pvc
Pushing the CONTINUE button will cause the specified X.25 Relay PVC entity
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.17 – x25_server
Pushing the CONTINUE button will cause the X.25 Server entity to be
deleted from the system. X.25 Server entity must be disabled before you
can delete it.
Pushing the CANCEL button will dismiss the window with no action taken.
4.17.1 – security
Pushing the CONTINUE button will cause the specified X.25 Server Security
DTE entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.17.2 – client
Pushing the CONTINUE button will cause the specified X.25 Server Client
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.18 – x25_protocol
Pushing the CONTINUE button will cause the X.25 Protocol entity to be
deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.18.1 – group
Pushing the CONTINUE button will cause the specified X.25 Protocol Group
Filter entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.18.2 – dte
Pushing the CONTINUE button will cause the specified X.25 Protocol DTE
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
4.18.2.1 – pvc
Pushing the CONTINUE button will cause the specified X.25 Protocol DTE PVC
entity to be deleted from the system.
Pushing the CANCEL button will dismiss the window with no action taken.
5 – Disable
5.1 – ALIAS
5.1.1 – Port
Pushing the CONTINUE button will cause the specified Alias Port to be
placed in the disabled state.
Pushing the CANCEL button will dismiss the window with no action taken.
5.2 – CSMA-CD
5.2.1 – Station
Pushing the CONTINUE button will cause the specified CSMA-CD Station
to be placed in the disabled state.
Pushing the CANCEL button will dismiss the window with no action taken.
5.3 – DDCMP
5.3.1 – Link
Pushing the CONTINUE button will cause the specified DDCMP Link to be
placed in the disabled state.
Pushing the CANCEL button will dismiss the window with no action taken.
5.3.1.1 – logical_station
Pushing the CONTINUE button will cause the specified DDCMP Link Logical
Station to be placed in the disabled state.
Pushing the CANCEL button will dismiss the window with no action taken.
5.4 – evd
Pushing the CONTINUE button will cause the Event Dispatcher to be set
to the disabled state.
Pushing the CANCEL button will dismiss the window with no action taken.
5.4.1 – outbound_stream
Pushing the CONTINUE button will cause the specified Event Dispatcher
Outbound Stream to be set to the disabled state.
Pushing the CANCEL button will dismiss the window with no action taken.
5.4.2 – Relay
Pushing the CONTINUE button will cause the Event Dispatcher Relay to be
disabled. All three Event Relay Logging entities (Console, File and
Monitor) will be automatically deleted. This will discontinue all
logging of DECnet Phase IV events to the DECnet-Plus system.
Pushing the CANCEL button will dismiss the window with no action taken.
5.4.2.1 – Logging
Pushing the CONTINUE button will cause the specified Event Dispatcher
Relay Logging entity, either Console, Monitor, or File, to be disabled.
Disabling the Console logging will prevent Phase IV events from being
logged to the operator console (OPA0).
Disabling the Monitor logging will prevent Phase IV events from being
logged to the Operator Communication Facility (OPCOM).
Disabling the File logging will prevent Phase IV events from being
recorded in binary format.
Pushing the CANCEL button will dismiss the window with no action taken.
5.4.3 – Sink
Pushing the CONTINUE button will cause the specified Event Dispatcher
Sink entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.5 – FDDI
5.5.1 – Station
Pushing the CONTINUE button will cause the specified FDDI Station
entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.6 – FRAME
Pushing the CONTINUE button will cause the FRAME entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.6.1 – Link
Pushing the CONTINUE button will cause the specified FRAME Link entity
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.7 – HDLC
5.7.1 – Link
Pushing the CONTINUE button will cause the specified HDLC Link entity
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.7.1.1 – logical_station
Pushing the CONTINUE button will cause the specified HDLC Link Logical
Station entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.8 – MOP
Pushing the CONTINUE button will cause the MOP entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.9 – Modem
5.9.1 – line
Pushing the CONTINUE button will cause the MODEM Connect Line entity to be
disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.9.2 – Circuit
Pushing the CONTINUE button will cause the specified MOP Circuit
entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.10 – NSP
Pushing the CONTINUE button will cause the NSP entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.11 – osak
Pushing the CONTINUE button will cause the specified OSAK entity to be
disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.12 – osi_transport
Pushing the CONTINUE button will cause the OSI Transport entity to be
disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.13 – Routing
Pushing the CONTINUE button will cause the Routing entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.13.1 – Circuit
Pushing the CONTINUE button will cause the selected Routing Circuit
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.13.1.1 – ip_reachable_address
Pushing the CONTINUE button will cause the selected Routing Circuit IP
Reachable Address to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.13.1.2 – reachable_address
Pushing the CONTINUE button will cause the selected Routing Circuit
Reachable Address to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.13.2 – egp_group
Pushing the CONTINUE button will cause the selected Routing EGP Group
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.13.2.1 – group_egp_neighbor
Pushing the CONTINUE button will cause the selected Routing EGP Group
EGP Neighbor to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.14 – x25_access
Pushing the CONTINUE button will cause the X.25 Access entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.14.1 – app
Pushing the CONTINUE button will cause the selected X.25 Access Application
entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.15 – x25_client
Pushing the CONTINUE button will cause the X.25 Client entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.16 – x25_relay
5.16.1 – client
Pushing the CONTINUE button will cause the selected X.25 Relay Client entity
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.16.2 – pvc
Pushing the CONTINUE button will cause the selected X.25 Relay PVC entity
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.17 – x25_server
Pushing the CONTINUE button will cause the X.25 Server entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.17.1 – client
Pushing the CONTINUE button will cause the selected X.25 Server Client
entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.18 – x25_protocol
5.18.1 – dte
Pushing the CONTINUE button will cause the selected X.25 Protocol DTE entity
to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
5.18.1.1 – pvc
Pushing the CONTINUE button will cause the selected X.25 Protocol DTE PVC
entity to be disabled.
Pushing the CANCEL button will dismiss the window with no action taken.
6 – Disconnect
6.1 – evd
6.1.1 – outbound_stream
Pushing the CONTINUE button will cause the disconnection of the
specified outbound stream from its sink partner. This will abort the
entity's specified outbound stream connection to the sink.
Pushing the CANCEL button will dismiss the window with no action taken.
6.1.2 – Sink
6.1.2.1 – inbound_stream
Pushing the CONTINUE button will disconnect the entity's specified
stream connection. It disconnects the entity's stream connection
immediately. Event reports in transit are lost, and the sink cannot
perform an orderly shutdown on the stream.
Pushing the CANCEL button will dismiss the window with no action taken.
7 – Echo
7.1 – FDDI
7.1.1 – Station
7.1.1.1 – Link
Causes the link subentity to transmit an SMT Echo request
frame and await the response. If a response is received, it is
displayed.
echo [node node-id] fddi station station-name link link-id
target lan address timeout integer-16 data octet-string
7.1.1.1.1 – Arguments
o data
Data to transmit in echo request.
o target
48-bit LAN address of the target.
o timeout
Value: 1-65535
Timeout, in seconds, optional.
8 – Enable
8.1 – Alias
8.1.1 – Port
Pushing the CONTINUE button will cause the specified Alias Port to be
enabled. When the Alias Port entity is enabled, the node becomes an
active member of the VMScluster alias it specifies.
Pushing the CANCEL button will dismiss the window with no action taken.
8.2 – CSMA-CD
8.2.1 – Station
Enables the specified CSMA-CD Station entity. The MAC Address represents
an individual medium access control address for the station. Pushing the
CONTINUE button will cause the specified CSMA-CD Station to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.3 – DDCMP
8.3.1 – Link
Pushing the CONTINUE button will cause the specified DDCMP Link to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.3.1.1 – logical_station
Pushing the CONTINUE button will cause the specified DDCMP Link Logical
Station entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.4 – event_dispatcher
Pushing the CONTINUE button will cause the Event Dispatcher to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.4.1 – outbound_stream
Pushing the CONTINUE button will cause the specified Event Dispatcher
Outbound Stream to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.4.2 – relay
Pushing the CONTINUE button will cause the Event Dispatcher Relay to be
enabled so that events from DECnet Phase IV systems will be processed
and posted into the DECnet-Plus logging system.
Enabling the Event Dispatcher Relay will automatically create and
enable the three Event Dispatcher Relay Logging entities (Console,
File and Monitor). If you wish, each of these logging entities can
be disabled and reenabled individually.
Pushing the CANCEL button will dismiss the window with no action taken.
8.4.2.1 – Logging
Pushing the CONTINUE button will cause the specified Event Dispatcher
Relay Logging to be enabled (either Console, Monitor or File).
Enabling the Console logging will cause Phase IV events to be logged
to the operator console (OPA0).
Enabling the Monitor logging will cause Phase IV events to be logged
to the Operator Communication Facility (OPCOM).
Enabling the File logging will cause Phase IV events to be recorded
in binary format.
Pushing the CANCEL button will dismiss the window with no action taken.
8.4.3 – Sink
Pushing the CONTINUE button will cause the specified Event Dispatcher
Sink to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.5 – FDDI
8.5.1 – Station
Pushing the CONTINUE button will cause the specified FDDI Station to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.6 – FRAME
Pushing the CONTINUE button will cause the FRAME entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.6.1 – Link
Pushing the CONTINUE button will cause the specified FRAME Link to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.7 – HDLC
8.7.1 – Link
Pushing the CONTINUE button will cause the specified HDLC Link to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.7.1.1 – logical_station
Pushing the CONTINUE button will cause the specified HDLC Link Logical
Station to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.8 – MODEM
8.8.1 – line
Pushing the CONTINUE button will cause the Modem Connect Line entity to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.9 – MOP
Pushing the CONTINUE button will cause the MOP entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.10 – nsp
Pushing the CONTINUE button will cause the NSP entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.11 – Osak
Pushing the CONTINUE button will cause the specified OSAK entity to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.12 – osi_transport
Pushing the CONTINUE button will cause the OSI Transport entity to be
enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.13 – Routing
Pushing the CONTINUE button will cause the Routing entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.13.1 – Circuit
Pushing the CONTINUE button will cause the specified Routing Circuit to
be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.13.1.1 – ip_reachable_address
Pushing the CONTINUE button will cause the specified Routing Circuit IP
Reachable Address to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.13.1.2 – reachable_address
Pushing the CONTINUE button will cause the specified Routing Circuit
Reachable Address to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.13.2 – egp_group
Pushing the CONTINUE button will cause the specified Routing EGP Group
to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.13.2.1 – egp_neighbor
Pushing the CONTINUE button will cause the specified Routing EGP Group's
EGP Neighbor to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.14 – session
Pushing the CONTINUE button will cause the Session Control Entity
to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.15 – x25_access
Pushing the CONTINUE button will cause X.25 Access entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.16 – app
Pushing the CONTINUE button will cause the specified X.25 Access Application
entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.17 – x25_client
Pushing the CONTINUE button will cause the specified X.25 Client entity
to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.18 – x25_relay
8.18.1 – client
Pushing the CONTINUE button will cause the specified X.25 Relay Client
entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.18.2 – pvc
Pushing the CONTINUE button will cause the specified X.25 Relay PVC entity
to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.19 – x25_server
Pushing the CONTINUE button will cause the X.25 Server entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.19.1 – client
Pushing the CONTINUE button will cause the specified X.25 Server Client
entity to be enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
8.20 – x25_protocol
8.20.1 – dte
Pushing the CONTINUE button will cause the specified X.25 Protocol DTE
entity enabled.
Pushing the CANCEL button will dismiss the window with no action taken.
9 – enable_disable
9.1 – MOP
9.1.1 – Circuit
Toggle buttons in the on state (filled in) represent those MOP
functions enabled for the circuit. Toggle buttons in the off state
(empty) represent those MOP functions disabled for the circuit.
To enable a function, click on the associated toggle button until that
button is in the on state.
To disable a function, click on the associated toggle button until that
button is in the off state.
Once you have determined that all the toggle buttons are in their proper
states, press the CONTINUE button to cause the appropriate Enable and
Disable commands to be issued. Or press the CANCEL button to cancel the
operation. In either case, you will be returned to the main window.
9.2 – Node
Toggle buttons in the on state (filled in) represent those functions
enabled for the Node. Toggle buttons in the off state (empty) represent
those functions disabled for the Node. To enable a function, click on
the associated toggle button until that button is in the on state.
To disable a function, click on the associated toggle button until that
button is in the off state. The functions are:
Address Enables the address watcher function. Enabling
Watcher this function allows the node to update its
address identifier when a change of address is
detected.
Disabling this function causes the state attribute
to be set to off, but the node can still respond to
management through its CMIP interface.
CMIP Enabled automatically by the software. This
Listener function permits the node to respond to management
through its CMIP listener interface.
Once you have determined that all the toggle buttons are in their proper
states, press the CONTINUE button to cause the appropriate enable and
disable commands to be issued. Or press the CANCEL button to cancel the
operation. In either case, you will be returned to the main window.
10 – Getnif
10.1 – FDDI
10.1.1 – Station
10.1.1.1 – Link
Causes the link subentity to transmit a SMT NIF (Neighbor
Information) request frame and await the response. If a response
is received, it is displayed.
getnif [node node-id] fddi station station-name link link-id
target lan address timeout integer-16
10.1.1.1.1 – Arguments
o target
48-bit LAN address of the target.
o timeout
Value: 1-65535
Timeout, in seconds, optional.
11 – Getsif
11.1 – FDDI
11.1.1 – Station
11.1.1.1 – Link
Causes the link subentity to transmit a SMT SIF (Station
Information) request frame and await the response. If a response
if received, it is displayed.
getsif [node node-id] fddi station station-name link
link-id target lan address timeout integer-16 type
configuration
operation
11.1.1.1.1 – Arguments
o target
48-bit LAN address of the target.
o timeout
Value: 1-65535
Timeout, in seconds, optional.
o type
Value: Configuration or operation
SIF configuration or SIF operation request.
12 – Limit
12.1 – HDLC
12.1.1 – Link
12.1.1.1 – logical_station
Limits the specified HDLC Link Logical Station exclusively to
unsequenced data service.
13 – Load
13.1 – MOP
13.1.1 – Circuit
Initiates a downline load from the node you are managing to
a target system. If you optionally chose to enter a Client name
in the previous menu, the default load parameters for this operation
were obtained by looking up the information for that MOP Client, and
those parameters are present in the current display.
The required arguments for this load operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit you have currently selected for the load operation.
The optional arguments for this load operation are:
o Client
A client entity to be used for this operation, if you provided one
in the previous display.
o Management Image
A file containing initialization data for the node; data is
encoded in a product-specific format. (Also see the script file
argument.) This argument may be required by the target system.
o Script File
A file containing initialization data for the node; data is
encoded as a sequence of network management commands in CMIP
form. (Also see the management image argument.) This argument may
be required by the target system.
o Secondary Loader
Specifies the name of a second file containing the software to
be downline loaded. This argument may be required by the target
system.
o System Image
Specifies the file containing the system image to be downline
loaded. This argument is required for LAN circuits. If you do not
supply this information as an argument for this command, you must
specify a client set of parameters to provide this data. See the
client argument.
o Tertiary Loader
Specifies the name of a third file containing the software to
be downline loaded. This argument may be required by the target
system.
o Verification
Is a hex string that must match a verification code at the receiving
system in order to trigger the bootstrap mechanism so that the
downline load can be performed. The default is '0000000000000000'H,
or %x00-00-00-00-00-00-00-00.
Pressing the OK button will cause the load command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No load
command will be issued.
13.1.2 – Client
Initiates a downline load from the node you are managing to
a target client system.
The required arguments for this load operation are:
o Address
The LAN address of the target node on circuit named in the circuit
argument.
o Circuit
The MOP circuit over which the load operation is to occur.
The optional arguments for this load operation are:
o Management Image
A file containing initialization data for the node; data is
encoded in a product-specific format. (Also see the script file
argument.) This argument may be required by the target system.
o Script File
A file containing initialization data for the node; data is
encoded as a sequence of network management commands in CMIP
form. (Also see the management image argument.) This argument may
be required by the target system.
o Secondary Loader
Specifies the name of a second file containing the software to
be downline loaded. This argument may be required by the target
system.
o System Image
Specifies the file containing the system image to be downline
loaded. This argument is required for LAN circuits. If you do not
supply this information as an argument for this command, you must
specify a client set of parameters to provide this data. See the
client argument.
o Tertiary Loader
Specifies the name of a third file containing the software to
be downline loaded. This argument may be required by the target
system.
o Verification
Is a hex string that must match a verification code at the receiving
system in order to trigger the bootstrap mechanism so that the
downline load can be performed. The default is '0000000000000000'H,
or %x00-00-00-00-00-00-00-00.
Pressing the OK button will cause the load command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No load
command will be issued.
14 – Loop
14.1 – Loopback application
Starts a loop test between the loopback applications on the
specified source and destination nodes. The node keyword
specifies the node from which the loop messages are sent. If
you omit this keyword, the test is performed from the node on
which you issue the loop command. The name or address argument
specifies the node whose loop mirror is used to reflect the
messages back to the originator. Specify either the name or
address (but not both).
address tower-set
count integer
loop [node node-id] loopback application format hex-string
length integer
name full-name
14.1.1 – Characteristics
o address tower-set
Number of the destination for loopback messages, in the form
of a protocol tower. Specify either this argument or the name
argument.
o count integer
Default: 1 Value: 0-4294967295
Number of loop messages to be sent to the loop mirror. The test
is complete when this number of loop messages has been reflected
back by the loop mirror.
o format hex-string
Default: 55 Value: 00-FF
Content of the data field of a loop message. Enter a pair of
hexadecimal digits. Each octet in the data field of a loop
message has this value.
o length integer
Default: 40 Value: 0-65534
Length, in octets, of the data field in each loop message.
o name full-name
DNS name of the node to which loopback messages are sent. Specify
either this argument or the address argument, but not both.
14.2 – MOP
14.2.1 – Circuit
Performs a loop operation with another system. If you optionally
chose to enter a Client Name in the previous menu, the default loop
parameters for this operation were obtained by looking up the
information for that MOP Client, and those parameters are present in
the current display.
The required arguments for this loop operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit you have currently selected for the loop operation.
The optional arguments for this loop operation are:
o Client
A client entity to be used for this operation, if you provided one
in the previous display.
o Count
An integer representing the number of messages to be looped.
On failure of the loop test, a the count of messages
successfully looped will be displayed.
o Format
Value of each byte in the test data part of each loop message.
The default results in alternating 0 and 1 bits.
o Length
Integer representing length of the test data part of each loop
message. The maximum and minimum permitted values depend on the
particular data link in use.
o Assistance Type
Degree of loopback assistance required, for LAN circuits only.
Valid values are none, transmit, receive, and full.
o Assistant Address
LAN address to be used as a loopback assistant. The involvement
of the assistant depends on the assistance type parameter. For
assistance of type none, no assistant is needed, and is ignored
if specified. For other values, an assistant is required. If not
specified, an assistant is located by first sending a request to
the loopback assistant multicast address.
o Assistant System
A MOP Client entity, from which an assistant address is obtained.
Meaningful for LAN circuits only, see assistant address.
Pressing the OK button will cause the loop command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No loop
command will be issued.
14.2.2 – Client
Performs a loop operation with the specified client system.
The required arguments for this loop operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit over which this loop operation is to be performed.
The optional arguments for this loop operation are:
o Count
An integer representing the number of messages to be looped.
On failure of the loop test, a the count of messages
successfully looped will be displayed.
o Format
Value of each byte in the test data part of each loop message.
The default results in alternating 0 and 1 bits.
o Length
Integer representing length of the test data part of each loop
message. The maximum and minimum permitted values depend on the
particular data link in use.
o Assistance Type
Degree of loopback assistance required, for LAN circuits only.
Valid values are None, Transmit, Receive, and Full.
o Assistant Address
LAN address to be used as a loopback assistant. The involvement
of the assistant depends on the assistance type parameter. For
assistance of type none, no assistant is needed, and is ignored
if specified. For other values, an assistant is required. If not
specified, an assistant is located by first sending a request to
the loopback assistant multicast address.
o Assistant System
A MOP Client entity, from which an assistant address is obtained.
Meaningful for LAN circuits only, see assistant address.
Pressing the OK button will cause the loop command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No loop
command will be issued.
15 – Query
15.1 – MOP
15.1.1 – Circuit
Initiates an XID exchange between the system you are managing and the
system specified by the LAN Address below. If you optionally
chose to enter a Client Name in the previous menu, the default query
parameters for this operation were obtained by looking up the
information for that MOP Client, and those parameters are present in
the current display.
The required arguments for this query operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP Circuit entity you have currently selected for the query
operation.
The optional arguments for this query operation are:
o Client
A client entity to be used for this operation, if you provided one
in the previous display.
o SAP
An octet representing the Service Access Point (on the target system)
to which the XID message is to be sent.
Pressing the OK button will cause the query command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No query
command will be issued.
15.1.2 – Client
Initiates an XID exchange between the system you are managing and the
system specified by the LAN Address below.
The required arguments for this query operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP Circuit over which the query operation is to be performed.
The optional argument for this query operation is:
o SAP
An octet representing the Service Access Point (on the target
system) to which the XID message is to be sent.
Pressing the OK button will cause the query command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No query
command will be issued.
16 – Rename
16.1 – Node
Changes the node's name within the node and does not affect
the name server directly. It uses the new name and an immediate
"keep me here" transaction with the name servers which then update
themselves based on the node's new name.
The node's new fullname is a required argument.
Pressing the CONTINUE button will cause the node to be renamed.
Pressing the CANCEL button will dismiss the window with no rename
action taken.
17 – Reset
17.1 – evd
17.1.1 – outbound_stream
Pushing the CONTINUE button resets the catchall, specific, and global
filters to the default value for the specified Event Dispatcher
Outbound Stream entity. It causes these filters to be reset to the
values they had when the entity was created. It is equivalent to
setting the values for these filters to their defaults.
Pushing the CANCEL button dismisses the window, and no reset action
is taken.
17.1.2 – Sink
Pushing the CONTINUE button resets the catchall, specific, and global
filters to the default value for the specified Event Dispatcher Sink
entity. It causes these filters to be reset to the values they
had when the entity was created. It is equivalent to setting the
values for these filters to their defaults.
Pushing the CANCEL button dismisses the window, and no reset action
is taken.
18 – Shutdown
18.1 – event_dispatcher
18.1.1 – outbound_stream
Pushing the CONTINUE button requests an orderly shutdown of the
connection between the specified Event Dispatcher Outbound Stream
entity and the sink partner. The shutdown directive attempts an
orderly shutdown of the connection in cooperation with the sink.
Pushing the CANCEL button dismisses the window, and no shutdown
action is taken.
19 – Test
19.1 – evd
Pushing the CONTINUE button causes an event be logged to test the
entire event logging subsystem. This tests the complete event
logging system from entity to manager, causing the test requested
event to be logged.
Pushing the CANCEL button dismisses the window, and no test
action is taken.
19.2 – MOP
19.2.1 – Circuit
Initiates an XID test between the system specified by the LAN
Address described below. If you optionally chose to enter a
Client Name in the previous menu, the default test parameters for
this operation were obtained by looking up the information for that
MOP Client, and those parameters are present in the current display.
The required arguments for this test operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit you have currently selected for the test operation.
The optional arguments for this test operation are:
o Client
A client entity to be used for this operation, if you provided one
in the previous display.
o Count
An Integer representing the number of test messages to be sent.
o Format
Value of each byte in the data part of each test message.
The default results in alternating 0 and 1 bits.
o Length
Integer representing Length of the data part of each test
message. The maximum and minimum permitted values depend on the
particular data link in use.
o SAP
An octet representing the Service Access Point (on the target
system) to which the XID message is to be sent.
Pressing the OK button will cause the test command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No test
command will be issued.
19.2.2 – Client
19.2.2.1 – Circuit
Initiates an XID test between the system specified by the LAN
Address described below.
The required arguments for this test operation are:
o Address
The LAN address of the target node on the circuit named in the
circuit argument.
o Circuit
The MOP circuit over which the test is to occur.
The optional arguments for this test operation are:
o Count
An integer representing the number of test messages to be sent.
o Format
Value of each byte in the data part of each test message.
The default results in alternating 0 and 1 bits.
o Length
Integer representing Length of the data part of each test
message. The maximum and minimum permitted values depend on the
particular data link in use.
o SAP
An octet representing the Service Access Point (on the target
system) to which the XID message is to be sent.
Pressing the OK button will cause the test command to be executed and
will return control back to the main window.
Pressing the RESET button will cause all the arguments to be reset back
to the state they were in when you first entered this display.
Pressing the CANCEL button will return you to the main window. No test
command will be issued.
20 – Testevent
20.1 – evd
20.1.1 – outbound_stream
20.1.2 – Sink
21 – UNLIMIT
21.1 – HDLC
21.1.1 – Link
21.1.1.1 – logical_station
Pressing the CONTINUE button will enable sequenced and unsequenced
data service for the specified Logical Station.
Pressing the CANCEL button will dismiss the window, and no Unlimit
action will be taken.
22 – Update
22.1 – session_control
22.1.1 – backtranslation_softlink
Pushing the CONTINUE button will update a the specified
Backtranslation Softlink entity.
Pushing the CANCEL button will dismiss the window, and no update
action will be taken.
22.1.2 – tower_maintenance
Pushing the CONTINUE button updates the specified Tower Maintenance
entity.
Pushing the CANCEL button will dismiss the window, and no update
action will be taken.