Can you please review and approve my iSCSI storage design. I have read alot of information regarding the MD3200i and to get true active/active multipathing and best throughput I need to dedicate each Host pNIC to a seperate subnet. Also Switches will have Jumbo Frames and Flow Control enabled.
It looks fine to me. I would suggest you to review few other parts before mark it as final.
http://stretch-cloud.info/2011/06/impact-of-stp-and-lacp-in-design/
http://stretch-cloud.info/2011/06/n2-failover-for-a-blade-design-with-upstream-switches/
http://stretch-cloud.info/2011/06/multipathing-within-a-multisite-cluster-a-design-constraint/
Looks good but my personal take on sharing vMotion with another network that will typically take on a lot of traffic is to keep them segregated. I always try to separate the vMotion traffic from other things so I can guarantee my vMotion full throttle. Other than my personal opinion, I think it looks good.
IMHO I prefer have dedicated iSCSI switches.
In your case if you use the PC5424 only for iSCSI you can have two switches without any connection between them.
The vMotion network usually can go on more powerful switches (in a dedicated VLAN).
About the backup network, this really depend on how do you handle backup. If you use SAN or hot-add more you do not need a specific backup network at all.
Andre
These are 2 PC5424s that are dedicated for iSCSI but with 3 VLANs on each. The only VLAN that is on both switches is the vMotion/Backup subnet. I plan on using the VMware Data Recovery solution that comes with Essentials plus to backup the VMs from the production MD3200i to the Backup MD3200i over the 2 dedicated pNICs on each host.
If this is the wrong approach let me know as I have never implemented VDR.
If you go to network more, then VDR talk with hosts, so it depends where is the management port.
Otherwise it can work in hot-add so no need of specific network (basically it works on iSCSI network doing a disk copy).
Andre