Generally, announced AFs depends only on channels, it is irrelevant whether peers are IPv4 or IPv6. Perhaps you have some channels inherited from templates? Could you send the config file?
Well, "show protocols all" says there's only one channel:
ipv4_X BGP --- up 2018-04-20 Established BGP state: Established Neighbor address: X.X.X.X Neighbor AS: X Neighbor ID: X.X.X.X Local capabilities Multiprotocol AF announced: ipv4 ipv6 Route refresh Graceful restart 4-octet AS numbers Enhanced refresh Neighbor capabilities Multiprotocol AF announced: ipv4 Route refresh 4-octet AS numbers Session: internal AS4 Source address: X.X.X.X Hold timer: 94.575/180 Keepalive timer: 10.969/60 Channel ipv4 State: UP Table: master4 Preference: 100 Input filter: ibgp_in Output filter: (unnamed) Routes: 4 imported, 693644 exported Route change stats: received rejected filtered ignored accepted Import updates: 14 0 0 4 10 Import withdraws: 0 0 --- 0 0 Export updates: 3983676 10 9177 --- 3974489 Export withdraws: 872997 --- --- --- 865206 BGP Next hop: X.X.X.X
bird>
The config (with templates merged) essential is this:
protocol bgp ipv4_X { local as my_asn; neighbor as my_asn; direct;
ipv4 { next hop self; import filter ibgp_in; export where source = RTS_BGP; }; neighbor X.X.X.X; }
Version is 2.0.2 btw. Best regards, Jan-Philipp Litza -- Jan-Philipp Litza PLUTEX GmbH Hermann-Ritter-Str. 108 28197 Bremen Hotline: 0800 100 400 800 Telefon: 0800 100 400 821 Telefax: 0800 100 400 888 E-Mail: support@plutex.de Internet: http://www.plutex.de USt-IdNr.: DE 815030856 Handelsregister: Amtsgericht Bremen, HRB 25144 Geschäftsführer: Torben Belz, Hendrik Lilienthal