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)
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
HPUXRAIDSANativeIndicationProviderModule are unique, which gets
logged in the evweb database.
Defects fixed in the B.11.31.1106 release
In the previous release, on legacy integrity and BL870c i2 platforms, when
excessive errors are generated from a faulty component, the RAIDSAPROVDB
QXCR1001083290
database connection with the
HPUXRAIDSANativeIndicationProviderModule 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
HPUXRAIDSANativeIndicationProviderModule is not supported on
legacy Integrity systems.
QXCR1001048147
In the current release, the
HPUXRAIDSANativeIndicationProviderModule 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)
Defects fixed in This version 9