[j-nsp] BGP/L3 routing support on EX2200 & EX2200-C

[Mark Tinka]

On Saturday, November 30, 2013 10:09:23 PM Saku Ytti wrote:

> I'm not sure the idealized BGP design from RFC translates
> this directly to any particular implementation.

This is specific to IOS, and by extension, IOS XE.

I've never been sure whether Juniper's "show route receive-
protocol bgp" command is similar to "soft-reconfiguration 
inbound" on Cisco. Do you know?

> However reason why people still use it, it helps with
> troubleshooting.

That's the common reason I still hear, but considering how 
well understood BGP is these days, I get more 
troubleshooting done by getting my peer to send me an e-mail 
with what they are sending to me.

The code has matured significantly that unless in the most 
rare of cases (which tend to be on older hardware that run 
older code), if your neighbor is sending you something you 
aren't receiving, chances are it's a filtering issue on your 
end. There isn't much to check in the way of what could be 
wrong, even on weird OS's like IOS which don't do syntax 
checking for common problems like spelling errors. 
Typically, it's route maps, prefix lists, AS_PATH filter 
lists and link MTU.

For me, since Route Refresh works, and works well, the hit 
you take on memory for enabling "soft-reconfiguration 
inbound" is not worth it. If you had to ask me the last time 
I had a need to use this feature, I'd be very hard-pressed 
to remember as well.

That said, IOS XR allows you to enable "soft-reconfiguration 
inbound" with an option to create or not create a second 
RIB. IOS and IOS XE are all-or-nothing.

"soft-reconfiguration inbound" can be helpful if your 
neighbor does not support Route Refresh. But in this 21st 
century, you're more likely to find someone running BGP 
version 3 than code that doesn't support Route Refresh :-).

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20131130/bc8d6dc3/attachment.sig>