OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-57
Troubleshooting Example
The SCF command
stats service $tap1.#l5
displays the following:
This screen shows that no SPDUs were sent or received by the TAPS process. This
indicates that the problem is not due to the TAPS process, and implies that the problem
originates in a lower layer.
Next, look at the service statistics for Layer 4 to verify whether a transport connection
occurred. The TSP names come from the STATUS SU command you did earlier on the
TAPS process.
OSIAS Stats SERVICE \MARS.$TAP1.#L5
Reset Time.... 15 Oct 1991, 13:39:46.637
Sample Time... 15 Oct 1991, 13:40:13.157
Refuse SPDUs: Received Threshold Sent Threshold
No reason.............. 0 -- 0 --
Permanent.............. 0 0 1 0
Temporary.............. 0 0 0 --
Other.................. 0 -- 0 --
Abort SPDUs:
No reason.............. 0 -- 0 --
Protocol Error......... 0 -- 0 0
Other.................. 0 -- 0 --
Connect SPDUs............ 0 0
Accept SPDUs............. 0 0
Disconnect SPDUs......... 0 0
Not Finished SPDUs....... 0 0
Finish SPDUs............. 0 0
Total Refuse/Abort SPDUs.... 0 0
Total SPDUs................. 0 0
Total SPDU Bytes............ 0 0
Total Data Bytes............ 0 0
Subdevice Summary:
Attach pending SUs...... 0
Active connection SUs... 0
Inactive (static) SUs... 0
Available SUs........... 100