HP-UX 11i v3 Installation and Update Guide, September 2011

Table 15 Known install and update problems (continued)
Description/actionProblem
The system may fail with a Machine Check Abort (MCA), halt and reboot due to
a very rare condition of the CPU where one processor core (and both of its threads
HP Integrity Superdome 2, BL8x0c
i2, rx2800 i2 – MCA (Machine
in the event that hyperthreading is enabled) locks up and stops executing
instructions. The cause is not defective hardware.
Check Abort) PIRB Timeout or ORB
Timeout
This might occur on HP Integrity Superdome 2 nPartitions and vPartitions running
HP-UX, HP Integrity BL860c i2, BL870c i2, BL890c i2 Blade Servers, and rx2800
i2 Servers running HP-UX.
What to do
This type of MCA is prevented by installing HP-UX patch PHKL_42230, available
at the HP Support Center (http://hp.com/go/hpsc). The final fix kernel change
will be included in a later release of HP-UX 11i v3 (11.31). This patch adds a
single instruction to the purge high-level TLB fault handler code path that prevents
the CPU core from becoming locked ultimately resulting in the Timeout MCA. There
is no adverse affect effect to system performance or operation as a result of this
change. This patch is recommended to be installed at an agreeable time.
When HP SMH is installed, the user hpsmh and group hpsmh are automatically
added to the /etc/passwd file. If you are using LDAP or any other network service
User and group IDs of HP SMH
conflicts with user and group IDs
of LDAP and other network
services
for managing user and group accounts, there is a possibility that the user ID (UID)
and the group ID (GID) of hpsmh are already in use by LDAP-users. The duplication
of user and group IDs results in changes in file ownership. This problem occurs in
HP-UX 11i v3 on Integrity systems.
What to do
As workaround, before installing HP SMH, you must manually add a local hpsmh
user and group using unique UID and GID. First, determine the available reserved
IDs for the group (say, 130) and the user (say, 125). Ensure that these IDs are not
in use by LDAP or other network services. Then, add the group using the following
command:
/usr/sbin/groupadd -g 130 hpsmh
After adding the group, add the user using the following command:
/usr/sbin/useradd -u 125 -g hpsmh -d \
/var/opt/hpsmh -c "System Management Homepage" hpsmh
Note: If you do not manually add the group and user before installing HP SMH,
during installation HP SMH creates the group and user using locally available IDs,
which may already be in use on the network.
During installation, HP WBEM Services creates a user cimsrvr and a group
cimsrvr. If you are using Network Information Services (NIS), Lightweight Directory
User and group IDs of HP WBEM
Services conflict with user and
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
76 Harmless messages and known problems