WBEM Services Release Notes (5900-1625, April 2011)

cimservermain, and cimserverd. The cimserverd process is a daemon process that monitors
cimserver to ensure it remains available.
WARNING! HP recommends not to disable cimserver at startup. Doing so, will impact other
HP products such as; iCOD/iCAP, HP SIM, VSE, and System Fault Management, as these HP
solutions depend on HP WBEM Services (cimserver) to be running.
Removing HP WBEM Services
Before removing the software, back up any files that you want to retain, such as the repository,
log files, configuration files, and certificate files. If these files are removed or overwritten during
the re-installation, you cannot restore them.
To remove HP WBEM Services, run the following HP-UX command:
# swremove WBEMServices
When there are providers in your environment that have a dependency on the file sets of HP WBEM
Services, then this command results in an error. In such cases, run the following command to remove
HP WBEM Services:
swremove -x enforce_dependencies=false WBEMServices
Patches and fixes in this version
This section describes the known problems, required patches, and fixes for this release of HP
WBEM Services.
Required and recommended patches
Currently, there are no patches required for HP WBEM Services Version A.02.09.08 for HP-UX
11i v2 and HP-UX 11i v3.
Fixes in this release
Unless listed in the Known Problems and workarounds section, all known problems of previous
versions of HP WBEM Services have been fixed in this version.
Table 5 describes the defects fixed in HP WBEM Services Version A.02.09.xx.
Table 5 Defects fixed in HP WBEM Services Version A.02.09.xx
ResolutionDescriptionIdentifier
Defects fixed in A.02.09.08
This defect is fixed in the current release.
The cimauth command and the internal
WBEM data structures are modified to
ensure that the namespace case sensitive
error does not occur.
According to the DMTF standards, the WBEM
namespaces are not case sensitive, but the
cimauth command processes namespaces
as case sensitive.
QXCR1001089629
This defect is fixed in the current release.
A mutex has been added to ensure that
the race condition does not occur.
The StorageNative Provider module
hangs when it is continuously enabled and
disabled for one process, while
EnumerateInstances is running for
StorageNative Provider in another
process. There is a race condition during the
provider shutdown.
QXCR1001103470
Patches and fixes in this version 17