<?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>The Journey of a Network Engineer &#187; scheme</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/network-engineering-journey/tag/scheme/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/network-engineering-journey</link>
	<description></description>
	<lastBuildDate>Tue, 26 Feb 2013 11:05:07 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>From trunk ports to routed ports &#8211; part 2</title>
		<link>http://itknowledgeexchange.techtarget.com/network-engineering-journey/from-trunk-ports-to-routed-ports-part-2/</link>
		<comments>http://itknowledgeexchange.techtarget.com/network-engineering-journey/from-trunk-ports-to-routed-ports-part-2/#comments</comments>
		<pubDate>Wed, 27 Oct 2010 08:46:28 +0000</pubDate>
		<dc:creator>Sulaiman Syed</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[core]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[distribution]]></category>
		<category><![CDATA[ip]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[routed]]></category>
		<category><![CDATA[scheme]]></category>
		<category><![CDATA[subnet]]></category>
		<category><![CDATA[trunk]]></category>
		<category><![CDATA[vlan]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/network-engineering-journey/from-trunk-ports-to-routed-ports-part-2/</guid>
		<description><![CDATA[In this part, I would talk bout the migration from current network, to the proposed network. Figure 1 shows a core layer with two distribution layer, the one on the left is current, and the one on the right is the proposed. Before explaining any further, take note that although user vlans were local (shouldn&#8217;t [...]]]></description>
				<content:encoded><![CDATA[<p>In this part, I would talk bout the migration from current network, to the proposed network.</p>
<p>Figure 1 shows a core layer with two distribution layer, the one on the left is current, and the one on the right is the proposed. Before explaining any further, take note that although user vlans were local (shouldn&#8217;t span to core and other distribution) they were spanning cause of some poor configuration.</p>
<p><a href="http://s116.photobucket.com/albums/o35/night_wolf_in/Blog/?action=view&amp;current=Routedlinks.jpg" target="_blank"><img src="http://i116.photobucket.com/albums/o35/night_wolf_in/Blog/Routedlinks.jpg" border="0" alt="Routed,Cisco,Ports" /></a></p>
<p>The core network will have ip address of 10.0.y.x/16 where y = 0 for core layer, and x = host number/id. The distribution layer follow the scheme of 10.0.y.x/16, where y = distribution switch location, x = host number/id. access switches will have same scheme as distribution just their x will start from 100.</p>
<p>The objective is to migrate to routed ports without loosing connectivity in management vlan and providing a good summary for routing table. This is possible by following the design on the right side of the figure. Change the subnet mask from /16 to /24 from distribution layer and lower. The routed ports will have IP address from the last subnet of the user vlans. The user vlan IP scheme follows as 10.y.x.z/24 where y is distribution switch location, x is vlan number, z is host id.  so for first distribution switch the following subnets were allocated for the routed ports. 10.1.255.255/31 and 10.1.255.252/31. second distribution switch used subnets 10.1.255.250/31 and 10.1.255.248/31.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/network-engineering-journey/from-trunk-ports-to-routed-ports-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
