[rbak-nsp] BGP routes rcvd 1, imported 0, active 0

[support at ecn.net.au]

BGP neighbor: 10.99.99.3, remote AS: 9652, internal link

  Version: 4, router identifier: 10.99.99.3

  State: Established for 00:12:47

  Last read 00:00:41, last send 00:00:48

  Hold time: configured 180, negotiated 180

  Keepalive time: configured 60, negotiated 60

  Local restart timer 120 sec, stale route retain timer 180 sec

  Received restart timer 0 sec, flag 0x0

  Minimum time between advertisement runs: 5 secs

  Source IP address used from interface: loopback-mpls

  Source (local) IP address: 10.99.99.129

  Next hop set to self (next-hop-self)

  Received messages: 17 (613 bytes), notifications: 0, in queue: 0

  Sent messages: 17 (474 bytes), notifications: 0, out queue: 0



  CapSent: refresh, 4byteAS, unicast, vpn, restart

  CapRcvd: refresh, 4byteAS, unicast, vpn



  Address family: ipv4 unicast

    BGP table version: 0, neighbor version: 0

    Routes: rcvd 0, imported 0, active 0, history 0, dampend 0, sent 0



  Address family: ipv4 vpn

    BGP table version: 25, neighbor version: 25

    Routes: rcvd 1, imported 0, active 0, history 0, dampend 0, sent 2





In this example we have a BGP session with a far-end router (10.99.99.3)



The Redback has a BGP peer with that router:



  neighbor 10.99.99.3 internal

    update-source loopback-mpls

    next-hop-self

   address-family ipv4 unicast

   address-family ipv4 vpn





The far end router (cisco 6500) can see routes from the VPN Context on the Redback, however he redback isn't adding the routes into the routing table of the customer context:



(see below the 172.16.254.250 is visible in "show bgp route" but it isn't in "show ip route".



[TEST_VRF]Redback#show bgp route

Address Family: ipv4 unicast

BGP table version is 25, local router ID is 10.99.99.129

Status codes: d damped, h history, > best, i internal

Origin codes: i - IGP, e - EGP, ? - incomplete





VPN RD: 13015:10

   Network            Next Hop                Metric  LocPrf  Weight Path

>  10.254.254.0/24    0.0.0.0                      0     100   32768 ?

 i 172.16.254.250/32  10.99.99.3                   0     100     100 ?

>i 172.16.254.251/32  10.99.99.1                   0     100     100 ?

>  172.16.254.252/32  0.0.0.0                      0     100   32768 ?

>i 192.168.1.1/32     10.99.99.1                   0     100     100 ?





Sure it is an simple issue but it's just stumping us.



10.99.99.3  (the BGP peer) is not directly connected (it's essentially PE(10.99.99.129)->PE(10.99.99.1)->PE(10.99.99.3))  (10.99.99.x/32 is used for loopbacks).?





Kind Regards,


ECN

The information contained in this mail message is confidential and may also be legally privileged.  If you are not the intended recipient, please note that any use, dissemination, further distribution, or reproduction of this message in any form whatsoever, is strictly prohibited.  If the mail is in error, please notify me by return E-mail, delete your copy of the message, and accept my apologies for any inconvenience caused.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20141112/b94c0c66/attachment.html>