OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-14
Troubleshooting Example
SELECT L4; FILTER L4SERVICES; NEXT
A typical record displayed by this command is as follows:
You can check specific TPDUs by specifying them in the FILTER command. The
following command specifies all CR-TPDUs, DR-TPDUs, and ER-TPDUs:
SELECT L4; FILTER TPDU CR, DR, ER
The following command lists the Network Layer primitives traced by the TSP process:
SELECT L3; FILTER L3SERVICES
A typical record displayed by this command is as follows:
If you determine that errors are coming from the NSP process, you can find them using
the command:
SELECT NETIO
To further analyze the cause of these errors, you have to trace the X25AM or
TLAM/PAM process.
The following command displays the IPPDUs for TLAM/PAM NSP processes:
SELECT L3; FILTER IPPDU
You can also select routing messages (an ES-IS routing exchange protocol feature) by
using the following command:
SELECT L3; FILTER RTPDU
Troubleshooting Example
The following is a TSP problem you might encounter. The steps in this example
illustrate the logic you might follow when using a top-down problem-solving approach.
Symptoms
In this example the application is waiting to accept an incoming transport connection.
Connect requests are coming into the subsystem from a remote entity, but for some
reason, the application continues to wait for the completion of the request. There are no
instances of errors returned, either to the application or to the console log.
1. The following steps are used to solve this problem:
2. Reset the statistics counters and rerun the application.
17:11:52:960 >000.040 #19 T-Primitive
T-CON attach BufLen: 0 Addr: 1930676 SU: #Z000006
17:11:53:780 >000.000 #44 L3 Primitive
N-DATA indication NCB Index: 0 Buflen: 30 Addr: 1929808 SU: #TSP1004