HP-UX WBEM DAS Provider release notes (5900-1778, September 2011)

NOTE: Removing old Disk Native Provider.

NOTE: PGC00614: Deleting the provider module... PGC00607: The

provider is deleted successfully.

NOTE: Creating the Disk log database

NOTE: Disk log database setup completed.

NOTE: Registering Storage WBEM Indication Provider schema

NOTE: Registering Storage WBEM Instance Provider schema

NOTE: Registering Storage WBEM Record Log Provider

NOTE: Registering Storage Native Control Provider

NOTE: Registering the Storage WBEM Native Provider.

ERROR: The "configure" script for "WBEMP-Storage.STORAGE-PROV-RUN"

failed (exit code "1"). The script location was

"/var/adm/sw/products/WBEMP-Storage.2/STORAGE-PROV-RUN/configure".

Workaround: Uninstall the currently running DASProvider (where the problem is seen) and

install either B.11.31.1106 or B.11.31.1109.05.01 DAS Provider version.

• When DAS Provider B.11.31.1103.15 or later is installed on legacy Integrity systems, disk_em

and msamon_sas are never launched regardless of the diag mode.

HPUXDiskNativeIndicationProvider always monitors natively the hardware and generates

WBEM events. The reverse wrapper, DAS_WbemWrapperMonitor and/or

MSA_WbemWrapperMonitor, may be launched depending on the connected hardware.

These reverse wrappers convert the WBEM event to the corresponding EMS event.

The introduction of this native support adds to support the following EMS resource paths:

/storage/events/DAS_wrapper_wbem

/storage/events/MSA_wrapper_wbem

On the other hand, as the process for disk_em and msamon_sas are never launched, the

corresponding EMS resource paths are not monitored:

/storage/events/disks/default

/storage/events/enclosures/msamon_sas

The product has the following limitation:

• It is a read-only provider and hence does not allow users to modify, create, or delete instances.