HP Insight Cluster Management Utility v7.2 Release Notes

5 Limitations and workarounds
5.1 LVM and Software RAID nonsupport
IMPORTANT: Do not install LVM or Software RAID on the HP Insight CMU compute nodes. LVM
or Software RAID on the compute nodes will cause backup or cloning to fail.
TIP: LVM and Software RAID are supported on the management node.
5.2 HP iLO CM ssh/vsp connections are limited to 15
Each HP iLO CM allows up to 15 concurrent ssh/vsp sessions. To go beyond that limit, close old
connections before starting new connections.
Starting new ssh/vsp connections to HP iLO CM from the HP Insight CMU GUI or cmu_console
tool can be slow, resulting in connection timeout errors. To eliminate these errors, increase the
CMU_CONSOLE_CONNECTION_TIMEOUT value in /opt/cmu/etc/cmuserver.conf.
5.3 Renamed autoinstall logical groups must be manually changed in
/etc/exports
When an existing autoinstall logical group is renamed using the HP Insight CMU GUI, the
corresponding entry in the /etc/exports file is not automatically updated on the management
node. Manually edit the /etc/exports file after renaming the autoinstall logical group.
5.4 RHEL6.x diskless boot failure
RHEL6.x diskless nodes fail to boot when NetworkManager service is enabled in the diskless image.
Disable NetworkManager service on the golden node before creating the diskless image. For
example:
chkconfig --level 345 NetworkManager off
5.5 Diskless unavailable on Ubuntu compute nodes
Ubuntu is supported only on compute nodes. Diskless environments require that the compute nodes
share the operating system on the HP Insight CMU management node.
5.6 Red Hat 5 update 7 and 8 rsync bug impacts diskless
The rsync executable delivered with rh5u7 (package: rsync-3.0.6-4.el5) and rh5u8 does
not work properly with the command rsync -e ssh. This command causes a failure when
creating a diskless logical group. If you are using the GUI, the following message is returned:
Add Logical Group failed: unknown error occurred while executing /opt/cmu/tools/opt/cmu/tools/cmu_dl_register_image
If you are using the CLI command /opt/cmu/bin/cmu_add_logical_group, the following
messages are returned:
building image from golden node with rsync
usage: ssh [-1246AaCfgkMNnqsTtVvXxY] [-b bind_address] [-c cipher_spec]
[-D [bind_address:]port] [-e escape_char] [-F configfile]
[-i identity_file] [-L [bind_address:]port:host:hostport]
[-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
[-R [bind_address:]port:host:hostport] [-S ctl_path]
[-w tunnel:tunnel] [user@]hostname [command]
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(600) [receiver=3.0.6] script reported (7) i.e. rsync reported
non zero exit code, exiting
To work around this error, remove rsync-3.0.6-4.el5 and install a working package. The
rsync package from rh5u5 (rsync-2.6.8-3.1) works correctly.
5.1 LVM and Software RAID nonsupport 15