From: Eagle (ddycus@gmail.com)
Date: Tue Oct 09 2007 - 10:05:06 ART
Two thoughts. Perhaps a bug in the "default passive-interface" feature
you're relying on to set your interfaces to passive globally?
Also, I can't tell from your config snippits what your broadcast
configuration looks like. You might try adding "no ip directed-broadcast"
to the individual interfaces that you don't want to send updates.
Other than that, I am in agreement with you... looks like those statements
shouldnt be in R1's table...
-Eagle
On 10/9/07, ccie1101 <ccie1101@gmail.com> wrote:
>
> Hi Grace,
> Yes, your understanding is correct. Since we only want one
> interface
> on R2 to participate in RIP, therefore that particular interface will be
> active and the others are passive as with the 'passive-interface default'
> command.
>
> As for split-horizon, it is turned off when we do a encapsulation
> frame-relay on the router. Therefore, I turned on split-horizon since I
> need
> this serial interface to send and receive updates on this serial
> interface.
>
> The connection for this network is R2 --- serial interface --- R1.
>
> It really buffles me, anyone care to explain this ? Argggghhh ...
> or
> am i missing something here .....
>
> Thanks in advance,
>
> Cheers,
> - ccie1101.
>
>
> On 10/9/07, Grace Simon <SimonG@pcsystems.gr> wrote:
> >
> > My understanding is passive interface just stops it sending updates out
> > of those interfaces.
> >
> > By configuring network 7.0.0.0
> >
> > You are telling the RIP process what networks to include in the updates.
> >
> > Split Horizon is stopping it from advertising a route that it learnt via
> > that interface. If this router is a hub with two or more spokes then by
> > disabling the split horizon you allow the routes to be passed from one
> > spoke to the other.
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> > ccie1101
> > Sent: Monday, October 08, 2007 8:31 PM
> > To: Cisco certification
> > Subject: Re: RIP Question across FR ......
> >
> > Hi GS,
> > I have a RIP scenario here which is as follows . Here is my
> > configuration :-
> >
> > R2
> > --
> > router rip
> > version 2
> > passive-interface default
> > no passive-interface Serial0/1/0
> > network 7.0.0.0
> > no auto-summary
> > !
> > !
> > int s0/0/0
> > no ip split-horizon
> >
> > ------------------------------------------------------------
> > R2#sh ip rip data
> > 7.0.0.0/8 auto-summary
> > 7.7.1.0/24
> > [1] via 7.7.13.1, 00:00:16, Serial0/1/0
> > 7.7.3.0/24 directly connected, Loopback0
> > 7.7.13.0/24 directly connected, Serial0/1/0
> > 7.7.30.0/24 directly connected, FastEthernet0/1
> > 7.7.35.0/24 directly connected, FastEthernet0/0
> > 7.7.100.0/24 directly connected, Serial0/0/0
> > !
> > ------------------------------------------------------------
> >
> > Now when I do a 'sh ip route rip' on the other end of the frame-relay
> > link,
> > I still see these
> > networks that is connected to R2 even though all those interfaces are in
> > passive-interface
> > mode ....
> >
> > R1(config)#do sir rip
> > 7.0.0.0/24 is subnetted, 6 subnets
> > R 7.7.0.0 [120/1] via 7.7.13.3, 00:00:15, Serial0/0/0
> > R 7.7.40.0 [120/1] via 7.7.13.3, 00:00:15, Serial0/0/0
> > R 7.7.45.0 [120/1] via 7.7.13.3, 00:00:15, Serial0/0/0
> > R 7.7.150.0 [120/1] via 7.7.13.3, 00:00:15, Serial0/0/0
> >
> > (1) Can someone explain if I am missing something here ?
> > (2) Since this connection is across the frame-relay link, I have turned
> > on
> > split-horizon as the
> > default mode for split-horizon is turned off when we use the command
> > 'encap frame-relay' ....
> >
> > Thanks in advance,
> >
> > Cheers,
> >
> > ccie1101.
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:12 ART