HP Storage Essentials Enterprise Edition Software - Manual (Page 604)

Provisioning Manager 566
Issues Specific to HDS Storage Systems
This section contains the following topics:
• About Provisioning on HDS Storage Systems , page 566
• Host Security Group Names on HDS Storage Systems , page 566
• Unable to Provision When HDS CruiseControl Is Enabled , page 567
• Increasing the Wait Time for the Management Server , page 567
• Initiator Ports Cannot Be Used for Provisioning , page 568
• Mapping Issue on HDS 9900V Storage Systems , page 568
About Provisioning on HDS Storage Systems
IMPORTANT: The management server does not allow LUSE of different RAID levels.
HDS ships some of its storage systems with volumes already created. When the software first
discovers an HDS storage system, it detects the volumes created by HDS. When you use the
software's create a volume feature, you are assigning already-created volumes.
The software does not delete volumes created by HDS. When you use the software's delete a
volume feature, the software marks the volume as hidden in its repository. These hidden volumes are
stored in the Free LDEVs list.
If you use an LDEV from the Free LDEVs list when you create a volume, the LDEV is removed from the
list because it is now assigned.
HDS cannot create a LUSE volume (made up of multiple LDEVs) without mapping it to a target port
(that is, without creating a LUN). In the software, creating a volume and creating a LUN are two
different operations. Therefore, the software keeps the volumes, made from multiple LDEVs in the
Grouped LDEVs list in the repository. Once these volumes are mapped to the target port and a LUN
is created for them, they are removed from the repository and a real LUSE volume is created on the
HDS box.
For example, assume you have several 2-GB Free LDEVs and you want to create a 4-GB volume.
Since the requested 4-GB volume is larger than one LDEV, two of the Free LDEVs will be used for the
4-GB volume.
Host Security Group Names on HDS Storage Systems
In releases prior to build 5.0, when you used the management server to create a host security
group, the newly created host security group was displayed by the name attribute. The name
attribute is stored only in the HiCommand database and it is not stored in the host security group
itself on the device. This is why the name attribute does not appear in the native tools. The name
attribute can be 50 characters in length. Hitachi storage arrays contain host security group records
on the device. These are identified by the DisplayName attribute that is read only. The
DisplayName is displayed in the native tools. On some HDS storage systems, an additional
nickname
attribute is available to be set on the host security group and its value is stored on the
device itself. The management server uses the name attribute instead of the nickname attribute
because not all HDS storage systems support setting the nickname attribute.