Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP 9000 Networking: Installing and Administering OSI Transport Services > Chapter 1 HP OTS /9000 Resources

Logging Messages

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

HP OTS/9000 uses the nettl(1M) logging and tracing facility supplied with HP-UX. See the nettl(1M) manual (man) page for information on using the command line interface.

NOTE: All log message cause and action statements are now online and can be viewed with any ASCII text editor. The OTS cause and action statement file is / opt/ots/doc/ ots_messages.txt.

Listed below are some example commands.

  • To examine the log file:

    netfmt -file /var/adm/nettl.LOG00 -t 50

    Note the message number, then search the messages.txt message file for a description of the problem and possible solutions. A sample OTS log message is shown below.

    **************************HP OSI MGMT**********************
    Timestamp        :Mon Dec 16PST 1996  03:40:10.555252
    Process ID       :750                 Subsystem   :TRANSPORT
    User ID (UID)    :0                   Log Class   :DISASTER
    Device ID        :1                   Path ID     :0
    Connection ID    :0                   Log Instance:0
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <1317> OTS driver encountered a lobe error on interface unit 
    <1>. The error code is <-1>; reset or reboot.
  • To check network logging and tracing status:

    nettl -status

  • To start all OTS transport and session tracing to the file /var/adm/tracefile:

    nettl -traceon all hdrin hdrout pduin pduout -entity transport session -file /var/adm/tracefile

  • To stop OTS tracing:

    nettl -traceoff -entity transport session

  • To format the OTS trace file into the file /var/adm/traceout:

    netfmt -file /usr/adm/tracefile.TRC0 > /var/adm/ traceout

Link Subsystems

Use the following link subsystem names when logging and tracing OTS/9000:

  • NS_LS_DRIVER - This is the IEEE 802.3 LAN link.

  • FDDI - This is the FDDI LAN link.

  • SX25L2 - This is the level 2 high performance X.25 link tracing subsystem.

  • SX25L3 - This is the level 3 high performance X.25 link tracing subsystem.

OTS Subsystems

Use the following subsystem names when logging and tracing OTS/9000:

  • Network - This is the Network layer entity of the OTS stack. This subsystem includes both the Connection-Oriented (CONS) and Connectionless (CLNS) Network Service entities.

  • Transport - This is the Transport layer entity. Some CLNS logged errors may also appear under this entity.

  • Session - This is the Session layer entity.

  • ACSE_PRES - This is the ACSE/Presentation entity.

  • OTS - This corresponds to non-layer specific tasks performed while managing the various stack entities, for example, communication between the OTS stack and user space, communication between the OTS stack and network devices, and other administrative tasks, such as buffer management.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© © 1989, 1991, 1992, 1995, 1996 Hewlett-Packard Development Company, L.P.