HP Matrix Operating Environment 7.3 Release Notes

support for port groups: Storage controller port load balancing using SPM white paper at http://
www.hp.com/go/matrixoe/docs.
HP 3PAR StoreServe Storage Zero Detect
SPM does not recognize the Zero Detect property of volumes on 3PAR StoreServ Storage. SPM
2.3 (included with Matrix 7.3) cannot create volumes with the Zero Detect property. SPM can
import and use pre-provisioned volumes with the Zero Detect property, but it does not recognize
the property value. SPM will continue to use volumes it has created after an administrator applies
HP 3PAR Zero Detect in the HP 3PAR Management Console, but does not recognize if a volume
has the Zero Detect property value.
3PAR StoreServ Storage Peer Motion has limited support in SPM
If Peer Motion is used on an HP 3PAR StoreServ Storage System that is imported into an SPM
catalog, a number of steps must be performed in order to ensure that SPM and Matrix OE can
properly use the storage affected by Peer Motion. For details on these steps, see the SPM 3PAR
StoreServ Storage Peer Motion Technical White Paper at http://www.hp.com/go/matrixoe/docs.
3PAR StoreServ Storage Peer Persistence is not supported in SPM
SPM 2.3 (provided in Matrix OE 7.3) does not support peer persistence. SPM 2.3 cannot import
volumes that are part of a remote copy group, and cannot import two volumes that share the same
worldwide name. For this reason, SPM cannot be used to manage volumes in a peer persistence
configuration.
Managed node installation
Limitations
Multipath I/O and Emulex FC HBA or Emulex FlexFabric Converged Network Adapter is not
supported on Windows Server 2008 and Windows Server 2008 R2
Using multipath I/O during OS installation is not supported with an Emulex FC HBA or an Emulex
FlexFabric Converged Network Adapter on any Matrix-supported server on Windows Server 2008,
Windows Server 2008 R2 and Windows 2012.
The following suggested actions enable you to install the OS single-path and then modify the
storage definitions to create multiple-path access to the boot volume. After a successful OS
installation, these instructions will define an additional physical path to the boot volume by:
• Modifying the storage definition to add an additional server HBA definition (port)
• Modifying the boot volume definition to add a second physical ‘path’ to its definition.
Suggested action 1
If you are creating a template using Matrix OE infrastructure orchestration designer select Redundant
SAN paths to disk when configuring the boot volume.
Beginning in Matrix OE 7.2, infrastructure orchestration executes steps to work around this issue
by ensuring that the OS is single-path while the OS is being provisioned, and then modifies the
storage definitions to create multipath access to the boot volume when OS provisioning is complete.
Suggested action 2
If you are defining a storage pool entry in Matrix OE logical server management:
1. Define the storage pool entry, adding multiple ports, and marking all non-boot disks as
redundant. Keep the boot volume as a single path.
2. Assign the storage pool entry to a logical server.
3. Activate the logical server.
4. Provision the OS, and install the multipath IO drivers as appropriate.
Managed node installation 45