HP-UX WBEM Fibre Channel (FC) Provider Release Notes (September 2013)

Table 10 Defects fixed in the HP-UX 11i v3 OS (continued)
DescriptionDefect ID
In the previous release, cimprovagt process generated a core during unload of the
HPUXFCIndicationProviderModule.
QXCR1001223185
In the current release, this problem is fixed.
Defects fixed in version B.11.31.1303.05.01
During the unconfiguration of FCProvider, the native library gets deleted. Therefore, configuring
of FCProvider fails.
QXCR1001232692
This issue is fixed in this release.
The following error message is logged in FCProvider log:QXCR1001228957
SFM: ERROR: invalid input syntax for type timestamp with time zone: ""
This issue is fixed in this release.
Known problems, workarounds, and limitations
Following is the known problem tabulated from the current release.
Problem: After the installation of FC Provider, couple of initial events are not generated.
Workaround: After installation run /opt/fcprovider/bin/FC_Provider_Test -a twice.
The following known problems are tabulated from the previous 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
• The FCIndication provider crashes while upgrading from versions earlier than the March 2012
release. This problem does not occur while upgrading from March 2012 release to any later
releases.
• Problem: The events are lost when diagnostic products are upgraded on a DRD cloned disk.
Description: Prior to September 2012 release version of diagnostics product, the postgres
7.4.2 version was supported. However version 8.4.8 is shipped from September 2012 release.
Due to the missing data compatibility between PostgreSQL version 7.4.2 (prior to September
2012) and 8.4.8 (September 2012 release or later) when diagnostics products are upgraded
from prior to September 2012 release to September 2012 web release and later, the postgres
data need to be migrated to 8.4.8 format. Data migration involves backup in 7.4.2 version
using the pg_dumpall and restore in 8.4.8 version using the psql operations. Both of these
operations requires a running postgres service. But in the DRD environment there is a limitation
that no service can be run on the cloned disk when products are either installed or upgraded.
This limits diagnostics product upgrade steps from taking the backup of the postgres 7.4.2
data. As a result, the data such as events and error records is lost during such circumstances.
16 Fibre Channel (FC) provider release notes for September 2013 release