HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 78 (of 108)
Chapter 15 Serviceguard
October 29, 2013
Note: This force import procedure should only be used when you are certain the disk is not
currently being accessed by another node. If you force import a disk that is already being
accessed on another node, data corruption can result.
Further Problems
In this section are described further uncategorized very well known Serviceguard problems.
• Sendmail version
Some companies such as AT&T install an unsupported version of sendmail. Sendmail hosts
identd, which Serviceguard uses to validate the host from which Serviceguard commands are
run. If the customer uses an unsupported version of sendmail, edit the /etc/inetd.conf file and
modify this hacl-cfg line thus:
hacl-cfg stream tcp nowait root /usr/lbin/cmclconfd cmclconfd -c -i
Then restart inetd:
$ inetd –k ; inetd
• Problem: HP-UX Strong Random Number Generator
Serviceguard A.11.16 and the latest patches for A.11.15 include functionality which uses the HP-
UX Strong Random Number Generator on HP-UX 11i if this is loaded.
Unfortunately some versions of the HP-UX Strong Random Number Generator
prior to version B.11.11.07 have a defective startup script which can
result in the wrong major number for the random number device files
/dev/random and /dev/urandom. This can result in a number of different
symptoms which can be difficult to troubleshoot. Serviceguard commands
can hang, fail or take a very long time to work often with no apparent
errors in syslog.log or other external symptoms.
Any Serviceguard clusters which have the HP-UX Strong Random Number
Generator software loaded should ensure they have version B.11.11.07 or
newer. This can be checked by looking at the version of the KRNG11i
bundle:
# swlist -l bundle | grep KRNG
KRNG11i B.11.11.09 HP-UX 11.11 Strong Random Number Generator
If you have a cluster which is behaving erratically after installing
Serviceguard A.11.16 or the patches shown above and the HP-UX Strong
Random Number Generator is loaded you should check that the /dev/urandom
device file has the correct major number. The driver given by the major
number should be the "rng" driver. This can be verified by checking the
devices files and the kernel major number: