This appendix provides changes to reference pages due to patches included
in this kit.
A.1 envconfig(8) Update
This section updates the
envconfig(8)
envconfig(8)
NAME
envconfig - Configures the Environmental Monitoring daemon
SYNOPSIS
/usr/sbin/envconfig -c var=value
/usr/sbin/envconfig start | stop
/usr/sbin/envconfig -q
OPTIONS
Environmental Monitoring provides a means of detecting system threshold
conditions, that if exceeded, could result in a loss of data or damage to
the system itself. To detect and notify users of critical conditions, the
envmond daemon is used. This utility, envconfig, is used to customize the
envmond daemon. This section describes the envconfig options you can use
to configure the daemon.
-c var=value
Sets the variables that specify how the system environment is
monitored. These variables are stored in the /etc/rc.config file and are
read by the envmond daemon at system startup. If a variable is not
set, the default value of that variable is assumed.
ENVMON_CONFIGURED
Specifies the state of Environmental Monitoring. If this variable
is set to zero (0), the Environmental Monitoring package is not
started during the system boot. If this variable is set to 1, and
Environmental Monitoring is supported by that platform, it is
started during the system boot. The default value is zero (0).
ENVMON_GRACE_PERIOD
Specifies the time (in minutes) that can elapse between the detec-
tion of a high temperature condition and the shutdown of the sys-
tem. The default value is 15 minutes.
ENVMON_HIGH_THRESH
Specifies the threshold level that can be encountered before the
envmond daemon broadcasts a warning and suggested action.
ENVMON_MONITOR_PERIOD
Specifies the frequency (in seconds) between queries of the system
by the envmond daemon. The default value is 60 seconds.
ENVMON_USER_SCRIPT
Specifies the path of a user-defined script that you want the
envmond daemon to execute when a high threshold level is encoun-
tered. The envmond daemon continues to check the environment after
the script has executed and proceeds as needed should the high
threshold levels persist.
If you set this variable, the envmond daemon directs output from
the script to /dev/console. Output is not displayed on standard
output or written to a file as this is not the behavior of the dae-
mon. To display on standard output, explicitly specify the logger
command within the user defined script
ENVMON_SHUTDOWN_SCRIPT
Specifies the path of a user-defined shutdown script that you want
the envmond daemon to execute when a shutdown condition is encoun-
tered. The envmond daemon will execute this script in place of
/sbin/shutdown. If you want the system to be shut down and you
configure a script for ENVMON_SHUTDOWN_SCRIPT you must execute
/sbin/shutdown from within your script. If you do not specify
anything for ENVMON_SHUTDOWN_SCRIPT envmond will, by default,
run /sbin/shutdown when a shutdown condition is encountered.
If you set this variable, the envmond daemon directs output from
the script to /dev/console. Output is not displayed on standard
output or written to a file as this is not the behavior of the dae-
mon. To display on standard output, explicitly specify the logger
command within the user-defined script.
start | stop
Turns the envmond daemon on or off after system startup.
-q Displays the values of ENVMON_CONFIGURED, ENVMON_GRACE_PERIOD,
ENVMON_HIGH_THRESH, ENVMON_MONITOR_PERIOD, ENVMON_USER_SCRIPT,
and ENVMON_SHUTDOWN_SCRIPT as specified in the /etc/rc.config
file. If a specified entry is not found, the environmental
variable is not displayed.
DESCRIPTION
The envconfig utility is used to customize the envmond daemon. You must
have root privileges to use this utility. Using this utility, you can:
+ Specify whether or not Environmental Monitoring is turned on or off at
system startup.
+ Specify how much time can elapse between the envmond daemon encounter-
ing a critical condition and the daemon initiating an orderly shutdown
of the system.
+ Specify how frequently the envmond daemon queries the system for
information.
+ Start and stop the envmond after Environmental Monitoring has been
turned on at system startup.
+ Display the settings of the environment variables as specified in the
/etc/rc.config file.
Note that the feature that you want to monitor must be supported on a given
platform. For example, the AlphaServer 8400/GS140 supports reporting of
power supply and fan status, the current system temperature, and the max-
imum allowed system temperature.
EXAMPLES
The following procedure describes how you test for and start the environ-
mental monitoring subsystem
1. In multiuser mode, check the status of the environmental monitoring
subsystem as follows:
# /sbin/sysconfig -q envmon
envmon:
env_current_temp = 35
env_high_temp_thresh = 40
env_fan_status = 0
env_ps_status = 0
env_supported = 1
2. If the value of env_supported is 0, configure the envmond daemon and
reboot the system using either of the following methods:
+ At the command prompt, enter the following command:
# /usr/sbin/envconfig -c ENVMON_CONFIGURED=1
+ Use the rcmgr command as follows:
# rcmgr set ENVMON_CONFIGURED 1
This command will enable the envmond daemon and export the variable, creat-
ing the following two lines in the /etc/rc.configfile:
ENVMON_CONFIGURED="1"
export ENVMON_CONFIGURED
You can use the /sbin/sysconfig command to view the system environment at
any time. The envmond daemon will the print warning messages in the event
of a power supply failure, abnormality, or high temperatures. Error logs
are logged in the /var/adm/binary.errlog.
In the following example, the system shuts down in 10 minutes if the tem-
perature does not fall below the critical threshold.
/usr/sbin/envconfig -c ENVMON_GRACE_PERIOD=10
FILES
/etc/rc.config*
Databases that contains the values of the environment monitoring vari-
ables. Note that you must use the rcmgr comand to update the rc.config*
files, particularly on clustered systems.
SEE ALSO
Commands: envmond(8)
This section updates the
sys_check(8)
syscheck (8)
NAME
sys_check, runsyscheck - Generates system configuration information and
analysis
SYNOPSIS
/usr/sbin/sys_check [options...]
OPTIONS
-all
Lists all subsystems, including security information and setld inven-
tory verification. This option may take a long time to complete.
-debug
Outputs debugging information to stderr (standard error output).
-escalate [ xx ]
Creates escalation files for reporting problems to your technical sup-
port representative. This option produces one file,
TMPDIR/escalate.tar unless there are crash dump files; if so,
it also creates two other files: TMPDIR/escalate_vmunix.xx.gz
and TMPDIR/escalate_vmcore.xx.gz. If you use the -escalate
option, sys_check runs with the -noquick option and collects the output
in the escalate.tar file. Optionally, you can specify a number (xx)
with the -escalate option to define a crash number.
See also the ENVIRONMENT VARIABLES section for information on how you
can set the value of TMPDIR.
-evm
Generates Event Manager (EVM) warnings. When EVM is configured, warn-
ings are posted as EVM events identified by the string
sys.unix.sys_check.warning. Six levels of priority ranging from 0-500
are used, as follows:
+ 0 - Information only.
+ 100 - Note
+ 200 - Tuning Note
+ 300 - Tuning Suggestion
+ 400 - Operational
+ 500 - Warning
-frame
Produces frame HTML output, which consists of three files:
sys_checkfr.html, sys_checktoc.html, and sys_check.html (unless you
specify a different file name with the -name option). This option
cannot be used with the -nohtml option. The following options are
available for use with the -frame option:
-name name
Specifies the name to use for the frame files output. The default
name is sys_check.
-dir name
Sets the directory for the frames output. Used only with the
-frame option. The default is the current directory (.).
-help or (-h)
Outputs help information.
-nohtml
Produces text output, consisting of one text file, instead of the
default HTML output. This option cannot be used with the -frame option.
-noquick
Outputs configuration data and the setld scan. Excludes security
information.
-perf
Outputs only performance data and excludes configuration data. This
option takes less time to run than others.
-v Displays the sys_check version number.
-warn
Executes only the warning pass. This option takes less time to run than
other options.
-nowarn
Executes only the data gathering pass.
DESCRIPTION
The sys_check utility is a system census and configuration verification
tool that is also used to aid in diagnosing system errors and problems. Use
sys_check to create an HTML report of your system's configuration (software
and hardware). The size of the HTML output that is produced by the
sys_check utility is usually between .5 MB and 3 MB.
The sys_check utility also performs an analysis of operating system parame-
ters and attributes such as those that tune the performance of the system.
The report generated by sys_check provides warnings if it detects problems
with any current settings. Note that while sys_check can generate hundreds
of useful warnings, it is not a complete and definitive check of the health
of your system. The sys_check utility should be used in conjunction with
event management and system monitoring tools to provide a complete overview
and control of system status. Refer to EVM(5) for infor-
mation on event management. Refer to the System Administration guide for
information on monitoring your system.
When used as a component of fault diagnosis, sys_check can reduce system
down time by as much as 50% by providing fast access to critical system
data. It is recommended that you run a full check at least once a week to
maintain the currency of system data. However, note that some options will
take a long time to run and can have an impact on system performance. You
should therefore choose your options carefully and run them during off-peak
hours. At a minimum, perform at least one full run (all data and warnings)
as a post-configuration task in order to identify configuration problems
and establish a configuration baseline. The following table provides guide-
lines for balancing data needs with performance impact.
___________________________________________________________________________
Option Run time Performance Recommended At
impact
___________________________________________________________________________
-warn, -perf Short. Minimal. Regular
updates, at
least weekly
null - no options Medium, perhaps Some likely at Run at least
selected. 15 to 45 minutes peak system use. once post-
depending on pro- installation
cessor. and update
after major
configuration
changes. Update
your initial
baseline and
check warnings
regularly.
-noquick, -all, Long, perhaps 45 Very likely at Use only when
-escalate. minutes on fast, peak use. troubleshooting
large systems to a system prob-
hours on low-end lem or escalat-
systems. ing a problem
to your techni-
cal support
representative.
___________________________________________________________________________
You can run some sys_check options from the SysMan Menu or the
/usr/sbin/sysman -cli command-line interface. Choose one of the following
options from the menu:
>- Support and Services
| Create escalation report [escalation]
| Create configuration report [config_report]
Alternatively, use the config_report and escalation accelerators from the
command line. Note that the escalation option should only be used in con-
junction with a technical support request.
The runsyscheck script will run sys_check as a cron task automatically if
you do not disable the crontab entry in /var/spool/cron/crontabs/root.
Check for the presence of an automatically generated log file before you
create a new log as it may save time.
When you run the sys_check utility without command options, it gathers con-
figuration data excluding the setld scan and the security information and
displays the configuration and performance data by default. It is recom-
mended that you do this at least once soon after initial system configura-
tion to create a baseline of system configuration, and to consider perform-
ing any tuning recommendations.
On the first run, the sys_check utility creates a directory named
/var/recovery/sys_check. On subsequent runs, sys_check creates additional
directories with a sequential numbering scheme:
+ The previous sys_check directory is renamed to
/var/recovery/sys_check.0 while the most recent data (that is, from
the current run) is always maintained in /var/recovery/sys_check.
+ Previous sys_check directories are renamed with an incrementing exten-
sion; /var/recovery/sys_check.0 becomes /var/recovery/sys_check.1, and
so on, up to /var/recovery/sys_check.5.
There is a maximum of seven directories. This feature ensures that you
always have up to seven sets of data automatically. Note that if you only
perform a full run once, you may want to save the contents of that direc-
tory to a different location.
Depending on what options you choose, the /var/recovery/sys_check.*
directories will contain the following data:
+ Catastrophic recovery data, such as an etc files directory, containing
copies of important system files. In this directory, you will find
copies of files such as /etc/group, /etc/passwd, and /etc/fstab.
+ Formatted stanza files and shell scripts and that you can optionally
use to implement any configuration and tuning recommendations gen-
erated by asys_check run. You use the sysconfigdb command or run the
shell scripts to implement the stanza files. See the sysconfigdb(8)
reference page for more information.
NOTES
You must be root to invoke the sys_check utility from the command line;
you must be root or have the appropriate privileges through Division of
Privileges (DoP) to run Create Configuration Report and Create Escalation
Report from the SysMan Menu. The sys_check utility does not change any sys-
tem files.
The sys_check utility is updated regularly. You can obtain the latest ver-
sion of the sys_check utility from either of two sources:
+ The most up-to-date version of the sys_check kit is located on the
sys_check tool web site,
http://www.tru64unix.compaq.com/sys_check/sys_check.html.
+ You can also obtain sys_check from the patch kit, see
http://www.support.compaq.com/patches/.
You should run only one instance of sys_check at a time. The sys_check
utility prevents the running of multiple instances of itself, provided that
the value of the TMPDIR environment variable is /var/tmp, /usr/tmp, /tmp,
or a common user-defined directory. This avoids possible collisions when
an administrator attempts to run sys_check while another administrator is
already running it. However, no guarantees can be made for the case when
two administrators set their TMPDIR environment variables to two different
user-defined directories (this presumes that one administrator does not
choose /var/tmp, /usr/tmp, or /tmp).
The sys_check utility does not perform a total system analysis, but it does
check for the most common system configuration and operational problems on
production systems.
Although the sys_check utility gathers firmware and hardware device revi-
sion information, it does not validate this data. This must be done by
qualified support personnel.
The sys_check utility uses other system tools to gather an analyze data. At
present, sys_check prefers to use DECevent, and you should install and con-
figure DECevent for best results.
If DECevent is not present, the sys_check utility issues a warning message
as a priority 500 EVM event and attempts to use uerf instead. In future
releases, Compaq Analyze will also be supported on certain processors.
Note that there are restrictions on using uerf, DECevent and Compaq Analyze
that apply to:
+ The version of UNIX that you are currently using.
+ The installed version of sys_check.
+ The type of processor.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
LIMITATIONS
DECevent or Compaq Analyze may not be able to read the binary error log
file if old versions of DECevent are being used or if the binary.errlog
file is corrupted. If this problem occurs, install a recent version of
DECevent and, if corrupted, recreate the binary.errlog file.
HSZ controller-specific limitations include the following:
HSZ40 and HSZ50 controllers:
The sys_check utility uses a free LUN on each target in order to com-
municate with HSZ40 and HSZ50 controllers. To avoid data gathering
irregularities, always leave LUN 7 free on each HSZ SCSI target for
HSZ40 and HSZ50 controllers.
HSZ70, HSZ80 and G80 controllers:
The sys_check utility uses a CCL port in order to communicate with
HSZ70 controllers. If a CCL port is not available, sys_check will use
an active LUN. To avoid data gathering irregularities, enable the CCL
port for each HSZ70 controller.
The sys_check utility attempts to check the NetWorker backup schedule
against the /etc/fstab file. For some older versions of NetWorker, the
nsradmin command contains a bug that prevents sys_check from correctly
checking the schedule. In addition, the sys_check utility will not
correctly validate the NetWorker backup schedule for TruCluster Server.
EXAMPLES
1. The following command creates escalation files that are used to report
problems to your technical support organization:
# sys_check -escalate
2. The following command outputs configuration and performance informa-
tion, excluding security information and the setld inventory, and pro-
vides an analysis of common system configuration and operational prob-
lems:
# sys_check > file.html
3. The following command outputs all information, including configura-
tion, performance, and security information and a setld inventory of
the system:
# sys_check -all > file.html
4. The following command outputs only performance information:
# sys_check -perf > file.html
5. The following command provides HTML output with frames, including con-
figuration and performance information and the setld inventory of the
system:
# sys_check -frame -noquick
6. The following command starts the SysMan Menu config_report task from
the command line:
# /usr/sbin/sysman config_report
Entering this command invokes the SysMan Menu, which prompts you to
supply the following optional information:
+ Save to (HTML) - A location to which the HTML report should be
saved, which is /var/adm/hostname_date.html by default.
+ Export to Web (Default) - Export the HTML report to Insight
Manager. Refer to the System Administration manual for information on
Insight Manager.
+ Advanced options - This option displays another screen in which
you can choose a limited number of run time options. The options
are equivalent to certain command-line options listed in the
OPTIONS section.
In this screen, you can also specify an alternate temporary
directory other than the default of /var/tmp.
+ Log file - The location of the log file, which is
/var/adm/hostname_date.log by default.
7. The following is an example of a stanza file advfs.stanza in
/var/recovery/sys_check.*:
advfs:
AdvfsCacheMaxPercent=8
8. The following is an example of a shell script apply.kshin
/var/recovery/sys_check.*:
cd /var/cluster/members/member/recovery/sys_check/
llist="advfs.stanza
vfs.stanza "
for stf in $llist; do
print " $stf "
stanza=`print $stf | awk -F . '{print $1 }'`
print "/sbin/sysconfigdb -m -f $stf $stanza"
/sbin/sysconfigdb -m -f $stf $stanza
done
print "The system may need to be rebooted for these
changes to take effect"
ENVIRONMENT VARIABLES
The following environment variables affect the execution of the sys_check
utility. Normally, you only change these variables under the direction of
your technical support representative, as part of a fault diagnosis pro-
cedure.
TMPDIR
Specifies a default parent directory for the sys_check working sub-
directory, whose name is randomly created; this working subdirectory is
removed when sys_check exits. The default value for TMPDIR is /var/tmp.
LOGLINES
Specifies the number of lines of log file text that sys_check includes
in the HTML output. The default is 500 lines.
BIGNUMFILE
Specifies the number of files in a directory, above which a directory
is considered excessively large. The default is 15 files.
BIGFILE
Specifies the file size, above which a file is considered excessively
large. The default is 3072 KB.
VARSIZE
Specifies the minimum amount of free space that sys_check requires in
the TMPDIR directory. The default is 15 MB and should not be reduced.
The sys_check utility will not run if there is insufficient disk space.
RECOVERY_DIR
Specifies the location for the sys_check recovery data. The default is
/var/recovery. The sys_check utility automatically cleans up data from
previous command runs. The typical size of the output generated by
each sys_check utility run is 400 KB. This data may be useful in
recovering from a catastrophic system failure.
ADHOC_DIR
Specifies the location at which sys_check expects to find the text
files to include in the HTML output. The default is the /var/adhoc
directory.
TOOLS_DIR
Specifies the location at which sys_check expects to find the binaries
for the tools that it calls. The default is /usr/lbin.
FILES
/usr/sbin/sys_check
Specifies the command path.
Note
This file may be a symbolic link.
/usr/lbin/*
Various utilities in this directory are used by sys_check.
Note
These files may be symbolic links.
The sys_check utility reads many system files.
SEE ALSO
Commands: dop(8), sysconfigdb(8), sysman_cli(8), sysman_menu(8)
Miscellaneous: EVM(5), insight_manager(5)
Books: System Administration, System Tuning
A.3 sys_attrs_netrain(5), nifftmt(7), and niffconfig(8) Updates
The installation of Patch 1830.00 results in changes to the
sys_attrs_netrain(5)nifftmt(7)niffconfig(8)ifconfig(8)ifconfig(8)A.3.1 sys_attrs_netrain(5)
nr_timeout_dead_interface
The time interval or frequency between successive polls of a dead
interface by the NetRAIN interface recovery thread.
Minimum value: 0.5 (seconds)
nr_timeout_o
Minimum value: 1.1
nr_timeout_t
Minimum value: 0.5
You can specify decimal values (for example, 2.5 or 0.8) for
nr_timeout_dead_interface, nr_timeout_o, and nr_timeout_t. When you recon-
figure any of these values by using the sysconfig -r command, they are all
validated together. If any value fails validation, all previous (valid)
values are restored and EINVAL is returned. Each value must be greater than
or equal to its minimum value.
The nr_timeout_o and nr_timeout_t values are validated in conjunction with
a third timer value (dt), calculated as (nr_timeout_t - nr_timeout_o) / 3.
These 3 timer values are validated as described in nifftmt(7).
SEE ALSO
sys_attrs(5), nifftmt(7)
Network Administration: Connections
The time_to_dead field (shown in the EXAMPLES section and in
niffconfig -v) is the amount of time that expires between the
red alert being raised and the interface being declared dead. It
is calculated by the traffic monitor thread as t2 - t1 - (2 *
dt).
You can specify the values for t1, dt, and t2 in seconds (if the
MIF_MILLISECONDS bit is clear in the flags field), or in milliseconds (if
the MIF_MILLISECONDS bit is set). See the EXAMPLES section to see how this
is used.
The traffic monitor thread enforces the following restriction between the
timing parameters:
t2 >= t1 + 2dt
t1 >= 0.5
t2 >= 1.1
dt >= 0.2
In the preceding restrictions, the values for t1, dt, and t2 are in
seconds.
#include <stdio.h>
#include <string.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <sys/ioctl.h>
#include <sys/param.h>
#include <net/if.h>
#include <errno.h>
/* these strings map to the "state" enum */
char *state[] = {"INIT", "GREEN", "YELLOW", "ORANGE", "RED", "DEAD"};
/* usage: niff_example tu0 tu1 tu2...
* must supply the name of at least one
* network interface
*/
main(int ac, char **av)
{
int t1 = 20, t2 = 60, dt = 5;
char **oldav;
mif_t mif;
int s;
oldav = ++av;
s = socket(AF_INET, SOCK_DGRAM, 0);
/* tell the traffic monitor to start watching these interfaces */
while (*av) {
printf("Adding interface %s to the traffic monitor\n", *av);
bzero(&mif, sizeof (mif));
bcopy(*av, &mif.name[0], MIN(strlen(*av)+1, sizeof(mif.name)-1));
mif.t1 = t1;
mif.t2 = t2;
mif.dt = dt;
mif.flags = 0;
if (ioctl(s, SIOCTMTADD, &mif) < 0) {
perror("couldn't add interface");
break;
}
++av;
}
av = oldav;
/* get the status of the interfaces - NB will probably always
* be in the "init" state
*/
while (*av) {
printf("checking the status of interface %s\n", *av);
bzero(&mif, sizeof (mif));
bcopy(*av, &mif.name[0], MIN(strlen(*av)+1, sizeof(mif.name)-1));
if (ioctl(s, SIOCTMTSTATUS, &mif) < 0) {
perror("couldn't get status for interface");
break;
} else {
printf("Interface: %05s, state: %s ", mif.name,
state[miff.current_state]);
if (mif.flags & MIF_MILLISECONDS)
printf("Timer values in milliseconds...\n");
else
printf("Timer values in seconds...\n");
printf("t1: %d, dt: %d, t2: %d, time to dead: %d,
current_interval:%d, next time: %d\n",
mif.t1, mif.dt, mif.t2, mif.time_to_dead, mif.current_interval,
mif.next_time);
}
++av;
}
av = oldav;
/* tell the traffic monitor to stop watching */
while (*av) {
printf("deleting interface %s from the traffic monitor0, *av);
bzero(&mif, sizeof (mif));
bcopy(*av, &mif.name[0], MIN(strlen(*av)+1, sizeof(mif.name)-1));
if (ioctl(s, SIOCTMTREMOVE, &mif) < 0) {
perror("couldn't remove interface");
}
++av;
}
exit(0);
}
SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d dt] [-o t2] [-t t1]
[interface1 interface2...]
-d dt
Specifies the time period, in seconds, that the traffic monitor thread
uses between reads of the interface counters when it suspects there is
a connectivity problem. This number must be smaller than the number
given for t1 (see the -t option). The default time period is 5 seconds.
If dt is not specified, niffconfig uses the default.
-o t2
Specifies the total number of traffic-free seconds that must elapse
before the traffic monitor thread determines that a network interface
has failed. This number must be at least the sum of the t1 and two
times dt. That is, given the default time period for dt (5 seconds)
and t1 (20 seconds), the t2 value must be at least 30 seconds. The
default time period for t2 is 60 seconds. If t2 is not specified,
niffconfig uses the default.
-m Modifies the timing parameters of an interface that is already being
monitored. Typically, this option is specified along with one or more
of -t t1, -d dt, or -o t2 options. If none of these parameters are
specified, the default value is used. You cannot specify the -m option
with the -a, -s, -r, -u, or -v options.
-t t1
Specifies the time period, in seconds, that the traffic monitor thread
delays between reads of the interface counters when the network is run-
ning normally. The default time period is 20 seconds. If t1 is not
specified, niffconfig uses the default.
-v Displays the status, timer values, and description (verbose mode) of
all interfaces currently being monitored to standard out (stdout). See
nifftmt(7) for a definition of each of the parameters.
Except for the -u and -v options, all niffconfig options require one or
more network interfaces to be specified.
You can specify the t1, dt, and t2 timer values as decimal values (for
example, 2.6 or 0.8). When setting timer values with the -a or -m options,
all three timer values (t1, dt, and t2) are validated as described in
nifftmt(7). If the validation fails, the operation is cancelled and a mes-
sage is printed t o stdout.
NetRAIN initiates its own internal interface monitoring (using NIFF) when a
NetRAIN set is created. NetRAIN monitored interfaces are visible only with
the -v option. You cannot use niffconfig to perform any other management
operations on the NetRAIN interfaces. To modify the timer values for
NetRAIN monitored interfaces, use the ifconfig command.
You can start additional monitoring of an interface that is already being
monitored internally for NetRAIN. In that case, the niffconfig -v command
will display the two different monitoring structures for the interface.
All other niffconfig options will operate only on the non-NetRAIN monitor-
ing structure.
EXAMPLES
5. To display all parameters for all interfaces that are being monitored,
including NetRAIN interface monitoring, enter:
# niffconfig -v
The installation of Patch 1830.00 changes the information in the
wol(8)
wol(8)
NAME
wol - Send network packet to power on target system (wake-on-LAN)
SYNOPSIS
/usr/sbin/wol [nw_interface] hw_address
OPTIONS
nw_interface
Specifies the network interface to use in making the connection to the
target system, for example: tu1. This argument is optional.
OPERANDS
hw_address
Specifies the hardware network address of the target system, for exam-
ple: 00-02-56-00-03-29. This argument is mandatory.
DESCRIPTION
The wol utility generates and transmits a network packet to power on a
remote system. Before you can use the wol utility, you must enable the
remote system management wake-on-LAN feature on the target system.
You must specify the target system's hardware address. You may optionally
specify the network interface to use in making the connection to the target
system. If no network interface is specified, the wol utility locates the
first configured network interface and prompts you for confirmation.
To enable the wake-on-LAN feature, set the target system's wol_enable con-
sole variable to on and reset the system so that the network controller can
read the new state. Use one of the following methods to enable this feature
on the target system:
+ From the target system's console prompt. enter the following commands:
>>> set wol_enable on
>>> init
+ From the target system's UNIX root prompt, enter the following com-
mands:
% consvar -s wol_enable on
set wol_enable = on
% consvar -a
Console environment variables saved
% reboot
Use one of the following methods to disable the wake-on-LAN feature:
+ From the target system's console prompt. enter the following commands:
>>> set wol_enable off
>>> init
+ From the target system's UNIX root prompt, enter the following commands:
% consvar -s wol_enable off
set wol_enable = on
% consvar -a
Console environment variables saved
% reboot
Note
You must reset the target system for the new setting to take effect.
RESTRICTIONS
You must be logged in as root or have superuser privileges to use the wol
utility.
The wake-on-LAN feature is only available on specific platforms. On plat-
forms that support this feature, additional restrictions may apply. For
example, the wake-on-LAN feature may be supported on specific network
interface ports only. See your hardware documentation for additional infor-
mation.
EXIT STATUS
0 (Zero)
Success.
>0 An error occurred.
ERRORS
+ Error detecting default interface
Explanation:
The wol utility cannot automatically detect a default network inter-
face.
User Action:
-- Verify that a configured network interface exists on your system.
-- Manually specify a configured network interface on the wol com-
mand line.
+ Patterns must be specified as hex digits The Magic Packet address must
be specified as 00-11-22-33-44-55
Explanation:
The hardware network address entered was in the wrong format. This
argument must be in the following format: xx-xx-xx-xx-xx-xx, where x
is a hexadecimal character (0 through 9 and A through F, inclusive).
User Action:
Specify the hardware network address correctly.
EXAMPLES
1. The following example shows a simple use of the wol utility, where the
host system detects the first configured network interface and prompts
for confirmation:
# /usr/sbin/wol 00-02-56-00-03-29
No sending device specified, using tu0, continue? (y/n) y
2. The following example shows the same use of the wol utility, where the
user declines confirmation of the selected network interface:
# /usr/sbin/wol 00-02-56-00-03-29
No sending device specified, using tu0, continue? (y/n) n
Aborting...
3. The following example explicitly specifies a network interface:
# /usr/sbin/wol tu1 00-02-56-00-03-29
ENVIRONMENT VARIABLES
wol_enable
Enables or disables the wake-on-LAN feature on the target system. Valid
values are on and off.
Note
This is a system console variable, not a UNIX environment variable.
The DESCRIPTION section tells you how to enable the wake-on-LAN
feature on the target system. You must enable this feature before
you use the wol utility.
FILES
/usr/sbin/wol
Wake-on-LAN utility.
SEE ALSO
Commands: consvar(8), halt(8), reboot(8), shutdown(8)
New Hardware Delivery Release Notes and Installation Instructions
System Administration