Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
Technical white paper | Faster storage provisioning in the HP Matrix Operating Environment
or manually. Or the WWNs can be allocated in advance and the SPM storage catalog populated with volumes already
presented to those initiator WWNs, in which case the Matrix OE “SAN Pre-Populated Catalog Storage Entry” wil use
those WWNs.
This flexibility enables Matrix OE and the SPM to work effectively within a wide range of customer environments. Some
storage administrators may disal ow any change to host mode or LUN presentation. Others may choose to have certain
arrays able to support automated changes to the host mode and LUN presentation, when the requestor has suitable
permissions. Others may take advantage of additional automated features such as on-demand storage provisioning
discussed in an earlier section. It is not necessary to make one choice for the environment; some storage requests might
use pre-provisioned volumes while others may use on-demand provisioned volumes. More information is provided in the
SPM storage template overview section, as SPM storage templates are the means by which a storage architect defines such
policies.
SAN zoning is another aspect which may differ among environments. Some customers may find LUN presentation offers
them suitable protection, and they choose not to zone their SAN fabrics. Those using zoning would be doing WWN-based
zoning in a Virtual Connect environment. They may be creating a separate zone set for each initiator-target pair, or creating
a zone set for each initiator or server where a server may have multiple initiator WWNs which communicate with multiple
storage targets, providing redundant paths to the storage. The WWN management and SAN zoning section of this white
paper provide best practices for WWN management. The Matrix OE 7.0 release also introduced the ability for SPM to
perform SAN zoning for either pre-provisioned volumes supporting automation or on-demand provisioned volumes. SPM
will create single initiator zones in Brocade SAN environments, using the Brocade SMI-S instrumentation to ensure
each initiator is able to access the appropriate targets.
For the storage administrator to successful y use pre-presented volumes which do not support automated changes to
presentation, the volumes need to be presented to suitable server initiator WWNs. For environments with SAN zoning, the
volumes need to be zoned for suitable access (initiator WWNs and storage target WWNs). Thus, there are situations wherein
the storage administrator needs to have a valid set of initiator WWNs that can be used to present the volumes and zone for
access.
Matrix OE provides an option to the lsmutil command to allow the storage administrator to reserve a specified number of
initiator WWNs. The lsmutil –reserve –wwn command reserves initiator WWNs appropriate for the specified Virtual
Connect Doman Group.
The initiator WWNs returned by the command are valid Virtual Connect WWNs which can be used in storage pool entries
(and then placed in VC profiles by Matrix OE). Rather than have the initiator WWNs al ocated at the time of storage pool entry
creation, they can be al ocated in advance. The storage pool entry al ows the manual specification of a valid VC WWN
(replacing the one automatical y al ocated). This is for the use case when the administrator creating the storage pool entry
wants to replace the automatical y al ocated initiator WWN in the storage pool entry with one of these pre-known WWNs for
which appropriate zoning has already been done. Use of the automatically al ocated WWNs is appropriate for use cases not
involving pre-presented volumes (i.e., when the storage administrator al ows LUN masking to adjust the volumes to the
specified initiator WWNs, or wishes to fulfill the requests as they are received, and will zone and present based on the
supplied initiator WWNs).
Note
The initiator WWNs are reserved for the purpose of facilitating storage pre-al ocation, enabling the administrator creating
the storage pool entry to specify one of these reserved WWNs explicitly (replacing the automatically allocated initiator
WWNs in the storage pool entry, knowing storage is pre-zoned for that specific initiator). These reserved initiator WWNs wil
be freely re-used once the storage pool entry to which they are affiliated is deleted; they are not permanently reserved.
Thus, if the intent is to delete volumes no longer required, but also make available a different set of volumes using the
same initiator WWNs and SAN zoning, the recommended approach is to delete the volumes from the storage pool entry,
which is not affiliated with a logical server, and then add new volumes meeting the needs. This preserves the initiator
WWNs in the storage pool entry, and any SAN zoning which has been done for those initiators to specific array controller
target ports. If the storage pool entry were deleted, the initiator WWNs could be re-used and thus the storage administrator
would want to appropriately adjust zoning to ensure the next user of those initiator WWNs is not granted access
inappropriately.
Use of a CLI enables the storage administrator to gather the information without needing to navigate the Matrix Operating
Environment GUI and then extract the returned WWNs from the storage pool entries. Figure 5 notes use of this CLI and
26
... Ce manuel est également adapté pour les modèles :
Logiciel - HP Matrix Operating Environment w/Insight Control 24x7 Supp 1 Server Lic (3.83 mb)
Logiciel - HP Matrix Operating Environment w/Insight Control 24x7 Supp E-LTU (3.83 mb)
Logiciel - HP Matrix Operating Environment w/Insight Control 24x7 Supp Flexible Lic (3.83 mb)
Logiciel - HP Matrix Operating Environment w/Insight Control 24x7 Supp Tracking Lic (3.83 mb)