<?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: Secondary address.</title>
	<atom:link href="http://www.networkingblog.in/secondary-address-2889/feed" rel="self" type="application/rss+xml" />
	<link>http://www.networkingblog.in/secondary-address-2889</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: Kumar</title>
		<link>http://www.networkingblog.in/secondary-address-2889/comment-page-1#comment-2022</link>
		<dc:creator>Kumar</dc:creator>
		<pubDate>Mon, 15 Mar 2010 12:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkingblog.in/?p=2889#comment-2022</guid>
		<description>There is another aspect of secondary addresses which you should be aware of and which does impact using secondary addresses with routing protocols including EIGRP. The routing updates (and the EIGRP HELLO messages) have their source address as the primary address and not the secondary address. So EIGRP can not form neighbor relationships using the secondary addresses. This means that all routers on that segment must have primary addresses in the same subnet, and configure EIGRP to use both the primary address and the secondary address. If you do not do this EIGRP will not be able to form neighbor relationship and will not advertise routes.</description>
		<content:encoded><![CDATA[<p><!--INFOLINKS_ON-->There is another aspect of secondary addresses which you should be aware of and which does impact using secondary addresses with routing protocols including EIGRP. The routing updates (and the EIGRP HELLO messages) have their source address as the primary address and not the secondary address. So EIGRP can not form neighbor relationships using the secondary addresses. This means that all routers on that segment must have primary addresses in the same subnet, and configure EIGRP to use both the primary address and the secondary address. If you do not do this EIGRP will not be able to form neighbor relationship and will not advertise routes.<!--INFOLINKS_OFF--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: karan</title>
		<link>http://www.networkingblog.in/secondary-address-2889/comment-page-1#comment-2021</link>
		<dc:creator>karan</dc:creator>
		<pubDate>Mon, 15 Mar 2010 12:44:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkingblog.in/?p=2889#comment-2021</guid>
		<description>There are 2 disadvantages I can think of, though neither are really specific to EIGRP.
1. Traffic between the 2 subnets has to pass through the router even though they are in the same broadcast domain. This &quot;one-armed&quot; routing is probably not a big deal unless there is a huge amount of traffic between the subnets.
2. You can&#039;t use DHCP via ip helper addresses for PCs in the secondary subnet. The router will always use the primary subnet when it relays the DHCP request to the  DHCP server.</description>
		<content:encoded><![CDATA[<p><!--INFOLINKS_ON-->There are 2 disadvantages I can think of, though neither are really specific to EIGRP.<br />
1. Traffic between the 2 subnets has to pass through the router even though they are in the same broadcast domain. This &#8220;one-armed&#8221; routing is probably not a big deal unless there is a huge amount of traffic between the subnets.<br />
2. You can&#8217;t use DHCP via ip helper addresses for PCs in the secondary subnet. The router will always use the primary subnet when it relays the DHCP request to the  DHCP server.<!--INFOLINKS_OFF--></p>
]]></content:encoded>
	</item>
</channel>
</rss>

