http://itknowledgeexchange.techtarget.com/virtualization-pro/getting-started-with-iscsi-and-vmware-esx/ A SearchVMware.com blog Wed, 25 Nov 2009 14:23:01 +0000 http://wordpress.org/?v=2.6.2 http://itknowledgeexchange.techtarget.com/virtualization-pro/getting-started-with-iscsi-and-vmware-esx/#comment-128 Duhaas Fri, 23 Jan 2009 16:42:18 +0000 http://itknowledgeexchange.techtarget.com/virtualization-pro/?p=308#comment-128 1fizgig, just curious to know how many ip's you have defined on your EMC for the target. right now we have use three of the four ports of the datamover and lacp them back to a cisco switch, and just have one ip bound right now. do folks see performance increases with multiple ips pointing to same target? 1fizgig, just curious to know how many ip’s you have defined on your EMC for the target. right now we have use three of the four ports of the datamover and lacp them back to a cisco switch, and just have one ip bound right now. do folks see performance increases with multiple ips pointing to same target?

]]> http://itknowledgeexchange.techtarget.com/virtualization-pro/getting-started-with-iscsi-and-vmware-esx/#comment-127 1fizgig Thu, 22 Jan 2009 22:56:14 +0000 http://itknowledgeexchange.techtarget.com/virtualization-pro/?p=308#comment-127 Rick, we implemented our VI3.5 infrastructure around the middle of last year entirely on iSCSI with an EMC SAN going to 2 HP C7000 blade chassis with 2 hosts in each chassis. This has worked 100% with no issue, and was chosen because even VMWare believed we could happily run over iSCSI in our environment. Capacity planner determined we could virtualize around 50 of our 55 servers, and we've slowly been migrating over the past months to great success. I'd thoroughly recommend going iSCSI as a starting point for a VI infrastructure - you could always migrate to FC if your infrastructure required. Rick, we implemented our VI3.5 infrastructure around the middle of last year entirely on iSCSI with an EMC SAN going to 2 HP C7000 blade chassis with 2 hosts in each chassis. This has worked 100% with no issue, and was chosen because even VMWare believed we could happily run over iSCSI in our environment. Capacity planner determined we could virtualize around 50 of our 55 servers, and we’ve slowly been migrating over the past months to great success. I’d thoroughly recommend going iSCSI as a starting point for a VI infrastructure - you could always migrate to FC if your infrastructure required.

]]> http://itknowledgeexchange.techtarget.com/virtualization-pro/getting-started-with-iscsi-and-vmware-esx/#comment-125 Rick Vanover Thu, 22 Jan 2009 13:40:28 +0000 http://itknowledgeexchange.techtarget.com/virtualization-pro/?p=308#comment-125 There are multiple IPs on the storage device as separate targets, and then paths inward to the same LUNs. There are multiple IPs on the storage device as separate targets, and then paths inward to the same LUNs.

]]> http://itknowledgeexchange.techtarget.com/virtualization-pro/getting-started-with-iscsi-and-vmware-esx/#comment-124 Duhaas Thu, 22 Jan 2009 03:54:20 +0000 http://itknowledgeexchange.techtarget.com/virtualization-pro/?p=308#comment-124 Rick, just curious to know how you have two scsi targets pointing @ the same lun? Do you have multiple ips pointing @ the same target? Rick, just curious to know how you have two scsi targets pointing @ the same lun? Do you have multiple ips pointing @ the same target?

]]>