<?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: Introduction to Cisco VLANs</title>
	<atom:link href="http://www.techhead.co.uk/introduction-to-cisco-vlans/feed" rel="self" type="application/rss+xml" />
	<link>http://www.techhead.co.uk/introduction-to-cisco-vlans</link>
	<description>TechHead.co.uk is a site dedicated to information on various IT technologies, solutions, fixes and IT news. Topic areas include HP Proliant Servers &#38; Storage, VMware vSphere,ESX,ESXi, Microsoft Hyper V and Windows Server</description>
	<lastBuildDate>Sat, 04 Feb 2012 18:50:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Jon Langemak</title>
		<link>http://www.techhead.co.uk/introduction-to-cisco-vlans#comment-13083</link>
		<dc:creator>Jon Langemak</dc:creator>
		<pubDate>Fri, 26 Aug 2011 01:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.techhead.co.uk/?p=4183#comment-13083</guid>
		<description>@Sergey

Thanks for the comment!  A couple of points...

Inter VLAN communication with SVIs is perhaps the easiest means to communicate between VLANs (In my mind).  Configure the VLANs, add interfaces, and make sure the switch has &#039;ip routing&#039; turned on.  Clients who point to SVI as their default gateway can talk to any other VLAN since the switch sees the other interfaces as &#039;directly connected&#039;

In regards to the &#039;General&#039; VLAN you reference.  Sounds a lot like the native VLAN that Cisco has been using since the beginning.  The native VLAN is sort of like its own little VLAN in many ways.  Good network design means that you dont use the native VLAN but like any other VLAN, if it has a SVI it cant talk layer 3 to any other VLAN with an SVI if security allows it to do so.

Thanks! - Jon</description>
		<content:encoded><![CDATA[<p>@Sergey</p>
<p>Thanks for the comment!  A couple of points&#8230;</p>
<p>Inter VLAN communication with SVIs is perhaps the easiest means to communicate between VLANs (In my mind).  Configure the VLANs, add interfaces, and make sure the switch has &#8216;ip routing&#8217; turned on.  Clients who point to SVI as their default gateway can talk to any other VLAN since the switch sees the other interfaces as &#8216;directly connected&#8217;</p>
<p>In regards to the &#8216;General&#8217; VLAN you reference.  Sounds a lot like the native VLAN that Cisco has been using since the beginning.  The native VLAN is sort of like its own little VLAN in many ways.  Good network design means that you dont use the native VLAN but like any other VLAN, if it has a SVI it cant talk layer 3 to any other VLAN with an SVI if security allows it to do so.</p>
<p>Thanks! &#8211; Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergey</title>
		<link>http://www.techhead.co.uk/introduction-to-cisco-vlans#comment-13064</link>
		<dc:creator>Sergey</dc:creator>
		<pubDate>Wed, 24 Aug 2011 17:45:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.techhead.co.uk/?p=4183#comment-13064</guid>
		<description>Hi Jon,

Having Layer 3 for inter-VLAN communications involved, has always been a pain to configure and support.

With acquisition of Linksys, Cisco has introduced new VLAN mode on the switches: General. In this mode one switch port could have multiple untagged VLANs associated. And that would have a great consequences in creation of separated segments with a shared resources on a FLAT IP network - yes - all connected devices would have the same IP network address and network mask. The shared resources like servers, printers, Internet routers would be connected to such General VLAN ports and able to communicate within any VLANs defined as Untagged. And still, Access VLAN ports would connect end-user computers, which will be separated into a segments accordingly to their VLAN ids.

How would you comment that?

Thank you.

Sergey

P.S. It looks like Netgear devices have that functionality too.</description>
		<content:encoded><![CDATA[<p>Hi Jon,</p>
<p>Having Layer 3 for inter-VLAN communications involved, has always been a pain to configure and support.</p>
<p>With acquisition of Linksys, Cisco has introduced new VLAN mode on the switches: General. In this mode one switch port could have multiple untagged VLANs associated. And that would have a great consequences in creation of separated segments with a shared resources on a FLAT IP network &#8211; yes &#8211; all connected devices would have the same IP network address and network mask. The shared resources like servers, printers, Internet routers would be connected to such General VLAN ports and able to communicate within any VLANs defined as Untagged. And still, Access VLAN ports would connect end-user computers, which will be separated into a segments accordingly to their VLAN ids.</p>
<p>How would you comment that?</p>
<p>Thank you.</p>
<p>Sergey</p>
<p>P.S. It looks like Netgear devices have that functionality too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.techhead.co.uk/introduction-to-cisco-vlans#comment-11533</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 29 Sep 2010 17:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.techhead.co.uk/?p=4183#comment-11533</guid>
		<description>Thanks Jon.  Great article.  I&#039;m Brand new to networking and am researching how to correct overlap errors on my Cisco 3750 when trying to create a second VLAN.  This article did shed some light on the issue for me.</description>
		<content:encoded><![CDATA[<p>Thanks Jon.  Great article.  I&#8217;m Brand new to networking and am researching how to correct overlap errors on my Cisco 3750 when trying to create a second VLAN.  This article did shed some light on the issue for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.techhead.co.uk/introduction-to-cisco-vlans#comment-11493</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 22 Sep 2010 17:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.techhead.co.uk/?p=4183#comment-11493</guid>
		<description>Great writeup - understandable and comprehensive at the same time.

Thanks!</description>
		<content:encoded><![CDATA[<p>Great writeup &#8211; understandable and comprehensive at the same time.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Techhead Guest Post!</title>
		<link>http://www.techhead.co.uk/introduction-to-cisco-vlans#comment-10502</link>
		<dc:creator>&#187; Techhead Guest Post!</dc:creator>
		<pubDate>Sat, 27 Mar 2010 18:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.techhead.co.uk/?p=4183#comment-10502</guid>
		<description>[...] TechHead – VMWare, Virtualization, Virtualisation, HP &amp; Microsoft Related IT Blog http://www.techhead.co.uk/introduction-to-cisco-vlans  [...]</description>
		<content:encoded><![CDATA[<p>[...] TechHead – VMWare, Virtualization, Virtualisation, HP &amp; Microsoft Related IT Blog <a href="http://www.techhead.co.uk/introduction-to-cisco-vlans" rel="nofollow">http://www.techhead.co.uk/introduction-to-cisco-vlans</a>  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forbes Guthrie</title>
		<link>http://www.techhead.co.uk/introduction-to-cisco-vlans#comment-10329</link>
		<dc:creator>Forbes Guthrie</dc:creator>
		<pubDate>Tue, 16 Mar 2010 23:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.techhead.co.uk/?p=4183#comment-10329</guid>
		<description>Nice write up Jon,
I&#039;d love to see a follow-up article on PVLANs, primary/secondary, promiscuous/community/isolated.  These are new networking terms for the VMware audience here, and a more generic, real-world networking explanation like you provided above, would be very valuable.
Anyway, nice article. Thanks.</description>
		<content:encoded><![CDATA[<p>Nice write up Jon,<br />
I&#8217;d love to see a follow-up article on PVLANs, primary/secondary, promiscuous/community/isolated.  These are new networking terms for the VMware audience here, and a more generic, real-world networking explanation like you provided above, would be very valuable.<br />
Anyway, nice article. Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

Served from: www.techhead.co.uk @ 2012-02-07 08:59:31 -->
