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

[tao liu]

following is the config for bgp and show ip route, thanks

router bgp 65453
 no synchronization
 bgp router-id 192.168.96.2
 bgp log-neighbor-changes
 redistribute connected route-map NEW
 redistribute static route-map NEW
 neighbor 192.168.2.49 remote-as 65450
 neighbor 192.168.2.49 send-community
 neighbor 192.168.96.1 remote-as 65453
 neighbor 192.168.96.1 update-source Loopback0
 neighbor 192.168.96.1 next-hop-self
 no auto-summary

ip bgp-community new-format

route-map NEW permit 10
 set community 65453:100

routerB#show ip route 192.168.2.50
Routing entry for 192.168.2.50/32
  Known via "connected", distance 0, metric 0 (connected)
  Redistributing via bgp 65453
  Routing Descriptor Blocks:
  * directly connected, via Multilink1
      Route metric is 0, traffic share count is 1

routerB#show ip route connected :
C        192.168.2.48/29 is directly connected, Multilink1
C        192.168.2.49/32 is directly connected, Multilink1
L        192.168.2.50/32 is directly connected, Multilink1


routerB#show ip int multilink 1
Multilink1 is up, line protocol is up
  Internet address is 192.168.2.50/29
  Broadcast address is 255.255.255.255
  Address determined by non-volatile memory
  Peer address is 192.168.2.49
  MTU is 1500 bytes
  Helper address is not set
  Directed broadcast forwarding is disabled
  Outgoing access list is not set
  Inbound  access list is not set
  Proxy ARP is enabled
  Local Proxy ARP is disabled
  Security level is default
  Split horizon is enabled
  ICMP redirects are always sent
  ICMP unreachables are always sent

On Tue, Apr 19, 2011 at 9:12 PM, Harold 'Buz' Dale <buz.dale at usg.edu> wrote:

> 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/
>