As he wrote before, he needs to be able to manage the P4000 and cant dedicate a management port for them.
-Anders Sent from my iPhone On 6 dec 2010, at 03:40, Ben N <[email protected]> wrote: I see. And why do you want your iSCSI network to be accessible in your LAN? I was confused initally that you were out of NICs based on your design and wanted your VM Mgmt in your iSCSI network. On Dec 5, 2010 2:23 AM, "Paul Hutchings" <[email protected]> wrote: 12 NICs is more than enough- I got 12 simply as it's easier to have surplus from day one. As for assignments, tbh I think there will be some trial and error there, but I'm leaning towards something along the lines on each host of: vSwitch1 3 NICs (1 onboard and one on each quad card) Port Group 1 - vMotion Port Group 2 - Management/VM Network vSwitch2 2 or 3 NICs Port Group 1 - iSCSI (setup with multiple VMKernels and multi-pathing) The 10gbps link between switches will tag the vMotion and iSCSI VLANs between the switches and the two locations. Not sure whether to go to the lengths of having the Management traffic on its own VLAN or not - I'm not convinced I need it for performance reasons nor for additional security in our environment. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.c... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
