From: dhbrown@xxxxxxxxxxxx
Date: Fri Mar 17 2000 - 18:24:54 GMT-3
I duplicated this in my environment (different IPs), and found the same thing.
I get a debug error: "IGRP: received update from invalid source 10.2.1.3 on BV
I1" which prompted adding the command "no validate-update-source" to the IGRP p
rocess -- with no change. I also added a neighbor command to the other (non-BV
I) router, again no success. Then I added a Loopback to the BVI router and adde
d the loopback as a neighbor as well, no change. I enable IP Directed Broadcas
t on BVI and the incoming interface, no change. I also added another Ethernet
interface to the unicast neighbor list, no change.
>From the debugs, it looks like the BVI is receiving the broadcast (and the uni
cast) and then not allowing it to pass through to the IGRP process. Anyone els
e??
David
(RTP Lab 3/23-3/24)
Ronald Johnson <rjohnson@ebnetworks.com> wrote:
> Thanks for your responses guys but I'm not sure we have this one nailed yet.
I have heard a couple of different suggestions. One was to enable a BVI interf
ace (this was already in the config), the second suggestion was to turn off bri
dging for IP (if only bridging is enabled, things work fine.. I only run into p
roblems when I create the BVI interface. Bridging works fine by itself, so turn
ing off bridging for IP does not make a difference). Another suggestion was to
create the BVI and add a network statement under the IGRP routing process that
included the ip address of the BVI. If you reference the config you will see th
at this was already done as well...
So guys.. the jury is still out on this one. What I am not sure about is how th
e IGRP updates are sourced once the BVI is created. If I debug the IGRP updates
it shows that updates are sourced not only by the BVI, but the Serial 0 interf
ace as well. As I mentioned in my previous e-mail.. I am still receiving update
s just fine on Router A. According to router A, I am still sending them.. Howev
er, there is something weird about the creation of the BVI on Router A that is
keeping router B from receiving IGRP updates as usual.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:05 GMT-3