HP-UX WBEM Fibre Channel Provider release notes (5900-2053, March 2012)

Table 9 Defects fixed in the HP-UX 11i v3 OS (continued)
DescriptionDefect ID
This defect is fixed in the current release.
Defects fixed in B.11.31.1203 release
When a provider is disabled, the failure messages are logged in syslog. This is because, the
time taken by the provider registration/reply with monitor exceeds the time limit set for the
cimserver shutdown.
QXCR1001030689
This defect is fixed in this release. Timeout is set for each monitor request/reply calls and
provider shutdown failure messages are not seen in syslog.
Some of the FCD and FCLP event fields in /var/opt/resmon/log/event.log from CED
database are displayed as NA.
QXCR1001146566
This defect is fixed in the current release.
The Provider Data Sheets (PDS) is no longer shipped as part of the depot. The latest PDS is
available at http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?
QXCR1001087417
lang=en&cc=us&taskId=101&prodClassId=10008&contentType=SupportManual&
docIndexId=64255&prodTypeId=18964&prodSeriesId=4183083
The system crashes during the FC provider upgradation.QXCR1001163320
This defect is fixed in the current release.
The system crashes while registering and unregistering the provider along with the event
generation in process.
QXCR1001164894
This defect is fixed in the current release.
The install logs present under the /var/opt/ directory displays unwanted messages during
cold install for RAIDSA, SAS, DAS, and FC providers
QXCR1001133148
This defect is fixed in the current release. The createtable.sh script is modified to check
the cold install and database accordingly.
Known problems, workarounds and limitations
The following known problems are for the current release:
When FC provider B.11.31.1103.14 or later is installed on legacy Integrity systems,
dm_ql_adapter and dm_fclp_adapter are never launched regardless of the diag mode.
HPUXFCNativeIndicationProvider always monitors natively the hardware and generates WBEM
events. The reverse wrapper, FC_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 paths:
/adapters/events/ql_wrapper_wbem
/adapters/events/fclp_wrapper_wbem
On the other hand, as the process for dm_ql_adapter and dm_fclp_adapter are never
launched, the corresponding EMS resource paths are not monitored:
/adapters/events/ql_adapter
/adapters/events/fclp_adapter
Related documentation
Table 7 lists the available documentation for the WBEM providers:
Known problems, workarounds and limitations 13