HP-UX WBEM RAIDSA Provider release notes (5900-2478, September 2012 web release)

Table 7 Defects fixed in the HP-UX 11i v3 OS (continued)
This issue is fixed in this release.
Defects fixed in version B.11.31.1209.08.01
Bay and enclosure values are incorrectly displayed for RAIDSAProvider. Bay
value is displayed as enclosure value and vice versa.
QXCR1001206587
This issue is fixed in this release. The Bay and enclosure values are correctly
displayed.
During multiple system reboot, past provider events get reported for RAIDSA
provider.
QXCR1001198841
This issue is fixed in this release. When the past provider events get reported,
the following warning message is seen in the provider log:
WARNING! Started processing old osel log files. Old events may get reported.
You can safely ignore this message.
When the RAIDSA provider having large number of records in the database
is upgraded, the provider upgrade fails.
QXCR1001200700
This issue is fixed in this release.
Defects fixed in version B.11.31.1209.10.02
When the first node of the hostname is changed to a name that has more than
8 characters, the RAIDSAProvider fails to report the events.
QXCR1001221295
This issue is fixed in this release. The events get generated even after changing
the first node of system name to more than 8 characters.
The event suppression in HPUXRAIDSANativeIndicationProvider is not
getting reset after the system reboot.
QXCR1001230102
This issue is fixed in this release.
In the previous release, cimprovagt process generated a core during unload
of the HPUXRAIDSAIndicationProviderModule.
QXCR1001223185
In the current release, this problem is fixed.
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.
Known problems, workarounds, and limitations 11