HP Matrix Operating Environment 7.1 Release Notes

Suggested action
Upgrade to Hyper-V R2. In R2, Microsoft corrected the problem so that the activation of a virtual
machine logical server configured to be created on a cluster disk or a cluster shared volume lists
all Hyper-V hosts in the cluster on the target screen.
High Availability Hyper-V virtual machine with RDM disk can be activated only on cluster disk
owner
When an HA Hyper-V logical server with a SAN-based storage pool entry (RDM disk) is activated,
only the RDM disk host owner is displayed as a target on which to activate the logical server. It is
not possible to enable HA for a VM with an RDM disk if the Hyper-V host that is hosting the VM
is not the owner of the RDM disk.
Some Virtual Connect profile capabilities are not supported by logical server management
Importing a server with Virtual Connect that implements the following features is not supported by
Matrix OE logical server management. If the Virtual Connect profile is using these features, the
error “The Server Profile cannot be imported because it contains the following capabilities
unsupported by Logical Servers:” is displayed.
Extended VLAN Multiple networks in the server profile have more than 28 Virtual Local Area
Networks (VLANs)
EXTENDEDFC Server profile has two or more FC Connections using the same connection
bay (with the same connectionBay attribute value), which identifies a server
profile created for an HP Integrity BL860c)
EXTENDEDFCOE Server profile has more than one Fibre Channel over Ethernet (FCoE)
connection associated with the same interconnect bay (IO bay)
ISCSI Server profile has at least one iSCSI connection
NAG Server profile has an associated Network Access Group
LUNs are not detected after activating a logical server using logical server management on an HP
Integrity Virtual Machine host
A logical server, when activated directly on an HP Integrity Virtual Machine host using LSM, fails
to detect the LUNs assigned to it at the virtual machine EFI prompt. Due to this limitation, the logical
server will not boot up the operating system automatically even if it is assigned with a LUN that is
pre-provisioned with an operating system.
Suggested action
At the Integrity Virtual Machine EFI prompt, execute the following commands to see LUN mappings.
When these steps are complete, the user can select the required LUN from the displayed device
list to boot up or to install the operating system.
1. Check configurable controllers using the drvcfg command.
Shell> drvcfg
Configurable Components
Drv[2C] Ctrl[29] Lang[eng]
2. Enumerate all SCSI amd FC LUNs using drvcfg -s <drvnum> <ctrlnum>. (drvnum
and ctrlnum are displayed as part of step 1.) Press Y for confirmation on enumerating both
SCSI and FC LUNs.
Shell> drvcfg -s 2C 29
Set Configuration Options
Drv[2C] Ctrl[29] Lang[eng]
HP AVIO Stor Driver Configuration
==================================
Warning: Enumerating all SCSI or FC LUNs increases initialization times.
Enumerate all SCSI LUNs (Y/N)? [current setting: Y]: Y
34 Issues and suggested actions