From: Kian Wah Lai (kian_wah@aces-star.com)
Date: Wed Apr 27 2005 - 13:20:39 GMT-3
Hi,
RIPv2 does not broadcast by default. There is a command to make it do so.
Neighbor statements makes the RIP sends a unicast update to the neighbor in
addition to broadcast/multicast if you have them configured.
Based on your configuration, that is the expected behavior. I am not very
sure what you are asking but if you want RIP to multicast and unicast in
your configuration, you have to add "no passive e0/0.312" and not the "no
passive e0/0"
Regards,
Kian Wah
http://www.aces-star.com
Your Asia Pacific Rack Rental Source.
Ace the CCIE lab with it!
-----Original Message-----
From: Ed Lui [mailto:edwlui@gmail.com]
Sent: Thursday, April 28, 2005 12:15 AM
To: gladston@br.ibm.com
Cc: ccielab@groupstudy.com
Subject: Re: RIP - No Multicast Without Passive
Gladston,
I think rip ver 2 doesn't send broadcast and with the neighbor
statement. It turns multicast to unicast.
HTH,
Ed Lui
On 4/27/05, gladston@br.ibm.com <gladston@br.ibm.com> wrote:
> Have you seen this behavior?
>
> It was not necessary passive interface to avoid broadcast. Version is
12.2T.
>
> I always used neighbor and passive interface under RIP, and if may memory
is not kiding me, once I do not used passive and RIP multicast updates,
besides unicast it. (version was 12.2)
>
> BB2#deb ip rip
> RIP protocol debugging is on
> BB2#deb ip pa
> IP packet debugging is on
> BB2#clear ip ro *
> BB2#
> *Mar 1 02:24:07.275: RIP: sending v2 flash update to 150.100.20.1 via
Ethernet0/0.312 (150.100.20.254)
> *Mar 1 02:24:07.275: RIP: build flash update entries
> *Mar 1 02:24:07.275: 150.100.1.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.275: 150.100.2.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.275: 150.100.3.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.279: 150.100.4.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.279: 150.100.5.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.279: 150.100.6.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.279: 150.100.7.0/26 via 0.0.0.0, metric 1, tag 0
> BB2#
> *Mar 1 02:24:07.279: 150.100.8.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:07.283: IP: s=150.100.20.254 (local), d=150.100.20.1
(Ethernet0/0.312), len 192, sending
> BB2#
> *Mar 1 02:24:13.914: RIP: sending v2 update to 150.100.20.1 via
Ethernet0/0.312 (150.100.20.254)
> *Mar 1 02:24:13.914: RIP: build update entries
> *Mar 1 02:24:13.914: 150.100.1.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.914: 150.100.2.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.914: 150.100.3.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.918: 150.100.4.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.918: 150.100.5.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.918: 150.100.6.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.918: 150.100.7.0/26 via 0.0.0.0, metric 1, tag 0
> *Mar 1 02:24:13.918: 150.100.8.0/26 via 0.0.0.0, metric 1, tag 0
> BB2#
> *Mar 1 02:24:13.922: IP: s=150.100.20.254 (local), d=150.100.20.1
(Ethernet0/0.312), len 192, sending
> BB2#no deb all
> All possible debugging has been turned off
> BB2#sh run | b router rip
> router rip
> version 2
> passive-interface default
> no passive-interface Ethernet0/0
> network 150.100.0.0
> neighbor 150.100.20.1
> no auto-summary
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:55:09 GMT-3