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.