HP Insight Dynamics 6.2 Release Notes

• For Windows 2003, apply the KB932370 patch. For more information, see http://
support.microsoft.com/kb/932370/.
• For HP-UX 11 v2, apply the PHKL_37803 patch. You can download this patch from http://
www13.itrc.hp.com/service/patch/mainPage.do. After downloading, execute the command
sh PHKL_37803, and install the depot file that is generated.
No patch is necessary for Windows 2008 or HP-UX 11 v3.
This information does not apply to HP-UX 11 v1.
Global Workload Manager
Limitations
HP Integrity Superdome 2 support
The HP Global Workload Manager (gWLM) supports Fair Share Scheduler (FSS), Partition Sets
(PSETS), and HP Integrity Virtual Machines on HP Integrity Superdome 2. Global Workload Manager
does not support nPartitions and vPartitions. Online migration of CPU is also not supported.
HP Insight Orchestration
HP Insight Orchestration runs on an x86/x64 Windows CMS.
Limitations
Number of networks provisioned to a logical server
The Insight Dynamics infrastructure template Designer does not restrict the number of networks that
can be connected to a logical server group. In practice, only four networks can be connected to
virtual logical servers, and 32 networks can be connected to physical logical servers designed to
run on HP c-Class server blades. These practical limits will increase over time as Virtual Connect
and hypervisors are enhanced.
If these limits are exceeded in an infrastructure template, provisioning operations using that template
will fail.
Suggested action
Limit the number of network connections to a logical server group to four for virtual logical servers
and 32 for physical logical servers.
Manually configure the SAN boot path for ProLiant DL/ML servers before provisioning
The job "Deploy ProLiant System Configuration (BL BFS),” contained in the Insight Control Rapid
Deployment software job folder deployed using Insight Orchestration, cannot be used to configure
ProLiant DL/ML target servers. The job configures ProLiant/Integrity BL target servers. If you attempt
to configure ProLiant DL/ML servers using this job, the request will fail.
Suggested action
Manually configure the SAN boot path before you use Insight Orchestration to provision a ProLiant
DL/ML target server on SAN boot LUN, as follows.
1. Create a server deployment job folder that does not contain the "Deploy ProLiant System
Configuration (BL BFS)" job.
2. Change the Boot Controller Order (from ROM-Based Setup Utility) for the ProLiant DL/ML
server to select Fiber Channel port (HBA) as the first in the boot order.
3. Use the HBA vendor's utility to configure the HBA's boot path to boot from the desired SAN
boot LUN.
4. Power off the target server after the Boot Controller Order and the HBA's boot path have been
configured correctly.
18 Issues and suggested actions