PCI FDDI Administrator's Guide

Troubleshooting PCI FDDI
Diagnostics
Chapter 384
lo0 4608 loopback localhost 890 890
lan2 4352 192.103.48 h4-6w 350002 701564
lan4* 4352 none none 0 0
lan3 4352 192.20.40 192.20.40.50 14 14
lan0 1500 15.13.112 hpntch4 644287 1787
ping
Use ping to test connectivity to stations on your local ring.
hpntc7q:root> ping 192.20.100.112
PING 192.20.100.112: 64 byte packets
64 bytes from 192.20.100.112: icmp_seq=0. time=0 ms
64 bytes from 192.20.100.112: icmp_seq=1. time=0 ms
64 bytes from 192.20.100.112: icmp_seq=2. time=0 ms
64 bytes from 192.20.100.112: icmp_seq=3. time=0 ms
nettl, netfmt, nettladm
• The nettl command is used to start and stop tracing. The netfmt
command is used to format a trace file. The
/opt/nettladm/bin/nettladm utility provides a GUI interface to
nettl and netfmt.
• Log messages for 11.0 are sent by default to the file
/var/adm/nettl.LOG## and for 11i to the file
/var/adm/nettl.LOG### (LOG000 or LOG001). For tracing, use the
-f option to indicate where you want the trace to go. All disaster
messages are sent to the console.
• The PCI FDDI adapter card uses the nettl entity PCI FDDI
• From the command line, you can enable tracing for all inbound,
outbound and driver loopback PCI FDDI packets with the following
command:
nettl -traceon pduin pduout loopback -e PCI_FDDI -f
my_file
• To disable tracing:
nettl -traceoff -e all