<?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>BRAD HEDLUND&#187; NIV</title>
	<atom:link href="http://bradhedlund.com/topics/data-center/niv/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradhedlund.com</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Sat, 19 May 2012 14:08:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Cisco UCS criticism and FUD: Answered</title>
		<link>http://bradhedlund.com/2010/12/31/cisco-ucs-criticism-and-fud-answered/</link>
		<comments>http://bradhedlund.com/2010/12/31/cisco-ucs-criticism-and-fud-answered/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 01:30:48 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[Cisco UCS]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[FUD]]></category>
		<category><![CDATA[NIV]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=2529</guid>
		<description><![CDATA[One of my readers recently submitted a comment asking me to respond to some criticisms he frequently hears about Cisco UCS.  This is a pretty typical request I get from partners and perspective customers, and its a list of stuff I &#8216;ve seen many times before, so I thought it would be fun to address [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2010/12/31/cisco-ucs-criticism-and-fud-answered/feed/</wfw:commentRss>
		<slash:comments>47</slash:comments>
		</item>
		<item>
		<title>Great questions on FCoE, VN-Tag, FEX, and vPC</title>
		<link>http://bradhedlund.com/2010/12/09/great-questions-on-fcoe-vntag-fex-vpc/</link>
		<comments>http://bradhedlund.com/2010/12/09/great-questions-on-fcoe-vntag-fex-vpc/#comments</comments>
		<pubDate>Thu, 09 Dec 2010 16:49:05 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FCoE]]></category>
		<category><![CDATA[FEX]]></category>
		<category><![CDATA[Nexus]]></category>
		<category><![CDATA[NIV]]></category>
		<category><![CDATA[Q&A]]></category>
		<category><![CDATA[vPC]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=2449</guid>
		<description><![CDATA[I received some really good questions about FCoE, VN-Tag, FEX, and vPC from a reader named Lucas.  Although I had 10 other things to do, I just couldn&#8217;t resist highlighting these questions, and my answers, in a new post that I thought my readers would enjoy! Brad, You have amazing information about Nexus and UCS [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2010/12/09/great-questions-on-fcoe-vntag-fex-vpc/feed/</wfw:commentRss>
		<slash:comments>35</slash:comments>
		</item>
		<item>
		<title>Cisco UCS Fabric Extender (FEX) QoS</title>
		<link>http://bradhedlund.com/2010/12/08/cisco-ucs-fabric-extender-fex-qos/</link>
		<comments>http://bradhedlund.com/2010/12/08/cisco-ucs-fabric-extender-fex-qos/#comments</comments>
		<pubDate>Wed, 08 Dec 2010 16:47:31 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[Cisco UCS]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[FEX]]></category>
		<category><![CDATA[NIV]]></category>
		<category><![CDATA[Q&A]]></category>
		<category><![CDATA[QoS]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=2430</guid>
		<description><![CDATA[What is the role of the fabric extender (FEX) in Cisco UCS QoS? This question was posted as a comment to my recent article VMware 10GE QoS Design Deep Dive with Cisco UCS, Nexus &#8212; as well as here, at the Cisco Support community forums. Brad: A comment to test my understanding and then a [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2010/12/08/cisco-ucs-fabric-extender-fex-qos/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>The end to end (FCoE) justifies the means to means</title>
		<link>http://bradhedlund.com/2010/11/19/the-end-to-end-fcoe-justifies-the-means-to-means/</link>
		<comments>http://bradhedlund.com/2010/11/19/the-end-to-end-fcoe-justifies-the-means-to-means/#comments</comments>
		<pubDate>Sat, 20 Nov 2010 02:18:24 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FCoE]]></category>
		<category><![CDATA[media & analyst]]></category>
		<category><![CDATA[NIV]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=2297</guid>
		<description><![CDATA[I was pleasantly surprised to see that Mike Fratto, site editor and lead analyst from Network Computing, called me out in this article, with the following statement: two nodes using FCoE connected to a Nexus 2000 Fabric Extender, which is connected to a Nexus 5000, does not constitute end-to-end Ethernet FCoE because the Nexus 2000 [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2010/11/19/the-end-to-end-fcoe-justifies-the-means-to-means/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Cisco UCS Fabric Failover: Slam Dunk? or So What?</title>
		<link>http://bradhedlund.com/2010/09/23/cisco-ucs-fabric-failover/</link>
		<comments>http://bradhedlund.com/2010/09/23/cisco-ucs-fabric-failover/#comments</comments>
		<pubDate>Thu, 23 Sep 2010 20:03:03 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[Cisco UCS]]></category>
		<category><![CDATA[NIV]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=1867</guid>
		<description><![CDATA[Fabric Failover is a unique capability found only in Cisco UCS that allows a server adapter to have a highly available connection to two redundant network switches without any NIC teaming drivers or any NIC failover configuration required in the OS, hypervisor, or virtual machine.  In this article we will take a brief look at [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2010/09/23/cisco-ucs-fabric-failover/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
		<item>
		<title>Simple use cases for Network Interface Virtualization</title>
		<link>http://bradhedlund.com/2009/10/23/simple-use-cases-for-network-interface-virtualization/</link>
		<comments>http://bradhedlund.com/2009/10/23/simple-use-cases-for-network-interface-virtualization/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 21:52:49 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Nexus]]></category>
		<category><![CDATA[NIV]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/?p=761</guid>
		<description><![CDATA[My most recent post Simple Example of Network Interface Virtualization generated enough interest and curosity to warrant a follow-up post showing simple uses cases for NIV. NIV takes a single physical adapter and presents multiple virtual adapters as if they were physical adapters to the server and network.  Now that the server and network see [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2009/10/23/simple-use-cases-for-network-interface-virtualization/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>A simple example of Network Interface Virtualization</title>
		<link>http://bradhedlund.com/2009/10/23/network-interface-virtualization-simple-example/</link>
		<comments>http://bradhedlund.com/2009/10/23/network-interface-virtualization-simple-example/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 17:37:56 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FCoE]]></category>
		<category><![CDATA[NIV]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/?p=749</guid>
		<description><![CDATA[I&#8217;m seeing some confusion in the blogosphere about how Cisco&#8217;s implementation of Network Interface Virtualization (NIV) really works so perhaps a very simple example is needed, and that is the intent of this post.  My previous posts about NIV with Cisco&#8217;s Palo adapter were focused on the big picture and the complete solution, such as [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2009/10/23/network-interface-virtualization-simple-example/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Cisco UCS and Nexus 1000V design diagram with Palo adapter</title>
		<link>http://bradhedlund.com/2009/08/11/cisco-ucs-nexus-1000v-design-palo-virtual-adapter/</link>
		<comments>http://bradhedlund.com/2009/08/11/cisco-ucs-nexus-1000v-design-palo-virtual-adapter/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 22:21:20 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[Cisco UCS]]></category>
		<category><![CDATA[Design Diagrams]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Nexus]]></category>
		<category><![CDATA[NIV]]></category>
		<category><![CDATA[QoS]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/?p=641</guid>
		<description><![CDATA[This is a follow-up and enhancement of a previous design diagram in which I showed Cisco UCS running the standard VMware vSwitch.  In this post I am once again showing Cisco UCS utilizing the Cisco (Palo) virtualized adapter with an implementation of VMware vSphere 4.0, however in this design we are running ESXi and the [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2009/08/11/cisco-ucs-nexus-1000v-design-palo-virtual-adapter/feed/</wfw:commentRss>
		<slash:comments>44</slash:comments>
		</item>
	</channel>
</rss>

