Initiator ports cannot be used for provisioning, The software is unable to map a host to volumes, In different host storage domains of the same port – HP Storage Essentials NAS Manager Software User Manual
Page 375: On hds 9900v, Issues specific to hp storage systems, Size reported as 0 on eva array volumes of 1 gb or, Details on eva array, Last volume, Same port on hds 9900v
Storage Essentials 5.00.01 User Guide 345
example, assume you want the management server to wait an hour. You would assign 3600000
to cimom.provider.hds.ProvisioningTimeout, since 3600000 milliseconds is one
hour.
cimom.provider.hds.ProvisioningTimeout
=3600000
7.
When you are done, click Save.
8.
Restart the service for the management server for your changes to take effect.
While AppStorManager is restarting, users are not able to access the management server. The
AppStorManager service must be running for the management server to monitor elements.
Initiator Ports Cannot Be Used for Provisioning
Ports designated as an Initiator on a storage system belonging to the HDS Freedom Storage™
Lightning 9900™ Series or Freedom Storage Lightning 9900V Series cannot be used for
provisioning. If you select one of these ports, you receive a message saying that provisioning failed
because the HiCommand Database was not refreshed. The management server does not support
provisioning for ports designated as Initiators on these storage systems.
The Software Is Unable to Map a Host to Volumes
in Different Host Storage Domains of the Same Port
on HDS 9900V
On HDS 9900V storage systems, if a host is already mapped to a volume and you try to map the
same host to a volume in another host storage domain, corresponding to the same port, it will fail.
However for HDS 9900, the host can be mapped to a volume in another host storage domain
corresponding to the same port.
A Default LUN Number Is Used Instead of a User-Specified One
When you create a LUN, the user-specified LUN is ignored. The LUN is created with the next
available default number.
Issues Specific to HP Storage Systems
•
Size Reported as 0 on EVA Array Volumes of 1 GB or More (Correct Size is Reported After
Running Get All Details on EVA Array
•
Cannot Always Delete Selected Volume on MSA, MSA Allows Deletion of Only Topmost or Last
Size Reported as 0 on EVA Array Volumes of 1 GB or
More (Correct Size is Reported After Running Get All
Details on EVA Array
If you create a volume of 1 GB or more on an EVA, the size reported is 0 until a Get All Details is
run on the EVA array. Smaller volume sizes do not exhibit this problem. This is a limitation in the
EVA array software, and AppIQ is working with HP to resolve this issue.
Cannot Always Delete Selected Volume on MSA, MSA Allows Deletion of
Only Topmost or Last Volume
You can delete only the last or topmost volume on each of the MSA array’s controllers (modeled as
pools). Attempting to delete other volumes will return a generic error code 4. This is a limitation in
the MSA array software and AppIQ is working with HP to resolve the issues.
- Storage Essentials Provisioning Manager Software Storage Essentials Backup Manager Software Storage Essentials Chargeback Manager Software Storage Essentials Report Designer Software Storage Essentials Global Reporter Software Storage Essentials Enterprise Edition Software Storage Essentials Exchange Viewer Software Storage Essentials File System Viewer Software