<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Route Summarization</title>
	<atom:link href="http://ciscotips.wordpress.com/2006/05/12/route-summarization/feed/" rel="self" type="application/rss+xml" />
	<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/</link>
	<description>Make life easy for Cisco Engineers</description>
	<lastBuildDate>Sat, 02 Jan 2010 05:56:13 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JB</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3580</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Thu, 08 Oct 2009 16:40:42 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3580</guid>
		<description>Because the first 6 digits (including leading zeros) in the first octet are all the same for each network (8,9,10,11), the mask would be 

11111100.00000000.00000000.00000000 or
252.0.0.0</description>
		<content:encoded><![CDATA[<p>Because the first 6 digits (including leading zeros) in the first octet are all the same for each network (8,9,10,11), the mask would be </p>
<p>11111100.00000000.00000000.00000000 or<br />
252.0.0.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amit</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3564</link>
		<dc:creator>amit</dc:creator>
		<pubDate>Wed, 02 Sep 2009 05:40:50 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3564</guid>
		<description>is root summarization and supernetting same????


if not then why????</description>
		<content:encoded><![CDATA[<p>is root summarization and supernetting same????</p>
<p>if not then why????</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shyam kumar Pundir</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3390</link>
		<dc:creator>Shyam kumar Pundir</dc:creator>
		<pubDate>Thu, 25 Sep 2008 06:44:05 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3390</guid>
		<description>What is route summerization and how is work on routing protocol.</description>
		<content:encoded><![CDATA[<p>What is route summerization and how is work on routing protocol.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: faisal</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3361</link>
		<dc:creator>faisal</dc:creator>
		<pubDate>Tue, 08 Jul 2008 08:52:51 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3361</guid>
		<description>kindly favour me to understand the summerization of rputer IP</description>
		<content:encoded><![CDATA[<p>kindly favour me to understand the summerization of rputer IP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Shafer</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3350</link>
		<dc:creator>Mike Shafer</dc:creator>
		<pubDate>Mon, 26 May 2008 19:50:13 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3350</guid>
		<description>To continue on the above it appears that it&#039;s a RIP thing in not allowing summarization less than the classful boundary.

I took my above configuration and changed it over to EIGRP and all worked just dandy! That is I was able to summarize the Class A addresses on the S1/0 interface using:

p1R7(config-if)#ip summary-address eigrp 100 8.0.0.0 252.0.0.0

and the routes were summarized on the routing table on R21 as expected showing:

D    8.0.0.0/6 [90/2323456] via 172.16.1.2, 00:00:15, Serial0 

If anyone knows how to accomplish this using RIP v2 I would appreciate you&#039;re letting me know. I&#039;m taking the BSCI exam in the near future and it&#039;s *my* $150 down the drain if I crash and burn! :)

Cheers!

MS</description>
		<content:encoded><![CDATA[<p>To continue on the above it appears that it&#8217;s a RIP thing in not allowing summarization less than the classful boundary.</p>
<p>I took my above configuration and changed it over to EIGRP and all worked just dandy! That is I was able to summarize the Class A addresses on the S1/0 interface using:</p>
<p>p1R7(config-if)#ip summary-address eigrp 100 8.0.0.0 252.0.0.0</p>
<p>and the routes were summarized on the routing table on R21 as expected showing:</p>
<p>D    8.0.0.0/6 [90/2323456] via 172.16.1.2, 00:00:15, Serial0 </p>
<p>If anyone knows how to accomplish this using RIP v2 I would appreciate you&#8217;re letting me know. I&#8217;m taking the BSCI exam in the near future and it&#8217;s *my* $150 down the drain if I crash and burn! <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Cheers!</p>
<p>MS</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Shafer</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3349</link>
		<dc:creator>Mike Shafer</dc:creator>
		<pubDate>Mon, 26 May 2008 18:39:55 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3349</guid>
		<description>Small Correction: (this should not be on R4)
If I redo this using
p1R4(config-if)#ip summary-address rip 8.0.0.0 255.0.0.0

Should read: (but on R7)
If I redo this using
p1R7(config-if)#ip summary-address rip 8.0.0.0 255.0.0.0</description>
		<content:encoded><![CDATA[<p>Small Correction: (this should not be on R4)<br />
If I redo this using<br />
p1R4(config-if)#ip summary-address rip 8.0.0.0 255.0.0.0</p>
<p>Should read: (but on R7)<br />
If I redo this using<br />
p1R7(config-if)#ip summary-address rip 8.0.0.0 255.0.0.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Shafer</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3348</link>
		<dc:creator>Mike Shafer</dc:creator>
		<pubDate>Mon, 26 May 2008 18:33:29 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3348</guid>
		<description>Hi,

Curious as to what I&#039;m missing here as I set up a simulation of this in my lab. I have a router 7 (3640-ios 12.4) configured with 4 Ethernet interfaces with each connecting to a corresponding Ethernet interface on another router (routers 1-4) for five routers total.

For simplicity all routers are running
router rip
no auto
vers 2
net 192.168.0.0
net xxxx (as appropriate for the ip of lo0)

and router R7 has the addition of
net 172.16.0.0 to handle the serial connection to R21

On routers 1-4 I configured loopback0 as 
R1: 8.8.8.8/8
R2: 9.9.9.9/8
R3: 10.10.10.10/8
R4: 11.11.11.11/8

I then have S1/0 (IP 172.16.1.2/30) on R7 acting as the outbound connection to S0 (IP 172.16.1.1/30) on my primary router (R21) that connects to my LAN and is the gateway router to the firewall and Internet.

I have the routers R1-R4 divided as various subnets of the address space 192.168.0.0/24. When I summarize this on the S1/0 interface as: #ip summary-address rip 192.168.0.0 255.255.255.0

it acts as expected and the routing table on R21 shows

R    192.168.0.0/24 [120/1] via 172.16.1.2, 00:00:09, Serial0

and all the various subnetted interfaces can be successfully pinged from R21.

However:
If I also try to summarize the loopback interfaces on S1/0 I get:
p1R4(config-if)#ip summary-address rip 8.0.0.0 252.0.0.0
 Summary mask must be greater or equal to major net

If I redo this using
p1R4(config-if)#ip summary-address rip 8.0.0.0 255.0.0.0

the router is happy but of course this doesn&#039;t summarize the address space of 8.0.0.0/8-11.0.0.0/8


What am I missing/need to change to get this working?

TIA!

Cheers!

Mike Shafer</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Curious as to what I&#8217;m missing here as I set up a simulation of this in my lab. I have a router 7 (3640-ios 12.4) configured with 4 Ethernet interfaces with each connecting to a corresponding Ethernet interface on another router (routers 1-4) for five routers total.</p>
<p>For simplicity all routers are running<br />
router rip<br />
no auto<br />
vers 2<br />
net 192.168.0.0<br />
net xxxx (as appropriate for the ip of lo0)</p>
<p>and router R7 has the addition of<br />
net 172.16.0.0 to handle the serial connection to R21</p>
<p>On routers 1-4 I configured loopback0 as<br />
R1: 8.8.8.8/8<br />
R2: 9.9.9.9/8<br />
R3: 10.10.10.10/8<br />
R4: 11.11.11.11/8</p>
<p>I then have S1/0 (IP 172.16.1.2/30) on R7 acting as the outbound connection to S0 (IP 172.16.1.1/30) on my primary router (R21) that connects to my LAN and is the gateway router to the firewall and Internet.</p>
<p>I have the routers R1-R4 divided as various subnets of the address space 192.168.0.0/24. When I summarize this on the S1/0 interface as: #ip summary-address rip 192.168.0.0 255.255.255.0</p>
<p>it acts as expected and the routing table on R21 shows</p>
<p>R    192.168.0.0/24 [120/1] via 172.16.1.2, 00:00:09, Serial0</p>
<p>and all the various subnetted interfaces can be successfully pinged from R21.</p>
<p>However:<br />
If I also try to summarize the loopback interfaces on S1/0 I get:<br />
p1R4(config-if)#ip summary-address rip 8.0.0.0 252.0.0.0<br />
 Summary mask must be greater or equal to major net</p>
<p>If I redo this using<br />
p1R4(config-if)#ip summary-address rip 8.0.0.0 255.0.0.0</p>
<p>the router is happy but of course this doesn&#8217;t summarize the address space of 8.0.0.0/8-11.0.0.0/8</p>
<p>What am I missing/need to change to get this working?</p>
<p>TIA!</p>
<p>Cheers!</p>
<p>Mike Shafer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3309</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Thu, 20 Mar 2008 21:41:34 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3309</guid>
		<description>Josef,
252.0.0.0 is the correct mask. If you used 248.0.0.0, it would also include the networks 12.0.0.0/8, 13.0.0.0/8, 14.0.0.0/8, and 15.0.0.0/8.</description>
		<content:encoded><![CDATA[<p>Josef,<br />
252.0.0.0 is the correct mask. If you used 248.0.0.0, it would also include the networks 12.0.0.0/8, 13.0.0.0/8, 14.0.0.0/8, and 15.0.0.0/8.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joao Costa</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3283</link>
		<dc:creator>Joao Costa</dc:creator>
		<pubDate>Tue, 05 Feb 2008 01:26:46 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3283</guid>
		<description>There is a tutorial on how to get summary routes at http://searchwarp.com/swa45047.htm</description>
		<content:encoded><![CDATA[<p>There is a tutorial on how to get summary routes at <a href="http://searchwarp.com/swa45047.htm" rel="nofollow">http://searchwarp.com/swa45047.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josef</title>
		<link>http://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3274</link>
		<dc:creator>Josef</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:20:31 +0000</pubDate>
		<guid isPermaLink="false">https://ciscotips.wordpress.com/2006/05/12/route-summarization/#comment-3274</guid>
		<description>In the first paragraph, wouldn&#039;t the route mask be 248.0.0.0?</description>
		<content:encoded><![CDATA[<p>In the first paragraph, wouldn&#8217;t the route mask be 248.0.0.0?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
