HP-UX WBEM RAIDSA Provider Release Notes (766964-001, March 2014)
Table 19 B.11.31.1004 (continued)
In the current release, the log configuration file for RAIDSA provider available
at: /var/opt/raidsaprovider/conf is termed as
RAIDSALoggerConfig.xml.
In the previous release, Memory leak encountered due to ComponentData
indication properties of HPUXRAIDSAIndicationProviderModule.
QXCR1001016011
In the current release, this defect is fixed.
Defects fixes in B.11.31.1003 release
Table 20 B.11.31.1003
DescriptionDefect ID
The /tmp/raidsa_log file gets created because the ioctl() call fails and
returns EINVAL error value.
QXCR1000989338
This defect is fixed in the current release, and the log file is created under the
path /var/opt/raidsaprovider/log with the filename as raidsa.log.
HP-UX 11i v2 OS
Defects fixes in B.11.23.1012 release
Table 21 B.11.23.1012
DescriptionDefect ID
In the previous version, property details of RAIDSA HBA is not displayed on
HP SMH (System Management Homepage) web page under the Storage
subsystem.
QXCR1001039271
In the current release, this defect is fixed. Property details of RAIDSA HBA is
displayed on HP SMH (System Management Homepage) web page under the
Storage subsystem.
Known problems, workaround, and limitations
Known problems
The following known problems are tabulated from multiple releases.
• 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:
The events are lost when diagnostic products are upgraded on a DRD cloned disk.
Description:
14 RAIDSA provider release notes for March 2014 release