11

I'm having a weird issue. Here is the setup. We have 2 Foundry SX's.

SX01 --->  ISPA
|
|
SX02 --->  ISPB

I have a /24 from ISPA and another /24 from ISPB. Both /24's are able to be announced to each of the providers.

iBGP runs between the two SX's and eBGP is being used from each of the SX's to the respective ISP.

So, I have the following on the SX's:

ip route 1.1.1.0/24 null0
ip route 2.2.2.0/24 null0

I also have prefix-lists configured for each of the /24's and configured the bgp neighbors to make use of the prefix-lists.

My problem is that whenever I add the above null routes to both routers at the same time, I get connectivity issues and complete packetloss. I've tried changing the administrative distance on these static routes but with no luck. If I only add these null routes to one of the SX's and remove them from the other, then the prefixes get announced fine to the respective ISP and things work fine.

Any ideas how to fix? On cisco devices, it's as simple as adding the above commands to both edge routers so not sure why this isn't working at the moment.

  • Did any answer help you? if so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. – Ron Maupin Aug 8 '17 at 9:22
8

Check that you actually have valid internal routes for these networks to override the routes to null0. If there are no more-specific or more-preferable routes for these networks, the routers will of course discard traffic destined for them.

| improve this answer | |
4

Your anchor routes are correct, but to override those routes you'll need more-specifics in your IGP. How you go about that is really dependent on your network layout, but for an example....

Say you have a couple of different router ports with a /28 assigned to each. One router will now have more specifics and will not blackhole traffic destined to those /28s, but the other router won't know about them unless you advertise them in your IGP (OSPF, IS-IS, etc). The routers will still send traffic for unused subnets to null0 until you have a valid more-specific route to them.

You want to keep those anchor routes so BGP will be able to advertise the /24s. If you have the /24s assigned to a single port(s) and aren't subnetting them at all, then you don't need the anchor routes. Basically your routing table needs to have a valid route to the /24s (whether to a live port or the null0 static) before BGP will advertise those routes. You just need to make sure you are redistributing more specifics in your IGP so the routers know where to send valid traffic.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.