HP-UX WBEM RAIDSA Provider Release Notes (766964-001, March 2014)

Table 15 B.11.31.1106 (continued)
Table 16 QXCR1001066416 (continued)
Earlier Severity LevelCurrent Severity Level
Subsystem
GroupOperationalStatus
OK(2) and
Completed(17).
Has the lowest
severity level.
Has the highest severity
level.
• OK(2)
• Completed(17)
In the previous release, cimprovagt program generated a core during unload
of the provider. The program was terminated with signal 11, segmentation
fault.
QXCR1001051369
In the current release, this problem is fixed.
Defects fixes in B.11.31.1103 release
Table 17 B.11.31.1103
DescriptionDefect ID
In the previous release, on BL870c i2 platform, the RAIDSA disk test command:QXCR1001058688
#/opt/raidsaprovider/lib/RAID_Provider_Test -d fails to generate
events for all subsequent RAIDSA disks available on the system if the first
instance of the disk is not supported by the
HPUXRAIDSANativeIndicationProviderModule.
This defect is fixed in the current release on BL870c i2 platform. The disk test
is enhanced to send events for all the monitored paths even if the first instance
of the disk is not supported by the
HPUXRAIDSANativeIndicationProviderModule.
In the previous release, the HPUXRAIDSAIndicationProviderModule
displays incorrect severity value after registering with EMS sub-system on HP-UX
QXCR1001048021
11i v3 OS. The moncheck utility output, used to view the status of OnlineDiag
monitors, displays incorrect severity value.
This defect is fixed in the current release. The
HPUXRAIDSAIndicationProviderModule displays appropriate severity
value after registering with EMS sub-system on HP-UX 11i v3 OS.
In the previous release on HP-UX 11i v3 OS, enumeration of classes available
in RAIDSA Instance provider and RAIDSA Consolidated Status provider fails
for a user with non-root privileges.
QXCR1001068706
This defect is fixed in the current release. Enumeration of classes available in
RAIDSA Instance provider and RAIDSA Consolidated Status provider is successful
even for a normal user.
In the previous release on BL870c i2 platform, when the cimserver /
HPUXRAIDSANativeIndicationProviderModule is restarted, the
QXCR1001078598
Indication Identifier index is reset. If the evweb current database already has
events with the same event number or Indication Identifier index, such duplicate
events are not logged in the evweb database. When events with the same IDs
are reported frequently, the events will be logged in the /var/opt/sfm/log/
event.log file and the syslog file.
In the current release on BL870c i2 platform, when the cimserver /
HPUXRAIDSANativeIndicationProviderModule is restarted, the
Indication Identifier is concatenated with a timestamp along with the event
number and Index. With this modification, the Indication Identifier can never
be duplicated and all the event IDs generated by the
12 RAIDSA provider release notes for March 2014 release