HP Logical Server Management Best Practices

Figure 26: Exporting and importing storage pool entry definitions

Creation of storage pool entries in advance requires that the storage administrator anticipate the types of storage

required, and the initiator WWNs needed for storage presentation and SAN zoning are made available through

another option of the lsmutil command (-reserve -wwn).

When the lsmutil -import -spe command is used, Matrix OE will match the storage pool entries in the XML file

based on the <id> element. If there is no <id> tag, the entry is assumed to be a new storage pool entry. When a

matching <id> is found, the information in the XML file is used to populate the storage pool entry (i.e., adding

information such as storage controller port WWN and LUN number, and perhaps defining additional ports and

WWNs).

NOTE: The WWNs in the imported storage pool entry take precedence; if the storage administrator wishes to

change the initiator WWNs from those in the original request, they can edit new WWNs into the XML file. The

WWNs specified must be valid Virtual Connect WWNs and the storage administrator should ensure the WWNs are

not already in use.

The format of the XML file is shown below, with the example containing two storage pool entries, both SAN storage

in the “razorsaw” portability group storage pool. The first entry has one 20 GB boot volume, with a Windows host

mode, RAID0, and a single path (no redundancy). The storage target information has been specified in the

<targetWWN> element of the <SanVolumePath> (and 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 shown below is for a web server with one 40 GB data volume and a 10 GB boot

volume. These two volumes use a Linux host mode and RAID0. The data volume is single path (no redundancy), and

the boot volume has redundancy (two paths, thus two visible server initiator WWNs, with one path indicated as

PRIMARY and the other as SECONDARY). The initiator WWNs are in the <SanPort> elements, and the storage

target information (<targetWWN> and <LUN>) is in the <SanVolumePath>. If the storage has been defined, but