<?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>Virtualization Adapted &#187; network</title>
	<atom:link href="http://www.vadapt.com/tag/network/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vadapt.com</link>
	<description>Adapting Business Processes for Virtual Infrastrcuture (and vice-versa)</description>
	<lastBuildDate>Wed, 14 Jul 2010 00:36:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Host Profiles N1KV VDS</title>
		<link>http://www.vadapt.com/2010/03/232/</link>
		<comments>http://www.vadapt.com/2010/03/232/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 13:21:04 +0000</pubDate>
		<dc:creator>iben</dc:creator>
				<category><![CDATA[virtualization]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[cli]]></category>
		<category><![CDATA[enterprise plus]]></category>
		<category><![CDATA[esxtop]]></category>
		<category><![CDATA[host profiles]]></category>
		<category><![CDATA[n1kv]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[nexus]]></category>
		<category><![CDATA[vds]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vNetwork]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.vadapt.com/2010/03/232/</guid>
		<description><![CDATA[Applying NIC Teaming Policies to DV Port Groups With a vSS, NIC teaming policies are defined on the virtual switch with an optional override on each Port Group definition.  With vDS, NIC teaming policies are only defined on the DV Port Groups and apply to dvUplinks, not vmnics.  The vmnics are mapped to the dvUplinks on a per host basis.  This enables each host to have a different vmnic to physical host configuration and yet use the same NIC teaming policy over all hosts spanned by the vDS.]]></description>
		<wfw:commentRss>http://www.vadapt.com/2010/03/232/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>vSphere Network Connections and Ports</title>
		<link>http://www.vadapt.com/2010/03/vsphere-network-connections-and-ports/</link>
		<comments>http://www.vadapt.com/2010/03/vsphere-network-connections-and-ports/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 18:57:01 +0000</pubDate>
		<dc:creator>iben</dc:creator>
				<category><![CDATA[virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.vadapt.com/?p=209</guid>
		<description><![CDATA[The amazing Dudley Smith, from VMware&#8217;s Technical Account Manager team has release a larger version of his vSphere Network Connections and Ports for ESX diagram and an accompanying excel spreadsheet listing all the TCP/IP ports for various communication purposes. Get them directly from the VMware blog site here: http://communities.vmware.com/blogs/dudleysmith Add this to 100 bookmarks Share this on [...]]]></description>
		<wfw:commentRss>http://www.vadapt.com/2010/03/vsphere-network-connections-and-ports/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>vmxnet3 &#8211; features and use information &#8211; tips and tricks</title>
		<link>http://www.vadapt.com/2009/05/vmxnet3/</link>
		<comments>http://www.vadapt.com/2009/05/vmxnet3/#comments</comments>
		<pubDate>Wed, 06 May 2009 07:01:34 +0000</pubDate>
		<dc:creator>iben</dc:creator>
				<category><![CDATA[virtualization]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vmxnet]]></category>
		<category><![CDATA[vmxnet3]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.vadapt.com/?p=96</guid>
		<description><![CDATA[How to remove these “phantom” NICs from Windows.
How to improve VMware Virtual Machine Guest performance and reduce CPU utilization.]]></description>
		<wfw:commentRss>http://www.vadapt.com/2009/05/vmxnet3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>NMAP tricks</title>
		<link>http://www.vadapt.com/2009/04/nmap-tricks/</link>
		<comments>http://www.vadapt.com/2009/04/nmap-tricks/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 05:49:31 +0000</pubDate>
		<dc:creator>iben</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[count]]></category>
		<category><![CDATA[ip address]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[nmap]]></category>
		<category><![CDATA[scan]]></category>

		<guid isPermaLink="false">http://www.vadapt.com/2009/04/nmap-tricks/</guid>
		<description><![CDATA[How to use NMAP to count the number of hosts on a given subnet. #!/bin/bash echo 4192 > /proc/sys/net/ipv4/neigh/default/gc_thresh3 nmap -sP -PI $1 -n &#8211;max_rtt_timeout 5000 &#8211;initial_rtt_timeout 5000 &#124; tail -1 &#124; cut -f 2 -d &#8220;(&#8221; &#124; cut -f 1 -d &#8221; &#8221; 2> /dev/null (Thanks to Gabriel for this one!) Add this to [...]]]></description>
		<wfw:commentRss>http://www.vadapt.com/2009/04/nmap-tricks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
