OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-20
Troubleshooting Example
Record #70 indicates that the CR-TPDU is answered with a DR-TPDU. The reason
given is that there is no Session Layer entity (in other words, no transport user) to accept
the connection request.
So far, you have established that:
•
The TSP process refused an incoming connection.
•
The reason is that there is no transport user to accept the connection.
The transport protocol specification requires that the various connection attributes be
qualified by the receiving side before the connection is accepted. In this case, one of the
attributes must be unacceptable.
All of the parameters to be negotiated are broken down by PTrace in the CR-TPDU and
CC-TPDU fields of the SELECT L4; FILTER TPDU command.
The PTrace record #66 displays the parameters of the CR-TPDU, as follows:
These values need to be verified against the SCF attributes. Table 4-1
shows the
correspondences between the PTrace display of the negotiation parameters and the SCF
attributes.
To find out how the TSP subdevice attributes are configured, use the SCF INFO
command.
The SCF command
10/10/91 15:28:52.219646 >000.048340 #66 L4 TPDU IN
CR-TPDU CDT: 4 Dst: 0 Src: 1 Class: 2 Ext-Frmt: NO Exp-Flwctl: YES
Calling TSAP:(hex) 3231 30 Called TSAP:(hex) 3031 32 TPDU Size:4096
Version: 1 Option:N-expedited(NO) Option:Receive Conf(NO)
Option:No Checksum(NO) Option:T-Expedited(YES)
Table 4-1. Negotiation Parameters: PTrace Display vs. SCF Attributes
PTrace Negotiation Parameters SCF Attributes
CDT L4window
Class Class, Altclass
Ext-Frmt Extendedformat
Exp-Flwctl (not applicable)
Calling TSAP (not applicable on ATTACH)
Called TSAP Localtsel
TPDU Size TPDUsize
Version (not applicable)
Protection Recvsecurity (on ATTACH)