HP-UX WBEM SAS Provider Release Notes (766963-001, March 2014)

Defect fixes in B.11.31.1109 release
Table 14 B.11.31.1109
DescriptionDefect ID
In the previous release, core file generated by cimprovagt, program
terminated with signal 11, resulting in segmentation fault.
QXCR1001051369
This issue has been fixed in this release.
In the previous release, the HPUXSASIndicationProviderModule data
had junk values at the end in evweb o/p under "Error Details/Component
Data".
QXCR1001053727
This defect is fixed in the current release. Void Pointer is passed to the EMS
API which fills the "Error Details/Component Data".
Defect fixes in B.11.31.1103 release
Table 15 B.11.31.1103
DescriptionDefect ID
In the previous release, on BL870c i2 platform, the SAS disk test command:QXCR1001058688
#/opt/sas/provider/bin/SAS_Provider_Test -d fails to generate
events for all SAS disks available on the system if the first instance of the disk
is not supported by the HPUXSASNativeIndicationProviderModule.
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
HPUXSASNativeIndicationProviderModule.
In the previous release, the HPUXSASIndicationProviderModule
displays incorrect severity value after registering with EMS sub-system on
QXCR1001048021
HP-UX 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
HPUXSASIndicationProviderModule 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 SAS Instance provider and SAS 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 SAS Instance provider and SAS Consolidated Status provider is successful
even for a normal user.
In the previous release on the BL870c i2 platform, when the cimserver
/ HPUXSASNativeIndicationProviderModule 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
same event 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 the BL870c i2 platform, when the cimserver /
NativeFCIndicationProvider 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
HPUXSASNativeIndicationProviderModule are unique, which gets
logged in the evweb database.
10 SAS provider release notes for March 2014 release