Use the set command to modify one or more attributes of an
entity. For example:
ncl> set node 0 osi transport delay factor=6,delay weight=10
modifies two characteristics of the OSI Transport entity. If
you specify more than one characteristic in a set command, use a
comma to separate each characteristic and its value.
If you specify a characteristic name, but no value, the
characteristic is set to its default value; for example:
ncl> set node 0 osi transport delay factor
sets delay factor to its default value, 4.
Use set to give a value to a characteristic whose value is a set,
for example:
ncl> set node 0 osi transport cons filters={filter_2,filter_3}
but note the difference between this command and:
ncl> add node 0 osi transport cons filters={filter_2,filter_3}
The set command gives the cons filters characteristic a set value
with two components: filter_2 and filter_3; if the set previously
had other values, these are lost. The add command, on the other
hand, adds the values filter_2 and filter_3 to whatever values
the characteristic already has; any other current values are
retained.
To specify the empty set (that is, a set with no values), specify
{ } as the value.
The set of attributes called characteristics can be
changed by direct management commands and not by the system or
indirect commands. For example, it may be changed by the set
command, but not by the create or enable commands. However, some
characteristics are read-only and never change. Each entity section
gives complete information about the entity's characteristics, if any,
and explains if and how they are modified.
Sequences, sets, and similar constructed data types must be
explicitly stated in a set command.
There are certain restrictions on the use of set to modify
characteristics:
o Some characteristics can be modified only while the entity is
disabled.
o A few characteristics can be modified only while the entity
is disabled, and can then have only their value increased, not
decreased.
1 – alias (OpenVMS)
set [node node-id] alias port port-name -
selection weight integer
Selection Weight is 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. Selection Weight is used to
apportion incoming alias connections according to the capacity
of each alias member. Nodes with greater capacity should have
larger values of Selection Weight, while local area VMScluster
satellities should generally have a value of zero. Values
between 0 and 10 are suggested.
NOTE
The nsp maximum transport connection value determines the
number of connections on an alias member. If the Alias Port
is enabled, changing the nsp maximum transport connection
value has no effect.
Example:
set alias port DEC:.LKG.BULEAN selection weight 5
2 – ddcmp (OpenVMS VAX)
2.1 – link
set [node node-id] ddcmp link link-name ...
Modifies the attributes of a link to a DDCMP communications port.
The modifiable attributes and their data types [in brackets] are:
retransmit timer [integer]
physical line [local-entity-name]
receive buffers [integer]
Refer to attributes for specific command examples, or select
logical_station to view the settable attributes of the ddcmp
link logical_station subentity.
2.1.1 – physical_line
Default: No name Value: Local entity name
Name of the Physical layer entity that the link operates over. A
value for this characteristic must be set before the link entity
is enabled. You can modify this characteristic only when the
entity is disabled.
set [node node-id] ddcmp link link-name -
physical line local-entity-name
2.1.2 – receive_buffers
Default: 4 Value: 1-255
Specifies the number of receive buffers reserved for the link.
You can only increase the characteristic value.
set [node node-id] ddcmp link link-name receive buffers integer
Example:
set ddcmp link ddcmp-0 receive buffers 8
2.1.3 – retransmit_timer
Default: 3000 Value: 1-65535
Maximum time (in milliseconds) to wait between sending a message
and receiving a valid response. If this time expires, the local
station takes error recovery action. On full-duplex point-to-
point links, the timer is started immediately when a message is
sent.
set [node node-id] ddcmp link link-name retransmit timer integer
Example:
set ddcmp link ddcmp-0 retransmit timer 3000
2.1.4 – logical_station
set [node node-id] ddcmp link link-name -
logical station station-name ...
Modifies the attributes of a ddcmp link logical station entity
which manages a link to a remote station. The modifiable
attributes and their data types [in brackets] are:
address [integer]
babble timer [milliseconds]
holdback timer [milliseconds]
transmit window [integer]
Refer to attributes for specific command examples.
2.1.4.1 – address
Default: 1 Value: 1-255
Data link address of the remote station or tributary. You can
modify this characteristic only when the entity is disabled.
set [node node-id] ddcmp link link-name -
logical station station-name -
address integer
Example:
set ddcmp link ddcmp-0 logical station ddcmp-0 address 1
2.1.4.2 – babble_timer
Default: 6000 Value: 1-65535
Specifies the time, in milliseconds, for which a selected
tributary or remote station is allowed to transmit. This
characteristic is not used on full-duplex links.
This characteristic is not supported if the characteristic
protocol of the owning ddcmp link entity is set to tributary.
set [node node-id] ddcmp link link-name -
logical station station-name -
babble timer integer
Example:
set ddcmp link ddcmp-0 logical station ddcmp-0 babble timer 6000
2.1.4.3 – holdback_timer
Default: 0 Value: 0-13000
Maximum time, in milliseconds, that the local station can delay
acknowledging a received message if there is no data to send.
The value of this characteristic is linked to the retransmit
timer used on the remote station. A suggested value is between
10% and 20% of that timer. However, the actual values you can use
may be limited by the communications product.
The default value indicates that no holdback is used and the
local station must acknowledge immediately.
set [node node-id] ddcmp link link-name -
logical station station-name -
holdback timer integer
Example:
set ddcmp link ddcmp-0 logical station ddcmp-0 -
holdback timer 0
2.1.4.4 – transmit_window
Default: 1 Value: 1-255
Specifies the maximum number of data messages that the local
station can send without receiving an acknowledgment. This
characteristic applies only when the remote station is a control
station or on a half-duplex, point-to-point link. The value of
this characteristic must be less than or equal to the equivalent
of the maximum transmit characteristic on the control station or
remote station.
set [node node-id] ddcmp link link-name -
logical station station-name -
transmit window integer
Example:
set ddcmp link ddcmp-0 logical station ddcmp-0 -
transmit window 127
3 – device
set [node node-id] device unit simple-name ...
Modifies the attributes of a ddcmp link logical station entity
which manages a link to a remote station. The modifiable
attributes and their data types [in brackets] are:
auto load [boolean]
dump destination [filespec]
dump on error [boolean]
load source [filespec]
3.1 – auto_load
Default: True Value: True or false
Specifies whether the device should try to load its microcode
without management intervention. Autoloading would occur after
initialization, a failure, or a dump.
3.2 – dump_destination
File specification to hold the contents of the device's microcode
when a dump occurs.
For Tru64 UNIX, the default value for the dump destination is
/usr/var/xxx.dump where xxx is the device specification. For
example: /usr/var /dsv.dump.
3.3 – dump_on_error
Default: False Value: True or false
Whether a device should try to dump its microcode after a device
failure. Set this characteristic only for those devices that
support the dump operation.
3.4 – load_source
Default: None Value: File specification
File specification that contains the device's microcode. This is
used during a load operation.
For Tru64 UNIX the default value is /usr/var/xxx.firmware, where xxx
is the device specification. For example: /usr/var/dsv.firmware.
4 – dns
set [node node-id] dns clerk clerk timeout [seconds]
solicit holddown [seconds]
default namespace [namespace-ident]
Modifies the clerk timeout, solicit holddown, or default namespace
attributes for the dns clerk entity.
Known namespace is a subentity of the dns clerk. To view the
modifiable attributes of a dns clerk known namespace entity, select
known_namespace below.
You must have the NET$MANAGE rights identifier (OpenVMS systems) or
superuser privileges (Tru64 systems).
Examples:
set node .eng.rigel dns clerk clerk timeout 90
set dns clerk solicit holddown 20
4.1 – clerk_timeout
Default: 60 seconds
Specifies the default timeout of client interface calls. If no
response is received in the specified timeout, the clerk generates
an error message.
4.2 – default_namespace
Default: none
Designates the Known Namespace whose name is given as the default
namespace for this clerk. A namespace-ident must be supplied using
either the name or the nscts; there is no default:
name The name of the namespace. The name argument may
be different from the nickname if the nickname is
ambiguous.
nscts The value of the namespace creation timestamp
(NSCTS) assigned to the specified namespace when
it was created. The format is 14 pairs of hex
digits (xx-xx).
4.3 – solicit_holddown
Default: 15 seconds
Specifies the time (in seconds) to wait after initialization
before soliciting advertisements from servers.
4.4 – known_namespace
set [node node-id] dns clerk -
known namespace [namespace-ident] name[=]new-name
Specifies a new name for a known namespace entity. The nickname
attribute is not changes. You will find this command useful in
the case of ambiguous nicknames, where a name was generated that
you want to change. You can also enter this command through the
dns$control utility. The namespace identifier may be specified
using either the name or the nscts:
name The name of the namespace. The name argument may
be different from the nickname if the nickname is
ambiguous.
nscts The value of the namespace creation timestamp
(NSCTS) assigned to the specified namespace when
it was created. The format is 14 pairs of hex
digits (xx-xx).
You must have the NET$MANAGE rights identifier (OpenVMS systems) or
superuser privileges (Tru64 systems).
The following command renames the IAF_1 namespace in the local
clerk's cache with the new name NDL:
set dns clerk known namespace IAF_1 name NDL
5 – dtss
set [node node-id] dtss ...
Modifies the attributes for the dtss entity. The modifiable
attributes and their data types [in brackets] are:
advertisement interval [relative-time]
check interval [relative-time]
courier role [role]
error tolerance [relative-time]
global directory [full-name]
lan timeout [relative-time]
maximum inaccuracy [relative-time]
query attempts [integer]
servers required [integer]
synchronization hold down [relative-time]
wan timeout [relative-time]
Example:
set dtss servers required 3
5.1 – advertisement_interval
Default: 0-01:30:00.000 Value: 0-00:00:30.000-99-99:99:99.999
Specifies the amount of time between a server's advertisement
broadcasts.
5.2 – check_interval
Default: 0-01:30:00.00 Value: 0-00:00:30.000-99-99:99:99.999
Specifies the amount of time between checks for faulty servers.
Applicable only to servers that have external time-providers.
5.3 – courier_role
Specifies a server's interaction with the set of global servers.
backup courier The local server becomes a courier if none are
available on the LAN.
courier The local server synchronizes with the global set
of servers.
noncourier The local server does not routinely synchronize
with the global set of servers. This is the
default.
5.4 – error_tolerance
Default: 0-00:10:00.000 Value: 0-00:00:00.500-99-99:99:99.999
Specifies the maximum separation allowed between the local clock
and the computed time before synchronizations become abrupt
rather than gradual (monotonic).
5.5 – global_directory
Specifies the full name of the DECdns directory that contains the
list of DECdts servers that belong to the global set.
5.6 – lan_timeout
Default: 0-00:00:02.000 Value: 0-00:00:01.000-0-00:05:00.000
Specifies the amount of time the node waits for a response
to a synchronization request before sending another request
or declaring a server to be unavailable. The node sends
three requests before declaring a non-responding server to be
unavailable.
5.7 – maximum_inaccuracy
Default: 0-00:01:40.00 Value: 0-00:00:00.0 - 99 99:99:99.99
Specifies the inaccuracy limit for the node. When the node exceeds
the maximum inaccuracy setting, it attempts to synchronize.
5.8 – query_attempts
Default: 3 Value: 1-10
Specifies the number of attempts that a node makes to contact a
server before the node considers the server unavailable.
5.9 – servers_required
Default: 3 (servers) Value: 1-32
1 (clerks)
Specifies the minimum number of servers the specified node must
successfully query for time values before it can synchronize.
5.10 – synchronization_hold_down
Default: 0-00:10:00.0(Clerks) Value: 0-00:00:30.0- 01 00:00:00.00
0-00:02.00.0-(Servers)
Specifies the interval a node must wait to synchronize. Also
specifies synchronization frequency when a node reaches the value
specified by the maximum inaccuracy characteristic.
5.11 – wan_timeout
Default: 0-00:00:15.000 Value: 0-00:00:01.000-0-00:10:00.000
Specifies the amount of time the node waits for a response to a
WAN synchronization request before sending another request and
declaring a global server to be unavailable. The node sends three
requests before declaring a non-responding global server to be
unavailable.
6 – event_dispatcher
6.1 – outbound_stream
set [node node-id] event dispatcher -
outbound stream simple-name ...
Modifies the attributes for the event dispatcher outbound stream
entity, which represents an outgoing connection to a sink on a
local or remote node. The modifiable attributes and their data
types [in brackets] are:
catch all filter [action]
connect retry timer [seconds]
connect timer enabled [boolean]
disconnect timer [seconds]
sink address [sink-address-tower]
sink end user [end-user-spec]
sink node [full-name]
sink object [full-name]
template [simple-name] (Tru64 UNIX)
Refer to attributes for specific command examples.
6.1.1 – catch_all_filter
Default: Pass Value: Block or pass
Action to take if neither the specific filter nor the global
filter contains an entry that matches an event.
block Discard the event.
pass Report the event.
set [node node-id] event dispatcher outbound stream stream-name -
catch all filter block-or-pass
Example:
set event dispatcher outbound stream local_stream -
catch all filter pass
6.1.2 – connect_retry_timer
Default: 120 Value: 0-65535
Number of seconds to wait after a disconnect or connection reject
before reattempting a connection. Connection attempts continue
until a connection is made or until the connect timer enabled
attribute is set to false or the outbound stream is disabled.
If the outbound stream is already connected to the sink when
the timer expires, no connection is attempted at that time. The
timer resets and connection attempts continue whenever the timer
expires.
set [node node-id] event dispatcher outbound stream stream-name -
connect retry timer integer
Example:
set event dispatcher outbound stream local_stream -
connect retry timer 130, connect timer enabled true
6.1.3 – connect_timer_enabled
Default: True Value: True or false
Specifies whether the connect timer is operational (see connect
retry timer).
set [node node-id] event dispatcher outbound stream stream-name -
connect timer enabled boolean
Example:
set event dispatcher outbound stream local_stream -
connect retry timer 130, connect timer enabled true
6.1.4 – disconnect_timer
Default: 0; see Value: 0-4294967295
following description
Number of seconds to wait before disconnecting an idle
connection. Zero indicates that there is no disconnect timer
and connections are never automatically disconnected.
set [node node-id] event dispatcher outbound stream stream-name -
disconnect timer integer
Example:
set event dispatcher outbound stream local_stream -
disconnect timer 4294967295
6.1.5 – sink_address
Default: No address Value: Sink address tower set
Sink address tower for this stream. Modifying this characteristic
affects only subsequent connect requests; existing connections
are unaffected.
set [node node-id] event dispatcher outbound stream stream-name -
sink address {towerset}
6.1.6 – sink_end_user
Default: Number = 82 Value: End-user specification
Sink session control end user specification for this stream.
set [node node-id] event dispatcher outbound stream stream-name -
sink end user end-user-spec
Example:
set event disp out stream local_stream sink end user number = 82
6.1.7 – sink_node
Default: Local node Value: Full-name
Full DNS node name of the sink for this stream. Modifying this
characteristic affects only subsequent connect requests; existing
connections are unaffected. This fullname is used in combination
with the sink end user characteristic to establish the sink
connection.
set [node node-id] event dispatcher outbound stream stream-name -
sink node full-name
Example:
set event disp out stream lamchp_stream sink node LOCAL:.LAMCHP
6.1.8 – sink_object
Default: No sink object Value: Full-name
Full DNS object name of the sink for this stream. Modifying this
characteristic affects only subsequent connect requests; existing
connections are unaffected. This fullname should match the object
name characteristic of the target sink.
set [node node-id] event dispatcher outbound stream stream-name -
sink object full-name
6.1.9 – template (Tru64 UNIX)
Default: No template Value: Simple name
Transport template (see osi transport template) for this stream's
connections.
6.1.10 – Exception Messages
o entity class not supported (OpenVMS)
The Event Dispatcher is not registered with EMAA. The NET$EVD
process is probably not started. For instructions on how to
restart the Event Dispatcher, refer to
HELP NETWORK_MANAGEMENT EVENT_DISPATCHER.
6.2 – sink
set [node node-id] event dispatcher sink simple-name ...
Modifies the attributes for an event dispatcher sink entity, which
represents incoming connections and filters incoming events. The
modifiable attributes and their data types [in brackets] are:
catch all filter [block-or-pass]
client type [console-device-or-file]
device name [latin1string]
description [latin1string]
file name [filespec]
object name [full-name]
template [simple-name] (Tru64 UNIX)
user client [end-user-spec] (Tru64 UNIX)
displayuids [boolean]
Refer to attributes for specific command examples.
6.2.1 – catch_all_filter
Default: Pass Value: Block or pass
Specifies the action to take if neither the specific filter
setting nor the global filter setting matches an event or if a
filter setting that does match an event is set to Ignore.
block Discard the event.
pass Report the event.
set [node node-id] event dispatcher sink sink-name -
catch all filter block-or-pass
Example:
set event dispatcher sink local_sink -
catch all filter pass
6.2.2 – client_type
Specifies the application to accept the events received by the
sink. This can only be set when the event dispatcher sink entity
is disabled (when the sink state is off).
console Events go to the operator's console (OPCOM-OpenVMS).
This is the default.
device Events go to a device (see the device name
attribute).
file Events go to a file (see the file name
attribute).
set [node node-id] event dispatcher sink sink-name -
client type sink-type
Example:
set event dispatcher sink local_sink -
client type file, -
file name SYS$MANAGER:MYSINK.LOG
6.2.3 – description
Default: Null Value: Latin1String
Application description string. On OpenVMS, this string must
be embedded in quotes.
set [node node-id] event dispatcher sink sink-name -
description latin1string
6.2.4 – device_name
Default: Null Value: Latin1String
Name of the device to which events are going to be logged, if the
client type of the sink is device. On OpenVMS, this string must
be embedded in quotes.
set [node node-id] event dispatcher sink sink-name -
device name latin1string
6.2.5 – displayuids
Default: True Value: Boolean
A boolean value indicating whether to include the UIDs when
displaying an event.
set [node node-id] event dispatcher sink sink-name -
displayuids boolean
Example:
set event dispatcher sink local_sink displayuids false
6.2.6 – file_name
Default for Tru64 UNIX: Value: File specification
/usr/adm/event_file
Default for OpenVMS: Value: File specification
SYS$MANAGER:NET$EVD_SINK_sinkname.LOG
Name of the file to which events are going to be logged if the
client type of the sink is file.
set [node node-id] event dispatcher sink sink-name -
file name file-name
Example:
set event dispatcher sink local_sink -
client type file, -
file name SYS$MANAGER:MYSINK.LOG
6.2.7 – object_name
Default: No sink object Value: Full-name
Full DNS object name of the sink. Modifying this characteristic
affects only subsequent connect requests; existing connections
are unaffected.
set [node node-id] event dispatcher sink sink-name -
object name full-name
6.2.8 – template (Tru64 UNIX)
Default: No template Value: Simple name
Transport template (see the osi transport template entity) for
this sink's connections.
6.2.9 – user client (Tru64 UNIX)
Default: Null Value: End-user specification
Session control end user specification for a user program that
has been set to receive events.
7 – frame (OpenVMS)
7.1 – link
set [node node-id] frame link link-id ...
Modifies the attributes for an frame link entity, which is
associated with a physical line and controls the framing protocol
used on that line. The modifiable attributes and their data
types [in brackets] are:
bisync code [ASCII-or-EBCDIC]
bits per character [integer]
buffer size [integer]
crc type [crc-type]
framing timer [milliseconds]
initial state one [state-info]
initial state two [state-info]
local station address [integer]
match station address [on-or-off]
number of buffers [integer]
physical line [local-entity-name]
sync character [octet]
sync count [integer]
Examples:
set frame link frame-0 bisync code EBCDIC, -
framing timer 25, number of buffers 6
set frame link frame-1 match station address on
7.1.1 – bisync_code
Default: EBCDIC Value: ASCII or EBCDIC
Character code to be used on the link. This characteristic is
supported only when the characteristic protocol is set to one of
the following: bisync, chips, genbyte, or swift. You can modify
this characteristic only when the entity is disabled.
7.1.2 – bits_per_character
Default: 8 Value: 5-8
Number of bits in each character. This characteristic is
supported only when the characteristic protocol is set to
genbyte. You can modify this characteristic only when the entity
is disabled.
7.1.3 – buffer_size
Default: 512 Value: 0-65535
Size, in octets, of each receive buffer for the link. You can
modify this characteristic only when the entity is disabled.
Also, you can only increase the characteristic value.
7.1.4 – crc_type
CRC type used on the link:
AUTO_DIN
CRC_16
CRC_CCITT
CRC_CCITT0
LRC_EVEN
LRC_ODD
LRC_VRC_
EVEN
LRC_VRC_
ODD
NONE
The default value depends on the protocol.
BISYNC CRC_16
CHIPS LRC_EVEN
DDCMP CRC_16
GENBYTE NONE
HDLC CRC_CCITT
SDLC CRC_CCITT
SWIFT CRC_16
genbyte crc checking is done in the genbyte framing routine.
7.1.5 – framing_timer
Default: 25 Value: 10-1000
Maximum length of time, in milliseconds, to wait for the next
character to arrive. This characteristic is supported only when
the characteristic protocol is set to genbyte.
7.1.6 – initial_state_one
Default: 4
First 32 bits of state information. This characteristic is
supported only when the characteristic protocol is set to
genbyte. You can modify this characteristic only when the entity
is disabled.
7.1.7 – initial_state_two
Default: 4
Last 32 bits of state information. This characteristic is
supported only when the characteristic protocol is set to
genbyte. You can modify this characteristic only when the entity
is disabled.
7.1.8 – local_station_address
Default: 255 Value: 0-255
Address of the local station. The default value means that only
broadcast messages are accepted. The interpretation of this
characteristic is controlled by the value of the characteristic
match station address.
This attribute is supported only if the characteristic protocol
is set to sdlc. You can modify this characteristic only when the
entity is disabled.
7.1.9 – match_station_address
Default: Off Value: On or Off
Specifies whether the value of the characteristic local station
address is to be interpreted as a valid address. This attribute
is supported only if the characteristic protocol is set to
sdlc. You can modify this characteristic only when the entity
is disabled.
7.1.10 – number_of_buffers
Default: 4 Value: 0-255
Number of receive buffers reserved for the link. You can modify
this characteristic only when the entity is disabled. Also, you
can only increase the characteristic value.
7.1.11 – physical_line
Default: none Value: Local entity name
A local entity name specifying the physical layer line entity on
which the link entity is to operate. A non-null value must be
set before the link can be enabled. Can only be set when the
link is off.
7.1.12 – sync_character
Default: See description Value: 0-FF
Hexadecimal code of the sync character to be used on the link.
The default value depends on the value of the characteristic
protocol, as follows:
bisync 32
chips 32
ddcmp 96
genbyte 32
swift 32
This attribute is supported only if the characteristic protocol
is set to bisync, chips, ddcmp, genbyte, or swift. You can modify
this characteristic only when the entity is disabled.
7.1.13 – sync_count
Default: 4 Value: 0-255
Number of sync characters that precede each message. This
attribute is supported only if the characteristic protocol is
set to bisync, chips, ddcmp, genbyte, or swift. You can modify
this characteristic only when the entity is disabled.
8 – hdlc
8.1 – link
set [node node-id] hdlc link link-name ...
Modifies the attributes for an hdlc link entity, which is
associated with a port of the supporting physical layer module.
It contains attributes common to local HDLC operations for all
logical stations on the line. The modifiable attributes and
their data types [in brackets] are:
acknowledge timer [milliseconds]
holdback timer [milliseconds]
maximum data size [integer]
maximum unsequenced pdus [integer]
minimum data size [integer]
physical line [local-entity-name]
preferred crc type [CRC-type]
preferred local station address [integer]
preferred maximum data size [integer]
preferred window size [integer]
receive buffers [integer] (OpenVMS)
retry maximum [integer]
sequence modulus [8 or 128]
8.1.1 – acknowledge_timer
Default: 3000 Value: 1-60000
Time, in milliseconds, to wait for an acknowledgment before using
error recovery procedures. The value of this characteristic
corresponds to the T1 parameter of HDLC. You can modify this
characteristic only when the entity is disabled.
8.1.2 – holdback_timer
Default: 0 Value: 1-60000
Maximum time to wait before sending an acknowledgment supervisory
frame if no other frames carry the acknowledgment. A value of
zero means that the frame will be sent immediately if no I-frame
can be sent. You can modify this characteristic only when the
entity is disabled.
8.1.3 – maximum_data_size
Default: 1500 Value: 262-65532
Maximum number of bytes that users of the data link can specify.
This number applies to both transmit and receive frames.
The value of this characteristic must be greater than or equal to
the value of the minimum data size characteristic. You can modify
this characteristic only when the entity is disabled.
8.1.4 – maximum_unsequenced_pdus
Default: 1 Value: 1-127
Maximum number of unsequenced I-frames that a primary or
secondary station can send in a single transmission. This
characteristic is not used if the link type characteristic is
balanced.
8.1.5 – minimum_data_size
Default: 576 Value: 262-65532
Minimum number of bytes that users of the data link can specify.
This number applies to both transmit and receive frames.
The value of this characteristic must be less than or equal to
the value of the maximum data size characteristic. You can modify
this characteristic only when the entity is disabled.
8.1.6 – physical_line
Default: None Value: Local entity name
Local entity name of the the Physical layer entity over which the
HDLC protocol is to operate.
This characteristic must have a value before the HDLC link is
enabled. You can modify this characteristic only when the entity
is disabled.
8.1.7 – preferred_crc_type
Default: Either Value: 16 bit, 32 bit, or either
CRC types available for negotiation. If the value of this
characteristic is either, the station will try to use 32-bit but
will use 16-bit if that is all that the remote station supports.
8.1.8 – preferred_local_station_address
Default: 2 Value: 1-253
Address proposed for the local logical station during
negotiation. If there is no negotiation, the value of this
characteristic is the value that is used. If negotiation is
necessary, the value of this characteristic must be between 2
and 253. You can modify this characteristic only when the entity
is disabled.
8.1.9 – preferred_maximum_data_size
Default: 1500 Value: 262-65532
Default size (in octets) of frames that the station receives and
transmits. This value is used only if the link initialization
does not specify a buffer value.
The value of this characteristic must lie between those of the
maximum data size and minimum data size characteristics. You can
modify this characteristic to a lower value only when the entity
is disabled.
8.1.10 – preferred_window_size
Default: 2 Value: 1-127
Window size to be offered during negotiation for both receive
and transmit frames. The value of this characteristic must be
compatible with that for the sequence modulus characteristic.
8.1.11 – receive buffers (OpenVMS)
Default: 4 Value: 1-128
Number of receive buffers reserved for the link. This
characteristic can only be set to a lower value when the entity
is disabled.
8.1.12 – retry_maximum
Default: 10 Value: 1-255
Maximum number of times that a frame will be retransmitted before
the local station assumes that a fatal error has occurred. This
characteristic can be modified only when the entity is disabled.
8.1.13 – sequence_modulus
Default: 128 Value: 8 or 128
Whether modulo-8 or modulo-128 sequence numbering is allowed
on the HDLC link. The value 8 means that only normal sequence
numbering is allowed. The value 128 means that both extended and
normal sequence numbering are supported for negotiation.
9 – lapb
9.1 – link
set [node node-id] lapb link simple-name ...
Modifies the attributes for an lapb link entity, which is
associated with a port of the supporting physical layer, and
contains attributes that describle local LAPB operation. The
modifiable attributes and their data types [in brackets] are:
acknowledge timer [milliseconds]
holdback timer [milliseconds]
interface type [DTE-or-DCE]
maximum data size [integer]
physical line [local-entity-name]
poll timer [seconds]
receive buffers [integer] (OpenVMS)
retry maximum [integer]
sequence modulus [8-or-128]
window size [integer]
9.1.1 – acknowledge_timer
Default: Supplied by profile Value: 1-60000
Time, in milliseconds, to wait for an acknowledgment before
initiating recovery action. This attribute corresponds to the
LAPB parameter T1. You can modify this characteristic only when
the entity is disabled.
9.1.2 – holdback_timer
Default: Implementation specific Value: 0-60000
Delay, in milliseconds, before an acknowledgment must be sent.
This characteristic corresponds to the LAPB parameter T2. You can
modify this characteristic only when the entity is disabled.
9.1.3 – interface_type
Default: dte Value: dce or dte
Address mode for this link.
dce Use DCE address mode.
dte Use DTE address mode.
You can modify this characteristic only when the entity is
disabled.
9.1.4 – maximum_data_size
Default: Supplied by profile Value: 1-65532
Maximum frame size, in octets, of an information field in an
I-frame.
9.1.5 – physical_line
Default: No default Value: Local entity name
Name of the Physical layer and line entity over which the LAPB
protocol is to operate. You must give this characteristic a value
before you enable the link.
9.1.6 – poll_timer
Default: Implementation specific Value: Supplied by profile
Maximum period in seconds that may elapse without frames being
exchanged on the Data Link. On expiration, an RR(P) is sent to
elicit a response from the other end.
9.1.7 – receive buffers (OpenVMS)
Default: Implementation specific Value: 1-128
Specifies the number of receive data buffers.
9.1.8 – retry_maximum
Default: Supplied by profile Value: 1-255
Maximum number of times that a frame will be retransmitted
before assuming a fatal error, at which point more drastic
error recovery action will be attempted. This characteristic
corresponds to the LAPB parameter N2.
9.1.9 – sequence_modulus
Default: Supplied by profile Value: 8 or 128
Type of sequence numbering.
8 Use normal sequence numbering.
128 Use extended sequence numbering.
9.1.10 – window_size
Default: Supplied by profile Value: 1-127
Window size for transmitting and receiving I-frames. This
characteristic corresponds to the LAPB parameter K.
10 – llc2
10.1 – sap
set [node node-id] llc2 sap simple-name ...
Modifies the attributes for an llc2 service access point entity,
which allows links to be multiplexed over its associated port.
The modifiable attributes and their data types [in brackets] are:
lan station [local-entity-name]
local lsap address [octet]
Select link for information on setting the attributes of an
llc2 sap link subentity.
10.1.1 – lan_station
Default: No entity name Value: Local entity name
Specifies the name of the LAN station entity used by the SAP. You
must specify a value for this attribute before you enable the SAP.
10.1.2 – local_lsap_address
Default: 7E Value: 00-FE
Specifies the address of the local link service access point
(LSAP) to be used. The lowest significant bit of this value must
be clear; the address specified must be an individual address.
10.1.3 – link
set [node node-id] llc2 sap simple-name link simple-name ...
Modifies the attributes for an llc2 sap link entity, which
represents one of the links that operates over a particular SAP.
The modifiable attributes and their data types [in brackets] are:
acknowledge timer [milliseconds]
busy timer [milliseconds]
holdback timer [milliseconds]
local receive window size [integer]
maximum data size [octets]
poll timer [milliseconds]
reject timer [milliseconds]
remote lsap address [hex-number]
remote mac address [lan-address]
retry maximum [integer]
10.1.3.1 – acknowledge_timer
Default: 1000 Value: 1-60000
Specifies the time, in milliseconds, the link waits for an
acknowledgment before initiating recovery action.
The granularity of this timer is 10 milliseconds. Values that are
not multiples of 10 are rounded up.
10.1.3.2 – busy_timer
Default: 10000 Value: 1-60000
Specifies the time, in milliseconds, the link waits for indication
of the clearance of a busy condition at the remote station.
The granularity of this timer is 10 milliseconds. Values that are
not multiples of 10 are rounded up.
10.1.3.3 – holdback_timer
Default: 500 Value: 0-60000
Specifies the delay, in milliseconds, before an acknowledgment
must be sent. The granularity of this timer is 10 milliseconds.
Values that are not multiples of 10 are rounded down.
10.1.3.4 – local_receive_window_size
Default: 127 Value: 1-127
Specifies the window size used by the link for receiving frames.
10.1.3.5 – maximum_data_size
Default: 1027 Value: 1-65531
Specifies the largest frame size, in octets, the link can use to
send or receive data. This value does not include the size of the
frame header.
10.1.3.6 – poll_timer
Default: 1000 Value: 1-60000
Specifies the time, in milliseconds, the link waits for a response
with the F bit set.
The granularity of this timer is 10 milliseconds. Values that are
not multiples of 10 are rounded up.
10.1.3.7 – reject_timer
Default: 3000 Value: 1-60000
Specifies the time, in milliseconds, the link waits for a reply to
a REJ (reject) frame.
The granularity of this timer is 10 milliseconds. Values that are
not multiples of 10 are rounded up.
10.1.3.8 – remote_lsap_address
Default: 7E Value: Hex-number
Specifies the address of the destination LSAP (local service
access point) to be used by the link. The lowest significant
bit must be clear; the specified address must be an individual
address.
10.1.3.9 – remote_mac_address
Default: 00-00-00-00-00-00 Value: LAN-address
Specifies the destination MAC address to be used by the link.
10.1.3.10 – retry_maximum
Default: 10 Value: 1-255
Specifies the maximum number of times the link retransmits a frame
before assuming a fatal error and taking more drastic recovery
action.
11 – loopback_application
set [node node-id] loopback application -
maximum mirrors integer
Example:
set loopback application maximum mirrors 10
Maximum Mirrors is an integer (0-4294967295) specifying the
maximum number of loop mirrors supported. The default value
of 0 means the node supports an unlimited number of mirrors.
For Tru64 UNIX to limit the number of loop mirrors, use the
maximum instances characteristic of the session control application
mirror entity.
12 – modem_connect
12.1 – line
set [node node-id] modem connect line line-name ...
Modifies the attributes for an modem connect line entity, which is
associated with a physical circuit on the node. The modifiable
attributes and their data types [in brackets] are:
alternate speed [bits-per-second]
call accept timer [milliseconds]
carrier loss timer [milliseconds]
clock [external, internal, or reflected]
encoding [normal or nrzi]
initial hold timer [seconds] (Tru64 UNIX)
maximum call setup timer [seconds]
maximum disable transmit timer [milliseconds]
maximum dsr deassertion timer [milliseconds]
maximum enable transmit timer [milliseconds]
minimum dtr deassertion timer [milliseconds]
modem control [full or none]
modem options [dialout, direct or rate select]
modem protocol format [type] (Tru64 UNIX)
modem protocol type [prot-type] (Tru64 UNIX)
rate select [high or low]
speed [bits-per-second]
successful call indication timer [seconds]
suppress test indicator [boolean]
transmit holdoff timer [milliseconds]
12.1.1 – alternate_speed
Default: 0
Alternate (low) speed (in bits per second) to operate the
line. You can modify this characteristic only when the entity
is disabled. This characteristic is supported only when the
characteristic communications mode is asynchronous, the
characteristic modem control is full, the characteristic modem
options includes rateselect, the characteristic clock is internal,
and when the alternate line speed is needed.
12.1.2 – call_accept_timer
Default: 500
Minimum time, in milliseconds, between the assertion of data set
ready and accepting a call by asserting request to send. This
characteristic is not supported if the characteristic modem
control is none.
12.1.3 – carrier_loss_timer
Default: 15000
Maximum time, in milliseconds, that the carrier detect signal
can be absent before the loss of carrier event is generated.
This characteristic is not supported if the characteristic modem
control is none.
12.1.4 – clock
Source of the transmit and receive clocks.
external The modem provides the clock.
internal The communications device provides the clock.
reflected The DTE transmit clock is a reflection of the
DCE transmit clock. This minimizes the clock to
data skew that the DCE encounters when high line
speeds are used.
The default value depends on the setting of the characteristic
communications mode. If communications mode is asynchronous, the
default value of this characteristic is internal. Otherwise, the
default value is external.
The value of this attribute has no effect when the communications
line is in loopback mode. In this case, the type of loopback
determines the type of clock. You can modify this characteristic
only when the entity is disabled.
12.1.5 – encoding
Default: normal Value: normal or nrzi
Encoding technique used on the line. You can modify this
characteristic only when the entity is disabled.
12.1.6 – initial_hold_timer
Default: 10 Value: 0-300
Maximum time, in seconds, within which the control service client
must accept an incoming call. This characteristic is supported
only when the characteristic connection type is switched.
12.1.7 – maximum_call_setup_timer
Default: 60 Value: 1-300
Maximum time, in seconds, that can pass before an outgoing call
is connected. This characteristic is supported only when the
characteristic connection type is switched.
12.1.8 – maximum_disable_transmit_timer
Default: 500
Maximum time, in milliseconds, that clear to send can remain
asserted before the line is disconnected after Request to Send
is deasserted. This characteristic is not supported if the
characteristic modem control is none.
12.1.9 – maximum_dsr_deassertion_timer
Default: 5000
Maximum time, in milliseconds, the entity will wait for data set
ready to be deasserted after it has deasserted data terminal
ready. If this timer expires, the entity assumes it can assert
data terminal ready once again. This characteristic is not
supported if the characteristic modem control is none.
12.1.10 – maximum_enable_transmit_timer
Default: 2000 Value: 1-5000
Maximum time, in milliseconds, between the assertion of the
request to send signal and receiving the assertion of the clear
to send signal. This characteristic is not supported if the
characteristic modem control is none.
12.1.11 – minimum_dtr_deassertion_timer
Default: 1000
Minimum timer, in milliseconds, that the DTE will deassert data
terminal ready during a disconnection. This characteristic is not
supported if the characteristic modem control is none.
12.1.12 – modem_control
Default: full Value: full or none
Indicates whether the interchange circuits are to be monitored and
used. The value none means that only the data leads are monitored.
The value full must be used when the value of the characteristic
duplex is half. You can modify this this characteristic only when
the entity is disabled. This characteristic is supported only if
the characteristic connection type is non-switched.
12.1.13 – modem_options
Default: No options Value: Set of options
Set of values that determine the capabilities of the modem. The
value dialout is supported only if the value of communications
type is switched. You can modify this characteristic only
when the entity is disabled.
dialout The modem can dial the remote modem.
direct The modem is directly connected to the remote
modem through a non-switched line.
rate select The modem is capable of data rate selection.
The value direct must be accompanied with dialout and used only
when the modem protocol type supports direct dial.
Format the values to specify one or any combination of modem
options.
12.1.14 – modem protocol format (Tru64 UNIX)
Format to use for V.25bis protocol messages. You can modify
this characteristic only when the entity is disabled. This
characteristic is supported only when the characteristic
connection type is non-switched. This characteristic applies only
when the characteristic modem protocol type is v25bis or dmcl.
asynchronous Use the asynchronous format.
hdlc Use the HDLC format.
synchronous Use the synchronous format.
The default value depends on the value of the characteristic
communications mode. If communications mode is asynchronous, the
default value of this characteristic is also asynchronous. If the
value of communications mode is synchronous, the default value of
this characteristic is hdlc.
12.1.15 – modem protocol type (Tru64 UNIX)
Default: V25bis Value: See following description.
Protocol that the modem uses to select modem options and to set
line control parameters. You can modify this characteristic only
when the entity is disabled. This characteristic is supported only
when the characteristic connection type is non-switched.
at A set of automatic calling procedures used in the
Hayes Smartmodem 2400.
dmcl The Digital Modem Control Language, based on
V.25bis.
v25 A set of automatic calling and answering
procedures defined by CCITT. These procedures
use the 200-series circuits defined in the
CCITT recommendation V.24. The V.235 procedures
are also known as parallel automatic calling
procedures.
v25bis A set of automatic calling and answering
procedures defined by CCITT. These procedures
use the 100-series circuits defined in the CCITT
recommendation V.24. The V.25bis procedures
are also known as serial automatic calling
procedures.
12.1.16 – profile
Name of the local profile to be used with the line. The value of
this characteristic is a copy of the profile argument specified
when the entity is created. You cannot modify this characteristic.
12.1.17 – rate_select
Default: High Value: High or Low
Which of the line rates is to be used if none is specified when
a call is setup. high indicates that the value of the speed
characteristic be used, and low indicates that the value of the
alternate speed characteristic be used. This characteristic is
supported only if the characteristic modem control is full, and if
the characteristic modem options includes rateselect.
12.1.18 – speed
Default: 0
High speed (in bits per second) to be used on the line. This value
is always used on asynchronous links. It is used on synchronous
links only in the following circumstances:
o When the value of the clock characteristic is internal
o When a null modem cable is detected
o When using a loopback mode that uses internal clocking
You can modify this characteristic only when the entity is
disabled.
12.1.19 – successful_call_indication_timer
Default: 30
Maximum time, in seconds, that the entity will wait for indication
of a successful call before disconnecting the line. This
characteristic is supported only when the characteristic modem
control is none.
12.1.20 – suppress_test_indicator
Default: False Value: True or false
Indicates whether the Test Mode signal is to be monitored. Use the
value false if the DCE deals with the Test Mode signal.
Setting this characteristic to true means that the interchange
circuit status attribute test mode will also be displayed as
Unknown.
12.1.21 – transmit_holdoff_timer
Default: 0
Necessary delay, in milliseconds, between the transmitter
being disabled and being enabled again. The value 0 means
that the request to send signal can be asserted as soon as the
client requests it. This characteristic is not supported if the
characteristic modem control is none.
13 – mop
13.1 – circuit
set [node node-id] mop circuit circuit-name ...
Modifies the attributes for a mop circuit entity, which is
a data link circuit on which MOP services are available. The
modifiable attributes and their data types [in brackets] are:
known clients only [boolean]
link name [data-link-entity-name]
retransmit timer [seconds]
Refer to attributes for specific command examples.
13.1.1 – known_clients_only
Default: False Value: True or false
Specifies whether MOP attempts to service load requests from
remote systems which do not have a corresponding client entity.
Some network servers are designed to request specific software
by name, and in such a case there is no need for a client entity
to exist. By default, MOP tries to process requests for named
software from unknown clients. Set this attribute to true if you
wish MOP to ignore such requests.
set [node node-id] mop circuit circuit-name -
known clients only boolean
Example:
set mop circuit fddi-1 known clients only true
13.1.2 – link_name
Default: No name Value: Data link entity name
Name of a station entity in the Data Link layer module indicated
by the type characteristic. This name is passed to the Data Link
layer module when MOP opens a portal for the circuit.
set [node node-id] mop circuit circuit-name -
link name data-link-entity-name
13.1.3 – retransmit_timer
Default: 4 Value: 1-30
Time, in seconds, to wait for a response before retransmitting a
MOP protocol message.
set [node node-id] mop circuit circuit-name -
retransmit timer integer
Example:
set mop circuit fddi-1 retransmit timer 4
13.2 – client
set [node node-id] mop client client-name ...
Modifies the attributes for a mop circuit entity, which is
used to store default characteristics used by several MOP
functions. The modifiable attributes and their data types
[in brackets] are:
addresses [set of lan-addresses]
circuit [circuit-name]
device types [set of device-types] (OpenVMS)
diagnostic image [filespec]
dump address [integer]
dump file [filespec]
management image [filespec]
phase iv client address [phase4-address]
phase iv client name [phase4-name]
phase iv host address [phase4-address]
phase iv host name [phase4-name]
script file [filespec]
secondary loader [filespec]
system image [filespec]
tertiary loader [filespec]
verification [hex-string]
Refer to attribute descriptions for specific command examples.
13.2.1 – addresses
Default: Empty set Value: Set of LAN addresses
Set of LAN addresses for this client on the circuit specified
by the circuit characteristic.
For OpenVMS, Phase IV nodes can use an extended DECnet LAN
address in addition to their hardware address, so you must
include both of these addresses in the addresses set. To
calculate the extended DECnet address, express the Phase IV
node address as a four-digit hex integer, then add the
prefix AA-00-04-00.
For example, if the Phase IV node address is 4.260:
4.260
set [node node-id] mop client client-name -
addresses {lan-address[,lan-address..]}
Examples:
set mop client imply -
addresses {08-00-2b-13-d6-e0, aa-00-04-00-8a-13}
set mop client mynode addresses {08-00-2b-13-d6-e0}
13.2.2 – circuit
Default: No circuit Value: Circuit-id
Name of the MOP circuit that corresponds to the Data Link
circuit that is to be used for communicating with this client.
set [node node-id] mop client client-name circuit circuit-id
Examples:
set mop client imply circuit csmacd-1
13.2.3 – device types (OpenVMS)
Default: No device types Value: Set of device types
Specifies one or more device types associated with this client.
Use device types and omit addresses if you want to set up a
generic client entity; the entity will be used for any incoming
load or dump requests that specify a matching communications
device type.
To determine the communications device type for a particular
network server, consult the server documentation, or use the
Configuration Monitor Function of MOP.
set [node node-id] mop client client-name -
device types {device[,device...]}
Examples:
set mop client csma_clients device types {una,sva}
13.2.4 – diagnostic_image
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a diagnostic image
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
set [node node-id] mop client client-name -
diagnostic image {file-spec[,file-spec]}
13.2.5 – dump_address
Default: 1 Value: 0-4294967295
Memory address at which to begin an upline dump.
set [node node-id] mop client client-name dump address integer
Examples:
set mop client imply dump address 1
13.2.6 – dump_file
Default: No file Value: Sequence of file specifications
Files to write to when the client is upline dumped. File
identifications are interpreted according to the file system
of the local system.
set [node node-id] mop client client-name -
dump file {filespec[,filespec...]}
13.2.7 – management_image
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a management image
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
set [node node-id] mop client client-name -
management image {filespec[,filespec...]}
13.2.8 – phase_iv_client_address
Default: 0.0 Value: Phase IV address
Phase IV node address given to the client system when it is
downline loaded. This address is passed in a load parameters
message; whether it is needed depends on the software being
loaded.
set [node node-id] mop client client-name -
phase iv client address phaseiv-address
Example:
set mop client imply phase iv client name imply, -
phase iv client address 4.906
13.2.9 – phase_iv_client_name
Default: No name Value: Phase IV name
Phase IV node name given to the client system when it is downline
loaded. This name is passed in a load parameters message; whether
it is needed depends on the software being loaded.
set [node node-id] mop client client-name -
phase iv client name phaseiv-name
Example:
set mop client imply phase iv client name imply, -
phase iv client address 4.906
13.2.10 – phase_iv_host_address
Default: 0 Value: Phase IV address
Phase IV node address to be passed as the host node address when
a client is downline loaded. This address is passed in a load
parameters message; whether it is needed depends on the software
being loaded.
set [node node-id] mop client client-name -
phase iv host address phasiv-address
Example:
set mop client imply phase iv host name imply, -
phase iv host address 4.906
13.2.11 – phase_iv_host_name
Default: No name Value: Phase IV name
Phase IV node name that is passed as the host name when the
client is downline loaded. This name is passed in a load
parameters message; whether it is needed depends on the software
being loaded.
set [node node-id] mop client client-name -
phase iv host name phasiv-name
Example:
set mop client imply phase iv host name imply, -
phase iv host address 4.906
13.2.12 – script_file
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a CMIP initialization
script during a downline load operation. File identifications are
interpreted according to the file system of the local system.
set [node node-id] mop client client-name -
script file {filespec[,filespec...]}
13.2.13 – secondary_loader
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a secondary loader
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
set [node node-id] mop client client-name -
secondary loader {filespec[,filespec...]}
Example:
set mop client lamchp -
secondary loader {sys$system:secondary_vmb.exe}
13.2.14 – system_image
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests an operating system
image during a downline load operation. File identifications are
interpreted according to the file system of the local system.
set [node node-id] mop client client-name -
system image {filespec[,filespec...]}
Example:
set mop client lamchp -
system image {"@net$niscs_laa($1$dua0:<sys16.>)"}
13.2.15 – tertiary_loader
Default: No file Value: Sequence of file specifications
Files to be loaded when the client requests a tertiary loader
during a downline load operation. File identifications are
interpreted according to the file system of the local system.
set [node node-id] mop client client-name -
tertiary loader {filespec[,filespec...]}
Example:
set mop client lamchp -
tertiary loader {sys$system:tertiary_vmb.exe}
13.2.16 – verification
Default: %x00-00-00-00-00-00 Value: Hex string
Verification string to be sent in a boot message to this client.
The value must have an even number of digits from 2 to 16.
set [node node-id] mop client client-name -
verification hex-string
Example:
set mop client lamchp -
verification %x0000000000000000
14 – ncl
14.1 – default_access
Provides default access control information to be used for
subsequent NCL commands.
ncl> set ncl default access by user=username, password=password
This command is usually used in conjunction with the SET NCL
DEFAULT_ENTITY command to manage a remote Phase V node.
Refer to HELP NCL DEFAULT_CONTEXT for more information.
14.2 – default_entity
Allows you to set a default entity, to which all subsequent NCL
commands will refer.
ncl> set ncl default entity [entity-name]
Examples:
ncl> set ncl default entity session control
ncl> set ncl default entity -
node remnod"remoteuser remotepassword"
This command is usually used in conjunction with the SET NCL
DEFAULT_ENTITY command to manage a remote Phase V node. Refer to
HELP NCL DEFAULT_CONTEXT for more detailed information.
14.3 – logfile
set ncl logfile filespecification.ncl
This command, coupled with the "enable ncl logging" command,
will start the logging of an NCL session to the file specified.
To determine the name of the log file later on, use the "show
ncl logfile" command.
For example, on OpenVMS:
NCL>set ncl logfile test
NCL>enable ncl logging
NCL>show all
NCL>disable ncl logging
NCL>show ncl logfile
Logfile name is: test
Logfile is Disabled
The results will be in the file TEST.NCL. That file will
contain the logged NCL command(s), and the output will be
commented out. You may then reissue the command(s) you logged
by:
NCL>do test.ncl
15 – nsp
set [node node-id] nsp ...
Modifies the attributes of the nsp entity. The modifiable
attributes and their data types [in brackets] are:
congestion avoidance [boolean]
delay factor [integer]
delay weight [integer]
flow control policy [segment flow control|no flow control]
keepalive time [seconds]
maximum remote nsaps [integer]
maximum receive buffers [integer] (OpenVMS)
maximum transport connections [integer]
retransmit threshold [integer]
15.1 – congestion_avoidance
Default: False Value: True or false
Enables the use of the automatic congestion avoidance mechanism.
This mechanism reduces the transport window size in response to
an indication from the Network layer.
set [node node-id] nsp congestion avoidance boolean
Example:
set nsp congestion avoidance false
15.2 – delay_factor
Default: 2 Value: 2-15
Factor by which to multiply the current value of the roundtrip
delay estimate status attribute in order to set a value for the
retransmission timer.
Note, the roundtrip delay estimate is an attribute of the
nsp port entity.
set [node node-id] nsp delay factor integer
Example:
set nsp delay factor 2
15.3 – delay_weight
Default: 3 Value: 0-255
Relative weighting to apply to the current estimate and to a
new sample when estimating roundtrip delay.
set [node node-id] nsp delay weight integer
Example:
set nsp delay weight 3
15.4 – flow_control_policy
Default: Segment flow control Value: Segment flow control
or
no flow control
Determines NSP flow control policy used. This attribute may not be
changed when NSP state is "on."
Flow control is the mechanism that determines when to send a Data
or expedited messages. Flow control is performed separately for
normal and expedited data. During transport connection formation,
each end of the connection determines the kind of flow control
policy it expects when acting as a data receiver. It is not
required that both end operate with the same flow control policy.
set [node node-id] nsp flow control policy control-policy
Examples:
set nsp flow control policy segment flow control
set nsp flow control policy no flow control
15.5 – keepalive_time
Default for Tru64 UNIX: 30 Value: 1-65535
Default for OpenVMS: 60 Value: 1-65535
Time, in seconds, that NSP waits for data to be transmitted or
received before testing a transport connection. When this timer
expires, NSP sends a data request PDU to the remote NSP. This
PDU does not change the flow control parameters, but does require
acknowledgment. For Tru64 UNIX, You can modify this
characteristic to a lower value only when the entity is disabled.
set [node node-id] nsp keepalive time integer
Example:
set nsp keepalive time 60
15.6 – maximum receive buffers (OpenVMS)
Default: 2000 Value: 1-65535
Maximum number of receive buffers that can store received transport
PDUs. You may not decrease the value while NSP is enabled.
set [node node-id] nsp maximum receive buffers integer
Example:
set nsp maximum receive buffers 4000
15.7 – maximum_remote_nsaps
Default for Tru64 UNIX: 160 Value: 1-65535
Default for OpenVMS: 201 Value: 1-65535
Maximum number of remote NSAPs that can exist concurrently. Must
be equal to or greater than the default, which equals the current
value of maximum transport connections. You can modify this
characteristic to a lower value only when the entity is disabled.
set [node node-id] nsp maximum remote nsaps integer
Example:
set nsp maximum remote nsaps 201
15.8 – maximum_transport_connections
Default for Tru64 UNIX: 128 Value: 0-1023
Default for OpenVMS: 200 Value: 0-65535
Maximum number of active transport connections allowed at one
time. Must not be less than the current value of maximum remote
NSAPs. You may not decrease the value while NSP is enabled.
set [node node-id] nsp maximum transport connections integer
Example:
set nsp maximum transport connections 200
15.9 – retransmit_threshold
Default: 12 Value: 1-65535
Maximum number of times a source nsp entity is to restart an
expired retransmission timer before the remote node is to be
considered unreachable. When the threshold is reached, NSP
sets the confidence variable to false.
set [node node-id] nsp retransmit threshold integer
Example:
set nsp retransmit threshold 12
16 – osak (OpenVMS)
set [node node-id] osak disconnect timer integer
Example:
set osak disconnect timer 30
Disconnect timer is the length of time in seconds that the
OSAK software waits when it expects the remote peer to disconnect
a transport connection. If the timer expires and the remote peer
has not disconnected the connection, the OSAK software
disconnects the connection. The default disconnect timer is 30
seconds.
17 – osi_transport
set [node node-id] osi transport ...
Modifies the attributes of the osi transport entity. The modifiable
attributes and their data types [in brackets] are:
cltp nsap selector [integer] (Tru64 UNIX)
congestion avoidance [boolean]
CONS filters [set of simplenames]
CONS nsap address [set of NSAPs]
delay factor [integer]
delay weight [integer]
disconnect holdback [seconds]
maximum cltp ports [integer] (Tru64 UNIX)
maximum listeners [integer] (Tru64 UNIX)
maximum multiplexing [integer]
maximum network connections [integer]
maximum receive buffers [integer] (OpenVMS)
maximum remote nsaps [integer]
maximum transport connections [integer]
maximum window [integer]
nsap selector [integer]
RFC1006 listener ports [set of TCP/IP port numbers] (OpenVMS)
RFC1006 listener ipaddresses [set of IP Addresses] (OpenVMS)
Refer to attribute descriptions for specific command examples.
Select application to view the settable attributes
of an osi transport application, or select template to display the
settable attributes of an osi transport template.
17.1 – cltp nsap selector (Tru64 UNIX)
Default: 0 Value: 0-255 (except 32)
The NSAP selector to use for CLTS when running over CLNS. If the
value is 0 or 1, a single NSAP is shared between the Connection-
Oriented Transport Service (COTS), and the connectionless
transport protocol according to the osi transport attribute nsap
selector. If both nsap selectors are 0 or 1, then COTS and CLTS
over CLNS are disabled.
This attribute cannot be set either to 32, which is the value
of the NSP NSAP selector, or to the current setting of the osi
transport attribute, nsap selector, if the attribute has a value
other than 0 or 1.
This attribute cannot be modified when transport is enabled.
17.2 – congestion_avoidance
Default: False Value: True or false
Enables the use of the automatic congestion avoidance mechanism
to reduce the transport window size in response to an indication
from the Network layer when operating on the Connectionless
Network Service (CLNS).
set [node node-id] osi transport congestion avoidance boolean
Example:
set osi transport congestion avoidance false
17.3 – cons_filters
Default: { } Value: Set of simple names
The names of X.25 Access module filters used to determine which
inbound network connection requests should be directed to the
transport entity.
On OpenVMS Modification of this attribute while OSI transport is
enabled is permitted only with the add command. The set and
remove commands can only be used to modify this attribute when the
OSI transport is disabled.
For each cons filter, there must be a corresponding x25 access
template with the same name. One or more of these filters must be
specified in order to run COTS over CONS. The X.25 access filter
osi transport is typically used. See X.25/CONS Configuration for
more information.
set osi transport cons filters {simplename[,simplename...]}
Example:
set osi transport cons filters {"OSI Transport"}
17.4 – cons_nsap_addresses
Default: { } Value: Set of NSAP addresses
The set of valid NSAP addresses for use with CONS. One or more
NSAPs must be specified to run COTS over CONS. See the DECnet-Plus
for Tru64 UNIX Programming manual for more information.
set osi transport cons nsap addresses {nsap[,nsap...]}
17.5 – delay_factor
Default: 4 Value: 2-15
Factor by which to multiply the current value of the round-trip
delay estimate status attribute in order to set a value for the
retransmission timer. This attribute works with protocol class 4
only.
set [node node-id] osi transport delay factor integer
Example:
set osi transport delay factor 4
17.6 – delay_weight
Default: 5 Value: 0-255
Relative weighting to apply to the current estimate and to a new
sample when estimating round-trip delay. This attribute works
with protocol class 4 only.
set [node node-id] osi transport delay weight integer
Example:
set osi transport delay weight 5
17.7 – disconnect_holdback
Default: 0 Tru64 UNIX Value: 0-(2 raised to
the power of 31 -1)
OpenVMS Default: 0 OpenVMS Value: 0-4294967295
When operating over the Connection-Oriented Network Service
(CONS), the length of the time to maintain a network connection
for possible reuse after all transport connections multiplexed
upon it have been disconnected. Specified in seconds. This
characteristic may not be changed while the transport entity
is enabled. See X.25/CONS Configuration for more information.
set [node node-id] osi transport disconnect holdback integer
Example:
set osi transport disconnect holdback 0
17.8 – maximum cltp ports (Tru64 UNIX)
Default: 128 Value: 0-(2 raised to the power of 32 -1)
Maximum number of CLTS ports at one time. This characteristic can
only be increased while transport is enabled. You can modify this
characteristic to a lower value only when the entity is disabled.
17.9 – maximum listeners (Tru64 UNIX)
Default: 32 Value: 1-65535
Maximum number of listeners at one time. This characteristic can
only be increased while transport is enabled. You can modify this
characteristic to a lower value only when the entity is disabled.
17.10 – maximum_multiplexing
Tru64 UNIX Default: 1023 Tru64 UNIX Value: 1-1023
OpenVMS Default: 4294967295 OpenVMS Value: 1-4294967295
When operating over the Connection-Oriented Network Service
(CONS), the maximum number of transport connections that can be
multiplexed on any single network connection. This characteristic
can be increased only when the transport entity is enabled.
You can modify this characteristic to a lower value only when
the entity is disabled. See X.25/CONS Configuration for more
information.
set [node node-id] osi transport maximum multiplexing integer
Example:
set osi transport maximum multiplexing 4294967295
17.11 – maximum_network_connections
Tru64 UNIX Default: 1023 Tru64 UNIX Value: 0-1023
OpenVMS Default: 4294967295 OpenVMS Value: 0-4294967295
When operating over the Connection-Oriented Network Service
(CONS), the maximum number of network connections which can be
in use concurrently by DNA OSI Transport. This characteristic
can be incresed only when the transport entity is enabled.
See X.25/CONS Configuration for more information.
set [node node-id] osi transport -
maximum network connections integer
Example:
set osi transport maximum network connections 4294967295
17.12 – maximum receive buffers (OpenVMS)
Default: 2000 Value: 1-4294967295
Maximum number of receive buffers that can store received
DT transport PDUs. You can modify this characteristic only
when the entity is disabled. Also, you can only increase the
characteristic value.
set [node node-id] osi transport maximum receive buffers integer
Example:
set osi transport maximum receive buffers 2000
17.13 – maximum_remote_nsaps
Tru64 UNIX Default: 160 Tru64 UNIX Value: 1-65536
OpenVMS Default: 201 OpenVMS Value: 0-4294967295
Maximum number of remote NSAPs that can exist concurrently. This
value must be greater than the current value of maximum transport
connections. You can modify this characteristic to a lower value
only when the entity is disabled. This characteristic can be
increased when enabled.
set [node node-id] osi transport maximum remote nsaps integer
Example:
set osi transport maximum remote nsaps 201
17.14 – maximum_transport_connections
Tru64 UNIX Default: 128 Tru64 UNIX Value: 0-1023
OpenVMS Default: 200 OpenVMS Value: 0-4294967295
Maximum number of active transport connections allowed at one
time. Must be less than the current value of maximum remote
nsaps. You can modify this characteristic to a lower value only
when the entity is disabled.
set [node node-id] osi transport -
maximum transport connections integer
Example:
set osi transport maximum transport connections 200
17.15 – maximum_window
Tru64 UNIX Default: 20 Tru64 UNIX Value: 1-65535
OpenVMS Default: 8 OpenVMS Value: 1-65535
Maximum credit window that can be granted on a transport
connection. This is used for control of the number of data
segments (PDUs) allowed to be transmitted over a particular
transport connection before at least one acknowledgment must
be returned from the destination system. If the number of
PDUs already transmitted equals the maximum window and no
corresponding acknowledgments have been received, transport
stops sending PDUs over the transport connection and waits for
an acknowledgment message. You can modify this characteristic to
a lower value only when the entity is disabled.
set [node node-id] osi transport maximum window integer
Example:
set osi transport maximum window 20
17.16 – nsap_selector
Default: 33 Value: 0-255 (except 32)
The NSAP selector to use for the Connection-Oriented Transport
Service (COTS) when running over CLNS. If 0 or 1, COTS over CLNS
is not enabled. This attribute cannot be set to 32, which is the
value of the NSP NSAP selector. Or, on Tru64 UNIX, to the current
setting of the osi transport attribute cltp nsap selector if it
is other than 0 or 1.
This attribute cannot be modified when transport is enabled.
set [node node-id] osi transport nsap selector integer
Example:
set osi transport nsap selector 33
17.17 – RFC1006 listener ports (OpenVMS)
Default: { 102, 399 } Value: Set of TCP/IP port numbers
The names of the TCP listener ports used to receive inbound
RFC1006 connection requests. This is applicable for both RFC1006
and RFC1859.
Modification of this attribute while OSI transport is enabled is
permitted only with the add command. The set and remove commands
can only be used to modify this attribute when the OSI transport
is disabled.
set [node node-id] osi transport -
rfc1006 listener ports {port[,port...]}
Example:
set osi transport rfc1006 listener ports {102, 399}
See HELP NETWORK_MANAGEMENT RUNNING_OVER_TCP-IP for more information.
17.18 – RFC1006 listener ipaddresses (OpenVMS)
Default: { 0.0.0.0 } Value: Set of IP Addresses
The names of the listener IP addresses used to receive inbound
RFC1006 connection requests. This is applicable for both RFC1006
and RFC1859.
Modification of this attribute while OSI transport is enabled is
permitted only with the add command. The set and remove commands
can only be used to modify this attribute when the OSI transport
is disabled.
set [node node-id] osi transport -
rfc1006 listener ipaddresses {ipaddr[,ipaddr...]}
Example:
set osi transport rfc1006 listener ipaddresses {a.b.c.d,w.x.y.z}
See HELP NETWORK_MANAGEMENT RUNNING_OVER_TCP-IP for more information.
17.19 – application (OpenVMS)
set [node node-id] osi transport application application-name ...
Modifies attributes of the OSI transport application entity. The
modifiable attributes and their data types [in brackets] are:
called tsels [hex-string]
file name [filename]
user name [latin1string]
Refer to attribute descriptions for specific command examples.
17.19.1 – called_tsels
Default: No tsap Value: Hex-string
Transport Service Access Point (TSAP) for which the image
specified by the image name characteristic accepts connections.
This characteristic, which is similar to the addresses
characteristic, is used by applications that do not use the DNA
session control protocol (for example, VOTS applications).
set [node node-id] osi transport application application-name -
called tsels {hex-string}
Example:
set osi transport application osit$ivp -
called tsels {%x564F5453495650}
17.19.2 – file_name
Default: No file name Value: Filename
File 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.
set [node node-id] osi transport application application-name -
file name filename
Example:
set osi transport application osit$ivp -
file name sys$test:osit$ivpresp.com
17.19.3 – user_name
Default: No user name Value: Latin1string
User name portion of the access control information that
identifies the account under which the application is to run. If
invalid information or no user name is specified, system defaults
are used to select the user. On OpenVMS, the user name must be
embedded in quotes.
set [node node-id] osi transport application application-name -
user name latin1string
Example:
set osi transport application osit$ivp -
user name "systest"
17.20 – template
set [node node-id] osi transport template template-id ...
Modifies the attributes of an osi transport template entity. The
modifiable attributes and their data types [in brackets] are:
acknowledge delay time [seconds]
checksums [boolean]
classes [set-of-classes]
clns inactive area address [area-address] (OpenVMS)
cons template [simple-name]
cr timeout [seconds]
er timeout [seconds]
expedited data [boolean]
extended format [boolean]
inbound [boolean] (OpenVMS)
initial retransmit time [seconds]
keepalive time [seconds]
local nsap [nsap-address]
loopback [boolean] (OpenVMS)
maximum nsdu size [integer]
network priority [integer] (OpenVMS)
network service [service-type]
retransmit threshold [integer]
RFC1006 port number [integer] (OpenVMS)
security [octet-string]
send preferred maximum tpdu size [boolean]
send request acknowledgment [boolean]
send implementation id [boolean]
use clns error reports [boolean]
Refer to attribute descriptions for specific command examples.
17.20.1 – acknowledgment_delay_time
Default: 1 Value: 0-65
Maximum amount of time, in seconds, that an AK TPDU is to be
withheld. This attribute is valid for protocol class 4 only.
set [node node-id] osi transport template template-id -
acknowledgment delay time integer
Example:
set osi transport template default acknowledgment delay time 1
17.20.2 – checksums
Default: False Value: True or false
Specifies whether the use of checksums should be negotiated for a
transport connection. This attribute is valid for protocol class
4 only.
set [node node-id] osi transport template template-id -
checksums boolean
Example:
set osi transport template default checksums false
17.20.3 – classes
Default: {4} Value: Bit-set
Set of protocol classes that can be negotiated for use on a
transport connection. If the value of the network service
attribute is CLNS, the class must be a subset of the classes
supported by the OSI transport attribute clns classes supported.
If the value is CONS, the classes must be a subset of the
classes supported by the OSI transport attribute cons classes
supported. If the value of the network service attribute is ANY,
the classes must be a subset of the combined classes in the clns
classes supported and cons classes supported attributes.
set [node node-id] osi transport template template-id -
classes {class[,class...]}
Example:
set osi transport template osit$loop_cons classes {0,2,4}
17.20.4 – clns inactive area address (OpenVMS)
Default: Empty set Value: Set of area-address
Specifies the inactive area address to be used by transport
connections that use this template. This characteristic is
relevant only for connections that use CLNS with Null Internet.
The set must contain no more than one area address.
set [node node-id] osi transport template template-id -
clns inactive area address {area-address}
17.20.5 – cons_template
Default: OSI Transport Value: Simple-name
Name of the X.25 Access module template to be used when
establishing a network connection over the CONS. Used only when
the value of the network service attribute is cons.
set [node node-id] osi transport template template-id -
cons template simplename
Example:
set osi transport template osit$loop_cons -
cons template "OSI Transport"
17.20.6 – cr_timeout
Default: 30 Value for Tru64 UNIX: 1-(2 raised to the
power of 31 -1)
Default: 30 Value for OpenVMS: 1-4294967295
During connection establishment, the amount of time (in seconds)
to wait for a response to a CR TPDU before assuming that
the remote transport service provider will not respond. This
attribute is valid for protocol classes 0 and 2 only.
set [node node-id] osi transport template template-id -
cr timeout integer
Example:
set osi transport template osit$loop_cons -
cr timeout 30
17.20.7 – er_timeout
Default: 30 Value for Tru64 UNIX: 1-(2 raised to the
power of 31 -1)
Default: 30 Value for OpenVMS: 1-4294967295
The amount of time (in seconds) to wait for a response to an ER
TPDU before disconnecting the network connection. This attribute
is used for protocol classes 0 and 2 only.
set [node node-id] osi transport template template-id -
er timeout integer
Example:
set osi transport template osit$loop_cons -
er timeout 30
17.20.8 – expedited_data
Default: True Value: True or false
Specifies whether use of the expedited data option should be
negotiated for the transport connections. This attribute is not
valid for protocol class 0.
set [node node-id] osi transport template template-id -
expedited data boolean
Example:
set osi transport template osit$loop_clns -
expedited data true
17.20.9 – extended_format
Default: None Value: True or false
Specifies whether the use of extended TPDU format should be
negotiated for the transport connections. Normal format gives
7-bit sequence numbers and 4-bit credit fields; extended format
gives 31-bit sequence numbers and 16-bit credit fields. This
attribute is supported only for class 2 and class 4 protocols.
set [node node-id] osi transport template template-id -
extended format boolean
Example:
set osi transport template osit$loop_clns -
extended format true
17.20.10 – inbound (OpenVMS)
Default: True Value: True or false
Indicates whether this template may be used as the template for
an inbound transport connection. The algorithm of selection
of the inbound template is different depending on the type of
network service over which the transport connection is made.
If an inbound template cannot be found for an inbound transport
connection, then the template called DEFAULT will be selected as
the default. For the CLNS network service, the inbound template
selected is the first template found that has the Inbound
attribute set to true, the Network Service attribute set to
CLNS, and the CLNS Inactive Area Address attribute set to empty
set.
For the CLNS network service (using the inactive subset, that
is, null internet), the incoming template selected is the first
template found that has the Inbound attribute set to True, the
Network Service attribute set to CLNS and the CLNS Inactive Area
Address attribute matches the Inactive Area Address attribute
of the Routing Circuit entity that the transport connection
is using. For the CONS network service, the inbound template
selected is the first template found that has the inbound
attribute set to true, the network service attribute set to CONS
and the CONS template attribute (that is, an X.25 Access template
name) matches the name of the X.25 Access filter that was used to
accept the inbound network connection.
set [node node-id] osi transport template template-id -
inbound boolean
Example:
set osi transport template osit$rfc1006 -
inbound true
17.20.11 – initial_retransmit_time
Tru64 UNIX Default: 5 Tru64 UNIX Value: 1-(2 raised to the
power of 31 -1)
OpenVMS Default: 5 OpenVMS Value: 1-4294967295
Amount of time, in seconds, to wait for an acknowledgment before
retransmitting the first TPDU over the transport connection.
set [node node-id] osi transport template template-id -
initial retransmit time integer
Example:
set osi transport template osit$loop_clns -
initial retransmit time 5
17.20.12 – keepalive_time
Default: 60 Value: 1-16383
Time (in seconds) to be used for the window timer. When the
transport service provider has no TPDUs to send over a transport
connection, it retransmits the last AK TPDU at the specified
frequency to prevent expiration of the remote NSAP's inactivity
timer. This attribute is valid for protocol class 4 only.
set [node node-id] osi transport template template-id -
keepalive time integer
Example:
set osi transport template osit$loop_clns -
keepalive time 60
17.20.13 – local_nsap
Default: System dependent, determined Value: NSAP address
at run-time
A local NSAP address to be used by default if one is not supplied
across the service interface.
set [node node-id] osi transport template template-id -
local nsap nsap-address
17.20.14 – loopback (OpenVMS)
Default: False Value: True or false
Specifies whether transport connections using this template are
looped back locally in the transport layer.
set [node node-id] osi transport template template-id -
loopback boolean
Example:
set osi transport template osit$loop_clns -
loopback true
17.20.15 – maximum_nsdu_size
Default: 2048 Value for Tru64 UNIX: 128-(2 raised to the
power of 32 -1)
Default: 2048 Value for OpenVMS: 2048
When operating over the CONS, the maximum NSDU size to use for
transmit and receive buffers. Expressed as a number of octets.
set [node node-id] osi transport template template-id -
maximum ndsu size integer
Example:
set osi transport template osit$loop_clns -
maximum ndsu size 2048
17.20.16 – network priority (OpenVMS)
Default: 0 Value: 0-255
When operating over CLNS, indicates network priority encoded in
NPDU header for all transmitted packets. It may be used by
intermediate systems to assign the packets to queues of
appropriate priority.
set [node node-id] osi transport template template-id -
network priority integer
Example:
set osi transport template osit$loop_clns -
network priority 0
17.20.17 – network_service
Default: clns Value: Any, clns, cons, or RFC1006
(OpenVMS)
Type of network service. On Tru64 UNIX, the default template
network service cannot be set to any. The network service
chosen must be compatible with the value of the protocol class
attribute.
any Either
clns Connectionless Network Service
cons Connection-Oriented Network Service
RFC1006 ISO Transport Service on top of TCP
set [node node-id] osi transport template template-id -
network service service-type
Examples:
set osi transport template osit$rfc1006 - ! OSI over TCP/IP
network service rfc1006 ! RFC1006
set osi transport template osit$rfc1006plus - ! DECnet over TCP/IP
network service rfc1006 ! RFC1859 a.k.a.
! RFC1006+
17.20.18 – retransmit_threshold
Default: 8 Value: 0-4294967295
Number of times a TPDU requiring acknowledgment is to be
retransmitted before it is assumed that network connectivity
has failed. This attribute is valid for protocol class 4 only.
set [node node-id] osi transport template template-id -
retransmit threshold integer
Example:
set osi transport template osit$loop_clns -
retransmit threshold 8
17.20.19 – RFC1006 port number (OpenVMS)
Default: 102 Value: TCP port number
Specifies the TCP port number to use. Only applicable if the
network service is RFC1006.
set [node node-id] osi transport template template-id -
rfc1006 port number port-id
Examples:
set osi transport template osit$rfc1006 - ! OSI over TCP/IP
rfc1006 port number 102 ! RFC1006
set osi transport template osit$rfc1006plus - ! DECnet over TCP/IP
rfc1006 port number 399 ! RFC1859 a.k.a.
! RFC1006+
17.20.20 – security
Default: Null value Value: 00-FF
An octet string to be transmitted in the security parameter of
a CR or CC TPDU. A null value causes the security parameter to
be omitted from the TPDU.
set [node node-id] osi transport template template-id -
security octet-string
Example:
set osi transport template default security %xFF
17.20.21 – send_implementation_id
Default: True Value: True or false
Indicates whether the implementation id should be sent in the CR if
the proposed protocol class is 2 or 4. It is always returned in the
CC if it is present in the CR.
set [node node-id] osi transport template template-id -
send implementation id boolean
Example:
set osi trans temp default send imp id true
17.20.22 – send preferred maximum TPDU size
Default: True Value: True or false
Indicates whether the preferred maximum TPDU size parameter should
be sent in the CR TPDU.
If the preferred maximum TPDU size parameter was present in the
CR TPDU, then it indicates whether the preferred maximum TPDU
size parameter should be sent in the CC TPDU.
NOTE
The default value of this characteristic should not be changed
unless the remote implementation does not conform to ISO 8073.
set [node node-id] osi transport template template-id -
send preferred maximum tpdu size boolean
Example:
set osi trans temp default send pref max tpdu size true
17.20.23 – send_request_acknowledgment
Default: True Value: True or false
Indicates whether the request acknowledgment parameter should be
sent in the CR TPDU.
If the request acknowledgment parameter was present in the CR TPDU,
then it indicates whether the request acknowledgment parameter
should be sent in the CC TPDU.
NOTE
The default of this characteristic should not be changed unless the
remote implementation does not conform to ISO 8073.
set [node node-id] osi transport template template-id -
send request acknowledgement boolean
Example:
set osi trans temp default send req ack true
17.20.24 – use_clns_error_reports
Default: False Value: True or false
Indicates whether the network Routing layer's error report
facility should be used when performing connection establishment.
If set to true, this may result in faster detection of an
unreachable node at the time of connection establishment. This
characteristic should not be set to true on an end system that
is either dual-railed or connected to a network that has a high
probability of duplication. This is valid only if network service
equals clns.
set [node node-id] osi transport template template-id -
use clns error reports boolean
Example:
set osi trans temp osit$loop_clns use clns err rep true
18 – routing
set [node node-id] routing ...
Modifies attributes of the routing entity. Support for the
various attributes depends upon the routing type of the
node (End, L1, L2, IP). The modifiable routing attributes
and their data types [in brackets] are:
area authentication type [none or simple]
area receive passwords [set of hex-string]
area send password [hex-string]
autonomous system number [integer]
dna address format [boolean]
default eshello timer [integer]
domain authentication type [none or simple]
domain receive passwords [set of hex-string]
domain send password [hex-string]
generate checksums [boolean]
lifetime [integer]
manual area addresses [set of area addresses]
manual L1 algorithm [string]
manual L2 algorithm [string]
manual network entity titles [set of NETs]
maximum buffers [integer]
maximum path splits [integer]
phaseiv address [ph4-address]
phaseiv prefix [address-prefix]
phaseiv area maximum cost [integer]
phaseiv area maximum hops [integer]
phaseiv broadcast routing timer [integer]
phaseiv buffer size [integer]
phaseiv maximum address [integer]
phaseiv maximum area [integer]
phaseiv maximum cost [integer]
phaseiv maximum hops [integer]
phaseiv maximum visits [integer]
probe rate [integer]
protocols [IP or ISO 8473]
redirect holding time [integer]
routing mode [integrated or segregated]
segment buffer size [integer]
send source quench [boolean]
source quench interval [boolean]
summary addresses [set of summary-address]
time to live [integer]
Refer to the specific attributes for more information.
Select circuit to view the modifiable attributes of a routing
circuit, a routing circuit ip reachable address, or a routing
circuit reachable address.
Select egp_group to view the modifiable attributes of a
routing egp group.
Select permitted_neighbor for information on modifying the
verifier attribute of a routing permitted neighbor.
18.1 – area_authentication_type
Support: L1,IP
Default: None Value: None or simple
Type of authentication to be used for level 1 LSPs, PSNPs, and
CSNPs.
18.2 – area_receive_passwords
Support: L1,IP
Default: No passwords Value: Set of hex-string
Set of passwords that are valid in level 1 LSPs, PSNPs, and CSNPs
when simple authentication is in use. You cannot use the show
command to display the value of this attribute.
18.3 – area_send_password
Support: L1,IP
Default: No password Value: Hex-string
Password to be sent in level 1 LSPs, PSNPs, and CSNPs when simple
authentication is in use. You cannot use the show command to
display the value of this attribute.
18.4 – autonomous_system_number
Support: IP
Default: 0 Value: 0-65535
Autonomous system number of the local system. This characteristic
is supported only if the value of the routing protocols supported
characteristic includes EGP. You can modify this characteristic
only when the status attribute routing state is off.
18.5 – dna_address_format
Support: End
Default: True Value: True or false
If true, specifies that NSAP addresses are DNA structured, and
that NSAP address autoconfiguring is possible. If false, this
specifies that NSAP addresses for this node are constructed
from the characteristic manual network entity titles and the
selectors supplied by the transport protocol module (NSP and/or
OSI transport).
The DNA address format attribute controls only the interpretation
of address structuring and no longer controls autoconfiguration.
To control autoconfiguration, you need to use the manual network
entity titles attribute by manually adding or removing NETs.
set [node node-id] routing dna address format boolean
Example:
set routing dna address format true
18.6 – default_eshello_timer
Default: 600 Value: 1-65535
Value to be used for current suggested hello timer in the absence
of any suggested values from the IS.
set [node node-id] routing default eshello timer integer
Example:
set routing default eshello timer 600
18.7 – domain_authentication_type
Support: L2,IP
Default: None Value: None or simple
Type of authentication to be used for level 2 LSPs, PSNPs, and
CSNPs.
18.8 – domain_receive_passwords
Support: L2,IP
Default: No passwords Value: Set of hex-string
Set of passwords that are valid in level 2 LSPs, PSNPs, and CSNPs
when simple authentication is in use. You cannot use the show
command to display the value of this attribute.
18.9 – domain_send_password
Support: L2,IP
Default: No password Value: Hex-string
Password to be sent in level 2 LSPs, PSNPs, and CSNPs when simple
authentication is in use. You cannot use the show command to
display the value of this attribute.
18.10 – generate_checksums
Support: All
Default: False Value: True or false
If true, specifies that checksums are generated for data, error
report, and ES-IS PDUs initiated by this node. If false, these
checksums are not generated. It is strongly recommended that,
for performance reasons, you use the default value (indicating no
checksum generation).
18.11 – lifetime
Support: All
Default: 63 Value: 2-255
Value to be placed in the "lifetime" field of originating data
packets. This value should be greater than the maximum number of
hops in any path in the network, plus the maximum packet lifetime
in half-seconds.
18.12 – manual_area_addresses
Support: L1,L2
Default: No area Value: Set of area addresses
addresses
Area addresses to be used for this node. An area address cannot
be a Phase IV address or the address DefaultArea.
If the characteristic manual L1 algorithm has the value routing
vector, this set must be empty, and the characteristic phase iv
address must not be 0.0. If the characteristic phase iv address
is 0.0, there must be at least one area address.
18.13 – manual L1 algorithm
Support: L1
Default: Routing Value: See description
vector
Type of routing algorithm to be used within the area. You can
modify this characteristic only when the entity is disabled.
link state The DECnet-Plus link-state algorithm is used.
routing The Phase IV routing-vector algorithm is used.
vector
18.14 – manual L2 algorithm
Support: L2
Default: Routing Value: See description
vector
Type of routing algorithm to be used at level 2. You can modify
this characteristic only when the entity is disabled.
link state The DECnet-Plus link-state algorithm is used.
routing The Phase IV routing-vector algorithm is used.
vector
18.15 – manual_network_entity_titles
Support: End
Default: No NETs Value: Set of NETs
Network entity titles (NETs) to be used for this node. If the
characteristic dna address format is set to false, there must be
at least one NET.
set [node node-id] routing manual network entity titles {NET[,NET...]}
Example:
set routing manual network entity titles -
{49::00-04:AA-00-04-00-45-13:00}
18.16 – maximum_buffers
Default: 100 Value: 0-65535
Specifies the guaranteed number of buffers for forwarding. More
buffers may be used if they are available. You can only increase
the characteristic value.
18.17 – maximum_path_splits
Support: L1,L2
Default: 2 Value: 1-32
Maximum number of equal cost paths to split traffic between. You
can modify this characteristic only when the entity is disabled.
18.18 – phaseiv_address
Support: All
Default: 0.0 Value: PhaseIV address
Specifies a Phase IV compatible address for communication with
other Phase IV nodes. The default address, 0.0, indicates that
no Phase IV compatible address is provided for the node. You can
modify this characteristic only when the entity is disabled.
set [node node-id] routing phaseiv address phiv-address
Example:
set routing phaseiv address = 4.863
18.19 – phaseiv_area_maximum_cost
Support: L2
Default: 1022 Value: 1-1022
Maximum cost of a path to a reachable Phase IV area. This
characteristic is only used by the Phase IV routing algorithm
(that is, the routing-vector algorithm).
18.20 – phaseiv_area_maximum_hops
Support: L2
Default: 30 Value: 1-30
Maximum number of hops in a path to a reachable Phase IV
area. This characteristic is only used by the Phase IV routing
algorithm (that is, the routing-vector algorithm).
18.21 – phaseiv_broadcast_routing_timer
Support: L1,L2
Default: 10 Value: 1-65535
Maximum interval, in seconds, between broadcast routing messages
on broadcast circuits. This characteristic is only used by
the Phase IV routing algorithm (that is, the routing-vector
algorithm).
18.22 – phaseiv_buffer_size
Support: All
Default: 576 Value: 1-65535
Size, in octets, of buffers used for routing to adjacent Phase IV
nodes. This value is actually six octets greater than the maximum
buffer size, and does not include the headers for the Routing and
Data Link layers.
18.23 – phaseiv_maximum_address
Support: L1,L2
Default: 1023 Value: 1-1023
Maximum node number within the Phase IV area. This characteristic
is only used by the Phase IV routing algorithm (that is, the
routing-vector algorithm).
18.24 – phaseiv_maximum_area
Support: L2
Default: 63 Value: 1-63
Maximum Phase IV area number. This characteristic is only used
by the Phase IV routing algorithm (that is, the routing-vector
algorithm).
18.25 – phaseiv_maximum_cost
Support: L1,L2
Default: 1022 Value: 1-1022
Maximum cost of a path to a reachable node within the Phase IV
area. This characteristic is only used by the Phase IV routing
algorithm (that is, the routing-vector algorithm).
18.26 – phaseiv_maximum_hops
Support: L1,L2
Default: 30 Value: 1-30
Maximum number of hops in a path to a reachable node within the
Phase IV area. This characteristic is only used by the Phase IV
routing algorithm (that is, the routing-vector algorithm).
18.27 – phaseiv_maximum_visits
Support: All
Default: 63 Value: 1-63
Maximum number of visits that a packet can make to this node
before Routing assumes that the packet is looping. This
characteristic is only used by the Phase IV routing algorithm
(that is, the routing-vector algorithm).
18.28 – phaseiv_prefix
Support: All
Default: Hex 49 Value: Address prefix
Prefix for Phase IV addresses. If the characteristic phase iv
address is not 0.0, a DECnet area address is formed by adding
the area portion of the Phase IV address to this prefix.
You can modify this characteristic only when the entity is
disabled.
set [node node-id] routing phaseiv prefix address-prefix
Example:
set routing phaseiv prefix = 49::
18.29 – probe_rate
Support: End
Default: 20 Value for Tru64 UNIX: 10-1000
Default: 20 Value for OpenVMS: 1-65535
Number of packets after which a probe is sent. This
characteristic is used only on multilink end systems, on
circuits without cache entries for the destination.
18.30 – protocols
Support: IP Value: IP or ISO8473
The protocol stacks that are enabled on this system. These
can be either or both of the above values. The value of this
characteristic derives from an argument to the create command.
You cannot modify this characteristic.
18.31 – redirect_holding_time
Support: L1,L2
Default: 600 Value: 1-65535
Holding time, in seconds, to be specified in Redirect PDUs
generated by this node.
18.32 – rip_receive_metric_class
Support: L2,IP
Default: External Value: External or Internal
The class to be associated with routes received through RIP.
This value may be overridden by a routing receive route entity.
This characteristic is supported only if the routing protocols
supported characteristic includes the RIP routing protocol.
18.33 – rip_send_local_metric
Support: L2,IP
Default: 1 Value: 0-16
The metric value used by RIP when announcing routes derived from
local information. This value is used unless it is overridden by
a routing send route entity. This characteristic is supported
only if the routing protocols supported characteristic includes
the RIP routing protocol.
18.34 – rip_send_metric_classes
Support: L2,IP
Default: Internal Value: Set of external, internal
Routes received through routing protocols other than RIP with metric
classes in this set are candidates for announcement in RIP messages
subject to the route propagation policy in force. Routes with metric
classes not in this set will not be announced. Each value in this
set may be overridden separately by a more specific propagation
policy specified by a routing send route or routing send route route
source entity. This characteristic is supported only if the routing
protocols supported characteristic includes the RIP routing protocol.
18.35 – rip_send_replacement_metric
Support: L2,IP
Default: 1 Value: 0-16
The metric value used by RIP when announcing routes derived through
other routing protocols. This value is used unless it is overridden
by a routing send route entity. This characteristic is supported
only if the routing protocols supported characteristic includes the
RIP routing protocol.
18.36 – route_propagation
Support: L2,IP
Default: No Route Propagation Value: Set of protocol pairs
The default route propagation to be performed. The set may include
the following protocol pairs:
EGP to IS-IS IS-IS to RIP
EGP to RIP RIP to EGP
IS-IS to EGP
If a particular value is not present in the set, routes are not
propagated between those two protocols in that direction. This
characteristic is supported only if the routing protocols
supported characteristic includes either of the EGP or RIP
routing protocols.
18.37 – routing_mode
Support: End
Default: Integrated (OpenVMS) Value: Segregated or
Segregated (Tru64 UNIX) Integrated
Determines the behavior of the forwarding algorithm. When the
routing mode is set to Segregated, data being transmitted to
Phase IV destination addresses is sent in Phase IV format packets,
to the adjacent Phase IV router, if available. In Integrated mode,
data is sent to Phase V (OSI) router adjacencies in CLNP packets,
if possible.
This characteristic can only be set when Routing is disabled.
For example, to switch to segregated mode from the default:
NCL> disable routing
NCL> set routing routing mode = segregated
NCL> enable routing
NCL> enable routing circuit *
18.38 – routing_protocols_supported
Support: L2,IP
The set of routing protocols supported by this implementation. You
cannot modify this characteristic.
EGP
IS-IS
RIP
18.39 – segment_buffer_size
Support: All
Default: 570 Value: 0-65535
Maximum segment size, in octets, to be used by the Transport
layer. A value of zero means that the segment size is unlimited.
18.40 – send_source_quench
Support: L1,L2,IP
Default: False Value: True or false
Specifies whether an ICMP source quench packet is sent when an IP
packet is discarded because of congestion. If false, ICMP source
quench packets are never sent.
18.41 – source_quench_interval
Support: L1,L2,IP
Default: 100 Value: 1-65535
Minimum time, in milliseconds, between transmission of successive
ICMP source quench packets.
18.42 – summary_addresses
Support: L2,IP
Default: No addresses Value: Set of summary addresses
Summary address information to be included in level 2 link state
packets sent by this node.
18.43 – time_to_live
Support: IP
Default: 35 Value: 1-255
Specifies the value to be placed in the time to live field of
originating IP packets. This value should be greater than the
maximum number of hops in any path on the network.
18.44 – circuit
set [node node-id] routing circuit circuit-name ...
Modifies attributes of the routing entity which represents
a data link to another node. Support for the various attributes
depends upon the routing type of the node (End, L1, L2, IP).
The modifiable routing circuit attributes and their data types
[in brackets] are:
data link entity [local-entity-name]
dna neighbor [boolean]
enable phaseiv address [boolean]
explicit receive verification [boolean]
hello timer [integer]
idle timer [integer]
inactive area address [set]
initial minimum timer [integer]
isis hello timer [integer]
L1 cost [integer]
L1 router priority [integer]
L2 cost [integer]
L2 router priority [integer]
manual data link sdu size [integer]
manual L2only mode [boolean]
manual routers [set]
maximum call attempts [integer]
maximum svc adjacencies [integer]
originating queue limit [integer]
recall timer [integer]
receive verifier [hex-string]
reserved adjacency [boolean]
reserve timer [integer]
template [template-id]
transmit verifier [hex-string]
x.25 filters [set]
Select reachable_address to view the modifiable attributes of a
routing circuit reachable address subentity.
Selecte ip_reachable_address to view the modifiable attributes
of a routing circuit ip reachable address subentity.
18.44.1 – data_link_entity
Support: All
Default: No data link Value: Local-entity-name
Name of the entity within the data link module to be created when
a port is opened for that data link type. You can modify this
characteristic only when the entity is disabled. This attribute
is supported for all types of circuits, however for X.25 circuits
set the attribute to x25 access.
set [node node-id] routing circuit circuit-name -
data link entity [local entity name]
Examples:
set routing circuit csmacd-1 -
data link entity csma-cd station csmacd-1
set routing circuit x25_circuit-1 data link entity x25 access
18.44.2 – dna_neighbor
Support: L1,L2
Default: True Value: True or false
If true, specifies that the neighbor is expected to be DNA
compliant, and so proprietary mechanisms are possible. If
false, no router-to-router Hellos or LSPs will be sent over
this circuit. This characteristic is supported only if the
characteristic type is not x25 da. You can modify this
characteristic only when the entity is disabled.
18.44.3 – enable_phaseiv_address
Support: All
Default: True Value: True or false
Specifies whether the physical LAN address is to be set to the
Phase IV style LAN address (that is, AA-00-04-00-xx-xx). The
LAN address is set only if this attribute is true and the value
of the Phase IV Address characteristic is not 0.0. If Phase IV
Address is not 0.0 and there are multiple adaptors to the same
LAN, only one circuit may have this attribute set to true. This
characteristic is supported only if the characteristic type is
set to csma-cd.
set [node node-id] routing circuit circuit-name -
enable phaseiv address boolean
Example:
set routing circuit csmacd-1 enable phaseiv address true
18.44.4 – explicit_receive_verification
Support: All
Default: True Value: True or false
Type of password verification performed at circuit
initialization. If true, the received verifier is checked
against the value of the characteristic receive verifier for
this circuit, if any. If false, the received verifier is checked
against the set of verifiers specified in the routing permitted
neighbor entities. This attribute is supported only if the
characteristic type is set to ddcmp, hdlc, x25 static incoming,
x25 static outgoing, and x25 permanent.
18.44.5 – hello_timer
Support: L1,L2
Default: 10 Value: 1-32767
Interval, in seconds, between IS Hello messages.
18.44.6 – idle_timer
Support: All
Default: 30 Value: 1-65535
Number of seconds of idle time before a call is cleared. This
attribute is supported only if the characteristic type is x25 da.
18.44.7 – inactive_area_address
Support: All
Default: No area Value: Set of area addresses
address
Area address associated with the use of the inactive subnet of
ISO 8473. Maximum area address that may be present is 1. This
characterisitic is supported only if the characteristic type is
set to csma-cd.
set [node node-id] routing circuit circuit-name -
inactive area address {one_area_address}
Example:
set routing circuit csmacd-1 inactive area address {49::FF-00}
18.44.8 – initial_minimum_timer
Support: All
Default: 55 Value: 1-65535
Period, in seconds, for which an X.25 call remains connected
after being established, irrespective of traffic. This should be
set small enough that the call is cleared before the start of the
next charging interval. This attribute is supported only if the
characteristic type is x25 da.
18.44.9 – isis_hello_timer
Support: L1,L2
Default: 3 Value: 1-32767
Interval, in seconds, between LAN level 1 and level 2 router-to-
router Hello messages. This value is also used as the interval
between IS Hello messages when polling the ES configuration.
18.44.10 – L1 cost
Support: L1,L2
Default: 20 Value: 1-63
Cost of this circuit for level 1 traffic.
18.44.11 – L1 router priority
Support: L1,L2
Default: 64 Value: 1-127
Priority for becoming LAN level 1 designated router. This
attribute is supported only if the circuit's characteristic type
is csma-cd.
18.44.12 – L2 cost
Support: L2
Default: 20 Value: 1-63
Cost of this circuit for level 2 traffic.
18.44.13 – L2 router priority
Support: L2
Default: 64 Value: 1-127
Priority for becoming LAN level 2 designated router. This
attribute is supported only if the circuit's characteristic type
is csma-cd.
18.44.14 – manual_data_link_sdu_size
Support: All
Default: 1492 Value: 128-65535
Preferred maximum data-link block size, in octets. You can modify
this characteristic only when the entity is disabled. If the
characteristic type is csma-cd, this characteristic is a read-
only attribute whose value is fixed at 1492.
set [node node-id] routing circuit circuit-name -
manual data link sdu size
Example:
set routing circuit fddi-1 manual data link sdu size 4352
18.44.15 – manual L2only mode
Support: L2
Default: False Value: True or false
If true, specifies that this circuit is to be used only for level
2 traffic. If false, the circuit may be used for both level 1 and
level 2 traffic. You can modify this characteristic only when the
entity is disabled.
18.44.16 – manual_routers
Support: End
Default: No router Value: Set of LAN addresses
IDs
Manually entered IDs of routers. If this set is empty, the
circuit will auto-configure the routers. This characteristic is
supported only if the circuit's characteristic type is csma-cd.
For Tru64 UNIX, a maximum of 5 routers can be in the set.
set [node node-id] routing circuit circuit-name -
manual routers {address[,address...]}
Example:
set routing circuit csmacd-1 manual routers {aa-00-04-00-12-34}
18.44.17 – maximum_call_attempts
Support: All
Default: 10 Value: 0-255
Maximum number of successive X.25 call failures before the
circuit is regarded as being halted. A value of zero means that
there is no limit to the number of retries.
This attribute is supported only if the characteristic type is
set to x25 static outgoing. You can modify this characteristic
only when the entity is disabled. Also, you can only increase the
characteristic value.
18.44.18 – maximum_svc_adjacencies
Support: All
Default: 1 Value: 1-65535
Number of routing circuit adjacency entities to reserve for
SVCs on this circuit. This is effectively the maximum number
of simultaneous calls possible on this circuit. This attribute is
supported only if the characteristic type is x25 da.
18.44.19 – originating_queue_limit
Support: L1,L2
Default: 2 Value: 1-50
Maximum number of data PDUs originated by this node that can
be on this circuit's transmit queue. This should be set to the
minimum number required to keep the data link from idling. You
can modify this characteristic to a higher value when the entity
is disabled; you can never modify it to a lower value.
18.44.20 – recall_timer
Support: All
Default: 60 Value: 0-65535
Interval, in seconds, that must elapse between a call failure and
a recall. This attribute is supported only if the characteristic
type is set to x25 static outgoing, x25 da, hdlc, or ddcmp.
18.44.21 – receive_verifier
Support: All
Default: No verifier Value: Hex string, length 0-38
Value against which a neighbor node's received verifier is
to be checked. If no verifier is specified, no verification
is performed. This attribute is supported only if the
characteristic type is either ddcmp, hdlc, x25 static incoming,
x25 static outgoing, or x25 permanent. You cannot display this
characteristic.
18.44.22 – reserved_adjacency
Support: End
Default: False Value: True or false
If true, specifies that one SVC must be reserved for connection
to a router. If false, no SVC needs to be reserved for
this purpose. This characteristic is supported only if the
circuit's characteristic type is x25 da). You can modify this
characteristic only when the entity is disabled.
18.44.23 – reserve_timer
Support: All
Default: 600 Value: 1-65535
Interval, in seconds, during which the SVC remains reserved for
the previous DTE address after a call is cleared due to lack of
traffic. This attribute is supported only if the characteristic
type is x25 da.
18.44.24 – template
Support: All
Default: No template Value: Template-id
name
Name of the template to be used when a port is opened for this
data-link type. If no template name is specified, no template is
used. You can modify this characteristic only when the entity is
disabled.
18.44.25 – transmit_verifier
Support: All
Default: No verifier Value: Hex-string, length 0-38
Value to be transmitted for verifying the identity of this node.
If no verifier is specified, no verifier is transmitted. This
characteristic is supported only if the characteristic type is
either ddcmp, hdlc, x25 static outgoing, x25 static incoming, or
x25 permanent. You cannot display this characteristic.
18.44.26 – x.25_filters
Default: See Value: Set of simple names
description
Specifies the set of X.25 filters to be used when a port is
opened to the X.25 module. Typically, there will be two sets: one
to specify the selection on the Call User Data field for DECnet-Plus
and the other to specify the selection on the subaddress
for Phase IV. This attribute is valid only if the characteristic
type is x25 static incoming or x25 da.
18.44.27 – ip_reachable_address
Support: L2,IP
set [node node-id] routing circuit circuit-name
ip reachable address destination
18.44.28 – reachable_address
set [node node-id] routing circuit circuit-name -
reachable address simple-name ...
Modifies attributes of a routing circuit reachable address entity
which contains information about a manually entered address prefix
accessible over that circuit. It exists only on L2 routers and
end nodes. The modifiable routing circuit reachable address
attributes and their data types [in brackets] are:
block size [integer]
cost [integer]
data format [PhaseIV or Phasev]
DTE addresses [set of dte addresses]
ISDN address [isdn-address]
LAN address [id]
metric type [metric-type]
mapping [string]
modem addresses [modem-address]
modem address prefix [modem-address-prefix]
modem address suffix [modem-address-suffix]
permitted lan address [lan-address]
type [string]
18.44.28.1 – block_size
Support: End, type outbound
Default: 0 Value: 0-65536
The data link block size to be used for this prefix.
For an end system, the data link block size to be used for this
prefix. If the block size is set to the default, the manual
block size of the circuit will be used instead. This attribute
is supported only if the type characteristic is set to outbound.
set [node node-id] routing circuit circuit-name -
reachable address simplename block size integer
Example:
set routing circuit csmacd-1 -
reachable address to-area4 block size 500
18.44.28.2 – cost
Support: L2
Default: 20 Value: 1-63
Cost of reaching this address prefix over this circuit.
18.44.28.3 – data_format
Support: L2
Default: PhaseV Value: PhaseIV (1) or PhaseV (0)
The PDU data format to be used when forwarding data (or
error report) NPDUs using this reachable address.
This attribute is supported only if the type characteristic
is set to outbound. You can modify this characteristic only
when the entity is disabled.
18.44.28.4 – dte_addresses
Support: End,L2
Default: No DTE addresses={ } Value: Set of DTE addresses
A set of DTE addresses to which a call may be directed in order
to reach an address that matches the address prefix of this
reachable address.
This characteristic is supported if the node is a level 2 router,
where the owning circuit's characteristic type is one of the X.25
circuit types, and the reachable address's characteristic type
is outbound. It is also supported by end nodes operating over an
x25 da circuit. You can modify this characteristic only when the
entity is disabled.
set [node node-id] routing circuit circuit-name reachable -
address simplename dte address {dte-address[dte-address...]}
Example:
set routing circuit x25_circuit-1 reachable address ughh_v -
dte address { 2267643 }
18.44.28.5 – ISDN address
Support: L1,L2
Default: { } Value: Set of ISDN addresses
A full set of E.164 ISDN network addresses that a call may be
directed in order to reach a network number that matches the
address prefix of the parent reachable address entity. Associated
with each ISDN network address, but not visible to Network
Management, is a variable last failure of type binary absolute
time. This attribute is supported only if access type is ISDN DA.
18.44.28.6 – LAN address
Support: L2,End
Default: 00-00-00-00-00-00 Value: ID
A single LAN address to which an NPDU can be directed in order
to reach an address that matches the address prefix of the parent
reachable address entity. This attribute is supported only if the
type characteristic is set to outbound on broadcast circuits only.
A valid address is required here.
You can modify this characteristic only when the entity is
disabled.
set [node node-id] routing circuit circuit-name reachable -
address simplename lan address aa-00-04-00-xx-xx
Example:
set routing circuit csmacd-1 reachable address to-area4 -
lan address aa-00-04-00-12-34
18.44.28.7 – mapping
Support: End,L2
Default: X.121 Value: Manual or X.121
Type of mapping used to determine the SNPA address to which a
call should be placed for this address prefix. You can modify
this characteristic only when the entity is disabled. If the
circuit is a broadcast circuit, this attribute must have the
value manual.
manual The mapping uses the set of addresses in the
characteristic dte addresses or the address in the
characteristic LAN address.
X.121 The mapping uses the X.121 address extraction algorithm.
This characteristic is supported only if either of the following
conditions is satisfied:
o The node is a level 2 router or an end node, and the owning
circuit's characteristic type is one of the X.25 circuit
types; or
o The node is a level 2 router, the owning circuit's
characteristic type is csma-cd, and the reachable address's
characteristic type is outbound.
set [node node-id] routing circuit circuit-name reachable -
address simplename mapping manual_or_x.121
Example:
set routing circuit csmacd-1 reachable address to-area4 -
mapping manual
18.44.28.8 – metric_type
Support: L2
Default: Internal Value: Internal, external
The metric type of the cost metric for the circuits. If internal,
the I/E bit for the metric in the Prefix Neighbors option of
L2 LSPs is set to 0, otherwise (external) is set to 1.
18.44.28.9 – modem_addresses
Support: L1,L2
Default: { } Value: Set of modem addresses
A set of full dial sequence that contains the address (PSTN or
ISDN) to which a call may be directed in order to reach a
network number that matches the address prefix of the parent
reachable address) entity. Associated with each modem address,
but not visible to Network Management, is a variable last
failure of type binary absolute time. This is valid only if
mapping is manual and the parent circuit entity's access time
is Modem DA.
18.44.28.10 – modem_address_prefix
Support: L1,L2
Default: L1,L2 Value: Address string
The address that is to be inserted to the beginning of the address
extracted from the NSAP address. This is valid only if mapping is
not manual and the parent circuit entity's access type is Modem
DA. It is used in conjunction with modem access suffix to form the
complete dial sequence.
18.44.28.11 – modem_address_suffix
Support: L1,L2
Default: L1,L2 Value: Address string
The address that is to be inserted to the end of the address
extracted from the NSAP address. This is valid only if mapping
is not manual and the parent circuit entity's access type is
Modem DA. It is used in conjunction with modem access prefix
to form the complete dial sequencence.
18.44.28.12 – permitted LAN address
Support: End
Default: { } Value: Set of LAN addresses
The set of LAN addresses corresponding to routers that are
permitted to be used for forwarding to this prefix. This
attribute is supported only if the type characteristic is
set to filter on broadcast circuits only. The default is
an empty set, and at least one LAN address is required.
set [node node-id] routing circuit circuit-name -
reachable address simplename -
permitted lan address {lan-address[,lan-address...]}
Example:
set routing circuit csmacd-1 reachable address to-area4 -
type filter, -
permitted lan address {aa-00-04-00-23-45,aa-00-04-00-BC-DE}
18.44.28.13 – type
Support: L2,End
Default: Outbound Value: Inbound, outbound, or filter
Type of the reachable address. You can modify this characteristic
only when the entity is disabled.
inbound For L2 only, the address prefix corresponds to a
Phase IV area that is reachable through this node
and circuit by inbound traffic.
outbound The address prefix is in an external domain
that is reachable over this circuit by outbound
traffic.
filter The address prefix defines a set of addresses that
should be reached via the set of routers listed in
the permitted LAN address characteristic.
set [node node-id] routing circuit circuit-name -
reachable address simplename -
type reachable-addr-type
Example:
set routing circuit csmacd-1 -
reachable address to-area4 type filter
18.45 – egp_group
set [node node-id] routing egp group group-name ...
Modifies the attributes of a routing egp group entity, which
defines a set of systems in the same autonomous system with which
this system may exchange EGP messages. The modifiable attributes
and their data types [in brackets] are:
autonomous system number [integer]
external routes [set of send,receive]
maximum active neighbors [integer]
receive metric class [internal or external]
send local metric [integer]
send metric classes [set of external,internal]
send replacement metric [integer]
18.45.1 – autonomous_system_number
Support: L2,IP
Default: 0 Value: 0-65535
The autonomous system number common to members of this group. You
can modify this characteristic only when the entity is disabled.
This attribute is supported only if the node is a level 2 router,
and if the system supports dual routing (both DECnet and IP
routing).
18.45.2 – external_routes
Support: L2,IP
Default: Receive Value: Set of send,receive
If the set includes receive, external gateway routes are accepted
from neighbors in the group; if the set does not include receive,
external gateway routes are discarded. If the set includes send,
external gateway routes will be sent to neighbors in this group;
if the set does not include send, external gateway routes are not
sent. You can modify this characteristic only when the entity is
disabled.
18.45.3 – maximum_active_neighbors
Support: L2,IP
Default: 1 Value: 0-255
The maximum number of neighbor systems in the group that this
system will attempt to acquire and maintain in the Up state at
any given time. You can modify this characteristic only when the
entity is disabled.
18.45.4 – receive_metric_class
Support: L2,IP
Default: External Value: Internal or external
The class to be associated with routes received from EGP
neighbors in this group (unless overridden by a routing receive
route entity). You can modify this characteristic only when the
entity is disabled.
18.45.5 – send_local_metric
Support: L2,IP
Default: 1 Value: 0-255
The metric value to be used when announcing routes derived from
local information (unless overridden by a routing send route
entity). You can modify this characteristic only when the entity
is disabled.
18.45.6 – send_metric_classes
Support: L2,IP
Default: Internal Value: Set of external,internal
Routes received through routing protocols other than EGP with
metric classes in this set are candidates for announcement
in EGP messages sent to neighbors in this group, subject to
route propagation policy. Routes with metric classes not
specified in this set will not be announced. You can modify this
characteristic only when the entity is disabled.
18.45.7 – send_replacement_metric
Support: L2,IP
Default: 1 Value: 0-255
Specifies the metric value to be used when announcing routes
derived from non-EGP routing protocols (unless overridden by a
routing send route entity). You can modify this characteristic
only when the entity is disabled.
18.46 – permitted_neighbor
set [node node-id] routing permitted neighbor neighbor-name -
verifier hex-string
18.46.1 – verifier
Support: All
Default: No verifier Value: hex-string, length 0-38
Verifier to be checked from this neighbor. You may change this
characteristic at any time; however, the change will not take
effect until the circuit is next initialized. You cannot
display this characteristic.
If the verifier is not set, then a connection to the neighboring
node whose ID matches the ID in this entry is allowed. If the
verifier is set, the connection is allowed only if the verifier
sent by the remote node matches the one in this entry.
Examples:
create routing permitted neighbor nashua_decnet-osi -
id 08-00-2b-12-34-56
set routing permitted neighbor nashua_decnet-osi -
verifier %x1234
create routing permitted neighbor nashua_phase_iv -
id aa-00-04-00-12-34
set routing permitted neighbor nashua_phase_iv -
verifier %x1234
19 – session_control
set [node node-id] session control ...
Modifies the attributes of the session control entity. The
modifiable attributes and their data types [in brackets] are:
address update interval [integer]
backtranslation search path [ordered list of directory, template]
decnet-internet gateway enabled [boolean] (Tru64 UNIX)
decnet-internet gateway user [username] (Tru64 UNIX)
incoming proxy [boolean]
incoming timer [integer]
maintain backward soft links [boolean]
modify acs [boolean]
naming cache timeout [binreltime] (OpenVMS)
naming cache checkpoint interval [binreltime] (OpenVMS)
naming search path [ordered list of directory, template]
network priority [integer] (OpenVMS)
node synonym directory [full-name]
non privileged user [username] (OpenVMS)
outgoing proxy [boolean]
outgoing timer [integer]
soft link timer [binary-relative-time] (Tru64 UNIX)
transport precedence [set of OSI or NSP]
update retry interval [integer]
For specific command examples, refer to the attribute
descriptions below.
Select application to view the modifiable attributes a session
control application.
Select proxy to view the modifiable attributes of a session
control proxy on Tru64 UNIX.
19.1 – address_update_interval
Default: 10 Values: 1-4294967296
Specifies the minimum time (in seconds) allowed between updates
of address information. More frequent modification to the set of
local towers is prohibited.
Example:
set session control address update interval 10
19.2 – backtranslation_search_path
Default: {} Value: Ordered list of directory, template
An ordered list used by the common directory interface to determine
the order of the naming services used for lookup in
address-to-nodename translation.
On OpenVMS the recommended method of modifying this attribute is to
run NET$CONFIGURE and use Option 2. The result of the configuration
is saved in the SYS$MANAGER:NET$SEARCHPATH_STARTUP.NCL script so the
session control backtranslation search path attribute will be re-set
on startup. However, if a NET$SEARCHPATH_LOCAL.NCL script is found
during startup, that local procedure will be executed in lieu of
the NET$SEARCHPATH_STARTUP.NCL script.
Example:
set node 0 session control back search path -
([directory service = local, template = ""], -
[directory service = domain, template = ""])
19.3 – decnet-internet gateway enabled (Tru64 UNIX)
Default: False Value: True or false
If true, the DECnet-Internet Gateway is enabled.
19.4 – decnet-internet gateway user (Tru64 UNIX)
Name of a user under whose account to run gateway applications.
19.5 – incoming_proxy
Default: True Value: True or false
Specifies whether to honor incoming proxy requests. If this
attribute is set to false, requests to invoke proxies on incoming
requests are ignored.
Example:
set session control incoming proxy true
19.6 – incoming_timer
Default: 45 Values: 0-65535
Time (in seconds) to wait for a user module to issue an
accept/reject call after a port enters a state indicating that
a connection request was received. If the timer expires, Session
Control aborts the transport connection with a timed out error.
For OpenVMS, a zero (0) value directs Session Control to wait
indefinitely without aborting the connection.
Example:
set session control incoming timer 45
19.7 – maintain_backward_soft_links
Default: False Value: True or false
Specifies whether Session Control should attempt to update
the backward translation soft links when it detects an address
change. If this attribute is set to false, Session Control will
add no new backward translation soft links and it may delete any
that it has created.
On OpenVMS, even though the default NCL value for this attribute
is False, the sys$manager:net$session_startup.ncl script resets
this attribute to True.
Examples:
set session control maintain backward soft links true
set session control - ! Resets the attribute to
maintain backward soft links ! the default, which is
! False.
19.8 – modify_acs
Default: True Value: True or false
Specifies whether Session Control should attempt to update the
ACS (access control set) of the node object whenever it attempts
to update the towers attribute for the node in the namespace.
Example:
set session control modify acs true
19.9 – network priority (OpenVMS)
Default: 0 Value: 0-255
When operating over CLNS, indicates network priority encoded in
NPDU header for all transmitted packets. It may only be used by
intermediate systems to assign the packets to queues of appropriate
priority.
19.10 – node_synonym_directory
Default: None Value: Full-name
Full name of a DECdns directory that contains node synonyms.
Example:
set session control node synonym directory DEC:.DNA_NodeSynonym
19.11 – non privileged user (OpenVMS)
Default: None Value: username
Specifies a non-privileged user account. This default account
allows users to perform certain network operations, such as the
exchange of electronic mail between users on different nodes,
without having to supply a user name and password. The default
DECnet user name is also used for file operations when access control
information is not supplied. For example, it permits remote users to
access local files on which the file protection has been set to allow
world access.
You may use NET$CONFIGURE.COM to request a nonprivileged
DECnet account. Refer to the Network Management manual for more
information before adding a default nonprivileged DECnet account.
Example:
set session control non privileged user "netnonpriv"
19.12 – outgoing_proxy
Default: True Value: True or false
Specifies whether to invoke a proxy on outgoing connection
requests when the user does not explicitly specify to do so.
If this attribute is set to false, no proxy is invoked.
Example:
set session control outgoing proxy false
19.13 – outgoing_timer
Default: 60 Values: 0-65535
Time (in seconds) to wait for an outgoing transport connection
to be accepted before Session Control aborts the connection with
a timed out error. For OpenVMS, a zero (0) value directs Session
Control to wait indefinitely without aborting the connection.
Example:
set session control outgoing timer 60
19.14 – soft link timer (Tru64 UNIX)
Default: 30 days Value: Binary relative time
Interval of time (in days) DECdns checks that an object pointed
to by a backward translation soft link still exists.
19.15 – transport_precedence
Default: {} Values: Set of osi or nsp
Note: On the DECnet/OSI for Digital UNIX V1.0
products the default was tp4 rather than osi.
This command sets the order in which transports are selected when
establishing a connection. The default order is to try OSI, then
NSP. The command takes a set as input. Valid items in the set are
SESSION CONTROL TRANSPORT SERVICE entity names.
Examples:
set session control -
transport precedence {} ! By default OSI is preferred over NSP.
set session control -
transport precedence {nsp,osi} ! Prefers NSP over OSI.
19.16 – update_retry_interval
Default: 60 Values: 1-4294967296
Time to wait before Session Control retries a failed attempt to
update information in the namespace.
Example:
set session control update retry interval 60
19.17 – naming cache timeout (OpenVMS)
Default: 30 Value: binary relative time
Amount of time, in days, after which the address and node name
information for a node is deleted from the in-memory, local
naming cache.
Example:
set session control naming cache timeout 30-00:00:00
19.18 – naming cache checkpoint interval (OpenVMS)
Default: 8 Value: binary relative time
The amount of time, in hours, between times when the address and
node name information is checkpointed (flushed) to disk from the
in-memory, local naming cache. The minimum is 15 minutes.
Examples:
set session control -
naming cache checkpoint interval 08:00:00
set session control -
naming cache checkpoint interval 00:15:00
19.19 – naming_search_path
Default: {} Value: Ordered list of directory, template
An ordered list used by the common directory interface to determine
the order of the naming services used for lookup in
nodename-to-address translation.
On OpenVMS the recommended method of modifying this attribute is to
run NET$CONFIGURE and use Option 2. The result of the configuration
is saved in the SYS$MANAGER:NET$SEARCHPATH_STARTUP.NCL script so the
session control naming search path attribute will be re-set on
startup. However, if a NET$SEARCHPATH_LOCAL.NCL script is found
during startup, that local script will be executed in lieu of the
NET$SEARCHPATH_STARTUP.NCL script.
Example:
set node 0 session control naming search path -
([directory service = local, template = "*"], -
[directory service = local, template = "LOCAL:*"], -
[directory service = local, template = "lOCAL:.*"], -
[directory service = domain, template = "*"], -
[directory service = domain, template = "*.SCH.DEC.COM"])
19.20 – application
set [node node-id] session control -
application object-name-or-object-number ...
You can identify an application with an object name or an object
number. Usually, applications are identified by network object
number 0, but you can optionally assign it a nonzero object number,
in the range from 128 to 255. A nonzero object number can be
specified without an application name. Object numbers 1 through
127 are reserved for use by Tru64. Specific network services
are identified by nonzero object numbers; for example, 27
represents the mail utility.
This Set command modifies attributes of a session control application
entity, which 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 modifiable session control application attributes and their
data types [in brackets] are:
accept mode [immediate or deferred] (Tru64 UNIX)
addresses [set of end-user specifications]
allow decnet-internet gateway access [boolean] (Tru64 UNIX)
client [client-id]
data abstraction [message or stream] (Tru64 UNIX)
image name [file-spec]
incoming alias [boolean] (Tru64 UNIX)
incoming osi tsel [hex-string] (OpenVMS)
incoming proxy [boolean]
maximum instances [integer] (Tru64 UNIX)
network priority [integer] (OpenVMS)
node synonym [boolean]
outgoing alias [boolean] (OpenVMS)
outgoingalias name [fullname] (OpenVMS)
outgoing proxy [boolean] (OpenVMS)
programming interface [Phase IV or Phase V] (Tru64 UNIX)
user name [username]
On OpenVMS, the recommended method of modifying session control
application attributes is to run NET$CONFIGURE and choose Option 7.
The configuration information for the applications is then written
to the SYS$MANAGER:NET$APPLICATION_STARTUP.NCL script so the
applications can be re-set on reboot.
If you wish to modify these attributes manually, you may refer
specific command examples in the attribute descriptions.
19.20.1 – addresses
Default: Empty set Value: Set of end-user specifications
A set of end-user specifications, any one of which, when
specified in the destination name field of an incoming connection
request, causes applications defined by this entity to be
invoked.
You can identify an application with an object name or an object
number. Usually, applications are identified by network object
number 0, but you can optionally assign it a nonzero object number,
in the range from 128 to 255. A nonzero object number can be
specified without an application name. Object numbers 1 through
127 are reserved for use by HP. Specific network services
are identified by nonzero object numbers; for example, 27
represents the mail utility.
Examples:
set session control application mail addresses {number=27}
set session control application task addresses {name=task}
19.20.2 – accept mode (Tru64 UNIX)
Default: Immediate Value: Immediate or deferred
If accept mode is immediate, then session control will
automatically accept the connection before activating the
end user. If accept mode is deferred, then it is up to the
program to accept or reject the connection.
19.20.3 – allow decnet-internet gateway access (Tru64 UNIX)
Default: False Value: True or false
If true, this application supports gateway access. If the user
name supplied by the incoming connect request contains a @ or
!, the application spawner starts up the application under the
session control DECnet-Internet Gateway user.
19.20.4 – client
Default: None Value: Entity 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.
19.20.5 – data abstraction (Tru64 UNIX)
Default: Message Value: Message or stream
Type of data transfer interface the application will be using;
message type or stream type. The message data abstraction is
identical to the Sequenced-packet socket concept of the Phase IV
session control. When writing applications, you should use the
same data abstraction as that used by the program to which you
connect.
Table Data Abstraction Type Comparison compares Message and
Stream data abstractions.
Table 1-1 Data Abstraction Type Comparison
Message Type Stream Type
Preserves message Does not preserve message boundaries
boundaries
HP DECnet-Plus Commonly used for Tru64 UNIX
for OpenVMS default applications
abstraction
Not available on Available on TCP/IP
TCP/IP
Supported by XTI Supported by XTI
19.20.6 – image_name
Default: No image name Value: File specification
File name 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.
Example:
set session control application mirror -
image name sys$system:net$mirror.exe
19.20.7 – incoming alias (Tru64 UNIX)
Specifies how a particular application responds to incoming
connect requests directed to the alias node address. If False,
the application does not allow a specified application to receive
incoming connect requests that have been directed to the alias
node address.
19.20.8 – incoming osi tsel (OpenVMS)
Default: None Value: hex-string
The TSEL for which this image will accept connections. This is
similar to the destination names attribute. However,
applications using this access point for in-connection matching
do not use DNA Session Control protocol.
19.20.9 – incoming_proxy
Default: True Value: True or false
Specifies whether to honor incoming proxy requests. If this
attribute is set to false, requests to invoke proxies on
incoming requests are ignored. The setting of this characteristic
overrides the setting of the session control incoming proxy
characteristic for the specified application.
Example:
set session control application mail incoming proxy false
19.20.10 – maximum instances (Tru64 UNIX)
Default: 0
Maximum number of simultaneous instances of this application
allowed. If a connect request comes in for this application
while the maximum number of instances exist, the connect request
will be rejected with ObjectTooBusy. A value of 0 indicates no
maximum.
19.20.11 – network priority (OpenVMS)
Default: 0 Value: 0-225
When operating over Connectionless Network Service (CLNS),
indicates network priority encoded in the NPDU (network protocol
data unit) header for all transmitted packets. It can be used by
intermediate systems to assign the packets to queues of
appropriate priority.
19.20.12 – node_synonym
Default: False Value: True or false
Default form in which the remote node name is passed to the
application.
false The full node name is used.
true The node synonym is used; if no synonym is available,
the full name is used.
Example:
set session control application mail node synonym true
19.20.13 – outgoing alias (OpenVMS)
Default: False Value: True or false
Specifies whether a particular object uses the alias node
identifier in its outgoing connect requests. If false,
the specified object is not allowed to use the alias node
address in its outgoing connect requests.
Example:
set session control application mail outgoing alias true
19.20.14 – outgoingalias name (OpenVMS)
Default: None Value: fullname of alias
Specifies which alias name a particular object uses in its
outgoing connect requests when multiple aliases are in use.
If you do not set an application outgoingalias name and the
application has the outgoing alias set to true, the alias
name for which you set the alias port outgoing default true
is used for outgoing connect requests.
If you define application outgoingalias name, this supersedes
the setting of alias port outgoing default. So if the
application outgoing alias attribute is then set to false to
disable the application outgoingalias name, the local node
name is used.
If neither alias port going default nor application
outgoingalias name is set, the first alias created is used as
the default for the system. If this alias is not enabled,
the local node name is used.
Example:
set session control application mail -
outgoingalias name DEC:.lkg.MyAlias
19.20.15 – outgoing proxy (OpenVMS)
Default: False Value: True or false
Default action to execute when user does not explicitly
specify whether or not to invoke a proxy.
Example:
set session control application 36 outgoing proxy true
19.20.16 – programming interface (Tru64 UNIX)
Default: Phase IV Value: Phase IV or Phase V
Programming interface used by the DECnet application (socket
interface).
19.20.17 – user_name
Default: None Data type: Latin1String
Identifies the default account under which the application is to
run. For OpenVMS, if null then system defaults are used to select
the user. The username must be specified in quotes on OpenVMS.
Example:
set session control application cml user name "cml$server"
19.21 – proxy (Tru64 UNIX)
set [node node-id] session control proxy proxy-name ...
Modifies the attributes of a session control proxy entity which
stores the information that grants remote users proxy access to
given application subentity instances. The modifiable
attributes and their data types [in brackets] are:
applications [set of simplenames]
source end users [set of records]
target user [latin1string]
type [explicit or default]
19.21.1 – applications
Default: None Value: Set of simplenames
Set of application identifiers, one of which must match the
application requested. If this attribute value is null, any
requested application will match.
19.21.2 – source_end_users
Default: None Value: Set of records
Set of remote end users for whom this proxy entry applies.
An unspecified end user implies all end users on the node
specified in the same record. The record format has two
fields: node, which has a data type of fullname, and
end user, which has a data type of enduserspecification.
19.21.3 – target_user
Default: None Value: Latin1string
Local user name under which access is granted.
19.21.4 – type
Default: Explicit Value: Explicit or default
Type of proxy entry: explicit means that the destination
the user requested in the connect request must match the
target user for this entry; default means if no explicit
entry matches, this entry will be tried. An explicit
proxy entry matches before a default one.
20 – x25_access
20.1 – application
set [node node-id] x25 access application application-name ...
Modifies the attributes of an x25 access application entity, which
defines an application to be executed for an incoming call. The
modifiable attributes and their data types [in brackets] are:
account [latin1string] (Tru64 UNIX)
activation data [latin1string] (Tru64 UNIX)
file [filename]
filters [set of simplenames]
maximum activations [integer] (Tru64 UNIX)
template [simplename] (Tru64 UNIX)
type [X25, X29, or X29 login]
user [latin1string]
20.1.1 – account (Tru64 UNIX)
Default: No service/account data Value: Latin1String
Default service or account identifier to be used when starting
the applications process.
20.1.2 – activation data (Tru64 UNIX)
Default: None Value: Latin1String
Data required to start the application process. This
characteristic is optional.
20.1.3 – file
Default: None Value: File name
Indicates the file name or command that is associated with starting a
process for the represented application.
Example:
set x25 access application X25_MAIL file "sys$system:x25$mail.com"
20.1.4 – filters
Default: None Value: Set of simplenames
Set of filters that are associated with filtering calls for
either X.25 or X.29 applications represented by this entity.
Example:
set x25 access application X29_LOGIN filters {X29}
20.1.5 – maximum activations (Tru64 UNIX)
Default: 1 Value: 1-65535
Maximum number of concurrent activations of the represented
application that are possible.
Example:
set x25 access application X29_LOGIN maximum activations 5
20.1.6 – template (Tru64 UNIX)
Default: No template Value: simplename
Template to be used in a call accept.
Example:
set x25 access application X29_LOGIN template X29Server
20.1.7 – type
Specifies the type of application.
X25 This application operates in X.25 mode. This
is the default.
X29 This application operates in character mode.
X29 login This is an application of X.29 type devoted
specifically to login sessions.
Example:
set x25 access application X25_MAIL type x25
20.1.8 – user
Default: No user ID Value: Latin1String
Default user identification to be used to start the application
process. This attribute is not valid for type X29 login and
should be null. On OpenVMS, Latin1Strings must be embedded in
quotes.
Example:
set x25 access application X25_MAIL user "X25MAIL"
20.2 – dte_class
set [node node-id] x25 access dte class class-name ...
Modifies the attributes of an x25 access dte class entity, which
defines a named class of DTEs. The modifiable attributes and
their data types [in brackets] are:
account [latin1string] (OpenVMS)
DNIC [DTE address]
international prefix [DTE address]
local dtes [set of simplenames]
local prefix [DTE address]
node [full-name] (OpenVMS VAX)
outgoing session template [simplename] (OpenVMS)
security dte class [simplename]
service nodes [set of records] (OpenVMS Alpha)
strip DNIC [boolean]
user [latin1string] (OpenVMS)
20.2.1 – account (OpenVMS)
Default: No service/account data Value: Latin1String
Default service or account data to be used when connecting to
the X.25 server on the gateway system specified by the node
characteristic or service node characteristic. This attribute is
supported only for DTE classes with characteristic type remote.
The account value must be specified in quotes.
20.2.2 – DNIC
Default: Supplied by Value: DTE address of 3 or 4 digits length
profile
The first part of the Network User Address (NUA). This takes
one of two forms: Either it is in the form of the Data Network
Identification Code (DNIC) and is specified by 4 digits, or it
is in the form of a Data Country Code (DCC) and is specified by
3 digits. If no profile is specified, the default is null.
20.2.3 – international_prefix
Default: Supplied by Value: DTE address of 1 digit only.
profile
First digit of an X.121 address to indicate an international or
internetwork call. If no profile is specified, the default is a
null DTE address.
20.2.4 – local_dtes
Default: No names Value: Set of simplenames
Names of the local x25 protocol dte entities that belong to this
DTE class. Note that these DTE entities need not exist when their
names are entered in this set; DTEs that do not exist when the
DTE class is used are not considered when the DTE class is used
for an outgoing call.
If an x25 protocol dte entity has status attribute state set to
running when its name is added to local dtes, you must disable
the DTE entity and reenable it (see the disable x25 protocol dte
and enable x25 protocol dte commands) in order for the DTE to be
considered when this DTE class is used for an outgoing call.
You can specify this characteristic only for DTE classes with
characteristic type local.
Example:
set x25 access dte class dte-1 local dtes (dte-0)
20.2.5 – local_prefix
Default: Supplied by Value: DTE address of 1 digit only
profile
First digit of a DTE address to indicate a local call. If no
profile is specified, the default is a null DTE address.
20.2.6 – node (OpenVMS VAX)
Default: No name Value: Full-name
Node name of the remote gateway system on which the DTEs in this
DTE class reside. Note that this characteristic is supported only
if the service nodes characteristic is not supported.
This characteristic is supported only for DTE classes
with type characteristic set to remote.
20.2.7 – outgoing session template (OpenVMS)
Default: Default or no name Value: simplename
(see description)
Name of the OSI Transport template to be used by the X.25 client to
connect to the X.25 server on the gateway system. The default
value default is valid only if OSI session control is being used.
This attribute is supported only for DTE classes with characteristic
type remote.
20.2.8 – security_dte_class
Default: Default Value: simplename
Name of the x25 access security dte class entity that controls
inbound and outbound access using this DTE class.
Example:
set x25 access dte class dte-1 security dte class Default
20.2.9 – service nodes (OpenVMS Alpha)
Default: No records Value: Set of records
Names of the nodes that may be used as candidate X.25 gateway
systems and their associated ratings. Each record consists of
a full name that describes the candidate node and an integer
that indicates its ratings. The records are listed in order
of descending rating. Values are entered as [node=nodename,
rating=integer]. The rating represents the maximum number of
session control connections to the node pair.
20.2.10 – strip DNIC
Default: False Value: True or false
Defines whether the first part of the NUA (the DNIC or DCC
specified by the DNIC characteristic) should be stripped for
outgoing calls, and whether the network strips the first portion
of the NUA from addresses it presents to the DTE.
20.2.11 – user (OpenVMS)
Default: No user ID Value: Latin1String
Default user identification to be used when connecting to the
gateway system specified by the service nodes characteristic.
The user id must be specified in quotes.
20.3 – filter
set [node node-id] x25 access filter filter-name ...
Modifies the attributes for an x25 access filter entity, which
defines the criteria by which the destination of an incoming call
is determined. The modifiable attributes and their data types
[in brackets] are:
call data mask [hex-string]
call data value [hex-string]
called address extension mask [hex-string]
called address extension value [hex-string]
called nsap [nsap-address] (Tru64 UNIX)
group [simplename]
inbound dte class [simplename]
incoming dte address [dte-address]
originally called address [dte-address]
priority [integer]
receiving dte address [dte-address]
redirect reason [reason]
security filter [simplename]
sending dte address [dte-address]
subaddress range [one-range-set] (OpenVMS VAX)
20.3.1 – call_data_mask
Default: No mask Value: Hex string
Mask to be applied to call user data in an incoming call. The
result is compared, octet by octet, with the call data value
characteristic.
Example:
set x25 access filter "OSI Transport" -
call data value "03010100'H, call data mask "FFFFFFFF'H
20.3.2 – call_data_value
Default: No call user data Value: Hex string
Call user data value to be matched by this filter. This value is
compared, octet by octet, with the masked call user data in the
call request. This string must have the same length as the string
specified for the call data mask characteristic.
Example:
set x25 access filter "OSI Transport" -
call data value "03010100'H, call data mask "FFFFFFFF'H
20.3.3 – called_address_extension_mask
Default: No called Value: Hex string
address extension
mask
Mask to be applied to the called address extension in an incoming
call. The result is compared, octet by octet, with the called
address extension value characteristic.
20.3.4 – called_address_extension_value
Default: No called Value: Hex string
address extension
value
Called address extension value to be matched by this filter.
This value is compared, octet by octet, with the masked called
address extension value. This string must have the same length
as the string specified in the called address extension mask
characteristic.
20.3.5 – group
Default: No group name Value: simplename
Name of the x25 protocol group entity to be matched by this
filter. The DTE must belong to this group for the filter to
match. Wildcards can be used in the group name.
20.3.6 – inbound_dte_class
Default: No DTE class Value: simplename
Name of the DTE class to be matched by this filter. The DTE must
belong to this DTE class for the filter to match. This is the
DECnet-Plus mechanism for specifying a local receiving DTE; see
also the description of the receiving dte address characteristic.
Wilcards can be used in the class name.
Example:
set x25 access filter FILTER_0 inbound dte class remote-class-0
20.3.7 – incoming_dte_address
Default: No DTE Value: DTE address
address
Value to be matched with the "called address" field of an
incoming call packet. Wildcards can be used in the incoming
DTE address.
Example:
set x25 access filter FILTER_1 incoming dte address 987654444
20.3.8 – originally_called_address
Default: No address Value: DTE address
Value to be matched with the "originally called address" field of
an incoming call that has been redirected. Wildcards can be used
in the originally called DTE address.
20.3.9 – called_nsap
Default: No NSAP Value: NSAP address
address
Value to be matched against the called address extension field
of an incoming call packet when the field contents are encoded in
ISO format.
20.3.10 – priority
Default: 1 Value: 0-65535
Filter's position in an ordered set of filters used for matching
incoming calls.
Example:
set x25 access filter FILTER_0 priority 1
20.3.11 – receiving_dte_address
Default: No DTE Value: DTE address
address
Address that is used to match the DTE address of the local
receiving DTE. This characteristic is included for backward
compatibility with Phase IV; the DECnet-Plus mechanism uses the
dte class characteristic. Wildcards can be used in the
receiving DTE address.
Example:
set x25 access filter FILTER_0 receiving dte address 987655555
20.3.12 – redirect_reason
Default: Not Value: See description
specified
Reason for matching a call that has been redirected.
busy The original destination was busy.
not Redirection was not checked.
specified
out of The original destination was not operational.
order
systematic Calls to the original destination are systematically
redirected.
This value must be the same as the redirect reason in the call
request for the filter to match.
Example:
set x25 access filter "OSI Transport" redirect reason not specified
20.3.13 – security_filter
Default: Default Value: simplename
Name of the x25 access security filter entity that controls
access to this filter. Wildcards can be used in the security
filter name.
Example:
set x25 access filter X25_MAIL security filter Default
20.3.14 – sending_dte_address
Default: No DTE Value: DTE address
address
Value to be compared with the "calling address" field of an
incoming call packet. These values must be the same for the
filter to match. Wildcards can be used in the sending DTE
address.
Example:
set x25 access filter FILTER_0 sending dte address 987656789
20.3.15 – subaddress range (OpenVMS VAX)
Default: No range Value: Set of one range
Subaddress range value to be matched by this filter. Format the
values to specify this subaddress range. This set must either
be empty or contain exactly one value. This attribute has been
retired; it has been included to allow the value of the attribute
to be seen, but it cannot be modified.
20.4 – reachable_address
set [node node-id] x25 access reachable address address-name ...
Modifies the an x25 access reachable address entity, which maps a
destination network service access point (NSAP) address in an
outgoing call to a DTE class/DTE address pair. The modifiable
attributes and their data types [in brackets] are:
address extensions [boolean]
destination [dte-address]
dte class [simplename]
mapping [Manual or X.121]
20.4.1 – address_extensions
Default: True Value: True or false
Specifies whether the "called address extension" and "calling
address extension" fields are to be included in the outgoing call
packet.
Example:
set x25 access reachable address x121 address extensions true
20.4.2 – destination
Default: No DTE Value: DTE address
address
Manually entered DTE address. This address is used only if the
mapping characteristic has the value manual.
20.4.3 – dte_class
Default: No class Value: Class name
name
Name of the DTE class to be used in making the outgoing call. If
not specified, any DTE class may be used.
Example:
set x25 access reachable address FRED dte class remote-class-0
20.4.4 – mapping
Default: X.121 Value: Manual or X.121
Mechanism by which the destination DTE address is to be derived.
manual The destination DTE address is supplied manually by means
of the destination characteristic.
X.121 The destination DTE address is derived by an algorithm from
an NSAP address in X.121 format. X.121 address mapping may
only be specified with address prefixes of 36, 37, 49, 52
and 53.
Example:
set x25 access reachable address x121 mapping X . 121
20.5 – security_dte_class
20.5.1 – remote_dte
set [node node-id] x25 access security dte class class-name
remote dte dte-name ...
Modifies attributes of an x25 access security dte class remote dte
entity, which is a collection of access control attributes that
control inbound calls from and outbound calls to a set of remote
DTEs. The modifiable attributes and their data types [in brackets]
are:
acl [access-control-list]
rights identifiers [set of simplenames]
20.5.1.1 – acl
Default: No acl Value: Access control list
Access Control List (ACL) that is used when checking outbound
calls to the set of DTE addresses that this remote DTE
represents. Wildcards can be used in the identifiers that form
part of each Access Control Entry (ACE) in an Access Control
List (ACL).
Example:
set x25 access security dte class Default -
remote dte match_all -
acl (( identifier = ( docwriter ), access = NONE))
20.5.1.2 – rights_identifiers
Default: No rights identifiers Value: Set of simplenames
Rights identifiers possessed by this remote DTE. It is used
for incoming call checking against the ACL attribute of a
security filter entity that is used to guard a filter.
Example:
set x25 access security dte class Default -
remote dte match_all -
rights identifiers (FILT_FILTER_1_NONE,APPL_APPLICATION_0_NONE)
20.6 – security_filter
set [node node-id] x25 access security filter filter-name -
acl access-control-list
acl
Default: No acl Value: Access control list
Access control list that is used for checking inbound calls for
all filters using this security filter. Wildcards can be
used in the identifiers that form part of each Access Control
Entry (ACE) in an Access Control List (ACL).
Example:
set x25 access security filter Default acl -
((identifier= (Default_ALL), access = ALL), -
(identifier= (Default_REMOTE), access = REMOTE_CHARGE), -
(identifier= (Default_NONE), access = NONE))
20.7 – template
set [node node-id] x25 access template template-name ...
Modifies an x25 access template entity, which is used to supply
default values for call parameters when an outgoing call is made.
The modifiable attributes and their data types [in brackets] are:
call data [hex-string]
calling address extension [nsap-address]
charging information [boolean]
destination dte address [dte-address]
dte class [simplename]
end-to-end delay [range]
expedited data [Not Specified, Use, or Do Not Use]
fast select [string]
local facilities [hex-string]
local subaddress [dte-address]
network user identity [hex-string]
nsap mapping [boolean]
packet size [integer]
quality of service [hex-string]
reverse charging [boolean]
rpoa sequence [sequence of hex-string]
selected group [simplename]
target address extension [nsap-address]
throughput class request [range]
transit delay selection [range]
window size [integer]
20.7.1 – call_data
Default: No call user data Value: Hex string
Call user data to be sent in the call.
Example:
set x25 access template "OSI Transport" call data '03010100'H
20.7.2 – calling_address_extension
Default: No NSAP address Value: NSAP address
Calling Network Service Access Point (NSAP) address is to be
passed to a higher-level entity within the called DTE. A null
address indicates that this facility is not included in the
outgoing call.
20.7.3 – charging_information
Default: False Value: True or false
Specifies whether charging information is requested for this
call.
Example:
set x25 access template "OSI Transport" -
charging information false
20.7.4 – destination_dte_address
Default: No DTE address Value: DTE address
Address of the remote DTE, including the remote subaddress (if
any), to which the call is directed.
Example:
set x25 access template TEMPLATE-0 -
destination dte address 3234234234
20.7.5 – dte_class
Default: No DTE class name Value: simplename
Name of the DTE class to be used for the call.
set x25 access template TEMPLATE-0 dte class remote-class-0
20.7.6 – end-to-end_delay
Default: [0..0] Value: Range (see description)
Lower and upper bounds of the acceptable end-to-end delay for the
call. A zero value for either bound indicates that no range is
included in the outgoing call.
Example:
set x25 access template X29Server end-to-end delay [0..0]
20.7.7 – expedited_data
Default: Not specified Value: See description
Specifies whether expedited data is requested for the call.
do not use Expedited data is not in use.
not Expedited data is not requested.
specified
use Expedited data is in use.
Example:
set x25 access template Default expedited data not specified
20.7.8 – fast_select
Default: Not specified Value: See description
Specifies whether fast select is requested for the call.
fast select Fast select is in use.
no fast Fast select is not in use.
select not Fast select is not requested.
specified Fast select with response is in use.
with response
Example:
set x25 access template "OSI Transport" fast select not specified
20.7.9 – local_facilities
Default: No facilities Value: Hex string
Non-CCITT facilities that are available from the local PSDN.
The string is placed in the outgoing call request packet without
modification. The contents and interpretation of this string are
implementation-dependent.
20.7.10 – local_subaddress
Default: No DTE address Value: DTE address
Local subaddress to be appended to the calling DTE address in the
call.
20.7.11 – network_user_identity
Default: No network user identity Value: Hex string
Network user identity to be included in the call packet. The
format of the network user identity is specified by the PSDN
administration.
Example:
set x25 access template TEMPLATE-0 network user identity %x12fe
20.7.12 – nsap_mapping
Default: False Value: True or false
Specifies whether an x25 access reachable address entity is used
to map the supplied NSAP address to a destination DTE class/DTE
address pair.
Example:
set x25 access template TEMPLATE-0 nsap mapping false
20.7.13 – packet_size
Default: Supplied by profile Value: 0-4096
Packet size, in octets, for transmitted and received data
packets. The value must be a power of 2 in the range 0 to 4096.
The value zero indicates that no packet size is included in the
outgoing call.
Example:
set x25 access template TEMPLATE-0 packet size 512
20.7.14 – quality_of_service
Default: No data Value: Hex string
Quality of service data. The contents and interpretation of this
string are implementation-dependent.
20.7.15 – reverse_charging
Default: False Value: True or false
Specifies whether reverse charging is requested for the call.
Example:
set x25 access template TEMPLATE-0 reverse charging false
20.7.16 – rpoa_sequence
Default: No DTE addresses Value: Set of DTE addresses
Private Operating Agency sequence of transit networks to be used
in setting up the call. Format the values to specify a set of
DTE addresses. Each DTE address is four digits long. An empty set
indicates that no sequence is included in the outgoing call.
20.7.17 – selected_group
Default: No group name Value: simplename
Name of the x25 protocol group entity that represents the CUG
selected for the call. The index for group is included in the
facility field of the call request packet.
20.7.18 – target_address_extension
Default: No NSAP address Value: NSAP address
Called NSAP address to be sent to the called DTE should be
supplied by a higher-level entity in the calling DTE. A null
address indicates that this facility is not required.
20.7.19 – throughput_class_request
Default: [0..0] Value: Range (see the following
description)
Minimum acceptable throughput class (the lower bound of the
range) and the target throughput class (the upper bound of the
range) for a call. The only legal range values are as follows:
0 2400
75 4800
150 9600
300 19200
600 48000
1200
The range 0-0 indicates that no throughput class is
included in the outgoing call.
Example:
set x25 access template TEMPLATE-0 -
throughput class request [0..0]
20.7.20 – transit_delay_selection
Default: 0 Value: Integer
Desired transit delay. A zero value for either bound indicates
that no value is included in the outgoing call.
Example:
set x25 access template X29Server transit delay selection 0
20.7.21 – window_size
Default: Supplied by profile Value: 0-127
Window size for transmitted and received data packets. A zero
value indicates that no window size is included in the outgoing
call.
Example:
set x25 access template TEMPLATE-0 window size 7
21 – x25_protocol
21.1 – dte
set [node node-id] x25 protocol dte dte-name ...
Modifies the attributes of an x25 protocol dte entity which
describes a local DTE. Modifiable attributes and their data
types [in brackets] are:
call timer [integer]
ccitt version [integer]
clear timer [integer]
default packet size [integer]
default window size [integer]
extended packet sequencing [boolean]
inbound dte class [simple-name]
incoming list [set of ranges]
interface type [dte, dce, or negotiated]
interrupt timer [integer]
link service provider [local-entity-name]
maximum clear attempts [integer]
maximum packet size [integer]
maximum reset attempts [integer]
maximum restart attempts [integer]
maximum throughput classes [integer]
maximum window size [integer]
minimum packet size [integer]
minimum throughput classes [integer]
minimum window size [integer]
outgoing list [set of ranges]
reset timer [integer]
restart timer [integer]
segment size [bytes]
x25 address [DTE-address]
switched circuit [boolean]
Select pvc to view the modifiable attributes of an x25 protocol
dte pvc entity.
21.1.1 – call_timer
Default: Supplied by Value: Bounded by profile
profile
Elapsed time, in seconds, before which a clear packet is sent
for outgoing calls from the DTE that have received no response. A
zero value indicates that no clear is sent.
21.1.2 – ccitt_version
Default: 1984 Value: 1-9999
Version of the CCITT X.25 recommendations to which the DTE
conforms.
21.1.3 – clear_timer
Default: Supplied by Value: Bounded by profile
profile
Value of the retransmit timer for outgoing clear packets from the
DTE. The default value is profile dependent.
21.1.4 – default_packet_size
Default: 128 Value: 16-4096 raised to the power of 2
Default packet size, in octets, for all virtual circuits on the
DTE. The value must not be less than the value of the minimum
packet size characteristic.
Example:
set x25 protocol dte dte-1 default packet size 128
21.1.5 – default_window_size
Default: 2 Value: 1-127
Default window size for all virtual circuits on the DTE; that
is, the default number of unacknowledged packets. This value
must not be greater than the value of the maximum window size
characteristic, and must not be less than the value of the
minimum window size characteristic.
Example:
set x25 protocol dte dte-1 default window size 2
21.1.6 – extended_packet_sequencing
Default: False Value: True or false
Specifies whether the extended packet sequencing facility is
subscribed to, in which modulo 128 packet numbering is used. If
false, extended packet sequencing is not used. The profile may
provide overriding default or legal values.
Example:
set x25 protocol dte dte-1 extended packet sequencing false
21.1.7 – inbound_dte_class
Default: No DTE class Value: Simple-name
name
Name of the DTE class to be associated with all incoming calls to
the DTE. You must specify this characteristic before you enable
the DTE. The x25 access dte class entity to which the name refers
must exist when you enable the DTE.
Example:
set x25 protocol dte dte-1 inbound dte class lls2-class-0
21.1.8 – incoming_list
Default: (1-4095) Value: Set of range (1-4095)
ranges
Channel number ranges that define the Logical Channel Numbers
(LCNs) that are available for calls on incoming or bothway
channels. Format the values to specify a set of channel number
ranges. Each channel number is the concatenation of the logical
channel group number and logical channel number of an SVC on the
DTE.
Example:
set x25 protocol dte dte-1 incoming list ([10..4095])
21.1.9 – interface_type
Default: DTE Value: See description
Interface mode in which the packet protocol for the DTE will
operate. You can modify this characteristic only when the entity
is disabled.
dce DCE mode.
dte DTE mode.
negotiated The interface mode is negotiated with the other end
to be either DTE or DCE. This value applies only to
point-to-point links.
Example:
set x25 protocol dte dte-1 interface type negotiated
21.1.10 – interrupt_timer
Default: Supplied by profile Value: Bounded by profile
Value of the interrupt timer. This timer is started when an
interrupt packet is sent. If no interrupt confirmation packet
is received before the timer expires, a reset is caused. A zero
value indicates that there is no timer.
21.1.11 – link_service_provider
Default: No link Value: local entity name
service provider name
Name of the link service provider entity used by the DTE.
You must give this characteristic a value before you enable
the DTE.
Example:
set x25 protocol dte dte-1 -
link service provider lapb link link-0
21.1.12 – maximum_clear_attempts
Default: Supplied by Value: Bounded by profile
profile
Number of times that sending a clear packet can be attempted on
a virtual circuit on the DTE. The value 1 indicates that a clear
packet is sent only once; that is, there are no retries.
21.1.13 – maximum_packet_size
Default: 128 Value: 16-4096 raised to the power of 2
Maximum packet size, in octets, for all virtual circuits on the
DTE. This value must be greater than or equal to the value of the
minimum packet size and default packet size characteristics.
Example:
set x25 protocol dte dte-0 maximum packet size 256
21.1.14 – maximum_reset_attempts
Default: Supplied by Value: Bounded by profile
profile
Number of times the DTE attempts to send a reset packet. The
value 1 indicates that a reset packet is sent only once; that is,
there are no retries.
21.1.15 – maximum_restart_attempts
Default: Supplied by Value: Bounded by profile
profile
Number of times that any virtual circuit on the DTE attempts
to send a restart packet. The value 1 indicates that a restart
packet is sent only once; that is, there are no retries.
21.1.16 – maximum_throughput_class
Default: 4800 Value: See description
Maximum value for the throughput class (65535) of any virtual
circuit on the DTE. The value specified must be one of the
following: 0, 75, 150, 300, 600, 1200, 2400, 4800, 9600, 48000,
or 64000. The value must be greater than or equal to the value of
the minimum throughput class characteristic.
21.1.17 – maximum_window_size
Default: 2 Value: 1-127
Maximum number of unacknowledged packets for all virtual
circuits on the DTE. This value must be greater than or equal
to the value of the minimum window size and default window size
characteristics.
Example:
set x25 protocol dte dte-1 maximum window size 4
21.1.18 – minimum_packet_size
Default: 128 Value: 16-4096 raised to the power of 2
Minimum packet size, in octets, for all virtual circuits on the
DTE. This value must be less than or equal to the value of the
maximum packet size and default packet size characteristics.
Example:
set x25 protocol dte dte-1 minimum packet size 128
21.1.19 – minimum_throughput_class
Default: Supplied by Value: Bounded by profile
profile
Minimum throughput class for any virtual circuit on the DTE. The
value specified must be one of the following: 0, 75, 150, 300,
600, 1200, 2400, 4800, 9600, 48000, or 64000. The value must be
less than or equal to the value of the maximum throughput class
characteristic.
21.1.20 – minimum_window_size
Default: 2 Value: 1-127
Minimum window size for all virtual circuits on the DTE. This
value must be less than or equal to the value of the maximum
window size characteristic.
Example:
set x25 protocol dte dte-1 minimum window size 1
21.1.21 – outgoing_list
Default: [1...4095] Value: Set of range (0-4095)
Channel number ranges that define the LCNs that are available
for calls on outgoing or two-way channels. Format the values to
specify a set of channel number ranges. Each channel number is
the concatenation of the logical channel group number and logical
channel number of an SVC on the DTE.
Example:
set x25 protocol dte dte-1 outgoing list ([10..4095])
21.1.22 – reset_timer
Default: Supplied by Value: Bounded by profile
profile
Value of the retransmit timer for outgoing reset packets from the
DTE. The default value is profile-dependent.
21.1.23 – restart_timer
Default: Supplied by Value: Bounded by profile
profile
Value of the retransmit timer for outgoing restart packets from
the DTE. The default value is profile dependent.
21.1.24 – segment_size
Default: 64
Segment unit size specified for data sent at this DTE to be
used for charging.
Example:
set x25 protocol dte dte-1 segment size 64
21.1.25 – switched_circuit
Default: false Value: True or false
Set to true if DTE is operating over a switched circuit.
21.1.26 – x25_address
Default: No DTE address Value: DTE-address
Full address of the DTE. You must give this characteristic a
value before you enable the DTE.
Example:
set x25 protocol dte dte-1 x25 address 123456789
21.1.27 – pvc
set [node node-id] x25 protocol dte dte-name pvc pvc-name ...
Modifies the attributes of an x25 protocol dte pvc, which describes
a permanent virtual circuit (PVC). The modifiable attributes and
their data types [in brackets] are:
acl [access-control-list]
packet size [octets]
window size [integer]
21.1.27.1 – acl
Default: No access Value: Access-control-list
control list
Access control list that controls access to this PVC.
Example:
set x25 protocol dte dte-1 pvc PVC-1 -
acl ((identifier = (*), access = NONE))
21.1.27.2 – packet_size
Default: No default Value: 16-4096
Packet size for the PVC, in octets. The value must be a power
of 2 in the range 16 to 4096. The value of this characteristic
derives from an argument to the create command.
Example:
set x25 protocol dte dte-1 pvc PVC-1 packet size 128
21.1.27.3 – window_size
Default: No default Value: 1-127
Window size for the PVC. The value of this characteristic derives
from an argument to the create command.
Example:
set x25 protocol dte dte-1 pvc PVC-1 window size 2
21.2 – group
set [node node-id] x25 protocol group group-name ...
Modifies the attributes of an x25 protocol group entity, which
specifies a number of DTEs that make up a closed user group (CUG).
Modifiable attributes and their data types (in brackets) are:
members [set of records]
remote dte address [dte-address]
type [CUG, BCUG, or CUGOA]
rights identifiers [set of simplenames]
acl [access-control-list]
21.2.1 – members
Default: No DTEs Value: Set of records
DTEs at a gateway system that make up the group. Format the
values to specify a set of records. Each record consists of a
name that identifies an X25 protocol dte entity and an integer
(in the range 0 to 9999) that identifies the CUG number assigned
by the network. If a DTE is already created and enabled and is
then added to the set of members, it must be disabled and re-
enabled to service the specified CUG number or BCUG.
Example:
set x25 protocol group GROUP-0 -
members ((dte = dte-1, index = 444), -
(dte = dte-0, index = 8787))
21.2.2 – remote_dte_address
Default: No DTE Value: DTE-address
address
DTE address to be associated with this entity for matching x25
access security dte class remote dte entities for both incoming
and outgoing calls. This characteristic is only supported if the
characteristic type is bcug.
21.2.3 – type
Default: BCUG Value: CUG, BCUG, or CUGOA
Type of the CUG.
cug Normal CUG.
bcug Bilateral CUG.
cugoa CUGOA outgoing access.
Example:
set x25 protocol group GROUP-0 type CUG
21.2.4 – rights_identifiers
Default: No rights identifiers Value: Set of simple names
Set of rights identifiers that this group possesses.
21.2.5 – acl
Default: No access Value: Access-control-list
control list
Access control list that controls access to this group.
22 – x25 relay (Alpha)
22.1 – client
set [node node-id] x25 relay client client-name ...
Modifies the attributes of an x25 relay client entity, which
provides a set of default values to be used to set up a relay
between an incoming call and an outgoing call. The modifiable
attributes and their data types (in brackets) are:
dte class [simplename]
filters [set of simplenames]
rights identifiers [set of simplenames]
template [simplename]
22.1.1 – dte_class
Default: No DTE class Value: Simple-name
Name of the x25 access DTE class entity to use when making the
outgoing call.
22.1.2 – filters
Default: No filters Value: Set of simple names
Set of filters that are listened to by this client. Each name
is the name of an x25 access filter entity. For the add and set
commands, the x25 relay client entity must be in the Off state
before the filters attribute can be modified.
22.1.3 – rights_identifiers
Default: No rights Value: Set of simple names
identifiers
Set of rights identifiers that this client possesses. It is used
when placing the outgoing call.
22.1.4 – template
Default: No template Value: Simple name
Name of the x25 access template entity to be used for the
outgoing call.
22.2 – pvc
set [node node-id] x25 relay pvc pvc-name ...
Modifies the attributes of an x25 relay pvc entity, which provides
a set of default values to be used to establish a connection to a
client over a permanent virtual circuit (PVC). The modifiable
attributes and their data types (in brackets) are:
local pvc [simplename]
remote dte class [simplename]
remote pvc [simplename]
retry limit [integer]
retry timer [integer]
rights identifiers [set of simplenames]
22.2.1 – local PVC
Default: No PVC name Value: Simplename
Name of the PVC entity that represents the local end of the
connection.
22.2.2 – remote_dte_class
Default: No DTE class Value: Simplename
DTE class to be used when setting up the remote end of the
connection. It is only specified if the relayed PVC does not
reside on the local system.
22.2.3 – remote PVC
Default: No PVC name Value: Simplename
Name of the PVC entity that represents the remote end of the
connection.
22.2.4 – retry_limit
Default: 10 Value: 0-65535
Number of attempts that will be made to set up the PVC connection
following the failure of an enable command.
22.2.5 – retry_timer
Default: 60 Value: 1-65535
Interval, in seconds, between retries.
22.2.6 – rights_identifiers
Default: No rights Value: Set of simplenames
identifiers
Rights identifiers possessed by this entity. These rights are
used to access the local PVC and relayed PVC if it resides on the
local system.
23 – x25_server
23.1 – client
set [node node-id] x25 server client simple-name ...
Modifies the attributes of an x25 server client entity, which
represents the X.25 server that runs on a gateway system. The
X.25 server serves X.25 clients on accessing systems, providing
X.25 access to systems that do not have a direct connection to a
PSDN. The modifiable attributes and their data types (in brackets)
are:
account [latin1string] (OpenVMS)
application [end-user-specification]
destination [fullname] (OpenVMS)
filters [set of simplenames]
node [fullname]
outgoing session template [simplename] (OpenVMS)
password [latin1string]
service nodes [set]
user [latin1string]
23.1.1 – account (OpenVMS)
Default: No service/account data Value: Latin1String
Default service or account data to be used when connecting to the
system hosting the X.25 client. The account must be embedded in
quotes.
23.1.2 – application
Default: 36 Value: End-user-specification
Address information used by the destination Session Control
module to select the X.25 client that will receive the connection
request.
23.1.3 – destination (OpenVMS)
Default: No client name Value: Fullname
name
Name of the X.25 client to which a connection is to be made when
delivering a "filtered" call.
23.1.4 – filters
Default: No default Value: Set of simple names
Set of filters to be used by the server to filter calls for
this X.25 client. Each name is the name of an x25 access filter
entity.
23.1.5 – node
Default: No node name Value: Fullname
Name of the node that hosts the X.25 client to which connection
is to be made. This characteristic is supported only if the
service nodes characteristic is not supported.
23.1.6 – outgoing session template (OpenVMS)
Default: Default template Value: Simplename
Transport template to be used by the X.25 server to set up a
session control connection to the X.25 client. The name is the
name of an osi transport template entity.
23.1.7 – password
Default: No password Value: Latin1String
Default password to be used for verification when connecting
to the system that hosts the X.25 client. You cannot
display this characteristic with the show command. On OpenVMS
the password must be embedded in quotes.
23.1.8 – service nodes (OpenVMS)
Default: Empty set Value: Set of candidate records
Set of nodes that host the x25 client entities to which
connections can be made. Each candidate record consists of a
Rating, which is an integer, and a Node, which is specified as a
fullname.
23.1.9 – user
Default: No user id Value: Latin1String
Default user identification to be used in access verification
when connecting to the system that hosts the X.25 client. On
OpenVMS, the user id must be embedded in quotes.
23.2 – security_nodes
set [node node-id] x25 server security nodes simple-name ...
Modifies the attribute of an x25 server security nodes entity,
which defines a set of rights identifiers associated with calls
issued by the X.25 Access module at the gateway system. These
rights identifiers are used when making access control checks on
the DTE class specified when a call is made.
The modifiable attributes and their data types (in brackets) are:
nodes [set of fullnames]
rights identifiers [set of simplenames]
23.2.1 – nodes
Default: No node Value: Set of fullnames
names
DNS full names of accessing systems, or the wildcard full name.
Note, when managing entities on an OpenVMS system, this name must
be a Phase IV node name.
23.2.2 – rights_identifiers
Default: No rights Value: Set of simplenames
identifiers
Set of rights identifiers to be associated with the set of nodes
named in the nodes characteristic for purposes of access control
to DTE classes at the gateway node.
24 – xot (OpenVMS Alpha)
set [node node-id] xot maximum connections integer
Modifies the number of X.25 Over TCP/IP (XOT) connections
allowed. Note that each XOT SAP LINK entity is limited to
4095 connections. This Maximum Connections attribute sets the
limit for connections over all existing XOT SAP LINK entities.
The integer must be in the range 1-65535, and the default
value is 256.
Example:
set xot maximum connections 128
SAP is a subentity of the XOT module.
24.1 – sap
set [node node-id] xot sap sap-name ...
Modifies the attributes of a XOT SAP entity, which represents the
point at which the XOT entity gains access to the TCP/IP
environment for the purposes of listening for inbound XOT
connections. The sap-name is a simple name that uniquely
identifies a particular SAP instance. The modifiable attributes
and their data types (in brackets) are:
local IP address [ip-address]
local RFC1613 port number [integer]
By default, XOT's single SAP entity is configured to listen
on all available IP interfaces (as specified by the local IP
address 0.0.0.0). You can create multiple SAP entities, each
listening on a unique IP address. However, if you create
more than one SAP entity, you must assign each entity a
unique IP address; no SAP entity can use the 0.0.0.0 address.
In other words, you may do this:
set xot sap sap-0 -
local ip address 0.0.0.0
or this:
set xot sap sap-0 -
local ip address 123.23.49.235
set xot sap sap-1 -
local ip address 123.23.49.236
but not this:
set xot sap sap-0 -
local ip address 0.0.0.0
set xot sap sap-1 -
local ip address 123.23.49.236
LINK is a subentity of XOT SAP.
24.1.1 – link
set [node node-id] xot sap sap-name link link-name...
Modifies the attributes of a XOT SAP LINK entity, which
represents a remote system with which XOT is allowed to
communicate. In the case of an inbound XOT connection,
there must be a LINK entity with a matching remote IP address
and a remote port number in order for XOT to accept the
TCP/IP connection. In the case of an outbound connection,
the LINK entity specifies the remote IP address and remote
port number of the system with which to attempt the TCP/IP
connection.
The sap-name and link-name are simple names which uniquely
identify particular SAP and LINK instances. The modifiable
attributes of a XOT SAP LINK entity are (with data types in
brackets):
remote IP address [ip-address]
remote RFC1613 port number [integer]
Examples:
set xot sap sap-0 link link-0 -
remote ip address 125.65.82.34
set xot sap sap-0 link link-0 -
remote rfc1613 port number 1998
24.1.1.1 – remote_ip_address
Default: 0.0.0.0 Value: IP address
Specifies the remote IP address of the cooperating
XOT system that implements RFC1613. The IP
address is specified as a numeric address in the
form a.b.c.d. Specify the address 127.0.0.1 for
loopback testing. For more information on TCP/IP
loopback testing, see the TCP/IP Services for
OpenVMS documentation.
24.1.1.2 – remote_rfc1613_port_number
Default: 1998 Value: TCP port number
Specifies the TCP port number to use for an outgoing
connection.
The remote system must be listening for inbound XOT
connections on this port. In other words, the
remote system must have a SAP with this port as its
Local RFC1613 Port Number.
24.1.2 – local_ip_address
Default: 0.0.0.0 Value: IP address
The IP interface (identified by the address) where the SAP
entity will listen. The default of 0.0.0.0 specifies that the
SAP should listen on any available IP interface.
You may choose to create one or more SAP entities to listen on
specific IP interfaces. However, if multiple SAP entities are
in use, then none of them can use the local ip address of
0.0.0.0.
24.1.3 – local_rfc1613_port_number
Default: 1998 Value: TCP port number
The port number on which the SAP entity will listen for
inbound XOT connections. HP strongly recommends that you
use the value 1998 as specified in RFC1613.