 |
» |
|
|
 |
|  |  |
gWLM 提供兩個屬性檔案,讓您控制多種 gWLM 行為。一個檔案適用於 CMS 協助程式,另一個則用於所有的受管理節點。若需這些檔案控制行為的相關資訊,請詳讀這些檔案。 CMS 屬性 (/etc/opt/gwlm/conf/gwlmcms.properties) |  |
gwlmcms.properties 檔案顯示如下。  |
#
# (C) Copyright 2004-2006 Hewlett-Packard Development Company, L.P.
#
# $Date: 2007/05/17 08:33:25 $
# $Revision: 1.6 $
#
# Contents:
# This file contains the default configuration values for the
# Global Workload Manager CMS.
#
# You must restart gwlmcmsd for changes made to this file
# to take effect--unless otherwise noted.
#
#
# Set FileHandler /var/opt/gwlm/gwlmcmsd.log.0 log level.
# Valid levels, from most severe to least, are:
# SEVERE
# WARNING
# INFO
# CONFIG
# FINE
# FINER
# FINEST
# When you set the level, you will see messages only from that level and
# the levels that are more severe.So, the SEVERE level produces the fewest
# messages, while the FINEST level includes messages from all seven levels.
#
com.hp.gwlm.util.Log.logLevel = INFO
#
# Turn on/off ConsoleHandler.ConsoleHandler uses the same log
# level as defined for FileHandler /var/opt/gwlm/gwlmcmsd.log.0.
#
com.hp.gwlm.util.Log.ConsoleHandler = off
#
# Support for the database cache on the CMS.
#
# cachesize:
# The number of database objects that should be cached in memory
# in order to reduce the number of round-trip operations.
# If you set this property to a value that is too low, gWLM will
# use a default value of 4096.
#
com.hp.gwlm.cms.cachesize = 100000
#
# Support for local data caching on a remote node for report generation.
# These properties are defined on the CMS but are pushed out to the remote
# node managers during deployment of an SRD.The cached objects on the
# agent consume an amount of memory approximated by:
#
# Memory = 5000 * workloads * cachesize * (60 / resource_domain_interval)
#
# bytes of memory.For example, if there are 4 workloads deployed with a
# 15 second interval and a cachesize of 20 minutes, the agent will need:
#
# Memory = 5000 * 4 * 20 * (60 / 15) ~ 2.5 MB.
#
# cachesize:
# The number of minutes of real-time data to maintain on the remote
# node for future CMS access.This value must be at least three
# times the 'samples' value specified below.The default value is
# 20 minutes.
#
# samples:
# The number of minutes of real-time data used to aggregate into a
# historical data point.The default is to aggregate the data into
# 5-minute averages.
#
com.hp.gwlm.node.cachesize = 20
com.hp.gwlm.node.samples = 5
#
# Support for real-time graphing properties.
#
# viewport:
# The size of the displayed real-time graph (in minutes).
#
# refresh:
# The refresh rate of the real-time graphs and tables (in seconds).
#
com.hp.gwlm.ui.monitor.viewport = 20
com.hp.gwlm.ui.monitor.refresh = 15
|
 |
代理程式屬性 (/etc/opt/gwlm/conf/gwlmagent.properties) |  |
 |  |  |  |  | 附註: 您必須重新啟動每一個曾修改屬性檔案的受管理節點上之 gwlmagent 協助程式,方可使檔案變更內容生效。 |  |  |  |  |
gwlmagent.properties 檔案顯示如下。  |
#
# (C) Copyright 2004-2006 Hewlett-Packard Development Company, L.P.
#
# $Date: 2007/05/17 08:33:25 $
# $Revision: 1.6 $
#
# Contents:
# This file contains the default configuration values for the
# Global Workload Manager Agent on a given managed node.The
# agent on each managed node uses the default values unless you
# edit that node's gwlmagent.properties file.
#
# You must restart gwlmagent for changes made to this file to
# take effect.
#
#
# Set FileHandler /var/opt/gwlm/gwlmagent.log.0 log level.
# Valid levels, from most severe to least, are:
# SEVERE
# WARNING
# INFO
# CONFIG
# FINE
# FINER
# FINEST
# When you set the level, you will see messages only from that level and
# the levels that are more severe.So, the SEVERE level produces the fewest
# messages, while the FINEST level includes messages from all seven levels.
#
com.hp.gwlm.util.Log.logLevel = INFO
#
# Specify the size (in MB) and number of files to use
# for logging.For a single file of unlimited size, set
# logFileSize to negative one (logFileSize=-1).
# Otherwise, total log file size is
# logFileSize * logNFiles
#
com.hp.gwlm.util.Log.logFileSize = 20
com.hp.gwlm.util.Log.logNFiles = 3
#
# Turn on/off ConsoleHandler.ConsoleHandler uses the same log
# level as defined for FileHandler /var/opt/gwlm/gwlmagent.log.0.
#
com.hp.gwlm.util.Log.ConsoleHandler = off
#
# Set the number of seconds for the high availability (HA) minimum
# timeout.Communication is considered lost on a managed node
# once the timeout period has elapsed.
#
# By default, communication is not considered lost until 10 allocation
# intervals have elapsed without communication.The default value of the
# property (60) is used only when the allocation interval is less than 6
# seconds.
#
com.hp.gwlm.node.HA.minimumTimeout = 60
#
# Enable/disable use of Instant Capacity (iCAP) to simulate movement of
# cores across nPartitions.To use iCAP, you must enable this property on
# each managed nPartition where you want to take advantage of iCAP.Also,
# each nPartition must meet the requirements outlined in the online help
# topic "Getting the most out of gWLM" as well as in the section "USING
# NPARS AS COMPARTMENTS IN AN SRD" in the gwlmxml(4) man page on HP-UX or
# the gwlmxml(5) man page on Linux.
#
com.hp.gwlm.platform.icap.manageWithIcap = on
#
# Set the minimum number of Temporary Instant Capacity (TiCAP) minutes
# that must be available for TiCAP activation. gWLM will stop using
# TiCAP when the available balance goes below this threshold.The
# same value should be set on all agents managing the SRD.To use
# TiCAP, it must be available on the complex and enabled at the policy
# level or the SRD level.
#
com.hp.gwlm.node.ticap.minimumBalance = 30
|
 |
通訊連接埠 |  |
下列為 gWLM 用於通訊的連接埠: 受管理的節點: 9617 CMS: 9618 若需變更這些連接埠,請將下列各行: com.hp.gwlm.cms.port = 連接埠X com.hp.gwlm.node.port = 連接埠Y 新增至下列兩個屬性檔案中: /etc/opt/gwlm/conf/gwlmcms.properties /etc/opt/gwlm/conf/gwlmagent.properties 連接埠X 和連接埠Y 的值不得相同。 跨所有受管理節點和在 CMS 上的所有屬性檔案,其 com.hp.gwlm.cms.port 屬性需具相同的連接埠X 值。相同地,跨所有受管理節點和在 CMS 上的所有屬性檔案,其 com.hp.gwlm.node.port 屬性需具相同的連接埠Y 值。 您必須重新啟動 gwlmcmsd 和 gwlmagent,方可使變更內容生效。若是透過 HP Systems Insight Manager (SIM) 使用 gWLM,還必須停止 (/opt/mx/bin/mxstop) 並重新啟動 (mxstart) SIM。  |  |  |  |  | 附註: 重新啟動 gwlmcmsd 會暫時停用 HP Integrity Essentials 虛擬化管理員和 HP Integrity Essentials 容量規劃員。 |  |  |  |  |
|