HP-UX WBEM DAS Provider Release Notes (5900-1602, April 2011)

NOTE: The DiagProdCollection mega bundle includes DAS provider, ProviderSvcsBase, and
other dependent products listed in the table Table 4 (page 6). In this mega bundle, a version lock
is implemented between ProviderSvcsBase (Product name ProviderSvcsCore), SysFaultMgmt, WBEM
Services, and OnlineDiag starting from B.11.31.0903 release. The version lock ensures that if
ProviderSvcsBase product is selected for installation, other products (of versions listed in table
Table 4 (page 6)) are pulled in for installation.
For more information about DiagProdCollection mega bundle, see
https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?
productNumber=DiagProdCollection.
NOTE:
Table 5 DAS Provider Software Requirement for PA-RISC system
Product VersionProduct
A.02.09WBEM Services
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.
Defects Fixed in This Version 7