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

n
nettl(1M) nettl(1M)
Examples of LAN subsystems:
ns_ls_driver ns_ls_loopback ns_ls_x25
ns_ls_icmp ns_ls_tcp ns_ls_igmp
ns_ls_nfs ns_ls_udp ns_ls_ip
ns_ls_ipv6 ns_ls_icmpv6
Two X.25-specific subsystems are used for tracing only:
SX25L2 SX25L3
-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 .TRC000 which receives the binary tracing data. If a trace file of the name
tracename .TRC000 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.
HP-UX servers (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
messages as well as the default messages. A level of 2 specifies information messages in
addition to the cautionary and default messages. This option is recognized only by the
ns_ls_x25 subsystem.
-log class ... (Abbr.: -l)
Requires the -entity option.
Control the class of log messages that are enabled for the subsystems specified by the
-entity option.
class specifies the logging class. Available classes are:
Full Abbr. Mask
informative i 1
warning w 2
error e 4
disaster d 8
informative Describes routine operations and current system values.
warning Indicates abnormal events possibly caused by subsystem prob-
lems.
error Signals an event or condition which was not affecting the
overall subsystem or network operation, but may have caused
an application program to fail.
disaster Signals an event or condition which did affect the overall sub-
system or network operation, caused several programs to fail
or the entire node to shut down.
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
Section 1M524 Hewlett-Packard Company 3 HP-UX 11i Version 2: September 2004