<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malaysia VMware Communities &#187; VNTag</title>
	<atom:link href="http://malaysiavm.com/blog/tag/vntag/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Thu, 26 Apr 2012 15:54:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>VN-Link and Cisco Nexus 1000V Confusion</title>
		<link>http://malaysiavm.com/blog/vn-link-and-cisco-nexus-1000v-confusion/</link>
		<comments>http://malaysiavm.com/blog/vn-link-and-cisco-nexus-1000v-confusion/#comments</comments>
		<pubDate>Sat, 26 Jun 2010 06:23:58 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[nexus 1000v]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[VN-Link]]></category>
		<category><![CDATA[VNTag]]></category>
		<category><![CDATA[vsphere 4]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1954</guid>
		<description><![CDATA[Recently there are many confusion about these new terms VN-Link &#38; Cisco nexus 1000V which been widely communicated to the IT user groups. Where were the confusion come from? Most of the time, we are getting confuse about what is VN-Link meant by Cisco. Below is some short description you may want to refer to. [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-7430566020196385";
/* MVM Index Link Code 468x15, created 1/3/10 */
google_ad_slot = "5937837755";
google_ad_width = 468;
google_ad_height = 15;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p><p>Recently there are many confusion about these new terms <a href="http://malaysiavm.com/blog/tag/VN-link">VN-Link</a> &amp; Cisco nexus 1000V which been widely communicated to the IT user groups. Where were the confusion come from? Most of the time, we are getting confuse about what is VN-Link meant by Cisco. Below is some short description you may want to refer to.</p>
<p>Cisco <a href="http://malaysiavm.com/blog/tag/nexus">Nexus</a> 1000V is a enhance virtual distributed virtual switch which integrate to the VMware vSphere 4. With Cisco Nexus 1000V, you will contain VSM and VEM, which VSM will be the virtual appliances that host the management of Nexus 1000V, and VEM will be installed on each ESX host that been connected to the Nexus 1000V.  I will not go in too details about Nexus 1000V in this post as my intention is to clear up the confusion on the VN-Link meant by <a href="http://malaysiavm.com/blog/tag/cisco">Cisco</a>.</p>
<p><span id="more-1954"></span>6 months ago, this new term had come to my career while someone had claimed that the VN-Link will allow virtual machine to direct interact to the physical IO devices on the PCI-E without hypervisor in place. Well, this features had been included in VMware for quite some times in <a href="http://malaysiavm.com/blog/tag/vsphere">vSphere</a> 4 by using the functionality call VMDirectPath I/O. But while doing this, you will lose the functionality of VMotion, and most users will not go for this due to the limitation on <a href="http://malaysiavm.com/blog/tag/VMotion">VMotion</a>. Since this is new, no right or wrong, I decided to leave it for a while and further research to understand it.</p>
<p>After many round of discussion and reading on the blog and white paper, finally I have the answer I want now. VN-Link is the product name for a family of products, does not specifically refer to any one product so forget the idea of hardware vs. software implementation, etc.  Think of the Nexus family of switches: 1000v, 2000, 4000, 5000, 7000.  All different products solving different design goals but are components of the Data Center 3.0 portfolio from Cisco.  In VN-Link it contains Cisco Nexus 1000V, <a href="http://malaysiavm.com/blog/tag/hypervisor">Hypervisor</a> Bypass with Direct Path I/O, Pass Through Switching, Virtual Interface card &amp; VNTag. If you had done the administration or implementation on Cisco UCS, Nexus <a href="http://malaysiavm.com/blog/tag/1000v">1000V</a>, Nexus 5000 &amp; 2000, you should familar with all these term that I mentioned here.</p>
<p>For more details information, I will recommend the <a href="http://www.unifiedcomputingblog.com/?p=116">Unified Computing Blog</a> who had done the good explanation to described further in details for the VN-Link technology.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/vn-link-and-cisco-nexus-1000v-confusion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.308 seconds -->

