OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-28
Troubleshooting Example
Next you should take a look at the NSP statistics for Layer 3 to verify whether a
connection occurred. But first you need to find out the line name.
Either of the SCF commands
status su $tsp1.#z000022, detail
check su $tsp1.#z000022, detail
displays a status screen from which you can get the line name. An example screen is
included in the previous TSP example. In this case, the screen would show that the line
name is $X251.
Now you can check the NSP statistics.
The SCF command
stats line $x251
displays the following:
This screen shows that a call request packet was initiated by Layer 3. It also shows that
the remote side responded with a clear packet, and that the Network Layer never
progressed into data transfer phase. From this information you can assume that the
problem is in the X25AM process.
X25AM STATS Line $X251
Resettime 5:21:41.013 10/10/91 Sampletime 5:25:05.064 10/10/91
Line Quality 100 Modem Error 0 Modem Overrun 0
[ Packet Level Information ]
Data Call Clear Reset Rstrt Intrp Diag RR RNR REJ
Send 0 1 0 0 0 0 0 0 0 0
Rcvd 0 0 1 0 0 0 0 0 0 0
[ Confirmation Packets ]
Send 0 1 0 0 0
Rcvd 0 0 0 0 0
Total Sent 1 Total Rcvd 2 Invalids Rcvd 0 Discarded
0
[ Frame Level Information ]
For 6100/6105 Subsystem:
I^P I^NOP RR RNR REJ SREJ SABM DISC FRMR UA DM
Send 0 0 0 0 0 0 0 0 0 0 0
Rcvd 0 0 0 0 0 0 0 0 0 0 0
For NON-6100/6105 Subsystem:
I S U
Send 1 14 0
Rcvd 2 26 0
[ LIU Errors ] [ DRIVER info ]
FCS 0 Modem 0 Length 0 Overruns 0 BCC Errs 0 Frames 0
T1 0 Nobuf 0 Addrs 0 Rvc Abrt 0 No Buffs 0 Errors 0
[ Buffer Pool Information in pages ]
Size 512 In use 3 High Water 4 Failures 0