Rajesh,

As far as r4 is concerned, you should see the network as being directly
connected via loopback0 in the routing table and not learned from IGRP.
Also, I'm wondering why you have IGRP turned on for the 200.0.0.0 network
and are resdistributing connected.  With just the 200 defined in IGRP, R2
should learned about that network. I think you may be having issues with the
have that you have both the network statement for that network and also the
redistribution of connected.  Try removing the redistribution command. Or
maybe i'm completely off, in either case, hopefully others will respond.


Tim

-----Original Message-----
From: Rajesh Kumar [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 12:36 PM
To: [EMAIL PROTECTED]
Subject: Advertising loopback interfaces via IGRP. [7:32498]


Hi all,

The scenario is this :

                    R2------------------------R3-------------------R4


        R3 is a FR switch between 2 DTE devices R2 and R4.

R4 is having a loopback interface, ethernet interface and a serial
interface.  I am running IGRP 2 on R4 on loopback and serial
interfaces.  I have not included the ethernet interface in the config.

Assume, I have assigned the IP for the loopback as 200.0.0.4/32

The config is this :

router igrp 2
net 150.50.0.0
net 200.0.0.0
redis connected
default-metric 64 1000 255 1 1500


When I issued "sh ip route" in R4 : sometimes the loopback interface is
advertised as IGRP route properly and sometimes it shows "possibly down"
network.


I couldn't seem to get the timings of when it was up and when it is
going down.

Any insights in this please?

Thanks
rajesh




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32501&t=32498
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to