HP Matrix Operating Environment 7.0 Release Notes

Suggested action
Do not change PRM configuration files using the PRM user interface when privilege elevation is
enabled.
Storage Provisioning Manager
Storage Provisioning Manager runs on an x86/x64 Windows CMS.
Limitations
Presenting an in-use storage volume to an unintended consumer may result in data loss
Pay special attention when importing pre-presented volumes into SPM because all storage volumes
imported into SPM are made available to fulfill storage services requested by SPM consumers such
as Matrix Operating Environment. Import only storage volumes intended to fulfill storage requests
serviced by this instance of SPM. If you have multiple instances of SPM (either independent or in
a federated configuration), you may wish to have each instance manage different storage array
pools or completely different arrays.
When importing pre-presented storage volumes, ensure the volume is not already in use. Do not
import volumes that are in use, are intended for use by other systems or services, or that have been
imported into any other instance of SPM.
Storage volumes must be managed by one SPM
Large data center environments may make use of multiple CMS configurations (either independent
or in a federated configuration). Any individual storage volume/LUN should be managed by only
one SPM. This can be done by having different SPM instances on different CMSs manage different
storage array pools, or completely different arrays.
Required version of Brocade Network Advisor and HP B-Series Network Advisor
Brocade Network Advisor 11.1.3 or HP B-Series Network Advisor 11.1.3 must be installed in
order to manage Brocade-based SAN environments.
HP B-Series Network Advisor is available from http://h18006.www1.hp.com/products/
storageworks/dc_fabricmgr/index.html. See the HP Storage Provisioning Manager (SPM) User
Guide at www.hp.com/go/matrixoe/docs for additional details.
SPM cannot support a mixture of SPM-created and administrator-created zones
When using the SPM automated zoning capability with HP B-series or Brocade SAN networks,
storage administrators cannot present storage to the same initiator from two separate arrays if they
have manually created zones via the Brocade Network Advisor that include that initiator.
SPMs managing the same Brocade network must have distinct zones
When using the SPM automated zoning capability with HP B-series or Brocade SAN networks,
environments that make use of multiple CMS configurations (either independent or in a federated
configuration) may manage the same HP B-series or Brocade network. In this situation, however,
the set of initiators managed by each instance of SPM must be distinct, therefore making correlated
zones created and managed by each instance of SPM also distinct.
Non-Brocade SAN environments must have unmanaged networks in SPM
Storage administrators must provide SPM with information regarding SAN connectivity. In addition,
for non-Brocade SAN environments, an unmanaged network must be created to communicate the
SAN configuration to SPM as described in the HP Insight Management Installation and Configuration
Guide at www.hp.com/go/matrixoe/docs.
36 Issues and suggested actions