HP-UX WBEM SAS Provider release notes (5900-2319, September 2012)

Table 7 Defects fixed in the HP-UX 11i v3 OS (continued)

DescriptionDefect ID

This issue is fixed in this release.

During multiple system reboot, past provider events get reported for SAS provider.QXCR1001198841

This issue is fixed in this release. When the past provider events get reported, the

following warning message is seen in the provider log:

WARNING! Started processing old osel log files. Old events may get reported.

You can safely ignore this message.

Known problems, workarounds, and limitations

There are no known problems and workarounds in the current release.

Following is 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 dm_sas_adapter is never launched, the corresponding

EMS resource path is not monitored:

/adapters/events/sas_adapter

• Problem: When the first node of the hostname is changed to a name that has more than 8

characters, the SAS provider fails to report the events.

Workaround: To ensure SAS provider works as expected, change the first node of the hostname

to a name that has less than 8 characters.