27.2.5 – pvc
show [node node-id] x25 protocol -
dte dte-name -
pvc pvc-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
Examples:
show x25 protocol dte dte-1 pvc * name, channel
show x25 protocol dte dte-1 pvc PVC-1 all
27.2.5.1 – Characteristics
o acl
Default: No access Value: Access-control-list
control list
Access control list that controls access to this PVC.
o channel
Default: No default Value: 0-4095
Concatenated logical channel group and logical channel number
for the PVC. The value of this characteristic derives from an
argument to the create command.
o 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.
o 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.
27.2.5.2 – Counters
These counters record values over the lifetime of a PVC. For
counters that refer to use of the PVC by individual clients, see
the x25 access port entity.
o accesses blocked
Number of times an attempt to open a PVC has failed because of
security.
o creation time
Time at which this entity was created.
o data octets received
Number of octets received by the PVC since it was created.
o data octets sent
Number of octets sent by the PVC since it was created.
o data pdus received
Number of data PDUs received by the PVC since it was created.
o data pdus sent
Number of data PDUs sent by the PVC since it was created.
o pvc failures
Number of times the PVC has failed while the entity has been
allocated.
27.2.5.3 – Identifier
o name
Simple name assigned to the PVC when it is created.
27.2.5.4 – Status
o allocated
True if the PVC is allocated to a user. False if otherwise.
o port
X25 Access port with which the PVC is associated.
o uid
Entity's unique identifier, which is generated when the entity is
created.
27.3 – group
show [node node-id] x25 protocol -
group group-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
Examples:
show x25 protocol group * name, type
show x25 protocol group GROUP-0 all
27.3.1 – Characteristics
o 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.
o remote dte address
Default: No DTE address Value: DTE-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.
o type
Default: BCUG Value: CUG, BCUG, or CUGOA
Type of the CUG.
cug Normal CUG.
bcug Bilateral CUG.
cugoa CUG outgoing access.
27.3.2 – Counters
o creation time
Time at which this entity was created.
o incoming calls blocked
Number of times that an incoming call to a bilateral CUG has been
blocked by security from accessing a filter.
o outgoing calls blocked
Number of times that a call has been blocked by security from
accessing this bilateral CUG.
27.3.3 – Identifier
o name
Simple name assigned to the group when it is created.
27.3.4 – Status
o uid
Entity's unique identifier, which is generated when the entity is
created.
28 – x25 relay (Alpha)
show [node node-id] x25 relay attribute [,attribute...]
all [attributes]
all characteristics
28.1 – Characteristics
o maximum active connections
Maximum number of active connections supported by this module.
This characteristic is an optional argument on the create
command. You cannot modify this characteristic.
o version
Version number of the X.25 Relay architecture to which this
implementation conforms. You cannot modify this attribute.
28.2 – client
show [node node-id] x25 relay -
client client-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
28.2.1 – Characteristics
o DTE class
Default: No DTE class Value: Simple-name
Name of the x25 access DTE class entity to use when making the
outgoing call.
o 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.
o rights identifiers
Default: No rights identifiers Value: Set of simple names
Set of rights identifiers that this client possesses. It is used
when placing the outgoing call.
o template
Default: No template Value: Simple name
Name of the x25 access template entity to be used for the
outgoing call.
28.2.2 – Counters
o connections failed
Number of times that a connection setup has failed.
o connections lost
Number of times that a successfully established connection has
been abnormally terminated.
o connections made
Number of connections that have been made successfully.
o creation time
Time at which this entity was created.
28.2.3 – Identifier
o name
Simple name assigned to the client when it is created.
28.2.4 – Status
o active connections
Number of connections that are currently active on this client. A
connection is a pair of incoming/outgoing calls. This value does
not include connections that are still waiting to be established.
o state
Specifies the state of the x25 relay client entity.
off The entity is disabled.
on The entity is enabled.
o uid
Entity's unique identifier, which is generated when the entity is
created.
28.3 – pvc
show [node node-id] x25 relay -
pvc pvc-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
28.3.1 – Characteristics
o local PVC
Default: No PVC name Value: Simple name
Name of the PVC entity that represents the local end of the
connection.
o remote DTE class
Default: No DTE class Value: Simple name
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. This attribute is only applicable
to connector nodes, and will not be visible in other
implementations.
o remote PVC
Default: No PVC name Value: Simple-name
Name of the PVC entity that represents the relayed end of the
connection.
o 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. This attribute is
only applicable to connector nodes, and will not be visible
in other implementations.
o retry timer
Default: 60 Value: 1-65535
Interval, in seconds, between retries. This attribute is only
applicable to connector nodes, and will not be visible in
other implementations.
o rights identifiers
Default: No rights identifiers Value: Set of simple names
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.
28.3.2 – Counters
o connections made
Number of successful connections made by this entity.
o creation time
Time at which this entity was created.
o times connections lost
Number of times that a successfully established PVC connection
has been abnormally terminated.
o times retry limit exceeded
Number of times that the retry limit has been reached when trying
to set up a PVC connection.
28.3.3 – Identifier
o name
Simple name assigned to the PVC when it is created.
28.3.4 – Status
o state
State of the x25 relay pvc entity.
failed The retry mechanism has failed to set up the connection.
off The PVC is disabled.
on The PVC is enabled.
retrying The Retry timer is running.
o uid
Entity's unique identifier, which is generated when the entity is
created.
29 – x25_server
show [node node-id] x25 server attribute [,attribute...]
all [attributes]
all characteristics
all counters
all status
29.1 – Characteristics
o incoming session template (Tru64 UNIX)
The Session Control template specified on an OpenIncoming
invocation at the End User Session Control interface. You cannot
modify this characteristic.
o maximum session connections
Default: 512 Value: [1..65535]
Maximum number of session control connections with clients that
the entity can support. This includes both incoming and outgoing
connections. You cannot modify this characteristic.
o version
Default: Current version number
Version number of the X.25 Gateway Access Protocol to which the
implementation conforms. You cannot modify this characteristic.
29.2 – Counters
o connection attempts failed
Number of session control connection requests to clients that
have failed, due either to exceeding the maximum number of
connections or rejection by X.25 clients in accessing systems.
o creation time
Time at which this entity was created.
o times session control unavailable
Number of times the session control unavailable event was raised.
29.3 – Status
o active inbound session connections
Current number of active inbound session control connections with
clients.
o active outbound session connections
Current number of active outbound session control connections
with clients.
o state
Current state of the x25 server entity.
off The x25 server entity is disabled.
on The x25 server entity is enabled.
o uid
Specifies the entity's unique identifier, which is generated when
the entity is created.
29.4 – client
show [node node-id] x25 server -
client client-name attribute [,attribute...]
all [attributes]
all characteristics
all identifiers
all status
29.4.1 – Characteristics
o account (OpenVMS)
Default: No service/account data Value: String
Default service or account data to be used when connecting to the
system hosting the X.25 client.
o 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.
o destination (OpenVMS)
Default: No client name Value: Full-name
Name of the X.25 client to which a connection is to be made when
delivering a "filtered" call.
o 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.
o node
Default: No node name Value: Full-name
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.
o outgoing session template (OpenVMS)
Default: Default template Value: Simple-name
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.
o password
Default: No password Value: String
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.
o service nodes (Tru64 UNIX)
Default: Empty set Value: Set of candidate records
Set of nodes that host the x25 client entities to which
connections can be made.
o user
Default: No user id Value: String
Default user identification to be used in access verification
when connecting to the system that hosts the X.25 client.
29.4.2 – Identifier
o name
Simple name assigned to the client when it is created.
29.4.3 – Status
o state
Status of the x25 server client entity.
off The x25 server client entity is disabled.
on The x25 server client entity is enabled.
29.5 – security_nodes
show [node node-id] x25 server -
security nodes simple-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
29.5.1 – Characteristics
o nodes
Default: No node names Value: Set of full-name
DNS full names of accessing systems, or the wildcard full name.
o rights identifiers
Default: No rights identifiers Value: Set of simple names
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.
29.5.2 – Counters
o creation time
Time at which this entity was created.
o outgoing calls blocked
Number of times that an attempt to establish a call or use a PVC
has failed for security reasons.
29.5.3 – Identifier
o name
Simple name assigned to the security node when it is created.
29.5.4 – Status
o uid
Entity's unique identifier, which is generated when the entity is
created.
30 – xot (OpenVMS Alpha)
Shows the X.25 Over TCP/IP module and its attributes.
show [node node-id] xot attribute [,attribute...]
all [attributes]
all characteristics
all status
Examples:
show xot currently active connections
show xot maximum connections
PORT and SAP are subentities of XOT.
30.1 – Characteristics
o version
The version of the XOT implementation, initially "1.0.0".
You cannot modify this characteristic.
o maximum connections
Default: 256 Value: 1-65535
The maximum number of connections allowed. Note that each
XOT SAP LINK entity is limited to 4095 connections. The
Maximum Connections attribute sets the limit for connections
over all existing XOT SAP LINK entities.
30.2 – Status
o uid
The universal identifier of the XOT module, which is generated
when the entity is created.
o currently active connections
The number of currently active XOT connections, that is, the
number of XOT PORTs.
30.3 – port
Shows a XOT PORT entity which provides information on an
active XOT connection over TCP/IP. Ports are created and
deleted dynamically as X.25 connections are requested.
show [node node-id] xot -
port port-name attribute [,attribute...]
all [attributes]
all counters
all identifiers
all status
The port-name can be either a wildcard, or it can be a
simple name that uniquely identifies a particular port
instance. XOT port-names are automatically created in
the form XOT-port-xxxx, where xxxx is a 4 digit
hexadecimal value indicating the port number.
Examples:
show xot port * client, link, direction
show xot port XOT-port-0000 all
30.3.1 – Counters
o creation time
The time that the port entity was created.
o octets received
The number of data octets received from TCP/IP for the port.
o octets sent
The number of data octets sent to TCP/IP from the port.
o pdus received
The number of data PDUs (X.25 packets) received from TCP/IP.
o pdus sent
The number of data PDUs (X.25 packets) sent to TCP/IP.
30.3.2 – Identifiers
o name
The simple name assigned to the port when it was created. It
will consist of xot-port-xxxx, where xxxx is the hexadecimal
representation of the connection id.
30.3.3 – Status
o client
The client of the port, that is, the name of the X25
PROTOCOL DTE entity.
o link
The XOT SAP LINK entity with which this port is associated.
o protocol state
The state of the XOT protocol over this port:
Idle The port is idle.
Running The port is running.
Connecting The entity is making an X.25 connection.
Failed The port connection failed.
o direction
Whether the port is inbound or outbound.
o type
The type of X.25 connection: PVC or SVC.
o uid
The universal identifier of the PORT entity, which is generated
when the entity is created.
30.4 – sap
Shows a XOT SAP entity which specifies the point at which
the XOT entity gains access to the TCP/IP environment for
the purposes of listening for inbound XOT connections.
show [node node-id] xot -
sap sap-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
The sap-name can be either a simple name that uniquely
identifies a particular SAP instance, or a wildcard
to identify multiple SAP instances.
Examples:
show xot sap * all
show xot sap sap-0 local ip address, state
LINK is a subentity of XOT SAP.
30.4.1 – link
Shows a XOT SAP LINK entity which represents a remote
system with which XOT is allowed to communicate.
show [node node-id] xot -
sap sap-name link link-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
The sap-name must be a simple name which uniquely
identifies a particular SAP instance. The link-name
can be either a simple name that uniquely identifies
a particular LINK instance, or a wildcard to identify
multiple LINK instances.
Examples:
show xot sap sap-0 link * remote IP address, state
show xot sap sap-0 link link-0 all
30.4.1.1 – Characteristics
o 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.
o 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.
30.4.1.2 – Counters
o creation time
The time that the XOT SAP LINK entity was created.
o connects sent
The number of connection requests sent.
o connects received
The number of connection requests received.
o disconnects sent
The number of disconnect requests sent.
o disconnects received
The number of disconnects received.
o octets sent
The number of data octets sent from TCP/IP for
all ports on the link.
o octets received
The number of data octets received from TCP/IP
for all ports on the link.
o pdus sent
The number of X.25 packets sent from TCP/IP
for all ports on the link.
o pdus received
The number of X.25 packets received from TCP/IP
for all ports on the link.
o connects failed
The number of times an attempt to establish an
outgoing connection failed.
o link state changed
The number of times that the link has changed
state from enabled to disabled or disabled to
enabled.
o protocol errors
The number of protocol errors that occurred.
30.4.1.3 – Identifiers
o name
The simple name assigned to the LINK entity
when it was created.
30.4.1.4 – Status
o state
The state of the LINK entity:
On The LINK is enabled
Off The LINK is disabled
o uid
The universal identifier of the LINK entity,
which is generated when the entity is created.
30.4.2 – Characteristics
o local IP address
Default: 0.0.0.0 Value: IP Address
The IP interface (identified by the address) where the
SAP entity will listen. Any available interface is
specified with the address of 0.0.0.0. This characteristic
is mainly set when a system has multiple TCP/IP interfaces.
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.
o 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.
30.4.3 – Counters
o creation time
The time that the XOT SAP entity was created.
o connections rejected
The number of times an inbound connection was rejected.
o sap state changed
The number of times that the SAP entity state changed.
30.4.4 – Identifiers
o name
The simple name assigned to the SAP entity when it was created.
30.4.5 – Status
o state
The state of the SAP entity:
On The entity is enabled.
Off The entity is disabled.
Connecting To PWIP The entity is connecting to TCP/IP.
o uid
The universal identifier of the SAP entity, which is generated
when the entity is created.