Because the ipv4 address family is the default context within router bgp (for legacy reasons) all the subsequent commands are executed within the address-family ipv4 context removing next-hop self from neighbors in IPv4 address family.

No wonder David Barroso named his library NAPALM (you’ll find the full story in this or this podcast).

Related posts by categories

6 comments:

if you are still thinking about box level commit check, it is time to change :) it doesn't matter if network OS is still cmd by cmd, what you need is a network wide "show|compare" and "commit|check", it doesn't mater if underneath is IOS or Cumulus or JUNos, EOS ....

Hi Eric! I totally understand you love what your company is doing, but in essence it's just replacing the point of lock-in. See also http://blog.ipspace.net/2015/01/lock-in-is-inevitable-get-used-to-it.html

Yeah they made a bunch of legacy support decisions with XR when they should have just thrown it all out. Automatic context switching, ambiguous "no" statements to delete config. Not being able to define empty prefix-lists is another peeve of mine.

Speaking about "automatic context switching", did it ever happen to you to try to apply a route-policy to a peer, but forget to mention in or out ? If so, have you realised what happened before or after "commit" ? :) IOS-XR case....

The author

Ivan Pepelnjak (CCIE#1354 Emeritus), Independent Network Architect at ipSpace.net, has been designing and implementing large-scale data communications networks as well as teaching and writing books about advanced internetworking technologies since 1990.