<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: ESX Server and the Native VLAN</title>
	<atom:link href="http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: VMware ESX, NIC Teaming, and VLAN Trunking with HP ProCurve - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</title>
		<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/comment-page-1/#comment-41198</link>
		<dc:creator>VMware ESX, NIC Teaming, and VLAN Trunking with HP ProCurve - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</dc:creator>
		<pubDate>Fri, 05 Sep 2008 15:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/#comment-41198</guid>
		<description>[...] a port can only be marked as untagged for a single VLAN). This correlates to the discussion about VMware ESX and the native VLAN, in which I reminded users that port groups intended to receive traffic for the native VLAN should [...]</description>
		<content:encoded><![CDATA[<p>[...] a port can only be marked as untagged for a single VLAN). This correlates to the discussion about VMware ESX and the native VLAN, in which I reminded users that port groups intended to receive traffic for the native VLAN should [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New VLAN Article at SearchVMware.com - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</title>
		<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/comment-page-1/#comment-40352</link>
		<dc:creator>New VLAN Article at SearchVMware.com - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</dc:creator>
		<pubDate>Wed, 06 Aug 2008 16:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/#comment-40352</guid>
		<description>[...] article published on SearchVMware.com, a VLAN article published here on my site, and the latest discussion of the use of the native VLAN, I&#8217;m trying to make sure everyone has the information they need to understand and use VLANs [...]</description>
		<content:encoded><![CDATA[<p>[...] article published on SearchVMware.com, a VLAN article published here on my site, and the latest discussion of the use of the native VLAN, I&#8217;m trying to make sure everyone has the information they need to understand and use VLANs [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miked</title>
		<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/comment-page-1/#comment-34400</link>
		<dc:creator>miked</dc:creator>
		<pubDate>Wed, 28 Nov 2007 22:13:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/#comment-34400</guid>
		<description>Its actually very simple, ...and classic. We have three zones. Public, DMZ, and Inside. I created vlan 20 for Public, 30 for DMZ, and vlan 40 for Inside. Then i created vlan dummy_vlan2, dummy_vlan3, and dummy_vlan4, then i went into the vlan database and suspended each. Then, I went to each access port (via the interface-range qualifier) and assigned the native vlan and set the vlan membership explicitly, nearly the same as you showed in your article (you showed an example of allowing all vlans). Finally, I explicited allowed only vlans 20,30, and 40 on the Trunk. 

I hope this is the appropriate place for it, but here is how I set it up, straight from the documentation I wrote.

------

+ Set up the Aggregated Ports


Set up PAGP on Switch01 side

# conf t
(config)# interface range gi 1/43 - 44
(config-if-range)# channel-group 1 mode desirable 

Set up PAGP on Switch02 side

(config)# interface range gi 1/43 - 44
(config-if-range)# channel-group 1 mode desirable 

port-channel 1 is the resulting virtual interface

The following command will verify what has been set up.
# show etherchannel summary


Set up the IEEE 802.1Q Trunk

SW02

(config)# interface port-channel 1
(config-if)# switchport trunk encapsulation dot1q
(config-if)# switchport mode trunk


SW01

(config)# interface port-channel 1
(config-if)# switchport trunk encapsulation dot1q
(config-if)# switchport mode trunk


+ Configure VTP

SW01

(config)# vtp mode server
(config)# vtp domain xxxxxxx
(config)# vtp password xxxxxxxxxxxxxxx


SW02

(config)# vtp mode server
(config)# vtp domain xxxxxxx
(config)# vtp password xxxxxxxxxxxxxxx


+ Vlan Configuration

SW01
Create Dummy VLANs

(config)# vlan 2
(config-vlan)# name dummy_vlan2
(config)# vlan 3
(config-vlan)# name dummy_vlan3
(config)# vlan 4
(config-vlan)# name dummy_vlan4
(config)# end


Suspend dummy_vlanâ€™s

#vlan database
#vlan 2 state suspend
#vlan 3 state suspend
#vlan 4 state suspend


Create Active VLANâ€™s

#vlan 20
#name PUBLIC_VLAN
#interface range 1/1 - 4
#switchport access vlan 20
#switchport trunk native vlan 2

#vlan 30
(config-vlan)#name DMZ_VLAN
(config-vlan)#interface range 1/17 - 32
(config-vlan)#switchport access vlan 30
(config-vlan)#switchport trunk native vlan 3

#vlan 40
(config-vlan)#name INSIDE_VLAN
(config-vlan)#interface range 1/33 - 35
(config-vlan)#switchport access vlan 40
(config-vlan)#switchport trunk native vlan 4


Configure Trunk Interface

(config)# interface port-channel 1
(config-if)# switchport trunk allowed vlan 20,30,40
(config-if)#end
# wr mem</description>
		<content:encoded><![CDATA[<p>Its actually very simple, &#8230;and classic. We have three zones. Public, DMZ, and Inside. I created vlan 20 for Public, 30 for DMZ, and vlan 40 for Inside. Then i created vlan dummy_vlan2, dummy_vlan3, and dummy_vlan4, then i went into the vlan database and suspended each. Then, I went to each access port (via the interface-range qualifier) and assigned the native vlan and set the vlan membership explicitly, nearly the same as you showed in your article (you showed an example of allowing all vlans). Finally, I explicited allowed only vlans 20,30, and 40 on the Trunk. </p>
<p>I hope this is the appropriate place for it, but here is how I set it up, straight from the documentation I wrote.</p>
<p>&#8212;&#8212;</p>
<p>+ Set up the Aggregated Ports</p>
<p>Set up PAGP on Switch01 side</p>
<p># conf t<br />
(config)# interface range gi 1/43 &#8211; 44<br />
(config-if-range)# channel-group 1 mode desirable </p>
<p>Set up PAGP on Switch02 side</p>
<p>(config)# interface range gi 1/43 &#8211; 44<br />
(config-if-range)# channel-group 1 mode desirable </p>
<p>port-channel 1 is the resulting virtual interface</p>
<p>The following command will verify what has been set up.<br />
# show etherchannel summary</p>
<p>Set up the IEEE 802.1Q Trunk</p>
<p>SW02</p>
<p>(config)# interface port-channel 1<br />
(config-if)# switchport trunk encapsulation dot1q<br />
(config-if)# switchport mode trunk</p>
<p>SW01</p>
<p>(config)# interface port-channel 1<br />
(config-if)# switchport trunk encapsulation dot1q<br />
(config-if)# switchport mode trunk</p>
<p>+ Configure VTP</p>
<p>SW01</p>
<p>(config)# vtp mode server<br />
(config)# vtp domain xxxxxxx<br />
(config)# vtp password xxxxxxxxxxxxxxx</p>
<p>SW02</p>
<p>(config)# vtp mode server<br />
(config)# vtp domain xxxxxxx<br />
(config)# vtp password xxxxxxxxxxxxxxx</p>
<p>+ Vlan Configuration</p>
<p>SW01<br />
Create Dummy VLANs</p>
<p>(config)# vlan 2<br />
(config-vlan)# name dummy_vlan2<br />
(config)# vlan 3<br />
(config-vlan)# name dummy_vlan3<br />
(config)# vlan 4<br />
(config-vlan)# name dummy_vlan4<br />
(config)# end</p>
<p>Suspend dummy_vlanâ€™s</p>
<p>#vlan database<br />
#vlan 2 state suspend<br />
#vlan 3 state suspend<br />
#vlan 4 state suspend</p>
<p>Create Active VLANâ€™s</p>
<p>#vlan 20<br />
#name PUBLIC_VLAN<br />
#interface range 1/1 &#8211; 4<br />
#switchport access vlan 20<br />
#switchport trunk native vlan 2</p>
<p>#vlan 30<br />
(config-vlan)#name DMZ_VLAN<br />
(config-vlan)#interface range 1/17 &#8211; 32<br />
(config-vlan)#switchport access vlan 30<br />
(config-vlan)#switchport trunk native vlan 3</p>
<p>#vlan 40<br />
(config-vlan)#name INSIDE_VLAN<br />
(config-vlan)#interface range 1/33 &#8211; 35<br />
(config-vlan)#switchport access vlan 40<br />
(config-vlan)#switchport trunk native vlan 4</p>
<p>Configure Trunk Interface</p>
<p>(config)# interface port-channel 1<br />
(config-if)# switchport trunk allowed vlan 20,30,40<br />
(config-if)#end<br />
# wr mem</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/comment-page-1/#comment-34399</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Wed, 28 Nov 2007 19:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/#comment-34399</guid>
		<description>Miked,

Thanks for your feedback. I&#039;m wondering if you&#039;d be willing to disclose a little bit of information on how the judicious use of native VLANs allowed you to accomplish your goals? It would, I think, be useful information to a lot of readers.

Thanks!</description>
		<content:encoded><![CDATA[<p>Miked,</p>
<p>Thanks for your feedback. I&#8217;m wondering if you&#8217;d be willing to disclose a little bit of information on how the judicious use of native VLANs allowed you to accomplish your goals? It would, I think, be useful information to a lot of readers.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miked</title>
		<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/comment-page-1/#comment-34398</link>
		<dc:creator>miked</dc:creator>
		<pubDate>Wed, 28 Nov 2007 17:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/#comment-34398</guid>
		<description>I also suggest use of native vlans. In our initial data center rollout for a financial company, i needed to keep costs down, so i resolved to reduce the number of high end switch hardware we bought. Using native vlans properly allowed me to do this while mitigating the &#039;vlan hopping&#039; exploit.</description>
		<content:encoded><![CDATA[<p>I also suggest use of native vlans. In our initial data center rollout for a financial company, i needed to keep costs down, so i resolved to reduce the number of high end switch hardware we bought. Using native vlans properly allowed me to do this while mitigating the &#8216;vlan hopping&#8217; exploit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremYprieS.com</title>
		<link>http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/comment-page-1/#comment-34154</link>
		<dc:creator>jeremYprieS.com</dc:creator>
		<pubDate>Wed, 14 Nov 2007 20:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/11/13/esx-server-and-the-native-vlan/#comment-34154</guid>
		<description>&lt;strong&gt;vSwitch0, Native VLANs and Host Building...&lt;/strong&gt;

I was just reading Scott&#8217;s posting regarding ESX Server and the Native VLAN.&#160; It got me started on a post to describe my logic regarding vSwitch0 design for ESX host building.&#160; 
I&#160;can tell you that I&#160;suggest native VLAN use fo...</description>
		<content:encoded><![CDATA[<p><strong>vSwitch0, Native VLANs and Host Building&#8230;</strong></p>
<p>I was just reading Scott&#8217;s posting regarding ESX Server and the Native VLAN.&nbsp; It got me started on a post to describe my logic regarding vSwitch0 design for ESX host building.&nbsp;<br />
I&nbsp;can tell you that I&nbsp;suggest native VLAN use fo&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

