HP-UX 11i v3 Installation and Update Guide, March 2012

Table 15 Known install and update problems (continued)
Description/actionProblem
group IDs of NIS, LDAP, and other
network services
Access Protocol (LDAP), or any other network service for managing user and group
accounts, there is a possibility that the user ID (UID) and the group ID (GID) created
for HP WBEM Services are already in use by other users. The duplication of user
and group IDs results in a change in file ownership and can stop applications
working correctly.
This issue is only applicable for HP WBEM Services A.02.07 and later versions.
What to do
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 "WBEMServices" 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 while 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
are present before NIS, LDAP, or other network services are configured; or minor
upgrades of HP WBEM Services where the cimsrvr user and group are present
from an installation of HP WBEM versions earlier than version A.02.07.
If you have installed HP-UX Security Containment Extensions (ContainmentExt
bundle) version B.11.31.01 (which includes the CompartmentLogin and
HP-UX Security Containment
Extensions version B.11.31.01
might produce unexpected
behaviors and swverify errors
ContainmentWiz products) from the HP-UX 11i v3 March 2009, September
2009, or March 2010 OE media, you might experience unexpected behaviors
while using HP-UX Compartment Login and HP-UX Containment Wizard.
In addition, when you update the OE with ContainmentExt B.11.31.01 to a
newer OE version, you might find swverify errors that indicate
ContainmentExt, CompartmentLogin, and/or ContainmentWiz are not
found on the system.
What to do
Update the product bundle to version B.11.31.01.01 or later, which can be
obtained from http://software.hp.com, or from the HP-UX 11i v3 September 2010
OE media. Then you can install or update to your target HP-UX 11i v3 OE media.
New installation of a P700m controller is not recommended on HP-UX 11i v3
releases prior to March 2010. HP-UX 11i v3 Releases prior to March 2010 might
Issues with HP Smart Array P700m
RAID controllers
not guarantee that P700m Device Special Files (DSFs) are persistent between
releases. This can cause data on arrays to become unavailable after you upgrade
to the March 2010 (or later) release of HP-UX 11i v3.
What to do
76 Harmless messages and known problems