HP-UX WBEM Services Release Notes (B8465-90045, March 2011)

IMPORTANT: This issue is only applicable for HP WBEM Services A.02.07 and later versions.
What is the workaround?
For systems using LDAP or other network services, before installing HP WBEM Services, you must
manually add a local cimsrvr user and group using a unique UID and GID. You must first
determine the available reserved IDs for the group (for example 130) and for the user (for example,
125) ensuring that these IDs are not in use by LDAP or other network services. Run the following
command to add the group:
/usr/sbin/groupadd -g 130 cimsrvr
After creating the group, run the following command to add the user:
/usr/sbin/useradd -u 125 -g cimsrvr -d /var/opt/wbem -c "WBEM Services"
cimsrvr
NOTE: If you do not manually add the group and the user before installing HP WBEM Services,
the installation scripts add a group and user using locally available IDs, returned by useradd(1M)
and groupadd(1M), which may already be in use on the network.
For systems using NIS the problem is encountered when HP WBEM Services is installed as part of
a custom bundle that requires a system reboot or if NIS is stopped for any other reason whilst the
HP WBEM Services installation is performed. In the former case, this is because the HP WBEM
Services configure phase (when the user and group are created) is run before NIS is up and running
after a system reboot. To avoid this problem on systems that have NIS configured, install the HP
WBEM Services upgrade on its own or as part of a custom bundle that does not contain updates
that require a system reboot.
This problem does not affect new installations where the cimsrvr user and group is present before
NIS, LDAP or other network services are configured; or minor upgrades of HP WBEM Services
where the cimsrvr user and group is present from an earlier HP WBEM Services A.02.07 or
later installation.
Failure to configure WBEM-CORE fileset (Updating from A.02.00.08 and earlier to A.02.05 and
later)
What is the problem?
Use of the usePAMAuthentication configuration option will result in failure to configure the
WBEM-CORE fileset during an update of the WBEM Services. The usePAMAuthentication
configuration option has been obsoleted and is no longer supported.
What is the workaround or available patch?
You must do the following:
1. Before updating the WBEM Services, check if the usePAMAuthentication configuration
option is present in the following WBEM configuration files:
/var/opt/wbem/cimserver_current.conf
/var/opt/wbem/cimserver_planned.conf
2. If the usePAMAuthentication configuration option is present, then run the following command
before updating the WBEM Services product.
# cimconfig -u usePAMAuthentication -p
cimserver becomes unstable due to swverify command
What is the Problem?
Running the swverify –x fix=true WBEMServices command makes the cimserver unstable.
Subsequent cimserver start up fails.
20 HP WBEM Services Version A.02.09.06 Release Notes