OSI Troubleshooting Guide, May 1997

Chapter 1 33
Interoperability Testing
Interpreting Transport Errors
Interpreting Transport Errors
The following are possible situations you may currently find yourself in.
Transport problem corrected.
If you have made a change that corrected your Transport problem, then
return to the Service Layer test that originally failed and try again.
Configuration or other change required.
If the corrective action in the following sections require you to change a
configuration parameter or make some other change, then do so and
rerun the Transport test.
Problem persists.
If you have been unsuccessful in correcting the problem, gather the
information you have collected to provide to your HP support
representative.
Table 1-4 Transport Call Errors
Error Reason Action
t_open() The stack is most likely
not up.
Run status operation under
Transport menu.
t_bind() Failed to associate an
address with the transport
endpoint. Likely a
parameter error. Link
supporting this address
went down.
Verify that the parameter
tp_my_tsap is set to “diagt” or
diagt.NSAP” where NSAP is
valid local address. Run status
operation under Transport menu.
t_rcvdis() Called to decode a
disconnect indication.
Check online error messages.
t_look() Remote stack does not
respond for default time.
Check to see if one node is
configured as NULL internet and
other is not. Check for incorrect
remote network address.