HP UX 11i Workload Management (gWLM/WLM) Software manual # gwlm undeploy --srd=SRD--force

Page 44

1.Delete the deployed.config file on each managed node:

#rm -f /etc/opt/gwlm/deployed.config

2.Force an undeploy of the SRD (named SRD below) to ensure the CMS and the managed nodes agree on the SRD’s state. Run the following command on the CMS:

#gwlm undeploy --srd=SRD--force

3.Restart the gwlmagent daemon on each managed node:

#/opt/gwlm/bin/gwlmagent --restart

NOTE: If the gWLM CMS and agent disagree about whether an SRD is deployed or undeployed, you can use the --forceoption with the gwlm deploy or gwlm undeploy commands.

44 Additional configuration and administration tasks

Image 44
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Additional configuration and administration tasks Support and other resourcesIndex Benefits of using gWLM Comparison of PRM, WLM, and gWLM featuresOverview GWLM OverviewConcepts and terms for using gWLM Scheduler fss group. gWLM manages a workload byWould make for a workload-without actually affecting GWLM management model SRDHow gWLM allocates CPU resources Available interfaces AssumptionsWhere to find additional information Finding more gWLM informationLearn about other gWLM commands Configuring gWLM to manage workloads Policy typesPolicy types Choosing a policy type Choosing a policy typeUsing the wizard Seeing how gWLM will perform without affecting the systemGetting started with gWLM Combining the different policy typesSeeing gWLM in action # /opt/gwlm/bin/gwlmagent# perl -e ’print $$\nwhile 1 ’ & 1 Common uses for gWLM Fixing the amount of CPU resources a workload getsCommon configuration tasks Setting up gWLM initial setup stepsChanging from advisory mode to managed mode Creating a new policyEditing a policy Changing which policy is associated with a workloadAdding a new compartment or GiCAP group member to an SRD Stop managing a workloadStop managing an SRD Quick Link Option Viewing gWLM reports in monitor-Only mode Monitoring workloads and gWLMMonitoring workloads High-Level viewMonitoring gWLM from the command line Message logsHP-UX /var/opt/gwlm/gwlmcommand.log.0 Viewing HP Systems Insight Manager events Monitoring gWLM with GlancePlusSecurity General security topicsSecuring gWLM communications Securing database communicationsSecurity Additional configuration and administration tasks Manually adjusting CPU resourcesManually adjusting memory resources Setting aside space for historical dataSetting cache size for historical configuration data Setting database recovery modelCreating a database maintenance plan Tips for backup and restoreSetting gWLM properties CMS propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Controlling gWLM’s startup behavior Communications ports # /opt/gwlm/bin/gwlmagent --enablestartonboot How the automatic restart works Related eventsManually clearing an SRD Node Failed to Rejoin SRD on Start-up event# gwlm undeploy --srd=SRD--force Nesting partitions Nested partitionsUsing gWLM with Hyper-Threading Changing the interval on the command lineChanging the gWLM resource allocation interval Changing the interval in HP System Insight ManagerUsing gWLM with hosts on multiple LANs Shows a possible scenarioCreating Golden Images Multiple network interface cardsIncorrectly configured host name or IP address Get the IP address configured for the host using nslookupUnable to create new native thread Enabling or disabling dumping core for gWLMCore dump file is available in root directory How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPTypographic conventions HP authorized resellersRelated information User input Documentation feedback Compatibility with agents Global Workload Manager known issues LimitationsUnable to build a single shared resource domain Compatibility with PRM and WLMHost name aliases are not supported Making a configuration change to a large SRD is slowRare incompatibility with virtual partitions Deleting workloads takes a long time Integrity VM prevents discovery of psets and fss groupsCustom metrics lost on redeploy Information error during shutdownProcess placement using psrset is ignored Major issues Documentation or minor issues Remove old configuration data from the gWLM databaseCell-local processors and iCAP environment CMS is slow to respondModifying Java while gWLM is running Error during discovery of compartmentsCombining psets and virtual partitions Only one SRD is allowed to be deployed Missing or unexpected historical data system clocks differSample missing at start or end of gwlmreport output Processes moved to default pset or default fss group SRD deployment times out and displays a blank screenApplication hangs in fss group Scripts not placed in correct workloadsUnable to remove workload from nested partitions SRD Configuration of agent and CMS not synchronizedChanges in sizes in Discovery Missing historical data gWLM CMS daemon/service restarted Negative current size for NonvmUnmanaging a VM or vPar that is on leaves SRD undeployed Index SRDIndex