 |
» |
|
|
|
This section addresses the following topics: Configuring HP Serviceguard Package Resource Dependencies with
the PSM | |
PSM enables you to create HP Serviceguard package dependencies for resources monitored
by EMS Hardware Monitors. To use the PSM with HP Serviceguard, you must configure one
or more of the resource instances available in PSM as HP Serviceguard
package dependencies. This creates an EMS monitoring request that
monitors the status of the resource and alerts HP Serviceguard if
the status of the resource changes. You can use the PSM monitoring requests as follows: When one copy of data is shared among all the nodes
in a cluster, you can fail over a package if the host adapter fails
on the node running the package. However, package failover to another
node might not occur successfully because buses, controllers, and
disks that are shared fail. To ensure proper failover in a shared
data environment, you must create identical package dependencies on
all nodes in the cluster. HP Serviceguard can compare the resource
UP values on all nodes and fail over to the node that has the correct
resources available. When each node in a cluster has its own copy of data,
you can fail over a package to another node for a host adapter, bus,
controller, or disk failure. In such a cluster of Web servers, where
each node has a copy of the data and users are distributed for load
balancing, you can fail over a package to another node with the correct
resources available. However, you must configure the package resource
dependencies on all the nodes in the same way.
| | | |  | NOTE: You must create the same requests on all nodes in a HP Serviceguard
cluster. | | | | |
Following are the methods for configuring PSM package dependencies: Using HP System Management Homepage (HP SMH) Editing the package configuration file
Configuring Package Dependencies by Editing the Configuration
File You can add PSM package dependencies by editing the package /etc/cmcluster/pkg.ascii configuration file. For
information on how to modify this file, see Managing HP Serviceguard
at: http://www.docs.hp.com When you use the HP Serviceguard commands, such as cmapplyconf, to specify the use of the PSM Resource
Monitor, do the following: Uncomment the section of the package
configuration file that has the RESOURCE_NAME keyword. Set the value of the desired resource
name.
The PSM has a different resource path name for the hardware
resource being monitored. For example, to create a dependency on a SCSI disk whose resource
path is /storage/status/disks/default/10_0_5.0.0, with a polling interval of 10 seconds and the UP state as the only
state that does not cause failover, you must add the following entry
to the configuration file: RESOURCE_NAME /storage/status/disks/default/10_0_5.0.0
RESOURCE_POLLING_INTERVAL 10
RESOURCE_UP_VALUE =UP |
| | | | | NOTE: You can configure package resource dependencies using HP SMH
on the HP-UX 11i v3 system. | | | | |
For information on how to configure package resource dependencies
or create EMS Monitoring Requests for PSM, using HP SMH on HP-UX 11i
v3, see Managing HP Serviceguard at: http://docs.hp.com/en/ha.html Copying Monitoring Requests | |
You copy monitoring requests for the following
reasons: To create requests for multiple resources using the same monitoring parameters. To create requests for the same resource using different monitoring parameters. This enables you to create
requests that send events using multiple notification methods.
| | | | | NOTE: To create requests for multiple resources
using the same monitoring parameters, or to create requests for the
same resource using different monitoring parameters,
you must configure at least one monitoring request for a similar instance. | | | | |
To create requests for multiple resources using the same monitoring
parameters, complete the following steps: Select the required monitoring
request in the EMS main window. Select Copy Monitoring
Request in the Actions menu. The Add Monitoring Request window is displayed. Select a different resource instance,
and click OK in the Add Monitoring Request
window. The Monitoring Request Parameters window is displayed. Click OK in the Monitoring Request Parameters window. The message
indicating that the new request is added and the EMS main window are
displayed.
To create requests for the same resource using different monitoring
parameters, complete the following steps: Select the required monitoring
request in the EMS main window. Select Copy Monitoring
Request in the Actions menu. The Add Monitoring Request window is displayed. Click OK in the Add Monitoring Request window. The Monitoring
Request Parameters window is displayed. Modify the parameters as desired
in the Monitoring Request Parameters window. Click OK. The message indicating that the new request is added
and the EMS main window are displayed.
Modifying Monitoring Requests | |
To change the monitoring parameters
of a monitoring request, complete the following steps: Select the monitoring request in
the EMS main window whose parameters you want to modify. Select Modify Monitoring
Request in the Actions menu. The Monitoring Request Parameters window is displayed. Modify the parameters as desired
in the Monitoring Request Parameters window. Click OK. The message indicating that the new request is modified
and the EMS main window are displayed.
Removing Monitoring Requests | |
The Remove Monitoring Requests option functions
with multiple requests and single requests. To remove monitoring requests, complete the following steps: In the EMS main window, select
the monitoring request you want to remove. Select Remove Monitoring
Requestin the Actions menu. A Confirmation window is displayed. Click OK. A message indicating that the new request is removed
and the EMS main window are displayed. To start monitoring the resource again, you must recreate the
request either by copying a similar request for a similar resource
or by re-entering the details.
Viewing Monitoring Requests | |
To view the parameters for a monitoring request,
complete the following steps: In the EMS main window, double-click
the monitoring request you want to view. The View Monitoring
Request Parameters window is displayed. The parameters listed here
must match the parameters specified for the monitoring request. Click OKto exit the View Monitoring Request screen.
Using the set_fixed Utility | |
Most monitors cannot detect when a failed hardware is repaired
and the resource returns to normal operation. These monitors cannot
alert the PSM to change the status of the hardware from DOWN to UP.
Therefore, you must manually change the status of the hardware using
the set_fixed utility included in the PSM. To determine whether a monitor requires
the use of the set_fixed utility,
see the monitor data sheets at: http://docs.hp.com/en/diag For information on how to change the state of a resource, see set_fixed(1M). | | | |  | IMPORTANT: Ensure that you have repaired the problem before you use the set_fixed utility to return the hardware status
to UP. If the hardware is not repaired, the change in status to UP
can cause HP Serviceguard to behave as though the hardware is working
properly. | | | | |
To restore the operating status of a resource to UP, complete
the following steps: At the HP-UX prompt, enter the
following command to view the hardware resources whose status is DOWN: # /etc/opt/resmon/lbin/set_fixed -L At the HP-UX prompt, enter the
following command to change the status of the hardware resource to
UP: # set_fixed -n <resource_name> Replace resource_name with the status resource path name to
the hardware resource that is repaired. While specifying the resource_name,
you can use wildcards such as * to indicate all instances. The following example illustrates how to set the status of the
SCSI tape device at hardware path 10_12_5.0.0 to UP: # set_fixed -n /storage/status/tapes/SCSI_tape/10_12_5.0.0 The following example illustrates how to set the status of all
AutoRAID disk arrays to UP: # set_fixed -n /storage/status/disk_arrays/AutoRAID/*
Replicating Configuration Settings on Multiple Systems | |
To replicate the monitor configuration settings on multiple systems, complete
the following steps: Configure settings on one system
using the monconfig utility. The monitor /var/stm/config/tools/monitor/*.sapcfg file is created. Modify the following configuration
files, if required: /var/stm/config/tools/monitor/*.cfg, default_*.clcfg /var/stm/config/tools/monitor/Global.cfg /var/stm/data/tools/monitor/
| | | | | NOTE: If you do not choose to modify these configuration files, the
default values are used. | | | | |
Copy all the /var/stm/config/tools/monitor/*.cfg, default_*.clcfg, and *.sapcfg files on the new system. Do not copy a file with the name predictive, rst (ISEE), wbem, or ovfn (HPEN) in the file
name. | | | | | IMPORTANT: If you choose OpenView Configuration (OVC), you must set the
initial configuration on a system that has OVC installed. Otherwise,
OVC will not be available for use in the monconfig utility. | | | | |
Enter the following command at
the HP-UX prompt to enable the new configuration: # /etc/opt/resmon/lbin/startcfg_client |
|
Printable version
