README - HP Systems Insight Manager 5.3 with Update 1
4. Specify how to save data by selecting either:
• Overwrite existing data set (for detailed analysis.) Provides a network snapshot at a certain time
• Append new data set (for historical trend analysis.) Provides trend and usage analysis
5. Click Run Now.
-------------------------------------------------------------
Systems with a dual-port Emulex 1050C HBA card appear in HP SIM as two single-port HBAs. This behavior
is expected because the Emulex 1050DC card is actually two single-port HBAs on one physical card, and
each has its own SCSI controller.
-------------------------------------------------------------
BC1000 blades might appear with an Unknown or Unmanaged status if the CMS is being used as the WMI
Mapper proxy. To correct this problem, enter the WBEM credentials for the CMS in the Global Protocol
Settings page, or edit the system protocol settings for the CMS on the System Protocol Settings page.
Run identification again on the CMS, and then run identification on the blades. See the
HP Systems Insight
Manager Technical Reference Guide
for setting protocol settings and running identification.
-------------------------------------------------------------
HP SIM now supports HP ProLiant Lights-Out 100 Remote Management enabled G3 servers. HP ProLiant
Lights-Out 100 Remote Management enabled G2 servers and earlier are not supported.
Initial ProLiant Support Pack Install
-------------------------------------------------------------
The target status shows failed and there is no output in STDOUT: The credentials supplied are wrong for at
least one of the target systems, causing the task to terminate immediately. The log displayed in the Task
Results for that system shows Could not log in to host with given credentials. The Task
Results for all other systems show a Failed status but no other log information.
-------------------------------------------------------------
The target status shows “Dependency Failure”
No components were installed on the target because there is a component in the ProLiant Support Pack
whose installation requires another component to be installed. Copy the files under
SIMInstallationDirectory\hpsum to the HP Version Control Repository Manager repository directory.
Execute hpsum.exe and start the installation on the target system. The same dependency failure should
occur, but will provide additional details on the nature of the missing dependencies.
-------------------------------------------------------------
If the message stating Discovery Failed with message 113 is observed while running the Initial
ProLiant Support Pack Install task, you must stop the daemon named daemon347.exe running on the target
system. After stopping the daemon, rerun the Initial ProLiant Support Pack Install.
-------------------------------------------------------------
The Initial ProLiant Support Pack Install process hangs on 0% status if the Install and initialize SSH (Secure
Shell) and Reboot systems if necessary after successful install options are both selected.
-------------------------------------------------------------
HP recommends that you do not use the Initial ProLiant Support Pack Install Force downgrade or re-install
the same version option because selecting this option makes the target system NIC to go down.
-------------------------------------------------------------
The Initial ProLiant Support Pack Install process completes quickly, but the task results still show Running. This
is because the Initial ProLiant Support Pack Install portion of the task completes normally. However, the task
has a 10 minute delay to accommodate a system reboot between the installation of the ProLiant Support
Pack and OpenSSH. You might need to perform a manual reboot of the HP SIM system for the task status
to show as complete.
Initial ProLiant Support Pack Install 29