HPE EVA Storage

MSA 2012i vdisk, volumes etc

 
Jeroen H_1
Advisor

MSA 2012i vdisk, volumes etc

I have a MSA2012i single controller unit with 12 750 GB SATA disks. I am struggling with how to configure the vdisk and volume configuration.
I hope there is someone who can point me in the right direction. How many vdisks can I make and how many volumes per disk is wise. I am thinking about two RAID5 vdisks with one hot spare disk for both (so 1 RAID5 5 disk en 1 RAID5 6 disk).
I also want to host hyper-v machines on this SAN. Anybody knows how to do that?
5 REPLIES 5
kunalsahoo
Valued Contributor

Re: MSA 2012i vdisk, volumes etc

Creating Virtual Disks
Two or more disk drives can be logically combined to form a virtual disk. The
combined storage capacity can then be partitioned into volumes. SMU provides both
manual and automatic methods for creating virtual disks, as described in its online
help and in the Administratorâ s Guide.
As an example, the following steps use the manual method to create two virtual
disks with the following characteristics:
â   RAID 5, in which parity is distributed across all disk drives in the virtual disk
â   Five disk drives per virtual disk
â   One spare disk drive dedicated to each virtual disk
â   One volume per virtual disk, where the volume is not visible to data hosts
To create both virtual disks:

1. In SMU, select Manage > Virtual Disk Config > Create A Vdisk.

2. Select Manual Virtual Disk Creation (Detail-based).

3. Type a name for the virtual disk.
The name is case-sensitive and can include
17 characters. Allowed characters
include letters, numbers, hyphens, underscores, and spaces.

4. Select RAID 5 â Parity RAID, Parity Distributed.

5. Click Create New Virtual Disk.

6. Select five drives of the same size and type (all SAS or all SATA).

7. For the dedicated spare drive option, select Yes and click Continue.

8. Select a drive to be the spare and click Continue.

9. For the number of volumes, select 1.(change as per your requirement)

Notice that by default the volume will not be exposed to (accessible by) hosts.

10. Click Create Virtual Disk.
A page is displayed that shows the progress of initializing the virtual disk.

11. Click the link to create another virtual disk.

12. Repeat Step 2 to Step 10 to create a second virtual disk with a different name.

HOST MAPPING


To enable a data host to access a volume you created, you must map the volume to
the host. The host value, typically the IQN (iSCSI qualified name), of each host port
connected to the system is automatically added to the systemâ s global host port list.
Before mapping a data host to a volume you must identify the data hostâ s iSCSI
node name (IQN) and a LUN that the host is not using.
To map a data host to a volume:

1. Select Manage > Volume Management > Volume Mapping > Map Hosts To Volume.
Notice that your first virtual disk and its volume are selected, and the volumeâ s host
mapping values are set to None.

2. In the Assign Host Access Privileges panel:

a. Select the host port IQN value that you identified before beginning.
b. Type the LUN that you identified.

Notice that the mapped host will have read-write access through all controller host ports.
c. Click Map It.

Jeroen H_1
Advisor

Re: MSA 2012i vdisk, volumes etc

Thank you very much for this information. I have three hosts with some virtual machines. i would like to give a few of these a pass-Through disk. But with this config I only have two large disks. Can I make it three? And then I would have to use VHD disks to get the extra disks for my virtual machines?

kunalsahoo
Valued Contributor

Re: MSA 2012i vdisk, volumes etc

yes....you can...that was an example..
depending upon size availability you can create and present to host....
Jeroen H_1
Advisor

Re: MSA 2012i vdisk, volumes etc

But in any case it would be wise to use one volume/LUN per Vdisk? Or can you use multiple volumes on one vdisk?
Thanks again for your quick response.
kunalsahoo
Valued Contributor

Re: MSA 2012i vdisk, volumes etc

you can do multiple volumes in 1 Vdisk....also 1 volume / vdisk is a good idea...