Operating Environment Software Instruction Manual

2. The device on which the read-only volume exists can be created in the SPM catalog as an
unmanaged array. All volumes from this array are unmanaged, and do not have the ability to
automate volume presentation.
3. Create storage pool entries for the read-only volume that are not fulfilled through SPM catalog
storage. Instead, manually populate storage details into the storage pool entry after consultation
with the storage administrator.
Windows 2008 Host Mode
Symptom–When using the Windows 2008 host mode in a storage profile entry, and after having
selected a candidate volume, the request fails to bind.
Possible cause–Some EVA 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–There are two alternatives to work around this issue:
1. Do not use Windows 2008 host mode unless there is an identified need for it. Today, using this
mode is only useful in situations involving clustering: specifying Windows 2008 causes read
capacity commands to execute whether the LUN is reserved or not. This is the only difference
between Windows and Windows 2008 host modes. Thus, the Windows hostmode can be used
when the OS is Windows Server 2008, unless the environment is using clustering and requires
the read capacity behavior described above.
2. If using Insight Dynamics 6.0, upgrade Command View to version 9.1 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. The Insight Dynamics 6.0 Update 1
release adds support for Command View 9.0 with Windows 2008 host mode.
Delay in changes made to EVA array becoming visible in SPM catalog
Symptom–When a storage administrator makes a change to an EVA 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 via the SMI-S interface. The EVA SMI-S implementation
caches information for fast retrieval and the cache is updated every 30 minutes. 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 modification using Command View, an SPM user must either
wait up to 30 minutes before the change is visible to SPM, or manually cause the EVA to release the
updated EVA information from its cache. To refresh, manually restart the HP StorageWorks CIM
Object Manager and then refresh the array or volume information in SPM (depending on the type of
EVA change made in Command View). For example, if a new volume was created on the EVA 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.
Troubleshooting68