回到網頁內容 臺灣-繁體中文
HP.com 首頁 產品資訊 支�#169;及驅動程式 解決方案 如何購買
» 聯絡 HP
進階選項
HP.com 首頁
HP 全域工作負載管理員 4.0 版使用指南 > 第 5 章. 其他的配置與管理作業

設定 gWLM 屬性

» 

技術文件

PDF 格式的完整書籍
» 回饋意見
內容©韟像B開©l

 » 目錄

 » 索引

gWLM 提供兩個屬性檔案,讓您控制多種 gWLM 行為。一個檔案適用於 CMS 協助程式或服務,另一個則用於所有的受管理節點。若需這些檔案控制行為的相關資訊,請詳讀這些檔案。

CMS 屬性

在 HP-UX 上,CMS 屬性位於 /etc/opt/gwlm/conf/gwlmcms.properties,而在 Windows 上則位於 C:\Program Files\HP\Virtual Server Environment\conf\gwlmcms.properties (指定的 Windows 路徑為預設值,但安裝時可能會選擇不同的路徑)。

附註: 僅在協助程式啟動或服務時,gWLM 才會讀取某些值;其他的值則在部署 SRD 後讀取。若需讀取個別屬性時的相關資訊,請參閱此檔案。

重新啟動 gwlmcmsd 會暫時停用 HP 虛擬化管理員 (HP Virtualization Manager) 和 HP 容量規劃員 (HPCapacityAdvisor)。

gwlmcms.properties 檔案顯示如下。

#
# (C) Copyright 2004-2008 Hewlett-Packard Development Company, L.P.
#
# $Date: 2008/02/01 19:00:32 $
# $Revision: 1.28 $
#
# 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 log level for the following log files:
#       /var/opt/gwlm/gwlmcmsd.log.0
#       /var/opt/gwlm/gwlmcommand.log.0
#       /var/opt/gwlm/gwlm.log.0
#       /var/opt/vse/logs/gwlminitconfig.log.0
# 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

#
# Support for automatic database statistics gathering.  These properties
# control how often row-level statistics are gathered from the database in
# order to optimize performance.
#
#   com.hp.gwlm.cms.db.analyze.time:
#       Frequency, in minutes, in which statistics are gathered.本
#       default is to attempt to gather database statistics every 60
#       minutes.  When the analysis runs, statistics will only be gathered
#       if a certain number of transactions  have been processed (which is
#       configured in the property below).
#
#   com.hp.gwlm.cms.db.analyze.limit:
#       Number of consecutive transactions that must take place before a
#       database analysis is performed.
#
com.hp.gwlm.cms.db.analyze.time  = 60
com.hp.gwlm.cms.db.analyze.limit = 50

#
# Support for the database cache on the CMS.
#
#   cachesize:
#	The number of historical configurations to cache in memory.
#	A larger historical configuration cache reduces time spent
#	in database lookups.  The valid range is 1-1000.
#
com.hp.gwlm.cms.cachesize = 100

#
# 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

代理程式屬性

在 HP-UX 上,代理程式屬性位於 /etc/opt/gwlm/conf/gwlmagent.properties,而在 Windows 上則位於 C:\Program Files\HP\Virtual Server Environment\conf\gwlmagent.properties (指定的 Windows 路徑為預設值,但安裝時可能會選擇不同的路徑)。

附註: 您必須重新啟動每一個曾修改屬性檔案的受管理節點上之 gwlmagent 協助程式,方可使檔案變更內容生效。

gwlmagent.properties 檔案顯示如下。

#
# (C) Copyright 2004-2007 Hewlett-Packard Development Company, L.P.
#
# $Date: 2007/04/12 15:46:19 $
# $Revision: 1.17 $
#
# 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

#
# 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

新增至下列兩個屬性檔案中:

  • gwlmcms.properties

    在 HP-UX 上,此檔案位於 /etc/opt/gwlm/conf/ 中。在 Windows 上則位於 C:\Program Files\HP\Virtual Server Environment\conf\ (指定的 Windows 路徑為預設值,但安裝時可能會選擇不同的路徑)。

  • /etc/opt/gwlm/conf/gwlmagent.properties

連接埠X連接埠Y 的值不得相同。

跨所有受管理節點和在 CMS 上的所有屬性檔案,其 com.hp.gwlm.cms.port 屬性需具相同的連接埠X 值。相同地,跨所有受管理節點和在 CMS 上的所有屬性檔案,其 com.hp.gwlm.node.port 屬性需具相同的連接埠Y 值。

您必須重新啟動 gwlmcmsdgwlmagent,方可使變更內容生效。若透過 HP SIM 使用 gWLM,亦須重新啟動 HP SIM (在 HP-UX 上,請使用 /opt/mx/bin/mxstopmxstart 重新啟動 SIM 協助程式。在 Windows 上則重新啟動 HP Systems Insight Manager 服務)。

附註: 重新啟動 gwlmcmsd 會暫時停用「HP 虛擬化管理員」和「HP 容量規劃員」。
可列印版本
隱私權聲明 使用範圍與著作權聲明
© 2004-2008 Hewlett-Packard Development Company, L.P.