HP UX 11i v2 Networking Software manual Tracing and Logging through, Opt/ots/bin/osidiag

Page 62

Problem Solving

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

Tracing and Logging through

/opt/ots/bin/osidiag

osidiag (located in the /opt/ots/bin directory) provides the ability to automatically capture nettl trace and log information and append it to the output for a test operation. osidiag also allows you to copy the results displayed to the screen to a result file. The following steps describe how to enable both facilities through osidiag.

1.Invoke osidiag either directly or through osiadmin and go to the Utilities menu.

2.Select “Open Result File” and enter a file to save the results of the test operation (for example, /tmp/ftam.res). The file specified will be overwritten if it already exists.

3.Select “Tracing and Logging.”

4.Enable logging for OTS, by placing a “Y” after its name in the pop-up window. Enable tracing for the layer being tested and the layer below. So, for FTAM you would enable FTAM and ACSE/Presentation. For Transport, you would enable Transport and Network. Use the “Help” facility for more information about a particular flag. Press Done on the Trace and Log screen after setting the appropriate fields to “Y.”

5.Use the default values presented for the log and trace levels by pressing Done on these screens, and then exit the Utilities menu.

6.Now rerun the test you are gathering information for. The results of the logging and tracing will be displayed on your screen as well as copied to the file you specified in step 2.

To analyze the errors logged, see “Common Logged Errors” on page 67.

The trace information produced may be useful to your HP support representative. Interpreting traces requires a good understanding of the various OSI protocol internals. Some information on trace interpretation is given at the end of the “Session,” “OTS,” “X.25,” and “LAN” sections of Chapter 1 “Interoperability Testing”.

62

Chapter 2

Image 62
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 TestingCheck the following before attempting to run the Ftam tests Ftam Pre-Test ChecklistFtam Pre-Test Checklist 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 Errors Reason Action Interpreting X.25 ErrorsProblem corrected 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 Code Meaning Session Refuse CodesSession Refuse Codes To Create a Result File Problem Solving Basic Steps Where Action Interpreting ErrorsInterpreting Errors Checking System Status Status CheckStatus Check Running Verification Tests Link VerificationService Verification OTS Transport VerificationRunning Verification Tests Type Troubleshooting Method Error Collecting Troubleshooting DataTroubleshooting Methods Tracing and Logging through Opt/ots/bin/osidiagLogging and Tracing Entities Service/Layer Entities to LogTracing and Logging User Applications Fddi Otssubnets Common Mistakes Common Configuration MistakesOtsdests Common Mistakes Remoteapp Common Mistakes Otsparms Common MistakesLocalapp 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 Component Test OSI DiagnosticsTests Provided by osidiag Fddi Osistart Command Starting and Stopping OSIOsistat Command Stopping OSIExample Starting OTS otsstartSyntax 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