http://www.1usdbidlink.net
http://www.1usdbidlink.com/

also http://www.media-packs.com is a good link exchange source,if you want to link exchange pls consider this site PR3 and 24hours link exchange promiss.

Thanks again Hany for your valuable input.

—–
Alex

The only thing that would worry me about putting everything on one vDS is security. I have to dig deep into this topic before I can give any opinion about it.

It depends on the customer requirements whether to use the Cisco Nexus 1000V or the native vDS. For me, as an example, NX1V is mandatory because I need to have Netflow stats, and also to run IDS using the SPAN ports of the switches. There are a lot more features of course that comes with it, I’m just naming a few.

Regards,

Thanks for letting me know that there is a limit to the vDS for the entire vCenter server.

Do you think it makes any sense to put everything is one vDS? Would this simplify things or do you recommend having different vDS for each services.

Also what's your take on the Nexus 1000 switch? Is it a buy? or just use the vSphere Enterprise Plus with the vDS.

Thanks

—–
Alex

The reason why I made deferent VMkernel portgroups for VMotion & FT was to dedicate deferent uplinks for them. It is highly recommended by VMware to dedicate at least 1Gbps links for FT (better 10GbE) due to the extensive BW it uses for the logging traffic.

Please also note one important thing, you can’t have more than 16 vDS per an entire vCenter server! This is kind of a limitation for the time being IMHO, so you must use your vDSs wisely.

I use MS Visio 2007 for my diagrams. Mainly using basic block shapes – Glad you liked them

Regards,

I know why NOW! these are the VMkernel Port assigned to each ESX HOST, hence the different ip address assignment.

Thanks

—–
Alex

You are absolutely right on that part. I had some trouble taking back control of my host once I lost connection to my host by moving the management console over to vDS.

After review the whole design of the vDS and having a better understanding of the the new technology. It makes a lot of sense to split up the different services. VM Network should be one vDS. FT+VMotion should maybe have it own vDS. and vSS should be only for management. What I don't really get is why do you have multiple VMkernel Ports for VMotion and FT? vmk1:192.168.10.1, 192.168.10.2, and 192.168.10.3. Does this improve the performance?

Also, my understanding is the vSphere 4 has improve the Network performance in general by a lot does this this mean for vSS or vDS? I would imagine that vDS would be slower overall because it need to keep track of the traffic and there could be more overhead since it's being managed by the vCenter side.

I would like to hear your thoughts on this.

BTW nice diagrams, which program did you used to make them? Their really cool! I would like to generate my own and maybe I can send you what I have.

Thanks

—–
Alex