[c-nsp] no bgp route from 0.0.0.0 for a interface ip address

[Harold 'Buz' Dale]

At first blush it looks like 192.168.2.50 can't talk to anyone.  Try changing his mask to /31 or something so that 192.168.2.49 is on the same network..
----
BGP routing table entry for 192.168.2.50/32
----

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of tao liu
Sent: Tuesday, April 19, 2011 8:55 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] no bgp route from 0.0.0.0 for a interface ip address

Why bgp route from 0.0.0.0 doesn't exist, 192.168.2.50 is a interface ip
address on routerB!
Instead bgp route for 192.168.2.50 is from "192.168.96.1" and
"192.168.2.49", it is strange.
we redistribute static and connected on all four routers.
the topology like below:


lo0:192.168.96.2                lo0:192.168.96.1
routerA                 ----   ebgp  -----     routerB
------ibgp-------- routerBB
              192.168.2.49
192.168.2.50                                             |
|
|
|----------------ibgp--------------------------routerAA--------ebgp---------------

routerB# show ip bgp 192.168.2.50
BGP routing table entry for 192.168.2.50/32, version 151
Paths: (2 available, best #2, table default, RIB-failure(17) - next-hop
mismatch
)
  Advertised to update-groups:
     1
  65450
    192.168.96.1 from 192.168.96.1 (192.168.96.1)
      Origin incomplete, metric 0, localpref 100, valid, internal
  65450
    192.168.2.49 from 192.168.2.49 (192.168.0.2)
      Origin incomplete, metric 0, localpref 100, valid, external, best
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/