HP-UX Reference (11i v2 04/09) - 1M System Administration Commands N-Z (vol 4)

n
nettl(1M) nettl(1M)
-timer (Abbr.: -t)
Used with first -traceon option or alone after tracing has been turned on.
Used to set the buffer flush timer. This value can be set in seconds. Default value is 5
seconds. timer_value can be in the range of 1 to 10 seconds.
Set the maximum time (in seconds) by which buffers are flushed to the disk. The trace
buffers are written to the disk when the timer value expires or once the buffers are filled,
whichever occurs earlier. A larger value is better when the rate of data traced per second
is high (of the order of 100 MBytes per second); while a lower value would be preferred
for tracing at lower speeds, and when delays in seeing the data in the trace cannot be
tolerated.
-bind (Abbr.: -b)
Used with first -traceon option or alone after tracing has been turned on.
Used to bind the daemon process which writes the trace messages to the file, to the pro-
cessor given by cpu_id . This helps in improving performance of tracing. It is recom-
mended that the processor chosen satisfies one or more of the following conditions:
• receives interrupts from the disk to which trace buffers are being written
• does not receive non-disk interrupts
• is least loaded (can be found using the
top command).
Note : The bind request is processed only when the disk-write daemon process is idle.
This means that
-bind operation might return successfully while process is not yet
bound to the processor. Hence, check the Processor ID field in nettl -status
TRACE output to know if the binding request has been serviced. Hence, it is advisable to
use this option with the first -traceon operation or while tracing activity is minimal.
-card dev_name ...
(Abbr.: -c)
This option is required by the X.25 subsystems; it is optional for other subsystems. Some
subsystems do not support this option.
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 applicable and 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 subsystem s 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
HP-UX 11i Version 2: September 2004 − 2 − Hewlett-Packard Company Section 1M−−523