HP Matrix Operating Environment 7.3 and 7.3 Update 1 Logical Server Management User Guide

<xs:element name="wwnNumber" type="xs:int" minOccurs="0" />
<xs:element name="WWN" type="xs:string" minOccurs="0" />
<xs:element name="type" type="xs:int" minOccurs="0" />
<xs:element name="nodeValue" type="xs:string" minOccurs="0">
<xs:element name="allocatedValue" type="xs:string" minOccurs="0">
<xs:element name="ready" type="xs:boolean" nillable="true" minOccurs="0" />
<xs:element name="inProfile" type="xs:boolean" nillable="true" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Requesting server (initiator) WWNs for storage preallocation
The LSMUTIL -reserve –wwn option allows the storage administrator to request a number (from
1 to 100) of server (initiator) WWNs for a specified Virtual Connect Domain Group or a particular
server WWN. The server WWNs are allocated in advance, instead of during storage pool entry
creation, and are reserved for storage preallocation.
Preallocating server WWNs allows an administrator to preconfigure any needed zoning, and
possibly pre-present volumes for later use. Preallocation of WWNs is required if the administrator
is using the –import –spe option to create a new SAN storage pool entry, because the storage
pool entry must have server WWNs specified for its storage port(s). If the administrator is using
the –import –spe option to modify an existing storage pool entry, specifying server WWNs
are optional. However, if used, the server WWN replaces the server WWN previously associated
with the storage pool entry.
These reserved server 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, remove the volumes from the storage pool entry (that is not associated with a logical
server), and add new volumes. This preserves the server WWNs in the storage pool entry (and
any SAN zoning that has been done for those server WWNs to specific array controller target
ports). If the storage pool entry is deleted, the server WWN can be re-used. The storage
administrator should adjust zoning to ensure the next user of those server WWNs is not granted
access inappropriately.
Example XML file
Example 2 “Example XML file for storage import and export” is an example XML file containing
two storage pool entries, both of which are 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 tagged within
<WWN> 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> <ServerWWN> element with the
initiator WWNs tagged within <WWN>, and the storage target information (<targetWWN>
and <LUN>) is in the <SanVolumePath> element.
72 LSMUTIL database utility