nettl.1m (2010 09)

n
nettl(1M) nettl(1M)
Classes can be specified as keywords or as a single numeric mask depicting which classes
to log. The mask is formed by adding the individual masks of the log classes. If you
choose to indicate several classes at once, be sure to separate each log class with a space.
disaster logging is always on. The default logging classes for each subsystem is
configured into the configuration file,
/etc/nettlgen.conf
. When the
tracing/logging facility is started, the information in the configuration file is read and
subsystems are enabled for logging with the specified classes. To change the log class,
use the "
nettl -log class
-entity subsystem" command with a new log class
value. If desired, the command can be run for different log classes and different entities.
-m bytes Specify the number of bytes (bytes ) of each trace record to trace. This option allows you
to specify the number of bytes to be captured in the trace packet. You may prefer not to
capture an entire PDU trace, such as when you are only interested in the header.
The maximum value for bytes is 2000. By default, the entire packet is traced. A value of
0 will also cause the entire packet to be traced. This option currently applies only to ker-
nel subsystems.
-mem init_mem [max_mem]
Used with the first -traceon option only.
Set the amount of memory (in kilobytes) used to hold the trace messages until they are
written to the file. init_mem is the memory allocated with the first
-traceon
operation.
If not specified, the default value of init_mem is 7% of the free memory available (can be
found using
vmstat command) when tracing is first enabled. The minimum value that
can be specified for init_mem is 8 KB and the maximum value is 50% of the free memory
available.
If the memory allocated when tracing is first enabled proves to be insufficient, that is,
when trace buffers cannot accommodate more messages, additional memory may be allo-
cated up to a maximum limit given by max_mem. If not specified, the default value of
max_mem is init_mem itself. Hence, if the volume of trace messages is high, max_mem
must be set in order to avoid loss of trace messages. The maximum value that can be
specified for max_mem is 70% of free memory available. The minimum value for
max_mem should be greater than or equal to the init_mem value. Please note that speci-
fying a max_mem value for
-mem option is optional.
Setting these values too low increases the possibility of dropped messages. See the Trace
Memory Management section below to determine the size of the trace buffer and for more
details.
Note : The default unit for init_mem and max_mem is Kilobytes. Use
m or M suffix to
specify the values in Megabytes. Refer to examples 9 and 10 for the usage.
-size portsize
(Abbr.: -s)
Note : This option is being maintained for backward compatibility and is currently
ignored. This option will be obsoleted in the next major release. Use
-mem option to
configure memory used for trace buffers.
Used with first
-traceon option only.
Set the size in kilobytes (KB) of the trace buffer used to hold trace messages until they
are written to the file. The default size for this buffer is 68 KB. The possible range for
portsize is 1 to 1024. Setting this value too low increases the possibility of dropped trace
messages from fast subsystems.
-status log
-status trace
-status [all]
(Abbr.: -ss)
Used alone without other options.
Report the tracing and logging facility status. The facility must be operational, that is,
nettl -start has been completed. The additional options define the type of trace or
log information that is to be displayed. The default value is all.
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010