Well so much for my ascii art router1 -- 2620:0:5100:1::/64
2620:0:5100:8:::/64 router3 --- 2620:0:5100:0::/64 router4 router2 -- 2620:0:5100:3::/64 so basically 2620:0:5100:8/64 goes between router1 and router2 the :1: and the :3: networks connect routers 1 and router 2 to router 3 and the :0: subnet connects router 4. On Sun, May 16, 2010 at 9:52 PM, George B. <[email protected]> wrote: > Ran into an odd problem with BGP4+ and a route reflector client > > > ROUTER 1-------------------2620:0:5100:1::/64 > | | > | | > | | > 2620:0:5100:8::/64 ROUTER > 3----------2620:0:5100:0::/64-----ROUTER 4 > | | > (route reflector client) > | | > | | > ROUTER 2-------------------2620:0:5100:3::/64 > > > > I am also running RIPng. > > Router #4 saw 2620:0:5100:8::/64 via RIPng but not via BGP. Router 3 > was not announcing the network to Router 4 even though Router 4 is > configured as a route reflector client. > > > Kicked the sessions between ROUTER3 and ROUTER1 and ROUTER3 and > ROUTER2 and suddenly it began announcing the route to ROUTER4. No > amount of clearing the sessions to ROUTER4 would result in ROUTER3 > sending the route. Once I cleared ROUTER3's upstream sessions, it > sent the route downstream. > > Never seen anything like it. > _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
