HP Matrix Operating Environment Software User Manual
Page 60
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
It may also be necessary to manually enter proxy WWNs. For more information, see
.
SPM supports FC fabric repair and FC fabric re-configuration where the fabric identify remains
intact
When using the SPM automated zoning capability with HP B-series or Brocade SAN networks,
SPM can recover from fabric repairs and from fabric re-configuration automatically, but only as
long as the fabric’s identity remains intact. Fabric repairs are fabric changes such as switch
replacement and switch firmware upgrades. Re-configuration changes are fabric switch configuration
changes or additional switches to support datacenter growth or additional features. In either case
SPM will handle the change automatically, as long as the fabric’s identify as tracked by Brocade’s
Network Advisor, remains intact.
Any change, regardless if it is a repair or re-configuration, that is severe enough to change the
identity of the fabric as tracked by Brocade Network Advisor will require administrator intervention
on SPM’s part to recover and will not be automatically handled
Importing a large number of volumes is time consuming and may result in failure
Depending on your environment, importing 1,000 or 5,000 or more volumes at the same time
into SPM can cause a service crash which requires a restart of the SPM service. Restrict simultaneous
volume imports into SPM to less than 5,000 for InForm OS 3.1.1 MU1 or later, and to less than
1,000 for all other storage operating systems.
3PAR autonomic groups, peer motion, and virtual domains are not supported in SPM
The following 3PAR features are not supported in this release of SPM. See the HP Storage
Provisioning Manager (SPM) User Guide at
for more information.
•
Autonomic groups
SPM does not support 3PAR autonomic groups (host sets and virtual volume sets). Under certain
conditions, SPM can coexist with autonomic groups, but it does not take advantage of that
functionality. For more information, see
“Working with autonomic groups” (page 72)
•
Virtual domains
SPM does not support 3PAR virtual domains. Using virtual domains on 3PAR storage systems
managed by SPM will likely result in erratic behavior in SPM, particularly during volume
import, volume refresh and goal binding.
•
Peer motion
SPM cannot detect migration of a volume from one array to another using Peer Motion.
Volumes that are migrated from one array to another using Peer Motion will be marked offline
in SPM, and services using such volumes will become nonconformant. In addition, any hosts
that are using such volumes may lose access if the volume moves out of the zone that connects
it to the host.
SPM cannot import or resynchronize P9500 or XP storage array resources if they are locked by
RWC
If resources from a P9500 or XP storage array, including pools and volumes, are locked by the
Remote Web Console (RWC), SPM cannot import or re-sync those resources. (This does not affect
SPM's ability to perform mapping and masking during service activation.)
Suggested action
Ensure that all web browsers running RWC are shut down during import or re-sync operations.
See the
for more information.
60
Troubleshooting