HP Matrix Operating Environment 7.3 Update 1 Release Notes

NOTE: By default, specifying storage volume names when adding a disk to a VM is
restricted to administrators. To enable all users to specify storage volume names when
adding a disk to a VM, change the value of the hpio.properties
user.disk.add.storage.volume.names.restricted properly from true to
false. Setting this property to false also means that the users can specify storage volume
names which are not part of the service template.
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.
For more information about cross-technology logical servers, see the HP Matrix Operating
Environment Recovery Management User Guide at Enterprise Information Library.
Number of networks provisioned to a logical server
The 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 server 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.
23