HP Systems Insight Manager 7.3 Release Notes

2 Important notes
Central Management Server
Do careful planning to deploy new drivers, firmware agents, or other software to the local CMS
to avoid unexpected results, such as a mandatory restart of the CMS.
HP Systems Insight Manager
Includes the following supports:
SNMPv3 INFORM support
Use SIM Engine ID - 0x8000000b0448502d53494d to send SNMPv3 INFORMs to SIM.
NOTE: It is mandatory to specify the Engine ID to discover HP P6000 Command View and HP
P6000 Performance Advisor devices through SNMPv3. Also, you must enter the security name,
security level, authorization, or privilege fields to receive the SNMPv3 traps from these devices.
Engine ID of HP P6000 Command View is constant and is set to 0x800000e80450363030304356.
Engine ID of HP P6000 Performance Advisor is constant and is set to
0x800000e80450363030305041.
SNMP traps
SIM introduces a custom defined community string, which applies to all the SNMPv3 traps. These
community strings are forwarded as traps in v1 format using AEH (Automatic Event Handling).
Under globalsettingsupd.tpl(/config) file, snmpv3_trap_forward_community defines
a custom community for all SNMPv3 trap forwards instead of the default public community string.
Community string is retained for SNMPv1 and forwarded for SNMPv2 traps. Set this field through
the Global Settings user interface on the debug page.
SNMP pass-thru
SNMP pass-thru discovery of a ProLiant Gen 8 server through HP iLO 4 does not work as in the
previous Generations. An other way to achieve this functionality is to install HP ProLiant Agentless
Management Service on the server and select Agentless Management in HP iLO 4 Management
page. The Agentless Management discovers and associates the complete server details with the
server node.
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 Σ log into 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 are already installed, then the localhost\hpsum_detail_log.txt
file shows a dependency conflict hp-health conflicts with hp-smx.
6 Important notes