Beruflich Dokumente
Kultur Dokumente
1 Release Notes
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products
and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. UNIX is a registered
trademark of The Open Group.
Acknowledgments
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open
Group UNIX 95 branded products.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Table of Contents 3
4
1 Enhancements
Please read this document in its entirety to understand what you should expect from this software.
These release notes describe HP Insight Control software.
6 Enhancements
2 System requirements, installation, upgrades, configuration,
and licensing
For system requirements see the HP Insight Software 6.1 Support Matrix. For installation instructions,
see the HP Insight Software 6.1 Installation and Configuration Guide.
Post-installation configuration
See the HP Insight Software 6.1 Installation and Configuration Guide for configuration steps to
perform after installation.
Upgrade paths
For instructions on upgrading from older versions to the latest version, see the HP Insight Software
6.1 Installation and Configuration Guide.
Post-installation configuration 7
8
3 Issues and suggested actions
Issues and limitations of this release are listed below, organized by HP Insight Control product
or functional area. The following categories are used. If a product area has no limitations or
issues, that category will not appear.
Limitations Limitations of the implemented functions and features of this release
Major issues Issues that may significantly affect functionality and usability in this release
Minor issues Issues that may be noticeable but do not have a significant impact on
functionality or usability
HP Insight Control
Minor issues
Product name changes
With Version 6.0, HP introduced significant name changes to the components of HP Insight
Control. HP Insight Rapid Deployment software (RDP) is now called HP Insight Control server
deployment. HP Insight Virtual Machine Manager software (VMM) is now called HP Insight
Control virtual machine management. HP Insight Server Migration software for ProLiant (SMP)
is now called HP Insight Control server migration. HP Insight Power Manager software (IPM)
is now called HP Insight Control power management. HP Insight Performance Manager module
(PMP) is now called HP Insight Control performance management. We complete this name
change in Version 6.1.
An occasional error displays “Communication with SIM has been lost" while monitoring
a number of servers
While monitoring a number of servers, the application fails to respond by displaying
“Communication with SIM has been lost" message.
Suggested action Perform the following steps:
1. Close the error page.
2. Re-login to the Systems Insight Manager and continue.
Vulnerability and Patch Manager software being phased out of HP Insight Control
HP is phasing out the HP Insight Vulnerability and Patch Manager software (VPM) from HP
Insight Control. Technical support will be offered based on the Technical Support and Upgrade
offerings for HP Insight Control sold through November 2009. HP Insight Control licenses include
one year of Technical Support and Update, which you can upgrade to 3, 4, or 5 years. Depending
on the purchase date of HP Insight Control licenses and technical support extension, support
for Vulnerability and Patch Manager functionality will end no later than November 2012.
Starting with the Insight software DVD 6.0, Vulnerability and Patch Manager will no longer be
available.
Suggested action Existing users of the vulnerability and patch management capabilities can
upgrade to Vulnerability and Patch Manager 6.0 by downloading the software from Software
depot at http://software.hp.com.
HP Insight Control 9
HP Insight Control power management
Limitations
Unsupported feature
HP Integrity BL860c i2, BL870c i2, and BL890c i2 servers do not support the Power Level and
Power Switch (on/off) functionalities; therefore, the resulting Data Centre Power Control (DCPC)
operations report that the capability is not supported.
Rules take longer to start when invoked or simulated against a large number of systems
When a Data Center Power Control rule is invoked or simulated against a large number of
systems (hundreds or thousands), it can take several minutes for the rule preview page to appear
or the rule simulation to start running. During this delay, the browser will show a progress
indicator. If the browser session that invoked the rule or simulated rule is closed, or navigated
away from the progress indicator page, the rule or simulated rule will not proceed.
During this rule start-up delay period, if any browser session attempts to enter Data Center
Power Control pages, those browser sessions will also show a progress indicator until the preview
processing is complete. This is true even if the original browser session is closed or navigated
away from the progress indicator page.
If many user sessions are active on the CMS at the same time, the rule start-up delay period can
be proportionally longer.
Inappropriate description message displays below the Group Cap table for “Discovery Error”
When power data is not collected for a server in an enclosure and when you change the power
cap, the Group Cap table shows “Discovery Error,” and the description under the Group Cap
table may not specify the correct message.
Suggested action Perform one of the following steps:
• Collect power data for the servers and then set or change the power cap settings for the
enclosure.
• Click Refresh Bays to collect power data for all servers in the enclosure
Configured alert value results in one value more than the entered input value
While configuring alerts, if you select BTU/hr for Warning Threshold and enter a value, the Task
Results page displays the New Threshold value as one value more than the entered input value.
For a server, iLO expects the threshold value to be set in Watts. When you enter the value in
BTU/hr, power management converts it to Watts (where 1 watt equals 3.413 BTU/hr). This results
in a float value, which iLO does not accept. Power management then rounds the value after
conversion resulting in increment or decrement of the entered input value by one.
Major issues
Data Center Power Control Rule Preview page hangs when you execute a rule without user
permission
When you do not have the user permissions of Data Center Power Control and execute a rule,
the rule hangs in the Rule Preview page. The Invoke Rules tab will show the rule as running,
but the Systems Insight Manager Task Results page will not show an entry for the rule. If you
click Stop on the Invoke Rules tab, you will see the following exception:
org.apache.jasper.JasperException: java.lang.NumberFormatException: For
input string: “null”. You will be unable to use the affected rule until
the Systems Insight Manager service is restarted.
Suggested action Perform the following:
• Obtain the appropriate user permission to execute the rules. You will need to test the rules
once, at least in the simulation mode, prior to actual use.
• When a rule hangs, restart Systems Insight Manager service to free the rule for use. If you
cannot restart Systems Insight Manager service, then, as a temporary solution, make a copy
of the affected rule and execute the copied version of the rule.
Scheduled tasks for Power Regulator or Power Cap are not listed under “Scheduled tasks” list or
not editable
If you have scheduled a Power Regulator or Power Cap task using Power Management 6.0 or
earlier and when you upgrade your system to Power Management 6.1, the task may not be listed
in the Scheduled tasks list or may result in failure when you try to edit the task.
Suggested action Delete the existing power regulator or power cap task and schedule new
task.
Power management cannot communicate with iLO management processors when the iLO credentials
contain the double-quote (") character
Because of limitations in the management protocol provided by the iLO management processor
interface, you cannot specify a double-quote character in the credentials. If the credentials include
the double-quote character, even if the credentials are correctly configured in Systems Insight
Manager, Insight Control power management will report the power management authorization
failure:
Insight Control power management was unable to log in the system`s
management processor due to incorrect or missing credentials. Please
ensure correct credentials are entered on the Insight Control power
management options page.
The Data Center Power Control shutdown rule stays indefinitely in a “running state”
The Data Center Power Control shutdown rule uses a single-system-aware (SSA) tool to execute
shutdown on selected targets. In executing an SSA tool, the HP Systems Insight Manager
distributed task facility (DTF) of the central management server (CMS) uses secure shell (SSH)
to send one or more files to the target system, which then executes the tool. If the target node is
unresponsive, the SSA tool waits indefinitely on a return status from the target node and hence
shutdown rule is left in a running state indefinitely.
Suggested action Stop the Data Center Power Control shutdown rule using the Data Center
Power Control Stop button or cancel the rule as a Systems Insight Manager task.
Shutdown rule may fail when applied on a large set of Windows-based managed nodes
The Data Center Power Control shutdown rule fails to complete successfully when applied on
a large set of Windows-based managed nodes. The shutdown action is executed using Systems
Insight Manager v6.x SSA tool via a Windows OS command line. A single command line is
executed with arguments that contain the Windows shutdowncommand followed by the
hostnames of the large set of Windows-based managed node. This command-line operation
causes a command-line buffer overflow and results in a failure to shutdown all the Windows-based
managed nodes.
Suggested action A single Data Center Power Control rule acting upon a large set of Windows
managed nodes causes command buffer overflow, so the number of target nodes will need to
be carefully calculated and a single Data Center Power Control rule will need to be split into
multiple steps or rules each acting upon a subset of target nodes until all the target nodes are
exhausted.
Insight Control power management fails while changing the power cap value
When a server reports an anomalously high maximum-power value, power management will
accept a system power cap value that the server subsequently rejects when Insight Control power
management attempts to apply the power cap.
Suggested action Perform the following steps:
1. Verify that the firmware version of the server is up to date.
2. Reset the server.
3. Using the iLO power settings page, verify that the server reports a plausible maximum
power value. For a blade server, this value should be less than the initial power-on request
value.
Minor issues
“Trap Details” table contains blank or zero value for SNMP threshold event for iLO 3 based
DL G7 servers
For iLO 3–based DL G7 servers such as ProLiant DL360 G7, DL380 G7, and DL385 G7 Server
Blades, the “Trap Details” table for alert event displays blank or zero value.
Suggested action No action is required.
Inconsistent system details displayed when multiple browser instances opened sharing the
same user session
If you have multiple browser windows open to view different systems and these browser instances
share the same browser session, inconsistent system details data can be displayed inside some
of the browser instances.
Unable to shut down the hosts and guests in either a forced or graceful manner
VMware ESXi 3.5 and ESXi 4.0 versions do not support SSH capability. A manual shutdown of
the guests or hosts will be required until HP more fully integrates power management with
VMware vCenter.
Suggested action The hosts and guests can be powered on and off until HP more fully integrates
power management with VMware vCenter.
Inconsistent system details displayed when multiple browser instances opened sharing the
same user session
If you have multiple browser windows open to view different systems and these browser instances
share the same browser session, inconsistent system details data can be displayed inside some
of the browser instances.
Suggested action Refresh the browser window that displays inconsistent system details. Start
and sign in to HP Systems Insight Manager using separate browser session:
• For Microsoft Internet Explorer 8 (IE8), click File->New Session to start the new browser
session.
• For Mozilla Firefox, start multiple browser sessions using separate profiles. For example,
firefox.exe -no-remote -P profile_name.
Unable to display graphs and reports when the time difference between the CMS and
managed node is more than 24 hours
HP Insight Control power management cannot display power/utilization/temperature graphs
if the time difference between the CMS and managed node is more than 24 hours, although data
collection status reports as successful. Power data is stored based on the managed node's time.
Suggested action If the date and time on the CMS and managed nodes are inconsistent with
their respective time zones, then change the date and time to be consistent with their respective
time zones.
Setting power cap for an enclosure group or a group of servers and enclosures in
percentage may result in incorrect distribution
When you select an enclosure group or a group of servers and enclosures to set power cap in
percentage, it may result in an incorrect distribution of power.
Suggested action For an enclosure group or a group of servers and enclosures, set the power
cap in Watts.
HP Systems Insight Manager may not recognize the installed HP Insight Control power
management that followed immediately after an uninstallation of power management.
When uninstalling HP Insight Control power management from HP-UX, HP Systems Insight
Manager will be restarted. If power management is installed immediately after it is uninstalled
and before Systems Insight Manager has fully restarted, power management will be installed
successfully but Systems Insight Manager may not recognize that power management is installed.
Major issues
Insight Control virtual machine management returns duplicated Hyper-V host entries with the same
serial number after an upgrade from 3.7.1 to 6.x
After an upgrade from 3.7.1 to 6.x, virtual machine management returns duplicated Hyper-V
host entries with the same serial number for Hyper-V host with multiple NICs.
Suggested action Unregister all of the IP addresses with the same serial number using vmm
cli and re-register the Hyper-v host in virtual machine management 6.x to receive accurate data
from the Hyper-V host.
Hyper-V R2 hosts may hang while under going rapid VM creation/deletion operations
Microsoft Hyper-V host servers might hang in situations where many simultaneous virtual
machine operations (such as creating, deleting, or activating virtual machines) are taking place.
• The source server is running without Windows Server 2003 Service Pack 1 or later.
• The source server does not have the Microsoft Storport Storage Driver from Knowledge
Base (KB) article 932755 installed.
• The migration is performed to a destination server connected to a SAN Logical Unit Number
(LUN)
• The SAN fabric zone has multiple paths between the destination server and the SAN storage.
Suggested action Microsoft Corporation has supplied a patch that corrects the problem. At the
following website download the patch and install it on your Hyper-V hosts: http://
support.microsoft.com/kb/980081
Minor issues
If the IP address of the host changes, virtual machine management cannot manage the
host
If the IP address of a hypervisor host is changed, virtual machine management will not be able
to manage the host.
Suggested action HP recommends that you unregister the hypervisor host before changing
the IP address. After the IP address is changed, identify the host in HP Systems Insight Manager
and register with virtual machine management. If the IP address is changed without unregistering
the host, unregister the host with the old IP address using the vmcli tool and register with the
new IP address.
vCenter server host associations may be incorrect if the host is present in multiple vCenter
servers
vCenter server host associations may be incorrect if the host is present in multiple vCenter servers.
Suggested action Ensure that the host is managed in only one vCenter server by removing it
from all other vCenter servers. Run the Identify Systems task against each vCenter server in HP
Systems Insight Manager to refresh the associations.
Deprecated feature
The Options→Performance Management→Hardware Specifications menu has been removed
in the 6.1 version.
Major issues
Network, Storage, and Host Bus Subsystems display “0” value for status counters in the Offline
Analysis page
Offline Analysis fetches performance and configuration data of the servers from the database to
play back and to monitor the server’s continuous performance. In Offline Analysis, Network,
Storage, and host bus subsystem counters display a “0” value in the status table and in the status
tab, although the online analysis page shows values and the data is available in the database.
Minor issues
Counters are not displaying for some PCI devices
For some PCI devices, performance counters are not displayed.
For some NIC adapters (for example, NC7782 and NC7170) all network ports are shown
as disabled or not configured in Online Analysis
Network ports can sometimes appear as disabled or not configured in online analysis for some
network adapters when they are configured in a server running Microsoft Hyper-V technology
in Windows or configured as a bridge in Linux.
Details of NIC teaming type and the involved ports are not displayed
Network adapters can be configured with different NIC teaming types to handle fail over. Also,
the IP Address will be configured on the Teamed NIC. Performance management does not display
the configured NIC teaming type, involved ports, or details in the inventory tab of the online
analysis page.
External storage information is not detailed in the generated system summary report
Performance management does not display the external storage configuration information in
the System Summary Report.
NIC subsystem’s major or minor performance state (icon) is not reflected against the server
or in the PF column
When network components are stressed on the server, the Network Subsystem/NIC Adapter/NIC
Port components show minor or major state icons on the Online Analysis page. The consolidated
status, however, is not propagated to the Server Model status in Online Analysis or to the PF
(Performance State) icon in the Systems Insight Manager All Systems page.
Status does not change in Server Configuration Tree when you click on Previous/Next
bottleneck buttons in the Offline Analysis page
System subsystem components status and counter values are logged to the database for playback.
When you click on the Previous and Next buttons in a bottleneck condition, the Offline Analysis
page shows the data when the system was in a Minor or a Major State. The status icon and
Analysis explanation message the display correct information in the status tab with values listed
on Counter table; however, the normal status icon is displayed in the Server Configuration tree
for the same component.
Monitoring Administration page hangs after monitoring of the servers is started for the first
time
Occasionally, the Monitoring Administration page hangs after monitoring of the servers is started
for the first time.
Suggested action Restart HP Systems Insight Manager service.
Windows Server 2008 x64 and x86 migrations are not supported from Windows 2003 application
station or CMS
A Windows Server 2008 and x86 migration will be blocked on Step 1 of the server migration
wizard if attempted from a Windows 2003 application station or CMS. If the source agent was
launched from the Windows 2003 application station, the source will be locked to that specific
application station and must be stopped.
Suggested action Install HP Insight Control server migration application on a Windows Server
2008 x32 or x64 system to run Windows Server 2008 x64 server migrations. Stop the agent on the
Windows Server 2008 x64 source server manually by running stopHPSMPAgent.cmd tool on
the source desktop, before attempting a migration from another application station.
Migrating Windows Server 2003 to a destination server with a Brocade HBA requires a minimum
of Service Pack 2
Migration of Windows Server 2003 to a destination server with a Brocade HBA needs a minimum
of Service Pack 2, because the Brocade HBA drivers require a minimum of Service Pack 2 for
Windows 2003.
Suggested action Install Service Pack 2 for Windows Server 2003 on the source server before
attempting the migration.
X2P migrations of Windows Server 2003 need a minimum of Service Pack 1 on the source server
X2P migrations of Windows Server 2003 need a minimum of Service Pack 1 on the source server.
Major issues
Migrating a Linux source server with terabyte storage fails when the migration is initiated
Migrating a Linux source server with terabyte storage fails with the
java.lang.OutOfMemoryError: Java heap space error in the <SMP Install folder>/
log/hpsmpsvc.log file.
Suggested action Increase the heap size on the source server, by performing the following
steps:
1. Increase the initial memory by changing the following parameters in /tmp/smpagent/
bin/hpvmmsmp.conf:
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=<initmemory>
2. Start the SMP source agent with the following commands:
cd /tmp/smpagent/bin ./startHPSMPCnt.sh
./startHPSMPCnt.sh
After a Virtual to ProLiant (V2P) or Physical to ProLiant (P2P) migration, a destination server connected
to the Storage Area Network (SAN) may display a blue screen after booting
When performing a Windows 2003 Virtual to ProLiant (V2P) or Physical to ProLiant (P2P)
migration, a destination server connected to the Storage Area Network (SAN) may display a
blue screen after booting. This can occur when the destination server is connected to a SAN LUN
and either of the following conditions is met: The source does not have Service Pack 1 or later
or the source does not have Storport driver. Causes include the following:
• The source server is running without Windows Server 2003 Service Pack 1 or later.
• The source server does not have the Microsoft Storport Storage Driver from Knowledge
Base (KB) article 932755 installed.
• The migration is performed to a destination server connected to a SAN Logical Unit Number
(LUN)
• The SAN fabric zone has multiple paths between the destination server and the SAN storage.
Suggested action Download and install Windows Server 2003 Service Pack 1 or later and the
Storport Driver.After downloading and installing Windows Server 2003 Service Pack 1 or
Windows Server 2003 Service Pack 2 and the Microsoft Storport Storage Driver from Knowledge
Base (KB) 932755 article, perform the V2P or P2P migration.
Minor issues
Migration Wizard does not proceed to Step 2 automatically when the source agent
deployment succeeds in Step 1
When source agent deployment succeeds in Step 1 of the migration wizard, the migration wizard
does not proceed to Step 2 automatically; instead Step 1 reappears with out any warning or error
message.
Suggested action Press "Next" button without choosing the "Deploy server migration Source
Agent" option in Step 1 of the migration wizard.
[Boot CD] Screen is not loaded when booting with unsupported server
Booting an unsupported server with HP Insight Control server migration ProLiant Boot CD
might not bring up the boot CD application wizard. Instead, a shell prompt will be displayed.
Suggested action If the destination server boots to a shell prompt with the HP Insight Control
server migration ProLiant Boot CD, check the Insight Control support matrix to verify the server
support.
The destination server might display a blank screen when booting to the server migration
Boot CD
The destination server might display a blank screen when booting to the HP Insight Control
server migration Boot CD if the server has more than 64 GB of RAM.
Suggested action Perform the following steps:
1. At the boot menu, press ESC to enter text mode.
2. At the text mode boot prompt, enter sos mem=4G.
3. Press Enter.
Destination server does not boot when automatic booting option was chosen during X2P
migrations
During X2P migrations, if the automatic booting option was chosen during the "Identify
Destination Server" step of the Migration Wizard and if the destination server does not boot,
then either of the following scenarios might occur:
• Automatic booting fails with the error “Could not get timely response from iLO. Please try
again or use manual Boot option.” in the Migration Wizard.
• Automatic booting continues for over 40 minutes without any error messages displayed in
the Migration Wizard.
Suggested action Reset the iLO on the destination server and then reboot the destination server.
Launching server Migration tools from HP Systems Insight Manager requires the source
server to be discovered with an IP address and operating system type
Launching server migration from Systems Insight Manager requires that the source server be
discovered with an IP address and operating-system type.
Suggested action In Systems Insight Manager, verify that the source server is properly discovered
with an IP address and operating system type.
Mouse does not work on the destination server's iLO after a Linux X2P migration
Mouse does not work on the destination server's iLO after an X2P migration when “High
Performance Mouse” is enabled in iLO settings.
Suggested action To resolve this issue, disable the “High Performance Mouse” in iLO settings.
Major issues
Patch required to register Integrity VM hosts running Integrity VM 4.1 or higher and
11.31 HA-OE or DC-OE
The Insight Managed System Setup Wizard fails to register Integrity VM hosts running Integrity
VM 4.1 or higher and either the 11.31 High Availability Operating Environment (HA-OE) or the
11.31 Data Center Operating Environment (DC-OE).
Suggested action Apply the patch PHSS_40784 to the HP-UX 11i v3 Integrity VM host. The
patch is needed on systems where Serviceguard is installed, but the systems are not actively in
a Serviceguard cluster. Serviceguard is included with the HP-UX 11i v3 HA-OE and DC-OE.
You can download this patch from http://www13.itrc.hp.com/service/patch/mainPage.do.
Minor issues
Insight Managed System Setup Wizard fails to install the version 4.1 HP Integrity VM
provider on VM guest systems
The Insight Managed System Setup Wizard attempts to install the version 4.1 HP Integrity VM
provider on VM guest systems running on an HP Integrity VM host whose version is greater
than 4.1. When the VM provider version on a VM guest is lower than the HP Integrity VM version
on the host, the managed system setup wizard will try to update the VM provider on the VM
guest.
There are two scenarios in which the VM provider will fail to install on the VM guest:
• If the Integrity VM version on the VM host is manually updated with a version greater than
4.1 and the VM provider on the VM guest is not updated, the managed system setup wizard
will try to update the VM provider on the VM guest with the 4.1 version regardless of the
version already running on the VM guest. This does not cause any failures other than the
managed system setup wizard attempting to install the VM provider each time you try to
configure Insight Dynamics features on that VM guest system.
• If the Integrity VM version on the VM host is manually updated with a version greater than
4.1 (for example, 4.3) and the VM provider on the VM guest is also updated with a version
greater than 4.1 (for example, 4.2) but less than the version of the Integrity VM host, then
the managed system setup wizard will try to install the VM provider version 4.1 on the VM
guest. The install will fail because there is a higher version of the VM provider already
installed and running on the VM guest. This failure can be safely ignored.
Suggested action Manually update the VM provider on the VM guest system to match the
Integrity VM version on the VM host. After this is done, the managed system setup wizard will
not attempt to install the VM provider on the VM guest again.
Contacting HP 23
Warranty information
HP will replace defective delivery media for a period of 90 days from the date of purchase. This
warranty applies to all HP Insight Control Management, HP Systems Insight Manager, and
ProLiant Essentials products.
HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources:
• In the United States, see the HP U.S. service locator website at
http://www.hp.com/service_locator
• In other locations, see the Contact HP worldwide website at
http://welcome.hp.com/country/us/en/wwcontact.html
Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation,
send a message to:
docsfeedback@hp.com
Include the document title and manufacturing part number in your message. All submissions
become the property of HP.
Security bulletin and alert policy for non-HP owned software components
Open source software (such as OpenSSL) or third-party software (such as Java) are sometimes
included in HP products. HP discloses that the non-HP owned software components listed in
the Insight software end user license agreement (EULA) are included with Insight software. The
EULA is included with the HP Insight Software Installer on Insight software DVD #1.
HP addresses security bulletins for the software components listed in the EULA with the same
level of support afforded HP products. HP is committed to reducing security defects and helping
you mitigate the risks associated with security defects when they do occur.
When a security defect is found, HP has a well defined process that culminates with the
publication of a security bulletin. The security bulletin provides you with a high level description
of the problem and explains how to mitigate the security defect.
Related information 25