HP-UX WBEM RAIDSA Provider release notes (5900-2057, March 2012)

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."

Defects fixed in the B.11.31.1203.04.01 release

The "Recommended Action" notes is not displayed in the /var/opt/resmon/

log/event.log file for all the FC, RAIDSA and SAS events.

QXCR1001152987

This defect is fixed in the current release.

The install logs present under the /var/opt/ directory displays unwanted

messages during cold install for RAIDSA, SAS, DAS and FC providers

QXCR1001133148

This defect is fixed in the current release. The createtable.sh script is

modified to check the cold install and database accordingly.

The RAIDSA event 54 and 55, for removal and insertion of a disk connected

to the machine through a RAID controller in RAID mode is suppressed for 24

hours.

QXCR1001162174

The TC file is now modified to remove suppression of event 54 and 55.

Known problems, workarounds, and 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 dm_raid_adapter is never launched, the corresponding

EMS resource path is not monitored:

/adapters/events/raid_adapter

• 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.

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.