HP UX 11i Workload Management (gWLM/WLM) Software manual Manually clearing an SRD

Page 43

For information on enabling and viewing these events, refer to Optimize→Global Workload Manager→Events.

You can then view these events using the Event Lists item in the left pane of System Insight Manager.

The following sections explain how to handle some of the events.

“Node Failed to Rejoin SRD on Start-up” event

If you see the event “Node Failed to Rejoin SRD on Start-up”:

1.Restart the gwlmagent on each managed node in the affected SRD:

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

2.Verify the agent rejoined the SRD by monitoring the Shared Resource Domain View in System Insight Manager or by using the gwlm monitor command.

3.If the problem persists, check the files /var/opt/gwlm/gwlmagent.log.0 and /var/ opt/gwlm/gwlmcmsd.log.0 for additional diagnostic messages.

“SRD Communication Issue” and “SRD Reformed with Partial Set of Nodes” events

NOTE: Reforming with a partial set of nodes requires a minimum of three managed nodes in the SRD.

NOTE: “SRD Communication Issue” events are not enabled by default. To see these events, configure your events in System Insight Manager through the HP Matrix OE visualization menu bar using Tools→Global Workload Manager→Events.

If you have an SRD containing n nodes and you get n - 1 of the “SRD Communication Issue” events but no “SRD Reformed with Partial Set of Nodes” events within 5 minutes (assuming an allocation interval of 15 seconds) of the first “SRD Communication Issue” event, you might need to restart the gwlmagent on each managed node in the affected SRD:

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

Manually clearing an SRD

If gWLM is unable to reform an SRD, you can manually clear the SRD, as described in the following section.

Clearing an SRD of A.02.50.00.04 (or later) agents

The following command is an advanced command for clearing an SRD. The recommended method for typically removing a host from management is by using the gwlm undeploy command.

Starting with A.02.50.00.04 agents, you can manually clear an SRD with the following command:

#gwlm reset --host=host

where host specifies the host with the SRD to be cleared.

If this command does not work, use the procedure given in the following section.

Clearing an SRD of agents of any version

The procedure in this section clears an SRD regardless of the version of the agents in the SRD.

The gwlm command is added to the path during installation. On HP-UX systems, the command is in /opt/gwlm/bin/. On Microsoft Windows systems, the command is in C:\Program Files\ HP\Virtual Server Environment\bin\gwlm\ by default. However, a different path might have been selected at installation.

NOTE: You must be logged in as root on HP-UX or into an account that is a member of the Administrators group on Windows to run the commands below.

Automatic restart of gWLM’s managed nodes in SRDs (high availability) 43

Page 42 Page 44
Image 43
Page 42 Page 44
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Support and other resources Additional configuration and administration tasksIndex GWLM Overview Benefits of using gWLMComparison of PRM, WLM, and gWLM features OverviewScheduler fss group. gWLM manages a workload by Concepts and terms for using gWLMWould make for a workload-without actually affecting SRD GWLM management modelHow gWLM allocates CPU resources Assumptions Available interfacesFinding more gWLM information Where to find additional informationLearn about other gWLM commands Policy types Configuring gWLM to manage workloadsPolicy types Choosing a policy type Choosing a policy typeCombining the different policy types Using the wizardSeeing how gWLM will perform without affecting the system Getting started with gWLM# /opt/gwlm/bin/gwlmagent Seeing gWLM in action# perl -e ’print $$\nwhile 1 ’ & 1 Fixing the amount of CPU resources a workload gets Common uses for gWLMSetting up gWLM initial setup steps Common configuration tasksCreating a new policy Changing from advisory mode to managed modeChanging which policy is associated with a workload Editing a policyStop managing a workload Adding a new compartment or GiCAP group member to an SRDStop managing an SRD Quick Link Option High-Level view Viewing gWLM reports in monitor-Only modeMonitoring workloads and gWLM Monitoring workloadsMessage logs Monitoring gWLM from the command lineHP-UX /var/opt/gwlm/gwlmcommand.log.0 Monitoring gWLM with GlancePlus Viewing HP Systems Insight Manager eventsSecuring database communications SecurityGeneral security topics Securing gWLM communicationsSecurity Manually adjusting CPU resources Additional configuration and administration tasksSetting aside space for historical data Manually adjusting memory resourcesTips for backup and restore Setting cache size for historical configuration dataSetting database recovery model Creating a database maintenance planCMS properties Setting gWLM propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Communications ports Controlling gWLM’s startup behavior# /opt/gwlm/bin/gwlmagent --enablestartonboot Related events How the automatic restart worksNode Failed to Rejoin SRD on Start-up event Manually clearing an SRD# gwlm undeploy --srd=SRD--force Nested partitions Nesting partitionsChanging the interval in HP System Insight Manager Using gWLM with Hyper-ThreadingChanging the interval on the command line Changing the gWLM resource allocation intervalShows a possible scenario Using gWLM with hosts on multiple LANsMultiple network interface cards Creating Golden ImagesGet the IP address configured for the host using nslookup Incorrectly configured host name or IP addressEnabling or disabling dumping core for gWLM Unable to create new native threadCore dump file is available in root directory Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesRelated information HP authorized resellersTypographic conventions User input Documentation feedback Compatibility with agents Limitations Global Workload Manager known issuesCompatibility with PRM and WLM Unable to build a single shared resource domainRare incompatibility with virtual partitions Making a configuration change to a large SRD is slowHost name aliases are not supported Integrity VM prevents discovery of psets and fss groups Deleting workloads takes a long timeProcess placement using psrset is ignored Information error during shutdownCustom metrics lost on redeploy Major issues Remove old configuration data from the gWLM database Documentation or minor issuesCMS is slow to respond Cell-local processors and iCAP environmentCombining psets and virtual partitions Error during discovery of compartmentsModifying Java while gWLM is running Sample missing at start or end of gwlmreport output Missing or unexpected historical data system clocks differOnly one SRD is allowed to be deployed Scripts not placed in correct workloads Processes moved to default pset or default fss groupSRD deployment times out and displays a blank screen Application hangs in fss groupChanges in sizes in Discovery Configuration of agent and CMS not synchronizedUnable to remove workload from nested partitions SRD Negative current size for Nonvm Missing historical data gWLM CMS daemon/service restartedUnmanaging a VM or vPar that is on leaves SRD undeployed SRD IndexIndex
Top Page Image Contents