Re: IGRP to EIGRP question

From: Stephen C. Feldberg (scfeldberg@xxxxxxxxxxx)
Date: Mon Jan 07 2002 - 11:37:13 GMT-3


   
When the 10.1.1.3/24 and 200.0.0.3/32 routes are advertised to their IGRP
peers over a (sub)network (the subnet used for your serial connections) that
does not fall under either 10.0.0.0/8 or 200.0.0.0/24, you will see the
classful behavior of IGRP - subnets will be summarized to their classful
networks prior to being advertised to the peers.

If, for example, the serial connection to R2 was 10.1.2.0/24, IGRP would not
summarize the 10.1.1.3/24 route into 10.0.0.0/8 - it would be advertised to
the peer as 10.1.2.0/24. The 200.0.0.3/32 would still be summarized to
200.0.0.0/24.

You also want to make sure that your R1 and R2 routers EIGRP processes are
not summarizing the routes (no auto-summary).

Steve
----- Original Message -----
From: <Giveortake@aol.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, January 06, 2002 11:29 PM
Subject: IGRP to EIGRP question

> Three routers R1 -R2- R3 connected via Serials
>
> R3 runs IGRP 2 only
> R2 runs EIGRP 1 and IGRP 2 and redistributes back and forth between them.
> R1 runs EIGRP 1 only
>
> R3 has Eth 0 that has IP address of 10.1.1.3/24
> R4 has Loopback 0 that has IP address 200.0.0.3/32
>
> When you look at routing table of R2 & R1 they show an external route of
> 10.0.0.0/8 and a 200.0.0.0/24. I know this is due to IGRP Classfull
routing
> protocal. The question is, is there a way to make it show up on R2 & R1
as
> the true 10.1.1.0/24 and 200.0.0.3/32 that it is?
>
> This is pulled more or less out of IPexpert IGRP-EIGRP lab. All my
routers
> (there are others in the scenerio I just didnt put them in to cloud the
> issue) are able to ping all my other routers and my solution is matching
that
> which IpExpert has, just concerned that I should be trying to get that
> 10.1.1.0/24 and the 200.0.0.4/32 to propagate to R2 & R1 as that which
they
> really are vs their classess.....
>
> David



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:18 GMT-3