L Migrating EMS Resources to Generic Resources

To migrate from EMS resource to generic resource for monitoring resources, follow these steps:

1.Identify the EMS resource that is configured, resource_start, and polling interval.

2.If this is a standard EMS resource then identify the equivalent SFM style resource monitor. In this case, the equivalent SFM style resource monitor is the SFM provider class HPUX_PhysicalVolume that is used to monitor the physical volumes which are a part of a Logical volume group (LVM).

For more information, see the HP-UX WBEM LVM Provider Datasheet at http://www.hp.com/ go/hpux-core-docs—>HP-UX 11i Volume Management (LVM/VxVM) Software.

3.Create a monitoring script to contain the logic to monitor the resource. A sample script is provided by HP in the /etc/cmcluster/examples directory. You can use this script by customizing it according to your requirements.

See “Monitoring Script for Generic Resources” (page 390) and “Template of a Monitoring Script” (page 392) for details on monitoring scripts and a template.

4.Configure a generic resource by choosing an appropriate name.

5.Identify the generic_resource_evaluation_type that you would wish to specify. (See parameter explanation (page 245)).

6.Test the monitoring script to ensure that the monitoring is working fine as expected.

If the EMS resource is of type AUTOMATIC, then configure the generic resource with 'evaluation_type' as before_package_start. Skip steps from 7–12 and proceed from step 13 onwards.

If the EMS resource is of type DEFERRED, then configure the generic resource with 'evaluation_type' as during_package_start and proceed with the steps below till step 12.

7.Edit the package configuration file by removing the EMS resource from the package.

8.Validate the changes done by running: cmcheckconf -v-p <pkg_name>

9.Edit the package configuration file to add the generic resource parameters.

10.Validate the changes done by running: cmcheckconf -v-p <pkg_name>

11.Apply the changes by running: cmapplyconf -v-p <pkg_name>

12.Start the package.

13.Create a multi-node package and configure the monitoring of the resource as part of the package via services.

This makes the monitoring scripts highly available, since Serviceguard monitors them and is the recommended approach. See “Launching Monitoring Scripts” (page 390) for launching monitoring scripts for resources of evaluation type before_package_start.

14.Validate the changes done by running: cmcheckconf -v-p <pkg_name>

15.Apply the changes by running: cmapplyconf -v-p <pkg_name>

16.Start the multi-node package.

17.Halt the application package. cmhaltpkg <pkg_name>

18.Edit the package configuration file by removing the EMS resource from the package.

396 Migrating EMS Resources to Generic Resources

Page 396
Image 396
HP Serviceguard manual Migrating EMS Resources to Generic Resources