Logging and Tracing Messages

HP FDDI/9000 comes with an online message catalog that reports HP FDDI problems, probable causes, and actions for you to take to correct the problems. Messages are sent either to the system console or log files, and come in the following format:

`1041 MESSAGE`	`HP-PB FDDI LAN driver received an error from the adapter in path %s indicating length mismatch on transmission of a data packet.`
`CAUSE`	`(Disaster) This is probably due to a hardware problem on the adapter.`
`ACTION`	`Execute the lanscan command to identify the device logical unit of the LAN adapter. Re-initialize the adapter using fddiinit. If initializing the adapter does not solve the problem, reboot. If rebooting is ineffective, notify your HP representative.`

HP FDDI/9000 uses the nettl logging and tracing facility supplied with HP- UX to capture, control, and format messages produced by HP FDDI. When using nettl, note the following:

log and trace messages are sent to the files /var/adm/nettl.LOG## or /var/adm/nettl.TRC##
all disaster messages are sent to the system console
tracing and logging have an impact on system performance and should be used judiciously

Listed below are some example commands.

To examine the log file with message, cause, and action:
netfmt -v -file /var/adm/nettl.LOG00 -t 50
To check network logging and tracing status:
nettl -status
To start all tracing to the file /var/adm/tracefile:
nettl -traceon all hdrin hdrout pduin pduout -file /usr/adm/tracefile
To stop tracing:
nettl -traceoff
To format the trace file into the file/usr/adm/traceout:
netfmt -file /var/adm/tracefile.TRC0 > /var/adm/ traceout

Logging and Tracing Messages

Technical documentation

» Table of Contents

» Index