OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-29
Troubleshooting Example
Step 4: Collect Trace Information, Using SCF
To find out the real nature of the problem, you need to generate a trace. Since you have
narrowed the problem down to the Network Layer, you can concentrate on tracing the
X.25 LINE object only. The following SCF command starts the trace:
trace line $x251, to trx1
While the trace is running, rerun the application.
After recording the problem, be sure to stop the trace. The following SCF command
stops the trace:
trace line $x251, stop
Step 5: Analyze the Trace, Using PTrace
The SCF command
ptrace from trx1; select l3
starts the PTrace trace formatter on the trace in TRX1, selects the Layer 3 mask, and
displays the following:
The following PTrace command records all the trace records selected by the select mask:
record all
The following are the trace records selected by PTrace:
Record #37 shows the call request packet. The two fields after the call request are the
SNPA addresses (X.25 subnetwork addresses), each 12 digits long (%HCC). The called
address (X25DESTADDR) is 408333222203. The calling address (SOURCEADDR
Trace of: \MARS.$X251, Type (61,0).
Ptrace Data File: $DIAG.MYSTUFF.TRX1
Trace started: 10/10/91 05:23:05.741230
First trace entry: 10/10/91 05:23:05.925310
Last trace entry: 10/10/91 05:24:20.375450
Trace entry size limit: 128
05:23:13:390 >000.000 #37 L3 Pkt Out
SDN #001/%001 LEN #0024 GFI(0001) MOD8 LGN/LCN $001
Call^req
000: 1001 0BCC 4083 3322 2203 4083 3311 1102
008: 0343 0202 0000 0000
CALLED ADDRESS ($C) 408333222203
CALLING ADDRESS ($C) 408333111102
FACILITIES ($03)
CCITT STANDARD X.25 FACILITIES ---
WINDOW SIZE FROM CALLED DTE: 02 FROM CALLING DTE: 02
USER DATA ($04) 00000000