HP HP-UX 11i Troubleshooting

HP OSI Troubleshooting Guide

HP 9000 Networking

Edition 6

32070-90031

E0597

Printed in: United States

Legal Notices

The information in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and ﬁtness for a particular purpose. Hewlett-Packard

shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Warranty. A copy of the speciﬁc warranty terms applicable to your Hewlett- Packard product and replacement parts can be obtained from your local Sales and Service Ofﬁce.

Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies.

Hewlett-Packard Company 3000 Hanover Street Palo Alto, California 94304 U.S.A.

Use of this manual and ﬂexible disk(s) or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited.

written permission is prohibited, except as allowed under the copyright laws.

This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California.

©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation ©copyright 1990 Motorola, Inc. ©copyright 1990, 1991, 1992 Cornell University ©copyright 1989-1991 The University of Maryland ©copyright 1988 Carnegie Mellon University

Trademark Notices

UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.

X Window System is a trademark of the Massachusetts Institute of Technology.

MS-DOS and Microsoft are U.S. registered trademarks of Microsoft Corporation.

OSF/Motif is a trademark of the Open Software Foundation, Inc. in the U.S. and other countries.

Contents

1. Interoperability Testing

Testing FTAM Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

FTAM Interoperability Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

FTAM Pre-Test Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

FTAM Interoperability Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

FTAM Connectivity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

FTAM File Transfer Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Interpreting FTAM Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Testing APRI Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

APRI Pretest Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Running APRI Tests (Client Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Running APRI Tests (Server Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Interpreting APRI Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Testing Session Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Session Pre-Test Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Running Session Tests (Client Mode). . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Running Session Tests (Server Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Interpreting Session Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Testing Transport Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Transport Pre-Test Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Running Transport Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Interpreting Transport Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Testing LAN (802.3 or FDDI) Interoperability . . . . . . . . . . . . . . . . . . . .34

LAN Pre-Test Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Contents

Running LAN Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Interpreting LAN Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Testing X.25 Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

X.25 Pre-Test Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Running X.25 Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Interpreting X.25 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Reason and Refuse Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Protocol Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Session Refuse Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

To Create A Result File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2. Problem Solving

Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Interpreting Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Checking System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Status Check 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Status Check 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Status Check 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Status Check 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Status Check 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Running Veriﬁcation Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Link Veriﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

OTS Transport Veriﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Service Veriﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Collecting Troubleshooting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Tracing and Logging through /opt/ots/bin/osidiag . . . . .62

Tracing and Logging User Applications . . . . . . . . . . . . . . . . . . . . . . . 63

Contents

Common Conﬁguration Mistakes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

ots_dests Common Mistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

ots_subnets Common Mistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

ots_parms Common Mistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

local_app Common Mistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

remote_app Common Mistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Common Logged Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Submitting Problem Information to HP. . . . . . . . . . . . . . . . . . . . . . . . . .70

3. Using OSI and OTS Tools

OSIADMIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Managing Your Conﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Using osiconf . . . . . . . . . . . . . . . . . . . .74

Using osiconfchk . . . . . . . . . . . . . . . . . . .74

OSI Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Starting and Stopping OSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

osistart Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Stopping OSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

osistat Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Starting OTS: otsstart . . . . . . . . . . . . . . . . .80

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Recovering from otsstart Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Checking OTS Status: otsstat . . . . . . . . . . . . . . .82

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Contents

Updating OTS: otsupdate . . . . . . . . . . . . . . . .84

Dynamic Routing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

End System Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Intermediate System Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

ES/IS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Route Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Route Command Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Route Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

NSAP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Printing History

The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. the manual part number will change when extensive changes are made.

Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details.

Edition 1 June 1989 Edition 2 April 1991 Edition 3 March 1992 Edition 4 January 1995 Edition 5 July 1996 Edition 6 May 1997

1 Interoperability Testing

Processes for verifying and troubleshooting communication between your local HP node and another node on the network.

Interoperability Testing

Testing FTAM Interoperability

Use the following procedures to test FTAM Interoperability.

FTAM Interoperability Testing

1. Log on as root.

2. Perform the pre-test checklist.

3. Create a result ﬁle.

4. Perform FTAM tests.

5. If osidiag cannot ﬁnd a default local application title, perform “Specifying Application Titles.”

6. Interpret errors.

12 Chapter 1

FTAM Pre-Test Checklist

Check the following before attempting to run the FTAM tests.

Figure 1-1 FTAM Pre-Test Checklist

Interoperability Testing

FTAM Pre-Test Checklist

Is the local stack running over the appropriate link?

Yes

Is the FTAM

responder daemon running?

Yes

Is the remote stack running?

Yes

Is the FTAM service

running on the remote?

Yes

Is FTAM logging enabled?

Yes

Start the local stack.

Start FTAM.

Start the remote stack.

Start FTAM on the remote.

Start logging. Type:

/usr/sbin/nettl -start

Determine Presentation Address. Includes P-Selector, S-Selector, T-Selector, and Network Address.

Start the FTAM Tests.

Chapter 1 13

Interoperability Testing

FTAM Interoperability Testing

This procedure invokes FTAM through osidiag to provide as much information as possible about errors that might occur.

FTAM Connectivity Test

The steps below describe how to test FTAM connectivity between the local and remote node.

1. From root, type osidiag and select “FTAM TESTS.”

2. Create a result ﬁle.

3. Select “Connect” from the FTAM menu.

4. Enter Initiator Identiﬁcation (your login information for the remote node).

• Change ID ﬁeld from local login name to remote unless login on

remote is the same.

• Enter initiator password associated with remote login.

5. Press Done.

6. Enter Presentation Address for remote node.

7. Go to the “FTAM File Transfer Test” on page 15.

14 Chapter 1

Interoperability Testing

FTAM Interoperability Testing

FTAM File Transfer Test

After a successful FTAM connect test. Follow the steps below to do an FTAM ﬁle transfer.

1. From the FTAM menu, create a new result ﬁle.

2. Select “Low Level Transfer.”

3. The initiator ID parameters are displayed. a. Leave ﬁrst ID set to local login.

b. Set ﬁrst password to your local password. c. Leave second set unchanged. d. Press Done.

4. Leave source Presentation address unchanged. Press Done.

5. Leave destination address unchanged. Press Done.

6. If your system has a “message of the day” conﬁgured, leave the source and destination ﬁle names unchanged. If your system does not have a “message of the day” conﬁgured, overwrite the source ﬁle name with a valid name.

7. Check “TEST STATUS” near the end of the report. If the status is “PASSED,” FTAM veriﬁcation is complete. If the status is “FAILED,” see “Interpreting FTAM Errors” on page

16, make your corrections, then re-run this test.

Chapter 1 15

Interoperability Testing

Interpreting FTAM Errors

Table 1-1 may help you to ﬁnd what caused your FTAM test to fail.

1. Check the ﬁeld labeled “Diagnostic”. If this ﬁeld is present, look for a text string labeled “further details”

for the cause.

2. Look at the line after “FAILED”. The operation that failed is listed.

Table 1-1 FTAM Call Errors

FTAM Call Reason Corrective Action

ft_aeactivation() FTAM not correctly

installed.

OTS stack not up. Run the Status operation

ft_connect() Incorrect address

speciﬁed.

Incorrect User ID. Check user name and

Remote stack not up. Recheck stack. Responder not running. Repeat the veriﬁcation

Lower Layer Problem. Go back to the step you were

ft_select() Incorrect source ﬁle

name.

Run swverify on the FTAM ﬁleset to verify that all components are installed.

under Session or Transport to verify.

Recheck the value of the Presentation address speciﬁed and the value conﬁgured for the remote.

password, usually corresponds to the remote.

described in the pre-test section.

on and continue. Check the source ﬁle name

and correct.

16 Chapter 1

Interoperability Testing

Interpreting FTAM Errors

FTAM Call Reason Corrective Action

ft_create() Permission problem or

incorrect directories were speciﬁed in the path for the destination ﬁle name.

ft_sdata() Transfer ﬁle too large.

(Error code 101 Buffer too large error).

ft_xxx() Uncommon points of

error; or, if an abort indication is received, the remote went down for some reason.

Check the permissions and the directories speciﬁed.

Rerun the test with a smaller ﬁle or use the High Level Transfer test.

Check the remote stack and FTAM responder if an abort indication is indicated.

Chapter 1 17

Interoperability Testing

Testing APRI Interoperability

The steps below describe how to test the ACSE/Presentation and ROSE (APRI) layer connectivity between the local and remote node. Use this only if you are developing APRI programs and wish to verify connectivity at this layer.

1. Log on as root.

2. Perform the pre-test checklist.

3. Perform APRI test - Client Mode.

4. Perform APRI test - Server Mode (optional).

5. If osidiag cannot ﬁnd a default local application title, perform “Specifying Application Titles.”

6. Interpret errors.

18 Chapter 1

APRI Pretest Checklist

Check the following before attempting the APRI Interoperability tests.

Figure 1-2 APRI Pre-Test Checklist

Interoperability Testing

APRI Pretest Checklist

Is the local OTS stack up?

Yes

Is the stack up on

the remote system?

Yes

Do you have the Remote Presentation Address?

Yes

Do you have the proposed

context list for the remote?

Yes

Do you have the application context expected by remote?

Yes

Type otsstart to bring up the system.

Start the remote stack.

Get it from the Remote System Worksheet.

Determine context.

Default object IDs: ACSE {2 2 1 0 1} Arbitrary {2 1 9999 1}

Determine context.

Default object ID: {2 1 9999 1}

Do you have the local NSAP?

Start APRI Tests.

Chapter 1 19

By default, osidiag binds to CNLS over LAN,

if one is configured.

Interoperability Testing

Running APRI Tests (Client Mode)

The following steps verify APRI connectivity and interoperability with a remote node.

If the remote is not capable of receiving connections, or you want to test the remote’s ability to establish connections, follow the instructions in “Running APRI Tests (Server Mode)” on page 21.

1. From root, type /opt/ots/bin/osidiag and select “ACSE/Presentation or ROSE Tests.”

2. Create a result ﬁle.

3. Make sure a server application is running on the remote. Then, select “Connect” from the Test Case menu.

4. Enter Presentation Address when prompted.

NOTE osidiag will display the local address by default. The default P, S, and T

selectors are given in ASCII surrounded by double quotes. If the address you must use is speciﬁed in hexadecimal rather than ASCII, then omit the double quotes (for example, 22003176).

5. Enter Proposed Contexts when prompted.

6. Enter Application Context when prompted.

7. For ROSE only: Enter the context identiﬁers when prompted.

8. Check the “TEST STATUS” near the end of the report. If the status is “PASSED,” you have successfully communicated with

the remote node and are ﬁnished with this section. If the status is “FAILED , ” see “Interpreting APRI Errors” on page 22,

and ﬁnd problem. If you ﬁnd the error, rerun this test. If you cannot ﬁnd the error, enable tracing. See “Tracing and Logging

through /opt/ots/bin/osidiag” on page 62 for more information.

9. Go to the APRI Tests (Server Mode). (Optional)

20 Chapter 1

Interoperability Testing

Running APRI Tests (Server Mode)

If the remote is not capable of receiving connections, or you want to test the remote’s ability to establish connections, follow these instructions.

1. From root, type /opt/ots/bin/osidiag -w 300 (the -w 300 allows 300 seconds to get the client ready once the server is started), and select “ACSE/Presentation or ROSE Tests.”

2. Create a result ﬁle.

3. Select “Server...” from the Test Case menu.

4. For ROSE only: Enter the Presentation context identiﬁers to be used as ROSE contexts.

5. For ROSE only: Leave the autorespond to ROSE default set to “Y”.

6. Generate the connection from the client side via the remote application. Follow steps in the APRI Tests (Client Mode) if an HP system.

7. Check the “TEST STATUS” near the end of the report. If the status is “PASSED,” you have successfully communicated with

the remote node and are ﬁnished with this section. If the status is “FAILED , ” see “Interpreting APRI Errors” on page 22,

and ﬁnd the problem. If you ﬁnd the error, rerun the server test and rerun the client test on

the remote to connect to this server. If you cannot ﬁnd the error, enable tracing on the local node. See

“Tracing and Logging through /opt/ots/bin/osidiag” on page 62 for more information.

Chapter 1 21

Interoperability Testing

Interpreting APRI Errors

Table 1-2 describes possible errors and corrective actions if an error occurs during a call to APRI.

Table 1-2 APRI Call Errors

APRI Call Reason Corrective Action

ap_open() Incorrect installation or OTS

stack is not up.

ap_set_env() Incorrect address speciﬁed.

(parameter ap_my_psap)

ap_poll() Time out (osidiag defaults to

30 seconds for indication or conﬁrmation).

Unanticipated primitive (osidiag received an indication it did not expect.)

ap_rcv(A_PABORT_IND) Incorrect remote address. Recheck remote

ap_rcv(A_ABORT_IND) The application on top of the

Presentation layer detected some problem. An abort may also be sent by the HP provider if the speciﬁed address is valid, but no process is currently accepting connections.

Run otsstat to see if OTS stack is up. Run otsstart to start OTS stack.

Recheck the value of ap_my_psap.

Increase time if needed.

Check osidiag display immediately after the call to ap_poll().

address; check that local NSAP is on same subnet as the destination system.

Examine the output of the remote application for further information as to why the abort was sent.

22 Chapter 1

Interoperability Testing

Interpreting APRI Errors

APRI Call Reason Corrective Action

ap_rcv(A_ASSOC_CNF) Your connect request arrived

at the remote, but the remote did not like one of your proposed values or it is not available to service connections. The conﬁrmation carries three pieces of information: the result, the source (if rejected), and a diagnostic code.

ro_bind() The values you speciﬁed are

not compatible with those negotiated.

Examine the diagnostic code for the course of action.

Verify that the values for ap_p_ctx_list and rose_pci_list are consistent.

Chapter 1 23

Interoperability Testing

Testing Session Interoperability

The steps below describe how to test the session layer connectivity between the local and remote node. Use this only if you are developing session programs and wish to verify connectivity at this layer.

1. Log on as root.

2. Perform the pre-test checklist.

3. Perform Session tests - Client Mode.

4. Perform Session tests - Server Mode (optional).

5. If osidiag cannot ﬁnd a default local application title, perform “Specifying Application Titles.”

6. Interpret errors.

24 Chapter 1

Session Pre-Test Checklist

Figure 1-3 Session Pre-Test Checklist

Interoperability Testing

Session Pre-Test Checklist

Is OTS stack up?

Yes

Is the remote stack up?

Yes

Do you have the session address?

Yes

Does remote have the

remote ready to accept a connection?

Yes

Do the session IOP tests.

Perform Session Tests - Client Mode.

Start OTS using osistart.

Start the remote stack.

Get the address made up of S-Sel, T-Sel, and Network Address.

Start FTAM on the remote.

Is the remote HP? Run osidiag as server on the remote.

Is the remote non-HP? Run demo or other Session application.

Does Remote only initiate activity? Prepare local node as a server

("Perform Session Tests - Server Mode"), then run remote Client application.

Chapter 1 25

Interoperability Testing

Running Session Tests (Client Mode)

Normally you use this list of steps to verify connectivity and interoperability with a remote node. If the remote is not capable of receiving connections, or you wish to test the remote’s ability to establish connections, follow the instructions in “Running APRI Tests (Server Mode)” on page 21.

1. From root, type /opt/ots/bin/osidiag and select “Session Tests.”

2. Create a result ﬁle.

3. Make sure a server application is running on the remote, then: Select “Connect” from the Test Case menu.

4. Enter the destination Session Address when prompted. NOTE: osidiag will display the local address by default.

5. Check the “TEST STATUS” near the end of the report. If the status is “PASSED,” you have successfully communicated with

the remote node and are ﬁnished with this section. If the status is “FAILED,” see “Interpreting Session Errors” on page

28 to ﬁnd the problem. If you ﬁnd the error, rerun this test. If you cannot ﬁnd the error, enable tracing. See “Tracing and Logging

through /opt/ots/bin/osidiag” on page 62.

6. Go to “Running APRI Tests (Server Mode)” on page 21 (Optional).

26 Chapter 1

Interoperability Testing

Running Session Tests (Server Mode)

If the remote is not capable of receiving connections, or you wish to test the remote’s ability to establish connections, follow these instructions.

1. From root, type /opt/ots/bin/osidiag -w 300 (the -w 300 allows 300 seconds to get the client ready once the server is started), and select “Session Tests”.

2. Create a result ﬁle.

3. Select “Server...” from the Test Case menu.

4. Generate the connection from the client side via the remote application. Follow steps in “Running APRI Tests (Client Mode)” on page 20, if an HP system.

5. Check the “TEST STATUS” near the end of the report. If the status is “PASSED,” you have successfully communicated with the remote node and are ﬁnished with this section.

If the staus is “FAILED,” see “Interpreting Session Errors” on page

28. If you ﬁnd the error, rerun the server test, then rerun the client test

on remote to connect to this server. If you cannot ﬁnd the error, enable tracing on the local node. See

“Tracing and Logging through /opt/ots/bin/osidiag” on page 62.

Chapter 1 27

Interoperability Testing

Interpreting Session Errors

Table 1-3 describes possible errors and corrective actions. The list is sorted by the name of the function producing the error. The names are displayed by osidiag on the line immediately after the test status.

Table 1-3 Session Call Errors

Session Call Reason Corrective Action

osi_init() Usually lack of available

swap space.

osi_rgr_rq() osi_rgr_cf()

osi_get_event() Two common errors:

ses_pabort_id() Used to decode an incoming

Possibly stack is not up. Another application is already listening on this address or has requested exclusive access to this address.

1. Time out - osidiag only waits 30 seconds by default. May indicate that the remote is not sending any response to your request.

2. Unanticipated primitive osidiag received an indication that it did not expect.

provider abort indication. For more information see “Protocol Reason Codes” on page 44. The reason code appears in the middle of the osidiag output.

Add swap space as necessary.

Check to see if stack is up. See if another applications is using this address or has exclusive access.

Verify that the remote is indeed performing its end of the dialog. If the timeout is too short, it may be changed under the utilities menu. The name of the indication will be displayed immediately after the call to osi_get_event().

Check the reason code and correct accordingly.

28 Chapter 1

Interoperability Testing

Interpreting Session Errors

Session Call Reason Corrective Action

ses_uabort_id() Used to decode incoming

abort indication. Indicates the application on top of the Session layer detected some problem.

ses_connect_rf() Called to decode a refusal to

connection request. Indicates that your connect request arrived at the remote, but remote did not like one of your proposed values or it is not available to service connections. The refuse code is displayed in the middle of the osidiag output.

Examine the output of the remote application for further information as to why the abort was sent.

Check the remote to see if it is available to service connections. Also check your proposed values. For more information on disconnect codes and suggested actions, See “Interpreting Transport Errors” on page 33.

Chapter 1 29

+ 65 hidden pages