HP Systems Insight Manager 7.1 Release Notes

2 Important notes
Central Management Server
Use careful planning if you want to deploy new drivers, firmware agents, or other software to the
local CMS because you might receive unexpected results, such as a mandatory reboot of the CMS.
Configure or Repair Agents
Configure or Repair Agents fails on Linux systems if the HP Insight Management WBEM providers
are already installed on the system. HP does not support both WBEM and SNMP (contained in
the Linux support pack deployed by Configure or Repair Agents) on the same system. If the Configure
or Repair Agents operation fails, you can view the HP Smart Update Manager log on the target
system, located in the /var/hp/log/hpsum_execution_log* file and /var/hp/log/
localhost/*.txt files for more details. If the WBEM providers have already been installed,
the localhost\hpsum_detail_log.txt file will show a dependency conflict - hp-health
conflicts with hp-smx.
Data Collection
After discovering MSA2000 systems, Data Collection might fail resulting in minimal information
appearing on the System page and only Discovery/Identification data appearing in Data Collection
report. To resolve this issue, run Data Collection again.
Database credentials
During HP SIM installation, the database credentials must have SQL administrator access with
dbowner rights. After installation, these rights can be reduced.
Environment changes
The mxreconfig command is used to reconfigure HP SIM to accommodate environment changes
such as a CMS hostname change, CMS IP address change, or service credential changes. It also
has a sqlredirect option used to configure HP SIM to point to a different database server and/or
SQL server port number.
Discovering ESXi 4.x and 5.x and above with lockdown enabled in HP
SIM 7.1
When discovering ESXi 4.x and 5.x and above HP WBEM providers must be installed on the
system for DC, hardware status polling, and indications to work.
To discover ESXi 4.x and 5.x and above with lockdown enabled in HP SIM 7.1:
1. Check the option Automatically discover Vmware ESX host server in lockdown enabled mode
in Options→Discovery→Configure Global Settings.
2. Discover the Virtual Center first to which the ESXi Host is registered.
Make sure Virtual Center credentials are properly entered for the Virtual Center and the node
has the subtype set as “Virtual Center”.
If a node is Virtual Center, provide the Virtual Center credentials:
a. From the System Page→Edit System Credentials select all the credential and click the Edit
Credential button. Select Show Advanced Credentials, select the VME tab and provide
the vCenter credentials.
b. The credentials will be set and will trigger a discovery over the node again, which will
identify the node as a “Virtual Center” node.
6 Important notes