HP-UX WBEM DAS Provider release notes (5900-1805, June 2011)

Table 7 Defects Fixed in HP-UX 11i v3 OS (continued)
DescriptionDefect ID
In the previous release, the HPUXStorageNativeProviderModule leaks memory,
on legacy Integrity and BL870c i2 platforms, when the module receives an evm
notification about the IO subsystem status change.
QXCR1001075851
This defect is fixed in the current release.
Defects Fixed in version B.11.31.1103.15
In the previous release, after reinserting an internal disk , the CIMUtil does not
show the disk details.
QXCR1001103562
This defect is fixed in the current release. The details of the reinserted disk are
displayed correctly.
In the previous release, event numbers 7 and 8 were supported by the
HPUXStorageNativeIndicationProviderModule on legacy Integrity and
BL870c i2 platforms.
QXCR1001088668
In the current release, event numbers 7 and 8 are no longer supported by the
HPUXStorageNativeIndicationProviderModule on legacy Integrity and
BL870c i2 platforms. For information about the events, see http://
bizsupport1.austin.hp.com/bizsupport/TechSupport/SupportTaskIndex.jsp?lang=en&
cc=us&taskId=110&prodTypeId=18964&prodSeriesId=4183083
In the previous release, on legacy integrity and BL870c i2 platforms, when
excessive errors are generated from a faulty component, the DISKPROVDB database
QXCR1001083290
connection with the HPUXStorageNativeIndicationProviderModule exceeds
the threshold limit. This potentially leads to core dump.
In the current release, the defect is fixed and excessive errors generated from a
faulty component are handled appropriately.
In the previous release, the HPUXStorageNativeIndicationProviderModule
is not supported on legacy Integrity systems.
QXCR1001048147
In the current release, the HPUXStorageNativeIndicationProviderModule
is supported on legacy Integrity systems. The monitors disk_em and msamon_sas
no longer generate events on legacy Integrity systems.
The consolidated status provider displays the overall status of the IO subsystem
based on the GroupOperationalStatus property severity level. The severity
QXCR1001066416
levels associated for the GroupOperationalStatus property values during the
previous release and the current release are tabulated below.
Table 8
Earlier Severity LevelCurrent Severity Level
Subsystem
GroupOperationalStatus
Has higher severity
level than the states
Has less severity level than the
states Unknown(0) and No
Contact(12).
• Other(1)
• Starting(8)
Unknown(0) and No
Contact(12).
• Stopping(9)
• In Service(11)
• Dormant(15)
• Power Mode(18)
Has higher severity
level than the states
Has less severity level than the
states OK(2) and
Completed(17).
• Unknown(0)
• No Contact(12)
OK(2) and
Completed(17).
Has the lowest
severity level.
Has the highest severity level.
• OK(2)
• Completed(17)
Defects Fixed in This Version 11