HP Matrix Operating Environment 7.0 Release Notes

Limitations
Cross-technology logical servers are not supported by infrastructure orchestration
Cross-technology logical servers are not supported by Matrix OE infrastructure orchestration. Only
logical servers created or imported in Matrix OE logical server management, using Create→Logical
Server or Tools→Logical Servers→Import, can be moved from physical to virtual or virtual to
physical. A logical server created in infrastructure orchestration (by deploying a service template)
cannot be managed as a cross-technology logical server. For example, if a physical logical server
is created in infrastructure orchestration, it cannot be moved to a virtual machine using logical
server management. Similarly, if a virtual logical server is created in infrastructure orchestration,
it cannot be moved to a server with Virtual Connect using logical server management.
Number of networks provisioned to a logical server
The Matrix OE infrastructure orchestration 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 128 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 128 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 infrastructure 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 infrastructure 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 Fibre 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.
Required HBA firmware and OS drivers to access multi-initiator N-Port ID Virtualization (NPIV) data
disks
The HP blade multi-initiator NPIV feature allows you to configure multiple WWNs for a single HBA
connected with a Virtual Connect Fibre Channel module. Although Matrix OE automates the
configuration, certain versions of HBA firmware and drivers are required to access multi-initiator
NPIV data disks configured for any target BL server.
Suggested action
The HBA firmware and drivers shown for the following operating systems are required to support
multi-initiator NPIV data disks.
Infrastructure orchestration 17