Chances are it's not installing the bgp routes because it doesn't know the "next hop" for those routes (ie: juniper to ISP). Two ways to fix it:
1.) add the /30 between the Juniper and ISP into your IGP (static or via ospf). Or... 2.) use "next-hop-self" on both boxes (only required on the Juniper to fix this problem, but you'll have the same issue with the J learning routes from the XMR, so use it there too). Unlike eBGP, iBGP peers don't set themselves as the next hop when advertising routes. You can check if this is the case by doing a "show ip route 1.1.1.1" on your XMR where 1.1.1.1 is the /30 between your juniper and your ISP. If nothings there then this is your fix. Good luck, Jared On Dec 22, 2010, at 1:18 AM, Brendan Mannella <[email protected]> wrote: > Hello, > > So i am bringing up a new XMR router, i have two border routers. One > is the new xmr and other is a juniper. So the juniper has a eBGP > session with a transit taking full routes. I brought up IBGP between > the Juniper and XMR. > > "IBGP Peer IP Here" "ASN here" ESTAB 0h20m59s 333495 > 0 9 0 > > So as you can see it has 333k routes that it accepted. But its like > its not installing them in the routing table. All i see are internal > connected routes, loopbacks, and statics in my routing table. > > If i do > > sh ip route 8.8.8.8 i get > > sh ip route 8.8.8.8 > Can't find matching entry > > Maybe i am missing something stupid, but i cant understand why its not > showing all 333k routes in the routing table. > > Any ideas? > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
