{"id":608,"date":"2012-06-14T15:20:53","date_gmt":"2012-06-14T21:20:53","guid":{"rendered":"http:\/\/benincosa.com\/blog\/?p=608"},"modified":"2014-11-19T11:24:53","modified_gmt":"2014-11-19T17:24:53","slug":"a-nexus-1000v-value-proposition","status":"publish","type":"post","link":"https:\/\/benincosa.com\/?p=608","title":{"rendered":"A Nexus 1000v Value Proposition"},"content":{"rendered":"

There’s a lot of collateral <\/a>about why the Nexus 1000v would be a good thing to have in your virtual environment. \u00a0When I talk to people about it one of my first questions is:<\/p>\n

“Who manages the virtual networking environment in the data center?”<\/p>\n

Most of the time its the virtual machine administrators. \u00a0Its usually not the networking team. Typically the network team stops at the physical access layer and anything on the server is the responsibility of the server administrator (which is also the VM administrator)<\/p>\n

If the shop is big enough, the second question I usually ask is:<\/p>\n

“Would you like the networking team to manage the virtual networking environment?”<\/p>\n

Most of the time this is greeted enthusiastically. \u00a0After all, the networking team has to troubleshoot the VMware environment anyway. \u00a0Why not just give them control of it? \u00a0That’s one less problem the virtual administrative team has to deal with.<\/p>\n

That’s one of the best benefits of the Nexus 1000v. \u00a0Those old lines of demarkations are back. \u00a0And the cool thing? \u00a0Network visibility is back with a consistent command line.<\/p>\n

Here’s a video I made to show this line of demarkation in action<\/p>\n