[quagga-users 8012] Re: FW: bgp routes not being used by Linux

Collins, Richard (SNL US) rich.collins at siemens.com
Sun Feb 11 08:27:34 GMT 2007


Maybe you can show us some of the outputs of bgp (on that one router)
such as my
example.  You can see if the neighbor relationship has been established
and what routes are being received.

Rgds,
Richard


quagga# sh ip bgp 
BGP table version is 0, local router ID is 10.90.0.20
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 9.0.0.0/10       0.0.0.0                  0         32768 i
*> 10.10.90.0/24    0.0.0.0                  0         32768 i
*> 34.34.34.0/24    7.7.7.1                  0             0 254 i
*> 52.52.52.0/24    7.7.7.1                                0 254 400 40
e
*> 53.53.53.0/24    7.7.7.1                  0             0 254 i
*> 129.73.90.0/24   0.0.0.0                  0         32768 i
*> 172.36.1.0/24    7.7.7.1                                0 254 400 i

Total number of prefixes 7
quagga# sh ip bgp ne
quagga# sh ip bgp neighbors 
BGP neighbor is 7.7.7.1, remote AS 254, local AS 300, external link
  BGP version 4, remote router ID 1.1.1.1
  BGP state = Established, up for 00:00:47
  Last read 00:00:47, hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    Route refresh: advertised and received(old & new)
    Address family IPv4 Unicast: advertised and received
  Received 40 messages, 0 notifications, 0 in queue
  Sent 25 messages, 0 notifications, 0 in queue
  Route refresh request: received 0, sent 0
  Minimum time between advertisement runs is 30 seconds

 For address family: IPv4 Unicast
  Inbound soft reconfiguration allowed
  Community attribute sent to this neighbor(both)
  4 accepted prefixes

  Connections established 3; dropped 2
  Last reset 00:01:11, due to Peer closed the session
  External BGP neighbor may be up to 3 hops away.
Local host: 10.10.90.2, Local port: 50273
Foreign host: 7.7.7.1, Foreign port: 179
Nexthop: 10.10.90.2
Nexthop global: fe80::2b0:d0ff:fe98:4315
Nexthop local: ::
BGP connection: non shared network
Read thread: on  Write thread: off


>I'm not sure why bgpd is not updating the system routing table which is
>causing loop routing
> 
>PING surfer1(172.31.128.2) 56(84) bytes of data.
>>From 172.28.90.1: icmp_seq=0 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=1 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=2 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=3 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=4 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=5 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=6 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
>>From 172.28.90.1: icmp_seq=7 Redirect Network(New nexthop:
>nistnet2-eth1.ang.avaya.com (172.28.90.250))
> 
>--- surfer1 ping statistics ---
>8 packets transmitted, 0 received, 100% packet loss, time 7010ms
> 
>Can anyone suggest where I should look next?
> 
>Thanks for your help
> 
>Carol A. Sanders | QA  Engineer |  Avaya | Assured Networks Group |
1033
>McCarthy Blvd. | Milpitas, CA 95035 | 408.577.7518 |
>carolsanders at avaya.com <mailto:carolsanders at avaya.com>   




More information about the Quagga-users mailing list