HP-UX WBEM DAS Provider release notes (5900-1805, June 2011)

Table 5 DAS Provider Software Requirement for PA-RISC system (continued)
A.01.00SysMgmtPlus
B.11.31.06.05OnlineDiag
A.04.00.01EMS-Core
NOTE: Fibre-Channel Indication provider monitors DAS hardware indications on HP-UX 11i v2
OS, so Fibre-Channel Indication provider must be installed to monitor DAS indications on HP-UX
11i v2 OS.
Disk Space Requirement
Table 6 lists the disk space requirement for the DAS provider.
Table 6 DAS Provider Disk Space Requirement
Disk Space RequiredProvider
16696 KBDAS Provider (includes CSP and IP Providers)
Defects Fixed in This Version
This section describes WBEM DAS Provider defects fixed in HP-UX 11i v3 OS.
Table 7 Defects Fixed in HP-UX 11i v3 OS
DescriptionDefect ID
Defects Fixed in version B.11.31.0909.01
In the previous release, the getwbemstatus function in the XML page uses the
class HP_DiskDrive to get the consolidated status of the disks, but the consolidated
status is provided by the classHP_DiskCollection.
In the current release, this defect is fixed and the XML page is modified to get the
consolidated status from the class HP_DiskCollection. Appropriate status is
displayed on the SMH page.
QXCR1000896835
In the previous release, a file named diskaldata is created in the root directory
of a system when the DAS™ provider is started. The file size is negligible and users
QXCR1000893566
can ignore the occurrence of the file. This file can be deleted, but the file may
reappear.
In the current release, this defect is fixed and the file diskaldata is not created
in the root directory of the system.
In the previous release, a core file is created randomly in the var/opt/wbem
directory. Occurrence of this file does not affect normal working of the product.
In the current release, this defect is fixed and the core file is not created in the var/
opt/wbem directory.
QXCR1000894271
Defects Fixed in version B.11.31.0909.02
In the previous release, when an application requests thread creation on a system
on which DAS provider is running, the request is not processed if the provider has
QXCR1000938587
created threads beyond the threshold value set on the system. Due to this, warning
messages are logged in the system log file as the DAS provider thread spawns
over a period of time.
In the current release, this defect is fixed and warning messages are not logged in
the system log file as the DAS provider thread does not spawn over a period
of time.
Defects Fixed in This Version 7