i BGP next hop self issue

[Sumanta_Ghosh]

Next hop self not working as expected in i-BGP peering. We have e-BGP peering across Extreme pair of L3 switches towards ISP routers. Also we have i-BGP peering between application nodes and the Extreme switches. Refer to diagram below. Default route is advertised by ISP routers and reaches Extreme A and B, but not till Application node at the left-most side. Next-hop self is enabled for IPv6, still I can see on Extreme that the default route next hop is shown as the ISP router interface, instead of the Extreme switch.

This works fine with IPv4, as expected.

[Jeremy_Gibbs]

Why are you using BGP for this? Sounds like you should be using eBGP at the edge, and using OSPF to do route redistribution.

A topology drawing with interfaces that are labeled would be helpful.

Also, it depends on what you are doing with ipv6. Do you have v6 routes that you are learning about via iBGP from your application stack or the other way around?

I am assuming you are using BGP to advertise some public IP addresses and not do route selection (since you said you are only receiving a default route from your ISP.

I would run iBGP between both the Extreme 670s and another routing protocol between the applications.

[Sumanta_Ghosh]

Hi Experts

Any assistance please on this? We have some time constraints on this.

[Sumanta_Ghosh]

Hi Jeremy

Please see snapshot of BGP config. i-BGP is across switches A and B, for IPv4 and with the left most side application nodes, running BGP. Do we need IPv6 across switch A and B as well?

e-BGP is across switches and ISP routers.

[Sumanta_Ghosh]

Also, it is under a child VR.

[Jeremy_Gibbs]

What does the config look like? Are you using a loopback for the iBGP stuff?