<?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: Configuring VLANs</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/configuring-vlans/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/configuring-vlans/</link>
	<description></description>
	<lastBuildDate>Thu, 20 Jun 2013 11:12:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: amykucharik</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/configuring-vlans/#comment-52019</link>
		<dc:creator>amykucharik</dc:creator>
		<pubDate>Mon, 03 Mar 2008 16:54:47 +0000</pubDate>
		<guid isPermaLink="false">#comment-52019</guid>
		<description><![CDATA[Hi Dave,
This may or may not help with your specific question, but I thought it might be good as a general reference:
&lt;a href=&quot;http://searchnetworking.techtarget.com/generic/0,295582,sid7_gci1280695,00.html&quot;&gt;Screencast: Configuring VLANs&lt;/a&gt;

It&#039;s a 15-minute automated demo of how to configure a VLAN with &lt;a href=&quot;http://itknowledgeexchange.techtarget.com/profile/Davis420&quot;&gt;David Davis&lt;/a&gt;. Enjoy!]]></description>
		<content:encoded><![CDATA[<p>Hi Dave,<br />
This may or may not help with your specific question, but I thought it might be good as a general reference:<br />
<a href="http://searchnetworking.techtarget.com/generic/0,295582,sid7_gci1280695,00.html">Screencast: Configuring VLANs</a></p>
<p>It&#8217;s a 15-minute automated demo of how to configure a VLAN with <a href="http://itknowledgeexchange.techtarget.com/profile/Davis420">David Davis</a>. Enjoy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tbitner</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/configuring-vlans/#comment-36094</link>
		<dc:creator>tbitner</dc:creator>
		<pubDate>Wed, 11 Jul 2007 13:35:16 +0000</pubDate>
		<guid isPermaLink="false">#comment-36094</guid>
		<description><![CDATA[Dave,

My remarks (possibly flawed); If you give you Vlan interfaces IP address, the L3 switch should know how to get to those directly connected networks.  Your hosts will need their gateway changed to the vlan interface IPs.  You&#039;ll need static routes for networks not directly connected.  Think of a L3 switch as a standard switch until you put IP addresses on interfaces (including virtual interfaces).  Once an interface has an IP address, it behaves like a router interface.  Make sure to turn on IP routing on the switch.  

If you stay with L2 Vlans, you&#039;ll need one trunk port (tagged for vlans) connected to a router that has sub-interfaces for each vlan to route between each vlan.  This is called &quot;router on a stick&quot;.

For the L2 switches with multiple VLANS, is each switch a separate VLAN, or multiple VLANs on multiple switches?  If the latter, yes you&#039;ll need a &quot;tagged&quot; port to trunk all the VLANS across a single link.  From my brief experience, though, I could not use more than one port a trunked on a HP switch.  

Also try looking in the HP procurve guides online,  they&#039;ll explain how HP implements VLANS.]]></description>
		<content:encoded><![CDATA[<p>Dave,</p>
<p>My remarks (possibly flawed); If you give you Vlan interfaces IP address, the L3 switch should know how to get to those directly connected networks.  Your hosts will need their gateway changed to the vlan interface IPs.  You&#8217;ll need static routes for networks not directly connected.  Think of a L3 switch as a standard switch until you put IP addresses on interfaces (including virtual interfaces).  Once an interface has an IP address, it behaves like a router interface.  Make sure to turn on IP routing on the switch.  </p>
<p>If you stay with L2 Vlans, you&#8217;ll need one trunk port (tagged for vlans) connected to a router that has sub-interfaces for each vlan to route between each vlan.  This is called &#8220;router on a stick&#8221;.</p>
<p>For the L2 switches with multiple VLANS, is each switch a separate VLAN, or multiple VLANs on multiple switches?  If the latter, yes you&#8217;ll need a &#8220;tagged&#8221; port to trunk all the VLANS across a single link.  From my brief experience, though, I could not use more than one port a trunked on a HP switch.  </p>
<p>Also try looking in the HP procurve guides online,  they&#8217;ll explain how HP implements VLANS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/8 queries in 0.048 seconds using memcached
Object Caching 283/284 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-20 12:42:26 -->