HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
n
nettl(1M) nettl(1M)
Limit the trace information gathered to only the data that comes from the specified net-
work interface card. More than one dev_name can be specified at a time in order to trace
multiple network interfaces.
dev_name specifies a device which corresponds to a network interface card that has been
installed and configured. It can be either an integer representing the network interface, or
the device file name of the network interface. Some subsystems do not support both types
of dev_name. For example, the X25 subsystems require that dev_name be a device file
name. The product documentation for the subsystems should explain if the -card option
is applicableand how to choose an appropriate dev_name.
If dev_name is not an integer it is assumed to be a device file name. The path prefix
/dev/ will be attached in front of dev_name if it is not an absolute path name to form the
device file name, /dev/dev_name. dev_name must refer to a valid network device file.
-entity all
-entity
subsystem ...
(Abbr.: -e)
Limit the action of -log, -traceoff
,or-traceon to the specified protocol layers or
software modules specified by subsystem.
The number and names of subsystems on each system are dependent on the products that
have been installed. Use the command
nettlconf -status to obtain a full listing of
supported subsystems and the products that own them.
Examples of OSI subsystems:
acse_pres ftam_init mms
asn1 ftam_resp network
cm ftam_vfs ots
em ftp_ftam_gw transport
ftam_ftp_gw hps ula_utils
Examples of LAN subsystems:
ns_ls_driver ns_ls_loopback ns_ls_ni
ns_ls_icmp ns_ls_netisr ns_ls_tcp
ns_ls_igmp ns_ls_nfs ns_ls_udp
ns_ls_ip ns_ls_nft ns_ls_x25
Two X.25-specific subsystems are used for tracing only:
X25L2 X25L3
-file
tracename
(Abbr.: -f)
Used with the first -traceon option only.
The first time the -traceon keyword is used, it initializes tracing, creating a file
tracename.TRC0 which receives the binary tracing data. If a trace file of the name
tracename.TRC0 already exists the binary trace data is appended to the end of the file.
To start a fresh trace file, first turn off tracing then turn it back on again using a different
tracename. See "Data File Management" below for more information on file naming.
If -file is omitted, binary trace output goes to standard output. If standard output is a
terminal device, an error message is issued and no tracing is generated.
-firmlog 012
(Abbr.: -fm)
Requires the -card option.
Series 800 and X.25 only.
Set the X.25/800 interface card logging mask to level 0, 1, or 2. The default level is 0. The
X.25/800 interface logs a standard set of messages. A level of 1 specifies cautionary mes-
sages as well as the default messages. A level of 2 specifies information messages in addi-
tion to the cautionary and default messages. This option is recognized only by the
ns_ls_x25 subsystem.
HP-UX Release 11i: December 2000 − 2 − Section 1M−−549
___
___