<?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: Redistribution problem</title>
	<atom:link href="http://www.networkingblog.in/redistribution-problem-855/feed" rel="self" type="application/rss+xml" />
	<link>http://www.networkingblog.in/redistribution-problem-855</link>
	<description>Cisco Netpro Blog</description>
	<lastBuildDate>Wed, 23 Jun 2010 06:07:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: karan</title>
		<link>http://www.networkingblog.in/redistribution-problem-855/comment-page-1#comment-707</link>
		<dc:creator>karan</dc:creator>
		<pubDate>Wed, 03 Feb 2010 09:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkingblog.in/?p=855#comment-707</guid>
		<description>Hello,

Jon is right the reason for the issues may be that you have a daisy chain topology and devices far from the redistributing device may consider some routes as useless.

if so this means that your network is almost too big for RIP.

to be noted that Ripv2 has improvements but not on this aspect.</description>
		<content:encoded><![CDATA[<p><!--INFOLINKS_ON-->Hello,</p>
<p>Jon is right the reason for the issues may be that you have a daisy chain topology and devices far from the redistributing device may consider some routes as useless.</p>
<p>if so this means that your network is almost too big for RIP.</p>
<p>to be noted that Ripv2 has improvements but not on this aspect.<!--INFOLINKS_OFF--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arul</title>
		<link>http://www.networkingblog.in/redistribution-problem-855/comment-page-1#comment-706</link>
		<dc:creator>arul</dc:creator>
		<pubDate>Wed, 03 Feb 2010 09:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkingblog.in/?p=855#comment-706</guid>
		<description>For RIP the metric is hop count so that is what you were specifying. Each time a the traffic goes through a router the hop count is incremented by 1. A hop count of 16 is considered an unreachable network ie. you can&#039;t have a route with more than 15 hops. So it may be that by using 2 you actually managed to get to a hop count of 16 for some of the routes thus making them unreachable.

This is one of the reason why RIP is only suited to very small networks.</description>
		<content:encoded><![CDATA[<p><!--INFOLINKS_ON-->For RIP the metric is hop count so that is what you were specifying. Each time a the traffic goes through a router the hop count is incremented by 1. A hop count of 16 is considered an unreachable network ie. you can&#8217;t have a route with more than 15 hops. So it may be that by using 2 you actually managed to get to a hop count of 16 for some of the routes thus making them unreachable.</p>
<p>This is one of the reason why RIP is only suited to very small networks.<!--INFOLINKS_OFF--></p>
]]></content:encoded>
	</item>
</channel>
</rss>

