Not too sure to be honest on that one, my plan is for all iSCSI traffic to go through the 8024F anyway.
Going to experiment a little and see what each one can do as I am still unsure on how to setup this all. Could do with another 10GbE SFP NIC for that though!
In regards to my previous post on power usage, I plugged the 8024F alongside the following
APC 1U Switched PDU with all ports on (roughly 8w)
HP ProCurve 1800-24G (19w previously)
Dell 5524 (assuming 18w roughly)
For a grand total of 134w, so the 8024F idle with one PSU in (removed the 2nd) seems to be about 90w
I don't plan on leaving that on 24/7, there is absolutely no need seeing as it will be used for either development purposes or accessing data on NAS.
Drawn down in paint my plan which I had in my head for how the two networks would interface, but now I have seen it in drawn out it's probably a bad idea. My thinking behind the below is there would be a iSCSI vlan on the 24/7 network and a corresponding one on the part time network and either node0 or node1 would route between the two.
But more I think about it, this is a little nuts!
(The supermicro node is what I haven't purchased yet, but very tempted!)
Not too sure the best way to do this, after seeing the Dell's power usage I am tempted to lose the HP ProCurve and somehow have the 5524 as my primary 24/7 switch
Think the best way is going to be setup a few different ways of doing things and see what works best.
Looking like my goal of 100w maximum running 24/7 is going out of the window quickly!
EDIT:
I am also thinking about getting 3x additional 240GB OCZ SSD's for Node 0 and running them in RAID10 alongside my original one.
This would then be my primary VM store for all hosts. Need to find a suitable RAID card for this though.
Then have the large, slower RAID10 on my NAS server using 6x 7K3000 Hitachi disks (should be 8 soon as my warranty replacements come through
)