HP-UX WBEM DAS Provider release notes (5900-2516, March 2013)

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 DAS provider version B.11.31.1106 or B.11.31.1109.05.01.

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

and msamon_sas are not launched regardless of the diag mode.

HPUXDiskNativeIndicationProvider always natively monitors 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 not launched, the

corresponding EMS resource paths are not monitored:

/storage/events/disks/default

/storage/events/enclosures/msamon_sas

• Problem: There are no email alerts for the subscription.

Description: User do not receive email alerts for existing and new email subscriptions due to

database authorization issue in September 2011 release.

Workaround: There is no workaround for this problem.

• Problem: The events are lost when diagnostic products are upgraded on a DRD cloned disk.

Description: Prior to September 2012 release version of diagnostics product, the postgres

7.4.2 version was supported. However version 8.4.8 is shipped from September 2012 release.

Due to the missing data compatibility between PostgreSQL version 7.4.2 (prior to September

2012) and 8.4.8 (September 2012 release or later) when diagnostics products are upgraded

from prior to September 2012 release to September 2012 web release and later, the postgres

data need to be migrated to 8.4.8 format. Data migration involves backup in 7.4.2 version

using the pg_dumpall and restore in 8.4.8 version using the psql operations. Both of these

operations requires a running postgres service. But in the DRD environment there is a limitation

that no service can be run on the cloned disk when products are either installed or upgraded.

This limits diagnostics product upgrade steps from taking the backup of the postgres 7.4.2

data. As a result, the data such as events and error records is lost during such circumstances.

Workaround: You can select any of the following two alternatives:

1. To install the product on the DRD cloned disk as a normal upgrade scenario. The scenario

will be same as fresh installation and user may refer to event.log for historical event data.

2. To have a seamless migration of the data from postgres 7.4.2 version. In this case, the

user is required to perform the manual steps listed in the Installation scenarios of Postgres

8.4.8 guide at www.hp.com/go/hpux-diagnostics-sfm-docs.

The product has the following limitation:

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

• For disks having capacity more than 2TB (terrabyte), the “Capacity” field in the disk instance

output contains value as “Not Available”.