So I'm looking to get a good answer on this....
UCS has big share in the market, Part of the cool thing with UCS is you create agregated links to your core, and some storage paths and off you go, you create vnics for managment and production and hbas and you are off.
I have also heard because of this, this doesn't follow VMware best practices to have separate links for managment, production, ...and so on and VMware doesn't support the UCS architecture.....Is this true. I thought VMware and Cisco developed this together???
Yes it is supported - after all VMware has partnered woth Cisco and EMC to form VCE and their offering is built of of the UCS platform
You can also check this one..
For every best practice, there is a history as well as exceptions. The best practice you are talking about (separate physical links for different traffic types) is rooted in the 1GbE world where bandwidth was a consideration. In a 10GbE infrastructure, it is common to aggregate the traffic types on the same physical link because there is more bandwidth. If you still want NIC separation in the UCS you can always use the Virtual Interface Card (VIC) to carve up several vNICs for the different traffic types for both administrative separation and QoS opportunities on each NIC. As with any "best practice," it is best to question and know the history behind the best practice and examine whether it still applies today to your particular environment.