PS4100X - Initial Set configuration (vSphere 5)

Thanks for this detailed information.

based on 12 600GB Drives how would we suggest creating the raid sets / LUNs i.e would you create 3 x 4 Disk Raid 10 LUNS, with a Datastore on each, or would you create a mix of say Raid 5, and Raid 6.

As i get the comment regarding splitting up into smaller vloumes, but want to ensure good raid protection and esx performanace.

Thanks for the info.

I have created a 4.7 TB array on my san. Using Raid 6 and a hot spare.

I was advised to create volumes and present them directly to the guest os inside the vm enviroment, but I was just going to create datastores, as my enviroment has low i/o requirements.

This being the case, is there any best practices for creating datastores, or do I just have to follow esx best practices for datastores.

cheers

John

One thing I did wonder, is if you are running presenting volumes directly to the vm, the vm will have to share the vswitch with a network port group and iscsi traffic. Does this not affect performance, as I have separate vswitches for iscsi traffic, and network port groups on another vswitch. or did I miss something.

cheers Don food for thought.

"Ideally, you would have a separate vSwitch and physical NICs for that VM iSCSI traffic. It's not required, since in most installations, you don't max out the network bandwidth."

didnt quite follow sorry. currently i have physical nics hanging off the vswitch for network connectivity and additional physical nics attached to another vswitch that runs the iscsi traffic.

The iscsi traffic is ran though physically seperated by switches, therefor a windows 2003 server for example can not see the iscsi target on the san if i created it a volume.

hope that makes sense

cheers

John

also.

Where you say "In the VM settings, when you have multiple VMDKs (or RDMs), create a new Virtual SCSI adapter for each VMDK/RDM."

Is this not the standard action when you create a additonal virtual disk.

cheers

John

one final question would be is it better to create volumes and present them to the VMs using the method above. as in  "the VM settings, when you have multiple VMDKs (or RDMs), create a new Virtual SCSI adapter for each VMDK/RDM.  (up to 4 SCSI controllers per VM max)"

or do it via the direct mapoping on the vswitch as you suggested "  You would create a new vswitch and add physical nics to it.  Those nics would be in same subnet as the esx iscsi nics are.  So those vm would be able to access the san.  That way you don't share phyysical nics for esx iscsi and guest iscsi"

I guess it depends on the applicaions?

cheers

John

I get it, sorry, been away,

So the traffic is separated by vswitch but contactable by network.

sorry for being so slow.