HP-UX ProviderSvcsBase Release Notes (5900-2226, March 2012 web release)

Fibre-Channel Provider, HP-UX WBEM Direct Attached Storage Provider (DASProvider) must be
installed together to maintain compatibility among the diagnostic products.
On web:
September 2011 web release onwards, all the HP-UX 11i v3 version of WBEM
providers and Diagnostics products, are available for download on the WBEM
Management bundle for HP-UX 11i v3 bundle page at https://
h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?
productNumber=WBEMMgmtBundle.
NOTE: HP's WBEM Management bundle is released only on the web. All the
products from the WBEM Management bundle must be installed together. This is
due to product interdependency. These products might not work if they are installed
individually.
Hardware requirements
Currently, this product is supported on all HP Integrity systems.
Software requirements and OS support
The provider requires certain software products to be installed on the managed system.
Table 2 (page 5) lists the software product requirement for the provider.
Table 2 ProviderSvcsBase software requirement
Product versionProduct
B.11.31Event Manager (EVM)
C.07.06.03 March 2012 web release or laterSysFaultMgmt
A.02.09.04 or laterWBEM Services
A.05.00.09.01, March 2011 release or laterSysMgmtPlus
NOTE: On legacy Integrity systems running HP-UX 11i v3, both dialogd and oserrlogd
co-exist from March 2009. The OnlineDiag product, if installed, must be March 2009 or later
version.
Disk space requirement
Table 3 (page 5) lists the amount of disk space required to install theProviderSvcsBase
bundle products:
Table 3 Disk space requirement
Disk spaceProduct
85 MBProviderSvcsBase products with the Health
Test sub-product.
15 MBHealth Test sub-product only
Known problems, workarounds and limitations
Following known problem is applicable for the current release:
Problem: If the permission for /tmp and /var/tmp directories are changed during HP-UX
installation phase, the sfmdb user cannot write temporary files. As a result, WBEM events are not
logged at the following locations: EventArchive, syslog, email and /var/opt/sfm/log/
event.log.
Known problems, workarounds and limitations 5