wlmd man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

wlmd(1M)							      wlmd(1M)

NAME
       wlmd - activate the HP-UX Workload Manager (WLM)

SYNOPSIS
       [-p] [-s] [-t] [-W] [-i] [-l logopt[=n][,...]]
       [-p] [-s] [-t] [-W] [-i] [-l logopt[=n][,...]]
       [-W]

DESCRIPTION
       can  activate  the  HP-UX WLM configuration (using either the specified
       configfile or the most recent configuration) or	check  the  syntax  of
       configfile  without activating the configuration.  When a configuration
       is activated, the HP-UX WLM daemon is started and a copy of the config‐
       uration	is made. The daemon then starts all the data collectors speci‐
       fied in the configuration file. Every interval, as defined in the  con‐
       figuration  file,  the  HP-UX  WLM daemon checks for data from the data
       collectors and automatically adjusts CPU	 allocations,  if  needed,  to
       better achieve the specified SLOs.

       In  addition  to	 the WLM management within systems and partitions pro‐
       vided by WLM can manage workloads across nPartitions and virtual parti‐
       tions  (vPars)  using  its global arbiter This arbiter takes input from
       the WLM instances on the partitions, then  moves	 cores	across	parti‐
       tions,  if needed, to better achieve the SLOs specified in the WLM con‐
       figuration files that are active in the partitions.   These  partitions
       can  be	nested--and even contain FSS or PSET-based workload groups. (A
       core is the actual data-processing engine within a processor,  where  a
       processor might have multiple cores.)  also provides management of Tem‐
       porary Instant Capacity and Pay per use resources.  For	more  informa‐
       tion, see the wlmpard(1M) manpage.

       WLM  can	 also manage workloads within an HP Integrity Virtual Machines
       environment. For more information and certain  restrictions,  refer  to
       the wlm(5) manpage.

       To  start  automatically	 at  system  boot,  edit the file /etc/rc.con‐
       fig.d/wlm.

OPTIONS
       Displays usage information and exits.
	    This option overrides all other options.

       Displays version information and exits.	This option overrides all
	    options other than

       Displays the most recent WLM  configuration,  appending	two  commented
       lines
	    that indicate the origin of the configuration.

       Initializes workload group assignments, ensuring a new configuration's
	    user,  Unix	 group,	 compartment, and application records are used
	    when the same workload groups exist in the active and new WLM con‐
	    figurations.

	    Use this option when the following conditions are met:

	    ·  You  have  workload groups that are in both the active WLM con‐
	       figuration and the new configuration that you want to activate

	    ·  You are going to activate the new configuration	without	 first
	       stopping the WLM daemon

	    Without if a currently running process is in a workload group that
	    also exists in the new configuration, the process  stays  in  that
	    group  regardless of application, compartment, Unix group, or user
	    records in the new configuration.

	    The option is only valid with the options.

       Causes WLM to run in passive mode. In this mode, you can	 see  how  WLM
       will
	    approximately  respond  to a configuration--without the configura‐
	    tion actually taking control  of  your  system.  Using  this  mode
	    allows  you	 to  analyze  various items in your configuration. For
	    more information on this mode, including its limitations, see  the
	    wlm(5) manpage.

	    To	see how the configuration would affect your workloads, use the
	    WLM utility

	    Do not rely on or to observe  changes  when	 using	passive	 mode.
	    These  utilities  will  display a configuration WLM uses to create
	    the passive mode. However, you can use to gather CPU usage data.

	    The option must be used with either the options.

	    When managing with both and if you use you must also use

       Causes WLM to run in secure mode if you have distributed security
	    certificates to the systems in question. For more  information  on
	    using security certificates, see the wlmcert(1M) manpage.

	    WLM	  runs	 in   secure   mode   by  default  when	 you  use  the
	    /sbin/init.d/wlm script to start WLM. If you upgraded WLM,	secure
	    mode  might	 not  be the default. Ensure that the following secure
	    mode variables  are	 enabled  in  /etc/rc.config.d/wlm.   You  can
	    change the default by editing the values for these variables.

       Generates  comma-separated  audit data files. These files are placed in
       the
	    directory /var/opt/wlm/audit/ and  are  named  wlmd.monyyyy,  with
	    monyyyy representing the month and year the data was gathered. You
	    can access these files directly or through the command.  has audit
	    data  to display only when you use the option.) For information on
	    or on the format of the data files, see the wlmaudit(1M) manpage.

	    Be sure to set in your WLM configuration file as indicated in  the
	    wlmconf(4) manpage when you use the option.

       Activates a copy of the most recent WLM configuration.

       Prints  warning	messages  found when parsing the configuration file as
       error
	    messages. The option is only valid with the and options.

       Activates the configuration specified in the file
	    configfile.	 If configfile is not valid, an error message is  dis‐
	    played, and exits.

       Checks the configuration specified in the file
	    configfile	for  syntax  errors.  The current configuration is not
	    affected.

       Causes wlmd to log statistics to the file
	    /var/opt/wlm/wlmdstats. Use this data for tuning your WLM configu‐
	    ration. Acceptable values for logopt are:

	    Logs  statistics  for every group, host, metric, and SLO every WLM
	    interval

	    Logs statistics for every group, host, metric, and SLO every
		      n WLM intervals

	    Logs group statistics every WLM interval

	    Logs group statistics every
		      n WLM intervals

	    Logs host statistics every WLM interval

	    Logs host statistics every
		      n WLM intervals

	    Logs metric statistics every WLM interval

	    Logs metric statistics every
		      n WLM intervals

	    Logs SLO statistics every WLM interval

	    Logs SLO statistics every
		      n WLM intervals

	    The option is ignored unless used with the option. When  the  same
	    logopt  is	specified multiple times, the last one specified takes
	    precedence.

	    Combine multiple values separating them with a comma. The  follow‐
	    ing combination requests all the statistics--with the exception of
	    the host statistics, which have been turned off:

	    In data reports such as those provided by the reported CPU	(core)
	    usage represents the amount of CPU resources the group used in the
	    last WLM interval. However, the  group's  reported	allocation  is
	    from  the  current	WLM interval. As a result, comparisons between
	    these two numbers could lead mistakenly to the conclusion that the
	    usage exceeds the allocation.

	    You	   can	 use   the   command   to   review   statistics	  from
	    /var/opt/wlm/wlmdstats. For example, to view SLO data, enter:

	    % wlminfo slo -o

	    In place of you can also use or For more information  on  see  the
	    wlminfo(1M) manpage.

	    You	 can  enable automatic trimming of the wlmdstats file by using
	    the tunable in your WLM configuration. For more  information,  see
	    the wlmconf(4) manpage.

       Kills any running instance of
	    Use this option to shutdown HP-UX Workload Manager.

RETURN VALUE
       returns exit status if no errors occur, or if there are errors.

       and  return exit status if no errors occur or nonzero if the configura‐
       tion file is invalid or there were errors while activating the configu‐
       ration.

       returns	exit status if no errors occur or nonzero if the running could
       not be confirmed as killed.

EXAMPLES
       Check the configuration file for syntax errors:

	      configfile

       Activate the specified configuration file and move all  currently  run‐
       ning  configured	 applications  and  user  processes  to their assigned
       groups:

	      configfile

       Activate the specified configuration file, leave all currently  running
       application  and	 user  processes  in their current groups, and collect
       logging statistics every fifth WLM interval:

	      configfile

WARNINGS
       Do not use while is active.

DEPENDENCIES
       Starting with WLM A.03.01, WLM no longer includes PRM  in  the  bundle.
       If  any version of PRM is already on the machine where you install WLM,
       or if you upgrade WLM, you can continue to manage  FSS  and  PSET-based
       workload	 groups	 (just as if PRM had been installed with WLM--when you
       purchase WLM, you receive a PRM license that enables  you  to  continue
       using PRM). In addition, upgrading WLM no longer triggers a reboot.

       If you are installing WLM for the first time on a machine, you can only
       use strictly host-based configurations--configurations designed	exclu‐
       sively for moving cores across HP-UX Virtual Partitions or nPartitions,
       or for activating Temporary Instant Capacity or Pay per use cores.   To
       manage  FSS  and PSET-based workload groups, you must install PRM sepa‐
       rately.

       When the Servicecontrol Manager (SCM) bundle is built  during  the  WLM
       installation,  it  will	include	 the  PRM  API	only if PRM is already
       installed.  WLM uses the PRM API to dynamically adjust the CPU  alloca‐
       tions of the PRM groups to which managed workloads are assigned (in WLM
       terminology, these PRM groups  are  known  as  PSET  and	 FSS  workload
       groups).	 WLM adjusts the CPU allocations to achieve the specified ser‐
       vice-level objectives (SLOs).

       WLM also uses the PRM API to set memory and disk bandwidth allocations,
       if defined. Furthermore, the PRM API is used when dynamically adjusting
       memory allocations (if defined) to  compensate  for  inactive  workload
       groups (workload groups with no active SLOs).

AUTHOR
       was developed by HP.

FEEDBACK
       If  you would like to comment on the current HP-UX WLM functionality or
       make suggestions for future releases, please send email to:

       wlmfeedback@rsn.hp.com

FILES
       system initialization directives

       default message log

       optional statistics log

       process mutual exclusion lock file

       copy of most recent configuration file

SEE ALSO
       wlmaudit(1M), wlmemsmon(1M), wlminfo(1M), wlmpard(1M), libwlm(3),  wlm‐
       conf(4), wlm(5)

       HP-UX Workload Manager User's Guide (/opt/wlm/share/doc/WLMug.pdf)

       HP-UX Workload Manager homepage (http://www.hp.com/go/wlm)

								      wlmd(1M)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net