HP System Management Homepage 3.2.1 Release Notes

3 Issues and workarounds
HP SMH undergoes rigorous testing before releasing any given version of the product. From HP test activities
to date, the following items have been uncovered that you should keep in mind. Please also refer to the HP
System Management Homepage Installation Guide and HP System Management Homepage Online Help
for known issues.
HP SMH 3.2.1 release for HP-UX 11.31/ HP SMH 3.1.2 release for HP-UX
11.23
• If a serviceguard cluster is down, fsweb does not create a perfect cluster volume group.
fsweb creates and distributes a volume group, but it fails to mark the volume group as cluster aware.
As a result, it appears that the creating cluster volume group operation has failed instead a new volume
group is created. Ideally, the fsweb should detect whether serviceguard cluster is down, and if so, let
you know that a volume group will not be marked as cluster aware and question you whether you still
want to proceed and mark the volume group as cluster aware through the serviceguard tools. So, fsweb
can still successfully create a cluster volume group, and you can mark it as a cluster aware through
serviceguard. This is the known behavior of fsweb in 11.23.
To resolve this issue, change the volume group cluster-aware either by bringing the serviceguard cluster
up and running vgchange command or explicitly configure the volume group as a cluster volume
group in the serviceguard cluster configuration after creating the cluster volume group in fsweb.
• In HP SMH, select the Home -> System Configuration -> Disks and File Systems path and then
select the Disk tab. HP SMH shows a used VxVM disk as unused. However, in an HP-UX login session,
the vxdisk list command displays the disk as an used VxVM disk.
As a workaround, run the vxddladm set namingscheme=osn mode=legacy command before
you run the fsweb or disklist command. This command switches the view to the legacy mode and
has a dependency on the disklist command which causes the issue. After executing this command,
the VxVM used disk is marked as a used disk.
• Users not defined on the local system, but defined only on an Active Directory, cannot login to HP SMH
in an environment where Kerberos authentication via PAM on HP-UX is implemented. This problem
occurs in HP-UX 11i v2 and 11i v3 on Integrity systems.
A 64 bit libnss.winbind.so is necessary for the authentication. The 64-bit shared library,
/usr/lib/hpux64/libnss_winbind.so.1 that is required for SMH authentication is currently
not available.
This problem currently does not have any known workaround. The problem is planned to be resolved
in a future release of HP SMH.
• When HP SMH is installed, the user hpsmh and group hpsmh is automatically added to the
/etc/passwd file. If you are using LDAP or any other network service to manage user and group
accounts, there might be a possibility that the user ID (UID) and the group ID (GID) is already in use
by the LDAP users, which can be confusing. The problem occurs in HP-UX 11i v3 on Integrity systems.
To overcome this, add a local hpsmh user and group using unique UID and GID (IDs not in use by
LDAP or the other network services) manually before installing the HP SMH.
Complete the following steps to manually add the local hpsmh user and group IDs:
1. Determine the available reserved IDs for the group (for example, 130) and the user (for example,
125).
2. Add the group using the command /usr/sbin/groupadd -g 130 hpsmh.
3. Add the user using the command /usr/sbin/useradd -u 125 -g hpsmh
-d/var/opt/hpsmh \ -c "System Management Homepage" hpsmh.
HP SMH 3.2.1 release for HP-UX 11.31/ HP SMH 3.1.2 release for HP-UX 11.23 15