["no activate" ipv6 neighbor under ipv4 address-family]

[Carlos A. Silva]

Hi!

Is it normal for a BGP ipv6 neighbor to appear under ipv4 address-family as "no activate"?

This is on an ASR1000 working as RR, running IOS XE.

For example:

(I removed many commands for brevity, but that's a real config)

router bgp AAAAAA

neighbor X:X:X::X remote-as AAAAAA
neighbor X:X:X::X description BBBBBBB
neighbor X:X:X::X password CCCCCC
neighbor X:X:X::X update-source Loopback0

[snip]

address-family ipv4

no neighbor X:X:X::X activate <---appeared by itself

[snip]

address-family ipv6
neighbor X:X:X::X activate

Maybe it is OK, just haven't ran across this before.

Thanks!

c.

(Sorry, this is a duplicate post. The first one I opened in the wrong place)

**Edit: Just tested this in a simulation and as soon as I activate the neighbor under 'address-family ipv6 unicast', the router creates an ipv4 no activate entry under 'address-family ipv4'. This makes the configuration ridiculously long. Same goes for a 'show ip bgp summary' command. Tons of idle ipv6 neighbors. Is there a way to avoid this?

**Edit:

Seems the command "no bgp default ipv4-unicast" fixes the whole thing. Hope this helps someone.

[Harold Ritter]

Hi Carlos,

Yes, this is normal behavior. The previous behavior in IOS was to activate address-family ipv4 for all neighbors, including the ipv6 neighbor. This behavior was changed a couple of years back to configure an explicit "no neighbor activate" for ipv6 neighbor", therefore if you ever need to activate address-family ipv4 on an ipv6 neighbor (not recommended), you should explicitly configure it.

Regards,