HP Logical Server Management Best Practices

9
Figure 5: Fabric names in Virtual Connect Enterprise Manager
Matrix is integrated with the bundled HP Storage Provisioning Manager (SPM) solution. In the version 6.3 release,
SPM was aware of SAN fabrics through the specification of SAN IDs (which needed to correlate with the VCM
definitions). With the 7.0 and later releases, SPM is able to automate SAN operations in a Brocade SAN
environment (discovering SAN fabrics for import and performing zoning). Correlation between the SAN fabrics
known to VCM/VCEM and those known to SPM and BNA (the Brocade Network Advisor solution) is done via the
„Connected To‟ WWN associated with each fabric in VCM. To support this correlation of VCM fabrics to those
known to SPM, it is mandatory that the „Connected To‟ WWN associated with the fabric in VCM for a logical server
storage is found in one of the SAN fabrics (networks) imported into SPM, to enable fulfillment of logical server storage
requests from the SPM catalog. More information on SPM is available in later sections of this white paper and a
separate Faster storage provisioning in the HP Matrix Operating Environment - Use of the HP Storage Provisioning
Manager storage catalog with controlled storage operations white paper available at
http://www.hp.com/go/matrixoe/docs.
Figure 6 shows the fabric names in the HP Storage Provisioning Manager in Matrix 6.3 (denoted as SAN IDs). The
fabric names defined in SPM must match the fabric names defined in Virtual Connect Manager (and used by Virtual
Connect Enterprise Manager and Matrix OE). The names need to match exactly for storage requests to be
automatically matched to catalog entries (as part of the Matrix OE integration with SPM capabilities). Starting in
Matrix OE 7.0 (SPM 2.0), SPM no longer uses SAN IDs. Instead, the WWN that the Fabric is connected to must be
defined in one of the networks defined within SPM in order for SPM to find the correct connectivity.