21.2 – pvc
o pvc failed
Generated when an allocated PVC fails during the data phase.
Arguments:
cause Cause code provided by some DCEs on some failures.
diagnostic Diagnostic code provided by some DCEs on some
failures.
failure Why the PVC failed.
reason
DTE The local DTE was disabled by network
disabled management.
level 2 A failure occurred at the Frame level
failure link or below.
PVC The x25 protocol dte pvc entity has been
deleted deleted by network management.
restart Restart initiated by network or remote
DTE, or sent by this DTE.
22 – x25 relay (Alpha)
22.1 – client
o connection failed
Generated when a connection cannot be established.
Arguments:
call accept Error returned when attempting to accept the
reason incoming call. This argument is present only
if Reason is Call Accept Failure.
cleared by directive
invalid parameter
no such port
service not available
destination DTE address of the called DTE.
DTE
destination Called Address Extension supplied in the Call packet.
nsap
outgoing Error returned when attempting to make the outgoing
failure call. This argument is present only if Reason is
reason Outgoing Call Failure.
called address not reachable
cleared by directive
destination not known
DTE class members not active
DTE class not known
DTE class not specified
incompatible reserved lcn
invalid parameter
no such port
no such template
security failure
service not available
transit not allowed
reason Whether the connection failed at the incoming or
outgoing stage.
call accept The client could not accept the
failure incoming call.
outgoing The client could not make the
call failure outgoing call.
sending DTE address of the calling DTE.
DTE
sending Calling Address Extension supplied in the Call
nsap packet.
o connection lost
Generated when a connection that has been successfully etablished
is abnormally terminated.
Arguments:
cause X.25 cause code provided by the clearing DTE. Only
present if the Reason argument is Calling DTE Clear
or Called DTE Clear.
destination DTE address of the called DTE.
DTE
destination Called Address Extension supplied in the Call packet.
nsap
diagnostic X.25 diagnostic code provided by the clearing DTE.
Only present if the Reason argument is Calling DTE
Clear or Called DTE Clear.
network Reason why the connection was lost. This argument is
error present only if reason is network error.
reason
reason Reason for the loss of the connection.
calling The local call was abnormally
DTE clear terminated.
network The cause of the connection loss is
error given by network error reason.
called DTE The remote call was abnormally
clear terminated.
sending Specifies the DTE address of the calling DTE.
DTE
sending Specifies the Calling Address Extension supplied in
nsap the Call packet.
22.2 – pvc
o connection lost
Generated when a successfully established PVC connection fails
for some other reason than being disabled.
Argument:
reason Error returned by the X.25 Access module when
notifying the X.25 Relay module of the disconnection.
o retry limit exceeded
Generated when an attempt to set up a PVC connection fails.
Arguments:
local pvc State of the local end of the PVC connection.
status
relayed State of the relayed end of the PVC connection.
pvc status
23 – x25_server
o client connect failed
Generated when the X.25 server is unable to make a connection to
an X.25 client (or to any of an alternative set of X.25 clients
if the service nodes characteristic is supported for the x25
server client entity).
Arguments:
client Full name of the x25 server client entity.
nodes The node or set of nodes associated with the x25
server client entity.
application Application type in the client entity.
o session control unavailable
Generated when the X.25 server detects the absence of the Session
Control module or when it detects that the state of Session
Control is not set to on.
Arguments:
module True or false. Set to false when the X.25 Server
extent cannot detect the presence of Session Control. When
set false, the value of the session control port
state argument is always null.
session Null, off, shut, or restricted. Reflects the state
control returned by the Port State End User Interface when
port state the value of the module extent argument is set true.
24 – xot (OpenVMS Alpha)
24.1 – sap
o sap state changed
The XOT SAP state has changed. The new SAP state (on, off,
or connecting to PWIP) is an argument for this event.
o sap inbound connect failed
Indicates that an inbound connection attempt failed. The
event arguments are: failure reason, remote ip address,
remote port number, and pwip error code. Possible connect
failure reasons are:
Remote System Unreachable
Connection Rejected
Connection Timed Out
No Match for SAP Link
Maximum Connections Exceeded
Not Connected to PWIP
PWIP Error
No Reason Specified
24.1.1 – link
o link state changed
The XOT SAP LINK state has changed. The new XOT SAP LINK
state (on or off) is an argument for this event.
o outbound connect failed
Occurs when an attempt to establish an outbound connection
with a remote system fails. The event returns the
following arguments: Failure Reason, Remote IP Address,
Remote Port Number, and if the Failure Reason argument
indicates a PWIP Error, PWIP Error Code.
The Failure Reason agrument indicates why the connection
could not be made, the argument takes one of the following
values:
Remote System The XOT system could not reach the
Unreachable requested remote system.
Connection The XOT system was able to reach the
Rejected remote system. However, the remote
system denied the connection request.
PWIP Error During the connection establishment
process the XOT system received an
unexpected error from the PWIP software
it uses.
No Reason The XOT system could not establish a
Specified connection with the requested remote
system. No additional information is
available.
o protocol error
Indicates an error occurred in the XOT protocol during a
XOT protocol exchange with the remote system. The event
returns the following arguments: Error Reason, Remote
IP Address, Remote Port Number, and Received PDU.
The Error Reason argument indicates what type of protocol
error was detected; the argument takes one of the
following values:
Invalid XOT The XOT system received a PDU apparently
Header destined for the XOT software, but the
XOT header was not valid.
Invalid PVC While attempting to establish a PVC
Setup Packet connection with the remote system, the
remote system returned an invalid
response PDU. This error can also occur
if the remote system attempts to
establish a PVC connection with the
local system and the PVC connection PDU
is invalid.