<?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>VM-Aware &#187; Networking</title>
	<atom:link href="http://www.vm-aware.com/category/networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vm-aware.com</link>
	<description>Server, Storage &#38; Application Virtualisation!</description>
	<lastBuildDate>Thu, 03 Mar 2011 11:28:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How To Virtualise DMZs Well</title>
		<link>http://www.vm-aware.com/2008/07/how-to-virtualise-dmzs-well/</link>
		<comments>http://www.vm-aware.com/2008/07/how-to-virtualise-dmzs-well/#comments</comments>
		<pubDate>Mon, 21 Jul 2008 16:01:13 +0000</pubDate>
		<dc:creator>Paul Shannon</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualisation]]></category>

		<guid isPermaLink="false">http://www.vm-aware.com/?p=154</guid>
		<description><![CDATA[VMware have released a Best Practice guide for DMZ implementations in a VMware ESX infrastructure.
It outlines the three main implementation routes and discusses the advantages and disadvantages below:
Partially Collapsed DMZ with Separate Physical Trust Zones
Advantages

Simpler, less complex configuration
Less change to physical environment
Less change to separation of duties
Less change in staff knowledge requirements
Less chance for misconfiguration [...]]]></description>
			<content:encoded><![CDATA[<p>VMware have released a Best Practice guide for DMZ implementations in a VMware ESX infrastructure.</p>
<p>It outlines the three main implementation routes and discusses the advantages and disadvantages below:<span id="more-154"></span></p>
<p><strong>Partially Collapsed DMZ with Separate Physical Trust Zones</strong></p>
<p><em>Advantages</em></p>
<ul>
<li>Simpler, less complex configuration</li>
<li>Less change to physical environment</li>
<li>Less change to separation of duties</li>
<li>Less change in staff knowledge requirements</li>
<li>Less chance for misconfiguration because of lower complexity</li>
</ul>
<p><em>Disadvantages</em></p>
<ul>
<li>Lower consolidation and utilization of resources</li>
<li>Higher costs because of need for more ESX hosts and additional cooling and power</li>
<li>Incomplete utilization of the advantages of virtualization</li>
</ul>
<p><strong>Partially Collapsed DMZ with Virtual Separation of Trust Zones</strong></p>
<p><em>Advantages</em></p>
<ul>
<li>Full utilization of resources</li>
<li>Full utilization of the advantages of virtualization</li>
<li>Lower cost</li>
</ul>
<p><em>Disadvantages<br />
</em></p>
<ul>
<li>More complexity</li>
<li>Greater chance of misconfiguration requires explicit configuration of separation of duties to help mitigate risk of misconfiguration</li>
<li>requires regular audits of configurations</li>
</ul>
<p><strong>Fully Collapsed DMZ</strong></p>
<p><em>Advantages</em></p>
<ul>
<li>Full utilization of resources, replacing physical security devices with virtual</li>
<li>Lowest-cost option</li>
<li>Management of entire DMZ and network from a single management workstation</li>
</ul>
<p><em>Disadvantages</em></p>
<ul>
<li>Greatest complexity, which in turn creates highest chance of misconfiguration</li>
<li>Requirement for explicit configuration of separation of duties to help mitigate risk of misconfiguration</li>
<li>Requires regular audits of configurations</li>
<li>Loss of certain functionality, such as VMotion, if current virtual security appliances are not properly configured and audited</li>
</ul>
<p>Download it <a title="DMZ Best Practices" href="http://www.vmware.com/files/pdf/dmz_virtualization_vmware_infra_wp.pdf" target="_blank">here</a> as there is a lot of information here, to get your teeth into.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vm-aware.com/2008/07/how-to-virtualise-dmzs-well/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ESX With Nortel Switch VLANs</title>
		<link>http://www.vm-aware.com/2008/07/esx-with-nortel-switch-vlans/</link>
		<comments>http://www.vm-aware.com/2008/07/esx-with-nortel-switch-vlans/#comments</comments>
		<pubDate>Mon, 21 Jul 2008 16:01:09 +0000</pubDate>
		<dc:creator>Paul Shannon</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualisation]]></category>
		<category><![CDATA[Nortel]]></category>
		<category><![CDATA[Service Console]]></category>

		<guid isPermaLink="false">http://www.vm-aware.com/?p=144</guid>
		<description><![CDATA[For all of you out there that have recently started buying the Nortel layer 2-7 Switch Modules for your IBM BladeCenter H because they can be cheaper than there Cisco counterpart with more functionality, check out this article.
It points out how to resolve some of the issues that you may be having with VLANs and [...]]]></description>
			<content:encoded><![CDATA[<p>For all of you out there that have recently started buying the <a title="Nortel BC Switch" href="http://www-03.ibm.com/systems/bladecenter/hardware/openfabric/ethernet.html" target="_blank">Nortel layer 2-7 Switch Modules</a> for your IBM BladeCenter H because they can be cheaper than there Cisco counterpart with more functionality, check out this <a title="Nortel &amp; ESX VLANs" href="http://blog.scottlowe.org/2008/06/24/vlans-on-esx-with-nortel-switches/" target="_blank">article</a>.</p>
<p>It points out how to resolve some of the issues that you may be having with VLANs and ESX.  The crux being that by default the Nortel Switch will tag the default VLAN so unless the Service Console is configured with the same VLAN tag, then things get messy.  A simple checkbox is all that is required to fix this problem, but check out the <a title="Nortel &amp; ESX VLANs" href="http://blog.scottlowe.org/2008/06/24/vlans-on-esx-with-nortel-switches/" target="_blank">article</a> for more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vm-aware.com/2008/07/esx-with-nortel-switch-vlans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

