Readme - HP Systems Insight Manager 6.0
-------------------------------------------------------------
When an Onboard Administrator is discovered, the enclosure that it resides in is created. If this enclosure
is daisy chained to other c-class enclosures, then these enclosures are also created. By default, daisy chained
enclosures are displayed as c7000 enclosure models. As a result, when c7000 and c3000 enclosures are
daisy chained, and the Onboard Administrator is discovered, the c3000 Tower Model enclosure is displayed
as a c7000 enclosure. To ensure that the daisy chained enclosures are displayed accurately, you must
discover the Onboard Administrator on each of these enclosures.
-------------------------------------------------------------
To correctly identify the xw25p Blade Workstation, you must install Insight Management Agents 7.4.
-------------------------------------------------------------
To associate the Cisco Gigabit Ethernet Switch Module with the HP BladeSystem enclosure it is inserted in,
you must update the HP Insight Management Agents to 7.3 or later on at least one blade in the enclosure.
-------------------------------------------------------------
If you have licensed a system for HP Insight Control power management and receive the following error
message while attempting to view the last data collection status on the System Page for the system,
Unable to communicate with Management Processor <mpname> in server <servername>
because the Management Processor does not have a serial number and(or) network
address. Please re-identify the Management Processor and try again., then there
might be a problem with duplicate iLOs associated with the system. Use the All Management Processors
view and identify the iLOs associated with the server. There is one iLO with its name being the IP address
of the iLO and another iLO with the serial number of the iLO as its system name. Deleting the iLO with no
IP address recorded resolves the issue.
HP Insight Control virtual machine management
After you have selected the Install Linux PSP or ESX agents and Register VM host options in a Configure
or Repair Agents task for ESX 3.5 U4 or later, the VM-host registration task fails because the system shows
as Not Responding in Vcenter. Vcenter takes about five minutes for a system to reach a Normal status and
therefore fails when Systems Insight Manager tries to register the VM host. Re-run the VM-host registration
task at a later time when the server is in a Normal state in Vcenter.
HP MIBs
The LinkUp and LinkDown traps in IF-MIB.mib are redundant traps; these are also present in rfc1215.mib.
As per the current framework, the redundant traps are not allowed in Systems Insight Manager Traps with
same name.
Change the loading of MIBs. The IF-MIB.mib is loaded first and then the RFC1215.mib. The IF-MIB.mib
will be listed in mibcore.list and rfc1215 in preload.list. By doing this the LinkUp and linkDown
traps from IF-mib.mib will only be registered with Systems Insight Manager and in Options→Events→File
Name. The RFC1215 file will only show four traps Cold Start, Warm Start, Authentication Failure, egp....
HP Smart Update Manager
If you are receiving an HP Smart Update Manager Connection Error or Discovery Failed message in the
StdOut Task Results for Initial ProLiant Support Pack Install, SSH Install, or Configure or Repair Agents, follow
the following troubleshooting tips:
• Ensure your workstation does not have an existing connection to the admdin$ share on the target IP
address. If it does, it prevents HP Smart Update Manager from connecting to the remote server’s share
because Windows only allows one connection from a client to a server’s share. This can be checked
by entering net use at a command prompt. If there is an existing share to the target IP address,
\admin$ share, delete it and try the installation again.
• Ensure that the target IP address server’s admin$ share is accessible. Validate the target server can be
accessed by entering net use x: \\<ip_address_or_dns_name>\admin$ for the target server’s
IP address or DNS name. When the connection is validated, ensure that it is deleted by entering net
use x: /d at command prompt.
20 Issues and suggested actions