+1 What Chris said. Shouldn't be anything complex about these. Should be flat IX with a variety of next-hops on the same subnet, not the route-server.
Cheers Mike On 11 April 2016 at 09:09, Chris Kawchuk <juniperd...@gmail.com> wrote: > 1. Do you have an import policy on the BGP session to the route server? > (seeing if maybe you're overwriting protocol-next-hop -- or you may have > an inherited policy at a higher level than the group/neighbour...dunno) > > 2. As you mentioned, What does 'show route receive-protocol bgp > <neighbour.ip.of.the.session>' say in terms of the next hop it's sending? > You said route-server member, but that doesnt make sense if it's a /24 or > something "flat" peering exchange, it should return the next hop of the > actual peer (and not the route server's IP).. unless the topology of the > exchange is different from what I'm expecting. > > I think you're likely doing everything right, but if you can send > (sanitised) configs for: > > ergo: > > show configuration protocols bgp > show configuration policy-options > show route receive-protocol bgp <ip.of.bgp.session> extensive > > the 'next hop self' export policy should be on iBGP to the rest of your > network. No need to next-hop self on an eBGP session, since JunOS does this > for you automatically. > > - Ck. > > > > On 11 Apr 2016, at 8:27 am, Jeffrey Nikoletich <je...@xfernet.com> wrote: > > > First post here. We recently switched from Cisco to juniper and it has > been > > an adventure to say the least. We are running in to an issue with BGP > > session with peering exchanges route servers. The session comes online > and > > doing a received-protocol it is showing the correct next hop of the other > > route server member. When doing a show route it is showing the next hop > as > > the IP of the route server itself. As you can imagine, it is not passing > > traffic correctly. > > > > > > > > We have set the next hop self on the export policy but how do we fix the > > inbound next hop? > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Michael Gehrmann Senior Network Engineer - Atlassian m: +61 407 570 658 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp