HP Logical Server Management Best Practices

28
Figure 22: Add Storage Pool Entry (using SPM storage catalog)
Figure 22 shows a storage pool entry for a web server, containing ports defined for two fabrics, and two volumes
(one 10 GB boot LUN with redundant paths, and one 40 GB data LUN). Matrix OE has allocated the server WWNs
for both HBA ports defined for this entry (shown in the Manage Server WWNs table at the bottom of the screen). All
volumes should be initially made visible to the initiator HBA WWNs by selecting the “Masked” checkbox. If
appropriate, the data volumes can later be unmasked (using this interface or automatically by infrastructure
orchestration) to make them inaccessible during OS installation.
Figure 22 also shows the result of selecting the boot volume and using the “Show Candidates” button. The
Candidates list in the Volume & Path Selection table is now populated with suitable matches. In this case there are
four matches, two 10 GB in size, as well as 20 GB and 40 GB volumes (which are larger than the size requested for
this boot volume). Volumes which did not match the RAID level, tags, or could not be modified to have suitable host
mode or LUN masking are not returned as candidates.
Saving the storage pool entry with candidates selected will result in Matrix OE automatically having SPM associate
(or bind) those selected volumes with the defined volume requests. Until the storage pool entry is saved, those volume
are not yet associated/bound, and can be returned in other candidate searches as available candidates. In the
storage pool entry in Figure 22, the same 40 GB volume will be returned when showing candidates for the data
volume (since it requires a minimum size of 40 GB). Obviously the same candidate should not be chosen twice. Once
the storage pool entry is saved and the candidate volumes are associated/bound, they will not be retuned for future
requests.