HP Storage Provisioning Manager (SPM) Version 1.2 User Guide

Possible cause–These symptoms indicate that while SPM is able to send a request to the device via
the Extensible Storage Adapter (ESA), ESA is not able to communicate the device response to SPM.
This usually happens because of a DNS on Active Directory configuration issue. The CMS advertises
a network name that cannot be resolved in the DNS. It is not the purpose of this document to provide
guidance on network configuration, but potential causes can be:
• The CMS is not registered on the DNS.
• CMS operates in a protected environment without a DNS service.
• A conflict exists between the names registered on the DNS and the Active Directory.
Suggested action–SPM provides a solution for this scenario through a means to override the name
that ESA should use to post the response. To override the name:
1. Locate the HP.Arcadia.ServerWindowsService.exe.userconfig file.
2. Within that file, locate the <LocalHostnameOverride> element.
3. Use localhost as an override:
<LocalHostnameOverride>localhost</LocalHostNameOverride>.
Alternatively, you can use a known working hostname or the IP address of the CMS. This last
alternative is not recommended.
Insight Dynamics storage pool issues
No matching candidates found
Symptom–The Use catalog storage checkbox on the storage pool entry is disabled (grayed out).
Possible cause–The Insight Dynamics 6.0 solution (including 6.0 Update 1) released with the storage
catalog capabilities is disabled because SPM was a technology preview.
Suggested action–If suitable storage is not in the catalog, the storage administrator must create/zone
appropriate storage and make it available in the catalog. Unfulfilled requests are easily visible and
can be manually or automatically fulfilled. If you believe the storage catalog contains suitable storage
that is not being returned as matching candidates, consider the following:
• Check the requirements specified in the logical server storage pool entry (size, redundancy, fabric,
tags).
• The Fabric Name must be an exact match to the SAN ID values in SPM; check and adjust if neces-
sary.
• Tag values must be an exact match between the logical server storage pool entry and SPM; check
and adjust if necessary.
• The Masked checkbox on the storage pool entry screen should be selected. You may later clear
it for data volumes prior to OS deployment, or infrastructure orchestration may clear it for you,
but it should be selected initially to find candidate volumes to bind.
• The Presentation checkboxes on the volume in SPM should be selected and should have appropriate
SAN ID and port values, or the catalog entry should provide permissions for the presentation to
be modified.
• Another storage pool entry may have bound to the storage volumes you intended to use; check
and either get additional storage or unbind that storage it if was mistakenly bound. The SPM service
needs to be running.
• The SPM Fulfillment screen can provide additional details, including the ability to browse all un-
bound volumes and see an evaluation of how they match to the specific requirements of the storage
request. The administrator can force a binding within SPM even if all requirements are not met,
creating a Nonconforming fulfillment.
HP Storage Provisioning Manager (SPM) Version 1.2 User Guide 69