HP Insight Control for Linux 6.0 Installation Guide

9.1.11 Reinitializing Systems Insight Manager requires you to reinstall Insight Control
for Linux
If you reinitialize Systems Insight Manager by running the mxinitconfig –r command, and
then run the mxinitconfig –a command, you must reinstall Insight Control for Linux.
Corrective action: Use the installation procedure in to re-run the install.sh installation script
and reinstall Insight Control for Linux. It is not necessary to uninstall Insight Control for Linux
first.
9.1.12 MP password length issue can cause bare metal discovery to fail
If the management processor password has fewer than eight characters, the bare metal discovery
post processing task fails during the Finalize IC-Linux Discovery operation with the
following error message:
Unable to add new user account.
Attempting to modify password for user.
Password modification failed.
Unable to add or update user account on management processor.
Corrective action: Verify that the default global management processor password has eight or
more characters, which is required by the management processor.
If the password you specified has fewer than eight characters, you can either change the setting
on the iLO to accept passwords with fewer than eight characters or use the
Configure→Management Processor→Credentials to configure a new global password of at
least eight characters.
9.2 Upgrades
9.2.1 Linux OS RPM dependencies are missing on SLES 11 CMS
On a CMS with a SLES 11 OS, you might see the following Linux OS RPM dependency errors
when you upgrade to the new release:
An RPM dependency is missing: apache2-mod_php5
An RPM dependency is missing: libmm14
An RPM dependency is missing: php5
Install error: 10_mgmt_preinstall.sh exited with error code 128
Please view /opt/hp/icelx/logs/install_log for details
This dependency error occurs because the version of Nagios that is integrated with the new
release of Insight Control for Linux uses PHP instead of HTML.
Corrective action: Install the missing Linux OS RPMs on your CMS and rerun the install.sh
script.
66 Troubleshooting