HP UX 11i v2 Networking Software manual Running Verification Tests, Link Verification

Page 58

NOTE

Problem Solving

Running Verification Tests

Running Verification Tests

The verification strategy described here follows a bottom up approach. It first checks the ability of the links to communicate, then the OTS Transport Layer, and last the desired service.

All the verification tests use osidiag. Testing the X.400 services may alternatively be performed through x4admin or the X.400 tools described in Managing X.400—Administrator’s Guide.

osidiag may be invoked directly from the command line, or through osiadmin by selecting “Test Connectivity->” for the appropriate layer.

Hewlett-Packard strongly recommends that you run these verification tests even if the problem you are troubleshooting is seen through a user-written application. If the verification tests fail, then there is a general network problem that you should correct. If these tests pass, then the problem is related to your program's behavior. For a description on how to further analyze program-specific problems, see “Collecting Troubleshooting Data” on page 61.

Link Verification

For X.25

1.For X.25, run the “Loopback...” test under osidiag’s “X.25 Test Cases.”

2.If you have multiple X.25 cards, run this test under osiadmin, so that osidiag will use the correct default values.

3.If OTS is not configured to use subaddressing, you will not be able to run this test when OTS is running. The error you see is “Address already in use.” Try running the “Connect...” test instead, making sure the Protocol ID field is blank and not “dx25.”

4.If you encounter errors, see “Interpreting X.25 Errors” on page 42.

For LAN

1.For LAN, run the “Test Frames...” test under osidiag’s “LAN Test Cases.”

58

Chapter 2

Image 58
Contents HP 9000 Networking 32070-90031 E0597Legal Notices Copyright NoticesTrademark Notices Page Contents Problem Solving Using OSI and OTS Tools Syntax Example Recovering from otsstart FailureUpdating OTS otsupdate Printing History Page Interoperability Testing Testing Ftam Interoperability Ftam Interoperability TestingFtam Pre-Test Checklist Ftam Pre-Test ChecklistCheck the following before attempting to run the Ftam tests Ftam Interoperability Testing Ftam Connectivity TestFtam File Transfer Test Interpreting Ftam Errors Ftam Call Errors Reason Corrective ActionFtam Call Reason Corrective Action Testing Apri Interoperability Apri Pretest Checklist Apri Pre-Test ChecklistRunning Apri Tests Client Mode Running Apri Tests Server Mode Interpreting Apri Errors Apri Call Errors Reason Corrective ActionApri Call Reason Corrective Action Testing Session Interoperability Session Pre-Test Checklist Session Pre-Test ChecklistRunning Session Tests Client Mode Running Session Tests Server Mode Interpreting Session Errors Session Call Errors Reason Corrective ActionSession Call Reason Corrective Action Testing Transport Interoperability Transport Pre-Test Checklist Transport Pre-Test ChecklistRunning Transport Tests Problem persists Interpreting Transport ErrorsTransport problem corrected Transport Call Errors Reason ActionTesting LAN 802.3 or Fddi Interoperability LAN Pre-Test Checklist LAN Pre-Test ChecklistRunning LAN Tests LAN Errors Reason Action Interpreting LAN ErrorsLAN problem corrected Configuration change requiredError Reason Action Testing X.25 Interoperability Pre-Test Checklist Pre-Test ChecklistRunning X.25 Tests Problem corrected Interpreting X.25 ErrorsErrors Reason Action Recv*00B Reason and Refuse Codes Protocol Reason CodesCode Meaning Action 0x08 Reject Nsap unreachable/ Permanent Reason and Refuse Codes Local node may not be compatible with that Osiadmin F0-FF Session Refuse Codes Session Refuse CodesCode Meaning To Create a Result File Problem Solving Basic Steps Interpreting Errors Interpreting ErrorsWhere Action Checking System Status Status CheckStatus Check Running Verification Tests Link VerificationService Verification OTS Transport VerificationRunning Verification Tests Troubleshooting Methods Collecting Troubleshooting DataType Troubleshooting Method Error Tracing and Logging through Opt/ots/bin/osidiagTracing and Logging User Applications Service/Layer Entities to LogLogging and Tracing Entities Fddi Otsdests Common Mistakes Common Configuration MistakesOtssubnets Common Mistakes Localapp Common Mistakes Otsparms Common MistakesRemoteapp Common Mistakes Subsystem OTS Common Logged ErrorsError Description Subsystem AcsepresSubsystem Transport Subsystem Network Submitting Problem Information to HP Using OSI and OTS Tools Osiadmin RFC1006 Configure Using osiconf Managing Your ConfigurationTroubleshooting Using osiconfchk Tests Provided by osidiag OSI DiagnosticsComponent Test Fddi Osistart Command Starting and Stopping OSIOsistat Command Stopping OSISyntax Starting OTS otsstartExample Recovering from otsstart Failure Checking OTS Status otsstat OTS Updating OTS otsupdate Dynamic Routing Commands End System CommandsIntermediate System Commands OtsaddisArgument ES/IS Command ParametersES/IS Parameters ParameterES/IS Command Options Option DescriptionRoute Commands Dynamic Routing CommandsRoute Command Parameters Dynamic Route CommandsRoute Command Options Route Command OptionsNsap Commands Argument DescriptionOtsshownsaps Index ApriIndex
Related manuals
Manual 175 pages 52.54 Kb Manual 74 pages 39 Kb Manual 236 pages 18.16 Kb Manual 12 pages 39.66 Kb Manual 28 pages 49.76 Kb