>>i can't figure out why u r using IGRP in R3, since obviously he would >>know about the routes. >>Regards, Amar."
I was testing auto-summary with different protocols and I ended up in this configuration, before remove one of the protocols. >>actually it is Eigrp that has a better AD than Igrp, 90 and 100, >>respectively, the route u see in ur table has 170 as the AD, therefore >>External EIGRP,caused by the implicit redistribution, imposed when using >>these routing protocols with the same AS. If I got that right, even if the value used in the routing table (170) is higher than the route from IGRP (100), the process will consider the route better because it is from EIGRP (90). It makes me wonder how the value 170 is applyed to the route (I know it is not sent by R2, or is it, indirectly?). "Amar KHELIFI" @groupstudy.com em 07/03/2003 21:38:07 Favor responder a "Amar KHELIFI" Enviado Por: [EMAIL PROTECTED] Para: [EMAIL PROTECTED] cc: Assunto: Re: Unexpected behavior of IGRP and EIGRP [7:64625] Hi, actually it is Eigrp that has a better AD than Igrp, 90 and 100, respectively, the route u see in ur table has 170 as the AD, therefore External EIGRP,caused by the implicit redistribution, imposed when using these routing protocols with the same AS. so u are having normal behavior of the protocols. but i can't figure out why u r using IGRP in R3, since obviously he would know about the routes. Regards, Amar. a icrit dans le message de news: [EMAIL PROTECTED] > R1 ---- R2 ---- R3 > > router R1 is running igrp process 1 > router R2 is running igrp process 1 and eigrp process 2 > router R3 is running igrp process 1 and eigrp process 2 > > R1 is running IGRP on network 10.0.0.0. > > I would expect R1 advertise router 10.0.0.0 to R2 via igrp and R2 > advertise 10.0.0.0 via igrp to R3 > > But this is the result of R3 routing table: > > R3#sh ip route > > > D 192.168.12.0/24 [90/2681856] via 192.168.23.1, 00:04:45, Serial0.32 > 3.0.0.0/24 is subnetted, 1 subnets > C 3.3.3.0 is directly connected, Loopback0 > D EX 10.0.0.0/8 [170/2809856] via 192.168.23.1, 00:04:46, Serial0.32 > C 192.168.23.0/24 is directly connected, Serial0.32 > > Debug igrp transactions shows R3 receiving news about 10.0.0.0 network, > but the route is not installed on the routing table via IGRP; as IGRP > has a better administrative cost than redistributed routes via EIGRP, I > would expect the IGRP route to be the routing table. > > R3#debu ip igrp transactions > IGRP protocol debugging is on > IP routing: > IGRP protocol debugging is on > > 00:24:24: IGRP: sending update to 255.255.255.255 via Serial0.32 > (192.168.23.2) - suppressing null update > 00:24:56: IGRP: received update from 192.168.23.1 on Serial0.32 > 00:24:56: network 192.168.12.0, metric 10476 (neighbor 8476) > 00:24:56: network 10.0.0.0, metric 10976 (neighbor 8976) > > > R1 > > interface Loopback1 > ip address 10.10.10.10 255.255.255.0 > ! > interface Serial0.12 point-to-point > ip address 192.168.12.1 255.255.255.0 > frame-relay interface-dlci 112 > ! > router igrp 1 > network 10.0.0.0 > network 192.168.12.0 > > R2 > > interface Loopback0 > ip address 2.2.2.2 255.255.255.0 > ! > interface Serial0.21 point-to-point > ip address 192.168.12.2 255.255.255.0 > no ip directed-broadcast > frame-relay interface-dlci 121 > ! > interface Serial0.23 point-to-point > ip address 192.168.23.1 255.255.255.0 > no ip directed-broadcast > frame-relay interface-dlci 123 > ! > router eigrp 1 > network 192.168.23.0 > ! > router igrp 1 > network 192.168.12.0 > network 192.168.23.0 > > R3 > > interface Serial0.32 point-to-point > ip address 192.168.23.2 255.255.255.0 > frame-relay interface-dlci 132 > ! > router eigrp 1 > network 192.168.23.0 > no eigrp log-neighbor-changes > ! > router igrp 1 > network 192.168.23.0 > > Any Thoughts? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=64925&t=64625 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
