HP Matrix Operating Environment Software - Manual (Page 56)

Possible cause–Some EVA disk arrays support a specific Windows 2008 host mode. A known issue
in Command View EVA 9.0 prevents SPM from using Windows 2008 mode when configuring an
existing host (or creating a new one) on the array. Additionally, this defect prevents SPM from
detecting that the Windows 2008 mode was assigned to a host (possibly via Command View EVA).
Suggested action—If using Insight Dynamics 6.x, upgrade Command View to version 9.2 or above.
In some cases, this may require an upgrade of the array firmware as well. Compatibility information
is available on the HP web site:
http://www.hp.com/storage/spock .
Delay in changes made to EVA disk array becoming visible in SPM catalog
Symptom–When a storage administrator makes a change to an EVA disk array using the EVA
Command View management utility (for example, creating a new volume or performing volume
mapping), it may take several minutes for those changes to be reflected in the SPM storage catalog.
Possible cause–SPM communicates with the EVA disk array via the SMI-S interface. If the cache
has not been refreshed to the latest information, the information returned to SPM does not include
the most recent changes.
Suggested action–After making an EVA disk array modification using Command View, an SPM
user must either wait for the change to become visible to SPM, or manually cause the EVA disk
array to release the updated EVA disk array information from its cache. To refresh, manually restart
the HP CIM Object Manager and then refresh the array or volume information in SPM (depending
on the type of EVA disk array change made in Command View). For example, if a new volume
was created on the EVA disk array, and you want to see it in SPM, restart the CIM Object Manager,
start SPM, refresh information from the array, and if preferred, import the new volumes into the
catalog.
Device Communication Failures and DNS Configuration
Symptom–When performing SPM operations involving communication with the array, get a failure
message: Application Error - Device communication failure (See log for details). Additionally, the
SPM log contains a WAITING_TO_PUBLISH error.
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 element.
3. Use localhost as an override:
localhost .
Alternatively, you can use a known working hostname or the IP address of the CMS. This last
alternative is not recommended.
HP 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 HP Insight Dynamics 6.0 solution (including 6.0 Update 1) released with the
storage catalog capabilities is disabled because SPM was a technology preview.
56 Troubleshooting