HP-UX WBEM SAS Provider release notes (5900-1781, September 2011)

Table 7 Defects Fixed in the HP-UX 11i v3 OS (continued)
DescriptionDefect ID
Table 8 (continued)
Earlier Severity LevelCurrent Severity Level
Subsystem
GroupOperationalStatus
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)
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 Fixed in B.11.31.1109 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."
Known Problems, Workarounds, Limitations
The following known problem is for the current release:
• Problem: No e-mail alerts for the subscription.
Description: Users will not receive e-mail alerts for existing and new e-mail subscriptions due
to database authorization issue in September 2011 release.
Workaround: There is no workaround for this problem.
Following are the limitation of the SAS provider:
• SAS is a read-only provider, and hence does not allow users to modify, create, or delete
instances.
• When SAS Provider B.11.31.1106 or later is installed on legacy Integrity systems,
dm_sas_adapter is never launched regardless of the diag mode.
HPUXSASNativeIndicationProviderModule always monitors natively the hardware and generates
WBEM events. The reverse wrapper, sas_Wbemwrapper, may be launched depending on
the connected hardware. This reverse wrapper converts the WBEM event to the corresponding
EMS event.
The introduction of this native support adds to support the following EMS resource path:
/adapters/events/sas_wrapper_wbem
On the other hand, as the process for disk_em and msamon_sas are never launched, the
corresponding EMS resource paths are not monitored:
/adapters/events/sas_adapter
Known Problems, Workarounds, Limitations 9