OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-46
Troubleshooting Example
Record #57 shows the incoming CR-TPDU. The attributes include the TSAP IDs,
TPDU size, and the security protection field.
Record #58 indicates that the state machine has begun to verify the CR-TPDU
(A4^CHK^CR).
Record #59 indicates that the state machine rejected the CR-TPDU
(E4^CO2^CR^NOT^ACCEPTABLE).
Record #62 indicates that the TSP process responded to the incoming CR-TPDU by
sending a DR-TPDU with the reason negotiation failed.
And finally, record #83 indicates that a DC-TPDU is received in response to the
DR-TPDU. Now you know what kind of TPDUs were indicated on the Layer 4 STATS
SERVICE screen in the TPDUs-sent and TPDUs-received fields.
Results of Diagnostics
So far, you have established that:
•
The TSP process refused an incoming connection.
•
The reason is that the negotiation failed.
Connection negotiation is done during the connection-establishment phase. 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.
10/16/91 04:36:04:920 >000.010 #58 L4 SM
TCB: 1 Class: 2 S4^CO2^WFCR
:E4^CO2^TP^CR =>A4^CHK^CR SU: #Z00001S
10/16/91 04:36:04:920 >000.000 #59 L4 SM
TCB: 1 Class: 2 S4^CO2^WFCR1
:E4^CO2^CR^NOT^ACCEPTABLE
=>A4^SND^DR^DISCIND^NEGOT^TMTS2 SU: #Z00001S
10/16/91 04:36:04:920 >000.000 #62 L4 TPDU OUT
DR-TPDU Dst: 0 Src: 1 Reason: Negotiation failed
000: 0680 0000 0001 8200
10/16/91 04:36:04:980 >000.000 #83 L4 TPDU IN
DC-TPDU Dst: 1 Src: 0
000: 05C0 0001 0000