HP Logical Server Management Best Practices

Figure 39: Adding Storage Port WWN and LUN information

Once the storage entry is saved with the appropriate storage details and the Ready checkbox selected for each

potential target (indicating storage has been created, presented, and zoned), it is available for use when the logical

server is instantiated onto a virtual machine (and perhaps later onto a physical system as the administrator takes

advantage of the Matrix OE capabilities for flexible movement of cross-technology logical servers).

WWN Management and SAN zoning

As shown earlier, initiator HBA WWNs are affiliated with logical server storage pool entries. The initiator HBA

WWNs can be provisioned by the Matrix OE solution, can be manually specified by the administrator when defining

the logical server storage pool entry, or can be populated into the storage catalog entry from a pre-presented, view

only SPM storage catalog entry. The specified initiator WWN (provided manually by the administrator defining the

storage pool entry, or used for a pre-populated SPM storage catalog entry with the storage pre-presented to the

initiator WWN) must be a valid Virtual Connect WWN (most likely obtained through the use of the lsmutil –

reserve -wwn command or previously allocated by Matrix OE and now available for safe re-use due to deletion of

the previous storage pool entry using that initiator WWN).

NOTE: The initiator WWNs specified must be valid VC WWNs. To avoid potential conflicts (specification of a

WWN that the Matrix OE solution might automatically provision), there is an lsmutil –reserve -wwn command

which the administrator can use to reserve from 1 to 100 valid VC initiator WWNs. Those initiator WWNs can be

used for storage presentation and later supplied when defining a storage pool entry (through the graphical interface

or via the command line). The initiator WWNs are reserved for the purpose of facilitating storage pre-allocation.

These reserved initiator WWNs will 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, the recommended approach is to delete the volumes from the storage pool entry