HP-UX WBEM RAIDSA Provider release notes (5900-1785, September 2011)

Table 7 Defects Fixed in the HP-UX 11i v3 OS (continued)

In the previous release, the RAIDSAProvider test binary was available in

/opt/raidsaprovider/lib directory.

QXCR1001087415

In the current release, the RAIDSAProvider test binary has been moved to

/opt/raidsaprovider/bin directory.

In the previous release, the HPUXRAIDSAIndicationProviderModule

data had junk values at the end in evweb o/p under "Error Details/Component

Data."

QXCR1001053727

This defect is fixed in the current release. Void Pointer is passed to the EMS

API which fills the "Error Details/Component Data."

Known Problems, Workarounds, Limitations

The following known problems are for the current release:

• When RAIDSA Provider B.11.31.1106 or later is installed on legacy Integrity systems,

dm_raid_adapter is never launched regardless of the diag mode.

HPUXRAIDSAIndicationProviderModule always monitors natively the hardware and generates

WBEM events. The reverse wrapper, RAID_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 path:

/adapters/events/raid_wbem_wrapper

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

corresponding EMS resource path are not monitored:

/adapters/events/raid_adapter

• Problem: No e-mail alerts for the subscription.

Description: Users will not receive e-mail alerts for existing and new e-mail subscriptions due

to database authorization issue in September 2011 release.

Workaround: There is no workaround for this problem.

Following is the limitation of the RAIDSA provider:

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