OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-22
NSP Process Problems: X25AM
trace process $tsp2, to tr1
While the trace is running, rerun the application. You can see that the transport
connection is successful.
Stop the trace:
trace process $tsp2, stop
Use PTrace to analyze the trace. This time you need to look only at the TPDUs, filtering
for Layer 4.
The SCF command
ptrace from tr4; select L4
displays the following:
The following PTrace command records all the trace records selected:
record all
The following are the two trace records of interest:
Records #49 and #63 show that the CR-TPDU was accepted and that a CC-TPDU was
sent in response.
NSP Process
Problems: X25AM
X25AM acts as the service provider for the TSP process, and supplies the Data Link
Layer and Physical Layer as well.
•
Common problems to look for are the following:
Trace of: \MARS.$TSP2, Type (55,4).
Ptrace Data File: $OSI.DIAG.TR4
Trace started: 10/10/91 04:38:29.230451
First trace entry: 10/10/91 04:38:29.241723
Last trace entry: 10/10/91 18:04:22.728070
Trace entry size limit: 520
10/10/91 16:07:20.380437 >000.000000 #49 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)
10/10/91 16:07:20.898392 >000.517955 #63 L4 TPDU OUT
CC-TPDU CDT: 4 Dst: 1 Src: 1 Class: 2 Ext-Frmt: NO Exp-Flwctl:
YES
TPDU Size:4096 Option:N-Expedited(NO) Option:Receive Conf(NO)
Option:No Checksum(NO) Option:T-Expedited(YES)