HP Insight Virtualization Manager with Logical Server Management 6.1 User Guide

</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Requesting initiator WWNs for storage preallocation
The LSMUTIL --reserveWWNs option allows the storage administrator to request a number
(from 1 to 100) of initiator WWNs for a specified Virtual Connect Domain Group. The initiator
WWNs are allocated in advance, instead of during storage pool entry creation, and are reserved
for storage preallocation.
Preallocating initator WWNs is useful if the administrator creating the storage pool entry wants
to manually replace the automatically allocated initiator WWN in the storage pool entry with a
preallocated WWN, for which appropriate zoning and perhaps storage presentation has already
been done. Automatically allocated WWNs can be used when a prepopulated storage catalog is
not used (for example, when the storage administrator fulfills requests as they are received, and
zones and presents storage based on the supplied initiator WWN).
These reserved initiator WWNs can be freely reused when the storage pool entry to which they
are associated is deleted; they are not permanently reserved. To delete volumes that are no longer
required, but also make available a different set of volumes using the same initiator WWNs and
SAN zoning, delete the volumes from the storage pool entry (that is not associated with a logical
server), and add new volumes. This preserves the initiator WWNs in the storage pool entry (and
any SAN zoning that has been done for those initiators to specific array controller target ports).
If the storage pool entry is deleted, the initiator WWN can be re-used. The storage administrator
should adjust zoning to ensure the next user of those initiator WWNs is not granted access
inappropriately.
Example XML file
Example 7-2 “Example XML file for storage import and export” is an example XML file containing
two storage pool entries, both SAN storage in the “razorsaw” portability group's storage pool.
The first storage pool entry has one 20 GB boot volume, with a Windows hostmode, RAID0,
and a single path (no redundancy). The storage target information has been specified in the
<targetWWN> element of the <SanVolumePath>. The <LUN> is also specified. The
<SanPort> element contains information about the HBA initiator WWNs for use by the
storage administrator to configure LUN masking and SAN zoning.
The second storage pool entry is for a web server with one 40 GB data volume and a 10 GB
boot volume. These two volumes use a Linux hostmode, no RAID, and are single path (no
redundancy). The initiator WWNs are in the <SanPort> elements, and the storage target
information (<targetWWN> and <LUN>) is in the <SanVolumePath> element.
Using LSMUTIL with logical server storage 91