HP Systems Insight Manager 7.0 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. The option to specify a non-standard port (other than 1433) does not
work correctly. Therefore, the sqlredirect option should only be used if the database is on the
standard port 1433.
ESXi Hosts
To discover ESXi 4.x and 5.x hosts with lockdown enabled:
1. In HP SIM, click Options→Discovery.
2. Click Configure general settings.
3. Select Automatically discover VMWare ESX host server in lockdown enabled mode.
If an ESXi 4.x host is managed in lockdown mode in VMware vCenter, then these hosts cannot be
monitored and managed by Insight Control components by providing the root credentials.
A user with named, remmgr, must be created on each of the ESXi 4.x hosts that need to be managed
by vCenter 4.x in lockdown enabled mode. The username, remmgr, should have root equivalent
privileges. This user credentials (remmgr and its password) should be used as to discover and
identify the host in HP SIM.
-------------------------------------------------------------
If you install HP agents separately from ESXi; the ESXi server must be re-identified to prevent WBEM
subscriptions from failing as the system gets identified completely on re-identification.
6 Important notes